From owner-freebsd-hackers@FreeBSD.ORG Sun Sep 23 15:54:13 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 002E516A419 for ; Sun, 23 Sep 2007 15:54:12 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.174]) by mx1.freebsd.org (Postfix) with ESMTP id 6967813C448 for ; Sun, 23 Sep 2007 15:54:12 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so832175ugf for ; Sun, 23 Sep 2007 08:54:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:received:received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; bh=BO+spTJN4+gfrdmg76Uz7Y3zj7bNvQwKvKUNuDLiUv4=; b=QrpJty2BYSqAdBrJlFBOAXyCLfjnIg6Yj7BWdlMP9te9ngLaKTHX9cQgr4Mky3qv6iK4JH8fbSuozhEELyJcfYOMEWJHgHobBKspoRN9q4MXrYcg22LVzmCGayOUb/JQYg4zI9JgrALXxVQsY8OyXk1idsjMMs6ZhPGpDol5PQc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:date:from:to:cc:subject:message-id:mail-followup-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=BcfrMzT4DRmRNv/YFxQZkV2h5SaNGQ1UJtPAbxtdBJb9xuBqRdojUzH+LNGXmCFr7P6d1ONrdiMVExM2xxbgn6bt0QvbXxThcT6s05RNg4j32NIeASjcM4vZx0LiMqFRMkgCu/1j990LPHzEUlQLmp8cWd8eAlEEgE6WiMjxl+U= Received: by 10.67.22.14 with SMTP id z14mr6772475ugi.1190561351847; Sun, 23 Sep 2007 08:29:11 -0700 (PDT) Received: from roadrunner.spoerlein.net ( [85.180.157.142]) by mx.google.com with ESMTPS id k28sm6508660ugd.2007.09.23.08.29.10 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 23 Sep 2007 08:29:11 -0700 (PDT) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.1/8.14.1) with ESMTP id l8NFT8XA092728; Sun, 23 Sep 2007 17:29:08 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Received: (from q@localhost) by roadrunner.spoerlein.net (8.14.1/8.14.1/Submit) id l8NFJHhU092607; Sun, 23 Sep 2007 17:19:17 +0200 (CEST) (envelope-from uspoerlein@gmail.com) Date: Sun, 23 Sep 2007 17:19:17 +0200 From: Ulrich Spoerlein To: Matthias Fechner Message-ID: <20070923151916.GB1444@roadrunner.spoerlein.net> Mail-Followup-To: Matthias Fechner , freebsd-hackers@freebsd.org References: <46F22228.5070203@fechner.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F22228.5070203@fechner.net> User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-hackers@freebsd.org Subject: Re: Own Install CD with custom kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Sep 2007 15:54:13 -0000 On Thu, 20.09.2007 at 09:32:56 +0200, Matthias Fechner wrote: > It seems that sysinstall will not install per default the new kernel. > For a non SMP system (like mine) it is I4B. > So it seems to me that I must change /usr/src/usr.sbin/sysinstall to > do this. I attached a patch to this email which should do it. > > [...] > > I checked now the the installed system and there is absolutly no kernel > installed. (no /boot/GENERIC, no /boot/I4B or anything else) > > I'm sure that I must oversaw something in sysinstall to change but I > cannot find it. > Can please anyone provide with some help? Hi, we need to install multiple kernels per system and instead of relying on sysinstall (I couldn't figure out, how to install multiple kernels with it, especially since it wants to install the default kernel to 'kernel') I hacked up my own kernel installation I'm using a Makefile to drive our release and package building and for the releases I'm using an install.cfg, which gets created on the fly, since the names of the kernels change now and then, here is the release target KERNELS= SERVER GENERIC SMP release rerelease: # Write automation script for sysinstall rm -f ${TLR}/usr/src/release/.install.cfg for k in ${KERNELS}; do printf "%s\n%s\n" "command=/bin/sh -c \"cd /dist/${RELEASE}/kernels && ./install.sh $$k\"" "system" \ >> ${TLR}/usr/src/release/.install.cfg; done sed '/^#KERNELS#/r ${TLR}/usr/src/release/.install.cfg' files/install.cfg > ${TLR}/usr/src/release/install.cfg cp files/src.diff ${TLR}/usr/src/release/src.diff # Create a src patch for our kernels on the fly, so we can pass it to make release (for i in ${KERNELS}; do diff -u /dev/null kernels/$$i 2>/dev/null || true; done) | sed 's,kernels/,sys/i386/conf/,' \ > ${TLR}/usr/src/release/kernels.diff # Copy them over again for rerelease, perhaps something changed .if make(rerelease) .for k in ${KERNELS} -cp kernels/$k ${TRR}/usr/src/sys/i386/conf/ .endfor .endif cd ${TLR}/usr/src/release && make ${.TARGET} \ BUILDNAME=${RELEASE} \ CHROOTDIR=${TRR} \ WORLD_FLAGS="-j4 \ MODULES_WITH_WORLD=yes \ WITHOUT_MODULES='3dfx 3dfx_linux ath ath_hal ath_rate_amrr ath_rate_onoe ath_rate_sample aue\ bktr cardbus coda coda5 dcons dcons_crom fatm firewire firmware harp hatm \ if_ndis ip6fw ipw iwi joy kue ndis pccard ral splash syscons umodem ural urio\ uscanner utopia uvisor wi wlan wlan_acl wlan_ccmp wlan_tkip wlan_wep wlan_xauth'" \ KERNEL_FLAGS="-j4 MODULES_WITH_WORLD=yes" \ KERNELS_BASE=''\ NODOC=YES NOPORTS=YES NOSRC=YES NO_FLOPPIES=YES \ RELEASENOUPDATE=YES \ LOCAL_PATCHES='src.diff kernels.diff' \ KERNELS='${KERNELS}' \ CVSROOT=${CVSROOT} \ CVSCMDARGS='${SRCDATE}' \ RELEASETAG=${SRCBRANCH} cd ${TRR}/R/ftp && find -d . | cpio --quiet -dumpl ${TFR} And files/install.cfg contains the following debug=yes mediaSetCDROM # Select which distributions we want. We omit the kernels here, we do them by hand dists= base doc manpages games catpages dict info distSetCustom # Partition Editor diskInteractive=YES bootManager=standard diskPartitionEditor diskLabelEditor installCommit # Magic marker, don't edit! Is set automatically from the Makefile! #KERNELS# # End of magic marker So basically, sysinstall is intructed to not install any kernel, but after all distributions are extracted the following commands are run command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh GENERIC" system command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh SMP" system It has the nice side effekt of GENERIC and SMP landing in /boot/{GENERIC,SMP} We also ship a /boot/loader.conf that sets the correct kernel to boot and is versioned and centrally controlled, yadda yadda yadda hth, Ulrich Spoerlein -- It is better to remain silent and be thought a fool, than to speak, and remove all doubt. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 21 22:50:49 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7538616A46B for ; Fri, 21 Sep 2007 22:50:49 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.235]) by mx1.freebsd.org (Postfix) with ESMTP id 3EB0E13C45D for ; Fri, 21 Sep 2007 22:50:49 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by nz-out-0506.google.com with SMTP id l8so723836nzf for ; Fri, 21 Sep 2007 15:50:48 -0700 (PDT) Received: by 10.114.73.1 with SMTP id v1mr4094949waa.1190413593375; Fri, 21 Sep 2007 15:26:33 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Fri, 21 Sep 2007 15:26:33 -0700 (PDT) Message-ID: Date: Fri, 21 Sep 2007 18:26:33 -0400 From: "Benjie Chen" To: freebsd-hardware@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 X-Mailman-Approved-At: Mon, 24 Sep 2007 08:25:07 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Sep 2007 22:50:49 -0000 Hi FreeBSD hackers and engineers, I am experiencing a kernel panic that comes on when my new PowerEdge 1950 FreeBSD 6.2 setup is under a certain stress load. I've emailed a few people on the list who have given me useful comments, some of which I am still following up. But I wanted to send a general cry for help to see if there are more knowledge out there about this problem. FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver (PERC5i). 4GB RAM. I am currently running i386, and not amd64, due to various reasons. I've ran exhaustively memory tests, disk tests, and network tests and cannot produce the kernel panic. I worked with Dell support to run memory test 1 DIMM at a time and cannot find any problem. With 1 DIMM at a time, I could still get the kernel panic under my work load. My work load is heavily hitting a web site running on the machine and requiring the web service to do MySQL requests. On the side, I am running a bunch of scripts that mostly read from the MySQL database but also write to it occasionally. Not memory intensive -- still have usually about 1GB free memory, but fairly disk intensive. I don't get disk errors. Anywhere from between 10 minutes to 4 or 5 hours into the test, I get the kernel panic. Again, still no disk errors. I turned off soft-update, still happens. Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin c066c7b4 T _mtx_lock_spin c066c85c T _mtx_unlock_sleep So this could mean that independent stress tests will not result in panic if there aren't enough concurrency to cause the problem. There are a few other complaints about kernel panics at the same IP on the web (google 0xc066c731)... I was wondering if anyone had dealt with this before and if there are any work arounds? Thanks, Benjie From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 22 06:52:18 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 506EB16A417 for ; Sat, 22 Sep 2007 06:52:18 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id A48AD13C455 for ; Sat, 22 Sep 2007 06:52:17 +0000 (UTC) (envelope-from eugen@www.svzserv.kemerovo.su) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id l8M6P147029721 for ; Sat, 22 Sep 2007 14:25:01 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id l8M6P1ZI029720 for freebsd-hackers@freebsd.org; Sat, 22 Sep 2007 14:25:01 +0800 (KRAST) (envelope-from eugen) Date: Sat, 22 Sep 2007 14:25:01 +0800 From: Eugene Grosbein To: freebsd-hackers@freebsd.org Message-ID: <20070922062501.GA26284@svzserv.kemerovo.su> References: <20070921161917.GA65081@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070921161917.GA65081@eos.sc1.parodius.com> User-Agent: Mutt/1.4.2.3i X-Mailman-Approved-At: Mon, 24 Sep 2007 08:25:07 +0000 Subject: Re: Serial console/remote install discussion X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Sep 2007 06:52:18 -0000 On Fri, Sep 21, 2007 at 09:19:17AM -0700, Jeremy Chadwick wrote: > I'd like to open up a discussion regarding FreeBSD serial console and > the aspect of installation via serial console. > > There seem to be quite a few surprises in regards to installing (or even > using!) FreeBSD this way. I thought I'd mention some of them, in hopes > that by bringing them to light we can work towards making the > installation process easier, or at least more headless-friendly. > > 1) Administrators are required to "build their own installation disks" > (the Handbook goes over this with regards to floppy disks) if they want > FreeBSD installs to support serial console. Based on what I've read, > the procedure is required because the stock installation disks lack a > /boot.config that contains -h. > > Has anyone ever proposed including a /boot.config on all the > installation mediums that contains -P by default? I don't know how > reliable -P is, but I've used it for years on numerous servers (all > different hardware) without any issues; others may have different > experiences. See also: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/58951 > Which brings me to the next item... > > 2) FreeBSD's serial vs. VGA concept (keyword: versus) is disheartening. > The whole "one or the other" concept is unrealistic in this day and age, > and this was more or less admitted by the Dragonfly folks when they > re-wrote whatever code to get simultaneous dual console (VGA+serial) > working. This seems to be wrong: FreeBSD has dual console support for quite long time. Eugene Grosbein From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 08:49:00 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57A5F16A420 for ; Mon, 24 Sep 2007 08:49:00 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id 0721913C465 for ; Mon, 24 Sep 2007 08:49:00 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by proxypop1.sarenet.es (Postfix) with ESMTP id 73EF55CC5; Mon, 24 Sep 2007 10:48:58 +0200 (CEST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Mon, 24 Sep 2007 10:48:57 +0200 To: "Benjie Chen" X-Mailer: Apple Mail (2.752.2) Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 08:49:00 -0000 On 22 Sep 2007, at 00:26, Benjie Chen wrote: > FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver > (PERC5i). 4GB > RAM. I am currently running i386, and not amd64, due to various > reasons. > > Kernel panic is at 0xC066C731, which from nm shows it's in > mtx_lock_spin > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep > > So this could mean that independent stress tests will not result in > panic if > there aren't enough concurrency to cause the problem. I don't have the exact IP address involved, but we experienced consistent panics in two heavily loaded mail servers (same hardware models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. Suspecting an issue with the IP stack and smp I tried to set "debug.mpsafenet=0" and the problems are gone. Of course I've lost some performance, but the systems have been solid for some weeks so far. Borja. ---------------- "The thing he realised about the windows was this: because they had been converted into openable windows after they had first been designed to be impregnable, they were, in fact, much less secure than if they had been designed as openable windows in the first place." Douglas Adams, "Mostly Harmless" From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 09:28:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0792E16A417 for ; Mon, 24 Sep 2007 09:28:44 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 6C55A13C467 for ; Mon, 24 Sep 2007 09:28:43 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1123249nfb for ; Mon, 24 Sep 2007 02:28:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=n1ojkXU90LreeGxePPeEenoGHNSAj6YQWpzVMJ+5isM=; b=m8Asc7YZipIGYwUgAQxZ/Hx3tYsfc5YZkdRirkkkUnxLZTLxeIxGExHEKUcRG7ZaVzY0RDTyQdIX/PsAASUsFdPK4p8BI84CHL+OGluB5+LKtbs6fNLBIBXrI90eMJUOIOyywFqFXquiZVKAl134idowGyOJeJFWdDhNsx+ZT6U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=nig+sAVh0cu6hKK9XphjYXLXt2L789+xpgDg/DaQSmm4me3fLXxslvSsiZqna0rUKYaRexHraFNbH+hHxi+7I8ODxHRvLccU+8IWzv/qErMUNwFcK4LAOxeLZ18CxT2IrBY7m0fWPPF6TiSaTnyO1kZSzben4LgDO/rh2FbsG+s= Received: by 10.86.100.7 with SMTP id x7mr4572276fgb.1190626122217; Mon, 24 Sep 2007 02:28:42 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id 22sm9899463fkr.2007.09.24.02.28.40 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Sep 2007 02:28:41 -0700 (PDT) Message-ID: <46F78343.6060809@gmail.com> Date: Mon, 24 Sep 2007 13:28:35 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: linuxolator problem on i386 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:28:44 -0000 Hi # su hlds -c "ktrace -i ./hlds_run -game cstrike +ip 0.0.0.0 +port 27015 +map de_dust -debug" Auto detecting CPU Using Pentium II Optimised binary. Enabling debug mode Auto-restarting the server on crash Console initialized. scandir failed:/usr/home/hlds/1.6/./platform/SAVE Protocol version 47 Exe version 1.1.2.5/Stdio (cstrike) Exe build: 20:02:49 Oct 24 2006 (3651) STEAM Auth Server couldn't exec language.cfg Server IP address 0.0.0.0:27015 scandir failed:/usr/home/hlds/1.6/./platform/SAVE *** glibc detected *** ./hlds_i686: double free or corruption (!prev): 0x08da3738 *** ======= Backtrace: ========= /lib/libc.so.6[0x2811ac88] /lib/libc.so.6(cfree+0x90)[0x2811e230] /lib/libc.so.6(closedir+0x28)[0x2813ecf8] /lib/libc.so.6(scandir+0x14b)[0x2813f21b] /usr/home/hlds/1.6/filesystem_stdio_i386.so(findFileInDirCaseInsensitive__FPCc+0xe4)[0x28af41d8] /usr/home/hlds/1.6/filesystem_stdio_i386.so(FS_stat__17CFileSystem_StdioPCcP4stat+0x40)[0x28af861c] /usr/home/hlds/1.6/filesystem_stdio_i386.so(FastFindFileSize__15CBaseFileSystemPCQ215CBaseFileSystem11CSearchPathPCc+0x17e)[0x28af572a] /usr/home/hlds/1.6/filesystem_stdio_i386.so(Size__15CBaseFileSystemPCc+0x5b)[0x28af557b] /usr/home/hlds/1.6/engine_i686.so(FS_FileSize+0x2a)[0x2828679e] ======= Memory map: ======== 08048000-08054000 r-xp 0003a000 00:00 1931338 /usr/home/hlds/1.6/hlds_i686 08054000-0805b000 rw-p 0003a000 00:00 1931338 /usr/home/hlds/1.6/hlds_i686 0805b000-0805e000 rw-p 00d60000 00:00 0 0805e000-08dbb000 rwxp 00d60000 00:00 0 28054000-2806d000 r-xp 0001e000 00:00 1719480 /usr/compat/linux/lib/ld-2.5.so 2806d000-2806e000 r-xp 0001e000 00:00 1719480 /usr/compat/linux/lib/ld-2.5.so 2806e000-2806f000 rw-p 00002000 00:00 0 2806f000-28070000 rwxp 00002000 00:00 0 28071000-28073000 r-xp 00004000 00:00 1719493 /usr/compat/linux/lib/libdl-2.5.so 28073000-28074000 r-xp 00004000 00:00 1719493 /usr/compat/linux/lib/libdl-2.5.so 28074000-28075000 rwxp 00004000 00:00 1719493 /usr/compat/linux/lib/libdl-2.5.so 28075000-28076000 rwxp 00001000 00:00 0 28076000-28088000 r-xp 0001e000 00:00 1719511 /usr/compat/linux/lib/libpthread-2.5.so 28088000-28089000 r-xp 0001e000 00:00 1719511 /usr/compat/linux/lib/libpthread-2.5.so 28089000-2808a000 rwxp 0001e000 00:00 1719511 /usr/compat/linuxAbort trap (core dumped) debug.cmds:1: Error in sourced command file: Previous frame inner to this frame (corrupt stack?) email debug.log to linux at valvesoftware.com Wed Sep 12 20:27:04 SAMST 2007: Server restart in 10 seconds Wed Sep 12 20:27:06 SAMST 2007: Server Quit # =================================================== # uname -a FreeBSD damask 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Sep 12 17:04:55 SAMST 2007 root at cs.udmvt.ru :/usr/obj/usr/src/sys/CS2 i386 # sysctl compat compat.linux.oss_version: 198144 compat.linux.osrelease: 2.6.16 compat.linux.osname: Linux # kldstat Id Refs Address Size Name 1 14 0xc0400000 3e6ee0 kernel 2 1 0xc07e7000 69514 acpi.ko 3 1 0xc3ddd000 7000 linprocfs.ko 4 2 0xc3de4000 21000 linux.ko 5 1 0xc3e0e000 3000 linsysfs.ko # mount|grep linux linprocfs on /usr/compat/linux/proc (linprocfs, local) linsysfs on /usr/compat/linux/sys (linsysfs, local) # pkg_info | grep linux linux_base-fc6-6_3 Base set of packages needed in Linux mode (for i386/amd64) [private links to debug.log & ktrace.out] please send me message after downloaded this files (for removing) /Vladimir Ermakov cross-posting: http://lists.freebsd.org/pipermail/freebsd-emulation/2007-September/003960.html From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 09:33:15 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4598E16A419 for ; Mon, 24 Sep 2007 09:33:15 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 3F91613C448; Mon, 24 Sep 2007 09:33:12 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F78459.4060607@FreeBSD.org> Date: Mon, 24 Sep 2007 11:33:13 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Borja Marcos References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Benjie Chen Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:33:15 -0000 Borja Marcos wrote: > > On 22 Sep 2007, at 00:26, Benjie Chen wrote: > >> FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver (PERC5i). 4GB >> RAM. I am currently running i386, and not amd64, due to various reasons. >> >> Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin >> c066c7b4 T _mtx_lock_spin >> c066c85c T _mtx_unlock_sleep >> >> So this could mean that independent stress tests will not result in >> panic if >> there aren't enough concurrency to cause the problem. > > I don't have the exact IP address involved, but we experienced > consistent panics in two heavily loaded mail servers (same hardware > models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. > > Suspecting an issue with the IP stack and smp I tried to set > "debug.mpsafenet=0" and the problems are gone. Of course I've lost some > performance, but the systems have been solid for some weeks so far. What number is the PR with the details? Kris From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 09:35:30 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB4116A421; Mon, 24 Sep 2007 09:35:30 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 3B1E313C458; Mon, 24 Sep 2007 09:35:29 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F784E1.1080000@FreeBSD.org> Date: Mon, 24 Sep 2007 11:35:29 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Benjie Chen References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:35:30 -0000 Benjie Chen wrote: > Hi FreeBSD hackers and engineers, > > I am experiencing a kernel panic that comes on when my new PowerEdge 1950 > FreeBSD 6.2 setup is under a certain stress load. I've emailed a few people > on the list who have given me useful comments, some of which I am still > following up. But I wanted to send a general cry for help to see if there > are more knowledge out there about this problem. > > FreeBSD 6.2 on PowerEdge 1950, RAID1 setup with mfi driver (PERC5i). 4GB > RAM. I am currently running i386, and not amd64, due to various reasons. > > I've ran exhaustively memory tests, disk tests, and network tests and cannot > produce the kernel panic. I worked with Dell support to run memory test 1 > DIMM at a time and cannot find any problem. With 1 DIMM at a time, I could > still get the kernel panic under my work load. > > My work load is heavily hitting a web site running on the machine and > requiring the web service to do MySQL requests. On the side, I am running a > bunch of scripts that mostly read from the MySQL database but also write to > it occasionally. Not memory intensive -- still have usually about 1GB free > memory, but fairly disk intensive. I don't get disk errors. Anywhere from > between 10 minutes to 4 or 5 hours into the test, I get the kernel panic. > Again, still no disk errors. I turned off soft-update, still happens. > > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep > > So this could mean that independent stress tests will not result in panic if > there aren't enough concurrency to cause the problem. > > There are a few other complaints about kernel panics at the same IP on the > web (google 0xc066c731)... I was wondering if anyone had dealt with this > before and if there are any work arounds? The IP is meaningless, it changes each time you compile your kernel. Unfortunately even knowing that it is in that symbol is nearly meaningless, because it doesn't provide enough information (only that your panic involved a spin mutex somehow). Please read the chapter on kernel debugging in the developers handbook and file a PR containing enough information for a developer to investigate the problem. Kris From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 09:39:32 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06ACB16A421; Mon, 24 Sep 2007 09:39:32 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from proxypop1.sarenet.es (proxypop1.sarenet.es [194.30.0.99]) by mx1.freebsd.org (Postfix) with ESMTP id AAFBF13C46A; Mon, 24 Sep 2007 09:39:31 +0000 (UTC) (envelope-from BORJAMAR@SARENET.ES) Received: from [127.0.0.1] (matahari.sarenet.es [192.148.167.18]) by proxypop1.sarenet.es (Postfix) with ESMTP id B56EE5CE0; Mon, 24 Sep 2007 11:39:30 +0200 (CEST) In-Reply-To: <46F78459.4060607@FreeBSD.org> References: <46F78459.4060607@FreeBSD.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Borja Marcos Date: Mon, 24 Sep 2007 11:39:30 +0200 To: Kris Kennaway X-Mailer: Apple Mail (2.752.2) Cc: freebsd-hackers@freebsd.org, Benjie Chen Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 09:39:32 -0000 On 24 Sep 2007, at 11:33, Kris Kennaway wrote: > Borja Marcos wrote: >> I don't have the exact IP address involved, but we experienced >> consistent panics in two heavily loaded mail servers (same >> hardware models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. >> Suspecting an issue with the IP stack and smp I tried to set >> "debug.mpsafenet=0" and the problems are gone. Of course I've lost >> some performance, but the systems have been solid for some weeks >> so far. > > What number is the PR with the details? Sorry, I couldn't diagnose anything properly. When it happened the sysadmin didn't give me the panic details, and being production machines the main priority was to put them back into service as soon as possible. Would it be a good idea to file a PR with such fuzzy information? I don't think so, that's why I didn't do it. Of course I can do it if someone thinks it's worth. But unfortunately I cannot get more precise details. Borja. ---------------- "The thing he realised about the windows was this: because they had been converted into openable windows after they had first been designed to be impregnable, they were, in fact, much less secure than if they had been designed as openable windows in the first place." Douglas Adams, "Mostly Harmless" From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 10:05:37 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8457C16A41A for ; Mon, 24 Sep 2007 10:05:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 6F91513C448; Mon, 24 Sep 2007 10:05:35 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F78BEF.4070406@FreeBSD.org> Date: Mon, 24 Sep 2007 12:05:35 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Borja Marcos References: <46F78459.4060607@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Benjie Chen Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:05:37 -0000 Borja Marcos wrote: > > On 24 Sep 2007, at 11:33, Kris Kennaway wrote: > >> Borja Marcos wrote: >>> I don't have the exact IP address involved, but we experienced >>> consistent panics in two heavily loaded mail servers (same hardware >>> models, Dell Powereedge) runnning Postfix and FreeBSD 6.2. >>> Suspecting an issue with the IP stack and smp I tried to set >>> "debug.mpsafenet=0" and the problems are gone. Of course I've lost >>> some performance, but the systems have been solid for some weeks so far. >> >> What number is the PR with the details? > > Sorry, I couldn't diagnose anything properly. When it happened the > sysadmin didn't give me the panic details, and being production machines > the main priority was to put them back into service as soon as possible. > > Would it be a good idea to file a PR with such fuzzy information? I > don't think so, that's why I didn't do it. Of course I can do it if > someone thinks it's worth. But unfortunately I cannot get more precise > details. No it isn't. You will need to do some more work to obtain this information, otherwise your bug will probably not be fixed. debug.mpsafenet=0 is no longer an option in 7.0, so you will have to deal with this sooner or later. Kris From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 10:51:20 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A29A16A417 for ; Mon, 24 Sep 2007 10:51:20 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id A5D6213C459 for ; Mon, 24 Sep 2007 10:51:19 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IZlX2-0000MX-Hm for freebsd-hackers@freebsd.org; Mon, 24 Sep 2007 10:51:16 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 10:51:16 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 Sep 2007 10:51:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Mon, 24 Sep 2007 12:50:54 +0200 Lines: 38 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enigD1A7E375A316CC6D39AE1BFB" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.12 (X11/20060911) In-Reply-To: X-Enigmail-Version: 0.94.4.0 Sender: news Cc: freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 10:51:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigD1A7E375A316CC6D39AE1BFB Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Benjie Chen wrote: > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spi= n > c066c7b4 T _mtx_lock_spin > c066c85c T _mtx_unlock_sleep >=20 > So this could mean that independent stress tests will not result in pan= ic if > there aren't enough concurrency to cause the problem. When you get a kernelbacktrace, see if it's the same as the one=20 mentioned here: http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.= html --------------enigD1A7E375A316CC6D39AE1BFB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG95aPldnAQVacBcgRAwHVAJ9wHslgdVRAY0/2fNb4CKq3o9S+ywCgy2qi 0b6j5dYUJplPbWuBHunb7vY= =er0K -----END PGP SIGNATURE----- --------------enigD1A7E375A316CC6D39AE1BFB-- From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 14:43:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DDDBF16A41B for ; Mon, 24 Sep 2007 14:43:44 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7DE2313C46E for ; Mon, 24 Sep 2007 14:43:44 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1190210nfb for ; Mon, 24 Sep 2007 07:43:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=7FDFP7iqlg2z3juoVE6GiS7BewaPgl1l82rdThg6QuE=; b=iK0Id5mYwYvucMEcXxvx1giUAVk0ClXWGLLo0FTx3QJY0i/sTEgilrNQV/vN2FyxbLhHdCoThDpiwDrV6BhfR2jDXL+vGFqy2ww/LaSjiaIWBgmbdq5YbVXw7Kz6sfO3WZcNbjagdsLZ1YRDuavFHy1f9qOzgzYBtqsG5hE6/s8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=Qlgo1wMzGxORsqbE3JMT3yCkicMMxty6iQSZkwqZpYGW+DG5VnPaNj9W5HKuHD9S4hORHHrughGYX1pNX1MeOKX8cnGgW3anQcn6tGmo6nPdfqhWhUhRg1kUYZxl8k71mjW14I97vDZuuVT44xPaKxnaKogU9saVYGtCR4GzWAA= Received: by 10.86.65.11 with SMTP id n11mr4792486fga.1190645022728; Mon, 24 Sep 2007 07:43:42 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id p9sm10595280fkb.2007.09.24.07.43.40 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Sep 2007 07:43:41 -0700 (PDT) Message-ID: <46F7CCF8.5010402@gmail.com> Date: Mon, 24 Sep 2007 18:43:04 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 14:43:45 -0000 hi, all http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html my problem # fsck /dev/aacd0s1f ** /dev/aacd0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes fsck_ufs: cannot alloc 2378019004 bytes for inoinfo # cat /boot/loader.conf kern.maxdsiz="1073741824" # 1GB kern.dfldsiz="1073741824" # 1GB kern.maxssiz="134217728" # 128MB # uname -rms FreeBSD 6.2-STABLE amd64 # limits Resource limits (current): cputime infinity secs filesize infinity kB datasize 1048576 kB stacksize 131072 kB coredumpsize infinity kB memoryuse infinity kB memorylocked infinity kB maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kB # dmesg|less Copyright (c) 1992-2007 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 6.2-STABLE #4: Wed Sep 19 13:56:13 MSD 2007 root@localhost:/usr/obj/usr/src/sys/STONE Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2191.66-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10 Features=0x78bfbff AMD Features=0xe0500800 real memory = 2147418112 (2047 MB) avail memory = 2066296832 (1970 MB) ACPI APIC Table: any solutions ? /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 17:18:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0013D16A46E for ; Mon, 24 Sep 2007 17:18:23 +0000 (UTC) (envelope-from kkuehl@cisco.com) Received: from sj-iport-3.cisco.com (sj-iport-3-in.cisco.com [171.71.176.72]) by mx1.freebsd.org (Postfix) with ESMTP id E0C6F13C49D for ; Mon, 24 Sep 2007 17:18:23 +0000 (UTC) (envelope-from kkuehl@cisco.com) X-IronPort-AV: E=Sophos;i="4.20,292,1186383600"; d="scan'208";a="527449215" Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 24 Sep 2007 10:18:23 -0700 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id l8OHINo5032430 for ; Mon, 24 Sep 2007 10:18:23 -0700 Received: from kkuehl-lnx.local ([10.25.80.154]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id l8OHILin027171 for ; Mon, 24 Sep 2007 17:18:23 GMT From: Kirby Kuehl Organization: Cisco Systems, Inc. To: freebsd-hackers@freebsd.org User-Agent: KMail/1.9.6 MIME-Version: 1.0 Content-Disposition: inline Date: Mon, 24 Sep 2007 12:18:15 -0500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200709241218.15814.kkuehl@cisco.com> DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1243; t=1190654303; x=1191518303; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=kkuehl@cisco.com; z=From:=20Kirby=20Kuehl=20 |Subject:=20Intel=20D975XBX2=20BTX=20halted |Sender:=20; bh=4MTLbj5ca1uuatbZIfUG77Aar2PxZxr+cG81NBL4CLE=; b=duvQUbDfWny/DyYj8eT3CD1IDTKoroFbTxkcMFCPoKeefAa53Jh6srDJ8xmHQYj3jFNWvEB7 HxdIRvk/N974fSZfDuqiTuoKWzbPtyoRT9bHyZp4v8ldoCMMgCyGo9Ru; Authentication-Results: sj-dkim-2; header.From=kkuehl@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; ); Subject: Intel D975XBX2 BTX halted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 17:18:24 -0000 After experiencing overheating problems, I purchased a new CPU and motherbo= ard=20 (Intel D975XBX2)=A0which has a built in Raid controller Marvell 88SE61xx I connected my existing FreeBSD-STABLE SATA drive to port 0. Upon boot, I receive the following error: int=3D0000000d err=3D00000000 efl=3D00030086 eip=3D00001526 eax=3D00000110 ebx=3D0000ffff ecx=3Dffffffff edx=3D95200110 esi=3D00003684 edi=3D000036ac ebp=3D00004eac esp=3D00004e9a cs=3Dcf00 ds=3D9b00 es=3Dcf00 fs=3D9941 gs=3D9ac0 ss=3D9b00 sc:eip=3D2e 0f 01 16 8d 07 0f 20-c0 40 0f 22 c0 b8 08 00 8e e8 67 66 65 89 0a 0f-20 c0 48 0f 22 c0 66 58 ss:esp=3D10 01 00 00 c0 9a 20 95-00 00 ff ff 00 00 ac 36 84 36 d4 4e 6c 32 00 01-00 00 00 40 25 00 00 00 BTX halted I have tried disabling the secondary SATA Controller, but it says no boot=20 devices available. I have tried configuring my ATA/IDE Mode as Native (the default) and Legacy. I have tried configuring SATA as IDE, AHCI, and RAID I have tried S.M.A.R.T both enabled and disabled. Similar Posts: http://lists.freebsd.org/pipermail/freebsd-questions/2007-March/146146.html http://lists.freebsd.org/pipermail/freebsd-questions/2007-March/146252.html Thanks in advance, Kirby From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 18:22:35 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6285016A418 for ; Mon, 24 Sep 2007 18:22:35 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb7:ef56]) by mx1.freebsd.org (Postfix) with ESMTP id 9D63913C468 for ; Mon, 24 Sep 2007 18:22:34 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id l8OIMPxW027437; Mon, 24 Sep 2007 20:22:26 +0200 From: Pieter de Goeje To: freebsd-hackers@freebsd.org Date: Mon, 24 Sep 2007 20:22:25 +0200 User-Agent: KMail/1.9.7 References: <46F78343.6060809@gmail.com> In-Reply-To: <46F78343.6060809@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709242022.25624.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: sam Subject: Re: linuxolator problem on i386 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 18:22:35 -0000 On Monday 24 September 2007, sam wrote: > Hi > > # su hlds -c "ktrace -i ./hlds_run -game cstrike +ip 0.0.0.0 +port 27015 > +map de_dust -debug" > Auto detecting CPU > Using Pentium II Optimised binary. > Enabling debug mode > Auto-restarting the server on crash > > Console initialized. > scandir failed:/usr/home/hlds/1.6/./platform/SAVE > Protocol version 47 > Exe version 1.1.2.5/Stdio (cstrike) > Exe build: 20:02:49 Oct 24 2006 (3651) > STEAM Auth Server > couldn't exec language.cfg > Server IP address 0.0.0.0:27015 > scandir failed:/usr/home/hlds/1.6/./platform/SAVE > *** glibc detected *** ./hlds_i686: double free or corruption (!prev): > 0x08da3738 *** > ======= Backtrace: ========= > /lib/libc.so.6[0x2811ac88] > /lib/libc.so.6(cfree+0x90)[0x2811e230] > /lib/libc.so.6(closedir+0x28)[0x2813ecf8] > /lib/libc.so.6(scandir+0x14b)[0x2813f21b] > /usr/home/hlds/1.6/filesystem_stdio_i386.so(findFileInDirCaseInsensitive__F >PCc+0xe4)[0x28af41d8] > > /usr/home/hlds/1.6/filesystem_stdio_i386.so(FS_stat__17CFileSystem_StdioPCc >P4stat+0x40)[0x28af861c] > > /usr/home/hlds/1.6/filesystem_stdio_i386.so(FastFindFileSize__15CBaseFileSy >stemPCQ215CBaseFileSystem11CSearchPathPCc+0x17e)[0x28af572a] > > /usr/home/hlds/1.6/filesystem_stdio_i386.so(Size__15CBaseFileSystemPCc+0x5b >)[0x28af557b] > > /usr/home/hlds/1.6/engine_i686.so(FS_FileSize+0x2a)[0x2828679e] > ======= Memory map: ======== > 08048000-08054000 r-xp 0003a000 00:00 1931338 > /usr/home/hlds/1.6/hlds_i686 > 08054000-0805b000 rw-p 0003a000 00:00 1931338 > /usr/home/hlds/1.6/hlds_i686 > 0805b000-0805e000 rw-p 00d60000 00:00 0 > 0805e000-08dbb000 rwxp 00d60000 00:00 0 > 28054000-2806d000 r-xp 0001e000 00:00 1719480 > /usr/compat/linux/lib/ld-2.5.so > 2806d000-2806e000 r-xp 0001e000 00:00 1719480 > /usr/compat/linux/lib/ld-2.5.so > 2806e000-2806f000 rw-p 00002000 00:00 0 > 2806f000-28070000 rwxp 00002000 00:00 0 > 28071000-28073000 r-xp 00004000 00:00 1719493 > /usr/compat/linux/lib/libdl-2.5.so > 28073000-28074000 r-xp 00004000 00:00 1719493 > /usr/compat/linux/lib/libdl-2.5.so > 28074000-28075000 rwxp 00004000 00:00 1719493 > /usr/compat/linux/lib/libdl-2.5.so > 28075000-28076000 rwxp 00001000 00:00 0 > 28076000-28088000 r-xp 0001e000 00:00 1719511 > /usr/compat/linux/lib/libpthread-2.5.so > 28088000-28089000 r-xp 0001e000 00:00 1719511 > /usr/compat/linux/lib/libpthread-2.5.so > 28089000-2808a000 rwxp 0001e000 00:00 1719511 /usr/compat/linuxAbort > trap (core dumped) > debug.cmds:1: Error in sourced command file: > Previous frame inner to this frame (corrupt stack?) > email debug.log to linux at valvesoftware.com > Wed Sep 12 > 20:27:04 SAMST 2007: Server restart in 10 seconds > Wed Sep 12 20:27:06 SAMST 2007: Server Quit > # > =================================================== > > # uname -a > FreeBSD damask 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed Sep 12 17:04:55 > SAMST 2007 root at cs.udmvt.ru > :/usr/obj/usr/ >src/sys/CS2 i386 > > # sysctl compat > compat.linux.oss_version: 198144 > compat.linux.osrelease: 2.6.16 > compat.linux.osname: Linux > > # kldstat > Id Refs Address Size Name > 1 14 0xc0400000 3e6ee0 kernel > 2 1 0xc07e7000 69514 acpi.ko > 3 1 0xc3ddd000 7000 linprocfs.ko > 4 2 0xc3de4000 21000 linux.ko > 5 1 0xc3e0e000 3000 linsysfs.ko > > # mount|grep linux > linprocfs on /usr/compat/linux/proc (linprocfs, local) > linsysfs on /usr/compat/linux/sys (linsysfs, local) > > # pkg_info | grep linux > linux_base-fc6-6_3 Base set of packages needed in Linux mode (for > i386/amd64) > > [private links to debug.log & ktrace.out] > > please send me message after downloaded this files (for removing) > > /Vladimir Ermakov > > cross-posting: > http://lists.freebsd.org/pipermail/freebsd-emulation/2007-September/003960. >html I haven't tried it on i386 yet, but I know that this works on amd64 with linux 2.4 compat and linux_base-fc4 on FreeBSD 7. - Pieter From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 19:15:46 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437BB16A418; Mon, 24 Sep 2007 19:15:46 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFC713C45B; Mon, 24 Sep 2007 19:15:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80CE0.6010609@FreeBSD.org> Date: Mon, 24 Sep 2007 21:15:44 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:15:46 -0000 Ivan Voras wrote: > Benjie Chen wrote: > >> Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin >> c066c7b4 T _mtx_lock_spin >> c066c85c T _mtx_unlock_sleep >> >> So this could mean that independent stress tests will not result in >> panic if >> there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html Surely it cannot be since it involves a different function ;-) Kris From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 19:25:00 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CCD516A41B for ; Mon, 24 Sep 2007 19:25:00 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id 1ADF413C4A3 for ; Mon, 24 Sep 2007 19:25:00 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1341364rvb for ; Mon, 24 Sep 2007 12:25:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=Qt6y2GCW1z1uSO+jacwVctVad8qdG+Lrx6YGBM0PS7M=; b=RwTOfuFp10nzjgcHTJhtzV0bFTNFONMInvl78/BvFyT+ppzkGJIozz9K3uieeuCoIIYVpLd41H+dZmnuGQedOjkyqqqiiHcjPQjyH/Eq7u7S8EVeXHElR9SMbJVSZ+0o8PYxdvoJwd5M+y90xt3pb7GG/5W/wAXng8U4GHihOnw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=N5zLUQ/wMR0NBFPerw7c2jkpVWdtYoRvIiG2x9KWOgEaRJ1hz+PmkD7gm852NK9fLhwu5mGp+xwOShiT6KwQPcs/QuPt2TVcocR6X5tfI8wgG7ubbUxMF02LxUvg3/gL8zttuyvXV3OZDCAtDU+yh2Z3umVq42gtQAZ0EacCCrM= Received: by 10.140.250.14 with SMTP id x14mr1739123rvh.1190661481178; Mon, 24 Sep 2007 12:18:01 -0700 (PDT) Received: by 10.141.159.3 with HTTP; Mon, 24 Sep 2007 12:18:01 -0700 (PDT) Message-ID: <9bbcef730709241218u20d1824cn20c72d0863f6366e@mail.gmail.com> Date: Mon, 24 Sep 2007 21:18:01 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Kris Kennaway" In-Reply-To: <46F80CE0.6010609@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F80CE0.6010609@FreeBSD.org> X-Google-Sender-Auth: adfe825d10757db5 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:25:00 -0000 On 24/09/2007, Kris Kennaway wrote: > Ivan Voras wrote: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html > > Surely it cannot be since it involves a different function ;-) :) When all you have is a hammer... From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 19:35:20 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E76D016A419 for ; Mon, 24 Sep 2007 19:35:20 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id C155513C455 for ; Mon, 24 Sep 2007 19:35:20 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1343679rvb for ; Mon, 24 Sep 2007 12:35:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=gEa2/4tUSTaYto9mmtyQ0XFkxMpmYPQ+DYlvscpFQmA=; b=sYyWC7cQtROUU7Tef/HcYgho1fl4eY5puxBHb3DKWpJst0tJtcQOD+nLYGfCNf70BfayvrgcjEHWw3XlZeRBmzH/RkF+eIbDj8HD2UFIxPCRAay9sQd17l67uptnPghsbLFOGdvQIkke5XxQWvYPr9DvsIZUe1mD6lqUUBcytP0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=kBGJsqheo2CwnLfkP9oMHPUTdtztHtKiOxgNU6hisD1P8wiRvmbIiHg9hdususfFsaonZdQpLWH0QSANU9FhAx4+4UlkcCKJrP6LCyCkOZlIt2osWJsihJguOXAC233PljMs23eN78UyE32JKDnyx+ZRZqIY9nn6f0q64PJ0YIo= Received: by 10.140.177.15 with SMTP id z15mr1738425rve.1190661075563; Mon, 24 Sep 2007 12:11:15 -0700 (PDT) Received: by 10.141.159.3 with HTTP; Mon, 24 Sep 2007 12:11:15 -0700 (PDT) Message-ID: <9bbcef730709241211o479e3e5dwf64382596c837dfb@mail.gmail.com> Date: Mon, 24 Sep 2007 21:11:15 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Benjie Chen" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Google-Sender-Auth: d92aa624b22c440d Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:35:21 -0000 On 24/09/2007, Benjie Chen wrote: > Ivan and Kris, > > I will try to get a kernel trace -- it may not happen for awhile since I am > not in the office and working remotely for awhile so it may not be easy to > get a trace... but I will check. It's fairly easy: 1) add lines like the following in rc.conf: dumpdev="/dev/amrd0s1b" dumpdir="/storage1/crashdumps" (dumpdev is your swap partition, which must be larger than your RAM, dumpdir is where the crash dumps will be saved, also needs to be larger than RAM) 2) add these lines to sysctl.conf: debug.debugger_on_panic=0 debug.trace_on_panic=1 (These will cause the panic message and backtrace to be automatically recorded in the message buffer saved to the kernel crash dump. If not told otherwise, the machine will then reboot and at the next boot generate a crash dump in your dumpdir. When you get the kernel crash dump, run "kgdb vmcore.0 /boot/kernel/kernel" as root and then you can inspect the trace, core dump, etc. You don't need any special knowledge of (k)gdb for this. The one useful command to you may be "bt" - generate a backtrace). > It looks like the problem reported by that link, and some of the links from > there though... I'm trying to solve that one with Craig Rodrigues. So far it's been without success but we know where the problem is. From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 20:01:33 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52D0C16A41A for ; Mon, 24 Sep 2007 20:01:33 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from webmail31.mail.yandex.net (webmail31.mail.yandex.net [213.180.223.177]) by mx1.freebsd.org (Postfix) with ESMTP id AE66213C45B for ; Mon, 24 Sep 2007 20:01:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from YAMAIL (webmail31) by mail.yandex.ru id S6455639AbXIXTvT for ; Mon, 24 Sep 2007 23:51:19 +0400 X-Yandex-Spam: 1 Received: from [77.72.136.69] ([77.72.136.69]) by mail.yandex.ru with HTTP; Mon, 24 Sep 2007 23:51:19 +0400 From: "Andrey V. Elsukov" To: kkuehl@cisco.com In-Reply-To: 1550000000217039020 References: 1550000000217039020 MIME-Version: 1.0 Message-Id: <300481190663479@webmail31.yandex.ru> Date: Mon, 24 Sep 2007 23:51:19 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain Cc: freebsd-hackers@freebsd.org Subject: Re: Intel D975XBX2 BTX halted X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 20:01:33 -0000 Hi, i have motherboard with integrated Marvell 88SE6141 controller. And i can't boot from any drives attached to this controller. This controller family is not yet supported. > After experiencing overheating problems, I purchased a new CPU and motherboard > (Intel D975XBX2) which has a built in Raid controller Marvell 88SE61xx > I connected my existing FreeBSD-STABLE SATA drive to port 0. > Upon boot, I receive the following error: -- WBR, Andrey V. Elsukov From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 22:59:47 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4223F16A49C for ; Mon, 24 Sep 2007 22:59:47 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from anny.lostinspace.de (anny.ipv6.lostinspace.de [IPv6:2a01:138:100:1:219:d1ff:fe6a:ef49]) by mx1.freebsd.org (Postfix) with ESMTP id AFC1913C515 for ; Mon, 24 Sep 2007 22:59:46 +0000 (UTC) (envelope-from idefix@fechner.net) Received: from server.idefix.lan (ppp-82-135-85-62.dynamic.mnet-online.de [82.135.85.62]) (authenticated bits=0) by anny.lostinspace.de (8.14.1/8.14.1) with ESMTP id l8OMxXUM065267 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 25 Sep 2007 00:59:38 +0200 (CEST) (envelope-from idefix@fechner.net) Received: from idefix by server.idefix.lan with local (Exim 4.68 (FreeBSD)) (envelope-from ) id 1IZwsz-000LmJ-F1 for freebsd-hackers@freebsd.org; Tue, 25 Sep 2007 00:58:41 +0200 Date: Tue, 25 Sep 2007 00:58:41 +0200 From: Matthias Fechner To: freebsd-hackers@freebsd.org Message-ID: <20070924225841.GA75866@server.idefix.lan> References: <46F22228.5070203@fechner.net> <20070923151916.GB1444@roadrunner.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070923151916.GB1444@roadrunner.spoerlein.net> X-Crypto: GnuPG/1.0.6 http://www.gnupg.org X-GnuPG: 0x1B756EF6 User-Agent: Mutt/1.5.16 (2007-06-09) Sender: Matthias Fechner X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (anny.lostinspace.de [80.190.182.2]); Tue, 25 Sep 2007 00:59:38 +0200 (CEST) X-Spam-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00, UNPARSEABLE_RELAY autolearn=ham version=3.2.3 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on anny.lostinspace.de X-Virus-Scanned: ClamAV 0.91.2/4382/Mon Sep 24 23:24:56 2007 on anny.lostinspace.de X-Virus-Status: Clean Subject: Re: Own Install CD with custom kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Sep 2007 22:59:47 -0000 Hello Ulrich, * Ulrich Spoerlein [23-09-07 17:19]: > I'm using a Makefile to drive our release and package building and for > the releases I'm using an install.cfg, which gets created on the fly, > since the names of the kernels change now and then, here is the release > target thx a lot for your really great answer, but I have some more short questions. :) Do you copy the release target to the Makefile in /usr/src/release/Makefile or do you execute from another place? > rm -f ${TLR}/usr/src/release/.install.cfg > [...] > cd ${TRR}/R/ftp && find -d . | cpio --quiet -dumpl ${TFR} hm, cannot found the variables TLR and TRR anywhere defined. Can you please give me some more information how your buildprocess looks? > And files/install.cfg contains the following where should I store that file? man release doesn't give here any information about it. > So basically, sysinstall is intructed to not install any kernel, but > after all distributions are extracted the following commands are run > > command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh GENERIC" > system > command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh SMP" > system where can you say sysinstall that it should run such commands after the installation? Best regards, Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 23:56:18 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 622AE16A419 for ; Mon, 24 Sep 2007 23:56:18 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (adsl-75-1-14-242.dsl.scrm01.sbcglobal.net [75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 1101313C45B for ; Mon, 24 Sep 2007 23:56:17 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id l8ONU0IT008004; Mon, 24 Sep 2007 16:30:04 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200709242330.l8ONU0IT008004@gw.catspoiler.org> Date: Mon, 24 Sep 2007 16:30:00 -0700 (PDT) From: Don Lewis To: samflanker@gmail.com In-Reply-To: <46F7CCF8.5010402@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-hackers@FreeBSD.org Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 23:56:18 -0000 On 24 Sep, sam wrote: > hi, all > http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html > > my problem > # fsck /dev/aacd0s1f > ** /dev/aacd0s1f (NO WRITE) > ** Last Mounted on /usr > ** Phase 1 - Check Blocks and Sizes > fsck_ufs: cannot alloc 2378019004 bytes for inoinfo I'd be willing to bet that one of the cylinder group blocks in your file system got corrupted. > any solutions ? The patch below should allow a manual fsck to run to completion. I'd recommend running "fsck -N" and capturing its output. Then use the clri command (either standalone or in fsdb) to zero out the uninitialized inodes that are unmasked by setting cg_initediblk to its maximum possible value based on the file system parameters. Expect major file system lossage ... I think this patch could be better, but this should get you going ... Index: sbin/fsck_ffs/pass1.c =================================================================== RCS file: /home/ncvs/src/sbin/fsck_ffs/pass1.c,v retrieving revision 1.43 diff -u -r1.43 pass1.c --- sbin/fsck_ffs/pass1.c 8 Oct 2004 20:44:47 -0000 1.43 +++ sbin/fsck_ffs/pass1.c 24 Sep 2007 23:15:22 -0000 @@ -93,9 +93,29 @@ inumber = c * sblock.fs_ipg; setinodebuf(inumber); getblk(&cgblk, cgtod(&sblock, c), sblock.fs_cgsize); - if (sblock.fs_magic == FS_UFS2_MAGIC) + if (sblock.fs_magic == FS_UFS2_MAGIC) { inosused = cgrp.cg_initediblk; - else + if (inosused < 0 || inosused > sblock.fs_ipg) { + pfatal("CG %d: PREPOSTEROUS NUMBER OF INODES %d (cg_initediblk), ASSUMING %d (fs_ipg)\n", + c, inosused, sblock.fs_ipg); + /* + * The cylinder group block is most likely + * totally corrupted and will probably + * fail the magic number check below as well. + * Ignoring cg_initediblk and setting + * inosused to sblock.fs_ipg will allow + * a manual fsck to proceed further instead + * of dying when it attempts to allocate + * an insane amount of memory to store + * the inode info for this cylinder group. + * This may provide enough information + * to allow the system administrator to + * do a better job of patching the + * filesystem with fsdb. + */ + inosused = sblock.fs_ipg; + } + } else inosused = sblock.fs_ipg; if (got_siginfo) { printf("%s: phase 1: cyl group %d of %d (%d%%)\n", From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 01:24:00 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C7FE16A41A; Tue, 25 Sep 2007 01:24:00 +0000 (UTC) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.freebsd.org (Postfix) with ESMTP id 1D21313C45B; Tue, 25 Sep 2007 01:23:59 +0000 (UTC) (envelope-from frank@exit.com) Received: from jill.exit.com (jill.exit.com [206.223.0.4]) by tinker.exit.com (8.14.1/8.14.1) with ESMTP id l8P0sKOH053476; Mon, 24 Sep 2007 17:54:20 -0700 (PDT) (envelope-from frank@exit.com) Received: from jill.exit.com (localhost [127.0.0.1]) by jill.exit.com (8.14.1/8.14.1) with ESMTP id l8P0sKo6016200; Mon, 24 Sep 2007 17:54:20 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by jill.exit.com (8.14.1/8.14.1/Submit) id l8P0sKD5016199; Mon, 24 Sep 2007 17:54:20 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: jill.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: Don Lewis In-Reply-To: <200709242330.l8ONU0IT008004@gw.catspoiler.org> References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Mon, 24 Sep 2007 17:54:20 -0700 Message-Id: <1190681660.60981.2.camel@jill.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.91.1/4383/Mon Sep 24 15:26:10 2007 on tinker.exit.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, samflanker@gmail.com Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 01:24:00 -0000 On Mon, 2007-09-24 at 16:30 -0700, Don Lewis wrote: > On 24 Sep, sam wrote: > > hi, all > > http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html > > > > my problem > > # fsck /dev/aacd0s1f > > ** /dev/aacd0s1f (NO WRITE) > > ** Last Mounted on /usr > > ** Phase 1 - Check Blocks and Sizes > > fsck_ufs: cannot alloc 2378019004 bytes for inoinfo > > I'd be willing to bet that one of the cylinder group blocks in your file > system got corrupted. > > > any solutions ? > > The patch below should allow a manual fsck to run to completion. I'd > recommend running "fsck -N" and capturing its output. Then use the clri > command (either standalone or in fsdb) to zero out the uninitialized > inodes that are unmasked by setting cg_initediblk to its maximum > possible value based on the file system parameters. > > Expect major file system lossage ... You might also want to try ports/sysutils/ffsrecov2 before you run this fsck. It might allow you to recover data that would otherwise be lost. (Like, say, if there are directories hidden beneath the corrupt inode.) -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ http://www.zazzle.com/fmayhar* From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 04:39:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28E0116A418 for ; Tue, 25 Sep 2007 04:39:24 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.freebsd.org (Postfix) with ESMTP id DA0A713C45A for ; Tue, 25 Sep 2007 04:39:23 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (qevi4km7462weulg@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.6/8.13.3) with ESMTP id l8P4DDsL048481; Mon, 24 Sep 2007 21:13:13 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.6/8.13.3/Submit) id l8P4DANK048480; Mon, 24 Sep 2007 21:13:10 -0700 (PDT) (envelope-from jmg) Date: Mon, 24 Sep 2007 21:13:10 -0700 From: John-Mark Gurney To: Ian Smith Message-ID: <20070925041310.GA47467@funkthat.com> Mail-Followup-To: Ian Smith , freebsd-hackers@freebsd.org References: <46F48911.6010106@nimnet.asn.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F48911.6010106@nimnet.asn.au> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (hydrogen.funkthat.com [127.0.0.1]); Mon, 24 Sep 2007 21:13:13 -0700 (PDT) Cc: freebsd-hackers@freebsd.org Subject: Re: how to use iic(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 04:39:24 -0000 Ian Smith wrote this message on Sat, Sep 22, 2007 at 13:16 +1000: > This drew a blank in -questions. I don't know where else to post it, so > I'm hoping someone here might be able to spare me a clue. You should probably have posted this question to -hackers instead.. This is more low level hardware than networking... > We're building a small board with two AVR Tiny MCUs chatting to each > other over an opto-isolated I2C-compatible bus, hopefully at 400kbps. > > Hoping to use the iicbb(4) on lpbb(4) parallel port interface to talk > with either of these MCUs for debugging, control and data acquisition. > > iic(4) says: > ======= > The iic character device driver provides generic i/o to any iicbus(4) > instance. In order to control I2C devices, use /dev/iic? with the fol- > lowing ioctls: > > Ioctl Description > I2CSTART send start condition to the specified device (with 7-bit > address) on the bus > I2CSTOP send stop condition to the bus > I2CRSTCARD reset the bus > > You may also use read/write routines, then I2C start/stop handshake is > managed by the iicbus system. > ======= > > Does the latter statement suggest that ordinary reads from or writes to > /dev/iic? could be performed by redirection of say echo and read from a > script? Or is the device only accessible by ioctl from eg a C program? No, as you need to select (via I2CSTART) the slave device you are talking w/ before you do a read or a write... > Secondly, how does /dev/iic? come to exist? This 5.5-STABLE system > seems to have all the requisite drivers, but there's no /dev/iic*: > paqi% kldstat -v | egrep 'iic|lpbb' > 29 iicbus/ic > 30 iicbus/iic > 31 bktr/iicbb > 32 lpbb/iicbb > 33 viapm/iicbb > 34 pcf/iicbus > 35 envctrl/iicbus > 36 iicbb/iicbus > 37 bti2c/iicbus > 38 iicbus/iicsmb > 86 iicsmb/smbus > 12 1 0xc2456000 3000 lpbb.ko > 247 ppbus/lpbb You need to have a device that connects between your i2c bus hardware and iicbb or iicbus... I'm not familar w/ lpbb, but I have used /dev/iic? w/ some HD capture card drivers I've written, and they are created when the device driver probes them... lpbb may need hints to get it to attach, or may need a properly functioning parallel port.. > Also, iicbb(4) is said to be a master-only interface. I can work with > that, but if anyone knows of any iicbus slave-mode code I'm all eyes .. That's even more complicated as you either need specialized hardware that will detect when your i2c address is on the bus, or you need to poll/interrupt on line changes, which could get a bit expensive... I have a command line iic program that I used to help debug my drivers.. The tool lets you start and then read/write from the device, and then stop the bus... I haven't committed it yet, because a few other developers want it under tools, and I don't like it there, as no one knows about most of the tools under there... Maybe if we had a man page that talked about the tools available there it'd be more attractive... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 05:40:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0926B16A417 for ; Tue, 25 Sep 2007 05:40:52 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.freebsd.org (Postfix) with ESMTP id 7DC0213C458 for ; Tue, 25 Sep 2007 05:40:51 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1360324nfb for ; Mon, 24 Sep 2007 22:40:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=6R/Eg+YQF5v+4BlBwTXyQZaF6D0Q6ghvLJpUAu9fVgc=; b=fwraKfqVqFhNAB7aj1J+Hndg8XHrIhTQv7JfGFBZ6IxqknEq9GmlVT9YKndK2k2f22i96d81iqVgnIVUbgsYD2fnShh45clqExbMxvwsfBWbZobYZnjREfsPwKWIWyja+G2GtI7I/xIsegUHCudHZerpP2sQc/CAYjKoPl6IyO8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=RRzRXJo26cfvydCmh1UQiud0wBd11dwa6XF3Wm0gC2kFMvdzzqhPmd1o/ihd1Jy/xL/palMeYyOT92WHC3WTZpugqHUeXjiOlPJ832efn4BcOf0UZo3+cFlfI+9l0E4sfkvo8SG44ktZaagqa3JT/0Z7ch4/5Ohf368Eff4tNtA= Received: by 10.86.99.9 with SMTP id w9mr3622796fgb.1190698850053; Mon, 24 Sep 2007 22:40:50 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id g28sm12251151fkg.2007.09.24.22.40.47 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Sep 2007 22:40:47 -0700 (PDT) Message-ID: <46F89F5A.2060301@gmail.com> Date: Tue, 25 Sep 2007 09:40:42 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Pieter de Goeje References: <46F78343.6060809@gmail.com> <200709242022.25624.pieter@degoeje.nl> In-Reply-To: <200709242022.25624.pieter@degoeje.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: linuxolator problem on i386 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 05:40:52 -0000 Pieter de Goeje wrote: > On Monday 24 September 2007, sam wrote: > >> # mount|grep linux >> linprocfs on /usr/compat/linux/proc (linprocfs, local) >> linsysfs on /usr/compat/linux/sys (linsysfs, local) >> >> # pkg_info | grep linux >> linux_base-fc6-6_3 Base set of packages needed in Linux mode (for >> i386/amd64) >> >> [private links to debug.log & ktrace.out] >> >> please send me message after downloaded this files (for removing) >> >> /Vladimir Ermakov >> >> cross-posting: >> http://lists.freebsd.org/pipermail/freebsd-emulation/2007-September/003960. >> html >> > I haven't tried it on i386 yet, but I know that this works on amd64 with linux > 2.4 compat and linux_base-fc4 on FreeBSD 7. > > - Pieter > > yes, working but, this trouble in kernel new linux-software require linux 2.6 /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 06:14:19 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5C7016A417 for ; Tue, 25 Sep 2007 06:14:19 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.189]) by mx1.freebsd.org (Postfix) with ESMTP id 253F613C457 for ; Tue, 25 Sep 2007 06:14:18 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so2279420mue for ; Mon, 24 Sep 2007 23:14:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=Zjd9yPI+oaw/bM7A7F0vWiWm3qFmTYmx3KBitHOz9bk=; b=urSaBG0l3BgxhOOsPpCKRYVWauqTaBFgTyHMnEQzyzXrS4wGo4ebf9s1Js2Oh2kKBLzs1T9EdVWq35pOBxzduagq0thLmWSYLwNF28P8RbqN3KMwG4cua+K1y70aexy837fVVedvLlLxS2CSJ68q9a6itbiZV1GwzBJjdTwRZLg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NWd74bk4VQx51gqKESlFa5ApT1DBWeXTyqJuQZNdaOQ2wASMmonIDlS0mjpjpdsEQLkvqetRqXXYar38TXO1wL8FCxQ0HbVgbTpITkwwM7ILmVIncW/vMc/MW/QYaiaRUwGMRFAJ4X4ZXMv12/Su0n2Vk2u8mnpR4k9uYysAn5w= Received: by 10.86.77.5 with SMTP id z5mr4191803fga.1190700856365; Mon, 24 Sep 2007 23:14:16 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id f31sm12314989fkf.2007.09.24.23.14.13 (version=SSLv3 cipher=RC4-MD5); Mon, 24 Sep 2007 23:14:14 -0700 (PDT) Message-ID: <46F8A730.509@gmail.com> Date: Tue, 25 Sep 2007 10:14:08 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: frank@exit.com References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> <1190681660.60981.2.camel@jill.exit.com> In-Reply-To: <1190681660.60981.2.camel@jill.exit.com> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Don Lewis Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 06:14:19 -0000 Frank Mayhar wrote: > >>> hi, all >>> http://lists.freebsd.org/pipermail/freebsd-questions/2007-June/151686.html >>> >>> my problem >>> # fsck /dev/aacd0s1f >>> ** /dev/aacd0s1f (NO WRITE) >>> ** Last Mounted on /usr >>> ** Phase 1 - Check Blocks and Sizes >>> >>> > You might also want to try ports/sysutils/ffsrecov2 before you run this > fsck. It might allow you to recover data that would otherwise be lost. > (Like, say, if there are directories hidden beneath the corrupt inode.) > thx but this partition is mounted, iam have access to this data trouble in boot stage /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 06:39:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 748DE16A419 for ; Tue, 25 Sep 2007 06:39:52 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from loki.netlab.sk (loki.netlab.sk [84.245.65.11]) by mx1.freebsd.org (Postfix) with ESMTP id EFFDC13C465 for ; Tue, 25 Sep 2007 06:39:51 +0000 (UTC) (envelope-from freebsd-hackers@dino.sk) Received: from lex.dino.sk (home.dino.sk [84.245.95.252]) (AUTH: PLAIN milan, TLS: TLSv1/SSLv3,256bits,AES256-SHA) by loki.netlab.sk with esmtp; Tue, 25 Sep 2007 08:28:38 +0200 id 0002E023.46F8AA96.00011CF1 From: Milan Obuch To: freebsd-hackers@freebsd.org, John-Mark Gurney Date: Tue, 25 Sep 2007 07:15:10 +0200 User-Agent: KMail/1.9.6 References: <46F48911.6010106@nimnet.asn.au> <20070925041310.GA47467@funkthat.com> In-Reply-To: <20070925041310.GA47467@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709250715.13520.freebsd-hackers@dino.sk> Cc: Subject: Re: how to use iic(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 06:39:52 -0000 On Tuesday 25 September 2007 06:13:10 John-Mark Gurney wrote: > Ian Smith wrote this message on Sat, Sep 22, 2007 at 13:16 +1000: > > This drew a blank in -questions. I don't know where else to post it, so > > I'm hoping someone here might be able to spare me a clue. > > You should probably have posted this question to -hackers instead.. > This is more low level hardware than networking... > ... > > You need to have a device that connects between your i2c bus hardware > and iicbb or iicbus... I'm not familar w/ lpbb, but I have used > /dev/iic? w/ some HD capture card drivers I've written, and they are > created when the device driver probes them... lpbb may need hints to > get it to attach, or may need a properly functioning parallel port.. > > > Also, iicbb(4) is said to be a master-only interface. I can work with > > that, but if anyone knows of any iicbus slave-mode code I'm all eyes .. > > That's even more complicated as you either need specialized hardware > that will detect when your i2c address is on the bus, or you need to > poll/interrupt on line changes, which could get a bit expensive... > > I have a command line iic program that I used to help debug my drivers.. > The tool lets you start and then read/write from the device, and then > stop the bus... > > I haven't committed it yet, because a few other developers want it under > tools, and I don't like it there, as no one knows about most of the > tools under there... Maybe if we had a man page that talked about the > tools available there it'd be more attractive... Could you post it somewhere? Web, maybe... I was trying to write i2c driver for WRAP board, but failed. Now it's time to try again, maybe, (there is new generation WRAP board). It is definitely possible, there is an ACB driver in OpenBSD, but I did not gain knowledge to port it, the whole bus/driver infrastructure is too different... Regards, Milan -- No need to mail me directly. Just reply to mailing list, please. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 07:17:39 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E371F16A41B for ; Tue, 25 Sep 2007 07:17:39 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.191]) by mx1.freebsd.org (Postfix) with ESMTP id 61B7C13C461 for ; Tue, 25 Sep 2007 07:17:38 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by mu-out-0910.google.com with SMTP id w9so2297157mue for ; Tue, 25 Sep 2007 00:17:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=A3rfKxkNc9My3flhJVm8wF2qWfxAVPAGyErf0xXKRlI=; b=lpDqBKMa5ytA1bZOId9FDhY4Lvflj0mW7VfNb+d4niA0bGgME9+QQ8pqq7372dTDEDnu7Zoydui7jicCzCtfz60bJjFRYyOoQad8ai4RIgzKlgzY6XIctMI6Jqk/S97fpOihE0MbjUJw2lwP0ZvN0X91pXrkCSmp3ZgqPMeIzKY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=oS0xnmOs0JlbXGJMIuGntMOsigqOlJzdy0OcstnMFGOl98HABmT7cjmQI5XzRb2qIbT4L58PsWTj2tbbhJzIAwbBkwReTwMTmmQDKBul4PZkZB2khg3556Fp6rClW5QwNLVhT+P5kagNIR5UtdfVMkdLh4YaAG7RMhea9069bVc= Received: by 10.86.58.3 with SMTP id g3mr5394835fga.1190704657369; Tue, 25 Sep 2007 00:17:37 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id y18sm12406338fkd.2007.09.25.00.17.35 (version=SSLv3 cipher=RC4-MD5); Tue, 25 Sep 2007 00:17:36 -0700 (PDT) Message-ID: <46F8B60A.3080901@gmail.com> Date: Tue, 25 Sep 2007 11:17:30 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Don Lewis References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> In-Reply-To: <200709242330.l8ONU0IT008004@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 07:17:40 -0000 Don Lewis wrote: > On 24 Sep, sam wrote: > > >> any solutions ? >> > > The patch below should allow a manual fsck to run to completion. I'd > recommend running "fsck -N" and capturing its output. Then use the clri > # fsck -N fsck: illegal option -- N usage: fsck [-dfnpvy] [-B | -F] [-T fstype:fsoptions] [-t fstype] [special | node] ... /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 07:42:30 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B24A616A417 for ; Tue, 25 Sep 2007 07:42:30 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from ramstind.fig.ol.no (ramstind.fig.ol.no [IPv6:2001:700:1100:1:250:4ff:fe43:9d15]) by mx1.freebsd.org (Postfix) with ESMTP id 1DD0E13C45D for ; Tue, 25 Sep 2007 07:42:29 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from ramstind.fig.ol.no (Ximalas@localhost [127.0.0.1]) by ramstind.fig.ol.no (8.13.8/8.13.8) with ESMTP id l8P7gJ2B032959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 25 Sep 2007 09:42:20 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by ramstind.fig.ol.no (8.13.8/8.13.8/Submit) with ESMTP id l8P7gJAi032956 for ; Tue, 25 Sep 2007 09:42:19 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: ramstind.fig.ol.no: trond owned process doing -bs Date: Tue, 25 Sep 2007 09:42:15 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: freebsd-hackers@freebsd.org In-Reply-To: <46F8B60A.3080901@gmail.com> Message-ID: <20070925093902.E7819@ramstind.fig.ol.no> References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> <46F8B60A.3080901@gmail.com> Organization: =?ISO-8859-1?Q?Fagskolen_i_Gj=F8vik?= MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1890754826-1190706020=:7819" Content-ID: <20070925094039.Q7819@ramstind.fig.ol.no> X-Spam-Status: No, hits=0.0 required=5.0 tests=UPPERCASE_25_50 autolearn=failed X-Spam-Checker-Version: SpamAssassin on ramstind.fig.ol.no Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 07:42:30 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1890754826-1190706020=:7819 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Content-Transfer-Encoding: 8BIT Content-ID: <20070925094039.S7819@ramstind.fig.ol.no> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 25 Sep 2007 11:17+0400, sam wrote: > fsck: illegal option -- N Try: fsck -n man fsck should give you some hints on what Don was talking about. I.e.: -n Causes fsck to assume no as the answer to all operator questions, except "CONTINUE?". - -- - ---------------------------------------------------------------------- Trond Endrestøl | trond@fagskolen.gjovik.no Patron of The Art of Computer Programming| FreeBSD 6.2-S & Pine 4.64 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFG+LvbbYWZalUoElsRAoHTAJ0fDsiQZ6eauxnL8FK3UDDUSA8oMgCeNpcv vzDPK6R+nXz2SGzNdAK3qpI= =xWtk -----END PGP SIGNATURE----- --0-1890754826-1190706020=:7819-- From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 07:50:22 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39DBB16A41B for ; Tue, 25 Sep 2007 07:50:22 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.184]) by mx1.freebsd.org (Postfix) with ESMTP id 69C0813C469 for ; Tue, 25 Sep 2007 07:50:21 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1378582nfb for ; Tue, 25 Sep 2007 00:50:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=9sOevAwGUQzWwiBe6DTR+MA/KIhqiG3C+v7Us4G/8FE=; b=rNc5od38wFbmmwM4hjiDbiga3zBnT18ND00byIXMW/ooU2gL2P1hWaYb0AtfV2dqrgrP/Sl2fH41edlueUntYm5aHxLVZfeTjropJnokd/BOOUqrvsEwRcJ9FlzWflwCEY93BTBZrPaelmropmKoE3xcr6WDGN55B9zFScloHUs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=m4bM748EgAQGswSysSaojJ7YCaDLw+ED9y18QMAmsAOiUIxU4c06abBudTTttCqluU0Bv+z0Udv2ZLiYjsletT3zyH768uljsQT4rPAcHiWlNHF6tdK58R0p/o1SwMCVbRXFbWKZU1/4oRpXVJz04nNeh1hFBPR42d5N2i2nRfc= Received: by 10.86.93.17 with SMTP id q17mr5411696fgb.1190706620030; Tue, 25 Sep 2007 00:50:20 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id 31sm12473465fkt.2007.09.25.00.50.17 (version=SSLv3 cipher=RC4-MD5); Tue, 25 Sep 2007 00:50:18 -0700 (PDT) Message-ID: <46F8BDAD.4000309@gmail.com> Date: Tue, 25 Sep 2007 11:50:05 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 To: Don Lewis References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> In-Reply-To: <200709242330.l8ONU0IT008004@gw.catspoiler.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 07:50:22 -0000 Don Lewis wrote: > On 24 Sep, sam wrote: > > Expect major file system lossage ... > I think this patch could be better, but this should get you going ... > > Index: sbin/fsck_ffs/pass1.c > =================================================================== > RCS file: /home/ncvs/src/sbin/fsck_ffs/pass1.c,v > retrieving revision 1.43 > diff -u -r1.43 pass1.c > --- sbin/fsck_ffs/pass1.c 8 Oct 2004 20:44:47 -0000 1.43 > +++ sbin/fsck_ffs/pass1.c 24 Sep 2007 23:15:22 -0000 > @@ -93,9 +93,29 @@ > inumber = c * sblock.fs_ipg; > setinodebuf(inumber); > getblk(&cgblk, cgtod(&sblock, c), sblock.fs_cgsize); > - if (sblock.fs_magic == FS_UFS2_MAGIC) > + if (sblock.fs_magic == FS_UFS2_MAGIC) { > inosused = cgrp.cg_initediblk; > - else > + if (inosused < 0 || inosused > sblock.fs_ipg) { > + pfatal("CG %d: PREPOSTEROUS NUMBER OF INODES %d (cg_initediblk), ASSUMING %d (fs_ipg)\n", > + c, inosused, sblock.fs_ipg); > + /* > + * The cylinder group block is most likely > + * totally corrupted and will probably > + * fail the magic number check below as well. > + * Ignoring cg_initediblk and setting > + * inosused to sblock.fs_ipg will allow > + * a manual fsck to proceed further instead > + * of dying when it attempts to allocate > + * an insane amount of memory to store > + * the inode info for this cylinder group. > + * This may provide enough information > + * to allow the system administrator to > + * do a better job of patching the > + * filesystem with fsdb. > + */ > + inosused = sblock.fs_ipg; > + } > + } else > inosused = sblock.fs_ipg; > if (got_siginfo) { > printf("%s: phase 1: cyl group %d of %d (%d%%)\n", > > > after patching ====================================================== # fsck /dev/aacd0s1f ** /dev/aacd0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes CG 124: PREPOSTEROUS NUMBER OF INODES 1668246575 (cg_initediblk), ASSUMING 23552 (fs_ipg) UNEXPECTED SOFT UPDATE INCONSISTENCY ** Phase 2 - Check Pathnames UNALLOCATED I=2732216 OWNER=svn MODE=40755 SIZE=512 MTIME=Sep 4 12:22 2007 DIR=/home/svn UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=2732189 OWNER=venom MODE=40755 SIZE=512 MTIME=Sep 3 17:16 2007 DIR=/home/venom/svn UNEXPECTED SOFT UPDATE INCONSISTENCY REMOVE? no UNALLOCATED I=2732248 OWNER=root MODE=40755 SIZE=512 MTIME=Sep 14 19:03 2007 DIR=/home/venom/temp/devel/trunk *** DELETE OUTPUT *** ** Phase 3 - Check Connectivity UNREF DIR I=2755667 OWNER=games MODE=40750 SIZE=1536 MTIME=Jul 19 16:45 2007 RECONNECT? no UNREF DIR I=2755600 OWNER=games MODE=40750 SIZE=1024 MTIME=Jul 19 16:45 2007 RECONNECT? no UNREF DIR I=2755628 OWNER=games MODE=40750 SIZE=1536 MTIME=Jul 19 16:45 2007 RECONNECT? no UNREF DIR I=2755584 OWNER=games MODE=40750 SIZE=512 MTIME=Jul 19 16:45 2007 RECONNECT? no ** Phase 4 - Check Reference Counts UNREF FILE I=541705 OWNER=root MODE=100555 SIZE=218296 MTIME=Sep 10 14:51 2007 CLEAR? no UNREF FILE I=541950 OWNER=root MODE=100555 SIZE=37832 MTIME=Sep 10 14:52 2007 CLEAR? no *** DELETE OUTPUT *** UNREF FILE I=4875961 OWNER=root MODE=100444 SIZE=35552 MTIME=Sep 10 14:50 2007 CLEAR? no UNREF FILE I=6312454 OWNER=root MODE=104555 SIZE=15880 MTIME=Sep 10 14:52 2007 CLEAR? no ** Phase 5 - Check Cyl groups CG 116: BAD MAGIC NUMBER UNEXPECTED SOFT UPDATE INCONSISTENCY FREE BLK COUNT(S) WRONG IN SUPERBLK SALVAGE? no SUMMARY INFORMATION BAD SALVAGE? no BLK(S) MISSING IN BIT MAPS SALVAGE? no CG 124: BAD MAGIC NUMBER UNEXPECTED SOFT UPDATE INCONSISTENCY LOST 74 DIRECTORIES UNEXPECTED SOFT UPDATE INCONSISTENCY fsck: /dev/aacd0s1f: Segmentation fault: 11 # ====================================================== /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Mon Sep 24 15:42:41 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C312F16A41B for ; Mon, 24 Sep 2007 15:42:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9271913C465 for ; Mon, 24 Sep 2007 15:42:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by wa-out-1112.google.com with SMTP id k17so2088931waf for ; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Received: by 10.115.17.1 with SMTP id u1mr728887wai.1190648560551; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Mon, 24 Sep 2007 08:42:40 -0700 (PDT) Message-ID: Date: Mon, 24 Sep 2007 11:42:40 -0400 From: "Benjie Chen" To: "Ivan Voras" In-Reply-To: MIME-Version: 1.0 References: X-Mailman-Approved-At: Tue, 25 Sep 2007 08:28:44 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 15:42:41 -0000 Ivan and Kris, I will try to get a kernel trace -- it may not happen for awhile since I am not in the office and working remotely for awhile so it may not be easy to get a trace... but I will check. It looks like the problem reported by that link, and some of the links from there though... Benjie On 9/24/07, Ivan Voras wrote: > > Benjie Chen wrote: > > > Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin > > c066c7b4 T _mtx_lock_spin > > c066c85c T _mtx_unlock_sleep > > > > So this could mean that independent stress tests will not result in > panic if > > there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html > > > > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 08:53:05 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9DC216A418 for ; Tue, 25 Sep 2007 08:53:05 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 526C613C457 for ; Tue, 25 Sep 2007 08:53:05 +0000 (UTC) (envelope-from samflanker@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1388740nfb for ; Tue, 25 Sep 2007 01:53:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=HZzdXbJASjFQYq+nTf7O12ddtz0wvUiDJyBJPaKIx3I=; b=eZY8Liq4H+hkjqz7tbzUsh5jGLwQjhnIEArHZDvYupoQmIQH8BSuT4ta+wEVQCqSRLh124fG/8LvDZwgvjDPIn50QyKZzhnaD4P32jX8a3oWqJak1pw6lae++0fdDhJdCKQ/uq0cR5ww7Ldjd1D+pK3nveNjb7vuhAOTg5MI5C0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=lJOJmhVLw8FnPFOk0ceq7H1D6CcXNgh1/v4k/7aQOSAFpF6LUg9SREljn5jIwxxoAsn1bK8wKuvLpdbZgD3bwTvREZ4MoNhVk0Ht7SB5U4oDuyiCoKCnaD8FSmFYHr9w+g5Xq9gi9eYklBxHW95pC1G/lEqKoaUH9qDA8Jq5kyw= Received: by 10.86.95.20 with SMTP id s20mr4045518fgb.1190710384096; Tue, 25 Sep 2007 01:53:04 -0700 (PDT) Received: from ?192.168.1.185? ( [213.152.137.35]) by mx.google.com with ESMTPS id o11sm12620026fkf.2007.09.25.01.53.02 (version=SSLv3 cipher=RC4-MD5); Tue, 25 Sep 2007 01:53:03 -0700 (PDT) Message-ID: <46F8CC62.903@gmail.com> Date: Tue, 25 Sep 2007 12:52:50 +0400 From: sam User-Agent: Thunderbird 2.0.0.4 (Windows/20070604) MIME-Version: 1.0 References: <200709242330.l8ONU0IT008004@gw.catspoiler.org> <46F8BDAD.4000309@gmail.com> In-Reply-To: <46F8BDAD.4000309@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@FreeBSD.org, Don Lewis Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 08:53:06 -0000 sam wrote: > Don Lewis wrote: >> On 24 Sep, sam wrote: >> Expect major file system lossage ... >> I think this patch could be better, but this should get you going ... >> >> > > > UNEXPECTED SOFT UPDATE INCONSISTENCY > LOST 74 DIRECTORIES > > UNEXPECTED SOFT UPDATE INCONSISTENCY > fsck: /dev/aacd0s1f: Segmentation fault: 11 > # > ====================================================== > > /Vladimir Ermakov > > # cat /etc/rc.conf |grep fsck fsck_y_enable="YES" background_fsck="NO" hm, and after system reboot ================================================= # fsck /dev/aacd0s1f ** /dev/aacd0s1f (NO WRITE) ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 438959 files, 3567329 used, 69528964 free (94684 frags, 8679285 blocks, 0.1% fragmentation) # ================================================= my big thx /Vladimir Ermakov From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 09:13:18 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E0D7A16A41B for ; Tue, 25 Sep 2007 09:13:18 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 3026C13C458; Tue, 25 Sep 2007 09:13:17 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F8D12E.7060202@FreeBSD.org> Date: Tue, 25 Sep 2007 11:13:18 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Benjie Chen , freebsd-hackers@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 09:13:19 -0000 Benjie Chen wrote: > Ivan and Kris, > > I will try to get a kernel trace -- it may not happen for awhile since I am > not in the office and working remotely for awhile so it may not be easy to > get a trace... but I will check. > > It looks like the problem reported by that link, and some of the links from > there though... Does it really? i.e. did you compare the function names in detail and find that they match precisely, or do you just mean "they are both panics of some description and I dunno what it all means"? :) I ask because the linked trace does not involve a spinlock, which means it cannot be precisely the same trace. Kris From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 12:43:31 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC78016A418 for ; Tue, 25 Sep 2007 12:43:31 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 7057D13C44B for ; Tue, 25 Sep 2007 12:43:31 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Ia9l2-0001hW-Lr for freebsd-hackers@freebsd.org; Tue, 25 Sep 2007 12:43:20 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 12:43:20 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 25 Sep 2007 12:43:20 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Tue, 25 Sep 2007 14:43:09 +0200 Lines: 34 Message-ID: References: <46F8D12E.7060202@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig84A152B62A6A8ADA5CD0A085" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 1.5.0.12 (X11/20060911) In-Reply-To: <46F8D12E.7060202@FreeBSD.org> X-Enigmail-Version: 0.94.4.0 Sender: news Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 12:43:31 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig84A152B62A6A8ADA5CD0A085 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Kris Kennaway wrote: > Does it really? i.e. did you compare the function names in detail and=20 > find that they match precisely, or do you just mean "they are both=20 > panics of some description and I dunno what it all means"? :) I ask=20 > because the linked trace does not involve a spinlock, which means it=20 > cannot be precisely the same trace. Isn't spinning and waiting "adaptive"? (AFAIK some locks spin for a=20 short while before they wait). At least, that's why I thought they might = be the same problem. --------------enig84A152B62A6A8ADA5CD0A085 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFG+QJdldnAQVacBcgRAxgsAJ9hH+MtE+RuOOng5ryMcuE8RLqKigCgnK1g wwvIezHzeSTZewZxc+z/3M8= =65wF -----END PGP SIGNATURE----- --------------enig84A152B62A6A8ADA5CD0A085-- From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 16:27:32 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B025616A41B for ; Tue, 25 Sep 2007 16:27:32 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 18BD313C45B for ; Tue, 25 Sep 2007 16:27:31 +0000 (UTC) (envelope-from uspoerlein@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so1486467nfb for ; Tue, 25 Sep 2007 09:27:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=pXK5u6k5keSHYYd7iYukw5MgoVrQULN2Zv52pVcjd8w=; b=Luwzwsk5ACMWdrvBRiEvl/aBs90SvzszxOl80XDgM6I/nwV2KnKs7REOG9qwuk7axad8BgTyudm7GeLe0T7mMcYMtKuEQx2NJYrbEyOCIR3L75GeanKV6Cgu4Xw4kiTi1DhQfe1ZX0ajlT//d+GQDo+9FusimgC8bg5+h+4jIYY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Zon3xJ3GvkZTb2hno0F4HhNsHe0gGNE5fqeuJJAJ5mqTCWo8FWfDrNH3pFRYh4yPV4iGlpfcUIK8bay30tCtiSBFYwmMV17uckwH4QmVW09jS5+k1ms83o/rzhdP9FigzsigVV/Kpdxajogs8USshSdVD7iyFmZCCVojXJECehc= Received: by 10.78.201.2 with SMTP id y2mr4513412huf.1190737649542; Tue, 25 Sep 2007 09:27:29 -0700 (PDT) Received: by 10.78.173.13 with HTTP; Tue, 25 Sep 2007 09:27:29 -0700 (PDT) Message-ID: <7ad7ddd90709250927o772264b1v34446145d292b8bd@mail.gmail.com> Date: Tue, 25 Sep 2007 18:27:29 +0200 From: "Ulrich Spoerlein" To: freebsd-hackers@freebsd.org In-Reply-To: <20070924225841.GA75866@server.idefix.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F22228.5070203@fechner.net> <20070923151916.GB1444@roadrunner.spoerlein.net> <20070924225841.GA75866@server.idefix.lan> Subject: Re: Own Install CD with custom kernel X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 16:27:32 -0000 On 9/25/07, Matthias Fechner wrote: > thx a lot for your really great answer, but I have some more short > questions. :) > Do you copy the release target to the Makefile in > /usr/src/release/Makefile or do you execute from another place? Since we need to be able to reproduce our releases, we use the chroot facility and build those releases in their very own directory. That way we can also easily use a custom make.conf, especially for the package building (which are built in that same chroot). So, with the variables as defined below, I first run the 'init' target, which sets up the chroot environment init: mkdir -p ${TLR}/usr ${TLR}/etc ${TLR}/usr/ports/local mkdir -p ${TFR}/packages ${TFR}/distfiles ${TLR}/usr/ports/packages ${TLR}/usr/ports/distfiles cd ${TLR}/usr && ${CVS} co -r ${SRCBRANCH} ${SRCDATE} src cd ${TLR}/usr/src && make -j4 buildworld DESTDIR=${TLR} cd ${TLR}/usr/src && make installworld DESTDIR=${TLR} cd ${TLR}/usr/src && make distribution DESTDIR=${TLR} cd ${TLR}/usr && ${CVS} co ${PORTSDATE} ports cp -pr ports/* ${TLR}/usr/ports/local then 'release' is run as given in my previous mail. After that, the 'packages' target does a lot of voodoo and then loops over a make variable which contains all the packages we are interested in and builds them. It is kind of messy, though as we have local patches which are to be applied to the cvs checkout. Makeing this step idempotent is ... interesting. > > rm -f ${TLR}/usr/src/release/.install.cfg > > [...] > > cd ${TRR}/R/ftp && find -d . | cpio --quiet -dumpl ${TFR} > > hm, cannot found the variables TLR and TRR anywhere defined. Can you > please give me some more information how your buildprocess looks? These are just arbitrary places where the stuff is located, they are defined as # Build tree, needs LOTS of space ... T= /build # Shortcuts TLR= $T/live/${RELEASE} TRR= $T/release/${RELEASE} TFR= $T/ftproot/pub/FreeBSD/${RELEASE} > > And files/install.cfg contains the following > > where should I store that file? > man release doesn't give here any information about it. This is documented somewhere in sysinstall(8), I guess. You can place it on a floppy (yeah, right). I put it in ${TLR}/usr/src/release/install.cfg as you saw from the example in my previous mail and it should then make it into the ISO. How exactly this works, I can't remember right now ... Ah, src/release/Makefile contains under the release.8 target: -test -f ${.CURDIR}/install.cfg \ && cp ${.CURDIR}/install.cfg ${RD}/mfsfd So it ends up in the MFS from which FreeBSD installs itself. > > So basically, sysinstall is intructed to not install any kernel, but > > after all distributions are extracted the following commands are run > > > > command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh GENERIC" > > system > > command=/bin/sh -c "cd /dist/${RELEASE}/kernels && ./install.sh SMP" > > system > > where can you say sysinstall that it should run such commands after > the installation? install.cfg, take a look at /usr/src/usr.sbin/sysinstall/install.cfg hth, Uli From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 17:51:37 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9047216A420 for ; Tue, 25 Sep 2007 17:51:37 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id C894113C469; Tue, 25 Sep 2007 17:51:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F94AAA.5030504@FreeBSD.org> Date: Tue, 25 Sep 2007 19:51:38 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Benjie Chen References: <46F8D12E.7060202@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:51:37 -0000 Benjie Chen wrote: > You are right, they may not be the same. From first look it seems like > they are similar based on the description of the problems -- system > stable, then under load related to network, get panic after different > time intervals. I just assumed that kernel is typically stable enough > that this kind of panic are rare (been using FBSD for 7 or 8 years now > and in heavy loads as well, never had kernel panics to deal with). OK, that means it is likely it has absolutely nothing in common. > I did reboot the system and set mpsafenet to 0 and I have not had a > crash since then (almost a day) running the same load, so that's > positive: at least it may be that that's the workaround, and I don't > need Dell to send me new memory modules to try... That should only be considered a temporary workaround while you continue to obtain debugging information to solve the problem for good. e.g. support for mpsafenet=0 has already been removed from 7.0. > Kris or Ivan: I was wondering if you could briefly explain what your > guess the problem might be. I am curious what the cause of the problem > is. E.g. it seems like a race condition, but I am curious to know more > of the details... It is impossible to say until you obtain some actual details about the panic :) Kris From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 17:54:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DD9B16A418; Tue, 25 Sep 2007 17:54:52 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 5C5CE13C457; Tue, 25 Sep 2007 17:54:51 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F94B6C.2090107@FreeBSD.org> Date: Tue, 25 Sep 2007 19:54:52 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: <46F8D12E.7060202@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:54:52 -0000 Ivan Voras wrote: > Kris Kennaway wrote: > >> Does it really? i.e. did you compare the function names in detail and >> find that they match precisely, or do you just mean "they are both >> panics of some description and I dunno what it all means"? :) I ask >> because the linked trace does not involve a spinlock, which means it >> cannot be precisely the same trace. > > Isn't spinning and waiting "adaptive"? (AFAIK some locks spin for a > short while before they wait). At least, that's why I thought they might > be the same problem. Not in the sense of transmuting a sleep mutex into a spin mutex, no. sleep mutexes will spin when the lock holder is currently running, but this happens within the context of the mtx_lock_sleep function itself. Kris From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 18:36:51 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 316B616A41B for ; Tue, 25 Sep 2007 18:36:51 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.186]) by mx1.freebsd.org (Postfix) with ESMTP id D24F913C46A for ; Tue, 25 Sep 2007 18:36:50 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: by rv-out-0910.google.com with SMTP id l15so1601777rvb for ; Tue, 25 Sep 2007 11:36:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=yy44clij25ABiFu6IqbZvzo+RuLee9Gyt39UDOlzKXw=; b=Yu/1yj7RU06Y66/Oyf8RunaQO38YIOLQg2CLSl8/wnu89xgtLvjzpsaZwEHQd0+D8dF0z+h8/xlJNfkhlMjDlkZG25QvVNLRCscERHbOQXsel0P0cTvErnrGjip6mZ+56oLwAfZYNJ1f9Ias4+myQQSCZk7+JyTx3vpXuj5ALb0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=YnEyiaIHXrzohUmg3JJ8d5sDrfBWxa84EklyUuXvQB2z5tq0QZIF2cEIqmRuA/uzFH0ra0h8KT9LlBROh2X0Z1cGWp+KJBbr4f5unB8mCt3neM9JfdZTJLty0VvZ8Ndplia8W0jiHZ/NZZAGjYSih+MJVARfsbpMkT9JQngBj5g= Received: by 10.141.137.8 with SMTP id p8mr2032487rvn.1190745408943; Tue, 25 Sep 2007 11:36:48 -0700 (PDT) Received: by 10.141.159.3 with HTTP; Tue, 25 Sep 2007 11:36:48 -0700 (PDT) Message-ID: <9bbcef730709251136j24bacae2j9b1e216d58fee10@mail.gmail.com> Date: Tue, 25 Sep 2007 20:36:48 +0200 From: "Ivan Voras" Sender: ivoras@gmail.com To: "Kris Kennaway" In-Reply-To: <46F94B6C.2090107@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46F8D12E.7060202@FreeBSD.org> <46F94B6C.2090107@FreeBSD.org> X-Google-Sender-Auth: 6c48700c1c325eb0 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:36:51 -0000 On 25/09/2007, Kris Kennaway wrote: > Not in the sense of transmuting a sleep mutex into a spin mutex, no. > sleep mutexes will spin when the lock holder is currently running, but > this happens within the context of the mtx_lock_sleep function itself. Ok, thanks, this clears things a bit for me. From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 18:50:18 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C87DF16A421 for ; Tue, 25 Sep 2007 18:50:18 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (adsl-75-1-14-242.dsl.scrm01.sbcglobal.net [75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 7F8D813C46A for ; Tue, 25 Sep 2007 18:50:18 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id l8PIo9WJ010198; Tue, 25 Sep 2007 11:50:13 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200709251850.l8PIo9WJ010198@gw.catspoiler.org> Date: Tue, 25 Sep 2007 11:50:09 -0700 (PDT) From: Don Lewis To: samflanker@gmail.com In-Reply-To: <46F8B60A.3080901@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-hackers@FreeBSD.org Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 18:50:18 -0000 On 25 Sep, sam wrote: > Don Lewis wrote: >> On 24 Sep, sam wrote: >> >> >>> any solutions ? >>> >> >> The patch below should allow a manual fsck to run to completion. I'd >> recommend running "fsck -N" and capturing its output. Then use the clri >> > # fsck -N > fsck: illegal option -- N > usage: fsck [-dfnpvy] [-B | -F] [-T fstype:fsoptions] [-t fstype] > [special | node] ... Sorry, it should be "fsck -n". From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 19:22:09 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BFE916A418 for ; Tue, 25 Sep 2007 19:22:09 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (adsl-75-1-14-242.dsl.scrm01.sbcglobal.net [75.1.14.242]) by mx1.freebsd.org (Postfix) with ESMTP id 6420E13C457 for ; Tue, 25 Sep 2007 19:22:09 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id l8PJM284010258; Tue, 25 Sep 2007 12:22:06 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <200709251922.l8PJM284010258@gw.catspoiler.org> Date: Tue, 25 Sep 2007 12:22:02 -0700 (PDT) From: Don Lewis To: samflanker@gmail.com In-Reply-To: <46F8CC62.903@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Cc: freebsd-hackers@FreeBSD.org Subject: Re: fsck of large volume with small memory X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 19:22:09 -0000 On 25 Sep, sam wrote: > sam wrote: >> Don Lewis wrote: >>> On 24 Sep, sam wrote: >>> Expect major file system lossage ... >>> I think this patch could be better, but this should get you going ... >>> >>> >> >> >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> LOST 74 DIRECTORIES >> >> UNEXPECTED SOFT UPDATE INCONSISTENCY >> fsck: /dev/aacd0s1f: Segmentation fault: 11 It would be good to know the cause of this segfault so that the code could be fixed to prevent it. >> # >> ====================================================== >> >> /Vladimir Ermakov >> >> > # cat /etc/rc.conf |grep fsck > fsck_y_enable="YES" > background_fsck="NO" > > hm, and after system reboot > > ================================================= > # fsck /dev/aacd0s1f > ** /dev/aacd0s1f (NO WRITE) > ** Last Mounted on /usr > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 438959 files, 3567329 used, 69528964 free (94684 frags, 8679285 blocks, > 0.1% fragmentation) > # > ================================================= That's the fastest way of getting the file system back into a consistent state (or you could run "fsck -y" in single-user mode), but it increases the probability of data loss. The problem is that my patch allows fsck to examine a bunch of uninitialized inodes in the damaged cylinder group, and there is the possibility that one or more of these inodes could look reasonably valid and contain block pointers that point to blocks in valid files. Fsck will then detect the duplicate block pointers and clear the inodes for both files. It would be nice if fsck could be told to put less trust in the inodes that might not actually be initialized, but this gets complicated ... From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 22:31:19 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7940F16A418 for ; Tue, 25 Sep 2007 22:31:19 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchfe01.datapipe-corp.net (exchfe01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id 2C36513C465 for ; Tue, 25 Sep 2007 22:31:19 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from [192.168.131.233] (192.168.131.233) by exchfe01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server (TLS) id 8.0.730.1; Tue, 25 Sep 2007 18:21:06 -0400 Message-ID: <46F98972.80403@datapipe.com> Date: Tue, 25 Sep 2007 18:19:30 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: "freebsd-hackers@FreeBSD.org" Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Tue, 25 Sep 2007 22:31:19 -0000 Hello Hackers I was looking into setting up the Intel / NetBSD iSCSI Target port on FreeBSD 6-STABLE . The first question I have is related to the use of the iscsi target port on FreeBSD. In the original docs, bundled with the Intel source, Intel had an example of setting up the target to have direct access to a raw device. Below is a snippet from /usr/ports/net/iscsi-target/work/netbsd-iscsi-20070908/doc/README With ufsdisk and ufsdisk_mmap you can directly access a device in /dev by creating a symbolic link in /tmp to point to the appropriate device. For example: "ln -s /dev/sdd /tmp/iqn.com.intel.abc123_3260_iscsi_disk_lun_0" Does anyone know off hand if this works in FreeBSD or NetBSD? The second question what iscsi initiators are out there ? Along time ago Lucent had iscsi software for FreeBSD 4.x which has initiator support but this has a restrictive license and does not support anything newer then 4.9-RELEASE . Does anyone know what else could possibly be used on 6-STABLE ? Thanks Again. -- Mark Saad DataPipe Managed Global IT Services msaad@datapipe.com From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 14:58:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E00B16A417 for ; Tue, 25 Sep 2007 14:58:24 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.181]) by mx1.freebsd.org (Postfix) with ESMTP id 178A513C468 for ; Tue, 25 Sep 2007 14:58:23 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by wa-out-1112.google.com with SMTP id k17so2468092waf for ; Tue, 25 Sep 2007 07:58:23 -0700 (PDT) Received: by 10.115.47.1 with SMTP id z1mr7311369waj.1190732302607; Tue, 25 Sep 2007 07:58:22 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Tue, 25 Sep 2007 07:58:22 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 10:58:22 -0400 From: "Benjie Chen" To: "Kris Kennaway" In-Reply-To: <46F8D12E.7060202@FreeBSD.org> MIME-Version: 1.0 References: <46F8D12E.7060202@FreeBSD.org> X-Mailman-Approved-At: Wed, 26 Sep 2007 12:41:19 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 14:58:24 -0000 You are right, they may not be the same. From first look it seems like they are similar based on the description of the problems -- system stable, then under load related to network, get panic after different time intervals. I just assumed that kernel is typically stable enough that this kind of panic are rare (been using FBSD for 7 or 8 years now and in heavy loads as well, never had kernel panics to deal with). Upon closer look at the trace and the problem, they may not be the same, since one on those web pages was about the route code and my breaks only in one place - waiting for a lock. Again, I will see if I could get a dump when I return to the office. I did reboot the system and set mpsafenet to 0 and I have not had a crash since then (almost a day) running the same load, so that's positive: at least it may be that that's the workaround, and I don't need Dell to send me new memory modules to try... Kris or Ivan: I was wondering if you could briefly explain what your guess the problem might be. I am curious what the cause of the problem is. E.g. it seems like a race condition, but I am curious to know more of the details... Thanks, Benjie On 9/25/07, Kris Kennaway wrote: > > Benjie Chen wrote: > > Ivan and Kris, > > > > I will try to get a kernel trace -- it may not happen for awhile since I > am > > not in the office and working remotely for awhile so it may not be easy > to > > get a trace... but I will check. > > > > It looks like the problem reported by that link, and some of the links > from > > there though... > > Does it really? i.e. did you compare the function names in detail and > find that they match precisely, or do you just mean "they are both > panics of some description and I dunno what it all means"? :) I ask > because the linked trace does not involve a spinlock, which means it > cannot be precisely the same trace. > > Kris > > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 16:30:43 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFF0016A498 for ; Tue, 25 Sep 2007 16:30:43 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from rv-out-0910.google.com (rv-out-0910.google.com [209.85.198.191]) by mx1.freebsd.org (Postfix) with ESMTP id 7B70513C481 for ; Tue, 25 Sep 2007 16:30:43 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by rv-out-0910.google.com with SMTP id l15so1572726rvb for ; Tue, 25 Sep 2007 09:30:43 -0700 (PDT) Received: by 10.114.135.1 with SMTP id i1mr1698771wad.1190737842656; Tue, 25 Sep 2007 09:30:42 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Tue, 25 Sep 2007 09:30:42 -0700 (PDT) Message-ID: Date: Tue, 25 Sep 2007 12:30:42 -0400 From: "Benjie Chen" To: "Kris Kennaway" In-Reply-To: MIME-Version: 1.0 References: <46F8D12E.7060202@FreeBSD.org> X-Mailman-Approved-At: Wed, 26 Sep 2007 12:41:19 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 16:30:44 -0000 Well I spoke too soon. I increased the load even more and it crashed again. Same IP. So FYI, mpsafenet did not work, although it did allow me to stress the system for longer than I've ever done before. Perhaps that just reduced the concurrency enough. I will try kernel trace next. Thanks, Benjie On 9/25/07, Benjie Chen wrote: > > You are right, they may not be the same. From first look it seems like > they are similar based on the description of the problems -- system stable, > then under load related to network, get panic after different time > intervals. I just assumed that kernel is typically stable enough that this > kind of panic are rare (been using FBSD for 7 or 8 years now and in heavy > loads as well, never had kernel panics to deal with). > > Upon closer look at the trace and the problem, they may not be the same, > since one on those web pages was about the route code and my breaks only in > one place - waiting for a lock. Again, I will see if I could get a dump when > I return to the office. > > I did reboot the system and set mpsafenet to 0 and I have not had a crash > since then (almost a day) running the same load, so that's positive: at > least it may be that that's the workaround, and I don't need Dell to send me > new memory modules to try... > > Kris or Ivan: I was wondering if you could briefly explain what your guess > the problem might be. I am curious what the cause of the problem is. E.g. > it seems like a race condition, but I am curious to know more of the > details... > > Thanks, > Benjie > > > > On 9/25/07, Kris Kennaway wrote: > > > > Benjie Chen wrote: > > > Ivan and Kris, > > > > > > I will try to get a kernel trace -- it may not happen for awhile since > > I am > > > not in the office and working remotely for awhile so it may not be > > easy to > > > get a trace... but I will check. > > > > > > It looks like the problem reported by that link, and some of the links > > from > > > there though... > > > > Does it really? i.e. did you compare the function names in detail and > > find that they match precisely, or do you just mean "they are both > > panics of some description and I dunno what it all means"? :) I ask > > because the linked trace does not involve a spinlock, which means it > > cannot be precisely the same trace. > > > > Kris > > > > > > > -- > Benjie Chen, Ph.D. > Addgene, a better way to share plasmids > www.addgene.org > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 25 17:02:34 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCC4916A496 for ; Tue, 25 Sep 2007 17:02:34 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF4813C478 for ; Tue, 25 Sep 2007 17:02:34 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mail.rsync.net (8.12.11/8.12.11) with ESMTP id l8PGp6dN019089 for ; Tue, 25 Sep 2007 09:51:06 -0700 (PDT) (envelope-from info@rsync.net) Received: from localhost (info@localhost) by mail.rsync.net (8.12.11/8.12.11/Submit) with ESMTP id l8PGp6p7019086 for ; Tue, 25 Sep 2007 09:51:06 -0700 (PDT) (envelope-from info@rsync.net) X-Authentication-Warning: mail.rsync.net: info owned process doing -bs Date: Tue, 25 Sep 2007 09:51:06 -0700 (PDT) From: "rsync.net" To: freebsd-hackers@freebsd.org Message-ID: <20070925093722.N21960@mail.rsync.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 26 Sep 2007 12:41:19 +0000 Subject: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Sep 2007 17:02:34 -0000 It has been impossible to change kern.ngroups - at least for several years now. It was not fixed in either 5.x or 6.x : http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html It is seemingly a difficult problem: http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] However it should be solved - we can't be the only ones out there trying to add a UID to more than 16 groups... ----- The rsync.net code bounties have been fairly successful this year - two of the five projects have been completed, and the large "vmware 6 on FreeBSD" project is now underway. We'd like to add a new bounty for this kern.ngroups issue. We are posting to -hackers today to get some feedback on how long this will take and how much money might reasonably be expected to lure this work. --rsync.net Support [1] Is it indeed true that these programs are broken by not following NGROUPS_MAX from syslimits.h? From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 05:15:39 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B75DD16A4F1 for ; Wed, 26 Sep 2007 05:15:39 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 3EC4D13C467 for ; Wed, 26 Sep 2007 05:15:37 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id OAA13729; Wed, 26 Sep 2007 14:44:03 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Wed, 26 Sep 2007 14:44:02 +1000 (EST) From: Ian Smith To: John-Mark Gurney In-Reply-To: <20070925041310.GA47467@funkthat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Wed, 26 Sep 2007 12:49:09 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: how to use iic(4) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 05:15:39 -0000 On Mon, 24 Sep 2007, John-Mark Gurney wrote: > Ian Smith wrote this message on Sat, Sep 22, 2007 at 13:16 +1000: > > This drew a blank in -questions. I don't know where else to post it, so > > I'm hoping someone here might be able to spare me a clue. > > You should probably have posted this question to -hackers instead.. > This is more low level hardware than networking... Ok, and thanks heaps for your response. I'll follow -hackers on the web on this, but really can't deal with any more subscribed lists just now. I should also confess straight up that C is pretty much read-only for me, I'm most at home with assembler (though not x86) and other languages perhaps best not mentioned in polite -hackers company .. best I can manage in C is a bit of hacking on existing code frameworks and such. > > We're building a small board with two AVR Tiny MCUs chatting to each > > other over an opto-isolated I2C-compatible bus, hopefully at 400kbps. > > > > Hoping to use the iicbb(4) on lpbb(4) parallel port interface to talk > > with either of these MCUs for debugging, control and data acquisition. > > > > iic(4) says: > > ======= > > The iic character device driver provides generic i/o to any iicbus(4) > > instance. In order to control I2C devices, use /dev/iic? with the fol- > > lowing ioctls: > > > > Ioctl Description > > I2CSTART send start condition to the specified device (with 7-bit > > address) on the bus > > I2CSTOP send stop condition to the bus > > I2CRSTCARD reset the bus > > > > You may also use read/write routines, then I2C start/stop handshake is > > managed by the iicbus system. > > ======= > > > > Does the latter statement suggest that ordinary reads from or writes to > > /dev/iic? could be performed by redirection of say echo and read from a > > script? Or is the device only accessible by ioctl from eg a C program? > > No, as you need to select (via I2CSTART) the slave device you are talking > w/ before you do a read or a write... Ah right, then I did indeed misinterpret that last sentence quoted above, and need to study that code in depth .. I've only skimmed so far. > > Secondly, how does /dev/iic? come to exist? This 5.5-STABLE system > > seems to have all the requisite drivers, but there's no /dev/iic*: > > paqi% kldstat -v | egrep 'iic|lpbb' > > 29 iicbus/ic > > 30 iicbus/iic > > 31 bktr/iicbb > > 32 lpbb/iicbb > > 33 viapm/iicbb > > 34 pcf/iicbus > > 35 envctrl/iicbus > > 36 iicbb/iicbus > > 37 bti2c/iicbus > > 38 iicbus/iicsmb > > 86 iicsmb/smbus > > 12 1 0xc2456000 3000 lpbb.ko > > 247 ppbus/lpbb > > You need to have a device that connects between your i2c bus hardware > and iicbb or iicbus... I'm not familar w/ lpbb, but I have used > /dev/iic? w/ some HD capture card drivers I've written, and they are > created when the device driver probes them... lpbb may need hints to > get it to attach, or may need a properly functioning parallel port.. I have the latter, but as you see I kldloaded lbpp; maybe it needs to be compiled in kernel. Nothing obvious in device.hints. I'll do some more research, now that you've increased my confidence that this should be doable, and that there's at least one somebody to hassle for details :) > > Also, iicbb(4) is said to be a master-only interface. I can work with > > that, but if anyone knows of any iicbus slave-mode code I'm all eyes .. > > That's even more complicated as you either need specialized hardware > that will detect when your i2c address is on the bus, or you need to > poll/interrupt on line changes, which could get a bit expensive... Thought as much. pcf(4) looked promising, but it's apparently only for the isa bus, or at least was at the time this was written. > I have a command line iic program that I used to help debug my drivers.. > The tool lets you start and then read/write from the device, and then > stop the bus... Pretty much exactly what I need, sounds like! > I haven't committed it yet, because a few other developers want it under > tools, and I don't like it there, as no one knows about most of the > tools under there... Maybe if we had a man page that talked about the > tools available there it'd be more attractive... Any chance of a sneak preview, John-Mark? Promise I won't break it .. Cheers, Ian From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 15:07:59 2007 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4107716A418 for ; Wed, 26 Sep 2007 15:07:59 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 48EEA13C47E for ; Wed, 26 Sep 2007 15:07:59 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id E0055117A8; Wed, 26 Sep 2007 10:07:58 -0500 (CDT) Date: Wed, 26 Sep 2007 10:07:57 -0500 From: Craig Boston To: freebsd-hackers@FreeBSD.org Message-ID: <20070926150756.GA26578@nowhere> Mail-Followup-To: Craig Boston , freebsd-hackers@FreeBSD.org References: <46F98972.80403@datapipe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46F98972.80403@datapipe.com> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 15:07:59 -0000 On Tue, Sep 25, 2007 at 06:19:30PM -0400, Mark Saad wrote: > Does anyone know off hand if this works in FreeBSD or NetBSD? The last time (about 1.5 months ago) I tried the iSCSI target from ports -- net/iscsi-target, it had some issues. The first was that it didn't work with raw devices. The cause was that in a couple places it tries to read a single byte from the device, but on FreeBSD where everything is a character device you have to read using the block size. I suspect that NetBSD still has buffered block devices so it isn't an issue there. I hacked it locally to read 512 (at mediasize-512 instead of mediasize-1) for its test and that seemed to work, but it was pretty ugly. The right way would be to use an ioctl to get the block size I think. The other thing was that it was listening on a different port number than the FreeBSD initiator was trying to connect to. For some reason even though iscsi-target claims to have a "-p" option to specify the port number, after reading the code it was clear that it doesn't actually use that value for anything and instead is hardcoded to use whatever is in /etc/services. I checked the NetBSD cvs and the same issue existed there. Reading the code gave me the distinct impression that it was incomplete. > The second question what iscsi initiators are out there ? Along time > ago Lucent had iscsi software for FreeBSD 4.x which has initiator > support but this has a restrictive license and does not support anything > newer then 4.9-RELEASE . Does anyone know what else could possibly be > used on 6-STABLE ? I'm not sure about 6-STABLE, though a kernel initiator was added to 7 not too long ago. Craig From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 16:06:25 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5A4C16A420; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id A828B13C457; Wed, 26 Sep 2007 16:06:25 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 1E9EF1A4D94; Wed, 26 Sep 2007 08:48:16 -0700 (PDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 26 Sep 2007 10:28:42 -0400 User-Agent: KMail/1.9.7 References: <20070901073440.GL85633@comp.chem.msu.su> <46DAFE5C.6070806@freebsd.org> <20070903120353.GH30502@comp.chem.msu.su> In-Reply-To: <20070903120353.GH30502@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709261028.43378.jhb@freebsd.org> Cc: Yar Tikhiy , Tim Kientzle Subject: Re: Useful tools missing from /rescue X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 16:06:25 -0000 On Monday 03 September 2007 08:03:53 am Yar Tikhiy wrote: > On Sun, Sep 02, 2007 at 11:18:04AM -0700, Tim Kientzle wrote: > > Yar Tikhiy wrote: > > >Hi all, > > > > > >I've had to use /rescue recently and felt lack of a few basic tools > > >in it, namely pgrep(1), head(1), tail(1), tee(1), and a text filter, > > >e.g., sed(1). Well, in fact most functionality of pgrep(1), head(1), > > >tail(1), and even tee(1) can be emulated if one has sed(1), but the > > >tools are so tiny and convenient that it's a pity not to have them > > >all handy during hard times. > > > > > >In addition, there are chflags and chmod in /rescue, but there's > > >no chown in it, so the toolset is a bit incomplete. > > > > Oh, my. chown was definitely an oversight. That > > should have been in there. > > > > My opinions: > > * head, tail, and tee are no-brainers; just do it. > > * sed would be a nice addition. (I atttempted to > > fit 'vi' in there, but curses is rather finicky; > > 'sed' would be more useful.) > > Thank you for supporting my idea! I would go for all of these as well as 'chown'. Are you still planning on doing this? -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 16:35:59 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A3B016A49E for ; Wed, 26 Sep 2007 16:35:59 +0000 (UTC) (envelope-from cb@severious.net) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 339EB13C467 for ; Wed, 26 Sep 2007 16:35:59 +0000 (UTC) (envelope-from cb@severious.net) Received: by ion.gank.org (Postfix, from userid 1001) id C331B115D7; Wed, 26 Sep 2007 11:35:58 -0500 (CDT) Date: Wed, 26 Sep 2007 11:35:58 -0500 From: Craig Boston To: Michael Reifenberger Message-ID: <20070926163558.GA76061@nowhere> References: <46F98972.80403@datapipe.com> <20070926150756.GA26578@nowhere> <20070926162014.GA13737@fw.reifenberger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070926162014.GA13737@fw.reifenberger.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 16:35:59 -0000 On Wed, Sep 26, 2007 at 06:20:14PM +0200, Michael Reifenberger wrote: > That issue is fixed. Just looked at netbsd-iscsi-20070908 and it does look fixed in that version. Thanks, Craig From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 16:39:42 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 30B2D16A417 for ; Wed, 26 Sep 2007 16:39:42 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.10]) by mx1.freebsd.org (Postfix) with ESMTP id 07F6513C45D for ; Wed, 26 Sep 2007 16:39:41 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail01.m-online.net (mail.m-online.net [192.168.3.149]) by mail-out.m-online.net (Postfix) with ESMTP id A133F222DD7; Wed, 26 Sep 2007 18:20:15 +0200 (CEST) Received: from mail.reifenberger.com (ppp-82-135-66-60.dynamic.mnet-online.de [82.135.66.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTP id 91A8A90653; Wed, 26 Sep 2007 18:20:15 +0200 (CEST) Received: (from mike@localhost) by mail.reifenberger.com (8.13.8/8.13.8/Submit) id l8QGKE0W013765; Wed, 26 Sep 2007 18:20:14 +0200 (CEST) (envelope-from mike@reifenberger.com) X-Authentication-Warning: fw.reifenberger.com: mike set sender to mike@reifenberger.com using -f Date: Wed, 26 Sep 2007 18:20:14 +0200 From: Michael Reifenberger To: Craig Boston Message-ID: <20070926162014.GA13737@fw.reifenberger.com> References: <46F98972.80403@datapipe.com> <20070926150756.GA26578@nowhere> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070926150756.GA26578@nowhere> User-Agent: Mutt/1.4.2.2i Priority: normal Cc: freebsd-hackers@freebsd.org Subject: Re: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 16:39:42 -0000 Hi, ... > The other thing was that it was listening on a different port number > than the FreeBSD initiator was trying to connect to. For some reason > even though iscsi-target claims to have a "-p" option to specify the > port number, after reading the code it was clear that it doesn't > actually use that value for anything and instead is hardcoded to use > whatever is in /etc/services. > That issue is fixed. -- Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 18:22:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF87E16A421 for ; Wed, 26 Sep 2007 18:22:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outK.internet-mail-service.net (outK.internet-mail-service.net [216.240.47.234]) by mx1.freebsd.org (Postfix) with ESMTP id C5C3413C468 for ; Wed, 26 Sep 2007 18:22:52 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 26 Sep 2007 11:22:51 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 4F2E512650B; Wed, 26 Sep 2007 11:22:51 -0700 (PDT) Message-ID: <46FAA37B.3020903@elischer.org> Date: Wed, 26 Sep 2007 11:22:51 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "rsync.net" References: <20070925093722.N21960@mail.rsync.net> In-Reply-To: <20070925093722.N21960@mail.rsync.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 18:22:53 -0000 rsync.net wrote: > It has been impossible to change kern.ngroups - at least for several years > now. It was not fixed in either 5.x or 6.x : > > http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html > > It is seemingly a difficult problem: > > http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] > > However it should be solved - we can't be the only ones out there trying > to add a UID to more than 16 groups... the big question is what do you do for NFS? remember something about it only having a fixed storage for groups. > > > ----- > > > The rsync.net code bounties have been fairly successful this year - two of > the five projects have been completed, and the large "vmware 6 on FreeBSD" > project is now underway. > > We'd like to add a new bounty for this kern.ngroups issue. We are posting > to -hackers today to get some feedback on how long this will take and how > much money might reasonably be expected to lure this work. > > > --rsync.net Support > > > > [1] Is it indeed true that these programs are broken by not following > NGROUPS_MAX from syslimits.h? > _______________________________________________ > 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 Sep 26 18:42:02 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 557A016A419 for ; Wed, 26 Sep 2007 18:42:02 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchfe01.datapipe-corp.net (exchfe01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id 2AA9C13C48D for ; Wed, 26 Sep 2007 18:42:01 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from [192.168.131.233] (192.168.131.233) by exchfe01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server (TLS) id 8.0.730.1; Wed, 26 Sep 2007 14:42:01 -0400 Message-ID: <46FAA792.5000105@datapipe.com> Date: Wed, 26 Sep 2007 14:40:18 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.6 (X11/20070728) MIME-Version: 1.0 To: References: <46F98972.80403@datapipe.com> <20070926150756.GA26578@nowhere> <20070926162014.GA13737@fw.reifenberger.com> <20070926163558.GA76061@nowhere> In-Reply-To: <20070926163558.GA76061@nowhere> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 26 Sep 2007 18:42:02 -0000 Are they any other target ports available ? Does Open-iSCSI work ? Anyone working on it ? Craig Boston wrote: > On Wed, Sep 26, 2007 at 06:20:14PM +0200, Michael Reifenberger wrote: >> That issue is fixed. > > Just looked at netbsd-iscsi-20070908 and it does look fixed in that > version. > > Thanks, > Craig > _______________________________________________ > 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" -- Mark Saad Managed UNIX Support DataPipe Managed Global IT Services msaad@datapipe.com 1.201.792.4847 (international) 1.888.749.5821 (toll free) From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 21:00:46 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECA0716A417 for ; Wed, 26 Sep 2007 21:00:46 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outE.internet-mail-service.net (outE.internet-mail-service.net [216.240.47.228]) by mx1.freebsd.org (Postfix) with ESMTP id B705213C48D for ; Wed, 26 Sep 2007 21:00:46 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 26 Sep 2007 14:00:24 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id A5D59126503; Wed, 26 Sep 2007 14:00:23 -0700 (PDT) Message-ID: <46FAC866.5050602@elischer.org> Date: Wed, 26 Sep 2007 14:00:22 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "rsync.net" References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net> In-Reply-To: <20070926130845.U21960@mail.rsync.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 21:00:47 -0000 rsync.net wrote: > > On Wed, 26 Sep 2007, Julian Elischer wrote: > >> rsync.net wrote: >>> It has been impossible to change kern.ngroups - at least for several years >>> now. It was not fixed in either 5.x or 6.x : >>> >>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html >>> >>> It is seemingly a difficult problem: >>> >>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] >>> >>> However it should be solved - we can't be the only ones out there trying >>> to add a UID to more than 16 groups... >> the big question is what do you do for NFS? remember something about >> it only having a fixed storage for groups. > > > (snip) > > >>> [1] Is it indeed true that these programs are broken by not following >>> NGROUPS_MAX from syslimits.h? > > > Assuming the answer to the above footnote is "yes", would it be reasonable > to fix the OS generally, but continue to hard code the limits in things > like NFS ? > > Are you saying that, unlike other items, NFS _does_ respect NGROUPS_MAX ? actually it doesn't see: nfs/rpcv2.h:#define RPCAUTH_UNIXGIDS 16 but what do we do if a user has > 16? From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 21:30:27 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD43016A417 for ; Wed, 26 Sep 2007 21:30:27 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outF.internet-mail-service.net (outF.internet-mail-service.net [216.240.47.229]) by mx1.freebsd.org (Postfix) with ESMTP id 7C0EB13C458 for ; Wed, 26 Sep 2007 21:30:27 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.40) with ESMTP; Wed, 26 Sep 2007 14:30:26 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id A108D12650E; Wed, 26 Sep 2007 14:30:18 -0700 (PDT) Message-ID: <46FACF69.4070803@elischer.org> Date: Wed, 26 Sep 2007 14:30:17 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: "rsync.net" References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net> <46FAC866.5050602@elischer.org> <20070926141636.P21960@mail.rsync.net> In-Reply-To: <20070926141636.P21960@mail.rsync.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 21:30:27 -0000 rsync.net wrote: of more > than 16 groups, and that is currently impossible. > > We are happy to lend financial support to a solution ... however it sounds > like $500 and free rsync.net storage space isn't going to be sufficient ? > > Is it unexpected that someone has run into this limit ? no. Others have hit it, and the SAMBA group have asked us to fix it. just no-one has all three of: 1/ the ability. 2/ the time. 3/ the need. Linux recently changed this so we should probably just do the same as they did.. From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 08:08:54 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8363D16A419 for ; Thu, 27 Sep 2007 08:08:54 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id EEA0813C447 for ; Thu, 27 Sep 2007 08:08:52 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 5B2001B10F09; Thu, 27 Sep 2007 10:08:51 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on blah.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-104.4 required=5.0 tests=ALL_TRUSTED,BAYES_00, USER_IN_WHITELIST autolearn=ham version=3.2.3 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id A643A1B10EE8; Thu, 27 Sep 2007 10:08:48 +0200 (CEST) Message-ID: <46FB64FC.6050807@moneybookers.com> Date: Thu, 27 Sep 2007 11:08:28 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.6 (X11/20070918) MIME-Version: 1.0 To: Craig Boston References: <46F98972.80403@datapipe.com> <20070926150756.GA26578@nowhere> <20070926162014.GA13737@fw.reifenberger.com> <20070926163558.GA76061@nowhere> In-Reply-To: <20070926163558.GA76061@nowhere> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.91.2/4411/Wed Sep 26 23:43:35 2007 on blah.cmotd.com X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, Michael Reifenberger Subject: Re: iSCSI Target and raw devices X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 08:08:54 -0000 Hi, Craig Boston wrote: > On Wed, Sep 26, 2007 at 06:20:14PM +0200, Michael Reifenberger wrote: > >> That issue is fixed. >> > > Just looked at netbsd-iscsi-20070908 and it does look fixed in that > version. > Actually the fix was in FreeBSD's /etc/services :) so it's not exactly fix. I think the interesting part is to have support for raw devices :) > Thanks, > Craig > _______________________________________________ > 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" > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 08:32:07 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C05EA16A421 for ; Thu, 27 Sep 2007 08:32:07 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 7F49313C494 for ; Thu, 27 Sep 2007 08:32:07 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 196FC33C8B for ; Thu, 27 Sep 2007 10:16:12 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tCMSHqEm275d for ; Thu, 27 Sep 2007 10:16:08 +0200 (CEST) Received: from aurynmob2.giulioferro.it (unknown [192.168.114.15]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id C8B5833C82 for ; Thu, 27 Sep 2007 10:16:08 +0200 (CEST) Message-ID: <46FB66B8.2000704@zirakzigil.org> Date: Thu, 27 Sep 2007 10:15:52 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 08:32:07 -0000 What is the status of the work required by the vidia guys so that they can code their driver for amd64 architecture? From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 08:52:18 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83C8416A46D for ; Thu, 27 Sep 2007 08:52:18 +0000 (UTC) (envelope-from atom@smasher.org) Received: from atom.smasher.org (atom.smasher.org [69.55.237.145]) by mx1.freebsd.org (Postfix) with SMTP id 70EDE13C46A for ; Thu, 27 Sep 2007 08:52:18 +0000 (UTC) (envelope-from atom@smasher.org) Received: (qmail 74938 invoked by uid 1000); 27 Sep 2007 08:25:26 -0000 Message-ID: <20070927082526.74934.qmail@smasher.org> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Date: Thu, 27 Sep 2007 20:25:21 +1200 (NZST) From: Atom Smasher MIME-Version: 1.0 OpenPGP: id=0xB88D52E4D9F57808; algo=1 (RSA); size=4096; url=http://atom.smasher.org/pgp.txt To: freebsd-hackers@freebsd.org X-POM: The Moon is Full X-Hashcash: 1:20:0709270825:freebsd-hackers@freebsd.org::qAA4aSOZpIrGldvz:000000 0000000000000000000000001sH0 Subject: no console bell X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 08:52:18 -0000 i've got this laptop running great, but i haven't been able to get a console bell working on it. in the BIOS setup i can get a really loud beep from the mobo speaker (so i know it's there and working), but otherwise i can't get any sound from it. for a while i had 'device speaker' in the kernel and it produced a /dev/speaker with no complaints, but i couldn't get any sound out of it. not encouraging, but i booted up with ubuntu 7.04 i386 (live cd) and still couldn't get the console bell to beep. one theory is that the BIOS disables the speaker before booting. another theory is that freebsd (and ubuntu) just aren't finding the speaker. any ways to execute a shell script (mpg123) instead of the console bell? i can do that in mrxvt (bellCommand) but it only works if mrxvt rings the bell. any other ideas? thanks.... system: FreeBSD 6.2-RELEASE amd64 Acer Aspire 5100 - V2.70 kenv stuff: acpi_load="YES" hint.acpi.0.oem="ACRSYS" hint.acpi.0.revision="1" hint.acpi.0.rsdt="0x37e91b46" smbios.bios.reldate="12/07/2006" smbios.bios.vendor="Acer" smbios.bios.version="V2.70" smbios.chassis.maker="Acer" smbios.chassis.serial="xxx " smbios.chassis.tag=" " smbios.chassis.version="N/A" smbios.planar.maker="Acer" smbios.planar.product="Navarro" smbios.planar.serial="xxx" smbios.planar.version="N/A" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="Acer " smbios.system.product="Aspire 5100 " smbios.system.serial="xxx" smbios.system.uuid="xxx" smbios.system.version="V2.70" -- ...atom ________________________ http://atom.smasher.org/ 762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808 ------------------------------------------------- "The lie can be maintained only for such time as the State can shield the people from the political, economic and/or military consequences of the lie. It thus becomes vitally important for the State to use all of its powers to repress dissent, for the truth is the mortal enemy of the lie, and thus by extension, the truth becomes the greatest enemy of the State." -- Josef Goebbels From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 11:10:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4197516A418 for ; Thu, 27 Sep 2007 11:10:44 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (arm132.internetdsl.tpnet.pl [83.17.198.132]) by mx1.freebsd.org (Postfix) with ESMTP id D8FC813C4AC for ; Thu, 27 Sep 2007 11:10:43 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 2300F45F44; Thu, 27 Sep 2007 13:10:42 +0200 (CEST) Received: from localhost (pjd.wheel.pl [10.0.1.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 0CEC945E97; Thu, 27 Sep 2007 13:10:32 +0200 (CEST) Date: Thu, 27 Sep 2007 13:09:00 +0200 From: Pawel Jakub Dawidek To: "rsync.net" Message-ID: <20070927110900.GD1193@garage.freebsd.pl> References: <20070925093722.N21960@mail.rsync.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mR8QP4gmHujQHb1c" Content-Disposition: inline In-Reply-To: <20070925093722.N21960@mail.rsync.net> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 7.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-5.9 required=3.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:10:44 -0000 --mR8QP4gmHujQHb1c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Sep 25, 2007 at 09:51:06AM -0700, rsync.net wrote: >=20 > It has been impossible to change kern.ngroups - at least for several years > now. It was not fixed in either 5.x or 6.x : >=20 > http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html >=20 > It is seemingly a difficult problem: >=20 > http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] >=20 > However it should be solved - we can't be the only ones out there trying > to add a UID to more than 16 groups... >=20 >=20 > ----- >=20 >=20 > The rsync.net code bounties have been fairly successful this year - two of > the five projects have been completed, and the large "vmware 6 on FreeBSD" > project is now underway. >=20 > We'd like to add a new bounty for this kern.ngroups issue. We are posting > to -hackers today to get some feedback on how long this will take and how > much money might reasonably be expected to lure this work. >=20 >=20 > --rsync.net Support >=20 >=20 >=20 > [1] Is it indeed true that these programs are broken by not following > NGROUPS_MAX from syslimits.h? I don't see how they can be broken. They may not see more than 16 groups, but they shouldn't blow up. The only possibility of bad usage I see is something like this: gid_t gids[NGROUPS_MAX]; int gidsetlen; gidsetlen =3D getgroups(0, NULL); getgroups(gidsetlen, gids); But I guess the most common use is: gid_t gids[NGROUPS_MAX]; int gidsetlen; gidsetlen =3D getgroups(NGROUPS_MAX, gids); Binaries using the latter method should be just fine. BTW. The latter method is what all utilities from the base system use. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --mR8QP4gmHujQHb1c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFG+49MForvXbEpPzQRArKLAJwMvA85vNuEiUlKkFDO2qmbPkrvIgCfQiO2 LMGAyT+FfATQk1YIbG9Jy/w= =j8gH -----END PGP SIGNATURE----- --mR8QP4gmHujQHb1c-- From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 11:17:27 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6C0416A496 for ; Thu, 27 Sep 2007 11:17:27 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from cpanel03.rubas-s03.net (cpanel03.rubas-s03.net [195.182.222.73]) by mx1.freebsd.org (Postfix) with ESMTP id 85CE613C50C for ; Thu, 27 Sep 2007 11:17:27 +0000 (UTC) (envelope-from gahr@gahr.ch) Received: from town.bfh.ch ([147.87.98.171]) by cpanel03.rubas-s03.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1IarMx-0000Q9-SZ; Thu, 27 Sep 2007 13:17:23 +0200 Message-ID: <46FB913B.7070409@gahr.ch> Date: Thu, 27 Sep 2007 13:17:15 +0200 From: Pietro Cerutti User-Agent: Thunderbird 1.5.0.9 (X11/20070104) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <20070925093722.N21960@mail.rsync.net> <20070927110900.GD1193@garage.freebsd.pl> In-Reply-To: <20070927110900.GD1193@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - cpanel03.rubas-s03.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - gahr.ch X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-hackers@freebsd.org, "rsync.net" Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 11:17:28 -0000 Pawel Jakub Dawidek wrote: > On Tue, Sep 25, 2007 at 09:51:06AM -0700, rsync.net wrote: >> It has been impossible to change kern.ngroups - at least for several years >> now. It was not fixed in either 5.x or 6.x : >> >> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html >> >> It is seemingly a difficult problem: >> >> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] >> >> However it should be solved - we can't be the only ones out there trying >> to add a UID to more than 16 groups... >> >> >> ----- >> >> >> The rsync.net code bounties have been fairly successful this year - two of >> the five projects have been completed, and the large "vmware 6 on FreeBSD" >> project is now underway. >> >> We'd like to add a new bounty for this kern.ngroups issue. We are posting >> to -hackers today to get some feedback on how long this will take and how >> much money might reasonably be expected to lure this work. >> >> >> --rsync.net Support >> >> >> >> [1] Is it indeed true that these programs are broken by not following >> NGROUPS_MAX from syslimits.h? > > I don't see how they can be broken. They may not see more than 16 > groups, but they shouldn't blow up. The only possibility of bad usage I > see is something like this: > > gid_t gids[NGROUPS_MAX]; > int gidsetlen; > > gidsetlen = getgroups(0, NULL); > getgroups(gidsetlen, gids); > > But I guess the most common use is: > > gid_t gids[NGROUPS_MAX]; > int gidsetlen; > > gidsetlen = getgroups(NGROUPS_MAX, gids); > > Binaries using the latter method should be just fine. > BTW. The latter method is what all utilities from the base system use. > Anyway, why should we worry about possible breakage software written with a bad design? -- Pietro Cerutti PGP Public Key: http://gahr.ch/pgp From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 12:01:17 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A68716A419; Thu, 27 Sep 2007 12:01:17 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id 2D37913C474; Thu, 27 Sep 2007 12:01:16 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from knop-beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Sep 2007 13:47:58 +0200 Date: Thu, 27 Sep 2007 13:48:02 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt_h@knop-beagle.kn.op.dlr.de To: Pietro Cerutti In-Reply-To: <46FB913B.7070409@gahr.ch> Message-ID: <20070927133713.R63884@knop-beagle.kn.op.dlr.de> References: <20070925093722.N21960@mail.rsync.net> <20070927110900.GD1193@garage.freebsd.pl> <46FB913B.7070409@gahr.ch> X-OpenPGP-Key: harti@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 27 Sep 2007 11:47:59.0009 (UTC) FILETIME=[40452110:01C800FC] Cc: freebsd-hackers@freebsd.org, Pawel Jakub Dawidek , "rsync.net" Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 12:01:17 -0000 On Thu, 27 Sep 2007, Pietro Cerutti wrote: PC>Pawel Jakub Dawidek wrote: PC>> On Tue, Sep 25, 2007 at 09:51:06AM -0700, rsync.net wrote: PC>>> It has been impossible to change kern.ngroups - at least for several years PC>>> now. It was not fixed in either 5.x or 6.x : PC>>> PC>>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html PC>>> PC>>> It is seemingly a difficult problem: PC>>> PC>>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] PC>>> PC>>> However it should be solved - we can't be the only ones out there trying PC>>> to add a UID to more than 16 groups... PC>>> PC>>> PC>>> ----- PC>>> PC>>> PC>>> The rsync.net code bounties have been fairly successful this year - two of PC>>> the five projects have been completed, and the large "vmware 6 on FreeBSD" PC>>> project is now underway. PC>>> PC>>> We'd like to add a new bounty for this kern.ngroups issue. We are posting PC>>> to -hackers today to get some feedback on how long this will take and how PC>>> much money might reasonably be expected to lure this work. PC>>> PC>>> PC>>> --rsync.net Support PC>>> PC>>> PC>>> PC>>> [1] Is it indeed true that these programs are broken by not following PC>>> NGROUPS_MAX from syslimits.h? PC>> PC>> I don't see how they can be broken. They may not see more than 16 PC>> groups, but they shouldn't blow up. The only possibility of bad usage I PC>> see is something like this: PC>> PC>> gid_t gids[NGROUPS_MAX]; PC>> int gidsetlen; PC>> PC>> gidsetlen = getgroups(0, NULL); PC>> getgroups(gidsetlen, gids); PC>> PC>> But I guess the most common use is: PC>> PC>> gid_t gids[NGROUPS_MAX]; PC>> int gidsetlen; PC>> PC>> gidsetlen = getgroups(NGROUPS_MAX, gids); PC>> PC>> Binaries using the latter method should be just fine. PC>> BTW. The latter method is what all utilities from the base system use. PC>> PC> PC>Anyway, why should we worry about possible breakage software written PC>with a bad design? We should worry about all software in the base system. Especially if the implications are security related. BTW - the software is not necessary bad designed - it may just be old. There are things to think about: in several places the group list would be truncated: NFS, struct ucred, struct xucred, struct kinfo_proc, struct cmsgcred (this is just from a grep in include/sys). Truncating is ok as long as you use group membership only to give access to a ressource - the user will just not be able to access a ressource that in principle he should be able to access. Unfortunately someone in the past thought that making negative decisions based on group membership would be a nice thing (prominent example: NTFS). Here truncating the group list has the effect of giving access to resource the user should have no access to. I don't think the brain-dead concept of deny groups is used anywhere in the base system, but applications certainly could use it and in this case surprises are just waiting to pop up by ignoring the truncation problem. harti From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 16:55:41 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9EE8F16A417 for ; Wed, 26 Sep 2007 16:55:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.176]) by mx1.freebsd.org (Postfix) with ESMTP id 79B7C13C45A for ; Wed, 26 Sep 2007 16:55:41 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by el-out-1112.google.com with SMTP id r27so439361ele for ; Wed, 26 Sep 2007 09:55:40 -0700 (PDT) Received: by 10.114.131.9 with SMTP id e9mr1253822wad.1190825739631; Wed, 26 Sep 2007 09:55:39 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Wed, 26 Sep 2007 09:55:39 -0700 (PDT) Message-ID: Date: Wed, 26 Sep 2007 12:55:39 -0400 From: "Benjie Chen" To: "Ivan Voras" , "Kris Kennaway" In-Reply-To: <9bbcef730709241211o479e3e5dwf64382596c837dfb@mail.gmail.com> MIME-Version: 1.0 References: <9bbcef730709241211o479e3e5dwf64382596c837dfb@mail.gmail.com> X-Mailman-Approved-At: Thu, 27 Sep 2007 12:09:16 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 16:55:41 -0000 We got this bt after setting kernel dump stuff up. For some reason kgdb did not find debugging symbols, even though the kernel was compiled with -g. Hopefully this helps and I will go dig some more to find why we don't have a debug symbol. #0 0xc0674fae in doadump () #1 0xc067550a in boot () #2 0xc0675831 in panic () #3 0xc088e29c in trap_fatal () #4 0xc088da0e in trap () #5 0xc0879d4a in calltrap () #6 0xc066c731 in _mtx_lock_sleep () #7 0xc06bba96 in unp_gc () #8 0xc06961b3 in taskqueue_run () #9 0xc0696696 in taskqueue_thread_loop () #10 0xc065ec4d in fork_exit () #11 0xc0879dac in fork_trampoline () On 9/24/07, Ivan Voras wrote: > > On 24/09/2007, Benjie Chen wrote: > > Ivan and Kris, > > > > I will try to get a kernel trace -- it may not happen for awhile since I > am > > not in the office and working remotely for awhile so it may not be easy > to > > get a trace... but I will check. > > It's fairly easy: > > 1) add lines like the following in rc.conf: > dumpdev="/dev/amrd0s1b" > dumpdir="/storage1/crashdumps" > > (dumpdev is your swap partition, which must be larger than your RAM, > dumpdir is where the crash dumps will be saved, also needs to be > larger than RAM) > > 2) add these lines to sysctl.conf: > > debug.debugger_on_panic=0 > debug.trace_on_panic=1 > > (These will cause the panic message and backtrace to be automatically > recorded in the message buffer saved to the kernel crash dump. If not > told otherwise, the machine will then reboot and at the next boot > generate a crash dump in your dumpdir. When you get the kernel crash > dump, run "kgdb vmcore.0 /boot/kernel/kernel" as root and then you can > inspect the trace, core dump, etc. You don't need any special > knowledge of (k)gdb for this. The one useful command to you may be > "bt" - generate a backtrace). > > > It looks like the problem reported by that link, and some of the links > from > > there though... > > I'm trying to solve that one with Craig Rodrigues. So far it's been > without success but we know where the problem is. > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 19:21:06 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 291E816A41A for ; Wed, 26 Sep 2007 19:21:06 +0000 (UTC) (envelope-from benjie@addgene.org) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.235]) by mx1.freebsd.org (Postfix) with ESMTP id 4DB6B13C461 for ; Wed, 26 Sep 2007 19:21:01 +0000 (UTC) (envelope-from benjie@addgene.org) Received: by wr-out-0506.google.com with SMTP id 70so884037wra for ; Wed, 26 Sep 2007 12:21:00 -0700 (PDT) Received: by 10.114.199.1 with SMTP id w1mr1486507waf.1190834459139; Wed, 26 Sep 2007 12:20:59 -0700 (PDT) Received: by 10.114.15.16 with HTTP; Wed, 26 Sep 2007 12:20:59 -0700 (PDT) Message-ID: Date: Wed, 26 Sep 2007 15:20:59 -0400 From: "Benjie Chen" To: "Ivan Voras" , "Kris Kennaway" In-Reply-To: MIME-Version: 1.0 References: <9bbcef730709241211o479e3e5dwf64382596c837dfb@mail.gmail.com> X-Mailman-Approved-At: Thu, 27 Sep 2007 12:09:16 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 19:21:06 -0000 Sorry to waste your time. I discovered a similar PR with unp_gc and there may be a patch already. I will see if that works. Thanks, Benjie On 9/26/07, Benjie Chen wrote: > > We got this bt after setting kernel dump stuff up. For some reason kgdb > did not find debugging symbols, even though the kernel was compiled with -g. > Hopefully this helps and I will go dig some more to find why we don't have a > debug symbol. > > #0 0xc0674fae in doadump () > #1 0xc067550a in boot () > #2 0xc0675831 in panic () > #3 0xc088e29c in trap_fatal () > #4 0xc088da0e in trap () > #5 0xc0879d4a in calltrap () > #6 0xc066c731 in _mtx_lock_sleep () > #7 0xc06bba96 in unp_gc () > #8 0xc06961b3 in taskqueue_run () > #9 0xc0696696 in taskqueue_thread_loop () > #10 0xc065ec4d in fork_exit () > #11 0xc0879dac in fork_trampoline () > > > > > On 9/24/07, Ivan Voras wrote: > > > > On 24/09/2007, Benjie Chen wrote: > > > Ivan and Kris, > > > > > > I will try to get a kernel trace -- it may not happen for awhile since > > I am > > > not in the office and working remotely for awhile so it may not be > > easy to > > > get a trace... but I will check. > > > > It's fairly easy: > > > > 1) add lines like the following in rc.conf: > > dumpdev="/dev/amrd0s1b" > > dumpdir="/storage1/crashdumps" > > > > (dumpdev is your swap partition, which must be larger than your RAM, > > dumpdir is where the crash dumps will be saved, also needs to be > > larger than RAM) > > > > 2) add these lines to sysctl.conf: > > > > debug.debugger_on_panic=0 > > debug.trace_on_panic=1 > > > > (These will cause the panic message and backtrace to be automatically > > recorded in the message buffer saved to the kernel crash dump. If not > > told otherwise, the machine will then reboot and at the next boot > > generate a crash dump in your dumpdir. When you get the kernel crash > > dump, run "kgdb vmcore.0 /boot/kernel/kernel" as root and then you can > > inspect the trace, core dump, etc. You don't need any special > > knowledge of (k)gdb for this. The one useful command to you may be > > "bt" - generate a backtrace). > > > > > It looks like the problem reported by that link, and some of the links > > from > > > there though... > > > > I'm trying to solve that one with Craig Rodrigues. So far it's been > > without success but we know where the problem is. > > > > > > -- > Benjie Chen, Ph.D. > Addgene, a better way to share plasmids > www.addgene.org > -- Benjie Chen, Ph.D. Addgene, a better way to share plasmids www.addgene.org From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 20:02:37 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BFBD016A41B for ; Wed, 26 Sep 2007 20:02:37 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mx1.freebsd.org (Postfix) with ESMTP id A729013C468 for ; Wed, 26 Sep 2007 20:02:37 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mail.rsync.net (8.12.11/8.12.11) with ESMTP id l8QKBMtf065461; Wed, 26 Sep 2007 13:11:22 -0700 (PDT) (envelope-from info@rsync.net) Received: from localhost (info@localhost) by mail.rsync.net (8.12.11/8.12.11/Submit) with ESMTP id l8QKBMmI065458; Wed, 26 Sep 2007 13:11:22 -0700 (PDT) (envelope-from info@rsync.net) X-Authentication-Warning: mail.rsync.net: info owned process doing -bs Date: Wed, 26 Sep 2007 13:11:22 -0700 (PDT) From: "rsync.net" To: Julian Elischer In-Reply-To: <46FAA37B.3020903@elischer.org> Message-ID: <20070926130845.U21960@mail.rsync.net> References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 27 Sep 2007 12:09:16 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 20:02:37 -0000 On Wed, 26 Sep 2007, Julian Elischer wrote: > rsync.net wrote: > > It has been impossible to change kern.ngroups - at least for several years > > now. It was not fixed in either 5.x or 6.x : > > > > http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html > > > > It is seemingly a difficult problem: > > > > http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] > > > > However it should be solved - we can't be the only ones out there trying > > to add a UID to more than 16 groups... > > the big question is what do you do for NFS? remember something about > it only having a fixed storage for groups. (snip) > > [1] Is it indeed true that these programs are broken by not following > > NGROUPS_MAX from syslimits.h? Assuming the answer to the above footnote is "yes", would it be reasonable to fix the OS generally, but continue to hard code the limits in things like NFS ? Are you saying that, unlike other items, NFS _does_ respect NGROUPS_MAX ? From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 26 21:12:31 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6B2616A419 for ; Wed, 26 Sep 2007 21:12:31 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mx1.freebsd.org (Postfix) with ESMTP id C45FE13C45B for ; Wed, 26 Sep 2007 21:12:31 +0000 (UTC) (envelope-from info@rsync.net) Received: from mail.rsync.net (mail.rsync.net [69.43.165.11]) by mail.rsync.net (8.12.11/8.12.11) with ESMTP id l8QLL3Qe071115; Wed, 26 Sep 2007 14:21:03 -0700 (PDT) (envelope-from info@rsync.net) Received: from localhost (info@localhost) by mail.rsync.net (8.12.11/8.12.11/Submit) with ESMTP id l8QLL3Cl071112; Wed, 26 Sep 2007 14:21:03 -0700 (PDT) (envelope-from info@rsync.net) X-Authentication-Warning: mail.rsync.net: info owned process doing -bs Date: Wed, 26 Sep 2007 14:21:03 -0700 (PDT) From: "rsync.net" To: Julian Elischer In-Reply-To: <46FAC866.5050602@elischer.org> Message-ID: <20070926141636.P21960@mail.rsync.net> References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net> <46FAC866.5050602@elischer.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Thu, 27 Sep 2007 12:09:16 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Sep 2007 21:12:32 -0000 On Wed, 26 Sep 2007, Julian Elischer wrote: > >> rsync.net wrote: > >>> It has been impossible to change kern.ngroups - at least for several years > >>> now. It was not fixed in either 5.x or 6.x : > >>> > >>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html > >>> > >>> It is seemingly a difficult problem: > >>> > >>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] > >>> > >>> However it should be solved - we can't be the only ones out there trying > >>> to add a UID to more than 16 groups... > >> the big question is what do you do for NFS? remember something about > >> it only having a fixed storage for groups. > > > > > > (snip) > > > > > >>> [1] Is it indeed true that these programs are broken by not following > >>> NGROUPS_MAX from syslimits.h? > > > > > > Assuming the answer to the above footnote is "yes", would it be reasonable > > to fix the OS generally, but continue to hard code the limits in things > > like NFS ? > > > > Are you saying that, unlike other items, NFS _does_ respect NGROUPS_MAX ? > > actually it doesn't > > see: > > nfs/rpcv2.h:#define RPCAUTH_UNIXGIDS 16 > > but what do we do if a user has > 16? We have no idea. All we know is, we need some UIDs to be members of more than 16 groups, and that is currently impossible. We are happy to lend financial support to a solution ... however it sounds like $500 and free rsync.net storage space isn't going to be sufficient ? Is it unexpected that someone has run into this limit ? From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 12:46:04 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 841CA16A419 for ; Thu, 27 Sep 2007 12:46:04 +0000 (UTC) (envelope-from agh@tpg.com.au) Received: from mail9.tpgi.com.au (smtp9.tpgi.com.au [220.244.226.119]) by mx1.freebsd.org (Postfix) with ESMTP id 1484E13C447 for ; Thu, 27 Sep 2007 12:46:03 +0000 (UTC) (envelope-from agh@tpg.com.au) X-TPG-Antivirus: Passed Received: from localhost.madcat (123-243-254-144.static.tpgi.com.au [123.243.254.144] (may be forged)) by mail9.tpgi.com.au (envelope-from agh@tpg.com.au) (8.13.6/8.13.6) with ESMTP id l8RCTc9J004293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Sep 2007 22:29:45 +1000 From: Alastair Hogge To: freebsd-hackers@freebsd.org Date: Thu, 27 Sep 2007 22:33:54 +1000 User-Agent: KMail/1.9.7 References: <46FB66B8.2000704@zirakzigil.org> In-Reply-To: <46FB66B8.2000704@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709272233.54689.agh@tpg.com.au> Cc: Giulio Ferro Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 12:46:04 -0000 On Thu, 27 Sep 2007 18:15:52 Giulio Ferro wrote: > What is the status of the work required by the vidia guys > so that they can code their driver for amd64 architecture? Hey, There is no driver. Status can be found here: http://wiki.freebsd.org/NvidiaFeatureRequests Also you can find more info on the nvnews FreeBSD fourms. -Alastair From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 12:58:42 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFB6716A417 for ; Thu, 27 Sep 2007 12:58:42 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 6BCF313C461 for ; Thu, 27 Sep 2007 12:58:42 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 6B91233C45; Thu, 27 Sep 2007 14:58:52 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zh-Fa--MJfyq; Thu, 27 Sep 2007 14:58:48 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id E3F7C33C42; Thu, 27 Sep 2007 14:58:48 +0200 (CEST) Message-ID: <46FBA8F7.80305@zirakzigil.org> Date: Thu, 27 Sep 2007 14:58:31 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: Alastair Hogge , freebsd-hackers@freebsd.org References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> In-Reply-To: <200709272233.54689.agh@tpg.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 12:58:42 -0000 Alastair Hogge wrote: > On Thu, 27 Sep 2007 18:15:52 Giulio Ferro wrote: > >> What is the status of the work required by the vidia guys >> so that they can code their driver for amd64 architecture? >> > Hey, > > There is no driver. I sort of surmised that already... > Status can be found here: > http://wiki.freebsd.org/NvidiaFeatureRequests > Also you can find more info on the nvnews FreeBSD fourms. > > So, we are still years away from seeing a working nvidia driver, by the look of it... From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 13:07:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D23D116A420 for ; Thu, 27 Sep 2007 13:07:52 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 8163613C468 for ; Thu, 27 Sep 2007 13:07:52 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 04B7633C45; Thu, 27 Sep 2007 15:08:03 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kvVSVACbTMea; Thu, 27 Sep 2007 15:07:59 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id A917A33C42; Thu, 27 Sep 2007 15:07:59 +0200 (CEST) Message-ID: <46FBAB1E.8060103@zirakzigil.org> Date: Thu, 27 Sep 2007 15:07:42 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> In-Reply-To: <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:07:52 -0000 Sam Fourman Jr. wrote: >>> There is no driver. >>> >> I sort of surmised that already... >> >> >> So, we are still years away from seeing a working nvidia driver, >> by the look of it... >> > > I guess what I am confused about, is there someone actively working on > the Nvidia requests, or does a capable individual need to take the > lead on this project? > > And that's exactly what I'd very much like to know... From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 13:28:33 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E112A16A418 for ; Thu, 27 Sep 2007 13:28:33 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.251]) by mx1.freebsd.org (Postfix) with ESMTP id A238113C455 for ; Thu, 27 Sep 2007 13:28:33 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so579425anc for ; Thu, 27 Sep 2007 06:28:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=eeMU9u3Dh68lF5XWzhWfvUVtmwVNXrjQ0rhxQm//JlU=; b=RDFflDje1dJ5euHh2sY1M+c9p6ldGwpPn/OS6dHRLNrv9huRxx/ZGKiacJ+DBI8amd4mbzZ5SLtQmqTAp5/AqPWoAT/YPJ4Pm/z4nztDLsj2rc/hLqUh87CD6GvhooTbOLV6nIljeVjkyzaNDhg70WWmgWrIsFVMvygA9rPh8AI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZdhRDWmJ8jPPSoCuEQAIbLTHWm5FDzhPM8YkShAyhoK0ths0NFEKnnHvsVcCdEeHhwaB6cSSj4UO4YMi1VmZSOvxzIhz6XbcoYSoSFjrikRaiNw+T1xC+y0kKnNbMzOK6Z4YrbpnUJXv6nEZQ/cUv7Egb1Pw4twVzykwCdyCfDc= Received: by 10.140.191.14 with SMTP id o14mr818929rvf.1190898131655; Thu, 27 Sep 2007 06:02:11 -0700 (PDT) Received: by 10.86.91.5 with HTTP; Thu, 27 Sep 2007 06:02:11 -0700 (PDT) Message-ID: <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> Date: Thu, 27 Sep 2007 08:02:11 -0500 From: "Sam Fourman Jr." To: "Giulio Ferro" In-Reply-To: <46FBA8F7.80305@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> Cc: freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:28:34 -0000 On 9/27/07, Giulio Ferro wrote: > Alastair Hogge wrote: > > On Thu, 27 Sep 2007 18:15:52 Giulio Ferro wrote: > > > >> What is the status of the work required by the vidia guys > >> so that they can code their driver for amd64 architecture? > >> > > Hey, > > > > There is no driver. > I sort of surmised that already... > > > > Status can be found here: > > http://wiki.freebsd.org/NvidiaFeatureRequests > > Also you can find more info on the nvnews FreeBSD fourms. > > > > > > > So, we are still years away from seeing a working nvidia driver, > by the look of it... I guess what I am confused about, is there someone actively working on the Nvidia requests, or does a capable individual need to take the lead on this project? Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 13:35:49 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DDA616A49C for ; Thu, 27 Sep 2007 13:35:49 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from guardian.elvandar.org (evilcoder.xs4all.nl [195.64.94.120]) by mx1.freebsd.org (Postfix) with ESMTP id D7B2513C4C5 for ; Thu, 27 Sep 2007 13:35:48 +0000 (UTC) (envelope-from remko@elvandar.org) Received: by guardian.elvandar.org (Postfix, from userid 1001) id E7E4A7EDEB3; Thu, 27 Sep 2007 15:19:35 +0200 (CEST) Date: Thu, 27 Sep 2007 15:19:35 +0200 From: Remko Lodder To: Giulio Ferro Message-ID: <20070927131935.GD1421@elvandar.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FBAB1E.8060103@zirakzigil.org> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:35:49 -0000 On Thu, Sep 27, 2007 at 03:07:42PM +0200, Giulio Ferro wrote: > Sam Fourman Jr. wrote: > >>> There is no driver. > >>> > >> I sort of surmised that already... > >> > >> > >> So, we are still years away from seeing a working nvidia driver, > >> by the look of it... > >> > > > > I guess what I am confused about, is there someone actively working on > > the Nvidia requests, or does a capable individual need to take the > > lead on this project? > > > > > And that's exactly what I'd very much like to know... > _______________________________________________ >From what I know and what I can see; there is nobody actively working in this region to get the things fixed to get this far. Ofcourse like rsync.net you are free to sponsor these items if they are really important to you, without that, do notice that people do this in their own free time, which could either take some time before it's there, or might not be interesting enough to work on currently (because of other things at work, private life other code etc). It's not a matter of a capable individual taking the lead, it's a matter of having someone capable enough working on this for some time, which can be achieved by sponsoring that capable person for example. Cheers remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 13:38:04 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB8B516A417; Thu, 27 Sep 2007 13:38:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id CFE8713C44B; Thu, 27 Sep 2007 13:38:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 7FFFE1A4D94; Thu, 27 Sep 2007 06:38:03 -0700 (PDT) From: John Baldwin To: freebsd-hackers@freebsd.org, Harti Brandt Date: Thu, 27 Sep 2007 09:26:31 -0400 User-Agent: KMail/1.9.7 References: <20070925093722.N21960@mail.rsync.net> <46FB913B.7070409@gahr.ch> <20070927133713.R63884@knop-beagle.kn.op.dlr.de> In-Reply-To: <20070927133713.R63884@knop-beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709270926.31739.jhb@freebsd.org> Cc: Pawel Jakub Dawidek , "rsync.net" , Pietro Cerutti Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:38:05 -0000 On Thursday 27 September 2007 07:48:02 am Harti Brandt wrote: > On Thu, 27 Sep 2007, Pietro Cerutti wrote: > > PC>Pawel Jakub Dawidek wrote: > PC>> On Tue, Sep 25, 2007 at 09:51:06AM -0700, rsync.net wrote: > PC>>> It has been impossible to change kern.ngroups - at least for several years > PC>>> now. It was not fixed in either 5.x or 6.x : > PC>>> > PC>>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html > PC>>> > PC>>> It is seemingly a difficult problem: > PC>>> > PC>>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] > PC>>> > PC>>> However it should be solved - we can't be the only ones out there trying > PC>>> to add a UID to more than 16 groups... > PC>>> > PC>>> > PC>>> ----- > PC>>> > PC>>> > PC>>> The rsync.net code bounties have been fairly successful this year - two of > PC>>> the five projects have been completed, and the large "vmware 6 on FreeBSD" > PC>>> project is now underway. > PC>>> > PC>>> We'd like to add a new bounty for this kern.ngroups issue. We are posting > PC>>> to -hackers today to get some feedback on how long this will take and how > PC>>> much money might reasonably be expected to lure this work. > PC>>> > PC>>> > PC>>> --rsync.net Support > PC>>> > PC>>> > PC>>> > PC>>> [1] Is it indeed true that these programs are broken by not following > PC>>> NGROUPS_MAX from syslimits.h? > PC>> > PC>> I don't see how they can be broken. They may not see more than 16 > PC>> groups, but they shouldn't blow up. The only possibility of bad usage I > PC>> see is something like this: > PC>> > PC>> gid_t gids[NGROUPS_MAX]; > PC>> int gidsetlen; > PC>> > PC>> gidsetlen = getgroups(0, NULL); > PC>> getgroups(gidsetlen, gids); > PC>> > PC>> But I guess the most common use is: > PC>> > PC>> gid_t gids[NGROUPS_MAX]; > PC>> int gidsetlen; > PC>> > PC>> gidsetlen = getgroups(NGROUPS_MAX, gids); > PC>> > PC>> Binaries using the latter method should be just fine. > PC>> BTW. The latter method is what all utilities from the base system use. > PC>> > PC> > PC>Anyway, why should we worry about possible breakage software written > PC>with a bad design? > > We should worry about all software in the base system. Especially if the > implications are security related. BTW - the software is not necessary bad > designed - it may just be old. > > There are things to think about: in several places the group list would be > truncated: NFS, struct ucred, struct xucred, struct kinfo_proc, struct > cmsgcred (this is just from a grep in include/sys). Truncating is ok as > long as you use group membership only to give access to a ressource - the > user will just not be able to access a ressource that in principle he > should be able to access. Unfortunately someone in the past thought that > making negative decisions based on group membership would be a nice thing > (prominent example: NTFS). Here truncating the group list has the effect > of giving access to resource the user should have no access to. I don't > think the brain-dead concept of deny groups is used anywhere in the base > system, but applications certainly could use it and in this case surprises > are just waiting to pop up by ignoring the truncation problem. And some sysadmins may use it via 'chmod 606' or the like. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 13:38:05 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D490C16A420 for ; Thu, 27 Sep 2007 13:38:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id C8CB313C455 for ; Thu, 27 Sep 2007 13:38:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by elvis.mu.org (Postfix) with ESMTP id 6ACBB1A4D98; Thu, 27 Sep 2007 06:38:05 -0700 (PDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Thu, 27 Sep 2007 09:28:30 -0400 User-Agent: KMail/1.9.7 References: <46FB66B8.2000704@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> In-Reply-To: <46FBAB1E.8060103@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709270928.31576.jhb@freebsd.org> Cc: "Sam Fourman Jr." , Giulio Ferro , Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 13:38:05 -0000 On Thursday 27 September 2007 09:07:42 am Giulio Ferro wrote: > Sam Fourman Jr. wrote: > >>> There is no driver. > >>> > >> I sort of surmised that already... > >> > >> > >> So, we are still years away from seeing a working nvidia driver, > >> by the look of it... > >> > > > > I guess what I am confused about, is there someone actively working on > > the Nvidia requests, or does a capable individual need to take the > > lead on this project? > > > > > And that's exactly what I'd very much like to know... I don't think anyone is currently working on this at the moment. I was hoping that the superpages work would have been in the tree by now as it would have helped with some of the pending issues. -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 14:05:39 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7974316A419 for ; Thu, 27 Sep 2007 14:05:39 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 1756513C480 for ; Thu, 27 Sep 2007 14:05:39 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 710CF33C83; Thu, 27 Sep 2007 16:05:49 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8P98bmEjlIU8; Thu, 27 Sep 2007 16:05:46 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 5ED6133C41; Thu, 27 Sep 2007 16:05:46 +0200 (CEST) Message-ID: <46FBB8A8.1050202@zirakzigil.org> Date: Thu, 27 Sep 2007 16:05:28 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: Remko Lodder References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> In-Reply-To: <20070927131935.GD1421@elvandar.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:05:39 -0000 Remko Lodder wrote: > without that, do notice that people do this in their own free time, which > could either take some time before it's there, or might not be interesting > enough to work on currently (because of other things at work, private life > other code etc). > > To say that there isn't enough interest in the nvidia driver would be outrageous. The lack of a amd64 nvidia driver currently the first cause that makes desktop users like myself prefer other operating systems to freebsd. I'm still using fb, of course, because on the whole it's still worth it. But I'm not happy about it (the nv driver doesn't work on the 8600M GT, so I'm forced to use the dumb vesa driver)... There's a lot of projects going on, and I appreciate it, but I can't help thinking that maybe some developers should consider this a priority as much as many of us users do... From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 14:14:32 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A04CF16A417 for ; Thu, 27 Sep 2007 14:14:32 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from guardian.elvandar.org (evilcoder.xs4all.nl [195.64.94.120]) by mx1.freebsd.org (Postfix) with ESMTP id 5EF2613C474 for ; Thu, 27 Sep 2007 14:14:32 +0000 (UTC) (envelope-from remko@elvandar.org) Received: by guardian.elvandar.org (Postfix, from userid 1001) id 8672A7EDEB3; Thu, 27 Sep 2007 16:14:31 +0200 (CEST) Date: Thu, 27 Sep 2007 16:14:31 +0200 From: Remko Lodder To: Giulio Ferro Message-ID: <20070927141431.GF1421@elvandar.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FBB8A8.1050202@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FBB8A8.1050202@zirakzigil.org> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:14:32 -0000 On Thu, Sep 27, 2007 at 04:05:28PM +0200, Giulio Ferro wrote: > Remko Lodder wrote: > > without that, do notice that people do this in their own free time, which > > could either take some time before it's there, or might not be interesting > > enough to work on currently (because of other things at work, private life > > other code etc). > > > > > To say that there isn't enough interest in the nvidia driver would > be outrageous. The lack of a amd64 nvidia driver currently the first > cause that makes desktop users like myself prefer other operating > systems to freebsd. I'm still using fb, of course, because on the whole > it's still worth it. But I'm not happy about it (the nv driver doesn't work > on the 8600M GT, so I'm forced to use the dumb vesa driver)... > > There's a lot of projects going on, and I appreciate it, but I can't help > thinking that maybe some developers should consider this a priority as much > as many of us users do... Well the problem here imo (I am speaking for myself here, as well as in my previous reply) is that -you- cannot set the priorities for our developers unless you pay the developer to just that what you want to have. For you the AMD64 driver of the Nvidia GPU's might be interesting for someone else it isn't, you might or might not like that but interests can go a whole round and every step in that circle means a different interest. You and indeed a lot of others think it would be beneficial to have, but so far nobody stepped up who had enough time or interest or whatever to do this, if you all make a bounty for this or try something else to get this covered, I am pretty sure at least someone will do it (sometime). It's unfair from you to -demand- something from a volunteer project with software that you are free to use, or rather from developers' free time while you are seemingly not willing to spend your own free time on it (I would get the same reponse from you if I were to ask you to paint my entire house for nothing (and you are the one paying for the paint) where the house is a huge castle). So, if you want this really bad, and others as well, consider my above reasoning, till that time, we (including myself indeed) can only hope that at some point somebody has enough time and interest to start and finish this project. Cheers remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 14:25:59 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBA3316A419 for ; Thu, 27 Sep 2007 14:25:59 +0000 (UTC) (envelope-from joel@FreeBSD.org) Received: from swip.net (mailfe08.swip.net [212.247.154.225]) by mx1.freebsd.org (Postfix) with ESMTP id 5264313C461 for ; Thu, 27 Sep 2007 14:25:59 +0000 (UTC) (envelope-from joel@FreeBSD.org) X-Cloudmark-Score: 0.000000 [] Received: from [81.233.61.198] (account mj571680@tele2.se HELO [192.168.0.112]) by mailfe08.swip.net (CommuniGate Pro SMTP 5.1.10) with ESMTPA id 626325071; Thu, 27 Sep 2007 15:25:57 +0200 From: Joel Dahl To: Giulio Ferro In-Reply-To: <46FBAB1E.8060103@zirakzigil.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> Content-Type: text/plain Date: Thu, 27 Sep 2007 15:25:56 +0200 Message-Id: <1190899556.1148.1.camel@jesus.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.10.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:25:59 -0000 On Thu, 2007-09-27 at 15:07 +0200, Giulio Ferro wrote: > Sam Fourman Jr. wrote: > >>> There is no driver. > >>> > >> I sort of surmised that already... > >> > >> > >> So, we are still years away from seeing a working nvidia driver, > >> by the look of it... > >> > > > > I guess what I am confused about, is there someone actively working on > > the Nvidia requests, or does a capable individual need to take the > > lead on this project? > > > > > And that's exactly what I'd very much like to know... We have no developer actively working on it right now (AFAIK of course). -- Joel From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 14:44:43 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24BF716A417 for ; Thu, 27 Sep 2007 14:44:43 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id CFE4313C45A for ; Thu, 27 Sep 2007 14:44:42 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 2F86F20A2; Thu, 27 Sep 2007 16:44:36 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 1C816209E; Thu, 27 Sep 2007 16:44:36 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 0690A8448A; Thu, 27 Sep 2007 16:44:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Giulio Ferro References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FBB8A8.1050202@zirakzigil.org> Date: Thu, 27 Sep 2007 16:44:35 +0200 In-Reply-To: <46FBB8A8.1050202@zirakzigil.org> (Giulio Ferro's message of "Thu\, 27 Sep 2007 16\:05\:28 +0200") Message-ID: <86wsucp3qk.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:44:43 -0000 Giulio Ferro writes: > To say that there isn't enough interest in the nvidia driver would be > outrageous. No, it would be true. If there were enough interest, someone would have stepped up to the plate to implement the required features. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 14:58:24 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1F1C116A41A for ; Thu, 27 Sep 2007 14:58:24 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from smtp-1.dlr.de (smtp-1.dlr.de [195.37.61.185]) by mx1.freebsd.org (Postfix) with ESMTP id 93C1A13C478 for ; Thu, 27 Sep 2007 14:58:23 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from knop-beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Thu, 27 Sep 2007 16:58:21 +0200 Date: Thu, 27 Sep 2007 16:58:21 +0200 (CEST) From: Harti Brandt X-X-Sender: brandt_h@knop-beagle.kn.op.dlr.de To: "rsync.net" In-Reply-To: <20070926141636.P21960@mail.rsync.net> Message-ID: <20070927165321.A63884@knop-beagle.kn.op.dlr.de> References: <20070925093722.N21960@mail.rsync.net> <46FAA37B.3020903@elischer.org> <20070926130845.U21960@mail.rsync.net> <46FAC866.5050602@elischer.org> <20070926141636.P21960@mail.rsync.net> X-OpenPGP-Key: harti@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 27 Sep 2007 14:58:21.0222 (UTC) FILETIME=[D8708460:01C80116] Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups (non) setting ... new bounty ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 14:58:24 -0000 On Wed, 26 Sep 2007, rsync.net wrote: r> r> r>On Wed, 26 Sep 2007, Julian Elischer wrote: r> r>> >> rsync.net wrote: r>> >>> It has been impossible to change kern.ngroups - at least for several years r>> >>> now. It was not fixed in either 5.x or 6.x : r>> >>> r>> >>> http://lists.freebsd.org/pipermail/freebsd-bugs/2007-January/022140.html r>> >>> r>> >>> It is seemingly a difficult problem: r>> >>> r>> >>> http://www.atm.tut.fi/list-archive/freebsd-stable/msg09969.html [1] r>> >>> r>> >>> However it should be solved - we can't be the only ones out there trying r>> >>> to add a UID to more than 16 groups... r>> >> the big question is what do you do for NFS? remember something about r>> >> it only having a fixed storage for groups. r>> > r>> > r>> > (snip) r>> > r>> > r>> >>> [1] Is it indeed true that these programs are broken by not following r>> >>> NGROUPS_MAX from syslimits.h? r>> > r>> > r>> > Assuming the answer to the above footnote is "yes", would it be reasonable r>> > to fix the OS generally, but continue to hard code the limits in things r>> > like NFS ? r>> > r>> > Are you saying that, unlike other items, NFS _does_ respect NGROUPS_MAX ? r>> r>> actually it doesn't r>> r>> see: r>> r>> nfs/rpcv2.h:#define RPCAUTH_UNIXGIDS 16 r>> r>> but what do we do if a user has > 16? r> r> r>We have no idea. All we know is, we need some UIDs to be members of more r>than 16 groups, and that is currently impossible. r> r>We are happy to lend financial support to a solution ... however it sounds r>like $500 and free rsync.net storage space isn't going to be sufficient ? r> r>Is it unexpected that someone has run into this limit ? I have :-) There is an easy solution: Bump NGROUPS_MAX and recompile everything. Be aware that in some cases the group list is truncated: NFS and socket credentials (there may be more). I've done this over a year ago on my desktop because I'm in 50 groups that come from an active directory. Making this changeable via sysctl involves more work (see for example struct kproc_info). harti From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 15:46:33 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B33D616A41A for ; Thu, 27 Sep 2007 15:46:33 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 56C2C13C469 for ; Thu, 27 Sep 2007 15:46:33 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id EC8DC33C82; Thu, 27 Sep 2007 17:46:41 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9z5VPAWxcu6H; Thu, 27 Sep 2007 17:46:38 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id D2E3433C45; Thu, 27 Sep 2007 17:46:38 +0200 (CEST) Message-ID: <46FBD04C.3050409@zirakzigil.org> Date: Thu, 27 Sep 2007 17:46:20 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FBB8A8.1050202@zirakzigil.org> <86wsucp3qk.fsf@ds4.des.no> In-Reply-To: <86wsucp3qk.fsf@ds4.des.no> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 15:46:33 -0000 Dag-Erling Smørgrav wrote: > Giulio Ferro writes: > >> To say that there isn't enough interest in the nvidia driver would be >> outrageous. >> > > No, it would be true. From the slew of messages on the subject (on the nvidia forum, for example) it wouldn't seem to be so true... I can understand the lack of interest of the developers for a task so difficult as this one, but please don't assume that others have no interest as well... From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 15:56:43 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64BDE16A41A for ; Thu, 27 Sep 2007 15:56:43 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 1457313C448 for ; Thu, 27 Sep 2007 15:56:43 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id EF71D20AC; Thu, 27 Sep 2007 17:56:36 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id D05BF20AA; Thu, 27 Sep 2007 17:56:36 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id B11648448A; Thu, 27 Sep 2007 17:56:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Giulio Ferro References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FBB8A8.1050202@zirakzigil.org> <86wsucp3qk.fsf@ds4.des.no> <46FBD04C.3050409@zirakzigil.org> Date: Thu, 27 Sep 2007 17:56:36 +0200 In-Reply-To: <46FBD04C.3050409@zirakzigil.org> (Giulio Ferro's message of "Thu\, 27 Sep 2007 17\:46\:20 +0200") Message-ID: <86sl50p0ej.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 15:56:43 -0000 Giulio Ferro writes: > Dag-Erling Sm=C3=B8rgrav wrote: > > Giulio Ferro writes: > > > To say that there isn't enough interest in the nvidia driver would > > > be outrageous. > > No, it would be true. > From the slew of messages on the subject (on the nvidia forum, for > example) it wouldn't seem to be so true... It's a simple statement of fact. There is not enough interest in the nvidia driver for anyone to have written the code required to make it work. If you still don't get it, I suggest you go look up "enough" in a dictionary. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Thu Sep 27 16:23:30 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25B6416A417 for ; Thu, 27 Sep 2007 16:23:30 +0000 (UTC) (envelope-from vladvic_r@mail.ru) Received: from host-a.dgs.ru (host-a.dgs.ru [213.183.124.34]) by mx1.freebsd.org (Postfix) with ESMTP id BFCF213C48E for ; Thu, 27 Sep 2007 16:23:29 +0000 (UTC) (envelope-from vladvic_r@mail.ru) Received: from [192.168.0.199] (vvp.tomcity.net [88.204.24.82]) by host-a.dgs.ru (Postfix) with ESMTP id CD19111E5B0 for ; Thu, 27 Sep 2007 22:51:15 +0700 (NOVST) From: "Vladimir V. Pavluk" To: freebsd-hackers@freebsd.org Date: Thu, 27 Sep 2007 22:54:24 +0700 User-Agent: KMail/1.9.3 References: <46FB66B8.2000704@zirakzigil.org> <86wsucp3qk.fsf@ds4.des.no> <46FBD04C.3050409@zirakzigil.org> In-Reply-To: <46FBD04C.3050409@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200709272254.26364.vladvic_r@mail.ru> Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2007 16:23:30 -0000 Yes, there is no official driver, but maybe you can use one from here: http://silversoft.net/projects.html this is a disassembled and patched version of the official driver. Sincerely, Vladimir V. Pavluk From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 02:41:35 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD5F216A469 for ; Fri, 28 Sep 2007 02:41:35 +0000 (UTC) (envelope-from ktullavik@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.190]) by mx1.freebsd.org (Postfix) with ESMTP id 8B5D913C494 for ; Fri, 28 Sep 2007 02:41:35 +0000 (UTC) (envelope-from ktullavik@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2100122nfb for ; Thu, 27 Sep 2007 19:41:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; bh=vP80woHcas9LM2qaqJ40n2ExTqJrdtwoB4VTYQ4PyCY=; b=AAOCvWgIVK4sa1sh/MxTQvPsjFgQfrel5thpBI8uJKwk8vYYjUFJYqmBx9ghsRv7pIZlRhau+KIxMXcWGnvUd78pDqxhW0XcUftfY/scBmNyefBRDLACjnKZi0YnPOg6MAEMW0QuUOdg99VguuCsHdIWl6YMa9CRF3qR8ANc/38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=NmDVJqaGAdmi4C9JhK4kjZwm2wpFp1P8pW2ozZ3yN29WO9P6pSjFbKFm71is/Yyp0Z2vj+cKBBj/KdK3/YZcxhOHMpkpBwsxHawW441ptW6Y4LwW0pBdaEdcp4CPgGqNrOg5AGOUgHo3mfeDkV+Og6hM8Qlf5XIn2/tA+xyLkPU= Received: by 10.78.166.7 with SMTP id o7mr2478793hue.1190945541555; Thu, 27 Sep 2007 19:12:21 -0700 (PDT) Received: from gauss.lan ( [84.49.131.253]) by mx.google.com with ESMTPS id 31sm775056nfu.2007.09.27.19.12.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 Sep 2007 19:12:20 -0700 (PDT) Message-ID: <46FC62E9.7020204@gmail.com> Date: Fri, 28 Sep 2007 04:11:53 +0200 From: Kjell Tore Ullavik User-Agent: Thunderbird 2.0.0.6 (X11/20070808) MIME-Version: 1.0 To: Remko Lodder References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> In-Reply-To: <20070927131935.GD1421@elvandar.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Giulio Ferro , Alastair Hogge Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 02:41:35 -0000 Remko Lodder wrote: > On Thu, Sep 27, 2007 at 03:07:42PM +0200, Giulio Ferro wrote: > >> Sam Fourman Jr. wrote: >> >>>>> There is no driver. >>>>> >>>>> >>>> I sort of surmised that already... >>>> >>>> >>>> So, we are still years away from seeing a working nvidia driver, >>>> by the look of it... >>>> >>>> >>> I guess what I am confused about, is there someone actively working on >>> the Nvidia requests, or does a capable individual need to take the >>> lead on this project? >>> >>> >>> >> And that's exactly what I'd very much like to know... >> _______________________________________________ >> > > >From what I know and what I can see; there is nobody actively working in > this region to get the things fixed to get this far. Ofcourse like rsync.net > you are free to sponsor these items if they are really important to you, > without that, do notice that people do this in their own free time, which > could either take some time before it's there, or might not be interesting > enough to work on currently (because of other things at work, private life > other code etc). > > It's not a matter of a capable individual taking the lead, it's a matter > of having someone capable enough working on this for some time, which can > be achieved by sponsoring that capable person for example. > > Cheers > remko > Maybe the FreeBSD project could provide an official site for bounties? Some things might have more interest among users than developers, and an easy way to create and donate to bounties for everyone to see may make it less of a barrier for people to put their money where their mouth is. Ubuntu seem to have something going, https://launchpad.net/ubuntu/+bounties From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 02:46:03 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B35D16A41B for ; Fri, 28 Sep 2007 02:46:03 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.freebsd.org (Postfix) with ESMTP id 1BCFD13C45A for ; Fri, 28 Sep 2007 02:46:02 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: by ug-out-1314.google.com with SMTP id a2so1664163ugf for ; Thu, 27 Sep 2007 19:46:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=gMicsrB+Ue7X+RsCsKv7GJuMcIGUZd9fV9sivyyoHlA=; b=W2DdmBwVTTnYilpGvpEZ0nzdeh7QlP8A+tea0KLM/AgF+rlMMxx8jiCk1MSpu5vijJIxJP+5gVPuj9e35AqZMbvPfOhy3FALSP9jRecuW3pl7poHjwKdeUYuRuchmTNJB9vUviw4PHV+uZue8BO45ABSlQRMbwT82Lq3v91ZQAI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=PxHwWg5IQbl2233pDx+VKGAT0k04BBhUr4AX8DjIGKdi3bRfHAnP0GiNvb2i/iwqXfLlYbIaOQWUb1hHIHsEz+Wb7vwiUxMWWt3TMZyhaw9LliyEqjexu4mnGbn/7wWe080N7VWp0nkV4b/e5BJnhOt4WMyeC/YQJ1037mWBevc= Received: by 10.66.224.3 with SMTP id w3mr4393854ugg.1190947560665; Thu, 27 Sep 2007 19:46:00 -0700 (PDT) Received: by 10.86.91.5 with HTTP; Thu, 27 Sep 2007 19:45:59 -0700 (PDT) Message-ID: <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> Date: Thu, 27 Sep 2007 21:45:59 -0500 From: "Sam Fourman Jr." To: "Kjell Tore Ullavik" In-Reply-To: <46FC62E9.7020204@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> Cc: freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge , Giulio Ferro Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 02:46:03 -0000 On 9/27/07, Kjell Tore Ullavik wrote: > Remko Lodder wrote: > > On Thu, Sep 27, 2007 at 03:07:42PM +0200, Giulio Ferro wrote: > > > >> Sam Fourman Jr. wrote: > >> > >>>>> There is no driver. > >>>>> > >>>>> > >>>> I sort of surmised that already... > >>>> > >>>> > >>>> So, we are still years away from seeing a working nvidia driver, > >>>> by the look of it... > >>>> > >>>> > >>> I guess what I am confused about, is there someone actively working on > >>> the Nvidia requests, or does a capable individual need to take the > >>> lead on this project? > >>> > >>> > >>> > >> And that's exactly what I'd very much like to know... > >> _______________________________________________ > >> > > > > >From what I know and what I can see; there is nobody actively working in > > this region to get the things fixed to get this far. Ofcourse like rsync.net > > you are free to sponsor these items if they are really important to you, > > without that, do notice that people do this in their own free time, which > > could either take some time before it's there, or might not be interesting > > enough to work on currently (because of other things at work, private life > > other code etc). > > > > It's not a matter of a capable individual taking the lead, it's a matter > > of having someone capable enough working on this for some time, which can > > be achieved by sponsoring that capable person for example. > > > > Cheers > > remko > > > Maybe the FreeBSD project could provide an official site for bounties? > Some things might have more interest among users than developers, > and an easy way to create and donate to bounties for everyone to see may > make it less of a barrier for people to put their money where their > mouth is. > > Ubuntu seem to have something going, https://launchpad.net/ubuntu/+bounties > > > if there was a bounty system for FreeBSD I would pledge $100 USD for work that would help amd64 nvidia... heck I would even settle for someone that wants to take lead and setup a paypal collection. Sam Fourman Jr. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 03:47:42 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A95F616A419 for ; Fri, 28 Sep 2007 03:47:42 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from hannah.tgi.net (hannah.tgi.net [64.34.34.36]) by mx1.freebsd.org (Postfix) with ESMTP id 85F3313C4A3 for ; Fri, 28 Sep 2007 03:47:42 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: (qmail 17867 invoked from network); 27 Sep 2007 20:51:10 -0700 Received: from cs213-82.fsmodem.washington.edu (HELO ?127.0.0.1?) (140.142.173.83) by tgi.net with SMTP; 27 Sep 2007 20:51:10 -0700 Message-ID: <46FC793F.5010906@u.washington.edu> Date: Thu, 27 Sep 2007 20:47:11 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> In-Reply-To: <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge , Giulio Ferro , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 03:47:42 -0000 Sam Fourman Jr. wrote: > On 9/27/07, Kjell Tore Ullavik wrote: > >> Remko Lodder wrote: >> >>> On Thu, Sep 27, 2007 at 03:07:42PM +0200, Giulio Ferro wrote: >>> >>> >>>> Sam Fourman Jr. wrote: >>>> >>>> >>>>>>> There is no driver. >>>>>>> >>>>>>> >>>>>>> >>>>>> I sort of surmised that already... >>>>>> >>>>>> >>>>>> So, we are still years away from seeing a working nvidia driver, >>>>>> by the look of it... >>>>>> >>>>>> >>>>>> >>>>> I guess what I am confused about, is there someone actively working on >>>>> the Nvidia requests, or does a capable individual need to take the >>>>> lead on this project? >>>>> >>>>> >>>>> >>>>> >>>> And that's exactly what I'd very much like to know... >>>> _______________________________________________ >>>> >>>> >>> >From what I know and what I can see; there is nobody actively working in >>> this region to get the things fixed to get this far. Ofcourse like rsync.net >>> you are free to sponsor these items if they are really important to you, >>> without that, do notice that people do this in their own free time, which >>> could either take some time before it's there, or might not be interesting >>> enough to work on currently (because of other things at work, private life >>> other code etc). >>> >>> It's not a matter of a capable individual taking the lead, it's a matter >>> of having someone capable enough working on this for some time, which can >>> be achieved by sponsoring that capable person for example. >>> >>> Cheers >>> remko >>> >>> >> Maybe the FreeBSD project could provide an official site for bounties? >> Some things might have more interest among users than developers, >> and an easy way to create and donate to bounties for everyone to see may >> make it less of a barrier for people to put their money where their >> mouth is. >> >> Ubuntu seem to have something going, https://launchpad.net/ubuntu/+bounties >> >> >> >> > if there was a bounty system for FreeBSD I would pledge $100 USD for > work that would help amd64 nvidia... heck I would even settle for > someone that wants to take lead and setup a paypal collection. > > Sam Fourman Jr. > What needs to be done is FreeBSD users need to be asked, specifically, if they have interest in an amd64 capable nvidia-driver being released. If so, then a donation page should be setup and coordinated either through the FreeBSD Foundation (desired) or a trusted, private individual who will distribute the funds to the parties implementing the feature. Personally I think that this should apply to many things, not just nvidia-driver. If that was done, maybe volunteer work (I know, less volunteer, more work) would move along faster. The same thing occurs in the business world but instead of small bounties it's usually a large sum of money for a set of features developed and supported over a long period of time. At least that's what Linux would make me think... Just my two cents.. -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 07:58:56 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86A7716A419 for ; Fri, 28 Sep 2007 07:58:56 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 392E113C467 for ; Fri, 28 Sep 2007 07:58:56 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 6996233C8B; Fri, 28 Sep 2007 09:59:04 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oih4X7-IbMd3; Fri, 28 Sep 2007 09:58:57 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id 6190533C83; Fri, 28 Sep 2007 09:58:57 +0200 (CEST) Message-ID: <46FCB42E.1000407@zirakzigil.org> Date: Fri, 28 Sep 2007 09:58:38 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> In-Reply-To: <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 07:58:56 -0000 Sam Fourman Jr. wrote: > > if there was a bounty system for FreeBSD I would pledge $100 USD for > work that would help amd64 nvidia... heck I would even settle for > someone that wants to take lead and setup a paypal collection. > > Sam Fourman Jr. > I completely agree. Some guy here went as far as saying that nobody gives a damn about nvidia drivers, but from what I see (here and on nvidia forum) the opposite is true. Ok, let's see how we can fund this project. First of all the interested developers should assess the bulk of work to do and how long it will take them to complete it. Then we can think about how many people are interested in opening their wallet to see it come into being. From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 08:04:35 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E12B16A420 for ; Fri, 28 Sep 2007 08:04:35 +0000 (UTC) (envelope-from remko@elvandar.org) Received: from guardian.elvandar.org (evilcoder.xs4all.nl [195.64.94.120]) by mx1.freebsd.org (Postfix) with ESMTP id F3E9813C4BC for ; Fri, 28 Sep 2007 08:04:34 +0000 (UTC) (envelope-from remko@elvandar.org) Received: by guardian.elvandar.org (Postfix, from userid 1001) id 88A037EDEB3; Fri, 28 Sep 2007 10:04:33 +0200 (CEST) Date: Fri, 28 Sep 2007 10:04:33 +0200 From: Remko Lodder To: Giulio Ferro Message-ID: <20070928080433.GA1395@elvandar.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FCB42E.1000407@zirakzigil.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FCB42E.1000407@zirakzigil.org> User-Agent: Mutt/1.5.15 (2007-04-06) Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:04:35 -0000 On Fri, Sep 28, 2007 at 09:58:38AM +0200, Giulio Ferro wrote: > Sam Fourman Jr. wrote: > > > > if there was a bounty system for FreeBSD I would pledge $100 USD for > > work that would help amd64 nvidia... heck I would even settle for > > someone that wants to take lead and setup a paypal collection. > > > > Sam Fourman Jr. > > > > I completely agree. Some guy here went as far as saying that nobody gives a > damn about nvidia drivers, but from what I see (here and on nvidia forum) > the opposite is true. Hello, Hopefully you are not pointing to me in this case? > > Ok, let's see how we can fund this project. First of all the interested > developers > should assess the bulk of work to do and how long it will take them to > complete > it. Then we can think about how many people are interested in opening their > wallet to see it come into being. Lets do it the other way around ,lets see what people are willing to pay for this, so that the person applying for this knows what he can expect. Pay by feature instead of pay by time. Cheers remko -- Kind regards, Remko Lodder ** remko@elvandar.org FreeBSD ** remko@FreeBSD.org /* Quis custodiet ipsos custodes */ From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 08:09:10 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C84A116A417 for ; Fri, 28 Sep 2007 08:09:10 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 8618713C45D for ; Fri, 28 Sep 2007 08:09:10 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 92AD320A3; Fri, 28 Sep 2007 10:09:04 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on tim.des.no Received: from ds4.des.no (des.no [80.203.243.180]) by smtp.des.no (Postfix) with ESMTP id 7D6C220A0; Fri, 28 Sep 2007 10:09:04 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 5A91E844A1; Fri, 28 Sep 2007 10:09:04 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Giulio Ferro References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FCB42E.1000407@zirakzigil.org> Date: Fri, 28 Sep 2007 10:09:04 +0200 In-Reply-To: <46FCB42E.1000407@zirakzigil.org> (Giulio Ferro's message of "Fri\, 28 Sep 2007 09\:58\:38 +0200") Message-ID: <86tzpf9ppb.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:09:10 -0000 Giulio Ferro writes: > I completely agree. Some guy here went as far as saying that nobody > gives a damn about nvidia drivers, but from what I see (here and on > nvidia forum) the opposite is true. I did not say that. I said that there was not *enough interest*. What you fail to understand is that this is a volunteer project, and the very definition of "enough interest" is that somebody either does the work or pays somebody else to do it. I simply can't understand where you got the idea that what gets done in FreeBSD is determined by who yells loudest without putting down any time, effort or money to back his words. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 08:21:48 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6BC316A46E for ; Fri, 28 Sep 2007 08:21:48 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from aurynwork1sv1.giulioferro.it (85-18-102-52.ip.fastwebnet.it [85.18.102.52]) by mx1.freebsd.org (Postfix) with ESMTP id 53DDD13C457 for ; Fri, 28 Sep 2007 08:21:46 +0000 (UTC) (envelope-from auryn@zirakzigil.org) Received: from localhost (localhost [127.0.0.1]) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id D675533C8B; Fri, 28 Sep 2007 10:21:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at giulioferro.it Received: from aurynwork1sv1.giulioferro.it ([127.0.0.1]) by localhost (aurynwork1sv1.giulioferro.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E0HX+5FfBOHX; Fri, 28 Sep 2007 10:21:55 +0200 (CEST) Received: from aurynmob2.giulioferro.it (89-96-52-22.ip10.fastwebnet.it [89.96.52.22]) (Authenticated sender: gferro@giulioferro.it) by aurynwork1sv1.giulioferro.it (Postfix) with ESMTP id B507C33C82; Fri, 28 Sep 2007 10:21:55 +0200 (CEST) Message-ID: <46FCB990.1010303@zirakzigil.org> Date: Fri, 28 Sep 2007 10:21:36 +0200 From: Giulio Ferro User-Agent: Thunderbird 2.0.0.5 (X11/20070724) MIME-Version: 1.0 To: Remko Lodder References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FCB42E.1000407@zirakzigil.org> <20070928080433.GA1395@elvandar.org> In-Reply-To: <20070928080433.GA1395@elvandar.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Alastair Hogge , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 08:21:48 -0000 Remko Lodder wrote: >> Ok, let's see how we can fund this project. First of all the interested >> developers >> should assess the bulk of work to do and how long it will take them to >> complete >> it. Then we can think about how many people are interested in opening their >> wallet to see it come into being. >> > > Lets do it the other way around ,lets see what people are willinoneg to pay for > this, so that the person applying for this knows what he can expect. Pay by > feature instead of pay by time. > I'm in, as are at least other two posters in this thread. I think that if someone set up a web page for the bounty and spread the news to other forums a fair number of subscriptions will come up. What we need to know is : what is the bulk of work needed? Can't anyone sketch a simple plan with the tasks and the hours/man for each? From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 13:55:38 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5AA916A538 for ; Fri, 28 Sep 2007 13:55:38 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.freebsd.org (Postfix) with ESMTP id 05D5413C4A3 for ; Fri, 28 Sep 2007 13:55:37 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: by nf-out-0910.google.com with SMTP id b2so2225544nfb for ; Fri, 28 Sep 2007 06:55:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:organization:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id:sender; bh=QA84XPyrZsw1psktKGxCCXIgcCaRV4IeMhb6ltcbPQA=; b=EsZm6daTZyuR/8xXZOCvK6nJ8Tw+xc9/ff2RUwmvf2CuYKzb/jLhU39ysmoUmmlGAJmNe9DLjYQJv1xQeC0JOXWPxSe/ZYRpoSTZZddOxxqFx9xao0vYfFfwZK1Vl4ojZOxnAni1M7aych2ufgsSAw5HEJ5I4HbQPrsf6DKkEYM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:organization:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:message-id:sender; b=WhHbUS5TP14QENxCVcyte6i723Ytfqh7iK2v6pE+4t0oAa1g3vs0pARgMKDam4jir26pFX1QBmRXrsgaMNfI720LCnXKM8o0xeQx1KrzCxq2RF1oWCqVCPWCHjZdXtZhHa2V226IMSIm0iQWxKu+vpbPhdwb/Z6v2bzmlutUvDo= Received: by 10.78.97.7 with SMTP id u7mr3097311hub.1190985999983; Fri, 28 Sep 2007 06:26:39 -0700 (PDT) Received: from homegate ( [196.34.241.123]) by mx.google.com with ESMTPS id i4sm5080545nfh.2007.09.28.06.26.31 (version=SSLv3 cipher=OTHER); Fri, 28 Sep 2007 06:26:38 -0700 (PDT) From: David Naylor Organization: Private To: freebsd-hackers@freebsd.org Date: Fri, 28 Sep 2007 15:26:57 +0200 User-Agent: KMail/1.9.5 References: <46FB66B8.2000704@zirakzigil.org> <20070928080433.GA1395@elvandar.org> <46FCB990.1010303@zirakzigil.org> In-Reply-To: <46FCB990.1010303@zirakzigil.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1803695.V4ux7cQ6hh"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200709281527.02072.blackdragon@highveldmail.co.za> Sender: David Naylor Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 13:55:38 -0000 --nextPart1803695.V4ux7cQ6hh Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 28 September 2007 10:21, you wrote: > Remko Lodder wrote: > >> Ok, let's see how we can fund this project. First of all the interest= ed > >> developers > >> should assess the bulk of work to do and how long it will take them to > >> complete > >> it. Then we can think about how many people are interested in opening > >> their wallet to see it come into being. > > > > Lets do it the other way around ,lets see what people are willinoneg to > > pay for this, so that the person applying for this knows what he can > > expect. Pay by feature instead of pay by time. > > I'm in, as are at least other two posters in this thread. > I think that if someone set up a web page for the bounty > and spread the news to other forums a fair number of subscriptions > will come up. > > What we need to know is : what is the bulk of work needed? Can't anyone > sketch a simple plan with the tasks and the hours/man for each? Hi Has anyone contacted the FreeBSD Foundation. They would be the best to=20 provide this "bounty" service and could most effectively invest and utilise= =20 the "bounties" for the greater benefit of the comunity while the project is= =20 under work. (And they are most likely to be the most trusted people to=20 handle the project and the money). =20 There was a KDE project, Kontact (if I remember correctly), that had=20 implemented a similar facility. (And of course there is the Ubuntu=20 equivalent). =20 May I also point out that this, specifically with regards to nVidia/amd64 a= nd=20 generally, can only work if capable hackers are willing to work on the=20 project(s). Generally with volunteers money is not a critical issue to beg= in=20 with and thus may not be a strong enough incentive and interest is. =20 I may be jumping the gun here but if this "bounty" principle takes of then= =20 enthusiasts could earn a descant wage and provide a viable financial=20 community around FreeBSD (with businesses more willing to use FreeBSD knowi= ng=20 that requested features [and form of support] could be "purchased"). =20 I am also keenly awaiting a nvidia/amd64 driver and am willing to donate wh= at=20 I can to the good cause. =20 David --nextPart1803695.V4ux7cQ6hh Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBG/QEmyqzxLKpyZI8RAuaNAKCJoiEC25g/URGB8yVeIdjhdZLPSQCfTapk XtHP5WH0a0AGioFDCInRaDA= =D/qB -----END PGP SIGNATURE----- --nextPart1803695.V4ux7cQ6hh-- From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 14:43:52 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A31116A47D for ; Fri, 28 Sep 2007 14:43:52 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.8]) by mx1.freebsd.org (Postfix) with ESMTP id AC7F313C4AA for ; Fri, 28 Sep 2007 14:43:51 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.1/8.13.8) with ESMTP id l8SENEck087836; Fri, 28 Sep 2007 10:23:14 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.1/8.13.8/Submit) id l8SENCIQ087835; Fri, 28 Sep 2007 10:23:12 -0400 (EDT) (envelope-from mwlucas) Date: Fri, 28 Sep 2007 10:23:12 -0400 From: "Michael W. Lucas" To: Garrett Cooper Message-ID: <20070928142312.GA87523@bewilderbeast.blackhelicopters.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FC793F.5010906@u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <46FC793F.5010906@u.washington.edu> User-Agent: Mutt/1.4.2.2i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Fri, 28 Sep 2007 10:23:14 -0400 (EDT) Cc: Remko Lodder , Alastair Hogge , freebsd-hackers@freebsd.org, Kjell Tore Ullavik , "Sam Fourman Jr." , Giulio Ferro Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 14:43:52 -0000 [I would trim this down, but it's so damn big that I'm certain I'd confuse attributions...] On Thu, Sep 27, 2007 at 08:47:11PM -0700, Garrett Cooper wrote: > Sam Fourman Jr. wrote: > >On 9/27/07, Kjell Tore Ullavik wrote: > >>Remko Lodder wrote: > >>>On Thu, Sep 27, 2007 at 03:07:42PM +0200, Giulio Ferro wrote: > >>>> Sam Fourman Jr. wrote: > >>>>>>>There is no driver. > >>>>>>I sort of surmised that already... > >>>>>>So, we are still years away from seeing a working nvidia driver, > >>>>>>by the look of it... > >>>>>I guess what I am confused about, is there someone actively working on > >>>>>the Nvidia requests, or does a capable individual need to take the > >>>>>lead on this project? > >>>> And that's exactly what I'd very much like to know... > >>>>From what I know and what I can see; there is nobody actively working in > >>>this region to get the things fixed to get this far. Ofcourse like > >>>rsync.net > >>>you are free to sponsor these items if they are really important to you, > >>>without that, do notice that people do this in their own free time, which > >>>could either take some time before it's there, or might not be > >>>interesting > >>>enough to work on currently (because of other things at work, private > >>>life > >>>other code etc). > >>>It's not a matter of a capable individual taking the lead, it's a matter > >>>of having someone capable enough working on this for some time, which can > >>>be achieved by sponsoring that capable person for example. > >>Maybe the FreeBSD project could provide an official site for bounties? > >>Some things might have more interest among users than developers, > >>and an easy way to create and donate to bounties for everyone to see may > >>make it less of a barrier for people to put their money where their > >>mouth is. Hi, There's been discussion about the possibility of providing an "official" FreeBSD bounty page run by the FreeBSD Project. As I recall, for a variety of legal reasons the Foundation will not do it. Remember that "the FreeBSD Project" is not a legal entity. We are a loosely affiliated gang with no existence outside the minds of our members and users. This does not affect people much in the software world -- you don't care that the main FreeBSD FTP server is actually owned by ISC, or that the Web server is provided by Yahoo! Legally, TFP cannot hold your money in trust as part of a bounty. These two points reach a simple conclusion: there will be no "official FreeBSD Project Bounty Page," end of discussion. (I'm sure that people are going to blather about it more, but this really is the final word from the FreeBSD Project side. The Internet loves beating that greasy spot on the ground where the dead horse used to be, though...) "Enough interest" is not a question of quantity, but a qualitative question. It doesn't matter if millions of users want a nVidia amd64 driver if none of them can write the code. Every one of those millions of users may be a high-quality human being with a great deal of inherent worth, but if they don't have the quality of "can write the code" they don't count. When someone who has the skills to develop the kernel support nVidia requires is sufficiently interested to develop that kernel support, it will happen. Not before. If you don't have the skills, but you believe that you have sufficient motivation and interest, then you tneed to do the work to motivate a developer. Hint: email alone, no matter how impassioned or whiny, will not do it. If you do not do this, then you do not have sufficient interest. > What needs to be done is FreeBSD users need to be asked, > specifically, if they have interest in an amd64 capable nvidia-driver > being released. If so, then a donation page should be setup and > coordinated either through the FreeBSD Foundation (desired) or a > trusted, private individual who will distribute the funds to the parties > implementing the feature. Great idea! The Foundation is not going to do this -- last I knew, they do not accept directed donations for legal reasons. Everybody on this list is an individual, however. Step up. Do it. Yes, I'm talking to you, the person reading this right now. That's how you become part of the loose gang called The FreeBSD Project. Don't ask me to do it. I think that there should be better FreeBSD books available in bookstores, and so I'm doing that. This is the *only* way ANYTHING gets done in the FreeBSD Project. > Personally I think that this should apply to many things, not just > nvidia-driver. If that was done, maybe volunteer work (I know, less > volunteer, more work) would move along faster. The same thing occurs in > the business world but instead of small bounties it's usually a large > sum of money for a set of features developed and supported over a long > period of time. At least that's what Linux would make me think... I would suggest that whoever does the work break up the nVidia needs list into a small series of steps that could be accomplished (and bought) more easily, rather than a single monolithic bounty. I would also suggest that whoever does this talks to a lawyer first. You might find the legal restrictions on this less onerous if you're not in the USA. Here, it's hard to just be a good guy. :-( > Just my two cents.. Two cents? Wow. Mine is, like, a half-penny. :-) ==ml -- Michael W. Lucas mwlucas@BlackHelicopters.org, mwlucas@FreeBSD.org http://www.BlackHelicopters.org/~mwlucas/ Coming Soon: "Absolute FreeBSD" -- http://www.AbsoluteFreeBSD.com On 5/4/2007, the TSA kept 3 pairs of my soiled undies "for security reasons." From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 16:41:36 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E48A16A41A for ; Fri, 28 Sep 2007 16:41:36 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtao107.cox.net (eastrmmtao107.cox.net [68.230.240.59]) by mx1.freebsd.org (Postfix) with ESMTP id BA85A13C474 for ; Fri, 28 Sep 2007 16:41:35 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo02.cox.net ([68.1.16.120]) by eastrmmtao107.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20070928164135.TZFS7818.eastrmmtao107.cox.net@eastrmimpo02.cox.net>; Fri, 28 Sep 2007 12:41:35 -0400 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo02.cox.net with bizsmtp id tsha1X0064iy4EG0000000; Fri, 28 Sep 2007 12:41:34 -0400 Date: Fri, 28 Sep 2007 11:45:28 -0500 To: "Giulio Ferro" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FCB42E.1000407@zirakzigil.org> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <46FCB42E.1000407@zirakzigil.org> User-Agent: Opera Mail/9.23 (Linux) Cc: "Sam Fourman Jr." , freebsd-hackers@freebsd.org, Remko Lodder , Alastair Hogge , Kjell Tore Ullavik Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 16:41:36 -0000 On Fri, 28 Sep 2007 02:58:38 -0500, Giulio Ferro wrote: > Sam Fourman Jr. wrote: >> >> if there was a bounty system for FreeBSD I would pledge $100 USD for >> work that would help amd64 nvidia... heck I would even settle for >> someone that wants to take lead and setup a paypal collection. >> >> Sam Fourman Jr. >> > > I completely agree. Some guy here went as far as saying that nobody > gives a > damn about nvidia drivers, but from what I see (here and on nvidia > forum) > the opposite is true. If there are the people in nvidia forum have 'enough insterest' to write then it would have been already done by now. :-) It is what others in here are trying to tell you about that we don't have anybody (even include nvidia forum) that who have 'enough insterest' to write it for nvidia driver's need. As for me, I am a nvidia driver user and I do want it works with amd64, but I do not have 'enough insterest' to learn and write it. It looks like it is included you too. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org http://wiki.freebsd.org/multimedia - multimedia@FreeBSD.org From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 17:33:44 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B949E16A419 for ; Fri, 28 Sep 2007 17:33:44 +0000 (UTC) (envelope-from mah@jump-ing.de) Received: from mail.ud03.udmedia.de (ud03.udmedia.de [194.117.254.43]) by mx1.freebsd.org (Postfix) with ESMTP id 0DD6E13C469 for ; Fri, 28 Sep 2007 17:33:43 +0000 (UTC) (envelope-from mah@jump-ing.de) Received: (qmail 8172 invoked from network); 28 Sep 2007 19:33:43 +0200 Received: from unknown (HELO ?10.0.0.50?) (ud03?291p1@91.89.219.223) by mail.ud03.udmedia.de with ESMTPA; 28 Sep 2007 19:33:43 +0200 In-Reply-To: <20070928142312.GA87523@bewilderbeast.blackhelicopters.org> References: <46FB66B8.2000704@zirakzigil.org> <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FC793F.5010906@u.washington.edu> <20070928142312.GA87523@bewilderbeast.blackhelicopters.org> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1BD09BB1-4BCE-44EE-A04D-67E94A8A26D3@jump-ing.de> Content-Transfer-Encoding: 7bit From: Markus Hitter Date: Fri, 28 Sep 2007 19:33:35 +0200 To: Michael W. Lucas X-Mailer: Apple Mail (2.752.2) Cc: Remko Lodder , Alastair Hogge , freebsd-hackers@freebsd.org, Garrett Cooper , Kjell Tore Ullavik , "Sam Fourman Jr." , Giulio Ferro Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 17:33:44 -0000 Am 28.09.2007 um 16:23 schrieb Michael W. Lucas: > If you don't have the skills, but you believe that you have sufficient > motivation and interest, then you tneed to do the work to motivate a > developer. There is another option: learning. Instead of complaining "nobody has interest" and "your opinion doesn't count" a few hints where to get started as a not-yet-skilled developer would be a lot more helpful. my $ 0.02 Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 18:54:29 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C167916A418 for ; Fri, 28 Sep 2007 18:54:29 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (bewilderbeast.blackhelicopters.org [198.22.63.8]) by mx1.freebsd.org (Postfix) with ESMTP id 2B6B013C44B for ; Fri, 28 Sep 2007 18:54:28 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.1/8.13.8) with ESMTP id l8SIsSQp089377 for ; Fri, 28 Sep 2007 14:54:28 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.1/8.13.8/Submit) id l8SIsSY9089376 for freebsd-hackers@freebsd.org; Fri, 28 Sep 2007 14:54:28 -0400 (EDT) (envelope-from mwlucas) Date: Fri, 28 Sep 2007 14:54:28 -0400 From: "Michael W. Lucas" To: freebsd-hackers@freebsd.org Message-ID: <20070928185428.GB89169@bewilderbeast.blackhelicopters.org> References: <200709272233.54689.agh@tpg.com.au> <46FBA8F7.80305@zirakzigil.org> <11167f520709270602n2f96e5d5kb250ac21af096073@mail.gmail.com> <46FBAB1E.8060103@zirakzigil.org> <20070927131935.GD1421@elvandar.org> <46FC62E9.7020204@gmail.com> <11167f520709271945p7453b254gf60d10ed231f3ea4@mail.gmail.com> <46FC793F.5010906@u.washington.edu> <20070928142312.GA87523@bewilderbeast.blackhelicopters.org> <1BD09BB1-4BCE-44EE-A04D-67E94A8A26D3@jump-ing.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1BD09BB1-4BCE-44EE-A04D-67E94A8A26D3@jump-ing.de> User-Agent: Mutt/1.4.2.2i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Fri, 28 Sep 2007 14:54:28 -0400 (EDT) Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 18:54:29 -0000 (trimming the cc-list) On Fri, Sep 28, 2007 at 07:33:35PM +0200, Markus Hitter wrote: > > Am 28.09.2007 um 16:23 schrieb Michael W. Lucas: > > >If you don't have the skills, but you believe that you have sufficient > >motivation and interest, then you tneed to do the work to motivate a > >developer. > > There is another option: learning. Absolutely! If you're sufficiently interested, break out a compiler and learn. Look at the page that lists the driver requirements. Read about those requirements. Read the FreeBSD source code that you'd have to change, and understand it. Read "Design & Implementation of the FreeBSD OS." I'm afraid I thought that was obvious. I'm not trying to discount anyone, far from it. But after hearing for the umpteenth time "The FreeBSD Project/Foundation outght to set up a bounty page," I had to say why it wasn't going to happen. (My apologies if I offended anyone, that was unintentional.) I'll stand by saying that when a person says "someone should do something," that someone is "the person writing that email." You have many options for what to do, far more than I could list. I don't care what option people choose. Just do it. > Instead of complaining "nobody has interest" and "your opinion > doesn't count" a few hints where to get started as a not-yet-skilled > developer would be a lot more helpful. I would suggest starting with a very specific question. Somewhere out there is a list of requirements for the amd64 nVidia port. (I found one at http://lists.freebsd.org/pipermail/freebsd-hackers/2006-June/016995.html, but I have no idea if this is the current authoritative list.) Look at the list, and do the reading and research necessary to understand one or more requirements. If no authoritative list exists, create one. Do the necessary mailing list archive searching to determine the status of each. I assure you that if you miss anything, the first person to come across your page will let you know. ;-) Pick a tack on that list. Read it. Understand it. Read the underlying FreeBSD code that supports that function. Explore the kernel. Read D&IotFOS with a highlighter in hand. Print out source code, mark it up, understand it. Then ask a specific question about where to go on one very small part of your project. Specific questions get answers. General ones do not. It's sad, but that's how it is. Take that answer. Read more code. Write a few lines of code. Repeat until the driver is done. ==ml -- Michael W. Lucas mwlucas@BlackHelicopters.org, mwlucas@FreeBSD.org http://www.BlackHelicopters.org/~mwlucas/ Coming Soon: "Absolute FreeBSD" -- http://www.AbsoluteFreeBSD.com On 5/4/2007, the TSA kept 3 pairs of my soiled undies "for security reasons." From owner-freebsd-hackers@FreeBSD.ORG Fri Sep 28 19:23:48 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E0CF16A417 for ; Fri, 28 Sep 2007 19:23:48 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: from hatpro.mr-paradox.net (hatpro.mr-paradox.net [204.11.33.143]) by mx1.freebsd.org (Postfix) with ESMTP id 6FE1213C478 for ; Fri, 28 Sep 2007 19:23:48 +0000 (UTC) (envelope-from jfb@mr-paradox.net) Received: by hatpro.mr-paradox.net (Postfix, from userid 16139) id C2E0AC0FD; Fri, 28 Sep 2007 14:50:43 -0400 (EDT) Date: Fri, 28 Sep 2007 14:50:42 -0400 From: Jeff Blank To: freebsd-hackers@freebsd.org Message-ID: <20070928185042.GB73316@mr-happy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Face: #0jV*~a}VtKS-&E/!EJpH('H1Va}24dxF0oT&+.R3Gu8C; xhSC+<|+H84&YLbMvphuRT4cp3.|8EN_(2Eix/6{.Up~u`a^}0Ln&b+9Fw|BPig@-{y\pL_46d&ZwA]5%_AU?}DezfE&1!>H?3E$!Yve7.O<+..Jnb4:'6Ey_]FtFzU9=*l$1p/@gA,Ze>^5<]+r(XJ+m7`/vMDc$'wy|`e Subject: Comtrol RocketPort 550 uPCI, 16-port X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2007 19:23:48 -0000 Hi, I've just installed a 16-port RocketPort 550 uPCI (Comtrol part # 99211-0) and am getting a failure in device_attach: rp0: port 0xdc80-0xdcff,0xd800-0xd8ff mem 0xfcf00400-0xfcf0047f,0xfcf00000-0xfcf000ff irq 20 at device 8.0 on pci1 rp0: ioaddr mapping failed for RocketPort(PCI). device_attach: rp0 attach returned 6 # pciconf -l -v [...] rp0@pci1:8:0: class=0x028000 card=0x802211fe chip=0x802211fe rev=0x00 hdr=0x00 vendor = 'Comtrol Corp' class = network I've read an older thread from this list regarding a 32-port version of this card, and a device-id (0x08##) seemed to be available from the output of pciconf in that thread, but I'm not getting anything more than the above for my card. do I have any hope of getting this card to work under 6-STABLE? (the server is running 6.2-RELEASE now, but I'd be happy to go to -STABLE to get it to work.) what other information from me would be helpful? thanks much, Jeff From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 29 02:40:55 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ACEE016A418 for ; Sat, 29 Sep 2007 02:40:55 +0000 (UTC) (envelope-from ighighi@gmail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.228]) by mx1.freebsd.org (Postfix) with ESMTP id 675B013C447 for ; Sat, 29 Sep 2007 02:40:55 +0000 (UTC) (envelope-from ighighi@gmail.com) Received: by wx-out-0506.google.com with SMTP id i29so2139793wxd for ; Fri, 28 Sep 2007 19:40:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; bh=wrilX8MEOhxTlJzdp1LNRqeDYulpd61SPIcxH4iCTjQ=; b=RJOsD+TBnJ9IQfAoPm/ZW95RqG3TojKVHM0SJYstSEGdJkznyN7ISXKMHliRHeXO0GJdpoc4RGrElIXK6acS+P3h53PxOQ/ThtXmp3H3veNwUgFOTdU040TwH7lqiepKi+rOVQlWsedeVuO0pwWCuw92pYcVr2T9DyRZrxYHTOQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=s+eRQeZbycNvT2EMPumUG7c2GQXKaQSq2h7VLM4UE7PKXIIe/zRurDRqUn7qdPWBm3aTUBJstxdLBchLJBzTqanP87Kd9wvrRtew7dU1/UcIEwRMLOniONQOsQkf/ZL+Y5rtQSqjc8ktvgOtXwsSJj+7rCECRucUerDvFkgG4ZU= Received: by 10.90.89.5 with SMTP id m5mr7001870agb.1191033654418; Fri, 28 Sep 2007 19:40:54 -0700 (PDT) Received: from orion.nebula.mil ( [200.44.87.172]) by mx.google.com with ESMTPS id l43sm4126143wrl.2007.09.28.19.40.47 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 28 Sep 2007 19:40:52 -0700 (PDT) Message-ID: <46FDBAFC.1010000@gmail.com> Date: Fri, 28 Sep 2007 22:39:56 -0400 From: Ighighi User-Agent: Thunderbird 2.0.0.6 (X11/20070803) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: POSIXfy readlink() call X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 02:40:55 -0000 The POXIX prototype for readlink(2) is: ssize_t readlink(const char *restrict path, char *restrict buf, size_t bufsize); See: http://www.opengroup.org/onlinepubs/000095399/functions/readlink.html NetBSD already did it: http://netbsd.gw.com/cgi-bin/man-cgi?readlink+2+ It'd be good have it corrected in 7.0. Salutes, Igh. From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 29 11:58:54 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A282016A417 for ; Sat, 29 Sep 2007 11:58:54 +0000 (UTC) (envelope-from mmendez@energyhq.be) Received: from spitfire.energyhq.be (34.Red-88-6-2.staticIP.rima-tde.net [88.6.2.34]) by mx1.freebsd.org (Postfix) with ESMTP id BA95313C457 for ; Sat, 29 Sep 2007 11:58:53 +0000 (UTC) (envelope-from mmendez@energyhq.be) Received: from [192.168.3.3] (mindfields.energyhq.be [192.168.3.3]) by spitfire.energyhq.be (Postfix) with ESMTP id B3D69FF1D; Sat, 29 Sep 2007 13:31:44 +0200 (CEST) In-Reply-To: <200709272254.26364.vladvic_r@mail.ru> References: <46FB66B8.2000704@zirakzigil.org> <86wsucp3qk.fsf@ds4.des.no> <46FBD04C.3050409@zirakzigil.org> <200709272254.26364.vladvic_r@mail.ru> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-2-157628121" Message-Id: From: Miguel Mendez Date: Sat, 29 Sep 2007 13:35:09 +0200 To: freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit X-Pgp-Agent: GPGMail 1.1.2 (Tiger) X-Mailer: Apple Mail (2.752.3) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "Vladimir V. Pavluk" Subject: Re: Nvidia amd64 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 11:58:54 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-2-157628121 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > http://silversoft.net/projects.html > > this is a disassembled and patched version of the official driver. Wow, that's pretty interesting. I spent some time with objdump (dasm actually) studying the code but got bored after a while. After AMD announced the release of the GPU specs I decided it would be more practical to get ATI hardware and let the proprietary nvidia blob rot. The knowledge gained from the reverse engineering can be useful for the Nouveau guys (http://nouveau.freedesktop.org/wiki/) anyway. Cheers, Miguel Mendez mmendez@energyhq.be --Apple-Mail-2-157628121 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) iD8DBQFG/jhtnLctrNyFFPERAl1JAKCoxA9DdRwnJgeQj6UOY82y5wMBzgCeOyZo 8UW/oW7TBIYzdElh0l4dOns= =oIe3 -----END PGP SIGNATURE----- --Apple-Mail-2-157628121-- From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 29 14:43:54 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2D22816A420 for ; Sat, 29 Sep 2007 14:43:54 +0000 (UTC) (envelope-from nicholas.thompson1@mchsi.com) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.freebsd.org (Postfix) with ESMTP id E60F713C455 for ; Sat, 29 Sep 2007 14:43:53 +0000 (UTC) (envelope-from nicholas.thompson1@mchsi.com) Received: from [192.168.1.75] (12-218-7-27.client.mchsi.com[12.218.7.27]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20070929143334m92002rjnse>; Sat, 29 Sep 2007 14:33:35 +0000 Message-ID: <46FE620F.7000809@mchsi.com> Date: Sat, 29 Sep 2007 09:32:47 -0500 From: nick thompson User-Agent: Thunderbird 2.0.0.6 (X11/20070908) MIME-Version: 1.0 To: Jeff Blank References: <20070928185042.GB73316@mr-happy.com> In-Reply-To: <20070928185042.GB73316@mr-happy.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, nick.thompson@comtrol.com Subject: Re: Comtrol RocketPort 550 uPCI, 16-port X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 14:43:54 -0000 Jeff Blank wrote: > Hi, > > I've just installed a 16-port RocketPort 550 uPCI (Comtrol part # > 99211-0) and am getting a failure in device_attach: > > rp0: port 0xdc80-0xdcff,0xd800-0xd8ff mem 0xfcf00400-0xfcf0047f,0xfcf00000-0xfcf000ff irq 20 at device 8.0 on pci1 > rp0: ioaddr mapping failed for RocketPort(PCI). > device_attach: rp0 attach returned 6 > > # pciconf -l -v > [...] > rp0@pci1:8:0: class=0x028000 card=0x802211fe chip=0x802211fe rev=0x00 hdr=0x00 > vendor = 'Comtrol Corp' > class = network > > I've read an older thread from this list regarding a 32-port version > of this card, and a device-id (0x08##) seemed to be available from the > output of pciconf in that thread, but I'm not getting anything more > than the above for my card. > > do I have any hope of getting this card to work under 6-STABLE? (the > server is running 6.2-RELEASE now, but I'd be happy to go to -STABLE > to get it to work.) what other information from me would be helpful? > > thanks much, > Jeff > Jeff, Hi. First off, to get it out of the way, I work for Comtrol. This is a Comtrol GMBH (used to be Comtrol UK, now Comtrol GMBH [Switzerland]) product. The two are separate companies now. Anyhow, if you have had this card for less than 30 days, I would hi,ghly recommend returning it to the distributor for a RocketPort uPCI 16 port card, as this is a Comtrol U.S. product and we have a 6.2 driver for our entire RocketPort line. There is no problem with the 550 cards, but they have no FreeBSD drivers at all, nor even a Linux 2.6 driver yet. I would just post a link but we've been upgrading servers this past week and I won't have the exact link until I get to work on Monday. I am the FreeBSD / Linux / other Unices guy in tech support at Comtrol U.S. and I would definitely like to extend an invitation for anyone who would like a copy of the driver to email me at my work address nick dot thompson at comtrol dot com, or to call Comtrol Tech Support and ask for Nick Thompson; 763-494-4100 is the number. Once I have the exact link, I will make sure and get it into this thread. Regards, Nick "All unix, all the time." http://npt.ath.cx From owner-freebsd-hackers@FreeBSD.ORG Sat Sep 29 17:37:08 2007 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADAB116A41B for ; Sat, 29 Sep 2007 17:37:08 +0000 (UTC) (envelope-from arun@eagle.sharma-home.net) Received: from eagle.sharma-home.net (cpe-24-221-178-208.ca.sprintbbd.net [24.221.178.208]) by mx1.freebsd.org (Postfix) with ESMTP id 8390E13C469 for ; Sat, 29 Sep 2007 17:37:05 +0000 (UTC) (envelope-from arun@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 1001) id 6CC1F341; Sat, 29 Sep 2007 08:14:37 -0700 (PDT) Date: Sat, 29 Sep 2007 08:14:37 -0700 From: Arun Sharma To: tbb-develop@lists.sourceforge.net Message-ID: <20070929151437.GA35489@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Sat, 29 Sep 2007 18:08:28 +0000 Cc: freebsd-hackers@freebsd.org, kfarnham@users.sourceforge.net Subject: TBB support for FreeBSD X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Sep 2007 17:37:08 -0000 FreeBSD support - tested on 7.0-CURRENT/amd64. Should apply cleanly to tbb20_20070815oss_src.tar.gz. Signed-off-by: Arun Sharma diff -r 627751b671bb -r ac2c116b7cee build/common.inc --- a/build/common.inc Sat Sep 29 16:18:03 2007 -0700 +++ b/build/common.inc Sat Sep 29 16:51:17 2007 -0700 @@ -37,6 +37,9 @@ ifndef tbb_os endif ifeq ($(OS), Darwin) export tbb_os=macos + endif + ifeq ($(OS), FreeBSD) + export tbb_os=freebsd endif endif endif diff -r 627751b671bb -r ac2c116b7cee build/freebsd.gcc.inc --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/build/freebsd.gcc.inc Sat Sep 29 16:51:17 2007 -0700 @@ -0,0 +1,98 @@ +# Copyright 2005-2007 Intel Corporation. All Rights Reserved. +# +# This file is part of Threading Building Blocks. +# +# Threading Building Blocks is free software; you can redistribute it +# and/or modify it under the terms of the GNU General Public License +# version 2 as published by the Free Software Foundation. +# +# Threading Building Blocks is distributed in the hope that it will be +# useful, but WITHOUT ANY WARRANTY; without even the implied warranty +# of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with Threading Building Blocks; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +# +# As a special exception, you may use this file as part of a free software +# library without restriction. Specifically, if other files instantiate +# templates or use macros or inline functions from this file, or you compile +# this file and link it with other files to produce an executable, this +# file does not by itself cause the resulting executable to be covered by +# the GNU General Public License. This exception does not however +# invalidate any other reasons why the executable file might be covered by +# the GNU General Public License. + +COMPILE_ONLY = -c -MMD +PREPROC_ONLY = -E -MMD +INCLUDE_KEY = -I +DEFINE_KEY = -D +OUTPUT_KEY = -o # +OUTPUTOBJ_KEY = -o # +PIC_KEY = -fPIC +WARNING_KEY = -Wall -Werror +DYLIB_KEY = -shared +LIBDL = + +TBB_NOSTRICT = 1 + +CPLUS = g++ +INCLUDES += -I$(tbb_root)/src/tbb -I$(tbb_root)/include -I$(tbb_root)/src +LIB_LINK_FLAGS = -shared +LIBS = -lpthread -lrt +C_FLAGS = $(CPLUS_FLAGS) -x c + +ifeq ($(cfg), release) + CPLUS_FLAGS = -DDO_ITT_NOTIFY -O2 -DUSE_PTHREAD +endif +ifeq ($(cfg), debug) + CPLUS_FLAGS = -DTBB_DO_ASSERT -DDO_ITT_NOTIFY -g -O0 -DUSE_PTHREAD +endif + +ASM= +ASM_FLAGS= + +TBB_ASM.OBJ= + +ifeq (itanium,$(arch)) +# Position-independent code (PIC) is a must for IA-64 + CPLUS_FLAGS += $(PIC_KEY) + $(PIC_KEY) = +endif + +ifeq (em64t,$(arch)) + CPLUS_FLAGS += -m64 + LIB_LINK_FLAGS += -m64 +endif + +ifeq (ia32,$(arch)) + CPLUS_FLAGS += -m32 + LIB_LINK_FLAGS += -m32 +endif + +#------------------------------------------------------------------------------ +# Setting assembler data. +#------------------------------------------------------------------------------ +%.$(OBJ): %.s + cpp $(ASM_FLAGS) <$< | grep -v '^#' >$*.tmp + $(ASM) -o $@ $*.tmp + rm $*.tmp + +ASSEMBLY_SOURCE=$(arch)-gas +ifeq (itanium,$(arch)) + ASM=ias + TBB_ASM.OBJ = atomic_support.o lock_byte.o log2.o pause.o +endif +#------------------------------------------------------------------------------ +# End of setting assembler data. +#------------------------------------------------------------------------------ + +#------------------------------------------------------------------------------ +# Setting tbbmalloc data. +#------------------------------------------------------------------------------ +M_INCLUDES = $(INCLUDES) -I$(MALLOC_ROOT) -I$(MALLOC_SOURCE_ROOT) +M_CPLUS_FLAGS = $(CPLUS_FLAGS) -fno-rtti -fno-exceptions -fno-schedule-insns2 +#------------------------------------------------------------------------------ +# End of setting tbbmalloc data. +#------------------------------------------------------------------------------ diff -r 627751b671bb -r ac2c116b7cee build/freebsd.inc --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/build/freebsd.inc Sat Sep 29 16:51:17 2007 -0700 @@ -0,0 +1,86 @@ +# Copyright 2005-2007 Intel Corporation. All Rights Reserved. +# +# This file is part of Threading Building Blocks. +# +# Threading Building Blocks is free software; you can redistribute it +# and/or modify it under the terms of the GNU General Public License +# version 2 as published by the Free Software Foundation. +# +# Threading Building Blocks is distributed in the hope that it will be +# useful, but WITHOUT ANY WARRANTY; without even the implied warranty +# of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +# GNU General Public License for more details. +# +# You should have received a copy of the GNU General Public License +# along with Threading Building Blocks; if not, write to the Free Software +# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +# +# As a special exception, you may use this file as part of a free software +# library without restriction. Specifically, if other files instantiate +# templates or use macros or inline functions from this file, or you compile +# this file and link it with other files to produce an executable, this +# file does not by itself cause the resulting executable to be covered by +# the GNU General Public License. This exception does not however +# invalidate any other reasons why the executable file might be covered by +# the GNU General Public License. + +ifndef arch + ifeq ($(shell uname -m),i686) + export arch:=ia32 + endif + ifeq ($(shell uname -m),ia64) + export arch:=itanium + endif + ifeq ($(shell uname -m),amd64) + export arch:=em64t + endif +endif + +ifndef runtime + gcc_version_full=$(shell gcc --version | grep 'gcc'| egrep -o ' [0-9]+\.[0-9]+\.[0-9]+.*' | sed -e 's/^\ //') + gcc_version=$(shell echo "$(gcc_version_full)" | egrep -o '^[0-9]+\.[0-9]+\.[0-9]+\s*' | head -n 1 | sed -e 's/ *//g') + os_version:=$(shell uname -r) + os_kernel_version:=$(shell uname -r | sed -e 's/-.*$$//') + export runtime:=cc$(os_version) +endif + +native_compiler := gcc +export compiler ?= gcc +debugger ?= gdb + +CWD=$(shell pwd) +RM?=rm -f +RD?=rmdir +MD?=mkdir -p +NUL= > /dev/null 2>&1 +SLASH=/ +MAKE_VERSIONS=sh $(tbb_root)/build/version_info_linux.sh $(CPLUS) $(CPLUS_FLAGS) $(INCLUDES) >version_string.tmp +MAKE_TBBVARS=sh $(tbb_root)/build/generate_tbbvars.sh + +ifdef LD_LIBRARY_PATH + export LD_LIBRARY_PATH := .:$(LD_LIBRARY_PATH) +else + export LD_LIBRARY_PATH := . +endif + +####### Build settigns ######################################################## + +OBJ = o +DLL = so +LIBEXT = so + +ifeq ($(cfg),debug) + DEBUG_SUFFIX = _debug +endif + +TBB.DEF = +TBB.DLL = libtbb$(DEBUG_SUFFIX).$(DLL) +TBB.LIB = $(TBB.DLL) + +MALLOC.DLL = libtbbmalloc$(DEBUG_SUFFIX).so +MALLOC.LIB = $(MALLOC.DLL) + +TBB_NOSTRICT=1 + + + diff -r 627751b671bb -r ac2c116b7cee examples/common/gui/convideo.cpp --- a/examples/common/gui/convideo.cpp Sat Sep 29 16:18:03 2007 -0700 +++ b/examples/common/gui/convideo.cpp Sat Sep 29 16:51:17 2007 -0700 @@ -48,7 +48,7 @@ void video::win_load_accelerators(int id } #endif -#elif __linux__ || __APPLE__ +#elif __linux__ || __APPLE__ || __FreeBSD__ #include #include diff -r 627751b671bb -r ac2c116b7cee examples/parallel_for/tacheon/src/types.h --- a/examples/parallel_for/tacheon/src/types.h Sat Sep 29 16:18:03 2007 -0700 +++ b/examples/parallel_for/tacheon/src/types.h Sat Sep 29 16:51:17 2007 -0700 @@ -61,6 +61,8 @@ #ifdef _WIN32 #include #define alloca _alloca +#elif __FreeBSD__ +#include #else #include #endif diff -r 627751b671bb -r ac2c116b7cee examples/parallel_reduce/convex_hull/convex_hull.h --- a/examples/parallel_reduce/convex_hull/convex_hull.h Sat Sep 29 16:18:03 2007 -0700 +++ b/examples/parallel_reduce/convex_hull/convex_hull.h Sat Sep 29 16:51:17 2007 -0700 @@ -133,7 +133,7 @@ namespace util { }; int random(unsigned int& rseed) { -#if __linux__ || __APPLE__ +#if __linux__ || __APPLE__ || __FreeBSD__ return rand_r(&rseed); #elif _WIN32 return rand(); diff -r 627751b671bb -r ac2c116b7cee include/tbb/machine/freebsd_em64t.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/include/tbb/machine/freebsd_em64t.h Sat Sep 29 16:51:17 2007 -0700 @@ -0,0 +1,160 @@ +/* + Copyright 2005-2007 Intel Corporation. All Rights Reserved. + + This file is part of Threading Building Blocks. + + Threading Building Blocks is free software; you can redistribute it + and/or modify it under the terms of the GNU General Public License + version 2 as published by the Free Software Foundation. + + Threading Building Blocks is distributed in the hope that it will be + useful, but WITHOUT ANY WARRANTY; without even the implied warranty + of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with Threading Building Blocks; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + As a special exception, you may use this file as part of a free software + library without restriction. Specifically, if other files instantiate + templates or use macros or inline functions from this file, or you compile + this file and link it with other files to produce an executable, this + file does not by itself cause the resulting executable to be covered by + the GNU General Public License. This exception does not however + invalidate any other reasons why the executable file might be covered by + the GNU General Public License. +*/ + +#ifndef __TBB_machine_H +#error Do not include this file directly; include tbb_machine.h instead +#endif + +#include +#include +#include + +#define __TBB_OFFSET_OF_NEXT -8 +#define __TBB_WORDSIZE 8 +#define __TBB_BIG_ENDIAN 0 + +//! Load with acquire semantics, both for hardware and compiler. +template +inline T __TBB_load_with_acquire_via_explicit_fence(const volatile T& location) { + T tmp = location; + __asm__ __volatile__("": : :"memory"); + return tmp; +} + +//! Store with release semantics, both for hardware and compiler. +template +inline void __TBB_store_with_release_via_explicit_fence(volatile T& location, V value) { + __asm__ __volatile__("": : :"memory"); + location = value; +} + +#define __TBB_load_with_acquire __TBB_load_with_acquire_via_explicit_fence +#define __TBB_store_with_release __TBB_store_with_release_via_explicit_fence + +#define __MACHINE_DECL_ATOMICS(S,T,X) \ +static inline T __TBB_machine_cmpswp##S (volatile void *ptr, T value, T comparand ) \ +{ \ + T result; \ + \ + __asm__ __volatile__("lock\ncmpxchg" X " %2,%1" \ + : "=a"(result), "=m"(*(T *)ptr) \ + : "q"(value), "0"(comparand) \ + : "memory"); \ + return result; \ +} \ + \ +static inline T __TBB_machine_fetchadd##S(volatile void *ptr, T addend) \ +{ \ + T result; \ + __asm__ __volatile__("lock\nxadd" X " %0,%1" \ + : "=r"(result),"=m"(*(T *)ptr) \ + : "0"(addend) \ + : "memory"); \ + return result; \ +} \ + \ +static inline T __TBB_machine_fetchstore##S(volatile void *ptr, T value) \ +{ \ + T result; \ + __asm__ __volatile__("lock\nxchg" X " %0,%1" \ + : "=r"(result),"=m"(*(T *)ptr) \ + : "0"(value) \ + : "memory"); \ + return result; \ +} \ + +__MACHINE_DECL_ATOMICS(1,int8_t,"") +__MACHINE_DECL_ATOMICS(2,int16_t,"") +__MACHINE_DECL_ATOMICS(4,int32_t,"") +__MACHINE_DECL_ATOMICS(8,int64_t,"q") + +static inline int64_t __TBB_machine_lg( uint64_t x ) { + int64_t j; + __asm__ ("bsr %1,%0" : "=r"(j) : "r"(x)); + return j; +} + +static inline void __TBB_machine_or( volatile void *ptr, uint64_t addend ) { + __asm__ __volatile__("lock\norq %1,%0" : "=m"(*(uint64_t *)ptr) : "r"(addend) : "memory"); +} + +static inline void __TBB_machine_pause( int32_t delay ) { + for (int32_t i = 0; i < delay; i++) { + __asm__ __volatile__("pause;"); + } + return; +} + +// Machine specific atomic operations + +#define __TBB_CompareAndSwap1(P,V,C) __TBB_machine_cmpswp1(P,V,C) +#define __TBB_CompareAndSwap2(P,V,C) __TBB_machine_cmpswp2(P,V,C) +#define __TBB_CompareAndSwap4(P,V,C) __TBB_machine_cmpswp4(P,V,C) +#define __TBB_CompareAndSwap8(P,V,C) __TBB_machine_cmpswp8(P,V,C) +#define __TBB_CompareAndSwapW(P,V,C) __TBB_machine_cmpswp8(P,V,C) + +#define __TBB_FetchAndAdd1(P,V) __TBB_machine_fetchadd1(P,V) +#define __TBB_FetchAndAdd2(P,V) __TBB_machine_fetchadd2(P,V) +#define __TBB_FetchAndAdd4(P,V) __TBB_machine_fetchadd4(P,V) +#define __TBB_FetchAndAdd8(P,V) __TBB_machine_fetchadd8(P,V) +#define __TBB_FetchAndAddW(P,V) __TBB_machine_fetchadd8(P,V) + +#define __TBB_FetchAndStore1(P,V) __TBB_machine_fetchstore1(P,V) +#define __TBB_FetchAndStore2(P,V) __TBB_machine_fetchstore2(P,V) +#define __TBB_FetchAndStore4(P,V) __TBB_machine_fetchstore4(P,V) +#define __TBB_FetchAndStore8(P,V) __TBB_machine_fetchstore8(P,V) +#define __TBB_FetchAndStoreW(P,V) __TBB_machine_fetchstore8(P,V) + +#define __TBB_Store8(P,V) (*P = V) +#define __TBB_Load8(P) (*P) + +#define __TBB_AtomicOR(P,V) __TBB_machine_or(P,V) + +// Definition of other functions +#define __TBB_Yield() sched_yield() +#define __TBB_Pause(V) __TBB_machine_pause(V) +#define __TBB_Log2(V) __TBB_machine_lg(V) + +// Special atomic functions +#define __TBB_FetchAndAddWrelease(P,V) __TBB_FetchAndAddW(P,V) +#define __TBB_FetchAndIncrementWacquire(P) __TBB_FetchAndAddW(P,1) +#define __TBB_FetchAndDecrementWrelease(P) __TBB_FetchAndAddW(P,-1) + +// Definition of Lock functions +#undef __TBB_TryLockByte +#undef __TBB_LockByte + +#define __TBB_cpuid +static inline void __TBB_x86_cpuid( int32_t buffer[4], int32_t mode ) { + // NOTE: gcc sometimes fails to compile the following asm. But icc always succeeds. + __asm__ ("cpuid" : "=a"(buffer[0]), + "=b"(buffer[1]), + "=c"(buffer[2]), + "=d"(buffer[3]) : "0"(mode) : "memory" ); +} + diff -r 627751b671bb -r ac2c116b7cee include/tbb/machine/freebsd_ia32.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/include/tbb/machine/freebsd_ia32.h Sat Sep 29 16:51:17 2007 -0700 @@ -0,0 +1,225 @@ +/* + Copyright 2005-2007 Intel Corporation. All Rights Reserved. + + This file is part of Threading Building Blocks. + + Threading Building Blocks is free software; you can redistribute it + and/or modify it under the terms of the GNU General Public License + version 2 as published by the Free Software Foundation. + + Threading Building Blocks is distributed in the hope that it will be + useful, but WITHOUT ANY WARRANTY; without even the implied warranty + of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with Threading Building Blocks; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + As a special exception, you may use this file as part of a free software + library without restriction. Specifically, if other files instantiate + templates or use macros or inline functions from this file, or you compile + this file and link it with other files to produce an executable, this + file does not by itself cause the resulting executable to be covered by + the GNU General Public License. This exception does not however + invalidate any other reasons why the executable file might be covered by + the GNU General Public License. +*/ + +#ifndef __TBB_machine_H +#error Do not include this file directly; include tbb_machine.h instead +#endif + +#include +#include +#include + +#define __TBB_OFFSET_OF_NEXT -4 +#define __TBB_WORDSIZE 4 +#define __TBB_BIG_ENDIAN 0 + + +#define __MACHINE_DECL_ATOMICS(S,T,X) \ +static inline T __TBB_machine_cmpswp##S (volatile void *ptr, T value, T comparand ) \ +{ \ + T result; \ + \ + __asm__ __volatile__("lock\ncmpxchg" X " %2,%1" \ + : "=a"(result), "=m"(*(T *)ptr) \ + : "q"(value), "0"(comparand) \ + : "memory"); \ + return result; \ +} \ + \ +static inline T __TBB_machine_fetchadd##S(volatile void *ptr, T addend) \ +{ \ + T result; \ + __asm__ __volatile__("lock\nxadd" X " %0,%1" \ + : "=r"(result), "=m"(*(T *)ptr) \ + : "0"(addend) \ + : "memory"); \ + return result; \ +} \ + \ +static inline T __TBB_machine_fetchstore##S(volatile void *ptr, T value) \ +{ \ + T result; \ + __asm__ __volatile__("lock\nxchg" X " %0,%1" \ + : "=r"(result), "=m"(*(T *)ptr) \ + : "0"(value) \ + : "memory"); \ + return result; \ +} \ + +__MACHINE_DECL_ATOMICS(1,int8_t,"") +__MACHINE_DECL_ATOMICS(2,int16_t,"") +__MACHINE_DECL_ATOMICS(4,int32_t,"l") + +static int64_t __TBB_machine_cmpswp8 (volatile void *ptr, int64_t value, int64_t comparand ) +{ + const int32_t comparand_lo = (int32_t)comparand; + const int32_t comparand_hi = *(int32_t*)((intptr_t)&comparand+sizeof(int32_t)); + int64_t result; + // EBX register saved for compliancy with position-independent code (PIC) rules on IA32 + __asm__ __volatile__ ( + "pushl %%ebx\n\t" + "movl (%%ecx),%%ebx\n\t" + "movl 4(%%ecx),%%ecx\n\t" + "lock\ncmpxchg8b (%2)\n\t" + "popl %%ebx" + : "=A"(result), "=m"(*(int64_t *)ptr) + : "S"(ptr), + "a"(comparand_lo), + "d"(comparand_hi), + "c"(&value) + : "memory", "esp"); + return result; +} + +static inline int32_t __TBB_machine_lg( uint32_t x ) { + int32_t j; + __asm__ ("bsr %1,%0" : "=r"(j) : "r"(x)); + return j; +} + +static inline void __TBB_machine_or( volatile void *ptr, uint32_t addend ) { + __asm__ __volatile__("lock\norl %1,%0" : "=m"(*(uint32_t *)ptr) : "r"(addend) : "memory"); +} + +static inline void __TBB_machine_pause( int32_t delay ) { + for (int32_t i = 0; i < delay; i++) { + __asm__ __volatile__("pause;"); + } + return; +} + +static inline int64_t __TBB_machine_load8 (const volatile void *ptr) { + int64_t result; + __asm__ __volatile__ ( "fildq %1\n\t" + "fistpq %0" : "=m"(result) : "m"(*(uint64_t *)ptr), "m"(result) : "memory" ); + return result; +} + +static inline void __TBB_machine_store8 (volatile void *ptr, int64_t value) { + __asm__ __volatile__ ( "fildq %1\n\t" + "fistpq (%2)" : "=m"(*(int64_t *)ptr) : "m"(value), "r"(ptr) : "memory" ); +} + +template +struct __TBB_machine_load_store { + static inline T load_with_acquire(const volatile T& location) { + T to_return = location; + __asm__ __volatile__("" : : : "memory" ); // Compiler fence to keep operations from migrating upwards + return to_return; + } + + static inline void store_with_release(volatile T &location, T value) { + __asm__ __volatile__("" : : : "memory" ); // Compiler fence to keep operations from migrating upwards + location = value; + } +}; + +template +struct __TBB_machine_load_store { + static inline T load_with_acquire(const volatile T& location) { + T to_return = __TBB_machine_load8((volatile void *)&location); + __asm__ __volatile__("" : : : "memory" ); // Compiler fence to keep operations from migrating upwards + return to_return; + } + + static inline void store_with_release(volatile T &location, T value) { + __asm__ __volatile__("" : : : "memory" ); // Compiler fence to keep operations from migrating downwards + __TBB_machine_store8((volatile void *)&location,(int64_t)value); + } +}; + +template +inline T __TBB_machine_load_with_acquire(const volatile T &location) { + return __TBB_machine_load_store::load_with_acquire(location); +} + +template +inline void __TBB_machine_store_with_release(volatile T &location, V value) { + __TBB_machine_load_store::store_with_release(location,value); +} + +#define __TBB_load_with_acquire(L) __TBB_machine_load_with_acquire((L)) +#define __TBB_store_with_release(L,V) __TBB_machine_store_with_release((L),(V)) + +// Machine specific atomic operations + +#define __TBB_CompareAndSwap1(P,V,C) __TBB_machine_cmpswp1(P,V,C) +#define __TBB_CompareAndSwap2(P,V,C) __TBB_machine_cmpswp2(P,V,C) +#define __TBB_CompareAndSwap4(P,V,C) __TBB_machine_cmpswp4(P,V,C) +#define __TBB_CompareAndSwap8(P,V,C) __TBB_machine_cmpswp8(P,V,C) +#define __TBB_CompareAndSwapW(P,V,C) __TBB_machine_cmpswp4(P,V,C) + +#define __TBB_FetchAndAdd1(P,V) __TBB_machine_fetchadd1(P,V) +#define __TBB_FetchAndAdd2(P,V) __TBB_machine_fetchadd2(P,V) +#define __TBB_FetchAndAdd4(P,V) __TBB_machine_fetchadd4(P,V) +#define __TBB_FetchAndAddW(P,V) __TBB_machine_fetchadd4(P,V) + +#define __TBB_FetchAndStore1(P,V) __TBB_machine_fetchstore1(P,V) +#define __TBB_FetchAndStore2(P,V) __TBB_machine_fetchstore2(P,V) +#define __TBB_FetchAndStore4(P,V) __TBB_machine_fetchstore4(P,V) +#define __TBB_FetchAndStoreW(P,V) __TBB_machine_fetchstore4(P,V) + +#define __TBB_Store8(P,V) __TBB_machine_store8(P,V) +#define __TBB_Load8(P) __TBB_machine_load8(P) + +#define __TBB_AtomicOR(P,V) __TBB_machine_or(P,V) + + +// Those we chose not to implement (they will be implemented generically using CMPSWP8) +#undef __TBB_FetchAndAdd8 +#undef __TBB_FetchAndStore8 + +// Definition of other functions +#define __TBB_Yield() sched_yield() +#define __TBB_Pause(V) __TBB_machine_pause(V) +#define __TBB_Log2(V) __TBB_machine_lg(V) + +// Special atomic functions +#define __TBB_FetchAndAddWrelease(P,V) __TBB_FetchAndAddW(P,V) +#define __TBB_FetchAndIncrementWacquire(P) __TBB_FetchAndAddW(P,1) +#define __TBB_FetchAndDecrementWrelease(P) __TBB_FetchAndAddW(P,-1) + +// Definition of Lock functions +#undef __TBB_TryLockByte +#undef __TBB_LockByte + +#define __TBB_cpuid +static inline void __TBB_x86_cpuid( int32_t buffer[4], int32_t mode ) { + // EBX register saved for compliancy with position-independent code (PIC) rules on IA32 + __asm__ ("pushl %%ebx\n\t" + "cpuid\n\t" + "movl %%ebx,%1\n\t" + "popl %%ebx" + : "=a"(buffer[0]), + "=S"(buffer[1]), + "=c"(buffer[2]), + "=d"(buffer[3]) + : "0"(mode) + : "memory" ); +} + diff -r 627751b671bb -r ac2c116b7cee include/tbb/machine/freebsd_itanium.h --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/include/tbb/machine/freebsd_itanium.h Sat Sep 29 16:51:17 2007 -0700 @@ -0,0 +1,179 @@ +/* + Copyright 2005-2007 Intel Corporation. All Rights Reserved. + + This file is part of Threading Building Blocks. + + Threading Building Blocks is free software; you can redistribute it + and/or modify it under the terms of the GNU General Public License + version 2 as published by the Free Software Foundation. + + Threading Building Blocks is distributed in the hope that it will be + useful, but WITHOUT ANY WARRANTY; without even the implied warranty + of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with Threading Building Blocks; if not, write to the Free Software + Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA + + As a special exception, you may use this file as part of a free software + library without restriction. Specifically, if other files instantiate + templates or use macros or inline functions from this file, or you compile + this file and link it with other files to produce an executable, this + file does not by itself cause the resulting executable to be covered by + the GNU General Public License. This exception does not however + invalidate any other reasons why the executable file might be covered by + the GNU General Public License. +*/ + +#ifndef __TBB_machine_H +#error Do not include this file directly; include tbb_machine.h instead +#endif + +#include +#include +#include +#include + +#define __TBB_OFFSET_OF_NEXT -8 +#define __TBB_WORDSIZE 8 +#define __TBB_BIG_ENDIAN 0 +#define __TBB_DECL_FENCED_ATOMICS 1 + +// Most of the functions will be in a .s file + +extern "C" { + int8_t __TBB_machine_cmpswp1__TBB_full_fence (volatile void *ptr, int8_t value, int8_t comparand); + int8_t __TBB_machine_fetchadd1__TBB_full_fence (volatile void *ptr, int8_t addend); + int8_t __TBB_machine_fetchadd1acquire(volatile void *ptr, int8_t addend); + int8_t __TBB_machine_fetchadd1release(volatile void *ptr, int8_t addend); + int8_t __TBB_machine_fetchstore1acquire(volatile void *ptr, int8_t value); + int8_t __TBB_machine_fetchstore1release(volatile void *ptr, int8_t value); + + int16_t __TBB_machine_cmpswp2__TBB_full_fence (volatile void *ptr, int16_t value, int16_t comparand); + int16_t __TBB_machine_fetchadd2__TBB_full_fence (volatile void *ptr, int16_t addend); + int16_t __TBB_machine_fetchadd2acquire(volatile void *ptr, int16_t addend); + int16_t __TBB_machine_fetchadd2release(volatile void *ptr, int16_t addend); + int16_t __TBB_machine_fetchstore2acquire(volatile void *ptr, int16_t value); + int16_t __TBB_machine_fetchstore2release(volatile void *ptr, int16_t value); + + int32_t __TBB_machine_fetchstore4__TBB_full_fence (volatile void *ptr, int32_t value); + int32_t __TBB_machine_fetchstore4acquire(volatile void *ptr, int32_t value); + int32_t __TBB_machine_fetchstore4release(volatile void *ptr, int32_t value); + int32_t __TBB_machine_fetchadd4acquire(volatile void *ptr, int32_t addend); + int32_t __TBB_machine_fetchadd4release(volatile void *ptr, int32_t addend); + + int64_t __TBB_machine_cmpswp8__TBB_full_fence (volatile void *ptr, int64_t value, int64_t comparand); + int64_t __TBB_machine_fetchstore8__TBB_full_fence (volatile void *ptr, int64_t value); + int64_t __TBB_machine_fetchstore8acquire(volatile void *ptr, int64_t value); + int64_t __TBB_machine_fetchstore8release(volatile void *ptr, int64_t value); + int64_t __TBB_machine_fetchadd8acquire(volatile void *ptr, int64_t addend); + int64_t __TBB_machine_fetchadd8release(volatile void *ptr, int64_t addend); + + int8_t __TBB_machine_cmpswp1acquire(volatile void *ptr, int8_t value, int8_t comparand); + int8_t __TBB_machine_cmpswp1release(volatile void *ptr, int8_t value, int8_t comparand); + int8_t __TBB_machine_fetchstore1__TBB_full_fence (volatile void *ptr, int8_t value); + + int16_t __TBB_machine_cmpswp2acquire(volatile void *ptr, int16_t value, int16_t comparand); + int16_t __TBB_machine_cmpswp2release(volatile void *ptr, int16_t value, int16_t comparand); + int16_t __TBB_machine_fetchstore2__TBB_full_fence (volatile void *ptr, int16_t value); + + int32_t __TBB_machine_cmpswp4__TBB_full_fence (volatile void *ptr, int32_t value, int32_t comparand); + int32_t __TBB_machine_cmpswp4acquire(volatile void *ptr, int32_t value, int32_t comparand); + int32_t __TBB_machine_cmpswp4release(volatile void *ptr, int32_t value, int32_t comparand); + int32_t __TBB_machine_fetchadd4__TBB_full_fence (volatile void *ptr, int32_t value); + + int64_t __TBB_machine_cmpswp8acquire(volatile void *ptr, int64_t value, int64_t comparand); + int64_t __TBB_machine_cmpswp8release(volatile void *ptr, int64_t value, int64_t comparand); + int64_t __TBB_machine_fetchadd8__TBB_full_fence (volatile void *ptr, int64_t value); + + int64_t __TBB_machine_lg(uint64_t value); + void __TBB_machine_pause(int32_t delay); + bool __TBB_machine_trylockbyte( volatile unsigned char &ptr ); +} + +#define __TBB_CompareAndSwap1(P,V,C) __TBB_machine_cmpswp1__TBB_full_fence(P,V,C) +#define __TBB_CompareAndSwap2(P,V,C) __TBB_machine_cmpswp2__TBB_full_fence(P,V,C) + +#define __TBB_FetchAndAdd1(P,V) __TBB_machine_fetchadd1__TBB_full_fence(P,V) +#define __TBB_FetchAndAdd1acquire(P,V) __TBB_machine_fetchadd1acquire(P,V) +#define __TBB_FetchAndAdd1release(P,V) __TBB_machine_fetchadd1release(P,V) +#define __TBB_FetchAndAdd2(P,V) __TBB_machine_fetchadd2__TBB_full_fence(P,V) +#define __TBB_FetchAndAdd2acquire(P,V) __TBB_machine_fetchadd2acquire(P,V) +#define __TBB_FetchAndAdd2release(P,V) __TBB_machine_fetchadd2release(P,V) +#define __TBB_FetchAndAdd4acquire(P,V) __TBB_machine_fetchadd4acquire(P,V) +#define __TBB_FetchAndAdd4release(P,V) __TBB_machine_fetchadd4release(P,V) +#define __TBB_FetchAndAdd8acquire(P,V) __TBB_machine_fetchadd8acquire(P,V) +#define __TBB_FetchAndAdd8release(P,V) __TBB_machine_fetchadd8release(P,V) + +#define __TBB_FetchAndStore1acquire(P,V) __TBB_machine_fetchstore1acquire(P,V) +#define __TBB_FetchAndStore1release(P,V) __TBB_machine_fetchstore1release(P,V) +#define __TBB_FetchAndStore2acquire(P,V) __TBB_machine_fetchstore2acquire(P,V) +#define __TBB_FetchAndStore2release(P,V) __TBB_machine_fetchstore2release(P,V) +#define __TBB_FetchAndStore4acquire(P,V) __TBB_machine_fetchstore4acquire(P,V) +#define __TBB_FetchAndStore4release(P,V) __TBB_machine_fetchstore4release(P,V) +#define __TBB_FetchAndStore8acquire(P,V) __TBB_machine_fetchstore8acquire(P,V) +#define __TBB_FetchAndStore8release(P,V) __TBB_machine_fetchstore8release(P,V) + +#define __TBB_CompareAndSwap1acquire(P,V,C) __TBB_machine_cmpswp1acquire(P,V,C) +#define __TBB_CompareAndSwap1release(P,V,C) __TBB_machine_cmpswp1release(P,V,C) +#define __TBB_CompareAndSwap2acquire(P,V,C) __TBB_machine_cmpswp2acquire(P,V,C) +#define __TBB_CompareAndSwap2release(P,V,C) __TBB_machine_cmpswp2release(P,V,C) +#define __TBB_CompareAndSwap4(P,V,C) __TBB_machine_cmpswp4__TBB_full_fence(P,V,C) +#define __TBB_CompareAndSwap4acquire(P,V,C) __TBB_machine_cmpswp4acquire(P,V,C) +#define __TBB_CompareAndSwap4release(P,V,C) __TBB_machine_cmpswp4release(P,V,C) +#define __TBB_CompareAndSwap8(P,V,C) __TBB_machine_cmpswp8__TBB_full_fence(P,V,C) +#define __TBB_CompareAndSwap8acquire(P,V,C) __TBB_machine_cmpswp8acquire(P,V,C) +#define __TBB_CompareAndSwap8release(P,V,C) __TBB_machine_cmpswp8release(P,V,C) + +#define __TBB_FetchAndAdd4(P,V) __TBB_machine_fetchadd4__TBB_full_fence(P,V) +#define __TBB_FetchAndAdd8(P,V) __TBB_machine_fetchadd8__TBB_full_fence(P,V) + +#define __TBB_FetchAndStore1(P,V) __TBB_machine_fetchstore1__TBB_full_fence(P,V) +#define __TBB_FetchAndStore2(P,V) __TBB_machine_fetchstore2__TBB_full_fence(P,V) +#define __TBB_FetchAndStore4(P,V) __TBB_machine_fetchstore4__TBB_full_fence(P,V) +#define __TBB_FetchAndStore8(P,V) __TBB_machine_fetchstore8__TBB_full_fence(P,V) + +#define __TBB_FetchAndIncrementWacquire(P) __TBB_FetchAndAdd8acquire(P,1) +#define __TBB_FetchAndDecrementWrelease(P) __TBB_FetchAndAdd8release(P,-1) + +#ifndef __INTEL_COMPILER +template +inline void __TBB_store_with_release_via_explicit_fence(volatile T& location, V value) { + __asm__ __volatile__("": : :"memory"); + location = value; +} + +//! Load with acquire semantics, both for hardware and compiler. +/** Even though GCC imbues volatile loads with acquire semantics, + it sometimes hoists loads over the acquire fence. We use + an explicit memory fence to prevent such incorrect hoisting. */ +template +inline T __TBB_load_with_acquire_via_explicit_fence(const volatile T& location) { + T tmp = location; + __asm__ __volatile__("": : :"memory"); + return tmp; +} +#define __TBB_load_with_acquire(L) __TBB_load_with_acquire_via_explicit_fence(L) +#define __TBB_store_with_release(L,V) __TBB_store_with_release_via_explicit_fence(L,V) +#endif + +// Special atomic functions +#define __TBB_CompareAndSwapW(P,V,C) __TBB_CompareAndSwap8(P,V,C) +#define __TBB_FetchAndStoreW(P,V) __TBB_FetchAndStore8(P,V) +#define __TBB_FetchAndAddW(P,V) __TBB_FetchAndAdd8(P,V) +#define __TBB_FetchAndAddWrelease(P,V) __TBB_FetchAndAdd8release(P,V) + +// Not needed +#undef __TBB_Store8 +#undef __TBB_Load8 + +// Definition of Lock functions +#define __TBB_TryLockByte(P) __TBB_machine_trylockbyte(P) +#undef __TBB_LockByte + +// Definition of other utility functions +#define __TBB_Yield() sched_yield() +#define __TBB_Pause(V) __TBB_machine_pause(V) +#define __TBB_Log2(V) __TBB_machine_lg(V) + diff -r 627751b671bb -r ac2c116b7cee include/tbb/tbb_machine.h --- a/include/tbb/tbb_machine.h Sat Sep 29 16:18:03 2007 -0700 +++ b/include/tbb/tbb_machine.h Sat Sep 29 16:51:17 2007 -0700 @@ -65,6 +65,16 @@ typedef unsigned __int64 uint64_t; #include "tbb/machine/linux_em64t.h" #elif __ia64__ #include "tbb/machine/linux_itanium.h" +#endif + +#elif __FreeBSD__ + +#if __i386__ +#include "tbb/machine/freebsd_ia32.h" +#elif __x86_64__ +#include "tbb/machine/freebsd_em64t.h" +#elif __ia64__ +#include "tbb/machine/freebsd_itanium.h" #endif #elif __APPLE__ diff -r 627751b671bb -r ac2c116b7cee src/tbb/cache_aligned_allocator.cpp --- a/src/tbb/cache_aligned_allocator.cpp Sat Sep 29 16:18:03 2007 -0700 +++ b/src/tbb/cache_aligned_allocator.cpp Sat Sep 29 16:51:17 2007 -0700 @@ -69,7 +69,7 @@ static const DynamicLinkDescriptor Mallo #define MALLOCLIB_NAME "tbbmalloc" DEBUG_SUFFIX ".dll" #elif __APPLE__ #define MALLOCLIB_NAME "libtbbmalloc" DEBUG_SUFFIX ".dylib" -#elif __linux__ +#elif __linux__ || __FreeBSD__ #define MALLOCLIB_NAME "libtbbmalloc" DEBUG_SUFFIX ".so" #else #error Unknown OS diff -r 627751b671bb -r ac2c116b7cee src/tbb/itt_notify.cpp --- a/src/tbb/itt_notify.cpp Sat Sep 29 16:18:03 2007 -0700 +++ b/src/tbb/itt_notify.cpp Sat Sep 29 16:51:17 2007 -0700 @@ -70,7 +70,7 @@ static const DynamicLinkDescriptor ITT_H // LIBITTNOTIFY_NAME is the name of the ITT notification library # if _WIN32||_WIN64 # define LIBITTNOTIFY_NAME "libittnotify.dll" -# elif __linux__ +# elif __linux__ || __FreeBSD__ # define LIBITTNOTIFY_NAME "libittnotify.so" # elif __APPLE__ # define LIBITTNOTIFY_NAME "libittnotify.dylib" diff -r 627751b671bb -r ac2c116b7cee src/tbb/tbb_misc.h --- a/src/tbb/tbb_misc.h Sat Sep 29 16:18:03 2007 -0700 +++ b/src/tbb/tbb_misc.h Sat Sep 29 16:51:17 2007 -0700 @@ -32,11 +32,8 @@ #include "tbb/tbb_stddef.h" #include "tbb/tbb_machine.h" -#if __linux__ -#include -#elif __APPLE__ -#include -#include +#if defined(__linux__) || defined(__APPLE__) || defined(__FreeBSD__) +#include #endif namespace tbb { @@ -59,24 +56,11 @@ static inline int DetectNumberOfWorkers( return number_of_workers; } -#elif __linux__ +#elif defined(__linux__) || defined(__APPLE__) || defined(__FreeBSD__) static inline int DetectNumberOfWorkers( void ) { if (!number_of_workers) { - number_of_workers = get_nprocs(); - } - return number_of_workers; -} - -#elif __APPLE__ - -static inline int DetectNumberOfWorkers( void ) { - if (!number_of_workers) { - int name[2] = {CTL_HW, HW_AVAILCPU}; - int ncpu; - size_t size = sizeof(ncpu); - sysctl( name, 2, &ncpu, &size, NULL, 0 ); - number_of_workers = ncpu; + number_of_workers = sysconf(_SC_NPROCESSORS_ONLN); } return number_of_workers; } diff -r 627751b671bb -r ac2c116b7cee src/tbbmalloc/MemoryAllocator.cpp --- a/src/tbbmalloc/MemoryAllocator.cpp Sat Sep 29 16:18:03 2007 -0700 +++ b/src/tbbmalloc/MemoryAllocator.cpp Sat Sep 29 16:51:17 2007 -0700 @@ -324,7 +324,7 @@ static inline unsigned int highestBitPos unsigned int pos; #if __ARCH_x86_32||__ARCH_x86_64 -# if __linux__||__APPLE__ +# if __linux__||__APPLE__ || __FreeBSD__ __asm__ ("bsr %1,%0" : "=r"(pos) : "r"(number)); # elif (_WIN32 && (!_WIN64 || __INTEL_COMPILER)) __asm diff -r 627751b671bb -r ac2c116b7cee src/test/harness.h --- a/src/test/harness.h Sat Sep 29 16:18:03 2007 -0700 +++ b/src/test/harness.h Sat Sep 29 16:51:17 2007 -0700 @@ -38,7 +38,7 @@ #include "tbb/tbb_stddef.h" #include "harness_assert.h" -#if __linux__||__APPLE__ +#if __linux__||__APPLE__ || __FreeBSD__ #include #elif _WIN32||WIN64 #include @@ -120,7 +120,7 @@ public: //! Start task void start() { -#if __linux__||__APPLE__ +#if __linux__||__APPLE__ || __FreeBSD__ int status = pthread_create(&thread_id, NULL, thread_function, this); ASSERT(0==status, "NativeParallelFor: pthread_create failed"); #else @@ -132,7 +132,7 @@ public: //! Wait for task to finish void wait_to_finish() { -#if __linux__||__APPLE__ +#if __linux__||__APPLE__ || __FreeBSD__ int status = pthread_join( thread_id, NULL ); ASSERT( !status, "pthread_join failed" ); #else @@ -148,7 +148,7 @@ public: Top-level caller should let index default to 0. */ static size_t build_task_array( const Range& range, const Body& body, NativeParalleForTask* array, size_t index ); private: -#if __linux__||__APPLE__ +#if __linux__||__APPLE__ || __FreeBSD__ pthread_t thread_id; #else HANDLE thread_handle; @@ -160,7 +160,7 @@ private: //! Body to invoke over the range. const Body body; -#if __linux__||__APPLE__ +#if __linux__||__APPLE__ || __FreeBSD__ static void* thread_function(void* object) #else static unsigned __stdcall thread_function( void* object ) --- a/src/test/test_concurrent_hash_map.cpp Sat Sep 29 16:51:17 2007 -0700 +++ b/src/test/test_concurrent_hash_map.cpp Sat Sep 29 17:08:18 2007 -0700 @@ -320,7 +320,7 @@ public: // more logical threads than physical threads, and should yield in // order to let suspended logical threads make progress. j = 0; -#if __linux__||__APPLE__ +#if __linux__ || __APPLE__ || __FreeBSD__ sched_yield(); #else Sleep(0);