From owner-freebsd-current Mon Jan 1 2:25:19 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 02:25:17 2001 Return-Path: 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 876A137B400; Mon, 1 Jan 2001 02:25:16 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f01AP9q36404; Mon, 1 Jan 2001 11:25:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: John Baldwin , current@FreeBSD.ORG Subject: Re: Current hangs... In-Reply-To: Your message of "Sun, 31 Dec 2000 18:04:50 PST." <200101010204.f0124oW47215@earth.backplane.com> Date: Mon, 01 Jan 2001 11:25:08 +0100 Message-ID: <36402.978344708@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101010204.f0124oW47215@earth.backplane.com>, Matt Dillon writes: >: >:Why not this: >: >:s = splbio(); >:TAILQ_FOREACH(bp, &vp->v_dirtyblkhd, b_vnbufs) { > > First rule when making simple bug fixes by copying working code from one > source file to another is: Dont try to optimize the code on the > fly. > > Personally speaking, I don't find the FOREACH macros any more readable > vs an explicit for loop. They hide too much... like for example the > fact that you are dependant on the current pointer remaining valid to > get the next pointer in the loop. Is that any different from for (i = 0; i < N; i++) { bla; } ? -- 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 Mon Jan 1 3:28:53 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 03:28:51 2001 Return-Path: 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 CD5E037B402 for ; Mon, 1 Jan 2001 03:28:50 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f01BSjq37152; Mon, 1 Jan 2001 12:28:45 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: bloom@acm.org Cc: current@freebsd.org Subject: Re: Problem building md module In-Reply-To: Your message of "Sun, 31 Dec 2000 15:48:53 EST." <3A4F9BB5.F699D66B@acm.org> Date: Mon, 01 Jan 2001 12:28:45 +0100 Message-ID: <37150.978348525@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Committed, thanks! Poul-Henning In message <3A4F9BB5.F699D66B@acm.org>, Jim Bloom writes: >While trying to build a new kernel today, I received errors relating to >vnode_if.h not existing. I have put the patch below which fixed the >problem for me. (Sorry if the patch does not apply because of cut and >paste errors, but it may easily be hand editted.) > >Jim Bloom >bloom@acm.org > > >Index: Makefile >=================================================================== >RCS file: /users/ncvs/src/sys/modules/md/Makefile,v >retrieving revision 1.7 >diff -u -r1.7 Makefile >--- Makefile 2000/09/02 19:17:10 1.7 >+++ Makefile 2000/12/31 18:35:36 >@@ -2,7 +2,7 @@ > > .PATH: ${.CURDIR}/../../dev/md > KMOD= md >-SRCS= md.c opt_mfs.h opt_md.h >+SRCS= md.c opt_mfs.h opt_md.h vnode_if.h > NOMAN= > > .include > -- 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 Mon Jan 1 5:38:14 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 05:38:12 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from citusc.usc.edu (citusc.usc.edu [128.125.38.123]) by hub.freebsd.org (Postfix) with ESMTP id 309AA37B402 for ; Mon, 1 Jan 2001 05:38:12 -0800 (PST) Received: (from kris@localhost) by citusc.usc.edu (8.9.3/8.9.3) id FAA11684; Mon, 1 Jan 2001 05:39:29 -0800 Date: Mon, 1 Jan 2001 05:39:29 -0800 From: Kris Kennaway To: Raymond Hicks Cc: current@FreeBSD.ORG Subject: Re: buildworld still failing when going current Message-ID: <20010101053929.B11343@citusc.usc.edu> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="c3bfwLpm8qysLVxt" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from rayhicks@UU.NET on Sun, Dec 31, 2000 at 08:24:21PM -0500 Sender: kris@citusc.usc.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --c3bfwLpm8qysLVxt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sun, Dec 31, 2000 at 08:24:21PM -0500, Raymond Hicks wrote: > I have had this problem since yesterday... I cvsup using the supfile on > handbook for going current... i remove all from /usr/obj... I cd > /usr/src and make buildworld and I get the following errors.. I am > running 4.2 STABLE.. please lend a hand... You've fubar'ed something..restore from a backup or reinstall and try again. Kris P.S. Did I see you say you're running current on a remote machine with no serial console? That's not smart, even if you know what you're doing. --c3bfwLpm8qysLVxt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE6UIiRWry0BWjoQKURAtHNAJ4jcdc69lKWPjenkU3i0LDLM8R2lgCgvYnz hJLRy1maD30BFqIbXZ1M6dU= =2xz7 -----END PGP SIGNATURE----- --c3bfwLpm8qysLVxt-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 6:26: 2 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 06:26:00 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from Awfulhak.org (awfulhak.demon.co.uk [194.222.196.252]) by hub.freebsd.org (Postfix) with ESMTP id A932A37B400 for ; Mon, 1 Jan 2001 06:25:57 -0800 (PST) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.11.1/8.11.1) with ESMTP id f01EQ2r22304; Mon, 1 Jan 2001 14:26:02 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.1/8.11.1) with ESMTP id f01EP9263868; Mon, 1 Jan 2001 14:25:09 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200101011425.f01EP9263868@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: "Leif Neland" Cc: freebsd-current@FreeBSD.ORG, brian@Awfulhak.org Subject: Re: IGMP queries In-Reply-To: Message from "Leif Neland" of "Sat, 30 Dec 2000 18:32:36 +0100." <001f01c07286$9a055a00$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Jan 2001 14:25:09 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If it is true, how can I filter it to stop resetting the idle-timeout? I'm > on flat rate now, but even so I don't want to be online 24h/day... Add this to your ppp profile: set filter alive N deny igmp > Leif -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 6:51: 4 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 06:51:01 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from bsdconspiracy.net (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 5F0D637B400 for ; Mon, 1 Jan 2001 06:51:01 -0800 (PST) Received: from zaphod.softweyr.com ([204.68.178.35] helo=softweyr.com ident=wes) by bsdconspiracy.net with esmtp (Exim 3.14 #1) id 14D6Go-0001uZ-00; Mon, 01 Jan 2001 07:49:06 -0700 Sender: wes@FreeBSD.ORG Message-ID: <3A509994.D341766A@softweyr.com> Date: Mon, 01 Jan 2001 07:52:04 -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: "Louis A. Mamakos" Cc: Gerhard Sittig , freebsd-current@FreeBSD.ORG Subject: Re: IGMP queries References: <001f01c07286$9a055a00$0e00a8c0@neland.dk> <20001230215241.M253@speedy.gsinet> <200012311049.eBVAnBr23486@whizzo.transsys.com> <20001231215515.Q253@speedy.gsinet> <200101010546.f015k9r27506@whizzo.transsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Louis A. Mamakos" wrote: > > EGP hasn't been in wide use for probably 7 or 8 years now. > > I think the real problem with this dynamic link issue and keeping the > connection up is that the default policy is wrong. You ought to > specify what sort of traffic is "important" and should cause a > dynamic link to be established (and kept up), rather than trying > to exclude things. > > For example, you'd probably not want to have NTP establish or keep > your link up; perhaps not DNS, either. Probabably you'd want > TCP/SSH or TCP/HTTPD though. Most SSH and HTTP traffic is preceeded by a DNS lookup; if you don't allow the DNS traffic, the SSH or HTTP traffic will never occur. Trying to predict how these things happen is a non-obvious exercise that requires careful study or you will break things horribly. We tune our default firewall configuration by practicing on our real, live internet connection at work, just to make sure we're not cutting off our customers heads. It can be quite irritating at times, but fits with the "eat your own dog food" philosophy. -- Where am I, and what am I doing in this handbasket? Wes Peters wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 10:51:54 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 10:51:51 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cmr1.ash.ops.us.uu.net (cmr1.ash.ops.us.uu.net [198.5.241.39]) by hub.freebsd.org (Postfix) with ESMTP id 7E27337B400 for ; Mon, 1 Jan 2001 10:51:51 -0800 (PST) Received: from neserve0.corp.us.uu.net by cmr1.ash.ops.us.uu.net with ESMTP (peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148]) id QQjwcx08420; Mon, 1 Jan 2001 18:51:50 GMT Received: from localhost by neserve0.corp.us.uu.net with ESMTP (peer crosschecked as: rayhicks@localhost) id QQjwcx20453; Mon, 1 Jan 2001 13:51:50 -0500 (EST) Date: Mon, 1 Jan 2001 13:51:50 -0500 (EST) From: Raymond Hicks X-Sender: rayhicks@neserve0.corp.us.uu.net To: "Niels Chr. Bank-Pedersen" Cc: current@freebsd.org Subject: Re: buildworld still failing when going current In-Reply-To: <20010101054714.A1851@bank-pedersen.dk> 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 Thanks guy that worked for me although now when I make buildkernel KERNEL=GENERIC I get the following errors.. = something greater must be wrong? mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev -I@/../include -I/usr/obj/usr/src/i386/usr/include /usr/src/sys/modules/md/../../dev/md/md.c In file included from /usr/src/sys/modules/md/../../dev/md/md.c:28: @/sys/vnode.h:522: vnode_if.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/sys/modules/md. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. any help appreciated once again... On Mon, 1 Jan 2001, Niels Chr. Bank-Pedersen wrote: > You should be able to "bootstrap" yourself by using ``make -k buildworld'' > and ``make -k installworld''. After that, things should be back to normal. > There is probably other ways around it (and faster ones), but this worked > for me. > > On Sun, Dec 31, 2000 at 08:24:21PM -0500, Raymond Hicks wrote: > > I have had this problem since yesterday... I cvsup using the supfile on > > handbook for going current... i remove all from /usr/obj... I cd > > /usr/src and make buildworld and I get the following errors.. I am > > running 4.2 STABLE.. please lend a hand... > > > > uudecode < /usr/src/share/tabset/xerox1720.uu > > uudecode < /usr/src/share/tabset/xerox1730.uu > > uudecode < /usr/src/share/tabset/xerox1730-lm.uu > > uudecode < /usr/src/share/tabset/zenith29.uu > > ===> share/termcap > > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > > > /dev/null > > Segmentation fault - core dumped > > *** Error code 139 > > > > Stop in /usr/src/share/termcap. > > *** Error code 1 > > > > Stop in /usr/src/share. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > thanks > > raymond hicks > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > /Niels Chr. > > -- > Niels Christian Bank-Pedersen, NCB1-RIPE. > Network Manager, Tele Danmark NET, IP-section. > > "Hey, are any of you guys out there actually *using* RFC 2549?" > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 11: 0:50 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 11:00:47 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id F417037B402 for ; Mon, 1 Jan 2001 11:00:46 -0800 (PST) Received: by peitho.fxp.org (Postfix, from userid 1501) id 25CA01360E; Mon, 1 Jan 2001 14:00:46 -0500 (EST) Date: Mon, 1 Jan 2001 14:00:45 -0500 From: Chris Faulhaber To: Raymond Hicks Cc: current@freebsd.org Subject: Re: buildworld still failing when going current Message-ID: <20010101140045.A58209@peitho.fxp.org> References: <20010101054714.A1851@bank-pedersen.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rayhicks@UU.NET on Mon, Jan 01, 2001 at 01:51:50PM -0500 Sender: cdf.lists@fxp.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 01, 2001 at 01:51:50PM -0500, Raymond Hicks wrote: > Thanks guy that worked for me although now when I make buildkernel > KERNEL=GENERIC I get the following errors.. = something greater must be > wrong? > > mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/dev > -I@/../include -I/usr/obj/usr/src/i386/usr/include > /usr/src/sys/modules/md/../../dev/md/md.c > In file included from /usr/src/sys/modules/md/../../dev/md/md.c:28: > @/sys/vnode.h:522: vnode_if.h: No such file or directory > mkdep: compile failed > *** Error code 1 > Check cvs-all. This was fixed a few hours ago. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: 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 Mon Jan 1 11:34:51 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 11:34:45 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from jxmls04.se.mediaone.net (jxmls04.se.mediaone.net [24.129.0.51]) by hub.freebsd.org (Postfix) with ESMTP id 517A837B400 for ; Mon, 1 Jan 2001 11:34:45 -0800 (PST) Received: from FreeBSD.org (dbe114-124.jacksonville.net [24.129.114.124] (may be forged)) by jxmls04.se.mediaone.net (8.8.7/8.8.7) with SMTP id OAA09878 for ; Mon, 1 Jan 2001 14:29:30 -0500 (EST) Date: Mon, 1 Jan 2001 14:29:30 -0500 (EST) From: marketing@netoneplus.com Message-Id: <200101011929.OAA09878@jxmls04.se.mediaone.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=200101011026=" To: current@FreeBSD.org X-Mailer: 5D7D2827.4BEB6807.8ad4eb59de03b79336a171b889d6db59 Subject: Information on your website Organization: Net One Plus Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=200101011026= Content-Type: text/html;charset=US-ASCII Net 1 One Plus- www.netoneplus.com

If you are unable to view this page, please go to  www.netoneplus.com
www.netoneplus.com

 
www.netoneplus.com		  
.


Obtain  free
Web hosting!

Why pay for web hosting?

1

Receive a 6 page website, 3 years of 
domain name registrations and 1 year of hosting!

(click here for more information)

FREE hosting is available
to your website!
(click here for more information)

Or, if you are looking to start your
own website we have
"The Complete Choice!"
(click here for more information)

Hosting made easy!

Domain Registration E-Mail Forwarding
Multiple Access Connections Unlimited Updates
Via FTP
E-Mail Auto 
responders		 MS FrontPage extensions
Web Based 
Control Panel		 Detailed Web 
Usage Page
Access to Raw Log Files Your own local 
"cgibin" dir
SSL Secure Server 99% uptime
Guest book Email Forms
Search Engine Registration Unlimited POP
Email Accounts 

And much much more!

www.netoneplus.com
i

  .

If you feel that you have received this email in error,
please reply to remove@netoneplus.com with just the word remove in the subject line.
--=200101011026=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 13:46:48 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 13:46:44 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pimout4-int.prodigy.net (pimout4-ext.prodigy.net [207.115.63.103]) by hub.freebsd.org (Postfix) with ESMTP id 2BC1937B400 for ; Mon, 1 Jan 2001 13:46:44 -0800 (PST) Received: from ppp-207-193-3-100.kscymo.swbell.net (ppp-207-193-3-100.kscymo.swbell.net [207.193.3.100]) by pimout4-int.prodigy.net (8.11.0/8.11.0) with ESMTP id f01LkaZ118020 for ; Mon, 1 Jan 2001 16:46:36 -0500 Received: (from jbryant@localhost) by ppp-207-193-3-100.kscymo.swbell.net (8.11.1/8.9.3) id f01LkSN12741 for freebsd-current@freebsd.org; Mon, 1 Jan 2001 15:46:28 -0600 (CST) (envelope-from jbryant) From: Jim Bryant Message-Id: <200101012146.f01LkSN12741@ppp-207-193-3-100.kscymo.swbell.net> Subject: if_fpa.c is broke again. To: freebsd-current@freebsd.org Date: Mon, 1 Jan 101 15:46:26 -0600 (CST) Reply-To: kc5vdj@prodigy.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 4.0-RELEASE X-Mailer: ELM [version 2.4ME+ PL32 (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 Hi, it looks like if_fpa.c has been modified again, but was checked into CVS untested. from a basic GENERIC, with nothing other than the fddi and fpa devices added to the config, I get the attached messages on compile. also, i noticed that in pdareg.h, that the full duplex options are included in the structs, but they are used nowhere int he driver itself, that seems to use the adapter in half duplex mode. Are there plans to add the full duplex functionality in the near future? ----------------------- cc -c -O2 -mpentiumpro -march=pentiumpro -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/acpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/dev/pdq/if_fpa.c /usr/src/sys/dev/pdq/if_fpa.c:141: syntax error before `config_id' /usr/src/sys/dev/pdq/if_fpa.c:143: warning: function declaration isn't a prototype /usr/src/sys/dev/pdq/if_fpa.c: In function `pdq_pci_probe': /usr/src/sys/dev/pdq/if_fpa.c:144: `device_id' undeclared (first use in this function) /usr/src/sys/dev/pdq/if_fpa.c:144: (Each undeclared identifier is reported only once /usr/src/sys/dev/pdq/if_fpa.c:144: for each function it appears in.) /usr/src/sys/dev/pdq/if_fpa.c: At top level: /usr/src/sys/dev/pdq/if_fpa.c:152: syntax error before `config_id' /usr/src/sys/dev/pdq/if_fpa.c:154: warning: function declaration isn't a prototype /usr/src/sys/dev/pdq/if_fpa.c: In function `pdq_pci_attach': /usr/src/sys/dev/pdq/if_fpa.c:159: `unit' undeclared (first use in this function) /usr/src/sys/dev/pdq/if_fpa.c:165: warning: implicit declaration of function `pci_conf_read' /usr/src/sys/dev/pdq/if_fpa.c:165: `config_id' undeclared (first use in this function) /usr/src/sys/dev/pdq/if_fpa.c:169: warning: implicit declaration of function `pci_conf_write' /usr/src/sys/dev/pdq/if_fpa.c:176: warning: implicit declaration of function `pci_map_mem' /usr/src/sys/dev/pdq/if_fpa.c:194: warning: implicit declaration of function `pci_map_int' /usr/src/sys/dev/pdq/if_fpa.c: At top level: /usr/src/sys/dev/pdq/if_fpa.c:210: variable `fpadevice' has initializer but incomplete type /usr/src/sys/dev/pdq/if_fpa.c:211: warning: excess elements in struct initializer /usr/src/sys/dev/pdq/if_fpa.c:211: warning: (near initialization for `fpadevice') /usr/src/sys/dev/pdq/if_fpa.c:212: warning: excess elements in struct initializer /usr/src/sys/dev/pdq/if_fpa.c:212: warning: (near initialization for `fpadevice') /usr/src/sys/dev/pdq/if_fpa.c:213: warning: excess elements in struct initializer /usr/src/sys/dev/pdq/if_fpa.c:213: warning: (near initialization for `fpadevice') /usr/src/sys/dev/pdq/if_fpa.c:214: warning: excess elements in struct initializer /usr/src/sys/dev/pdq/if_fpa.c:214: warning: (near initialization for `fpadevice') /usr/src/sys/dev/pdq/if_fpa.c:216: warning: excess elements in struct initializer /usr/src/sys/dev/pdq/if_fpa.c:216: warning: (near initialization for `fpadevice') /usr/src/sys/dev/pdq/if_fpa.c:218: warning: type defaults to `int' in declaration of `COMPAT_PCI_DRIVER' /usr/src/sys/dev/pdq/if_fpa.c:218: warning: parameter names (without types) in function declaration /usr/src/sys/dev/pdq/if_fpa.c:218: warning: data definition has no type or storage class /usr/src/sys/dev/pdq/if_fpa.c:210: warning: `fpadevice' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ kc5vdj@prodigy.net KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOAM HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81A KPC3+ & PK-232MBX Grid: EM28px ------------------------------------------------------------------------------ ET has one helluva sense of humor, always anal-probing right-wing schizos! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 16:39:35 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 16:39:33 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from femail2.rdc1.on.home.com (femail2.rdc1.on.home.com [24.2.9.89]) by hub.freebsd.org (Postfix) with ESMTP id 6BCBE37B400 for ; Mon, 1 Jan 2001 16:39:33 -0800 (PST) Received: from foo ([24.114.70.142]) by femail2.rdc1.on.home.com (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010102003927.WQBC21590.femail2.rdc1.on.home.com@foo> for ; Mon, 1 Jan 2001 16:39:27 -0800 Message-ID: <000a01c0746d$cc35a960$0a00000a@bar.com> From: "Mike Poirier" To: Subject: subscribe Date: Mon, 1 Jan 2001 19:40:46 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0742A.BDD6E700" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0742A.BDD6E700 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0007_01C0742A.BDD6E700 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0007_01C0742A.BDD6E700-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 21:48:16 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 21:48:14 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.ticonet.co.cr (mail.ticonet.co.cr [196.40.4.5]) by hub.freebsd.org (Postfix) with ESMTP id 44C7137B400 for ; Mon, 1 Jan 2001 21:48:09 -0800 (PST) Received: from Popeye [196.40.53.184] by mail.ticonet.co.cr (SMTPD32-6.05) id AA08DC01E0; Mon, 01 Jan 2001 21:43:36 +0000 To: Happy@FreeBSD.ORG, New@FreeBSD.ORG, !!@Year.FreeBSD.ORG From: Oldies@FreeBSD.ORG, Online@FreeBSD.ORG, Casino@FreeBSD.ORG Subject: 01-01-2001 Date: Mon, 01 Jan 2001 22:50:03 -0600 Message-Id: <36892.951430312503400.159775@localhost> MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oldies Online Casino - Happy New Year!!!

Oldies Online Casino
Would like to welcome you and your family a Happy New Year!

We Would also like to offer ALL NEW & EXISTING Members a
Holiday 25% Bonus
Oldies Online Casino offers Free no download Flash Internet
gambling, games include craps, keno, slots, video poker,
roulette and blackjack in real time. Play for fun or cash!
http://www.oldiesonlinecasino.com

to unsubscribe click here

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 1 21:59:56 2001 From owner-freebsd-current@FreeBSD.ORG Mon Jan 1 21:59:52 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.ticonet.co.cr (mail.ticonet.co.cr [196.40.4.5]) by hub.freebsd.org (Postfix) with ESMTP id E9CF837B402; Mon, 1 Jan 2001 21:59:46 -0800 (PST) Received: from Popeye [196.40.53.184] by mail.ticonet.co.cr (SMTPD32-6.05) id AA4327B01DA; Mon, 01 Jan 2001 22:52:51 +0000 To: Happy@FreeBSD.ORG, New@FreeBSD.ORG, !!@Year.FreeBSD.ORG From: Oldies@FreeBSD.ORG, Online@FreeBSD.ORG, Casino@FreeBSD.ORG Subject: 01-01-2001 Date: Mon, 01 Jan 2001 23:59:16 -0600 Message-Id: <36892.999497453704000.238432@localhost> MIME-Version: 1.0 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oldies Online Casino - Happy New Year!!!

Oldies Online Casino
Would like to welcome you and your family a Happy New Year!

We Would also like to offer ALL NEW & EXISTING Members a
Holiday 25% Bonus
Oldies Online Casino offers Free no download Flash Internet
gambling, games include craps, keno, slots, video poker,
roulette and blackjack in real time. Play for fun or cash!
http://www.oldiesonlinecasino.com

to unsubscribe click here

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 0:23:11 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 00:23:07 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (c1315225-a.plstn1.sfba.home.com [65.0.135.147]) by hub.freebsd.org (Postfix) with ESMTP id 3BB1237B404 for ; Tue, 2 Jan 2001 00:23:07 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id f028NN807893; Tue, 2 Jan 2001 00:23:24 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200101020823.f028NN807893@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: kc5vdj@prodigy.net Cc: freebsd-current@FreeBSD.ORG Subject: Re: if_fpa.c is broke again. In-Reply-To: <200101012146.f01LkSN12741@ppp-207-193-3-100.kscymo.swbell.net> Date: Tue, 02 Jan 2001 00:23:23 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Bryant wrote: > Hi, it looks like if_fpa.c has been modified again, but was checked > into CVS untested. Actually, the problem is the opposite.. It has not been modified, but some of the old backwards compatability infrastructure got cleaned out, leaving fpa broken. It doesn't appear to be too hard to adapt to newbus, is it a major showstopper for you? > from a basic GENERIC, with nothing other than the fddi and fpa devices > added to the config, I get the attached messages on compile. > > also, i noticed that in pdareg.h, that the full duplex options are > included in the structs, but they are used nowhere int he driver > itself, that seems to use the adapter in half duplex mode. Are there > plans to add the full duplex functionality in the near future? > > ----------------------- > cc -c -O2 -mpentiumpro -march=pentiumpro -pipe -Wall -Wredundant-decls -Wnest ed-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winli ne -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sy s -I/usr/src/sys/dev -I/usr/src/sys/../include -I/usr/src/sys/contrib/dev/a cpica/Subsystem/Include -D_KERNEL -include opt_global.h -elf -mpreferred- stack-boundary=2 /usr/src/sys/dev/pdq/if_fpa.c > /usr/src/sys/dev/pdq/if_fpa.c:141: syntax error before `config_id' > /usr/src/sys/dev/pdq/if_fpa.c:143: warning: function declaration isn't a prot otype > /usr/src/sys/dev/pdq/if_fpa.c: In function `pdq_pci_probe': > /usr/src/sys/dev/pdq/if_fpa.c:144: `device_id' undeclared (first use in this function) > /usr/src/sys/dev/pdq/if_fpa.c:144: (Each undeclared identifier is reported on ly once > /usr/src/sys/dev/pdq/if_fpa.c:144: for each function it appears in.) > /usr/src/sys/dev/pdq/if_fpa.c: At top level: > /usr/src/sys/dev/pdq/if_fpa.c:152: syntax error before `config_id' > /usr/src/sys/dev/pdq/if_fpa.c:154: warning: function declaration isn't a prot otype > /usr/src/sys/dev/pdq/if_fpa.c: In function `pdq_pci_attach': > /usr/src/sys/dev/pdq/if_fpa.c:159: `unit' undeclared (first use in this funct ion) > /usr/src/sys/dev/pdq/if_fpa.c:165: warning: implicit declaration of function `pci_conf_read' > /usr/src/sys/dev/pdq/if_fpa.c:165: `config_id' undeclared (first use in this function) > /usr/src/sys/dev/pdq/if_fpa.c:169: warning: implicit declaration of function `pci_conf_write' > /usr/src/sys/dev/pdq/if_fpa.c:176: warning: implicit declaration of function `pci_map_mem' > /usr/src/sys/dev/pdq/if_fpa.c:194: warning: implicit declaration of function `pci_map_int' > /usr/src/sys/dev/pdq/if_fpa.c: At top level: > /usr/src/sys/dev/pdq/if_fpa.c:210: variable `fpadevice' has initializer but i ncomplete type > /usr/src/sys/dev/pdq/if_fpa.c:211: warning: excess elements in struct initial izer > /usr/src/sys/dev/pdq/if_fpa.c:211: warning: (near initialization for `fpadevi ce') > /usr/src/sys/dev/pdq/if_fpa.c:212: warning: excess elements in struct initial izer > /usr/src/sys/dev/pdq/if_fpa.c:212: warning: (near initialization for `fpadevi ce') > /usr/src/sys/dev/pdq/if_fpa.c:213: warning: excess elements in struct initial izer > /usr/src/sys/dev/pdq/if_fpa.c:213: warning: (near initialization for `fpadevi ce') > /usr/src/sys/dev/pdq/if_fpa.c:214: warning: excess elements in struct initial izer > /usr/src/sys/dev/pdq/if_fpa.c:214: warning: (near initialization for `fpadevi ce') > /usr/src/sys/dev/pdq/if_fpa.c:216: warning: excess elements in struct initial izer > /usr/src/sys/dev/pdq/if_fpa.c:216: warning: (near initialization for `fpadevi ce') > /usr/src/sys/dev/pdq/if_fpa.c:218: warning: type defaults to `int' in declara tion of `COMPAT_PCI_DRIVER' > /usr/src/sys/dev/pdq/if_fpa.c:218: warning: parameter names (without types) i n function declaration > /usr/src/sys/dev/pdq/if_fpa.c:218: warning: data definition has no type or st orage class > /usr/src/sys/dev/pdq/if_fpa.c:210: warning: `fpadevice' defined but not used > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/GENERIC. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > > jim > -- > All opinions expressed are mine, if you | "I will not be pushed, stamped, > think otherwise, then go jump into turbid | briefed, debriefed, indexed, or > radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" > ----------------------------------------------------------------------------- - > kc5vdj@prodigy.net KC5VDJ - HF to 23cm KC5VDJ@NW0I.#NEKS.KS.USA.NOA M > HF/VHF: IC-706MkII VHF/UHF/SHF: IC-T81A KPC3+ & PK-232MBX Grid: EM28p x > ----------------------------------------------------------------------------- - > ET has one helluva sense of humor, always anal-probing right-wing schizos! > > > 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 Jan 2 1:59:58 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 01:59:56 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 8F66637B400 for ; Tue, 2 Jan 2001 01:59:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id QAA05390; Wed, 27 Dec 2000 16:04:37 GMT (envelope-from n_hibma@calcaphon.com) Date: Wed, 27 Dec 2000 16:04:37 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: janb@cs.utep.edu Cc: freebsd-current@freebsd.org Subject: Re: state of usb? 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 Could you send me the output of dmesg and the complaints usbd is producing? Nick On Tue, 21 Nov 2000 janb@cs.utep.edu wrote: > What is the current state of the usbd? I keep getting messages that > complain about a host controller error and a shutdown of the usb > interface. And I don't even have any devices on my usb ports... > > JAN > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 3:21: 0 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 03:20:58 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from popd.goldenlines.net.il (unknown [212.117.129.238]) by hub.freebsd.org (Postfix) with ESMTP id 23BC337B400 for ; Tue, 2 Jan 2001 03:20:58 -0800 (PST) Received: from egemin.be ([63.20.241.213]) by popd.goldenlines.net.il with SMTP id <20010102112020.IGSW9957.popd@egemin.be>; Tue, 2 Jan 2001 13:20:20 +0200 Message-Id: <003v0h5y.886f0e71jidoy@egemin.be> From: NewPager9@egemin.be To: Horne@buttler-mad.mad.servicom.es Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT Subject: Watch 100's of Channels on your New Free Satellite System! Date: Tue, 02 Jan 2001 06:20:48 -0500 Sender: NewPager9@eei.cz Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FREE Satellite T.V. System and FREE Installation For a limited time we'll give you this top of the line Digital Satellite System for FREE! We'll even include Free installation. Enjoy 100's of Channels of crystal clear digital picture and cd stereo sound on your FREE Satellite TV System. Why pay for these items in a retail store, when we're giving you the same satellite package for free. Call 888-514-6881 to be Guaranteed Your FREE Satellite Today This Innovative 20" Satellite includes a stereo receiver and an infrared remote. With this FREE offer you will have both Interactive Television Capability and an On Screen Program Guide. This limited time FREE offer is much less than the monthly cost of cable tv. All you have to do is call us to arrange delivery. If you call today, we'll throw in a second receiver for your second T.V. free. Call 888-514-6881 to Begin Surfing through 100's of Channels Today! To be removed send email to chillywus@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 Jan 2 6:24:35 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 06:24:33 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id C6A7C37B400 for ; Tue, 2 Jan 2001 06:24:32 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f02ENBx02918 for ; Tue, 2 Jan 2001 10:23:11 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Jan 2001 10:23:11 -0400 (AST) From: The Hermit Hacker To: Subject: System hangs with -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 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? Thanks ... 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 Tue Jan 2 6:36:58 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 06:36:57 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from tomts5-srv.bellnexxia.net (tomts5.bellnexxia.net [209.226.175.25]) by hub.freebsd.org (Postfix) with ESMTP id AD80337B400 for ; Tue, 2 Jan 2001 06:36:53 -0800 (PST) Received: from [64.230.32.214] by tomts5-srv.bellnexxia.net (InterMail vM.4.01.03.00 201-229-121) with SMTP id <20010102143652.UBJW14993.tomts5-srv.bellnexxia.net@[64.230.32.214]> for ; Tue, 2 Jan 2001 09:36:52 -0500 From: Robert Jackson To: current@freebsd.org Subject: Hey X-Mailer: Mail Bomber Reply-To: RobertJackson3@yahoo.com Date: Tue, 2 Jan 2001 09:36:51 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20010102143652.UBJW14993.tomts5-srv.bellnexxia.net@[64.230.32.214]> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey whats up- You gotta check out this www.Politicians Stink.com it's great. A couple of college kids set it up I think- If only CNN could write like that. Ne way give it a look- Cya around To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 7:32:38 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 07:32:35 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hotmail.com (oe66.law11.hotmail.com [64.4.16.201]) by hub.freebsd.org (Postfix) with ESMTP id 4C7C237B400 for ; Tue, 2 Jan 2001 07:32:35 -0800 (PST) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 2 Jan 2001 07:32:35 -0800 X-Originating-IP: [12.20.58.68] From: "none listed" To: Subject: Subscription Date: Tue, 2 Jan 2001 10:27:56 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000C_01C074A6.ABEB6DA0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Message-ID: X-OriginalArrivalTime: 02 Jan 2001 15:32:35.0043 (UTC) FILETIME=[3AD57B30:01C074D1] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000C_01C074A6.ABEB6DA0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello BSD gurus, Please subscribe me to what all newbies should know. I am currently = trying to learn UNIX in all of its flavors. I might be too ambitious, = but I'm too ignorant to the intracacies of UNIX to know better. I have = acces to Sun Solaris and HP UNIX, and I have successfully installed = both. However, I have found your site to be the most help/hope to my = self-led instruction. Thank you for access to your books and software. sincerely from a BSD novice in training ------=_NextPart_000_000C_01C074A6.ABEB6DA0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
    Hello BSD = gurus,
 
Please subscribe me to what all newbies = should=20 know.  I am currently trying to learn UNIX in all of its = flavors.  I=20 might be too ambitious, but I'm too ignorant to the intracacies of UNIX = to know=20 better.  I have acces to Sun Solaris and HP UNIX, and I have=20 successfully installed both.  However, I have found your site to be = the=20 most help/hope to my self-led instruction.  Thank you for access to = your=20 books and software.
    sincerely from a BSD = novice in=20 training
------=_NextPart_000_000C_01C074A6.ABEB6DA0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 9:10:12 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 09:10:10 2001 Return-Path: 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 942F637B400 for ; Tue, 2 Jan 2001 09:10:09 -0800 (PST) Received: from EnContacto.Net (localhost [127.0.0.1]) by casa.encontacto.net (8.11.1/8.11.1) with ESMTP id f02HA1u77201 for ; Tue, 2 Jan 2001 09:10:01 -0800 (PST) (envelope-from eculp@EnContacto.Net) Sender: root@casa.encontacto.net Message-ID: <3A520B68.8E137888@EnContacto.Net> Date: Tue, 02 Jan 2001 09:10:00 -0800 From: Charlie Root Organization: InternetSalon.Org/EnContacto.Net/CafeMania.Net X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORg Subject: Core dumps on Current Make World this morning Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All the machines that I have running Current dumped core at the same place this morning. ===> share/termcap ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > /dev/null Segmentation fault - core dumped *** Error code 139 Stop in /usr/src/share/termcap. *** Error code 1 For a couple of days now, I haven't been able to use vi because it also dumps core on all the machines except the only one that was able to build world and a new kernel yesterday, just good timing I guess. I haven't seen this on the list. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 9:15:46 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 09:15:44 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 872CC37B400 for ; Tue, 2 Jan 2001 09:15:43 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f02HEIV05056; Tue, 2 Jan 2001 13:14:18 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 2 Jan 2001 13:14:18 -0400 (AST) From: The Hermit Hacker To: Charlie Root Cc: Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <3A520B68.8E137888@EnContacto.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 do a 'make -k world' ... I had the same problem with vi, and the same SegFault ... by using -k, it bypasses the error, which allows it to get to the point that the newer vi is installed, which doesn't SegFault ... On Tue, 2 Jan 2001, Charlie Root wrote: > All the machines that I have running Current dumped core at the same > place this morning. > > ===> share/termcap > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > > /dev/null > Segmentation fault - core dumped > *** Error code 139 > > Stop in /usr/src/share/termcap. > *** Error code 1 > > For a couple of days now, I haven't been able to use vi because it also > dumps core on all the machines except the only one that was able to > build world and a new kernel yesterday, just good timing I guess. I > haven't seen this on the list. > > Thanks, > > ed > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > 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 Tue Jan 2 10: 3: 2 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 10:02:59 2001 Return-Path: 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 5702737B400 for ; Tue, 2 Jan 2001 10:02:59 -0800 (PST) Received: from MexComUSA.Net (localhost [127.0.0.1]) by dsl.MexComUSA.net (8.11.1/8.11.1) with ESMTP id f02HwMF77035; Tue, 2 Jan 2001 09:58:23 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Sender: eculp@dsl.MexComUSA.net Message-ID: <3A5216BD.15D23E65@MexComUSA.Net> Date: Tue, 02 Jan 2001 09:58:22 -0800 From: Edwin Culp Organization: CafeMania.net/EnContacto.Net/InternetSalon.Org X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker Cc: current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > do a 'make -k world' ... I had the same problem with vi, and the same > SegFault ... by using -k, it bypasses the error, which allows it to get to > the point that the newer vi is installed, which doesn't SegFault ... Thanks, I just started them all up with -k . I didn't even think of that. Thanks again, ed > > > On Tue, 2 Jan 2001, Charlie Root wrote: > > > All the machines that I have running Current dumped core at the same > > place this morning. > > > > ===> share/termcap > > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > > > /dev/null > > Segmentation fault - core dumped > > *** Error code 139 > > > > Stop in /usr/src/share/termcap. > > *** Error code 1 > > > > For a couple of days now, I haven't been able to use vi because it also > > dumps core on all the machines except the only one that was able to > > build world and a new kernel yesterday, just good timing I guess. I > > haven't seen this on the list. > > > > Thanks, > > > > ed > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 10: 6: 6 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 10:06:03 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7493037B400 for ; Tue, 2 Jan 2001 10:05: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 KAA21731; Tue, 2 Jan 2001 10:05:53 -0800 Date: Tue, 2 Jan 2001 10:05:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Charlie Root Cc: current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <3A520B68.8E137888@EnContacto.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 Same with me. > All the machines that I have running Current dumped core at the same > place this morning. > > ===> share/termcap > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > > /dev/null > Segmentation fault - core dumped > *** Error code 139 > > Stop in /usr/src/share/termcap. > *** Error code 1 > > For a couple of days now, I haven't been able to use vi because it also > dumps core on all the machines except the only one that was able to > build world and a new kernel yesterday, just good timing I guess. I > haven't seen this on the list. > > Thanks, > > ed > > > > 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 Tue Jan 2 10: 7:12 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 10:07:08 2001 Return-Path: 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 7F07B37B402 for ; Tue, 2 Jan 2001 10:07:08 -0800 (PST) Received: from MexComUSA.Net (localhost [127.0.0.1]) by dsl.MexComUSA.net (8.11.1/8.11.1) with ESMTP id f02I2LF79415; Tue, 2 Jan 2001 10:02:21 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Sender: eculp@dsl.MexComUSA.net Message-ID: <3A5217AC.C43C06F@MexComUSA.Net> Date: Tue, 02 Jan 2001 10:02:21 -0800 From: Edwin Culp Organization: CafeMania.net/EnContacto.Net/InternetSalon.Org X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mark Hittinger Cc: Szilveszter Adam , current@FreeBSD.ORG Subject: Re: Current stalls...(now also panic) References: <200012292333.RAA09579@freebsd.netcom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark, Thanks a lot. I read Marc's mail first so I'm trying the -k solution first but I will also take USB support out of the kernels that have it. Thanks, ed Mark Hittinger wrote: > > Maybe this is related, maybe not... I upgraded to the latest CURRENT > > available this morning and now I also see occasional (albeit short) hangs > > sometimes, although the machine seems to be responsive otherwise. > > I see this also. If you aren't using USB but have it compiled into your > kernel try commenting out all the "device" entries after "# USB support" > in the config file. A kernel built without USB may not show the hangs. > > I think there is a buglet that has krept into the USB code within the > last couple of weeks. > > Later > > Mark Hittinger > Earthlink > bugs@freebsd.netcom.com > > 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 Tue Jan 2 10:16:21 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 10:16:18 2001 Return-Path: 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 8277337B400 for ; Tue, 2 Jan 2001 10:16:17 -0800 (PST) Received: from MexComUSA.Net (localhost [127.0.0.1]) by dsl.MexComUSA.net (8.11.1/8.11.1) with ESMTP id f02IBsF82885; Tue, 2 Jan 2001 10:11:54 -0800 (PST) (envelope-from eculp@MexComUSA.Net) Sender: eculp@dsl.MexComUSA.net Message-ID: <3A5219EA.308EFD02@MexComUSA.Net> Date: Tue, 02 Jan 2001 10:11:54 -0800 From: Edwin Culp Organization: CafeMania.net/EnContacto.Net/InternetSalon.Org X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Szilveszter Adam Cc: current@FreeBSD.ORG Subject: Re: Current stalls...(now also panic) References: <13929.978110736@critter> <20001229225710.A25801@petra.hos.u-szeged.hu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Szilveszter, I've got some other weird problems with cores and panics but vi is the only one that I can define well enough. I'm also taking all USB support from the kernels that have it to see if my other strange problems disappear like access to mysql databases with php4 cvs and some strange library problems that I am having with my new XFree4.0.2_3 with kde-2.0.1 and LinuxNetscape that I just installed on Dec. 31. (Poor timing, but sorting these things out is what makes life interesting :-) Thanks, ed Szilveszter Adam wrote: > Hi! > > Maybe this is related, maybe not... I upgraded to the latest CURRENT > available this morning and now I also see occasional (albeit short) hangs > sometimes, although the machine seems to be responsive otherwise. > > But, not only that, I also got a cool panic while trying to do some stuff > (like compiling the docs) and pressing Ctrl-Z in another tty. No X, no > nothing. I was dropped into the debugger, but since I am not a ddb artist, > I tried to avoid to type the whole trace by hand and in the process managed > to reboot the box... oh well. Next time I will know. > > But, the panic message was this: > > panic: blockable mtx_enter() of lockmgr interlock when not legal @ > ../../kern/kern_lock.c:247 > > Maybe this rings a bell with someone. The error was appearently caught by > WITNESS, which I also have enabled in my kernel (albeit without > MUTEX_DEBUG, because *that* really made it impossible to do anything > sensible on the machine...) > > Hardware-wise, nothing fancy here... UP PII-233, 128M non-ECC RAM, all-IDE, > two disks, one CD-ROM. Next time, I promise to write down all the > details... but just wanted to chime in quickly since this might be related > to the hangs other people are seeing, but maybe they don't panic() because > they don't have WITNESS enabled (just speculating) > > -- > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 11:36:28 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 11:36:25 2001 Return-Path: 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 37DB537B400 for ; Tue, 2 Jan 2001 11:36:25 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f02JZuG01048; Tue, 2 Jan 2001 11:35:57 -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: Tue, 02 Jan 2001 11:36:20 -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 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 Tue Jan 2 11:47:12 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 11:47:09 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cmr2.ash.ops.us.uu.net (cmr2.ash.ops.us.uu.net [198.5.241.40]) by hub.freebsd.org (Postfix) with ESMTP id 7327D37B400 for ; Tue, 2 Jan 2001 11:47:09 -0800 (PST) Received: from imr0.ash.ops.us.uu.net by cmr2.ash.ops.us.uu.net with ESMTP (peer crosschecked as: imr0.ash.ops.us.uu.net [153.39.43.11]) id QQjwgt16978; Tue, 2 Jan 2001 19:47:05 GMT Received: from sysenglt112 by imr0.ash.ops.us.uu.net with SMTP (peer crosschecked as: ippool144-215.corp.us.uu.net [153.39.144.215]) id QQjwgs27166; Tue, 2 Jan 2001 19:44:19 GMT Reply-To: From: "Raymond Hicks" To: , "'Charlie Root'" Cc: Subject: RE: Core dumps on Current Make World this morning Date: Tue, 2 Jan 2001 14:48:02 -0500 Message-ID: <002901c074f4$eb47b000$d7902799@sysenglt112> 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 8.5, Build 4.71.2173.0 Importance: Normal X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG same here as well... i did a make -k buildworld and that worked for me/.. -----Original Message----- From: owner-freebsd-current@FreeBSD.ORG [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Matthew Jacob Sent: Tuesday, January 02, 2001 1:06 PM To: Charlie Root Cc: current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning Same with me. > All the machines that I have running Current dumped core at the same > place this morning. > > ===> share/termcap > ex - /usr/src/share/termcap/termcap.src < /usr/src/share/termcap/reorder > > /dev/null > Segmentation fault - core dumped > *** Error code 139 > > Stop in /usr/src/share/termcap. > *** Error code 1 > > For a couple of days now, I haven't been able to use vi because it also > dumps core on all the machines except the only one that was able to > build world and a new kernel yesterday, just good timing I guess. I > haven't seen this on the list. > > Thanks, > > ed > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 12:36: 4 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 12:36:01 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from math.uic.edu (seifert.math.uic.edu [131.193.178.249]) by hub.freebsd.org (Postfix) with SMTP id 8363337B400 for ; Tue, 2 Jan 2001 12:36:01 -0800 (PST) Received: (qmail 69247 invoked by uid 30007); 2 Jan 2001 20:34:24 -0000 Date: Tue, 2 Jan 2001 14:34:24 -0600 From: Marc Culler To: dfr@nlsystems.com, mike@smith.net.au, paulz@trantor.stuyts.nl, current@freebsd.org Cc: consult@math.uic.edu Subject: Weird NFS error using Solaris 8 client Message-ID: <20010102143424.A69160@math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In December 1998 a message from Paul van der Zwan with a similar subject ( http://lists.openresources.com/FreeBSD/freebsd-current/msg00018.html ) started a thread dealing with a problem of bad timestamps for NFS files. By the end of the thread Doug Rabson had apparently solved the problem for FreeBSD NFS clients and a Solaris 7 NFS server. Unfortunately, the problem does not seem to have been solved yet for a FreeBSD NFS server with Solaris 8 NFS clients. Our FreeBSD NFS server is running 4.1.1-stable. Our Solaris clients are running Solaris 5.8. I can produce our problem with the same test program that was used in that message from 1998: #include main() { int rv; rv=open("testfile1",O_CREAT|O_RDWR|O_EXCL,0666); if ( rv < 0 ) perror("testfile1"); rv=open("testfile2",O_CREAT|O_RDWR,0666); if ( rv < 0 ) perror("testfile2"); } When I run the above program on a FreeBSD client using a FreeBSD NFS server there are no errors reported. I can list the files: [culler@seifert culler]$ ls -l testfile* -rw------- 1 culler 30007 0 Jan 2 14:07 testfile1 -rw------- 1 culler 30007 0 Jan 2 14:07 testfile2 But, if I now login to a Solaris 8 client which is using the same FreeBSD NFS server I am not able to stat testfile1: [culler@neumann culler]$ ls -l testfile* ls: testfile1: Value too large for defined data type -rw------- 1 culler 30007 0 Jan 2 14:07 testfile2 If I go back to the FreeBSD client and touch testfile1, the error disappears: [culler@seifert culler]$ touch testfile1 [culler@neumann culler]$ ls -l testfile1 -rw------- 1 culler 30007 0 Jan 2 14:11 testfile1 I presume that the problem still has to do with bad timestamps, but under some slightly different situation than in December 1998. Can anyone help us? Sadly, pine seems to trigger this bug, so we are getting a fair number of these bad files. Thanks. Marc Culler Department of Mathematics University of Illinois at Chicago PS Here are the revision numbers for nfs_vnops.c and nfs_vfsops.c on our FreeBSD test machines. FreeBSD client: $FreeBSD: src/sys/nfs/nfs_vnops.c,v 1.150 2000/01/05 00:32:18 dillon Exp $ $FreeBSD: src/sys/nfs/nfs_vfsops.c,v 1.91 2000/01/05 05:11:37 dillon Exp $ FreeBSD server: $FreeBSD: src/sys/nfs/nfs_vnops.c,v 1.150 2000/01/05 00:32:18 dillon Exp $ $FreeBSD: src/sys/nfs/nfs_vfsops.c,v 1.91.2.1 2000/09/10 01:45:36 ps Exp $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 12:38:48 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 12:38:46 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3807E37B402 for ; Tue, 2 Jan 2001 12:38:45 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id f02Kchs94683; Tue, 2 Jan 2001 13:38:43 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA31734; Tue, 2 Jan 2001 13:38:42 -0700 (MST) Message-Id: <200101022038.NAA31734@harmony.village.org> To: mjacob@feral.com Subject: Re: Core dumps on Current Make World this morning Cc: Charlie Root , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 02 Jan 2001 10:05:51 PST." References: Date: Tue, 02 Jan 2001 13:38:42 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Matthew Jacob writes: : Same with me. This sounds like a job for Captain UPDATING: 20010101: ex and vi were broken by some changes to sys/queue.h. If you have a bad vi (and are getting core dumps when building termcap), you can work around this problem by adding -k to your command line. This will cause the build to complete and install a new vi. Once that's done, you can rebuild again without the -k to pick up anything that might have been ignored by the -k option. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 12:40:44 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 12:40:43 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7F2D237B400 for ; Tue, 2 Jan 2001 12:40:42 -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 MAA22300; Tue, 2 Jan 2001 12:40:36 -0800 Date: Tue, 2 Jan 2001 12:40:35 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Charlie Root , current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <200101022038.NAA31734@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 Ta-da! > In message Matthew Jacob writes: > : Same with me. > > This sounds like a job for Captain UPDATING: > > 20010101: > ex and vi were broken by some changes to sys/queue.h. If > you have a bad vi (and are getting core dumps when building > termcap), you can work around this problem by adding -k to > your command line. This will cause the build to complete > and install a new vi. Once that's done, you can rebuild again > without the -k to pick up anything that might have been > ignored by the -k option. > > > 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 Tue Jan 2 12:57: 4 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 12:57:01 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hkabc.com (ngw-gw.hkabc.com [202.73.255.5]) by hub.freebsd.org (Postfix) with SMTP id 90D6137B400 for ; Tue, 2 Jan 2001 12:57:00 -0800 (PST) Received: by hkabc.com with Novell_GroupWise; Wed, 03 Jan 2001 01:06:48 +0800 Received: from VAIO_[63.232.160.107] ([63.232.160.107]) by hkabc.com (GroupWise SMTP/MIME daemon 4.1 v3) ; Wed, 3 Jan 01 01:06:33 Received: from by VAIO with ESMTP; Tue, 02 Jan 2001 10:07:01 -0700 To: From: moreleads@uswest.net Subject: How do you create your leads? 15344 Date: Tue, 02 Jan 2001 10:06:52 -0700 MIME-Version: 1.0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal Message-Id: <20010102205700.90D6137B400@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Email Letter

Reach Millions W= ith Your Product or Service!

We are a professional commercial e-m= ail service that has been in business for over 6 years. We can help you reach more p= otential customers through e-mail. No doubt you've heard every horror story about= UCE, but frankly it's not true. There is a very small element that does not w= ant the Internet to be used for commercial purposes, but isn't that what the= Internet really is? And it completely legal to send commercial e-mail.

There is Target and Bulk Email. We c= an send either for you! We've mailed for hundreds of For= tune 500 companies over the last 6 years, and many of them you would recog= nize.

Here are some of the advantages:

  • No Printing Cost! No Handling (s= tuffing envelops)!
  • No Postage!
  • Cost Effective Too!
  • We do all the mailing, you have = no hassle!

We will assist you in the preparatio= n of your e-mail letter! We provide you with "FREE" voice mail! Results!!! Ask us = for our Special Introduction Price when you phone. We will show you that e-m= ailing works!

For complete det= ails, phone (877) 203-3700 ext. 150

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:17:49 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:17:47 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 72D8337B698 for ; Tue, 2 Jan 2001 14:17:47 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f02MHfX57879; Tue, 2 Jan 2001 14:17:41 -0800 (PST) (envelope-from dillon) Date: Tue, 2 Jan 2001 14:17:41 -0800 (PST) From: Matt Dillon Message-Id: <200101022217.f02MHfX57879@earth.backplane.com> To: Matthew Jacob Cc: Warner Losh , Charlie Root , current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Ta-da! : : :> In message Matthew Jacob writes: :> : Same with me. :> :> This sounds like a job for Captain UPDATING: :> :> 20010101: :> ex and vi were broken by some changes to sys/queue.h. If :> you have a bad vi (and are getting core dumps when building :> termcap), you can work around this problem by adding -k to :> your command line. This will cause the build to complete :> and install a new vi. Once that's done, you can rebuild again :> without the -k to pick up anything that might have been :> ignored by the -k option. Why in (insert favorite deity)'s name does ex and vi depend on sys/queue.h ? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:22:58 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:22:55 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 32F3A37B400 for ; Tue, 2 Jan 2001 14:22:55 -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 OAA22668; Tue, 2 Jan 2001 14:19:44 -0800 Date: Tue, 2 Jan 2001 14:19:43 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matt Dillon Cc: Warner Losh , Charlie Root , current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <200101022217.f02MHfX57879@earth.backplane.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 > > Why in (insert favorite deity)'s name does ex and vi depend on > sys/queue.h ? Oh, christ, who knows? I just saw the new David Mamet film "State && Main"... in one scene, Alec Baldwin has just crashed a stationwagon and flipped it, wiping out the only stoplight in this town..... he crawls out of the wreckage, lounges against the car and says, "Well... that happened....." Thie sys/queue.h is probably of the same order. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:23:18 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:23:17 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 2A3DE37B402 for ; Tue, 2 Jan 2001 14:23:16 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id f02MNEs95042; Tue, 2 Jan 2001 15:23:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA32566; Tue, 2 Jan 2001 15:23:14 -0700 (MST) Message-Id: <200101022223.PAA32566@harmony.village.org> To: Matt Dillon Subject: Re: Core dumps on Current Make World this morning Cc: Matthew Jacob , Charlie Root , current@FreeBSD.ORG In-reply-to: Your message of "Tue, 02 Jan 2001 14:17:41 PST." <200101022217.f02MHfX57879@earth.backplane.com> References: <200101022217.f02MHfX57879@earth.backplane.com> Date: Tue, 02 Jan 2001 15:23:14 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101022217.f02MHfX57879@earth.backplane.com> Matt Dillon writes: : Why in (insert favorite deity)'s name does ex and vi depend on : sys/queue.h ? Because it does. :-) Lots of places in the userland tree use it. phk committed a fix to vi that broke vi, and that's the problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:28: 6 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:28:03 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 9E18637B400 for ; Tue, 2 Jan 2001 14:28:02 -0800 (PST) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA33755; Tue, 2 Jan 2001 14:27:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200101022227.OAA33755@gndrsh.dnsmgr.net> Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <200101022038.NAA31734@harmony.village.org> from Warner Losh at "Jan 2, 2001 01:38:42 pm" To: imp@bsdimp.com (Warner Losh) Date: Tue, 2 Jan 2001 14:27:28 -0800 (PST) Cc: mjacob@feral.com, eculp@EnContacto.Net (Charlie Root), 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 message Matthew Jacob writes: > : Same with me. > > This sounds like a job for Captain UPDATING: Don't you just need to rebuild vi/ex? Ie would not: cd /usr/src/usr.bin/vi; make cleandir && make obj && make depend && make all install fix the problem? Two buildworlds seems like a big sledgehammer when a small tap with a 2oz would do :-) > 20010101: > ex and vi were broken by some changes to sys/queue.h. If > you have a bad vi (and are getting core dumps when building > termcap), you can work around this problem by adding -k to > your command line. This will cause the build to complete > and install a new vi. Once that's done, you can rebuild again > without the -k to pick up anything that might have been > ignored by the -k option. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:28:11 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:28:04 2001 Return-Path: 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 09D6837B402 for ; Tue, 2 Jan 2001 14:28:04 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f02MRkq53305; Tue, 2 Jan 2001 23:27:46 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Matt Dillon Cc: Matthew Jacob , Warner Losh , Charlie Root , current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: Your message of "Tue, 02 Jan 2001 14:17:41 PST." <200101022217.f02MHfX57879@earth.backplane.com> Date: Tue, 02 Jan 2001 23:27:46 +0100 Message-ID: <53303.978474466@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101022217.f02MHfX57879@earth.backplane.com>, Matt Dillon writes: > >:Ta-da! >: >: >:> In message Matthew Jacob writes: >:> : Same with me. >:> >:> This sounds like a job for Captain UPDATING: >:> >:> 20010101: >:> ex and vi were broken by some changes to sys/queue.h. If >:> you have a bad vi (and are getting core dumps when building >:> termcap), you can work around this problem by adding -k to >:> your command line. This will cause the build to complete >:> and install a new vi. Once that's done, you can rebuild again >:> without the -k to pick up anything that might have been >:> ignored by the -k option. > > Why in (insert favorite deity)'s name does ex and vi depend on > sys/queue.h ? Actually they don't, they depend on db1.85's "mpool" which depends on since it lives in libc. vi/ex comes with their own copy of -- 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 Jan 2 14:29:15 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:29:14 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3EA7B37B400 for ; Tue, 2 Jan 2001 14:29:13 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id f02MTBs95084; Tue, 2 Jan 2001 15:29:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA32640; Tue, 2 Jan 2001 15:29:11 -0700 (MST) Message-Id: <200101022229.PAA32640@harmony.village.org> To: "Rodney W. Grimes" Subject: Re: Core dumps on Current Make World this morning Cc: mjacob@feral.com, eculp@EnContacto.Net (Charlie Root), current@FreeBSD.ORG In-reply-to: Your message of "Tue, 02 Jan 2001 14:27:28 PST." <200101022227.OAA33755@gndrsh.dnsmgr.net> References: <200101022227.OAA33755@gndrsh.dnsmgr.net> Date: Tue, 02 Jan 2001 15:29:11 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101022227.OAA33755@gndrsh.dnsmgr.net> "Rodney W. Grimes" writes: : > This sounds like a job for Captain UPDATING: : : Don't you just need to rebuild vi/ex? Ie would not: : cd /usr/src/usr.bin/vi; : make cleandir && make obj && make depend && make all install : fix the problem? : : Two buildworlds seems like a big sledgehammer when a small tap with : a 2oz would do :-) If someone with a bad vi tries this and it works, I'll change it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 14:29:27 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:29:25 2001 Return-Path: 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 2928F37B404 for ; Tue, 2 Jan 2001 14:29:24 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id f02MT9q53362; Tue, 2 Jan 2001 23:29:09 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Rodney W. Grimes" Cc: imp@bsdimp.com (Warner Losh), mjacob@feral.com, eculp@EnContacto.Net (Charlie Root), current@FreeBSD.ORG Subject: Re: Core dumps on Current Make World this morning In-Reply-To: Your message of "Tue, 02 Jan 2001 14:27:28 PST." <200101022227.OAA33755@gndrsh.dnsmgr.net> Date: Tue, 02 Jan 2001 23:29:09 +0100 Message-ID: <53360.978474549@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200101022227.OAA33755@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes : >> In message Matthew Jacob writes: >> : Same with me. >> >> This sounds like a job for Captain UPDATING: > >Don't you just need to rebuild vi/ex? Ie would not: > cd /usr/src/usr.bin/vi; > make cleandir && make obj && make depend && make all install > >fix the problem? > >Two buildworlds seems like a big sledgehammer when a small tap with >a 2oz would do :-) It's actually libc you need to reinstall (unless your vi/ex is statically linked). -- 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 Jan 2 14:35: 7 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 14:35:05 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D343637B400 for ; Tue, 2 Jan 2001 14:35:04 -0800 (PST) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA33788; Tue, 2 Jan 2001 14:32:47 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200101022232.OAA33788@gndrsh.dnsmgr.net> Subject: Re: Core dumps on Current Make World this morning In-Reply-To: <53360.978474549@critter> from Poul-Henning Kamp at "Jan 2, 2001 11:29:09 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Tue, 2 Jan 2001 14:32:46 -0800 (PST) Cc: imp@bsdimp.com (Warner Losh), mjacob@feral.com, eculp@EnContacto.Net (Charlie Root), 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 message <200101022227.OAA33755@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes > : > >> In message Matthew Jacob writes: > >> : Same with me. > >> > >> This sounds like a job for Captain UPDATING: > > > >Don't you just need to rebuild vi/ex? Ie would not: > > cd /usr/src/usr.bin/vi; > > make cleandir && make obj && make depend && make all install > > > >fix the problem? > > > >Two buildworlds seems like a big sledgehammer when a small tap with > >a 2oz would do :-) > > It's actually libc you need to reinstall (unless your vi/ex is > statically linked). Okay... cd /usr/src/lib/libc; make cleandir && make obj && make depend && make all install -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 17:42:31 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 17:42:24 2001 Return-Path: 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 AFCAD37B404 for ; Tue, 2 Jan 2001 17:42:24 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f031g4G09212 for ; Tue, 2 Jan 2001 17:42: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 Resent-Date: Tue, 2 Jan 2001 17:25:26 -0800 (PST) Resent-Message-Id: <200101030125.f031PQg41496@freefall.freebsd.org> Resent-From: John Baldwin Resent-To: cvs-committers@FreeBSD.org Date: Tue, 02 Jan 2001 17:42:31 -0800 (PST) From: John Baldwin To: current@FreeBSD.org Subject: HEADS UP: hw.sndunit -> hw.snd.unit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A heads up to everyone who has hw.sndunit set to something in /etc/sysctl.conf, it is now hw.snd.unit. -----FW: <200101030125.f031PQg41496@freefall.freebsd.org>----- jhb 2001/01/02 17:25:26 PST Modified files: sys/dev/sound/pcm sound.c sound.h Log: Create a new sysctl node 'hw.snd' and move 'hw.sndunit' to 'hw.snd.unit'. Reviewed by: cg --------------End of forwarded message------------------------- -- 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 Tue Jan 2 20:49:11 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 20:49:07 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 28C9637B400; Tue, 2 Jan 2001 20:49:07 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id f034n4b00287; Tue, 2 Jan 2001 20:49:05 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010102204401.00b13e88@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Tue, 02 Jan 2001 20:49:04 -0800 To: smp@freebsd.org From: Manfred Antar Subject: Fatal trap while printing under SMP Cc: 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 When trying to print using a current SMP kernel, I get the following: Fatal trap 12: page fault while in kernel mode cpuid = 1; lapic.id = 0c000000 fault virtual address = 0xe1810412 fault code = supervisor write, page not present instruction pointer = 0x8:0xcb0a7977 stack pointer = 0x10:0xcb08cf84 frame pointer = 0x10:0xcb08cf9c 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 = 30652 (irq7: lpt0) trap number = 12 panic: page fault cpuid = 1; lapic.id = 0c000000 boot() called on cpu#1 syncing disks... Printing works fine with a current non SMP kernel. 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 Tue Jan 2 21: 5: 9 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 21:05:05 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id D1AC137B400; Tue, 2 Jan 2001 21:05:04 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id D68656A90D; Wed, 3 Jan 2001 15:34:59 +1030 (CST) Date: Wed, 3 Jan 2001 15:34:59 +1030 From: Greg Lehey To: Manfred Antar Cc: smp@freebsd.org, current@freebsd.org Subject: Re: Fatal trap while printing under SMP Message-ID: <20010103153459.J4336@wantadilla.lemis.com> References: <5.0.2.1.2.20010102204401.00b13e88@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <5.0.2.1.2.20010102204401.00b13e88@pozo.com>; from null@pozo.com on Tue, Jan 02, 2001 at 08:49:04PM -0800 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 2 January 2001 at 20:49:04 -0800, Manfred Antar wrote: > When trying to print using a current SMP kernel, I get the following: > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; lapic.id = 0c000000 > fault virtual address = 0xe1810412 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xcb0a7977 > stack pointer = 0x10:0xcb08cf84 > frame pointer = 0x10:0xcb08cf9c > 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 = 30652 (irq7: lpt0) > trap number = 12 > panic: page fault > cpuid = 1; lapic.id = 0c000000 > boot() called on cpu#1 We really need more information than this. Can you get a dump, or at least a stack trace? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 21:37:17 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 21:37:13 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from lolita.speakeasy.net (lolita.speakeasy.net [216.254.0.13]) by hub.freebsd.org (Postfix) with SMTP id F174537B402 for ; Tue, 2 Jan 2001 21:37:12 -0800 (PST) Received: (qmail 5211 invoked from network); 3 Jan 2001 05:30:25 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 3 Jan 2001 05:30:25 -0000 Received: (qmail 31438 invoked from network); 3 Jan 2001 05:37:08 -0000 Received: from unknown (HELO celebris.tddhome) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 3 Jan 2001 05:37:08 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.1/8.11.1) id f035b6u18627; Tue, 2 Jan 2001 21:37:06 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Tue, 2 Jan 2001 21:37:06 -0800 (PST) Message-Id: <200101030537.f035b6u18627@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: grog@lemis.com Cc: null@pozo.com, smp@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <20010103153459.J4336@wantadilla.lemis.com> (message from Greg Lehey on Wed, 3 Jan 2001 15:34:59 +1030) Subject: Re: Fatal trap while printing under SMP References: <5.0.2.1.2.20010102204401.00b13e88@pozo.com> <20010103153459.J4336@wantadilla.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is what I saw on 12/24. This is with DDB and KTRACE. I added options WITNESS options INVARIANT_SUPPORT options INVARIANTS but gained no futher information. Fatal Trap 12: page fault while in kernel mode cpuid=0; lapic.id=00000000 fault virtual address = 0x18c7a2bb fault code = 0x8:0xc6bb0ca0 stack pointer = 0x10:0xc7aa1f84 frame pointer = 0x10:0xc7aa1f9c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor flags = interrupt enabled, resume, IOPL=0 current process = 416 (irq7, lpt0) kernel: type 12 trap, code=0 cpu0 stopping CPUs: 0x00000002... stopped stopped at 0xc6bb0ca0: movb 0x18c7a22b, %al db> trace _end(0) at 0xc6bb0ca0 fork_trampoline() at fork_trampoline+0x45 tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 2 22:11:39 2001 From owner-freebsd-current@FreeBSD.ORG Tue Jan 2 22:11:37 2001 Return-Path: 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 7490237B400 for ; Tue, 2 Jan 2001 22:11:32 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id f036BPV11918 for freebsd-current@freebsd.org; Wed, 3 Jan 2001 08:11:25 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200101030611.f036BPV11918@zibbi.icomtek.csir.co.za> Subject: unexpected vn driver lock: To: freebsd-current@freebsd.org Date: Wed, 3 Jan 2001 08:11:25 +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: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I see these messages regularly when building releases on my SMP current box. It happens during the part where the floppies are built. It does not break the build process and the machine does not panic, so it isn't a big problem for me. Maybe it rings a bell for someone. This is with a kernel built yesterday, but it also happened with a kernel built on Dec 21. ################# unexpected vn driver lock: 0xc9494d00: type VREG, usecount 2, writecount 1, refcount 541, flags (VOBJBUF) tag VT_UFS, ino 403493, on dev #da/20 (13, 20) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc9494d00: type VREG, usecount 2, writecount 1, refcount 322, flags (VOBJBUF) tag VT_UFS, ino 403493, on dev #da/20 (13, 20) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc9580f00: type VREG, usecount 2, writecount 1, refcount 361, flags (VOBJBUF) tag VT_UFS, ino 382428, on dev #da/20 (13, 20) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc90c4d00: type VREG, usecount 2, writecount 1, refcount 541, flags (VOBJBUF) tag VT_UFS, ino 404067, on dev #da/20 (13, 20) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc90c4d00: type VREG, usecount 2, writecount 1, refcount 181, flags (VOBJBUF) tag VT_UFS, ino 404079, on dev #da/20 (13, 20) lock type inode: EXCL (count 1) by pid 76048 ################## 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 Jan 3 7: 8:48 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 07:08:47 2001 Return-Path: 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 16F0737B402 for ; Wed, 3 Jan 2001 07:08:46 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id QAA02847; Wed, 3 Jan 2001 16:08:38 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 14DpWo-0002ok-00; Wed, 03 Jan 2001 16:08:38 +0100 Date: Wed, 3 Jan 2001 16:08:38 +0100 From: Szilveszter Adam To: freebsd-current@freebsd.org Cc: imp@village.org Subject: workaround for ex breakage works Message-ID: <20010103160838.A10349@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , freebsd-current@freebsd.org, imp@village.org 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 Hello Warner, Hello everybody, If you are looking for confirmation that the workaround for the ex/libc related world breakage works then here it is: I have just finished upgrading this way and did not have any problems. Actually, there is an even simpler way: If you already have started a buildworld and it has crashed on you then you alrady have libc built under /usr/obj. So you can just install that, (of course carefully) and than restart the buildworld with -DNOCLEAN. Will work from that point on. (Ripped from the underground bestseller: "Forbidden & Obscure ways of upgrading a FreeBSD system. Don't show this to a committer!") BTW: When the buildworld crashed, the console was left all hosed. Only grabage characters were generated, somehow even a break signal was sent (it surely wasn't me) so it dumped into DDB, but I could not do anything there either... weird. But maybe just coincidence. -- 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 Wed Jan 3 8:54:35 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 08:54:30 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id D8DB637B402 for ; Wed, 3 Jan 2001 08:54:29 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14DrBD-0002dV-00 for ; Wed, 03 Jan 2001 17:54:27 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14DrBC-0005xK-00 for ; Wed, 03 Jan 2001 17:54:26 +0100 Date: Wed, 3 Jan 2001 17:54:26 +0100 From: Nicolas Souchu To: freebsd-current@freebsd.org Subject: missing THREAD_UNLOCK in libc? Message-ID: <20010103175425.A22841@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have some troubleshootings with -current. A program that previously worked (-current of November) with -pthread now fails with an abort and a " in free(): error: recursive call" warning. I think that there may be some errors in my program and I'd like to know what was recently modified in libc or libc_r in order to track them down. While looking at the source of the warning in free(), I noticed that a THREAD_UNLOCK() may be missing in the case of a recursive call... Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 8:59:59 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 08:59:58 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (poynting.physics.purdue.edu [128.210.146.58]) by hub.freebsd.org (Postfix) with ESMTP id 0AFA637B400 for ; Wed, 3 Jan 2001 08:59:58 -0800 (PST) Received: from argon.firepipe.net (pm007-022.dialup.bignet.net [64.79.81.54]) by puck.firepipe.net (Postfix) with ESMTP id 3ED251982; Wed, 3 Jan 2001 11:59:57 -0500 (EST) Received: by argon.firepipe.net (Postfix, from userid 1000) id 5CB6519E0; Wed, 3 Jan 2001 11:59:46 -0500 (EST) Date: Wed, 3 Jan 2001 11:59:46 -0500 From: Will Andrews To: Nicolas Souchu Cc: freebsd-current@FreeBSD.ORG Subject: Re: missing THREAD_UNLOCK in libc? Message-ID: <20010103115945.K86630@argon.firepipe.net> Reply-To: Will Andrews References: <20010103175425.A22841@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103175425.A22841@wiliam.alcove-int>; from nsouch@alcove.fr on Wed, Jan 03, 2001 at 05:54:26PM +0100 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: will@argon.firepipe.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote: > A program that previously worked (-current of November) with -pthread now > fails with an abort and a " in free(): error: recursive call" warning. FWIW, WindowMaker 0.62.1 also crashes like this ocassionally (usually when I open a new aterm, at random intervals) on my 5.0-CURRENT laptop (-current as of Dec 14 or something). -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 10: 0:28 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 10:00:25 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8E4AA37B400 for ; Wed, 3 Jan 2001 10:00:25 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89197; Wed, 3 Jan 2001 10:00:24 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03I0MF61723; Wed, 3 Jan 2001 10:00:22 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:00:22 -0800 From: "David O'Brien" To: Nicolas Souchu Cc: freebsd-current@freebsd.org Subject: Re: missing THREAD_UNLOCK in libc? Message-ID: <20010103100022.A61682@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010103175425.A22841@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103175425.A22841@wiliam.alcove-int>; from nsouch@alcove.fr on Wed, Jan 03, 2001 at 05:54:26PM +0100 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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote: > A program that previously worked (-current of November) with -pthread now > fails with an abort and a " in free(): error: recursive call" warning. I need a copy of this program (source form) to test with. -- -- 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 Wed Jan 3 10:18:52 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 10:18:50 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from lolita.speakeasy.net (lolita.speakeasy.net [216.254.0.13]) by hub.freebsd.org (Postfix) with SMTP id 7EB3437B400 for ; Wed, 3 Jan 2001 10:18:49 -0800 (PST) Received: (qmail 3986 invoked from network); 3 Jan 2001 18:11:58 -0000 Received: from unknown (HELO gonzo.speakeasy.net) (192.168.0.5) by 192.168.0.13 with SMTP; 3 Jan 2001 18:11:58 -0000 Received: (qmail 2301 invoked from network); 3 Jan 2001 18:18:45 -0000 Received: from unknown (HELO celebris.tddhome) (64.81.20.229) by gonzo.speakeasy.net with SMTP; 3 Jan 2001 18:18:45 -0000 Received: (from tomdean@localhost) by celebris.tddhome (8.11.1/8.11.1) id f03IIiZ00370; Wed, 3 Jan 2001 10:18:44 -0800 (PST) (envelope-from tomdean@speakeasy.org) Date: Wed, 3 Jan 2001 10:18:44 -0800 (PST) Message-Id: <200101031818.f03IIiZ00370@celebris.tddhome> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@speakeasy.org using -f From: "Thomas D. Dean" To: freebsd-current@FreeBSD.ORG Subject: Make World Success - Good Going Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just completed a 'make world' from sources at midnight PST. I made a static vi before starting. I had problems trying to make libc. I got lots of complaints about 'tqh_last' not being members of a structure. But, world completed OK. Must have been something on my system or something I did. Good work everyone. I have a nagging worry with SMP, but, UP seems OK, now. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 10:26:34 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 10:26:32 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 711A137B400 for ; Wed, 3 Jan 2001 10:26:32 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA89316 for ; Wed, 3 Jan 2001 10:26:31 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f03IQVU62137 for current@freebsd.org; Wed, 3 Jan 2001 10:26:31 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 10:26:30 -0800 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** world build known broken Message-ID: <20010103102630.A62110@dragon.nuxi.com> Reply-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i 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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I suspected. I've got to head to an appointment, so the world will be broken for a little while. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 10:29:39 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 10:29:37 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 0607E37B400; Wed, 3 Jan 2001 10:29:36 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14Dseb-0003KG-00; Wed, 03 Jan 2001 19:28:53 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14Dseb-00064W-00; Wed, 03 Jan 2001 19:28:53 +0100 Date: Wed, 3 Jan 2001 19:28:53 +0100 From: Nicolas Souchu To: Andrew Kenneth Milton Cc: freebsd-current@freebsd.org, msmith@freebsd.org Subject: Re: turning off vga_pci Message-ID: <20010103192853.C22841@wiliam.alcove-int> References: <20001230031324.A93726@zeus.theinternet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <20001230031324.A93726@zeus.theinternet.com.au>; from akm@mail.theinternet.com.au on Sat, Dec 30, 2000 at 03:13:24AM +1000 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 30, 2000 at 03:13:24AM +1000, Andrew Kenneth Milton wrote: > Is there a nice way to stop vga_pci from attaching to my video card, or > to allow another driver to attach to it after vga_pci has done its thing? > > At the moment I'm removing all traces of vga_pci from the Makefile in > my kernel 'compile' directory (which works)... Just remove the vga_pci entry in sys/conf/files. It would be nice to make this optional if we want to load a module for a given graphic card later on. I have for example a VESA-extended driver (http://www.freebsd.org/~nsouch/download/s3pci.c) for S3 graphic cards that _have_ linear framebuffer but only VESA 1.2 bios. It currently works on top of VESA by replacing the video switch by another. Exactly as VESA does on top of VGA. What about including it into the tree as a module... s3_pci.c would be in sys/dev/pci, nothing in sys/conf/files: just a module in sys/modules/s3. Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 10:36:31 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 10:36:29 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (placeholder-dcat-1076843399.broadbandoffice.net [64.47.83.135]) by hub.freebsd.org (Postfix) with ESMTP id 2936837B400 for ; Wed, 3 Jan 2001 10:36:29 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f03IZmP48298; Wed, 3 Jan 2001 10:35:48 -0800 (PST) (envelope-from dillon) Date: Wed, 3 Jan 2001 10:35:48 -0800 (PST) From: Matt Dillon Message-Id: <200101031835.f03IZmP48298@earth.backplane.com> To: "David O'Brien" Cc: current@FreeBSD.ORG Subject: Re: ** HEADS UP ** world build known broken References: <20010103102630.A62110@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I :suspected. I've got to head to an appointment, so the world will be broken :for a little while. : ( sky starts to fall as David O takes a coffee break at the local starbucks, remarking merrily to other patrons who are staring out the window in horror: "I did that!" ). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 11:28:53 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 11:28:50 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 296CA37B400 for ; Wed, 3 Jan 2001 11:28:50 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 14Dtaa-000JWC-00; Wed, 03 Jan 2001 19:28:48 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.1) id f03JTcB01119; Wed, 3 Jan 2001 20:29:38 +0100 (CET) (envelope-from wkb) Date: Wed, 3 Jan 2001 20:29:38 +0100 From: Wilko Bulte To: Matt Dillon Cc: "David O'Brien" , current@freebsd.org Subject: Re: ** HEADS UP ** world build known broken Message-ID: <20010103202938.H336@freebie.demon.nl> References: <20010103102630.A62110@dragon.nuxi.com> <200101031835.f03IZmP48298@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200101031835.f03IZmP48298@earth.backplane.com>; from dillon@earth.backplane.com on Wed, Jan 03, 2001 at 10:35:48AM -0800 X-OS: FreeBSD 4.2-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 10:35:48AM -0800, Matt Dillon wrote: > > :The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I > :suspected. I've got to head to an appointment, so the world will be broken > :for a little while. > : > > ( sky starts to fall as David O takes a coffee break at the local > starbucks, remarking merrily to other patrons who are staring out > the window in horror: "I did that!" ). Yikes.. if that is the case my vote is to hook David up to an IV caffeine drip.. ;-) -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 18:22:43 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 18:22:42 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id C9CA837B400 for ; Wed, 3 Jan 2001 18:22:41 -0800 (PST) Received: from dragon.nuxi.com (Ipitythefoolthattrustsident@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA91762 for ; Wed, 3 Jan 2001 18:22:41 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id f042Meg64406 for current@freebsd.org; Wed, 3 Jan 2001 18:22:40 -0800 (PST) (envelope-from obrien) Date: Wed, 3 Jan 2001 18:22:40 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: ** HEADS UP ** world build known broken Message-ID: <20010103182239.A64370@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20010103102630.A62110@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010103102630.A62110@dragon.nuxi.com>; from TrimYourCc@NUXI.com on Wed, Jan 03, 2001 at 10:26:30AM -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: obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 10:26:30AM -0800, David O'Brien wrote: > The merging of our bits into GCC 2.95.3(RC#1) took a little longer than I > suspected. I've got to head to an appointment, so the world will be broken > for a little while. World should be buildable again. Quite sorry for the longer than expected delay, I'm not happy how long I took. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 20:13:30 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 20:13:29 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 29D2537B400; Wed, 3 Jan 2001 20:13:28 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f044DQs12669; Wed, 3 Jan 2001 21:13:27 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101040413.f044DQs12669@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: John Baldwin Cc: Jonathan Chen , imp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Cardbus woes In-Reply-To: Your message of "Wed, 27 Dec 2000 13:43:57 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Jan 2001 21:13:26 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I was mostly trying to push the locks down so that they weren't held during >attach and remove. I was using them to protect mostly the kthread state flag >in the softc, as well as other variables in the softc. > >> Comments? It seems to me that having a single thread per-softc gives you this protection without requiring any locks. Other than having to aquire Giant at thread starup (as most code below us is not thread safe yet), I don't see any other locking requirements. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 20:29:56 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 20:29:54 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 5DF7237B400; Wed, 3 Jan 2001 20:29:53 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f044Tqs12960; Wed, 3 Jan 2001 21:29:52 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101040429.f044Tqs12960@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Cc: John Baldwin , Jonathan Chen , imp@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Cardbus woes In-Reply-To: Your message of "Wed, 03 Jan 2001 21:13:26 MST." <200101040413.f044DQs12669@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 Jan 2001 21:29:52 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It seems to me that having a single thread per-softc gives you this >protection without requiring any locks. Other than having to aquire >Giant at thread starup (as most code below us is not thread safe yet), >I don't see any other locking requirements. I take that back. In pccbb_detach, you need a mechanism to ensure that you are no-longer executing in your interrupt handler prior to destroying the softc. What you really want on detach (not only for pccbb, but in general), is a way to kill your ithread via bus_teardown_intr. Since we only provide a single ithread per shareable interrupt source, this wouldn't quite work, but you get the general idea. Can anyone think of another general "synchronization method" for a case where the second event may never happen again? Even if you check in the detach routine to see if an interrupt is pending in hardware for your device, this won't tell you if your interrupt thread has already been dispatched but the interrupt source has gone away (card was removed, so interrupt line is dead). Hmmm. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 22: 2:42 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 22:02:39 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.82]) by hub.freebsd.org (Postfix) with ESMTP id 516B237B400 for ; Wed, 3 Jan 2001 22:02:37 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id A2BEC61077; Thu, 4 Jan 2001 13:02:21 +0700 (JAVT) Date: Thu, 4 Jan 2001 13:02:21 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: make buildkernel failed Message-ID: <20010104130221.A517@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-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all... Recent -CURRENT make buildkernel target died with this message: ===> uscanner cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c/usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: `USB_PRODUCT_EPSON_1640' undeclared here (not in a function) /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: initializer element is not constant /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: (near initialization for `scanner_ids[45].product') *** Error code 1 Stop in /usr/src/sys/modules/uscanner. *** Error code 1 Stop in /usr/src/sys/modules. *** Error code 1 Stop in /usr/obj/usr/src/sys/DANTE. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 22:12: 5 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 22:12:02 2001 Return-Path: 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 2545B37B400 for ; Wed, 3 Jan 2001 22:12:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id f046Bx828061 for ; Thu, 4 Jan 2001 15:12:00 +0900 (JST) (envelope-from 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 (Peisino,Ak(B) 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: 11 From: Makoto MATSUSHITA To: current@freebsd.org Subject: Can't check with LINT kernel (i386) Date: Thu, 04 Jan 2001 15:11:49 +0900 Message-Id: <20010104151149C.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires COMPAT_OLDPCI support which is removed a few weeks before. Can we temporary disable these devices from src/sys/i386/conf/NOTES ? -- - Makoto MATSUSHITA To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 22:27:32 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 22:27:29 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from biperson.com (biperson.com [64.19.199.34]) by hub.freebsd.org (Postfix) with ESMTP id 091A037B402 for ; Wed, 3 Jan 2001 22:27:29 -0800 (PST) Received: (from root@localhost) by biperson.com (8.9.3/8.9.3) id WAA10542 for freebsd-current@FreeBSD.org; Wed, 3 Jan 2001 22:27:23 -0800 Date: Wed, 3 Jan 2001 22:27:23 -0800 From: lolly@biperson.com Message-Id: <200101040627.WAA10542@biperson.com> To: freebsd-current@FreeBSD.org Subject: If you come only once, you've been cheated. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Our motto: More tail for less money. We've got whining, spoiled, American bitches getting what's coming to them. And liking it! Spum guzzling hose hogs who can't live without a white boy's jimmy or a black boy's cactus in their mouths 24 hours a day! (We have to punish them when they swallow instead of taking it on the face!) Delicate, oriental beauties with tight cooters getting split down the middle, lumberjack style! Sign me up Jack!!! Gorgeous, buxom, chocolate wenches that will make your snicker caramel its nuts! Latin lovelies getting their tacos stuffed with the biggest beef in Texas! Remember that teacher with big knobs whose skirt you used to look up? Yes? Well, we got her too! Young? Old? Thick? Thin? Tall? Short? Whatever! If it's got a hole and a temperature we've got it! http://64.19.199.34/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 22:47: 4 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 22:47:03 2001 Return-Path: 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 3065D37B400 for ; Wed, 3 Jan 2001 22:47:02 -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 RAA27939; Thu, 4 Jan 2001 17:46:50 +1100 Date: Thu, 4 Jan 2001 17:47:43 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Makoto MATSUSHITA Cc: current@FreeBSD.ORG Subject: Re: Can't check with LINT kernel (i386) In-Reply-To: <20010104151149C.matusita@jp.FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 4 Jan 2001, Makoto MATSUSHITA wrote: > > > According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet > SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires > COMPAT_OLDPCI support which is removed a few weeks before. > > Can we temporary disable these devices from src/sys/i386/conf/NOTES ? No. This would defeat the main points of NOTES, which are to test everything and generate mail for people who break something. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 3 23:15:58 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 23:15:57 2001 Return-Path: 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 911CE37B402 for ; Wed, 3 Jan 2001 23:15:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by updraft.jp.freebsd.org (8.11.1+3.4W/8.11.1) with ESMTP/inet id f047Fm828513; Thu, 4 Jan 2001 16:15:50 +0900 (JST) (envelope-from matusita@jp.FreeBSD.org) Cc: current@FreeBSD.ORG In-Reply-To: References: <20010104151149C.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 (Peisino,Ak(B) 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: 9 From: Makoto MATSUSHITA To: bde@zeta.org.au Subject: Re: Can't check with LINT kernel (i386) Date: Thu, 04 Jan 2001 16:15:36 +0900 Message-Id: <20010104161536F.matusita@jp.FreeBSD.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG bde> No. This would defeat the main points of NOTES, which are to bde> test everything and generate mail for people who break something. Ah, sorry. I just forget why we have NOTES. -- - 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 Jan 3 23:20:55 2001 From owner-freebsd-current@FreeBSD.ORG Wed Jan 3 23:20:52 2001 Return-Path: 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 F2D6637B400 for ; Wed, 3 Jan 2001 23:20:49 -0800 (PST) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.0/8.11.0) id f047Ilk46558; Thu, 4 Jan 2001 09:18:47 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200101040718.f047Ilk46558@zibbi.icomtek.csir.co.za> Subject: Re: Can't check with LINT kernel (i386) In-Reply-To: from Bruce Evans at "Jan 4, 2001 05:47:43 pm" To: bde@zeta.org.au (Bruce Evans) Date: Thu, 4 Jan 2001 09:18:46 +0200 (SAT) Cc: matusita@jp.FreeBSD.org (Makoto MATSUSHITA), 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: jhay@zibbi.icomtek.csir.co.za Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > > According to this logfile, 'cy' (Cyclades serial), 'ar' (Arnet > > SYNC/570i), 'sr' (RISCom/N2) and 'meteor' (Matrox meteor) requires > > COMPAT_OLDPCI support which is removed a few weeks before. > > > > Can we temporary disable these devices from src/sys/i386/conf/NOTES ? > > No. This would defeat the main points of NOTES, which are to test everything > and generate mail for people who break something. Well I wouldn't mind if we disable the ar(4) and sr(4) drivers. I know they are broken and am in the process of fixing them. It just takes a little longer than I anticipated because of a new kiddie that pitched up and parents hat came to visit and so on. :-/ 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 Thu Jan 4 1:17: 3 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 01:17:02 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from seagull.infodom.ru (seagull.infodom.ru [212.45.11.91]) by hub.freebsd.org (Postfix) with ESMTP id BB67137B404 for ; Thu, 4 Jan 2001 01:17:01 -0800 (PST) Received: from gatekeeper.infodom.ru ([212.45.11.140] helo=bp) by seagull.infodom.ru with smtp (Exim 3.13 #1) id 14E6Vv-0003d0-00 for freebsd-current@FreeBSD.org; Thu, 04 Jan 2001 12:16:51 +0300 Message-ID: <001d01c0762e$bd32cc50$b564a8c0@bp> From: "Pavel Bolotin" To: Subject: Join Date: Thu, 4 Jan 2001 12:14:27 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Join ------------------- Pavel Bolotin System Engineer V6 Company phone: 913-9313 bp@v6.ru ------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 1:34:54 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 01:34:52 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mailgate.westmarsh.com (unknown [193.195.76.57]) by hub.freebsd.org (Postfix) with ESMTP id A7D5937B400 for ; Thu, 4 Jan 2001 01:34:51 -0800 (PST) Received: from westmarsh.com (mailgate.westmarsh.com [193.195.76.50]) by mailgate.westmarsh.com (8.11.1/8.11.1) with ESMTP id f049Y1n18969; Thu, 4 Jan 2001 09:34:04 GMT (envelope-from pierre.dampure@westmarsh.com) Sender: pierre.dampure@westmarsh.com Message-ID: <3A544389.432F9800@westmarsh.com> Date: Thu, 04 Jan 2001 09:34:01 +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: John Indra Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel failed References: <20010104130221.A517@naver.co.id> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Indra wrote: > > Dear all... > > Recent -CURRENT make buildkernel target died with this message: > > ===> uscanner > cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/dev -I@/../include -mpreferred-stack-boundary=2 -c > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c/usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: > `USB_PRODUCT_EPSON_1640' undeclared here (not in a function) > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: initializer > element > is not constant > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: (near > initialization for `scanner_ids[45].product') > *** Error code 1 > It looks like devlist2h.awk was not re-run after addition of the EPSON scanner (there is an entry for it in usbdevs, but not in usbdevs.h, hence the above error). You can run it manually by changing to /sys/dev/usb and issuing a: make -f Makefile.usbdevs That should fix your build. PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 1:45:57 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 01:45:55 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 31C2E37B400; Thu, 4 Jan 2001 01:45:51 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14E6xt-0000vq-00; Thu, 04 Jan 2001 10:45:45 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14E6xs-0006Xp-00; Thu, 04 Jan 2001 10:45:44 +0100 Date: Thu, 4 Jan 2001 10:45:44 +0100 From: Nicolas Souchu To: David O'Brien Cc: freebsd-current@freebsd.org Subject: Re: missing THREAD_UNLOCK in libc? Message-ID: <20010104104544.B25110@wiliam.alcove-int> References: <20010103175425.A22841@wiliam.alcove-int> <20010103100022.A61682@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <20010103100022.A61682@dragon.nuxi.com>; from obrien@freebsd.org on Wed, Jan 03, 2001 at 10:00:22AM -0800 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 03, 2001 at 10:00:22AM -0800, David O'Brien wrote: > On Wed, Jan 03, 2001 at 05:54:26PM +0100, Nicolas Souchu wrote: > > A program that previously worked (-current of November) with -pthread now > > fails with an abort and a " in free(): error: recursive call" warning. > > I need a copy of this program (source form) to test with. Tell me rather how you'd investigate it. It's a bit large (GGI). Nicholas -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 2: 8:41 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 02:08:39 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mailgate.westmarsh.com (orion.westmarsh.com [193.195.76.57]) by hub.freebsd.org (Postfix) with ESMTP id 5735D37B400 for ; Thu, 4 Jan 2001 02:08:38 -0800 (PST) Received: from westmarsh.com (mailgate.westmarsh.com [193.195.76.50]) by mailgate.westmarsh.com (8.11.1/8.11.1) with ESMTP id f04A7fn39338; Thu, 4 Jan 2001 10:07:50 GMT (envelope-from pierre.dampure@westmarsh.com) Sender: pierre.dampure@westmarsh.com Message-ID: <3A544B69.91F5BA02@westmarsh.com> Date: Thu, 04 Jan 2001 10:07:37 +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: John Indra , freebsd-current@freebsd.org Subject: Re: make buildkernel failed References: <20010104130221.A517@naver.co.id> <3A544389.432F9800@westmarsh.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. It looks like there were other bits missing... the MELCO LUATX entry was replaced in the last commit to usbdevs by two new entries, LUATX1 and LUATX5, but if_aue.c was not modified to reflect this. You need to do this manually. If the goal is to make modifications in one place only (and that certainly seems to be the case, hence usbdev2h.awk), maybe what's required is a new field in the usbdevs table, so that the tables used by the various *.c get generated automagically too? PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 2:31:13 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 02:31:11 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.82]) by hub.freebsd.org (Postfix) with ESMTP id E270337B402 for ; Thu, 4 Jan 2001 02:31:10 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id C691D60F42; Thu, 4 Jan 2001 17:30:49 +0700 (JAVT) Date: Thu, 4 Jan 2001 17:30:49 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: Re: make buildkernel failed Message-ID: <20010104173049.B52463@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org References: <20010104130221.A517@naver.co.id> <3A544389.432F9800@westmarsh.com> <3A544B69.91F5BA02@westmarsh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3A544B69.91F5BA02@westmarsh.com>; from pierre.dampure@westmarsh.com on Thu, Jan 04, 2001 at 10:07:37AM +0000 X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 10:07:37AM +0000, Pierre Y. Dampure wrote: >Hmmm. It looks like there were other bits missing... the MELCO LUATX >entry was replaced in the last commit to usbdevs by two new entries, >LUATX1 and LUATX5, but if_aue.c was not modified to reflect this. You >need to do this manually. >If the goal is to make modifications in one place only (and that >certainly seems to be the case, hence usbdev2h.awk), maybe what's >required is a new field in the usbdevs table, so that the tables used by >the various *.c get generated automagically too? I really really wish I could understand this :) I'm not a C programmer, and I'm just a FreeBSD user tracking -CURRENT. But I am learning, so that one they I can help commit a helpful patches :) /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 3:20:25 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 03:20:23 2001 Return-Path: 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 04CDB37B400 for ; Thu, 4 Jan 2001 03:20:21 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14E8RB-0003Rt-00; Thu, 04 Jan 2001 13:20:05 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id NAA19825; Thu, 4 Jan 2001 13:20:02 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 19600; Thu Jan 4 13:19:01 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14E8Q8-000NGm-00; Thu, 04 Jan 2001 13:19:00 +0200 From: Sheldon Hearn To: "Pierre Y. Dampure" Cc: John Indra , freebsd-current@freebsd.org Subject: Re: make buildkernel failed In-reply-to: Your message of "Thu, 04 Jan 2001 10:07:37 GMT." <3A544B69.91F5BA02@westmarsh.com> Date: Thu, 04 Jan 2001 13:19:00 +0200 Message-ID: <89451.978607140@axl.fw.uunet.co.za> Sender: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Jan 2001 10:07:37 GMT, "Pierre Y. Dampure" wrote: > If the goal is to make modifications in one place only (and that > certainly seems to be the case, hence usbdev2h.awk), maybe what's > required is a new field in the usbdevs table, so that the tables used by > the various *.c get generated automagically too? In the meantime, rev 1.9 of uscanner.c fixes the kernel build. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 4:19:34 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 04:19:31 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from henny.webweaving.org (unknown [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 3409137B400 for ; Thu, 4 Jan 2001 04:19:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id LAA11821; Thu, 4 Jan 2001 11:50:35 GMT (envelope-from n_hibma@calcaphon.com) Date: Thu, 4 Jan 2001 11:50:35 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@henny.webweaving.org Reply-To: Nick Hibma To: John Indra Cc: freebsd-current@freebsd.org Subject: Re: make buildkernel failed In-Reply-To: <20010104130221.A517@naver.co.id> 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 Sorry, me lame. I got distrcacted between committing usbdevs and its derivative usbdevs.h. I've committed the file and am doing a complete kernel build and will commit uscanner.c 1.8 again after that. Sorry. Nick On Thu, 4 Jan 2001, John Indra wrote: > Dear all... > > Recent -CURRENT make buildkernel target died with this message: > > ===> uscanner > cc -O -pipe -g -D_KERNEL -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ > -I@/dev -I@/../include -mpreferred-stack-boundary=2 -c > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c/usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: > `USB_PRODUCT_EPSON_1640' undeclared here (not in a function) > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: initializer > element > is not constant > /usr/src/sys/modules/uscanner/../../dev/usb/uscanner.c:146: (near > initialization for `scanner_ids[45].product') > *** Error code 1 > > Stop in /usr/src/sys/modules/uscanner. > *** Error code 1 > > Stop in /usr/src/sys/modules. > *** Error code 1 > > Stop in /usr/obj/usr/src/sys/DANTE. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > > /john > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Qube Software, Ltd. Private: n_hibma@qubesoft.com n_hibma@webweaving.org n_hibma@freebsd.org http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 4:48:24 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 04:48:20 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from citadel.cequrux.com (citadel.cequrux.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 0F15D37B402 for ; Thu, 4 Jan 2001 04:48:17 -0800 (PST) Received: (from nobody@localhost) by citadel.cequrux.com (8.8.8/8.6.9) id OAA26733 for ; Thu, 4 Jan 2001 14:48:13 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 26615; Thu Jan 4 14:47:52 2001 Sender: gram@citadel.cequrux.com Message-ID: <3A5458B0.6FFFB454@cequrux.com> Date: Thu, 04 Jan 2001 13:04:16 +0200 From: Graham Wheeler Organization: Cequrux Technologies X-Mailer: Mozilla 4.75 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Manual contribution Content-Type: multipart/mixed; boundary="------------1459E9AAC9540CAF48FC5DC5" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------1459E9AAC9540CAF48FC5DC5 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi all Sometime back I submitted a short manual contribution about the kernel.conf file. I note that this hasn't found its way into the handbook; I'm attaching it to this message in the hope that someone will add it and commit it. regards gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Director, Research and Development WWW: http://www.cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/VPN Specialists Fax: +27(21)424-3656 --------------1459E9AAC9540CAF48FC5DC5 Content-Type: text/plain; charset=us-ascii; name="config.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="config.txt" Configuring An Already Compiled Kernel If you don't want to create a custom kernel, you can configure many hardware settings for none Plug 'n' Play devices without doing so, by putting them in the /boot/kernel.conf file. This file contains a sequence of commands compatible with those that are supported by the kernel configuration editor (which you may have seen when you first installed FreeBSD, and which is also accessible by booting with a `-c' argument). Because the commands in this file are essentially fed to the kernel configuration editor, the last command in the file should be `q' for `quit'. The commands that the kernel configuration editor understands are: di(sable) Disable device en(able) Enable device dr(q) Set DMA channel for device to ei(sa) Set number of EISA slots to probe f(lags) Set the device-specific flags for the device iom(em)
Sets the base address of the I/O memory ios(ize) Sets the size of the I/O memory ir(q) Set the IRQ for the device po(rt) Set the I/O port base address for the device ex Exit (quit) q Quit The commands are shown with their full names, and the optional parts parenthesised. Thus, for example, the "enable" command can be abbreviated to "en". There are other commands, for example to list the devices or reset the CPU, but these only make sense when using the interactive editor, and not when using kernel.conf. , , ,
, are all numeric arguments. They can be either decimal numbers, or hexadecimal numbers (in which case they must be prefixed by "0x"). Here is a simple example, which sets the interrupt and port for device ed0 to be irq 10, port 0x320: irq ed0 10 port ed0 0x320 q --------------1459E9AAC9540CAF48FC5DC5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 5:11:16 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 05:11:14 2001 Return-Path: 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 6E7D537B402 for ; Thu, 4 Jan 2001 05:11:12 -0800 (PST) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 14EAAf-0004d5-00; Thu, 04 Jan 2001 15:11:09 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id PAA12714; Thu, 4 Jan 2001 15:11:08 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 12517; Thu Jan 4 15:10:09 2001 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.20 #1) id 14EA9g-000NUt-00; Thu, 04 Jan 2001 15:10:08 +0200 From: Sheldon Hearn To: Graham Wheeler Cc: freebsd-current@freebsd.org Subject: Re: Manual contribution In-reply-to: Your message of "Thu, 04 Jan 2001 13:04:16 +0200." <3A5458B0.6FFFB454@cequrux.com> Date: Thu, 04 Jan 2001 15:10:08 +0200 Message-ID: <90326.978613808@axl.fw.uunet.co.za> Sender: Sheldon Hearn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 04 Jan 2001 13:04:16 +0200, Graham Wheeler wrote: > Sometime back I submitted a short manual contribution about the > kernel.conf file. I note that this hasn't found its way into the > handbook; These things have much better odds of adoption when they're either mailed to the freebsd-doc mailing list or (even better) filed as doc category PRs. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 5:11:55 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 05:11:53 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from numeri.campus.luth.se (numeri.campus.luth.se [130.240.197.103]) by hub.freebsd.org (Postfix) with ESMTP id D2C3337B400 for ; Thu, 4 Jan 2001 05:11:52 -0800 (PST) Received: from numeri.campus.luth.se (localhost [127.0.0.1]) by numeri.campus.luth.se (8.9.3/8.9.3) with ESMTP id OAA72242; Thu, 4 Jan 2001 14:12:59 +0100 (CET) (envelope-from k@numeri.campus.luth.se) Message-Id: <200101041312.OAA72242@numeri.campus.luth.se> X-Mailer: exmh version 2.1.1 10/15/1999 To: Graham Wheeler Cc: freebsd-current@FreeBSD.ORG Subject: Re: Manual contribution In-Reply-To: Your message of "Thu, 04 Jan 2001 13:04:16 +0200." <3A5458B0.6FFFB454@cequrux.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Jan 2001 14:12:59 +0100 From: Johan Karlsson Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Thu, 04 Jan 2001 13:04:16 +0200, Graham Wheeler wrote: > This is a multi-part message in MIME format. > --------------1459E9AAC9540CAF48FC5DC5 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > Hi all > > Sometime back I submitted a short manual contribution about the > kernel.conf file. I note that this hasn't found its way into the > handbook; I'm attaching it to this message in the hope that someone will > add it and commit it. > > regards > gram Please use send-pr (or the w3 interface) for this kind of contributions, that way it will not get lost evwen if no one adds it right away. /Johan K To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 6:11: 1 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 06:10:52 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from ada.eu.org (marvin.enst.fr [137.194.161.2]) by hub.freebsd.org (Postfix) with ESMTP id F054637B400 for ; Thu, 4 Jan 2001 06:10:51 -0800 (PST) Received: by ada.eu.org (Postfix, from userid 10) id 0498119190; Thu, 4 Jan 2001 15:10:50 +0100 (CET) Received: by trillian.enst.fr (Postfix, from userid 1000) id E8C1278; Thu, 4 Jan 2001 15:06:36 +0100 (CET) Date: Thu, 4 Jan 2001 15:06:36 +0100 To: freebsd-current@freebsd.org Subject: Booting with Ethernet plugged in Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i From: Samuel Tardieu Organization: Ecole Nationale Superieure des Telecommunications Reply-To: Samuel Tardieu Content-Transfer-Encoding: 8bit X-WWW: http://www.inf.enst.fr/~tardieu/ X-Mail-Processing: Sam's procmail tools X-ICQ: 21547599 X-Sam-Laptop: yes Message-Id: <2001-01-04-15-06-36+trackit+sam@inf.enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Sony VAIO PCG-Z600NE with an internal fxp0. I do not configure the network in rc.conf as I do not want to launch dhclient unconditionnaly. As long as the interface has not been brought up, I get errors when packets are seen on it (well, I guess this is it, I receive approximately two messages per second, which correspond to the frequency of the broadcasts on my switched network). See end of dmesg for warnings. This is -CURRENT from one hour ago. Note that with late december -CURRENT, I got panics when booting with Ethernet plugged in. Sam 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: Thu Jan 4 14:31:57 CET 2001 root@trillian.enst.fr:/usr/obj/usr/src/sys/TRILLIAN Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (645.21-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383f9ff real memory = 134152192 (131008K bytes) avail memory = 126152704 (123196K bytes) Preloaded elf kernel "kernel" at 0xc0446000. Preloaded elf module "ipl.ko" at 0xc044609c. link_elf: symbol pfil_add_hook undefined KLD file ipl.ko - could not finalize loading Pentium Pro MTRR support enabled ACPI debug layer 0x0 debug level 0x0 Using $PIR table, 7 entries at 0xc00fdf50 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 acpi0: on motherboard acpi_tz0: on acpi0 acpi_tz0: current temperature 65.9C acpi_button0: on acpi0 acpi_pcib0: on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga_pci0: mem 0xfeb00000-0xfebfffff,0xfe400000-0xfe7fffff,0xfc000000-0xfdffffff irq 9 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfc90-0xfc9f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xfca0-0xfcbf irq 9 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at 7.3 (no driver attached) pci0: at 8.0 (no driver attached) pcm0: port 0xfc8c-0xfc8f,0xfcc0-0xfcff mem 0xfedf8000-0xfedfffff irq 9 at device 9.0 on pci0 pci0: at 10.0 (no driver attached) fxp0: port 0xfc40-0xfc7f mem 0xfec00000-0xfecfffff,0xfedf6000-0xfedf6fff irq 9 at device 11.0 on pci0 fxp0: Ethernet address 08:00:46:0c:b4:c7 pcic-pci0: at device 12.0 on pci0 pci0: at 13.0 (no driver attached) acpi_ec0: on acpi0 acpi_cmbat0: on acpi0 acpi_acad0: on acpi0 acpi_acad0: On Line acpi_pr0: on acpi0 acpi_pr0: supported power states: C0 (0us) C1 (0us) C2 (10us) acpi_pr0: supported throttling states: 100% 87% 75% 62% 50% 37% 25% 12% acpi_timer0: <24-bit timer at 3.579545MHz> on acpi0 npx0: on motherboard npx0: INT 16 interface atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model GlidePoint, device ID 0 pcic0: at port 0x3e0 iomem 0xd0000 irq 10 on isa0 pcic0: management irq 10 pccard0: on pcic0 pmtimer0 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 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: configured irq 3 not in bitmap of probed irqs 0 spic0: at port 0x10a0-0x10a4 on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atspeaker0: at port 0x61 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ppc1: parallel port not found. ppc1: parallel port not found. unknown: can't assign resources ppc1: parallel port not found. IPsec: Initialized Security Association Processing. ad0: 11513MB [23392/16/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s2a swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. swi_net: unregistered isr number: 18. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 9: 9:12 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 09:09:10 2001 Return-Path: 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 4E00A37B400 for ; Thu, 4 Jan 2001 09:09:06 -0800 (PST) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA75688; Thu, 4 Jan 2001 18:08:55 +0100 (CET) (envelope-from des@ofug.org) Sender: 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: Graham Wheeler Cc: freebsd-current@FreeBSD.ORG Subject: Re: Manual contribution References: <3A5458B0.6FFFB454@cequrux.com> From: Dag-Erling Smorgrav Date: 04 Jan 2001 18:08:54 +0100 In-Reply-To: Graham Wheeler's message of "Thu, 04 Jan 2001 13:04:16 +0200" Message-ID: Lines: 11 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 Graham Wheeler writes: > Sometime back I submitted a short manual contribution about the > kernel.conf file. I note that this hasn't found its way into the > handbook; I'm attaching it to this message in the hope that someone will > add it and commit it. This should be a man page (in section 5), not a handbook entry. 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 Jan 4 12:34:22 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 12:34:21 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from genesis.k.pl (genesis.korbank.pl [195.117.162.253]) by hub.freebsd.org (Postfix) with ESMTP id B17E737B400 for ; Thu, 4 Jan 2001 12:34:16 -0800 (PST) Received: (from ns88@localhost) by genesis.k.pl (8.11.1/8.11.1) id f04KYxU21338 for freebsd-current@freebsd.org; Thu, 4 Jan 2001 21:34:59 +0100 (CET) (envelope-from ns88) Date: Thu, 4 Jan 2001 21:34:59 +0100 From: Tomasz Paszkowski To: freebsd-current@freebsd.org Subject: kernel panic Message-ID: <20010104213459.A26801@genesis.k.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: ns88@genesis.k.pl Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Current from 03.01.2001 have kernel panic (GENERIC kernel configuration to), when doing /etc/periodic/weekly/310.locate >& /dev/null -- _ _ _ _ _ / \ | | / / / \ / \ ---------- Tomasz Paszkowski --- NS88-6BONE -------- | |\ \| | \ \ |/ \||/ \| === BSD is for people who love Unix ================ /_/ \__/ /_/ \_/ \_/ --- Linux is for people who hate Microsoft --------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 13: 6:21 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 13:06:19 2001 Return-Path: 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 723D837B404 for ; Thu, 4 Jan 2001 13:06:19 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id f04L4mG62692; Thu, 4 Jan 2001 13:05: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: <20010104213459.A26801@genesis.k.pl> Date: Thu, 04 Jan 2001 13:05:46 -0800 (PST) From: John Baldwin To: Tomasz Paszkowski Subject: RE: kernel panic Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Jan-01 Tomasz Paszkowski wrote: > > > Current from 03.01.2001 have kernel panic (GENERIC kernel configuration to), > when doing /etc/periodic/weekly/310.locate >& /dev/null Can you build a kernel with 'DDB', 'INVARIANTS', 'INVARIANT_SUPPORT', and 'WITNESS' and get a backtrace when it panic's? -- 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 Jan 4 13:52:27 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 13:52:25 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from panasync.canuck.ca (sktnsk01d05180191.sk.sympatico.ca [142.165.123.91]) by hub.freebsd.org (Postfix) with ESMTP id 10B6537B400 for ; Thu, 4 Jan 2001 13:52:24 -0800 (PST) Received: from localhost (edwards@localhost) by panasync.canuck.ca (8.9.3/8.9.3) with ESMTP id PAA11163 for ; Thu, 4 Jan 2001 15:52:13 -0600 X-Authentication-Warning: panasync.canuck.ca: edwards owned process doing -bs Date: Thu, 4 Jan 2001 15:52:13 -0600 (CST) From: Colten Edwards X-Sender: edwards@panasync.canuck.ca Reply-To: edwards@bitchx.dimension6.com To: freebsd-current@FreeBSD.ORG Subject: problem with make in /usr/src 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 Well I seem to remember a post about the TAILQ_* macro's but I seemed to have deleted it. My current freebsd source will not compile because of a problem in mpool.c which is related to these macro's. If anyone has an idea on this could you either forward the fix for the brokenness or repost here? /usr/src/lib/libc/../libc/db/mpool/mpool.c:338: structure has no member named `tqe_prev' /usr/src/lib/libc/../libc/db/mpool/mpool.c:338: structure has no member named `tqe_prev' /usr/src/lib/libc/../libc/db/mpool/mpool.c:338: structure has no member named `tqe_next' /usr/src/lib/libc/../libc/db/mpool/mpool.c: In function `mpool_look': /usr/src/lib/libc/../libc/db/mpool/mpool.c:404: structure has no member named `tqh_first' /usr/src/lib/libc/../libc/db/mpool/mpool.c:404: structure has no member named `tqe_next' *** Error code 1 Colten Edwards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 14:20:20 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 14:20:15 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (poynting.physics.purdue.edu [128.210.146.58]) by hub.freebsd.org (Postfix) with ESMTP id C70D237B404 for ; Thu, 4 Jan 2001 14:20:14 -0800 (PST) Received: from argon.firepipe.net (pm013-044.dialup.bignet.net [64.79.82.108]) by puck.firepipe.net (Postfix) with ESMTP id 6BF581A0A; Thu, 4 Jan 2001 17:20:13 -0500 (EST) Received: by argon.firepipe.net (Postfix, from userid 1000) id B1FE819E0; Thu, 4 Jan 2001 17:20:05 -0500 (EST) Date: Thu, 4 Jan 2001 17:20:05 -0500 From: Will Andrews To: Garrett Wollman Cc: current@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/apply apply.c Message-ID: <20010104172004.P86630@argon.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Garrett Wollman , current@FreeBSD.org References: <200101041905.f04J5ou82617@freefall.freebsd.org> <200101041909.OAA61522@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101041909.OAA61522@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Jan 04, 2001 at 02:09:53PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: will@argon.firepipe.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 02:09:53PM -0500, Garrett Wollman wrote: > What is the reason for this change? Paranoia. There's nothing wrong with a little extra paranoia in case someone tries to use apply(1) through suidperl on a web interface. Granted, it's not likely to happen, but you never know. > I see no benefit in modifying many programs in this manner which do > not ordinarily run with elevated privileges. I do; FreeBSD's reputation for security. There's nothing like having some confidence in the OS. > It is the responsibility of those programs that do, to ensure that the > environment passed to their children is safe and sane. So what? Not that many people consider security concerns, let alone write them. What, exactly, are we trading off by making apply(1) a bit more paranoid? A couple extra cpu cycles? Maybe you haven't noticed, but these days there's almost nobody still using 100MHz chips. And out of the ones that do, how many will use apply(1) more than once or twice in the lifetime of the machine? I think such logic could be applied to most usr.bin and probably other parts of the tree. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 15:20:53 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 15:20:51 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 9A68737B400 for ; Thu, 4 Jan 2001 15:20:50 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f04NKnl09141; Thu, 4 Jan 2001 16:20:49 -0700 (MST) (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.8.3) with ESMTP id f04NKm147924; Thu, 4 Jan 2001 16:20:48 -0700 (MST) Message-Id: <200101042320.f04NKm147924@harmony.village.org> To: Will Andrews Subject: Re: cvs commit: src/usr.bin/apply apply.c Cc: Garrett Wollman , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Jan 2001 17:20:05 EST." <20010104172004.P86630@argon.firepipe.net> References: <20010104172004.P86630@argon.firepipe.net> <200101041905.f04J5ou82617@freefall.freebsd.org> <200101041909.OAA61522@khavrinen.lcs.mit.edu> Date: Thu, 04 Jan 2001 16:20:48 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010104172004.P86630@argon.firepipe.net> Will Andrews writes: : What, exactly, are we trading off by making apply(1) a bit more : paranoid? A couple extra cpu cycles? Maybe you haven't noticed, but : these days there's almost nobody still using 100MHz chips. And out of : the ones that do, how many will use apply(1) more than once or twice in : the lifetime of the machine? First off, we do still have a significant part of the user base that is using older, slower machines. Many of them run embedded systems, some of which use apply(1). I have a big problem with this argument since it is doesn't understand the wide range of environments that FreeBSD runs in and runs very well in. Having said that, these patches are likely not to significantly slow things down. Apply tends to do a lot of I/O, which swamps the few extra instructions that the strl* or snprintf routines introduce. There's little reason to optimize things. I'm still not sure about the shell environment actually buying anything, but I could see how it might help. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 15:25:58 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 15:25:56 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from puck.firepipe.net (poynting.physics.purdue.edu [128.210.146.58]) by hub.freebsd.org (Postfix) with ESMTP id E425A37B400 for ; Thu, 4 Jan 2001 15:25:55 -0800 (PST) Received: from argon.firepipe.net (pm013-044.dialup.bignet.net [64.79.82.108]) by puck.firepipe.net (Postfix) with ESMTP id A6E6E1A0A; Thu, 4 Jan 2001 18:25:54 -0500 (EST) Received: by argon.firepipe.net (Postfix, from userid 1000) id C9FCD19E0; Thu, 4 Jan 2001 18:25:46 -0500 (EST) Date: Thu, 4 Jan 2001 18:25:46 -0500 From: Will Andrews To: Warner Losh Cc: Will Andrews , Garrett Wollman , current@FreeBSD.ORG Subject: Re: cvs commit: src/usr.bin/apply apply.c Message-ID: <20010104182546.T86630@argon.firepipe.net> Reply-To: Will Andrews Mail-Followup-To: Will Andrews , Warner Losh , Garrett Wollman , current@FreeBSD.ORG References: <20010104172004.P86630@argon.firepipe.net> <200101041905.f04J5ou82617@freefall.freebsd.org> <200101041909.OAA61522@khavrinen.lcs.mit.edu> <20010104172004.P86630@argon.firepipe.net> <200101042320.f04NKm147924@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200101042320.f04NKm147924@harmony.village.org>; from imp@bsdimp.com on Thu, Jan 04, 2001 at 04:20:48PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: will@argon.firepipe.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 04:20:48PM -0700, Warner Losh wrote: > First off, we do still have a significant part of the user base that > is using older, slower machines. Many of them run embedded systems, > some of which use apply(1). I have a big problem with this argument > since it is doesn't understand the wide range of environments that > FreeBSD runs in and runs very well in. I know we do, but I (as you say in the your next paragraph) was trying to point out that the extra checking wasn't likely to slow things down much, and I think it's worth the extra cycles. Please don't get me wrong; if I thought it was gratuitous, I wouldn't have done that in the first place. > I'm still not sure about the shell environment actually buying > anything, but I could see how it might help. I'm not understanding what you're saying here. -- wca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 18:47: 8 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 18:47:07 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3135E37B400 for ; Thu, 4 Jan 2001 18:47:05 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f052l2l09731; Thu, 4 Jan 2001 19:47:03 -0700 (MST) (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.8.3) with ESMTP id f052l2149361; Thu, 4 Jan 2001 19:47:02 -0700 (MST) Message-Id: <200101050247.f052l2149361@harmony.village.org> To: Will Andrews Subject: Re: cvs commit: src/usr.bin/apply apply.c Cc: Garrett Wollman , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Jan 2001 18:25:46 EST." <20010104182546.T86630@argon.firepipe.net> References: <20010104182546.T86630@argon.firepipe.net> <20010104172004.P86630@argon.firepipe.net> <200101041905.f04J5ou82617@freefall.freebsd.org> <200101041909.OAA61522@khavrinen.lcs.mit.edu> <20010104172004.P86630@argon.firepipe.net> <200101042320.f04NKm147924@harmony.village.org> Date: Thu, 04 Jan 2001 19:47:02 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010104182546.T86630@argon.firepipe.net> Will Andrews writes: : > I'm still not sure about the shell environment actually buying : > anything, but I could see how it might help. : : I'm not understanding what you're saying here. I'm saying I agree with Garrett in that I don't see what checking for valid shells buys us in the general case. I'm saying that maybe we might save some sloppy cgi/shell progarmmer from him/her self when the script kidz attack that script. But that's sucha large stretch that I don't see that as a win. Eg, it doesn't buy us much in real situations. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 19: 9:49 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 19:09:42 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (unknown [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 552C337B400; Thu, 4 Jan 2001 19:09:41 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.1/8.11.0) with ESMTP id f0539dl09789; Thu, 4 Jan 2001 20:09:40 -0700 (MST) (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.8.3) with ESMTP id f0539d149502; Thu, 4 Jan 2001 20:09:39 -0700 (MST) Message-Id: <200101050309.f0539d149502@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Cardbus woes Cc: arch@freebsd.org, current@freebsd.org Reply-To: arch@freebsd.org In-reply-to: Your message of "Wed, 03 Jan 2001 21:29:52 MST." <200101040429.f044Tqs12960@aslan.scsiguy.com> References: <200101040429.f044Tqs12960@aslan.scsiguy.com> Date: Thu, 04 Jan 2001 20:09:39 -0700 From: Warner Losh Sender: imp@harmony.village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [[ This is drifting over into -arch, so I'm ccing there and asking people to redirect there. ]] [[ The context is what to do about certain kinds of locking with pccard code raising the bigger issue of what to do with interrupts and sleepers in a hostile environemnt ]] In message <200101040429.f044Tqs12960@aslan.scsiguy.com> "Justin T. Gibbs" writes: : I take that back. In pccbb_detach, you need a mechanism to ensure : that you are no-longer executing in your interrupt handler prior to : destroying the softc. There are two sitautions where you need to worry about things. The first one is where your ISR is interrupted and the thing that interrupts it wants to blow away the device. I think that the current pccard (eg oldcard) code queues an soft interrupt to deal with this so it can't interrupt things, but maybe I'm misremembering. Or maybe it does it badly enough to cause problems (I know this is different than the pccbb case, since that's newcard). The second is where you have sleepers that need to "drain" before you can delete the device. The first one strikes me as a special case of the second one, but maybe it needs to be handled specially. At the BSDcon removable device meeting (which I missed because I found out about it too late), the idea was that the detach routine would sleep until all the sleepers had woken up and exited. Then the detach routine would complete. It was suggested that some provision be made for telling the device that this was a forced detach, but I don't think that was nailed down. I think that having the detach routine call the bridge and ask it if the hardware is still there would come close to answering this question. When the hardware is gone, detach cannot return EBUSY and have that be meaningful. The hardware is gone. Who cares if it is busy, it has to cope with it being ripped untimely from the driver's grasp. Gone is gone :-). One way to deal with this would be to have all devices that sleep do a ref/deref on the device around the sleep. There would be an implicit ref/deref in the ISR too. However, that strikes me as unworkable. There are a lot of drivers that do a lot of sleeping and when they wake up. This would require a massive pass through the entire device driver tree (well, at least for the ones that can be removed). I also don't like the idea of doing boatloads of locking/unlocking code on every single interrupt, but maybe that's unavoidable. One way around the interrupt context problem is to ensure that devices are never removed from an interrupt context. Or are at least never detached from an interrupt context. However, I'm not sure the concept of an interrupt context still has meaning in the new threads for ISR. Can an interrupt thread block and allow other non-interrupt threads to run? Warner P.S. Here's two interfaces that I'd like to add to the bus interface file. They try to implement part of the removable feature. They are based on my talking to phk after the arch meeting I missed. I don't see any other way to ensure that interrupts will terminate. # # Ask the bridge if the device is still there. If the bus doesn't # support removal, then it should always return true. If the bus # does support removal, this method must return the real status of # the child. Generally this is done by asking the bridge chip to # see if card is present or not. # # Drivers may call this routine from an interrupt context. Drivers # may assume this call is relatively inexpensive. Bridge drivers # that implement this call should endeavor to make this inexpensive. # METHOD int child_present { device_t dev; device_t child; } DEFAULT bus_generic_child_present; # # Ask the bridge if this instance of a device can be removed. Drivers # may call this at any time. The bus code must guarantee that the # value returned from this function is invariant on a per instance # basis so drivers may cache the results. # # Drivers do not necessarily know that a bus supports device removal # based on the attachment. PCI has both hot-plug and non-hot-plug # variants, for example. # METHOD int is_removable { device_t dev; device_t child; } DEFAULT bus_generic_is_removable; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 20:29:39 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 20:29:37 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (SHW2-220.accesscable.net [24.71.145.220]) by hub.freebsd.org (Postfix) with ESMTP id 253FC37B400 for ; Thu, 4 Jan 2001 20:29:37 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.1/8.11.1) with ESMTP id f054SF532766 for ; Fri, 5 Jan 2001 00:28:15 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 5 Jan 2001 00:28:15 -0400 (AST) From: The Hermit Hacker To: Subject: using -pthread causes mcopidl to seg fault ... 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 morning all ... running 5.0-CURRENT here, and found the other day that mcopidl started to segfault the other day in kdelibs (from CVS) ... this evening, someone brought up the possibility that its a threading issue, and suggested taking -pthread out of the compile to see if it fixes it ... it did. are there any known problems with -pthread in 5.0-CURRENT right now? anything I can do to debug it (a gdb trace of the core file shows zip) ... 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 Jan 4 20:38:24 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 20:38:20 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 8C83737B402 for ; Thu, 4 Jan 2001 20:38:19 -0800 (PST) Received: (qmail 19938173 invoked from network); 5 Jan 2001 04:38:17 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 5 Jan 2001 04:38:17 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id f054cGN03464; Fri, 5 Jan 2001 05:38:17 +0100 (CET) (envelope-from root) From: Cyrille Lefevre Message-Id: <200101050438.f054cGN03464@gits.dyndns.org> Subject: Re: bin/19635: add -c for grand total to df(1), like du(1) does To: freebsd-stable@FreeBSD.org, freebsd-current@FreeBSD.org Date: Fri, 5 Jan 2001 05:38:16 +0100 (CET) Cc: will@FreeBSD.org Reply-To: clefevre@citeweb.net Organization: ACME X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C 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 hi everybody and Happy New Year, anybody to commit http://www.FreeBSD.org/cgi/query-pr.cgi?pr=19635 ? one of the reasons it was not commited was due to an overflow problem which has been fixed since. thanks by advance.. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 20:52:36 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 20:52:34 2001 Return-Path: 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 2399F37B400 for ; Thu, 4 Jan 2001 20:52:34 -0800 (PST) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id XAA27979; Thu, 4 Jan 2001 23:52:06 -0500 (EST) Date: Thu, 4 Jan 2001 23:52:06 -0500 (EST) From: Daniel Eischen To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: using -pthread causes mcopidl to seg fault ... 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 Fri, 5 Jan 2001, The Hermit Hacker wrote: > > morning all ... > > running 5.0-CURRENT here, and found the other day that mcopidl > started to segfault the other day in kdelibs (from CVS) ... this evening, > someone brought up the possibility that its a threading issue, and > suggested taking -pthread out of the compile to see if it fixes it ... it > did. > > are there any known problems with -pthread in 5.0-CURRENT right > now? anything I can do to debug it (a gdb trace of the core file shows > zip) ... Yeah, threaded C++ apps that make use of libstdc++ are borken in both -current and -stable. See the stable mailing list and search for C++ and/or mozilla. You can probably get around the problem by explicitly linking with -lgcc_r. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 21:57: 7 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 21:57:02 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id D2C0837B400; Thu, 4 Jan 2001 21:57:01 -0800 (PST) Received: from dual.pozo.com (dual.pozo.com [216.101.162.51]) by pozo.com (8.11.1/8.11.1) with ESMTP id f055tvl01980; Thu, 4 Jan 2001 21:55:57 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <5.0.2.1.2.20010104215541.00a63c38@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Version 5.0.2 Date: Thu, 04 Jan 2001 21:55:57 -0800 To: Jake Burkholder From: Manfred Antar Subject: Re: Continuing Fatal Trap 12 Cc: current@freebsd.org;, smp@freebsd.org;, tomdean@speakeasy.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jake I applied the patch: #define LPT_DEBUG=20 =20 --- lpt.c Thu Dec 7 17:33:12 2000=20 +++ lpt.c.hack Thu Jan 4 00:46:41 2001=20 @@ -394,6 +394,7 @@=20 /* retrieve the ppbus irq */=20 BUS_READ_IVAR(ppbus, dev, PPBUS_IVAR_IRQ, &irq);=20 =20 +#if 0=20 if (irq > 0) {=20 /* declare our interrupt handler */=20 sc->intr_resource =3D bus_alloc_resource(dev, SYS_RES_IRQ,=20 @@ -403,9 +404,12 @@=20 sc->sc_irq =3D LP_HAS_IRQ | LP_USE_IRQ | LP_ENABLE_IRQ;=20 device_printf(dev, "Interrupt-driven port\n");=20 } else {=20 +#endif=20 sc->sc_irq =3D 0;=20 device_printf(dev, "Polled port\n");=20 +#if 0=20 }=20 +#endif=20 lprintf(("irq %x %x\n", irq, sc->sc_irq));=20 =20 lpt_release_ppbus(dev);=20 And now printing seems to work fine under SMP Just alot of debbuging stuff when I print : Jan 4 21:52:45 pozo /boot/kernel/kernel:= ppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppppp= pppppppppppppppp Jan 4 21:52:45 pozo /boot/kernel/kernel: pppppppppclosed. Jan 4 21:52:45 pozo /boot/kernel/kernel: pppppppppclosed. Manfred =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D || null@pozo.com || || Ph. (415) 681-6235 || =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 22:21:58 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 22:21:54 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 3F11537B400; Thu, 4 Jan 2001 22:21:53 -0800 (PST) Received: from bissau-07.budapest.interware.hu ([195.70.53.135] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14EQG5-0008MS-00; Fri, 05 Jan 2001 07:21:50 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A5567A7.A11F47E3@elischer.org> Date: Thu, 04 Jan 2001 22:20:23 -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: net@freebsd.org, current@freebsd.org Subject: HEADSUP! New netgraph code coming Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a largely rewritten version of netgraph ready for commit. It is redesigned to work in an SMP "ouside the BGL" environment. I have not completed it to the stage yet that it will run without BGL yet but it's close and it's running stably. I hope to commit this in about 24 hours (maybe less) the files concerned are: julian@jules:grep Index: /tmp/xx Index: sys/dev/lmc/if_lmc.c Index: sys/dev/usb/udbp.c Index: sys/i386/isa/if_ar.c Index: sys/i386/isa/if_sr.c Index: sys/i4b/driver/i4b_ing.c Index: sys/pci/if_mn.c Index: sys/dev/musycc/musycc.c Index: sys/netgraph/netgraph.h Index: sys/netgraph/ng_UI.c Index: sys/netgraph/ng_async.c Index: sys/netgraph/ng_base.c Index: sys/netgraph/ng_bpf.c Index: sys/netgraph/ng_bridge.c Index: sys/netgraph/ng_cisco.c Index: sys/netgraph/ng_echo.c Index: sys/netgraph/ng_ether.c Index: sys/netgraph/ng_frame_relay.c Index: sys/netgraph/ng_hole.c Index: sys/netgraph/ng_iface.c Index: sys/netgraph/ng_ksocket.c Index: sys/netgraph/ng_lmi.c Index: sys/netgraph/ng_message.h Index: sys/netgraph/ng_mppc.c Index: sys/netgraph/ng_one2many.c Index: sys/netgraph/ng_ppp.c Index: sys/netgraph/ng_pppoe.c Index: sys/netgraph/ng_pptpgre.c Index: sys/netgraph/ng_rfc1490.c Index: sys/netgraph/ng_sample.c Index: sys/netgraph/ng_socket.c Index: sys/netgraph/ng_tee.c Index: sys/netgraph/ng_tty.c Index: sys/netgraph/ng_vjc.c -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 22:50:45 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 22:50:43 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 98BDF37B400 for ; Thu, 4 Jan 2001 22:50:42 -0800 (PST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:i5YJrBViwLH0F6gjy8rPtd1FCxp3o13k@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.11.0/3.7Wpl2) with ESMTP id f056oUH10455 for ; Fri, 5 Jan 2001 15:50:30 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:/F1F1u41C83GsWpnN6TBOKKa0vIFAX/E@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id PAA11958; Fri, 5 Jan 2001 15:58:09 +0900 (JST) Message-Id: <200101050658.PAA11958@zodiac.mech.utsunomiya-u.ac.jp> To: freebsd-current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: mtx_destroy() and MTX_COLD Date: Fri, 05 Jan 2001 15:58:08 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In order to declare a mutex which will be used before malloc(9) becomes available in the kernel, MUTEX_DECLARE() should be used, then it should be initialized by passing the MTX_COLD flag to mtx_init(), so that a statically allocated buffer will be used, instead of malloc()ing a buffer, right? Will it be safe to call mtx_destroy() for this mutex? /sys/kern/kern_mutex.c:mtx_destroy() seems to always try to free() the buffer... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 22:59:56 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 22:59:54 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (dhcp244.osd.bsdi.com [204.216.28.244]) by hub.freebsd.org (Postfix) with ESMTP id EE74437B400 for ; Thu, 4 Jan 2001 22:59:53 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.1/8.11.1) with ESMTP id f057Bst03427; Thu, 4 Jan 2001 23:11:55 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200101050711.f057Bst03427@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nicolas Souchu Cc: Andrew Kenneth Milton , freebsd-current@freebsd.org Subject: Re: turning off vga_pci In-reply-to: Your message of "Wed, 03 Jan 2001 19:28:53 +0100." <20010103192853.C22841@wiliam.alcove-int> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 04 Jan 2001 23:11:54 -0800 From: Mike Smith Sender: msmith@mass.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, Dec 30, 2000 at 03:13:24AM +1000, Andrew Kenneth Milton wrote: > > Is there a nice way to stop vga_pci from attaching to my video card, = or > > to allow another driver to attach to it after vga_pci has done its th= ing? > > = > > At the moment I'm removing all traces of vga_pci from the Makefile in= > > my kernel 'compile' directory (which works)... > = > Just remove the vga_pci entry in sys/conf/files. vga_pci is actually more of a nuisance than anything, and I've no = objections to seeing it removed (or doing it myself for that matter). = All the good reasons I thought I had for keeping it are long gone. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 4 23:12:44 2001 From owner-freebsd-current@FreeBSD.ORG Thu Jan 4 23:12:42 2001 Return-Path: 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 1017B37B400 for ; Thu, 4 Jan 2001 23:12:42 -0800 (PST) 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 f057COm71417; Thu, 4 Jan 2001 23:12:24 -0800 (PST) (envelope-from jhb@foo.osd.bsdi.com) Received: (from jhb@localhost) by foo.osd.bsdi.com (8.11.1/8.11.0) id f057CIv66169; Thu, 4 Jan 2001 23:12:18 -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: <200101050658.PAA11958@zodiac.mech.utsunomiya-u.ac.jp> Date: Thu, 04 Jan 2001 23:12:18 -0800 (PST) Organization: BSD, Inc. From: John Baldwin To: Kazutaka YOKOTA Subject: RE: mtx_destroy() and MTX_COLD Cc: freebsd-current@FreeBSD.ORG Sender: jhb@foo.osd.bsdi.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-01 Kazutaka YOKOTA wrote: > In order to declare a mutex which will be used before malloc(9) > becomes available in the kernel, MUTEX_DECLARE() should be used, then > it should be initialized by passing the MTX_COLD flag to mtx_init(), > so that a statically allocated buffer will be used, instead of > malloc()ing a buffer, right? Yes. > Will it be safe to call mtx_destroy() for this mutex? > /sys/kern/kern_mutex.c:mtx_destroy() seems to always try to free() the > buffer... No, the assumption is that anything that comes before malloc is so critical that it won't be destroyed, and thus one shouldn't have to worry about this. If you have a mutex that is used before malloc() and needs to be destroy'd (doing so won't free any memory, the mutex is already statically allocated) then mtx_destroy() could be taught to handle MTX_COLD being passed in, but I'd be surprised that such a mutex exists.. > Kazu -- 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 Jan 5 0:37:48 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 00:37:45 2001 Return-Path: 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 854DD37B400 for ; Fri, 5 Jan 2001 00:37:45 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 5 Jan 2001 00:36:03 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id f058bhc25881 for freebsd-current@freebsd.org; Fri, 5 Jan 2001 00:37:43 -0800 (PST) (envelope-from cjc) Date: Fri, 5 Jan 2001 00:37:43 -0800 From: "Crist J. Clark" To: freebsd-current@freebsd.org Subject: buildworld Problems at NTP Message-ID: <20010105003743.P95729@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: cjc@rfx-64-6-211-149.users.reflexcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having a really weird problem trying to buildworld on a CURRENT box. The build starts just fine and gets though the first three steps. When it gets to building everything, it plows right along until it hits usr.sbin/ntp/ntpd, ===> usr.sbin/ntp/libparse cc -O -pipe -I/usr/src/usr.sbin/ntp/libparse/../../../contrib/ntp/include -I/usr/src/usr.sbin/ntp/libparse/../ -DSYS_FREEBSD -DPARSE -DHAVE_CONFIG_H -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/ntp/libparse/../../../contrib/ntp/libparse/parse.c -o parse.o . . . ===> usr.sbin/ntp/ntpd Killed What is happening is that the system is killing off the make process because it starts to swell up so much it consumes all swap. Here is the dmesg, Jan 4 15:21:08 bubbles /boot/kernel/kernel: swap_pager: out of swap space Jan 4 15:21:09 bubbles /boot/kernel/kernel: swap_pager_getswapspace: failed Jan 4 15:21:19 bubbles /boot/kernel/kernel: pid 11799 (make), uid 0, was killed: out of swap space Jan 4 15:21:22 bubbles /boot/kernel/kernel: pid 9428 (make), uid 0, was killed: out of swap space Jan 4 15:21:22 bubbles /boot/kernel/kernel: pid 58084 (make), uid 0, was killed: out of swap space Jan 4 15:21:22 bubbles /boot/kernel/kernel: pid 44119 (make), uid 0, was killed: out of swap space Jan 4 15:21:22 bubbles /boot/kernel/kernel: pid 12418 (make), uid 0, was killed: out of swap space I've nuked the /usr/obj tree and started over to get the same result. I took out /usr/src/contrib/ntp and re-cvsup'ed, but the above was the result. I'd really like to get this working so I can play with some kernel mods I made last week. Any ideas? Oh, the hardware is a Pentium 133 with 32MB RAM and 100 MB of swap. Copyright (c) 1992-2000 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 #11: Wed Dec 13 23:14:41 PST 2000 cjc@bubbles.cjclark.org:/usr/obj/usr/src/sys/BUBBLES Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P54C (132.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping = 11 Features=0x1bf real memory = 33554432 (32768K bytes) avail memory = 30126080 (29420K bytes) Preloaded elf kernel "kernel" at 0xc02aa000. Intel Pentium detected, installing workaround for F00F bug I had been building CURRENT fine for the two months I've had it. Thanks. -- 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 Fri Jan 5 0:45:10 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 00:45:09 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from dante.naver.co.id (unknown [202.155.86.82]) by hub.freebsd.org (Postfix) with ESMTP id B1CC637B400 for ; Fri, 5 Jan 2001 00:45:08 -0800 (PST) Received: by dante.naver.co.id (Postfix, from userid 1000) id 2B7B16113D; Fri, 5 Jan 2001 15:45:03 +0700 (JAVT) Date: Fri, 5 Jan 2001 15:45:03 +0700 From: John Indra To: freebsd-current@freebsd.org Subject: Re: buildworld Problems at NTP Message-ID: <20010105154503.E508@naver.co.id> Mail-Followup-To: freebsd-current@freebsd.org References: <20010105003743.P95729@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010105003743.P95729@rfx-64-6-211-149.users.reflexco>; from cjclark@reflexnet.net on Fri, Jan 05, 2001 at 12:37:43AM -0800 X-Mailer: Mutt 1.2.5i on FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 12:37:43AM -0800, Crist J. Clark wrote: >I'd really like to get this working so I can play with some kernel >mods I made last week. Any ideas? I've just finished building world and kernel with recent -CURRENT. Didn't encounter any problem though. % uname -a FreeBSD dante.naver.co.id 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Jan 5 13:19:17 JAVT 2001 root@dante.naver.co.id:/usr/obj/usr/src/sys/DANTE i386 /john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 2:11:57 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 02:11:56 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id BDC1D37B402; Fri, 5 Jan 2001 02:11:52 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 14ETqa-0002Tf-00; Fri, 05 Jan 2001 11:11:44 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 14ETqY-0000Ed-00; Fri, 05 Jan 2001 11:11:42 +0100 Date: Fri, 5 Jan 2001 11:11:42 +0100 From: Nicolas Souchu To: Mike Smith Cc: Andrew Kenneth Milton , freebsd-current@freebsd.org Subject: Re: turning off vga_pci Message-ID: <20010105111142.A875@wiliam.alcove-int> References: <20010103192853.C22841@wiliam.alcove-int> <200101050711.f057Bst03427@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <200101050711.f057Bst03427@mass.osd.bsdi.com>; from msmith@freebsd.org on Thu, Jan 04, 2001 at 11:11:54PM -0800 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 04, 2001 at 11:11:54PM -0800, Mike Smith wrote: > > On Sat, Dec 30, 2000 at 03:13:24AM +1000, Andrew Kenneth Milton wrote: > > > Is there a nice way to stop vga_pci from attaching to my video card, or > > > to allow another driver to attach to it after vga_pci has done its thing? > > > > > > At the moment I'm removing all traces of vga_pci from the Makefile in > > > my kernel 'compile' directory (which works)... > > > > Just remove the vga_pci entry in sys/conf/files. > > vga_pci is actually more of a nuisance than anything, and I've no > objections to seeing it removed (or doing it myself for that matter). > All the good reasons I thought I had for keeping it are long gone. Ok, that's on my todo list. -- Nicolas.Souchu@alcove.fr Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 3:17:44 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 03:17:42 2001 Return-Path: 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 F32EB37B400 for ; Fri, 5 Jan 2001 03:17:41 -0800 (PST) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Jan 2001 11:17:41 +0000 (GMT) Date: Fri, 5 Jan 2001 11:17:39 +0000 From: David Malone To: cjclark@alum.mit.edu Cc: freebsd-current@freebsd.org Subject: Re: buildworld Problems at NTP Message-ID: <20010105111739.A50775@walton.maths.tcd.ie> References: <20010105003743.P95729@rfx-64-6-211-149.users.reflexco> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010105003743.P95729@rfx-64-6-211-149.users.reflexco>; from cjclark@reflexnet.net on Fri, Jan 05, 2001 at 12:37:43AM -0800 Sender: dwmalone@maths.tcd.ie Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 12:37:43AM -0800, Crist J. Clark wrote: > What is happening is that the system is killing off the make process > because it starts to swell up so much it consumes all swap. Here is > the dmesg, Were any bits of the compiler killed off? A new test snapshot of gcc was recently added to -current and maybe it's had a strange effect on makedepend or something David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 6:26: 8 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 06:26:03 2001 Return-Path: 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 3C5F937B400; Fri, 5 Jan 2001 06:26:03 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id E76282CE7C; Fri, 5 Jan 2001 16:25:46 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f05EPul00541; Fri, 5 Jan 2001 16:25:56 +0200 (EET) (envelope-from vallo) Date: Fri, 5 Jan 2001 16:25:56 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Cc: gibbs@freebsd.org, msmith@freebsd.org Subject: Lost second channel of AIC-7896 Message-ID: <20010105162556.A454@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.11i Sender: vallo@myhakas.matti.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After upgrading my system from 13'th December to latest -current, the ahc driver doesn't attach to onboard AIC-7896 second channel anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right persons. 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: Fri Jan 5 15:42:56 EET 2001 root@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 = 257298432 (251268K 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 0xc03c5000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03c509c. 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 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga_pci0: mem 0xfd800000-0xfdffffff,0xfe2fc000-0xfe2fffff,0xf2000000-0xf3ffffff irq 16 at device 0.0 on pci1 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 16 at device 11.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs pci0: at 11.1 (no driver attached) pcm0: port 0xed80-0xedbf irq 18 at device 12.0 on pci0 fxp0: port 0xee80-0xeebf mem 0xfe800000-0xfe8fffff,0xfebfd000-0xfebfdfff irq 19 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 17 at device 15.0 on pci0 fxp1: Ethernet address 00:90:27:54:57:26 ed0: port 0xef80-0xef9f irq 18 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) 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 Pciconf: hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71a08086 rev=0x00 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71a18086 rev=0x00 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 none0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00 none1@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 none2@pci0:11:1: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 pcm0@pci0:12:0: class=0x040100 card=0x13711274 chip=0x13711274 rev=0x06 hdr=0x00 fxp0@pci0:13:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 fxp1@pci0:15:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 ed0@pci0:18:0: class=0x020000 card=0x201110b8 chip=0x802910ec rev=0x00 hdr=0x00 vga_pci0@pci1:0:0: class=0x030000 card=0x19f8102b chip=0x0525102b rev=0x03 hdr=0x00 -- 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 Fri Jan 5 6:49:10 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 06:49:07 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 24CDE37B402 for ; Fri, 5 Jan 2001 06:49:07 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f05Emas32202; Fri, 5 Jan 2001 07:48:41 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101051448.f05Emas32202@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: vallo@matti.ee Cc: freebsd-current@freebsd.org Subject: Re: Lost second channel of AIC-7896 In-Reply-To: Your message of "Fri, 05 Jan 2001 16:25:56 +0200." <20010105162556.A454@myhakas.matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jan 2001 07:48:36 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >After upgrading my system from 13'th December to latest -current, >the ahc driver doesn't attach to onboard AIC-7896 second channel >anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right >persons. > >Dmesg: Can you send me the output of "pciconf -l" on this system? My guess is that your MB vendor did not use the correct subsystem ID for the aic7896 to enable the second channel. We only recently started to pay attention to this. What MB is this? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 6:57:14 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 06:57:12 2001 Return-Path: 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 1D2B537B400 for ; Fri, 5 Jan 2001 06:57:12 -0800 (PST) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (Postfix) with ESMTP id 9B3A92CE74; Fri, 5 Jan 2001 16:57:00 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id f05EvAg00852; Fri, 5 Jan 2001 16:57:10 +0200 (EET) (envelope-from vallo) Date: Fri, 5 Jan 2001 16:57:10 +0200 From: Vallo Kallaste To: "Justin T. Gibbs" Cc: freebsd-current@freebsd.org Subject: Re: Lost second channel of AIC-7896 Message-ID: <20010105165710.A825@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <20010105162556.A454@myhakas.matti.ee> <200101051448.f05Emas32202@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <200101051448.f05Emas32202@aslan.scsiguy.com>; from gibbs@scsiguy.com on Fri, Jan 05, 2001 at 07:48:36AM -0700 Sender: vallo@myhakas.matti.ee Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 07:48:36AM -0700, "Justin T. Gibbs" wrote: > Can you send me the output of "pciconf -l" on this system? My guess > is that your MB vendor did not use the correct subsystem ID for the > aic7896 to enable the second channel. We only recently started to > pay attention to this. What MB is this? It's Tyan Thunderbolt, S1837-UANG. hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71a08086 rev=0x00 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71a18086 rev=0x00 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 none0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00 none1@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 none2@pci0:11:1: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 pcm0@pci0:12:0: class=0x040100 card=0x13711274 chip=0x13711274 rev=0x06 hdr=0x00 fxp0@pci0:13:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 fxp1@pci0:15:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 ed0@pci0:18:0: class=0x020000 card=0x201110b8 chip=0x802910ec rev=0x00 hdr=0x00 vga_pci0@pci1:0:0: class=0x030000 card=0x19f8102b chip=0x0525102b rev=0x03 hdr=0x00 -- 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 Fri Jan 5 8: 3:31 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 08:03:28 2001 Return-Path: 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 CB84F37B402 for ; Fri, 5 Jan 2001 08:03:24 -0800 (PST) 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 f05G2fY10694; Fri, 5 Jan 2001 18:02:44 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101051602.f05G2fY10694@gratis.grondar.za> To: David Malone Cc: cjclark@alum.mit.edu, freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP References: <20010105111739.A50775@walton.maths.tcd.ie> In-Reply-To: <20010105111739.A50775@walton.maths.tcd.ie> ; from David Malone "Fri, 05 Jan 2001 11:17:39 GMT." Date: Fri, 05 Jan 2001 18:02:30 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jan 05, 2001 at 12:37:43AM -0800, Crist J. Clark wrote: > > > What is happening is that the system is killing off the make process > > because it starts to swell up so much it consumes all swap. Here is > > the dmesg, > > Were any bits of the compiler killed off? A new test snapshot of gcc > was recently added to -current and maybe it's had a strange effect on > makedepend or something There was a make(1) problem a couple of weeks back. Resup, make-and-install make(1), and you should be OK. Dunno why, but ntp(d) tickled the bug. 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 Fri Jan 5 15:32:54 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 15:32:51 2001 Return-Path: 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 EB20D37B400 for ; Fri, 5 Jan 2001 15:32:50 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 5 Jan 2001 15:30:53 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id f05NWR530992; Fri, 5 Jan 2001 15:32:27 -0800 (PST) (envelope-from cjc) Date: Fri, 5 Jan 2001 15:32:27 -0800 From: "Crist J. Clark" To: Mark Murray Cc: David Malone , freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP Message-ID: <20010105153227.A30927@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010105111739.A50775@walton.maths.tcd.ie> <200101051602.f05G2fY10694@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200101051602.f05G2fY10694@gratis.grondar.za>; from mark@grondar.za on Fri, Jan 05, 2001 at 06:02:30PM +0200 Sender: cjc@rfx-64-6-211-149.users.reflexcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 06:02:30PM +0200, Mark Murray wrote: > > On Fri, Jan 05, 2001 at 12:37:43AM -0800, Crist J. Clark wrote: > > > > > What is happening is that the system is killing off the make process > > > because it starts to swell up so much it consumes all swap. Here is > > > the dmesg, > > > > Were any bits of the compiler killed off? A new test snapshot of gcc > > was recently added to -current and maybe it's had a strange effect on > > makedepend or something > > There was a make(1) problem a couple of weeks back. Resup, make-and-install > make(1), and you should be OK. > > Dunno why, but ntp(d) tickled the bug. To be safe, I nuked the /usr/src/usr.bin/make tree and re-cvsup'ed so I'd checkout new-car-smell-fresh copies. I killed the /usr/obj tree to ensure a clean start there and started a buildworld. Six hours later, ===> usr.sbin/ntp/ntpd Killed And the dmesg, swap_pager: out of swap space swap_pager_getswapspace: failed pid 82558 (make), uid 0, was killed: out of swap space pid 80182 (make), uid 0, was killed: out of swap space pid 28915 (make), uid 0, was killed: out of swap space pid 14928 (make), uid 0, was killed: out of swap space pid 14920 (make), uid 0, was killed: out of swap space pid 83174 (make), uid 0, was killed: out of swap space A note to the first respondant, David Malone, whose attribution seems to hav ebeen lost. As you can see it is all make(1). No other processes are killed off. I've run make with the '-dl' too and make has not spawned anything off just prior to the fatal moment. I've frozen things at after the '==> usr.sbin/ntp/ntpd' but before the kernel starts reaping processes and it is a big, fat make process eating memory. Any more ideas what to try here? -- 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 Fri Jan 5 15:54:35 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 15:54:32 2001 Return-Path: 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 865C937B402 for ; Fri, 5 Jan 2001 15:54:26 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 9DDFD3E0C; Fri, 5 Jan 2001 15:54:25 -0800 (PST) Received: from unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 9CAE13C10A; Fri, 5 Jan 2001 15:54:25 -0800 (PST) To: cjclark@alum.mit.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP In-Reply-To: Message from "Crist J. Clark" of "Fri, 05 Jan 2001 15:32:27 PST." <20010105153227.A30927@rfx-64-6-211-149.users.reflexco> Date: Fri, 05 Jan 2001 15:54:20 -0800 From: Dima Dorfman Message-Id: <20010105235425.9DDFD3E0C@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any more ideas what to try here? I'm sure you already thought of this, but have you made sure that you aren't running any memory-hogging applications? I just compiled all the ntp programs on my laptop which is a Pentium 75 with 24MB of memory and 64MB of swap (I didn't do an entire buildworld; I don't really want to wait a day). It's running 5.0-20001223-CURRENT, and compiled the ntp suite from 5.0-20010101-CURRENT. Hope this helps 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 Fri Jan 5 16:44:25 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 16:44:22 2001 Return-Path: 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 C2E8737B400 for ; Fri, 5 Jan 2001 16:44:22 -0800 (PST) Received: from rfx-64-6-211-149.users.reflexcom.com ([64.6.211.149]) by mailhost01.reflexnet.net with Microsoft SMTPSVC(5.5.1877.197.19); Fri, 5 Jan 2001 16:42:40 -0800 Received: (from cjc@localhost) by rfx-64-6-211-149.users.reflexcom.com (8.11.0/8.11.0) id f060P1331290; Fri, 5 Jan 2001 16:25:01 -0800 (PST) (envelope-from cjc) Date: Fri, 5 Jan 2001 16:24:56 -0800 From: "Crist J. Clark" To: Dima Dorfman Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP Message-ID: <20010105162456.A31261@rfx-64-6-211-149.users.reflexco> Reply-To: cjclark@alum.mit.edu References: <20010105235425.9DDFD3E0C@bazooka.unixfreak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20010105235425.9DDFD3E0C@bazooka.unixfreak.org>; from dima@unixfreak.org on Fri, Jan 05, 2001 at 03:54:20PM -0800 Sender: cjc@rfx-64-6-211-149.users.reflexcom.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 05, 2001 at 03:54:20PM -0800, Dima Dorfman wrote: > > Any more ideas what to try here? > > I'm sure you already thought of this, but have you made sure that you > aren't running any memory-hogging applications? I just compiled all > the ntp programs on my laptop which is a Pentium 75 with 24MB of > memory and 64MB of swap (I didn't do an entire buildworld; I don't > really want to wait a day). It's running 5.0-20001223-CURRENT, and > compiled the ntp suite from 5.0-20010101-CURRENT. Pretty lean on this machine, I make sure to turn off SETI@Home for builds or it'll swap like a maniac. ;) Perhaps I should point out that I am building with sources mounted via NFS, but /usr/obj is local. [170:~] ps uax USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND root 10 99.0 0.0 0 0 ?? RL 13Dec00 1239:51.83 (idle) root 1 0.0 0.5 552 128 ?? ILs 13Dec00 0:00.51 /sbin/init -- root 11 0.0 0.0 0 0 ?? WL 13Dec00 11:00.26 (swi1: net) root 12 0.0 0.0 0 0 ?? WL 13Dec00 178:01.38 (swi6: clock) root 13 0.0 0.0 0 0 ?? WL 13Dec00 0:00.00 (swi4: vm) root 14 0.0 0.0 0 0 ?? DL 13Dec00 11:48.92 (random) root 15 0.0 0.0 0 0 ?? WL 13Dec00 0:00.00 (swi5: task queue) root 16 0.0 0.0 0 0 ?? WL 13Dec00 52:22.08 (irq14: ata0) root 17 0.0 0.0 0 0 ?? WL 13Dec00 0:17.18 (irq6: fdc0) root 18 0.0 0.0 0 0 ?? WL 13Dec00 0:00.00 (irq7: ppc0) root 19 0.0 0.0 0 0 ?? WL 13Dec00 0:00.01 (swi0: tty:sio) root 20 0.0 0.0 0 0 ?? WL 13Dec00 28:27.06 (irq10: ep0) root 2 0.0 0.0 0 0 ?? DL 13Dec00 4:16.76 (pagedaemon) root 3 0.0 0.0 0 0 ?? DL 13Dec00 0:00.36 (vmdaemon) root 4 0.0 0.0 0 0 ?? DL 13Dec00 0:28.82 (bufdaemon) root 5 0.0 0.0 0 0 ?? DL 13Dec00 12:45.19 (syncer) root 114 0.0 1.2 932 360 ?? Ss 13Dec00 0:33.22 syslogd -s root 119 0.0 0.5 1252 132 ?? Is 13Dec00 0:09.18 timed root 126 0.0 0.0 208 0 ?? IW - 0:00.00 nfsiod -n 4 root 127 0.0 0.0 208 0 ?? IW - 0:00.00 nfsiod -n 4 root 128 0.0 0.0 208 0 ?? IW - 0:00.00 nfsiod -n 4 root 129 0.0 0.0 208 0 ?? IW - 0:00.00 nfsiod -n 4 root 147 0.0 0.9 996 248 ?? Ss 13Dec00 0:37.23 cron root 150 0.0 1.6 2648 476 ?? Is 13Dec00 0:05.21 /usr/sbin/sendmail -q30m root 154 0.0 0.9 2192 248 ?? Is 13Dec00 0:34.69 /usr/sbin/sshd root 198 0.0 0.0 948 0 d0 IWs+ - 0:00.00 /usr/libexec/getty std.115200 ttyd0 root 48855 0.0 1.5 2280 448 ?? S 10:02AM 0:02.85 sshd: cjc@ttyp0 (sshd) cjc 48877 0.0 2.7 1412 788 p0 Ss 10:02AM 0:01.35 -tcsh (tcsh) root 0 0.0 0.0 0 0 ?? DLs 13Dec00 0:10.73 (swapper) cjc 83227 0.0 1.2 520 336 p0 R+ 4:15PM 0:00.00 ps uax [171:~] swapinfo Device 1K-blocks Used Avail Capacity Type /dev/rad0s1b 102272 2104 100168 2% Interleaved [172:~] vmstat procs memory page disks faults cpu r b w avm fre flt re pi po fr sr ad0 ac0 in sy cs us sy id 1 0 0 4632 14236 24 0 0 0 26 21 0 0 225 50 265 95 1 4 [173:~] uname -a FreeBSD bubbles.cjclark.org 5.0-CURRENT FreeBSD 5.0-CURRENT #11: Wed Dec 13 23:14:41 PST 2000 cjc@bubbles.cjclark.org:/usr/obj/usr/src/sys/BUBBLES i386 Sources for the existing system would be from 2000/12/09. Again, the one I am trying to build has been re-cvsup'ed several times the last being about 0830 PST today. -- 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 Fri Jan 5 16:51:56 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 16:51:50 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 41F4B37B400; Fri, 5 Jan 2001 16:51:49 -0800 (PST) Received: from victoria-060.budapest.interware.hu ([195.70.63.60] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14EhaE-0007Ej-00; Sat, 06 Jan 2001 01:51:47 +0100 Sender: julian@FreeBSD.ORG Message-ID: <3A566BCB.BFD6FA2D@elischer.org> Date: Fri, 05 Jan 2001 16:50:19 -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: net@freebsd.org, current@freebsd.org Subject: Re: HEADSUP! New netgraph code coming References: <3A5567A7.A11F47E3@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 This has been committed. People with unusual netgraph usage should contact me for assistance if things fail. In particular I would like to get some more pppoe users to try it as I haven't convinced myself it's tested enough. For the Netgraph-aware, the following changes have been made. 1/ data and contol-messages are now delivered as part of a larger entity called an 'item'. Thus the prototypes for these methods has changed and the code must be changed to free this (or not) as required. 2/ piggyback responses have been removed, The new response method is almost as quick and much cleaner. 3/ All nodes have queues into which items are place IFF there is lock contention and teh data cannot be processed immediatly. I expect the code to be a LITLE shaky for a few days around the time when nodes are deleted. but operation seems solid. Julian Elischer wrote: > > I have a largely rewritten version of netgraph > ready for commit. > It is redesigned to work in an SMP "ouside the BGL" environment. > I have not completed it to the stage yet that it will run > without BGL yet but it's close and it's running stably. > > I hope to commit this in about 24 hours (maybe less) > > the files concerned are: > > julian@jules:grep Index: /tmp/xx > Index: sys/dev/lmc/if_lmc.c > Index: sys/dev/usb/udbp.c > Index: sys/i386/isa/if_ar.c > Index: sys/i386/isa/if_sr.c > Index: sys/i4b/driver/i4b_ing.c > Index: sys/pci/if_mn.c > Index: sys/dev/musycc/musycc.c > Index: sys/netgraph/netgraph.h > Index: sys/netgraph/ng_UI.c > Index: sys/netgraph/ng_async.c > Index: sys/netgraph/ng_base.c > Index: sys/netgraph/ng_bpf.c > Index: sys/netgraph/ng_bridge.c > Index: sys/netgraph/ng_cisco.c > Index: sys/netgraph/ng_echo.c > Index: sys/netgraph/ng_ether.c > Index: sys/netgraph/ng_frame_relay.c > Index: sys/netgraph/ng_hole.c > Index: sys/netgraph/ng_iface.c > Index: sys/netgraph/ng_ksocket.c > Index: sys/netgraph/ng_lmi.c > Index: sys/netgraph/ng_message.h > Index: sys/netgraph/ng_mppc.c > Index: sys/netgraph/ng_one2many.c > Index: sys/netgraph/ng_ppp.c > Index: sys/netgraph/ng_pppoe.c > Index: sys/netgraph/ng_pptpgre.c > Index: sys/netgraph/ng_rfc1490.c > Index: sys/netgraph/ng_sample.c > Index: sys/netgraph/ng_socket.c > Index: sys/netgraph/ng_tee.c > Index: sys/netgraph/ng_tty.c > Index: sys/netgraph/ng_vjc.c e -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 17:47:14 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 17:47:12 2001 Return-Path: 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 1D87637B400 for ; Fri, 5 Jan 2001 17:47:12 -0800 (PST) Received: by bazooka.unixfreak.org (Postfix, from userid 1000) id 647F63E0C; Fri, 5 Jan 2001 17:47:11 -0800 (PST) Received: from unixfreak.org (localhost [127.0.0.1]) by bazooka.unixfreak.org (Postfix) with ESMTP id 6332B3C10A; Fri, 5 Jan 2001 17:47:11 -0800 (PST) To: cjclark@alum.mit.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP In-Reply-To: Message from "Crist J. Clark" of "Fri, 05 Jan 2001 16:24:56 PST." <20010105162456.A31261@rfx-64-6-211-149.users.reflexco> Date: Fri, 05 Jan 2001 17:47:06 -0800 From: Dima Dorfman Message-Id: <20010106014711.647F63E0C@bazooka.unixfreak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jan 05, 2001 at 03:54:20PM -0800, Dima Dorfman wrote: > > > Any more ideas what to try here? > > > > I'm sure you already thought of this, but have you made sure that you > > aren't running any memory-hogging applications? I just compiled all > > the ntp programs on my laptop which is a Pentium 75 with 24MB of > > memory and 64MB of swap (I didn't do an entire buildworld; I don't > > really want to wait a day). It's running 5.0-20001223-CURRENT, and > > compiled the ntp suite from 5.0-20010101-CURRENT. > > Pretty lean on this machine, I make sure to turn off SETI@Home for > builds or it'll swap like a maniac. ;) Perhaps I should point out that > I am building with sources mounted via NFS, but /usr/obj is local. For the tests I described above, the equivalents (i.e., I used different paths) of /usr/src and /usr/obj were both on NFS-mounted filesysems. If anything, this should makes things easier on the build host, provided that the NFS subsystem doesn't puke, of course. > [170:~] ps uax I don't see anything abnormal here. If you just want to get this stuff built, you might try adding more swap using the vn(4) driver. As to why make is getting killed, however, I'm at a loss. Although it shouldn't matter, you might try rebooting. This is current, after all, and as such it's not immune to weird bugs. 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 Fri Jan 5 21:12:27 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 21:12:26 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from cmr0.ash.ops.us.uu.net (cmr0.ash.ops.us.uu.net [198.5.241.38]) by hub.freebsd.org (Postfix) with ESMTP id 524E537B400 for ; Fri, 5 Jan 2001 21:12:25 -0800 (PST) Received: from neserve0.corp.us.uu.net by cmr0.ash.ops.us.uu.net with ESMTP (peer crosschecked as: neserve0.corp.us.uu.net [153.39.92.148]) id QQjwtg26354 for ; Sat, 6 Jan 2001 05:12:24 GMT Received: from localhost by neserve0.corp.us.uu.net with ESMTP (peer crosschecked as: rayhicks@localhost) id QQjwtg14547 for ; Sat, 6 Jan 2001 00:12:24 -0500 (EST) Date: Sat, 6 Jan 2001 00:12:24 -0500 (EST) From: Raymond Hicks X-Sender: rayhicks@neserve0.corp.us.uu.net To: current@freebsd.org Subject: CURRENT breaks some apps 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 have had a problem with running infobot after my recent cvsup to current. I have heard that there is a problem with the newer perl version.. is this a result of that? Here is error: deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near ">>> $b" Missing braces on \N{} at ./src/Irc.pl line 133, near ">>> $b" Missing braces on \N{} at ./src/Irc.pl line 152, within string Compilation failed in require at ./infobot line 39. BEGIN failed--compilation aborted at ./infobot line 42. and here is perl -v deepwoods# perl -v This is perl, v5.6.0 built for i386-freebsd (with 1 registered patch, see perl -V for more detail) I am not sure if it is true regarding perl so I though it prudent to ask... perhaps I should have stayed STABLE on this box but dont think that it is possible to go backwords with the simplicity of going fowards... regards raymond hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 5 22:52:36 2001 From owner-freebsd-current@FreeBSD.ORG Fri Jan 5 22:52:33 2001 Return-Path: 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 0E7B037B400 for ; Fri, 5 Jan 2001 22:52:30 -0800 (PST) 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 f066pvY15587; Sat, 6 Jan 2001 08:51:59 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200101060651.f066pvY15587@gratis.grondar.za> To: cjclark@alum.mit.edu Cc: David Malone , freebsd-current@FreeBSD.ORG Subject: Re: buildworld Problems at NTP References: <20010105153227.A30927@rfx-64-6-211-149.users.reflexco> In-Reply-To: <20010105153227.A30927@rfx-64-6-211-149.users.reflexco> ; from "Crist J. Clark" "Fri, 05 Jan 2001 15:32:27 PST." Date: Sat, 06 Jan 2001 08:51:41 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There was a make(1) problem a couple of weeks back. Resup, make-and-install > > make(1), and you should be OK. > > > > Dunno why, but ntp(d) tickled the bug. > > To be safe, I nuked the /usr/src/usr.bin/make tree and re-cvsup'ed so > I'd checkout new-car-smell-fresh copies. I killed the /usr/obj tree to > ensure a clean start there and started a buildworld. Six hours later, > > ===> usr.sbin/ntp/ntpd > Killed Read what I said!! Make-and-install _make_ (not anything else) first. 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 Jan 6 8:25:47 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 08:25:44 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from smtpgate1.syd.iprimus.com.au (smtpgate1.syd.iprimus.com.au [203.134.64.91]) by hub.freebsd.org (Postfix) with ESMTP id 32E4037B400; Sat, 6 Jan 2001 08:25:43 -0800 (PST) Received: from iprimus.com.au ([203.134.49.250]) by smtpgate1.syd.iprimus.com.au with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 7 Jan 2001 03:26:28 +1100 Message-ID: <3A574677.184C029A@iprimus.com.au> Date: Sun, 07 Jan 2001 03:23:19 +1100 From: Justin Clift X-Mailer: Mozilla 4.75 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: msmith@FreeBSD.org Cc: freebsd-current@freebsd.org Subject: Mylex DAC960 RAID Controller - bus_dmamap_load errors Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Mike, Have you had any errors reported from users lately with Mylex DAC960P RAID Contollers with v2.xx firmware? For the past few hours I have been trying to install various versions of FreeBSD 4.2 (Release version, snapshots right up to yesterdays date, etc) but can never manage to get it installed. I am consistently getting an error message something like "bus_dmamap_load : Too many segs", and then a few seconds later something like "attempted write beyond end of disk". (Please note, this isn't the precise spelling, it's a description from memory hoping you've seen it before - and know how to solve it!). This is occuring when attempting to install the "base" group of FreeBSD, after the initial 'newfs' has successfully done it's thing. I have tried with one Mylex DAC960P PCI controller with firmware 2.73.0.0, and also with an IBM F/W PCI SCSI RAID Adapter with firmware 2.43.0.0 (it's a Mylex DAC960P rebadged by IBM and used in all sorts of equipment). Exactly the same error from both controllers. The PC I'm trying this in is a Pentium III with 160MB RAM, Cirrus Logic GD5446 graphics adapter, and other standard stuff. The hard drives attached to the Mylex card are 2 x 4.3GB Fujitsu UW SCSI drives, set up as a single mirrored pair. It all works fine with NT4, but that's not an option for this server. Regards and best wishes, Justin Clift To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 9:37: 2 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 09:36:59 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mail7.nc.rr.com (fe7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id 1ACF037B400 for ; Sat, 6 Jan 2001 09:36:59 -0800 (PST) Received: from undeniable.detachment.org ([24.25.3.165]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sat, 6 Jan 2001 12:36:57 -0500 Received: from stromberg.org (localhost [::1]) by undeniable.detachment.org (8.9.3+Sun/8.9.3) with ESMTP id MAA02551; Sat, 6 Jan 2001 12:36:13 -0500 (EST) Message-ID: <3A57578C.30203@stromberg.org> Date: Sat, 06 Jan 2001 12:36:12 -0500 From: Thomas Stromberg User-Agent: Mozilla/5.0 (X11; U; SunOS 5.8 sun4u; en-US; m18) Gecko/20010103 X-Accept-Language: en MIME-Version: 1.0 To: Raymond Hicks , freebsd-current@freebsd.org Subject: Re: CURRENT breaks some perl? References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Raymond Hicks wrote: > I have had a problem with running infobot after my recent cvsup to > current. I have heard that there is a problem with the newer perl > version.. is this a result of that? Here is error: > deepwoods# Missing braces on \N{} at ./src/Irc.pl line 131, near ">>> $b" > Missing braces on \N{} at ./src/Irc.pl line 133, near ">>> $b" > Missing braces on \N{} at ./src/Irc.pl line 152, within string > Compilation failed in require at ./infobot line 39. > BEGIN failed--compilation aborted at ./infobot line 42. Welp, hard to help you here since there isn't any version info for the infobot, but.. I am succesfully running a blootbot 1.0.0pre4 (infobot derivative) in -CURRENT, and haven't seen any such problem. If there is indeed a problem with the new perl (which is in -STABLE too I believe), I'm sure it's been fixed by now. Just about every new box that gets rolled out with perl comes with 5.6.0 nowadays.. The only problem I've seen, since ~October? is the ocassional exec bug from backticked execs in perl from the infobot. In this case, it was for ps/tail to find out it's current memory. We just commented out the memory usage check and perl no longer core dumps. Just for reference, here are two of the perl core dumps from November (libc actually!) #0 0x2819e1b8 in kill () from /usr/lib/libc_r.so.5 #1 0x281eb652 in abort () from /usr/lib/libc_r.so.5 #2 0x281b6095 in _thread_exit () from /usr/lib/libc_r.so.5 #3 0x281af4ba in _pq_remove () from /usr/lib/libc_r.so.5 #4 0x281b1d55 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #5 0x0 in ?? () #0 0x2819e184 in getegid () from /usr/lib/libc_r.so.5 #1 0x281eb61e in abort () from /usr/lib/libc_r.so.5 #2 0x281b6015 in _thread_exit () from /usr/lib/libc_r.so.5 #3 0x281af42e in _pq_init () from /usr/lib/libc_r.so.5 #4 0x281b1cd5 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5 #5 0x0 in ?? ()  / Thomas Stromberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 9:51:17 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 09:51:07 2001 Return-Path: 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 2F4B237B402; Sat, 6 Jan 2001 09:51:06 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id f06HoxO75206; Sat, 6 Jan 2001 18:50:59 +0100 (CET) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.11.1/8.11.0) with ESMTP id f06HojO01838; Sat, 6 Jan 2001 18:50:51 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sat, 6 Jan 2001 18:50:45 +0100 (CET) From: Leif Neland To: freebsd-isdn@freebsd.org Cc: freebsd-current@freebsd.org Subject: i4b: I'm missing something in my kernel config. 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 (fbsd-current) I lost my kernel config in august; now I'm trying to make a new. But I must be missing something in my config. I'm getting this from make buildkernel: Script started on Sat Jan 6 15:53:44 2001 gina/usr/src # make -DNOCLEAN buildkernel KERNEL=ARNOLD (I'm getting the same error without NOCLEAN; it's just for getting the typescript) -------------------------------------------------------------- >>> Rebuilding kernel(s) -------------------------------------------------------------- ===> ARNOLD 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/ARNOLD ARNOLD ... cd /usr/obj/usr/src/sys/ARNOLD; MAKEOBJDIRPREFIX=/usr/obj COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.6.0 DESTDIR=/usr/obj/usr/src/i386 INSTALL="sh /usr/src/tools/install.sh" 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 MACHINE=i386 make KERNEL=kernel all linking kernel i4b_ctl.o: In function `i4bctlioctl': i4b_ctl.o(.text+0x131): undefined reference to `i4b_l1_debug' i4b_ctl.o(.text+0x157): undefined reference to `i4b_l1_debug' i4b_l2.o: In function `i4b_ph_activate_ind': i4b_l2.o(.text+0x1ea): undefined reference to `i4b_l1_debug' i4b_l2.o: In function `i4b_ph_deactivate_ind': i4b_l2.o(.text+0x22a): undefined reference to `i4b_l1_debug' i4b_l2.o: In function `i4b_mph_status_ind': i4b_l2.o(.text+0x366): undefined reference to `i4b_l1_debug' i4b_l2.o: In function `i4b_mdl_command_req': i4b_l2.o(.text+0x4f2): undefined reference to `i4b_l1l2_func' i4b_uframe.o: In function `i4b_tx_sabme': i4b_uframe.o(.text+0x422): undefined reference to `i4b_l1l2_func' i4b_uframe.o: In function `i4b_tx_dm': i4b_uframe.o(.text+0x46e): undefined reference to `i4b_l1l2_func' i4b_uframe.o: In function `i4b_tx_disc': i4b_uframe.o(.text+0x4ba): undefined reference to `i4b_l1l2_func' i4b_uframe.o: In function `i4b_tx_ua': i4b_uframe.o(.text+0x506): undefined reference to `i4b_l1l2_func' i4b_uframe.o(.text+0x555): more undefined references to `i4b_l1l2_func' follow *** Error code 1 Stop in /usr/obj/usr/src/sys/ARNOLD. *** Error code 1 Script done on Sat Jan 6 15:55:49 2001 My config is this: machine i386 cpu I586_CPU ident ARNOLD maxusers 32 options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable 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 options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #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 #ktrace(1) support 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 options SHOW_BUSYBUFS device isa device eisa device pci device ncr # NCR/Symbios Logic 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) device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen device splash device sc 1 device npx device pmtimer device sio # 8250, 16[45]50 based serial ports device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device device miibus # MII bus support device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device random # Entropy device options NOBLOCKRANDOM # avoid any blocking on device random device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) device bpf # Berkeley packet filter device sppp #Generic Synchronous PPP options DRN_NGO device "i4bq921" device "i4bq931" device "i4b" device "i4btrc" 4 device "i4bctl" device "i4btel" 2 device "i4bipr" 4 device "i4bisppp" 4 Leif Neland To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 10: 9:14 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 10:09:10 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from hub-wue.franken.de (hub-wue.franken.de [193.141.110.10]) by hub.freebsd.org (Postfix) with ESMTP id 50E8437B400; Sat, 6 Jan 2001 10:09:10 -0800 (PST) Received: from gaspode.franken.de ([193.141.110.4]:34309 "EHLO gaspode.franken.de" ident: "NO-IDENT-SERVICE") by hub-wue.franken.de with ESMTP id <381203-14075>; Sat, 6 Jan 2001 19:09:30 +0100 Received: (from tanis@localhost) by gaspode.franken.de (8.11.1/8.9.3) id f06I97O03616; Sat, 6 Jan 2001 19:09:07 +0100 (CET) (envelope-from tanis) From: German Tischler To: Leif Neland Cc: freebsd-isdn@freebsd.org, freebsd-current@freebsd.org Subject: Re: i4b: I'm missing something in my kernel config. Message-ID: <20010106190907.A3567@gaspode.franken.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from leifn@neland.dk on Sat, Jan 06, 2001 at 06:51:42PM +0100 Date: Sat, 6 Jan 2001 19:09:30 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 06:51:42PM +0100, Leif Neland wrote: > options DRN_NGO > device "i4bq921" > device "i4bq931" > device "i4b" > device "i4btrc" 4 > device "i4bctl" > device "i4btel" 2 > device "i4bipr" 4 > device "i4bisppp" 4 Seems you left out "device isic". --gt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 10:46: 2 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 10:45:59 2001 Return-Path: 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 5266B37B400 for ; Sat, 6 Jan 2001 10:45:59 -0800 (PST) Received: (qmail 4974 invoked by uid 3130); 6 Jan 2001 18:45:58 -0000 Date: Sat, 6 Jan 2001 13:45:58 -0500 From: Garrett Rooney To: Thomas Stromberg Cc: Raymond Hicks , freebsd-current@freebsd.org Subject: Re: CURRENT breaks some perl? Message-ID: <20010106134558.E264@electricjellyfish.net> Mail-Followup-To: Garrett Rooney , Thomas Stromberg , Raymond Hicks , freebsd-current@freebsd.org References: <3A57578C.30203@stromberg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A57578C.30203@stromberg.org>; from thomas@stromberg.org on Sat, Jan 06, 2001 at 12:36:12PM -0500 Sender: rooneg@isris.pair.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 12:36:12PM -0500, Thomas Stromberg wrote: > Welp, hard to help you here since there isn't any version info for the > infobot, but.. I am succesfully running a blootbot 1.0.0pre4 (infobot > derivative) in -CURRENT, and haven't seen any such problem. If there is > indeed a problem with the new perl (which is in -STABLE too I believe), > I'm sure it's been fixed by now. Just about every new box that gets > rolled out with perl comes with 5.6.0 nowadays.. actually, -STABLE as of last night still has 5.005_3. I believe that they are waiting for a new version of perl to fix some known bugs before back porting 5.6 to -STABLE. -- garrett rooney my pid is inigo montoya. rooneg@electricjellyfish.net you kill -9 my parent process. http://electricjellyfish.net/ prepare to vi. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 13: 2:57 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 13:02:55 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from lips.borg.umn.edu (lips.borg.umn.edu [160.94.232.50]) by hub.freebsd.org (Postfix) with ESMTP id 85F0137B402 for ; Sat, 6 Jan 2001 13:02:54 -0800 (PST) Received: from thebarn.com (nic-31-c12-053.mn.mediaone.net [24.31.12.53]) by lips.borg.umn.edu (8.11.1/8.10.1) with ESMTP id f06L2je70046; Sat, 6 Jan 2001 15:02:45 -0600 (CST) Sender: cattelan@thebarn.com Message-ID: <3A5787F5.CDD5E009@thebarn.com> Date: Sat, 06 Jan 2001 15:02:45 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.74 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Justin T. Gibbs" Cc: vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Lost second channel of AIC-7896 References: <200101051448.f05Emas32202@aslan.scsiguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Justin T. Gibbs" wrote: > >After upgrading my system from 13'th December to latest -current, > >the ahc driver doesn't attach to onboard AIC-7896 second channel > >anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right > >persons. > > > >Dmesg: > > Can you send me the output of "pciconf -l" on this system? My guess > is that your MB vendor did not use the correct subsystem ID for the > aic7896 to enable the second channel. We only recently started to > pay > attention to this. What MB is this? My system doesn't find any scsi controllers. Tyan thunder... I think burst[3:02pm]-=>sudo pciconf -l hostb0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x71908086 rev=0x03 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x71918086 rev=0x03 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x71108086 rev=0x02 hdr=0x00 atapci0@pci0:7:1: class=0x010180 card=0x00000000 chip=0x71118086 rev=0x01 hdr=0x00 uhci0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 rev=0x01 hdr=0x00 none0@pci0:7:3: class=0x068000 card=0x00000000 chip=0x71138086 rev=0x02 hdr=0x00 ahc0@pci0:11:0: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 ahc1@pci0:11:1: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 hdr=0x00 fxp0@pci0:13:0: class=0x020000 card=0x000c8086 chip=0x12298086 rev=0x08 hdr=0x00 -- Russell Cattelan cattelan@thebarn.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 15:50:41 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 15:50:40 2001 Return-Path: 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 0C3AF37B400 for ; Sat, 6 Jan 2001 15:50:40 -0800 (PST) Received: by c1030098-a.wtrlo1.ia.home.com (Postfix, from userid 1001) id D1E6014A47; Sat, 6 Jan 2001 17:50:31 -0600 (CST) To: freebsd-current@freebsd.org Subject: broken at if_ray.c Keywords: ray,usr,sys,src,modules,dev,function,card From: Michael Harnois Date: 06 Jan 2001 17:50:30 -0600 Message-ID: <86itnsme9l.fsf@mharnois.workgroup.net> Lines: 17 User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Millennium) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -march=i686 -D_KERNEL -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/dev -I@/../include -mpreferred-stack-boundary=2 -c /usr/src/sys/modules/ray/../../dev/ray/if_ray.c /usr/src/sys/modules/ray/../../dev/ray/if_ray.c: In function `ray_res_alloc_am': /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:3369: too few arguments to function `CARD_SET_MEMORY_OFFSET' card_if.h:44: warning: inlining failed in call to `CARD_SET_MEMORY_OFFSET' /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:3369: warning: called from here /usr/src/sys/modules/ray/../../dev/ray/if_ray.c: In function `ray_res_alloc_cm': /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:3457: too few arguments to function `CARD_SET_MEMORY_OFFSET' *** Error code 1 Stop in /usr/src/sys/modules/ray. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org Paranoids are people, too; they have their own problems. It's easy to criticize, but if everybody hated you, you'd be paranoid too. -- D. J. Hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 15:57:24 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 15:57:22 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 02E5837B400 for ; Sat, 6 Jan 2001 15:57:22 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id f06NvEs55276; Sat, 6 Jan 2001 16:57:14 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200101062357.f06NvEs55276@aslan.scsiguy.com> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Russell Cattelan Cc: vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Lost second channel of AIC-7896 In-Reply-To: Your message of "Sat, 06 Jan 2001 15:02:45 CST." <3A5787F5.CDD5E009@thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Jan 2001 16:57:14 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Can you send me the output of "pciconf -l" on this system? My guess >> is that your MB vendor did not use the correct subsystem ID for the >> aic7896 to enable the second channel. We only recently started to >> pay > >> attention to this. What MB is this? > >My system doesn't find any scsi controllers. Are you sure that your drives aren't just attached to the second port? Have you tried a current since Friday? I committed a fix for the original problem that was reported. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 16: 5:11 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 16:05:09 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C10C537B404 for ; Sat, 6 Jan 2001 16:05:08 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA26739; Sat, 6 Jan 2001 17:04:59 -0700 (MST) (envelope-from ken) Date: Sat, 6 Jan 2001 17:04:59 -0700 From: "Kenneth D. Merry" To: Russell Cattelan Cc: "Justin T. Gibbs" , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Lost second channel of AIC-7896 Message-ID: <20010106170459.A26638@panzer.kdm.org> References: <200101051448.f05Emas32202@aslan.scsiguy.com> <3A5787F5.CDD5E009@thebarn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3A5787F5.CDD5E009@thebarn.com>; from cattelan@thebarn.com on Sat, Jan 06, 2001 at 03:02:45PM -0600 Sender: ken@panzer.kdm.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 06, 2001 at 15:02:45 -0600, Russell Cattelan wrote: > "Justin T. Gibbs" wrote: > > > >After upgrading my system from 13'th December to latest -current, > > >the ahc driver doesn't attach to onboard AIC-7896 second channel > > >anymore. I'm cc'g to Mr. Gibbs and Smith in hope they are the right > > >persons. > > > > > >Dmesg: > > > > Can you send me the output of "pciconf -l" on this system? My guess > > is that your MB vendor did not use the correct subsystem ID for the > > aic7896 to enable the second channel. We only recently started to > > pay > > > attention to this. What MB is this? > > My system doesn't find any scsi controllers. > > Tyan thunder... I think > burst[3:02pm]-=>sudo pciconf -l [ ... ] > ahc0@pci0:11:0: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 > hdr=0x00 > ahc1@pci0:11:1: class=0x010000 card=0x080f9005 chip=0x005f9005 rev=0x00 > hdr=0x00 [ ... ] Looks like you have a 7896 there. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 17: 7:35 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 17:07:17 2001 Return-Path: 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 14C6237B400 for ; Sat, 6 Jan 2001 17:07:17 -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 UAA14929 for ; Sat, 6 Jan 2001 20:07:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f0717F488044; Sat, 6 Jan 2001 20:07:15 -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 Date: Sat, 6 Jan 2001 20:07:15 -0500 (EST) To: freebsd-current@freebsd.org Subject: holy buses & user-level pci access problem X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14935.49104.217145.400932@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When trying to figure out a bizzare failure of the X server on my UP1000, I found a bug in the user-level pci bus code. This machine is rather wacky in that it has 2 busses: 0 and 2. 0 is the pci bus, 2 is the AGP bus, behind the AMD-751 host-pci bridge (pcib1): <...> pcib0: on irongate0 pci0: on pcib0 pcib1: at device 1.0 on pci0 pci2: on pcib1 pci2: at 5.0 isab0: at device 7.0 on pci0 <...> # pciconf -l none0@pci0:0:0: class=0x060000 card=0x00000000 chip=0x70061022 rev=0x25 hdr=0x00 pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x70071022 rev=0x01 hdr=0x01 isab0@pci0:7:0: class=0x060100 card=0x00000000 chip=0x153310b9 rev=0xc3 hdr=0x00 dc0@pci0:9:0: class=0x020000 card=0x500b1011 chip=0x00191011 rev=0x30 hdr=0x00 sym0@pci0:10:0: class=0x010000 card=0x00000000 chip=0x000f1000 rev=0x04 hdr=0x00 fxp0@pci0:11:0: class=0x020000 card=0x00018086 chip=0x12298086 rev=0x02 hdr=0x00 atapci0@pci0:16:0: class=0x0101fa card=0x00000000 chip=0x522910b9 rev=0xc1 hdr=0x00 alpm0@pci0:17:0: class=0x000000 card=0x00000000 chip=0x710110b9 rev=0x00 hdr=0x00 vga_pci0@pci2:5:0: class=0x030000 card=0x0a351048 chip=0x3d07104c rev=0x11 hdr=0x00 # pciconf -r pci2:5:0 0 pciconf: ioctl(PCIOCREAD): Operation not supported by device # pciconf -r pci1:5:0 0 0x3d07104c Wow. Note that by doing PCIOREADs of the DEVVENDOR, the graphics card is found at 1:5:0 and not 2:5:0 -- this confuses the hell out of the XFree86 resource mapping code, since there isn't a bus 1 on this system. It tries to remap the card into the memory space of bus 0 and fails miserably. I've got a special-case hack to the XFree86-4 port that I could commit (lie to the resource code and tell it the bridge is a bridge to bus1), but I'd rather have it fixed correctly. I think this (in sys/dev/pci/pci_user.c) is the culprit: /* * Assume that the user-level bus number is * actually the pciN instance number. We map * from that to the real pcib+bus combination. */ But I'm at a loss as to how to fix this bug and not introduce a binary incompatability by adding a hose field to struct pcisel in pciio.h Can anybody with more newbus fu than me help me out here? Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 17:16:53 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 17:16:36 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 042E237B400 for ; Sat, 6 Jan 2001 17:16:36 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id RAA48958 for ; Sat, 6 Jan 2001 17:16:35 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id f071GZR41032 for freebsd-current@freebsd.org; Sat, 6 Jan 2001 17:16:35 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200101070116.f071GZR41032@curve.dellroad.org> Subject: weird cvs update problem To: freebsd-current@freebsd.org Date: Sat, 6 Jan 2001 17:16:35 -0800 (PST) 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 I have a -current system from Dec. 7 on which I'm trying to do a cvs update in preparation of make world, and am seeing wierd stuff like this: > cvs server: Updating crypto/kerberosIV/appl/afsutil > U crypto/kerberosIV/appl/afsutil/Makefile.in > U crypto/kerberosIV/appl/afsutil/aklog.c > U crypto/kerberosIV/appl/afsutil/kstring2key.c > U crypto/kerberosIV/appl/afsutil/pagsh.c > cvs server: Updating crypto/kerberosIV/appl/bsd > U crypto/kerberosIV/appl/bsd/Makefile.in > U crypto/kerberosIV/appl/bsd/README.login > U crypto/kerberosIV/appl/bsd/bsd_locl.h > U crypto/kerberosIV/appl/bsd/encrypt.c > U crypto/kerberosIV/appl/bsd/forkpty.c > U crypto/kerberosIV/appl/bsd/kcmd.c > U crypto/kerberosIV/appl/bsd/klogin.c > U crypto/kerberosIV/appl/bsd/krcmd.c > U crypto/kerberosIV/appl/bsd/login.c > U crypto/kerberosIV/appl/bsd/login_access.c > U crypto/kerberosIV/appl/bsd/login_fbtab.c > U crypto/kerberosIV/appl/bsd/osfc2.c > U crypto/kerberosIV/appl/bsd/pathnames.h_ > U crypto/kerberosIV/appl/bsd/rcmd_util.c > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > cvs update: warning: unrecognized response ` */' from cvs server > cvs update: warning: unrecognized response `' from cvs server > cvs update: warning: unrecognized response `void' from cvs server > cvs update: warning: unrecognized response `ip_options_and_die (int sock, struct sockaddr_in *fromp)' from cvs server > cvs update: warning: unrecognized response `{' from cvs server > cvs update: warning: unrecognized response `#if defined(IP_OPTIONS) && defined(HAVE_GETSOCKOPT)' from cvs server > cvs update: warning: unrecognized response ` u_char optbuf[BUFSIZ/3], *cp;' from cvs server > cvs update: warning: unrecognized response ` char lbuf[BUFSIZ], *lp;' from cvs server The file data is somehow getting mixed into the "control stream" or something. The cvs server is a 5.0-20000506-CURRENT machine that has been working fine for many months (and I don't see the same problem when cvs updating from other machines). I notice that "cvs" was updated to version 1.11 on 10/31/00... Has anyone else seen this, and if so, what's the fix?? Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 17:26:54 2001 From owner-freebsd-current@FreeBSD.ORG Sat Jan 6 17:26:37 2001 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A37A837B400 for ; Sat, 6 Jan 2001 17:26:36 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA28960; Sat, 6 Jan 2001 17:26:30 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.1/8.11.0) id f071QT512153; Sat, 6 Jan 2001 17:26:29 -0800 (PST) (envelope-from jdp) Date: Sat, 6 Jan 2001 17:26:29 -0800 (PST) Message-Id: <200101070126.f071QT512153@vashon.polstra.com> To: current@freebsd.org From: John Polstra Reply-To: current@freebsd.org Cc: archie@dellroad.org Subject: Re: weird cvs update problem In-Reply-To: <200101070116.f071GZR41032@curve.dellroad.org> References: <200101070116.f071GZR41032@curve.dellroad.org> Organization: Polstra & Co., Seattle, WA Sender: jdp@wall.polstra.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200101070116.f071GZR41032@curve.dellroad.org>, Archie Cobbs wrote: > I have a -current system from Dec. 7 on which I'm trying to do > a cvs update in preparation of make world, and am seeing wierd > stuff like this: > > > cvs server: Updating crypto/kerberosIV/appl/afsutil > > U crypto/kerberosIV/appl/afsutil/Makefile.in > > U crypto/kerberosIV/appl/afsutil/aklog.c > > U crypto/kerberosIV/appl/afsutil/kstring2key.c > > U crypto/kerberosIV/appl/afsutil/pagsh.c > > cvs server: Updating crypto/kerberosIV/appl/bsd > > U crypto/kerberosIV/appl/bsd/Makefile.in > > U crypto/kerberosIV/appl/bsd/README.login > > U crypto/kerberosIV/appl/bsd/bsd_locl.h > > U crypto/kerberosIV/appl/bsd/encrypt.c > > U crypto/kerberosIV/appl/bsd/forkpty.c > > U crypto/kerberosIV/appl/bsd/kcmd.c > > U crypto/kerberosIV/appl/bsd/klogin.c > > U crypto/kerberosIV/appl/bsd/krcmd.c > > U crypto/kerberosIV/appl/bsd/login.c > > U crypto/kerberosIV/appl/bsd/login_access.c > > U crypto/kerberosIV/appl/bsd/login_fbtab.c > > U crypto/kerberosIV/appl/bsd/osfc2.c > > U crypto/kerberosIV/appl/bsd/pathnames.h_ > > U crypto/kerberosIV/appl/bsd/rcmd_util.c > > cvs update: warning: unrecognized response ` If there are any IP options on `sock', die.' from cvs server > > cvs update: warning: unrecognized response ` */' from cvs server [...] It sounds like maybe the rcmd_util.c,v RCS file is corrupted on the CVS server. Just a guess. I haven't seen the problem here. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 18:46:30 2001 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 725C937B400; Sat, 6 Jan 2001 18:46:12 -0800 (PST) Received: from nairobi-35.budapest.interware.hu ([195.70.50.227] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 14F5qU-00047r-00; Sun, 07 Jan 2001 03:46:10 +0100 Message-ID: <3A57D816.FDE9B45F@elischer.org> Date: Sat, 06 Jan 2001 18:44:38 -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: net@freebsd.org, current@freebsd.org Subject: Warning: wild pointer somewhere in netgraph. Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have uncovered some odd behavior on my machine here using netgraph since the last changes.. I'm trying to find the problem but I need sleep... If you have used he latest netgraph code, let me know what modules you are using and how so I can try narrow my search.. thanks.. Julian -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ from Perth, presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 23:21: 9 2001 Delivered-To: freebsd-current@freebsd.org Received: from harmony.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8468E37B7A4 for ; Sat, 6 Jan 2001 23:03:48 -0800 (PST) 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 f0773Js67894; Sun, 7 Jan 2001 00:03:25 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200101070703.f0773Js67894@harmony.village.org> To: Michael Harnois Subject: Re: broken at if_ray.c Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "06 Jan 2001 17:50:30 CST." <86itnsme9l.fsf@mharnois.workgroup.net> References: <86itnsme9l.fsf@mharnois.workgroup.net> Date: Sun, 07 Jan 2001 00:03:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <86itnsme9l.fsf@mharnois.workgroup.net> Michael Harnois writes: : /usr/src/sys/modules/ray/../../dev/ray/if_ray.c:3369: too few arguments to function `CARD_SET_MEMORY_OFFSET' : card_if.h:44: warning: inlining failed in call to `CARD_SET_MEMORY_OFFSET' Thanks, this is another place that Jonathan forgot to update when he checked in his changes. I'm on it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 6 23:48:10 2001 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id 1046637B400; Sat, 6 Jan 2001 23:47:46 -0800 (PST) Received: from C992631-A.pinol1.sfba.home.com (C992631-A.pinol1.sfba.home.com [24.12.58.155]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id JAA27171; Sun, 7 Jan 2001 09:47:27 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by C992631-A.pinol1.sfba.home.com (8.11.1/8.11.1) id f077l0D48707; Sat, 6 Jan 2001 23:47:00 -0800 (PST) (envelope-from reg) Date: Sat, 6 Jan 2001 23:46:55 -0800 From: Jeremy Lea To: freebsd-ports@FreeBSD.org, "Jordan K. Hubbard" Cc: freebsd-current@FreeBSD.org, Satoshi Asami Subject: Latest on rewrite of pkg_install tools. Message-ID: <20010106234655.K388@shale.csir.co.za> Mail-Followup-To: Jeremy Lea , freebsd-ports@FreeBSD.org, "Jordan K. Hubbard" , freebsd-current@FreeBSD.org, Satoshi Asami 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 Hi, hub seems to be acting up, so I'm sending this a second time... Sorry for any duplicates. At http://people.FreeBSD.org/~reg/, I have placed the latest of my patches to the pkg_install tools. This is an almost complete rewrite of the tools, based around a 'Package Manager', which supplies an API which could be used by third party applications (like a KDE or GTK+ application.) There is more status on the page, but the current patch set implements: - which(1) like functionality, to tell you which package installed a particular file. - BUILD_DEPEND and LIB_DEPEND style dependency checking, which relies on installed files and libraries, not the package names. - Use pkg_add from bsd.port.mk, so that building a port no longer requires any of the dependencies to be checked out. - Backup packages created from the installed packages. Future enhancements include the ability to run a backup script to save local configuration/data files into the backup package. - Inplace upgrading of installed packages, by deleting the old package, except it's shared libraries, and merging these into the new package's plist. This will obsolete the recent pkg_upgrade commit. The code is pretty rough at the moment. I'm still testing it, so expect a new release soon, with a bunch of bug fixes. I would really like people to comment on the added functionality, the design and pkg_mgr API and also do some testing for me. There is also a patch for bsd.port.mk, which uses these changes. Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message