From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 27 04:29:02 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD52037B401 for ; Sun, 27 Apr 2003 04:29:02 -0700 (PDT) Received: from ns2.alphaque.com (ns2.alphaque.com [202.75.47.153]) by mx1.FreeBSD.org (Postfix) with SMTP id 5B55043FB1 for ; Sun, 27 Apr 2003 04:29:01 -0700 (PDT) (envelope-from dinesh@alphaque.com) Received: (qmail 52970 invoked by uid 0); 27 Apr 2003 11:28:59 -0000 Received: from lucifer.net-gw.com (HELO prophet.alphaque.com) (202.75.47.153) by lucifer.net-gw.com with SMTP; 27 Apr 2003 11:28:59 -0000 Received: from localhost (localhost [127.0.0.1]) by prophet.alphaque.com (8.12.9/8.12.3) with ESMTP id h3R6CH2q008748; Sun, 27 Apr 2003 14:12:17 +0800 (MYT) (envelope-from dinesh@alphaque.com) Date: Sun, 27 Apr 2003 14:12:17 +0800 (MYT) From: Dinesh Nair To: Wilko Bulte In-Reply-To: <20030424172440.GB14946@freebie.xs4all.nl> Message-ID: <20030427141157.C1267-100000@prophet.alphaque.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org Subject: Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2003 11:29:03 -0000 On Thu, 24 Apr 2003, Wilko Bulte wrote: > On Thu, Apr 24, 2003 at 09:42:38AM -0700, Peter Wemm wrote: > > Wilko Bulte wrote: > > > On Thu, Apr 24, 2003 at 08:50:07AM -0700, Andrew Kinney wrote: > > > > On 24 Apr 2003, at 9:56, Anthony Schneider wrote: > > > > > > > > > this doesn't look very pOwErFuL. :( > > > > > > > > > > > CPU: AMD ClawHammer(tm) (3.14-MHz Hammer-class CPU) > > > > > > > > > > -Anthony. > > > > > > > > > > > > > > > > > > That's the low budget "crawlhammer" version. Someone's reading > > > > the CPUID wrong! ;-) > > > > > > > > > > > > No, somebody not allowed by an NDA to display the actual cpu clock > > > frequency. > > > > And I would have thought it would have been obvious.. :-/ > > I would have thought so too... :-/ > Maybe have it display: 3.1415926535897 MHz? just 22/7 Mhz would have sufficed. :) Regards, /\_/\ "All dogs go to heaven." dinesh@alphaque.com (0 0) http://www.alphaque.com/ +==========================----oOO--(_)--OOo----==========================+ | for a in past present future; do | | for b in clients employers associates relatives neighbours pets; do | | echo "The opinions here in no way reflect the opinions of my $a $b." | | done; done | +=========================================================================+ From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 27 05:48:17 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B4D1537B401 for ; Sun, 27 Apr 2003 05:48:17 -0700 (PDT) Received: from mail.bellavista.cz (mail.bellavista.cz [213.235.167.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE5FC43F85 for ; Sun, 27 Apr 2003 05:48:15 -0700 (PDT) (envelope-from neuhauser@bellavista.cz) Received: from freepuppy.bellavista.cz (freepuppy.bellavista.cz [10.0.0.10]) by mail.bellavista.cz (Postfix) with ESMTP id 1EF02349 for ; Sun, 27 Apr 2003 14:48:13 +0200 (CEST) Received: by freepuppy.bellavista.cz (Postfix, from userid 1001) id E47732FDAB2; Sun, 27 Apr 2003 14:48:12 +0200 (CEST) Date: Sun, 27 Apr 2003 14:48:12 +0200 From: Roman Neuhauser To: freebsd-hackers Message-ID: <20030427124812.GU13541@freepuppy.bellavista.cz> Mail-Followup-To: freebsd-hackers References: <20030425184400.GS13541@freepuppy.bellavista.cz> <20030426115336.GF761@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030426115336.GF761@straylight.oblivion.bg> User-Agent: Mutt/1.5.1i Subject: Re: make: variable expansion in .for/.endfor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Apr 2003 12:48:18 -0000 # roam@ringlet.net / 2003-04-26 14:53:36 +0300: > On Fri, Apr 25, 2003 at 08:44:00PM +0200, Roman Neuhauser wrote: > > Try the following makefile: it works if called with -DONE, but does not > > if called with -DTWO. Should I treat it as a bug and file a PR? > > > > LIST= foo bar baz > > > > .if defined(ONE) > > . for v in ${LIST} > > . if !defined(WITHOUT_${v:U}) > > WITH_${v:U}=yes > > . endif > > . endfor > > .endif > > > > .if defined(TWO) > > . for v in ${LIST} > > V=${v:U} > > . if !defined(WITHOUT_${V}) > > WITH_${V}=yes > > . endif > > . endfor > > .endif > > > > a: > > @echo \$${WITH_FOO}: ${WITH_FOO} > > @echo \$${WITH_BAR}: ${WITH_BAR} > > @echo \$${WITH_BAZ}: ${WITH_BAZ} > > > > .PHONY: a > > I think this is a known bug, and it seems to even be documented > in the BUGS section of -STABLE's make(1) manual page. I don't think this is covered. Can you point out the relevant text? -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 27 17:49:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5210937B401 for ; Sun, 27 Apr 2003 17:49:46 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id A676E43FAF for ; Sun, 27 Apr 2003 17:49:45 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 497AB5308; Mon, 28 Apr 2003 02:49:43 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Raunchy McSmutbag" From: Dag-Erling Smorgrav Date: Mon, 28 Apr 2003 02:49:43 +0200 In-Reply-To: ("Raunchy McSmutbag"'s message of "Sun, 27 Apr 2003 04:27:00 +0000") Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: int's and bus error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 00:49:46 -0000 "Raunchy McSmutbag" writes: > Hey =) What im trying to do is run vm86 interrupts from a userland > process (int 10h in particular). So ive tried doing.. *choke* what on earth do you want to do that for? DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 27 17:54:32 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8873337B401 for ; Sun, 27 Apr 2003 17:54:32 -0700 (PDT) Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 771C643FA3 for ; Sun, 27 Apr 2003 17:54:31 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (hevuhu@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.8p1/8.12.8) with ESMTP id h3S0sTB5006267 for ; Mon, 28 Apr 2003 02:54:30 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.8p1/8.12.8/Submit) id h3S0sTi2006266; Mon, 28 Apr 2003 02:54:29 +0200 (CEST) Date: Mon, 28 Apr 2003 02:54:29 +0200 (CEST) Message-Id: <200304280054.h3S0sTi2006266@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20030427065621.G40030-100000@haldjas.folklore.ee> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.8-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 00:54:32 -0000 Narvi wrote: > On Sat, 26 Apr 2003, M. Warner Losh wrote: > > In message: <20030427064014.H40030-100000@haldjas.folklore.ee> > > Narvi writes: > > : option USE_PI_DIGITS 100 > > > > Only if you could implement it with integer math :-) > > where's the problem in that ? most mp libs use integer arithmetic, and > x86-64 gives you 64x64->128 bit widening multiplies 8-) You don't need that; the digits of pi can be calculated quite easily with integer math. This snippet is from my signature collection: int f[9800],b,c=9814,g,i;long a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} Of course it doesn't comply with style(9), otherwise it wouldn't fit into two lines. Prettifying (de-obfuscating) it to make it style(9)-compliant is left as an exercise to the reader. ;-) Regards Oliver PS: The number of digits is specified by the iteration counter c which starts at 9814 in this case, producing 2800 digits (35 rows on an 80-columns terminal). The counter should be initialized with (digits / 4 + 1) * 14. Don't forget to make the f[] array sufficiently large. -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 M黱chen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke's Third Law, from Profiles of the Future From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 27 21:05:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE18137B401 for ; Sun, 27 Apr 2003 21:05:27 -0700 (PDT) Received: from hotmail.com (f65.law11.hotmail.com [64.4.17.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D8C743FE3 for ; Sun, 27 Apr 2003 21:05:27 -0700 (PDT) (envelope-from int0x80@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 27 Apr 2003 21:05:27 -0700 Received: from 24.203.121.28 by lw11fd.law11.hotmail.msn.com with HTTP; Mon, 28 Apr 2003 04:05:27 GMT X-Originating-IP: [24.203.121.28] X-Originating-Email: [int0x80@hotmail.com] From: "Raunchy McSmutbag" To: freebsd-hackers@freebsd.org Date: Mon, 28 Apr 2003 04:05:27 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 28 Apr 2003 04:05:27.0235 (UTC) FILETIME=[669DB930:01C30D3B] Subject: Re: int's and bus error X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 04:05:28 -0000 >"Raunchy McSmutbag" writes: > > Hey =) What im trying to do is run vm86 interrupts from a userland > > process (int 10h in particular). So ive tried doing.. > >*choke* what on earth do you want to do that for? > I think it was Linus that said "Hacking - Just for Fun" >DES >-- >Dag-Erling Smorgrav - des@ofug.org _________________________________________________________________ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 06:53:18 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8265037B401 for ; Mon, 28 Apr 2003 06:53:18 -0700 (PDT) Received: from woozle.rinet.ru (woozle.rinet.ru [195.54.192.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70ADE43FB1 for ; Mon, 28 Apr 2003 06:53:17 -0700 (PDT) (envelope-from marck@rinet.ru) Received: from localhost (localhost [127.0.0.1]) by woozle.rinet.ru (8.12.9/8.12.9) with ESMTP id h3SDrFeR078590 for ; Mon, 28 Apr 2003 17:53:16 +0400 (MSD) (envelope-from marck@rinet.ru) Date: Mon, 28 Apr 2003 17:53:15 +0400 (MSD) From: Dmitry Morozovsky To: freebsd-hackers@freebsd.org In-Reply-To: <200304280054.h3S0sTi2006266@lurza.secnetix.de> Message-ID: <20030428175010.K77005@woozle.rinet.ru> References: <200304280054.h3S0sTi2006266@lurza.secnetix.de> X-NCC-RegID: ru.rinet MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 13:53:18 -0000 On Mon, 28 Apr 2003, Oliver Fromme wrote: OF> You don't need that; the digits of pi can be calculated OF> quite easily with integer math. This snippet is from my OF> signature collection: OF> OF> int f[9800],b,c=9814,g,i;long a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( OF> "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} OF> OF> Of course it doesn't comply with style(9), otherwise it OF> wouldn't fit into two lines. Prettifying (de-obfuscating) OF> it to make it style(9)-compliant is left as an exercise to OF> the reader. ;-) OF> OF> Regards OF> Oliver OF> OF> PS: The number of digits is specified by the iteration OF> counter c which starts at 9814 in this case, producing OF> 2800 digits (35 rows on an 80-columns terminal). The OF> counter should be initialized with (digits / 4 + 1) * 14. OF> Don't forget to make the f[] array sufficiently large. In your particular case it does not work, at least under -stable (2.95); moreover, it produces different (both wrong ;) output for -O and -O0 cases. Actually, it's all because f[] isn't large enough ;-) Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru *** ------------------------------------------------------------------------ From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 10:09:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB6DE37B401 for ; Mon, 28 Apr 2003 10:09:15 -0700 (PDT) Received: from lurza.secnetix.de (lurza.secnetix.de [212.66.1.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id A11A743F75 for ; Mon, 28 Apr 2003 10:09:14 -0700 (PDT) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (dazwtc@localhost [127.0.0.1]) by lurza.secnetix.de (8.12.8p1/8.12.8) with ESMTP id h3SH9DB5034149 for ; Mon, 28 Apr 2003 19:09:13 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.12.8p1/8.12.8/Submit) id h3SH9Dau034148; Mon, 28 Apr 2003 19:09:13 +0200 (CEST) Date: Mon, 28 Apr 2003 19:09:13 +0200 (CEST) Message-Id: <200304281709.h3SH9Dau034148@lurza.secnetix.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG In-Reply-To: <20030428175010.K77005@woozle.rinet.ru> X-Newsgroups: list.freebsd-hackers User-Agent: tin/1.5.4-20000523 ("1959") (UNIX) (FreeBSD/4.8-RELEASE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Subject: Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-hackers@FreeBSD.ORG List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 17:09:16 -0000 Dmitry Morozovsky wrote: > In your particular case it does not work, at least under -stable (2.95); > moreover, it produces different (both wrong ;) output for -O and -O0 cases. > > Actually, it's all because f[] isn't large enough ;-) Yeah, sorry, I pasted from two different versions and borked it. It _does_ work, though, if the array is as big as the counter initialization. :-) Regards Oliver -- Oliver Fromme, secnetix GmbH & Co KG, Oettingenstr. 2, 80538 M黱chen Any opinions expressed in this message may be personal to the author and may not necessarily reflect the opinions of secnetix in any way. "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke's Third Law, from Profiles of the Future From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 12:52:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA0FC37B401 for ; Mon, 28 Apr 2003 12:52:41 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 0B62443F3F for ; Mon, 28 Apr 2003 12:52:40 -0700 (PDT) (envelope-from andreas-moeller@gmx.net) Received: (qmail 28950 invoked by uid 65534); 28 Apr 2003 19:52:38 -0000 Received: from pD9E21B13.dip.t-dialin.net (EHLO gmx.net) (217.226.27.19) by mail.gmx.net (mp021-rz3) with SMTP; 28 Apr 2003 21:52:38 +0200 Message-ID: <3EAD8681.3050108@gmx.net> Date: Mon, 28 Apr 2003 21:52:33 +0200 From: =?ISO-8859-15?Q?Andreas_M=F6ller?= User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030420 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: current@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: hackers@FreeBSD.org Subject: -CURRENT system panic X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 19:52:42 -0000 Hello! My system just crashed and captured the following dump. Please let me know if I should provide any further information. # uname -a FreeBSD blah 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Apr 27 19:02:12 CEST 2003 root@blah:/usr/obj/usr/src/sys/GENERIC i386 (The sources are from approximately 5:00 PM CEST of the same day.) # gdb -k /var/crash/kernel.debug.0 /var/crash/vmcore.0 GNU gdb 5.2.1 (FreeBSD) Copyright 2002 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-undermydesk-freebsd"... panic: bremfree: removing a buffer not on a queue panic messages: --- panic: ffs_blkfree: freeing free block syncing disks, buffers remaining... panic: bremfree: removing a buffer not on a queue Uptime: 7h40m19s Dumping 767 MB ata0: resetting devices .. done [CTRL-C to abort] 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256 272 288 304 320 336 352 368 384 400 416 432 448 464 480 496 512 528 544 560 576 592 608 624 640 656 672 688 704 720 736 752 --- Reading symbols from /boot/kernel/snd_pcm.ko...done. Loaded symbols for /boot/kernel/snd_pcm.ko Reading symbols from /boot/kernel/snd_emu10k1.ko...done. Loaded symbols for /boot/kernel/snd_emu10k1.ko Reading symbols from /boot/kernel/acpi.ko...done. Loaded symbols for /boot/kernel/acpi.ko Reading symbols from /boot/kernel/blank_saver.ko...done. Loaded symbols for /boot/kernel/blank_saver.ko Reading symbols from /boot/kernel/linux.ko...done. Loaded symbols for /boot/kernel/linux.ko #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238 238 dumping++; (kgdb) where #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:238 #1 0xc030f735 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:370 #2 0xc030fa6a in panic () at /usr/src/sys/kern/kern_shutdown.c:543 #3 0xc0351b62 in bremfreel (bp=0xd2269c00) at /usr/src/sys/kern/vfs_bio.c:648 #4 0xc0351a45 in bremfree (bp=0x0) at /usr/src/sys/kern/vfs_bio.c:630 #5 0xc0354eb8 in getblk (vp=0xc5c3a000, blkno=42509792, size=16384, slpflag=0, slptimeo=0, flags=0) at /usr/src/sys/kern/vfs_bio.c:2442 #6 0xc0351c32 in breadn (vp=0xc5c3a000, blkno=0, size=0, rablkno=0x0, rabsize=0x0, cnt=0, cred=0x0, bpp=0x0) at /usr/src/sys/kern/vfs_bio.c:701 #7 0xc0351bdc in bread (vp=0x0, blkno=0, size=0, cred=0x0, bpp=0x0) at /usr/src/sys/kern/vfs_bio.c:683 #8 0xc041b143 in ffs_update (vp=0xc60b1920, waitfor=0) at /usr/src/sys/ufs/ffs/ffs_inode.c:102 #9 0xc042f933 in ffs_fsync (ap=0xde73eaf4) at /usr/src/sys/ufs/ffs/ffs_vnops.c:316 #10 0xc042ea1e in ffs_sync (mp=0xc5af1600, waitfor=2, cred=0xc1b5ee80, td=0xc0585140) at vnode_if.h:612 #11 0xc0366be4 in sync (td=0xc0585140, uap=0x0) at /usr/src/sys/kern/vfs_syscalls.c:137 #12 0xc030f2a3 in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:279 #13 0xc030fa6a in panic () at /usr/src/sys/kern/kern_shutdown.c:543 #14 0xc041700a in ffs_blkfree (fs=0xc5aeb800, devvp=0xc5c3a000, bno=10638104, size=16384, inum=2661386) at /usr/src/sys/ufs/ffs/ffs_alloc.c:1768 #15 0xc0424eb3 in handle_workitem_freefrag (freefrag=0xc5c8a880) at /usr/src/sys/ufs/ffs/ffs_softdep.c:1587 #16 0xc0423bf5 in process_worklist_item (matchmnt=0x0, flags=0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:767 #17 0xc04238f0 in softdep_process_worklist (matchmnt=0x0) at /usr/src/sys/ufs/ffs/ffs_softdep.c:622 #18 0xc0363464 in sched_sync () at /usr/src/sys/kern/vfs_subr.c:1757 #19 0xc02fb5f0 in fork_exit (callout=0xc0363180 , arg=0x0, frame=0x0) at /usr/src/sys/kern/kern_fork.c:795 -Andreas From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 13:49:32 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BD8637B407 for ; Mon, 28 Apr 2003 13:49:31 -0700 (PDT) Received: from mail.speakeasy.net (mail14.speakeasy.net [216.254.0.214]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BA0C43FDF for ; Mon, 28 Apr 2003 13:49:30 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6931 invoked from network); 28 Apr 2003 20:49:37 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 28 Apr 2003 20:49:37 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h3SKnOOv016010; Mon, 28 Apr 2003 16:49:25 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3EAAC30C.1010803@nord-com.net> Date: Mon, 28 Apr 2003 16:49:29 -0400 (EDT) From: John Baldwin To: Thomas Wintergerst cc: hackers@freebsd.org cc: Hellmuth Michaelis Subject: RE: Request for a new major character device number X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 20:49:32 -0000 On 26-Apr-2003 Thomas Wintergerst wrote: > Hi all, > > I need an "official" major device number for the CAPI subsystem for > *BSD. The file "/usr/src/sys/conf/majors" states that I should contact > this list to obtain a reserved major device number. The device number > should be useable in 5.0-RELEASE and earlier releases. > > As You may have noticed by watching the the mailing list > "freebsd-isdn@freebsd.org" I wrote a package for CAPI support for > FreeBSD. For those not familiar with this term: CAPI is the "Common ISDN > API", the standard interface to communicate over ISDN with ISDN boards. > > The device number is needed to link the kernel CAPI manager and its > attached device drivers with userspace applications. > > Maybe Hellmuth Michaelis, maintainer of I4B, already sent out this > request. I am in contact with him to integrate the CAPI subsystem into > "current". Well, current has a device filesystem that controls /dev and doesn't require fixed major numbers. Assuming that userland opens devices by name, then you don't need a fixed major number for 5.x. If you backport the driver to 4.x, then in 4.x a major number can be allocated. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 14:32:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00AA837B401; Mon, 28 Apr 2003 14:32:44 -0700 (PDT) Received: from relay.cigital.com (relay.cigital.com [64.80.176.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2234343FB1; Mon, 28 Apr 2003 14:32:43 -0700 (PDT) (envelope-from ykorff@cigital.com) Received: by relay.cigital.com (Postfix, from userid 103) id 48306BBAD; Mon, 28 Apr 2003 17:32:42 -0400 (EDT) Received: from va-mail.cigital.com (va-mail.cigital.com [10.1.20.12]) by relay.cigital.com (Postfix) with ESMTP id A40E5BA46; Mon, 28 Apr 2003 17:32:21 -0400 (EDT) Received: from va-mail.cigital.com ([10.1.20.12]) by va-mail.cigital.com with Microsoft SMTPSVC(5.0.2195.5329); Mon, 28 Apr 2003 17:32:21 -0400 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Importance: normal Priority: normal Date: Mon, 28 Apr 2003 17:32:21 -0400 Message-ID: <9B05A21842F77F41ABFB3153FC93201D04884F@va-mail.cigital.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Load Balancing on Dell 1655MC thread-index: AcMNzaaodNoGNQYwTqayH3i9WurN4w== From: "Yanek Korff" To: , X-OriginalArrivalTime: 28 Apr 2003 21:32:21.0674 (UTC) FILETIME=[A6F078A0:01C30DCD] X-Spam-Status: No, hits=-47.4 required=5.0 tests=AWL,SPAM_PHRASE_05_08 version=2.41 X-Spam-Level: Subject: Load Balancing on Dell 1655MC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 21:32:44 -0000 First of all, let me apologize for the cross-post. Not quite sure which the best forum for this question might be. That said... I've got a few new Dell 1655MC blade servers Broadcom BCM5703X Gigabit Ethernet with dual logical Broadcom BCM5703X Gigabit Ethernet NICs. They ship with some Broacom software (Advanced Control Suite) which on wintel provides failover and load balancing capability. Does anyone know if I can get this failover/load balancing on -STABLE? -Yanek. -------------------------------------------------------------------------= --- This electronic message transmission contains information that may be confidential or privileged. The information contained herein is = intended solely for the recipient and use by any other party is not authorized. = If you are not the intended recipient (or otherwise authorized to receive = this message by the intended recipient), any disclosure, copying, = distribution or use of the contents of the information is prohibited. If you have = received this electronic message transmission in error, please contact the sender = by reply email and delete all copies of this message. Cigital, Inc. = accepts no responsibility for any loss or damage resulting directly or indirectly = from the use of this email or its contents. Thank You. -------------------------------------------------------------------------= --- From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 15:44:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EBFB837B401 for ; Mon, 28 Apr 2003 15:44:49 -0700 (PDT) Received: from heron.mail.pas.earthlink.net (heron.mail.pas.earthlink.net [207.217.120.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 368AB43F93 for ; Mon, 28 Apr 2003 15:44:48 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0208.cvx22-bradley.dialup.earthlink.net ([209.179.198.208] helo=mindspring.com) by heron.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19AHMY-0006A0-00; Mon, 28 Apr 2003 15:44:42 -0700 Message-ID: <3EADAE8A.145453AE@mindspring.com> Date: Mon, 28 Apr 2003 15:43:22 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yanek Korff References: <9B05A21842F77F41ABFB3153FC93201D04884F@va-mail.cigital.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4cd9ec5334604c08000d5df0cfb2061bb667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org Subject: Re: Load Balancing on Dell 1655MC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 22:44:50 -0000 Yanek Korff wrote: > First of all, let me apologize for the cross-post. Not quite sure which > the best forum for this question might be. That said... > > I've got a few new Dell 1655MC blade servers Broadcom BCM5703X Gigabit > Ethernet with dual logical Broadcom BCM5703X Gigabit Ethernet NICs. > They ship with some Broacom software (Advanced Control Suite) which on > wintel provides failover and load balancing capability. Does anyone > know if I can get this failover/load balancing on -STABLE? I've played with this. The ACS replaces the firmware in order to get the load-balancing. You aren't going to be able to do this in FreeBSD. The firmware documentation sucks (this card is a "Tigon III", and the last time they made firmware or documentation available was "Tigon II"). They were supposedly going to support this on Linux, at one point, according to their sales rep.; you could probably make that work with FreeBSD, but AFAIK, they never really did support Linux like they said they would. -- Terry From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 18:51:30 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16F0C37B401 for ; Mon, 28 Apr 2003 18:51:30 -0700 (PDT) Received: from jive.SoftHome.net (jive.SoftHome.net [66.54.152.27]) by mx1.FreeBSD.org (Postfix) with SMTP id 4DDE343F3F for ; Mon, 28 Apr 2003 18:51:28 -0700 (PDT) (envelope-from davoid@softhome.net) Received: (qmail 16318 invoked by uid 417); 29 Apr 2003 01:51:27 -0000 Received: from slide-.softhome.net (HELO softhome.net) (172.16.2.21) by shunt-smtp-out-0 with SMTP; 29 Apr 2003 01:51:27 -0000 Received: from localhost (localhost [127.0.0.1]) (uid 417) by softhome.net with local; Mon, 28 Apr 2003 19:51:27 -0600 From: davoid@softhome.net To: freebsd-hackers@freebsd.org Date: Mon, 28 Apr 2003 19:51:27 -0600 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Sender: davoid@softhome.net X-Originating-IP: [24.202.234.243] Message-ID: Subject: beginning driver development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 01:51:30 -0000 Hello, I am a junior programmer, and I have to write a driver for a USB wireless network card( I've heard it's an Atmel-based card -- Network Everywhere NWU11b ). I know of 3 different drivers for this card that are said to work on Linux, I will therefore inspire myself from them, of course. However this _is_ my first contact with a kernel from a developer's point of view, and I don't know how to start. Can you help me? Thanks! Andrei From owner-freebsd-hackers@FreeBSD.ORG Mon Apr 28 19:57:41 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6DB4B37B401 for ; Mon, 28 Apr 2003 19:57:41 -0700 (PDT) Received: from hotmail.com (f48.law11.hotmail.com [64.4.17.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B67743F85 for ; Mon, 28 Apr 2003 19:57:41 -0700 (PDT) (envelope-from int0x80@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 28 Apr 2003 19:57:40 -0700 Received: from 24.203.121.28 by lw11fd.law11.hotmail.msn.com with HTTP; Tue, 29 Apr 2003 02:57:40 GMT X-Originating-IP: [24.203.121.28] X-Originating-Email: [int0x80@hotmail.com] From: "Raunchy McSmutbag" To: davoid@softhome.net Date: Tue, 29 Apr 2003 02:57:40 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 29 Apr 2003 02:57:40.0877 (UTC) FILETIME=[194A7BD0:01C30DFB] cc: freebsd-hackers@freebsd.org Subject: Re: beginning driver development X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 02:57:41 -0000 >Hello, > >I am a junior programmer, and I have to write a driver for a USB wireless >network card( I've heard it's an Atmel-based card -- Network Everywhere >NWU11b ). I know of 3 different drivers for this card that are said to work >on Linux, I will therefore inspire myself from them, of course. However >this _is_ my first contact with a kernel from a developer's point of view, >and I don't know how to start. Can you help me? > >Thanks! >Andrei >_______________________________________________ http://www.daemonnews.org/200010/blueprints.html http://packetstormsecurity.nl/papers/unix/bsdkern.htm http://www.r4k.net/mod/fbsdfun.html have fun =) _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 00:51:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44E5637B408; Tue, 29 Apr 2003 00:51:10 -0700 (PDT) Received: from hotmail.com (f34.law14.hotmail.com [64.4.21.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD6EB43F85; Tue, 29 Apr 2003 00:51:09 -0700 (PDT) (envelope-from aaa000111@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 29 Apr 2003 00:51:09 -0700 Received: from 69.3.176.26 by lw14fd.law14.hotmail.msn.com with HTTP; Tue, 29 Apr 2003 07:51:05 GMT X-Originating-IP: [69.3.176.26] X-Originating-Email: [aaa000111@hotmail.com] From: "Eric Murphy" To: ykorff@cigital.com, freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org Date: Tue, 29 Apr 2003 15:51:05 +0800 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed Message-ID: X-OriginalArrivalTime: 29 Apr 2003 07:51:09.0860 (UTC) FILETIME=[19100E40:01C30E24] Subject: Re: Load Balancing on Dell 1655MC X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 07:51:11 -0000 Check out http://www.xgforce.com/product.html for load balancing and clustering solutions. It's hell a lot cheaper and better than Dell's. >From: "Yanek Korff" >To: , >Subject: Load Balancing on Dell 1655MC >Date: Mon, 28 Apr 2003 17:32:21 -0400 > > >First of all, let me apologize for the cross-post. Not quite sure which >the best forum for this question might be. That said... > >I've got a few new Dell 1655MC blade servers Broadcom BCM5703X Gigabit >Ethernet with dual logical Broadcom BCM5703X Gigabit Ethernet NICs. >They ship with some Broacom software (Advanced Control Suite) which on >wintel provides failover and load balancing capability. Does anyone >know if I can get this failover/load balancing on -STABLE? > >-Yanek. > > >---------------------------------------------------------------------------- >This electronic message transmission contains information that may be >confidential or privileged. The information contained herein is intended >solely for the recipient and use by any other party is not authorized. If >you are not the intended recipient (or otherwise authorized to receive this >message by the intended recipient), any disclosure, copying, distribution or >use of the contents of the information is prohibited. If you have received >this electronic message transmission in error, please contact the sender by >reply email and delete all copies of this message. Cigital, Inc. accepts no >responsibility for any loss or damage resulting directly or indirectly from >the use of this email or its contents. >Thank You. >---------------------------------------------------------------------------- >_______________________________________________ >freebsd-hackers@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" _________________________________________________________________ 免费下载 MSN Explorer: http://explorer.msn.com/lccn/ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 03:36:26 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B273C37B414 for ; Tue, 29 Apr 2003 03:36:26 -0700 (PDT) Received: from gandalf.online.bg (gandalf.online.bg [217.75.128.9]) by mx1.FreeBSD.org (Postfix) with SMTP id C4E9243FB1 for ; Tue, 29 Apr 2003 03:36:24 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 29720 invoked from network); 29 Apr 2003 10:30:40 -0000 Received: from office.sbnd.net (HELO straylight.ringlet.net) (217.75.140.130) by gandalf.online.bg with SMTP; 29 Apr 2003 10:30:40 -0000 Received: (qmail 10292 invoked by uid 1000); 29 Apr 2003 10:34:04 -0000 Date: Tue, 29 Apr 2003 13:34:04 +0300 From: Peter Pentchev To: freebsd-hackers Message-ID: <20030429103404.GA680@straylight.oblivion.bg> Mail-Followup-To: freebsd-hackers References: <20030425184400.GS13541@freepuppy.bellavista.cz> <20030426115336.GF761@straylight.oblivion.bg> <20030427124812.GU13541@freepuppy.bellavista.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20030427124812.GU13541@freepuppy.bellavista.cz> User-Agent: Mutt/1.5.4i Subject: Re: make: variable expansion in .for/.endfor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 10:36:27 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=windows-1251 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Apr 27, 2003 at 02:48:12PM +0200, Roman Neuhauser wrote: > # roam@ringlet.net / 2003-04-26 14:53:36 +0300: > > On Fri, Apr 25, 2003 at 08:44:00PM +0200, Roman Neuhauser wrote: > > > Try the following makefile: it works if called with -DONE, but does n= ot > > > if called with -DTWO. Should I treat it as a bug and file a PR? > > >=20 > > > LIST=3D foo bar baz > > >=20 > > > .if defined(ONE) > > > . for v in ${LIST} > > > . if !defined(WITHOUT_${v:U}) > > > WITH_${v:U}=3Dyes > > > . endif > > > . endfor > > > .endif > > >=20 > > > .if defined(TWO) > > > . for v in ${LIST} > > > V=3D${v:U} > > > . if !defined(WITHOUT_${V}) > > > WITH_${V}=3Dyes > > > . endif > > > . endfor > > > .endif > > >=20 > > > a: > > > @echo \$${WITH_FOO}: ${WITH_FOO} > > > @echo \$${WITH_BAR}: ${WITH_BAR} > > > @echo \$${WITH_BAZ}: ${WITH_BAZ} > > >=20 > > > .PHONY: a > >=20 > > I think this is a known bug, and it seems to even be documented > > in the BUGS section of -STABLE's make(1) manual page. >=20 > I don't think this is covered. Can you point out the relevant text? Looking at: $FreeBSD: src/usr.bin/make/make.1,v 1.29.2.15 2002/12/17 19:01:18 seanc E= xp $ The rendered version reads, right at the end of the BUGS section: For loops are expanded before tests, so a fragment such as: .for TMACHINE in ${SHARED_ARCHS} .if ${TMACHINE} =3D ${MACHINE} ... .endif .endfor won't work, and should be rewritten the other way around. This particular part of the manual page seems to have been there for the past three years, since Tim Vanderhoek's merge from OpenBSD in rev. 1.23. At least, I think that this is similar (actually, nearly identical) to your Makefile fragment. G'luck, Peter --=20 Peter Pentchev roam@ringlet.net roam@sbnd.net roam@FreeBSD.org PGP key: http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 The rest of this sentence is written in Thailand, on --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+rlUc7Ri2jRYZRVMRAqDuAJ9/E6y3JxhXQAJ87PmkHlNmOxswEACgp8/S rZuPD5jWfXYazJ1p3KSUVUQ= =2mCL -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 06:01:49 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B7EC637B401 for ; Tue, 29 Apr 2003 06:01:49 -0700 (PDT) Received: from mail.bellavista.cz (mail.bellavista.cz [213.235.167.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AA1443F75 for ; Tue, 29 Apr 2003 06:01:48 -0700 (PDT) (envelope-from neuhauser@bellavista.cz) Received: from freepuppy.bellavista.cz (freepuppy.bellavista.cz [10.0.0.10]) by mail.bellavista.cz (Postfix) with ESMTP id 82540349 for ; Tue, 29 Apr 2003 15:01:45 +0200 (CEST) Received: by freepuppy.bellavista.cz (Postfix, from userid 1001) id 81DF62FDAB2; Tue, 29 Apr 2003 15:01:43 +0200 (CEST) Date: Tue, 29 Apr 2003 15:01:43 +0200 From: Roman Neuhauser To: freebsd-hackers Message-ID: <20030429130143.GK13541@freepuppy.bellavista.cz> Mail-Followup-To: freebsd-hackers References: <20030425184400.GS13541@freepuppy.bellavista.cz> <20030426115336.GF761@straylight.oblivion.bg> <20030427124812.GU13541@freepuppy.bellavista.cz> <20030429103404.GA680@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030429103404.GA680@straylight.oblivion.bg> User-Agent: Mutt/1.5.1i Subject: Re: make: variable expansion in .for/.endfor X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 13:01:50 -0000 # roam@ringlet.net / 2003-04-29 13:34:04 +0300: > On Sun, Apr 27, 2003 at 02:48:12PM +0200, Roman Neuhauser wrote: > > # roam@ringlet.net / 2003-04-26 14:53:36 +0300: > > > On Fri, Apr 25, 2003 at 08:44:00PM +0200, Roman Neuhauser wrote: > > > > Try the following makefile: it works if called with -DONE, but does not > > > > if called with -DTWO. Should I treat it as a bug and file a PR? > > > > > > > > LIST= foo bar baz > > > > > > > > .if defined(ONE) > > > > . for v in ${LIST} > > > > . if !defined(WITHOUT_${v:U}) > > > > WITH_${v:U}=yes > > > > . endif > > > > . endfor > > > > .endif > > > > > > > > .if defined(TWO) > > > > . for v in ${LIST} > > > > V=${v:U} > > > > . if !defined(WITHOUT_${V}) > > > > WITH_${V}=yes > > > > . endif > > > > . endfor > > > > .endif > > > > > > > > a: > > > > @echo \$${WITH_FOO}: ${WITH_FOO} > > > > @echo \$${WITH_BAR}: ${WITH_BAR} > > > > @echo \$${WITH_BAZ}: ${WITH_BAZ} > > > > > > > > .PHONY: a > > > > > > I think this is a known bug, and it seems to even be documented > > > in the BUGS section of -STABLE's make(1) manual page. > > > > I don't think this is covered. Can you point out the relevant text? > > Looking at: > $FreeBSD: src/usr.bin/make/make.1,v 1.29.2.15 2002/12/17 19:01:18 seanc Exp $ > > The rendered version reads, right at the end of the BUGS section: > > For loops are expanded before tests, so a fragment such as: > > .for TMACHINE in ${SHARED_ARCHS} > .if ${TMACHINE} = ${MACHINE} > ... > .endif > .endfor > won't work, and should be rewritten the other way around. > > This particular part of the manual page seems to have been there > for the past three years, since Tim Vanderhoek's merge from OpenBSD > in rev. 1.23. > > At least, I think that this is similar (actually, nearly identical) to > your Makefile fragment. both fragments are "nearly identical", and the first one works. it's the assignment (V=${v:U}) that breaks. so, where's the similarity (or identity), given that the snippet from the make man page is unrelated to assignments? again, the first version (wrapped in ifdef ONE) works just fine. -- If you cc me or remove the list(s) completely I'll most likely ignore your message. see http://www.eyrie.org./~eagle/faqs/questions.html From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 07:34:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 81A9037B409 for ; Tue, 29 Apr 2003 07:34:34 -0700 (PDT) Received: from sabre.velocet.net (sabre.velocet.net [216.138.209.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9453043FBF for ; Tue, 29 Apr 2003 07:34:33 -0700 (PDT) (envelope-from dgilbert@velocet.ca) Received: from trooper.velocet.ca (trooper.velocet.net [216.138.242.2]) by sabre.velocet.net (Postfix) with ESMTP id CD71113826D; Tue, 29 Apr 2003 10:34:24 -0400 (EDT) Received: by trooper.velocet.ca (Postfix, from userid 66) id 4BC8274748; Tue, 29 Apr 2003 10:34:24 -0400 (EDT) Received: by canoe.velocet.net (Postfix, from userid 101) id 8924D567607; Tue, 29 Apr 2003 10:34:20 -0400 (EDT) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16046.36204.494761.258593@canoe.velocet.net> Date: Tue, 29 Apr 2003 10:34:20 -0400 To: Oliver Fromme In-Reply-To: <200304280054.h3S0sTi2006266@lurza.secnetix.de> References: <20030427065621.G40030-100000@haldjas.folklore.ee> <200304280054.h3S0sTi2006266@lurza.secnetix.de> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid cc: freebsd-hackers@FreeBSD.ORG Subject: [hackers] Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 14:34:34 -0000 >>>>> "Oliver" == Oliver Fromme writes: Oliver> Narvi wrote: >> On Sat, 26 Apr 2003, M. Warner Losh wrote: > In message: >> <20030427064014.H40030-100000@haldjas.folklore.ee> > Narvi >> writes: > : option USE_PI_DIGITS 100 >> > >> > Only if you could implement it with integer math :-) >> >> where's the problem in that ? most mp libs use integer arithmetic, >> and x86-64 gives you 64x64->128 bit widening multiplies 8-) Oliver> You don't need that; the digits of pi can be calculated quite Oliver> easily with integer math. This snippet is from my signature Oliver> collection: Oliver> int f[9800],b,c=9814,g,i;long Oliver> a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( Oliver> "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} With gcc -o pi pi.c, the output is: [2:19:319]dgilbert@canoe:~/devel> ./pi 187700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 and so on. All Zeros. With gcc -O -o pi pi.c, the output is: [2:21:321]dgilbert@canoe:~/devel> ./pi 501859265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316 ... and so on for many digits. Neither matches: echo "scale=200; 4*a(1)" | bc -l 3.141592653589793238462643383279502884197169399375105820974944592307\ 81640628620899862803482534211706798214808651328230664709384460955058\ 223172535940812848111745028410270193852110555964462294895493038196 Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://daveg.ca | are precisely opposite. | =========================================================GLO================ From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 07:38:58 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DE0337B439 for ; Tue, 29 Apr 2003 07:38:58 -0700 (PDT) Received: from mailhub.fokus.fraunhofer.de (mailhub.fokus.fraunhofer.de [193.174.154.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD57243F3F for ; Tue, 29 Apr 2003 07:38:56 -0700 (PDT) (envelope-from brandt@fokus.fraunhofer.de) Received: from beagle (beagle [193.175.132.100])h3TEcqE19690; Tue, 29 Apr 2003 16:38:52 +0200 (MEST) Date: Tue, 29 Apr 2003 16:38:52 +0200 (CEST) From: Harti Brandt To: David Gilbert In-Reply-To: <16046.36204.494761.258593@canoe.velocet.net> Message-ID: <20030429163802.D38451@beagle.fokus.fraunhofer.de> References: <20030427065621.G40030-100000@haldjas.folklore.ee> <16046.36204.494761.258593@canoe.velocet.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-hackers@freebsd.org cc: Oliver Fromme Subject: Re: [hackers] Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 14:38:58 -0000 On Tue, 29 Apr 2003, David Gilbert wrote: DG>>>>>> "Oliver" == Oliver Fromme writes: DG> DG>Oliver> Narvi wrote: DG>>> On Sat, 26 Apr 2003, M. Warner Losh wrote: > In message: DG>>> <20030427064014.H40030-100000@haldjas.folklore.ee> > Narvi DG>>> writes: > : option USE_PI_DIGITS 100 DG>>> > DG>>> > Only if you could implement it with integer math :-) DG>>> DG>>> where's the problem in that ? most mp libs use integer arithmetic, DG>>> and x86-64 gives you 64x64->128 bit widening multiplies 8-) DG> DG>Oliver> You don't need that; the digits of pi can be calculated quite DG>Oliver> easily with integer math. This snippet is from my signature DG>Oliver> collection: DG> DG>Oliver> int f[9800],b,c=9814,g,i;long DG>Oliver> a=1e4,d,e,h;main(){for(;b=c,c-=14;i=printf( DG>Oliver> "%04d",e+d/a),e=d%a)while(g=--b*2)d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g;} DG> DG>With gcc -o pi pi.c, the output is: DG> DG>[2:19:319]dgilbert@canoe:~/devel> ./pi DG>187700000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 DG> DG>and so on. All Zeros. DG> DG>With gcc -O -o pi pi.c, the output is: DG> DG>[2:21:321]dgilbert@canoe:~/devel> ./pi DG>501859265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316 DG> DG>... and so on for many digits. Neither matches: DG> DG>echo "scale=200; 4*a(1)" | bc -l DG>3.141592653589793238462643383279502884197169399375105820974944592307\ DG>81640628620899862803482534211706798214808651328230664709384460955058\ DG>223172535940812848111745028410270193852110555964462294895493038196 If you look careful only the first four digits don't match. harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private brandt@fokus.fraunhofer.de, harti@freebsd.org From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 09:05:09 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A91637B401 for ; Tue, 29 Apr 2003 09:05:09 -0700 (PDT) Received: from antivirussmtp.procergs.com.br (antivirussmtp.procergs.com.br [200.198.128.200]) by mx1.FreeBSD.org (Postfix) with SMTP id 100AD43FAF for ; Tue, 29 Apr 2003 09:05:07 -0700 (PDT) (envelope-from marcelo-leal@procergs.rs.gov.br) Received: from honolulu.procergs.com.br(200.198.128.103) by antivirussmtp.procergs.com.br via csmap id 23749; Tue, 29 Apr 2003 13:04:57 -0300 (BRT) Received: from ws-tor-0004.procergs (unknown [172.28.5.20]) by honolulu.procergs.com.br (Postfix) with ESMTP id 6398CA936 for ; Tue, 29 Apr 2003 13:05:02 -0300 (BRT) Received: by ws-tor-0004.procergs (Postfix, from userid 1000) id E514F107C1; Tue, 29 Apr 2003 13:05:00 -0300 (BRT) Received: from procergs.rs.gov.br (localhost [127.0.0.1]) by ws-tor-0004.procergs (Postfix) with ESMTP id 8B388107C0 for ; Tue, 29 Apr 2003 13:05:00 -0300 (BRT) From: omestre@freeshell.org To: freebsd-hackers@freebsd.org Date: Tue, 29 Apr 2003 13:04:55 -0300 Sender: marcelo-leal@procergs.rs.gov.br Message-Id: <20030429160500.E514F107C1@ws-tor-0004.procergs> Subject: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 16:05:09 -0000 Hello, I'm having problems with rpc.lockd (nfs locks)... Now, i guess that i know "where is" the problem. I have one Linux box as my NFS server to Linux and FreBSD 4.x machines, working fine. I have some FreeBSD 5.0 machines that do not work the locks. Looking at the log in the Linux server, i have saw these messages: kernel: lockd: bad cookie size 16 (only cookies under 8 bytes are supported.) Without 5.0 clients, these messages go out! So, how can i make the rpc.lockd work like 4.x series? The 5.0 lock protocol, i guess, is incompatible with linux ( kernel 2.4.20). Thanks. --- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 10:00:25 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D70F937B401 for ; Tue, 29 Apr 2003 10:00:25 -0700 (PDT) Received: from mail.cruzio.com (mail.cruzio.com [63.249.95.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5426B43FCB for ; Tue, 29 Apr 2003 10:00:25 -0700 (PDT) (envelope-from brucem@cruzio.com) Received: from cruzio.com (dsl3-63-249-85-132.cruzio.com [63.249.85.132]) by mail.cruzio.com with ESMTP id h3TH4MjM066450; Tue, 29 Apr 2003 10:04:23 -0700 (PDT) Received: (from brucem@localhost) by cruzio.com (8.12.6/8.12.6/Submit) id h3TGw7qL000418; Tue, 29 Apr 2003 09:58:07 -0700 (PDT) Date: Tue, 29 Apr 2003 09:58:07 -0700 (PDT) From: "Bruce R. Montague" Message-Id: <200304291658.h3TGw7qL000418@cruzio.com> To: freebsd-hackers@FreeBSD.ORG cc: jordbaer@mac.com Subject: Re: misc patches to FreeBSD (Geode, USB, ... (from arch@freebsd.org) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 17:00:26 -0000 Hi, re the USB ohci patches Bodo RusKamp mentioned in: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2917+0+current/freebsd-arch > This contains a fix for a serious bug in the OHCI code that was present > for a very long time in FreeBSD and NetBSD: ... Manual application of the "ohci.c" patch file shows that all but two of the hunks patching usb driver file "ohci.c" are already present in "ohci.c" in the -current sources (obtained via cvsup as of 10-April-2003). The two new patches potentially effect unprotected critical sections in isochronous transfers. However, with the patches applied, isochronous transfers still only work for me for about 23 frames frames on my 'test device' (a webcam). Additionally, there appears to be other code blocks in the -current "ohci.c" that would require similar patching (that is, that aren't included in the patch). Perhaps the patches are based on older versions of ohci that don't have these other cases... The two new patches, as far as I can tell, are: 1) The hunk 4 and 5 patches to "ohci_alloc_sitd()" that adds a "s = splusb();/splx()" encapsulation around sitd descriptor updates in the case of a new allocation (these hunks have some other updates already applied in the current code), and, 2) The hunk 7 patches to "ohci_softintr()" protecting a "usb_transfer_complete()" call with a "s = splusb(); splx()". There are other calls to "usb_transfer_complete()" in this same routine that are also not protected in a splusb() critical section... - bruce From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 10:17:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A10B37B401 for ; Tue, 29 Apr 2003 10:17:27 -0700 (PDT) Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C8ED43FBD for ; Tue, 29 Apr 2003 10:17:26 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: from ussenterprise.ufp.org (bicknell@localhost [127.0.0.1]) by ussenterprise.ufp.org (8.12.9/8.12.9) with ESMTP id h3THHPq1075770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 29 Apr 2003 13:17:25 -0400 (EDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.12.9/8.12.9/Submit) id h3THHMAW075769 for freebsd-hackers@freebsd.org; Tue, 29 Apr 2003 13:17:22 -0400 (EDT) Date: Tue, 29 Apr 2003 13:17:22 -0400 From: Leo Bicknell To: freebsd-hackers@freebsd.org Message-ID: <20030429171722.GA75578@ussenterprise.ufp.org> Mail-Followup-To: freebsd-hackers@freebsd.org References: <20030427065621.G40030-100000@haldjas.folklore.ee> <200304280054.h3S0sTi2006266@lurza.secnetix.de> <16046.36204.494761.258593@canoe.velocet.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ikeVEW9yuYc//A+q" Content-Disposition: inline In-Reply-To: <16046.36204.494761.258593@canoe.velocet.net> Organization: United Federation of Planets X-PGP-Key: http://www.ufp.org/~bicknell/ Subject: Re: [hackers] Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 17:17:27 -0000 --ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good grief. 1c1 < int f[9800],b,c=3D9814,g,i;long a=3D1e4,d,e,h;main(){for(;b=3Dc,c-=3D14;i= =3Dprintf( --- > int f[9814],b,c=3D9814,g,i;long a=3D1e4,d,e,h;main(){for(;b=3Dc,c-=3D14;i= =3Dprintf( --=20 Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+rrOdNh6mMG5yMTYRArrTAJ0a6vmBmjM6wL/CFqhQIBOvVMH40QCeMD5O noBmduDK5ErbPTelALsOBQ4= =ddab -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q-- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 12:06:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71F5B37B401 for ; Tue, 29 Apr 2003 12:06:15 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id E401D43FBF for ; Tue, 29 Apr 2003 12:06:14 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0394.cvx22-bradley.dialup.earthlink.net ([209.179.199.139] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19AaQX-0006zc-00; Tue, 29 Apr 2003 12:06:06 -0700 Message-ID: <3EAECCCD.9299B2A2@mindspring.com> Date: Tue, 29 Apr 2003 12:04:45 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Harti Brandt References: <20030427065621.G40030-100000@haldjas.folklore.ee> <20030429163802.D38451@beagle.fokus.fraunhofer.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a49018b604d12a3f3d678c415ab9d6b8962601a10902912494350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org cc: David Gilbert cc: Oliver Fromme Subject: Re: [hackers] Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 19:06:15 -0000 Harti Brandt wrote: DG>501859265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316 > DG> > DG>... and so on for many digits. Neither matches: > DG> > DG>echo "scale=200; 4*a(1)" | bc -l > DG>3.141592653589793238462643383279502884197169399375105820974944592307\ > DG>81640628620899862803482534211706798214808651328230664709384460955058\ > DG>223172535940812848111745028410270193852110555964462294895493038196 > > If you look careful only the first four digits don't match. You mean the four most significant digits, right? 8-) 8-) 8-). -- Terry From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 12:54:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ECD237B401 for ; Tue, 29 Apr 2003 12:54:33 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B20743F93 for ; Tue, 29 Apr 2003 12:54:32 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h3TJsVNm076705; Tue, 29 Apr 2003 14:54:31 -0500 (CDT) (envelope-from dan) Date: Tue, 29 Apr 2003 14:54:31 -0500 From: Dan Nelson To: omestre@freeshell.org Message-ID: <20030429195431.GA22259@dan.emsphone.com> References: <20030429160500.E514F107C1@ws-tor-0004.procergs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030429160500.E514F107C1@ws-tor-0004.procergs> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: freebsd-hackers@freebsd.org Subject: Re: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 19:54:33 -0000 In the last episode (Apr 29), omestre@freeshell.org said: > I'm having problems with rpc.lockd (nfs locks)... > Now, i guess that i know "where is" the problem. I have one Linux box > as my NFS server to Linux and FreBSD 4.x machines, working fine. > I have some FreeBSD 5.0 machines that do not work the locks. Looking at > the log in the Linux server, i have saw these messages: > kernel: lockd: bad cookie size 16 (only cookies under 8 bytes are supported.) > Without 5.0 clients, these messages go out! So, how can i make the rpc.lockd > work like 4.x series? > The 5.0 lock protocol, i guess, is incompatible with linux ( kernel 2.4.20). > Thanks. FreeBSD 4.* didn't do locking at all; rpc.lockd simply accepted all requests but never tried to lock the remote sfile. FreeBSD 5's rpc.lockd does send lock requests, but the Linux kernel apparently cannot handle the 16-byte request. If you were happy with FreeBSD 4's behaviour, try just not running rpc.lockd on your FreeBSD 5 systems. If you really need locking, you can probably cut FreeBSD's cookie size down to 8 bytes by removing the pid_start element from struct lockd_msg_ident in /sys/nfsclient/nfs_lock.h (and removing the code that sets it in nfs_lock.c), and rebuilding world and the kernel. A better solution would be to submit a bugreport to your Linux vendor and have them fix it on their end. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 13:15:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E19F37B401 for ; Tue, 29 Apr 2003 13:15:34 -0700 (PDT) Received: from honolulu.procergs.com.br (honolulu.procergs.com.br [200.198.128.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 522C943F75 for ; Tue, 29 Apr 2003 13:15:33 -0700 (PDT) (envelope-from marcelo-leal@procergs.rs.gov.br) Received: from ws-tor-0004.procergs (unknown [172.28.5.20]) by honolulu.procergs.com.br (Postfix) with ESMTP id 92B4DA98A; Tue, 29 Apr 2003 17:15:30 -0300 (BRT) Received: by ws-tor-0004.procergs (Postfix, from userid 1000) id B8741107C3; Tue, 29 Apr 2003 17:15:28 -0300 (BRT) Received: from procergs.rs.gov.br (localhost [127.0.0.1]) by ws-tor-0004.procergs (Postfix) with ESMTP id A1EDD107C1; Tue, 29 Apr 2003 17:15:28 -0300 (BRT) From: omestre@freeshell.org To: Dan Nelson In-Reply-To: Message from Dan Nelson <20030429195431.GA22259@dan.emsphone.com> References: <20030429160500.E514F107C1@ws-tor-0004.procergs> <20030429195431.GA22259@dan.emsphone.com> Date: Tue, 29 Apr 2003 17:15:23 -0300 Sender: marcelo-leal@procergs.rs.gov.br Message-Id: <20030429201528.B8741107C3@ws-tor-0004.procergs> cc: freebsd-hackers@freebsd.org Subject: Re: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 20:15:34 -0000 Thanks for your answer. But, if the FreeBSD 4.x do not "lock" anything, how can i reproduce it in FreeBSD 5.0? It is not just "kill" rpc.lockd, because in FreeBSD 4.x, the programs do not know that the locks have failed. (Sorry by the english). What i want to say is: "The FreeBSD 4.x knows how to mask this situation" (very well) :) Now, in FreeBSD 5.0, after two or three days with the programs runnig, the flocks procedures returns (with sucess status). Maybe, the FreeBSD 5.0 change your behavior after some "big timeout". And if i "kill" the rpc.lockd, the flocks calls will return error, and the programs will fail. Thanks again. From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 13:41:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1725437B401 for ; Tue, 29 Apr 2003 13:41:00 -0700 (PDT) Received: from honolulu.procergs.com.br (honolulu.procergs.com.br [200.198.128.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD1A43FAF for ; Tue, 29 Apr 2003 13:40:59 -0700 (PDT) (envelope-from marcelo-leal@procergs.rs.gov.br) Received: from ws-tor-0004.procergs (unknown [172.28.5.20]) by honolulu.procergs.com.br (Postfix) with ESMTP id C941AA97A; Tue, 29 Apr 2003 17:40:53 -0300 (BRT) Received: by ws-tor-0004.procergs (Postfix, from userid 1000) id DB706107C3; Tue, 29 Apr 2003 17:40:51 -0300 (BRT) Received: from procergs.rs.gov.br (localhost [127.0.0.1]) by ws-tor-0004.procergs (Postfix) with ESMTP id C2F1D107C1; Tue, 29 Apr 2003 17:40:51 -0300 (BRT) From: omestre@freeshell.org To: Dan Nelson In-Reply-To: Message from Dan Nelson <20030429195431.GA22259@dan.emsphone.com> References: <20030429160500.E514F107C1@ws-tor-0004.procergs> <20030429195431.GA22259@dan.emsphone.com> Date: Tue, 29 Apr 2003 17:40:46 -0300 Sender: marcelo-leal@procergs.rs.gov.br Message-Id: <20030429204051.DB706107C3@ws-tor-0004.procergs> cc: freebsd-hackers@freebsd.org Subject: Re: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 20:41:00 -0000 hello again... I will make what you have sad. commnet the pid_start in the .h file. I'm in doubt about the code that i must comment in nfs_lock.c. Only the lines where pid_start appears, or the whole statement? thanks again From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 14:50:33 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44F1937B401; Tue, 29 Apr 2003 14:50:33 -0700 (PDT) Received: from mail0.ewetel.de (mail0.ewetel.de [212.6.122.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF09F43F85; Tue, 29 Apr 2003 14:50:31 -0700 (PDT) (envelope-from Thomas.Wintergerst@nord-com.net) Received: from kalak.lemur.nord.de (dialin-80-228-54-017.ewe-ip-backbone.de [80.228.54.17]) by mail0.ewetel.de (8.12.1/8.12.9) with ESMTP id h3TLoQru014104; Tue, 29 Apr 2003 23:50:28 +0200 (MEST) Received: from nord-com.net (lullog-w2k.lemur.nord.de [192.168.2.132]) by kalak.lemur.nord.de (8.12.3/8.12.3) with ESMTP id h3TLa3MX014420; Tue, 29 Apr 2003 23:36:07 +0200 (CEST) (envelope-from Thomas.Wintergerst@nord-com.net) Message-ID: <3EAEF043.6030701@nord-com.net> Date: Tue, 29 Apr 2003 23:36:03 +0200 From: Thomas Wintergerst User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: de-de, de, en-us, en MIME-Version: 1.0 To: John Baldwin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-CheckCompat: OK cc: hackers@FreeBSD.org cc: Hellmuth Michaelis Subject: Re: Request for a new major character device number X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Apr 2003 21:50:33 -0000 Hi John, John Baldwin wrote: >On 26-Apr-2003 Thomas Wintergerst wrote: > > >>Hi all, >> >>I need an "official" major device number for the CAPI subsystem for >>*BSD. The file "/usr/src/sys/conf/majors" states that I should contact >>this list to obtain a reserved major device number. The device number >>should be useable in 5.0-RELEASE and earlier releases. >> >>As You may have noticed by watching the the mailing list >>"freebsd-isdn@freebsd.org" I wrote a package for CAPI support for >>FreeBSD. For those not familiar with this term: CAPI is the "Common ISDN >>API", the standard interface to communicate over ISDN with ISDN boards. >> >>The device number is needed to link the kernel CAPI manager and its >>attached device drivers with userspace applications. >> >>Maybe Hellmuth Michaelis, maintainer of I4B, already sent out this >>request. I am in contact with him to integrate the CAPI subsystem into >>"current". >> >> > >Well, current has a device filesystem that controls /dev and doesn't >require fixed major numbers. Assuming that userland opens devices by >name, then you don't need a fixed major number for 5.x. If you backport >the driver to 4.x, then in 4.x a major number can be allocated. > Today I spoke to Hellmuth Michaelis by phone. He told me something about how major device numbers are handled in current. I am relatively new to 5.0-RELEASE and until now did not see anything about current. So I thought a major device number was still necessary. I will change to current for v5 developement and so will hopefully not need this number in this version. But v4.x will stay in use for some time and some people might want to use CAPI for BSD with these releases. So a reserved device number for 4.x would good. Currently I use 170, that was unused at least until 4.7-RELEASE. -- Regards, Thomas Wintergerst From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 23:12:54 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1827537B401; Tue, 29 Apr 2003 23:12:54 -0700 (PDT) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3276243FBF; Tue, 29 Apr 2003 23:12:51 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id h4U6Ck4H075845; Wed, 30 Apr 2003 09:12:46 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h3U5tqKP006272; Wed, 30 Apr 2003 08:55:52 +0300 (EEST) (envelope-from netch) Date: Wed, 30 Apr 2003 08:55:52 +0300 From: Valentin Nechayev To: John Baldwin Message-ID: <20030430055552.GA6089@iv.nn.kiev.ua> References: <200304112357.BAA02170@faui40p.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-42: On Organization: Dark side of coredump cc: freebsd-hackers@freebsd.org cc: Toerless Eckert Subject: Re: boot2 broken ? (booting from pst fails) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 06:12:54 -0000 Mon, Apr 14, 2003 at 10:36:55, jhb (John Baldwin) wrote about "Re: boot2 broken ? (booting from pst fails)": >> - Do you know wether Linux relies on virtual mode in booting their kernel ? >> because the vendor in my case is officially suporting linux. I guess i >> need to test setting that up and see if i can boot it from the disk. JB> Linux doesn't have a bootloader like FreeBSD. I can mistake but it seems to me GRUB works in protected mode. (Seeing stage2/asm.S in grub-0.92.) If yes, TE can ask vendor to support modern distributions with GRUB ;) -netch- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 23:13:03 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A33F237B401; Tue, 29 Apr 2003 23:13:03 -0700 (PDT) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A5F843FA3; Tue, 29 Apr 2003 23:13:01 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id h4U6Cx42075846; Wed, 30 Apr 2003 09:12:59 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h3U5vlj3006296; Wed, 30 Apr 2003 08:57:47 +0300 (EEST) (envelope-from netch) Date: Wed, 30 Apr 2003 08:57:47 +0300 From: Valentin Nechayev To: Toerless Eckert Message-ID: <20030430055747.GB6089@iv.nn.kiev.ua> References: <200304141600.SAA21075@faui40p.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304141600.SAA21075@faui40p.informatik.uni-erlangen.de> X-42: On Organization: Dark side of coredump cc: freebsd-hackers@freebsd.org Subject: Re: boot2 broken ? (booting from pst fails) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 06:13:04 -0000 Mon, Apr 14, 2003 at 18:00:28, eckert (Toerless Eckert) wrote about "Re: boot2 broken ? (booting from pst fails)": TE> When was actually this btx client concept introduced in FreeBSD ? Eg: TE> wasn't the bootstrap in before the kernel real-mode up until TE> BSD 4.x ? AFAIR, it was introduced between 3.0 and 3.1. 3.1 already had got /boot/loader very similar to modern one. -netch- From owner-freebsd-hackers@FreeBSD.ORG Tue Apr 29 23:13:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AB54337B401; Tue, 29 Apr 2003 23:13:11 -0700 (PDT) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE36043FAF; Tue, 29 Apr 2003 23:13:09 -0700 (PDT) (envelope-from netch@iv.nn.kiev.ua) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id h4U6D8Kd075848; Wed, 30 Apr 2003 09:13:08 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.12.8p1/8.12.8) id h3U6Axop006379; Wed, 30 Apr 2003 09:10:59 +0300 (EEST) (envelope-from netch) Date: Wed, 30 Apr 2003 09:10:58 +0300 From: Valentin Nechayev To: Toerless Eckert Message-ID: <20030430061058.GC6089@iv.nn.kiev.ua> References: <200304142136.XAA28381@faui40p.informatik.uni-erlangen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304142136.XAA28381@faui40p.informatik.uni-erlangen.de> X-42: On Organization: Dark side of coredump cc: freebsd-hackers@freebsd.org Subject: Re: boot2 broken ? (booting from pst fails) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 06:13:12 -0000 Mon, Apr 14, 2003 at 23:36:59, eckert (Toerless Eckert) wrote about "Re: boot2 broken ? (booting from pst fails)": TE> Don't forget that neither 3ware nor promise list FreeBSD as a supported TE> operating system, both are equally listed in FreeBSDs hardware list, TE> there's no indication that booting for one of them doesn't work but TE> that it's supposed to work on the other. Neither does the documentation TE> of boot2 or loader explain the possible issue so as to buy possible buyers. TE> It would really be nice if this boot-compatiblity/incompatiblity information TE> would be documented somehwere. Like in pst(4) and boot(8). It's not so simple as you think. HCLs (hardware compatibility lists) are stably available only having stable and documented (even under NDA) feature lists of hardware and feature access methods in software. For PC world, it isn't method of duty work; e.g. mainboard manufacturers can skip EDD support from some versions of their BIOSes basing on some internal and non-exported information and decisions, even nowadays; and booting from such mainboard requires more strict partitioning scheme or even dirty tricks (as placing unused, but formatted, FAT16 slice at beginning of boot disk). Reality in PC/Wintel world is devil's dance of drivers variants, tiny-but-painful deviations against standards, etc. Moscow PC construction market, e.g., contains now ~1000 different mainboards for P-III, P-4 and Athlon CPU groups. Who have enough resources to test all of them? ;(( OS vendor, as FreeBSD, tries to keep average between all them and provide product which working on most, and all this in conditions of permanent resource lacking. You can do your's best. You already posted here about problems of booting from such controller, and it is recorded in mailing list archives. If you can, fix it. If no, change hardware and hope that somebody will fix it as soon as possible. -netch- From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 01:01:52 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5AF4637B401; Wed, 30 Apr 2003 01:01:52 -0700 (PDT) Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BD4043FBD; Wed, 30 Apr 2003 01:01:48 -0700 (PDT) (envelope-from eckert@faui40p.informatik.uni-erlangen.de) Received: from faui40p.informatik.uni-erlangen.de (faui40p.informatik.uni-erlangen.de [131.188.34.77]) id KAA06446; Wed, 30 Apr 2003 10:01:46 +0200 (MEST) Received: (from eckert@localhost) by faui40p.informatik.uni-erlangen.de (8.9.3/8.1.6-FAU) id KAA15829; Wed, 30 Apr 2003 10:01:43 +0200 (MEST) From: Toerless Eckert Message-Id: <200304300801.KAA15829@faui40p.informatik.uni-erlangen.de> In-Reply-To: <20030430061058.GC6089@iv.nn.kiev.ua> from Valentin Nechayev at "Apr 30, 2003 9:10:58 am" To: netch@netch.kiev.ua (Valentin Nechayev) Date: Wed, 30 Apr 2003 10:01:43 +0200 (MEST) Organisation: CSD IMMD IV, University of Erlangen, Germany X-Mailer: ELM [version 2.4ME+ PL42 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-hackers@freebsd.org cc: eckert@i4.informatik.uni-erlangen.de Subject: Re: boot2 broken ? (booting from pst fails) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 08:01:52 -0000 > resource lacking. You can do your's best. You already posted here about > problems of booting from such controller, and it is recorded in mailing > list archives. If you can, fix it. If no, change hardware and hope that > somebody will fix it as soon as possible. Mailinglists are not a good way of archiving known information, it takes far too much work for people to search that information. I think if it's known that booting works/does-not-work for a given combination of hw then it would be good to document it in a bit less volatile documentation like the manual page or HW compatbilitiy list or whatever else is easie found than mailinglists archives. Cheers Toerless From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 01:51:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F31DB37B401 for ; Wed, 30 Apr 2003 01:50:59 -0700 (PDT) Received: from memphis.mephi.ru (memphis.mephi.ru [194.67.67.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B4B543F93 for ; Wed, 30 Apr 2003 01:50:58 -0700 (PDT) (envelope-from timon@memphis.mephi.ru) Received: from [10.0.1.2] (timon.memphis.mephi.ru [10.0.1.2]) by memphis.mephi.ru (8.12.6p2/8.12.6) with ESMTP id h3U8oqPt071075 for ; Wed, 30 Apr 2003 12:50:53 +0400 (MSD) (envelope-from timon@memphis.mephi.ru) From: "Artem 'Zazoobr' Ignatjev" To: freebsd-hackers@freebsd.org Content-Type: text/plain Organization: Message-Id: <1051692657.296.15.camel@timon.memphis.mephi.ru> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 30 Apr 2003 12:50:57 +0400 Content-Transfer-Encoding: 7bit Subject: Implementing a FS: some help required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 08:51:00 -0000 Hello I've recently came accross an issue with solaris/x86 hard, which was damaged so much, that it caused native solaris fsck dump a core. Since there was some important data on that hard, I started playing with that hard. It's said that Solaris uses UFS derived from 4.2BSD, and after a while I was able to mount it. I've found their disklabel structure and now I want to make BSD recognize it, so that it will automatically detect layout of their partitions. Where can i find docs on adding implementations of others filesystems into kernel? From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 02:36:01 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF40737B401 for ; Wed, 30 Apr 2003 02:36:01 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D51643F75 for ; Wed, 30 Apr 2003 02:36:01 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3U9Zws4006765; Wed, 30 Apr 2003 11:35:59 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: "Artem 'Zazoobr' Ignatjev" From: "Poul-Henning Kamp" In-Reply-To: Your message of "30 Apr 2003 12:50:57 +0400." <1051692657.296.15.camel@timon.memphis.mephi.ru> Date: Wed, 30 Apr 2003 11:35:58 +0200 Message-ID: <6764.1051695358@critter.freebsd.dk> cc: freebsd-hackers@freebsd.org Subject: Re: Implementing a FS: some help required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 09:36:02 -0000 In message <1051692657.296.15.camel@timon.memphis.mephi.ru>, "Artem 'Zazoobr' I gnatjev" writes: >Hello > >I've recently came accross an issue with solaris/x86 hard, which was >damaged so much, that it caused native solaris fsck dump a core. Since >there was some important data on that hard, I started playing with that >hard. It's said that Solaris uses UFS derived from 4.2BSD, and after a >while I was able to mount it. >I've found their disklabel structure and now I want to make BSD >recognize it, so that it will automatically detect layout of their >partitions. >Where can i find docs on adding implementations of others filesystems >into kernel? Freebsd 5.x already recognizes SUN disklabels, just add the GEOM_SUNLABEL to your kernel configuration. -- 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-hackers@FreeBSD.ORG Wed Apr 30 02:50:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23C3E37B401 for ; Wed, 30 Apr 2003 02:50:44 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E81D43F75 for ; Wed, 30 Apr 2003 02:50:38 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h3U9oaOh058094 for ; Wed, 30 Apr 2003 11:50:36 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Wed, 30 Apr 2003 11:50:36 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: freebsd-hackers@freebsd.org Message-ID: <20030430114317.V2090-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: ipfw2 interface / examples X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 09:50:44 -0000 I am recoding some firewall management code which acts on data on the application layer (to open ports etc) from ipfw to the new ipfw2. And am struggling a bit understanding what exactly to pass. - Needless to say - a bug in your rule gives one a 'Adding rule: Invalid argument' errno; is there any way/tool to decode how the IP_FW_ADD struct is passed and get some more insight ? - Is there a simpler example than ipfw2.c, or an raw docs for the getsockopt() api which helps me understand this better. In particular the from/to 'O_IN/(!O_IN)' versus the ability of ipfw.c to set both IP_FW_F_IN and IP_FW_F_OUT to make the rule symetrical around from/to. Thanks. Dw From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 07:26:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CE33237B401 for ; Wed, 30 Apr 2003 07:26:08 -0700 (PDT) Received: from smtpproxy1.mitre.org (smtpproxy1.mitre.org [192.160.51.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECCBF43F3F for ; Wed, 30 Apr 2003 07:26:07 -0700 (PDT) (envelope-from jandrese@mitre.org) Received: from avsrv1.mitre.org (avsrv1.mitre.org [129.83.20.58]) by smtpproxy1.mitre.org (8.12.9/8.12.8) with ESMTP id h3UEQ2Vb029944 for ; Wed, 30 Apr 2003 10:26:02 -0400 (EDT) Received: from MAILHUB1 (mailhub1.mitre.org [129.83.20.31]) by smtpsrv1.mitre.org (8.12.9/8.12.8) with ESMTP id h3UEPvCg024282 for ; Wed, 30 Apr 2003 10:25:57 -0400 (EDT) Received: from mm112324-2k.mitre.org (128.29.3.65) by mailhub1.mitre.org with SMTP id 2217945; Wed, 30 Apr 2003 10:25:46 -0400 Message-ID: <3EAFDCEA.3000307@mitre.org> Date: Wed, 30 Apr 2003 10:25:46 -0400 From: Jason Andresen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org References: <20030427065621.G40030-100000@haldjas.folklore.ee> <20030429163802.D38451@beagle.fokus.fraunhofer.de> <3EAECCCD.9299B2A2@mindspring.com> In-Reply-To: <3EAECCCD.9299B2A2@mindspring.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [hackers] Re: x86-64 support X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 14:26:09 -0000 Terry Lambert wrote: > Harti Brandt wrote: > DG>501859265358979323846264338327950288419716939937510582097494459230781640628620899862803482534211706798214808651328230664709384460955058223172535940812848111745028410270193852110555964462294895493038196442881097566593344612847564823378678316 > >>DG> >>DG>... and so on for many digits. Neither matches: >>DG> >>DG>echo "scale=200; 4*a(1)" | bc -l >>DG>3.141592653589793238462643383279502884197169399375105820974944592307\ >>DG>81640628620899862803482534211706798214808651328230664709384460955058\ >>DG>223172535940812848111745028410270193852110555964462294895493038196 >> >>If you look careful only the first four digits don't match. > > > You mean the four most significant digits, right? 8-) 8-) 8-). Strange though, it worked for me (although I did clean up the code a touch to see exactly what it did before I ran it): #include int main() { int f[91800],b,c=9814,g,i; long a=1e4,d,e,h; for(;b=c,c-=14;i=printf("%04d",e+d/a),e=d%a) while(g=--b*2) d=h*b+a*(i?f[b]:a/5),h=d/--g,f[b]=d%g; } % ./pi 31415926535897932384626433832795028841971693993751058209749445923078164062862089986280348253421170679821480865132823066470938446095505822317253594081284811174502841027019385211055596446229489549303819644288109756659334461284756482337867831652712019091456485669234603486104543266482133936072602491412737245870066063155881748815209209628292540917153643678925903600113305305488204665213841469519415116094330572703657595919530921861173819326117931051185480744623799627495673518857527248912279381830119491298336733624406566430860213949463952247371907021798609437027705392171762931767523846748184676694051320005681271452635608277857713427577896091736371787214684409012249534301465495853710507922796892589235420199561121290219608640344181598136297747713099605187072113499999983729780499510597317328160963185950244594553469083026425223082533446850352619311881710100031378387528865875332083814206171776691473035982534904287554687311595628638823537875937519577818577805321712268066130019278766111959 092164201989380952572010654858632788659361533818279682303019520353018529689957736225994138912497217752834791315155748572424541506959508295331168617278558890750983817546374649393192550604009277016711390098488240128583616035637076601047101819429555961989467678374494482553797747268471040475346462080466842590694912933136770289891521047521620569660240580381501935112533824300355876402474964732639141992726042699227967823547816360093417216412199245863150302861829745557067498385054945885869269956909272107975093029553211653449872027559602364806654991198818347977535663698074265425278625518184175746728909777727938000816470600161452491921732172147723501414419735685481613611573525521334757418494684385233239073941433345477624168625189835694855620992192221842725502542568876717904946016534668049886272327917860857843838279679766814541009538837863609506800642251252051173929848960841284886269456042419652850222106611863067442786220391949450471237137869609563643719172874677646575739624138908658326 459958133904780275900994657640789512694683983525957098258226205224894077267194782684826014769909026401363944374553050682034962524517493996514314298091906592509372216964615157098583874105978859597729754989301617539284681382686838689427741559918559252459539594310499725246808459872736446958486538367362226260991246080512438843904512441365497627807977156914359977001296160894416948685558484063534220722258284886481584560285060168427394522674676788952521385225499546667278239864565961163548862305774564980355936345681743241125150760694794510965960940252288797108931456691368672287489405601015033086179286809208747609178249385890097149096759852613655497818931297848216829989487226588048575640142704775551323796414515237462343645428584447952658678 I made f bigger than I needed to, but it was only on a hunch with the original code (which dumped core). -- \ |_ _|__ __|_ \ __| Jason Andresen jandrese@mitre.org |\/ | | | / _| Network and Distributed Systems Engineer _| _|___| _| _|_\___| Office: 703-883-7755 From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 08:07:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3DE5537B401 for ; Wed, 30 Apr 2003 08:07:12 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4BF343FAF for ; Wed, 30 Apr 2003 08:07:10 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 56F775308; Wed, 30 Apr 2003 17:07:09 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Poul-Henning Kamp" From: Dag-Erling Smorgrav Date: Wed, 30 Apr 2003 17:07:08 +0200 In-Reply-To: <6764.1051695358@critter.freebsd.dk> ("Poul-Henning Kamp"'s message of "Wed, 30 Apr 2003 11:35:58 +0200") Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 References: <6764.1051695358@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-hackers@freebsd.org Subject: Re: Implementing a FS: some help required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 15:07:12 -0000 "Poul-Henning Kamp" writes: > Freebsd 5.x already recognizes SUN disklabels, just add the > GEOM_SUNLABEL to your kernel configuration. Would it be possible to make geoms dynamically loadable? DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 08:09:11 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 327C437B401 for ; Wed, 30 Apr 2003 08:09:10 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 05FE143FBD for ; Wed, 30 Apr 2003 08:09:09 -0700 (PDT) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h3UF97Nj007233; Wed, 30 Apr 2003 17:09:07 +0200 (CEST) (envelope-from phk@phk.freebsd.dk) To: Dag-Erling Smorgrav From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 30 Apr 2003 17:07:08 +0200." Date: Wed, 30 Apr 2003 17:09:07 +0200 Message-ID: <7232.1051715347@critter.freebsd.dk> cc: freebsd-hackers@freebsd.org Subject: Re: Implementing a FS: some help required X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 15:09:11 -0000 In message , Dag-Erling Smorgrav writes: >"Poul-Henning Kamp" writes: >> Freebsd 5.x already recognizes SUN disklabels, just add the >> GEOM_SUNLABEL to your kernel configuration. > >Would it be possible to make geoms dynamically loadable? Yes, it's in the roadmap, but there are a few things on top of it. -- 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-hackers@FreeBSD.ORG Wed Apr 30 08:37:16 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22E4637B401 for ; Wed, 30 Apr 2003 08:37:16 -0700 (PDT) Received: from spmler1.mail.eds.com (spmler1.mail.eds.com [194.128.225.190]) by mx1.FreeBSD.org (Postfix) with ESMTP id C46B743F93 for ; Wed, 30 Apr 2003 08:37:14 -0700 (PDT) (envelope-from thomas.sparrevohn@eds.com) Received: from spmlir2.mail.eds.com (spmlir2.mail.eds.com [205.191.69.42] (may be forged)) by spmler1.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UFb0901853; Wed, 30 Apr 2003 16:37:01 +0100 Received: from spmlir2.mail.eds.com (localhost [127.0.0.1]) by spmlir2.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UFb0Y16861; Wed, 30 Apr 2003 16:37:00 +0100 Received: from ukspm101.exgb01.exch.eds.com ([204.230.90.43]) by spmlir2.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UFb0O16821; Wed, 30 Apr 2003 16:37:00 +0100 Received: by ukspm101.exgb01.exch.eds.com with Internet Mail Service (5.5.2656.59) id ; Wed, 30 Apr 2003 16:37:03 +0100 Message-ID: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A5@GBCHM201> From: "Sparrevohn, Thomas" To: "'omestre@freeshell.org'" Date: Wed, 30 Apr 2003 16:37:00 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain cc: "'freebsd-hackers@freebsd.org'" Subject: RE: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 15:37:16 -0000 After changing my FS to UFS2 yesterday I saw strange behaviour from rpc.statd and rpc.lockd - The statd process grew to 256MB in size. There are memory leaks some where in the 5.0-Release with UFS2 that I did not see with UFS1 - It seems that inactive pages are never reclaimed and on a 1GB system during a make world I ended up with 8MB free. -- Thomas -----Original Message----- From: omestre@freeshell.org [mailto:omestre@freeshell.org] Sent: 29 April 2003 17:05 To: freebsd-hackers@freebsd.org Subject: rpc.lockd Hello, I'm having problems with rpc.lockd (nfs locks)... Now, i guess that i know "where is" the problem. I have one Linux box as my NFS server to Linux and FreBSD 4.x machines, working fine. I have some FreeBSD 5.0 machines that do not work the locks. Looking at the log in the Linux server, i have saw these messages: kernel: lockd: bad cookie size 16 (only cookies under 8 bytes are supported.) Without 5.0 clients, these messages go out! So, how can i make the rpc.lockd work like 4.x series? The 5.0 lock protocol, i guess, is incompatible with linux ( kernel 2.4.20). Thanks. --- _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 09:35:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1BC737B401 for ; Wed, 30 Apr 2003 09:35:46 -0700 (PDT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC54343F3F for ; Wed, 30 Apr 2003 09:35:45 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.9/8.12.9) id h3UGZgJ6072810; Wed, 30 Apr 2003 11:35:42 -0500 (CDT) (envelope-from dan) Date: Wed, 30 Apr 2003 11:35:42 -0500 From: Dan Nelson To: "Sparrevohn, Thomas" Message-ID: <20030430163542.GB90046@dan.emsphone.com> References: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A5@GBCHM201> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A5@GBCHM201> X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.4i cc: "'freebsd-hackers@freebsd.org'" cc: "'omestre@freeshell.org'" Subject: Re: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 16:35:47 -0000 In the last episode (Apr 30), Sparrevohn, Thomas said: > After changing my FS to UFS2 yesterday I saw strange behaviour from > rpc.statd and rpc.lockd - The statd process grew to 256MB in size. > There are memory leaks some where in the 5.0-Release with UFS2 that I > did not see with UFS1 - It seems that inactive pages are never > reclaimed and on a 1GB system during a make world I ended up with 8MB > free. rpc.statd is always that size; you probably never noticed it before. It mmaps a 256MB window, but only uses a couple KB of it. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LEAK -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 09:58:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E71FE37B401 for ; Wed, 30 Apr 2003 09:58:42 -0700 (PDT) Received: from spmler3.mail.eds.com (spmler3.mail.eds.com [194.128.225.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4B8C43FB1 for ; Wed, 30 Apr 2003 09:58:41 -0700 (PDT) (envelope-from thomas.sparrevohn@eds.com) Received: from spmlir2.mail.eds.com (spmlir2.mail.eds.com [205.191.69.42]) by spmler3.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UGwLT09073; Wed, 30 Apr 2003 12:58:21 -0400 Received: from spmlir2.mail.eds.com (localhost [127.0.0.1]) by spmlir2.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UGwLY22160; Wed, 30 Apr 2003 17:58:21 +0100 Received: from gbspm011.exgb01.exch.eds.com ([207.37.51.203]) by spmlir2.mail.eds.com (8.11.6p2/8.11.6) with ESMTP id h3UGwLO22154; Wed, 30 Apr 2003 17:58:21 +0100 Received: by GBSPM011 with Internet Mail Service (5.5.2656.59) id ; Wed, 30 Apr 2003 17:58:27 +0100 Message-ID: <2946E9F05C8DD511A7DC0002A5608CE4BEC3A6@GBCHM201> From: "Sparrevohn, Thomas" To: "'Dan Nelson'" Date: Wed, 30 Apr 2003 17:58:21 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2656.59) Content-Type: text/plain cc: "'freebsd-hackers@freebsd.org'" cc: "'omestre@freeshell.org'" Subject: RE: rpc.lockd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 16:58:43 -0000 Most likely - I noticed that I did not release the pages - but due to the other error I was trying to figure out what kept the pages inactive without releasing them. It rules out rpc.statd, Thanks -- Thomas -----Original Message----- From: Dan Nelson [mailto:dnelson@allantgroup.com] Sent: 30 April 2003 17:36 To: Sparrevohn, Thomas Cc: 'omestre@freeshell.org'; 'freebsd-hackers@freebsd.org' Subject: Re: rpc.lockd In the last episode (Apr 30), Sparrevohn, Thomas said: > After changing my FS to UFS2 yesterday I saw strange behaviour from > rpc.statd and rpc.lockd - The statd process grew to 256MB in size. > There are memory leaks some where in the 5.0-Release with UFS2 that I > did not see with UFS1 - It seems that inactive pages are never > reclaimed and on a 1GB system during a make world I ended up with 8MB > free. rpc.statd is always that size; you probably never noticed it before. It mmaps a 256MB window, but only uses a couple KB of it. http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/admin.html#STATD-MEM-LE AK -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-hackers@FreeBSD.ORG Wed Apr 30 13:09:10 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FE4F37B401 for ; Wed, 30 Apr 2003 13:09:10 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id C79D243FBD for ; Wed, 30 Apr 2003 13:09:09 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0231.cvx40-bradley.dialup.earthlink.net ([216.244.42.231] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19Axsj-0007XR-00; Wed, 30 Apr 2003 13:08:45 -0700 Message-ID: <3EB02CEB.F27C40B7@mindspring.com> Date: Wed, 30 Apr 2003 13:07:07 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Toerless Eckert References: <200304300801.KAA15829@faui40p.informatik.uni-erlangen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a475b35ca5d914f3110faa7bbe589a1df5667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c cc: freebsd-hackers@freebsd.org cc: Valentin Nechayev Subject: Re: boot2 broken ? (booting from pst fails) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 20:09:10 -0000 Toerless Eckert wrote: > > resource lacking. You can do your's best. You already posted here about > > problems of booting from such controller, and it is recorded in mailing > > list archives. If you can, fix it. If no, change hardware and hope that > > somebody will fix it as soon as possible. > > Mailinglists are not a good way of archiving known information, > it takes far too much work for people to search that information. > I think if it's known that booting works/does-not-work for a given > combination of hw then it would be good to document it in a bit less > volatile documentation like the manual page or HW compatbilitiy list or > whatever else is easie found than mailinglists archives. Are you volunteering? -- Terry From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 07:51:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 42E0A37B401 for ; Thu, 1 May 2003 07:51:44 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3F8B43F3F for ; Thu, 1 May 2003 07:51:43 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id C07155308; Thu, 1 May 2003 16:51:41 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: hackers@freebsd.org From: Dag-Erling Smorgrav Date: Thu, 01 May 2003 16:51:40 +0200 Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 14:51:44 -0000 Why does the following code in OpenPAM headers: /* * XSSO 5.4 */ enum { PAM_SILENT = 0x80000000, PAM_DISALLOW_NULL_AUTHTOK = 0x1, PAM_ESTABLISH_CRED = 0x1, PAM_DELETE_CRED = 0x2, PAM_REINITIALIZE_CRED = 0x4, PAM_REFRESH_CRED = 0x8, PAM_PRELIM_CHECK = 0x1, PAM_UPDATE_AUTHTOK = 0x2, PAM_CHANGE_EXPIRED_AUTHTOK = 0x4 }; cause the following warning when compiled with CSTD=c99: /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' when 0x80000000 is clearly within the range of 'int' on all platforms we support? DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 07:59:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0996037B405 for ; Thu, 1 May 2003 07:59:12 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id E786C43FAF for ; Thu, 1 May 2003 07:59:10 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.8p1/8.12.3) with ESMTP id h41ExABp034136; Thu, 1 May 2003 07:59:10 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.8p1/8.12.3/Submit) id h41ExAD2034135; Thu, 1 May 2003 07:59:10 -0700 (PDT) (envelope-from rizzo) Date: Thu, 1 May 2003 07:59:09 -0700 From: Luigi Rizzo To: Dag-Erling Smorgrav Message-ID: <20030501075909.B33903@xorpc.icir.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: ; from des@ofug.org on Thu, May 01, 2003 at 04:51:40PM +0200 cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 14:59:12 -0000 On Thu, May 01, 2003 at 04:51:40PM +0200, Dag-Erling Smorgrav wrote: ... > PAM_SILENT = 0x80000000, ... > cause the following warning when compiled with CSTD=c99: > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' > > when 0x80000000 is clearly within the range of 'int' on all platforms > we support? maybe 0x80000000 gets interpreted as unsigned and then the compiler complains. E.g. in machine/limits.h you find #define INT_MIN (-0x7fffffff - 1) /* min value for an int */ (to tell the truth you also find there the following definition for UINT_MAX, and I don't understand why the 'U' is necessary then) #define UINT_MAX 0xffffffffU /* max value for an unsigned int */ cheers luigi > DES > -- > Dag-Erling Smorgrav - des@ofug.org > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:06:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB91437B401 for ; Thu, 1 May 2003 08:06:44 -0700 (PDT) Received: from mail.speakeasy.net (mail16.speakeasy.net [216.254.0.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AB0543F85 for ; Thu, 1 May 2003 08:06:44 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 14849 invoked from network); 1 May 2003 15:06:47 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 1 May 2003 15:06:47 -0000 Received: from laptop.baldwin.cx ([216.133.140.1]) by server.baldwin.cx (8.12.8/8.12.8) with ESMTP id h41F6fOv025765; Thu, 1 May 2003 11:06:42 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 01 May 2003 11:06:45 -0400 (EDT) From: John Baldwin To: Dag-Erling Smorgrav cc: hackers@freebsd.org Subject: RE: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:06:45 -0000 On 01-May-2003 Dag-Erling Smorgrav wrote: > Why does the following code in OpenPAM headers: > > /* > * XSSO 5.4 > */ > enum { > PAM_SILENT = 0x80000000, > PAM_DISALLOW_NULL_AUTHTOK = 0x1, > PAM_ESTABLISH_CRED = 0x1, > PAM_DELETE_CRED = 0x2, > PAM_REINITIALIZE_CRED = 0x4, > PAM_REFRESH_CRED = 0x8, > PAM_PRELIM_CHECK = 0x1, > PAM_UPDATE_AUTHTOK = 0x2, > PAM_CHANGE_EXPIRED_AUTHTOK = 0x4 > }; > > cause the following warning when compiled with CSTD=c99: > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts > enumerator values to range of `int' > > when 0x80000000 is clearly within the range of 'int' on all platforms > we support? On an i386: #define INT_MAX 0x7fffffff /* max value for an int */ 0x80000000 > 0x7fffffff -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:07:15 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D366437B408 for ; Thu, 1 May 2003 08:07:15 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id D72D843FBF for ; Thu, 1 May 2003 08:07:14 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 5110AB4; Thu, 1 May 2003 10:07:14 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 9D43E78C4A; Thu, 1 May 2003 10:07:13 -0500 (CDT) Date: Thu, 1 May 2003 10:07:13 -0500 From: "Jacques A. Vidrine" To: Dag-Erling Smorgrav Message-ID: <20030501150713.GA34992@madman.celabo.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:07:16 -0000 On Thu, May 01, 2003 at 04:51:40PM +0200, Dag-Erling Smorgrav wrote: > Why does the following code in OpenPAM headers: > > /* > * XSSO 5.4 > */ > enum { > PAM_SILENT = 0x80000000, > PAM_DISALLOW_NULL_AUTHTOK = 0x1, > PAM_ESTABLISH_CRED = 0x1, > PAM_DELETE_CRED = 0x2, > PAM_REINITIALIZE_CRED = 0x4, > PAM_REFRESH_CRED = 0x8, > PAM_PRELIM_CHECK = 0x1, > PAM_UPDATE_AUTHTOK = 0x2, > PAM_CHANGE_EXPIRED_AUTHTOK = 0x4 > }; > > cause the following warning when compiled with CSTD=c99: > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' > > when 0x80000000 is clearly within the range of 'int' on all platforms > we support? Guessing: C does not specify one's complement or two's complement representation of integers. On a one's complement 32-bit platform, 0x80000000 is -0 (negative zero), which cannot be an `int'. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:20:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C556D37B401; Thu, 1 May 2003 08:20:27 -0700 (PDT) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id F20A843F85; Thu, 1 May 2003 08:20:26 -0700 (PDT) (envelope-from stefan@fafoe.dyndns.org) Received: from wombat.fafoe (wombat.fafoe [192.168.2.102]) by fafoe.dyndns.org (Postfix) with ESMTP id 31A603FC4; Thu, 1 May 2003 17:20:25 +0200 (CEST) Received: by wombat.fafoe (Postfix, from userid 1001) id 912BF5E; Thu, 1 May 2003 17:20:22 +0200 (CEST) Date: Thu, 1 May 2003 17:20:22 +0200 From: Stefan Farfeleder To: "Jacques A. Vidrine" Message-ID: <20030501152022.GC568@wombat.fafoe> Mail-Followup-To: "Jacques A. Vidrine" , Dag-Erling Smorgrav , hackers@freebsd.org References: <20030501150713.GA34992@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501150713.GA34992@madman.celabo.org> User-Agent: Mutt/1.5.4i cc: hackers@freebsd.org cc: Dag-Erling Smorgrav Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:20:28 -0000 On Thu, May 01, 2003 at 10:07:13AM -0500, Jacques A. Vidrine wrote: > On Thu, May 01, 2003 at 04:51:40PM +0200, Dag-Erling Smorgrav wrote: > > Why does the following code in OpenPAM headers: > > > > enum { > > PAM_SILENT = 0x80000000, <...> > > }; > > > > cause the following warning when compiled with CSTD=c99: > > > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' > > > > when 0x80000000 is clearly within the range of 'int' on all platforms > > we support? > > Guessing: > C does not specify one's complement or two's complement representation > of integers. On a one's complement 32-bit platform, 0x80000000 is -0 > (negative zero), which cannot be an `int'. 6.4.4.1 Integer constants <...> The type of an integer constant is the first of the corresponding list in which its value can be represented. int unsigned int long int unsigned long int long long int unsigned long long int [This is for hexadecimal constants without suffix.] Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has type unsigned. But enumeration constants always have type int, that's why you're getting this warning. Regards, Stefan Farfeleder From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:24:36 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D2A5137B401 for ; Thu, 1 May 2003 08:24:36 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DF2643F85 for ; Thu, 1 May 2003 08:24:34 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 96EE9B4; Thu, 1 May 2003 10:24:33 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id E3BB278C4A; Thu, 1 May 2003 10:24:32 -0500 (CDT) Date: Thu, 1 May 2003 10:24:32 -0500 From: "Jacques A. Vidrine" To: Dag-Erling Smorgrav , hackers@freebsd.org Message-ID: <20030501152432.GC34992@madman.celabo.org> References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501152022.GC568@wombat.fafoe> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:24:37 -0000 On Thu, May 01, 2003 at 05:20:22PM +0200, Stefan Farfeleder wrote: > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has You forgot to quote where INT_MAX is defined in the standard. -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:37:41 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0CC4937B401; Thu, 1 May 2003 08:37:41 -0700 (PDT) Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDC1A43F85; Thu, 1 May 2003 08:37:36 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from haldjas.folklore.ee (localhost [127.0.0.1]) by haldjas.folklore.ee (8.12.3/8.11.3) with ESMTP id h41FbZ6U001033; Thu, 1 May 2003 18:37:35 +0300 (EEST) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost)h41FbZwd001030; Thu, 1 May 2003 18:37:35 +0300 (EEST) Date: Thu, 1 May 2003 18:37:35 +0300 (EEST) From: Narvi To: "Jacques A. Vidrine" In-Reply-To: <20030501150713.GA34992@madman.celabo.org> Message-ID: <20030501181950.G40030-100000@haldjas.folklore.ee> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: hackers@freebsd.org cc: Dag-Erling Smorgrav Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:37:41 -0000 On Thu, 1 May 2003, Jacques A. Vidrine wrote: > On Thu, May 01, 2003 at 04:51:40PM +0200, Dag-Erling Smorgrav wrote: > > Why does the following code in OpenPAM headers: > > > > /* > > * XSSO 5.4 > > */ > > enum { > > PAM_SILENT = 0x80000000, > > PAM_DISALLOW_NULL_AUTHTOK = 0x1, > > PAM_ESTABLISH_CRED = 0x1, > > PAM_DELETE_CRED = 0x2, > > PAM_REINITIALIZE_CRED = 0x4, > > PAM_REFRESH_CRED = 0x8, > > PAM_PRELIM_CHECK = 0x1, > > PAM_UPDATE_AUTHTOK = 0x2, > > PAM_CHANGE_EXPIRED_AUTHTOK = 0x4 > > }; > > > > cause the following warning when compiled with CSTD=c99: > > > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' > > > > when 0x80000000 is clearly within the range of 'int' on all platforms > > we support? > > Guessing: > C does not specify one's complement or two's complement representation > of integers. On a one's complement 32-bit platform, 0x80000000 is -0 > (negative zero), which cannot be an `int'. > -0 would be a valid int on a one's complement platform It would probably compare equal to zero. Gcc only runs on 2-s complement platforms anyways. > Cheers, > -- > Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal > nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se > From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 08:43:12 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A3D7237B401; Thu, 1 May 2003 08:43:12 -0700 (PDT) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAD2A43F85; Thu, 1 May 2003 08:43:11 -0700 (PDT) (envelope-from stefan@fafoe.dyndns.org) Received: from wombat.fafoe (wombat.fafoe [192.168.2.102]) by fafoe.dyndns.org (Postfix) with ESMTP id B57754061; Thu, 1 May 2003 17:43:10 +0200 (CEST) Received: by wombat.fafoe (Postfix, from userid 1001) id 3207C5E; Thu, 1 May 2003 17:43:08 +0200 (CEST) Date: Thu, 1 May 2003 17:43:08 +0200 From: Stefan Farfeleder To: "Jacques A. Vidrine" Message-ID: <20030501154307.GD568@wombat.fafoe> Mail-Followup-To: "Jacques A. Vidrine" , hackers@freebsd.org References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> <20030501152432.GC34992@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501152432.GC34992@madman.celabo.org> User-Agent: Mutt/1.5.4i cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 15:43:12 -0000 On Thu, May 01, 2003 at 10:24:32AM -0500, Jacques A. Vidrine wrote: > On Thu, May 01, 2003 at 05:20:22PM +0200, Stefan Farfeleder wrote: > > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has > > You forgot to quote where INT_MAX is defined in the standard. 5.2.4.2.1 Sizes of integer types -- maximum value for an object of type int INT_MAX +32767 // 2^15 - 1 [where 32767 is the smallest legal value for INT_MAX] Regards, Stefan Farfeleder From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 12:02:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E88F937B401 for ; Thu, 1 May 2003 12:02:00 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 8387143FE1 for ; Thu, 1 May 2003 12:02:00 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 86689 invoked by uid 1000); 1 May 2003 19:02:01 -0000 Date: Thu, 1 May 2003 12:02:01 -0700 (PDT) From: Nate Lawson To: hackers@freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: hsf/hcf conexant winmodem support? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 19:02:01 -0000 This question has come up before but I lost the URL. I belive someone (I think in .jp) had done a port of the Linux conexant hsf/hcf winmodem drivers. Anyone have a pointer to that? The Linux code is at: http://www.linuxant.com/drivers/ -Nate From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 14:03:44 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B87C637B401; Thu, 1 May 2003 14:03:44 -0700 (PDT) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8450143FCB; Thu, 1 May 2003 14:03:43 -0700 (PDT) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 8B03A530E; Thu, 1 May 2003 23:03:41 +0200 (CEST) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Jacques A. Vidrine" From: Dag-Erling Smorgrav Date: Thu, 01 May 2003 23:03:40 +0200 In-Reply-To: <20030501152022.GC568@wombat.fafoe> (Stefan Farfeleder's message of "Thu, 1 May 2003 17:20:22 +0200") Message-ID: User-Agent: Gnus/5.090015 (Oort Gnus v0.15) Emacs/21.3 References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 21:03:45 -0000 Stefan Farfeleder writes: > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has > type unsigned. But enumeration constants always have type int, that's > why you're getting this warning. but 0x80000000 == INT_MIN on 32-bit two's complement systems... DES -- Dag-Erling Smorgrav - des@ofug.org From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 14:34:24 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E329C37B401 for ; Thu, 1 May 2003 14:34:24 -0700 (PDT) Received: from falcon.midgard.homeip.net (h76n3fls20o913.telia.com [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id 6FC5843FB1 for ; Thu, 1 May 2003 14:34:22 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: (qmail 51819 invoked by uid 1001); 1 May 2003 21:34:19 -0000 Date: Thu, 1 May 2003 23:34:18 +0200 From: Erik Trulsson To: Dag-Erling Smorgrav Message-ID: <20030501213418.GA42794@falcon.midgard.homeip.net> Mail-Followup-To: Dag-Erling Smorgrav , "Jacques A. Vidrine" , hackers@freebsd.org References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i cc: "Jacques A. Vidrine" cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 21:34:25 -0000 On Thu, May 01, 2003 at 11:03:40PM +0200, Dag-Erling Smorgrav wrote: > Stefan Farfeleder writes: > > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has > > type unsigned. But enumeration constants always have type int, that's > > why you're getting this warning. > > but 0x80000000 == INT_MIN on 32-bit two's complement systems... No. 0x80000000 has type unsigned int (assuming 32-bit int) and is thus a large positive number. INT_MIN has type signed int and is a negative number. The fact that they happen to have the same representation does not mean they are the same thing. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 14:43:31 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 796A037B401; Thu, 1 May 2003 14:43:31 -0700 (PDT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C98C43FDD; Thu, 1 May 2003 14:43:31 -0700 (PDT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id h41LhQj10372; Thu, 1 May 2003 14:43:26 -0700 (PDT) Date: Thu, 1 May 2003 14:43:26 -0700 From: Mike Hunter To: Dag-Erling Smorgrav , "Jacques A. Vidrine" , hackers@FreeBSD.org Message-ID: <20030501214326.GA10277@ack.Berkeley.EDU> References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> <20030501213418.GA42794@falcon.midgard.homeip.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501213418.GA42794@falcon.midgard.homeip.net> User-Agent: Mutt/1.4i Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 21:43:31 -0000 On May 01, "Erik Trulsson" wrote: > On Thu, May 01, 2003 at 11:03:40PM +0200, Dag-Erling Smorgrav wrote: > > Stefan Farfeleder writes: > > > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has > > > type unsigned. But enumeration constants always have type int, that's > > > why you're getting this warning. > > > > but 0x80000000 == INT_MIN on 32-bit two's complement systems... > > No. 0x80000000 has type unsigned int (assuming 32-bit int) and is thus > a large positive number. INT_MIN has type signed int and is a negative > number. The fact that they happen to have the same representation does > not mean they are the same thing. #include #include int main () { printf("%d\n", (0x80000000 == INT_MIN)); return 0; } ./a.out 1 Just pointing out that they do "==" each other, which is what was said. Mike From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 15:16:40 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59FB437B401; Thu, 1 May 2003 15:16:40 -0700 (PDT) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96BF443F85; Thu, 1 May 2003 15:16:39 -0700 (PDT) (envelope-from stefan@fafoe.dyndns.org) Received: from wombat.fafoe (wombat.fafoe [192.168.2.102]) by fafoe.dyndns.org (Postfix) with ESMTP id 3A2BA3FC4; Fri, 2 May 2003 00:16:36 +0200 (CEST) Received: by wombat.fafoe (Postfix, from userid 1001) id 5483DD1; Fri, 2 May 2003 00:16:32 +0200 (CEST) Date: Fri, 2 May 2003 00:16:32 +0200 From: Stefan Farfeleder To: Mike Hunter Message-ID: <20030501221631.GB546@wombat.fafoe> Mail-Followup-To: Mike Hunter , Dag-Erling Smorgrav , "Jacques A. Vidrine" , hackers@FreeBSD.org References: <20030501150713.GA34992@madman.celabo.org> <20030501152022.GC568@wombat.fafoe> <20030501213418.GA42794@falcon.midgard.homeip.net> <20030501214326.GA10277@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030501214326.GA10277@ack.Berkeley.EDU> User-Agent: Mutt/1.5.4i cc: "Jacques A. Vidrine" cc: hackers@FreeBSD.org cc: Dag-Erling Smorgrav Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 22:16:40 -0000 On Thu, May 01, 2003 at 02:43:26PM -0700, Mike Hunter wrote: > On May 01, "Erik Trulsson" wrote: > > > On Thu, May 01, 2003 at 11:03:40PM +0200, Dag-Erling Smorgrav wrote: > > > Stefan Farfeleder writes: > > > > Because 0x80000000 > INT_MAX on 32-Bit architectures, 0x80000000 has > > > > type unsigned. But enumeration constants always have type int, that's > > > > why you're getting this warning. > > > > > > but 0x80000000 == INT_MIN on 32-bit two's complement systems... > > > > No. 0x80000000 has type unsigned int (assuming 32-bit int) and is thus > > a large positive number. INT_MIN has type signed int and is a negative > > number. The fact that they happen to have the same representation does > > not mean they are the same thing. > > #include > #include > > int main () > { > printf("%d\n", (0x80000000 == INT_MIN)); > return 0; > } > > ./a.out > 1 > > Just pointing out that they do "==" each other, which is what was said. That is because the comparison is done in unsigned arithmetics due to the "usual arithmetic conversions". The negative int value INT_MIN is converted to unsigned int by adding UINT_MAX + 1 before the comparison is evaluated. Regards, Stefan Farfeleder From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 15:31:48 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D3E0237B401; Thu, 1 May 2003 15:31:48 -0700 (PDT) Received: from bitblocks.com (bitblocks.com [209.204.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4498E43FBD; Thu, 1 May 2003 15:31:48 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by bitblocks.com (8.12.9/8.12.9) with ESMTP id h41MVePF062201; Thu, 1 May 2003 15:31:40 -0700 (PDT) (envelope-from bakul@bitblocks.com) Message-Id: <200305012231.h41MVePF062201@bitblocks.com> To: Stefan Farfeleder In-reply-to: Your message of "Fri, 02 May 2003 00:16:32 +0200." <20030501221631.GB546@wombat.fafoe> Date: Thu, 01 May 2003 15:31:40 -0700 From: Bakul Shah cc: Mike Hunter cc: Dag-Erling Smorgrav cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 22:31:49 -0000 > > int main () > > { > > printf("%d\n", (0x80000000 == INT_MIN)); > > return 0; > > } > > > > ./a.out > > 1 > > > > Just pointing out that they do "==" each other, which is what was said. > > That is because the comparison is done in unsigned arithmetics due to > the "usual arithmetic conversions". The negative int value INT_MIN is > converted to unsigned int by adding UINT_MAX + 1 before the comparison > is evaluated. \begin{nitpicking} 0x80000000 is *not* an unsigned int, just a regular signed int but outside the legal range. An unsigned int literal has to have a U at the end. Since 0x80000000 > INT_MAX, all bets are off. The result is unspecified and happens to be 1 on a 2s complement 32 bit machine but can be 0 or anything else on a ones complement machine or where int is not 32 bits wide. \end{nitpicking} From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 15:43:45 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C26E937B401 for ; Thu, 1 May 2003 15:43:42 -0700 (PDT) Received: from fafoe.dyndns.org (chello212186121237.14.vie.surfer.at [212.186.121.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22EA743F93 for ; Thu, 1 May 2003 15:43:42 -0700 (PDT) (envelope-from stefan@fafoe.dyndns.org) Received: from wombat.fafoe (wombat.fafoe [192.168.2.102]) by fafoe.dyndns.org (Postfix) with ESMTP id 4034A3FC4; Fri, 2 May 2003 00:43:39 +0200 (CEST) Received: by wombat.fafoe (Postfix, from userid 1001) id 089CED1; Fri, 2 May 2003 00:43:34 +0200 (CEST) Date: Fri, 2 May 2003 00:43:34 +0200 From: Stefan Farfeleder To: Bakul Shah Message-ID: <20030501224334.GD546@wombat.fafoe> Mail-Followup-To: Bakul Shah , hackers@freebsd.org References: <20030501221631.GB546@wombat.fafoe> <200305012231.h41MVePF062201@bitblocks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305012231.h41MVePF062201@bitblocks.com> User-Agent: Mutt/1.5.4i cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 22:43:46 -0000 On Thu, May 01, 2003 at 03:31:40PM -0700, Bakul Shah wrote: > \begin{nitpicking} > 0x80000000 is *not* an unsigned int, just a regular signed > int but outside the legal range. It is and I quoted the relevant section of ISO/IEC 9899:1999 in this thread. Stefan Farfeleder From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 15:45:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5ADB37B401 for ; Thu, 1 May 2003 15:45:59 -0700 (PDT) Received: from falcon.midgard.homeip.net (h76n3fls20o913.telia.com [213.67.148.76]) by mx1.FreeBSD.org (Postfix) with SMTP id 7555143F85 for ; Thu, 1 May 2003 15:45:57 -0700 (PDT) (envelope-from ertr1013@student.uu.se) Received: (qmail 1879 invoked by uid 1001); 1 May 2003 22:45:53 -0000 Date: Fri, 2 May 2003 00:45:53 +0200 From: Erik Trulsson To: Bakul Shah Message-ID: <20030501224552.GA91998@falcon.midgard.homeip.net> Mail-Followup-To: Bakul Shah , Stefan Farfeleder , Mike Hunter , Dag-Erling Smorgrav , hackers@freebsd.org References: <20030501221631.GB546@wombat.fafoe> <200305012231.h41MVePF062201@bitblocks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305012231.h41MVePF062201@bitblocks.com> User-Agent: Mutt/1.5.4i cc: hackers@freebsd.org cc: Mike Hunter cc: Stefan Farfeleder cc: Dag-Erling Smorgrav Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 May 2003 22:46:00 -0000 On Thu, May 01, 2003 at 03:31:40PM -0700, Bakul Shah wrote: > > > int main () > > > { > > > printf("%d\n", (0x80000000 == INT_MIN)); > > > return 0; > > > } > > > > > > ./a.out > > > 1 > > > > > > Just pointing out that they do "==" each other, which is what was said. > > > > That is because the comparison is done in unsigned arithmetics due to > > the "usual arithmetic conversions". The negative int value INT_MIN is > > converted to unsigned int by adding UINT_MAX + 1 before the comparison > > is evaluated. > > \begin{nitpicking} > 0x80000000 is *not* an unsigned int, just a regular signed > int but outside the legal range. An unsigned int literal has > to have a U at the end. Since 0x80000000 > INT_MAX, all bets > are off. The result is unspecified and happens to be 1 on a > 2s complement 32 bit machine but can be 0 or anything else on > a ones complement machine or where int is not 32 bits wide. > \end{nitpicking} Your nitpicking is wrong. The type of 0x80000000 (or other hex-constants without any suffix) is the first of int unsigned int long unsigned long long long unsigned long long in which the value of the constant can be represented without overflow. For 32-bit int the first of the types above that can hold the value 2^31 without overflow is unsigned int. -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 17:46:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FA2C37B401 for ; Thu, 1 May 2003 17:46:43 -0700 (PDT) Received: from ussenterprise.ufp.org (ussenterprise.ufp.org [208.185.30.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13B7343F3F for ; Thu, 1 May 2003 17:46:43 -0700 (PDT) (envelope-from bicknell@ussenterprise.ufp.org) Received: from ussenterprise.ufp.org (bicknell@localhost [127.0.0.1]) by ussenterprise.ufp.org (8.12.9/8.12.9) with ESMTP id h420kcq1062705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 1 May 2003 20:46:38 -0400 (EDT) Received: (from bicknell@localhost) by ussenterprise.ufp.org (8.12.9/8.12.9) id h420kZ7B062704 for hackers@freebsd.org; Thu, 1 May 2003 20:46:35 -0400 (EDT) Date: Thu, 1 May 2003 20:46:35 -0400 From: Leo Bicknell To: hackers@freebsd.org Message-ID: <20030502004635.GA62467@ussenterprise.ufp.org> Mail-Followup-To: hackers@freebsd.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+HP7ph2BbKc20aGI" Content-Disposition: inline Organization: United Federation of Planets X-PGP-Key: http://www.ufp.org/~bicknell/ Subject: Sendmail submit. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 00:46:51 -0000 --+HP7ph2BbKc20aGI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I finally switched to sendmail w/submit, as freebsd has come with by default now for a few versions. Unfortunately with my semi-complex mail setup something strange is happening with mail originated from the local box. After much googling, I've concluded the submit config file is poorly documented. :) If there's someone on here that really understands submit.mc/cf and how it should work and would be willing to answer a few questions please drop me a note off-list. --=20 Leo Bicknell - bicknell@ufp.org - CCIE 3440 PGP keys at http://www.ufp.org/~bicknell/ Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org --+HP7ph2BbKc20aGI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+sb/rNh6mMG5yMTYRAjyyAJ9yELbN94YNtELrrYn96kRYcC+GLwCggJt0 d2AT1Qa8hgyMdk2xb98K7j8= =SjjS -----END PGP SIGNATURE----- --+HP7ph2BbKc20aGI-- From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 18:18:08 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DFC137B401; Thu, 1 May 2003 18:18:08 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 610EB43FA3; Thu, 1 May 2003 18:18:07 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h421I6A7012693; Thu, 1 May 2003 19:18:06 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 01 May 2003 19:17:50 -0600 (MDT) Message-Id: <20030501.191750.12268648.imp@bsdimp.com> To: nectar@freebsd.org From: "M. Warner Losh" In-Reply-To: <20030501150713.GA34992@madman.celabo.org> References: <20030501150713.GA34992@madman.celabo.org> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org cc: des@ofug.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 01:18:08 -0000 In message: <20030501150713.GA34992@madman.celabo.org> "Jacques A. Vidrine" writes: : > when 0x80000000 is clearly within the range of 'int' on all platforms : > we support? : : Guessing: : C does not specify one's complement or two's complement representation : of integers. On a one's complement 32-bit platform, 0x80000000 is -0 : (negative zero), which cannot be an `int'. No. The reason is that 0x800000000 is a positive number that's bigger than MAX_INT (which is 0x7fffffff). It isn't bigger than an unsigned int, but it is larger than an int, but the standard doesn't say 'unsigned int' it says 'int' which implies signed. Warner From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 18:18:42 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1206E37B404 for ; Thu, 1 May 2003 18:18:42 -0700 (PDT) Received: from backmaster.cdsnet.net (backmaster.cdsnet.net [63.163.68.2]) by mx1.FreeBSD.org (Postfix) with SMTP id F052743FCB for ; Thu, 1 May 2003 18:18:40 -0700 (PDT) (envelope-from mrcpu@backmaster.cdsnet.net) Received: (qmail 8883 invoked by uid 29999); 2 May 2003 01:18:39 -0000 Date: Thu, 1 May 2003 18:18:39 -0700 From: Jaye Mathisen To: hackers@freebsd.org Message-ID: <20030502011839.GU19993@backmaster.cdsnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: atapifd/afd0 issue. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 01:18:42 -0000 FreeBSD 4.8 I have this cool little gizmo that reads a bunch of different media formats, plugs into an IDE channel, and at least loads the kernel from the device, but can't mount root. http://www.addonics.com/products/flash_memory_reader/ide_ultra_digidrive.asp I have atapifd in the kernel, but the messages I get are: afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 afd0: floppy device - NO DRIVER! However, as I said, it's able to get to the "mountroot" phase of booting, so I'm thinking it's pretty darn close to working. Any ideas on anythign I can try to make this work? It mounts in a floppy bay, so makes the port external, which is nice, going to use it in a little router box. Any ideas/tips appreciated. From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 20:54:30 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4BEE437B401 for ; Thu, 1 May 2003 20:54:30 -0700 (PDT) Received: from bitblocks.com (bitblocks.com [209.204.185.216]) by mx1.FreeBSD.org (Postfix) with ESMTP id B776143F85 for ; Thu, 1 May 2003 20:54:29 -0700 (PDT) (envelope-from bakul@bitblocks.com) Received: from bitblocks.com (localhost [127.0.0.1]) by bitblocks.com (8.12.9/8.12.9) with ESMTP id h423sMPF063284; Thu, 1 May 2003 20:54:24 -0700 (PDT) (envelope-from bakul@bitblocks.com) Message-Id: <200305020354.h423sMPF063284@bitblocks.com> To: Erik Trulsson , Stefan Farfeleder In-reply-to: Your message of "Fri, 02 May 2003 00:45:53 +0200." <20030501224552.GA91998@falcon.midgard.homeip.net> Date: Thu, 01 May 2003 20:54:22 -0700 From: Bakul Shah cc: hackers@freebsd.org Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 03:54:30 -0000 > Your nitpicking is wrong. Yes, indeed. I should have checked the standard instead of relying on my faulty memory. Thanks for a gentle correction and apologies for misleading anyone. From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 22:57:32 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C54A437B401 for ; Thu, 1 May 2003 22:57:32 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7B8843FCB for ; Thu, 1 May 2003 22:57:30 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.8p1/8.12.8) id h425vS73056299; Fri, 2 May 2003 07:57:28 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200305020557.h425vS73056299@spider.deepcore.dk> In-Reply-To: <20030502011839.GU19993@backmaster.cdsnet.net> To: Jaye Mathisen Date: Fri, 2 May 2003 07:57:28 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: hackers@FreeBSD.ORG Subject: Re: atapifd/afd0 issue. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 05:57:33 -0000 It seems Jaye Mathisen wrote: > > FreeBSD 4.8 > > I have this cool little gizmo that reads a bunch of different > media formats, plugs into an IDE channel, and at least loads the kernel > from the device, but can't mount root. > > http://www.addonics.com/products/flash_memory_reader/ide_ultra_digidrive.asp > > I have atapifd in the kernel, but the messages I get are: > > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > afd0: floppy device - NO DRIVER! This suggests that the device does not support reading the capabilities page. You will probably need a hack like the one present for the IOMEGA Clik! in the atapi-fd.c driver. Seems this device is just as non-standard compliant as the IOMEGA product it tries to emulate :( -S鴕en From owner-freebsd-hackers@FreeBSD.ORG Thu May 1 23:57:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5451F37B401 for ; Thu, 1 May 2003 23:57:57 -0700 (PDT) Received: from web15212.mail.bjs.yahoo.com (web15212.mail.bjs.yahoo.com [202.3.77.142]) by mx1.FreeBSD.org (Postfix) with SMTP id 65BDF43FAF for ; Thu, 1 May 2003 23:57:55 -0700 (PDT) (envelope-from fellforan@yahoo.com.cn) Message-ID: <20030502065753.96501.qmail@web15212.mail.bjs.yahoo.com> Received: from [210.15.53.130] by web15212.mail.bjs.yahoo.com via HTTP; Fri, 02 May 2003 14:57:53 CST Date: Fri, 2 May 2003 14:57:53 +0800 (CST) From: =?gb2312?q?bai=20song?= To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: 8bit Subject: Re: flashpluginwrapper problem. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 06:57:57 -0000 --- Norikatsu Shigemura 的正文：> 日期: Sun, 27 Apr 2003 05:44:03 +0900 (JST) > 发件人: Norikatsu Shigemura > 收件人: Joe Kelsey > 抄送: freebsd-stable@FreeBSD.org > 抄送: brent@bermls.oau.org > 主题: Re: flashpluginwrapper problem. > > On 25 Apr 2003 18:34:24 -0700 > Joe Kelsey wrote: > > See ports/48470. More than 2 months ago, I > submitted a change to the > > flashpluginwrapper port to add a helper script to > allow people to easily > > automate this process. The patch is just sitting > there, ignored. > > Oops, sorry. I have no time for release > engineering for it. > In > http://tmp.ninth-nine.com/FlashPluginWrapper/2003-03-21/ > there are it's release candidate alpha version. > Some messages should be fixed and brushed up. > > I think I make a patch for run-mozila.sh in > www/mozilla, > www/mozilla-vendor, www/mozilla-devel. OK? > > SAMPLE PATCH for www/mozilla's > files/patch-build_unix_run-mozilla.sh > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - > Index: patch-build_unix_run-mozilla.sh > =================================================================== > RCS file: > /home/ncvs/ports/www/mozilla/files/patch-build_unix_run-mozilla.sh,v > retrieving revision 1.2 > diff -u -r1.2 patch-build_unix_run-mozilla.sh > --- patch-build_unix_run-mozilla.sh 23 Oct 2002 > 04:43:14 -0000 1.2 > +++ patch-build_unix_run-mozilla.sh 26 Apr 2003 > 20:36:50 -0000 > @@ -1,5 +1,5 @@ > ---- build/unix/run-mozilla.sh.orig Wed Oct 23 > 00:08:03 2002 > -+++ build/unix/run-mozilla.sh Wed Oct 23 00:08:59 > 2002 > +--- build/unix/run-mozilla.sh.orig Fri Feb 14 > 05:30:52 2003 > ++++ build/unix/run-mozilla.sh Sun Apr 27 05:36:20 > 2003 > @@ -355,7 +355,7 @@ > fi > ## > @@ -9,8 +9,8 @@ > if [ -n "$LD_LIBRARYN32_PATH" ] > then > > LD_LIBRARYN32_PATH=${MOZ_DIST_BIN}:${MOZ_DIST_BIN}/plugins:${MRE_HOME}${LD_LIBRARYN32_PATH+":$LD_LIBRARYN32_PATH"} > -@@ -392,7 +392,7 @@ > - export XSUNTRANSPORT XSUNSMESIZE > +@@ -402,7 +402,7 @@ > + fi > fi > # Font path for Xft > > -FONTCONFIG_PATH="/etc/fonts:${MOZILLA_FIVE_HOME}/res/Xft" > @@ -18,11 +18,13 @@ > export FONTCONFIG_PATH > > if [ "$moz_debug" -eq 1 ] > -@@ -435,6 +435,9 @@ > +@@ -445,6 +445,11 @@ > # > export MOZILLA_FIVE_HOME LD_LIBRARY_PATH > export SHLIB_PATH LIBPATH LIBRARY_PATH ADDON_PATH > DYLD_LIBRARY_PATH > + > ++LD_PRELOAD=/usr/local/lib/flash/flashwrapper.so > ++export LD_PRELOAD > +MOZ_PLUGIN_PATH=%%PREFIX%%/lib/browser_plugins > +export MOZ_PLUGIN_PATH > > - - - - - - - - - - - - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" _________________________________________________________ Do You Yahoo!? 相见不如聊天!不出门一样面对面！网络摄像头对对派送中~赶快用你的雅虎电邮帐号参与吧…… http://cn.rd.yahoo.com/mail_cn/tag/?http://cn.messenger.yahoo.com/ From owner-freebsd-hackers@FreeBSD.ORG Fri May 2 03:46:23 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7BA3A37B401 for ; Fri, 2 May 2003 03:46:23 -0700 (PDT) Received: from mail.acquirer.com (mail.acquirer.com [213.190.156.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 072B743F75 for ; Fri, 2 May 2003 03:46:22 -0700 (PDT) (envelope-from nick-list@netability.ie) X-Envelope-To: Received: from [192.168.100.44] (pancake.netability.ie [192.168.100.44]) by mail.acquirer.com (8.12.9/8.12.3) with ESMTP id h42AkJJZ025520 for ; Fri, 2 May 2003 11:46:19 +0100 (IST) (envelope-from nick-list@netability.ie) From: Nick Hilliard To: hackers@freebsd.org Content-Type: text/plain Organization: Message-Id: <1051872378.90848.53.camel@pancake.netability.ie> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 02 May 2003 11:46:19 +0100 Content-Transfer-Encoding: 7bit Subject: Re: hsf/hcf conexant winmodem support? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 10:46:23 -0000 > This question has come up before but I lost the URL. I belive someone > (I think in .jp) had done a port of the Linux conexant hsf/hcf > winmodem drivers. Anyone have a pointer to that? The Linux code is > at: > http://www.linuxant.com/drivers/ I think you might be confusing this with the lucent winmodem driver, which is in the ports. To my knowledge, there is no port of the Conexant drivers. Several people have attempted to contact Linuxant and its predecessor, MBSI, about porting the code, but there has been little or no response from them. There are a number of problems with the code: it would be a lot more difficult to port to 4.x than 5.x due to dependence on various kernel functionality. It also uses FP in the kernel - although to be fair, it looks like all FP code is suitably wrapped with os specific functions. Also, Linuxant changed the license a couple of weeks ago so that beta drivers are now not freely redistributable under a bsd-style license, and that reverse engineering is not allowed. As they only have beta drivers available, this is a pain in the butt. It should be possible to port the code. There are several portions to it: the actual driver is provided in obj format and for the most part uses scrambled function names so that you can't tell what it's doing. There are a bunch of external symbols which refer to os-specific code, which is provided in the linux port. Most of what's going on has equivalent functionality in the 5.x kernel. It looks like Linuxant have access to the driver source-code, because some of the function calls start with _Linux and do linuxy-kernel stuff. This makes the code more difficult to port, because you're starting off with more linux dependence. Nick From owner-freebsd-hackers@FreeBSD.ORG Fri May 2 08:12:38 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 88D5937B401 for ; Fri, 2 May 2003 08:12:38 -0700 (PDT) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72B9343FBF for ; Fri, 2 May 2003 08:12:37 -0700 (PDT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h42FCUA7017659; Fri, 2 May 2003 09:12:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Fri, 02 May 2003 09:12:22 -0600 (MDT) Message-Id: <20030502.091222.22499453.imp@bsdimp.com> To: sos@spider.deepcore.dk From: "M. Warner Losh" In-Reply-To: <200305020557.h425vS73056299@spider.deepcore.dk> References: <20030502011839.GU19993@backmaster.cdsnet.net> <200305020557.h425vS73056299@spider.deepcore.dk> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: mrcpu@internetcds.com cc: hackers@freebsd.org Subject: Re: atapifd/afd0 issue. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 15:12:38 -0000 In message: <200305020557.h425vS73056299@spider.deepcore.dk> Soeren Schmidt writes: : It seems Jaye Mathisen wrote: : > : > FreeBSD 4.8 : > : > I have this cool little gizmo that reads a bunch of different : > media formats, plugs into an IDE channel, and at least loads the kernel : > from the device, but can't mount root. : > : > http://www.addonics.com/products/flash_memory_reader/ide_ultra_digidrive.asp : > : > I have atapifd in the kernel, but the messages I get are: : > : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: MODE_SENSE_BIG - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 : > afd0: floppy device - NO DRIVER! : : This suggests that the device does not support reading the capabilities : page. You will probably need a hack like the one present for the : IOMEGA Clik! in the atapi-fd.c driver. : : Seems this device is just as non-standard compliant as the IOMEGA : product it tries to emulate :( IOMEGA sucks in this reguard. I don't think they believe in the read capabilities page for any of their products. Warner From owner-freebsd-hackers@FreeBSD.ORG Fri May 2 14:24:50 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB4CC37B401 for ; Fri, 2 May 2003 14:24:50 -0700 (PDT) Received: from mail.advantagecom.net (mail.advantagecom.net [65.103.151.155]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2140043FBF for ; Fri, 2 May 2003 14:24:50 -0700 (PDT) (envelope-from andykinney@advantagecom.net) Received: from SCSI-MONSTER (scsi-monster.advantagecom.net [207.109.186.200]) by mail.advantagecom.net (8.11.6/8.11.6) with ESMTP id h42LOni10111 for ; Fri, 2 May 2003 14:24:49 -0700 From: "Andrew Kinney" Organization: Advantagecom Networks, Inc. To: freebsd-hackers@freebsd.org Date: Fri, 2 May 2003 14:24:47 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Message-ID: <3EB27FAF.9300.FD28393@localhost> Priority: normal X-mailer: Pegasus Mail for Win32 (v3.12c) Subject: need opinion on kernel debug output from crash dump X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: andykinney@advantagecom.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 21:24:51 -0000 Hello, I finally managed to get an IDE drive into our system that's been having nightly panics while running a cron job and finally got a crash dump out of it. I've got the debug output from the crash dump and I think I'm reading it correctly, but I'd like a second opinion. # uname -smr FreeBSD 4.7-RELEASE-p7 i386 # gdb -k kernel.debug.03-13-03 vmcore.0 SMP 2 cpus IdlePTD at phsyical address 0x00357000 initial pcb at physical address 0x002c04c0 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0xbfc00000 fault code = supervisor write, page not present instruction pointer = 0x8:0xc024dafd stack pointer = 0x10:0xfac94e04 frame pointer = 0x10:0xfac94e10 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 = 30307 (perl5) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 30 8 1 1 1 1 1 1 1 done Uptime: 3d18h49m47s mlx0: flushing cache...done mlxd0: detached mlxd1: detached xl0: reset didn't complete dumping to dev #ad/0x20001, offset 984064 dump ata0: resetting devices .. done 3615 ... 0 --- #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 487 if (dumping++) { (kgdb) where #0 dumpsys () at /usr/src/sys/kern/kern_shutdown.c:487 #1 0xc017335b in boot (howto=256) at /usr/src/sys/kern/kern_shutdown.c:316 #2 0xc01737b4 in poweroff_wait (junk=0xc02937f9, howto=-1071041841) at /usr/src/sys/kern/kern_shutdown.c:595 #3 0xc0251c78 in trap_fatal (frame=0xfac94dc4, eva=3217031168) at /usr/src/sys/i386/i386/trap.c:974 #4 0xc0251909 in trap_pfault (frame=0xfac94dc4, usermode=0, eva=3217031168) at /usr/src/sys/i386/i386/trap.c:867 #5 0xc02514a7 in trap (frame={tf_fs = 24, tf_es = 16, tf_ds = 16, tf_edi = 16384, tf_esi = -94850808, tf_ebp = -87470576, tf_isp = -87470608, tf_ebx = 0, tf_edx = -1052901760, tf_ecx = 0, tf_eax = 556142595, tf_trapno = 12, tf_err = 2, tf_eip = -1071326467, tf_cs = 8, tf_eflags = 66054, tf_esp = -1024212940, tf_ss = 136142848}) at /usr/src/sys/i386/i386/trap.c:466 #6 0xc024dafd in pmap_qenter (va=0, m=0xfa58b108, count=4) at /usr/src/sys/i386/i386/pmap.c:786 #7 0xc0183bae in pipe_build_write_buffer (wpipe=0xfa58b0e0, uio=0xfac94ed0) at /usr/src/sys/kern/sys_pipe.c:593 #8 0xc0183d80 in pipe_direct_write (wpipe=0xfa58b0e0, uio=0xfac94ed0) at /usr/src/sys/kern/sys_pipe.c:708 #9 0xc0184122 in pipe_write (fp=0xcbb2ce00, uio=0xfac94ed0, cred=0xcf0cde80, flags=0, p=0xfa68b820) at /usr/src/sys/kern/sys_pipe.c:826 #10 0xc018247d in dofilewrite (p=0xfa68b820, fp=0xcbb2ce00, fd=1, buf=0x81d2000, nbyte=16384, offset=-1, flags=0) at /usr/src/sys/sys/file.h:162 #11 0xc0182336 in write (p=0xfa68b820, uap=0xfac94f80) at /usr/src/sys/kern/sys_generic.c:329 #12 0xc0251fa9 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 20459, tf_esi = 672929112, tf_ebp = -1077938456, tf_isp = -87470124, tf_ebx = 672929580, tf_edx = 672929112, tf_ecx = 136126464, tf_eax = 4, tf_trapno = 672126832, tf_err = 2, tf_eip = 672882720, tf_cs = 31, tf_eflags = 647, tf_esp = -1077938500, tf_ss = 47}) at /usr/src/sys/i386/i386/trap.c:1175 #13 0xc023f93b in Xint0x80_syscall () cannot read proc at 0 Each panic has the same instruction pointer, so the problem is consistent. On line 6 of the debugger output, you can see that the value for "va" is 0. Shouldn't that be some non-zero value? As used in that function, "va" is supposed to contain a virtual address from KVA space, right? If that's the case, would a zero value indicate that the system had run out KVA space? How would someone tell how much KVA space is in use? I'm sure this information can be found or calculated in some manner, but I'm just not sure how to get the information. Our limit on this sytem for KVA space is 1GB (the default). There is approximately 3500MB of RAM available for use (after BIOS maps out space for PCI devices within the 4GB address space). The system is tuned up to support the kinds of loads that are easily handled by a system with dual 2GHz processors and tons of RAM. I know that running out of KVA space is the most likely cause of the panic since we've tuned the system with higher settings on things that can eat into KVA space, but I would like to be certain before I go fiddling with KVA_PAGES in my kernel config. Thanks in advance for the second opinion on the cause of this panic. Sincerely, Andrew Kinney President and Chief Technology Officer Advantagecom Networks, Inc. http://www.advantagecom.net From owner-freebsd-hackers@FreeBSD.ORG Fri May 2 14:38:07 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7388A37B40A for ; Fri, 2 May 2003 14:38:07 -0700 (PDT) Received: from mx.vvo.ru (mx.vvo.ru [212.107.196.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B3D43F85 for ; Fri, 2 May 2003 14:38:03 -0700 (PDT) (envelope-from kenga@vvo.ru) Received: from [212.107.205.26] by mx.vvo.ru (NTMail 5.06.0014/CM4133.52.28e0adbc) with ESMTP id rgqfcaaa for freebsd-hackers@freebsd.org; Sat, 3 May 2003 08:44:48 +1100 From: "PAS Laboratry" To: "" Content-Type: multipart/mixed; boundary="x0x0x0x0x0x0x0x0x0x0x0x0x"; charset="Windows-1251" Date: Sat, 3 May 2003 08:44:48 +1100 Message-Id: <21444808604496@mx.vvo.ru> X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Need representative X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 May 2003 21:38:07 -0000 --x0x0x0x0x0x0x0x0x0x0x0x0x Content-Type: multipart/related; boundary="letters0x0x0x0x0x0x0x0x0x0x0x0x"; charset="Windows-1251" --letters0x0x0x0x0x0x0x0x0x0x0x0x MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1251" Best for you! We are finding a person who is represent new diagnostic device in the region. The device is based on the theory of Oriental medicine and it is named as PAS - [cid:x97aimage_0.jpg] A new processing principle of Pulse waves on the PC is using by the PAS. The developer has found this principle after 14 years of researches On the Five Elements diagrams that are worked out by the PAS you could see the conditions of the elements (in accordance with TCM) and their activity too. Such diagram is a direct order what to do. For example: 1. To chose the diet (in accordance with Ayrveda), 2. To massage by the any method using active points on the body, 3. To use acupuncture properly. There are many applications in researching herbology, homeopathy and so on. Such wide application of the device demands a well-organized network of distributors and we are ready to support our distributors. OUR discounts reach up to 90%!!! If the dealer sells more than 2000 registration, he/she can have such huge discount (but in one region can be only one such dealer). You can test the PAS and we will return the money if the device is not suitable for you (You pay only delivery fees). Why we think the PAS is useful for many people? It is well known fact that skilled pulse doctor works for many years before he will reach the art of diagnosis. The PAS allows be almost the same professor in three or five weeks. It is revolution of penetration of ancient knowledge to our days. Now many people can receive the correct and fast diagnosis at early stages of illness. We are proud that we do a very useful thing and we are sure, in the nearest future many people will use the PAS. And we are very interested in equal in rights partnership in your region. Please ask the details right now via e-mail [1]tigertel@stl.ru. We will answer in a very short time. The information about PAS you can find at the site: [2]www.tiger-tele.com/pas/english/index.html Best regards, the team of the PAS and the manager Serguei Fedotov. Sorry, if our letter disturbed you. References 1. mailto:tigertel@stl.ru 2. file://localhost/tmp/www.tiger-tele.com/pas/english/index.html --letters0x0x0x0x0x0x0x0x0x0x0x0x-- --x0x0x0x0x0x0x0x0x0x0x0x0x-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 03:42:23 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 247B237B401 for ; Sat, 3 May 2003 03:42:23 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C5BB43FBD for ; Sat, 3 May 2003 03:42:19 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h43AgHOh090507 for ; Sat, 3 May 2003 12:42:17 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Sat, 3 May 2003 12:42:17 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: freebsd-hackers@freebsd.org Message-ID: <20030503123757.W62023-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: CompactFlash / new GEOM / boot fails on certain brand / Soekris X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 10:42:23 -0000 Not sure if I am chasing a FreeBSD problem or a deficiency in certain ATA flash cards which lack, say sector 0, or something. On 5.0 release - on a soekris.com 4521. Several essentially identical flash disks brands: 1. SAMSUNG CF/ATA 126 Mbyte fails 2. Hitachi CVM1.1.1 125 Mbyte boots 3. SunDisk 126 Mbyte boots 4. PANASONIC/CF 125 Mbyte boots with identical content/scripted-preparation method. All of them boot; except the ones of the SAMSUNG type which the other gives a 'read error' in the bios on boot: comBIOS ver. 1.10 20020603 Copyright (C) 2000-2002 Soekris Engineering. Soekris Engineering net4501 CPU 80486 134 Mhz 0064 Mbyte Memory Primary Master SAMSUNG CF/ATA 126 Mbyte PXE-M00: BootManage UNDI, PXE-2.0 (build 082) 1 Seconds to automatic boot. Press Ctrl-P for entering Monitor. Read error ( or alternatively, at some boots, it will go into PXE boot immediately not even seeing the disk) The other disk launch into the boot loader fine. The main issue that the failing type of disk is commonly found in shops in the Netherlands; and not readily distinguishable from other types/brands. I.e. the label on the outside says nothing :-( *All* disks will allow a dd if=/dev/at0 from beginning to end and return the right data. Suggesting that sector 0.. end is reliably read/writable. Or is there certain data which gets written to the disk which is NOT visible that way? Any suggestions what could cause this ? -> is this a HW issue / ATA compatibility issue; i.e. are some Compact Flash disks fundamentally unbootable because the lack something ? -> is this a BIOS issue ? -> is this related to the new GEOM work ? It is very reproducable. Below is the (scripted) process which is used to create the disk; which as said, functions for virtually all disks except a few. dd-ing or other operations give -no- soft/hard read or write errors. http://wleiden.webweaving.org:8080/svn/node-config/master/install-time/make-cf.sh or the key lines from the above script: dd if=/dev/zero of=/dev/ad0 fdisk -BI ad0 disklabel -w -B ad0s1 auto disklabel ad0s1 | egrep unused | sed "s/c:/a:/" | sed "s/unused.*/4.2BSD/" > f disklabel -R -B ad0s1 f boot0cfg -v -B ad0 newfs /dev/ad0s1a tar files Below are the values extracted from the disk. Apart from cylinder counts they are identical to other flash disks which function (and which where created with the same process). Any thougds ? Dw dubbeldrank# fdisk -v ad0 ******* Working on device /dev/ad0 ******* parameters extracted from in-core disklabel are: cylinders=496 heads=16 sectors/track=32 (512 blks/cyl) parameters to be used for BIOS calculations are: cylinders=496 heads=16 sectors/track=32 (512 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 32, size 253920 (123 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 495/ head 15/ sector 32 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: dubbeldrank# disklabel -r ad0 disklabel: bad pack magic number (label is damaged, or pack is unlabeled) dubbeldrank# disklabel -r ad0s1 # /dev/ad0s1c: type: unknown disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 32 tracks/cylinder: 16 sectors/cylinder: 512 cylinders: 495 sectors/unit: 253920 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] a: 253920 32 4.2BSD 1024 8192 31744 # (Cyl. 0*- 495*) c: 253920 32 unused 0 0 # (Cyl. 0*- 495*) partition a: partition extends past end of unit partition c: partition extends past end of unit Warning, partition c doesn't start at 0! Warning, An incorrect partition c may cause problems for standard system utilities dubbeldrank# boot0cfg -v ad0 # flag start chs type end chs offset size 1 0x80 0: 1: 1 0xa5 495: 15:32 32 253920 version=1.0 drive=0x80 mask=0xf ticks=182 options=nopacket,update,nosetdrv dubbeldrank# mount /dev/ad0s1a /mnt dubbeldrank# ls /mnt .cshrc bin dev proc tmp From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 05:30:00 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0449437B401; Sat, 3 May 2003 05:30:00 -0700 (PDT) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4391E43F3F; Sat, 3 May 2003 05:29:59 -0700 (PDT) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (#6@localhost [127.0.0.1]) by whizzo.transsys.com (8.12.9/8.12.7) with ESMTP id h43CTw1L067503; Sat, 3 May 2003 08:29:58 -0400 (EDT) (envelope-from louie@whizzo.transsys.com) Message-Id: <200305031229.h43CTw1L067503@whizzo.transsys.com> X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4 To: "Jacques A. Vidrine" X-Image-URL: http://www.transsys.com/louie/images/louie-mail.jpg From: "Louis A. Mamakos" References: <20030501150713.GA34992@madman.celabo.org> In-reply-to: Your message of "Thu, 01 May 2003 10:07:13 CDT." <20030501150713.GA34992@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 May 2003 08:29:58 -0400 Sender: louie@TransSys.COM cc: hackers@freebsd.org cc: Dag-Erling Smorgrav Subject: Re: incorrect enum warning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 12:30:00 -0000 > On Thu, May 01, 2003 at 04:51:40PM +0200, Dag-Erling Smorgrav wrote: > > Why does the following code in OpenPAM headers: > > > > /* > > * XSSO 5.4 > > */ > > enum { > > PAM_SILENT = 0x80000000, > > PAM_DISALLOW_NULL_AUTHTOK = 0x1, > > PAM_ESTABLISH_CRED = 0x1, > > PAM_DELETE_CRED = 0x2, > > PAM_REINITIALIZE_CRED = 0x4, > > PAM_REFRESH_CRED = 0x8, > > PAM_PRELIM_CHECK = 0x1, > > PAM_UPDATE_AUTHTOK = 0x2, > > PAM_CHANGE_EXPIRED_AUTHTOK = 0x4 > > }; > > > > cause the following warning when compiled with CSTD=c99: > > > > /usr/src/contrib/openpam/include/security/pam_constants.h:100: warning: ISO C restricts enumerator values to range of `int' > > > > when 0x80000000 is clearly within the range of 'int' on all platforms > > we support? > > Guessing: > C does not specify one's complement or two's complement representation > of integers. On a one's complement 32-bit platform, 0x80000000 is -0 > (negative zero), which cannot be an `int'. That's incorrect; on a 32-bit 1's complement CPU, 0xffffffff is -0. You're thinking of the signed magnitude representation. louie > From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 07:59:38 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D39937B401 for ; Sat, 3 May 2003 07:59:38 -0700 (PDT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C10C843FAF for ; Sat, 3 May 2003 07:59:37 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.8p1/8.12.3) with ESMTP id h43ExWOH010829; Sat, 3 May 2003 07:59:32 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.8p1/8.12.3/Submit) id h43ExWGv010828; Sat, 3 May 2003 07:59:32 -0700 (PDT) (envelope-from rizzo) Date: Sat, 3 May 2003 07:59:32 -0700 From: Luigi Rizzo To: Dirk-Willem van Gulik Message-ID: <20030503075932.A10701@xorpc.icir.org> References: <20030503123757.W62023-100000@foem> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030503123757.W62023-100000@foem>; from dirkx@webweaving.org on Sat, May 03, 2003 at 12:42:17PM +0200 cc: freebsd-hackers@freebsd.org Subject: Re: CompactFlash / new GEOM / boot fails on certain brand / Soekris X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 14:59:38 -0000 On Sat, May 03, 2003 at 12:42:17PM +0200, Dirk-Willem van Gulik wrote: > > Not sure if I am chasing a FreeBSD problem or a deficiency in certain ATA > flash cards which lack, say sector 0, or something. > > On 5.0 release - on a soekris.com 4521. i had similar problems in the past with 4.7-based sources on a soekris 4501, and i tracked the problem to the bios returning an error when reading multiple sectors at once from the flash card. The same card works fine in a Lex System box and in a CF-ATA adapter on my desktop machine, so i don't know if the bios on the latter retries with single block reads or what. This is what i posted. The patch goes to /sys/boot/i386/boot2/boot1.s (it is inefficient because it always reads one sector at a time; at the time i believe i found a way to read the full track on the first attempt abd one sector on subsequent ones, but did not save the actual patch). hope this helps cheers luigi > From: Luigi Rizzo > To: soekris-tech@lists.soekris.com > Cc: small@freebsd.org > Bcc: Luigi Rizzo > Subject: summary and patch for CF problems in booting the 4501 > Message-ID: <20030218164802.A484@xorpc.icir.org> > > > A quick and dirty patch to fix the problem in the FreeBSD loader > (boot1) and the Etherboot loader (boot1a.bin) consists in forcing > the loader to load one sector at a time. Fortunately the code is > already structured to support something similar on crossing track > boundaries, so it suffices to replace the sequence: > > jb read.2 # this > movb %ah,%al # track > with the sequence > movb $1, %al > nop > nop > > right before the 'read.2' label. > The string to be replaced is \0162\02\0210\0340 > and the replacement is \0260\01\0220\0220 > > A binary patch is the following (the location of the code changes > in /boot/boot1 and /boot/boot1a.bin): > > ofs=328 # for boot1 > ofs=335 # for boot1a.bin > file="/boot/boot1a.bin" > > sh -c "echo -e '\0260\01\0220\0220'" | \ > dd of=${file} bs=1 count=4 oseek=${ofs} conv=notrunc > > I am not sure if this is a complete fix, i.e. there might be > other parts of the kernel which use the BIOS to access the > CF loading multiple sectors at once. > > cheers > luigi From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 10:05:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8B62D37B407 for ; Sat, 3 May 2003 10:05:51 -0700 (PDT) Received: from foem.leiden.webweaving.org (fia224-72.dsl.hccnet.nl [62.251.72.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E1243FBD for ; Sat, 3 May 2003 10:05:43 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: from foem (IDENT:chuckwebweaving.org@foem [10.11.0.2]) h43H5gOh002274; Sat, 3 May 2003 19:05:42 +0200 (CEST) (envelope-from dirkx@webweaving.org) Date: Sat, 3 May 2003 19:05:42 +0200 (CEST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@foem To: Luigi Rizzo In-Reply-To: <20030503075932.A10701@xorpc.icir.org> Message-ID: <20030503171007.H62023-100000@foem> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: techniek@WirelessLeiden.NL cc: freebsd-hackers@freebsd.org Subject: Re: CompactFlash / new GEOM / boot fails on certain brand / Soekris X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 17:05:51 -0000 Luigi, Wonderful; yes - the fix does indeed work around the issue - Mille Thanks for all the help. For completeness: At: http://webfolder.wleiden.webweaving.org/apacher-boot/ patch.txt patch for boot1.s on x86 Which is also used by boot2 (see xread refernence in boot2.s). However it also needs a fix in the BTX boot loader which gets called later by boot2: patch2.txt for i386/libi386/biosdisk.c What I did for now was set the 'maxfer=1' in the bd_read/bd_write after one error. I suppose that this does slow things down. Compiled versions to experiment: boot1.bin boot2.bin loader.bin But if I understand you right - this really is an issue in the bios of Soekris - and I should ping Soeren to help fix this ? I.e the BIOS should grafecully scale back to one sector at a time ? Or is the bios already out of the picture when we get to the loader/BTX stage - and should FreeBSD scale back to one sector/at/the/time after the first error ? Thanks a bundle ! Dw From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 10:15:59 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 35DDF37B401 for ; Sat, 3 May 2003 10:15:59 -0700 (PDT) Received: from smtpzilla1.xs4all.nl (smtpzilla1.xs4all.nl [194.109.127.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1660A43F75 for ; Sat, 3 May 2003 10:15:58 -0700 (PDT) (envelope-from wleiden@xs4all.nl) Received: from localhost.localdomain (zorknet.xs4all.nl [194.109.254.102]) by smtpzilla1.xs4all.nl (8.12.9/8.12.9) with ESMTP id h43HFtsA049253; Sat, 3 May 2003 19:15:56 +0200 (CEST) From: Marten To: tech In-Reply-To: <20030503171007.H62023-100000@foem> References: <20030503171007.H62023-100000@foem> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 03 May 2003 19:15:55 +0200 Message-Id: <1051982156.1245.2.camel@amd> Mime-Version: 1.0 cc: Luigi Rizzo cc: freebsd-hackers@freebsd.org Subject: Re: WLT: Re: CompactFlash / new GEOM / boot fails on certain brand / Soekris X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 17:15:59 -0000 On Sat, 2003-05-03 at 19:05, Dirk-Willem van Gulik wrote: > > Luigi, > > Wonderful; yes - the fix does indeed work around the issue - Mille Thanks > for all the help. > > For completeness: > > At: http://webfolder.wleiden.webweaving.org/apacher-boot/ this is the good one :) http://webfolder.wleiden.webweaving.org/apacer-flash/ Marten From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 13:49:45 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71F2E37B401 for ; Sat, 3 May 2003 13:49:45 -0700 (PDT) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id C690F43F3F for ; Sat, 3 May 2003 13:49:43 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b207.otenet.gr [212.205.244.215]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h43KndmX025914 for ; Sat, 3 May 2003 23:49:40 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h43KndoP004068 for ; Sat, 3 May 2003 23:49:39 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h43KncUl004067 for freebsd-hackers@freebsd.org; Sat, 3 May 2003 23:49:38 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 3 May 2003 23:49:38 +0300 From: Giorgos Keramidas To: freebsd-hackers@freebsd.org Message-ID: <20030503204938.GA3907@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: Periodic email about security notifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 20:49:45 -0000 Hi all, A friend asked me a while ago on IRC if it was possible to receive periodic email notifications with new security advisories. The following script for /etc/periodic/security implements exactly this idea. It depends on lynx(1) to run, which isn't part of the base system, so I'm not sure if it's ok to add it to the base system at all. Here it is for anyone who might find it useful though: : #!/bin/sh - : # : # Copyright (c) 2003 Giorgos Keramidas : # All rights reserved. : # : # Redistribution and use in source and binary forms, with or without : # modification, are permitted provided that the following conditions : # are met: : # 1. Redistributions of source code must retain the above copyright : # notice, this list of conditions and the following disclaimer. : # 2. Redistributions in binary form must reproduce the above copyright : # notice, this list of conditions and the following disclaimer in the : # documentation and/or other materials provided with the distribution. : # : # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND : # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE : # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE : # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE : # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL : # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS : # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) : # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT : # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY : # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF : # SUCH DAMAGE. : # : # $FreeBSD$ : # : : sa_url='ftp://ftp.jp.freebsd.org/pub/FreeBSD/CERT/advisories/' : : # If there is a global system configuration file, suck it in. : # : if [ -r /etc/defaults/periodic.conf ] : then : . /etc/defaults/periodic.conf : source_periodic_confs : fi : : . /etc/periodic/security/security.functions : : rc=0 : : case "$daily_status_security_advisory_enable" in : [Yy][Ee][Ss]) : echo "" : echo 'Checking for new security advisories or notifications:' : : lynx -dump ftp://ftp.jp.freebsd.org/pub/FreeBSD/CERT/advisories/ | \ : grep 'text/plain[[:space:]].*\]FreeBSD-S[AN]-' | sort | \ : sed -e 's/^.*]//' -e 's/ .*$//' -e 's|^| '"${sa_url}"'|' | \ : check_diff advisory - "${host} security advisories:" : rc=$? ;; : *) rc=0;; : esac : : exit $rc Just save it as /etc/periodic/security/999.advisory and then create two empty logfiles: # touch /var/log/advisory.today # touch /var/log/advisory.yesterday Enable it by setting daily_status_security_advisory_enable=yes in your /etc/periodic.conf file and have fun :-) - Giorgos From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 14:29:27 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5EB537B660 for ; Sat, 3 May 2003 14:29:26 -0700 (PDT) Received: from lakemtao01.cox.net (lakemtao01.cox.net [68.1.17.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id E09F043FB1 for ; Sat, 3 May 2003 14:29:25 -0700 (PDT) (envelope-from brian@shadowcom.net) Received: from shadowcom.net ([68.100.212.237]) by lakemtao01.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with SMTP id <20030503212925.MSQW8337.lakemtao01.cox.net@shadowcom.net> for ; Sat, 3 May 2003 17:29:25 -0400 Received: (qmail 22576 invoked by uid 500); 3 May 2003 21:29:55 -0000 Date: Sat, 3 May 2003 17:29:55 -0400 From: Brian Ledbetter To: Giorgos Keramidas Message-ID: <20030503212954.GC21307@shadowcom.net> References: <20030503204938.GA3907@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030503204938.GA3907@gothmog.gr> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org Subject: Re: Periodic email about security notifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 21:29:27 -0000 Giorgos, That looks really awesome! I think you may be able to accomplish this with /usr/bin/fetch (which _is_ a part of base), though. If you'd like, I can send you a patch to accomplish this. :) I plan on putting this on all of my computers! Excellent work, sir! -B On Sat, May 03, 2003 at 11:49:38PM +0300, Giorgos Keramidas wrote: > Hi all, > > A friend asked me a while ago on IRC if it was possible to receive > periodic email notifications with new security advisories. > > The following script for /etc/periodic/security implements exactly this > idea. It depends on lynx(1) to run, which isn't part of the base > system, so I'm not sure if it's ok to add it to the base system at all. > Here it is for anyone who might find it useful though: -- Brian Ledbetter http://www.shadowcom.net/brian/ From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 14:47:47 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0532437B401 for ; Sat, 3 May 2003 14:47:47 -0700 (PDT) Received: from lakemtao03.cox.net (lakemtao03.cox.net [68.1.17.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE9FE43F3F for ; Sat, 3 May 2003 14:47:44 -0700 (PDT) (envelope-from brian@shadowcom.net) Received: from shadowcom.net ([68.100.212.237]) by lakemtao03.cox.net (InterMail vM.5.01.04.05 201-253-122-122-105-20011231) with SMTP id <20030503214743.NTHY23518.lakemtao03.cox.net@shadowcom.net> for ; Sat, 3 May 2003 17:47:43 -0400 Received: (qmail 22890 invoked by uid 500); 3 May 2003 21:48:14 -0000 Date: Sat, 3 May 2003 17:48:14 -0400 From: Brian Ledbetter To: Giorgos Keramidas Message-ID: <20030503214814.GD21307@shadowcom.net> References: <20030503204938.GA3907@gothmog.gr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="bg08WKrSYDhXBjb5" Content-Disposition: inline In-Reply-To: <20030503204938.GA3907@gothmog.gr> User-Agent: Mutt/1.4i cc: freebsd-hackers@freebsd.org Subject: Re: Periodic email about security notifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 21:47:47 -0000 --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Ok, so /usr/bin/fetch isn't really suited for this, as I'm sure you knew already. My bad. Here is a patched version which will do the same thing with /usr/bin/ftp. I hope it works for you. (As a side note, in your code, you set $sa_url initially, but never use it later. I fixed that with this patch, too.) Regards! B On Sat, May 03, 2003 at 11:49:38PM +0300, Giorgos Keramidas wrote: > Hi all, > > A friend asked me a while ago on IRC if it was possible to receive > periodic email notifications with new security advisories. > > The following script for /etc/periodic/security implements exactly this > idea. It depends on lynx(1) to run, which isn't part of the base > system, so I'm not sure if it's ok to add it to the base system at all. > Here it is for anyone who might find it useful though: -- Brian Ledbetter http://www.shadowcom.net/brian/ --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="security-advisory.patch" --- 999.security-advisory.orig Sat May 3 17:47:05 2003 +++ 999.security-advisory Sat May 3 17:46:32 2003 @@ -27,7 +27,7 @@ # $FreeBSD$ # -sa_url='ftp://ftp.jp.freebsd.org/pub/FreeBSD/CERT/advisories/' +sa_url='ftp://ftp2.freebsd.org/pub/FreeBSD/CERT/advisories/' # If there is a global system configuration file, suck it in. # @@ -46,8 +46,8 @@ echo "" echo 'Checking for new security advisories or notifications:' - lynx -dump ftp://ftp.jp.freebsd.org/pub/FreeBSD/CERT/advisories/ | \ - grep 'text/plain[[:space:]].*\]FreeBSD-S[AN]-' | sort | \ + echo ls \*.asc | /usr/bin/ftp $sa_url 2>&1 | \ + grep 'FreeBSD-S[AN]-' | awk '{ print $9 }' | sort | \ sed -e 's/^.*]//' -e 's/ .*$//' -e 's|^| '"${sa_url}"'|' | \ check_diff advisory - "${host} security advisories:" rc=$? ;; --bg08WKrSYDhXBjb5-- From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 14:54:37 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3509937B4AE for ; Sat, 3 May 2003 14:54:36 -0700 (PDT) Received: from thalia.otenet.gr (thalia.otenet.gr [195.170.0.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4699A43FBD for ; Sat, 3 May 2003 14:54:34 -0700 (PDT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.gr (patr530-b207.otenet.gr [212.205.244.215]) by thalia.otenet.gr (8.12.9/8.12.9) with ESMTP id h43LsUmX019197; Sun, 4 May 2003 00:54:31 +0300 (EEST) Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.12.9/8.12.9) with ESMTP id h43LsUoP005569; Sun, 4 May 2003 00:54:30 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.gr (8.12.9/8.12.9/Submit) id h43LsUXY005568; Sun, 4 May 2003 00:54:30 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sun, 4 May 2003 00:54:30 +0300 From: Giorgos Keramidas To: Brian Ledbetter Message-ID: <20030503215430.GB5539@gothmog.gr> References: <20030503204938.GA3907@gothmog.gr> <20030503212954.GC21307@shadowcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030503212954.GC21307@shadowcom.net> cc: freebsd-hackers@freebsd.org Subject: Re: Periodic email about security notifications X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 May 2003 21:54:38 -0000 On 2003-05-03 17:29, Brian Ledbetter wrote: > Giorgos, > > That looks really awesome! I think you may be able to accomplish this > with /usr/bin/fetch (which _is_ a part of base), though. If you'd like, > I can send you a patch to accomplish this. :) fetch(1) doesn't work for listing directory files here. I am not sure it can do this at all, but if you make it work I'd appreciate any patches :-) From owner-freebsd-hackers@FreeBSD.ORG Sat May 3 17:50:57 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28C9937B401 for ; Sat, 3 May 2003 17:50:57 -0700 (PDT) Received: from HAL9000.homeunix.com (12-233-57-131.client.attbi.com [12.233.57.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F05143F93 for ; Sat, 3 May 2003 17:50:56 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.5) with ESMTP id h440otdN000855; Sat, 3 May 2003 17:50:55 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.5/Submit) id h440otAY000854; Sat, 3 May 2003 17:50:55 -0700 (PDT) (envelope-from das@FreeBSD.ORG) Date: Sat, 3 May 2003 17:50:55 -0700 From: David Schultz To: drew@PoohSticks.ORG Message-ID: <20030504005055.GA789@HAL9000.homeunix.com> Mail-Followup-To: drew@PoohSticks.ORG, freebsd-hackers@freebsd.org References: <200304252247.h3PMlpd17574@revolt.poohsticks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200304252247.h3PMlpd17574@revolt.poohsticks.org> cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Problems with AIO? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 May 2003 00:50:57 -0000 On Fri, Apr 25, 2003, drew@PoohSticks.ORG wrote: > I have a program which needs to do multiple non-blocking disk I/Os > in parallel on raw devices, have been using pthreads with wrappers that > provide a single-threaded event driven interface, and am in the process of > switching to AIO to get rid of some debugger/pthread interactions > and make some Windows guys happy because AIO looks more like their > async IO interface. > > So, I look in the LINT config file and see this: > # Use real implementations of the aio_* system calls. There are numerous > # stability issues in the current aio code that make it unsuitable for > # inclusion on shell boxes. > options VFS_AIO > When I query GNATs for AIO in the single-line text fields, I get just this > > 2002/01/17] kern/34017 The siginfo_t passed to the signal handling routine is not filled out for AIO > > and a web search only turns up this exploit > > http://www.securiteam.com/exploits/6L00E0A3FC.html Of these bugs, I believe the first one still exists, and the second was eliminated long ago in -CURRENT. (You may wish to try the posted exploit to confirm this.) I don't know what other problems might exist, but realize that this feature is not heavily utilized and therefore tested by the FreeBSD user base. That said, it works for me. Perhaps people would use it more and work all the bugs out right away if we removed the ``beware of dog'' sign and a while later enabled it by default.