From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 00:13:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 768EF16A41F; Sun, 1 Jan 2006 00:13:21 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id EABC843D48; Sun, 1 Jan 2006 00:13:20 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k010DFo7001277 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 31 Dec 2005 16:13:17 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43B71EF7.2010803@errno.com> Date: Sat, 31 Dec 2005 16:14:47 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bill Paul References: <20051231212858.9F9D116A420@hub.freebsd.org> In-Reply-To: <20051231212858.9F9D116A420@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Ondra Holecek , freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 00:13:21 -0000 Bill Paul wrote: >>yes, i can load if_ath, wireless card is found and i can set it up as >>ath0, but i still have no signal (and there are many ap's - i can see >>with different pcmcia card) > > > Note that if this in fact a problem with ACPI not supporting the > wireless enable switch on your laptop correctly, it won't work > with the NDISulator any better than it will with the ath(4) driver. > I think the wireless enable switch controls the connection to the > antenna(s), and is a separate device from the NIC itself that varies > in implementation depending on the laptop. The NDIS driver only knows > how to manipulate the NIC hardware: the NIC manufacturer can't really > customize the driver for each laptop out there (and the laptop > manufacturers usually don't customize the drivers either, beyond > sticking their logo on them). <...ndis related stuff deleted...> Handling this in the ath driver is actually very simple; I've just never done it 'cuz none of my laptops have the this setup to test with. When you hit the switch the driver gets an interrupt from the ath card and can then toggle the state of the rfkill pin. If you run the latest code out for testing there is also a sysctl that you can use to control this manually. Sam From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 01:06:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15D9916A41F for ; Sun, 1 Jan 2006 01:06:02 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from skewer.dreamhost.com (skewer.dreamhost.com [64.111.107.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D5C43D46 for ; Sun, 1 Jan 2006 01:06:01 +0000 (GMT) (envelope-from dev@unixdaemon.org) Received: from [192.168.1.101] (cpe-24-24-83-9.stny.res.rr.com [24.24.83.9]) by skewer.dreamhost.com (Postfix) with ESMTP id E5B4E7C2D7; Sat, 31 Dec 2005 17:06:00 -0800 (PST) From: Dev Tugnait To: Rafael Caesar Lenzi In-Reply-To: <20051231144848.76938.qmail@web51001.mail.yahoo.com> References: <20051231144848.76938.qmail@web51001.mail.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Date: Sat, 31 Dec 2005 20:05:57 -0500 Message-Id: <1136077558.78035.61.camel@dracula.transylvania.net> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: current@freebsd.org Subject: Re: Nvidia driver freeze system X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dev@unixdaemon.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 01:06:02 -0000 On Sat, 2005-12-31 at 11:48 -0300, Rafael Caesar Lenzi wrote: > I installed Nvidia-driver 8178 on FreeBSD-5.4, after start X, logo of > Nvidia appers, and then system freeze and reboot automatically. > Why does this belong in current? Wrong mailing list for one...secondly you haven't mentioned which nvidia gpu or tried to post an actual log of the issue. On a side note nvidia has a forum as well. > Thanks, > > Rafael Lenzi > > > > > > > > > _______________________________________________________ > Yahoo! doce lar. Faça do Yahoo! sua homepage. > http://br.yahoo.com/homepageset.html > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Dev Tugnait From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 01:15:15 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5984D16A41F for ; Sun, 1 Jan 2006 01:15:15 +0000 (GMT) (envelope-from rmtodd@ichotolot.servalan.com) Received: from mx2.synetsystems.com (mx2.synetsystems.com [216.226.140.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EF9D43D58 for ; Sun, 1 Jan 2006 01:15:13 +0000 (GMT) (envelope-from rmtodd@ichotolot.servalan.com) Received: by mx2.synetsystems.com (Postfix, from userid 66) id E766534C; Sat, 31 Dec 2005 20:15:12 -0500 (EST) Received: from rmtodd by servalan.servalan.com with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EsrFz-00003Z-Uq; Sat, 31 Dec 2005 18:39:32 -0600 To: "Wojciech A. Koszek" References: <20051221031526.31ABC290@mx2.synetsystems.com> <200512211111.44268.jhb@freebsd.org> <20051227173434.GA53513@FreeBSD.czest.pl> From: Richard Todd Date: Sat, 31 Dec 2005 18:39:31 -0600 In-Reply-To: <20051227173434.GA53513@FreeBSD.czest.pl> (Wojciech A. Koszek's message of "Tue, 27 Dec 2005 17:34:35 +0000") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: Bug in latest rev kern_acct.c: panic: Trying sleep, but thread marked as sleeping prohibited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 01:15:15 -0000 "Wojciech A. Koszek" writes: > On Wed, Dec 21, 2005 at 11:11:43AM -0500, John Baldwin wrote: >> acctwatch() probably isn't a good thing to do from a callout since it wants to >> do VOPs and such. Probably the easiest fix is to stick acctwatch() in its >> own kthread. > > I think I didn't break current behaviour. Patch is here: > > http://freebsd.czest.pl/dunstan/FreeBSD/kern_acct.0.patch > > Richard, could you try to repeat your problem with my patch? Got a chance to try a new kernel today with your patch. I tried to reproduce the panic by repeatedly copying a bunch of stuff onto /usr and deleting it in one window, and in another repeatedly doing "make configure; make clean" in one rather large port. Lots of "Accounting suspended/resumed" messages in the logs and no panics. So it's looking good from here. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 01:37:58 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02C8816A41F; Sun, 1 Jan 2006 01:37:58 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82FA943D5A; Sun, 1 Jan 2006 01:37:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k011bvX5013508; Sat, 31 Dec 2005 20:37:57 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k011buiY056226; Sat, 31 Dec 2005 20:37:56 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1450A7302F; Sat, 31 Dec 2005 20:37:56 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060101013756.1450A7302F@freebsd-current.sentex.ca> Date: Sat, 31 Dec 2005 20:37:56 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 01:37:58 -0000 TB --- 2006-01-01 00:21:04 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-01 00:21:04 - starting HEAD tinderbox run for alpha/alpha TB --- 2006-01-01 00:21:04 - cleaning the object tree TB --- 2006-01-01 00:21:24 - checking out the source tree TB --- 2006-01-01 00:21:24 - cd /tinderbox/HEAD/alpha/alpha TB --- 2006-01-01 00:21:24 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-01 00:27:16 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-01 00:27:16 - cd /src TB --- 2006-01-01 00:27:16 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2006-01-01 01:32:04 - generating LINT kernel config TB --- 2006-01-01 01:32:04 - cd /src/sys/alpha/conf TB --- 2006-01-01 01:32:04 - /usr/bin/make -B LINT TB --- 2006-01-01 01:32:04 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-01 01:32:04 - cd /src TB --- 2006-01-01 01:32:04 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Jan 1 01:32:04 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/eisa_pci.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/fixup_pci.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/hostb_pci.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/ignore_pci.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/isa_pci.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/pci/pci.c /src/sys/dev/pci/pci.c: In function `pci_add_map': /src/sys/dev/pci/pci.c:903: warning: long long unsigned int format, uint64_t arg (arg 3) *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-01 01:37:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-01 01:37:55 - ERROR: failed to build lint kernel TB --- 2006-01-01 01:37:55 - tinderbox aborted TB --- 0.66 user 3.52 system 4611.38 real From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 02:31:48 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06C1D16A41F; Sun, 1 Jan 2006 02:31:48 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7309543D5A; Sun, 1 Jan 2006 02:31:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp232-237.lns2.adl4.internode.on.net [203.122.232.237]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k012VZwY040983 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Sun, 1 Jan 2006 13:01:37 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Ondra Holecek Date: Sun, 1 Jan 2006 13:01:19 +1030 User-Agent: KMail/1.8.3 References: <43B5274C.5010206@deprese.net> <200512311422.13184.doconnor@gsoft.com.au> <43B65249.1030104@deprese.net> In-Reply-To: <43B65249.1030104@deprese.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2631632.gJjh6IHy4W"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601011301.29541.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: problems with wifi X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 02:31:48 -0000 --nextPart2631632.gJjh6IHy4W Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sat, 31 Dec 2005 20:11, Ondra Holecek wrote: > yes, i can load if_ath, wireless card is found and i can set it up as > ath0, but i still have no signal (and there are many ap's - i can see > with different pcmcia card) > > therefore, i think i have to somehow turn it on (the special "wireless" > key on keyboard of course doesn't work) Hmm, in my experience the key actually works, but there is no response apar= t=20 from the radio magically working. > > Why don't you just load if_ath.ko? It should support that chipset. > i know, i did it. loaded generated kernel module, but no ndis0 Then I'd say you didn't do it correctly :) PS cross posting to 3 lists is a bad idea. I seriously doubt this thread is= =20 appropriate to all 3 (especially -acpi). =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart2631632.gJjh6IHy4W Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDtz8B5ZPcIHs/zowRAj8sAKCa1AuD7VqZ7xe6NrvHAg8JfEjMTQCdEweh vmv7sfjT58Tn4E7PsNjH8j4= =NJ7w -----END PGP SIGNATURE----- --nextPart2631632.gJjh6IHy4W-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 03:05:52 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D550616A41F; Sun, 1 Jan 2006 03:05:52 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29DC543D48; Sun, 1 Jan 2006 03:05:52 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k0135pnx016879; Sat, 31 Dec 2005 22:05:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k0135odM054984; Sat, 31 Dec 2005 22:05:50 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id BA2D87302F; Sat, 31 Dec 2005 22:05:50 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060101030550.BA2D87302F@freebsd-current.sentex.ca> Date: Sat, 31 Dec 2005 22:05:50 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 03:05:53 -0000 TB --- 2006-01-01 01:37:56 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-01 01:37:56 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-01 01:37:56 - cleaning the object tree TB --- 2006-01-01 01:38:18 - checking out the source tree TB --- 2006-01-01 01:38:18 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-01 01:38:18 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-01 01:44:23 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-01 01:44:23 - cd /src TB --- 2006-01-01 01:44:23 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries [...] /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:385: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:395: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:415: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:431: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:432: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:434: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:435: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:437: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/kerberos5/lib/libgssapi. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-01 03:05:50 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-01 03:05:50 - ERROR: failed to build world TB --- 2006-01-01 03:05:50 - tinderbox aborted TB --- 0.99 user 4.14 system 5274.26 real From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 04:59:46 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BEF616A41F; Sun, 1 Jan 2006 04:59:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3048D43D49; Sun, 1 Jan 2006 04:59:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 19B551A4E2C; Sat, 31 Dec 2005 20:59:46 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6B340513FB; Sat, 31 Dec 2005 23:59:45 -0500 (EST) Date: Sat, 31 Dec 2005 23:59:45 -0500 From: Kris Kennaway To: David Xu , Kris Kennaway , freebsd-current@freebsd.org, Jason Evans Message-ID: <20060101045945.GB1464@xor.obsecurity.org> References: <43B36B83.7080404@freebsd.org> <32729773-B07C-4AEE-92D0-62ACE0E3AFEB@freebsd.org> <43B36EB9.70205@freebsd.org> <2E722A13-C880-41B6-A84C-3927C8FE90E5@freebsd.org> <43B3768F.40704@freebsd.org> <811F628B-A89B-4359-A219-13B5337726A9@freebsd.org> <43B378BA.10201@freebsd.org> <20051231034731.GA65751@xor.obsecurity.org> <43B67C49.2010904@freebsd.org> <20051231213407.GA752@funkthat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8GpibOaaTibBMecb" Content-Disposition: inline In-Reply-To: <20051231213407.GA752@funkthat.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: New malloc ready, take 42 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 04:59:46 -0000 --8GpibOaaTibBMecb Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Dec 31, 2005 at 01:34:08PM -0800, John-Mark Gurney wrote: > David Xu wrote this message on Sat, Dec 31, 2005 at 20:40 +0800: > > Kris Kennaway wrote: > >=20 > > >>I remembered its highest number is 216xxx. > > > > > >I don't believe you :-) > >=20 > > Get a Pentium-D , then test it by yourself. :-) >=20 > I think he mean he doesn't believe that it's 200k+... you have three > numbers and three x's... >=20 Yeah, a factor of >10 improvement is not credible. Perhaps you meant 216xx? Kris --8GpibOaaTibBMecb Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDt2HAWry0BWjoQKURArvEAKDuND3NnmYlMLYMvG4j3JqkcNUA4ACglWkq OTJN3Ws6I4Q4dO5SZRhzW8E= =r/ao -----END PGP SIGNATURE----- --8GpibOaaTibBMecb-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 06:10:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id A758416A41F; Sun, 1 Jan 2006 06:10:00 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43B77244.3030205@freebsd.org> Date: Sun, 01 Jan 2006 14:10:12 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.12) Gecko/20051228 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <43B36B83.7080404@freebsd.org> <32729773-B07C-4AEE-92D0-62ACE0E3AFEB@freebsd.org> <43B36EB9.70205@freebsd.org> <2E722A13-C880-41B6-A84C-3927C8FE90E5@freebsd.org> <43B3768F.40704@freebsd.org> <811F628B-A89B-4359-A219-13B5337726A9@freebsd.org> <43B378BA.10201@freebsd.org> <20051231034731.GA65751@xor.obsecurity.org> <43B67C49.2010904@freebsd.org> <20051231213407.GA752@funkthat.com> <20060101045945.GB1464@xor.obsecurity.org> In-Reply-To: <20060101045945.GB1464@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Jason Evans Subject: Re: New malloc ready, take 42 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 06:10:05 -0000 Kris Kennaway wrote: >Yeah, a factor of >10 improvement is not credible. Perhaps you meant >216xx? > >Kris > > Sorry, my typo, it is 216xx. David Xu From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 08:04:16 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E4C7116A41F; Sun, 1 Jan 2006 08:04:15 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA5543D60; Sun, 1 Jan 2006 08:04:12 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k0184CWd028354; Sun, 1 Jan 2006 03:04:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k0184Brf057436; Sun, 1 Jan 2006 03:04:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 6D1937302F; Sun, 1 Jan 2006 03:04:11 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060101080411.6D1937302F@freebsd-current.sentex.ca> Date: Sun, 1 Jan 2006 03:04:11 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 08:04:16 -0000 TB --- 2006-01-01 07:29:33 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-01 07:29:33 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2006-01-01 07:29:33 - cleaning the object tree TB --- 2006-01-01 07:29:40 - checking out the source tree TB --- 2006-01-01 07:29:40 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2006-01-01 07:29:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-01 07:35:53 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-01 07:35:53 - cd /src TB --- 2006-01-01 07:35:53 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ng.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_nw.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_pr.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_sv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c: In function `getaddrinfo': /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:342: error: structure has no member named `_ai_pad' /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:373: error: structure has no member named `_ai_pad' *** Error code 1 Stop in /src/lib/bind/bind. *** Error code 1 Stop in /src/lib/bind. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-01 08:04:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-01 08:04:11 - ERROR: failed to build world TB --- 2006-01-01 08:04:11 - tinderbox aborted TB --- 0.42 user 1.66 system 2077.83 real From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 09:59:13 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DF1716A41F for ; Sun, 1 Jan 2006 09:59:13 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from mail.neovanglist.net (blackacid.neovanglist.net [69.16.150.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9676343D55 for ; Sun, 1 Jan 2006 09:59:12 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from localhost (localhost.neovanglist.net [127.0.0.1]) by mail.neovanglist.net (Postfix) with ESMTP id 033166D442; Sun, 1 Jan 2006 02:59:10 -0700 (MST) Received: from mail.neovanglist.net ([127.0.0.1]) by localhost (blackacid.neovanglist.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12924-08; Sun, 1 Jan 2006 02:59:08 -0700 (MST) Received: from melchior (0x5358bc07.bynxx15.adsl-dhcp.tele.dk [83.88.188.7]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.neovanglist.net (Postfix) with ESMTP id 16F856D44C; Sun, 1 Jan 2006 02:59:08 -0700 (MST) From: Chris Gilbert To: Ulrich Spoerlein Date: Sun, 1 Jan 2006 10:58:56 +0100 User-Agent: KMail/1.8.2 References: <200512270950.KAA06620@stoney.dudes.ch> <20051229102222.GB1024@galgenberg.net> <20051229173701.GA1531@galgenberg.net> In-Reply-To: <20051229173701.GA1531@galgenberg.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601011058.57555.Chris@lainos.org> X-Virus-Scanned: amavisd-new at neovanglist.net Cc: freebsd-current@freebsd.org Subject: Re: ATI on FreeBSD! FireGL Linux Driver Port (New Version) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 09:59:13 -0000 Fantastic! Yup, I'll update the README with this information. (xorg-snap incompatibility) Sorry for my absence for a few days, but here is the current agenda and status: The amd64 version is about 50% ready with the help of a donated amd64 shell. I have been sidetracked however, by some bugs in the fireglcontrolpanel. Once these fireglcontrolpanel bugs are squared away I will resume work on the amd64 port and release a simultaneous i386 and amd64 version with all of the updates. I'm also going to be expanding the documentation provided a fair deal to help get people started. (In my opinion the official ATI docs severely lack and expect the user to use their configuration utilities solely. They offer little to no xorg.conf samples and so on.) It's very important to me that we get what we have polished and working as much as possible before complicating issues by adding a kernel module. Once this has been accomplished, I will resume work on the kernel module required for the 3D DRI. -- Regards, Chris Gilbert On Thursday 29 December 2005 18:37, Ulrich Spoerlein wrote: > > Ok, it was pointed out to me, that xorg-server-snap won't work with this > driver, and I'm happy to report that it works rock solid with the > xorg-server port. > > I even got TV out working without a fuzz, only thing missing is XV on > the TV screen (somehow, there is no XV_SWITCHCRT attribute as with the > radeon(4) driver). > > Anyway, THANK YOU for this Christmas present ;] > > You might wanna mentio the xorg-server-snap incaompatibility in the > README and this is my hardware, which is now known to work: > > acpi_video0@pci1:0:0: class=0x030000 card=0x20011028 chip=0x4e501002 > rev=0x00 hdr=0x00 vendor = 'ATI Technologies Inc' > device = 'Mobility Radeon 9700 (M10 NP) (RV350)' > class = display > subclass = VGA > > > Ulrich Spoerlein From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 09:59:17 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D52D16A41F for ; Sun, 1 Jan 2006 09:59:17 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFC0F43D5D for ; Sun, 1 Jan 2006 09:59:16 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id F1176BC50 for ; Sun, 1 Jan 2006 09:59:15 +0000 (UTC) To: current@freebsd.org From: Poul-Henning Kamp Date: Sun, 01 Jan 2006 10:59:14 +0100 Message-ID: <73774.1136109554@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Subject: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 09:59:17 -0000 http://phk.freebsd.dk/misc/leapsecond.txt Notice how CLOCK_REALTIME recycles the 1136073599 second. Happy new-year! Poul-Henning -- 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. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 10:06:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B62AB16A41F for ; Sun, 1 Jan 2006 10:06:53 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from mail.neovanglist.net (blackacid.neovanglist.net [69.16.150.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5447643D5A for ; Sun, 1 Jan 2006 10:06:53 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from localhost (localhost.neovanglist.net [127.0.0.1]) by mail.neovanglist.net (Postfix) with ESMTP id F24AC6D43A for ; Sun, 1 Jan 2006 03:06:52 -0700 (MST) Received: from mail.neovanglist.net ([127.0.0.1]) by localhost (blackacid.neovanglist.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13437-04 for ; Sun, 1 Jan 2006 03:06:51 -0700 (MST) Received: from melchior (0x5358bc07.bynxx15.adsl-dhcp.tele.dk [83.88.188.7]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.neovanglist.net (Postfix) with ESMTP id BE6A96D438 for ; Sun, 1 Jan 2006 03:06:50 -0700 (MST) From: Chris Gilbert To: freebsd-current@freebsd.org Date: Sun, 1 Jan 2006 11:06:44 +0100 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> In-Reply-To: <73774.1136109554@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601011106.44615.Chris@lainos.org> X-Virus-Scanned: amavisd-new at neovanglist.net Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 10:06:53 -0000 Another potential timekeeping disaster averted. Now we wait for 2012... In any case, glad to see everything is working as it should, great work! (I know from your website that you are into all of that crazy stratum-1 stuff :) Oh and happy new year! (Things were freaking crazy in Kbh this year!!) By the way, if it's of any interest I worked with Line Bundgaard until she moved onto another company recently. (I believe she said she worked with you at one point.) I see her every so often and can give her your regards if you like. :) On Sunday 01 January 2006 10:59, Poul-Henning Kamp wrote: > http://phk.freebsd.dk/misc/leapsecond.txt > > Notice how CLOCK_REALTIME recycles the 1136073599 second. > > Happy new-year! > > Poul-Henning From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 10:08:58 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CE4A16A41F for ; Sun, 1 Jan 2006 10:08:58 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from mail.neovanglist.net (blackacid.neovanglist.net [69.16.150.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9734243D5E for ; Sun, 1 Jan 2006 10:08:57 +0000 (GMT) (envelope-from Chris@lainos.org) Received: from localhost (localhost.neovanglist.net [127.0.0.1]) by mail.neovanglist.net (Postfix) with ESMTP id 4ABDA6D43A; Sun, 1 Jan 2006 03:08:57 -0700 (MST) Received: from mail.neovanglist.net ([127.0.0.1]) by localhost (blackacid.neovanglist.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13437-05; Sun, 1 Jan 2006 03:08:55 -0700 (MST) Received: from melchior (0x5358bc07.bynxx15.adsl-dhcp.tele.dk [83.88.188.7]) (using SSLv3 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by mail.neovanglist.net (Postfix) with ESMTP id 6187B6D438; Sun, 1 Jan 2006 03:08:55 -0700 (MST) From: Chris Gilbert To: Poul-Henning Kamp , freebsd-current@freebsd.org Date: Sun, 1 Jan 2006 11:08:48 +0100 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> <200601011106.44615.Chris@lainos.org> In-Reply-To: <200601011106.44615.Chris@lainos.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601011108.49648.Chris@lainos.org> X-Virus-Scanned: amavisd-new at neovanglist.net Cc: Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 10:08:58 -0000 Crap, crap, crap! this was supposed to go to phk not the list :) (That will teach me for using a dodgy gui mail client!) Sorry for the noise... and happy new year :) On Sunday 01 January 2006 11:06, Chris Gilbert wrote: > Another potential timekeeping disaster averted. Now we wait for 2012... > > In any case, glad to see everything is working as it should, great work! > > (I know from your website that you are into all of that crazy stratum-1 > stuff :) > > Oh and happy new year! (Things were freaking crazy in Kbh this year!!) > > By the way, if it's of any interest I worked with Line Bundgaard until she > moved onto another company recently. (I believe she said she worked with > you at one point.) I see her every so often and can give her your regards > if you like. :) > > On Sunday 01 January 2006 10:59, Poul-Henning Kamp wrote: > > http://phk.freebsd.dk/misc/leapsecond.txt > > > > Notice how CLOCK_REALTIME recycles the 1136073599 second. > > > > Happy new-year! > > > > Poul-Henning From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 10:09:05 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AE3F16A41F for ; Sun, 1 Jan 2006 10:09:05 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id F150B43D4C for ; Sun, 1 Jan 2006 10:09:04 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id C4EDCBC50; Sun, 1 Jan 2006 10:09:02 +0000 (UTC) To: Chris Gilbert From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 01 Jan 2006 11:06:44 +0100." <200601011106.44615.Chris@lainos.org> Date: Sun, 01 Jan 2006 11:09:01 +0100 Message-ID: <73819.1136110141@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 10:09:05 -0000 In message <200601011106.44615.Chris@lainos.org>, Chris Gilbert writes: >By the way, if it's of any interest I worked with Line Bundgaard until she >moved onto another company recently. (I believe she said she worked with you >at one point.) I see her every so often and can give her your regards if you >like. :) By all means say hi to her from me :-) -- 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. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 11:19:51 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94CEB16A41F for ; Sun, 1 Jan 2006 11:19:51 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail12.syd.optusnet.com.au (mail12.syd.optusnet.com.au [211.29.132.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7F6643D45 for ; Sun, 1 Jan 2006 11:19:50 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail12.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k01BJlmn001319 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 1 Jan 2006 22:19:48 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k01BJkHh043925; Sun, 1 Jan 2006 22:19:46 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k01BJjGD043924; Sun, 1 Jan 2006 22:19:45 +1100 (EST) (envelope-from pjeremy) Date: Sun, 1 Jan 2006 22:19:45 +1100 From: Peter Jeremy To: Poul-Henning Kamp Message-ID: <20060101111945.GA42228@cirb503493.alcatel.com.au> References: <73774.1136109554@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <73774.1136109554@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 11:19:51 -0000 On Sun, 2006-Jan-01 10:59:14 +0100, Poul-Henning Kamp wrote: >http://phk.freebsd.dk/misc/leapsecond.txt > >Notice how CLOCK_REALTIME recycles the 1136073599 second. Thank you (and others) for your efforts in getting FreeBSD to this point. I did find what appears to be two hosts that both held the leap indicator as "01", well after the leap second, until I unpeered them. My configuration is: firewall - 5.4-STABLE 3 internal hosts - 4.9, 6.0 and 7.0. All these systems peer each other. The firewall is additionally a client to a number of external servers (only 1 of which handled the leap second correctly). All my systems correctly handled the leap second. (Though I had to manually unconfig several external systems which failed to handle the leap second and threatened to compromise my clock by over-loading the false-ticker algorithm). My firewall reset the leap indicator bit at 0030 UTC and the 5.4 host reset it at about 0106 UTC. Neither the 6.0 nor 7.0 systems reset the leap bit until I unpeered them at 0500 UTC. I suspect that both systems saw the leap indicator bit in the NTP packets from each other and held each other's leap indicator set. Once I unpeered them, both reset their leap indicator bits. Happy New Year to all. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 11:27:47 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ED0516A41F for ; Sun, 1 Jan 2006 11:27:47 +0000 (GMT) (envelope-from lexa@wincmd.ru) Received: from kunnilinux.birulevo.net (kunnilinux.birulevo.net [195.54.208.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 219D343D55 for ; Sun, 1 Jan 2006 11:27:45 +0000 (GMT) (envelope-from lexa@wincmd.ru) Received: (qmail 3490 invoked by uid 210); 1 Jan 2006 14:27:44 +0300 Received: from 10.4.22.222 by kunnilinux (envelope-from , uid 201) with qmail-scanner-1.25st (clamdscan: 0.87.1/1219. spamassassin: 3.1.0. perlscan: 1.25st. Clear:RC:1(10.4.22.222):. Processed in 0.117649 secs); 01 Jan 2006 11:27:44 -0000 Received: from unknown (HELO ?192.0.0.1?) (10.4.22.222) by kunnilinux.birulevo.net with SMTP; 1 Jan 2006 14:27:44 +0300 Message-ID: <43B7BCB2.6000209@wincmd.ru> Date: Sun, 01 Jan 2006 14:27:46 +0300 From: Tarasov Alexey User-Agent: Thunderbird 1.5 (X11/20051110) MIME-Version: 1.0 To: Chris Gilbert , freebsd-current@freebsd.org References: <200512270449.41709.Chris@lainos.org> In-Reply-To: <200512270449.41709.Chris@lainos.org> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ATI on FreeBSD! FireGL Linux Driver Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 11:27:47 -0000 Hello Chris! I have some errors running you port of ATI driver: > This *is* a pre-release version *of* the X server *from* The X.Org Foundation. > It *is* *not* supported *in* *any* way. > Bugs may be filed *in* the bugzilla *at* http://bugs.freedesktop.org/. > *Select* the "xorg" product *for* bugs you find *in* this release. > *Before* reporting bugs *in* pre-release versions please check the > latest version *in* the X.Org Foundation CVS repository. > See http://wiki.x.org/wiki/CvsPage *for* CVS access instructions. > > X *Window* System Version 6.8.99.902 (6.9.0 RC 2) > Release Date: 09 November 2005 + cvs > X Protocol Version 11, Revision 0, Release 6.8.99.902 > Build Operating System: FreeBSD 7.0 i386 [ELF] > *Current* Operating System: FreeBSD amd64.lexasoft.birulevo.net 7.0-*CURRENT* FreeBSD 7.0-*CURRENT* /#8: Sun Dec 18 19:04:21 MSK 2005 lexa@amd64.lexasoft.birulevo.net:/usr/obj/usr/src/sys/Lexasoft i386/ > Build Date: 03 December 2005 > *Before* reporting problems, check http://wiki.X.Org > *to* make sure that you have the latest version. > Module Loader present > Markers: (/--) probed, (**) from config file, (==) default setting,/ > (++) *from* *command* *line*, (!!) notice, (II) informational, > (WW) warning, (EE) *error*, (NI) *not* implemented, (??) unknown. > (==) *Log* *file*: "/var/log/Xorg.0.log", Time: Sun Jan 1 14:19:26 2006 > (==) *Using* config *file*: "/etc/X11/xorg.conf" > (WW) fglrx: *No* matching Device section *for* instance (BusID PCI:1:0:1) found > Symbol vgaHWGetIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWUnlock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWSave *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWLock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWFreeHWRec *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol vgaHWGetIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWUnlock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWRestore *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWLock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol xf86FreeInt10 *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWGetHWRec *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol xf86InitInt10 *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmMap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbPictureInit *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol vgaHWGetIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWUnlock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWRestore *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWLock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol vgaHWGetIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWUnlock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWRestore *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWLock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol vgaHWGetIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWUnlock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWRestore *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWFreeHWRec *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol xf86FreeInt10 *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Required symbol vgaHWLock *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmMap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol DRIGetDeviceInfo *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmMap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmMap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmMap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmUnmap *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpGetMode *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpVendorId *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpDeviceId *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpRelease *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpEnable *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpSize *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol drmAgpBase *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol DRIGetDrawableInfo *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol __glXActiveScreens *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol fbGetWinPrivateIndex *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol xf86InterpretEDID *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > Symbol xf86PrintEDID *from* module /usr/X11R6/lib/modules/drivers/fglrx_drv.o *is* unresolved! > > Fatal server *error*: > Some required symbols were unresolved > > > Please consult the The X.Org Foundation support > *at* http://wiki.X.Org > *for* *help*. > Please also check the *log* *file* *at* "/var/log/Xorg.0.log" *for* additional information. > > X connection *to* :0.0 broken (explicit kill *or* server shutdown). System information: > uname -a > FreeBSD amd64.lexasoft.birulevo.net 7.0-CURRENT FreeBSD 7.0-CURRENT > #8: Sun Dec 18 19:04:21 MSK 2005 > lexa@amd64.lexasoft.birulevo.net:/usr/obj/usr/src/sys/Lexasoft i38 Kernel config: > machine i386 > makeoptions COPTFLAGS="-O2 -pipe -funroll-loops -ffast-math" > cpu I686_CPU > ident Lexasoft > > options SCHED_4BSD # 4BSD scheduler > options PREEMPTION # Enable kernel thread preemption > options INET # InterNETworking > options INET6 # IPv6 communications protocols > options FFS # Berkeley Fast Filesystem > options SOFTUPDATES # Enable FFS soft updates support > options UFS_ACL # Support for access control lists > options UFS_DIRHASH # Improve performance on big directories > options MD_ROOT # MD is a potential root device > options NFSCLIENT # Network Filesystem Client > options NFSSERVER # Network Filesystem Server > options NFS_ROOT # NFS usable as /, requires NFSCLIENT > options MSDOSFS # MSDOS Filesystem > options CD9660 # ISO 9660 Filesystem > options PROCFS # Process filesystem (requires PSEUDOFS) > options PSEUDOFS # Pseudo-filesystem framework > options GEOM_GPT # GUID Partition Tables. > options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] > options COMPAT_FREEBSD4 # Compatible with FreeBSD4 > options COMPAT_FREEBSD5 # Compatible with FreeBSD5 > options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI > options KTRACE # ktrace(1) support > options SYSVSHM # SYSV-style shared memory > options SYSVMSG # SYSV-style message queues > options SYSVSEM # SYSV-style semaphores > options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions > options KBD_INSTALL_CDEV # install a CDEV entry in /dev > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~128k to driver. > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > # output. Adds ~215k to driver. > options ADAPTIVE_GIANT # Giant mutex is adaptive. > > > options VESA > options SC_PIXEL_MODE > options SC_HISTORY_SIZE=1000 > > device drm # DRM core module required by DRM drivers > device radeondrm # ATI Radeon > > options IBCS2 > > options SPX_HACK > > > options COMPAT_LINUX > > > options COMPAT_AOUT > ) > options LINPROCFS > > > > options NETGRAPH > options NETGRAPH_ETHER > options NETGRAPH_BRIDGE > options NETGRAPH_SOCKET > > options NETGRAPH_BLUETOOTH # ng_bluetooth(4) > options NETGRAPH_BLUETOOTH_BT3C # ng_bt3c(4) > options NETGRAPH_BLUETOOTH_HCI # ng_hci(4) > options NETGRAPH_BLUETOOTH_L2CAP # ng_l2cap(4) > options NETGRAPH_BLUETOOTH_SOCKET # ng_btsocket(4) > options NETGRAPH_BLUETOOTH_UBT # ng_ubt(4) > options NETGRAPH_BLUETOOTH_UBTBCMFW # ubtbcmfw(4) > > > device sound > > options LIBICONV > > options NTFS #NT File System > options CD9660 #ISO 9660 filesystem > options CD9660_ICONV > options MSDOSFS_ICONV > options NTFS_ICONV > > device atapicam # emulate ATAPI devices as SCSI ditto via CAM > # needs CAM to be present (scbus & pass) > > device tap #Virtual Ethernet driver > > # Bus support. Do not remove isa, even if you have no isa slots > device isa > device eisa > device pci > > # Floppy drives > device fdc > > # ATA and ATAPI devices > device ata > device atadisk # ATA disk drives > device ataraid # ATA RAID drives > device atapicd # ATAPI CDROM drives > device atapifd # ATAPI floppy drives > device atapist # ATAPI tape drives > options ATA_STATIC_ID # Static device numbering > > # SCSI peripherals > device scbus # SCSI bus (required for SCSI) > device ch # SCSI media changers > device da # Direct Access (disks) > device sa # Sequential Access (tape etc) > device cd # CD > device pass # Passthrough device (direct SCSI access) > device ses # SCSI Environmental Services (and SAF-TE) > > # RAID controllers > device aac # Adaptec FSA RAID > device aacp # SCSI passthrough for aac (requires CAM) > device ida # Compaq Smart RAID > device mlx # Mylex DAC960 family > device pst # Promise Supertrak SX6000 > device twe # 3ware ATA RAID > > # atkbdc0 controls both the keyboard and the PS/2 mouse > device atkbdc # AT keyboard controller > device atkbd # AT keyboard > device psm # PS/2 mouse > > device vga # VGA video card driver > > device splash # Splash screen and screen saver support > > device sc > > > device agp # support several AGP chipsets > > > device npx > > device pmtimer > > device cbb # cardbus (yenta) bridge > device pccard # PC Card (16-bit) bus > device cardbus # CardBus (32-bit) bus > > # 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 > > > device miibus # MII bus support > device sk # SysKonnect SK-984x & SK-982x gigabit Ethernet > > > # Wireless NIC cards > device wlan # 802.11 support > device an # Aironet 4500/4800 802.11 wireless NICs. > device awi # BayStack 660 and others > device ral # Ralink Technology RT2500 wireless NICs. > device wi # WaveLAN/Intersil/Symbol 802.11 wireless NICs. > #device wl # Older non 802.11 Wavelan wireless NIC. > > # Pseudo devices. > device loop # Network loopback > device mem # Memory and kernel memory devices > device io # I/O device > device random # Entropy device > device ether # Ethernet support > device sl # Kernel SLIP > device ppp # Kernel PPP > device tun # Packet tunnel. > device pty # Pseudo-ttys (telnet etc) > device md # Memory "disks" > device gif # IPv6 and IPv4 tunneling > device faith # IPv6-to-IPv4 relaying (translation) > > # The `bpf' device enables the Berkeley Packet Filter. > # Be aware of the administrative consequences of enabling this! > # Note that 'bpf' is required for DHCP. > device bpf # Berkeley packet filter > > # USB support > device uhci # UHCI PCI->USB interface > device ohci # OHCI PCI->USB interface > device ehci # EHCI PCI->USB interface (USB 2.0) > 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 ural # Ralink Technology RT2500USB wireless NICs > device urio # Diamond Rio 500 MP3 player > device uscanner # Scanners > # USB Ethernet, requires miibus > device aue # ADMtek USB Ethernet > device axe # ASIX Electronics USB Ethernet > device cdce # Generic USB over Ethernet > device cue # CATC USB Ethernet > device kue # Kawasaki LSI USB Ethernet > device rue # RealTek RTL8150 USB Ethernet > > # FireWire support > device firewire # FireWire bus code > device sbp # SCSI over FireWire (Requires scbus and da) > device fwe # Ethernet over FireWire (non-standard!) > Device lines in xorg.conf are copied from your "README" file. Thanks, -- Best regards, Tarasov Alexey. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 12:00:05 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51DAB16A41F for ; Sun, 1 Jan 2006 12:00:05 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4C2943D48 for ; Sun, 1 Jan 2006 12:00:04 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.11/8.12.11) with ESMTP id k01Bxx1f086328; Sun, 1 Jan 2006 03:59:59 -0800 (PST) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.11/8.12.3/Submit) id k01Bxwmn086327; Sun, 1 Jan 2006 03:59:58 -0800 (PST) (envelope-from rizzo) Date: Sun, 1 Jan 2006 03:59:58 -0800 From: Luigi Rizzo To: Poul-Henning Kamp Message-ID: <20060101035958.A86264@xorpc.icir.org> References: <73774.1136109554@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <73774.1136109554@critter.freebsd.dk>; from phk@phk.freebsd.dk on Sun, Jan 01, 2006 at 10:59:14AM +0100 Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 12:00:05 -0000 On Sun, Jan 01, 2006 at 10:59:14AM +0100, Poul-Henning Kamp wrote: > > http://phk.freebsd.dk/misc/leapsecond.txt > > Notice how CLOCK_REALTIME recycles the 1136073599 second. on a related topic, any comments on this one ? Is this code that we could use ? http://www.dragonflybsd.org/docs/nanosleep/ happy new year luigi From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 14:06:21 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F81516A41F for ; Sun, 1 Jan 2006 14:06:21 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91DA743D48 for ; Sun, 1 Jan 2006 14:06:20 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id D2FD15D3D; Sun, 1 Jan 2006 09:06:19 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46000-05; Sun, 1 Jan 2006 09:06:16 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-122-227.ny325.east.verizon.net [68.161.122.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 5977E5CA3; Sun, 1 Jan 2006 09:06:16 -0500 (EST) Message-ID: <43B7E1EC.5090301@mac.com> Date: Sun, 01 Jan 2006 09:06:36 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Luigi Rizzo References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> In-Reply-To: <20060101035958.A86264@xorpc.icir.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 14:06:21 -0000 Luigi Rizzo wrote: > On Sun, Jan 01, 2006 at 10:59:14AM +0100, Poul-Henning Kamp wrote: >>http://phk.freebsd.dk/misc/leapsecond.txt >> >>Notice how CLOCK_REALTIME recycles the 1136073599 second. > > on a related topic, any comments on this one ? > Is this code that we could use ? > > http://www.dragonflybsd.org/docs/nanosleep/ I ported the tvtohz change from Dragonfly back to 4.10 and 5-STABLE here: http://www.pkix.net/~chuck/timer/ ...so anyone who wants to experiment can try it out. :-) -- -Chuck From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 16:43:44 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D94516A41F; Sun, 1 Jan 2006 16:43:44 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E41C43D58; Sun, 1 Jan 2006 16:43:39 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [80.177.232.250]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id k01GhbK1048103; Sun, 1 Jan 2006 16:43:37 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 1 Jan 2006 16:43:34 +0000 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> In-Reply-To: <73774.1136109554@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601011643.35578.dfr@nlsystems.com> X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.87.1/1219/Wed Dec 28 22:57:59 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 16:43:44 -0000 On Sunday 01 January 2006 09:59, Poul-Henning Kamp wrote: > http://phk.freebsd.dk/misc/leapsecond.txt > > Notice how CLOCK_REALTIME recycles the 1136073599 second. > > Happy new-year! Mmmmm... Leap seconds... I can hear Warner grinding his teeth from here :-) From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 16:43:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D94516A41F; Sun, 1 Jan 2006 16:43:44 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E41C43D58; Sun, 1 Jan 2006 16:43:39 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [80.177.232.250]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id k01GhbK1048103; Sun, 1 Jan 2006 16:43:37 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Sun, 1 Jan 2006 16:43:34 +0000 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> In-Reply-To: <73774.1136109554@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601011643.35578.dfr@nlsystems.com> X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.87.1/1219/Wed Dec 28 22:57:59 2005 on itchy.rabson.org X-Virus-Status: Clean Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 16:43:44 -0000 On Sunday 01 January 2006 09:59, Poul-Henning Kamp wrote: > http://phk.freebsd.dk/misc/leapsecond.txt > > Notice how CLOCK_REALTIME recycles the 1136073599 second. > > Happy new-year! Mmmmm... Leap seconds... I can hear Warner grinding his teeth from here :-) From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 18:19:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9824716A41F; Sun, 1 Jan 2006 18:19:20 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADABE43D58; Sun, 1 Jan 2006 18:19:19 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id k01IMSPx017972; Sun, 1 Jan 2006 18:22:28 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id k01IMSL5017971; Sun, 1 Jan 2006 18:22:28 GMT (envelope-from dunstan) Date: Sun, 1 Jan 2006 18:22:27 +0000 From: "Wojciech A. Koszek" To: Richard Todd Message-ID: <20060101182227.GB17837@FreeBSD.czest.pl> References: <20051221031526.31ABC290@mx2.synetsystems.com> <200512211111.44268.jhb@freebsd.org> <20051227173434.GA53513@FreeBSD.czest.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, rwatson@freebsd.org Subject: Re: Bug in latest rev kern_acct.c: panic: Trying sleep, but thread marked as sleeping prohibited X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 18:19:20 -0000 On Sat, Dec 31, 2005 at 06:39:31PM -0600, Richard Todd wrote: > "Wojciech A. Koszek" writes: > > > On Wed, Dec 21, 2005 at 11:11:43AM -0500, John Baldwin wrote: > >> acctwatch() probably isn't a good thing to do from a callout since it wants to > >> do VOPs and such. Probably the easiest fix is to stick acctwatch() in its > >> own kthread. > > > > I think I didn't break current behaviour. Patch is here: > > > > http://freebsd.czest.pl/dunstan/FreeBSD/kern_acct.0.patch > > > > Richard, could you try to repeat your problem with my patch? > > Got a chance to try a new kernel today with your patch. I tried to reproduce > the panic by repeatedly copying a bunch of stuff onto /usr and deleting it > in one window, and in another repeatedly doing "make configure; make clean" > in one rather large port. Lots of "Accounting suspended/resumed" messages > in the logs and no panics. So it's looking good from here. Thanks for testing this. I couldn't crash my box either. I belive that KASSERT() before suspend/resume handling will always be true, just like ACCT_ENABLED state. In the final version of the patch I'll include some cosmetic changes suggested by Robert Watson (thanks!). -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 19:50:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C64116A420 for ; Sun, 1 Jan 2006 19:50:08 +0000 (GMT) (envelope-from pbowen@fastmail.fm) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3884D43D7D for ; Sun, 1 Jan 2006 19:49:58 +0000 (GMT) (envelope-from pbowen@fastmail.fm) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id D23E5D2E2AA for ; Sun, 1 Jan 2006 14:49:56 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Sun, 01 Jan 2006 14:49:56 -0500 X-Sasl-enc: E4pE6sPr/enkj+WPBnsH4RB4IcZmPckdl+19eDFyHScf 1136144995 Received: from [192.168.205.79] (unknown [12.109.105.194]) by frontend2.messagingengine.com (Postfix) with ESMTP id C408C571482 for ; Sun, 1 Jan 2006 14:49:55 -0500 (EST) Message-ID: <43B83262.1090907@fastmail.fm> Date: Sun, 01 Jan 2006 13:49:54 -0600 From: Patrick Bowen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: multipart/mixed; boundary="------------090708090503060709080407" Subject: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 19:50:08 -0000 This is a multi-part message in MIME format. --------------090708090503060709080407 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Hello and Happy New Year; I just bought a D-Link DWL-G630 Wireless G Adapter for my laptop (Dell Latitude C-600), and it worked fine until I cvsup'ed last nights sources (12/31/05) and did canonical rebuild. Now the machine panics whenever I plug the card in. sg1# uname -a FreeBSD sg1.sgc.org 7.0-CURRENT FreeBSD 7.0-CURRENT #3: Sun Jan 1 10:51:32 CST 2006 pbowen@sg1.sgc.org:/usr/obj/usr/src/sys/GENERIC i386 I've included dmesg as attachment. sg1# kgdb kernel.debug /var/crash/vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0xd6975000 fault code = supervisor read, page not present instruction pointer = 0x20:0xc04fc2a8 stack pointer = 0x28:0xd4497748 frame pointer = 0x28:0xd4497754 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 = 22 (cbb1) panic: from debugger cpuid = 0 Uptime: 40s Dumping 511 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 511MB (130779 pages) 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:166 166 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) list *0xc04fc2a8 0xc04fc2a8 is in cardbus_read_tuple_mem (bus.h:225). 220 bus_size_t offset) 221 { 222 223 if (tag == I386_BUS_SPACE_IO) 224 return (inb(handle + offset)); 225 return (*(volatile u_int8_t *)(handle + offset)); 226 } 227 228 static __inline u_int16_t 229 bus_space_read_2(bus_space_tag_t tag, bus_space_handle_t handle, (kgdb) bt #0 doadump () at pcpu.h:166 #1 0xc06539f8 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc0653d0d in panic (fmt=0xc08493c3 "from debugger") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc046a7c1 in db_panic (addr=-1068514648, have_addr=0, count=-1, modif=0xd4497518 "") at /usr/src/sys/ddb/db_command.c:435 #4 0xc046a758 in db_command (last_cmdp=0xc0933d84, cmd_table=0x0, aux_cmd_tablep=0xc08ad950, aux_cmd_tablep_end=0xc08ad96c) at /usr/src/sys/ddb/db_command.c:404 #5 0xc046a820 in db_command_loop () at /usr/src/sys/ddb/db_command.c:455 #6 0xc046c439 in db_trap (type=12, code=0) at /usr/src/sys/ddb/db_main.c:221 #7 0xc066e134 in kdb_trap (type=12, code=0, tf=0xd4497708) at /usr/src/sys/kern/subr_kdb.c:485 #8 0xc0813aac in trap_fatal (frame=0xd4497708, eva=3600240640) at /usr/src/sys/i386/i386/trap.c:853 #9 0xc08137ef in trap_pfault (frame=0xd4497708, usermode=0, eva=3600240640) at /usr/src/sys/i386/i386/trap.c:770 #10 0xc0813409 in trap (frame= {tf_fs = -1019150328, tf_es = -2013265880, tf_ds = -733413336, tf_edi = 20480, tf_esi = 1, tf_ebp = -733382828, tf_isp = -733382860, tf_ebx = -733382736, tf_edx = -694747136, tf_ecx = -694747136, tf_eax = 20480, tf_trapno = 12, tf_err = 0, tf_eip = -1068514648, tf_cs = 32, tf_eflags = 590338, tf_esp = -73338273 2, tf_ss = -733382736}) at /usr/src/sys/i386/i386/trap.c:455 #11 0xc07ffb1a in calltrap () at /usr/src/sys/i386/i386/exception.s:137 #12 0xc04fc2a8 in cardbus_read_tuple_mem (cbdev=0xc341c180, res=0xd44977b0, start=20480, off=0xd44977b0, tupleid=0x5000, len=0xd44977b8, tupledata=0xd44977c4 "") at bus.h:224 #13 0xc04fc35e in cardbus_read_tuple (cbdev=0xc341c180, child=0xc37f6800, res=0xd6970000, start=20480, off=0xd44977b0, tupleid=0xd44977b4, len=0xd6970000, tupledata=0x5000
) at /usr/src/sys/dev/cardbus/cardbus_cis.c:460 #14 0xc04fc9ec in cardbus_parse_cis (cbdev=0xc341c180, child=0xc37f6800, callbacks=0xd4497bf4, argp=0x0) at /usr/src/sys/dev/cardbus/cardbus_cis.c:647 #15 0xc04fcaa2 in cardbus_do_cis (cbdev=0xc341c180, child=0xc37f6800) at /usr/src/sys/dev/cardbus/cardbus_cis.c:693 #16 0xc04fb5e8 in cardbus_attach_card (cbdev=0xc341c180) at /usr/src/sys/dev/cardbus/cardbus.c:195 #17 0xc058a3ee in cbb_insert (sc=0xc33e0000) at card_if.h:82 #18 0xc058a21d in cbb_event_thread (arg=0xc33e0000) at /usr/src/sys/dev/pccbb/pccbb.c:507 #19 0xc063fd74 in fork_exit (callout=0xc058a0f4 , arg=0xc33e0000, frame=0xd4497d38) at /usr/src/sys/kern/kern_fork.c:790 #20 0xc07ffb7c in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:198 (kgdb) q sg1# I'm not at the point where I can tell exactly what the problen is, but the "out of bounds" at #13 looks suspect to me. Can anyone tell me whats going wrong here? Thanks, Patrick --------------090708090503060709080407 Content-Type: text/plain; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2006 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 7.0-CURRENT #3: Sun Jan 1 10:51:32 CST 2006 pbowen@sg1.sgc.org:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (751.71-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 536719360 (511 MB) avail memory = 515596288 (491 MB) ath_hal: 0.9.14.9 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413) npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 battery1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xec00-0xecff mem 0xf8000000-0xfbffffff,0xfdffc000-0xfdffffff irq 11 at device 0.0 on pci1 cbb0: at device 3.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: at device 3.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x860-0x86f at device 7.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xdce0-0xdcff irq 11 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) pcm0: port 0xd800-0xd8ff mem 0xf3ffe000-0xf3ffffff irq 5 at device 8.0 on pci0 pcm0: xl0: <3Com 3c556 Fast Etherlink XL> port 0xd400-0xd4ff mem 0xf3ffdc00-0xf3ffdc7f,0xf3ffd800-0xf3ffd87f irq 11 at device 16.0 on pci0 miibus0: on xl0 tdkphy0: on miibus0 tdkphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:48:c7:b2 pci0: at device 16.1 (no driver attached) acpi_tz0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 ppi0: on ppbus0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port pmtimer0 on isa0 orm0: at iomem 0xc0000-0xcffff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 751707939 Hz quality 800 Timecounters tick every 1.000 msec ad0: 19077MB at ata0-master UDMA33 acd0: CDRW at ata1-master PIO4 Trying to mount root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted wi0: at port 0x100-0x13f irq 11 function 0 config 1 on pccard0 wi0: using RF:PRISM2.5 MAC:ISL3873 wi0: Intersil Firmware: Primary (1.1.0), Station (1.4.9) wi0: Ethernet address: 00:04:e2:80:34:be --------------090708090503060709080407-- From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 21:18:04 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0AB4E16A41F for ; Sun, 1 Jan 2006 21:18:04 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52A4143D5A for ; Sun, 1 Jan 2006 21:18:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k01LHi4S097346; Sun, 1 Jan 2006 14:17:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 14:17:47 -0700 (MST) Message-Id: <20060101.141747.125947927.imp@bsdimp.com> To: PeterJeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20060101111945.GA42228@cirb503493.alcatel.com.au> References: <73774.1136109554@critter.freebsd.dk> <20060101111945.GA42228@cirb503493.alcatel.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 14:17:45 -0700 (MST) Cc: phk@phk.freebsd.dk, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 21:18:04 -0000 In message: <20060101111945.GA42228@cirb503493.alcatel.com.au> Peter Jeremy writes: : On Sun, 2006-Jan-01 10:59:14 +0100, Poul-Henning Kamp wrote: : >http://phk.freebsd.dk/misc/leapsecond.txt : > : >Notice how CLOCK_REALTIME recycles the 1136073599 second. : : Thank you (and others) for your efforts in getting FreeBSD to this point. : : I did find what appears to be two hosts that both held the leap : indicator as "01", well after the leap second, until I unpeered them. That's OK. The 'ins' indicator is only used on June 30 and December 31. The leap second indicators will stay on as long as the up-stream servers have them turned on. Also, there's a 1024 second polling interval to consider, which can make the indicator persist for hours depending on the network topology, etc. : My firewall reset the leap indicator bit at 0030 UTC and the 5.4 host : reset it at about 0106 UTC. Neither the 6.0 nor 7.0 systems reset the : leap bit until I unpeered them at 0500 UTC. I suspect that both : systems saw the leap indicator bit in the NTP packets from each other : and held each other's leap indicator set. Once I unpeered them, both : reset their leap indicator bits. To be pedantic about what NTP does, it will keep the leap bit on so long as at least one of the peers with a lower stratum has its bit on. As I said above, it doesn't matter until June sometime. Yes, the June and December dates are hard wired into ntpd. The primary times are June 30 and December 31. The backup dates are March 31, September 30, but very few things implement those dates at all (more devices implement a more generic 'do leap second at the end of DOY #xxx). There won't be leap seconds on the alternative dates for at least tens of years (2030 to 2050 were the time frames that 2x year leap seconds won't be enough in projections that I've seen). Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 21:24:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B3AA16A420; Sun, 1 Jan 2006 21:24:28 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91E9E43D7C; Sun, 1 Jan 2006 21:24:26 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k01LNYoe097389; Sun, 1 Jan 2006 14:23:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 14:23:37 -0700 (MST) Message-Id: <20060101.142337.33509370.imp@bsdimp.com> To: dfr@nlsystems.com From: "M. Warner Losh" In-Reply-To: <200601011643.35578.dfr@nlsystems.com> References: <73774.1136109554@critter.freebsd.dk> <200601011643.35578.dfr@nlsystems.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 14:23:35 -0700 (MST) Cc: phk@phk.freebsd.dk, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 21:24:28 -0000 In message: <200601011643.35578.dfr@nlsystems.com> Doug Rabson writes: : On Sunday 01 January 2006 09:59, Poul-Henning Kamp wrote: : > http://phk.freebsd.dk/misc/leapsecond.txt : > : > Notice how CLOCK_REALTIME recycles the 1136073599 second. : > : > Happy new-year! : : Mmmmm... Leap seconds... I can hear Warner grinding his teeth from : here :-) Having experienced on has not changed my deep, and abiding feelings for leapseconds in the least. I've spent about 120 hours on leap seconds in the past couple of years. For something so damn simple, these are a huge pita. Most of the time has been determining what real devices will do over a leap second, which information is reliable and which information lags and how. There's too damn many variables to know what information you can rely on and what information you have to 'filter' and how. You can make the data streams more reliable at the cost of code complexity and inflexibility. I guess that's a long way of saying that I hate Leap Seconds. They are too damn complicated for such a simple concept :-( Wanrer From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 21:24:28 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B3AA16A420; Sun, 1 Jan 2006 21:24:28 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91E9E43D7C; Sun, 1 Jan 2006 21:24:26 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k01LNYoe097389; Sun, 1 Jan 2006 14:23:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 14:23:37 -0700 (MST) Message-Id: <20060101.142337.33509370.imp@bsdimp.com> To: dfr@nlsystems.com From: "M. Warner Losh" In-Reply-To: <200601011643.35578.dfr@nlsystems.com> References: <73774.1136109554@critter.freebsd.dk> <200601011643.35578.dfr@nlsystems.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 14:23:35 -0700 (MST) Cc: phk@phk.freebsd.dk, freebsd-current@freebsd.org, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 21:24:28 -0000 In message: <200601011643.35578.dfr@nlsystems.com> Doug Rabson writes: : On Sunday 01 January 2006 09:59, Poul-Henning Kamp wrote: : > http://phk.freebsd.dk/misc/leapsecond.txt : > : > Notice how CLOCK_REALTIME recycles the 1136073599 second. : > : > Happy new-year! : : Mmmmm... Leap seconds... I can hear Warner grinding his teeth from : here :-) Having experienced on has not changed my deep, and abiding feelings for leapseconds in the least. I've spent about 120 hours on leap seconds in the past couple of years. For something so damn simple, these are a huge pita. Most of the time has been determining what real devices will do over a leap second, which information is reliable and which information lags and how. There's too damn many variables to know what information you can rely on and what information you have to 'filter' and how. You can make the data streams more reliable at the cost of code complexity and inflexibility. I guess that's a long way of saying that I hate Leap Seconds. They are too damn complicated for such a simple concept :-( Wanrer From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 21:33:04 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB92016A41F for ; Sun, 1 Jan 2006 21:33:04 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E01643D48 for ; Sun, 1 Jan 2006 21:33:04 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k01LUXkS097465; Sun, 1 Jan 2006 14:30:33 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 14:30:36 -0700 (MST) Message-Id: <20060101.143036.06971801.imp@bsdimp.com> To: pbowen@fastmail.fm From: "M. Warner Losh" In-Reply-To: <43B83262.1090907@fastmail.fm> References: <43B83262.1090907@fastmail.fm> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 14:30:34 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 21:33:04 -0000 I'll take a look with my atheros cards. I just committed a major simplification of the resource code. This fixed a number of other cards, but might have broken something in the CIS parsing for this card. The different CIS structures are kept in different places on different cards. I'll investigate. Warner From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 22:56:31 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFFA216A41F; Sun, 1 Jan 2006 22:56:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323BA43D5C; Sun, 1 Jan 2006 22:56:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id A9EC1BC50; Sun, 1 Jan 2006 22:56:30 +0000 (UTC) To: "M. Warner Losh" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 01 Jan 2006 14:23:37 MST." <20060101.142337.33509370.imp@bsdimp.com> Date: Sun, 01 Jan 2006 23:56:29 +0100 Message-ID: <75804.1136156189@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 22:56:32 -0000 In message <20060101.142337.33509370.imp@bsdimp.com>, "M. Warner Losh" writes: >I guess that's a long way of saying that I hate Leap Seconds. They >are too damn complicated for such a simple concept :-( Seconded. -- 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. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 22:56:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFFA216A41F; Sun, 1 Jan 2006 22:56:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323BA43D5C; Sun, 1 Jan 2006 22:56:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id A9EC1BC50; Sun, 1 Jan 2006 22:56:30 +0000 (UTC) To: "M. Warner Losh" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Sun, 01 Jan 2006 14:23:37 MST." <20060101.142337.33509370.imp@bsdimp.com> Date: Sun, 01 Jan 2006 23:56:29 +0100 Message-ID: <75804.1136156189@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: freebsd-current@freebsd.org, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 22:56:32 -0000 In message <20060101.142337.33509370.imp@bsdimp.com>, "M. Warner Losh" writes: >I guess that's a long way of saying that I hate Leap Seconds. They >are too damn complicated for such a simple concept :-( Seconded. -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 02:20:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB40416A420; Mon, 2 Jan 2006 02:20:02 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6970E43D67; Mon, 2 Jan 2006 02:19:57 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id k022JtZS074027; Sun, 1 Jan 2006 21:19:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k022JtEd022584; Sun, 1 Jan 2006 21:19:55 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 5393F7302F; Sun, 1 Jan 2006 21:19:55 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060102021955.5393F7302F@freebsd-current.sentex.ca> Date: Sun, 1 Jan 2006 21:19:55 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 02:20:02 -0000 TB --- 2006-01-02 00:51:42 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-02 00:51:42 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-02 00:51:42 - cleaning the object tree TB --- 2006-01-02 00:52:03 - checking out the source tree TB --- 2006-01-02 00:52:03 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-02 00:52:03 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-02 00:58:02 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-02 00:58:02 - cd /src TB --- 2006-01-02 00:58:02 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries [...] /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:385: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:395: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:415: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:431: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:432: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:434: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:435: error: dereferencing pointer to incomplete type /src/kerberos5/lib/libgssapi/../../../crypto/heimdal/lib/gssapi/accept_sec_context.c:437: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /src/kerberos5/lib/libgssapi. *** Error code 1 Stop in /src/kerberos5/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-02 02:19:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-02 02:19:55 - ERROR: failed to build world TB --- 2006-01-02 02:19:55 - tinderbox aborted TB --- 0.87 user 4.27 system 5292.46 real From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 02:47:51 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 727B216A420 for ; Mon, 2 Jan 2006 02:47:51 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA7043D5A for ; Mon, 2 Jan 2006 02:47:49 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id k022ljpE006975; Sun, 1 Jan 2006 21:47:45 -0500 (EST) Date: Sun, 1 Jan 2006 21:47:45 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Patrick Bowen In-Reply-To: <43B83262.1090907@fastmail.fm> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: freebsd-current@freebsd.org Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 02:47:51 -0000 On Sun, 1 Jan 2006, Patrick Bowen wrote: > Hello and Happy New Year; > > I just bought a D-Link DWL-G630 Wireless G Adapter for my laptop (Dell > Latitude C-600), and it worked fine until I cvsup'ed last nights sources > (12/31/05) and did canonical rebuild. Now the machine panics whenever I > plug the card in. Same here, though I got the kernel panic at boot when I had inserted during the boot. The panic was in cardbus_read_tuple() also. I can post the hand scribed trace to anyone interested if necessary. -- DE From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 03:28:48 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 509D416A41F for ; Mon, 2 Jan 2006 03:28:48 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id EDFBD43D53 for ; Mon, 2 Jan 2006 03:28:47 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 43E3A225EE2 for ; Sun, 1 Jan 2006 19:28:47 -0800 (PST) Received: from [192.168.2.4] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id k023Skt4081221 for ; Sun, 1 Jan 2006 19:28:47 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <43B89DED.3060207@elischer.org> Date: Sun, 01 Jan 2006 19:28:45 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051120 X-Accept-Language: en, hu MIME-Version: 1.0 To: Current Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: size of /boot/kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 03:28:48 -0000 SO my system of about 2 weeks or so ago had a /boot/kernl for which du returned a value of ~19000K On rebuild and reinstall today my root filesystem filled up when the size of /boot/kernel passed 49203K and it wasn't anywhere near finished. Can someone put an UPDATING entry explaining why this happenned (there seems to now be a .symbols fir for every .ko that is much larger) and how to turn it off! thanks Julian From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 03:43:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B67516A41F for ; Mon, 2 Jan 2006 03:43:24 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DCB543D4C for ; Mon, 2 Jan 2006 03:43:24 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id DAD1B22F834 for ; Sun, 1 Jan 2006 19:43:23 -0800 (PST) Received: from [192.168.2.4] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id k023gj0f000558; Sun, 1 Jan 2006 19:42:46 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <43B8A135.6060505@elischer.org> Date: Sun, 01 Jan 2006 19:42:45 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051120 X-Accept-Language: en, hu MIME-Version: 1.0 To: Julian Elischer References: <43B89DED.3060207@elischer.org> In-Reply-To: <43B89DED.3060207@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Current Subject: Re: size of /boot/kernel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 03:43:24 -0000 Julian Elischer wrote: > SO my system of about 2 weeks or so ago had a /boot/kernl for which du > returned a value of ~19000K > > On rebuild and reinstall today my root filesystem filled up when the size > of /boot/kernel passed 49203K and it wasn't anywhere near finished. > > Can someone put an UPDATING entry explaining why this happenned > (there seems to now be a .symbols fir for every .ko that is much larger) > and how to turn it off! Answering myself it seems that you need to add -DINSTALL_NODEBUG to your install line (or maybe in /etc/make.conf?) if you don't want to blow out your root partition.. > > > thanks > > Julian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 04:29:02 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9461316A41F; Mon, 2 Jan 2006 04:29:02 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DE0743D4C; Mon, 2 Jan 2006 04:29:01 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k024PjbK002055; Sun, 1 Jan 2006 21:25:45 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 01 Jan 2006 21:25:52 -0700 (MST) Message-Id: <20060101.212552.85411680.imp@bsdimp.com> To: deischen@FreeBSD.ORG From: "M. Warner Losh" In-Reply-To: References: <43B83262.1090907@fastmail.fm> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 01 Jan 2006 21:25:45 -0700 (MST) Cc: pbowen@fastmail.fm, freebsd-current@FreeBSD.ORG Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 04:29:02 -0000 In message: Daniel Eischen writes: : On Sun, 1 Jan 2006, Patrick Bowen wrote: : : > Hello and Happy New Year; : > : > I just bought a D-Link DWL-G630 Wireless G Adapter for my laptop (Dell : > Latitude C-600), and it worked fine until I cvsup'ed last nights sources : > (12/31/05) and did canonical rebuild. Now the machine panics whenever I : > plug the card in. : : Same here, though I got the kernel panic at boot when I had inserted during : the boot. The panic was in cardbus_read_tuple() also. I can post the : hand scribed trace to anyone interested if necessary. No need. I have the card here, and it fails too. All my other cards work, but the atheros card is the only one that stores the CIS in a bar that I have (I'm sure that others do as well, but they aren't in the 10 cards I grabbed to test with). This appears to be resource related in some way, since it appears that we're getting a resource of '0' back. I'm trying to debug it now. Sorry for the hassle. Warner From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 06:52:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CDDF16A41F for ; Mon, 2 Jan 2006 06:52:10 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (skippyii.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF3743D45 for ; Mon, 2 Jan 2006 06:52:09 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id k026rT8i076481 for ; Mon, 2 Jan 2006 01:53:29 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: Date: Mon, 2 Jan 2006 01:53:03 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Subject: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 06:52:10 -0000 Just looking through the kernel code, and there are many strong warnings (in NOTES, GENERIC and various bits of code) that strongly advise *not* removing COMPAT_43 from the kernel config. In fact, doing so causes lots of things to break, especially the Linuxulator. That said, would COMPAT_43 (and possibly COMPAT_FREEBSD4 and COMPAT_FREEBSD5) be good candidates to put in DEFAULTS -- at least on i386? Regards, -- Matt Emmerton From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 07:18:45 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1182B16A41F; Mon, 2 Jan 2006 07:18:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E56B43D4C; Mon, 2 Jan 2006 07:18:44 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k027IgAb097876; Mon, 2 Jan 2006 02:18:42 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id k027IgfY081707; Mon, 2 Jan 2006 02:18:42 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3EB507302F; Mon, 2 Jan 2006 02:18:41 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060102071841.3EB507302F@freebsd-current.sentex.ca> Date: Mon, 2 Jan 2006 02:18:41 -0500 (EST) X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 07:18:45 -0000 TB --- 2006-01-02 06:26:46 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-02 06:26:46 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2006-01-02 06:26:46 - cleaning the object tree TB --- 2006-01-02 06:26:56 - checking out the source tree TB --- 2006-01-02 06:26:56 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2006-01-02 06:26:56 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-02 06:41:57 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-02 06:41:57 - cd /src TB --- 2006-01-02 06:41:57 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ng.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_nw.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_pr.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_sv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c: In function `getaddrinfo': /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:342: error: structure has no member named `_ai_pad' /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:373: error: structure has no member named `_ai_pad' *** Error code 1 Stop in /src/lib/bind/bind. *** Error code 1 Stop in /src/lib/bind. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-02 07:18:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-02 07:18:39 - ERROR: failed to build world TB --- 2006-01-02 07:18:39 - tinderbox aborted TB --- 0.40 user 1.76 system 3112.48 real From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 07:51:45 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F253D16A41F; Mon, 2 Jan 2006 07:51:44 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ABC143D55; Mon, 2 Jan 2006 07:51:44 +0000 (GMT) (envelope-from danny@cs.huji.ac.il) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by cs1.cs.huji.ac.il with esmtp id 1EtKTm-0002vl-Ku; Mon, 02 Jan 2006 09:51:42 +0200 X-Mailer: exmh version 2.7.0 06/18/2004 with nmh-1.0.4 To: Dario Freni In-reply-to: Your message of Thu, 29 Dec 2005 17:07:34 +0100 . Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Jan 2006 09:51:42 +0200 From: Danny Braniss Message-ID: Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, daichi@freebsd.org Subject: Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 07:51:45 -0000 > Masanori OZAWA wrote: > [...] > > Nice work! This is just a "works for me". In only find some issues with > permissions that were already present in the previous implementation of > unionfs. Some of them are partially corrected in the "useful" copymode. > I mailed the details to the author. the following will hang the kernel: root is mounted nfs, /etc is unionfs'ed so: from /etc/rc.initdiskless: ... # Create a generic memory disk # mount_md() { /sbin/mdmfs -i 4096 -s $1 -M md $2 } kldload unionfs mount_md 4096 /.etc mount_unionfs /.etc /etc ... and now: cd /etc mv some-file somefile and now the system is stuck. this behaviour is also present in the unpatched unionfs, but would be nice if it can be fixed. danny ps: see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84107 From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 10:12:04 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A7BF16A41F for ; Mon, 2 Jan 2006 10:12:04 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B11A43D5A for ; Mon, 2 Jan 2006 10:12:02 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id k02ABwcY064626 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 2 Jan 2006 11:11:58 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id k02ABvsP064624; Mon, 2 Jan 2006 11:11:57 +0100 (CET) Date: Mon, 2 Jan 2006 11:11:57 +0100 From: Divacky Roman To: Matt Emmerton Message-ID: <20060102101157.GA63949@stud.fit.vutbr.cz> References: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: current@freebsd.org Subject: Re: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 10:12:04 -0000 On Mon, Jan 02, 2006 at 01:53:03AM -0500, Matt Emmerton wrote: > Just looking through the kernel code, and there are many strong warnings (in > NOTES, GENERIC and various bits of code) that strongly advise *not* removing > COMPAT_43 from the kernel config. > > In fact, doing so causes lots of things to break, especially the > Linuxulator. > > That said, would COMPAT_43 (and possibly COMPAT_FREEBSD4 and > COMPAT_FREEBSD5) be good candidates to put in DEFAULTS -- at least on i386? I have patch in queue which removes dependancy of linuxator on COMPAT_43 (hysteria.sk/~neologism/linux43.patch) - its tested on amd64/i386 but havent tried alpha (not even building it - anyone willing to test this?) and I plan to work to split COMPAT_43 into whats necessary for tty stuff and the rest. after this we can remove COMPAT_43 from even GENERIC imho. I dont think that moving in the direction you suggest is correct. roman From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 10:16:58 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57DDC16A41F for ; Mon, 2 Jan 2006 10:16:58 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47EF543D64 for ; Mon, 2 Jan 2006 10:16:57 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id k02AGrT5065322 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Mon, 2 Jan 2006 11:16:53 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id k02AGrxI065321 for current@freebsd.org; Mon, 2 Jan 2006 11:16:53 +0100 (CET) Date: Mon, 2 Jan 2006 11:16:53 +0100 From: Divacky Roman To: current@freebsd.org Message-ID: <20060102101653.GA65178@stud.fit.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: Subject: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 10:16:58 -0000 Hi after booting new kernel I got this: witten ~# sysctl vm.stats.pagequeue vm.stats.pagequeue.prime2: 5 vm.stats.pagequeue.prime1: 9 vm.stats.pagequeue.cachenways: 0 vm.stats.pagequeue.cachesize: 0 vm.stats.pagequeue.page_colors: 32 my CPU is: CPU: AMD Athlon(tm) XP 2500+ (1834.88-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc0400800 I am willing/ready to test any patches you provide :) roman From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 11:09:30 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B72916A41F for ; Mon, 2 Jan 2006 11:09:30 +0000 (GMT) (envelope-from netchild@FreeBSD.org) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id D671943D78 for ; Mon, 2 Jan 2006 11:09:16 +0000 (GMT) (envelope-from netchild@FreeBSD.org) Received: from Andro-Beta.Leidinger.net (p54A5F5E3.dip.t-dialin.net [84.165.245.227]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02B5FJR068849; Mon, 2 Jan 2006 12:05:15 +0100 (CET) (envelope-from netchild@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02B8kIQ098610; Mon, 2 Jan 2006 12:08:46 +0100 (CET) (envelope-from netchild@FreeBSD.org) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 12:08:45 +0100 Message-ID: <20060102120845.ec93s6hb4gk8gk4c@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 12:08:45 +0100 From: Alexander Leidinger To: Kent Stewart References: <200512301955.jBUJtto5078174@repoman.freebsd.org> <200601011220.46770.kstewart@owt.com> In-Reply-To: <200601011220.46770.kstewart@owt.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: current@FreeBSD.org Subject: strange cvsweb display (was: Re: cvs commit: src UPDATING src/sys/conf NOTES files src/sys/boot/forth loader.conf src/sys/sys soundcard.h src/sys/dev/sound driver.c src/sys/dev/sound/isa ad1816.c ess.c mss.c sb16.c sb8.c sbc.c src/sys/dev/sound/pci als4000.c atiixp.c ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 11:09:30 -0000 Kent Stewart wrote: [CCing current@] > On Friday 30 December 2005 11:55 am, you wrote: >> netchild 2005-12-30 19:55:55 UTC >> >> FreeBSD src repository >> >> Modified files: (Branch: RELENG_6) >> . UPDATING >> sys/conf NOTES files > >> Revision Changes Path >> 1.416.2.12 +5 -0 src/UPDATING > > Something strange is going on with the mods to UPDATING. If you use > cvsweb to look at the history, only your BP change shows up and none of > the December mods can be viewed. When you cvsup RELENG_6, they are in > the downloaded src. I can confirm that only the branch point entry of RELENG_6 is visible in cvsweb. Does anyone out there knows the reason for this? Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 BOFH excuse #1: clock speed From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 13:07:23 2006 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C8C816A41F; Mon, 2 Jan 2006 13:07:23 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: from eddie.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7303F43D69; Mon, 2 Jan 2006 13:07:18 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: by eddie.nitro.dk (Postfix, from userid 1000) id 254FC119C4F; Mon, 2 Jan 2006 14:07:17 +0100 (CET) Date: Mon, 2 Jan 2006 14:07:17 +0100 From: "Simon L. Nielsen" To: Alexander Leidinger Message-ID: <20060102130716.GD80845@eddie.nitro.dk> References: <200512301955.jBUJtto5078174@repoman.freebsd.org> <200601011220.46770.kstewart@owt.com> <20060102120845.ec93s6hb4gk8gk4c@netchild.homeip.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XvKFcGCOAo53UbWW" Content-Disposition: inline In-Reply-To: <20060102120845.ec93s6hb4gk8gk4c@netchild.homeip.net> User-Agent: Mutt/1.5.11 Cc: current@FreeBSD.org, Kent Stewart Subject: Re: strange cvsweb display (was: Re: cvs commit: src UPDATING src/sys/conf NOTES files src/sys/boot/forth loader.conf src/sys/sys soundcard.h src/sys/dev/sound driver.c src/sys/dev/sound/isa ad1816.c ess.c mss.c sb16.c sb8.c sbc.c src/sys/dev/sound/pci als4000.c atiixp.c ...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 13:07:23 -0000 --XvKFcGCOAo53UbWW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2006.01.02 12:08:45 +0100, Alexander Leidinger wrote: > Kent Stewart wrote: >=20 > [CCing current@] >=20 > >On Friday 30 December 2005 11:55 am, you wrote: > >>netchild 2005-12-30 19:55:55 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: (Branch: RELENG_6) > >> . UPDATING > >> sys/conf NOTES files > > > >> Revision Changes Path > >> 1.416.2.12 +5 -0 src/UPDATING > > > >Something strange is going on with the mods to UPDATING. If you use > >cvsweb to look at the history, only your BP change shows up and none of > >the December mods can be viewed. When you cvsup RELENG_6, they are in > >the downloaded src. >=20 > I can confirm that only the branch point entry of RELENG_6 is visible in > cvsweb. >=20 > Does anyone out there knows the reason for this? Yes, the history for UPDATING contains a commit log message which looks like for format cvs uses to seperate entries which in turn confuses cvsweb. fenner wrote about the problem in more detail some time ago (probably on the src commit list). --=20 Simon L. Nielsen --XvKFcGCOAo53UbWW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDuSWEh9pcDSc1mlERApoPAJ9xxzxxN9FDJrx1MoLOzBucBaOASwCgvVSy +PabukkQEN0DLDqCEhSTcmU= =Gk6l -----END PGP SIGNATURE----- --XvKFcGCOAo53UbWW-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 14:00:58 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D287316A41F for ; Mon, 2 Jan 2006 14:00:58 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.uni-dortmund.de [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3703543D48 for ; Mon, 2 Jan 2006 14:00:57 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 9867244128; Mon, 2 Jan 2006 15:00:56 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 06540-08; Mon, 2 Jan 2006 15:00:55 +0100 (CET) Received: from m2a2.dyndns.org (p5091360C.dip0.t-ipconnect.de [80.145.54.12]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id DFD52440A8; Mon, 2 Jan 2006 15:00:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id E2CB32007AE; Mon, 2 Jan 2006 15:00:52 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 07981-01; Mon, 2 Jan 2006 15:00:50 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id C2B4C20155D; Mon, 2 Jan 2006 15:00:50 +0100 (CET) From: Matthias Andree To: Poul-Henning Kamp In-Reply-To: <73774.1136109554@critter.freebsd.dk> (Poul-Henning Kamp's message of "Sun, 01 Jan 2006 10:59:14 +0100") References: <73774.1136109554@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Mon, 02 Jan 2006 15:00:50 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 14:00:58 -0000 Poul-Henning Kamp writes: > http://phk.freebsd.dk/misc/leapsecond.txt > > Notice how CLOCK_REALTIME recycles the 1136073599 second. Well, it is in accordance with POSIX, but that doesn't mean its "correct". How does the POSIX "consistency" babble, and particularly the FreeBSD 5 or 6 implementation, make sure that "make(1)" or other application doesn't see a file created on 2005-12-31T23:59:60.1Z as older than a file created 0.9 seconds earlier, on 2005-12-31T23:59:59.2Z, because of the time warp caused by POSIX's demand to ignore leap seconds? Are there plans to add monotonous TAI clock interfaces to FreeBSD 7 so we have an alternative to the differential CLOCK_MONOTONIC and the jumpy CLOCK_REALTIME? Is any reader of this message aware of efforts to standardize such a TAI clock? The FreeBSD 6 zoneinfo stuff seems to be ready for leap seconds, if only someone uses -L leapseconds with zic. It appears some systems (SUSE Linux) have been doing such for a subdirectory right/ (i. e. TZ=right/Europe/Berlin) for half a decade now. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 14:44:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A494C16A41F for ; Mon, 2 Jan 2006 14:44:02 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAFAD43D5A for ; Mon, 2 Jan 2006 14:44:01 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id A9E75BC50; Mon, 2 Jan 2006 14:43:55 +0000 (UTC) To: Matthias Andree From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 15:00:50 +0100." Date: Mon, 02 Jan 2006 15:43:55 +0100 Message-ID: <79206.1136213035@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 14:44:02 -0000 In message , Matthias Andree writes: >Are there plans to add monotonous TAI clock interfaces to FreeBSD 7 so >we have an alternative to the differential CLOCK_MONOTONIC and the jumpy >CLOCK_REALTIME? Is any reader of this message aware of efforts to >standardize such a TAI clock? No such effort is underway, partly because it does not solve the problems. First of all, TAI is not a real-time clock, it is an after the fact paper clock. Second, reliably getting hold of the UTC-TAI delta is exactly the same job as reliably getting hold of leap-second information. Third, it sounds like you really havn't studied this to any dept since, quite clearly, you attack the problem from the wrong end (making FreeBSD non-portable) rather than the right end (make sure that computer standards represent time according to our definition of time). You can either fix POSIX to cope correctly with leap-seconds or you can abandon leap seconds which also fixes POSIX for the future, but adding non-standard timescales to FreeBSD will not solve the problem. I think abandonning leap seconds so that POSIX becomes correct is by several orders of magnitude the more economical solution. The fact that the global network of NTP servers which are run by the most "time" interested and motivated people in the computing world couldn't get a leapsecond right this time only reinforces this view. -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 15:24:20 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A28B116A41F; Mon, 2 Jan 2006 15:24:20 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-3.dlr.de (smtp-3.dlr.de [195.37.61.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17C4643D77; Mon, 2 Jan 2006 15:24:10 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-3.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Mon, 2 Jan 2006 16:24:06 +0100 Date: Mon, 2 Jan 2006 16:24:07 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: current@freebsd.org Message-ID: <20060102160909.U85149@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-800950730-1136215447=:85149" X-OriginalArrivalTime: 02 Jan 2006 15:24:06.0655 (UTC) FILETIME=[921B20F0:01C60FB0] Cc: dougb@freebsd.org Subject: bind breakage in current on sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 15:24:20 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-800950730-1136215447=:85149 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Please could someone with enough bind or gcc knowledge fix the buildworld= =20 breakage introduced probably with the last bind import? The problem seems= =20 to be that the lines in question are under #ifdef __sparcv9 while the line defining the _ai_pad field in bind's local netdb.h is: #if defined(sun) && defined(_SOCKLEN_T) #ifdef __sparc9 I sure that both should read either __sparc9 or __sparcv9 and I'm not sure= =20 whether we actually define sun. harti =3D=3D=3D> lib/bind (all) =3D=3D=3D> lib/bind/bind (all) cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/ftruncate.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/gettimeofday.= c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/mktemp.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/putenv.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/readv.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/setenv.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/setitimer.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/strcasecmp.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/strdup.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/strerror.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/strpbrk.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/strtoul.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/utimes.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/bsd/writev.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/dst/dst_api.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/dst/hmac_link.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/dst/md5_dgst.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/dst/support.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_addr.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_cidr_nt= op.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_cidr_pt= on.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_data.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_lnaof.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_makeadd= r.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_net_nto= p.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_net_pto= n.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_neta.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_netof.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_network= =2Ec cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_ntoa.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_ntop.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/inet_pton.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/inet/nsap_addr.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gethostent_r.= c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getnetgrent_r= =2Ec cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getprotoent_r= =2Ec cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getservent_r.= c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/dns.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/dns_ho.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/dns_nw.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/dns_pr.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/dns_sv.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gai_strerror.= c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ho.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ng.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_nw.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_pr.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_sv.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c cc -O2 -fno-strict-aliasing -pipe -I/usr/src/lib/bind/bind/../../../contri= b/bind9/lib/bind/port/freebsd/include -I/usr/src/lib/bind/bind/../../../con= trib/bind9/lib/bind/include -I/usr/src/lib/bind/bind -DVERSION=3D'"9.3.2"' = -DHAVE_CONFIG_H -DLIBINTERFACE=3D4 -DLIBREVISION=3D2 -DLIBAGE=3D0 -DWANT_IP= V6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR=3D'"/var"' -DNS= _SYSCONFDIR=3D'"/etc/namedb"' -DNAMED_CONFFILE=3D'"/etc/namedb/named.conf"'= -DRNDC_CONFFILE=3D'"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE=3D'"/etc/namedb= /rndc.key"' -I/usr/src/lib/bind/bind/.. -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/bind9/include -I/usr/src/lib/bind/bind/../../../contrib/bi= nd9/lib/dns/include/dst -I/usr/src/lib/bind/bind/../../../contrib/bind9/li= b/dns/include -I/usr/src/lib/bind/bind/../dns -I/usr/src/lib/bind/bind/../= =2E./../contrib/bind9/lib/isccc/include -I/usr/src/lib/bind/bind/../../../c= ontrib/bind9/lib/isccfg/include -I/usr/src/lib/bind/bind/../../../contrib/b= ind9/lib/isc/unix/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/nothreads/include -I/usr/src/lib/bind/bind/../../../contrib/bind9/= lib/isc/include -I/usr/src/lib/bind/bind/../isc -I/usr/src/lib/bind/bind/.= =2E/../../contrib/bind9/lib/lwres/unix/include -I/usr/src/lib/bind/bind/..= /../../contrib/bind9/lib/lwres/include -I/usr/src/lib/bind/bind/../lwres = -c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gethostent.c /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c: I= n function `getaddrinfo': /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:34= 2: error: structure has no member named `_ai_pad' /usr/src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:37= 3: error: structure has no member named `_ai_pad' *** 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 *** Error code 2 1 error *** Error code 2 1 error --0-800950730-1136215447=:85149-- From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 16:21:34 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D4A516A41F for ; Mon, 2 Jan 2006 16:21:34 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id C6E8A43D69 for ; Mon, 2 Jan 2006 16:21:20 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 02 Jan 2006 16:21:18 -0000 Received: from p5091360C.dip0.t-ipconnect.de (EHLO merlin) [80.145.54.12] by mail.gmx.net (mp031) with SMTP; 02 Jan 2006 17:21:18 +0100 X-Authenticated: #428038 Date: Mon, 2 Jan 2006 17:21:17 +0100 From: Matthias Andree To: Poul-Henning Kamp Message-ID: <20060102162117.GB14097@merlin.emma.line.org> Mail-Followup-To: Poul-Henning Kamp , current@freebsd.org References: <79206.1136213035@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <79206.1136213035@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 X-Y-GMX-Trusted: 0 Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 16:21:34 -0000 On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: > In message , Matthias Andree writes: > > >Are there plans to add monotonous TAI clock interfaces to FreeBSD 7 so > >we have an alternative to the differential CLOCK_MONOTONIC and the jumpy > >CLOCK_REALTIME? Is any reader of this message aware of efforts to > >standardize such a TAI clock? > > No such effort is underway, partly because it does not solve the > problems. > > First of all, TAI is not a real-time clock, it is an after the fact > paper clock. That depends on what you consider "real time" (without dash). Ask two experts and get three opinions. I don't mean to bikeshed here, I'm neutral. I'm only annoyed that POSIX pretends leap seconds were non-existant, and even more because I have no satisfactory answer to my question how FreeBSD knows that a file created at 23:59:59.2 is older than a file created at 23:59:60.1 if the timestamp is recycled but rather unsubstantiated assumptions about the amount of research I have done. I don't want to bore readers on mailing lists with epic breadth... > Second, reliably getting hold of the UTC-TAI delta is exactly the > same job as reliably getting hold of leap-second information. I'm aware of this problem, and I am aware that this is, according to Dave Mills (which he underlined again in January 2004), the showstopper that prevented NTPD from switching to TAI, because many applications desire UTC and knowing leap seconds only 6 months in advance is too short notice for autonomous appliances. > Third, it sounds like you really havn't studied this to any dept > since, quite clearly, you attack the problem from the wrong end > (making FreeBSD non-portable) rather than the right end (make > sure that computer standards represent time according to our > definition of time). Wrong, I have read up a bit (Mills, Kuhn, your posts and FAQ entries), and made up my mind - just because I'm not writing a dozen cubits of parchment full with prose doesn't mean I don't know, and I am not suggesting to warp time(3) or similar incompatible changes. (I omitted mention of Dan J. Bernstein who is also in the favor of the TAI approach because that would lead to even more bikeshedding.) Markus Kuhn suggested adding a new interface, or as an alternative solution, smoothing the UTC by slewing the clock ("UTS") for the past 1,000 seconds before the insertion or deletion of the leap second. TAI is the monotonous timescale that computers should have been using since Epoch, but I'm not sure who was there first, TAI or UNIX. Why "TAI is not a real-time clock" is irrelevant is that no-one uses internal timestamps for presentation anyways. The goals are: 1. consistent time across POSIX computers, 2. monotonic clocks inside POSIX computers (which is an extension currently), 3. a time presentation to end users that matches the astronomical view of "noon". > You can either fix POSIX to cope correctly with leap-seconds or you > can abandon leap seconds which also fixes POSIX for the future, > but adding non-standard timescales to FreeBSD will not solve the > problem. > > I think abandonning leap seconds so that POSIX becomes correct is > by several orders of magnitude the more economical solution. Does POSIX specify a solution to the problem with the ordering of the two files' age I outlined above? Not to my knowledge, so how can it possibly be "correct"? > The fact that the global network of NTP servers which are run by > the most "time" interested and motivated people in the computing > world couldn't get a leapsecond right this time only reinforces > this view. Any precendents where the leap second didn't work? URL suffices. It appears all POSIX machines I look after got the leap second right one way or another, the Linux machines slewed their clocks by 500 ppm, what the Solaris 8 machines did, I didn't check, since I have more interesting things to do on New Year's Day at 1 a.m., but they didn't log any difficulties, the FreeBSD machines were offline and resynched through ntpdate at bootup (no info), so I'm taking your word UTC remained correct. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 17:08:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E77316A41F for ; Mon, 2 Jan 2006 17:08:14 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from skippyii.compar.com (skippyii.compar.com [216.208.38.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF29743D5F for ; Mon, 2 Jan 2006 17:08:11 +0000 (GMT) (envelope-from matt@gsicomp.on.ca) Received: from hermes (CPE00062566c7bb-CM0011e6ede298.cpe.net.cable.rogers.com [70.28.254.189]) by skippyii.compar.com (8.13.1/8.13.1) with ESMTP id k02H9U4u020138; Mon, 2 Jan 2006 12:09:31 -0500 (EST) (envelope-from matt@gsicomp.on.ca) Message-ID: <00bc01c60fbf$3d7a8e50$1200a8c0@gsicomp.on.ca> From: "Matt Emmerton" To: "Divacky Roman" References: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> <20060102101157.GA63949@stud.fit.vutbr.cz> Date: Mon, 2 Jan 2006 12:09:05 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1506 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: current@freebsd.org Subject: Re: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 17:08:14 -0000 > On Mon, Jan 02, 2006 at 01:53:03AM -0500, Matt Emmerton wrote: > > Just looking through the kernel code, and there are many strong warnings (in > > NOTES, GENERIC and various bits of code) that strongly advise *not* removing > > COMPAT_43 from the kernel config. > > > > In fact, doing so causes lots of things to break, especially the > > Linuxulator. > > > > That said, would COMPAT_43 (and possibly COMPAT_FREEBSD4 and > > COMPAT_FREEBSD5) be good candidates to put in DEFAULTS -- at least on i386? > > I have patch in queue which removes dependancy of linuxator on COMPAT_43 > (hysteria.sk/~neologism/linux43.patch) - its tested on amd64/i386 but havent > tried alpha (not even building it - anyone willing to test this?) > > and I plan to work to split COMPAT_43 into whats necessary for tty stuff and > the rest. after this we can remove COMPAT_43 from even GENERIC imho. That's great news! > I dont think that moving in the direction you suggest is correct. Agreed. In the context of your work, my suggestion is definitely a step in the wrong direction. -- Matt Emmerton From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 18:52:15 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D86416A41F for ; Mon, 2 Jan 2006 18:52:15 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C98DB43D5C for ; Mon, 2 Jan 2006 18:52:10 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5F5E3.dip.t-dialin.net [84.165.245.227]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02ImVrt070793; Mon, 2 Jan 2006 19:48:32 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02Iq66Q083628; Mon, 2 Jan 2006 19:52:06 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 19:52:06 +0100 Message-ID: <20060102195206.az4i1xoffkgg0gs0@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 19:52:06 +0100 From: Alexander Leidinger To: Matt Emmerton References: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> In-Reply-To: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org Subject: Re: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 18:52:15 -0000 Matt Emmerton wrote: > Just looking through the kernel code, and there are many strong warnings (in > NOTES, GENERIC and various bits of code) that strongly advise *not* removing > COMPAT_43 from the kernel config. > > In fact, doing so causes lots of things to break, especially the > Linuxulator. > > That said, would COMPAT_43 (and possibly COMPAT_FREEBSD4 and > COMPAT_FREEBSD5) be good candidates to put in DEFAULTS -- at least on i386? There's a PR with a patch which removes the dependency from the linuxolator. My intend is to give it a try (and commit it). Maybe this week, if time permits. Regarding the FreeBSD compatibility options: if you don't run software from those releases, you don't need them. Entries in DEFAULTS are supposed to render any kernel useless if removed. So I don't think the FreeBSD compatibility options are good candidates for DEFAULTS. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 I believe that professional wrestling is clean and everything else in the world is fixed. -- Frank Deford, sports writer From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 18:53:42 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2583716A41F for ; Mon, 2 Jan 2006 18:53:42 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29EFA43D45 for ; Mon, 2 Jan 2006 18:53:29 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5F5E3.dip.t-dialin.net [84.165.245.227]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02Inqvg070809; Mon, 2 Jan 2006 19:49:53 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02IrRts083839; Mon, 2 Jan 2006 19:53:27 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 19:53:27 +0100 Message-ID: <20060102195327.p8kxba7sgs40swg8@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 19:53:27 +0100 From: Alexander Leidinger To: Divacky Roman References: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> <20060102101157.GA63949@stud.fit.vutbr.cz> In-Reply-To: <20060102101157.GA63949@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: current@freebsd.org, Matt Emmerton Subject: Re: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 18:53:42 -0000 Divacky Roman wrote: > I have patch in queue which removes dependancy of linuxator on COMPAT_43 > (hysteria.sk/~neologism/linux43.patch) - its tested on amd64/i386 but havent > tried alpha (not even building it - anyone willing to test this?) Is this more recent than your PR? Maybe I get time this week to test (and commit) it on x86/"make universe"). Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Unhappy the land that needs heroes. -- Bertolt Brecht From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 19:03:53 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 794FC16A41F for ; Mon, 2 Jan 2006 19:03:53 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBECE43D45 for ; Mon, 2 Jan 2006 19:03:51 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5F5E3.dip.t-dialin.net [84.165.245.227]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02J0Edi070876; Mon, 2 Jan 2006 20:00:14 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02J3mRn085862; Mon, 2 Jan 2006 20:03:49 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 20:03:47 +0100 Message-ID: <20060102200347.2bumr7okkkgossww@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 20:03:47 +0100 From: Alexander Leidinger To: Divacky Roman References: <20060102101653.GA65178@stud.fit.vutbr.cz> In-Reply-To: <20060102101653.GA65178@stud.fit.vutbr.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 19:03:53 -0000 Divacky Roman wrote: [no cachesize detection] > my CPU is: > CPU: AMD Athlon(tm) XP 2500+ (1834.88-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > Features=0x383fbff > AMD Features=0xc0400800 So the AMD64 code works (on AMD processors) but the IA32 (on AMD) fails. Either I did something completely wrong, or it's a small typo I do overlook (tomatoes on the eyes...). Can someone with a little bit of AMD feature detection knowledge have a look at: ---snip--- static void setPQL2_AMD(int *const size, int *const ways) { if (cpu_exthigh >= 0x80000006) { u_int regs[4]; do_cpuid(0x80000006, regs); *size = regs[2] >> 16; *ways = (regs[2] >> 12) & 0x0f; if(*ways == 255) /* fully associative */ *ways = 1; } } void setPQL2(int *const size, int *const ways) { if (strcmp(cpu_vendor, "AuthenticAMD") == 0) setPQL2_AMD(size, ways); else if (strcmp(cpu_vendor, "GenuineIntel") == 0) setPQL2_INTEL(size, ways); } ---snip--- This is from sys/i386/i386/identcpu.c. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 When we are planning for posterity, we ought to remember that virtue is not hereditary. -- Thomas Paine From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 19:30:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7494A16A41F for ; Mon, 2 Jan 2006 19:30:30 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B9B043D48 for ; Mon, 2 Jan 2006 19:30:29 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: by wproxy.gmail.com with SMTP id i28so1398165wra for ; Mon, 02 Jan 2006 11:30:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=hDFRRX3bXobYnqQL9u/IBogrHDgxgWMlgpfu/Ur9PI2DnHrE2FzRnAYCZkOnL0oB0wChKw6cktEiFRYH+Et9CxBk9QS49oTQwCefpeJr0VLQgOX2kV4SgImpT1i44Tx4aSCThVPGZEyMbhJoX2kAMWPBmvGtnor2RaaW9dnNYf0= Received: by 10.65.218.9 with SMTP id v9mr263126qbq; Mon, 02 Jan 2006 11:30:28 -0800 (PST) Received: by 10.64.209.20 with HTTP; Mon, 2 Jan 2006 11:30:28 -0800 (PST) Message-ID: Date: Mon, 2 Jan 2006 22:30:28 +0300 From: Anton Karpov To: freebsd-current@freebsd.org In-Reply-To: <20060101.212552.85411680.imp@bsdimp.com> MIME-Version: 1.0 References: <43B83262.1090907@fastmail.fm> <20060101.212552.85411680.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 19:30:30 -0000 I can confirm it with atheros-based Orinoco 8470-wd! I've got kernel panic since last days of december. With a little bit earlier kernel builds (a mid of december, I thought), card works well but kismet fails to work with it. Now, I'm getting panic inserting it into cardbus slot... : Same here, though I got the kernel panic at boot when I had inserted > during > : the boot. The panic was in cardbus_read_tuple() also. I can post the > : hand scribed trace to anyone interested if necessary. > > No need. I have the card here, and it fails too. All my other cards > work, but the atheros card is the only one that stores the CIS in a > bar that I have (I'm sure that others do as well, but they aren't in > the 10 cards I grabbed to test with). This appears to be resource > related in some way, since it appears that we're getting a resource of > '0' back. I'm trying to debug it now. > > > From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 19:54:04 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26B4816A41F for ; Mon, 2 Jan 2006 19:54:04 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4D2343D48 for ; Mon, 2 Jan 2006 19:54:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 5391CBC50; Mon, 2 Jan 2006 19:54:01 +0000 (UTC) To: Matthias Andree From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 17:21:17 +0100." <20060102162117.GB14097@merlin.emma.line.org> Date: Mon, 02 Jan 2006 20:54:00 +0100 Message-ID: <80148.1136231640@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 19:54:04 -0000 In message <20060102162117.GB14097@merlin.emma.line.org>, Matthias Andree writes: >> First of all, TAI is not a real-time clock, it is an after the fact >> paper clock. > >That depends on what you consider "real time" (without dash). Ask two >experts and get three opinions. I don't mean to bikeshed here, I'm >neutral. TAI is a paper clock, end of story. It is calculated from comparisons between a large number of atomic frequency standards from all over the world. Estimates of TAI may exist in real time, but TAI does not and therefore the BIPM, CCTF and IERS actively discourages its use as anything but a reference timescale. It can be argued that this is not a sensible position on their part, but that is nontheless their position. >I'm only annoyed that POSIX pretends leap seconds were non-existant, and >even more because I have no satisfactory answer to my question how >FreeBSD knows that a file created at 23:59:59.2 is older than a file >created at 23:59:60.1 if the timestamp is recycled but rather >unsubstantiated assumptions about the amount of research I have done. I >don't want to bore readers on mailing lists with epic breadth... No POSIX compliant system can tell the difference, not even FreeBSD. >Markus Kuhn suggested adding a new interface, or as an alternative >solution, smoothing the UTC by slewing the clock ("UTS") for the past >1,000 seconds before the insertion or deletion of the leap second. Yes, that is a total non-starter, now we don't even know how long seconds are going to be any more :-( >TAI is the monotonous timescale that computers should have been using >since Epoch, but I'm not sure who was there first, TAI or UNIX. No, no and no. Computers should use UTC because UTC underlies civil timekeeping. It's the definition of UTC that is the problem, not the choice of it. >Does POSIX specify a solution to the problem with the ordering of the >two files' age I outlined above? Not to my knowledge, so how can it >possibly be "correct"? If there are no more leap seconds, POSIX doesn't have to specify how to deal with them. >It appears all POSIX machines I look after got the leap second right one >way or another[...] None of them got it right by any strech of the imagination because it is impossible to get it right and be POSIX compliance. -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:03:55 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8C0816A41F for ; Mon, 2 Jan 2006 20:03:55 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 494CD43D5D for ; Mon, 2 Jan 2006 20:03:55 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 10406 invoked by uid 399); 2 Jan 2006 20:03:53 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 2 Jan 2006 20:03:53 -0000 Message-ID: <43B98725.3020505@FreeBSD.org> Date: Mon, 02 Jan 2006 12:03:49 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051226) MIME-Version: 1.0 To: Harti Brandt References: <20060102160909.U85149@beagle.kn.op.dlr.de> In-Reply-To: <20060102160909.U85149@beagle.kn.op.dlr.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: bind breakage in current on sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:03:56 -0000 Harti Brandt wrote: > > Please could someone with enough bind or gcc knowledge fix the > buildworld breakage introduced probably with the last bind import? I'm actually working on this today. I finally found someone with a sparc that was willing to let me work on it. The bind9 port builds fine on freebsd sparc, so I am going to figure out what's different, test the change, and commit it. > The > problem seems to be that the lines in question are under > > #ifdef __sparcv9 > > while the line defining the _ai_pad field in bind's local netdb.h is: > > #if defined(sun) && defined(_SOCKLEN_T) > #ifdef __sparc9 > > I sure that both should read either __sparc9 or __sparcv9 and I'm not > sure whether we actually define sun. Ok, that's a good place to start looking, thanks. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:20:56 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DC0A16A420 for ; Mon, 2 Jan 2006 20:20:56 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.10.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D1843D55 for ; Mon, 2 Jan 2006 20:20:54 +0000 (GMT) (envelope-from xdivac02@stud.fit.vutbr.cz) Received: from eva.fit.vutbr.cz (localhost [127.0.0.1]) by eva.fit.vutbr.cz (envelope-from xdivac02@eva.fit.vutbr.cz) (8.13.4/8.13.3) with ESMTP id k02KKpbP058981 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 2 Jan 2006 21:20:51 +0100 (CET) Received: (from xdivac02@localhost) by eva.fit.vutbr.cz (8.13.4/8.13.3/Submit) id k02KKoJ3058979; Mon, 2 Jan 2006 21:20:50 +0100 (CET) Date: Mon, 2 Jan 2006 21:20:50 +0100 From: Divacky Roman To: Alexander Leidinger Message-ID: <20060102202050.GA58502@stud.fit.vutbr.cz> References: <005001c60f69$2dfff650$1200a8c0@gsicomp.on.ca> <20060102101157.GA63949@stud.fit.vutbr.cz> <20060102195327.p8kxba7sgs40swg8@netchild.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060102195327.p8kxba7sgs40swg8@netchild.homeip.net> User-Agent: Mutt/1.4.2i X-Scanned-By: MIMEDefang 2.49 on 147.229.10.14 Cc: current@freebsd.org, Matt Emmerton Subject: Re: Candidates for inclusion in DEFAULTS X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:20:56 -0000 On Mon, Jan 02, 2006 at 07:53:27PM +0100, Alexander Leidinger wrote: > Divacky Roman wrote: > > >I have patch in queue which removes dependancy of linuxator on COMPAT_43 > >(hysteria.sk/~neologism/linux43.patch) - its tested on amd64/i386 but > >havent > >tried alpha (not even building it - anyone willing to test this?) > > Is this more recent than your PR? Maybe I get time this week to test (and > commit) it on x86/"make universe"). yes.. the alpha support was added - but its "blind" support - as I didnt test it at all. I just know I use this patch on my i386 machine without ANY problems for a couple of months and people reported me that amd64 works as well... if someone is willing to test alpha and/or amd64 I think its almost commitable (phk@ did a quick review of the patch) roman From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:23:15 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4655E16A41F for ; Mon, 2 Jan 2006 20:23:15 +0000 (GMT) (envelope-from antoine@peanut.dreadbsd.org) Received: from barton.dreadbsd.org (peanut.dreadbsd.org [82.67.196.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4721543D49 for ; Mon, 2 Jan 2006 20:23:13 +0000 (GMT) (envelope-from antoine@peanut.dreadbsd.org) Received: from barton.dreadbsd.org (localhost [127.0.0.1]) by barton.dreadbsd.org (8.13.4/8.13.4) with ESMTP id k02KNAQg000744; Mon, 2 Jan 2006 21:23:10 +0100 (CET) (envelope-from antoine@peanut.dreadbsd.org) Received: (from antoine@localhost) by barton.dreadbsd.org (8.13.4/8.13.1/Submit) id k02KN94Q000743; Mon, 2 Jan 2006 21:23:09 +0100 (CET) (envelope-from antoine) Date: Mon, 2 Jan 2006 21:23:09 +0100 From: Antoine Brodin To: Alexander Leidinger Message-Id: <20060102212309.6ebcf836.antoine.brodin@laposte.net> In-Reply-To: <20060102200347.2bumr7okkkgossww@netchild.homeip.net> References: <20060102101653.GA65178@stud.fit.vutbr.cz> <20060102200347.2bumr7okkkgossww@netchild.homeip.net> X-Mailer: Sylpheed version 2.0.4 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: xdivac02@stud.fit.vutbr.cz, current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:23:15 -0000 Alexander Leidinger wrote: > Divacky Roman wrote: > [no cachesize detection] > > my CPU is: > > CPU: AMD Athlon(tm) XP 2500+ (1834.88-MHz 686-class CPU) > > Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 > > Features=0x383fbff > > AMD Features=0xc0400800 > > So the AMD64 code works (on AMD processors) but the IA32 (on AMD) fails. > Either I did something completely wrong, or it's a small typo I do overlook > (tomatoes on the eyes...). Can someone with a little bit of AMD feature > detection knowledge have a look at: Hi Alexander, The detection doesn't work because the cpu_exthigh variable isn't initialized. And if you and *ways with 0x0f, it will never be 255. Cheers, Antoine PS: with the attached path I've got > sysctl vm.stats.pagequeue vm.stats.pagequeue.page_colors: 16 vm.stats.pagequeue.cachesize: 512 vm.stats.pagequeue.cachenways: 8 vm.stats.pagequeue.prime1: 5 vm.stats.pagequeue.prime2: 3 Index: i386/i386/identcpu.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/identcpu.c,v retrieving revision 1.152 diff -u -p -r1.152 identcpu.c --- i386/i386/identcpu.c 31 Dec 2005 14:39:17 -0000 1.152 +++ i386/i386/identcpu.c 2 Jan 2006 20:09:48 -0000 @@ -1425,14 +1425,15 @@ print_INTEL_TLB(u_int data) static void setPQL2_AMD(int *const size, int *const ways) { - if (cpu_exthigh >= 0x80000006) { - u_int regs[4]; + u_int regs[4]; + do_cpuid(0x80000000, regs); + if (regs[0] >= 0x80000000) + cpu_exthigh = regs[0]; + if (cpu_exthigh >= 0x80000006) { do_cpuid(0x80000006, regs); *size = regs[2] >> 16; *ways = (regs[2] >> 12) & 0x0f; - if(*ways == 255) /* fully associative */ - *ways = 1; } } From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:26:11 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70B9716A41F for ; Mon, 2 Jan 2006 20:26:11 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from ylpvm12.prodigy.net (ylpvm12-ext.prodigy.net [207.115.57.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CEE743D48 for ; Mon, 2 Jan 2006 20:26:10 +0000 (GMT) (envelope-from mbsd@pacbell.net) Received: from pimout5-ext.prodigy.net (pimout5-int.prodigy.net [207.115.4.21]) by ylpvm12.prodigy.net (8.12.10 outbound/8.12.10) with ESMTP id k02KQAKI028321 for ; Mon, 2 Jan 2006 15:26:10 -0500 X-ORBL: [71.139.60.194] DomainKey-Signature: a=rsa-sha1; s=sbc01; d=pacbell.net; c=nofws; q=dns; h=date:from:x-x-sender:to:cc:subject:in-reply-to:message-id: references:mime-version:content-type; b=BYuqZZ2pdR48F7CtDgOagIsE09Bb8W54L4FGsHD7SvSTLyrHxlMMCYWyNKvbbJLa1 zwGgWVUXSGEV1S0mkQrGA== Received: from inspiron.home (ppp-71-139-60-194.dsl.snfc21.pacbell.net [71.139.60.194]) by pimout5-ext.prodigy.net (8.13.4 outbound domainkey aix/8.13.4) with ESMTP id k02KPvvK031294; Mon, 2 Jan 2006 15:26:03 -0500 Date: Mon, 2 Jan 2006 12:25:58 -0800 (PST) From: =?ISO-8859-1?Q?Mikko_Ty=F6l=E4j=E4rvi?= X-X-Sender: mikko@inspiron.home To: Alexander Leidinger In-Reply-To: <20060102200347.2bumr7okkkgossww@netchild.homeip.net> Message-ID: <20060102122209.G59712@inspiron.home> References: <20060102101653.GA65178@stud.fit.vutbr.cz> <20060102200347.2bumr7okkkgossww@netchild.homeip.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Divacky Roman , current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:26:11 -0000 On Mon, 2 Jan 2006, Alexander Leidinger wrote: > Divacky Roman wrote: > > [no cachesize detection] >> my CPU is: >> CPU: AMD Athlon(tm) XP 2500+ (1834.88-MHz 686-class CPU) >> Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 >> Features=0x383fbff >> AMD Features=0xc0400800 > > So the AMD64 code works (on AMD processors) but the IA32 (on AMD) fails. > Either I did something completely wrong, or it's a small typo I do overlook > (tomatoes on the eyes...). Not sure it is AMD specific. % sysctl vm.stats.pagequeue vm.stats.pagequeue.prime2: 5 vm.stats.pagequeue.prime1: 9 vm.stats.pagequeue.cachenways: 0 vm.stats.pagequeue.cachesize: 0 vm.stats.pagequeue.page_colors: 32 The CPU is: CPU: Intel(R) Pentium(R) M processor 1.80GHz (1794.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6d6 Stepping = 6 Features=0xafe9f9bf Features2=0x180 $.02, /Mikko From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:50:40 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 780CE16A41F for ; Mon, 2 Jan 2006 20:50:40 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.uni-dortmund.de [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 971BF43D53 for ; Mon, 2 Jan 2006 20:50:39 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 5B5F744128; Mon, 2 Jan 2006 21:50:38 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 17485-02; Mon, 2 Jan 2006 21:50:36 +0100 (CET) Received: from m2a2.dyndns.org (p5091360C.dip0.t-ipconnect.de [80.145.54.12]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 700AB440A8; Mon, 2 Jan 2006 21:50:36 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id BC291200A3B; Mon, 2 Jan 2006 21:50:35 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04166-04; Mon, 2 Jan 2006 21:50:32 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id 8D44D201628; Mon, 2 Jan 2006 21:50:32 +0100 (CET) From: Matthias Andree To: "Poul-Henning Kamp" In-Reply-To: <80148.1136231640@critter.freebsd.dk> (Poul-Henning Kamp's message of "Mon, 02 Jan 2006 20:54:00 +0100") References: <80148.1136231640@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Mon, 02 Jan 2006 21:50:32 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:50:40 -0000 "Poul-Henning Kamp" writes: >>I'm only annoyed that POSIX pretends leap seconds were non-existant, and >>even more because I have no satisfactory answer to my question how >>FreeBSD knows that a file created at 23:59:59.2 is older than a file >>created at 23:59:60.1 if the timestamp is recycled but rather >>unsubstantiated assumptions about the amount of research I have done. I >>don't want to bore readers on mailing lists with epic breadth... > > No POSIX compliant system can tell the difference, not even FreeBSD. Well, some systems appear to be cheating, at the expense of "length of a second"... >>Markus Kuhn suggested adding a new interface, or as an alternative >>solution, smoothing the UTC by slewing the clock ("UTS") for the past >>1,000 seconds before the insertion or deletion of the leap second. > > Yes, that is a total non-starter, now we don't even know how long > seconds are going to be any more :-( ...as you word it. Some systems seem to actually be doing this, in a slightly different manner, today. Check Linux's kernel/timer.c (I was looking at SUSE 10.0, which is based on 2.6.13), if NTP tells Linux "heya, how 'bout a leap second insertion today", Linux will log a message at UTC midnight, slew the clock by 500 ppm and compensate over the next 2,000 seconds, without stepping backwards. You can argue that Linux's notion of a second is off (because it's actually 1,000.5 ms), and that the clock is off during these 33'20" - on the other hand, time of day is monotonic, a "make" process running during the leap second and its preceding second. > Computers should use UTC because UTC underlies civil timekeeping. I don't care the least about civil timekeeping if it breaks builds. The simple solution would be to block all file creations by non-realtime processes during that inserted leap second, which causes similar symptoms to an I/O load spike (or disk retry on read or whatever) that prevent 23:59:60. Yes, it's ugly. But at least it doesn't break builds. And tell me one reason why the leap second must be discontinued while the leap day (Feb 29th) can be carried on. It's the same story, irregular rollover, inserting one particular unit of time. > It's the definition of UTC that is the problem, not the choice of it. Seems like exchanging cause and effect. If it's got a problematic definition, why choose it? Of course FreeBSD won't change POSIX and we don't want to deviate from POSIX >>Does POSIX specify a solution to the problem with the ordering of the >>two files' age I outlined above? Not to my knowledge, so how can it >>possibly be "correct"? > > If there are no more leap seconds, POSIX doesn't have to specify > how to deal with them. That one excess "if"... >>It appears all POSIX machines I look after got the leap second right one >>way or another[...] > > None of them got it right by any strech of the imagination because > it is impossible to get it right and be POSIX compliance. Wow, and you claim FreeBSD handles it correctly. -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 20:53:46 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 795C516A41F for ; Mon, 2 Jan 2006 20:53:46 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E9C743D55 for ; Mon, 2 Jan 2006 20:53:45 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 669B2BC50; Mon, 2 Jan 2006 20:53:44 +0000 (UTC) To: Matthias Andree From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 21:50:32 +0100." Date: Mon, 02 Jan 2006 21:53:43 +0100 Message-ID: <80432.1136235223@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 20:53:46 -0000 In message , Matthias Andree writes: >And tell me one reason why the leap second must be discontinued while >the leap day (Feb 29th) can be carried on. It's the same story, >irregular rollover, inserting one particular unit of time. You are clearly not thinking rationally here. I know already now that year 2048 will be a leap year, but I still don't know if there will be a leap second on june 30th 2006. >> None of them got it right by any strech of the imagination because >> it is impossible to get it right and be POSIX compliance. > >Wow, and you claim FreeBSD handles it correctly. Yes, FreeBSD handles it correctly under the impossible constraints of POSIX. -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 21:17:10 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B041B16A41F for ; Mon, 2 Jan 2006 21:17:10 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7CA343D5D for ; Mon, 2 Jan 2006 21:17:09 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D613.dip.t-dialin.net [84.165.214.19]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02LDUwb071426; Mon, 2 Jan 2006 22:13:31 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02LH6tH010617; Mon, 2 Jan 2006 22:17:06 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 22:17:06 +0100 Message-ID: <20060102221706.3ic2h61uoks00k4c@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 22:17:06 +0100 From: Alexander Leidinger To: Mikko =?utf-8?b?VHnDtmzDpGrDpHJ2aQ==?= References: <20060102101653.GA65178@stud.fit.vutbr.cz> <20060102200347.2bumr7okkkgossww@netchild.homeip.net> <20060102122209.G59712@inspiron.home> In-Reply-To: <20060102122209.G59712@inspiron.home> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: Divacky Roman , current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 21:17:10 -0000 Mikko Ty=C3=B6l=C3=A4j=C3=A4rvi wrote: > Not sure it is AMD specific. > > % sysctl vm.stats.pagequeue > vm.stats.pagequeue.prime2: 5 > vm.stats.pagequeue.prime1: 9 > vm.stats.pagequeue.cachenways: 0 > vm.stats.pagequeue.cachesize: 0 > vm.stats.pagequeue.page_colors: 32 > > The CPU is: > CPU: Intel(R) Pentium(R) M processor 1.80GHz (1794.19-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x6d6 Stepping =3D 6 Ok, I think I know what the problem is now... Thanks for the report. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 I call them as I see them. If I can't see them, I make them up. =09=09-- Biff Barf From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 21:19:28 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B14316A41F for ; Mon, 2 Jan 2006 21:19:28 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6324C43D5A for ; Mon, 2 Jan 2006 21:19:27 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D613.dip.t-dialin.net [84.165.214.19]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k02LFk17071439; Mon, 2 Jan 2006 22:15:47 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k02LJMeR011017; Mon, 2 Jan 2006 22:19:23 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Mon, 02 Jan 2006 22:19:22 +0100 Message-ID: <20060102221922.i1keboodckwc0w88@netchild.homeip.net> X-Priority: 3 (Normal) Date: Mon, 02 Jan 2006 22:19:22 +0100 From: Alexander Leidinger To: Antoine Brodin References: <20060102101653.GA65178@stud.fit.vutbr.cz> <20060102200347.2bumr7okkkgossww@netchild.homeip.net> <20060102212309.6ebcf836.antoine.brodin@laposte.net> In-Reply-To: <20060102212309.6ebcf836.antoine.brodin@laposte.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: xdivac02@stud.fit.vutbr.cz, current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 21:19:28 -0000 Antoine Brodin wrote: > The detection doesn't work because the cpu_exthigh variable isn't > initialized. Thanks for the hint. I will take your patch as a base (some minor changes). Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 PORK IS NOT A VERB PORK IS NOT A VERB PORK IS NOT A VERB PORK IS NOT A VERB Bart Simpson on chalkboard in episode AABF22 From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 21:20:01 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46FA816A41F for ; Mon, 2 Jan 2006 21:20:01 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 5758043D58 for ; Mon, 2 Jan 2006 21:19:59 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 02 Jan 2006 21:19:57 -0000 Received: from p5091360C.dip0.t-ipconnect.de (EHLO merlin) [80.145.54.12] by mail.gmx.net (mp039) with SMTP; 02 Jan 2006 22:19:57 +0100 X-Authenticated: #428038 Date: Mon, 2 Jan 2006 22:19:56 +0100 From: Matthias Andree To: Poul-Henning Kamp Message-ID: <20060102211956.GA10928@merlin.emma.line.org> Mail-Followup-To: Poul-Henning Kamp , current@freebsd.org References: <80432.1136235223@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80432.1136235223@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 X-Y-GMX-Trusted: 0 Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 21:20:01 -0000 On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: > In message , Matthias Andree writes: > > >And tell me one reason why the leap second must be discontinued while > >the leap day (Feb 29th) can be carried on. It's the same story, > >irregular rollover, inserting one particular unit of time. > > You are clearly not thinking rationally here. > > I know already now that year 2048 will be a leap year, but I still > don't know if there will be a leap second on june 30th 2006. And you can predict the DST rules for all major countries for 2048? Who says the EU won't discontinue DST effective 2008? We don't know yet. You suggest UTC needs to be used because civil time matters, yet at the same time UTC were broken, and thus POSIX were broken, but could not be blamed for picking UTC. Leap days (called leap year, to compensate for earth orbiting the sun), leap hours (called daylight savings time, completely artificial); aren't questioned, but leap seconds are. Is it just me who sees inconsistencies in your argumentation here? No offense, but I simply don't get your point. Another question: Did you mean to write "FreeBSD handles leapsecond in POSIX compliance" for the subject? -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 21:37:31 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA99916A41F for ; Mon, 2 Jan 2006 21:37:31 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2691A43D69 for ; Mon, 2 Jan 2006 21:37:26 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 57F39BC50; Mon, 2 Jan 2006 21:37:21 +0000 (UTC) To: Matthias Andree From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 22:19:56 +0100." <20060102211956.GA10928@merlin.emma.line.org> Date: Mon, 02 Jan 2006 22:37:20 +0100 Message-ID: <80684.1136237840@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 21:37:32 -0000 In message <20060102211956.GA10928@merlin.emma.line.org>, Matthias Andree writes: >On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: >No offense, but I simply don't get your point. Right, I'm getting that feeling here too. I think the only way for you to catch up is to study the subject matter much more carefully. In particular you need to understand the "ownership" of the various time/frequency related units, standards and timescales much better than you do now. A good place to start is the classic 1968 Essen article in Metrologica: http://www.leapsecond.com/history/1968-Metrologia-v4-n4-Essen.pdf And next read Steve Allens very comprehensive but rather politically slanted web-page about the leap-second problem: http://www.ucolick.org/~sla/leapsecs/dutc.html Next you want to read RFC1305 to understand how NTP works, pay particular attention to the timescale/representation parts. Finally, you may want to buy and explore "Calendrical Calculations" http://emr.cs.uiuc.edu/home/reingold/calendar-book/index.shtml And then, feel free come back and tell me and the rest of the world how easy this problem can be solved correctly. >Another question: Did you >mean to write "FreeBSD handles leapsecond in POSIX compliance" for the >subject? POSIX compliance is assumed for FreeBSD and no other relevant computer standardization exists for this area. I assumed this to be self-evident, but I guess I need to lower the bar in future emails. Poul-Henning -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 21:53:06 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E425416A420 for ; Mon, 2 Jan 2006 21:53:06 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id A992B43D48 for ; Mon, 2 Jan 2006 21:53:05 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 02 Jan 2006 21:53:04 -0000 Received: from p5091360C.dip0.t-ipconnect.de (EHLO merlin) [80.145.54.12] by mail.gmx.net (mp001) with SMTP; 02 Jan 2006 22:53:04 +0100 X-Authenticated: #428038 Date: Mon, 2 Jan 2006 22:53:02 +0100 From: Matthias Andree To: Poul-Henning Kamp Message-ID: <20060102215302.GB10928@merlin.emma.line.org> Mail-Followup-To: Poul-Henning Kamp , current@freebsd.org References: <20060102211956.GA10928@merlin.emma.line.org> <80684.1136237840@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80684.1136237840@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc User-Agent: Mutt/1.5.11 X-Y-GMX-Trusted: 0 Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 21:53:07 -0000 On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: > And then, feel free come back and tell me and the rest of the world > how easy this problem can be solved correctly. I made no statement to the extent this problem were _easy_ to solve, and I am aware that any "solution" goes beyond FreeBSD's scope. > I assumed this to be self-evident, but I guess I need to lower > the bar in future emails. The actual point was that the definition of "correct" depends on the scope, and that drifted through the discussion. "Correct in POSIX:" yes, "correct" as "doing the right thing[tm] for all fields of application": clearly no. "Handles leapsecond according to IEEE Std 1003.1-2001" (or whichever you chose) avoids the need to disambiguate. BTW, thanks for providing evidence that your system was made aware of the leap second, and processed it in accordance with POSIX -- this is a data point for "leap seconds do work". -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:19:52 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E04B716A41F for ; Mon, 2 Jan 2006 22:19:52 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6270C43D49 for ; Mon, 2 Jan 2006 22:19:52 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Mon, 02 Jan 2006 14:19:48 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id EBE475D09; Mon, 2 Jan 2006 14:19:48 -0800 (PST) To: Matthias Andree In-reply-to: Your message of "Mon, 02 Jan 2006 22:19:56 +0100." <20060102211956.GA10928@merlin.emma.line.org> Date: Mon, 02 Jan 2006 14:19:48 -0800 From: "Kevin Oberman" Message-Id: <20060102221948.EBE475D09@ptavv.es.net> Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:19:53 -0000 > Date: Mon, 2 Jan 2006 22:19:56 +0100 > From: Matthias Andree > Sender: owner-freebsd-current@freebsd.org > > On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: > > > In message , Matthias Andree writes: > > > > >And tell me one reason why the leap second must be discontinued while > > >the leap day (Feb 29th) can be carried on. It's the same story, > > >irregular rollover, inserting one particular unit of time. > > > > You are clearly not thinking rationally here. > > > > I know already now that year 2048 will be a leap year, but I still > > don't know if there will be a leap second on june 30th 2006. > > And you can predict the DST rules for all major countries for 2048? Who > says the EU won't discontinue DST effective 2008? We don't know yet. They can, but FreeBSD and any POSIX system keeps time in UTC. DST has no impact on UTC, GMT, TAI, or the like. > You suggest UTC needs to be used because civil time matters, yet at the > same time UTC were broken, and thus POSIX were broken, but could not be > blamed for picking UTC. Civil time matters for many of us. UTC is certainly not perfect, but it's more practical than GMT and more real than TAI. It provides a consistent, very accurately defined second which is VERY important to many things which don't care an iota what time it is. > Leap days (called leap year, to compensate for earth orbiting the sun), > leap hours (called daylight savings time, completely artificial); aren't > questioned, but leap seconds are. Leap years are an artifact of a lousy calendar that has origins over 2 millennia ago. Many calendars have been proposed which fix this, but calendar reform is simply not going to happen in our society, but leap years are a known, non-varying and trivially calculable issue. No magic and trivial to handle. Leap seconds occur because the earth does not spin quite uniformly. There is no way to know exactly when one will be needed, although we are pretty sure that they will be needed more often in the future. Their only purpose is to keep GMT and UTC close. Are they needed? Get an astronomer and a physicist in the same room and ask them. (Make sure that they are physically separated, first, if you want to avoid any bloodshed.) > > Is it just me who sees inconsistencies in your argumentation here? There are no known good solutions to this problem, but your arguments are mostly orthogonal to the problem. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:27:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DB1616A41F for ; Mon, 2 Jan 2006 22:27:35 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D9C943D72 for ; Mon, 2 Jan 2006 22:27:27 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id k02MRN6X001779 for ; Mon, 2 Jan 2006 14:27:24 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id k02MRN2P001778 for freebsd-current@freebsd.org; Mon, 2 Jan 2006 14:27:23 -0800 (PST) (envelope-from obrien) Date: Mon, 2 Jan 2006 14:27:23 -0800 From: "David O'Brien" To: freebsd-current@freebsd.org Message-ID: <20060102222723.GA1754@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.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 User-Agent: Mutt/1.5.11 Subject: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:27:35 -0000 Just in case anyone thought the bug had been fixed... FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 panic: ufs_dirbad: bad dir cpuid = 1 KDB: stack backtrace: kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e = kdb_backtrace+0x2e panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 = panic+0x128 ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d = ufs_dirbad+0x4d ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = ufs_lookup+0x3ad VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0xc068cd4e = VOP_CACHEDLOOKUP_APV+0x9e vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc057275a = vfs_cache_lookup+0xca VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 = VOP_LOOKUP_APV+0xa6 lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e = lookup+0x44e namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf = namei+0x44f kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd = kern_stat+0x3d stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f = stat+0x2f syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 = syscall+0x323 Xint0x80_syscall() at 0xc066d33f = Xint0x80_syscall+0x1f -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:27:40 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06ABC16A41F for ; Mon, 2 Jan 2006 22:27:40 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id F19E343D75 for ; Mon, 2 Jan 2006 22:27:34 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id CAC24BC50; Mon, 2 Jan 2006 22:27:31 +0000 (UTC) To: "Kevin Oberman" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 14:19:48 PST." <20060102221948.EBE475D09@ptavv.es.net> Date: Mon, 02 Jan 2006 23:27:31 +0100 Message-ID: <80965.1136240851@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:27:40 -0000 In message <20060102221948.EBE475D09@ptavv.es.net>, "Kevin Oberman" writes: >Leap years are an artifact of a lousy calendar that has origins over 2 >millennia ago. Many calendars have been proposed which fix this, but >calendar reform is simply not going to happen in our society, but leap >years are a known, non-varying and trivially calculable issue. No magic >and trivial to handle. Interestingly, the main reason why calendar reform is a no-talk issue seems to be that The Vatican owns the standardization area of calendars because they have written all (relevant) standards for the area in the past. According to one insider, none of the possible owners of a new calendar (ITU, ISO & BIPM) can bring it on themselves to ask the pope permission to take over the area. (ISO has documented the current calendar, but go to some pains to make it clear that they didn't come up with it.) Considering that a merry band of brits are still fighting to get compensation for the 15 days they "lost" last time Brittain changed calendar, the political and legal fallout will probably galvanize the current calendar until something really drastic happens. Poul-Henning -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:32:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF7B816A41F for ; Mon, 2 Jan 2006 22:32:02 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr13.xs4all.nl (smtp-vbr13.xs4all.nl [194.109.24.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DC143D7E for ; Mon, 2 Jan 2006 22:32:01 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by smtp-vbr13.xs4all.nl (8.13.3/8.13.3) with ESMTP id k02MVnD9022416; Mon, 2 Jan 2006 23:31:49 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.4/8.13.3) with ESMTP id k02MVmtL055535; Mon, 2 Jan 2006 23:31:48 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.4/8.13.1/Submit) id k02MVl6J055530; Mon, 2 Jan 2006 23:31:47 +0100 (CET) (envelope-from wb) Date: Mon, 2 Jan 2006 23:31:47 +0100 From: Wilko Bulte To: Poul-Henning Kamp Message-ID: <20060102223147.GA55461@freebie.xs4all.nl> References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80965.1136240851@critter.freebsd.dk> X-OS: FreeBSD 6.0-STABLE User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:32:02 -0000 On Mon, Jan 02, 2006 at 11:27:31PM +0100, Poul-Henning Kamp wrote.. > In message <20060102221948.EBE475D09@ptavv.es.net>, "Kevin Oberman" writes: > > >Leap years are an artifact of a lousy calendar that has origins over 2 > >millennia ago. Many calendars have been proposed which fix this, but > >calendar reform is simply not going to happen in our society, but leap > >years are a known, non-varying and trivially calculable issue. No magic > >and trivial to handle. > > Interestingly, the main reason why calendar reform is a no-talk > issue seems to be that The Vatican owns the standardization area > of calendars because they have written all (relevant) standards for > the area in the past. > > According to one insider, none of the possible owners of a new > calendar (ITU, ISO & BIPM) can bring it on themselves to ask the > pope permission to take over the area. (ISO has documented > the current calendar, but go to some pains to make it clear > that they didn't come up with it.) > > Considering that a merry band of brits are still fighting to get > compensation for the 15 days they "lost" last time Brittain changed > calendar, the political and legal fallout will probably galvanize > the current calendar until something really drastic happens. Like the earth starting to rotate in the other direction? :-P -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:41:57 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B768D16A41F for ; Mon, 2 Jan 2006 22:41:57 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4956843D55 for ; Mon, 2 Jan 2006 22:41:57 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id D1CE9BC50; Mon, 2 Jan 2006 22:41:54 +0000 (UTC) To: Wilko Bulte From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 23:31:47 +0100." <20060102223147.GA55461@freebie.xs4all.nl> Date: Mon, 02 Jan 2006 23:41:54 +0100 Message-ID: <81077.1136241714@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:41:57 -0000 In message <20060102223147.GA55461@freebie.xs4all.nl>, Wilko Bulte writes: >> Considering that a merry band of brits are still fighting to get >> compensation for the 15 days they "lost" last time Brittain changed >> calendar, the political and legal fallout will probably galvanize >> the current calendar until something really drastic happens. > >Like the earth starting to rotate in the other direction? :-P Hard to tell. The most likely mechanism for such an event is the spinning-top like reversal of the Earths core relative to the mantle. I'm not sure if we know the relative masses and momentums well enough to tell exactly how the two will flip relative to the other, the friction between them is a big unknown variable too. If we assumed it happened without significant losses so that only the direction changed, then the calendar would still be good to go. Another mechanism could be changes to the Earths orbital parameters by vagabondeering masses passing through our solar system. As far as I know, we have no reliably geological or fossil records of that happening recently. A Roman empire style collapse of western civilization however is not merely a possibility, it's nearly a certainty, only the timescale being really in doubt. Poul-Henning -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:43:54 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D72B16A426 for ; Mon, 2 Jan 2006 22:43:54 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mo3so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id AF35843D49 for ; Mon, 2 Jan 2006 22:43:53 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd3mr7so.prod.shaw.ca (pd3mr7so-qfe3.prod.shaw.ca [10.0.141.23]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0ISH00CJHLT4RIC0@l-daemon> for current@freebsd.org; Mon, 02 Jan 2006 15:43:52 -0700 (MST) Received: from pn2ml6so.prod.shaw.ca ([10.0.121.150]) by pd3mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0ISH009QJLT4L220@pd3mr7so.prod.shaw.ca> for current@freebsd.org; Mon, 02 Jan 2006 15:43:52 -0700 (MST) Received: from [192.168.0.60] ([24.87.209.6]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0ISH00NS8LT32E70@l-daemon> for current@freebsd.org; Mon, 02 Jan 2006 15:43:52 -0700 (MST) Date: Mon, 02 Jan 2006 14:43:30 -0800 From: Colin Percival In-reply-to: <80965.1136240851@critter.freebsd.dk> To: Poul-Henning Kamp Message-id: <43B9AC92.2020400@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Accept-Language: en-us, en X-Enigmail-Version: 0.93.0.0 References: <80965.1136240851@critter.freebsd.dk> User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051228) Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:43:54 -0000 Poul-Henning Kamp wrote: > In message <20060102221948.EBE475D09@ptavv.es.net>, "Kevin Oberman" writes: >>Leap years are an artifact of a lousy calendar that has origins over 2 >>millennia ago. Many calendars have been proposed which fix this, but >>calendar reform is simply not going to happen in our society, but leap >>years are a known, non-varying and trivially calculable issue. No magic >>and trivial to handle. > > Interestingly, the main reason why calendar reform is a no-talk > issue seems to be that The Vatican owns the standardization area > of calendars because they have written all (relevant) standards for > the area in the past. Didn't the EU come up with the Feb 24 -> Feb 29 leap day change? Anyway, the Vatican certainly hasn't produced all the standards for our calendar -- they may have owned the calendar recently, but before their days it was mangled by Roman emperors, and I believe that it originated about 4000 years before that, along the banks of the Nile. Colin Percival From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 22:52:07 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32DBC16A41F; Mon, 2 Jan 2006 22:52:07 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FB6F43D67; Mon, 2 Jan 2006 22:52:06 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id BE2DCBC50; Mon, 2 Jan 2006 22:52:04 +0000 (UTC) To: Colin Percival From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jan 2006 14:43:30 PST." <43B9AC92.2020400@freebsd.org> Date: Mon, 02 Jan 2006 23:52:04 +0100 Message-ID: <81146.1136242324@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Matthias Andree , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 22:52:07 -0000 In message <43B9AC92.2020400@freebsd.org>, Colin Percival writes: >Poul-Henning Kamp wrote: >> In message <20060102221948.EBE475D09@ptavv.es.net>, "Kevin Oberman" writes: >>>Leap years are an artifact of a lousy calendar that has origins over 2 >>>millennia ago. Many calendars have been proposed which fix this, but >>>calendar reform is simply not going to happen in our society, but leap >>>years are a known, non-varying and trivially calculable issue. No magic >>>and trivial to handle. >> >> Interestingly, the main reason why calendar reform is a no-talk >> issue seems to be that The Vatican owns the standardization area >> of calendars because they have written all (relevant) standards for >> the area in the past. > >Didn't the EU come up with the Feb 24 -> Feb 29 leap day change? > >Anyway, the Vatican certainly hasn't produced all the standards for our >calendar Notice the telltale use of the "(relevant)" on my explanation :-) > -- they may have owned the calendar recently, but before their >days it was mangled by Roman emperors, Remember that the Pope is legally the successor in interest (Pontifex Maximus) of the empire of Rome (which is different from (both of!) the Roman empires). > and I believe that it originated >about 4000 years before that, along the banks of the Nile. That is less relevant, the question is if whoever touched it last still reads their mail. Poul-Henning -- 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. From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 23:22:15 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A84616A41F for ; Mon, 2 Jan 2006 23:22:15 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail14.syd.optusnet.com.au (mail14.syd.optusnet.com.au [211.29.132.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3896643D45 for ; Mon, 2 Jan 2006 23:22:13 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail14.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k02NM9GG014464 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Jan 2006 10:22:11 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k02NM9Hh046306; Tue, 3 Jan 2006 10:22:09 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k02NM9SO046305; Tue, 3 Jan 2006 10:22:09 +1100 (EST) (envelope-from pjeremy) Date: Tue, 3 Jan 2006 10:22:08 +1100 From: Peter Jeremy To: Poul-Henning Kamp Message-ID: <20060102232208.GC42228@cirb503493.alcatel.com.au> References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <80965.1136240851@critter.freebsd.dk> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 23:22:15 -0000 On Mon, 2006-Jan-02 23:27:31 +0100, Poul-Henning Kamp wrote: >Interestingly, the main reason why calendar reform is a no-talk >issue seems to be that The Vatican owns the standardization area >of calendars because they have written all (relevant) standards for >the area in the past. Actually, the Vatican has only been responsible for one variant of the Western calendar (the Gregorian). The Julian calendar predates the Christian church. The Vatican was open to calendar reform at the time because trying to combine elements of both Lunar and Solar calendars with a relatively inaccurate year length meant that Easter was heading for Christmas - which was felt to be undesirable. The actual algorithm was not developed within the Vatican but was promulgated by the Vatican because it was about the only international body which more than one or two countries would actually take any notice of - and even so, it wasn't until the 20th Century that (eg) Russia switched. Islam has its own calendar (with a particularly painful Leap Year calculation that gives very marginally more accuracy than the Gregorian). I'm not sure how the Chinese, Hindu, Japanese and Jewish calendars handle leap years. (I think that covers the major non- Gregorian calendars). >According to one insider, none of the possible owners of a new >calendar (ITU, ISO & BIPM) can bring it on themselves to ask the >pope permission to take over the area. The Gregorian algorithm is reasonably accurate - I think it's good for about 1 day in 3000 years. I don't know how this compares to the magnitude of miscellaneous perturbations in the Earth's orbit but it's likely to be a couple of thousand years before a further adjustmens is necessary. The obvious solution is to shift the Earth's orbit slightly towards the Sun to provide an even 365 day period. To make things even simpler, move the Earth a bit further to give a 360 day period and move the moon a bit further away to give a 30 day period. (Of course the downside of the latter change is that solar eclipses would become even rarer and might even disappear totally). With a bit of tweaking of the Earth's rotation, the need for leap seconds can also be removed. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Mon Jan 2 23:31:57 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 291B616A41F for ; Mon, 2 Jan 2006 23:31:57 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id C931C43D58 for ; Mon, 2 Jan 2006 23:31:56 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Mon, 02 Jan 2006 15:31:53 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 7D1345D07; Mon, 2 Jan 2006 15:31:53 -0800 (PST) To: Peter Jeremy In-reply-to: Your message of "Tue, 03 Jan 2006 10:22:08 +1100." <20060102232208.GC42228@cirb503493.alcatel.com.au> Date: Mon, 02 Jan 2006 15:31:53 -0800 From: "Kevin Oberman" Message-Id: <20060102233153.7D1345D07@ptavv.es.net> Cc: Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jan 2006 23:31:57 -0000 > Date: Tue, 3 Jan 2006 10:22:08 +1100 > From: Peter Jeremy > Sender: owner-freebsd-current@freebsd.org > > On Mon, 2006-Jan-02 23:27:31 +0100, Poul-Henning Kamp wrote: > >Interestingly, the main reason why calendar reform is a no-talk > >issue seems to be that The Vatican owns the standardization area > >of calendars because they have written all (relevant) standards for > >the area in the past. > > Actually, the Vatican has only been responsible for one variant of the > Western calendar (the Gregorian). The Julian calendar predates the > Christian church. The Vatican was open to calendar reform at the time > because trying to combine elements of both Lunar and Solar calendars > with a relatively inaccurate year length meant that Easter was heading > for Christmas - which was felt to be undesirable. The actual > algorithm was not developed within the Vatican but was promulgated by > the Vatican because it was about the only international body which > more than one or two countries would actually take any notice of - and > even so, it wasn't until the 20th Century that (eg) Russia switched. > > Islam has its own calendar (with a particularly painful Leap Year > calculation that gives very marginally more accuracy than the > Gregorian). I'm not sure how the Chinese, Hindu, Japanese and Jewish > calendars handle leap years. (I think that covers the major non- > Gregorian calendars). > > >According to one insider, none of the possible owners of a new > >calendar (ITU, ISO & BIPM) can bring it on themselves to ask the > >pope permission to take over the area. > > The Gregorian algorithm is reasonably accurate - I think it's good for > about 1 day in 3000 years. I don't know how this compares to the > magnitude of miscellaneous perturbations in the Earth's orbit but it's > likely to be a couple of thousand years before a further adjustmens is > necessary. > > The obvious solution is to shift the Earth's orbit slightly towards > the Sun to provide an even 365 day period. To make things even > simpler, move the Earth a bit further to give a 360 day period and > move the moon a bit further away to give a 30 day period. (Of course > the downside of the latter change is that solar eclipses would become > even rarer and might even disappear totally). With a bit of tweaking > of the Earth's rotation, the need for leap seconds can also be removed. We keep trying to define the universe and keep getting annoyed when the universe fails to cooperate. I still want pi to be 3.14. Yeah, it would warp the universe rather badly, but would make the arithmetic so much easier. And I guess sin(90) would no longer be rational, either. Guess we just can't win. :-( I like the old "joke": Q. How do you make God laugh? A. Tell him your plans. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 00:25:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D6BB16A41F for ; Tue, 3 Jan 2006 00:25:44 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3854B43D46 for ; Tue, 3 Jan 2006 00:25:43 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id EAF4C119FA; Mon, 2 Jan 2006 19:25:41 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 478C61A08AA; Mon, 2 Jan 2006 19:25:36 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17337.50303.811554.900031@canoe.dclg.ca> Date: Mon, 2 Jan 2006 19:25:35 -0500 To: freebsd-current@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 18) "Social Property" XEmacs Lucid Subject: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 00:25:44 -0000 I've got a laptop with the PC-CARD wi0 in it. I've currently got "ifconfig_wi0="DHCP"" in the rc.conf file. dhclient runs and everything is fine... until the association drops for a little bit. Then it looses the IP address and dhclient never relizes that it's associated again. Very annoying. I thought the whole point was that dhclient was suppose to notice these events? Dhclient in this case never quits ... and ... as far as I can tell, never looks for an address again (athough I'm not going to wait a whole day for the dhcp lease to timeout). Has anyone looked into this? This is on 6.0-p1. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 00:45:19 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C202D16A41F for ; Tue, 3 Jan 2006 00:45:19 +0000 (GMT) (envelope-from cisbjc@cs.unisa.edu.au) Received: from reason.levels.unisa.edu.au (reason.levels.unisa.edu.au [130.220.33.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECA5643D4C for ; Tue, 3 Jan 2006 00:45:18 +0000 (GMT) (envelope-from cisbjc@cs.unisa.edu.au) Received: from [192.168.0.91] (cis220313.levels.unisa.edu.au [130.220.37.202]) by reason.levels.unisa.edu.au (8.12.10/8.12.10) with ESMTP id k030j1vp018437; Tue, 3 Jan 2006 11:15:03 +1030 (CST) Message-ID: <43B9C7F1.5030303@cs.unisa.edu.au> Date: Tue, 03 Jan 2006 11:10:17 +1030 From: Benjamin Close User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050627) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Gilbert References: <17337.50303.811554.900031@canoe.dclg.ca> In-Reply-To: <17337.50303.811554.900031@canoe.dclg.ca> X-Enigmail-Version: 0.89.6.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 00:45:19 -0000 David Gilbert wrote: >I've got a laptop with the PC-CARD wi0 in it. I've currently got >"ifconfig_wi0="DHCP"" in the rc.conf file. dhclient runs and >everything is fine... until the association drops for a little bit. >Then it looses the IP address and dhclient never relizes that it's >associated again. Very annoying. > >I thought the whole point was that dhclient was suppose to notice >these events? > >Dhclient in this case never quits ... and ... as far as I can tell, >never looks for an address again (athough I'm not going to wait a >whole day for the dhcp lease to timeout). > >Has anyone looked into this? This is on 6.0-p1. > > I have a slightly different but some what related issue. I can't get an initial IP. The ironic thing is sometimes I can, other times I can't. It seems to be related to whether the lease has expired on the server or not. Commenting out line 274 in dhclient.c seems to fix the problem as a temporary solution, but it's not the correct fix. There was one point after the dhcp import where things worked but it might have been luck. I've been trying to trace this down for a while. I believe it's a bug in the wi code. Two Dissassociate events are sent to the 80211 state machine by dhclient and it gets put in the INIT state, later the card gets link and it puts the 80211 state machine in the RUN state, though it's an invalid state transition. I've tried forcing it to the ASSOC state first with minor luck but I've not yet been able to get it consistent. I'll try and provide more concrete data tonight... Cheers, Benjamin -- 3D Research Associate / System Administrator +61 8 8302 3669 School of Computer and Information Science Room D1-07, ML Campus University of South Australia Mawson Lakes Blvd. Benjamin.Close@cs.unisa.edu.au South Australia, 5095 F00D C83D 5F7E 5561 DF91 B74D E602 CAA3 4842 B5B4 From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 01:07:03 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0146C16A41F for ; Tue, 3 Jan 2006 01:07:03 +0000 (GMT) (envelope-from jonathan@fosburgh.org) Received: from pop-siberian.atl.sa.earthlink.net (pop-siberian.atl.sa.earthlink.net [207.69.195.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85BF043D55 for ; Tue, 3 Jan 2006 01:07:02 +0000 (GMT) (envelope-from jonathan@fosburgh.org) Received: from user-0cetssr.cable.mindspring.com ([24.238.243.155] helo=gw.fosburgh.org) by pop-siberian.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1Etade-0006UP-00; Mon, 02 Jan 2006 20:06:58 -0500 Received: by gw.fosburgh.org (Postfix, from userid 1001) id AC49CB585; Mon, 2 Jan 2006 19:07:04 -0600 (CST) From: Jonathan Fosburgh To: freebsd-current@freebsd.org Date: Mon, 2 Jan 2006 19:07:03 -0600 User-Agent: KMail/1.9.1 References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> In-Reply-To: <43B9C7F1.5030303@cs.unisa.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601021907.04098.jonathan@fosburgh.org> Cc: David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 01:07:03 -0000 On Monday 02 January 2006 18:40, Benjamin Close wrote: > >Has anyone looked into this? This is on 6.0-p1. > > I have a slightly different but some what related issue. I can't get an > initial IP. > The ironic thing is sometimes I can, other times I can't. It seems to be > related to whether the lease has expired on the server or not. > Commenting out line 274 in dhclient.c seems to fix the problem as a > temporary solution, but it's not the correct fix. > There was one point after the dhcp import where things worked but it > might have been luck. > On 6.0-STABLE (whould this be forwarded to -stable as well?) I have had a problem with dhclient not renewing the address when the lease expires. Note, I am using dhclient on dc0. My fix is to kill dhclient and then restart it. -- Jonathan Fosburgh From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 01:45:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 14DED16A41F for ; Tue, 3 Jan 2006 01:45:14 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp3.Stanford.EDU (smtp3.Stanford.EDU [171.67.16.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B27843D5D for ; Tue, 3 Jan 2006 01:45:12 +0000 (GMT) (envelope-from richw@richw.org) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp3.Stanford.EDU (8.12.11/8.12.11) with ESMTP id k031j8Wi024506 for ; Mon, 2 Jan 2006 17:45:11 -0800 Received: from [172.29.0.21] (evilempire.richw.org [172.29.0.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: richw) by whodunit.richw.org (Postfix) with ESMTP id 948273C9ED; Mon, 2 Jan 2006 17:45:08 -0800 (PST) Date: Mon, 02 Jan 2006 17:45:08 -0800 From: Rich Wales User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: current@freebsd.org References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> <20060102232208.GC42228@cirb503493.alcatel.com.au> In-Reply-To: <20060102232208.GC42228@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060103014508.948273C9ED@whodunit.richw.org> Cc: Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 01:45:14 -0000 Peter Jeremy wrote: > Islam has its own calendar (with a particularly painful Leap Year > calculation that gives very marginally more accuracy than the > Gregorian). Are you perhaps thinking about the Iranian (Persian) calendar here? The Islamic calendar, AFAIK, is a 12-month lunar calendar which makes =no= attempt whatsoever to stay in sync with the seasons. > I'm not sure how the Chinese, Hindu, Japanese and Jewish calendars > handle leap years. The Jewish calendar uses a 13th lunar month in seven out of every 19 years. Additionally, some months can have either 29 or 30 days, depending on complex calculations. Rich Wales Palo Alto, CA, USA richw@richw.org http://www.richw.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 02:24:26 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5DF516A420 for ; Tue, 3 Jan 2006 02:24:26 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B4EB43D8F; Tue, 3 Jan 2006 02:24:20 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k032McEE090642; Tue, 3 Jan 2006 02:23:57 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43B9DFD9.9050509@freebsd.org> Date: Tue, 03 Jan 2006 10:22:17 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rich Wales References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> <20060102232208.GC42228@cirb503493.alcatel.com.au> <20060103014508.948273C9ED@whodunit.richw.org> In-Reply-To: <20060103014508.948273C9ED@whodunit.richw.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 02:24:26 -0000 Rich Wales wrote: > > Peter Jeremy wrote: > >> Islam has its own calendar (with a particularly painful Leap Year >> calculation that gives very marginally more accuracy than the >> Gregorian). > > > Are you perhaps thinking about the Iranian (Persian) calendar here? > > The Islamic calendar, AFAIK, is a 12-month lunar calendar which makes > =no= attempt whatsoever to stay in sync with the seasons. > >> I'm not sure how the Chinese, Hindu, Japanese and Jewish calendars >> handle leap years. > Here is some descriptions of the traditional Chinese calendar (the lunar calendar) http://webexhibits.org/calendars/calendar-chinese.html Note that Chinese farming is based on the lunar calender. > > The Jewish calendar uses a 13th lunar month in seven out of every > 19 years. Additionally, some months can have either 29 or 30 days, > depending on complex calculations. > > Rich Wales > Palo Alto, CA, USA > richw@richw.org > http://www.richw.org Regards, David Xu From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 04:50:13 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51F2616A424; Tue, 3 Jan 2006 04:50:13 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id B100343D4C; Tue, 3 Jan 2006 04:50:12 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k034nh85017560; Mon, 2 Jan 2006 21:49:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 02 Jan 2006 21:49:56 -0700 (MST) Message-Id: <20060102.214956.40574756.imp@bsdimp.com> To: deischen@freebsd.org From: "M. Warner Losh" In-Reply-To: <20060101.212552.85411680.imp@bsdimp.com> References: <43B83262.1090907@fastmail.fm> <20060101.212552.85411680.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 02 Jan 2006 21:49:44 -0700 (MST) Cc: pbowen@fastmail.fm, freebsd-current@freebsd.org Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 04:50:13 -0000 In message: <20060101.212552.85411680.imp@bsdimp.com> "M. Warner Losh" writes: : In message: : Daniel Eischen writes: : : On Sun, 1 Jan 2006, Patrick Bowen wrote: : : : : > Hello and Happy New Year; : : > : : > I just bought a D-Link DWL-G630 Wireless G Adapter for my laptop (Dell : : > Latitude C-600), and it worked fine until I cvsup'ed last nights sources : : > (12/31/05) and did canonical rebuild. Now the machine panics whenever I : : > plug the card in. : : : : Same here, though I got the kernel panic at boot when I had inserted during : : the boot. The panic was in cardbus_read_tuple() also. I can post the : : hand scribed trace to anyone interested if necessary. : : No need. I have the card here, and it fails too. All my other cards : work, but the atheros card is the only one that stores the CIS in a : bar that I have (I'm sure that others do as well, but they aren't in : the 10 cards I grabbed to test with). This appears to be resource : related in some way, since it appears that we're getting a resource of : '0' back. I'm trying to debug it now. : : Sorry for the hassle. I've just commited changes that fix it for me. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:10:50 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 639E716A41F for ; Tue, 3 Jan 2006 05:10:50 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4A0743D53 for ; Tue, 3 Jan 2006 05:10:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k035AYWT017669; Mon, 2 Jan 2006 22:10:35 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 02 Jan 2006 22:10:46 -0700 (MST) Message-Id: <20060102.221046.75255380.imp@bsdimp.com> To: matthias.andree@gmx.de From: "M. Warner Losh" In-Reply-To: References: <73774.1136109554@critter.freebsd.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 02 Jan 2006 22:10:35 -0700 (MST) Cc: phk@phk.freebsd.dk, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 05:10:50 -0000 Hit the delete key now if you don't care why I hate leapseconds so much :-) In message: Matthias Andree writes: : Poul-Henning Kamp writes: : : > http://phk.freebsd.dk/misc/leapsecond.txt : > : > Notice how CLOCK_REALTIME recycles the 1136073599 second. : : Well, it is in accordance with POSIX, but that doesn't mean its : "correct". POSIX is broken by design. It does not define what happens to system time during a leap second. : How does the POSIX "consistency" babble, and particularly the FreeBSD 5 : or 6 implementation, make sure that "make(1)" or other application : doesn't see a file created on 2005-12-31T23:59:60.1Z as older than a : file created 0.9 seconds earlier, on 2005-12-31T23:59:59.2Z, because of : the time warp caused by POSIX's demand to ignore leap seconds? It doesn't. FreeBSD (and other systems) run in UTC. UTC is a timescale that jumps. There are inconsistancies in it, and math with UTC time stamps is consequently hard. : Are there plans to add monotonous TAI clock interfaces to FreeBSD 7 so : we have an alternative to the differential CLOCK_MONOTONIC and the jumpy : CLOCK_REALTIME? Is any reader of this message aware of efforts to : standardize such a TAI clock? Nope. That's not standard. Getting a leap second table is hard. You *MUST* have one, no matter what time scale you run in. If you run in UTC, you can get away with being blissfully ignorant (if you don't care about time_t subtraction accross leap seconds). If you run in TAI, you need to have a complete table in order to print times correctly. It is even worse than this. As of this instant, no one can tell me with absolute certainty, how many seconds will elapse between June 29, 2006 0:00:00 and July 2 0:00:00. No one. We'll know in a few days or weeks when Bulletin C is published. No one will know for sure the answer for Dec 30 2006 0:0:0 to Jan 2 2007, 0:0:0 until sometime in July. : The FreeBSD 6 zoneinfo stuff seems to be ready for leap seconds, if only : someone uses -L leapseconds with zic. It appears some systems (SUSE : Linux) have been doing such for a subdirectory right/ : (i. e. TZ=right/Europe/Berlin) for half a decade now. We could also add the right directory. But "right" here isn't really right. There are lots of issues with it for people that don't expect the system time to be in TAI... One has been able to add LEAPSECONDS=yes to make.conf for a very long time.nnn The biggest problem with compiling leap seconds into this is that you can only be sure that leap seconds are right for at most 6 months. Sure, you can make statistical statements about how likely a leap second is or isn't going to be, but this non-determinism is a big problem. There's no way you can deploy a system and have a sane leap second table without a connection to the outside world... I'll bet that the Debian system was installed 5 years ago with the so-called 'right' tables has only had the right leap table for this past leap seconds for 3-4 months tops. This last leap second was not announced until July 4, 2005. Leap seconds are evil. For such a simple concept, they are damn hard to get right. China's time broadcast was interrupted for 61s at the leap second. Others have reported anomalous behavior in the ntp stratum 1 servers, and other time signals had various anomalies (including the cool real-time spectrum trace of many time signals, with annotations: http://wwwhome.cs.utwente.nl/~ptdeboer/ham/sdr/leapsecond.html). Leap seconds are hard and I hate them. But I've been paid for over 120 hours in the past couple of years to make sure that we got them right. It was some of these hours that ensured that the proper fixes to FreeBSD were integrated well in advance of this last leap second. Yet, I'd give up 3 weeks pay to never have to deal with leap seconds again :-). Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:14:16 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB54C16A41F for ; Tue, 3 Jan 2006 05:14:15 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49F4743D62 for ; Tue, 3 Jan 2006 05:14:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k035DWul017706; Mon, 2 Jan 2006 22:13:32 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 02 Jan 2006 22:13:44 -0700 (MST) Message-Id: <20060102.221344.32719867.imp@bsdimp.com> To: matthias.andree@gmx.de From: "M. Warner Losh" In-Reply-To: <20060102162117.GB14097@merlin.emma.line.org> References: <79206.1136213035@critter.freebsd.dk> <20060102162117.GB14097@merlin.emma.line.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 02 Jan 2006 22:13:32 -0700 (MST) Cc: phk@phk.freebsd.dk, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 05:14:16 -0000 In message: <20060102162117.GB14097@merlin.emma.line.org> Matthias Andree writes: : I'm only annoyed that POSIX pretends leap seconds were non-existant, and : even more because I have no satisfactory answer to my question how : FreeBSD knows that a file created at 23:59:59.2 is older than a file : created at 23:59:60.1 if the timestamp is recycled but rather : unsubstantiated assumptions about the amount of research I have done. I : don't want to bore readers on mailing lists with epic breadth... It can't know. POSIX's time_t is ambiguous. Get annoyed, but get used to it. :-) : > Second, reliably getting hold of the UTC-TAI delta is exactly the : > same job as reliably getting hold of leap-second information. : : I'm aware of this problem, and I am aware that this is, according to : Dave Mills (which he underlined again in January 2004), the showstopper : that prevented NTPD from switching to TAI, because many applications : desire UTC and knowing leap seconds only 6 months in advance is too : short notice for autonomous appliances. Yup. : > Third, it sounds like you really havn't studied this to any dept : > since, quite clearly, you attack the problem from the wrong end : > (making FreeBSD non-portable) rather than the right end (make : > sure that computer standards represent time according to our : > definition of time). : : Wrong, I have read up a bit (Mills, Kuhn, your posts and FAQ entries), : and made up my mind - just because I'm not writing a dozen cubits of : parchment full with prose doesn't mean I don't know, and I am not : suggesting to warp time(3) or similar incompatible changes. : : (I omitted mention of Dan J. Bernstein who is also in the favor of the : TAI approach because that would lead to even more bikeshedding.) : : Markus Kuhn suggested adding a new interface, or as an alternative : solution, smoothing the UTC by slewing the clock ("UTS") for the past : 1,000 seconds before the insertion or deletion of the leap second. : : TAI is the monotonous timescale that computers should have been using : since Epoch, but I'm not sure who was there first, TAI or UNIX. : : Why "TAI is not a real-time clock" is irrelevant is that no-one uses : internal timestamps for presentation anyways. The goals are: 1. : consistent time across POSIX computers, 2. monotonic clocks inside POSIX : computers (which is an extension currently), 3. a time presentation to : end users that matches the astronomical view of "noon". There are no standards. No matter what we do here, we have to invent something. : > You can either fix POSIX to cope correctly with leap-seconds or you : > can abandon leap seconds which also fixes POSIX for the future, : > but adding non-standard timescales to FreeBSD will not solve the : > problem. : > : > I think abandonning leap seconds so that POSIX becomes correct is : > by several orders of magnitude the more economical solution. : : Does POSIX specify a solution to the problem with the ordering of the : two files' age I outlined above? Not to my knowledge, so how can it : possibly be "correct"? Nope. Posix sucks. : > The fact that the global network of NTP servers which are run by : > the most "time" interested and motivated people in the computing : > world couldn't get a leapsecond right this time only reinforces : > this view. : : Any precendents where the leap second didn't work? URL suffices. : : It appears all POSIX machines I look after got the leap second right one : way or another, the Linux machines slewed their clocks by 500 ppm, what : the Solaris 8 machines did, I didn't check, since I have more : interesting things to do on New Year's Day at 1 a.m., but they didn't : log any difficulties, the FreeBSD machines were offline and resynched : through ntpdate at bootup (no info), so I'm taking your word UTC remained : correct. FreeBSD properly stepped the time. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:20:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A480116A41F for ; Tue, 3 Jan 2006 05:20:03 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 564B343D4C for ; Tue, 3 Jan 2006 05:20:02 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k035HHKQ017728; Mon, 2 Jan 2006 22:17:17 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 02 Jan 2006 22:17:29 -0700 (MST) Message-Id: <20060102.221729.22019809.imp@bsdimp.com> To: matthias.andree@gmx.de From: "M. Warner Losh" In-Reply-To: References: <80148.1136231640@critter.freebsd.dk> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 02 Jan 2006 22:17:18 -0700 (MST) Cc: phk@phk.freebsd.dk, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 05:20:03 -0000 In message: Matthias Andree writes: : >>It appears all POSIX machines I look after got the leap second right one : >>way or another[...] : > : > None of them got it right by any strech of the imagination because : > it is impossible to get it right and be POSIX compliance. : : Wow, and you claim FreeBSD handles it correctly. Maybe you should spend all the energy working on a solution rather than casting stones. I have personally put in weeks of my time to get leap seconds right. The problem is that your notion of right and mine are different and your holier than thou attitude is not helpful. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:20:09 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE7E616A41F for ; Tue, 3 Jan 2006 05:20:09 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EBC943D5F for ; Tue, 3 Jan 2006 05:20:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k035IwKQ017730; Mon, 2 Jan 2006 22:18:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 02 Jan 2006 22:19:10 -0700 (MST) Message-Id: <20060102.221910.122060994.imp@bsdimp.com> To: matthias.andree@gmx.de From: "M. Warner Losh" In-Reply-To: <20060102211956.GA10928@merlin.emma.line.org> References: <80432.1136235223@critter.freebsd.dk> <20060102211956.GA10928@merlin.emma.line.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 02 Jan 2006 22:18:58 -0700 (MST) Cc: phk@phk.freebsd.dk, current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 05:20:09 -0000 In message: <20060102211956.GA10928@merlin.emma.line.org> Matthias Andree writes: : On Mon, 02 Jan 2006, Poul-Henning Kamp wrote: : : > In message , Matthias Andree writes: : > : > >And tell me one reason why the leap second must be discontinued while : > >the leap day (Feb 29th) can be carried on. It's the same story, : > >irregular rollover, inserting one particular unit of time. : > : > You are clearly not thinking rationally here. : > : > I know already now that year 2048 will be a leap year, but I still : > don't know if there will be a leap second on june 30th 2006. : : And you can predict the DST rules for all major countries for 2048? Who : says the EU won't discontinue DST effective 2008? We don't know yet. : : You suggest UTC needs to be used because civil time matters, yet at the : same time UTC were broken, and thus POSIX were broken, but could not be : blamed for picking UTC. : : Leap days (called leap year, to compensate for earth orbiting the sun), : leap hours (called daylight savings time, completely artificial); aren't : questioned, but leap seconds are. : : Is it just me who sees inconsistencies in your argumentation here? No. UTC has no timezones, so is nearly predictable for long stretches of time. Leap seconds are a random pertebtation that can only be known as a table. Leap days are know for the next several thousand years. : No offense, but I simply don't get your point. Another question: Did you : mean to write "FreeBSD handles leapsecond in POSIX compliance" for the : subject? FreeBSD did it right. End of story. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 05:41:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3A1916A41F for ; Tue, 3 Jan 2006 05:41:28 +0000 (GMT) (envelope-from dalius.dobravolskas@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 026B943D55 for ; Tue, 3 Jan 2006 05:41:27 +0000 (GMT) (envelope-from dalius.dobravolskas@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1666250wxc for ; Mon, 02 Jan 2006 21:41:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Y2nXzqYkFSk9M+zOfxgv5kwuhVRvyuHnzAUUfFWOHJDVMR+McfFEJl0J+miO4/BnlAiGaUCSG7EAgh10mEhh2FW6rlSIHlo9WrFIoXh9a5MDiplXWojSabs/dzQkTfKG9zaSCm7JMOPoSPxmYjYJhiRBh8PmfQJzUOtzBCCB/y0= Received: by 10.70.53.16 with SMTP id b16mr13163422wxa; Mon, 02 Jan 2006 21:41:27 -0800 (PST) Received: by 10.70.54.11 with HTTP; Mon, 2 Jan 2006 21:41:27 -0800 (PST) Message-ID: <98dd087e0601022141r350d48d5q@mail.gmail.com> Date: Tue, 3 Jan 2006 07:41:27 +0200 From: Dalius Dobravolskas To: freebsd-current@freebsd.org In-Reply-To: <98dd087e0512270540h44b6e89bh@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <98dd087e0512270540h44b6e89bh@mail.gmail.com> Subject: Re: mouse and extra buttons X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 05:41:28 -0000 Hello, On 27/12/05, Dalius Dobravolskas wrote: > I need help with mouse having extra buttons. I wrote here about before one week. So the problem seems to be that my mouse is more UHID device than usb mouse. However UHID support for mouses seems to be incomplete. I have NGS mouse. Just in case someone else meets similar problem ;-) -- Dalius From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 06:18:10 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B364616A41F for ; Tue, 3 Jan 2006 06:18:10 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail11.syd.optusnet.com.au (mail11.syd.optusnet.com.au [211.29.132.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED25E43D58 for ; Tue, 3 Jan 2006 06:18:09 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail11.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k036HqCw003702 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Jan 2006 17:17:53 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k036HqHh046693; Tue, 3 Jan 2006 17:17:52 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k036HqMx046692; Tue, 3 Jan 2006 17:17:52 +1100 (EST) (envelope-from pjeremy) Date: Tue, 3 Jan 2006 17:17:52 +1100 From: Peter Jeremy To: "M. Warner Losh" Message-ID: <20060103061752.GE42228@cirb503493.alcatel.com.au> References: <73774.1136109554@critter.freebsd.dk> <20060102.221046.75255380.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060102.221046.75255380.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 06:18:10 -0000 On Mon, 2006-Jan-02 22:10:46 -0700, M. Warner Losh wrote: >The biggest problem with compiling leap seconds into this is that you >can only be sure that leap seconds are right for at most 6 months. >Sure, you can make statistical statements about how likely a leap >second is or isn't going to be, but this non-determinism is a big >problem. There's no way you can deploy a system and have a sane leap >second table without a connection to the outside world... The Islamic calendar is based on lunar _sightings_: If it's cloudy, the calendar shifts a day. This wreaks even more havoc than the odd leap-second and many Islamic countries have therefore switched to using almanac based dates. Actually, I'd suggest that you can't build a system that keeps any sort of accurate time without a connection to the outside world or a quite substantial budget. If you assume a leap second every 5 years then the difference between UTC and TAI is about 6e-9 - being able to tell the difference requires an atomic clock - which isn't common in embedded systems. >Leap seconds are hard and I hate them. Which of the competing alternatives would you prefer? -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 06:37:02 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43E6016A41F for ; Tue, 3 Jan 2006 06:37:02 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EEBC43D45 for ; Tue, 3 Jan 2006 06:37:01 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail17.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k036avPd025837 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Jan 2006 17:36:58 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k036avHh046716; Tue, 3 Jan 2006 17:36:57 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k036avZX046715; Tue, 3 Jan 2006 17:36:57 +1100 (EST) (envelope-from pjeremy) Date: Tue, 3 Jan 2006 17:36:56 +1100 From: Peter Jeremy To: Rich Wales Message-ID: <20060103063656.GF42228@cirb503493.alcatel.com.au> References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> <20060102232208.GC42228@cirb503493.alcatel.com.au> <20060103014508.948273C9ED@whodunit.richw.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103014508.948273C9ED@whodunit.richw.org> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 06:37:02 -0000 On Mon, 2006-Jan-02 17:45:08 -0800, Rich Wales wrote: >Peter Jeremy wrote: > >>Islam has its own calendar (with a particularly painful Leap Year >>calculation that gives very marginally more accuracy than the >>Gregorian). > >Are you perhaps thinking about the Iranian (Persian) calendar here? Having checked, it seems I mis-remembered (it was an article I read some years ago and I was certain that the author claimed that it was Islamic). Looking at the Iranian calendar, it matches the leap year configuration I recalled. >The Islamic calendar, AFAIK, is a 12-month lunar calendar which makes >=no= attempt whatsoever to stay in sync with the seasons. The Islamic calendar (at least the concensus from some googling) appears to have 11 leap years in a 30 (lunar) year cycle - and it seems that there isn't even general agreement on which years are leap years. >>I'm not sure how the Chinese, Hindu, Japanese and Jewish calendars >>handle leap years. > >The Jewish calendar uses a 13th lunar month un seven out of every 19 >years. Additionally, some months can have either 29 or 30 days, >depending on complex calculations. Compared to which, the Gregorian calendar appears quite sane :-). I'll stick by my assertion that the easiest solution is to move the earth and moon into orbits that have periods that are an integral number of days. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 07:26:11 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76CB016A41F; Tue, 3 Jan 2006 07:26:11 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id E091243D46; Tue, 3 Jan 2006 07:26:10 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k037Q9o5073665; Tue, 3 Jan 2006 02:26:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k037Q9TH032775; Tue, 3 Jan 2006 02:26:09 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 43BE27302F; Tue, 3 Jan 2006 02:26:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060103072609.43BE27302F@freebsd-current.sentex.ca> Date: Tue, 3 Jan 2006 02:26:09 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 07:26:11 -0000 TB --- 2006-01-03 06:37:21 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-03 06:37:21 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2006-01-03 06:37:21 - cleaning the object tree TB --- 2006-01-03 06:37:42 - checking out the source tree TB --- 2006-01-03 06:37:42 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2006-01-03 06:37:42 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-03 06:51:57 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-03 06:51:57 - cd /src TB --- 2006-01-03 06:51:57 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ng.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_nw.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_pr.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_sv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c: In function `getaddrinfo': /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:342: error: structure has no member named `_ai_pad' /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:373: error: structure has no member named `_ai_pad' *** Error code 1 Stop in /src/lib/bind/bind. *** Error code 1 Stop in /src/lib/bind. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-03 07:26:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-03 07:26:08 - ERROR: failed to build world TB --- 2006-01-03 07:26:08 - tinderbox aborted TB --- 0.50 user 1.66 system 2927.32 real From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 08:55:53 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58F1C16A41F for ; Tue, 3 Jan 2006 08:55:53 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B56C43D5E for ; Tue, 3 Jan 2006 08:55:51 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k038t4xB018986; Tue, 3 Jan 2006 01:55:04 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 03 Jan 2006 01:55:16 -0700 (MST) Message-Id: <20060103.015516.21274860.imp@bsdimp.com> To: PeterJeremy@optushome.com.au From: "M. Warner Losh" In-Reply-To: <20060103061752.GE42228@cirb503493.alcatel.com.au> References: <20060102.221046.75255380.imp@bsdimp.com> <20060103061752.GE42228@cirb503493.alcatel.com.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 03 Jan 2006 01:55:04 -0700 (MST) Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 08:55:53 -0000 In message: <20060103061752.GE42228@cirb503493.alcatel.com.au> Peter Jeremy writes: : On Mon, 2006-Jan-02 22:10:46 -0700, M. Warner Losh wrote: : >The biggest problem with compiling leap seconds into this is that you : >can only be sure that leap seconds are right for at most 6 months. : >Sure, you can make statistical statements about how likely a leap : >second is or isn't going to be, but this non-determinism is a big : >problem. There's no way you can deploy a system and have a sane leap : >second table without a connection to the outside world... : : The Islamic calendar is based on lunar _sightings_: If it's cloudy, : the calendar shifts a day. This wreaks even more havoc than the : odd leap-second and many Islamic countries have therefore switched : to using almanac based dates. : : Actually, I'd suggest that you can't build a system that keeps any : sort of accurate time without a connection to the outside world or a : quite substantial budget. If you assume a leap second every 5 years : then the difference between UTC and TAI is about 6e-9 - being able Actually, that's wrong. If you assume a leap second every 18 months you'd be better off, in the long run. : to tell the difference requires an atomic clock - which isn't common : in embedded systems. Unless those embedded systems deal with time. I build GPS based NTP servers, amoung other things, in my day job. You have to get the right second every time, or people won't buy your products. This every time includes cases where the GPS reciever has been a powered down spare for the past 9 months and therefore has no notion of the leap seconds that have accumulated. This means it has to have an extra long startup period while the GPS receive gets a new almanac. This long wait is irritating to a customer, as you might imagine. However, having to handle both cases in your code base is irritating to a programmer. We can't start broadcasting time without being certain that it is right. The probelm with the dormant system is that we can learn only what the current table is, not what all the past leap seconds were if a GPS receiver has been off for a while, unless the computer is connected to the internet (most of ours are not). This creates difficulties when populating leap second tables, as well as any elapsed time computations with times starting in the past. This limts what you can do, but not substantially as you can usually recover the last leap second if it was recent enough. GPS gives only the current and future values, which is mostly good enough for most things. However, testing these different scenarios can be a royal PITA. Knowing that you need to test them is even harder. Knowing what the actual GPS receiver will report over a leap second is also important. Assume that the receiver will lie to you, because they all do in some manner. This requires that you build lots of knowledge of the rules of leap seconds into your application. The more of these you build in, the more changes that you'll have a bug like some GPS paced clocked had back on September 30 where they glitched a second because the leap second future indicator was turned on in GPS more than 3 months before the leap second happened (the data in GPS correctly said end of year, but these clocks glitched). Other GPS receivers have problems where they won't report the correct UTC GPS offset until a new almanac is downloaded after a leapsecond (if you relied on this data, then woe be to you). : >Leap seconds are hard and I hate them. : : Which of the competing alternatives would you prefer? Kill all leapseconds. They don't matter. Move the time zones every few hundred/thousand years to keep in sync. Noon is an artificial construct these days anyway, as solar noon can vary by an hour in most normal timezones (and more in the weird edge cases like Togo). Failing that, decide today what the next 10 years of leap seconds will be and publish that table. Append to it yearly 1 years (or more) worth of future leap seconds. This would require allowing DUT1 to grow beyond .9s, but would keep things right on the average and be more predictable than the mess we have today. Warner From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 09:21:50 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 261F416A423; Tue, 3 Jan 2006 09:21:50 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CCA143D8A; Tue, 3 Jan 2006 09:21:30 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [80.177.232.250]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id k039KwpS064035; Tue, 3 Jan 2006 09:20:59 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Tue, 3 Jan 2006 09:20:56 +0000 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> <20060102.221046.75255380.imp@bsdimp.com> <20060103061752.GE42228@cirb503493.alcatel.com.au> In-Reply-To: <20060103061752.GE42228@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601030920.57890.dfr@nlsystems.com> X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.87.1/1225/Mon Jan 2 17:54:07 2006 on itchy.rabson.org X-Virus-Status: Clean Cc: Peter Jeremy , current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 09:21:50 -0000 On Tuesday 03 January 2006 06:17, Peter Jeremy wrote: > On Mon, 2006-Jan-02 22:10:46 -0700, M. Warner Losh wrote: > > >Leap seconds are hard and I hate them. > > Which of the competing alternatives would you prefer? I think we should fit gigantic rocket motors around the equator and use them to regularlise the earth's spin :-) From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 09:21:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 261F416A423; Tue, 3 Jan 2006 09:21:50 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3CCA143D8A; Tue, 3 Jan 2006 09:21:30 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from herring.rabson.org (herring.rabson.org [80.177.232.250]) by itchy.rabson.org (8.13.3/8.13.3) with ESMTP id k039KwpS064035; Tue, 3 Jan 2006 09:20:59 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-current@freebsd.org Date: Tue, 3 Jan 2006 09:20:56 +0000 User-Agent: KMail/1.8.2 References: <73774.1136109554@critter.freebsd.dk> <20060102.221046.75255380.imp@bsdimp.com> <20060103061752.GE42228@cirb503493.alcatel.com.au> In-Reply-To: <20060103061752.GE42228@cirb503493.alcatel.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601030920.57890.dfr@nlsystems.com> X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on itchy.rabson.org X-Virus-Scanned: ClamAV 0.87.1/1225/Mon Jan 2 17:54:07 2006 on itchy.rabson.org X-Virus-Status: Clean Cc: Peter Jeremy , current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 09:21:50 -0000 On Tuesday 03 January 2006 06:17, Peter Jeremy wrote: > On Mon, 2006-Jan-02 22:10:46 -0700, M. Warner Losh wrote: > > >Leap seconds are hard and I hate them. > > Which of the competing alternatives would you prefer? I think we should fit gigantic rocket motors around the equator and use them to regularlise the earth's spin :-) From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 09:42:49 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC5FC16A41F for ; Tue, 3 Jan 2006 09:42:49 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7E2843D5E for ; Tue, 3 Jan 2006 09:42:48 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id k039gkPt012387 for ; Tue, 3 Jan 2006 10:42:46 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id k039gg78066141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 3 Jan 2006 10:42:43 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id k039ggBT001013 for ; Tue, 3 Jan 2006 10:42:42 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id k039ggEM001012 for current@freebsd.org; Tue, 3 Jan 2006 10:42:42 +0100 (CET) (envelope-from ticso) Date: Tue, 3 Jan 2006 10:42:42 +0100 From: Bernd Walter To: current@freebsd.org Message-ID: <20060103094240.GA807@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: Subject: NFS server problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 09:42:49 -0000 I often see clients getting NFS errors when the server mounts an new and unrelated filesystem. This is especially annoying as one of the NFS servers is used to read removeable media. I also get errors when a server just reboots - maybe these are related to boot mounts? Unfortunately my environment isn't very good to isolate the problem so my hope is that someone with more NFS knowledge and a test environment can reproduce the simptoms. My assumption is that it just happens for write access, but I can't tell for shure. Mounts are UDP over IPv4 with statd/lockd running. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 10:17:23 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A8116A41F for ; Tue, 3 Jan 2006 10:17:23 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id A585843D45 for ; Tue, 3 Jan 2006 10:17:22 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail07.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k03AHDXT004457 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Tue, 3 Jan 2006 21:17:14 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k03AHDHh046950; Tue, 3 Jan 2006 21:17:13 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k03AHDTL046949; Tue, 3 Jan 2006 21:17:13 +1100 (EST) (envelope-from pjeremy) Date: Tue, 3 Jan 2006 21:17:13 +1100 From: Peter Jeremy To: "M. Warner Losh" Message-ID: <20060103101713.GI42228@cirb503493.alcatel.com.au> References: <20060102.221046.75255380.imp@bsdimp.com> <20060103061752.GE42228@cirb503493.alcatel.com.au> <20060103.015516.21274860.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103.015516.21274860.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 10:17:23 -0000 On Tue, 2006-Jan-03 01:55:16 -0700, M. Warner Losh wrote: >In message: <20060103061752.GE42228@cirb503493.alcatel.com.au> > Peter Jeremy writes: >: Actually, I'd suggest that you can't build a system that keeps any >: sort of accurate time without a connection to the outside world or a >: quite substantial budget. If you assume a leap second every 5 years >: then the difference between UTC and TAI is about 6e-9 - being able > >Actually, that's wrong. If you assume a leap second every 18 months >you'd be better off, in the long run. That brings you into the high-end OCXO range I think - though I was thinking in terms of systems which needed to distinguish UTC and TAI without any external references. >: to tell the difference requires an atomic clock - which isn't common >: in embedded systems. > >Unless those embedded systems deal with time. Timing products are obviously a special case. I still stand by my "common" statement. >every time includes cases where the GPS reciever has been a powered >down spare for the past 9 months and therefore has no notion of the >leap seconds that have accumulated. This means it has to have an >extra long startup period while the GPS receive gets a new almanac. >This long wait is irritating to a customer, as you might imagine. In this case, the problem is that the connection to the outside world exists but does not provide the required information (UTC/GPS offset) in a timely manner. You could suggest that if the correct time is that critical to the customer, maybe they should be using hot-standby, not cold-standby spares :-). Does Galileo handle this any better? I now have a much better understanding of the background to your stance on leap seconds. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 10:59:56 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECD8216A41F for ; Tue, 3 Jan 2006 10:59:55 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65FF543D48 for ; Tue, 3 Jan 2006 10:59:55 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 53B7ABC50; Tue, 3 Jan 2006 10:59:53 +0000 (UTC) To: Peter Jeremy From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 03 Jan 2006 21:17:13 +1100." <20060103101713.GI42228@cirb503493.alcatel.com.au> Date: Tue, 03 Jan 2006 11:59:52 +0100 Message-ID: <83586.1136285992@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 10:59:56 -0000 In message <20060103101713.GI42228@cirb503493.alcatel.com.au>, Peter Jeremy writes: >Timing products are obviously a special case. I still stand by my >"common" statement. This is a very nice position to take, but how do you plan to educate all the people who need to know, how to tell the difference between a "common" and a "timing" requirement ? How do you even define the difference ? If you start to analyse things, you soon end up with the with same conclusion that Dave Mills and Dennis Ferguson did many years ago: If it is connected, it is a "timing system". The biggest problem about the leapsecond debate is that very few people know enough about what they are talking about. The astronomers know far too little about modern computing. They think that their instruments will be more expensive to modify than it will be to teach all other computers to handle leap seconds properly. The "time lords" are in the same category, they havn't realized that other kit than their clocks work in the sub-millisecond regime for long periods of time. The entire IT business, as such, knows far too little about time and virtually nothing about leapseconds as evidenced by the POSIX text and Windows handling of time. The press will print anything which makes a good headline, without trying to understand the underlying subject matter or its implications. There are two fundamental issues: 1. POSIX is lame. 2. Leapseconds are only announced 3-6 months in advance. Fixing POSIX will mean that applications can precisely calculate time intervals into the past, but still not further than 3 months into the future. Neither of which seem particularly important for the majority of computer users. But fixing POSIX does not solve the second half of the problem and may in fact only make the consequences of it worse, as programmers will then have the option of taking leap seconds into account, but may be running without up to date leap second tables. It's the unpredictability and short notice of the leapseconds that is the fundamental problem. The following proposals have been aired: A) Abandon leap seconds. This makes POSIX correct and computer timekeeping comes down to being in sync or not being in sync. The Sun will slowly (over centuries) drift across the sky. The easiest way to compensate for that is to skip timezones by not "falling back" from DST or similar. Such changes can be announced 100 years in advance and should therefore pose little trouble for computers. B) Predict leap seconds further in advance. This increases the |UT1-UTC| tolerance and the astronomers will have to cope. Provided that the notice becomes long enough, 10 years as a minimum, computing problems will mostly disappear, provided operating system suppliers pay attention to it. C) Make leapseconds smaller and more frequent Make the individual steps smaller (10 msec ?) and more frequent (every month ?) and therefore less dangerous at the expense of higher frequency. Again, provided we get to know far enough in advance (10 years or more) this is workable for computers. And finally some anti-FUD: "Abandonning leap seconds means the sun will rise at night and it will be dark during the day!" No, a simple change of timezones will prevent this. Changing timezones is about as much trouble as changing daylight savings time, something which the US congress has no qualms doing. "It is very important for people that the sun is in south at noon" Less than 1% of the earths population has that priviledge now. The majorty lives with timezones that put the sun anywhere from -15 to +15 degrees from south at noon, in some notable cases like China, up to +/- 45 degrees or more. "We don't know what will break if we drop leap-seconds" We know very well what can break: Only systems which relate the position of extra-terrestial objects to UTC time can break. These devices are called antennas and telescopes and they are operated by scientists and technicians who should be more than able to figure out how to deal with this. -- 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. From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 11:03:01 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5E0216A41F for ; Tue, 3 Jan 2006 11:03:01 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F88543D48 for ; Tue, 3 Jan 2006 11:03:01 +0000 (GMT) (envelope-from toxahost@gmail.com) Received: by zproxy.gmail.com with SMTP id i11so2320712nzh for ; Tue, 03 Jan 2006 03:03:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=LgJqHrYIoqvsYGjIhnL8bQRl8qs5B9+1juevSjJVE4Ff6OTRXISnCqSSECeVK2utjhmyuWVZAXYUpkSe51nGxq5kz9/d76uqPw43w+dHrS7e8fdmb1pw3lCmu3gsCKESzNfMtyMPza7mwsKtaywFRrHuZNTNQy1aaiZRnHny4KY= Received: by 10.65.191.10 with SMTP id t10mr400552qbp; Tue, 03 Jan 2006 03:03:00 -0800 (PST) Received: by 10.64.209.20 with HTTP; Tue, 3 Jan 2006 03:03:00 -0800 (PST) Message-ID: Date: Tue, 3 Jan 2006 14:03:00 +0300 From: Anton Karpov To: freebsd-current@freebsd.org In-Reply-To: <20060102.214956.40574756.imp@bsdimp.com> MIME-Version: 1.0 References: <43B83262.1090907@fastmail.fm> <20060101.212552.85411680.imp@bsdimp.com> <20060102.214956.40574756.imp@bsdimp.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 11:03:02 -0000 > > > I've just commited changes that fix it for me. Wow, my Proxim Orinoco Gold 8470-WD works again. And Kismet too. Thanks a lot! From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 11:47:22 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 920D116A41F for ; Tue, 3 Jan 2006 11:47:22 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAECC43D46 for ; Tue, 3 Jan 2006 11:47:21 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: from localhost (localhost [127.0.0.1]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id 80D6F44129; Tue, 3 Jan 2006 12:47:20 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 04565-08; Tue, 3 Jan 2006 12:47:19 +0100 (CET) Received: from m2a2.dyndns.org (p5091330E.dip0.t-ipconnect.de [80.145.51.14]) by mail.dt.e-technik.uni-dortmund.de (Postfix) with ESMTP id CEE8344128; Tue, 3 Jan 2006 12:47:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 25028200603; Tue, 3 Jan 2006 12:47:17 +0100 (CET) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28116-13; Tue, 3 Jan 2006 12:47:15 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id BF7FA20148E; Tue, 3 Jan 2006 12:47:14 +0100 (CET) From: Matthias Andree To: "Poul-Henning Kamp" In-Reply-To: <83586.1136285992@critter.freebsd.dk> (Poul-Henning Kamp's message of "Tue, 03 Jan 2006 11:59:52 +0100") References: <83586.1136285992@critter.freebsd.dk> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Tue, 03 Jan 2006 12:47:14 +0100 Message-ID: User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at dt.e-technik.uni-dortmund.de Cc: Peter Jeremy , current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 11:47:22 -0000 "Poul-Henning Kamp" writes: > "We don't know what will break if we drop leap-seconds" > > We know very well what can break: Only systems which relate > the position of extra-terrestial objects to UTC time can break. > > These devices are called antennas and telescopes and they are > operated by scientists and technicians who should be more than > able to figure out how to deal with this. The same argument can come back in your face, computer scientists and engineers should be able to figure out how to deal with time tracking earth rotation, you're tracking all sorts of things... And then you're back where you started, trying to argue with costs, the other side doesn't know, and so on. Who is assigning the weights to the opposing opinions? -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 11:50:41 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D8E2D16A41F for ; Tue, 3 Jan 2006 11:50:41 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7649243D4C for ; Tue, 3 Jan 2006 11:50:41 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id A7532BC50; Tue, 3 Jan 2006 11:50:39 +0000 (UTC) To: Matthias Andree From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 03 Jan 2006 12:47:14 +0100." Date: Tue, 03 Jan 2006 12:50:38 +0100 Message-ID: <84028.1136289038@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Peter Jeremy , current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 11:50:42 -0000 In message , Matthias Andree writes: >"Poul-Henning Kamp" writes: > >> "We don't know what will break if we drop leap-seconds" >> >> We know very well what can break: Only systems which relate >> the position of extra-terrestial objects to UTC time can break. >> >> These devices are called antennas and telescopes and they are >> operated by scientists and technicians who should be more than >> able to figure out how to deal with this. > >The same argument can come back in your face, computer scientists and >engineers should be able to figure out how to deal with time tracking >earth rotation, you're tracking all sorts of things... 99.9% of the computers are used by people who are not scientists and engineers. 99.999% of the computers do not track extra-terrestial objects. Wanna bet how the cost balances ? -- 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. From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 14:49:32 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 803E516A41F; Tue, 3 Jan 2006 14:49:32 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 91D5943D58; Tue, 3 Jan 2006 14:49:31 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 7897352CB1; Tue, 3 Jan 2006 15:49:28 +0100 (CET) Received: from localhost (dld227.neoplus.adsl.tpnet.pl [83.24.33.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 0AF1252BC5; Tue, 3 Jan 2006 15:49:19 +0100 (CET) Date: Tue, 3 Jan 2006 15:49:13 +0100 From: Pawel Jakub Dawidek To: obrien@freebsd.org, freebsd-current@freebsd.org Message-ID: <20060103144913.GE8302@garage.freebsd.pl> References: <20060102222723.GA1754@dragon.NUXI.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Dzs2zDY0zgkG72+7" Content-Disposition: inline In-Reply-To: <20060102222723.GA1754@dragon.NUXI.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 14:49:32 -0000 --Dzs2zDY0zgkG72+7 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jan 02, 2006 at 02:27:23PM -0800, David O'Brien wrote: +> Just in case anyone thought the bug had been fixed... +>=20 +> FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 +>=20 +> panic: ufs_dirbad: bad dir +> cpuid =3D 1 +> KDB: stack backtrace: +> kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e =3D k= db_backtrace+0x2e +> panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 =3D panic+0x1= 28 +> ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d =3D ufs_dirba= d+0x4d +> ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = =3D ufs_lookup+0x3ad +> VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0x= c068cd4e =3D VOP_CACHEDLOOKUP_APV+0x9e +> vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc057= 275a =3D vfs_cache_lookup+0xca +> VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 =3D = VOP_LOOKUP_APV+0xa6 +> lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e =3D lookup+0x44e +> namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf =3D namei+0x44f +> kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd =3D kern_stat+0x= 3d +> stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f =3D stat+0x2f +> syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 =3D syscall+0x323 +> Xint0x80_syscall() at 0xc066d33f =3D Xint0x80_syscall+0x1f Do you have a way to reproduce it? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Dzs2zDY0zgkG72+7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDuo7pForvXbEpPzQRAi/yAKCPV1HvDxnYlakefhaJ+k08EvzQ3QCfaJqU aSBCRjLE/Ixl2uN46gBz4S0= =j5cb -----END PGP SIGNATURE----- --Dzs2zDY0zgkG72+7-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 15:46:48 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 220D716A41F; Tue, 3 Jan 2006 15:46:48 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C05543D7C; Tue, 3 Jan 2006 15:46:37 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k03FkaG8073620; Tue, 3 Jan 2006 08:46:36 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BA9C5C.9010307@samsco.org> Date: Tue, 03 Jan 2006 08:46:36 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: obrien@freebsd.org References: <20060102222723.GA1754@dragon.NUXI.org> In-Reply-To: <20060102222723.GA1754@dragon.NUXI.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 15:46:48 -0000 David O'Brien wrote: > Just in case anyone thought the bug had been fixed... > > FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 > > panic: ufs_dirbad: bad dir > cpuid = 1 > KDB: stack backtrace: > kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e = kdb_backtrace+0x2e > panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 = panic+0x128 > ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d = ufs_dirbad+0x4d > ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = ufs_lookup+0x3ad > VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0xc068cd4e = VOP_CACHEDLOOKUP_APV+0x9e > vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc057275a = vfs_cache_lookup+0xca > VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 = VOP_LOOKUP_APV+0xa6 > lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e = lookup+0x44e > namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf = namei+0x44f > kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd = kern_stat+0x3d > stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f = stat+0x2f > syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 = syscall+0x323 > Xint0x80_syscall() at 0xc066d33f = Xint0x80_syscall+0x1f > Please include the console printf that is right about the panic message. It will say either something about a mangled entry or an isize too small. Since this problem is happening consistently for you, but there seem to be no other problem reports from others, I'd highly suspect that you have filesystem damage that isn't getting detected by fsck. I assume that you are running fsck in the foreground and not in the background, yes? The easiest solution here might be to figure out which directory is causing the problem, and just clri its inode and then clean up the mess. Scott From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 16:26:23 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3EC4316A41F for ; Tue, 3 Jan 2006 16:26:23 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from lira.ugcs.caltech.edu (lira.ugcs.caltech.edu [131.215.176.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id C781443D55 for ; Tue, 3 Jan 2006 16:26:22 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by lira.ugcs.caltech.edu (Postfix, from userid 3640) id 493606B002; Tue, 3 Jan 2006 08:26:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lira.ugcs.caltech.edu (Postfix) with ESMTP id 08FE25300A; Tue, 3 Jan 2006 08:26:21 -0800 (PST) Date: Tue, 3 Jan 2006 08:26:20 -0800 (PST) From: Jon Dama To: Poul-Henning Kamp In-Reply-To: <83586.1136285992@critter.freebsd.dk> Message-ID: References: <83586.1136285992@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Peter Jeremy , current@freebsd.org, "M. Warner Losh" Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 16:26:23 -0000 I think you had the answer more clearly earlier. Computers display event times in UTC, but intervals are based on SI seconds (and now finer granuality). I might be crazy, but I understand stopwatch seconds after the epoch (SI) to be the fundamental unit of POSIX time. Days, Hours, Months, etc simply does not enter into the consideration except in the context of "formating functions" such as gmtime(), localtime(), mktime(), etc. Here I agree that POSIX is lying when it suggests you can get UTC time out without leapsecond tables, but this does not seem to be a very fundamental problem. difftime operates on stopwatch seconds after the epoch. It is quite informative to realize that time_t has sub-second granularity whereas struct tm have seconds as their smallest unit of time. Typically on any instrument, at least the least significant digit is considered approximate. Such will be the case in regards to the POSIX definition of time for some years into the future. So chill. If you just avoid discussing the translation of stopwatch seconds into minutes/hours/days the problem goes away and we can all chalk up that conversion of seconds into minutes/hours/days that we all learned in grade school as another poorly explained simplification and proceed to unlearn it from our minds. From owner-freebsd-current@FreeBSD.ORG Sun Jan 1 13:23:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 893F316A41F; Sun, 1 Jan 2006 13:23:10 +0000 (GMT) (envelope-from bjoern.koenig@spray.se) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id E604A43D4C; Sun, 1 Jan 2006 13:23:09 +0000 (GMT) (envelope-from bjoern.koenig@spray.se) Received: from eurystheus.local (port-212-202-169-24.dynamic.qsc.de [212.202.169.24]) by efacilitas.de (Postfix) with ESMTP id D0AEC4B061; Sun, 1 Jan 2006 14:31:48 +0100 (CET) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id BF0C15285C; Sun, 1 Jan 2006 14:21:59 +0100 (CET) Message-ID: <43B7D7BC.9050706@spray.se> Date: Sun, 01 Jan 2006 14:23:08 +0100 From: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: Bill Paul References: <20051230205736.3260C16A420@hub.freebsd.org> In-Reply-To: <20051230205736.3260C16A420@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Tue, 03 Jan 2006 16:55:26 +0000 Cc: freebsd-current@freebsd.org, Andrea Brancatelli Subject: Re: ADM64 floppies X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Jan 2006 13:23:10 -0000 Hello, Installing FreeBSD 6.0/amd64 with i386 boot floppies worked for me in the most simple case that you just want a base installation. I specified an FTP site as installation source manually and installed from an "amd64" directory instead of "i386". Just reboot after installation and do configuration later. I never had problems with this method. Björn From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 20:25:08 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CAA716A422; Tue, 3 Jan 2006 20:25:08 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70E6B43D49; Tue, 3 Jan 2006 20:25:06 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5191192 for multiple; Tue, 03 Jan 2006 15:25:04 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k03KP0iK095359; Tue, 3 Jan 2006 15:25:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 3 Jan 2006 14:47:23 -0500 User-Agent: KMail/1.8.2 References: <20051229221459.A17102@cons.org> <0r1wzteiyc.fsf@hanbruch.tg.intern> <20051231093050.GB73324@nagual.pp.ru> In-Reply-To: <20051231093050.GB73324@nagual.pp.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601031447.26215.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1226/Tue Jan 3 11:51:16 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Thomas Gellekum , Martin Cracauer , Colin Percival Subject: Re: fetch extension - use local filename from content-dispositionheader (new diff) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 20:25:08 -0000 On Saturday 31 December 2005 04:30 am, Andrey Chernov wrote: > On Sat, Dec 31, 2005 at 10:04:11AM +0100, Thomas Gellekum wrote: > > Andrey Chernov writes: > > > There is easy way to make most security hackarounds unneeded in the way > > > like every browser does: confirm final file name interactively. I.e. > > > fetch can do something like this: > > > > > > Save as filename.exe (Y/N)? > > > > And for use in scripts you'd like to add a -y switch to say "yes, I > > mean it"? > > Personally I prefer to see this feature not for scripts at all, but this > is the next story and can be discussed afterwards. It is only intended for scripts. You can already use Mozilla and have it do this feature for non-scripted behavior. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 21:11:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 653AF16A41F for ; Tue, 3 Jan 2006 21:11:43 +0000 (GMT) (envelope-from listas@informatica.info) Received: from deneb.informatica.info (lincl214.informatica.info [86.109.161.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29BFD43D68 for ; Tue, 3 Jan 2006 21:11:40 +0000 (GMT) (envelope-from listas@informatica.info) Received: from [192.168.1.33] (115.Red-83-60-90.dynamicIP.rima-tde.net [83.60.90.115]) (authenticated bits=0) by deneb.informatica.info (8.13.1/8.13.1) with ESMTP id k03LBOQ7010512 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 3 Jan 2006 22:11:33 +0100 Message-ID: <43BAE883.1090705@informatica.info> Date: Tue, 03 Jan 2006 22:11:31 +0100 From: Carlos Amengual User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: es-es, en, ca MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20060103120026.EEEC916A41F@hub.freebsd.org> In-Reply-To: <20060103120026.EEEC916A41F@hub.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on deneb.informatica.info X-Virus-Status: Clean Subject: Re: freebsd-current Digest, Vol 127, Issue 4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 21:11:43 -0000 Poul-Henning Kamp wrote: > > The astronomers know far too little about modern computing. Something shared with the POSIX specifications writers. > The following proposals have been aired: > > A) Abandon leap seconds. See last paragraphs. > B) Predict leap seconds further in advance. > > This increases the |UT1-UTC| tolerance and the astronomers > will have to cope. > > Provided that the notice becomes long enough, 10 years as > a minimum, computing problems will mostly disappear, provided > operating system suppliers pay attention to it. Leap seconds cannot be predicted reliably. If you mean having an initial prediction and then issuing (supposedly less frequent) differential corrections, you still have the problem, but with more confusion added. > C) Make leapseconds smaller and more frequent Then you loose the concept of a second and make the idea of timekeeping impractical. If I understand correctly, you agree with that and choose the idea of dropping the leap seconds: > And finally some anti-FUD: > [...] > "We don't know what will break if we drop leap-seconds" > > We know very well what can break: Only systems which relate > the position of extra-terrestial objects to UTC time can break. > > These devices are called antennas and telescopes and they are > operated by scientists and technicians who should be more than > able to figure out how to deal with this. You are missing the sextants, and their users, which would be much more complicated to "fix" than those telescopes. If leap seconds are dropped, ships and planes are going to notice it sooner or later. You may think that all those users could be educated to use a new, modified procedure, but the fact that many people still talks about GMT, which was abandoned as a timescale years ago (together with the whole concept of "Mean Time"), should evidence that such a change is not that easy. Regards, Carlos Amengual From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 22:42:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99CC516A41F for ; Tue, 3 Jan 2006 22:42:27 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D7C143D4C for ; Tue, 3 Jan 2006 22:42:27 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EturK-0000lp-Bg; Tue, 03 Jan 2006 22:42:26 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EturJ-0009sk-9M; Tue, 03 Jan 2006 12:42:25 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17338.64976.685459.349707@roam.psg.com> Date: Tue, 3 Jan 2006 12:42:24 -1000 To: FreeBSD Current Subject: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 22:42:27 -0000 7-current system as of nov 27 cvsupped removed CFLAGS and COPTFLAGS from make.conf built and installed kernel and world fsck ran fine when it went to mount file systems, mount option is unknown mount: /dev/da0s1a: Invalid argument this fstab was last touched in nov 2004, over a year ago had to do /rescue/mount -u -w /dev/da0s1a / and so on for all filesystems. then had to comment out fstab so i could go multi. wtf????? randy From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 22:54:02 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 740E416A41F for ; Tue, 3 Jan 2006 22:54:02 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1EF2B43D62 for ; Tue, 3 Jan 2006 22:54:02 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k03Ms1lV003222; Tue, 3 Jan 2006 14:54:01 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k03Ms12u003221; Tue, 3 Jan 2006 14:54:01 -0800 (PST) (envelope-from sgk) Date: Tue, 3 Jan 2006 14:54:01 -0800 From: Steve Kargl To: Randy Bush Message-ID: <20060103225401.GA3009@troutmask.apl.washington.edu> References: <17338.64976.685459.349707@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17338.64976.685459.349707@roam.psg.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 22:54:02 -0000 On Tue, Jan 03, 2006 at 12:42:24PM -1000, Randy Bush wrote: > 7-current system as of nov 27 > cvsupped > removed CFLAGS and COPTFLAGS from make.conf > built and installed kernel and world > > fsck ran fine > when it went to mount file systems, > > mount option is unknown > mount: /dev/da0s1a: Invalid argument > > this fstab was last touched in nov 2004, over a year ago > > had to do > > /rescue/mount -u -w /dev/da0s1a / > > and so on for all filesystems. then had to comment out fstab > so i could go multi. > > wtf????? > http://lists.freebsd.org/pipermail/freebsd-current/2005-December/059330.html http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/mount/mount.c Backwards compatibility was broken in rev. 1.7 in mount.c -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 22:54:37 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C236216A41F for ; Tue, 3 Jan 2006 22:54:37 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 556C943D5C for ; Tue, 3 Jan 2006 22:54:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k03MsTr6075789; Tue, 3 Jan 2006 15:54:30 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BB00A8.8010201@samsco.org> Date: Tue, 03 Jan 2006 15:54:32 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Carlos Amengual References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> In-Reply-To: <43BAE883.1090705@informatica.info> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org Subject: Re: freebsd-current Digest, Vol 127, Issue 4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 22:54:37 -0000 Carlos Amengual wrote: > Poul-Henning Kamp wrote: > >> >> The astronomers know far too little about modern computing. > > > Something shared with the POSIX specifications writers. > > >> The following proposals have been aired: >> >> A) Abandon leap seconds. > > > See last paragraphs. > > >> B) Predict leap seconds further in advance. >> >> This increases the |UT1-UTC| tolerance and the astronomers >> will have to cope. >> >> Provided that the notice becomes long enough, 10 years as >> a minimum, computing problems will mostly disappear, provided >> operating system suppliers pay attention to it. > > > Leap seconds cannot be predicted reliably. If you mean having an initial > prediction and then issuing (supposedly less frequent) differential > corrections, you still have the problem, but with more confusion added. > > >> C) Make leapseconds smaller and more frequent > > > Then you loose the concept of a second and make the idea of timekeeping > impractical. If I understand correctly, you agree with that and choose > the idea of dropping the leap seconds: > > >> And finally some anti-FUD: >> [...] >> "We don't know what will break if we drop leap-seconds" >> >> We know very well what can break: Only systems which relate >> the position of extra-terrestial objects to UTC time can break. >> >> These devices are called antennas and telescopes and they are >> operated by scientists and technicians who should be more than >> able to figure out how to deal with this. > > > You are missing the sextants, and their users, which would be much more > complicated to "fix" than those telescopes. If leap seconds are dropped, > ships and planes are going to notice it sooner or later. > Pointing a telescope at an object 100 million light years away requires incredibly precise timing. Pointing a quadrant or sextant at an object 8 light minutes to 50 light years away requires considerably less precision. And, let's face it, real ships navigate via gyroscopes, GPS, and LORAN, all devices that value consistent timekeeping, not celestially accurate timekeeping. At least, that was my impression during my time at sea =-) Scott From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 22:57:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A21CE16A41F for ; Tue, 3 Jan 2006 22:57:39 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D9A943D55 for ; Tue, 3 Jan 2006 22:57:39 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k03MvcR4003278; Tue, 3 Jan 2006 14:57:38 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k03MvcXj003277; Tue, 3 Jan 2006 14:57:38 -0800 (PST) (envelope-from sgk) Date: Tue, 3 Jan 2006 14:57:38 -0800 From: Steve Kargl To: Randy Bush Message-ID: <20060103225738.GB3009@troutmask.apl.washington.edu> References: <17338.64976.685459.349707@roam.psg.com> <20060103225401.GA3009@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060103225401.GA3009@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 22:57:39 -0000 On Tue, Jan 03, 2006 at 02:54:01PM -0800, Steve Kargl wrote: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/mount/mount.c > Backwards compatibility was broken in rev. 1.7 in mount.c I meant rev 1.77 -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:10:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 988AA16A41F for ; Tue, 3 Jan 2006 23:10:10 +0000 (GMT) (envelope-from pbowen@fastmail.fm) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2992F43D46 for ; Tue, 3 Jan 2006 23:10:09 +0000 (GMT) (envelope-from pbowen@fastmail.fm) Received: from frontend1.internal (mysql-sessions.internal [10.202.2.149]) by frontend1.messagingengine.com (Postfix) with ESMTP id D20E4D2E9D3 for ; Tue, 3 Jan 2006 18:10:07 -0500 (EST) Received: from frontend2.messagingengine.com ([10.202.2.151]) by frontend1.internal (MEProxy); Tue, 03 Jan 2006 18:10:07 -0500 X-Sasl-enc: qdNv8uHdmB6YQF/R4EjN6xczEFg5xmKTJMmukbVtQdnV 1136329806 Received: from [192.168.221.65] (unknown [12.177.81.66]) by frontend2.messagingengine.com (Postfix) with ESMTP id D36E05714A4 for ; Tue, 3 Jan 2006 18:10:06 -0500 (EST) Message-ID: <43BB0455.80508@fastmail.fm> Date: Tue, 03 Jan 2006 17:10:13 -0600 From: Patrick Bowen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050920 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <43B83262.1090907@fastmail.fm> <20060101.212552.85411680.imp@bsdimp.com> <20060102.214956.40574756.imp@bsdimp.com> In-Reply-To: <20060102.214956.40574756.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:10:10 -0000 M. Warner Losh wrote: >In message: <20060101.212552.85411680.imp@bsdimp.com> > "M. Warner Losh" writes: >: In message: >: Daniel Eischen writes: >: : On Sun, 1 Jan 2006, Patrick Bowen wrote: >: : >: : > Hello and Happy New Year; >: : > >: : > I just bought a D-Link DWL-G630 Wireless G Adapter for my laptop (Dell >: : > Latitude C-600), and it worked fine until I cvsup'ed last nights sources >: : > (12/31/05) and did canonical rebuild. Now the machine panics whenever I >: : > plug the card in. >: : >: : Same here, though I got the kernel panic at boot when I had inserted during >: : the boot. The panic was in cardbus_read_tuple() also. I can post the >: : hand scribed trace to anyone interested if necessary. >: >: No need. I have the card here, and it fails too. All my other cards >: work, but the atheros card is the only one that stores the CIS in a >: bar that I have (I'm sure that others do as well, but they aren't in >: the 10 cards I grabbed to test with). This appears to be resource >: related in some way, since it appears that we're getting a resource of >: '0' back. I'm trying to debug it now. >: >: Sorry for the hassle. > >I've just commited changes that fix it for me. > >Warner > > > Yep. Works for me , also! Thanks for all your work, even over a holiday weekend!! BTW; what does "BAR" stand for? Patrick From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:23:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A98FD16A41F for ; Tue, 3 Jan 2006 23:23:33 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32E1D43D70 for ; Tue, 3 Jan 2006 23:23:22 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtvUt-0001lr-Lk; Tue, 03 Jan 2006 23:23:20 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtvUs-0009wc-Il; Tue, 03 Jan 2006 13:23:18 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17339.1894.74343.72704@roam.psg.com> Date: Tue, 3 Jan 2006 13:23:18 -1000 To: Steve Kargl References: <17338.64976.685459.349707@roam.psg.com> <20060103225401.GA3009@troutmask.apl.washington.edu> Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:23:33 -0000 >> 7-current system as of nov 27 >> cvsupped >> removed CFLAGS and COPTFLAGS from make.conf >> built and installed kernel and world >> fsck ran fine >> when it went to mount file systems, >> mount option is unknown >> mount: /dev/da0s1a: Invalid argument >> this fstab was last touched in nov 2004, over a year ago >> had to do >> /rescue/mount -u -w /dev/da0s1a / >> and so on for all filesystems. then had to comment out fstab >> so i could go multi. > http://lists.freebsd.org/pipermail/freebsd-current/2005-December/059330.html > http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/mount/mount.c > Backwards compatibility was broken in rev. 1.7 in mount.c no comprendo while the mount man page seems not to have rw as an option # mount -p /dev/da0s1a / ufs rw 1 1 devfs /dev devfs rw 0 0 /dev/da0s1e /root ufs rw 2 2 /dev/da0s1h /usr ufs rw 2 2 /dev/da0s1f /var ufs rw 2 2 /dev/da0s1g /var/spool ufs rw 2 2 procfs /proc procfs rw 0 0 which is pretty much what /etc/fstab had before i commented the entries out so i could go multi #/dev/da0s1a / ufs rw 1 1 #/dev/da0s1e /root ufs rw 2 2 #/dev/da0s1h /usr ufs rw 2 2 #/dev/da0s1f /var ufs rw 2 2 #/dev/da0s1g /var/spool ufs rw 2 2 randy From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:23:49 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 517EC16A420 for ; Tue, 3 Jan 2006 23:23:49 +0000 (GMT) (envelope-from psionic@csh.rit.edu) Received: from blacksheep.csh.rit.edu (blacksheep.csh.rit.edu [129.21.60.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3321343D91 for ; Tue, 3 Jan 2006 23:23:23 +0000 (GMT) (envelope-from psionic@csh.rit.edu) Received: from localhost (localhost [127.0.0.1]) by blacksheep.csh.rit.edu (Postfix) with ESMTP id 775A6254F for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from blacksheep.csh.rit.edu ([127.0.0.1]) by localhost (blacksheep.csh.rit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 486196-08 for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from fury.csh.rit.edu (fury.csh.rit.edu [IPv6:2001:470:1f00:135:a00:20ff:fe8d:5399]) by blacksheep.csh.rit.edu (Postfix) with ESMTP id 2F96726C9 for ; Tue, 3 Jan 2006 18:23:20 -0500 (EST) Received: from fury.csh.rit.edu (localhost [127.0.0.1]) by fury.csh.rit.edu (Postfix) with ESMTP id E097D1560 for ; Tue, 3 Jan 2006 18:23:19 -0500 (EST) From: Jordan Sissel To: freebsd-current@freebsd.org Date: Tue, 03 Jan 2006 18:23:19 -0500 Sender: psionic@csh.rit.edu Message-Id: <20060103232319.E097D1560@fury.csh.rit.edu> X-Virus-Scanned: amavisd-new at csh.rit.edu Subject: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:23:49 -0000 On my grande circuit of trying to make mouse support better for FreeBSD, I've finally come about to working on usb mice. I've done a bit of research about usb hid, and I need some feedback on where I should take usb mouse support. In case you didn't read my previous post about a new moused and psm driver: The reengineered psm(4) exists to provide moused with a userland interface for talking to the mouse. Thusly, all functionality (specific mouse support) is provided through userland drivers. Back to usb mice... I've been playing some with usbhidctl(1) and usbhidaction(1) aswell as perusing the ums(4) sourcecode. It looks like ums(4) just talks uhid (looking up hid usage pages, etc). Turns out you can do this from the userland aswell. The immediate question is should I follow my psm work by turning usb mouse support into a userland driver for moused? That is, ums(4) would go away and usb mouse support would be provided by moused alone. Alternatively, instead of tossing out ums, I could work on fixing it so known-broken mice work properly with it. USB HID seems to be a very set standard, though some manufs decide to provide nonstandard data in hid usage pages. Moral of this story is that I want to make known-broken mice work with FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice (including usb->ps2 adapted mice), and probably others. I'm willing to do either option for ums - turn it into a userland driver for moused or just fix what's broken with it as is. Either way, I need to know what mice don't work properly. Ideally going for a more unified mouse driver structure (userland moused drivers, for example) would be best in my opinion. How can you help? If you are having issues with mouse support in FreeBSD I need to know the following: - Mouse model and brand (as specific as possible would help) - Symptoms of strange behavior - Environment (moused+ums? plain ums in X? plain psm in X? moused with serial mice?) Thanks, -Jordan From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:34:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B26ED16A41F for ; Tue, 3 Jan 2006 23:34:44 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C8AA43D75 for ; Tue, 3 Jan 2006 23:34:36 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k03NY6i14518 for ; Tue, 3 Jan 2006 15:34:06 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k03NY6uB001750 for freebsd-current@freebsd.org; Tue, 3 Jan 2006 15:34:06 -0800 (PST) (envelope-from faber) Date: Tue, 3 Jan 2006 15:34:06 -0800 From: Ted Faber To: freebsd-current@freebsd.org Message-ID: <20060103233406.GA1564@hut.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Subject: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:34:44 -0000 --0eh6TmSyL6TZE2Uz Content-Type: multipart/mixed; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 package against the new source, my Xserver won't allocate many video modes because it can't open /dev/agpgart to allocate memory. The video card is an Intel I810 - 865G chipset. On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide appears (which seems to be hinted at in the comments to the most recent change to /sys/pci/agp_i810.c from the CVS tree). I've attached a verbose dmesg from the kernel recent -CURRENT kernel. Anyone else having a similar problem or know what I'm doing wrong? I'm happy to test patches or provide more info. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2006 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 7.0-CURRENT #0: Tue Jan 3 13:14:26 PST 2006 root@hut.isi.edu:/usr/obj/usr/src/sys/HUT Using 32 colors for the VM-PQ tuning (1024, 8) Preloaded elf kernel "/boot/kernel/kernel" at 0xc07d4000. Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc07d41bc. Preloaded elf module "/boot/kernel/sound.ko" at 0xc07d4268. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc07d4314. MP Configuration Table version 1.4 found at 0xc00f0000 Table 'FACP' at 0xfd2bf Table 'SSDT' at 0xfffd1cbc Table 'APIC' at 0xfd333 MADT: Found table at 0xfd333 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 1: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 2: disabled MADT: Found CPU APIC ID 1 ACPI ID 3: disabled MADT: Found CPU APIC ID 3 ACPI ID 4: disabled ACPI APIC Table: Calibrating clock(s) ... i8254 clock: 1193124 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2793017231 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x441d> Instruction TLB: 4-KB, 2-MB or 4-MB pages, fully associative, 128 entries Data TLB: 4-KB or 4-MB pages, fully associative, 64 entries 1st-level data cache: 16-KB, 8-way set associative, sectored cache, 64-byte line size Trace cache: 12K-uops, 8-way set associative 2nd-level cache: 1-MB, 8-way set associative, sectored cache, 64-byte line size L2 cache: 24640 kbytes, 0-way associative, 4 bytes/line real memory = 1072103424 (1022 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000828000 - 0x000000003ec3efff, 1044475904 bytes (254999 pages) avail memory = 1044148224 (995 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xbbf8 pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:e2f4 Rev = 1.0 Other BIOS signatures found: APIC: CPU 0 has ACPI ID 1 MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 1 ioapic0: Routing external 8259A's -> intpin 0 ioapic0: intpin 0 -> ExtINT (edge, high) ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) ioapic0: intpin 16 -> PCI IRQ 16 (level, low) ioapic0: intpin 17 -> PCI IRQ 17 (level, low) ioapic0: intpin 18 -> PCI IRQ 18 (level, low) ioapic0: intpin 19 -> PCI IRQ 19 (level, low) ioapic0: intpin 20 -> PCI IRQ 20 (level, low) ioapic0: intpin 21 -> PCI IRQ 21 (level, low) ioapic0: intpin 22 -> PCI IRQ 22 (level, low) ioapic0: intpin 23 -> PCI IRQ 23 (level, low) MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 ioapic0: intpin 2 trigger: edge ioapic0: intpin 2 polarity: high MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0: intpin 9 polarity: high ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x01000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010000 io: mem: Pentium Pro MTRR support enabled null: random: ioapic0: routing intpin 13 (ISA IRQ 13) to vector 48 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ioapic0: routing intpin 9 (ISA IRQ 9) to vector 49 acpi0: [MPSAFE] pci_open(1): mode 1 addr port (0x0cf8) is 0x80000050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=25708086) pcibios: BIOS version 2.10 Found $PIR table, 8 entries at 0xc00feae0 PCI-Only Interrupts: none Location Bus Device Pin Link IRQs embedded 0 31 A 0x62 3 4 5 6 7 9 10 11 14 15 embedded 0 31 B 0x61 3 4 5 6 7 9 10 11 14 15 embedded 0 29 A 0x60 3 4 5 6 7 9 10 11 14 15 embedded 0 29 B 0x63 3 4 5 6 7 9 10 11 14 15 embedded 0 29 C 0x62 3 4 5 6 7 9 10 11 14 15 embedded 0 29 D 0x6b 3 4 5 6 7 9 10 11 14 15 embedded 0 2 A 0x60 3 4 5 6 7 9 10 11 14 15 embedded 1 8 A 0x68 3 4 5 6 7 9 10 11 14 15 slot 1 1 0 A 0x69 3 4 5 6 7 9 10 11 14 15 slot 1 1 0 B 0x6a 3 4 5 6 7 9 10 11 14 15 slot 1 1 0 C 0x6b 3 4 5 6 7 9 10 11 14 15 slot 1 1 0 D 0x68 3 4 5 6 7 9 10 11 14 15 slot 2 1 1 A 0x6a 3 4 5 6 7 9 10 11 14 15 slot 2 1 1 B 0x69 3 4 5 6 7 9 10 11 14 15 slot 2 1 1 C 0x68 3 4 5 6 7 9 10 11 14 15 slot 2 1 1 D 0x6b 3 4 5 6 7 9 10 11 14 15 slot 3 1 2 A 0x61 3 4 5 6 7 9 10 11 14 15 slot 3 1 2 B 0x62 3 4 5 6 7 9 10 11 14 15 slot 3 1 2 C 0x63 3 4 5 6 7 9 10 11 14 15 slot 3 1 2 D 0x60 3 4 5 6 7 9 10 11 14 15 slot 4 1 3 A 0x63 3 4 5 6 7 9 10 11 14 15 slot 4 1 3 B 0x62 3 4 5 6 7 9 10 11 14 15 slot 4 1 3 C 0x69 3 4 5 6 7 9 10 11 14 15 slot 4 1 3 D 0x6a 3 4 5 6 7 9 10 11 14 15 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: bus 0 dev 31 func 0 acpi0: Power Button (fixed) pci_link0: Links after initial probe: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 12 15 pci_link0: Links after initial validation: Index IRQ Rtd Ref IRQs 0 11 N 0 3 4 5 6 7 9 10 11 12 15 pci_link0: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link1: Links after initial probe: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 6 7 9 10 11 12 15 pci_link1: Links after initial validation: Index IRQ Rtd Ref IRQs 0 3 N 0 3 4 5 6 7 9 10 11 12 15 pci_link1: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link2: Links after initial probe: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 6 7 9 10 11 12 15 pci_link2: Links after initial validation: Index IRQ Rtd Ref IRQs 0 5 N 0 3 4 5 6 7 9 10 11 12 15 pci_link2: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link3: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 15 pci_link3: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 15 pci_link3: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link4: Links after initial probe: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 15 pci_link4: Links after initial validation: Index IRQ Rtd Ref IRQs 0 10 N 0 3 4 5 6 7 9 10 11 12 15 pci_link4: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link5: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link5: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link5: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link6: Links after initial probe: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link6: Links after initial validation: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link6: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 pci_link7: Links after initial probe: Index IRQ Rtd Ref IRQs 0 9 N 0 3 4 5 6 7 9 10 11 12 15 pci_link7: Links after initial validation: Index IRQ Rtd Ref IRQs 0 9 N 0 3 4 5 6 7 9 10 11 12 15 pci_link7: Links after disable: Index IRQ Rtd Ref IRQs 0 255 N 0 3 4 5 6 7 9 10 11 12 15 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: physical bus=0 found-> vendor=0x8086, dev=0x2570, revid=0x02 bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x2090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) map[10]: type 3, range 32, base f0000000, size 27, enabled found-> vendor=0x8086, dev=0x2572, revid=0x02 bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0003, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D3 current D0 map[10]: type 3, range 32, base e8000000, size 27, enabled map[14]: type 1, range 32, base feb80000, size 19, enabled map[18]: type 4, range 32, base 0000ed98, size 3, enabled pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x24d2, revid=0x02 bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000ff80, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x24d4, revid=0x02 bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=10 map[20]: type 4, range 32, base 0000ff60, size 5, enabled pcib0: matched entry for 0.29.INTB pcib0: slot 29 INTB hardwired to IRQ 19 found-> vendor=0x8086, dev=0x24de, revid=0x02 bus=0, slot=29, func=3 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type 4, range 32, base 0000ff20, size 5, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 16 found-> vendor=0x8086, dev=0x24dd, revid=0x02 bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=9 powerspec 2 supports D0 D3 current D0 map[10]: type 1, range 32, base ffa80800, size 10, enabled pcib0: matched entry for 0.29.INTD pcib0: slot 29 INTD hardwired to IRQ 23 found-> vendor=0x8086, dev=0x244e, revid=0xc2 bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x02 (500 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24d0, revid=0x02 bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24db, revid=0x02 bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0288, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=5 map[20]: type 4, range 32, base 0000ffa0, size 4, enabled map[24]: type 1, range 32, base feb7fc00, size 10, enabled pcib0: matched entry for 0.31.INTA pcib0: slot 31 INTA hardwired to IRQ 18 found-> vendor=0x8086, dev=0x24d3, revid=0x02 bus=0, slot=31, func=3 class=0c-05-00, hdrtype=0x00, mfdev=0 cmdreg=0x0001, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 map[20]: type 4, range 32, base 0000eda0, size 5, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 found-> vendor=0x8086, dev=0x24d5, revid=0x02 bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=3 powerspec 2 supports D0 D3 current D0 map[10]: type 4, range 32, base 0000ee00, size 8, enabled map[14]: type 4, range 32, base 0000edc0, size 6, enabled map[18]: type 1, range 32, base feb7fa00, size 9, enabled map[1c]: type 1, range 32, base feb7f900, size 8, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 17 vgapci0: port 0xed98-0xed9f mem 0xe8000000-0xefffffff,0xfeb80000-0xfebfffff irq 16 at device 2.0 on pci0 uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 uhci0: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff80 ioapic0: routing intpin 16 (PCI IRQ 16) to vector 50 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 uhci1: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff60 ioapic0: routing intpin 19 (PCI IRQ 19) to vector 51 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 uhci2: Reserved 0x20 bytes for rid 0x20 type 4 at 0xff20 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xffa80800 ioapic0: routing intpin 23 (PCI IRQ 23) to vector 52 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: wrong number of companions (4 != 3) usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered uhub4: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered pcib1: at device 30.0 on pci0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0xd000-0xdfff pcib1: memory decode 0xfea00000-0xfeafffff pcib1: prefetched decode 0xfff00000-0xfffff pcib1: Subtractively decoded bridge. pci1: on pcib1 pci1: physical bus=1 found-> vendor=0x8086, dev=0x1050, revid=0x02 bus=1, slot=8, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0117, statreg=0x0290, cachelnsz=16 (dwords) lattimer=0x40 (1920 ns), mingnt=0x08 (2000 ns), maxlat=0x38 (14000 ns) intpin=a, irq=10 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type 1, range 32, base feaff000, size 12, enabled pcib1: (null) requested memory range 0xfeaff000-0xfeafffff: good map[14]: type 4, range 32, base 0000df40, size 6, enabled pcib1: (null) requested I/O range 0xdf40-0xdf7f: in range pcib1: matched entry for 1.8.INTA pcib1: slot 8 INTA hardwired to IRQ 20 fxp0: port 0xdf40-0xdf7f mem 0xfeaff000-0xfeafffff irq 20 at device 8.0 on pci1 fxp0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xfeaff000 fxp0: using memory space register mapping fxp0: PCI IDs: 8086 1050 1028 019d 0002 fxp0: Dynamic Standby mode is enabled miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: bpf attached fxp0: Ethernet address: 00:13:20:69:97:0e ioapic0: routing intpin 20 (PCI IRQ 20) to vector 53 fxp0: [MPSAFE] isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7ffff irq 18 at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata0: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=50 stat1=00 devices=0x1 ioapic0: routing intpin 14 (ISA IRQ 14) to vector 54 ata0: [MPSAFE] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x04 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x4 ioapic0: routing intpin 15 (ISA IRQ 15) to vector 55 ata1: [MPSAFE] pci0: at device 31.3 (no driver attached) pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 pcm0: Reserved 0x200 bytes for rid 0x18 type 3 at 0xfeb7fa00 pcm0: Reserved 0x100 bytes for rid 0x1c type 3 at 0xfeb7f900 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 56 pcm0: [MPSAFE] pcm0: primary codec not ready! pcm0: pcm0: Codec features headphone, 20 bit DAC, 5 bit master volume, no 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, double rate PCM, center DAC, surround DAC, LFE DAC, AMAP pcm0: ac97 codec dac ready count: 0 pcm0: sndbuf_setmap 3e62d000, 4000; 0xe4eed000 -> 3e62d000 pcm0: sndbuf_setmap 3e629000, 4000; 0xe4ef1000 -> 3e629000 sio0: irq maps: 0xcc29 0xcc39 0xcc29 0xcc29 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A ioapic0: routing intpin 4 (ISA IRQ 4) to vector 57 ppc0: using extended I/O port range ppc0: ECP SPP ECP+EPP SPP ppc0: port 0x378-0x37f,0x778-0x77f irq 7 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 ioapic0: routing intpin 7 (ISA IRQ 7) to vector 58 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it ppc: ppc0 already exists; skipping it sc: sc0 already exists; skipping it sio: sio0 already exists; skipping it vga: vga0 already exists; skipping it pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xca800-0xcbfff pnpid ORM0000 on isa0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0xffffffff (1) atkbd: failed to reset the keyboard. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 adv0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 kbd0: atkbd0, AT 84 (1), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to vector 59 atkbd0: [GIANT-LOCKED] psm0: current command byte:0045 psm0: failed to reset the aux device. bt0: not probed (disabled) cs0: not probed (disabled) ed0: not probed (disabled) fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 fe0: not probed (disabled) ie0: not probed (disabled) lnc0: not probed (disabled) sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: irq maps: 0xcca9 0xcca9 0xcca9 0xcca9 sio1: probe failed test(s): 0 1 2 4 6 7 9 sio1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 sio2: not probed (disabled) sio3: not probed (disabled) sn0: not probed (disabled) vt0: not probed (disabled) isa_probe_children: probing PnP devices ums0: Logitech USB-PS/2 Trackball, rev 1.00/2.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: DELL DELL USB Keyboard, rev 1.10/1.04, addr 3, iclass 3/1 kbd: new array size 4 kbd1 at ukbd0 kbd1: ukbd0, generic (0), config:0x0, flags:0x1d0000 Device configuration finished. lapic: Divisor 2, Frequency 66500395 hz Timecounter "TSC" frequency 2793017231 Hz quality 800 Timecounters tick every 1.000 msec lo0: bpf attached ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=80 wire ad0: setting PIO4 on ICH5 chip ad0: setting UDMA100 on ICH5 chip ad0: 76293MB at ata0-master UDMA100 ad0: 156250000 sectors [155009C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad0 ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting PIO4 on ICH5 chip acd0: setting UDMA33 on ICH5 chip acd0: DVDR drive at ata1 as master acd0: read 8268KB/s (8268KB/s) write 8268KB/s (8268KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, DVDR, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc pcm0: measured ac97 link rate at 48016 Hz, will use 48000 Hz ioapic0: routing intpin 1 (ISA IRQ 1) to cluster 0 ioapic0: routing intpin 4 (ISA IRQ 4) to cluster 0 ioapic0: routing intpin 7 (ISA IRQ 7) to cluster 0 ioapic0: routing intpin 9 (ISA IRQ 9) to cluster 0 ioapic0: routing intpin 13 (ISA IRQ 13) to cluster 0 ioapic0: routing intpin 14 (ISA IRQ 14) to cluster 0 ioapic0: routing intpin 15 (ISA IRQ 15) to cluster 0 ioapic0: routing intpin 16 (PCI IRQ 16) to cluster 0 ioapic0: routing intpin 17 (PCI IRQ 17) to cluster 0 ioapic0: routing intpin 19 (PCI IRQ 19) to cluster 0 ioapic0: routing intpin 20 (PCI IRQ 20) to cluster 0 ioapic0: routing intpin 23 (PCI IRQ 23) to cluster 0 Trying to mount root from ufs:/dev/ad0s1a start_init: trying /sbin/init procfs registered Linux ELF exec handler installed linprocfs registered ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled nfslock: pseudo-device --fdj2RfSjLxBAspz7-- --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDuwnuaUz3f+Zf+XsRArFAAKCL5YWD3zHX5noRt4Q1qDttOJCdgwCeMZt0 lwb/h5tBPJO0rEeps9HdI/A= =qBOy -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz-- From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:35:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6201F16A41F for ; Tue, 3 Jan 2006 23:35:00 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 459A643D72 for ; Tue, 3 Jan 2006 23:34:59 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k03NYw6x003884; Tue, 3 Jan 2006 15:34:58 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k03NYwx6003883; Tue, 3 Jan 2006 15:34:58 -0800 (PST) (envelope-from sgk) Date: Tue, 3 Jan 2006 15:34:58 -0800 From: Steve Kargl To: Randy Bush Message-ID: <20060103233458.GA3763@troutmask.apl.washington.edu> References: <17338.64976.685459.349707@roam.psg.com> <20060103225401.GA3009@troutmask.apl.washington.edu> <17339.1894.74343.72704@roam.psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17339.1894.74343.72704@roam.psg.com> User-Agent: Mutt/1.4.2.1i Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:35:00 -0000 On Tue, Jan 03, 2006 at 01:23:18PM -1000, Randy Bush wrote: > >> 7-current system as of nov 27 > >> cvsupped > >> removed CFLAGS and COPTFLAGS from make.conf > >> built and installed kernel and world > >> fsck ran fine > >> when it went to mount file systems, > >> mount option is unknown > >> mount: /dev/da0s1a: Invalid argument > >> this fstab was last touched in nov 2004, over a year ago > >> had to do > >> /rescue/mount -u -w /dev/da0s1a / > >> and so on for all filesystems. then had to comment out fstab > >> so i could go multi. > > http://lists.freebsd.org/pipermail/freebsd-current/2005-December/059330.html > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sbin/mount/mount.c > > Backwards compatibility was broken in rev. 1.7 in mount.c > > no comprendo > The first URL notes the same problem with "mount option is unknown". The second URL points to the CVS repository for sbin/mount/mount.c. It should have read "rev. 1.77". In particular, Revision 1.77 / (download) - annotate - [select for diffs], Sat Dec 3 01:57:58 2005 UTC (4 weeks, 3 days ago) by rodrigc Branch: MAIN Changes since 1.76: +1 -1 lines Diff to previous 1.76 (colored) Simplify parsing of mount options by passing "rw" option down to kernel, since vfs_donmount() can now parse it. "Simplify" is a misspelling of "Break possibility of using older kernels with newer sbin/mount command". This, of course, makes panic recovery more difficult. I don't recall what the outcome of using a newer kernel with an old sbin/mount is. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:49:22 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 489A416A443 for ; Tue, 3 Jan 2006 23:49:22 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7312643DE6 for ; Tue, 3 Jan 2006 23:47:32 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k03Nkqh7005233; Tue, 3 Jan 2006 15:46:54 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k03NkcVm005228; Tue, 3 Jan 2006 15:46:38 -0800 (PST) (envelope-from jmg) Date: Tue, 3 Jan 2006 15:46:38 -0800 From: John-Mark Gurney To: Carlos Amengual Message-ID: <20060103234638.GA69162@funkthat.com> Mail-Followup-To: Carlos Amengual , freebsd-current@freebsd.org References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43BAE883.1090705@informatica.info> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-current@freebsd.org Subject: Re: freebsd-current Digest, Vol 127, Issue 4 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:49:24 -0000 Carlos Amengual wrote this message on Tue, Jan 03, 2006 at 22:11 +0100: > You are missing the sextants, and their users, which would be much more > complicated to "fix" than those telescopes. If leap seconds are dropped, > ships and planes are going to notice it sooner or later. Having talked with a sextant user... leap seconds don't matter to sextant users... They have a book of times and possitions, and the book is only good for a year or two... so needs to be reprinted, and on reprints, they can take care of the leap second issue... A second wrt sextants on the surface of the earth is about a quarter of a mile, and the rest of the reading is less precise than that, so even if you are a second off, you won't be that much further off course.. so, the only fix for a sextant is a new table of numbers... don't forget the tables HAVE to be updated for precisely the reason leap seconds are inserted... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:49:29 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B78716A44B; Tue, 3 Jan 2006 23:49:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 587EA43D49; Tue, 3 Jan 2006 23:49:27 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id k03NnPfI081929; Tue, 3 Jan 2006 18:49:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k03NnPBe028720; Tue, 3 Jan 2006 18:49:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id EEC407302F; Tue, 3 Jan 2006 18:49:24 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060103234924.EEC407302F@freebsd-current.sentex.ca> Date: Tue, 3 Jan 2006 18:49:24 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:49:29 -0000 TB --- 2006-01-03 22:24:32 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-03 22:24:32 - starting HEAD tinderbox run for alpha/alpha TB --- 2006-01-03 22:24:32 - cleaning the object tree TB --- 2006-01-03 22:24:58 - checking out the source tree TB --- 2006-01-03 22:24:58 - cd /tinderbox/HEAD/alpha/alpha TB --- 2006-01-03 22:24:58 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-03 22:30:53 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-03 22:30:53 - cd /src TB --- 2006-01-03 22:30:53 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2006-01-03 23:36:02 - generating LINT kernel config TB --- 2006-01-03 23:36:02 - cd /src/sys/alpha/conf TB --- 2006-01-03 23:36:02 - /usr/bin/make -B LINT TB --- 2006-01-03 23:36:02 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-03 23:36:02 - cd /src TB --- 2006-01-03 23:36:02 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jan 3 23:36:02 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -c __reml.S MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror vers.c linking kernel vfs_syscalls.o(.text+0x6610): In function `normalize_timeval': : undefined reference to `memmove' vfs_syscalls.o(.text+0x6614): In function `normalize_timeval': : undefined reference to `memmove' *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-03 23:49:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-03 23:49:24 - ERROR: failed to build lint kernel TB --- 2006-01-03 23:49:24 - tinderbox aborted TB --- 0.98 user 5.02 system 5092.52 real From owner-freebsd-current@FreeBSD.ORG Tue Jan 3 23:53:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D78C816A47C for ; Tue, 3 Jan 2006 23:53:37 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C865643E3E for ; Tue, 3 Jan 2006 23:52:13 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k03NljPd084033; Wed, 4 Jan 2006 00:47:45 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k03NpYw3003125; Wed, 4 Jan 2006 00:51:34 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (Andro-Beta.Leidinger.net [192.168.1.42]) by webmail.leidinger.net (Horde MIME library) with HTTP; Wed, 04 Jan 2006 00:51:34 +0100 Message-ID: <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> X-Priority: 3 (Normal) Date: Wed, 04 Jan 2006 00:51:34 +0100 From: Alexander Leidinger To: Benjamin Close References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> In-Reply-To: <43B9C7F1.5030303@cs.unisa.edu.au> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0.3) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 23:53:39 -0000 Benjamin Close wrote: > David Gilbert wrote: > >> I've got a laptop with the PC-CARD wi0 in it. I've currently got >> "ifconfig_wi0="DHCP"" in the rc.conf file. dhclient runs and >> everything is fine... until the association drops for a little bit. >> Then it looses the IP address and dhclient never relizes that it's >> associated again. Very annoying. >> >> I thought the whole point was that dhclient was suppose to notice >> these events? It does, but the driver doesn't send the corret events and also exhibits other misbehavior. > I have a slightly different but some what related issue. I can't get > an initial IP. > I've been trying to trace this down for a while. I believe it's a bug > in the wi code. The problem is, that the wi driver isn't ported to the current WLAN infrastructure. There's no documentation available for the WLAN infrastructure, so you have to read the source (the ath driver is the de-facto reference driver for the WLAN stuff), search the net and if nothing helps, ask sam@FreeBSD.org some well thought questions. If you have the time and energy to have a look at porting the wi driver to (at least parts of) the current WLAN framework, all wi users would appreciate some patches... Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 There is nothing wrong with abstinence, in moderation. From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:03:24 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3CF816A41F for ; Wed, 4 Jan 2006 00:03:24 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 531CE43D58 for ; Wed, 4 Jan 2006 00:03:24 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id 84374117C2; Tue, 3 Jan 2006 19:03:23 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id B94511A08A9; Tue, 3 Jan 2006 19:03:17 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17339.4293.673806.446317@canoe.dclg.ca> Date: Tue, 3 Jan 2006 19:03:17 -0500 To: Alexander Leidinger In-Reply-To: <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> X-Mailer: VM 7.17 under 21.4 (patch 18) "Social Property" XEmacs Lucid Cc: freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:03:24 -0000 >>>>> "Alexander" == Alexander Leidinger writes: [various problems with wi, deleted] Alexander> The problem is, that the wi driver isn't ported to the Alexander> current WLAN infrastructure. There's no documentation Alexander> available for the WLAN infrastructure, so you have to read Alexander> the source (the ath driver is the de-facto reference driver Alexander> for the WLAN stuff), search the net and if nothing helps, Alexander> ask sam@FreeBSD.org some well thought questions. I also thought that someone might have comments about a wi0 as an access point. This used to work, but all clients (even windoze) seem to loose association every 20 to 40 minutes (although the timing is random it seems). Alexander> If you have the time and energy to have a look at porting Alexander> the wi driver to (at least parts of) the current WLAN Alexander> framework, all wi users would appreciate some patches... Not that I'm afraid of development, but I'm unfamilliar with the difference between the revisions of acceptable wifi behaviour. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:24:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D3DE16A41F for ; Wed, 4 Jan 2006 00:24:30 +0000 (GMT) (envelope-from listas@informatica.info) Received: from deneb.informatica.info (lincl214.informatica.info [86.109.161.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 986CD43D48 for ; Wed, 4 Jan 2006 00:24:28 +0000 (GMT) (envelope-from listas@informatica.info) Received: from [192.168.1.33] (115.Red-83-60-90.dynamicIP.rima-tde.net [83.60.90.115]) (authenticated bits=0) by deneb.informatica.info (8.13.1/8.13.1) with ESMTP id k040OPjf011065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 01:24:26 +0100 Message-ID: <43BB15BB.2070705@informatica.info> Date: Wed, 04 Jan 2006 01:24:27 +0100 From: Carlos Amengual User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: es-es, en, ca MIME-Version: 1.0 To: John-Mark Gurney References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> <20060103234638.GA69162@funkthat.com> In-Reply-To: <20060103234638.GA69162@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on deneb.informatica.info X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:24:30 -0000 John-Mark Gurney wrote: > > Having talked with a sextant user... leap seconds don't matter to > sextant users... They have a book of times and possitions, and the > book is only good for a year or two... so needs to be reprinted, and > on reprints, they can take care of the leap second issue... Those tables are valid for a year (you can use computer programs too). If you use software, you have to fix the software, and if you use tables then a new set of tables has to be produced, where the time argument is not Universal Time (as until now), but Dynamical Time (TDT), or maybe something in the middle: "Dynamical Time plus something". > so, the only fix for a sextant is a new table of numbers... don't > forget the tables HAVE to be updated for precisely the reason leap > seconds are inserted... It is not only an update, it is a change in the tables themselves. And sidereal time would no longer be sidereal time. The current nautical tables use UT and not TDT as time argument precisely to avoid confusing people with timescales. Astronomical tables already use TDT (except for sidereal time), which is the kind of timescale that you want (TDT is based on TAI). Regards, Carlos Amengual From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:37:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E4F516A41F for ; Wed, 4 Jan 2006 00:37:00 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 320D843D4C for ; Wed, 4 Jan 2006 00:36:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k040afA0006492; Tue, 3 Jan 2006 16:36:42 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k040acwd006490; Tue, 3 Jan 2006 16:36:38 -0800 (PST) (envelope-from jmg) Date: Tue, 3 Jan 2006 16:36:38 -0800 From: John-Mark Gurney To: Carlos Amengual Message-ID: <20060104003637.GB69162@funkthat.com> Mail-Followup-To: Carlos Amengual , freebsd-current@freebsd.org References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> <20060103234638.GA69162@funkthat.com> <43BB15BB.2070705@informatica.info> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43BB15BB.2070705@informatica.info> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:37:00 -0000 Carlos Amengual wrote this message on Wed, Jan 04, 2006 at 01:24 +0100: > John-Mark Gurney wrote: > >so, the only fix for a sextant is a new table of numbers... don't > >forget the tables HAVE to be updated for precisely the reason leap > >seconds are inserted... > > It is not only an update, it is a change in the tables themselves. And > sidereal time would no longer be sidereal time. I mean how they are currently updated each year, not updated to use a new time scale.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:55:14 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8E20216A41F for ; Wed, 4 Jan 2006 00:55:14 +0000 (GMT) (envelope-from jonathan@fosburgh.org) Received: from pop-altamira.atl.sa.earthlink.net (pop-altamira.atl.sa.earthlink.net [207.69.195.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11F5043D60 for ; Wed, 4 Jan 2006 00:55:13 +0000 (GMT) (envelope-from jonathan@fosburgh.org) Received: from user-0cetsmu.cable.mindspring.com ([24.238.242.222] helo=gw.fosburgh.org) by pop-altamira.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1Etwvo-0005Zm-00; Tue, 03 Jan 2006 19:55:12 -0500 Received: by gw.fosburgh.org (Postfix, from userid 1001) id 8F12BB585; Tue, 3 Jan 2006 18:55:18 -0600 (CST) From: Jonathan Fosburgh To: freebsd-current@freebsd.org Date: Tue, 3 Jan 2006 18:55:16 -0600 User-Agent: KMail/1.9.1 References: <20060103232319.E097D1560@fury.csh.rit.edu> In-Reply-To: <20060103232319.E097D1560@fury.csh.rit.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601031855.17687.jonathan@fosburgh.org> Cc: Jordan Sissel Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:55:14 -0000 On Tuesday 03 January 2006 17:23, Jordan Sissel wrote: > On my grande circuit of trying to make mouse support better for FreeBSD, > I've finally come about to working on usb mice. I've done a bit of > research about usb hid, and I need some feedback on where I should take > usb mouse support. > Oh, good! :) > Moral of this story is that I want to make known-broken mice work with > FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice > (including usb->ps2 adapted mice), and probably others. > > > How can you help? If you are having issues with mouse support in > FreeBSD I need to know the following: > - Mouse model and brand (as specific as possible would help) > - Symptoms of strange behavior > - Environment (moused+ums? plain ums in X? plain psm in X? moused > with serial mice?) Check usb/77604 for some mice known to have problems and for a fix for them. -- Jonathan Fosburgh From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 00:57:53 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D3B416A41F for ; Wed, 4 Jan 2006 00:57:53 +0000 (GMT) (envelope-from listas@informatica.info) Received: from deneb.informatica.info (lincl214.informatica.info [86.109.161.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FCC243D45 for ; Wed, 4 Jan 2006 00:57:51 +0000 (GMT) (envelope-from listas@informatica.info) Received: from [192.168.1.33] (115.Red-83-60-90.dynamicIP.rima-tde.net [83.60.90.115]) (authenticated bits=0) by deneb.informatica.info (8.13.1/8.13.1) with ESMTP id k040vmwB011143 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 01:57:50 +0100 Message-ID: <43BB1D8E.1010204@informatica.info> Date: Wed, 04 Jan 2006 01:57:50 +0100 From: Carlos Amengual User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: es-es, en, ca MIME-Version: 1.0 To: John-Mark Gurney References: <20060103120026.EEEC916A41F@hub.freebsd.org> <43BAE883.1090705@informatica.info> <20060103234638.GA69162@funkthat.com> <43BB15BB.2070705@informatica.info> <20060104003637.GB69162@funkthat.com> In-Reply-To: <20060104003637.GB69162@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on deneb.informatica.info X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 00:57:53 -0000 John-Mark Gurney wrote: > Carlos Amengual wrote this message on Wed, Jan 04, 2006 at 01:24 +0100: > >>John-Mark Gurney wrote: >> >>>so, the only fix for a sextant is a new table of numbers... don't >>>forget the tables HAVE to be updated for precisely the reason leap >>>seconds are inserted... >> >>It is not only an update, it is a change in the tables themselves. And >>sidereal time would no longer be sidereal time. > > > I mean how they are currently updated each year, not updated to use a > new time scale.. > Dropping leap seconds would lead to the use of a timescale different to UT in tables. Of course, a point could be reached where leap seconds are frequent enough to become a pain for computers. In that case, computers could use TDT as time scale, but we need to have UT one way or the other. Astronomers regularly use TDT (formerly ET) as a work timescale, and UT only for Earth-orientation matters (Sidereal Time, which in fact defines UT). Computers could use TDT (not TAI, which AFAIK is not in "real" practical use elsewhere), but simply "freezing" UTC with the drop of leap seconds just adds confusion (another TAI-based timescale in addition to TAI itself and TDT). A "frozen" UT in current use is already invented: TDT. Regards, Carlos Amengual From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 01:06:41 2006 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B2DE16A41F; Wed, 4 Jan 2006 01:06:41 +0000 (GMT) (envelope-from dds@aueb.gr) Received: from mx-out-02.forthnet.gr (mx-out.forthnet.gr [193.92.150.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DCC143D49; Wed, 4 Jan 2006 01:06:38 +0000 (GMT) (envelope-from dds@aueb.gr) Received: from mx-av-03.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-02.forthnet.gr (8.13.5/8.13.5) with ESMTP id k0416bLO014439; Wed, 4 Jan 2006 03:06:37 +0200 Received: from mx-in-04.forthnet.gr (mx-in-04.forthnet.gr [193.92.150.163]) by mx-av-03.forthnet.gr (8.13.5/8.13.5) with ESMTP id k0416bIr023503; Wed, 4 Jan 2006 03:06:37 +0200 Received: from [192.168.136.16] (ppp65-adsl-173.ath.forthnet.gr [62.1.29.173]) by mx-in-04.forthnet.gr (8.13.5/8.13.5) with ESMTP id k03N7B8P022481; Wed, 4 Jan 2006 01:07:12 +0200 Authentication-Results: mx-in-04.forthnet.gr from=dds@aueb.gr; sender-id=neutral; spf=neutral Message-ID: <43BB1F9C.80600@aueb.gr> Date: Wed, 04 Jan 2006 03:06:36 +0200 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en, el, en-us, de MIME-Version: 1.0 To: FreeBSD Tinderbox References: <20060103234924.EEC407302F@freebsd-current.sentex.ca> In-Reply-To: <20060103234924.EEC407302F@freebsd-current.sentex.ca> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 01:06:41 -0000 FreeBSD Tinderbox wrote: > TB --- 2006-01-03 22:24:32 - tinderbox 2.3 running on freebsd-current.sentex.ca > TB --- 2006-01-03 22:24:32 - starting HEAD tinderbox run for alpha/alpha > TB --- 2006-01-03 22:24:32 - cleaning the object tree > TB --- 2006-01-03 22:24:58 - checking out the source tree > TB --- 2006-01-03 22:24:58 - cd /tinderbox/HEAD/alpha/alpha > TB --- 2006-01-03 22:24:58 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src > TB --- 2006-01-03 22:30:53 - building world (CFLAGS=-O2 -pipe) > TB --- 2006-01-03 22:30:53 - cd /src > TB --- 2006-01-03 22:30:53 - /usr/bin/make -B buildworld > >>>>Rebuilding the temporary build tree >>>>stage 1.1: legacy release compatibility shims >>>>stage 1.2: bootstrap tools >>>>stage 2.1: cleaning up the object tree >>>>stage 2.2: rebuilding the object tree >>>>stage 2.3: build tools >>>>stage 3: cross tools >>>>stage 4.1: building includes >>>>stage 4.2: building libraries >>>>stage 4.3: make dependencies >>>>stage 4.4: building everything > > TB --- 2006-01-03 23:36:02 - generating LINT kernel config > TB --- 2006-01-03 23:36:02 - cd /src/sys/alpha/conf > TB --- 2006-01-03 23:36:02 - /usr/bin/make -B LINT > TB --- 2006-01-03 23:36:02 - building LINT kernel (COPTFLAGS=-O2 -pipe) > TB --- 2006-01-03 23:36:02 - cd /src > TB --- 2006-01-03 23:36:02 - /usr/bin/make buildkernel KERNCONF=LINT > >>>>Kernel build for LINT started on Tue Jan 3 23:36:02 UTC 2006 >>>>stage 1: configuring the kernel >>>>stage 2.1: cleaning up the object tree >>>>stage 2.2: rebuilding the object tree >>>>stage 2.3: build tools >>>>stage 3.1: making dependencies >>>>stage 3.2: building everything > > [...] > cc -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -c __reml.S > MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh LINT > cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror vers.c > linking kernel > vfs_syscalls.o(.text+0x6610): In function `normalize_timeval': > : undefined reference to `memmove' > vfs_syscalls.o(.text+0x6614): In function `normalize_timeval': > : undefined reference to `memmove' > *** Error code 1 From the alpha assembly listing I understand that this was caused by the function returning a structure by dereferencing a pointer to it. It should be ok now, but I'm surprised such an operation isn't supported on our alpha build. Diomidis From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 01:32:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA5D16A41F for ; Wed, 4 Jan 2006 01:32:30 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1C18543D5E for ; Wed, 4 Jan 2006 01:32:29 +0000 (GMT) (envelope-from randy@psg.com) Received: from [127.0.0.1] (helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtxPA-00019j-1G; Wed, 04 Jan 2006 01:25:32 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtwGf-0000Sn-RW; Tue, 03 Jan 2006 14:12:41 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17339.4857.348573.80866@roam.psg.com> Date: Tue, 3 Jan 2006 14:12:41 -1000 To: Steve Kargl References: <17338.64976.685459.349707@roam.psg.com> <20060103225401.GA3009@troutmask.apl.washington.edu> <17339.1894.74343.72704@roam.psg.com> <20060103233458.GA3763@troutmask.apl.washington.edu> Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 01:32:30 -0000 ignore me! i checked, and was using wrong==old kernel From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 01:32:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3988016A41F for ; Wed, 4 Jan 2006 01:32:35 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6B1B43D4C for ; Wed, 4 Jan 2006 01:32:34 +0000 (GMT) (envelope-from randy@psg.com) Received: from [127.0.0.1] (helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtxOt-00019L-36; Wed, 04 Jan 2006 01:25:15 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EtwEx-0000SN-7w; Tue, 03 Jan 2006 14:10:55 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17339.4750.741506.183096@roam.psg.com> Date: Tue, 3 Jan 2006 14:10:54 -1000 To: Steve Kargl References: <17338.64976.685459.349707@roam.psg.com> <20060103225401.GA3009@troutmask.apl.washington.edu> <17339.1894.74343.72704@roam.psg.com> <20060103233458.GA3763@troutmask.apl.washington.edu> Cc: FreeBSD Current Subject: Re: mount option is unknown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 01:32:35 -0000 maybe i am being unclear new mount with 'normal' fstab fails # mount -a mount: /dev/da0s1a: Invalid argument and # grep da0s1a /etc/fstab /dev/da0s1a / ufs rw 1 1 randy From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 02:02:44 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6597A16A41F for ; Wed, 4 Jan 2006 02:02:44 +0000 (GMT) (envelope-from richw@richw.org) Received: from smtp2.Stanford.EDU (smtp2.Stanford.EDU [171.67.16.125]) by mx1.FreeBSD.org (Postfix) with ESMTP id C082143D5F for ; Wed, 4 Jan 2006 02:02:43 +0000 (GMT) (envelope-from richw@richw.org) Received: from whodunit.richw.org (SW-90-716-276-1.Stanford.EDU [171.66.155.243]) by smtp2.Stanford.EDU (8.12.11/8.12.11) with ESMTP id k0422fxG024595 for ; Tue, 3 Jan 2006 18:02:41 -0800 Received: from [172.29.0.21] (evilempire.richw.org [172.29.0.21]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: richw) by whodunit.richw.org (Postfix) with ESMTP id 086DD3C9ED; Tue, 3 Jan 2006 18:02:41 -0800 (PST) Date: Tue, 03 Jan 2006 18:02:40 -0800 From: Rich Wales User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: current@freebsd.org References: <20060102221948.EBE475D09@ptavv.es.net> <80965.1136240851@critter.freebsd.dk> <20060102232208.GC42228@cirb503493.alcatel.com.au> <20060103014508.948273C9ED@whodunit.richw.org> <20060103063656.GF42228@cirb503493.alcatel.com.au> In-Reply-To: <20060103063656.GF42228@cirb503493.alcatel.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-Id: <20060104020241.086DD3C9ED@whodunit.richw.org> Cc: Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 02:02:44 -0000 Peter Jeremy wrote: > The Islamic calendar (at least the concensus from some googling) > appears to have 11 leap years in a 30 (lunar) year cycle . . . AFAIK, no, this is not correct. The Islamic calendar is a 12-month, strictly lunar (=not= lunisolar) calendar. The Islamic year is 11 days shorter than a solar year, and there is =no= correction for this discrepancy, so any given Islamic month/day will drift through the seasons over a period of about 33 years. This is why, for example, the Islamic month of fasting (Ramadan) is a little earlier every year (same lunar month, but different solar calendar dates). > . . . and it seems that there isn't even general agreement on > which years are leap years. As I said, there's no such thing as a "leap year" in the Islamic calendar. Were you perhaps reading about how the start of each month (and, thus, the length of each month) is traditionally determined by actual observation of the young crescent moon? Rich Wales richw@richw.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 02:11:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9081E16A41F for ; Wed, 4 Jan 2006 02:11:31 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 807D043D49 for ; Wed, 4 Jan 2006 02:11:28 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (root@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k042BQTZ075137 for ; Wed, 4 Jan 2006 02:11:27 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43BB2ED5.4020306@freebsd.org> Date: Wed, 04 Jan 2006 10:11:33 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: lockmgr: thread 0xc06f50e0 unlocking unheld lock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 02:11:31 -0000 Copyright (c) 1992-2005 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 7.0-CURRENT #1: Mon Jan 2 09:51:43 CST 2006 davidxu@apple.my.domain:/usr/src/sys/i386/compile/gennw ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) D CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf44 Stepping = 4 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 Logical CPUs per core: 2 real memory = 1072218112 (1022 MB) avail memory = 1040052224 (991 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger lockmgr: thread 0xc06f50e0 unlocking unheld lock KDB: stack backtrace: kdb_backtrace(c069e6f9,c06f50e0) at kdb_backtrace+0x29 lockmgr(c06ff8e8,6,c06ff90c,c06f50e0,c0c20d3c) at lockmgr+0x589 smb_co_unlock(c06ff8e0,0,c06f50e0,c0c20d48,c05ac441) at smb_co_unlock+0x1d smb_sm_init(c4acf880,c0c20d74,c0507c4b,c4acf880,0) at smb_sm_init+0x31 nsmb_dev_load(c4acf880,0,0,c06f5c20,0) at nsmb_dev_load+0x1d module_register_init(c06dd404,c1ec00,c1e000,0,c0433455) at module_register_init+0x4b mi_startup() at mi_startup+0x96 begin() at begin+0x2c netsmb_dev: loaded I have following options in kernel config file: options NETSMB options NETSMBCRYPTO options LIBMCHAIN options LIBICONV options SMBFS From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 05:10:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5528F16A41F for ; Wed, 4 Jan 2006 05:10:50 +0000 (GMT) (envelope-from brian@aljex.com) Received: from s1tank.virtdom.com (s1tank.virtdom.com [216.240.101.50]) by mx1.FreeBSD.org (Postfix) with SMTP id D0B5443D4C for ; Wed, 4 Jan 2006 05:10:49 +0000 (GMT) (envelope-from brian@aljex.com) Received: (qmail 81563 invoked by uid 89); 4 Jan 2006 05:45:05 -0000 Received: from ool-4355e580.dyn.optonline.net (HELO venti) (brian@aljex.com@67.85.229.128) by s1tank.virtdom.com with SMTP; 4 Jan 2006 05:45:05 -0000 Message-ID: <00fb01c610ed$392fdf10$951fa8c0@venti> From: "Brian K. White" To: "Jonathan Fosburgh" , References: <20060103232319.E097D1560@fury.csh.rit.edu> <200601031855.17687.jonathan@fosburgh.org> Date: Wed, 4 Jan 2006 00:10:47 -0500 Organization: Aljex Software MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Cc: Jordan Sissel Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 05:10:50 -0000 ----- Original Message ----- From: "Jonathan Fosburgh" To: Cc: "Jordan Sissel" Sent: Tuesday, January 03, 2006 7:55 PM Subject: Re: usb mouse support update plans > On Tuesday 03 January 2006 17:23, Jordan Sissel wrote: >> On my grande circuit of trying to make mouse support better for FreeBSD, >> I've finally come about to working on usb mice. I've done a bit of >> research about usb hid, and I need some feedback on where I should take >> usb mouse support. >> > > Oh, good! :) > >> Moral of this story is that I want to make known-broken mice work with >> FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice >> (including usb->ps2 adapted mice), and probably others. >> > >> >> How can you help? If you are having issues with mouse support in >> FreeBSD I need to know the following: >> - Mouse model and brand (as specific as possible would help) >> - Symptoms of strange behavior >> - Environment (moused+ums? plain ums in X? plain psm in X? moused >> with serial mice?) > > Check usb/77604 for some mice known to have problems and for a fix for > them. Indeed "Oh Good!" I would soooo love to ditch the hacked knoppix-4 I'm currently net booting and nfs mounting to run on my thin client. (I guess a nfs mounted full dvd version of knoppix-4.0 with 4 more gigs of room to grow besides would have to be a fat client) The only reason I'm using linux on this thing is because this usb wireless keyboard with built-in touch pad works under linux and not under freebsd, including 6.0 current as of several weeks ago. Sony VGP-WKB1/U http://keyofr.homeunix.net:81/DCIM/100CANON/IMG_0041.JPG http://keyofr.homeunix.net:81/DCIM/100CANON/IMG_0042.JPG http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_DisplayProductInformation-Start?ProductSKU=VGPWKB1&CategoryName=hid_pr_p_20_per_ecoupon_all&DCMP=CNET_DF&HQS=NBA_VGPWKB1 http://www.gizmodo.com/gadgets/peripherals/input/vaio-vgpwkb1-wireless-keyboard-with-touchpad-036744.php Symptoms: keyboard works fine, mouse is unrecognized. (neither at the OS or X levels) It's been several weeks since I gave up so I'll need to perform tests again to define "mouse is unrecognized" better. I _think_ on the latest ThinBSD, which is 5.4-release, and all later versions, that the touch pad pointer works but not the buttons. I may be misremembering but we don't have to guess once I try it again. Some people have said it might be that it's because there is a single usb wireless receiverfor 3 devices (keyboard, built-in touchpad mouse, and a seperate optical mouse which I don't happen to use.) And the keyboard sort of takes exclusive control of the usb device. I'm very fuzzy on the low level workings of usb in any os, or drivers in any os for that matter. But I know how to capture kernel messages and perform other tests upon request. I have a net booting copy of 6.0-current from some weeks ago all ready to boot on demand so I can resume testing fairly easy. And I can build new kernels & world for it no problem. I can also capture various diagnostics from the fully working linux too. I've even offered to buy and ship one of these kits for anyone if they want to work on making it work (you get to keep it) That offer still stands. The device works out of the box, no drivers, on XP and I can use usbsnoop if desired too to capture xp traffic, but since it already works on linux then the code to make it work is already out there to be mined right? Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 06:50:54 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44D1416A420; Wed, 4 Jan 2006 06:50:54 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B22EE43D45; Wed, 4 Jan 2006 06:50:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k046opdK069071; Wed, 4 Jan 2006 01:50:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k046oqAn065393; Wed, 4 Jan 2006 01:50:52 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E4A3F7302F; Wed, 4 Jan 2006 01:50:51 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060104065051.E4A3F7302F@freebsd-current.sentex.ca> Date: Wed, 4 Jan 2006 01:50:51 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 06:50:54 -0000 TB --- 2006-01-04 06:09:07 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-04 06:09:07 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2006-01-04 06:09:07 - cleaning the object tree TB --- 2006-01-04 06:09:17 - checking out the source tree TB --- 2006-01-04 06:09:17 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2006-01-04 06:09:17 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-04 06:15:53 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-04 06:15:53 - cd /src TB --- 2006-01-04 06:15:53 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries [...] cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_ng.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_nw.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_pr.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/gen_sv.c cc -O2 -pipe -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/port/freebsd/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind/include -I/src/lib/bind/bind -DVERSION='"9.3.2"' -DHAVE_CONFIG_H -DLIBINTERFACE=4 -DLIBREVISION=2 -DLIBAGE=0 -DWANT_IPV6 -DOPENSSL -DUSE_MD5 -DWORDS_BIGENDIAN -DNS_LOCALSTATEDIR='"/var"' -DNS_SYSCONFDIR='"/etc/namedb"' -DNAMED_CONFFILE='"/etc/namedb/named.conf"' -DRNDC_CONFFILE='"/etc/namedb/rndc.conf"' -DRNDC_KEYFILE='"/etc/namedb/rndc.key"' -I/src/lib/bind/bind/.. -I/src/lib/bind/bind/../../../contrib/bind9/lib/bind9/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include/dst -I/src/lib/bind/bind/../../../contrib/bind9/lib/dns/include -I/src/lib/bind/bind/../dns -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccc/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isccfg/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/isc/nothreads/include -I /src/lib/bind/bind/../../../contrib/bind9/lib/isc/include -I/src/lib/bind/bind/../isc -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/unix/include -I/src/lib/bind/bind/../../../contrib/bind9/lib/lwres/include -I/src/lib/bind/bind/../lwres -c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c: In function `getaddrinfo': /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:342: error: structure has no member named `_ai_pad' /src/lib/bind/bind/../../../contrib/bind9/lib/bind/irs/getaddrinfo.c:373: error: structure has no member named `_ai_pad' *** Error code 1 Stop in /src/lib/bind/bind. *** Error code 1 Stop in /src/lib/bind. *** Error code 1 Stop in /src/lib. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-04 06:50:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-04 06:50:51 - ERROR: failed to build world TB --- 2006-01-04 06:50:51 - tinderbox aborted TB --- 0.48 user 1.67 system 2503.38 real From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 07:06:54 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F2E2916A420 for ; Wed, 4 Jan 2006 07:06:53 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp1-g19.free.fr (smtp1-g19.free.fr [212.27.42.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E771A43D68 for ; Wed, 4 Jan 2006 07:06:51 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp1-g19.free.fr (Postfix) with ESMTP id D774569230 for ; Wed, 4 Jan 2006 08:06:49 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id k0476jEp003043 for ; Wed, 4 Jan 2006 08:06:47 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Wed, 4 Jan 2006 08:06:36 +0100 User-Agent: KMail/1.8.3 X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601040806.37953.thierry@herbelot.com> Subject: panic: spin lock held too long (while rebooting) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 07:06:54 -0000 I just had this panic, on an SMP machine Rebooting... cpu_reset: Stopping other CPUs spin lock sched lock held by 0xc16de480 for > 5 seconds panic: spin lock held too long cpuid = 0 KDB: enter: panic [thread pid 18843 tid 100041 ] Stopped at kdb_enter+0x2b: nop db> trace Tracing pid 18843 tid 100041 td 0xc182e600 kdb_enter(c0880e62) at kdb_enter+0x2b panic(c088029b,c094cdf0,c16de480,c0880272,c08803ee) at panic+0x127 _mtx_lock_spin(c094cdf0,c182e600,2,c087cbfa,cb) at _mtx_lock_spin+0xa9 _mtx_lock_spin_flags(c094cdf0,2,c087cbfa,cb) at _mtx_lock_spin_flags+0x9e hardclock_cpu(0,c09cdb20,0,c72a2ba0,c08069cd) at hardclock_cpu+0x25 hardclock(0,c0816772) at hardclock+0x13 lapic_handle_timer(8,28,c16b0028,c16ba00c,0) at lapic_handle_timer+0x71 Xtimerint() at Xtimerint+0x1e --- interrupt, eip = 0xc0816772, esp = 0xc72a2be8, ebp = 0xc72a2c0c --- DELAY(f4240) at DELAY+0x92 cpu_reset(f4240,c0881049,c72a2c64,c0653a0f,0) at cpu_reset+0xc8 shutdown_reset(0,0,c16ba00c,0,c0880e86) at shutdown_reset+0x1c boot(0,c094ce0c,0,c0880e86,a1) at boot+0x553 reboot(c182e600,c72a2d04,c182e600,0,2) at reboot+0x32 syscall(3b,3b,3b,0,2) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (55, FreeBSD ELF32, reboot), eip = 0x280adc5f, esp = 0xbfbfedcc, ebp = 0xbfbfee18 --- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 10:45:21 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 463FA16A420; Wed, 4 Jan 2006 10:45:21 +0000 (GMT) In-Reply-To: <00fb01c610ed$392fdf10$951fa8c0@venti> from "Brian K. White" at "Jan 4, 2006 00:10:47 am" To: brian@aljex.com (Brian K. White) Date: Wed, 4 Jan 2006 10:45:21 +0000 (GMT) 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: <20060104104521.463FA16A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 10:45:21 -0000 > > > On Tuesday 03 January 2006 17:23, Jordan Sissel wrote: > >> On my grande circuit of trying to make mouse support better for FreeBSD, > >> I've finally come about to working on usb mice. I've done a bit of > >> research about usb hid, and I need some feedback on where I should take > >> usb mouse support. > >> > > > > Oh, good! :) > > > >> Moral of this story is that I want to make known-broken mice work with > >> FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice > >> (including usb->ps2 adapted mice), and probably others. > >> > > > >> > >> How can you help? If you are having issues with mouse support in > >> FreeBSD I need to know the following: > >> - Mouse model and brand (as specific as possible would help) > >> - Symptoms of strange behavior > >> - Environment (moused+ums? plain ums in X? plain psm in X? moused > >> with serial mice?) > > > > Check usb/77604 for some mice known to have problems and for a fix for > > them. > > Indeed "Oh Good!" > > I would soooo love to ditch the hacked knoppix-4 I'm currently net booting > and nfs mounting to run on my thin client. (I guess a nfs mounted full dvd > version of knoppix-4.0 with 4 more gigs of room to grow besides would have > to be a fat client) Would it be too much trouble for you to describe your system in a bit more depth? "Thin client" is... well, not very helpful. > The only reason I'm using linux on this thing is because this usb wireless > keyboard with built-in touch pad works under linux and not under freebsd, > including 6.0 current as of several weeks ago. That's a really crummy reason to be running Linux. I'm sorry, but it is. [...] > Symptoms: keyboard works fine, mouse is unrecognized. (neither at the OS or > X levels) > > It's been several weeks since I gave up so I'll need to perform tests again > to define "mouse is unrecognized" better. Well, maybe your memory isn't that great, but the intarweb never forgets. Travelling back in time to the freebsd-usb mailing list from July, we find a similar post from you about this very same issue, in which you thankfully had the presence of mind to say: > dmesg on 5.4-release shows this near the end: > > ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 > uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 There's something very strange about this output, by the way. I don't think you cut & pasted it exactly as it appeared on the screen. I think it should look more like this: > ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 > kbd1 at ukbd0 > uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 But even this isn't quite right, because I don't think both devices should appear at address 2 on the same hub. I suspect you transcribed the information and typed it in wrong. Assuming the presence of the 'uhid0' line isn't a mistake, the real description of the problem is: "the mouse is showing up as a uhid(4) evice instead of a ums(4) device." uhid(4) is a generic driver for USB devices in the Human Interface Device class. This includes mice, keyboards, joysticks, gamepads, drawing tablets, and so on. Keyboards and mice are considered special enough to warrant their own private drivers (ukbd(4) and ums(4)), largely to make them emulate the behavior of their non-USB ancestors (thereby allowing existing application software to use USB keyboards and mice without having to be modified to include special USB support). Any HID device that doesn't have a special driver just gets picked up by the uhid(4) generic driver. When you plug in your mouse, the USB mouse driver probe checks its HID usage group to make sure it's a 'generic desktop' device with 'mouse' usage. If this check fails, the driver decides the device isn't really a mouse and fails the probe. Later, the uhid(4) driver will claim the device since nobody else did. Now, there's two possible things that can be going wrong here: 1) The ums(4) driver isn't loaded. Given that the ums(4) driver is part of the GENERIC kernel, the only way this could have happened is if you went and built your own kernel and then for some stange reason took 'device ums' out of the config file. You never bothered to state whether or not you compiled your own kernel, so I have no way of knowing whether or not this happened. 2) The mouse is not reporting itself as a generic desktop/mouse device, and the ums(4) driver is ignoring it. If the issue is thing 1, then you need to either add 'device ums' back to your kernel config, or add 'ums_load="YES"' to your /boot/loader.conf file. If the issue is thing 2, then you need to do the following: - Boot up FreeBSD 6.0. - Plug the wireless keyboard/mouse into a USB port on a FreeBSD machine - Wait until you see the ukbd0/uhid0 probe output on the console (i.e. wait until FreeBSD sees the devices) - Run "dmesg" and save _ALL_ the output. Report it to us so we can see it. And I mean _ALL_ of it. - Run the following commands, as root: # usbdevs -v # usbhidctl -f /dev/uhid0 -r - This should show all the information that the mouse reports about itself. Save the output (there'll probably be a page or two of information) and report _ALL_ of it here so that we can see it. And I mean _ALL_ of it. If it really is a USB mouse class device and it's just misrepresenting itself, then it's likely the USB_MATCH() routine in sys/dev/usb/ums.c can be tweaked a little to recognize the device. But we won't know for sure until we see the output of the usbhidctl command. > I _think_ on the latest ThinBSD, which is 5.4-release, and all later > versions, that the touch pad pointer works but not the buttons. I may be > misremembering but we don't have to guess once I try it again. Why didn't you try it again before writing this e-mail? Then your faulty memory wouldn't be an issue. Also, what the heck is ThinBSD? > Some people have said it might be that it's because there is a single usb > wireless receiverfor 3 devices (keyboard, built-in touchpad mouse, and a > seperate optical mouse which I don't happen to use.) And the keyboard sort > of takes exclusive control of the usb device. The people who told you this are feelthy liars. Feelthy, I say. > The device works out of the box, no drivers, on XP and I can use usbsnoop if > desired too to capture xp traffic, but since it already works on linux then > the code to make it work is already out there to be mined right? I don't think the solution will be all that complicated. Just go boot up FreeBSD 6.0 and report the stuff I asked for. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 10:59:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA4A416A41F for ; Wed, 4 Jan 2006 10:59:10 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12FED43D4C for ; Wed, 4 Jan 2006 10:59:09 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04At5WT091504; Wed, 4 Jan 2006 11:55:05 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04AwxgL028096; Wed, 4 Jan 2006 11:58:59 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 11:58:59 +0100 From: Alexander Leidinger To: David Gilbert Message-ID: <20060104115859.554eff0a@Magellan.Leidinger.net> In-Reply-To: <17339.4293.673806.446317@canoe.dclg.ca> References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> <17339.4293.673806.446317@canoe.dclg.ca> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 10:59:11 -0000 On Tue, 3 Jan 2006 19:03:17 -0500 David Gilbert wrote: > >>>>> "Alexander" == Alexander Leidinger writes: > > [various problems with wi, deleted] > > Alexander> The problem is, that the wi driver isn't ported to the > Alexander> current WLAN infrastructure. There's no documentation > Alexander> available for the WLAN infrastructure, so you have to read > Alexander> the source (the ath driver is the de-facto reference driver > Alexander> for the WLAN stuff), search the net and if nothing helps, > Alexander> ask sam@FreeBSD.org some well thought questions. > > I also thought that someone might have comments about a wi0 as an > access point. This used to work, but all clients (even windoze) seem > to loose association every 20 to 40 minutes (although the timing is > random it seems). I'm sure this is just another problem related to the outdated WLAN part of wi. > Alexander> If you have the time and energy to have a look at porting > Alexander> the wi driver to (at least parts of) the current WLAN > Alexander> framework, all wi users would appreciate some patches... > > Not that I'm afraid of development, but I'm unfamilliar with the > difference between the revisions of acceptable wifi behaviour. There are maybe 2 or 3 people in the FreeBSD world which are (at least partly) familiar with it. And all of them aren't interested or don't have time to take care of wi (or think the wi technology is outdated and should RIP). So it comes down to "someone with interest in wi has to make himself familiar with the WLAN infrastructure". I'm sure Sam will answer questions if the person attacking the problem stumbles upon some questions regarding the WLAN infrastructure part. Bye, Alexander. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 11:18:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6EC916A41F for ; Wed, 4 Jan 2006 11:18:00 +0000 (GMT) (envelope-from dalius.dobravolskas@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id C057143D5A for ; Wed, 4 Jan 2006 11:17:59 +0000 (GMT) (envelope-from dalius.dobravolskas@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1853262wxc for ; Wed, 04 Jan 2006 03:17:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SOlgsW96hxX2gJJswnJWcZ4nRKgYG6Lze6D40+M+tmCq0luEJ2LmZpLxhYs6grlTmxsht554dGmNHVxcL3G4iOBC0Y1VQxfEOnspQ4+HLZQupiaKqm3wkqzoaXCT3GOc77XYeJhOXjDAXhpIyqTBzWC1wxh8OA8TPRaknjh0gTQ= Received: by 10.70.53.9 with SMTP id b9mr2525126wxa; Wed, 04 Jan 2006 03:17:58 -0800 (PST) Received: by 10.70.54.11 with HTTP; Wed, 4 Jan 2006 03:17:56 -0800 (PST) Message-ID: <98dd087e0601040317j46c10561m@mail.gmail.com> Date: Wed, 4 Jan 2006 13:17:56 +0200 From: Dalius Dobravolskas To: freebsd-current@freebsd.org In-Reply-To: <20060104104521.463FA16A420@hub.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <00fb01c610ed$392fdf10$951fa8c0@venti> <20060104104521.463FA16A420@hub.freebsd.org> Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 11:18:00 -0000 Hello, I will join discussion to make it more interesting :-) > > ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 > > kbd1 at ukbd0 > > uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 ... > But even this isn't quite right, because I don't think both devices > should appear at address 2 on the same hub. I suspect you transcribed > the information and typed it in wrong. He/She does not. I have the same situation (two devices on same addr): ums0: vendor 0x1733 Wireless RF Mouse, rev 1.10/0.01, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhid0: Cellink Co., LTD. Wireless RF Mouse, rev 1.10/0.01, addr 2, iclass 3= /1 ums0 works OK but extra buttons (uhid0) does not. Windows recognise my mouse as UHID device. Those extra buttons in windows works as mute, volume up, volume down, page up, page down. My mouse has two modes (mouse and presentation tool). My mouse is neither mouse nor keyboard. It is something between. It would be great if I could use my mouse as presentation tool even though it is the poorest reason in the world. > Assuming the presence of the 'uhid0' line isn't a mistake, the real > description of the problem is: "the mouse is showing up as a uhid(4) > evice instead of a ums(4) device." Because mouse is more uhid device than mouse IMHO. ... > Keyboards and mice are considered special enough > to warrant their own private drivers (ukbd(4) and ums(4)) So maybe this philosophy should be reconsidered? ... > 2) The mouse is not reporting itself as a generic desktop/mouse > device, and the ums(4) driver is ignoring it. 3) The device reported itself as keyboard and algorithm does not check for mouse; It must be checked it is just my guess ;) Brian, could you try to remove ukbd from kernel in this case and look if mouse is found? Best regards, Dalius From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 11:45:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1019A16A41F for ; Wed, 4 Jan 2006 11:45:35 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from pipa.profix.cz (ruprt.hosting4u.cz [82.208.25.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA15C43D49 for ; Wed, 4 Jan 2006 11:45:31 +0000 (GMT) (envelope-from dandee@hellteam.net) Received: from localhost (localhost [127.0.0.1]) by pipa.profix.cz (Postfix) with ESMTP id 3AF9B4E706 for ; Wed, 4 Jan 2006 12:45:30 +0100 (CET) Received: from pipa.profix.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22563-07 for ; Wed, 4 Jan 2006 12:45:30 +0100 (CET) Received: from gandalf (unknown [80.95.121.105]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.profix.cz (Postfix) with ESMTP id D91B94E705 for ; Wed, 4 Jan 2006 12:45:29 +0100 (CET) From: =?us-ascii?Q?Daniel_Dvorak?= To: Date: Wed, 4 Jan 2006 12:45:23 +0100 Message-ID: <001401c61124$5c5f4480$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcYRJFjqQNHmhvOCTL+STxf57V36jw== X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 11:45:35 -0000 > -----Original Message----- > From: owner-freebsd-current@freebsd.org > [ mailto:owner-freebsd-current@freebsd.org] On Behalf Of David Gilbert > Sent: Wednesday, January 04, 2006 1:03 AM > To: Alexander Leidinger > Cc: freebsd-current@freebsd.org; David Gilbert > Subject: Re: dhclient ignoring link on wi0 > > > I also thought that someone might have comments about a wi0 > as an access point. This used to work, but all clients (even > windoze) seem to loose association every 20 to 40 minutes > (although the timing is random it seems). > > > Dave. Not only this one, to make the picture complete. For example, another relevant issue is: from rc.conf: ifconfig_wi1="inet w.x.y.z/m ssid A mediaopt hostap channel 4 up" reality ? # ifconfig wi1 wi1: flags=8843 mtu 1500 media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps ) status: associated authmode OPEN privacy OFF txpowmax 100 dtimperiod 1 bintval 100 It has never reached more than DS/2Mbps in hostap mode. ... and other issue is about transmit power limit, no chance to limit tx, txpowmax does not work at all. Card transmits at full power. I know from my friend there exists some patch for the first issue, but CVS does not contain it even in 7-CURRENT, let alone 6-STABLE. Dan _____ avast! Antivirus : Odchozi zprava cista. Virova databaze (VPS): 0601-1, 03.01.2006 Testovano: 4.1.2006 12:45:23 avast! - copyright (c) 1988-2005 ALWIL Software. From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 12:01:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7793E16A41F; Wed, 4 Jan 2006 12:01:31 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7A1143D5D; Wed, 4 Jan 2006 12:01:30 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04BvVTT091769; Wed, 4 Jan 2006 12:57:32 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04C1QMx039575; Wed, 4 Jan 2006 13:01:27 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 13:01:26 +0100 From: Alexander Leidinger To: Dalius Dobravolskas Message-ID: <20060104130126.0bd6a9f9@Magellan.Leidinger.net> In-Reply-To: <98dd087e0601040317j46c10561m@mail.gmail.com> References: <00fb01c610ed$392fdf10$951fa8c0@venti> <20060104104521.463FA16A420@hub.freebsd.org> <98dd087e0601040317j46c10561m@mail.gmail.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: wpaul@freebsd.org, freebsd-current@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 12:01:31 -0000 On Wed, 4 Jan 2006 13:17:56 +0200 Dalius Dobravolskas wrote: > 3) The device reported itself as keyboard and algorithm does not check > for mouse; It must be checked it is just my guess ;) Brian, could you > try to remove ukbd from kernel in this case and look if mouse is > found? Maxime (CCed) is working on porting the uhidev part from NetBSD. This is supposed to fix those problems (at least if I read the symptoms correctly). Bill, the problem is that some combi-devices don't meet the expectations of FreeBSD. AFAIK they report one device with 2 functions while FreeBSD currently needs 2 devices to work as expected. Bye, Alexander. -- I believe the technical term is "Oops!" http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 12:58:45 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0381B16A41F for ; Wed, 4 Jan 2006 12:58:45 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D07043D49 for ; Wed, 4 Jan 2006 12:58:43 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04CsjgL092002; Wed, 4 Jan 2006 13:54:46 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04CwfXn050081; Wed, 4 Jan 2006 13:58:41 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 13:58:40 +0100 From: Alexander Leidinger To: Antoine Brodin Message-ID: <20060104135840.5c55c494@Magellan.Leidinger.net> In-Reply-To: <20060102212309.6ebcf836.antoine.brodin@laposte.net> References: <20060102101653.GA65178@stud.fit.vutbr.cz> <20060102200347.2bumr7okkkgossww@netchild.homeip.net> <20060102212309.6ebcf836.antoine.brodin@laposte.net> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: xdivac02@stud.fit.vutbr.cz, current@freebsd.org Subject: Re: AMD cache values for page colouring X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 12:58:45 -0000 On Mon, 2 Jan 2006 21:23:09 +0100 Antoine Brodin wrote: > The detection doesn't work because the cpu_exthigh variable isn't > initialized. > And if you and *ways with 0x0f, it will never be 255. I committed a fix, this should result in working autotuning on AMD and Intel CPU's. Bye, Alexander. -- Speak softly and carry a cellular phone. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 13:36:40 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CC2F16A41F for ; Wed, 4 Jan 2006 13:36:40 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EAA043D49 for ; Wed, 4 Jan 2006 13:36:39 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5260155 for multiple; Wed, 04 Jan 2006 08:37:57 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04DaUsH002574; Wed, 4 Jan 2006 08:36:31 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 4 Jan 2006 08:36:28 -0500 User-Agent: KMail/1.8.3 References: <20060103233406.GA1564@hut.isi.edu> In-Reply-To: <20060103233406.GA1564@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601040836.29244.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1228/Wed Jan 4 05:29:17 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Ted Faber Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 13:36:40 -0000 On Tuesday 03 January 2006 06:34 pm, Ted Faber wrote: > On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 > package against the new source, my Xserver won't allocate many video > modes because it can't open /dev/agpgart to allocate memory. The video > card is an Intel I810 - 865G chipset. > > On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide > appears (which seems to be hinted at in the comments to the most recent > change to /sys/pci/agp_i810.c from the CVS tree). I've attached a > verbose dmesg from the kernel recent -CURRENT kernel. > > Anyone else having a similar problem or know what I'm doing wrong? I'm > happy to test patches or provide more info. vgapci doesn't create a /dev entry, but it did probe. Can you get devinfo = =2Dv=20 output? =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 13:40:25 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B45216A41F for ; Wed, 4 Jan 2006 13:40:25 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE91543D5C for ; Wed, 4 Jan 2006 13:40:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5260426 for multiple; Wed, 04 Jan 2006 08:41:37 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04De9xr002598; Wed, 4 Jan 2006 08:40:10 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, thierry@herbelot.com Date: Wed, 4 Jan 2006 08:38:48 -0500 User-Agent: KMail/1.8.3 References: <200601040806.37953.thierry@herbelot.com> In-Reply-To: <200601040806.37953.thierry@herbelot.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601040838.49663.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1228/Wed Jan 4 05:29:17 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: panic: spin lock held too long (while rebooting) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 13:40:25 -0000 On Wednesday 04 January 2006 02:06 am, Thierry Herbelot wrote: > I just had this panic, on an SMP machine > > Rebooting... > cpu_reset: Stopping other CPUs > spin lock sched lock held by 0xc16de480 for > 5 seconds > panic: spin lock held too long > cpuid =3D 0 > KDB: enter: panic > [thread pid 18843 tid 100041 ] > Stopped at kdb_enter+0x2b: nop > db> trace > Tracing pid 18843 tid 100041 td 0xc182e600 > kdb_enter(c0880e62) at kdb_enter+0x2b > panic(c088029b,c094cdf0,c16de480,c0880272,c08803ee) at panic+0x127 > _mtx_lock_spin(c094cdf0,c182e600,2,c087cbfa,cb) at _mtx_lock_spin+0xa9 > _mtx_lock_spin_flags(c094cdf0,2,c087cbfa,cb) at _mtx_lock_spin_flags+0x9e > hardclock_cpu(0,c09cdb20,0,c72a2ba0,c08069cd) at hardclock_cpu+0x25 > hardclock(0,c0816772) at hardclock+0x13 > lapic_handle_timer(8,28,c16b0028,c16ba00c,0) at lapic_handle_timer+0x71 > Xtimerint() at Xtimerint+0x1e > --- interrupt, eip =3D 0xc0816772, esp =3D 0xc72a2be8, ebp =3D 0xc72a2c0c= --- > DELAY(f4240) at DELAY+0x92 > cpu_reset(f4240,c0881049,c72a2c64,c0653a0f,0) at cpu_reset+0xc8 > shutdown_reset(0,0,c16ba00c,0,c0880e86) at shutdown_reset+0x1c > boot(0,c094ce0c,0,c0880e86,a1) at boot+0x553 > reboot(c182e600,c72a2d04,c182e600,0,2) at reboot+0x32 > syscall(3b,3b,3b,0,2) at syscall+0x27e > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (55, FreeBSD ELF32, reboot), eip =3D 0x280adc5f, esp =3D > 0xbfbfedcc, ebp =3D 0xbfbfee18 --- Next time you get this, can you use 'show threads' to figure out the tid fo= r=20 the thread whose pointer is in the printf (0xc16de480 in this case) and the= n=20 do a trace of that thread? =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 13:40:25 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 47A9D16A420; Wed, 4 Jan 2006 13:40:25 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2237943D5D; Wed, 4 Jan 2006 13:40:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5260427 for multiple; Wed, 04 Jan 2006 08:41:37 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04De9xs002598; Wed, 4 Jan 2006 08:40:10 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 4 Jan 2006 08:40:07 -0500 User-Agent: KMail/1.8.3 References: <1136000459.660.12.camel@RabbitsDen> In-Reply-To: <1136000459.660.12.camel@RabbitsDen> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-5" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601040840.09169.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1228/Wed Jan 4 05:29:17 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Warner Losh , "Alexandre \"Sunny\" Kovalenko" Subject: Re: Fatal trap 12 when inserting Linksys WPC55AG cardbus card on 12/30 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 13:40:25 -0000 On Friday 30 December 2005 10:40 pm, Alexandre "Sunny" Kovalenko wrote: > This happens on -CURRENT as of 8:00AM, December 30: > > Unread portion of the kernel message buffer: > Status is 0x30000821 d8bb0000 > cbb0: card inserted: event=3D0x00000000, state=3D30000821 > cbb0: cbb_power: 3V > Interrupt storm detected on "irq10:"; throttling interrupt source > > > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0xda183000 > fault code =3D supervisor read, page not present > instruction pointer =3D 0x20:0xc04ac0f8 > stack pointer =3D 0x28:0xd8b62728 > frame pointer =3D 0x28:0xd8b62738 > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 21 (cbb0) Does this still occur on recent HEAD? There have been several cardbus chan= ges=20 in the past few days. > Dumping 607 MB (2 chunks) > chunk 0: 1MB (159 pages) ... ok > chunk 1: 607MB (155376 pages) 591 575 559 543 527 511 495 479 463 447 > 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 > 143 127 111 95 79 63 47 31 15 > > #0 doadump () at pcpu.h:166 > 166 pcpu.h: No such file or directory. > in pcpu.h > #0 doadump () at pcpu.h:166 > #1 0xc0471a29 in db_fncall (dummy1=3D0, dummy2=3D0, dummy3=3D1999, > dummy4=3D0xd8b624e0 at /usr/src/sys/ddb/db_command.c:489 > #2 0xc04717a2 in db_command (last_cmdp=3D0xc07b70c4, cmd_table=3D0x0, > aux_cmd_tablep=3D0xc077d288, aux_cmd_tablep_end=3D0xc077d28c) > at /usr/src/sys/ddb/db_command.c:404 > #3 0xc04718aa in db_command_loop () > at /usr/src/sys/ddb/db_command.c:455 > #4 0xc04739b5 in db_trap (type=3D12, code=3D0) > at /usr/src/sys/ddb/db_main.c:221 > #5 0xc05764f7 in kdb_trap (type=3D0, code=3D0, tf=3D0xd8b626e8) > at /usr/src/sys/kern/subr_kdb.c:485 > #6 0xc0721a8b in trap_fatal (frame=3D0xd8b626e8, eva=3D0) > at /usr/src/sys/i386/i386/trap.c:853 > #7 0xc0721795 in trap_pfault (frame=3D0xd8b626e8, usermode=3D0, > eva=3D3659018240) > at /usr/src/sys/i386/i386/trap.c:770 > #8 0xc07212f2 in trap (frame=3D > {tf_fs =3D 8, tf_es =3D 40, tf_ds =3D 40, tf_edi =3D 20480, tf_esi = =3D 1, > tf_ebp =3D -659151048, tf_isp =3D -659151084, tf_ebx =3D -65 9150952, tf_= edx =3D > -635969536, tf_ecx =3D -635969536, tf_eax =3D 20480, tf_trapno =3D 12, tf= _err > =3D 0, tf_eip =3D -1068842760, tf_cs =3D 32, tf_eflags =3D 66050, tf_esp = =3D > -1009411456, tf_ss =3D -659150948}) at /usr/src/sys/i386/i386/trap.c:455#9 > 0xc070dc9a in calltrap () at /usr/src/sys/i386/i386/exception.s:137 > #10 0xc04ac0f8 in cardbus_read_tuple_mem (cbdev=3D0xc39f9680, > res=3D0xd8b62798, start=3D20480, > off=3D0xd8b62798, tupleid=3D0x5000, len=3D0xd8b627a0, tupledata=3D0xd= 8b627ac > "") at bus.h:224 > #11 0xc04ac1f3 in cardbus_read_tuple (cbdev=3D0xc39f9680, child=3D0x5000, > res=3D0xda17e000, > start=3D20480, off=3D0xd8b62798, tupleid=3D0xd8b6279c, len=3D0xda17e0= 00, > tupledata=3D0x5000
) > at /usr/src/sys/dev/cardbus/cardbus_cis.c:458 > #12 0xc04aca95 in cardbus_parse_cis (cbdev=3D0xc39f9680, child=3D0xc3d59b= 00, > callbacks=3D0xd8b62bd0, argp=3D0x0) > at /usr/src/sys/dev/cardbus/cardbus_cis.c:645 > #13 0xc04acb96 in cardbus_do_cis (cbdev=3D0x5000, child=3D0x5000) > at /usr/src/sys/dev/cardbus/cardbus_cis.c:691 > #14 0xc04ab17d in cardbus_attach_card (cbdev=3D0xc39f9680) > at /usr/src/sys/dev/cardbus/cardbus.c:499 > #15 0xc04d246f in cbb_insert (sc=3D0xc39b4000) at card_if.h:82 > #16 0xc04d21eb in cbb_event_thread (arg=3D0xc39b4000) > at /usr/src/sys/dev/pccbb/pccbb.c:507 > #17 0xc053b2bf in fork_exit (callout=3D0xc04d2080 , > arg=3D0x5000, > frame=3D0x5000) at /usr/src/sys/kern/kern_fork.c:790 > #18 0xc070dcfc in fork_trampoline () > at /usr/src/sys/i386/i386/exception.s:198 > (kgdb) > > On the kernel built on December 17 (not necessarily -CURRENT as of > December 17) card works properly. Here are dmesg bits from card > insertion: > > Status is 0x30000821 > cbb0: card inserted: event=3D0x00000000, state=3D30000821 > cbb0: cbb_power: 3V > Interrupt storm detected on "irq10:"; throttling interrupt source > cardbus0: Non-prefetchable memory at 88000000-8800ffff > ath0: mem 0x88000000-0x8800ffff irq 10 at device 0.0 on > cardbus0 > ath0: Ethernet address: 00:0c:41:dd:c7:0d > ath0: mac 5.6 phy 4.1 radio 3.6 > > Cardbus controller is: > > cbb0@pci0:10:0: class=3D0x060700 card=3D0xc60214ff chip=3D0x69721217 rev= =3D0x00 > hdr=3D0x02 > vendor =3D 'O2 Micro Inc' > device =3D 'OZ6912/711E0 SmartCardBus Controller' > class =3D bridge > subclass =3D PCI-CardBus > > PCMCIA-to-CF adapter does not cause Fatal trap. > > If there are any other bits of information I can provide, please, let me > know. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 14:55:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6312516A41F for ; Wed, 4 Jan 2006 14:55:30 +0000 (GMT) (envelope-from unixfreunde@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id C5D1F43D46 for ; Wed, 4 Jan 2006 14:55:29 +0000 (GMT) (envelope-from unixfreunde@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so2981218nzo for ; Wed, 04 Jan 2006 06:55:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:subject:message-id:x-mailer:mime-version:content-type:content-transfer-encoding; b=fU0jsXDe35zX+trKeODQ7WwfVYfsS+cD/M/K4jDfdLaJdCFxc5C9fr7yXXkhwakN931v0oYSrxUlo+q/S1qIHeT14/0b/1w11IOdld4r1I58ZmX6PTgtPettuNdm6WdaGbMUez++TrrqUbt5SrxgEYPYcbVJ3qW0ysRNZ+NEvsU= Received: by 10.36.13.1 with SMTP id 1mr467973nzm; Wed, 04 Jan 2006 06:55:22 -0800 (PST) Received: from splash.homeunix.org ( [84.141.43.199]) by mx.gmail.com with ESMTP id 34sm3919121nza.2006.01.04.06.55.18; Wed, 04 Jan 2006 06:55:20 -0800 (PST) Date: Wed, 4 Jan 2006 16:02:07 +0100 From: Martin Wilke To: freebsd-current@freebsd.org Message-ID: <20060104160207.5f324c1c@splash.homeunix.org> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 Subject: next gcc update ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 14:55:30 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBMQ0KDQpIZWxsbw0K DQp3aGVuIGlzIHRoZSBuZXh0IGdjYyB1cGRhdGUgZm9yIHNyYyBnb2luIHRvIGJlIHJlbGVhc2Vk PyBhbmQgd2hpY2gNCnZlcnNpb24gaXMgZ29pbiB0byBiZSBpbmNsdWRlZCBhdCBuZXh0LCAzLjQu NSBvciA0LjAuWD8NCg0KDQotIC0tDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KVmVy c2lvbjogR251UEcgdjEuNC4yIChGcmVlQlNEKQ0KDQppRDhEQlFGRHUrTnZGUlova0JUNHZwOFJB b3RjQUo5OGh4R25jbEgrYXdwS3NWTzU2UUZDdkNmUHBBQ2RIQUZlDQpRa0NRb3pPdGw2cmN0UHhr ckhQbXNWTT0NCj12Q3JQDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0tLS0NCg== From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 15:02:38 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFB9816A41F for ; Wed, 4 Jan 2006 15:02:38 +0000 (GMT) (envelope-from brian@aljex.com) Received: from s1tank.virtdom.com (s1tank.virtdom.com [216.240.101.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 469C143D53 for ; Wed, 4 Jan 2006 15:02:36 +0000 (GMT) (envelope-from brian@aljex.com) Received: (qmail 52730 invoked by uid 89); 4 Jan 2006 15:36:55 -0000 Received: from ool-4355e580.dyn.optonline.net (HELO venti) (brian@aljex.com@67.85.229.128) by s1tank.virtdom.com with SMTP; 4 Jan 2006 15:36:55 -0000 Message-ID: <025a01c6113f$e130a030$951fa8c0@venti> From: "Brian K. White" To: References: <00fb01c610ed$392fdf10$951fa8c0@venti><20060104104521.463FA16A420@hub.freebsd.org><98dd087e0601040317j46c10561m@mail.gmail.com> <20060104130126.0bd6a9f9@Magellan.Leidinger.net> Date: Wed, 4 Jan 2006 10:02:28 -0500 Organization: Aljex Software MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 15:02:39 -0000 ----- Original Message ----- From: "Alexander Leidinger" To: "Dalius Dobravolskas" Cc: ; Sent: Wednesday, January 04, 2006 7:01 AM Subject: Re: usb mouse support update plans > On Wed, 4 Jan 2006 13:17:56 +0200 > Dalius Dobravolskas wrote: > >> 3) The device reported itself as keyboard and algorithm does not check >> for mouse; It must be checked it is just my guess ;) Brian, could you >> try to remove ukbd from kernel in this case and look if mouse is >> found? > > Maxime (CCed) is working on porting the uhidev part from NetBSD. This is > supposed to fix those problems (at least if I read the symptoms > correctly). > > Bill, the problem is that some combi-devices don't meet the > expectations of FreeBSD. AFAIK they report one device with 2 functions > while FreeBSD currently needs 2 devices to work as expected. I'll try that and everything BP said when I get home tonight. Thanks for giving me something _to_ do. Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 16:55:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 281D516A420; Wed, 4 Jan 2006 16:55:50 +0000 (GMT) In-Reply-To: <98dd087e0601040317j46c10561m@mail.gmail.com> from Dalius Dobravolskas at "Jan 4, 2006 01:17:56 pm" To: dalius.dobravolskas@gmail.com (Dalius Dobravolskas) Date: Wed, 4 Jan 2006 16:55:50 +0000 (GMT) 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: <20060104165550.281D516A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 16:55:50 -0000 > Hello, > > I will join discussion to make it more interesting :-) > > > > ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 > > > kbd1 at ukbd0 > > > uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 > ... > > But even this isn't quite right, because I don't think both devices > > should appear at address 2 on the same hub. I suspect you transcribed > > the information and typed it in wrong. > He/She does not. I have the same situation (two devices on same addr): > > ums0: vendor 0x1733 Wireless RF Mouse, rev 1.10/0.01, addr 2, iclass 3/1 > ums0: 3 buttons and Z dir. > uhid0: Cellink Co., LTD. Wireless RF Mouse, rev 1.10/0.01, addr 2, iclass 3/1 > > ums0 works OK but extra buttons (uhid0) does not. Windows recognise my > mouse as UHID > device. Those extra buttons in windows works as mute, volume up, > volume down, page up, > page down. My mouse has two modes (mouse and presentation tool). My > mouse is neither > mouse nor keyboard. It is something between. > > It would be great if I could use my mouse as presentation tool even > though it is the poorest reason in the world. I think you can do this with usbhidaction(1). Like I mentioned earlier, try using usbhidctl -f /dev/uhid0 -r to see what sort of features the device reports. It sounds like it just has some buttons. You can use usbhidaction(1) to have the buttons perform specific actions when activated. You just need to create a config file and launch usbhidaction at system startup. This should be fairly easy to do for the volume controls at least: I'm not sure how to use usbhidaction to emulate keyboard presses. > > Assuming the presence of the 'uhid0' line isn't a mistake, the real > > description of the problem is: "the mouse is showing up as a uhid(4) > > evice instead of a ums(4) device." > Because mouse is more uhid device than mouse IMHO. > > ... > > Keyboards and mice are considered special enough > > to warrant their own private drivers (ukbd(4) and ums(4)) > So maybe this philosophy should be reconsidered? I don't think so. It's convenient to make USB keyboards and mice appear to work just like legacy keyboards and mice. > ... > > 2) The mouse is not reporting itself as a generic desktop/mouse > > device, and the ums(4) driver is ignoring it. > > 3) The device reported itself as keyboard and algorithm does not check > for mouse; It must be checked it is just my guess ;) Brian, could you > try to remove ukbd from kernel in this case and look if mouse is > found? Something tells me this isn't the case. It's possible for a single USB device to have multiple interfaces, but bear in mind that you have to be able to use both the keyboard and mouse at the same time. For that, you would need two separate device instances, not one device whose personality can be toggled back and forth between keyboard mode and mouse mode. Once again, we need to know what usbdevs -v and usbhidctl have to say before we can speculate further. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:05:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 699E516A420 for ; Wed, 4 Jan 2006 17:05:29 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 95FAB43D68 for ; Wed, 4 Jan 2006 17:05:28 +0000 (GMT) (envelope-from randy@psg.com) Received: from [127.0.0.1] (helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuBsO-000IIe-7Y for freebsd-current@freebsd.org; Wed, 04 Jan 2006 16:52:40 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuBr5-000Cx8-6n for freebsd-current@freebsd.org; Wed, 04 Jan 2006 06:51:19 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17339.64774.805229.732725@roam.psg.com> Date: Wed, 4 Jan 2006 06:51:18 -1000 To: FreeBSD Current Subject: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:05:29 -0000 *very* fresh cvsup, booting single to do installworld cores on boot [sorry, forgot trace] KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2006 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 7.0-CURRENT #23: Wed Jan 4 16:01:13 UTC 2006 root@work0.psg.com:/usr/obj/usr/src/sys/WORK0 Fatal trap 18: integer divide fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x20:0xc05e6295 stack pointer = 0x28:0xc0820d04 frame pointer = 0x28:0xc0820d14 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 = 0 () [thread pid 0 tid 0 ] Stopped at vm_coloring_init+0x35: idivl pq_cachenways,%eax db> trace Tracing pid 0 tid 0 td 0xc0692660 vm_coloring_init(3,c0820d60,c05e156a,c069d7a4,c065ad0e) at vm_coloring_init+0x35 vm_pageq_init(c069d7a4,c065ad0e,0,1,c04caf4b) at vm_pageq_init+0x9 vm_page_startup(c0c3d000,a,c0820d88,c049dbf5,0) at vm_page_startup+0x10a vm_mem_init(0,81e000,81ec00,81e000,0) at vm_mem_init+0x18 mi_startup() at mi_startup+0xb5 begin() at begin+0x2c From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:22:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C459A16A436 for ; Wed, 4 Jan 2006 17:22:28 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B73C43D5C for ; Wed, 4 Jan 2006 17:22:15 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k04HM9o7022777 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 09:22:10 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BC049E.2040301@errno.com> Date: Wed, 04 Jan 2006 09:23:42 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alexander Leidinger References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> <17339.4293.673806.446317@canoe.dclg.ca> <20060104115859.554eff0a@Magellan.Leidinger.net> In-Reply-To: <20060104115859.554eff0a@Magellan.Leidinger.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:22:29 -0000 Alexander Leidinger wrote: > On Tue, 3 Jan 2006 19:03:17 -0500 > David Gilbert wrote: > > >>>>>>>"Alexander" == Alexander Leidinger writes: >> >>[various problems with wi, deleted] >> >>Alexander> The problem is, that the wi driver isn't ported to the >>Alexander> current WLAN infrastructure. There's no documentation >>Alexander> available for the WLAN infrastructure, so you have to read >>Alexander> the source (the ath driver is the de-facto reference driver >>Alexander> for the WLAN stuff), search the net and if nothing helps, >>Alexander> ask sam@FreeBSD.org some well thought questions. >> >>I also thought that someone might have comments about a wi0 as an >>access point. This used to work, but all clients (even windoze) seem >>to loose association every 20 to 40 minutes (although the timing is >>random it seems). > > > I'm sure this is just another problem related to the outdated WLAN part > of wi. Sigh, I can't take any more of this nonsense. wi was one of the first drivers moved over to use net80211. It is not using "outdated WLAN" code. The problems with wi are almost entirely due to my being coerced into bringing updated net80211 code before all the drivers (other than ath) were ready. I did this because I was PROMISED (in person) that wi would be maintained and any problems fixed as they arose. That did not happen and ever since wi has languished. I have several wi cards and I test them each time I make changes to the net80211 layer to make sure there are no regressions but there are known outstanding problems that I am unlikely to work on. Find someone that cares and I will help them (as I've said numerous times). > > >>Alexander> If you have the time and energy to have a look at porting >>Alexander> the wi driver to (at least parts of) the current WLAN >>Alexander> framework, all wi users would appreciate some patches... >> >>Not that I'm afraid of development, but I'm unfamilliar with the >>difference between the revisions of acceptable wifi behaviour. > > > There are maybe 2 or 3 people in the FreeBSD world which are (at least > partly) familiar with it. And all of them aren't interested or don't > have time to take care of wi (or think the wi technology is outdated > and should RIP). There are many people capable of dealing with these issues but most are smart enough to recognize that there is little to be gained by hacking on a driver for hardware that is out of date and can be replaced for the price of a cheap dinner. > > So it comes down to "someone with interest in wi has to make himself > familiar with the WLAN infrastructure". I'm sure Sam will answer > questions if the person attacking the problem stumbles upon some > questions regarding the WLAN infrastructure part. Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:25:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 039F016A41F for ; Wed, 4 Jan 2006 17:25:39 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 59BB943D79 for ; Wed, 4 Jan 2006 17:25:28 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k04HPPo7022801 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Jan 2006 09:25:28 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BC0563.3050600@errno.com> Date: Wed, 04 Jan 2006 09:26:59 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dandee@volny.cz References: <001401c61124$5c5f4480$6508280a@tocnet28.jspoj.czf> In-Reply-To: <001401c61124$5c5f4480$6508280a@tocnet28.jspoj.czf> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:25:39 -0000 Daniel Dvorak wrote: >>-----Original Message----- >>From: owner-freebsd-current@freebsd.org >>[ > > mailto:owner-freebsd-current@freebsd.org] On Behalf Of David Gilbert > >>Sent: Wednesday, January 04, 2006 1:03 AM >>To: Alexander Leidinger >>Cc: freebsd-current@freebsd.org; David Gilbert >>Subject: Re: dhclient ignoring link on wi0 >> >> >>I also thought that someone might have comments about a wi0 >>as an access point. This used to work, but all clients (even >>windoze) seem to loose association every 20 to 40 minutes >>(although the timing is random it seems). >> >> >>Dave. > > > Not only this one, to make the picture complete. For example, another > relevant issue is: > > from rc.conf: > > ifconfig_wi1="inet w.x.y.z/m ssid A mediaopt hostap channel 4 up" > > reality ? > > # ifconfig wi1 > wi1: flags=8843 mtu 1500 > > media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps > ) > status: associated > > authmode OPEN privacy OFF txpowmax 100 dtimperiod 1 bintval 100 > > It has never reached more than DS/2Mbps in hostap mode. That is a firmware issue. OTOH there are patches floating around that bypass the firmware and select the tx rate in the host and which make operation better. > > ... and other issue is about transmit power limit, no chance to limit tx, > txpowmax does not work at all. Card transmits at full power. This is a firmware issue. Find a driver that supports changing the tx power and you will find a driver that works only for certain cards and certain revs of firmware. Feel free to supply patches for this; you can get them from the linux hostap driver for example. > > I know from my friend there exists some patch for the first issue, but CVS > does not contain it even in 7-CURRENT, let alone 6-STABLE. Becuase the person working on the patch received feedback that it did not work in all cases and has not had time to identify the issue. Sam From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:30:38 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD06916A41F; Wed, 4 Jan 2006 17:30:38 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (gw.zefyris.com [213.41.131.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7380E43D49; Wed, 4 Jan 2006 17:30:36 +0000 (GMT) (envelope-from ftigeot@aoi.wolfpond.org) Received: from aoi.wolfpond.org (localhost [127.0.0.1]) by aoi.wolfpond.org (8.13.4/8.13.4) with ESMTP id k04HUD22038234; Wed, 4 Jan 2006 18:30:13 +0100 (CET) (envelope-from ftigeot@aoi.wolfpond.org) Received: (from ftigeot@localhost) by aoi.wolfpond.org (8.13.4/8.13.1/Submit) id k04HUCxQ038233; Wed, 4 Jan 2006 18:30:12 +0100 (CET) (envelope-from ftigeot) Date: Wed, 4 Jan 2006 18:30:12 +0100 From: Francois Tigeot To: Bill Paul Message-ID: <20060104173012.GA38198@aoi.wolfpond.org> References: <00fb01c610ed$392fdf10$951fa8c0@venti> <20060104104521.463FA16A420@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060104104521.463FA16A420@hub.freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: "Brian K. White" , freebsd-current@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:30:38 -0000 On Wed, Jan 04, 2006 at 10:45:21AM +0000, Bill Paul wrote: > [Brian K. White] > > I _think_ on the latest ThinBSD, which is 5.4-release, and all later > > versions, that the touch pad pointer works but not the buttons. I may be > > misremembering but we don't have to guess once I try it again. > > Why didn't you try it again before writing this e-mail? Then your faulty > memory wouldn't be an issue. > > Also, what the heck is ThinBSD? It is a mfsroot based system used to create X11 or RDP terminals. It is entirely configured by dhcp. I am mainly to blame for its creation. Check it out here: http://www.thinbsd.org/ -- Francois Tigeot From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:34:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3B60C16A420 for ; Wed, 4 Jan 2006 17:34:31 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF1BF43D80 for ; Wed, 4 Jan 2006 17:34:17 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id AF04B11C63; Wed, 4 Jan 2006 12:34:16 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id 699831A07FA; Wed, 4 Jan 2006 12:34:10 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17340.1810.346416.267523@canoe.dclg.ca> Date: Wed, 4 Jan 2006 12:34:10 -0500 To: Sam Leffler In-Reply-To: <43BC049E.2040301@errno.com> References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> <17339.4293.673806.446317@canoe.dclg.ca> <20060104115859.554eff0a@Magellan.Leidinger.net> <43BC049E.2040301@errno.com> X-Mailer: VM 7.17 under 21.4 (patch 18) "Social Property" XEmacs Lucid Cc: Alexander Leidinger , freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:34:31 -0000 >>>>> "Sam" == Sam Leffler writes: Sam> There are many people capable of dealing with these issues but Sam> most are smart enough to recognize that there is little to be Sam> gained by hacking on a driver for hardware that is out of date Sam> and can be replaced for the price of a cheap dinner. Well I care. People are still producing prism based high power router cards (400 mW and better). I was looking at some today. To be a serious router OS, I see wi support as important for a few more years. Also ... do to spotty support, buying a new card for FreeBSD is difficult. While I might pay only $50 or so for a new card, finding a compatible one is difficult (mostly due to vendor sillyness). Neither has ATH been good to me. I was an early ATH adopter --- I still have an early ATH mini-pci in my laptop. Lately I havn't been able to figure out how to give it an encryption key ... the ifconfig (in 6.0-STABLE) refuses. It's always had some sort of bug that dropps the odd packet. I've never really figured it out ... I just run local web proxies. I'm somewhat happy to have an intel a/b/g card arriving with my new laptop. Anyways... I'm game. I have a test system (I'll have to find a disk for it) and I have a PCI prism. I also have severl pccard prisms to test with, should that be required. While I don't have fancy new hardware to play with, I have a goodly collection of old hardware. Anyone have some notes before I dive in? Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:35:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43AB216A41F for ; Wed, 4 Jan 2006 17:35:20 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09E5243D7C for ; Wed, 4 Jan 2006 17:35:15 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k04HWkSm010670; Wed, 4 Jan 2006 10:32:51 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 04 Jan 2006 10:33:01 -0700 (MST) Message-Id: <20060104.103301.123400258.imp@bsdimp.com> To: pbowen@fastmail.fm From: "M. Warner Losh" In-Reply-To: <43BB0455.80508@fastmail.fm> References: <20060101.212552.85411680.imp@bsdimp.com> <20060102.214956.40574756.imp@bsdimp.com> <43BB0455.80508@fastmail.fm> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 04 Jan 2006 10:32:51 -0700 (MST) Cc: freebsd-current@freebsd.org Subject: Re: Kernel panics when Atheros card plugged in. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:35:20 -0000 In message: <43BB0455.80508@fastmail.fm> Patrick Bowen writes: : BTW; what does "BAR" stand for? Base Address Register. These are the registers that determine which address range the PCI device will respond to. If they are incorrectly programmed, then the driver will access resources that the device hasn't been setup to respond to. Warner From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:42:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8847B16A420 for ; Wed, 4 Jan 2006 17:42:16 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121CA43D55 for ; Wed, 4 Jan 2006 17:42:00 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04HbtHr093134; Wed, 4 Jan 2006 18:37:56 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04HfrFP002162; Wed, 4 Jan 2006 18:41:53 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 18:41:53 +0100 From: Alexander Leidinger To: freebsd-current@freebsd.org, Randy Bush Message-ID: <20060104184153.5c59b660@Magellan.Leidinger.net> In-Reply-To: <17339.64774.805229.732725@roam.psg.com> References: <17339.64774.805229.732725@roam.psg.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_=79SENEVCH4jU19D5By2jWc" X-Virus-Scanned: by amavisd-new Cc: Subject: Re: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:42:16 -0000 --MP_=79SENEVCH4jU19D5By2jWc Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, 4 Jan 2006 06:51:18 -1000 Randy Bush wrote: > Fatal trap 18: integer divide fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xc05e6295 > stack pointer = 0x28:0xc0820d04 > frame pointer = 0x28:0xc0820d14 > 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 = 0 () > [thread pid 0 tid 0 ] > Stopped at vm_coloring_init+0x35: idivl pq_cachenways,%eax > db> trace > Tracing pid 0 tid 0 td 0xc0692660 > vm_coloring_init(3,c0820d60,c05e156a,c069d7a4,c065ad0e) at vm_coloring_init+0x35 > vm_pageq_init(c069d7a4,c065ad0e,0,1,c04caf4b) at vm_pageq_init+0x9 > vm_page_startup(c0c3d000,a,c0820d88,c049dbf5,0) at vm_page_startup+0x10a > vm_mem_init(0,81e000,81ec00,81e000,0) at vm_mem_init+0x18 > mi_startup() at mi_startup+0xb5 > begin() at begin+0x2c Uhm... this looks like my fault... Can you please try the attached diff and report back if it works? If it doesn't work I need more debugging output: - the content of pq_cachesize and pq_cachenways - the line where it's panicing Bye, Alexander. -- Where do you think you're going today? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ --MP_=79SENEVCH4jU19D5By2jWc Content-Type: text/plain; name=vm.diff Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename=vm.diff Index: sys/vm/vm_pageq.c =================================================================== RCS file: /big/FreeBSD-CVS/src/sys/vm/vm_pageq.c,v retrieving revision 1.19 diff -u -u -r1.19 vm_pageq.c --- sys/vm/vm_pageq.c 31 Dec 2005 14:39:20 -0000 1.19 +++ sys/vm/vm_pageq.c 4 Jan 2006 17:39:09 -0000 @@ -79,7 +79,7 @@ setPQL2(&pq_cachesize, &pq_cachenways); - if (pq_cachesize > 0) + if (pq_cachesize > 0 && pq_cachenways > 0 && PAGE_SIZE > 1024) PQ_NUMCOLORS = pq_cachesize / (PAGE_SIZE/1024) / \ pq_cachenways; else --MP_=79SENEVCH4jU19D5By2jWc-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:45:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 963C116A420 for ; Wed, 4 Jan 2006 17:45:33 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0450043D8D for ; Wed, 4 Jan 2006 17:45:26 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuChR-000Ji2-AZ; Wed, 04 Jan 2006 17:45:25 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuChQ-000D3R-95; Wed, 04 Jan 2006 07:45:24 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17340.2483.773739.624104@roam.psg.com> Date: Wed, 4 Jan 2006 07:45:23 -1000 To: Alexander Leidinger References: <17339.64774.805229.732725@roam.psg.com> <20060104184153.5c59b660@Magellan.Leidinger.net> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:45:33 -0000 > Uhm... this looks like my fault... > > Can you please try the attached diff and report back if it works? patched and building now randy From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:48:34 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFD3F16A41F for ; Wed, 4 Jan 2006 17:48:34 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1670043DA3 for ; Wed, 4 Jan 2006 17:48:25 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04HiF4s093170; Wed, 4 Jan 2006 18:44:16 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04HmCnX003275; Wed, 4 Jan 2006 18:48:13 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 18:48:12 +0100 From: Alexander Leidinger To: Sam Leffler Message-ID: <20060104184812.442c37af@Magellan.Leidinger.net> In-Reply-To: <43BC049E.2040301@errno.com> References: <17337.50303.811554.900031@canoe.dclg.ca> <43B9C7F1.5030303@cs.unisa.edu.au> <20060104005134.k60dxcrrcw0c40kk@netchild.homeip.net> <17339.4293.673806.446317@canoe.dclg.ca> <20060104115859.554eff0a@Magellan.Leidinger.net> <43BC049E.2040301@errno.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, David Gilbert Subject: Re: dhclient ignoring link on wi0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:48:34 -0000 On Wed, 04 Jan 2006 09:23:42 -0800 Sam Leffler wrote: > Sigh, I can't take any more of this nonsense. wi was one of the first > drivers moved over to use net80211. It is not using "outdated WLAN" > code. The problems with wi are almost entirely due to my being coerced > into bringing updated net80211 code before all the drivers (other than > ath) were ready. I did this because I was PROMISED (in person) that wi > would be maintained and any problems fixed as they arose. That did not > happen and ever since wi has languished. I have several wi cards and I > test them each time I make changes to the net80211 layer to make sure > there are no regressions but there are known outstanding problems that I > am unlikely to work on. Find someone that cares and I will help them > (as I've said numerous times). I may have used the wrong words to describe the problem. I didn't meant to say that the bits from the WLAN framework the wi driver uses are outdated. What I meant was, that the wi driver isn't up-to-date how it uses the WLAN framework code. So the wi driver is "outdated" in this regard, not the net80211 code. Sorry for not finding the right words earlier, and thanks for explaining the issue in a better way. 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 = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 17:59:11 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 40A9316A41F for ; Wed, 4 Jan 2006 17:59:11 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8104543D5F for ; Wed, 4 Jan 2006 17:59:01 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuCuZ-000K3B-6k; Wed, 04 Jan 2006 17:58:59 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EuCuX-000D4o-Ph; Wed, 04 Jan 2006 07:58:57 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17340.3297.187368.120900@roam.psg.com> Date: Wed, 4 Jan 2006 07:58:57 -1000 To: Alexander Leidinger References: <17339.64774.805229.732725@roam.psg.com> <20060104184153.5c59b660@Magellan.Leidinger.net> Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 17:59:11 -0000 > Index: sys/vm/vm_pageq.c > =================================================================== > RCS file: /big/FreeBSD-CVS/src/sys/vm/vm_pageq.c,v > retrieving revision 1.19 > diff -u -u -r1.19 vm_pageq.c > --- sys/vm/vm_pageq.c 31 Dec 2005 14:39:20 -0000 1.19 > +++ sys/vm/vm_pageq.c 4 Jan 2006 17:39:09 -0000 > @@ -79,7 +79,7 @@ > > setPQL2(&pq_cachesize, &pq_cachenways); > > - if (pq_cachesize > 0) > + if (pq_cachesize > 0 && pq_cachenways > 0 && PAGE_SIZE > 1024) > PQ_NUMCOLORS = pq_cachesize / (PAGE_SIZE/1024) / \ > pq_cachenways; > else worked! mahalo, randy From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 18:17:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6D6616A41F; Wed, 4 Jan 2006 18:17:39 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6413143D46; Wed, 4 Jan 2006 18:17:39 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k04IG2i08272; Wed, 4 Jan 2006 10:16:02 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k04IG2Ta001457; Wed, 4 Jan 2006 10:16:02 -0800 (PST) (envelope-from faber) Date: Wed, 4 Jan 2006 10:16:02 -0800 From: Ted Faber To: John Baldwin Message-ID: <20060104181602.GA1371@hut.isi.edu> References: <20060103233406.GA1564@hut.isi.edu> <200601040836.29244.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lCAWRPmW1mITcIfM" Content-Disposition: inline In-Reply-To: <200601040836.29244.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 18:17:40 -0000 --lCAWRPmW1mITcIfM Content-Type: multipart/mixed; boundary="tjCHc7DPkfUGtrlw" Content-Disposition: inline --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 04, 2006 at 08:36:28AM -0500, John Baldwin wrote: > On Tuesday 03 January 2006 06:34 pm, Ted Faber wrote: > > On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 > > package against the new source, my Xserver won't allocate many video > > modes because it can't open /dev/agpgart to allocate memory. The video > > card is an Intel I810 - 865G chipset. > > > > On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide > > appears (which seems to be hinted at in the comments to the most recent > > change to /sys/pci/agp_i810.c from the CVS tree). I've attached a > > verbose dmesg from the kernel recent -CURRENT kernel. > > > > Anyone else having a similar problem or know what I'm doing wrong? I'm > > happy to test patches or provide more info. >=20 > vgapci doesn't create a /dev entry, but it did probe. Can you get devinf= o -v=20 > output? Sure thing. It's attached. vgapci seems to attach to something, but I'm not entirely sure how to read the output. It's attached. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --tjCHc7DPkfUGtrlw Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=devinfo nexus0 legacy0 npx0 acpi0 cpu0 pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU0 unknown pnpinfo _HID=none _UID=0 at handle=\_PR_.CPU1 acpi_button0 pnpinfo _HID=PNP0C0C _UID=0 at handle=\_SB_.VBTN acpi_sysresource0 pnpinfo _HID=PNP0C01 _UID=1 at handle=\_SB_.MEM_ pcib0 pnpinfo _HID=PNP0A03 _UID=4 at handle=\_SB_.PCI0 pci0 hostb0 pnpinfo vendor=0x8086 device=0x2570 subvendor=0x1028 subdevice=0x019d class=0x060000 at slot=0 function=0 vgapci0 pnpinfo vendor=0x8086 device=0x2572 subvendor=0x1028 subdevice=0x019d class=0x030000 at slot=2 function=0 drm0 uhci0 pnpinfo vendor=0x8086 device=0x24d2 subvendor=0x1028 subdevice=0x019d class=0x0c0300 at slot=29 function=0 handle=\_SB_.PCI0.USB0 usb0 uhub0 ums0 pnpinfo vendor=0x046d product=0xc401 devclass=0x00 devsubclass=0x00 release=0x0210 sernum="" intclass=0x03 intsubclass=0x01 at port=0 interface=0 ukbd0 pnpinfo vendor=0x413c product=0x2005 devclass=0x00 devsubclass=0x00 release=0x0104 sernum="" intclass=0x03 intsubclass=0x01 at port=1 interface=0 uhci1 pnpinfo vendor=0x8086 device=0x24d4 subvendor=0x1028 subdevice=0x019d class=0x0c0300 at slot=29 function=1 handle=\_SB_.PCI0.USB1 usb1 uhub1 uhci2 pnpinfo vendor=0x8086 device=0x24de subvendor=0x1028 subdevice=0x019d class=0x0c0300 at slot=29 function=3 handle=\_SB_.PCI0.USB3 usb2 uhub2 ehci0 pnpinfo vendor=0x8086 device=0x24dd subvendor=0x1028 subdevice=0x019d class=0x0c0320 at slot=29 function=7 usb3 uhub3 uhub4 pnpinfo vendor=0x0424 product=0x2504 devclass=0x09 devsubclass=0x00 release=0x0000 sernum="" at port=2 pcib1 pnpinfo vendor=0x8086 device=0x244e subvendor=0x0000 subdevice=0x0000 class=0x060400 at slot=30 function=0 handle=\_SB_.PCI0.PCI1 pci1 fxp0 pnpinfo vendor=0x8086 device=0x1050 subvendor=0x1028 subdevice=0x019d class=0x020000 at slot=8 function=0 miibus0 inphy0 pnpinfo oui=0xaa00 model=0x33 rev=0x0 at phyno=1 isab0 pnpinfo vendor=0x8086 device=0x24d0 subvendor=0x0000 subdevice=0x0000 class=0x060100 at slot=31 function=0 handle=\_SB_.PCI0.ISA_ isa0 pmtimer0 sc0 vga0 adv0 aha0 aic0 atkbdc0 atkbd0 psm0 bt0 cs0 ed0 fdc0 fe0 ie0 lnc0 sio1 sio2 sio3 sn0 vt0 orm0 pnpinfo pnpid=ORM0000 atapci0 pnpinfo vendor=0x8086 device=0x24db subvendor=0x1028 subdevice=0x019d class=0x01018a at slot=31 function=1 ata0 ad0 subdisk0 ata1 acd0 unknown pnpinfo vendor=0x8086 device=0x24d3 subvendor=0x1028 subdevice=0x019d class=0x0c0500 at slot=31 function=3 pcm0 pnpinfo vendor=0x8086 device=0x24d5 subvendor=0x1028 subdevice=0x019d class=0x040100 at slot=31 function=5 unknown pnpinfo _HID=none _UID=20 at handle=\_SB_.PCI0.USB2 atdma0 pnpinfo _HID=PNP0200 _UID=0 at handle=\_SB_.PCI0.ISA_.DMA_ npxisa0 pnpinfo _HID=PNP0C04 _UID=0 at handle=\_SB_.PCI0.ISA_.FPU_ atpic0 pnpinfo _HID=PNP0000 _UID=0 at handle=\_SB_.PCI0.ISA_.PIC_ unknown pnpinfo _HID=PNP0800 _UID=0 at handle=\_SB_.PCI0.ISA_.SPK_ attimer0 pnpinfo _HID=PNP0B00 _UID=0 at handle=\_SB_.PCI0.ISA_.RTC_ attimer1 pnpinfo _HID=PNP0100 _UID=0 at handle=\_SB_.PCI0.ISA_.TMR_ unknown pnpinfo _HID=PNP0700 _UID=0 at handle=\_SB_.PCI0.ISA_.FDC_ unknown pnpinfo _HID=PNP0303 _UID=0 at handle=\_SB_.PCI0.ISA_.KBD_ unknown pnpinfo _HID=PNP0F13 _UID=0 at handle=\_SB_.PCI0.ISA_.MOU_ sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.ISA_.COMA ppc0 pnpinfo _HID=PNP0401 _UID=0 at handle=\_SB_.PCI0.ISA_.PRT_ ppbus0 lpt0 ppi0 acpi_sysresource1 pnpinfo _HID=PNP0C01 _UID=11 at handle=\_SB_.PCI0.ISA_.MBIO pci_link0 pnpinfo _HID=PNP0C0F _UID=12 at handle=\_SB_.LNKA pci_link1 pnpinfo _HID=PNP0C0F _UID=13 at handle=\_SB_.LNKB pci_link2 pnpinfo _HID=PNP0C0F _UID=14 at handle=\_SB_.LNKC pci_link3 pnpinfo _HID=PNP0C0F _UID=15 at handle=\_SB_.LNKD pci_link4 pnpinfo _HID=PNP0C0F _UID=16 at handle=\_SB_.LNKE pci_link5 pnpinfo _HID=PNP0C0F _UID=17 at handle=\_SB_.LNKF pci_link6 pnpinfo _HID=PNP0C0F _UID=18 at handle=\_SB_.LNKG pci_link7 pnpinfo _HID=PNP0C0F _UID=19 at handle=\_SB_.LNKH acpi_timer0 pnpinfo unknown at unknown --tjCHc7DPkfUGtrlw-- --lCAWRPmW1mITcIfM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvBDiaUz3f+Zf+XsRAsilAJ448j7qCC50kCmhy5blE+F3a/pmUgCg454E VifitkanQyznI+PhcQxV960= =pMCN -----END PGP SIGNATURE----- --lCAWRPmW1mITcIfM-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 18:27:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DA03C16A41F for ; Wed, 4 Jan 2006 18:27:30 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01FE243D5E for ; Wed, 4 Jan 2006 18:27:29 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D07C.dip.t-dialin.net [84.165.208.124]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k04INSMu093327; Wed, 4 Jan 2006 19:23:28 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k04IRPI6010531; Wed, 4 Jan 2006 19:27:26 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Wed, 4 Jan 2006 19:27:25 +0100 From: Alexander Leidinger To: Randy Bush Message-ID: <20060104192725.65dcccf2@Magellan.Leidinger.net> In-Reply-To: <17340.3297.187368.120900@roam.psg.com> References: <17339.64774.805229.732725@roam.psg.com> <20060104184153.5c59b660@Magellan.Leidinger.net> <17340.3297.187368.120900@roam.psg.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org Subject: Re: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 18:27:31 -0000 On Wed, 4 Jan 2006 07:58:57 -1000 Randy Bush wrote: > worked! Committed. Thanks, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 18:31:41 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6372A16A41F for ; Wed, 4 Jan 2006 18:31:41 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F5B843D49 for ; Wed, 4 Jan 2006 18:31:40 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5278730 for multiple; Wed, 04 Jan 2006 13:33:01 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04IVUct004504; Wed, 4 Jan 2006 13:31:33 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 4 Jan 2006 13:32:13 -0500 User-Agent: KMail/1.8.2 References: <17339.64774.805229.732725@roam.psg.com> <20060104184153.5c59b660@Magellan.Leidinger.net> In-Reply-To: <20060104184153.5c59b660@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041332.14788.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Randy Bush , Alexander Leidinger Subject: Re: Fatal trap 18: integer divide fault while in kernel mode X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 18:31:41 -0000 On Wednesday 04 January 2006 12:41 pm, Alexander Leidinger wrote: > On Wed, 4 Jan 2006 06:51:18 -1000 > > Randy Bush wrote: > > Fatal trap 18: integer divide fault while in kernel mode > > cpuid = 0; apic id = 00 > > instruction pointer = 0x20:0xc05e6295 > > stack pointer = 0x28:0xc0820d04 > > frame pointer = 0x28:0xc0820d14 > > 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 = 0 () > > [thread pid 0 tid 0 ] > > Stopped at vm_coloring_init+0x35: idivl pq_cachenways,%eax > > db> trace > > Tracing pid 0 tid 0 td 0xc0692660 > > vm_coloring_init(3,c0820d60,c05e156a,c069d7a4,c065ad0e) at > > vm_coloring_init+0x35 vm_pageq_init(c069d7a4,c065ad0e,0,1,c04caf4b) at > > vm_pageq_init+0x9 vm_page_startup(c0c3d000,a,c0820d88,c049dbf5,0) at > > vm_page_startup+0x10a vm_mem_init(0,81e000,81ec00,81e000,0) at > > vm_mem_init+0x18 > > mi_startup() at mi_startup+0xb5 > > begin() at begin+0x2c > > Uhm... this looks like my fault... > > Can you please try the attached diff and report back if it works? > > If it doesn't work I need more debugging output: > - the content of pq_cachesize and pq_cachenways > - the line where it's panicing You should probably CTASSERT(PAGE_SIZE/1024 > 0). That should probably never be false. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 19:09:37 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1CD2D16A41F for ; Wed, 4 Jan 2006 19:09:37 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 008E443D49 for ; Wed, 4 Jan 2006 19:09:33 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5281002 for multiple; Wed, 04 Jan 2006 14:10:44 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04J9HV4004706; Wed, 4 Jan 2006 14:09:18 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ted Faber Date: Wed, 4 Jan 2006 14:08:27 -0500 User-Agent: KMail/1.8.2 References: <20060103233406.GA1564@hut.isi.edu> <200601040836.29244.jhb@freebsd.org> <20060104181602.GA1371@hut.isi.edu> In-Reply-To: <20060104181602.GA1371@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041408.28753.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 19:09:37 -0000 On Wednesday 04 January 2006 01:16 pm, Ted Faber wrote: > On Wed, Jan 04, 2006 at 08:36:28AM -0500, John Baldwin wrote: > > On Tuesday 03 January 2006 06:34 pm, Ted Faber wrote: > > > On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 > > > package against the new source, my Xserver won't allocate many video > > > modes because it can't open /dev/agpgart to allocate memory. The video > > > card is an Intel I810 - 865G chipset. > > > > > > On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide > > > appears (which seems to be hinted at in the comments to the most recent > > > change to /sys/pci/agp_i810.c from the CVS tree). I've attached a > > > verbose dmesg from the kernel recent -CURRENT kernel. > > > > > > Anyone else having a similar problem or know what I'm doing wrong? I'm > > > happy to test patches or provide more info. > > > > vgapci doesn't create a /dev entry, but it did probe. Can you get > > devinfo -v output? > > Sure thing. It's attached. vgapci seems to attach to something, but > I'm not entirely sure how to read the output. It's attached. Odd, it seems you don't have any AGP devices. The 865G isn't a PCI-e chipset, so you should have them. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 19:20:56 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF89416A41F for ; Wed, 4 Jan 2006 19:20:56 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B67B443D5D for ; Wed, 4 Jan 2006 19:20:55 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id k04JKtPx070061 for ; Wed, 4 Jan 2006 11:20:55 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id k04JKtEH070060 for freebsd-current@freebsd.org; Wed, 4 Jan 2006 11:20:55 -0800 (PST) (envelope-from sgk) Date: Wed, 4 Jan 2006 11:20:55 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20060104192055.GA70045@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: buildkernel is broken! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 19:20:56 -0000 Fresh source from 10 minutes ago. MAKE=/usr/obj/mnt1/src/make.amd64/make sh /mnt1/src/sys/conf/newvers.sh SPEW cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=opteron -Wall -Wr edundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoin ter-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- - I. -I/mnt1/src/sys -I/mnt1/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_H EADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit -growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mcmodel =kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -mso ft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror vers.c linking kernel.debug ld: kern_malloc.o(.debug_frame+0x264): reloc against `.debug_frame': error 2 *** Error code 1 Stop in /mnt1/obj/mnt1/src/sys/SPEW. *** Error code 1 Stop in /mnt1/src. *** Error code 1 -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 19:22:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1904716A41F; Wed, 4 Jan 2006 19:22:16 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97D9043D4C; Wed, 4 Jan 2006 19:22:15 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k04JKYi00790; Wed, 4 Jan 2006 11:20:34 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k04JKYmV003057; Wed, 4 Jan 2006 11:20:34 -0800 (PST) (envelope-from faber) Date: Wed, 4 Jan 2006 11:20:34 -0800 From: Ted Faber To: John Baldwin Message-ID: <20060104192034.GH1371@hut.isi.edu> References: <20060103233406.GA1564@hut.isi.edu> <200601040836.29244.jhb@freebsd.org> <20060104181602.GA1371@hut.isi.edu> <200601041408.28753.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="64LDleNqNegJ4g97" Content-Disposition: inline In-Reply-To: <200601041408.28753.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 19:22:16 -0000 --64LDleNqNegJ4g97 Content-Type: multipart/mixed; boundary="u3W6riq+uV6J42Ub" Content-Disposition: inline --u3W6riq+uV6J42Ub Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 04, 2006 at 02:08:27PM -0500, John Baldwin wrote: > Odd, it seems you don't have any AGP devices. The 865G isn't a PCI-e > chipset, so you should have them. Yeah, my X server seems upset about it, all right. Am I not loading a module or device in my kernel config? (attached) The config that's attached has been working for a while, and I didn't see anything in /usr/src/UPDATING that told me to change anything. Of course, if I've been doing something wrong and getting away with it for a while, that's to be expected. The change between 1.33 and 1.34 to /sys/pci/agp_i810.c seems to delete some code that added a device for the drm, but that's just me reading a comment from http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_i810.c.diff?r1=3D1.33= &r2=3D1.34&f=3Dh I haven't really gone digging. Any suggestions? --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --u3W6riq+uV6J42Ub Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=HUT # # HUT -- 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/doc/en_US.ISO8859-1/books/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 ../../conf/NOTES and NOTES files. # 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.433 2005/10/27 17:34:35 jhb Exp $ machine i386 cpu I686_CPU ident HUT # 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 SCHED_ULE # ULE scheduler options SCHED_4BSD # 4BSD scheduler options PREEMPTION # Enable kernel thread preemption options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories options MD_ROOT # MD is a potential root device options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 options COMPAT_FREEBSD5 # Compatible with FreeBSD5 options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options ADAPTIVE_GIANT # Giant mutex is adaptive. # Debugging for use in -current options KDB # Enable kernel debugger support. options DDB # Support DDB. # To make an SMP kernel, the next two lines are needed options SMP # Symmetric MultiProcessor Kernel device apic # I/O APIC # Bus support. device eisa device pci # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Add suspend/resume support for the i8254. device pmtimer # 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 # 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 fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices. device loop # Network loopback device random # Entropy device device ether # Ethernet support device sl # Kernel SLIP device ppp # Kernel PPP device tun # Packet tunnel. device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" device gif # IPv6 and IPv4 tunneling device faith # IPv6-to-IPv4 relaying (translation) # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! # Note that 'bpf' is required for DHCP. device bpf # Berkeley packet filter # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # EHCI PCI->USB interface (USB 2.0) device usb # USB Bus (required) 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 --u3W6riq+uV6J42Ub-- --64LDleNqNegJ4g97 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvCACaUz3f+Zf+XsRAjJrAKDdrvDQmeihD/ZXZsXtx2xo3jrIUQCg3QXU lbWd/aF8yTaJb3wtB9G3sV8= =IKKv -----END PGP SIGNATURE----- --64LDleNqNegJ4g97-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 19:59:00 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0610416A41F for ; Wed, 4 Jan 2006 19:59:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6EAE43D77 for ; Wed, 4 Jan 2006 19:58:44 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5284304 for multiple; Wed, 04 Jan 2006 14:59:58 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04JwU0Y005038; Wed, 4 Jan 2006 14:58:30 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ted Faber Date: Wed, 4 Jan 2006 14:58:22 -0500 User-Agent: KMail/1.8.2 References: <20060103233406.GA1564@hut.isi.edu> <200601041408.28753.jhb@freebsd.org> <20060104192034.GH1371@hut.isi.edu> In-Reply-To: <20060104192034.GH1371@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041458.23129.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 19:59:00 -0000 On Wednesday 04 January 2006 02:20 pm, Ted Faber wrote: > On Wed, Jan 04, 2006 at 02:08:27PM -0500, John Baldwin wrote: > > Odd, it seems you don't have any AGP devices. The 865G isn't a PCI-e > > chipset, so you should have them. > > Yeah, my X server seems upset about it, all right. > > Am I not loading a module or device in my kernel config? (attached) > The config that's attached has been working for a while, and I didn't > see anything in /usr/src/UPDATING that told me to change anything. Of > course, if I've been doing something wrong and getting away with it for > a while, that's to be expected. > > The change between 1.33 and 1.34 to /sys/pci/agp_i810.c seems to delete > some code that added a device for the drm, but that's just me reading a > comment from > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_i810.c.diff?r1=1.33&r >2=1.34&f=h I haven't really gone digging. > > Any suggestions? For i915 systems some people have hacked vga_pci.c to always add an "agp" child device rather than doing it conditionally, but that I wouldn't expect non-PCI-e chipsets to have the same issue. Do you have AGP enabled in your BIOS? -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 21:26:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E8A716A41F; Wed, 4 Jan 2006 21:26:50 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 995C243D77; Wed, 4 Jan 2006 21:26:44 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k04LQOi12587; Wed, 4 Jan 2006 13:26:24 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k04LQNjd001115; Wed, 4 Jan 2006 13:26:23 -0800 (PST) (envelope-from faber) Date: Wed, 4 Jan 2006 13:26:23 -0800 From: Ted Faber To: John Baldwin Message-ID: <20060104212623.GA1002@hut.isi.edu> References: <20060103233406.GA1564@hut.isi.edu> <200601041408.28753.jhb@freebsd.org> <20060104192034.GH1371@hut.isi.edu> <200601041458.23129.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jho1yZJdad60DJr+" Content-Disposition: inline In-Reply-To: <200601041458.23129.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 21:26:50 -0000 --jho1yZJdad60DJr+ Content-Type: multipart/mixed; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 04, 2006 at 02:58:22PM -0500, John Baldwin wrote: > On Wednesday 04 January 2006 02:20 pm, Ted Faber wrote: > > On Wed, Jan 04, 2006 at 02:08:27PM -0500, John Baldwin wrote: > > > Odd, it seems you don't have any AGP devices. The 865G isn't a PCI-e > > > chipset, so you should have them. > > > > Yeah, my X server seems upset about it, all right. > > > > Am I not loading a module or device in my kernel config? (attached) > > The config that's attached has been working for a while, and I didn't > > see anything in /usr/src/UPDATING that told me to change anything. Of > > course, if I've been doing something wrong and getting away with it for > > a while, that's to be expected. > > > > The change between 1.33 and 1.34 to /sys/pci/agp_i810.c seems to delete > > some code that added a device for the drm, but that's just me reading a > > comment from > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_i810.c.diff?r1=3D= 1.33&r > >2=3D1.34&f=3Dh I haven't really gone digging. > > > > Any suggestions? >=20 > For i915 systems some people have hacked vga_pci.c to always add an "agp"= =20 > child device rather than doing it conditionally, but that I wouldn't expe= ct=20 > non-PCI-e chipsets to have the same issue. Do you have AGP enabled in yo= ur=20 > BIOS? As far as I can tell. The BIOS setup didn't have a particular AGP on/off entry, but all the entries seemed reasonable to me and are the factory defaults. The box is a Dell Dimension 3000 if that helps. I'm currently running a -CURRENT kernel from Mon Dec 19 11:21:13 PST and it properly detects the AGP, the /dev/agppart device appears, and the X server is fine. I'm assuming that means AGP is enabled in my BIOS. If that's a bad assumption, do you know how I can test it? In case it helps, I've included a dmesg from the Dec 19 kernel. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Copyright (c) 1992-2005 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 7.0-CURRENT #5: Mon Dec 19 11:21:13 PST 2005 root@hut.isi.edu:/usr/obj/usr/src/sys/HUT link_elf: symbol pci_find_extcap_desc undefined KLD file acpi.ko - could not finalize loading MPTable: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf41 Stepping = 1 Features=0xbfebfbff Features2=0x441d> real memory = 1072103424 (1022 MB) avail memory = 1044172800 (995 MB) ioapic0: Changing APIC ID to 1 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0xed98-0xed9f mem 0xe8000000-0xefffffff,0xfeb80000-0xfebfffff irq 16 at device 2.0 on pci0 agp0: detected 892k stolen memory agp0: aperture size is 128M uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb3: EHCI version 1.0 usb3: wrong number of companions (4 != 3) usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 8 ports with 8 removable, self powered uhub4: vendor 0x0424 product 0x2504, class 9/0, rev 2.00/0.00, addr 2 uhub4: multiple transaction translators uhub4: 4 ports with 4 removable, self powered pcib1: at device 30.0 on pci0 pci1: on pcib1 fxp0: port 0xdf40-0xdf7f mem 0xfeaff000-0xfeafffff irq 20 at device 8.0 on pci1 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:13:20:69:97:0e isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xfeb7fc00-0xfeb7ffff irq 18 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0xee00-0xeeff,0xedc0-0xedff mem 0xfeb7fa00-0xfeb7fbff,0xfeb7f900-0xfeb7f9ff irq 17 at device 31.5 on pci0 pcm0: primary codec not ready! pcm0: pmtimer0 on isa0 orm0: at iomem 0xc0000-0xca7ff,0xca800-0xcbfff pnpid ORM0000 on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) ums0: Logitech USB-PS/2 Trackball, rev 1.00/2.10, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. ukbd0: DELL DELL USB Keyboard, rev 1.10/1.04, addr 3, iclass 3/1 kbd1 at ukbd0 Timecounter "TSC" frequency 2793013650 Hz quality 800 Timecounters tick every 1.000 msec ad0: 76293MB at ata0-master UDMA100 acd0: DVDR at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled link_elf: symbol pci_find_extcap_desc undefined KLD i915.ko: depends on drm - not available --OgqxwSJOaUobr8KG-- --jho1yZJdad60DJr+ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvD1/aUz3f+Zf+XsRAkC/AJ9oOgPMofxg9gWhs+zs6goO7cdn6wCeK66V 7eWNkktdiPtpPp7qdtujbBw= =Ykx6 -----END PGP SIGNATURE----- --jho1yZJdad60DJr+-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 21:59:58 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A13416A41F for ; Wed, 4 Jan 2006 21:59:58 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8992843D5E for ; Wed, 4 Jan 2006 21:59:52 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5293011 for multiple; Wed, 04 Jan 2006 17:00:55 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k04LxP65005632; Wed, 4 Jan 2006 16:59:28 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ted Faber Date: Wed, 4 Jan 2006 17:00:13 -0500 User-Agent: KMail/1.8.2 References: <20060103233406.GA1564@hut.isi.edu> <200601041458.23129.jhb@freebsd.org> <20060104212623.GA1002@hut.isi.edu> In-Reply-To: <20060104212623.GA1002@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601041700.14244.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1229/Wed Jan 4 10:08:11 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 21:59:58 -0000 On Wednesday 04 January 2006 04:26 pm, Ted Faber wrote: > On Wed, Jan 04, 2006 at 02:58:22PM -0500, John Baldwin wrote: > > On Wednesday 04 January 2006 02:20 pm, Ted Faber wrote: > > > On Wed, Jan 04, 2006 at 02:08:27PM -0500, John Baldwin wrote: > > > > Odd, it seems you don't have any AGP devices. The 865G isn't a PCI-e > > > > chipset, so you should have them. > > > > > > Yeah, my X server seems upset about it, all right. > > > > > > Am I not loading a module or device in my kernel config? (attached) > > > The config that's attached has been working for a while, and I didn't > > > see anything in /usr/src/UPDATING that told me to change anything. Of > > > course, if I've been doing something wrong and getting away with it for > > > a while, that's to be expected. > > > > > > The change between 1.33 and 1.34 to /sys/pci/agp_i810.c seems to delete > > > some code that added a device for the drm, but that's just me reading a > > > comment from > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/pci/agp_i810.c.diff?r1=1. > > >33&r 2=1.34&f=h I haven't really gone digging. > > > > > > Any suggestions? > > > > For i915 systems some people have hacked vga_pci.c to always add an "agp" > > child device rather than doing it conditionally, but that I wouldn't > > expect non-PCI-e chipsets to have the same issue. Do you have AGP > > enabled in your BIOS? > > As far as I can tell. The BIOS setup didn't have a particular AGP > on/off entry, but all the entries seemed reasonable to me and are the > factory defaults. The box is a Dell Dimension 3000 if that helps. > > I'm currently running a -CURRENT kernel from Mon Dec 19 11:21:13 PST and > it properly detects the AGP, the /dev/agppart device appears, and the X > server is fine. I'm assuming that means AGP is enabled in my BIOS. If > that's a bad assumption, do you know how I can test it? > > In case it helps, I've included a dmesg from the Dec 19 kernel. Ok, use the workaround other folks have posted for now. Hack vga_pci.c to always add the "agp" device in its attach routine instead of checking for PCIY_AGP. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 22:04:17 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id C903616A420; Wed, 4 Jan 2006 22:04:17 +0000 (GMT) In-Reply-To: <98dd087e0601041155y4ee8a125v@mail.gmail.com> from Dalius Dobravolskas at "Jan 4, 2006 09:55:51 pm" To: dalius.dobravolskas@gmail.com (Dalius Dobravolskas) Date: Wed, 4 Jan 2006 22:04:17 +0000 (GMT) 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: <20060104220417.C903616A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: psionic@csh.rit.edu, freebsd-current@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 22:04:17 -0000 > Hello, > > > I think you can do this with usbhidaction(1). > I would do it but I have not succeeded to make UHID device to work at all. > > > Once again, we need to know what usbdevs -v and usbhidctl have to say > > before we can speculate further. > I hope this list allows attachments. I think it is quite interesting > to look at my results. I have tested system with ums in kernel and > without it. If first case I have ums0 and uhid0 in second two uhid > devices. The second uhid device (or the first when ums is in kernel) > is not working for me. usbhidctl prints no valuable information. I > have installed usbutil to my system as well. It printed some valuable > information. uhid1 is both Keyboard (for page up and page down > buttons) and Consumer device (for volume control buttons). > > I have checked /usr/share/misc/usb_hid_usages and found that following > three lines corresponds to Volume Up, Volume Down and Mute: > Usage(234) > Usage(233) > Usage(226) > > Best regards, > Dalius Looking at the output you sent me from usbctl, it appears there is in fact one device with two interfaces. Interface 0 is the mouse and interface 1 is the keyboard. It looks like the uhid0 device is supposed to be the instance related to the keyboard (interface 1) but it's not seeing the HID descriptors. I'm not sure why this is. Possibly the code that's setting up the uhid device instance isn't setting the iface number correctly. If the interface setting was correct, you should have gotten more information from usbhidctl on uhid1. Unfortunatelt, I can't really debug this without physical access to the device, and even then I'm not sure I can help since I'm not all that familiar with the guts of the USB code. (You can try building with USB_DEBUG and turning on some of the verbose logging to see where it might be going wrong.) -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 22:49:01 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2A7AC16A420; Wed, 4 Jan 2006 22:49:01 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id E85A843D70; Wed, 4 Jan 2006 22:48:50 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k04Mm6i07331; Wed, 4 Jan 2006 14:48:06 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k04Mm5la001235; Wed, 4 Jan 2006 14:48:05 -0800 (PST) (envelope-from faber) Date: Wed, 4 Jan 2006 14:48:05 -0800 From: Ted Faber To: John Baldwin Message-ID: <20060104224805.GA1191@hut.isi.edu> References: <20060103233406.GA1564@hut.isi.edu> <200601041458.23129.jhb@freebsd.org> <20060104212623.GA1002@hut.isi.edu> <200601041700.14244.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <200601041700.14244.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 22:49:01 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 04, 2006 at 05:00:13PM -0500, John Baldwin wrote: > Ok, use the workaround other folks have posted for now. Hack vga_pci.c t= o=20 > always add the "agp" device in its attach routine instead of checking for= =20 > PCIY_AGP. FYI, this worked just fine. I see that a few people are having problems with this. Is there any interest in adding a tunable to force the agp device into existence? I'd be happy to whip up a patch. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvFClaUz3f+Zf+XsRAiGjAKDstikuIc4DiTTz/sU7uOYw4x5RuwCeJwzK SuoGuI+1izFIZf7ueqLkT3o= =CV4s -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 23:36:18 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ECA4216A41F for ; Wed, 4 Jan 2006 23:36:18 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3303043D58 for ; Wed, 4 Jan 2006 23:36:14 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id k04NaDa8088185; Thu, 5 Jan 2006 00:36:13 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id k04NaD18088184; Wed, 4 Jan 2006 18:36:13 -0500 (EST) (envelope-from cracauer) Date: Wed, 4 Jan 2006 18:36:13 -0500 From: Martin Cracauer To: "Bjoern A. Zeeb" Message-ID: <20060104183612.A88093@cons.org> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> <20051210125221.M23668@maildrop.int.zabbadoz.net> <20051216173106.B31803@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20051216173106.B31803@cons.org>; from cracauer@cons.org on Fri, Dec 16, 2005 at 05:31:06PM -0500 Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 23:36:19 -0000 Since I sent the mail below I had to discover that the new driver has a problem when no cable is plugged in, at least on my Asus board. It doesn't only run into timeouts, during some of these timeout the machine or at least the keyboard hangs for about a minute. Is there anything I can do to help debug this? dmesg acpiconf etc of one of the machines are here: http://www.cons.org/cracauer/machines/wings-a8ne-premium/ Martin Martin Cracauer wrote on Fri, Dec 16, 2005 at 05:31:06PM -0500: > Sorry for being late. > > The code that has been committed to -current works fine for me (DFI > NF4 SLI-DR). It occasionally prints a timeout message on startup > (long into userland start), but it works fine and doesn't print more > messages. > > Performance is lower than Linux (about 70 MB/sec versus Linux which > gets the 108 MB/sec). > > Martin > -- > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > Martin Cracauer http://www.cons.org/cracauer/ > FreeBSD - where you want to go, today. http://www.freebsd.org/ -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-current@FreeBSD.ORG Wed Jan 4 21:39:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02CDC16A41F for ; Wed, 4 Jan 2006 21:39:18 +0000 (GMT) (envelope-from sveinhal@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34DA043D83 for ; Wed, 4 Jan 2006 21:39:08 +0000 (GMT) (envelope-from sveinhal@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so1930488wxc for ; Wed, 04 Jan 2006 13:39:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DBdDDTRN/UY6Xk5p5kF8oF1e53gaV2vIFH4yucBFgzw3L+IIW0He8dHF9rYuiTGQ5N5RP++TLqCgsCb+9fPNnuEYoixb8Z8QoyEuBs/NPWLBf+1sCZzFnlCYgD002fhQeRkgpRSkBNVzm2UuTsuZU6tgXuvohMElS+gk5E47iaA= Received: by 10.70.108.5 with SMTP id g5mr4327825wxc; Wed, 04 Jan 2006 13:39:07 -0800 (PST) Received: by 10.70.105.11 with HTTP; Wed, 4 Jan 2006 13:39:07 -0800 (PST) Message-ID: Date: Wed, 4 Jan 2006 22:39:07 +0100 From: Svein Halvor Halvorsen Sender: sveinhal@gmail.com To: Ted Faber In-Reply-To: <20060103233406.GA1564@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060103233406.GA1564@hut.isi.edu> X-Mailman-Approved-At: Thu, 05 Jan 2006 00:01:06 +0000 Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jan 2006 21:39:18 -0000 On 1/4/06, Ted Faber wrote: > On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 > package against the new source, my Xserver won't allocate many video > modes because it can't open /dev/agpgart to allocate memory. The video > card is an Intel I810 - 865G chipset. > > On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide > appears (which seems to be hinted at in the comments to the most recent > change to /sys/pci/agp_i810.c from the CVS tree). I've attached a > verbose dmesg from the kernel recent -CURRENT kernel. > > Anyone else having a similar problem or know what I'm doing wrong? I'm > happy to test patches or provide more info. Even though I asked tis question twice, I did not get a single response. No-one even bothered to ask me for more detail. On my Dell Latitude x300 I had a similar problem but on the 855GM-chipset. The problem seemed to be related to apci_video loading boefore agp and somehow attaching to the video card, and blocking agp from attaching. Or something like that. Your problem might not be the same, though. Svein Halvor From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 00:21:16 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF8FD16A41F for ; Thu, 5 Jan 2006 00:21:16 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from dglawrence.com (dsl-230-156.ipns.com [209.210.230.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id E426B43D53 for ; Thu, 5 Jan 2006 00:21:12 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from tnn.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.4/8.13.3) with ESMTP id k050L5sC058519; Wed, 4 Jan 2006 16:21:05 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by tnn.dglawrence.com (8.13.4/8.13.3/Submit) id k050L3lQ058501; Wed, 4 Jan 2006 16:21:03 -0800 (PST) (envelope-from dg@dglawrence.com) X-Authentication-Warning: tnn.dglawrence.com: dg set sender to dg@dglawrence.com using -f Date: Wed, 4 Jan 2006 16:21:03 -0800 From: "David G. Lawrence" To: Martin Cracauer Message-ID: <20060105002103.GB98594@tnn.dglawrence.com> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> <20051210125221.M23668@maildrop.int.zabbadoz.net> <20051216173106.B31803@cons.org> <20060104183612.A88093@cons.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <20060104183612.A88093@cons.org> Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 00:21:16 -0000 --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Since I sent the mail below I had to discover that the new driver > has a problem when no cable is plugged in, at least on my Asus board. > > It doesn't only run into timeouts, during some of these timeout the > machine or at least the keyboard hangs for about a minute. > > Is there anything I can do to help debug this? I ran into this problem recently as well and spent some time diagnosing it. It's not that the cable isn't plugged in - rather it happens whenever the traffic levels are low. The problem is that the nvidia-supplied portion of the driver is defering the releasing of the completed transmit buffers and this occasionally results in if_timer expiring, causing the driver watchdog routine to be called ("device timeout"). The watchdog routine resets the card and the nvidia-supplied code sits in a high-priority loop waiting for the card to reset. This can take many seconds and your system will be hung until it completes. I have a work-around patch for the problem that I've attached to this email. It simply disables the watchdog. A real fix would involve accounting for the outstanding transmit buffers differently (or perhaps not at all - e.g. always attempt to call the nvidia-supplied code and if a queue-full error occurs, then wait for an interrupt before trying to queue more transmit packets). -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="nve.diff" Index: if_nve.c =================================================================== RCS file: /home/ncvs/src/sys/dev/nve/if_nve.c,v retrieving revision 1.7.2.8 diff -c -r1.7.2.8 if_nve.c *** if_nve.c 25 Dec 2005 21:57:03 -0000 1.7.2.8 --- if_nve.c 5 Jan 2006 00:12:45 -0000 *************** *** 943,949 **** return; } /* Set watchdog timer. */ ! ifp->if_timer = 8; /* Copy packet to BPF tap */ BPF_MTAP(ifp, m0); --- 943,949 ---- return; } /* Set watchdog timer. */ ! ifp->if_timer = 0; /* Copy packet to BPF tap */ BPF_MTAP(ifp, m0); --YiEDa0DAkWCtVeE4-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 00:22:40 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97E2316A41F; Thu, 5 Jan 2006 00:22:40 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (geri.cc.fer.hr [161.53.72.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 939FD43D49; Thu, 5 Jan 2006 00:22:38 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from geri.cc.fer.hr (localhost.cc.fer.hr [127.0.0.1]) by geri.cc.fer.hr (8.13.4/8.13.1) with ESMTP id k050LVOT037299; Thu, 5 Jan 2006 01:21:31 +0100 (CET) (envelope-from ivoras@fer.hr) Received: from localhost (ivoras@localhost) by geri.cc.fer.hr (8.13.4/8.13.1/Submit) with ESMTP id k050LVdE037296; Thu, 5 Jan 2006 01:21:31 +0100 (CET) (envelope-from ivoras@fer.hr) X-Authentication-Warning: geri.cc.fer.hr: ivoras owned process doing -bs Date: Thu, 5 Jan 2006 01:21:31 +0100 (CET) From: Ivan Voras Sender: ivoras@geri.cc.fer.hr To: hackers@freebsd.org Message-ID: <20060105005633.H36895@geri.cc.fer.hr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: A sort-of distributed filesystem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 00:22:40 -0000 I've threatened several times to make a distributed filesystem (or something like it) using FUSE, so I found the time over the holiday and did it. http://ivoras.sharanet.org/stuff/tdfs-r0.tgz This is a FUSE (userland) filesystem that propagates write requests to a remote daemon, while implementing read (and fstat and the like) requests locally. In short, this implements single-writer-multiple-readers scenario, where on one machine the filesystem is both readable and writeable and on multiple others it's only readable. (Actually, it's also writeable there, but the changes are not propagated). It's not a complete new filesystem but acts on existing filesystems, like an overlay / stacked filesystem (it's completely independant of the underlying filesystem type, but it's not tested on msdosfs :) ). The idea is that this could be used for hot-backups, load balancing, etc. This is only a proof of concept implementation, undertested and possibly with several bugs (I noticed late that timestamps are not always correctly propagated but will look into it tomorrow). To make it faster and possibly more robust for general usage it would have to be reimplemented in kernel. It's developed and tested on FreeBSD 6-stable and is currently not very portable to other operating systems (except 7-current and up). FUSE libraries and kernel module are required for operation. Don't forget to load the fuse.ko module. More information is provided in the README file so read it before trying to use it. If anyone wants to contact me off-list, please use the address in the README file. -- Preserve wildlife -- pickle a squirrel today! From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 02:54:14 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC3F016A41F; Thu, 5 Jan 2006 02:54:14 +0000 (GMT) (envelope-from mux@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id A545643D53; Thu, 5 Jan 2006 02:54:14 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 82CF51A3C22; Wed, 4 Jan 2006 18:54:14 -0800 (PST) Date: Thu, 5 Jan 2006 03:54:14 +0100 From: Maxime Henrion To: Alexander Leidinger Message-ID: <20060105025414.GJ55746@elvis.mu.org> References: <00fb01c610ed$392fdf10$951fa8c0@venti> <20060104104521.463FA16A420@hub.freebsd.org> <98dd087e0601040317j46c10561m@mail.gmail.com> <20060104130126.0bd6a9f9@Magellan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060104130126.0bd6a9f9@Magellan.Leidinger.net> User-Agent: Mutt/1.4.2.1i Cc: Dalius Dobravolskas , freebsd-current@freebsd.org, wpaul@freebsd.org Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 02:54:15 -0000 Alexander Leidinger wrote: > On Wed, 4 Jan 2006 13:17:56 +0200 > Dalius Dobravolskas wrote: > > > 3) The device reported itself as keyboard and algorithm does not check > > for mouse; It must be checked it is just my guess ;) Brian, could you > > try to remove ukbd from kernel in this case and look if mouse is > > found? > > Maxime (CCed) is working on porting the uhidev part from NetBSD. This is > supposed to fix those problems (at least if I read the symptoms > correctly). > > Bill, the problem is that some combi-devices don't meet the > expectations of FreeBSD. AFAIK they report one device with 2 functions > while FreeBSD currently needs 2 devices to work as expected. Yes, it might indeed be an USB HID device with mutliple report IDs, in which case it should work OK as soon as I finish merging the NetBSD code. In the new world order, there is an uhidev(4) driver that attaches to any USB HID device, and it spawns one child per report ID. The child can be any of ums(4), ukbd(4), ucycom(4), etc, or the "base" uhid(4) driver if none of the previous ones matched. Sample output from my dev box : uhidev0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1 ums0 on uhidev0 And now a multiple report id device : uhidev1: vendor 0x0810 Twin USB Joystick, rev 1.00/1.06, addr 2, iclass 3/0 uhidev1: 2 report ids uhid0 on uhidev1 uhid0: input=7, output=4, feature=0 uhid1 on uhidev1 uhid1: input=7, output=4, feature=0 The second device allows one to plug two PS2 gamepads, and I recommend anyone that likes xmame to buy one. It's actually what prompted this work :-). FWIW, it shouldn't take long for me to finish this stuff, but I'm currently stuck with ukbd(4) making my system panic in weird ways... Life would have probably been easier if our kbd framework wasn't such a mess. Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 03:47:05 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DD2416A41F for ; Thu, 5 Jan 2006 03:47:05 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from smtp02.mrf.mail.rcn.net (smtp02.mrf.mail.rcn.net [207.172.4.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id B700943D5E for ; Thu, 5 Jan 2006 03:47:04 +0000 (GMT) (envelope-from roberthuff@rcn.com) Received: from 209-6-22-49.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com (HELO jerusalem.litteratus.org.litteratus.org) ([209.6.22.49]) by smtp02.mrf.mail.rcn.net with ESMTP; 04 Jan 2006 22:46:57 -0500 X-IronPort-AV: i="3.99,331,1131339600"; d="scan'208"; a="191595329:sNHT85341538" From: Robert Huff MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17340.38546.880801.123738@jerusalem.litteratus.org> Date: Wed, 4 Jan 2006 22:46:26 -0500 To: current@freebsd.org X-Mailer: VM 7.17 under 21.5 (beta24) "dandelion" XEmacs Lucid Cc: Subject: sk(4) ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 03:47:05 -0000 Is there anyone currently in charge of the sk driver? Bill Paul has disclaimed any further connection (never mind lack of time) and I have a NIC which is not being recognized. Robert Huff From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 06:00:14 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B99116A41F for ; Thu, 5 Jan 2006 06:00:14 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABA8143D5E for ; Thu, 5 Jan 2006 06:00:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id DEED81FFACF; Thu, 5 Jan 2006 07:00:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 423151FFACE; Thu, 5 Jan 2006 07:00:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 78F4044487E; Thu, 5 Jan 2006 05:58:24 +0000 (UTC) Date: Thu, 5 Jan 2006 05:58:24 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Robert Huff In-Reply-To: <17340.38546.880801.123738@jerusalem.litteratus.org> Message-ID: <20060105055731.Q24703@maildrop.int.zabbadoz.net> References: <17340.38546.880801.123738@jerusalem.litteratus.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: FreeBSD current mailing list Subject: Re: sk(4) ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 06:00:14 -0000 On Wed, 4 Jan 2006, Robert Huff wrote: > > Is there anyone currently in charge of the sk driver? Bill > Paul has disclaimed any further connection (never mind lack of time) > and I have a NIC which is not being recognized. And it's a PCI-E one? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 09:17:41 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 889B216A41F for ; Thu, 5 Jan 2006 09:17:41 +0000 (GMT) (envelope-from andrea@brancatelli.it) Received: from reddevil.brancatelli.it (reddevil.brancatelli.it [66.98.144.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2EB8F43D48 for ; Thu, 5 Jan 2006 09:17:41 +0000 (GMT) (envelope-from andrea@brancatelli.it) Received: from UebiMiau (localhost.brancatelli.it [127.0.0.1]) by reddevil.brancatelli.it (8.12.9p2/8.12.9) with SMTP id k059HeAN023417 for ; Thu, 5 Jan 2006 09:17:40 GMT (envelope-from andrea@brancatelli.it) Message-Id: <200601050917.k059HeAN023417@reddevil.brancatelli.it> Received: from client 80.207.172.194 for UebiMiau2.7 (webmail client); Thu, 5 Jan 2006 9:17:40 -0000 Date: Thu, 5 Jan 2006 9:17:40 -0000 From: "Andrea Brancatelli" To: current@freebsd.org X-Priority: 3 X-Mailer: UebiMiau 2.7.2 X-Original-IP: 80.207.172.194 Content-Transfer-Encoding: 8bit X-MSMail-Priority: Medium Importance: Medium Content-Type: text/plain; charset="iso-8859-1"; MIME-Version: 1.0 Cc: Subject: The BladeCenter Saga. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrea Brancatelli List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 09:17:41 -0000 Hello everybody. A quick update on the good old IBM BladeCenter saga. We have several BladeCenter in our server farm. The first two (the oldest one) have a USB CD Rom and refuse to boot from the CD. I succesfully booted them with the i386 floppies: they booted ok but when SysInstall started the default keyboard was NOT the local console one (that is connected on USB port 2) but the Web-Based Java Management one, so taking remote control of the blade allowed us to use the keyboard without any problem. Then we stepped on next problem... but first... On the third bladecenter (the newest one) I could succesfully boot from either the i386 and the amd64 CDRoms, but when the kernel booted it would hang at atkbd's detection (as someone else reported in different threads). To workaround this we used the set hint.atkbd.0.disabled=1 and everything went ok. As usual the local keyboard wasn't working but the remote one was. And then we stepped on the same problem as the first 2 bladecenters: The blades have two Broadcom NICs... the bge drivers fires up with no problem, but none of the bge0/bge1 card seems to actually work. Whathever setting I apply to them I cannot reach anything on the outside, and furthermore the emergency shell on VTY4 allows me a very short set of commands. I have no doubts on the functionality of the hardware for various reason (we tried to install on 3 different server always with the same results; one of the blades was working ok with windows 2003 before). A very suspicious thing is that ifconfig reports for both the cards: "status: no carrier", while the cable is surely pulled in (it's hard wired, it cannot be pulled off at all). So we are stuck again. I downloaded the complete ISO for amd64. I plan on doing the installation from CDRom on Blade 3 (the one that actually succeeds in seeing the CD) and then investigate further on the Broadcom issue. Do anyone has ever stepped on problem with the bge driver? Hints? Thank you very much. I will report more detailedly later. -- Andrea Brancatelli http://andrea.brancatelli.it/ ________________________________________________ Message sent using UebiMiau 2.7.2 From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 10:42:37 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D72716A41F; Thu, 5 Jan 2006 10:42:37 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8501F43D46; Thu, 5 Jan 2006 10:42:34 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp232-237.lns2.adl4.internode.on.net [203.122.232.237]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k05AgBiw082555 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Thu, 5 Jan 2006 21:12:12 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jo Rhett Date: Thu, 5 Jan 2006 21:11:58 +1030 User-Agent: KMail/1.8.3 References: <43A266E5.3080103@samsco.org> <200512231126.51500.doconnor@gsoft.com.au> <20060105093220.GJ1358@svcolo.com> In-Reply-To: <20060105093220.GJ1358@svcolo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4565128.1sz4yHWUgZ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601052112.09446.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, current , Peter Jeremy , stable@freebsd.org, K?vesd?n G?bor Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 10:42:37 -0000 --nextPart4565128.1sz4yHWUgZ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 5 Jan 2006 20:02, Jo Rhett wrote: > On Fri, Dec 23, 2005 at 11:26:44AM +1030, Daniel O'Connor wrote: > > How do you expect these two to be handled in a binary upgrade? > > I can't see how it's possible.. > > Look around. Every major commercial OS does it just fine. Most of the > open source OSes do it just fine. Debian had probably the easiest to use > system, and they've risen, owned the world and fallen all while FreeBSD h= as > been debating this issue. You appear to be misunderstanding what I said. I'm not arguing binary upgrades shouldn't be done but I'm suggesting that i= t=20 isn't NECESSARY to version and package the base install to do it. > > I don't think integrating it with the core OS (whatever that means) will > > magically fix this. > > If you knew what it meant, you would understand why it would help. Ah what a great explanation of what is meant. There are several people who don't know what is meant here and I haven't se= en=20 a decent explanation forthcoming. > > Not having run jails I am not very qualified to comment > > Exactly. Sorry, not trying to be rude but if you have never felt the pain > don't try and say it doesn't exist. Just because I don't run jails doesn't mean I don't know the pain of upgrad= ing=20 a system. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart4565128.1sz4yHWUgZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvPgB5ZPcIHs/zowRAptBAJ9nSXeZUYkCicFxhv5CrNcuAQ7e/gCdFTXh oT226YogorSiHAgu2EmN0hs= =SGCC -----END PGP SIGNATURE----- --nextPart4565128.1sz4yHWUgZ-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 11:26:26 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D583A16A41F; Thu, 5 Jan 2006 11:26:26 +0000 (GMT) (envelope-from ozawa@ongs.co.jp) Received: from hepitas.ongs.net (hepitas.ongs.net [202.216.232.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6392943D58; Thu, 5 Jan 2006 11:26:25 +0000 (GMT) (envelope-from ozawa@ongs.co.jp) Received: from [IPv6???1] (localhost.ongs.net [127.0.0.1]) by hepitas.ongs.net (Postfix) with ESMTP id 6F8763F; Thu, 5 Jan 2006 13:51:30 +0900 (JST) Message-ID: <43BCAA9F.2000505@ongs.co.jp> Date: Thu, 05 Jan 2006 14:11:59 +0900 From: Masanori OZAWA Organization: ONGS Inc. User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051219) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, daichi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ozawa@ongs.co.jp List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 11:26:27 -0000 Danny Braniss wrote: >>Masanori OZAWA wrote: >>[...] >> >>Nice work! This is just a "works for me". In only find some issues with >>permissions that were already present in the previous implementation of >>unionfs. Some of them are partially corrected in the "useful" copymode. >>I mailed the details to the author. > > > the following will hang the kernel: > root is mounted nfs, > /etc is unionfs'ed so: > from /etc/rc.initdiskless: > ... > # Create a generic memory disk > # > mount_md() { > /sbin/mdmfs -i 4096 -s $1 -M md $2 > } > kldload unionfs > mount_md 4096 /.etc > mount_unionfs /.etc /etc > ... > and now: > cd /etc > mv some-file somefile > and now the system is stuck. > this behaviour is also present in the unpatched unionfs, but would be nice > if it can be fixed. > > danny > ps: see http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84107 > Okey. I found the cause of this problem. I fixed it :) http://people.freebsd.org/~daichi/unionfs/unionfs-p2.diff I am getting a edit of HP around my improvements of unionfs bacause someone have pointed out that your explanation is not enough. -- ONGS Inc. Masanori OZAWA (ozawa@ongs.co.jp) WWW: http://www.ongs.co.jp/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 11:41:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D2A116A41F; Thu, 5 Jan 2006 11:41:03 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail04.syd.optusnet.com.au (mail04.syd.optusnet.com.au [211.29.132.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5DC9843D5C; Thu, 5 Jan 2006 11:41:00 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail04.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k05BewI1008763 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 5 Jan 2006 22:40:58 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k05BevHh050117; Thu, 5 Jan 2006 22:40:57 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k05BevOZ050116; Thu, 5 Jan 2006 22:40:57 +1100 (EST) (envelope-from pjeremy) Date: Thu, 5 Jan 2006 22:40:56 +1100 From: Peter Jeremy To: Jo Rhett Message-ID: <20060105114056.GN42228@cirb503493.alcatel.com.au> References: <43A266E5.3080103@samsco.org> <20051217215434.GB92180@svcolo.com> <20051217220807.GA28741@freebie.xs4all.nl> <43A492B6.6050305@t-hosting.hu> <20051217232856.GT77268@cirb503493.alcatel.com.au> <43A4B91D.8040304@samsco.org> <20051222211730.GK39174@svcolo.com> <20051223045648.GH77268@cirb503493.alcatel.com.au> <20060105093727.GK1358@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105093727.GK1358@svcolo.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: stable@freebsd.org, current Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 11:41:03 -0000 On Thu, 2006-Jan-05 01:37:27 -0800, Jo Rhett wrote: >No. I want a binary update mechanism. Obviously if we have local >configuration options we'll have to compile our own binaries. But doing >the work of tracking system updates currently requires us to build our own >patch tracking mechanism, and then re-write it for every new release. If you're willing to do your own compiles: 1) CVSup or cvs update to whatever branch you want 2) make build{world,kernel} 3) make DESTDIR=/updates install{world,kernel} 4) mergemaster -D /updates 5) rsync or similar It seems fairly obvious that you are frustrated by FreeBSD's inability to meet your needs as far as updating is concerned. I suspect I'm not alone in being uncertain exactly what your requirements are and what additional features FreeBSD needs to satisfy you. How would you like to write a formal requirements specification and post it here (or in -arch). >It's not a recompile issue. It's a tracking/update/backout issue. I don't >mind recompiling, if I could somehow push the updates to all the right >systems and they would have it stored somewhere that they were patched... Have you looked at tools like Bcfg2 ( http://www.mcs.anl.gov/cobalt/bcfg2/ )? -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 12:25:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFC8C16A41F; Thu, 5 Jan 2006 12:25:52 +0000 (GMT) (envelope-from ozawa@ongs.co.jp) Received: from hepitas.ongs.net (hepitas.ongs.net [202.216.232.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E13343D5F; Thu, 5 Jan 2006 12:25:51 +0000 (GMT) (envelope-from ozawa@ongs.co.jp) Received: from [IPv6???1] (localhost.ongs.net [127.0.0.1]) by hepitas.ongs.net (Postfix) with ESMTP id 7CCC83F; Thu, 5 Jan 2006 21:05:21 +0900 (JST) Message-ID: <43BD1054.7020409@ongs.co.jp> Date: Thu, 05 Jan 2006 21:25:56 +0900 From: Masanori OZAWA Organization: ONGS Inc. User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051219) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Danny Braniss References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, daichi@freebsd.org, freebsd-current@freebsd.org Subject: Re: [unionfs][patch] improvements of the unionfs - Problem Report, kern/91010 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ozawa@ongs.co.jp List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 12:25:52 -0000 Danny Braniss wrote: >>Okey. I found the cause of this problem. I fixed it :) >> >>http://people.freebsd.org/~daichi/unionfs/unionfs-p2.diff > > > can you make the diffs for 6.0? > thanks, > danny > > For 7-current patch: http://people.freebsd.org/~daichi/unionfs/unionfs-p2.diff (latest patch) http://people.freebsd.org/~daichi/unionfs/unionfs-p1.diff (old patch) For 6.x patch: http://people.freebsd.org/~daichi/unionfs/unionfs6-p2.diff (latest patch) http://people.freebsd.org/~daichi/unionfs/unionfs6-p1.diff (old patch) HowToInstall: http://people.freebsd.org/~daichi/unionfs/howtoinstall (UTF-8) Detail description: http://people.freebsd.org/~daichi/unionfs/index-ja.html (Japanese, UTF-8) http://people.freebsd.org/~daichi/unionfs/index.html (English, but not yet, so sorry) Please keep up your interest around unionfs. We need to improve FreeBSD's unionfs I believe :) -- ONGS Inc. Masanori OZAWA (ozawa@ongs.co.jp) WWW: http://www.ongs.co.jp/ From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 12:49:43 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C99F616A41F for ; Thu, 5 Jan 2006 12:49:43 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3259743D46 for ; Thu, 5 Jan 2006 12:49:42 +0000 (GMT) (envelope-from jiashiun@gmail.com) Received: by wproxy.gmail.com with SMTP id i14so2665975wra for ; Thu, 05 Jan 2006 04:49:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fKvPYas0IiUI3628ulGa06zG2dL9vP6l/HVj/pt9YRdBFb+h1D1prnn7I4OmEEbxcO+5igx3HkrWdQU7/GUl9puVj076i1PROZ5N6OChSMKzBSODTDqAbXAu0M0TsZPz/t1VDJVIXXJsVbsGvAb0IJjc6DerNkFwcukS+R4+6fY= Received: by 10.54.97.2 with SMTP id u2mr3171163wrb; Thu, 05 Jan 2006 04:49:42 -0800 (PST) Received: by 10.54.131.9 with HTTP; Thu, 5 Jan 2006 04:49:42 -0800 (PST) Message-ID: <1d6d20bc0601050449r62edc659x@mail.gmail.com> Date: Thu, 5 Jan 2006 20:49:42 +0800 From: Jia-Shiun Li To: Dalius Dobravolskas In-Reply-To: <98dd087e0601022141r350d48d5q@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <98dd087e0512270540h44b6e89bh@mail.gmail.com> <98dd087e0601022141r350d48d5q@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: mouse and extra buttons X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 12:49:43 -0000 2006/1/3, Dalius Dobravolskas : > On 27/12/05, Dalius Dobravolskas wrote: > > I need help with mouse having extra buttons. > I wrote here about before one week. So the problem seems to be that my > mouse is more UHID device than usb mouse. However UHID support for > mouses seems to be incomplete. 'cat' maybe not so good because the raw data are sometimes interpreted as invisible characters. Try 'moused -d -f -t auto -p /dev/ums0' instead and see what happens when you press buttons. And you did not mentioned where you wanted to use these extra buttons. In X I believe you have to set max button number and blah blah in config file. See the chapter about X and mice in FreeBSD FAQ. Jia-Shiun. From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 17:01:36 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BA3E16A41F for ; Thu, 5 Jan 2006 17:01:36 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from lexi.siliconlandmark.com (lexi.siliconlandmark.com [209.69.98.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 924CC43D60 for ; Thu, 5 Jan 2006 17:01:33 +0000 (GMT) (envelope-from andy@siliconlandmark.com) Received: from [10.7.6.251] ([63.76.235.163]) by lexi.siliconlandmark.com (8.13.3/8.13.3) with ESMTP id k05H1FcX042500; Thu, 5 Jan 2006 12:01:15 -0500 (EST) (envelope-from andy@siliconlandmark.com) In-Reply-To: <200601050917.k059HeAN023417@reddevil.brancatelli.it> References: <200601050917.k059HeAN023417@reddevil.brancatelli.it> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <160B72FB-0B0A-4B8F-9065-5EFBCB41D4EC@siliconlandmark.com> Content-Transfer-Encoding: 7bit From: Andre Guibert de Bruet Date: Thu, 5 Jan 2006 12:01:09 -0500 To: Andrea Brancatelli X-Mailer: Apple Mail (2.746.2) X-Information: Please contact the ISP for more information X-SL-MailScanner: Found to be clean X-SL-SpamCheck: not spam, SpamAssassin (score=-1.738, required 6, AWL -0.28, BAYES_00 -2.60, SPF_FAIL 1.14) X-MailScanner-From: andy@siliconlandmark.com Cc: current@freebsd.org Subject: Re: The BladeCenter Saga. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 17:01:36 -0000 On Jan 5, 2006, at 4:17 AM, Andrea Brancatelli wrote: > The blades have two Broadcom NICs... the bge drivers fires up with no > problem, but none of the bge0/bge1 card seems to actually work. > Whathever > setting I apply to them I cannot reach anything on the outside, and > furthermore the emergency shell on VTY4 allows me a very short set of > commands. I have no doubts on the functionality of the hardware for > various reason (we tried to install on 3 different server always > with the > same results; one of the blades was working ok with windows 2003 > before). > > A very suspicious thing is that ifconfig reports for both the cards: > "status: no carrier", while the cable is surely pulled in (it's hard > wired, it cannot be pulled off at all). > > So we are stuck again. I downloaded the complete ISO for amd64. I > plan on > doing the installation from CDRom on Blade 3 (the one that actually > succeeds in seeing the CD) and then investigate further on the > Broadcom > issue. > > Do anyone has ever stepped on problem with the bge driver? Though not in a blade configuration, I have had a couple of Dell PowerEdge servers with the bge driver running for a couple of years flawlessly. pciconf thinks the following, on both systems: bge0@pci1:8:0: class=0x020000 card=0x00d11028 chip=0x164414e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5700 NetXtreme Gigabit Ethernet Controller' class = network subclass = ethernet dmesg: bge0: mem 0xfeb00000-0xfeb0ffff irq 17 at device 8.0 on pci1 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:06:5b:3a:xx:xx ifconfig: bge0: flags=8843 mtu 1500 options=1a inet 10.10.10.110 netmask 0xffffff00 broadcast 10.10.10.255 ether 00:06:5b:3a:xx:xx media: Ethernet autoselect (100baseTX ) status: active > Hints? Does your blade management console allow you to enable/disable the ethernet cards presented to the system (By returning no carrier status)? Andy /* Andre Guibert de Bruet * 6f43 6564 7020 656f 2e74 4220 7469 6a20 */ /* Code poet / Sysadmin * 636f 656b 2e79 5320 7379 6461 696d 2e6e */ /* GSM: +1 734 846 8758 * 5520 494e 2058 6c73 7565 6874 002e 0000 */ /* WWW: siliconlandmark.com * Tormenting bytes since 1980. */ From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 18:02:59 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAF6C16A41F for ; Thu, 5 Jan 2006 18:02:59 +0000 (GMT) (envelope-from andrea@brancatelli.it) Received: from reddevil.brancatelli.it (reddevil.brancatelli.it [66.98.144.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE7ED43D5A for ; Thu, 5 Jan 2006 18:02:58 +0000 (GMT) (envelope-from andrea@brancatelli.it) Received: from UebiMiauCustomizedbyRagedRecords (localhost.brancatelli.it [127.0.0.1]) by reddevil.brancatelli.it (8.12.9p2/8.12.9) with SMTP id k05I2wAN026595 for ; Thu, 5 Jan 2006 18:02:58 GMT (envelope-from andrea@brancatelli.it) Message-Id: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> Received: from client 80.207.172.194 for UebiMiau2.7 (webmail client); Thu, 5 Jan 2006 18:02:58 +0100 Date: Thu, 5 Jan 2006 18:02:58 +0100 From: "Andrea Brancatelli" To: current@freebsd.org X-Priority: 3 X-Mailer: UebiMiau/Customized by RagedRecords 2.7.2 X-Original-IP: 80.207.172.194 Content-Transfer-Encoding: 8bit X-MSMail-Priority: Medium Importance: Medium Content-Type: text/plain; charset="iso-8859-1"; MIME-Version: 1.0 Cc: Subject: The BladeCenter Saga -> bge driver not behaving properly... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Andrea Brancatelli List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 18:02:59 -0000 Sorry for breaking the thread and posting a new message instead of replying but I'm having some problems with my mailserver. I did a few screenshots of the problems we are having with the Broadcom lan card and the bge driver... I cannot paste text because I cannot access the machine in SSH (since it's not working...) So here they are: dmesg output: http://andrea.brancatelli.it/shots/cupido_dmesg.jpg ifconfig output: http://andrea.brancatelli.it/shots/cupido_ifconfig.jpg strange arp behaviours: http://andrea.brancatelli.it/shots/cupido_arp.jpg I hope this enlighten a bit someone. The hardware is working properly (I have no doubt about this) and the lan settings are ok. Another strange thing is that as soon as FreeBSD starts the (usually always blinking due to net traffic) lan's LED goes always-on and stays steady on forever (as if there was no traffic at all). We have no idea of what's happening. Seems like all the traffic is going lost somewhere. FreeBSD is just installed so there is nothing like pf, software firewalling, or such. -- Andrea Brancatelli http://andrea.brancatelli.it/ ___________________________________________________ Raged Records s.r.l. - http://www.ragedrecords.com/ UebiMiau/Customized by RagedRecords - version 2.7.2 From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 18:28:34 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DC8F16A41F; Thu, 5 Jan 2006 18:28:34 +0000 (GMT) (envelope-from ender@tog.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F11043D91; Thu, 5 Jan 2006 18:28:13 +0000 (GMT) (envelope-from ender@tog.net) Received: by tog.net (Postfix, from userid 96) id 18BB329B6C6; Thu, 5 Jan 2006 13:28:12 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.0-terranovanet_v6 (2005-09-13) on doppelganger.terranova.net X-Spam-Level: X-Spam-Status: No, score=-5.1 required=7.1 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0-terranovanet_v6 Received: from [192.168.8.150] (host-216-89-225-138.terranova.net [216.89.225.138]) by tog.net (Postfix) with ESMTP id 02A3E29B6A3; Thu, 5 Jan 2006 13:28:06 -0500 (EST) Message-ID: <43BD64C4.4090307@tog.net> Date: Thu, 05 Jan 2006 13:26:12 -0500 From: Ender User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel O'Connor References: <43A266E5.3080103@samsco.org> <200512231126.51500.doconnor@gsoft.com.au> <20060105093220.GJ1358@svcolo.com> <200601052112.09446.doconnor@gsoft.com.au> In-Reply-To: <200601052112.09446.doconnor@gsoft.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, freebsd-stable@freebsd.org, current , Jo Rhett , K?vesd?n G?bor , Peter Jeremy Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 18:28:34 -0000 Daniel O'Connor wrote: >On Thu, 5 Jan 2006 20:02, Jo Rhett wrote: > > >>On Fri, Dec 23, 2005 at 11:26:44AM +1030, Daniel O'Connor wrote: >> >> >>>How do you expect these two to be handled in a binary upgrade? >>>I can't see how it's possible.. >>> >>> >>Look around. Every major commercial OS does it just fine. Most of the >>open source OSes do it just fine. Debian had probably the easiest to use >>system, and they've risen, owned the world and fallen all while FreeBSD has >>been debating this issue. >> >> > >You appear to be misunderstanding what I said. > >I'm not arguing binary upgrades shouldn't be done but I'm suggesting that it >isn't NECESSARY to version and package the base install to do it. > > > >>>I don't think integrating it with the core OS (whatever that means) will >>>magically fix this. >>> >>> >>If you knew what it meant, you would understand why it would help. >> >> > >Ah what a great explanation of what is meant. >There are several people who don't know what is meant here and I haven't seen >a decent explanation forthcoming. > > > I think what "integrated with the core OS" means from a user standpoint is: from a fresh minimum install of freebsd I can type "freebsd-update-whatever" and it will update my system. From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 18:42:11 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B77016A41F; Thu, 5 Jan 2006 18:42:11 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F97443D77; Thu, 5 Jan 2006 18:41:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k05IfoBT067226; Thu, 5 Jan 2006 10:41:50 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k05Ifl1L067225; Thu, 5 Jan 2006 10:41:47 -0800 (PST) (envelope-from jmg) Date: Thu, 5 Jan 2006 10:41:47 -0800 From: John-Mark Gurney To: "Daniel O'Connor" , freebsd-stable@freebsd.org, Chuck Swiger , current Message-ID: <20060105184147.GD69162@funkthat.com> Mail-Followup-To: Daniel O'Connor , freebsd-stable@freebsd.org, Chuck Swiger , current References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060105092448.GH1358@svcolo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 18:42:11 -0000 Jo Rhett wrote this message on Thu, Jan 05, 2006 at 01:24 -0800: > > You are putting words in the mouth of core@ - > > Sorry. As said before, the topic is always struck down and nobody from > core has ever stood up to say "we'll support this". I don't know whose on > core this week, nor will I at any given time. I just know that core has > either struck it down or been Silent. I believe core has a policy of never supporting vaporware... There is always the chicken and egg problem with arguments like this... I'll code this if you agree to support it and maintain it/I will agree to support it once you code it... In FreeBSD, and many open source projects, no code, no support, how can you support or even agree to support something that doesn't exist? And then as soon as FreeBSD agrees to support something that doesn't exist, either a) other people who were interested in the project stop, even if you end up never producing a bit of code, or b) someone else produces better code, drops the support for the original, but then the author complains about being told they'd support his code, and going with another code base... Bottom line: Once code exists, then support can be talked about.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 19:17:12 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22AA116A420 for ; Thu, 5 Jan 2006 19:17:12 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C9143D8F for ; Thu, 5 Jan 2006 19:17:00 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by wproxy.gmail.com with SMTP id i12so2579513wra for ; Thu, 05 Jan 2006 11:17:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=fC1a4V9YVX84RrlwvcsITBiNk/gUXop7+7fbGa7LOXMj6n38YEcgUFwutbYM8Jc7f1RxF9V0I0UwQyubKc3Jf3BIZbYzbbTaJ9E9RpLTUIl6V12NMyE4cY8cYCqbjA/DOQ5kbvp7SrG1rhz4Ffsb3e5/i15bnojlDxJ3j6T5x9U= Received: by 10.64.151.12 with SMTP id y12mr1504658qbd; Thu, 05 Jan 2006 11:16:59 -0800 (PST) Received: by 10.64.210.8 with HTTP; Thu, 5 Jan 2006 11:16:59 -0800 (PST) Message-ID: <2a41acea0601051116t6a1f277cwf378a3917fbf7ac@mail.gmail.com> Date: Thu, 5 Jan 2006 11:16:59 -0800 From: Jack Vogel To: Andrea Brancatelli In-Reply-To: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> Cc: current@freebsd.org Subject: Re: The BladeCenter Saga -> bge driver not behaving properly... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 19:17:12 -0000 On 1/5/06, Andrea Brancatelli wrote: > Sorry for breaking the thread and posting a new message instead of replyi= ng > but I'm having some problems with my mailserver. > > I did a few screenshots of the problems we are having with the Broadcom l= an > card and the bge driver... I cannot paste text because I cannot access th= e > machine in SSH (since it's not working...) > > So here they are: > > dmesg output: http://andrea.brancatelli.it/shots/cupido_dmesg.jpg > > ifconfig output: http://andrea.brancatelli.it/shots/cupido_ifconfig.jpg > > strange arp behaviours: http://andrea.brancatelli.it/shots/cupido_arp.jpg > > I hope this enlighten a bit someone. > > The hardware is working properly (I have no doubt about this) and the lan > settings are ok. > > Another strange thing is that as soon as FreeBSD starts the (usually alwa= ys > blinking due to net traffic) lan's LED goes always-on and stays steady on > forever (as if there was no traffic at all). > > We have no idea of what's happening. Seems like all the traffic is going > lost somewhere. > > FreeBSD is just installed so there is nothing like pf, software firewalli= ng, > or such. There is an internal switch to the Bladecenter chassis, its a module on the back (you dont get to just plug right into a NIC as on a normal PC :). The behavior of that switch is controlled by the management module if I am not mistaken, are you sure its configured sanely? Also, have you tried IBM support? I know they normally sell Linux for these, but maybe they'd offer some ideas?? Jack From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 21:13:38 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D45516A41F for ; Thu, 5 Jan 2006 21:13:38 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF6343D58 for ; Thu, 5 Jan 2006 21:13:35 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR003.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ISN00AN61MHA0F0@VL-MO-MR003.ip.videotron.ca> for freebsd-current@freebsd.org; Thu, 05 Jan 2006 16:13:31 -0500 (EST) Date: Thu, 05 Jan 2006 16:13:21 -0500 From: Nicolas Blais To: freebsd-current@freebsd.org Message-id: <200601051613.27718.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart126288579.fMAEobqRMM; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.8.3 Subject: linux-flashplugin-6.0 not working anymore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 21:13:38 -0000 --nextPart126288579.fMAEobqRMM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline A while ago I noticed that firefox and konqueror are not displaying flash=20 applets anymore on my -CURRENT system yet it works fine on all my 6-STABLE= =20 machines. When I run firefox from the shell, I get: [nicblais@clk01a] ~> firefox LoadPlugin: failed to initialize shared=20 library /usr/X11R6/lib/linux-flashplugin6/libflashplayer.so=20 [/usr/local/lib/pluginwrapper/flash6.so: version GLIBC_2.1 required=20 by /usr/X11R6/lib/linux-flashplugin6/libflashplayer.so not defined] (I have linux-glib2-2.4.8_1 installed) My libmap.conf is untouched :=20 # Flash6 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase [/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so] libpthread.so.0 pluginwrapper/flash6.so libdl.so.2 pluginwrapper/flash6.so libz.so.1 libz.so.3 libstdc++-libc6.2-2.so.3 libstdc++.so.5 libm.so.6 libm.so.4 libc.so.6 pluginwrapper/flash6.so And konqueror no longer finds my linux-flashplugin-6.0. The mplayer plugin = is=20 detected fine in both browsers. Since the linuxpluginwrapper port is broken= =20 for -CURRENT, I haven't tried to mess with it. Am I the only one with this problem? =2D-=20 =46reeBSD 7.0-CURRENT #9: Sat Dec 31 14:24:32 EST 2005 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart126288579.fMAEobqRMM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvYv34wTBlvcsbJURAqvvAJwLLprDuPCrRbXlBagPIszLJajvbwCgr7WL MfQ5qMZnJVZhammpAQPBTzk= =aDwa -----END PGP SIGNATURE----- --nextPart126288579.fMAEobqRMM-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 21:29:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 272E116A41F for ; Thu, 5 Jan 2006 21:29:59 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from ms-dienst.rz.rwth-aachen.de (ms-2.rz.RWTH-Aachen.DE [134.130.3.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2F3443D5A for ; Thu, 5 Jan 2006 21:29:34 +0000 (GMT) (envelope-from chris@haakonia.hitnet.rwth-aachen.de) Received: from circe (circe.rz.RWTH-Aachen.DE [134.130.3.36]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004)) with ESMTP id <0ISN00JQ92CN2X@ms-dienst.rz.rwth-aachen.de> for freebsd-current@freebsd.org; Thu, 05 Jan 2006 22:29:12 +0100 (MET) Received: from talos.rz.RWTH-Aachen.DE ([134.130.3.22]) by circe (MailMonitor for SMTP v1.2.2 ) ; Thu, 05 Jan 2006 22:29:11 +0100 (MET) Received: from bigboss.hitnet.rwth-aachen.de (bigspace.hitnet.RWTH-Aachen.DE [137.226.181.2]) by smarthost.rwth-aachen.de (8.13.1/8.13.1/1) with ESMTP id k05LRdha006386; Thu, 05 Jan 2006 22:27:39 +0100 Received: from lorien.hitnet.rwth-aachen.de ([137.226.181.92] helo=haakonia.hitnet.rwth-aachen.de) by bigboss.hitnet.rwth-aachen.de with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.50) id 1EucfX-0004Bh-Bz; Thu, 05 Jan 2006 22:29:11 +0100 Received: by haakonia.hitnet.rwth-aachen.de (Postfix, from userid 1001) id 092523F413; Thu, 05 Jan 2006 22:29:10 +0100 (CET) Date: Thu, 05 Jan 2006 22:29:10 +0100 From: Christian Brueffer In-reply-to: <200512270449.41709.Chris@lainos.org> To: Chris Gilbert Message-id: <20060105212910.GA907@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary=UlVJffcvxoiEqYs2; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.5.11 X-Operating-System: FreeBSD 6.0-STABLE X-PGP-Key: http://people.FreeBSD.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <200512270449.41709.Chris@lainos.org> Cc: freebsd-current@freebsd.org Subject: Re: ATI on FreeBSD! FireGL Linux Driver Port X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 21:29:59 -0000 --UlVJffcvxoiEqYs2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 27, 2005 at 04:49:41AM +0100, Chris Gilbert wrote: > Hi there! >=20 > Some time ago (about a year actually) I started some work in cooperation = with=20 > ATI to port their Linux "fglrx" driver to FreeBSD. >=20 > Well, about 2 months into that process I ended up moving to the other sid= e of=20 > the pond and leaving one of my dev machines behind. (The one with the ATI= =20 > card) >=20 > However, this last week I managed to get ahold of another machine with an= ATI=20 > card, and have picked back up where I left off about 9 months ago. >=20 > I've put together a preliminary alpha release of the driver port in it's= =20 > current state, and done a bit of testing myself. However, I would be thri= lled=20 > to get some feedback from you guys! >=20 > I have probably done some really horrible things, and I would like to hea= r it=20 > from you nice folks rather than from a thousand angry gamers. :) >=20 > The driver as it stands does the following: > * Installs the applicable linux libraries, and ATI programs to your=20 > linux_base. > * Compiles and installs the following ATI programs (For FreeBSD):=20 > fgl_glxgears, fglrx_gamma, and the ATI control panel. > * Installs the X11 drivers and libraries. (Linux builds, but work fine u= nder=20 > FreeBSD) > * Supports full 2D acceleration, including accelerated XVideo. > * Supports TV out and MultiHead. > * Does NOT support 3D acceleration, or build the kernel module. >=20 > I have tested the driver with an ATI Radeon 9800LE, and it seems to work = great=20 > for desktop, non-gaming use. (Playing video, running KDE, etc) >=20 > I am currently working on the kernel module portion of the project. >=20 > The X side of the driver is ready and waiting for a DRM device to plug in= to.=20 >=20 > The current hurdles are working with the ATI team to get rid of any=20 > show-stopping linux specifics in the closed-source static libraries which= I=20 > have to link my kernel module to. >=20 > If there is significant intrest in the project's current state, (without = 3D) I=20 > will make a proper port and submit it. >=20 > If there are any problems please let me know and I will do my best to fix= them=20 > ASAP! >=20 Great work, thanks! The driver works fine when I'm only my notebook display with no external monitor connected. When I'm using the same config file as above (one screen) but with an external monitor connected, X and the WM load, but when I start to move my mouse, it crashes. Works with the radeon driver. Config and X log: http://people.freebsd.org/~brueffer/xerrors/xorg.conf http://people.freebsd.org/~brueffer/xerrors/Xorg.0.log I also have problems with dual-head configurations. If I configure dual or clone setups using 'Option DesktopSetup', X starts to load, but crashed shortly after and both the notebook display and the external monitor stay black. The log just says the following and is the same as the one above otherwise: Fatal server error: Caught signal 11. Server aborting Is this a known problem? Thanks, - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --UlVJffcvxoiEqYs2 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvY+mbHYXjKDtmC0RArRlAKD5WxoiRKH92rXiTAZP+U+xOVcuZwCfYeLa p4T3THo4V23WhyzB9NP8X00= =PZ6Q -----END PGP SIGNATURE----- --UlVJffcvxoiEqYs2-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 21:39:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9447D16A41F for ; Thu, 5 Jan 2006 21:39:52 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B83A443D5C for ; Thu, 5 Jan 2006 21:39:51 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k05Ldopb050313; Thu, 5 Jan 2006 15:39:50 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43BD9212.40807@centtech.com> Date: Thu, 05 Jan 2006 15:39:30 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nicolas Blais References: <200601051613.27718.nb_root@videotron.ca> In-Reply-To: <200601051613.27718.nb_root@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1230/Thu Jan 5 05:49:56 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: linux-flashplugin-6.0 not working anymore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 21:39:52 -0000 Nicolas Blais wrote: >A while ago I noticed that firefox and konqueror are not displaying flash >applets anymore on my -CURRENT system yet it works fine on all my 6-STABLE >machines. > >When I run firefox from the shell, I get: >[nicblais@clk01a] ~> firefox >LoadPlugin: failed to initialize shared >library /usr/X11R6/lib/linux-flashplugin6/libflashplayer.so >[/usr/local/lib/pluginwrapper/flash6.so: version GLIBC_2.1 required >by /usr/X11R6/lib/linux-flashplugin6/libflashplayer.so not defined] > >(I have linux-glib2-2.4.8_1 installed) > >My libmap.conf is untouched : ># Flash6 with Mozilla/Firebird/Galeon/Epiphany/Konqueror/Kazehakase >[/usr/X11R6/lib/linux-flashplugin6/libflashplayer.so] >libpthread.so.0 pluginwrapper/flash6.so >libdl.so.2 pluginwrapper/flash6.so >libz.so.1 libz.so.3 >libstdc++-libc6.2-2.so.3 libstdc++.so.5 >libm.so.6 libm.so.4 >libc.so.6 pluginwrapper/flash6.so > >And konqueror no longer finds my linux-flashplugin-6.0. The mplayer plugin is >detected fine in both browsers. Since the linuxpluginwrapper port is broken >for -CURRENT, I haven't tried to mess with it. > >Am I the only one with this problem? > > No - I too have this problem, and can't find a solution. It broke with some commits back around Dec 20th, 2005 from Alexander Kabaev I think. I mentioned it, and his response was something like: - The segfault was caused by *((char *)0) = 0; statement that I forgot to remove from the source before committing. Now firefox does not segfault but properly fails to load plugin due to inadequate versioning emulation by flash[67].so wrappers. - See the thread with a subject of: [openoffice]no suitable windowing system found, exiting. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 21:57:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36FB816A420 for ; Thu, 5 Jan 2006 21:57:10 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A69D43D58 for ; Thu, 5 Jan 2006 21:57:08 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR003.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0ISN00AHR3N5A7I0@VL-MO-MR003.ip.videotron.ca> for freebsd-current@freebsd.org; Thu, 05 Jan 2006 16:57:05 -0500 (EST) Date: Thu, 05 Jan 2006 16:56:55 -0500 From: Nicolas Blais In-reply-to: <43BD9212.40807@centtech.com> To: freebsd-current@freebsd.org Message-id: <200601051657.04796.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart4030499.3zRpiJDubr; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601051613.27718.nb_root@videotron.ca> <43BD9212.40807@centtech.com> User-Agent: KMail/1.8.3 Cc: Eric Anderson Subject: Re: linux-flashplugin-6.0 not working anymore X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 21:57:10 -0000 --nextPart4030499.3zRpiJDubr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > >And konqueror no longer finds my linux-flashplugin-6.0. The mplayer plug= in > > is detected fine in both browsers. Since the linuxpluginwrapper port is > > broken for -CURRENT, I haven't tried to mess with it. > > > >Am I the only one with this problem? > > No - I too have this problem, and can't find a solution. It broke with > some commits back around Dec 20th, 2005 from Alexander Kabaev I think. > I mentioned it, and his response was something like: > > - > The segfault was caused by *((char *)0) =3D 0; statement that I forgot to > remove from the source before committing. Now firefox does not segfault > but properly fails to load plugin due to inadequate versioning > emulation by flash[67].so wrappers. > - > > See the thread with a subject of: > [openoffice]no suitable windowing system found, exiting. > > Eric Good, I feel better knowing I didn't fubar'ed my -CURRENT box. (Now I'll go back to trying to get xorg-server-snap to not blow up with my = ATI=20 9550, ah the joy of living on the edge...) Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #9: Sat Dec 31 14:24:32 EST 2005 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart4030499.3zRpiJDubr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvZYw4wTBlvcsbJURAmnwAKDEahC5sGVnAN3qs9iaoGcHg8V79wCfYhlh 06HrY6z+yD96XVHHBCciaG0= =1ZCi -----END PGP SIGNATURE----- --nextPart4030499.3zRpiJDubr-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 21:59:33 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE5716A422 for ; Thu, 5 Jan 2006 21:59:33 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 252AD43D90 for ; Thu, 5 Jan 2006 21:59:05 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5376387 for multiple; Thu, 05 Jan 2006 17:00:23 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k05LwqTk018928; Thu, 5 Jan 2006 16:58:53 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Ted Faber Date: Thu, 5 Jan 2006 16:59:39 -0500 User-Agent: KMail/1.8.2 References: <20060103233406.GA1564@hut.isi.edu> <200601041700.14244.jhb@freebsd.org> <20060104224805.GA1191@hut.isi.edu> In-Reply-To: <20060104224805.GA1191@hut.isi.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200601051659.40514.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1230/Thu Jan 5 06:49:56 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 21:59:33 -0000 On Wednesday 04 January 2006 05:48 pm, Ted Faber wrote: > On Wed, Jan 04, 2006 at 05:00:13PM -0500, John Baldwin wrote: > > Ok, use the workaround other folks have posted for now. Hack vga_pci.c > > to always add the "agp" device in its attach routine instead of checking > > for PCIY_AGP. > > FYI, this worked just fine. > > I see that a few people are having problems with this. Is there any > interest in adding a tunable to force the agp device into existence? > I'd be happy to whip up a patch. The real fix is to change the various agp drivers to use identify routines to create the agp devices off of hostb and vgapci devices themselves and stop creating the devices in the hostb and vgapci attach routines. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 22:42:44 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9163816A41F for ; Thu, 5 Jan 2006 22:42:44 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5F9F43D66 for ; Thu, 5 Jan 2006 22:42:39 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id E41C572DD9; Thu, 5 Jan 2006 14:42:37 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id E1A3E72DD4; Thu, 5 Jan 2006 14:42:37 -0800 (PST) Date: Thu, 5 Jan 2006 14:42:37 -0800 (PST) From: Doug White To: Andrea Brancatelli In-Reply-To: <200512291052.00546.andrea@brancatelli.it> Message-ID: <20060105142139.W58957@carver.gumbysoft.com> References: <200512291052.00546.andrea@brancatelli.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-current@freebsd.org Subject: Re: IBM Blade Center - FreeBSD on HS20 type MTM 8832/N1X X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 22:42:44 -0000 Sorry for joining the thread late, but I'm an expert on this hardware. :-) Note that the IBM BladeCenter HS series is identical to the Intel SBCE series blades; you might find more info looking for SBCE info since they're widely sold by whitebox resellers. I've also had the (mis)fortune of working with these extensively and know their quirks inside and out. On Thu, 29 Dec 2005, Andrea Brancatelli wrote: > Here's the symptoms... when booting from CD the CD boots regulary, then > the "searching for Kernel" part comes in, the whirl starts spinning and > everything stop. I mean, it doesn't stop, it keeps spinning and spinning > and spinning and spinning, but without doing anything. If I take the CD > out of the drive it returns and error complaining it can't find the > Kernel and asking me where it should look for it. The USB CDROM is very, very, VERY slow. As recommended later in the thread, installing via PXE is highly recommended. http://people.freebsd.org/~dwhite/pxeboot.html has a quick and dirty framework for getting sysinstall up over PXE. > It's a dual xeon machine with 4gb of ram, 2 internal (S-ATA) drives > (40gb each), one (possibily deactivable) internal Raid controller > (deactivating this may be a good try, since Debiand refuses to see the > drive as well with this turned on), a SCSI cdrom and a SCSI floppy > drive. The older HS20s and the Intel SBXL52 are 2xPATA and the floppy/cdrom/front usb socket are connected by usb via the switchable media tray. They are probably showing up as "SCSI" to Linux since, like FreeBSD, USB media uses the SCSI subsystem. The SBX82 uses 2.5" SCSI disks, but also supports hyperthreading. Your 8832-N1X appears to be what Intel calls an SBX82, based on the supported CPUs and the use of SCSI disks. The onboard RAID is provided by the mpt integrated mirroring feature and is supported on FreeBSD 6.0 and later. > I don't have any fiber optic channel so the SAN/multipath and everything > else is not an issue. The keyboard is a PS/2 one, so the USB keyboard > isn't an issue as well (I'm writing this because I did some digging in > the archives for similar problems). You will run into the infamous FreeBSD single keyboard quirk. Syscons will only listen to one keyboard at a time, and by default its the first one discovered ("kbd0"). Since these blades do not have atkbd keyboard controllers, usually the USB device that provides input from the Remote Console in the MM is the one that gets grabbed. Under certain circumstances you can get the system to grab a keyboard plugged into the front-panel USB port. The PS/2 ports on the MM will never ever become the console unless you explicity select them using kbdcontrol. Hopefully kbdmux will become the default in a later release and this sillyness will cease, but for now you need to be aware of what keyboard is the active one. At least it tends to default to the Remote Console so you can access stuff remotely. For the record the SAN cards are Qlogic (QLA2310) and are fully supported by the isp driver. I even had freebsd talking to an Xserve RAID via a Brocade switch module before the switch committed suicide (firmware image corrupted or something). I know a bunch of other stuff about these that might be useful. Drop me a message if you get stuck and I'll help you out. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 23:00:54 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BB7716A41F; Thu, 5 Jan 2006 23:00:54 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B43E43D64; Thu, 5 Jan 2006 23:00:53 +0000 (GMT) (envelope-from faber@ISI.EDU) Received: from hut.isi.edu (hut.isi.edu [128.9.168.160]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id k05N0Pi16877; Thu, 5 Jan 2006 15:00:25 -0800 (PST) Received: (from faber@localhost) by hut.isi.edu (8.13.4/8.13.4/Submit) id k05N0Pku017500; Thu, 5 Jan 2006 15:00:25 -0800 (PST) (envelope-from faber) Date: Thu, 5 Jan 2006 15:00:24 -0800 From: Ted Faber To: John Baldwin Message-ID: <20060105230024.GB12969@hut.isi.edu> References: <20060103233406.GA1564@hut.isi.edu> <200601041700.14244.jhb@freebsd.org> <20060104224805.GA1191@hut.isi.edu> <200601051659.40514.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="neYutvxvOLaeuPCA" Content-Disposition: inline In-Reply-To: <200601051659.40514.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i X-url: http://www.isi.edu/~faber X-ISI-4-43-8-MailScanner: Found to be clean X-MailScanner-From: faber@hut.isi.edu Cc: freebsd-current@freebsd.org Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 23:00:54 -0000 --neYutvxvOLaeuPCA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 05, 2006 at 04:59:39PM -0500, John Baldwin wrote: > On Wednesday 04 January 2006 05:48 pm, Ted Faber wrote: > > On Wed, Jan 04, 2006 at 05:00:13PM -0500, John Baldwin wrote: > > > Ok, use the workaround other folks have posted for now. Hack vga_pci= .c > > > to always add the "agp" device in its attach routine instead of check= ing > > > for PCIY_AGP. > > > > FYI, this worked just fine. > > > > I see that a few people are having problems with this. Is there any > > interest in adding a tunable to force the agp device into existence? > > I'd be happy to whip up a patch. >=20 > The real fix is to change the various agp drivers to use identify routine= s to=20 > create the agp devices off of hostb and vgapci devices themselves and sto= p=20 > creating the devices in the hostb and vgapci attach routines. I understand. I have time and knowledge to apply the band-aid, but not to do the surgery. :-) If you think someone would be interested enough to commit the band-aid, I'll happily do the legwork. --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --neYutvxvOLaeuPCA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvaUIaUz3f+Zf+XsRAkyHAJ0aG27EjM0iYeNPc4vF1JzU9kQsEACeOxAk t/JtA/TEYoV00Ivtlu/oW2Y= =os2w -----END PGP SIGNATURE----- --neYutvxvOLaeuPCA-- From owner-freebsd-current@FreeBSD.ORG Thu Jan 5 23:03:34 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C7F816A41F for ; Thu, 5 Jan 2006 23:03:34 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EA043D45 for ; Thu, 5 Jan 2006 23:03:33 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id DFE7472DD4; Thu, 5 Jan 2006 15:03:33 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id DAC0872DCB; Thu, 5 Jan 2006 15:03:33 -0800 (PST) Date: Thu, 5 Jan 2006 15:03:33 -0800 (PST) From: Doug White To: Andrea Brancatelli In-Reply-To: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> Message-ID: <20060105145731.F58957@carver.gumbysoft.com> References: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: current@freebsd.org Subject: Re: The BladeCenter Saga -> bge driver not behaving properly... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jan 2006 23:03:34 -0000 On Thu, 5 Jan 2006, Andrea Brancatelli wrote: > Sorry for breaking the thread and posting a new message instead of replying > but I'm having some problems with my mailserver. > > I did a few screenshots of the problems we are having with the Broadcom lan > card and the bge driver... I cannot paste text because I cannot access the > machine in SSH (since it's not working...) You need to compile your kernel with options BGE_FAKE_AUTONEG This option is available on RELENG_5 after 5.4 only .. 5.4-RELEASE itself should work due to my attempts to sabotage other blade vendors' products. Our driver does not handle autonegotation for the blades correctly. Its a quirk of their implementation (not uncommon, don't forget we're talking about IBM here). Also note that dhclient in 6.x will not work correctly since the link status it not updated until the interface is up'd. If you want to use DHCP create /etc/start_if.bge0 with: ifconfig bge0 up dhclient bge0 in it and that should get dhclient working properly. Also, if you haven't used these blades much, the external switch ports default to disabled, so you may need to go into the MM and enable the external ports on the ethernet switch i/o modules. You might find the kernel config at http://people.freebsd.org/~dwhite/BLADE useful. Thats the config I use for the Intel blades. I can make a device.hints available too if that would be useful for you. You will also find that the blades will not reboot correctly. You will have to reset them from the MM after halting them from FreeBSD. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 00:50:19 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3E62916A41F; Fri, 6 Jan 2006 00:50:19 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F90543D45; Fri, 6 Jan 2006 00:50:17 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k060oEp4015334 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 6 Jan 2006 11:20:16 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jo Rhett Date: Fri, 6 Jan 2006 11:20:13 +1030 User-Agent: KMail/1.8.3 References: <43A266E5.3080103@samsco.org> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> In-Reply-To: <20060105092448.GH1358@svcolo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1266678.4ed0llI9s7"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601061120.14707.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED,SUBJECT_EXCESS_QP X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 ) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 00:50:19 -0000 --nextPart1266678.4ed0llI9s7 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline [cross post to -current removed] On Thu, 5 Jan 2006 19:54, Jo Rhett wrote: > On Fri, Dec 23, 2005 at 11:36:11AM +1030, Daniel O'Connor wrote: > > On each 'client' PC.. > > NFS mount /usr/src and /usr/obj > > installkernel > > reboot > > installworld > > Works fine on home computers behind firewalls. > > Useless on public servers that don't run RPC. > Useless on flash-based servers where minimizing writes is necessary. > (mergemaster does far far far too many writes) =46or NFS mount, read: any network file system. You can also use, say IPSEC= to=20 protect the NFS packets (although I'm not claiming it's a trivial thing to= =20 set up..) As for restricting the number of writes - that is a totally separate issue = and=20 isn't very relevant to this discussion. > > You are putting words in the mouth of core@ - > > Sorry. As said before, the topic is always struck down and nobody from > core has ever stood up to say "we'll support this". I don't know whose on > core this week, nor will I at any given time. I just know that core has > either struck it down or been Silent. In general core IS silent. Core isn't some governing body that decides what happens in FreeBSD and pla= ns=20 in detail what happens. You are showing a fundamental misunderstanding abou= t=20 how FreeBSD "works". Also, you just said "... the topic is always struck down ..." - what do you= =20 mean? Are you claiming someone from (or claiming to be from core) said "Don= 't=20 do this, we won't allow it"? If so, can you supply proof? > A good binary update mechanism shouldn't be just the network. Updates fr= om > flash devices, ISO images, etc should all work much the same way. Absolutely. In fact you could put /usr/src and /usr/obj on a CD/DVD/Flash drive and=20 upgrade that way. I would *welcome* a more sophisticated method for binary upgrades that was = a=20 lot smarter. I imagine pretty much everyone else would too. > > Unless you mean "core@ said they would not support packaging the base" > > which is different. > > People have clearly identified the problems that prevent a useful binary > update mechanism from working, and what they need from core. Some have > asked for core packages, others have other ideas, and some have said > "anything that gives me versioning ability" and and..? Anyway, so what? Nothing stops you writing such a system, and I contend it= =20 isn't necessary to version the base system, or package it specially to do=20 binary upgrades. Something similar to freebsd-update could do it. > > This is not true - I don't see it as being mandatory to be able to apply > > binary updates. (Case in point - freebsd-update works fine without it) > > freebsd-update works "fine" if you run GENERIC with no build options. > Back to "useful for home computers". So, uhh, how would your magical binary upgrade system handle custom kernels? Why would it be any different? You still haven't explained how this would=20 work.. > freebsd-update is hampered by the exact problems I'm listing here. > Difficulty determining "what I have", no method to store "what I did" and > no effective backout mechanism to speak of. Then feel free to expand on it. This IS an open source project - you can see how everything is written, if = you=20 want to improve it > Nobody that I know cares whether or not the solution manifests as core os > packages, but some sort of core versioning ability has to be developed and > supported by the core. I don't think core is really very relevant here - core is there to mostly=20 settle disputes. The way forward is to achieve consensus and have working=20 solutions. If you supply a working framework then I think you'll find a lot of support= =20 materialises. The problem is when you are just proposing vapourware solutio= ns=20 everyone steps in and wants it done their way. Code speaks louder than words :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1266678.4ed0llI9s7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvb7G5ZPcIHs/zowRAnY0AJ9Ny5aDvmRhRlYzB9iVANDTHK0IbACfdG9f 8VJRrdpxZqqee85xpei2O3Y= =oKH9 -----END PGP SIGNATURE----- --nextPart1266678.4ed0llI9s7-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 01:55:50 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3901016A41F for ; Fri, 6 Jan 2006 01:55:50 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from msgmmp-2.gci.net (msgmmp-2.gci.net [209.165.130.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id D8D3D43D48 for ; Fri, 6 Jan 2006 01:55:49 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from stargate.akparadise.com ([209.124.141.64]) by msgmmp-2.gci.net (Sun Java System Messaging Server 6.2-3.03 (built Jun 27 2005)) with ESMTPA id <0ISN00DLCENDP790@msgmmp-2.gci.net> for freebsd-current@freebsd.org; Thu, 05 Jan 2006 16:54:52 -0900 (AKST) Received: by stargate.akparadise.com (Postfix, from userid 0) id 27ADD3FAF; Thu, 05 Jan 2006 16:54:47 -0900 (AKST) Date: Thu, 05 Jan 2006 16:54:34 -0900 From: Beech Rintoul To: freebsd-current@freebsd.org Message-id: <200601051654.46420.akbeech@gmail.com> Organization: NorthWind Communications MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1275097.WV2EIj8eiE; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.8.3 Subject: libjpeg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 01:55:50 -0000 --nextPart1275097.WV2EIj8eiE Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I'm trying to compile a program from source that needs libjpeg6b. I have=20 searched and can't find it . I have jpeg6b installed. Can someone point me = to=20 the correct path? Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - System Administrator - akbeech@gmail.com /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://akparadise.byethost33.com =2D------------------------------------------------------------------------= =2D------------- --nextPart1275097.WV2EIj8eiE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvc3mVq19LUoGB+MRAhqWAJ99EL8zVVJuiAzVbYyWdgbOKPVZggCggRis KqlZ9Zit0tERWBdvZ8mxuYM= =g4aK -----END PGP SIGNATURE----- --nextPart1275097.WV2EIj8eiE-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 02:39:37 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5159816A41F for ; Fri, 6 Jan 2006 02:39:37 +0000 (GMT) (envelope-from dcornejo@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB98343D46 for ; Fri, 6 Jan 2006 02:39:36 +0000 (GMT) (envelope-from dcornejo@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so3350591nzo for ; Thu, 05 Jan 2006 18:39:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=EzTDFhrihorAO1lnVr+b1i7DuyeLbvq6xCMN+sU+OAEgXr8s08QcQ4ICvYsIohblbgF8ajfTQJDyQ1KCGiZ1jZm4D3XA6O1t2LmxSNxWpZ56CGsm0hwOcBpW240J1YPoKbcMCZqH4Mk1ccvSWLP9M9guLV/ognN+5B8TaSvybXk= Received: by 10.36.2.19 with SMTP id 19mr7698396nzb; Thu, 05 Jan 2006 18:39:35 -0800 (PST) Received: by 10.36.140.18 with HTTP; Thu, 5 Jan 2006 18:39:35 -0800 (PST) Message-ID: <6b8e8f4f0601051839j7342ad57j950598c3ac56b65e@mail.gmail.com> Date: Thu, 5 Jan 2006 16:39:35 -1000 From: spoggle To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: cardbus compilation failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 02:39:37 -0000 I recently updated four of my machines to the latest current and am having problems getting the kernel to build: cc -c -O -pipe -march=3Dpentium3 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=3Dc99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-growth=3D100 --param large-function-growth=3D1000 -mno-align-long-strings -mpreferred-stack-boundary=3D2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/dev/cardbus/cardbus.c /usr/src/sys/dev/cardbus/cardbus.c: In function `cardbus_alloc_resources': /usr/src/sys/dev/cardbus/cardbus.c:187: warning: implicit declaration of function `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: nested extern declaration of `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:208: warning: nested extern declaration of `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: redundant redeclaration of 'BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: previous implicit declaration of 'BARBIT' was here /usr/src/sys/dev/cardbus/cardbus.c:243: warning: nested extern declaration of `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: redundant redeclaration of 'BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: previous implicit declaration of 'BARBIT' was here /usr/src/sys/dev/cardbus/cardbus.c:263: warning: nested extern declaration of `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: redundant redeclaration of 'BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: previous implicit declaration of 'BARBIT' was here /usr/src/sys/dev/cardbus/cardbus.c:299: warning: nested extern declaration of `BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: redundant redeclaration of 'BARBIT' /usr/src/sys/dev/cardbus/cardbus.c:187: warning: previous implicit declaration of 'BARBIT' was here *** Error code 1 Stop in /u0/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. I've cvsup'ed a couple of times, and rebuilt and installed world, removed /usr/obj/* and still get this problem. I notice that it affected tinderbox on 12/29 & 30, but I find no discussion of it - I guess it was resolved 12/31 or later - can someone tell me what I may be doing wrong? (I did google it and searched my current mail for mentions of BARBIT, finding only the tinderbox failures) thanks, dave c From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 03:24:04 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27C6C16A41F for ; Fri, 6 Jan 2006 03:24:04 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3DD643D58 for ; Fri, 6 Jan 2006 03:24:02 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so2141020wxc for ; Thu, 05 Jan 2006 19:24:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=jmk+ODjk8kOeBh2l/3gWBrSuIov0CvuiD0vbDv1KbHI226uYfiGRWlJ57PvhFP4olravuBGuAbMGEUsBuHUsPUg13nupeEyDAuNT2eKM2qqe8ZoSwRKbAf1fF2D5nfi/G/XbMxOGxnaH/WtGRXxt7CDV71UCTx407fU7el7eELc= Received: by 10.70.54.3 with SMTP id c3mr2825546wxa; Thu, 05 Jan 2006 19:24:01 -0800 (PST) Received: by 10.70.105.2 with HTTP; Thu, 5 Jan 2006 19:24:01 -0800 (PST) Message-ID: <84dead720601051924v55cad2bv7685a7f87a3e50a1@mail.gmail.com> Date: Fri, 6 Jan 2006 08:54:01 +0530 From: Joseph Koshy To: jrhett@svcolo.com In-Reply-To: <20060105233226.GC17890@soaustin.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <20060105092448.GH1358@svcolo.com> <20060105184147.GD69162@funkthat.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105233226.GC17890@soaustin.net> Cc: Mark Linimon , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 03:24:04 -0000 ml> (And, as well, that you do not even understand the role the core plays ml> in the project. Hint: it is not primarily technical in nature.) For those curious to know how the project works, the following online resources may help: A project model for the FreeBSD Project http://www.freebsd.org/doc/en_US.ISO8859-1/books/dev-model/index.html The FreeBSD development process: a case study http://www.cs.colostate.edu/puml/pub/FreeBSD_TSEVersion.pdf The FreeBSD Committers Guide http://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 04:07:11 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36CFA16A41F for ; Fri, 6 Jan 2006 04:07:11 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76BCD43D45 for ; Fri, 6 Jan 2006 04:07:10 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k06478a5026135 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 6 Jan 2006 15:07:08 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k06477Hh051283; Fri, 6 Jan 2006 15:07:07 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k06477j9051282; Fri, 6 Jan 2006 15:07:07 +1100 (EST) (envelope-from pjeremy) Date: Fri, 6 Jan 2006 15:07:07 +1100 From: Peter Jeremy To: Beech Rintoul Message-ID: <20060106040707.GR42228@cirb503493.alcatel.com.au> References: <200601051654.46420.akbeech@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200601051654.46420.akbeech@gmail.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: libjpeg X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 04:07:11 -0000 On Thu, 2006-Jan-05 16:54:34 -0900, Beech Rintoul wrote: >I'm trying to compile a program from source that needs libjpeg6b. I have >searched and can't find it . I have jpeg6b installed. Can someone point me to >the correct path? I presume you mean you have jpeg-6b installed. I don't know of any libjpeg6b library. jpeg-6b installs libjpeg.{a,so,so.9}. server% /usr/sbin/pkg_info -L jpeg-6b_3 | grep libjpeg /usr/local/lib/libjpeg.a /usr/local/lib/libjpeg.so /usr/local/lib/libjpeg.so.9 /usr/local/share/doc/jpeg/libjpeg.doc server% Peter From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 05:21:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D61A16A41F; Fri, 6 Jan 2006 05:21:29 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: from ox.eicat.ca (ox.eicat.ca [66.96.30.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id C841343D46; Fri, 6 Jan 2006 05:21:28 +0000 (GMT) (envelope-from dgilbert@daveg.ca) Received: by ox.eicat.ca (Postfix, from userid 66) id C9C0311B4E; Fri, 6 Jan 2006 00:21:27 -0500 (EST) Received: by canoe.dclg.ca (Postfix, from userid 101) id D05EC1A0A96; Fri, 6 Jan 2006 00:21:19 -0500 (EST) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17341.65102.980006.14057@canoe.dclg.ca> Date: Fri, 6 Jan 2006 00:21:18 -0500 To: freebsd-current@freebsd.org, freebsd-usb@freebsd.org X-Mailer: VM 7.17 under 21.4 (patch 18) "Social Property" XEmacs Lucid Cc: Subject: Disappearing memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 05:21:29 -0000 For some time, my answer to disappearing memory has been to always unplug the USB device before removing (or inserting different) memory cards. The issue is that they seem to not signal the USB infrastructure that they have been ejected, and thus the operating system doesn't know. In fact, most "x in 1" card readers --- ones that read many types of memory --- actually attach a bunch of disks with zero blocks in addition to attaching the memory card you have inserted --- as if they have the capability of simutaneously handling all different kinds of memory (although they often don't). So this seems like an acceptable solution. Until now. Now that I have a Dell 2405 flat panel display on my desk (gorgeous, BTW), I have a permanently attached cluster of memory card slots. Sure ... I can grope around behind things, find the usb cord for the monitor, but that's very ungraceful and ends up unplugging any other USB devices that go through the monitor (thus causing all kinds of trouble). So I set about tonight to see if I could convince camcontrol to realize that one of the previously full disks was now empty again. It doesn't seem that I can. Maybe what we need is 'usbcontrol' ... allowing us to reset (or at least reset the OSs idea of) one usb device. Dave. -- ============================================================================ |David Gilbert, Independent Contractor. | Two things can be | |Mail: dave@daveg.ca | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 05:58:35 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4BFA16A422 for ; Fri, 6 Jan 2006 05:58:35 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B5A843D55 for ; Fri, 6 Jan 2006 05:58:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.21]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k065vtGg037738 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 6 Jan 2006 16:28:00 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "M. Warner Losh" Date: Fri, 6 Jan 2006 16:27:52 +1030 User-Agent: KMail/1.8.3 References: <200510132028.32070.doconnor@gsoft.com.au> <20051013.213621.35849592.imp@bsdimp.com> <200510141444.21457.doconnor@gsoft.com.au> In-Reply-To: <200510141444.21457.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1229756.77kpKj5cRa"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601061627.53743.doconnor@gsoft.com.au> X-Spam-Score: -1.36 () ALL_TRUSTED X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-current@freebsd.org Subject: Re: Patches for ports to install KLD source X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 05:58:35 -0000 --nextPart1229756.77kpKj5cRa Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 14 Oct 2005 14:44, Daniel O'Connor wrote: > On Fri, 14 Oct 2005 13:06, M. Warner Losh wrote: > > : For the nvidia port - I've only tried it on -current so I don't know = if > > : it will work OK with the other versions it installs on different > > : systems/configurations. > > > > How is this different than setting PORTS_MODULES in your kernel config > > file? > > PORTS_MODULES will upgrade your port if your ports tree is updated, this > can be a nasty suprise. nvidia-driver 6113 used to be the latest version = of > the port that would work on my laptop and an automatic upgrade would have > been very frustrating - ie I think it's a POLA violation. > > It makes building your kernel slower - it installs everything related to > the port instead of just rebuilding the KLD. For most people this probably > isn't a big issue but it's a drag when you are testing new kernels. > > It also seems a bit less of a "big hammer" approach to the problem :) So.. Any chance you think it's worth committing? :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1229756.77kpKj5cRa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvgbh5ZPcIHs/zowRAkzaAJ95mQSRzF/X+vxJxY8p8UYjow29nACdG4UU q05lp7wzsz03cBLPYYJjYGo= =eTer -----END PGP SIGNATURE----- --nextPart1229756.77kpKj5cRa-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 06:05:47 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AE7BB16A41F; Fri, 6 Jan 2006 06:05:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3051043D48; Fri, 6 Jan 2006 06:05:47 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k0662sfl001050; Thu, 5 Jan 2006 23:02:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 05 Jan 2006 23:02:53 -0700 (MST) Message-Id: <20060105.230253.93225432.imp@bsdimp.com> To: dgilbert@dclg.ca From: "M. Warner Losh" In-Reply-To: <17341.65102.980006.14057@canoe.dclg.ca> References: <17341.65102.980006.14057@canoe.dclg.ca> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Thu, 05 Jan 2006 23:02:55 -0700 (MST) Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org Subject: Re: Disappearing memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 06:05:47 -0000 In message: <17341.65102.980006.14057@canoe.dclg.ca> David Gilbert writes: : Maybe what we need is 'usbcontrol' ... allowing us to reset (or at : least reset the OSs idea of) one usb device. I've wanted a generic way to send messages to busses about children and to devices. PC Card and CardBus could use that for power down as well.. Warner From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 06:36:25 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30E2916A41F for ; Fri, 6 Jan 2006 06:36:25 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B59F143D49 for ; Fri, 6 Jan 2006 06:36:24 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id k066aO0K079018; Thu, 5 Jan 2006 22:36:24 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id k066aNYn079015; Thu, 5 Jan 2006 22:36:23 -0800 (PST) Date: Thu, 5 Jan 2006 22:36:23 -0800 (PST) From: Matthew Dillon Message-Id: <200601060636.k066aNYn079015@apollo.backplane.com> To: Chuck Swiger References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> Cc: Luigi Rizzo , Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 06:36:25 -0000 :Luigi Rizzo wrote: :> On Sun, Jan 01, 2006 at 10:59:14AM +0100, Poul-Henning Kamp wrote: :>>http://phk.freebsd.dk/misc/leapsecond.txt :>> :>>Notice how CLOCK_REALTIME recycles the 1136073599 second. :> :> on a related topic, any comments on this one ? :> Is this code that we could use ? :> :> http://www.dragonflybsd.org/docs/nanosleep/ : :I ported the tvtohz change from Dragonfly back to 4.10 and 5-STABLE here: : :http://www.pkix.net/~chuck/timer/ : :...so anyone who wants to experiment can try it out. :-) : :-- :-Chuck It isn't so much tvtohz that's the issue, but the fact that the nanosleep() system call has really coarse hz-based resolution. That's been fixed in DragonFly and I would recommend that it be fixed in FreeBSD too. After all, there isn't much of a point having a system call called 'nanosleep' whos time resolution is coarse-grained and non-deterministic from computer to computer (based on how hz was configured). Since you seem to be depending on fine-resolution timers more and more in recent kernels, you should consider porting our SYSTIMER API to virtualize one-shot and periodic-timers. Look at kern/kern_systimer.c in the DragonFly source. The code is fairly well abstracted, operates on a per-cpu basis, and even though you don't have generic IPI messaging I think you could port it without too much trouble. If you port it and start using it you will quickly find that you can't live without it. e.g. take a look at how we implement network POLLING for an example of its use. The polling rate can be set to anything at any time, regardless of 'hz'. Same goes for interrupt rate limiting, various scheduler timers, and a number of other things. All the things that should be divorced from 'hz' have been. For people worried about edge conditions due to multiple unsynchronized timers going off I will note that its never been an issue for us, and in anycase it's fairly trivial to adjust the systimer code to synchronize periodic time bases which run at integer multiples to timeout at the same time. Most periodic time bases tend to operate in this fashion (the stat clock being the only notable exception) so full efficiency can be retained. But, as I said, I've actually done that and not noticed any significant improvement in performance so I just don't bother right now. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 08:18:41 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05FA416A41F for ; Fri, 6 Jan 2006 08:18:41 +0000 (GMT) (envelope-from brian@aljex.com) Received: from s1tank.virtdom.com (s1tank.virtdom.com [216.240.101.50]) by mx1.FreeBSD.org (Postfix) with SMTP id 6DA3443D45 for ; Fri, 6 Jan 2006 08:18:40 +0000 (GMT) (envelope-from brian@aljex.com) Received: (qmail 88048 invoked by uid 89); 6 Jan 2006 08:53:10 -0000 Received: from ool-4355e580.dyn.optonline.net (HELO venti) (brian@aljex.com@67.85.229.128) by s1tank.virtdom.com with SMTP; 6 Jan 2006 08:53:10 -0000 Message-ID: <007e01c61299$cb158800$951fa8c0@venti> From: "Brian K. White" To: References: <20060104104521.463FA16A420@hub.freebsd.org> Date: Fri, 6 Jan 2006 03:18:37 -0500 Organization: Aljex Software MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2670 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 Subject: Re: usb mouse support update plans X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 08:18:41 -0000 ----- Original Message ----- From: "Bill Paul" To: "Brian K. White" Cc: Sent: Wednesday, January 04, 2006 5:45 AM Subject: Re: usb mouse support update plans >> >> > On Tuesday 03 January 2006 17:23, Jordan Sissel wrote: >> >> On my grande circuit of trying to make mouse support better for >> >> FreeBSD, >> >> I've finally come about to working on usb mice. I've done a bit of >> >> research about usb hid, and I need some feedback on where I should >> >> take >> >> usb mouse support. >> >> >> > >> > Oh, good! :) >> > >> >> Moral of this story is that I want to make known-broken mice work with >> >> FreeBSD. This includes *several* Microsoft USB models, many ps/2 mice >> >> (including usb->ps2 adapted mice), and probably others. >> >> >> > >> >> >> >> How can you help? If you are having issues with mouse support in >> >> FreeBSD I need to know the following: >> >> - Mouse model and brand (as specific as possible would help) >> >> - Symptoms of strange behavior >> >> - Environment (moused+ums? plain ums in X? plain psm in X? moused >> >> with serial mice?) >> > >> > Check usb/77604 for some mice known to have problems and for a fix for >> > them. >> >> Indeed "Oh Good!" >> >> I would soooo love to ditch the hacked knoppix-4 I'm currently net >> booting >> and nfs mounting to run on my thin client. (I guess a nfs mounted full >> dvd >> version of knoppix-4.0 with 4 more gigs of room to grow besides would >> have >> to be a fat client) > > Would it be too much trouble for you to describe your system in a bit > more depth? "Thin client" is... well, not very helpful. Don't let "thin client" imply strange hardware. It's not very special hardware other than small form factor and low power dissipation. Normal x86 platform. It's this board from intel: http://www.mini-itx.com/news/17911903/ I was not able to find any real docs about it on the net and I got it used on ebay without docs. It came with a plain unmarked cd-r driver disk which provides basic clues but everything was already supported out of the box in freebsd anyways. Here is the last kernel config I had used on it. Note this appears to reflect a test in progress. atkbdc, atkbdc and psm are commented out and ukbd & ums are built-in. Looks like the generic kernel would run fine on it as all I did was remove unused nic and disk controllers and build in snd_ich. http://keyofr.homeunix.net:81/netgear_hub_thin_client/HUBPC (dmesg provided below) And build it with this make command: make CPUTYPE=pentium3m KERNCONF=HUBPC DESTDIR=/pxe buildkernel Which by the way I want to say to whoever cares, I think is exceedingly cool to be able to build a target system from a host systems source tree by doing just that. Note /pxe is a fs mount point for the sake of the nfs share, and since I didn't want to carve up my disk or be locked into any particular size, it's a file backed ramdisk. >> The only reason I'm using linux on this thing is because this usb >> wireless >> keyboard with built-in touch pad works under linux and not under freebsd, >> including 6.0 current as of several weeks ago. > > That's a really crummy reason to be running Linux. > > I'm sorry, but it is. Well, since the telepathy driver is still in negative zeta, and no other rf wireless keybord with built in touch-pad exists that I've found, barring one other unit that's over $200, (the Sony is already $150) And since it's just a thin client (or fat, I don't care which), it doesn't much matter what runs on it. The real machine with the raid array and the cpu horsepower and which is hosting the nfs shared unpacked copy of knoppix, and dhcp & tftp is freebsd. Not that I'm overly religeous about it. Right next to it on the same rack in my cellar, both performing necessary tasks, are a SuSE 10 box and a SCO Open Server 5.0.6 (sometimes 5.0.7) box. Really, rather than being a crummy reason to run Linux, it's the other way around. I actually don't have a defensible reason I can think of to bother with the necessary effort to get freebsd working on the thin client as long as anything at all works that has the necessary client software (rdesktop/vnc/web browser/ssh/telnet/NX/etc... Even if the only thing that worked were win-ce. But I'm not too snooty to admit that I simply want to run freebsd on it because I just want to. :) Because it's "cool" and so that I can say that I am running freebsd as part of my entertainment system without making my living room look like a server closet. Rather, having more functionality (via using any*ix) and at the very same time having to put up with actually less computer station ugliness than most people, who have a ordinary windows pc and all the typical parephenalia somewhere in their living space. Cake, and eating it too. >> Symptoms: keyboard works fine, mouse is unrecognized. (neither at the OS >> or >> X levels) >> >> It's been several weeks since I gave up so I'll need to perform tests >> again >> to define "mouse is unrecognized" better. > > Well, maybe your memory isn't that great, but the intarweb never forgets. > Travelling back in time to the freebsd-usb mailing list from July, we > find a similar post from you about this very same issue, in which you > thankfully had the presence of mind to say: > >> dmesg on 5.4-release shows this near the end: >> >> ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 >> uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 kbd1 at ukbd0 > > There's something very strange about this output, by the way. I don't > think you cut & pasted it exactly as it appeared on the screen. I think > it should look more like this: > >> ukbd0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 >> kbd1 at ukbd0 >> uhid0: Sony RF Receiver, rev 1.10/1.00, addr 2, iclass 3/1 > > But even this isn't quite right, because I don't think both devices > should appear at address 2 on the same hub. I suspect you transcribed > the information and typed it in wrong. > > Assuming the presence of the 'uhid0' line isn't a mistake, the real > description of the problem is: "the mouse is showing up as a uhid(4) > evice instead of a ums(4) device." > > uhid(4) is a generic driver for USB devices in the Human Interface Device > class. This includes mice, keyboards, joysticks, gamepads, drawing > tablets, and so on. Keyboards and mice are considered special enough > to warrant their own private drivers (ukbd(4) and ums(4)), largely to > make them emulate the behavior of their non-USB ancestors (thereby > allowing existing application software to use USB keyboards and mice > without having to be modified to include special USB support). Any HID > device that doesn't have a special driver just gets picked up by the > uhid(4) generic driver. > > When you plug in your mouse, the USB mouse driver probe checks > its HID usage group to make sure it's a 'generic desktop' device > with 'mouse' usage. If this check fails, the driver decides the > device isn't really a mouse and fails the probe. Later, the uhid(4) > driver will claim the device since nobody else did. > > Now, there's two possible things that can be going wrong here: > > 1) The ums(4) driver isn't loaded. Given that the ums(4) driver is > part of the GENERIC kernel, the only way this could have happened > is if you went and built your own kernel and then for some stange > reason took 'device ums' out of the config file. You never bothered > to state whether or not you compiled your own kernel, so I have > no way of knowing whether or not this happened. > > 2) The mouse is not reporting itself as a generic desktop/mouse > device, and the ums(4) driver is ignoring it. > > If the issue is thing 1, then you need to either add 'device ums' > back to your kernel config, or add 'ums_load="YES"' to your > /boot/loader.conf file. At the moment, ums is built-in, and psm is commented out. > If the issue is thing 2, then you need to do the following: > > - Boot up FreeBSD 6.0. > - Plug the wireless keyboard/mouse into a USB port on a FreeBSD machine > - Wait until you see the ukbd0/uhid0 probe output on the console (i.e. > wait until FreeBSD sees the devices) > - Run "dmesg" and save _ALL_ the output. Report it to us so we can > see it. And I mean _ALL_ of it. The following were all run on the thin client, using the kernel and world built from this config file: http://keyofr.homeunix.net:81/netgear_hub_thin_client/HUBPC root@ngh# dmesg >20060106_dmesg.txt http://keyofr.homeunix.net:81/netgear_hub_thin_client/20060106_dmesg.txt - removed and reinserted the receiver - root@ngh# tail -10 /var/log/messages >20060106_ukbd_insert.txt http://keyofr.homeunix.net:81/netgear_hub_thin_client/20060106_ukbd_insert.txt Note: there is a 3rd device not showing here, that is part of the kit, but which I am not using, which is the seperate wireless mouse. It uses the same reciever as the keyboard and touch pad. There is also a "sleep" button on the keyboard that doesn't generate a scancode (even on Linux where the touch pad mouse works fully) so that may be yet another device all it's own. (It is used to put windows to sleep/hibernate/death so it's not something purely local to the device like the on/off switch on the side of the keyboard. There are also a few multimedia buttons implimented as hardware hot keys ("Fn" + F2/F3/F4), but they already generate scancodes and so they are obviously part of ukbd. > - Run the following commands, as root: > > # usbdevs -v root@ngh# usbdevs -v >20060106_usbdevs.txt http://keyofr.homeunix.net:81/netgear_hub_thin_client/20060106_usbdevs.txt > # usbhidctl -f /dev/uhid0 -r root@ngh# usbhidctl -f /dev/uhid0 -r >20060106_usbhidctl_uhid0.txt http://keyofr.homeunix.net:81/netgear_hub_thin_client/20060106_usbhidctl_uhid0.txt > - This should show all the information that the mouse reports about > itself. > Save the output (there'll probably be a page or two of information) and > report _ALL_ of it here so that we can see it. And I mean _ALL_ of it. > > If it really is a USB mouse class device and it's just misrepresenting > itself, then it's likely the USB_MATCH() routine in sys/dev/usb/ums.c > can be tweaked a little to recognize the device. But we won't know for > sure until we see the output of the usbhidctl command. > >> I _think_ on the latest ThinBSD, which is 5.4-release, and all later >> versions, that the touch pad pointer works but not the buttons. I may be >> misremembering but we don't have to guess once I try it again. > > Why didn't you try it again before writing this e-mail? Then your faulty > memory wouldn't be an issue. > > Also, what the heck is ThinBSD? It's way cool daddy-o. Short answer: stripped down freebsd 5.4-release that: * runs entirely within a small ramdisk * boots the kernel & loads modules via tftp * gets the ramdisk via tftp * gets key per-client configuration via dhcp * includes an rdp client and x server ready to go out of the box * is installed by merely placing the premade compressed fs image, and unpacking a premade tar of the /boot tree, in /tftpboot * is configured by merely adding a few lines to dhcpd.conf Though as it happens I'm currently more interested in a full nfs boot, nfs root, and so that's what I'm doing now. But this is primarily just to make it easier to work out problems like this keyboard and do other customizations like add a ups monitor, print server, audio server, wired remote controls for all the entertainment components, other clients besides rdp & x, like vnc, nx, ssh, cu, kermit, etc... Ultimately after arriving at a working customized system, I may then try to make a customized thinbsd out of it and go back to the simpler scheme of only needing tftp & dhcp. >> Some people have said it might be that it's because there is a single usb >> wireless receiverfor 3 devices (keyboard, built-in touchpad mouse, and a >> seperate optical mouse which I don't happen to use.) And the keyboard >> sort >> of takes exclusive control of the usb device. > > The people who told you this are feelthy liars. Feelthy, I say. > >> The device works out of the box, no drivers, on XP and I can use usbsnoop >> if >> desired too to capture xp traffic, but since it already works on linux >> then >> the code to make it work is already out there to be mined right? > > I don't think the solution will be all that complicated. Just go boot up > FreeBSD 6.0 and report the stuff I asked for. Done. Thanks much. Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/ +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++. filePro BBx Linux SCO FreeBSD #callahans Satriani Filk! From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 09:32:13 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4096E16A41F for ; Fri, 6 Jan 2006 09:32:13 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: from bsd.ultra-secure.de (bsd.ultra-secure.de [62.146.20.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE21243D45 for ; Fri, 6 Jan 2006 09:32:11 +0000 (GMT) (envelope-from rainer@ultra-secure.de) Received: (qmail 39447 invoked by uid 89); 6 Jan 2006 09:32:10 -0000 Received: by simscan 1.1.0 ppid: 39431, pid: 39435, t: 1.7103s scanners: attach: 1.1.0 clamav: 0.86.2/m:33/d:1045 spam: 3.0.4 Received: from unknown (HELO ?192.168.100.179?) (rainer@ultra-secure.de@217.71.84.110) by bsd.ultra-secure.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 6 Jan 2006 09:32:08 -0000 Message-ID: <43BE3914.3030208@ultra-secure.de> Date: Fri, 06 Jan 2006 10:32:04 +0100 From: Rainer Duffner User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <200601051802.k05I2wAN026595@reddevil.brancatelli.it> <20060105145731.F58957@carver.gumbysoft.com> In-Reply-To: <20060105145731.F58957@carver.gumbysoft.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on bsd.ultra-secure.de X-Spam-Level: X-Spam-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.0.4 Cc: Andrea Brancatelli , current@freebsd.org Subject: Re: The BladeCenter Saga -> bge driver not behaving properly... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 09:32:13 -0000 Doug White wrote: >On Thu, 5 Jan 2006, Andrea Brancatelli wrote: > > > >>Sorry for breaking the thread and posting a new message instead of replying >>but I'm having some problems with my mailserver. >> >>I did a few screenshots of the problems we are having with the Broadcom lan >>card and the bge driver... I cannot paste text because I cannot access the >>machine in SSH (since it's not working...) >> >> > >You need to compile your kernel with > >options BGE_FAKE_AUTONEG > >This option is available on RELENG_5 after 5.4 only .. 5.4-RELEASE itself >should work due to my attempts to sabotage other blade vendors' products. >Our driver does not handle autonegotation for the blades correctly. > > FYI: The LS20 blades only do 1000 TX anyway (at least here, we don't have the internal switch). That may be the reason for this quirk. cheers, Rainer From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 10:54:16 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4920216A41F for ; Fri, 6 Jan 2006 10:54:16 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD0E243D46 for ; Fri, 6 Jan 2006 10:54:15 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id 18C31105; Fri, 6 Jan 2006 05:54:37 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id A4D8F4A1F; Fri, 6 Jan 2006 05:54:33 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EupEY-0007do-3m; Fri, 06 Jan 2006 10:54:10 +0000 Date: Fri, 6 Jan 2006 10:54:10 +0000 From: Brian Candler To: Scott Long Message-ID: <20060106105409.GA29355@uk.tiscali.com> References: <20051230104816.GA1779@webcom.it> <001601c60d86$0a8fe8e0$642a15ac@smiley> <20051230235132.GC1779@webcom.it> <43B5CA24.5030604@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43B5CA24.5030604@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: Andrea Campi , freebsd-current@freebsd.org, Darren Pilgrim Subject: Re: sudo in basesystem (was: fetch extension - use local filenamefrom content-disposition header) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 10:54:16 -0000 On Fri, Dec 30, 2005 at 05:00:36PM -0700, Scott Long wrote: > Now, if portupgrade > were written in C or even C++, it would be a no-brainer to import. Does sysutils/portmanager meet the requirements? From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 11:05:39 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D75C516A41F for ; Fri, 6 Jan 2006 11:05:39 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D74943D45 for ; Fri, 6 Jan 2006 11:05:39 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by zproxy.gmail.com with SMTP id q3so2692668nzb for ; Fri, 06 Jan 2006 03:05:38 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nkiIi149OrgjmBd4l2m9fj5h4i9ZNbSdK58ERRoL7OqsNZxuVnSBg4Gt6zYd3FZ66EBEmZRpZd4M+fVGXLzKbuqBCU9g5hQvA5cZAPiCw5gAtrBqj5j8RfZah2u9VxiK0qOV0m6x3vx9vt2zP9ElUbVLlG0uv2SO9JOz67tTL1E= Received: by 10.65.240.8 with SMTP id s8mr1865799qbr; Fri, 06 Jan 2006 03:05:38 -0800 (PST) Received: by 10.65.110.4 with HTTP; Fri, 6 Jan 2006 03:05:38 -0800 (PST) Message-ID: Date: Fri, 6 Jan 2006 19:05:38 +0800 From: Jiawei Ye To: Brian Candler In-Reply-To: <20060106105409.GA29355@uk.tiscali.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051230104816.GA1779@webcom.it> <001601c60d86$0a8fe8e0$642a15ac@smiley> <20051230235132.GC1779@webcom.it> <43B5CA24.5030604@samsco.org> <20060106105409.GA29355@uk.tiscali.com> Cc: Andrea Campi , freebsd-current@freebsd.org, Darren Pilgrim Subject: Re: sudo in basesystem (was: fetch extension - use local filenamefrom content-disposition header) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 11:05:40 -0000 On 1/6/06, Brian Candler wrote: > On Fri, Dec 30, 2005 at 05:00:36PM -0700, Scott Long wrote: > > Now, if portupgrade > > were written in C or even C++, it would be a no-brainer to import. > > Does sysutils/portmanager meet the requirements? You have my vote for this one too. Jiawei Ye -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 11:50:25 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F018816A41F; Fri, 6 Jan 2006 11:50:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 922B443D49; Fri, 6 Jan 2006 11:50:22 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp232-237.lns2.adl4.internode.on.net [203.122.232.237]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k06BoHrD041706 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 6 Jan 2006 22:20:20 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jo Rhett Date: Fri, 6 Jan 2006 22:20:11 +1030 User-Agent: KMail/1.8.3 References: <43A266E5.3080103@samsco.org> <200601061120.14707.doconnor@gsoft.com.au> <20060106112329.GG54324@svcolo.com> In-Reply-To: <20060106112329.GG54324@svcolo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart17759608.RyVHtf6x3N"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601062220.13417.doconnor@gsoft.com.au> X-Spam-Score: 0 () SUBJECT_EXCESS_QP X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006 ) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 11:50:26 -0000 --nextPart17759608.RyVHtf6x3N Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 6 Jan 2006 21:53, Jo Rhett wrote: > > you mean? Are you claiming someone from (or claiming to be from core) > > said "Don't do this, we won't allow it"? If so, can you supply proof? > > I used to write a lot of patches to freebsd. I used to submit a lot of b= ug > reports. I've found over the years that unless you have gotten > pre-agreement from others about the nature of the patch, or agreement to > focus on the problem, neither one amounts to a hill of beans. Installati= on > problems that existed in 4.4 are still alive and well in the 6.0 installe= r, > for example. That is not my experience. > How FreeBSD "works" is by getting someone in the core team to care about > the issue. No amount of problem reports, patches or code will generate > even a millimeter of movement otherwise. You are mistaking core@ for developers@.. Like I've said before, core is largely irrelevant in FreeBSD when it comes = to=20 deciding what stuff gets added. > I've written far too much code for various freebsd problems, and it has > always been ignored. Not rejected, ignored. Unless someone with commit > rights thinks it's a good idea, writing code for freebsd is a waste of > time. Yes.. and those people AREN'T CORE. Please, please stop confusing your term= s,=20 it makes the discussion much harder than it needs to be. You ARE right if what you mean is that "We need interested committers to he= lp=20 thrash out a system for making upgrades simpler". I imagine there are a few committers interested, but I'd say you need to as= k=20 the right way first.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart17759608.RyVHtf6x3N Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvll15ZPcIHs/zowRAmo8AJ9ocN73YZijfX5s6c0b5FL4AhIKgwCeIL4j oC06ZOPLwTvNrCdlTzdm/i8= =hJ81 -----END PGP SIGNATURE----- --nextPart17759608.RyVHtf6x3N-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 12:23:03 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E29BB16A41F; Fri, 6 Jan 2006 12:23:02 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from crivens.unixoid.de (crivens.unixoid.de [81.169.171.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C5FE43D48; Fri, 6 Jan 2006 12:23:02 +0000 (GMT) (envelope-from MH@kernel32.de) Received: from localhost (localhost [127.0.0.1]) by crivens.unixoid.de (Postfix) with ESMTP id 43F693F7E; Fri, 6 Jan 2006 13:23:00 +0100 (CET) Received: from crivens.unixoid.de ([127.0.0.1]) by localhost (crivens.unixoid.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 95718-16; Fri, 6 Jan 2006 13:22:56 +0100 (CET) Received: from [10.38.0.120] (unknown [213.238.63.253]) by crivens.unixoid.de (Postfix) with ESMTP id 1356E41BD; Fri, 6 Jan 2006 13:22:56 +0100 (CET) Message-ID: <43BE6226.5000103@kernel32.de> Date: Fri, 06 Jan 2006 13:27:18 +0100 From: Marian Hettwer User-Agent: Mozilla Thunderbird 1.0.2 (Macintosh/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jo Rhett References: <43A266E5.3080103@samsco.org> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> <200601061120.14707.doconnor@gsoft.com.au> <20060106112329.GG54324@svcolo.com> In-Reply-To: <20060106112329.GG54324@svcolo.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at unixoid.de Cc: freebsd-stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 12:23:03 -0000 Hi there, Jo Rhett wrote: > On Fri, Jan 06, 2006 at 11:20:13AM +1030, Daniel O'Connor wrote: >> >>So, uhh, how would your magical binary upgrade system handle custom kernels? >>Why would it be any different? You still haven't explained how this would >>work.. > > > Versioning of the core package would tell you WHAT you have with a query. > It's trivial to then install the matching patches. Right now every > enterprise has to build a backend database tracking core os, installed > options, compile options, etc for every single installed system. Or build > a checksum database that can be used to derive this information from the > system (if all systems have the CPU/RAM to spare to play this game) > I'm actually wondering how yahoo for instance handles this situation. To my knowledge, they have several thousand of FreeBSD based servers. Either they are all the same in regards to configuration and version, or they have some other cunning way to solve the issue of patching. > > We need support from the freebsd core developers that this is a worthwhile > idea, and what kind of solutions would be acceptable to them. Once we have > a direction to go in, code can be written. > Generally speaking: Your statement is true. You don't start writing code without an agreement that the direction choosen is a direction where FreeBSD wants to evolve. However, you (as in, you as a developer) could come up with a proof of concept. Start with an implementation like you would like to have it. And even if it's just a piece of paper and some code. Then start this thread over again, fine tune the concept and hopefully some others will jump aboard and help developing. I would like to, but I do lack knowledge in C. Shell and a wee bit of Perl is fine. Definitly too few knowledge for a project like that :-/ > >>If you supply a working framework then I think you'll find a lot of support >>materialises. The problem is when you are just proposing vapourware solutions >>everyone steps in and wants it done their way. >> >>Code speaks louder than words :) > > > I've written far too much code for various freebsd problems, and it has > always been ignored. Not rejected, ignored. Unless someone with commit > rights thinks it's a good idea, writing code for freebsd is a waste of > time. > That statement ain't true. If the code solves your problem, fine. If it solves problems of others too, even better. Chances are higher that it doesn't get ignored... regards, Marian From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 12:41:36 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E247716A41F for ; Fri, 6 Jan 2006 12:41:36 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from msgmmp-4.gci.net (msgmmp-4.gci.net [209.165.130.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FD8843D48 for ; Fri, 6 Jan 2006 12:41:36 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from stargate.akparadise.com ([209.124.141.64]) by msgmmp-4.gci.net (Sun Java System Messaging Server 6.2-3.03 (built Jun 27 2005)) with ESMTPA id <0ISO00CDF8JQF6A0@msgmmp-4.gci.net> for freebsd-current@freebsd.org; Fri, 06 Jan 2006 03:40:41 -0900 (AKST) Received: by stargate.akparadise.com (Postfix, from userid 0) id C966C3FAA; Fri, 06 Jan 2006 03:40:37 -0900 (AKST) Date: Fri, 06 Jan 2006 03:40:21 -0900 From: Beech Rintoul To: freebsd-current@freebsd.org Message-id: <200601060340.35999.akbeech@gmail.com> Organization: NorthWind Communications MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1810774.cbsc3BK0Ty; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.8.3 Subject: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 12:41:37 -0000 --nextPart1810774.cbsc3BK0Ty Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I have noticed that for about the past month or so I've been getting hundre= ds=20 of the following every day in /var/log/messages: +ath0: link state changed to DOWN +ath0: link state changed to UP It doesn't seem to affect connectivity, but it's really annoying in the=20 security report. Is there anything I can do to stop this? I'm running=20 =2DCURRENT from yesterday. I have built Sam's new drivers, but this problem= =20 started long before that and was not affected by the upgrade. The lease on= =20 the AP I'm connecting to is good for 24 hours so I don't think that's an=20 issue. I looked at the traffic with ethereal and everything looks normal. I= 'm=20 getting sorely tempted to go back to isc-dhclient and see if this goes away= ,=20 but I thought I would ask here first. Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - System Administrator - akbeech@gmail.com /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://akparadise.byethost33.com =2D------------------------------------------------------------------------= =2D------------- --nextPart1810774.cbsc3BK0Ty Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvmVDVq19LUoGB+MRAoxwAJ9PQjqtsmMlLQJPNcFiLf4luRipWgCdEVTo WwLNZQEPz2WSOv4nEJ/CUbU= =9pkm -----END PGP SIGNATURE----- --nextPart1810774.cbsc3BK0Ty-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 13:24:52 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B3B116A420 for ; Fri, 6 Jan 2006 13:24:52 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD2F843D45 for ; Fri, 6 Jan 2006 13:24:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 5424832 for multiple; Fri, 06 Jan 2006 08:26:20 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.4/8.13.4) with ESMTP id k06DOlCp024148; Fri, 6 Jan 2006 08:24:47 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 6 Jan 2006 08:24:44 -0500 User-Agent: KMail/1.8.3 References: <20060103233406.GA1564@hut.isi.edu> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200601060824.45913.jhb@freebsd.org> X-Virus-Scanned: ClamAV 0.87.1/1232/Fri Jan 6 06:04:05 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.4 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Svein Halvor Halvorsen , Ted Faber Subject: Re: lost /dev/agpgart , X11 confused. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 13:24:52 -0000 On Wednesday 04 January 2006 04:39 pm, Svein Halvor Halvorsen wrote: > On 1/4/06, Ted Faber wrote: > > On -CURRENT as of today, and a rebuild today of the xorg-server-6.8.2_7 > > package against the new source, my Xserver won't allocate many video > > modes because it can't open /dev/agpgart to allocate memory. The video > > card is an Intel I810 - 865G chipset. > > > > On the new kernel neither the /dev/agpgart nor a /dev/vgapci devide > > appears (which seems to be hinted at in the comments to the most recent > > change to /sys/pci/agp_i810.c from the CVS tree). I've attached a > > verbose dmesg from the kernel recent -CURRENT kernel. > > > > Anyone else having a similar problem or know what I'm doing wrong? I'm > > happy to test patches or provide more info. > > Even though I asked tis question twice, I did not get a single > response. No-one even bothered to ask me for more detail. On my Dell > Latitude x300 I had a similar problem but on the 855GM-chipset. The > problem seemed to be related to apci_video loading boefore agp and > somehow attaching to the video card, and blocking agp from attaching. > Or something like that. > > Your problem might not be the same, though. The problem with acpi_video is fixed in CURRENT. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 14:03:11 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD0EF16A420 for ; Fri, 6 Jan 2006 14:03:11 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D6143D48 for ; Fri, 6 Jan 2006 14:03:09 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id k06E38E8078927; Fri, 6 Jan 2006 08:03:08 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43BE7888.8060302@centtech.com> Date: Fri, 06 Jan 2006 08:02:48 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Beech Rintoul References: <200601060340.35999.akbeech@gmail.com> In-Reply-To: <200601060340.35999.akbeech@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1233/Fri Jan 6 06:31:08 2006 on mh2.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 14:03:11 -0000 Beech Rintoul wrote: >I have noticed that for about the past month or so I've been getting hundreds >of the following every day in /var/log/messages: > >+ath0: link state changed to DOWN >+ath0: link state changed to UP > >It doesn't seem to affect connectivity, but it's really annoying in the >security report. Is there anything I can do to stop this? I'm running >-CURRENT from yesterday. I have built Sam's new drivers, but this problem >started long before that and was not affected by the upgrade. The lease on >the AP I'm connecting to is good for 24 hours so I don't think that's an >issue. I looked at the traffic with ethereal and everything looks normal. I'm >getting sorely tempted to go back to isc-dhclient and see if this goes away, >but I thought I would ask here first. > > > I've noticed something recently too - my ath device frequently stops working, and I get this in messages: Jan 6 06:19:48 neutrino kernel: ath0: link state changed to DOWN Jan 6 06:20:35 neutrino kernel: ath0: device timeout Jan 6 06:20:56 neutrino kernel: ath0: device timeout Jan 6 06:21:06 neutrino kernel: ath0: device timeout Jan 6 06:21:59 neutrino last message repeated 2 times Jan 6 06:22:25 neutrino kernel: ath0: device timeout Jan 6 06:23:03 neutrino kernel: ath0: link state changed to UP Jan 6 06:41:35 neutrino kernel: ath0: link state changed to DOWN Jan 6 06:42:03 neutrino kernel: Memory modified after free 0xc5402000(2048) val=11600000 @ 0xc5402000 Jan 6 06:42:04 neutrino kernel: ath0: link state changed to UP Jan 6 06:42:08 neutrino kernel: ath0: device timeout Jan 6 06:42:09 neutrino kernel: ath0: link state changed to DOWN Jan 6 06:43:12 neutrino kernel: ath0: link state changed to UP Jan 6 06:43:17 neutrino kernel: ath0: device timeout Jan 6 06:43:17 neutrino kernel: ath0: link state changed to DOWN Jan 6 06:43:33 neutrino kernel: ath0: device timeout Jan 6 06:44:10 neutrino kernel: ath0: device timeout [and so on] I would say this started happening for me in the last 2 weeks. I'm running -current from Jan 4th. All kinds of system information is here: http://googlebit.com/freebsd/ Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 15:50:27 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDCB616A420; Fri, 6 Jan 2006 15:50:27 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4880443D53; Fri, 6 Jan 2006 15:50:26 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5DD32.dip.t-dialin.net [84.165.221.50]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.1/8.13.1) with ESMTP id k06FjO0v014216; Fri, 6 Jan 2006 16:45:25 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.3/8.13.3) with ESMTP id k06Fnifn018274; Fri, 6 Jan 2006 16:49:45 +0100 (CET) (envelope-from Alexander@Leidinger.net) Date: Fri, 6 Jan 2006 16:49:44 +0100 From: Alexander Leidinger To: "M. Warner Losh" Message-ID: <20060106164944.39011848@Magellan.Leidinger.net> In-Reply-To: <20060105.230253.93225432.imp@bsdimp.com> References: <17341.65102.980006.14057@canoe.dclg.ca> <20060105.230253.93225432.imp@bsdimp.com> X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org, dgilbert@dclg.ca Subject: Re: Disappearing memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 15:50:28 -0000 On Thu, 05 Jan 2006 23:02:53 -0700 (MST) "M. Warner Losh" wrote: > In message: <17341.65102.980006.14057@canoe.dclg.ca> > David Gilbert writes: > : Maybe what we need is 'usbcontrol' ... allowing us to reset (or at > : least reset the OSs idea of) one usb device. > > I've wanted a generic way to send messages to busses about children > and to devices. PC Card and CardBus could use that for power down as > well.. If you aren't going to write it yourself, feel free to write up a (plain-text) entry for http://www.FreeBSD.org/projects/ideas/ and send it to us. Bye, Alexander. -- ...and that is how we know the Earth to be banana-shaped. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 WL http://www.amazon.de/exec/obidos/registry/1FZ4DTHQE9PQ8/ref=wl_em_to/ From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 16:45:32 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42F0316A41F for ; Fri, 6 Jan 2006 16:45:32 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA83743D48 for ; Fri, 6 Jan 2006 16:45:29 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k06GjQo7036544 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jan 2006 08:45:26 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BE9F0A.5000200@errno.com> Date: Fri, 06 Jan 2006 08:47:06 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Beech Rintoul References: <200601060340.35999.akbeech@gmail.com> In-Reply-To: <200601060340.35999.akbeech@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 16:45:32 -0000 Beech Rintoul wrote: > I have noticed that for about the past month or so I've been getting hundreds > of the following every day in /var/log/messages: > > +ath0: link state changed to DOWN > +ath0: link state changed to UP > > It doesn't seem to affect connectivity, but it's really annoying in the > security report. Is there anything I can do to stop this? I'm running > -CURRENT from yesterday. I have built Sam's new drivers, but this problem > started long before that and was not affected by the upgrade. The lease on > the AP I'm connecting to is good for 24 hours so I don't think that's an > issue. I looked at the traffic with ethereal and everything looks normal. I'm > getting sorely tempted to go back to isc-dhclient and see if this goes away, > but I thought I would ask here first. sysctl net.link.log_link_state_change=0 will make the msgs go away. I do this on all my laptops. The issue (which should be in an FAQ) is that your station is reassociating to the ap, typically because you are idle. Each time this happens the link state goes down+up. The dhcp lease is not relevant. You might be able to tweak ap parameters to increase the idle timeout but aside from the link state msgs there's no reason to. Sam From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 16:50:30 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86C7D16A41F for ; Fri, 6 Jan 2006 16:50:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF6943D46 for ; Fri, 6 Jan 2006 16:50:30 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k06GoOo7036567 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jan 2006 08:50:25 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BEA035.9030704@errno.com> Date: Fri, 06 Jan 2006 08:52:05 -0800 From: Sam Leffler User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051227) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <200601060340.35999.akbeech@gmail.com> <43BE7888.8060302@centtech.com> In-Reply-To: <43BE7888.8060302@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Beech Rintoul Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 16:50:30 -0000 Eric Anderson wrote: > Beech Rintoul wrote: > >> I have noticed that for about the past month or so I've been getting >> hundreds of the following every day in /var/log/messages: >> >> +ath0: link state changed to DOWN >> +ath0: link state changed to UP >> >> It doesn't seem to affect connectivity, but it's really annoying in >> the security report. Is there anything I can do to stop this? I'm >> running -CURRENT from yesterday. I have built Sam's new drivers, but >> this problem started long before that and was not affected by the >> upgrade. The lease on the AP I'm connecting to is good for 24 hours so >> I don't think that's an issue. I looked at the traffic with ethereal >> and everything looks normal. I'm getting sorely tempted to go back to >> isc-dhclient and see if this goes away, but I thought I would ask here >> first. >> >> >> > > I've noticed something recently too - my ath device frequently stops > working, and I get this in messages: > > Jan 6 06:19:48 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:20:35 neutrino kernel: ath0: device timeout > Jan 6 06:20:56 neutrino kernel: ath0: device timeout > Jan 6 06:21:06 neutrino kernel: ath0: device timeout > Jan 6 06:21:59 neutrino last message repeated 2 times > Jan 6 06:22:25 neutrino kernel: ath0: device timeout > Jan 6 06:23:03 neutrino kernel: ath0: link state changed to UP > Jan 6 06:41:35 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:42:03 neutrino kernel: Memory modified after free > 0xc5402000(2048) val=11600000 @ 0xc5402000 > Jan 6 06:42:04 neutrino kernel: ath0: link state changed to UP > Jan 6 06:42:08 neutrino kernel: ath0: device timeout > Jan 6 06:42:09 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:43:12 neutrino kernel: ath0: link state changed to UP > Jan 6 06:43:17 neutrino kernel: ath0: device timeout > Jan 6 06:43:17 neutrino kernel: ath0: link state changed to DOWN > Jan 6 06:43:33 neutrino kernel: ath0: device timeout > Jan 6 06:44:10 neutrino kernel: ath0: device timeout > [and so on] > > > I would say this started happening for me in the last 2 weeks. Device timeouts should not happen; it means the driver submitted a packet to the card and didn't get a tx complete interrupt back in 5 seconds. It's unclear if the "modified after free" msgs is related and w/o more diagnostic info it's really hard to say why you're seeing device timeouts. > > I'm running -current from Jan 4th. All kinds of system information is > here: > > http://googlebit.com/freebsd/ Most of the useful info is not there. No boot dmsg or indication of what your network config is. No indication of the hal version or the mac+phy revs. yada yada yada... Sam From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 17:21:33 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9515916A420 for ; Fri, 6 Jan 2006 17:21:33 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88FEB43D46 for ; Fri, 6 Jan 2006 17:21:22 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id A3A025DE9; Fri, 6 Jan 2006 12:21:21 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57657-06; Fri, 6 Jan 2006 12:21:19 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-122-227.ny325.east.verizon.net [68.161.122.227]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 04B815DDA; Fri, 6 Jan 2006 12:21:18 -0500 (EST) Message-ID: <43BEA718.6090306@mac.com> Date: Fri, 06 Jan 2006 12:21:28 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> In-Reply-To: <200601060636.k066aNYn079015@apollo.backplane.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: Luigi Rizzo , Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 17:21:33 -0000 Matthew Dillon wrote: >: Luigi Rizzo wrote: [ ... ] >:> on a related topic, any comments on this one ? >:> Is this code that we could use ? >:> >:> http://www.dragonflybsd.org/docs/nanosleep/ >: >:I ported the tvtohz change from Dragonfly back to 4.10 and 5-STABLE here: >: >:http://www.pkix.net/~chuck/timer/ >: >:...so anyone who wants to experiment can try it out. :-) [ ... ] > > It isn't so much tvtohz that's the issue, but the fact that the > nanosleep() system call has really coarse hz-based resolution. That's > been fixed in DragonFly and I would recommend that it be fixed in > FreeBSD too. After all, there isn't much of a point having a system > call called 'nanosleep' whos time resolution is coarse-grained and > non-deterministic from computer to computer (based on how hz was > configured). Agreed. The changes I'd copied back basicly correct the issue of nanosleep() waiting an extra tick, so they cut the average latency seen by something trying to wakeup at an exact point from about 1.5 * HZ to about 0.5 * HZ, but they don't give it finer-grained timing. > Since you seem to be depending on fine-resolution timers more and > more in recent kernels, you should consider porting our SYSTIMER API > to virtualize one-shot and periodic-timers. Look at kern/kern_systimer.c > in the DragonFly source. The code is fairly well abstracted, operates > on a per-cpu basis, and even though you don't have generic IPI messaging > I think you could port it without too much trouble. > > If you port it and start using it you will quickly find that you can't > live without it. e.g. take a look at how we implement network POLLING for > an example of its use. The polling rate can be set to anything at > any time, regardless of 'hz'. Same goes for interrupt rate limiting, > various scheduler timers, and a number of other things. All the things > that should be divorced from 'hz' have been. Out of curiosity, what is DragonFly doing with the network timing counters (ie, TCPOPT_TIMESTAMP and the stuff in ), has that been seperated from HZ too? I'm pretty sure that setting: #define TCPTV_MSL ( 30*hz) /* max seg lifetime (hah!) */ ...with HZ=1000 or more is not entirely correct. :-) Not when it started with the TTL in hops being equated to one hop per second... -- -Chuck From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 17:54:46 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0BCAB16A41F for ; Fri, 6 Jan 2006 17:54:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5877643D80 for ; Fri, 6 Jan 2006 17:54:31 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id k06HsFdN066370; Fri, 6 Jan 2006 11:54:16 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <43BEAEB3.1050105@centtech.com> Date: Fri, 06 Jan 2006 11:53:55 -0600 From: Eric Anderson User-Agent: Mozilla Thunderbird 1.0.7 (X11/20060104) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sam Leffler References: <200601060340.35999.akbeech@gmail.com> <43BE7888.8060302@centtech.com> <43BEA035.9030704@errno.com> In-Reply-To: <43BEA035.9030704@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87.1/1234/Fri Jan 6 07:54:31 2006 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-current@freebsd.org, Beech Rintoul Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 17:54:46 -0000 Sam Leffler wrote: > Eric Anderson wrote: > >> Beech Rintoul wrote: >> >>> I have noticed that for about the past month or so I've been getting >>> hundreds of the following every day in /var/log/messages: >>> >>> +ath0: link state changed to DOWN >>> +ath0: link state changed to UP >>> >>> It doesn't seem to affect connectivity, but it's really annoying in >>> the security report. Is there anything I can do to stop this? I'm >>> running -CURRENT from yesterday. I have built Sam's new drivers, but >>> this problem started long before that and was not affected by the >>> upgrade. The lease on the AP I'm connecting to is good for 24 hours >>> so I don't think that's an issue. I looked at the traffic with >>> ethereal and everything looks normal. I'm getting sorely tempted to >>> go back to isc-dhclient and see if this goes away, but I thought I >>> would ask here first. >>> >>> >>> >> >> I've noticed something recently too - my ath device frequently stops >> working, and I get this in messages: >> >> Jan 6 06:19:48 neutrino kernel: ath0: link state changed to DOWN >> Jan 6 06:20:35 neutrino kernel: ath0: device timeout >> Jan 6 06:20:56 neutrino kernel: ath0: device timeout >> Jan 6 06:21:06 neutrino kernel: ath0: device timeout >> Jan 6 06:21:59 neutrino last message repeated 2 times >> Jan 6 06:22:25 neutrino kernel: ath0: device timeout >> Jan 6 06:23:03 neutrino kernel: ath0: link state changed to UP >> Jan 6 06:41:35 neutrino kernel: ath0: link state changed to DOWN >> Jan 6 06:42:03 neutrino kernel: Memory modified after free >> 0xc5402000(2048) val=11600000 @ 0xc5402000 >> Jan 6 06:42:04 neutrino kernel: ath0: link state changed to UP >> Jan 6 06:42:08 neutrino kernel: ath0: device timeout >> Jan 6 06:42:09 neutrino kernel: ath0: link state changed to DOWN >> Jan 6 06:43:12 neutrino kernel: ath0: link state changed to UP >> Jan 6 06:43:17 neutrino kernel: ath0: device timeout >> Jan 6 06:43:17 neutrino kernel: ath0: link state changed to DOWN >> Jan 6 06:43:33 neutrino kernel: ath0: device timeout >> Jan 6 06:44:10 neutrino kernel: ath0: device timeout >> [and so on] >> >> >> I would say this started happening for me in the last 2 weeks. > > > Device timeouts should not happen; it means the driver submitted a > packet to the card and didn't get a tx complete interrupt back in 5 > seconds. > > It's unclear if the "modified after free" msgs is related and w/o more > diagnostic info it's really hard to say why you're seeing device > timeouts. Ok - wasn't sure if was related or not, so I posted it anyway. Before about 2 weeks ago, ath has been rock solid for me. > >> >> I'm running -current from Jan 4th. All kinds of system information >> is here: >> >> http://googlebit.com/freebsd/ > > > Most of the useful info is not there. No boot dmsg or indication of > what your network config is. No indication of the hal version or the > mac+phy revs. yada yada yada... Yea, I see that now. Sorry - here's dmesg.boot: http://googlebit.com/freebsd/dmesg.boot-20060106 And some additional info: /etc/rc.conf snippet: ifconfig_em0="DHCP" ifconfig_ath0="WPA DHCP" /etc/wpa_supplicant.conf: ctrl_interface=/var/run/wpa_supplicant ctrl_interface_group=wheel network={ ssid="centtech" key_mgmt=NONE wep_key0=0E...CD wep_tx_keyidx=0 scan_ssid=1 priority=5 } $ kldstat Id Refs Address Size Name 1 36 0xc0400000 7707a4 kernel 2 2 0xc0b71000 1e198 linux.ko 3 1 0xc0b90000 125a0 if_ath.ko 4 3 0xc0ba3000 26b70 ath_hal.ko 5 2 0xc0bca000 472c ath_rate.ko 6 1 0xc0bcf000 55e8 snd_ich.ko 7 2 0xc0bd5000 268b8 sound.ko 8 1 0xc0bfc000 56e4 acpi_video.ko 9 3 0xc0c02000 63c94 acpi.ko 10 1 0xc0c66000 2730 acpi_sony.ko 11 1 0xc0c69000 2fac wlan_wep.ko 12 1 0xc0c6c000 416c atapicam.ko 13 1 0xc0c71000 3694 ucom.ko 14 1 0xc0c75000 9454 cpufreq.ko 15 6 0xc0c7f000 d3b0 netgraph.ko 16 1 0xc0c8d000 8550 ng_ubt.ko 17 1 0xc0c96000 68f8 vkbd.ko 18 1 0xc53bd000 6000 linprocfs.ko 19 4 0xc56be000 2000 ng_bluetooth.ko 20 1 0xc56ec000 d000 ng_hci.ko 21 1 0xc5712000 10000 ng_l2cap.ko 22 1 0xc5722000 1a000 ng_btsocket.ko 23 1 0xc5744000 4000 ng_socket.ko I have several AP's I roam on, but I am about 10ft from the closest AP which I seem to stick with. This also happens at home where I have a single AP (same brand and model). Unloading and reloading the modules helped once if I recall correctly, but not usually. Rebooting the computer does help, but only for some period of time, sometimes many hours, but usually not that long. Anything else I can provide? Thanks! Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 18:23:21 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EFE916A41F for ; Fri, 6 Jan 2006 18:23:21 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3614643D49 for ; Fri, 6 Jan 2006 18:23:21 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id k06INKb9082000; Fri, 6 Jan 2006 10:23:21 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id k06INKYn081999; Fri, 6 Jan 2006 10:23:20 -0800 (PST) Date: Fri, 6 Jan 2006 10:23:20 -0800 (PST) From: Matthew Dillon Message-Id: <200601061823.k06INKYn081999@apollo.backplane.com> To: Chuck Swiger References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> <43BEA718.6090306@mac.com> Cc: Luigi Rizzo , Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 18:23:21 -0000 :Out of curiosity, what is DragonFly doing with the network timing counters (ie, :TCPOPT_TIMESTAMP and the stuff in ), has that been :seperated from HZ too? : :I'm pretty sure that setting: : :#define TCPTV_MSL ( 30*hz) /* max seg lifetime (hah!) */ : :...with HZ=1000 or more is not entirely correct. :-) Not when it started with :the TTL in hops being equated to one hop per second... : :-- :-Chuck Well, you know what they say... if it aint broke, don't fix it. In this case the network stacks use that wonderful callwheel code that was written years ago (in FreeBSD). SYSTIMERS aren't designed to handle billions of timers like the callwheel code is so it wouldn't be a proper application. The one change I made to the callwheel code was to make it per-cpu in order to guarentee that e.g. a device driver that installs an interrupt and a callout would get both on the same cpu and thus be able to use normal critical sections to interlock between them. This is a particularly important aspect of our lockless per-cpu tcp protocol threads. DragonFly's crit_enter()/crit_exit() together only take 9ns (with INVARIANTS turned on), whereas the minimum non-contended inline mutex (lwkt_serialize_enter()/exit()) takes around 20ns. I don't know what edge cases exist when 'hz' is set so high. Since we don't use hz for things that would normally require it to be set to a high frequency, we just leave hz set to 100. -- One side note. I've found both our userland (traditional bsd4) and our LWKT scheduler to be really finicky about being properly woken up via AST when a reschedule is required. Preemption by <> threads is not beneficial at all since most kernel ops take < 1uS to execute major operations. 'hz' is not relevant because it only effects processes operating in batch. But 'forgetting' to queue an AST to reschedule a thread ASAP (without preempting) when you are supposed to can result in terrible interactive response because you have processes winding up using their whole quantum before they realize that they should have rescheduled. I've managed to break this three times over the years in DragonFly... stupid things like forgetting a crit_exit() or clearing the reschedule bit without actually rescheduling or doing the wrong check in doreti(), etc. The bugs often went unnoticed for weeks because it wasn't noticed until someone did some heavily cpu-bound work or test. It is the A#1 problem that you have to look for if you have scheduler issues. All non-interrupt-thread preemption accomplishes is to blow up your caches and prevent you from being able to aggregate work between threads (which could be especially important since your I/O is threaded in FreeBSD). -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 19:44:45 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4140816A41F; Fri, 6 Jan 2006 19:44:45 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C6043D48; Fri, 6 Jan 2006 19:44:43 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail01.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k06Jib48032747 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 7 Jan 2006 06:44:37 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k06JiaHh055435; Sat, 7 Jan 2006 06:44:36 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k06Jia2n055434; Sat, 7 Jan 2006 06:44:36 +1100 (EST) (envelope-from pjeremy) Date: Sat, 7 Jan 2006 06:44:36 +1100 From: Peter Jeremy To: freebsd-stable@freebsd.org, current Message-ID: <20060106194436.GD51452@cirb503493.alcatel.com.au> References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> <20060105184147.GD69162@funkthat.com> <20060106110318.GF54324@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106110318.GF54324@svcolo.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 19:44:45 -0000 On Fri, 2006-Jan-06 03:03:18 -0800, Jo Rhett wrote: >> Bottom line: Once code exists, then support can be talked about.. > >This is bullhockey and you know it. Once the project is done, we'll >authorize a budget for it? Once the season is over we'll know who should >be on the starting team? In general, volunteer projects have a surfeit of ideas and a shortage of real implementations. The Project is never going to agree to import an idea without some substance. > Yeah, hindsight is sweet. But this isn't a >simple change. It will require very close integration with the installation >and kernel modules at least (and probably more). So having some sort of >consensus that (a) the project has interest and (b) what flavors would be >acceptable to the existing groups - are both necessary for this project to >even mumble it's first line of code. In which case you need to move this thread to freebsd-arch where these sort of issues are discussed. You need to clearly define your goals and suggest a design to meet them. If your idea has merit, you'll be able to convince at least one committer to work with you to implement your design. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 20:00:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7049916A41F; Fri, 6 Jan 2006 20:00:29 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCA4D43D46; Fri, 6 Jan 2006 20:00:28 +0000 (GMT) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2ADA552C88; Fri, 6 Jan 2006 21:00:26 +0100 (CET) Received: from localhost (dkr191.neoplus.adsl.tpnet.pl [83.24.21.191]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id D052950F92; Fri, 6 Jan 2006 21:00:16 +0100 (CET) Date: Fri, 6 Jan 2006 21:00:10 +0100 From: Pawel Jakub Dawidek To: Scott Long Message-ID: <20060106200009.GA53067@garage.freebsd.pl> References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline In-Reply-To: <43BA9C5C.9010307@samsco.org> X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 User-Agent: mutt-ng/devel-r535 (FreeBSD) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=BAYES_00,RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 20:00:29 -0000 --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: +> David O'Brien wrote: +>=20 +> >Just in case anyone thought the bug had been fixed... +> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 +> >panic: ufs_dirbad: bad dir +> >cpuid =3D 1 +> >KDB: stack backtrace: +> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e =3D = kdb_backtrace+0x2e +> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 =3D panic+0x= 128 +> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d =3D ufs_dirb= ad+0x4d +> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = =3D ufs_lookup+0x3ad +> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0= xc068cd4e =3D VOP_CACHEDLOOKUP_APV+0x9e +> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc05= 7275a =3D vfs_cache_lookup+0xca +> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 =3D= VOP_LOOKUP_APV+0xa6 +> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e =3D lookup+0x44e +> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf =3D namei+0x44f +> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd =3D kern_stat+0= x3d +> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f =3D stat+0x2f +> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 =3D syscall+0x323 +> >Xint0x80_syscall() at 0xc066d33f =3D Xint0x80_syscall+0x1f +>=20 +> Please include the console printf that is right about the panic message. +> It will say either something about a mangled entry or an isize too +> small. Since this problem is happening consistently for you, but there +> seem to be no other problem reports from others, I'd highly suspect that +> you have filesystem damage that isn't getting detected by fsck. I assum= e that you are running fsck in the foreground and not in the background, ye= s? The easiest solution=20 +> here might be to figure out which +> directory is causing the problem, and just clri its inode and then clean +> up the mess. I'm able to reproduce it with newly newfs(8)ed file system: /mnt: bad dir ino 17382405 at offset 0: mangled entry panic: ufs_dirbad: bad dir KDB: enter: panic [...] db> tr =20 Tracing pid 427 tid 100057 td 0xc7ccaa80 kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup+0x39f VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at VOP_C= ACHEDLOOKUP_APV+0xc4 vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0xc8 VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x28176efb, esp =3D 0xbfbf= e90c, ebp =3D 0xbfbfea48 --- --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDvsxJForvXbEpPzQRAju3AJwLmWmSNIi5PpkON09wtLlaGvZgcgCfVkbd QPAGBcCIQ2q0PfVrabWLqp8= =dY0H -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 20:31:23 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74ACA16A41F; Fri, 6 Jan 2006 20:31:23 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail24.syd.optusnet.com.au (mail24.syd.optusnet.com.au [211.29.133.165]) by mx1.FreeBSD.org (Postfix) with ESMTP id B98BB43D46; Fri, 6 Jan 2006 20:31:22 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k06KVKCQ001186 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 7 Jan 2006 07:31:21 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k06KVKHh055483; Sat, 7 Jan 2006 07:31:20 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k06KVKvY055482; Sat, 7 Jan 2006 07:31:20 +1100 (EST) (envelope-from pjeremy) Date: Sat, 7 Jan 2006 07:31:20 +1100 From: Peter Jeremy To: freebsd-stable@freebsd.org, current Message-ID: <20060106203120.GE51452@cirb503493.alcatel.com.au> References: <20060105093220.GJ1358@svcolo.com> <200601050947.k059lctk024288@hugo10.ka.punkt.de> <20060106103440.GB54324@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106103440.GB54324@svcolo.com> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: Subject: Re: FreeBSD Update is the binary update solution [Re: HEADS UP: Release schedule for 2006] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 20:31:23 -0000 On Fri, 2006-Jan-06 02:34:40 -0800, Jo Rhett wrote: >On Thu, Jan 05, 2006 at 10:47:38AM +0100, Patrick M. Hausen wrote: >> While I agree with much of your reasoning, I know exactly zero >> people running a modified kernel of any version of Windows, >> Mac OS X or Solaris, to name just three commercial OS's. > >You're tickling a different subject here. All three of these operating >systems have loadable kernel modules that work. As does FreeBSD. > I mean, they dynamically >load the modules they need, and you can disable kernel modules in >configuration files. FreeBSD has loadable kernel modules, but they don't >autoload (you have to modify rc files) This isn't quite true. FreeBSD does not currently have the tools to automatically load kernel modules for most hardware device drivers and they need to either be built into the kernel or specified in loader.conf. Writing a tool to do this automatically would be fairly simple - either use pciconf(8) and a database of PCI ID to driver mappings or (as Solaris and X do) load every module and see if it can attach to anything, unload it if it can't. To date, no-one has been sufficiently motivated to do so. FreeBSD will autoload kernel modules for many software functions if their functionality is required (NFS, SysV IPC, firewalls). In some cases this is automatic (NFS client loads automatically if NFS filesystems are found). In other cases, (eg firewalls) you need to configure the functionality anyway. > and you can't trim down the kernel >to minimize unused memory without recompiling. In the absence of tools to automatically detect your configuration and load the appropriate modules, GENERIC includes a fairly standard set of drivers that also exist as modules. GENERIC probably could be cut down somewhat but this isn't the forum to discuss that. >To give you a specific example: if we could remove NFS and the 3ware >driver from the kernel in a configuration file, we could probably run >GENERIC. IMHO, NFS server could be removed without problems (it will autoload), as could tw{a,e} (which are loadable). NFS client can't be removed because it has to be built in to support diskless operation. >hog we have to remove on small footprint systems FreeBSD has never claimed to optimally support small footprint systems without customisation. There are too many variables and some kernel functionality can't be readily converted to modules (eg IPv6 support). In any case, the way to minimise the kernel footprint is to statically load all the required functionality and not have any modules. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 21:16:46 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F1AF16A420; Fri, 6 Jan 2006 21:16:46 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id D96F243D48; Fri, 6 Jan 2006 21:16:45 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k06LGb9h003864; Fri, 6 Jan 2006 13:16:37 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k06LGa4a003863; Fri, 6 Jan 2006 13:16:36 -0800 (PST) (envelope-from jmg) Date: Fri, 6 Jan 2006 13:16:36 -0800 From: John-Mark Gurney To: "Daniel O'Connor" , freebsd-stable@freebsd.org, Chuck Swiger , current Message-ID: <20060106211636.GF69162@funkthat.com> Mail-Followup-To: Daniel O'Connor , freebsd-stable@freebsd.org, Chuck Swiger , current References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> <20060105184147.GD69162@funkthat.com> <20060106110318.GF54324@svcolo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060106110318.GF54324@svcolo.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 21:16:46 -0000 Jo Rhett wrote this message on Fri, Jan 06, 2006 at 03:03 -0800: > On Thu, Jan 05, 2006 at 10:41:47AM -0800, John-Mark Gurney wrote: > > I believe core has a policy of never supporting vaporware... There is > > always the chicken and egg problem with arguments like this... I'll > > code this if you agree to support it and maintain it/I will agree to > > support it once you code it... In FreeBSD, and many open source > > projects, no code, no support, how can you support or even agree to > > support something that doesn't exist? And then as soon as FreeBSD > > agrees to support something that doesn't exist, either a) other people who > > were interested in the project stop, even if you end up never producing > > a bit of code, or b) someone else produces better code, drops the > > support for the original, but then the author complains about being > > told they'd support his code, and going with another code base... > > > > Bottom line: Once code exists, then support can be talked about.. > > This is the chicken and egg problem that will kill FreeBSD. I don't And many other open source software projects... FreeBSD isn't unique in this.. I've submitted patches to many other projects just to have them ignored for years too... It's a problem of voluteer orginizations.. > bother writing up patches for FreeBSD because every time I do they sit in a > PR and get ignored for several years. Then someone that does have commit > rights makes their own patch (which often is less useful) but they own it > and the best I've ever succeeded at was convincing them to put some of the > ideas from my patch into their code. > > Note that none of these patches were ever rejected for any technical or > political or any other reason. They just don't get paid attention to. > > Thus, I try to get consensus that the idea has merit. IF freebsd > committers can be bothered to pay attention to the idea, I'll write code > for it. But I'm too old and tired to spend another week writing up > something that will get ignored for X years and then dropped for obsoletion > again. You're trying to target to large of an audience... You need to get _A_ committer interested in your work, and get HIM to guide you and commit your work... > AND there are a lot of opinions and politics around how to version the core > that have nothing to do with code. There's no value in writing code that > will be ignored because it doesn't agree with -core's view of "should be". > I'm a coder, not a politician. If we can get consensus on what type of > implementation would be acceptable to core, then I and many others would be > happy to write code to implement this idea. But this is a considerable > amount of work that will be closely tied to the operation system > installation. It's not something that you can churn out 7 different > implementations of just to see which one fits the current polical > environment. stop talking about core... -core makes absolutely no technical decisions about how FreeBSD is.. it is the developers, and previously there was a technical review board for settling differences between developers that were pure "technical" in nature... And if you claim you didn't know this, then you better read the email you respond to more closely, since this has been pointed out to you numerous times.. and you said in another email: > First, this is obvious and true for all open source projects. But no, > FreeBSD _never_ advances because someone writes code that does something > well. FreeBSD _only_ advances when the core developers agree that this > thing is worthy of their interest. hmmm... you really are choosing to completely ignore what people have said about core, that at least you did add developers after core, which makes it appear less likely that you're talking about -core.. but lots of stuff gets done w/o core developers... I did lots of work on -sparc64, and I'm pretty sure you wouldn't call me a core developer.. and I also got TS-7200 arm support (though it hasn't been committed to cvs due to issues that I haven't resolved with device configuration)... As for the whole installation thing, you need to talk with re (release engineering) as they are the ones to really have final say in what installation and releases look like... > Back to your finale: > > > Bottom line: Once code exists, then support can be talked about.. > > This is bullhockey and you know it. Once the project is done, we'll > authorize a budget for it? Once the season is over we'll know who should FreeBSD isn't commercial, so you can't talk about budgets... And most orgs want some sort of prototypes and feasibility study done before they'll commit any budget to it... > be on the starting team? Yeah, hindsight is sweet. But this isn't a > simple change. It will require very close integration with the installation > and kernel modules at least (and probably more). So having some sort of > consensus that (a) the project has interest and (b) what flavors would be > acceptable to the existing groups - are both necessary for this project to > even mumble it's first line of code. Yeh, you can get a & b, but you can't get commitment to accept what comes out of a & b... Unless of course you can make the time between findout what a & b are and having code that implements a & b down to zero... None of this prevents you from getting a basic prototype that works, but isn't complete with bells and whistles.. Look at what Colin did with FreeBSD update, I didn't see him demanding anyone in FreeBSD to sign off on his work... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 22:33:18 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 58AB516A41F for ; Fri, 6 Jan 2006 22:33:18 +0000 (GMT) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1F9B43D45 for ; Fri, 6 Jan 2006 22:33:17 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.199] ([10.0.0.199]) (authenticated bits=0) by ebb.errno.com (8.12.9/8.12.6) with ESMTP id k06MXBo7038414 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Jan 2006 14:33:12 -0800 (PST) (envelope-from sam@errno.com) Message-ID: <43BEEFF2.6060300@errno.com> Date: Fri, 06 Jan 2006 14:32:18 -0800 From: Sam Leffler Organization: Errno Consulting User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <200601060340.35999.akbeech@gmail.com> <43BE7888.8060302@centtech.com> <43BEA035.9030704@errno.com> <43BEAEB3.1050105@centtech.com> In-Reply-To: <43BEAEB3.1050105@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 22:33:18 -0000 Eric Anderson wrote: > Sam Leffler wrote: > >> Eric Anderson wrote: >> >>> Beech Rintoul wrote: >>> >>>> I have noticed that for about the past month or so I've been getting >>>> hundreds of the following every day in /var/log/messages: >>>> >>>> +ath0: link state changed to DOWN >>>> +ath0: link state changed to UP >>>> >>>> It doesn't seem to affect connectivity, but it's really annoying in >>>> the security report. Is there anything I can do to stop this? I'm >>>> running -CURRENT from yesterday. I have built Sam's new drivers, but >>>> this problem started long before that and was not affected by the >>>> upgrade. The lease on the AP I'm connecting to is good for 24 hours >>>> so I don't think that's an issue. I looked at the traffic with >>>> ethereal and everything looks normal. I'm getting sorely tempted to >>>> go back to isc-dhclient and see if this goes away, but I thought I >>>> would ask here first. >>>> >>>> >>>> >>> >>> I've noticed something recently too - my ath device frequently stops >>> working, and I get this in messages: >>> >>> Jan 6 06:19:48 neutrino kernel: ath0: link state changed to DOWN >>> Jan 6 06:20:35 neutrino kernel: ath0: device timeout >>> Jan 6 06:20:56 neutrino kernel: ath0: device timeout >>> Jan 6 06:21:06 neutrino kernel: ath0: device timeout >>> Jan 6 06:21:59 neutrino last message repeated 2 times >>> Jan 6 06:22:25 neutrino kernel: ath0: device timeout >>> Jan 6 06:23:03 neutrino kernel: ath0: link state changed to UP >>> Jan 6 06:41:35 neutrino kernel: ath0: link state changed to DOWN >>> Jan 6 06:42:03 neutrino kernel: Memory modified after free >>> 0xc5402000(2048) val=11600000 @ 0xc5402000 >>> Jan 6 06:42:04 neutrino kernel: ath0: link state changed to UP >>> Jan 6 06:42:08 neutrino kernel: ath0: device timeout >>> Jan 6 06:42:09 neutrino kernel: ath0: link state changed to DOWN >>> Jan 6 06:43:12 neutrino kernel: ath0: link state changed to UP >>> Jan 6 06:43:17 neutrino kernel: ath0: device timeout >>> Jan 6 06:43:17 neutrino kernel: ath0: link state changed to DOWN >>> Jan 6 06:43:33 neutrino kernel: ath0: device timeout >>> Jan 6 06:44:10 neutrino kernel: ath0: device timeout >>> [and so on] >>> >>> >>> I would say this started happening for me in the last 2 weeks. >> >> >> >> Device timeouts should not happen; it means the driver submitted a >> packet to the card and didn't get a tx complete interrupt back in 5 >> seconds. >> >> It's unclear if the "modified after free" msgs is related and w/o more >> diagnostic info it's really hard to say why you're seeing device >> timeouts. > > > > Ok - wasn't sure if was related or not, so I posted it anyway. Before > about 2 weeks ago, ath has been rock solid for me. The last change I made to the ath driver was >1 month ago and that was to delete code. Recent changes to the net80211 layer mostly add code that is not yet used. If a code change is affecting operation it seems likely it's elsewhere in the system. If you can rollback code to the point where things work and they return to operation then perhaps you can pinpoint the problem if it's s/w. > >> >>> >>> I'm running -current from Jan 4th. All kinds of system information >>> is here: >>> >>> http://googlebit.com/freebsd/ >> >> >> >> Most of the useful info is not there. No boot dmsg or indication of >> what your network config is. No indication of the hal version or the >> mac+phy revs. yada yada yada... > > > > Yea, I see that now. Sorry - here's dmesg.boot: > http://googlebit.com/freebsd/dmesg.boot-20060106 > > And some additional info: > /etc/rc.conf snippet: > ifconfig_em0="DHCP" > ifconfig_ath0="WPA DHCP" > > /etc/wpa_supplicant.conf: > ctrl_interface=/var/run/wpa_supplicant > ctrl_interface_group=wheel > > network={ > ssid="centtech" > key_mgmt=NONE > wep_key0=0E...CD > wep_tx_keyidx=0 > scan_ssid=1 > priority=5 > } > > $ kldstat > Id Refs Address Size Name > 1 36 0xc0400000 7707a4 kernel > 2 2 0xc0b71000 1e198 linux.ko > 3 1 0xc0b90000 125a0 if_ath.ko > 4 3 0xc0ba3000 26b70 ath_hal.ko > 5 2 0xc0bca000 472c ath_rate.ko > 6 1 0xc0bcf000 55e8 snd_ich.ko > 7 2 0xc0bd5000 268b8 sound.ko > 8 1 0xc0bfc000 56e4 acpi_video.ko > 9 3 0xc0c02000 63c94 acpi.ko > 10 1 0xc0c66000 2730 acpi_sony.ko > 11 1 0xc0c69000 2fac wlan_wep.ko > 12 1 0xc0c6c000 416c atapicam.ko > 13 1 0xc0c71000 3694 ucom.ko > 14 1 0xc0c75000 9454 cpufreq.ko > 15 6 0xc0c7f000 d3b0 netgraph.ko > 16 1 0xc0c8d000 8550 ng_ubt.ko > 17 1 0xc0c96000 68f8 vkbd.ko > 18 1 0xc53bd000 6000 linprocfs.ko > 19 4 0xc56be000 2000 ng_bluetooth.ko > 20 1 0xc56ec000 d000 ng_hci.ko > 21 1 0xc5712000 10000 ng_l2cap.ko > 22 1 0xc5722000 1a000 ng_btsocket.ko > 23 1 0xc5744000 4000 ng_socket.ko > > I have several AP's I roam on, but I am about 10ft from the closest AP > which I seem to stick with. This also happens at home where I have a > single AP (same brand and model). > > Unloading and reloading the modules helped once if I recall correctly, > but not usually. Rebooting the computer does help, but only for some > period of time, sometimes many hours, but usually not that long. > > Anything else I can provide? You mean like your network config? I see you're using wpa but 11g, 11a, 11b? Have you tried operating w/o WPA? Different channel? Different card? Since there don't appear to be code changes related to your issue you need to work on isolating what's changed or is failing. Sam From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 23:06:25 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 360D316A41F for ; Fri, 6 Jan 2006 23:06:25 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 883EC43D45 for ; Fri, 6 Jan 2006 23:06:24 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k06N6MJn026688 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Sat, 7 Jan 2006 10:06:23 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id k06N6MHh055706 for ; Sat, 7 Jan 2006 10:06:22 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id k06N6Mlx055705 for freebsd-current@freebsd.org; Sat, 7 Jan 2006 10:06:22 +1100 (EST) (envelope-from pjeremy) Date: Sat, 7 Jan 2006 10:06:22 +1100 From: Peter Jeremy To: freebsd-current@freebsd.org Message-ID: <20060106230622.GH51452@cirb503493.alcatel.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Subject: Sleeping in vm_pageout_flush() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 23:06:25 -0000 vm_pageout_flush() takes an optional flag to control whether or not the pageout should be synchronous. If the object passed is kernel_object, the pageout is forced synchronous. This is causing a problem with trying to make vm_contig_launder_page() support M_NOWAIT. Could someone please explain why the kernel_object can't be asynchronously flushed. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 01:53:08 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E3F7316A41F; Sat, 7 Jan 2006 01:53:08 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C3BF43D45; Sat, 7 Jan 2006 01:53:08 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id k071r63M085566; Fri, 6 Jan 2006 20:53:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k071r6ke061399; Fri, 6 Jan 2006 20:53:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3E1427302F; Fri, 6 Jan 2006 20:53:06 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060107015306.3E1427302F@freebsd-current.sentex.ca> Date: Fri, 6 Jan 2006 20:53:06 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 01:53:09 -0000 TB --- 2006-01-07 00:33:02 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-07 00:33:02 - starting HEAD tinderbox run for alpha/alpha TB --- 2006-01-07 00:33:02 - cleaning the object tree TB --- 2006-01-07 00:33:28 - checking out the source tree TB --- 2006-01-07 00:33:28 - cd /tinderbox/HEAD/alpha/alpha TB --- 2006-01-07 00:33:28 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-07 00:39:24 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-07 00:39:24 - cd /src TB --- 2006-01-07 00:39:24 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2006-01-07 01:44:32 - generating LINT kernel config TB --- 2006-01-07 01:44:32 - cd /src/sys/alpha/conf TB --- 2006-01-07 01:44:32 - /usr/bin/make -B LINT TB --- 2006-01-07 01:44:32 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-07 01:44:32 - cd /src TB --- 2006-01-07 01:44:32 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Jan 7 01:44:32 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_malloc.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_mbuf.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_mib.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_module.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_mtxpool.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/kern/kern_mutex.c /src/sys/kern/kern_mutex.c: In function `mtx_destroy': /src/sys/kern/kern_mutex.c:887: error: structure has no member named `lo_class' *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-07 01:53:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-07 01:53:06 - ERROR: failed to build lint kernel TB --- 2006-01-07 01:53:06 - tinderbox aborted TB --- 1.01 user 4.99 system 4803.95 real From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 02:20:56 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46FB216A41F; Sat, 7 Jan 2006 02:20:56 +0000 (GMT) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (sasami.jurai.net [70.88.158.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE17143D55; Sat, 7 Jan 2006 02:20:52 +0000 (GMT) (envelope-from winter@jurai.net) Received: from sasami.jurai.net (winter@sasami.jurai.net [70.88.158.93]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id k072KMC9034577; Fri, 6 Jan 2006 21:20:27 -0500 (EST) (envelope-from winter@jurai.net) Date: Fri, 6 Jan 2006 21:20:22 -0500 (EST) From: "Matthew N. Dodd" To: Alexander Leidinger In-Reply-To: <20060106164944.39011848@Magellan.Leidinger.net> Message-ID: <20060106211840.O91753@sasami.jurai.net> References: <17341.65102.980006.14057@canoe.dclg.ca> <20060105.230253.93225432.imp@bsdimp.com> <20060106164944.39011848@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [70.88.158.93]); Fri, 06 Jan 2006 21:20:33 -0500 (EST) Cc: freebsd-current@freebsd.org, freebsd-usb@freebsd.org, "M. Warner Losh" , dgilbert@dclg.ca Subject: Re: Disappearing memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 02:20:56 -0000 On Fri, 6 Jan 2006, Alexander Leidinger wrote: > On Thu, 05 Jan 2006 23:02:53 -0700 (MST) > "M. Warner Losh" wrote: > >> In message: <17341.65102.980006.14057@canoe.dclg.ca> >> David Gilbert writes: >> : Maybe what we need is 'usbcontrol' ... allowing us to reset (or at >> : least reset the OSs idea of) one usb device. >> >> I've wanted a generic way to send messages to busses about children >> and to devices. PC Card and CardBus could use that for power down as >> well.. > > If you aren't going to write it yourself, feel free to write up a > (plain-text) entry for http://www.FreeBSD.org/projects/ideas/ and send > it to us. I wrote something simple a while back that does some of this: ftp://ftp.jurai.net/users/winter/foot.tar.gz It allows newbus methods to be invoked for a given device. From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 03:01:20 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7010816A41F for ; Sat, 7 Jan 2006 03:01:20 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from msgmmp-4.gci.net (msgmmp-4.gci.net [209.165.130.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41BCE43D48 for ; Sat, 7 Jan 2006 03:01:19 +0000 (GMT) (envelope-from akbeech@gmail.com) Received: from stargate.akparadise.com ([209.124.141.64]) by msgmmp-4.gci.net (Sun Java System Messaging Server 6.2-3.03 (built Jun 27 2005)) with ESMTPA id <0ISP003E9CE22SA0@msgmmp-4.gci.net> for freebsd-current@freebsd.org; Fri, 06 Jan 2006 18:01:18 -0900 (AKST) Received: by stargate.akparadise.com (Postfix, from userid 0) id 65F073FA8; Fri, 06 Jan 2006 18:01:14 -0900 (AKST) Date: Fri, 06 Jan 2006 18:01:01 -0900 From: Beech Rintoul In-reply-to: <43BE9F0A.5000200@errno.com> To: Sam Leffler Message-id: <200601061801.12841.akbeech@gmail.com> Organization: NorthWind Communications MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1203715.moLr5JRJVm; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200601060340.35999.akbeech@gmail.com> <43BE9F0A.5000200@errno.com> User-Agent: KMail/1.8.3 Cc: freebsd-current@freebsd.org Subject: Re: /dev/ath log messages X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 03:01:20 -0000 --nextPart1203715.moLr5JRJVm Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 06 January 2006 07:47 am, Sam Leffler wrote: > Beech Rintoul wrote: > > I have noticed that for about the past month or so I've been getting > > hundreds of the following every day in /var/log/messages: > > > > +ath0: link state changed to DOWN > > +ath0: link state changed to UP > > > > It doesn't seem to affect connectivity, but it's really annoying in the > > security report. Is there anything I can do to stop this? I'm running > > -CURRENT from yesterday. I have built Sam's new drivers, but this probl= em > > started long before that and was not affected by the upgrade. The lease > > on the AP I'm connecting to is good for 24 hours so I don't think that's > > an issue. I looked at the traffic with ethereal and everything looks > > normal. I'm getting sorely tempted to go back to isc-dhclient and see if > > this goes away, but I thought I would ask here first. > > sysctl net.link.log_link_state_change=3D0 > > will make the msgs go away. I do this on all my laptops. > > The issue (which should be in an FAQ) is that your station is > reassociating to the ap, typically because you are idle. Each time this > happens the link state goes down+up. The dhcp lease is not relevant. > You might be able to tweak ap parameters to increase the idle timeout > but aside from the link state msgs there's no reason to. > > Sam Thanks Sam, that did fix my problem. That was really annoying, especially I= f I=20 wanted to look at dmesg and that was all that was there. Maybe that should= =20 default to "0" with the option to turn it on as I'm sure most users don't=20 want all those messages. just my $.02 Beech =2D-=20 =2D------------------------------------------------------------------------= =2D------------- Beech Rintoul - System Administrator - akbeech@gmail.com /"\ ASCII Ribbon Campaign | NorthWind Communications \ / - NO HTML/RTF in e-mail | 201 East 9th Avenue Ste.310 X - NO Word docs in e-mail | Anchorage, AK 99501 / \ - Please visit Alaska Paradise - http://akparadise.byethost33.com =2D------------------------------------------------------------------------= =2D------------- --nextPart1203715.moLr5JRJVm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDvy74Vq19LUoGB+MRAkO3AJ9/WZtz4D97k55aWPlO6JvFVmtQjQCeP/o5 n1XElXSueSsLOSX+ULb721Q= =PLqx -----END PGP SIGNATURE----- --nextPart1203715.moLr5JRJVm-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 03:40:10 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F32B16A4A3; Sat, 7 Jan 2006 03:40:10 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93A0E43D46; Sat, 7 Jan 2006 03:40:09 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id k073e7aD081614; Fri, 6 Jan 2006 22:40:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id k073e8kt016184; Fri, 6 Jan 2006 22:40:08 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 19E0D7302F; Fri, 6 Jan 2006 22:40:08 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060107034008.19E0D7302F@freebsd-current.sentex.ca> Date: Fri, 6 Jan 2006 22:40:08 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 03:40:11 -0000 TB --- 2006-01-07 01:53:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-01-07 01:53:06 - starting HEAD tinderbox run for amd64/amd64 TB --- 2006-01-07 01:53:06 - cleaning the object tree TB --- 2006-01-07 01:53:40 - checking out the source tree TB --- 2006-01-07 01:53:40 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2006-01-07 01:53:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2006-01-07 01:59:39 - building world (CFLAGS=-O2 -pipe) TB --- 2006-01-07 01:59:39 - cd /src TB --- 2006-01-07 01:59:39 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2006-01-07 03:31:16 - generating LINT kernel config TB --- 2006-01-07 03:31:16 - cd /src/sys/amd64/conf TB --- 2006-01-07 03:31:16 - /usr/bin/make -B LINT TB --- 2006-01-07 03:31:16 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-01-07 03:31:16 - cd /src TB --- 2006-01-07 03:31:16 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Jan 7 03:31:16 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_malloc.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_mbuf.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_mib.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_module.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_mtxpool.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/kern_mutex.c /src/sys/kern/kern_mutex.c: In function `mtx_destroy': /src/sys/kern/kern_mutex.c:887: error: structure has no member named `lo_class' *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-01-07 03:40:07 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-01-07 03:40:07 - ERROR: failed to build lint kernel TB --- 2006-01-07 03:40:07 - tinderbox aborted TB --- 1.29 user 6.80 system 6421.50 real From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 05:04:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5264C16A41F; Sat, 7 Jan 2006 05:04:29 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F75443D48; Sat, 7 Jan 2006 05:04:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.217.198] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1Ev6Fe2Sft-0001Ke; Sat, 07 Jan 2006 06:04:27 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 7 Jan 2006 06:04:59 +0100 User-Agent: KMail/1.8.3 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8358241.Rc3f7sHePR"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601070605.05535.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Damien Bergamini Subject: Intel 2915abg and 11a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 05:04:29 -0000 --nextPart8358241.Rc3f7sHePR Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, is anyone successfully running their Intel 2915abg card in 11a mode with th= e=20 iwi(4) driver? I am wondering, because since 11a has been enabled in the=20 driver I can't use it anymore. "fatal error" while scanning through the 11= a=20 channels. No matter what firmware I use. Please let me know - if there are no positive reports I'd like to disable 1= 1a=20 for the moment to have the driver working in 11b/g mode at least - which it= =20 does. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart8358241.Rc3f7sHePR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDv0wBXyyEoT62BG0RAmWmAJ9ClDSScYpIPFWVw3FUB91Sk/UtpACfRnjA 11XLZrt0RmdFix704bIMIyg= =9x+C -----END PGP SIGNATURE----- --nextPart8358241.Rc3f7sHePR-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 07:25:31 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C28CD16A41F; Sat, 7 Jan 2006 07:25:31 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from vms048pub.verizon.net (vms048pub.verizon.net [206.46.252.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E3D343D46; Sat, 7 Jan 2006 07:25:31 +0000 (GMT) (envelope-from Alex.Kovalenko@verizon.net) Received: from [10.0.3.231] ([70.21.200.69]) by vms048.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0ISP004LGOLZXUR2@vms048.mailsrvcs.net>; Sat, 07 Jan 2006 01:25:12 -0600 (CST) Date: Sat, 07 Jan 2006 02:24:28 -0500 From: "Alexandre \"Sunny\" Kovalenko" In-reply-to: <200601040840.09169.jhb@freebsd.org> To: John Baldwin Message-id: <1136618668.821.2.camel@RabbitsDen> MIME-version: 1.0 X-Mailer: Evolution 2.4.2.1 FreeBSD GNOME Team Port Content-type: text/plain; charset=iso-8859-5 Content-transfer-encoding: 8BIT References: <1136000459.660.12.camel@RabbitsDen> <200601040840.09169.jhb@freebsd.org> Cc: freebsd-current@freebsd.org, Warner Losh Subject: Re: Fatal trap 12 when inserting Linksys WPC55AG cardbus card on 12/30 -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 07:25:31 -0000 On Wed, 2006-01-04 at 08:40 -0500, John Baldwin wrote: > On Friday 30 December 2005 10:40 pm, Alexandre "Sunny" Kovalenko wrote: > > This happens on -CURRENT as of 8:00AM, December 30: > > > > Unread portion of the kernel message buffer: > > Status is 0x30000821 d8bb0000 > > cbb0: card inserted: event=0x00000000, state=30000821 > > cbb0: cbb_power: 3V > > Interrupt storm detected on "irq10:"; throttling interrupt source > > > > > > Fatal trap 12: page fault while in kernel mode > > fault virtual address = 0xda183000 > > fault code = supervisor read, page not present > > instruction pointer = 0x20:0xc04ac0f8 > > stack pointer = 0x28:0xd8b62728 > > frame pointer = 0x28:0xd8b62738 > > 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 = 21 (cbb0) > > Does this still occur on recent HEAD? There have been several cardbus changes > in the past few days. Sorry for the delay in answer -- day job decided to interfere with vengeance. This is definitely fixed in the -CURRENT as of late afternoon January 7th. Thank you, -- Alexandre "Sunny" Kovalenko (¾ÛÕÚáÐÝÔà ºÞÒÐÛÕÝÚÞ) From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 11:03:56 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B8A016A41F; Sat, 7 Jan 2006 11:03:56 +0000 (GMT) (envelope-from bland@FreeBSD.org) Received: from mvs4.plala.or.jp (c158132.vh.plala.or.jp [210.150.158.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78D2943D45; Sat, 7 Jan 2006 11:03:54 +0000 (GMT) (envelope-from bland@FreeBSD.org) Received: from hub.bbnest.net ([219.165.238.110]) by mvs4.plala.or.jp with ESMTP id <20060107110353.JOHN4019.mvs4.plala.or.jp@hub.bbnest.net>; Sat, 7 Jan 2006 20:03:53 +0900 Received: from [10.0.0.2] (nest.bbnest.net [10.0.0.2]) by hub.bbnest.net (8.13.4/8.13.4) with ESMTP id k07B3qco028554; Sat, 7 Jan 2006 20:03:53 +0900 (JST) (envelope-from bland@FreeBSD.org) Message-ID: <43BF9F42.3090809@FreeBSD.org> Date: Sat, 07 Jan 2006 20:00:18 +0900 From: Alexander Nedotsukov User-Agent: Thunderbird 1.5 (X11/20051227) MIME-Version: 1.0 To: Max Laier References: <200601070605.05535.max@love2party.net> In-Reply-To: <200601070605.05535.max@love2party.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Damien Bergamini Subject: Re: Intel 2915abg and 11a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 11:03:56 -0000 FYI. I tried iwi(4) before 6.0-RELEASE (on 6-RCx) series w/o any success. It was ad-hoc mode connection. If I properly recall w/ debug output enabled I got some invalid link state messages during association. Networks scan was ok. All the best, Alexander. Max Laier wrote: > Hi, > > is anyone successfully running their Intel 2915abg card in 11a mode with the > iwi(4) driver? I am wondering, because since 11a has been enabled in the > driver I can't use it anymore. "fatal error" while scanning through the 11a > channels. No matter what firmware I use. > > Please let me know - if there are no positive reports I'd like to disable 11a > for the moment to have the driver working in 11b/g mode at least - which it > does. > > From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 12:05:42 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CCE716A41F; Sat, 7 Jan 2006 12:05:42 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B18643D60; Sat, 7 Jan 2006 12:05:35 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 9C0BF20A9; Sat, 7 Jan 2006 13:05:13 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.2/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 7DC8F20A8; Sat, 7 Jan 2006 13:05:13 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 5833A33C3E; Sat, 7 Jan 2006 13:05:13 +0100 (CET) To: Jo Rhett References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> <20060105184147.GD69162@funkthat.com> <20060106110318.GF54324@svcolo.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Sat, 07 Jan 2006 13:05:13 +0100 In-Reply-To: <20060106110318.GF54324@svcolo.com> (Jo Rhett's message of "Fri, 6 Jan 2006 03:03:18 -0800") Message-ID: <86irsw1bwm.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org, current Subject: Re: Fast releases demand binary updates.. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 12:05:42 -0000 Jo Rhett writes: > On Thu, Jan 05, 2006 at 10:41:47AM -0800, John-Mark Gurney wrote: > > Bottom line: Once code exists, then support can be talked about.. > This is the chicken and egg problem that will kill FreeBSD. So *you're* the AC that keeps predicting the death of *BSD on /.! > I don't bother writing up patches for FreeBSD because every time I > do they sit in a PR and get ignored for several years. Then someone > that does have commit rights makes their own patch (which often is > less useful) but they own it and the best I've ever succeeded at was > convincing them to put some of the ideas from my patch into their > code. Every single time? There are five PRs with your name on in GNATS (assuming you and are one and same) ports/76013 - patch committed after four months ports/76019 - superceded after a month ports/76041 - duplicate of ports/76013 ports/76724 - patch committed after a week docs/87445 - immediately adopted by a committer, being worked on Oh, how we have wronged you! Please let us know how we may correct this grievous injustice! DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 16:24:18 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 002CB16A49E for ; Sat, 7 Jan 2006 16:24:17 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 179B743D46 for ; Sat, 7 Jan 2006 16:24:16 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 52667 invoked from network); 7 Jan 2006 16:27:40 -0000 Received: from dotat.atdotat.at (HELO [62.48.0.47]) ([62.48.0.47]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 7 Jan 2006 16:27:40 -0000 Message-ID: <43BFEB2E.4040303@freebsd.org> Date: Sat, 07 Jan 2006 17:24:14 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217 MIME-Version: 1.0 To: Matthew Dillon References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> In-Reply-To: <200601060636.k066aNYn079015@apollo.backplane.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Luigi Rizzo , Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 16:24:18 -0000 Matthew Dillon wrote: > :Luigi Rizzo wrote: > :> On Sun, Jan 01, 2006 at 10:59:14AM +0100, Poul-Henning Kamp wrote: > :>>http://phk.freebsd.dk/misc/leapsecond.txt > :>> > :>>Notice how CLOCK_REALTIME recycles the 1136073599 second. > :> > :> on a related topic, any comments on this one ? > :> Is this code that we could use ? > :> > :> http://www.dragonflybsd.org/docs/nanosleep/ > : > :I ported the tvtohz change from Dragonfly back to 4.10 and 5-STABLE here: > : > :http://www.pkix.net/~chuck/timer/ > : > :...so anyone who wants to experiment can try it out. :-) > : > :-- > :-Chuck > > It isn't so much tvtohz that's the issue, but the fact that the > nanosleep() system call has really coarse hz-based resolution. That's > been fixed in DragonFly and I would recommend that it be fixed in > FreeBSD too. After all, there isn't much of a point having a system > call called 'nanosleep' whos time resolution is coarse-grained and > non-deterministic from computer to computer (based on how hz was > configured). > > Since you seem to be depending on fine-resolution timers more and > more in recent kernels, you should consider porting our SYSTIMER API > to virtualize one-shot and periodic-timers. Look at kern/kern_systimer.c > in the DragonFly source. The code is fairly well abstracted, operates > on a per-cpu basis, and even though you don't have generic IPI messaging > I think you could port it without too much trouble. > > If you port it and start using it you will quickly find that you can't > live without it. e.g. take a look at how we implement network POLLING for > an example of its use. The polling rate can be set to anything at > any time, regardless of 'hz'. Same goes for interrupt rate limiting, > various scheduler timers, and a number of other things. All the things > that should be divorced from 'hz' have been. > > For people worried about edge conditions due to multiple unsynchronized > timers going off I will note that its never been an issue for us, and > in anycase it's fairly trivial to adjust the systimer code to synchronize > periodic time bases which run at integer multiples to timeout at the > same time. Most periodic time bases tend to operate in this fashion > (the stat clock being the only notable exception) so full efficiency > can be retained. But, as I said, I've actually done that and not > noticed any significant improvement in performance so I just don't bother > right now. Matt, I've been testing network and routing performance over the past two weeks with an calibrated Agilent N2X packet generator. My test box is a dual Opteron 852 (2.6Ghz) with Tyan S8228 mobo and Intel dual-GigE in PCI-X-133 slot. Note that I've run all tests with UP kernels em0->em1. For stock FreeBSD-7-CURRENT from 28. Dec. 2005 I've got 580kpps with fast- forward enabled. A em(4) patch from Scott Long implementing a taskqueue raised this to 729kpps. For stock DragonFlyBSD-1.4-RC1 I've got 327kpps and then it breaks down and never ever passes a packet again until a down/up on the receiving interface. net.inet.ip.intr_queue_maxlen has to be set to 200, otherwise it breaks down at 252kpps already. Enabling polling did not make a difference and I've tried various settings and combinations without any apparent effect on performance (burst=1000, each_burst=50, user_frac=1, pollhz=5000). What suprised me most, apart from the generally poor performance, is the sharp dropoff after max pps and the wedging of the interface. I didn't see this kind of behaviour on any other OS I've tested (FreeBSD and OpenBSD). -- Andre From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 16:45:58 2006 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E30E16A41F; Sat, 7 Jan 2006 16:45:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D2E9443D45; Sat, 7 Jan 2006 16:45:57 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k07Gjre7000323; Sat, 7 Jan 2006 09:45:53 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BFF041.8070300@samsco.org> Date: Sat, 07 Jan 2006 09:45:53 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> <20060106200009.GA53067@garage.freebsd.pl> In-Reply-To: <20060106200009.GA53067@garage.freebsd.pl> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@FreeBSD.org, obrien@FreeBSD.org Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 16:45:58 -0000 Pawel Jakub Dawidek wrote: > On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: > +> David O'Brien wrote: > +> > +> >Just in case anyone thought the bug had been fixed... > +> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 > +> >panic: ufs_dirbad: bad dir > +> >cpuid = 1 > +> >KDB: stack backtrace: > +> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e = kdb_backtrace+0x2e > +> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 = panic+0x128 > +> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d = ufs_dirbad+0x4d > +> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = ufs_lookup+0x3ad > +> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0xc068cd4e = VOP_CACHEDLOOKUP_APV+0x9e > +> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc057275a = vfs_cache_lookup+0xca > +> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 = VOP_LOOKUP_APV+0xa6 > +> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e = lookup+0x44e > +> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf = namei+0x44f > +> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd = kern_stat+0x3d > +> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f = stat+0x2f > +> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 = syscall+0x323 > +> >Xint0x80_syscall() at 0xc066d33f = Xint0x80_syscall+0x1f > +> > +> Please include the console printf that is right about the panic message. > +> It will say either something about a mangled entry or an isize too > +> small. Since this problem is happening consistently for you, but there > +> seem to be no other problem reports from others, I'd highly suspect that > +> you have filesystem damage that isn't getting detected by fsck. I assume that you are running fsck in the foreground and not in the background, yes? The easiest solution > +> here might be to figure out which > +> directory is causing the problem, and just clri its inode and then clean > +> up the mess. > > I'm able to reproduce it with newly newfs(8)ed file system: > > /mnt: bad dir ino 17382405 at offset 0: mangled entry > panic: ufs_dirbad: bad dir > KDB: enter: panic > [...] > db> tr > Tracing pid 427 tid 100057 td 0xc7ccaa80 > kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 > panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce > ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e > ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup+0x39f > VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at VOP_CACHEDLOOKUP_APV+0xc4 > vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0xc8 > VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 > lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 > namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 > kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b > lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f > syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 > Xint0x80_syscall() at Xint0x80_syscall+0x1f > --- syscall (190, FreeBSD ELF32, lstat), eip = 0x28176efb, esp = 0xbfbfe90c, ebp = 0xbfbfea48 --- > Since you can reproduce it, can you find out which test it is failing? At the very least we need to add the test to fsck. Scott From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 17:04:38 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 159CC16A41F for ; Sat, 7 Jan 2006 17:04:38 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id B031143D48 for ; Sat, 7 Jan 2006 17:04:36 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: by wproxy.gmail.com with SMTP id 71so2894192wra for ; Sat, 07 Jan 2006 09:04:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aRJmhoFblAtY27BRyOnE6Mg5PlE2K75Qewk+YEXBl5rFcllXkEES3tCv4rIplmzMpP/FGQi2WH13VtXCAZnBTkotvOFb52VmXlsXP3+6Yum7bYkP5wOq1khZuhBNnMcuViC8+nJcR7hNhPE6vCd/yXO0BTF5BXbQrmYETmPrcBc= Received: by 10.64.143.7 with SMTP id q7mr2071737qbd; Sat, 07 Jan 2006 09:04:35 -0800 (PST) Received: by 10.64.178.4 with HTTP; Sat, 7 Jan 2006 09:04:35 -0800 (PST) Message-ID: Date: Sat, 7 Jan 2006 12:04:35 -0500 From: David Rhodus Sender: sdrhodus@gmail.com To: Scott Long In-Reply-To: <43BFF041.8070300@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> <20060106200009.GA53067@garage.freebsd.pl> <43BFF041.8070300@samsco.org> Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 17:04:38 -0000 On 1/7/06, Scott Long wrote: > Pawel Jakub Dawidek wrote: > > > On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: > > +> David O'Brien wrote: > > +> > > +> >Just in case anyone thought the bug had been fixed... > > +> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 > > +> >panic: ufs_dirbad: bad dir > > +> >cpuid =3D 1 > > +> >KDB: stack backtrace: > > +> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e = =3D kdb_backtrace+0x2e > > +> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 =3D pani= c+0x128 > > +> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d =3D ufs_= dirbad+0x4d > > +> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc0616= 5cd =3D ufs_lookup+0x3ad > > +> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) = at 0xc068cd4e =3D VOP_CACHEDLOOKUP_APV+0x9e > > +> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0= xc057275a =3D vfs_cache_lookup+0xca > > +> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66= =3D VOP_LOOKUP_APV+0xa6 > > +> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e =3D lookup+0x= 44e > > +> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf =3D namei+0x44= f > > +> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd =3D kern_st= at+0x3d > > +> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f =3D stat+0x2f > > +> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 =3D syscall+0x323 > > +> >Xint0x80_syscall() at 0xc066d33f =3D Xint0x80_syscall+0x1f > > +> > > +> Please include the console printf that is right about the panic mess= age. > > +> It will say either something about a mangled entry or an isize too > > +> small. Since this problem is happening consistently for you, but th= ere > > +> seem to be no other problem reports from others, I'd highly suspect = that > > +> you have filesystem damage that isn't getting detected by fsck. I a= ssume that you are running fsck in the foreground and not in the background= , yes? The easiest solution > > +> here might be to figure out which > > +> directory is causing the problem, and just clri its inode and then c= lean > > +> up the mess. > > > > I'm able to reproduce it with newly newfs(8)ed file system: > > > > /mnt: bad dir ino 17382405 at offset 0: mangled entry > > panic: ufs_dirbad: bad dir > > KDB: enter: panic > > [...] > > db> tr > > Tracing pid 427 tid 100057 td 0xc7ccaa80 > > kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 > > panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce > > ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e > > ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup+= 0x39f > > VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at V= OP_CACHEDLOOKUP_APV+0xc4 > > vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0x= c8 > > VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 > > lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 > > namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 > > kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b > > lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f > > syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 > > Xint0x80_syscall() at Xint0x80_syscall+0x1f > > --- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x28176efb, esp =3D 0x= bfbfe90c, ebp =3D 0xbfbfea48 --- > > > > Since you can reproduce it, can you find out which test it is failing? > At the very least we need to add the test to fsck. > > Scott The main problem with dirbad panics is that the corruption accrued a long time ago, so a backtrace usually doesn't provide enough information to find out what went wrong. Doing a fsck _should_ fix the filesystem corruption, but only after the problem has already accrued. There are a few cases in which fsck needs to restart its current scan level or it can leave corruption inside the filesystem while marking the partition clean. -DR From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 17:44:58 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FB2116A422; Sat, 7 Jan 2006 17:44:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB75B43D70; Sat, 7 Jan 2006 17:44:53 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k07Hip4k000559; Sat, 7 Jan 2006 10:44:51 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BFFE1D.4070502@samsco.org> Date: Sat, 07 Jan 2006 10:45:01 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Rhodus References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> <20060106200009.GA53067@garage.freebsd.pl> <43BFF041.8070300@samsco.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 17:44:58 -0000 David Rhodus wrote: > On 1/7/06, Scott Long wrote: > >>Pawel Jakub Dawidek wrote: >> >> >>>On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: >>>+> David O'Brien wrote: >>>+> >>>+> >Just in case anyone thought the bug had been fixed... >>>+> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 >>>+> >panic: ufs_dirbad: bad dir >>>+> >cpuid = 1 >>>+> >KDB: stack backtrace: >>>+> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e = kdb_backtrace+0x2e >>>+> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 = panic+0x128 >>>+> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d = ufs_dirbad+0x4d >>>+> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc06165cd = ufs_lookup+0x3ad >>>+> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80) at 0xc068cd4e = VOP_CACHEDLOOKUP_APV+0x9e >>>+> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at 0xc057275a = vfs_cache_lookup+0xca >>>+> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc66 = VOP_LOOKUP_APV+0xa6 >>>+> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e = lookup+0x44e >>>+> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf = namei+0x44f >>>+> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd = kern_stat+0x3d >>>+> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f = stat+0x2f >>>+> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 = syscall+0x323 >>>+> >Xint0x80_syscall() at 0xc066d33f = Xint0x80_syscall+0x1f >>>+> >>>+> Please include the console printf that is right about the panic message. >>>+> It will say either something about a mangled entry or an isize too >>>+> small. Since this problem is happening consistently for you, but there >>>+> seem to be no other problem reports from others, I'd highly suspect that >>>+> you have filesystem damage that isn't getting detected by fsck. I assume that you are running fsck in the foreground and not in the background, yes? The easiest solution >>>+> here might be to figure out which >>>+> directory is causing the problem, and just clri its inode and then clean >>>+> up the mess. >>> >>>I'm able to reproduce it with newly newfs(8)ed file system: >>> >>>/mnt: bad dir ino 17382405 at offset 0: mangled entry >>>panic: ufs_dirbad: bad dir >>>KDB: enter: panic >>>[...] >>>db> tr >>>Tracing pid 427 tid 100057 td 0xc7ccaa80 >>>kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 >>>panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce >>>ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e >>>ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup+0x39f >>>VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at VOP_CACHEDLOOKUP_APV+0xc4 >>>vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0xc8 >>>VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 >>>lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 >>>namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 >>>kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b >>>lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f >>>syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 >>>Xint0x80_syscall() at Xint0x80_syscall+0x1f >>>--- syscall (190, FreeBSD ELF32, lstat), eip = 0x28176efb, esp = 0xbfbfe90c, ebp = 0xbfbfea48 --- >>> >> >>Since you can reproduce it, can you find out which test it is failing? >>At the very least we need to add the test to fsck. >> >>Scott > > > The main problem with dirbad panics is that the corruption accrued a > long time ago, so a backtrace usually doesn't provide enough > information to find out what went wrong. > > Doing a fsck _should_ fix the filesystem corruption, but only after > the problem has already accrued. There are a few cases in which fsck > needs to restart its current scan level or it can leave corruption > inside the filesystem while marking the partition clean. > > -DR Yes, I'm well aware of all of this, that's why I'm asking Pawel to determine which test is failing so we can find out why fsck isn't catching it. Scott From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 18:10:23 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F02216A41F for ; Sat, 7 Jan 2006 18:10:23 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 98BD643D55 for ; Sat, 7 Jan 2006 18:10:21 +0000 (GMT) (envelope-from sdrhodus@gmail.com) Received: by wproxy.gmail.com with SMTP id i32so3023457wra for ; Sat, 07 Jan 2006 10:10:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=aS1OV1LKuAokB3X0aE+2omryHUoaIfw/9miq+ypRs/6zwcIyIvRx5QS1Go20Lk63NBqi2p1+PotlxB6aZu/O4vz+ggynIc7f8C+PMCRvVuSh7iRk5Le/IhcQlrnHtisJ8qiXkcFSRnq6z7q/PlWGTmnHjpHiOP+wr+4jvOHwjzw= Received: by 10.64.150.20 with SMTP id x20mr2070487qbd; Sat, 07 Jan 2006 10:10:20 -0800 (PST) Received: by 10.64.178.4 with HTTP; Sat, 7 Jan 2006 10:10:20 -0800 (PST) Message-ID: Date: Sat, 7 Jan 2006 13:10:20 -0500 From: David Rhodus Sender: sdrhodus@gmail.com To: Scott Long In-Reply-To: <43BFFE1D.4070502@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060102222723.GA1754@dragon.NUXI.org> <43BA9C5C.9010307@samsco.org> <20060106200009.GA53067@garage.freebsd.pl> <43BFF041.8070300@samsco.org> <43BFFE1D.4070502@samsco.org> Cc: freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: It still here... panic: ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 18:10:23 -0000 On 1/7/06, Scott Long wrote: > David Rhodus wrote: > > On 1/7/06, Scott Long wrote: > > > >>Pawel Jakub Dawidek wrote: > >> > >> > >>>On Tue, Jan 03, 2006 at 08:46:36AM -0700, Scott Long wrote: > >>>+> David O'Brien wrote: > >>>+> > >>>+> >Just in case anyone thought the bug had been fixed... > >>>+> >FreeBSD 7.0-CURRENT #531: Mon Jan 2 11:32:17 PST 2006 i386 > >>>+> >panic: ufs_dirbad: bad dir > >>>+> >cpuid =3D 1 > >>>+> >KDB: stack backtrace: > >>>+> >kdb_backtrace(c06c9ba1,1,c06c03c6,eae718c8,c8a91480) at 0xc053657e= =3D kdb_backtrace+0x2e > >>>+> >panic(c06c03c6,c85bf1f8,dade11,580,c06c0380) at 0xc0516618 =3D pan= ic+0x128 > >>>+> >ufs_dirbad(c9171bdc,580,c06c0380,0,eae7193c) at 0xc0616e4d =3D ufs= _dirbad+0x4d > >>>+> >ufs_lookup(eae719e8,c916c528,eae71bc4,c916c528,eae71a24) at 0xc061= 65cd =3D ufs_lookup+0x3ad > >>>+> >VOP_CACHEDLOOKUP_APV(c06f2a80,eae719e8,eae71bc4,c8a91480,cac28d80)= at 0xc068cd4e =3D VOP_CACHEDLOOKUP_APV+0x9e > >>>+> >vfs_cache_lookup(eae71a90,eae71a90,c916c528,c916c528,eae71bc4) at = 0xc057275a =3D vfs_cache_lookup+0xca > >>>+> >VOP_LOOKUP_APV(c06f2a80,eae71a90,c8a91480,c106fc88,0) at 0xc068cc6= 6 =3D VOP_LOOKUP_APV+0xa6 > >>>+> >lookup(eae71b9c,0,c06b5c8e,b6,c057f7ed) at 0xc057760e =3D lookup+0= x44e > >>>+> >namei(eae71b9c,eae71b3c,60,0,c8a91480) at 0xc0576ecf =3D namei+0x4= 4f > >>>+> >kern_stat(c8a91480,8106f20,0,eae71c10,e0) at 0xc05863dd =3D kern_s= tat+0x3d > >>>+> >stat(c8a91480,eae71d04,8,43c,c8a91480) at 0xc058636f =3D stat+0x2f > >>>+> >syscall(3b,3b,3b,80dbe80,8106f20) at 0xc0682b43 =3D syscall+0x323 > >>>+> >Xint0x80_syscall() at 0xc066d33f =3D Xint0x80_syscall+0x1f > >>>+> > >>>+> Please include the console printf that is right about the panic mes= sage. > >>>+> It will say either something about a mangled entry or an isize too > >>>+> small. Since this problem is happening consistently for you, but t= here > >>>+> seem to be no other problem reports from others, I'd highly suspect= that > >>>+> you have filesystem damage that isn't getting detected by fsck. I = assume that you are running fsck in the foreground and not in the backgroun= d, yes? The easiest solution > >>>+> here might be to figure out which > >>>+> directory is causing the problem, and just clri its inode and then = clean > >>>+> up the mess. > >>> > >>>I'm able to reproduce it with newly newfs(8)ed file system: > >>> > >>>/mnt: bad dir ino 17382405 at offset 0: mangled entry > >>>panic: ufs_dirbad: bad dir > >>>KDB: enter: panic > >>>[...] > >>>db> tr > >>>Tracing pid 427 tid 100057 td 0xc7ccaa80 > >>>kdb_enter(c060029a,c065c020,c0610849,f6b228c0,100) at kdb_enter+0x30 > >>>panic(c0610849,c7914210,1093c05,0,c0610803) at panic+0xce > >>>ufs_dirbad(cb2b4b58,0,c0610803,0,f6b22934) at ufs_dirbad+0x4e > >>>ufs_lookup(f6b229e4,c061b519,cb092c60,cb092c60,f6b22b64) at ufs_lookup= +0x39f > >>>VOP_CACHEDLOOKUP_APV(c063a7e0,f6b229e4,f6b22b64,c7ccaa80,c7d52b80) at = VOP_CACHEDLOOKUP_APV+0xc4 > >>>vfs_cache_lookup(f6b22a8c,f6b22a8c,0,cb092c60,0) at vfs_cache_lookup+0= xc8 > >>>VOP_LOOKUP_APV(c063a7e0,f6b22a8c,c7ccaa80,38,0) at VOP_LOOKUP_APV+0xa6 > >>>lookup(f6b22b3c,0,c060880c,b5,c0511d45) at lookup+0x454 > >>>namei(f6b22b3c,f6b22b8c,60,0,c7ccaa80) at namei+0x441 > >>>kern_lstat(c7ccaa80,8059800,0,f6b22c10,2) at kern_lstat+0x5b > >>>lstat(c7ccaa80,f6b22d04,8,43c,c065c740) at lstat+0x2f > >>>syscall(805003b,807003b,bfbf003b,805f19c,bfbfeba0) at syscall+0x325 > >>>Xint0x80_syscall() at Xint0x80_syscall+0x1f > >>>--- syscall (190, FreeBSD ELF32, lstat), eip =3D 0x28176efb, esp =3D 0= xbfbfe90c, ebp =3D 0xbfbfea48 --- > >>> > >> > >>Since you can reproduce it, can you find out which test it is failing? > >>At the very least we need to add the test to fsck. > >> > >>Scott > > > > > > The main problem with dirbad panics is that the corruption accrued a > > long time ago, so a backtrace usually doesn't provide enough > > information to find out what went wrong. > > > > Doing a fsck _should_ fix the filesystem corruption, but only after > > the problem has already accrued. There are a few cases in which fsck > > needs to restart its current scan level or it can leave corruption > > inside the filesystem while marking the partition clean. > > > > -DR > > Yes, I'm well aware of all of this, that's why I'm asking Pawel to > determine which test is failing so we can find out why fsck isn't > catching it. > > Scott I think the problem in Pawels case is that the filesystem itself is writing out corrupt data then later he's hitting a assertion when the filesystem is trying to read the corrupt entry. This seems to be a problem with UFS itself. As for fsck, it should fix this problem, but only after its already happened and it may take two fsck scans. I'm not sure what the current state of fsck is in fbsd, but one problem I've noticed in the past while working on fbsd is that if fsck has to create a lost+found directory it doesn't restart the current scan level. This can lead to the dirbad panic. -DR From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 18:57:17 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48D2516A41F; Sat, 7 Jan 2006 18:57:17 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 34F9843D45; Sat, 7 Jan 2006 18:57:15 +0000 (GMT) (envelope-from max@love2party.net) Received: from [84.163.206.120] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1EvJFZ3h6s-0000ls; Sat, 07 Jan 2006 19:57:14 +0100 From: Max Laier Organization: FreeBSD To: freebsd-current@freebsd.org Date: Sat, 7 Jan 2006 19:57:48 +0100 User-Agent: KMail/1.8.3 References: <200601070605.05535.max@love2party.net> In-Reply-To: <200601070605.05535.max@love2party.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1376887.ZC23clUomX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200601071957.55542.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Damien Bergamini , Alexander Nedotsukov Subject: Re: Intel 2915abg and 11a X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 18:57:17 -0000 --nextPart1376887.ZC23clUomX Content-Type: multipart/mixed; boundary="Boundary-01=_u8AwDzxaeWM2LKO" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_u8AwDzxaeWM2LKO Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 07 January 2006 06:04, Max Laier wrote: > Hi, > > is anyone successfully running their Intel 2915abg card in 11a mode with > the iwi(4) driver? I am wondering, because since 11a has been enabled in > the driver I can't use it anymore. "fatal error" while scanning through > the 11a channels. No matter what firmware I use. > > Please let me know - if there are no positive reports I'd like to disable > 11a for the moment to have the driver working in 11b/g mode at least - > which it does. Andrew Atrens, who did the DragonFly port, was nice enough to let me know t= hat=20 he had worked around the issue. By looking at the diffs I came up with thi= s=20 patch, which fixes things for me. There is more to be done wrt locking, bu= t=20 that's another story - for now only fixing the obvious problems. BTW, I am working on the firmware loading proposed by Sam in -arch a while= =20 back. My latest version is here: http://people.freebsd.org/~mlaier/firmware.tgz including these changes to iwi as well as the modified firmware loading. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --Boundary-01=_u8AwDzxaeWM2LKO Content-Type: text/x-diff; charset="iso-8859-6"; name="if_iwi.11a.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="if_iwi.11a.diff" Index: if_iwi.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: /usr/store/mlaier/fcvs/src/sys/dev/iwi/if_iwi.c,v retrieving revision 1.26 diff -u -r1.26 if_iwi.c =2D-- if_iwi.c 20 Nov 2005 16:02:04 -0000 1.26 +++ if_iwi.c 7 Jan 2006 18:46:16 -0000 @@ -150,6 +150,7 @@ static int iwi_scan(struct iwi_softc *); static int iwi_auth_and_assoc(struct iwi_softc *); static void iwi_init(void *); +static void iwi_init_locked(void *); static void iwi_stop(void *); static int iwi_read_firmware(const char *, caddr_t *, size_t *); static int iwi_sysctl_stats(SYSCTL_HANDLER_ARGS); @@ -881,7 +882,7 @@ } =20 if ((ifp->if_flags & IFF_UP) && (ifp->if_drv_flags & IFF_DRV_RUNNING)) =2D iwi_init(sc); + iwi_init_locked(sc); =20 IWI_UNLOCK(sc); =20 @@ -1773,7 +1774,7 @@ case SIOCSIFFLAGS: if (ifp->if_flags & IFF_UP) { if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) =2D iwi_init(sc); + iwi_init_locked(sc); } else { if (ifp->if_drv_flags & IFF_DRV_RUNNING) iwi_stop(sc); @@ -1788,7 +1789,7 @@ if ((ifp->if_flags & IFF_UP) && (ifp->if_drv_flags & IFF_DRV_RUNNING) && (ic->ic_roaming !=3D IEEE80211_ROAMING_MANUAL)) =2D iwi_init(sc); + iwi_init_locked(sc); error =3D 0; } =20 @@ -2255,10 +2256,12 @@ struct ieee80211com *ic =3D &sc->sc_ic; struct iwi_scan scan; uint8_t *p; =2D int i, count; + int i, count, do_5ghz_scan =3D 0; =20 =2D memset(&scan, 0, sizeof scan); + sc->scan_counter++; + sc->flags |=3D IWI_FLAG_SCANNING; =20 + bzero(&scan, sizeof(scan)); if (ic->ic_des_esslen !=3D 0) { scan.bdirected =3D htole16(sc->dwelltime); memset(scan.type, IWI_SCAN_TYPE_BDIRECTED, sizeof scan.type); @@ -2268,25 +2271,40 @@ } =20 p =3D scan.channels; =2D count =3D 0; =2D for (i =3D 0; i <=3D IEEE80211_CHAN_MAX; i++) { =2D if (IEEE80211_IS_CHAN_5GHZ(&ic->ic_channels[i]) && =2D isset(ic->ic_chan_active, i)) { =2D *++p =3D i; =2D count++; =2D } + /* + * If we have .11a capable adapter, and + * - we are in .11a mode, or + * - we are in auto mode and this is an odd numbered scan + * then do a 5GHz scan, otherwise do a 2GHz scan. + */ + if ( ic->ic_sup_rates[IEEE80211_MODE_11A].rs_nrates > 0 ) { + if (( ic->ic_curmode =3D=3D IEEE80211_MODE_11A ) || + (( ic->ic_curmode =3D=3D IEEE80211_MODE_AUTO ) && + ( sc->scan_counter & 1))) + do_5ghz_scan =3D 1; } =2D *(p - count) =3D IWI_CHAN_5GHZ | count; =2D count =3D 0; =2D for (i =3D 0; i <=3D IEEE80211_CHAN_MAX; i++) { =2D if (IEEE80211_IS_CHAN_2GHZ(&ic->ic_channels[i]) && =2D isset(ic->ic_chan_active, i)) { =2D *++p =3D i; =2D count++; + if ( do_5ghz_scan ) { + DPRINTF(("Scanning 5GHz band\n")); + for (i =3D 0; i <=3D IEEE80211_CHAN_MAX; i++) { + if (IEEE80211_IS_CHAN_5GHZ(&ic->ic_channels[i]) && + isset(ic->ic_chan_active, i)) { + *++p =3D i; + count++; + } + } + *(p - count) =3D IWI_CHAN_5GHZ | count; + } else { + DPRINTF(("Scanning 2GHz band\n")); + for (i =3D 0; i <=3D IEEE80211_CHAN_MAX; i++) { + if (IEEE80211_IS_CHAN_2GHZ(&ic->ic_channels[i]) && + isset(ic->ic_chan_active, i)) { + *++p =3D i; + count++; + } } + *(p - count) =3D IWI_CHAN_2GHZ | count; } =2D *(p - count) =3D IWI_CHAN_2GHZ | count; =20 DPRINTF(("Start scanning\n")); return iwi_cmd(sc, IWI_CMD_SCAN, &scan, sizeof scan, 1); @@ -2418,6 +2436,16 @@ iwi_init(void *priv) { struct iwi_softc *sc =3D priv; + + IWI_LOCK(sc); + iwi_init_locked(sc); + IWI_UNLOCK(sc); +} + +static void +iwi_init_locked(void *priv) +{ + struct iwi_softc *sc =3D priv; struct ieee80211com *ic =3D &sc->sc_ic; struct ifnet *ifp =3D ic->ic_ifp; struct iwi_rx_data *data; Index: if_iwivar.h =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: /usr/store/mlaier/fcvs/src/sys/dev/iwi/if_iwivar.h,v retrieving revision 1.8 diff -u -r1.8 if_iwivar.h =2D-- if_iwivar.h 19 Nov 2005 16:54:55 -0000 1.8 +++ if_iwivar.h 7 Jan 2006 18:46:16 -0000 @@ -118,6 +118,7 @@ struct mtx sc_mtx; struct unrhdr *sc_unr; =20 + uint32_t scan_counter; uint32_t flags; #define IWI_FLAG_FW_INITED (1 << 0) #define IWI_FLAG_SCANNING (1 << 1) --Boundary-01=_u8AwDzxaeWM2LKO-- --nextPart1376887.ZC23clUomX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDwA8zXyyEoT62BG0RAlP2AJ9K8a7Ew4bsZLuf2sOK7JEs7WAl+QCePOoH JKnQwQHZAW0HdMkszC4Jjuo= =p7HK -----END PGP SIGNATURE----- --nextPart1376887.ZC23clUomX-- From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 19:40:19 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2CF516A420; Sat, 7 Jan 2006 19:40:19 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67F0643D46; Sat, 7 Jan 2006 19:40:19 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id k07JeIWr095161; Sat, 7 Jan 2006 11:40:18 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id k07JeHt3095158; Sat, 7 Jan 2006 11:40:17 -0800 (PST) Date: Sat, 7 Jan 2006 11:40:17 -0800 (PST) From: Matthew Dillon Message-Id: <200601071940.k07JeHt3095158@apollo.backplane.com> To: Andre Oppermann References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> <43BFEB2E.4040303@freebsd.org> Cc: Luigi Rizzo , Poul-Henning Kamp , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 19:40:20 -0000 :Matt, : :I've been testing network and routing performance over the past two weeks :with an calibrated Agilent N2X packet generator. My test box is a dual :Opteron 852 (2.6Ghz) with Tyan S8228 mobo and Intel dual-GigE in PCI-X-133 :slot. Note that I've run all tests with UP kernels em0->em1. : :For stock FreeBSD-7-CURRENT from 28. Dec. 2005 I've got 580kpps with fast- :forward enabled. A em(4) patch from Scott Long implementing a taskqueue :raised this to 729kpps. : :For stock DragonFlyBSD-1.4-RC1 I've got 327kpps and then it breaks down and :never ever passes a packet again until a down/up on the receiving interface. :net.inet.ip.intr_queue_maxlen has to be set to 200, otherwise it breaks down :at 252kpps already. Enabling polling did not make a difference and I've tried :various settings and combinations without any apparent effect on performance :(burst=1000, each_burst=50, user_frac=1, pollhz=5000). : :What suprised me most, apart from the generally poor performance, is the sharp :dropoff after max pps and the wedging of the interface. I didn't see this kind :of behaviour on any other OS I've tested (FreeBSD and OpenBSD). : :-- :Andre Well, considering that we haven't removed the MP lock from the network code yet, I'm not surprised at the poorer performance. The priority has been on getting the algorithms in, correct, and stable, proving their potential, but not hacking things up to eek out maximum performance before its time. At the moment there is a great deal of work slated for 1.5 to properly address many of the issues. Remember that the difference between 327kps and 792kps is the difference between 3 uS and 1.2 uS per packet of overhead. That isn't all that huge a difference, really, especially considering that everything is serialized down to effectively 1 cpu due to the MP lock. :For stock FreeBSD-7-CURRENT from 28. Dec. 2005 I've got 580kpps with fast- :forward enabled. A em(4) patch from Scott Long implementing a taskqueue :raised this to 729kpps. The single biggest overhead we have right now is that we have not yet embedded a LWKT message structure in the mbuf. That means we are currently malloc() and free()ing a message structure for every packet, costing at least 700 nS in additional overhead and possibly more if a cross-cpu free is needed (even with the passive IPIQ the free() code does in that case). This problem is going to be fixed once 1.4 is released, but in order to do it properly I intend to completely separate the mbuf data vs header concept... give them totally different structural names instead of overloading them with a union, then embedding the LWKT message structure in the mbuf_pkt. Another example would be our IP forwarding code. Hahahah. I'm amazed that it only takes 3 uS considering that it is running under both the MP lock *AND* the new mutex-like serializer locks that will be replacing the MP lock in the network subsystem AND hacking up those locks (so there are four serializer locking operations per packet plus the MP lock). The interrupt routing code has similar issues. The code is designed to be per-cpu and tested in that context (by testing driver entry from other cpus), but all hardware interrupts are still being taken on cpu #0, and all polling is issued on cpu #0. This adds considerable overhead, though it is mitigated somewhat by packet aggregation. There are two or three other non-algorithmic issues of that nature in the current network path that exist to allow the old algorithms to be migrated to the new ones and which are slowly being cleaned up. I'm not at all surprised that all of these shims cost us 1.8 uS in overhead. I've run end-to-end timing tests for a number of operations, which you can see from my BayLisa slides here: http://www.dragonflybsd.org/docs/LISA200512/ What I have found is that the algorithms are sound and the extra overheads are basically just due to the migrationary hacks (like the malloc). Those tests also tested that our algorithms are capable of pipelining (MP safe wise) between the network interrupt and TCP or UDP protocol stacks, and they can with only about 40 ns of IPI messaging overhead. There are sysctls for testing the MP safe interrupt path, but they aren't production ready yet (because they aren't totally MP safe due to the route table, IP filter, and mbuf stats which are the only remaining items that need to be made MP safe). Frankly, I'm not really all that concerned about any of this. Certainly not raw routing overhead (someone explain to me why you don't simply buy a cisco, or write a custom driver if you really need to pop packets between interfaces at 1 megapps instead of trying to use a piece of generic code in a generic operating system to do it). Our focus is frankly never going to be on raw packet switching because there is no real-life situation where you would actually need to switch such a high packet rate where you wouldn't also have the budget to simply buy an off-the-shelf solution. Our focus vis-a-vie the network stack is going to be on terminus communications, meaning UDP and TCP services terminated or sourced on the machine. All the algorithms have been proved out, the only thing preventing me from flipping the MP lock off are the aformentioned mbuf stats, route table, and packet filter code. In fact, Jeff *has* turned off the MP lock for the TCP protocol threads for testing purposes, with very good results. The route table is going to be fixed this month when we get Jeff's MPSAFE parallel route table code into the tree. The mbuf stats are a non-problem, really, just some minor work. The packet filter(s) are more of an issue. The numbers I ran for the BayLisa talk show our network interrupt overhead is around 1-1.5 uS per packet, and our TCP overhead is around 1-1.5 uS per packet. 700 ns of that is the aformentioned malloc/free issue, and a good chunk of the remaining overhead is MP lock related. :For stock FreeBSD-7-CURRENT from 28. Dec. 2005 I've got 580kpps with fast- :forward enabled. A em(4) patch from Scott Long implementing a taskqueue :raised this to 729kpps. An interface lockup is a different matter. Nothing can be said about that until the cause of the problem is tracked down. I can't speculate as to the problem without more information. -Matt Matthew Dillon From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 20:24:04 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4248F16A41F; Sat, 7 Jan 2006 20:24:04 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3AE343D45; Sat, 7 Jan 2006 20:23:59 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k07KNqaq001321; Sat, 7 Jan 2006 13:23:52 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43C02362.2070009@samsco.org> Date: Sat, 07 Jan 2006 13:24:02 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Dillon References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> <43BFEB2E.4040303@freebsd.org> <200601071940.k07JeHt3095158@apollo.backplane.com> In-Reply-To: <200601071940.k07JeHt3095158@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: Andre Oppermann , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 20:24:04 -0000 Matthew Dillon wrote: [...] I'm about to release a patch to Andre that should allow if_em to fast forward 1mpps or more on his hardware, using no shortcuts or hacks other than the inherent shortcut that the ffwd code provides. The approach I'm taking also works on the other high performance network interfaces. There is also a lot of work going on to streamline the ifnet layer that will likely result in several hundred nanoseconds of latency being removed from there. I'd personally love to see DragonFly approach this level of performance. Given that it took FreeBSD about 3-4 years to slog through setting up and validating a new architecture before we could start focusing on performance, I think that DFly is right on track on the same schedule. Hopefully the results are as worthwhile on DFly in the future as they are on FreeBSD right now. Scott From owner-freebsd-current@FreeBSD.ORG Fri Jan 6 02:53:10 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B68516A41F for ; Fri, 6 Jan 2006 02:53:10 +0000 (GMT) (envelope-from don@sandvine.com) Received: from mailserver.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA10143D45 for ; Fri, 6 Jan 2006 02:53:07 +0000 (GMT) (envelope-from don@sandvine.com) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Jan 2006 21:51:57 -0500 Message-ID: <2BCEB9A37A4D354AA276774EE13FB8C2B109E3@mailserver.sandvine.com> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 X-MS-TNEF-Correlator: Thread-Topic: Trendnet TEW-424UB usb wireless card & ndis driver Thread-Index: AcYSbF0wUiB9hcgwSiK1DQB6bVLsEA== From: "Don Bowman" To: X-Mailman-Approved-At: Sat, 07 Jan 2006 20:30:00 +0000 Subject: Trendnet TEW-424UB usb wireless card & ndis driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jan 2006 02:53:10 -0000 I'm on 6.0 release I ran ndisgen SiS163u.INF SiS163u.sys and then loaded the resulting driver. However, i get missing symbols when i load it: no match for InterlockedCompareExchange no match for KeSetPriorityThread no match for KeGetCurrentThread no match for USBD_ParseConfigurationDescriptorEx no match for USBD_CreateConfigurationRequestEx It appears that at least the first one i could add to the compat/ndis code, but i'm not really sure on the others. Has anyone used the TEW-424UB in some other way? Or has anyone run into these missing symbols when using ndis and come up with a solution? --don From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 12:42:48 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF2E816A41F for ; Sat, 7 Jan 2006 12:42:48 +0000 (GMT) (envelope-from ggajic@afrodita.rcub.bg.ac.yu) Received: from afrodita.rcub.bg.ac.yu (afrodita.rcub.bg.ac.yu [147.91.1.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32EBE43D45 for ; Sat, 7 Jan 2006 12:42:39 +0000 (GMT) (envelope-from ggajic@afrodita.rcub.bg.ac.yu) Received: from afrodita.rcub.bg.ac.yu (localhost.localdomain [127.0.0.1]) by afrodita.rcub.bg.ac.yu (8.13.4/8.13.4) with ESMTP id k07CgUmB024932 for ; Sat, 7 Jan 2006 13:42:30 +0100 Received: from localhost (ggajic@localhost) by afrodita.rcub.bg.ac.yu (8.13.4/8.13.4/Submit) with ESMTP id k07CgT89024929 for ; Sat, 7 Jan 2006 13:42:30 +0100 Date: Sat, 7 Jan 2006 13:42:29 +0100 (CET) From: Goran Gajic To: freebsd-current@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-RCUB-MailScanner-Information: Please contact the RCUB if you have problem with mail X-RCUB-MailScanner: Found to be clean X-RCUB-MailScanner-From: ggajic@afrodita.rcub.bg.ac.yu X-Mailman-Approved-At: Sat, 07 Jan 2006 20:30:56 +0000 Subject: 7.0-CURRENT ppp related panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 12:42:48 -0000 Hi, I have managed to trigger two panics by doing ifconfig ppp0 destroy while ppp was running. Reagrads, gg. # kgdb /usr/src/sys/amd64/compile/TEST/kernel.debug vmcore.0 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde fined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 "amd64-marcel-freebsd". Unread portion of the kernel message buffer: Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff804757d0 stack pointer = 0x10:0xffffffffa569c940 frame pointer = 0x10:0xffffffffa569ca60 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 31 (swi0: sio) panic: from debugger cpuid = 0 Uptime: 36m28s Dumping 1023 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 83 1 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 51 1 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 19 1 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h #0 doadump () at pcpu.h:172 #1 0xffffffff803faa0c in boot (howto=260) at ../../../kern/kern_shutdown.c:399 #2 0xffffffff803fa4ab in panic (fmt=0xffffffff8062d726 "from debugger") at ../../../kern/kern_shutdown.c:555 #3 0xffffffff801c7402 in db_panic (addr=0, have_addr=0, count=0, modif=0x0) at ../../../ddb/db_command.c:435 #4 0xffffffff801c7945 in db_command_loop () at ../../../ddb/db_command.c:404 #5 0xffffffff801c9853 in db_trap (type=-1519794512, code=0) at ../../../ddb/db_main.c:221 #6 0xffffffff8041a549 in kdb_trap (type=9, code=0, tf=0xffffffffa569c890) at ../../../kern/subr_kdb.c:485 #7 0xffffffff805c2e35 in trap_fatal (frame=0xffffffffa569c890, eva=18446742975232440144) at ../../../amd64/amd64/trap.c:679 #8 0xffffffff805c33a1 in trap (frame= {tf_rdi = -2401050962867404546, tf_rsi = 0, tf_rdx = -1519793496, tf_rcx = -2401050962867404546, tf_r8 = 80, tf_r9 = -1519793536, tf_rax = -24010509628674 04546, tf_rbx = -2140624749, tf_rbp = -1519793568, tf_r10 = 0, tf_r11 = 16, tf_r 12 = -2143174672, tf_r13 = 0, tf_r14 = -2140624751, tf_r15 = 0, tf_trapno = 9, t f_addr = 0, tf_flags = 2, tf_err = 0, tf_rip = -2142808112, tf_cs = 8, tf_rflags = 66118, tf_rsp = -1519793832, tf_ss = 16}) at ../../../amd64/amd64/trap.c:492 #9 0xffffffff805af8eb in calltrap () at ../../../amd64/amd64/exception.S:168 #10 0xffffffff804757d0 in strlcpy () at ../../../kern/kern_shutdown.c:555 #3 0xffffffff801c7402 in db_panic (addr=0, have_addr=0, count=0, modif=0x0) at ../../../ddb/db_command.c:435 #4 0xffffffff801c7945 in db_command_loop () at ../../../ddb/db_command.c:404 #5 0xffffffff801c9853 in db_trap (type=-1519794512, code=0) at ../../../ddb/db_main.c:221 #6 0xffffffff8041a549 in kdb_trap (type=9, code=0, tf=0xffffffffa569c890) at ../../../kern/subr_kdb.c:485 #7 0xffffffff805c2e35 in trap_fatal (frame=0xffffffffa569c890, eva=18446742975232440144) at ../../../amd64/amd64/trap.c:679 #8 0xffffffff805c33a1 in trap (frame= {tf_rdi = -2401050962867404546, tf_rsi = 0, tf_rdx = -1519793496, tf_rcx = -2401050962867404546, tf_r8 = 80, tf_r9 = -1519793536, tf_rax = -24010509628674 04546, tf_rbx = -2140624749, tf_rbp = -1519793568, tf_r10 = 0, tf_r11 = 16, tf_r 12 = -2143174672, tf_r13 = 0, tf_r14 = -2140624751, tf_r15 = 0, tf_trapno = 9, t f_addr = 0, tf_flags = 2, tf_err = 0, tf_rip = -2142808112, tf_cs = 8, tf_rflags = 66118, tf_rsp = -1519793832, tf_ss = 16}) at ../../../amd64/amd64/trap.c:492 #9 0xffffffff805af8eb in calltrap () at ../../../amd64/amd64/exception.S:168 #10 0xffffffff804757d0 in strlcpy () #11 0xffffffffa569ca80 in ?? () #12 0x0000000000000000 in ?? () Previous frame identical to this frame (corrupt stack?) [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Unde fined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 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 "amd64-marcel-freebsd". Unread portion of the kernel message buffer: <118>. <118>Terminated <118>. <118>Jan 7 13:20:13 magarac syslogd: exiting on signal 15 Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff8043fc90 stack pointer = 0x10:0xffffffffa7e71890 frame pointer = 0x10:0xffffffffa7e718b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 579 (pppd) Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id = 00 instruction pointer = 0x8:0xffffffff8043fc90 stack pointer = 0x10:0xffffffffa7e71890 frame pointer = 0x10:0xffffffffa7e718b0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 579 (pppd) Dumping 1023 MB (2 chunks) chunk 0: 1MB (156 pages) ... ok chunk 1: 1023MB (261872 pages) 1007 991 975 959 943 927 911 895 879 863 847 83 1 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 51 1 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 19 1 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:172 172 pcpu.h: No such file or directory. in pcpu.h (kgdb) (kgdb) backtrace #0 doadump () at pcpu.h:172 #1 0xffffffff801c74f1 in db_fncall (dummy1=0, dummy2=0, dummy3=0, dummy4=0x0) at ../../../ddb/db_command.c:489 #2 0xffffffff801c7945 in db_command_loop () at ../../../ddb/db_command.c:404 #3 0xffffffff801c9853 in db_trap (type=-1478027776, code=0) at ../../../ddb/db_main.c:221 #4 0xffffffff8041a549 in kdb_trap (type=9, code=0, tf=0xffffffffa7e717e0) at ../../../kern/subr_kdb.c:485 #5 0xffffffff805c2e35 in trap_fatal (frame=0xffffffffa7e717e0, eva=18446742974867610672) at ../../../amd64/amd64/trap.c:679 #6 0xffffffff805c33a1 in trap (frame= {tf_rdi = -2401050962867404578, tf_rsi = -1098841940944, tf_rdx = 0, tf_rc x = 622, tf_r8 = -2140674520, tf_r9 = -1098841940944, tf_rax = -2401050962867404 578, tf_rbx = -1098479361024, tf_rbp = -1478027088, tf_r10 = 0, tf_r11 = 4, tf_r 12 = -1098479361024, tf_r13 = -2138808448, tf_r14 = -1098841956352, tf_r15 = -10 98490738688, tf_trapno = 9, tf_addr = 0, tf_flags = -2143359391, tf_err = 0, tf_ rip = -2143028080, tf_cs = 8, tf_rflags = 66182, tf_rsp = -1478027104, tf_ss = 1 6}) at ../../../amd64/amd64/trap.c:492 #7 0xffffffff805af8eb in calltrap () at ../../../amd64/amd64/exception.S:168 #8 0xffffffff8043fc90 in m_freem (mb=0xdeadc0dedeadc0de) at mbuf.h:447 #9 0xffffffff804873b6 in pppasyncrelinq (sc=0xffffff003d872400) at ../../../net/ppp_tty.c:270 #10 0xffffffff80487457 in pppclose (tp=0xffffff003cd98850, flag=669686832) at ../../../net/ppp_tty.c:252 #11 0xffffffff80438ad5 in ttioctl (tp=0xffffff003cd98800, cmd=2147775515, data=0xffffff003cdc7780, flag=3) at linedisc.h:93 #12 0xffffffff8043ac53 in ttyioctl (dev=0xdeadc0dedeadc0de, cmd=2147775515, data=0xffffff003cdc7780 "", flag=3, td=0xfffffffd) at ../../../kern/tty.c:3224 #13 0xffffffff803cec85 in giant_ioctl (dev=0xffffff003cda5600, cmd=2147775515, data=0xffffff003cdc7780 "", fflag=3, td=0xffffff0027ea9c30) at ../../../kern/kern_conf.c:288 #14 0xffffffff8039d6ff in devfs_ioctl_f (fp=0xffffff0030bfc870, com=2147775515, data=0xffffffff8083f340, cred=0x26e, td=0xffffff0027ea9c30) at ../../../fs/devfs/devfs_vnops.c:407 #15 0xffffffff80429837 in ioctl (td=0xffffff0027ea9c30, uap=0xffffffffa7e71c00) at file.h:259 #16 0xffffffff805c3cf7 in syscall (frame= {tf_rdi = 5, tf_rsi = 2147775515, tf_rdx = 5347264, tf_rcx = 34374038268, tf_r8 = -2140497280, tf_r9 = 140737488349784, tf_rax = 54, tf_rbx = 5, tf_rbp = 0, tf_r10 = 1, tf_r11 = 582, tf_r12 = 1500, tf_r13 = 0, tf_r14 = 34375374336, tf _r15 = 0, tf_trapno = 12, tf_addr = 5347268, tf_flags = 12, tf_err = 2, tf_rip = 34374100300, tf_cs = 43, tf_rflags = 582, tf_rsp = 140737488349784, tf_ss = 35} ) at ../../../amd64/amd64/trap.c:821 #17 0xffffffff805afa88 in Xfast_syscall () at ../../../amd64/amd64/exception.S:270 #18 0x0000000800db254c in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) #dmesg Copyright (c) 1992-2006 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 7.0-CURRENT #9: Sat Jan 7 12:15:00 CET 2006 root@magarac:/usr/src/sys/amd64/compile/TEST WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) 64 Processor 3200+ (2009.79-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 usable memory = 1062264832 (1013 MB) avail memory = 1022590976 (975 MB) ACPI APIC Table: ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff,0xcf0-0xcf3 on acpi0 pci0: on pcib0 agp0: on hostb0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xf6003000-0xf6003fff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xf6004000-0xf6004fff irq 21 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem 0xf6005000-0xf60050ff irq 22 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered pci0: at device 6.0 (no driver attached) atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 8.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xd800-0xd80f,0xdc00-0xdc7f irq 21 at device 10.0 on pci0 ata2: on atapci1 ata3: on atapci1 pcib1: at device 11.0 on pci0 pci1: on pcib1 vgapci0: port 0x9000-0x90ff mem 0xe0000000-0xe7ffffff,0xf3000000-0xf300ffff irq 16 at device 0.0 on pci1 vgapci1: mem 0xe8000000-0xefffffff,0xf3010000-0xf301ffff at device 0.1 on pci1 pcib2: at device 14.0 on pci0 pci2: on pcib2 skc0: port 0xa000-0xa0ff mem 0xf5000000-0xf5003fff irq 19 at device 11.0 on pci2 skc0: bad VPD resource id: expected 82 got 0 skc0: Marvell Yukon Lite Gigabit Ethernet rev. (0x9) sk0: on skc0 sk0: Ethernet address: 00:14:85:22:8f:62 miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xc0000-0xccfff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ugen0: American Power Conversion Back-UPS CS 350 FW:807.q5.I USB FW:q5, rev 1.10/0.06, addr 2 Timecounter "TSC" frequency 2009790478 Hz quality 800 Timecounters tick every 1.000 msec IP Filter: v4.1.10 initialized. Default = pass all, Logging = disabled ad0: 76318MB at ata0-master UDMA100 acd0: CDRW at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s2a WARNING: / was not properly dismounted pcm0: port 0xb800-0xb8ff,0xbc00-0xbc7f mem 0xf6001000-0xf6001fff irq 20 at device 6.0 on pci0 pcm0: From owner-freebsd-current@FreeBSD.ORG Sat Jan 7 20:40:57 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CD49116A41F; Sat, 7 Jan 2006 20:40:57 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5818243D45; Sat, 7 Jan 2006 20:40:57 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id k07KeviA095628; Sat, 7 Jan 2006 12:40:57 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id k07KetMR095625; Sat, 7 Jan 2006 12:40:55 -0800 (PST) Date: Sat, 7 Jan 2006 12:40:55 -0800 (PST) From: Matthew Dillon Message-Id: <200601072040.k07KetMR095625@apollo.backplane.com> To: Scott Long References: <73774.1136109554@critter.freebsd.dk> <20060101035958.A86264@xorpc.icir.org> <43B7E1EC.5090301@mac.com> <200601060636.k066aNYn079015@apollo.backplane.com> <43BFEB2E.4040303@freebsd.org> <200601071940.k07JeHt3095158@apollo.backplane.com> <43C02362.2070009@samsco.org> Cc: Andre Oppermann , current@freebsd.org Subject: Re: FreeBSD handles leapsecond correctly X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 20:40:58 -0000 : :Matthew Dillon wrote: :[...] : :I'm about to release a patch to Andre that should allow if_em to fast :forward 1mpps or more on his hardware, using no shortcuts or hacks other :than the inherent shortcut that the ffwd code provides. The approach :I'm taking also works on the other high performance network interfaces. :There is also a lot of work going on to streamline the ifnet layer that :will likely result in several hundred nanoseconds of latency being :removed from there. I'd personally love to see DragonFly approach this :level of performance. Given that it took FreeBSD about 3-4 years to :slog through setting up and validating a new architecture before we :could start focusing on performance, I think that DFly is right on track :on the same schedule. Hopefully the results are as worthwhile on DFly :in the future as they are on FreeBSD right now. : :Scott I think it's very possible. We have taken pains to retain the fast-forwarding architecture (i.e. direct lookups, no context switches, handle everything in the interrupt) and to greatly reduce mbuf allocation overheads (e.g. by using Jeff's objcache infrastructure, which is an algorithmic port of Sun's objcache infrastructure). There are three areas of interest for us in this architecutre: (1) Route table lookups. This is basically a non-problem because Jeff already has a per-cpu route table replication patch that will allow us to do route table lookups without having to obtain or release any locks or perform any bus locked instructions. (2) Per-interface serializer (mutex). Right now the core packet processing loop must release the originating interface serializer and obtain the target interface serializer to forward a packet, then release the target and re-obtain the originating. Clearly this can be cleaned up by aggregating packets processed by the originating interface and only doing the swap-a-roo once for N packets. The current code is a migratory 'hack' until the whole network subsystem can be moved to the new network interface serializer. Right now only the network interrupt subsystem has been moved to the new serializer, so networking code is holding both the MP lock AND the serializer. (3) The IP filter / firewall code is the last big item we are going to have a problem with. I intend to remove at least one of the packet filters we support and do per-cpu replication for the remainder. It turns out that most of the packet filter can be replicated, even dynamically generated rules and queues and such. But its a lot of work. -Matt Matthew Dillon