From owner-freebsd-current Sun Nov 19 1: 0:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from eeyore.local.dohd.org (d0030.dtk.chello.nl [213.46.0.30]) by hub.freebsd.org (Postfix) with ESMTP id 8FDA937B479 for ; Sun, 19 Nov 2000 01:00:49 -0800 (PST) Received: by eeyore.local.dohd.org (Postfix, from userid 1008) id DE8F5BA9D; Sun, 19 Nov 2000 10:00:43 +0100 (MET) Date: Sun, 19 Nov 2000 10:00:43 +0100 From: Mark Huizer To: current@freebsd.org Subject: Re: CURRENT is freezing again ... Message-ID: <20001119100043.A1025@dohd.cx> References: <200011161717.SAA30813@freebsd.dk> <027d01c04ff1$90d9cf40$8a1a050a@winstar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2i In-Reply-To: <027d01c04ff1$90d9cf40$8a1a050a@winstar.com>; from steve@virtual-voodoo.com on Thu, Nov 16, 2000 at 12:20:49PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Nov 16, 2000 at 12:20:49PM -0500, Steven E. Ames wrote: > It seems to only do it SMP... the same machine built with a non-SMP > kernel (same source code) runs just fine for extended periods. I have a non-SMP machine that is running a 15-nov current kernel, which freezes a few times a day. This morning I found it might coincide with the times that cvsup is running. Disabled that, I'll see if that's where the problem might show up. Freeze means: no keyboard activity possible, machine just does nothing. > > > > On Thu, 16 Nov 2000, Soren Schmidt wrote: > > > > > > > > After last cvsup my machine (Dual PIII, SMP kernel) is freezing > again in > > > > > 10 min after boot... > > > > > > > > You mean "is still freezing" right ? > > > > > > > > Current has been like this for longer than I care to think about, > it > > > > seems those in charge doesn't take these problems seriously > (enough)... > > > > > > I think info about where/how it freezing would be more helpful. > > > > No idea, the system just freezes, no drob to DDB no remote gdb no > > nothing, so its really hard to tell where... > > As to how, just boot current on a fairly fast machine, make a kernel > > and it'll hang in minutes if not less, or just leave it alone and > > it will hang in 10-30 mins... > > > > -Søren > > > > > > 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 -- Nice testing in little China... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 2:29: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from siri.nordier.com (c3-dbn-69.dial-up.net [196.33.200.69]) by hub.freebsd.org (Postfix) with ESMTP id CC62337B479; Sun, 19 Nov 2000 02:29:01 -0800 (PST) Received: (from rnordier@localhost) by siri.nordier.com (8.9.3/8.6.12) id MAA13020; Sun, 19 Nov 2000 12:29:23 +0200 (SAST) From: Robert Nordier Message-Id: <200011191029.MAA13020@siri.nordier.com> Subject: Re: Highspeed serial consoles and -current To: jwd@FreeBSD.ORG (John W. De Boskey) Date: Sun, 19 Nov 2000 12:29:23 +0200 (SAST) Cc: freebsd-current@FreeBSD.ORG (Current List) Reply-To: rnordier@FreeBSD.ORG In-Reply-To: <20001118183824.A64932@FreeBSD.org> from "John W. De Boskey" at Nov 18, 2000 06:38:24 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. De Boskey wrote: > I'm trying to increase the speed of the serial console > on a -current box from 9600 to 38400. I've put the following > in /etc/make.conf: > > BOOT_COMCONSOLE_SPEED=38400 # serial console speed > > Unfortunately, it doesn't work. It still runs at 9600. > I remember seeing something about this (I thought) in one > of the mailing lists, but I can't seem to find it. Is that all you did, or did you also rebuild and reinstall all the boot code, and refresh the boot blocks on disk using disklabel -B? -- Robert Nordier rnordier@nordier.com rnordier@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 Nov 19 5:41:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 1A7AE37B479 for ; Sun, 19 Nov 2000 05:41:08 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id IAA16696; Sun, 19 Nov 2000 08:44:28 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200011191344.IAA16696@hda.hda.com> Subject: Re: Typo in labpc.c In-Reply-To: <33305.974579762@critter> from Poul-Henning Kamp at "Nov 18, 2000 09:36:02 pm" To: Poul-Henning Kamp Date: Sun, 19 Nov 2000 08:44:22 -0500 (EST) Cc: Julian Elischer , David Malone , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >> >This seems to only do the cdevsw_add if the malloc failed. I presume > >> >this is the opposit of the intended sense. I'll fix it up if you also > >> >think it looks wrong. > >> > >> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > >> that labpc doesn't work, the labpc driver should be killed, not fixed. > >> > >> Objections ? > > > >What you are saying is that people who may be using this driver have > >not yet moved up to -current or 4.x and as such should not be allowed > >to? > > I'm saying: > > "If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > that labpc doesn't work, the labpc driver should be killed, not fixed." > > That's 1.5 year Julian, and if nobody *who is using it* objects it goes. For the record: If anyone wants labpc tested and kept up to date send me a card and I'll test it at each stable release cycle. Even better, also send me the register compatible DAQCARD 1200 PC card version. My former client using a batch of those cards obviously isn't staying up to date on the OS. Anyone who upgrades a working system will be just as upset if it doesn't work as if it is gone so I defer on the axe discussion. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 5:52:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 969CD37B479 for ; Sun, 19 Nov 2000 05:52:15 -0800 (PST) Received: from kinshasa-37.budapest.interware.hu ([195.70.51.165] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xUt9-00064J-00; Sun, 19 Nov 2000 14:52:12 +0100 Message-ID: <3A17DB02.F62DA218@elischer.org> Date: Sun, 19 Nov 2000 05:52:03 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Dufault Cc: Poul-Henning Kamp , David Malone , current@FreeBSD.ORG Subject: Re: Typo in labpc.c References: <200011191344.IAA16696@hda.hda.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Dufault wrote: > > > > > >> >This seems to only do the cdevsw_add if the malloc failed. I presume > > >> >this is the opposit of the intended sense. I'll fix it up if you also > > >> >think it looks wrong. > > >> > > >> If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > > >> that labpc doesn't work, the labpc driver should be killed, not fixed. > > >> > > >> Objections ? > > > > > >What you are saying is that people who may be using this driver have > > >not yet moved up to -current or 4.x and as such should not be allowed > > >to? > > > > I'm saying: > > > > "If nobody have noticed in "17 months, 2 weeks ago" (as cvs-web says) > > that labpc doesn't work, the labpc driver should be killed, not fixed." > > > > That's 1.5 year Julian, and if nobody *who is using it* objects it goes. > > For the record: If anyone wants labpc tested and kept up to date send > me a card and I'll test it at each stable release cycle. Even better, > also send me the register compatible DAQCARD 1200 PC card version. > > My former client using a batch of those cards obviously > isn't staying up to date on the OS. Anyone who upgrades a working > system will be just as upset if it doesn't work as if it is gone > so I defer on the axe discussion. I gather you aren't in a position to test using your former client's cards.. ("former" is a bit of a clue I guess). What are the chances that he may decide one day to upgrade? (e.g. to support a new PC) > > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Fail-Safe systems, Agency approval > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 6:14:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 0F2B337B479 for ; Sun, 19 Nov 2000 06:14:41 -0800 (PST) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id JAA16768; Sun, 19 Nov 2000 09:18:40 -0500 (EST) (envelope-from dufault) From: Peter Dufault Message-Id: <200011191418.JAA16768@hda.hda.com> Subject: Re: Typo in labpc.c In-Reply-To: <3A17DB02.F62DA218@elischer.org> from Julian Elischer at "Nov 19, 2000 05:52:03 am" To: Julian Elischer Date: Sun, 19 Nov 2000 09:18:40 -0500 (EST) Cc: phk@critter.freebsd.dk, current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > For the record: If anyone wants labpc tested and kept up to date send > > me a card and I'll test it at each stable release cycle. Even better, > > also send me the register compatible DAQCARD 1200 PC card version. > > > > My former client using a batch of those cards obviously > > isn't staying up to date on the OS. Anyone who upgrades a working > > system will be just as upset if it doesn't work as if it is gone > > so I defer on the axe discussion. > > I gather you aren't in a position to test using your former client's > cards.. ("former" is a bit of a clue I guess). What are the chances that > he may decide one day to upgrade? (e.g. to support a new PC) We aren't enemies, and they will probably be clients again. I could test things down their on my own dime but it would be too big a dime. I'd be better off buying a board on my own but I'm not going to. These are manufacturing test stands for medical equipment that have been "validated" in their limited environment. They have identical spare computers, will install 3.4, and set them up and test the test stands following a formal step by step procedure. They don't need me to help them and they probably won't upgrade for the life of the current product unless they needed to change production numbers. Unlike many projects, this sort is extremely close-ended. One of the things we do during release is to make sure every feature is specified and has a test, and I happily go through and rip out those features without that. That's why it is hard for me to argue with Poul. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 6:38:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 18C8237B479 for ; Sun, 19 Nov 2000 06:38:35 -0800 (PST) Received: from kinshasa-37.budapest.interware.hu ([195.70.51.165] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xVbv-00005y-00; Sun, 19 Nov 2000 15:38:28 +0100 Message-ID: <3A17E5DD.F06DFFE6@elischer.org> Date: Sun, 19 Nov 2000 06:38:21 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Peter Dufault , current@freebsd.org Subject: Re: Typo in labpc.c References: <200011191418.JAA16768@hda.hda.com> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Dufault wrote: > > > > For the record: If anyone wants labpc tested and kept up to date send > > > me a card and I'll test it at each stable release cycle. Even better, > > > also send me the register compatible DAQCARD 1200 PC card version. > > > > > > My former client using a batch of those cards obviously > > > isn't staying up to date on the OS. Anyone who upgrades a working > > > system will be just as upset if it doesn't work as if it is gone > > > so I defer on the axe discussion. > > > > I gather you aren't in a position to test using your former client's > > cards.. ("former" is a bit of a clue I guess). What are the chances that > > he may decide one day to upgrade? (e.g. to support a new PC) > > We aren't enemies, and they will probably be clients again. I > could test things down their on my own dime but it would be too > big a dime. I'd be better off buying a board on my own but I'm not > going to. > > These are manufacturing test stands for medical equipment that have > been "validated" in their limited environment. They have identical > spare computers, will install 3.4, and set them up and test the > test stands following a formal step by step procedure. They don't > need me to help them and they probably won't upgrade for the life > of the current product unless they needed to change production > numbers. > > Unlike many projects, this sort is extremely close-ended. One of > the things we do during release is to make sure every feature is > specified and has a test, and I happily go through and rip out > those features without that. That's why it is hard for me to argue > with Poul. My thinking is that there are others like them out there using these cards, that are not in 'regular contact' with the freeBSD community. If these cards are dropped entirely, then we never hear from them again, as when they need to upgrade for somereason, they just say "stuffit, let's use linux". We don;t even KNOW we pissed off users. If we have a driver (with the typo fixed) then at least we'll hear from them if it doesn't work, and get a chance to fix it.. if we do we are noce guys and they sing praise of our support. in either case I think we are no worse off, and probably better off than if we delete the file, and silently lose users. We certainly don't know who wants to use BSD in the future for some cute control operation.. > > Peter > > -- > Peter Dufault (dufault@hda.com) Realtime development, Machine control, > HD Associates, Inc. Fail-Safe systems, Agency approval -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 7: 8:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id EC3C637B479; Sun, 19 Nov 2000 07:08:26 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eAJF8O433473; Sun, 19 Nov 2000 08:08:24 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011191508.eAJF8O433473@aslan.scsiguy.com> To: Warner Losh Cc: jon@FreeBSD.org, current@FreeBSD.org Subject: Re: Cardbus fixes In-Reply-To: Your message of "Sat, 18 Nov 2000 22:39:35 MST." <200011190539.WAA87209@harmony.village.org> Date: Sun, 19 Nov 2000 08:08:24 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring >things like this. Where did you get a copy of the pccard spec? Do you have to order it from the pcmcia SIG? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 7:45:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 43E1837B479 for ; Sun, 19 Nov 2000 07:45:38 -0800 (PST) Received: from vigrid.com (pm3-pt18.pcnet.net [206.105.29.92]) by pcnet1.pcnet.com (8.8.7/PCNet) with ESMTP id KAA01273; Sun, 19 Nov 2000 10:45:17 -0500 (EST) Message-ID: <3A17F630.6E1B6F45@vigrid.com> Date: Sun, 19 Nov 2000 10:48:00 -0500 From: "Daniel M. Eischen" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: pccardd dies with SIGSEGV [PATCH included] Content-Type: multipart/mixed; boundary="------------3A4C922084D75946AE21466B" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3A4C922084D75946AE21466B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Many weeks ago, I noticed that pccardd died with a SIGSEGV when I inserted my Motorola Montana 33.6 fax/modem. I'm not sure of the exact time as to when this occurred, but I know that pccardd had been working just fine with this card. I finally found the time to track down the problem (now that I really need to use it). Here's an excerpt from `pccardc dumpcis`: Tuple #2, code = 0x15 (Version 1 info), length = 39 000: 04 01 4d 6f 74 6f 72 6f 6c 61 00 4d 4f 4e 54 41 010: 4e 41 20 33 33 2e 36 20 46 41 58 2f 4d 4f 44 45 020: 4d 00 56 32 2e 30 00 Version = 4.1, Manuf = [Motorola], card vers = [MONTANA 33.6 FAX/MODEM] Addit. info = [V2.0],[] ^^ Note this field is empty When pccardd reads the field above, the length is supposedly 4, but garbage is read in and the field is not terminated with a null character. This causes problems later on when the field is copied using strdup(). Attach is a patch that fixes the problem for me. I can offer a `pccardc dumpcis` and a full gdb session that shows the problem to anyone interested. -- Dan Eischen --------------3A4C922084D75946AE21466B Content-Type: text/plain; charset=us-ascii; name="read_cis.diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="read_cis.diffs" Index: readcis.c =================================================================== RCS file: /opt/b/CVS/src/usr.sbin/pccard/pccardd/readcis.c,v retrieving revision 1.20 diff -u -r1.20 readcis.c --- readcis.c 2000/06/18 20:22:11 1.20 +++ readcis.c 2000/11/19 16:30:57 @@ -202,7 +202,9 @@ cp->manuf = NULL; } if (len > 1 && *p != 0xff) { - cp->manuf = strdup(p); + /* cp->manuf = strdup(p); */ + cp->manuf = xmalloc(len + 1); + strncat(cp->manuf, p, len); while (*p++ && --len > 0); } if (cp->vers) { --------------3A4C922084D75946AE21466B-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 7:52:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from markw2kpro.dyn.dhs.org (okc-27-136-119.mmcable.com [24.27.136.119]) by hub.freebsd.org (Postfix) with ESMTP id B5D7137B479 for ; Sun, 19 Nov 2000 07:52:07 -0800 (PST) Received: from mmcable.com (localhost [127.0.0.1]) by markw2kpro.dyn.dhs.org (8.11.0/8.11.0) with ESMTP id eAJFsw812098 for ; Sun, 19 Nov 2000 09:54:58 -0600 (CST) (envelope-from mark@mmcable.com) Message-ID: <3A17F7D1.732AB18D@mmcable.com> Date: Sun, 19 Nov 2000 09:54:58 -0600 From: Mark R Grant Reply-To: mark@mmcable.com X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Error in libstdc++ buildworld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FreeBSD user since 2.x, but never attempted to make/build/install world. While doing 'make -j2 buildworld': ===> libstdc++ ~~~deleted a couple hundred lines between, then got here: cc -pg -O -pipe -I/usr/src/gnu/lib/libstdc++ -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/include -I/usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio -I. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/gnu/lib/libstdc++/../../../contrib/libstdc++/../libio/floatconv.c -o floatconv.po {standard input}: cc: Assembler messages: Internal compiler error: program cc1 got fatal signal 11{standard input}:0: Warning: end of file not at end of a line; newline inserted {standard input}:2148: Error: bad register name `%' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Got the same error after several cvs updates and retries. Mark Grant mark@mmcable.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 8:27:51 2000 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 AA3F037B479 for ; Sun, 19 Nov 2000 08:27:49 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA13513; Sun, 19 Nov 2000 08:27:48 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAJGRlA39610; Sun, 19 Nov 2000 08:27:47 -0800 (PST) (envelope-from obrien) Date: Sun, 19 Nov 2000 08:27:47 -0800 From: "David O'Brien" To: Mark R Grant Cc: current@FreeBSD.org Subject: Re: Error in libstdc++ buildworld Message-ID: <20001119082746.A39585@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <3A17F7D1.732AB18D@mmcable.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A17F7D1.732AB18D@mmcable.com>; from mark@mmcable.com on Sun, Nov 19, 2000 at 09:54:58AM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 19, 2000 at 09:54:58AM -0600, Mark R Grant wrote: > FreeBSD user since 2.x, but never attempted to make/build/install world. > While doing 'make -j2 buildworld': It would help us immensely if you would give some details of the environment in which you are having this problem. What CLFAGS are you using? What version of FreeBSD are you running? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 8:41:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from markw2kpro.dyn.dhs.org (okc-27-136-119.mmcable.com [24.27.136.119]) by hub.freebsd.org (Postfix) with ESMTP id 5E07A37B479; Sun, 19 Nov 2000 08:41:18 -0800 (PST) Received: from mmcable.com (localhost [127.0.0.1]) by markw2kpro.dyn.dhs.org (8.11.0/8.11.0) with ESMTP id eAJGi9812617; Sun, 19 Nov 2000 10:44:09 -0600 (CST) (envelope-from mark@mmcable.com) Message-ID: <3A180358.652F4AF9@mmcable.com> Date: Sun, 19 Nov 2000 10:44:09 -0600 From: Mark R Grant Reply-To: mark@mmcable.com X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Cc: obrien@FreeBSD.org Subject: Re: Error in libstdc++ buildworld References: <3A17F7D1.732AB18D@mmcable.com> <20001119082746.A39585@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > On Sun, Nov 19, 2000 at 09:54:58AM -0600, Mark R Grant wrote: > > FreeBSD user since 2.x, but never attempted to make/build/install world. > > While doing 'make -j2 buildworld': > > It would help us immensely if you would give some details of the > environment in which you are having this problem. > What CLFAGS are you using? What version of FreeBSD are you running? > Following my interpretation of the instructions in the make.conf file, the CFLAGS line is commented out. I am running version 4.1.1-RELEASE, trying to upgrade to -CURRENT using the 'RELENG_4' tag. Last cvsup was Nov 18, 2300 GMT To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 8:49:58 2000 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 0A8F137B479 for ; Sun, 19 Nov 2000 08:49:56 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA13600; Sun, 19 Nov 2000 08:49:55 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAJGnsM44292; Sun, 19 Nov 2000 08:49:54 -0800 (PST) (envelope-from obrien) Date: Sun, 19 Nov 2000 08:49:53 -0800 From: "David O'Brien" To: Mark R Grant Cc: current@FreeBSD.org Subject: Re: Error in libstdc++ buildworld Message-ID: <20001119084953.A43120@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <3A17F7D1.732AB18D@mmcable.com> <20001119082746.A39585@dragon.nuxi.com> <3A180358.652F4AF9@mmcable.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A180358.652F4AF9@mmcable.com>; from mark@mmcable.com on Sun, Nov 19, 2000 at 10:44:09AM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 19, 2000 at 10:44:09AM -0600, Mark R Grant wrote: > David O'Brien wrote: Respect my "Reply-To: current@freebsd.org" or I won't respond to queries for help in the future. > Following my interpretation of the instructions in the make.conf file, the > CFLAGS line is commented out. > I am running version 4.1.1-RELEASE, trying to upgrade to -CURRENT using the > 'RELENG_4' tag. Last cvsup was Nov 18, 2300 GMT One cannot "upgrade"[*] to -CURRENT using he "RELENG_4" tag. The "RELENG_4" is the 4.x code base. To get -CURRENT source one would use no tag. RELENG_4 is very buildable right now, so something is weird on your end. You'll [again] need to give more _details_. Example: 1. I checked out the source using ``cd /usr ; cvs co src'' 2. I then made sure the /usr/obj/ directory existed. 3. I then did ``cd /usr/src ; make world''. [*] "upgrading" to -CURRENT really doesn't mean anything as it isn't a release and for your use it may easily be a "downgrade". You should examine your reasons for wanting to run -CURRENT. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 9: 6:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6DA2D37B479; Sun, 19 Nov 2000 09:06:57 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA28867; Sun, 19 Nov 2000 10:06:55 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA06547; Sun, 19 Nov 2000 10:06:51 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14872.2219.449023.519561@nomad.yogotech.com> Date: Sun, 19 Nov 2000 10:06:51 -0700 (MST) To: "Justin T. Gibbs" Cc: Warner Losh , jon@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Cardbus fixes In-Reply-To: <200011191508.eAJF8O433473@aslan.scsiguy.com> References: <200011190539.WAA87209@harmony.village.org> <200011191508.eAJF8O433473@aslan.scsiguy.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring > >things like this. > > Where did you get a copy of the pccard spec? Do you have to order > it from the pcmcia SIG? Mike has my really old copy you can have (if you can get it from him), and I think FreeBSD Inc. bought Warner a copy. It's *HUGE*. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 9:38:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 141EB37B479; Sun, 19 Nov 2000 09:38:41 -0800 (PST) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAJHcdQ18621; Sun, 19 Nov 2000 10:38:40 -0700 (MST) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.1/8.8.3) with ESMTP id eAJHcNG02809; Sun, 19 Nov 2000 10:38:23 -0700 (MST) Message-Id: <200011191738.eAJHcNG02809@billy-club.village.org> To: nate@yogotech.com (Nate Williams) Subject: Re: Cardbus fixes Cc: "Justin T. Gibbs" , jon@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Sun, 19 Nov 2000 10:06:51 MST." <14872.2219.449023.519561@nomad.yogotech.com> References: <14872.2219.449023.519561@nomad.yogotech.com> <200011190539.WAA87209@harmony.village.org> <200011191508.eAJF8O433473@aslan.scsiguy.com> Date: Sun, 19 Nov 2000 10:38:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14872.2219.449023.519561@nomad.yogotech.com> Nate Williams writes: : > >I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring : > >things like this. : > : > Where did you get a copy of the pccard spec? Do you have to order : > it from the pcmcia SIG? : : Mike has my really old copy you can have (if you can get it from him), : and I think FreeBSD Inc. bought Warner a copy. Yes, they did. Since it was FreeBSD, Inc a limited sharing of the electronic version may be permitted (I have to go look at the license that came with the cdrom, but I think it said limited sharing within the organization is permitted). : It's *HUGE*. Yes. It takes up more space than the cabinet that I keep 90% of my pcmcia/cardbus cards in :-). I'd have been happy with the cdrom only. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 10:32:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id 2E84737B4CF for ; Sun, 19 Nov 2000 10:32:13 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id KAA26242 for ; Sun, 19 Nov 2000 10:32:11 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A181CAA.4641A709@FreeBSD.org> Date: Sun, 19 Nov 2000 10:32:10 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Mini head's up: [Fwd: cvs commit: src/etc crontab] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Per discussion that ensued after the most round of DST changes last month, I've changed the default time for the periodic/daily job to 3:01am (0301). The commit message describes the reasoning, and many, many more details are available in the mail archives. Enjoy, Doug -------- Original Message -------- Subject: cvs commit: src/etc crontab Date: Sun, 19 Nov 2000 10:16:47 -0800 (PST) From: Doug Barton To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org dougb 2000/11/19 10:16:47 PST Modified files: etc crontab Log: When to run the periodic/daily event has had several rounds of discussion over the past couple years. The most recent came to the general consensus that this was the best time, but no one actually made the change, so I'll don my asbestos undies and dive in. Please note that this time was chosen with input from people in various countries with various methods and schedules for switching to and from DST. There is no perfect time to schedule this job that works for everyone, but this time both A) Works for more people, and B) Causes problems for fewer people. And, ultimately, you can always change it if you need to. Revision Changes Path 1.23 +2 -2 src/etc/crontab http://www.FreeBSD.org/cgi/cvsweb.cgi/src/etc/crontab.diff?&r1=1.22&r2=1.23&f=h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 10:42:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from markw2kpro.dyn.dhs.org (okc-27-136-119.mmcable.com [24.27.136.119]) by hub.freebsd.org (Postfix) with ESMTP id 98DDE37B479 for ; Sun, 19 Nov 2000 10:42:25 -0800 (PST) Received: from mmcable.com (localhost [127.0.0.1]) by markw2kpro.dyn.dhs.org (8.11.0/8.11.0) with ESMTP id eAJIjC881846 for ; Sun, 19 Nov 2000 12:45:12 -0600 (CST) (envelope-from mark@mmcable.com) Message-ID: <3A181FB7.FBB1A4AC@mmcable.com> Date: Sun, 19 Nov 2000 12:45:11 -0600 From: Mark R Grant Reply-To: mark@mmcable.com X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.1.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.org Subject: Re: Error in libstdc++ buildworld References: <3A17F7D1.732AB18D@mmcable.com> <20001119082746.A39585@dragon.nuxi.com> <3A180358.652F4AF9@mmcable.com> <20001119084953.A43120@dragon.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > Example: > > 1. I checked out the source using ``cd /usr ; cvs co src'' > 2. I then made sure the /usr/obj/ directory existed. > 3. I then did ``cd /usr/src ; make world''. > > [*] "upgrading" to -CURRENT really doesn't mean anything as it isn't a > release and for your use it may easily be a "downgrade". You should > examine your reasons for wanting to run -CURRENT. Now, here is where I am. For precision, I decided to take it step-by-step again and document every action: 0. The CHFLAGS setting my my make.conf file is commented out. 1. I cleaned up the source directories using "cd /usr ; make cleandir" 2. I cleaned up the object directories using "cd /usr/obj ; chflags -R noschg * ; rm -rf *" 3. I edited by cvs-supfile to "tag=*" then checked out the source using "cd /usr/src ; cvsup -g -L 2 /usr/local/etc/cvs-supfile" 4. I decided that since I am too much of a novice at this, I should use the buildworld and installworld seperately. I ran "cd /usr/src ; make -j2 buildworld" This is where it errored out, somewhere during the building of "===> rpcsrv" ///deleted several hundred messages/// cd /usr/src/secure/lib/libcrypto; make beforeinstall sh /usr/src/tools/install.sh -c -o root -g wheel -m 444 bsd.README bsd.dep.mk bsd.doc.mk bsd.docb.mk bsd.info.mk bsd.kern.mk bsd.kmod.mk bsd.lib.mk bsd.libnames.mk bsd.man.mk bsd.obj.mk bsd.own.mk bsd.port.mk bsd.port.post.mk bsd.port.pre.mk bsd.port.subdir.mk bsd.prog.mk bsd.sgml.mk bsd.subdir.mk sys.mk /usr/obj/usr/src/i386/mk usage: install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 file2 install [-CcDpsv] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory install -d [-v] [-g group] [-m mode] [-o owner] directory ... *** Error code 64 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error I can provide all/more of the script output To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 14:32:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 0FFF337B479 for ; Sun, 19 Nov 2000 14:32:13 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAJMW8b01477 for ; Sun, 19 Nov 2000 15:32:08 -0700 (MST) Date: Sun, 19 Nov 2000 15:32:08 -0700 (MST) From: X-Sender: janb@gecko To: freebsd-current@FreeBSD.ORG Subject: /etc/local/rc.conf not working? 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 the rc.conf on my computer sets the sendmail enable flag to NO, and yet on bootup the sendmail daemon is started. ps -ax confirms this with sendmail: accepting connections JAn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 15: 4:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n37.san.rr.com (dt051n37.san.rr.com [204.210.32.55]) by hub.freebsd.org (Postfix) with ESMTP id C46D037B479 for ; Sun, 19 Nov 2000 15:04:18 -0800 (PST) Received: from FreeBSD.org (Studded@master [10.0.0.2]) by dt051n37.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA29102; Sun, 19 Nov 2000 15:04:15 -0800 (PST) (envelope-from DougB@FreeBSD.org) Message-ID: <3A185C6F.96D4D7D8@FreeBSD.org> Date: Sun, 19 Nov 2000 15:04:15 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: janb@cs.utep.edu Cc: freebsd-current@FreeBSD.org Subject: Re: /etc/local/rc.conf not working? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG janb@cs.utep.edu wrote: > > the rc.conf on my computer sets the sendmail enable flag to NO, and yet on > bootup the sendmail daemon is started. ps -ax confirms this with sendmail: > accepting connections Do you actually have the file in /etc/local as the subject of your email suggests? If so, that's your problem. You want to have rc.conf and/or rc.conf.local in /etc/ itself. Good luck, Doug -- Life is an essay test. Long form. Spelling counts. Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 15:32:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id A86B737B479; Sun, 19 Nov 2000 15:32:06 -0800 (PST) Received: from [127.0.0.1] (helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13xdsA-0000CP-00; Sun, 19 Nov 2000 16:27:46 -0700 Message-ID: <3A1861F2.4CE4451A@softweyr.com> Date: Sun, 19 Nov 2000 16:27:46 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Nate Williams , "Justin T. Gibbs" , jon@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Cardbus fixes References: <14872.2219.449023.519561@nomad.yogotech.com> <200011190539.WAA87209@harmony.village.org> <200011191508.eAJF8O433473@aslan.scsiguy.com> <200011191738.eAJHcNG02809@billy-club.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <14872.2219.449023.519561@nomad.yogotech.com> Nate Williams writes: > : > >I'll have to look up the CIS_PTR spec. I'm not sure I like hardwiring > : > >things like this. > : > > : > Where did you get a copy of the pccard spec? Do you have to order > : > it from the pcmcia SIG? > : > : Mike has my really old copy you can have (if you can get it from him), > : and I think FreeBSD Inc. bought Warner a copy. > > Yes, they did. Since it was FreeBSD, Inc a limited sharing of the > electronic version may be permitted (I have to go look at the license > that came with the cdrom, but I think it said limited sharing within > the organization is permitted). If it permits sharing within the "engineering department" perhaps we should just mount it in a drive on freefall. That's the usual sharing arrangement within for-profit companies, and only FreeBSD "associates" have access to freefall. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 15:35:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 459EF37B4C5; Sun, 19 Nov 2000 15:35:16 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAJNZEQ19959; Sun, 19 Nov 2000 16:35:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA27788; Sun, 19 Nov 2000 16:35:14 -0700 (MST) Message-Id: <200011192335.QAA27788@harmony.village.org> To: Wes Peters Subject: Re: Cardbus fixes Cc: Nate Williams , "Justin T. Gibbs" , jon@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Sun, 19 Nov 2000 16:27:46 MST." <3A1861F2.4CE4451A@softweyr.com> References: <3A1861F2.4CE4451A@softweyr.com> <14872.2219.449023.519561@nomad.yogotech.com> <200011190539.WAA87209@harmony.village.org> <200011191508.eAJF8O433473@aslan.scsiguy.com> <200011191738.eAJHcNG02809@billy-club.village.org> Date: Sun, 19 Nov 2000 16:35:14 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <3A1861F2.4CE4451A@softweyr.com> Wes Peters writes: : If it permits sharing within the "engineering department" perhaps we should : just mount it in a drive on freefall. That's the usual sharing arrangement : within for-profit companies, and only FreeBSD "associates" have access to : freefall. I think that we can do that (or I can just put them in my local directory). We can't put them on a web page, however. I had them in a private directory for a while. I'm having problems finding the cdrom, so I'm having problems finding the exact license that we have the cdrom under. Some of them restrict things to one geographic division, while others do not. Until then, I'm not going to make them generally available to all FreeBSD developers. I may make them available on an as needed basis to bonified cardbus workers (which I define arbitrarily as people that have submitted code for cardbus). BTW, http://www.pcisig.com/order/index.php3 has the pci specs on a cdrom for an excellent deal on pci specs. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 16:22: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id 1834D37B479 for ; Sun, 19 Nov 2000 16:22:00 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.Beta0/8.11.2.Beta0) id eAK0LkB50754; Sun, 19 Nov 2000 16:21:46 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14872.28310.870075.928166@horsey.gshapiro.net> Date: Sun, 19 Nov 2000 16:21:42 -0800 From: Gregory Neil Shapiro To: Cc: freebsd-current@FreeBSD.ORG Subject: Re: /etc/local/rc.conf not working? In-Reply-To: References: X-Mailer: VM 6.82 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG janb> the rc.conf on my computer sets the sendmail enable flag to NO, and janb> yet on bootup the sendmail daemon is started. ps -ax confirms this janb> with sendmail: accepting connections At least as of November 6th, the only rc.conf files are /etc/defaults/rc.conf, /etc/rc.conf, and /etc/rc.conf.local. There is no /etc/local/rc.conf. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 16:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 7513037B479; Sun, 19 Nov 2000 16:46:47 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAK0kgH02086; Sun, 19 Nov 2000 17:46:42 -0700 (MST) Date: Sun, 19 Nov 2000 17:46:42 -0700 (MST) From: X-Sender: janb@gecko To: Doug Barton Cc: freebsd-current@FreeBSD.org Subject: Re: /etc/local/rc.conf not working? In-Reply-To: <3A185C6F.96D4D7D8@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OOPs, well this was the problem. That leaves me wondering, why this is on two places... Thanks, JAN On Sun, 19 Nov 2000, Doug Barton wrote: > janb@cs.utep.edu wrote: > > > > the rc.conf on my computer sets the sendmail enable flag to NO, and yet on > > bootup the sendmail daemon is started. ps -ax confirms this with sendmail: > > accepting connections > > Do you actually have the file in /etc/local as the subject of your > email suggests? If so, that's your problem. You want to have rc.conf > and/or rc.conf.local in /etc/ itself. > > Good luck, > > Doug > -- > Life is an essay test. Long form. Spelling counts. > > Do YOU Yahoo!? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 16:53:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from horsey.gshapiro.net (horsey.gshapiro.net [209.220.147.178]) by hub.freebsd.org (Postfix) with ESMTP id EEFD837B479; Sun, 19 Nov 2000 16:53:55 -0800 (PST) Received: (from gshapiro@localhost) by horsey.gshapiro.net (8.11.2.Beta0/8.11.2.Beta0) id eAK0rrE52936; Sun, 19 Nov 2000 16:53:53 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14872.30240.506505.972789@horsey.gshapiro.net> Date: Sun, 19 Nov 2000 16:53:52 -0800 From: Gregory Neil Shapiro To: Cc: Doug Barton , freebsd-current@FreeBSD.ORG Subject: Re: /etc/local/rc.conf not working? In-Reply-To: References: <3A185C6F.96D4D7D8@FreeBSD.org> X-Mailer: VM 6.82 under 21.2 (beta36) "Notus" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG janb> OOPs, well this was the problem. That leaves me wondering, why this is on janb> two places... /etc/defaults/rc.conf are the defaults -- you should not be editing that file. Any settings you want to change to in /etc/rc.conf (which should be a small file, not a copy of /etc/defaults/rc.conf). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Nov 19 18:11:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from blount.mail.mindspring.net (blount.mail.mindspring.net [207.69.200.226]) by hub.freebsd.org (Postfix) with ESMTP id 0717537B479 for ; Sun, 19 Nov 2000 18:11:10 -0800 (PST) Received: from ix.netcom.com (sil-wa17-10.ix.netcom.com [207.93.156.10]) by blount.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA22983 for ; Sun, 19 Nov 2000 21:11:06 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.11.1/8.9.3) id eAK2Cj500371; Sun, 19 Nov 2000 18:12:45 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Sun, 19 Nov 2000 18:12:45 -0800 (PST) Message-Id: <200011200212.eAK2Cj500371@ix.netcom.com> From: "Thomas D. Dean" To: current@FreeBSD.ORG Subject: Clock Strangeness in UP Kernel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The clock is strange in -current UP. # uname -a FreeBSD celebris 5.0-CURRENT FreeBSD 5.0-CURRENT #1: \ Sun Nov 19 17:53:38 PST 2000 \ root@celebris:/usr/src/sys/compile/CELEBRIS i386 dmesg is attached. Some of the garbage at the top of dmesg is from 2 kernels ago, 15 Nov., when I was running SMP and had silo overflows. Both timecounters are listed in dmesg: ... Timecounter "i8254" frequency 1193026 Hz Timecounter "TSC" frequency 121329898 Hz ... I have options CLK_USE_I8254_CALIBRATION in my config. Some recent output from ntpdate log: (I changed the server from 140.142.16.34 to xxxx). ... 18 Nov 16:29:41 ntpdate[10276]: step time server xxxx offset -443.428520 sec 18 Nov 20:29:41 ntpdate[10463]: step time server xxxx offset -443.462177 sec 19 Nov 00:29:41 ntpdate[10799]: step time server xxxx offset -443.474425 sec 19 Nov 04:29:42 ntpdate[11305]: step time server xxxx offset -443.515112 sec 19 Nov 08:29:41 ntpdate[11536]: step time server xxxx offset -443.437881 sec 19 Nov 12:29:42 ntpdate[11855]: step time server xxxx offset -443.461982 sec 19 Nov 16:29:41 ntpdate[12378]: step time server xxxx offset -443.430663 sec The step has a high std. dev. I see values of 115 to 2900 sec over the past few days. The machine was up for 3 days, 10 hours, before rebooting an hour ago. tomdean ===== dmesg ============ B/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) Mounting root from ufs:/dev/da1s1a da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) SMP: AP CPU #1 Launched! de0: enabling BNC port sio0: 1 more silo overflow (total 1) sio0: 1 more silo overflow (total 2) sio0: 1 more silo overflow (total 3) sio0: 2 more silo overflows (total 5) boot() called on cpu#1 Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped Waiting (max 60 seconds) for system process `syncer' to stop...stopped syncing disks... done Uptime: 6m6s RebooCopyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #1: Sun Nov 19 17:53:38 PST 2000 root@celebris:/usr/src/sys/compile/CELEBRIS Timecounter "i8254" frequency 1193026 Hz Timecounter "TSC" frequency 121329898 Hz CPU: Pentium/P54C (121.33-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 94822400 (92600K bytes) Preloaded elf kernel "kernel" at 0xc0302000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030209c. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 ncr0: port 0xec00-0xecff mem 0xfedfbf00-0xfedfbfff irq 11 at device 1.0 on pci0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at 6.0 irq 9 de0: port 0xe880-0xe8ff mem 0xfedfbe80-0xfedfbeff irq 10 at device 8.0 on pci0 de0: DEC DE450-CA 21041 [10Mb/s] pass 1.1 de0: address 00:00:f8:02:76:db atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: 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 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: <16550 compatible COM device> can't assign resources unknown: can't assign resources unknown: can't assign resources Waiting 10 seconds for SCSI devices to settle Mounting root from ufs:/dev/da1s1a cd0 at ncr0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: cd present [329507 x 2048 byte records] da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 1042MB (2134305 512 byte sectors: 255H 63S/T 132C) da2 at ncr0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 3090MB (6328861 512 byte sectors: 255H 63S/T 393C) da1 at ncr0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) de0: enabling BNC port To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 0:28: 2 2000 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 348E937B479 for ; Mon, 20 Nov 2000 00:27:57 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA17346; Mon, 20 Nov 2000 00:27:56 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAK8Rsg70070; Mon, 20 Nov 2000 00:27:54 -0800 (PST) (envelope-from obrien) Date: Mon, 20 Nov 2000 00:27:53 -0800 From: "David O'Brien" To: Mark R Grant Cc: current@FreeBSD.org Subject: Re: Error in libstdc++ buildworld Message-ID: <20001120002753.A70004@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <3A17F7D1.732AB18D@mmcable.com> <20001119082746.A39585@dragon.nuxi.com> <3A180358.652F4AF9@mmcable.com> <20001119084953.A43120@dragon.nuxi.com> <3A181FB7.FBB1A4AC@mmcable.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A181FB7.FBB1A4AC@mmcable.com>; from mark@mmcable.com on Sun, Nov 19, 2000 at 12:45:11PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Nov 19, 2000 at 12:45:11PM -0600, Mark R Grant wrote: > 1. I cleaned up the source directories using "cd /usr ; make cleandir" > 2. I cleaned up the object directories using "cd /usr/obj ; chflags -R > noschg * ; rm -rf *" These two steps should be reversed. The `make cleandir' in #1 will clean out the /usr/obj/<...dir> shadow tree if it exists, else the dir w/in /usr/src/ ``make cleandir && make cleandir'' is the way to ensure that /usr/src is truely clean (or do your step #2 above first). > 4. I decided that since I am too much of a novice at this, I should use the > buildworld and installworld seperately. I ran "cd /usr/src ; make -j2 > buildworld" With -jX (X > 1), you cannot trust any error output. You would be better off not using -j until you know you can build the world. From the output you provide I'm not sure why the /usr/obj/usr/src/i386/mk directory doesn't exist. But please try your step #2, followed by our step #1 and see if this goes away. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 0:35: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 76B5137B479; Mon, 20 Nov 2000 00:35:00 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAK8a0W73948; Mon, 20 Nov 2000 00:36:00 -0800 (PST) (envelope-from kris) Date: Mon, 20 Nov 2000 00:36:00 -0800 From: Kris Kennaway To: Kris Kennaway Cc: Soren Schmidt , Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... Message-ID: <20001120003600.A73879@citusc17.usc.edu> References: <2967.974461715@axl.fw.uunet.co.za> <200011171155.MAA92493@freebsd.dk> <20001117175830.A65059@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001117175830.A65059@citusc17.usc.edu>; from kris@FreeBSD.ORG on Fri, Nov 17, 2000 at 05:58:30PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 17, 2000 at 05:58:30PM -0800, Kris Kennaway wrote: > On Fri, Nov 17, 2000 at 12:55:28PM +0100, Soren Schmidt wrote: >=20 > > > I thought I was the only one, since my question on the freebsd-current > > > mailing list went unanswered. > >=20 > > You are _not_ alone, there has been numerous complains about this > > on the list, but so far they have not been taken seriously :| >=20 > One of my non-SMP machines reliably wedges whenever I do heavy disk > I/O. I can't break to debugger. >=20 > Nov 4 15:46:41 mollari /boot/kernel/kernel: atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 > Nov 4 15:46:41 mollari /boot/kernel/kernel: ata0: at 0x1f0 irq 14 on ata= pci0 > Nov 4 15:46:41 mollari /boot/kernel/kernel: ahc0: port 0xfc00-0xfcff mem 0xffbeb000-0xffbebfff irq 15 at device 1= 1.0 on pci0 > Nov 4 15:46:41 mollari /boot/kernel/kernel: aic7880: Wide Channel A, SCS= I Id=3D7, 16/255 SCBs Well, adding INVARIANTS, INVARIANTS_SUPPORT, MUTEX_DEBUG and WITNESS didn't give me anything to go off. Interestingly though - I thrashed the disks for about 15 minutes to no avail before kldloading random.ko and firing up ssh, at which point it froze within a few minutes while typing. Obviously one data point isn't much to go off, but it might be somewhere to start looking. Kris --mYCpIKhGyMATD0i+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjoY4nAACgkQWry0BWjoQKVKrgCeJJZW0np9QN37+L8nthsXUkeh A4EAoOnjoJrmut0s4xl/W45sXfV5n1Y/ =KQE/ -----END PGP SIGNATURE----- --mYCpIKhGyMATD0i+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 4:23:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from thing.orbitel.bg (thing.orbitel.bg [195.24.32.46]) by hub.freebsd.org (Postfix) with SMTP id 191B737B479 for ; Mon, 20 Nov 2000 04:23:36 -0800 (PST) Received: (qmail 98953 invoked by uid 1001); 20 Nov 2000 12:23:26 -0000 Date: Mon, 20 Nov 2000 14:23:26 +0200 From: Stanislav Grozev To: current@freebsd.org Subject: -current scheduler strangeness Message-ID: <20001120142326.A97732@thing.orbitel.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mojUlQ0s9EVzWg2t" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --mojUlQ0s9EVzWg2t Content-Type: multipart/mixed; boundary="RnlQjJ0d97Da+TV1" Content-Disposition: inline --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, today I upgraded my 5.0-CURRENT from PRE_SMPNG to -current from about 5-6 hours. everything went fine, the system is working, but I now notice the=20 following: whenever I compile something (say a port) and play an mp3 in xmms at the same time, the mp3 playing is frequently interrupted, or loops for a second. when I stop the compile, the mp3 files are playing ok. with PRE_SMPNG I never experienced such behavior, even with 2 or 3 simultaneous compiles. I am attaching the dmesg output and my kernel config file if that would be helpful. as you can see, pcm shows: pcm0: hwptr went backwards 3896 -> 3720 with PRE_SMPNG it didn't show such things, and when I do not load the machi= ne with compiles, it never displays such messages and plays fine. any info will be greatly appreciated. -tacho -- [i don't follow] | [http://daemonz.org/ || tacho@daemonz.org] [everything should be made as simple as possible, but no simpler] 0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339] --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=THING Content-Transfer-Encoding: quoted-printable # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.291 2000/11/15 18:36:24 imp Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident THING maxusers 32 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required #options DEVFS #Device Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=3D15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci #options COMPAT_OLDISA # compatability shims for lnc, le #options COMPAT_OLDPCI # compatability shims for lnc # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device isp # Qlogic family #device ncr # NCR/Symbios Logic #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') #device adv # Advansys scsi adapters #device adw # Advansys wide scsi adapters #device aha 1 # Adaptec 154x scsi adapters #device aic # Adaptec 15[012]x scsi adapters, AIC-6[23]60. #device bt # Buslogic/Mylex MultiMaster scsi adapters #device ncv # NCR 53C500 #device nsp # Workbit Ninja SCSI-3 #device stg # TMC 18C30/18C50 # RAID controllers interfaced to the SCSI subsystem #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID #device dpt # DPT Smartcache III, IV - See NOTES for options! #device mly # Mylex AcceleRAID/eXtremeRAID # SCSI peripherals #device scbus # SCSI bus (required) #device da # Direct Access (disks) #device sa # Sequential Access (tape etc) #device cd # CD #device pass # Passthrough device (direct SCSI access) # RAID controllers #device aac # Adaptec FSA RAID #device amr # AMI MegaRAID #device ida # Compaq Smart RAID #device mlx # Mylex DAC960 family #device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT li= nes #options PCVT_SCANSET=3D2 # IBM keyboards are non-std # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # Add suspend/resume support for the i8254. device pmtimer # Audio support device pcm # PCCARD (PCMCIA) support #device card # pccard bus #device pcic # PCMCIA bridge # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer #device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') #device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #device pcn # AMD Am79C79x PCI 10/100 NICs #device rl # RealTek 8129/8139 #device sf # Adaptec AIC-6915 (``Starfire'') #device sis # Silicon Integrated Systems SiS 900/SiS 7016 #device ste # Sundance ST201 (D-Link DFE-550TX) #device tl # Texas Instruments ThunderLAN #device tx # SMC EtherPower II (83c170 ``EPIC'') #device vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. pccard nics included. #device cs # Crystal Semiconductor CS89x0 NIC #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards #device ex # Intel EtherExpress Pro/10 and Pro/10+ #device ep # Etherlink III based cards #device fe # Fujitsu MB8696x based cards #device sn # SMC's 9000 series of ethernet chips #device xe # Xircom pccard ethernet # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie #device le #device lnc # Wireless NIC cards #device an # Aironet 4500/4800 802.11 wireless NICs.=20 #device awi # BayStack 660 and others #device wi # WaveLAN/IEEE 802.11 wireless NICs.=20 #device wl # Older non 802.11 Wavelan wireless NIC. # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device options NOBLOCKRANDOM # avoid any blocking on device random device loop # Network loopback device ether # Ethernet support #device sl # Kernel SLIP #device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse #device urio # Diamond Rio 500 MP3 player #device uscanner # Scanners # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet device pcm --RnlQjJ0d97Da+TV1 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Mon Nov 20 09:47:33 EET 2000 root@thing.orbitel.bg:/usr/src/sys/compile/THING Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 334093718 Hz CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x660 Stepping = 0 Features=0x183f9ff real memory = 134152192 (131008K bytes) config> q avail memory = 127025152 (124048K bytes) Preloaded elf kernel "kernel" at 0xc0381000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc038109c. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 9 entries at 0xc00fdee0 npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 9 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 irq 9 pci0: at 7.3 xl0: <3Com 3c980 Fast Etherlink XL> port 0xd400-0xd47f mem 0xd9000000-0xd900007f irq 10 at device 13.0 on pci0 xl0: Ethernet address: 00:50:04:13:ad:d0 miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0xe800-0xe8ff,0xe400-0xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 irq 10 at device 19.0 on pci0 ata2: at 0xd800 on atapci1 ata3: at 0xe000 on atapci1 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 6149MB [13328/15/63] at ata0-master UDMA33 Mounting root from ufs:/dev/ad0s1a IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled pcm0: hwptr went backwards 1876 -> 1656 pcm0: hwptr went backwards 1724 -> 1616 pcm0: hwptr went backwards 3896 -> 3720 --RnlQjJ0d97Da+TV1-- --mojUlQ0s9EVzWg2t Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6GRe+3KS+A0T8MzkRAlUpAJ4wQxWo+g43JSvPzGzOal1IEeuubQCfcrTL uE/eJGK6AyUVoalio0pJyRU= =o/vB -----END PGP SIGNATURE----- --mojUlQ0s9EVzWg2t-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 4:25:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from thing.orbitel.bg (thing.orbitel.bg [195.24.32.46]) by hub.freebsd.org (Postfix) with SMTP id A7C8B37B479 for ; Mon, 20 Nov 2000 04:25:44 -0800 (PST) Received: (qmail 3699 invoked by uid 1001); 20 Nov 2000 12:25:43 -0000 Date: Mon, 20 Nov 2000 14:25:43 +0200 From: Stanislav Grozev To: current@freebsd.org Subject: Re: -current scheduler strangeness Message-ID: <20001120142543.B97732@thing.orbitel.bg> References: <20001120142326.A97732@thing.orbitel.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eHhjakXzOLJAF9wJ" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001120142326.A97732@thing.orbitel.bg>; from tacho@orbitel.bg on Mon, Nov 20, 2000 at 02:23:26PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --eHhjakXzOLJAF9wJ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable as a followup, whenever I have disk access the problem shows also... On Mon, Nov 20, 2000 at 02:23:26PM +0200, Stanislav Grozev wrote: > Hi, > today I upgraded my 5.0-CURRENT from PRE_SMPNG to -current from about 5-6 > hours. everything went fine, the system is working, but I now notice the= =20 > following: whenever I compile something (say a port) and play an mp3 > in xmms at the same time, the mp3 playing is frequently interrupted, > or loops for a second. when I stop the compile, the mp3 files are playing > ok. with PRE_SMPNG I never experienced such behavior, even with 2 or 3 > simultaneous compiles. I am attaching the dmesg output and my kernel > config file if that would be helpful. >=20 > as you can see, pcm shows: > pcm0: hwptr went backwards 3896 -> 3720 >=20 > with PRE_SMPNG it didn't show such things, and when I do not load the mac= hine > with compiles, it never displays such messages and plays fine. >=20 > any info will be greatly appreciated. >=20 > -tacho >=20 > # > # GENERIC -- Generic kernel configuration file for FreeBSD/i386 > # > # For more information on this file, please read the handbook section on > # Kernel Configuration Files: > # > # http://www.FreeBSD.org/handbook/kernelconfig-config.html > # > # The handbook is also available locally in /usr/share/doc/handbook > # if you've installed the doc distribution, otherwise always see the > # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the > # latest information. > # > # An exhaustive list of options and more detailed explanations of the > # device lines is also present in the NOTES configuration file. If you are > # in doubt as to the purpose or necessity of a line, check first in NOTES. > # > # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.291 2000/11/15 18:36:24 imp Exp= $ >=20 > machine i386 > #cpu I386_CPU > #cpu I486_CPU > #cpu I586_CPU > cpu I686_CPU > ident THING > maxusers 32 >=20 > #To statically compile in device wiring instead of /boot/device.hints > #hints "GENERIC.hints" #Default places to look for devices. >=20 > #makeoptions DEBUG=3D-g #Build kernel with gdb(1) debug symbols >=20 > #options MATH_EMULATE #Support for x87 emulation > options INET #InterNETworking > options INET6 #IPv6 communications protocols > options FFS #Berkeley Fast Filesystem > options FFS_ROOT #FFS usable as root device [keep this!] > options SOFTUPDATES #Enable FFS soft updates support > options MFS #Memory Filesystem > options MD_ROOT #MD is a potential root device > options NFS #Network Filesystem > options NFS_ROOT #NFS usable as root device, NFS required > options MSDOSFS #MSDOS Filesystem > options CD9660 #ISO 9660 Filesystem > options CD9660_ROOT #CD-ROM usable as root, CD9660 required > #options DEVFS #Device Filesystem > options PROCFS #Process filesystem > options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] > options SCSI_DELAY=3D15000 #Delay (in ms) before probing SCSI > options UCONSOLE #Allow users to grab the console > options USERCONFIG #boot -c editor > options VISUAL_USERCONFIG #visual boot -c editor > options KTRACE #ktrace(1) support > options SYSVSHM #SYSV-style shared memory > options SYSVMSG #SYSV-style message queues > options SYSVSEM #SYSV-style semaphores > options P1003_1B #Posix P1003_1B real-time extensions > options _KPOSIX_PRIORITY_SCHEDULING > options KBD_INSTALL_CDEV # install a CDEV entry in /dev >=20 > # To make an SMP kernel, the next two are needed > #options SMP # Symmetric MultiProcessor Kernel > #options APIC_IO # Symmetric (APIC) I/O >=20 > device isa > #device eisa > device pci > #options COMPAT_OLDISA # compatability shims for lnc, le > #options COMPAT_OLDPCI # compatability shims for lnc >=20 > # Floppy drives > device fdc >=20 > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device atapicd # ATAPI CDROM drives > #device atapifd # ATAPI floppy drives > #device atapist # ATAPI tape drives > options ATA_STATIC_ID #Static device numbering > options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices >=20 > # SCSI Controllers > #device ahb # EISA AHA1742 family > #device ahc # AHA2940 and onboard AIC7xxx devices > #device amd # AMD 53C974 (Teckram DC-390(T)) > #device isp # Qlogic family > #device ncr # NCR/Symbios Logic > #device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') >=20 > #device adv # Advansys scsi adapters > #device adw # Advansys wide scsi adapters > #device aha 1 # Adaptec 154x scsi adapters > #device aic # Adaptec 15[012]x scsi adapters, AIC-6[23]60. > #device bt # Buslogic/Mylex MultiMaster scsi adapters >=20 > #device ncv # NCR 53C500 > #device nsp # Workbit Ninja SCSI-3 > #device stg # TMC 18C30/18C50 >=20 > # RAID controllers interfaced to the SCSI subsystem > #device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID > #device dpt # DPT Smartcache III, IV - See NOTES for options! > #device mly # Mylex AcceleRAID/eXtremeRAID >=20 > # SCSI peripherals > #device scbus # SCSI bus (required) > #device da # Direct Access (disks) > #device sa # Sequential Access (tape etc) > #device cd # CD > #device pass # Passthrough device (direct SCSI access) >=20 > # RAID controllers > #device aac # Adaptec FSA RAID > #device amr # AMI MegaRAID > #device ida # Compaq Smart RAID > #device mlx # Mylex DAC960 family > #device twe # 3ware ATA RAID >=20 > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc 1 # At keyboard controller > device atkbd # at keyboard > device psm # psm mouse >=20 > device vga # VGA screen >=20 > # splash screen/screen saver > device splash >=20 > # syscons is the default console driver, resembling an SCO console > device sc 1 >=20 > # Enable this for the pcvt (VT220 compatible) console driver > #device vt > #options XSERVER # support for X server on a vt console > #options FAT_CURSOR # start with block cursor > # If you have a ThinkPAD, uncomment this along with the rest of the PCVT = lines > #options PCVT_SCANSET=3D2 # IBM keyboards are non-std >=20 > # Floating point support - do not disable. > device npx >=20 > # Power management support (see NOTES for more options) > device apm > # Add suspend/resume support for the i8254. > device pmtimer >=20 > # Audio support > device pcm >=20 > # PCCARD (PCMCIA) support > #device card # pccard bus > #device pcic # PCMCIA bridge >=20 > # Serial (COM) ports > device sio # 8250, 16[45]50 based serial ports >=20 > # Parallel port > device ppc > device ppbus # Parallel port bus (required) > device lpt # Printer > #device plip # TCP/IP over parallel > device ppi # Parallel port interface device > #device vpo # Requires scbus and da >=20 >=20 > # PCI Ethernet NICs. > #device de # DEC/Intel DC21x4x (``Tulip'') > #device fxp # Intel EtherExpress PRO/100B (82557, 82558) > #device vx # 3Com 3c590, 3c595 (``Vortex'') > #device wx # Intel Gigabit Ethernet Card (``Wiseman'') >=20 > # PCI Ethernet NICs that use the common MII bus controller code. > # NOTE: Be sure to keep the 'device miibus' line in order to use these NI= Cs! > device miibus # MII bus support > #device dc # DEC/Intel 21143 and various workalikes > #device pcn # AMD Am79C79x PCI 10/100 NICs > #device rl # RealTek 8129/8139 > #device sf # Adaptec AIC-6915 (``Starfire'') > #device sis # Silicon Integrated Systems SiS 900/SiS 7016 > #device ste # Sundance ST201 (D-Link DFE-550TX) > #device tl # Texas Instruments ThunderLAN > #device tx # SMC EtherPower II (83c170 ``EPIC'') > #device vr # VIA Rhine, Rhine II > #device wb # Winbond W89C840F > device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') >=20 > # ISA Ethernet NICs. pccard nics included. > #device cs # Crystal Semiconductor CS89x0 NIC > #device ed # NE[12]000, SMC Ultra, 3c503, DS8390 cards > #device ex # Intel EtherExpress Pro/10 and Pro/10+ > #device ep # Etherlink III based cards > #device fe # Fujitsu MB8696x based cards > #device sn # SMC's 9000 series of ethernet chips > #device xe # Xircom pccard ethernet >=20 > # The probe order of these is presently determined by i386/isa/isa_compat= .c. > #device ie > #device le > #device lnc >=20 > # Wireless NIC cards > #device an # Aironet 4500/4800 802.11 wireless NICs.=20 > #device awi # BayStack 660 and others > #device wi # WaveLAN/IEEE 802.11 wireless NICs.=20 > #device wl # Older non 802.11 Wavelan wireless NIC. >=20 > # Pseudo devices - the number indicates how many units to allocated. > device random # Entropy device > options NOBLOCKRANDOM # avoid any blocking on device random > device loop # Network loopback > device ether # Ethernet support > #device sl # Kernel SLIP > #device ppp 1 # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif 4 # IPv6 and IPv4 tunneling > device faith 1 # IPv6-to-IPv4 relaying (translation) >=20 > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > device bpf # Berkeley packet filter >=20 > # USB support > #device uhci # UHCI PCI->USB interface > #device ohci # OHCI PCI->USB interface > #device usb # USB Bus (required) > #device udbp # USB Double Bulk Pipe devices > #device ugen # Generic > #device uhid # "Human Interface Devices" > #device ukbd # Keyboard > #device ulpt # Printer > #device umass # Disks/Mass storage - Requires scbus and da > #device ums # Mouse > #device urio # Diamond Rio 500 MP3 player > #device uscanner # Scanners > # USB Ethernet, requires mii > #device aue # ADMtek USB ethernet > #device cue # CATC USB ethernet > #device kue # Kawasaki LSI USB ethernet >=20 > device pcm > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 5.0-CURRENT #0: Mon Nov 20 09:47:33 EET 2000 > root@thing.orbitel.bg:/usr/src/sys/compile/THING > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 334093718 Hz > CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x660 Stepping =3D 0 > Features=3D0x183f9ff > real memory =3D 134152192 (131008K bytes) > config> q > avail memory =3D 127025152 (124048K bytes) > Preloaded elf kernel "kernel" at 0xc0381000. > Preloaded userconfig_script "/boot/kernel.conf" at 0xc038109c. > Pentium Pro MTRR support enabled > md0: Malloc disk > Using $PIR table, 9 entries at 0xc00fdee0 > npx0: on motherboard > npx0: INT 16 interface > pcib0: at pcibus 0 on motherb= oard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > pci1: at 0.0 irq 9 > isab0: at device 7.0 on pci0 > isa0: on isab0 > atapci0: port 0xf000-0xf00f at device 7.1 = on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > ata1: at 0x170 irq 15 on atapci0 > pci0: at 7.2 irq 9 > pci0: at 7.3 > xl0: <3Com 3c980 Fast Etherlink XL> port 0xd400-0xd47f mem 0xd9000000-0xd= 900007f irq 10 at device 13.0 on pci0 > xl0: Ethernet address: 00:50:04:13:ad:d0 > miibus0: on xl0 > xlphy0: <3Com internal media interface> on miibus0 > xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > atapci1: port 0xe800-0xe8ff,0xe400-0= xe403,0xe000-0xe007,0xdc00-0xdc03,0xd800-0xd807 irq 10 at device 19.0 on pc= i0 > ata2: at 0xd800 on atapci1 > ata3: at 0xe000 on atapci1 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-= 0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > unknown: can't assign resources > ad0: 6149MB [13328/15/63] at ata0-master UDMA33 > Mounting root from ufs:/dev/ad0s1a > IP packet filtering initialized, divert disabled, rule-based forwarding d= isabled, default to deny, logging disabled > pcm0: hwptr went backwards 1876 -> 1656 > pcm0: hwptr went backwards 1724 -> 1616 > pcm0: hwptr went backwards 3896 -> 3720 -tacho -- [i don't follow] | [http://daemonz.org/ || tacho@daemonz.org] [everything should be made as simple as possible, but no simpler] 0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339] --eHhjakXzOLJAF9wJ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6GRhG3KS+A0T8MzkRAg44AJ9Ky/IIDsvsGxRk1VXHV5ksZcQ+ygCfWUOt 95JyIQUgv6BmleEITuRnpvE= =V9xS -----END PGP SIGNATURE----- --eHhjakXzOLJAF9wJ-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 4:38:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from blizzard.sabbo.net (ns.sabbo.net [193.193.218.18]) by hub.freebsd.org (Postfix) with ESMTP id 1AB3837B479 for ; Mon, 20 Nov 2000 04:38:05 -0800 (PST) Received: from vic.sabbo.net (root@vic.sabbo.net [193.193.218.109]) by blizzard.sabbo.net (8.10.1/8.10.1) with ESMTP id eAKCblX25400; Mon, 20 Nov 2000 14:37:54 +0200 Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vic.sabbo.net (8.11.1/8.9.3) with ESMTP id eAKCbo047341; Mon, 20 Nov 2000 14:37:50 +0200 (EET) (envelope-from sobomax@FreeBSD.org) Message-ID: <3A191B13.60A7C199@FreeBSD.org> Date: Mon, 20 Nov 2000 14:37:39 +0200 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Stanislav Grozev Cc: current@FreeBSD.org Subject: Re: -current scheduler strangeness References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stanislav Grozev wrote: > as a followup, whenever I have disk access the problem shows also... > > > > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 It could be due to my commit in which I reduced buffer size in mss driver from 64K to 4K. Please try to increase it to 8KB, 16KB etc and let me know if it helps ("#define MSS_BUFFSIZE (4096)" line in src/sys/dev/sound/isa/mss.c). -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 5: 4:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id C579837B4C5 for ; Mon, 20 Nov 2000 05:04:38 -0800 (PST) Received: from victoria-203.budapest.interware.hu ([195.70.63.203] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xqcf-0002sG-00; Mon, 20 Nov 2000 14:04:37 +0100 Message-ID: <3A192161.7186C803@elischer.org> Date: Mon, 20 Nov 2000 05:04:33 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Stanislav Grozev Cc: current@freebsd.org Subject: Re: -current scheduler strangeness References: <20001120142326.A97732@thing.orbitel.bg> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stanislav Grozev wrote: > > Hi, > today I upgraded my 5.0-CURRENT from PRE_SMPNG to -current from about 5-6 > hours. everything went fine, the system is working, but I now notice the > following: whenever I compile something (say a port) and play an mp3 > in xmms at the same time, the mp3 playing is frequently interrupted, > or loops for a second. when I stop the compile, the mp3 files are playing > ok. with PRE_SMPNG I never experienced such behavior, even with 2 or 3 > simultaneous compiles. I am attaching the dmesg output and my kernel > config file if that would be helpful. > > as you can see, pcm shows: > pcm0: hwptr went backwards 3896 -> 3720 I get this too. However for me it's related to using the mouse (though maybe using the mose uses CPU and it's actually CPU....) I'm using the snd_maestro module. This has been happenning since before the SMPNG tag was layed down so it's not related to the new SMP code.. > > with PRE_SMPNG it didn't show such things, and when I do not load the machine > with compiles, it never displays such messages and plays fine. > > any info will be greatly appreciated. > > -tacho > > -- > [i don't follow] | [http://daemonz.org/ || tacho@daemonz.org] > [everything should be made as simple as possible, but no simpler] > 0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339] > > ------------------------------------------------------------------------ > Name: THING > THING Type: Plain Text (text/plain) > Encoding: quoted-printable > > dmesgName: dmesg > Type: Plain Text (text/plain) > > Part 1.2Type: application/pgp-signature -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 5:22: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from thing.orbitel.bg (thing.orbitel.bg [195.24.32.46]) by hub.freebsd.org (Postfix) with SMTP id 18E7A37B479 for ; Mon, 20 Nov 2000 05:21:59 -0800 (PST) Received: (qmail 19964 invoked by uid 1001); 20 Nov 2000 13:21:55 -0000 Date: Mon, 20 Nov 2000 15:21:55 +0200 From: Stanislav Grozev To: Maxim Sobolev Cc: current@freebsd.org Subject: Re: -current scheduler strangeness Message-ID: <20001120152154.A644@thing.orbitel.bg> References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xHFwDpU9dbj6ez1V" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A191B13.60A7C199@FreeBSD.org>; from sobomax@FreeBSD.org on Mon, Nov 20, 2000 at 02:37:39PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 20, 2000 at 02:37:39PM +0200, Maxim Sobolev wrote: > > > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x= 330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 >=20 > It could be due to my commit in which I reduced buffer size in mss driver= from 64K to 4K. Please try to increase it to 8KB, 16KB etc and let me know= if it > helps ("#define MSS_BUFFSIZE (4096)" line in src/sys/dev/sound/isa/mss.c). >=20 the results: 8k - plays absolute garbage (this is strange, because with 4k it plays musi= c, but skips) 16k - plays music, the skips aren't so often heard as with 4k, but are often enough to be annoying 32k - everything plays fine, even with 3 compilations and heavy disk access. so, thanks for the quick answer - I will now keep it at 32k, i don't know the rationale of downing this to 4k. maybe you should commit it to 32k in the repo too? -tacho -- [i don't follow] | [http://daemonz.org/ || tacho@daemonz.org] [everything should be made as simple as possible, but no simpler] 0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339] --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE6GSVy3KS+A0T8MzkRAsaLAJ4kp0tln7MFYK8gY6HQjWpanx5GsACfTXmj pib8xptAqw40YzGjrDZcvr0= =+6Hn -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 5:35:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 0E2DF37B479; Mon, 20 Nov 2000 05:35:45 -0800 (PST) Received: from victoria-203.budapest.interware.hu ([195.70.63.203] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13xr6l-0004wM-00; Mon, 20 Nov 2000 14:35:43 +0100 Message-ID: <3A1928AC.E627E639@elischer.org> Date: Mon, 20 Nov 2000 05:35:40 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: Stanislav Grozev Cc: Maxim Sobolev , current@freebsd.org Subject: Re: -current scheduler strangeness References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> <20001120152154.A644@thing.orbitel.bg> Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Stanislav Grozev wrote: > > On Mon, Nov 20, 2000 at 02:37:39PM +0200, Maxim Sobolev wrote: > > > > pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38b,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 > > > > It could be due to my commit in which I reduced buffer size in mss driver from 64K to 4K. Please try to increase it to 8KB, 16KB etc and let me know if it > > helps ("#define MSS_BUFFSIZE (4096)" line in src/sys/dev/sound/isa/mss.c). > > > > the results: > > 8k - plays absolute garbage (this is strange, because with 4k it plays music, > but skips) > 16k - plays music, the skips aren't so often heard as with 4k, but are > often enough to be annoying > 32k - everything plays fine, even with 3 compilations and heavy disk access. > > so, thanks for the quick answer - I will now keep it at 32k, i don't know > the rationale of downing this to 4k. maybe you should commit it to 32k in > the repo too? Maybe it should be self tuning according to the speed of the data. I don't understand why the hwptr would go backwards due to system load.. if this is an underflow, then the message should say so... > > -tacho > > -- > [i don't follow] | [http://daemonz.org/ || tacho@daemonz.org] > [everything should be made as simple as possible, but no simpler] > 0x44FC3339 || [02B5 798B 4BD1 97FB F8DB 72E4 DCA4 BE03 44FC 3339] > > ------------------------------------------------------------------------ > Part 1.2Type: application/pgp-signature -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 6:43:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 9877237B479 for ; Mon, 20 Nov 2000 06:43:46 -0800 (PST) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.3+Sun/SMI-SVR4) id PAA04226; Mon, 20 Nov 2000 15:43:28 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 3.12 #1 (Debian)) id 13xsAK-0006QO-00 for ; Mon, 20 Nov 2000 15:43:28 +0100 Date: Mon, 20 Nov 2000 15:43:27 +0100 From: Szilveszter Adam To: current@freebsd.org Subject: Re: -current scheduler strangeness Message-ID: <20001120154327.C16019@petra.hos.u-szeged.hu> Mail-Followup-To: Szilveszter Adam , current@freebsd.org References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> <20001120152154.A644@thing.orbitel.bg> <3A1928AC.E627E639@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A1928AC.E627E639@elischer.org>; from julian@elischer.org on Mon, Nov 20, 2000 at 05:35:40AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 20, 2000 at 05:35:40AM -0800, Julian Elischer wrote: > Maybe it should be self tuning according to the speed of the data. > I don't understand why the hwptr would go backwards due to system load.. > if this is an underflow, then the message should say so... Just FYI, I also get this behaviour with my SB 64 AWE ISA PnP card and a recent -CURRENT. The 'hwptr went backwards' messages are triggered most often by heavy disk access (esp CVS operations), compiles and using the Linux emulation, but sometimes by using the mouse on the console as well (this is a serial mouse) Of course, bloated software makes things worse, so RealPlayer is a really bad offender. The messages did not start with SMPNG but got a *lot* more frequent in the last couple of weeks, making listening to mp3-s a real annoyance during any more serious system activity. (Earlier, ie in the early fall and in the summer) these messages were almost never seen while in console mode, but only with X and RealPlayer messing things up. The sound card works fine otherwise. (have not tried recording.) (just my HUF 0.02:-) -- Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 7:43:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhub.fokus.gmd.de (mailhub.fokus.gmd.de [193.174.154.14]) by hub.freebsd.org (Postfix) with ESMTP id DF63837B479 for ; Mon, 20 Nov 2000 07:43:45 -0800 (PST) Received: from beagle (beagle [193.175.132.100]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id QAA25583 for ; Mon, 20 Nov 2000 16:43:43 +0100 (MET) Date: Mon, 20 Nov 2000 16:43:43 +0100 (CET) From: Harti Brandt To: current@freebsd.org Subject: Re: binutils commit breaks kernel builds? In-Reply-To: <20001115144941.A34327@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Nov 2000, David O'Brien wrote: > On Wed, Nov 15, 2000 at 04:15:55PM +0100, Harti Brandt wrote: > > with fresh sources from today 6:00 MET kernel builds fail. The victim is > > I'm done with the upgrade - you may have easily CVSuped during the > upgrade process. Can you wait an hour or so, CVSup again and see if you > still see the problem? > > Is anyone else experience[31~ing this? Well, I cvsuped twice and it didn't work. But today everything is fine. Thanks, harti -- harti brandt, http://www.fokus.gmd.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.gmd.de, harti@begemot.org, lhbrandt@mail.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 7:51:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id A75C837B479; Mon, 20 Nov 2000 07:51:13 -0800 (PST) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id eAKFp1J19623; Mon, 20 Nov 2000 17:51:01 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200011201551.eAKFp1J19623@gratis.grondar.za> To: Kris Kennaway Cc: Soren Schmidt , Sheldon Hearn , Alfred Perlstein , "Steven E. Ames" , Boris Popov , Valentin Chopov , current@FreeBSD.ORG Subject: Re: CURRENT is freezing again ... References: <20001120003600.A73879@citusc17.usc.edu> In-Reply-To: <20001120003600.A73879@citusc17.usc.edu> ; from Kris Kennaway "Mon, 20 Nov 2000 00:36:00 PST." Date: Mon, 20 Nov 2000 17:51:00 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Interestingly though - I thrashed the disks for about 15 minutes to no > avail before kldloading random.ko and firing up ssh, at which point it > froze within a few minutes while typing. Obviously one data point > isn't much to go off, but it might be somewhere to start looking. Now that I've (almost) cleared get_cyclecounter(9) out of my TODO, I can use it, and then go about getting rid of most malloc(9)s and all TAILQs in random.ko. 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 Mon Nov 20 10: 2:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id E326537B479 for ; Mon, 20 Nov 2000 10:02:30 -0800 (PST) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAKI28I72996 for ; Mon, 20 Nov 2000 10:02:08 -0800 (PST) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Subject: USW2 Root: -current build report for Mon Nov 20 02:06:26 CST 2000 Date: Mon, 20 Nov 2000 10:02:08 -0800 Message-ID: <72993.974743328@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kaboom. Looks like the fixes to perl unfixed the release. ------- Forwarded Message Return-Path: root@usw2.freebsd.org Delivery-Date: Mon Nov 20 05:13:27 2000 Return-Path: Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAKDDRI71931 for ; Mon, 20 Nov 2000 05:13:27 -0800 (PST) (envelope-from root@usw2.freebsd.org) Received: from hub.freebsd.org (hub.FreeBSD.org [216.136.204.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 403446E253D for ; Mon, 20 Nov 2000 05:13:48 -0800 (PST) Received: by hub.freebsd.org (Postfix) id 30F8637B4C5; Mon, 20 Nov 2000 05:13:48 -0800 (PST) Delivered-To: jkh@freebsd.org Received: from usw2.freebsd.org (usw2.freebsd.org [209.180.6.226]) by hub.freebsd.org (Postfix) with ESMTP id B2B5337B479 for ; Mon, 20 Nov 2000 05:13:47 -0800 (PST) Received: (from root@localhost) by usw2.freebsd.org (8.11.1/8.11.0) id eAKDDlw23230 for build-reports@freebsd.org; Mon, 20 Nov 2000 07:13:47 -0600 (CST) (envelope-from root) Date: Mon, 20 Nov 2000 07:13:47 -0600 (CST) From: USW2 Root Message-Id: <200011201313.eAKDDlw23230@usw2.freebsd.org> To: build-reports@freebsd.org Subject: -current build report for Mon Nov 20 02:06:26 CST 2000 Doing nightly build attempt for 5.0-20001120-CURRENT at Mon Nov 20 02:06:26 CST 2000 Updating source tree... Making release... Release build of 5.0-20001120-CURRENT was an abject failure. install -c -o root -g wheel -m 444 libperl_p.a /R/stage/trees/bin/usr/lib install -c -s -o root -g wheel -m 444 libperl.so.4 /R/stage/trees/bin/usr/lib ln -sf libperl.so.4 /R/stage/trees/bin/usr/lib/libperl.so ===> gnu/usr.bin/perl/perl cd /usr/src/gnu/usr.bin/perl/perl ; make install DESTDIR=/R/stage/trees/bin SHARED=copies install -c -s -o root -g wheel -m 555 perl /R/stage/trees/bin/usr/bin /R/stage/trees/bin/usr/bin/perl5 -> /R/stage/trees/bin/usr/bin/perl /R/stage/trees/bin/usr/bin/perl5.6.0 -> /R/stage/trees/bin/usr/bin/perl ===> gnu/usr.bin/perl/suidperl cd /usr/src/gnu/usr.bin/perl/suidperl ; make install DESTDIR=/R/stage/trees/bin SHARED=copies install -c -s -o root -g wheel -m 511 suidperl /R/stage/trees/bin/usr/bin /R/stage/trees/bin/usr/bin/sperl5 -> /R/stage/trees/bin/usr/bin/suidperl /R/stage/trees/bin/usr/bin/sperl5.6.0 -> /R/stage/trees/bin/usr/bin/suidperl ===> gnu/usr.bin/perl/library cd /usr/src/gnu/usr.bin/perl/library ; make install DESTDIR=/R/stage/trees/bin SHARED=copies ===> gnu/usr.bin/perl/library/B miniperl: not found *** Error code 127 Stop in /usr/obj/usr/src/gnu/usr.bin/perl/library/B/ext/B. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/library/B. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/library. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl/library. *** Error code 1 Stop in /usr/src/gnu/usr.bin/perl. *** Error code 1 Stop in /usr/src/gnu/usr.bin. *** Error code 1 Stop in /usr/src/gnu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 11:57: 8 2000 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 F079137B4C5; Mon, 20 Nov 2000 11:57:04 -0800 (PST) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA21255; Mon, 20 Nov 2000 11:57:04 -0800 (PST) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.0/8.11.0) id eAKJv3C69131; Mon, 20 Nov 2000 11:57:03 -0800 (PST) (envelope-from jdp) Date: Mon, 20 Nov 2000 11:57:03 -0800 (PST) Message-Id: <200011201957.eAKJv3C69131@vashon.polstra.com> To: current@freebsd.org From: John Polstra Reply-To: current@freebsd.org Cc: obrien@freebsd.org Subject: Re: Error in libstdc++ buildworld In-Reply-To: <20001119084953.A43120@dragon.nuxi.com> References: <3A17F7D1.732AB18D@mmcable.com> <20001119082746.A39585@dragon.nuxi.com> <3A180358.652F4AF9@mmcable.com> <20001119084953.A43120@dragon.nuxi.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <20001119084953.A43120@dragon.nuxi.com>, David O'Brien wrote: > One cannot "upgrade"[*] to -CURRENT using he "RELENG_4" tag. The > "RELENG_4" is the 4.x code base. To get -CURRENT source one would use no > tag. Not correct! One should use "tag=.". If he uses no tag then he'll get the RCS files. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 12:50:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 9259037B4C5 for ; Mon, 20 Nov 2000 12:50:48 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id BF12CC5; Mon, 20 Nov 2000 12:50:45 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id MAA11395; Mon, 20 Nov 2000 12:50:36 -0800 (PST) Message-ID: <3A198E9B.71DB602D@cup.hp.com> Date: Mon, 20 Nov 2000 12:50:35 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Jordan Hubbard Cc: current@FreeBSD.ORG Subject: Re: USW2 Root: -current build report for Mon Nov 20 02:06:26 CST 2000 References: <72993.974743328@winston.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan Hubbard wrote: > > Kaboom. Looks like the fixes to perl unfixed the release. I'll take a look at it. I tested a buildworld and an installworld, so this failure is unexpected. I don't have an explanation yet. This can take a couple of hours... -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 12:57:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from spock.org (cm-24-169-11-24.nycap.rr.com [24.169.11.24]) by hub.freebsd.org (Postfix) with ESMTP id 4A3F637B479; Mon, 20 Nov 2000 12:57:52 -0800 (PST) Received: (from jon@localhost) by spock.org serial EF600Q3T-B7F; Mon, 20 Nov 2000 15:57:47 -0500 (EST) (envelope-from jon) Date: Mon, 20 Nov 2000 15:57:47 -0500 From: Jonathan Chen To: "Justin T. Gibbs" Cc: jon@FreeBSD.org, imp@FreeBSD.org, current@FreeBSD.org Subject: Re: Cardbus fixes Message-ID: <20001120155746.A2669@spock.org> References: <200011190505.eAJ552428239@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: telnet/1.1x In-Reply-To: <200011190505.eAJ552428239@aslan.scsiguy.com>; from gibbs@scsiguy.com on Sat, Nov 18, 2000 at 10:05:01PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been side tracked for a long time since after the con with various more urgant things to do, and have left the cardbus stuff along for a while, but now that thanksgiving is near, I might have some more time to work on this... On Sat, Nov 18, 2000 at 10:05:01PM -0700, Justin T. Gibbs wrote: > While working on getting the APA-1480 to work under FreeBSD's new > cardbus support, I ran into several issues. > > 1) When mucking with mapping registers, it is best to *not* have > io or memory space access enabled. This patch defers the setting > of these bits until after all of the mapping registers are probed. > It might be even better to defer this until a particular mapping > is activated and to disable that type of access when a new > register is activated. Good... > 2) The PCI spec is very explicit about how mapping registers and > the expansion ROM mapping register should be probed. This patch > makes cardbus_add_map() follow the spec. Gook... > 3) The PCI spec allows a device to use the same address decoder for > expansion ROM access as is used for memory mapped register access. > This patch carefully enables and disables ROM access along with > resource (de)activiation. Hmm... I didn't think of this... > 4) The cardbus CIS code treats the CIS_PTR as a mapping register if > it is mentioned in the CIS. I don't have a spec handy to understand > why the CIS_PTR is mentioned in the CIS, but allocating a memory range > for it is certainly bogus. My patch ignores bar #6 to prevent the > mapping. > > 5) The CIS code allocated duplicate resources to those already found > by cardbus_add_resources(). The fix is to pass in the bar computed > from the CIS instead of the particular resource ID for that bar, > so bus_generic_alloc_resource succeeds in finding the old resource. > It seems somewhat strange that we have to have two methods for > finding and activating the mapping registers. Isn't one method > sufficient? > > 6) cardbus_read_exrom_cis() failed to advance correctly to higer rom > images. To effect the fix, the cis_ptr value must be provided to > the different CIS reading methods, unaltered. > > 7) The CIS code seems to use the wrong bit to determine rather a particular > register mapping is for I/O or memory space. From looking at the > two cards I have, it seems TPL_BAR_REG_AS should be 0x10 instead > of 0x08. Otherwise, all registers that should be I/O mapped gain > a second mapping in memory space. Okay... CIS stuff is nasty in the current code. Basically - First, the whole CIS reading needs to be rewritten. The current practice of reading the whole rom then passing it to various functions is bad because it would fail for CIS tuples that should make the reader jump around, say, to another rom image or whatever. Second, the BAR mapping stuff, yes, it is wrong. I don't know where I got the idea of doing it wrong in the first place... too much coding late at night without proper documentation I guess... I've had a fix sitting on my local tree for a while, and will commit that soon-ish. And lastly, as for why we need to read the BAR at all, I thought about this briefly when I first wrote the code and came up with the logic that there might be some random cardbus device that stuck a BAR outside of the normal registers but still had the proper mapping in the CIS. For "normal" cards this additional mapping doesn't do anything as they are already mapped. This attempt at mapping BARs using both the PCI and the CIS methods has made the resource allocation functions more ugly than it needs to be. I'm wondering if perhaps one of the two should just be left out. > 8) The cardbus bridge code leaves memory space prefetching enabled. > Prefetching is only allowed if the target device indicates (through > its mapping register) that prefetching is allowable. My patch > simply disables prefetching and includes code to detect this capability > and pass an RF flag to enable it, but nothing more. Good... I was wondering whether I should leave that enabled or not. > 9) The pccbb code was impoperly handling the I/O and mem range limit > registers. The limit register indicates the highest valid address > in the window, not the first invalid address outside the window. Oops... > One last thing that is started here is an attempt to rely more heavily > on PCI register definitions and eventually functions, to get things > done. The cardbus code duplicates a lot of functionality that is > already available in the pci code (mapping register size/type detection). Good. > One other thing that struck me while I was looking at this was that > the resource manager should be providing the "resource pooling" > that pccbb_cardbus_auto_open() emulates. Although the cardbus > bridges we support only provide 4K granularity for memory mapped > windows, things like external rom access often can be mapped on > 2K boundaries. This could allow the resource manager to allocate > a range that doesn't appear to overlap with another allocation but > does due to the bridges constraints. I might look into adding the > concept of hierarchical resource pools to the resource manager so > that, for example, the cardbus bridges pool will always grow in > 4K increments from its parent resource pool. The parent would then > grow according to its own requirements, etc. This will be very cool... -- (o_ 1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2-1-2 _o) \\\_\ Jonathan Chen jon@spock.org /_/// <____) No electrons were harmed during production of this message (____> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 13:31:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15]) by hub.freebsd.org (Postfix) with ESMTP id 1B70B37B711 for ; Mon, 20 Nov 2000 13:30:55 -0800 (PST) Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch2.nortel.com; Mon, 20 Nov 2000 15:26:24 -0600 Received: from zrchb211.us.nortel.com ([47.100.128.40]) by zrchb213.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W57YWBFX; Mon, 20 Nov 2000 15:30:34 -0600 Received: from zrchb211.us.nortel.com ([47.100.128.40]) by zrchb211.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W7VSJA3W; Mon, 20 Nov 2000 15:30:33 -0600 Received: from americasm01.nt.com (zngds004.us.nortel.com [47.124.160.58]) by zrchb211.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W7VSJA34; Mon, 20 Nov 2000 15:30:33 -0600 Message-ID: <3A199800.E16A322F@americasm01.nt.com> Date: Mon, 20 Nov 2000 15:30:40 -0600 From: "Michael Brune" Organization: Nortel Networks X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Problem Compiling Kernel Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Orig: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I CVSup'ed the sources today, built and installed world and everything was fine. When I tried to compile the kernel, I recieve this error when I do the 'make depend' ./aicasm -nostdinc -I- -I. -I../../ -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -I../../cam/scsi -I../../dev/aic7xxx -o aic7xxx_seq.h -r aic7xxx_reg.h ../../dev/aic7xxx/aic7xxx.seq ./aicasm: Stopped at file ../../dev/aic7xxx/aic7xxx.seq, line 81 - syntax error ./aicasm: Removing aic7xxx_seq.h due to error ./aicasm: Removing aic7xxx_reg.h due to error *** Error code 65 I looked at the file aic7xxx.seq on line 81, but I did not see any errors. This is on a Dell Latitude 600 PIII. Please let me know if anyone has a suggestion or needs more information. Thanks in advance! Corey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 17:30:13 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 679C837B4D7; Mon, 20 Nov 2000 17:30:10 -0800 (PST) Subject: Getting at cardbus CIS data from inside drivers To: freebsd-current@freebsd.org Date: Mon, 20 Nov 2000 17:30:10 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20001121013010.679C837B4D7@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay. Recently, David O'Brien handed me an Intel 10/100 Cardbus NIC, which uses the 21143-PB chip. It's a non-MII card (has a Quality Semi symbol PHY). Unfortunately, it looks like Intel has taken a few shortcuts with this card: the serial EEPROM doesn't contain any useful information. Instead, the MAC address and, I presume, the GPIO programming info is stored in the CIS. When the card is inserted, the cardbus code prints out several 'Function Extension' lines, one of which contains the MAC address. The problem is, there's no way for me to obtain this info from inside the driver, unless I map the expansion ROM directly and grovel through the CIS myself, which I don't want to do. I have the card working at the moment using a couple of ugly cheats: I programmed the MAC address in manually using ifconfig dc0 ether blah, and I brute forced the GPIO settings so that all of the pins are configured as outputs and are forced to 1's. This seems to be enough to activate the transceiver, and I can exchange traffic. (I'm composing this e-mail with it right now.) The LED programming is still off though: both LEDs are lit green, and stay on regardless of link indication or speed. Is there any support planned for externalizing the CIS info somehow, i.e. by providing bus methods to call the CIS parsing routines? Another way to do it would be to pass the info down to the child device using ivars. I would imaging that there's similar support for this in Windows, otherwise Intel's driver wouldn't work. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Nov 20 19:27: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AC91037B479; Mon, 20 Nov 2000 19:27:04 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAL3R3Q28487; Mon, 20 Nov 2000 20:27:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA30567; Mon, 20 Nov 2000 20:27:02 -0700 (MST) Message-Id: <200011210327.UAA30567@harmony.village.org> To: wpaul@FreeBSD.ORG (Bill Paul) Subject: Re: Getting at cardbus CIS data from inside drivers Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Nov 2000 17:30:10 PST." <20001121013010.679C837B4D7@hub.freebsd.org> References: <20001121013010.679C837B4D7@hub.freebsd.org> Date: Mon, 20 Nov 2000 20:27:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001121013010.679C837B4D7@hub.freebsd.org> Bill Paul writes: : Is there any support planned for externalizing the CIS info somehow, : i.e. by providing bus methods to call the CIS parsing routines? Another : way to do it would be to pass the info down to the child device using : ivars. I would imaging that there's similar support for this in Windows, : otherwise Intel's driver wouldn't work. Yes. There's two things we're planning on exporting. First is to export parsed data as various Ivars, like we do for the the 16-bit cards. This will likely be the interface that you want to use, since we know about network nic addresses. The whole CIS parsing for cardbus is a little bogus at the moment, so we're looking at making it much less bogus. The other interface will be an enumerative interface where you can get a callback for each CIS entry. These will be bus method based so that they will be the same between 16-bit and 32 bit code. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 4:45: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id C61AD37B4CF for ; Tue, 21 Nov 2000 04:44:58 -0800 (PST) Received: from e5y4s0 (213.36.98.47) by mail.libertysurf.net (5.1.053) id 3A0B791700119511; Tue, 21 Nov 2000 13:27:42 +0100 Message-ID: <008e01c053b6$8323f920$a66524d5@e5y4s0> Reply-To: "pop.libertysurf.fr" From: "pop.libertysurf.fr" To: Subject: VENTE ET LOCATION DE FICHIERS Date: Tue, 21 Nov 2000 13:27:50 +0100 Organization: ACPS MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0089_01C053BE.D834BB40" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0089_01C053BE.D834BB40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Comment trouver vos futurs clients et doper les ventes de votre = entreprise ? A.C.P.S VENTE ET LOCATION DE FICHIERS Disquettes-=C9tiquettes-CD-Listing shershire. 353.638 ADRESSES M=E9dical M=C9DECINS (GEN-SPE)CHIRURGIENS=20 CABINETS H=D4PITAUX CLINIQUES Vous souhaitez recevoir une information compl=E9mentaire ainsi que nos conditions tarifaires, alors n'h=E9sitez pas contactez = nous. A.C.P.S 27520 THUIT H=C9BERT FRANCE TEL 02 32 42 83 43 FAX 02 32 42 75 18 =C9MAIL=20 acps@wanadoo.fr Vous souhaitant bonne r=E9ception de la pr=E9sente, nous vous prions = d'agr=E9er, l'expression de nos sentiments les meilleurs. Service Commerciale MR JC BOULAN ps: =E9galement disponible 2.400.000 adresses toutes prof france sur CD = ( pc-mac) ------=_NextPart_000_0089_01C053BE.D834BB40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Comment trouver vos futurs clients et doper les ventes de votre = entreprise ?
A.C.P.S
VENTE ET=20 LOCATION DE FICHIERS
Disquettes-=C9tiquettes-CD-Listing = shershire.
353.638=20 ADRESSES M=E9dical
M=C9DECINS (GEN-SPE)CHIRURGIENS=20
CABINETS=20 H=D4PITAUX CLINIQUES
Vous souhaitez recevoir une information=20 compl=E9mentaire
ainsi que nos=20 conditions tarifaires, alors n'h=E9sitez pas contactez = nous.
A.C.P.S
27520 THUIT=20 H=C9BERT FRANCE
TEL 02 32 42 83=20 43 FAX 02 32 42 75 18
=C9MAIL=20
acps@wanadoo.fr
=
Vous souhaitant=20 bonne r=E9ception de la pr=E9sente, nous vous prions d’agr=E9er, = l’expression de nos=20 sentiments les meilleurs.
Service=20 Commerciale
MR JC = BOULAN
ps: =E9galement=20 disponible 2.400.000 adresses toutes prof france sur CD (=20 pc-mac)
------=_NextPart_000_0089_01C053BE.D834BB40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 6:11:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from myhakas.matti.ee (myhakas.matti.ee [194.126.114.87]) by hub.freebsd.org (Postfix) with ESMTP id 24EC937B4CF for ; Tue, 21 Nov 2000 06:11:22 -0800 (PST) Received: (from vallo@localhost) by myhakas.matti.ee (8.11.1/8.11.1) id eALEBF500588 for freebsd-current@freebsd.org; Tue, 21 Nov 2000 16:11:15 +0200 (EET) (envelope-from vallo) Date: Tue, 21 Nov 2000 16:11:15 +0200 From: Vallo Kallaste To: freebsd-current@freebsd.org Subject: lock order reversal messages? Message-ID: <20001121161115.A457@myhakas.matti.ee> Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Just got some while colleague used the bridge segment behind fxp1 interface. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Tue Nov 21 15:22:26 EET 2000 vallo@myhakas.matti.ee:/usr/src/sys/compile/Myhakas.SMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383fbff real memory = 268435456 (262144K bytes) avail memory = 257351680 (251320K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc03ba000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03ba09c. Pentium Pro MTRR support enabled VESA: v2.0, 32768k memory, flags:0x1, mode table:0xc00c6954 (c0006954) VESA: Matrox Graphics Inc. npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 16 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 7.2 Timecounter "PIIX" frequency 3579545 Hz pci0: at 7.3 ahc0: port 0xe400-0xe4ff mem 0xfebfc000-0xfebfcfff irq 16 at device 11.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 16 at device 11.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs pcm0: port 0xed80-0xedbf irq 18 at device 12.0 on pci0 fxp0: port 0xee80-0xeebf mem 0xfe800000-0xfe8fffff,0xfebfd000-0xfebfdfff irq 19 at device 13.0 on pci0 fxp0: Ethernet address 00:e0:81:10:50:32 fxp1: port 0xef00-0xef3f mem 0xfea00000-0xfeafffff,0xfebfe000-0xfebfefff irq 17 at device 15.0 on pci0 fxp1: Ethernet address 00:90:27:54:57:26 ed0: port 0xef80-0xef9f irq 18 at device 18.0 on pci0 ed0: address 00:e0:29:6d:14:19, type NE2000 (16 bit) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <9 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 BRIDGE 990810, have 4 interfaces -- index 1 type 6 phy 0 addrl 6 addr 00.e0.81.10.50.32 -- index 2 type 6 phy 0 addrl 6 addr 00.90.27.54.57.26 -- index 3 type 6 phy 0 addrl 6 addr 00.e0.29.6d.14.19 ad0: 14649MB [29765/16/63] at ata0-master tagged UDMA33 ad1: 35772MB [72680/16/63] at ata1-master tagged UDMA33 Waiting 5 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 1 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) cd0 at ahc1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! fxp0: promiscuous mode enabled >> now fxp0 promisc ON if_flags 0xffff8943 bdg_flags 0x5 fxp1: promiscuous mode enabled >> now fxp1 promisc ON if_flags 0xffff8943 bdg_flags 0x5 ed0: promiscuous mode enabled >> now ed0 promisc ON if_flags 0xffff8943 bdg_flags 0x5 lock order reversal 1st fxp0 last acquired @ ../../pci/if_fxp.c:1130 2nd 0xc0f462f4 fxp1 @ ../../pci/if_fxp.c:974 3rd 0xc0f466f4 fxp0 @ ../../pci/if_fxp.c:823 -- 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 Tue Nov 21 6:24: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtprch2.nortel.com (smtprch2.nortelnetworks.com [192.135.215.15]) by hub.freebsd.org (Postfix) with ESMTP id 1FB6C37B4C5 for ; Tue, 21 Nov 2000 06:23:58 -0800 (PST) Received: from zrchb213.us.nortel.com (actually zrchb213) by smtprch2.nortel.com; Tue, 21 Nov 2000 08:13:35 -0600 Received: from zrchb211.us.nortel.com ([47.100.128.40]) by zrchb213.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W57YWNJC; Tue, 21 Nov 2000 08:17:51 -0600 Received: from zrchb211.us.nortel.com ([47.100.128.40]) by zrchb211.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W7VSJBAQ; Tue, 21 Nov 2000 08:17:51 -0600 Received: from americasm01.nt.com (zngds004.us.nortel.com [47.124.160.58]) by zrchb211.us.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2652.39) id W7VSJBA3; Tue, 21 Nov 2000 08:17:50 -0600 Message-ID: <3A1A8411.F208B5D4@americasm01.nt.com> Date: Tue, 21 Nov 2000 08:17:53 -0600 From: "Michael Brune" Organization: Nortel Networks X-Mailer: Mozilla 4.74 [en] (X11; U; SunOS 5.7 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Problem Compiling Kernel References: <3A199800.E16A322F@americasm01.nt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Orig: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brune, Michael" wrote: > I CVSup'ed the sources today, built and installed world and everything > was fine. When I tried to compile the kernel, I recieve this error when > I do the 'make depend' > > ./aicasm -nostdinc -I- -I. -I../../ -I../../../include > -I../../contrib/dev/acpica/Subsystem/Include -I../../cam/scsi > -I../../dev/aic7xxx -o aic7xxx_seq.h -r aic7xxx_reg.h > ../../dev/aic7xxx/aic7xxx.seq > > ./aicasm: Stopped at file ../../dev/aic7xxx/aic7xxx.seq, line 81 - > syntax error > ./aicasm: Removing aic7xxx_seq.h due to error > ./aicasm: Removing aic7xxx_reg.h due to error > *** Error code 65 > > I looked at the file aic7xxx.seq on line 81, but I did not see any > errors. This is on a Dell Latitude 600 PIII. Please let me know if > anyone has a suggestion or needs more information. > > Thanks in advance! > > Corey > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message Please ignore this email. The problem wan mine... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 9: 4:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id EEF8837B4C5; Tue, 21 Nov 2000 09:04:26 -0800 (PST) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA38946; Tue, 21 Nov 2000 10:04:25 -0700 (MST) (envelope-from ken) Date: Tue, 21 Nov 2000 10:04:25 -0700 From: "Kenneth D. Merry" To: net@FreeBSD.org Subject: new zero copy sockets and NFS snapshot Message-ID: <20001121100425.A38926@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ -arch and -current BCC'ed for wider coverage, please direct followups to -net and/or me ] I have put a new copy of the zero copy sockets and NFS patches, against -current as of early November 20th, 2000, here: http://people.FreeBSD.ORG/~ken/zero_copy/ Questions, comments and feedback are welcome. Besides being generated against a newer version of -current, the following things have changed in the new patches posted above: - The fix to the "localhost panic" problem has been revamped. We now use a new external mbuf type, EXT_DISPOSABLE, to indicate that the external mbuf payload may be page-flipped or otherwise discarded. Instead of attempting to page flip any pages that meet the size and alignment criteria, we now only page flip external mbufs marked as disposable. (Thanks to Drew Gallatin for suggesting this approach.) - The decision process on when to use vm_uiomove() versus vm_pgmoveco() in uiomoveco() has been revamped somewhat. We no longer panic in any case. Anything that isn't handled by vm_pgmoveco() (according to the page flip criteria described above) is passed to vm_uiomove(). - uiomoveco() has been reorganized somewhat, with some of the functionality split out into a subfunction. There are no known problems with the code. If anyone wants to challenge that, I'll gladly accept bug reports, code comments, etc. :) For those of you who missed the previous messages about this code (that went out to -net, -arch and -current), here's a quick list of what is included in the code: - Zero copy send and receive code, written by Drew Gallatin . - Zero copy NFS code, written by Drew Gallatin. - Header splitting firmware for Alteon's Tigon II boards (written by me), based on version 12.4.11 of their firmware. This is used in combination with the zero copy receive code to guarantee that the payload of TCP or UDP packet is placed into a page-aligned buffer. - Alteon firmware debugging ioctls and supporting routines for the Tigon driver (also written by me). This will help anyone who is doing firmware development under FreeBSD for the Tigon boards. The Alteon header splitting and debugging code was written for Pluto Technologies (www.plutotech.com), which kindly agreed to let me release the code. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 10: 0:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from c736718-a.vncvr1.wa.home.com (c736718-a.vncvr1.wa.home.com [24.176.60.197]) by hub.freebsd.org (Postfix) with ESMTP id 34FEA37B4C5 for ; Tue, 21 Nov 2000 10:00:20 -0800 (PST) Received: (from chuck@localhost) by c736718-a.vncvr1.wa.home.com (8.11.0/8.11.0) id eALI0V886206 for freebsd-current@freebsd.org; Tue, 21 Nov 2000 10:00:31 -0800 (PST) (envelope-from chuck) Date: Tue, 21 Nov 2000 10:00:31 -0800 (PST) From: Scott Worley Message-Id: <200011211800.eALI0V886206@c736718-a.vncvr1.wa.home.com> To: freebsd-current@freebsd.org Subject: Re: -current scheduler strangeness Reply-To: chkno@home.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (just a little extra info) Scheduler issues have been present since at least 20001112-current. I installed the snapshot as my first venture into the current tree. Mp3 skippage and loopage was very bad. The box in question is an amd k6-2 300 (lower than average in this list, i gather). Mp3 decoding is only a 15-18% processor load, yet -current would skip & jump even while doing nothing else. a note on "pcm0: hwptr went backwards XXX -> XXX" I did not get these in 4.0-release. (or at least didn't notice them in six months..) I got a lot of these in -current. I've gotten two of these so far since reinstalling 4.1.1-release a few days ago. (i think they coincided with a load of mp3 playing, two compiles, & a mv between hds on my dma-crippled ata controller (this is heavy for me & my 300)) (sorry if this thread is outdated, i've been following -digest til now) -- chuck chkno@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 10:43:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id F302937B4CF; Tue, 21 Nov 2000 10:43:39 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eALIhE465132; Tue, 21 Nov 2000 11:43:26 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011211843.eALIhE465132@aslan.scsiguy.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-Reply-To: Your message of "Mon, 20 Nov 2000 20:27:02 MST." <200011210327.UAA30567@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 11:43:14 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The other interface will be an enumerative interface where you can get >a callback for each CIS entry. These will be bus method based so that >they will be the same between 16-bit and 32 bit code. I don't think the enumerative interface should be callback based. I'd rather have something that facilitates walking the CIS that can be used at anytime. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 11:32:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id D541C37B4D7; Tue, 21 Nov 2000 11:32:50 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eALJWnQ31620; Tue, 21 Nov 2000 12:32:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA36176; Tue, 21 Nov 2000 12:32:49 -0700 (MST) Message-Id: <200011211932.MAA36176@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Getting at cardbus CIS data from inside drivers Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 11:43:14 MST." <200011211843.eALIhE465132@aslan.scsiguy.com> References: <200011211843.eALIhE465132@aslan.scsiguy.com> Date: Tue, 21 Nov 2000 12:32:49 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011211843.eALIhE465132@aslan.scsiguy.com> "Justin T. Gibbs" writes: : >The other interface will be an enumerative interface where you can get : >a callback for each CIS entry. These will be bus method based so that : >they will be the same between 16-bit and 32 bit code. : : I don't think the enumerative interface should be callback based. I'd : rather have something that facilitates walking the CIS that can be used : at anytime. That's what I mean. You call this, and it will remap the CIS (if it has been unmapped), walk it for you and pass you a pointer to each CIS entry one at a time to the function you specify. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 12: 8:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from granger.mail.mindspring.net (granger.mail.mindspring.net [207.69.200.148]) by hub.freebsd.org (Postfix) with ESMTP id E376737B4D7 for ; Tue, 21 Nov 2000 12:08:13 -0800 (PST) Received: from ix.netcom.com (sil-wa15-43.ix.netcom.com [207.93.148.43]) by granger.mail.mindspring.net (8.9.3/8.8.5) with ESMTP id PAA14814 for ; Tue, 21 Nov 2000 15:08:08 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.11.1/8.9.3) id eALK83E00524; Tue, 21 Nov 2000 12:08:03 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Tue, 21 Nov 2000 12:08:03 -0800 (PST) Message-Id: <200011212008.eALK83E00524@ix.netcom.com> From: "Thomas D. Dean" To: current@FreeBSD.ORG In-reply-to: <200011200212.eAK2Cj500371@ix.netcom.com> (tomdean@ix.netcom.com) Subject: Re: Clock Strangeness in UP Kernel References: <200011200212.eAK2Cj500371@ix.netcom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a high clock drift rate. The problem is in selecting the timecounter, at least on my machine. Both the TSC and the i8254 timecounters are checked and, since, I believe, TSC is last, TSC is the timecounter the kernel uses. TSC is a horrible timer, at least on my machine. i8254 is not perfect, but several orders of magnitude better, at least with FreeBSD. # sysctl -a ... kern.timecounter.hardware: TSC ... # sysctl -w kern.timecounter.hardware=i8264 fixes the clock drift. Now, it is less than 2 seconds per 4 hours. And, that is well within the range ntp can satisfactorily correct for. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 12:29:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 53D6337B479; Tue, 21 Nov 2000 12:29:11 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eALKSk465978; Tue, 21 Nov 2000 13:28:50 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011212028.eALKSk465978@aslan.scsiguy.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-Reply-To: Your message of "Tue, 21 Nov 2000 12:32:49 MST." <200011211932.MAA36176@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 13:28:46 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >That's what I mean. You call this, and it will remap the CIS (if it >has been unmapped), walk it for you and pass you a pointer to each CIS >entry one at a time to the function you specify. > >Warner I'd rather have a seek/read interface than have a callback. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 12:43:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 7F27137B4C5; Tue, 21 Nov 2000 12:43:26 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eALKhNQ32214; Tue, 21 Nov 2000 13:43:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA37246; Tue, 21 Nov 2000 13:43:23 -0700 (MST) Message-Id: <200011212043.NAA37246@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Getting at cardbus CIS data from inside drivers Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 13:28:46 MST." <200011212028.eALKSk465978@aslan.scsiguy.com> References: <200011212028.eALKSk465978@aslan.scsiguy.com> Date: Tue, 21 Nov 2000 13:43:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011212028.eALKSk465978@aslan.scsiguy.com> "Justin T. Gibbs" writes: : >That's what I mean. You call this, and it will remap the CIS (if it : >has been unmapped), walk it for you and pass you a pointer to each CIS : >entry one at a time to the function you specify. : > : >Warner : : I'd rather have a seek/read interface than have a callback. The problem with a read/seek interface is that you are consuming a resource (a memory window) while you are using it. You'd need an open/close on top of that as well to properly map things in to start and then free them at the end. Plus you might want a ftell sort of interface as well. I'll likely punt on the seek/ftell part. But it would make the client code a little easier to cope with: uchar8_t cis[CIS_MAX_LENGTH]; size_t len; cis_cookie_t cookie; card_map_cis(dev, &cookie); while (card_read_cis(dev, cookie, cis, &len)) { frob the cis entry } card_unmap_cis(dev, cookie); I'll see how hard it would be to come up with this, if this sort of interface is reasonable. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 13: 0: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 821) id 6735437B4CF; Tue, 21 Nov 2000 12:59:56 -0800 (PST) Date: Tue, 21 Nov 2000 12:59:56 -0800 From: "John W. De Boskey" To: Current List Subject: No console on AlphaServer 2000 4/233 4.2-RC2 Message-ID: <20001121125955.A76196@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Console, console, where's the console? We are attempting to use FreeBSD 4.2-RC2 on an AlphaServer 2000 4/233 and are running into trouble with the console device. When we boot from the CD, it comes up to the boot prompt on the console where we tell it to boot from the cd device. The cd then boots up to the following: /stand/sysinstall running as init on serial console These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color) 4 ...................... FreeBSD system console (monochrome) 5 ...................... xterm terminal emulator Your choice: (1-5) At this point, no keyboard input is accepted. We then successfully installed onto an AlphaServer 1000 and moved the disks to the 2000. At this point the console is still useless, but we can telnet into the machine and use it... I've included the dmesg output below. Note, on the console after boot, but right before the useless login prompt: Cannot open /dev/ttyv0: not such device or address and from ls: %ls -al /dev/ttyv0 crw------- 1 root wheel 12, 0 Nov 21 10:02 /dev/ttyv0 So, it seems getty can't open the virtual terminal devices. A ps -aux right after boot: PID PPID UID %CPU %MEM STAT TIME COMMAND 0 0 0 0.0 0.0 DLs 0:00.00 (swapper) 1 0 0 0.0 0.2 ILs 0:00.03 (init) 2 0 0 0.0 0.0 DL 0:00.00 (pagedaemon) 3 0 0 0.0 0.0 DL 0:00.00 (vmdaemon) 4 0 0 0.0 0.0 DL 0:00.00 (bufdaemon) 5 0 0 0.0 0.0 DL 0:00.07 (syncer) 83 1 0 0.0 0.4 Ss 0:00.57 syslogd -s 86 1 1 0.0 0.3 Is 0:00.01 /usr/sbin/portmap 102 1 0 0.0 0.5 Is 0:00.13 inetd -wW 104 1 0 0.0 0.5 Is 0:00.04 cron 107 1 0 0.0 0.8 Is 0:00.05 sendmail: accepting connections (sen 111 1 0 0.0 0.8 Is 0:05.88 /usr/sbin/sshd 141 102 0 0.0 0.9 Ss 0:00.37 telnetd 142 141 896 0.0 0.3 Is 0:00.23 -ksh (ksh) 159 142 0 0.0 0.3 S 0:00.26 -su (ksh) 206 159 0 0.0 0.2 R+ 0:00.00 /bin/ps -axo pid aux 140 1 0 0.0 0.4 Is+ 0:00.05 /usr/libexec/getty Pc console and dmesg: (Yes, the 1st 2 lines are from dmesg, and I cannot find where they are coming from yet). Unrecognized boot flag '0'. Unrecognized boot flag ','. Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.2-RC1 #0: Thu Nov 16 06:10:10 EST 2000 root@apdrb.vms.sas.com:/usr/src/sys/compile/ALPHADOG DEC AlphaServer 2100 AlphaServer 2000 4/233, 233MHz 8192 byte page size, 1 processor. CPU: EV45 (21064A) major=6 minor=2 OSF PAL rev: 0x4000c0002012d real memory = 266264576 (260024K bytes) avail memory = 254279680 (248320K bytes) Preloaded elf kernel "kernel" at 0xfffffc00005f8000. md0: Malloc disk pci0: on pcib0 sym0: <810> port 0x10000-0x100ff mem 0x81080000-0x810800ff irq 33 at device 1.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking sym0: interrupting at T2 irq 33 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: (vendor=0x1011, dev=0x0004) at 6.0 irq 32 de0: port 0x10100-0x1017f mem 0x81080100-0x8108017f irq 36 at device 7.0 on pci0 de0: interrupting at T2 irq 36 de0: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0 de0: address 00:00:f8:07:3a:b7 pci0: (vendor=0x10d5, dev=0x0002) at 8.0 irq 37 pci0: (vendor=0x4f24, dev=0x1721) at 12.0 irq 33 pci0: (vendor=0x0100, dev=0x0100) at 12.4 irq 65 pci0: (vendor=0x4f24, dev=0x1721) at 13.0 irq 33 pci0: (vendor=0x0100, dev=0x0100) at 13.4 irq 65 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: interrupting at T2 irq 6 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd0: interrupting at T2 irq 1 psm0: irq 12 on atkbdc0 psm0: interrupting at T2 irq 12 psm0: model Generic PS/2 mouse, device ID 0 mcclock0: at port 0x70-0x71 on isa0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at T2 irq 4 sio1: reserved for low-level i/o ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Polled port ppc0: interrupting at T2 irq 7 Timecounter "alpha" frequency 233332635 Hz Waiting 2 seconds for SCSI devices to settle da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da1: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled da2: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) Mounting root from ufs:/dev/da0a WARNING: / was not properly dismounted de0: enabling 10baseT port cd0 at sym0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 4.237MB/s transfers (4.237MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 13: 8:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 443FF37B4CF; Tue, 21 Nov 2000 13:08:16 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eALL7r466624; Tue, 21 Nov 2000 14:07:57 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011212107.eALL7r466624@aslan.scsiguy.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-Reply-To: Your message of "Tue, 21 Nov 2000 13:43:23 MST." <200011212043.NAA37246@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 14:07:53 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >The problem with a read/seek interface is that you are consuming a >resource (a memory window) while you are using it. Yes, but this is the client's resource to use anyway. >You'd need an >open/close on top of that as well to properly map things in to start >and then free them at the end. Plus you might want a ftell sort of >interface as well. I'll likely punt on the seek/ftell part. I think it was Jonathan that mentioned that at times when you read one entry you want to skip to another entry that it may reference. I don't have the spec to know, but that is why I thought the flexibility of having a seeking interface might be necessary. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 13:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from bsdone.bsdwins.com (www.bsdwins.com [192.58.184.33]) by hub.freebsd.org (Postfix) with ESMTP id 97A0B37B4C5 for ; Tue, 21 Nov 2000 13:17:46 -0800 (PST) Received: (from jwd@localhost) by bsdone.bsdwins.com (8.11.0/8.11.0) id eALLHkX52920 for freebsd-current@FreeBSD.ORG; Tue, 21 Nov 2000 16:17:46 -0500 (EST) (envelope-from jwd) Date: Tue, 21 Nov 2000 16:17:46 -0500 From: "John W. De Boskey" To: Current List Subject: Re: No console on AlphaServer 2000 4/233 4.2-RC1 Message-ID: <20001121161746.A52853@bsdwins.com> References: <20001121125955.A76196@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001121125955.A76196@FreeBSD.org>; from jwd@FreeBSD.ORG on Tue, Nov 21, 2000 at 12:59:56PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grr... make that 4.2-RC1 FreeBSD 4.2-RC1 #0: Thu Nov 16 06:10:10 EST 2000 -john ----- John W. De Boskey's Original Message ----- > > Hi, > > Console, console, where's the console? > > We are attempting to use FreeBSD 4.2-RC2 on an > AlphaServer 2000 4/233 and are running into trouble > with the console device. > > When we boot from the CD, it comes up to the boot > prompt on the console where we tell it to boot from > the cd device. The cd then boots up to the following: > > /stand/sysinstall running as init on serial console > > These are the predefined terminal types available to > sysinstall when running stand-alone. Please choose the > closest match for your particular terminal. > > 1 ...................... Standard ANSI terminal. > 2 ...................... VT100 or compatible terminal. > 3 ...................... FreeBSD system console (color) > 4 ...................... FreeBSD system console (monochrome) > > 5 ...................... xterm terminal emulator > > Your choice: (1-5) > > > At this point, no keyboard input is accepted. > > > > We then successfully installed onto an AlphaServer 1000 > and moved the disks to the 2000. At this point the console > is still useless, but we can telnet into the machine and > use it... > > I've included the dmesg output below. Note, on the console > after boot, but right before the useless login prompt: > > Cannot open /dev/ttyv0: not such device or address > > and from ls: > > %ls -al /dev/ttyv0 > crw------- 1 root wheel 12, 0 Nov 21 10:02 /dev/ttyv0 > > > So, it seems getty can't open the virtual terminal > devices. A ps -aux right after boot: > > PID PPID UID %CPU %MEM STAT TIME COMMAND > 0 0 0 0.0 0.0 DLs 0:00.00 (swapper) > 1 0 0 0.0 0.2 ILs 0:00.03 (init) > 2 0 0 0.0 0.0 DL 0:00.00 (pagedaemon) > 3 0 0 0.0 0.0 DL 0:00.00 (vmdaemon) > 4 0 0 0.0 0.0 DL 0:00.00 (bufdaemon) > 5 0 0 0.0 0.0 DL 0:00.07 (syncer) > 83 1 0 0.0 0.4 Ss 0:00.57 syslogd -s > 86 1 1 0.0 0.3 Is 0:00.01 /usr/sbin/portmap > 102 1 0 0.0 0.5 Is 0:00.13 inetd -wW > 104 1 0 0.0 0.5 Is 0:00.04 cron > 107 1 0 0.0 0.8 Is 0:00.05 sendmail: accepting connections > (sen > 111 1 0 0.0 0.8 Is 0:05.88 /usr/sbin/sshd > 141 102 0 0.0 0.9 Ss 0:00.37 telnetd > 142 141 896 0.0 0.3 Is 0:00.23 -ksh (ksh) > 159 142 0 0.0 0.3 S 0:00.26 -su (ksh) > 206 159 0 0.0 0.2 R+ 0:00.00 /bin/ps -axo pid aux > 140 1 0 0.0 0.4 Is+ 0:00.05 /usr/libexec/getty Pc console > > > and dmesg: (Yes, the 1st 2 lines are from dmesg, and I cannot > find where they are coming from yet). > > Unrecognized boot flag '0'. > Unrecognized boot flag ','. > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-RC1 #0: Thu Nov 16 06:10:10 EST 2000 > root@apdrb.vms.sas.com:/usr/src/sys/compile/ALPHADOG > DEC AlphaServer 2100 > AlphaServer 2000 4/233, 233MHz > 8192 byte page size, 1 processor. > CPU: EV45 (21064A) major=6 minor=2 > OSF PAL rev: 0x4000c0002012d > real memory = 266264576 (260024K bytes) > avail memory = 254279680 (248320K bytes) > Preloaded elf kernel "kernel" at 0xfffffc00005f8000. > md0: Malloc disk > pci0: on pcib0 > sym0: <810> port 0x10000-0x100ff mem 0x81080000-0x810800ff irq 33 at device > 1.0 on pci0 > sym0: No NVRAM, ID 7, Fast-10, SE, parity checking > sym0: interrupting at T2 irq 33 > isab0: at device 2.0 on pci0 > isa0: on isab0 > pci0: (vendor=0x1011, dev=0x0004) at 6.0 irq 32 > de0: port 0x10100-0x1017f mem > 0x81080100-0x8108017f irq 36 at device 7.0 on pci0 > de0: interrupting at T2 irq 36 > de0: DEC DE500-BA 21143 [10-100Mb/s] pass 3.0 > de0: address 00:00:f8:07:3a:b7 > pci0: (vendor=0x10d5, dev=0x0002) at 8.0 irq 37 > pci0: (vendor=0x4f24, dev=0x1721) at 12.0 irq 33 > pci0: (vendor=0x0100, dev=0x0100) at 12.4 irq 65 > pci0: (vendor=0x4f24, dev=0x1721) at 13.0 irq 33 > pci0: (vendor=0x0100, dev=0x0100) at 13.4 irq 65 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: interrupting at T2 irq 6 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > atkbd0: interrupting at T2 irq 1 > psm0: irq 12 on atkbdc0 > psm0: interrupting at T2 irq 12 > psm0: model Generic PS/2 mouse, device ID 0 > mcclock0: at port 0x70-0x71 on isa0 > sio0: configured irq 4 not in bitmap of probed irqs 0 > sio0 at port 0x3f8-0x3ff irq 4 on isa0 > sio0: type 16550A > sio0: interrupting at T2 irq 4 > sio1: reserved for low-level i/o > ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > ppi0: on ppbus0 > lpt0: on ppbus0 > lpt0: Polled port > ppc0: interrupting at T2 irq 7 > Timecounter "alpha" frequency 233332635 Hz > Waiting 2 seconds for SCSI devices to settle > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da0: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da1: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) > da2 at sym0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 8), Tagged Queueing Enabled > da2: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) > Mounting root from ufs:/dev/da0a > WARNING: / was not properly dismounted > de0: enabling 10baseT port > cd0 at sym0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 4.237MB/s transfers (4.237MHz, offset 8) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > > Thanks! > John > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 13:25:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 3DF1037B4C5; Tue, 21 Nov 2000 13:25:39 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eALLPYQ32507; Tue, 21 Nov 2000 14:25:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA37742; Tue, 21 Nov 2000 14:25:34 -0700 (MST) Message-Id: <200011212125.OAA37742@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Getting at cardbus CIS data from inside drivers Cc: wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 14:07:53 MST." <200011212107.eALL7r466624@aslan.scsiguy.com> References: <200011212107.eALL7r466624@aslan.scsiguy.com> Date: Tue, 21 Nov 2000 14:25:33 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011212107.eALL7r466624@aslan.scsiguy.com> "Justin T. Gibbs" writes: : >The problem with a read/seek interface is that you are consuming a : >resource (a memory window) while you are using it. : : Yes, but this is the client's resource to use anyway. IIRC, it is shared at the bridge, so the client driver needs to conserve this resource. The comment was more of a thnking out loud for the need to have an open and close (or in this case map and unmap) around its use. : >You'd need an : >open/close on top of that as well to properly map things in to start : >and then free them at the end. Plus you might want a ftell sort of : >interface as well. I'll likely punt on the seek/ftell part. : : I think it was Jonathan that mentioned that at times when you read : one entry you want to skip to another entry that it may reference. : I don't have the spec to know, but that is why I thought the flexibility : of having a seeking interface might be necessary. That's one reason that I'd want the callback interface. There are pointers in CIS to other CIS entries that the driver shouldn't care about. However, these are relatively rare, but do appear in multi-function cards (at least for 16-bit cards) and so would likely need to be taken care of. I could have something that would skip ahead, but it wouldn't be a fully general seek/ftell function. That moves more of the processing into the driver than I'd rather see, but I don't see a clean way around it. IIRC, and I haven't looked it up, the CIS entries that would be problematical have two next pointers. One is for the next function, while the other is for the first entry specific to this function. The driver code could look at the CIS entry to tell what to do, and if it was the wrong function, call cis_skip_this_function(dev, cookie, cis); which would skip this function and position the read pointer hidden in the cookie to point to the first entry in the next function's cis (or more accurately, the first entry in the series of entries that are specific to that function). And if you provide this, then people will want to just look at the cis entries for their function only next, which is another interface. Or they will want to search for a certain kind of cis entry. I'm disinclined to make this interface too rich. Oh, and I'd have to make sure that the CIS pointers were sane, which can be hard. One of the problems with the NetBSD code, at least in the past, is that it was too believing that the CIS entries would be compliant with the specs. So certain 16-bit cards would crash the system. It is complications like this that lead me to want to not allow CIS reading at all, but rather provide the commonly parsed information easily to the driver. I don't want drivers groveling through all this stuff to find an ethernet address when the bus is able to parse the CIS and return this on request. Having said that, and based on my experience with some really whacko hardware in the 16-bit world, I think that I can't justify this stand because it makes writing a device driver for whacked out hardware impossible w/o gross hacks (cf older revs of if_xe.c). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 13:36:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4B08637B4CF; Tue, 21 Nov 2000 13:36:28 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #4) id 13yL5W-0004tg-00; Tue, 21 Nov 2000 21:36:26 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eALLZLU68895; Tue, 21 Nov 2000 22:35:21 +0100 (CET) (envelope-from wkb) Date: Tue, 21 Nov 2000 22:35:21 +0100 From: Wilko Bulte To: "John W. De Boskey" Cc: Current List Subject: Re: No console on AlphaServer 2000 4/233 4.2-RC2 Message-ID: <20001121223521.B64714@freebie.demon.nl> References: <20001121125955.A76196@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20001121125955.A76196@FreeBSD.org>; from jwd@freebsd.org on Tue, Nov 21, 2000 at 12:59:56PM -0800 X-OS: FreeBSD 4.2-BETA X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Nov 21, 2000 at 12:59:56PM -0800, John W. De Boskey wrote: > Console, console, where's the console? > > We are attempting to use FreeBSD 4.2-RC2 on an > AlphaServer 2000 4/233 and are running into trouble > with the console device. > > When we boot from the CD, it comes up to the boot > prompt on the console where we tell it to boot from > the cd device. The cd then boots up to the following: > > /stand/sysinstall running as init on serial console > > These are the predefined terminal types available to > sysinstall when running stand-alone. Please choose the > closest match for your particular terminal. > > 1 ...................... Standard ANSI terminal. > 2 ...................... VT100 or compatible terminal. > 3 ...................... FreeBSD system console (color) > 4 ...................... FreeBSD system console (monochrome) > > 5 ...................... xterm terminal emulator > > Your choice: (1-5) > > > At this point, no keyboard input is accepted. What video adapter is inside? I'm guessing, but this is not by any chance a TGA-based card is it? FreeBSD/axp does not currently support TGA based adapters. The SRM will use it, but the kernel not once started. I think this is what: /stand/sysinstall running as init on serial console is trying to tell you. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 18:32:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 4FEC437B4D7 for ; Tue, 21 Nov 2000 18:32:30 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAM2WJJ22778 for ; Tue, 21 Nov 2000 19:32:20 -0700 (MST) Date: Tue, 21 Nov 2000 19:32:18 -0700 (MST) From: X-Sender: janb@gecko To: freebsd-current@FreeBSD.ORG Subject: state of usb? 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 What is the current state of the usbd? I keep getting messages that complain about a host controller error and a shutdown of the usb interface. And I don't even have any devices on my usb ports... JAN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 20:14:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id A080437B4CF; Tue, 21 Nov 2000 20:14:38 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAM4LtF00755; Tue, 21 Nov 2000 20:21:55 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011220421.eAM4LtF00755@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Justin T. Gibbs" Cc: Warner Losh , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-reply-to: Your message of "Tue, 21 Nov 2000 13:28:46 MST." <200011212028.eALKSk465978@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 20:21:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >That's what I mean. You call this, and it will remap the CIS (if it > >has been unmapped), walk it for you and pass you a pointer to each CIS > >entry one at a time to the function you specify. > > > >Warner > > I'd rather have a seek/read interface than have a callback. Let's be realistic; the right way to do this is going to be to use the ivar interface; cardbus_get_cistuple(dev, index) just like all the other PCI bus accessor functions. PCI will just need to pass the request through to its parent, assuming its parent is a cardbus bridge, or veto it otherwise. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 20:20:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id 1A54037B4CF; Tue, 21 Nov 2000 20:20:17 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAM4RYF00772; Tue, 21 Nov 2000 20:27:34 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011220427.eAM4RYF00772@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: "Justin T. Gibbs" , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-reply-to: Your message of "Tue, 21 Nov 2000 14:25:33 MST." <200011212125.OAA37742@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 20:27:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IIRC, and I haven't looked it up, the CIS entries that would be > problematical have two next pointers. One is for the next function, > while the other is for the first entry specific to this function. The > driver code could look at the CIS entry to tell what to do, and if it > was the wrong function, call > cis_skip_this_function(dev, cookie, cis); > which would skip this function and position the read pointer hidden in > the cookie to point to the first entry in the next function's cis (or > more accurately, the first entry in the series of entries that are > specific to that function). No; the CIS parser should know which function it's being called on behalf of, and simply elide the tuples that don't relate to that function. > It is complications like this that lead me to want to not allow CIS > reading at all, but rather provide the commonly parsed information > easily to the driver. I don't want drivers groveling through all this > stuff to find an ethernet address when the bus is able to parse the > CIS and return this on request. Having said that, and based on my > experience with some really whacko hardware in the 16-bit world, I > think that I can't justify this stand because it makes writing a > device driver for whacked out hardware impossible w/o gross hacks (cf > older revs of if_xe.c). Export the commonly-known stuff through the "right" interface (eg. cardbus_get_cistuple(dev, CARDBUS_CIS_STATION_ADDRESS)) and then provide a backdoor (cardbus_get_cistuple(dev, CARSBUS_CIS_RAW + index)) for the evil side, perhaps. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 20:34:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id DC1DD37B4CF; Tue, 21 Nov 2000 20:34:21 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAM4YKQ33720; Tue, 21 Nov 2000 21:34:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA39864; Tue, 21 Nov 2000 21:34:20 -0700 (MST) Message-Id: <200011220434.VAA39864@harmony.village.org> To: Mike Smith Subject: Re: Getting at cardbus CIS data from inside drivers Cc: "Justin T. Gibbs" , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 20:21:55 PST." <200011220421.eAM4LtF00755@mass.osd.bsdi.com> References: <200011220421.eAM4LtF00755@mass.osd.bsdi.com> Date: Tue, 21 Nov 2000 21:34:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011220421.eAM4LtF00755@mass.osd.bsdi.com> Mike Smith writes: : > >That's what I mean. You call this, and it will remap the CIS (if it : > >has been unmapped), walk it for you and pass you a pointer to each CIS : > >entry one at a time to the function you specify. : > > : > >Warner : > : > I'd rather have a seek/read interface than have a callback. : : Let's be realistic; the right way to do this is going to be to use the : ivar interface; cardbus_get_cistuple(dev, index) just like all the other : PCI bus accessor functions. PCI will just need to pass the request : through to its parent, assuming its parent is a cardbus bridge, or veto : it otherwise. Why does this have to go even to the bridge? The cardbus bus code already deals with the CIS and it should be the one to arrange things to happen. We can tweak the current cardbus CIS reading stuff to do this and maybe combine it somewhat with the pccard CIS reading stuff. Also, the index doesn't make so much sense because each CIS entry is a variable length, so we'd have to walk the chain. The length is variable, which doesn't work so well with the accessor function which tend to like things to be <= sizeof(long). Also, this isn't a PCI thing, so no PCI code should be called. :-) For mapping some parts of the CIS, I think that you need to do that at the cardbus bridge, which means that you can only do that for the cardbus children that are attached. Going up through multiple bridges isn't going to work. This is especially true for the 16-bit CIS entries. Eg, if you have something like the following: pci --- pccbb0 --- cardbus0 --- pcib --- pci -- pccbb0 -- cardbus1 -- dc then when the dc driver wants to map the CIS, the cardbus bus will ask the pccbb to map it, which will go up the usual food chain for mapping, but after it leaves the pccbb it is just a normal map request. The second cardbus bridge (pccbb0) doesn't get into the act of mapping the CIS. Once mapped, cardbus1 will be returning the CIS to dc and also handling the jump discontinuties that can happen in the CIS. This is why I want to have cardbus be its own bus that happens to implement all the pci bus things properly. It is, in C++ terms, a subclass: it is a pci bus plus a few other things. I don't think we should try to shoehorn it all into the PCI bus code. Something tells me that it will result in chaos. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 20:41: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id 75FDC37B479 for ; Tue, 21 Nov 2000 20:40:59 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAM4mIF00882; Tue, 21 Nov 2000 20:48:18 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011220448.eAM4mIF00882@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-reply-to: Your message of "Tue, 21 Nov 2000 21:34:20 MST." <200011220434.VAA39864@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 20:48:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Let's be realistic; the right way to do this is going to be to use the > : ivar interface; cardbus_get_cistuple(dev, index) just like all the other > : PCI bus accessor functions. PCI will just need to pass the request > : through to its parent, assuming its parent is a cardbus bridge, or veto > : it otherwise. > > Why does this have to go even to the bridge? Because it's the bridge driver that has to parse the CIS; it needs it to eg. set power and so forth. And because the bus code should be generic. > The cardbus bus code > already deals with the CIS and it should be the one to arrange things > to happen. We can tweak the current cardbus CIS reading stuff to do > this and maybe combine it somewhat with the pccard CIS reading stuff. > Also, the index doesn't make so much sense because each CIS entry is a > variable length, so we'd have to walk the chain. Index is the tuple index, not the byte offset in the CIS; sorry I didn't make that clear. > Also, this isn't a PCI thing, so no PCI code should be called. :-) Interrupts aren't a PCI thing either, but we pass attempts by PCI drivers to do stuff with them up through the stack. This really isn't any different. > For mapping some parts of the CIS, I think that you need to do that at > the cardbus bridge, which means that you can only do that for the > cardbus children that are attached. Going up through multiple bridges > isn't going to work. This is especially true for the 16-bit CIS > entries. Yeah; I don't think I was proposing anything like this. > Eg, if you have something like the following: > > pci --- pccbb0 --- cardbus0 --- pcib --- pci -- pccbb0 -- cardbus1 -- dc > > then when the dc driver wants to map the CIS, the cardbus bus will ask > the pccbb to map it, which will go up the usual food chain for > mapping, but after it leaves the pccbb it is just a normal map > request. The second cardbus bridge (pccbb0) doesn't get into the act > of mapping the CIS. Once mapped, cardbus1 will be returning the CIS > to dc and also handling the jump discontinuties that can happen in the > CIS. > > This is why I want to have cardbus be its own bus that happens to > implement all the pci bus things properly. It is, in C++ terms, a > subclass: it is a pci bus plus a few other things. I don't think we > should try to shoehorn it all into the PCI bus code. Something tells > me that it will result in chaos. I think that you're overrating the things that need to be "shoehorned" into PCI to make it a comfortable superset of stock PCI + hot-plug PCI + CardBus. So far all we have is passing through a CIS tuple accessor function. 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 20:42: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id 8C2D937B479; Tue, 21 Nov 2000 20:42:04 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAM4g3Q33748; Tue, 21 Nov 2000 21:42:03 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA39910; Tue, 21 Nov 2000 21:42:02 -0700 (MST) Message-Id: <200011220442.VAA39910@harmony.village.org> To: Mike Smith Subject: Re: Getting at cardbus CIS data from inside drivers Cc: "Justin T. Gibbs" , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 20:27:34 PST." <200011220427.eAM4RYF00772@mass.osd.bsdi.com> References: <200011220427.eAM4RYF00772@mass.osd.bsdi.com> Date: Tue, 21 Nov 2000 21:42:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011220427.eAM4RYF00772@mass.osd.bsdi.com> Mike Smith writes: : No; the CIS parser should know which function it's being called on behalf : of, and simply elide the tuples that don't relate to that function. This isn't always the right thing to do. At least in the 16-bit world, there are drivers that want to look at the CIS entries for the other function of the card for various reasons (some of them need to know what kind of modem is present, iirc, to initalize some things in a non-standard way, the example was the NetBSD driver mhz, iirc). I don't wish to preclude that. : Export the commonly-known stuff through the "right" interface : (eg. cardbus_get_cistuple(dev, CARDBUS_CIS_STATION_ADDRESS)) and then : provide a backdoor (cardbus_get_cistuple(dev, CARSBUS_CIS_RAW + index)) : for the evil side, perhaps. Right now pccard exports this as: uchar8_t ether_addr[ETEHR_ADDR_LEN]; pccard_get_ether(dev, ether_addr); where pccard_get_ether is generated by really ugly, but usefully stolen from pci, macros in dev/pccard/pccardvar.h. The OLDCARD code set this from the userland after parsing the CIS. NEWCARD currently doesn't implement this correctly, but will need to do so shortly. I'd like to do exactly the same thing for cardbus: uchar8_t ether_addr[ETEHR_ADDR_LEN]; cardbus_get_ether(dev, ether_addr); to make things easy. I don't think that we can easily do the index thing for CIS entries, for reasons that I've talked about before. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 21:36: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AA3B737B479; Tue, 21 Nov 2000 21:36:02 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAM5a1Q33859; Tue, 21 Nov 2000 22:36:02 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA40087; Tue, 21 Nov 2000 22:36:01 -0700 (MST) Message-Id: <200011220536.WAA40087@harmony.village.org> To: Mike Smith Subject: Re: Getting at cardbus CIS data from inside drivers Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 20:48:18 PST." <200011220448.eAM4mIF00882@mass.osd.bsdi.com> References: <200011220448.eAM4mIF00882@mass.osd.bsdi.com> Date: Tue, 21 Nov 2000 22:36:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011220448.eAM4mIF00882@mass.osd.bsdi.com> Mike Smith writes: : > : Let's be realistic; the right way to do this is going to be to use the : > : ivar interface; cardbus_get_cistuple(dev, index) just like all the other : > : PCI bus accessor functions. PCI will just need to pass the request : > : through to its parent, assuming its parent is a cardbus bridge, or veto : > : it otherwise. : > : > Why does this have to go even to the bridge? : : Because it's the bridge driver that has to parse the CIS; it needs it to : eg. set power and so forth. And because the bus code should be generic. I don't think that the bridge driver should parse the CIS. The bus driver should do the parsing. The bridge driver may be asked by the bus driver to do mapping and such, but it shouldn't do the parsing of the CIS. This is a card services vs socket services issue. I want to be able to implement card services and socket services (maybe in a form different than the pccard spec states). Other card services, from the spec, include resource management (which the bus does), cis traversal, bulk memory services, cis verification, and event managment (note that socket services generate these events and card services respond to them) and some power management issues. All the flash MDTs are handled here as well. Many of these are unique to cardbus and pccard. Many of these are shared with pci. The mapping into FreeBSD's newbus has been a little fuzzy. The experience from the 16-bit days was that one can have different PCIC bridges that the pccard bus sits on top of. There are at least 4 different APIs to talk to the pcic bridge that I know of (pcic (i82365), pcic98 (a custom NEC part found on some pc98 laptops (including mine!)), tcic (an 8-bit pccard interface) and some sbus chip that I know nothing about). We don't want to have the CIS parsing code replicated in each one. While there is only one known cardbus bridge API today, I don't want to architect something that will be hard to have a different one should it become necessary if there's a cardbusII bridge based on pcix that has a legacy way to support cardbus1 (for example). : > The cardbus bus code : > already deals with the CIS and it should be the one to arrange things : > to happen. We can tweak the current cardbus CIS reading stuff to do : > this and maybe combine it somewhat with the pccard CIS reading stuff. : > Also, the index doesn't make so much sense because each CIS entry is a : > variable length, so we'd have to walk the chain. : : Index is the tuple index, not the byte offset in the CIS; sorry I didn't : make that clear. I'm not sure that I follow what you mean by tuple index then. Is that the Nth CIS, or the CIS of type N? If it is the Nth cis, then we do have to walk N-1 CIS tuples to find it. If it is the CIS of type N, then how do we do multiple ones of type N (which is legal and happens for the config entries)? The CIS is an array of bytes. It lives in 1 or more address spaces. Each CIS tuple contains a length (which is used to find the next one). Some CIS tuples are multi-function chaining tuples and contain two lengths, one of the current CIS tuple, and the aggregate length of all tuples for this function. I do not recall if there's a function number in it, but that is implicit from where we are in the CIS. Each CIS tuple is between 2 and 254 bytes long. To find the Nth one, I have to know where the N-1th one ends for all values of N > 0. The 0th element is pointed to by the CIS pointer in the pci config space. : > Also, this isn't a PCI thing, so no PCI code should be called. :-) : : Interrupts aren't a PCI thing either, but we pass attempts by PCI drivers : to do stuff with them up through the stack. This really isn't any : different. I do think it is different, but maybe we're arguing about semantics here. I'm talking about having the cardbus bus (cardbusN) code do the parsing of the CIS, while asking for assistance from the cardbus bridge code (pccbbN) to apply power to the slot, map in address spaces, etc. The carbus bus code can generically parse the CIS and dole it out to its children by asking the bridge to do certain specific things. The bridge shouldn't be doing the actual parsing. This is a layering argument. The bus is where the resource allocation book keeping takes place, and we'd need it to do that for the CIS stuff that has been mapped so that if the card driver is a bad citizen, it can cleanup properly. I guess I fear putting the cardbus bus function in the cardbus bridge and teaching a regular pci bus to pass them through. I'd rather have the pci bus code reject such attempts and the cardbus bus code process them. : I think that you're overrating the things that need to be "shoehorned" : into PCI to make it a comfortable superset of stock PCI + hot-plug PCI + : CardBus. So far all we have is passing through a CIS tuple accessor : function. 8) It isn't just an accessor to a configuration space, like PCI has. It is access to a byte stream that may live in many different spaces, even on the same card (this was true of 16-bit cards, I'm not sure of the 32-bit cards). Again, we have a disagreement about where the parsing should rightly be done and where information about the state of the parsing and resouce maps should be cached. These tuples aren't like PCI configuration space. That makes sense to have at the bridge level because no parsing is necessary. The accessors for the CIS just don't make sense because the CIS tuples are variable length and are more expensive to map in and out than the pci configuration space. The CIS is also read-only, whereas the pci config space is read/write to configure the card. The attribtue memory for 16-bit cards can be written to and is usually where the CIS lives, but that's something altogether different. Maybe I'm not explaining well, or maybe there are issues here that I don't understand. I am finding it hard to understand exactly what you are suggesting at times. I think I have it, but it just doesn't make sense. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 22:23:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id E0DD037B4CF; Tue, 21 Nov 2000 22:23:11 -0800 (PST) Received: from aslan (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.0/8.9.3) with ESMTP id eAM6N9473750; Tue, 21 Nov 2000 23:23:09 -0700 (MST) (envelope-from gibbs@aslan.scsiguy.com) Message-Id: <200011220623.eAM6N9473750@aslan.scsiguy.com> To: Warner Losh Cc: Mike Smith , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-Reply-To: Your message of "Tue, 21 Nov 2000 21:42:02 MST." <200011220442.VAA39910@harmony.village.org> Date: Tue, 21 Nov 2000 23:23:09 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In message <200011220427.eAM4RYF00772@mass.osd.bsdi.com> Mike Smith writes: >: No; the CIS parser should know which function it's being called on behalf >: of, and simply elide the tuples that don't relate to that function. > >This isn't always the right thing to do. At least in the 16-bit >world, there are drivers that want to look at the CIS entries for the >other function of the card for various reasons (some of them need to >know what kind of modem is present, iirc, to initalize some things in >a non-standard way, the example was the NetBSD driver mhz, iirc). I >don't wish to preclude that. The ROM BAR is only implemented for function 0 and the ROM contains information for all functions of the chip. So, functions greater than 0 must have the flexibility to activate at least the ROM BAR on function 0 as well as access that region. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 22:28:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id B73FA37B479 for ; Tue, 21 Nov 2000 22:28:32 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAM6ZYF01178; Tue, 21 Nov 2000 22:35:35 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011220635.eAM6ZYF01178@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Justin T. Gibbs" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-reply-to: Your message of "Tue, 21 Nov 2000 23:23:09 MST." <200011220623.eAM6N9473750@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Nov 2000 22:35:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >In message <200011220427.eAM4RYF00772@mass.osd.bsdi.com> Mike Smith writes: > >: No; the CIS parser should know which function it's being called on behalf > >: of, and simply elide the tuples that don't relate to that function. > > > >This isn't always the right thing to do. At least in the 16-bit > >world, there are drivers that want to look at the CIS entries for the > >other function of the card for various reasons (some of them need to > >know what kind of modem is present, iirc, to initalize some things in > >a non-standard way, the example was the NetBSD driver mhz, iirc). I > >don't wish to preclude that. > > The ROM BAR is only implemented for function 0 and the ROM > contains information for all functions of the chip. So, functions > greater than 0 must have the flexibility to activate at least the ROM > BAR on function 0 as well as access that region. Does the driver need the ROM, or the CIS which may be inside the ROM? If the driver needs structured information from inside the ROM, this falls into the same category as the CIS. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Nov 21 23: 3:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E42DC37B4CF; Tue, 21 Nov 2000 23:03:37 -0800 (PST) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.0/8.11.0) with ESMTP id eAM73aQ34017; Wed, 22 Nov 2000 00:03:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA40559; Wed, 22 Nov 2000 00:03:36 -0700 (MST) Message-Id: <200011220703.AAA40559@harmony.village.org> To: "Justin T. Gibbs" Subject: Re: Getting at cardbus CIS data from inside drivers Cc: Mike Smith , wpaul@FreeBSD.ORG (Bill Paul), freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Nov 2000 23:23:09 MST." <200011220623.eAM6N9473750@aslan.scsiguy.com> References: <200011220623.eAM6N9473750@aslan.scsiguy.com> Date: Wed, 22 Nov 2000 00:03:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011220623.eAM6N9473750@aslan.scsiguy.com> "Justin T. Gibbs" writes: : The ROM BAR is only implemented for function 0 and the ROM : contains information for all functions of the chip. So, functions : greater than 0 must have the flexibility to activate at least the ROM : BAR on function 0 as well as access that region. I think there's a difference between where the CIS actually lives, and the CIS chains for the each function. cardbus cards give each function its own CIS chain. These CIS chains can live in configuration space, in memory space or the expansion ROM (which I assume is the same thing as the ROM BAR on function 0, but maybe I'm mistaken) and the bridge is responsible for properlly mapping the last two. The config space presents the biggest problem because we don't have any way to access it with the bus_space(9) functions, so special code is needed in the cardbus bus driver to know where to read from. I talked with YAMAMOTO shigeru-san at BSDcon about an extension to the bus_space code to allow user defined regions/functions to be used so that one can write generic code to access each of these regions with bus_space_read/write_N. Since this is getting off topic, I'll leave it there, but it looked cool and many of the issues I could think of to bring up were handled well. I also made an error in a previous message. 16-bit and 32bit cis parsing is somewhat different. 16-bit cards effectively have the functions comingled with global entries, while cardbus segregates them. With cardbus the iterated chain would just contain CIS entries for that function. They designed things this way so that the functions could be completely separate, integrated only on an ASIC at the last minute before being placed on a cardbus card :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 0: 7: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id 8A86337B479 for ; Wed, 22 Nov 2000 00:06:58 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eAM8EGF01417; Wed, 22 Nov 2000 00:14:16 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011220814.eAM8EGF01417@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: Getting at cardbus CIS data from inside drivers In-reply-to: Your message of "Wed, 22 Nov 2000 00:03:35 MST." <200011220703.AAA40559@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Nov 2000 00:14:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > function its own CIS chain. These CIS chains can live in > configuration space, in memory space or the expansion ROM (which I > assume is the same thing as the ROM BAR on function 0, but maybe I'm > mistaken) and the bridge is responsible for properlly mapping the last > two. > > The config space presents the biggest problem because we don't have > any way to access it with the bus_space(9) functions, so special code > is needed in the cardbus bus driver to know where to read from. The code reading the CIS should be using callbacks into the hardware-specific code, which will know how to read/write PCI configuration space. Having said that, there's a good argument to be made for adding PCI configuration space as a new bus_space type. Any thoughts on why this might be a bad idea? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 6:19:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns5.pacific.net.au (ns5.pacific.net.au [203.143.252.30]) by hub.freebsd.org (Postfix) with ESMTP id 358A637B4C5 for ; Wed, 22 Nov 2000 06:19:44 -0800 (PST) Received: from dungeon.home (ppp110.dyn250.pacific.net.au [203.143.250.110]) by ns5.pacific.net.au (8.9.0/8.9.1) with ESMTP id BAA27869 for ; Thu, 23 Nov 2000 01:19:39 +1100 (EST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.9.3/8.9.3) with ESMTP id AAA22195; Thu, 23 Nov 2000 00:26:54 +1000 (EST) (envelope-from mckay) Message-Id: <200011221426.AAA22195@dungeon.home> To: freebsd-current@freebsd.org Cc: mckay@thehub.com.au Subject: A tiny Perl bug? Date: Thu, 23 Nov 2000 00:26:53 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was trying to get FreeBSD 4.2-BETA to compile under FreeBSD 3.4 when I found that the use of the new setresgid() and setresuid() system calls were causing the perl5 compile to fail. I got around this using NOPERL=yup but while investigating I noticed an apparent bug in the use of setresgid() and propose this patch: Index: mg.c =================================================================== RCS file: /cvs/src/contrib/perl5/mg.c,v retrieving revision 1.1.1.4 diff -u -r1.1.1.4 mg.c --- mg.c 2000/08/20 08:42:14 1.1.1.4 +++ mg.c 2000/11/22 12:01:32 @@ -1926,7 +1926,7 @@ (void)setregid((Gid_t)PL_gid, (Gid_t)-1); #else #ifdef HAS_SETRESGID - (void)setresgid((Gid_t)PL_gid, (Gid_t)-1, (Gid_t) 1); + (void)setresgid((Gid_t)PL_gid, (Gid_t)-1, (Gid_t)-1); #else if (PL_gid == PL_egid) /* special case $( = $) */ (void)PerlProc_setgid(PL_gid); I assume this was just a typo. I can't think of any reason to try to set the saved uid to daemon. I'd whip in and commit this myself, but I'm sure there are "vendor branch considerations", and I've never found out what's involved with that. And piggybacking a slightly wider issue: The cross-tools section of Makefile.inc1 is supposed to address the use of new system calls and such in build tools, right? Can we forget about the old "try to use the new syscall and do something else if it isn't there" code? And all we need to do to fix my migration problem is to MFC marcel's miniperl cross-build fix? Right? Otherwise I have all this blather I was going to say about using fancy new syscalls in perl just to emulate old syscalls we already have, and the way that makes upgrading harder. But I don't have to go on about that, it seems. :-) Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 6:31:55 2000 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 7CE3F37B4CF; Wed, 22 Nov 2000 06:31:51 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id JAA06680; Wed, 22 Nov 2000 09:31:51 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eAMEVos64701; Wed, 22 Nov 2000 09:31:50 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 22 Nov 2000 09:31:50 -0500 (EST) To: "John W. De Boskey" Cc: Current List Subject: Re: No console on AlphaServer 2000 4/233 4.2-RC2 In-Reply-To: <20001121125955.A76196@FreeBSD.org> References: <20001121125955.A76196@FreeBSD.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14875.55102.709671.416932@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. De Boskey writes: > > Hi, > > Console, console, where's the console? The SRM console is using a TGA video card as the console output device. TGA is not supported by syscons. So FreeBSD is forced to use the serial console instead... You can "fix" this by using just about any $10 pci vga card you happen to have laying around in place of the TGA card. Or hook up a 9600 8,n,1 connection to the 1st serial port and tell the srm to use it as a console (>>> set console serial) > > and dmesg: (Yes, the 1st 2 lines are from dmesg, and I cannot > find where they are coming from yet). > Unrecognized boot flag '0'. > Unrecognized boot flag ','. They're coming from the kernel, I think. You probably have 'boot_osflags' set to something like '0,a' in the srm console. Clear that variable, or set it to "a" and those messages will go away. > pci0: (vendor=0x1011, dev=0x0004) at 6.0 irq 32 FWIW, this is the TGA card. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 8:44:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from squishycow.goldenterrace.com.au (squishycow.goldenterrace.com.au [203.41.110.130]) by hub.freebsd.org (Postfix) with ESMTP id 765C837B4CF for ; Wed, 22 Nov 2000 08:44:15 -0800 (PST) Received: by squishycow.goldenterrace.com.au (Postfix, from userid 1000) id E83E419D02; Thu, 23 Nov 2000 03:44:11 +1100 (EST) Date: Thu, 23 Nov 2000 03:44:11 +1100 From: Steve Horan To: -CURRENT Subject: Laptops and sc0/vt0 consoles Message-ID: <20001123034411.F377@goldenterrace.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Apologies upfront if anything I ask/say has already been covered, I'm somwhat limited in my resources at present. In my past experience, FreeBSD hasn't agreed very well with IBM thinkpad laptops, unless you were using the vt0 console driver. This makes me ask a couple of questions: 1) Does vt0 work for everything? Or only laptops? (my understanding is that it works for "everything" 2) If 1) is true, why doesn't the kernel on install floppies/cd's use vt0 instead of sc0. I haven't been able to test with anything post 3.4, so again, apologies if sc0 has been fixed to work with thinkpads etc. Just thought this could be worth raising, would be curious of peoples thoughts. Regards, sjh. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 9:53:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.yogotech.com (ns.yogotech.com [206.127.123.66]) by hub.freebsd.org (Postfix) with ESMTP id 6C31637B479 for ; Wed, 22 Nov 2000 09:53:47 -0800 (PST) Received: from nomad.yogotech.com (nomad.yogotech.com [206.127.123.131]) by ns.yogotech.com (8.9.3/8.9.3) with ESMTP id KAA10613; Wed, 22 Nov 2000 10:53:46 -0700 (MST) (envelope-from nate@nomad.yogotech.com) Received: (from nate@localhost) by nomad.yogotech.com (8.8.8/8.8.8) id KAA05592; Wed, 22 Nov 2000 10:53:41 -0700 (MST) (envelope-from nate) From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14876.2084.621017.530399@nomad.yogotech.com> Date: Wed, 22 Nov 2000 10:53:40 -0700 (MST) To: Steve Horan Cc: -CURRENT Subject: Re: Laptops and sc0/vt0 consoles In-Reply-To: <20001123034411.F377@goldenterrace.com.au> References: <20001123034411.F377@goldenterrace.com.au> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-To: nate@yogotech.com (Nate Williams) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Apologies upfront if anything I ask/say has already been covered, I'm > somwhat limited in my resources at present. > > In my past experience, FreeBSD hasn't agreed very well with IBM > thinkpad laptops, unless you were using the vt0 console driver. This is *VERY* old information. When Pentium's were introduced (755/560) series, it has no longer been a necessity. The old 486 laptops need vt0, but anything newer works fine with sc0. (I speak from experience, having had an IBM laptop for 7-8 years, and being responsible for writing or integrating the code in FreeBSD to support IBM Thinkpads.) I'm also typing on a ThinkPad right now, which is my 'main' platform, and it's doing fine with syscons, as have my previous 3 ThinkPads. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 10:19:59 2000 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 7A2D237B661; Wed, 22 Nov 2000 10:19:56 -0800 (PST) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13yeUr-0000i7-00; Wed, 22 Nov 2000 18:19:53 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.1/8.11.0) id eAMIIpk01515; Wed, 22 Nov 2000 19:18:51 +0100 (CET) (envelope-from wkb) Date: Wed, 22 Nov 2000 19:18:51 +0100 From: Wilko Bulte To: Andrew Gallatin Cc: "John W. De Boskey" , Current List Subject: Re: No console on AlphaServer 2000 4/233 4.2-RC2 Message-ID: <20001122191851.F926@freebie.demon.nl> References: <20001121125955.A76196@FreeBSD.org> <14875.55102.709671.416932@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14875.55102.709671.416932@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Nov 22, 2000 at 09:31:50AM -0500 X-OS: FreeBSD 4.2-RELEASE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 22, 2000 at 09:31:50AM -0500, Andrew Gallatin wrote: > John W. De Boskey writes: > > > > and dmesg: (Yes, the 1st 2 lines are from dmesg, and I cannot > > find where they are coming from yet). > > > Unrecognized boot flag '0'. > > Unrecognized boot flag ','. > > They're coming from the kernel, I think. You probably have > 'boot_osflags' set to something like '0,a' in the srm console. Probably a leftover from a previous VMS life: 0,0 is for VMS. -- Wilko Bulte Arnhem, the Netherlands wilko@freebsd.org http://www.freebsd.org http://www.nlfug.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 12:41: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id BE70D37B4CF; Wed, 22 Nov 2000 12:40:42 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAMKefa01052; Wed, 22 Nov 2000 21:40:41 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org, arch@freebsd.org Subject: RFC: /dev/console -> /var/log/messages idea/patch From: Poul-Henning Kamp Date: Wed, 22 Nov 2000 21:40:41 +0100 Message-ID: <1050.974925641@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The attached patch is a "proof-of-concept" on which I would like to get some comments: It bugs me big time that the output from /etc/rc and all other output to /dev/console is volatile and lost once it scrolls of your console. It particular bugs me for systems which are configured with a modem on a serial port as console, if something choked badly in /etc/rc I will never know. (Don't tell me to use a SilentWriter or DecWriter as console, OK ? Been There, Done That, Got The Piles Of Paper To Prove It. :-) Ideally our console would be much more functional, but that is a project which would fall sideways off my todo list if I tried to balance it there. (If anybody is looking for a medium complex kernel task, a new console system is a place to look. Enquire within). So I though about it from a "how little can we get away with" and realized that by simply grabbing a copy of everything written to /dev/console and feeding it to syslogd would gain us a lot of mileage. Now, there are several issues to understand here, so please read on before you apply paint to this bikeshed: By "/dev/console" output I mean just and only that. Characters which arrive by write(2)/writev(2) on a fd opened to "/dev/console". Kernel printfs are not /dev/console output in this context. Characters written directly to your console device ("/dev/ttyd0", "/dev/ttyv0" or "/dev/cuaa0") are *not* /dev/console output either. Input from /dev/console are not part of this. You will not be able to see the answers people give fsck. The output do of course still also arrive on your console device. Obviously, if syslogd were to write these messages back to /dev/console bad things would happen. Syslogd may need to gain a tabu there. The formatting cannot be preserved. If somebody were to: echo -n "You're screwed now ---> " > /dev/console we would never see the message in syslogd if the code waited for the final '\n' to arrive. (I guess a timeout based solution could be feasible, what do people think ?) In this patch I have deliberatly output a '"' in front of all messages, this is merely for debugging right now. The patch probably has all sorts of issues, style, locking, you name it. It is only intended as a proof-of-concept patch. Sample output from /var/log/messages attached below. Comments, volounteers, ideas most welcome... Poul-Henning Nov 22 21:16:38 syv /boot/kernel/kernel: "swapon: adding /dev/ad1s1b as swap device Nov 22 21:16:38 syv /boot/kernel/kernel: "swapon: adding /dev/ad0s1b as swap device Nov 22 21:16:38 syv /boot/kernel/kernel: "Automatic boot in progress... Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad0s1a: Nov 22 21:16:38 syv /boot/kernel/kernel: "FILESYSTEM CLEAN; SKIPPING CHECKS Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad0s1a: Nov 22 21:16:38 syv /boot/kernel/kernel: "clean, 134807 free Nov 22 21:16:38 syv /boot/kernel/kernel: "(823 frags, 16748 blocks, 0.4% fragmentation) Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad1s1e: Nov 22 21:16:38 syv /boot/kernel/kernel: "FILESYSTEM CLEAN; SKIPPING CHECKS Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad1s1e: Nov 22 21:16:38 syv /boot/kernel/kernel: "clean, 184706 free Nov 22 21:16:38 syv /boot/kernel/kernel: "(138 frags, 23071 blocks, 0.1% fragmentation) Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad1s1f: Nov 22 21:16:38 syv /boot/kernel/kernel: "FILESYSTEM CLEAN; SKIPPING CHECKS Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad1s1f: Nov 22 21:16:38 syv /boot/kernel/kernel: "clean, 1775231 free Nov 22 21:16:38 syv /boot/kernel/kernel: "(13343 frags, 220236 blocks, 0.7% fragmentation) Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad0s1e: Nov 22 21:16:38 syv /boot/kernel/kernel: "FILESYSTEM CLEAN; SKIPPING CHECKS Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ad0s1e: Nov 22 21:16:38 syv /boot/kernel/kernel: "clean, 2032838 free Nov 22 21:16:38 syv /boot/kernel/kernel: "(14 frags, 254103 blocks, 0.0% fragmentation) Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ccd0c: Nov 22 21:16:38 syv /boot/kernel/kernel: "FILESYSTEM CLEAN; SKIPPING CHECKS Nov 22 21:16:38 syv /boot/kernel/kernel: "/dev/ccd0c: Nov 22 21:16:38 syv /boot/kernel/kernel: "clean, 3464429 free Nov 22 21:16:38 syv /boot/kernel/kernel: "(3245 frags, 865296 blocks, 0.1% fragmentation) Nov 22 21:16:38 syv /boot/kernel/kernel: "Can't use /entropy as an entropy file, trying other sources Nov 22 21:16:38 syv /boot/kernel/kernel: "cat: Nov 22 21:16:38 syv /boot/kernel/kernel: "malloc.conf Nov 22 21:16:38 syv /boot/kernel/kernel: ": Nov 22 21:16:38 syv /boot/kernel/kernel: "No such file or directory Nov 22 21:16:38 syv /boot/kernel/kernel: "Doing initial network setup: Nov 22 21:16:38 syv /boot/kernel/kernel: " hostname Nov 22 21:16:38 syv /boot/kernel/kernel: ". Nov 22 21:16:38 syv /boot/kernel/kernel: "fxp0: flags=8843 mtu 1500 Nov 22 21:16:38 syv /boot/kernel/kernel: " inet 212.242.40.133 netmask 0xfffffff0 broadcast 212.242.40.143 Nov 22 21:16:38 syv /boot/kernel/kernel: " ether 00:90:27:2c:60:72 Nov 22 21:16:38 syv /boot/kernel/kernel: " media: autoselect (100baseTX ) status: active Nov 22 21:16:38 syv /boot/kernel/kernel: " supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP Nov 22 21:16:38 syv /boot/kernel/kernel: "lo0: flags=8049 mtu 16384 Nov 22 21:16:38 syv /boot/kernel/kernel: " inet 127.0.0.1 netmask 0xff000000 Nov 22 21:16:38 syv /boot/kernel/kernel: "add net default: gateway 212.242.40.129 Nov 22 21:16:38 syv /boot/kernel/kernel: "Additional routing options: Nov 22 21:16:38 syv /boot/kernel/kernel: " tcp extensions=NO Nov 22 21:16:38 syv /boot/kernel/kernel: " TCP keepalive=YES Nov 22 21:16:38 syv /boot/kernel/kernel: ". Nov 22 21:16:38 syv /boot/kernel/kernel: "routing daemons: Nov 22 21:16:38 syv /boot/kernel/kernel: ". Nov 22 21:16:38 syv /boot/kernel/kernel: "additional daemons: Nov 22 21:16:38 syv /boot/kernel/kernel: " syslogd Nov 22 21:16:38 syv /boot/kernel/kernel: ". Nov 22 21:16:38 syv /boot/kernel/kernel: "rm: Nov 22 21:16:38 syv /boot/kernel/kernel: "/var/run/dev.db Nov 22 21:16:38 syv /boot/kernel/kernel: ": Nov 22 21:16:38 syv /boot/kernel/kernel: "No such file or directory Nov 22 21:16:38 syv /boot/kernel/kernel: "Doing additional network setup: Nov 22 21:16:38 syv /boot/kernel/kernel: " portmap Nov 22 21:16:39 syv /boot/kernel/kernel: ". Nov 22 21:16:39 syv /boot/kernel/kernel: "Starting final network daemons: Nov 22 21:16:39 syv /boot/kernel/kernel: ". Nov 22 21:16:39 syv /boot/kernel/kernel: "setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib Nov 22 21:16:39 syv /boot/kernel/kernel: "setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Nov 22 21:16:39 syv /boot/kernel/kernel: "starting standard daemons: Nov 22 21:16:39 syv /boot/kernel/kernel: " inetd Nov 22 21:16:39 syv /boot/kernel/kernel: " cron Nov 22 21:16:39 syv /boot/kernel/kernel: " sendmail Nov 22 21:16:39 syv /boot/kernel/kernel: " sshd Nov 22 21:16:39 syv /boot/kernel/kernel: ". Nov 22 21:16:39 syv /boot/kernel/kernel: "Recovering vi editor sessions Nov 22 21:16:40 syv /boot/kernel/kernel: "Initial rc.i386 initialization: Nov 22 21:16:40 syv /boot/kernel/kernel: ". Nov 22 21:16:40 syv /boot/kernel/kernel: "rc.i386 configuring syscons: Nov 22 21:16:40 syv /boot/kernel/kernel: " blank_time Nov 22 21:16:40 syv /boot/kernel/kernel: ". Nov 22 21:16:40 syv /boot/kernel/kernel: "additional ABI support: Nov 22 21:16:40 syv /boot/kernel/kernel: ". Nov 22 21:16:40 syv /boot/kernel/kernel: "Local package initialization: Nov 22 21:16:40 syv /boot/kernel/kernel: ". Nov 22 21:16:40 syv /boot/kernel/kernel: "Additional TCP options: Nov 22 21:16:40 syv /boot/kernel/kernel: ". Index: sys/syslog.h =================================================================== RCS file: /home/ncvs/src/sys/sys/syslog.h,v retrieving revision 1.19 diff -u -r1.19 syslog.h --- sys/syslog.h 1999/12/29 04:24:48 1.19 +++ sys/syslog.h 2000/11/22 20:02:26 @@ -107,6 +107,7 @@ #define LOG_FTP (11<<3) /* ftp daemon */ #define LOG_NTP (12<<3) /* NTP subsystem */ #define LOG_SECURITY (13<<3) /* security subsystems (firewalling, etc.) */ +#define LOG_CONSOLE (14<<3) /* /dev/console output */ /* other codes through 15 reserved for system use */ #define LOG_LOCAL0 (16<<3) /* reserved for local use */ @@ -127,6 +128,7 @@ CODE facilitynames[] = { { "auth", LOG_AUTH, }, { "authpriv", LOG_AUTHPRIV, }, + { "console", LOG_CONSOLE, }, { "cron", LOG_CRON, }, { "daemon", LOG_DAEMON, }, { "ftp", LOG_FTP, }, Index: kern/subr_prf.c =================================================================== RCS file: /home/ncvs/src/sys/kern/subr_prf.c,v retrieving revision 1.64 diff -u -r1.64 subr_prf.c --- kern/subr_prf.c 2000/10/02 07:13:10 1.64 +++ kern/subr_prf.c 2000/11/22 20:14:50 @@ -49,6 +49,7 @@ #include #include #include +#include /* * Note that stdarg.h and the ANSI style va_start macro is used for both @@ -223,6 +224,52 @@ logwakeup(); return retval; } + +#define CONSCHUNK 4096 +static char consbuffer[CONSCHUNK]; + +void +log_console(struct uio *uio) +{ + int s, c, i, error, iovlen, nlf = 0; + struct uio muio; + struct iovec *miov = NULL; + + muio = *uio; + iovlen = uio->uio_iovcnt * sizeof (struct iovec); + MALLOC(miov, struct iovec *, iovlen, M_TEMP, M_WAITOK); + bcopy((caddr_t)muio.uio_iov, (caddr_t)miov, iovlen); + muio.uio_iov = miov; + uio = &muio; + + s = splhigh(); + error = 0; + while (error == 0 && uio->uio_resid > 0) { + c = imin(uio->uio_resid, CONSCHUNK); + error = uiomove(consbuffer, c, uio); + if (!error) { + for (i = 0; i < c; i++) { + if (!nlf) { + logpri(LOG_INFO | LOG_CONSOLE); + msglogchar('"', 0); + nlf = 1; + } + msglogchar(consbuffer[i], 0); + if (consbuffer[i] == '\n') { + nlf = 0; + logwakeup(); + } + } + } + } + if (nlf) + msglogchar('\n', 0); + logwakeup(); + splx(s); + FREE(miov, M_TEMP); + return; +} + static void logpri(level) Index: kern/tty_cons.c =================================================================== RCS file: /home/ncvs/src/sys/kern/tty_cons.c,v retrieving revision 1.84 diff -u -r1.84 tty_cons.c --- kern/tty_cons.c 2000/10/29 16:06:34 1.84 +++ kern/tty_cons.c 2000/11/22 20:20:20 @@ -352,6 +352,7 @@ dev = constty->t_dev; else dev = cn_tab->cn_dev; + log_console(uio); return ((*devsw(dev)->d_write)(dev, uio, flag)); } -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 12:58:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from kyra.unloved.org (kyra.unloved.org [62.58.62.162]) by hub.freebsd.org (Postfix) with ESMTP id EEC6E37B4CF; Wed, 22 Nov 2000 12:58:11 -0800 (PST) Received: from ashp by kyra.unloved.org with local (Exim 3.15 #1) id 13ygyi-000Jbd-00; Wed, 22 Nov 2000 21:58:52 +0100 Date: Wed, 22 Nov 2000 21:58:52 +0100 From: Ashley Penney To: Poul-Henning Kamp Cc: current@freebsd.org, arch@freebsd.org Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch Message-ID: <20001122215852.A75332@kyra.unloved.org> References: <1050.974925641@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1050.974925641@critter>; from phk@freebsd.org on Wed, Nov 22, 2000 at 09:40:41PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 22, 2000 at 09:40:41PM +0100, Poul-Henning Kamp said: > > The attached patch is a "proof-of-concept" on which I would like > to get some comments: I'm only a moronic user, but this would make my life easier. My machine switches into 132x43 on startup, and I always lose the output. So this is just me saying "Yay for phk." -- Pine vs Mutt : It's like the difference between playing with yourself and getting head from a hot girl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 13:12:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 38AD237B4C5; Wed, 22 Nov 2000 13:12:27 -0800 (PST) Received: (from dan@localhost) by dan.emsphone.com (8.11.1/8.11.1) id eAMLCMU07305; Wed, 22 Nov 2000 15:12:22 -0600 (CST) (envelope-from dan) Date: Wed, 22 Nov 2000 15:12:22 -0600 From: Dan Nelson To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch Message-ID: <20001122151221.A29341@dan.emsphone.com> References: <1050.974925641@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <1050.974925641@critter>; from "Poul-Henning Kamp" on Wed Nov 22 21:40:41 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Nov 22), Poul-Henning Kamp said: > The attached patch is a "proof-of-concept" on which I would like to > get some comments: > > It bugs me big time that the output from /etc/rc and all other output > to /dev/console is volatile and lost once it scrolls of your console. SCO logs its startup by simply piping the output of its rc scripts through "2>&1 | tee -a /usr/adm/rc#.log". We could do something similar by wrapping everything after the "mount -a -t nonfs" command on like 174 with { } 2>&1 | tee -a /var/log/boot.log -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 13:22:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 98CDF37B4CF; Wed, 22 Nov 2000 13:22:47 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAMLMda01472; Wed, 22 Nov 2000 22:22:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dan Nelson Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: Your message of "Wed, 22 Nov 2000 15:12:22 CST." <20001122151221.A29341@dan.emsphone.com> Date: Wed, 22 Nov 2000 22:22:39 +0100 Message-ID: <1470.974928159@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20001122151221.A29341@dan.emsphone.com>, Dan Nelson writes: >In the last episode (Nov 22), Poul-Henning Kamp said: >> The attached patch is a "proof-of-concept" on which I would like to >> get some comments: >> >> It bugs me big time that the output from /etc/rc and all other output >> to /dev/console is volatile and lost once it scrolls of your console. > >SCO logs its startup by simply piping the output of its rc scripts >through "2>&1 | tee -a /usr/adm/rc#.log". We could do something >similar by wrapping everything after the "mount -a -t nonfs" command on >like 174 with I've tried stuff like that and I didn't particularly like the result, for one thing many programs (or maybe it was tee(1) itself) changed buffering because of the pipe, which meant that the partial lines like "starting standard daemons: inetd cron sendmail sshd." would only arrive on the real console when the final \n arrived. Another particular thing I remember was that some syslog-challenged daemons whine on /dev/console long after /etc/rc has finished. Dump(8) will do something similar if you don't flip the tapes in finite time. So while it goes a long way, I think we need to provide more coverage of "/dev/console" as a concept. Poul-Henning PS: As I said, a decently functional console subsystem would be a nice thing. At the very least I would want to be able to specify: console output to /dev/ttyd0, /dev/ttyv0 and /var/log/console console input from /dev/ttyd0 or /dev/ttyv0. and preferably with a scrollback buffer too. Network consoles would be nice as well. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 13:49:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 8CBE337B479 for ; Wed, 22 Nov 2000 13:49:30 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAMLnTa01733 for ; Wed, 22 Nov 2000 22:49:29 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: sound card errors in -current ? From: Poul-Henning Kamp Date: Wed, 22 Nov 2000 22:49:29 +0100 Message-ID: <1731.974929769@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on a -current system when loading snd_maestro some time after boot. pcm0: port 0x1400-0x14ff irq 5 at device 8.0 on pci0 pcm0: chn_init() for (play:0) failed pcm0: offset 0xfef7a000 exceeds limit. pcm0: chn_init() for (play:1) failed pcm0: offset 0xfefa9000 exceeds limit. pcm0: chn_init() for (play:2) failed pcm0: offset 0xfefb5000 exceeds limit. pcm0: chn_init() for (play:3) failed -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 14:42:24 2000 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 6D46837B4CF for ; Wed, 22 Nov 2000 14:42:21 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA48717; Wed, 22 Nov 2000 17:39:34 -0500 (EST) (envelope-from wollman) Date: Wed, 22 Nov 2000 17:39:34 -0500 (EST) From: Garrett Wollman Message-Id: <200011222239.RAA48717@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: <1470.974928159@critter> References: <20001122151221.A29341@dan.emsphone.com> <1470.974928159@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Another particular thing I remember was that some syslog-challenged > daemons whine on /dev/console long after /etc/rc has finished. They can try, but by the time they do the console has already been revoke()d, so they no longer have access to the real console. I've thought about writing daemon(8) which will put these turkeys in their place. Just a Small Matter of Programming.... -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 14:44:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id CC7DC37B479 for ; Wed, 22 Nov 2000 14:44:18 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAMMiCa02212; Wed, 22 Nov 2000 23:44:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: Your message of "Wed, 22 Nov 2000 17:39:34 EST." <200011222239.RAA48717@khavrinen.lcs.mit.edu> Date: Wed, 22 Nov 2000 23:44:12 +0100 Message-ID: <2210.974933052@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011222239.RAA48717@khavrinen.lcs.mit.edu>, Garrett Wollman write s: >< said: > >> Another particular thing I remember was that some syslog-challenged >> daemons whine on /dev/console long after /etc/rc has finished. > >They can try, but by the time they do the console has already been >revoke()d, so they no longer have access to the real console. I don't know what you consider "the real console", but opening "/dev/console" and barfing on it works all the time. (Well, *almost* all the time, not if you have foobar'ed your serial console but...) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 15:32: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from riffraff.plig.net (riffraff.plig.net [195.40.6.40]) by hub.freebsd.org (Postfix) with ESMTP id 1FD8D37B4D7 for ; Wed, 22 Nov 2000 15:31:50 -0800 (PST) Received: (from rv@localhost) by riffraff.plig.net (8.9.3/8.9.0) id XAA86801 for freebsd-current@freebsd.org; Wed, 22 Nov 2000 23:31:45 GMT Date: Wed, 22 Nov 2000 23:31:45 +0000 From: Russell Vincent To: freebsd-current@freebsd.org Subject: Kernel panic with ipfw pipes Message-ID: <20001122233145.A86303@riffraff.plig.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="ZGiS0Q5IWpPtfppv" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline The attached kernel panic occurs when a connection is made that would pass through an ipfw pipe configured as: ipfw add 1000 pipe 1 tcp from any 119 to any out ipfw add 1001 pipe 2 tcp from any to any 119 in ipfw pipe 1 config bw 64Kbit/s ipfw pipe 2 config bw 64Kbit/s I can reproduce this at will (and have the vmcore), so if anyone needs more details, just let me know. This is -current of a few days ago (18th Nov 2000, if I recall correctly). -Russell --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="kgdb.out" GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 4771840 initial pcb at 3de1e0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x7f7b1028 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0248899 stack pointer = 0x10:0xc7098be4 frame pointer = 0x10:0xc7098c30 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 = 12 (swi6: clock) trap number = 12 panic: page fault syncing disks... 5 5 done Uptime: 1m27s dumping to dev #ad/1, offset 131072 dump ata0: resetting devices .. done 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 dumpsys () at /b/src/sys/kern/kern_shutdown.c:477 477 if (dumping++) { (kgdb) where #0 dumpsys () at /b/src/sys/kern/kern_shutdown.c:477 #1 0xc01e26b3 in boot (howto=256) at /b/src/sys/kern/kern_shutdown.c:320 #2 0xc01e2ad8 in poweroff_wait (junk=0xc039e68f, howto=-966215744) at /b/src/sys/kern/kern_shutdown.c:568 #3 0xc03386b8 in trap_fatal (frame=0xc7098ba4, eva=2138771496) at /b/src/sys/i386/i386/trap.c:941 #4 0xc033843d in trap_pfault (frame=0xc7098ba4, usermode=0, eva=2138771496) at /b/src/sys/i386/i386/trap.c:855 #5 0xc0337ef7 in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = 0, tf_ebp = -955675600, tf_isp = -955675696, tf_ebx = 1, tf_edx = 2138771456, tf_ecx = -24083, tf_eax = -1063531204, tf_trapno = 12, tf_err = 2, tf_eip = -1071347559, tf_cs = 8, tf_eflags = 66118, tf_esp = -1054004288, tf_ss = -1054027776}) at /b/src/sys/i386/i386/trap.c:438 #6 0xc0248899 in ip_output (m0=0xc09bcd00, opt=0x0, ro=0xc12d2be4, flags=0, imo=0x0) at /b/src/sys/netinet/ip_output.c:806 #7 0xc023e526 in transmit_event (pipe=0xc12cd000) at /b/src/sys/netinet/ip_dummynet.c:394 #8 0xc023e72b in ready_event (q=0xc12c2100) at /b/src/sys/netinet/ip_dummynet.c:525 #9 0xc023f467 in dummynet_io (pipe_nr=1, dir=1, m=0xc09bcd00, ifp=0xc09ae400, ro=0xc7098d98, dst=0xc12729d0, rule=0xc123a3a0, flags=0) at /b/src/sys/netinet/ip_dummynet.c:1062 #10 0xc024858b in ip_output (m0=0xc09bcd00, opt=0x0, ro=0xc7098d98, flags=0, imo=0x0) at /b/src/sys/netinet/ip_output.c:497 #11 0xc024f00c in tcp_respond (tp=0x0, ipgen=0xc09bcd3c, th=0xc09bcd50, m=0xc09bcd00, ack=2736966641, seq=0, flags=20) at /b/src/sys/netinet/tcp_subr.c:458 #12 0xc024cfc3 in tcp_input (m=0xc09bcd00, off0=20, proto=6) at /b/src/sys/netinet/tcp_input.c:2303 #13 0xc0244dd8 in ip_input (m=0xc09bcd00) at /b/src/sys/netinet/ip_input.c:729 #14 0xc023e53a in transmit_event (pipe=0xc12cef00) at /b/src/sys/netinet/ip_dummynet.c:399 #15 0xc023e72b in ready_event (q=0xc12c2180) at /b/src/sys/netinet/ip_dummynet.c:525 #16 0xc023eb63 in dummynet (unused=0x0) at /b/src/sys/netinet/ip_dummynet.c:660 #17 0xc01e9ad4 in softclock (dummy=0x0) at /b/src/sys/kern/kern_timeout.c:134 #18 0xc01d95cd in sithd_loop (dummy=0x0) at /b/src/sys/kern/kern_intr.c:227 (kgdb) quit --ZGiS0Q5IWpPtfppv Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=RV # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.278 2000/09/20 17:30:20 wpaul Exp $ machine i386 cpu I586_CPU cpu I686_CPU ident RV maxusers 128 #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" #Default places to look for devices. #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options MFS #Memory Filesystem #options DEVFS #Device Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV # install a CDEV entry in /dev # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=8 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers device ahb # EISA AHA1742 family device ahc # AHA2940 and onboard AIC7xxx devices device amd # AMD 53C974 (Teckram DC-390(T)) device isp # Qlogic family #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets + those of `ncr') device adv device adw device bt device aha 1 device aic # RAID controllers interfaced to the SCSI subsystem device asr # DPT SmartRAID V, VI and Adaptec SCSI RAID device dpt # DPT Smartcache III, IV - See NOTES for options! device mly # Mylex AcceleRAID/eXtremeRAID # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers device aac # Adaptec FSA RAID device ida # Compaq Smart RAID device amr # AMI MegaRAID device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 device atkbd device psm device vga # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Enable this for the pcvt (VT220 compatible) console driver #device vt #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) device apm # PCCARD (PCMCIA) support device card device pcic # Serial (COM) ports device sio # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. device miibus # MII bus support device dc # DEC/Intel 21143 and various workalikes device pcn # AMD Am79C79x PCI 10/100 NICs device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device tx # SMC 9432TX (83c170 ``EPIC'') device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. device ed device ex device ep device fe device cs device sn # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. device an # BayStack 660 and others device awi # Xircom pccard ethernet device xe # Pseudo devices - the number indicates how many units to allocated. device random # Entropy device device loop # Network loopback device ether # Ethernet support device sl # Kernel SLIP device ppp 1 # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif 4 # IPv6 and IPv4 tunneling device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse device urio # Diamond Rio 500 MP3 player # USB Ethernet, requires mii device aue # ADMtek USB ethernet device cue # CATC USB ethernet device kue # Kawasaki LSI USB ethernet # Local mods options DUMMYNET options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPV6FIREWALL #firewall for IPv6 options IPV6FIREWALL_VERBOSE options IPV6FIREWALL_VERBOSE_LIMIT=100 options IPV6FIREWALL_DEFAULT_TO_ACCEPT options IPDIVERT #divert sockets --ZGiS0Q5IWpPtfppv-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 16:58:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 6AF6C37B4CF for ; Wed, 22 Nov 2000 16:58:33 -0800 (PST) Received: from curve.dellroad.org (curve.dellroad.org [10.1.1.30]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id QAA69058 for ; Wed, 22 Nov 2000 16:58:32 -0800 (PST) Received: (from archie@localhost) by curve.dellroad.org (8.11.0/8.11.0) id eAN0wWI62818 for freebsd-current@freebsd.org; Wed, 22 Nov 2000 16:58:32 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200011230058.eAN0wWI62818@curve.dellroad.org> Subject: how to mutex'ify a device driver To: freebsd-current@freebsd.org Date: Wed, 22 Nov 2000 16:58:32 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL82 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As a relatively simple exercise in -current kernel programming, I'm planning to mutex'ify the ichsmb(4) device driver (this is a relatively simple driver that currently uses splhigh()). I'd appreciate some feedback if what I'm doing is the right thing. The plan is to give each instance of the device a mutex. This mutex will be grabbed by both the top level code (when programming the chip to do something or reading the results) and the interrupt code (when servicing an interrupt). So far so good.. but what I don't understand is what happens if the interrupt thread has to block on the mutex? It seems like all other devices sharing the same interrupt (and therefore thread) could be indefinitely blocked from servicing their IRQ's. Or is it just assumed that the top half will never hold the mutex for a "long" time? Thanks, -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 17:26:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 459AA37B479 for ; Wed, 22 Nov 2000 17:26:10 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAN1PZC06331; Wed, 22 Nov 2000 17:25:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200011230058.eAN0wWI62818@curve.dellroad.org> Date: Wed, 22 Nov 2000 17:25:40 -0800 (PST) From: John Baldwin To: Archie Cobbs Subject: RE: how to mutex'ify a device driver Cc: freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Nov-00 Archie Cobbs wrote: > As a relatively simple exercise in -current kernel programming, > I'm planning to mutex'ify the ichsmb(4) device driver (this is > a relatively simple driver that currently uses splhigh()). I'd > appreciate some feedback if what I'm doing is the right thing. > > The plan is to give each instance of the device a mutex. This > mutex will be grabbed by both the top level code (when programming > the chip to do something or reading the results) and the interrupt > code (when servicing an interrupt). This should work. Sort of. You probably want to wait a bit until I commit my cdevsw wrapper patches and an MP safe version of the psm(4) driver which will help detail what has to happen. > So far so good.. but what I don't understand is what happens if > the interrupt thread has to block on the mutex? It seems like all > other devices sharing the same interrupt (and therefore thread) > could be indefinitely blocked from servicing their IRQ's. Or is > it just assumed that the top half will never hold the mutex for > a "long" time? It the interrupt thread blocks on the mutex, then yes, that IRQ will be blocked. However, mutexes are intended to be held for relatively short periods of time. For example, you can't sleep (SSLEEP) with a mutex, so if you are blocked, you won't be blocked for very long. Also, since interrupt threads run at a very high priority, it will run again as soon as the top half releases the mutex. > Thanks, > -Archie -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 17:48:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.ciac.jl.cn (unknown [202.98.16.1]) by hub.freebsd.org (Postfix) with ESMTP id 51B8337B4C5 for ; Wed, 22 Nov 2000 17:48:26 -0800 (PST) Received: from 11 ([159.226.123.49]) by ns.ciac.jl.cn (8.9.1/8.9.1) with SMTP id JAA22980; Thu, 23 Nov 2000 09:40:32 +0800 (CST) Message-ID: <002001c054f0$374f4500$317be29f@11> From: "S.W.Liu" To: "Current List" Cc: "Current List" Subject: rtc-2000.09.22.tgz can't load on my system Date: Thu, 23 Nov 2000 09:53:46 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: base64 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG TXkgc3lzdGVtIGlzIEZyZWVCU0QgNS4wKHNyYy1jdXIuNDYxMikgLCBJIHdhbnQgdG8gcnVuIHZt d2FyZTIgLCBzbyBJIHBrZ19hZGQgcnRjLTIwMDAuMDkuMjIudGd6LiBCdXQgd2hlbiBNeSBjb21w dXRlciBzdGFydGluZywgaXQgc2F5IGNhbid0IGxvYWQgcnRjLmtvLCBFeGVjdXRlIGVycm9yLCBX aHk/DQoNCg0KDQo= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 18:19:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 6634037B4C5; Wed, 22 Nov 2000 18:19:21 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G4G00D26H47KW@field.videotron.net>; Wed, 22 Nov 2000 21:19:19 -0500 (EST) Date: Wed, 22 Nov 2000 21:19:41 -0500 (EST) From: Bosko Milekic Subject: Re: Kernel panic with ipfw pipes In-reply-to: <20001122233145.A86303@riffraff.plig.net> To: Russell Vincent Cc: freebsd-current@FreeBSD.ORG, joe@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Please try this patch and report: http://people.freebsd.org/~bmilekic/ip_pipe.diff joe, it appears that this commit: Revision 1.114 / (download) - annotate - [select for diffs], Sun Oct 29 01:05:07 2000 UTC (3 weeks, 4 days ago) by joe Changes since 1.113: +7 -3 lines Diff to previous 1.113 (colored) Count per-address statistics for IP fragments. Requested by: ru Obtained from: BSD/OS is the cause of the crashes... joe, please verify that this is the correct fix and let me know so that I can commit. On Wed, 22 Nov 2000, Russell Vincent wrote: > The attached kernel panic occurs when a connection is made that > would pass through an ipfw pipe configured as: > > ipfw add 1000 pipe 1 tcp from any 119 to any out > ipfw add 1001 pipe 2 tcp from any to any 119 in > ipfw pipe 1 config bw 64Kbit/s > ipfw pipe 2 config bw 64Kbit/s > > I can reproduce this at will (and have the vmcore), so if anyone needs > more details, just let me know. > > This is -current of a few days ago (18th Nov 2000, if I recall correctly). > > -Russell Thanks, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 19: 7:27 2000 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 D3D0837B479 for ; Wed, 22 Nov 2000 19:07:24 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id WAA50246; Wed, 22 Nov 2000 22:05:17 -0500 (EST) (envelope-from wollman) Date: Wed, 22 Nov 2000 22:05:17 -0500 (EST) From: Garrett Wollman Message-Id: <200011230305.WAA50246@khavrinen.lcs.mit.edu> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: <2210.974933052@critter> References: <200011222239.RAA48717@khavrinen.lcs.mit.edu> <2210.974933052@critter> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > In message <200011222239.RAA48717@khavrinen.lcs.mit.edu>, Garrett Wollman write >> They can try, but by the time they do the console has already been >> revoke()d, so they no longer have access to the real console. > I don't know what you consider "the real console", but opening > "/dev/console" and barfing on it works all the time. We are talking at cross purposes. I am talking about programs which don't properly detach from their controlling terminal (the console, in this case) and then periodically warble things to standard error. Luckily, such programs never seem to bother to check the error returns. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 20:30:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from clmboh1-smtp1.columbus.rr.com (clmboh1-smtp1.columbus.rr.com [65.24.0.110]) by hub.freebsd.org (Postfix) with ESMTP id 1922537B4C5; Wed, 22 Nov 2000 20:30:51 -0800 (PST) Received: from columbus.rr.com (dzerkel@dhcp065-024-166-103.columbus.rr.com [65.24.166.103]) by clmboh1-smtp1.columbus.rr.com (8.9.3/8.9.3) with ESMTP id XAA29589; Wed, 22 Nov 2000 23:27:30 -0500 (EST) Message-ID: <3A1C9D77.57A09D56@columbus.rr.com> Date: Wed, 22 Nov 2000 23:30:48 -0500 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current , dillon@FreeBSD.ORG Subject: COMPAT_SVR4 broken after uipc_syscalls commit (1.77) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The recent renaming of getsock() to holdsock() broke COMPAT_SVR4 (and MISC_FS). I have made a quick stab at fixing it up in src/sys/compat/svr4/svr4_stream.c, but I'm a little hesitent to figure out what is going on in src/sys/miscfs/portal/portal_vfsops.c. Note: I don't actually use COMPAT_SVR4 for anything, it just happened to be in my config and broke. Any way, here is a possible fix. -- Danny J. Zerkel dzerkel@columbus.rr.com --- svr4_stream.c.orig Thu Aug 31 18:54:05 2000 +++ svr4_stream.c Wed Nov 22 22:39:00 2000 @@ -162,7 +162,7 @@ struct uio ktruio; #endif - error = getsock(p->p_fd, s, &fp); + error = holdsock(p->p_fd, s, &fp); if (error) return (error); auio.uio_iov = mp->msg_iov; @@ -174,13 +174,17 @@ auio.uio_resid = 0; iov = mp->msg_iov; for (i = 0; i < mp->msg_iovlen; i++, iov++) { - if ((auio.uio_resid += iov->iov_len) < 0) + if ((auio.uio_resid += iov->iov_len) < 0) { + fdrop(fp, p); return (EINVAL); + } } if (mp->msg_name) { error = getsockaddr(&to, mp->msg_name, mp->msg_namelen); - if (error) + if (error) { + fdrop(fp, p); return (error); + } } else to = 0; if (mp->msg_control) { @@ -229,6 +233,7 @@ bad: if (to) FREE(to, M_SONAME); + fdrop(fp, p); return (error); } @@ -253,7 +258,7 @@ struct uio ktruio; #endif - error = getsock(p->p_fd, s, &fp); + error = holdsock(p->p_fd, s, &fp); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 20:33:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from clmboh1-smtp1.columbus.rr.com (clmboh1-smtp1.columbus.rr.com [65.24.0.110]) by hub.freebsd.org (Postfix) with ESMTP id 9790437B479; Wed, 22 Nov 2000 20:33:34 -0800 (PST) Received: from columbus.rr.com (dzerkel@dhcp065-024-166-103.columbus.rr.com [65.24.166.103]) by clmboh1-smtp1.columbus.rr.com (8.9.3/8.9.3) with ESMTP id XAA29788; Wed, 22 Nov 2000 23:30:14 -0500 (EST) Message-ID: <3A1C9E1D.574887CE@columbus.rr.com> Date: Wed, 22 Nov 2000 23:33:33 -0500 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current , dillon@FreeBSD.ORG Subject: RE: COMPAT_SVR4 broken after uipc_syscalls commit (1.77) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, this time I'll even include the entire patch... -- Danny J. Zerkel dzerkel@columbus.rr.com --- svr4_stream.c.orig Thu Aug 31 18:54:05 2000 +++ svr4_stream.c Wed Nov 22 22:39:00 2000 @@ -162,7 +162,7 @@ struct uio ktruio; #endif - error = getsock(p->p_fd, s, &fp); + error = holdsock(p->p_fd, s, &fp); if (error) return (error); auio.uio_iov = mp->msg_iov; @@ -174,13 +174,17 @@ auio.uio_resid = 0; iov = mp->msg_iov; for (i = 0; i < mp->msg_iovlen; i++, iov++) { - if ((auio.uio_resid += iov->iov_len) < 0) + if ((auio.uio_resid += iov->iov_len) < 0) { + fdrop(fp, p); return (EINVAL); + } } if (mp->msg_name) { error = getsockaddr(&to, mp->msg_name, mp->msg_namelen); - if (error) + if (error) { + fdrop(fp, p); return (error); + } } else to = 0; if (mp->msg_control) { @@ -229,6 +233,7 @@ bad: if (to) FREE(to, M_SONAME); + fdrop(fp, p); return (error); } @@ -253,7 +258,7 @@ struct uio ktruio; #endif - error = getsock(p->p_fd, s, &fp); + error = holdsock(p->p_fd, s, &fp); if (error) return (error); auio.uio_iov = mp->msg_iov; @@ -265,8 +270,10 @@ auio.uio_resid = 0; iov = mp->msg_iov; for (i = 0; i < mp->msg_iovlen; i++, iov++) { - if ((auio.uio_resid += iov->iov_len) < 0) + if ((auio.uio_resid += iov->iov_len) < 0) { + fdrop(fp, p); return (EINVAL); + } } #ifdef KTRACE if (KTRPOINT(p, KTR_GENIO)) { @@ -352,6 +359,7 @@ FREE(fromsa, M_SONAME); if (control) m_freem(control); + fdrop(fp, p); return (error); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 21: 6: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id F408E37B4CF for ; Wed, 22 Nov 2000 21:05:58 -0800 (PST) Received: by relay.butya.kz (Postfix, from userid 1000) id 75848285CC; Thu, 23 Nov 2000 11:05:55 +0600 (ALMT) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id 6ACD9285C4; Thu, 23 Nov 2000 11:05:55 +0600 (ALMT) Date: Thu, 23 Nov 2000 11:05:55 +0600 (ALMT) From: Boris Popov To: Nate Williams Cc: Steve Horan , -CURRENT Subject: Re: Laptops and sc0/vt0 consoles In-Reply-To: <14876.2084.621017.530399@nomad.yogotech.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 Wed, 22 Nov 2000, Nate Williams wrote: > > In my past experience, FreeBSD hasn't agreed very well with IBM > > thinkpad laptops, unless you were using the vt0 console driver. > > This is *VERY* old information. When Pentium's were introduced > (755/560) series, it has no longer been a necessity. > > The old 486 laptops need vt0, but anything newer works fine with sc0. Hmm, then I'm the lucky one :). There is an old ThinkPad 340 (486/4MB/120MB) which runs heavily trimmed down preSMPNG -current with sc driver. The only caveat is that one should specify a flag which disables keyboard reset, because without it machine will silently reboot. Besides that this ThinkPad works as gateway (even with PCMCIA ethernet card) without any problems. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Nov 22 22:40:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id E387637B4C5 for ; Wed, 22 Nov 2000 22:40:49 -0800 (PST) Received: (qmail 83066 invoked by uid 100); 23 Nov 2000 06:40:48 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14876.48112.785320.465213@guru.mired.org> Date: Thu, 23 Nov 2000 00:40:48 -0600 (CST) To: current@freebsd.org Subject: Confusing error messages from shell image activation X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could I get some feedback on ? It's just a one-line kernel patch with some attendant updates in the kernel and libc, but it makes dealing with broken #! scripts *much* saner, and no one has even seen fit to comment on it yet :-(. Thanx, ; Thu, 23 Nov 2000 20:27:44 +1300 From: "turehu" To: Subject: Accept credit cards on-line THE EASY WAY! Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Date: Thu, 23 Nov 2000 08:24:45 +1300 Content-Transfer-Encoding: 8bit Message-Id: <20001123072744.OAIP60565.mta5-rme.xtra.co.nz@themail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No set up fees No monthly interest No minimum transaction fees The only charge is a small percentage of the cost of the transaction. You can not lose money! You only pay fees if you sell your product. Get in the act and launch your online bussiness which will work for you 24hrs a day, seven days a week and it is worldwide. Want to find out more? Go to: http://www.cyberturf.com/creditcard If this Email has reached you by mistake, we apologize. To remove your Email from the mailing list please send: jennifer@nottern.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 0:24:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from riffraff.plig.net (riffraff.plig.net [195.40.6.40]) by hub.freebsd.org (Postfix) with ESMTP id 9293437B4C5; Thu, 23 Nov 2000 00:24:26 -0800 (PST) Received: by riffraff.plig.net (Postfix, from userid 1005) id 0022847B0F; Thu, 23 Nov 2000 08:18:12 +0000 (GMT) Date: Thu, 23 Nov 2000 08:18:12 +0000 From: Russell Vincent To: Bosko Milekic Cc: Russell Vincent , freebsd-current@FreeBSD.ORG, joe@FreeBSD.ORG Subject: Re: Kernel panic with ipfw pipes Message-ID: <20001123081812.A8958@riffraff.plig.net> References: <20001122233145.A86303@riffraff.plig.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from bmilekic@technokratis.com on Wed, Nov 22, 2000 at 09:19:41PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 22, 2000 at 09:19:41PM -0500, Bosko Milekic wrote: > > The attached kernel panic occurs when a connection is made that > > would pass through an ipfw pipe configured as: > Please try this patch and report: > > http://people.freebsd.org/~bmilekic/ip_pipe.diff That seems to have done the trick. The new structure also makes sense when viewed in the kgdb context. Thanks -Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 2:45:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.alcove.fr (smtp.alcove.fr [212.155.209.139]) by hub.freebsd.org (Postfix) with ESMTP id 58A8C37B4CF for ; Thu, 23 Nov 2000 02:45:32 -0800 (PST) Received: from wiliam.alcove-int ([10.16.110.19]) by smtp.alcove.fr with esmtp (Exim 3.12 #1 (Debian)) id 13ytrx-0006f9-00; Thu, 23 Nov 2000 11:44:45 +0100 Received: from nsouch by wiliam.alcove-int with local (Exim 3.12 #1 (Debian)) id 13ytrr-0005FV-00; Thu, 23 Nov 2000 11:44:39 +0100 Date: Thu, 23 Nov 2000 11:44:38 +0100 From: Nicolas Souchu To: Archie Cobbs Cc: freebsd-current@freebsd.org Subject: Mutex, SMBUS, ACPI (Re: how to mutex'ify a device driver) Message-ID: <20001123114438.C19987@wiliam.alcove-int> References: <200011230058.eAN0wWI62818@curve.dellroad.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.4i In-Reply-To: <200011230058.eAN0wWI62818@curve.dellroad.org>; from archie@dellroad.org on Wed, Nov 22, 2000 at 04:58:32PM -0800 Organization: =?iso-8859-1?Q?Alc=F4ve=2C_http:=2F=2Fwww=2Ealcove=2Efr?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Nov 22, 2000 at 04:58:32PM -0800, Archie Cobbs wrote: > As a relatively simple exercise in -current kernel programming, > I'm planning to mutex'ify the ichsmb(4) device driver (this is > a relatively simple driver that currently uses splhigh()). I'd > appreciate some feedback if what I'm doing is the right thing. What are kernel mutex? A new mechanism for spl replacement? Is it introduced with the new SMP? I found nothing in the mail archives... > > The plan is to give each instance of the device a mutex. This > mutex will be grabbed by both the top level code (when programming > the chip to do something or reading the results) and the interrupt > code (when servicing an interrupt). Have you comments about smbus/iicbus? What would you add to the todo list of the framework? Did you participate to ACPI discussions? -- Nicolas Souchu Alcôve - Open Source Software Engineer - http://www.alcove.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 3: 6:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 16A1E37B4C5 for ; Thu, 23 Nov 2000 03:06:10 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eANB5TB19825; Thu, 23 Nov 2000 03:05:29 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Nov 2000 03:05:29 -0800 (PST) From: Matt Dillon Message-Id: <200011231105.eANB5TB19825@earth.backplane.com> To: "Danny J. Zerkel" Cc: FreeBSD Current Subject: Re: RE: COMPAT_SVR4 broken after uipc_syscalls commit (1.77) References: <3A1C9E1D.574887CE@columbus.rr.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Okay, this time I'll even include the entire patch... : :-- Danny J. Zerkel :dzerkel@columbus.rr.com Thanks Danny. I've comitted it. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 4:59:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id 1C48F37B479; Thu, 23 Nov 2000 04:59:15 -0800 (PST) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout0.freenet.de with esmtp (Exim 3.16 #20) id 13yvy0-0005wZ-00; Thu, 23 Nov 2000 13:59:08 +0100 Received: from a38b1.pppool.de ([213.6.56.177] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #20) id 13yvxw-0006Rz-00; Thu, 23 Nov 2000 13:59:06 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.1/8.11.1) with ESMTP id eANC70202422; Thu, 23 Nov 2000 13:07:01 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200011231207.eANC70202422@Magelan.Leidinger.net> Date: Thu, 23 Nov 2000 13:06:58 +0100 (CET) From: Alexander Leidinger Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch To: ashp@unloved.org Cc: phk@FreeBSD.ORG, current@FreeBSD.ORG, arch@FreeBSD.ORG In-Reply-To: <20001122215852.A75332@kyra.unloved.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22 Nov, Ashley Penney wrote: >> The attached patch is a "proof-of-concept" on which I would like >> to get some comments: > > I'm only a moronic user, but this would make my life easier. My machine > switches into 132x43 on startup, and I always lose the output. So this Its in the scrollback buffer. BTW: are you using a recent -current on an UP machine? After the first SMPNG commits the switch to 132x60 caused a hang on my machine and I haven't tested if this still happens. > is just me saying "Yay for phk." Yes. Regarding the "syslog writes messages back to /dev/console" thing: isn't this just a "I want to be able to shoot in my own foot" bikeshed? Bye, Alexander. -- Give a man a fish and you feed him for a day; teach him to use the Net and he won't bother you for weeks. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 11: 4:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id D4B4D37B4C5 for ; Thu, 23 Nov 2000 11:04:51 -0800 (PST) Received: from pretoria-31.budapest.interware.hu ([195.70.53.95] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13z1fs-0004J0-00 for ; Thu, 23 Nov 2000 20:04:49 +0100 Message-ID: <3A1D47C6.D35464F0@elischer.org> Date: Thu, 23 Nov 2000 08:37:26 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: current@freebsd.org Subject: slight improvement in locore.s? Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG locore.s includes: #define ALLOCPAGES(foo) \ movl R(physfree), %esi ; \ movl $((foo)*PAGE_SIZE), %eax ; \ addl %esi, %eax ; \ movl %eax, R(physfree) ; \ movl %esi, %edi ; \ movl $((foo)*PAGE_SIZE),%ecx ; \ xorl %eax,%eax ; \ cld ; \ rep ; \ stosb might it be a very slight optimisation to change this to: #define ALLOCPAGES(foo) \ movl R(physfree), %esi ; \ movl $((foo)*PAGE_SIZE), %eax ; \ movl %eax, %ecx ; \ addl %esi, %eax ; \ movl %eax, R(physfree) ; \ movl %esi, %edi ; \ xorl %eax,%eax ; \ cld ; \ rep ; \ stosb ?? -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 11: 8:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C331C37B4CF for ; Thu, 23 Nov 2000 11:08:30 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id eANJ8TY22735; Thu, 23 Nov 2000 11:08:29 -0800 (PST) Date: Thu, 23 Nov 2000 11:08:28 -0800 From: Alfred Perlstein To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation Message-ID: <20001123110828.V18037@fw.wintelcom.net> References: <14876.48112.785320.465213@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <14876.48112.785320.465213@guru.mired.org>; from mwm@mired.org on Thu, Nov 23, 2000 at 12:40:48AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mike Meyer [001122 22:41] wrote: > Could I get some feedback on http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 >? It's just a > one-line kernel patch with some attendant updates in the kernel and > libc, but it makes dealing with broken #! scripts *much* saner, and no > one has even seen fit to comment on it yet :-(. This patch may break compliance, ENOEXEC is the proper error code, the shell should try to be a bit smarter about explaining why ENOEXEC was returned. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 11:32: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id CBE9B37B4CF for ; Thu, 23 Nov 2000 11:32:04 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eANJVEW21174; Thu, 23 Nov 2000 11:31:14 -0800 (PST) (envelope-from dillon) Date: Thu, 23 Nov 2000 11:31:14 -0800 (PST) From: Matt Dillon Message-Id: <200011231931.eANJVEW21174@earth.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? References: <3A1D47C6.D35464F0@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :might it be a very slight optimisation to change this to: :#define ALLOCPAGES(foo) \ : movl R(physfree), %esi ; \ :... : movl $((foo)*PAGE_SIZE), %eax ; \ ... but why? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 11:41:32 2000 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 B937337B479 for ; Thu, 23 Nov 2000 11:41:29 -0800 (PST) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA20771; Thu, 23 Nov 2000 11:40:02 -0800 (PST) Message-Id: <200011231940.LAA20771@implode.root.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? In-reply-to: Your message of "Thu, 23 Nov 2000 08:37:26 PST." <3A1D47C6.D35464F0@elischer.org> From: David Greenman Reply-To: dg@root.com Date: Thu, 23 Nov 2000 11:40:02 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >locore.s includes: >#define ALLOCPAGES(foo) \ > movl R(physfree), %esi ; \ > movl $((foo)*PAGE_SIZE), %eax ; \ > addl %esi, %eax ; \ > movl %eax, R(physfree) ; \ > movl %esi, %edi ; \ > movl $((foo)*PAGE_SIZE),%ecx ; \ > xorl %eax,%eax ; \ > cld ; \ > rep ; \ > stosb > > >might it be a very slight optimisation to change this to: >#define ALLOCPAGES(foo) \ > movl R(physfree), %esi ; \ > movl $((foo)*PAGE_SIZE), %eax ; \ > movl %eax, %ecx ; \ > addl %esi, %eax ; \ > movl %eax, R(physfree) ; \ > movl %esi, %edi ; \ > xorl %eax,%eax ; \ > cld ; \ > rep ; \ > stosb > >?? Improvement in what way? Readability? I don't think so. Performance? This macro is only used in the initial bootstrap of the kernel. ...changing it might save a few bytes, however. -DG David Greenman Co-founder, The FreeBSD Project - http://www.freebsd.org President, TeraSolutions, Inc. - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 11:44:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 627A537B4C5 for ; Thu, 23 Nov 2000 11:44:10 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eANJhrF04412; Thu, 23 Nov 2000 12:43:53 -0700 (MST) Date: Thu, 23 Nov 2000 12:43:53 -0700 (MST) From: X-Sender: janb@gecko To: David Greenman Cc: Julian Elischer , current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? In-Reply-To: <200011231940.LAA20771@implode.root.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 It does not impair readability. As long as that is true, I believe its prudent to save every byte possible... Only my 2 cents worth. JAn On Thu, 23 Nov 2000, David Greenman wrote: > >locore.s includes: > >#define ALLOCPAGES(foo) \ > > movl R(physfree), %esi ; \ > > movl $((foo)*PAGE_SIZE), %eax ; \ > > addl %esi, %eax ; \ > > movl %eax, R(physfree) ; \ > > movl %esi, %edi ; \ > > movl $((foo)*PAGE_SIZE),%ecx ; \ > > xorl %eax,%eax ; \ > > cld ; \ > > rep ; \ > > stosb > > > > > >might it be a very slight optimisation to change this to: > >#define ALLOCPAGES(foo) \ > > movl R(physfree), %esi ; \ > > movl $((foo)*PAGE_SIZE), %eax ; \ > > movl %eax, %ecx ; \ > > addl %esi, %eax ; \ > > movl %eax, R(physfree) ; \ > > movl %esi, %edi ; \ > > xorl %eax,%eax ; \ > > cld ; \ > > rep ; \ > > stosb > > > >?? > > Improvement in what way? > Readability? I don't think so. > Performance? This macro is only used in the initial bootstrap of the > kernel. > ...changing it might save a few bytes, however. > > -DG > > David Greenman > Co-founder, The FreeBSD Project - http://www.freebsd.org > President, TeraSolutions, Inc. - http://www.terasolutions.com > Pave the road of life with opportunities. > > > 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 Thu Nov 23 12:34:53 2000 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 A060237B4C5 for ; Thu, 23 Nov 2000 12:34:51 -0800 (PST) Received: from newsguy.com (p35-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.100]) by peach.ocn.ne.jp (8.9.1a/OCN/) with ESMTP id FAA27887; Fri, 24 Nov 2000 05:34:37 +0900 (JST) Message-ID: <3A1D7EEF.6A6063F5@newsguy.com> Date: Fri, 24 Nov 2000 05:32:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR MIME-Version: 1.0 To: janb@cs.utep.edu Cc: David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG janb@cs.utep.edu wrote: > > It does not impair readability. As long as that is true, I believe its > prudent to save every byte possible... My two cents. It's an improvement in speed (unmeasurable, granted :) and size (a couple of bytes). It doesn't have any disadvantage. So, if someone is willing to commit it, there really shouldn't be any objection to it. As silly as the improvement it, contest it is even more silly. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@united.bsdconspiracy.net "All right, Lieutenant, let's see what you do know. Whatever it is, it's not enough, but at least you haven't done anything stupid yet." "I've hardly had time, sir." "There's a naive statement." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 12:35:35 2000 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 20A4C37B4C5; Thu, 23 Nov 2000 12:35:32 -0800 (PST) Received: (from alc@localhost) by cs.rice.edu (8.9.0/8.9.0) id OAA00297; Thu, 23 Nov 2000 14:35:30 -0600 (CST) Date: Thu, 23 Nov 2000 14:35:30 -0600 From: Alan Cox To: Mike Smith , Mikulas Patocka Cc: current@freebsd.org Subject: Re: page coloring Message-ID: <20001123143530.E21300@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 > Hi. > > Isn't the page coloring algoritm in _vm_page_list_find totally bogus? > No, it's not. The comment is, however, misplaced. It describes the behavior of an inline function in vm_page.h, and not the function it precedes. > It skips queue pq[index & PQ_L2_MASK]. > That's correct. The inline function vm_page_list_find() in vm_page.h has already failed to allocate a page of the desired color, index, and so _vm_page_list_find() is called to allocate a page of ANY other color it can find. Rather than choose a random page, the odd-looking loop in _vm_page_list_find() tries to find a page whose color is unlikely to equal the neighboring pages in the vm object if colored allocation for them succeeded. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 12:40:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-178-138.dsl.snfc21.pacbell.net [63.202.178.138]) by hub.freebsd.org (Postfix) with ESMTP id 7EAD137B4D7 for ; Thu, 23 Nov 2000 12:40:43 -0800 (PST) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.11.1) with ESMTP id eANKm9F01796; Thu, 23 Nov 2000 12:48:09 -0800 (PST) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200011232048.eANKm9F01796@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alan Cox Cc: Mikulas Patocka , current@freebsd.org Subject: Re: page coloring In-reply-to: Your message of "Thu, 23 Nov 2000 14:35:30 CST." <20001123143530.E21300@cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Nov 2000 12:48:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Isn't the page coloring algoritm in _vm_page_list_find totally bogus? > > > > No, it's not. The comment is, however, misplaced. It describes > the behavior of an inline function in vm_page.h, and not the function > it precedes. Hrm. My comment was based on John Dyson's own observations on its behaviour, and other discussions which concluded that the code wasn't flexible enough (hardcoded assumptions on cache organisation, size etc.) If this isn't applicable, my apologies for confusing the matter. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 13:48:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 1171437B4CF for ; Thu, 23 Nov 2000 13:48:34 -0800 (PST) Received: from adlmail.cup.hp.com (adlmail.cup.hp.com [15.0.100.30]) by palrel3.hp.com (Postfix) with ESMTP id 43EA771B; Thu, 23 Nov 2000 13:48:30 -0800 (PST) Received: from cup.hp.com (p1000180.nsr.hp.com [15.109.0.180]) by adlmail.cup.hp.com (8.9.3 (PHNE_18546)/8.9.3 SMKit7.02) with ESMTP id NAA16676; Thu, 23 Nov 2000 13:48:29 -0800 (PST) Message-ID: <3A1D90AD.FE0CC1CF@cup.hp.com> Date: Thu, 23 Nov 2000 13:48:29 -0800 From: Marcel Moolenaar Organization: Hewlett-Packard X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? References: <3A1D47C6.D35464F0@elischer.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > movl $((foo)*PAGE_SIZE), %eax ; \ ... > movl $((foo)*PAGE_SIZE),%ecx ; \ > might it be a very slight optimisation to change this to: > movl $((foo)*PAGE_SIZE), %eax ; \ > movl %eax, %ecx ; \ ... I don't know to much about the micro-architecture of the x86 family, but we know that the value of $((foo)*PAGE_SIZE) is cached. So the ld into %ecx might not take more time than a register copy and if it does, it can probably be performed in parallel. The register copy however must be performed before the "addl %esi, %eax", adding to the dependency graph of %eax and decreasing parallelism on the critical path. In short: I don't think micro-optimizations should be made without benchmark results :-) -- Marcel Moolenaar mail: marcel@cup.hp.com / marcel@FreeBSD.org tel: (408) 447-4222 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 15:16:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.interware.hu (mail.interware.hu [195.70.32.130]) by hub.freebsd.org (Postfix) with ESMTP id 62AC937B479 for ; Thu, 23 Nov 2000 15:16:49 -0800 (PST) Received: from kairo-29.budapest.interware.hu ([195.70.50.93] helo=elischer.org) by mail.interware.hu with esmtp (Exim 3.16 #1 (Debian)) id 13z5bf-00013E-00; Fri, 24 Nov 2000 00:16:44 +0100 Message-ID: <3A1DA552.14FF9F86@elischer.org> Date: Thu, 23 Nov 2000 15:16:34 -0800 From: Julian Elischer X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en, hu MIME-Version: 1.0 To: janb@cs.utep.edu Cc: David Greenman , current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? References: Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG that's all I was thinking.. I actually think it DOES improve readability.. because I spent time wondering why the same line was there twice :-) I was just reading the file and thought, 'hey why not'? then I thought probably it's doing something I don't understand.. but I think I was right the first time.. just an unimportant niggly thing.. > > Improvement in what way? > > Readability? I don't think so. > > Performance? This macro is only used in the initial bootstrap of the > > kernel. > > ...changing it might save a few bytes, however. > > > > -DG > > > > David Greenman > > Co-founder, The FreeBSD Project - http://www.freebsd.org > > President, TeraSolutions, Inc. - http://www.terasolutions.com > > Pave the road of life with opportunities. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > -- __--_|\ Julian Elischer / \ julian@elischer.org ( OZ ) World tour 2000 ---> X_.---._/ presently in: Budapest v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 16: 8:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 4B73137B4C5 for ; Thu, 23 Nov 2000 16:08:47 -0800 (PST) Received: (qmail 11716671 invoked from network); 24 Nov 2000 00:08:45 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 24 Nov 2000 00:08:45 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id eAO08gV30354; Fri, 24 Nov 2000 01:08:42 +0100 (CET) (envelope-from clefevre@cybercable.fr) Original-Sender: Cyrille Lefevre Original-Sender: Cyrille Lefevre To: Alexander Leidinger Cc: ashp@unloved.org, phk@FreeBSD.ORG, current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch References: <200011231207.eANC70202422@Magelan.Leidinger.net> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C In-Reply-To: Alexander Leidinger's message of "Thu, 23 Nov 2000 13:06:58 +0100 (CET)" From: Cyrille Lefevre Reply-To: Cyrille Lefevre Mail-Copies-To: never Date: 24 Nov 2000 01:08:37 +0100 Message-ID: <7l5umdtm.fsf@gits.dyndns.org> Lines: 18 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger writes: > On 22 Nov, Ashley Penney wrote: > > >> The attached patch is a "proof-of-concept" on which I would like > >> to get some comments: > > > > I'm only a moronic user, but this would make my life easier. My machine > > switches into 132x43 on startup, and I always lose the output. So this > > Its in the scrollback buffer. and how do you access the scroll-back buffer if you are not front to the console (read remote) ? Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Nov 23 21:39:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from guru.mired.org (okc-65-26-235-186.mmcable.com [65.26.235.186]) by hub.freebsd.org (Postfix) with SMTP id 81A3137B4CF for ; Thu, 23 Nov 2000 21:39:13 -0800 (PST) Received: (qmail 10987 invoked by uid 100); 24 Nov 2000 05:39:07 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14877.65275.744127.863828@guru.mired.org> Date: Thu, 23 Nov 2000 23:39:07 -0600 (CST) To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: <20001123110828.V18037@fw.wintelcom.net> References: <14876.48112.785320.465213@guru.mired.org> <20001123110828.V18037@fw.wintelcom.net> X-Mailer: VM 6.75 under 21.1 (patch 10) "Capitol Reef" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein types: > * Mike Meyer [001122 22:41] wrote: > > Could I get some feedback on > http://www.freebsd.org/cgi/query-pr.cgi?pr=22755 >? It's just a > > one-line kernel patch with some attendant updates in the kernel and > > libc, but it makes dealing with broken #! scripts *much* saner, and no > > one has even seen fit to comment on it yet :-(. Thank you for taking time to look at it. > This patch may break compliance, ENOEXEC is the proper error code, Um - compliance with what, exactly? I know it breaks compliance with Unix standards for user friendliness, but that was the point. I also agree that ENOEXEC is the best currently existing error code - but for this it pretty much sucks. Exec returns other codes providing more informative error messages; adding one more shouldn't be a problem. > the shell should try to be a bit smarter about explaining why > ENOEXEC was returned. Um - not "the" shell; all of them. Given that the authors of some of them are worried about portability, doing so portably is probably important as well. That's why I decided it belonged in the kernel. Doing this means that all shells get the benefit of it without a source change, and the only change other than better error messages was if there is an executable with the same name behind a broken script in the path - and I *couldn't* convince myself that was a problem! ; Fri, 24 Nov 2000 09:12:03 -0800 (PST) Received: from localhost (cc@localhost) by albert.gate5.de (8.11.1/8.11.1) with ESMTP id eAOIBiJ00423 for ; Fri, 24 Nov 2000 18:11:45 GMT (envelope-from cc@devcon.net) Date: Fri, 24 Nov 2000 18:11:43 +0000 (GMT) From: Christian Carstensen X-Sender: cc@albert.gate5.de To: current@FreeBSD.ORG Subject: -current on ibm tp a20p? 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, has someone of you got -current working on a ibm thinkpad a20p? at the moment, i can't use pccard and sound card support. to be honest, this problem is not -current specific, - it also occurs with 4.x os. the sound card is a Crystal Semiconductor CS 4624 controller with CS 4297A AC97 codec, pcic0 is a TI PCI-1450 PCI-CardBus Bridge. sound output results in "pcm0: play interrupt timeout, channel dead". when inserting a pccard, the card is not being recognized, pccardd tends to call it something like "Null, Null". Any hints or ideas? regards, christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 9:22:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (10dyn134.dh.casema.net [212.64.31.134]) by hub.freebsd.org (Postfix) with ESMTP id D84B937B4CF for ; Fri, 24 Nov 2000 09:22:36 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id eAOHcdN14635; Fri, 24 Nov 2000 18:38:40 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001124182039.00dca170@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Fri, 24 Nov 2000 18:21:51 +0100 To: Christian Carstensen , current@FreeBSD.ORG From: "Rogier R. Mulhuijzen" Subject: Re: -current on ibm tp a20p? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >when inserting a pccard, the card is not being recognized, pccardd tends >to call it something like "Null, Null". 1) is this a CardBus card maybe? 2) What does 'pccardc dumpcis' return? DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 9:50:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 2C2FA37B479; Fri, 24 Nov 2000 09:50:53 -0800 (PST) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #20) id 13zMzq-000807-00; Fri, 24 Nov 2000 18:50:50 +0100 Received: from a318d.pppool.de ([213.6.49.141] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #20) id 13zMzm-0004pJ-00; Fri, 24 Nov 2000 18:50:47 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.11.1/8.11.1) with ESMTP id eAOGdOE06364; Fri, 24 Nov 2000 17:39:25 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200011241639.eAOGdOE06364@Magelan.Leidinger.net> Date: Fri, 24 Nov 2000 17:39:23 +0100 (CET) From: Alexander Leidinger Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch To: clefevre@cybercable.fr Cc: ashp@unloved.org, current@FreeBSD.ORG, arch@FreeBSD.ORG In-Reply-To: <7l5umdtm.fsf@gits.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Nov, Cyrille Lefevre wrote: >> >> The attached patch is a "proof-of-concept" on which I would like >> >> to get some comments: >> > >> > I'm only a moronic user, but this would make my life easier. My machine >> > switches into 132x43 on startup, and I always lose the output. So this >> >> Its in the scrollback buffer. > > and how do you access the scroll-back buffer if you are not front to the > console (read remote) ? You can't. I didn't see the relationship between my answer to Ashley and your question, can you please give me a hint? Bye, Alexander. -- "One world, one web, one program" -- Microsoft promotional ad "Ein Volk, ein Reich, ein Fuehrer" -- Adolf Hitler http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 11: 3:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [194.84.67.11]) by hub.freebsd.org (Postfix) with ESMTP id 47FAC37B4C5; Fri, 24 Nov 2000 11:03:08 -0800 (PST) Received: (from osa@localhost) by ozz.freebsd.org.ru (8.11.1/8.11.1) id eAOJ34L01054; Fri, 24 Nov 2000 22:03:04 +0300 (MSK) (envelope-from osa) Date: Fri, 24 Nov 2000 22:03:04 +0300 From: Sergey Osokin To: freebsd-current@FreeBSD.org Cc: freebsd-stable@FreeBSD.org Subject: stranges in threads implementation... possible bug? Message-ID: <20001124220303.A1027@freebsd.org.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! My friend find some stranges in FreeBSD threads implementation... Here is a "special" code: ===================================== #include #include #include #include #include #include #define Debug(x) printf x extern "C" { typedef void *(*_THR_C_FUNC)(void *args); } typedef void *(*_THR_FUNC)(void *args); /*-----------------------------------------------------------------*/ class Mutex { public: Mutex() { assert(::pthread_mutex_init(&this->lock_, 0) == 0); } ~Mutex (void) { assert(::pthread_mutex_destroy(&this->lock_)==0); } int acquire (void) { return ::pthread_mutex_lock(&this->lock_); } int release (void) { return ::pthread_mutex_unlock (&this->lock_); } pthread_mutex_t lock_; }; /*-----------------------------------------------------------------*/ class Condition { public: Condition (Mutex &m); ~Condition (void); int wait (void); void signal (void); protected: pthread_cond_t cond_; Mutex &mutex_; }; Condition::Condition (Mutex &m) : mutex_ (m) { assert (pthread_cond_init(&this->cond_, 0) == 0); } Condition::~Condition (void) { while(::pthread_cond_destroy(&this->cond_) == -1 && errno == EBUSY) { assert(::pthread_cond_broadcast(&this->cond_) == 0); #ifdef __linux__ ::sched_yield (); #else ::pthread_yield(); #endif } } int Condition::wait (void) { return ::pthread_cond_wait(&this->cond_, &this->mutex_.lock_); } void Condition::signal (void) { assert(::pthread_cond_signal(&this->cond_) == 0); } /*-----------------------------------------------------------------*/ class Guard { public: Guard (Mutex &l); ~Guard (void); private: Mutex *lock_; }; Guard::Guard (Mutex &l) : lock_ (&l) { this->lock_->acquire (); } Guard::~Guard (void) { this->lock_->release (); } /*-----------------------------------------------------------------*/ class _Base_Thread_Adapter { public: _Base_Thread_Adapter (_THR_FUNC user_func, void *arg); void *invoke (void); _THR_C_FUNC entry_point (void) { return entry_point_; } private: _THR_FUNC user_func_; void *arg_; _THR_C_FUNC entry_point_; }; extern "C" void * _thread_adapter (void *args) { _Base_Thread_Adapter *thread_args = (_Base_Thread_Adapter*)args; void *status = thread_args->invoke (); return status; } _Base_Thread_Adapter::_Base_Thread_Adapter (_THR_FUNC user_func, void *arg) : user_func_ (user_func), arg_ (arg), entry_point_ (_thread_adapter) { } void * _Base_Thread_Adapter::invoke (void) { void *(*func)(void *) = this->user_func_; void *arg = this->arg_; delete this; return func(arg); } /*-----------------------------------------------------------------*/ class SS { public: void spawn(); static void run(); static void *WThread( void *data ); }; /*---------------------------------------------------------------------*/ static Mutex CMutex; static Condition Cond(CMutex); static Mutex m1; /*---------------------------------------------------------------------*/ #define REL(m,n) assert(m.release() != -1) #define ACQ(m,n) assert(m.acquire() != -1) /*---------------------------------------------------------------------*/ void * SS::WThread( void *data ) { Cond.signal(); Debug(("run thread...\n")); SS::run(); Debug(("thread ended\n")); return NULL; } /*---------------------------------------------------------------------*/ int thr_create (_THR_FUNC func, void *args) { _Base_Thread_Adapter *thread_args; thread_args = new _Base_Thread_Adapter(func, args); pthread_attr_t attr; if (::pthread_attr_init (&attr) != 0) return -1; ::pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_DETACHED); pthread_t thr_id; assert( ::pthread_create (&thr_id, &attr, thread_args->entry_point(), thread_args) == 0 ); ::pthread_attr_destroy (&attr); } /*---------------------------------------------------------------------*/ void SS::spawn() { #ifdef BAD int rc; Guard guard(m1); // !!! #else Guard guard(m1); // !!! int rc; #endif pthread_attr_t attr; if (::pthread_attr_init (&attr) != 0) return; ::pthread_attr_setdetachstate(&attr, PTHREAD_CREATE_DETACHED); thr_create(SS::WThread, (void *)0); ::pthread_attr_destroy (&attr); ACQ(CMutex, "CMutex"); rc = Cond.wait(); if( rc == -1 ) Debug(("Cond wait failed: %s\n", strerror(errno))); REL(CMutex, "CMutex"); } /*---------------------------------------------------------------------*/ void SS::run() { string s; // !!! string s1; // !!! sleep(1); } /*=====================================================================*/ static void sp_call(SS *ss) { string s; // !!! ss->spawn(); } /*------------------------------------------------------------------*/ int main(int argc, char **argv) { SS ss; sp_call(&ss); sleep(2); Debug(("Exitting...\n")); sleep(3); return 0; } ===================================== and here is is a makefile (use gmake for build): ===================================== Goal: bad good bad: tt.cpp $(CXX) -DBAD tt.cpp -pthread -g -o bad good: tt.cpp $(CXX) tt.cpp -pthread -g -o good ===================================== After build code, try run ./good and ./bad: ===================================== $ ./good run thread... thread ended Exitting... $ ./bad run thread... zsh: segmentation fault (core dumped) ./bad $ ===================================== Thats stranges work in FreeBSD 4.2-STABLE #0: Wed Nov 22 19:25:46 MSK 2000 and FreeBSD 5.0-CURRENT #0: Wed Nov 22 01:23:44 MSK 2000 Any idea? Make send-pr? Sergey Osokin, osa@freebsd.org.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 11: 5:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id A565037B4D7 for ; Fri, 24 Nov 2000 11:05:08 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id eAOJ4qe25159; Fri, 24 Nov 2000 11:04:52 -0800 (PST) (envelope-from dillon) Date: Fri, 24 Nov 2000 11:04:52 -0800 (PST) From: Matt Dillon Message-Id: <200011241904.eAOJ4qe25159@earth.backplane.com> To: "Daniel C. Sobral" Cc: janb@cs.utep.edu, David Greenman , Julian Elischer , current@FreeBSD.ORG Subject: Re: slight improvement in locore.s? References: <3A1D7EEF.6A6063F5@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My two cents: If it's assembly, and it works, and you didn't write it... then don't mess with it unless you absolutely have to. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 11:32:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from albert.gate5.de (gatekeeper.gate5.de [212.84.193.254]) by hub.freebsd.org (Postfix) with ESMTP id 5BE2A37B4C5 for ; Fri, 24 Nov 2000 11:32:51 -0800 (PST) Received: from localhost (cc@localhost) by albert.gate5.de (8.11.1/8.11.1) with ESMTP id eAOKWSB00262; Fri, 24 Nov 2000 20:32:28 GMT (envelope-from cc@devcon.net) Date: Fri, 24 Nov 2000 20:32:28 +0000 (GMT) From: Christian Carstensen X-Sender: cc@albert.gate5.de To: "Rogier R. Mulhuijzen" Cc: current@FreeBSD.ORG Subject: Re: -current on ibm tp a20p? In-Reply-To: <4.3.2.7.0.20001124182039.00dca170@mail.drwilco.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 Fri, 24 Nov 2000, Rogier R. Mulhuijzen wrote: > 1) is this a CardBus card maybe? It happens with a) Lucent WaveLAN (silver) b) 3com 3c589d > 2) What does 'pccardc dumpcis' return? Code 85 not found Code 85 not found code Unknown ignored Code 134 not found Code 134 not found code Unknown ignored Code 13 not found Code 13 not found code Unknown ignored Code 195 not found Code 195 not found code Unknown ignored Code 100 not found Code 100 not found code Unknown ignored Code 115 not found Code 115 not found code Unknown ignored Code 93 not found Code 93 not found code Unknown ignored Code 96 not found Code 96 not found code Unknown ignored Code 192 not found Code 192 not found code Unknown ignored Configuration data for card in slot 0 Tuple #1, code = 0x0 (Null tuple), length = 12 000: 40 cb a3 00 00 00 00 00 00 20 40 60 Tuple #2, code = 0x0 (Null tuple), length = 139 000: 55 44 16 00 01 f3 00 30 70 50 49 2e c0 8b 2e c0 010: 50 49 86 29 00 18 00 00 0c 01 00 00 2e c0 8b 8b 020: 24 6e 01 00 00 00 00 b4 c6 02 00 00 00 41 00 00 030: 0d 43 70 72 67 74 28 29 31 39 2c 39 38 31 39 20 040: 49 74 6c 43 72 6f 61 69 6e 0a 49 74 6c 43 72 6f 050: 61 69 6e 49 74 6c 55 44 2c 50 45 32 30 28 75 6c 060: 20 37 29 18 18 ff 00 80 54 41 00 f2 00 b4 cd 0a 070: 74 32 c3 01 16 02 c0 c0 02 e4 c0 55 ec 60 46 b4 080: bb 00 01 cd 66 90 c2 00 20 e2 c3 Tuple #3, code = 0x0 (Null tuple), length = 220 000: 6a e8 ff 55 ec 53 c5 04 07 00 09 e4 e8 ff eb 1f 010: 58 c2 00 8b 50 46 24 04 3c 76 04 50 a2 58 c2 00 020: 8b 50 46 c0 04 e8 ff c0 50 d1 58 c2 00 8b 50 46 030: 86 50 d9 86 50 d3 58 c2 00 8b 66 66 46 66 c0 50 040: d7 66 c0 50 cf 66 5d 04 55 ec 50 8b 04 c1 10 e8 050: ff 3a 36 66 c0 50 ab 66 5d 04 55 ec 53 1e 46 8e 060: 06 8b 08 4e 67 03 43 f9 59 5b e4 c2 00 66 06 30 070: 2b 8b 4e 02 75 16 66 f6 f5 6c 66 c0 c0 c1 04 03 080: 89 02 c1 10 46 88 07 46 2f c6 05 8d 10 56 66 ca 090: 88 04 76 66 ca c7 00 ff 46 93 6c 89 02 c1 10 5e 0a0: 88 07 c1 10 46 ff c6 05 b4 f8 15 5d c4 55 07 5e 0b0: 32 80 00 01 c3 80 28 f0 00 1e 4d 1e 46 f0 07 59 0c0: 38 59 00 60 08 2e 1e 00 e1 cd 72 80 00 1a e1 80 0d0: 80 0b 2e 1e 00 e1 cd 72 80 00 00 61 Tuple #4, code = 0x0 (Null tuple), length = 96 000: 8b e6 bf 00 0a cd 66 f9 74 f6 01 1c 2a 18 b8 b1 010: 1a 83 01 30 b8 b1 1a 06 02 10 83 01 30 b8 b1 1a 020: 06 02 61 c3 60 3e 02 77 80 bd 00 18 33 0e 02 33 030: 2e 1e 00 30 b8 b1 1a 1d 0e 02 8b e6 bf 00 0a cd 040: 66 e1 bf 00 0d cd 66 90 52 4c f5 88 02 00 03 49 050: 74 6c 42 6f 20 67 6e 20 65 73 6f 20 2e 20 42 69 Tuple #5, code = 0x0 (Null tuple), length = 48 000: 36 00 00 00 00 00 00 01 e8 ff 83 bd 00 04 c0 04 010: 01 cb 60 06 40 26 13 0e 83 20 e0 66 33 66 00 00 020: 2e 0e 03 03 8a 66 c1 03 00 d1 66 e9 66 83 40 00 Tuple #6, code = 0x0 (Null tuple), length = 14 000: 26 e8 fd 3c 0d 50 45 45 30 20 6f 6c 20 6f Tuple #7, code = 0x20 (Manufacturer ID), length = 105 000: 64 65 6f 67 20 72 65 62 73 20 65 6f 79 00 c0 ff 010: 80 00 8d 81 00 75 e2 8c c1 06 8c 8b 6a 07 8b 13 020: 83 20 e1 8e 2e 26 03 50 53 2e 3e 02 75 66 8b a5 030: 66 0f 1e 02 2e b7 ab 66 d9 17 2e 16 02 2e b7 b5 040: 66 0f 0e 02 03 66 d3 83 10 c1 04 c1 04 33 5b 66 050: e3 66 e3 33 2e 0e 03 03 8e 83 02 e9 1b 73 eb e8 060: fe 50 e0 0e 0f 50 ff 92 cb PCMCIA ID = 0x6564, OEM ID = 0x676f Tuple #8, code = 0x0 (Null tuple), length = 229 000: 5b 8e 8b fb 8b 8a 2e 0e 03 c1 03 e9 d1 c1 0a 03 010: 90 81 00 8e 33 33 fc aa 1d 0a 45 69 69 67 74 65 020: 52 4c 4c 61 65 0d 0a e8 fd 68 05 d4 b4 b9 00 c0 030: cd 07 66 90 e8 fd e8 fe f8 75 c3 a9 0e c6 e8 fb 040: 68 00 a6 53 66 57 1e 0f 0f 66 83 b1 00 0b f7 a3 050: 40 0f c6 ba c0 da 3e 00 aa 69 c2 00 fa f0 ec 68 060: 05 68 66 83 b1 00 85 00 12 0d 50 45 45 31 20 61 070: 65 63 64 20 4f 20 44 73 72 63 75 65 77 73 6e 74 080: 66 75 64 00 c3 07 e3 f8 eb 08 eb 03 72 eb 8a 02 090: 80 00 8e e3 53 6a 1e 00 a8 3c 74 e9 ff 3e 00 ff 0a0: 74 3b 73 66 3d 42 24 b8 b6 04 f8 72 50 00 1e 00 0b0: 78 3c 74 eb 8c 8e 66 83 b1 00 17 f7 a3 40 0f 92 0c0: 66 81 24 43 0f 86 0e 20 2e 36 00 ff ee 2e 36 00 0d0: ff e8 2e 36 00 00 c4 50 68 06 26 75 cb c4 5a c4 0e0: 83 00 1f 68 06 Tuple #9, code = 0x0 (Null tuple), length = 82 000: af eb 0d 42 5f 6f 64 72 29 3d 20 bb 00 db 48 8a 010: 6c 38 74 8a e2 0f 0f 07 5e 66 59 c3 0a 4e 49 49 020: 4c 29 66 0f 16 00 2e b7 2e 66 d0 2e b7 30 66 d0 030: 2e b7 b9 66 d0 2e b7 bb 66 d0 81 ff 00 66 ea b8 040: 00 c0 8b 13 2b 26 36 00 66 53 50 a1 00 e0 8e 66 050: e2 66 Tuple #10, code = 0x0 (Null tuple), length = 219 000: 89 66 74 83 04 f4 db c3 10 db db e8 58 66 1f d0 010: c1 10 c4 c1 10 8b 2c fa 40 8e 36 26 00 e4 8e 8b 020: fb c1 10 50 53 57 55 00 00 6a 66 00 56 ec 40 8e 030: 26 16 00 e2 83 18 fc a1 00 89 02 a1 00 89 04 a1 040: 00 89 06 a1 00 89 08 a1 00 89 0a 2e b7 2c 66 c0 050: 66 e8 03 89 0c 2e b7 b9 66 c0 66 e8 03 89 0e 2e 060: b7 bb 66 c0 66 e8 03 36 55 66 0f 06 00 83 0f c1 070: 04 d0 89 0e 57 e8 05 c4 66 8b 10 89 08 36 55 66 080: 56 5a c4 83 00 84 01 c4 83 20 1d f0 81 c6 74 b8 090: 09 fa 00 0b 5e 81 c9 0f 67 0e e8 f8 5f 0d 50 45 0a0: 45 30 20 49 53 65 74 6e 65 20 65 6f 79 63 70 20 0b0: 72 6f 2e 0d 50 45 45 36 20 4e 49 64 69 65 20 6d 0c0: 67 20 73 69 76 6c 64 00 0a 58 2d 43 3a 21 58 20 0d0: 74 75 74 72 20 61 20 6f 20 6f 6e 2 slots found To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 11:48:19 2000 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 873BF37B4C5 for ; Fri, 24 Nov 2000 11:48:16 -0800 (PST) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA64331; Fri, 24 Nov 2000 14:48:14 -0500 (EST) (envelope-from wollman) Date: Fri, 24 Nov 2000 14:48:14 -0500 (EST) From: Garrett Wollman Message-Id: <200011241948.OAA64331@khavrinen.lcs.mit.edu> To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: Confusing error messages from shell image activation In-Reply-To: <14877.65275.744127.863828@guru.mired.org> References: <14876.48112.785320.465213@guru.mired.org> <20001123110828.V18037@fw.wintelcom.net> <14877.65275.744127.863828@guru.mired.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Um - compliance with what, exactly? IEEE Std.1003.1-1990 et seq. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 12:35:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 5F35C37B4E5 for ; Fri, 24 Nov 2000 12:35:04 -0800 (PST) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by pike.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id eAOKYdC56218; Fri, 24 Nov 2000 12:34:44 -0800 (PST) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001123114438.C19987@wiliam.alcove-int> Date: Fri, 24 Nov 2000 12:34:53 -0800 (PST) From: John Baldwin To: Nicolas Souchu Subject: RE: Mutex, SMBUS, ACPI (Re: how to mutex'ify a device driver) Cc: freebsd-current@FreeBSD.org, Archie Cobbs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Nov-00 Nicolas Souchu wrote: > On Wed, Nov 22, 2000 at 04:58:32PM -0800, Archie Cobbs wrote: >> As a relatively simple exercise in -current kernel programming, >> I'm planning to mutex'ify the ichsmb(4) device driver (this is >> a relatively simple driver that currently uses splhigh()). I'd >> appreciate some feedback if what I'm doing is the right thing. > > What are kernel mutex? A new mechanism for spl replacement? Is it > introduced with the new SMP? I found nothing in the mail archives... Yes, they are used to replace spl()'s. You can read the mutex(9) manpage in -current for details about how the mutexes work. Hopefully before too long I will be adding some stuff to the developer's handbook to explain how to use the mutexes in the kernel. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 12:40:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from albert.gate5.de (gatekeeper.gate5.de [212.84.193.254]) by hub.freebsd.org (Postfix) with ESMTP id 5880137B4C5 for ; Fri, 24 Nov 2000 12:40:25 -0800 (PST) Received: from localhost (cc@localhost) by albert.gate5.de (8.11.1/8.11.1) with ESMTP id eAOLdqE00357; Fri, 24 Nov 2000 21:39:52 GMT (envelope-from cc@devcon.net) Date: Fri, 24 Nov 2000 21:39:52 +0000 (GMT) From: Christian Carstensen X-Sender: cc@albert.gate5.de To: "Rogier R. Mulhuijzen" Cc: current@freebsd.org Subject: Re: -current on ibm tp a20p? In-Reply-To: <4.3.2.7.0.20001124210856.00e4a620@mail.drwilco.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 Fri, 24 Nov 2000, Rogier R. Mulhuijzen wrote: > >It happens with > > > > a) Lucent WaveLAN (silver) > > b) 3com 3c589d > > Are they PCMCIA or CardBus? they are both PCMCIA, not CardBus. regards, Christian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 15:44:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B75137B479; Fri, 24 Nov 2000 15:44:18 -0800 (PST) Received: from localhost (1g6qok@localhost [127.0.0.1]) by green.dyndns.org (8.11.0/8.11.0) with ESMTP id eAONiG560473; Fri, 24 Nov 2000 18:44:17 -0500 (EST) (envelope-from green@FreeBSD.org) Message-Id: <200011242344.eAONiG560473@green.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: audit@FreeBSD.org Cc: current@FreeBSD.org Subject: OpenSSH 2.3.0 pre-upgrade From: "Brian F. Feldman" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 24 Nov 2000 18:44:16 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Please direct followups to audit@FreeBSD.org and remove all extraneous addresses. I'm cross-posting in hopes of reaching the right audiences that won't necessarily overlap.) It's time again for an upgrade to our FreeBSD OpenSSH. Version 2.3.0 was released a few weeks back, and working off that I've produced a set of diffs from either what's in the tree now or the original OpenBSD, 2.3.0 sources. What's new in this release? Mostly the adding of the AES (Rijndael) to the SSH2 algorithms. Is anything now broken? Well, nothing new broken that I know of; there was an issue of the canonical host name not being used, which I could have sworn it was before: in either case, it is used now. The auth loops previously did not take NULL struct passwd * arguments, but now they do (to inform them to fake authorization). This deprecated our fake auth loop, but gave me a lot of work to correct the logic in the code that expects non-NULL pw's. I think I did it all, but wouldn't be surprised if there's still a mistake, so I'd really appreciate others looking at it. There's some weird issue where for the Diffie-Hellman exchange, OpenSSH wants primes but doesn't seem to want to generate them... it expects an /etc/ssh/primes (which should become /var/run/ssh_primes, if anything) and I have no clue where the program is that supposedly generates them. So, for SSH2, the authentication stage generates a large warning and uses a hardcoded prime. This should not actually have an affect on security, though, according to my understanding of the Diffie-Hellman protocol. I probably fixed a ton of smaller bugs on the way I've all but forgotten about now. I'd appreciate anyone who can either test this out to see if it works for them (I upgraded all my OpenSSH stuff to 2.3.0, and it is working great) or review the changes. If I've made some mistakes in the code I've changed, it could easily be a huge security issue, so it would be really nice to have others back me up on the changes made. The patch to apply on a -CURRENT/-STABLE FreeBSD system's src tree to update to this version can be found at: http://green.bikeshed.org/OpenSSH-2.3.0.patch.gz Similarly, the diffs from plain OpenBSD OpenSSH 2.3.0 to ours are at: http://green.bikeshed.org/OpenSSH_to_FreeBSD-2.3.0.patch.gz Thanks! -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@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 Nov 24 17:53:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rcpt-expgw.biglobe.ne.jp (rcpt-expgw.biglobe.ne.jp [210.147.6.216]) by hub.freebsd.org (Postfix) with ESMTP id D828F37B479 for ; Fri, 24 Nov 2000 17:53:28 -0800 (PST) Received: from smtp-gw.biglobe.ne.jp by rcpt-expgw.biglobe.ne.jp (8.9.3+3.2W/3.7W-00110911) with ESMTP id KAA21432 for ; Sat, 25 Nov 2000 10:53:22 +0900 (JST) X-Biglobe-Sender: Received: from localhost (211.13.107.87 [211.13.107.87]) by smtp-gw.biglobe.ne.jp id KAJQ85CD0C62; Sat, 25 Nov 2000 10:53:21 +0900 (JST) To: current@freebsd.org Subject: Re: -current on ibm tp a20p? In-Reply-To: References: <4.3.2.7.0.20001124210856.00e4a620@mail.drwilco.net> X-Mailer: Mew version 1.94.2 on XEmacs 21.1 (Channel Islands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20001125105240B.yatt@msc.biglobe.ne.jp> Date: Sat, 25 Nov 2000 10:52:40 +0900 From: Yoichi ASAI X-Dispatcher: imput version 20000228(IM140) Lines: 33 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Carstensen wrote: > has someone of you got -current working on a ibm thinkpad a20p? > at the moment, i can't use pccard and sound card support. > to be honest, this problem is not -current specific, - it also occurs > with 4.x os. I have ThinkPad A20m, perhaps that is a subset of A20p. On these laptops, use 0xd4000 as memory slots. -- kernel config hint file -- hint.pcic.0.maddr="0xd4000" -- /etc/pccard.conf -- memory 0xd4000 96k Pccard works fine with these settings. On the other hand, sound chip does not work. Kernel recognizes Crystal SoundFusion as CS461x, with device pcm and csa included in my config. But IRQ sharing prevents it from working. mpg123 and play (sox) return this message: pcm0: play interrupt timeout, channel dead -- dmesg -- csa0: mem 0xf4000000-0xf40fffff,0xf4121000-0xf4 121fff irq 11 at device 5.0 on pci0 pcm0: on csa0 --- Yoichi ASAI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 18:35:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id CA18937B479 for ; Fri, 24 Nov 2000 18:35:17 -0800 (PST) Received: from zippy.pacbell.net ([207.214.149.167]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0G4K00M5B73WA5@mta6.snfc21.pbi.net> for current@freebsd.org; Fri, 24 Nov 2000 18:33:33 -0800 (PST) Received: by zippy.pacbell.net (Postfix, from userid 1000) id 9C54717F9; Fri, 24 Nov 2000 18:33:54 -0800 (PST) Date: Fri, 24 Nov 2000 18:33:54 -0800 From: Alex Zepeda Subject: Re: -current scheduler strangeness In-reply-to: <20001120154327.C16019@petra.hos.u-szeged.hu>; from sziszi@petra.hos.u-szeged.hu on Mon, Nov 20, 2000 at 03:43:27PM +0100 To: current@freebsd.org Message-id: <20001124183354.B6896@zippy.pacbell.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> <20001120152154.A644@thing.orbitel.bg> <3A1928AC.E627E639@elischer.org> <20001120154327.C16019@petra.hos.u-szeged.hu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 20, 2000 at 03:43:27PM +0100, Szilveszter Adam wrote: > The messages did not start with SMPNG but got a *lot* more frequent in the > last couple of weeks, making listening to mp3-s a real annoyance during any > more serious system activity. (Earlier, ie in the early fall and in the > summer) these messages were almost never seen while in console mode, but > only with X and RealPlayer messing things up. I'm getting this too, in fact even pcmplay (about as minimalistic as you can get) skips a lot and often throws hwptr went backwards. Oh yeah, I'm using an AWE64 PnP as well. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Nov 24 20: 5:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from hera.drwilco.net (22dyn15.dh.casema.net [212.64.69.15]) by hub.freebsd.org (Postfix) with ESMTP id 50A3737B479 for ; Fri, 24 Nov 2000 20:05:51 -0800 (PST) Received: from ceres.drwilco.nl (ceres.drwilco.net [10.1.1.19]) by hera.drwilco.net (8.11.1/8.11.1) with ESMTP id eAP4MAN18411; Sat, 25 Nov 2000 05:22:11 +0100 (CET) (envelope-from drwilco@drwilco.nl) Message-Id: <4.3.2.7.0.20001125045912.00ca03f0@mail.drwilco.net> X-Sender: drwilco@mail.drwilco.net X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Sat, 25 Nov 2000 05:05:22 +0100 To: Alex Zepeda , freebsd-current@freebsd.org From: "Rogier R. Mulhuijzen" Subject: Re: -current scheduler strangeness In-Reply-To: <20001124183354.B6896@zippy.pacbell.net> References: <20001120154327.C16019@petra.hos.u-szeged.hu> <20001120142326.A97732@thing.orbitel.bg> <20001120142543.B97732@thing.orbitel.bg> <3A191B13.60A7C199@FreeBSD.org> <20001120152154.A644@thing.orbitel.bg> <3A1928AC.E627E639@elischer.org> <20001120154327.C16019@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Stuff about sound skippage & mouse jerkiness snipped) >I'm getting this too, in fact even pcmplay (about as minimalistic as you >can get) skips a lot and often throws hwptr went backwards. Oh yeah, I'm >using an AWE64 PnP as well. Making the sound buffer 32K instead of 4K (like a related thread on this list suggested) helped me with the sound, listening to MP3's while I work is now bearable, and I don't get the "hwptr moved backwards" crap, but the jerkiness is still there. It's been said it's caused by IRQ latency and that the SMPNG guys are working on it, so I guess it's a question of keeping current till this is solved. DocWilco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 0:19:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.san.rr.com (smtp2.san.rr.com [24.25.195.39]) by hub.freebsd.org (Postfix) with ESMTP id 70CA337B4C5 for ; Sat, 25 Nov 2000 00:19:28 -0800 (PST) Received: from san.rr.com ([24.25.222.134]) by smtp2.san.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sat, 25 Nov 2000 00:16:40 -0800 Message-ID: <3A1F75E3.2E17FC43@san.rr.com> Date: Sat, 25 Nov 2000 00:18:43 -0800 From: Derek Schene' X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: current@freebsd.org Subject: libc.so.4 not found Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On a fresh hard drive I installed 5.0 20001123 Current and got the following after installation: Local package initialization:/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found I tried again from scratch with 5.0 20001124 Current and have the same problem. This affects emacs, apache, and unfortunately cvsup I have played with some symbolic links with no luck. This came from reading- http://www.freebsd.org/handbook/linuxemu-lbc-install.html#LINUXEMU-LIBS-PORT but I don't think this has anything to do with Linux Binary Compatibility. This was the closes I came when searching on ld-elf.so.1 and libc.so.4 Note the only change between my 11/23 and 11/24 install was I added Netscape Communicator 4.74 and got- xfree86-aoutlibs-3.3.3 installation aborted error code 1 Any ideas on the libc? Derek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 0:44:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id A2EDC37B4CF for ; Sat, 25 Nov 2000 00:44:13 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id 285BF2B210; Sat, 25 Nov 2000 02:44:08 -0600 (CST) Date: Sat, 25 Nov 2000 02:44:08 -0600 From: Bill Fumerola To: Derek Schene' Cc: current@freebsd.org Subject: Re: libc.so.4 not found Message-ID: <20001125024407.O14080@elvis.mu.org> References: <3A1F75E3.2E17FC43@san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A1F75E3.2E17FC43@san.rr.com>; from ferret@san.rr.com on Sat, Nov 25, 2000 at 12:18:43AM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote: > On a fresh hard drive I installed 5.0 20001123 Current and got the > following after installation: > > Local package initialization:/usr/libexec/ld-elf.so.1: Shared object > "libc.so.4" not found we bumped the libc version to 5, but we didn't make compat4 libaries available for installation yet. I'll renew my annoyance with the fact that we just bumped this without even figuring out why things broke or if we could change them in a way to save functionality without having to bump the version number[1]. We also never propogated this bump to RELENG_4, so the release shipped with the worst of both worlds. To answer your question, though: I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible should happen. This should work until we get our act together regarding this change. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org 1. to my knowledge. I tried to keep up on this thread but its possible someone figure it out and we just didn't revert the libc bump. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 3: 8:43 2000 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 5CCE837B4C5 for ; Sat, 25 Nov 2000 03:08:37 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id DAA52636; Sat, 25 Nov 2000 03:08:36 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAPB8Y754098; Sat, 25 Nov 2000 03:08:34 -0800 (PST) (envelope-from obrien) Date: Sat, 25 Nov 2000 03:08:34 -0800 From: "David O'Brien" To: Bill Fumerola Cc: "Derek Schene'" , current@freebsd.org Subject: Re: libc.so.4 not found Message-ID: <20001125030833.A54062@dragon.nuxi.com> Reply-To: current@freebsd.org References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001125024407.O14080@elvis.mu.org>; from billf@mu.org on Sat, Nov 25, 2000 at 02:44:08AM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 02:44:08AM -0600, Bill Fumerola wrote: > On Sat, Nov 25, 2000 at 12:18:43AM -0800, Derek Schene' wrote: > > On a fresh hard drive I installed 5.0 20001123 Current and got the > > following after installation: > > > > Local package initialization:/usr/libexec/ld-elf.so.1: Shared object > > "libc.so.4" not found > > we bumped the libc version to 5, but we didn't make compat4 libaries > available for installation yet. In this case it doesn't matter -- "a fresh hard drive" and "local package" implies that the -current packages on ftp.freebsd.org haven't been built since the bump and are thus slightly out dated. > I'll renew my annoyance with the fact that we just bumped this without > even figuring out why things broke or if we could change them in a way > to save functionality without having to bump the version number[1]. It doesn't matter as at least Garrett has some changes he's going to make that aren't compatible. libc.so will be at least at version "5" in FreeBSD 5.0, so we'll have to go thru this pain eventually anyway. > We also never propagated this bump to RELENG_4, so the release shipped > with the worst of both worlds. Huh? Why the worst of both worlds?? > To answer your question, though: > > I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible > should happen. This should work until we get our act together regarding > this change. I'm not quite sure what isn't together other than no compat4x libc.so.4 yet -- I can certainly create one, but I'll have to update it for the libc.so.4 in 4.3 and 4.4. Don't forget the compat libs are uuencoded files, so CVS will see large diffs. If people don't mind, I'll certainly make the compat libs now. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 6:30:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id 80E9C37B4D7 for ; Sat, 25 Nov 2000 06:28:53 -0800 (PST) Received: (qmail 12571759 invoked from network); 25 Nov 2000 14:28:47 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 25 Nov 2000 14:28:47 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id eAPEScY48936; Sat, 25 Nov 2000 15:28:38 +0100 (CET) (envelope-from clefevre@cybercable.fr) Original-Sender: Cyrille Lefevre Original-Sender: Cyrille Lefevre To: Steve Kargl Cc: Eivind Eklund , current@FreeBSD.ORG Subject: Re: INVARIANTS and -current References: <200010311738.e9VHcdA51034@troutmask.apl.washington.edu> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C In-Reply-To: Steve Kargl's message of "Tue, 31 Oct 2000 09:38:39 -0800 (PST)" From: Cyrille Lefevre Reply-To: Cyrille Lefevre Mail-Copies-To: never Date: 25 Nov 2000 15:28:31 +0100 Message-ID: <3dggktww.fsf@gits.dyndns.org> Lines: 31 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steve Kargl writes: > Eivind Eklund wrote: > > (Based on suggestion from Robert Watson.) > > > > I want to enable INVARIANTS by default in -current. This result in some > > slowdown, but it also makes it more likely that we'll find bugs quickly. > > People that want to run -current should know enough to disable it if it is > > in the way, anyway. > > I support your proposal. But, have a question: Has > anyone actually measured the performance impact of > INVARIANTS? I'm tempted to suggest that INVARIANTS > should be the default in not only -current in 5.0 > when she's released. Anyone interested in performance > in 5.0 will build custom kernels, and so he can turn > INVARIANTS off. sorry for the late answer. well, I'm not at all w/ you to enable INVARIANTS in -stable. the reason is simple. I had INVARIANTS for months (years?), but in september, I got plenty of "TRAP FAULT 12 and calcru: monotonisation" because of this. after disabling INVARIANTS, no problems anymore. I've posted a message about that in -stable w/ no answer, as I remember me. so, before to enable INVARIANTS in -stable or anywhere, the code should be much better checked, at least around kern_resource.c. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 7:41:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id AD10937B4C5; Sat, 25 Nov 2000 07:41:09 -0800 (PST) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id HAA02819; Sat, 25 Nov 2000 07:41:03 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda02817; Sat Nov 25 07:40:56 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.11.1/8.9.1) id eAPFepI56547; Sat, 25 Nov 2000 07:40:51 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdx56544; Sat Nov 25 07:40:05 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.11.1/8.9.1) id eAPFe4N00849; Sat, 25 Nov 2000 07:40:04 -0800 (PST) Message-Id: <200011251540.eAPFe4N00849@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdPDY837; Sat Nov 25 07:39:33 2000 X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 4.2-RELEASE X-Sender: cy To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-reply-to: Your message of "Wed, 22 Nov 2000 21:40:41 +0100." <1050.974925641@critter> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 25 Nov 2000 07:39:33 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <1050.974925641@critter>, Poul-Henning Kamp writes: > > The attached patch is a "proof-of-concept" on which I would like > to get some comments: > > It bugs me big time that the output from /etc/rc and all other output > to /dev/console is volatile and lost once it scrolls of your console. It's a no-brainer. Let's do it. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Team Leader, Sun/DEC Team Internet: Cy.Schubert@osg.gov.bc.ca Open Systems Group, ITSD, ISTA Province of BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 8:36:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id EFA0637B4C5; Sat, 25 Nov 2000 08:36:51 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAPGagO10434; Sat, 25 Nov 2000 09:36:42 -0700 (MST) Date: Sat, 25 Nov 2000 09:36:39 -0700 (MST) From: X-Sender: janb@gecko To: freebsd-current@FreeBSD.ORG Cc: freebsd-stable@FreeBSD.ORG Subject: kde2 upgrade fails in wierd fashion 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 This is strange. I deinstalled all kde11 type ports and then made installed the kde2 port. However, each time I got and startx, I stay with kde 1.1.2. I am using Xfree86 4.01 and a reasonably recent version of CURRENT. Has anybody got an explanation for this behavior? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 8:54:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 1308537B4CF for ; Sat, 25 Nov 2000 08:54:06 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eAPGs1t22391 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Sat, 25 Nov 2000 17:54:03 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eAPGs3M48816 for ; Sat, 25 Nov 2000 17:54:03 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eAPGrx340662 for freebsd-current@freebsd.org; Sat, 25 Nov 2000 17:53:59 +0100 (CET) (envelope-from ticso) Date: Sat, 25 Nov 2000 17:53:58 +0100 From: Bernd Walter To: freebsd-current@freebsd.org Subject: Missing ithreads Message-ID: <20001125175357.A40643@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm missing the ithread processes for irq10 and irq15. As you can see in the dmesg output there are de devices that are using the irqs in question. I asume that they are only missing in the list as the devices are working fine. PID TT STAT TIME COMMAND 0 ?? DLs 0:00.16 (swapper) 1 ?? ILs 0:00.06 /sbin/init -- 2 ?? DL 0:06.24 (pagedaemon) 3 ?? DL 0:00.00 (vmdaemon) 4 ?? DL 0:00.20 (bufdaemon) 5 ?? DL 0:07.21 (syncer) 10 ?? RL 702:28.90 (idle) 11 ?? WL 2:44.60 (swi1: net) 12 ?? WL 32:02.76 (swi6: clock) 13 ?? WL 0:00.00 (swi4: vm) 14 ?? DL 0:00.87 (random) 15 ?? WL 0:00.00 (swi5: task queue) 16 ?? WL 0:01.49 (irq14: ata0) 17 ?? WL 0:39.49 (irq12: de0) 18 ?? WL 0:06.24 (irq11: de4) 19 ?? WL 0:00.01 (irq1: atkbd0) 20 ?? RL 9:05.12 (irq5: isic0) 21 ?? WL 0:00.00 (irq7: ppc0) 22 ?? WL 0:00.00 (swi0: tty:sio) 155 ?? Ss 2:14.50 ppp -auto gtn 225 ?? Ss 1:02.22 natd -f /etc/natd.conf 384 ?? Is 0:04.79 syslogd -s 393 ?? S real memory = 16777216 (16384K bytes) avail memory = 12795904 (12496K bytes) Preloaded elf kernel "kernel.ko" at 0xc03b6000. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe800-0xe80f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pcib1: at device 10.0 on pci0 pci1: on pcib1 de0: port 0xd800-0xd87f mem 0xfbdff000-0xfbdff07f irq 12 at device 4.0 on pci1 de0: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:92:a7:13:40 de1: port 0xd400-0xd47f mem 0xfbdfe000-0xfbdfe07f irq 15 at device 5.0 on pci1 de1: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de1: address 00:00:92:a7:13:41 de2: port 0xd000-0xd07f mem 0xfbdfd000-0xfbdfd07f irq 10 at device 6.0 on pci1 de2: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de2: address 00:00:92:a7:13:42 de3: port 0xc800-0xc87f mem 0xfbdfc000-0xfbdfc07f irq 11 at device 7.0 on pci1 de3: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de3: address 00:00:92:a7:13:43 pcib2: at device 11.0 on pci0 pci2: on pcib2 de4: port 0xb800-0xb87f mem 0xfbcff000-0xfbcff07f irq 11 at device 4.0 on pci2 de4: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de4: address 00:00:92:a7:12:88 de5: port 0xb400-0xb47f mem 0xfbcfe000-0xfbcfe07f irq 12 at device 5.0 on pci2 de5: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de5: address 00:00:92:a7:12:89 de6: port 0xb000-0xb07f mem 0xfbcfd000-0xfbcfd07f irq 15 at device 6.0 on pci2 de6: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de6: address 00:00:92:a7:12:8a de7: port 0xa800-0xa87f mem 0xfbcfc000-0xfbcfc07f irq 10 at device 7.0 on pci2 de7: Cogent EM440TX 21140A [10-100Mb/s] pass 2.0 de7: address 00:00:92:a7:12:8b atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 isic0 at port 0x1b40-0x1b5f,0x1720-0x173f,0x720-0x73f,0xf20-0xf3f,0x1340-0x135f,0x340-0x35f,0xb40-0xb5f irq 5 flags 0x4 on isa0 isic0: passive stack unit 0 isic0: AVM A1 or Fritz!Card Classic ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources DUMMYNET initialized (000608) i4b: ISDN call control device attached i4brbch: 4 raw B channel access device(s) attached IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4bctl: ISDN system control port attached IPv6 packet filtering initialized, default to accept, unlimited logging i4btrc: 4 ISDN trace device(s) attached i4bing: 4 i4b NetGraph ISDN B-channel device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4bisppp: 16 ISDN SyncPPP device(s) attached (VJ header compression) IPsec: Initialized Security Association Processing. ad0: 1536MB [3121/16/63] at ata0-master WDMA2 Mounting root from ufs:/dev/ad0a [...] -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 10:12:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id 53DCF37B479 for ; Sat, 25 Nov 2000 10:12:37 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAPICbk86673; Sat, 25 Nov 2000 12:12:37 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: freebsd-current@freebsd.org Subject: -current dies in kerberosIV Keywords: usr,kerberosiv,src,kipd,libexec,crypto,include,obj From: Michael Harnois Date: 25 Nov 2000 12:12:37 -0600 Message-ID: <86hf4vhqei.fsf@mharnois.workgroup.net> Lines: 21 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Pan) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -O -pipe -march=i686 -I/usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/include -I/usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/roken -I/usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/krb -I/usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip -I/usr/src/kerberosIV/libexec/kipd/../../include -Wall -DHAVE_CONFIG_H -I/usr/obj/usr/src/kerberosIV/libexec/kipd/../../include -DBINDIR=\"/usr/bin\" -DSBINDIR=\"/usr/sbin\" -I/usr/obj/usr/src/i386/usr/include -c /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip/kipd.c In file included from /usr/obj/usr/src/i386/usr/include/net/if_var.h:78, from /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip/kip.h:78, from /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip/kipd.c:36: /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: size of array `MH_databuf' has non-integer type /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: `MSIZE' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: size of array `M_databuf' has non-integer type /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:239: `MCLBYTES' undeclared here (not in a function) In file included from /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/krb/krb.h:355, from /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip/kip.h:87, from /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/appl/kip/kipd.c:36: /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/krb/krb-protos.h:523: syntax error before `.' /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/krb/krb-protos.h:533: syntax error before `.' /usr/src/kerberosIV/libexec/kipd/../../../crypto/kerberosIV/lib/krb/krb-protos.h:551: syntax error before `.' -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "It's not what we don't know that hurts us, it's what we know for certain that just ain't so." -- Mark Twain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 10:34:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 723C037B4C5 for ; Sat, 25 Nov 2000 10:34:37 -0800 (PST) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id eAPIYXK27862 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK) for ; Sat, 25 Nov 2000 19:34:36 +0100 (MET) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id eAPIYZM49037 for ; Sat, 25 Nov 2000 19:34:36 +0100 (CET) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id eAPIYVx40758 for freebsd-current@freebsd.org; Sat, 25 Nov 2000 19:34:31 +0100 (CET) (envelope-from ticso) Date: Sat, 25 Nov 2000 19:34:30 +0100 From: Bernd Walter To: freebsd-current@freebsd.org Subject: Patch for current on LCA based alphas Message-ID: <20001125193430.A40717@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG LCA systems doesn't like probing after PCI slot 19. Probing slot 20 panics the system. The following patch made it into single user mode on my AXPpci33. I asume it will also work on multias. I can't tell more as the tested system is a 4.1-RELEASE and I need to update the world before further testing. Index: lca_pci.c =================================================================== RCS file: /vol/cvs/FreeBSD/src/sys/alpha/pci/lca_pci.c,v retrieving revision 1.7 diff -u -r1.7 lca_pci.c --- lca_pci.c 2000/08/31 16:19:27 1.7 +++ lca_pci.c 2000/11/25 18:23:26 @@ -76,7 +76,7 @@ static int lca_pcib_maxslots(device_t dev) { - return 31; + return 19; } #define LCA_CFGOFF(b, s, f, r) \ -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 10:44:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 3F50537B4C5 for ; Sat, 25 Nov 2000 10:44:35 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id C6FA72B259; Sat, 25 Nov 2000 12:44:34 -0600 (CST) Date: Sat, 25 Nov 2000 12:44:34 -0600 From: Bill Fumerola To: current@freebsd.org Cc: Derek Schene' Subject: Re: libc.so.4 not found Message-ID: <20001125124434.Q14080@elvis.mu.org> References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <20001125030833.A54062@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001125030833.A54062@dragon.nuxi.com>; from obrien@freebsd.org on Sat, Nov 25, 2000 at 03:08:34AM -0800 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 03:08:34AM -0800, David O'Brien wrote: > In this case it doesn't matter -- "a fresh hard drive" and "local > package" implies that the -current packages on ftp.freebsd.org haven't > been built since the bump and are thus slightly out dated. Plus all 3rd party software that provides only binaries (legato, glftpd, etc). Without the compat libraries or the symlink hacks these programs have no way of running. > > I'll renew my annoyance with the fact that we just bumped this without > > even figuring out why things broke or if we could change them in a way > > to save functionality without having to bump the version number[1]. > > It doesn't matter as at least Garrett has some changes he's going to make > that aren't compatible. libc.so will be at least at version "5" in > FreeBSD 5.0, so we'll have to go thru this pain eventually anyway. Suckage. At least we'll know the reason this time. > > We also never propagated this bump to RELENG_4, so the release shipped > > with the worst of both worlds. > > Huh? Why the worst of both worlds?? Incompatible changes AND no way to differentiate between the two. (plus we don't even know what changed it, so we have no way of telling people "your libc before X won't work with binarys that use the frobozz() interface) > I'm not quite sure what isn't together other than no compat4x libc.so.4 > yet -- I can certainly create one, but I'll have to update it for the > libc.so.4 in 4.3 and 4.4. Don't forget the compat libs are uuencoded > files, so CVS will see large diffs. If people don't mind, I'll certainly > make the compat libs now. People who have binaries they can't recompile will need them. The fact that it pains our CVS tree really isn't an issue to me, I'd like to think we have software engineering that utilizes source code management, and not the other way around. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 11: 8:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from host.cer.ntnu.edu.tw (cer.ntnu.edu.tw [140.122.119.9]) by hub.freebsd.org (Postfix) with ESMTP id 96A8437B4C5 for ; Sat, 25 Nov 2000 11:08:26 -0800 (PST) Received: (from clive@localhost) by host.cer.ntnu.edu.tw (8.11.0/8.11.0) id eAPJ7kF55165; Sun, 26 Nov 2000 03:07:46 +0800 (CST) (envelope-from clive) Date: Sun, 26 Nov 2000 03:07:46 +0800 From: Clive Lin To: Bosko Milekic Cc: current@freebsd.org Subject: Re: Kernel panic with ipfw pipes Message-ID: <20001126030746.A55094@host.cer.ntnu.edu.tw> Reply-To: Clive Lin References: <8vi3j3$43o$1@FreeBSD.csie.NCTU.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <8vi3j3$43o$1@FreeBSD.csie.NCTU.edu.tw>; from bmilekic@technokratis.com on Thu, Nov 23, 2000 at 11:40:19AM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, This works ! I was the dummynet victim due to dummynet, but now I'm saved :-) Hopes this to be committed soon. On Thu, Nov 23, 2000 at 11:40:19AM +0800, Bosko Milekic wrote: > Please try this patch and report: > > http://people.freebsd.org/~bmilekic/ip_pipe.diff -- CirX - This site doesnt' exist. 9c k9o h9 s1bg s1f, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38. ant sj m8r ob ? 1fj mwby a1 tao vg5. soq df v' .a. CirX. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 11:27:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from berserker.bsdi.com (unknown [199.79.183.1]) by hub.freebsd.org (Postfix) with ESMTP id B76DB37B4D7; Sat, 25 Nov 2000 11:27:54 -0800 (PST) Received: from berserker.bsdi.com (cp@localhost.bsdi.com [127.0.0.1]) by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA17860; Sat, 25 Nov 2000 12:27:54 -0700 (MST) (envelope-from cp@berserker.bsdi.com) Message-Id: <200011251927.MAA17860@berserker.bsdi.com> To: Poul-Henning Kamp Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-reply-to: Your message of "Wed, 22 Nov 2000 21:40:41 +0100." <1050.974925641@critter> From: Chuck Paterson Date: Sat, 25 Nov 2000 12:27:54 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there reason to believe that we won't have dead lock problems from the M_WAITOK? It seems like that if anything in the path needed to full fill the malloc needs to log there is a problem. Chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 12:26:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D459737B479; Sat, 25 Nov 2000 12:26:09 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAPKQ2T20475; Sat, 25 Nov 2000 21:26:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Paterson Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: Your message of "Sat, 25 Nov 2000 12:27:54 MST." <200011251927.MAA17860@berserker.bsdi.com> Date: Sat, 25 Nov 2000 21:26:02 +0100 Message-ID: <20473.975183962@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011251927.MAA17860@berserker.bsdi.com>, Chuck Paterson writes: > > Is there reason to believe that we won't have dead lock >problems from the M_WAITOK? It seems like that if anything in >the path needed to full fill the malloc needs to log there >is a problem. We don't otherwise treat the /dev/console file descriptor magically. Think about ktracing a process which writes to /dev/console, debugging it and so on... One can successfully argue that the relationship between the console device and syslogd is needlessly incestous but until somebody restructures the console code to be more sanely (or even just at all) layered that is a "Sigh.. wouldn't it be nice if..." kind of item. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 12:34:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by hub.freebsd.org (Postfix) with ESMTP id E0C2937B4C5 for ; Sat, 25 Nov 2000 12:34:26 -0800 (PST) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.11.1/8.11.1) id eAPKeH620773 for freebsd-current@freebsd.org; Sat, 25 Nov 2000 12:40:17 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200011252040.eAPKeH620773@troutmask.apl.washington.edu> Subject: world broken: mbuf.h:120: `MSIZE' undeclared here To: freebsd-current@freebsd.org Date: Sat, 25 Nov 2000 12:40:17 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.bin/netstat cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/if.c In file included from /usr/obj/usr/src/i386/usr/include/net/if_var.h:78, from /usr/src/usr.bin/netstat/if.c:49: /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: size of array `MH_databuf' has non-integer type /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: `MSIZE' undeclared here (not in a function) /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: size of array `M_databuf' has non-integer type /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:239: `MCLBYTES' undeclared here (not in a function) *** Error code 1 Stop in /usr/src/usr.bin/netstat. *** Error code 1 Sources are from today at 10:27 PST. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 13:31:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.internet.dk (ns.internet.dk [194.19.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 4244F37B4CF for ; Sat, 25 Nov 2000 13:31:22 -0800 (PST) Received: (from uucp@localhost) by ns.internet.dk (8.11.1/8.11.1) with UUCP id eAPLVDK53881; Sat, 25 Nov 2000 22:31:13 +0100 (CET) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.11.0/8.11.0) with SMTP id eAPLRqp97483; Sat, 25 Nov 2000 22:28:04 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <003f01c05726$da81fe60$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Bill Fumerola" , Cc: "Derek Schene'" References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <20001125030833.A54062@dragon.nuxi.com> <20001125124434.Q14080@elvis.mu.org> Subject: Re: libc.so.4 not found Date: Sat, 25 Nov 2000 22:28:53 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps core on Fbsd current? It works on a Fbsd stable. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 13:31:45 2000 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 8807537B4CF for ; Sat, 25 Nov 2000 13:31:43 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA56509; Sat, 25 Nov 2000 13:31:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAPLVcH02527; Sat, 25 Nov 2000 13:31:38 -0800 (PST) (envelope-from obrien) Date: Sat, 25 Nov 2000 13:31:38 -0800 From: "David O'Brien" To: Cyrille Lefevre Cc: current@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch Message-ID: <20001125133138.A2493@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <200011231207.eANC70202422@Magelan.Leidinger.net> <7l5umdtm.fsf@gits.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7l5umdtm.fsf@gits.dyndns.org>; from clefevre@cybercable.fr on Fri, Nov 24, 2000 at 01:08:37AM +0100 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Nov 24, 2000 at 01:08:37AM +0100, Cyrille Lefevre wrote: > > Its in the scrollback buffer. > > and how do you access the scroll-back buffer if you are not front to the > console (read remote) ? Do you mean remotely loged in across the network, or a serial [remote] console? If you mean the later the comconsole port logs all console output to a file. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 13:43:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [207.154.226.10]) by hub.freebsd.org (Postfix) with ESMTP id D030037B4CF for ; Sat, 25 Nov 2000 13:43:37 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1098) id 56AE22B259; Sat, 25 Nov 2000 15:43:32 -0600 (CST) Date: Sat, 25 Nov 2000 15:43:32 -0600 From: Bill Fumerola To: Leif Neland Cc: current@FreeBSD.ORG Subject: Re: libc.so.4 not found Message-ID: <20001125154332.V14080@elvis.mu.org> References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <20001125030833.A54062@dragon.nuxi.com> <20001125124434.Q14080@elvis.mu.org> <003f01c05726$da81fe60$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003f01c05726$da81fe60$0e00a8c0@neland.dk>; from leifn@neland.dk on Sat, Nov 25, 2000 at 10:28:53PM +0100 X-Operating-System: FreeBSD 4.2-FEARSOME-20001103 i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 10:28:53PM +0100, Leif Neland wrote: > Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps > core on Fbsd current? > It works on a Fbsd stable. no, if it was missing the proper version of libc, the linker would let you know about it. coredump is completly different. I'd suggest truss/kdump/etc to try and figure out what avp is doing differently on -current then -stable. -- Bill Fumerola - security yahoo / Yahoo! inc. - fumerola@yahoo-inc.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 13:57:17 2000 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 7720237B4CF for ; Sat, 25 Nov 2000 13:57:15 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id NAA56585; Sat, 25 Nov 2000 13:56:58 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAPLunP02645; Sat, 25 Nov 2000 13:56:49 -0800 (PST) (envelope-from obrien) Date: Sat, 25 Nov 2000 13:56:49 -0800 From: "David O'Brien" To: Bill Fumerola Cc: current@freebsd.org, "Derek Schene'" Subject: Re: libc.so.4 not found Message-ID: <20001125135649.C2493@dragon.nuxi.com> Reply-To: current@freebsd.org References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <20001125030833.A54062@dragon.nuxi.com> <20001125124434.Q14080@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20001125124434.Q14080@elvis.mu.org>; from billf@mu.org on Sat, Nov 25, 2000 at 12:44:34PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 12:44:34PM -0600, Bill Fumerola wrote: > > Huh? Why the worst of both worlds?? > > Incompatible changes AND no way to differentiate between the two. (plus we > don't even know what changed it, so we have no way of telling people "your > libc before X won't work with binarys that use the frobozz() interface) There wasn't an incompatible change. There is too much confusion on this issue. There were two things that caused a problem. 1. a bug in libc_r such that programs that ran before, crashed. 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. #1 just showed off incorrect application code. #2 has never been officially supported. > People who have binaries they can't recompile will need them. The fact that > it pains our CVS tree really isn't an issue to me, This is -current, so people should be able to deal with the issue. I'll probably put a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually. > I'd like to think we have software engineering that utilizes source > code management, and not the other way around. I would like to think that way too -- but that isn't the truth. As I said, I'm willing to commit a compat lib now, but I don't want any crap when I update it and the diff is the size of the file itself. -- -- David (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 Sat Nov 25 14: 7:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.utep.edu (mail.cs.utep.edu [129.108.5.3]) by hub.freebsd.org (Postfix) with ESMTP id 5210337B479 for ; Sat, 25 Nov 2000 14:07:15 -0800 (PST) Received: from gecko (gecko [129.108.5.51]) by cs.utep.edu (8.10.1/8.10.1) with ESMTP id eAPM76M11227; Sat, 25 Nov 2000 15:07:07 -0700 (MST) Date: Sat, 25 Nov 2000 15:07:05 -0700 (MST) From: X-Sender: janb@gecko To: current@FreeBSD.ORG Cc: Bill Fumerola , "Derek Schene'" Subject: Re: libc.so.4 not found In-Reply-To: <20001125135649.C2493@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am not sure, if anybody care for this fix, but I just copied libc.so.5 to libc.so.4 when kde was complaining about not finding it. I am not sure if this should work, but it does work just fine... JAn On Sat, 25 Nov 2000, David O'Brien wrote: > On Sat, Nov 25, 2000 at 12:44:34PM -0600, Bill Fumerola wrote: > > > Huh? Why the worst of both worlds?? > > > > Incompatible changes AND no way to differentiate between the two. (plus we > > don't even know what changed it, so we have no way of telling people "your > > libc before X won't work with binarys that use the frobozz() interface) > > There wasn't an incompatible change. There is too much confusion on > this issue. There were two things that caused a problem. > > 1. a bug in libc_r such that programs that ran before, crashed. > 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. > > #1 just showed off incorrect application code. > #2 has never been officially supported. > > > People who have binaries they can't recompile will need them. The fact that > > it pains our CVS tree really isn't an issue to me, > > This is -current, so people should be able to deal with the issue. I'll > probably put a 4.2-RELEASE libc.so.4 up for people to download and put in > /usr/lib/compat manually. > > > I'd like to think we have software engineering that utilizes source > > code management, and not the other way around. > > I would like to think that way too -- but that isn't the truth. > As I said, I'm willing to commit a compat lib now, but I don't want any > crap when I update it and the diff is the size of the file itself. > > -- > -- David (obrien@FreeBSD.org) > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 14:28:14 2000 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 0FB7A37B4CF for ; Sat, 25 Nov 2000 14:28:11 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA56654; Sat, 25 Nov 2000 14:28:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAPMPEx02735; Sat, 25 Nov 2000 14:25:14 -0800 (PST) (envelope-from obrien) Date: Sat, 25 Nov 2000 14:19:07 -0800 From: "David O'Brien" To: janb@cs.utep.edu Cc: current@FreeBSD.ORG Subject: Re: libc.so.4 not found Message-ID: <20001125141907.D2493@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <20001125135649.C2493@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from janb@cs.utep.edu on Sat, Nov 25, 2000 at 03:07:05PM -0700 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 03:07:05PM -0700, janb@cs.utep.edu wrote: > I am not sure, if anybody care for this fix, but I just copied libc.so.5 > to libc.so.4 when kde was complaining about not finding it. I am not sure > if this should work, but it does work just fine... It will work for a while. But we'll have to offer -current users a proper libc.so.4 soon. -- -- David (obrien@FreeBSD.org) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 14:53:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from field.videotron.net (field.videotron.net [205.151.222.108]) by hub.freebsd.org (Postfix) with ESMTP id 9A0E237B479 for ; Sat, 25 Nov 2000 14:53:16 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by field.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G4L00K0FRKNXM@field.videotron.net> for current@freebsd.org; Sat, 25 Nov 2000 17:53:11 -0500 (EST) Date: Sat, 25 Nov 2000 17:53:40 -0500 (EST) From: Bosko Milekic Subject: Re: Kernel panic with ipfw pipes In-reply-to: <20001126030746.A55094@host.cer.ntnu.edu.tw> To: Clive Lin Cc: current@freebsd.org Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gentlemen, I'm holding up on committing this as we speak as I believe the counter manipulations become illegal following the ifq locking commits. This is good as it will give us an opportunity/bigger reason to review this code further before making a commit. Feel free to use the diff for yourselves for now. Cheers, Bosko. On Sun, 26 Nov 2000, Clive Lin wrote: > Hi, > > This works ! I was the dummynet victim due to dummynet, but now > I'm saved :-) Hopes this to be committed soon. > > On Thu, Nov 23, 2000 at 11:40:19AM +0800, Bosko Milekic wrote: > > Please try this patch and report: > > > > http://people.freebsd.org/~bmilekic/ip_pipe.diff > > -- > CirX - This site doesnt' exist. > 9c k9o h9 s1bg s1f, 7v .y xqx a sj m8r ffg1 vg5 a6 asox tmul h38. > ant sj m8r ob ? 1fj mwby a1 tao vg5. soq df v' .a. CirX. > > Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 14:57:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.chuckr.org (picnic.chuckr.org [216.254.96.118]) by hub.freebsd.org (Postfix) with ESMTP id 4547737B4C5 for ; Sat, 25 Nov 2000 14:57:16 -0800 (PST) Received: from localhost (chuckr@localhost) by picnic.chuckr.org (8.11.1/8.9.3) with ESMTP id eAPNw4O00493 for ; Sat, 25 Nov 2000 18:58:04 -0500 (EST) (envelope-from chuckr@picnic.chuckr.org) Date: Sat, 25 Nov 2000 18:58:04 -0500 (EST) From: Chuck Robey To: FreeBSD-current Subject: lpd panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm finally having enough time again to look at FreeBSD again, so I went back and I'm looking at my port complaints. In looking at a2ps, after I reinstalled it fresh (so if it'd been changed I would see those) I see it seems to be going ok, but I pick up a kernel panic whilst printing. The process active at the time is (irq7:lpt0), the trace shows it's dying in fork_trampoline. I have a two processor machine in a very recent (hours old) current, and the panic is a "supervisor read, page not present". If this is familiar to anyone, please give me a shout (note I *am* running a smp kernel). If I get no reply, I guess I'm going to see about tracing this thing back. Thanks. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 15: 1:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from falla.videotron.net (falla.videotron.net [205.151.222.106]) by hub.freebsd.org (Postfix) with ESMTP id 39BEC37B4D7; Sat, 25 Nov 2000 15:01:07 -0800 (PST) Received: from modemcable213.3-201-24.mtl.mc.videotron.ca ([24.201.3.213]) by falla.videotron.net (Sun Internet Mail Server sims.3.5.1999.12.14.10.29.p8) with ESMTP id <0G4L000XWRXSIU@falla.videotron.net>; Sat, 25 Nov 2000 18:01:05 -0500 (EST) Date: Sat, 25 Nov 2000 18:01:33 -0500 (EST) From: Bosko Milekic Subject: Re: world broken: mbuf.h:120: `MSIZE' undeclared here In-reply-to: <200011252040.eAPKeH620773@troutmask.apl.washington.edu> To: Steve Kargl Cc: jlemon@freebsd.org, freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No biggie guys... jlemon, I think you may want to remove the include for sys/mbuf.h in if_var.h if it isn't needed (try) -- I think this is what may be screwing up netstat. Sorry, Steve, for this inconvenience, but this stuff does occasionally happen in -CURRENT. :-) On Sat, 25 Nov 2000, Steve Kargl wrote: > ===> usr.bin/netstat > cc -O -pipe -Wall -DIPSEC -DINET6 -DIPSEC -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/netstat/if.c > In file included from /usr/obj/usr/src/i386/usr/include/net/if_var.h:78, > from /usr/src/usr.bin/netstat/if.c:49: > /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: `MSIZE' undeclared here (not in a function) > /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:120: size of array `MH_databuf' has non-integer type > /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: `MSIZE' undeclared here (not in a function) > /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:123: size of array `M_databuf' has non-integer type > /usr/obj/usr/src/i386/usr/include/sys/mbuf.h:239: `MCLBYTES' undeclared here (not in a function) > *** Error code 1 > > Stop in /usr/src/usr.bin/netstat. > *** Error code 1 > > > Sources are from today at 10:27 PST. > -- > Steve Cheers, Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 15:25:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mharnois.workgroup.net (c1030098-a.wtrlo1.ia.home.com [24.11.39.39]) by hub.freebsd.org (Postfix) with ESMTP id BC08837B4C5; Sat, 25 Nov 2000 15:25:53 -0800 (PST) Received: (from mdharnois@localhost) by mharnois.workgroup.net (8.11.1/8.11.1) id eAPNPnN03587; Sat, 25 Nov 2000 17:25:49 -0600 (CST) (envelope-from mdharnois@home.com) X-Authentication-Warning: mharnois.workgroup.net: mdharnois set sender to mdharnois@home.com using -f To: Bosko Milekic Cc: Steve Kargl , jlemon@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: world broken: mbuf.h:120: `MSIZE' undeclared here Keywords: usr,src,libncp,ipx,include References: From: Michael Harnois Date: 25 Nov 2000 17:25:48 -0600 In-Reply-To: Message-ID: <86d7fjhbwj.fsf@mharnois.workgroup.net> Lines: 20 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.2 (Pan) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Nov 2000 18:01:33 -0500 (EST), Bosko Milekic said: > jlemon, I think you may want to remove the include for > sys/mbuf.h in if_var.h if it isn't needed (try) -- I think this > is what may be screwing up netstat. I tried your suggestion and it got me past the problem I was having in kerberosIV (same error as Steve, different place) but stopped here: ===> libncp cc -O -pipe -march=i686 -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libncp/ipx.c -o ipx.o In file included from /usr/src/lib/libncp/ipx.c:41: /usr/obj/usr/src/i386/usr/include/net/if_var.h:95: field `ifq_mtx' has incomplete type -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois@home.com aa0bt@aa0bt.ampr.org "Any movement in history which attempts to perpetuate itself, becomes reactionary." -- Josip Broz Tito To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 15:35:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp2.san.rr.com (smtp2.san.rr.com [24.25.195.39]) by hub.freebsd.org (Postfix) with ESMTP id EBF0237B4CF for ; Sat, 25 Nov 2000 15:35:35 -0800 (PST) Received: from san.rr.com ([24.25.222.134]) by smtp2.san.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-0U10L2S100V35) with ESMTP id com for ; Sat, 25 Nov 2000 15:32:43 -0800 Message-ID: <3A204C98.CE92ADD0@san.rr.com> Date: Sat, 25 Nov 2000 15:34:49 -0800 From: Derek Schene' X-Mailer: Mozilla 4.75 [en] (Win95; U) X-Accept-Language: en,pdf MIME-Version: 1.0 To: current@freebsd.org Subject: Re: libc.so.4 not found References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for everyone's input, I feel I'm getting closer and see where my previous thinking had gone wrong. I tried this- > I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible > should happen. and now when booting get- Local package initialization:fopen: No such file or directory So I copied libc.so.4 from the 4.0 livefile cd....This gave the same message (also had a core dump but may be unrelated). But the good news is now emacs, cvsup, etc. are working. I don't know if this matters but when looking at- implies that the -current packages on ftp.freebsd.org haven't been built since the bump and are thus slightly out dated. I'm thinking the snapshot came from current.freebsd.org? (SNAP5) And when it was mentioned- 2. a 4.1.1-RELEASE libc.so.4 was being used on a 4.0-RELEASE system. I thought I may have problems with using 4.0-RELEASE libc.so.4 on a 5.0-CURRENT system and may be better going with the symlink to libc.so.5? or look for a 4.2-RELEASE libc.so.4 up for people to download and put in /usr/lib/compat manually.? Thanks, Derek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 17:16:47 2000 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 DDC8137B4C5 for ; Sat, 25 Nov 2000 17:16:45 -0800 (PST) Received: from dragon.nuxi.com (root@trang.nuxi.com [209.152.133.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA57148; Sat, 25 Nov 2000 17:16:40 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.11.1/8.11.1) id eAQ1Gdv10523; Sat, 25 Nov 2000 17:16:39 -0800 (PST) (envelope-from obrien) Date: Sat, 25 Nov 2000 17:16:38 -0800 From: "David O'Brien" To: "Derek Schene'" Cc: current@freebsd.org Subject: Re: libc.so.4 not found Message-ID: <20001125171638.A10485@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <3A204C98.CE92ADD0@san.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A204C98.CE92ADD0@san.rr.com>; from ferret@san.rr.com on Sat, Nov 25, 2000 at 03:34:49PM -0800 X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Nov 25, 2000 at 03:34:49PM -0800, Derek Schene' wrote: > I tried this- > > > I'd suggest just symlinking libc.so.4 to libc.so.5, nothing terrible > > should happen. Since nothing has changed in the -CURRENT libc yet, this will work. BTW, you'd want to do the same for libc_r.so.4. > Local package initialization:fopen: No such file or directory I would go into /usr/local/etc/rc.d/ and try to figure out *which* binary is causing all the trouble so the problem can be efficiently debugged. At this point you're skating around the problem rather than just hit it head on. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 19:13:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from racine.cybercable.fr (racine.cybercable.fr [212.198.0.201]) by hub.freebsd.org (Postfix) with SMTP id EFB6137B4CF for ; Sat, 25 Nov 2000 19:13:33 -0800 (PST) Received: (qmail 71567 invoked from network); 26 Nov 2000 03:13:32 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by racine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Nov 2000 03:13:32 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id eAQ3DVN75472; Sun, 26 Nov 2000 04:13:31 +0100 (CET) (envelope-from clefevre@citeweb.net) Original-Sender: Cyrille Lefevre Original-Sender: Cyrille Lefevre To: Alexander Leidinger Cc: clefevre@cybercable.fr, ashp@unloved.org, current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch References: <200011241639.eAOGdOE06364@Magelan.Leidinger.net> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre In-Reply-To: Alexander Leidinger's message of "Fri, 24 Nov 2000 17:39:23 +0100 (CET)" From: Cyrille Lefevre Date: 26 Nov 2000 04:13:30 +0100 Message-ID: Lines: 27 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alexander Leidinger writes: > On 24 Nov, Cyrille Lefevre wrote: > > >> >> The attached patch is a "proof-of-concept" on which I would like > >> >> to get some comments: > >> > > >> > I'm only a moronic user, but this would make my life easier. My machine > >> > switches into 132x43 on startup, and I always lose the output. So this > >> > >> Its in the scrollback buffer. > > > > and how do you access the scroll-back buffer if you are not front to the > > console (read remote) ? > > You can't. > > I didn't see the relationship between my answer to Ashley and your > question, can you please give me a hint? I just want to say that I'm full about doing something which logs what's happen at boot time, and that the scrollback buffer isn't sufficient. in other words, something like PR#14931 until this work is commited. Cyrille. -- home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 20:10:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 2DE1337B4CF for ; Sat, 25 Nov 2000 20:10:22 -0800 (PST) Received: (qmail 9213463 invoked from network); 26 Nov 2000 04:10:19 -0000 Received: from s011.dhcp212-229.cybercable.fr (HELO gits.dyndns.org) ([212.198.229.11]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 26 Nov 2000 04:10:19 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.1/8.11.1) id eAQ4AIR75559; Sun, 26 Nov 2000 05:10:18 +0100 (CET) (envelope-from clefevre@citeweb.net) Original-Sender: Cyrille Lefevre Original-Sender: Cyrille Lefevre To: current@FreeBSD.ORG Cc: Cyrille Lefevre Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch References: <200011231207.eANC70202422@Magelan.Leidinger.net> <7l5umdtm.fsf@gits.dyndns.org> <20001125133138.A2493@dragon.nuxi.com> X-Face: V|+c;4!|B?E%BE^{E6);aI.[<97Zd*>^#%Y5Cxv;%Y[PT-LW3;A:fRrJ8+^k"e7@+30g0YD0*^^3jgyShN7o?a]C la*Zv'5NA,=963bM%J^o]C Reply-To: Cyrille Lefevre In-Reply-To: "David O'Brien"'s message of "Sat, 25 Nov 2000 13:31:38 -0800" From: Cyrille Lefevre Date: 26 Nov 2000 05:10:16 +0100 Message-ID: Lines: 23 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Channel Islands) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > On Fri, Nov 24, 2000 at 01:08:37AM +0100, Cyrille Lefevre wrote: > > > Its in the scrollback buffer. > > > > and how do you access the scroll-back buffer if you are not front to the > > console (read remote) ? > > Do you mean remotely loged in across the network, or a serial [remote] > console? If you mean the later the comconsole port logs all console > output to a file. remotly logged. at my job, I manage around 160 machines (unfortunaly, there is no FreeBSD) and I appreciate HP-UX boxes which have this feature. if something doesn't start at boot time, I've just to look at /var/adm/rc.log and search the FAIL keyword. don't rememeber about IRIX boxes, nothing exists under Solaris boxes. Cyrille. -- Cyrille Lefevre 12, Rue de Bizerte 75017 Paris tel/fax: +33 (0)1 45 22 83 85 home: mailto:clefevre@citeweb.net work: mailto:Cyrille.Lefevre@edf.fr icq: mailto:17089123@pager.icq.com http://wwp.icq.com/17089123 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 20:16:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mobile.wemm.org (adsl-64-163-195-99.dsl.snfc21.pacbell.net [64.163.195.99]) by hub.freebsd.org (Postfix) with ESMTP id 1542137B4CF for ; Sat, 25 Nov 2000 20:16:42 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by mobile.wemm.org (8.11.1/8.11.1) with ESMTP id eAQ4GRD25816; Sat, 25 Nov 2000 20:16:27 -0800 (PST) (envelope-from peter@netplex.com.au) Message-Id: <200011260416.eAQ4GRD25816@mobile.wemm.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Christian Carstensen Cc: "Rogier R. Mulhuijzen" , current@FreeBSD.ORG, imp@freebsdf.org Subject: Re: -current on ibm tp a20p? In-Reply-To: Date: Sat, 25 Nov 2000 20:16:27 -0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Carstensen wrote: > On Fri, 24 Nov 2000, Rogier R. Mulhuijzen wrote: > > > 1) is this a CardBus card maybe? > > It happens with > > a) Lucent WaveLAN (silver) > b) 3com 3c589d > > > > 2) What does 'pccardc dumpcis' return? > > Code 85 not found > Code 85 not found > code Unknown ignored > Code 134 not found > Code 134 not found This means your pccard memory window overlaps something. Do you have an ATI rage chipset by any chance? My Vaio has one of these and its rom is 80K long and goes from 0xc0000 -> 0xd3fff. pccardd defaults to 0xd0000 for mapping the CIS which is right underneath the ROM. Try: pccard_mem="0xd4000" in /etc/rc.conf. Or even 0xd8000 if that doesn't work. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 20:22:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id 7606D37B479 for ; Sat, 25 Nov 2000 20:22:31 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAQ4NRJ13599; Sat, 25 Nov 2000 20:23:27 -0800 (PST) (envelope-from kris) Date: Sat, 25 Nov 2000 20:23:27 -0800 From: Kris Kennaway To: Leif Neland Cc: current@FreeBSD.ORG Subject: Re: libc.so.4 not found Message-ID: <20001125202326.A13561@citusc17.usc.edu> References: <3A1F75E3.2E17FC43@san.rr.com> <20001125024407.O14080@elvis.mu.org> <20001125030833.A54062@dragon.nuxi.com> <20001125124434.Q14080@elvis.mu.org> <003f01c05726$da81fe60$0e00a8c0@neland.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="qMm9M+Fa2AknHoGS" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003f01c05726$da81fe60$0e00a8c0@neland.dk>; from leifn@neland.dk on Sat, Nov 25, 2000 at 10:28:53PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --qMm9M+Fa2AknHoGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Nov 25, 2000 at 10:28:53PM +0100, Leif Neland wrote: > Could this be the reason why Avp (virusscanner) for FreeBSD 4X just dumps > core on Fbsd current? > It works on a Fbsd stable. Could be malloc.conf defaults. i.e. a bug in avp triggered by the debugging /etc/malloc.conf settings in -current. Kris --qMm9M+Fa2AknHoGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjogkD4ACgkQWry0BWjoQKXSTQCfU/G6wzJ9CawSl3W4GWFJx4ha a+gAoIrBRtzAGVzbOpTcO+Yg9HRGVGg/ =ibV6 -----END PGP SIGNATURE----- --qMm9M+Fa2AknHoGS-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 21:58:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from citusc17.usc.edu (citusc17.usc.edu [128.125.38.177]) by hub.freebsd.org (Postfix) with ESMTP id BDA3137B4CF for ; Sat, 25 Nov 2000 21:58:13 -0800 (PST) Received: (from kris@localhost) by citusc17.usc.edu (8.11.1/8.11.1) id eAQ5xDi15345 for current@FreeBSD.org; Sat, 25 Nov 2000 21:59:13 -0800 (PST) (envelope-from kris) Date: Sat, 25 Nov 2000 21:59:13 -0800 From: Kris Kennaway To: current@FreeBSD.org Subject: wall/rwall cleanups Message-ID: <20001125215912.A15309@citusc17.usc.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Nq2Wo0NMKNjxTN9z" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Nq2Wo0NMKNjxTN9z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Please review. This syncs up our code with some NetBSD changes, as well as attempting to sync rwall up with wall. Kris Index: wall/wall.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: /mnt/ncvs/src/usr.bin/wall/wall.c,v retrieving revision 1.15 diff -u -r1.15 wall.c --- wall/wall.c 2000/10/02 17:31:57 1.15 +++ wall/wall.c 2000/11/26 05:55:24 @@ -68,6 +68,7 @@ =20 void makemsg __P((char *)); static void usage __P((void)); +char *ttymsg __P((struct iovec *, int, char *, int)); =20 #define IGNOREUSER "sleeper" =20 @@ -85,7 +86,7 @@ struct iovec iov; struct utmp utmp; FILE *fp; - char *p, *ttymsg(); + char *p; char line[sizeof(utmp.ut_line) + 1]; =20 (void)setlocale(LC_CTYPE, ""); @@ -109,7 +110,7 @@ makemsg(*argv); =20 if (!(fp =3D fopen(_PATH_UTMP, "r"))) - errx(1, "cannot read %s", _PATH_UTMP); + err(1, "cannot read %s", _PATH_UTMP); iov.iov_base =3D mbuf; iov.iov_len =3D mbufsize; /* NOSTRICT */ @@ -144,17 +145,17 @@ time_t now; FILE *fp; int fd; - char *p, *whom, hostname[MAXHOSTNAMELEN], lbuf[256], tmpname[64]; + char *p, *tty, hostname[MAXHOSTNAMELEN], lbuf[256], tmpname[64]; + const char *whom; =20 - snprintf(tmpname, sizeof(tmpname), "%s/wall.XXXXXX", _PATH_TMP); - - if (!(fd =3D mkstemp(tmpname)) || !(fp =3D fdopen(fd, "r+"))) - errx(1, "can't open temporary file"); + (void)snprintf(tmpname, sizeof(tmpname), "%s/wall.XXXXXX", _PATH_TMP); + if ((fd =3D mkstemp(tmpname)) =3D=3D -1 || !(fp =3D fdopen(fd, "r+"))) + err(1, "can't open temporary file"); (void)unlink(tmpname); =20 if (!nobanner) { - char *tty =3D ttyname(2); - if (!tty) + tty =3D ttyname(STDERR_FILENO); + if (tty =3D=3D NULL) tty =3D "no tty"; =20 if (!(whom =3D getlogin())) @@ -175,7 +176,7 @@ "Broadcast Message from %s@%s", whom, hostname); (void)fprintf(fp, "%-79.79s\007\007\r\n", lbuf); - (void)snprintf(lbuf, sizeof(lbuf),=20 + (void)snprintf(lbuf, sizeof(lbuf), " (%s) at %d:%02d %s...", tty, lt->tm_hour, lt->tm_min, lt->tm_zone); (void)fprintf(fp, "%-79.79s\r\n", lbuf); @@ -183,7 +184,7 @@ (void)fprintf(fp, "%79s\r\n", " "); =20 if (fname && !(freopen(fname, "r", stdin))) - errx(1, "can't read %s", fname); + err(1, "can't read %s", fname); while (fgets(lbuf, sizeof(lbuf), stdin)) for (cnt =3D 0, p =3D lbuf; (ch =3D *p) !=3D '\0'; ++p, ++cnt) { if (ch =3D=3D '\r') { @@ -232,11 +233,11 @@ rewind(fp); =20 if (fstat(fd, &sbuf)) - errx(1, "can't stat temporary file"); + err(1, "can't stat temporary file"); mbufsize =3D sbuf.st_size; if (!(mbuf =3D malloc((u_int)mbufsize))) - errx(1, "out of memory"); + err(1, "out of memory"); if (fread(mbuf, sizeof(*mbuf), mbufsize, fp) !=3D mbufsize) - errx(1, "can't read temporary file"); + err(1, "can't read temporary file"); (void)close(fd); } Index: rwall/rwall.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: /mnt/ncvs/src/usr.bin/rwall/rwall.c,v retrieving revision 1.8 diff -u -r1.8 rwall.c --- rwall/rwall.c 1999/08/28 01:05:32 1.8 +++ rwall/rwall.c 2000/11/26 05:55:59 @@ -61,6 +61,7 @@ #include #include #include +#include #include #include =20 @@ -70,8 +71,9 @@ int mbufsize; char *mbuf; =20 -void makemsg __P((char *)); +void makemsg __P((char *)); static void usage __P((void)); +char *ttymsg __P((struct iovec *, int, char *, int)); =20 /* ARGSUSED */ int @@ -120,7 +122,7 @@ static void usage() { - fprintf(stderr, "usage: rwall hostname [file]\n"); + (void)fprintf(stderr, "usage: rwall hostname [file]\n"); exit(1); } =20 @@ -131,14 +133,15 @@ struct tm *lt; struct passwd *pw; struct stat sbuf; - time_t now, time(); + time_t now; FILE *fp; int fd; - char *whom, hostname[MAXHOSTNAMELEN], lbuf[256], tmpname[64]; + char *tty, hostname[MAXHOSTNAMELEN], lbuf[256], tmpname[64]; + const char *whom; =20 - snprintf(tmpname, sizeof(tmpname), "%s/wall.XXXXXX", _PATH_TMP); - if (!(fd =3D mkstemp(tmpname)) || !(fp =3D fdopen(fd, "r+"))) - errx(1, "can't open temporary file"); + (void)snprintf(tmpname, sizeof(tmpname), "%s/wall.XXXXXX", _PATH_TMP); + if ((fd =3D mkstemp(tmpname)) =3D=3D -1 || !(fp =3D fdopen(fd, "r+"))) + err(1, "can't open temporary file"); (void)unlink(tmpname); =20 if (!(whom =3D getlogin())) @@ -156,23 +159,26 @@ */ (void)fprintf(fp, "Remote Broadcast Message from %s@%s\n", whom, hostname); - (void)fprintf(fp, " (%s) at %d:%02d ...\n", ttyname(2), + tty =3D ttyname(STDERR_FILENO); + if (tty =3D=3D NULL) + tty =3D "no tty"; + (void)fprintf(fp, " (%s) at %d:%02d ...\n", tty, lt->tm_hour, lt->tm_min); =20 putc('\n', fp); =20 if (fname && !(freopen(fname, "r", stdin))) - errx(1, "can't read %s", fname); + err(1, "can't read %s", fname); while (fgets(lbuf, sizeof(lbuf), stdin)) fputs(lbuf, fp); rewind(fp); =20 if (fstat(fd, &sbuf)) - errx(1, "can't stat temporary file"); + err(1, "can't stat temporary file"); mbufsize =3D sbuf.st_size; if (!(mbuf =3D malloc((u_int)mbufsize))) - errx(1, "out of memory"); + err(1, "out of memory"); if (fread(mbuf, sizeof(*mbuf), mbufsize, fp) !=3D mbufsize) - errx(1, "can't read temporary file"); + err(1, "can't read temporary file"); (void)close(fd); } --Nq2Wo0NMKNjxTN9z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjogprAACgkQWry0BWjoQKX3EACeK1sHctkqaOK5PTMYx4t1fYZz ukgAoJ1XJU80PSq12PpM35YSvLCENAQx =RSwv -----END PGP SIGNATURE----- --Nq2Wo0NMKNjxTN9z-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Nov 25 23:36:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (grouter.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 29A7237B4C5 for ; Sat, 25 Nov 2000 23:36:30 -0800 (PST) Received: from grondar.za (gratis.grondar.za [196.7.18.133]) by gratis.grondar.za (8.11.1/8.11.1) with ESMTP id eAQ7aE804112; Sun, 26 Nov 2000 09:36:14 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200011260736.eAQ7aE804112@gratis.grondar.za> To: Chuck Robey Cc: FreeBSD-current Subject: Re: lpd panic References: In-Reply-To: ; from Chuck Robey "Sat, 25 Nov 2000 18:58:04 EST." Date: Sun, 26 Nov 2000 11:36:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > seems to be going ok, but I pick up a kernel panic whilst printing. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Ditto. Also on a dual-cpu machine, also a really recent CURRENT. 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