From owner-freebsd-current Sun Jul 25 1: 4: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 26828150A6 for ; Sun, 25 Jul 1999 01:04:00 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA11332; Sun, 25 Jul 1999 17:31:38 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA51701; Sun, 25 Jul 1999 17:31:33 +0930 (CST) Date: Sun, 25 Jul 1999 17:31:32 +0930 From: Greg Lehey To: Kevin Day Cc: kkenn@rebel.net.au, current@FreeBSD.ORG Subject: Re: Unkillable processes Message-ID: <19990725173132.E51019@freebie.lemis.com> References: <19990725154108.A51019@freebie.lemis.com> <199907250621.BAA55777@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907250621.BAA55777@celery.dragondata.com>; from Kevin Day on Sun, Jul 25, 1999 at 01:21:03AM -0500 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sunday, 25 July 1999 at 1:21:03 -0500, Kevin Day wrote: >> On Saturday, 24 July 1999 at 20:51:37 -0500, Kevin Day wrote: >>>> On Sat, 24 Jul 1999, Kevin Day wrote: >>>> >>>>> For one, do another 'ps' with the 'l' option, so you can see what it's stuck >>>>> on. >>>> >>>> UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND >>>> 1000 1103 1086 29 75 20 5740 384 - TWN ?? 0:00.00 (kvt) >>>> 1000 1109 1103 0 4 0 1504 0 ttywri IWs+ p1 0:00.00 (tcsh) >>>> >>>> 1000 92724 1086 279 105 20 5736 356 - RN ?? 139:40.13 kvt -T Termi >>>> 1000 92743 92724 2 18 0 1576 0 pause IWs p8 0:00.00 (tcsh) >>>> >>> Well, since the CPU time in the active process (92724) went up since your >>> last e-mail, and it's in the RUN state (a - in the WCHAN and a R in the >>> STAT), it looks like the process is just spinning, eating CPU. >> >> Right. >> >>> The tcsh listed below that is a zombie of the running kvt. >> >> There aren't any zombies here. >> >> It's a child of the kvt. It's not a zombie. Take a look at the STAT >> field (and ps(1)): process > > Good point, i didn't notice that, i saw the ()'s from his first message, They mean that ps can't access the command line information, for example because the process has been swapped. >> Process 92724 is runnable, nice and running (no WCHAN). I really >> don't understand why you can't stop this one. > > The only time I've seen this is when my console is getting flooded with > 'vm_fault: pager error' messages for that process. Otherwise, there's no > reason why a running process can't be killed, correct? No. You can't kill a process which is in kernel mode. If it doesn't come out, you won't be able to stop it. It seems rather unlikely that that's the case here, though. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 3:40:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7042714BFA for ; Sun, 25 Jul 1999 03:40:35 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118Lhp-000Far-00; Sun, 25 Jul 1999 12:40:33 +0200 From: Sheldon Hearn To: Nick Hibma Cc: FreeBSD current mailing list Subject: Re: PR 12634 In-reply-to: Your message of "Sat, 24 Jul 1999 18:47:37 +0200." Date: Sun, 25 Jul 1999 12:40:33 +0200 Message-ID: <59944.932899233@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999 18:47:37 +0200, Nick Hibma wrote: > PR 12634 mentions the increase of MAXSYMLINKS (src/sys/sys/param.h) to > 64. There has to be a limit. Like so many limits, it has to increase as more and more people bump up against it, provided: 1) They're not bumping up against it just because they've done something silly. 2) They've all hiked the limit in question locally and haven't observed any problems for a while. I don't think we clear either of these two with this PR. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 3:42: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 24DDE14DA0 for ; Sun, 25 Jul 1999 03:42:02 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118Lkc-000Fbe-00; Sun, 25 Jul 1999 12:43:26 +0200 From: Sheldon Hearn To: Thomas Schuerger Cc: freebsd-current@FreeBSD.ORG Subject: Re: IDE_DELAY In-reply-to: Your message of "Sat, 24 Jul 1999 20:26:56 +0200." <199907241826.UAA15612@wjpserver.cs.uni-sb.de> Date: Sun, 25 Jul 1999 12:43:26 +0200 Message-ID: <59993.932899406@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 24 Jul 1999 20:26:56 +0200, Thomas Schuerger wrote: > I've set the option > > IDE_DELAY=1500 Did you read the warning in LINT about this one? # Setting this below 10000 violate the IDE specs, but may still work for # you (it will work for most people). _May_ still work for you implies may not. What happens when you set it to 10000? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 3:46:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 632E414D32 for ; Sun, 25 Jul 1999 03:46:05 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118LpB-000FdH-00 for freebsd-current@freebsd.org; Sun, 25 Jul 1999 12:48:09 +0200 From: Sheldon Hearn To: bpechter@shell.monmouth.com Subject: Re: FreeBSD-current and Netscape Java In-reply-to: Your message of "Sat, 24 Jul 1999 19:46:52 -0400." <199907242346.TAA10489@pechter.dyndns.org> Date: Sun, 25 Jul 1999 12:47:51 +0200 Message-ID: <60079.932899671@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Hijacked from the freebsd-current mailing list] On Sat, 24 Jul 1999 19:46:52 -0400, Bill Pechter wrote: > Are there any tricks to getting Java in Netscape running with > FreeBSD --current. Just because CURRENT is the platform you use when you encounter a problem, doesn't mean that the freebsd-current mailing list is the right place to discuss it. I'd suggest the freebsd-ports, assuming good old freebsd-questions isn't good enough for you. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 4:19:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 037AF14FDC for ; Sun, 25 Jul 1999 04:18:47 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id UAA19524 for ; Sun, 25 Jul 1999 20:48:29 +0930 Received: (qmail 62974 invoked from network); 25 Jul 1999 11:17:48 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 25 Jul 1999 11:17:48 -0000 Date: Sun, 25 Jul 1999 20:47:47 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Greg Lehey Cc: Kevin Day , current@FreeBSD.ORG Subject: Re: Unkillable processes In-Reply-To: <19990725154108.A51019@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jul 1999, Greg Lehey wrote: > > The tcsh listed below that is a zombie of the running kvt. > > There aren't any zombies here. Right, they'd show up as 'Z' in the state field, I'd guess. > > This seems to be more of a kvt bug than a freebsd bug. :) > > I don't see that either. The fact that process 1103 is stopped is one > thing; is there a gdb process in sight? Nope. I did attach to it with gdb at one point to try and figure out what it was running, but because it was compiled w/o debugging symbols I didn't get anything out of a backtrace except for something similar to: #0 0x28557c28 in ?? () #1 0x804f0c7 in ?? () #2 #3 0x2851f918 in ?? () #4 0x8053038 in ?? () #5 0x8050273 in ?? () #6 0x8056369 in ?? () #7 0x28388581 in ?? () #8 0x28388369 in ?? () #9 0x2838960c in ?? () #10 0x283882f5 in ?? () #11 0x805dca2 in ?? () #12 0x804f020 in ?? () (this is from process 92724 which is still running). I might try and compile kvt with debugging support and see what it's doing; I think I can repeat the problem at will. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 4:23:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id E17C314FDC for ; Sun, 25 Jul 1999 04:23:32 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id EAA00868; Sun, 25 Jul 1999 04:21:11 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907251121.EAA00868@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kkenn@rebel.net.au Cc: Greg Lehey , Kevin Day , current@FreeBSD.ORG Subject: Re: Unkillable processes In-reply-to: Your message of "Sun, 25 Jul 1999 20:47:47 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jul 1999 04:21:11 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG while you are at it try to compile a kernel with symbols ... -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 4:47: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from rebel.net.au (rebel.rebel.net.au [203.20.69.66]) by hub.freebsd.org (Postfix) with ESMTP id 04CA51511A for ; Sun, 25 Jul 1999 04:46:35 -0700 (PDT) (envelope-from kkenn@rebel.net.au) Received: from 203.20.69.80 (dialup-10.rebel.net.au [203.20.69.80]) by rebel.net.au (8.8.5/8.8.4) with ESMTP id VAA19896 for ; Sun, 25 Jul 1999 21:13:31 +0930 Received: (qmail 65888 invoked from network); 25 Jul 1999 11:43:03 -0000 Received: from localhost (kkenn@127.0.0.1) by localhost with SMTP; 25 Jul 1999 11:43:03 -0000 Date: Sun, 25 Jul 1999 21:13:00 +0930 (CST) From: Kris Kennaway Reply-To: kkenn@rebel.net.au To: Amancio Hasty Cc: Greg Lehey , Kevin Day , current@FreeBSD.ORG Subject: Re: Unkillable processes In-Reply-To: <199907251121.EAA00868@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jul 1999, Amancio Hasty wrote: > while you are at it try to compile a kernel with symbols ... I already have (this is my standard practice). What should I do with it here? Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 4:52:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 0BFFD14F66 for ; Sun, 25 Jul 1999 04:52:50 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id EAA01042; Sun, 25 Jul 1999 04:48:06 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907251148.EAA01042@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: kkenn@rebel.net.au Cc: Greg Lehey , Kevin Day , current@FreeBSD.ORG Subject: Re: Unkillable processes In-reply-to: Your message of "Sun, 25 Jul 1999 21:13:00 +0930." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 25 Jul 1999 04:48:06 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 25 Jul 1999, Amancio Hasty wrote: > > > while you are at it try to compile a kernel with symbols ... > > I already have (this is my standard practice). What should I do with it > here? > > Kris > Well, if the process is not in a zombie state and you can't kill it . We may need to examine the process structure. Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 7:39:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 562DC14EE7 for ; Sun, 25 Jul 1999 07:39:32 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA02801; Sun, 25 Jul 1999 23:38:50 +0900 (JST) Message-ID: <379B2163.CAB603E5@newsguy.com> Date: Sun, 25 Jul 1999 23:38:27 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: kkenn@rebel.net.au Cc: current@FreeBSD.ORG Subject: Re: Unkillable processes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > Nope. I did attach to it with gdb at one point to try and figure out what > it was running, but because it was compiled w/o debugging symbols I didn't > get anything out of a backtrace except for something similar to: You *can* compile it again, just adding the -g and _without changing any other option_, and then use that new executable as source of the symbols. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 7:59: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from bingsun1.cc.binghamton.edu (bingsun1.cc.binghamton.edu [128.226.6.3]) by hub.freebsd.org (Postfix) with ESMTP id 34A5E15199 for ; Sun, 25 Jul 1999 07:58:57 -0700 (PDT) (envelope-from bf20761@binghamton.edu) Received: from localhost (bf20761@localhost) by bingsun1.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA01856; Sun, 25 Jul 1999 10:56:58 -0400 (EDT) X-Authentication-Warning: bingsun1.cc.binghamton.edu: bf20761 owned process doing -bs Date: Sun, 25 Jul 1999 10:56:58 -0400 (EDT) From: Zhihui Zhang X-Sender: bf20761@bingsun1 To: Grey Lehey Cc: current@freebsd.org Subject: Re: Unkillable processes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > No. You can't kill a process which is in kernel mode. If it doesn't > come out, you won't be able to stop it. It seems rather unlikely that > that's the case here, though. It seems to me that a process can only suicide after it detects somebody wants to kill it. Anyway, it is the process itself that calls exit(). A process must be runnable to be killed (actually suicide). Am I right? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 10:29:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id 55023151F7 for ; Sun, 25 Jul 1999 10:29:45 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id TAA23257; Sun, 25 Jul 1999 19:29:31 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id TAA04222; Sun, 25 Jul 1999 19:32:46 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990725193241.48737@breizh.teaser.fr> Date: Sun, 25 Jul 1999 19:32:41 +0200 From: Nicolas Souchu To: Bruce Evans Cc: current@FreeBSD.ORG, des@flood.ping.uio.no, obrien@NUXI.com, sobomax@altavista.net Subject: Re: PLIP is still broken :( References: <199907242335.JAA10442@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199907242335.JAA10442@godzilla.zeta.org.au>; from Bruce Evans on Sun, Jul 25, 1999 at 09:35:36AM +1000 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jul 25, 1999 at 09:35:36AM +1000, Bruce Evans wrote: > >>>Possible quick fix (hack): change all the spltty()'s in lpt.c to >>>splnet()'s. lpt isn't a tty driver; it just abuses spltty(). Abusing >>>splnet() instead should work OK for lpt and fix if_plip. >> >>This seems good until the intr stuff handle dynamic update of a interrupt spl. >>Is there some work in progress on that? > >Not much. ppc needs to do most of the work by registering its interrupt >with the correct interrupt maskptr for the currently attached device. >This may involve unregistering the interrupt when the device changes. >The generic code could help here by supporting atomic changing of >interrupt maskptrs without unregistering the interrupt. Otherwise, >the generic code is missing mainly update of the interrupt masks when >an interrupt is unregistered. For the low level side, we could consider something like the following code. But this shall be called by the nexus layer and then needs generic newbus support (as you said above, didn't you?). /* * Switch an irq from a maskptr to another without unregistering the irq * handler. * This function is supposed to work with only one handler per irq. */ void switch_masks(intrmask_t *oldmaskptr, intrmask_t *newmaskptr, int irq) { int s; intrec *idesc; intrmask_t mask = 1 << irq; if ((oldmaskptr == NULL) || (newmaskptr == NULL)) return; if (((idesc = find_idesc(oldmaskptr, irq)) == NULL) || (find_idesc(newmaskptr, irq) != NULL)) return; /* block all interrupts */ s = splhigh(); /* update the irq mask ptr */ idesc->maskptr = newmaskptr; /* remove the irq from the old mask and add it to the new one */ INTRUNMASK(*oldmaskptr, mask); INTRMASK(*newmaskptr, mask); /* we need to update all values in the intr_mask[irq] array */ update_intr_masks(); /* update mask in chains of the interrupt multiplex handler as well */ update_mux_masks(); /* restore interrupts */ splx(s); return; } Your opinion? Nicholas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sun Jul 25 11: 0: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from november.jaded.net (november.jaded.net [216.94.113.4]) by hub.freebsd.org (Postfix) with ESMTP id B8CA81520D for ; Sun, 25 Jul 1999 11:00:03 -0700 (PDT) (envelope-from dan@november.jaded.net) Received: (from dan@localhost) by november.jaded.net (8.9.3/8.9.3+trinsec_nospam) id OAA43643 for current@freebsd.org; Sun, 25 Jul 1999 14:12:53 -0400 (EDT) Date: Sun, 25 Jul 1999 14:12:53 -0400 From: Dan Moschuk To: current@freebsd.org Subject: whereis broken? Message-ID: <19990725141253.A43496@trinsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG whereis anything yields.. Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! ad infinity. Cheers, Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 11:13: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 9D3E714CD4 for ; Sun, 25 Jul 1999 11:12:55 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118SlS-000GEN-00; Sun, 25 Jul 1999 20:12:46 +0200 From: Sheldon Hearn To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: whereis broken? In-reply-to: Your message of "Sun, 25 Jul 1999 14:12:53 -0400." <19990725141253.A43496@trinsec.com> Date: Sun, 25 Jul 1999 20:12:46 +0200 Message-ID: <62394.932926366@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jul 1999 14:12:53 -0400, Dan Moschuk wrote: > whereis anything yields.. > > Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! Staleness. Unfortunately, the whereis(1) manpage doesn't tell you to look at the manpath(1) manpage. Do so now and you'll see that you should check your /etc/manpath.config and your $MANPATH environment variable. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 12: 4:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 6062B1522F for ; Sun, 25 Jul 1999 12:04:48 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id FAA12887; Mon, 26 Jul 1999 05:04:42 +1000 Date: Mon, 26 Jul 1999 05:04:42 +1000 From: Bruce Evans Message-Id: <199907251904.FAA12887@godzilla.zeta.org.au> To: bde@zeta.org.au, nsouch@teaser.fr Subject: Re: PLIP is still broken :( Cc: current@FreeBSD.ORG, des@flood.ping.uio.no, obrien@NUXI.com, sobomax@altavista.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Otherwise, >>the generic code is missing mainly update of the interrupt masks when >>an interrupt is unregistered. > >For the low level side, we could consider something like the following code. >But this shall be called by the nexus layer and then needs generic newbus >support (as you said above, didn't you?). >/* > * Switch an irq from a maskptr to another without unregistering the irq > * handler. > * This function is supposed to work with only one handler per irq. > */ >void >switch_masks(intrmask_t *oldmaskptr, intrmask_t *newmaskptr, int irq) ... I don't like most of this. Driver level code won't even know the correct maskptrs. (irq, maskptr) pairs depend on i386 implementation details for uniqueness. Use { s = splhigh(); BUS_TEARDOWN_INTR(...); BUS_SETUP_INTR(...); splx(s); } until/unless the newbus level provides a better interface. The problem with the masks not being updated when interrupts are unregistered should be fixed in update*_masks(). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 12:24:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 54C9D14CB1 for ; Sun, 25 Jul 1999 12:24:42 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118TsQ-000GM5-00; Sun, 25 Jul 1999 21:24:02 +0200 From: Sheldon Hearn To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: whereis broken? In-reply-to: Your message of "Sun, 25 Jul 1999 20:12:46 +0200." <62394.932926366@axl.noc.iafrica.com> Date: Sun, 25 Jul 1999 21:24:02 +0200 Message-ID: <62872.932930642@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jul 1999 20:12:46 +0200, Sheldon Hearn wrote: > > Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! > > Staleness. It's been pointed out to me in private mail that current's manpath.config is broken. If nobody's looked at it by tomorrow, I'll do so then. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 12:28: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 74CB91522F for ; Sun, 25 Jul 1999 12:28:05 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.3]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB5005; Sun, 25 Jul 1999 21:25:29 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id VAA15447; Sun, 25 Jul 1999 21:16:59 +0200 (CEST) (envelope-from asmodai) Date: Sun, 25 Jul 1999 21:16:58 +0200 From: Jeroen Ruigrok/Asmodai To: Sheldon Hearn Cc: Dan Moschuk , current@FreeBSD.ORG Subject: Re: whereis broken? Message-ID: <19990725211658.D14954@daemon.ninth-circle.org> References: <19990725141253.A43496@trinsec.com> <62394.932926366@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <62394.932926366@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Jul 25, 1999 at 08:12:46PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sheldon Hearn (sheldonh@uunet.co.za) [990725 20:29]: > > > On Sun, 25 Jul 1999 14:12:53 -0400, Dan Moschuk wrote: > > > whereis anything yields.. > > > > Warning: couldn't stat file /usr/local/lib/perl5/5.00502/man! > > Staleness. Unfortunately, the whereis(1) manpage doesn't tell you to > look at the manpath(1) manpage. Do so now and you'll see that you should > check your /etc/manpath.config and your $MANPATH environment variable. Prolly didn't use mergemaster after making world eh Dan? ;) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 12:34:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id BCB96152ED for ; Sun, 25 Jul 1999 12:34:46 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA64080; Sun, 25 Jul 1999 21:33:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199907251933.VAA64080@gratis.grondar.za> To: Sheldon Hearn Cc: Dan Moschuk , current@FreeBSD.ORG Subject: Re: whereis broken? Date: Sun, 25 Jul 1999 21:33:55 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It's been pointed out to me in private mail that current's > manpath.config is broken. If nobody's looked at it by tomorrow, I'll do > so then. Fixed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 12:45:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 17BD014C15 for ; Sun, 25 Jul 1999 12:45:10 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118UAe-000GPP-00; Sun, 25 Jul 1999 21:42:52 +0200 From: Sheldon Hearn To: Dan Moschuk Cc: current@FreeBSD.ORG Subject: Re: whereis broken? In-reply-to: Your message of "Sun, 25 Jul 1999 21:33:55 +0200." <199907251933.VAA64080@gratis.grondar.za> Date: Sun, 25 Jul 1999 21:42:52 +0200 Message-ID: <63078.932931772@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 25 Jul 1999 21:33:55 +0200, Mark Murray wrote: > > It's been pointed out to me in private mail that current's > > manpath.config is broken. > > Fixed. Hi Dan, You'll need rev 1.11 of src/gnu/usr.bin/man/manpath/manpath.config, but you should be able to get away with commenting out those MANDATORY_MANPATH lines that reference /usr/local . Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 15: 0:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [194.242.128.25]) by hub.freebsd.org (Postfix) with ESMTP id 7FAED15010 for ; Sun, 25 Jul 1999 15:00:22 -0700 (PDT) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id WAA79589; Sun, 25 Jul 1999 22:59:41 +0100 (BST) (envelope-from joe) Date: Sun, 25 Jul 1999 22:59:41 +0100 From: Josef Karthauser To: Brian Somers Cc: Mark Thomas , freebsd-current@FreeBSD.org, Wayne Self Subject: Re: userland ppp - startup Message-ID: <19990725225941.B74812@pavilion.net> References: <19990707103746.A30024@pavilion.net> <199907072102.WAA19958@dev.lan.awfulhak.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=VbJkn9YxBvnuCH5J X-Mailer: Mutt 0.95.4i In-Reply-To: <199907072102.WAA19958@dev.lan.awfulhak.org>; from Brian Somers on Wed, Jul 07, 1999 at 10:02:44PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, 24 The Old Steine, Brighton, BN1 1EL, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii On Wed, Jul 07, 1999 at 10:02:44PM +0100, Brian Somers wrote: > > This aside, I think there are more bits required for the patches :*1 > > rc.conf.5 needs to be updated - that's the easy bit. Done - see attached. > I think we also need a src/etc/ppp/ppp.conf that installs with 0600 > permissions at installation time. This file would have a default > and a papchap entry in it - that's where the url for Waynes ppp.conf > comes in - its contents are probably what we're after. Older versions > of src/etc/Makefile installed ppp.conf, so it should be easy to do that > side of things. Done - attached is Waynes ppp.conf and a patch for /usr/src/etc/Makefile. > Sysinstall however is also capable of writing ppp.conf. It would > need to be smart enough to update the default one with the lines that > it wants to use (just appending an ``install'' label with the > necessary bits is probably the best thing to do). This answers your > other question..... src/release/sysinstall/network.c - search for > ppp.conf. That's how sysinstall does it :-) Attached is network.c.patch, which should do the right thing. It simply appends to /etc/ppp/ppp.conf with an 'install' profile, and also sets the relevent rc.conf variables so that the configuration survives across reboots. (This should probably be a little more intelligent, but lets get the functionality in first and "better" it up later.) > Ha, and you thought it'd be straight forward ;^P Of course not ;). Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="usr_src_etc_ppp_ppp.conf" ################################################################# # PPP Sample Configuration File # Originally written by Toshiharu OHNO # Simplified 5/14/1999 by wself@cdrom.com # # $Id$ ################################################################# default: # # Instructions: # # edit the next three lines and replace the items in caps with # the values which have been assigned by your ISP. # set phone PHONE_NUM set authname USERNAME set authkey PASSWORD # # Make sure that "device" references the correct serial port # for your modem. (cuaa0 = COM1, cuaa1 = COM2) # set device /dev/cuaa1 set log Phase Chat LCP IPCP CCP tun command set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 120 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="usr_src_etc_Makefile.patch" Index: etc/Makefile =================================================================== RCS file: /home/ncvs/src/etc/Makefile,v retrieving revision 1.201 diff -u -r1.201 Makefile --- Makefile 1999/07/10 18:02:12 1.201 +++ Makefile 1999/07/25 17:46:57 @@ -24,6 +24,7 @@ BSD.var.dist BSD.x11.dist NAMEDB= PROTO.localhost.rev named.conf named.root make-localhost PPPCNF= ppp.deny ppp.shells.sample +PPPCF2= ppp.conf NOSPAM= Makefile README @@ -79,6 +80,8 @@ ${NAMEDB} ${DESTDIR}/etc/namedb cd ${.CURDIR}/ppp; ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 644 \ ${PPPCNF} ${DESTDIR}/etc/ppp + cd ${.CURDIR}/ppp; ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 600 \ + ${PPPCF2} ${DESTDIR}/etc/ppp cd ${.CURDIR}/mail; ${INSTALL} -c -o ${BINOWN} -g ${BINGRP} -m 644 \ ${NOSPAM} ${DESTDIR}/etc/mail ${INSTALL} -c -o ${BINOWN} -g operator -m 664 /dev/null \ --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="usr_src_share_man_man5_rc.conf.5.patch" Index: rc.conf.5 =================================================================== RCS file: /home/ncvs/src/share/man/man5/rc.conf.5,v retrieving revision 1.36 diff -u -r1.36 rc.conf.5 --- rc.conf.5 1999/07/16 09:22:01 1.36 +++ rc.conf.5 1999/07/25 17:19:02 @@ -218,6 +218,30 @@ .Ed Then note that alias4 would \fBnot\fR be added since the search would stop with the missing alias3 entry. +.It Ar ppp_enable +(bool) If set to +.Ar YES , +run the +.Xr ppp 8 +daemon. +.It Ar ppp_mode +(str) Mode in which to run the +.Xr ppp 8 +daemon. Accepted modes are +.Ar auto , ddial , direct +and +.Ar dedicated . +See the manual for a full description. +.It Ar ppp_alias +(bool) If set to +.Ar YES , +enables packet aliasing. Used in conjunction with +.Ar gateway_enable +allows hosts on private network addresses access the Internet using +this host as a network address translating router. +.It Ar ppp_profile +(str) The name of the profile to use from +.Ar /etc/ppp/ppp.conf . .It Ar rc_conf_files (str) This option is used to specify a list of files that will override the settings in --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="usr_src_release_sysinstall_sysinstall.h" Index: sysinstall.h =================================================================== RCS file: /home/ncvs/src/release/sysinstall/sysinstall.h,v retrieving revision 1.171 diff -u -r1.171 sysinstall.h --- sysinstall.h 1999/07/19 10:06:17 1.171 +++ sysinstall.h 1999/07/25 21:24:15 @@ -148,6 +148,8 @@ #define VAR_PCNFSD "pcnfsd" #define VAR_PKG_TMPDIR "PKG_TMPDIR" #define VAR_PORTS_PATH "ports" +#define VAR_PPP_ENABLE "ppp_enable" +#define VAR_PPP_PROFILE "ppp_profile" #define VAR_RELNAME "releaseName" #define VAR_ROOT_SIZE "rootSize" #define VAR_ROUTER "router" --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="usr_src_release_sysinstall_network.c" Index: network.c =================================================================== RCS file: /home/ncvs/src/release/sysinstall/network.c,v retrieving revision 1.37 diff -u -r1.37 network.c --- network.c 1999/07/18 10:18:05 1.37 +++ network.c 1999/07/25 21:56:15 @@ -246,7 +246,7 @@ close(fd2); } if (!Fake) - fp = fopen("/etc/ppp/ppp.conf", "w"); + fp = fopen("/etc/ppp/ppp.conf", "a"); else fp = fopen("/dev/stderr", "w"); if (!fp) { @@ -268,7 +268,7 @@ dialog_clear_norefresh(); pulse = dialog_yesno("", "Does your telephone line support tone dialing?", -1, -1); } - fprintf(fp, "default:\n"); + fprintf(fp, "\ninstall:\n"); fprintf(fp, " set speed %s\n", speed); fprintf(fp, " set device %s\n", devp->devname); fprintf(fp, " set ifaddr %s %s\n", myaddr, provider); @@ -282,10 +282,14 @@ fprintf(fp, " set authkey %s\n", authkey); fprintf(fp, " set phone %s\n", phone); } - if (fchmod(fileno(fp), 0640) != 0) + if (fchmod(fileno(fp), 0600) != 0) msgConfirm("Warning: Failed to fix permissions on /etc/ppp/ppp.conf !"); fclose(fp); + /* Make the ppp config persistant */ + variable_set2(VAR_PPP_ENABLE, "YES", 0); + variable_set2(VAR_PPP_PROFILE, "install", 0); + if (!Fake && !file_readable("/dev/tun0") && mknod("/dev/tun0", 0600 | S_IFCHR, makedev(52, 0))) { msgConfirm("Warning: No /dev/tun0 device. PPP will not work!"); return 0; @@ -318,7 +322,7 @@ } else msgDebug("ppp: Unable to get the terminal attributes!\n"); - execlp("ppp", "ppp", (char *)NULL); + execlp("ppp", "ppp install", (char *)NULL); msgDebug("PPP process failed to exec!\n"); exit(1); } --VbJkn9YxBvnuCH5J-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jul 25 16:23:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id F0348152E0 for ; Sun, 25 Jul 1999 16:22:59 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA15571 for ; Sun, 25 Jul 1999 19:22:57 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA06412 for ; Sun, 25 Jul 1999 19:22:56 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA06408 for ; Sun, 25 Jul 1999 19:22:56 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Sun, 25 Jul 1999 19:22:56 -0400 (EDT) From: Kenneth Wayne Culver To: current@freebsd.org Subject: Aureal Vortex soundcard drivers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just wondering how the drivers on the aureal vortex are coming along... I know that Cameron Grant was working on them, but I have not heard anything on that subject fora while, so I was kinda hoping to hear about it soon. Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 26 1:11:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (Postfix) with ESMTP id D9B8614FED for ; Mon, 26 Jul 1999 01:11:39 -0700 (PDT) (envelope-from vallo@matti.ee) Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by solaris.matti.ee (8.9.3/8.9.3) with ESMTP id LAA20001; Mon, 26 Jul 1999 11:08:44 +0300 (EET DST) Received: by myhakas.matti.ee (Postfix, from userid 1000) id 8109E1FBF; Mon, 26 Jul 1999 11:09:04 +0300 (EEST) Date: Mon, 26 Jul 1999 11:09:04 +0300 From: Vallo Kallaste To: Greg Lehey Cc: Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: world builds but doesn't install Message-ID: <19990726110904.A38516@myhakas.matti.ee> Reply-To: vallo@matti.ee References: <19990723220508.A83138@myhakas.matti.ee> <19990724111151.L84734@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990724111151.L84734@freebie.lemis.com>; from Greg Lehey on Sat, Jul 24, 1999 at 11:11:51AM +0930 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jul 24, 1999 at 11:11:51AM +0930, Greg Lehey wrote: > > Whats more interesting, the July 19 sources which built and > > installed fine before now doesn't install anymore. Exactly same > > message. I've downloaded the fresh sources just to be sure I > > haven't screwed something. No difference. I don't understand > > for what the .ph suffix stands for and what the install > > procedure does in this phase, it seems doing some perl stuff. > > What's happening? > > Good question. I just did a make world, and it went fine. And the > UDMA brokenness is gone again. Oh well, I screwed up my system so badly finally, swapper dumped core and I got crashes everytime the fsck hope to fix my filesystems, seems that I mixed different versions of binaries and kernel. I went with binary upgrade route and so far all works again, thought I haven't tried to do make world yet. Thanks for your reply, it's really my system which is screwed up. -- Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 26 9:49:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 052C014C90 for ; Mon, 26 Jul 1999 09:49:53 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.155]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA226C; Mon, 26 Jul 1999 18:49:44 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id SAA04153; Mon, 26 Jul 1999 18:48:15 +0200 (CEST) (envelope-from asmodai) Date: Mon, 26 Jul 1999 18:48:15 +0200 From: Jeroen Ruigrok/Asmodai To: Sheldon Hearn Cc: Dan Moschuk , current@FreeBSD.ORG Subject: Re: whereis broken? Message-ID: <19990726184815.I1384@daemon.ninth-circle.org> References: <199907251933.VAA64080@gratis.grondar.za> <63078.932931772@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <63078.932931772@axl.noc.iafrica.com>; from Sheldon Hearn on Sun, Jul 25, 1999 at 09:42:52PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Sheldon Hearn (sheldonh@uunet.co.za) [990726 02:00]: > > > On Sun, 25 Jul 1999 21:33:55 +0200, Mark Murray wrote: > > > > It's been pointed out to me in private mail that current's > > > manpath.config is broken. > > > > Fixed. > > You'll need rev 1.11 of src/gnu/usr.bin/man/manpath/manpath.config, but > you should be able to get away with commenting out those > MANDATORY_MANPATH lines that reference /usr/local . Sheldon, I got /usr/local ref's in my /etc/manpath.config, the MANDATORY_MANPATHs, using man, whatis, whereis or other utilities that reference manpath.config I got no problem whatsoever. This is -CURRENT from last night. What was/is the presumed problem with manpath.config then? Mayhaps I misunderstood the whole thing. Gracias, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 26 9:55: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 639F5154A6 for ; Mon, 26 Jul 1999 09:54:54 -0700 (PDT) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.02 #1) id 118o1E-0000SS-00; Mon, 26 Jul 1999 18:54:28 +0200 From: Sheldon Hearn To: Jeroen Ruigrok/Asmodai Cc: Dan Moschuk , current@FreeBSD.ORG Subject: Re: whereis broken? In-reply-to: Your message of "Mon, 26 Jul 1999 18:48:15 +0200." <19990726184815.I1384@daemon.ninth-circle.org> Date: Mon, 26 Jul 1999 18:54:28 +0200 Message-ID: <1763.933008068@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 26 Jul 1999 18:48:15 +0200, Jeroen Ruigrok/Asmodai wrote: > I got /usr/local ref's in my /etc/manpath.config, the MANDATORY_MANPATHs, > using man, whatis, whereis or other utilities that reference manpath.config > I got no problem whatsoever. This is -CURRENT from last night. You have perl5 packages or ports installed into /usr/local . :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jul 26 11:21:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id C7DA114F89 for ; Mon, 26 Jul 1999 11:21:50 -0700 (PDT) (envelope-from nsouch@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id UAA05626; Mon, 26 Jul 1999 20:21:21 +0200 (MET DST) Received: (from nsouch@localhost) by teaser.fr (8.9.3/8.9.1) id UAA00685; Mon, 26 Jul 1999 20:24:42 +0200 (CEST) (envelope-from nsouch) Message-ID: <19990726202441.57962@breizh.teaser.fr> Date: Mon, 26 Jul 1999 20:24:41 +0200 From: Nicolas Souchu To: Bruce Evans Cc: current@FreeBSD.ORG, des@flood.ping.uio.no, obrien@NUXI.com, sobomax@altavista.net Subject: Re: PLIP is still broken :( References: <199907251904.FAA12887@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199907251904.FAA12887@godzilla.zeta.org.au>; from Bruce Evans on Mon, Jul 26, 1999 at 05:04:42AM +1000 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jul 26, 1999 at 05:04:42AM +1000, Bruce Evans wrote: > >>>Otherwise, >>>the generic code is missing mainly update of the interrupt masks when >>>an interrupt is unregistered. >> >>For the low level side, we could consider something like the following code. >>But this shall be called by the nexus layer and then needs generic newbus >>support (as you said above, didn't you?). > >>/* >> * Switch an irq from a maskptr to another without unregistering the irq >> * handler. >> * This function is supposed to work with only one handler per irq. >> */ >>void >>switch_masks(intrmask_t *oldmaskptr, intrmask_t *newmaskptr, int irq) >.... > >I don't like most of this. Driver level code won't even know the >correct maskptrs. (irq, maskptr) pairs depend on i386 implementation >details for uniqueness. Use { s = splhigh(); BUS_TEARDOWN_INTR(...); >BUS_SETUP_INTR(...); splx(s); } until/unless the newbus level provides This is what I meant when I said the nexus layer shall do the switch_masks() call. The current implementation of SETUP_INTR/TEARDOWN involves the overhead of unregistering and registering the interrupt. This is why I propose switch_masks() which doesn't. Moreover, in the ppbus model, the ppc_intr() function is _always_ the registered interrupt handler and it dispatches the interrupt depending on the device driver which currently owns the bus when the interrupt occurs. >a better interface. The problem with the masks not being updated when >interrupts are unregistered should be fixed in update*_masks(). I agree if unregistering/registering is declared better than switching masks for the current registered handler. > >Bruce > -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Jul 26 11:32:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id E78931508A for ; Mon, 26 Jul 1999 11:32:12 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA55353; Mon, 26 Jul 1999 20:30:39 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nicolas Souchu Cc: Bruce Evans , current@FreeBSD.ORG, des@flood.ping.uio.no, obrien@NUXI.com, sobomax@altavista.net Subject: Re: PLIP is still broken :( In-reply-to: Your message of "Mon, 26 Jul 1999 20:24:41 +0200." <19990726202441.57962@breizh.teaser.fr> Date: Mon, 26 Jul 1999 20:30:38 +0200 Message-ID: <55351.933013838@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990726202441.57962@breizh.teaser.fr>, Nicolas Souchu writes: >Moreover, in the ppbus model, the ppc_intr() function is _always_ >the registered interrupt handler and it dispatches the interrupt >depending on the device driver which currently owns the bus when >the interrupt occurs. This is also something that should be changed since we are to modify things anyway, it introduces un-needed delays (and jitter) in the interrupt delivery. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 1:45: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles554.castles.com [208.214.165.118]) by hub.freebsd.org (Postfix) with ESMTP id 6F1681538A for ; Tue, 27 Jul 1999 01:45:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id BAA01530; Tue, 27 Jul 1999 01:40:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907270840.BAA01530@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Sedore Cc: freebsd-current@freebsd.org Subject: Re: aio and fd patches In-reply-to: Your message of "Thu, 15 Jul 1999 14:27:31 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 27 Jul 1999 01:40:08 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm interested in finding someone to help me get the aio patches I've > written committed into -current. These fixes make the aio routines much > more useful for io on sockets than they are now (each io op on a socket > blocks an aiod). This is a bit of a work in progress, but I've been > running these patches here for over a month with good performance and > no new detriment to stability. There should be no stability impact on > code which doesn't utilize aio routines. > > I'm also interested in whether anyone is working to get the patches from > Ville-Pertti Keinonen for file descriptor referencing committed. These > are important for aio and other more critical subsystems. > > You can see my report of issues in kern/12053. I somehow managed to > include a mangled and outdated version of the patch with that report, so > that patch shouldn't be integrated. An updated patch is available at > http://tfeed.maxwell.syr.edu/aio-diff If someone else running each of these patch sets is willing to vouch for their direct applyability to -current and their ongoing functionality, I'll commit them immediately. Sorry that your work has been basically ignored; it looks like there are no committers actively working on this right now. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 3:49:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-2.uoregon.edu (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id 4BAEF14D77 for ; Tue, 27 Jul 1999 03:49:51 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-2.uoregon.edu (8.9.1/8.8.7) id DAA00497; Tue, 27 Jul 1999 03:49:38 -0700 (PDT) Message-ID: <19990727034937.10144@hydrogen.fircrest.net> Date: Tue, 27 Jul 1999 03:49:37 -0700 From: John-Mark Gurney To: Mike Smith Cc: Christopher Sedore , freebsd-current@FreeBSD.ORG Subject: Re: aio and fd patches References: <199907270840.BAA01530@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199907270840.BAA01530@dingo.cdrom.com>; from Mike Smith on Tue, Jul 27, 1999 at 01:40:08AM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith scribbled this message on Jul 27: > > > > I'm interested in finding someone to help me get the aio patches I've > > written committed into -current. These fixes make the aio routines much > > more useful for io on sockets than they are now (each io op on a socket > > blocks an aiod). This is a bit of a work in progress, but I've been > > running these patches here for over a month with good performance and > > no new detriment to stability. There should be no stability impact on > > code which doesn't utilize aio routines. > > > > I'm also interested in whether anyone is working to get the patches from > > Ville-Pertti Keinonen for file descriptor referencing committed. These > > are important for aio and other more critical subsystems. > > > > You can see my report of issues in kern/12053. I somehow managed to > > include a mangled and outdated version of the patch with that report, so > > that patch shouldn't be integrated. An updated patch is available at > > http://tfeed.maxwell.syr.edu/aio-diff > > If someone else running each of these patch sets is willing to vouch > for their direct applyability to -current and their ongoing > functionality, I'll commit them immediately. > > Sorry that your work has been basically ignored; it looks like there > are no committers actively working on this right now. I have been meaning to look at these patches, it's just that I haven't had a -current box to do testing on, but soon (like the end of the week), I should have a box that I can do testing, and if so, I'll make sure that these function, and if so, commit them... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 3:59: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 03A6B14BD4 for ; Tue, 27 Jul 1999 03:58:55 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-33.iptelecom.net.ua [212.42.69.224]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA17538 for ; Tue, 27 Jul 1999 13:28:18 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id NAA10728 for ; Tue, 27 Jul 1999 13:20:56 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379D8807.B9DE0277@altavista.net> Date: Tue, 27 Jul 1999 13:20:55 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: current@freebsd.org Subject: MAKEDEV (or sh?) broken Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my CURRENT system cvsup'ed and builded yesterday when I'm trying to do "cd /dev; sh MAKEDEV all" I see following errors: Script started on Tue Jul 27 13:14:47 1999 sh-2.03# cd /dev ; sh MAKEDEV all MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da0b MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da1b MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da2b MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da3b MAKEDEV: arith: syntax error: "¶† " usage: mknod name [b | c] major minor /sbin/mknod wd0b MAKEDEV: arith: syntax error: "¶† " usage: mknod name [b | c] major minor /sbin/mknod wd1b MAKEDEV: arith: syntax error: "?† ¶† " usage: mknod name [b | c] major minor /sbin/mknod wd2b MAKEDEV: arith: syntax error: "?† ¶† " usage: mknod name [b | c] major minor /sbin/mknod wd3b MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod od0b MAKEDEV: arith: syntax error: "µ† ?† " usage: mknod name [b | c] major minor /sbin/mknod wfd0b MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod vn0b sh-2.03# exit Script done on Tue Jul 27 13:16:57 1999 -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 4: 8:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 6510314BE9 for ; Tue, 27 Jul 1999 04:08:35 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id HAA45240; Tue, 27 Jul 1999 07:06:38 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 27 Jul 1999 07:06:38 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: MAKEDEV (or sh?) broken In-Reply-To: <379D8807.B9DE0277@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 27 Jul 1999, Maxim Sobolev wrote: > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > do "cd /dev; sh MAKEDEV all" I see following errors: Did you somehow replace Bourne with BASH? Check. > > Script started on Tue Jul 27 13:14:47 1999 > sh-2.03# cd /dev ; sh MAKEDEV all > ... > Script done on Tue Jul 27 13:16:57 1999 > > -Maxim > -- > "We believe in the Power and the Might!" > (Manowar, 1996) > ---------------------------------------- > Maxim V. Sobolev, Financial Analyst, > Vega International Capital > Phone: +380-(44)-246-6396 > Fax: +380-(44)-220-8715 > E-mail: sobomax@altavista.net > ICQ: #42290709 > ---------------------------------------- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 4:42:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id CE5AE14D71; Tue, 27 Jul 1999 04:42:42 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup1-54.iptelecom.net.ua [212.42.68.181]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id OAA24093; Tue, 27 Jul 1999 14:46:59 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id OAA11042; Tue, 27 Jul 1999 14:35:58 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379D999D.4A3C5452@altavista.net> Date: Tue, 27 Jul 1999 14:35:58 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: "Brian F. Feldman" Cc: current@FreeBSD.org Subject: Re: MAKEDEV (or sh?) broken References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > On Tue, 27 Jul 1999, Maxim Sobolev wrote: > > > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > > do "cd /dev; sh MAKEDEV all" I see following errors: > > Did you somehow replace Bourne with BASH? Check. No, in any way I didn't replaced it (yesterday I installed fresh word and since that I'm not undertake any activity which might replace /bin/sh): Script started on Tue Jul 27 14:26:45 1999 sh-2.03# which sh /bin/sh sh-2.03# ls -l /bin/sh -r-xr-xr-x 1 root wheel 349808 Jul 26 19:05 /bin/sh sh-2.03# exit As you can see paths is right and /bin/sh is not a symlink. Mergemaster yields similar results, so it can't be my local MAKEDEV fault. -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 5:21:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id AB39A153DA for ; Tue, 27 Jul 1999 05:21:35 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id IAA46556; Tue, 27 Jul 1999 08:21:28 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 27 Jul 1999 08:21:28 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: MAKEDEV (or sh?) broken In-Reply-To: <379D999D.4A3C5452@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Isolate a specific case of MAKEDEV (not just all) that will demonstrate this, sh -x it, and send it to me. Failing that, set -x and do ./MAKEDEV all, and send me this output. That's where we need to go next to try to find out what is wrong. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 6:34:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id D8C0D1540C; Tue, 27 Jul 1999 06:34:06 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-47.iptelecom.net.ua [212.42.69.238]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA04510; Tue, 27 Jul 1999 16:38:55 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id PAA11309; Tue, 27 Jul 1999 15:38:52 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379DA85B.DA4E80AC@altavista.net> Date: Tue, 27 Jul 1999 15:38:51 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: "Brian F. Feldman" Cc: current@FreeBSD.org Subject: Re: MAKEDEV (or sh?) broken References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here it is. -Maxim Script started on Tue Jul 27 15:34:02 1999 sh-2.03# sh -x MAKEDEV da0 + PATH=/sbin:/bin/:/usr/bin:/usr/sbin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/X11R6/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + name=da + blk=4 + chr=13 + expr da0 : ..\(.*\) + unit=0 + sh MAKEDEV da0s0h MAKEDEV: arith: syntax error: "?† ž† " usage: mknod name [b | c] major minor /sbin/mknod da0b + sh MAKEDEV da0s1 + sh MAKEDEV da0s2 + sh MAKEDEV da0s3 + sh MAKEDEV da0s4 + umask 77 sh-2.03# sh -x MAKEDEV da0s0h + PATH=/sbin:/bin/:/usr/bin:/usr/sbin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/X11R6/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + name=da + blk=4 + chr=13 + expr da0s0h : ..\([0-9]*\)s + unit=0 + expr da0s0h : ..[0-9]*s\([0-9]*\) + slice=0 + expr da0s0h : ..[0-9]*s[0-9]*\(.*\) + part=h + oldslice=0 + slice=1 + dkitos 1 + local s + s= + echo + slicename= + dkminor 0 0 1 2 + echo 65538 + minor=65538 + mknod da0 b 4 65538 + rm -f da0 + /sbin/mknod da0 b 4 65538 + chown root.wheel da0 + mknod rda0 c 13 65538 + rm -f rda0 + /sbin/mknod rda0 c 13 65538 + chown root.wheel rda0 + slice=0 + dkminor 0 0 0 0 + echo 0 + minor=0 + dkitop 0 + local p + p=a + echo a + partname=a + mknod da0a b 4 0 + rm -f da0a + /sbin/mknod da0a b 4 0 + chown root.wheel da0a + mknod rda0a c 13 0 + rm -f rda0a + /sbin/mknod rda0a c 13 0 + chown root.wheel rda0a + dkminor 0 0 0 1 MAKEDEV: arith: syntax error: "?† ž† " + minor= + dkitop 1 + local p + p=b + echo b + partname=b + mknod da0b b 4 + rm -f da0b + /sbin/mknod da0b b 4 usage: mknod name [b | c] major minor + die 2 /sbin/mknod da0b b 4 failed + echo /sbin/mknod da0b /sbin/mknod da0b + exit 2 sh-2.03# exit Script done on Tue Jul 27 15:34:56 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 6:37: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 3D93A1540D for ; Tue, 27 Jul 1999 06:36:59 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-27.iptelecom.net.ua [212.42.68.218]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA04914; Tue, 27 Jul 1999 16:43:39 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id QAA11554; Tue, 27 Jul 1999 16:35:53 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379DB5B8.CD5E2D99@altavista.net> Date: Tue, 27 Jul 1999 16:35:53 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Philipp Mergenthaler , current@freebsd.org Subject: Re: MAKEDEV (or sh?) broken References: <379D8807.B9DE0277@altavista.net> <19990727145128.A17042@rz.uni-karlsruhe.de> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Philipp Mergenthaler wrote: > Hi, > > On Tue, Jul 27, 1999 at 01:20:55PM +0300, Maxim Sobolev wrote: > > On my CURRENT system cvsup'ed and builded yesterday when I'm trying to > > do "cd /dev; sh MAKEDEV all" I see following errors: > > > > Script started on Tue Jul 27 13:14:47 1999 > > sh-2.03# cd /dev ; sh MAKEDEV all > > MAKEDEV: arith: syntax error: "?† ž† " > > I saw a similar error ("arith:") once when I had compiled /bin/sh > with high optimization (ok, that was with gcc, not egcs). > So, as a wild guess, maybe you did use some high optimization > and hit a bug in egcs? No, I'm not using high optimisation (I think my -O2 can be considered relatively safe). But to check for shure I've recompilled sh with -O and it yeld exctly the same result as it was with -O2. -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 6:54:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 9557E14DBF for ; Tue, 27 Jul 1999 06:54:30 -0700 (PDT) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id BAA18844 for freebsd-current@freebsd.org; Wed, 28 Jul 1999 01:54:29 +1200 (NZST) Date: Wed, 28 Jul 1999 01:54:28 +1200 From: Joe Abley To: freebsd-current@freebsd.org Subject: coda in STABLE Message-ID: <19990728015428.A27527@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, From /sys/coda/coda.h on 3.2-STABLE, it looks like the version in the tree is 3.1. At http://www.coda.cs.cmu.edu/download.html#gpl_notice it is mentioned that version 5 clients and servers are not backwards compatible with version 4 (and by inference, previous versions, hence my first paragraph). Earlier on the same page, -CURRENT is mentioned, but not -STABLE. Does -CURRENT have different kernel hooks for coda than -STABLE? If so, does anybody know if work is progressing to back-port the changes? If anybody has any general experience of coda on FreeBSD, and feels like sharing it, I'm keen to listen :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 7:29:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id A29F414D80; Tue, 27 Jul 1999 07:29:24 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup4-5.iptelecom.net.ua [212.42.68.100]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id RAA09533; Tue, 27 Jul 1999 17:35:59 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id RAA12001; Tue, 27 Jul 1999 17:29:11 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379DC237.152F9C0A@altavista.net> Date: Tue, 27 Jul 1999 17:29:11 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Brian Somers Cc: current@FreeBSD.ORG, brian@FreeBSD.ORG, jmg@FreeBSD.ORG Subject: Re: [Fwd: Tun interface related panic] References: <199907240252.DAA03879@keep.lan.Awfulhak.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > Ok, I found the culprit in ppp. I'm committing a change now. > > Thanks for the report ! It seems that have found other culpit, because I'm continuing to see "Error: ip_Input: deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed and builded today. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 8:47:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 46D9C15914; Tue, 27 Jul 1999 08:41:40 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id QAA68049; Tue, 27 Jul 1999 16:41:13 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id QAA04883; Tue, 27 Jul 1999 16:41:42 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199907271541.QAA04883@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: Brian Somers , current@FreeBSD.ORG, brian@FreeBSD.ORG, jmg@FreeBSD.ORG Subject: Re: [Fwd: Tun interface related panic] In-reply-to: Your message of "Tue, 27 Jul 1999 17:29:11 +0300." <379DC237.152F9C0A@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii From: Brian Somers Date: Tue, 27 Jul 1999 16:41:42 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Brian Somers wrote: > > > Ok, I found the culprit in ppp. I'm committing a change now. > > > > Thanks for the report ! > > It seems that have found other culpit, because I'm continuing to see "Error: ip_Input: > deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed and builded > today. I've fixed it in -current, not yet in -stable. You could try the latest ppp archive from my web site if you want to confirm whether or not the fix works. > -Maxim -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 9: 6:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A76814D87; Tue, 27 Jul 1999 09:06:19 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-15.iptelecom.net.ua [212.42.68.206]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id TAA17451; Tue, 27 Jul 1999 19:13:01 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id TAA12361; Tue, 27 Jul 1999 19:06:15 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379DD8F6.F7FAF025@altavista.net> Date: Tue, 27 Jul 1999 19:06:14 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: Brian Somers Cc: Brian Somers , current@FreeBSD.ORG, brian@FreeBSD.ORG, jmg@FreeBSD.ORG Subject: Re: [Fwd: Tun interface related panic] References: <199907271541.QAA04883@keep.lan.Awfulhak.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > Brian Somers wrote: > > > > > Ok, I found the culprit in ppp. I'm committing a change now. > > > > > > Thanks for the report ! > > > > It seems that have found other culpit, because I'm continuing to see "Error: ip_Input: > > deflink: wrote 0, got Input/output error" (3.2-STABLE) even using ppp cvsup'ed and builded > > today. > > I've fixed it in -current, not yet in -stable. You could try the > latest ppp archive from my web site if you want to confirm whether > or not the fix works. No, you misunderstood me. I'm usually using on my 3.2 box the ppp compiled from the current sources of 4.0 (BTW ppp from 3.2 doesn't have this bug). When I've wrote that sources was cvsup'ed today I mean 4.0 sources not 3.2. -Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 12:53:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id D117714C9E; Tue, 27 Jul 1999 12:53:19 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebv6.dialup.mindspring.com [165.247.47.230]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01669; Tue, 27 Jul 1999 15:23:49 -0400 Message-ID: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: , , , , Subject: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 15:54:07 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having a pecular problem trying to run SCO binaries under the iBCS emulation in Linux. I figure the problem may be related to Linux lacking the necesary functionality to support files larger than 2GB which this SCO binary supports. I was thinking of trying freeBSD with its SCO emulation support but I am uncertain whether freeBSD supports files larger than 2GB on 32bit x86 platforms. Anybody know the answer to this question. Also if only a peticular version supports it, let me know so I can get the correct version. The program that I am trying to get to run under freeBSD or Linux is the Microfocus cobol runtime. Everything else in that COBOL development package works except the actual runtime, which just happens to support large files (> 2GB) for the COBOL databases. This is why I fugure its dying under Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 12:55:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id 0A3AD15337; Tue, 27 Jul 1999 12:55:12 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebsm.dialup.mindspring.com [165.247.47.150]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01675; Tue, 27 Jul 1999 15:25:36 -0400 Message-ID: <001301bed86a$1d2e2910$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: , , , , Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 15:55:51 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I forgot, please forward a copy of any responses to my email address as I am not a member of any of these lists. ----- Original Message ----- From: NT Workstation User To: ; ; ; ; Sent: Tuesday, July 27, 1999 3:54 PM Subject: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms > I am having a pecular problem trying to run SCO binaries under the iBCS > emulation in Linux. I figure the problem may be related to Linux lacking > the necesary functionality to support files larger than 2GB which this SCO > binary supports. I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. Anybody know the answer to this question. Also if > only a peticular version supports it, let me know so I can get the correct > version. The program that I am trying to get to run under freeBSD or Linux > is the Microfocus cobol runtime. Everything else in that COBOL development > package works except the actual runtime, which just happens to support large > files (> 2GB) for the COBOL databases. This is why I fugure its dying under > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 13: 6: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 8300F153D1; Tue, 27 Jul 1999 13:05:39 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (209-122-238-225.s225.tnt2.lnh.md.dialup.rcn.com [209.122.238.225]) by tasam.com (8.9.3/8.9.1) with SMTP id QAA11004; Tue, 27 Jul 1999 16:05:23 -0400 (EDT) Message-ID: <009a01bed86b$601baf80$0286860a@tasam.com> From: "Joe Gleason" To: "NT Workstation User" , , , , , References: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 16:05:17 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am uncertain about the emulation issues, but I know my backup tar files often exceed 4GB on x86 systems. I have done this with versions FreeBSD 2.2.2-3.2. I have never heard it mentioned before, so I assume it works on all versions. Probably a UFS thing. Joe Gleason Tasam > I am having a pecular problem trying to run SCO binaries under the iBCS > emulation in Linux. I figure the problem may be related to Linux lacking > the necesary functionality to support files larger than 2GB which this SCO > binary supports. I was thinking of trying freeBSD with its SCO emulation > support but I am uncertain whether freeBSD supports files larger than 2GB on > 32bit x86 platforms. Anybody know the answer to this question. Also if > only a peticular version supports it, let me know so I can get the correct > version. The program that I am trying to get to run under freeBSD or Linux > is the Microfocus cobol runtime. Everything else in that COBOL development > package works except the actual runtime, which just happens to support large > files (> 2GB) for the COBOL databases. This is why I fugure its dying under > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 13:22:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from Hinako.AMBusiness.com (hinako.ambusiness.com [204.183.184.20]) by hub.freebsd.org (Postfix) with ESMTP id 28D6114DE3; Tue, 27 Jul 1999 13:22:17 -0700 (PDT) (envelope-from gdsntusr@globaldelsys.com) Received: from optimant (user-2ivebm6.dialup.mindspring.com [165.247.46.198]) by Hinako.AMBusiness.com (8.9.3/8.9.3) with SMTP id PAA01720; Tue, 27 Jul 1999 15:52:44 -0400 Message-ID: <001901bed86d$e7b4c010$2bc809c0@HalbartAir.com> From: "NT Workstation User" To: "Joe Gleason" , , , , , References: <000d01bed869$ddeec110$2bc809c0@HalbartAir.com> <009a01bed86b$601baf80$0286860a@tasam.com> Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms Date: Tue, 27 Jul 1999 16:22:59 -0400 Organization: Global Delivery Systems X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm, I'm not sure whether tar files count. See the 2GB file limit under Linux comes from the maximum value of a 32bit signed integer. Because the file system calls use those 32bit integers a file's size is limited to 2GB, at least if you want random access. tar files generally aren't accessed in a random access fashion, instead the file is treated as a byte stream. Though I can't remember exactly, I think I created (> 2GB) tar files under Linux once too. I know SCO and other commercial OSes have addition file functions for large files which use 64bit integers to overcome this limitation. As Linux lacks this feature I am considering giving freeBSD (or any of the other BSDs) a try. Of course this leaves me wondering whether to try the pre-4.0 or the 3.2 version. ----- Original Message ----- From: Joe Gleason To: NT Workstation User ; ; ; ; ; Sent: Tuesday, July 27, 1999 4:05 PM Subject: Re: Does freeBSD or any related freeBSDs support file larger than 2GB on 32bit x86 platforms > I am uncertain about the emulation issues, but I know my backup tar files > often exceed 4GB on x86 systems. > I have done this with versions FreeBSD 2.2.2-3.2. I have never heard it > mentioned before, so I assume it works on all versions. Probably a UFS > thing. > > Joe Gleason > Tasam > > > I am having a pecular problem trying to run SCO binaries under the iBCS > > emulation in Linux. I figure the problem may be related to Linux lacking > > the necesary functionality to support files larger than 2GB which this SCO > > binary supports. I was thinking of trying freeBSD with its SCO emulation > > support but I am uncertain whether freeBSD supports files larger than 2GB > on > > 32bit x86 platforms. Anybody know the answer to this question. Also if > > only a peticular version supports it, let me know so I can get the correct > > version. The program that I am trying to get to run under freeBSD or > Linux > > is the Microfocus cobol runtime. Everything else in that COBOL > development > > package works except the actual runtime, which just happens to support > large > > files (> 2GB) for the COBOL databases. This is why I fugure its dying > under > > Linux, so does freeBSD on 32bit x86 platforms support files > 2GB? > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 14: 0:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 2B6C014BE6 for ; Tue, 27 Jul 1999 14:00:17 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.139]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA3B24 for ; Tue, 27 Jul 1999 23:00:09 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id XAA05329 for current@freebsd.org; Tue, 27 Jul 1999 23:00:16 +0200 (CEST) (envelope-from asmodai) Date: Tue, 27 Jul 1999 23:00:15 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: Library question/challenge Message-ID: <19990727230015.B393@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ in case this should've been -questions, please redirect this thread there ] Hi, after a make world on the 26th I tried to start netscape today and got a library error: /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older than expected 0, using it anyway ld.so failed: bad magic number in "/usr/lib/libc.so.3" This is netscape4.5 on CURRENT tracked since October 1998. One change since my previous builds is that I uncommented compat22 and compat3x prior to making world. I have the default aout ld path in /etc/defaults/rc.conf, none in /etc/rc.conf. A ldconfig -aout -r | head -2 yields: /var/run/ld.so.hints: search directories: /usr/lib/aout:/usr/lib/compat/aout: /usr/X11R6/lib/aout:/usr/local/lib/aout [ it has about 66 libs in this hints file ] I also get the above error when trying to install a newer netscape. Can it be I need to rebuild my XFree? I currently run 3.3.3.1 compiled under ELF and with a.out support AFAIK, else I couldn't have been running netscape before. Timestamp of /usr/X11r6/lib/aout is July 21st. /usr/lib/aout is dated March 20th /usr/lib/compat/aout is July 26th /usr/local/lib/aout is empty Anything you guys can think of, want to inspect, want me to test, because I cannot see where it goes wrong exactly. Thanks, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 14:25:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from shell3.ba.best.com (shell3.ba.best.com [206.184.139.134]) by hub.freebsd.org (Postfix) with ESMTP id F2C2614EE9 for ; Tue, 27 Jul 1999 14:25:32 -0700 (PDT) (envelope-from spatula@spatula.net) Received: from localhost (spatula@localhost [127.0.0.1]) by shell3.ba.best.com (8.9.3/8.9.2/best.sh) with ESMTP id OAA17524 for ; Tue, 27 Jul 1999 14:24:37 -0700 (PDT) Date: Tue, 27 Jul 1999 14:24:37 -0700 (PDT) From: Nick Johnson X-Sender: spatula@shell3.ba.best.com To: freebsd-current@freebsd.org Subject: Need help testing mods to nos-tun Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a few modifications to nos-tun in an attempt to make it a bit more robust and also to give it the ability to adapt to a link with an IP address that may change while the tunnel is up. I'd like to share my modifications with the rest of the community but... ...I lack sufficient facilities for testing my changes thoroughly. If you're interested, please take a look at http://www.spatula.net/nos-tun/ and see if it is now hopelessly broken. I'm especially interested in getting anyone who may already be using nos-tun and anyone who is using it across platforms to test my changes. More documentation about my changes can be found at the URL above, along with diffs & source code. Please send any feedback to me so I can correct any problems before doing a send-pr with the enhancements, thereby avoiding my looking like a complete imbecile. Nick -- "Unlike me, many of you have accepted the situation of your imprisonment and will die here like rotten cabbages!" - Number-6, "The Prisoner: Free For All" My PGP public key: http://www.spatula.net/pubkey.txt Nick Johnson, version 1.5 http://www.spatula.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 15: 5:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 82564153B9 for ; Tue, 27 Jul 1999 15:05:45 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id SAA58026; Tue, 27 Jul 1999 18:03:30 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Tue, 27 Jul 1999 18:03:30 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Maxim Sobolev Cc: current@FreeBSD.org Subject: Re: MAKEDEV (or sh?) broken In-Reply-To: <379DA85B.DA4E80AC@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, all recursive executions of it need to be -x too. The easiest way (if there's no environment variable for it, I don't recall), is to put "set -x" at the top of MAKEDEV. This will help, and then I'll understand much more. Thanks. I have a feeling it might be improper optimization breaking expr... Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 15:17:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D25F615386 for ; Tue, 27 Jul 1999 15:17:32 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id SAA07469 for ; Tue, 27 Jul 1999 18:16:46 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id SAA97333; Tue, 27 Jul 1999 18:16:45 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 27 Jul 1999 18:16:45 -0400 (EDT) To: current@freebsd.org Subject: diskless booting broken X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14238.9226.932501.308752@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Diskless (BOOTP_NFSROOT,NFS_ROOT) booting appears to be broken in -current. (at least on alpha, haven't tried x86): net0:> boot kernel.de1 /kernel.de1 data=0x261540+0x253f8 syms=[0x8+0x30ae0+0x8+0x232eb] Entering kernel.de1 at 0xfffffc0000325c80... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Tue Jul 27 14:46:14 EDT 1999 gallatin@broil.cs.duke.edu:/usr/src/sys/compile/BOOTP AlphaStation 500 or 600 (KN20AA) <.snip...> bootpc_init: wired to interface 'de1' bootpc_init: using network interface 'de1' Bootpc testing starting bootpc hw address is 0:0:f8:0:xx:yy My ip address is 152.3.x.y Server ip address is 152.3.x.y Gateway ip address is 0.0.0.0 Server name is xxx.cs.duke.edu boot file is /freebsd/diskless.alpha/boot/netboot Subnet mask is 255.255.0.0 rootfs is 152.3.x.y:/freebsd/diskless.alpha rootdev=0xffffffffffffffff error=6, panic: cannot mount root (2) panic Stopped at Debugger+0x2c: ldq ra,0(sp) <0xfffffc00005e3ca0> The rootdev is never set, so the mount is never attempted in vfs_mountrootfs. The appended hack (in the spirit of the first MFS_ROOT fix by John Birrell) seems to fix it temporarily. Can somebody with a clue please look into this? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 Index: vfs_conf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/vfs_conf.c,v retrieving revision 1.31 diff -u -b -B -c -r1.31 vfs_conf.c cvs diff: conflicting specifications of output style *** vfs_conf.c 1999/07/03 17:40:31 1.31 --- vfs_conf.c 1999/07/27 21:17:31 *************** *** 134,140 **** return ; } mp->mnt_flag |= MNT_ROOTFS; ! /* * Attempt the mount */ --- 134,142 ---- return ; } mp->mnt_flag |= MNT_ROOTFS; ! #if defined (BOOTP_NFSROOT) || defined (NFS_ROOT) ! err = VFS_MOUNT(mp, NULL, NULL, NULL, p); ! #else /* * Attempt the mount */ *************** *** 158,163 **** --- 160,166 ---- if (err != ENXIO) break; } + #endif if (err) { /* * XXX should ask the user for the name in some cases. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 19:55:59 1999 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 699F614C1A for ; Tue, 27 Jul 1999 19:55:49 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id WAA06022; Tue, 27 Jul 1999 22:52:36 -0400 (EDT) (envelope-from wollman) Date: Tue, 27 Jul 1999 22:52:36 -0400 (EDT) From: Garrett Wollman Message-Id: <199907280252.WAA06022@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: Nicolas Souchu , Bruce Evans , current@FreeBSD.ORG, des@flood.ping.uio.no, obrien@NUXI.com, sobomax@altavista.net Subject: Re: PLIP is still broken :( In-Reply-To: <55351.933013838@critter.freebsd.dk> References: <19990726202441.57962@breizh.teaser.fr> <55351.933013838@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > This is also something that should be changed since we are to modify > things anyway, it introduces un-needed delays (and jitter) in the > interrupt delivery. Plus, the resource manager has built-in hooks to manage resources which are time-shared by multiple devices. (The thing it's lacking, but ought to have, is a ``gang'' notion to claim several resources at once.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 20:57: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-2.uoregon.edu (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id 62BEF14DC3; Tue, 27 Jul 1999 20:56:56 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-2.uoregon.edu (8.9.1/8.8.7) id UAA13895; Tue, 27 Jul 1999 20:55:05 -0700 (PDT) Message-ID: <19990727205504.02382@hydrogen.fircrest.net> Date: Tue, 27 Jul 1999 20:55:04 -0700 From: John-Mark Gurney To: Kazutaka YOKOTA Cc: Gary Palmer , freebsd-current@FreeBSD.ORG Subject: Re: Patch for Alpha/AXP References: <86208.932805444@noop.colo.erols.net> <199907240854.RAA19619@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199907240854.RAA19619@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Sat, Jul 24, 1999 at 05:54:29PM +0900 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA scribbled this message on Jul 24: > > >> I am afraid this is not quite right. > >> > >> Bruce, Doug and I are currently in discussion to fix this. > > > >Hrm. Why does the AXP cons.c track udev_t while the x86 verson > >doesn't? As best as I can tell, the AXP doesn't seem to need it any > >more than the x86 does, unless I've missed something. > > As dev_t is now a struct, we cannot track dev_t for SYSCTL. It has to > be udev_t. sys/i386/i386/cons.c should be doing the same as the alpha > version, rather than vice versa. > > To quote Bruce: "alpha/alpha/cons.c should be identical with > i386/i386/cons.c and not in a machine-dependent place. All current > differences are bugs" :-) hmmm.. guess it's time for me to bring out my MI cons.c that I did a long time ago and dust it off?? Bruce kinda vetoed it, but I also didn't have the courage to commit it back then... and it's not hard to make it MI.... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jul 27 22:42:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id CD81F1502A for ; Tue, 27 Jul 1999 22:42:14 -0700 (PDT) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.8.8/8.8.8) with UUCP id IAA23300 for current@FreeBSD.org; Wed, 28 Jul 1999 08:40:21 +0400 (MSD) (envelope-from phantom@scorpion.crimea.ua) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id AAA05128 for current@FreeBSD.org; Wed, 28 Jul 1999 00:15:59 +0400 (MSD) Message-Id: <199907272015.AAA05128@scorpion.crimea.ua> Subject: ed? To: current@FreeBSD.org Date: Wed, 28 Jul 1999 00:15:58 +0400 (MSD) From: "Alexey M. Zelkin" X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! I am running CURRENT from 27 jul. So, I have PCI PnP Ethernet Adaptor and wrote in kernel config: > controller pnp0 > device ed0 at isa? disable port 0x280 irq 10 iomem 0xd8000 As usually this string included ethernet driver code into kernel and my card was found automaticly. But this time I pointed my eyes to dmesg output and found interesting thing: > ed0: irq 12 at device 9.0 on pci0 > ed0: address 00:00:21:c7:5b:a7, type NE2000 (16 bit) > devclass_alloc_unit: ed0 already exists, using next available unit number > isa0: on motherboard > ed1: not probed (disabled) So, what should do kernel when I insert new ISA ethernet into my machine and enable ed0 ? Logic tells that ed0 will change its name to ed1, and new card will stay ed0. Why my pnp ethernet was found as ed0 but not ed1 ? So, I would ask -- is this feature or bug ? If I am temporary changing my network devices configuration can I be sure that ethernet names will not be automaticly changed ? -- Sincerely Yours, | phantom@crimea.edu (primary) Alexey Zelkin | phantom@scorpion.crimea.ua (home) | ICQ: #6196584, FIDO: 2:460/12.26 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 1:46: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 1A4D41541C; Wed, 28 Jul 1999 01:45:47 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup2-36.iptelecom.net.ua [212.42.68.227]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id KAA05588; Wed, 28 Jul 1999 10:20:37 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id KAA14826; Wed, 28 Jul 1999 10:12:46 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379EAD6D.3A352C47@altavista.net> Date: Wed, 28 Jul 1999 10:12:45 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: "Brian F. Feldman" Cc: current@FreeBSD.ORG Subject: Sh broken (was: MAKEDEV (or sh?) broken) References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian F. Feldman" wrote: > Actually, all recursive executions of it need to be -x too. The easiest > way (if there's no environment variable for it, I don't recall), is to > put "set -x" at the top of MAKEDEV. > > This will help, and then I'll understand much more. Thanks. I have > a feeling it might be improper optimization breaking expr... Ok, I've did as you suggested and also make similar test using sh from the 3.2-STABLE. Following is results: 1. Using /bin/sh from -CURRENT (compiled with -O) sh-2.03# /bin/sh -x MAKEDEV da0s0h + set -x + PATH=/sbin:/bin/:/usr/bin:/usr/sbin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/X11R6/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + name=da + blk=4 + chr=13 + expr da0s0h : ..\([0-9]*\)s + unit=0 + expr da0s0h : ..[0-9]*s\([0-9]*\) + slice=0 + expr da0s0h : ..[0-9]*s[0-9]*\(.*\) + part=h + oldslice=0 + slice=1 + dkitos 1 + local s + s= + echo + slicename= + dkminor 0 0 1 2 + echo 65538 + minor=65538 + mknod da0 b 4 65538 + rm -f da0 + /sbin/mknod da0 b 4 65538 + chown root.wheel da0 + mknod rda0 c 13 65538 + rm -f rda0 + /sbin/mknod rda0 c 13 65538 + chown root.wheel rda0 + slice=0 + dkminor 0 0 0 0 + echo 0 + minor=0 + dkitop 0 + local p + p=a + echo a + partname=a + mknod da0a b 4 0 + rm -f da0a + /sbin/mknod da0a b 4 0 + chown root.wheel da0a + mknod rda0a c 13 0 + rm -f rda0a + /sbin/mknod rda0a c 13 0 + chown root.wheel rda0a + dkminor 0 0 0 1 MAKEDEV: arith: syntax error: "?† ž† " + minor= + dkitop 1 + local p + p=b + echo b + partname=b + mknod da0b b 4 + rm -f da0b + /sbin/mknod da0b b 4 usage: mknod name [b | c] major minor + die 2 /sbin/mknod da0b b 4 failed + echo /sbin/mknod da0b /sbin/mknod da0b + exit 2 2. Using sh from my -STABLE box sh-2.03# ../sh -x MAKEDEV da0s0h + set -x + PATH=/sbin:/bin/:/usr/bin:/usr/sbin:/usr/local/bin:/sbin:/usr/sbin:/usr/local/sbin:/bin:/usr/bin:/usr/X11R6/bin + umask 77 + dkrawpart=2 + dkcompatslice=0 + dkrawslice=1 + disk_umask=037 + tape_umask=017 + umask 037 + name=da + blk=4 + chr=13 + expr da0s0h : ..\([0-9]*\)s + unit=0 + expr da0s0h : ..[0-9]*s\([0-9]*\) + slice=0 + expr da0s0h : ..[0-9]*s[0-9]*\(.*\) + part=h + oldslice=0 + slice=1 + dkitos 1 + local s + s= + echo + slicename= + dkminor 0 0 1 2 + echo 65538 + minor=65538 + mknod da0 b 4 65538 + rm -f da0 + /sbin/mknod da0 b 4 65538 + chown root.wheel da0 + mknod rda0 c 13 65538 + rm -f rda0 + /sbin/mknod rda0 c 13 65538 + chown root.wheel rda0 + slice=0 + dkminor 0 0 0 0 + echo 0 + minor=0 + dkitop 0 + local p + p=a + echo a + partname=a + mknod da0a b 4 0 + rm -f da0a + /sbin/mknod da0a b 4 0 + chown root.wheel da0a + mknod rda0a c 13 0 + rm -f rda0a + /sbin/mknod rda0a c 13 0 + chown root.wheel rda0a + dkminor 0 0 0 1 + echo 1 + minor=1 + dkitop 1 + local p + p=b + echo b + partname=b + mknod da0b b 4 1 + rm -f da0b + /sbin/mknod da0b b 4 1 + chown root.wheel da0b + mknod rda0b c 13 1 + rm -f rda0b + /sbin/mknod rda0b c 13 1 + chown root.wheel rda0b + dkminor 0 0 0 2 + echo 2 + minor=2 + dkitop 2 + local p + p=c + echo c + partname=c + mknod da0c b 4 2 + rm -f da0c + /sbin/mknod da0c b 4 2 + chown root.wheel da0c + mknod rda0c c 13 2 + rm -f rda0c + /sbin/mknod rda0c c 13 2 + chown root.wheel rda0c + dkminor 0 0 0 3 + echo 3 + minor=3 + dkitop 3 + local p + p=d + echo d + partname=d + mknod da0d b 4 3 + rm -f da0d + /sbin/mknod da0d b 4 3 + chown root.wheel da0d + mknod rda0d c 13 3 + rm -f rda0d + /sbin/mknod rda0d c 13 3 + chown root.wheel rda0d + dkminor 0 0 0 4 + echo 4 + minor=4 + dkitop 4 + local p + p=e + echo e + partname=e + mknod da0e b 4 4 + rm -f da0e + /sbin/mknod da0e b 4 4 + chown root.wheel da0e + mknod rda0e c 13 4 + rm -f rda0e + /sbin/mknod rda0e c 13 4 + chown root.wheel rda0e + dkminor 0 0 0 5 + echo 5 + minor=5 + dkitop 5 + local p + p=f + echo f + partname=f + mknod da0f b 4 5 + rm -f da0f + /sbin/mknod da0f b 4 5 + chown root.wheel da0f + mknod rda0f c 13 5 + rm -f rda0f + /sbin/mknod rda0f c 13 5 + chown root.wheel rda0f + dkminor 0 0 0 6 + echo 6 + minor=6 + dkitop 6 + local p + p=g + echo g + partname=g + mknod da0g b 4 6 + rm -f da0g + /sbin/mknod da0g b 4 6 + chown root.wheel da0g + mknod rda0g c 13 6 + rm -f rda0g + /sbin/mknod rda0g c 13 6 + chown root.wheel rda0g + dkminor 0 0 0 7 + echo 7 + minor=7 + dkitop 7 + local p + p=h + echo h + partname=h + mknod da0h b 4 7 + rm -f da0h + /sbin/mknod da0h b 4 7 + chown root.wheel da0h + mknod rda0h c 13 7 + rm -f rda0h + /sbin/mknod rda0h c 13 7 + chown root.wheel rda0h + chgrp operator da0 da0a da0b da0c da0d da0e da0f da0g da0h rda0 rda0a rda0b rda0c rda0d rda0e rda0f rda0g rda0h + umask 77 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 2:34: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 28F231542C; Wed, 28 Jul 1999 02:33:53 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id KAA98210; Wed, 28 Jul 1999 10:32:33 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id JAA01248; Wed, 28 Jul 1999 09:54:32 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199907280854.JAA01248@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: sobomax@altavista.net Cc: Brian Somers , Brian Somers , current@FreeBSD.ORG, brian@FreeBSD.ORG, jmg@FreeBSD.ORG Subject: Re: [Fwd: Tun interface related panic] In-reply-to: Your message of "Tue, 27 Jul 1999 19:06:14 +0300." <379DD8F6.F7FAF025@altavista.net> Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_13032826870" Date: Wed, 28 Jul 1999 09:54:32 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_13032826870 Content-Type: text/plain; charset=us-ascii [.....] > > I've fixed it in -current, not yet in -stable. You could try the > > latest ppp archive from my web site if you want to confirm whether > > or not the fix works. > > No, you misunderstood me. I'm usually using on my 3.2 box the ppp compiled from the current > sources of 4.0 (BTW ppp from 3.2 doesn't have this bug). When I've wrote that sources was > cvsup'ed today I mean 4.0 sources not 3.2. Can you try applying the attached patch and enabling debug logging ? What do the diagnostics say for that packet before you see the IO error ? Cheers. > -Maxim > -- > "We believe in the Power and the Might!" > (Manowar, 1996) > ---------------------------------------- > Maxim V. Sobolev, Financial Analyst, > Vega International Capital > Phone: +380-(44)-246-6396 > Fax: +380-(44)-220-8715 > E-mail: sobomax@altavista.net > ICQ: #42290709 > ---------------------------------------- -- Brian Don't _EVER_ lose your sense of humour ! --==_Exmh_13032826870 Content-Type: application/x-patch ; name="link.patch" Content-Description: link.patch Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="link.patch" Index: link.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/usr.sbin/ppp/link.c,v retrieving revision 1.12 diff -u -r1.12 link.c --- link.c 1999/06/02 15:59:03 1.12 +++ link.c 1999/07/28 08:51:44 @@ -263,6 +263,8 @@ if (l->layer[layer]->pull !=3D NULL) bp =3D (*l->layer[layer]->pull)(b, l, bp, &proto); = + log_Printf(LogDEBUG, "link_PullPacket: Proto 0x%04x length %d\n", pr= oto, mbuf_Length(bp)); + if (layer =3D=3D l->nlayers - 1) { /* We've just done the top layer, despatch the packet(s) */ while (bp) { --==_Exmh_13032826870-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 4:47:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 66EBF14F22 for ; Wed, 28 Jul 1999 04:47:27 -0700 (PDT) (envelope-from dispatch@blackhelicopters.org) Received: (from dispatch@localhost) by blackhelicopters.org (8.8.8/8.8.8) id HAA20946; Wed, 28 Jul 1999 07:44:55 -0400 (EDT) (envelope-from dispatch) From: Dispatcher Message-Id: <199907281144.HAA20946@blackhelicopters.org> Subject: Re: ed? In-Reply-To: <199907272015.AAA05128@scorpion.crimea.ua> from "Alexey M. Zelkin" at "Jul 28, 1999 0:15:58 am" To: phantom@cris.net (Alexey M. Zelkin) Date: Wed, 28 Jul 1999 07:44:55 -0400 (EDT) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Please check the freebsd-questions mailing list archive at http://www.freebsd.org/search/#mailinglists This question has been answered many times there, in great detail. Regards, ==ml > Hello ! > > I am running CURRENT from 27 jul. > So, I have PCI PnP Ethernet Adaptor and wrote in kernel config: > > > controller pnp0 > > device ed0 at isa? disable port 0x280 irq 10 iomem 0xd8000 > > As usually this string included ethernet driver code into kernel > and my card was found automaticly. But this time I pointed my > eyes to dmesg output and found interesting thing: > > > ed0: irq 12 at device 9.0 on pci0 > > ed0: address 00:00:21:c7:5b:a7, type NE2000 (16 bit) > > devclass_alloc_unit: ed0 already exists, using next available unit number > > isa0: on motherboard > > ed1: not probed (disabled) > > So, what should do kernel when I insert new ISA ethernet into my machine and > enable ed0 ? Logic tells that ed0 will change its name to ed1, and > new card will stay ed0. > > Why my pnp ethernet was found as ed0 but not ed1 ? > > So, I would ask -- is this feature or bug ? If I am temporary changing my > network devices configuration can I be sure that ethernet names will not > be automaticly changed ? > > -- > Sincerely Yours, | phantom@crimea.edu (primary) > Alexey Zelkin | phantom@scorpion.crimea.ua (home) > | ICQ: #6196584, FIDO: 2:460/12.26 > > > 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 Wed Jul 28 7:17:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 4D11815495 for ; Wed, 28 Jul 1999 07:17:11 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id KAA27641 for ; Wed, 28 Jul 1999 10:16:46 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA10587; Wed, 28 Jul 1999 10:16:16 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA98204 for freebsd-current@freebsd.org; Wed, 28 Jul 1999 10:16:16 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199907281416.KAA98204@bb01f39.unx.sas.com> Subject: make release doc failure To: freebsd-current@freebsd.org Date: Wed, 28 Jul 1999 10:16:16 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, For those of you who may not have seen this, and my apologies if I haven't seen it and everyone else has... ===> FAQ sgmlfmt -f html -links /usr/doc/FAQ/FAQ.sgml sgmlfmt -f latin1 -links /usr/doc/FAQ/FAQ.sgml sgmlfmt -f ascii -links /usr/doc/FAQ/FAQ.sgml FAQ.trf:7781: warning: can't find special character `:i' FAQ.trf:7781: warning: can't find special character `:i' ===> en ===> en/handbook /usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/docbook/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/sgml/freebsd.dsl -t sgml handbook.sgml /usr/local/bin/jade:serialcomms/chapter.sgml:2016:2:E: general entity "man.boot.8" not defined and no default entity /usr/local/bin/jade:serialcomms/chapter.sgml:2016:19:E: general entity "man.loader.8" not defined and no default entity /usr/local/bin/jade:serialcomms/chapter.sgml:2680:12:E: general entity "man.loader.conf.5" not defined and no default entity *** Error code 1 Stop. *** Error code 1 sources current as of 2am EST, about 8 hours ago). Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 7:23:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from ender.ncsa.es (ender.ncsa.es [194.179.50.15]) by hub.freebsd.org (Postfix) with ESMTP id 8F0A114D73 for ; Wed, 28 Jul 1999 07:23:20 -0700 (PDT) (envelope-from jesusr@ncsa.es) Received: from ender.ncsa.es (localhost [127.0.0.1]) by ender.ncsa.es (8.9.3/8.9.3) with ESMTP id QAA20700; Wed, 28 Jul 1999 16:26:10 +0200 (CEST) (envelope-from jesusr@ncsa.es) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199907281416.KAA98204@bb01f39.unx.sas.com> Date: Wed, 28 Jul 1999 16:26:09 +0200 (CEST) Reply-To: jesusr@ncsa.es Organization: Nexus Comunicaciones, S.A. From: Jesus Rodriguez To: "John W. DeBoskey" Subject: RE: make release doc failure Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jul-99 John W. DeBoskey wrote: > hi, > > For those of you who may not have seen this, and my apologies > if I haven't seen it and everyone else has... > > ===> en/handbook > /usr/local/bin/jade -V html-manifest -ioutput.html -c > /usr/doc/share/sgml/catalog -c > /usr/local/share/sgml/docbook/dsssl/modular/catalog -c > /usr/local/share/sgml/docbook/catalog -c /usr/local/share/sgml/jade/catalog > -d /usr/doc/share/sgml/freebsd.dsl -t sgml handbook.sgml > /usr/local/bin/jade:serialcomms/chapter.sgml:2016:2:E: general entity > "man.boot.8" not defined and no default entity > /usr/local/bin/jade:serialcomms/chapter.sgml:2016:19:E: general entity > "man.loader.8" not defined and no default entity > /usr/local/bin/jade:serialcomms/chapter.sgml:2680:12:E: general entity > "man.loader.conf.5" not defined and no default entity > *** Error code 1 I think Nik has committed these files this morning... handbook has builded with no problem for me with sources of 15 minutes ago. Saludos JesusR. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 7:35:11 1999 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 E92511549D; Wed, 28 Jul 1999 07:35:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id KAA07938; Wed, 28 Jul 1999 10:34:03 -0400 (EDT) (envelope-from wollman) Date: Wed, 28 Jul 1999 10:34:03 -0400 (EDT) From: Garrett Wollman Message-Id: <199907281434.KAA07938@khavrinen.lcs.mit.edu> To: Doug Rabson Cc: current@FreeBSD.org Subject: cvs commit: src/sys/alpha/include resource.h src/sys/alpha/pci pcibus.c src/sys/i386/include resource.h src/sys/pci pci.c pci_compat.c In-Reply-To: <199907280757.AAA19112@freefall.freebsd.org> References: <199907280757.AAA19112@freefall.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Add support for SYS_RES_DENSE and SYS_RES_BWX resource types. These are > equivalent to SYS_RES_MEMORY for x86 but for alpha, the rman_get_virtual() > address of the resource is initialised to point into either dense-mapped > or bwx-mapped space respectively, allowing direct memory pointers to be > used to device memory. This makes me rather uncomfortable, on several fronts. I believe it would be more appropriate to add a type argument to rman_get_virtual. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 8:26:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id B5FC315044 for ; Wed, 28 Jul 1999 08:26:25 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA01382 for ; Wed, 28 Jul 1999 11:25:05 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17485; Wed, 28 Jul 1999 11:24:34 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id LAA61875; Wed, 28 Jul 1999 11:24:34 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199907281524.LAA61875@dean.pc.sas.com> Subject: sysinstall network performance To: freebsd-current@freebsd.org Date: Wed, 28 Jul 1999 11:24:34 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, During recent installs using the 7/26 snap, I noticed that the transfer rate for the "ports" distribution was about twice as fast as SNAPs from the beginning of the month. Previously I was seeing a download rate of around 13 KB/s, while now I'm seeing around 28 KB/s (while these rates may sound horrrendous, it's typical of what we get when installing ports - other distributions generally hit upwards of about 800 KB/s). I was wondering what to attribute this better performance to. Could this be due to the new network driver / newbus integration? Just curious (and pleased). Thanks, -Brian P.S. - we track current and build our own SNAPs locally on a daily basis for testing -- Brian Dean SAS Institute Inc brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 8:33:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id EE86F14FEC for ; Wed, 28 Jul 1999 08:33:20 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA14694; Wed, 28 Jul 1999 11:33:54 -0400 From: Bill Paul Message-Id: <199907281533.LAA14694@skynet.ctr.columbia.edu> Subject: Re: sysinstall network performance To: brdean@unx.sas.com (Brian Dean) Date: Wed, 28 Jul 1999 11:33:52 -0400 (EDT) Cc: current@freebsd.org In-Reply-To: <199907281524.LAA61875@dean.pc.sas.com> from "Brian Dean" at Jul 28, 99 11:24:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1329 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Brian Dean had to walk into mine and say: > Hi, > > During recent installs using the 7/26 snap, I noticed that the > transfer rate for the "ports" distribution was about twice as fast as > SNAPs from the beginning of the month. Previously I was seeing a > download rate of around 13 KB/s, while now I'm seeing around 28 KB/s > (while these rates may sound horrrendous, it's typical of what we get > when installing ports - other distributions generally hit upwards of > about 800 KB/s). > > I was wondering what to attribute this better performance to. Could > this be due to the new network driver / newbus integration? Well, since you didn't tell us what kind of network card(s) you have, that's impossible to say. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 8:39:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 2EAB6154B4 for ; Wed, 28 Jul 1999 08:39:10 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:cA1z3mOv6u96jrGvQbJUuvexaVS4iWEJ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id AAA05398; Thu, 29 Jul 1999 00:37:48 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id AAA28721; Thu, 29 Jul 1999 00:42:06 +0900 (JST) Message-Id: <199907281542.AAA28721@zodiac.mech.utsunomiya-u.ac.jp> To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: make release doc failure In-reply-to: Your message of "Wed, 28 Jul 1999 10:16:16 -0400." <199907281416.KAA98204@bb01f39.unx.sas.com> References: <199907281416.KAA98204@bb01f39.unx.sas.com> Date: Thu, 29 Jul 1999 00:42:05 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For those of you who may not have seen this, and my apologies >if I haven't seen it and everyone else has... [...] >===> en/handbook >/usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/cat >alog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/shar >e/sgml/docbook/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/shar >e/sgml/freebsd.dsl -t sgml handbook.sgml >/usr/local/bin/jade:serialcomms/chapter.sgml:2016:2:E: general entity "man.boo >t.8" not defined and no default entity >/usr/local/bin/jade:serialcomms/chapter.sgml:2016:19:E: general entity "man.lo >ader.8" not defined and no default entity >/usr/local/bin/jade:serialcomms/chapter.sgml:2680:12:E: general entity "man.lo >ader.conf.5" not defined and no default entity >*** Error code 1 [...] You need the following patch to doc/share/sgml/man-refs.ent. I submitted this to Nik this morning. Kazu Index: man-refs.ent =================================================================== RCS file: /src/CVS/doc/share/sgml/man-refs.ent,v retrieving revision 1.6 diff -u -r1.6 man-refs.ent --- man-refs.ent 1999/06/07 22:33:12 1.6 +++ man-refs.ent 1999/07/19 10:06:11 @@ -79,6 +79,7 @@ + @@ -92,6 +93,7 @@ + @@ -106,6 +108,7 @@ + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 8:40:13 1999 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 778E614DFD for ; Wed, 28 Jul 1999 08:40:08 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id LAA09614; Wed, 28 Jul 1999 11:39:58 -0400 (EDT) (envelope-from wollman) Date: Wed, 28 Jul 1999 11:39:58 -0400 (EDT) From: Garrett Wollman Message-Id: <199907281539.LAA09614@khavrinen.lcs.mit.edu> To: Brian Dean Cc: freebsd-current@FreeBSD.ORG Subject: sysinstall network performance In-Reply-To: <199907281524.LAA61875@dean.pc.sas.com> References: <199907281524.LAA61875@dean.pc.sas.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > During recent installs using the 7/26 snap, I noticed that the > transfer rate for the "ports" distribution was about twice as fast as > SNAPs from the beginning of the month. > I was wondering what to attribute this better performance to. Could > this be due to the new network driver / newbus integration? Jordan stopped including CVS directories in the /usr/ports tarball. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 8:40:51 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id F15AF154C6 for ; Wed, 28 Jul 1999 08:40:43 -0700 (PDT) (envelope-from brdean@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id LAA02412; Wed, 28 Jul 1999 11:40:32 -0400 (EDT) Received: from dean.pc.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA19110; Wed, 28 Jul 1999 11:40:01 -0400 Received: (from brdean@localhost) by dean.pc.sas.com (8.9.3/8.9.3) id LAA61947; Wed, 28 Jul 1999 11:40:00 -0400 (EDT) (envelope-from brdean) From: Brian Dean Message-Id: <199907281540.LAA61947@dean.pc.sas.com> Subject: Re: sysinstall network performance In-Reply-To: <199907281533.LAA14694@skynet.ctr.columbia.edu> from Bill Paul at "Jul 28, 1999 11:33:52 am" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Wed, 28 Jul 1999 11:40:00 -0400 (EDT) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Brian Dean had > to walk into mine and say: > > > I was wondering what to attribute this better performance to. Could > > this be due to the new network driver / newbus integration? > > Well, since you didn't tell us what kind of network card(s) you have, > that's impossible to say. Sorry ... I'm using the fxp driver. Thanks, -Brian -- Brian Dean SAS Institute Inc brdean@unx.sas.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 9:55:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 7276B14E8E for ; Wed, 28 Jul 1999 09:55:46 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from vega. (dialup3-19.iptelecom.net.ua [212.42.69.210]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id UAA24074 for ; Wed, 28 Jul 1999 20:00:33 +0300 (EEST) Received: from altavista.net (big_brother [192.168.1.1]) by vega. (8.9.3/8.9.3) with ESMTP id TAA17453 for ; Wed, 28 Jul 1999 19:52:18 +0300 (EEST) (envelope-from sobomax@altavista.net) Message-ID: <379F3541.1A52F974@altavista.net> Date: Wed, 28 Jul 1999 19:52:17 +0300 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.61 [en] (WinNT; I) X-Accept-Language: ru,uk,en MIME-Version: 1.0 To: current@freebsd.org Subject: Strange ppp dial filter failure. Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today I've discovered that dial rules not always executed correctly. In the example above request from 212.42.69.214 should not be blocked because 212.42.69.214 is in fact MYADDR! I'm using ppp from -current cvsup'ed and built today (-auto -alias). And what is really strange that this not always the case (in most cases it not blocking this packets and dials just fine). Following is the log: TCP/IP: DIAL UDP: 192.168.1.1:2191 ---> 193.193.193.100:53 - BLOCKED TCP/IP: DIAL UDP: 192.168.1.1:2191 ---> 193.193.193.100:53 - BLOCKED TCP/IP: DIAL UDP: 212.42.69.214:3604 ---> 212.42.68.2:53 - BLOCKED ppp ON vega> q Connection closed sh-2.03# ifconfig -a ed1: flags=8843 mtu 1500 inet 192.168.1.50 netmask 0xffffff00 broadcast 192.168.1.255 ether 00:40:05:3b:1c:23 tun0: flags=8051 mtu 1500 inet 212.42.69.214 --> 212.42.68.4 netmask 0xffffffff lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 Relevant pieces from ppp.conf: disable sroutes set filter dial 0 deny 0/0 0/0 tcp syn set filter dial 1 deny 0/0 0/0 tcp finrst set filter dial 2 permit MYADDR 0/0 udp dst eq 3130 set filter dial 3 permit MYADDR 0/0 udp dst eq 53 set filter dial 4 permit MYADDR 0/0 tcp dst eq 25 set filter dial 5 permit 0/0 0/0 udp dst eq 2074 Sincerely, Maxim -- "We believe in the Power and the Might!" (Manowar, 1996) ---------------------------------------- Maxim V. Sobolev, Financial Analyst, Vega International Capital Phone: +380-(44)-246-6396 Fax: +380-(44)-220-8715 E-mail: sobomax@altavista.net ICQ: #42290709 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 10:33:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E003614D70 for ; Wed, 28 Jul 1999 10:33:27 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id TAA48306 for current@freebsd.org; Wed, 28 Jul 1999 19:32:02 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199907281732.TAA48306@zibbi.mikom.csir.co.za> Subject: a little newbus problem To: current@freebsd.org Date: Wed, 28 Jul 1999 19:32:02 +0200 (SAT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been trying to get my ar(4) and sr(4) drivers going again on -current, but it seems that the newbus code doesn't like my little trick that worked for so long. :-( Basically the drivers are called ar0 in the kernel config file, but in the isa_driver struct I call them arc and not ar, because the chip that is used actually have 2 ports and I register them seperately as ar0 and ar1 during the attach phase. From what I can see now, it looks like the newbus code doesn't even call the arprobe routine. I have even added a printf right in the start of it, but it never prints anything. Just as a test I changed my kernel config file and files.i386 from ar to arc and then it works. So what should I do? Can the newbus code be fixed to work in this case too or should I newbusify the drivers and will that help? Won't that create a clash because of the isa compatabilty shim? John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 10:56:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 151CD14D51 for ; Wed, 28 Jul 1999 10:56:19 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA01514; Thu, 29 Jul 1999 02:55:57 +0900 (JST) Message-ID: <379F4390.950D08FA@newsguy.com> Date: Thu, 29 Jul 1999 02:53:20 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Garrett Wollman Cc: Brian Dean , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance References: <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > > During recent installs using the 7/26 snap, I noticed that the > > transfer rate for the "ports" distribution was about twice as fast as > > SNAPs from the beginning of the month. > > > I was wondering what to attribute this better performance to. Could > > this be due to the new network driver / newbus integration? > > Jordan stopped including CVS directories in the /usr/ports tarball. I don't think a transfer rate can be affected by that, though the total transfer time certainly would. Anyway... Jordan did it? Thanks God! -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 11:12:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id B4F2114C3F for ; Wed, 28 Jul 1999 11:12:20 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA86500; Wed, 28 Jul 1999 14:11:53 -0400 (EDT) Message-Id: <199907281811.OAA86500@cs.rpi.edu> To: "Daniel C. Sobral" Cc: Garrett Wollman , Brian Dean , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: sysinstall network performance In-Reply-To: Message from "Daniel C. Sobral" of "Thu, 29 Jul 1999 02:53:20 +0900." <379F4390.950D08FA@newsguy.com> Date: Wed, 28 Jul 1999 14:11:52 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Jordan stopped including CVS directories in the /usr/ports tarball. > > I don't think a transfer rate can be affected by that, though the > total transfer time certainly would. > > Anyway... Jordan did it? Thanks God! Ports is 20,000 some odd different files, the transfer rate is limited by disk I/O in creating those thousands of files. By eliminating some of the additional tiny files it creats I could certainly see an increase in throughput. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 12:15: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 9C13514CF3 for ; Wed, 28 Jul 1999 12:14:57 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA06608; Wed, 28 Jul 1999 12:14:50 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Brian Dean Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance In-reply-to: Your message of "Wed, 28 Jul 1999 11:24:34 EDT." <199907281524.LAA61875@dean.pc.sas.com> Date: Wed, 28 Jul 1999 12:14:50 -0700 Message-ID: <6604.933189290@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was wondering what to attribute this better performance to. Could > this be due to the new network driver / newbus integration? The CVS metadata was removed, reducing the inode count per port significantly. This results in faster extraction time and hence "faster" downloads, assuming that extraction time is the bottleneck (which it is for all but the 28K and below downloaders). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 12:27:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A2C1514C10 for ; Wed, 28 Jul 1999 12:27:33 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA64855; Wed, 28 Jul 1999 21:24:18 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: "Jordan K. Hubbard" Cc: Brian Dean , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance In-reply-to: Your message of "Wed, 28 Jul 1999 12:14:50 PDT." <6604.933189290@zippy.cdrom.com> Date: Wed, 28 Jul 1999 21:24:17 +0200 Message-ID: <64853.933189857@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <6604.933189290@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> I was wondering what to attribute this better performance to. Could >> this be due to the new network driver / newbus integration? > >The CVS metadata was removed, reducing the inode count per port significantly. >This results in faster extraction time and hence "faster" downloads, assuming >that extraction time is the bottleneck (which it is for all but the 28K and >below downloaders). We should look into distributing ports as a Makefile and a tar-ball with the rest of the files. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 12:41:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 5AAFE15025 for ; Wed, 28 Jul 1999 12:41:46 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id PAA14954; Wed, 28 Jul 1999 15:41:30 -0400 (EDT) Date: Wed, 28 Jul 1999 15:41:29 -0400 (EDT) From: "Matthew N. Dodd" To: John Hay Cc: current@FreeBSD.ORG Subject: Re: a little newbus problem In-Reply-To: <199907281732.TAA48306@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you by any chance kldload'ing the module for testing? If so you should have: DEVMETHOD(bus_driver_added, bus_generic_driver_added), For your 'arc' device_method_t method declaration. I got bit by this one too. On Wed, 28 Jul 1999, John Hay wrote: > I have been trying to get my ar(4) and sr(4) drivers going again on -current, > but it seems that the newbus code doesn't like my little trick that worked > for so long. :-( > > Basically the drivers are called ar0 in the kernel config file, but in > the isa_driver struct I call them arc and not ar, because the chip that > is used actually have 2 ports and I register them seperately as ar0 and > ar1 during the attach phase. > > >From what I can see now, it looks like the newbus code doesn't even > call the arprobe routine. I have even added a printf right in the start > of it, but it never prints anything. Just as a test I changed my kernel > config file and files.i386 from ar to arc and then it works. > > So what should I do? Can the newbus code be fixed to work in this case > too or should I newbusify the drivers and will that help? Won't that > create a clash because of the isa compatabilty shim? > > John > -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 13:11:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id DE8A214EE2 for ; Wed, 28 Jul 1999 13:11:20 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id WAA50899; Wed, 28 Jul 1999 22:11:08 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199907282011.WAA50899@zibbi.mikom.csir.co.za> Subject: Re: a little newbus problem In-Reply-To: from "Matthew N. Dodd" at "Jul 28, 1999 03:41:29 pm" To: winter@jurai.net (Matthew N. Dodd) Date: Wed, 28 Jul 1999 22:11:07 +0200 (SAT) Cc: jhay@mikom.csir.co.za (John Hay), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope, it is an ISA driver and I wasn't that brave. :-) It is part of standard FreeBSD and I just compiled it into the kernel with a kernel config file. > Are you by any chance kldload'ing the module for testing? > > If so you should have: > > DEVMETHOD(bus_driver_added, bus_generic_driver_added), > > For your 'arc' device_method_t method declaration. > > I got bit by this one too. > > On Wed, 28 Jul 1999, John Hay wrote: > > I have been trying to get my ar(4) and sr(4) drivers going again on -current, > > but it seems that the newbus code doesn't like my little trick that worked > > for so long. :-( > > > > Basically the drivers are called ar0 in the kernel config file, but in > > the isa_driver struct I call them arc and not ar, because the chip that > > is used actually have 2 ports and I register them seperately as ar0 and > > ar1 during the attach phase. > > > > >From what I can see now, it looks like the newbus code doesn't even > > call the arprobe routine. I have even added a printf right in the start > > of it, but it never prints anything. Just as a test I changed my kernel > > config file and files.i386 from ar to arc and then it works. > > > > So what should I do? Can the newbus code be fixed to work in this case > > too or should I newbusify the drivers and will that help? Won't that > > create a clash because of the isa compatabilty shim? > > John -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 14: 6: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id C0B5B154F9 for ; Wed, 28 Jul 1999 14:05:59 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id VAA71250; Wed, 28 Jul 1999 21:24:18 +0100 (BST) (envelope-from nik) Date: Wed, 28 Jul 1999 21:24:17 +0100 From: Nik Clayton To: "John W. DeBoskey" Cc: freebsd-current@freebsd.org Subject: Re: make release doc failure Message-ID: <19990728212417.A70422@catkin.nothing-going-on.org> References: <199907281416.KAA98204@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199907281416.KAA98204@bb01f39.unx.sas.com>; from John W. DeBoskey on Wed, Jul 28, 1999 at 10:16:16AM -0400 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jul 28, 1999 at 10:16:16AM -0400, John W. DeBoskey wrote: > ===> en/handbook > /usr/local/bin/jade -V html-manifest -ioutput.html -c /usr/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/docbook/catalog -c /usr/local/share/sgml/jade/catalog -d /usr/doc/share/sgml/freebsd.dsl -t sgml handbook.sgml > /usr/local/bin/jade:serialcomms/chapter.sgml:2016:2:E: general entity "man.boot.8" not defined and no default entity > /usr/local/bin/jade:serialcomms/chapter.sgml:2016:19:E: general entity "man.loader.8" not defined and no default entity > /usr/local/bin/jade:serialcomms/chapter.sgml:2680:12:E: general entity "man.loader.conf.5" not defined and no default entity > *** Error code 1 My SNAFU, sorry 'bout that. Now fixed. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 14:18:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 99DEA154F9 for ; Wed, 28 Jul 1999 14:18:29 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40336>; Thu, 29 Jul 1999 06:59:30 +1000 Date: Thu, 29 Jul 1999 07:18:19 +1000 From: Peter Jeremy Subject: Make world broken To: current@FreeBSD.ORG Message-Id: <99Jul29.065930est.40336@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cvs-cur 5518 breaks building libgcc with: c++ -c -I/usr/obj/3.0/cvs/src/tmp/usr/include/g++ -O -pipe -I/3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gc c -I. -fexceptions -DIN_GCC -I/usr/obj/3.0/cvs/src/tmp/usr/include -I/3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_new -o _op_new.o /3.0/cvs/s rc/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc In file included from /usr/obj/3.0/cvs/src/tmp/usr/include/stddef.h:39, from /usr/obj/3.0/cvs/src/tmp/usr/include/g++/new:8, from /3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/3.0/cvs/src/tmp/usr/include/machine/ansi.h:103: syntax error before `__attribute__' /usr/obj/3.0/cvs/src/tmp/usr/include/machine/ansi.h:104: syntax error before `__attribute__' In file included from /usr/obj/3.0/cvs/src/tmp/usr/include/g++/new:9, from /3.0/cvs/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/3.0/cvs/src/tmp/usr/include/g++/exception:9: syntax error before string constant *** Error code 1 Stop. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 14:29:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 10ED315519 for ; Wed, 28 Jul 1999 14:29:41 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA15255 for current@freebsd.org; Wed, 28 Jul 1999 17:31:53 -0400 From: Bill Paul Message-Id: <199907282131.RAA15255@skynet.ctr.columbia.edu> Subject: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: current@freebsd.org Date: Wed, 28 Jul 1999 17:31:52 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1730 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Somehow I knew this was going to happen. I just got done upgrading one of my Indigo2s to IRIX 6.5.4, with am-utils 6.0 for NFS automounting. IRIX 6.5.4 supports NFS v3 and TCP. I tried cd'ing to a directory served on a FreeBSD 3.2-RELEASE system which happens to have the build tree for the Alteon Tigon firmware (that's where I compiled the last firmware image for the Tigon driver). I did a 'du' and after a short while, it exploded with the following messages: mbuf siz=33524 panic: Bad nfs svc reply Inspecting a crash dump showed that the mbuf chain was trashed. The same thing happens with a 4.0-current snapshot from the 15th: this time I just manually mounted /usr from the FreeBSD server under /mnt on the SGI and did cd /mnt; du. Pow: died right away. The FreeBSD 3.2-RELEASE host has a 3Com 3c509 card. The 4.0-CURRENT host has a 3Com 3c900-COMBO PCI card. Each uses different drivers and networking works fine otherwise, so I'm pretty sure the problem is in NFS somewhere and not in the drivers. This doesn't happen when using UDP. Given that I can reproduce this on demand, I should be able to debug it eventually, but hints in the right direction would be useful. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 15:22:44 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 31C0414D97 for ; Wed, 28 Jul 1999 15:22:41 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.111]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA4242 for ; Thu, 29 Jul 1999 00:22:26 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA13051 for current@freebsd.org; Thu, 29 Jul 1999 00:22:41 +0200 (CEST) (envelope-from asmodai) Date: Thu, 29 Jul 1999 00:22:40 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: make.conf on CURRENT question Message-ID: <19990729002240.C12907@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just a couple of questions: compat22=yes in /etc/make.conf accomplishes a.out support which we need for netscape support. Correct? What does compat3x do however? Provide ELF compatibility libraries for programs written for 3.x? Also. Suppose I have an ELF CURRENT box that never ran a.out. If I want a.out support from a make world I would need to uncomment compat22=yes in /etc/make.conf, correct in assuming this? Thanks for the time taken to answer this, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 15:58: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4985A14C0A for ; Wed, 28 Jul 1999 15:58:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA64091; Wed, 28 Jul 1999 15:57:51 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 15:57:51 -0700 (PDT) From: Matthew Dillon Message-Id: <199907282257.PAA64091@apollo.backplane.com> To: Bill Paul Cc: current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907282131.RAA15255@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :IRIX 6.5.4 supports NFS v3 and TCP. I tried cd'ing to a directory :served on a FreeBSD 3.2-RELEASE system which happens to have the build :tree for the Alteon Tigon firmware (that's where I compiled the last :firmware image for the Tigon driver). I did a 'du' and after a short :while, it exploded with the following messages: : :mbuf siz=33524 :panic: Bad nfs svc reply : :Inspecting a crash dump showed that the mbuf chain was trashed. The :same thing happens with a 4.0-current snapshot from the 15th: this time :I just manually mounted /usr from the FreeBSD server under /mnt on :the SGI and did cd /mnt; du. Pow: died right away. : :The FreeBSD 3.2-RELEASE host has a 3Com 3c509 card. The 4.0-CURRENT :host has a 3Com 3c900-COMBO PCI card. Each uses different drivers and :networking works fine otherwise, so I'm pretty sure the problem is in :NFS somewhere and not in the drivers. : :This doesn't happen when using UDP. Given that I can reproduce this :on demand, I should be able to debug it eventually, but hints in the :right direction would be useful. : :-Bill :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Ok, so if I understand this correctly you have a FreeBSD server and an IRIX client. UDP mounts work, TCP mounts do not. You are using the AMD automounting software running on the ... client I presume? It is the server that is panicing. First of all, if these are production machines stick with UDP so's you don't tear your hair out. Also double check that the bug still exists with the absolute latest CURRENT if you can. Also please run this (on the FreeBSD server running CURRENT). It will tell me whether NFS is being forced to realign packet data coming from your ethernet controller. (In the example below, my NFS server has to realign the data). # sysctl -a | fgrep nfs vfs.nfs.realign_test: 1583064 vfs.nfs.realign_count: 1583064 We fixed a serious data corruption bug with NFSv3 over TCP that could result in panics. This fix was made on May 2nd to current and MFC'd to stable on May 8th. This fix made it into 3.2. There are probably still bugs laying around. Sigh. I'll try running amd and doing a du on a FreeBSD<->FreeBSD NFSv3 mount. However, I only give myself a 20% chance of reproducing the problem. The SGI is probably tickling something that FreeBSD doesn't or I would have caught the problem earlier. Your bug really sounds like a packet realignment bug, but I was sure I fixed those! So there may be a new one. -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 Wed Jul 28 16: 4:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id F3210154F4 for ; Wed, 28 Jul 1999 16:04:29 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA94454; Wed, 28 Jul 1999 19:04:05 -0400 (EDT) Message-Id: <199907282304.TAA94454@cs.rpi.edu> To: Matthew Dillon Cc: Bill Paul , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm In-Reply-To: Message from Matthew Dillon of "Wed, 28 Jul 1999 15:57:51 PDT." <199907282257.PAA64091@apollo.backplane.com> Date: Wed, 28 Jul 1999 19:04:05 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is yet another problem that we have run into here. If you check the digest for -hackers it was reported awhile ago (mike smith even cc-ed it to security since it may have been a kernel stack overflow) . Anyway, the problem is that IRIX defaults to 32K packets on TCP NFSv3 mounts, and 16K on UDP NFSv3 mounts. I recommend using UDP and setting rsize=8192, wsize=8192 in your amd maps (as we do now, no problems at all). -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 16:10:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7FF081556A for ; Wed, 28 Jul 1999 16:10:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA64183; Wed, 28 Jul 1999 16:09:06 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 16:09:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199907282309.QAA64183@apollo.backplane.com> To: "David E. Cross" Cc: Bill Paul , current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907282304.TAA94454@cs.rpi.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This is yet another problem that we have run into here. If you check the :digest for -hackers it was reported awhile ago (mike smith even cc-ed it :to security since it may have been a kernel stack overflow) . Anyway, the :problem is that IRIX defaults to 32K packets on TCP NFSv3 mounts, and :16K on UDP NFSv3 mounts. I recommend using UDP and setting rsize=8192, :wsize=8192 in your amd maps (as we do now, no problems at all). : :-- :David Cross | email: crossd@cs.rpi.edu :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Ah ha! Yes, 32K packets will certainly screw up NFS under FreeBSD. We need to fix that panic to have it simply drop the packet, I guess. -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 Wed Jul 28 16:33:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 2B78514C3C for ; Wed, 28 Jul 1999 16:33:40 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA15438; Wed, 28 Jul 1999 19:35:44 -0400 From: Bill Paul Message-Id: <199907282335.TAA15438@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 28 Jul 1999 19:35:43 -0400 (EDT) Cc: current@FreeBSD.ORG In-Reply-To: <199907282257.PAA64091@apollo.backplane.com> from "Matthew Dillon" at Jul 28, 99 03:57:51 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2674 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > > Ok, so if I understand this correctly you have a FreeBSD server and > an IRIX client. UDP mounts work, TCP mounts do not. You are using > the AMD automounting software running on the ... client I presume? > It is the server that is panicing. Yes. But it's nothing to do with AMD. I can do it manually: irix# mount -o vers=3,proto=tcp freebsd:/usr /mnt irix# cd /mnt; du FreeBSD box explodes. > First of all, if these are production machines stick with UDP so's > you don't tear your hair out. Also double check that the bug still > exists with the absolute latest CURRENT if you can. I'd love to except *somebody* hasn't gotten arround to fixing current.freebsd.org yet. *Nudges jkh* And I'm not going to stick with UDP mounts because that's hiding the problem, not fixing it. You're just going to get more grief from the next poor fool who runs afoul of this problem. > Also please run this (on the FreeBSD server running CURRENT). It > will tell me whether NFS is being forced to realign packet data > coming from your ethernet controller. (In the example below, my > NFS server has to realign the data). > > # sysctl -a | fgrep nfs > vfs.nfs.realign_test: 1583064 > vfs.nfs.realign_count: 1583064 In the case of the 4.0 box, it explodes almost immediately: there's no chance to actually obtain this data there. I added some printfs to the 3.2 box briefly and it didn't look like the realign code was being triggered. > We fixed a serious data corruption bug with NFSv3 over TCP that > could result in panics. This fix was made on May 2nd to current > and MFC'd to stable on May 8th. This fix made it into 3.2. FreeBSD mcmillan.ctr.columbia.edu 4.0-19990715-CURRENT FreeBSD 4.0-19990715-CURRENT #2: Tue Jul 20 17:07:35 EDT 1999 operator@mcmillan.ctr.columbia.edu:/usr/src/sys/compile/TEST i386 Should be in there. I don't think that's it. Note that the 'mbuf siz' value that gets printed is the exactly the same every time. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 16:40:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id D089C1508D for ; Wed, 28 Jul 1999 16:40:04 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA15454; Wed, 28 Jul 1999 19:40:20 -0400 From: Bill Paul Message-Id: <199907282340.TAA15454@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 28 Jul 1999 19:40:18 -0400 (EDT) Cc: crossd@cs.rpi.edu, current@FreeBSD.ORG In-Reply-To: <199907282309.QAA64183@apollo.backplane.com> from "Matthew Dillon" at Jul 28, 99 04:09:06 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1595 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :This is yet another problem that we have run into here. If you check the > :digest for -hackers it was reported awhile ago (mike smith even cc-ed it > :to security since it may have been a kernel stack overflow) . Anyway, the > :problem is that IRIX defaults to 32K packets on TCP NFSv3 mounts, and > :16K on UDP NFSv3 mounts. I recommend using UDP and setting rsize=8192, > :wsize=8192 in your amd maps (as we do now, no problems at all). > : > :-- > :David Cross | email: crossd@cs.rpi.edu > :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd > > Ah ha! Yes, 32K packets will certainly screw up NFS under FreeBSD. Uh.... could you elaborate a little? No, strike that: could you elaborate a *lot*. A whole lot. > We need to fix that panic to have it simply drop the packet, I guess. No, we need to fix the code so it handles 32K "packets" (datagrams) correctly. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 16:58:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4EBF11551D for ; Wed, 28 Jul 1999 16:58:31 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA64519; Wed, 28 Jul 1999 16:58:19 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 16:58:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199907282358.QAA64519@apollo.backplane.com> To: Bill Paul Cc: crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907282340.TAA15454@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Ah ha! Yes, 32K packets will certainly screw up NFS under FreeBSD. : :Uh.... could you elaborate a little? No, strike that: could you elaborate :a *lot*. A whole lot. Sure. There is a constant called NFS_MAXDATA defined in ..mmm.. nfs/nfsproto.h. Set to 32768 for TCP connections, 16384 for UDP connections. The code is a mess though, so usually just the higher limit is used. The fsinfo rpc returns this maximum to the client. The client is supposed to limit NFS packets to the specified size. :> We need to fix that panic to have it simply drop the packet, I guess. : :No, we need to fix the code so it handles 32K "packets" (datagrams) :correctly. : :-Bill But there is a bug somewhere. Nobody has been able to find it yet. There are cases where the server will attempt to return a packet that is larger then 32K. It's probably due to some NFS header records that aren't being accounted for. But where, I don't know. I'm guessing in the read or write code somewhere. The server panics if an rpc reply winds up being larger then NFS_MAXDATA. That is, when a packet generated by the server in response to a client request winds up being larger then NFS_MAXDATA. There could also be some confusion in the spec. I'm not sure whether NFS_MAXDATA refers to the maximum NFS message size inclusive of NFS headers, or just the data portion of the NFS message. It might help to get a backtrace if you have a kernel set to drop into DDB on a panic. This would be the 'trace' command from the DDB prompt. I could try to locate where the limit is being smashed. -Matt Matthew Dillon :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu :Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research :Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City :============================================================================= : "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" :============================================================================= : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 17:25:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.westbend.net (ns1.westbend.net [209.224.254.131]) by hub.freebsd.org (Postfix) with ESMTP id C402214EEF for ; Wed, 28 Jul 1999 17:25:06 -0700 (PDT) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [209.224.254.141]) by mail.westbend.net (8.9.3/8.9.3) with SMTP id TAA51109; Wed, 28 Jul 1999 19:24:27 -0500 (CDT) (envelope-from hetzels@westbend.net) Message-ID: <00a201bed958$bee6d1a0$8dfee0d1@westbend.net> From: "Scot W. Hetzel" To: "Jeroen Ruigrok/Asmodai" Cc: References: <19990729002240.C12907@daemon.ninth-circle.org> Subject: Re: make.conf on CURRENT question Date: Wed, 28 Jul 1999 19:24:38 -0500 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Jeroen Ruigrok/Asmodai > compat22=yes in /etc/make.conf accomplishes a.out support which we need > for netscape support. Correct? > You will also need a.out libraries from XFree86 in order to get Netscape working. > What does compat3x do however? Provide ELF compatibility libraries for > programs written for 3.x? > Yes > Also. Suppose I have an ELF CURRENT box that never ran a.out. > If I want a.out support from a make world I would need to uncomment > compat22=yes in /etc/make.conf, correct in assuming this? > You'll also want to use: make world -DWANT_AOUT=YES to have the a.out libraries built. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 18:14:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id 322F815308 for ; Wed, 28 Jul 1999 18:14:16 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id SAA18027 for ; Wed, 28 Jul 1999 18:12:08 -0700 (PDT) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.9.3/8.9.3) id SAA04047 for freebsd-current@freebsd.org; Wed, 28 Jul 1999 18:12:17 -0700 (PDT) (envelope-from scottm) Date: Wed, 28 Jul 1999 18:12:17 -0700 (PDT) From: Scott Michel Message-Id: <199907290112.SAA04047@mordred.cs.ucla.edu> To: freebsd-current@freebsd.org Subject: Extra characters? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At line 71 in i386/isa/clock.c, there is the following: #include #include XXX #ifdef APIC_IO #include #endif I'd say, and this is only a SWAG mind you, that the 'XXX' is extraneous. Right? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 18:20:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id A889A15308 for ; Wed, 28 Jul 1999 18:20:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id SAA01866; Wed, 28 Jul 1999 18:12:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907290112.SAA01866@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Scott Michel Cc: freebsd-current@freebsd.org Subject: Re: Extra characters? In-reply-to: Your message of "Wed, 28 Jul 1999 18:12:17 PDT." <199907290112.SAA04047@mordred.cs.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jul 1999 18:12:14 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At line 71 in i386/isa/clock.c, there is the following: > > #include > #include > XXX > #ifdef APIC_IO > #include > #endif > > > I'd say, and this is only a SWAG mind you, that the 'XXX' is > extraneous. Right? Ack. I have no idea how that snuck through; yes, it's extraneous. I'll fix it in a moment. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 18:25:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 3608315308 for ; Wed, 28 Jul 1999 18:23:28 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id VAA00220; Wed, 28 Jul 1999 21:23:00 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Wed, 28 Jul 1999 21:22:59 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Scott Michel Cc: freebsd-current@FreeBSD.org Subject: Re: Extra characters?y In-Reply-To: <199907290112.SAA04047@mordred.cs.ucla.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Scott Michel wrote: > At line 71 in i386/isa/clock.c, there is the following: > > #include > #include > XXX > #ifdef APIC_IO > #include > #endif > > > I'd say, and this is only a SWAG mind you, that the 'XXX' is > extraneous. Right? It just appeared in version 1.141 (msmith) when APM was completely removed from clock.c. I'm guessing it was an accident, because it probably broke your build, didn't it? I committed a fix. > > > -scooter > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 18:51: 9 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with SMTP id BDAA414ED4 for ; Wed, 28 Jul 1999 18:51:01 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Thu, 29 Jul 1999 11:29:39 +1000 Date: Thu, 29 Jul 1999 11:48:31 +1000 From: Peter Jeremy Subject: Re: make.conf on CURRENT question To: current@FreeBSD.ORG Message-Id: <99Jul29.112939est.40351@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Scot W. Hetzel" wrote: >You'll also want to use: > >make world -DWANT_AOUT=YES > >to have the a.out libraries built. You'll also need the a.out X11 libraries, and last time I tried, they built OK, but wouldn't work. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 19:18:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id B9E6B14F5D for ; Wed, 28 Jul 1999 19:18:50 -0700 (PDT) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA05892 for ; Wed, 28 Jul 1999 22:18:08 -0400 (EDT) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA06400 for ; Wed, 28 Jul 1999 22:18:07 -0400 (EDT) Received: from localhost by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA06396 for ; Wed, 28 Jul 1999 22:18:07 -0400 (EDT) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 28 Jul 1999 22:18:06 -0400 (EDT) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: kernel compile error. Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-851401618-933214686=:5873" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk 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. ---559023410-851401618-933214686=:5873 Content-Type: TEXT/PLAIN; charset=US-ASCII I just CVSupped at 10:10 eastern time (US) and now I have this error: cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../kern/subr_autoconf.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../kern/subr_bus.c ../../kern/subr_bus.c: In function `bus_print_child_header': ../../kern/subr_bus.c:1870: parse error before `}' *** Error code 1 here is my kernel conf file (as an attachment)... ---559023410-851401618-933214686=:5873 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=MYKERNEL Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=MYKERNEL Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv biByZWFkIHRoZSBoYW5kYm9vayBwYXJ0IFN5c3RlbSBBZG1pbmlzdHJhdGlv biAtPiANCiMgQ29uZmlndXJpbmcgdGhlIEZyZWVCU0QgS2VybmVsIC0+IFRo ZSBDb25maWd1cmF0aW9uIEZpbGUuIA0KIyBUaGUgaGFuZGJvb2sgaXMgYXZh aWxhYmxlIGluIC91c3Ivc2hhcmUvZG9jL2hhbmRib29rIG9yIG9ubGluZSBh cw0KIyBsYXRlc3QgdmVyc2lvbiBmcm9tIHRoZSBGcmVlQlNEIFdvcmxkIFdp ZGUgV2ViIHNlcnZlciANCiMgPFVSTDpodHRwOi8vd3d3LkZyZWVCU0QuT1JH Lz4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0IG9mIG9wdGlvbnMgYW5kIG1v cmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9mIHRoZSANCiMgZGV2aWNlIGxp bmVzIGlzIHByZXNlbnQgaW4gdGhlIC4vTElOVCBjb25maWd1cmF0aW9uIGZp bGUuIElmIHlvdSBhcmUgDQojIGluIGRvdWJ0IGFzIHRvIHRoZSBwdXJwb3Nl IG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUsIGNoZWNrIGZpcnN0IGluIExJTlQu DQojDQojCSRJZDogR0VORVJJQyx2IDEuMTcyIDE5OTkvMDUvMjEgMDQ6Mzc6 MzUgd3BhdWwgRXhwICQNCg0KbWFjaGluZQkJaTM4Ng0KY3B1CQlJNjg2X0NQ VQ0KaWRlbnQJCSJNWUtFUk5FTCINCm1heHVzZXJzCTY0DQoNCiMgbWFrZW9w dGlvbnMJQ09QVEZMQUdTPSItTzIgLXBpcGUiDQoNCiNtYWtlb3B0aW9ucwlE RUJVRz0tZwkJI0J1aWxkIGtlcm5lbCB3aXRoIGdkYigxKSBkZWJ1ZyBzeW1i b2xzDQoNCm9wdGlvbnMJCUlORVQJCQkjSW50ZXJORVR3b3JraW5nDQpvcHRp b25zCQlGRlMJCQkjQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25z CQlGRlNfUk9PVAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2UgW2tlZXAg dGhpcyFdDQpvcHRpb25zCQlQUk9DRlMJCQkjUHJvY2VzcyBmaWxlc3lzdGVt DQpvcHRpb25zCQlDT01QQVRfNDMJCSNDb21wYXRpYmxlIHdpdGggQlNEIDQu MyBbS0VFUCBUSElTIV0NCm9wdGlvbnMJCVVDT05TT0xFCQkjQWxsb3cgdXNl cnMgdG8gZ3JhYiB0aGUgY29uc29sZQ0Kb3B0aW9ucwkJVVNFUl9MRFQNCg0K IyBUbyBtYWtlIGFuIFNNUCBrZXJuZWwsIHRoZSBuZXh0IHR3byBhcmUgbmVl ZGVkDQojb3B0aW9ucwlTTVAJCQkjIFN5bW1ldHJpYyBNdWx0aVByb2Nlc3Nv ciBLZXJuZWwNCiNvcHRpb25zCUFQSUNfSU8JCQkjIFN5bW1ldHJpYyAoQVBJ QykgSS9PDQojIE9wdGlvbmFsbHkgdGhlc2UgbWF5IG5lZWQgdHdlYWtlZCwg KGRlZmF1bHRzIHNob3duKToNCiNvcHRpb25zCU5DUFU9MgkJCSMgbnVtYmVy IG9mIENQVXMNCiNvcHRpb25zCU5CVVM9NAkJCSMgbnVtYmVyIG9mIGJ1c3Nl cw0KI29wdGlvbnMJTkFQSUM9MQkJCSMgbnVtYmVyIG9mIElPIEFQSUNzDQoj b3B0aW9ucwlOSU5UUj0yNAkJIyBudW1iZXIgb2YgSU5Ucw0KDQpjb250cm9s bGVyCWlzYTANCmNvbnRyb2xsZXIJcG5wMAkJCSMgUG5QIHN1cHBvcnQgZm9y IElTQQ0KY29udHJvbGxlcglwY2kwDQoNCmNvbnRyb2xsZXIJZmRjMAlhdCBp c2E/IHBvcnQgSU9fRkQxIGlycSA2IGRycSAyDQpkaXNrCQlmZDAJYXQgZmRj MCBkcml2ZSAwDQoNCmNvbnRyb2xsZXIgYXRhMA0KZGV2aWNlIAkJYXRhZGlz azANCmRldmljZSAJCWF0YXBpY2QwDQoNCiMgQSBzaW5nbGUgZW50cnkgZm9y IGFueSBvZiB0aGVzZSBjb250cm9sbGVycyAobmNyLCBhaGIsIGFoYykgaXMN CiMgc3VmZmljaWVudCBmb3IgYW55IG51bWJlciBvZiBpbnN0YWxsZWQgZGV2 aWNlcy4NCg0KY29udHJvbGxlcglzY2J1czANCg0KZGV2aWNlCQlkYTAJI09u bHkgbmVlZCBvbmUgb2YgdGhlc2UsIHRoZSBjb2RlIGR5bmFtaWNhbGx5IGdy b3dzDQoNCiMgYXRrYmRjMCBjb250cm9scyBib3RoIHRoZSBrZXlib2FyZCBh bmQgdGhlIFBTLzIgbW91c2UNCmNvbnRyb2xsZXIJYXRrYmRjMAlhdCBpc2E/ IHBvcnQgSU9fS0JEDQpkZXZpY2UJCWF0a2JkMAlhdCBhdGtiZGM/IGlycSAx DQpkZXZpY2UJCXBzbTAJYXQgYXRrYmRjPyBpcnEgMTINCg0KZGV2aWNlCQl2 Z2EwCWF0IGlzYT8gcG9ydCA/IGNvbmZsaWN0cw0KDQojIHNwbGFzaCBzY3Jl ZW4vc2NyZWVuIHNhdmVyDQpwc2V1ZG8tZGV2aWNlCXNwbGFzaA0KDQojZGlz YWJsZSBjdHJsLWFsdC1kZWwNCm9wdGlvbnMgIFNDX0RJU0FCTEVfUkVCT09U DQoNCiMgc3lzY29ucyBpcyB0aGUgZGVmYXVsdCBjb25zb2xlIGRyaXZlciwg cmVzZW1ibGluZyBhbiBTQ08gY29uc29sZQ0KZGV2aWNlCQlzYzAJYXQgaXNh Pw0KDQojIEVuYWJsZSB0aGlzIGFuZCBQQ1ZUX0ZSRUVCU0QgZm9yIHBjdnQg dnQyMjAgY29tcGF0aWJsZSBjb25zb2xlIGRyaXZlcg0KI2RldmljZQkJdnQw CWF0IGlzYT8NCiNvcHRpb25zCQlYU0VSVkVSCQkJIyBzdXBwb3J0IGZvciBY IHNlcnZlcg0KI29wdGlvbnMJCUZBVF9DVVJTT1IJCSMgc3RhcnQgd2l0aCBi bG9jayBjdXJzb3INCiMgSWYgeW91IGhhdmUgYSBUaGlua1BBRCwgdW5jb21t ZW50IHRoaXMgYWxvbmcgd2l0aCB0aGUgcmVzdCBvZiB0aGUgUENWVCBsaW5l cw0KI29wdGlvbnMJCVBDVlRfU0NBTlNFVD0yCQkjIElCTSBrZXlib2FyZHMg YXJlIG5vbi1zdGQNCg0KZGV2aWNlCQlucHgwCWF0IG5leHVzPyBwb3J0IElP X05QWCBpcnEgMTMNCg0KIw0KIyBMYXB0b3Agc3VwcG9ydCAoc2VlIExJTlQg Zm9yIG1vcmUgb3B0aW9ucykNCiMNCmRldmljZQkJYXBtMCAgICBhdCBuZXh1 cz8gZGlzYWJsZSBmbGFncyAweDMxICMgQWR2YW5jZWQgUG93ZXIgTWFuYWdl bWVudA0KDQojIFBDQ0FSRCAoUENNQ0lBKSBzdXBwb3J0DQojY29udHJvbGxl cgljYXJkMA0KI2RldmljZQkJcGNpYzAJYXQgY2FyZD8NCiNkZXZpY2UJCXBj aWMxCWF0IGNhcmQ/DQoNCmRldmljZQkJc2lvMAlhdCBpc2E/IHBvcnQgSU9f Q09NMSBmbGFncyAweDEwIGlycSA0DQpkZXZpY2UJCXNpbzEJYXQgaXNhPyBw b3J0IElPX0NPTTIgaXJxIDMNCg0KIyBQYXJhbGxlbCBwb3J0DQpkZXZpY2UJ CXBwYzAJYXQgaXNhPyBwb3J0PyBmbGFncyAweDQwIGlycSA3DQpjb250cm9s bGVyCXBwYnVzMA0KZGV2aWNlCQlscHQwCWF0IHBwYnVzPw0KZGV2aWNlCQlw bGlwMAlhdCBwcGJ1cz8NCmRldmljZQkJcHBpMAlhdCBwcGJ1cz8NCmNvbnRy b2xsZXIJdnBvMAlhdCBwcGJ1cz8NCg0KIw0KIyBUaGUgZm9sbG93aW5nIEV0 aGVybmV0IE5JQ3MgYXJlIGFsbCBQQ0kgZGV2aWNlcy4NCiMNCmRldmljZSBk ZTAJCSMgREVDL0ludGVsIERDMjF4NHggKGBgVHVsaXAnJykNCg0KIyBPcmRl ciBpcyBpbXBvcnRhbnQgaGVyZSBkdWUgdG8gaW50cnVzaXZlIHByb2Jlcywg ZG8gKm5vdCogYWxwaGFiZXRpemUNCiMgdGhpcyBsaXN0IG9mIG5ldHdvcmsg aW50ZXJmYWNlcyB1bnRpbCB0aGUgcHJvYmVzIGhhdmUgYmVlbiBmaXhlZC4N CiMgUmlnaHQgbm93IGl0IGFwcGVhcnMgdGhhdCB0aGUgaWUwIG11c3QgYmUg cHJvYmVkIGJlZm9yZSBlcDAuIFNlZQ0KIyByZXZpc2lvbiAxLjIwIG9mIHRo aXMgZmlsZS4NCg0KcHNldWRvLWRldmljZQlsb29wDQpwc2V1ZG8tZGV2aWNl CWV0aGVyDQpwc2V1ZG8tZGV2aWNlCXNsCTENCnBzZXVkby1kZXZpY2UJcHBw CTENCnBzZXVkby1kZXZpY2UJdHVuCTENCnBzZXVkby1kZXZpY2UJcHR5CTE2 DQpwc2V1ZG8tZGV2aWNlCWd6aXAJCSMgRXhlYyBnemlwcGVkIGEub3V0J3MN Cg0KIyBLVFJBQ0UgZW5hYmxlcyB0aGUgc3lzdGVtLWNhbGwgdHJhY2luZyBm YWNpbGl0eSBrdHJhY2UoMikuDQojIFRoaXMgYWRkcyA0IEtCIGJsb2F0IHRv IHlvdXIga2VybmVsLCBhbmQgc2xpZ2h0bHkgaW5jcmVhc2VzDQojIHRoZSBj b3N0cyBvZiBlYWNoIHN5c2NhbGwuDQojIG9wdGlvbnMJCUtUUkFDRQkJI2tl cm5lbCB0cmFjaW5nDQoNCiMgVGhpcyBwcm92aWRlcyBzdXBwb3J0IGZvciBT eXN0ZW0gViBzaGFyZWQgbWVtb3J5IGFuZCBtZXNzYWdlIHF1ZXVlcy4NCiMN Cm9wdGlvbnMgICAgICAgICBTWVNWU0hNDQpvcHRpb25zICAgICAgICAgU1lT Vk1TRw0Kb3B0aW9ucyAgICAgICAgIFNZU1ZTRU0NCg0KIyAgVGhlIGBicGZp bHRlcicgcHNldWRvLWRldmljZSBlbmFibGVzIHRoZSBCZXJrZWxleSBQYWNr ZXQgRmlsdGVyLiAgQmUNCiMgIGF3YXJlIG9mIHRoZSBsZWdhbCBhbmQgYWRt aW5pc3RyYXRpdmUgY29uc2VxdWVuY2VzIG9mIGVuYWJsaW5nIHRoaXMNCiMg IG9wdGlvbi4gIFRoZSBudW1iZXIgb2YgZGV2aWNlcyBkZXRlcm1pbmVzIHRo ZSBtYXhpbXVtIG51bWJlciBvZg0KIyAgc2ltdWx0YW5lb3VzIEJQRiBjbGll bnRzIHByb2dyYW1zIHJ1bm5hYmxlLg0KI3BzZXVkby1kZXZpY2UJYnBmaWx0 ZXIgNAkjQmVya2VsZXkgcGFja2V0IGZpbHRlcg0KDQojVVNCIHN1cHBvcnQN CiNjb250cm9sbGVyCXVoY2kwDQojY29udHJvbGxlcglvaGNpMA0KI2NvbnRy b2xsZXIJdXNiMA0KIw0KI2RldmljZQkJdWdlbjANCiNkZXZpY2UJCXVoaWQw DQojZGV2aWNlCQl1a2JkMA0KI2RldmljZQkJdWxwdDANCiNjb250cm9sbGVy CXVtYXNzMA0KI2RldmljZQkJdW1zMA0KDQoja2VybmVsIHRocmVhZHMNCm9w dGlvbnMgICAgICAgICBQMTAwM18xQg0Kb3B0aW9ucyAgICAgICAgIF9LUE9T SVhfUFJJT1JJVFlfU0NIRURVTElORw0Kb3B0aW9ucyAgICAgICAgIF9LUE9T SVhfVkVSU0lPTj0xOTkzMDlMDQoNCiNzb3VuZCBjYXJkDQojY29udHJvbGxl ciAgICAgIHNuZDANCiNkZXZpY2Ugc2IwICAgICAgYXQgaXNhPyBwb3J0IDB4 MjIwIGlycSA1IGRycSAxDQojZGV2aWNlIHNieHZpMCAgIGF0IGlzYT8gY29u ZmxpY3RzIGRycSAxDQojZGV2aWNlIHNibWlkaTAgIGF0IGlzYT8gcG9ydCAw eDMzMA0KI2RldmljZSBvcGwwICAgICBhdCBpc2E/IHBvcnQgMHgzODgNCg0K I2RldmljZSBwY20wIGF0IGlzYT8gZGlzYWJsZSBwb3J0ID8gaXJxID8gZHJx ID8gZmxhZ3MgMHgwDQoNCiNzb2Z0dXBkYXRlcw0Kb3B0aW9ucyBTT0ZUVVBE QVRFUw0KDQojdm9vZG9vIDIgc3VwcG9ydA0KDQojZGV2aWNlIHZvb2RvbzAN CiNkZXZpY2Ugdm9vZG9vMQ0KDQojdHYgY2FyZCBzdXBwb3J0DQpjb250cm9s bGVyIHNtYnVzMA0KY29udHJvbGxlciBpaWNidXMwDQpjb250cm9sbGVyIGlp Y2JiMA0KZGV2aWNlIGJrdHIwDQo= ---559023410-851401618-933214686=:5873-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 19:51: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 45832154A7 for ; Wed, 28 Jul 1999 19:51:05 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id TAA13119; Wed, 28 Jul 1999 19:50:03 -0700 (PDT) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA89056; Wed, 28 Jul 1999 19:50:03 -0700 (PDT) (envelope-from jdp@polstra.com) Date: Wed, 28 Jul 1999 19:50:03 -0700 (PDT) Message-Id: <199907290250.TAA89056@vashon.polstra.com> To: asmodai@wxs.nl Subject: Re: Library question/challenge In-Reply-To: <19990727230015.B393@daemon.ninth-circle.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990727230015.B393@daemon.ninth-circle.org>, Jeroen Ruigrok/Asmodai wrote: > > /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older > than expected 0, using it anyway > ld.so failed: bad magic number in "/usr/lib/libc.so.3" > > This is netscape4.5 on CURRENT tracked since October 1998. > > One change since my previous builds is that I uncommented compat22 and > compat3x prior to making world. > > I have the default aout ld path in /etc/defaults/rc.conf, none in > /etc/rc.conf. > > A ldconfig -aout -r | head -2 yields: > > /var/run/ld.so.hints: > search directories: /usr/lib/aout:/usr/lib/compat/aout: > /usr/X11R6/lib/aout:/usr/local/lib/aout > > [ it has about 66 libs in this hints file ] Run ldd on the netscape binary and figure out why it's finding the wrong libc. Make sure you don't have LD_LIBRARY_PATH set to include "/usr/lib". John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 19:51:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id EEF211551C for ; Wed, 28 Jul 1999 19:51:21 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id WAA20700; Wed, 28 Jul 1999 22:50:57 -0400 (EDT) Date: Wed, 28 Jul 1999 22:50:57 -0400 (EDT) From: "Matthew N. Dodd" To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: kernel compile error. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Kenneth Wayne Culver wrote: > ../../kern/subr_bus.c: In function `bus_print_child_header': > ../../kern/subr_bus.c:1870: parse error before `}' > *** Error code 1 > > here is my kernel conf file (as an attachment)... Thats mine. Re-cvsup and try again. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 19:58:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F756154A7 for ; Wed, 28 Jul 1999 19:58:26 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA65776; Wed, 28 Jul 1999 19:58:19 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 19:58:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199907290258.TAA65776@apollo.backplane.com> To: John Polstra Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: Library question/challenge References: <199907290250.TAA89056@vashon.polstra.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older :> than expected 0, using it anyway :> ld.so failed: bad magic number in "/usr/lib/libc.so.3" :> :> This is netscape4.5 on CURRENT tracked since October 1998. :> :> /var/run/ld.so.hints: :> search directories: /usr/lib/aout:/usr/lib/compat/aout: :> /usr/X11R6/lib/aout:/usr/local/lib/aout :> :> [ it has about 66 libs in this hints file ] : :Run ldd on the netscape binary and figure out why it's finding the :wrong libc. Make sure you don't have LD_LIBRARY_PATH set to include :"/usr/lib". : :John This happened to me. The problem is usually that the library it is looking for is simply missing from /usr/lib/aout or /usr/X11R6/lib/aout. Another possibility is that there may be old softlinks laying around /usr/lib or /usr/X11R6/lib for that library which are pointing to nowhere. apollo:/usr/lib/aout# mv libc.so.3.1 xxx apollo:/home/dillon> netscape /usr/libexec/ld.so: warning: /usr/lib/libc.so.3: minor version -1 older than expected 0, using it anyway ld.so failed: bad magic number in "/usr/lib/libc.so.3" (fails to run) apollo:/home/dillon> apollo:/usr/lib/aout# mv xxx libc.so.3.1 apollo:/home/dillon> netscape ... runs fine ... See if you can find where those aout/ compatibility libraries are. Either you have them properly installed and the ldconfig_paths in /etc/rc.conf (defaults in /etc/defaults/rc.conf) are wrong, or you do not have them installed. -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 Wed Jul 28 21:36:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id DC94414D60 for ; Wed, 28 Jul 1999 21:36:41 -0700 (PDT) (envelope-from scottm@mordred.cs.ucla.edu) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id VAA20804 for ; Wed, 28 Jul 1999 21:34:22 -0700 (PDT) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.9.3/8.9.3) id VAA00333 for freebsd-current@freebsd.org; Wed, 28 Jul 1999 21:34:32 -0700 (PDT) (envelope-from scottm) Date: Wed, 28 Jul 1999 21:34:32 -0700 (PDT) From: Scott Michel Message-Id: <199907290434.VAA00333@mordred.cs.ucla.edu> To: freebsd-current@freebsd.org Subject: kernel snark, this evening, sup'd ~1800 PDT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A kernel cvsup'd at or about 1800 PDT this evening bought the farm as so: pmap_remove_pages(c3d07924, 0, bfbfe000, c3749034, 1) exec_new_vmspace(c3dafe80, 1, 1, c3dafe80, c025dd5c) exec_elf_imgact(c3d0fe80, c3d02fa0, c025e61c, 0, 1) syscall(...) Xint0x80_syscall(...) I don't have enough disk space to save kernel cores, so I can't give much more that this backtrace. Kernel configuration follows: -------------------------------------------------------------------------- machine "i386" ident MORDRED maxusers 10 cpu "I586_CPU" # aka Pentium(tm) options PQ_HUGECACHE options CPU_WT_ALLOC options "NO_F00F_HACK" options "COMPAT_43" options USER_LDT options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" options DDB #options DDB_UNATTENDED options KTRACE #kernel tracing options PERFMON options UCONSOLE options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INET #Internet communications protocols pseudo-device ether #Generic Ethernet pseudo-device loop #Network loopback device pseudo-device bpf 4 #Berkeley packet filter pseudo-device disc #Discard device options TCP_COMPAT_42 #emulate 4.2BSD TCP bugs options MROUTING # Multicast routing # One of these is mandatory: options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options NFS_NOSERVER options CD9660 #ISO 9660 filesystem options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options NSWAPDEV=2 options QUOTA #enable disk quotas options CD9660_ROOTDELAY=20 # NFS options: options NFS_MINATTRTIMO=3 # VREG attrib cache timeout in sec options NFS_MAXATTRTIMO=60 options NFS_MINDIRATTRTIMO=30 # VDIR attrib cache timeout in sec options NFS_MAXDIRATTRTIMO=60 options NFS_GATHERDELAY=10 # Default write gather delay (msec) options NFS_UIDHASHSIZ=29 # Tune the size of nfssvc_sock with this options NFS_WDELAYHASHSIZ=16 # and with this options NFS_MUIDHASHSIZ=63 # Tune the size of nfsmount with this #options NFS_DEBUG # Enable NFS Debugging options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options _KPOSIX_VERSION=199309L controller scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device da1 device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device pt0 at scbus? #device sctarg0 at scbus? options SCSI_DELAY=8000 # Be pessimistic about Joe SCSI device options CHANGER_MIN_BUSY_SECONDS=2 options CHANGER_MAX_BUSY_SECONDS=10 pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=40960 controller isa0 controller pnp0 options VESA pseudo-device splash device sc0 at isa? options MAXCONS=8 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines device npx0 at nexus? port IO_NPX iosiz 0x0 flags 0x0 irq 13 controller fdc0 at isa? port "IO_FD1" irq 6 drq 2 disk fd0 at fdc0 drive 0 controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? port IO_KBD conflicts irq 12 device sio0 at isa? port "IO_COM1" flags 0x10 irq 4 device sio1 at isa? port "IO_COM2" flags 0x10 irq 3 device vga0 at isa? port ? conflicts device ed0 at isa? port 0x240 irq 10 iomem 0xcc000 # Sound: #device pcm0 at isa? port ? irq 5 drq 3 flags 0x0f controller snd0 device sb0 at isa? port 0x220 irq 5 drq 3 device sbxvi0 at isa? drq 7 device sbmidi0 at isa? port 0x330 controller pci0 controller ncr0 controller ppbus0 device lpt0 at ppbus? controller ppc0 at isa? port ? irq 7 options CLK_CALIBRATION_LOOP #options "CLK_USE_I8254_CALIBRATION" options CLK_USE_TSC_CALIBRATION options COMPAT_LINUX options NBUF=512 options NMBCLUSTERS=512 options PANIC_REBOOT_WAIT_TIME=16 options SHOW_BUSYBUFS # List buffers that prevent root unmount # USB support controller uhci0 controller usb0 device ukbd0 device ugen0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 21:38:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 81FF6155A1 for ; Wed, 28 Jul 1999 21:38:25 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA15847; Thu, 29 Jul 1999 00:40:05 -0400 From: Bill Paul Message-Id: <199907290440.AAA15847@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 00:40:03 -0400 (EDT) Cc: cross@cs.rpi.edu, current@freebsd.org In-Reply-To: <199907282358.QAA64519@apollo.backplane.com> from "Matthew Dillon" at Jul 28, 99 04:58:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2685 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :> Ah ha! Yes, 32K packets will certainly screw up NFS under FreeBSD. > : > :Uh.... could you elaborate a little? No, strike that: could you elaborate > :a *lot*. A whole lot. > > Sure. There is a constant called NFS_MAXDATA defined in ..mmm.. > nfs/nfsproto.h. Set to 32768 for TCP connections, 16384 for UDP > connections. The code is a mess though, so usually just the higher > limit is used. The fsinfo rpc returns this maximum to the client. > > The client is supposed to limit NFS packets to the specified size. Okay. Well, I experimented a bit, and found that if I increased NFS_MAXPACKET by 512 bytes, the machines no longer panic. (Yes, that's NFS_MAXPACKET, not NFS_MAXDATA.) 512 is just a number I pulled out of my ass: initially I just tried increasing it by 372 bytes (33544 - NFS_MAXPACKET == 372) which got me a little further along, but later I got another crash where mbuf siz was 33632. So I tried 512 and was able to do a complete du on /usr without any problems. As for the trashed mbuf chain I thought I saw, I was confused by a couple of factors: - When you do gdb -k vmunix vmcore.X, values on the stack such as automatic variables aren't reliably preserved. In this case I was trying to do a "print *m" to observe the contents of the last used mbuf and this pointed me off into space somewhere. It should have been NULL since m_next off the last mbuf in a chain is NULL. - I was looking at m_pkthdr.rcvif and m_pkthdr.len of mreq, which were not initialized and hence were also bogus (which makes sense since this was an mbuf chain to be transmitted, not the request that was received). Following the mbuf chain along showed that it was in fact sane. I don't know where these extra bytes are coming from. Presumeably there is some upper bound to the size of an NFS v3 RPC; either we are computing it wrong or SGI is. What I'd love to be able to do is snoop the requests coming from the SGI but that's hard since they're encapsulated in a TCP stream. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 21:45: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles540.castles.com [208.214.165.104]) by hub.freebsd.org (Postfix) with ESMTP id 0D80914D60 for ; Wed, 28 Jul 1999 21:44:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id VAA00721; Wed, 28 Jul 1999 21:38:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907290438.VAA00721@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: dillon@apollo.backplane.com (Matthew Dillon), cross@cs.rpi.edu, current@freebsd.org Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm In-reply-to: Your message of "Thu, 29 Jul 1999 00:40:03 EDT." <199907290440.AAA15847@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jul 1999 21:38:59 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't know where these extra bytes are coming from. Presumeably there > is some upper bound to the size of an NFS v3 RPC; either we are computing > it wrong or SGI is. What I'd love to be able to do is snoop the requests > coming from the SGI but that's hard since they're encapsulated in a TCP > stream. Ethereal (in the ports collection) should do this. It has Ken Harris' name on it, just for starters. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:18:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 183F614ED2 for ; Wed, 28 Jul 1999 22:18:18 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id WAA06233; Wed, 28 Jul 1999 22:16:17 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907290516.WAA06233@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: dillon@apollo.backplane.com (Matthew Dillon), cross@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm In-reply-to: Your message of "Thu, 29 Jul 1999 00:40:03 EDT." <199907290440.AAA15847@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 Jul 1999 22:16:17 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try tcpdump which is in the system . man tcpdump. Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:19:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 71D2114ED2 for ; Wed, 28 Jul 1999 22:19:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA66504; Wed, 28 Jul 1999 22:19:05 -0700 (PDT) (envelope-from dillon) Date: Wed, 28 Jul 1999 22:19:05 -0700 (PDT) From: Matthew Dillon Message-Id: <199907290519.WAA66504@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: SMP builds broken - my_idlePTD missing. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG test3:/usr/src/sys/compile/ALPHA# make cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -include opt_global.h -elf ../../i386/i386/bios.c ../../i386/i386/bios.c: In function `bios16': ../../i386/i386/bios.c:389: `my_idlePTD' undeclared (first use in this function) ../../i386/i386/bios.c:389: (Each undeclared identifier is reported only once ../../i386/i386/bios.c:389: for each function it appears in.) *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:48:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 46B8414F4B for ; Wed, 28 Jul 1999 22:48:45 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 2C49C1C9E; Thu, 29 Jul 1999 13:48:44 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: dillon@apollo.backplane.com (Matthew Dillon), crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm In-reply-to: Your message of "Wed, 28 Jul 1999 19:40:18 -0400." <199907282340.TAA15454@skynet.ctr.columbia.edu> Date: Thu, 29 Jul 1999 13:48:44 +0800 From: Peter Wemm Message-Id: <19990729054844.2C49C1C9E@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: > Of all the gin joints in all the towns in all the world, Matthew Dillon > had to walk into mine and say: > > > :This is yet another problem that we have run into here. If you check the > > :digest for -hackers it was reported awhile ago (mike smith even cc-ed it > > :to security since it may have been a kernel stack overflow) . Anyway, the > > :problem is that IRIX defaults to 32K packets on TCP NFSv3 mounts, and > > :16K on UDP NFSv3 mounts. I recommend using UDP and setting rsize=8192, > > :wsize=8192 in your amd maps (as we do now, no problems at all). > > : > > :-- > > :David Cross | email: crossd@cs.rpi.edu > > :Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~cr ossd > > > > Ah ha! Yes, 32K packets will certainly screw up NFS under FreeBSD. > > Uh.... could you elaborate a little? No, strike that: could you elaborate > a *lot*. A whole lot. > > > We need to fix that panic to have it simply drop the packet, I guess. > > No, we need to fix the code so it handles 32K "packets" (datagrams) > correctly. Yes, we do. I've run into this problem elsewhere but a quick fix was needed so it just got hacked. NT NFS clients tend to trigger it too. The problem is that the sanity check is a fair way away from where the problem packet is generated. The bad reply is generated in the readdirplus routine, gets replied (without checking) and cached. The client drops the (oversize) packet, resends, and the nfsd replies from the cache and this time hits the sanity check and panics. I didn't have access to the machine that was dying and don't have an NT or IRIX client to provoke it. I suspect a 32K mount from a freebsd box will do it too but (at the time) didn't have one I could afford to crash test with, and never got around to revisiting it. I will have another look shortly. Anyway, the clue is that the server readdirplus routine is the apparent culprit. > -Bill Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:49:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 50F3415550 for ; Wed, 28 Jul 1999 22:49:21 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.11]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAC910; Thu, 29 Jul 1999 07:48:58 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id HAA47818; Thu, 29 Jul 1999 07:47:24 +0200 (CEST) (envelope-from asmodai) Date: Thu, 29 Jul 1999 07:47:23 +0200 From: Jeroen Ruigrok/Asmodai To: Matthew Dillon Cc: John Polstra , asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: Library question/challenge Message-ID: <19990729074723.B47767@daemon.ninth-circle.org> References: <199907290250.TAA89056@vashon.polstra.com> <199907290258.TAA65776@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199907290258.TAA65776@apollo.backplane.com>; from Matthew Dillon on Wed, Jul 28, 1999 at 07:58:19PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon (dillon@apollo.backplane.com) [990729 07:20]: > lib/libc.so.3: minor version -1 older > :> than expected 0, using it anyway > :> ld.so failed: bad magic number in "/usr/lib/libc.so.3" > :> > :> This is netscape4.5 on CURRENT tracked since October 1998. > :> > :> /var/run/ld.so.hints: > :> search directories: /usr/lib/aout:/usr/lib/compat/aout: > :> /usr/X11R6/lib/aout:/usr/local/lib/aout > :> > :> [ it has about 66 libs in this hints file ] > > This happened to me. The problem is usually that the library it > is looking for is simply missing from /usr/lib/aout or > /usr/X11R6/lib/aout. Another possibility is that there may be > old softlinks laying around /usr/lib or /usr/X11R6/lib for that > library which are pointing to nowhere. I will have to see about the softlinks. Well, it seems to want libc.so.3.1 and that one is present in /usr/lib/aout and is grepable from ldconfig -aout -r: [asmodai@daemon:/usr/home/asmodai] (3) $ ldconfig -aout -r | grep libc.so 27:-lc.3.1 => /usr/lib/aout/libc.so.3.1 > See if you can find where those aout/ compatibility libraries are. > Either you have them properly installed and the ldconfig_paths in > /etc/rc.conf (defaults in /etc/defaults/rc.conf) are wrong, or > you do not have them installed. My aout ldconfig path is the /etc/defaults/rc.conf one, I always sync /etc after a make world using mergemaster most of the time. In /usr/lib/aout there's a libc.so.3.1 but it is dated March the 20th. But given the fact that it ran good until now it should still be good I guess. One person also pointed out in another later post of mine that I forgot -DWANT_AOUT during make world, this might have caused problems. So I am trying a make world with -DWANT_AOUT as well. I am also going to build XFree 3.3.4.x just to be sure it's not that as well. Thanks for the suggestions, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:49:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id CC51315587 for ; Wed, 28 Jul 1999 22:49:17 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.197.11]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB910; Thu, 29 Jul 1999 07:48:57 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id HAA47793; Thu, 29 Jul 1999 07:35:03 +0200 (CEST) (envelope-from asmodai) Date: Thu, 29 Jul 1999 07:35:03 +0200 From: Jeroen Ruigrok/Asmodai To: John Polstra Cc: asmodai@wxs.nl, current@freebsd.org Subject: Re: Library question/challenge Message-ID: <19990729073502.A47767@daemon.ninth-circle.org> References: <19990727230015.B393@daemon.ninth-circle.org> <199907290250.TAA89056@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <199907290250.TAA89056@vashon.polstra.com>; from John Polstra on Wed, Jul 28, 1999 at 07:50:03PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Polstra (jdp@polstra.com) [990729 07:20]: > Run ldd on the netscape binary and figure out why it's finding the > wrong libc. Make sure you don't have LD_LIBRARY_PATH set to include > "/usr/lib". Well, I needed to update netscape anyways, so I rm'd the old binaries and proceeded to install navigator46. I even got these errors I mentioned during install of navigator. I am going to try some of what Matthew wrote [see other follow-up]. thanks for the suggestion, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 22:52:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 79B1814F4B for ; Wed, 28 Jul 1999 22:52:05 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA01693 for ; Thu, 29 Jul 1999 15:20:02 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA90217 for FreeBSD-current@FreeBSD.ORG; Thu, 29 Jul 1999 15:20:00 +0930 (CST) Date: Thu, 29 Jul 1999 15:20:00 +0930 From: Greg Lehey To: FreeBSD current users Subject: Broken world Message-ID: <19990729152000.M66861@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_new -o _op_new.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc In file included from /usr/obj/usr/src/tmp/usr/include/stddef.h:39, from /usr/obj/usr/src/tmp/usr/include/g++/new:8, from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:103: syntax error before `__attribute__' /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:104: syntax error before `__attribute__' In file included from /usr/obj/usr/src/tmp/usr/include/g++/new:9, from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant *** Error code 1 This happened on multiple machines. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 23: 6: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 4595A14E52 for ; Wed, 28 Jul 1999 23:06:03 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-4-30.ucdavis.edu [169.237.17.158]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA21032; Wed, 28 Jul 1999 23:05:59 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA77996; Wed, 28 Jul 1999 23:05:57 -0700 (PDT) (envelope-from obrien) Date: Wed, 28 Jul 1999 23:05:56 -0700 From: "David O'Brien" To: Greg Lehey Cc: FreeBSD current users Subject: Re: Broken world Message-ID: <19990728230556.A72065@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990729152000.M66861@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990729152000.M66861@freebie.lemis.com>; from Greg Lehey on Thu, Jul 29, 1999 at 03:20:00PM +0930 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: > /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant > *** Error code 1 This is due to the Bison->Yacc change. I did builds of the compiler and all, but not a full make world before commiting. I am *VERY* surprised it has taken nearly 24hrs for someone to yell Ouch! This morning and now I have been unable to verify this wasn't a problem due to local hacks. I am glad to now have independant verification. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 23:10:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id A0BCE14E52 for ; Wed, 28 Jul 1999 23:10:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA01748; Thu, 29 Jul 1999 15:37:22 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA90308; Thu, 29 Jul 1999 15:37:22 +0930 (CST) Date: Thu, 29 Jul 1999 15:37:22 +0930 From: Greg Lehey To: "David O'Brien" Cc: FreeBSD current users Subject: Re: Broken world Message-ID: <19990729153722.P66861@freebie.lemis.com> References: <19990729152000.M66861@freebie.lemis.com> <19990728230556.A72065@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990728230556.A72065@dragon.nuxi.com>; from David O'Brien on Wed, Jul 28, 1999 at 11:05:56PM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 28 July 1999 at 23:05:56 -0700, David O'Brien wrote: >> from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: >> /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant >> *** Error code 1 > > This is due to the Bison->Yacc change. I almost thought so. > I did builds of the compiler and all, but not a full make world > before commiting. I am *VERY* surprised it has taken nearly 24hrs > for someone to yell Ouch! I like to check my findings before screaming :-) > This morning and now I have been unable to verify this wasn't a > problem due to local hacks. I am glad to now have independant > verification. Any prognosis on a fix? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 23:15:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 6797B15550 for ; Wed, 28 Jul 1999 23:15:21 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id AF5691C9E; Thu, 29 Jul 1999 14:15:19 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Paul Cc: dillon@apollo.backplane.com (Matthew Dillon), cross@cs.rpi.edu, current@FreeBSD.org Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm In-reply-to: Your message of "Thu, 29 Jul 1999 00:40:03 -0400." <199907290440.AAA15847@skynet.ctr.columbia.edu> Date: Thu, 29 Jul 1999 14:15:19 +0800 From: Peter Wemm Message-Id: <19990729061519.AF5691C9E@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Paul wrote: [..] > Okay. Well, I experimented a bit, and found that if I increased > NFS_MAXPACKET by 512 bytes, the machines no longer panic. (Yes, that's > NFS_MAXPACKET, not NFS_MAXDATA.) 512 is just a number I pulled out of my > ass: initially I just tried increasing it by 372 bytes (33544 - > NFS_MAXPACKET == 372) which got me a little further along, but later I > got another crash where mbuf siz was 33632. So I tried 512 and was able > to do a complete du on /usr without any problems. One crashdump I've seen was oversize by 308 bytes, another was about 680 bytes. Having the client do a readdir() on a large directory is what triggers it. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jul 28 23:25:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CB5E15563 for ; Wed, 28 Jul 1999 23:25:11 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40345>; Thu, 29 Jul 1999 16:04:31 +1000 Date: Thu, 29 Jul 1999 16:23:17 +1000 From: Peter Jeremy Subject: Re: Broken world In-reply-to: <19990728230556.A72065@dragon.nuxi.com> To: obrien@NUXI.com Cc: FreeBSD-current@FreeBSD.ORG, grog@lemis.com Message-Id: <99Jul29.160431est.40345@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: >> from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: >> /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant >> *** Error code 1 > > >This is due to the Bison->Yacc change. I did builds of the compiler and >all, but not a full make world before commiting. I am *VERY* surprised >it has taken nearly 24hrs for someone to yell Ouch! I wrote exactly the same thing as Greg, just over 9 hours ago. Petrer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 0:24:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id C8AE91566E for ; Thu, 29 Jul 1999 00:24:35 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id JAA07068; Thu, 29 Jul 1999 09:23:38 +0200 (MET DST) Date: Thu, 29 Jul 1999 09:23:37 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: John Hay Cc: "Matthew N. Dodd" , current@FreeBSD.ORG Subject: Re: a little newbus problem In-Reply-To: <199907282011.WAA50899@zibbi.mikom.csir.co.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any source we can have a look at (probe/attach/*_MODULE)? Nick On Wed, 28 Jul 1999, John Hay wrote: > Nope, it is an ISA driver and I wasn't that brave. :-) It is part of > standard FreeBSD and I just compiled it into the kernel with a kernel > config file. > > > Are you by any chance kldload'ing the module for testing? > > > > If so you should have: > > > > DEVMETHOD(bus_driver_added, bus_generic_driver_added), > > > > For your 'arc' device_method_t method declaration. > > > > I got bit by this one too. > > > > On Wed, 28 Jul 1999, John Hay wrote: > > > I have been trying to get my ar(4) and sr(4) drivers going again on -current, > > > but it seems that the newbus code doesn't like my little trick that worked > > > for so long. :-( > > > > > > Basically the drivers are called ar0 in the kernel config file, but in > > > the isa_driver struct I call them arc and not ar, because the chip that > > > is used actually have 2 ports and I register them seperately as ar0 and > > > ar1 during the attach phase. > > > > > > >From what I can see now, it looks like the newbus code doesn't even > > > call the arprobe routine. I have even added a printf right in the start > > > of it, but it never prints anything. Just as a test I changed my kernel > > > config file and files.i386 from ar to arc and then it works. > > > > > > So what should I do? Can the newbus code be fixed to work in this case > > > too or should I newbusify the drivers and will that help? Won't that > > > create a clash because of the isa compatabilty shim? > > > > > John > -- > John Hay -- John.Hay@mikom.csir.co.za > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 0:28: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 8880814C47 for ; Thu, 29 Jul 1999 00:27:56 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id JAA61038; Thu, 29 Jul 1999 09:27:16 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199907290727.JAA61038@zibbi.mikom.csir.co.za> Subject: Re: a little newbus problem In-Reply-To: from Nick Hibma at "Jul 29, 1999 09:23:37 am" To: nick.hibma@jrc.it (Nick Hibma) Date: Thu, 29 Jul 1999 09:27:16 +0200 (SAT) Cc: current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /usr/src/sys/i386/isa/if_ar.c /usr/src/sys/i386/isa/if_sr.c John > > Any source we can have a look at (probe/attach/*_MODULE)? > > Nick > > On Wed, 28 Jul 1999, John Hay wrote: > > > Nope, it is an ISA driver and I wasn't that brave. :-) It is part of > > standard FreeBSD and I just compiled it into the kernel with a kernel > > config file. > > > > > Are you by any chance kldload'ing the module for testing? > > > > > > If so you should have: > > > > > > DEVMETHOD(bus_driver_added, bus_generic_driver_added), > > > > > > For your 'arc' device_method_t method declaration. > > > > > > I got bit by this one too. > > > > > > On Wed, 28 Jul 1999, John Hay wrote: > > > > I have been trying to get my ar(4) and sr(4) drivers going again on -current, > > > > but it seems that the newbus code doesn't like my little trick that worked > > > > for so long. :-( > > > > > > > > Basically the drivers are called ar0 in the kernel config file, but in > > > > the isa_driver struct I call them arc and not ar, because the chip that > > > > is used actually have 2 ports and I register them seperately as ar0 and > > > > ar1 during the attach phase. > > > > > > > > >From what I can see now, it looks like the newbus code doesn't even > > > > call the arprobe routine. I have even added a printf right in the start > > > > of it, but it never prints anything. Just as a test I changed my kernel > > > > config file and files.i386 from ar to arc and then it works. > > > > > > > > So what should I do? Can the newbus code be fixed to work in this case > > > > too or should I newbusify the drivers and will that help? Won't that > > > > create a clash because of the isa compatabilty shim? > > > > > > > > John > > -- > > John Hay -- John.Hay@mikom.csir.co.za > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > -- > ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy > -- John Hay -- John.Hay@mikom.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 0:51:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7F142155A8 for ; Thu, 29 Jul 1999 00:51:12 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-4.ucdavis.edu [169.237.16.132]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA21325; Thu, 29 Jul 1999 00:50:54 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA81251; Thu, 29 Jul 1999 00:50:52 -0700 (PDT) (envelope-from obrien) Date: Thu, 29 Jul 1999 00:50:51 -0700 From: "David O'Brien" To: Greg Lehey Cc: FreeBSD current users Subject: Re: Broken world Message-ID: <19990729005051.A81228@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990729152000.M66861@freebie.lemis.com> <19990728230556.A72065@dragon.nuxi.com> <19990729153722.P66861@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990729153722.P66861@freebie.lemis.com>; from Greg Lehey on Thu, Jul 29, 1999 at 03:37:22PM +0930 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Any prognosis on a fix? I'll revert when I go to bed if I am not getting anywhere. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 1: 1:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7594414C3F; Thu, 29 Jul 1999 01:01:53 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA98474; Thu, 29 Jul 1999 09:04:59 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Thu, 29 Jul 1999 09:04:59 +0100 (BST) From: Doug Rabson To: Garrett Wollman Cc: Doug Rabson , current@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/include resource.h src/sys/alpha/pci pcibus.c src/sys/i386/include resource.h src/sys/pci pci.c pci_compat.c In-Reply-To: <199907281434.KAA07938@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 28 Jul 1999, Garrett Wollman wrote: > < said: > > > Add support for SYS_RES_DENSE and SYS_RES_BWX resource types. These are > > equivalent to SYS_RES_MEMORY for x86 but for alpha, the rman_get_virtual() > > address of the resource is initialised to point into either dense-mapped > > or bwx-mapped space respectively, allowing direct memory pointers to be > > used to device memory. > > This makes me rather uncomfortable, on several fronts. I believe it > would be more appropriate to add a type argument to rman_get_virtual. To make that work, rman_get_virtual would need to be a BUS interface method. One possible alternative is to use SYS_RES_MEMORY with a set of flags to specify how the memory is to be accessed. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 1:40:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id B078B155B8 for ; Thu, 29 Jul 1999 01:40:28 -0700 (PDT) (envelope-from alc@cs.rice.edu) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id DAA12691; Thu, 29 Jul 1999 03:40:24 -0500 (CDT) Date: Thu, 29 Jul 1999 03:40:23 -0500 From: Alan Cox To: Scott Michel Cc: current@freebsd.org Subject: Re: kernel snark, this evening, sup'd ~1800 PDT Message-ID: <19990729034023.E10860@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5us Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think this is a new problem. I recall a similar error being mentioned on the -stable mailing list last week. If you can repeat the error, please write down the program counter value. Knowing the instruction at which the fault occurs would be most valuable. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 2:22:38 1999 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 0769614DFC for ; Thu, 29 Jul 1999 02:22:28 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA16870; Thu, 29 Jul 1999 11:21:20 +0200 (CEST) (envelope-from des) To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: make.conf on CURRENT question References: <99Jul29.112939est.40351@border.alcanet.com.au> From: Dag-Erling Smorgrav Date: 29 Jul 1999 11:21:19 +0200 In-Reply-To: Peter Jeremy's message of "Thu, 29 Jul 1999 11:48:31 +1000" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Jeremy writes: > You'll also need the a.out X11 libraries, and last time I tried, > they built OK, but wouldn't work. They build OK and work fine. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 2:28:26 1999 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 88440155AE for ; Thu, 29 Jul 1999 02:28:13 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA17002; Thu, 29 Jul 1999 11:27:16 +0200 (CEST) (envelope-from des) To: "Jordan K. Hubbard" Cc: Brian Dean , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance References: <6604.933189290@zippy.cdrom.com> From: Dag-Erling Smorgrav Date: 29 Jul 1999 11:27:16 +0200 In-Reply-To: "Jordan K. Hubbard"'s message of "Wed, 28 Jul 1999 12:14:50 -0700" Message-ID: Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > The CVS metadata was removed, reducing the inode count per port significantly. > This results in faster extraction time and hence "faster" downloads, assuming > that extraction time is the bottleneck (which it is for all but the 28K and > below downloaders). How about distributing an mtree file with the ports tarball, and applying that (mtree -deU -f BSD.ports.dist -p /usr) before unpacking the actual files? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 2:29:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from turing.mathematik.uni-ulm.de (turing.mathematik.uni-ulm.de [134.60.166.1]) by hub.freebsd.org (Postfix) with SMTP id BB77B155AB for ; Thu, 29 Jul 1999 02:28:59 -0700 (PDT) (envelope-from kuebart@mathematik.uni-ulm.de) Received: by turing.mathematik.uni-ulm.de (5.x/UniUlm-2.0m) id AA13995; Thu, 29 Jul 1999 11:28:16 +0200 From: kuebart@mathematik.uni-ulm.de (Joachim Kuebart) Message-Id: <19990729112816.A13960@mathematik.uni-ulm.de> Date: Thu, 29 Jul 1999 11:28:16 +0200 To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 2:30:35 1999 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 B8BD914DFC for ; Thu, 29 Jul 1999 02:26:47 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA16967; Thu, 29 Jul 1999 11:25:45 +0200 (CEST) (envelope-from des) To: "Daniel C. Sobral" Cc: Garrett Wollman , Brian Dean , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance References: <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> <379F4390.950D08FA@newsguy.com> From: Dag-Erling Smorgrav Date: 29 Jul 1999 11:25:44 +0200 In-Reply-To: "Daniel C. Sobral"'s message of "Thu, 29 Jul 1999 02:53:20 +0900" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" writes: > Garrett Wollman wrote: > > Jordan stopped including CVS directories in the /usr/ports tarball. > I don't think a transfer rate can be affected by that, though the > total transfer time certainly would. The transfer rate measured by sysinstall includes the time required to actually unpack the ports tree. > Anyway... Jordan did it? Thanks God! Jordan, God, what's the difference? DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 2:42: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 4ED1914C85 for ; Thu, 29 Jul 1999 02:41:58 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id LAA12242; Thu, 29 Jul 1999 11:40:48 +0200 (MET DST) Date: Thu, 29 Jul 1999 11:40:47 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Joachim Kuebart Cc: freebsd-current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <19990729112816.A13960@mathematik.uni-ulm.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try sending the command to majordomo@freebsd.org Nick On Thu, 29 Jul 1999, Joachim Kuebart wrote: > unsubscribe > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 3:23:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6967714ED4 for ; Thu, 29 Jul 1999 03:23:36 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id TAA28666; Thu, 29 Jul 1999 19:22:49 +0900 (JST) Message-ID: <37A02B42.C41FFAE7@newsguy.com> Date: Thu, 29 Jul 1999 19:21:54 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Dag-Erling Smorgrav Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance References: <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> <379F4390.950D08FA@newsguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav wrote: > > Jordan, God, what's the difference? God does not belong to the -core. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 5:48:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 4B5461547B for ; Thu, 29 Jul 1999 05:48:16 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id IAA26161 for ; Thu, 29 Jul 1999 08:47:23 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA29392; Thu, 29 Jul 1999 08:46:53 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id IAA10949 for freebsd-current@freebsd.org; Thu, 29 Jul 1999 08:46:52 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199907291246.IAA10949@bb01f39.unx.sas.com> Subject: make world failure (egcs) To: freebsd-current@freebsd.org Date: Thu, 29 Jul 1999 08:46:52 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, The following seems to have slipped in over the last 24 hours. I'm probably the last to see it, and it may already be fixed, but I don't see any obvious commits: c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_new -o _op_new.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc In file included from /usr/obj/usr/src/tmp/usr/include/stddef.h:39, from /usr/obj/usr/src/tmp/usr/include/g++/new:8, from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:103: syntax error before `__attribute__' /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:104: syntax error before `__attribute__' In file included from /usr/obj/usr/src/tmp/usr/include/g++/new:9, from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant *** Error code 1 Stop. *** Error code 1 source is current as of 2am (6hrs, 45mins ago). Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 8:17: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id BFB0714EC3 for ; Thu, 29 Jul 1999 08:16:54 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id IAA15944; Thu, 29 Jul 1999 08:16:53 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA89795; Thu, 29 Jul 1999 08:16:49 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990729074723.B47767@daemon.ninth-circle.org> Date: Thu, 29 Jul 1999 08:16:49 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Jeroen Ruigrok/Asmodai Subject: Re: Library question/challenge Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > * Matthew Dillon (dillon@apollo.backplane.com) [990729 07:20]: >> lib/libc.so.3: minor version -1 older >> :> than expected 0, using it anyway >> :> ld.so failed: bad magic number in "/usr/lib/libc.so.3" Look, it's finding its library in "/usr/lib" and it shouldn't be doing that. This is the problem, and there's no point in upgrading X11 or any such thing. > Well, it seems to want libc.so.3.1 and that one is present in /usr/lib/aout > and is grepable from ldconfig -aout -r: > > [asmodai@daemon:/usr/home/asmodai] (3) $ ldconfig -aout -r | grep libc.so > 27:-lc.3.1 => /usr/lib/aout/libc.so.3.1 Right. So the problem must be that you have LD_LIBRARY_PATH set. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 8:54:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from voyager.fisicc-ufm.edu (ip-46-094.guate.net [200.12.46.94]) by hub.freebsd.org (Postfix) with ESMTP id 375FB155F4 for ; Thu, 29 Jul 1999 08:51:45 -0700 (PDT) (envelope-from obonilla@voyager.fisicc-ufm.edu) Received: (from obonilla@localhost) by voyager.fisicc-ufm.edu (8.9.3/8.9.3) id JAA01333; Thu, 29 Jul 1999 09:49:50 -0600 (CST) (envelope-from obonilla) Date: Thu, 29 Jul 1999 09:49:49 -0600 From: Oscar Bonilla To: "John W. DeBoskey" Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world failure (egcs) Message-ID: <19990729094948.A1242@fisicc-ufm.edu> References: <199907291246.IAA10949@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199907291246.IAA10949@bb01f39.unx.sas.com>; from John W. DeBoskey on Thu, Jul 29, 1999 at 08:46:52AM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 29, 1999 at 08:46:52AM -0400, John W. DeBoskey wrote: > Hi, > > The following seems to have slipped in over the last 24 hours. I'm > probably the last to see it, and it may already be fixed, but I don't > see any obvious commits: > > c++ -c -I/usr/obj/usr/src/tmp/usr/include/g++ -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/inc -nostdinc++ -DL_op_new -o _op_new.o /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc > In file included from /usr/obj/usr/src/tmp/usr/include/stddef.h:39, > from /usr/obj/usr/src/tmp/usr/include/g++/new:8, > from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: > /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:103: syntax error before `__attribute__' > /usr/obj/usr/src/tmp/usr/include/machine/ansi.h:104: syntax error before `__attribute__' > In file included from /usr/obj/usr/src/tmp/usr/include/g++/new:9, > from /usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/cp/new1.cc:28: > /usr/obj/usr/src/tmp/usr/include/g++/exception:9: syntax error before string constant > *** Error code 1 > > Stop. > *** Error code 1 > > > source is current as of 2am (6hrs, 45mins ago). > It's been fixed. It had to do with the change from bison to yacc. regards, -Oscar -- For PGP Public Key: finger obonilla@fisicc-ufm.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 10:28: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A63D14C06 for ; Thu, 29 Jul 1999 10:26:21 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA76001; Thu, 29 Jul 1999 10:25:46 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 10:25:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199907291725.KAA76001@apollo.backplane.com> To: Peter Wemm Cc: Bill Paul , crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <19990729054844.2C49C1C9E@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Yes, we do. I've run into this problem elsewhere but a quick fix was needed :so it just got hacked. NT NFS clients tend to trigger it too. : :The problem is that the sanity check is a fair way away from where the problem :packet is generated. The bad reply is generated in the readdirplus routine, :gets replied (without checking) and cached. The client drops the (oversize) :packet, resends, and the nfsd replies from the cache and this time hits :the sanity check and panics. : :... : :I will have another look shortly. Anyway, the clue is that the server :readdirplus routine is the apparent culprit. : :Cheers, :-Peter This makes a lot of sense. A report of du causing the panic, and the good possibility that readdirplus is caching an oversized response packet. Tell me what you come up with! I'll take a crack at it if you don't find anything. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 10:51:39 1999 Delivered-To: freebsd-current@freebsd.org Received: from fep2.post.tele.dk (fep2.post.tele.dk [195.41.46.135]) by hub.freebsd.org (Postfix) with ESMTP id 902AE14FCE for ; Thu, 29 Jul 1999 10:51:27 -0700 (PDT) (envelope-from peter@holm.cc) Received: from holm.cc ([195.249.209.23]) by fep2.post.tele.dk (InterMail v4.0 201-221) with ESMTP id <19990729175058.JEYC25458.fep2@holm.cc> for ; Thu, 29 Jul 1999 19:50:58 +0200 Message-ID: <37A094ED.793A1AE9@holm.cc> Date: Thu, 29 Jul 1999 19:52:45 +0200 From: Peter Holm X-Mailer: Mozilla 4.51 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Freebsd-current@freebsd.org Subject: panic: softdep_flushfiles: looping Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kirk seems to be out of touch :-), so I created PR kern/12869. -- Peter Holm | mailto:peter@holm.cc | http://login.dknet.dk/~pho/ -[ Member of the BSD-Dk User Group / http://www.bsd-dk.dk/ ] - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 10:53:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from whizkidtech.net (r17.bfm.org [208.18.213.113]) by hub.freebsd.org (Postfix) with ESMTP id 120E2150DA for ; Thu, 29 Jul 1999 10:53:19 -0700 (PDT) (envelope-from adam@whizkidtech.net) Received: (from adam@localhost) by whizkidtech.net (8.9.2/8.9.2) id MAA00238; Thu, 29 Jul 1999 12:53:16 -0500 (CDT) (envelope-from adam) Date: Thu, 29 Jul 1999 12:52:45 -0500 From: "G. Adam Stanislav" To: Dag-Erling Smorgrav Cc: freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance Message-ID: <19990729125245.A224@whizkidtech.net> References: <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> <379F4390.950D08FA@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Dag-Erling Smorgrav on Thu, Jul 29, 1999 at 11:25:44AM +0200 Organization: Whiz Kid Technomagic X-URL: http://www.whizkidtech.net/ X-Operating-System: FreeBSD whizkidtech.net 3.1-RELEASE FreeBSD 3.1-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 29, 1999 at 11:25:44AM +0200, Dag-Erling Smorgrav wrote: > Jordan, God, what's the difference? Jordan exists. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 10:58:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1D7C6150E1 for ; Thu, 29 Jul 1999 10:58:55 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA19115; Fri, 30 Jul 1999 02:57:44 +0900 (JST) Message-ID: <37A095FA.67ACC58D@newsguy.com> Date: Fri, 30 Jul 1999 02:57:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Peter Holm Cc: Freebsd-current@FreeBSD.ORG Subject: Re: panic: softdep_flushfiles: looping References: <37A094ED.793A1AE9@holm.cc> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Holm wrote: > > Kirk seems to be out of touch :-), so I created PR kern/12869. I seem to recall a message from him last week saying he was going on a six weeks vacation. Well, he *did* said he was going on vacation, it's the "last week" and "six weeks" part I'm not 100% sure. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 11: 0: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 92AC8150DA for ; Thu, 29 Jul 1999 10:59:57 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA19282; Fri, 30 Jul 1999 02:59:51 +0900 (JST) Message-ID: <37A09679.88910EFD@newsguy.com> Date: Fri, 30 Jul 1999 02:59:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "G. Adam Stanislav" Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance References: <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> <379F4390.950D08FA@newsguy.com> <19990729125245.A224@whizkidtech.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "G. Adam Stanislav" wrote: > > On Thu, Jul 29, 1999 at 11:25:44AM +0200, Dag-Erling Smorgrav wrote: > > Jordan, God, what's the difference? > > Jordan exists. Don't go there. This whole existance-of-perl-scripts thingy is dangerous territory. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Is it true that you're a millionaire's son who never worked a day in your life?" "Yeah, I guess so." "Lemme tell you, son, you ain't missed a thing." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 11:30:31 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id F1FFF155F4 for ; Thu, 29 Jul 1999 11:30:18 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.214]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA518C; Thu, 29 Jul 1999 20:29:48 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA79367; Thu, 29 Jul 1999 20:24:35 +0200 (CEST) (envelope-from asmodai) Date: Thu, 29 Jul 1999 20:24:35 +0200 From: Jeroen Ruigrok/Asmodai To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: Library question/challenge Message-ID: <19990729202434.A78719@daemon.ninth-circle.org> References: <19990729074723.B47767@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from John Polstra on Thu, Jul 29, 1999 at 08:16:49AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Polstra (jdp@polstra.com) [990729 18:49]: > Jeroen Ruigrok/Asmodai wrote: > > Well, it seems to want libc.so.3.1 and that one is present in /usr/lib/aout > > and is grepable from ldconfig -aout -r: > > > > [asmodai@daemon:/usr/home/asmodai] (3) $ ldconfig -aout -r | grep libc.so > > 27:-lc.3.1 => /usr/lib/aout/libc.so.3.1 > > Right. So the problem must be that you have LD_LIBRARY_PATH set. Yes I have, but this hasn't been a problem for the last 5-6 months. In what way could it interfere with my ldconfig then? (I read man 1aout ld) I think, a guess, that make world without -DWANT_AOUT in conjunction with my make.conf adjustments caused problems. Then again, I am still a rookie. Thanks for the help thus far John, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 11:45:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6117214D52 for ; Thu, 29 Jul 1999 11:45:29 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-39.ucdavis.edu [169.237.16.167]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id LAA23512; Thu, 29 Jul 1999 11:45:14 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id LAA06301; Thu, 29 Jul 1999 11:45:12 -0700 (PDT) (envelope-from obrien) Date: Thu, 29 Jul 1999 11:45:11 -0700 From: "David O'Brien" To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: Library question/challenge Message-ID: <19990729114511.A6278@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990729074723.B47767@daemon.ninth-circle.org> <19990729202434.A78719@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990729202434.A78719@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Thu, Jul 29, 1999 at 08:24:35PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think, a guess, that make world without -DWANT_AOUT in conjunction with Unless you are trying to support current development of a.out binaries, there is little need to be useing "-DWANT_AOUT". All you want is suport for existing 2.2.x a.out binaries (since that is what Netscape is). Realize when building with -DWANT_AOUT, you are not creating the same libraries that were on 2.2.x, but rather libs with full 4.0-CURRENT features and content but in the a.out format. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 12:52:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 67C7115185 for ; Thu, 29 Jul 1999 12:51:36 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 87833 invoked from network); 29 Jul 1999 19:45:24 -0000 Received: from shell-1.enteract.com (dscheidt@207.229.143.40) by pop3-3.enteract.com with SMTP; 29 Jul 1999 19:45:24 -0000 Date: Thu, 29 Jul 1999 14:45:24 -0500 (CDT) From: David Scheidt To: "Daniel C. Sobral" Cc: Peter Holm , Freebsd-current@FreeBSD.ORG Subject: Re: panic: softdep_flushfiles: looping In-Reply-To: <37A095FA.67ACC58D@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Jul 1999, Daniel C. Sobral wrote: > Peter Holm wrote: > > > > Kirk seems to be out of touch :-), so I created PR kern/12869. > > I seem to recall a message from him last week saying he was going on > a six weeks vacation. Well, he *did* said he was going on vacation, > it's the "last week" and "six weeks" part I'm not 100% sure. Six weeks, and no computer more sophisticated than the SCUBA one, are what I remembered. Someone remind me what a vacation is again? David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 13: 5:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 532C815617 for ; Thu, 29 Jul 1999 13:05:42 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id WAA28094; Thu, 29 Jul 1999 22:05:19 +0200 (MET DST) Date: Thu, 29 Jul 1999 22:05:15 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: David Scheidt Cc: "Daniel C. Sobral" , Peter Holm , Freebsd-current@FreeBSD.ORG Subject: Re: panic: softdep_flushfiles: looping In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Six weeks, and no computer more sophisticated than the SCUBA one, are what > I remembered. Someone remind me what a vacation is again? It's when you don't have to answer your own e-mail. $ which vacation /usr/bin/vacation To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 13:23:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id BFE9714E59 for ; Thu, 29 Jul 1999 13:23:41 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id NAA24667; Thu, 29 Jul 1999 13:21:04 -0700 (PDT) Date: Thu, 29 Jul 1999 13:21:04 -0700 (PDT) From: Mike Hoskins To: "G. Adam Stanislav" Cc: Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance In-Reply-To: <19990729125245.A224@whizkidtech.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jul 1999, G. Adam Stanislav wrote: > > Jordan, God, what's the difference? > Jordan exists. Enough childish neo-religious babble? May we return to our regularly-scheduled, actually-FreeBSD-related discussions? Thanks. Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 13:40:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 4E8181511D for ; Thu, 29 Jul 1999 13:40:11 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-36.iptelecom.net.ua [212.42.69.227]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id XAA10641 for ; Thu, 29 Jul 1999 23:46:59 +0300 (EEST) Message-ID: <37A0BCEE.6A8B01F1@altavista.net> Date: Thu, 29 Jul 1999 23:43:26 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: APM related panic Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just suped and builded new kernel and discovered that it paniced when trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard + k6-II/300 CPU). Any ideas or recommendations about what should I do to make a more informative report? Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 13:44:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id BDEA91511D for ; Thu, 29 Jul 1999 13:44:15 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA17186; Thu, 29 Jul 1999 16:44:19 -0400 From: Bill Paul Message-Id: <199907292044.QAA17186@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 16:44:18 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG In-Reply-To: <199907291725.KAA76001@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 10:25:46 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3710 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :Yes, we do. I've run into this problem elsewhere but a quick fix was needed > :so it just got hacked. NT NFS clients tend to trigger it too. > : > :The problem is that the sanity check is a fair way away from where the problem > :packet is generated. The bad reply is generated in the readdirplus routine, > :gets replied (without checking) and cached. The client drops the (oversize) > :packet, resends, and the nfsd replies from the cache and this time hits > :the sanity check and panics. > : > :... > : > :I will have another look shortly. Anyway, the clue is that the server > :readdirplus routine is the apparent culprit. > : > :Cheers, > :-Peter > > This makes a lot of sense. A report of du causing the panic, and > the good possibility that readdirplus is caching an oversized response > packet. Tell me what you come up with! I'll take a crack at it if you > don't find anything. Caching doesn't enter into it. The problem is bad arithmetic. In /sys/nfs/nfs_serv.c:nfsrv_readdirplus(), we have the following code: /* * If either the dircount or maxcount will be * exceeded, get out now. Both of these lengths * are calculated conservatively, including all * XDR overheads. */ len += (7 * NFSX_UNSIGNED + nlen + rem + NFSX_V3FH + NFSX_V3POSTOPATTR); dirlen += (6 * NFSX_UNSIGNED + nlen + rem); if (len > cnt || dirlen > fullsiz) { eofflag = 0; break; } I observed that the value of "len" didn't agree with the actual amount of data beong consumed in the mbuf chain. It turns out that each time through the loop, len is being incremented by 4 bytes too little. In other words, 7 * NFSX_UNSIGNED should really be 8 * NFSX_UNSIGNED. When I change 7 to 8, I no longer get oversized replies and everything adds up. This sanity code is trying to add up the amount of data consumed for each entryplus3 that gets consumed by a directory entry. The entryplus3 is defined in nfs_prot.x like this: struct entryplus3 { fileid3 fileid; filename3 name; cookie3 cookie; post_op_attr name_attributes; post_op_fh3 name_handle; entryplus3 *nextentry; }; Unfortunately I haven't been able to wrap my brain around how this is being counted up for the "len" calculation. Whatever it's doing, it's off by 4 bytes. Possibly somebody forgot that "filename3" is a string, which in XDR format consists of a string bytes, plus padding to a longword boundary, *plus* a longword length value. Some comments would have been useful here. (Hint, hint.) What I don't know is whether or not the calculation for dirlen is wrong or not. Hopefully now that I've shown everyone the light, maybe somebody can tell me for sure. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 14:13:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BD8914CB5 for ; Thu, 29 Jul 1999 14:13:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA78730; Thu, 29 Jul 1999 14:11:36 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 14:11:36 -0700 (PDT) From: Matthew Dillon Message-Id: <199907292111.OAA78730@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907292044.QAA17186@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I counted it all up. It definitely needs to be 8 * NFSX_UNSIGNED. See my count below. -Matt :In /sys/nfs/nfs_serv.c:nfsrv_readdirplus(), we have the following :code: : : /* : * If either the dircount or maxcount will be : * exceeded, get out now. Both of these lengths : * are calculated conservatively, including all : * XDR overheads. : */ : len += (7 * NFSX_UNSIGNED + nlen + rem + NFSX_V3FH + : NFSX_V3POSTOPATTR); : dirlen += (6 * NFSX_UNSIGNED + nlen + rem); : :I observed that the value of "len" didn't agree with the actual amount :of data beong consumed in the mbuf chain. It turns out that each :time through the loop, len is being incremented by 4 bytes too little. :In other words, 7 * NFSX_UNSIGNED should really be 8 * NFSX_UNSIGNED. :When I change 7 to 8, I no longer get oversized replies and everything :adds up. :... : :Unfortunately I haven't been able to wrap my brain around how this is :being counted up for the "len" calculation. Whatever it's doing, it's :off by 4 bytes. Possibly somebody forgot that "filename3" is a string, :which in XDR format consists of a string bytes, plus padding to a longword :boundary, *plus* a longword length value. Some comments would have been :useful here. (Hint, hint.) : :What I don't know is whether or not the calculation for dirlen is :wrong or not. Hopefully now that I've shown everyone the light, maybe :somebody can tell me for sure. : :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu :... : len += (7 * NFSX_UNSIGNED + nlen + rem + NFSX_V3FH + : NFSX_V3POSTOPATTR); nfsm_clget; *tl = nfs_true; bp += NFSX_UNSIGNED; (one) nfsm_clget; *tl = 0; bp += NFSX_UNSIGNED; (two) nfsm_clget; *tl = txdr_unsigned(dp->d_fileno); bp += NFSX_UNSIGNED; (three) nfsm_clget; *tl = txdr_unsigned(nlen); bp += NFSX_UNSIGNED; (four) ... xfer = nlen; (nlen) while (xfer > 0) { nfsm_clget; if ((bp + xfer) > be) tsiz = be - bp; else tsiz = xfer; bcopy(cp, bp, tsiz); bp += tsiz; xfer -= tsiz; if (xfer > 0) cp += tsiz; } /* And null pad to a int32_t boundary */ for (i = 0; i < rem; i++) (rem) *bp++ = '\0'; /* * Now copy the flrep structure out. */ xfer = sizeof (struct flrep); >>>>>>> 8 + 4 + NFSX_V3FATTR + 4 + 4 + NFSX_V3FH note: NFSX_V3POSTOPATTR eats an extra 32 bit int because it is defined as: #define NFSX_V3POSTOPATTR (NFSX_V3FATTR + NFSX_UNSIGNED) (NFSX_V3POSTOPATTR) (NFSX_V3FATTR) (NFSX_V3FH) 20 remaining, remove 4 to take into account NFSX_UNSIGNED in NFSX_V3POSTOPATTR, leaving 16. (five) (six) (seven) (eight) ************* struct flrep { nfsuint64 fl_off; u_int32_t fl_postopok; u_int32_t fl_fattr[NFSX_V3FATTR / sizeof (u_int32_t)]; u_int32_t fl_fhok; u_int32_t fl_fhsize; u_int32_t fl_nfh[NFSX_V3FH / sizeof (u_int32_t)]; }; cp = (caddr_t)&fl; while (xfer > 0) { nfsm_clget; if ((bp + xfer) > be) tsiz = be - bp; else tsiz = xfer; bcopy(cp, bp, tsiz); bp += tsiz; xfer -= tsiz; if (xfer > 0) cp += tsiz; } -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 Thu Jul 29 14:19:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 3AB421561B for ; Thu, 29 Jul 1999 14:19:38 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA17253; Thu, 29 Jul 1999 17:19:57 -0400 From: Bill Paul Message-Id: <199907292119.RAA17253@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 17:19:55 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG In-Reply-To: <199907292111.OAA78730@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 02:11:36 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 980 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > I counted it all up. It definitely needs to be 8 * NFSX_UNSIGNED. Yes, I know that. :) But what about the check for dirlen: > : dirlen += (6 * NFSX_UNSIGNED + nlen + rem); Should this be 7 * NFSX_UNSIGNED or is it correct as it is. I don't know how dirlen relates to the entryplus3 structure. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 14:33:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id 4CB361560C for ; Thu, 29 Jul 1999 14:32:20 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id OAA42535; Thu, 29 Jul 1999 14:30:10 -0700 (PDT) Date: Thu, 29 Jul 1999 14:30:10 -0700 (PDT) From: Mike Hoskins To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: APM related panic In-Reply-To: <37A0BCEE.6A8B01F1@altavista.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jul 1999, Maxim Sobolev wrote: > + k6-II/300 CPU). Any ideas or recommendations about what should I do to > make a more informative report? Maybe dmesg would be a good start... Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 14:37:55 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id E531514DB2 for ; Thu, 29 Jul 1999 14:37:53 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA78832; Thu, 29 Jul 1999 14:37:19 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 14:37:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199907292137.OAA78832@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907292044.QAA17186@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : /* : * If either the dircount or maxcount will be : * exceeded, get out now. Both of these lengths : * are calculated conservatively, including all : * XDR overheads. : */ : len += (7 * NFSX_UNSIGNED + nlen + rem + NFSX_V3FH + : NFSX_V3POSTOPATTR); : dirlen += (6 * NFSX_UNSIGNED + nlen + rem); : if (len > cnt || dirlen > fullsiz) { : eofflag = 0; : break; : } : :Unfortunately I haven't been able to wrap my brain around how this is :being counted up for the "len" calculation. Whatever it's doing, it's :off by 4 bytes. Possibly somebody forgot that "filename3" is a string, :which in XDR format consists of a string bytes, plus padding to a longword :boundary, *plus* a longword length value. Some comments would have been :useful here. (Hint, hint.) : :What I don't know is whether or not the calculation for dirlen is :wrong or not. Hopefully now that I've shown everyone the light, maybe :somebody can tell me for sure. : :-Bill I think dirlen is supposed to be a calculation of the size of the struct dirent that the client will eventually synthesize from all of this, in order to ensure that the result synthesized by the client does not cross a 512 byte boundry. But if it is, it is being *very* conservative. I think this may simply be because different clients have different structural sizes for struct dirent. I am guess that the (6 * NFSX_UNSIGNED) is basically a NFS constant. -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 Thu Jul 29 15:20:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 0A97E15614 for ; Thu, 29 Jul 1999 15:20:23 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA17350; Thu, 29 Jul 1999 18:22:02 -0400 From: Bill Paul Message-Id: <199907292222.SAA17350@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 18:22:01 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG In-Reply-To: <199907292137.OAA78832@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 02:37:19 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1585 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > I think dirlen is supposed to be a calculation of the size of the > struct dirent that the client will eventually synthesize from all > of this, in order to ensure that the result synthesized by the client > does not cross a 512 byte boundry. But if it is, it is being *very* > conservative. > > I think this may simply be because different clients have different > structural sizes for struct dirent. I am guess that the > (6 * NFSX_UNSIGNED) is basically a NFS constant. Okay. I committed the fix to the length calculation to -current and -stable (I just love one-line patches that stop panics). I just got done patching my NFS server machines and they all seem to get along nicely with the SGI now. Now I can upgrade the other SGIs without worrying about them clobbering my FreeBSD machines. Hm. I wonder what would happen if the FreeBSD host was the client and the SGI was the server. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 15:25:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D276D15650 for ; Thu, 29 Jul 1999 15:25:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA79422; Thu, 29 Jul 1999 15:24:34 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 15:24:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199907292224.PAA79422@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907292222.SAA17350@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Okay. I committed the fix to the length calculation to -current and :-stable (I just love one-line patches that stop panics). I just got :done patching my NFS server machines and they all seem to get along :nicely with the SGI now. Now I can upgrade the other SGIs without :worrying about them clobbering my FreeBSD machines. : :Hm. I wonder what would happen if the FreeBSD host was the client :and the SGI was the server. : :-Bill :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu And here is something *really* scary. For the last month I've been running NFS over TCP without even realizing it. I had set up my machines to run NFS/TCP as a test instead of NFS/UDP and then forgot to change it back! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 16:20:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 6DAC2154E6 for ; Thu, 29 Jul 1999 16:20:44 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA17429; Thu, 29 Jul 1999 19:22:24 -0400 From: Bill Paul Message-Id: <199907292322.TAA17429@skynet.ctr.columbia.edu> Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 19:22:23 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG In-Reply-To: <199907292224.PAA79422@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 03:24:34 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2124 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > And here is something *really* scary. For the last month I've been > running NFS over TCP without even realizing it. I had set up my > machines to run NFS/TCP as a test instead of NFS/UDP and then forgot > to change it back! > > -Matt And here is something even scarier: readdirplus from the client side doesn't appear to work correctly either. This time, you don't need an IRIX machine to trigger the problem (though it helps :). Do the following client# mount -o nvsv3,tcp,rdirplus server:/somefs /mnt client# ls /mnt; du /mnt; etc... Seems okay so far, right? Ah, but now try to unmount the filesystem: # umount /mnt With an IRIX server, the machine wedges as soon as you do ls /mnt. With a FreeBSD server, nothing happens until you try to unmount the filesystem. The umount process looks like this: 0 418 388 0 -2 0 312 176 vnlock D+ p0 0:00.01 umount /mnt When the machine got stuck when I tested it with IRIX, I had to take a crash dump in order to analyze things; the kernel doesn't seem to be wedged, but I see these: 1063 362 293 0 -2 0 356 0 vnlock D+ v0 0:00.00 (ls) 1063 318 1 17 -2 17 748 0 vnlock DN p0 0:00.00 (mailck) Actually, it looks like it wedges if you use UDP too, so I guess it's not related to the transport. Anybody have any ideas? I did my good deed for the day. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 16:57:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from server.overflow.de (natgate.overflow.de [212.14.64.105]) by hub.freebsd.org (Postfix) with ESMTP id C43BB15662 for ; Thu, 29 Jul 1999 16:57:36 -0700 (PDT) (envelope-from malte@isoc.de) Received: from malte (malte@malte.overflow.de [192.168.0.14]) by server.overflow.de (8.8.8/8.8.8) with SMTP id PAA02520 for ; Thu, 29 Jul 1999 15:06:28 GMT From: Malte Wedel To: freebsd-current@freebsd.org Subject: best time for cvsup? Date: Thu, 29 Jul 1999 15:59:59 +0200 X-Mailer: KMail [version 0.7.9] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99072916110300.27179@malte> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I just wondered what time of the day is the best to do a cvsup, because it often happened to me, that I couldn't make world or compile the kernel because of current work. Of course I know, that's why it's called -current, but there should be a difference whether there are many people working on it at the moment, or all programmers are in bed and sleeping. Are there any experiences at what time (UTC) the -current tree is most stable? Malte Wedel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 17: 5:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id ACDD415742 for ; Thu, 29 Jul 1999 17:05:11 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA80452; Thu, 29 Jul 1999 17:05:02 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 17:05:02 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300005.RAA80452@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: <199907292322.TAA17429@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :And here is something even scarier: readdirplus from the client side :doesn't appear to work correctly either. This time, you don't need an :IRIX machine to trigger the problem (though it helps :). Do the following : :client# mount -o nvsv3,tcp,rdirplus server:/somefs /mnt :client# ls /mnt; du /mnt; etc... : :Seems okay so far, right? Ah, but now try to unmount the filesystem: : :# umount /mnt : :... :-Bill But, on the bright side, readdirplus is somewhat experimental in that it is not used by default, so very little testing of it has been done to date. Thus the bug is not unexepcted :-). At least the bugs we are getting now tend to be in the 'outlying areas' of NFS and not so much with the core code. Another area that is probably full of bugs: nqleasing. -- Ok, I was able to reproduce the above bug and fix it. The problem on the FreeBSD client is in nfs_readdirplusrpc() in nfs/nfs_vnops.c. It can obtain the vnode being used to populate the additional directory info in one of two ways. When it gets the vnode via nfs_nget(), the returned vnode is locked. When it gets it via a hit against NFS_CMPFH() (which I presume is for '.'), it simply VREF()'s the vnode. In the one case the vnode is returned locked, in the other it is not. However, the internal loop vrele()'s the vnode rather then vput()'s it, so the vnodes in the directory scan are never unlocked. This leads to the lockup. If you could test and then commit this patch (w/ me as the submitter), I would appreciate it! It seems to fix the problem for me. This patch is relative to CURRENT. The fix ought to be MFCable to STABLE. The funny thing is that the error termination code actually got it right and the loop got it wrong. Usually it's the other way around. -- Presumably this will not fix the SGI client. I've no idea what the problem there is. There may be a bug in the SGI client or there may be a bug in the client & server implementation of the protocol in FreeBSD. -Matt Matthew Dillon Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.135 diff -u -r1.135 nfs_vnops.c --- nfs_vnops.c 1999/07/01 13:32:54 1.135 +++ nfs_vnops.c 1999/07/29 23:57:06 @@ -2367,7 +2367,10 @@ nfsm_adv(nfsm_rndup(i)); } if (newvp != NULLVP) { - vrele(newvp); + if (newvp == vp) + vrele(newvp); + else + vput(newvp); newvp = NULLVP; } nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 17:56: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 7A26D14E96 for ; Thu, 29 Jul 1999 17:56:03 -0700 (PDT) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=genuine) by post.mail.nl.demon.net with smtp (Exim 2.02 #1) id 11A0xb-0003B7-00; Fri, 30 Jul 1999 00:55:43 +0000 Message-ID: <005b01beda26$3da0bfb0$0400000a@oldserver.demon.nl> From: "Marc Schneiders" To: "Malte Wedel" , References: <99072916110300.27179@malte> Subject: Re: best time for cvsup? Date: Fri, 30 Jul 1999 02:55:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Malte Wedel wrote on Thursday, July 29, 1999 3:59 PM > I just wondered what time of the day is the best to do a cvsup, because it > often happened to me, that I couldn't make world or compile the kernel because > of current work. Of course I know, that's why it's called -current, but there > should be a difference whether there are many people working on it at the > moment, or all programmers are in bed and sleeping. > > Are there any experiences at what time (UTC) the -current tree is most stable? I've had no problems so far some time after 0:00 h GMT, using the Dutch mirror. I suppose you use the German one. Perhaps that is updated more often. Marc Schneiders marc@oldserver.demon.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20: 6:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id B044F14DED for ; Thu, 29 Jul 1999 20:06:10 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA17720; Thu, 29 Jul 1999 23:06:36 -0400 From: Bill Paul Message-Id: <199907300306.XAA17720@skynet.ctr.columbia.edu> Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 23:06:35 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@freebsd.org In-Reply-To: <199907300005.RAA80452@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 05:05:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 5088 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :And here is something even scarier: readdirplus from the client side > :doesn't appear to work correctly either. This time, you don't need an > :IRIX machine to trigger the problem (though it helps :). Do the following > : > :client# mount -o nvsv3,tcp,rdirplus server:/somefs /mnt > :client# ls /mnt; du /mnt; etc... > : > :Seems okay so far, right? Ah, but now try to unmount the filesystem: > : > :# umount /mnt > : > :... > :-Bill > > But, on the bright side, readdirplus is somewhat experimental in that > it is not used by default, so very little testing of it has been done > to date. Thus the bug is not unexepcted :-). At least the bugs we > are getting now tend to be in the 'outlying areas' of NFS and not so much > with the core code. Well, IRIX is using it by default, and option or not, it's documented and implemented, so it should work. > Another area that is probably full of bugs: nqleasing. Well, the problem there is: what commercial UNIXes implement NQNFS? I stumbled over these problems because I was testing things with a commercial implementation of NFS. > -- > > Ok, I was able to reproduce the above bug and fix it. The problem on > the FreeBSD client is in nfs_readdirplusrpc() in nfs/nfs_vnops.c. It > can obtain the vnode being used to populate the additional directory > info in one of two ways. When it gets the vnode via nfs_nget(), the > returned vnode is locked. When it gets it via a hit against NFS_CMPFH() > (which I presume is for '.'), it simply VREF()'s the vnode. > > In the one case the vnode is returned locked, in the other it is not. > > However, the internal loop vrele()'s the vnode rather then vput()'s it, > so the vnodes in the directory scan are never unlocked. This leads to > the lockup. Uh, yeah. One of these days I'll be able to understand everything that you just said. But not today. > If you could test and then commit this patch (w/ me as the submitter), > I would appreciate it! It seems to fix the problem for me. This patch > is relative to CURRENT. The fix ought to be MFCable to STABLE. Close, but not quite. You didn't beat up on it hard enough. The secret is to think like a kid with a new toy, or more precisely, a sysadmin with a new toy (amounts to the same thing :). The first thing any sysadmin wants to do when you hand him a new gizmo is to push the buttons, turns the knobs and flip the switches, in order to try out all those great new features he's heard about. That's how you find the bugs. Anyway, in this case, I found another problem: with your patch applied, I mounted a filesystem from a 3.2-RELEASE server (which I fixed today with the readdirplus server side patch) which happened to have a directory containing the unpacked source code for Ghostscript 5.50, plus objects left over from a build. There are a crapload of files in the gs 5.50 distribution, plus another crapload created by compiling it. I did the following: client# mount -o nfsv3,tcp,rdirplus server:/fs /mnt client# cd /mnt client# ls client# du There seems to be another problem in nfs_readdirplusrpc(). The following diff shows the changes I made to stop the panic: > The funny thing is that the error termination code actually got it > right and the loop got it wrong. Usually it's the other way around. > > -- > > Presumably this will not fix the SGI client. I've no idea what the > problem there is. There may be a bug in the SGI client or there may > be a bug in the client & server implementation of the protocol in FreeBSD. > > -Matt > Matthew Dillon > > > > Index: nfs_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v > retrieving revision 1.135 > diff -u -r1.135 nfs_vnops.c > --- nfs_vnops.c 1999/07/01 13:32:54 1.135 > +++ nfs_vnops.c 1999/07/29 23:57:06 > @@ -2367,7 +2367,10 @@ > nfsm_adv(nfsm_rndup(i)); > } > if (newvp != NULLVP) { > - vrele(newvp); > + if (newvp == vp) > + vrele(newvp); > + else > + vput(newvp); > newvp = NULLVP; > } > nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED); > -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20:16:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 9245C14EED for ; Thu, 29 Jul 1999 20:16:00 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA17754; Thu, 29 Jul 1999 23:16:40 -0400 From: Bill Paul Message-Id: <199907300316.XAA17754@skynet.ctr.columbia.edu> Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 23:16:38 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@freebsd.org In-Reply-To: <199907300005.RAA80452@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 05:05:02 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Crap, I just sent out an incomplete message. Let me pick up from where I left off. Here's a diff that shows the changes I made to nfs_vfsops.c: *** nfs_vnops.c.orig Thu Jul 29 22:46:28 1999 --- nfs_vnops.c Thu Jul 29 22:36:39 1999 *************** *** 2342,2348 **** IFTODT(VTTOIF(np->n_vattr.va_type)); ndp->ni_vp = newvp; cnp->cn_hash = 0; ! for (cp = cnp->cn_nameptr, i = 1; i <= len; i++, cp++) cnp->cn_hash += (unsigned char)*cp * i; cache_enter(ndp->ni_dvp, ndp->ni_vp, cnp); --- 2342,2351 ---- IFTODT(VTTOIF(np->n_vattr.va_type)); ndp->ni_vp = newvp; cnp->cn_hash = 0; ! /*for (cp = cnp->cn_nameptr, i = 1; i <= len;*/ ! if (len != cnp->cn_namelen) ! printf("bogus: %d %d\n", len, cnp->cn_namelen); ! for (cp = cnp->cn_nameptr, i = 1; i <= cnp->cn_namelen; i++, cp++) cnp->cn_hash += (unsigned char)*cp * i; cache_enter(ndp->ni_dvp, ndp->ni_vp, cnp); Basically, at some point, the code tries to calculate a new hash value (what for I don't know) of a name that was read from the directory listing. However it uses "len" as the length of the name, which for some reason I can't understand turns out not matching the cn_namelen value in cnp. The "bogus" printf shows about a half dozen occasions where len and cn_namelen don't agree. Sometimes "len" is larger than "cnp->cn_namelen," sometimes it's smaller. By using cn_namelen instead of len, everything seems to work correctly. It looks like this loop makes more than one pass over directory entries, so it could be that len is sometimes stale. If you can make sense of why this happens, I would appreciate it: I don't like to commit changes when I don't fully understand what's going on. > Presumably this will not fix the SGI client. I've no idea what the > problem there is. There may be a bug in the SGI client or there may > be a bug in the client & server implementation of the protocol in FreeBSD. Er, I think you misunderstood: there's nothing wrong with the SGI in this case. I mentioned it because I was using it as a _server_ when testing the client side readdirplus support: the behavior with the SGI server was slightly different from another FreeBSD server (the FreeBSD client blew up right away with the SGI acting as server, where it took a little longer with the FreeBSD server). I think this was just a consequence of the filesystems being laid out differently. The patched FreeBSD client works fine now with the SGI server. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20:32:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E89F1504F for ; Thu, 29 Jul 1999 20:32:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA81350; Thu, 29 Jul 1999 20:31:38 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 20:31:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300331.UAA81350@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@freebsd.org Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: <199907300316.XAA17754@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Crap, I just sent out an incomplete message. Let me pick up from where :I left off. Here's a diff that shows the changes I made to nfs_vfsops.c: : :*** nfs_vnops.c.orig Thu Jul 29 22:46:28 1999 :--- nfs_vnops.c Thu Jul 29 22:36:39 1999 :*************** :*** 2342,2348 **** : IFTODT(VTTOIF(np->n_vattr.va_type)); : ndp->ni_vp = newvp; : cnp->cn_hash = 0; :! for (cp = cnp->cn_nameptr, i = 1; i <= len; : i++, cp++) : cnp->cn_hash += (unsigned char)*cp * i; : cache_enter(ndp->ni_dvp, ndp->ni_vp, cnp); :--- 2342,2351 ---- : IFTODT(VTTOIF(np->n_vattr.va_type)); : ndp->ni_vp = newvp; : cnp->cn_hash = 0; :! /*for (cp = cnp->cn_nameptr, i = 1; i <= len;*/ :! if (len != cnp->cn_namelen) :! printf("bogus: %d %d\n", len, cnp->cn_namelen); :! for (cp = cnp->cn_nameptr, i = 1; i <= cnp->cn_namelen; : i++, cp++) : cnp->cn_hash += (unsigned char)*cp * i; : cache_enter(ndp->ni_dvp, ndp->ni_vp, cnp); : :Basically, at some point, the code tries to calculate a new hash value :(what for I don't know) of a name that was read from the directory :listing. However it uses "len" as the length of the name, which for :some reason I can't understand turns out not matching the cn_namelen :value in cnp. The "bogus" printf shows about a half dozen occasions :where len and cn_namelen don't agree. Sometimes "len" is larger :than "cnp->cn_namelen," sometimes it's smaller. By using cn_namelen :instead of len, everything seems to work correctly. It looks like :this loop makes more than one pass over directory entries, so it could :be that len is sometimes stale. If you can make sense of why this :happens, I would appreciate it: I don't like to commit changes when :I don't fully understand what's going on. Look up a bit in the code. If bigenough is not true, cnp does not get initialized. This could lead to the bogus length -- or rather, it would be the cnp that is bogus, not the 'len'. The question is how to fix it. I think we can safely avoid doing the cache_enter so try changing the 'if (doit)' to 'if (doit && bigenough)'. I've included the patch below. I am not 100% sure about this. :> Presumably this will not fix the SGI client. I've no idea what the :> problem there is. There may be a bug in the SGI client or there may :> be a bug in the client & server implementation of the protocol in FreeBSD. : :Er, I think you misunderstood: there's nothing wrong with the SGI in :this case. I mentioned it because I was using it as a _server_ when :testing the client side readdirplus support: the behavior with the :... :was just a consequence of the filesystems being laid out differently. :The patched FreeBSD client works fine now with the SGI server. : :-Bill Ah, ok. I mistook the SGI for being a client. -Matt Matthew Dillon Index: nfs_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_vnops.c,v retrieving revision 1.135 diff -u -r1.135 nfs_vnops.c --- nfs_vnops.c 1999/07/01 13:32:54 1.135 +++ nfs_vnops.c 1999/07/30 03:28:36 @@ -2343,7 +2343,7 @@ newvp = NFSTOV(np); } } - if (doit) { + if (doit && bigenough) { dpossav2 = dpos; dpos = dpossav1; mdsav2 = md; @@ -2367,7 +2367,10 @@ nfsm_adv(nfsm_rndup(i)); } if (newvp != NULLVP) { - vrele(newvp); + if (newvp == vp) + vrele(newvp); + else + vput(newvp); newvp = NULLVP; } nfsm_dissect(tl, u_int32_t *, NFSX_UNSIGNED); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20:35:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A5EB61504F for ; Thu, 29 Jul 1999 20:35:10 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA81373; Thu, 29 Jul 1999 20:33:47 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 20:33:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300333.UAA81373@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: <199907300306.XAA17720@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Close, but not quite. You didn't beat up on it hard enough. The secret :is to think like a kid with a new toy, or more precisely, a sysadmin with :a new toy (amounts to the same thing :). The first thing any sysadmin :wants to do when you hand him a new gizmo is to push the buttons, turns :the knobs and flip the switches, in order to try out all those great :new features he's heard about. That's how you find the bugs. Well, I did a build world with /usr/src mounted with the rdirplus option. It obviously wasn't quite enough of a test. I'll try to reproduce the problem with a du in gs5.50 (and also see if my patch fixes it). -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 Thu Jul 29 20:35:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id 9283C15071 for ; Thu, 29 Jul 1999 20:35:18 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA08101; Thu, 29 Jul 1999 23:32:49 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 29 Jul 1999 23:32:49 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Bill Paul Cc: Matthew Dillon , peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.org Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) In-Reply-To: <199907300306.XAA17720@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 29 Jul 1999, Bill Paul wrote: > > Ok, I was able to reproduce the above bug and fix it. The problem on > > the FreeBSD client is in nfs_readdirplusrpc() in nfs/nfs_vnops.c. It > > can obtain the vnode being used to populate the additional directory > > info in one of two ways. When it gets the vnode via nfs_nget(), the > > returned vnode is locked. When it gets it via a hit against NFS_CMPFH() > > (which I presume is for '.'), it simply VREF()'s the vnode. > > > > In the one case the vnode is returned locked, in the other it is not. > > > > However, the internal loop vrele()'s the vnode rather then vput()'s it, > > so the vnodes in the directory scan are never unlocked. This leads to > > the lockup. > > Uh, yeah. > > One of these days I'll be able to understand everything that you just > said. But not today. It's not hard. vput() VOP_UNLOCK()s a vnode and then vrele() (opposite of vref())'s it (decreases v_usecount, I believe.) So when a file system is mounted, with these bugs, the locked vnodes are never unlocked. The unmount call will end up sleeping with the state "vnlock" waiting for the operation that has the vnode in question vref()d to vrele() and let go of it. At least, that's how it looks to me, but I never really looked at vnode code until today. Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20:42:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id BC6A214EBC; Thu, 29 Jul 1999 20:42:51 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA81494; Thu, 29 Jul 1999 20:42:40 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 20:42:40 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300342.UAA81494@apollo.backplane.com> To: "Brian F. Feldman" Cc: Bill Paul , peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It's not hard. vput() VOP_UNLOCK()s a vnode and then vrele() (opposite of :vref())'s it (decreases v_usecount, I believe.) So when a file system :is mounted, with these bugs, the locked vnodes are never unlocked. :The unmount call will end up sleeping with the state "vnlock" waiting for :the operation that has the vnode in question vref()d to vrele() and :let go of it. : :At least, that's how it looks to me, but I never really looked at vnode :code until today. : : Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ : green@FreeBSD.org _ __ ___ | _ ) __| \ : FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | : http://www.FreeBSD.org/ _ |___/___/___/ Basically, yes. The NFS code is a morass no matter what. Here's a full explanation: readdirplus is like readdir except it returns stat info along with the directory entries, since most NFS clients will stat the files it picks up scanning a directory. In order to accomplish this, the underlying vnode representing each directory entry is retrieved and locked. However, there is a special case: We *already* have a reference on the directory vnode itself, and one of the directory entries, ".", will be the same vnode. Our reference vnode, vp is *NOT* locked. In fact, we *can't* lock it without creating a potential deadlock situation (at least that is my take). Ok, so while scanning the directory we generate 'newvp' vnode pointers. If the directory entry is "." the newvp == vp (vp is the parent directory), and there is no lock on the vp, only a reference. If newvp != vp then it is a directory entry other then "." and newvp is both referenced *and* locked. When we are through retrieving the stat info from newvp, we have to release it. We either have to release and unlock newvp, or we simply have to release it depending on whether it was locked or not. vrele() will release a vnode without messing with any locks. vput() will release and unlock a vnode. Hence the complexity: if (newvp == vp) vrele(newvp); else; vput(newvp); -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 Thu Jul 29 20:51:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 993151504F for ; Thu, 29 Jul 1999 20:51:35 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id XAA17853; Thu, 29 Jul 1999 23:52:34 -0400 From: Bill Paul Message-Id: <199907300352.XAA17853@skynet.ctr.columbia.edu> Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 29 Jul 1999 23:52:32 -0400 (EDT) Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@freebsd.org In-Reply-To: <199907300331.UAA81350@apollo.backplane.com> from "Matthew Dillon" at Jul 29, 99 08:31:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1408 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > Look up a bit in the code. If bigenough is not true, cnp does not > get initialized. This could lead to the bogus length -- or rather, > it would be the cnp that is bogus, not the 'len'. > > The question is how to fix it. I think we can safely avoid doing the > cache_enter so try changing the 'if (doit)' to 'if (doit && bigenough)'. > I've included the patch below. > > I am not 100% sure about this. Hm. Well, it cures the panic that I was experiencing quite nicely. I'm going to commit this latest patch for now since it fixes both the vnode locking problem and a crash condition, which are pretty serious problems. If you come up with something different, I'll be happy to try it out. Not a bad day's work. :) -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 20:54:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id C78C7151FE for ; Thu, 29 Jul 1999 20:54:11 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.2/8.8.7) with ESMTP id XAA08453; Thu, 29 Jul 1999 23:51:38 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Thu, 29 Jul 1999 23:51:38 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Matthew Dillon Cc: Bill Paul , peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.org Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) In-Reply-To: <199907300342.UAA81494@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any good documentation on the vnode system? I'd like to know, for instance, what the deal is with v{hold,drop}. Originally, I was most interested in doing things with networking. VFS seems so interesting now... Perhaps I should wait before experimenting with it until the rewrite of lots of it later this year? Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 21:20:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 6A31914D5A; Thu, 29 Jul 1999 21:20:16 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA86839; Thu, 29 Jul 1999 21:20:08 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 21:20:08 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300420.VAA86839@apollo.backplane.com> To: "Brian F. Feldman" Cc: Bill Paul , peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Is there any good documentation on the vnode system? I'd like to know, for :instance, what the deal is with v{hold,drop}. : :Originally, I was most interested in doing things with networking. VFS :seems so interesting now... Perhaps I should wait before experimenting :with it until the rewrite of lots of it later this year? : : Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ : green@FreeBSD.org _ __ ___ | _ ) __| \ No, there is no good documentation, and since I am pretty much the only one who has been documenting the core VM, VFS, and NFS code, without my commit access there isn't going to be. -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 Thu Jul 29 21:30:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D5FF714D84 for ; Thu, 29 Jul 1999 21:30:32 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA86904; Thu, 29 Jul 1999 21:29:07 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 21:29:07 -0700 (PDT) From: Matthew Dillon Message-Id: <199907300429.VAA86904@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) References: <199907300352.XAA17853@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hm. Well, it cures the panic that I was experiencing quite nicely. :I'm going to commit this latest patch for now since it fixes both :the vnode locking problem and a crash condition, which are pretty :serious problems. If you come up with something different, I'll be happy :to try it out. : :Not a bad day's work. :) : :-Bill : :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu I was able to reproduce the second panic - in my case I did a du of /usr/src and it paniced in /usr/src/sys/compile/. My last patch fixes it for me too. I'll cvs update my source trees after you commit to make sure nothing has been lost. I've got 6 different patch sets in my tree right now, it will be nice to get rid of two of them :-) Really quite a good week's work. We've fixed, what, four serious bugs in NFS this week? Nice going guys! - mbuf leak (improper nfsrv_create error return) - packet size calculation (readdirplus on server side) - vnode locking (readdirplus on client side) - directory cnp (readdirplus on client side) -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 Thu Jul 29 23:47:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 2EC0D15275 for ; Thu, 29 Jul 1999 23:47:10 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.242]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2BE6 for ; Fri, 30 Jul 1999 08:45:18 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA01556 for current@freebsd.org; Fri, 30 Jul 1999 08:45:32 +0200 (CEST) (envelope-from asmodai) Date: Fri, 30 Jul 1999 08:45:32 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: Panic plus advice needed Message-ID: <19990730084532.B1396@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I started a make world on my box last night and then proceeded to go to bed. When I looked at my console this morning it had sprung into DDB because of a panic: ffs_alloccg: map corrupted. This panic occured on a box running pretty stable (at least panic less for the last past 4-8 weeks). I got show registers and trace information from DDB and also a crashdump. Now I am wanting to use GDB to get more relevant information from the crashdump. I have the GDB manual here, but could use some advice from people who've done this under FreeBSD before and could inform me of any things that are somewhat obligatory to look at under FreeBSD. If you want I can type in the DDB stuff later this day, but work awaits my presence first. Thanks for any advice. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 23:47:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 860BF15439 for ; Thu, 29 Jul 1999 23:47:13 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.242]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB2BE6 for ; Fri, 30 Jul 1999 08:45:19 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id IAA01549 for current@freebsd.org; Fri, 30 Jul 1999 08:41:27 +0200 (CEST) (envelope-from asmodai) Date: Fri, 30 Jul 1999 08:41:27 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: An oddity after a panic Message-ID: <19990730084127.A1396@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was cleansing /usr/obj after a panic to see if I could reproduce it and I have this slight oddity: [root@daemon:/usr/obj] (32) # rm -rf work/ rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty rm: work/FreeBSD/src/gnu: Directory not empty rm: work/FreeBSD/src: Directory not empty rm: work/FreeBSD: Directory not empty rm: work/: Directory not empty [note I already did chflags] [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll total 2 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../ [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd .. [root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll total 3 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../ 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/ I have no idea what's wrong here. After the panic however I did get some softupdates inconsistencies, such as: DUPs, Block counts, even an internal error: dups with -p. I'd love to hear some ideas about how to solve this. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jul 29 23:59:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id ADFD415439 for ; Thu, 29 Jul 1999 23:59:14 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id QAA07505; Fri, 30 Jul 1999 16:29:12 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id QAA57128; Fri, 30 Jul 1999 16:29:09 +0930 (CST) Date: Fri, 30 Jul 1999 16:29:09 +0930 From: Greg Lehey To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990730162908.B56925@freebie.lemis.com> References: <19990730084532.B1396@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990730084532.B1396@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Fri, Jul 30, 1999 at 08:45:32AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: > Hi, > > I started a make world on my box last night and then proceeded to go to bed. > > When I looked at my console this morning it had sprung into DDB because > of a panic: ffs_alloccg: map corrupted. > > This panic occured on a box running pretty stable (at least panic less for > the last past 4-8 weeks). > > I got show registers and trace information from DDB and also a crashdump. > Now I am wanting to use GDB to get more relevant information from the > crashdump. I have the GDB manual here, but could use some advice from > people who've done this under FreeBSD before and could inform me of any > things that are somewhat obligatory to look at under FreeBSD. > > If you want I can type in the DDB stuff later this day, but work awaits > my presence first. The first question is: do you have a kernel with debug symbols? If not, gdb isn't going to help you much. bde can do it with ddb (though it's a bit late if you have the dump), but mere mortals are in trouble without symbols. The first thing you should do with any dump is a backtrace (bt). The appearance depends on how you got there. Since you appear to have gone via ddb, your dump should look something like this: IdlePTD 3264512 initial pcb at 29dbc0 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x2fc fault code = supervisor read, page not present instruction pointer = 0x8:0xc011d71f stack pointer = 0x10:0xc74d3cc8 frame pointer = 0x10:0xc74d3ccc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 69 (pccardd) interrupt mask = net tty bio cam panic: from debugger panic: from debugger dumping to dev (3,1), offset 327808 dump 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:291 291 dumppcb.pcb_cr3 = rcr3(); This is where you are. You're in the dump routine. (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:291 #1 0xc014174d in panic (fmt=0xc024e3d4 "from debugger") at ../../kern/kern_shutdown.c:505 This is the panic call, from ddb. #2 0xc011e23d in db_panic (addr=-1072572641, have_addr=0, count=1, modif=0xc74d3b44 "") at ../../ddb/db_command.c:434 #3 0xc011e1dd in db_command (last_cmdp=0xc027bda8, cmd_table=0xc027bc08, aux_cmd_tablep=0xc029a834) at ../../ddb/db_command.c:334 #4 0xc011e2a2 in db_command_loop () at ../../ddb/db_command.c:456 #5 0xc0120327 in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 These frames relate to the debugger; they're not there if you panic and dump without entering ddb. #6 0xc021556c in kdb_trap (type=12, code=0, regs=0xc74d3c88) at ../../i386/i386/db_interface.c:157 #7 0xc02249cc in trap_fatal (frame=0xc74d3c88, eva=764) at ../../i386/i386/trap.c:902 #8 0xc02246a5 in trap_pfault (frame=0xc74d3c88, usermode=0, eva=764) at ../../i386/i386/trap.c:800 #9 0xc02242e7 in trap (frame={tf_fs = 16, tf_es = -1071710192, tf_ds = -65520, tf_edi = -1063317504, tf_esi = 0, tf_ebp = -951239476, tf_isp = -951239500, tf_ebx = -1063301376, tf_edx = -1063301372, tf_ecx = 744, tf_eax = 744, tf_trapno = 12, tf_err = 0, tf_eip = -1072572641, tf_cs = 8, tf_eflags = 66182, tf_esp = -1063301376, tf_ss = -951239332}) at ../../i386/i386/trap.c:426 The frames above are pretty much the same for all traps. #10 0xc011d71f in BUS_READ_IVAR (dev=0x2e8, child=0xc09f4f04, index=8, result=0xc74d3d3c) at bus_if.c:52 And this is where things really went crazy. From here on, your dump will look very different. This is where I'd expect to see the ffs_alloccg stack frame. The best thing to do there is to look at the local variables, which might give you more information. #11 0xc0246780 in sioprobe (dev=0xc09f4f04) at ../../isa/sio.c:599 #12 0xc024660d in sioinit (devi=0xc09f4f00) at ../../isa/sio.c:524 #13 0xc01cb8da in allocate_driver (slt=0xc0904600, desc=0xc09f1000) at ../../pccard/pccard.c:660 #14 0xc01cc156 in crdioctl (dev=0xc097a7e0, cmd=2158514182, data=0xc09f1000 "sio", fflag=3, p=0xc6d844c0) at ../../pccard/pccard.c:1061 #15 0xc0174428 in spec_ioctl (ap=0xc74d3e08) at ../../miscfs/specfs/spec_vnops.c:437 #16 0xc0173da9 in spec_vnoperate (ap=0xc74d3e08) at ../../miscfs/specfs/spec_vnops.c:128 #17 0xc01e45f5 in ufs_vnoperatespec (ap=0xc74d3e08) at ../../ufs/ufs/ufs_vnops.c:2334 #18 0xc016e681 in vn_ioctl (fp=0xc099ca40, com=2158514182, data=0xc09f1000 "sio", p=0xc6d844c0) at vnode_if.h:395 #19 0xc014ddc3 in ioctl (p=0xc6d844c0, uap=0xc74d3f80) at ../../kern/sys_generic.c:564 #20 0xc0224c36 in syscall (frame={tf_fs = -1078001617, tf_es = -1078001617, tf_ds = -1078001617, tf_edi = 0, tf_esi = 256, tf_ebp = -1077945096, tf_isp = -951238700, tf_ebx = 134635776, tf_edx = 8, tf_ecx = 3, tf_eax = 54, tf_trapno = 7, tf_err = 2, tf_eip = 134529928, tf_cs = 31, tf_eflags = 514, tf_esp = -1077945340, tf_ss = 47}) at ../../i386/i386/trap.c:1056 This is where the currently executing process entered the kernel (with an ioctl system call in this case). #21 0xc0215e66 in Xint0x80_syscall () #22 0x8048806 in ?? () #23 0x804861a in ?? () #24 0x80483b7 in ?? () #25 0x80480e9 in ?? () And this is the user context. With some difficulty you can load the symbol table for the binary and follow it back, but that doesn't help often. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:16: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 8ED0414BFE for ; Fri, 30 Jul 1999 00:16:04 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id AAA12928; Fri, 30 Jul 1999 00:12:04 -0700 (PDT) Message-Id: <199907300712.AAA12928@implode.root.com> To: Matthew Dillon Cc: Bill Paul , peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: readdirplus client side fix (was Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm) In-reply-to: Your message of "Thu, 29 Jul 1999 20:31:38 PDT." <199907300331.UAA81350@apollo.backplane.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 30 Jul 1999 00:12:04 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Look up a bit in the code. If bigenough is not true, cnp does not > get initialized. This could lead to the bogus length -- or rather, > it would be the cnp that is bogus, not the 'len'. > > The question is how to fix it. I think we can safely avoid doing the > cache_enter so try changing the 'if (doit)' to 'if (doit && bigenough)'. > I've included the patch below. ... > In order to accomplish this, the underlying vnode representing each > directory entry is retrieved and locked. However, there is a special > case: We *already* have a reference on the directory vnode itself, > and one of the directory entries, ".", will be the same vnode. Our > reference vnode, vp is *NOT* locked. In fact, we *can't* lock it > without creating a potential deadlock situation (at least that is my > take). I good bit of detective work...excellent job. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:29:18 1999 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 148F21574B for ; Fri, 30 Jul 1999 00:29:07 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id JAA47082; Fri, 30 Jul 1999 09:28:39 +0200 (CEST) (envelope-from des) To: David Scheidt Cc: "Daniel C. Sobral" , Peter Holm , Freebsd-current@FreeBSD.ORG Subject: Re: panic: softdep_flushfiles: looping References: From: Dag-Erling Smorgrav Date: 30 Jul 1999 09:28:38 +0200 In-Reply-To: David Scheidt's message of "Thu, 29 Jul 1999 14:45:24 -0500 (CDT)" Message-ID: Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt writes: > Six weeks, and no computer more sophisticated than the SCUBA one, are what > I remembered. Someone remind me what a vacation is again? des@flood ~% whatis vacation vacation(1) - return ``I am not here'' indication Apparently, it means he's not there. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:30:32 1999 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 15CA21567A for ; Fri, 30 Jul 1999 00:30:29 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id JAA47126; Fri, 30 Jul 1999 09:30:15 +0200 (CEST) (envelope-from des) To: "Marc Schneiders" Cc: "Malte Wedel" , Subject: Re: best time for cvsup? References: <99072916110300.27179@malte> <005b01beda26$3da0bfb0$0400000a@oldserver.demon.nl> From: Dag-Erling Smorgrav Date: 30 Jul 1999 09:30:15 +0200 In-Reply-To: "Marc Schneiders"'s message of "Fri, 30 Jul 1999 02:55:38 +0200" Message-ID: Lines: 14 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Marc Schneiders" writes: > > Are there any experiences at what time (UTC) the -current tree is most > stable? > I've had no problems so far some time after 0:00 h GMT, using the Dutch > mirror. I suppose you use the German one. Perhaps that is updated more > often. Considering that the FreeBSD developers are scattered around the globe, there's no "safe" time. And there's no guarantee that a bug introduced one day won't be there the next day, either. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:33:50 1999 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 E23DF1508B for ; Fri, 30 Jul 1999 00:33:47 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id JAA47154; Fri, 30 Jul 1999 09:31:15 +0200 (CEST) (envelope-from des) To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: An oddity after a panic References: <19990730084127.A1396@daemon.ninth-circle.org> From: Dag-Erling Smorgrav Date: 30 Jul 1999 09:31:15 +0200 In-Reply-To: Jeroen Ruigrok/Asmodai's message of "Fri, 30 Jul 1999 08:41:27 +0200" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai writes: > I'd love to hear some ideas about how to solve this. # chflags -R 0 /usr/obj/work # rm -rf /usr/obj/work DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:41: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 0126615676 for ; Fri, 30 Jul 1999 00:40:51 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA07697; Fri, 30 Jul 1999 17:10:00 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA57368; Fri, 30 Jul 1999 17:09:58 +0930 (CST) Date: Fri, 30 Jul 1999 17:09:58 +0930 From: Greg Lehey To: Jeroen Ruigrok/Asmodai , Dag-Erling Smorgrav Cc: current@FreeBSD.ORG Subject: Re: An oddity after a panic Message-ID: <19990730170958.C56925@freebie.lemis.com> References: <19990730084127.A1396@daemon.ninth-circle.org> <19990730084127.A1396@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990730084127.A1396@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Fri, Jul 30, 1999 at 08:41:27AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 30 July 1999 at 9:31:15 +0200, Dag-Erling Smorgrav wrote: > Jeroen Ruigrok/Asmodai writes: >> [note I already did chflags] >> I'd love to hear some ideas about how to solve this. > > # chflags -R 0 /usr/obj/work > # rm -rf /usr/obj/work That doesn't seem to be the answer. And the directory where the problem occurred doesn't normally get any schg flags set. On Friday, 30 July 1999 at 8:41:27 +0200, Jeroen Ruigrok/Asmodai wrote: > Hi, > > I was cleansing /usr/obj after a panic to see if I could reproduce it and > I have this slight oddity: > > [root@daemon:/usr/obj] (32) # rm -rf work/ > rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty > rm: work/FreeBSD/src/gnu: Directory not empty > rm: work/FreeBSD/src: Directory not empty > rm: work/FreeBSD: Directory not empty > rm: work/: Directory not empty > > [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll > total 2 > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../ > > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd .. > [root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll > total 3 > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../ > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/ That link count for usr.bin looks funny. It should be 2, and that's probably why you can't remove it. > I have no idea what's wrong here. > After the panic however I did get some softupdates inconsistencies, such > as: DUPs, Block counts, even an internal error: dups with -p. Yes, it looks like you have a broken file system. The easy part is to cut off the directory tree a bit further up (say, mv usr.bin to lost+found/andbroken). Actually getting rid of it and reclaiming any lost space will probably be more difficult and involve you in deeper knowledge of fsdb than you really wanted. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:48: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 036D41568E for ; Fri, 30 Jul 1999 00:47:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA02796; Fri, 30 Jul 1999 09:45:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Dag-Erling Smorgrav Cc: David Scheidt , "Daniel C. Sobral" , Peter Holm , Freebsd-current@FreeBSD.ORG Subject: Re: panic: softdep_flushfiles: looping In-reply-to: Your message of "30 Jul 1999 09:28:38 +0200." Date: Fri, 30 Jul 1999 09:45:15 +0200 Message-ID: <2794.933320715@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dag-Erling Smorgrav writes: >David Scheidt writes: >> Six weeks, and no computer more sophisticated than the SCUBA one, are what >> I remembered. Someone remind me what a vacation is again? > >des@flood ~% whatis vacation >vacation(1) - return ``I am not here'' indication > >Apparently, it means he's not there. You got that wrong: It said he's not *here*, so unless he has disappeared there is a very good chance that he is *there*, wherever that is. Probably out in the big coloured room somewhere... Can we please stop this thread now ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 0:53:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles548.castles.com [208.214.165.112]) by hub.freebsd.org (Postfix) with ESMTP id 81BFB15697 for ; Fri, 30 Jul 1999 00:53:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA01123; Fri, 30 Jul 1999 00:48:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907300748.AAA01123@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: APM related panic In-reply-to: Your message of "Thu, 29 Jul 1999 23:43:26 +0300." <37A0BCEE.6A8B01F1@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jul 1999 00:48:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just suped and builded new kernel and discovered that it paniced when > trying to initialise APM (VIA MVP3 based Tyan Trinity 100AT motherboard > + k6-II/300 CPU). Any ideas or recommendations about what should I do to > make a more informative report? Just the usual ones; full text of the panic message and anything leading up to it, traceback from ddb. Also check that your BIOS is up to date. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 1:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id E079B156C1 for ; Fri, 30 Jul 1999 01:12:49 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id EAA10892; Fri, 30 Jul 1999 04:13:40 -0400 (EDT) Date: Fri, 30 Jul 1999 04:13:39 -0400 (EDT) From: Alfred Perlstein To: Greg Lehey Cc: Jeroen Ruigrok/Asmodai , Dag-Erling Smorgrav , current@FreeBSD.ORG Subject: Re: An oddity after a panic In-Reply-To: <19990730170958.C56925@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Jul 1999, Greg Lehey wrote: > On Friday, 30 July 1999 at 9:31:15 +0200, Dag-Erling Smorgrav wrote: > > Jeroen Ruigrok/Asmodai writes: > >> [note I already did chflags] > >> I'd love to hear some ideas about how to solve this. > > > > # chflags -R 0 /usr/obj/work > > # rm -rf /usr/obj/work > > That doesn't seem to be the answer. And the directory where the > problem occurred doesn't normally get any schg flags set. > > On Friday, 30 July 1999 at 8:41:27 +0200, Jeroen Ruigrok/Asmodai wrote: > > Hi, > > > > I was cleansing /usr/obj after a panic to see if I could reproduce it and > > I have this slight oddity: > > > > [root@daemon:/usr/obj] (32) # rm -rf work/ > > rm: work/FreeBSD/src/gnu/usr.bin/: Directory not empty > > rm: work/FreeBSD/src/gnu: Directory not empty > > rm: work/FreeBSD/src: Directory not empty > > rm: work/FreeBSD: Directory not empty > > rm: work/: Directory not empty > > > > [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ > > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll > > total 2 > > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ../ > > > > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (35) # cd .. > > [root@daemon:/usr/obj/work/FreeBSD/src/gnu] (36) # ll > > total 3 > > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ > > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:33 ../ > > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 usr.bin/ > > That link count for usr.bin looks funny. It should be 2, and that's > probably why you can't remove it. > > > I have no idea what's wrong here. > > After the panic however I did get some softupdates inconsistencies, such > > as: DUPs, Block counts, even an internal error: dups with -p. > > Yes, it looks like you have a broken file system. The easy part is to > cut off the directory tree a bit further up (say, mv usr.bin to > lost+found/andbroken). Actually getting rid of it and reclaiming any > lost space will probably be more difficult and involve you in deeper > knowledge of fsdb than you really wanted. I've seen this happen with a DPT controller and regular scsi when under a lot of I/O load for long periods of time, you'll definetly want to use fsdb to ditch the dir, however if you root around in there it'd be great to see the values in the inodes pointed to by usr.bin and the "." and ".." entries contained within. It doesn't seem possible, but when I had this unreoveable directory problem one of the inode's fields had overflowed to some ridiculously high (or negative) number. -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Wintelcom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 1:39:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 3944914CC7 for ; Fri, 30 Jul 1999 01:39:30 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA05824; Fri, 30 Jul 1999 10:38:29 +0200 (MET DST) Date: Fri, 30 Jul 1999 10:38:27 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Dag-Erling Smorgrav Cc: Marc Schneiders , Malte Wedel , freebsd-current@FreeBSD.ORG Subject: Re: best time for cvsup? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Most active committers are in the States if you look at the frequency of commit messages. The European morning is the safest I guess. Nick On 30 Jul 1999, Dag-Erling Smorgrav wrote: > "Marc Schneiders" writes: > > > Are there any experiences at what time (UTC) the -current tree is most > > stable? > > I've had no problems so far some time after 0:00 h GMT, using the Dutch > > mirror. I suppose you use the German one. Perhaps that is updated more > > often. > > Considering that the FreeBSD developers are scattered around the > globe, there's no "safe" time. And there's no guarantee that a bug > introduced one day won't be there the next day, either. > > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 2: 6:55 1999 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 27DD314D94 for ; Fri, 30 Jul 1999 02:06:47 -0700 (PDT) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.1) id LAA49477; Fri, 30 Jul 1999 11:05:35 +0200 (CEST) (envelope-from des) To: Nick Hibma Cc: Dag-Erling Smorgrav , Marc Schneiders , Malte Wedel , freebsd-current@FreeBSD.ORG Subject: Re: best time for cvsup? References: From: Dag-Erling Smorgrav Date: 30 Jul 1999 11:05:34 +0200 In-Reply-To: Nick Hibma's message of "Fri, 30 Jul 1999 10:38:27 +0200 (MET DST)" Message-ID: Lines: 11 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > Most active committers are in the States if you look at the frequency of > commit messages. > > The European morning is the safest I guess. Not if I'm within reach of an Internet connection ;) DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 2:39:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles548.castles.com [208.214.165.112]) by hub.freebsd.org (Postfix) with ESMTP id 9680C150A7 for ; Fri, 30 Jul 1999 02:39:56 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id CAA02191; Fri, 30 Jul 1999 02:34:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907300934.CAA02191@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: MTRR stuff In-reply-to: Your message of "Fri, 09 Jul 1999 10:32:37 +0800." <199907090232.KAA04002@ariadne.tensor.pgs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jul 1999 02:34:34 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For some video cards (to wit, the voodoo stuff), the MTRRs should be set up as > follows > > write-combining > +----------------------------------------------------------+ > +-------+ > uncacheable > > i.e. the two regions have the same starting area, but the small chunk for the > registers should be uncacheable. When I try to do this using memconf on my > K6-2, it spits the dummy. Is there a work around for this? The i686 MTRR implementation, at least, doesn't allow UC to overlap WC; only Write-back and uncached are allowed to overlap. I don't know what the K6's limitations are; you should talk to Brian Feldman about that. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 8:29:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DBF0014BE4 for ; Fri, 30 Jul 1999 08:29:36 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA01457; Fri, 30 Jul 1999 11:28:38 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Fri, 30 Jul 1999 11:28:35 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Mike Smith Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.org Subject: Re: MTRR stuff In-Reply-To: <199907300934.CAA02191@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 30 Jul 1999, Mike Smith wrote: > > For some video cards (to wit, the voodoo stuff), the MTRRs should be set up as > > follows > > > > write-combining > > +----------------------------------------------------------+ > > +-------+ > > uncacheable > > > > i.e. the two regions have the same starting area, but the small chunk for the > > registers should be uncacheable. When I try to do this using memconf on my > > K6-2, it spits the dummy. Is there a work around for this? > > The i686 MTRR implementation, at least, doesn't allow UC to overlap WC; > only Write-back and uncached are allowed to overlap. I don't know what > the K6's limitations are; you should talk to Brian Feldman about that. As long as a range isn't exactly the same (base, len being the same), it allows the change. The question is how does it fail? I let the hardware decide what to actually do with the registers, but I write them, so... I need to know where the problem is. > > -- > \\ The mind's the standard \\ Mike Smith > \\ of the man. \\ msmith@freebsd.org > \\ -- Joseph Merrick \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@FreeBSD.org _ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \._ \ |) | http://www.FreeBSD.org/ _ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 9: 8:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mout0.01019freenet.de (mout0.01019freenet.de [62.104.201.5]) by hub.freebsd.org (Postfix) with ESMTP id 5B8C6156FE for ; Fri, 30 Jul 1999 09:07:59 -0700 (PDT) (envelope-from malte@isoc.de) Received: from [62.104.201.2] (helo=mx1.01019freenet.de) by mout0.01019freenet.de with esmtp (Exim 3.02 #10) id 11AFAT-00071L-00 for freebsd-current@freebsd.org; Fri, 30 Jul 1999 18:05:57 +0200 Received: from [212.81.168.149] (helo=isoc.de) by mx1.01019freenet.de with esmtp (Exim 3.02 #10) id 11AFAS-0004Aw-00 for freebsd-current@freebsd.org; Fri, 30 Jul 1999 18:05:56 +0200 Message-ID: <37A1E99B.449FB21C@isoc.de> Date: Fri, 30 Jul 1999 18:06:19 +0000 From: malte X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: make world still broken? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get this error on "make world" with the latest sources. it is still broken, or do I have another problem? malte cc -O -pipe -I/usr/src/gnu/usr.bin/ld -I/usr/src/gnu/usr.bin/ld/../../../libexec/rtld-aout -I/usr/src/gnu/usr.bin/ld/../../../libexec/rtld-aout/i386 -I/usr/src/gnu/usr.bin/ld/../../../contrib/egcs/gcc -DIN_GCC -DDEMANGLE_CPLUSPLUS -DFREEBSD_AOUT -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/ld/../../../libexec/rtld-aout/shlib.c In file included from /usr/src/gnu/usr.bin/ld/../../../libexec/rtld-aout/shlib.c:33: /usr/obj/usr/src/tmp/usr/include/sys/param.h:56: sy: No such file or directory In file included from /usr/obj/usr/src/tmp/usr/include/sys/param.h:90, from /usr/src/gnu/usr.bin/ld/../../../libexec/rtld-aout/shlib.c:33: /usr/obj/usr/src/tmp/usr/include/sys/signal.h:217: parse error before `size_t' /usr/obj/usr/src/tmp/usr/include/sys/signal.h:217: warning: no semicolon at end of struct or union /usr/obj/usr/src/tmp/usr/include/sys/signal.h:219: parse error before `}' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 11: 0:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-2.uoregon.edu (metriclient-2.uoregon.edu [128.223.172.2]) by hub.freebsd.org (Postfix) with ESMTP id C64C8151A4 for ; Fri, 30 Jul 1999 11:00:18 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-2.uoregon.edu (8.9.1/8.8.7) id KAA11458; Fri, 30 Jul 1999 10:59:39 -0700 (PDT) Message-ID: <19990730105939.41269@hydrogen.fircrest.net> Date: Fri, 30 Jul 1999 10:59:39 -0700 From: John-Mark Gurney To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: An oddity after a panic References: <19990730084127.A1396@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19990730084127.A1396@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Fri, Jul 30, 1999 at 08:41:27AM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai scribbled this message on Jul 30: > [root@daemon:/usr/obj] (33) # cd work/FreeBSD/src/gnu/usr.bin/ > [root@daemon:/usr/obj/work/FreeBSD/src/gnu/usr.bin] (34) # ll > total 2 > 1 drwxr-xr-x 3 root wheel - 512 Jul 30 08:31 ./ ^ that is your problem, this should be 2 not 3... rerun fsck on it manually... if it doesn't fix the problem... use fsdb to unlink this directory, and then run fsck, it should dump the directory (or put it in lost+found)... you can also use fsdb to reduce the link count to 2 so you can rmdir it... -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 11: 4:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from storm.FreeBSD.org.uk (storm.freebsd.org.uk [194.242.128.198]) by hub.freebsd.org (Postfix) with ESMTP id 7D88E151E4 for ; Fri, 30 Jul 1999 11:04:36 -0700 (PDT) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by storm.FreeBSD.org.uk (8.9.3/8.9.3) with ESMTP id TAA33936; Fri, 30 Jul 1999 19:04:22 +0100 (BST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id TAA04686; Fri, 30 Jul 1999 19:05:10 +0100 (BST) (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199907301805.TAA04686@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Nick Hibma Cc: Dag-Erling Smorgrav , Marc Schneiders , Malte Wedel , freebsd-current@FreeBSD.ORG Subject: Re: best time for cvsup? In-reply-to: Your message of "Fri, 30 Jul 1999 10:38:27 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Jul 1999 19:05:10 +0100 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nick.hibma@jrc.it said: > Most active committers are in the States if you look at the frequency > of commit messages. > The European morning is the safest I guess. 'till you get to build ppp and bump into the cr*p I committed at 4:30 the night before when I should have been asleep :-] -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 11:25:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (Postfix) with SMTP id 4813915154 for ; Fri, 30 Jul 1999 11:25:06 -0700 (PDT) (envelope-from geoff@rucus.ru.ac.za) Received: (qmail 99103 invoked by uid 268); 30 Jul 1999 18:25:33 -0000 Message-ID: <19990730182533.99101.qmail@rucus.ru.ac.za> Subject: Re: best time for cvsup? In-Reply-To: from Dag-Erling Smorgrav at "Jul 30, 1999 11: 5:34 am" To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Date: Fri, 30 Jul 1999 20:25:33 +0200 (SAST) Cc: current@freebsd.org Reply-To: "Geoff Rehmet" From: "Geoff Rehmet" X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dag-Erling Smorgrav writes : > Nick Hibma writes: > > Most active committers are in the States if you look at the frequency of > > commit messages. > > > > The European morning is the safest I guess. > > Not if I'm within reach of an Internet connection ;) Back in the days of version 1.1, the tree was often broken in the European / South African morning, which meant that a I was sometimes doing patches before a make world would work again. I think the maturity of the FreeBSD development process has changed somewhat since then. :-) Geoff. -- Geoff Rehmet, The Internet Solution geoffr@is.co.za; geoff@rucus.ru.ac.za; csgr@freebsd.org tel: +27-83-292-5800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 13:16:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.palmerharvey.co.uk (mail.palmerharvey.co.uk [62.172.109.58]) by hub.freebsd.org (Postfix) with ESMTP id A3959152FA for ; Fri, 30 Jul 1999 13:15:53 -0700 (PDT) (envelope-from Dom.Mitchell@palmerharvey.co.uk) Received: from ho-nt-01.pandhm.co.uk (unverified) by mail.palmerharvey.co.uk (Content Technologies SMTPRS 2.0.15) with ESMTP id ; Fri, 30 Jul 1999 21:13:03 +0100 Received: from voodoo.pandhm.co.uk (VOODOO [10.100.35.12]) by ho-nt-01.pandhm.co.uk with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PJ2VDZMM; Fri, 30 Jul 1999 21:13:01 +0100 Received: from dom by voodoo.pandhm.co.uk with local (Exim 2.10 #1) id 11AJ1Z-000OTX-00; Fri, 30 Jul 1999 21:13:01 +0100 Date: Fri, 30 Jul 1999 21:13:01 +0100 To: Brian Somers Cc: Nick Hibma , Dag-Erling Smorgrav , Marc Schneiders , Malte Wedel , freebsd-current@FreeBSD.ORG Subject: Re: best time for cvsup? Message-Id: <19990730211301.A94067@voodoo.pandhm.co.uk> References: <199907301805.TAA04686@keep.lan.Awfulhak.org> MIME-Version: 1.0 X-Mailer: Mutt 0.95.6i In-Reply-To: <199907301805.TAA04686@keep.lan.Awfulhak.org>; from Brian Somers on Fri, Jul 30, 1999 at 07:05:10PM +0100 From: Dominic Mitchell Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jul 30, 1999 at 07:05:10PM +0100, Brian Somers wrote: > nick.hibma@jrc.it said: > > Most active committers are in the States if you look at the frequency > > of commit messages. > > > The European morning is the safest I guess. > > 'till you get to build ppp and bump into the cr*p I committed at 4:30 > the night before when I should have been asleep :-] Yeah, and you won't be able to cvsup again, coz ppp's broke. ;-P -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator In Mountain View did Larry Wall Sedately launch a quiet plea: That DOS, the ancient system, shall On boxes pleasureless to all Run Perl though lack they C. -- ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 14:18:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id 12BF9151FA for ; Fri, 30 Jul 1999 14:18:46 -0700 (PDT) (envelope-from staylor@mrynet.com) Received: (from staylor@localhost) by mrynet.com (8.9.3/8.9.3) id OAA28740 for freebsd-current@freebsd.org; Fri, 30 Jul 1999 14:18:35 -0700 (PDT) (envelope-from staylor) Posted-Date: Fri, 30 Jul 1999 14:18:35 -0700 (PDT) Message-Id: <199907302118.OAA28740@mrynet.com> From: staylor@mrynet.com (S. Akmentins-Teilors) Date: Fri, 30 Jul 1999 14:18:35 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: WORLD hoseage with /usr/src/usr.sbin/apm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To wit: (CVSUP'd just prior to the world) ===> usr.sbin/apm cc -O -pipe -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/apm/apm.c gzip -cn /usr/src/usr.sbin/apm/apm.8 > apm.8.gz /usr/src/usr.sbin/apm/apm.c: In function `print_all_info': /usr/src/usr.sbin/apm/apm.c:112: storage size of `args' isn't known /usr/src/usr.sbin/apm/apm.c: In function `apm_set_timer': /usr/src/usr.sbin/apm/apm.c:269: storage size of `args' isn't known *** Error code 1 (followed-up with another CVSUP an hour later directly from cvsup.freebsd.org) (same error as above) mrynet# head -112 apm.c | tail -1 struct apm_bios_arg args; mrynet# head -269 apm.c | tail -1 struct apm_bios_arg args; mrynet# find /sys/ -type f -exec grep apm_bios_arg \{\} \; -print struct apm_bios_arg args; struct apm_bios_arg args; /usr/src/usr.sbin/apm/apm.c mrynet# Apparently, apm_bios_arg isn't defined anywhere. regards, -skots -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@idt.net, staylor@mrynet.lv Westlake Village, CA USA (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 14:23:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id 53F0E15247 for ; Fri, 30 Jul 1999 14:23:29 -0700 (PDT) (envelope-from staylor@mrynet.com) Received: (from root@localhost) by mrynet.com (8.9.3/8.9.3) id OAA28782 for freebsd-current@freebsd.org; Fri, 30 Jul 1999 14:22:56 -0700 (PDT) (envelope-from staylor) Posted-Date: Fri, 30 Jul 1999 14:22:56 -0700 (PDT) Message-Id: <199907302122.OAA28782@mrynet.com> From: staylor@mrynet.com (S. Akmentins-Teilors) Date: Fri, 30 Jul 1999 14:22:56 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: Re: WORLD hoseage with /usr/src/usr.sbin/apm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > mrynet# find /sys/ -type f -exec grep apm_bios_arg \{\} \; -print > struct apm_bios_arg args; > struct apm_bios_arg args; > /usr/src/usr.sbin/apm/apm.c > mrynet# The actual directory searched there was "/usr/src" FYI. Not /sys. I edited in a repaste of a second find. -skots -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@idt.net, staylor@mrynet.lv Westlake Village, CA USA (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 15:20:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id CF10A1571E for ; Fri, 30 Jul 1999 15:20:31 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.83]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB6B41; Sat, 31 Jul 1999 00:20:07 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA19472; Sat, 31 Jul 1999 00:03:11 +0200 (CEST) (envelope-from asmodai) Date: Sat, 31 Jul 1999 00:03:10 +0200 From: Jeroen Ruigrok/Asmodai To: John-Mark Gurney , Dag-Erling Smorgrav , Alfred Perlstein , Greg Lehey Cc: current@freebsd.org Subject: An oddity after a panic Message-ID: <19990731000310.E4337@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to you all for the hints and tips... I finally solved it by wanting to run fsck again before messing around with fsdb and stat. I shutdown'd, went into single user mode, fsck'd my slice and the problem got fixed. Hmmmm, gotta love FFS =) Thanks 'gain, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 15:20:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (Postfix) with ESMTP id 6497815733 for ; Fri, 30 Jul 1999 15:20:30 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.83]) by smtp03.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6B41; Sat, 31 Jul 1999 00:20:06 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id AAA22863; Sat, 31 Jul 1999 00:19:28 +0200 (CEST) (envelope-from asmodai) Date: Sat, 31 Jul 1999 00:19:27 +0200 From: Jeroen Ruigrok/Asmodai To: Greg Lehey Cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990731001927.A21870@daemon.ninth-circle.org> References: <19990730084532.B1396@daemon.ninth-circle.org> <19990730162908.B56925@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990730162908.B56925@freebie.lemis.com>; from Greg Lehey on Fri, Jul 30, 1999 at 04:29:09PM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey (grog@lemis.com) [990730 11:23]: > On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: > > I started a make world on my box last night and then proceeded to go to bed. > > > > When I looked at my console this morning it had sprung into DDB because > > of a panic: ffs_alloccg: map corrupted. > > The first question is: do you have a kernel with debug symbols? If > not, gdb isn't going to help you much. bde can do it with ddb (though > it's a bit late if you have the dump), but mere mortals are in trouble > without symbols. I thought I had one, but alas I didn't. *sigh* One of those days when ye bump against stuff you should've done. Learned from that in a multiple ways, so next time I got everything I need... > The first thing you should do with any dump is a backtrace (bt). The > appearance depends on how you got there. Since you appear to have > gone via ddb, your dump should look something like this: Here is at least some info: (kgdb) bt #0 0xc0155f14 in boot () #1 0xc0156249 in panic () #2 0xc01e737b in ffs_mapsearch () #3 0xc01e5cea in ffs_alloccg () #4 0xc01e5756 in ffs_hashalloc () #5 0xc01e4adc in ffs_alloc () #6 0xc01e7af0 in ffs_balloc () #7 0xc01f0a5c in ffs_write () #8 0xc01827ce in vn_write () #9 0xc01623ac in dofilewrite () #10 0xc01622bb in write () #11 0xc0225066 in syscall () #12 0xc02192b6 in Xint0x80_syscall () #13 0x807d24a in ?? () #14 0x807666d in ?? () Think I'll read up on GDB in my printed manual... Other hints/tips still welcome, I still have the dumps =) -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 16: 7:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 742A014F86 for ; Fri, 30 Jul 1999 16:07:44 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id IAA13552; Sat, 31 Jul 1999 08:37:02 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA64402; Sat, 31 Jul 1999 08:37:01 +0930 (CST) Date: Sat, 31 Jul 1999 08:37:01 +0930 From: Greg Lehey To: Jeroen Ruigrok/Asmodai Cc: John-Mark Gurney , Dag-Erling Smorgrav , Alfred Perlstein , current@freebsd.org Subject: Re: An oddity after a panic Message-ID: <19990731083701.J56925@freebie.lemis.com> References: <19990731000310.E4337@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990731000310.E4337@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Sat, Jul 31, 1999 at 12:03:10AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 31 July 1999 at 0:03:10 +0200, Jeroen Ruigrok/Asmodai wrote: > Thanks to you all for the hints and tips... > > I finally solved it by wanting to run fsck again before messing around > with fsdb and stat. Yes, it occurred to me that fsck should find an incorrect link count. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 16:33:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id AAC4D14D28; Fri, 30 Jul 1999 16:33:33 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-28.iptelecom.net.ua [212.42.69.219]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id CAA22284; Sat, 31 Jul 1999 02:38:38 +0300 (EEST) Message-ID: <37A22819.DD36695B@altavista.net> Date: Sat, 31 Jul 1999 01:32:57 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG, Mike Smith Subject: Re: APM related panic References: <37A0BCEE.6A8B01F1@altavista.net> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Finally I back from my work, suped, builded kernel with APM_DEBUG and managed to get my computer booted using serial console, however due to unknown for me problem it works only in one direction, i.e. I see boot messages on my notebook, but when I press any key on it it has absolutely no effect. Also after panic cu on notebook is hanging, so I have to kill it. Following is the log, bit if you think that it is not sufficien and I could do something more to shade light on this proble please do not hesitate to contact me. -Maxim Script started on Sat Jul 31 00:56:04 1999 sh-2.03# cu -l '/dev/cuaa0' Connected. Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.7 640/64448kB (root@home, Sun Jul 25 04:04:09 EEST 1999) Booting [kernel]... Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Jul 31 00:29:40 EEST 1999 root@home:/usr/src/sys/compile/MBSD Timecounter "i8254" frequency 1193027 Hz CPU: AMD-K6(tm) 3D processor (300.64-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 67043328 (65472K bytes) avail memory = 62607360 (61140K bytes) Preloaded elf kernel "kernel" at 0xc0265000. Probing for PnP devices: CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1013c276 Comp ID: PNP0600 [0x0006d041] npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f0000, Data 0xc00fdfa0 apm: Code entry 0x00008010, Idling CPU enabled, Management enabled apm: CS_limit=0x0, DS_limit=0x0 Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x48:0x8034 stack pointer = 0x10:0xc0279e98 frame pointer = 0x10:0x67890000 code segment = base 0xc00f0000, limit 0xffff, type 0x1b = DPL 0, pres 1, def32 1, gran 0 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (swapper) interrupt mask = net tty bio cam trap number = 9 panic: general protection fault Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cu: Got termination signal Killed sh-2.03# exit Script done on Sat Jul 31 00:57:46 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 16:33:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 02CB51577C for ; Fri, 30 Jul 1999 16:33:48 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA13606; Sat, 31 Jul 1999 09:02:42 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA64450; Sat, 31 Jul 1999 09:02:37 +0930 (CST) Date: Sat, 31 Jul 1999 09:02:37 +0930 From: Greg Lehey To: Jeroen Ruigrok/Asmodai Cc: current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990731090236.K56925@freebie.lemis.com> References: <19990730084532.B1396@daemon.ninth-circle.org> <19990730162908.B56925@freebie.lemis.com> <19990731001927.A21870@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19990731001927.A21870@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Sat, Jul 31, 1999 at 12:19:27AM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 31 July 1999 at 0:19:27 +0200, Jeroen Ruigrok/Asmodai wrote: > * Greg Lehey (grog@lemis.com) [990730 11:23]: >> On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: > >>> I started a make world on my box last night and then proceeded to go to bed. >>> >>> When I looked at my console this morning it had sprung into DDB because >>> of a panic: ffs_alloccg: map corrupted. >> >> The first question is: do you have a kernel with debug symbols? If >> not, gdb isn't going to help you much. bde can do it with ddb (though >> it's a bit late if you have the dump), but mere mortals are in trouble >> without symbols. > > I thought I had one, but alas I didn't. *sigh* One of those days when ye > bump against stuff you should've done. Learned from that in a multiple > ways, so next time I got everything I need... That's why I tried a few months back to make debug symbols the default. >> The first thing you should do with any dump is a backtrace (bt). The >> appearance depends on how you got there. Since you appear to have >> gone via ddb, your dump should look something like this: > > Here is at least some info: > > (kgdb) bt > #0 0xc0155f14 in boot () > #1 0xc0156249 in panic () > #2 0xc01e737b in ffs_mapsearch () > #3 0xc01e5cea in ffs_alloccg () > #4 0xc01e5756 in ffs_hashalloc () > #5 0xc01e4adc in ffs_alloc () > #6 0xc01e7af0 in ffs_balloc () > #7 0xc01f0a5c in ffs_write () > #8 0xc01827ce in vn_write () > #9 0xc01623ac in dofilewrite () > #10 0xc01622bb in write () > #11 0xc0225066 in syscall () > #12 0xc02192b6 in Xint0x80_syscall () > #13 0x807d24a in ?? () > #14 0x807666d in ?? () Hmm, that doesn't look like a dump from ddb. Did you have DDB_UNATTENDED set? > Think I'll read up on GDB in my printed manual... > > Other hints/tips still welcome, I still have the dumps =) OK, you have the stack frame. The panic name appears wrong; it's out of ffs_mapsearch, not ffs_alloccg. Anyway, ffs_mapsearch looks like this: static ufs_daddr_t ffs_mapsearch(fs, cgp, bpref, allocsiz) register struct fs *fs; register struct cg *cgp; ufs_daddr_t bpref; int allocsiz; { ufs_daddr_t bno; int start, len, loc, i; int blk, field, subfield, pos; At a first glance, it would seem that what you want to look at is *cgp, which is stored at a fixed location from the stack frame (%ebp+0xc). You could enter something like (kgdb) f 2 (kgdb) x/30x *(int*)($ebp+0xc) This should give you the first 30 ints of the cylinder group. If you had symbols, this would be quite a bit simpler: (kgdb) p *cgp What you do with the results depends a lot on what you find. On the whole, I wouldn't think it worth the pain of debugging without symbols. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jul 30 22: 1:29 1999 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5772814D32 for ; Fri, 30 Jul 1999 22:01:18 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.1) with ESMTP id VAA24304; Fri, 30 Jul 1999 21:59:58 -0700 (PDT) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA97970; Fri, 30 Jul 1999 21:59:57 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19990729202434.A78719@daemon.ninth-circle.org> Date: Fri, 30 Jul 1999 21:59:57 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Jeroen Ruigrok/Asmodai Subject: Re: Library question/challenge Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > * John Polstra (jdp@polstra.com) [990729 18:49]: >> >> Right. So the problem must be that you have LD_LIBRARY_PATH set. > > Yes I have, but this hasn't been a problem for the last 5-6 months. > In what way could it interfere with my ldconfig then? (I read man 1aout ld) It won't intefere with ldconfig, but it will affect what the dynamic linker does. If you have "/usr/lib" in your LD_LIBRARY_PATH then the dynamic linker will find libc there, rather than in "/usr/lib/aout" as it should. I don't know why it didn't cause problems for you earlier. This was netscape, right? If so, there's an easy fix. The command that you execute for netscape is really a shell script which does some stuff and then executes a big binary somewhere else. You could add "unset LD_LIBRARY_PATH" to that shell script to work around the problem. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 3:32:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 3006A14D22 for ; Sat, 31 Jul 1999 03:32:20 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.72]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA2464; Sat, 31 Jul 1999 12:30:25 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA58929; Sat, 31 Jul 1999 12:22:03 +0200 (CEST) (envelope-from asmodai) Date: Sat, 31 Jul 1999 12:22:02 +0200 From: Jeroen Ruigrok/Asmodai To: John Polstra Cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Library question/challenge Message-ID: <19990731122202.D378@daemon.ninth-circle.org> References: <19990729202434.A78719@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from John Polstra on Fri, Jul 30, 1999 at 09:59:57PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * John Polstra (jdp@polstra.com) [990731 09:28]: > Jeroen Ruigrok/Asmodai wrote: > > * John Polstra (jdp@polstra.com) [990729 18:49]: > >> > >> Right. So the problem must be that you have LD_LIBRARY_PATH set. > > > > Yes I have, but this hasn't been a problem for the last 5-6 months. > > In what way could it interfere with my ldconfig then? (I read man 1aout ld) > > It won't intefere with ldconfig, but it will affect what the dynamic > linker does. If you have "/usr/lib" in your LD_LIBRARY_PATH then the > dynamic linker will find libc there, rather than in "/usr/lib/aout" as > it should. Ah, ok, I was thinking in the wrong direction. The main reason I stuck LD_LIBRARY_PATH in there is because of Qt. If ldconfig paths are configured ok, will these replace LD_LIBRARY_PATH or would I have to adjust Makefiles/configures in order to point to the libraries present on this system? > I don't know why it didn't cause problems for you earlier. Well, I am glad it broke... Because else I would still be using this. > This was netscape, right? If so, there's an easy fix. The command > that you execute for netscape is really a shell script which does > some stuff and then executes a big binary somewhere else. You could > add "unset LD_LIBRARY_PATH" to that shell script to work around the > problem. Mayhaps, but I would rather tackle the whole of this challenge instead of just a subset. I mean if this LD_LIBRARY_PATH I set is a bad thing to do I want to learn the ways how to best do it instead. -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 3:32:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id F1D0714D41 for ; Sat, 31 Jul 1999 03:32:22 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.72]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAB2464; Sat, 31 Jul 1999 12:30:26 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id MAA58494; Sat, 31 Jul 1999 12:14:43 +0200 (CEST) (envelope-from asmodai) Date: Sat, 31 Jul 1999 12:14:42 +0200 From: Jeroen Ruigrok/Asmodai To: Greg Lehey Cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990731121442.C378@daemon.ninth-circle.org> References: <19990730084532.B1396@daemon.ninth-circle.org> <19990730162908.B56925@freebie.lemis.com> <19990731001927.A21870@daemon.ninth-circle.org> <19990731090236.K56925@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <19990731090236.K56925@freebie.lemis.com>; from Greg Lehey on Sat, Jul 31, 1999 at 09:02:37AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey (grog@lemis.com) [990731 03:50]: > On Saturday, 31 July 1999 at 0:19:27 +0200, Jeroen Ruigrok/Asmodai wrote: > > * Greg Lehey (grog@lemis.com) [990730 11:23]: > >> On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote: > >> The first thing you should do with any dump is a backtrace (bt). The > >> appearance depends on how you got there. Since you appear to have > >> gone via ddb, your dump should look something like this: > > > > (kgdb) bt > > #0 0xc0155f14 in boot () > > #1 0xc0156249 in panic () > > #2 0xc01e737b in ffs_mapsearch () > > #3 0xc01e5cea in ffs_alloccg () > > #4 0xc01e5756 in ffs_hashalloc () > > #5 0xc01e4adc in ffs_alloc () > > #6 0xc01e7af0 in ffs_balloc () > > #7 0xc01f0a5c in ffs_write () > > #8 0xc01827ce in vn_write () > > #9 0xc01623ac in dofilewrite () > > #10 0xc01622bb in write () > > #11 0xc0225066 in syscall () > > #12 0xc02192b6 in Xint0x80_syscall () > > #13 0x807d24a in ?? () > > #14 0x807666d in ?? () > > Hmm, that doesn't look like a dump from ddb. Did you have > DDB_UNATTENDED set? No, just options DDB. This bt was obtained after doing gdb -k kernel.0 vmcore.0 I still have the DDB trace on paper which I can type in if needed/wanted. > What you do with the results depends a lot on what you find. On the > whole, I wouldn't think it worth the pain of debugging without > symbols. No it isn't... I just made world and am building two kernels now (one with and one without debug info) so that the next time something happens like that I am prepared. Thanks anyways for the help Greg, this will surely help some parts of the PDP, hope I get some stuff in there about this sort of thing today. 'gards, -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 6:42:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 6F2B614F17 for ; Sat, 31 Jul 1999 06:42:26 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id WAA13178; Sat, 31 Jul 1999 22:41:34 +0900 (JST) Message-ID: <37A2FAF3.8ACE116E@newsguy.com> Date: Sat, 31 Jul 1999 22:32:35 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.6 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Nicolai Petri Cc: current@FreeBSD.ORG Subject: Re: kldload (module parameters ??) References: <002201bea9b1$f0772c00$6535a8c0@petri> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolai Petri wrote: > > Would it be possible and wise to implement a way to pass parameters to > modules when they are loaded ?? Like "kldload if_olp -recv_debug" ? This message might be over two months old, but hey... :-) Modules can receive parameters when loaded through loader(8). It would make sense that this capability were also present on kldload. One good reason not to do it this way: we want modules to be loadable-on-demand. Of course, there are all sorts of modules that wouldn't make sense to be demand-loadable, and, thus, would be perfectly all right with parameters. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org - Jordan, God, what's the difference? - God doesn't belong to the -core. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 6:57:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 28D4E14FED for ; Sat, 31 Jul 1999 06:57:42 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id PAA02838 for ; Sat, 31 Jul 1999 15:57:26 +0200 (CEST) Date: Sat, 31 Jul 1999 15:57:26 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Subject: network got stuck during high nfs-load Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi driver gurus, Today I had heavy NFS-load on my CURRENT-SMP machine while compiling world. Suddenly all NFS-Clients stopped working. I was't able to ping the server from inside my /29 subnet, same with ping the others from the server itself. I changed cables, plugged them in and out, did some ifconfig up down, deleted routes and added them again ... nothing. But the card was still sending from time to time (once a second) with 100% load many 0 bytes - like some waves: (tcp-dump from same subnet, MAC Adress 0:a0:cc:66:32:97 is the NFS-Server) -------------------------------------------------------------------------- 13:53:41.673733 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null test/C len=43 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00 13:53:41.773706 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null test/C len=43 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 00 It looks like a endless loop somewhere in the de0-driver ... I was able to ping the machine from itself via loopback and via the local ip. No stucked processes at all, the running make buildworld was still running. Also the load was normal, I couldn't see some special behaviour ... I paniced the server and made a crashdump. If anybody is interested in this strange behaviour, just write me back ... After a reboot, all worked again, but that's not a good solution ;) Martin PS: cvsup is from yesterday (30.7.1999) at 22:00 CET and I included a backtrace and a dmesg from my server ... backtrace from debug.kernel --------------------------- #0 boot (howto=260) at ../../kern/kern_shutdown.c:291 #1 0xc01538c9 in panic (fmt=0xc0277c14 "from debugger") at ../../kern/kern_shutdown.c:505 #2 0xc012df19 in db_panic (addr=-1071398025, have_addr=0, count=-1, modif=0xff80dddc "") at ../../ddb/db_command.c:434 #3 0xc012deb7 in db_command (last_cmdp=0xc02a6f30, cmd_table=0xc02a6d90, aux_cmd_tablep=0xc02c572c) at ../../ddb/db_command.c:334 #4 0xc012df7e in db_command_loop () at ../../ddb/db_command.c:456 #5 0xc012ffbb in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc023c0c2 in kdb_trap (type=3, code=0, regs=0xff80ded0) at ../../i386/i386/db_interface.c:157 #7 0xc02524a0 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -1070741376, tf_ebp = -8331496, tf_isp = -8331524, tf_ebx = -1070741376, tf_edx = -1070689184, tf_ecx = 16777217, tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071398025, tf_cs = 8, tf_eflags = 582, tf_esp = -1071030749, tf_ss = -1071045718}) at ../../i386/i386/trap.c:534 #8 0xc023c377 in Debugger (msg=0xc02923aa "manual escape to debugger") at machine/cpufunc.h:64 #9 0xc0236d7c in scgetc (sc=0xc02c3ca0, flags=2) at ../../dev/syscons/syscons.c:3813 #10 0xc0232529 in sckbdevent (thiskbd=0xc02db0a0, event=0, arg=0xc02c3ca0) at ../../dev/syscons/syscons.c:688 #11 0xc022bd77 in atkbd_intr (kbd=0xc02db0a0, arg=0x0) at ../../dev/kbd/atkbd.c:535 #12 0xc02692d7 in atkbd_isa_intr (arg=0xc05a2100) at ../../isa/atkbd_isa.c:125 dmesg-output ------------ Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Fri Jul 30 21:31:06 CEST 1999 root@fuchur.lan.attic.ch:/usr/src/sys/compile/FUCHUR Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8003bf real memory = 67108864 (65536K bytes) avail memory = 61652992 (60208K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0340000. Intel Pentium detected, installing workaround for F00F bug Probing for PnP devices: npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 de0: irq 17 at device 9.0 on pci0 de0: 21140A [10-100Mb/s] pass 2.0 de0: address 00:a0:cc:66:32:97 vga-pci0: irq 18 at device 10.0 on pci0 ahc0: irq 19 at device 12.0 on pci0 ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): , removable, accel, ovlap, dma, iordis wcd0: drive speed 5512KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked wdc0: unit 1 (atapi): , removable, intr, iordis wfd0: medium type unknown (no disk) wfd0: buggy Zip drive, 64-block transfer limit set atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: HP ENHANCED PCL5,PJL,POSTSCRIPT plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging limited to 100 packets/entry DUMMYNET initialized (990504) BRIDGE 981214, have 6 interfaces -- index 1 de0 type 6 phy 0 addrl 6 addr 00.a0.cc.66.32.97 IP Filter: initialized. Default = pass all, Logging = enabled Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! de0: enabling 10baseT port To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 8:19:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from freya.circle.net (morrigu.circle.net [209.95.64.11]) by hub.freebsd.org (Postfix) with ESMTP id 975F515113; Sat, 31 Jul 1999 08:19:04 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.2232.9) id ; Sat, 31 Jul 1999 11:13:21 -0400 Message-ID: From: tcobb@staff.circle.net To: blapp@attic.ch, freebsd-current@freebsd.org Cc: freebsd-smp@freebsd.org Subject: RE: network got stuck during high nfs-load Date: Sat, 31 Jul 1999 11:13:19 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="windows-1252" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm now getting a similar thing with the latest -STABLE build. NFS isn't involved, but this is on a heavily used webserver. NIC is a 3COM 3C905b. Ifconfig up and down works for about 5 packets, that's it. netstat was showing either errors inbound, or absolutely nothing. This happens about once per day now, on this machine. I've had to switch back to a UP kernel to avoid this (and another bug about processes getting wedged on a processor). I think this is an SMP problem, so I've included freebsd-smp in the reply. -Troy Cobb Circle Net, Inc. http://www.circle.net > -----Original Message----- > From: Martin Blapp [mailto:blapp@attic.ch] > Sent: Saturday, July 31, 1999 9:57 AM > To: freebsd-current@freebsd.org > Subject: network got stuck during high nfs-load > > > > Hi driver gurus, > > Today I had heavy NFS-load on my CURRENT-SMP machine while compiling > world. Suddenly all NFS-Clients stopped working. I was't > able to ping > the server from inside my /29 subnet, same with ping the > others from > the server itself. I changed cables, plugged them in and > out, did some > ifconfig up down, deleted routes and added them again ... > nothing. But > the card was still sending from time to time (once a > second) with 100% > load many 0 bytes - like some waves: > > (tcp-dump from same subnet, MAC Adress 0:a0:cc:66:32:97 is > the NFS-Server) > ------------------------------------------------------------ > -------------- > > 13:53:41.673733 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null > test/C len=43 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 00 > > 13:53:41.773706 0:a0:cc:66:32:97 > 0:a0:cc:66:32:97 null > test/C len=43 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 0000 0000 0000 > 0000 0000 0000 0000 0000 00 > > It looks like a endless loop somewhere in the de0-driver ... > > I was able to ping the machine from itself via loopback and > via the local > ip. No stucked processes at all, the running make > buildworld was still > running. Also the load was normal, I couldn't see some > special behaviour ... > > I paniced the server and made a crashdump. If anybody is > interested in > this strange behaviour, just write me back ... After a > reboot, all worked > again, but that's not a good solution ;) > > Martin > > PS: cvsup is from yesterday (30.7.1999) at 22:00 CET and I included > a backtrace and a dmesg from my server ... > > backtrace from debug.kernel > --------------------------- > > #0 boot (howto=260) at ../../kern/kern_shutdown.c:291 > #1 0xc01538c9 in panic (fmt=0xc0277c14 "from debugger") > at ../../kern/kern_shutdown.c:505 > #2 0xc012df19 in db_panic (addr=-1071398025, have_addr=0, count=-1, > modif=0xff80dddc "") at ../../ddb/db_command.c:434 > #3 0xc012deb7 in db_command (last_cmdp=0xc02a6f30, > cmd_table=0xc02a6d90, > aux_cmd_tablep=0xc02c572c) at ../../ddb/db_command.c:334 > #4 0xc012df7e in db_command_loop () at ../../ddb/db_command.c:456 > #5 0xc012ffbb in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 > #6 0xc023c0c2 in kdb_trap (type=3, code=0, regs=0xff80ded0) > at ../../i386/i386/db_interface.c:157 > #7 0xc02524a0 in trap (frame={tf_fs = 24, tf_es = 16, > tf_ds = 16, tf_edi > = 0, > tf_esi = -1070741376, tf_ebp = -8331496, tf_isp = -8331524, > tf_ebx = -1070741376, tf_edx = -1070689184, tf_ecx = 16777217, > tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = > -1071398025, tf_cs > = 8, > tf_eflags = 582, tf_esp = -1071030749, tf_ss = -1071045718}) > at ../../i386/i386/trap.c:534 > #8 0xc023c377 in Debugger (msg=0xc02923aa "manual escape > to debugger") > at machine/cpufunc.h:64 > #9 0xc0236d7c in scgetc (sc=0xc02c3ca0, flags=2) > at ../../dev/syscons/syscons.c:3813 > #10 0xc0232529 in sckbdevent (thiskbd=0xc02db0a0, event=0, > arg=0xc02c3ca0) > at ../../dev/syscons/syscons.c:688 > #11 0xc022bd77 in atkbd_intr (kbd=0xc02db0a0, arg=0x0) > at ../../dev/kbd/atkbd.c:535 > #12 0xc02692d7 in atkbd_isa_intr (arg=0xc05a2100) at > ../../isa/atkbd_isa.c:125 > > dmesg-output > ------------ > > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All > rights reserved. > FreeBSD 4.0-CURRENT #1: Fri Jul 30 21:31:06 CEST 1999 > root@fuchur.lan.attic.ch:/usr/src/sys/compile/FUCHUR > Timecounter "i8254" frequency 1193182 Hz > CPU: Pentium/P55C (586-class CPU) > Origin = "GenuineIntel" Id = 0x543 Stepping = 3 > Features=0x8003bf > real memory = 67108864 (65536K bytes) > avail memory = 61652992 (60208K bytes) > Programming 24 pins in IOAPIC #0 > FreeBSD/SMP: Multiprocessor motherboard > cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 > cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 > io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 > Preloaded elf kernel "kernel" at 0xc0340000. > Intel Pentium detected, installing workaround for F00F bug > Probing for PnP devices: > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > isab0: at device 7.0 on pci0 > ide_pci0: at device > 7.1 on pci0 > de0: irq 17 at device 9.0 on pci0 > de0: 21140A [10-100Mb/s] pass 2.0 > de0: address 00:a0:cc:66:32:97 > vga-pci0: accelerator> irq 18 at > device 10.0 on pci0 > ahc0: irq 19 at device > 12.0 on pci0 > ahc0: Using left over BIOS settings > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > isa0: on motherboard > fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 > wdc0: unit 0 (atapi): , > removable, accel, > ovlap, dma, iordis > wcd0: drive speed 5512KB/sec, 256KB cache > wcd0: supported read types: CD-R, CD-RW, CD-DA > wcd0: Audio: play, 255 volume levels > wcd0: Mechanism: ejectable tray > wcd0: Medium: CD-ROM 120mm data disc loaded, unlocked > wdc0: unit 1 (atapi): , > removable, intr, > iordis > wfd0: medium type unknown (no disk) > wfd0: buggy Zip drive, 64-block transfer limit set > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > vga0: at port 0x3b0-0x3df iomem > 0xa0000-0xbffff on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/16 bytes threshold > ppb0: IEEE1284 device found /NIBBLE > Probing for PnP devices on ppbus0: > ppbus0: HP ENHANCED > PCL5,PJL,POSTSCRIPT > plip0: on ppbus 0 > lpt0: on ppbus 0 > lpt0: Interrupt-driven port > ppi0: on ppbus 0 > APIC_IO: Testing 8254 interrupt delivery > APIC_IO: routing 8254 via pin 2 > IP packet filtering initialized, divert enabled, rule-based > forwarding > enabled, default to accept, logging limited to 100 packets/entry > DUMMYNET initialized (990504) > BRIDGE 981214, have 6 interfaces > -- index 1 de0 type 6 phy 0 addrl 6 addr 00.a0.cc.66.32.97 > IP Filter: initialized. Default = pass all, Logging = enabled > Waiting 15 seconds for SCSI devices to settle > SMP: AP CPU #1 Launched! > de0: enabling 10baseT port > > > > 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 Sat Jul 31 9:22:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 85FC214F7C; Sat, 31 Jul 1999 09:22:54 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA99944; Sat, 31 Jul 1999 09:22:38 -0700 (PDT) (envelope-from dillon) Date: Sat, 31 Jul 1999 09:22:38 -0700 (PDT) From: Matthew Dillon Message-Id: <199907311622.JAA99944@apollo.backplane.com> To: tcobb@staff.circle.net Cc: blapp@attic.ch, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: RE: network got stuck during high nfs-load References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The way I usually handle pseudo users via sendmail is to route them via a dummy subdomain. So, for example, my main server is 'apollo.backplane.com'. I route mail destined for 'pop.apollo.backplane.com' to my special pop mail backend. My /etc/aliases and other forwarding tables then simply map the usernames that I want to route to the dummy domain. For example, the pop user 'fubar' would be mapped to 'fubar@pop.apollo.backplane.com', where 'fubar' does not exist in the password file or anything like that. In sendmail, it is a simple addition to ruleset 98: R$+ + $* < @ pplus . $=w > $* $#popplus $: $1 < @ pplus . $3 > $4 R$+ + $* < @ pplus . $=w . > $* $#popplus $: $1 < @ pplus . $3 > $4 R$* < @ pplus . $=w > $* $#popplus $: $1 < @ pplus . $2 > $3 R$* < @ pplus . $=w . > $* $#popplus $: $1 < @ pplus . $2 > $3 And then add the new mailer: Mpopplus, P=/usr/local/bin/dpopmail, F=SDEFhlMsu, S=10/30, R=20/40, U=dpop, A=dpopmail $u -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 Sat Jul 31 12:44:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id C9FA614C57; Sat, 31 Jul 1999 12:44:42 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA14966; Sat, 31 Jul 1999 21:42:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) Date: Sat, 31 Jul 1999 21:42:26 +0200 Message-ID: <14964.933450146.1@critter.freebsd.dk> From: Poul-Henning Kamp Subject: Sitting inside, looking out... MIME-Version: 1.0 Content-Type: multipart/digest; boundary="----- =_aaaaaaaaaa" Content-Description: Blind Carbon Copy Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------- =_aaaaaaaaaa Content-Type: message/rfc822 Content-Description: Original Message Subject: Sitting inside, looking out... From: Poul-Henning Kamp Date: Sat, 31 Jul 1999 21:42:26 +0200 Message-ID: <14964.933450146@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Bcc: Blind Distribution List: ; MIME-Version: 1.0 We have repeatedly heard that -core's communication with the developers leaves something to be desired, so I'll venture this attempt at improving it. This email is NOT a official statement from core, it is MY PERSONAL attempt, as a core member, at improving communication between core and the developers. I will try to represent the consensus -core as faithfully as I can, but make no mistake: this is seen through my glasses. 1. Core decisions ----------------- A lot of you have been asking for -core direction and decisions on various issues, and mostly you didn't get any such thing. It seems that is the way the core team as such wants things to be. I think the best way to express it is that the core team sees itself as a supreme court, not as a governing board: We only act when all other avenues of closure have failed. Think of it as "gigamanagement" rather than "micromanagement". In general the core team doesn't make more than a handful of decisions a year (that is not counting appointing committers) and there isn't resonance in -core for changing this level of activity. So how are things decided in this project if not by -core ? Well, working code speaks loud and clear, thats for sure, but otherwise it happens exactly the way you see it: people discuss things in the mailing lists and try to reach agreement. But if you want to get a core decision on something, make sure that you send an email to core@freebsd.org with the question. You cannot expect any reaction from -core by posing the question in some random maillist. Make sure to include sufficient background and references to the subject, at least half of the core members have not heard of the discussion before. And please use a distinctive subject on your emails, "proposal for new committer" is a distinctively bad subject line, much better would be "Samuel B. Morse for committer ?" In the past -core has not been very good at even answering emails, but I have been trying to improve that by assuming a self-styled secretary function: as best I can I try to keep track of outstanding items and make sure they don't fall through the cracks. If you don't get a response from -core, nag me with an email, and I will try to make it happen. 2. Who are the committers anyway ? ---------------------------------- All the noise about Matt Dillons commit bit have generated a lot of questions about who gets to be committers, so here is a little insight into the process of appointing a committer: Generally we in core operate with three kinds of committers: Ports committers These are people who maintain one or more ports. If Asami-san wants to glue a bit on somebody, we will generally let him. Limited scope committers These are people who maintain some specific bit of the tree, typically a subsystem they are (co-)authors of. A good example is the HARP ATM stack, which Mike Spengler is taking care of (and many thanks for that Mike!) Since these people are taken on board with a explicitly stated limited scope, we are more relaxed about them than we are about the last category. People have been known to successfully sneak out from this category and into: Committers at large These are the people who persist in sending well documented PRs containing correct patches. The only way we have devised so far for ridding ourselves of this kind of annoying behaviour is to say "Here! you're a committer, now close your own PRs!" :-) For all these three categories some general rules apply, or rather if they apply the answer is a resounding "no": Flaming people and generally presenting the attitude that people who don't agree with you should leave the planet on the first available rocket (or otherwise), is the most reliable way to not pass the muster. It doesn't matter how good you are technically, if you can't work in a group, your not in this particular group. Being unresponsive to input is another good way to fall through. Some of the people are right 99.994% of the time, but nobody is right 100% of the time. If people point out to you that something you did or said isn't right, listen to them, think about it more than once, they could be right. [even Bruce has been caught on the wrong foot once, that's where I got the 99.994% figure from :-) ] Wasting peoples time. We're all here on borrowed time, most of us have jobs, families, cats, houses, you name it, things that also have legitimate claims to our time. Needlessly wasting peoples time is not welcome, in particular when it is their spare time. If you match any of these descriptions, and if you have proved that you can code or document, and have some time to spare, you'll pass the muster, no worries. And don't despair: we generally appoint a "mentor" for all new committers. The mentor is responsible for helping the new committer "learn the ropes", and generally help them get cross the threshold without getting eaten by the lions. And I hope it is all worth it for the committers, because you are certainly the biggest asset we have in the project. I'm sorry that there isn't much but the title and the rather limited fame we can offer you in return. NOTE: If somebody can find a sponsor for it, I would really like to offer an "official FreeBSD Committer sweat-shirt" to each and every single committer. Luxury cars, free vacations and suitcases filled with cash would also do. 3. The GNATS database, who handles it ? --------------------------------------- Simple: You do. Even if you are not a committer, you can help out: Find a PR, try to reproduce the problem if you can, then try to fix it if you can. If the PR contains a patch, try it out. And at the end, send a follow up to the PR with your results. A PR with a complex patch has much better chances of getting committed if the PR has a couple of follow-ups which say "works for me" than if it just sits there. 4. mac68k as a new platform ? ----------------------------- We have been contacted by Grant Stockly , who informed us that he has a almost finished port of FreeBSD to the mac68k platform. [In general I would advice that people drop the core team a note early in such an undertaking. It would be a pity if somebody else was doing the same thing and you couldn't work together just because you didn't know about each other]. The core team is very keen for more platforms, but a certain level of interest and support from users and developers is needed before we will add a platform as an official part of FreeBSD, so now is the time for those of you who have an interest in the mac68k or 68k support in general, to rally around Grant and work with him on this. Our postmaster will happily create a mailing list if you want it. That's all for now folks... Poul-Henning PS: See you all at the FreeBSD-con in October! http://www.freebsdcon.org/ -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! ------- =_aaaaaaaaaa-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 21: 1:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id E7DAE14C13; Sat, 31 Jul 1999 21:00:29 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA18294; Sun, 1 Aug 1999 13:27:52 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA83814; Sun, 1 Aug 1999 13:27:51 +0930 (CST) Date: Sun, 1 Aug 1999 13:27:51 +0930 From: Greg Lehey To: FreeBSD current users , FreeBSD Committers Subject: Recent -CURRENT doesn't show process times on some hardware Message-ID: <19990801132751.S64532@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For about a week now, I've been tracking -CURRENT on two machines, panic and mojave, building world almost daily. On mojave, a number of process timing functions have not been working at all during this time, though panic has no problems. For example: $ cat loop.c main () { while (1); } $ make loop cc loop.c -o loop $ loop& [1] 54987 $ ps up54987 USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND grog 54987 0.0 0.2 756 224 p2 R 1:20PM 0:28.98 loop $ ps up54987 In other words, though the process is looping in user state, ps shows no CPU usage, though the process time is being counted relatively correctly. Also, $ time loop Terminated [killed from another xterm] real 0m15.136s user 0m0.000s sys 0m15.040s Here the time has been attributed to the system, though it's all in user space. top shows: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Mem: 47M Active, 8284K Inact, 30M Wired, 6812K Cache, 9530K Buf, 576K Free Swap: 256M Total, 192K Used, 256M Free PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 54999 grog 28 0 756K 224K RUN 0:15 0.00% 0.00% loop The CPU timing information is always 0.0% for everything. vmstat shows: r b w avm fre flt re pi po fr sr wd0 wc0 in sy cs us sy id 1 1 0 9228 7284 112 0 0 0 133 11 0 0 131 230 23 0 0 0 1 1 0 9228 7280 4 0 0 0 0 0 0 0 106 43 24 0 0 0 What makes this all the more puzzling is that it happens only on one machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal Pentium machine of no particular lineage. Does this ring a bell with anybody? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jul 31 23:53:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id DC2E614DBB for ; Sat, 31 Jul 1999 23:53:30 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id OAA19786 for ; Sun, 1 Aug 1999 14:49:23 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id OAA16579 for ; Sun, 1 Aug 1999 14:50:43 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id OAA13313; Sun, 1 Aug 1999 14:50:44 +0800 Message-Id: <199908010650.OAA13313@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: Assembler capable of supporting 3dnow! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 14:50:44 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm messing around with the latest mesa and have discovered (suprise)that our assembler doesn't support 3dnow instructions. Are there any plans to update to a version of binutils that does? Linux's stuff appears to support it. Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message