From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 3 02:23:32 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4BD116A46B for ; Sun, 3 Jun 2007 02:23:32 +0000 (UTC) (envelope-from artifact.one@googlemail.com) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.230]) by mx1.freebsd.org (Postfix) with ESMTP id 94BBA13C457 for ; Sun, 3 Jun 2007 02:23:32 +0000 (UTC) (envelope-from artifact.one@googlemail.com) Received: by wx-out-0506.google.com with SMTP id h28so785920wxd for ; Sat, 02 Jun 2007 19:23:32 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CXp20s2tci6mnUOOmMP2a75lccumE/PwhrqOxZfZOAiKyufuA1Ug/6j0zQMUkdMDunYrUx7WQti5A+AK6N/XslWDOK7ZNAL8Ad4/PrsWk2OyYWhANAn2cdhqyXBVzjRRszDoosa4eGWFUNTIakCQKt9yU9RiOhbUk0KIasP63gA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=IYsMlVf1H+6JFG72UposFtDmdm4SlpviULx4c/Lt2s3eA7OZQjvU6Jc57WgYBrX0/Pm2dGcT1RExG1N397KxJiu8awm/AnrkIUhjFdBAL5AzsvdKIWT6pOgvA44achPz9GxjLwtQO5YwpTTvZWVA2HVUbqu6NTPJbK1KD+i+OjA= Received: by 10.90.28.13 with SMTP id b13mr2824098agb.1180837411917; Sat, 02 Jun 2007 19:23:31 -0700 (PDT) Received: by 10.90.51.1 with HTTP; Sat, 2 Jun 2007 19:23:31 -0700 (PDT) Message-ID: <8e96a0b90706021923i2ef1d95ey909e269f3061ca82@mail.gmail.com> Date: Sun, 3 Jun 2007 03:23:31 +0100 From: "mal content" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: FIFO asymmetry 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, 03 Jun 2007 02:23:33 -0000 Hello. This is related to my earlier email, which I now believe to be unanswerable (so it's probably worth ignoring). Why do FIFOs work asymmetrically with regards to opening for reading or writing? int rfd; int wfd; if (mkfifo("fifo_r", 0600) == -1) die(); rfd = open("fifo_r", O_RDONLY | O_NONBLOCK); if (rfd == -1) die(); if (mkfifo("fifo_w", 0600) == -1) die(); wfd = open("fifo_w", O_WRONLY | O_NONBLOCK); if (wfd == -1) die(); The first open() call will (unless there's a catastrophic error), be successful and will not block, even if there's no writer on the other end of the fifo. The second open() call will fail if there's no reader (ENXIO). Why this irritating difference in functionality? Surely the second open() call should fail and any write() on the fd should return -1 (EWOULDBLOCK) or 0 like the first would in the case of a read()? In a hypothetical program, I would create a FIFO in the filesystem and select for readability (a writer has turned up and has data). I can't do the same in reverse (create a FIFO and select for writability - a reader has turned up and expects data). Is there some sort of rationale for this surprising behaviour (in POSIX or some ancient UNIX docs)? Before anybody tries to shoot me down in flames, I realise this isn't FreeBSD-specific. thanks, MC From owner-freebsd-hackers@FreeBSD.ORG Sun Jun 3 04:32:18 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 97BAD16A46D for ; Sun, 3 Jun 2007 04:32:17 +0000 (UTC) (envelope-from craig@tobuj.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.freebsd.org (Postfix) with ESMTP id 83E4E13C457 for ; Sun, 3 Jun 2007 04:32:15 +0000 (UTC) (envelope-from craig@tobuj.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 23B09110F2; Sat, 2 Jun 2007 23:32:15 -0500 (CDT) Date: Sat, 2 Jun 2007 23:32:13 -0500 From: Craig Boston To: mal content Message-ID: <20070603043203.GA1341@nowhere> Mail-Followup-To: Craig Boston , mal content , freebsd-hackers@freebsd.org References: <8e96a0b90706021557h2168337emb9b7b59a2084530e@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8e96a0b90706021557h2168337emb9b7b59a2084530e@mail.gmail.com> User-Agent: Mutt/1.4.2.2i Cc: freebsd-hackers@freebsd.org Subject: Re: Open FIFO non-blocking but have write() block(?) 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, 03 Jun 2007 04:32:18 -0000 On Sat, Jun 02, 2007 at 11:57:19PM +0100, mal content wrote: > Logging date appears on one, to be read by any external program and > commands are read by the program from the other. I can't speak to the blocking semantics, but if you plan to have more than one process reading at once, FIFOs won't do what you want. I suspect unix sockets are closer to the behavior you're after. IIRC using them in datagram mode may give you the ability to write whether or not anyone is listening. Otherwise you'll have to do the normal listen, accept, select/poll loop. Craig From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 4 09:39:36 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B668116A473 for ; Mon, 4 Jun 2007 09:39:36 +0000 (UTC) (envelope-from Artis.Caune@latnet.lv) Received: from esbens.latnet.lv (esbens.latnet.lv [159.148.19.115]) by mx1.freebsd.org (Postfix) with ESMTP id 64B6A13C4C8 for ; Mon, 4 Jun 2007 09:39:36 +0000 (UTC) (envelope-from Artis.Caune@latnet.lv) Received: from localhost (localhost.localdomain [127.0.0.1]) by esbens.latnet.lv (Postfix) with ESMTP id AEC481743B6 for ; Mon, 4 Jun 2007 12:39:34 +0300 (EEST) X-Virus-Scanned: Debian amavisd-new at esbens.latnet.lv Received: from esbens.latnet.lv ([127.0.0.1]) by localhost (esbens.latnet.lv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdXfa8sktHkb for ; Mon, 4 Jun 2007 12:39:33 +0300 (EEST) Received: from [159.148.108.245] (didii.latnet.lv [159.148.108.245]) by esbens.latnet.lv (Postfix) with ESMTP id 2A49C139FE9 for ; Mon, 4 Jun 2007 12:39:33 +0300 (EEST) Message-ID: <4663DDD4.1020207@latnet.lv> Date: Mon, 04 Jun 2007 12:39:32 +0300 From: Artis Caune User-Agent: Thunderbird 1.5.0.10 (X11/20070327) MIME-Version: 1.0 To: hackers@freebsd.org References: <465FF29B.3010307@latnet.lv> <46604877.7030007@errno.com> In-Reply-To: <46604877.7030007@errno.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: stopping callouts 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, 04 Jun 2007 09:39:36 -0000 Sam Leffler wrote: > > If you use callout_init_mtx then use callout_stop while holding my_mtx; > if the callout is blocked waiting for my_mtx the request will be discarded. > > callout_drain should not be called while holding my_mtx because it can > sleep. > Thanks, than I will use: MTX_LOCK; ... callout_stop(); MTX_UNLOCK; From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 4 19:02:42 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DB5EC16A46B for ; Mon, 4 Jun 2007 19:02:42 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.236]) by mx1.freebsd.org (Postfix) with ESMTP id 6709D13C484 for ; Mon, 4 Jun 2007 19:02:42 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so803898wra for ; Mon, 04 Jun 2007 12:02:41 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type; b=RfjaKjCRVyWuAYwpLDTpXW90I4TSPvgAEmoQ/7Hva3NR25miQ3c5kFo6l5XgdnZKxDHBunuOxFoC2p5T9PBCtV0A0fvTKvDn/CPfPxEPtDbf88tfFgJbaczim+RgE04SRB2kfL/apf9pOzkyzIR3aTFlOhp7bicbYcE54GSpmSY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type; b=qohDV1nONpiJCYFI4nRocd42MSUt/lDJvwu7r3wPxauQgzhuskv2qPbzqlOg+KqHydnLj/Uev0WUG6PAnRHos0vKYjaIRR9HEx+Q7uxQXynSo9ylo/R4UY4xi4xFi96691dpYbsZONMCRb27RB2ck/S3VudzcC9QdArmPj8SfkE= Received: by 10.142.86.7 with SMTP id j7mr234697wfb.1180983761130; Mon, 04 Jun 2007 12:02:41 -0700 (PDT) Received: by 10.142.251.8 with HTTP; Mon, 4 Jun 2007 12:02:41 -0700 (PDT) Message-ID: <440b3e930706041202m7cbc7cap52947ae1d659d115@mail.gmail.com> Date: Mon, 4 Jun 2007 15:02:41 -0400 From: "Ali Mashtizadeh" To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: ZFS Panic on USB "SCSI" Device 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, 04 Jun 2007 19:02:43 -0000 SSBoYXZlIGJlZW4gdXNpbmcgWkZTIG9uIG15IGxhcHRvcCB3aXRoIGEgWkZTIHJvb3Qgd29ya3Mg Zmxhd2xlc3NseS4gVGhlCnByb2JsZW0gaXMgdGhhdCBJIHB1dCBhIFpGUyBmaWxlc3lzdGVtIG9u IG15IGV4dGVybmFsIHVzYiBoYXJkZHJpdmUgd2hpY2gKc2hvd3MgdXAgYXMgImRhMCIgc28gaXQg bG9va3MgbGlrZSBhIHNjc2kgZGV2aWNlLiBBbmQgSSBrZWVwIGdldHRpbmcgQ0FNCmVycm9ycyBz YXlpbmcgbG9naWNhbCBibG9jayBhZGRyZXNzIG91dCBvZiByYW5nZS4gQW0gSSBkb2luZyBzb21l dGhpbmcgd3JvbmcKaXMgdGhlcmUgc29tZSBzcGVjaWFsIHRoaW5nIEkgbmVlZCB0byBkbz8gVGhl IGVycm9ycyBhcmUgb2theSBhdCBmaXJzdCBidXQKYWZ0ZXIgYSBjb3VwbGUgb2YgdGhlbSBpdCBQ QU5JQ3MuIEluIGNhc2UgeW91ciB3b25kZXJpbmcgaXRzIE9OTFkgWkZTLCBVRlMKYW5kIHRoZSBN U0RPUyBwYXJ0aXRpb25zIHdvcmsgZmluZSBvbiB0aGUgc2FtZSBkcml2ZS4KCk15IGJ1aWxkIG9m IGN1cnJlbnQgaXMgYWJvdXQgYSB3ZWVrIG9sZC4KCi0tIApBbGkgTWFzaHRpemFkZWgK2LnZhNuM INmF2LTYqtuMINiy2KfYr9mHCg== From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 4 19:33:56 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C51F16A469 for ; Mon, 4 Jun 2007 19:33:56 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by mx1.freebsd.org (Postfix) with ESMTP id 69BAC13C458 for ; Mon, 4 Jun 2007 19:33:55 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by wr-out-0506.google.com with SMTP id 69so812219wra for ; Mon, 04 Jun 2007 12:33:54 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:references; b=mWxZHPELpxB25/TLPdZJmGLv/YIsfQFbenNDFotOxk82ZHg0fAjlWrzUuaX7motrt+sxfGFrls1U1XnrlEwkQaf3K0+JwOGTfCnluvlYa0xK4uJpd9MTU6EsoGzB5wpd9eePi/xi2FzcFc42XMAVCWl2+P1UJ56uIFRK7Hemkww= 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:references; b=W1lCCjZ/l5vPtC+SBTGYM0qfDt2CYHqXuRT3vVkTPLsWmaUqyVxqqg3JfVUb9PVjpmwkUmkDOV4KA613vZzA2qhxrwKgZtQoIeINSs7HAyphYs2dEukPjOG8x6B3+px7po+yXFdySgmaJC53cTaT8H2U9U3ovj0/va52yLaMuYQ= Received: by 10.100.191.5 with SMTP id o5mr2776266anf.1180985634093; Mon, 04 Jun 2007 12:33:54 -0700 (PDT) Received: by 10.100.32.4 with HTTP; Mon, 4 Jun 2007 12:33:54 -0700 (PDT) Message-ID: Date: Mon, 4 Jun 2007 21:33:54 +0200 From: "Harald Servat" To: "Nikolay Pavlov" , "Harald Servat" , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org In-Reply-To: <20070604192947.GA74531@zone3000.net> MIME-Version: 1.0 References: <20070604192947.GA74531@zone3000.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: testers wanted for PAPI / 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: Mon, 04 Jun 2007 19:33:56 -0000 Hello, What is the result of dmesg | grep hwpmc? Regards, 2007/6/4, Nikolay Pavlov : > > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > > Hello, > > > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try > to > > the package I'm porting. It would be great to have more feedback than > just > > that my laptop is able to provide me :) > > > > First of all, you can download the code at > > > > http://code.google.com/p/papi-for-freebsd > > > > Next, see man hwpmc(4) and compile a kernel with > > options HWPMC_HOOKS > > device hwpmc > > > > (you'll require device apic if you're running on i386 machines). > > > > When you boot your dmesg should print something like > > hwpmc: TSC/1/0x20 P6/2/0x1fe > > > > Once the machine is up and running, just untar the file you've > downloaded, > > run ./configure and just run make (not make install). > > > > Could you send me the output of the following commands? > > > > # dmesg | grep hwpmc > > # utils/papi_avail > > # utils/papi_decode > > # utils/papi_native_avail > > # ctests/low-level > > # ctests/high-level > > > > Thank you very much, > > Hi Harald. I have an error while running configure script: > > root@orion:~/papi/papi-3.5.0/src# > ./configure <796> > as_func_failure succeeded. > as_func_failure succeeded. > No shell found that supports shell functions. > Please tell autoconf@gnu.org about your system, > including any error possibly output before this > message > checking for architecture... i386 > checking for OS... freebsd > checking for OS version... 7.0-CURRENT > checking for CPU type... > checking for 32 or 64 bit mode... 32 > checking for debugging build... no > checking for gawk... no > checking for mawk... no > checking for nawk... nawk > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for g77... no > checking for xlf... no > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking whether we are using the GNU Fortran 77 compiler... (cached) yes > checking whether f77 accepts -g... (cached) yes > checking how to run the C preprocessor... gcc -E > checking whether ln -s works... yes > checking whether make sets $(MAKE)... yes > checking for ranlib... ranlib > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking for ffsll... no > checking for working MMTIMER... no > checking for working CLOCK_REALTIME_HR POSIX 1b timer... no > checking for working CLOCK_REALTIME POSIX 1b timer... no > checking for real time clock or cycle counter... cycle > checking for working __thread... yes > checking for high performance thread local storage... __thread > checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no > checking for working per-thread times() timer... no > checking for thread virtual clock or cycle counter... default > checking for /sys/class/perfctr... no > checking for /dev/perfctr... no > checking for /sys/kernel/perfmon/version... no > checking for /proc/perfmon... no > checking for perfctr version... none > checking for perfmon version... none > checking for Makefile to use... configure: error: Error! HWPMC module > seems not to be on the kernel. Have you compiled the kernel with HWPMC? (see > hwpmc(4)) > > However module is there: > > quetzal@viking:~/bugs> cat papi.bug > <1959> > root@orion:~/papi# kldstat -v | grep > hwpmc > <848> > 135 hwpmc > > root@orion:~/bugs# uname > -a <853> > FreeBSD orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Jun > 4 19:33:59 EEST 2007 > root@orion.zone3000.net:/usr/obj/usr/src/sys/GENERIC-PMC i386 > > And i have all required options in kernel config: > > quetzal@orion:~/bugs> grep -i PMC > /sys/i386/conf/GENERIC-PMC > <890> > device hwpmc # Driver (also a loadable module) > options HWPMC_HOOKS # Other necessary kernel hooks > > > -- > ====================================================================== > - Best regards, Nikolay Pavlov. <<<----------------------------------- > ====================================================================== > > -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-hackers@FreeBSD.ORG Mon Jun 4 19:56:25 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C74E16A468 for ; Mon, 4 Jun 2007 19:56:25 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id E369A13C469 for ; Mon, 4 Jun 2007 19:56:24 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 0 with SMTP; 4 Jun 2007 19:29:42 -0000 Date: Mon, 4 Jun 2007 22:29:47 +0300 From: Nikolay Pavlov To: Harald Servat Message-ID: <20070604192947.GA74531@zone3000.net> Mail-Followup-To: Nikolay Pavlov , Harald Servat , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-hackers@freebsd.org, freebsd-performance@freebsd.org, freebsd-hpc@freebsd.org Subject: Re: testers wanted for PAPI / 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: Mon, 04 Jun 2007 19:56:25 -0000 On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > Hello, > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try to > the package I'm porting. It would be great to have more feedback than just > that my laptop is able to provide me :) > > First of all, you can download the code at > > http://code.google.com/p/papi-for-freebsd > > Next, see man hwpmc(4) and compile a kernel with > options HWPMC_HOOKS > device hwpmc > > (you'll require device apic if you're running on i386 machines). > > When you boot your dmesg should print something like > hwpmc: TSC/1/0x20 P6/2/0x1fe > > Once the machine is up and running, just untar the file you've downloaded, > run ./configure and just run make (not make install). > > Could you send me the output of the following commands? > > # dmesg | grep hwpmc > # utils/papi_avail > # utils/papi_decode > # utils/papi_native_avail > # ctests/low-level > # ctests/high-level > > Thank you very much, Hi Harald. I have an error while running configure script: root@orion:~/papi/papi-3.5.0/src# ./configure <796> as_func_failure succeeded. as_func_failure succeeded. No shell found that supports shell functions. Please tell autoconf@gnu.org about your system, including any error possibly output before this message checking for architecture... i386 checking for OS... freebsd checking for OS version... 7.0-CURRENT checking for CPU type... checking for 32 or 64 bit mode... 32 checking for debugging build... no checking for gawk... no checking for mawk... no checking for nawk... nawk checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for g77... no checking for xlf... no checking for f77... f77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether f77 accepts -g... yes checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether we are using the GNU Fortran 77 compiler... (cached) yes checking whether f77 accepts -g... (cached) yes checking how to run the C preprocessor... gcc -E checking whether ln -s works... yes checking whether make sets $(MAKE)... yes checking for ranlib... ranlib checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for ANSI C header files... yes checking for ffsll... no checking for working MMTIMER... no checking for working CLOCK_REALTIME_HR POSIX 1b timer... no checking for working CLOCK_REALTIME POSIX 1b timer... no checking for real time clock or cycle counter... cycle checking for working __thread... yes checking for high performance thread local storage... __thread checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no checking for working per-thread times() timer... no checking for thread virtual clock or cycle counter... default checking for /sys/class/perfctr... no checking for /dev/perfctr... no checking for /sys/kernel/perfmon/version... no checking for /proc/perfmon... no checking for perfctr version... none checking for perfmon version... none checking for Makefile to use... configure: error: Error! HWPMC module seems not to be on the kernel. Have you compiled the kernel with HWPMC? (see hwpmc(4)) However module is there: quetzal@viking:~/bugs> cat papi.bug <1959> root@orion:~/papi# kldstat -v | grep hwpmc <848> 135 hwpmc root@orion:~/bugs# uname -a <853> FreeBSD orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon Jun 4 19:33:59 EEST 2007 root@orion.zone3000.net:/usr/obj/usr/src/sys/GENERIC-PMC i386 And i have all required options in kernel config: quetzal@orion:~/bugs> grep -i PMC /sys/i386/conf/GENERIC-PMC <890> device hwpmc # Driver (also a loadable module) options HWPMC_HOOKS # Other necessary kernel hooks -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 17:13:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6D3CA16A421 for ; Tue, 5 Jun 2007 17:13:20 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.230]) by mx1.freebsd.org (Postfix) with ESMTP id 16FC813C487 for ; Tue, 5 Jun 2007 17:13:19 +0000 (UTC) (envelope-from mashtizadeh@gmail.com) Received: by nz-out-0506.google.com with SMTP id 14so1267546nzn for ; Tue, 05 Jun 2007 10:13:19 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:references; b=AKauar/rytGsdkmkAEOvIJjyCvU1lc05RS0hxXOQwlWlfWfYWghd7kpuJjM6dENtQXTxXh1V1J5wCQA7HjoRR57MLx1UauXOWVGWJasj+cF2Rxsus2gh6fHu4C+GV+eThRZ5XdbRZN0Ce36NWosK3bW/oAOSVuGaeOX1WqBO1BQ= 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:references; b=fUEHZLrCTaFv0PCG8UcfYuzS+zCn2/JGqf4hkUsmZy+39bRQrYb6YBYxtzrGlFjeMRUcNUibE0reJfzxdyMOJ8yg9Q6ZIG8kf25OVRQIJUQ9mdAnc8mL78N/OSeLqjSZhc0LGD/Bu47WwLntm/T7yU15b1vPgKGwOsD8r4rrulM= Received: by 10.142.101.17 with SMTP id y17mr291967wfb.1181063599007; Tue, 05 Jun 2007 10:13:19 -0700 (PDT) Received: by 10.142.251.8 with HTTP; Tue, 5 Jun 2007 10:13:18 -0700 (PDT) Message-ID: <440b3e930706051013n65c171feta10a5872026c8f00@mail.gmail.com> Date: Tue, 5 Jun 2007 13:13:18 -0400 From: "Ali Mashtizadeh" To: freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: <440b3e930706041202m7cbc7cap52947ae1d659d115@mail.gmail.com> MIME-Version: 1.0 References: <440b3e930706041202m7cbc7cap52947ae1d659d115@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: ZFS Panic on USB "SCSI" Device 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, 05 Jun 2007 17:13:20 -0000 SWYgYW55b25lIGlzIGN1cmlvdXMgaXQgc2VlbXMgdGhpcyBpcyBhIHNvbWV3aGF0IHJhbmRvbSBv Y2N1cnJlbmNlLiBJIHRoaW5rCml0cyB1bnJlbGF0ZWQgdG8gWkZTIHByb2JhYmx5IHNvIG5ldmVy bWluZC4gSXQgd29ya3MgZmxhd2xlc3NseSAgbm93IDotKQoKT24gNi80LzA3LCBBbGkgTWFzaHRp emFkZWggPG1hc2h0aXphZGVoQGdtYWlsLmNvbT4gd3JvdGU6Cj4KPiBJIGhhdmUgYmVlbiB1c2lu ZyBaRlMgb24gbXkgbGFwdG9wIHdpdGggYSBaRlMgcm9vdCB3b3JrcyBmbGF3bGVzc2x5LiBUaGUK PiBwcm9ibGVtIGlzIHRoYXQgSSBwdXQgYSBaRlMgZmlsZXN5c3RlbSBvbiBteSBleHRlcm5hbCB1 c2IgaGFyZGRyaXZlIHdoaWNoCj4gc2hvd3MgdXAgYXMgImRhMCIgc28gaXQgbG9va3MgbGlrZSBh IHNjc2kgZGV2aWNlLiBBbmQgSSBrZWVwIGdldHRpbmcgQ0FNCj4gZXJyb3JzIHNheWluZyBsb2dp Y2FsIGJsb2NrIGFkZHJlc3Mgb3V0IG9mIHJhbmdlLiBBbSBJIGRvaW5nIHNvbWV0aGluZyB3cm9u Zwo+IGlzIHRoZXJlIHNvbWUgc3BlY2lhbCB0aGluZyBJIG5lZWQgdG8gZG8/IFRoZSBlcnJvcnMg YXJlIG9rYXkgYXQgZmlyc3QgYnV0Cj4gYWZ0ZXIgYSBjb3VwbGUgb2YgdGhlbSBpdCBQQU5JQ3Mu IEluIGNhc2UgeW91ciB3b25kZXJpbmcgaXRzIE9OTFkgWkZTLCBVRlMKPiBhbmQgdGhlIE1TRE9T IHBhcnRpdGlvbnMgd29yayBmaW5lIG9uIHRoZSBzYW1lIGRyaXZlLgo+Cj4gTXkgYnVpbGQgb2Yg Y3VycmVudCBpcyBhYm91dCBhIHdlZWsgb2xkLgo+Cj4gLS0KPiBBbGkgTWFzaHRpemFkZWgKPiDY udmE24wg2YXYtNiq24wg2LLYp9iv2YcKCgoKCi0tIApBbGkgTWFzaHRpemFkZWgK2LnZhNuMINmF 2LTYqtuMINiy2KfYr9mHCg== From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 17:08:46 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B403F16A468 for ; Tue, 5 Jun 2007 17:08:46 +0000 (UTC) (envelope-from rapopp@eastcentral.edu) Received: from ecmail.eastcentral.edu (ecmail.eastcentral.edu [198.209.216.1]) by mx1.freebsd.org (Postfix) with ESMTP id 908AD13C44B for ; Tue, 5 Jun 2007 17:08:46 +0000 (UTC) (envelope-from rapopp@eastcentral.edu) Received: from barbados.eastcentral.edu (unknown [10.15.0.132]) by ecmail.eastcentral.edu (Postfix) with ESMTP id 64FFA3981C for ; Tue, 5 Jun 2007 11:49:04 -0500 (CDT) From: "Reuben A. Popp" To: freebsd-hackers@freebsd.org Date: Tue, 5 Jun 2007 11:49:44 -0500 User-Agent: KMail/1.9.4 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051149.45787.rapopp@eastcentral.edu> X-Mailman-Approved-At: Tue, 05 Jun 2007 17:26:17 +0000 Subject: kern.ngroups question X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rapopp@eastcentral.edu List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 17:08:46 -0000 Hello all, Can someone explain to me the rationale behind having ngroups_max set to 16 by default? I came across this issue originally when working on our Samba implementation (samba-3 out of ports, running on 6-STABLE). We have some users that belong to a number of groups, some of whom need to belong to more groups than the defined hard limit. On doing a little research, I did come across the PR detailed in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108552, and continued reading the linked thread from March 2003, however this really doesn't explain why the limit is set to 16. Can one adjust the value in syslimits.h on a system and then rebuild world/ports with the expectation this will work, or is the issue more involved then that? Is (or has) there any discussion on raising that number to a larger value? Thanks in advance (doubly so if this is a lame question) Reuben -- Reuben A. Popp Systems Administrator Information Technology Department East Central College 1+ 636 583 5195 x2480 From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 18:49:45 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3962916A469 for ; Tue, 5 Jun 2007 18:49:45 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.freebsd.org (Postfix) with ESMTP id 7B59D13C458 for ; Tue, 5 Jun 2007 18:49:44 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from mail3.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.12.6/8.12.6) with ESMTP id l55I9hws015846; Tue, 5 Jun 2007 20:09:43 +0200 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.6/8.12.6) with ESMTP id l55I9gS9020596; Tue, 5 Jun 2007 20:09:42 +0200 Received: (from localhost) by curry.mchp.siemens.de (8.14.1/8.14.1) id l55I9gER037613; Date: Tue, 5 Jun 2007 20:09:42 +0200 From: Andre Albsmeier To: "Reuben A. Popp" Message-ID: <20070605180942.GA22237@curry.mchp.siemens.de> References: <200706051149.45787.rapopp@eastcentral.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706051149.45787.rapopp@eastcentral.edu> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.14 (2007-02-12) Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups question 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, 05 Jun 2007 18:49:45 -0000 On Tue, 05-Jun-2007 at 11:49:44 -0500, Reuben A. Popp wrote: > Hello all, > > Can someone explain to me the rationale behind having ngroups_max set to 16 by > default? > > I came across this issue originally when working on our Samba implementation > (samba-3 out of ports, running on 6-STABLE). We have some users that belong > to a number of groups, some of whom need to belong to more groups than the > defined hard limit. On doing a little research, I did come across the PR > detailed in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108552, and > continued reading the linked thread from March 2003, however this really > doesn't explain why the limit is set to 16. > > Can one adjust the value in syslimits.h on a system and then rebuild > world/ports with the expectation this will work, or is the issue more > involved then that? Is (or has) there any discussion on raising that number > to a larger value? About 2 years ago I changed it to 64 (all over the place) and recompiled world, kernels, ports and every programme on the boxes in question. Things worked well but NFS went mad (IIRC, NFS4 will do better here but I am not sure). Since I needed the groups in question to control file access, I reverted the change and switched to ACLs which is not so intrusive :-). -Andre > > Thanks in advance (doubly so if this is a lame question) > Reuben > > -- > Reuben A. Popp > Systems Administrator > Information Technology Department > East Central College > 1+ 636 583 5195 x2480 > _______________________________________________ > 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" -- ech`echo xiun | tr nu oc | sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 18:59:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F9CB16A421 for ; Tue, 5 Jun 2007 18:59:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outG.internet-mail-service.net (outG.internet-mail-service.net [216.240.47.230]) by mx1.freebsd.org (Postfix) with ESMTP id 1E5ED13C458 for ; Tue, 5 Jun 2007 18:59:19 +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.32) with ESMTP; Tue, 05 Jun 2007 11:59:19 -0700 Received: from julian-mac.elischer.org (nat.ironport.com [63.251.108.100]) by idiom.com (Postfix) with ESMTP id 5C72F125A28; Tue, 5 Jun 2007 11:59:19 -0700 (PDT) Message-ID: <4665B28A.7060608@elischer.org> Date: Tue, 05 Jun 2007 11:59:22 -0700 From: Julian Elischer User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) MIME-Version: 1.0 To: rapopp@eastcentral.edu References: <200706051149.45787.rapopp@eastcentral.edu> In-Reply-To: <200706051149.45787.rapopp@eastcentral.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups question 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, 05 Jun 2007 18:59:20 -0000 Reuben A. Popp wrote: > Hello all, > > Can someone explain to me the rationale behind having ngroups_max set to 16 by > default? > NFS only supports this much by default (from memory). Samba (in the guise of Jeremy Allison) has asked us to follow Linux's lead and support an arbitrary number of Groups but it hasn't happened yet, Partly due to the question of "what to do about NFS" and partly just due to ENOTIME. > I came across this issue originally when working on our Samba implementation > (samba-3 out of ports, running on 6-STABLE). We have some users that belong > to a number of groups, some of whom need to belong to more groups than the > defined hard limit. On doing a little research, I did come across the PR > detailed in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108552, and > continued reading the linked thread from March 2003, however this really > doesn't explain why the limit is set to 16. > > Can one adjust the value in syslimits.h on a system and then rebuild > world/ports with the expectation this will work, or is the issue more > involved then that? Is (or has) there any discussion on raising that number > to a larger value? > > Thanks in advance (doubly so if this is a lame question) > Reuben > From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 19:51:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E973116A468 for ; Tue, 5 Jun 2007 19:51:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5FC4913C44C for ; Tue, 5 Jun 2007 19:51:57 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l55JphV1030407; Tue, 5 Jun 2007 15:51:43 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 5 Jun 2007 15:39:22 -0400 User-Agent: KMail/1.9.6 References: <4649349D.4060101@room52.net> <86odkcugev.fsf@dwp.des.no> <46565781.2030407@room52.net> In-Reply-To: <46565781.2030407@room52.net> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200706051539.22662.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 05 Jun 2007 15:51:44 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Lawrence Stewart , Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?= Subject: Re: Writing a plain text file to disk from kernel space 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, 05 Jun 2007 19:51:58 -0000 On Thursday 24 May 2007 11:26:58 pm Lawrence Stewart wrote: > Comments inline... >=20 > Dag-Erling Sm=C3=B8rgrav wrote: > > Lawrence Stewart writes: > > =20 > >> Dag-Erling Sm=C3=B8rgrav writes: > >> =20 > >>> Since you are writing kernel code, I assume you have KDB/DDB in your > >>> kernel and know how to use it. > >>> =20 > >> I don't know how to use them really. Thus far I haven't had a need for > >> really low level debugging tools... seems that may have changed > >> though! Any good tutorials/pointers on how to get started with kernel > >> debugging? > >> =20 > > > > The handbook and FAQ have information on debugging panics. Greg Lehey > > (grog@) does a tutorial on kernel debugging, you can probably find > > slides online (or just ask him) > > =20 >=20 >=20 > For reference, I found what looks to be a very comprehensive kernel=20 > debugging reference here:=20 > http://www.lemis.com/grog/Papers/Debug-tutorial/tutorial.pdf >=20 > Greg certainly knows the ins and outs of kernel debugging! >=20 > > =20 > >>> kio_write probably blocks waiting for the write to complete. You can= 't > >>> do that while holding a non-sleepable lock. > >>> =20 > >> So this is where my knowledge/understanding gets very hazy... > >> > >> When a thread blocks waiting for some operation to complete or event > >> to happen, the thread effectively goes to sleep, correct? > >> =20 > > > > It depends on the type of lock used, but mostly, yes. > > > > =20 > >> Looking at the kio_write code in subr_kernio.c, I'm guessing the lock > >> that is causing the trouble is related to the "vn_lock" function call? > >> =20 > > > > What matters is that kio_write() may sleep and therefore can't be called > > while holding a non-sleepable lock. > > > > =20 > >> I don't understand though why the vnode lock would be set up in such a > >> way that when the write blocks whilst waiting for the underlying > >> filesystem to signal everything is ok, it causes the kernel to panic! > >> =20 > > > > You cannot sleep while holding a non-sleepable lock. You need to find > > out which locks are held at the point where you call kio_write(), and > > figure out a way to delay the kio_write() call until those locks are > > released. > > > > =20 > >> How do I make the lock "sleepable" or make sure the thread doesn't try > >> go to sleep whilst holding the lock? > >> =20 > > > > You can't make an unsleepable lock sleepable. You might be able to > > replace it with a sleepable lock, but you would have to go through every > > part of the kernel that uses the lock and make sure that it works > > correctly with a sleepable lock. Most likely, it won't. > > > > =20 >=20 >=20 > Thanks for the explanations. I'm starting to get a better picture of=20 > what's actually going on. >=20 > So it seems that there is no way I can call kio_write from within the=20 > function that is acting as a pfil output hook, because it blocks at some= =20 > point whilst doing the disk write, which makes the kernel unhappy=20 > because pfil code is holding a non-sleepable mutex somewhere. >=20 > If you read my other message from yesterday, I still can't figure out=20 > why this only happens with outbound TCP traffic, but anyways... >=20 > I'll have a bit more of a think about it and get back to the list shortly= =2E.. Use a task to defer the kio_write() to a taskqueue. You have to malloc sta= te=20 (using M_NOWAIT, which can fail) to do this properly. If you are doing thi= s=20 for every packet, you are probably better off using malloc() to throw items= =20 into a queue and having a global task that drains the queue on each executi= on=20 doing kio_write()'s for each object. Regarding sleepable vs. non-sleepable locks. Getting preempted by an=20 interrupt is not considered "sleeping". Sleeping means voluntarily yieldin= g=20 the CPU to wait for an event such as via msleep() or a condition variable. = =20 Note that interrupt handlers can acquire non-sleepable locks. If you sleep= =20 while holding a non-sleepable lock, you may have an interrupt handler that= =20 can't run while it waits for some async event (like disk I/O) to complete. =2D-=20 John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 19:51:58 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0E7316A469; Tue, 5 Jun 2007 19:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5774113C465; Tue, 5 Jun 2007 19:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l55JphV2030407; Tue, 5 Jun 2007 15:51:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 5 Jun 2007 15:50:53 -0400 User-Agent: KMail/1.9.6 References: <465FF29B.3010307@latnet.lv> <46604877.7030007@errno.com> <4663DDD4.1020207@latnet.lv> In-Reply-To: <4663DDD4.1020207@latnet.lv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051550.54460.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 05 Jun 2007 15:51:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: hackers@freebsd.org, Artis Caune Subject: Re: stopping callouts 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, 05 Jun 2007 19:51:58 -0000 On Monday 04 June 2007 05:39:32 am Artis Caune wrote: > Sam Leffler wrote: > > > > If you use callout_init_mtx then use callout_stop while holding my_mtx; > > if the callout is blocked waiting for my_mtx the request will be discarded. > > > > callout_drain should not be called while holding my_mtx because it can > > sleep. > > > > > Thanks, > than I will use: > > > MTX_LOCK; > ... > callout_stop(); > MTX_UNLOCK; During module unload (or device detach) you should still do a callout_drain() before destroying the mutex, to make sure softclock() doesn't race with the mtx_destroy(). Thus: foo_detach() { FOO_LOCK(sc); foo_stop(sc); callout_stop(&sc->callout); FOO_UNLOCK(sc); bus_teardown_intr(...) bus_release_resources(...); callout_drain(&sc->callout); mtx_destroy(&sc->lock); } -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Tue Jun 5 19:51:58 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C0E7316A469; Tue, 5 Jun 2007 19:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.freebsd.org (Postfix) with ESMTP id 5774113C465; Tue, 5 Jun 2007 19:51:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from localhost.corp.yahoo.com (john@localhost [127.0.0.1]) (authenticated bits=0) by server.baldwin.cx (8.13.8/8.13.8) with ESMTP id l55JphV2030407; Tue, 5 Jun 2007 15:51:54 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Tue, 5 Jun 2007 15:50:53 -0400 User-Agent: KMail/1.9.6 References: <465FF29B.3010307@latnet.lv> <46604877.7030007@errno.com> <4663DDD4.1020207@latnet.lv> In-Reply-To: <4663DDD4.1020207@latnet.lv> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706051550.54460.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [127.0.0.1]); Tue, 05 Jun 2007 15:51:54 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/3362/Tue Jun 5 13:02:53 2007 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: hackers@freebsd.org, Artis Caune Subject: Re: stopping callouts 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, 05 Jun 2007 19:51:58 -0000 On Monday 04 June 2007 05:39:32 am Artis Caune wrote: > Sam Leffler wrote: > > > > If you use callout_init_mtx then use callout_stop while holding my_mtx; > > if the callout is blocked waiting for my_mtx the request will be discarded. > > > > callout_drain should not be called while holding my_mtx because it can > > sleep. > > > > > Thanks, > than I will use: > > > MTX_LOCK; > ... > callout_stop(); > MTX_UNLOCK; During module unload (or device detach) you should still do a callout_drain() before destroying the mutex, to make sure softclock() doesn't race with the mtx_destroy(). Thus: foo_detach() { FOO_LOCK(sc); foo_stop(sc); callout_stop(&sc->callout); FOO_UNLOCK(sc); bus_teardown_intr(...) bus_release_resources(...); callout_drain(&sc->callout); mtx_destroy(&sc->lock); } -- John Baldwin From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 02:25:53 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0361A16A421 for ; Wed, 6 Jun 2007 02:25:53 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.224]) by mx1.freebsd.org (Postfix) with ESMTP id 936DA13C468 for ; Wed, 6 Jun 2007 02:25:52 +0000 (UTC) (envelope-from lstewart@room52.net) Received: from [136.186.229.95] (lstewart.caia.swin.edu.au [136.186.229.95]) by swin.edu.au (8.13.6.20060614/8.13.1) with ESMTP id l562Pjrr026565; Wed, 6 Jun 2007 12:25:46 +1000 Message-ID: <46661B30.10404@room52.net> Date: Wed, 06 Jun 2007 12:25:52 +1000 From: Lawrence Stewart User-Agent: Thunderbird 1.5.0.9 (X11/20070123) MIME-Version: 1.0 To: John Baldwin References: <4649349D.4060101@room52.net> <86odkcugev.fsf@dwp.des.no> <46565781.2030407@room52.net> <200706051539.22662.jhb@freebsd.org> In-Reply-To: <200706051539.22662.jhb@freebsd.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on gpo4.cc.swin.edu.au Cc: freebsd-hackers@freebsd.org, =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= Subject: Re: Writing a plain text file to disk from kernel space 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, 06 Jun 2007 02:25:53 -0000 Hi John, Thanks for the reply and additional information on locks. The solution I've just completed working on is designed exactly as you describe. We're about to begin testing and evaluating the module, and we'll be releasing the code and 2 technical reports related to it within the coming weeks with any luck. The first report describes the module and its performance characteristics... only interesting to people doing TCP related research with FreeBSD. The other report is a sort of "intro to FreeBSD kernel hacking" paper, which is a brain dump of all the useful lessons we've learnt throughout the process. This report is mostly for our benefit so we remember the lessons we learnt for next time, but we're hoping it will also be something useful for the community to point noob kernel hackers at for some introductory information. I'll be posting to this list as soon as the code and reports are available, as it has been indicated by people following this thread that having some sort of tutorial/reference information would be useful. Cheers, Lawrence John Baldwin wrote: > Use a task to defer the kio_write() to a taskqueue. You have to malloc state > (using M_NOWAIT, which can fail) to do this properly. If you are doing this > for every packet, you are probably better off using malloc() to throw items > into a queue and having a global task that drains the queue on each execution > doing kio_write()'s for each object. > > Regarding sleepable vs. non-sleepable locks. Getting preempted by an > interrupt is not considered "sleeping". Sleeping means voluntarily yielding > the CPU to wait for an event such as via msleep() or a condition variable. > Note that interrupt handlers can acquire non-sleepable locks. If you sleep > while holding a non-sleepable lock, you may have an interrupt handler that > can't run while it waits for some async event (like disk I/O) to complete. > > From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 10:26:08 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8FD5016A46B for ; Wed, 6 Jun 2007 10:26:08 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id 5057613C45E for ; Wed, 6 Jun 2007 10:26:08 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 0 with SMTP; 6 Jun 2007 10:26:07 -0000 Date: Wed, 6 Jun 2007 13:26:14 +0300 From: Nikolay Pavlov To: Harald Servat Message-ID: <20070606102614.GA45197@zone3000.net> Mail-Followup-To: Nikolay Pavlov , Harald Servat , freebsd-hackers@FreeBSD.org, freebsd-hpc@FreeBSD.org, freebsd-performance@FreeBSD.org References: <20070604192947.GA74531@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: freebsd-hackers@FreeBSD.org, freebsd-performance@FreeBSD.org, freebsd-hpc@FreeBSD.org Subject: Re: testers wanted for PAPI / 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: Wed, 06 Jun 2007 10:26:08 -0000 On Monday, 4 June 2007 at 21:33:54 +0200, Harald Servat wrote: > Hello, > > What is the result of dmesg | grep hwpmc? hwpmc: TSC/1/0x20 P6/2/0x1ff > > Regards, > > 2007/6/4, Nikolay Pavlov <[1]quetzal@zone3000.net>: > > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > > Hello, > > > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try > to > > the package I'm porting. It would be great to have more feedback than > just > > that my laptop is able to provide me :) > > > > First of all, you can download the code at > > > > [2]http://code.google.com/p/papi-for-freebsd > > > > Next, see man hwpmc(4) and compile a kernel with > > options HWPMC_HOOKS > > device hwpmc > > > > (you'll require device apic if you're running on i386 machines). > > > > When you boot your dmesg should print something like > > hwpmc: TSC/1/0x20 P6/2/0x1fe > > > > Once the machine is up and running, just untar the file you've > downloaded, > > run ./configure and just run make (not make install). > > > > Could you send me the output of the following commands? > > > > # dmesg | grep hwpmc > > # utils/papi_avail > > # utils/papi_decode > > # utils/papi_native_avail > > # ctests/low-level > > # ctests/high-level > > > > Thank you very much, > > Hi Harald. I have an error while running configure script: > > root@orion:~/papi/papi-3.5.0/src# > ./configure <796> > as_func_failure succeeded. > as_func_failure succeeded. > No shell found that supports shell functions. > Please tell [3]autoconf@gnu.org about your system, > including any error possibly output before this > message > checking for architecture... i386 > checking for OS... freebsd > checking for OS version... 7.0-CURRENT > checking for CPU type... > checking for 32 or 64 bit mode... 32 > checking for debugging build... no > checking for gawk... no > checking for mawk... no > checking for nawk... nawk > checking for gcc... gcc > checking for C compiler default output file name... a.out > checking whether the C compiler works... yes > checking whether we are cross compiling... no > checking for suffix of executables... > checking for suffix of object files... o > checking whether we are using the GNU C compiler... yes > checking whether gcc accepts -g... yes > checking for gcc option to accept ISO C89... none needed > checking for g77... no > checking for xlf... no > checking for f77... f77 > checking whether we are using the GNU Fortran 77 compiler... yes > checking whether f77 accepts -g... yes > checking whether we are using the GNU C compiler... (cached) yes > checking whether gcc accepts -g... (cached) yes > checking for gcc option to accept ISO C89... (cached) none needed > checking whether we are using the GNU Fortran 77 compiler... (cached) > yes > checking whether f77 accepts -g... (cached) yes > checking how to run the C preprocessor... gcc -E > checking whether ln -s works... yes > checking whether make sets $(MAKE)... yes > checking for ranlib... ranlib > checking for grep that handles long lines and -e... /usr/bin/grep > checking for egrep... /usr/bin/grep -E > checking for ANSI C header files... yes > checking for ffsll... no > checking for working MMTIMER... no > checking for working CLOCK_REALTIME_HR POSIX 1b timer... no > checking for working CLOCK_REALTIME POSIX 1b timer... no > checking for real time clock or cycle counter... cycle > checking for working __thread... yes > checking for high performance thread local storage... __thread > checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no > checking for working per-thread times() timer... no > checking for thread virtual clock or cycle counter... default > checking for /sys/class/perfctr... no > checking for /dev/perfctr... no > checking for /sys/kernel/perfmon/version... no > checking for /proc/perfmon... no > checking for perfctr version... none > checking for perfmon version... none > checking for Makefile to use... configure: error: Error! HWPMC module > seems not to be on the kernel. Have you compiled the kernel with HWPMC? > (see hwpmc(4)) > > However module is there: > > quetzal@viking:~/bugs> cat > papi.bug > <1959> > root@orion:~/papi# kldstat -v | grep > hwpmc > <848> > 135 hwpmc > > root@orion:~/bugs# uname > -a <853> > FreeBSD [4]orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Mon > Jun > 4 19:33:59 EEST 2007 > root@orion.zone3000.net:/usr/obj/usr/src/sys/GENERIC-PMC i386 > > And i have all required options in kernel config: > > quetzal@orion:~/bugs> grep -i PMC > /sys/i386/conf/GENERIC-PMC > <890> > device hwpmc # Driver (also a loadable module) > options HWPMC_HOOKS # Other necessary kernel hooks > > -- > ====================================================================== > - Best regards, Nikolay Pavlov. <<<----------------------------------- > ====================================================================== > > -- > _________________________________________________________________ > Empty your memory, > with a free()... > like a pointer! > > If you cast a pointer to an integer, > it becomes an integer, > if you cast a pointer to a struct, > it becomes a struct. > > The pointer can crash..., > and can overflow. > > Be a pointer my friend... > > References > > Visible links > 1. mailto:quetzal@zone3000.net > 2. http://code.google.com/p/papi-for-freebsd > 3. mailto:autoconf@gnu.org > 4. http://orion.zone3000.net/ -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 10:54:19 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3FAC116A46C for ; Wed, 6 Jun 2007 10:54:19 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id BB1CE13C4BF for ; Wed, 6 Jun 2007 10:54:18 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so24062anc for ; Wed, 06 Jun 2007 03:54:18 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:references; b=qtiveO7MmJkN4k34p8kQnAqy+dB5NmKVKKe6HT4s6lF0v7+uurR1oKfjImxqU2M5gh3G3hbMDS/k9Jbw/VdgJE8C8zz/MWjyjRfftgYzniHKpin+dAt74dWb3YDbMiexvlVl2I+llVlgFBtFkvQiX4lAwg9/anpUsCTrifRQIag= 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:references; b=Eq1pwJZXAb3eXZ4au1O5lxoBMUwF28ClWQiNgsQupwl/pi49qUmxH8QuFxF9yufdMgyILFEp203foTf1RvChAp9vt6uku452OyABEE2fuFXbtgVfJLZjzyxnmDPLjeSzwo2DjkhaFE5xjlBk1XnKrzKnIOSm81HWcFXs3HcJsq0= Received: by 10.100.94.3 with SMTP id r3mr184591anb.1181127256984; Wed, 06 Jun 2007 03:54:16 -0700 (PDT) Received: by 10.100.32.4 with HTTP; Wed, 6 Jun 2007 03:54:16 -0700 (PDT) Message-ID: Date: Wed, 6 Jun 2007 12:54:16 +0200 From: "Harald Servat" To: "Nikolay Pavlov" , "Harald Servat" , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org In-Reply-To: <20070606102614.GA45197@zone3000.net> MIME-Version: 1.0 References: <20070604192947.GA74531@zone3000.net> <20070606102614.GA45197@zone3000.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: testers wanted for PAPI / 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: Wed, 06 Jun 2007 10:54:19 -0000 2007/6/6, Nikolay Pavlov : > > On Monday, 4 June 2007 at 21:33:54 +0200, Harald Servat wrote: > > Hello, > > > > What is the result of dmesg | grep hwpmc? > > hwpmc: TSC/1/0x20 P6/2/0x1ff > > > > > > Regards, > > > > 2007/6/4, Nikolay Pavlov <[1]quetzal@zone3000.net>: > > > > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > > > Hello, > > > > > > I'm porting PAPI to FreeBSD. I was wondering if you could give > a try > > to > > > the package I'm porting. It would be great to have more feedback > than > > just > > > that my laptop is able to provide me :) > > > > > > First of all, you can download the code at > > > > > > [2]http://code.google.com/p/papi-for-freebsd > > > > > > Next, see man hwpmc(4) and compile a kernel with > > > options HWPMC_HOOKS > > > device hwpmc > > > > > > (you'll require device apic if you're running on i386 machines). > > > > > > When you boot your dmesg should print something like > > > hwpmc: TSC/1/0x20 > P6/2/0x1fe > > > > > > Once the machine is up and running, just untar the file you've > > downloaded, > > > run ./configure and just run make (not make install). > > > > > > Could you send me the output of the following commands? > > > > > > # dmesg | grep hwpmc > > > # utils/papi_avail > > > # utils/papi_decode > > > # utils/papi_native_avail > > > # ctests/low-level > > > # ctests/high-level > > > > > > Thank you very much, > > > > Hi Harald. I have an error while running configure script: > > > > root@orion:~/papi/papi-3.5.0/src# > > > ./configure <796> > > as_func_failure succeeded. > > as_func_failure succeeded. > > No shell found that supports shell functions. > > Please tell [3]autoconf@gnu.org about your system, > > including any error possibly output before this > > message > > checking for architecture... i386 > > checking for OS... freebsd > > checking for OS version... 7.0-CURRENT > > checking for CPU type... > > checking for 32 or 64 bit mode... 32 > > checking for debugging build... no > > checking for gawk... no > > checking for mawk... no > > checking for nawk... nawk > > checking for gcc... gcc > > checking for C compiler default output file name... a.out > > checking whether the C compiler works... yes > > checking whether we are cross compiling... no > > checking for suffix of executables... > > checking for suffix of object files... o > > checking whether we are using the GNU C compiler... yes > > checking whether gcc accepts -g... yes > > checking for gcc option to accept ISO C89... none needed > > checking for g77... no > > checking for xlf... no > > checking for f77... f77 > > checking whether we are using the GNU Fortran 77 compiler... yes > > checking whether f77 accepts -g... yes > > checking whether we are using the GNU C compiler... (cached) yes > > checking whether gcc accepts -g... (cached) yes > > checking for gcc option to accept ISO C89... (cached) none needed > > checking whether we are using the GNU Fortran 77 compiler... > (cached) > > yes > > checking whether f77 accepts -g... (cached) yes > > checking how to run the C preprocessor... gcc -E > > checking whether ln -s works... yes > > checking whether make sets $(MAKE)... yes > > checking for ranlib... ranlib > > checking for grep that handles long lines and -e... /usr/bin/grep > > checking for egrep... /usr/bin/grep -E > > checking for ANSI C header files... yes > > checking for ffsll... no > > checking for working MMTIMER... no > > checking for working CLOCK_REALTIME_HR POSIX 1b timer... no > > checking for working CLOCK_REALTIME POSIX 1b timer... no > > checking for real time clock or cycle counter... cycle > > checking for working __thread... yes > > checking for high performance thread local storage... __thread > > checking for working CLOCK_THREAD_CPUTIME_ID POSIX 1b timer... no > > checking for working per-thread times() timer... no > > checking for thread virtual clock or cycle counter... default > > checking for /sys/class/perfctr... no > > checking for /dev/perfctr... no > > checking for /sys/kernel/perfmon/version... no > > checking for /proc/perfmon... no > > checking for perfctr version... none > > checking for perfmon version... none > > checking for Makefile to use... configure: error: Error! HWPMC > module > > seems not to be on the kernel. Have you compiled the kernel with > HWPMC? > > (see hwpmc(4)) > > > > However module is there: > > > > quetzal@viking:~/bugs> cat > > papi.bug > > <1959> > > root@orion:~/papi# kldstat -v | grep > > hwpmc > > <848> > > 135 hwpmc > > > > root@orion:~/bugs# uname > > > -a <853> > > FreeBSD [4]orion.zone3000.net 7.0-CURRENT FreeBSD 7.0-CURRENT #0: > Mon > > Jun > > 4 19:33:59 EEST 2007 > > root@orion.zone3000.net:/usr/obj/usr/src/sys/GENERIC-PMC i386 > > > > And i have all required options in kernel config: > > > > quetzal@orion:~/bugs> grep -i PMC > > /sys/i386/conf/GENERIC-PMC > > <890> > > device hwpmc # Driver (also a loadable module) > > options HWPMC_HOOKS # Other necessary kernel hooks > > > > -- > > > ====================================================================== > > - Best regards, Nikolay Pavlov. > <<<----------------------------------- > > > ====================================================================== > > > > -- > > _________________________________________________________________ > > Empty your memory, > > with a free()... > > like a pointer! > > > > If you cast a pointer to an integer, > > it becomes an integer, > > if you cast a pointer to a struct, > > it becomes a struct. > > > > The pointer can crash..., > > and can overflow. > > > > Be a pointer my friend... > > > > References > > > > Visible links > > 1. mailto:quetzal@zone3000.net > > 2. http://code.google.com/p/papi-for-freebsd > > 3. mailto:autoconf@gnu.org > > 4. http://orion.zone3000.net/ > > -- > ====================================================================== > - Best regards, Nikolay Pavlov. <<<----------------------------------- > ====================================================================== > > Hello Nikolay, could you try to remove lines 1018 - 1022 from configure.in, run autoconf and rerun the configure? Regards, -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 15:59:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3CD1316A400 for ; Wed, 6 Jun 2007 15:59:51 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.freebsd.org (Postfix) with SMTP id DDBD213C465 for ; Wed, 6 Jun 2007 15:59:50 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.69.37) by 0 with SMTP; 6 Jun 2007 15:59:49 -0000 Date: Wed, 6 Jun 2007 18:59:55 +0300 From: Nikolay Pavlov To: Harald Servat , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org Message-ID: <20070606155955.GA48022@zone3000.net> Mail-Followup-To: Nikolay Pavlov , Harald Servat , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org References: <20070604192947.GA74531@zone3000.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070604192947.GA74531@zone3000.net> X-Operating-System: FreeBSD 6.2-RELEASE-p4 User-Agent: mutt-ng/devel-r804 (FreeBSD) Cc: Subject: Re: testers wanted for PAPI / 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: Wed, 06 Jun 2007 15:59:51 -0000 On Monday, 4 June 2007 at 22:29:47 +0300, Nikolay Pavlov wrote: > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > > Hello, > > > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try to > > the package I'm porting. It would be great to have more feedback than just > > that my laptop is able to provide me :) > > > > First of all, you can download the code at > > > > http://code.google.com/p/papi-for-freebsd > > > > Next, see man hwpmc(4) and compile a kernel with > > options HWPMC_HOOKS > > device hwpmc > > > > (you'll require device apic if you're running on i386 machines). > > > > When you boot your dmesg should print something like > > hwpmc: TSC/1/0x20 P6/2/0x1fe > > > > Once the machine is up and running, just untar the file you've downloaded, > > run ./configure and just run make (not make install). > > > > Could you send me the output of the following commands? > > > > # dmesg | grep hwpmc > > # utils/papi_avail > > # utils/papi_decode > > # utils/papi_native_avail > > # ctests/low-level > > # ctests/high-level > > > > Thank you very much, > > Hi Harald. I have an error while running configure script: > Ooops. Sorry for confusion Harald it was my fault. I have send the script gziped archive to you with all the tests in a privat email. -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ====================================================================== From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 19:26:59 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 470E316A46B for ; Wed, 6 Jun 2007 19:26:59 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.243]) by mx1.freebsd.org (Postfix) with ESMTP id F235A13C4BA for ; Wed, 6 Jun 2007 19:26:58 +0000 (UTC) (envelope-from redcrash@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so69476anc for ; Wed, 06 Jun 2007 12:26:58 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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:references; b=eKm4Mu/PlfinhUTSYyeV6/bAEpz1rwWaF6RRKIh+jNV++OIGYdgvgCjL6w3eLsfuu/ohBA+rp8lryfCVfQY1QMiT6ZLkc7WhqUklW4XeSk4j1y2EgA5QNj1nkPZzSMtQFyQvnPCexM41HY8VlccDco67KBDQf1Go2f2IcXLe4w0= 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:references; b=kRp+RCDF6jvK+hzs1xvMZO7B/9KhyLbcMOZfc2sZVSru5f+zIlJDoNsuopLuzNpqPGvmbpnBMYsgklDz3nETI4S8vo9swjtK/nxPrRsc+bhuyKeDgboyDTG9OrljznvDgcwKZrDsD4dIMpNBKtpt9ww/299C2B6roPZTFoXAUiw= Received: by 10.100.133.9 with SMTP id g9mr532183and.1181158018001; Wed, 06 Jun 2007 12:26:58 -0700 (PDT) Received: by 10.100.32.4 with HTTP; Wed, 6 Jun 2007 12:26:57 -0700 (PDT) Message-ID: Date: Wed, 6 Jun 2007 21:26:57 +0200 From: "Harald Servat" To: "Nikolay Pavlov" , "Harald Servat" , freebsd-hackers@freebsd.org, freebsd-hpc@freebsd.org, freebsd-performance@freebsd.org In-Reply-To: <20070606155955.GA48022@zone3000.net> MIME-Version: 1.0 References: <20070604192947.GA74531@zone3000.net> <20070606155955.GA48022@zone3000.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: testers wanted for PAPI / 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: Wed, 06 Jun 2007 19:26:59 -0000 2007/6/6, Nikolay Pavlov : > > On Monday, 4 June 2007 at 22:29:47 +0300, Nikolay Pavlov wrote: > > On Sunday, 20 May 2007 at 12:29:23 +0200, Harald Servat wrote: > > > Hello, > > > > > > I'm porting PAPI to FreeBSD. I was wondering if you could give a try > to > > > the package I'm porting. It would be great to have more feedback than > just > > > that my laptop is able to provide me :) > > > > > > First of all, you can download the code at > > > > > > http://code.google.com/p/papi-for-freebsd > > > > > > Next, see man hwpmc(4) and compile a kernel with > > > options HWPMC_HOOKS > > > device hwpmc > > > > > > (you'll require device apic if you're running on i386 machines). > > > > > > When you boot your dmesg should print something like > > > hwpmc: TSC/1/0x20 P6/2/0x1fe > > > > > > Once the machine is up and running, just untar the file you've > downloaded, > > > run ./configure and just run make (not make install). > > > > > > Could you send me the output of the following commands? > > > > > > # dmesg | grep hwpmc > > > # utils/papi_avail > > > # utils/papi_decode > > > # utils/papi_native_avail > > > # ctests/low-level > > > # ctests/high-level > > > > > > Thank you very much, > > > > Hi Harald. I have an error while running configure script: > > > > Ooops. Sorry for confusion Harald it was my fault. I have send the > script gziped archive to you with all the tests in a privat email. > > -- > ====================================================================== > - Best regards, Nikolay Pavlov. <<<----------------------------------- > ====================================================================== > > Thank you very much! Results seem fine! -- _________________________________________________________________ Empty your memory, with a free()... like a pointer! If you cast a pointer to an integer, it becomes an integer, if you cast a pointer to a struct, it becomes a struct. The pointer can crash..., and can overflow. Be a pointer my friend... From owner-freebsd-hackers@FreeBSD.ORG Wed Jun 6 21:41:59 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0EE8D16A469 for ; Wed, 6 Jun 2007 21:41:59 +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 A070C13C45E for ; Wed, 6 Jun 2007 21:41:56 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from [192.168.2.102] ([172.21.151.3]) by smtp-1.dlr.de with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Jun 2007 23:28:39 +0200 Message-ID: <46672710.9030508@dlr.de> Date: Wed, 06 Jun 2007 23:28:48 +0200 From: Hartmut Brandt Organization: German Aerospace Center User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) MIME-Version: 1.0 To: rapopp@eastcentral.edu References: <200706051149.45787.rapopp@eastcentral.edu> In-Reply-To: <200706051149.45787.rapopp@eastcentral.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Jun 2007 21:28:39.0592 (UTC) FILETIME=[A6327280:01C7A881] Cc: freebsd-hackers@freebsd.org Subject: Re: kern.ngroups question 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, 06 Jun 2007 21:41:59 -0000 Reuben A. Popp wrote: > Hello all, > > Can someone explain to me the rationale behind having ngroups_max set to 16 by > default? > > I came across this issue originally when working on our Samba implementation > (samba-3 out of ports, running on 6-STABLE). We have some users that belong > to a number of groups, some of whom need to belong to more groups than the > defined hard limit. On doing a little research, I did come across the PR > detailed in http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108552, and > continued reading the linked thread from March 2003, however this really > doesn't explain why the limit is set to 16. > > Can one adjust the value in syslimits.h on a system and then rebuild > world/ports with the expectation this will work, or is the issue more > involved then that? Is (or has) there any discussion on raising that number > to a larger value? > My desktop runs with ngroups 64 for over two years. The accounts come from an AD with a lot of groups for everything. If I remember correctly I fixed a number of issues in libc with regarding to truncating the group list when packing it into RPCs. It now just ignores the extra groups instead of dumping core :-) So if you don't need the group memberships for NFS access thing should work. harti From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 7 08:08:20 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4A3516A41F for ; Thu, 7 Jun 2007 08:08:19 +0000 (UTC) (envelope-from naylor.b.david@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 902D713C4B8 for ; Thu, 7 Jun 2007 08:08:19 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: by wx-out-0506.google.com with SMTP id h28so336904wxd for ; Thu, 07 Jun 2007 01:08:19 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id:sender; b=CWt8AvrdFf0miW6ONX2WzR2jndkEcdK8MkeNL3/N+SPXP0scUV0Nfp2+QuzbSuIDMhD4A58ecF/ukirxpJTGQWUlXE2XNmaZhSQDmpuEPdy67e213BkTBaQbCzryByQn/rvvb8Ol75BMrNyiZ57JC/ejy6mp17MeF2gMaYCrodo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:from:to:subject:date:user-agent:mime-version:content-type:content-transfer-encoding:message-id:sender; b=bWwzxDzgOzNi6TN1v8ZdXHzhwS9bfTVMQMqgDuAab+TSGCAkT2ucgsaOwYNfDZI9GC9nheWiSJsysKimxJxRKwMZ3GCctXfcRLYbdnIHcMyU8b/NCCDJRCbq0cE19Jckja8yGRdNnTaC8YExXcGf8AR6fEzfaasmAoUNR3kwvmY= Received: by 10.70.123.14 with SMTP id v14mr2127421wxc.1181203698988; Thu, 07 Jun 2007 01:08:18 -0700 (PDT) Received: from ?0.0.0.0? ( [196.37.90.163]) by mx.google.com with ESMTP id 27sm326190wra.2007.06.07.01.08.14 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 07 Jun 2007 01:08:18 -0700 (PDT) From: David Naylor To: freebsd-hackers@freebsd.org Date: Thu, 7 Jun 2007 10:06:01 +0200 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3011027.MtEEHuugcO"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200706071006.12201.blackdragon@highveldmail.co.za> Sender: David Naylor X-Mailman-Approved-At: Thu, 07 Jun 2007 11:41:48 +0000 Subject: fetch: Resume errors, help! 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, 07 Jun 2007 08:08:20 -0000 --nextPart3011027.MtEEHuugcO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, I have been having a very annoying problem with fetch and the ports distfil= es=20 fetching. Living in South Africa internet access is not what it could be, = as=20 such I have to use a proxy to access the internet. On to the problem: When fetch tries to resume from an ftp site that does not support resuming = (or=20 fetch lacks the ability in these specific cases, or the proxy + fetch=20 faulted) it appends to the file but restarts the transfer from 0. This=20 results in a file that is too big but does contain a complete copy of the=20 file. A solution is simple: es =3D Expected size of the file as =3D Actual size of the file f =3D File name # dd if=3Df of=3Df~ bs=3D$((as - es)) skip=3D1 # mv f~ f This is very inconvenient and a problem when trying to download files in=20 batch. One gets interrupted and stops everything else. As such I looked=20 into fetch.c and tried to fix the problem. See below for my patch. A=20 problem is that how to handle the -R flag (no overwrite file flag). I have= =20 three solutions: 1) Ignore flag and overwrite the file anyway 2) Do not overwrite and abort 3) Specify above behaviour with an additional flag Given that the ports and having many mirrors it is possible to find a site= =20 that does support resuming, and thus will save in bandwidth (important for= =20 me). However it is possible that there are no alternatives or all sites do= =20 not support resume. =20 In the patch the commented out section is solution 2, the implemented versi= on=20 is solution 1. =20 Any advice will be welcome, once a satisfactory solution has been achieved = I=20 will submit a PR with the patch? =20 Thank you David P.S. I've been using FreeBSD for a year or two however I am very new at=20 writing patches for it, this will be my first so all help and mentoring wil= l=20 be very welcome. =20 Patch file: =2D-- usr.bin/fetch/fetch.c.orig 2007-06-07 09:17:18.000000000 +0200 +++ usr.bin/fetch/fetch.c 2007-06-07 09:18:39.000000000 +0200 @@ -510,8 +510,36 @@ (intmax_t)sb.st_size, (intmax_t)us.size); goto failure; } +// /* check fetched offset is as expected */ +// if (url->offset !=3D sb.st_size) { +// if (R_flag) { +// /* unable to resume */ +// warnx("%s: unexpected offset, " +// "expected %jd bytes, got %jd " +// "bytes", (intmax_t)sb.st_size,=20 +// (intmax_t)url->offset); +// goto failure_keep; +// } else if (url->offset !=3D 0) +// /* if not we need to restart from scratch */ +// goto restart; +// } +// if ((of =3D fopen(path, "a")) =3D=3D NULL) { +// warn("%s: fopen()", path); +// goto failure; +// } +// /* check feteched offset is either as expected or 0 */ + if (url->offset !=3D sb.st_size || url->offset !=3D 0) + /* if not we need to restart from scratch */ + goto restart; + /* + * NOTE: R_flag is ignored and local file is over=20 + * written *not* deleted as it is the only way + * to resume transfer of this file from this=20 + * URL. + */ /* we got it, open local file */ =2D if ((of =3D fopen(path, "a")) =3D=3D NULL) { + if ((of =3D url->offset =3D=3D 0 ? fopen(path, "w") :=20 + fopen(path, "a")) =3D=3D NULL) { warn("%s: fopen()", path); goto failure; } @@ -536,6 +564,7 @@ goto success; } =20 +restart: if (of =3D=3D NULL) { /* * We don't yet have an output file; either this is a --nextPart3011027.MtEEHuugcO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBGZ7x0yqzxLKpyZI8RAl/EAJ0Rqk0h1a4yBPnbG9mOwLx6nA+qwgCgs2DH GSWFmYQd8+84NdIdlYJMvJA= =lCsd -----END PGP SIGNATURE----- --nextPart3011027.MtEEHuugcO-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 7 17:38:42 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6ECBD16A400 for ; Thu, 7 Jun 2007 17:38:42 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.freebsd.org (Postfix) with ESMTP id 281E213C469 for ; Thu, 7 Jun 2007 17:38:42 +0000 (UTC) (envelope-from stas@FreeBSD.org) Received: from [85.21.245.235] (helo=phonon.SpringDaemons.com) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1HwLwW-000325-04; Thu, 07 Jun 2007 21:38:40 +0400 Received: from localhost (localhost [127.0.0.1]) by phonon.SpringDaemons.com (Postfix) with SMTP id DC22F1145D; Thu, 7 Jun 2007 21:36:55 +0400 (MSD) Date: Thu, 7 Jun 2007 21:36:50 +0400 From: Stanislav Sedov To: freebsd-arch@FreeBSD.org Message-Id: <20070607213650.c02130bf.stas@FreeBSD.org> Organization: The FreeBSD Project X-Mailer: carrier-pigeon X-Voice: +7 916 849 20 23 X-XMPP: ssedov@jabber.ru X-ICQ: 208105021 X-Yahoo: stanislav_sedov X-PGP-Fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 X-University: MEPhI Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Thu__7_Jun_2007_21_36_50_+0400_q=oaWEyO7sI7gu3K" X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona 1.6.0 Cc: freebsd-hackers@FreeBSD.org, timur@gnu.org Subject: setegid bug 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, 07 Jun 2007 17:38:42 -0000 --Signature=_Thu__7_Jun_2007_21_36_50_+0400_q=oaWEyO7sI7gu3K Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! Recently several FreeBSD samba users reported a scary problem with samba (http://bugzilla.samba.org/?id=3D3990). Further research in cooperation with Timur Bakeyev (timur) showed, that we have a little problem with setegid implementation. In FreeBSD (and even in 4.4BSD-Lite2) egid of the process is merely groups[0], so calling seteuid function we simply override the first of supplementary groups. However, POSIX says that not rgid, not any of supplementary groups should bot be rewritten in setegid call. There's some comments about optimizations which caused so scary implementation, but I can't get what these optimizations are. Our first cvs revision of kern_prot.c already contains similar implementation with egid being effectively groups[0]. Probably, some of old-school committers remembered the initial intention of making egid equal to groups[0]? Probably, I have missed something? Thanks a lot! --=20 Stanislav Sedov ST4096-RIPE --Signature=_Thu__7_Jun_2007_21_36_50_+0400_q=oaWEyO7sI7gu3K Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.3 (FreeBSD) iD8DBQFGaEI3K/VZk+smlYERAkwdAJ9Sp8lDY3Pq9ip1bx9M67GR+w+cPgCeI6EK S1nHdh1Q416bECsdbapzk70= =skA0 -----END PGP SIGNATURE----- --Signature=_Thu__7_Jun_2007_21_36_50_+0400_q=oaWEyO7sI7gu3K-- From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 7 19:12:29 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 750CA16A480 for ; Thu, 7 Jun 2007 19:12:29 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.188]) by mx1.freebsd.org (Postfix) with ESMTP id 0D8E313C46E for ; Thu, 7 Jun 2007 19:12:28 +0000 (UTC) (envelope-from dudu@dudu.ro) Received: by mu-out-0910.google.com with SMTP id w9so603669mue for ; Thu, 07 Jun 2007 12:12:27 -0700 (PDT) Received: by 10.82.158.12 with SMTP id g12mr3829926bue.1181243546357; Thu, 07 Jun 2007 12:12:26 -0700 (PDT) Received: by 10.82.185.8 with HTTP; Thu, 7 Jun 2007 12:12:26 -0700 (PDT) Message-ID: Date: Thu, 7 Jun 2007 22:12:26 +0300 From: "Vlad GALU" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Status of base GDB 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, 07 Jun 2007 19:12:29 -0000 I couldn't help noticing that our gdb lags behind other BSDs. Is there a technical reason for this? I'm thinking threading changes/gcc changes (although I can't remember this kind of situation representing a setback in other BSDs' case). Thanks. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 7 21:37:54 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9EBA716A41F for ; Thu, 7 Jun 2007 21:37:54 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: from mired.org (vpn.mired.org [66.92.153.74]) by mx1.freebsd.org (Postfix) with SMTP id 2CE0413C457 for ; Thu, 7 Jun 2007 21:37:53 +0000 (UTC) (envelope-from mwm-keyword-freebsdhackers2.e313df@mired.org) Received: (qmail 53262 invoked by uid 1001); 7 Jun 2007 21:35:40 -0000 Received: by bhuda.mired.org (tmda-sendmail, from uid 1001); Thu, 07 Jun 2007 17:35:39 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <18024.31275.733694.236655@bhuda.mired.org> Date: Thu, 7 Jun 2007 17:35:39 -0400 To: Stanislav Sedov In-Reply-To: <20070607213650.c02130bf.stas@FreeBSD.org> References: <20070607213650.c02130bf.stas@FreeBSD.org> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Primary-Address: mwm@mired.org X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ X-Delivery-Agent: TMDA/1.1.11 (Ladyburn) From: Mike Meyer Cc: freebsd-hackers@FreeBSD.org, timur@gnu.org, freebsd-arch@FreeBSD.org Subject: Re: setegid bug 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, 07 Jun 2007 21:37:54 -0000 In <20070607213650.c02130bf.stas@FreeBSD.org>, Stanislav Sedov typed: > Recently several FreeBSD samba users reported a scary problem with > samba (http://bugzilla.samba.org/?id=3990). Further research in > cooperation with Timur Bakeyev (timur) showed, that we have a little > problem with setegid implementation. In FreeBSD (and even in > 4.4BSD-Lite2) egid of the process is merely groups[0], so calling > seteuid function we simply override the first of supplementary groups. > However, POSIX says that not rgid, not any of supplementary groups > should bot be rewritten in setegid call. > > Probably, some of old-school committers remembered the initial > intention of making egid equal to groups[0]? Probably, I have missed > something? The old school in this case is UC Berkeley. I found this behavior in 4.1BSD. Since it lets you violate ass-backwards group security settings (wherein you create a group "undesirables", and have files owned by that group with group bits 0 to keep them out) by removing yourself from that group, I reported it as a security bug to CSRG. Mike's response was that the security model was the bug, not this problem. I suspect it was done that way in the initial implementation, and nobody has ever felt that it should be fixed. http://www.mired.org/consulting.html Independent Network/Unix/Perforce consultant, email for more information. From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 00:39:40 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A8BC816A421 for ; Fri, 8 Jun 2007 00:39:40 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 677AF13C44C for ; Fri, 8 Jun 2007 00:39:40 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so176407anc for ; Thu, 07 Jun 2007 17:39:39 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=FD4R1Dehn9tH6FLrSdrn1YJWeNIHELatVKEuy9CGMr2rM5odsAslhdABXSTcHMIMEQW0vMFHcLatlfQVm8XnQuH/nKVR6kjGYu2FMTQvwdNbAB/BL4k87//gQSFlNqBQUVKsSV5IpQvNHIU53mEPuokeV0YZ0+yziTNwEJBO3oc= 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=ku6AACkjvrfXu2ZazdabPu5ibbwlNhACNe/LS/hnHSUKONOfpO1mWaIw6f6XrB4bDWLxbdhJ42eseHM7J8wNs1D7ZKUBgL9faHhM1eVF9lqxHPH5ZzXLUemMrfoDHzPK7WQJp+D/br6UOqXBah/NkQlGtevGzCQxP6t4d2WHAMU= Received: by 10.100.3.20 with SMTP id 20mr1387025anc.1181261730282; Thu, 07 Jun 2007 17:15:30 -0700 (PDT) Received: by 10.100.9.14 with HTTP; Thu, 7 Jun 2007 17:15:30 -0700 (PDT) Message-ID: <499c70c0706071715i321b46ddu73bdb867143e99e6@mail.gmail.com> Date: Fri, 8 Jun 2007 03:15:30 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Vlad GALU" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: freebsd-hackers@freebsd.org Subject: Re: Status of base GDB 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, 08 Jun 2007 00:39:40 -0000 On 6/7/07, Vlad GALU wrote: > I couldn't help noticing that our gdb lags behind other BSDs. Is > there a technical reason for this? I'm thinking threading changes/gcc > changes (although I can't remember this kind of situation representing > a setback in other BSDs' case). > Thanks. There is also a port not added since months *sigh* http://www.freebsd.org/cgi/query-pr.cgi?pr=100067 I wish this get resolved ASAP. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 04:00:55 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16AFB16A469; Fri, 8 Jun 2007 04:00:55 +0000 (UTC) (envelope-from grog@lemis.com) Received: from ozlabs.org (ozlabs.org [203.10.76.45]) by mx1.freebsd.org (Postfix) with ESMTP id B9A1713C45E; Fri, 8 Jun 2007 04:00:54 +0000 (UTC) (envelope-from grog@lemis.com) Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.135]) by ozlabs.org (Postfix) with ESMTP id 65461DDDD5; Fri, 8 Jun 2007 13:41:10 +1000 (EST) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id 2C1201A988A; Fri, 8 Jun 2007 13:11:10 +0930 (CST) Date: Fri, 8 Jun 2007 13:11:10 +0930 From: Greg 'groggy' Lehey To: FreeBSD Chat , FreeBSD Hackers Message-ID: <20070608034110.GA98942@wantadilla.lemis.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Organization: The FreeBSD Project Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 VoIP: sip:0871270137@sip.internode.on.net WWW-Home-Page: http://www.FreeBSD.org/ X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 Cc: Subject: Can anybody terminate an IP-IP tunnel for me? 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, 08 Jun 2007 04:00:55 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In a few weeks' time I'll be moving house, and it looks as if the new address currently doesn't have ADSL, so I'll be forced to use satellite again. I've done some investigation, and the costs don't look too prohibitive, but almost nobody is prepared to route my /24 net block (192.109.197.0/24). One alternative would be to route the block through an IP-IP tunnel from somewhere else in the Internet. I see a couple of potential problems with this approach: * I need somebody to provide the service. Do you know of anybody who can help here, for a reasonable price, or can you help yourself? Somewhere in Australia would be better, but given the satellite delay it could be almost anywhere in the world. I'd be looking to route about 2 GB a month, and the download speed of the satellite link is limited to 1 MB/s. * How do I terminate the IP-IP tunnel at my end? The last time I used it, I had a static IP address for the end of the link, and another for the end of the tunnel, which implies routing that address. This won't work in the scenario I'm looking at. Is it possible to route the tunnel to the same address as the external interface IP address? Alternatively, is there another way to handle this issue? Greg -- See complete headers for address and phone numbers. --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFGaM/WIubykFB6QiMRAtqNAKCoBJzGagoHG5BcLAbuFtzvxce/tQCeNQ4m 6wZGZl7XGhbvw2mU05HTm/A= =QBfY -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 06:48:44 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5EEFE16A400 for ; Fri, 8 Jun 2007 06:48:44 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id 00D5213C43E for ; Fri, 8 Jun 2007 06:48:43 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe11.swip.net (CommuniGate Pro SMTP 5.1.9) with ESMTPA id 344759022 for freebsd-hackers@freebsd.org; Fri, 08 Jun 2007 08:48:42 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Fri, 8 Jun 2007 08:48:36 +0200 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706080848.36402.hselasky@c2i.net> Subject: Lost interrupts during boot 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, 08 Jun 2007 06:48:44 -0000 Hi, I testing booting with a combo USB/Firewire carbus card, but no interrupts are genereated. If I plug the card in when the computer is not cold, it works fine. Any ideas? Does the cardbus driver generate a dummy interrupt to make sure that any outstanding interrupts are cleared? cbb0@pci2:6:0: class=0x060700 card=0x00641025 chip=0x8031104c rev=0x00 hdr=0x02 vendor = 'Texas Instruments (TI)' class = bridge subclass = PCI-CardBus --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 07:21:32 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C2C016A469 for ; Fri, 8 Jun 2007 07:21:32 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id DC9DF13C458 for ; Fri, 8 Jun 2007 07:21:31 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.9) with ESMTPA id 414199725; Fri, 08 Jun 2007 09:21:29 +0200 From: Hans Petter Selasky To: "Hidetoshi Shimokawa" Date: Fri, 8 Jun 2007 09:21:23 +0200 User-Agent: KMail/1.9.5 References: <200706080848.36402.hselasky@c2i.net> <626eb4530706080017w67820eabk7df95ca4ff50b695@mail.gmail.com> In-Reply-To: <626eb4530706080017w67820eabk7df95ca4ff50b695@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706080921.23638.hselasky@c2i.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 07:21:32 -0000 On Friday 08 June 2007 09:17, Hidetoshi Shimokawa wrote: > Do you have INTR_FILTER in your kernel config file? No. > Does the USB driver use interrupt filter or only ithread? Ithread. Interrupt filter is NULL I think. #if (__FreeBSD_version >= 700031) err = bus_setup_intr(self, sc->sc_irq_res, INTR_TYPE_BIO|INTR_MPSAFE, NULL, (void *)(void *)ehci_interrupt, sc, &sc->sc_intr_hdl); #else err = bus_setup_intr(self, sc->sc_irq_res, INTR_TYPE_BIO|INTR_MPSAFE, (void *)(void *)ehci_interrupt, sc, &sc->sc_intr_hdl); #endif --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 07:30:06 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8E1E716A469 for ; Fri, 8 Jun 2007 07:30:06 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.225]) by mx1.freebsd.org (Postfix) with ESMTP id 55BE613C45A for ; Fri, 8 Jun 2007 07:30:06 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by wr-out-0506.google.com with SMTP id 69so232785wra for ; Fri, 08 Jun 2007 00:30:05 -0700 (PDT) Received: by 10.65.248.19 with SMTP id a19mr2545553qbs.1181287805521; Fri, 08 Jun 2007 00:30:05 -0700 (PDT) Received: by 10.35.71.8 with HTTP; Fri, 8 Jun 2007 00:30:05 -0700 (PDT) Message-ID: <626eb4530706080030pc03d9e8t59d78956b0ba0479@mail.gmail.com> Date: Fri, 8 Jun 2007 16:30:05 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Hans Petter Selasky" In-Reply-To: <200706080921.23638.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200706080848.36402.hselasky@c2i.net> <626eb4530706080017w67820eabk7df95ca4ff50b695@mail.gmail.com> <200706080921.23638.hselasky@c2i.net> X-Google-Sender-Auth: 5e2b39489df0cac8 Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 07:30:06 -0000 The latest firewire driver I commited this week uses interrupt filter. There might be some bad interaction between them if they share IRQ. You can disable interrupt filter of firewire driver by changing #define FWOHCI_INTFILT 0 in fwohcivar.h. If you are using the latest firewire driver, can you try this? On 6/8/07, Hans Petter Selasky wrote: > On Friday 08 June 2007 09:17, Hidetoshi Shimokawa wrote: > > Do you have INTR_FILTER in your kernel config file? > > No. > > > Does the USB driver use interrupt filter or only ithread? > > Ithread. > > Interrupt filter is NULL I think. > > #if (__FreeBSD_version >= 700031) > err = bus_setup_intr(self, sc->sc_irq_res, INTR_TYPE_BIO|INTR_MPSAFE, > NULL, (void *)(void *)ehci_interrupt, sc, &sc->sc_intr_hdl); > #else > err = bus_setup_intr(self, sc->sc_irq_res, INTR_TYPE_BIO|INTR_MPSAFE, > (void *)(void *)ehci_interrupt, sc, > &sc->sc_intr_hdl); > #endif > > > --HPS > _______________________________________________ > 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" > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 07:46:16 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5F2B716A468 for ; Fri, 8 Jun 2007 07:46:16 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.239]) by mx1.freebsd.org (Postfix) with ESMTP id 2804D13C4BE for ; Fri, 8 Jun 2007 07:46:16 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by wr-out-0506.google.com with SMTP id 69so236942wra for ; Fri, 08 Jun 2007 00:46:15 -0700 (PDT) Received: by 10.64.183.6 with SMTP id g6mr4582180qbf.1181287033118; Fri, 08 Jun 2007 00:17:13 -0700 (PDT) Received: by 10.35.71.8 with HTTP; Fri, 8 Jun 2007 00:17:13 -0700 (PDT) Message-ID: <626eb4530706080017w67820eabk7df95ca4ff50b695@mail.gmail.com> Date: Fri, 8 Jun 2007 16:17:13 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Hans Petter Selasky" In-Reply-To: <200706080848.36402.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200706080848.36402.hselasky@c2i.net> X-Google-Sender-Auth: d4965e7019812014 Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 07:46:16 -0000 Do you have INTR_FILTER in your kernel config file? Does the USB driver use interrupt filter or only ithread? On 6/8/07, Hans Petter Selasky wrote: > Hi, > > I testing booting with a combo USB/Firewire carbus card, but no interrupts are > genereated. If I plug the card in when the computer is not cold, it works > fine. Any ideas? Does the cardbus driver generate a dummy interrupt to make > sure that any outstanding interrupts are cleared? > > cbb0@pci2:6:0: class=0x060700 card=0x00641025 chip=0x8031104c rev=0x00 > hdr=0x02 > vendor = 'Texas Instruments (TI)' > class = bridge > subclass = PCI-CardBus > > --HPS > _______________________________________________ > 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" > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 08:28:21 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30C7116A421; Fri, 8 Jun 2007 08:28:21 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe07.swip.net [212.247.154.193]) by mx1.freebsd.org (Postfix) with ESMTP id 958C213C4B8; Fri, 8 Jun 2007 08:28:20 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe07.swip.net (CommuniGate Pro SMTP 5.1.9) with ESMTPA id 515202738; Fri, 08 Jun 2007 10:28:19 +0200 From: Hans Petter Selasky To: "Hidetoshi Shimokawa" Date: Fri, 8 Jun 2007 10:28:12 +0200 User-Agent: KMail/1.9.5 References: <200706080848.36402.hselasky@c2i.net> <200706080921.23638.hselasky@c2i.net> <626eb4530706080030pc03d9e8t59d78956b0ba0479@mail.gmail.com> In-Reply-To: <626eb4530706080030pc03d9e8t59d78956b0ba0479@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706081028.12806.hselasky@c2i.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 08:28:21 -0000 On Friday 08 June 2007 09:30, Hidetoshi Shimokawa wrote: > The latest firewire driver I commited this week uses interrupt filter. > There might be some bad interaction between them if they share IRQ. > > You can disable interrupt filter of firewire driver by changing > #define FWOHCI_INTFILT 0 > in fwohcivar.h. > > If you are using the latest firewire driver, can you try this? I'm using this version of the FireWire driver: $FreeBSD: src/sys/dev/firewire/firewire.c,v 1.81 2005/11/25 Should I upgrade? --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 09:09:57 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E691916A41F for ; Fri, 8 Jun 2007 09:09:57 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.237]) by mx1.freebsd.org (Postfix) with ESMTP id ACE6713C448 for ; Fri, 8 Jun 2007 09:09:57 +0000 (UTC) (envelope-from freebsd@gm.nunu.org) Received: by wx-out-0506.google.com with SMTP id h28so630224wxd for ; Fri, 08 Jun 2007 02:09:57 -0700 (PDT) Received: by 10.64.210.3 with SMTP id i3mr4752288qbg.1181293796287; Fri, 08 Jun 2007 02:09:56 -0700 (PDT) Received: by 10.35.71.8 with HTTP; Fri, 8 Jun 2007 02:09:56 -0700 (PDT) Message-ID: <626eb4530706080209v4b8e1559qcd122ce36b5a747@mail.gmail.com> Date: Fri, 8 Jun 2007 18:09:56 +0900 From: "Hidetoshi Shimokawa" Sender: freebsd@gm.nunu.org To: "Hans Petter Selasky" In-Reply-To: <200706081028.12806.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200706080848.36402.hselasky@c2i.net> <200706080921.23638.hselasky@c2i.net> <626eb4530706080030pc03d9e8t59d78956b0ba0479@mail.gmail.com> <200706081028.12806.hselasky@c2i.net> X-Google-Sender-Auth: 8a780054e9fdc08c Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 09:09:58 -0000 It seems that the firewire driver is unrelated to the problem. Doesn't firewire device work too? On 6/8/07, Hans Petter Selasky wrote: > On Friday 08 June 2007 09:30, Hidetoshi Shimokawa wrote: > > The latest firewire driver I commited this week uses interrupt filter. > > There might be some bad interaction between them if they share IRQ. > > > > You can disable interrupt filter of firewire driver by changing > > #define FWOHCI_INTFILT 0 > > in fwohcivar.h. > > > > If you are using the latest firewire driver, can you try this? > > I'm using this version of the FireWire driver: > > $FreeBSD: src/sys/dev/firewire/firewire.c,v 1.81 2005/11/25 > > Should I upgrade? > > --HPS > > -- /\ Hidetoshi Shimokawa \/ simokawa@FreeBSD.ORG From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 09:25:50 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18AE316A41F; Fri, 8 Jun 2007 09:25:50 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe05.swip.net [212.247.154.129]) by mx1.freebsd.org (Postfix) with ESMTP id 7D51E13C457; Fri, 8 Jun 2007 09:25:49 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe05.swip.net (CommuniGate Pro SMTP 5.1.9) with ESMTPA id 414293327; Fri, 08 Jun 2007 11:25:47 +0200 From: Hans Petter Selasky To: "Hidetoshi Shimokawa" Date: Fri, 8 Jun 2007 11:25:41 +0200 User-Agent: KMail/1.9.5 References: <200706080848.36402.hselasky@c2i.net> <200706081028.12806.hselasky@c2i.net> <626eb4530706080209v4b8e1559qcd122ce36b5a747@mail.gmail.com> In-Reply-To: <626eb4530706080209v4b8e1559qcd122ce36b5a747@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706081125.41516.hselasky@c2i.net> Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 09:25:50 -0000 On Friday 08 June 2007 11:09, Hidetoshi Shimokawa wrote: > It seems that the firewire driver is unrelated to the problem. > Doesn't firewire device work too? > I haven't tested it. I don't have any FW devices. --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 10:03:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B9C116A41F for ; Fri, 8 Jun 2007 10:03:48 +0000 (UTC) (envelope-from p.pisati@oltrelinux.com) Received: from mail.oltrelinux.com (krisma.oltrelinux.com [194.242.226.43]) by mx1.freebsd.org (Postfix) with ESMTP id 1A47B13C45E for ; Fri, 8 Jun 2007 10:03:47 +0000 (UTC) (envelope-from p.pisati@oltrelinux.com) Received: from krisma.oltrelinux.com (krisma [127.0.0.1]) by mail.oltrelinux.com (Postfix) with ESMTP id B25F411AE91; Fri, 8 Jun 2007 11:43:32 +0200 (CEST) Received: from xs-217-221-237-206.mi2.albacom.net ([217.221.237.206]) (SquirrelMail authenticated user flag@oltrelinux.com) by krisma.oltrelinux.com with HTTP; Fri, 8 Jun 2007 11:43:32 +0200 (CEST) Message-ID: <38764.217.221.237.206.1181295812.squirrel@krisma.oltrelinux.com> In-Reply-To: <200706080848.36402.hselasky@c2i.net> References: <200706080848.36402.hselasky@c2i.net> Date: Fri, 8 Jun 2007 11:43:32 +0200 (CEST) From: "Paolo Pisati" To: "Hans Petter Selasky" User-Agent: SquirrelMail/1.4.4 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at krisma.oltrelinux.com Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 10:03:48 -0000 > I testing booting with a combo USB/Firewire carbus card, but no interrupts > are > genereated. If I plug the card in when the computer is not cold, it works > fine. Any ideas? Does the cardbus driver generate a dummy interrupt to > make > sure that any outstanding interrupts are cleared? how old is your kernel? can you see if there's a difference between a kernel earlier than Thu May 31 19:29:20 2007 UTC and a recent one (i.e. today)? -- bye, P. From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 10:17:27 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C82F16A468 for ; Fri, 8 Jun 2007 10:17:27 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.swip.net [212.247.155.1]) by mx1.freebsd.org (Postfix) with ESMTP id 37D7813C468 for ; Fri, 8 Jun 2007 10:17:27 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] Received: from [194.248.135.20] (account mc467741@c2i.net HELO laptop.lan) by mailfe09.swip.net (CommuniGate Pro SMTP 5.1.9) with ESMTPA id 345078874; Fri, 08 Jun 2007 12:17:25 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Fri, 8 Jun 2007 12:17:18 +0200 User-Agent: KMail/1.9.5 References: <200706080848.36402.hselasky@c2i.net> <38764.217.221.237.206.1181295812.squirrel@krisma.oltrelinux.com> In-Reply-To: <38764.217.221.237.206.1181295812.squirrel@krisma.oltrelinux.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200706081217.19035.hselasky@c2i.net> Cc: Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 10:17:27 -0000 On Friday 08 June 2007 11:43, Paolo Pisati wrote: > > I testing booting with a combo USB/Firewire carbus card, but no > > interrupts are > > genereated. If I plug the card in when the computer is not cold, it works > > fine. Any ideas? Does the cardbus driver generate a dummy interrupt to > > make > > sure that any outstanding interrupts are cleared? > > how old is your kernel? > can you see if there's a difference between a kernel > earlier than Thu May 31 19:29:20 2007 UTC and a recent one > (i.e. today)? I will try an update and let you know on Monday. --HPS From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 09:03:53 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2C0ED16A400 for ; Fri, 8 Jun 2007 09:03:53 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-out-05.forthnet.gr (mx-out.forthnet.gr [193.92.150.103]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0E813C46E for ; Fri, 8 Jun 2007 09:03:52 +0000 (UTC) (envelope-from dds@aueb.gr) Received: from mx-av-02.forthnet.gr (mx-av.forthnet.gr [193.92.150.27]) by mx-out-05.forthnet.gr (8.13.8/8.13.8) with ESMTP id l5893kme001590 for ; Fri, 8 Jun 2007 12:03:47 +0300 Received: from MX-IN-04.forthnet.gr (mx-in-04.forthnet.gr [193.92.150.163]) by mx-av-02.forthnet.gr (8.14.1/8.14.1) with ESMTP id l5893kJi004705 for ; Fri, 8 Jun 2007 12:03:46 +0300 Received: from [192.168.136.22] (ppp124-205.adsl.forthnet.gr [193.92.231.205]) by MX-IN-04.forthnet.gr (8.14.1/8.14.1) with ESMTP id l5893h4n004528 for ; Fri, 8 Jun 2007 12:03:45 +0300 Authentication-Results: MX-IN-04.forthnet.gr smtp.mail=dds@aueb.gr; spf=neutral Authentication-Results: MX-IN-04.forthnet.gr header.from=dds@aueb.gr; sender-id=neutral Message-ID: <46691B68.8000109@aueb.gr> Date: Fri, 08 Jun 2007 12:03:36 +0300 From: Diomidis Spinellis User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset=ISO-8859-7; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 08 Jun 2007 11:56:13 +0000 Cc: Subject: FreeBSD OLPC 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, 08 Jun 2007 09:03:53 -0000 Is anybody working on running FreeBSD on the One Laptop Per Child platform ? I'd be interested to try it, but I wouldn't want to duplicate work. The only thing I've found with a web search are some pictures of an OLPC at BSDCan . The first stumbling block would be booting with OLPC's OFW. Diomidis Spinellis - http://www.spinellis.gr From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 13:38:19 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0942516A468; Fri, 8 Jun 2007 13:38:19 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 7C4E913C455; Fri, 8 Jun 2007 13:38:18 +0000 (UTC) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.14.1/8.14.1) with ESMTP id l58DKeYY078592 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Jun 2007 15:20:41 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <20070608034110.GA98942@wantadilla.lemis.com> References: <20070608034110.GA98942@wantadilla.lemis.com> 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: Stefan Bethke Date: Fri, 8 Jun 2007 15:20:40 +0200 To: "Greg 'groggy' Lehey" X-Mailer: Apple Mail (2.752.2) Cc: FreeBSD Hackers , FreeBSD Chat Subject: Re: Can anybody terminate an IP-IP tunnel for me? 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, 08 Jun 2007 13:38:19 -0000 Am 08.06.2007 um 05:41 schrieb Greg 'groggy' Lehey: > How do I terminate the IP-IP tunnel at my end? I'm using OpenVPN for similar porposes, albeit on lower latency DSL links. OpenVPN can run over UDP or TCP, and can work through NAT, and even with dynamic IPs. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 14:20:52 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E751016A400 for ; Fri, 8 Jun 2007 14:20:52 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.234]) by mx1.freebsd.org (Postfix) with ESMTP id 7C86613C468 for ; Fri, 8 Jun 2007 14:20:52 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: by wr-out-0506.google.com with SMTP id 69so340140wra for ; Fri, 08 Jun 2007 07:20:51 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=googlemail.com; s=beta; h=domainkey-signature:received:received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=ezpUvRwgFlnpistQ3vIijUmI6lq7UPc/Y3HJkc6NMyH4ZSaA2JbfXAcx4x6lZtz9TsCSTGsbEwXrUSBfw/L0Nd7JRxup/vMHAnKcHwXCfGmttOWEUtaoQRpzvl9fx2xvpJ1fo2jeh6dUo8/AIOLkIiLOy3NNRLQHu3twh1c7zXY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=beta; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer; b=U6JQ7Vbrm9ah7mM6qqp8Fva0X44c//ul4RdYOq8BSByz87ED1lMsWEX3OAQPZVXhvUlfKrFY7kbXhSz8iAWhhcf7MLBNZTc7pwNFXwCVMhmcKyKdD8+isrdsPZ6ivWCjjJQuic0lx1l54x44r06E/7igrgWr9fo0fLyk7i2YrA4= Received: by 10.78.185.15 with SMTP id i15mr1246358huf.1181312451008; Fri, 08 Jun 2007 07:20:51 -0700 (PDT) Received: from ?IPv6:::ffff:127.0.0.1? ( [217.206.187.79]) by mx.google.com with ESMTP id f7sm6276373nfh.2007.06.08.07.20.50 (version=SSLv3 cipher=RC4-MD5); Fri, 08 Jun 2007 07:20:50 -0700 (PDT) From: Tom Evans To: Abdullah Ibn Hamad Al-Marri In-Reply-To: <499c70c0706071715i321b46ddu73bdb867143e99e6@mail.gmail.com> References: <499c70c0706071715i321b46ddu73bdb867143e99e6@mail.gmail.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-G5ceyIRBJldfxpBeR914" Date: Fri, 08 Jun 2007 15:20:48 +0100 Message-Id: <1181312448.48432.10.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.10.2 FreeBSD GNOME Team Port Cc: freebsd-hackers@freebsd.org, Vlad GALU Subject: Re: Status of base GDB 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, 08 Jun 2007 14:20:53 -0000 --=-G5ceyIRBJldfxpBeR914 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2007-06-08 at 03:15 +0300, Abdullah Ibn Hamad Al-Marri wrote: > On 6/7/07, Vlad GALU wrote: > > I couldn't help noticing that our gdb lags behind other BSDs. Is > > there a technical reason for this? I'm thinking threading changes/gcc > > changes (although I can't remember this kind of situation representing > > a setback in other BSDs' case). > > Thanks. >=20 > There is also a port not added since months *sigh* >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D100067 >=20 > I wish this get resolved ASAP. >=20 I don't see the problem? It is a shame it takes time to get stuff completely clean and fixed and ready for inclusion into the ports tree, but there is nothing stopping you from taking the shar archive from the PR and building the port for your own personal use until it is added. --=-G5ceyIRBJldfxpBeR914 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGaWXAlcRvFfyds/cRApqeAKCy/gBGHdNAPbfgHosQYXalN3rMKQCfbhfE DCWhNSDFAQZJs5hYopSGpr8= =zTTF -----END PGP SIGNATURE----- --=-G5ceyIRBJldfxpBeR914-- From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 14:30:15 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A6D1816A46B for ; Fri, 8 Jun 2007 14:30:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.freebsd.org (Postfix) with ESMTP id 6A72913C4B8 for ; Fri, 8 Jun 2007 14:30:15 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id A2CBC1FFBD3; Fri, 8 Jun 2007 16:30:13 +0200 (CEST) Received: by transport.cksoft.de (Postfix, from userid 66) id B99301FFAEC; Fri, 8 Jun 2007 16:30:06 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 25D5A444885; Fri, 8 Jun 2007 14:25:45 +0000 (UTC) Date: Fri, 8 Jun 2007 14:25:45 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Diomidis Spinellis In-Reply-To: <46691B68.8000109@aueb.gr> Message-ID: <20070608141341.A38838@maildrop.int.zabbadoz.net> References: <46691B68.8000109@aueb.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD OLPC 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, 08 Jun 2007 14:30:15 -0000 On Fri, 8 Jun 2007, Diomidis Spinellis wrote: Hi, > Is anybody working on running FreeBSD on the One Laptop Per Child platform > ? I'd be interested to try it, but I wouldn't want to > duplicate work. The only thing I've found with a web search are some > pictures of an OLPC at BSDCan . The first > stumbling block would be booting with OLPC's OFW. Oh that was during the last day's post-conference "social event", lateish in a bar and thing was running out of battery and crashed two times... There was a talk about it http://www.bsdcan.org/2007/schedule/events/57.en.html I had seen the presentation at FOSDEM and there was that "How Open Source Projects Survive Poisonous People", so I didn't attend. I am not going to comment more on the Software that this thing was running (the built-in camera was working;) but I don't think there is anything BSD related... Considering OFW, Sun released that under a 3 clause BSD license somewhen last year imho. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 15:52:32 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5ACBB16A46B for ; Fri, 8 Jun 2007 15:52:32 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout3.cac.washington.edu (mxout3.cac.washington.edu [140.142.32.166]) by mx1.freebsd.org (Postfix) with ESMTP id 39D6213C45A for ; Fri, 8 Jun 2007 15:52:32 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout3.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.05) with ESMTP id l58FqTCs022695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 8 Jun 2007 08:52:29 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l58FqSkX001141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 8 Jun 2007 08:52:29 -0700 Message-ID: <46697B3F.7080505@u.washington.edu> Date: Fri, 08 Jun 2007 08:52:31 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: Hans Petter Selasky References: <200706080848.36402.hselasky@c2i.net> <38764.217.221.237.206.1181295812.squirrel@krisma.oltrelinux.com> <200706081217.19035.hselasky@c2i.net> In-Reply-To: <200706081217.19035.hselasky@c2i.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.6.8.83248 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' Cc: freebsd-hackers@freebsd.org Subject: Re: Lost interrupts during boot 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, 08 Jun 2007 15:52:32 -0000 Hans Petter Selasky wrote: > On Friday 08 June 2007 11:43, Paolo Pisati wrote: > >>> I testing booting with a combo USB/Firewire carbus card, but no >>> interrupts are >>> genereated. If I plug the card in when the computer is not cold, it works >>> fine. Any ideas? Does the cardbus driver generate a dummy interrupt to >>> make >>> sure that any outstanding interrupts are cleared? >>> >> how old is your kernel? >> can you see if there's a difference between a kernel >> earlier than Thu May 31 19:29:20 2007 UTC and a recent one >> (i.e. today)? >> > > I will try an update and let you know on Monday. > > --HPS Who makes your MB? Is it an nVidia chipset one? -Garrett From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 16:27:11 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0403116A468 for ; Fri, 8 Jun 2007 16:27:11 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 7C7E013C487 for ; Fri, 8 Jun 2007 16:27:10 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.org (p549A4B70.dip.t-dialin.net [84.154.75.112]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l58FtO0A049213 for ; Fri, 8 Jun 2007 17:55:28 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.org (8.13.6/8.13.6) with ESMTP id l58FtL63051897 for ; Fri, 8 Jun 2007 17:55:21 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id l58FuQPu028947 for ; Fri, 8 Jun 2007 17:56:26 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Received: (from jhs@localhost) by fire.jhs.private (8.13.6/8.13.6/Submit) id l58FuQpn028946; Fri, 8 Jun 2007 17:56:26 +0200 (CEST) (envelope-from jhs) Date: Fri, 8 Jun 2007 17:56:26 +0200 (CEST) Message-Id: <200706081556.l58FuQpn028946@fire.jhs.private> To: hackers@freebsd.org From: "Julian Stacey" Organization: http://berklix.com BSD Unix C Net Consultancy, Munich/Muenchen Fcc: sent User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com/~jhs/cv/ X-Fallback: jhs@mail.brierdr.com, jhs@freebsd.org, jhs@berklix.net Cc: Subject: FreeBSD-6.2 & PLIP - does it still work ? 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, 08 Jun 2007 16:27:11 -0000 Anyone seen PLIP working on FreeBSD-6.2 release ? I've tested my PLIP cable between 2 x 4.11 boxes. I'm trying to install a laptop with 6.2 boot flops (with failed pcmcia/ether recognition) I cant get that laptop & a 6.2 tower to talk to each other. Neither will those 2 x 6.2 talk to 4.11. I havent quite done all exhaustive tests, (but am exhausted & seems worth asking :-) Julian -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com HTML mail=spam. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 16:53:03 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B449016A475; Fri, 8 Jun 2007 16:53:03 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 23FB713C45E; Fri, 8 Jun 2007 16:53:02 +0000 (UTC) (envelope-from stb@lassitu.de) Received: (from stb@koef.zs64.net) (authenticated) by koef.zs64.net (8.14.1/8.14.1) with ESMTP id l58Gr1S1008374 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 8 Jun 2007 18:53:01 +0200 (CEST) (envelope-from stb@lassitu.de) In-Reply-To: <200706081547.l58FlEsb084443@lurza.secnetix.de> References: <200706081547.l58FlEsb084443@lurza.secnetix.de> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <517403D5-E9FD-43EB-A027-7E0869939E55@lassitu.de> Content-Transfer-Encoding: 7bit From: Stefan Bethke Date: Fri, 8 Jun 2007 18:53:40 +0200 To: Oliver Fromme X-Mailer: Apple Mail (2.752.2) Cc: hackers@freebsd.org, chat@freebsd.org Subject: Re: Can anybody terminate an IP-IP tunnel for me? 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, 08 Jun 2007 16:53:03 -0000 Am 08.06.2007 um 17:47 schrieb Oliver Fromme: > While OpenVPN works well usually, it is generally not > advisable to run it over TCP, especially if your link > is not guaranteed to have 0% packet loss, which might > be the case for satellite links. Running OpenVPN over > UDP is fine. Sure, but slightly less than perfect connectivity is still better than none: being stuck on a corporate network, where you can use the proxy to establish a TCP connection to port 443, for example. Stefan -- Stefan Bethke Fon +49 170 346 0140 From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 16:26:35 2007 Return-Path: X-Original-To: hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 80FE816A421; Fri, 8 Jun 2007 16:26:35 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id E40A913C4C2; Fri, 8 Jun 2007 16:26:34 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (ajchob@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l58FlEVn084444; Fri, 8 Jun 2007 17:47:19 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l58FlEsb084443; Fri, 8 Jun 2007 17:47:14 +0200 (CEST) (envelope-from olli) Date: Fri, 8 Jun 2007 17:47:14 +0200 (CEST) Message-Id: <200706081547.l58FlEsb084443@lurza.secnetix.de> From: Oliver Fromme To: chat@FreeBSD.ORG, hackers@FreeBSD.ORG In-Reply-To: X-Newsgroups: list.freebsd-chat User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Fri, 08 Jun 2007 17:47:19 +0200 (CEST) X-Mailman-Approved-At: Fri, 08 Jun 2007 18:20:36 +0000 Cc: Subject: Re: Can anybody terminate an IP-IP tunnel for me? 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, 08 Jun 2007 16:26:35 -0000 Stefan Bethke wrote: > Greg 'groggy' Lehey wrote: > > How do I terminate the IP-IP tunnel at my end? > > I'm using OpenVPN for similar porposes, albeit on lower latency DSL > links. OpenVPN can run over UDP or TCP, and can work through NAT, > and even with dynamic IPs. While OpenVPN works well usually, it is generally not advisable to run it over TCP, especially if your link is not guaranteed to have 0% packet loss, which might be the case for satellite links. Running OpenVPN over UDP is fine. That problem has been discussed and explained quite often in various forums. Here's one of them: http://sites.inka.de/sites/bigred/devel/tcp-tcp.html I've used OpenVPN myself to tunnel official IP addresses to my (dynamic) DSL link at home. You need to have a server outside somewhere, of course, but that shouldn't be a problem. Here in .de you can rent a good root server for <= 50 Euro per month ("good" means you can install FreeBSD remotely without difficulty). I guess it's not much different in .au or elsewhere in the world. And if you share it with a few friends or collegues, then the costs are even less. That's how I've done it; I share a 50 Euro root server with three friends, so I pay only 12,50 per month. Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "Python is an experiment in how much freedom programmers need. Too much freedom and nobody can read another's code; too little and expressiveness is endangered." -- Guido van Rossum From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 19:01:16 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 73E5D16A46F; Fri, 8 Jun 2007 19:01:16 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0269A13C48A; Fri, 8 Jun 2007 19:01:15 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.1/8.14.1) with ESMTP id l58IVlmR085246; Fri, 8 Jun 2007 11:31:55 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.1/8.14.1/Submit) with ESMTP id l58IVl58085243; Fri, 8 Jun 2007 11:31:47 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 8 Jun 2007 11:31:47 -0700 (PDT) From: mjacob@freebsd.org To: Oliver Fromme In-Reply-To: <200706081547.l58FlEsb084443@lurza.secnetix.de> Message-ID: <20070608113000.E85226@ns1.feral.com> References: <200706081547.l58FlEsb084443@lurza.secnetix.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org, chat@freebsd.org Subject: Re: Can anybody terminate an IP-IP tunnel for me? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 19:01:16 -0000 > I've used OpenVPN myself to tunnel official IP addresses > to my (dynamic) DSL link at home. You need to have a > server outside somewhere, of course, but that shouldn't I find that vtun is a pretty reliable and less heavyweight solution for this- I use it to get a tunnel to a secondary lab of mine (at my mom's house) which only has dynamic IP. The only problem here is that this isn't a solution for providing routing for somebody else's Class C block. -matt From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 19:23:59 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 300ED16A485 for ; Fri, 8 Jun 2007 19:23:59 +0000 (UTC) (envelope-from ghozzy@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 08A4313C44C for ; Fri, 8 Jun 2007 19:23:58 +0000 (UTC) (envelope-from ghozzy@gmail.com) Received: by wa-out-1112.google.com with SMTP id j37so1320133waf for ; Fri, 08 Jun 2007 12:23:58 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=CPwQgXi38VPkXYYnctmO7JBHQskH1+R6uSurYLlvY3gqTlz4dRBh6PmDEoy2zulDDx2zbn7Fv7PQSWl3LFfpJfNdDVYHKQSYbuskLxNaJzKVOxzGJ16yUeQDmOxuFhv0okwGwjTwW05T0oRJtvKkzOffCbz/88DysnvGpqOp9R8= 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=m7fCdAHRAo8opUNCFQgbEr1ZtBk4ZMso24xQWtBlBj4D+28PmlVdy0ga5UZXBqe+ssZLd90Gpsmhu54DQ8aOJ+Q9Ja19CMUJiQgNlNPqMow/ZjJ57HXHQKr2IoMRKjZGI88dzNTy4HLv1O132QUVWHRzqO2XOaiX2nkExFyVujI= Received: by 10.114.73.1 with SMTP id v1mr2910874waa.1181329166857; Fri, 08 Jun 2007 11:59:26 -0700 (PDT) Received: by 10.114.135.20 with HTTP; Fri, 8 Jun 2007 11:59:26 -0700 (PDT) Message-ID: Date: Fri, 8 Jun 2007 22:59:26 +0400 From: ghozzy To: "Julian Stacey" In-Reply-To: <200706081556.l58FuQpn028946@fire.jhs.private> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200706081556.l58FuQpn028946@fire.jhs.private> Cc: hackers@freebsd.org Subject: Re: FreeBSD-6.2 & PLIP - does it still work ? 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, 08 Jun 2007 19:23:59 -0000 On 6/8/07, Julian Stacey wrote: > Anyone seen PLIP working on FreeBSD-6.2 release ? > I've tested my PLIP cable between 2 x 4.11 boxes. I'm trying to > install a laptop with 6.2 boot flops (with failed pcmcia/ether > recognition) I cant get that laptop & a 6.2 tower to talk to each > other. Neither will those 2 x 6.2 talk to 4.11. I havent quite > done all exhaustive tests, (but am exhausted & seems worth asking :-) > > Julian > -- > Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com > HTML mail=spam. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. It seems to me PLIP has been broken somwhere after branching RELENG_5. Between two RELENG_4 it worked fine (used from about 4.3 to latest 4.11). If any end was using RELENG_5 or RELENG_6 it didn't work any more. I thought first, maybe there were some incompatible changes in protocol or something, i tried to use the same FreeBSD versions on two ends (both RELENG_5 or both RELENG_6), but that was not the case. My tests were not exhaustive either, but i actually tried to fire it up again numerous times, enough for my own assurance. If anybody could shed some light, i would be curious. I could also make tests if needed. -- ghozzy From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 20:17:07 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9242916A469 for ; Fri, 8 Jun 2007 20:17:07 +0000 (UTC) (envelope-from ap@bnc.net) Received: from mailomat.net (mailomat.net [217.110.117.101]) by mx1.freebsd.org (Postfix) with ESMTP id 2A47D13C448 for ; Fri, 8 Jun 2007 20:17:06 +0000 (UTC) (envelope-from ap@bnc.net) X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on f-1.mailomat.net X-Spam-Level: X-Spam-Status: No, hits=-4.1 required=4.0 tests=ALL_TRUSTED=-1.8, AWL=0.276, BAYES_00=-2.599 autolearn=ham version=3.1.7 X-TFF-CGPSA-Version: 1.5 X-Mailomat-CGPSA-Filter: Scanned X-Mailomat-SpamCatcher-Score: 2 [X] X-Mailomat-Cloudmark-Score: 0.000000 [] Received: from [194.39.192.125] (account bnc-mail@mailrelay.mailomat.net HELO bnc.net) by mailomat.net (CommuniGate Pro SMTP 5.1.9) with ESMTPSA id 21800917 for hackers@freebsd.org; Fri, 08 Jun 2007 21:17:02 +0200 X-SpamCatcher-Score: 2 [X] Received: from [194.39.192.239] (account ap HELO [194.39.192.239]) by bnc.net (CommuniGate Pro SMTP 5.1.9) with ESMTPSA id 2824778 for hackers@freebsd.org; Fri, 08 Jun 2007 21:15:22 +0200 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <20070608113000.E85226@ns1.feral.com> References: <200706081547.l58FlEsb084443@lurza.secnetix.de> <20070608113000.E85226@ns1.feral.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <232616AA-03AF-4909-9177-CCE2E3CFF53C@bnc.net> Content-Transfer-Encoding: 7bit From: Achim Patzner Date: Fri, 8 Jun 2007 21:17:00 +0200 To: hackers@freebsd.org X-Mailer: Apple Mail (2.752.3) Cc: Subject: Re: Can anybody terminate an IP-IP tunnel for me? 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, 08 Jun 2007 20:17:07 -0000 On 08.06.2007, at 20:31, mjacob@freebsd.org wrote: > The only problem here is that this isn't a solution for providing > routing for somebody else's Class C block. Why? inetnum: 192.109.197.0 - 192.109.197.255 netname: LEMIS-LAN descr: LEMIS Lehey Microcomputer Systems descr: D-W-6324 Feldatal descr: Germany country: DE admin-c: GL3-RIPE tech-c: GL3-RIPE rev-srv: allegro.lemis.de rev-srv: ns.cls.net rev-srv: ns.maz.net mnt-by: AS2871-MNT status: ASSIGNED PI source: RIPE # Filtered Its current provider was able to add it to their AS, too so it shouldn't be that much of a problem in Australia. I remember my ISP (QSC Germany) being a bit too... unexperienced at first so they sent me on to one of their resellers (who knew how to configure BGP) and they warned me that they wouldn't accept anything less than a /22 but things might be a bit different on the wrong side of the planet. I'd just get the defunct rev-srv records out of the database entry and send an update for the ownership records. Achim From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 20:50:05 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5537E16A400 for ; Fri, 8 Jun 2007 20:50:05 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 3138E13C45E for ; Fri, 8 Jun 2007 20:50:05 +0000 (UTC) (envelope-from mjacob@freebsd.org) Received: from ns1.feral.com (localhost [127.0.0.1]) by ns1.feral.com (8.14.1/8.14.1) with ESMTP id l58KnaA5085826; Fri, 8 Jun 2007 13:49:44 -0700 (PDT) (envelope-from mjacob@freebsd.org) Received: from localhost (mjacob@localhost) by ns1.feral.com (8.14.1/8.14.1/Submit) with ESMTP id l58KnZ6o085823; Fri, 8 Jun 2007 13:49:36 -0700 (PDT) (envelope-from mjacob@freebsd.org) X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs Date: Fri, 8 Jun 2007 13:49:35 -0700 (PDT) From: mjacob@freebsd.org To: Achim Patzner In-Reply-To: <232616AA-03AF-4909-9177-CCE2E3CFF53C@bnc.net> Message-ID: <20070608134658.G85746@ns1.feral.com> References: <200706081547.l58FlEsb084443@lurza.secnetix.de> <20070608113000.E85226@ns1.feral.com> <232616AA-03AF-4909-9177-CCE2E3CFF53C@bnc.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: hackers@freebsd.org Subject: Re: Can anybody terminate an IP-IP tunnel for me? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mjacob@freebsd.org List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jun 2007 20:50:05 -0000 > On 08.06.2007, at 20:31, mjacob@freebsd.org wrote: >> The only problem here is that this isn't a solution for providing routing >> for somebody else's Class C block. > > Why? > > inetnum: 192.109.197.0 - 192.109.197.255 > netname: LEMIS-LAN > descr: LEMIS Lehey Microcomputer Systems > descr: D-W-6324 Feldatal > descr: Germany > country: DE > admin-c: GL3-RIPE > tech-c: GL3-RIPE > rev-srv: allegro.lemis.de > rev-srv: ns.cls.net > rev-srv: ns.maz.net > mnt-by: AS2871-MNT > status: ASSIGNED PI > source: RIPE # Filtered > > Its current provider was able to add it to their AS, too so it shouldn't be > that much of a problem in Australia. I remember my ISP (QSC Germany) being a > bit too... unexperienced at first so they sent me on to one of their > resellers (who knew how to configure BGP) and they warned me that they > wouldn't accept anything less than a /22 but things might be a bit different > on the wrong side of the planet. > > I'd just get the defunct rev-srv records out of the database entry and send > an update for the ownership records. In general ISPs are now very reluctant do less than a /22 or larget if it's not carved out of one of their blocks. It was a fair amount of hunting around in Menlo Park for me to find somebody to route FERAL.COM, and the big home serving ISPs like Sprint and Yahoo!/SBC were completely clueless about being asked if they would do so- even for a fee. -matt From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 20:55:59 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3863E16A400 for ; Fri, 8 Jun 2007 20:55:59 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: from gwyn.kn-bremen.de (gwyn.kn-bremen.de [212.63.36.242]) by mx1.freebsd.org (Postfix) with ESMTP id E545613C457 for ; Fri, 8 Jun 2007 20:55:58 +0000 (UTC) (envelope-from nox@saturn.kn-bremen.de) Received: by gwyn.kn-bremen.de (Postfix, from userid 10) id 43A2E1615CA; Fri, 8 Jun 2007 22:27:15 +0200 (CEST) Received: from saturn.kn-bremen.de (nox@localhost [127.0.0.1]) by saturn.kn-bremen.de (8.13.6/8.13.6) with ESMTP id l58KOpJC025657; Fri, 8 Jun 2007 22:24:51 +0200 (CEST) (envelope-from nox@saturn.kn-bremen.de) Received: (from nox@localhost) by saturn.kn-bremen.de (8.13.6/8.13.6/Submit) id l58KOoLC025656; Fri, 8 Jun 2007 22:24:50 +0200 (CEST) (envelope-from nox) From: Juergen Lock Date: Fri, 8 Jun 2007 22:24:50 +0200 To: Allan Jude Message-ID: <20070608202450.GA23993@saturn.kn-bremen.de> Mail-Followup-To: Allan Jude , bug-followup@FreeBSD.org, freebsd-hackers@freebsd.org, freebsd-emulation@freebsd.org References: <200706081510.l58FAA84097522@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200706081510.l58FAA84097522@freefall.freebsd.org> User-Agent: Mutt/1.5.14 (2007-02-12) X-Mailman-Approved-At: Fri, 08 Jun 2007 21:05:51 +0000 Cc: freebsd-hackers@FreeBSD.org, freebsd-emulation@FreeBSD.org, bug-followup@FreeBSD.org Subject: Re: ports/113430: Kernel Panic with emulators/qemu on AMD64 SMP 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, 08 Jun 2007 20:55:59 -0000 On Fri, Jun 08, 2007 at 03:10:10PM +0000, Allan Jude wrote: > I recreated it again, and the 'stopped at' in the kernel panic is: > > userret+0x22 movq 0(%rdi),%rbx Ok so apparently userret was called with a bogus td arg, can you find out from where? (there should be a return address on the stack, userret here starts with a sub $0x28,%rsp (hmm, no frame pointer?) so add that or whatever yours subtracts.) Btw, > fault virtual address = 0x202 > fault code = supervisor read, page not present >[...] > #9 0xffffffff80650f5d in trap (frame= > {tf_rdi = 0xffffff012f655720, tf_rsi = 0x4, tf_rdx = 0x46, tf_rcx >[...] shouldnt tf_rdi here be rdi at the time of the fault, i.e. 0x202? Anyone know why its different? Also, as mentioned above userret doesnt save a frame pointer here (rbp) and indeed, > 0xffffff012f655720, tf_rax = 0x2, tf_rbx = 0xf4240, tf_rbp = > 0xffffffffb38f5d10, tf_r10 = 0xffffff012b39e108, tf_r11 = 0x2, tf_r12 = >[...] > tf_rflags = 0x10282, tf_rsp = 0xffffffffb38f5bb0, tf_ss = tf_rbp seems to be way off compared to tf_rsp, are parts of the kernel now compiled with -fomit-frame-pointer? (even for a debug kernel?) This may explain why we dont see who called userret in the kgdb backtrace... From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 8 22:24:05 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8AC7116A41F for ; Fri, 8 Jun 2007 22:24:05 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.241]) by mx1.freebsd.org (Postfix) with ESMTP id 4545813C487 for ; Fri, 8 Jun 2007 22:24:05 +0000 (UTC) (envelope-from almarrie@gmail.com) Received: by an-out-0708.google.com with SMTP id c14so265752anc for ; Fri, 08 Jun 2007 15:24:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; 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; b=XV2iCeeI+LSXi5aCJBtaOQ4b+qQTWWn60iM7uyW8HC68vbFSUhaONsOt3MZhmpLCzUexf8hb50hS8iI1aWL650wkghizXpzMyuYSeSivUctd16ooiSnSU1bc9pajaVYnSxMmkETaCiVuczLVxRd1LGoI2/x1KFR9J1h9I8XIgrI= 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=L20PAapjP7atFXre0dsjw0kZzgY5IPhd7tqdgCEE0dssUes03be+IKMXJF0H4Zux1GFBO6a37DzpN863WRol5ww6tTRP1Dt1DU73wcZPNdtuBdEslUG+VzkF2i7P6RSNxWkW3N53miHit3guLbLvTY6egKHxRXuzWSa5ciiNbfs= Received: by 10.100.13.12 with SMTP id 12mr2056851anm.1181341444687; Fri, 08 Jun 2007 15:24:04 -0700 (PDT) Received: by 10.100.9.14 with HTTP; Fri, 8 Jun 2007 15:24:04 -0700 (PDT) Message-ID: <499c70c0706081524k3d2c0059n8376e18ce8995a2b@mail.gmail.com> Date: Sat, 9 Jun 2007 01:24:04 +0300 From: "Abdullah Ibn Hamad Al-Marri" To: "Tom Evans" In-Reply-To: <1181312448.48432.10.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <499c70c0706071715i321b46ddu73bdb867143e99e6@mail.gmail.com> <1181312448.48432.10.camel@localhost> Cc: freebsd-hackers@freebsd.org, Vlad GALU Subject: Re: Status of base GDB 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, 08 Jun 2007 22:24:05 -0000 On 6/8/07, Tom Evans wrote: > On Fri, 2007-06-08 at 03:15 +0300, Abdullah Ibn Hamad Al-Marri wrote: > > On 6/7/07, Vlad GALU wrote: > > > I couldn't help noticing that our gdb lags behind other BSDs. Is > > > there a technical reason for this? I'm thinking threading changes/gcc > > > changes (although I can't remember this kind of situation representing > > > a setback in other BSDs' case). > > > Thanks. > > > > There is also a port not added since months *sigh* > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=100067 > > > > I wish this get resolved ASAP. > > > > I don't see the problem? It is a shame it takes time to get stuff > completely clean and fixed and ready for inclusion into the ports tree, > but there is nothing stopping you from taking the shar archive from the > PR and building the port for your own personal use until it is added. I'm not saying I can't get it installed. The issue is why does it take forever, it's shame as you said. -- Regards, -Abdullah Ibn Hamad Al-Marri Arab Portal http://www.WeArab.Net/ From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 10:39:22 2007 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2074916A421 for ; Sat, 9 Jun 2007 10:39:22 +0000 (UTC) (envelope-from stsp@stsp.name) Received: from einhorn.in-berlin.de (einhorn.in-berlin.de [192.109.42.8]) by mx1.freebsd.org (Postfix) with ESMTP id A637A13C45E for ; Sat, 9 Jun 2007 10:39:21 +0000 (UTC) (envelope-from stsp@stsp.name) X-Envelope-From: stsp@stsp.name Received: from stsp.lan (stsp.in-vpn.de [217.197.85.96]) (authenticated bits=128) by einhorn.in-berlin.de (8.13.6/8.13.6/Debian-1) with ESMTP id l59AdIql031272 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 9 Jun 2007 12:39:19 +0200 Received: from ted.stsp.lan (localhost [127.0.0.1]) by stsp.lan (8.13.8/8.13.8) with ESMTP id l59AcoJo003202; Sat, 9 Jun 2007 12:38:50 +0200 (CEST) (envelope-from stsp@stsp.name) Received: (from stsp@localhost) by ted.stsp.lan (8.13.8/8.13.8/Submit) id l59Acmeu003200; Sat, 9 Jun 2007 12:38:48 +0200 (CEST) (envelope-from stsp@stsp.name) X-Authentication-Warning: ted.stsp.lan: stsp set sender to stsp@stsp.name using -f Date: Sat, 9 Jun 2007 12:38:48 +0200 From: Stefan Sperling To: bug-followup@FreeBSD.org Message-ID: <20070609103848.GA1465@ted.stsp.lan> Mail-Followup-To: bug-followup@FreeBSD.org, Edwin Mons , freebsd-hackers@freebsd.org References: <466A6DF1.3020306@edwinm.ik.nu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: <466A6DF1.3020306@edwinm.ik.nu> User-Agent: Mutt/1.5.15 (2007-04-06) X-Scanned-By: MIMEDefang_at_IN-Berlin_e.V. on 192.109.42.8 Cc: freebsd-hackers@FreeBSD.org, Edwin Mons Subject: Re: kern/83807: [sis] [patch] if_sis: Wake On Lan 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, 09 Jun 2007 10:39:22 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jun 09, 2007 at 11:08:01AM +0200, Edwin Mons wrote: > Will this feature ever be incorporated in mainstream FreeBSD? I'm eager= ly=20 > waiting for it to land in -CURRENT... I have no idea. I haven't got much feedback on this patch, apart from one or two people who sent me a quick thank you note :) So I have no idea how many people are actually using the patch. I know that: * if_sis and if_vr wake on lan support is very stable for me. I've been using this code for nearly 2 years now. * if_nve support has afaik never been tested (plus it's a binary blob driver and will apparently be replaced with OpenBSD's nfe driver soon.) I run a single 6.2 box here that I maintain the patch for. I'd be happy to setup a -current box to port the patch to -CURRENT. But I need to know whether it's worth doing the work. I'd like to get feedback on my patch by someone who is willing and able to help me get it into the tree. I need to know what needs to be done and/or changed to make the patch ready for mainline. There are some small bits in the patch that are incomplete, e.g. "secure on password" support. I've been thinking about simply dropping this feature because I consider it useless but ymmv. I'd also be happy to add WOL support for more chipsets. Adding support is relatively easy as long as another open source OS (e.g. Linux) supports wake on lan for a chipset and even easier if a good datasheet is available (as in case of if_sis). If anyone has a card that does wake on lan after shutdown from Linux but not after shutdown from FreeBSD with my patch applied let me know. You may need to use the ethtool utility to enable WOL on Linux. Cc'ing hackers@ in case someone there is interested in helping out. > Kind regards, > Edwin Mons --=20 stefan http://stsp.name PGP Key: 0xF59D25F0 --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGaoM45dMCc/WdJfARAkCVAJ4sGsoZllkxTMLZCcdrnllYrmVE5ACfbRhm e0VRmi3y+uMcksCsP6QX9IQ= =j6TM -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 13:10:54 2007 Return-Path: X-Original-To: hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13F6516A46C for ; Sat, 9 Jun 2007 13:10:54 +0000 (UTC) (envelope-from zhouzhouyi@ercist.iscas.ac.cn) Received: from ercist.iscas.ac.cn (ercist.iscas.ac.cn [124.16.138.3]) by mx1.freebsd.org (Postfix) with SMTP id EEF6C13C487 for ; Sat, 9 Jun 2007 13:10:50 +0000 (UTC) (envelope-from zhouzhouyi@ercist.iscas.ac.cn) Received: (qmail 13482 invoked by uid 98); 9 Jun 2007 12:41:43 -0000 Received: from 210.77.3.198 by ercist.iscas.ac.cn (envelope-from , uid 89) with qmail-scanner-1.25 (spamassassin: 3.1.0. Clear:RC:1(210.77.3.198):SA:0(2.2/10.0):. Processed in 5.296672 secs); 09 Jun 2007 12:41:43 -0000 X-Spam-Status: No, hits=2.2 required=10.0 X-Spam-Level: ++ X-Qmail-Scanner-Mail-From: zhouzhouyi@ercist.iscas.ac.cn via ercist.iscas.ac.cn X-Qmail-Scanner: 1.25 (Clear:RC:1(210.77.3.198):SA:0(2.2/10.0):. Processed in 5.296672 secs) Received: from unknown (HELO iosdf17a8152bc) (zhouzhouyi@ercist.iscas.ac.cn@210.77.3.198) by 0 with SMTP; 9 Jun 2007 12:41:38 -0000 Message-ID: <003501c7aa93$7e5c96a0$c6034dd2@iosdf17a8152bc> From: "Zhouyi Zhou" To: Date: Sat, 9 Jun 2007 20:41:23 +0800 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.3028 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-RFC2646: Format=Flowed; Original X-Mailman-Approved-At: Sat, 09 Jun 2007 13:26:59 +0000 Cc: current@FreeBSD.org Subject: a gdb patch for fbsd X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Zhouyi Zhou List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2007 13:10:54 -0000 Dear all, Following is a patch to current gdb support in FreeBSD. I think it is useful when FreeBSD is not going to upgrade its gdb to gdb 6.x. The patch settle the core dump problem of attach command without a object file: #gdb gdb> attach XXXX http://www.vlakno.cz/~rdivacky/gdb.patch Thanks rdivacky @FreeBSD.org for encouraging me settle this bug. Sincerely Zhouyi Zhou From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 16:02:15 2007 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CCB1716A421 for ; Sat, 9 Jun 2007 16:02:15 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.freebsd.org (Postfix) with ESMTP id 48C5513C44B for ; Sat, 9 Jun 2007 16:02:15 +0000 (UTC) (envelope-from jhs@berklix.org) Received: from js.berklix.org (p549a4b46.dip.t-dialin.net [84.154.75.70]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id l59G1i8c002832; Sat, 9 Jun 2007 18:01:45 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.org (8.13.6/8.13.6) with ESMTP id l59G1ecd056030; Sat, 9 Jun 2007 18:01:40 +0200 (CEST) (envelope-from jhs@berklix.org) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.6/8.13.6) with ESMTP id l59G2psm042173; Sat, 9 Jun 2007 18:02:51 +0200 (CEST) (envelope-from jhs@fire.jhs.private) Message-Id: <200706091602.l59G2psm042173@fire.jhs.private> To: ghozzy From: "Julian Stacey" Organization: http://berklix.com BSD Unix C Net Consultancy, Munich/Muenchen User-agent: EXMH http://beedub.com/exmh/ on FreeBSD http://freebsd.org X-URL: http://berklix.com X-Fallback: jhs@mail.brierdr.com, jhs@freebsd.org, jhs@berklix.net In-reply-to: Your message of "Fri, 08 Jun 2007 22:59:26 +0400." Date: Sat, 09 Jun 2007 18:02:51 +0200 Sender: jhs@berklix.org Cc: jhs@berklix.org, hackers@freebsd.org Subject: Re: FreeBSD-6.2 & PLIP - does it still work ? 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, 09 Jun 2007 16:02:15 -0000 Reference: > From: ghozzy > Date: Fri, 8 Jun 2007 22:59:26 +0400 > Message-id: ghozzy wrote: > On 6/8/07, Julian Stacey wrote: > > Anyone seen PLIP working on FreeBSD-6.2 release ? > > I've tested my PLIP cable between 2 x 4.11 boxes. I'm trying to > > install a laptop with 6.2 boot flops (with failed pcmcia/ether > > recognition) I cant get that laptop & a 6.2 tower to talk to each > > other. Neither will those 2 x 6.2 talk to 4.11. I havent quite > > done all exhaustive tests, (but am exhausted & seems worth asking :-) > > > > Julian > > -- > > Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com > > HTML mail=spam. Ihr Rauch=mein allergischer Kopfschmerz. Dump cigs 4 snuff. > > It seems to me PLIP has been broken somwhere after branching RELENG_5. > Between two RELENG_4 it worked fine (used from about 4.3 to latest 4.11). > If any end was using RELENG_5 or RELENG_6 it didn't work any more. > I thought first, maybe there were some incompatible changes in protocol > or something, i tried to use the same FreeBSD versions on two ends > (both RELENG_5 or both RELENG_6), but that was not the case. > > My tests were not exhaustive either, but i actually tried to fire it up again > numerous times, enough for my own assurance. > > If anybody could shed some light, i would be curious. > I could also make tests if needed. Thanks for confirmation ghozzy, Can anyone say eg "No it works for me" ? Or now we know PL-IP is broken, Options: - Post net@freebsd for specialists, - Post mobile@freebsd (where it most hurts, as PLIP really needed when pcmcia slots not recognised on older laptops so cant install FreeBSD). - Send-pr for manual to declare plip broken. - Read & compare source of 4.11 & 6.2 Release src/sys/dev/ppbus/if_plip.c (interesting, but short of time, & others who've hacked / broken it might fix quicker ?) I viewed with /usr/ports/textproc/mgdiff & diff not that big, eg diff -c 4.11/usr/src/sys/dev/ppbus/if_plip.c.~1~ \ 6.1/usr/src/sys/dev/ppbus/if_plip.c.~1~ | wc 481 1466 11651 Julian -- Julian Stacey. Munich Computer Consultant, BSD Unix C Linux. http://berklix.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 15:38:38 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7890616A400 for ; Sat, 9 Jun 2007 15:38:38 +0000 (UTC) (envelope-from freebsd@edwinm.ik.nu) Received: from mag.ik.nu (mag.ik.nu [80.255.245.75]) by mx1.freebsd.org (Postfix) with ESMTP id 4271913C45A for ; Sat, 9 Jun 2007 15:38:38 +0000 (UTC) (envelope-from freebsd@edwinm.ik.nu) Received: from localhost (localhost [127.0.0.1]) by mag.ik.nu (Postfix) with ESMTP id D2441A1043; Sat, 9 Jun 2007 17:08:09 +0200 (CEST) X-Virus-Scanned: amavisd-new at ik.nu Received: from mag.ik.nu ([127.0.0.1]) by localhost (mag.ik.nu [127.0.0.1]) (amavisd-new, port 10024) with SMTP id PP038sKmxR7o; Sat, 9 Jun 2007 17:08:07 +0200 (CEST) Received: from [172.16.1.18] (s5591501b.adsl.wanadoo.nl [85.145.80.27]) by mag.ik.nu (Postfix) with ESMTP id 12A79A1046; Sat, 9 Jun 2007 17:08:07 +0200 (CEST) Message-ID: <466AC23B.4040601@edwinm.ik.nu> Date: Sat, 09 Jun 2007 17:07:39 +0200 From: Edwin Mons User-Agent: Thunderbird 2.0.0.0 (Windows/20070326) MIME-Version: 1.0 To: bug-followup@FreeBSD.org, Edwin Mons , freebsd-hackers@freebsd.org References: <466A6DF1.3020306@edwinm.ik.nu> <20070609103848.GA1465@ted.stsp.lan> In-Reply-To: <20070609103848.GA1465@ted.stsp.lan> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 09 Jun 2007 16:37:39 +0000 Cc: Subject: Re: kern/83807: [sis] [patch] if_sis: Wake On Lan 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, 09 Jun 2007 15:38:38 -0000 Stefan Sperling wrote: > On Sat, Jun 09, 2007 at 11:08:01AM +0200, Edwin Mons wrote: > >> Will this feature ever be incorporated in mainstream FreeBSD? I'm eagerly >> waiting for it to land in -CURRENT... >> > > I have no idea. > > I haven't got much feedback on this patch, apart from one > or two people who sent me a quick thank you note :) > > So I have no idea how many people are actually using the patch. > > I know that: > > * if_sis and if_vr wake on lan support is very stable for me. > I've been using this code for nearly 2 years now. > > * if_nve support has afaik never been tested (plus > it's a binary blob driver and will apparently be > replaced with OpenBSD's nfe driver soon.) > > I run a single 6.2 box here that I maintain the patch for. > I'd be happy to setup a -current box to port the patch to -CURRENT. > I currently have one -CURRENT machine, and several 6.2-STABLE machines. For at least two of them (the -CURRENT and an x86 -STABLE machine) I'd really like to have WoL support, as these are my workstation and a home server, both of them really do not need to be on all the time, but I want to be able to reach them when I need a file from them when I'm elsewhere. > I'd also be happy to add WOL support for more chipsets. > Adding support is relatively easy as long as another open source > OS (e.g. Linux) supports wake on lan for a chipset and even easier > if a good datasheet is available (as in case of if_sis). > I usually use either if_em or if_xl chipsets, so I hoped landing this code in at least -CURRENT (should go there first, I guess) would result in more chipsets supported ;) > If anyone has a card that does wake on lan after shutdown from Linux > but not after shutdown from FreeBSD with my patch applied let me know. > You may need to use the ethtool utility to enable WOL on Linux. > I don't run Linux on either machine. Perhaps I could do some tests on my workstation with a CD-based linux distribution. Edwin From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 19:52:51 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8368F16A400; Sat, 9 Jun 2007 19:52:51 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.184]) by mx1.freebsd.org (Postfix) with ESMTP id 686CD13C45B; Sat, 9 Jun 2007 19:52:51 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) by smtpout.mac.com (Xserve/smtpout14/MantshX 4.0) with ESMTP id l59JqmuF001204; Sat, 9 Jun 2007 12:52:49 -0700 (PDT) Received: from [172.16.1.3] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id l59JqjTm016589 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Jun 2007 12:52:47 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4AB3C4C0-0DA1-482F-A4CD-375A53332F29@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Sat, 9 Jun 2007 12:52:35 -0700 To: Ivan Voras X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org Subject: Re: GPT - (last) call for action 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, 09 Jun 2007 19:52:51 -0000 On Jun 9, 2007, at 9:22 AM, Ivan Voras wrote: > Another thing that would be nice to have is support for fdisk and > disklabel partitions inside geom_part, so it's management utility > can be > used for both GPT and old style partition management (instead of > currently used two tools: fdisk and disklabel). I do have to make FreeBSD/ia64 boot on a rx2660, but after that I may be able to take a look at it. I know what's there and I know what's missing, so I should be able to get the partitioning stuff working soon-ish. The bootblock requirements may take little longer, because there's where g_part is missing features. Keep me in the loop. FYI, -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 20:17:48 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 69CC116A468; Sat, 9 Jun 2007 20:17:48 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.174]) by mx1.freebsd.org (Postfix) with ESMTP id 5120013C46E; Sat, 9 Jun 2007 20:17:48 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) by smtpout.mac.com (Xserve/smtpout04/MantshX 4.0) with ESMTP id l59KHkvR011320; Sat, 9 Jun 2007 13:17:46 -0700 (PDT) Received: from [172.16.1.3] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id l59KHi2W026793 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Jun 2007 13:17:44 -0700 (PDT) In-Reply-To: References: <4AB3C4C0-0DA1-482F-A4CD-375A53332F29@mac.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4D7CDA24-48FE-4319-A320-C8D7165E9EBC@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Sat, 9 Jun 2007 13:17:34 -0700 To: Ivan Voras X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, freebsd-geom@freebsd.org Subject: Re: GPT - (last) call for action 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, 09 Jun 2007 20:17:48 -0000 On Jun 9, 2007, at 1:04 PM, Ivan Voras wrote: > Marcel Moolenaar wrote: >> >> On Jun 9, 2007, at 9:22 AM, Ivan Voras wrote: >> >>> Another thing that would be nice to have is support for fdisk and >>> disklabel partitions inside geom_part, so it's management utility >>> can be >>> used for both GPT and old style partition management (instead of >>> currently used two tools: fdisk and disklabel). >> >> I do have to make FreeBSD/ia64 boot on a rx2660, but after that I may >> be able to take a look at it. I know what's there and I know what's >> missing, so I should be able to get the partitioning stuff working > > Thanks! > >> soon-ish. The bootblock requirements may take little longer, because >> there's where g_part is missing features. > > Do you mean installing boot blocks into the "protective MBR" via > geom_part or something else? Yep. Both MBR and BSD have boot code and we need to be able to install it through the GEOM ctlreq I/F. It's not a big problem per se, but it's something that needs to be implemented. I'm thinking of a new verb (say "install") that takes one or more blobs of code that the scheme knows how to handle. The boot code is installed after the partitioning scheme has been created on the disk... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 21:43:05 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6D2C16A421; Sat, 9 Jun 2007 21:43:05 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5509113C45A; Sat, 9 Jun 2007 21:43:05 +0000 (UTC) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.8/8.13.7) with ESMTP id l59LSjcA027672; Sat, 9 Jun 2007 14:28:45 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.13.8/8.13.4/Submit) id l59LSjRs027671; Sat, 9 Jun 2007 14:28:45 -0700 (PDT) Date: Sat, 9 Jun 2007 14:28:45 -0700 (PDT) From: Matthew Dillon Message-Id: <200706092128.l59LSjRs027671@apollo.backplane.com> To: Marcel Moolenaar References: <4AB3C4C0-0DA1-482F-A4CD-375A53332F29@mac.com> <4D7CDA24-48FE-4319-A320-C8D7165E9EBC@mac.com> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Ivan Voras , freebsd-geom@freebsd.org Subject: Re: GPT - (last) call for action 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, 09 Jun 2007 21:43:05 -0000 I'm having to tackle this issue right now in DFly. With GPT having to start at sector 1 (no choice there), the compatible MBR in sector 0 presumably must have a slice (#1) which covers the entire disk. But do we have to make slice #1 bootable? Could we also create a slice #2 in the MBR that points into the GPT's first partition, mark it bootable, and thus be able to put boot1 in the GPT's first partition? Or will the BIOS fart on the overlapping MBR slices? -Matt From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 22:43:13 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C046E16A468; Sat, 9 Jun 2007 22:43:13 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.186]) by mx1.freebsd.org (Postfix) with ESMTP id A46C113C48C; Sat, 9 Jun 2007 22:43:13 +0000 (UTC) (envelope-from xcllnt@mac.com) Received: from mac.com (smtpin02-en2 [10.13.10.147]) by smtpout.mac.com (Xserve/smtpout16/MantshX 4.0) with ESMTP id l59MhAq8027718; Sat, 9 Jun 2007 15:43:10 -0700 (PDT) Received: from [172.16.1.3] (209-128-86-226.bayarea.net [209.128.86.226]) (authenticated bits=0) by mac.com (Xserve/smtpin02/MantshX 4.0) with ESMTP id l59Mh8db022070 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 9 Jun 2007 15:43:09 -0700 (PDT) In-Reply-To: <200706092128.l59LSjRs027671@apollo.backplane.com> References: <4AB3C4C0-0DA1-482F-A4CD-375A53332F29@mac.com> <4D7CDA24-48FE-4319-A320-C8D7165E9EBC@mac.com> <200706092128.l59LSjRs027671@apollo.backplane.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <57F8CCC1-1841-41AE-9F82-0C87FE53BE99@mac.com> Content-Transfer-Encoding: 7bit From: Marcel Moolenaar Date: Sat, 9 Jun 2007 15:42:58 -0700 To: Matthew Dillon X-Mailer: Apple Mail (2.752.3) X-Brightmail-Tracker: AAAAAA== X-Brightmail-scanned: yes Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Ivan Voras , freebsd-geom@freebsd.org Subject: Re: GPT - (last) call for action 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, 09 Jun 2007 22:43:13 -0000 On Jun 9, 2007, at 2:28 PM, Matthew Dillon wrote: > I'm having to tackle this issue right now in DFly. With GPT > having to > start at sector 1 (no choice there), the compatible MBR in > sector 0 > presumably must have a slice (#1) which covers the entire disk. > > But do we have to make slice #1 bootable? Could we also create a > slice #2 in the MBR that points into the GPT's first partition, > mark > it bootable, and thus be able to put boot1 in the GPT's first > partition? > Or will the BIOS fart on the overlapping MBR slices? Technically speaking, the MBR can only have a single partition of type 0xEE that covers the whole disk. This is to protect the GPT from MBR-specific tools that do not know about the GPT. This is not a bootable slice by definition. Practice is different. To support bootcamp on Intel-based Macs, the MBR will have real partitions that mirror GPT partitions or otherwise describe partitions outside the GPT controlled area. These can be bootable partitions and the protective partition (the one with type 0xEE) will not cover the whole disk anymore. The nasty part is keeping MBR and GPT partitions in sync, so it may be better to have the MBR partition fall outside the GPT controlled area. This can be done because the GPT header contains the LBA of the first and last sectors on the disk that can be assigned to a partition. You can free up space for MBR partitions after the primary GPT table by adjusting the first LBA. In the MBR partition you can put a GPT aware boot loader that uses the GPT to find the real partitions... -- Marcel Moolenaar xcllnt@mac.com From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 22:49:12 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6954216A400 for ; Sat, 9 Jun 2007 22:49:12 +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 E6D3013C469 for ; Sat, 9 Jun 2007 22:49:11 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Hx9gw-0001ih-P2 for freebsd-hackers@freebsd.org; Sun, 10 Jun 2007 00:45:55 +0200 Received: from 78-1-71-165.adsl.net.t-com.hr ([78.1.71.165]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Jun 2007 00:45:54 +0200 Received: from ivoras by 78-1-71-165.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Jun 2007 00:45:54 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Sun, 10 Jun 2007 00:41:31 +0200 Lines: 56 Message-ID: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig97E7BF4F0A87352BF8777670" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-71-165.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) X-Enigmail-Version: 0.94.3.0 Sender: news Cc: freebsd-fs@freebsd.org Subject: file(1) cannot detect UFS2? 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, 09 Jun 2007 22:49:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig97E7BF4F0A87352BF8777670 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi! I'm trying to use file(1) to detect file system type on partitions, and so far it's working for any file system I've cared to try (the usual MS and Linux list) *except* UFS2. Detecting UFS1 works, though much more verbosely than it needs to be, but UFS2 isn't detected at all. I'd like to ask someone familiar with UFS2 to take a quick peak and add the appropriate rules to the file(1) magic database, if anyone's interest= ed. At the very least, I need someone to commit this patch: --- magic.old Fri Jun 8 17:42:01 2007 +++ magic Fri Jun 8 17:51:11 2007 @@ -4821,6 +4821,10 @@ >8320 belong 0 TIME optimization >8320 belong 1 SPACE optimization +66908 lelong 0x19540119 Unix Fast File system v2 (little-endian) + +66908 belong 0x19540119 Unix Fast File system v2 (big-endian) + # ext2/ext3 filesystems - Andreas Dilger 0x438 leshort 0xEF53 Linux >0x44c lelong x rev %d I don't know if it's correct (the offset seems a bit high...), but it works for me :) --------------enig97E7BF4F0A87352BF8777670 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGayybldnAQVacBcgRAvEKAJ9oQlUi3M883/uRWnnnhlbakoOaXQCfVA/N JyYva7TU7A7im+UizooO5eM= =iHEb -----END PGP SIGNATURE----- --------------enig97E7BF4F0A87352BF8777670-- From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 9 22:53:59 2007 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F78A16A400 for ; Sat, 9 Jun 2007 22:53:59 +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 C98B413C43E for ; Sat, 9 Jun 2007 22:53:58 +0000 (UTC) (envelope-from freebsd-hackers@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Hx9oa-0003TU-SQ for freebsd-hackers@freebsd.org; Sun, 10 Jun 2007 00:53:48 +0200 Received: from 78-1-71-165.adsl.net.t-com.hr ([78.1.71.165]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Jun 2007 00:53:48 +0200 Received: from ivoras by 78-1-71-165.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 10 Jun 2007 00:53:48 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hackers@freebsd.org From: Ivan Voras Date: Sun, 10 Jun 2007 00:53:34 +0200 Lines: 49 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF276B4088E67CD3BBEBF4E5F" X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-71-165.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.12 (Windows/20070509) In-Reply-To: X-Enigmail-Version: 0.94.3.0 Sender: news Cc: freebsd-fs@freebsd.org Subject: Re: file(1) cannot detect UFS2? 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, 09 Jun 2007 22:53:59 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF276B4088E67CD3BBEBF4E5F Content-Type: multipart/mixed; boundary="------------060402060207020002040909" This is a multi-part message in MIME format. --------------060402060207020002040909 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ivan Voras wrote: > At the very least, I need someone to commit this patch: I've attached a better, unmangled patch :) --------------060402060207020002040909 Content-Type: text/plain; name="magic.diff.txt" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="magic.diff.txt" LS0tIG1hZ2ljLm9sZAlGcmkgSnVuICA4IDE3OjQyOjAxIDIwMDcNCisrKyBtYWdpYwlGcmkg SnVuICA4IDE4OjAzOjI3IDIwMDcNCkBAIC00ODIxLDYgKzQ4MjEsMTIgQEANCiA+ODMyMAli ZWxvbmcJCTAJCVRJTUUgb3B0aW1pemF0aW9uDQogPjgzMjAJYmVsb25nCQkxCQlTUEFDRSBv cHRpbWl6YXRpb24NCiANCisjIFVGUzIgLyBsZQ0KKzY2OTA4CWxlbG9uZwkJMHgxOTU0MDEx OQlVbml4IEZhc3QgRmlsZSBzeXN0ZW0gdjIgKGxpdHRsZS1lbmRpYW4pDQorDQorIyBVRlMy IC8gYmUNCis2NjkwOAliZWxvbmcJCTB4MTk1NDAxMTkJVW5peCBGYXN0IEZpbGUgc3lzdGVt IHYyIChiaWctZW5kaWFuKQ0KKw0KICMgZXh0Mi9leHQzIGZpbGVzeXN0ZW1zIC0gQW5kcmVh cyBEaWxnZXIgPGFkaWxnZXJAdHVyYm9sYWJzLmNvbT4NCiAweDQzOAlsZXNob3J0CQkweEVG NTMJCUxpbnV4DQogPjB4NDRjCWxlbG9uZwkJeAkJcmV2ICVkDQo= --------------060402060207020002040909-- --------------enigF276B4088E67CD3BBEBF4E5F 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.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGay9uldnAQVacBcgRAqbSAJwL31GHNy1m+V0YLqu3ZFMve8I4uQCgyVZi vaq4ROqRw78q5qHZH+GWQxg= =5/kC -----END PGP SIGNATURE----- --------------enigF276B4088E67CD3BBEBF4E5F--