From owner-freebsd-current Sun Mar 24 0: 6:13 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 5386037B400 for ; Sun, 24 Mar 2002 00:06:10 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2O85tp1056590 for ; Sun, 24 Mar 2002 09:05:55 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: Your message of "Sat, 23 Mar 2002 15:55:00 PST." <20020323155500.A18666@dragon.nuxi.com> Date: Sun, 24 Mar 2002 09:05:55 +0100 Message-ID: <56589.1016957155@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20020323155500.A18666@dragon.nuxi.com>, "David O'Brien" writes: >The RE's are wanting to ship 5.0 DP#1 w/this patch applied. >If having 'AJ' by default is deemed not useful (by being removed from the >DP), it sounds like we should just turn it off. > >Unless there is strong objection, I plan on committing this. I firmly belive that only things which ship as FreeBSD-%d.%d-RELEASE should have the AJ options turned off. We want both our own code and 3rd party code to find the bugs in a DP release rather than in a RELEASE. Put a prominent notice in the release note, put a pointer to the recent libz scare if you feel like, and say that since this is about trying out and testing, we have set these options to help people flush out bugs. The steady trickle of emails I receive about things exposed by AJ is a clear indication that we need it on as much as possible. -- 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 Sun Mar 24 2:57:49 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id C60AE37B417 for ; Sun, 24 Mar 2002 02:57:45 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OAvSp1058486 for ; Sun, 24 Mar 2002 11:57:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: LINT börked... From: Poul-Henning Kamp Date: Sun, 24 Mar 2002 11:57:28 +0100 Message-ID: <58485.1016967448@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes - Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../../.. -I../. ./../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include -DGPROF -DG PROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -elf -malign-functions=4 - fno-builtin -mpreferred-stack-boundary=2 -Werror -pg -mprofiler-epilogue ../../../dev/bktr/bktr_i2c. c ../../../dev/bktr/bktr_i2c.c: In function `bt848_i2c_attach': ../../../dev/bktr/bktr_i2c.c:87: structure has no member named `i2c_sc' ../../../dev/bktr/bktr_i2c.c:92: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:93: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:101: dereferencing pointer to incomplete type ../../../dev/bktr/bktr_i2c.c:103: dereferencing pointer to incomplete type -- 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 Sun Mar 24 3:41:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id C929F37B41B for ; Sun, 24 Mar 2002 03:41:30 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g2OBfRT63329; Sun, 24 Mar 2002 12:41:27 +0100 (CET) (envelope-from wkb) Date: Sun, 24 Mar 2002 12:41:27 +0100 From: Wilko Bulte To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't build world on alpha Message-ID: <20020324124127.E63202@freebie.xs4all.nl> References: <200203231902.g2NJ2QS71349@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203231902.g2NJ2QS71349@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Mar 23, 2002 at 11:02:26AM -0800 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote: As a datapoint, this does work when starting from a 4.5-RELEASE I just did a build yesterday on the AS500 Wilko > Anyone have any ideas? I'm trying to build the latest -current > (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'. > > -Matt > Matthew Dillon > > > cc -O -pipe -mcpu=ev4 -D_open=open -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr/obj/FreeBSD/FreeBSD-current/src/alpha/usr\" -DHAIFA -I/usr/obj/FreeBSD/FreeBSD-current/src/alpha/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../cc_tools -I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../cc_tools -I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../contrib/gcc.295 -I/FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../contrib/gcc.295/config -c /FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c -o mktemp.o > /FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c:38: syntax error before string constant > /FreeBSD/FreeBSD-current/src/gnu/usr.bin/cc/cc_fbsd/../../../../lib/libc/stdio/mktemp.c:38: warning: data definition has no type or storage class > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---end of quoted text--- -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 5: 3:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from core.zp.ua (core.zp.ua [193.108.112.7]) by hub.freebsd.org (Postfix) with ESMTP id 01F4837B404; Sun, 24 Mar 2002 05:03:41 -0800 (PST) Received: (from oleg@localhost) by core.zp.ua with œ id g2OD3XE44357; Sun, 24 Mar 2002 15:03:33 +0200 (EET) (envelope-from oleg)œ Date: Sun, 24 Mar 2002 15:03:33 +0200 From: "Oleg V. Naumann" To: current@freebsd.org Cc: luigi@freebsd.org Subject: Re: is 'device ether' mandatory now? Message-ID: <20020324130333.GE25880@core.zp.ua> Mail-Followup-To: current@freebsd.org, luigi@FreeBSD.ORG References: <20020323204359.Y10340-100000@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20020323204359.Y10340-100000@news1.macomnet.ru> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Mar 23, 2002 at 08:50:19PM +0300, Maxim Konovalov wrote: > > Hello, > > After this commit 'device ether' is mandatory if ever there is no any > ethernet or token-ring devices. The same problem in STABLE... from revision 1.85.2.15 of net/if.c: #ifdef INET /* * Also send gratuitous ARPs to notify other nodes about * the address change. */ TAILQ_FOREACH(ifa, &ifp->if_addrhead, ifa_link) { if (ifa->ifa_addr != NULL && ifa->ifa_addr->sa_family == AF_INET) arp_ifinit((struct arpcom *)ifp, ifa); } #endif arp_ifinit defined in netinet/if_ether.c This makes 'device ether' mandatory for 'options INET', so kernel with 'options INET', but without 'device ether' failed to built: sh ../../conf/newvers.sh DIALUP cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/ipfilter -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel if.o: In function `if_setlladdr': if.o(.text+0x1ac8): undefined reference to `arp_ifinit' *** Error code 1 Stop in /usr/src/sys/compile/DIALUP. bash-2.05# uname -a FreeBSD core.zp.ua 4.5-STABLE FreeBSD 4.5-STABLE #2: Thu Mar 14 20:31:11 EET 2002 root@core.zp.ua:/usr/obj/usr/src/sys/core i386 (yes, my computer@home doesn't have any arp-capable devices, and connects with Internet via dialup) > > | luigi 2002/02/18 14:50:13 PST > | > | Modified files: > | sys/net if.c > | Log: > | When the local link address is changed, send out gratuitous ARPs > | to notify other nodes about the address change. Otherwise, they > | might try and keep using the old address until their arp table > | entry times out and the address is refreshed. > | > | Maybe this ought to be done for INET6 addresses as well but i have > | no idea how to do it. It should be pretty straightforward though. > | > | MFC-after: 10 days > | > | Revision Changes Path > | 1.128 +11 -0 src/sys/net/if.c > > -- > Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- With best wishes Oleg V. Nauman NO37-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 5:21:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 06EED37B435 for ; Sun, 24 Mar 2002 05:21:01 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g2ODKuH87499; Sun, 24 Mar 2002 05:20:56 -0800 (PST) (envelope-from rizzo) Date: Sun, 24 Mar 2002 05:20:56 -0800 From: Luigi Rizzo To: Maxim Konovalov Cc: current@freebsd.org Subject: Re: is 'device ether' mandatory now? Message-ID: <20020324052056.B87371@iguana.icir.org> References: <20020323204359.Y10340-100000@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020323204359.Y10340-100000@news1.macomnet.ru> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Do you have a suggestion for an #ifdef /#endif to remove the problem you mention ? cheers luigi On Sat, Mar 23, 2002 at 08:50:19PM +0300, Maxim Konovalov wrote: > > Hello, > > After this commit 'device ether' is mandatory if ever there is no any > ethernet or token-ring devices. > > | luigi 2002/02/18 14:50:13 PST > | > | Modified files: > | sys/net if.c > | Log: > | When the local link address is changed, send out gratuitous ARPs > | to notify other nodes about the address change. Otherwise, they > | might try and keep using the old address until their arp table > | entry times out and the address is refreshed. > | > | Maybe this ought to be done for INET6 addresses as well but i have > | no idea how to do it. It should be pretty straightforward though. > | > | MFC-after: 10 days > | > | Revision Changes Path > | 1.128 +11 -0 src/sys/net/if.c > > -- > Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 8:28:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 871A237B419; Sun, 24 Mar 2002 08:28:33 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2OGSRk75028; Sun, 24 Mar 2002 11:28:27 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Mar 2002 11:28:27 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "M. Warner Losh" Cc: current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: <20020323.172335.39636005.imp@village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 23 Mar 2002, M. Warner Losh wrote: > In message: <20020323155500.A18666@dragon.nuxi.com> > "David O'Brien" writes: > : The RE's are wanting to ship 5.0 DP#1 w/this patch applied. > : If having 'AJ' by default is deemed not useful (by being removed from the > : DP), it sounds like we should just turn it off. > : > : Unless there is strong objection, I plan on committing this. > > I think we should keep AJ enabled until at least DP2. It has found bugs > in the past, and I suspect that a lot of new code is going in between > now and then. Not clear from your suggestion if you mean the branch or the dp's. My feeling is that a useful strategy is: - -CURRENT has AJ from inception of branch until final DP before release. - DP's don't have AJ AJ generates false positives in the form of third party application behavior changes. When we're replacing things like the threading model, etc, etc, I don't want application failures to be attributed to those feature changes when they originate from memory junking. DP's offer an opportunity for third party developers to explore the new feature set, make sure their applications work with the new primitives, etc. While forcing them to fix memory related bugs is a useful activity, doing it with the DP seems to be a less useful activity. Useful feedback: - New protection settings for signalling break (fooapp) - There appear to be thread problems related to file descriptors and KSE - Changes in mmap behavior result in some applications with custom memory management failing Unuseful feedback: - Some major application coredumps before it even pops up a window due to referencing memory after a free but before it's reallocated, resulting in ten or fifteen such bug reports - Some X11 application usually run without a terminal on stderr dies frequently due to violating a safety constraint; failure mode is reported to us and prevents people from running that application, meaning we don't learn about system bugs - Some applications become incredibly slow and have very high loads, so the DP can't be used out of the box for some server environments where we'd like it to be used to maximize load on the system. With new userland code coming into -CURRENT at a rapid rate, it may be useful in -CURRENT for developers. For DPs, probably not. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 8:48:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id E938037B400; Sun, 24 Mar 2002 08:48:05 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OGlmp1062337; Sun, 24 Mar 2002 17:47:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: "M. Warner Losh" , current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: Your message of "Sun, 24 Mar 2002 11:28:27 EST." Date: Sun, 24 Mar 2002 17:47:47 +0100 Message-ID: <62336.1016988467@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >With new userland code coming into -CURRENT at a rapid rate, it may be >useful in -CURRENT for developers. For DPs, probably not. I don't have to tell you what the 'D' in 'DP' means, right ? :-) Robert, I can only say that I disagree 100% with you. In principle because I think only -RELEASE should not have J, and I think even -RELEASE should have A. In practice I think this is completely l00ney, considering what we have done in the kernel, worrying about AJ related false hits is sooo totally down in the noise. -- 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 Sun Mar 24 8:58:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1B02537B41B for ; Sun, 24 Mar 2002 08:58:49 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2OGwmYm005693 for ; Sun, 24 Mar 2002 08:58:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2OGvXuQ005669 for current@FreeBSD.ORG; Sun, 24 Mar 2002 08:57:33 -0800 (PST) Date: Sun, 24 Mar 2002 08:57:33 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default Message-ID: <20020324085733.C26339@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20020323.172335.39636005.imp@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: ; from rwatson@FreeBSD.ORG on Sun, Mar 24, 2002 at 11:28:27AM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 24, 2002 at 11:28:27AM -0500, Robert Watson wrote: > Not clear from your suggestion if you mean the branch or the dp's. My > feeling is that a useful strategy is: > > - -CURRENT has AJ from inception of branch until final DP before release. > - DP's don't have AJ The DP's should have what ever is in -CURRENT. I don't care which state that is. Should I also mention the DP's GENERIC kernel has no INVARIANTS and no WITNESS? I have not gotten a response back from the RE's about that one yet. This is also wrong. INVARIANTS is low-impact. I can kind of accept WITNESS -- maybe we should turn it off in GENERIC in -CURRENT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 9: 1: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 5D0F437B41C for ; Sun, 24 Mar 2002 09:00:59 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2OH0mYm005815; Sun, 24 Mar 2002 09:00:48 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2OGxWDW005702; Sun, 24 Mar 2002 08:59:32 -0800 (PST) Date: Sun, 24 Mar 2002 08:59:32 -0800 From: "David O'Brien" To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: can't build world on alpha Message-ID: <20020324085932.D26339@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200203231902.g2NJ2QS71349@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203231902.g2NJ2QS71349@apollo.backplane.com>; from dillon@apollo.backplane.com on Sat, Mar 23, 2002 at 11:02:26AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote: > Anyone have any ideas? I'm trying to build the latest -current > (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'. I have thought about what could be the problem several times and cannot come up with anything (thus my slow responce). Please tell more about your environment. How did you get 4.3 on the Alpha. Can you build 4.3 first to verify things are OK. Or are you willing to try building RELENG_4 first? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 9: 4:51 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 8046137B419; Sun, 24 Mar 2002 09:04:41 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2OH4Uk76459; Sun, 24 Mar 2002 12:04:34 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Mar 2002 12:04:29 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: "M. Warner Losh" , current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: <62336.1016988467@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Mar 2002, Poul-Henning Kamp wrote: > In message , Robe > rt Watson writes: > > >With new userland code coming into -CURRENT at a rapid rate, it may be > >useful in -CURRENT for developers. For DPs, probably not. > > I don't have to tell you what the 'D' in 'DP' means, right ? :-) > > Robert, I can only say that I disagree 100% with you. > > In principle because I think only -RELEASE should not have J, and I > think even -RELEASE should have A. > > In practice I think this is completely l00ney, considering what we have > done in the kernel, worrying about AJ related false hits is sooo totally > down in the noise. A few weeks ago, I would have believed you. Except that using -J was a workaround recommended in a recent security advisory--prior to recommending it, I ran it on a server of mine for a few days. You'd be surprised how many random applications keel over, and the performance impact it has for some specific types of applications. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 9:10:53 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A5BB137B419; Sun, 24 Mar 2002 09:10:50 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OHAYp1062767; Sun, 24 Mar 2002 18:10:34 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: "M. Warner Losh" , current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: Your message of "Sun, 24 Mar 2002 12:04:29 EST." Date: Sun, 24 Mar 2002 18:10:34 +0100 Message-ID: <62766.1016989834@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >A few weeks ago, I would have believed you. Except that using -J was a >workaround recommended in a recent security advisory--prior to >recommending it, I ran it on a server of mine for a few days. You'd be >surprised how many random applications keel over, and the performance >impact it has for some specific types of applications. No, I will not be surprised no matter what you tell me. I used to keep save all emails I got about phkmalloc nailing bugs, now I only track "significant" ones. But let me turn it around, what would it take for you to accept AJ in the developer release ? Better diagnostics ? -- 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 Sun Mar 24 9:18: 5 2002 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 E499437B417; Sun, 24 Mar 2002 09:18:02 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id CE2805346; Sun, 24 Mar 2002 18:18:00 +0100 (CET) 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: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default References: <20020323.172335.39636005.imp@village.org> <20020324085733.C26339@dragon.nuxi.com> From: Dag-Erling Smorgrav Date: 24 Mar 2002 18:18:00 +0100 In-Reply-To: <20020324085733.C26339@dragon.nuxi.com> Message-ID: Lines: 12 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "David O'Brien" writes: > Should I also mention the DP's GENERIC kernel has no INVARIANTS and no > WITNESS? I have not gotten a response back from the RE's about that one > yet. This is also wrong. INVARIANTS is low-impact. I can kind of > accept WITNESS -- maybe we should turn it off in GENERIC in -CURRENT. Agreed. Please turn on INVARIANTS by default in DP1; its impact on performance is minimal and it helps *a lot* in tracking down bugs. 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 Sun Mar 24 9:34:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E59FE37B417; Sun, 24 Mar 2002 09:34:17 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2OHY9k76843; Sun, 24 Mar 2002 12:34:10 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Mar 2002 12:34:08 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: "M. Warner Losh" , current@FreeBSD.ORG, obrien@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: <62766.1016989834@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Mar 2002, Poul-Henning Kamp wrote: > In message , Robe > rt Watson writes: > > >A few weeks ago, I would have believed you. Except that using -J was a > >workaround recommended in a recent security advisory--prior to > >recommending it, I ran it on a server of mine for a few days. You'd be > >surprised how many random applications keel over, and the performance > >impact it has for some specific types of applications. > > No, I will not be surprised no matter what you tell me. I used to keep > save all emails I got about phkmalloc nailing bugs, now I only track > "significant" ones. > > But let me turn it around, what would it take for you to accept AJ in > the developer release ? Better diagnostics ? Hmm. The argument for A is, I think, is a lot stronger than for J, since it comes without the performance impact, and you can actually generate useful diagnostics. I would be fine with leaving A in the developer snapshot. On the issue of making diagnostics more useful: sending this debugging information to syslog might be one way. The 'abort' already ends up on the console and in the log: Mar 24 12:25:39 paprika kernel: pid 52818 (tmp), uid 1000: exited on signal 6 (core dumped) Making that more informative might be helpful. I.e., Mar 24 12:25:39 paprika tmp: pid 52818: application error, double free(), aborting. Mar 24 12:25:39 paprika kernel: pid 52818 (tmp), uid 1000: exited on signal 6 (core dumped) would probably go a long way. This addresses the problem of "stderr lost for some or another reason, but the kernel message remains". On the other hand, it does introduce some potential recursion/reentrancy issues. I like the impact of J from the perspective of an application developer knowingly specifically turning it on, but part of the general problem with J is that the failure detection occurs as part of the application code, rather than specifically in a system library that can provide improved reporting. For example: ckimail is a command line IMAP tool which scans a set of IMAP mailboxes. It contains a bug (I assume) involving use of memory following a free(). With J turned on, it segfaults almost immediately on start (very soon after execve() completes). I'd like to be able to distinguish between bugs caused by this type of improved application debugging, and bugs generated by incorrect stack and signal handling, etc, which have the same failure mode (Segmentation Violation, Core Dumped). Other than playing electric fence-like games with memory protection and signal handlers (or heavy instrumentation in the form of purify), it's not clear to me how catching free'd memory use maps into specific reporting output. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 9:38:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A630D37B400; Sun, 24 Mar 2002 09:38:42 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g2OHcgh76708; Sun, 24 Mar 2002 09:38:42 -0800 (PST) (envelope-from dillon) Date: Sun, 24 Mar 2002 09:38:42 -0800 (PST) From: Matthew Dillon Message-Id: <200203241738.g2OHcgh76708@apollo.backplane.com> To: "David O'Brien" Cc: freebsd-current@freebsd.org Subject: Re: can't build world on alpha References: <200203231902.g2NJ2QS71349@apollo.backplane.com> <20020324085932.D26339@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote: :> Anyone have any ideas? I'm trying to build the latest -current :> (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'. : :I have thought about what could be the problem several times and cannot :come up with anything (thus my slow responce). : :Please tell more about your environment. How did you get 4.3 on the :Alpha. Can you build 4.3 first to verify things are OK. Or are you :willing to try building RELENG_4 first? I have successfully built and installed a -stable world. It took all day, but it worked :-) Unfortunately, it did not clear up the problem. I still get this error however: /FreeBSD/FreeBSD-current/src/sys/sys/types.h:50: global register variable follows a function definition /FreeBSD/FreeBSD-current/src/sys/sys/types.h:50: warning: call-clobbered register used for global register variable It appears that this line in alpha/include/pcpu.h: register struct pcpu *pcpup __asm__("$8"); Must occur before any inlines. There are inlines #include'd long before pcpu.h is included. The first I can find is in alpha/include/endian.h, which is included by sys/types.h. That's as far as I've gotten. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 10:33:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 1751737B41B; Sun, 24 Mar 2002 10:33:16 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2OIXFYm012684; Sun, 24 Mar 2002 10:33:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2OIW0Uj012644; Sun, 24 Mar 2002 10:32:00 -0800 (PST) Date: Sun, 24 Mar 2002 10:32:00 -0800 From: "David O'Brien" To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default Message-ID: <20020324103200.B8262@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <62766.1016989834@critter.freebsd.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 rwatson@FreeBSD.ORG on Sun, Mar 24, 2002 at 12:34:08PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 24, 2002 at 12:34:08PM -0500, Robert Watson wrote: > Hmm. The argument for A is, I think, is a lot stronger than for J, since > it comes without the performance impact, and you can actually generate > useful diagnostics. I would be fine with leaving A in the developer > snapshot. Lets back up and clarify RE's goals for the DP#1. Turning off all of our debugging options and appearing to make this benchmark ready were not part of what I [thought I] heard at the Kernel Summit at BSDcon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 11: 0:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D22C137B439 for ; Sun, 24 Mar 2002 11:00:00 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2OIxuk77844 for ; Sun, 24 Mar 2002 13:59:57 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Mar 2002 13:59:56 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: <20020324103200.B8262@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Mar 2002, David O'Brien wrote: > On Sun, Mar 24, 2002 at 12:34:08PM -0500, Robert Watson wrote: > > Hmm. The argument for A is, I think, is a lot stronger than for J, since > > it comes without the performance impact, and you can actually generate > > useful diagnostics. I would be fine with leaving A in the developer > > snapshot. > > Lets back up and clarify RE's goals for the DP#1. Turning off all of > our debugging options and appearing to make this benchmark ready were > not part of what I [thought I] heard at the Kernel Summit at BSDcon. The goal of DP's is to increase exposure of the development branch in some key audiences, including the developer community, and community of early adopters. Part of the discussion that lead up to deciding to follow through on the DP plan was the perception that many FreeBSD non-kernel developers are not running 5.0, and that 5.0 had a "fear" element that didn't seem to match with reality. A part of addressing this is to provide a window into which 4.x developers can try out 5.x with a lower level of risk: this is why we had something that resembled a code slush, and why when greenvm was committed during the code slush, we actually backed it out of the DP branch (it was later also backed out of the main development branch). We want to provide a stable and usable version of 5.0, in as much as that is possible, to provide access to the new features, services, APIs, etc. We want a reproduceable install that ports developers can use to learn more about the changing 5.0 environment, among other things. We will actually be offering at least three seperate kernels on the DP cd: - GENERIC, which resembles a normal release GENERIC - DEBUG, which has uber-debugging features - NEWCARD, which offers the NEWCARD feature set For future DPs, we'll lose the oldcard/newcard distinction so we'll cut that out of the offering as soon as that is possible. GENERIC will offer the user something that they can use easily and effectively from the install. DEBUG turns on many debugging features, and will provide an easy path to debug system problems without evening having to custom compile a kernel. Users will have the option of selecting "maximal debugging" to attempt to track down problems and test the system. They'll have the option to select "Looks most like a release" to use for application testing and porting, not to mention daily usage. Something that phk and I have discussed out-of-band is the idea of keying phkmalloc behavior to kernel selection. I.e., exposing a policy sysctl from the kernel, keyed to the kernel identity/option, causing phkmalloc to behave different based on the kernel selection. This would allow DEBUG to turn on maximal debugging, but GENERIC to have phkmalloc behave "like a release". Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 11: 8:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 7B4DD37B41F; Sun, 24 Mar 2002 11:08:08 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OJ7qp1064166; Sun, 24 Mar 2002 20:07:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: Your message of "Sun, 24 Mar 2002 13:59:56 EST." Date: Sun, 24 Mar 2002 20:07:52 +0100 Message-ID: <64165.1016996872@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message , Robe rt Watson writes: >Something that phk and I have discussed out-of-band is the idea of keying >phkmalloc behavior to kernel selection. I.e., exposing a policy sysctl >from the kernel, keyed to the kernel identity/option, causing phkmalloc to >behave different based on the kernel selection. This would allow DEBUG to >turn on maximal debugging, but GENERIC to have phkmalloc behave "like a >release". I said this as possible with a sysctl, I still think it is moderately disgusting though. You can do the same thing more visible by having /etc/rc* fiddle /etc/malloc.conf based on uname(1). >We will actually be offering at least three seperate kernels on the DP cd: > >- GENERIC, which resembles a normal release GENERIC >- DEBUG, which has uber-debugging features >- NEWCARD, which offers the NEWCARD feature set I would expect the three planned DP's to have these properties: One DEBUG kernel with: INVARIANTS WITNESS DDB One GENERIC kernel with: INVARIANTS DDB Userland: DP1 + DP2: malloc AJ DP3: malloc A Now, I also have to say that I'm not going to do any of this, so this will be my last email on the topic: Do whatever you think is the right thing to do. -- 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 Sun Mar 24 11:15:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id B8C4037B41D for ; Sun, 24 Mar 2002 11:15:14 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2OJExp1064239 for ; Sun, 24 Mar 2002 20:14:59 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: Cross architecture disklabels... From: Poul-Henning Kamp Date: Sun, 24 Mar 2002 20:14:59 +0100 Message-ID: <64238.1016997299@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I belive GEOM will now correctly identify the following label formats on all platforms: MSDOS MBR MSDOS MBR extended partitions FreeBSD/i386 disklabel FreeBSD/alpha disklabel Solaris/disklabel This in practice means that one can move a disk from one architecture to another and get at the slices/partitions etc. This also means that I belive GEOM will DTRT for -current users for a long stretch of the road, and would therefore encourage more people to please test it out. -- 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 Sun Mar 24 11:16:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 585A737B404 for ; Sun, 24 Mar 2002 11:16:11 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2OJG2k78040; Sun, 24 Mar 2002 14:16:02 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Sun, 24 Mar 2002 14:16:02 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default In-Reply-To: <64165.1016996872@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This seems like a reasonable strategy. If we do this, we'll need to expand the discussion of performance tuning and usability in the release notes for the DP. We'll also need to formalize the notion of DP3: right now we have only DP1 and DP2 formally scheduled, and DP2 is expected to have some bumps due to KSE hopefully becoming real for userland for that, and with the MAC code. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services On Sun, 24 Mar 2002, Poul-Henning Kamp wrote: > In message , Robe > rt Watson writes: > > > >Something that phk and I have discussed out-of-band is the idea of keying > >phkmalloc behavior to kernel selection. I.e., exposing a policy sysctl > >from the kernel, keyed to the kernel identity/option, causing phkmalloc to > >behave different based on the kernel selection. This would allow DEBUG to > >turn on maximal debugging, but GENERIC to have phkmalloc behave "like a > >release". > > I said this as possible with a sysctl, I still think it is moderately > disgusting though. You can do the same thing more visible by having > /etc/rc* fiddle /etc/malloc.conf based on uname(1). > > >We will actually be offering at least three seperate kernels on the DP cd: > > > >- GENERIC, which resembles a normal release GENERIC > >- DEBUG, which has uber-debugging features > >- NEWCARD, which offers the NEWCARD feature set > > I would expect the three planned DP's to have these properties: > > One DEBUG kernel with: > INVARIANTS > WITNESS > DDB > One GENERIC kernel with: > INVARIANTS > DDB > Userland: > DP1 + DP2: malloc AJ > DP3: malloc A > > Now, I also have to say that I'm not going to do any of this, so > this will be my last email on the topic: Do whatever you think is > the right thing to do. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 12: 3:52 2002 Delivered-To: freebsd-current@freebsd.org Received: from totem.fix.no (totem.fix.no [80.91.32.29]) by hub.freebsd.org (Postfix) with ESMTP id 0786237B400; Sun, 24 Mar 2002 12:03:27 -0800 (PST) Received: by totem.fix.no (Postfix, from userid 1000) id D52E13C97; Sun, 24 Mar 2002 21:03:43 +0100 (CET) Date: Sun, 24 Mar 2002 21:03:43 +0100 From: Anders Nordby To: dominic_marks@btinternet.com, current@freebsd.org, stable@freebsd.org Cc: n_hibma@freebsd.org Subject: How to make USB scanners work in FreeBSD (well at least Agfa ones..) Message-ID: <20020324200343.GA24999@totem.fix.no> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline User-Agent: Mutt/1.3.27i X-message-flag: Outlook : A program to spread viri, but it can do mail too. X-PGP-Key: http://anders.fix.no/pgp/ X-PGP-Key-FingerPrint: 1E0F C53C D8DF 6A8F EAAD 19C5 D12A BC9F 0083 5956 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Attached are patches that makes scanning work with sane, using an Agfa Snapscan 1212U USB scanner for me. They are merely reworked from PRs 32652 and 32653 by ebakke@trolltech.com. NB: Only tested in 4.5-stable, not in -current (sorry). Patches should apply cleanly in -stable. It would be nice if more people could have a look at this, so that we can get hopefully get it in the tree sometime soon. Thanks. -- Anders. --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mypatch-usb.h" --- sys/dev/usb/usb.h.orig Tue Oct 31 23:59:35 2000 +++ sys/dev/usb/usb.h Wed Feb 20 01:52:35 2002 @@ -566,4 +566,7 @@ #define USB_GET_CM_OVER_DATA _IOR ('U', 130, int) #define USB_SET_CM_OVER_DATA _IOW ('U', 131, int) +/* Scanner device */ +#define USB_GET_DEVICE_ID _IOR('U', 140, int) + #endif /* _USB_H_ */ --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mypatch-uscanner.c_v2" --- sys/dev/usb/uscanner.c.orig Thu Feb 14 03:52:50 2002 +++ sys/dev/usb/uscanner.c Sun Feb 24 00:46:11 2002 @@ -222,6 +222,8 @@ int sc_refcnt; u_char sc_dying; + u_int16_t sc_vendor_id; + u_int16_t sc_product_id; }; #if defined(__NetBSD__) || defined(__OpenBSD__) @@ -233,7 +235,7 @@ d_write_t uscannerwrite; d_ioctl_t uscannerioctl; d_poll_t uscannerpoll; - +d_ioctl_t uscannerioctl; #define USCANNER_CDEV_MAJOR 156 Static struct cdevsw uscanner_cdevsw = { @@ -289,6 +291,8 @@ sc->sc_dev_flags = uscanner_lookup(uaa->vendor, uaa->product)->flags; sc->sc_udev = uaa->device; + sc->sc_vendor_id = uaa->vendor; + sc->sc_product_id = uaa->product; err = usbd_set_config_no(uaa->device, 1, 1); /* XXX */ if (err) { @@ -360,9 +364,10 @@ USB_GET_SC_OPEN(uscanner, unit, sc); - DPRINTFN(5, ("uscanneropen: flag=%d, mode=%d, unit=%d\n", + DPRINTFN(5, ("uscanneropen: flag=%d, mode=%d, unit=%d\n", flag, mode, unit)); + printf( "uscanneropen()\n" ); if (sc->sc_dying) return (ENXIO); @@ -696,9 +701,25 @@ int uscannerioctl(dev_t dev, u_long cmd, caddr_t addr, int flag, struct proc *p) { - return (EINVAL); + struct uscanner_softc* sc; + + USB_GET_SC( uscanner, USCANNERUNIT( dev ), sc ); + + if( sc->sc_dying ) + return( EIO ); + + switch( cmd ) { + case USB_GET_DEVICE_ID: + *(u_int32_t*)addr = ( sc->sc_vendor_id << 16 ) | sc->sc_product_id; + break; + default: + return EINVAL; + } + return 0; } #if defined(__FreeBSD__) DRIVER_MODULE(uscanner, uhub, uscanner_driver, uscanner_devclass, usbd_driver_load, 0); #endif + + --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=mypatch-sane-backends diff -Nur sane-backends.old/files/patch-backend_snapscan.c sane-backends/files/patch-backend_snapscan.c --- sane-backends.old/files/patch-backend_snapscan.c Thu Jan 1 00:00:00 1970 +++ sane-backends/files/patch-backend_snapscan.c Tue Mar 5 23:49:15 2002 @@ -0,0 +1,19 @@ +--- backend/snapscan.c.bak Sun Dec 9 22:51:01 2001 ++++ backend/snapscan.c Sun Dec 9 22:51:01 2001 +@@ -1016,7 +1016,11 @@ + + vendor[0] = model[0] = '\0'; + ++#if defined( __FreeBSD__ ) ++ if(strstr (name, "uscanner")) ++#else /* __FreeBSD__ */ + if((strstr (name, "usb")) || (strstr (name, "USB"))) ++#endif /* __FreeBSD__ */ + { + DBG (DL_VERBOSE, "%s: Detected (kind of) an USB device\n", me); + +@@ -3540,3 +3544,4 @@ + * Revision 1.1 1997/10/13 02:25:54 charter + * Initial revision + * */ ++ diff -Nur sane-backends.old/files/patch-sanei_sanei_usb.c sane-backends/files/patch-sanei_sanei_usb.c --- sane-backends.old/files/patch-sanei_sanei_usb.c Thu Jan 1 00:00:00 1970 +++ sane-backends/files/patch-sanei_sanei_usb.c Tue Mar 5 23:49:22 2002 @@ -0,0 +1,42 @@ +--- sanei/sanei_usb.c.bak Sun Dec 9 22:40:14 2001 ++++ sanei/sanei_usb.c Sun Dec 9 22:49:04 2001 +@@ -112,6 +112,9 @@ + SANE_Word * product) + { + SANE_Word vendorID, productID; ++#if defined( __FreeBSD__ ) ++ u_int32_t vendorproductID; ++#endif /* __FreeBSD__ */ + + #if defined (__linux__) + #define IOCTL_SCANNER_VENDOR _IOR('U', 0x20, int) +@@ -145,8 +148,24 @@ + if (product) + *product = productID; + #else /* not defined (__linux__) */ ++#if defined( __FreeBSD__ ) ++#define USB_GET_DEVICE_ID _IOR('U', 140, int) ++ /* read the vendo and product IDs via the IOCTLs */ ++ if( ioctl( fd, USB_GET_DEVICE_ID, &vendorproductID ) == -1 ) ++ { ++ DBG( 3, "sanei_usb_get_vendor_product: ioctl( productid ) of fd %d " ++ "failed: %s\n", fd, strerror( errno ) ); ++ } ++ productID = vendorproductID & 0xffff; ++ vendorID = ( vendorproductID >> 16 ) & 0xffff; ++ if( vendor ) ++ *vendor = vendorID; ++ if( product ) ++ *product = productID; ++#else /* __FreeBSD__ */ + vendorID = 0; + productID = 0; ++#endif /* __FreeBSD__ */ + #endif /* not defined (__linux__) */ + + if (!vendorID || !productID) +@@ -309,3 +328,4 @@ + *size = write_size; + return SANE_STATUS_GOOD; + } ++ --2fHTh5uZTiUOsy+g-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 13:25:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id DA64137B419; Sun, 24 Mar 2002 13:25:06 -0800 (PST) Received: from DougBarton.net (12-234-22-238.client.attbi.com [12.234.22.238]) by mail-relay1.yahoo.com (Postfix) with ESMTP id C15058B5FF; Sun, 24 Mar 2002 13:25:05 -0800 (PST) Message-ID: <3C9E4431.2D103001@DougBarton.net> Date: Sun, 24 Mar 2002 13:25:05 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.79 [en] (X11; U; FreeBSD 4.5-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Cc: Robert Watson Subject: Re: turning off malloc's AJ by default References: <62766.1016989834@critter.freebsd.dk> <20020324103200.B8262@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Sun, Mar 24, 2002 at 12:34:08PM -0500, Robert Watson wrote: > > Hmm. The argument for A is, I think, is a lot stronger than for J, since > > it comes without the performance impact, and you can actually generate > > useful diagnostics. I would be fine with leaving A in the developer > > snapshot. > > Lets back up and clarify RE's goals for the DP#1. Turning off all of our > debugging options and appearing to make this benchmark ready were not > part of what I [thought I] heard at the Kernel Summit at BSDcon. I didn't hear that either, and it's starting to make me a little nervous. It's bad enough that the first DP will be almost wholely unlike what the 5.0-Release will actually look like, now it seems that its value will be further reduced by making it very different from -Current of the same time period. I see two major problems with that. First, it does little good for us to release something to a wider audience if it's not going to be what and how we're actually trying to test. The other major problem is that I really don't think many users are going to stick with the DP versions. When users complain about bugs in the DP's, they are going to be pointed to -Current. Then they are going to have to experience the learning curve anyway. I think a better solution would be to ship the DP's with the same defaults as -Current of the same vintage, and educate the users as to how to remove some of the debugging features. As others have said, this is supposed to be a DEVELOPER'S preview. Until we get closer to something that looks like a release, leaving the bar set a little higher benefits both us and our potential consumers. Doug -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 14:26:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-165-226-239.dsl.lsan03.pacbell.net [64.165.226.239]) by hub.freebsd.org (Postfix) with ESMTP id 3206837B444; Sun, 24 Mar 2002 14:26:33 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id A2A5E66C39; Sun, 24 Mar 2002 14:26:32 -0800 (PST) Date: Sun, 24 Mar 2002 14:26:32 -0800 From: Kris Kennaway To: alfred@FreeBSD.org, current@FreeBSD.org Subject: Lock order reversals in sys_pipe.c Message-ID: <20020324142632.A60767@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BXVAT5kNtrzKuDFl" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The bento cluster is now running with WITNESS enabled to try and track down some odd UMA lock corruption panics. Instead, it found the following lock order reversal in sys_pipe.c overnight: Mar 24 07:31:44 gohan17 kernel: lock order reversal Mar 24 07:31:44 gohan17 kernel: 1st 0xcf51aa80 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:31:44 gohan17 kernel: 2nd 0xcf88dadc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:12 gohan10 kernel: lock order reversal Mar 24 07:32:12 gohan10 kernel: 1st 0xd9a29dc0 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:12 gohan10 kernel: 2nd 0xd961addc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:57 gohan12 kernel: lock order reversal Mar 24 07:32:57 gohan12 kernel: 1st 0xd9423080 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:57 gohan12 kernel: 2nd 0xdaa704dc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 09:02:29 gohan13 kernel: lock order reversal Mar 24 09:02:29 gohan13 kernel: 1st 0xd99d6500 pipe mutex @ /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 09:02:29 gohan13 kernel: 2nd 0xd971cddc process lock @ /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Those source references are from a -current kernel from last night. Kris --BXVAT5kNtrzKuDFl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nlKXWry0BWjoQKURAoN0AKDv7/vBjrBJoUs5tyKZnMp2C6O11QCfUQhX 6wg8qJPRd73jwJa5Pgedpdg= =rt/D -----END PGP SIGNATURE----- --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 15: 3:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc1.dsl.speakeasy.net [66.92.171.91]) by hub.freebsd.org (Postfix) with SMTP id 1314237B416 for ; Sun, 24 Mar 2002 15:03:08 -0800 (PST) Received: (qmail 10495 invoked from network); 24 Mar 2002 23:02:58 -0000 Received: from ken.yumyumyum.org (HELO there) (192.168.0.2) by dsl092-171-091.wdc1.dsl.speakeasy.net with SMTP; 24 Mar 2002 23:02:58 -0000 Content-Type: text/plain; charset="iso-8859-1" From: Kenneth Culver To: Kris Kennaway Subject: Re: Lock order reversals in sys_pipe.c Date: Sun, 24 Mar 2002 18:03:21 -0500 X-Mailer: KMail [version 1.3.2] References: <20020324142632.A60767@xor.obsecurity.org> In-Reply-To: <20020324142632.A60767@xor.obsecurity.org> Cc: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020324230308.1314237B416@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sunday 24 March 2002 05:26 pm, you wrote: > The bento cluster is now running with WITNESS enabled to try and track > down some odd UMA lock corruption panics. Instead, it found the > following lock order reversal in sys_pipe.c overnight: > > Mar 24 07:31:44 gohan17 kernel: lock order reversal > Mar 24 07:31:44 gohan17 kernel: 1st 0xcf51aa80 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:31:44 > gohan17 kernel: 2nd 0xcf88dadc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:12 > gohan10 kernel: lock order reversal > Mar 24 07:32:12 gohan10 kernel: 1st 0xd9a29dc0 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:12 > gohan10 kernel: 2nd 0xd961addc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:57 > gohan12 kernel: lock order reversal > Mar 24 07:32:57 gohan12 kernel: 1st 0xd9423080 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:57 > gohan12 kernel: 2nd 0xdaa704dc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 09:02:29 > gohan13 kernel: lock order reversal > Mar 24 09:02:29 gohan13 kernel: 1st 0xd99d6500 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 09:02:29 > gohan13 kernel: 2nd 0xd971cddc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > > Those source references are from a -current kernel from last night. > > Kris I think I found something similar as well, I also found a panic, but havn't had time to track it down. The panic doesn't occur with a kernel from march 13th, but occurs with the latest kernels. Ken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 16:59:43 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id 25FC037B404; Sun, 24 Mar 2002 16:59:37 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 7A9CC66D19; Sun, 24 Mar 2002 16:59:36 -0800 (PST) Date: Sun, 24 Mar 2002 16:59:36 -0800 From: Kris Kennaway To: wollman@FreeBSD.org, current@FreeBSD.org Subject: New expr(1) breaks ports Message-ID: <20020324165936.A74698@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qDbXVdCdHGoSgWSk" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --qDbXVdCdHGoSgWSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline ...for example, the w3m port. As part of the configure script, it executes the following shell command: expr --prefix=/usr/local : -*prefix=\(.*\) expr: syntax error Is expr to blame, or w3m? Kris --qDbXVdCdHGoSgWSk Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nnZ3Wry0BWjoQKURAht9AKCZ68gBVNmvTcyjd2VfFq/OjMfWMgCfYpZj CNjzLeeEV02quR7gHXBJMW8= =JaI3 -----END PGP SIGNATURE----- --qDbXVdCdHGoSgWSk-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:10:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 09E0237B405 for ; Sun, 24 Mar 2002 17:10:32 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.11.4/8.11.6) id g2P15Qf44040; Sun, 24 Mar 2002 20:05:26 -0500 (EST) (envelope-from wollman) Date: Sun, 24 Mar 2002 20:05:26 -0500 (EST) From: Garrett Wollman Message-Id: <200203250105.g2P15Qf44040@khavrinen.lcs.mit.edu> To: Kris Kennaway Cc: current@FreeBSD.org Subject: New expr(1) breaks ports In-Reply-To: <20020324165936.A74698@xor.obsecurity.org> References: <20020324165936.A74698@xor.obsecurity.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > expr --prefix=/usr/local : -*prefix=\(.*\) > expr: syntax error > Is expr to blame, or w3m? w3m is to blame. See expr(1) for more details and a workaround which is portable to both historic and POSIX expr implementations. (Allegedly, the new expr behavior is already required of all UNIX-branded systems, so the w3m authors should be well familiar with it. It is an old POSIX.2 requirement.) -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:18:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id C45AE37B400 for ; Sun, 24 Mar 2002 17:18:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 1CC3566D19; Sun, 24 Mar 2002 17:18:12 -0800 (PST) Date: Sun, 24 Mar 2002 17:18:11 -0800 From: Kris Kennaway To: Garrett Wollman Cc: Kris Kennaway , current@FreeBSD.org Subject: Re: New expr(1) breaks ports Message-ID: <20020324171811.B74719@xor.obsecurity.org> References: <20020324165936.A74698@xor.obsecurity.org> <200203250105.g2P15Qf44040@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="WYTEVAkct0FjGQmd" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200203250105.g2P15Qf44040@khavrinen.lcs.mit.edu>; from wollman@lcs.mit.edu on Sun, Mar 24, 2002 at 08:05:26PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --WYTEVAkct0FjGQmd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 24, 2002 at 08:05:26PM -0500, Garrett Wollman wrote: > <= said: >=20 > > expr --prefix=3D/usr/local : -*prefix=3D\(.*\) > > expr: syntax error >=20 > > Is expr to blame, or w3m? >=20 > w3m is to blame. See expr(1) for more details and a workaround which > is portable to both historic and POSIX expr implementations. > (Allegedly, the new expr behavior is already required of all > UNIX-branded systems, so the w3m authors should be well familiar with > it. It is an old POSIX.2 requirement.) OK. Looking at the latest build logs there are only about 13/3500 ports which are broken with this, so it's not too bad. Kris --WYTEVAkct0FjGQmd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nnrTWry0BWjoQKURAghFAJwJnEYa/fymDKENijMUGrKODo5i5wCg+bSj GZ8Cm0iRDcVisYiGw1Jqybk= =Xcz+ -----END PGP SIGNATURE----- --WYTEVAkct0FjGQmd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:35:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id 8582037B405; Sun, 24 Mar 2002 17:35:14 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F260866D19; Sun, 24 Mar 2002 17:35:13 -0800 (PST) Date: Sun, 24 Mar 2002 17:35:13 -0800 From: Kris Kennaway To: bsdimp@FreeBSD.org, current@FreeBSD.org Cc: peter@FreeBSD.org Subject: stdout changes break some ports Message-ID: <20020324173513.A75429@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The changes to the definitions of stdout/stdin/stderr from a while back caused a number of ports to break (somewhere around 84, according to bento). For example, the cap port fails like this: http://bento.freebsd.org/errorlogs/5-latest/cap-6.0.198.log cc -DBYTESWAPPED -DPHASE2 -O -I/mnt/ports/net/cap/work/cap60 -DLWSRV_LPR_LOG -DSTAT_CACHE -DREREAD_AFPVOLS -DUSR_FILE_TYPES -DCREATE_AFPVOL=\"mac\" -DPID_FILE=\"/var/run/aufs.pid\" -DUSEVPRINTF -c ablog.c ablog.c:69: initializer element is not constant where the offending line is: static FILE *lfp = stderr; David O'Brien committed a workaround to the clog port yesterday to move the initializer to main() instead of trying to do it statically. Is this something which is supposed to work? Kris --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nn7RWry0BWjoQKURAgnXAJ9ow2Do0o6pnfZBKLSE3HhG5Njl9gCgi19E i8FkJNnuksdCkxCn6v/PBDU= =i5LL -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:44: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id D3F3E37B405; Sun, 24 Mar 2002 17:43:57 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DDD4A66D19; Sun, 24 Mar 2002 17:43:56 -0800 (PST) Date: Sun, 24 Mar 2002 17:43:56 -0800 From: Kris Kennaway To: des@FreeBSD.org, current@FreeBSD.org Subject: Ports broken by OpenPAM Message-ID: <20020324174356.A75631@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline ..include the following: bftpd-1.0.22.log pam-pgsql-0.5.2_2.log pam_ldap-1.4.0.log pam_mysql-0.4.7.log pam_ssh-1.5.log samba-3.0a15.log vlock-1.3.log Logs available on bento: http://bento.freebsd.org/errorlogs/5-latest/ Kris --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8noDbWry0BWjoQKURArslAKCKEiRA4uVTFBQf7b3DG3vEXIpP1gCgkoO3 jtNcdGDmPoiyNJqobYxTcDA= =pygQ -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:44:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 53D7637B41C; Sun, 24 Mar 2002 17:44:05 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id g2P1i4i04255; Sun, 24 Mar 2002 18:44:04 -0700 (MST) (envelope-from imp@village.org) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id g2P1i2L43934; Sun, 24 Mar 2002 18:44:03 -0700 (MST) (envelope-from imp@village.org) Date: Sun, 24 Mar 2002 18:43:13 -0700 (MST) Message-Id: <20020324.184313.30925676.imp@village.org> To: kris@obsecurity.org Cc: current@FreeBSD.org, peter@FreeBSD.org Subject: Re: stdout changes break some ports From: "M. Warner Losh" In-Reply-To: <20020324173513.A75429@xor.obsecurity.org> References: <20020324173513.A75429@xor.obsecurity.org> X-Mailer: Mew version 2.1 on Emacs 21.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <20020324173513.A75429@xor.obsecurity.org> Kris Kennaway writes: : The changes to the definitions of stdout/stdin/stderr from a while : back caused a number of ports to break (somewhere around 84, according : to bento). For example, the cap port fails like this: : : http://bento.freebsd.org/errorlogs/5-latest/cap-6.0.198.log : : cc -DBYTESWAPPED -DPHASE2 -O -I/mnt/ports/net/cap/work/cap60 -DLWSRV_LPR_LOG -DSTAT_CACHE -DREREAD_AFPVOLS -DUSR_FILE_TYPES -DCREATE_AFPVOL=\"mac\" -DPID_FILE=\"/var/run/aufs.pid\" -DUSEVPRINTF -c ablog.c : ablog.c:69: initializer element is not constant : : where the offending line is: : : static FILE *lfp = stderr; : : David O'Brien committed a workaround to the clog port yesterday to : move the initializer to main() instead of trying to do it statically. : : Is this something which is supposed to work? No. This isn't something that is guaranteed to work per the standards, iirc. The proper fix is to put the initializer in main. The pain level of going back to something the old style is too high to even contemplate reverting. The C standard says: secont 7.19 stderr stdin stdout which are expressions of type ``pointer to FILE'' that point to the FILE objects associated, respectively, with the standard error, input, and output streams. 213The primary use of the freopen function is to change the file associated with a standard text stream (stderr, stdin, or stdout), as those identifiers need not be modifiable lvalues to which the value returned by the fopen function may be assigned. stderr macro, 7.19.1, 7.19.2, 7.19.3 Notice that it doesn't say that stderr is a compile time constant. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 17:54:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id 140AC37B405; Sun, 24 Mar 2002 17:54:37 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5267866D19; Sun, 24 Mar 2002 17:54:36 -0800 (PST) Date: Sun, 24 Mar 2002 17:54:36 -0800 From: Kris Kennaway To: "M. Warner Losh" Cc: kris@obsecurity.org, current@FreeBSD.org, peter@FreeBSD.org Subject: Re: stdout changes break some ports Message-ID: <20020324175436.A75804@xor.obsecurity.org> References: <20020324173513.A75429@xor.obsecurity.org> <20020324.184313.30925676.imp@village.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="UlVJffcvxoiEqYs2" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020324.184313.30925676.imp@village.org>; from imp@village.org on Sun, Mar 24, 2002 at 06:43:13PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Mar 24, 2002 at 06:43:13PM -0700, M. Warner Losh wrote: > : David O'Brien committed a workaround to the clog port yesterday to > : move the initializer to main() instead of trying to do it statically. > :=20 > : Is this something which is supposed to work? >=20 > No. This isn't something that is guaranteed to work per the > standards, iirc. The proper fix is to put the initializer in main. OK. Someone needs to go and fix those 84 ports then. http://bento.freebsd.org/errorlogs/5-latest-4-latest.html is a better resource for finding these than the complete list of build logs, because it only shows the ones which fail in 5.0 but build in 4.x (we have an awful lot of ports which are just completely broken) Kris --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8noNbWry0BWjoQKURAgXgAKCzOj0lVKw3UFu0uNyDXZJHpnd4NACggCBR YuAl5JEt+UPkTHfZ29Lu6pc= =IPVd -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 18:22:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 9918937B405; Sun, 24 Mar 2002 18:22:41 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2P2MdYm016150; Sun, 24 Mar 2002 18:22:39 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2P2LO1C016128; Sun, 24 Mar 2002 18:21:24 -0800 (PST) Date: Sun, 24 Mar 2002 18:21:24 -0800 From: "David O'Brien" To: Robert Watson Cc: current@FreeBSD.ORG Subject: Re: turning off malloc's AJ by default Message-ID: <20020324182124.C15939@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <20020324103200.B8262@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: ; from rwatson@FreeBSD.ORG on Sun, Mar 24, 2002 at 01:59:56PM -0500 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 24, 2002 at 01:59:56PM -0500, Robert Watson wrote: > The goal of DP's is to increase exposure of the development branch in some > key audiences, including the developer community, and community of early > adopters. Part of the discussion that lead up to deciding to follow > through on the DP plan was the perception that many FreeBSD non-kernel > developers are not running 5.0, and that 5.0 had a "fear" element that > didn't seem to match with reality. A part of addressing this is to > provide a window into which 4.x developers can try out 5.x with a lower > level of risk: this is why we had something that resembled a code slush, > and why when greenvm was committed during the code slush, we actually > backed it out of the DP branch (it was later also backed out of the main > development branch). We want to provide a stable and usable version of > 5.0, in as much as that is possible, to provide access to the new > features, services, APIs, etc. We want a reproduceable install that ports > developers can use to learn more about the changing 5.0 environment, among > other things. There is nothing in the above that motivates turning off 'AJ' and INVARIANTS. Please address these two issues based on the above which I do think is what was generally agreed as the motivation for the DP. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 18:42:12 2002 Delivered-To: freebsd-current@freebsd.org Received: from green.gng.co.kr (green.gng.co.kr [211.115.192.3]) by hub.freebsd.org (Postfix) with ESMTP id 0201D37B405 for ; Sun, 24 Mar 2002 18:41:42 -0800 (PST) Received: by GREEN with Internet Mail Service (5.5.2653.19) id ; Mon, 25 Mar 2002 11:28:14 +0900 Message-ID: <72ED4C1E297BD5119BDE00B0D049185201C4C3AA@GREEN> From: =?euc-kr?B?wOW8usij?= To: current@FreeBSD.ORG Subject: [Q] Cardbus NICs drivers : xl and dc Date: Mon, 25 Mar 2002 11:28:12 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="euc-kr" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, everybody... Because I have to test 100Mbps network performance w/ notebook pc, I've installed FreeBSD 5.0 Current (3/22). But, there's some curious things. I have - Xircom RealPort CardBus Ethernet 10/100+Modem 56 (RBEM56G-100) w/ 'dc' driver - 3Com Megahertz 10/100 LAN CardBus (3CXFE575CT) w/ 'xl' driver and w/ iperf 1.2 (/usr/ports/net/iperf). [Q1] dc driver w/ Peer-to-Peer connection I got the different results as follows : Method 1 : Two Xircom NIC on notebook PCs. The forward/reverse results are the same. But, the performance is too poor. :( # iperf -c 192.168.16.76 -w 64k ------------------------------------------------------------ Client connecting to 192.168.16.76, TCP port 5001 TCP window size: 64.2 KByte (WARNING: requested 64.0 KByte) ------------------------------------------------------------ [ 3] local 192.168.16.75 port 49152 connected with 192.168.16.76 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 75.9 MBytes 63.6 Mbits/sec Method 2 : A Xircom on notebook pc and a Intel Pro 10/100+ PCI NIC on desktop pc w/ fxp driver Case 1 ) Iperf server on Xircom (dc) and a client on Intel NIC (fxp) # iperf -s -w 64k ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte ------------------------------------------------------------ [ 4] local 211.115.193.61 port 5001 connected with 192.168.16.73 port 1182 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 112 MBytes 93.9 Mbits/sec Case 2) Iperf server on Intel NIC (fxp) and a client on Xircom (dc) # iperf -c 192.168.16.73 -w 64k ------------------------------------------------------------ Client connecting to 192.168.16.73, TCP port 5001 TCP window size: 64.2 KByte (WARNING: requested 64.0 KByte) ------------------------------------------------------------ [ 3] local 211.115.193.61 port 49152 connected with 192.168.16.73 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 76.3 MBytes 64.0 Mbits/sec What makes a difference ?? [Q2] FE575CT cardbus nic w/ 'xl' dirver shows 'watchdog timeout' error. Is there any clue ?? Thank you for your advanced help. Here is my Kernel config. ====================================================== Last login: Mon Mar 25 10:32:11 2002 from black-pc.gngidc. Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RELEASE (N16384) #3: Fri Feb 22 17:28:27 KST 2002 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search/. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) man page. If you are not familiar with man pages, type `man man'. You may also use `/stand/sysinstall' to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. nrd2:/usr/home/sa 32 $ ssh -l sa 211.115.193.61 The authenticity of host '211.115.193.61 (211.115.193.61)' can't be established. RSA1 key fingerprint is 26:d0:04:a4:85:f9:e1:cd:29:2a:64:31:7c:39:98:4c. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '211.115.193.61' (RSA1) to the list of known hosts. sa@211.115.193.61's password: Last login: Mon Mar 25 10:31:58 2002 from black-pc.gngidc. Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (NMON2) #0: Sat Mar 23 09:40:51 KST 2002 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search/. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) man page. If you are not familiar with man pages, type `man man'. You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. nmon2:/usr/home/sa 17 $ su - Password: nmon2:/root 101 # iperf -s -w 64k ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte ------------------------------------------------------------ [ 4] local 211.115.193.61 port 5001 connected with 192.168.16.73 port 1182 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 112 MBytes 93.9 Mbits/sec ^Cnmon2:/root 102 # iperf -c 192.168.16.73 -w 64k ------------------------------------------------------------ Client connecting to 192.168.16.73, TCP port 5001 TCP window size: 64.2 KByte (WARNING: requested 64.0 KByte) ------------------------------------------------------------ [ 3] local 211.115.193.61 port 49152 connected with 192.168.16.73 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 76.3 MBytes 64.0 Mbits/sec nmon2:/root 103 # nmon2:/root 103 # nmon2:/root 103 # cd /usr/src/sys/i386/conf lnmon2:/usr/src/sys/i386/conf 104 # ls total 154 2 ./ 8 MON2 6 NMON2 2 ../ 2 Makefile 104 NOTES 10 GENERIC 10 NEWCARD 4 gethints.pl 2 GENERIC.hints 2 NEWCARD.hints 2 makeLINT.pl nmon2:/usr/src/sys/i386/conf 105 # mailx -s "NMON2" black@gng.co.kr , relay=root@localhost Mar 25 03:06:16 nmon2 sendmail[67390]: g2OI6GS67344: to=root, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31108, relay=local, dsn=2.0.0, stat=Sent Mar 25 03:06:16 nmon2 sendmail[67387]: unable to qualify my own domain name (nmon2) -- using short name Mar 25 03:06:16 nmon2 sendmail[67383]: unable to qualify my own domain name (nmon2) -- using short name Mar 25 03:06:16 nmon2 sendmail[67387]: gethostbyaddr(211.115.193.45) failed: 1 Mar 25 03:06:16 nmon2 sendmail[67387]: alias database /etc/mail/aliases.db out of date Mar 25 03:06:17 nmon2 sendmail[67383]: gethostbyaddr(211.115.193.45) failed: 1 Mar 25 03:06:17 nmon2 sendmail[67387]: g2OI6G667387: from=root, size=1398, class=0, nrcpts=1, msgid=<200203241806.g2OI6G667387@nmon2>, relay=root@localhost Mar 25 03:06:17 nmon2 sendmail[67393]: g2OI6G667387: to=root, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:00, mailer=local, pri=31398, relay=local, dsn=2.0.0, stat=Sent Mar 25 11:36:16 nmon2 sendmail[294]: My unqualified host name (nmon2) unknown; sleeping for retry nmon2:/usr/src/sys/i386/conf 107 # mailq ^C nmon2:/usr/src/sys/i386/conf 108 # vi /etc/hosts # $FreeBSD: src/etc/hosts,v 1.11.2.2 2001/10/08 09:32:08 ru Exp $ # # Host Database # This file should contain the addresses and aliases # for local hosts that share this file. # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/host.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0 - 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. PLEASE PLEASE PLEASE do not try # to invent your own network numbers but instead get one from your # network provider (if any) or from the Internet Registry (ftp to # rs.internic.net, directory `/templates'). # 211.115.193.62 nmon2 ~ ~ ~ ~ ~ ~ ~ ~ /etc/hosts: 31 lines, 1061 characters. nmon2:/usr/src/sys/i386/conf 109 # mailq ^C nmon2:/usr/src/sys/i386/conf 110 # /usr/sbin/sendmail -qR ^C nmon2:/usr/src/sys/i386/conf 111 # cd /var/spool/mail /var/spool/mail: No such file or directory. nmon2:/usr/src/sys/i386/conf 112 # ls total 154 2 ./ 8 MON2 6 NMON2 2 ../ 2 Makefile 104 NOTES 10 GENERIC 10 NEWCARD 4 gethints.pl 2 GENERIC.hints 2 NEWCARD.hints 2 makeLINT.pl nmon2:/usr/src/sys/i386/conf 113 # cd /var/ nmon2:/var 114 # ls total 42 2 ./ 2 crash/ 2 lib/ 2 run/ 2 yp/ 2 ../ 2 cron/ 2 log/ 2 rwho/ 2 account/ 2 db/ 2 mail/ 2 spool/ 2 at/ 2 games/ 2 msgs/ 2 tmp/ 2 backups/ 2 heimdal/ 2 preserve/ 2 ucd-snmp/ nmon2:/var 115 # ls mail total 38 2 ./ 2 ../ 34 root 0 sa nmon2:/var 116 # cd spool nmon2:/var/spool 117 # ls total 20 2 ./ 2 clientmqueue/ 2 lpd/ 2 opielocks/ 2 uucp/ 2 ../ 2 lock/ 2 mqueue/ 2 output/ 2 uucppublic/ nmon2:/var/spool 118 # cd mqueue/ lnmon2:/var/spool/mqueue 119 # ls total 4 2 ./ 2 ../ nmon2:/var/spool/mqueue 120 # ll total 4 2 drwxr-xr-x 2 root daemon 512 Mar 25 11:37 ./ 2 drwxr-xr-x 10 root wheel 512 Jan 28 22:10 ../ nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # ls total 4 2 ./ 2 ../ nmon2:/var/spool/mqueue 122 # ifconfig lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 dc0: flags=8843 mtu 1500 inet 211.115.193.61 netmask 0xffffff80 broadcast 211.115.193.127 ether 04:06:00:11:38:18 media: Ethernet autoselect (100baseTX ) status: active nmon2:/var/spool/mqueue 123 # cd /usr/src/sys/i386/conf nmon2:/usr/src/sys/i386/conf 124 # vi NMON2 device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard nics included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of ethernet chips device xe # Xircom pccard ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others device wi # WaveLAN/IEEE 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device 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 # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter :q! nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # grep -v "^#" NMON2 > NN nmon2:/usr/src/sys/i386/conf 126 # vi NN machine i386 cpu I686_CPU ident NEWCARD-NMON maxusers 100 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options NFSCLIENT #Network Filesystem Client options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console 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 NMBCLUSTERS=65536 device isa device pci device fdc device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID #Static device numbering 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 apm device pmtimer device pccbb # cardbus (yenta) bridge machine i386 cpu I686_CPU ident NEWCARD-NMON maxusers 100 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options NFSCLIENT #Network Filesystem Client options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console 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 NMBCLUSTERS=65536 device isa device pci device fdc device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID #Static device numbering device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse Last login: Mon Mar 25 10:32:11 2002 from black-pc.gngidc. Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.5-RELEASE (N16384) #3: Fri Feb 22 17:28:27 KST 2002 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search/. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) man page. If you are not familiar with man pages, type `man man'. You may also use `/stand/sysinstall' to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. nrd2:/usr/home/sa 32 $ ssh -l sa 211.115.193.61 The authenticity of host '211.115.193.61 (211.115.193.61)' can't be established. RSA1 key fingerprint is 26:d0:04:a4:85:f9:e1:cd:29:2a:64:31:7c:39:98:4c. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '211.115.193.61' (RSA1) to the list of known hosts. sa@211.115.193.61's password: Last login: Mon Mar 25 10:31:58 2002 from black-pc.gngidc. Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT (NMON2) #0: Sat Mar 23 09:40:51 KST 2002 Welcome to FreeBSD! Before seeking technical support, please use the following resources: o Security advisories and updated errata information for all releases are at http://www.FreeBSD.org/releases/ - always consult the ERRATA section for your release first as it's updated frequently. o The Handbook and FAQ documents are at http://www.FreeBSD.org/ and, along with the mailing lists, can be searched by going to http://www.FreeBSD.org/search/. If the doc distribution has been installed, they're also available formatted in /usr/share/doc. If you still have a question or problem, please take the output of `uname -a', along with any relevant error messages, and email it as a question to the questions@FreeBSD.org mailing list. If you are unfamiliar with FreeBSD's directory layout, please refer to the hier(7) man page. If you are not familiar with man pages, type `man man'. You may also use sysinstall(8) to re-enter the installation and configuration utility. Edit /etc/motd to change this login announcement. nmon2:/usr/home/sa 17 $ su - Password: nmon2:/root 101 # iperf -s -w 64k ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte ------------------------------------------------------------ [ 4] local 211.115.193.61 port 5001 connected with 192.168.16.73 port 1182 [ ID] Interval Transfer Bandwidth [ 4] 0.0-10.0 sec 112 MBytes 93.9 Mbits/sec ^Cnmon2:/root 102 # iperf -c 192.168.16.73 -w 64k ------------------------------------------------------------ Client connecting to 192.168.16.73, TCP port 5001 TCP window size: 64.2 KByte (WARNING: requested 64.0 KByte) ------------------------------------------------------------ [ 3] local 211.115.193.61 port 49152 connected with 192.168.16.73 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 76.3 MBytes 64.0 Mbits/sec nmon2:/root 103 # nmon2:/root 103 # nmon2:/root 103 # cd /usr/src/sys/i386/conf lnmon2:/usr/src/sys/i386/conf 104 # ls total 154 2 ./ 8 MON2 6 NMON2 2 ../ 2 Makefile 104 NOTES 10 GENERIC 10 NEWCARD 4 gethints.pl 2 GENERIC.hints 2 NEWCARD.hints 2 makeLINT.pl nmon2:/usr/src/sys/i386/conf 105 # mailx -s "NMON2" black@gng.co.kr , relay=root@localhost Mar 25 03:06:16 nmon2 sendmail[67390]: g2OI6GS67344: to=root, ctladdr=root (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31108, relay=local, dsn=2.0.0, stat=Sent Mar 25 03:06:16 nmon2 sendmail[67387]: unable to qualify my own domain name (nmon2) -- using short name Mar 25 03:06:16 nmon2 sendmail[67383]: unable to qualify my own domain name (nmon2) -- using short name Mar 25 03:06:16 nmon2 sendmail[67387]: gethostbyaddr(211.115.193.45) failed: 1 Mar 25 03:06:16 nmon2 sendmail[67387]: alias database /etc/mail/aliases.db out of date Mar 25 03:06:17 nmon2 sendmail[67383]: gethostbyaddr(211.115.193.45) failed: 1 Mar 25 03:06:17 nmon2 sendmail[67387]: g2OI6G667387: from=root, size=1398, class=0, nrcpts=1, msgid=<200203241806.g2OI6G667387@nmon2>, relay=root@localhost Mar 25 03:06:17 nmon2 sendmail[67393]: g2OI6G667387: to=root, ctladdr=root (0/0), delay=00:00:01, xdelay=00:00:00, mailer=local, pri=31398, relay=local, dsn=2.0.0, stat=Sent Mar 25 11:36:16 nmon2 sendmail[294]: My unqualified host name (nmon2) unknown; sleeping for retry nmon2:/usr/src/sys/i386/conf 107 # mailq ^C nmon2:/usr/src/sys/i386/conf 108 # vi /etc/hosts # $FreeBSD: src/etc/hosts,v 1.11.2.2 2001/10/08 09:32:08 ru Exp $ # # Host Database # This file should contain the addresses and aliases # for local hosts that share this file. # In the presence of the domain name service or NIS, this file may # not be consulted at all; see /etc/host.conf for the resolution order. # # ::1 localhost localhost.my.domain 127.0.0.1 localhost localhost.my.domain # # Imaginary network. #10.0.0.2 myname.my.domain myname #10.0.0.3 myfriend.my.domain myfriend # # According to RFC 1918, you can use the following IP networks for # private nets which will never be connected to the Internet: # # 10.0.0.0 - 10.255.255.255 # 172.16.0.0 - 172.31.255.255 # 192.168.0.0 - 192.168.255.255 # # In case you want to be able to connect to the Internet, you need # real official assigned numbers. PLEASE PLEASE PLEASE do not try # to invent your own network numbers but instead get one from your # network provider (if any) or from the Internet Registry (ftp to # rs.internic.net, directory `/templates'). # 211.115.193.62 nmon2 ~ ~ ~ ~ ~ ~ ~ ~ /etc/hosts: 31 lines, 1061 characters. nmon2:/usr/src/sys/i386/conf 109 # mailq ^C nmon2:/usr/src/sys/i386/conf 110 # /usr/sbin/sendmail -qR ^C nmon2:/usr/src/sys/i386/conf 111 # cd /var/spool/mail /var/spool/mail: No such file or directory. nmon2:/usr/src/sys/i386/conf 112 # ls total 154 2 ./ 8 MON2 6 NMON2 2 ../ 2 Makefile 104 NOTES 10 GENERIC 10 NEWCARD 4 gethints.pl 2 GENERIC.hints 2 NEWCARD.hints 2 makeLINT.pl nmon2:/usr/src/sys/i386/conf 113 # cd /var/ nmon2:/var 114 # ls total 42 2 ./ 2 crash/ 2 lib/ 2 run/ 2 yp/ 2 ../ 2 cron/ 2 log/ 2 rwho/ 2 account/ 2 db/ 2 mail/ 2 spool/ 2 at/ 2 games/ 2 msgs/ 2 tmp/ 2 backups/ 2 heimdal/ 2 preserve/ 2 ucd-snmp/ nmon2:/var 115 # ls mail total 38 2 ./ 2 ../ 34 root 0 sa nmon2:/var 116 # cd spool nmon2:/var/spool 117 # ls total 20 2 ./ 2 clientmqueue/ 2 lpd/ 2 opielocks/ 2 uucp/ 2 ../ 2 lock/ 2 mqueue/ 2 output/ 2 uucppublic/ nmon2:/var/spool 118 # cd mqueue/ lnmon2:/var/spool/mqueue 119 # ls total 4 2 ./ 2 ../ nmon2:/var/spool/mqueue 120 # ll total 4 2 drwxr-xr-x 2 root daemon 512 Mar 25 11:37 ./ 2 drwxr-xr-x 10 root wheel 512 Jan 28 22:10 ../ nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # nmon2:/var/spool/mqueue 121 # ls total 4 2 ./ 2 ../ nmon2:/var/spool/mqueue 122 # ifconfig lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 dc0: flags=8843 mtu 1500 inet 211.115.193.61 netmask 0xffffff80 broadcast 211.115.193.127 ether 04:06:00:11:38:18 media: Ethernet autoselect (100baseTX ) status: active nmon2:/var/spool/mqueue 123 # cd /usr/src/sys/i386/conf nmon2:/usr/src/sys/i386/conf 124 # vi NMON2 device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard nics included. #device cs # Crystal Semiconductor CS89x0 NIC # 'device ed' requires 'device miibus' device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of ethernet chips device xe # Xircom pccard ethernet # ISA devices that use the old ISA shims #device le # Wireless NIC cards #device an # Aironet 4500/4800 802.11 wireless NICs. #device awi # BayStack 660 and others device wi # WaveLAN/IEEE 802.11 wireless NICs. #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device 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 # IPv6 and IPv4 tunneling #device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter :q! nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # nmon2:/usr/src/sys/i386/conf 125 # grep -v "^#" NMON2 > NN nmon2:/usr/src/sys/i386/conf 126 # vi NN machine i386 cpu I686_CPU ident NEWCARD-NMON maxusers 100 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options NFSCLIENT #Network Filesystem Client options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem (requires PSEUDOFS) options PSEUDOFS #Pseudo-filesystem framework options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console 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 NMBCLUSTERS=65536 device isa device pci device fdc device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID #Static device numbering 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 apm device pmtimer device pccbb # cardbus (yenta) bridge device atkbd # at keyboard device psm # psm mouse device vga # VGA screen device splash device sc 1 device npx device apm device pmtimer device pccbb # cardbus (yenta) bridge device pccard device cardbus device de # DEC/Intel DC21x4x (``Tulip'') device txp # 3Com 3cR990 (``Typhoon'') device vx # 3Com 3c590, 3c595 (``Vortex'') device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device fxp # Intel EtherExpress PRO/100B (82557, 82558) device pcn # AMD Am79C97x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards device ex # Intel EtherExpress Pro/10 and Pro/10+ device ep # Etherlink III based cards device fe # Fujitsu MB8696x based cards device lnc # NE2100, NE32-VL Lance Ethernet cards device sn # SMC's 9000 series of ethernet chips # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" ---------------------------------------------------------- GNG Networks/GNGIDC/System Team System Engineer Seongho Chang E-Mail : black@gngidc.net mblck@chollian.net Tel +822-2105-6072 Fax +822-2105-6100 ---------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 20:57:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id 6E58437B405 for ; Sun, 24 Mar 2002 20:57:52 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2P4vlYm034522; Sun, 24 Mar 2002 20:57:47 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2P4uW37034493; Sun, 24 Mar 2002 20:56:32 -0800 (PST) Date: Sun, 24 Mar 2002 20:56:32 -0800 From: "David O'Brien" To: Matthew Dillon Cc: freebsd-current@freebsd.org Subject: Re: can't build world on alpha Message-ID: <20020324205632.A34463@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200203231902.g2NJ2QS71349@apollo.backplane.com> <20020324085932.D26339@dragon.nuxi.com> <200203241738.g2OHcgh76708@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200203241738.g2OHcgh76708@apollo.backplane.com>; from dillon@apollo.backplane.com on Sun, Mar 24, 2002 at 09:38:42AM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, Mar 24, 2002 at 09:38:42AM -0800, Matthew Dillon wrote: > :On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote: > :> Anyone have any ideas? I'm trying to build the latest -current > :> (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'. I just verified one can build last night's (March 24th 3am) -CURRENT on a Feb 10th' 4.5-STABLE box. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Mar 24 23:16:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc52.attbi.com (rwcrmhc52.attbi.com [216.148.227.88]) by hub.freebsd.org (Postfix) with ESMTP id 5760737B404; Sun, 24 Mar 2002 23:16:28 -0800 (PST) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc52.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020325071628.FJUZ1147.rwcrmhc52.attbi.com@blossom.cjclark.org>; Mon, 25 Mar 2002 07:16:28 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g2P7GRq84155; Sun, 24 Mar 2002 23:16:27 -0800 (PST) (envelope-from cjc) Date: Sun, 24 Mar 2002 23:16:27 -0800 From: "Crist J. Clark" To: nsouch@freebsd.org Cc: current@freebsd.org Subject: Broken bktr(4) module Message-ID: <20020324231627.A84096@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I believe the recent changes to the bktr(4) module Makefile broke it, ===> bktr ===> bktr/bktr make: don't know how to make smbus.h. Stop *** Error code 2 Stop in /usr/src/sys/modules/bktr. *** Error code 1 . . . A fresh checkout on freefall still seems to have this problem. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@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 Mar 25 0:34:23 2002 Delivered-To: freebsd-current@freebsd.org Received: from espresso.q9media.com (espresso.q9media.com [216.254.138.122]) by hub.freebsd.org (Postfix) with ESMTP id B24F337B404; Mon, 25 Mar 2002 00:34:19 -0800 (PST) Received: (from mike@localhost) by espresso.q9media.com (8.11.6/8.11.6) id g2P8SJO84737; Mon, 25 Mar 2002 03:28:19 -0500 (EST) (envelope-from mike) Date: Mon, 25 Mar 2002 03:28:19 -0500 From: Mike Barcroft To: current@FreeBSD.org Cc: nsouch@FreeBSD.org Subject: LINT/NOTES broken after recent bktr(4) change Message-ID: <20020325032819.A81971@espresso.q9media.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Organization: The FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/work/src/sys -I/work/src/sys/dev -I/work/src/sys/contrib/dev/acpica -I/work/src/sys/contrib/ipfilter -I/work/src/sys/../include -DGPROF -DGPROF4 -DGUPROF -D_KERNEL -ffreestanding -include opt_global.h -fno-common -malign-functions=4 -fno-builtin -mpreferred-stack-boundary=2 -Werror -pg -mprofiler-epilogue /work/src/sys/dev/bktr/bktr_i2c.c /work/src/sys/dev/bktr/bktr_i2c.c: In function `bt848_i2c_attach': /work/src/sys/dev/bktr/bktr_i2c.c:87: structure has no member named `i2c_sc' /work/src/sys/dev/bktr/bktr_i2c.c:92: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:93: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:95: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:101: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:103: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c: In function `bt848_i2c_detach': /work/src/sys/dev/bktr/bktr_i2c.c:113: structure has no member named `i2c_sc' /work/src/sys/dev/bktr/bktr_i2c.c:119: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:119: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:122: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:122: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c: In function `bti2c_smb_callback': /work/src/sys/dev/bktr/bktr_i2c.c:132: structure has no member named `i2c_sc' /work/src/sys/dev/bktr/bktr_i2c.c:141: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:142: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:149: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:150: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c: In function `bti2c_iic_callback': /work/src/sys/dev/bktr/bktr_i2c.c:165: structure has no member named `i2c_sc' /work/src/sys/dev/bktr/bktr_i2c.c:174: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:175: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:182: dereferencing pointer to incomplete type /work/src/sys/dev/bktr/bktr_i2c.c:183: dereferencing pointer to incomplete type *** Error code 1 I think I've narrowed down the problem: : revision 1.20 : date: 2002/03/23 15:47:08; author: nsouch; state: Exp; lines: +112 -192 : Major rework of the iicbus/smbus framework: : : - VIA chipset SMBus controllers added : - alpm driver updated : - Support for dynamic modules added : - bktr FreeBSD smbus updated but not tested ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ : - cleanup Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 0:59:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 2356737B404; Mon, 25 Mar 2002 00:59:41 -0800 (PST) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id g2P8xb017103; Mon, 25 Mar 2002 00:59:37 -0800 Date: Mon, 25 Mar 2002 00:59:37 -0800 From: Brooks Davis To: Mike Barcroft Cc: current@FreeBSD.ORG, nsouch@FreeBSD.ORG Subject: Re: LINT/NOTES broken after recent bktr(4) change Message-ID: <20020325005937.A16702@Odin.AC.HMC.Edu> References: <20020325032819.A81971@espresso.q9media.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020325032819.A81971@espresso.q9media.com>; from mike@FreeBSD.ORG on Mon, Mar 25, 2002 at 03:28:19AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2002 at 03:28:19AM -0500, Mike Barcroft wrote: >=20 > I think I've narrowed down the problem: > : revision 1.20 > : date: 2002/03/23 15:47:08; author: nsouch; state: Exp; lines: +112 -= 192 > : Major rework of the iicbus/smbus framework: > :=20 > : - VIA chipset SMBus controllers added > : - alpm driver updated > : - Support for dynamic modules added > : - bktr FreeBSD smbus updated but not tested > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > : - cleanup FWIW, if you uncomment "option BKTR_USE_FREEBSD_SMBUS" in NOTES, the resulting LINT will compile. Unfortunatly, it won't link due to a different error related to this commit that I haven't tracked down. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8nub4XY6L6fI4GtQRAghSAKDH0iTombmr4SUuL3EmHeK9RtATKACgza/f sijWKgBFt4WoxByaps0UN3U= =aT9/ -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 3:15:14 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtpzilla2.xs4all.nl (smtpzilla2.xs4all.nl [194.109.127.138]) by hub.freebsd.org (Postfix) with ESMTP id E521B37B400; Mon, 25 Mar 2002 03:15:08 -0800 (PST) Received: from router.hackerheaven.org (ipv6.hackerheaven.org [80.126.0.97]) by smtpzilla2.xs4all.nl (8.12.0/8.12.0) with ESMTP id g2PBF7ju039080; Mon, 25 Mar 2002 12:15:07 +0100 (CET) Received: by router.hackerheaven.org (Postfix, from userid 1000) id 7CDAE1C05; Mon, 25 Mar 2002 12:14:26 +0100 (CET) Date: Mon, 25 Mar 2002 12:14:26 +0100 From: Emiel Kollof To: "Crist J. Clark" Cc: nsouch@freebsd.org, current@freebsd.org Subject: Re: Broken bktr(4) module Message-ID: <20020325111426.GB9393@hackerheaven.org> References: <20020324231627.A84096@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020324231627.A84096@blossom.cjclark.org> User-Agent: Mutt/1.3.28i X-Mailer: Mutt 1.3.23i (2001-10-09) X-Editor: Vim http://www.vim.org/ X-Info: http://www.hackerheaven.org/ X-Info2: http://www.cmdline.org/ X-Info3: http://www.coolvibe.org/ X-message-flag: Out of cheese error! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Crist J. Clark (cjc@freebsd.org) wrote: > I believe the recent changes to the bktr(4) module Makefile broke it, > > ===> bktr > ===> bktr/bktr > make: don't know how to make smbus.h. Stop > *** Error code 2 > > Stop in /usr/src/sys/modules/bktr. > *** Error code 1 Hmm, I am not alone I see here.. Already filed a PR about it. Cheers, Emiel -- The universe is like a safe to which there is a combination -- but the combination is locked up in the safe. -- Peter DeVries To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 5:26:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from mongrel.pacific.net.au (mongrel.pacific.net.au [61.8.0.107]) by hub.freebsd.org (Postfix) with ESMTP id 732BD37B41C for ; Mon, 25 Mar 2002 05:26:39 -0800 (PST) Received: from dungeon.home (ppp31.dyn249.pacific.net.au [203.143.249.31]) by mongrel.pacific.net.au (8.9.3/8.9.3/Debian 8.9.3-21) with ESMTP id AAA20688; Tue, 26 Mar 2002 00:25:06 +1100 X-Authentication-Warning: mongrel.pacific.net.au: Host ppp31.dyn249.pacific.net.au [203.143.249.31] claimed to be dungeon.home Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.11.6/8.11.1) with ESMTP id g2PDRHu21490; Mon, 25 Mar 2002 23:27:17 +1000 (EST) (envelope-from mckay) Message-Id: <200203251327.g2PDRHu21490@dungeon.home> To: "Ilmar S. Habibulin" Cc: freebsd-current@freebsd.org, mckay@thehub.com.au Subject: Re: if_dc broken in -current References: <200203221433.g2MEXqZ16447@dungeon.home> <20020322093822.D42469-100000@fledge.watson.org> In-Reply-To: <20020322093822.D42469-100000@fledge.watson.org> from "Ilmar S. Habibulin" at "Fri, 22 Mar 2002 15:40:32 +0000" Date: Mon, 25 Mar 2002 23:27:17 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Friday, 22nd March 2002, "Ilmar S. Habibulin" wrote: >On Sat, 23 Mar 2002, Stephen McKay wrote: > >> It's been quite a while since I updated my -current box, but when I did, >> I was surprised to find that my DE500 network card (21143 chip) had stopped >> working. The switch showed no link. Ifconfig showed "no carrier". > >I've had the simular problem. Now i have media option set to needed value >in ifconfig_dc0 variable. This helped. What sort of card do you have? The output of dmesg would help. Have you tried 4.5 on this machine? Of course the dc driver should autonegotiate (and does so when I revert rev 1.56). Your info could help trace this problem. Stephen. PS I'm now assuming the number of -current users that use PNIC and Davicom cards with the dc driver is exactly zero. Oh well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 5:48: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 3E92537B41B for ; Mon, 25 Mar 2002 05:47:58 -0800 (PST) Received: by energyhq.homeip.net (Postfix, from userid 1001) id 880153FC39; Mon, 25 Mar 2002 14:48:30 +0100 (CET) Date: Mon, 25 Mar 2002 14:48:30 +0100 From: Miguel Mendez To: current@freebsd.org Subject: BTX halted Message-ID: <20020325144830.A17956@energyhq.homeip.net> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, I've tried to install two snapshots (20th and 21st of March) on my Thinkpad laptop, and after the loader has finished reading mfsroot.flp I get a register dump and a message saying BTX halted. Any hints of what could be causing this? The problem didn't show last time I used a snapshost, last December or 4.5-R install disks.=20 Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --BOKacYhQ+x31HxR3 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nyqtnLctrNyFFPERAj0YAJ9ubpUUYYl3Dpcma2HNpUdBxkfzVACgqWa6 cihd3AbHX9keO7Sz6vh6Qb0= =WnpW -----END PGP SIGNATURE----- --BOKacYhQ+x31HxR3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 6: 5:18 2002 Delivered-To: freebsd-current@freebsd.org Received: from web21101.mail.yahoo.com (web21101.mail.yahoo.com [216.136.227.103]) by hub.freebsd.org (Postfix) with SMTP id 551C837B400 for ; Mon, 25 Mar 2002 06:05:15 -0800 (PST) Message-ID: <20020325140514.92844.qmail@web21101.mail.yahoo.com> Received: from [62.254.0.5] by web21101.mail.yahoo.com via HTTP; Mon, 25 Mar 2002 06:05:14 PST Date: Mon, 25 Mar 2002 06:05:14 -0800 (PST) From: Hiten Pandya Reply-To: hiten@uk.FreeBSD.org Subject: Re: BTX halted To: Miguel Mendez , current@freebsd.org In-Reply-To: <20020325144830.A17956@energyhq.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --- Miguel Mendez wrote: > Hi, > > I've tried to install two snapshots (20th and 21st of March) on my > Thinkpad laptop, and after the loader has finished reading mfsroot.flp I > get a register dump and a message saying BTX halted. Any hints of what > could be causing this? The problem didn't show last time I used a > snapshost, last December or 4.5-R install disks. Hi Miguel, Could you please send us the register dump. Someone will analyse it and will get back to you. Or could you please file a Problem Report for this issue. :) Thanks, Regards, -- Hiten Pandya -- __________________________________________________ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards® http://movies.yahoo.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 6:24:17 2002 Delivered-To: freebsd-current@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id ACD3637B416 for ; Mon, 25 Mar 2002 06:24:00 -0800 (PST) Received: by energyhq.homeip.net (Postfix, from userid 1001) id 301583FC39; Mon, 25 Mar 2002 15:24:39 +0100 (CET) Date: Mon, 25 Mar 2002 15:24:39 +0100 From: Miguel Mendez To: hiten@uk.FreeBSD.org Cc: current@freebsd.org Subject: Re: BTX halted Message-ID: <20020325152439.B17956@energyhq.homeip.net> Mail-Followup-To: hiten@uk.FreeBSD.org, current@freebsd.org References: <20020325144830.A17956@energyhq.homeip.net> <20020325140514.92844.qmail@web21101.mail.yahoo.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="3uo+9/B/ebqu+fSQ" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020325140514.92844.qmail@web21101.mail.yahoo.com>; from hitmaster2k@yahoo.com on Mon, Mar 25, 2002 at 06:05:14AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --3uo+9/B/ebqu+fSQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2002 at 06:05:14AM -0800, Hiten Pandya wrote: > Could you please send us the register dump. Someone will analyse it and > will get back to you. Or could you please file a Problem Report for this > issue. :) Here's the dump, I want to open a PR too, what the category would be? i386?=20 int=3D00000006 err=3D00000000 efl=3D00010092 eip=3Dc0309927 eax=3Dc082e000 ebx=3D0082cc00 ecx=3D00000000 edx=3D00000002 esi=3D0082c000 edi=3D00834000 ebp=3Dc082fd94 esp=3Dc082fd78 cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 cs:eip=3Dff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 ss:esp=3D00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 BTX halted =20 Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --3uo+9/B/ebqu+fSQ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8nzMmnLctrNyFFPERAqwJAKDBOJhFlCqEU8vzLqI9MOfPcn6n9gCfdMmE 7mlV6vaD/gDqzvaB1szYxD4= =FJoS -----END PGP SIGNATURE----- --3uo+9/B/ebqu+fSQ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 6:47:58 2002 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 7B16937B419 for ; Mon, 25 Mar 2002 06:47:54 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id A52335348; Mon, 25 Mar 2002 15:47:52 +0100 (CET) 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: Kris Kennaway Cc: current@FreeBSD.org Subject: Re: Ports broken by OpenPAM References: <20020324174356.A75631@xor.obsecurity.org> From: Dag-Erling Smorgrav Date: 25 Mar 2002 15:47:51 +0100 In-Reply-To: <20020324174356.A75631@xor.obsecurity.org> Message-ID: Lines: 30 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Kris Kennaway writes: > bftpd-1.0.22.log > pam-pgsql-0.5.2_2.log Not tested. > pam_ldap-1.4.0.log Not my problem; I sent the maintainer a patch ages ago. > pam_mysql-0.4.7.log Not tested. > pam_ssh-1.5.log This port should die, pam_ssh(8) is in the base system and the port is way out of date. > samba-3.0a15.log See previous mail. > vlock-1.3.log Not tested. 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 Mon Mar 25 6:51:42 2002 Delivered-To: freebsd-current@freebsd.org Received: from shumai.marcuscom.com (rdu57-17-158.nc.rr.com [66.57.17.158]) by hub.freebsd.org (Postfix) with ESMTP id 992B337B417 for ; Mon, 25 Mar 2002 06:51:39 -0800 (PST) Received: from localhost (marcus@localhost) by shumai.marcuscom.com (8.11.6/8.11.6) with ESMTP id g2PEpZm48071; Mon, 25 Mar 2002 09:51:35 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: shumai.marcuscom.com: marcus owned process doing -bs Date: Mon, 25 Mar 2002 09:51:35 -0500 (EST) From: Joe Clarke To: Dag-Erling Smorgrav Cc: Kris Kennaway , Subject: Re: Ports broken by OpenPAM In-Reply-To: Message-ID: <20020325095032.F47578-100000@shumai.marcuscom.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25 Mar 2002, Dag-Erling Smorgrav wrote: > Kris Kennaway writes: > > bftpd-1.0.22.log > > pam-pgsql-0.5.2_2.log > > Not tested. > > > pam_ldap-1.4.0.log > > Not my problem; I sent the maintainer a patch ages ago. Really? I never received it. Please send it again. Thanks. Joe [snip] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 7: 2:37 2002 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 21C3737B420 for ; Mon, 25 Mar 2002 07:00:37 -0800 (PST) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 2F8B55346; Mon, 25 Mar 2002 16:00:34 +0100 (CET) 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: Joe Clarke Cc: Kris Kennaway , Subject: Re: Ports broken by OpenPAM References: <20020325095032.F47578-100000@shumai.marcuscom.com> From: Dag-Erling Smorgrav Date: 25 Mar 2002 16:00:34 +0100 In-Reply-To: <20020325095032.F47578-100000@shumai.marcuscom.com> Message-ID: Lines: 11 User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-=-= Joe Clarke writes: > Really? I never received it. Please send it again. Thanks. Here's an updated (but untested) version. DES -- Dag-Erling Smorgrav - des@ofug.org --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=pam_ldap.diff --- pam_ldap.c.orig Mon Mar 25 15:54:28 2002 +++ pam_ldap.c Mon Mar 25 15:54:29 2002 @@ -126,12 +126,7 @@ #include "pam_ldap.h" #include "md5.h" -#ifdef HAVE_SECURITY_PAM_MISC_H - /* FIXME: is there something better to check? */ #define CONST_ARG const -#else -#define CONST_ARG -#endif #ifndef HAVE_LDAP_MEMFREE #define ldap_memfree(x) free(x) @@ -2843,11 +2838,11 @@ { _conv_sendmsg (appconv, "Password change aborted", PAM_ERROR_MSG, no_warn); -#ifdef PAM_AUTHTOK_RECOVERY_ERR - return PAM_AUTHTOK_RECOVERY_ERR; -#else +#ifdef PAM_AUTHTOK_RECOVER_ERR return PAM_AUTHTOK_RECOVER_ERR; -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ +#else + return PAM_AUTHTOK_RECOVERY_ERR; +#endif /* PAM_AUTHTOK_RECOVER_ERR */ } else { @@ -2887,11 +2882,11 @@ syslog (LOG_ERR, "pam_ldap: error getting old authentication token (%s)", pam_strerror (pamh, rc)); -#ifdef PAM_AUTHTOK_RECOVERY_ERR - return PAM_AUTHTOK_RECOVERY_ERR; -#else +#ifdef PAM_AUTHTOK_RECOVER_ERR return PAM_AUTHTOK_RECOVER_ERR; -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ +#else + return PAM_AUTHTOK_RECOVERY_ERR; +#endif /* PAM_AUTHTOK_RECOVER_ERR */ } if (try_first_pass || use_first_pass) @@ -2901,11 +2896,11 @@ newpass = NULL; if (use_first_pass && newpass == NULL) -#ifdef PAM_AUTHTOK_RECOVERY_ERR - return PAM_AUTHTOK_RECOVERY_ERR; -#else +#ifdef PAM_AUTHTOK_RECOVER_ERR return PAM_AUTHTOK_RECOVER_ERR; -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ +#else + return PAM_AUTHTOK_RECOVERY_ERR; +#endif /* PAM_AUTHTOK_RECOVER_ERR */ } tries = 0; @@ -2955,11 +2950,11 @@ } else { -#ifdef PAM_AUTHTOK_RECOVERY_ERR - return PAM_AUTHTOK_RECOVERY_ERR; -#else +#ifdef PAM_AUTHTOK_RECOVER_ERR return PAM_AUTHTOK_RECOVER_ERR; -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ +#else + return PAM_AUTHTOK_RECOVERY_ERR; +#endif /* PAM_AUTHTOK_RECOVER_ERR */ } if (cmiscptr == NULL) @@ -2991,11 +2986,11 @@ { _conv_sendmsg (appconv, "Password change aborted", PAM_ERROR_MSG, no_warn); -#ifdef PAM_AUTHTOK_RECOVERY_ERR - return PAM_AUTHTOK_RECOVERY_ERR; -#else +#ifdef PAM_AUTHTOK_RECOVER_ERR return PAM_AUTHTOK_RECOVER_ERR; -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ +#else + return PAM_AUTHTOK_RECOVERY_ERR; +#endif /* PAM_AUTHTOK_RECOVER_ERR */ } } else if (!strcmp (newpass, miscptr)) --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 7:14: 3 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id AEEBB37B41D for ; Mon, 25 Mar 2002 07:13:45 -0800 (PST) Received: from localhost (ilmar@localhost) by fledge.watson.org (8.11.6/8.11.6) with ESMTP id g2PFDbE93910; Mon, 25 Mar 2002 10:13:37 -0500 (EST) (envelope-from ilmar@watson.org) Date: Mon, 25 Mar 2002 10:13:37 -0500 (EST) From: "Ilmar S. Habibulin" To: Stephen McKay Cc: freebsd-current@freebsd.org Subject: Re: if_dc broken in -current In-Reply-To: <200203251327.g2PDRHu21490@dungeon.home> Message-ID: <20020325100450.C93820-200000@fledge.watson.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-331194511-1017069217=:93820" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-331194511-1017069217=:93820 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 25 Mar 2002, Stephen McKay wrote: > What sort of card do you have? The output of dmesg would help. Have you > tried 4.5 on this machine? I have some noname nic with Intel 21143 chip. dmesg attached. I'm using only trustedbsd_mac branch on my ws. > Of course the dc driver should autonegotiate (and does so when I revert > rev 1.56). Your info could help trace this problem. Well, i don't think this is the problem. Hardware became too much inteligent now a days, so one have to use his own hands to make this hardware work like user wants it to work. Maybe just put some FAQ about dc(4) and autoconfigurable hubs/switches? --0-331194511-1017069217=:93820 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=dmesg Content-Transfer-Encoding: BASE64 Content-ID: <20020325101337.W93820@fledge.watson.org> Content-Description: Content-Disposition: attachment; filename=dmesg Q29weXJpZ2h0IChjKSAxOTkyLTIwMDIgVGhlIEZyZWVCU0QgUHJvamVjdC4N CkNvcHlyaWdodCAoYykgMTk3OSwgMTk4MCwgMTk4MywgMTk4NiwgMTk4OCwg MTk4OSwgMTk5MSwgMTk5MiwgMTk5MywgMTk5NA0KCVRoZSBSZWdlbnRzIG9m IHRoZSBVbml2ZXJzaXR5IG9mIENhbGlmb3JuaWEuIEFsbCByaWdodHMgcmVz ZXJ2ZWQuDQpGcmVlQlNEIDUuMC1UcnVzdGVkQlNEICM1OiBNb24gTWFyIDI1 IDE1OjQ1OjMyIE1TSyAyMDAyDQogICAgcm9vdEB3cy1pbG1hcjovdXNyL3Rt cC90dC9tYWMvc3lzL2kzODYvY29tcGlsZS9XU19JTE1BUg0KUHJlbG9hZGVk IGVsZiBrZXJuZWwgIi9ib290L2tlcm5lbC9rZXJuZWwiIGF0IDB4YzAzZTMw MDAuDQpQcmVsb2FkZWQgZWxmIG1vZHVsZSAiL2Jvb3Qva2VybmVsL2FjcGku a28iIGF0IDB4YzAzZTMwYTguDQpUaW1lY291bnRlciAiaTgyNTQiICBmcmVx dWVuY3kgMTE5MzE4MiBIeg0KVGltZWNvdW50ZXIgIlRTQyIgIGZyZXF1ZW5j eSA3MDYyOTM0ODcgSHoNCkNQVTogQU1EIER1cm9uKHRtKSBQcm9jZXNzb3Ig KDcwNi4yOS1NSHogNjg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkF1dGhl bnRpY0FNRCIgIElkID0gMHg2MzEgIFN0ZXBwaW5nID0gMQ0KICBGZWF0dXJl cz0weDE4M2Y5ZmY8RlBVLFZNRSxERSxQU0UsVFNDLE1TUixQQUUsTUNFLENY OCxTRVAsTVRSUixQR0UsTUNBLENNT1YsUEFULFBTRTM2LE1NWCxGWFNSPg0K ICBBTUQgRmVhdHVyZXM9MHhjMDQ0MDAwMDxSU1ZELEFNSUUsRFNQLDNETm93 IT4NCnJlYWwgbWVtb3J5ICA9IDEzNDEzNTgwOCAoMTMwOTkySyBieXRlcykN CmF2YWlsIG1lbW9yeSA9IDEyNjQxODk0NCAoMTIzNDU2SyBieXRlcykNClNl Y3VyaXR5IHBvbGljeTogVHJ1c3RlZEJTRCBNQUMvQlNEIEV4dGVuZGVkICh0 cnVzdGVkYnNkX21hY19ic2RleHRlbmRlZCkNClNlY3VyaXR5IHBvbGljeTog VHJ1c3RlZEJTRCBNQUMvQmliYSAodHJ1c3RlZGJzZF9tYWNfYmliYSkNClNl Y3VyaXR5IHBvbGljeTogVHJ1c3RlZEJTRCBNQUMvTUxTICh0cnVzdGVkYnNk X21hY19tbHMpDQpTZWN1cml0eSBwb2xpY3k6IFRydXN0ZWRCU0QgTUFDL1RF ICh0cnVzdGVkYnNkX21hY190ZSkNClNlY3VyaXR5IHBvbGljeTogVHJ1c3Rl ZEJTRCBNQUMvTm9uZSAodHJ1c3RlZGJzZF9tYWNfbm9uZSkNClBlbnRpdW0g UHJvIE1UUlIgc3VwcG9ydCBlbmFibGVkDQpVc2luZyAkUElSIHRhYmxlLCA5 IGVudHJpZXMgYXQgMHhjMDBmMTcyMA0KbnB4MDogPG1hdGggcHJvY2Vzc29y PiBvbiBtb3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVyZmFjZQ0KYWNw aTA6IDxBU1VTICAgQTdWLTEzMyA+IG9uIG1vdGhlcmJvYXJkDQphY3BpMDog cG93ZXIgYnV0dG9uIGlzIGhhbmRsZWQgYXMgYSBmaXhlZCBmZWF0dXJlIHBy b2dyYW1taW5nIG1vZGVsLg0KQUNQSSB0aW1lciBsb29rcyBHT09EIG1pbiA9 IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1lciBsb29rcyBHT09E IG1pbiA9IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1lciBsb29r cyBHT09EIG1pbiA9IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1l ciBsb29rcyBHT09EIG1pbiA9IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KQUNQ SSB0aW1lciBsb29rcyBHT09EIG1pbiA9IDEsIG1heCA9IDIsIHdpZHRoID0g Mg0KQUNQSSB0aW1lciBsb29rcyBHT09EIG1pbiA9IDEsIG1heCA9IDIsIHdp ZHRoID0gMg0KQUNQSSB0aW1lciBsb29rcyBHT09EIG1pbiA9IDEsIG1heCA9 IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1lciBsb29rcyBHT09EIG1pbiA9IDEs IG1heCA9IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1lciBsb29rcyBHT09EIG1p biA9IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KQUNQSSB0aW1lciBsb29rcyBH T09EIG1pbiA9IDEsIG1heCA9IDIsIHdpZHRoID0gMg0KVGltZWNvdW50ZXIg IkFDUEktZmFzdCIgIGZyZXF1ZW5jeSAzNTc5NTQ1IEh6DQphY3BpX3RpbWVy MDogPDI0LWJpdCB0aW1lciBhdCAzLjU3OTU0NU1Iej4gcG9ydCAweGU0MDgt MHhlNDBiIG9uIGFjcGkwDQphY3BpX2NwdTA6IDxDUFU+IG9uIGFjcGkwDQph Y3BpX2J1dHRvbjA6IDxQb3dlciBCdXR0b24+IG9uIGFjcGkwDQphY3BpX3Bj aWIwOiA8SG9zdC1QQ0kgYnJpZGdlPiBwb3J0IDB4Y2Y4LTB4Y2ZmIG9uIGFj cGkwDQpwY2kwOiA8UENJIGJ1cz4gb24gYWNwaV9wY2liMA0KcGNpYjE6IDxQ Q0ktUENJIGJyaWRnZT4gYXQgZGV2aWNlIDEuMCBvbiBwY2kwDQpwY2kxOiA8 UENJIGJ1cz4gb24gcGNpYjENCnBjaTE6IDxkaXNwbGF5LCBWR0E+IGF0IGRl dmljZSAwLjAgKG5vIGRyaXZlciBhdHRhY2hlZCkNCmlzYWIwOiA8UENJLUlT QSBicmlkZ2U+IGF0IGRldmljZSA0LjAgb24gcGNpMA0KaXNhMDogPElTQSBi dXM+IG9uIGlzYWIwDQphdGFwY2kwOiA8VklBIDgyQzY4NiBBVEExMDAgY29u dHJvbGxlcj4gcG9ydCAweGI4MDAtMHhiODBmIGF0IGRldmljZSA0LjEgb24g cGNpMA0KYXRhMDogYXQgMHgxZjAgaXJxIDE0IG9uIGF0YXBjaTANCmF0YTE6 IGF0IDB4MTcwIGlycSAxNSBvbiBhdGFwY2kwDQp1aGNpMDogPFZJQSA4M0M1 NzIgVVNCIGNvbnRyb2xsZXI+IHBvcnQgMHhiNDAwLTB4YjQxZiBpcnEgNSBh dCBkZXZpY2UgNC4yIG9uIHBjaTANCnVzYjA6IDxWSUEgODNDNTcyIFVTQiBj b250cm9sbGVyPiBvbiB1aGNpMA0KdXNiMDogVVNCIHJldmlzaW9uIDEuMA0K dWh1YjA6IFZJQSBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAw LzEuMDAsIGFkZHIgMQ0KdWh1YjA6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJs ZSwgc2VsZiBwb3dlcmVkDQp1aGNpMTogPFZJQSA4M0M1NzIgVVNCIGNvbnRy b2xsZXI+IHBvcnQgMHhiMDAwLTB4YjAxZiBpcnEgNSBhdCBkZXZpY2UgNC4z IG9uIHBjaTANCnVzYjE6IDxWSUEgODNDNTcyIFVTQiBjb250cm9sbGVyPiBv biB1aGNpMQ0KdXNiMTogVVNCIHJldmlzaW9uIDEuMA0KdWh1YjE6IFZJQSBV SENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIg MQ0KdWh1YjE6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dl cmVkDQpkYzA6IDxJbnRlbCAyMTE0MyAxMC8xMDBCYXNlVFg+IHBvcnQgMHg5 NDAwLTB4OTQ3ZiBtZW0gMHhkZTgwMDAwMC0weGRlODAwM2ZmIGlycSAxMCBh dCBkZXZpY2UgMTEuMCBvbiBwY2kwDQpkYzA6IEV0aGVybmV0IGFkZHJlc3M6 IDAwOjgwOmFkOjkwOmI0OjM4DQptaWlidXMwOiA8TUlJIGJ1cz4gb24gZGMw DQpkY3BoeTA6IDxJbnRlbCAyMTE0MyBOV0FZIG1lZGlhIGludGVyZmFjZT4g b24gbWlpYnVzMA0KZGNwaHkwOiAgMTBiYXNlVCwgMTBiYXNlVC1GRFgsIDEw MGJhc2VUWCwgMTAwYmFzZVRYLUZEWCwgYXV0bw0KZGMwOiBpbml0aWFsaXpl ZCBhcyB0cnVzdGVkIGludGVyZmFjZQ0KZmRjMDogPGVuaGFuY2VkIGZsb3Bw eSBjb250cm9sbGVyIChpODIwNzcsIE5FNzIwNjUgb3IgY2xvbmUpPiBwb3J0 IDB4M2Y3LDB4M2YyLTB4M2Y1IGlycSA2IG9uIGFjcGkwDQpmZGMwOiBGSUZP IGVuYWJsZWQsIDggYnl0ZXMgdGhyZXNob2xkDQpmZDA6IDwxNDQwLUtCIDMu NSIgZHJpdmU+IG9uIGZkYzAgZHJpdmUgMA0KcHBjMCBwb3J0IDB4Nzc4LTB4 NzdiLDB4Mzc4LTB4MzdmIGlycSA3IG9uIGFjcGkwDQpwcGMwOiBTTUMtbGlr ZSBjaGlwc2V0IChFQ1AvRVBQL1BTMi9OSUJCTEUpIGluIENPTVBBVElCTEUg bW9kZQ0KcHBjMDogRklGTyB3aXRoIDE2LzE2LzggYnl0ZXMgdGhyZXNob2xk DQpscHQwOiA8UHJpbnRlcj4gb24gcHBidXMwDQpscHQwOiBJbnRlcnJ1cHQt ZHJpdmVuIHBvcnQNCnBwaTA6IDxQYXJhbGxlbCBJL08+IG9uIHBwYnVzMA0K cGxpcDA6IDxQTElQIG5ldHdvcmsgaW50ZXJmYWNlPiBvbiBwcGJ1czANCmxw MDogaW5pdGlhbGl6ZWQgYXMgdW50cnVzdGVkIGludGVyZmFjZQ0Kc2lvMCBw b3J0IDB4M2Y4LTB4M2ZmIGlycSA0IG9uIGFjcGkwDQpzaW8wOiB0eXBlIDE2 NTUwQQ0Kc2lvMSBwb3J0IDB4MmY4LTB4MmZmIGlycSAzIG9uIGFjcGkwDQpz aW8xOiB0eXBlIDE2NTUwQQ0KYXRrYmRjMDogPEtleWJvYXJkIGNvbnRyb2xs ZXIgKGk4MDQyKT4gcG9ydCAweDY0LDB4NjAgaXJxIDEgb24gYWNwaTANCmF0 a2JkMDogPEFUIEtleWJvYXJkPiBmbGFncyAweDEgaXJxIDEgb24gYXRrYmRj MA0Ka2JkMCBhdCBhdGtiZDANCnBzbTA6IDxQUy8yIE1vdXNlPiBpcnEgMTIg b24gYXRrYmRjMA0KcHNtMDogbW9kZWwgTmV0TW91c2UvTmV0U2Nyb2xsIE9w dGljYWwsIGRldmljZSBJRCAwDQpvcm0wOiA8T3B0aW9uIFJPTT4gYXQgaW9t ZW0gMHhjMDAwMC0weGM3ZmZmIG9uIGlzYTANCnNjMDogPFN5c3RlbSBjb25z b2xlPiBhdCBmbGFncyAweDEwMCBvbiBpc2EwDQpzYzA6IFZHQSA8MTYgdmly dHVhbCBjb25zb2xlcywgZmxhZ3M9MHgzMDA+DQp2Z2EwOiA8R2VuZXJpYyBJ U0EgVkdBPiBhdCBwb3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhi ZmZmZiBvbiBpc2EwDQpsbzA6IGludGlhbGl6ZWQgYXMgbG9jYWxob3N0IGlu dGVyZmFjZQ0KSVBzZWM6IEluaXRpYWxpemVkIFNlY3VyaXR5IEFzc29jaWF0 aW9uIFByb2Nlc3NpbmcuDQphY3BpX2NwdTogQ1BVIHRocm90dGxpbmcgZW5h YmxlZCwgMTYgc3RlcHMgZnJvbSAxMDAlIHRvIDYuMiUNCmFkMDogOTc5N01C IDxRVUFOVFVNIEZJUkVCQUxMUCBBUzEwLjI+IFsxOTkwNi8xNi82M10gYXQg YXRhMC1tYXN0ZXIgVURNQTEwMA0KTW91bnRpbmcgcm9vdCBmcm9tIHVmczov ZGV2L2FkMHMxYQ0KcGlkIDIzMCAoZ2V0cG1hYyksIHVpZCAxMDAxOiBleGl0 ZWQgb24gc2lnbmFsIDExIChjb3JlIGR1bXBlZCkNCg== --0-331194511-1017069217=:93820-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 7:37:28 2002 Delivered-To: freebsd-current@freebsd.org Received: from gyros.marcuscom.com (dhcp-64-102-60-33.cisco.com [64.102.60.33]) by hub.freebsd.org (Postfix) with ESMTP id 5086937B419 for ; Mon, 25 Mar 2002 07:37:20 -0800 (PST) Received: (from marcus@localhost) by gyros.marcuscom.com (8.11.6/8.11.6) id g2PFbEO49999; Mon, 25 Mar 2002 10:37:14 -0500 (EST) (envelope-from marcus@marcuscom.com) X-Authentication-Warning: gyros.marcuscom.com: marcus set sender to marcus@marcuscom.com using -f Subject: Re: Ports broken by OpenPAM From: Joe Marcus Clarke To: Dag-Erling Smorgrav Cc: Kris Kennaway , current@FreeBSD.ORG In-Reply-To: References: <20020325095032.F47578-100000@shumai.marcuscom.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-PlmHEcAD+sCKf7bWK5C7" X-Mailer: Ximian Evolution 1.0.3 Date: 25 Mar 2002 10:37:14 -0500 Message-Id: <1017070634.49855.13.camel@gyros.marcuscom.com> Mime-Version: 1.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --=-PlmHEcAD+sCKf7bWK5C7 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2002-03-25 at 10:00, Dag-Erling Smorgrav wrote: > Joe Clarke writes: > > Really? I never received it. Please send it again. Thanks. >=20 > Here's an updated (but untested) version. Thanks. As soon as I finish get my -current machine built, I'll test these out. =20 Joe >=20 > DES > --=20 > Dag-Erling Smorgrav - des@ofug.org >=20 > ---- >=20 > --- pam_ldap.c.orig Mon Mar 25 15:54:28 2002 > +++ pam_ldap.c Mon Mar 25 15:54:29 2002 > @@ -126,12 +126,7 @@ > #include "pam_ldap.h" > #include "md5.h" > =20 > -#ifdef HAVE_SECURITY_PAM_MISC_H > - /* FIXME: is there something better to check? */ > #define CONST_ARG const > -#else > -#define CONST_ARG > -#endif > =20 > #ifndef HAVE_LDAP_MEMFREE > #define ldap_memfree(x) free(x) > @@ -2843,11 +2838,11 @@ > { > _conv_sendmsg (appconv, "Password change aborted", > PAM_ERROR_MSG, no_warn); > -#ifdef PAM_AUTHTOK_RECOVERY_ERR > - return PAM_AUTHTOK_RECOVERY_ERR; > -#else > +#ifdef PAM_AUTHTOK_RECOVER_ERR > return PAM_AUTHTOK_RECOVER_ERR; > -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ > +#else > + return PAM_AUTHTOK_RECOVERY_ERR; > +#endif /* PAM_AUTHTOK_RECOVER_ERR */ > } > else > { > @@ -2887,11 +2882,11 @@ > syslog (LOG_ERR, > "pam_ldap: error getting old authentication token (%s)", > pam_strerror (pamh, rc)); > -#ifdef PAM_AUTHTOK_RECOVERY_ERR > - return PAM_AUTHTOK_RECOVERY_ERR; > -#else > +#ifdef PAM_AUTHTOK_RECOVER_ERR > return PAM_AUTHTOK_RECOVER_ERR; > -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ > +#else > + return PAM_AUTHTOK_RECOVERY_ERR; > +#endif /* PAM_AUTHTOK_RECOVER_ERR */ > } > =20 > if (try_first_pass || use_first_pass) > @@ -2901,11 +2896,11 @@ > newpass =3D NULL; > =20 > if (use_first_pass && newpass =3D=3D NULL) > -#ifdef PAM_AUTHTOK_RECOVERY_ERR > - return PAM_AUTHTOK_RECOVERY_ERR; > -#else > +#ifdef PAM_AUTHTOK_RECOVER_ERR > return PAM_AUTHTOK_RECOVER_ERR; > -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ > +#else > + return PAM_AUTHTOK_RECOVERY_ERR; > +#endif /* PAM_AUTHTOK_RECOVER_ERR */ > } > =20 > tries =3D 0; > @@ -2955,11 +2950,11 @@ > } > else > { > -#ifdef PAM_AUTHTOK_RECOVERY_ERR > - return PAM_AUTHTOK_RECOVERY_ERR; > -#else > +#ifdef PAM_AUTHTOK_RECOVER_ERR > return PAM_AUTHTOK_RECOVER_ERR; > -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ > +#else > + return PAM_AUTHTOK_RECOVERY_ERR; > +#endif /* PAM_AUTHTOK_RECOVER_ERR */ > } > =20 > if (cmiscptr =3D=3D NULL) > @@ -2991,11 +2986,11 @@ > { > _conv_sendmsg (appconv, "Password change aborted", > PAM_ERROR_MSG, no_warn); > -#ifdef PAM_AUTHTOK_RECOVERY_ERR > - return PAM_AUTHTOK_RECOVERY_ERR; > -#else > +#ifdef PAM_AUTHTOK_RECOVER_ERR > return PAM_AUTHTOK_RECOVER_ERR; > -#endif /* PAM_AUTHTOK_RECOVERY_ERR */ > +#else > + return PAM_AUTHTOK_RECOVERY_ERR; > +#endif /* PAM_AUTHTOK_RECOVER_ERR */ > } > } > else if (!strcmp (newpass, miscptr)) --=-PlmHEcAD+sCKf7bWK5C7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEABECAAYFAjyfRCoACgkQb2iPiv4Uz4cUhwCgjYzC76spGZ/UhofznWzxY4VC u9cAn1yFmNAuJsfS/9oi8+YZVU1g5o15 =RSRG -----END PGP SIGNATURE----- --=-PlmHEcAD+sCKf7bWK5C7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 7:41:10 2002 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id BE9BF37B41A for ; Mon, 25 Mar 2002 07:41:07 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 95D3A319BE5; Mon, 25 Mar 2002 09:41:09 -0600 (CST) Date: Mon, 25 Mar 2002 09:41:09 -0600 From: "David W. Chapman Jr." To: current@freebsd.org Subject: ntfs causing kernel panic Message-ID: <20020325154109.GA8847@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has anyone seen mounting an NTFS drive casing a kernel panic? I'd love to give the output, but I'm not sure how to redirect the output into a file so I can post it here. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 8: 1:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from november.debolaz.com (november.debolaz.com [193.71.19.191]) by hub.freebsd.org (Postfix) with ESMTP id E041337B419 for ; Mon, 25 Mar 2002 08:01:27 -0800 (PST) Received: from amphibic.com (november [193.71.19.191]) by november.debolaz.com (Postfix) with SMTP id A135113603B; Mon, 25 Mar 2002 17:01:25 +0100 (CET) Received: from 62.179.190.82 (SquirrelMail authenticated user debolaz) by webmail.debolaz.com with HTTP; Mon, 25 Mar 2002 17:01:25 +0100 (CET) Message-ID: <4496.62.179.190.82.1017072085.squirrel@webmail.debolaz.com> Date: Mon, 25 Mar 2002 17:01:25 +0100 (CET) Subject: Re: BTX halted From: "Anders Nor Berle" To: In-Reply-To: <20020325140514.92844.qmail@web21101.mail.yahoo.com> References: <20020325140514.92844.qmail@web21101.mail.yahoo.com> X-Priority: 3 Importance: Normal X-MSMail-Priority: Normal Cc: X-Mailer: SquirrelMail (version 1.2.5) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, here's a dump from me too, it's 5.0-CURRENT-20020313-JPSNAP, the first snap from snapshots.jp.freebsd.org which has the problem. int=00000006 err=00000000 efl=00000006 eip=c03069d7 eax=00000081 ebx=0082fc00 ecx=00000000 edx=00000102 esi=0082f000 edi=00837000 ebp=c0832d94 esp=c0832d94 cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 cs:eip=ff ff 18 57 56 53 a1 44-15 37 c0 a3 c4 76 38 c0 a1 48 15 37 c0 a3 7c 77-38 c0 05 a0 1d ff ff a3 ss:esp=00 00 00 00 94 93 12 c0-00 70 83 00 00 f0 82 00 00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00 BTX halted > > Could you please send us the register dump. Someone will analyse it and will get > back to you. Or could you please file a Problem Report for this issue. :) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 8:40:16 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail13.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by hub.freebsd.org (Postfix) with ESMTP id B2E4E37B405 for ; Mon, 25 Mar 2002 08:40:11 -0800 (PST) Received: (qmail 8320 invoked from network); 25 Mar 2002 16:40:10 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 16:40:10 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PGeov82715; Mon, 25 Mar 2002 11:40:50 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020322204145.J88743-100000@mail.chesapeake.net> Date: Mon, 25 Mar 2002 11:40:12 -0500 (EST) From: John Baldwin To: Jeff Roberson Subject: RE: Peculiar(?) slowdown with -CURRENT as of 21 March Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Mar-2002 Jeff Roberson wrote: >> >> I saw some similar weirdness in my test machines last night where a dual >> processor DS20 (Alpha 21264 500x2) beat out a PII Xeon 450x4. Normally > the >> quad xeon beats the DS20. The quad xeon was using -j16 but was about 74% >> idle. >> The DS20 had used -j8. I didn't get a chacne to run top to see how it was >> doing during hte world since I didn't notice the weirdness until last > night >> after the DS20 had finsihed but the quad xeon was still chugging along. >> > > Are you both running with WITNESS and INVARIANTS? UMA is slightly slower > with these options on than the original malloc & vm_zone code. I'm not > sure why it would be even worse for SMP machines though. So maybe it > isn't UMA at all but it's worth looking into. Yes. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Mon Mar 25 8:41:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212]) by hub.freebsd.org (Postfix) with ESMTP id D810337B423 for ; Mon, 25 Mar 2002 08:40:35 -0800 (PST) Received: (qmail 7991 invoked from network); 25 Mar 2002 16:40:34 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail12.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 16:40:34 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PGfEv82736; Mon, 25 Mar 2002 11:41:14 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020325152439.B17956@energyhq.homeip.net> Date: Mon, 25 Mar 2002 11:40:36 -0500 (EST) From: John Baldwin To: Miguel Mendez Subject: Re: BTX halted Cc: current@freebsd.org, hiten@uk.FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25-Mar-2002 Miguel Mendez wrote: > On Mon, Mar 25, 2002 at 06:05:14AM -0800, Hiten Pandya wrote: > >> Could you please send us the register dump. Someone will analyse it and >> will get back to you. Or could you please file a Problem Report for this >> issue. :) > > Here's the dump, I want to open a PR too, what the category would be? > i386? > > int=00000006 err=00000000 efl=00010092 eip=c0309927 > eax=c082e000 ebx=0082cc00 ecx=00000000 edx=00000002 > esi=0082c000 edi=00834000 ebp=c082fd94 esp=c082fd78 > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 > cs:eip=ff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 > c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 > > ss:esp=00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > BTX halted Weird, it looks like you actually got into the kernel before blowing up. Did you have debug copy of the kernel with you. If so, can you do a listing of the address in %eip? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Mon Mar 25 8:41:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail16.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by hub.freebsd.org (Postfix) with ESMTP id DF74737B405 for ; Mon, 25 Mar 2002 08:40:29 -0800 (PST) Received: (qmail 24466 invoked from network); 25 Mar 2002 16:40:28 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail16.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 16:40:28 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PGf8v82732; Mon, 25 Mar 2002 11:41:08 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020323122141.A68389@freebie.xs4all.nl> Date: Mon, 25 Mar 2002 11:40:30 -0500 (EST) From: John Baldwin To: Wilko Bulte Subject: RE: witness panic on Alpha Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 23-Mar-2002 Wilko Bulte wrote: > Fri Mar 22 19:06:37 CET 2002 > > FreeBSD/alpha (ds10.wbnet) (ttyd0) > > login: syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/auth.log: No such file or directory > Mar 22 21:55:23 ds10 kernel: pid 27885 (telnetd), uid 0: exited on signal 11 > (co > re dumped) > Mar 22 21:55:30 ds10 kernel: pid 28342 (telnetd), uid 0: exited on signal 11 > (co > re dumped) > syslogd: /var/log/auth.log: No such file or directory > syslogd: /var/log/auth.log: No such file or directory > panic: blockable sleep lock (sleep mutex) vnode_free_list @ > /usr/src/sys/kern/vf > s_subr.c:2678 > panic > Stopped at Debugger+0x34: zapnot v0,#0xf,a0 > db> > db> tb > No such command > db> bt > No such command > db> st > Stopped at Debugger+0x38: call_pal osf1_swpipl > db> stack > No such command > db> trace > Debugger() at Debugger+0x3c > panic() at panic+0x100 > witness_lock() at witness_lock+0xb4 > _mtx_lock_flags() at _mtx_lock_flags+0xd8 > vfree() at vfree+0x30 > vm_page_free_toq() at vm_page_free_toq+0x200 > vm_page_free() at vm_page_free+0x2c > vm_page_alloc() at vm_page_alloc+0x1ac > pmap_growkernel() at pmap_growkernel+0x3e8 > vm_map_findspace() at vm_map_findspace+0x144 > kmem_alloc() at kmem_alloc+0x9c > _zget() at _zget+0x244 > zalloc() at zalloc+0x78 > getnewvnode() at getnewvnode+0x470 > ffs_vget() at ffs_vget+0x168 > ufs_lookup() at ufs_lookup+0xf78 > ufs_vnoperate() at ufs_vnoperate+0x2c > vfs_cache_lookup() at vfs_cache_lookup+0x3cc > ufs_vnoperate() at ufs_vnoperate+0x2c > lookup() at lookup+0x4d0 > namei() at namei+0x308 > lstat() at lstat+0x50 > syscall() at syscall+0x318 > XentSys() at XentSys+0x64 > --- syscall (190, FreeBSD ELF, lstat) --- > --- user mode --- > db> Is this reproducible? If so, can you do a 'show locks'? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Mon Mar 25 8:43:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 5839737B41A for ; Mon, 25 Mar 2002 08:43:31 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g2PGhUo79497; Mon, 25 Mar 2002 08:43:30 -0800 (PST) (envelope-from david) Date: Mon, 25 Mar 2002 08:43:30 -0800 (PST) From: David Wolfskill Message-Id: <200203251643.g2PGhUo79497@bunrab.catwhisker.org> To: brooks@one-eyed-alien.net Subject: Re: LINT/NOTES broken after recent bktr(4) change Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Mon, 25 Mar 2002 00:59:37 -0800 >From: Brooks Davis >FWIW, if you uncomment "option BKTR_USE_FREEBSD_SMBUS" in NOTES, the >resulting LINT will compile. Unfortunatly, it won't link due to a >different error related to this commit that I haven't tracked down. Would that, perhaps, be similar to: linking kernel.debug pcf.o: In function `pcf_attach': /usr/src/sys/i386/isa/pcf.c(.text+0x1f1): undefined reference to `iicbus_alloc_bus' *** Error code 1 Stop in /common/S3/obj/usr/src/sys/LAPTOP_30W. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. g1-9(5.0-C)[2] ? If so, I just did a search through my -CURENT /usr/src/sys, loooking for "iicbus_alloc_bus". Results aren't too promising: ./dev/iicbus/iiconf.h:102:extern device_t iicbus_alloc_bus(device_t); ./i386/isa/pcf.c:200: pcf->iicbus = iicbus_alloc_bus(pcfdev); Looks to me like a declaration & a reference, but no definition. :-(, david -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 8:47:45 2002 Delivered-To: freebsd-current@freebsd.org Received: from energyhq.homeip.net (213-97-200-73.uc.nombres.ttd.es [213.97.200.73]) by hub.freebsd.org (Postfix) with ESMTP id 368FC37B41B; Mon, 25 Mar 2002 08:47:39 -0800 (PST) Received: by energyhq.homeip.net (Postfix, from userid 1001) id D763A3FC39; Mon, 25 Mar 2002 17:48:11 +0100 (CET) Date: Mon, 25 Mar 2002 17:48:11 +0100 From: Miguel Mendez To: John Baldwin Cc: current@freebsd.org, hiten@uk.FreeBSD.org Subject: Re: BTX halted Message-ID: <20020325174811.C17956@energyhq.homeip.net> Mail-Followup-To: John Baldwin , current@freebsd.org, hiten@uk.FreeBSD.org References: <20020325152439.B17956@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="PuGuTyElPB9bOcsM" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Mar 25, 2002 at 11:40:36AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --PuGuTyElPB9bOcsM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2002 at 11:40:36AM -0500, John Baldwin wrote: > > int=3D00000006 err=3D00000000 efl=3D00010092 eip=3Dc0309927 > > eax=3Dc082e000 ebx=3D0082cc00 ecx=3D00000000 edx=3D00000002 > > esi=3D0082c000 edi=3D00834000 ebp=3Dc082fd94 esp=3Dc082fd78 > > cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 > > cs:eip=3Dff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 > > c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 > >=20 > > ss:esp=3D00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > > 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > > BTX halted >=20 > Weird, it looks like you actually got into the kernel before blowing up. > Did you have debug copy of the kernel with you. If so, can you do a > listing of the address in %eip? I don't have a debug kernel, those are the boot floppies downloaded from current.freebsd.org. If it helps, the snapshot floppies from 11th of March work, every floppy made after that date fails with the same error. I'm going to install that snapshot, upgrade the system and try to reproduce the error with a debug kernel. Cheers, --=20 Miguel Mendez - flynn@energyhq.homeip.net GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt EnergyHQ :: http://www.energyhq.tk FreeBSD - The power to serve! --PuGuTyElPB9bOcsM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8n1TLnLctrNyFFPERAoiIAKCG1e6l8jVOEFMMArEOdW5aJU5uCwCgud6K V69dHhcsp+dtpC4SqPP/LBw= =fage -----END PGP SIGNATURE----- --PuGuTyElPB9bOcsM-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 9:30:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 151BC37B421 for ; Mon, 25 Mar 2002 09:30:23 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2PHUCk95504; Mon, 25 Mar 2002 12:30:12 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 25 Mar 2002 12:30:11 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Ilmar S. Habibulin" Cc: Stephen McKay , freebsd-current@freebsd.org Subject: Re: if_dc broken in -current In-Reply-To: <20020325100450.C93820-200000@fledge.watson.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Mar 2002, Ilmar S. Habibulin wrote: > On Mon, 25 Mar 2002, Stephen McKay wrote: > > > What sort of card do you have? The output of dmesg would help. Have you > > tried 4.5 on this machine? > I have some noname nic with Intel 21143 chip. dmesg attached. I'm using > only trustedbsd_mac branch on my ws. > > > Of course the dc driver should autonegotiate (and does so when I revert > > rev 1.56). Your info could help trace this problem. > Well, i don't think this is the problem. Hardware became too much > inteligent now a days, so one have to use his own hands to make this > hardware work like user wants it to work. Maybe just put some FAQ about > dc(4) and autoconfigurable hubs/switches? I think I have an identical problem involving a Linksys ethernet card using if_dc. I have to force it to negotiate 10mbps, since it fails to negotiate anything higher with my 10/100 switch. No idea why at all. dc0: port 0xe800-0xe8ff mem 0xfebfff00-0xfebfffff irq 10 at device 19.0 on pci0 dc0: Ethernet address: 00:a0:cc:35:3e:56 miibus0: on dc0 dcphy0: on miibus0 dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto dc0: flags=8843 mtu 1500 inet6 fe80::2a0:ccff:fe35:3e56%dc0 prefixlen 64 scopeid 0x1 inet 192.168.11.150 netmask 0xffffff00 broadcast 192.168.11.255 ether 00:a0:cc:35:3e:56 media: Ethernet 10baseT/UTP status: active If I set it to auto-negotiate or hard-set to 100mbps, no packets go back or forth. I've had this problem for at least a year, if not longer. I have the same problem with 4.4-STABLE using an identical card on different hardware: if it tries to negotiate 100mbps, then it simply doesn't work. If I force it to 10, it's fine. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 9:31:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 84FE137B47C; Mon, 25 Mar 2002 09:31:06 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g2PHUqX79613; Mon, 25 Mar 2002 09:30:52 -0800 (PST) (envelope-from david) Date: Mon, 25 Mar 2002 09:30:52 -0800 (PST) From: David Wolfskill Message-Id: <200203251730.g2PHUqX79613@bunrab.catwhisker.org> To: brooks@one-eyed-alien.net, nsouch@FreeBSD.ORG Subject: Re: LINT/NOTES broken after recent bktr(4) change Cc: current@FreeBSD.ORG In-Reply-To: <200203251643.g2PGhUo79497@bunrab.catwhisker.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >Date: Mon, 25 Mar 2002 08:43:30 -0800 (PST) >From: David Wolfskill >linking kernel.debug >pcf.o: In function `pcf_attach': >/usr/src/sys/i386/isa/pcf.c(.text+0x1f1): undefined reference to `iicbus_alloc_bus' >*** Error code 1 >Looks to me like a declaration & a reference, but no definition. OK; I was able to get past this point by reverting src/sys/dev/iicbus/iiconf.c frlom 1.13 to 1.12. (The 1.12 version of the file had a definition of iicbus_alloc_bus() that the 1.13 change removed.) Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 10:15: 4 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id ED14737B404 for ; Mon, 25 Mar 2002 10:14:59 -0800 (PST) Received: (qmail 13238 invoked from network); 25 Mar 2002 18:14:58 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 18:14:58 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PIFZv83023; Mon, 25 Mar 2002 13:15:35 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020325174811.C17956@energyhq.homeip.net> Date: Mon, 25 Mar 2002 13:14:57 -0500 (EST) From: John Baldwin To: Miguel Mendez Subject: Re: BTX halted Cc: hiten@uk.FreeBSD.org, current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25-Mar-2002 Miguel Mendez wrote: > On Mon, Mar 25, 2002 at 11:40:36AM -0500, John Baldwin wrote: >> > int=00000006 err=00000000 efl=00010092 eip=c0309927 >> > eax=c082e000 ebx=0082cc00 ecx=00000000 edx=00000002 >> > esi=0082c000 edi=00834000 ebp=c082fd94 esp=c082fd78 >> > cs=0008 ds=0010 es=0010 fs=0010 gs=0010 ss=0010 >> > cs:eip=ff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 >> > c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 >> > >> > ss:esp=00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 >> > 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 >> > BTX halted >> >> Weird, it looks like you actually got into the kernel before blowing up. >> Did you have debug copy of the kernel with you. If so, can you do a >> listing of the address in %eip? > > I don't have a debug kernel, those are the boot floppies downloaded from > current.freebsd.org. If it helps, the snapshot floppies from 11th of > March work, every floppy made after that date fails with the same error. > I'm going to install that snapshot, upgrade the system and try to > reproduce the error with a debug kernel. Ok. If you can figure out what kernel commit broke things that would be very helpful. Thanks! -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Mon Mar 25 10:29:47 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id EA6EE37B427; Mon, 25 Mar 2002 10:29:12 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g2PITBN70368; Mon, 25 Mar 2002 19:29:11 +0100 (CET) (envelope-from wkb) Date: Mon, 25 Mar 2002 19:29:11 +0100 From: Wilko Bulte To: John Baldwin Cc: freebsd-current@FreeBSD.org Subject: Re: witness panic on Alpha Message-ID: <20020325192911.D70216@freebie.xs4all.nl> References: <20020323122141.A68389@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Mar 25, 2002 at 11:40:30AM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: > > lstat() at lstat+0x50 > > syscall() at syscall+0x318 > > XentSys() at XentSys+0x64 > > --- syscall (190, FreeBSD ELF, lstat) --- > > --- user mode --- > > db> > > Is this reproducible? If so, can you do a 'show locks'? Sofar it happened once. But I'll try to catch it again. -- | / o / /_ _ |/|/ / / /( (_) Bulte wilko@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 Mar 25 10:37: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from mass.dis.org (dhcp45-24.dis.org [216.240.45.24]) by hub.freebsd.org (Postfix) with ESMTP id 657B537B417 for ; Mon, 25 Mar 2002 10:36:53 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g2PIZfe00862; Mon, 25 Mar 2002 10:35:41 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200203251835.g2PIZfe00862@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: Miguel Mendez Cc: hiten@uk.FreeBSD.org, current@freebsd.org Subject: Re: BTX halted In-reply-to: Your message of "Mon, 25 Mar 2002 15:24:39 +0100." <20020325152439.B17956@energyhq.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 25 Mar 2002 10:35:41 -0800 From: Michael Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Please don't file a PR against something like this in -current until you've established that it's not a transient problem. In this case, it looks like a possibly corrupt kernel; you're dying very early on after jumping into the kernel. > On Mon, Mar 25, 2002 at 06:05:14AM -0800, Hiten Pandya wrote: > > > Could you please send us the register dump. Someone will analyse it and > > will get back to you. Or could you please file a Problem Report for this > > issue. :) > > Here's the dump, I want to open a PR too, what the category would be? > i386?=20 > > int=3D00000006 err=3D00000000 efl=3D00010092 eip=3Dc0309927 > eax=3Dc082e000 ebx=3D0082cc00 ecx=3D00000000 edx=3D00000002 > esi=3D0082c000 edi=3D00834000 ebp=3Dc082fd94 esp=3Dc082fd78 > cs=3D0008 ds=3D0010 es=3D0010 fs=3D0010 gs=3D0010 ss=3D0010 > cs:eip=3Dff ff a1 a4 48 37 c0 a3 - ac aa 38 c0 a1 a8 48 37 > c0 a3 84 ab 38 c0 05 a0 - 1d ff ff a3 60 ab 38 c0 > > ss:esp=3D00 40 83 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > 00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00 > BTX halted =20 > > Cheers, > --=20 > Miguel Mendez - flynn@energyhq.homeip.net > GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt > EnergyHQ :: http://www.energyhq.tk > FreeBSD - The power to serve! > > --3uo+9/B/ebqu+fSQ > Content-Type: application/pgp-signature > Content-Disposition: inline > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.0.6 (FreeBSD) > Comment: For info see http://www.gnupg.org > > iD8DBQE8nzMmnLctrNyFFPERAqwJAKDBOJhFlCqEU8vzLqI9MOfPcn6n9gCfdMmE > 7mlV6vaD/gDqzvaB1szYxD4= > =FJoS > -----END PGP SIGNATURE----- > > --3uo+9/B/ebqu+fSQ-- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 11:36:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by hub.freebsd.org (Postfix) with ESMTP id 4DAF737B41A for ; Mon, 25 Mar 2002 11:36:49 -0800 (PST) Received: from bremen.shuttle.de (localhost [127.0.0.1]) by bremen.shuttle.de (Postfix) with ESMTP id 8310817D6A for ; Mon, 25 Mar 2002 20:36:47 +0100 (CET) Received: (from uucp@localhost) by bremen.shuttle.de (8.12.2/8.12.2/Debian -5) with UUCP id g2PJalwQ018161 for freebsd-current@freebsd.org; Mon, 25 Mar 2002 20:36:47 +0100 Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.2/8.11.6) id g2PIStaI001969 for freebsd-current@freebsd.org; Mon, 25 Mar 2002 19:28:55 +0100 (CET) (envelope-from schweikh) Date: Mon, 25 Mar 2002 19:28:54 +0100 From: Jens Schweikhardt To: freebsd-current@freebsd.org Subject: Re: What changed with the resolver such that it won't use /etc/hosts anymore? Message-ID: <20020325192854.A1512@schweikhardt.net> References: <20020319131821.A93853@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: <20020319131821.A93853@dragon.nuxi.com>; from obrien@freebsd.org on Tue, Mar 19, 2002 at 01:18:21PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David et al, # So what broke this? # -- David (obrien@FreeBSD.org) Has this been fixed? I observe the same on FreeBSD 5.0-CURRENT #4: Fri Mar 8 19:51:15 CET 2002 and am wondering if a make world would fix this. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 12:43:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by hub.freebsd.org (Postfix) with ESMTP id D6F8E37B400; Mon, 25 Mar 2002 12:43:43 -0800 (PST) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.2/8.12.2) with ESMTP id g2PKhWYm013196; Mon, 25 Mar 2002 12:43:32 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.2/8.12.2/Submit) id g2PKgGQR013193; Mon, 25 Mar 2002 12:42:16 -0800 (PST) Date: Mon, 25 Mar 2002 12:42:16 -0800 From: "David O'Brien" To: Emiel Kollof Cc: "Crist J. Clark" , nsouch@freebsd.org, current@freebsd.org Subject: Re: Broken bktr(4) module Message-ID: <20020325124216.A13059@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20020324231627.A84096@blossom.cjclark.org> <20020325111426.GB9393@hackerheaven.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020325111426.GB9393@hackerheaven.org>; from coolvibe@hackerheaven.org on Mon, Mar 25, 2002 at 12:14: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: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 25, 2002 at 12:14:26PM +0100, Emiel Kollof wrote: > * Crist J. Clark (cjc@freebsd.org) wrote: > > I believe the recent changes to the bktr(4) module Makefile broke it, > > > > ===> bktr > > ===> bktr/bktr > > make: don't know how to make smbus.h. Stop > > *** Error code 2 > > > > Stop in /usr/src/sys/modules/bktr. > > *** Error code 1 > > Hmm, I am not alone I see here.. Already filed a PR about it. What was the PR number. I already fixed it. For build problem things like this, emailing the list is better as people will see it MUCH quicker. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 12:57:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 828AD37B404; Mon, 25 Mar 2002 12:57:14 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g2PKvC600462; Mon, 25 Mar 2002 21:57:12 +0100 (CET) (envelope-from wkb) Date: Mon, 25 Mar 2002 21:57:12 +0100 From: Wilko Bulte To: John Baldwin Cc: freebsd-current@FreeBSD.org Subject: Re: witness panic on Alpha Message-ID: <20020325215712.A257@freebie.xs4all.nl> References: <20020323122141.A68389@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Mar 25, 2002 at 11:40:30AM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: Looks like a different one: db> trace siointr1() at siointr1+0x17c siointr() at siointr+0x40 isa_handle_fast_intr() at isa_handle_fast_intr+0x28 alpha_dispatch_intr() at alpha_dispatch_intr+0xdc interrupt() at interrupt+0x108 XentInt() at XentInt+0x28 --- interrupt (from ipl 0) --- --- user mode --- db> and db> show locks exclusive (spin mutex) sio (0xfffffc0000648d20) locked @ /usr/src/sys/dev/sio/sio.c:1634 db> This is a serial console Wilko > > No such command > > db> trace > > Debugger() at Debugger+0x3c > > panic() at panic+0x100 > > witness_lock() at witness_lock+0xb4 > > _mtx_lock_flags() at _mtx_lock_flags+0xd8 > > vfree() at vfree+0x30 > > vm_page_free_toq() at vm_page_free_toq+0x200 > > vm_page_free() at vm_page_free+0x2c > > vm_page_alloc() at vm_page_alloc+0x1ac > > pmap_growkernel() at pmap_growkernel+0x3e8 > > vm_map_findspace() at vm_map_findspace+0x144 > > kmem_alloc() at kmem_alloc+0x9c > > _zget() at _zget+0x244 > > zalloc() at zalloc+0x78 > > getnewvnode() at getnewvnode+0x470 > > ffs_vget() at ffs_vget+0x168 > > ufs_lookup() at ufs_lookup+0xf78 > > ufs_vnoperate() at ufs_vnoperate+0x2c > > vfs_cache_lookup() at vfs_cache_lookup+0x3cc > > ufs_vnoperate() at ufs_vnoperate+0x2c > > lookup() at lookup+0x4d0 > > namei() at namei+0x308 > > lstat() at lstat+0x50 > > syscall() at syscall+0x318 > > XentSys() at XentSys+0x64 > > --- syscall (190, FreeBSD ELF, lstat) --- > > --- user mode --- > > db> > > Is this reproducible? If so, can you do a 'show locks'? -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 13: 0:41 2002 Delivered-To: freebsd-current@freebsd.org Received: from rahl.dorm.duke.edu (rahl.dorm.duke.edu [152.16.249.139]) by hub.freebsd.org (Postfix) with ESMTP id 6953937B419 for ; Mon, 25 Mar 2002 13:00:25 -0800 (PST) Received: (from scott@localhost) by rahl.dorm.duke.edu (8.11.6/8.11.6) id g2PL0TD39756 for freebsd-current@freebsd.org; Mon, 25 Mar 2002 16:00:29 -0500 (EST) (envelope-from scott) Message-Id: <200203252100.g2PL0TD39756@rahl.dorm.duke.edu> Content-Type: text/plain; charset="iso-8859-1" From: Scott Sipe To: freebsd-current@freebsd.org Subject: Alpha Build Date: Mon, 25 Mar 2002 16:00:29 -0500 X-Mailer: KMail [version 1.3.2] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, I have a chance to pick up an Alpha machine which I would use for FreeBSD testing. There are 4 AlphaStation 600's from which I could pick, 2 of them have 'TGA graphics cards', 2 have "normal" graphics cards and "can run X." Seeing as right now I know next to nothing about Alpha's, would it be better to pick one or the other, or, would one or the other be better for freeBSD testing? thanks much, Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 13: 6: 5 2002 Delivered-To: freebsd-current@freebsd.org Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by hub.freebsd.org (Postfix) with ESMTP id 1992337B416; Mon, 25 Mar 2002 13:05:58 -0800 (PST) Received: from router.hackerheaven.org (ipv6.hackerheaven.org [80.126.0.97]) by smtpzilla1.xs4all.nl (8.12.0/8.12.0) with ESMTP id g2PL5tG8035651; Mon, 25 Mar 2002 22:05:56 +0100 (CET) Received: by router.hackerheaven.org (Postfix, from userid 1000) id 1742D1C27; Mon, 25 Mar 2002 22:05:12 +0100 (CET) Date: Mon, 25 Mar 2002 22:05:09 +0100 From: Emiel Kollof To: "David O'Brien" Cc: "Crist J. Clark" , nsouch@freebsd.org, current@freebsd.org Subject: Re: Broken bktr(4) module Message-ID: <20020325210509.GB13003@hackerheaven.org> References: <20020324231627.A84096@blossom.cjclark.org> <20020325111426.GB9393@hackerheaven.org> <20020325124216.A13059@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020325124216.A13059@dragon.nuxi.com> User-Agent: Mutt/1.3.28i X-Mailer: Mutt 1.3.23i (2001-10-09) X-Editor: Vim http://www.vim.org/ X-Info: http://www.hackerheaven.org/ X-Info2: http://www.cmdline.org/ X-Info3: http://www.coolvibe.org/ X-message-flag: Out of cheese error! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * David O'Brien (obrien@freebsd.org) wrote: > > Hmm, I am not alone I see here.. Already filed a PR about it. > > What was the PR number. I already fixed it. For build problem things > like this, emailing the list is better as people will see it MUCH > quicker. kern/36298, but it's already closed. Maxim was quick to spot it. Next time I'll mail the list. I'll save the PR's for the not-really-obvious things then. Actually, the PR was closed quicker than you people replying that the current@ list was quicker. How's that for efficiency? ;-) Cheers, Emiel -- Of all the animals, the boy is the most unmanageable. -- Plato To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 13:14: 2 2002 Delivered-To: freebsd-current@freebsd.org Received: from postfix2-2.free.fr (postfix2-2.free.fr [213.228.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 0792C37B400 for ; Mon, 25 Mar 2002 13:13:58 -0800 (PST) Received: from free.fr (nas-cbv-3-138-237.dial.proxad.net [62.147.138.237]) by postfix2-2.free.fr (Postfix) with ESMTP id 6E4145F774 for ; Mon, 25 Mar 2002 22:13:56 +0100 (CET) Received: (from nsouch@localhost) by free.fr (8.11.6/8.9.3) id g2PLLtE17923 for current@freebsd.org; Mon, 25 Mar 2002 22:21:55 +0100 (CET) (envelope-from nsouch) Date: Mon, 25 Mar 2002 22:21:49 +0100 From: Nicolas Souchu To: current@freebsd.org Subject: bktr breakage Message-ID: <20020325222149.A12340@armor.fastether> 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, *Sorry* for the breakage. I'm currently fixing it. smbus.h is due to the missing rule, smbus.h removed from OBJS. bktr_i2c.c is due to its automatic inclusion in kernel by conf/files: conditional compilation inserted. pcf.c breakage is due to iicbus_alloc_bus() removed, device_add_child() inserted instead. LINT ok. GENERIC is compiling... I tell you once commited. -- Nicholas Souchu - nsouch@free.fr - nsouch@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 Mar 25 13:21:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail15.speakeasy.net (mail15.speakeasy.net [216.254.0.215]) by hub.freebsd.org (Postfix) with ESMTP id D6B4E37B400 for ; Mon, 25 Mar 2002 13:21:27 -0800 (PST) Received: (qmail 10842 invoked from network); 25 Mar 2002 21:21:26 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) by mail15.speakeasy.net (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 25 Mar 2002 21:21:26 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.11.6/8.11.6) with ESMTP id g2PLM2v83666; Mon, 25 Mar 2002 16:22:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20020325215712.A257@freebie.xs4all.nl> Date: Mon, 25 Mar 2002 16:21:23 -0500 (EST) From: John Baldwin To: Wilko Bulte Subject: Re: witness panic on Alpha Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 25-Mar-2002 Wilko Bulte wrote: > On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: > > Looks like a different one: > > db> trace > siointr1() at siointr1+0x17c > siointr() at siointr+0x40 > isa_handle_fast_intr() at isa_handle_fast_intr+0x28 > alpha_dispatch_intr() at alpha_dispatch_intr+0xdc > interrupt() at interrupt+0x108 > XentInt() at XentInt+0x28 > --- interrupt (from ipl 0) --- > --- user mode --- > db> > > and > > db> show locks > exclusive (spin mutex) sio (0xfffffc0000648d20) locked @ > /usr/src/sys/dev/sio/sio.c:1634 > db> > > This is a serial console Hummm, and you got a blockable lock panic here? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "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 Mon Mar 25 13:25:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from postfix1-2.free.fr (postfix1-2.free.fr [213.228.0.130]) by hub.freebsd.org (Postfix) with ESMTP id D8CEE37B41D for ; Mon, 25 Mar 2002 13:25:00 -0800 (PST) Received: from free.fr (nas-cbv-3-138-237.dial.proxad.net [62.147.138.237]) by postfix1-2.free.fr (Postfix) with ESMTP id 66EBAAB361 for ; Mon, 25 Mar 2002 22:24:59 +0100 (CET) Received: (from nsouch@localhost) by free.fr (8.11.6/8.9.3) id g2PLWwM18016 for current@FreeBSD.ORG; Mon, 25 Mar 2002 22:32:58 +0100 (CET) (envelope-from nsouch) Date: Mon, 25 Mar 2002 22:32:58 +0100 From: Nicolas Souchu To: current@FreeBSD.ORG Subject: Re: bktr breakage Message-ID: <20020325223258.A17992@armor.fastether> References: <20020325222149.A12340@armor.fastether> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20020325222149.A12340@armor.fastether>; from nsouch@free.fr on Mon, Mar 25, 2002 at 10:21:49PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 25, 2002 at 10:21:49PM +0100, Nicolas Souchu wrote: > Hi there, > > *Sorry* for the breakage. I'm currently fixing it. > > smbus.h is due to the missing rule, smbus.h removed from OBJS. > > bktr_i2c.c is due to its automatic inclusion in kernel by conf/files: > conditional compilation inserted. > > pcf.c breakage is due to iicbus_alloc_bus() removed, device_add_child() > inserted instead. > > LINT ok. > GENERIC is compiling... > > I tell you once commited. Done. Thanks guys. Nicholas -- Nicholas Souchu - nsouch@free.fr - nsouch@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 Mar 25 13:48:40 2002 Delivered-To: freebsd-current@freebsd.org Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by hub.freebsd.org (Postfix) with ESMTP id 95B5637B405; Mon, 25 Mar 2002 13:48:34 -0800 (PST) Received: (from wkb@localhost) by freebie.xs4all.nl (8.11.6/8.11.6) id g2PLmXA00847; Mon, 25 Mar 2002 22:48:33 +0100 (CET) (envelope-from wkb) Date: Mon, 25 Mar 2002 22:48:33 +0100 From: Wilko Bulte To: John Baldwin Cc: freebsd-current@FreeBSD.org Subject: Re: witness panic on Alpha Message-ID: <20020325224833.C776@freebie.xs4all.nl> References: <20020325215712.A257@freebie.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.org on Mon, Mar 25, 2002 at 04:21:23PM -0500 X-OS: FreeBSD 4.5-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 25, 2002 at 04:21:23PM -0500, John Baldwin wrote: > On 25-Mar-2002 Wilko Bulte wrote: > > On Mon, Mar 25, 2002 at 11:40:30AM -0500, John Baldwin wrote: > > > > Looks like a different one: > > > > db> trace > > siointr1() at siointr1+0x17c > > siointr() at siointr+0x40 > > isa_handle_fast_intr() at isa_handle_fast_intr+0x28 > > alpha_dispatch_intr() at alpha_dispatch_intr+0xdc > > interrupt() at interrupt+0x108 > > XentInt() at XentInt+0x28 > > --- interrupt (from ipl 0) --- > > --- user mode --- > > db> > > > > and > > > > db> show locks > > exclusive (spin mutex) sio (0xfffffc0000648d20) locked @ > > /usr/src/sys/dev/sio/sio.c:1634 > > db> > > > > This is a serial console > > Hummm, and you got a blockable lock panic here? Well.. I lost the system for a reboot that served as the console display so I cannot tell unfortunately what the panic message said. W/ -- | / o / /_ _ wilko@FreeBSD.org |/|/ / / /( (_) Bulte Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 15:40:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 8654E37B41E; Mon, 25 Mar 2002 15:40:41 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id DFDFF319BE5; Mon, 25 Mar 2002 17:40:40 -0600 (CST) Date: Mon, 25 Mar 2002 17:40:40 -0600 From: "David W. Chapman Jr." To: Greg 'groggy' Lehey Cc: "David W. Chapman Jr." , current@freebsd.org Subject: Re: ntfs causing kernel panic Message-ID: <20020325234040.GA55777@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Greg 'groggy' Lehey , "David W. Chapman Jr." , current@freebsd.org References: <20020325154109.GA8847@leviathan.inethouston.net> <20020326100820.B68341@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020326100820.B68341@wantadilla.lemis.com> User-Agent: Mutt/1.3.28i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Mar 26, 2002 at 10:08:20AM +1030, Greg 'groggy' Lehey wrote: > On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote: > > Has anyone seen mounting an NTFS drive casing a kernel panic? I'd > > love to give the output, but I'm not sure how to redirect the output > > into a file so I can post it here. > > You need to take a dump and analyse it. There's some stuff in the > handbook about how to do it. > Unfortunately it has been fixed, but I am still planning on looking at the handbook, thanks! -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 15:41:11 2002 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 73E1D37B41B for ; Mon, 25 Mar 2002 15:38:24 -0800 (PST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id BAF727830D; Tue, 26 Mar 2002 10:08:20 +1030 (CST) Date: Tue, 26 Mar 2002 10:08:20 +1030 From: Greg 'groggy' Lehey To: "David W. Chapman Jr." Cc: current@freebsd.org Subject: Re: ntfs causing kernel panic Message-ID: <20020326100820.B68341@wantadilla.lemis.com> References: <20020325154109.GA8847@leviathan.inethouston.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020325154109.GA8847@leviathan.inethouston.net> User-Agent: Mutt/1.3.23i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.FreeBSD.org/ 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote: > Has anyone seen mounting an NTFS drive casing a kernel panic? I'd > love to give the output, but I'm not sure how to redirect the output > into a file so I can post it here. You need to take a dump and analyse it. There's some stuff in the handbook about how to do it. Greg -- 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 Mon Mar 25 16:40:59 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4585137B41C; Mon, 25 Mar 2002 16:40:54 -0800 (PST) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.11.6/8.11.6) with SMTP id g2Q0ekk01967; Mon, 25 Mar 2002 19:40:46 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Mon, 25 Mar 2002 19:40:46 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Greg 'groggy' Lehey" Cc: "David W. Chapman Jr." , current@FreeBSD.org Subject: Re: ntfs causing kernel panic In-Reply-To: <20020326100820.B68341@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 26 Mar 2002, Greg 'groggy' Lehey wrote: > On Monday, 25 March 2002 at 9:41:09 -0600, David W. Chapman Jr. wrote: > > Has anyone seen mounting an NTFS drive casing a kernel panic? I'd > > love to give the output, but I'm not sure how to redirect the output > > into a file so I can post it here. > > You need to take a dump and analyse it. There's some stuff in the > handbook about how to do it. It could be this problem is a result of the loadable VFS module bug hacked/fixed in the tree this morning. Was the NTFS driver being loaded as a module, or compiled into the kernel? If a loadable module, could you try compiling it into the kernel, or updating past the fix? If already compiled in, follow the directions grog pointed at to generate useful debugging output. Ideally, a copy of the full panic message, stack trace, and information on what kernel options you linked with so that the symbol offsets are useful. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 16:42:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from leviathan.inethouston.net (leviathan.inethouston.net [66.64.12.249]) by hub.freebsd.org (Postfix) with ESMTP id 7681537B41C; Mon, 25 Mar 2002 16:42:30 -0800 (PST) Received: by leviathan.inethouston.net (Postfix, from userid 1001) id 26E3F319AFB; Mon, 25 Mar 2002 18:42:25 -0600 (CST) Date: Mon, 25 Mar 2002 18:42:25 -0600 From: "David W. Chapman Jr." To: Robert Watson Cc: Greg 'groggy' Lehey , "David W. Chapman Jr." , current@FreeBSD.org Subject: Re: ntfs causing kernel panic Message-ID: <20020326004225.GA59056@leviathan.inethouston.net> Reply-To: "David W. Chapman Jr." Mail-Followup-To: Robert Watson , Greg 'groggy' Lehey , "David W. Chapman Jr." , current@FreeBSD.org References: <20020326100820.B68341@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i X-Operating-System: FreeBSD 4.5-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > It could be this problem is a result of the loadable VFS module bug > hacked/fixed in the tree this morning. Was the NTFS driver being loaded > as a module, or compiled into the kernel? If a loadable module, could you > try compiling it into the kernel, or updating past the fix? If already > compiled in, follow the directions grog pointed at to generate useful > debugging output. Ideally, a copy of the full panic message, stack trace, > and information on what kernel options you linked with so that the symbol > offsets are useful. > The recent vfs fix has fixed it, but thanks for the tips on what information to provide. -- David W. Chapman Jr. dwcjr@inethouston.net Raintree Network Services, Inc. dwcjr@freebsd.org FreeBSD Committer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 20:11:34 2002 Delivered-To: freebsd-current@freebsd.org Received: from w2xo.pgh.pa.us (18.gibs5.xdsl.nauticom.net [209.195.184.19]) by hub.freebsd.org (Postfix) with ESMTP id 3262937B41A for ; Mon, 25 Mar 2002 20:11:31 -0800 (PST) Received: from there (jimslaptop.int [192.168.5.14]) by w2xo.pgh.pa.us (8.11.6/8.11.3) with SMTP id g2Q4BTP11797 for ; Tue, 26 Mar 2002 04:11:30 GMT (envelope-from durham@jcdurham.com) Message-Id: <200203260411.g2Q4BTP11797@w2xo.pgh.pa.us> Content-Type: text/plain; charset="iso-8859-1" From: Jim Durham Organization: JC Durham Consulting To: freebsd-current@freebsd.org Subject: Subscribe Date: Mon, 25 Mar 2002 23:11:29 -0500 X-Mailer: KMail [version 1.3] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe freebsd-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 21:30:48 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id 9FE8137B41D; Mon, 25 Mar 2002 21:30:45 -0800 (PST) Received: from 12-234-22-238.client.attbi.com ([12.234.22.238]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020326053045.GMXN2626.rwcrmhc51.attbi.com@12-234-22-238.client.attbi.com>; Tue, 26 Mar 2002 05:30:45 +0000 Received: from master.gorean.org (master.gorean.org [10.0.0.2]) by 12-234-22-238.client.attbi.com (8.11.6/8.11.6) with ESMTP id g2Q5Ujh50320; Mon, 25 Mar 2002 21:30:45 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from master.gorean.org (localhost [127.0.0.1]) by master.gorean.org (8.12.2/8.12.2) with ESMTP id g2Q5UiLe022420; Mon, 25 Mar 2002 21:30:44 -0800 (PST) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.12.2/8.12.2/Submit) with ESMTP id g2Q5UdAb022417; Mon, 25 Mar 2002 21:30:42 -0800 (PST) X-Authentication-Warning: master.gorean.org: doug owned process doing -bs Date: Mon, 25 Mar 2002 21:30:39 -0800 (PST) From: Doug Barton X-X-Sender: doug@master.gorean.org To: Kris Kennaway Cc: "M. Warner Losh" , , Subject: Re: stdout changes break some ports In-Reply-To: <20020324175436.A75804@xor.obsecurity.org> Message-ID: <20020325212838.U22294-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sun, 24 Mar 2002, Kris Kennaway wrote: > OK. Someone needs to go and fix those 84 ports then. > > http://bento.freebsd.org/errorlogs/5-latest-4-latest.html Has anyone contacted the maintainers? I'm sure that not all of them are on this list. It may be a good way to get a slightly more knowledgeable user base exposed to -current, as well as getting the ports fixed. -- "We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory." - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 21:37: 9 2002 Delivered-To: freebsd-current@freebsd.org Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by hub.freebsd.org (Postfix) with ESMTP id 385A937B41F for ; Mon, 25 Mar 2002 21:36:51 -0800 (PST) Received: from laptop.6bone.nl (penguin.ripe.net [193.0.1.232]) by birch.ripe.net (8.11.6/8.11.6) with SMTP id g2Q5aZ800566; Tue, 26 Mar 2002 06:36:36 +0100 Received: (nullmailer pid 30995 invoked by uid 1000); Tue, 26 Mar 2002 05:36:35 -0000 Date: Tue, 26 Mar 2002 06:36:34 +0100 From: Mark Santcroos To: Garance A Drosihn Cc: current@FreeBSD.ORG Subject: Re: VMWare2 seems broken in recent -current Message-ID: <20020326063634.A23222@laptop.6bone.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from drosih@rpi.edu on Sat, Mar 23, 2002 at 07:04:02PM -0500 X-Handles: MS6-6BONE, MS18417-RIPE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Currently rebuilding with latest sources, will look into it after that. Mark On Sat, Mar 23, 2002 at 07:04:02PM -0500, Garance A Drosihn wrote: > I've just upgraded my i386-current box from about March 13 to > a snapshot from late last night. Now when I run vmware, the > vmware program dies with: > > VMware Workstation PANIC: BUG F(571):1607 bugNr=2302 > > when I try to "Power on" some virtual machine. When I got in > today, I cvsup'ed again, removed all of /usr/obj/usr/src, and > did another buildworld/installworld. I'm still getting the > same error. I also rebuilt the vmware2 port, in case it was > some includes-library change. > > Unfortunately I am in today because I have a major deadline > for something on Tuesday (something which I need vmware to > do the testing, of course...), so I do not have the time to > do some binary-search of buildworlds to figure out what > the exact culprit is. (in my case, I can just reboot into > the march-13th snapshot of the system, so this issue isn't > an immediate problem for me) > > But I thought I'd mention it in case someone else is about > to do a buildworld and would need vmware2 working after it. > > -- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Mark Santcroos RIPE Network Coordination Centre http://www.ripe.net/home/mark/ New Projects Group/TTM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 22:25:54 2002 Delivered-To: freebsd-current@freebsd.org Received: from obsecurity.dyndns.org (adsl-64-169-104-17.dsl.lsan03.pacbell.net [64.169.104.17]) by hub.freebsd.org (Postfix) with ESMTP id F383437B419; Mon, 25 Mar 2002 22:25:48 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 64BF766D19; Mon, 25 Mar 2002 22:25:48 -0800 (PST) Date: Mon, 25 Mar 2002 22:25:48 -0800 From: Kris Kennaway To: Doug Barton Cc: Kris Kennaway , "M. Warner Losh" , current@FreeBSD.org, peter@FreeBSD.org Subject: Re: stdout changes break some ports Message-ID: <20020325222548.B18406@xor.obsecurity.org> References: <20020324175436.A75804@xor.obsecurity.org> <20020325212838.U22294-100000@master.gorean.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Dxnq1zWXvFF0Q93v" Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020325212838.U22294-100000@master.gorean.org>; from DougB@FreeBSD.org on Mon, Mar 25, 2002 at 09:30:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Mar 25, 2002 at 09:30:39PM -0800, Doug Barton wrote: > On Sun, 24 Mar 2002, Kris Kennaway wrote: >=20 > > OK. Someone needs to go and fix those 84 ports then. > > > > http://bento.freebsd.org/errorlogs/5-latest-4-latest.html >=20 > Has anyone contacted the maintainers? I'm sure that not all of > them are on this list. It may be a good way to get a slightly more > knowledgeable user base exposed to -current, as well as getting the ports > fixed. Yeah, that's something I'm going to do once the current package run finishes. I've held off doing it in the recent past since there were a lot of spurious failures caused by problems with bento, but I think this run is entirely free of such problems, and it's only ports which are truly broken that are showing up. Kris --Dxnq1zWXvFF0Q93v Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8oBRrWry0BWjoQKURAkygAJkBQteG5qj6JYxi9gIYGjdBhdEk3ACg/WaC WZuOW9VjbaN3naXdBhouuvs= =jV/A -----END PGP SIGNATURE----- --Dxnq1zWXvFF0Q93v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 23:28: 6 2002 Delivered-To: freebsd-current@freebsd.org Received: from mieszko.king.tarnow.pl (mieszko.king.tarnow.pl [217.144.201.162]) by hub.freebsd.org (Postfix) with ESMTP id 8460637B41B for ; Mon, 25 Mar 2002 23:28:02 -0800 (PST) Received: from n165 (spartacus.kim.pl [213.77.26.82]) by mieszko.king.tarnow.pl (Postfix) with SMTP id 37915F85C for ; Tue, 26 Mar 2002 06:18:00 +0100 (CET) Message-ID: <002101c1d498$2225baa0$0201a8c0@king.tarnow.pl> From: "=?iso-8859-2?B?TWFjaWVqIKNhYupkvA==?=" To: Subject: D-link 660+ PCMCIA + FreeBSD4.5 Date: Tue, 26 Mar 2002 08:30:34 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_001E_01C1D4A0.7FEBCBE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_001E_01C1D4A0.7FEBCBE0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable I have problem with D-link 660+ in FreeBSD. Pccardd say that: "driver = not configured, loading driver failed" What should I do? ------=_NextPart_000_001E_01C1D4A0.7FEBCBE0 Content-Type: text/html; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable
I have problem with D-link 660+ in = FreeBSD. Pccardd=20 say that: "driver not configured, loading driver failed"
 
What should I = do?
------=_NextPart_000_001E_01C1D4A0.7FEBCBE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 23:44:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 357CF37B417; Mon, 25 Mar 2002 23:44:19 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g2Q7iJ284228; Mon, 25 Mar 2002 23:44:19 -0800 (PST) (envelope-from dillon) Date: Mon, 25 Mar 2002 23:44:19 -0800 (PST) From: Matthew Dillon Message-Id: <200203260744.g2Q7iJ284228@apollo.backplane.com> To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: can't build world on alpha References: <200203231902.g2NJ2QS71349@apollo.backplane.com> <20020324085932.D26339@dragon.nuxi.com> <200203241738.g2OHcgh76708@apollo.backplane.com> <20020324205632.A34463@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Sun, Mar 24, 2002 at 09:38:42AM -0800, Matthew Dillon wrote: :> :On Sat, Mar 23, 2002 at 11:02:26AM -0800, Matthew Dillon wrote: :> :> Anyone have any ideas? I'm trying to build the latest -current :> :> (from cvs) on an alpha running 4.3-RELEASE, using 'make buildworld'. : :I just verified one can build last night's (March 24th 3am) -CURRENT on a :Feb 10th' 4.5-STABLE box. Yah. It turned out to be an out of date /usr/share/mk. I guess make installworld doesn't update those files. I can now buildworld successfully and buildkernel doesn't give me the weird global register warning any more. Yahh. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 23:57:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id F324E37B41B; Mon, 25 Mar 2002 23:57:30 -0800 (PST) Received: from localhost (ilmar@localhost) by fledge.watson.org (8.11.6/8.11.6) with ESMTP id g2Q7vQX07593; Tue, 26 Mar 2002 02:57:26 -0500 (EST) (envelope-from ilmar@watson.org) Date: Tue, 26 Mar 2002 02:57:26 -0500 (EST) From: "Ilmar S. Habibulin" To: Michael Smith Cc: Miguel Mendez , , Subject: Re: BTX halted In-Reply-To: <200203251835.g2PIZfe00862@mass.dis.org> Message-ID: <20020326025201.Q7535-100000@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 25 Mar 2002, Michael Smith wrote: > Please don't file a PR against something like this in -current until > you've established that it's not a transient problem. > > In this case, it looks like a possibly corrupt kernel; you're dying very > early on after jumping into the kernel. Someone already pointed out, that this problem can be in corrupted kernel floppy image. I have the same problem building release of different dates. Floppies and cdrom install crashes with the same error, but if you try to boot kernel from hdd - all seems to work. I tried to find this dramatic change in release makefiles, but nothing seems to be suspicious to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Mar 25 23:58:35 2002 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id D533C37B416; Mon, 25 Mar 2002 23:58:24 -0800 (PST) Received: from horsey.gshapiro.net (gshapiro@localhost [IPv6:::1]) by horsey.gshapiro.net (8.12.3.Beta2/8.12.3.Beta2) with ESMTP id g2Q7wOGd015308 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 25 Mar 2002 23:58:24 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.12.3.Beta2/8.12.3.Beta2/Submit) id g2Q7wODq015305; Mon, 25 Mar 2002 23:58:24 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15520.10783.995435.407285@horsey.gshapiro.net> Date: Mon, 25 Mar 2002 23:58:23 -0800 From: Gregory Neil Shapiro To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: For review: Revised sendmail startup settings X-Mailer: VM 7.00 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG An issue came up on freebsd-stable today regarding the boot-time startup of sendmail for users who are using other MTAs. The end result was that users needed a way to completely prevent sendmail from trying to start at boot time. The current order of operations at boot time is: # MTA if ${sendmail_enable} == YES start sendmail with ${sendmail_flags} else if ${sendmail_outbound_enable} == YES start sendmail with ${sendmail_outbound_flags} if ${sendmail_submit_enable} == YES start sendmail with ${sendmail_submit_flags} endif # MSP Queue Runner if [ -r /etc/mail/submit.cf] && ${sendmail_msp_queue_enable} == YES start sendmail with ${sendmail_msp_queue_flags} endif A few solutions were discussed and the patch represents what I feel to be the best solution. Instead of rc.conf's sendmail_enable only accepting YES or NO, it can now also accept NONE. If set to NONE, none of the other sendmail related startup items will be done. While creating the patch, I found an extra queue running daemon might be started that wasn't necessary (it didn't hurt anything but it wasn't needed). That has been fixed in the patch as well. Therefore, the new order of operations (as shown in the rc.conf man page and src/etc/defaults/rc.conf patches) is: # MTA if ${sendmail_enable} == NONE # Do nothing else if ${sendmail_enable} == YES start sendmail with ${sendmail_flags} else if ${sendmail_submit_enable} == YES start sendmail with ${sendmail_submit_flags} else if ${sendmail_outbound_enable} == YES start sendmail with ${sendmail_outbound_flags} endif # MSP Queue Runner if ${sendmail_enable} != NONE && [ -r /etc/mail/submit.cf] && ${sendmail_msp_queue_enable} == YES start sendmail with ${sendmail_msp_queue_flags} endif This will allow users to set sendmail_enable to NONE in /etc/rc.conf and completely avoid any sendmail daemons. I've also updated the /etc/mail/Makefile "start" target code to match the new order of operations and added a new set of targets for the MSP queue runner (start-mspq, stop-mspq, and restart-mspq). Unless I hear any good arguments against this change, I'll commit it in the next day or two (and MFC it a week later). The patches for the two branches are available at: FreeBSD 4.5-STABLE: http://people.freebsd.org/~gshapiro/smstart-STABLE FreeBSD 5.0-CURRENT: http://people.freebsd.org/~gshapiro/smstart-CURRENT Thanks go to Thomas Quinot and Christopher Schulte for their contributions to the idea and Mark Santcroos for reminding me to update /etc/mail/Makefile with the new startup routines. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 26 0:17: 0 2002 Delivered-To: freebsd-current@freebsd.org Received: from relay1.macomnet.ru (relay1.macomnet.ru [195.128.64.10]) by hub.freebsd.org (Postfix) with ESMTP id 559CB37B400; Tue, 26 Mar 2002 00:16:51 -0800 (PST) Received: from news1.macomnet.ru (maxim@news1.macomnet.ru [195.128.64.14]) by relay1.macomnet.ru (8.11.6/8.11.6) with ESMTP id g2Q8GnE9202032; Tue, 26 Mar 2002 11:16:49 +0300 (MSK) Date: Tue, 26 Mar 2002 11:16:49 +0300 (MSK) From: Maxim Konovalov To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: is 'device ether' mandatory now? In-Reply-To: <20020324052056.B87371@iguana.icir.org> Message-ID: <20020326105503.H58050-100000@news1.macomnet.ru> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello Luigi, On 05:20-0800, Mar 24, 2002, Luigi Rizzo wrote: > Do you have a suggestion for an #ifdef /#endif to > remove the problem you mention ? Frankly speaking, I have no solution atm. But IMHO we should fix LINT and warn our -stable users at least. Something like that: Index: sys/i386/conf/LINT =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v retrieving revision 1.749.2.106 diff -u -r1.749.2.106 LINT --- sys/i386/conf/LINT 2002/03/11 01:23:05 1.749.2.106 +++ sys/i386/conf/LINT 2002/03/26 08:06:56 @@ -468,8 +468,8 @@ # Network interfaces: # The `loop' pseudo-device is MANDATORY when networking is enabled. # The `ether' pseudo-device provides generic code to handle -# Ethernets; it is MANDATORY when a Ethernet device driver is -# configured or token-ring is enabled. +# Ethernets; it is MANDATORY when the Internet communication +# protocols family (INET) is configured. # The 'fddi' pseudo-device provides generic code to support FDDI. # The `arcnet' pseudo-device provides generic code to support Arcnet. # The `sppp' pseudo-device serves a similar role for certain types Index: NOTES =================================================================== RCS file: /home/ncvs/src/sys/i386/conf/NOTES,v retrieving revision 1.1011 diff -u -r1.1011 NOTES --- NOTES 2002/03/23 18:39:54 1.1011 +++ NOTES 2002/03/26 08:08:48 @@ -521,8 +521,8 @@ # Network interfaces: # The `loop' device is MANDATORY when networking is enabled. # The `ether' device provides generic code to handle -# Ethernets; it is MANDATORY when a Ethernet device driver is -# configured or token-ring is enabled. +# Ethernets; it is MANDATORY when the Internet communication +# protocols family (INET) is configured. # The `fddi' device provides generic code to support FDDI. # The `arcnet' device provides generic code to support Arcnet. # The `sppp' device serves a similar role for certain types %%% I believe handbook is affected too. > cheers > luigi > > On Sat, Mar 23, 2002 at 08:50:19PM +0300, Maxim Konovalov wrote: > > > > Hello, > > > > After this commit 'device ether' is mandatory if ever there is no any > > ethernet or token-ring devices. > > > > | luigi 2002/02/18 14:50:13 PST > > | > > | Modified files: > > | sys/net if.c > > | Log: > > | When the local link address is changed, send out gratuitous ARPs > > | to notify other nodes about the address change. Otherwise, they > > | might try and keep using the old address until their arp table > > | entry times out and the address is refreshed. > > | > > | Maybe this ought to be done for INET6 addresses as well but i have > > | no idea how to do it. It should be pretty straightforward though. > > | > > | MFC-after: 10 days > > | > > | Revision Changes Path > > | 1.128 +11 -0 src/sys/net/if.c > > > > -- > > Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer > > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 26 0:25:22 2002 Delivered-To: freebsd-current@freebsd.org Received: from iguana.icir.org (iguana.icir.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id 5841C37B419 for ; Tue, 26 Mar 2002 00:25:09 -0800 (PST) Received: (from rizzo@localhost) by iguana.icir.org (8.11.6/8.11.3) id g2Q8P4H06398; Tue, 26 Mar 2002 00:25:04 -0800 (PST) (envelope-from rizzo) Date: Tue, 26 Mar 2002 00:25:04 -0800 From: Luigi Rizzo To: Maxim Konovalov Cc: current@FreeBSD.ORG Subject: Re: is 'device ether' mandatory now? Message-ID: <20020326002504.A6127@iguana.icir.org> References: <20020324052056.B87371@iguana.icir.org> <20020326105503.H58050-100000@news1.macomnet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020326105503.H58050-100000@news1.macomnet.ru> User-Agent: Mutt/1.3.23i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG i'd rather fix the change so that ether is not mandatory. Let me think/experiment a bit about it. cheers luigi On Tue, Mar 26, 2002 at 11:16:49AM +0300, Maxim Konovalov wrote: > > Hello Luigi, > > On 05:20-0800, Mar 24, 2002, Luigi Rizzo wrote: > > > Do you have a suggestion for an #ifdef /#endif to > > remove the problem you mention ? > > Frankly speaking, I have no solution atm. But IMHO we should fix LINT > and warn our -stable users at least. > > Something like that: > > Index: sys/i386/conf/LINT > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/Attic/LINT,v > retrieving revision 1.749.2.106 > diff -u -r1.749.2.106 LINT > --- sys/i386/conf/LINT 2002/03/11 01:23:05 1.749.2.106 > +++ sys/i386/conf/LINT 2002/03/26 08:06:56 > @@ -468,8 +468,8 @@ > # Network interfaces: > # The `loop' pseudo-device is MANDATORY when networking is enabled. > # The `ether' pseudo-device provides generic code to handle > -# Ethernets; it is MANDATORY when a Ethernet device driver is > -# configured or token-ring is enabled. > +# Ethernets; it is MANDATORY when the Internet communication > +# protocols family (INET) is configured. > # The 'fddi' pseudo-device provides generic code to support FDDI. > # The `arcnet' pseudo-device provides generic code to support Arcnet. > # The `sppp' pseudo-device serves a similar role for certain types > Index: NOTES > =================================================================== > RCS file: /home/ncvs/src/sys/i386/conf/NOTES,v > retrieving revision 1.1011 > diff -u -r1.1011 NOTES > --- NOTES 2002/03/23 18:39:54 1.1011 > +++ NOTES 2002/03/26 08:08:48 > @@ -521,8 +521,8 @@ > # Network interfaces: > # The `loop' device is MANDATORY when networking is enabled. > # The `ether' device provides generic code to handle > -# Ethernets; it is MANDATORY when a Ethernet device driver is > -# configured or token-ring is enabled. > +# Ethernets; it is MANDATORY when the Internet communication > +# protocols family (INET) is configured. > # The `fddi' device provides generic code to support FDDI. > # The `arcnet' device provides generic code to support Arcnet. > # The `sppp' device serves a similar role for certain types > > %%% > > I believe handbook is affected too. > > > cheers > > luigi > > > > On Sat, Mar 23, 2002 at 08:50:19PM +0300, Maxim Konovalov wrote: > > > > > > Hello, > > > > > > After this commit 'device ether' is mandatory if ever there is no any > > > ethernet or token-ring devices. > > > > > > | luigi 2002/02/18 14:50:13 PST > > > | > > > | Modified files: > > > | sys/net if.c > > > | Log: > > > | When the local link address is changed, send out gratuitous ARPs > > > | to notify other nodes about the address change. Otherwise, they > > > | might try and keep using the old address until their arp table > > > | entry times out and the address is refreshed. > > > | > > > | Maybe this ought to be done for INET6 addresses as well but i have > > > | no idea how to do it. It should be pretty straightforward though. > > > | > > > | MFC-after: 10 days > > > | > > > | Revision Changes Path > > > | 1.128 +11 -0 src/sys/net/if.c > > > > > > -- > > > Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer > > > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > -- > Maxim Konovalov, MAcomnet, Internet-Intranet Dept., system engineer > phone: +7 (095) 796-9079, mailto:maxim@macomnet.ru > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Mar 26 0:51:11 2002 Delivered-To: freebsd-current@freebsd.org Received: from kylebutt.dorms.usu.edu (kylebutt.dorms.usu.edu [129.123.231.119]) by hub.freebsd.org (Postfix) with ESMTP id 8B3DF37B419 for ; Tue, 26 Mar 2002 00:50:56 -0800 (PST) Received: from kylebutt.dorms.usu.edu (9bbdfdeeaab15b4fa78d1dfc66e17825@localhost [127.0.0.1]) by kylebutt.dorms.usu.edu (8.12.2/8.12.2) with ESMTP id g2Q8w7PN001029 for ; Tue, 26 Mar 2002 01:58:07 -0700 (MST) (envelope-from kylebutt@myrealbox.com) Date: Tue, 26 Mar 2002 01:58:07 -0700 Message-ID: <87pu1rvh7k.wl@kylebutt.dorms.usu.edu> From: Kyle Butt To: freebsd-current@freebsd.org Subject: Superfast clock on current. User-Agent: Wanderlust/2.8.1 (Something) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.1 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG My system clock is running twice as fast as it should be, but it doesn't affect timing functions. Ex: bash-2.04$ date ; sleep 5 ; date Tue Mar 26 01:48:45 MST 2002 Tue Mar 26 01:48:55 MST 2002 bash-2.04$ Has anyone else experienced this problem? I'm running X4.2.0 but not from the ports. (I upgraded and X didn't work with opieaccess, but this was before the port for 420 was moved over) It's been going on for approximately a month now. Here's my dmesg, and kernel config file, if they help. dmesg: Copyright (c) 1992-2002 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 #4: Tue Mar 26 09:03:23 MST 2002 kyle@kylebutt.dorms.usu.edu:/usr/obj/usr/src/sys/HOMEBAKED Preloaded elf kernel "/boot/kernel/kernel" at 0xc04b2000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc04b20a8. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 350796711 Hz CPU: AMD-K6(tm) 3D processor (350.80-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134201344 (131056K bytes) avail memory = 125476864 (122536K bytes) K6-family MTRR support enabled (2 registers) Using $PIR table, 5 entries at 0xc00f0b40 npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xec08-0xec0b on acpi0 acpi_cpu0: on acpi0 acpi_pcib0: port 0xcf8-0xcff on acpi0 pci0: on acpi_pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) pci0: at device 3.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 pcm0: port 0xb800-0xb83f irq 9 at device 9.0 on pci0 pci0: at device 10.0 (no driver attached) rl0: port 0xa800-0xa8ff mem 0xde000000-0xde0000ff irq 10 at device 11.0 on pci0 rl0: Realtek 8139B detected. Warning, this may be unstable in autoselect mode rl0: Ethernet address: 00:4f:4e:03:38:9c miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xa400-0xa40f irq 0 at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0 port 0x778-0x77b,0x378-0x37f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 orm0: