From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 01:40:27 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6058516A41F; Sun, 4 Dec 2005 01:40:26 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43924917.3070506@freebsd.org> Date: Sun, 04 Dec 2005 09:40:39 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Evans References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 01:40:27 -0000 Jason Evans wrote: > On Dec 3, 2005, at 12:26 AM, David Xu wrote: > >> I have a question about mutex used in the patch, you are using >> a spin loop, isn't it suboptimal ? and a thread library like libpthread >> supports static priority scheduling, this mutex does not work, it >> will causes a dead lock, if a lower priority thread locked the mutex, >> and preempted by a higher priority thread, and the higher priority >> thread also calls malloc, it will spin there to wait lower >> priority thread to complete, but that will never happen. > > > David, > > You are correct that this is a problem. Thank you for pointing it > out. There's a new patch that uses the spinlocks that are provided > by the threads libraries. Please let me know if this looks okay. > > Also, this patch removes/modifies the code that was causing build > failures on amd64, so it's worth giving another try. Hopefully, it > will compile now... > > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051203a.diff > > Thanks, > Jason > The libc spinlocks are deprecated, in fact, thread libraries try to keep track off all spinlocks in libc and reset them in child process, they will complain if there are too many spinlocks, this is not very correct, but would resolve dead lock in real world applications (weird applications). Because I see you have put _malloc_prefork() and _malloc_postfork() hooks in thread libraries, I guess you want to manage all malloc locks, so you might don't need to use the spinlocks, you can implement these locks by using umtx provided by kernel, you can use UMTX_OP_WAIT and UMTX_OP_WAKE to implement these locks, the UMTX_OP_LOCK and UMTX_OP_UNLOCK can also be used to implement locks, but I reserve these two functions since I have plan to implement reliable POSIX process shared mutex. you can find those code in libthr to study how to use umtx. Last, I don't know if umtx will work with libc_r, but libc_r has already been disconneted from world for some days, it will rot away. Regards, David Xu From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 01:46:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A1DAD16A41F; Sun, 4 Dec 2005 01:46:16 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E48E43D6A; Sun, 4 Dec 2005 01:46:13 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jB41kBGY009309; Sat, 3 Dec 2005 20:46:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB41kB5v027569; Sat, 3 Dec 2005 20:46:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A59957302F; Sat, 3 Dec 2005 20:46:11 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051204014611.A59957302F@freebsd-current.sentex.ca> Date: Sat, 3 Dec 2005 20:46:11 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 01:46:16 -0000 TB --- 2005-12-04 00:30:15 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-04 00:30:15 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2005-12-04 00:30:15 - cleaning the object tree TB --- 2005-12-04 00:30:36 - checking out the source tree TB --- 2005-12-04 00:30:36 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2005-12-04 00:30:36 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-04 00:36:53 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-04 00:36:53 - cd /src TB --- 2005-12-04 00:36:53 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-04 01:41:40 - generating LINT kernel config TB --- 2005-12-04 01:41:40 - cd /src/sys/sparc64/conf TB --- 2005-12-04 01:41:40 - /usr/bin/make -B LINT TB --- 2005-12-04 01:41:41 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-04 01:41:41 - cd /src TB --- 2005-12-04 01:41:41 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Dec 4 01:41:41 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/cm/smc90cx6.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/cnw/if_cnw.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/cs/if_cs.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/cs/if_cs_isa.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/cs/if_cs_pccard.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/dev/dc/if_dc.c /src/sys/dev/dc/if_dc.c: In function `dc_attach': /src/sys/dev/dc/if_dc.c:2077: warning: passing arg 2 of `OF_getetheraddr' from incompatible pointer type *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-04 01:46:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-04 01:46:11 - ERROR: failed to build lint kernel TB --- 2005-12-04 01:46:11 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 02:11:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A785016A41F for ; Sun, 4 Dec 2005 02:11:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 266A143D45 for ; Sun, 4 Dec 2005 02:11:13 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 2910 invoked by uid 399); 4 Dec 2005 02:11:07 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 4 Dec 2005 02:11:07 -0000 Message-ID: <43925039.3060305@FreeBSD.org> Date: Sat, 03 Dec 2005 18:11:05 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: Nicolas Blais References: <200512031609.48962.nb_root@videotron.ca> In-Reply-To: <200512031609.48962.nb_root@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, asa@agava.com Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 02:11:13 -0000 Nicolas Blais wrote: > After a cvsup/buildworld today, sshd (and cupsd, reported in PR ports/89892) > will no longer start at boot on my system. There was a problem with the cups.sh startup script that is only apparent relative to the new rcorder stuff in HEAD. The cups.sh script has the PROVIDE label in it for NetBSD's purposes, but from our standpoint, it's still an "old style" startup script. Since the new code in HEAD looks for this label, it was trying to treat the script in the new way, and that caused the boot to fail. I just committed the the simplest possible fix, removing that line from the startup script. If the maintainer (cc'ed) has a better idea, that's not a problem, but since I use cups as well, I knew this was going to be a problem, and I wanted to make sure this didn't bite any more people than absolutely necessary. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 02:52:48 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CE42216A41F; Sun, 4 Dec 2005 02:52:47 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <43925A0D.8070906@freebsd.org> Date: Sun, 04 Dec 2005 10:53:01 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@freebsd.org> <43924917.3070506@freebsd.org> In-Reply-To: <43924917.3070506@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jason Evans , current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 02:52:48 -0000 Here is sample code to implement a mutex by using umtx syscalls: #include #include #include #include #include #include #include #define LCK_UNLOCKED 0 #define LCK_LOCKED 1 #define LCK_CONTENDED 2 void lock_mtx(struct umtx *mtx) { volatile uintptr_t *m = (volatile uintptr_t *)mtx; for (;;) { /* try to lock it. */ if (atomic_cmpset_acq_ptr(m, LCK_UNLOCKED, LCK_LOCKED)) return; if (atomic_load_acq_ptr(m) == LCK_LOCKED) { /* * if it was locked by single thread, try to * set it to contented state. */ if (!atomic_cmpset_acq_ptr(m, LCK_LOCKED, LCK_CONTENDED)) continue; } /* if in contented state, wait it to be unlocked. */ if (atomic_load_acq_ptr(m) == LCK_CONTENDED) _umtx_op((struct umtx *)m, UMTX_OP_WAIT, LCK_CONTENDED, 0, NULL); } } void unlock_mtx(struct umtx *mtx) { volatile uintptr_t *m = (volatile uintptr_t *)mtx; for (;;) { if (atomic_load_acq_ptr(m) == LCK_UNLOCKED) err(1, "unlock a unlocked mutex\n"); if (atomic_load_acq_ptr(m) == LCK_LOCKED) { if (atomic_cmpset_acq_ptr(m, LCK_LOCKED, LCK_UNLOCKED)) return; } if (atomic_load_acq_ptr(m) == LCK_CONTENDED) { atomic_store_rel_ptr(m, LCK_UNLOCKED); _umtx_op((struct umtx *)m, UMTX_OP_WAKE, 1, NULL, NULL); break; } } } struct umtx m; void * lock_test(void *arg) { int i = 0; for (i = 0; i < 10000; ++i) { lock_mtx(&m); pthread_yield(); unlock_mtx(&m); } return (0); } int main() { pthread_t td1, td2; pthread_create(&td1, NULL, lock_test, NULL); pthread_create(&td2, NULL, lock_test, NULL); pthread_join(td1, NULL); pthread_join(td2, NULL); return (0); } From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 03:34:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E05EB16A420; Sun, 4 Dec 2005 03:34:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9ADCD43D53; Sun, 4 Dec 2005 03:34:16 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB43YEI7049088; Sun, 4 Dec 2005 03:34:15 GMT (envelope-from davidxu@freebsd.org) Message-ID: <439263BA.1090404@freebsd.org> Date: Sun, 04 Dec 2005 11:34:18 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@freebsd.org> <43924917.3070506@freebsd.org> <43925A0D.8070906@freebsd.org> In-Reply-To: <43925A0D.8070906@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Jason Evans , current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 03:34:17 -0000 David Xu wrote: > Here is sample code to implement a mutex by using umtx syscalls: > ... > void > unlock_mtx(struct umtx *mtx) > { > volatile uintptr_t *m = (volatile uintptr_t *)mtx; > > for (;;) { > if (atomic_load_acq_ptr(m) == LCK_UNLOCKED) > err(1, "unlock a unlocked mutex\n"); > if (atomic_load_acq_ptr(m) == LCK_LOCKED) { > if (atomic_cmpset_acq_ptr(m, LCK_LOCKED, LCK_UNLOCKED)) > return; > } > if (atomic_load_acq_ptr(m) == LCK_CONTENDED) { > atomic_store_rel_ptr(m, LCK_UNLOCKED); > _umtx_op((struct umtx *)m, UMTX_OP_WAKE, 1, NULL, NULL); OOP, should be: _umtx_op((struct umtx *)m, UMTX_OP_WAKE, INT_MAX, NULL, NULL); This line is not very optimal if there are lots of thread waiting there. :-) There is optimal version using transaction id: http://www.dragonflybsd.org/cvsweb/src/lib/libthread_xu/thread/thr_umtx.c?rev=1.2&content-type=text/x-cvsweb-markup Though, libthr in freebsd does not use these semantices, instead they are implemented in kernel. David Xu From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 03:47:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB63216A41F; Sun, 4 Dec 2005 03:47:24 +0000 (GMT) (envelope-from jasone@canonware.com) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0AD443D81; Sun, 4 Dec 2005 03:47:18 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id 5A8695E48D1; Sat, 3 Dec 2005 19:47:18 -0800 (PST) Received: from [192.168.168.203] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id ABDDE5E4885; Sat, 3 Dec 2005 19:47:16 -0800 (PST) In-Reply-To: <43924917.3070506@freebsd.org> References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@freebsd.org> <43924917.3070506@freebsd.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Jason Evans Date: Sat, 3 Dec 2005 19:46:01 -0800 To: David Xu X-Mailer: Apple Mail (2.746.2) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 03:47:24 -0000 On Dec 3, 2005, at 5:40 PM, David Xu wrote: > The libc spinlocks are deprecated, in fact, thread libraries try to > keep track > off all spinlocks in libc and reset them in child process, they > will complain > if there are too many spinlocks, this is not very correct, but > would resolve > dead lock in real world applications (weird applications). > Because I see you have put _malloc_prefork() and _malloc_postfork() > hooks in thread libraries, I guess you want to manage all malloc > locks, so > you might don't need to use the spinlocks, you can implement these > locks by using umtx provided by kernel, you can use UMTX_OP_WAIT > and UMTX_OP_WAKE to implement these locks, the UMTX_OP_LOCK > and UMTX_OP_UNLOCK can also be used to implement locks, but I reserve > these two functions since I have plan to implement reliable POSIX > process > shared mutex. you can find those code in libthr to study how to > use umtx. > Last, I don't know if umtx will work with libc_r, but libc_r has > already been > disconneted from world for some days, it will rot away. I just need simple (low overhead) mutexes that don't cause malloc to be called during their initialization. I would have used pthread_mutex_* directly, but cannot due to infinite recursion problems during initialization. As you pointed out, it's important to get priority inheritance right in order to avoid priority inversion deadlock, so my hand-rolled spinlocks weren't adequate. I need mutexes that are managed by the threads library. The libc spinlocks appear to fit the bill perfectly in that capacity. It seems to me that using umtx would actually be the wrong thing to do, because I'd be circumventing libpthread's userland scheduler, and it would be the wrong thing for libc_r, as you pointed out. This approach would work for libthr, but perhaps nothing else? I'd like to keep things as simple and general as possible. Is the current implementation that uses libc spinlocks acceptable? Thanks, Jason P.S. Why are libc spinlocks deprecated? From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 09:54:51 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 795C016A420 for ; Sun, 4 Dec 2005 09:54:51 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3AA643D55; Sun, 4 Dec 2005 09:54:50 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB49smjX005495; Sun, 4 Dec 2005 09:54:50 GMT (envelope-from davidxu@freebsd.org) Message-ID: <4392BCED.3070500@freebsd.org> Date: Sun, 04 Dec 2005 17:54:53 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jason Evans References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@freebsd.org> <43924917.3070506@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 09:54:51 -0000 Jason Evans wrote: > I just need simple (low overhead) mutexes that don't cause malloc to be > called during their initialization. umtx is light weight and fast and need not malloc. > I would have used pthread_mutex_* > directly, but cannot due to infinite recursion problems during > initialization. > Yes, I know current pthread_mutex implementations use malloc, I don't think it will be changed to avoid using malloc very soon. > As you pointed out, it's important to get priority inheritance right in > order to avoid priority inversion deadlock, so my hand-rolled spinlocks > weren't adequate. I need mutexes that are managed by the threads > library. The libc spinlocks appear to fit the bill perfectly in that > capacity. It seems to me that using umtx would actually be the wrong > thing to do, because I'd be circumventing libpthread's userland > scheduler, and it would be the wrong thing for libc_r, as you pointed > out. This approach would work for libthr, but perhaps nothing else? > umtx will work with libpthread, I can not find any reason why using umtx will cause deadlock, the userland scheduler can not propagate its priority decision cross kernel, and umtx is a blockable syscall. > I'd like to keep things as simple and general as possible. Is the > current implementation that uses libc spinlocks acceptable? > > Thanks, > Jason > > P.S. Why are libc spinlocks deprecated? > > Because we want other libraries use pthread mutex, if it can not be used widely and we have to use spinlock, it is really a bad taste. I think only the malloc has recursive problem. I tell you the fact, libpthread needs malloc to initialize spinlock, so you can not create spinlock dynamically in your malloc code. only libthr does not have the problem. libc_r also has priority inversion problem with your current mutex code. Regards, David Xu From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 12:52:22 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C20BA16A41F for ; Sun, 4 Dec 2005 12:52:22 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6DA543D8E for ; Sun, 4 Dec 2005 12:51:41 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by wproxy.gmail.com with SMTP id i34so428887wra for ; Sun, 04 Dec 2005 04:51:40 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bgCvEoS4FEBjdKzz7kFR3A1JoCl06+nbTzkOSMPK5sWbDmqvGiYENXzCAPYCXCis7ij/ahtEc698y74rHhzCpYZ09co1DVpVRnJ+8S9oUWKYEEITbczxhJ/Lr7son/upX/ooSpGM46PsYDP8dS7Zwu6ri3VzOURYKwM8fqGfbY0= Received: by 10.64.150.8 with SMTP id x8mr2261981qbd; Sun, 04 Dec 2005 04:51:39 -0800 (PST) Received: by 10.65.192.14 with HTTP; Sun, 4 Dec 2005 04:51:39 -0800 (PST) Message-ID: Date: Sun, 4 Dec 2005 13:51:39 +0100 From: Claus Guttesen To: Jason Evans In-Reply-To: <7318D807-9086-4817-A40B-50D6960880FB@canonware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <7318D807-9086-4817-A40B-50D6960880FB@canonware.com> Cc: current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 12:52:23 -0000 > Did you use the 20051202b patch? I thought I had fixed the problem, > but I don't have an amd64 system to test on. In any case, I'll be > uploading up a new patch in a few minutes that removes the offending > code entirely. I was able to do a buildworld on current with this patch, but I had problems getting X to run and kldxref took all my space on the root-partition doing a installkernel. So I downgraded to 6.0 stable and get this error: =3D=3D=3D> libexec/atrun (all) cc -O2 -fno-strict-aliasing -pipe -march=3Dathlon64 -DATJOB_DIR=3D\"/var/at/jobs/\" -DLFILE=3D\"/var/at/jobs/.lockfile\"=20 -DLOADAVG_MX=3D1.5 -DATSPOOL_DIR=3D\"/var/at/spool\" -DVERSION=3D\"2.9\" -DDAEMON_UID=3D1 -DDAEMON_GID=3D1 -DDEFAULT_BATCH_QUEUE=3D\'E\'=20 -DDEFAULT_AT_QUEUE=3D\'c\' -DPERM_PATH=3D\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun -c /usr/src/libexec/atrun/atrun.c cc -O2 -fno-strict-aliasing -pipe -march=3Dathlon64 -DATJOB_DIR=3D\"/var/at/jobs/\" -DLFILE=3D\"/var/at/jobs/.lockfile\"=20 -DLOADAVG_MX=3D1.5 -DATSPOOL_DIR=3D\"/var/at/spool\" -DVERSION=3D\"2.9\" -DDAEMON_UID=3D1 -DDAEMON_GID=3D1 -DDEFAULT_BATCH_QUEUE=3D\'E\'=20 -DDEFAULT_AT_QUEUE=3D\'c\' -DPERM_PATH=3D\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun -c /usr/src/libexec/atrun/gloadavg.c cc -O2 -fno-strict-aliasing -pipe -march=3Dathlon64 -DATJOB_DIR=3D\"/var/at/jobs/\" -DLFILE=3D\"/var/at/jobs/.lockfile\"=20 -DLOADAVG_MX=3D1.5 -DATSPOOL_DIR=3D\"/var/at/spool\" -DVERSION=3D\"2.9\" -DDAEMON_UID=3D1 -DDAEMON_GID=3D1 -DDEFAULT_BATCH_QUEUE=3D\'E\'=20 -DDEFAULT_AT_QUEUE=3D\'c\' -DPERM_PATH=3D\"/var/at/\" -I/usr/src/libexec/atrun/../../usr.bin/at -I/usr/src/libexec/atrun =20 -o atrun atrun.o gloadavg.o /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `calloc' /usr/obj/usr/src/tmp/usr/lib/libc.so: undefined reference to `posix_memalig= n' *** Error code 1 Stop in /usr/src/libexec/atrun. *** Error code 1 Stop in /usr/src/libexec. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. make buildworld 1122,93s user 217,28s system 84% cpu 26:18,72 total twin/usr/src#>uname -a FreeBSD twin.gnome.no 6.0-STABLE FreeBSD 6.0-STABLE #0: Sun Dec 4 01:18:58 CET 2005 root@twin.gnome.no:/usr/obj/usr/src/sys/TWIN=20 amd64 regards Claus From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 14:29:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B826616A41F; Sun, 4 Dec 2005 14:29:45 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53EE543D5A; Sun, 4 Dec 2005 14:29:45 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.ntplx.net (8.13.5/8.13.5/NETPLEX) with ESMTP id jB4ETbOW001128; Sun, 4 Dec 2005 09:29:37 -0500 (EST) Date: Sun, 4 Dec 2005 09:29:37 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: David Xu In-Reply-To: <4392BCED.3070500@freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) Cc: Jason Evans , current@freebsd.org Subject: Re: New libc malloc patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 14:29:45 -0000 On Sun, 4 Dec 2005, David Xu wrote: > Jason Evans wrote: > > I just need simple (low overhead) mutexes that don't cause malloc to be > > called during their initialization. > umtx is light weight and fast and need not malloc. > > > I would have used pthread_mutex_* > > directly, but cannot due to infinite recursion problems during > > initialization. > > > Yes, I know current pthread_mutex implementations use malloc, > I don't think it will be changed to avoid using malloc very soon. It's on my list of things to do. > > As you pointed out, it's important to get priority inheritance right in > > order to avoid priority inversion deadlock, so my hand-rolled spinlocks > > weren't adequate. I need mutexes that are managed by the threads > > library. The libc spinlocks appear to fit the bill perfectly in that > > capacity. It seems to me that using umtx would actually be the wrong > > thing to do, because I'd be circumventing libpthread's userland > > scheduler, and it would be the wrong thing for libc_r, as you pointed > > out. This approach would work for libthr, but perhaps nothing else? > > > umtx will work with libpthread, I can not find any reason why using umtx > will cause deadlock, the userland scheduler can not propagate its > priority decision cross kernel, and umtx is a blockable syscall. The problem is userland code can exit, circumvent the unlock by exception handling, take a signal and longjmp, etc., which may leave locks (not known by libpthread) held. At least with spinlocks or mutex, the thread libraries can know that the application is in a critical region and can behave accordingly. Libpthread will defer switching threads when they are in critical regions (unless they are blocked). I think that libc or other libraries that want to be thread-safe shouldn't try to roll their own locks. The reason to do so is that lock overhead may be deemed too great. If that is the case, then we should fix the problem at its source ;-) Of course, the other reason is that mutexes currently have to be allocated. -- DE From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 15:22:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CD6116A41F for ; Sun, 4 Dec 2005 15:22:37 +0000 (GMT) (envelope-from martin.mato@wanadoo.fr) Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAB7E43D76 for ; Sun, 4 Dec 2005 15:22:36 +0000 (GMT) (envelope-from martin.mato@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0907.wanadoo.fr (SMTP Server) with ESMTP id 8DA361C0011C for ; Sun, 4 Dec 2005 16:22:35 +0100 (CET) Received: from pcgyver.dyndns.org (AMontpellier-252-1-20-232.w83-197.abo.wanadoo.fr [83.197.152.232]) by mwinf0907.wanadoo.fr (SMTP Server) with ESMTP id 5C6CE1C00118 for ; Sun, 4 Dec 2005 16:22:35 +0100 (CET) X-ME-UUID: 20051204152235378.5C6CE1C00118@mwinf0907.wanadoo.fr Received: from [192.168.0.2] (hayes.humanidyne.net [192.168.0.2]) by pcgyver.dyndns.org (8.13.4/8.13.4) with ESMTP id jB4FMW8F000806 for ; Sun, 4 Dec 2005 16:22:33 +0100 (CET) (envelope-from martin.mato@wanadoo.fr) Message-ID: <439309BA.3030800@wanadoo.fr> Date: Sun, 04 Dec 2005 16:22:34 +0100 From: Martin MATO User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: fr, en MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200512031609.48962.nb_root@videotron.ca> <43925039.3060305@FreeBSD.org> In-Reply-To: <43925039.3060305@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: isc-dhcpdserver (was Re: [rc update] sshd no longer starts at boot) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: martin.mato@wanadoo.fr List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 15:22:37 -0000 Doug Barton a écrit : >Nicolas Blais wrote: > > >>After a cvsup/buildworld today, sshd (and cupsd, reported in PR ports/89892) >>will no longer start at boot on my system. >> >> > >There was a problem with the cups.sh startup script that is only apparent >relative to the new rcorder stuff in HEAD. The cups.sh script has the >PROVIDE label in it for NetBSD's purposes, but from our standpoint, it's >still an "old style" startup script. Since the new code in HEAD looks for >this label, it was trying to treat the script in the new way, and that >caused the boot to fail. > >I just committed the the simplest possible fix, removing that line from the >startup script. If the maintainer (cc'ed) has a better idea, that's not a >problem, but since I use cups as well, I knew this was going to be a >problem, and I wanted to make sure this didn't bite any more people than >absolutely necessary. > >Doug > > > I announce that the built-in sendmail and the isc-dhcp3-server-3.0.3 port also fails at boot for sendmail, only the local mqueue is running, sendmail is not accepting connections from the outside... Removing the PROVIDE Label in the scripts solve the problem for isc-dhcpd only.... best regards. Martin MATO From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 16:35:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5D3016A41F for ; Sun, 4 Dec 2005 16:35:40 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6CA1243D53 for ; Sun, 4 Dec 2005 16:35:40 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR004.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IQZ00D9ZFFFNM40@VL-MO-MR004.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 04 Dec 2005 11:35:39 -0500 (EST) Date: Sun, 04 Dec 2005 11:35:33 -0500 From: Nicolas Blais In-reply-to: <200512031609.48962.nb_root@videotron.ca> To: freebsd-current@freebsd.org Message-id: <200512041135.39342.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart2239218.57TcFBcjQ3; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200512031609.48962.nb_root@videotron.ca> User-Agent: KMail/1.8.3 Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 16:35:40 -0000 --nextPart2239218.57TcFBcjQ3 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On December 3, 2005 04:09 pm, Nicolas Blais wrote: > After a cvsup/buildworld today, sshd (and cupsd, reported in PR > ports/89892) will no longer start at boot on my system. > sshd_enable=3D"YES" is still present in my /etc/rc.conf and yet it does n= ot > start, nor does it seem like it even tried as there are no error messages: > > Starting rpcbind. > ELF ldconfig > path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib / > usr/local/lib/compat/pkg > a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/ao= ut > Starting mountd. > Starting nfsd. > Starting apache2. > Usage: cups {reload|restart|start|status|stop} > Starting SAMBA: removing stale tdbs : > /var/db/samba/connections.tdb > /var/db/samba/locking.tdb > /var/db/samba/messages.tdb > /var/db/samba/sessionid.tdb > /var/db/samba/brlock.tdb > Starting nmbd. > Starting smbd. > Starting local daemons:. > > Yet: > [nicblais@clk01a] /home/nicblais# sshd > sshd re-exec requires execution with an absolute path > > ok so: > [nicblais@clk01a] /home/nicblais# /etc/rc.d/sshd start > Starting sshd. > > Nicolas. /usr/sbin/cron also doesn't start @ boot anymore :( Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #3: Sat Dec 3 12:39:04 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart2239218.57TcFBcjQ3 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDkxrb4wTBlvcsbJURAlzGAKConmmUmSFIWbd7McoVwB7wZTOoxgCePK3Q 9Cj785DXvfpPobnV0mPdAms= =WbcO -----END PGP SIGNATURE----- --nextPart2239218.57TcFBcjQ3-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 17:17:46 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 13A9916A41F; Sun, 4 Dec 2005 17:17:46 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 932A343D49; Sun, 4 Dec 2005 17:17:45 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jB4HFUJG004606; Sun, 4 Dec 2005 10:15:30 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sun, 04 Dec 2005 10:16:12 -0700 (MST) Message-Id: <20051204.101612.130709753.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: <20051203110534.N98873@fledge.watson.org> References: <20051203110534.N98873@fledge.watson.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Sun, 04 Dec 2005 10:15:30 -0700 (MST) Cc: current@freebsd.org Subject: Re: Brief Report: IBM/Lenovo z60t notebook with FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:17:46 -0000 In message: <20051203110534.N98873@fledge.watson.org> Robert Watson writes: : At the end of the day, I have most things working with this notebook : except for the following: : : - The Ricoh SD card reader is unsupported. Google suggests that Linux : also doesn't support it, and that although there's a reverse engineering : effort going on, it has made limited progress. They're looking for : volunteers if anyone is interested in learning about reverse : engineering. The Ricoh SD card reader uses the SD Standard Host Interface, as do the TI chipsets. Sadly, the SD Standard Host Interface version 1.0 (and all other) documents are available only under extreme NDA. There's been a few 'leaks' in the interface via different data sheets and such (I snagged my copies while I could). The SD consortium does this to protect the DRM functions they added over MMC. However, the real reason many think they do this is to assure their revenue stream. The MMC/SD card reader also needs a mmc bus driver as well. I'll be working on one for a port to an embedded part I'm doing for work, since we'll likely be storing our configuration data on a MMC part... Generally finding data on the 'standard host interface' for the SD, MMC, MemoryStick or SmartMedia adapters is an excersize in frustration. :-( Warner From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 17:30:52 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8995C16A41F for ; Sun, 4 Dec 2005 17:30:52 +0000 (GMT) (envelope-from ke.han@redstarling.com) Received: from smtp102.biz.mail.mud.yahoo.com (smtp102.biz.mail.mud.yahoo.com [68.142.200.237]) by mx1.FreeBSD.org (Postfix) with SMTP id F18EC43D6A for ; Sun, 4 Dec 2005 17:30:51 +0000 (GMT) (envelope-from ke.han@redstarling.com) Received: (qmail 38217 invoked from network); 4 Dec 2005 17:30:51 -0000 Received: from unknown (HELO ?192.168.1.2?) (jhancock@patternware.com@218.79.199.193 with plain) by smtp102.biz.mail.mud.yahoo.com with SMTP; 4 Dec 2005 17:30:51 -0000 Message-ID: <439327CA.6040104@redstarling.com> Date: Mon, 05 Dec 2005 01:30:50 +0800 From: "ke.han" User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <43906ED8.5060209@redstarling.com> In-Reply-To: <43906ED8.5060209@redstarling.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: Tyan i7520 mobo problems on FreeBSD 6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:30:52 -0000 Solution found !!! For the tyan i7520 mobo, you must go to the boot loader prompt and type set hint.apic.0.disabled="1". This clears up the issues. ke.han wrote: > Dear list, > I have been continuing efforts to get the Tyan i7520 mobo to work with > freeBSD 6. Here are some of the problems. I have tried the things > suggested by others like turning on/off Hyperthreading...no luck. > > If I can't find a solution by Monday, I will be forced to pull this mobo > and buy another. This is costly, but not compared to the time and face > I've lost over the past month. Centos 4.2 installs/works perfect. So > this is a problem between freeBSD 6 installer and the mobo, not the mobo > itself. freeBSD 5.4 gives my similar problems. > > Here are a few of the problems with freeBSD 6 and the tyan i7520: > > 1 - Floppy not found. I was able to fix this by turning off the onboard > SATA. > 2 - EIDE or SATA drive connected directly to respective mobo controller > not found. I'm not an expert at hints, but I tried a few things and no > luck. > 3 - 3Ware 9550sx card not found. With the latest not-released 9.3.0.2 > driver called twa_9ksx.ko, I was able to get the module loaded during > sysinstall and the card was usable and the install completed. After > reboot, I entered boot prompt and reloaded the same module and boot but > this time the card does not work. Another sided effect of loading this > module in sysinstall is that after it is loaded, the installer tells me > it can't find my cdrom to complete the install...yes, the same cdrom I > have booted the installer with. But an ftp install from this point worked. > > So, I would like any suggestions as to fixing item 3 above or find a > suitable mobo to replace. If I end up replacing the mobo I am happy to > gift the tyan i7520 to a team member that wants to debug with it. > > My mobo requirements are straightforward: > > 1 - Ethernet - two ports, great throughput with _no patches_ for all the > freeBSD 6 advance networking features: pf, altq, kqueue, polling. I > just want it work right "out of the box". > 2 - works with my 3ware 9550sx-4lp card. > 3 - It would be very nice if the sysinstall recognized my cd and floppy > with no hints or any other tricks. > > thanks, ke han > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 17:54:01 2005 Return-Path: X-Original-To: current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BF81D16A428 for ; Sun, 4 Dec 2005 17:54:01 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [128.30.28.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ECC843D8D for ; Sun, 4 Dec 2005 17:53:41 +0000 (GMT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (localhost.csail.mit.edu [127.0.0.1]) by khavrinen.csail.mit.edu (8.13.1/8.13.4) with ESMTP id jB4HrN8E045333 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK CN=khavrinen.csail.mit.edu issuer=Client+20CA); Sun, 4 Dec 2005 12:53:23 -0500 (EST) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.13.1/8.13.4/Submit) id jB4HrM0D045330; Sun, 4 Dec 2005 12:53:22 -0500 (EST) (envelope-from wollman) From: Garrett Wollman MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17299.11538.560643.715262@khavrinen.csail.mit.edu> Date: Sun, 4 Dec 2005 12:53:22 -0500 To: "Poul-Henning Kamp" In-Reply-To: <23153.1130423266@critter.freebsd.dk> References: <20051027140031.L32255@fledge.watson.org> <23153.1130423266@critter.freebsd.dk> X-Mailer: VM 7.17 under 21.4 (patch 17) "Jumbo Shrimp" XEmacs Lucid X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-1.6 (khavrinen.csail.mit.edu [127.0.0.1]); Sun, 04 Dec 2005 12:53:23 -0500 (EST) X-Spam-Status: No, score=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on khavrinen.csail.mit.edu Cc: current@FreeBSD.ORG Subject: Re: MySQL Performance 6.0rc1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:54:02 -0000 [Picking up a thread from more than a month ago...] < said: > * Additional CLOCK_FOO values for various degraded but fast > timestamps. > Unfortunately, they either force intense versioning of libc or > application source-code changes, so neither is very desirable. This option is not as bad as it sounds. For applications which use clock_gettime() et al it's a trivial change that can easily be hidden behind a preprocessor macro (and probably should be anyway, since most of those applications really want to use something like CLOCK_MONOTONIC iff it's available). I wouldn't be averse to downgrading gettimeofday(). >> Sadly, POSIX doesn't say anything about how applications can express >> preferences about the cost and granularity of time measurement. > Yes, in addition to their other defficiencies [1] the APIs are > somewhat limited in what they can express. I've tried to get the Austin Group interested in improving the clock APIs as a work item. No such luck, but it can't hurt to try some more. What would help greatly would be an actual implementation (e.g., new clock_xxx() functions and CLOCK_xxx constants) and some (even simple) applications that can take advantage of it. These are within the implementation namespace so there door is wide open in that respect. > I've often thought about inventing a new API to solve these problems, > it doesn't take much to do it right, but I have never carried through > on it because adding yet another "FreeBSD-propriety" API is not the > solution we're looking for. All APIs start out that way; the POSIX people have learned (by doing) that committee invention is a bad thing, and are rightfully reluctant to add new interfaces unless they are proven workable by prior implementation. -GAWollman From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 17:59:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4854816A41F for ; Sun, 4 Dec 2005 17:59:27 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from ms-smtp-02.rdc-nyc.rr.com (ms-smtp-02-smtplb.rdc-nyc.rr.com [24.29.109.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id B334643D4C for ; Sun, 4 Dec 2005 17:59:26 +0000 (GMT) (envelope-from scottro@scottro.net) Received: from mail.scottro.net (cpe-68-175-68-211.nyc.res.rr.com [68.175.68.211]) by ms-smtp-02.rdc-nyc.rr.com (8.12.10/8.12.7) with ESMTP id jB4HtkGe010062 for ; Sun, 4 Dec 2005 12:55:47 -0500 (EST) Received: by mail.scottro.net (Postfix, from userid 1001) id 6D1BD40EC; Sun, 4 Dec 2005 12:40:32 -0500 (EST) Date: Sun, 4 Dec 2005 12:40:32 -0500 From: Scott Robbins To: freebsd-current@freebsd.org Message-ID: <20051204174032.GA1304@mail.scottro.net> Mail-Followup-To: freebsd-current@freebsd.org References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed Content-Disposition: inline In-Reply-To: <200512041135.39342.nb_root@videotron.ca> User-Agent: mutt-ng/devel-r581 (FreeBSD) X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 17:59:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, Dec 04, 2005 at 11:35:33AM -0500, Nicolas Blais wrote: > On December 3, 2005 04:09 pm, Nicolas Blais wrote: > > After a cvsup/buildworld today, sshd (and cupsd, reported in PR > > ports/89892) will no longer start at boot on my system. > > sshd_enable="YES" is still present in my /etc/rc.conf and yet it does not > > start, nor does it seem like it even tried as there are no error messages: > > I'm finding sshd, cron, cups (there was a fix and an update which I did for the port but it didn't help) aren't starting. Postfix, which I was starting, following the instructions in pkg_info, which basically have you put "YES" for sendmail and no for a few other sendmail things, also doesn't start. I worked around that one by using the second method in its pkg_info, marking sendmail="NO" and symlinking /usr/local/sbin/postfix to /usr/local/etc/rc.d/postfix.sh pf, jails, and ntpd work. With cron, pgrep crond gives a result, but there's no /var/run/cron.pid (and cronjobs don't run) until it's manually started. - -- Scott Robbins PGP keyID EB3467D6 ( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 ) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: Generally speaking, when scary things get scared, not good. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkyoQ+lTVdes0Z9YRAjxKAKDAqoIi9QYDQePBvmJljwGzj1UAhQCgsD5+ AweC6irY/bjXqWWJ2RqO+xU= =Vpf1 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 18:04:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E607916A422 for ; Sun, 4 Dec 2005 18:04:06 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id A81B043D6E for ; Sun, 4 Dec 2005 18:03:51 +0000 (GMT) (envelope-from nb_root@videotron.ca) Received: from clk01a ([66.130.198.54]) by VL-MO-MR003.ip.videotron.ca (Sun Java System Messaging Server 6.2-2.05 (built Apr 28 2005)) with ESMTP id <0IQZ00DFTJIAQFE0@VL-MO-MR003.ip.videotron.ca> for freebsd-current@freebsd.org; Sun, 04 Dec 2005 13:03:46 -0500 (EST) Date: Sun, 04 Dec 2005 13:03:41 -0500 From: Nicolas Blais In-reply-to: <20051204174032.GA1304@mail.scottro.net> To: freebsd-current@freebsd.org Message-id: <200512041303.45970.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1977231.TLSL9xAJUb; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> User-Agent: KMail/1.8.3 Cc: Scott Robbins Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 18:04:07 -0000 --nextPart1977231.TLSL9xAJUb Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline > I'm finding sshd, cron, cups (there was a fix and an update > which I did for the port but it didn't help) aren't starting. Postfix, > which I was starting, following the instructions in pkg_info, which > basically have you put "YES" for sendmail and no for a few other > sendmail things, also doesn't start. I worked around that one by > using the second method in its pkg_info, marking sendmail=3D"NO" and > symlinking /usr/local/sbin/postfix to /usr/local/etc/rc.d/postfix.sh > =46or cupds, after you did the update, did you rm /usr/local/etc/rc.d/cups.= sh=20 and cp /usr/local/etc/rc.d/cups.sh.sample /usr/local/etc/rc.d/cups.sh ? It was cups.sh.sample that was 'touched'. Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #3: Sat Dec 3 12:39:04 EST 2005 =20 root@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1977231.TLSL9xAJUb Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDky+B4wTBlvcsbJURAl9YAJ9Ze2g/ynbXEKwb5UAEhtC9swYO5wCgld1S Qw3H9rHU7FYNiY3PeTFY9lk= =evxB -----END PGP SIGNATURE----- --nextPart1977231.TLSL9xAJUb-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 18:15:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04EAA16A41F for ; Sun, 4 Dec 2005 18:15:20 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 69E1443D4C for ; Sun, 4 Dec 2005 18:15:19 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 44819 invoked by uid 399); 4 Dec 2005 18:15:11 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 4 Dec 2005 18:15:11 -0000 Message-ID: <43933227.4050906@FreeBSD.org> Date: Sun, 04 Dec 2005 10:15:03 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: Nicolas Blais References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> In-Reply-To: <200512041303.45970.nb_root@videotron.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Scott Robbins Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 18:15:20 -0000 Nicolas Blais wrote: > For cupds, after you did the update, did you rm /usr/local/etc/rc.d/cups.sh > and cp /usr/local/etc/rc.d/cups.sh.sample /usr/local/etc/rc.d/cups.sh ? A more effective long term solution to that problem is to do: cd /usr/local/etc/rc.d rm cups.sh ln -s cups.sh.sample cups.sh Also, you can test the effectiveness of the solution by removing the line with the word PROVIDE on it from the cups.sh[.sample] script, which is all the update to the port does. Of course, it's possible that some OTHER script from another port is also causing a problem. If after you do the cups update you still have a problem, send me all the scripts you have in /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d, I will be glad to take a look. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 18:30:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2F3116A41F; Sun, 4 Dec 2005 18:30:09 +0000 (GMT) (envelope-from null@pozo.com) Received: from pozo.com (pozo.com [216.101.162.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 78C2A43D64; Sun, 4 Dec 2005 18:30:08 +0000 (GMT) (envelope-from null@pozo.com) Received: from sunpci.pozo.com (sunpci.pozo.com [192.168.0.29]) (authenticated bits=0) by pozo.com (8.13.4/8.13.4) with ESMTP id jB4IU5Ss072122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 4 Dec 2005 10:30:06 -0800 (PST) (envelope-from null@pozo.com) Message-Id: <7.0.0.16.2.20051204102647.037622d8@pozo.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.16 Date: Sun, 04 Dec 2005 10:30:05 -0800 To: Doug Barton , Nicolas Blais From: Manfred Antar In-Reply-To: <43933227.4050906@FreeBSD.org> References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: freebsd-current@freebsd.org, Scott Robbins Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 18:30:09 -0000 At 10:15 AM 12/4/2005, Doug Barton wrote: >Nicolas Blais wrote: > >>For cupds, after you did the update, did you rm /usr/local/etc/rc.d/cups.sh and cp /usr/local/etc/rc.d/cups.sh.sample /usr/local/etc/rc.d/cups.sh ? > >A more effective long term solution to that problem is to do: > >cd /usr/local/etc/rc.d >rm cups.sh >ln -s cups.sh.sample cups.sh > >Also, you can test the effectiveness of the solution by removing the line with the word PROVIDE on it from the cups.sh[.sample] script, which is all the update to the port does. > >Of course, it's possible that some OTHER script from another port is also causing a problem. If after you do the cups update you still have a problem, send me all the scripts you have in /usr/local/etc/rc.d and /usr/X11R6/etc/rc.d, I will be glad to take a look. > >hth, >Doug There are other scripts that cause this. I just did a portupgrade of portupgrade and it installs a script called 000.pkgtools.sh after rebooting no ssh sendmail or cron. Here is the script: #!/bin/sh # # $Id: pkgtools.sh 1047 2004-12-25 15:35:21Z knu $ # PROVIDE: pkgtools # REQUIRE: ldconfig # KEYWORD: FreeBSD . /etc/rc.subr name=pkgtools start_cmd=pkgtools_start stop_cmd=: [ -z "$pkgtools_libdir" ] && pkgtools_libdir="/usr/local/lib/compat/pkg" pkgtools_start() { if [ -d "$pkgtools_libdir" ]; then /sbin/ldconfig -m "$pkgtools_libdir" fi } load_rc_config $name run_rc_command "$1" ================================== || null@pozo.com || || Ph. (415) 681-6235 || ================================== From owner-freebsd-current@FreeBSD.ORG Sun Dec 4 19:01:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE9A016A41F for ; Sun, 4 Dec 2005 19:01:19 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id E26D743D5D for ; Sun, 4 Dec 2005 19:01:18 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 84120 invoked by uid 399); 4 Dec 2005 19:01:17 -0000 Received: from localhost (HELO ?192.168.1.101?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 4 Dec 2005 19:01:17 -0000 Message-ID: <43933CFB.8060908@FreeBSD.org> Date: Sun, 04 Dec 2005 11:01:15 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: Manfred Antar References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <7.0.0.16.2.20051204102647.037622d8@pozo.com> In-Reply-To: <7.0.0.16.2.20051204102647.037622d8@pozo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Scott Robbins , Nicolas Blais Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Dec 2005 19:01:19 -0000 Manfred Antar wrote: > There are other scripts that cause this. > I just did a portupgrade of portupgrade and it installs a script called 000.pkgtools.sh > after rebooting no ssh sendmail or cron. I just added isc-dhcpd and this pkgtools script to my /usr/local/etc/rc.d, and booted just fine, so I strongly suspect that there is some other problem here. Can you add rc_debug="yes" to your /etc/rc.conf file, boot again, and let me know what you see? You might try setting up syslog to log your console output first ... uncomment that line in /etc/syslog.conf and 'touch /var/log/console.log' before booting. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 00:55:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9BFB816A41F for ; Mon, 5 Dec 2005 00:55:05 +0000 (GMT) (envelope-from bofh@terranova.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35ADA43D45 for ; Mon, 5 Dec 2005 00:55:04 +0000 (GMT) (envelope-from bofh@terranova.net) Received: by tog.net (Postfix, from userid 96) id 2CED429B6A3; Sun, 4 Dec 2005 19:55:04 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.0-terranovanet_v6 (2005-09-13) on spamsmacker.terranova.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=7.1 tests=ALL_TRUSTED,FM_MULTI_ODD2 autolearn=failed version=3.1.0-terranovanet_v6 Received: from [192.168.5.103] (host-216-89-228-162.wireless.terranova.net [216.89.228.162]) by tog.net (Postfix) with ESMTP id B838829B655 for ; Sun, 4 Dec 2005 19:55:01 -0500 (EST) Message-ID: <43938F61.1050202@terranova.net> Date: Sun, 04 Dec 2005 19:52:49 -0500 From: Travis Mikalson Organization: TerraNovaNet Internet Services User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: make.conf options you cannot use for building CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 00:55:05 -0000 Hi, I'm just mentioning make.conf options that you cannot currently use for building CURRENT that work for RELENG_6. I'm using make.conf to avoid building a lot of things I don't need in order to create a very stripped-down basic base system. I hope this if of interest to somebody. NO_LIBPTHREAD=yes ===> usr.sbin/powerd (all) cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c /usr/src/usr.sbin/powerd/powerd.c cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -lpthread -o powerd powerd.o -lutil /usr/cfobj/usr/src/tmp/usr/bin/ld: cannot find -lpthread *** Error code 1 Stop in /usr/src/usr.sbin/powerd. *** Error code 1 Stop in /usr/src/usr.sbin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. NO_TOOLCHAIN=yes ===> gnu/lib/csu (depend,all,install) make -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/csu/../../../contrib/gcc tconfig.h echo '#ifndef GCC_TCONFIG_H' > tconfig.h echo '#define GCC_TCONFIG_H' >> tconfig.h echo '#ifdef IN_GCC' >> tconfig.h echo '# include "ansidecl.h"' >> tconfig.h echo '#endif' >> tconfig.h echo '#define USED_FOR_TARGET' >> tconfig.h echo '#endif /* GCC_TCONFIG_H */' >> tconfig.h make -f /usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile MFILE=/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools/Makefile GCCDIR=/usr/src/gnu/lib/csu/../../../contrib/gcc tm.h echo '#ifndef GCC_TM_H' > tm.h echo '#define GCC_TM_H' >> tm.h echo '#ifdef IN_GCC' >> tm.h echo '#include "i386/i386.h"' >> tm.h echo '#include "i386/unix.h"' >> tm.h echo '#include "i386/att.h"' >> tm.h echo '#include "dbxelf.h"' >> tm.h echo '#include "elfos.h"' >> tm.h echo '#include "freebsd-native.h"' >> tm.h echo '#include "freebsd-spec.h"' >> tm.h echo '#include "freebsd.h"' >> tm.h echo '#include "i386/freebsd.h"' >> tm.h echo '#include "defaults.h"' >> tm.h echo '#if !defined GENERATOR_FILE && !defined USED_FOR_TARGET' >> tm.h echo '# include "insn-constants.h"' >> tm.h echo '# include "insn-flags.h"' >> tm.h echo '#endif' >> tm.h echo '#endif' >> tm.h echo '#define EXTRA_MODES_FILE "i386/i386-modes.def"' >> tm.h echo '#endif /* GCC_TM_H */' >> tm.h rm -f .depend mkdep -f .depend -a -DCRT_BEGIN -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -I/usr/src/gnu/lib/csu/../../../contrib/gcc/config -I/usr/src/gnu/lib/csu/../../../contrib/gcc -I. -I/usr/src/gnu/lib/csu/../../usr.bin/cc/cc_tools /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c In file included from /usr/src/gnu/lib/csu/../../../contrib/gcc/crtstuff.c:62: /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:44:20: stddef.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:45:19: float.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:76:20: stdarg.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:79:19: stdio.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:85:19: errno.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:92:20: string.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:93:20: stdlib.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:94:20: unistd.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:97:20: limits.h: No such file or directory /usr/src/gnu/lib/csu/../../../contrib/gcc/tsystem.h:100:18: time.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/lib/csu. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Last but not least, things that I use that work: NO_ACPI=yes NO_ATM=yes NO_BLUETOOTH=yes NO_CVS=yes NO_CXX=yes NO_DICT=yes NO_FORTRAN=yes NO_GAMES=yes NO_GDB=yes NO_GPIB=yes NO_I4B=yes NO_INET6=yes NO_INFO=yes NO_IPFILTER=yes NO_KERBEROS=yes NO_LIBC_R=yes NO_LIBTHR=yes NO_LPR=yes NO_MAN=yes NO_MODULES=yes NO_NETCAT=yes NO_NIS=yes NO_OBJC=yes NO_PROFILE=yes NO_RCMDS=yes NO_SENDMAIL=yes NO_SHARE=yes NO_SHAREDOCS=yes NO_USB=yes NO_NLS=yes -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 x101 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Life's not fair, but the root password helps. From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 04:41:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6177316A41F; Mon, 5 Dec 2005 04:41:12 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 027A243D45; Mon, 5 Dec 2005 04:41:11 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.13.4/8.13.4) with ESMTP id jB54egdW043707; Sun, 4 Dec 2005 20:40:42 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.13.4/8.13.4/Submit) id jB54eghJ043706; Sun, 4 Dec 2005 20:40:42 -0800 (PST) Date: Sun, 4 Dec 2005 20:40:42 -0800 (PST) From: Matthew Dillon Message-Id: <200512050440.jB54eghJ043706@apollo.backplane.com> To: obrien@freebsd.org References: <20050926152952.GA1670@dragon.NUXI.org> <20050926160808.GB1649@dragon.NUXI.org> <20050926180615.GA61075@xor.obsecurity.org> <20051004172532.GA49048@dragon.NUXI.org> Cc: freebsd-current@freebsd.org, Kris Kennaway Subject: Re: [PANIC] ufs_dirbad: bad dir X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 04:41:12 -0000 I just had a thought on the dirbad panics (which we are also getting occassionally). These are the symptoms I see: * Seems to be related to softupdates * In all the panics I've seen, what I have *NOT* seen has been any panics related to bitmap corruption. I added a lot of extra checks in both the bitmap allocation and free code and not one of them has been hit. * I have not seen any vm_page corruption. e.g. no ref count panics. * The dirbad panics occurs infrequently, implying a narrow window where it occucrs. * The dirbad panics seem to be related to extraction of a tar, or filesystem synchronization. If we assume the file extension is not the problem (unless reallocblks or fragextend is the problem), then it could be related to truncation. * In all core dumps I've seen from DragonFly systems exhibiting the failure, the directory block in question has universally appeared to contain data from a fail. In the last dump I looked at the first 1K of an 8K directory block (well beyond the direct block array in the inode) contained data from a file while the remaining 7K had directory data in it. There are two scenarios that I can think of that can have these effects yet not trigger any of the bitmap corruption tests/panics. (1) If ffs_blkfree() is called on a block who's related buffer still exists and is or might become dirty, then a totally UNRELATED vnode can immediately reallocate the physical block and issue its own I/O operation. So we wind up with two buffer cache buffers with different vnodes and lblkno's but the same blkno, at least temporarily. The condition would only need to hold long enough for the writes to be ordered the wrong way and poof, the new vnode winds up with someone else's data in it. (2) If getblk() is called on (blkdev, blkno) (which softupdates does) and this somehow survives (vp, lblkno) and gets written back after the bitmap related to (vp, lblkno) has been freed, the data might now be owned by a different vnode and we'd be corrupting another vnode's data. The question is... can such a scenario occur anywhere in the UFS code? In particular with softupdates enabled? I did see one possible issue, and that is the fact that softdep_setup_freeblocks() is called BEFORE vinvalbuf() in ffs_truncate(). If softdeps somehow is able to execute *ANY* of those workitems before the vinvalbuf runs, in particular if there is already I/O in progress on any of those buffers (and thus doesn't get invalidated by vinvalbuf until after the I/O is complete), then that could result in the above scenario. The case occurs in several situations but the main one that DragonFly and FreeBSD shares is when a file is truncated to 0-length. -Matt From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 07:15:38 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 55BA616A41F for ; Mon, 5 Dec 2005 07:15:38 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id B851243D5C for ; Mon, 5 Dec 2005 07:15:37 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 88929 invoked by uid 399); 5 Dec 2005 07:15:34 -0000 Received: from localhost (HELO ?192.168.0.5?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 5 Dec 2005 07:15:34 -0000 Message-ID: <4393E915.8020302@FreeBSD.org> Date: Sun, 04 Dec 2005 23:15:33 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051203) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <7.0.0.16.2.20051204102647.037622d8@pozo.com> <43933CFB.8060908@FreeBSD.org> In-Reply-To: <43933CFB.8060908@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Scott Robbins , Nicolas Blais Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 07:15:38 -0000 Thanks to debugging help from Manfred and Scott, I've decided to give up on trying to figure out what's wrong with the ports scripts. :) Seriously though, Brooks and I have had a conversation about whether the *.sh scripts generally need to be sourced into the shell at all, or can they be run like "regular" rc.d scripts. The problems with the fairly simple stuff that Scott and Manfred had installed (i.e., completely non-obvious, and no good reason for it to fail) convinced me that we need to go this route, at least in the short term. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 08:11:02 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 45B2716A41F for ; Mon, 5 Dec 2005 08:11:02 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE81943D5A for ; Mon, 5 Dec 2005 08:11:01 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 042C01A9DD; Mon, 5 Dec 2005 09:10:59 +0100 (CET) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19085-04; Mon, 5 Dec 2005 09:10:57 +0100 (CET) Received: from [192.168.0.94] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id D0C221A9DC; Mon, 5 Dec 2005 09:10:57 +0100 (CET) Message-ID: <4393F60E.2040106@shapeshifter.se> Date: Mon, 05 Dec 2005 09:10:54 +0100 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Travis Mikalson References: <43938F61.1050202@terranova.net> In-Reply-To: <43938F61.1050202@terranova.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: current@freebsd.org Subject: Re: make.conf options you cannot use for building CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 08:11:02 -0000 Travis Mikalson wrote: > Hi, > > I'm just mentioning make.conf options that you cannot currently use for > building CURRENT that work for RELENG_6. I'm using make.conf to avoid > building a lot of things I don't need in order to create a very > stripped-down basic base system. > > I hope this if of interest to somebody. > > NO_LIBPTHREAD=yes > > ===> usr.sbin/powerd (all) > cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -c > /usr/src/usr.sbin/powerd/powerd.c > cc -O2 -fno-strict-aliasing -pipe -Wsystem-headers -Werror -Wall > -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wunused-parameter > -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -lpthread > -o powerd powerd.o -lutil > /usr/cfobj/usr/src/tmp/usr/bin/ld: cannot find -lpthread > *** Error code 1 > > Stop in /usr/src/usr.sbin/powerd. > *** Error code 1 > > Stop in /usr/src/usr.sbin. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > I introduced powerd to pthreads so this is most likely my fault. I'll post a patch as soon as possible, unless somebody else comes up with a patch faster than me :) Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 08:11:22 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7D6216A427; Mon, 5 Dec 2005 08:11:22 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id C02EA43D5E; Mon, 5 Dec 2005 08:11:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id jB58BFSc066832; Mon, 5 Dec 2005 00:11:16 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id jB58BFfh066831; Mon, 5 Dec 2005 00:11:15 -0800 (PST) (envelope-from obrien) Date: Mon, 5 Dec 2005 00:11:15 -0800 From: "David O'Brien" To: John Baldwin Message-ID: <20051205081115.GB61813@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, John Baldwin , freebsd-current@freebsd.org, "Matthew D. Fuller" , Brian Candler References: <20051201095426.GD17378@uk.tiscali.com> <438F2BFD.9030408@mac.com> <20051201202842.GP39831@over-yonder.net> <200512011621.24287.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200512011621.24287.jhb@freebsd.org> X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Cc: freebsd-current@freebsd.org, "Matthew D. Fuller" , Brian Candler Subject: Re: freebsd-current@ and freebsd-current@ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 08:11:22 -0000 On Thu, Dec 01, 2005 at 04:21:21PM -0500, John Baldwin wrote: > On Thursday 01 December 2005 03:28 pm, Matthew D. Fuller wrote: > > On Thu, Dec 01, 2005 at 11:59:41AM -0500 I heard the voice of > > > > Chuck Swiger, and lo! it spake thus: > > > I've asked postmaster@ about this, and there are mechanisms in place > > > which are supposed to merge the two names to avoid duplicate > > > postings, but some messages seem to get missed. > > > > Interestingly enough, there seems to be a pattern to it. All the > > places where somebody starts duplicating happen when somebody (a) is > > using KMail, and (b) replies to a message to 'current@' (never to > > freebsd-current@), it will set the To: to freebsd-current@, and leave > > current@ in the CC list. I've begged the FreeBSD postmaster and admins to add a script to make all the mailing list addresses canonical. Until then, I've added .procmailrc rules to my own mail handling to do it. Maybe Kmail users should do the same. ..snip.. > Yes, KMail parses the List-XXX headers that mailman sticks in messages to > figure out that when you reply to a list message it should use the list post > address for To:. Unfortunately, there is now way to turn this "feature" off > and when I submitted a bug report about it to KDE asking for the feature to > be toggleable the KMail developers basically told me to piss off. Maybe an enterprising KDE user could whip up a toggle patch that we could at least commit as a patch to the port. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 08:55:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E856916A41F for ; Mon, 5 Dec 2005 08:55:58 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FE4A43D4C for ; Mon, 5 Dec 2005 08:55:58 +0000 (GMT) (envelope-from kbuild@gmail.com) Received: by zproxy.gmail.com with SMTP id l8so1050196nzf for ; Mon, 05 Dec 2005 00:55:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=KxLU7eUd8xWyetqirUo6iYJybqdArLzTre9MKOzMmAR30StcbkKFD4DAoxzVJbpChm6CS+6IP4dKcjqayfKnBWMaQIvchoBTRFWInHqEYWEdUPruPesgek2muLjcdYz7BENdUhTB4b+jdQ2IaViQoHF0qeDfR/G/pFTVZStHZl8= Received: by 10.65.103.8 with SMTP id f8mr2529661qbm; Mon, 05 Dec 2005 00:55:57 -0800 (PST) Received: by 10.65.231.2 with HTTP; Mon, 5 Dec 2005 00:55:57 -0800 (PST) Message-ID: Date: Mon, 5 Dec 2005 16:55:57 +0800 From: Sun Le To: freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: I have a question X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 08:55:59 -0000 Hey folks, Can somebody tell me if the current freebsd support the vedio chipset - Intel 82945G?I am blocked here. Many thanks in advance! -Sandy -- Sun Le (Sandy) - Keep it simple,stupid and low-key From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 10:32:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F1EB16A41F for ; Mon, 5 Dec 2005 10:32:32 +0000 (GMT) (envelope-from pete@altadena.net) Received: from puffin.altadena.net (puffin.altadena.net [207.151.161.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8564143D6B for ; Mon, 5 Dec 2005 10:32:31 +0000 (GMT) (envelope-from pete@altadena.net) Received: from nat-gw.home.altadena.net ([66.127.158.99] helo=[192.168.169.21]) by puffin.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1EjDe2-0000cD-8f for current@freebsd.org; Mon, 05 Dec 2005 02:32:30 -0800 Message-ID: <4394173C.40606@altadena.net> Date: Mon, 05 Dec 2005 02:32:28 -0800 From: Peter Carah User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051122) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <7.0.0.16.2.20051204102647.037622d8@pozo.com> <43933CFB.8060908@FreeBSD.org> <4393E915.8020302@FreeBSD.org> In-Reply-To: <4393E915.8020302@FreeBSD.org> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 10:32:32 -0000 Doug Barton wrote: > Thanks to debugging help from Manfred and Scott, I've decided to give up > on trying to figure out what's wrong with the ports scripts. :) > Seriously though, Brooks and I have had a conversation about whether the > *.sh scripts generally need to be sourced into the shell at all, or can > they be run like "regular" rc.d scripts. The problems with the fairly > simple stuff that Scott and Manfred had installed (i.e., completely > non-obvious, and no good reason for it to fail) convinced me that we > need to go this route, at least in the short term. > > Doug > All this from cvsup about 2 or 3 pm pst: My problem is more related to the earlier ones; I hadn't noticed cron (which now looking didn't start), but moused doesn't start, nor sshd. These are *not* in the ports... (and yes, I refreshed all of /etc/rc* and removed old scripts from rc.d...) The problem with cups.sh dropped me into single user, from which if I just ^D all the missing stuff started, including cupsd. Strange... Actually does sound like a script is leaving state around that affects others. -- Pete From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 12:30:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4629316A41F; Mon, 5 Dec 2005 12:30:21 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id B45F243D64; Mon, 5 Dec 2005 12:30:20 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id C8C13E4; Mon, 5 Dec 2005 07:30:41 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 43F10F06; Mon, 5 Dec 2005 07:30:38 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.54 (FreeBSD)) id 1EjFTy-000Ne1-V4; Mon, 05 Dec 2005 12:30:14 +0000 Date: Mon, 5 Dec 2005 12:30:14 +0000 From: Brian Candler To: Doug Barton Message-ID: <20051205123014.GA90877@uk.tiscali.com> References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43933227.4050906@FreeBSD.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Scott Robbins , Nicolas Blais Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 12:30:21 -0000 On Sun, Dec 04, 2005 at 10:15:03AM -0800, Doug Barton wrote: > Nicolas Blais wrote: > > >For cupds, after you did the update, did you rm > >/usr/local/etc/rc.d/cups.sh and cp /usr/local/etc/rc.d/cups.sh.sample > >/usr/local/etc/rc.d/cups.sh ? > > A more effective long term solution to that problem is to do: > > cd /usr/local/etc/rc.d > rm cups.sh > ln -s cups.sh.sample cups.sh I presume that if ports are upgraded so that they honour foo_enable from rc.conf, there is no need for them to install foo.sh.sample any more, and they should just install foo.sh instead? That's unless the port *intends* that the user make changes to the startup script directly (in which case, the symlink option given above isn't really appropriate) Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 14:30:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA94E16A420 for ; Mon, 5 Dec 2005 14:30:30 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from wmptl.net (fw1.wmptl.com [216.8.159.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FA1843D55 for ; Mon, 5 Dec 2005 14:30:30 +0000 (GMT) (envelope-from nvidican@wmptl.com) Received: from [10.0.0.104] (r3140ca.wmptl.net [10.0.0.104]) by wmptl.net (8.13.1/8.13.1) with ESMTP id jB5EUTGY024455; Mon, 5 Dec 2005 09:30:29 -0500 (EST) (envelope-from nvidican@wmptl.com) Message-ID: <43944F05.8080000@wmptl.com> Date: Mon, 05 Dec 2005 09:30:29 -0500 From: Nathan Vidican User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sun Le References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.711 () J_CHICKENPOX_66,RATWR10_MESSID X-Scanned-By: MIMEDefang 2.44 Cc: current@freebsd.org Subject: Re-Post: Does -current support vedio chipset / Intel 82945G? (Was: I have a question) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Sun Le List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 14:30:31 -0000 Sun Le wrote: > Hey folks, > > Can somebody tell me if the current freebsd support the vedio chipset - > Intel 82945G?I am blocked here. > > Many thanks in advance! > -Sandy > > -- > Sun Le (Sandy) - > > Keep it simple,stupid and low-key > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > > Next time, try posting with a more appropriate subject line, most people will ignore or not even read 'i have a question' - that kinda goes without saying, you either email the list because you have a question, or because you have an answer... I 're-posted' your message with this reply using a more appropriate subject line - perhaps someone who knows the answer will give it to you now, I for one am sorry - but do not know/support/use the chipset and do not know how well if at all that it will work with -current branch. -- Nathan Vidican nvidican@wmptl.com Windsor Match Plate & Tool Ltd. http://www.wmptl.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 15:52:37 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31EF316A41F; Mon, 5 Dec 2005 15:52:37 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A23F543D80; Mon, 5 Dec 2005 15:52:30 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jB5FqUX1009104; Mon, 5 Dec 2005 07:52:30 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jB5FqTX5009102; Mon, 5 Dec 2005 07:52:29 -0800 Date: Mon, 5 Dec 2005 07:52:29 -0800 From: Brooks Davis To: Brian Candler Message-ID: <20051205155229.GB7653@odin.ac.hmc.edu> References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <20051205123014.GA90877@uk.tiscali.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="uZ3hkaAS1mZxFaxD" Content-Disposition: inline In-Reply-To: <20051205123014.GA90877@uk.tiscali.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: Doug Barton , Scott Robbins , Nicolas Blais , freebsd-current@freebsd.org Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 15:52:37 -0000 --uZ3hkaAS1mZxFaxD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 05, 2005 at 12:30:14PM +0000, Brian Candler wrote: > On Sun, Dec 04, 2005 at 10:15:03AM -0800, Doug Barton wrote: > > Nicolas Blais wrote: > >=20 > > >For cupds, after you did the update, did you rm=20 > > >/usr/local/etc/rc.d/cups.sh and cp /usr/local/etc/rc.d/cups.sh.sample= =20 > > >/usr/local/etc/rc.d/cups.sh ? > >=20 > > A more effective long term solution to that problem is to do: > >=20 > > cd /usr/local/etc/rc.d > > rm cups.sh > > ln -s cups.sh.sample cups.sh >=20 > I presume that if ports are upgraded so that they honour foo_enable from > rc.conf, there is no need for them to install foo.sh.sample any more, and > they should just install foo.sh instead? >=20 > That's unless the port *intends* that the user make changes to the startup > script directly (in which case, the symlink option given above isn't real= ly > appropriate) PREFIX/etc/rc.d/*.sh.sample should not be installed, no exceptions. If there's a need for sample startup scripts, we should put them somewhere under in ${PREFIX}/share/examples. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --uZ3hkaAS1mZxFaxD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDlGI8XY6L6fI4GtQRAnX+AJ4v01c1PbUPOmp8u4I0YNlYf0dC1gCdFGI0 Uh5IC6s3hPj2xeYi+0draWk= =pLpu -----END PGP SIGNATURE----- --uZ3hkaAS1mZxFaxD-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 16:50:03 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A2D516A41F for ; Mon, 5 Dec 2005 16:50:03 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9850243D6E for ; Mon, 5 Dec 2005 16:50:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id C18AF2082; Mon, 5 Dec 2005 17:49:56 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id A57D82080; Mon, 5 Dec 2005 17:49:56 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 8BC7C33C1D; Mon, 5 Dec 2005 17:49:56 +0100 (CET) To: Fredrik Lindberg References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Mon, 05 Dec 2005 17:49:56 +0100 In-Reply-To: <4393F60E.2040106@shapeshifter.se> (Fredrik Lindberg's message of "Mon, 05 Dec 2005 09:10:54 +0100") Message-ID: <86mzjflc97.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Travis Mikalson , current@freebsd.org Subject: Re: make.conf options you cannot use for building CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 16:50:03 -0000 Fredrik Lindberg writes: > I introduced powerd to pthreads so this is most likely my fault. There is no reason to use threads in powerd. Simply merge the devd_read() loop into your main loop, using select() with a timeout instead of usleep(). --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 17:11:32 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8670216A41F; Mon, 5 Dec 2005 17:11:32 +0000 (GMT) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [194.58.105.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1327143D5F; Mon, 5 Dec 2005 17:11:32 +0000 (GMT) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.44 (FreeBSD)) id 1EjJs3-000Avt-IQ; Mon, 05 Dec 2005 20:11:23 +0300 Date: Mon, 5 Dec 2005 20:11:23 +0300 From: Slawa Olhovchenkov To: Tai-hwa Liang Message-ID: <20051205171122.GB26742@zxy.spb.ru> References: <200511160247.jAG2lC9q024183@repoman.freebsd.org> <1133441247.1213.9.camel@localhost> <05120212092614.10343@www.mmlab.cse.yzu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <05120212092614.10343@www.mmlab.cse.yzu.edu.tw> User-Agent: Mutt/1.5.7i X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Vladimir Grebenschikov , Craig Rodrigues , current , cvs-src@FreeBSD.org Subject: Re: cvs commit: src/contrib/smbfs/mount_smbfs getmntopts.c mntopts.h mount_smbfs.c src/usr.sbin/mount_smbfs Makefile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 17:11:32 -0000 On Fri, Dec 02, 2005 at 12:12:06PM +0800, Tai-hwa Liang wrote: > On Thu, 1 Dec 2005, Vladimir Grebenschikov wrote: > [...] > >This commit broke long names on SMBFS: > > > >/usr/src/usr.sbin/mount_smbfs# > >/usr/obj/usr/src/usr.sbin/mount_smbfs/mount_smbfs -I192.168.1.240 -N > >//mir/public /m/mir > >/usr/src/usr.sbin/mount_smbfs# ls /m/mir/FreeBSD > >DAPZBN~6 PQIGAZ~G.GZ iso packages > [...] > > Does following patch work for you? > > http://people.freebsd.org/~avatar/smbfs_vfsops.c.patch This patch work for me. Please commit it. From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 18:54:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 72DB416A41F for ; Mon, 5 Dec 2005 18:54:30 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E33743D6A for ; Mon, 5 Dec 2005 18:54:22 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3200121 for multiple; Mon, 05 Dec 2005 13:52:28 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5Is6L4040561; Mon, 5 Dec 2005 13:54:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 5 Dec 2005 13:42:27 -0500 User-Agent: KMail/1.8.2 References: <200512031411.50840.mistry.7@osu.edu> In-Reply-To: <200512031411.50840.mistry.7@osu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051342.28489.jhb@freebsd.org> X-Spam-Status: No, score=-1.2 required=4.2 tests=ALL_TRUSTED,BIZ_TLD, SUBJ_HAS_UNIQ_ID autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: Can't boot latest CURRENT snapshot 7-CURRENT-SNAP009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:54:30 -0000 On Saturday 03 December 2005 02:11 pm, Anish Mistry wrote: > Information from the system running 5.4-STABLE-SNAP009: > http://am-productions.biz/docs/kev-amd64-pciconf.txt.gz > http://am-productions.biz/docs/kev-acpidump.txt.gz > http://am-productions.biz/docs/kev-dmesg.txt.gz > > I get the following when trying to boot from the install CD. The same > result occurs whether I disable ACPI or APIC. > GDB: no debug ports present > KDB: debugger backends: ddb > KDB: current backend: ddb > SMAP type=01 base=0000000000000000 len=000000000009f800 > SMAP type=02 base=00000000000f0000 len=0000000000010000 > SMAP type=02 base=00000000fec00000 len=0000000000001000 > SMAP type=02 base=00000000fee00000 len=0000000000100000 > SMAP type=02 base=00000000fefffc00 len=0000000000000400 > SMAP type=02 base=00000000ffff0000 len=0000000000010000 > SMAP type=03 base=000000001fee3000 len=000000000000d000 > SMAP type=04 base=000000001fee0000 len=0000000000003000 > SMAP type=02 base=000000000009f800 len=0000000000000800 > SMAP type=02 base=000000001fef0000 len=0000000000010000 > SMAP type=01 base=0000000000100000 len=000000001fde0000 > Copyright (c) 1992-2005 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 > The Regents of the University of California. All rights > reserved. > FreeBSD 7-CURRENT-SNAP009 #0: Sat Nov 12 01:43:08 UTC 2005 > root@portnoy.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC > WARNING: WITNESS option enabled, expect reduced performance. > Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff80e32000. > Preloaded mfs_root "/boot/mfsroot" at 0xffffffff80e321f8. > ACPI APIC Table: > Calibrating clock(s) ... i8254 clock: 1193256 Hz > CLK_USE_I8254_CALIBRATION not specified - using default frequency > Timecounter "i8254" frequency 1193182 Hz quality 0 > Calibrating TSC clock ... TSC clock: 1808257427 Hz > CPU: AMD Athlon(tm) 64 Processor 2800+ (1808.26-MHz K8-class CPU) > Origin = "AuthenticAMD" Id = 0xf4a Stepping = 10 > > Features=0x78bfbff,CMOV,PAT,PSE36,CLFLUS H,MMX,FXSR,SSE,SSE2> > AMD Features=0xe0500800 > L1 2MB data TLB: 8 entries, fully associative > L1 2MB instruction TLB: 8 entries, fully associative > L1 4KB data TLB: 32 entries, fully associative > L1 4KB instruction TLB: 32 entries, fully associative > L1 data cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way > associative > L1 instruction cache: 64 kbytes, 64 bytes/line, 1 lines/tag, 2-way > associative > L2 2MB unified TLB: 0 entries, disabled/not present > L2 4KB data TLB: 512 entries, 4-way associative > L2 4KB instruction TLB: 512 entries, 4-way associative > L2 unified cache: 512 kbytes, 64 bytes/line, 1 lines/tag, 16-way > associative > usable memory = 520404992 (496 MB) > Physical memory chunk(s): > 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) > 0x0000000000f2f000 - 0x000000001efa7fff, 503812096 bytes (123001 > pages) > avail memory = 500678656 (477 MB) > APIC: CPU 0 has ACPI ID 0 > MADT: Found IO APIC ID 2, Interrupt 0 at 0xfec00000 > ioapic0: Routing external 8259A's -> intpin 0 > ioapic0: intpin 0 -> ExtINT (edge, high) > ioapic0: intpin 1 -> ISA IRQ 1 (edge, high) > ioapic0: intpin 2 -> ISA IRQ 2 (edge, high) > ioapic0: intpin 3 -> ISA IRQ 3 (edge, high) > ioapic0: intpin 4 -> ISA IRQ 4 (edge, high) > ioapic0: intpin 5 -> ISA IRQ 5 (edge, high) > ioapic0: intpin 6 -> ISA IRQ 6 (edge, high) > ioapic0: intpin 7 -> ISA IRQ 7 (edge, high) > ioapic0: intpin 8 -> ISA IRQ 8 (edge, high) > ioapic0: intpin 9 -> ISA IRQ 9 (edge, high) > ioapic0: intpin 10 -> ISA IRQ 10 (edge, high) > ioapic0: intpin 11 -> ISA IRQ 11 (edge, high) > ioapic0: intpin 12 -> ISA IRQ 12 (edge, high) > ioapic0: intpin 13 -> ISA IRQ 13 (edge, high) > ioapic0: intpin 14 -> ISA IRQ 14 (edge, high) > ioapic0: intpin 15 -> ISA IRQ 15 (edge, high) > ioapic0: intpin 16 -> PCI IRQ 16 (level, low) > ioapic0: intpin 17 -> PCI IRQ 17 (level, low) > ioapic0: intpin 18 -> PCI IRQ 18 (level, low) > ioapic0: intpin 19 -> PCI IRQ 19 (level, low) > ioapic0: intpin 20 -> PCI IRQ 20 (level, low) > ioapic0: intpin 21 -> PCI IRQ 21 (level, low) > ioapic0: intpin 22 -> PCI IRQ 22 (level, low) > ioapic0: intpin 23 -> PCI IRQ 23 (level, low) > MADT: Interrupt override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > ioapic0: intpin 2 trigger: edge > ioapic0: intpin 2 polarity: high > MADT: Interrupt override: source 9, irq 9 > ioapic0: intpin 9 trigger: level > ioapic0: intpin 9 polarity: high > MADT: Interrupt override: source 14, irq 14 > ioapic0: intpin 14 trigger: edge > ioapic0: intpin 14 polarity: high > MADT: Interrupt override: source 15, irq 15 > ioapic0: intpin 15 trigger: edge > ioapic0: intpin 15 polarity: high > lapic0: Routing NMI -> LINT1 > lapic0: LINT1 trigger: edge > lapic0: LINT1 polarity: high > ioapic0 irqs 0-23 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00040010 LDR: 0x01000000 DFR: 0x0fffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00000000 err: 0x00010000 pcm: 0x00010000 > wlan: <802.11 Link Layer> > null: > random: > nfslock: pseudo-device > mem: > io: > cpuid = 0; apic id = 00 > instruction pointer = 0x8:0xffffffff803e9a40 > stack pointer = 0x10:0xffffffff80e36d00 > frame pointer = 0x10:0xffffffff80e36d20 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 0 > current process = 0 (swapper) > [thread pid 0 tid 0 ] > Stopped at root_bus_configure: pushq %rbp > db> bt > Tracing pid 0 tid 0 td 0xffffffff80854a60 > root_bus_configure() at root_bus_configure > mi_startup() at mi_startup+0xd3 > btext() at btext+0x2c This is already fixed in HEAD and RELENG_6 after SNAP009 was made. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 18:54:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7AAC16A41F for ; Mon, 5 Dec 2005 18:54:31 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B79243D77 for ; Mon, 5 Dec 2005 18:54:23 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3200123 for multiple; Mon, 05 Dec 2005 13:52:30 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB5Is6L5040561; Mon, 5 Dec 2005 13:54:18 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, psientist@gmail.com Date: Mon, 5 Dec 2005 13:45:09 -0500 User-Agent: KMail/1.8.2 References: <20051203120031.BC03216A420@hub.freebsd.org> <1133646682.20455.1.camel@localhost.localdomain> In-Reply-To: <1133646682.20455.1.camel@localhost.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512051345.10382.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: freebsd-current Digest, Vol 123, Issue 10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 18:54:32 -0000 On Saturday 03 December 2005 04:51 pm, discord wrote: > I need to make a bootable freeBSD install cd in the El Torito format. > Does anybody know how I go about doing that? man 7 release There's also some other info in the online docs about building releases. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 19:32:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F048D16A41F for ; Mon, 5 Dec 2005 19:32:16 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBFB243D69 for ; Mon, 5 Dec 2005 19:32:12 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id A5C9E1A9DD; Mon, 5 Dec 2005 20:32:10 +0100 (CET) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 26943-04; Mon, 5 Dec 2005 20:32:09 +0100 (CET) Received: from [192.168.0.94] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id 4D4C71A6EA; Mon, 5 Dec 2005 20:32:07 +0100 (CET) Message-ID: <439495B1.5060305@shapeshifter.se> Date: Mon, 05 Dec 2005 20:32:01 +0100 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> In-Reply-To: <86mzjflc97.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at h3q.net Cc: Travis Mikalson , current@freebsd.org Subject: Re: make.conf options you cannot use for building CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 19:32:17 -0000 Dag-Erling Smørgrav wrote: > Fredrik Lindberg writes: > >>I introduced powerd to pthreads so this is most likely my fault. > > > There is no reason to use threads in powerd. Simply merge the > devd_read() loop into your main loop, using select() with a timeout > instead of usleep(). > Wouldn't that turn in into a polling style again?. The reason to use devd was to obtain a more interrupt driven model instead of the sysctl-polling method originally used. Both metods are supported and the devd method is only used if the devd.pipe is avaiable. Obtaining the AC line state, which occurs at each iteration, requires in the devd case, only reading a variable which is very cheap. However, admittedly, I haven't studied the code for select, and it might be cheap enough. powerd can still run without pthreads (using the sysctl-method), it just needs the proper make magic. Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 20:31:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EB1016A41F for ; Mon, 5 Dec 2005 20:31:36 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E8F543D73 for ; Mon, 5 Dec 2005 20:31:29 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EjMxp-0000Vq-KG for freebsd-current@freebsd.org; Mon, 05 Dec 2005 21:29:33 +0100 Received: from gw205.f5.com ([205.229.151.151]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Dec 2005 21:29:33 +0100 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 05 Dec 2005 21:29:33 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: othermark Date: Mon, 05 Dec 2005 12:28:02 -0800 Lines: 25 Message-ID: References: <1132743283.1197.55.camel@leguin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: KNode/0.9.3 Sender: news Subject: Re: DRM update for testing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 20:31:36 -0000 Eric Anholt wrote: > I've got a patch at: > http://people.freebsd.org/~anholt/dri/drm-sys-20051123.diff > for testing, which merges DRM CVS into FreeBSD. > > It doesn't > bring in the via driver, which jakeb ported but which got overcome by > new linux-specific code (volunteers to work on this in DRM CVS would be > excellent!) in CVS. Also, the i915 (i830 through i915 integrated > graphics) driver should be pretty quick for someone with a bit of newbus > knowledge to finish off, or it could be a chance someone who cared to > learn more about the FreeBSD kernel :) Thanks for your work on this, with the recent commits to this and agp_810 in -current my card comes up and is detected and i915.ko and drm.ko load. Testing this and drm in X, generates a huge interrupt storm on irq 11. Things work, but are slow as molasses with the system 75% in interrupt servicing. Has anyone else seen this on their 915 systems? -- othermark atkin901 at nospam dot yahoo dot com (!wired)?(coffee++):(wired); From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 21:33:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C49016A420 for ; Mon, 5 Dec 2005 21:33:09 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FEEB43D7C for ; Mon, 5 Dec 2005 21:33:02 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jB5LWuI6030939 for ; Mon, 5 Dec 2005 13:32:56 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jB5LWuUa030934 for freebsd-current@freebsd.org; Mon, 5 Dec 2005 13:32:56 -0800 (PST) (envelope-from sgk) Date: Mon, 5 Dec 2005 13:32:56 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20051205213255.GA21943@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: Where's ldexpf? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 21:33:09 -0000 #include #include int main(void) { float x; x = ldexpf(2., 2); printf("%e\n", x); return 0; } cc -o z ldexpf.c -lm /mnt1/sgk/tmp/ccoP164Y.o(.text+0x16): In function `main': undefined reference to `ldexpf' Perhpas, we need a weak reference. --- /usr/src/lib/msun/src/e_scalbf.c.orig Mon Dec 5 13:29:47 2005 +++ /usr/src/lib/msun/src/e_scalbf.c Mon Dec 5 13:28:53 2005 @@ -42,3 +42,5 @@ return scalbnf(x,(int)fn); #endif } + +__weak_reference(scalbf, ldexpf); -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 22:11:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A05C916A41F for ; Mon, 5 Dec 2005 22:11:52 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81A9643D94 for ; Mon, 5 Dec 2005 22:11:43 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jB5MBdeP019912 for ; Mon, 5 Dec 2005 14:11:39 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jB5MBdDE019911 for freebsd-current@freebsd.org; Mon, 5 Dec 2005 14:11:39 -0800 (PST) (envelope-from sgk) Date: Mon, 5 Dec 2005 14:11:39 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20051205221139.GA14858@troutmask.apl.washington.edu> References: <20051205213255.GA21943@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051205213255.GA21943@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i Subject: Re: Where's ldexpf? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 22:11:52 -0000 On Mon, Dec 05, 2005 at 01:32:56PM -0800, Steve Kargl wrote: > > #include > #include > > int main(void) { > float x; > x = ldexpf(2., 2); > printf("%e\n", x); > return 0; > } > > cc -o z ldexpf.c -lm > /mnt1/sgk/tmp/ccoP164Y.o(.text+0x16): In function `main': > undefined reference to `ldexpf' > > Perhpas, we need a weak reference. > > --- /usr/src/lib/msun/src/e_scalbf.c.orig Mon Dec 5 13:29:47 2005 > +++ /usr/src/lib/msun/src/e_scalbf.c Mon Dec 5 13:28:53 2005 > @@ -42,3 +42,5 @@ > return scalbnf(x,(int)fn); > #endif > } > + > +__weak_reference(scalbf, ldexpf); > Can someone commit the above patch? It is needed for all non-i386 architectures. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Dec 5 22:30:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B60D216A41F for ; Mon, 5 Dec 2005 22:30:10 +0000 (GMT) (envelope-from bofh@terranova.net) Received: from tog.net (tog.net [216.89.226.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 639E343D60 for ; Mon, 5 Dec 2005 22:30:09 +0000 (GMT) (envelope-from bofh@terranova.net) Received: by tog.net (Postfix, from userid 96) id 7013C29B650; Mon, 5 Dec 2005 17:30:07 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.1.0-terranovanet_v6 (2005-09-13) on tog.net X-Spam-Level: X-Spam-Status: No, score=-4.4 required=7.1 tests=ALL_TRUSTED,AWL,BAYES_00, TW_PF autolearn=ham version=3.1.0-terranovanet_v6 Received: from [192.168.5.103] (host-216-89-228-162.wireless.terranova.net [216.89.228.162]) by tog.net (Postfix) with ESMTP id 25F4129B691 for ; Mon, 5 Dec 2005 17:29:40 -0500 (EST) Message-ID: <4394BECD.6090608@terranova.net> Date: Mon, 05 Dec 2005 17:27:25 -0500 From: Travis Mikalson Organization: TerraNovaNet Internet Services User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: -CURRENT crashdumps, mbuf corruption X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2005 22:30:10 -0000 Hi, This looks like an mbuf corruption problem, can you take a look at these? http://tog.net/crashdumps/ I've got two different ones, one seems to involve all of my network interfaces and another seems just to involve if_ath. I'm not an expert at reading this, but both crashes look like they choked on corrupt mbufs. I have WITNESS and INVARIANT running in that kernel, I don't know if they are of any use for figuring this problem out. Is there any additional information available that I can retrieve that can help? I'm told that mbuf corruption problems are very hard to track down, I'm wondering if there's anything I can do. FYI, this box's job in life at the moment while I've got it as stripped-down as possible is to shuffle packets back and forth between one if_ath (in hostap mode) and one if_vr using if_bridge. ipfw is in there somewhere but net.link.bridge.pfil_bridge is off and so is net.link.ether.ipfw and net.link.bridge.ipfw. Thanks, -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 x101 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- Life's not fair, but the root password helps. From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 02:16:15 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F257416A41F for ; Tue, 6 Dec 2005 02:16:14 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4766643D45 for ; Tue, 6 Dec 2005 02:16:14 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 21FB3229CE7 for ; Fri, 2 Dec 2005 11:45:59 -0800 (PST) Received: from [10.251.23.117] (nat.ironport.com [63.251.108.100]) by idiom.com (8.12.11/8.12.11) with ESMTP id jB2JjwbS037773 for ; Fri, 2 Dec 2005 11:45:58 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <4390A46C.4080506@elischer.org> Date: Fri, 02 Dec 2005 11:45:48 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: multipart/mixed; boundary="------------010808050109040606000601" Cc: Subject: [Fwd: Re: Looking for a project to get started with kernel programming] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 02:16:15 -0000 This is a multi-part message in MIME format. --------------010808050109040606000601 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit one down... --------------010808050109040606000601 Content-Type: message/rfc822; name="Re: Looking for a project to get started with kernel programming" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="Re: Looking for a project to get started with kernel programming" Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.195]) by idiom.com (8.12.11/8.12.11) with ESMTP id jB28n78m000306 for ; Fri, 2 Dec 2005 00:49:07 -0800 (PST) (envelope-from vbhanu@gmail.com) Received: by zproxy.gmail.com with SMTP id r28so481651nza for ; Fri, 02 Dec 2005 00:49:06 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FJRG35kYyUWfaJYMJyfS0kKtyj28fR30NF5+7pOu+GwQ8QH/NMF1HioqZQkvZ87kB9UigpIaAHYRc5xJKenAZF5N2UFMrCQcIcgtI/FeNG6AXf8LHgnXMlPirz1jGDklmZznpipv2RKr3jnn+in0RrNSpLV4haYob4ttuHkVom0= Received: by 10.65.38.14 with SMTP id q14mr1311850qbj; Fri, 02 Dec 2005 00:48:02 -0800 (PST) Received: by 10.65.235.20 with HTTP; Fri, 2 Dec 2005 00:48:01 -0800 (PST) Message-ID: <950bc01d0512020048m72692c6cs8e46be43ee654e65@mail.gmail.com> Date: Fri, 2 Dec 2005 14:18:02 +0530 From: Bhanu Chandra To: Julian Elischer Subject: Re: Looking for a project to get started with kernel programming In-Reply-To: <438FEA75.9040901@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <950bc01d0512012223g34083957s8250079a6aeccf39@mail.gmail.com> <438FEA75.9040901@elischer.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by idiom.com id jB28n78m000306 X-Spam-Status: No, hits=-2.6 required=5 tests=SPF_PASS,BAYES_00, AWL X-Accessio-Status: NO, score=0.00,none version=6.0 count=0 X-ClamAV-Status: No X-Idiom-Reporting: If this was spam, please report it to http://www.spamcop.net Ok I am doing it!!. Thanks, Bhanu On 12/2/05, Julian Elischer wrote: > Bhanu Chandra wrote: > > >Dear, > > > >I went through http://people.freebsd.org/~phk/TODO/ and found some > >inetersting projects. The one that i found the most captivating is the > >"Kernel stack depth warning" project. I am a student and I am > >interested in Operating Systems and intend to take up Research in the > >same field. You can find my resume in vairous formats at > >http://home.iitk.ac.in/~vbhanu . > > > >I have been a consistent performer in academics and am very much > >motivated to work on projects related to Operating Systems to get > >hands on experience. > > > >If for some reason you cannot give the above said project to me then > >please suggest other projects that you can. > > > > > >Anticipating a positive reply, > > > > > you don't need to ask for a project.. > just start, and tell us that you are doing it. > > >Thank you, > > > >V Bhanu Chandra > >Third Year Undergraduate (B. Tech.) > >Dept of Computer Science and Engineering. > >Indian Institute of Technology Kanpur. > >Kanpur. > >India > >_______________________________________________ > >freebsd-arch@freebsd.org mailing list > >http://lists.freebsd.org/mailman/listinfo/freebsd-arch > >To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > > > > > > --------------010808050109040606000601-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 05:42:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85D6116A41F; Tue, 6 Dec 2005 05:42:45 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from mta205-rme.xtra.co.nz (mta205-rme.xtra.co.nz [210.86.15.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63CF343D45; Tue, 6 Dec 2005 05:42:43 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from mta4-rme.xtra.co.nz ([210.86.15.193]) by mta205-rme.xtra.co.nz with ESMTP id <20051206054242.DKIA1687.mta205-rme.xtra.co.nz@mta4-rme.xtra.co.nz>; Tue, 6 Dec 2005 18:42:42 +1300 Received: from serv.int.fubar.geek.nz ([222.152.219.118]) by mta4-rme.xtra.co.nz with ESMTP id <20051206054242.KZVP1416.mta4-rme.xtra.co.nz@serv.int.fubar.geek.nz>; Tue, 6 Dec 2005 18:42:42 +1300 Received: from [192.168.1.160] (unknown [192.168.1.160]) by serv.int.fubar.geek.nz (Postfix) with ESMTP id 976FA60DD; Tue, 6 Dec 2005 18:42:40 +1300 (NZDT) Message-ID: <439524D6.6010705@fubar.geek.nz> Date: Tue, 06 Dec 2005 18:42:46 +1300 From: Andrew Turner User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chris Pressey References: <20051027200448.1ba236fe.cpressey@catseye.mine.nu> <43753528.7030802@freesbie.org> <20051202123120.736bf5ff.cpressey@catseye.mine.nu> In-Reply-To: <20051202123120.736bf5ff.cpressey@catseye.mine.nu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: geom@freebsd.org, current@freebsd.org, discussion@bsdinstaller.com Subject: Re: [BSDInstaller] Re: fdisk(8) no longer capable of altering geometry X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 05:42:45 -0000 Chris Pressey wrote: > Does ANYONE else see the same behaviour that I am seeing? Namely: > >- As root, run "fdisk -u ad1" (or on whatever disk you like) >- Tell fdisk(8) "yes, I'd like to change our idea of what the BIOS > thinks (of the geometry of this disk)" >- Give fdisk(8) any new geometry values you like >- Be happy with this choice >- Choose to write the new partition table >- Get a "GEOM not found" error (optional) >- Run "fdisk ad1" again and observe that the geometry hasn't changed > >I see this on CURRENT as of late last night. > > I can see this on CURRENT from a week ago. >-Chris > > > > From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 06:10:06 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B0E6716A41F for ; Tue, 6 Dec 2005 06:10:06 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [204.14.90.11]) by mx1.FreeBSD.org (Postfix) with SMTP id 5C2D343D7F for ; Tue, 6 Dec 2005 06:10:05 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 23915 invoked by uid 399); 6 Dec 2005 06:09:59 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.net@127.0.0.1) by localhost with SMTP; 6 Dec 2005 06:09:59 -0000 Message-ID: <43952B34.5010403@FreeBSD.org> Date: Mon, 05 Dec 2005 22:09:56 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051130) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Candler References: <200512031609.48962.nb_root@videotron.ca> <200512041135.39342.nb_root@videotron.ca> <20051204174032.GA1304@mail.scottro.net> <200512041303.45970.nb_root@videotron.ca> <43933227.4050906@FreeBSD.org> <20051205123014.GA90877@uk.tiscali.com> In-Reply-To: <20051205123014.GA90877@uk.tiscali.com> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Scott Robbins , Nicolas Blais Subject: Re: [rc update] sshd no longer starts at boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 06:10:06 -0000 Brian Candler wrote: > I presume that if ports are upgraded so that they honour foo_enable from > rc.conf, there is no need for them to install foo.sh.sample any more, and > they should just install foo.sh instead? Close, they should install foo. Doug -- This .signature sanitized for your protection From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 06:30:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F9EC16A41F for ; Tue, 6 Dec 2005 06:30:25 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7E7D43D53 for ; Tue, 6 Dec 2005 06:30:24 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Tue, 6 Dec 2005 09:30:20 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051206093020.691e1483.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 06:30:25 -0000 I add pseudo-device amdpmsub because nForce2 have two SMBus interfaces. Patch here: http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff dmesg output: amdpm0: port 0xdc00-0xdc1f,0x5000-0x501f,0x5500 -0x551f irq 5 at device 1.1 on pci0 smbus0: on amdpm0 smb0: on smbus0 amdpmsub0: on amdpm0 smbus1: on amdpmsub0 smb1: on smbus1 I`ve tested it with xmbmon and all works fine. -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 06:52:26 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1823A16A41F for ; Tue, 6 Dec 2005 06:52:26 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from jazz.hansabank.lt (jazz.hansabank.lt [193.109.235.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A34443D4C for ; Tue, 6 Dec 2005 06:52:24 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by jazz.hansabank.lt (Postfix) with ESMTP id 4E63FF952 for ; Tue, 6 Dec 2005 08:52:23 +0200 (EET) X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 6 Dec 2005 08:52:20 +0200 Message-ID: <217202CB5FF8AE439E263CE3D48ECB5068C4F2@honda.int.hansa.lt> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: vmware calcru runtime went backward and huge inaccuracy in clock Thread-Index: AcX6MYjvpIXiBSxQQsCEOgy7Z5O8yQ== From: "Putinas Piliponis" To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: vmware calcru runtime went backward and huge inaccuracy in clock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 06:52:26 -0000 Hey, =20 I know I am not the first who brings up this problem. But browsing trough mail archives I didn't found a working solution. I am running vmware 5.5 currently and FreeBSD 6.0-RELEASE. After upgrading from 5.4 (at the same time I upgraded vmware from 5.0 so can't really say which fault is it). I noticed what I don't get daily reports. After small investigation I found out what clock inaccuracy is like in 2 minutes I get 1 minute time delay from real clock. (I wait 2 minutes, I do ntpdate with server, I get every time offset 60 seconds) I tried all kern.timecounter.hardware available options (ACPI-Fast, i8254, TSC) pretty much same result with all of them. =20 Time on host machine is accurate. As well I have on other host (with same hardware) running VMware 5.0 with FreeBSD 5.4 with timecounter.hardware: ACPI-safe and time accuracy there is like 60s in 24h (or normal in other words). =20 =20 Soo.. here comes my question, is it vmware fault, or is it FreeBSD fault? And any suggestions what I can do about ? =20 From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 07:20:44 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7848C16A41F for ; Tue, 6 Dec 2005 07:20:44 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from blues.hansabank.lt (blues.hansabank.lt [193.109.235.156]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0290343D49 for ; Tue, 6 Dec 2005 07:20:43 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by blues.hansabank.lt (Postfix) with ESMTP id E6AD846129 for ; Tue, 6 Dec 2005 09:20:42 +0200 (EET) X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 6 Dec 2005 09:20:39 +0200 Message-ID: <217202CB5FF8AE439E263CE3D48ECB509BAA75@honda.int.hansa.lt> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: vmware calcru runtime went backward and huge inaccuracy in clock Thread-Index: AcX6MYjvpIXiBSxQQsCEOgy7Z5O8yQAA7SwA From: "Putinas Piliponis" To: Subject: RE: vmware calcru runtime went backward and huge inaccuracy in clock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 07:20:44 -0000 As additional test I have copied 6.0-STABLE to another host under VMWare 5.0 where 5.4-STABLE doesn't have issues with clock. Behaviour of 6 is same. So for me looks it's a FreeBSD 6.0 thing now. -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Putinas Piliponis Sent: Tuesday, December 06, 2005 8:52 AM To: freebsd-current@freebsd.org Subject: vmware calcru runtime went backward and huge inaccuracy in clock Hey, =20 I know I am not the first who brings up this problem. But browsing trough mail archives I didn't found a working solution. I am running vmware 5.5 currently and FreeBSD 6.0-RELEASE. After upgrading from 5.4 (at the same time I upgraded vmware from 5.0 so can't really say which fault is it). I noticed what I don't get daily reports. After small investigation I found out what clock inaccuracy is like in 2 minutes I get 1 minute time delay from real clock. (I wait 2 minutes, I do ntpdate with server, I get every time offset 60 seconds) I tried all kern.timecounter.hardware available options (ACPI-Fast, i8254, TSC) pretty much same result with all of them. =20 Time on host machine is accurate. As well I have on other host (with same hardware) running VMware 5.0 with FreeBSD 5.4 with timecounter.hardware: ACPI-safe and time accuracy there is like 60s in 24h (or normal in other words). =20 =20 Soo.. here comes my question, is it vmware fault, or is it FreeBSD fault? And any suggestions what I can do about ? =20 _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 08:24:12 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE01716A41F; Tue, 6 Dec 2005 08:24:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E1D343D5D; Tue, 6 Dec 2005 08:24:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 6BED11A3C27; Tue, 6 Dec 2005 00:24:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 97CAD533C6; Tue, 6 Dec 2005 03:24:11 -0500 (EST) Date: Tue, 6 Dec 2005 03:24:09 -0500 From: Kris Kennaway To: alc@FreeBSD.org Message-ID: <20051206082409.GA63640@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: current@FreeBSD.org Subject: Null pointer deref in swp_pager_meta_ctl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 08:24:13 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I configured a 74GB swap-backed md on sparc64..after a week or two (during which time swap was slowly filling as more of the md was dirtied) it panicked: #10 0x00000000c0179ec8 in panic (fmt=0xc03dcb80 "trap: %s") at ../../../kern/kern_shutdown.c:539 #11 0x00000000c031e818 in trap (tf=0xee0e32f0) at ../../../sparc64/sparc64/trap.c:369 #12 0x00000000c0048fc0 in tl1_trap () #13 0x00000000c02dc928 in swp_pager_meta_ctl (object=0x0, pindex=3874086912, flags=-420880384) at ../../../vm/swap_pager.c:1902 #14 0x00000000c01a6a90 in turnstile_release (lock=0x0) at ../../../kern/subr_turnstile.c:489 #15 0x00000000c02dafa4 in swap_pager_getpages (object=0xfffff8005c94b260, m=0xee0e3628, count=1, reqpage=0) at ../../../vm/swap_pager.c:992 #16 0x00000000c00e66c0 in mdstart_swap (sc=0xfffff80025ebd000, bp=0xfffff80122255b00) at vm_pager.h:130 #17 0x00000000c00e6c94 in md_kthread (arg=0xfffff80025ebd000) at ../../../dev/md/md.c:676 #18 0x00000000c015e7fc in fork_exit (callout=0xc00e6a00 , arg=0xfffff80025ebd000, frame=0xee0e3880) at ../../../kern/kern_fork.c:789 #19 0x00000000c00491b0 in fork_trampoline () #20 0x00000000c00491b0 in fork_trampoline () Previous frame identical to this frame (corrupt stack?) (kgdb) frame 15 #15 0x00000000c02dafa4 in swap_pager_getpages (object=0xfffff8005c94b260, m=0xee0e3628, count=1, reqpage=0) at ../../../vm/swap_pager.c:992 992 blk = swp_pager_meta_ctl(mreq->object, mreq->pindex, 0); (kgdb) print *mreq $2 = {pageq = {tqe_next = 0xfffff80139cbdd70, tqe_prev = 0xfffff8013b249470}, listq = {tqe_next = 0xfffff8013c93e080, tqe_prev = 0xfffff801393111f8}, left = 0xfffff801393111e8, right = 0xfffff8013d505a38, object = 0x0, pindex = 4341534, phys_addr = 1870839808, md = {tte_list = {tqh_first = 0xbee6e9c0, tqh_last = 0xbee6e9d0}, pmap = 0x0, colors = {1, 0}, color = 0, flags = 0}, queue = 23, flags = 0, pc = 22, wire_count = 0, cow = 0, hold_count = 0, act_count = 0 '\0', busy = 0 '\0', valid = 0, dirty = 0} (kgdb) print swap_pager_avail $3 = 6210309 What else can I extract from the core to help diagnose this? Kris --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDlUqoWry0BWjoQKURAuaqAKCgO5cqtXSIO0Be03xGyal1gR+GoACfR4q4 ld+21zKBybXyt7ZqLgB+HDI= =OLgb -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 09:17:48 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C02F16A41F; Tue, 6 Dec 2005 09:17:48 +0000 (GMT) (envelope-from tom.hurst@clara.net) Received: from spork.qfe3.net (spork.qfe3.net [212.13.207.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id B614243D76; Tue, 6 Dec 2005 09:17:42 +0000 (GMT) (envelope-from tom.hurst@clara.net) Received: from [81.104.55.176] (helo=voi.aagh.net) by spork.qfe3.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EjYxA-000Dpm-M0; Tue, 06 Dec 2005 09:17:40 +0000 Received: from freaky by voi.aagh.net with local (Exim 4.54 (FreeBSD)) id 1EjYxA-000La2-9Y; Tue, 06 Dec 2005 09:17:40 +0000 Date: Tue, 6 Dec 2005 09:17:40 +0000 From: Thomas Hurst To: =?iso-8859-1?Q?S=F8ren?= Schmidt Message-ID: <20051206091740.GA79710@voi.aagh.net> Mail-Followup-To: =?iso-8859-1?Q?S=F8ren?= Schmidt , Gavin Atkinson , Martin Cracauer , freebsd-current@FreeBSD.org References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> <20051127215510.A17131@cons.org> <1133190443.41553.18.camel@buffy.york.ac.uk> <438B1F90.3090708@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438B1F90.3090708@FreeBSD.org> Organization: Not much. User-Agent: Mutt/1.5.11 Sender: Thomas Hurst X-RBL-Warning: 81.104.55.176 is in RBL blacklist at dnsbl.sorbs.net Cc: Martin Cracauer , freebsd-current@FreeBSD.org Subject: Re: Building new Athlon AMD64 Socket 939 or 940 machine X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:17:48 -0000 * S?ren Schmidt (sos@FreeBSD.org) wrote: [nForce 4 SATA Hotswap] > That used to work on my MSI nf4 board on 6.0 forward. Tyan's nForce 4 boards seem to be among those that don't handle hot-swap properly in FreeBSD; the disks disconnect fine, and on attaching FreeBSD sees the "connect requested", but the disk doesn't get picked up: ata4: DISCONNECT requested subdisk8: detached ad8: detached ata4: DISCONNECTED ata4: CONNECT requested ata4: CONNECTED .. No amount of fiddling with atacontrol detach/attach/reinit brings it back. This is at least true of RELENG_6 on a K8WE and the Tyan board in Sun's new entry-level Opteron rackmount (X2100). -- Thomas 'Freaky' Hurst http://hur.st/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 09:44:56 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E710316A41F for ; Tue, 6 Dec 2005 09:44:56 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6082243D53 for ; Tue, 6 Dec 2005 09:44:56 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 814D92083; Tue, 6 Dec 2005 10:44:48 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 6E2692080; Tue, 6 Dec 2005 10:44:48 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 513E933C1D; Tue, 6 Dec 2005 10:44:48 +0100 (CET) To: Fredrik Lindberg References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 06 Dec 2005 10:44:48 +0100 In-Reply-To: <439495B1.5060305@shapeshifter.se> (Fredrik Lindberg's message of "Mon, 05 Dec 2005 20:32:01 +0100") Message-ID: <861x0qmuen.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Travis Mikalson , current@freebsd.org Subject: Re: make.conf options you cannot use for building CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 09:44:57 -0000 Fredrik Lindberg writes: > Dag-Erling Sm=F8rgrav wrote: > > There is no reason to use threads in powerd. Simply merge the > > devd_read() loop into your main loop, using select() with a timeout > > instead of usleep(). > Wouldn't that turn in into a polling style again? No. > The reason to use > devd was to obtain a more interrupt driven model instead of the > sysctl-polling method originally used. Both metods are supported and > the devd method is only used if the devd.pipe is avaiable. If the devd loop is an *alternative* to the polling loop, there's even less reason to use threads. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 10:41:44 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 48C5E16A41F for ; Tue, 6 Dec 2005 10:41:44 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BF9E43D6E for ; Tue, 6 Dec 2005 10:41:43 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id EB5331A9DD; Tue, 6 Dec 2005 11:41:40 +0100 (CET) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 39480-06; Tue, 6 Dec 2005 11:41:39 +0100 (CET) Received: from [192.168.0.94] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id A99FB1A6EA; Tue, 6 Dec 2005 11:41:39 +0100 (CET) Message-ID: <43956ADF.4050504@shapeshifter.se> Date: Tue, 06 Dec 2005 11:41:35 +0100 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> In-Reply-To: <861x0qmuen.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at h3q.net Cc: Travis Mikalson , current@freebsd.org Subject: Re: powerd [was: make.conf options you cannot use for building CURRENT] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 10:41:44 -0000 Dag-Erling Smørgrav wrote: > Fredrik Lindberg writes: > >>Dag-Erling Smørgrav wrote: >> >>>There is no reason to use threads in powerd. Simply merge the >>>devd_read() loop into your main loop, using select() with a timeout >>>instead of usleep(). >> >>Wouldn't that turn in into a polling style again? > > > No. > > >>The reason to use >>devd was to obtain a more interrupt driven model instead of the >>sysctl-polling method originally used. Both metods are supported and >>the devd method is only used if the devd.pipe is avaiable. > > > If the devd loop is an *alternative* to the polling loop, there's even > less reason to use threads. > > DES Yes it's an alternative, reading a variable versus doing a sysctl call each interation. It seemed like I good idea, when I first wrote this (almost a year ago), to have a thread providing a cached value of the AC state. But maybe I was trying to be too smart or something. Anyone know what happened to the powerd SoC project? I never spent more time on powerd because I assumed it would be more or less rewritten. I wouldn't mind hacking on powerd but I don't want to step on somebodys toes or duplicate work. Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 11:23:40 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDEC516A41F; Tue, 6 Dec 2005 11:23:40 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67E2F43D73; Tue, 6 Dec 2005 11:23:36 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 3A7A42085; Tue, 6 Dec 2005 12:23:28 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 254CD2083; Tue, 6 Dec 2005 12:23:28 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 016DA33C1D; Tue, 6 Dec 2005 12:23:27 +0100 (CET) To: Fredrik Lindberg References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Tue, 06 Dec 2005 12:23:27 +0100 In-Reply-To: <43956ADF.4050504@shapeshifter.se> (Fredrik Lindberg's message of "Tue, 06 Dec 2005 11:41:35 +0100") Message-ID: <86slt6lb9s.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Travis Mikalson , current@freebsd.org, njl@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 11:23:41 -0000 Fredrik Lindberg writes: > Dag-Erling Sm=F8rgrav wrote: > > If the devd loop is an *alternative* to the polling loop, there's > > even less reason to use threads. > Yes it's an alternative, reading a variable versus doing a sysctl call > each interation. It seemed like I good idea, when I first wrote this > (almost a year ago), to have a thread providing a cached value of the > AC state. But maybe I was trying to be too smart or something. Yes. Not only is it a bad design idea, but the implementation is wrong, and likely to fail badly when compiled at high optimization levels. Please revert powerd.c to revision 1.13. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 11:55:36 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FF1916A41F; Tue, 6 Dec 2005 11:55:36 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1897043D68; Tue, 6 Dec 2005 11:55:30 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.201] (celsius.cc.rsu.ru [195.208.252.201]) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6BtRJx088166; Tue, 6 Dec 2005 14:55:27 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <43957D3F.4070109@rsu.ru> Date: Tue, 06 Dec 2005 14:59:59 +0300 From: Michael Bushkov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: Subject: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 11:55:36 -0000 Hello! I've made the "nsswitch + caching daemon" project during the Google's Summer of Code. I'm still working on it - there is always a room for improvements :) Since previous release, I've made a lot of changes to the initial version, fixed some bugs, and this version seems to be worth using it :) Here is the the new release of the patch: http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached_rev2.patch The description of the project itself and of its several new features can be found here: http://rsu.ru/~bushman/nsswitch_cached/ Your feedback would be great! Michael Bushkov Rostov State University From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 13:18:23 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D40C916A41F; Tue, 6 Dec 2005 13:18:23 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1B7643D46; Tue, 6 Dec 2005 13:18:22 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id 88FD91A9DD; Tue, 6 Dec 2005 14:18:20 +0100 (CET) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42814-01; Tue, 6 Dec 2005 14:18:19 +0100 (CET) Received: from [192.168.0.94] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id 7A44D1A6EA; Tue, 6 Dec 2005 14:18:19 +0100 (CET) Message-ID: <43958F9A.2000205@shapeshifter.se> Date: Tue, 06 Dec 2005 14:18:18 +0100 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> In-Reply-To: <86slt6lb9s.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at h3q.net Cc: Travis Mikalson , current@freebsd.org, njl@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 13:18:24 -0000 Dag-Erling Smørgrav wrote: > Fredrik Lindberg writes: > >>Dag-Erling Smørgrav wrote: >> >>>If the devd loop is an *alternative* to the polling loop, there's >>>even less reason to use threads. >> >>Yes it's an alternative, reading a variable versus doing a sysctl call >>each interation. It seemed like I good idea, when I first wrote this >>(almost a year ago), to have a thread providing a cached value of the >>AC state. But maybe I was trying to be too smart or something. > > > Yes. Not only is it a bad design idea, but the implementation is > wrong, and likely to fail badly when compiled at high optimization > levels. Ignoring the fact that it does work with -O3 (gcc 3.4.4), could you please explain why it has the potential of failing with high optimizations. Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 14:30:53 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A90F416A420; Tue, 6 Dec 2005 14:30:53 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.95]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0949543D5E; Tue, 6 Dec 2005 14:30:41 +0000 (GMT) (envelope-from keramida@linux.gr) Received: from flame.pc (aris.bedc.ondsl.gr [62.103.39.226]) by kane.otenet.gr (8.13.4/8.13.4/Debian-8) with SMTP id jB6EUXDE012374; Tue, 6 Dec 2005 16:30:34 +0200 Received: by flame.pc (Postfix, from userid 1001) id 98A3F117BE; Tue, 6 Dec 2005 16:29:50 +0200 (EET) Date: Tue, 6 Dec 2005 16:29:50 +0200 From: Giorgos Keramidas To: Fredrik Lindberg Message-ID: <20051206142950.GA14331@flame.pc> References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <43958F9A.2000205@shapeshifter.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43958F9A.2000205@shapeshifter.se> Cc: Dag-Erling Sm?rgrav , Travis Mikalson , current@freebsd.org, njl@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 14:30:53 -0000 On 2005-12-06 14:18, Fredrik Lindberg wrote: >Dag-Erling Sm?rgrav wrote: >>Fredrik Lindberg writes: >>>Dag-Erling Sm?rgrav wrote: >>>> If the devd loop is an *alternative* to the polling loop, there's >>>> even less reason to use threads. >>> >>> Yes it's an alternative, reading a variable versus doing a sysctl call >>> each interation. It seemed like I good idea, when I first wrote this >>> (almost a year ago), to have a thread providing a cached value of the >>> AC state. But maybe I was trying to be too smart or something. >> >> Yes. Not only is it a bad design idea, but the implementation is >> wrong, and likely to fail badly when compiled at high optimization >> levels. > > Ignoring the fact that it does work with -O3 (gcc 3.4.4), could you > please explain why it has the potential of failing with high > optimizations. I haven't looked at the source code, but I think what Dag-Erling means is that optimizing compilers, in high optimization mode, may inhibit sequential read operations of the same variable, trying to 'optimize' many read operations that would (to the best of their knowledge) return the same result. This is never going to happen if the variable is declared as 'volatile' though, so I'm not sure if it applies in this case, until I look at the sources of powerd. - Giorgos From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 14:33:48 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08FE816A425; Tue, 6 Dec 2005 14:33:48 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 847CD43D5E; Tue, 6 Dec 2005 14:33:37 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from [195.208.252.201] (celsius.cc.rsu.ru [195.208.252.201]) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6EXXsC024533; Tue, 6 Dec 2005 17:33:33 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <4395A24D.9050001@rsu.ru> Date: Tue, 06 Dec 2005 17:38:05 +0300 From: Michael Bushkov User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051018) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Harti Brandt References: <43957D3F.4070109@rsu.ru> <20051206125936.E16797@beagle.kn.op.dlr.de> In-Reply-To: <20051206125936.E16797@beagle.kn.op.dlr.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 14:33:48 -0000 Hi Harti! I think, that there is a chance. We can make an nsswitch source, named "compat". This source will keep the "traditional" functionality, i.e. would be implemented through getgrent(), setgrent(). The "compat" source can also be used as a stub in all places, where we don't want to write the new, specialized code, but want our usual functionality (getgrent+setgrent). We then can modify the winbind nsswitch module to support the getgrouplist() function, so that it can work in the optimal way. So I don't see any reason, that won't allow us to do it. I can implement all the necessary stuff, If you don't mind. With best regards, Michael Harti Brandt wrote: >Hi Michael, > >just a short question: is there any chance you could marshall the >getgrouplist() call through nsswitch? Linux does this and FreeBSD doesn't. >The problem with not doing this comes when you connect a FreeBSD machine >via Samba to a large Active Directory. The current implementation of >getgrouplist() scans through all groups. This may take several minutes >depending on the size of the AD. On Linux this is much faster, because >Samba's implementation of getgrouplist() can directly ask the AD for a >list of all members of a given group. > >I would try to do this myself, but given my lack of knowledge in the >nsswitch stuff and the lack of free time this would take some time. > >Thanks, >harti > >On Tue, 6 Dec 2005, Michael Bushkov wrote: > >MB>Hello! >MB>I've made the "nsswitch + caching daemon" project during the Google's Summer >MB>of Code. I'm still working on it - there is always a room for improvements :) >MB> >MB>Since previous release, I've made a lot of changes to the initial version, >MB>fixed some bugs, and this version seems to be worth using it :) >MB> >MB>Here is the the new release of the patch: >MB>http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached_rev2.patch >MB> >MB>The description of the project itself and of its several new features can be >MB>found here: >MB>http://rsu.ru/~bushman/nsswitch_cached/ >MB> >MB>Your feedback would be great! >MB> >MB>Michael Bushkov >MB>Rostov State University >MB>_______________________________________________ >MB>freebsd-current@freebsd.org mailing list >MB>http://lists.freebsd.org/mailman/listinfo/freebsd-current >MB>To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >MB> >MB> >MB> > > From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 14:42:35 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 02D7B16A425; Tue, 6 Dec 2005 14:42:34 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from mx1.h3q.net (manticore.shapeshifter.se [212.37.5.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 304CB43D5C; Tue, 6 Dec 2005 14:42:06 +0000 (GMT) (envelope-from fli+freebsd-current@shapeshifter.se) Received: from localhost (localhost [127.0.0.1]) by mx1.h3q.net (Postfix) with ESMTP id C92BF1A9DD; Tue, 6 Dec 2005 15:41:59 +0100 (CET) Received: from mx1.h3q.net ([127.0.0.1]) by localhost (mx1.h3q.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42814-04; Tue, 6 Dec 2005 15:41:58 +0100 (CET) Received: from [192.168.0.94] (81-234-243-91-o926.tbon.telia.com [81.234.243.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.h3q.net (Postfix) with ESMTP id B40F11A6EA; Tue, 6 Dec 2005 15:41:58 +0100 (CET) Message-ID: <4395A336.3060909@shapeshifter.se> Date: Tue, 06 Dec 2005 15:41:58 +0100 From: Fredrik Lindberg User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050928) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Giorgos Keramidas References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <43958F9A.2000205@shapeshifter.se> <20051206142950.GA14331@flame.pc> In-Reply-To: <20051206142950.GA14331@flame.pc> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at h3q.net Cc: Dag-Erling Sm?rgrav , Travis Mikalson , current@freebsd.org, njl@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 14:42:35 -0000 Giorgos Keramidas wrote: > On 2005-12-06 14:18, Fredrik Lindberg wrote: > >>Dag-Erling Sm?rgrav wrote: >> >>>Fredrik Lindberg writes: >>> >>>>Dag-Erling Sm?rgrav wrote: >>>> >>>>>If the devd loop is an *alternative* to the polling loop, there's >>>>>even less reason to use threads. >>>> >>>>Yes it's an alternative, reading a variable versus doing a sysctl call >>>>each interation. It seemed like I good idea, when I first wrote this >>>>(almost a year ago), to have a thread providing a cached value of the >>>>AC state. But maybe I was trying to be too smart or something. >>> >>>Yes. Not only is it a bad design idea, but the implementation is >>>wrong, and likely to fail badly when compiled at high optimization >>>levels. >> >>Ignoring the fact that it does work with -O3 (gcc 3.4.4), could you >>please explain why it has the potential of failing with high >>optimizations. > > > I haven't looked at the source code, but I think what Dag-Erling means > is that optimizing compilers, in high optimization mode, may inhibit > sequential read operations of the same variable, trying to 'optimize' > many read operations that would (to the best of their knowledge) return > the same result. > > This is never going to happen if the variable is declared as 'volatile' > though, so I'm not sure if it applies in this case, until I look at the > sources of powerd. > Ah, ok. I was thinking of something like that. Anyway, thank you for explaining this. Fredrik Lindberg From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 16:28:52 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4ECF716A41F for ; Tue, 6 Dec 2005 16:28:52 +0000 (GMT) (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 A3C0B43D75 for ; Tue, 6 Dec 2005 16:28:51 +0000 (GMT) (envelope-from Hartmut.Brandt@dlr.de) Received: from beagle.kn.op.dlr.de ([129.247.173.6]) by smtp-1.dlr.de over TLS secured channel with Microsoft SMTPSVC(6.0.3790.211); Tue, 6 Dec 2005 17:28:49 +0100 Date: Tue, 6 Dec 2005 17:28:49 +0100 (CET) From: Harti Brandt X-X-Sender: brandt_h@beagle.kn.op.dlr.de To: Michael Bushkov In-Reply-To: <4395A24D.9050001@rsu.ru> Message-ID: <20051206172638.F16797@beagle.kn.op.dlr.de> References: <43957D3F.4070109@rsu.ru> <20051206125936.E16797@beagle.kn.op.dlr.de> <4395A24D.9050001@rsu.ru> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1250000812-1133886529=:16797" X-OriginalArrivalTime: 06 Dec 2005 16:28:49.0500 (UTC) FILETIME=[234F01C0:01C5FA82] Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 16:28:52 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1250000812-1133886529=:16797 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: QUOTED-PRINTABLE On Tue, 6 Dec 2005, Michael Bushkov wrote: MB>Hi Harti! MB>I think, that there is a chance. We can make an nsswitch source, named MB>"compat". This source will keep the "traditional" functionality, i.e. wo= uld MB>be implemented through getgrent(), setgrent(). The "compat" source can a= lso MB>be used as a stub in all places, where we don't want to write the new, MB>specialized code, but want our usual functionality (getgrent+setgrent). MB>We then can modify the winbind nsswitch module to support the getgroupli= st() MB>function, so that it can work in the optimal way. The winbind part should be easy, because one can copy this more or less=20 from the linux winbind module. MB>So I don't see any reason, that won't allow us to do it. MB> MB>I can implement all the necessary stuff, If you don't mind. This would be really, really great because it makes FreeBSD in an AD=20 environment a little more usable. =F3=D0=C1=D3=C9=C2=CF, harti MB> MB>With best regards, MB>Michael MB> MB>Harti Brandt wrote: MB> MB>> Hi Michael, MB>>=20 MB>> just a short question: is there any chance you could marshall the MB>> getgrouplist() call through nsswitch? Linux does this and FreeBSD does= n't. MB>> The problem with not doing this comes when you connect a FreeBSD machi= ne MB>> via Samba to a large Active Directory. The current implementation of MB>> getgrouplist() scans through all groups. This may take several minutes MB>> depending on the size of the AD. On Linux this is much faster, because MB>> Samba's implementation of getgrouplist() can directly ask the AD for a= list MB>> of all members of a given group. MB>>=20 MB>> I would try to do this myself, but given my lack of knowledge in the MB>> nsswitch stuff and the lack of free time this would take some time. MB>>=20 MB>> Thanks, MB>> harti MB>>=20 MB>> On Tue, 6 Dec 2005, Michael Bushkov wrote: MB>>=20 MB>> MB>Hello! MB>> MB>I've made the "nsswitch + caching daemon" project during the Google= 's MB>> Summer MB>> MB>of Code. I'm still working on it - there is always a room for MB>> improvements :) MB>> MB> MB>> MB>Since previous release, I've made a lot of changes to the initial MB>> version, MB>> MB>fixed some bugs, and this version seems to be worth using it :) MB>> MB> MB>> MB>Here is the the new release of the patch: MB>> MB>http://www.rsu.ru/~bushman/nsswitch_cached/nss_cached_rev2.patch MB>> MB> MB>> MB>The description of the project itself and of its several new featur= es MB>> can be MB>> MB>found here: MB>> MB>http://rsu.ru/~bushman/nsswitch_cached/ MB>> MB> MB>> MB>Your feedback would be great! MB>> MB> MB>> MB>Michael Bushkov MB>> MB>Rostov State University MB>> MB>_______________________________________________ MB>> MB>freebsd-current@freebsd.org mailing list MB>> MB>http://lists.freebsd.org/mailman/listinfo/freebsd-current MB>> MB>To unsubscribe, send any mail to MB>> "freebsd-current-unsubscribe@freebsd.org" MB>> MB> MB>> MB> MB>> MB> MB>> =20 MB> MB> MB> --0-1250000812-1133886529=:16797-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 18:46:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2199C16A41F; Tue, 6 Dec 2005 18:46:32 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8B743D4C; Tue, 6 Dec 2005 18:46:31 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 06 Dec 2005 10:46:27 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <4395DC82.1080103@elischer.org> Date: Tue, 06 Dec 2005 10:46:26 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Bushkov References: <43957D3F.4070109@rsu.ru> In-Reply-To: <43957D3F.4070109@rsu.ru> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 18:46:32 -0000 Michael Bushkov wrote: [...] so, I've been wonderring.. what's all the fuss about nsswitch? what does it get us? (Not saying it doesn't, just hoping someone will explain) From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 19:33:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E256916A41F; Tue, 6 Dec 2005 19:33:19 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5523843D5A; Tue, 6 Dec 2005 19:33:19 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id jB6JXHuq004166; Tue, 6 Dec 2005 11:33:17 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id jB6JXHSD004164; Tue, 6 Dec 2005 11:33:17 -0800 Date: Tue, 6 Dec 2005 11:33:17 -0800 From: Brooks Davis To: Julian Elischer Message-ID: <20051206193317.GB31292@odin.ac.hmc.edu> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <4395DC82.1080103@elischer.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:33:20 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > Michael Bushkov wrote: > [...] >=20 > so, I've been wonderring.. what's all the fuss about nsswitch? > what does it get us? It gives us the ability use modules to provide arbitrary backends for a variety of interfaces to system databases. For instance getpw*(), gethost*(), etc. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFDled7XY6L6fI4GtQRAvfpAJ9YhDgT4KsY19do3iArGig+LixbawCgyPj+ KJgNXqw1x4JvAwghd/2bCtg= =lsxm -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 19:39:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B574216A41F; Tue, 6 Dec 2005 19:39:12 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id E366843D82; Tue, 6 Dec 2005 19:38:42 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.3) id jB6JcVbs019222; Tue, 6 Dec 2005 13:38:31 -0600 (CST) (envelope-from dan) Date: Tue, 6 Dec 2005 13:38:31 -0600 From: Dan Nelson To: Brooks Davis Message-ID: <20051206193830.GA33064@dan.emsphone.com> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> <20051206193317.GB31292@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051206193317.GB31292@odin.ac.hmc.edu> X-OS: FreeBSD 5.4-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Julian Elischer , Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:39:12 -0000 In the last episode (Dec 06), Brooks Davis said: > On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > > Michael Bushkov wrote: > > [...] > > > > so, I've been wonderring.. what's all the fuss about nsswitch? > > what does it get us? > > It gives us the ability use modules to provide arbitrary backends for a > variety of interfaces to system databases. For instance getpw*(), > gethost*(), etc. Michael's patch itself adds caching to our nsswitch implementation, which dramatically improves performance on slow sources (ldaps, for example). -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 19:45:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE9B916A422; Tue, 6 Dec 2005 19:45:08 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from mail.r61.net (mail.r61.net [195.208.245.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE88D43D69; Tue, 6 Dec 2005 19:44:57 +0000 (GMT) (envelope-from bushman@rsu.ru) Received: from jersey (p49.mp96.aaanet.ru [80.80.96.49]) (authenticated bits=0) by mail.r61.net (8.13.4/8.13.4) with ESMTP id jB6Ji2wo078126 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Tue, 6 Dec 2005 22:44:11 +0300 (MSK) (envelope-from bushman@rsu.ru) Message-ID: <000c01c5fa9d$7d219710$0100a8c0@jersey> From: "Michael Bushkov" To: "Julian Elischer" References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> Date: Tue, 6 Dec 2005 22:44:02 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: ClamAV version 0.86.2, clamav-milter version 0.86 on asterix.r61.net X-Virus-Status: Clean Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 19:45:09 -0000 I haven't seen much fuss, actually :) Here are some points: 1. Nsswitch makes caching easy. As nsswitch-related calls are done quite often, caching can be very useful. With nsswitch we can organize caching of different types of data (passwd, groups, services, etc) in the quite simple uniform manner. In other OSes caching is usually organized via nscd. The caching daemon (it's implementation is in the patch) is the analogue of the nscd in some way. It has different approach for caching, but can work in the way, the nscd usually works. 2. Nsswitch implementation is not yet completed. There's a number of databases, which can be supported, but their support is not yet implemented. Their support in nsswitch will give us: a) uniform way to configure the data sources to use (via nsswitch.conf) 2) the ability to cache their data 3. More concrete example is /etc/services file. The services database didn't utilize nsswitch/nsdispatch. If it uses nsdispatch, it will be able to cache data from the file - and we'll be able to make it as big as we want. Of course, first "uncached" requests will take some time, but all subsequent requests for the information, that is already in the cache will be extremely fast - they won't event open the /etc/services file. 4. Another concrete example is OpenSSH authroization keys. If we use nsswitch to retrieve them, we can easily use NIS or LDAP as their storage, which is a good thing. I hope, this will satisfy you :) With best regards, Michael ----- Original Message ----- From: "Julian Elischer" To: "Michael Bushkov" Cc: ; Sent: Tuesday, December 06, 2005 9:46 PM Subject: Re: [PATCH] nsswitch extensions + caching > Michael Bushkov wrote: > [...] > > so, I've been wonderring.. what's all the fuss about nsswitch? > what does it get us? > (Not saying it doesn't, just hoping someone will explain) > From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 22:57:35 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2E1C16A420 for ; Tue, 6 Dec 2005 22:57:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E77043D7B for ; Tue, 6 Dec 2005 22:57:28 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 06 Dec 2005 14:57:28 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <43961758.4020407@elischer.org> Date: Tue, 06 Dec 2005 14:57:28 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 22:57:35 -0000 In short words for the likes of me, Can someone give a quicj roundup on PCI routing in 4.x and -current. Specifically: How much is set up by the BIOS and how much is set up by the OS (4.x and -current). How much of my fondly held knowledge of the old hardware PICS (where an interrupt corresponded to an interrupt line) is now out of date? In this world of multiple PCI to PCI bridges, how much latitude doe the OS have in deciding where an interrupt turns up? (in 4.x and -current) An example is my Dell PE2850 (on 4.x), in which my 4 port ethernet card seems to be assigned irqs 10,14,14,2 in that order sometimes and 16,17,17,2 at others. Who is making those decisions? Is it the BIOS and 4.x is just playing along? Assuming the much maligned "boot interrupt" comes in on irq2, does the OS have the oportunity to put my 4th port somewhere else? On 4.x it collides with one of my ether ports but in -current it doesn't Linux and -current on teh same box a;;ocate way different irqs, and they agree about it.. i.e. Linux and -current assign my 4 port card IRQs 18,19,19,16. Do they agree becasue something else has decided it (the bios again?) or becasue they use the same algorythm to work it out.. Also, if the "boot interrupt" was previously set to 2, is that likely to have changed in -current? Am I now going to get clobbered on IRQ16? If yes, is this something that teh BIOS writers decided, or something that the Motherboard designers decided? From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 23:14:00 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A842F16A41F for ; Tue, 6 Dec 2005 23:14:00 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id DEF9B43D72 for ; Tue, 6 Dec 2005 23:13:59 +0000 (GMT) (envelope-from jfvogel@gmail.com) Received: by zproxy.gmail.com with SMTP id 40so201314nzk for ; Tue, 06 Dec 2005 15:13:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=JXDpsCIm4WvB0kRMH6oFteM4M87agkJ3pE6Hn0fsXBNB2J/AOlaVwGGJLljlSC2bcTKcCu2FDf2qezC/LYTId6uqtL5Po7fafoCeOOH4Mbcgm4RqBW4DEJYHJCupL2IeNlG/MyLiqslrXyHv+qWpiDvWxgfbcN4wb8N3gmAV5ug= Received: by 10.64.249.4 with SMTP id w4mr1149964qbh; Tue, 06 Dec 2005 15:13:58 -0800 (PST) Received: by 10.64.213.7 with HTTP; Tue, 6 Dec 2005 15:13:58 -0800 (PST) Message-ID: <2a41acea0512061513l10695474yc63df81c5c92fe8f@mail.gmail.com> Date: Tue, 6 Dec 2005 15:13:58 -0800 From: Jack Vogel To: Julian Elischer In-Reply-To: <43961758.4020407@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <43961758.4020407@elischer.org> Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:14:00 -0000 On 12/6/05, Julian Elischer wrote: > In short words for the likes of me, > Can someone give a quicj roundup on PCI routing in 4.x and -current. > > Specifically: > > How much is set up by the BIOS and how much is set up by the OS (4.x and > -current). > > How much of my fondly held knowledge of the old hardware PICS (where > an interrupt corresponded to an interrupt line) is now out of date? > > In this world of multiple PCI to PCI bridges, how much latitude doe the > OS have in > deciding where an interrupt turns up? > (in 4.x and -current) > > An example is my Dell PE2850 (on 4.x), in which my 4 port ethernet card > seems to > be assigned irqs 10,14,14,2 in that order sometimes and 16,17,17,2 at > others. > > Who is making those decisions? Is it the BIOS and 4.x is just playing alo= ng? > > Assuming the much maligned "boot interrupt" comes in on irq2, does the OS > have the oportunity to put my 4th port somewhere else? On 4.x it collides > with one of my ether ports but in -current it doesn't > > Linux and -current on teh same box a;;ocate way different irqs, and > they agree about it.. i.e. Linux and -current assign my 4 port card IRQs > 18,19,19,16. > > Do they agree becasue something else has decided it (the bios again?) or > becasue they > use the same algorythm to work it out.. > > Also, if the "boot interrupt" was previously set to 2, is that likely to > have changed in -current? > Am I now going to get clobbered on IRQ16? If yes, is this something > that teh BIOS writers > decided, or something that the Motherboard designers decided? The canonical method for getting this kind of information now (and at least current Linux kernels do this unless forced not to) is via ACPI... And indirectly that really means how the BIOS sets up its tables. I'm still coming up to speed on the current FreeBSD kernel, but I would hope it does the same :) Cheers, Jack From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 23:27:03 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7774416A41F; Tue, 6 Dec 2005 23:27:03 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8ACA443D66; Tue, 6 Dec 2005 23:27:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 2751C2082; Wed, 7 Dec 2005 00:26:53 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 721E32080; Wed, 7 Dec 2005 00:26:52 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 3A19133C1D; Wed, 7 Dec 2005 00:26:52 +0100 (CET) To: Nate Lawson References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Wed, 07 Dec 2005 00:26:51 +0100 In-Reply-To: <4395A265.8080006@root.org> (Nate Lawson's message of "Tue, 06 Dec 2005 06:38:29 -0800") Message-ID: <86d5k9eric.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:27:03 -0000 --=-=-= Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Nate Lawson writes: > I'd prefer to move forward, not backward. When using AC modes, it is > an advantage to be devd-driven. The current implementation is not > right, I agree, but there shouldn't be any actual problem other than > suboptimal performance. Changing the thread to be a select() seems > good. I welcome any patches. You're welcome. powerd is a mess, BTW. I've tried to fix the most blatant mistakes (poor understanding of signal handling), but it basically needs a rewrite. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no --=-=-= Content-Type: text/x-patch Content-Disposition: attachment; filename=powerd.diff Index: usr.sbin/powerd/Makefile =================================================================== RCS file: /home/ncvs/src/usr.sbin/powerd/Makefile,v retrieving revision 1.4 diff -u -r1.4 Makefile --- usr.sbin/powerd/Makefile 19 Oct 2005 04:48:44 -0000 1.4 +++ usr.sbin/powerd/Makefile 6 Dec 2005 23:20:44 -0000 @@ -3,9 +3,12 @@ PROG= powerd MAN= powerd.8 WARNS?= 6 -LDFLAGS+= -lpthread DPADD= ${LIBUTIL} LDADD= -lutil +.if ${MACHINE_ARCH} == "i386" +CFLAGS+=-DUSE_APM +.endif + .include Index: usr.sbin/powerd/powerd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/powerd/powerd.c,v retrieving revision 1.16 diff -u -r1.16 powerd.c --- usr.sbin/powerd/powerd.c 24 Oct 2005 18:34:54 -0000 1.16 +++ usr.sbin/powerd/powerd.c 6 Dec 2005 23:23:11 -0000 @@ -28,19 +28,18 @@ #include __FBSDID("$FreeBSD: src/usr.sbin/powerd/powerd.c,v 1.16 2005/10/24 18:34:54 njl Exp $"); -#include #include #include #include #include #include +#include #include #include #include #include #include -#include #include #include #include @@ -55,17 +54,17 @@ #define DEFAULT_IDLE_PERCENT 90 #define DEFAULT_POLL_INTERVAL 500 /* Poll interval in milliseconds */ -enum modes_t { +typedef enum { MODE_MIN, MODE_ADAPTIVE, MODE_MAX, -}; +} modes_t; -enum power_src_t { +typedef enum { SRC_AC, SRC_BATTERY, SRC_UNKNOWN, -}; +} power_src_t; const char *modes[] = { "AC", @@ -82,10 +81,9 @@ static int read_freqs(int *numfreqs, int **freqs, int **power); static int set_freq(int freq); static void acline_init(void); -static int acline_read(void); +static void acline_read(void); static int devd_init(void); static void devd_close(void); -static void *devd_read(void *arg); static void handle_sigs(int sig); static void parse_mode(char *arg, int *mode, int ch); static void usage(void); @@ -96,19 +94,29 @@ static int levels_mib[4]; static int acline_mib[3]; -/* devd-cached value provided by our thread. */ -static int devd_acline; - /* Configuration */ static int cpu_running_mark; static int cpu_idle_mark; static int poll_ival; static int vflag; -static int apm_fd; -static int devd_pipe; -static pthread_t devd_thread; -static int exit_requested; +static volatile sig_atomic_t exit_requested; +static power_src_t acline_status; +static enum { + ac_none, + ac_acpi_sysctl, + ac_acpi_devd, +#ifdef USE_APM + ac_apm, +#endif +} acline_mode; +#ifdef USE_APM +static int apm_fd = -1; +#endif +static int devd_pipe = -1; + +#define DEVD_RETRY_INTERVAL 60 /* seconds */ +static struct timeval tried_devd; static int read_usage_times(long *idle, long *total) @@ -195,168 +203,132 @@ /* * Try to use ACPI to find the AC line status. If this fails, fall back - * to APM. If nothing succeeds, we'll just run in default mode. If we are - * using ACPI, try opening a pipe to devd to detect AC line events. + * to APM. If nothing succeeds, we'll just run in default mode. */ static void acline_init() { - int acline; size_t len; - apm_fd = -1; - devd_pipe = -1; - len = sizeof(acline); - if (sysctlbyname(ACPIAC, &acline, &len, NULL, 0) == 0) { - len = 3; - if (sysctlnametomib(ACPIAC, acline_mib, &len)) - err(1, "lookup acline"); - - /* Read line status once so that we have an initial value. */ - devd_acline = acline_read(); - - /* - * Try connecting to the devd pipe and start a read thread - * if we succeed. - */ - if ((devd_pipe = devd_init()) >= 0) { - if (pthread_create(&devd_thread, NULL, devd_read, - &devd_pipe)) - err(1, "pthread_create devd thread"); - } else if (vflag) { - warnx( - "unable to connect to devd pipe, using polling mode instead"); - } + len = 3; + if (sysctlnametomib(ACPIAC, acline_mib, &len) == 0) { + acline_mode = ac_acpi_sysctl; + if (vflag) + warnx("using sysctl for AC line status"); +#ifdef __i386__ + } else if ((apm_fd = open(APMDEV, O_RDONLY)) >= 0) { + if (vflag) + warnx("using APM for AC line status"); + acline_mode = ac_apm; +#endif } else { - apm_fd = open(APMDEV, O_RDONLY); - if (apm_fd == -1) - warnx( - "cannot read AC line status, using default settings"); + warnx("unable to determine AC line status"); + acline_mode = ac_none; } } -static int -acline_read() +static void +acline_read(void) { - int acline; - size_t len; -#ifdef __i386__ - struct apm_info info; -#endif - - acline = SRC_UNKNOWN; - len = sizeof(acline); + if (acline_mode == ac_acpi_devd) { + char buf[DEVCTL_MAXBUF], *ptr; + ssize_t rlen; + int notify; - /* - * Get state from our devd thread, the ACPI sysctl, or APM. We - * prefer sources in this order. - */ - if (devd_pipe >= 0) - acline = devd_acline; - else if (sysctl(acline_mib, 3, &acline, &len, NULL, 0) == 0) - acline = acline ? SRC_AC : SRC_BATTERY; -#ifdef __i386__ - else if (apm_fd != -1 && ioctl(apm_fd, APMIO_GETINFO, &info) == 0) - acline = info.ai_acline ? SRC_AC : SRC_BATTERY; + rlen = read(devd_pipe, buf, sizeof(buf)); + if (rlen == 0 || (rlen < 0 && errno != EWOULDBLOCK)) { + if (vflag) + warnx("lost devd connection, switching to sysctl"); + devd_close(); + acline_mode = ac_acpi_sysctl; + /* FALLTHROUGH */ + } + if (rlen > 0 && + (ptr = strstr(buf, "system=ACPI")) != NULL && + (ptr = strstr(ptr, "subsystem=ACAD")) != NULL && + (ptr = strstr(ptr, "notify=")) != NULL && + sscanf(ptr, "notify=%x", ¬ify) == 1) + acline_status = (notify ? SRC_AC : SRC_BATTERY); + } + if (acline_mode == ac_acpi_sysctl) { + int acline; + size_t len; + + len = sizeof(acline); + if (sysctl(acline_mib, 3, &acline, &len, NULL, 0) == 0) + acline_status = (acline ? SRC_AC : SRC_BATTERY); + else + acline_status = SRC_UNKNOWN; + } +#ifdef USE_APM + if (acline_mode == ac_apm) { + struct apm_info info; + + if (ioctl(apm_fd, APMIO_GETINFO, &info) == 0) { + acline_status = (info.ai_acline ? SRC_AC : SRC_BATTERY); + } else { + close(apm_fd); + apm_fd = -1; + acline_mode = ac_none; + acline_status = SRC_UNKNOWN; + } + } #endif - - return (acline); + /* try to (re)connect to devd */ + if (acline_mode == ac_acpi_sysctl) { + struct timeval now; + + gettimeofday(&now, NULL); + if (now.tv_sec > tried_devd.tv_sec + DEVD_RETRY_INTERVAL) { + if (devd_init() >= 0) { + if (vflag) + warnx("using devd for AC line status"); + acline_mode = ac_acpi_devd; + } + tried_devd = now; + } + } } static int devd_init(void) { struct sockaddr_un devd_addr; - int devd_sock; bzero(&devd_addr, sizeof(devd_addr)); - if ((devd_sock = socket(PF_LOCAL, SOCK_STREAM, 0)) < 0) { + if ((devd_pipe = socket(PF_LOCAL, SOCK_STREAM, 0)) < 0) { if (vflag) - warn("failed to create devd socket"); + warn("%s(): socket()", __func__); return (-1); } devd_addr.sun_family = PF_LOCAL; strlcpy(devd_addr.sun_path, DEVDPIPE, sizeof(devd_addr.sun_path)); - if (connect(devd_sock, (struct sockaddr *)&devd_addr, + if (connect(devd_pipe, (struct sockaddr *)&devd_addr, sizeof(devd_addr)) == -1) { - close(devd_sock); + if (vflag) + warn("%s(): connect()", __func__); + close(devd_pipe); + devd_pipe = -1; return (-1); } - return (devd_sock); + if (fcntl(devd_pipe, F_SETFL, O_NONBLOCK) == -1) { + if (vflag) + warn("%s(): fcntl()", __func__); + close(devd_pipe); + return (-1); + } + + return (devd_pipe); } static void devd_close(void) { - if (devd_pipe < 0) - return; - - pthread_kill(devd_thread, SIGTERM); close(devd_pipe); -} - -/* - * This loop runs as a separate thread. It reads events from devd, but - * spends most of its time blocked in select(2). - */ -static void * -devd_read(void *arg) -{ - char buf[DEVCTL_MAXBUF], *ptr; - fd_set fdset; - int fd, notify, rlen; - - fd = *(int *)arg; - notify = -1; - FD_ZERO(&fdset); - while (!exit_requested) { - FD_SET(fd, &fdset); - if (select(fd + 1, &fdset, NULL, NULL, NULL) < 0) - break; - if (!FD_ISSET(fd, &fdset)) - continue; - - /* Read the notify string, devd NULL-terminates it. */ - rlen = read(fd, buf, sizeof(buf)); - if (rlen <= 0) { - close(devd_pipe); - devd_pipe = -1; - if (vflag) - warnx( - "devd disappeared, downgrading to polling mode"); - - /* - * Keep trying to reconnect to devd but sleep in - * between to avoid wasting CPU cycles. - */ - while (!exit_requested && (fd = devd_init()) < 0) - sleep(300); - - if (fd >= 0) { - devd_pipe = fd; - if (vflag) - warnx( - "devd came back, upgrading to event mode"); - } - continue; - } - - /* Loosely match the notify string. */ - if ((ptr = strstr(buf, "system=ACPI")) != NULL && - (ptr = strstr(ptr, "subsystem=ACAD")) != NULL && - (ptr = strstr(ptr, "notify=")) != NULL) { - if (sscanf(ptr, "notify=%x", ¬ify) != 1) { - warnx("bad devd notify string"); - continue; - } - devd_acline = notify ? SRC_AC : SRC_BATTERY; - } - } - - return (NULL); + devd_pipe = -1; } static void @@ -392,10 +364,13 @@ int main(int argc, char * argv[]) { + struct timeval timeout; + fd_set fdset; + int nfds; struct pidfh *pfh = NULL; const char *pidfile = NULL; long idle, total; - int acline, curfreq, *freqs, i, *mwatts, numfreqs; + int curfreq, *freqs, i, *mwatts, numfreqs; int ch, mode, mode_ac, mode_battery, mode_none; uint64_t mjoules_used; size_t len; @@ -407,7 +382,6 @@ poll_ival = DEFAULT_POLL_INTERVAL; mjoules_used = 0; vflag = 0; - apm_fd = -1; /* User must be root to control frequencies. */ if (geteuid() != 0) @@ -479,15 +453,6 @@ if (read_freqs(&numfreqs, &freqs, &mwatts)) err(1, "error reading supported CPU frequencies"); - /* - * Exit cleanly on signals; devd may send a SIGPIPE if it dies. We - * do this before acline_init() since it may create a thread and we - * want it to inherit our signal mask. - */ - signal(SIGINT, handle_sigs); - signal(SIGTERM, handle_sigs); - signal(SIGPIPE, SIG_IGN); - /* Run in the background unless in verbose mode. */ if (!vflag) { pid_t otherpid; @@ -512,10 +477,24 @@ /* Decide whether to use ACPI or APM to read the AC line status. */ acline_init(); + /* + * Exit cleanly on signals. + */ + signal(SIGINT, handle_sigs); + signal(SIGTERM, handle_sigs); + /* Main loop. */ for (;;) { - /* Check status every few milliseconds. */ - usleep(poll_ival); + FD_ZERO(&fdset); + if (devd_pipe >= 0) { + FD_SET(devd_pipe, &fdset); + nfds = devd_pipe + 1; + } else { + nfds = 0; + } + timeout.tv_sec = poll_ival / 1000000; + timeout.tv_usec = poll_ival % 1000000; + select(nfds, &fdset, NULL, &fdset, &timeout); /* If the user requested we quit, print some statistics. */ if (exit_requested) { @@ -527,8 +506,8 @@ } /* Read the current AC status and record the mode. */ - acline = acline_read(); - switch (acline) { + acline_read(); + switch (acline_status) { case SRC_AC: mode = mode_ac; break; @@ -539,7 +518,7 @@ mode = mode_none; break; default: - errx(1, "invalid AC line status %d", acline); + errx(1, "invalid AC line status %d", acline_status); } /* Read the current frequency. */ @@ -568,7 +547,8 @@ if (vflag) { printf("now operating on %s power; " "changing frequency to %d MHz\n", - modes[acline], freqs[numfreqs - 1]); + modes[acline_status], + freqs[numfreqs - 1]); } if (set_freq(freqs[numfreqs - 1]) != 0) { warn("error setting CPU freq %d", @@ -585,7 +565,8 @@ if (vflag) { printf("now operating on %s power; " "changing frequency to %d MHz\n", - modes[acline], freqs[0]); + modes[acline_status], + freqs[0]); } if (set_freq(freqs[0]) != 0) { warn("error setting CPU freq %d", --=-=-=-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 23:34:14 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6711116A420; Tue, 6 Dec 2005 23:34:14 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0DC9143D72; Tue, 6 Dec 2005 23:34:08 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id CF3F42086; Wed, 7 Dec 2005 00:34:00 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id BE39C2085; Wed, 7 Dec 2005 00:34:00 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id 9B59F33C1D; Wed, 7 Dec 2005 00:34:00 +0100 (CET) To: Nate Lawson References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> <86d5k9eric.fsf@xps.des.no> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Wed, 07 Dec 2005 00:34:00 +0100 In-Reply-To: <86d5k9eric.fsf@xps.des.no> (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav's?= message of "Wed, 07 Dec 2005 00:26:51 +0100") Message-ID: <868xuxer6f.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:34:14 -0000 des@des.no (Dag-Erling Sm=F8rgrav) writes: > powerd is a mess, BTW. I've tried to fix the most blatant mistakes > (poor understanding of signal handling), but it basically needs a > rewrite. The signal handling code can probably be removed entirely. Its only purpose is to catch SIGINT / SIGTERM so powerd can print some stats before exiting, but said stats are meaningless because: a) they assume that the main loop runs once every poll_interval, when in fact the time between two successive iterations can range from microseconds (interrupted usleep() / select()) to hours or even days (suspended laptop). b) even assuming that a) does not apply and that ACPI provides accurate values, it still only reports power consumed by the CPU, not by peripherals or the LCD backlight. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 23:55:09 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B58C16A41F; Tue, 6 Dec 2005 23:55:09 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADD0743D5A; Tue, 6 Dec 2005 23:55:08 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB6Nt7et077968; Tue, 6 Dec 2005 18:55:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB6Nt7XW066156; Tue, 6 Dec 2005 18:55:07 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2147D7302F; Tue, 6 Dec 2005 18:55:06 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051206235506.2147D7302F@freebsd-current.sentex.ca> Date: Tue, 6 Dec 2005 18:55:06 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:55:09 -0000 TB --- 2005-12-06 22:16:45 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-06 22:16:45 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-06 22:16:45 - cleaning the object tree TB --- 2005-12-06 22:17:29 - checking out the source tree TB --- 2005-12-06 22:17:29 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-06 22:17:29 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-06 22:23:34 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-06 22:23:34 - cd /src TB --- 2005-12-06 22:23:34 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-06 23:54:37 - generating LINT kernel config TB --- 2005-12-06 23:54:37 - cd /src/sys/amd64/conf TB --- 2005-12-06 23:54:37 - /usr/bin/make -B LINT TB --- 2005-12-06 23:54:37 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-06 23:54:37 - cd /src TB --- 2005-12-06 23:54:37 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Dec 6 23:54:37 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] awk -f /src/sys/tools/usbdevs2h.awk /src/sys/dev/usb/usbdevs -d rpcgen -h -C /src/sys/netatm/spans/spans_xdr.x | grep -v rpc/rpc.h > spans_xdr.h rpcgen -c -C /src/sys/netatm/spans/spans_xdr.x | grep -v rpc/rpc.h > spans_xdr.c cc -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -c /src/sys/amd64/linux32/linux32_genassym.c sh /src/sys/kern/genassym.sh linux32_genassym.o > linux32_assym.h cc -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ipfilter -I/src/sys/contrib/pf -I/src/sys/contrib/dev/ath/freebsd -I/src/sys/contrib/ngatm -I/src/sys/dev/twa -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -c /src/sys/compat/ia32/ia32_genassym.c In file included from /src/sys/compat/ia32/ia32_genassym.c:11: /src/sys/compat/ia32/ia32_signal.h:158: error: syntax error before '.' token *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-06 23:55:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-06 23:55:06 - ERROR: failed to build lint kernel TB --- 2005-12-06 23:55:06 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Dec 6 23:59:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 758FE16A41F for ; Tue, 6 Dec 2005 23:59:36 +0000 (GMT) (envelope-from julian@elischer.org) Received: from a50.ironport.com (a50.ironport.com [63.251.108.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4549343D5A for ; Tue, 6 Dec 2005 23:59:35 +0000 (GMT) (envelope-from julian@elischer.org) Received: from unknown (HELO [10.251.17.229]) ([10.251.17.229]) by a50.ironport.com with ESMTP; 06 Dec 2005 15:59:34 -0800 X-IronPort-Anti-Spam-Filtered: true Message-ID: <439625E6.1000104@elischer.org> Date: Tue, 06 Dec 2005 15:59:34 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.11) Gecko/20050727 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jack Vogel References: <43961758.4020407@elischer.org> <2a41acea0512061513l10695474yc63df81c5c92fe8f@mail.gmail.com> In-Reply-To: <2a41acea0512061513l10695474yc63df81c5c92fe8f@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2005 23:59:36 -0000 Jack Vogel wrote: >On 12/6/05, Julian Elischer wrote: > > >>In short words for the likes of me, >>Can someone give a quicj roundup on PCI routing in 4.x and -current. >> >>Specifically: >> >>How much is set up by the BIOS and how much is set up by the OS (4.x and >>-current). >> >>How much of my fondly held knowledge of the old hardware PICS (where >>an interrupt corresponded to an interrupt line) is now out of date? >> >>In this world of multiple PCI to PCI bridges, how much latitude doe the >>OS have in >>deciding where an interrupt turns up? >>(in 4.x and -current) >> >>An example is my Dell PE2850 (on 4.x), in which my 4 port ethernet card >>seems to >>be assigned irqs 10,14,14,2 in that order sometimes and 16,17,17,2 at >>others. >> >>Who is making those decisions? Is it the BIOS and 4.x is just playing along? >> >>Assuming the much maligned "boot interrupt" comes in on irq2, does the OS >>have the oportunity to put my 4th port somewhere else? On 4.x it collides >>with one of my ether ports but in -current it doesn't >> >>Linux and -current on teh same box a;;ocate way different irqs, and >>they agree about it.. i.e. Linux and -current assign my 4 port card IRQs >>18,19,19,16. >> >>Do they agree becasue something else has decided it (the bios again?) or >>becasue they >>use the same algorythm to work it out.. >> >>Also, if the "boot interrupt" was previously set to 2, is that likely to >>have changed in -current? >>Am I now going to get clobbered on IRQ16? If yes, is this something >>that teh BIOS writers >>decided, or something that the Motherboard designers decided? >> >> > >The canonical method for getting this kind of information now (and at >least current Linux kernels do this unless forced not to) is via ACPI... >And indirectly that really means how the BIOS sets up its tables. > >I'm still coming up to speed on the current FreeBSD kernel, but I >would hope it does the same :) > > so, for your next trick can you explain acpi and the "boot interrupt" :-) p.s. got info on the dewey beach card yet? ;-) (That's what's causing me this pain :-) >Cheers, > >Jack > > From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 01:19:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 869F316A41F for ; Wed, 7 Dec 2005 01:19:02 +0000 (GMT) (envelope-from vovkasm@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96C6F43D68 for ; Wed, 7 Dec 2005 01:19:01 +0000 (GMT) (envelope-from vovkasm@gmail.com) Received: by wproxy.gmail.com with SMTP id 58so820792wri for ; Tue, 06 Dec 2005 17:19:00 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HeOFIAXiA0tYl6F1G34HHioxqx8aD1TVPIuhkvmbh061beh6R8DXzhVHOz0CkvknoWD3bNXn/d0EgWvWZFWO1yrkQ4WyxiA6r1JJaEqYxPymER2mizpPwZXGIsE1rSONCxlbOX1Cksbof7pHiMSqjjNNv6cFUY/8RluJ+0uH6ho= Received: by 10.54.125.13 with SMTP id x13mr2477934wrc; Tue, 06 Dec 2005 17:18:57 -0800 (PST) Received: by 10.54.157.12 with HTTP; Tue, 6 Dec 2005 17:18:56 -0800 (PST) Message-ID: Date: Wed, 7 Dec 2005 04:18:56 +0300 From: Vladimir Timofeev To: Artemiev Igor In-Reply-To: <20051206093020.691e1483.ai@bmc.brk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051206093020.691e1483.ai@bmc.brk.ru> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 01:19:02 -0000 I has applied this patch to my RELENG_6 and it seems to work (Abit NF7 motherboard) dmesg: amdpm0: port 0xe400-0xe41f,0x5000-0x501f irq 11 at device 1.1 on pci0 smbus0: on amdpm0 smb0: on smbus0 amdpmsub0: on amdpm0 smbus1: on amdpmsub0 smb1: on smbus1 But testing: # mbmon -S -d SMBus[NVidia nForce2] found, but No HWM available on it!! InitMBInfo: Unknown error: 0 # mbmon Temp.=3D 26.0, 42.5, 0.0; Rot.=3D 2481, 0, 0 Vcore =3D 1.63, 2.64; Volt. =3D 3.30, 5.03, 12.16, -11.87, -5.05 What additional tests can I do? 2005/12/6, Artemiev Igor : > > > I add pseudo-device amdpmsub because nForce2 have two SMBus > interfaces. Patch here: > > http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff > > dmesg output: > > amdpm0: port > 0xdc00-0xdc1f,0x5000-0x501f,0x5500 -0x551f irq 5 at device 1.1 on pci0 > smbus0: on amdpm0 > smb0: on smbus0 > amdpmsub0: on amdpm0 > smbus1: on amdpmsub0 > smb1: on smbus1 > > I`ve tested it with xmbmon and all works fine. > > -- > iprefetch ai > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 03:00:24 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D5FC216A426 for ; Wed, 7 Dec 2005 03:00:24 +0000 (GMT) (envelope-from dandee@volny.cz) Received: from pipa.profix.cz (ruprt.hosting4u.cz [82.208.25.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id B280443D6A for ; Wed, 7 Dec 2005 03:00:21 +0000 (GMT) (envelope-from dandee@volny.cz) Received: from localhost (localhost [127.0.0.1]) by pipa.profix.cz (Postfix) with ESMTP id B1C4C4E706 for ; Wed, 7 Dec 2005 04:00:21 +0100 (CET) Received: from pipa.profix.cz ([127.0.0.1]) by localhost (pipa [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 18619-07 for ; Wed, 7 Dec 2005 04:00:21 +0100 (CET) Received: from gandalf (unknown [80.95.121.105]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) by pipa.profix.cz (Postfix) with ESMTP id 65A9A4E705 for ; Wed, 7 Dec 2005 04:00:21 +0100 (CET) From: "Stay d" To: Date: Wed, 7 Dec 2005 04:00:15 +0100 Message-ID: <003401c5fada$5b504950$6508280a@tocnet28.jspoj.czf> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 11 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcX62ljm3SxqPzDYR/KO67v1fHqwdQ== X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at profix.cz X-Mailman-Approved-At: Wed, 07 Dec 2005 03:13:52 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: named problems and panic on fatal trap12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dandee@volny.cz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 03:00:25 -0000 Hi all, today I looked over messages on one of my router and I found problems about named server and finished with panic, after that it is not repeating ... up to know. I could not submit or say more information, but I have a complete crash dump. Here is problem: ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- --- named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1115: unexpected error: named[508]: internal_send: 10.40.0.4#54377: Bad address named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 : unexpected error: named[508]: unable to convert errno to isc_result: 14: Bad address named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1115: unexpected error: named[508]: internal_send: 10.40.0.4#59133: Bad address named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 : unexpected error: named[508]: unable to convert errno to isc_result: 14: Bad address named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1115: unexpected error: named[508]: internal_send: 10.40.0.4#60559: Bad address named[508]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/errno2result.c:109 : unexpected error: named[508]: unable to convert errno to isc_result: 14: Bad address Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x20:0xc07a9532 stack pointer = 0x28:0xcc9d9bd8 frame pointer = 0x28:0xcc9d9bfc code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 27 (swi1: net) trap number = 12 panic: page fault Uptime: 19m27s Dumping 255 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 255MB (65276 pages) 240 224 208 192 176 160 144 128 112 96 80 64 48 32 16 ---------------------------------------------------------------------------- ---------------------------------------------------------------------------- --- Dan _____ avast! Antivirus : Odchozi zprava cista. Virova databaze (VPS): 0549-2, 06.12.2005 Testovano: 7.12.2005 4:00:15 avast! - copyright (c) 1988-2005 ALWIL Software. From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 03:34:21 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D267216A41F for ; Wed, 7 Dec 2005 03:34:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D72343D55 for ; Wed, 7 Dec 2005 03:34:21 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id jB73YJAT010230 for ; Tue, 6 Dec 2005 19:34:19 -0800 (PST) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id jB73YJ54010229 for freebsd-current@freebsd.org; Tue, 6 Dec 2005 19:34:19 -0800 (PST) (envelope-from obrien) Date: Tue, 6 Dec 2005 19:34:19 -0800 From: "David O'Brien" To: freebsd-current@freebsd.org Message-ID: <20051207033419.GA10185@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 7.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.11 Subject: config(8) VERSREQ checking broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 03:34:21 -0000 sys/amd64/conf# config -V 600002 sys/amd/conf# config GENERIC Specify machine type, e.g. ``machine i386'' sys/amd/conf# grep VERSREQ ../../conf/Makefile.amd64 %VERSREQ= 600004 Shouldn't I be getting the usual error message that my config version isn't new enough to support building a kernel from these sources? -- -- David (obrien@FreeBSD.org) Q: Because it reverses the logical flow of conversation. A: Why is top-posting (putting a reply at the top of the message) frowned upon? From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 03:53:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 375C316A41F; Wed, 7 Dec 2005 03:53:45 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 23EE343D58; Wed, 7 Dec 2005 03:53:43 +0000 (GMT) (envelope-from nate@root.org) Received: from [172.16.0.224] (fi01-84CBdd.tokyo.flets.isao.net [211.132.203.221]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB73rYdu007045 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 6 Dec 2005 19:53:35 -0800 Message-ID: <43965CB2.5000707@root.org> Date: Wed, 07 Dec 2005 12:53:22 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> <86d5k9eric.fsf@xps.des.no> <868xuxer6f.fsf@xps.des.no> In-Reply-To: <868xuxer6f.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 03:53:45 -0000 Dag-Erling Smørgrav wrote: > des@des.no (Dag-Erling Smørgrav) writes: > >>powerd is a mess, BTW. I've tried to fix the most blatant mistakes >>(poor understanding of signal handling), but it basically needs a >>rewrite. Thanks for the patch. I'll review it later today and try to commit it. > The signal handling code can probably be removed entirely. Its only > purpose is to catch SIGINT / SIGTERM so powerd can print some stats > before exiting, but said stats are meaningless because: > > a) they assume that the main loop runs once every poll_interval, when > in fact the time between two successive iterations can range from > microseconds (interrupted usleep() / select()) to hours or even > days (suspended laptop). > > b) even assuming that a) does not apply and that ACPI provides > accurate values, it still only reports power consumed by the CPU, > not by peripherals or the LCD backlight. Both a) and b) are not applicable. The goal of those stats is to assist with profiling various algorithms. You can compare the total power consumed over the same interval and workload for different algorithms to decide which is best. Since the stats are only printed in verbose mode (and it doesn't daemonize in that mode), testers should know that suspending/resuming would cause the number to be inaccurate, it's only an estimate, and that it only pertains to CPU power. I'll make sure the signal handling is cleaned up when I commit it. -- Nate From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 05:40:36 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20B4616A41F for ; Wed, 7 Dec 2005 05:40:36 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09BF843D5A for ; Wed, 7 Dec 2005 05:40:34 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3297026 for multiple; Wed, 07 Dec 2005 00:41:56 -0500 Received: from [192.168.0.15] (osx.baldwin.cx [192.168.0.15]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB75eSMW053661; Wed, 7 Dec 2005 00:40:28 -0500 (EST) (envelope-from jhb@FreeBSD.org) In-Reply-To: <43961758.4020407@elischer.org> References: <43961758.4020407@elischer.org> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> Content-Transfer-Encoding: 7bit From: John Baldwin Date: Wed, 7 Dec 2005 00:40:19 -0500 To: Julian Elischer X-Mailer: Apple Mail (2.746.2) X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: current@FreeBSD.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 05:40:36 -0000 On Dec 6, 2005, at 5:57 PM, Julian Elischer wrote: > In short words for the likes of me, > Can someone give a quicj roundup on PCI routing in 4.x and -current. My, what a set of questions. :) I'll do my best, but this will probably be a long and perhaps wandering e-mail. First off, interrupts for PCI devices are roughly split up into two categories (currently): INTx interrupt lines and MSI interrupts. MSI is relatively new and I won't cover it much here. No versions of FreeBSD currently support MSI either (though it's on my todo list), so I'll limit this discussion to INTx interrupts. For INTx interrupts, each PCI device (or slot) has 4 interrupt lines: INTA, INTB, INTC, and INTD. Thus, you can describe any individual PCI interrupt as a tuple of (bus, slot, pin). For example, device 4's INTA pin on pci bus 0 would be (0, 4, INTA). Each PCI function is allowed to have one INTx interrupt. The bus and slot come from the location of that function in the PCI hierarchy, and the pin comes from the intpin PCI config register. PCI doesn't define beyond the INTx pin how an interrupt is delivered to the CPU, etc. That is all a property of the architecture, chipset, etc. On x86, there are two disparate sets of hardware for managing interrupt signals. The first is the pair of 8259A interrupt controllers found on all PC-AT compatible machines. The second set of hardware is the APIC subsystem as it were. Each processor contains a local APIC that can receive messages from other APICs and send messages to other local APICs. In addition to the local APICs, the chipset contains 1 or more I/O APICs. Each I/O APIC contains anywhere from 4 to 32 individual interrupt pins. Common numbers are 4 (somewhat rare), 16, 24, and 32. Conceptually, on x86 a given interrupt source can be described by the tuple (pic, pin). Simply put, PCI interrupt routing is the mapping of (bus, slot, pin) PCI interrupt tuples to (pic, pin) x86 interrupt tuples. Now, before delving deeper into the specifics of routing on x86, let me digress about IRQs on FreeBSD. Basically, an IRQ value is a cookie useful for binding a device interrupt (such as a PCI (bus, slot, pin) tuple or an ISA IRQ) to a x86 interrupt tuple (pic, pin). BIOSes don't operate with APICs at all, at least not for handling device interrupts. Thus, they all use a simple mapping where IRQs 0-7 correspond to pins 0-7 on the master 8259A, and IRQs 8-15 map to pins 0-7 on the slave 8259A. All versions of FreeBSD use the same mapping for IRQ cookie values when using the 8259As to route interrupts. For the APIC case the mapping of IRQ cookies to (pic, pin) tuples is slightly more complicated. First, the simple case. FreeBSD 5.2 and later follow the ACPI model (even when not using ACPI) where the IRQs 0-n correspond to the pins 0-n of the first I/O APIC, IRQs n+1 to (n+1)+m map to pins 0 to m of the second I/O APIC, etc. (There is one possible exception with ACPI I'll cover later.) FreeBSD 4.x is more complicated. The reason is that due to cpl and spl interrupt masks being 32-bit integers with 8 bits set aside for software interrupts (SWIs), cpl only has 24 bits available for hardware interrupts. Therefore, FreeBSD <= 5.2 is limited to IRQ values 0-23 and can't use the simple (and intuitive) model that FreeBSD 5.2+ and ACPI use. What FreeBSD 4.x does is to map the ISA interrupts attached to the first I/O APIC to IRQs 0, 1, and 3-15. This just leaves IRQs 2 and 16-23 available for all the other APIC interrupt pins. As each PCI device registers an interrupt handler for a specific (apic, pin) tuple, that x86 interrupt is mapped to one of the last set of IRQs. If all of them have been used already, then the kernel starts assigning multiple (apic, pin) tuples to the same IRQ resulting in interrupts being shared in software because of the cpl limitation even though they aren't shared in hardware. This is why your IRQ values are different on 4.x than on FreeBSD 5.2+ and Linux which use the ACPI global interrupt number model. Now, back to how routing of PCI device interrupts on x86 actually works. I'll cover non-ACPI first. There are two cases to consider. First, the easy case is that a PCI device interrupt (bus, tuple, pin) is wired directly to an individual pin on a pic. This is often how interrupts are wired when using APICs. If you look at the mptable output and look at the interrupt section, this is fairly obvious as you will see entries that map the interrupt for a given pci bus, slot and pin to a given apic id and intpin on that apic. Thus, there is the mapping for (bus, slot, pin) to (pic, pin) directly. The way interrupt routing is implemented in this case is that when we go to route an interrupt for a given PCI device, we search the mptable for a matching entry. We then look up the associated apic via its apic id, ask it for the specified pin, and then ask that pin for its IRQ (via the pic_vector method of the ioapic interrupt source object that describes the specific pin). When nexus(4) does bus_setup_intr(), it passes that IRQ to the x86 intr_machdep code which uses the IRQ as an index into its interrupt source array and ends up with the interrupt source object for the (apic, pin) tuple being used. (Thus, IRQs are just a cookie that is the index into the global array of interrupt sources on x86.) Note that interrupts routed this way are hardwired into the motherboard design. There's no chance for the OS to change which (pic, pin) a PCI device interrupt is hooked up to. For the non-APIC case (non-ACPI still), PCI device interrupts are usually wired up to a pin on a programmable interrupt router. Each of these pins is called a pci link device. Multiple PCI device interrupts may be wired up to the same link device, and systems typically have anywhere from 4 to 8 (sometimes even more) link devices. Each link device can be independently routed to a given (pic, pin) and it is limited to a fixed set of possible IRQs. If multiple link devices are routed to the same IRQ, then all of the devices attached to both link devices end up sharing the same IRQ (and thus the same ithread, etc.). Because the link devices are independently steerable, this is the one way in which the OS has limited flexibility in routing interrupts. However, the way it works is that you route the link devices, not individual PCI device interrupts. The table the BIOS provides with the information about the link devices is called the $PIR (since that's the 4 byte signature you search for in RAM to find it). You can see it during a verbose boot dmesg. It is a table that maps a given (bus, slot, intpin) PCI tuple to a link index. Each entry also has a bitmask of the valid ISA IRQs ($PIR only allows for the 16 ISA IRQs) that the specified link index can be routed to. Thus, the way that interrupt routing works with $PIR is that when a PCI interrupt is routed, you search the table for a matching entry to get a link index. The $PIR code in sys/i386/pci/pci_pir.c basically has a list of link objects that maintain state about each link. The code finds the data associated with the link index and sees if it has an IRQ routed already. If so, that's the IRQ that that PCI device interrupt is assigned to. If an IRQ isn't routed already, then it has to use an algorithm to pick one, make a BIOS call to route the link to the chosen IRQ, and then assign the PCI device interrupt to that IRQ. Now that you understand that, ACPI routing can make some sense. The way that ACPI routing works is that each PCI bus in the ACPI namespace has a _PRT method that returns a table of routing entries. Each entry contains the slot and intpin that it handles (so that you can build the (bus, slot, intpin) PCI tuple (bus comes from the PCI bus device _PRT is a child of, in FreeBSD the _PRT is actually a child of the pcib(4) device that is the bridge that is the parent of the PCI bus, but I digress)) as well as a reference to a link device in the ACPI namespace and a source index. If the link device reference is empty or NULL, then the interrupt is a hard-wired interrupt such as the ones used with MP Table routing, and the source index is the global interrupt number (==IRQ) that you use for this interrupt and you are done. If the link device reference isn't empty, then it is the name of a ACPI device object that manages a single pci link device. Example names include \_SB_.PCI0.LPC0.LNKA. Each link device object includes methods to query which IRQ it is currently routed to (though in practice this is unreliable), get the list of possible IRQs, disable the link device altogether, and route the link device to a specified IRQ. This is similar to the link objects we have in the $PIR code except that these end up being full blown devices on the ACPI side. ACPI adds another twist in that the BIOS is free to use link devices with APICs (MP Table has no way of handling that), and in fact in practice there are some nvidia chipsets for amd64 that do route some PCI device interrupts to link devices that in APIC mode can be routed to any of the IRQs 20-23. Now some of the minor trivia and exceptions. On the first I/O APIC, IRQ0 is generally routed to intpin 2, not intpin 0 (though many motherboards don't actually hook up the IRQ0 output from the ISA timer to intpin 2 but do claim to do so in the MP Table and MADT). Instead intpin 0 is a special ExtINT pin that listens to the 8259As and can forward interrupts from the 8259As to one or more CPUs. This is what "mixed mode" is, and on FreeBSD 4.x, if we discover via a test that the motherboard did not wire IRQ0 up to intpin 2, we use mixed mode to deliver it via the 8259A bounced through the ExtINT pin 0 on the first I/O APIC. Blech. Also, for ACPI, the SCI is generally tied to IRQ 9, however, the SCI may be routed to another intpin in APIC mode. Rather than change the IRQ value in the FADT (or whichever table the SCI INT is in), ACPI will include an entry in the MADT that maps IRQ 9 to some other intpin such as IRQ 13 or IRQ 20. If the new intpin is not an ISA IRQ (> 15) we use a backdoor to override the IRQ ACPI uses. If the new intpin is an ISA IRQ though, we actually rename the destination IRQ (such as IRQ 13 on one of my boxes) to IRQ 9, and the original IRQ 9 becomes a "dead" interrupt pin with no IRQ associated with it. Note that except for a few rare and very old SMP boxes, no FreeBSD x86 machine has an IRQ 2. Another odd case is that some very old SMP boxes did not route PCI device interrupts to the APICs at all. Instead, they routed the outputs of the link devices to the pins on the first I/O APIC corresponding to the same IRQ as on the 8259A (the I/O APIC only had 16 pins). Thus, on these boxes, PCI interrupts are still routed via link devices via $PIR, and end up triggering IRQ X via intpin X on the first I/O APIC. One final twist. If a PCI bus behind a PCI-PCI bridge is not listed in a BIOS table ($PIR or MP Table) or does not have a _PRT in ACPI, the interrupts are routed by applying the swizzle defined in the PCI standard to route the interrupt via one of the four INTx pins on the PCI-PCI bridge's parent PCI bus. The standard defines this behavior for add-in cards, but some built in busses do this as well. (I've seen several AGP busses that actually use this method to route the VGA IRQ). > Also, if the "boot interrupt" was previously set to 2, is that > likely to have changed in -current? > Am I now going to get clobbered on IRQ16? If yes, is this > something that teh BIOS writers > decided, or something that the Motherboard designers decided? The "boot interrupt" issue on some of the PXH's used for PCI-X and PCI-e host bridges is an unpleasant mess. I think it comes from Intel assuming all the world is windows (imagine that) and ignoring standards (such as MP Table and ACPI) that it helps to author. (Yay Intel!) The issue there is that the PXH's include a dedicated I/O APIC for each of the two busses the PXH serves, and the PCI device interrupts are routed to intpins on those APICs. To handle the non- APIC case, the PXH's forward any device interrupts to the INTx pins on the parent side of the PCI-PCI bridge if the APIC is disabled. The problem is that Intel chose a hack to figure out if the APIC was disabled and that hack interacts badly with FreeBSD. Basically, if the individual intpin is masked in the APIC, the PXH assumes you aren't using the APIC to handle interrupts and so it forwards the interrupt to the INTx pin on its bridge's parent side. The problem is that after an interrupt comes in on 4.x and later, we mask the interrupt in the APIC until we have run the interrupt handler. The reason is that PCI interrupts are level triggered, so they won't "shut up" until the ISR has run and pacified the PCI device. 4.x masks the interrupt because it wants to not run ISRs with all interrupts disabled, but at the same cpl that the interrupt was registered at so that higher priority interrupts can still preempt an ISR. 5.x and later need to mask the interrupt so that the processor doesn't have to keep interrupts disabled until the ithread finishes. Trying to do that would become complicated and quite painful since it would also mean deferring the EOI to the lapic (which has to happen on the same CPU that received the interrupt) and has other nastiness since ithreads can block on locks, etc. Other OS's that use ithreads such as BSD/OS and probably Solaris/x86 and Darwin/x86 probably have the same issue. The sucky part is that Intel didn't have to do this gross hack. ACPI requires that the OS call a method _PIC if it wants to use APIC mode, and the _PIC method is free to write to registers, PCI config space, etc., so Intel could have provided a register to specify if the PXH's APIC was being used or not and included the code to manage that in _PIC in their sample BIOS. But, they didn't. One possible workaround for this issue would be to provide a hacked PCI-PCI bridge driver for the PXH's that hacked the PCI interrupt routing such that the PCI device interrupts for child devices didn't use the APICs in the PXH at all, but used the IRQs that get aliased to (such as IRQ16 on 5.2+). Getting that to work on 4.x might be quite painful since 4.x PCI interrupt routing code is rather gross and hacky already. Hopefully this at least answers some questions and gives a good overview of what PCI interrupt routing is and how it works, etc. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 06:16:55 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 616D816A41F for ; Wed, 7 Dec 2005 06:16:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5112643D5F for ; Wed, 7 Dec 2005 06:16:54 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jB76GiB8020773; Tue, 6 Dec 2005 23:16:44 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 06 Dec 2005 23:16:44 -0700 (MST) Message-Id: <20051206.231644.34762139.imp@bsdimp.com> To: julian@elischer.org From: "M. Warner Losh" In-Reply-To: <43961758.4020407@elischer.org> References: <43961758.4020407@elischer.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Tue, 06 Dec 2005 23:16:44 -0700 (MST) Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 06:16:55 -0000 In message: <43961758.4020407@elischer.org> Julian Elischer writes: : How much is set up by the BIOS and how much is set up by the OS (4.x and : -current). On 4.x, the BIOS (PCI BIOS) is called to route interrupts from the PIR table when such a table exists. On current, ACPI routines are called (if acpi is enabled), with a fallback to the PIR. Both use the MPTABLE when an APIC i in voled. : How much of my fondly held knowledge of the old hardware PICS (where : an interrupt corresponded to an interrupt line) is now out of date? All of it. Except the parts that isn't. : In this world of multiple PCI to PCI bridges, how much latitude doe the : OS have in : deciding where an interrupt turns up? : (in 4.x and -current) Somehwere between none and a bunch. It all has to do with what interrupt controllers are available and how the interrupt lines are wired. Some systems force you to use the 'barberpole' for interrupts, while others wire them all to the same interrupts while others allow smome limited sleections. : An example is my Dell PE2850 (on 4.x), in which my 4 port ethernet card : seems to : be assigned irqs 10,14,14,2 in that order sometimes and 16,17,17,2 at : others. This looks to be the difference between using the APIC and not using the APIC. I'd guess this is an SMP vs non-SMP enabled kernel. : Who is making those decisions? Is it the BIOS and 4.x is just playing along? Kinda, except when it isn't. The BIOS usually assigns an interrupt, and we play along. However, usually is a lot less often than it used to be so we're now more typically routing ourselves. : Assuming the much maligned "boot interrupt" comes in on irq2, does the OS : have the oportunity to put my 4th port somewhere else? On 4.x it collides : with one of my ether ports but in -current it doesn't That I can't tell you. : Linux and -current on teh same box a;;ocate way different irqs, and : they agree about it.. i.e. Linux and -current assign my 4 port card IRQs : 18,19,19,16. Resources are alloacted differently between the OS and the BIOS. Looks like Linux has a slightly different algorithm for assigning interrupts to free APIC pins. Notice that in all cases the middle two are shared. That detail is likely in the MPTables for the device in question. : Do they agree becasue something else has decided it (the bios again?) or : becasue they : use the same algorythm to work it out.. It depends. On some system they will agree because the BIOS has set everything up. On other systems they may agree because they use similar algorithms to assign interrupts. : Also, if the "boot interrupt" was previously set to 2, is that likely to : have changed in -current? : Am I now going to get clobbered on IRQ16? If yes, is this something : that teh BIOS writers : decided, or something that the Motherboard designers decided? I've no clue about boot interrupts. Warner From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 06:58:15 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9B32216A41F; Wed, 7 Dec 2005 06:58:15 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EE7843D45; Wed, 7 Dec 2005 06:58:10 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 91602229FA7; Tue, 6 Dec 2005 22:58:09 -0800 (PST) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id jB76w85t050163; Tue, 6 Dec 2005 22:58:08 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <439687FF.3010402@elischer.org> Date: Tue, 06 Dec 2005 22:58:07 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051120 X-Accept-Language: en, hu MIME-Version: 1.0 To: John Baldwin References: <43961758.4020407@elischer.org> <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> In-Reply-To: <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 06:58:15 -0000 John Baldwin wrote: > > On Dec 6, 2005, at 5:57 PM, Julian Elischer wrote: > >> In short words for the likes of me, >> Can someone give a quicj roundup on PCI routing in 4.x and -current. > > > My, what a set of questions. :) I'll do my best, but this will > probably be a long and perhaps wandering e-mail. > [...] This reply should be saved somewhere... it's gold I tell you From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 06:58:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2381B16A41F for ; Wed, 7 Dec 2005 06:58:25 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 319C843D60 for ; Wed, 7 Dec 2005 06:58:22 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Wed, 7 Dec 2005 09:58:18 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051207095818.0b307c89.ai@bmc.brk.ru> In-Reply-To: References: <20051206093020.691e1483.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 06:58:25 -0000 On Wed, 7 Dec 2005 04:18:56 +0300 Vladimir Timofeev wrote: > But testing: > # mbmon -S -d > SMBus[NVidia nForce2] found, but No HWM available on it!! > InitMBInfo: Unknown error: 0 > > # mbmon > Temp.= 26.0, 42.5, 0.0; Rot.= 2481, 0, 0 > Vcore = 1.63, 2.64; Volt. = 3.30, 5.03, 12.16, -11.87, -5.05 > > What additional tests can I do? Thank you for testing. Some SMBus implementations, i.e. Abit, may not work correctly - see comments into xmbmon sources. I think it's maybe your case. I've got Epox EP-8RDA3+ PRO and mbmon -S gives me no errors. I`ll try investigate this, but i don`t think that problem is with driver - lm_sensors uses the similar way working with controller. Btw, what is your version of xmbmon? -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 07:05:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08FD416A41F for ; Wed, 7 Dec 2005 07:05:43 +0000 (GMT) (envelope-from freebsd@azimut-tour.ru) Received: from cny.innet.yaroslavl.su (cny.innet.yaroslavl.su [217.15.134.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28AA543D5C for ; Wed, 7 Dec 2005 07:05:40 +0000 (GMT) (envelope-from freebsd@azimut-tour.ru) Received: from tac.innet.yaroslavl.su (tac.innet.yaroslavl.su [217.15.135.68]) by cny.innet.yaroslavl.su (8.11.6/8.11.6) with ESMTP id jB775ce68941 for ; Wed, 7 Dec 2005 10:05:38 +0300 (MSK) Received: from greencomp.azimutprint.ru (azimutprint.ru [217.15.145.118]) by tac.innet.yaroslavl.su (8.12.11/8.12.9) with ESMTP id jB775Zl5095174 for ; Wed, 7 Dec 2005 10:05:37 +0300 (MSK) (envelope-from freebsd@azimut-tour.ru) Date: Wed, 7 Dec 2005 10:05:35 +0300 From: GreenX X-Mailer: The Bat! (v3.62.12) UNREG / CD5BF9353B3B7091 X-Priority: 3 (Normal) Message-ID: <64682545.20051207100535@azimut-tour.ru> To: freebsd-current@freebsd.org Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Will Robinson and all another X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "FreeBSD@azimut-tour.ru" List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:05:43 -0000 Hi PPL! I have a computer with parent payment ASUS P4C800E-DELUXE. OS FreeBSD 6.0-stable (CVS from 21.nov.2005) is established. It is established five hard disks: - One system on ICH5 ata100 Maxtor 6Y200P0 - And four on Promise RAID 0+1 WDC WD3200J (D/B) All fine worked (except for em0, but also he has normally earned after updating) while I have not wanted to establish two more hard disks (Maxtor 6Y080M0) on Intel in Stripe RAID. Hard disks have been put - the system of them has found out (the truth and known all bug "failed to enable memory mapping"), and I with them was more did than nothing (did not format, did not break - there was no time). In three days of job the system has given out me the following: ad4: req=0xc630f190 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! This warning has been given many times. And ad4 it is established on Promise! After reboot smartd has given out the warning smartd [767]: Device:/dev/ad10, 1 Currently unreadable (pending) sectors smartd [767]: Device:/dev/ad10, 26 Offline uncorrectable sectors (ad10 the first disk in Stripe RAID on Intel MATRIX) After that has made CVSUP and has put for the night rebuild the world. In the morning has seen - to warrning ad4: req=0xc90efd48 SETFEATURES SET TRANSFER MODE semaphore timeout!! DANGER Will Robinson!! It was added: kern.maxfiles limit exceeded by uid 100, please see tuning (7). Has install the world, has spat and has disconnected these both HDDs from the controller (itself Matrix has remained switched on) Has passed three more days and yesterday has received the new letter:) kernel: DOH! ata_alloc_request failed! kernel: FAILURE - out of memory in ata_raid_init_request last message repeated 4 times kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081878016, length=49152)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081730560, length=12288)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554082091008, length=65536)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081927168, length=16384)] error = 5 kernel: g_vfs_done ():ar0s1d [WRITE (offset=554081943552, length=16384)] error = 5 syslogd: kernel boot file is/boot/kernel/kernel kernel: panic: kmem_malloc (4096): kmem_map too small: 172470272 total allocated Then has switched off also the controller, has again updated system and I wait some more days:) Immemorial Russian question - "what to make?", I think here it is inappropriate, and so all is clear Remarks on system: it is switched on HHT (ACPI, SMP) and DEVICE POLLING, the network interface em0 and Intel Matrix, both stand on one irq. From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 07:21:07 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 808E416A41F; Wed, 7 Dec 2005 07:21:07 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B91C43D45; Wed, 7 Dec 2005 07:21:07 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 4D9C419F2C; Tue, 6 Dec 2005 23:21:06 -0800 (PST) From: "Darren Pilgrim" To: "'John Baldwin'" Date: Tue, 6 Dec 2005 23:20:59 -0800 Message-ID: <018e01c5fafe$c9154a20$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: Importance: Normal Cc: current@FreeBSD.org Subject: RE: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:21:07 -0000 From: John Baldwin >=20 > The reason [for masking interrupts] is that PCI interrupts are level > triggered, so they won't "shut up" until the ISR has run and pacified > the PCI device. But PCI interrupts can be programmed either level- or edge-triggered, so wouldn't programming to edge-triggered interrupts solve the "they won't = shut up" issue? From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 07:39:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F0E1D16A41F; Wed, 7 Dec 2005 07:39:00 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81E1D43D58; Wed, 7 Dec 2005 07:39:00 +0000 (GMT) (envelope-from julian@elischer.org) Received: from idiom.com (idiom.com [216.240.32.1]) by delight.idiom.com (Postfix) with ESMTP id 20F881F941F; Tue, 6 Dec 2005 23:39:00 -0800 (PST) Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id jB77crKX012928; Tue, 6 Dec 2005 23:38:53 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <4396918D.9060109@elischer.org> Date: Tue, 06 Dec 2005 23:38:53 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051120 X-Accept-Language: en, hu MIME-Version: 1.0 To: John Baldwin References: <43961758.4020407@elischer.org> <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> In-Reply-To: <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:39:01 -0000 John Baldwin wrote: > > On Dec 6, 2005, at 5:57 PM, Julian Elischer wrote: > >> In short words for the likes of me, >> Can someone give a quicj roundup on PCI routing in 4.x and -current. > > > My, what a set of questions. :) I'll do my best, but this will > probably be a long and perhaps wandering e-mail. > > First off, interrupts for PCI devices are roughly split up into two > categories (currently): INTx interrupt lines and MSI interrupts. MSI > is relatively new and I won't cover it much here. No versions of > FreeBSD currently support MSI either (though it's on my todo list), so > I'll limit this discussion to INTx interrupts. For INTx interrupts, > each PCI device (or slot) has 4 interrupt lines: INTA, INTB, INTC, and > INTD. Thus, you can describe any individual PCI interrupt as a tuple > of (bus, slot, pin). For example, device 4's INTA pin on pci bus 0 > would be (0, 4, INTA). Each PCI function is allowed to have one INTx > interrupt. The bus and slot come from the location of that function in > the PCI hierarchy, and the pin comes from the intpin PCI config > register. PCI doesn't define beyond the INTx pin how an interrupt is > delivered to the CPU, etc. That is all a property of the architecture, > chipset, etc. > > On x86, there are two disparate sets of hardware for managing interrupt > signals. The first is the pair of 8259A interrupt controllers found on > all PC-AT compatible machines. The second set of hardware is the APIC > subsystem as it were. Each processor contains a local APIC that can > receive messages from other APICs and send messages to other local > APICs. In addition to the local APICs, the chipset contains 1 or more > I/O APICs. Each I/O APIC contains anywhere from 4 to 32 individual > interrupt pins. Common numbers are 4 (somewhat rare), 16, 24, and 32. > Conceptually, on x86 a given interrupt source can be described by the > tuple (pic, pin). > > Simply put, PCI interrupt routing is the mapping of (bus, slot, pin) > PCI interrupt tuples to (pic, pin) x86 interrupt tuples. > > Now, before delving deeper into the specifics of routing on x86, let me > digress about IRQs on FreeBSD. Basically, an IRQ value is a cookie > useful for binding a device interrupt (such as a PCI (bus, slot, pin) > tuple or an ISA IRQ) to a x86 interrupt tuple (pic, pin). BIOSes don't > operate with APICs at all, at least not for handling device > interrupts. Thus, they all use a simple mapping where IRQs 0-7 > correspond to pins 0-7 on the master 8259A, and IRQs 8-15 map to pins > 0-7 on the slave 8259A. All versions of FreeBSD use the same mapping > for IRQ cookie values when using the 8259As to route interrupts. For > the APIC case the mapping of IRQ cookies to (pic, pin) tuples is > slightly more complicated. First, the simple case. FreeBSD 5.2 and > later follow the ACPI model (even when not using ACPI) where the IRQs > 0-n correspond to the pins 0-n of the first I/O APIC, IRQs n+1 to > (n+1)+m map to pins 0 to m of the second I/O APIC, etc. (There is one > possible exception with ACPI I'll cover later.) FreeBSD 4.x is more > complicated. The reason is that due to cpl and spl interrupt masks > being 32-bit integers with 8 bits set aside for software interrupts > (SWIs), cpl only has 24 bits available for hardware interrupts. > Therefore, FreeBSD <= 5.2 is limited to IRQ values 0-23 and can't use > the simple (and intuitive) model that FreeBSD 5.2+ and ACPI use. What > FreeBSD 4.x does is to map the ISA interrupts attached to the first I/O > APIC to IRQs 0, 1, and 3-15. This just leaves IRQs 2 and 16-23 > available for all the other APIC interrupt pins. As each PCI device > registers an interrupt handler for a specific (apic, pin) tuple, that > x86 interrupt is mapped to one of the last set of IRQs. If all of them > have been used already, then the kernel starts assigning multiple > (apic, pin) tuples to the same IRQ resulting in interrupts being shared > in software because of the cpl limitation even though they aren't > shared in hardware. This is why your IRQ values are different on 4.x > than on FreeBSD 5.2+ and Linux which use the ACPI global interrupt > number model. but if I change the code that does this, I may be able to get my devices that collide with the 'boot interrupt' to go elsewhere? That would be good.. > > Now, back to how routing of PCI device interrupts on x86 actually > works. I'll cover non-ACPI first. There are two cases to consider. > First, the easy case is that a PCI device interrupt (bus, tuple, pin) > is wired directly to an individual pin on a pic. This is often how > interrupts are wired when using APICs. If you look at the mptable > output and look at the interrupt section, this is fairly obvious as you > will see entries that map the interrupt for a given pci bus, slot and > pin to a given apic id and intpin on that apic. Thus, there is the > mapping for (bus, slot, pin) to (pic, pin) directly. The way interrupt > routing is implemented in this case is that when we go to route an > interrupt for a given PCI device, we search the mptable for a matching > entry. We then look up the associated apic via its apic id, ask it for > the specified pin, and then ask that pin for its IRQ (via the > pic_vector method of the ioapic interrupt source object that describes > the specific pin). When nexus(4) does bus_setup_intr(), it passes that > IRQ to the x86 intr_machdep code which uses the IRQ as an index into > its interrupt source array and ends up with the interrupt source object > for the (apic, pin) tuple being used. (Thus, IRQs are just a cookie > that is the index into the global array of interrupt sources on x86.) > Note that interrupts routed this way are hardwired into the motherboard > design. There's no chance for the OS to change which (pic, pin) a PCI > device interrupt is hooked up to. but from my memory, many PCI devices can select between A,B,C and D so maybe by going to the device and selecting a different one of those you can force it to go elsewhere... > > For the non-APIC case (non-ACPI still), PCI device interrupts are > usually wired up to a pin on a programmable interrupt router. Each of > these pins is called a pci link device. Multiple PCI device interrupts > may be wired up to the same link device, and systems typically have > anywhere from 4 to 8 (sometimes even more) link devices. Each link > device can be independently routed to a given (pic, pin) and it is > limited to a fixed set of possible IRQs. If multiple link devices are > routed to the same IRQ, then all of the devices attached to both link > devices end up sharing the same IRQ (and thus the same ithread, etc.). > Because the link devices are independently steerable, this is the one > way in which the OS has limited flexibility in routing interrupts. > However, the way it works is that you route the link devices, not > individual PCI device interrupts. The table the BIOS provides with the > information about the link devices is called the $PIR (since that's the > 4 byte signature you search for in RAM to find it). You can see it > during a verbose boot dmesg. It is a table that maps a given (bus, > slot, intpin) PCI tuple to a link index. Each entry also has a bitmask > of the valid ISA IRQs ($PIR only allows for the 16 ISA IRQs) that the > specified link index can be routed to. Thus, the way that interrupt > routing works with $PIR is that when a PCI interrupt is routed, you > search the table for a matching entry to get a link index. The $PIR > code in sys/i386/pci/pci_pir.c basically has a list of link objects > that maintain state about each link. The code finds the data > associated with the link index and sees if it has an IRQ routed > already. If so, that's the IRQ that that PCI device interrupt is > assigned to. If an IRQ isn't routed already, then it has to use an > algorithm to pick one, make a BIOS call to route the link to the chosen > IRQ, and then assign the PCI device interrupt to that IRQ. > so, is a "link device" a physical piece of hardware or a software abstraction? > Now that you understand that, ACPI routing can make some sense. The > way that ACPI routing works is that each PCI bus in the ACPI namespace > has a _PRT method that returns a table of routing entries. Each entry > contains the slot and intpin that it handles (so that you can build the > (bus, slot, intpin) PCI tuple (bus comes from the PCI bus device _PRT > is a child of, in FreeBSD the _PRT is actually a child of the pcib(4) > device that is the bridge that is the parent of the PCI bus, but I > digress)) as well as a reference to a link device in the ACPI namespace > and a source index. If the link device reference is empty or NULL, > then the interrupt is a hard-wired interrupt such as the ones used with > MP Table routing, and the source index is the global interrupt number > (==IRQ) that you use for this interrupt and you are done. If the link > device reference isn't empty, then it is the name of a ACPI device > object that manages a single pci link device. Example names include > \_SB_.PCI0.LPC0.LNKA. Each link device object includes methods to > query which IRQ it is currently routed to (though in practice this is > unreliable), get the list of possible IRQs, disable the link device > altogether, and route the link device to a specified IRQ. This is > similar to the link objects we have in the $PIR code except that these > end up being full blown devices on the ACPI side. ACPI adds another > twist in that the BIOS is free to use link devices with APICs (MP Table > has no way of handling that), and in fact in practice there are some > nvidia chipsets for amd64 that do route some PCI device interrupts to > link devices that in APIC mode can be routed to any of the IRQs 20-23. > > Now some of the minor trivia and exceptions. On the first I/O APIC, > IRQ0 is generally routed to intpin 2, not intpin 0 (though many > motherboards don't actually hook up the IRQ0 output from the ISA timer > to intpin 2 but do claim to do so in the MP Table and MADT). Instead > intpin 0 is a special ExtINT pin that listens to the 8259As and can > forward interrupts from the 8259As to one or more CPUs. This is what > "mixed mode" is, and on FreeBSD 4.x, if we discover via a test that the > motherboard did not wire IRQ0 up to intpin 2, we use mixed mode to > deliver it via the 8259A bounced through the ExtINT pin 0 on the first > I/O APIC. Blech. Also, for ACPI, the SCI is generally tied to IRQ 9, > however, the SCI may be routed to another intpin in APIC mode. Rather > than change the IRQ value in the FADT (or whichever table the SCI INT > is in), ACPI will include an entry in the MADT that maps IRQ 9 to some > other intpin such as IRQ 13 or IRQ 20. If the new intpin is not an ISA > IRQ (> 15) we use a backdoor to override the IRQ ACPI uses. If the new > intpin is an ISA IRQ though, we actually rename the destination IRQ > (such as IRQ 13 on one of my boxes) to IRQ 9, and the original IRQ 9 > becomes a "dead" interrupt pin with no IRQ associated with it. Note > that except for a few rare and very old SMP boxes, no FreeBSD x86 > machine has an IRQ 2. Another odd case is that some very old SMP boxes > did not route PCI device interrupts to the APICs at all. Instead, they > routed the outputs of the link devices to the pins on the first I/O > APIC corresponding to the same IRQ as on the 8259A (the I/O APIC only > had 16 pins). Thus, on these boxes, PCI interrupts are still routed > via link devices via $PIR, and end up triggering IRQ X via intpin X on > the first I/O APIC. One final twist. If a PCI bus behind a PCI-PCI > bridge is not listed in a BIOS table ($PIR or MP Table) or does not > have a _PRT in ACPI, the interrupts are routed by applying the swizzle > defined in the PCI standard to route the interrupt via one of the four > INTx pins on the PCI-PCI bridge's parent PCI bus. The standard defines > this behavior for add-in cards, but some built in busses do this as > well. (I've seen several AGP busses that actually use this method to > route the VGA IRQ). > >> Also, if the "boot interrupt" was previously set to 2, is that likely >> to have changed in -current? >> Am I now going to get clobbered on IRQ16? If yes, is this something >> that teh BIOS writers >> decided, or something that the Motherboard designers decided? > > > The "boot interrupt" issue on some of the PXH's used for PCI-X and > PCI-e host bridges is an unpleasant mess. I think it comes from Intel > assuming all the world is windows (imagine that) and ignoring standards > (such as MP Table and ACPI) that it helps to author. (Yay Intel!) The > issue there is that the PXH's include a dedicated I/O APIC for each of > the two busses the PXH serves, and the PCI device interrupts are routed > to intpins on those APICs. To handle the non- APIC case, the PXH's > forward any device interrupts to the INTx pins on the parent side of > the PCI-PCI bridge if the APIC is disabled. The problem is that Intel > chose a hack to figure out if the APIC was disabled and that hack > interacts badly with FreeBSD. Basically, if the individual intpin is > masked in the APIC, the PXH assumes you aren't using the APIC to handle > interrupts and so it forwards the interrupt to the INTx pin on its > bridge's parent side. The problem is that after an interrupt comes in > on 4.x and later, we mask the interrupt in the APIC until we have run > the interrupt handler. The reason is that PCI interrupts are level > triggered, so they won't "shut up" until the ISR has run and pacified > the PCI device. 4.x masks the interrupt because it wants to not run > ISRs with all interrupts disabled, but at the same cpl that the > interrupt was registered at so that higher priority interrupts can > still preempt an ISR. 5.x and later need to mask the interrupt so that > the processor doesn't have to keep interrupts disabled until the > ithread finishes. Trying to do that would become complicated and quite > painful since it would also mean deferring the EOI to the lapic (which > has to happen on the same CPU that received the interrupt) and has > other nastiness since ithreads can block on locks, etc. Other OS's > that use ithreads such as BSD/OS and probably Solaris/x86 and > Darwin/x86 probably have the same issue. The sucky part is that Intel > didn't have to do this gross hack. ACPI requires that the OS call a > method _PIC if it wants to use APIC mode, and the _PIC method is free > to write to registers, PCI config space, etc., so Intel could have > provided a register to specify if the PXH's APIC was being used or not > and included the code to manage that in _PIC in their sample BIOS. > But, they didn't. > > One possible workaround for this issue would be to provide a hacked > PCI-PCI bridge driver for the PXH's that hacked the PCI interrupt > routing such that the PCI device interrupts for child devices didn't > use the APICs in the PXH at all, but used the IRQs that get aliased to > (such as IRQ16 on 5.2+). Getting that to work on 4.x might be quite > painful since 4.x PCI interrupt routing code is rather gross and hacky > already. > > Hopefully this at least answers some questions and gives a good > overview of what PCI interrupt routing is and how it works, etc. My head hurts, but a lot makes more sense now. I'll need to read this a few more times however. if you made this into a web page, and added a few diagrams that would be amazing.. also you use a few Acronyms without saying what they are.. Thanks! > From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 07:59:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 68DCD16A41F; Wed, 7 Dec 2005 07:59:05 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8043743D5C; Wed, 7 Dec 2005 07:59:03 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id D5D452082; Wed, 7 Dec 2005 08:58:58 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id C68902080; Wed, 7 Dec 2005 08:58:58 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id A7E3B33C1D; Wed, 7 Dec 2005 08:58:58 +0100 (CET) To: Nate Lawson References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> <86d5k9eric.fsf@xps.des.no> <868xuxer6f.fsf@xps.des.no> <43965CB2.5000707@root.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Wed, 07 Dec 2005 08:58:58 +0100 In-Reply-To: <43965CB2.5000707@root.org> (Nate Lawson's message of "Wed, 07 Dec 2005 12:53:22 +0900") Message-ID: <86u0dluym5.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 07:59:05 -0000 Nate Lawson writes: > Both a) and b) are not applicable. The goal of those stats is to > assist with profiling various algorithms. [...] I agree that b) doesn't apply if this is only meant to be used under controlled conditions, but a) definitely applies. > I'll make sure the signal handling is cleaned up when I commit it. Already done in my patch. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 08:39:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6553716A41F; Wed, 7 Dec 2005 08:39:49 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn.pobox.com (thorn.pobox.com [208.210.124.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9939E43D55; Wed, 7 Dec 2005 08:39:48 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from thorn (localhost [127.0.0.1]) by thorn.pobox.com (Postfix) with ESMTP id A4E49B8; Wed, 7 Dec 2005 03:40:09 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by thorn.sasl.smtp.pobox.com (Postfix) with ESMTP id 3B9EE10BF; Wed, 7 Dec 2005 03:40:04 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1Ejupv-0003Om-P3; Wed, 07 Dec 2005 08:39:40 +0000 Date: Wed, 7 Dec 2005 08:39:39 +0000 From: Brian Candler To: Brooks Davis Message-ID: <20051207083939.GA13055@uk.tiscali.com> References: <43957D3F.4070109@rsu.ru> <4395DC82.1080103@elischer.org> <20051206193317.GB31292@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051206193317.GB31292@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org, Julian Elischer , Michael Bushkov Subject: Re: [PATCH] nsswitch extensions + caching X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 08:39:49 -0000 On Tue, Dec 06, 2005 at 11:33:17AM -0800, Brooks Davis wrote: > On Tue, Dec 06, 2005 at 10:46:26AM -0800, Julian Elischer wrote: > > Michael Bushkov wrote: > > [...] > > > > so, I've been wonderring.. what's all the fuss about nsswitch? > > what does it get us? > > It gives us the ability use modules to provide arbitrary backends for a > variety of interfaces to system databases. For instance getpw*(), > gethost*(), etc. Or put it another way - it supplies the missing half to PAM. Whilst PAM can check your password using arbitary backend modules, it can't return your $HOME directory or the uid/gid to use. Regards, Brian. From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 09:56:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8BBE16A41F for ; Wed, 7 Dec 2005 09:56:50 +0000 (GMT) (envelope-from vovkasm@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0388E43D53 for ; Wed, 7 Dec 2005 09:56:49 +0000 (GMT) (envelope-from vovkasm@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so655731wri for ; Wed, 07 Dec 2005 01:56:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ltmZTaEdmBLXmwS6oFEtApsCZW27Tm5gY7zHuWVc2U6tVkrIRS7AhPzNvIrzZwLipbpDb4PmW1wHDTeS06zrWfSVQMuuJhQoCT0Qji1+aLTcII/jZ1ZcA2RwrJV4BdrsOnTR3CLwGnmPqcPebvWzlHmrokOKfkvIoCd2A41Mk3Y= Received: by 10.54.132.8 with SMTP id f8mr2910530wrd; Wed, 07 Dec 2005 01:56:49 -0800 (PST) Received: by 10.54.157.12 with HTTP; Wed, 7 Dec 2005 01:56:49 -0800 (PST) Message-ID: Date: Wed, 7 Dec 2005 12:56:49 +0300 From: Vladimir Timofeev To: Artemiev Igor In-Reply-To: <20051207095818.0b307c89.ai@bmc.brk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 09:56:50 -0000 Thanks for ansver. I'll also try studing xmbmon sources ;-) I use xmbmon from latest ports - xmbmon-205_1 2005/12/7, Artemiev Igor : > On Wed, 7 Dec 2005 04:18:56 +0300 > Vladimir Timofeev wrote: > > But testing: > > # mbmon -S -d > > SMBus[NVidia nForce2] found, but No HWM available on it!! > > InitMBInfo: Unknown error: 0 > > > > # mbmon > > Temp.=3D 26.0, 42.5, 0.0; Rot.=3D 2481, 0, 0 > > Vcore =3D 1.63, 2.64; Volt. =3D 3.30, 5.03, 12.16, -11.87, -5.05 > > > > What additional tests can I do? > Thank you for testing. Some SMBus implementations, i.e. Abit, may not > work correctly - see comments into xmbmon sources. I think it's > maybe your case. I've got Epox EP-8RDA3+ PRO and mbmon -S > gives me no errors. I`ll try investigate this, but i don`t think that > problem is with driver - lm_sensors uses the similar way working with > controller. Btw, what is your version of xmbmon? > > -- > iprefetch ai > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 13:49:12 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A63AF16A41F for ; Wed, 7 Dec 2005 13:49:12 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id E8F7543D6E for ; Wed, 7 Dec 2005 13:49:11 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jB7DmQV8016736; Wed, 7 Dec 2005 14:48:26 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jB7DmOcI016734; Wed, 7 Dec 2005 08:48:24 -0500 (EST) (envelope-from cracauer) Date: Wed, 7 Dec 2005 08:48:24 -0500 From: Martin Cracauer To: Vladimir Timofeev Message-ID: <20051207084824.A16613@cons.org> References: <20051206093020.691e1483.ai@bmc.brk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from vovkasm@gmail.com on Wed, Dec 07, 2005 at 04:18:56AM +0300 Cc: freebsd-current@freebsd.org, Artemiev Igor Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 13:49:12 -0000 Vladimir Timofeev wrote on Wed, Dec 07, 2005 at 04:18:56AM +0300: > I has applied this patch to my RELENG_6 and it seems to work (Abit NF7 > motherboard) I don't know about that particular board. But on all newer Abit boards Abit decided not to connect the temperature sensors to the normal monitoring chips on the board (which are still there and do voltage monitoring), but instead they have their proprietary "uGuru" chip (which does all things overclocking related, including temperature sensors). The Linux folks have been told documentation for this chip is not and will not be available. I have been disrecommending Abit boards ever since (and my AV8-Pro is shelfware). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 14:02:01 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41A0916A41F for ; Wed, 7 Dec 2005 14:02:01 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B24F43D45 for ; Wed, 7 Dec 2005 14:02:00 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3317081 for multiple; Wed, 07 Dec 2005 09:04:02 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7E1rGi056645; Wed, 7 Dec 2005 09:01:53 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Dec 2005 08:16:44 -0500 User-Agent: KMail/1.8.3 References: <20051206093020.691e1483.ai@bmc.brk.ru> In-Reply-To: <20051206093020.691e1483.ai@bmc.brk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070816.46165.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Artemiev Igor Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:02:01 -0000 On Tuesday 06 December 2005 01:30 am, Artemiev Igor wrote: > I add pseudo-device amdpmsub because nForce2 have two SMBus > interfaces. Patch here: > > http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff > > dmesg output: > > amdpm0: port > 0xdc00-0xdc1f,0x5000-0x501f,0x5500 -0x551f irq 5 at device 1.1 on pci0 > smbus0: on amdpm0 > smb0: on smbus0 > amdpmsub0: on amdpm0 > smbus1: on amdpmsub0 > smb1: on smbus1 > > I`ve tested it with xmbmon and all works fine. Is there any reason you can't make smbus1 a childof amdpm0 directly and ski= p=20 the amdpmsub0 device? =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 14:02:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 84EE716A41F for ; Wed, 7 Dec 2005 14:02:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C41843D4C for ; Wed, 7 Dec 2005 14:02:03 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3317083 for multiple; Wed, 07 Dec 2005 09:04:05 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7E1rGj056645; Wed, 7 Dec 2005 09:01:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Dec 2005 09:01:45 -0500 User-Agent: KMail/1.8.3 References: <43961758.4020407@elischer.org> <20051206.231644.34762139.imp@bsdimp.com> In-Reply-To: <20051206.231644.34762139.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070901.47271.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: julian@elischer.org, "M. Warner Losh" Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:02:04 -0000 On Wednesday 07 December 2005 01:16 am, M. Warner Losh wrote: > In message: <43961758.4020407@elischer.org> > > Julian Elischer writes: > : How much is set up by the BIOS and how much is set up by the OS (4.x and > : -current). > > On 4.x, the BIOS (PCI BIOS) is called to route interrupts from the PIR > table when such a table exists. On current, ACPI routines are called > (if acpi is enabled), with a fallback to the PIR. Both use the > MPTABLE when an APIC i in voled. Actually, the MP Table is only used for !ACPI. For ACPI + APIC, you enumer= ate=20 APICs (both local and I/O) via the MADT, and for each I/O APIC, the MADT=20 specifies the IRQ cookie value of the first intpin. Then, you call the _PI= C=20 method to tell the BIOS you are using the APICs. Then, all the _PRT method= s=20 check a saved copy of that argument to _PIC and return different arrays=20 (packages in ACPI parlance) based on that, so that the _PRT's basically=20 return two different things for the two different modes. The MP Table isn'= t=20 used at all. > : In this world of multiple PCI to PCI bridges, how much latitude doe the > : OS have in > : deciding where an interrupt turns up? > : (in 4.x and -current) > > Somehwere between none and a bunch. It all has to do with what > interrupt controllers are available and how the interrupt lines are > wired. Some systems force you to use the 'barberpole' for interrupts, > while others wire them all to the same interrupts while others allow > smome limited sleections. Well, links have limited selection, everything else is hard-wired. :) > : Who is making those decisions? Is it the BIOS and 4.x is just playing > : along? > > Kinda, except when it isn't. The BIOS usually assigns an interrupt, > and we play along. However, usually is a lot less often than it used > to be so we're now more typically routing ourselves. Well, we use the BIOS set IRQs for heuristics. For example, $PIR has no wa= y=20 of telling you what IRQ given link is already routed to, so when we probe t= he=20 $PIR, we do a bunch of PCI config accesses to the IRQ register to sniff out= =20 what it looks like the BIOS has done and then use those IRQs for link=20 devices. For ACPI we do the same thing as a fallback for when _CRS on a li= nk=20 device doesn't work. This approach only works for links routed via ISA IRQ= s=20 though. For APIC routing (except for the early SMP boxes that still used=20 only ISA IRQs), the BIOS IRQ values are worthless so we ignore them. > : Linux and -current on teh same box a;;ocate way different irqs, and > : they agree about it.. i.e. Linux and -current assign my 4 port card IRQs > : 18,19,19,16. > > Resources are alloacted differently between the OS and the BIOS. > Looks like Linux has a slightly different algorithm for assigning > interrupts to free APIC pins. Notice that in all cases the middle two > are shared. That detail is likely in the MPTables for the device in > question. Linux is doing what FreeBSD 5.2+ does. :) Here what is happening is that = we=20 are doing the swizzle across the PCI-PCI bridge on the 4-port card and=20 routing on the parent sideof the bridge via ACPI or MP Table. It sounds li= ke=20 this 4-port card does something brain damaged such that the middle two=20 devices swizzle to the same INTx on the parent side of the bridge. (E.g.,= =20 the devices are at "slots" 0, 1, 5, 6 on the card instead of the more typic= al=20 0, 1, 2, 3. It could also be that it is 0, 1, 2, 3, but device 2 is using= =20 INTD rather than INTA.) =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 14:06:53 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6929F16A422 for ; Wed, 7 Dec 2005 14:06:53 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id C77C543D93 for ; Wed, 7 Dec 2005 14:06:22 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3317323 for multiple; Wed, 07 Dec 2005 09:08:12 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7E66Dd056676; Wed, 7 Dec 2005 09:06:06 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Dec 2005 09:06:03 -0500 User-Agent: KMail/1.8.3 References: <018e01c5fafe$c9154a20$642a15ac@smiley> In-Reply-To: <018e01c5fafe$c9154a20$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070906.05117.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Darren Pilgrim Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:06:53 -0000 On Wednesday 07 December 2005 02:20 am, Darren Pilgrim wrote: > From: John Baldwin > > > The reason [for masking interrupts] is that PCI interrupts are level > > triggered, so they won't "shut up" until the ISR has run and pacified > > the PCI device. > > But PCI interrupts can be programmed either level- or edge-triggered, so > wouldn't programming to edge-triggered interrupts solve the "they won't > shut up" issue? No, PCI interrupts are level triggered. Individual APIC pins can be=20 programmed to be edge-triggered, sure. However, then interrupts stop worki= ng=20 if 2 devices are sharing a line and one interrupts after the other has=20 already interrupted and after the second device's ISR has already run. In= =20 this case, the ithread will finish and go back to sleep waiting for an=20 interrupt. However, since the ISR for the second device wasn't run after=20 that device asserted its interrupt pin, the second device will keep the pin= =20 pulled low forever, so there will never be a hi -> low transition that the= =20 APIC pin would post an interrupt for and that intpin and all attached devic= es=20 are effectively dead. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 14:09:45 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2EFFF16A41F; Wed, 7 Dec 2005 14:09:45 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAC6C43D49; Wed, 7 Dec 2005 14:09:37 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3317489 for multiple; Wed, 07 Dec 2005 09:11:19 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7E9Cuc056693; Wed, 7 Dec 2005 09:09:12 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org, obrien@freebsd.org Date: Wed, 7 Dec 2005 09:09:10 -0500 User-Agent: KMail/1.8.3 References: <20051207033419.GA10185@dragon.NUXI.org> In-Reply-To: <20051207033419.GA10185@dragon.NUXI.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070909.11354.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Subject: Re: config(8) VERSREQ checking broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:09:45 -0000 On Tuesday 06 December 2005 10:34 pm, David O'Brien wrote: > sys/amd64/conf# config -V > 600002 > sys/amd/conf# config GENERIC > Specify machine type, e.g. ``machine i386'' > sys/amd/conf# grep VERSREQ ../../conf/Makefile.amd64 > %VERSREQ=3D 600004 > > Shouldn't I be getting the usual error message that my config version > isn't new enough to support building a kernel from these sources? It has no machine type, so it doesn't know which Makefile to open and searc= h=20 for the %VERSREQ variable. On current the machine directive moved from=20 GENERIC to DEFAULTS (since it isn't something you'd really want to be=20 changing anyway). =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 14:28:17 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 487AE16A420 for ; Wed, 7 Dec 2005 14:28:17 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 16C4143D92 for ; Wed, 7 Dec 2005 14:27:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3319097 for multiple; Wed, 07 Dec 2005 09:29:43 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7ERYo4056800; Wed, 7 Dec 2005 09:27:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Julian Elischer Date: Wed, 7 Dec 2005 09:25:45 -0500 User-Agent: KMail/1.8.3 References: <43961758.4020407@elischer.org> <1B4F46C2-C424-45F8-9328-BEE2AA6E0DC6@FreeBSD.org> <4396918D.9060109@elischer.org> In-Reply-To: <4396918D.9060109@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512070925.47141.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 14:28:17 -0000 On Wednesday 07 December 2005 02:38 am, Julian Elischer wrote: > > have been used already, then the kernel starts assigning multiple > > (apic, pin) tuples to the same IRQ resulting in interrupts being shared > > in software because of the cpl limitation even though they aren't > > shared in hardware. This is why your IRQ values are different on 4.x > > than on FreeBSD 5.2+ and Linux which use the ACPI global interrupt > > number model. > > but if I change the code that does this, I may be able to get my devices > that collide with the 'boot interrupt' to go elsewhere? That would be > good.. No, probably not. The "boot interrupt" collisions happen on all versions o= f=20 =46reeBSD currently. I do have a workaround in my head, and if it works, i= t=20 might even be backportable to 4.x. You can't change how the interrupts are= =20 physically wired though, and the boot interrupt collisions happens because = of=20 issues in hardware. You might be able to pull a trick where you map the tw= o=20 colliding interrupts to the same IRQ cookie on 4.x, but that'd be ugly, and= =20 the fix I'm considering would be a lot simpler and do the same thing (I nee= d=20 to check, but I think that the INTx swizzle the PXH's do might match the=20 standard PCI-PCI bridge swizzle, and if so, we can just depend on the boot= =20 interrupt and route the interrupts via the boot destination by ignoring the= =20 _PRT (for ACPI) on such bridges, and ignoring any MP Table entries (on=20 non-ACPI) so that it falls back to using the PCI-PCI swizzle. > > for the (apic, pin) tuple being used. (Thus, IRQs are just a cookie > > that is the index into the global array of interrupt sources on x86.) > > Note that interrupts routed this way are hardwired into the motherboard > > design. There's no chance for the OS to change which (pic, pin) a PCI > > device interrupt is hooked up to. > > but from my memory, many PCI devices can select between A,B,C and D > so maybe by going to the device and selecting a different one of those > you can force it to go elsewhere... They devices don't really get to choose, it's a read-only config register t= hat=20 is set in silicon. Even then, IIRC, PCI mandates that single-function=20 devices use INTA, and that multi function devices use INTA if they have one= =20 interrupt, INT[AB] if they have two, etc. (I'm less certain about the=20 multifunction part, but single-function devices must use INTA.) > > already. If so, that's the IRQ that that PCI device interrupt is > > assigned to. If an IRQ isn't routed already, then it has to use an > > algorithm to pick one, make a BIOS call to route the link to the chosen > > IRQ, and then assign the PCI device interrupt to that IRQ. > > so, is a "link device" a physical piece of hardware or a software > abstraction? It's a physical piece of hardware in that it represents a pin on a=20 programmable interrupt router. You basically have a chip that has several= =20 input pins (each of which is a link device) and the chip can programmably=20 route each intput pin to one of several output pins. Thus, you might have = a=20 single chip but with multiple pins (like an APIC with 24 different pins) an= d=20 each input pin is considered a link device. > > Hopefully this at least answers some questions and gives a good > > overview of what PCI interrupt routing is and how it works, etc. > > My head hurts, but a lot makes more sense now. > I'll need to read this a few more times however. > if you made this into a web page, and added a few diagrams that would be > amazing.. also you use a few Acronyms without saying what they are.. Yeah, I should probably put this in the arch-handbook, but I'd need to lear= n=20 pic to draw the diagrams (or perhaps I could draw them in something else an= d=20 export it as .eps?) =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 17:59:28 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3079616A41F; Wed, 7 Dec 2005 17:59:28 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B11C43D46; Wed, 7 Dec 2005 17:59:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id jB7HvL6K030512; Wed, 7 Dec 2005 10:57:21 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 07 Dec 2005 10:57:22 -0700 (MST) Message-Id: <20051207.105722.60788677.imp@bsdimp.com> To: darren.pilgrim@bitfreak.org From: "M. Warner Losh" In-Reply-To: <018e01c5fafe$c9154a20$642a15ac@smiley> References: <018e01c5fafe$c9154a20$642a15ac@smiley> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Wed, 07 Dec 2005 10:57:21 -0700 (MST) Cc: current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 17:59:28 -0000 In message: <018e01c5fafe$c9154a20$642a15ac@smiley> "Darren Pilgrim" writes: : From: John Baldwin : > : > The reason [for masking interrupts] is that PCI interrupts are level : > triggered, so they won't "shut up" until the ISR has run and pacified : > the PCI device. : : But PCI interrupts can be programmed either level- or edge-triggered, so : wouldn't programming to edge-triggered interrupts solve the "they won't shut : up" issue? PCI interrupts are level. There's no way to program them otherwise. Warner From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 18:07:40 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 94F5516A41F for ; Wed, 7 Dec 2005 18:07:40 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7EC043D5E for ; Wed, 7 Dec 2005 18:07:35 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id jB7I7S9W059718; Wed, 7 Dec 2005 11:07:28 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <439724E0.3020102@samsco.org> Date: Wed, 07 Dec 2005 11:07:28 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <018e01c5fafe$c9154a20$642a15ac@smiley> <20051207.105722.60788677.imp@bsdimp.com> In-Reply-To: <20051207.105722.60788677.imp@bsdimp.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: darren.pilgrim@bitfreak.org, current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 18:07:40 -0000 M. Warner Losh wrote: > In message: <018e01c5fafe$c9154a20$642a15ac@smiley> > "Darren Pilgrim" writes: > : From: John Baldwin > : > > : > The reason [for masking interrupts] is that PCI interrupts are level > : > triggered, so they won't "shut up" until the ISR has run and pacified > : > the PCI device. > : > : But PCI interrupts can be programmed either level- or edge-triggered, so > : wouldn't programming to edge-triggered interrupts solve the "they won't shut > : up" issue? > > PCI interrupts are level. There's no way to program them otherwise. > > Warner While electrically they are level, the APIC can be programmed to pass them on either level or edge. Once you get into MSI, the distinction becomes very muddy. Scott From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 20:41:55 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95A4616A420; Wed, 7 Dec 2005 20:41:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABE343D73; Wed, 7 Dec 2005 20:41:47 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3338755 for multiple; Wed, 07 Dec 2005 15:43:45 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7Kfbux062614; Wed, 7 Dec 2005 15:41:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Dec 2005 15:33:02 -0500 User-Agent: KMail/1.8.2 References: <018e01c5fafe$c9154a20$642a15ac@smiley> <20051207.105722.60788677.imp@bsdimp.com> <439724E0.3020102@samsco.org> In-Reply-To: <439724E0.3020102@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512071533.04396.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: darren.pilgrim@bitfreak.org, current@freebsd.org, "M. Warner Losh" Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 20:41:55 -0000 On Wednesday 07 December 2005 01:07 pm, Scott Long wrote: > M. Warner Losh wrote: > > In message: <018e01c5fafe$c9154a20$642a15ac@smiley> > > > > "Darren Pilgrim" writes: > > : From: John Baldwin > > : > > : > The reason [for masking interrupts] is that PCI interrupts are level > > : > triggered, so they won't "shut up" until the ISR has run and pacified > > : > the PCI device. > > : > > : But PCI interrupts can be programmed either level- or edge-triggered, > > : so wouldn't programming to edge-triggered interrupts solve the "they > > : won't shut up" issue? > > > > PCI interrupts are level. There's no way to program them otherwise. > > > > Warner > > While electrically they are level, the APIC can be programmed to pass > them on either level or edge. Once you get into MSI, the distinction > becomes very muddy. That's not for delivery, that's for how the APIC interprets the signals you see. See my earlier e-mail why misprogramming the APIC would hose things. MSI is a whole different ball of wax entirely in that regard. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 20:41:55 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95A4616A420; Wed, 7 Dec 2005 20:41:55 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABE343D73; Wed, 7 Dec 2005 20:41:47 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3338755 for multiple; Wed, 07 Dec 2005 15:43:45 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB7Kfbux062614; Wed, 7 Dec 2005 15:41:37 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 7 Dec 2005 15:33:02 -0500 User-Agent: KMail/1.8.2 References: <018e01c5fafe$c9154a20$642a15ac@smiley> <20051207.105722.60788677.imp@bsdimp.com> <439724E0.3020102@samsco.org> In-Reply-To: <439724E0.3020102@samsco.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512071533.04396.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: darren.pilgrim@bitfreak.org, current@freebsd.org, "M. Warner Losh" Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 20:41:55 -0000 On Wednesday 07 December 2005 01:07 pm, Scott Long wrote: > M. Warner Losh wrote: > > In message: <018e01c5fafe$c9154a20$642a15ac@smiley> > > > > "Darren Pilgrim" writes: > > : From: John Baldwin > > : > > : > The reason [for masking interrupts] is that PCI interrupts are level > > : > triggered, so they won't "shut up" until the ISR has run and pacified > > : > the PCI device. > > : > > : But PCI interrupts can be programmed either level- or edge-triggered, > > : so wouldn't programming to edge-triggered interrupts solve the "they > > : won't shut up" issue? > > > > PCI interrupts are level. There's no way to program them otherwise. > > > > Warner > > While electrically they are level, the APIC can be programmed to pass > them on either level or edge. Once you get into MSI, the distinction > becomes very muddy. That's not for delivery, that's for how the APIC interprets the signals you see. See my earlier e-mail why misprogramming the APIC would hose things. MSI is a whole different ball of wax entirely in that regard. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Dec 7 23:12:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2F45616A425; Wed, 7 Dec 2005 23:12:14 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id E21D143D46; Wed, 7 Dec 2005 23:11:51 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 3578119F2C; Wed, 7 Dec 2005 15:11:47 -0800 (PST) From: "Darren Pilgrim" To: "'John Baldwin'" , Date: Wed, 7 Dec 2005 15:11:41 -0800 Message-ID: <001801c5fb83$987529f0$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 In-Reply-To: <200512070906.05117.jhb@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal Cc: Subject: RE: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Dec 2005 23:12:14 -0000 From: John Baldwin >=20 > No, PCI interrupts are level triggered. Individual APIC pins > can be programmed to be edge-triggered, sure. However, then > interrupts stop working if 2 devices are sharing a line and > one interrupts after the other has already interrupted and > after the second device's ISR has already run. In this case, > the ithread will finish and go back to sleep waiting for an > interrupt. However, since the ISR for the second device > wasn't run after that device asserted its interrupt pin, the > second device will keep the pin pulled low forever, so there > will never be a hi -> low transition that the APIC pin would > post an interrupt for and that intpin and all attached > devices are effectively dead. What if the APIC was programmed to be edge-triggered just before the = ithread runs and programmed back to level-trigger when the ithread completes? From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 02:26:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A145216A41F for ; Thu, 8 Dec 2005 02:26:02 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from blake.polstra.com (blake.polstra.com [64.81.189.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09EA243D46 for ; Thu, 8 Dec 2005 02:25:54 +0000 (GMT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [64.81.189.67]) by blake.polstra.com (8.13.1/8.13.1) with ESMTP id jB82PVwY054349 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Dec 2005 18:25:31 -0800 (PST) (envelope-from jdp@strings.polstra.com) Received: (from jdp@localhost) by strings.polstra.com (8.13.1/8.13.1/Submit) id jB82PV3s006078; Wed, 7 Dec 2005 18:25:31 -0800 (PST) (envelope-from jdp) Message-ID: X-Mailer: XFMail 1.5.5 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <001801c5fb83$987529f0$642a15ac@smiley> Date: Wed, 07 Dec 2005 18:25:31 -0800 (PST) From: John Polstra To: Darren Pilgrim Cc: freebsd-current@freebsd.org Subject: RE: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 02:26:02 -0000 On 07-Dec-2005 Darren Pilgrim wrote: > What if the APIC was programmed to be edge-triggered just before the ithread > runs and programmed back to level-trigger when the ithread completes? For what it's worth (maybe not much), I tried that and couldn't get it to work. Various devices timed out during boot. I didn't spend any appreciable time investigating why, so it's possible I did something incorrectly or that it could have been made to work with more effort. John From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 04:37:30 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F5F116A41F; Thu, 8 Dec 2005 04:37:30 +0000 (GMT) (envelope-from cpressey@catseye.mine.nu) Received: from priv-edtnes51.telusplanet.net (outbound04.telus.net [199.185.220.223]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A0A943D60; Thu, 8 Dec 2005 04:37:10 +0000 (GMT) (envelope-from cpressey@catseye.mine.nu) Received: from catseye.biscuit.boo ([154.20.76.195]) by priv-edtnes51.telusplanet.net (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with SMTP id <20051208043707.XAER25350.priv-edtnes51.telusplanet.net@catseye.biscuit.boo>; Wed, 7 Dec 2005 21:37:07 -0700 Date: Wed, 7 Dec 2005 20:38:12 -0800 From: Chris Pressey To: Andrew Turner Message-Id: <20051207203812.32e831f8.cpressey@catseye.mine.nu> In-Reply-To: <439524D6.6010705@fubar.geek.nz> References: <20051027200448.1ba236fe.cpressey@catseye.mine.nu> <43753528.7030802@freesbie.org> <20051202123120.736bf5ff.cpressey@catseye.mine.nu> <439524D6.6010705@fubar.geek.nz> Organization: Cat's Eye Technologies X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd4.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: geom@freebsd.org, current@freebsd.org, discussion@bsdinstaller.com Subject: Re: [BSDInstaller] Re: fdisk(8) no longer capable of altering geometry X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 04:37:30 -0000 On Tue, 06 Dec 2005 18:42:46 +1300 Andrew Turner wrote: > Chris Pressey wrote: > > > Does ANYONE else see the same behaviour that I am seeing? Namely: > > [fdisk(8) incapable of changing geometry] > > > >I see this on CURRENT as of late last night. > > > I can see this on CURRENT from a week ago. Thanks, Andrew! The PR has been filed, the # is 90093. -Chris From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 06:08:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BED6C16A41F; Thu, 8 Dec 2005 06:08:43 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 186B943D7E; Thu, 8 Dec 2005 06:08:40 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Thu, 8 Dec 2005 09:08:35 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051208090835.471a5584.ai@bmc.brk.ru> In-Reply-To: <200512070816.46165.jhb@freebsd.org> References: <20051206093020.691e1483.ai@bmc.brk.ru> <200512070816.46165.jhb@freebsd.org> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 06:08:43 -0000 On Wed, 7 Dec 2005 08:16:44 -0500 John Baldwin wrote: > On Tuesday 06 December 2005 01:30 am, Artemiev Igor wrote: > > I add pseudo-device amdpmsub because nForce2 have two SMBus > > interfaces. Patch here: > > > > http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff > > > > dmesg output: > > > > amdpm0: port > > 0xdc00-0xdc1f,0x5000-0x501f,0x5500 -0x551f irq 5 at device 1.1 on > > pci0 smbus0: on amdpm0 > > smb0: on smbus0 > > amdpmsub0: on amdpm0 > > smbus1: on amdpmsub0 > > smb1: on smbus1 > > > > I`ve tested it with xmbmon and all works fine. > > Is there any reason you can't make smbus1 a childof amdpm0 directly > and skip the amdpmsub0 device? I simply do not see any way to do it with current implementation of ampdm(and also viapm, etc) & smbus, without modifying the smb->smbus->smbus driver interface. I may be wrong, but as far as I know, currently it's one smb for one driver (smbus_* limitation) -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 06:14:27 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6D6216A41F for ; Thu, 8 Dec 2005 06:14:27 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9A2443D62 for ; Thu, 8 Dec 2005 06:14:24 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Thu, 8 Dec 2005 09:14:22 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051208091422.4d1a3ee0.ai@bmc.brk.ru> In-Reply-To: References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 06:14:28 -0000 On Wed, 7 Dec 2005 12:56:49 +0300 Vladimir Timofeev wrote: > Thanks for ansver. I'll also try studing xmbmon sources ;-) > I use xmbmon from latest ports - xmbmon-205_1 I assume, that mbmon can't recognize the chip. I tested another board from Asus with nForce2 chipset, and it worked perfectly. Possibly, you should set the chip type by -p, if that is the case. It's not a driver problem. %mbmon -S -d Using SMBus access method[NVidia nForce2]!! * Asus Chip ASB100(Bach) found. %mbmon -S Temp.= 41.0, 25.0, 30.0; Rot.= 5314, 0, 0 Vcore = 1.68, 1.68; Volt. = 3.30, 4.92, 11.80, -10.79, -4.66 Temp.= 41.0, 25.0, 30.0; Rot.= 5314, 0, 0 Vcore = 1.70, 1.70; Volt. = 3.26, 4.92, 11.80, -10.79, -4.66 Temp.= 41.0, 25.0, 30.0; Rot.= 5357, 0, 0 Vcore = 1.68, 1.68; Volt. = 3.30, 4.92, 11.80, -10.79, -4.66 I've also added the support for nForce3/4, like with lm_sensors, but haven't tested a new patch: http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff You may try it with an other chipsets, if you want. -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 08:12:28 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D081016A41F for ; Thu, 8 Dec 2005 08:12:28 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from centrmmtao04.cox.net (centrmmtao04.cox.net [70.168.83.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B5CF43D78 for ; Thu, 8 Dec 2005 08:12:28 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by centrmmtao04.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051208081046.IRGM8318.centrmmtao04.cox.net@mezz.mezzweb.com>; Thu, 8 Dec 2005 03:10:46 -0500 Date: Thu, 08 Dec 2005 02:13:09 -0600 To: "Artemiev Igor" References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20051208091422.4d1a3ee0.ai@bmc.brk.ru> User-Agent: Opera M2/8.51 (Linux, build 1462) Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 08:12:29 -0000 On Thu, 08 Dec 2005 00:14:22 -0600, Artemiev Igor wrote: > On Wed, 7 Dec 2005 12:56:49 +0300 > Vladimir Timofeev wrote: > >> Thanks for ansver. I'll also try studing xmbmon sources ;-) >> I use xmbmon from latest ports - xmbmon-205_1 > > I assume, that mbmon can't recognize the chip. I tested another board > from Asus with nForce2 chipset, and it worked perfectly. Possibly, you > should set the chip type by -p, if that is the case. It's not a driver > problem. > > %mbmon -S -d > > Using SMBus access method[NVidia nForce2]!! > * Asus Chip ASB100(Bach) found. > > %mbmon -S > > Temp.= 41.0, 25.0, 30.0; Rot.= 5314, 0, 0 > Vcore = 1.68, 1.68; Volt. = 3.30, 4.92, 11.80, -10.79, -4.66 > > Temp.= 41.0, 25.0, 30.0; Rot.= 5314, 0, 0 > Vcore = 1.70, 1.70; Volt. = 3.26, 4.92, 11.80, -10.79, -4.66 > > Temp.= 41.0, 25.0, 30.0; Rot.= 5357, 0, 0 > Vcore = 1.68, 1.68; Volt. = 3.30, 4.92, 11.80, -10.79, -4.66 > > I've also added the support for nForce3/4, like with lm_sensors, > but haven't tested a new patch: > > http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff > > You may try it with an other chipsets, if you want. Thanks, I see you have added one of chipset (0x0084) that is what I have but mbmon couldn't pick up. Also, there is no /dev/smb*. FreeBSD 6.0-STABLE (Dec 6th) Motherboard: http://www.msicomputer.com/product/p_spec.asp?model=K7N2_Delta2_Platinum&class=mb dmesg: ========================================== --- dmesg-before Thu Dec 8 00:22:40 2005 +++ dmesg-after Thu Dec 8 01:21:08 2005 @@ -30,7 +30,10 @@ pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 -pci0: at device 1.1 (no driver attached) +amdpm0: port 0xc400-0xc41f,0x5000-0x501f irq 23 at device 1.1 on pci0 +smbus0: on amdpm0 +amdpmsub0: on amdpm0 +smbus1: on amdpmsub0 ohci0: mem 0xe4001000-0xe4001fff irq 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support ========================================== pciconf: ========================================== --- pciconf-before Thu Dec 8 00:23:53 2005 +++ pciconf-after Thu Dec 8 01:21:21 2005 @@ -33,7 +33,7 @@ device = 'nForce MCP2S PCI to ISA Bridge' class = bridge subclass = PCI-ISA -none5@pci0:1:1: class=0x0c0500 card=0x57001462 chip=0x008410de rev=0xa1 hdr=0x00 +amdpm0@pci0:1:1: class=0x0c0500 card=0x57001462 chip=0x008410de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP2S PCI System Management' class = serial bus ========================================== mbmon: ========================================== % mbmon -S -d No SMBus HWM available!! InitMBInfo: Unknown error: 0 ========================================== Without use -S in mbmon, mbmon always work fine with and without your patch. Cheers, Mezz -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 08:16:40 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 099B416A41F for ; Thu, 8 Dec 2005 08:16:40 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3E5F43D79 for ; Thu, 8 Dec 2005 08:16:32 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail18.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jB88GOu9026492 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Thu, 8 Dec 2005 19:16:26 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jB88GOHh067092; Thu, 8 Dec 2005 19:16:24 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jB88GMtE067091; Thu, 8 Dec 2005 19:16:22 +1100 (EST) (envelope-from pjeremy) Date: Thu, 8 Dec 2005 19:16:22 +1100 From: Peter Jeremy To: Putinas Piliponis Message-ID: <20051208081622.GV32006@cirb503493.alcatel.com.au> References: <217202CB5FF8AE439E263CE3D48ECB5068C4F2@honda.int.hansa.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <217202CB5FF8AE439E263CE3D48ECB5068C4F2@honda.int.hansa.lt> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: vmware calcru runtime went backward and huge inaccuracy in clock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 08:16:40 -0000 On Tue, 2005-Dec-06 08:52:20 +0200, Putinas Piliponis wrote: >I am running vmware 5.5 currently and FreeBSD 6.0-RELEASE. After >upgrading from 5.4 (at the same time I upgraded vmware from 5.0 so can't >really say which fault is it). Do you still have vmware-tools installed and configured to use the host clock? -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 08:57:41 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C23116A41F for ; Thu, 8 Dec 2005 08:57:41 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: from av10-1-sn2.hy.skanova.net (av10-1-sn2.hy.skanova.net [81.228.8.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 442FC43D79 for ; Thu, 8 Dec 2005 08:57:31 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av10-1-sn2.hy.skanova.net (Postfix, from userid 502) id 1581D381EC; Thu, 8 Dec 2005 09:57:29 +0100 (CET) Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av10-1-sn2.hy.skanova.net (Postfix) with ESMTP id DD544381EC; Thu, 8 Dec 2005 09:57:29 +0100 (CET) Received: from t3o955p111.telia.com (t3o955p111.telia.com [195.252.53.111]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 1361237E4B; Thu, 8 Dec 2005 09:57:28 +0100 (CET) From: Joel Dahl To: current@FreeBSD.org Content-Type: text/plain Date: Thu, 08 Dec 2005 09:55:01 +0100 Message-Id: <1134032101.664.22.camel@dude.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: hackers@FreeBSD.org Subject: FreeBSD list of projects for volunteers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 08:57:41 -0000 Hi all, As some of you may have noticed, we've added a new section to the website, which contains a lot of interesting projects and ideas that volunteers and developers are encouraged to evaluate and work on. Some of these projects are simple, and someone just needs to spend some time on them and do the work, some are harder, intended for junior kernel hackers. This should also serve as a good starting point for people that would like to contribute to FreeBSD and perhaps become committers in the future. You can find the list here: http://www.freebsd.org/projects/ideas/ -- Joel - joel at FreeBSD dot org From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 09:45:24 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7F2316A41F; Thu, 8 Dec 2005 09:45:24 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vbook.fbsd.ru (swsoft-mipt-nat.sw.ru [195.214.233.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42A1643D83; Thu, 8 Dec 2005 09:45:23 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1EkIL4-000MR0-G3; Thu, 08 Dec 2005 12:45:22 +0300 From: Vladimir Grebenschikov To: freebsd-net Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Thu, 08 Dec 2005 12:45:21 +0300 Message-Id: <1134035121.1229.22.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: current Subject: something wrong with either port net/iwi-firmare or iwi driver in tree on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 09:45:24 -0000 Hi It is happens on fresh 7-CURRENT. $ man 4 iwi ... This driver requires firmware to be loaded before it will work. You need to install the net/iwi-firmware port before ifconfig(8) will work ... /usr/ports/net/iwi-firmware# make ===> iwi-firmware-2.4 iwi(4) support is already included in your tree. /usr/ports/net/iwi-firmware# $ find /usr/src -name '*iwi*' | fgrep -v iwic /usr/src/share/man/man4/iwi.4 /usr/src/sys/dev/iwi /usr/src/sys/dev/iwi/if_iwi.c /usr/src/sys/dev/iwi/if_iwireg.h /usr/src/sys/dev/iwi/if_iwivar.h /usr/src/sys/modules/iwi /usr/src/tools/tools/iwi /usr/src/tools/tools/iwi/iwistats.c $ What is official way to fetch firmware now ? -- Vladimir B. Grebenschikov SWsoft Inc. vova@swsoft.com From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 09:54:09 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B441C16A41F for ; Thu, 8 Dec 2005 09:54:09 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E79943D8E for ; Thu, 8 Dec 2005 09:54:02 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Thu, 8 Dec 2005 12:53:59 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051208125359.17d7f47a.ai@bmc.brk.ru> In-Reply-To: References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 09:54:09 -0000 On Thu, 08 Dec 2005 02:13:09 -0600 "Jeremy Messenger" wrote: > Thanks, I see you have added one of chipset (0x0084) that is what I > have but mbmon couldn't pick up. Also, there is no /dev/smb*. It's my mistake - i haven`t put MODULE_DEPEND for amdpmsub into amdp.c. You need kldload smb BEFORE amdpm. Or add this line: MODULE_DEPEND(amdpmsub, smbus, SMBUS_MINVER, SMBUS_PREFVER, SMBUS_MAXVER) > Without use -S in mbmon, mbmon always work fine with and without > your patch. See above. I`ve updated the patch. -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 13:05:58 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 681EC16A422 for ; Thu, 8 Dec 2005 13:05:58 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from jazz.hansabank.lt (jazz.hansabank.lt [193.109.235.157]) by mx1.FreeBSD.org (Postfix) with ESMTP id 938C643D55 for ; Thu, 8 Dec 2005 13:05:47 +0000 (GMT) (envelope-from Putinas.Piliponis@hansa.lt) Received: from localhost (localhost [127.0.0.1]) by jazz.hansabank.lt (Postfix) with ESMTP id AB22DF981 for ; Thu, 8 Dec 2005 15:05:44 +0200 (EET) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.0.6556.0 Date: Thu, 8 Dec 2005 15:04:48 +0200 Message-ID: <217202CB5FF8AE439E263CE3D48ECB509BAA8E@honda.int.hansa.lt> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: vmware calcru runtime went backward and huge inaccuracy in clock Thread-Index: AcX7z9UT4x9qwtotR+ONQds8dHzi+gAJ9VSQ From: "Putinas Piliponis" To: Subject: RE: vmware calcru runtime went backward and huge inaccuracy in clock X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 13:05:58 -0000 Nope. After I found a working workaround - disable apic in kernel. (not acpi) -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Peter Jeremy Sent: Thursday, December 08, 2005 10:16 AM To: Putinas Piliponis Cc: freebsd-current@freebsd.org Subject: Re: vmware calcru runtime went backward and huge inaccuracy in clock On Tue, 2005-Dec-06 08:52:20 +0200, Putinas Piliponis wrote: >I am running vmware 5.5 currently and FreeBSD 6.0-RELEASE. After >upgrading from 5.4 (at the same time I upgraded vmware from 5.0 so can't >really say which fault is it). Do you still have vmware-tools installed and configured to use the host clock? --=20 Peter Jeremy _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 14:14:58 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 71C7216A41F; Thu, 8 Dec 2005 14:14:58 +0000 (GMT) (envelope-from fgast@howard.only640k.org) Received: from howard.only640k.org (howard.only640k.org [83.120.7.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB22F43D68; Thu, 8 Dec 2005 14:14:51 +0000 (GMT) (envelope-from fgast@howard.only640k.org) Received: from howard.only640k.org (fgast@localhost.only640k.org [127.0.0.1]) by howard.only640k.org (8.13.3/8.13.3) with ESMTP id jB8EEhVk023655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 8 Dec 2005 15:14:43 +0100 (CET) Received: (from fgast@localhost) by howard.only640k.org (8.13.3/8.13.3/Submit) id jB8EEge1001121; Thu, 8 Dec 2005 15:14:42 +0100 (CET) Date: Thu, 8 Dec 2005 15:14:42 +0100 From: fabian gast To: Vladimir Grebenschikov Message-ID: <20051208141442.GA12414@only640k.org> References: <1134035121.1229.22.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <1134035121.1229.22.camel@localhost> User-Agent: Mutt/1.4.2i X-Virus-Scanned: ClamAV 0.87/1205/Wed Dec 7 15:00:48 2005 on howard.only640k.org X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on howard.only640k.org Cc: current , freebsd-net Subject: Re: something wrong with either port net/iwi-firmare or iwi driver in tree on current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 14:14:58 -0000 Hi!=20 On Thu, Dec 08, 2005 at 12:45:21PM +0300, Vladimir Grebenschikov wrote: > Hi >=20 > It is happens on fresh 7-CURRENT. >=20 > $ man 4 iwi >=20 > ... > This driver requires firmware to be loaded before it will work. > You need > to install the net/iwi-firmware port before ifconfig(8) will work > ... >=20 i had the same here.=20 i just created /boot/firmeware and copied the firmware-files to it and iwi= =20 worked without iwicontrol. the firmware-path is specified in sys/dev/iwi/if_iwi.c fgast@hagbard:\> pwd /usr/src/sys/dev/iwi fgast@hagbard:\> grep -n boot/firmware * if_iwi.c:2563: snprintf(path, sizeof path, "/boot/firmware/%s.fw", name); hth. fabian=20 --=20 This signature is intentionally left blank. From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 14:57:02 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 790BD16A423 for ; Thu, 8 Dec 2005 14:57:02 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B1D243D67 for ; Thu, 8 Dec 2005 14:56:52 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3386560 for multiple; Thu, 08 Dec 2005 09:58:54 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB8EugW0071318; Thu, 8 Dec 2005 09:56:46 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Artemiev Igor Date: Thu, 8 Dec 2005 09:51:51 -0500 User-Agent: KMail/1.8.3 References: <20051206093020.691e1483.ai@bmc.brk.ru> <200512070816.46165.jhb@freebsd.org> <20051208090835.471a5584.ai@bmc.brk.ru> In-Reply-To: <20051208090835.471a5584.ai@bmc.brk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512080951.52387.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 14:57:02 -0000 On Thursday 08 December 2005 01:08 am, Artemiev Igor wrote: > On Wed, 7 Dec 2005 08:16:44 -0500 > > John Baldwin wrote: > > On Tuesday 06 December 2005 01:30 am, Artemiev Igor wrote: > > > I add pseudo-device amdpmsub because nForce2 have two SMBus > > > interfaces. Patch here: > > > > > > http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff > > > > > > dmesg output: > > > > > > amdpm0: port > > > 0xdc00-0xdc1f,0x5000-0x501f,0x5500 -0x551f irq 5 at device 1.1 on > > > pci0 smbus0: on amdpm0 > > > smb0: on smbus0 > > > amdpmsub0: on amdpm0 > > > smbus1: on amdpmsub0 > > > smb1: on smbus1 > > > > > > I`ve tested it with xmbmon and all works fine. > > > > Is there any reason you can't make smbus1 a childof amdpm0 directly > > and skip the amdpmsub0 device? > > I simply do not see any way to do it with current implementation of > ampdm(and also viapm, etc) & smbus, without modifying the smb->smbus->smb= us > driver interface. I may be wrong, but as far as I know, currently it's one > smb for one driver (smbus_* limitation) Hmm, it doesn't specify the child device, just the parent. *sigh* That's= =20 lame. You don't have to call it amdpmsub0 btw, you could just call it amdp= m1=20 if you wanted and have amdpm1 a child of amdpm0. All that would need to=20 change for that is the NF2_SUBDEV string and the DRIVER_MODULE line (it wou= ld=20 be DRIVER_MODULE(amdpm, amdpm, ...)). This has the added advantage that yo= u=20 don't have to patch smbus.c. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 14:57:04 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A88D316A420 for ; Thu, 8 Dec 2005 14:57:04 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EAC343D72 for ; Thu, 8 Dec 2005 14:56:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3386557 for multiple; Thu, 08 Dec 2005 09:58:52 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB8EugVx071318; Thu, 8 Dec 2005 09:56:43 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Darren Pilgrim" Date: Thu, 8 Dec 2005 09:37:21 -0500 User-Agent: KMail/1.8.3 References: <001801c5fb83$987529f0$642a15ac@smiley> In-Reply-To: <001801c5fb83$987529f0$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512080937.22418.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 14:57:04 -0000 On Wednesday 07 December 2005 06:11 pm, Darren Pilgrim wrote: > From: John Baldwin > > > No, PCI interrupts are level triggered. Individual APIC pins > > can be programmed to be edge-triggered, sure. However, then > > interrupts stop working if 2 devices are sharing a line and > > one interrupts after the other has already interrupted and > > after the second device's ISR has already run. In this case, > > the ithread will finish and go back to sleep waiting for an > > interrupt. However, since the ISR for the second device > > wasn't run after that device asserted its interrupt pin, the > > second device will keep the pin pulled low forever, so there > > will never be a hi -> low transition that the APIC pin would > > post an interrupt for and that intpin and all attached > > devices are effectively dead. > > What if the APIC was programmed to be edge-triggered just before the > ithread runs and programmed back to level-trigger when the ithread > completes? I'd rather work on my other solution which might be about 5 lines of code=20 rather than screw around with the APICs when that might have other side=20 effects. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 15:51:33 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75D6416A41F for ; Thu, 8 Dec 2005 15:51:33 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 612D843D7F for ; Thu, 8 Dec 2005 15:51:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id A51BC1A3C26 for ; Thu, 8 Dec 2005 07:51:27 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id EF621519E6; Thu, 8 Dec 2005 10:51:26 -0500 (EST) Date: Thu, 8 Dec 2005 10:51:26 -0500 From: Kris Kennaway To: current@FreeBSD.org Message-ID: <20051208155126.GB26759@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+g7M9IMkV8truYOl" Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Cc: Subject: [ports-i386@pointyhat.freebsd.org: electricfence-2.2.2 failed on i386 7] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 15:51:33 -0000 --+g7M9IMkV8truYOl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable FYI, some change to FreeBSD broke this port. Kris ----- Forwarded message from User Ports-i386 ----- X-Original-To: kkenn@localhost Delivered-To: kkenn@localhost.obsecurity.org X-Original-To: kris@FreeBSD.org Delivered-To: kris@FreeBSD.org Date: Thu, 8 Dec 2005 13:34:37 GMT From: User Ports-i386 To: krion@FreeBSD.org, kris@FreeBSD.org Subject: electricfence-2.2.2 failed on i386 7 X-UIDL: 9U5!!UI^!!!9l!!iUn!! X-Bogosity: Ham, tests=3Dbogofilter, spamicity=3D0.000000, version=3D0.96.6 building electricfence-2.2.2 on gohan15.freebsd.org in directory /x/tmp/7/chroot/43477 maintained by: ports@FreeBSD.org port directory: /usr/ports/devel/ElectricFence build started at Thu Dec 8 13:34:19 UTC 2005 FETCH_DEPENDS=3D PATCH_DEPENDS=3D EXTRACT_DEPENDS=3D BUILD_DEPENDS=3D RUN_DEPENDS=3D add_pkg =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D> ElectricFence-2.2.2.tar.gz doesn't seem to exist in /tmp/distfiles/. =3D> Attempting to fetch from ftp://ftp-master.freebsd.org/pub/FreeBSD/port= s/distfiles/. ElectricFence-2.2.2.tar.gz 27 kB 1697 kBps =3D> MD5 Checksum OK for ElectricFence-2.2.2.tar.gz. =3D> SHA256 Checksum OK for ElectricFence-2.2.2.tar.gz. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D add_pkg =3D=3D=3D> Extracting for electricfence-2.2.2 =3D> MD5 Checksum OK for ElectricFence-2.2.2.tar.gz. =3D> SHA256 Checksum OK for ElectricFence-2.2.2.tar.gz. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D add_pkg =3D=3D=3D> Patching for electricfence-2.2.2 =3D=3D=3D> Applying FreeBSD patches for electricfence-2.2.2 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D add_pkg =3D=3D=3D> Configuring for electricfence-2.2.2 =3D=3D=3D> Building for electricfence-2.2.2 cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -c efence.c -o efence.o cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -c page.c -o page.o cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -c print.c -o print.o print.c: In function `EF_Printv': print.c:114: warning: `char' is promoted to `int' when passed through `...' print.c:114: warning: (so you should pass `int' not `char' to `va_arg') print.c:114: note: if this code is reached, the program will abort rm -f libefence.a ar crv libefence.a efence.o page.o print.o a - efence.o a - page.o a - print.o cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -shared -Wl,-soname,libefence.so.0 -o libefence.so= .0.0 efence.o page.o print.o=20 cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -c tstheap.c -o tstheap.o rm -f tstheap cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS tstheap.o libefence.a -o tstheap=20 cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS -c eftest.c -o eftest.o rm -f eftest cc -O2 -fno-strict-aliasing -pipe -D__USE_BSD -g -fPIC -DPAGE_PROTECTION_= VIOLATED_SIGNAL=3DSIGBUS eftest.o libefence.a -o eftest=20 Testing Electric Fence. After the last test, it should print that the test has PASSED. EF_PROTECT_BELOW=3D && EF_PROTECT_FREE=3D && EF_ALIGNMENT=3D && ./eftest Segmentation fault (core dumped) *** Error code 139 Stop in /work/a/ports/devel/ElectricFence/work/ElectricFence-2.2.2. *** Error code 1 Stop in /a/ports/devel/ElectricFence. =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D build of /usr/ports/devel/ElectricFence ended at Thu Dec 8 13:34:32 UTC 20= 05 ----- End forwarded message ----- --+g7M9IMkV8truYOl Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmFZ+Wry0BWjoQKURArpvAKD2U0LLSUFHBzwoL1UuNViABbLqWgCgvFgS csM8Dwsr5PJ35ZDssiJZ7gM= =ikmU -----END PGP SIGNATURE----- --+g7M9IMkV8truYOl-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 18:16:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A656F16A420 for ; Thu, 8 Dec 2005 18:16:35 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: from mail.seekingfire.com (caliban.seekingfire.com [24.72.123.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id 000C543D79 for ; Thu, 8 Dec 2005 18:16:28 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id C648E59D; Thu, 8 Dec 2005 12:16:27 -0600 (CST) Date: Thu, 8 Dec 2005 12:16:27 -0600 From: Tillman Hodgson To: freebsd-current@freebsd.org Message-ID: <20051208181627.GM86838@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.11 Subject: Aftering updating from Dec 2 src, buildworld bombs with free() error on Dec 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 18:16:35 -0000 Cvsup'd this morning from cvsup8.FreeBSD.org. [root@thoth /usr/src]# uname -a FreeBSD thoth.seekingfire.com 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Dec 2 13:59:48 CST 2005 root@thoth.seekingfire.com:/usr/obj/usr/src/sys/THOTH i386 [root@thoth /usr/obj]# rm -rf usr/ [root@thoth /usr/src]# make buildworld make in free(): error: junk pointer, too high to make sense Abort trap: 6 (core dumped) [root@thoth /usr/src]# ls -l `which make` -r-xr-xr-x 1 root wheel 272884 Dec 2 20:57 /usr/bin/make [root@thoth /usr/obj]# cat /etc/make.conf | grep -v ^# | grep -v ^$ KERNCONF=THOTH KRB5_HOME= /usr/local/krb5 RANDOMIZE_MASTER_SITES=yes PERL_VER=5.8.6 PERL_VERSION=5.8.6 [root@thoth /usr/src]# ls -l /etc/malloc.conf lrwxr-xr-x 1 root wheel 2 Dec 7 20:02 /etc/malloc.conf -> aj (though it does same thing with /etc/malloc.conf removed for the default behaviour) -T From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 18:47:07 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFA8016A41F for ; Thu, 8 Dec 2005 18:47:07 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp2-g19.free.fr (smtp2-g19.free.fr [212.27.42.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5DB143D9C for ; Thu, 8 Dec 2005 18:46:52 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp2-g19.free.fr (Postfix) with ESMTP id 005D65D06A for ; Thu, 8 Dec 2005 19:46:50 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jB8IkTW2015049; Thu, 8 Dec 2005 19:46:32 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Thu, 8 Dec 2005 19:46:20 +0100 User-Agent: KMail/1.8.3 References: <20051208181627.GM86838@seekingfire.com> In-Reply-To: <20051208181627.GM86838@seekingfire.com> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200512081946.22340.thierry@herbelot.com> Cc: Tillman Hodgson Subject: Re: Aftering updating from Dec 2 src, buildworld bombs with free() error on Dec 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 18:47:08 -0000 Le Thursday 8 December 2005 19:16, Tillman Hodgson a écrit : > [root@thoth /usr/src]# make buildworld > make in free(): error: junk pointer, too high to make sense > Abort trap: 6 (core dumped) me too I also see make crashing with a free error, on my current box : I first thought it was a pilot error, then I was sidetracked and I did not take time to investigate. I last upgraded the box around 01/12 TfH From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 18:55:54 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 96D1116A423; Thu, 8 Dec 2005 18:55:54 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.bitfreak.org (mail.bitfreak.org [65.75.198.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id B800543D6A; Thu, 8 Dec 2005 18:55:46 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from smiley (mail.bitfreak.org [65.75.198.146]) by mail.bitfreak.org (Postfix) with ESMTP id 0127219F2C; Thu, 8 Dec 2005 10:55:35 -0800 (PST) From: "Darren Pilgrim" To: "'John Baldwin'" Date: Thu, 8 Dec 2005 10:55:27 -0800 Message-ID: <000101c5fc28$f791b520$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal In-Reply-To: <200512080937.22418.jhb@freebsd.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Cc: freebsd-current@freebsd.org Subject: RE: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 18:55:54 -0000 From: John Baldwin > On Wednesday 07 December 2005 06:11 pm, Darren Pilgrim wrote: > > What if the APIC was programmed to be edge-triggered just before the > > ithread runs and programmed back to level-trigger when the ithread > > completes? >=20 > I'd rather work on my other solution which might be about 5 lines of = code=20 > rather than screw around with the APICs when that might have other = side=20 > effects. My apologies, I didn't intend to come off as dictating design. I'm interested in the subject and it's rare to find people knowledgeable and willing to converse about more advanced topics. Like many others here, I have a very significant investment in hardware = to which this directly relates. I wanted to find out about the details of = the behavior I'm observing and the impact of various solutions as both a business man and a student of engineering. From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 19:05:46 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8BCE616A41F for ; Thu, 8 Dec 2005 19:05:46 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EEEC43D7D for ; Thu, 8 Dec 2005 19:05:28 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id E68A91A3C27; Thu, 8 Dec 2005 11:05:21 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 0752651593; Thu, 8 Dec 2005 14:05:21 -0500 (EST) Date: Thu, 8 Dec 2005 14:05:20 -0500 From: Kris Kennaway To: Thierry Herbelot Message-ID: <20051208190520.GA30123@xor.obsecurity.org> References: <20051208181627.GM86838@seekingfire.com> <200512081946.22340.thierry@herbelot.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IJpNTDwzlM2Ie8A6" Content-Disposition: inline In-Reply-To: <200512081946.22340.thierry@herbelot.com> User-Agent: Mutt/1.4.2.1i Cc: Tillman Hodgson , freebsd-current@freebsd.org Subject: Re: Aftering updating from Dec 2 src, buildworld bombs with free() error on Dec 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 19:05:46 -0000 --IJpNTDwzlM2Ie8A6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 08, 2005 at 07:46:20PM +0100, Thierry Herbelot wrote: > Le Thursday 8 December 2005 19:16, Tillman Hodgson a ?crit : >=20 > > [root@thoth /usr/src]# make buildworld > > make in free(): error: junk pointer, too high to make sense > > Abort trap: 6 (core dumped) >=20 > me too > I also see make crashing with a free error, on my current box : I first= =20 > thought it was a pilot error, then I was sidetracked and I did not take t= ime=20 > to investigate. >=20 > I last upgraded the box around 01/12 Make was broken in the above way for brief window..you probably upgraded at an unlucky time. Copy a working make from another system to bootstrap back to a working system. Kris --IJpNTDwzlM2Ie8A6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmIPwWry0BWjoQKURAvd/AKDmim9gy8xJ+l+a3CpdvAleDeImRQCbBa2P /5Dn0Pb5gwAQ280cv791sWM= =NWfh -----END PGP SIGNATURE----- --IJpNTDwzlM2Ie8A6-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 19:15:20 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9402F16A41F for ; Thu, 8 Dec 2005 19:15:20 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from centrmmtao04.cox.net (centrmmtao04.cox.net [70.168.83.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 090A243D70 for ; Thu, 8 Dec 2005 19:15:15 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by centrmmtao04.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051208191332.SDGZ8318.centrmmtao04.cox.net@mezz.mezzweb.com>; Thu, 8 Dec 2005 14:13:32 -0500 Date: Thu, 08 Dec 2005 13:15:57 -0600 To: "Artemiev Igor" References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> <20051208125359.17d7f47a.ai@bmc.brk.ru> From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <20051208125359.17d7f47a.ai@bmc.brk.ru> User-Agent: Opera M2/8.51 (Linux, build 1462) Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 19:15:20 -0000 On Thu, 08 Dec 2005 03:53:59 -0600, Artemiev Igor wrote: > On Thu, 08 Dec 2005 02:13:09 -0600 > "Jeremy Messenger" wrote: >> Thanks, I see you have added one of chipset (0x0084) that is what I >> have but mbmon couldn't pick up. Also, there is no /dev/smb*. > It's my mistake - i haven`t put MODULE_DEPEND for amdpmsub into amdp.c. > You need kldload smb BEFORE amdpm. Or add this line: > MODULE_DEPEND(amdpmsub, smbus, SMBUS_MINVER, SMBUS_PREFVER, > SMBUS_MAXVER) I can see /dev/smb* now, but I still can't use -S in mbmon. =============================== # kldstat Id Refs Address Size Name 1 15 0xc0400000 3b35a0 kernel 2 2 0xc07b4000 1aeac linux.ko 3 1 0xc07cf000 3bdffc nvidia.ko 4 1 0xc0b8d000 5b6b4 acpi.ko 5 1 0xc4419000 3000 smb.ko 6 3 0xc441c000 3000 smbus.ko 7 1 0xc441f000 3000 iicbus.ko 8 1 0xc4422000 4000 amdpm.ko # ls /dev | grep smb smb0 smb1 # mbmon -S No SMBus HWM available!! InitMBInfo: Unknown error: 0 =============================== /var/log/messages: =============================== Dec 8 13:04:51 mezz kernel: amdpm0: port 0xc400-0xc41f,0x5000-0x501f irq 23 at device 1.1 on pci0 Dec 8 13:04:51 mezz kernel: smbus0: on amdpm0 Dec 8 13:04:51 mezz kernel: smb0: on smbus0 Dec 8 13:04:51 mezz kernel: amdpmsub0: on amdpm0 Dec 8 13:04:51 mezz kernel: smbus1: on amdpmsub0 Dec 8 13:04:51 mezz kernel: smb1: on smbus1 =============================== Have you tried to do the kldunload amdpm yet? It will get FreeBSD crash and forced me to reboot. I don't have any debug in my kernel, so I can't provide the backtraces. Does amdpm needs the iic* stuff? I remember that one of my dead motherboard that use viapm required the iic* stuff. Cheers, Mezz >> Without use -S in mbmon, mbmon always work fine with and without >> your patch. > See above. I`ve updated the patch. -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 19:43:35 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA07316A420 for ; Thu, 8 Dec 2005 19:43:35 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 687C543D4C for ; Thu, 8 Dec 2005 19:43:12 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 08 Dec 2005 11:43:10 -0800 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.9) with ESMTP id jB8Jh9a2045956 for ; Thu, 8 Dec 2005 11:43:09 -0800 (PST) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id jB8Jh9d0045955 for current@freebsd.org; Thu, 8 Dec 2005 11:43:09 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200512081943.jB8Jh9d0045955@ambrisko.com> To: current@freebsd.org Date: Thu, 8 Dec 2005 11:43:09 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: Subject: Patch for FreeBSD 32bit running on 64bit for futimes for review X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 19:43:36 -0000 I'm looking for a review of fixing futimes when running on FreeBSD/i386 binary on FreeBSD/amd64. The problem is that tar uses this to set the time on files it is extracting. Without this shim the dates are messed up Jan 1 1970. This breaks a ports build of i386 on amd64 in a i386 chroot. Index: sys/compat/freebsd32/freebsd32_misc.c =================================================================== RCS file: /usr/local/cvsroot/freebsd/src/sys/compat/freebsd32/freebsd32_misc.c,v retrieving revision 1.38.2.1 diff -u -p -r1.38.2.1 freebsd32_misc.c --- sys/compat/freebsd32/freebsd32_misc.c 18 Jul 2005 19:49:48 -0000 1.38.2.1 +++ sys/compat/freebsd32/freebsd32_misc.c 8 Dec 2005 18:26:54 -0000 @@ -846,6 +846,28 @@ freebsd32_utimes(struct thread *td, stru } int +freebsd32_futimes(struct thread *td, struct freebsd32_futimes_args *uap) +{ + struct timeval32 s32[2]; + struct timeval s[2], *sp; + int error; + + if (uap->tptr != NULL) { + error = copyin(uap->tptr, s32, sizeof(s32)); + if (error) + return (error); + CP(s32[0], s[0], tv_sec); + CP(s32[0], s[0], tv_usec); + CP(s32[1], s[1], tv_sec); + CP(s32[1], s[1], tv_usec); + sp = s; + } else + sp = NULL; + return (kern_futimes(td, uap->fd, sp, UIO_SYSSPACE)); +} + + +int freebsd32_adjtime(struct thread *td, struct freebsd32_adjtime_args *uap) { struct timeval32 tv32; Index: sys/compat/freebsd32/syscalls.master =================================================================== RCS file: /usr/local/cvsroot/freebsd/src/sys/compat/freebsd32/syscalls.master,v retrieving revision 1.50.2.1 diff -u -p -r1.50.2.1 syscalls.master --- sys/compat/freebsd32/syscalls.master 20 Jul 2005 17:42:15 -0000 1.50.2.1 +++ sys/compat/freebsd32/syscalls.master 8 Dec 2005 18:26:55 -0000 @@ -366,7 +366,8 @@ 204 AUE_NULL MNOPROTO { int munlock(const void *addr, \ size_t len); } 205 AUE_NULL MNOPROTO { int undelete(char *path); } -206 AUE_NULL MNOPROTO { int futimes(int fd, struct timeval *tptr); } +206 AUE_NULL MSTD { int freebsd32_futimes(int fd, \ + struct timeval32 *tptr); } 207 AUE_NULL MNOPROTO { int getpgid(pid_t pid); } 208 AUE_NULL UNIMPL newreboot (NetBSD) 209 AUE_NULL MNOPROTO { int poll(struct pollfd *fds, u_int nfds, \ If this is correct, then it looks like I commit this then commit the generated files after. Thanks, Doug A. From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 19:46:14 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8203016A41F for ; Thu, 8 Dec 2005 19:46:14 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 665AA43D83 for ; Thu, 8 Dec 2005 19:46:06 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id 53F8440806 for ; Thu, 8 Dec 2005 20:45:53 +0100 (CET) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id jB8JjfoZ027311; Thu, 8 Dec 2005 20:45:43 +0100 (CET) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Thu, 8 Dec 2005 20:45:32 +0100 User-Agent: KMail/1.8.3 References: <20051208181627.GM86838@seekingfire.com> <200512081946.22340.thierry@herbelot.com> <20051208190520.GA30123@xor.obsecurity.org> In-Reply-To: <20051208190520.GA30123@xor.obsecurity.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200512082045.34388.thierry@herbelot.com> Cc: Tillman Hodgson , Kris Kennaway Subject: Re: Aftering updating from Dec 2 src, buildworld bombs with free() error on Dec 8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 19:46:14 -0000 Le Thursday 8 December 2005 20:05, Kris Kennaway a écrit : > > Make was broken in the above way for brief window..you probably > upgraded at an unlucky time. Copy a working make from another system > to bootstrap back to a working system. good news indeed ! I'll have a look ASAP Thanks TfH From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 20:57:16 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6BDB316A422 for ; Thu, 8 Dec 2005 20:57:16 +0000 (GMT) (envelope-from lexa@wincmd.ru) Received: from kunnilinux.birulevo.net (kunnilinux.birulevo.net [195.54.208.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39AB743D79 for ; Thu, 8 Dec 2005 20:57:09 +0000 (GMT) (envelope-from lexa@wincmd.ru) Received: (qmail 28834 invoked by uid 210); 8 Dec 2005 23:57:02 +0300 Received: from 10.4.22.222 by kunnilinux (envelope-from , uid 201) with qmail-scanner-1.25st (clamdscan: 0.87.1/1205. spamassassin: 3.1.0. perlscan: 1.25st. Clear:RC:1(10.4.22.222):. Processed in 0.129149 secs); 08 Dec 2005 20:57:02 -0000 Received: from unknown (HELO ?192.0.0.1?) (10.4.22.222) by kunnilinux.birulevo.net with SMTP; 8 Dec 2005 23:57:02 +0300 Message-ID: <43989E20.80204@wincmd.ru> Date: Thu, 08 Dec 2005 23:57:04 +0300 From: Tarasov Alexey User-Agent: Thunderbird 1.5 (X11/20051110) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Problem with running Linux applications X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 20:57:16 -0000 Hello! I have a problem with running Linux applications under FreeBSD-Current: > uname -a > FreeBSD amd64.lexasoft.birulevo.net 7.0-CURRENT FreeBSD 7.0-CURRENT > #6: Thu Dec 8 23:17:06 MSK 2005 > lexa@amd64.lexasoft.birulevo.net:/usr/obj/usr/src/sys/Lexasoft i386 When I try to run application I get the following messages: > /usr/X11R6/lib/ut2004-demo/System>./ut2004-bin > ./ut2004-bin: error while loading shared libraries: > /usr/lib/libstdc++.so.5: ELF file OS ABI invalid How can I fix it? -- Best regards, Tarasov Alexey. From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 21:38:43 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DD9416A432; Thu, 8 Dec 2005 21:38:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7152B43D7D; Thu, 8 Dec 2005 21:38:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp133-7.lns2.adl2.internode.on.net [59.167.133.7]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id jB8Lc65C013835 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 9 Dec 2005 08:08:07 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 9 Dec 2005 08:07:51 +1030 User-Agent: KMail/1.8.2 References: <43989E20.80204@wincmd.ru> In-Reply-To: <43989E20.80204@wincmd.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1272395.tvNZhWm6du"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512090807.59737.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Tarasov Alexey , current@freebsd.org Subject: Re: Problem with running Linux applications X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 21:38:43 -0000 --nextPart1272395.tvNZhWm6du Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 9 Dec 2005 07:27, Tarasov Alexey wrote: > When I try to run application I get the following messages: > > /usr/X11R6/lib/ut2004-demo/System>./ut2004-bin > > ./ut2004-bin: error while loading shared libraries: > > /usr/lib/libstdc++.so.5: ELF file OS ABI invalid > > How can I fix it? Looks like the UT2K4 binary is not marked (with brandlef) as a Linux=20 application. Run brandelf -t Linux ut2004-bin =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1272395.tvNZhWm6du Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDmKe35ZPcIHs/zowRAloYAKCNLRwjz6iszMG2E4kGAuN42ilPoQCgjRck 4Io21+c55pUYhuSDNaWYETM= =fWdo -----END PGP SIGNATURE----- --nextPart1272395.tvNZhWm6du-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 21:38:43 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4DD9416A432; Thu, 8 Dec 2005 21:38:43 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7152B43D7D; Thu, 8 Dec 2005 21:38:25 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp133-7.lns2.adl2.internode.on.net [59.167.133.7]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id jB8Lc65C013835 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 9 Dec 2005 08:08:07 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 9 Dec 2005 08:07:51 +1030 User-Agent: KMail/1.8.2 References: <43989E20.80204@wincmd.ru> In-Reply-To: <43989E20.80204@wincmd.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1272395.tvNZhWm6du"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200512090807.59737.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Tarasov Alexey , current@freebsd.org Subject: Re: Problem with running Linux applications X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 21:38:43 -0000 --nextPart1272395.tvNZhWm6du Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 9 Dec 2005 07:27, Tarasov Alexey wrote: > When I try to run application I get the following messages: > > /usr/X11R6/lib/ut2004-demo/System>./ut2004-bin > > ./ut2004-bin: error while loading shared libraries: > > /usr/lib/libstdc++.so.5: ELF file OS ABI invalid > > How can I fix it? Looks like the UT2K4 binary is not marked (with brandlef) as a Linux=20 application. Run brandelf -t Linux ut2004-bin =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1272395.tvNZhWm6du Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDmKe35ZPcIHs/zowRAloYAKCNLRwjz6iszMG2E4kGAuN42ilPoQCgjRck 4Io21+c55pUYhuSDNaWYETM= =fWdo -----END PGP SIGNATURE----- --nextPart1272395.tvNZhWm6du-- From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 22:14:16 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0047916A41F for ; Thu, 8 Dec 2005 22:14:15 +0000 (GMT) (envelope-from marcus@blazingdot.com) Received: from marklar.blazingdot.com (marklar.blazingdot.com [207.154.84.83]) by mx1.FreeBSD.org (Postfix) with SMTP id 1EA8B43D75 for ; Thu, 8 Dec 2005 22:14:10 +0000 (GMT) (envelope-from marcus@blazingdot.com) Received: (qmail 25034 invoked by uid 503); 8 Dec 2005 22:14:09 -0000 Date: Thu, 8 Dec 2005 14:14:09 -0800 From: Marcus Reid To: freebsd-current@freebsd.org Message-ID: <20051208221409.GA24685@blazingdot.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Coffee-Level: nearly-fatal User-Agent: Mutt/1.5.6i Subject: .snap in daily_clean_tmps_ignore? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 22:14:16 -0000 Hi, Shouldn't '.snap' be included in daily_clean_tmps_ignore in /etc/defaults/periodic.conf? Marcus From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 23:26:31 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0C1D616A41F; Thu, 8 Dec 2005 23:26:31 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56DBA43D72; Thu, 8 Dec 2005 23:26:25 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB8NQIv0077029; Thu, 8 Dec 2005 18:26:18 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB8NQIhA032686; Thu, 8 Dec 2005 18:26:18 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id F39237302F; Thu, 8 Dec 2005 18:26:17 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051208232617.F39237302F@freebsd-current.sentex.ca> Date: Thu, 8 Dec 2005 18:26:17 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 23:26:31 -0000 TB --- 2005-12-08 22:14:11 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-08 22:14:11 - starting HEAD tinderbox run for alpha/alpha TB --- 2005-12-08 22:14:11 - cleaning the object tree TB --- 2005-12-08 22:14:42 - checking out the source tree TB --- 2005-12-08 22:14:42 - cd /tinderbox/HEAD/alpha/alpha TB --- 2005-12-08 22:14:42 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-08 22:20:51 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-08 22:20:51 - cd /src TB --- 2005-12-08 22:20:51 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-08 23:25:52 - generating LINT kernel config TB --- 2005-12-08 23:25:52 - cd /src/sys/alpha/conf TB --- 2005-12-08 23:25:52 - /usr/bin/make -B LINT TB --- 2005-12-08 23:25:53 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-08 23:25:53 - cd /src TB --- 2005-12-08 23:25:53 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Dec 8 23:25:53 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/alpha/alpha/genassym.c:61: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-08 23:26:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-08 23:26:17 - ERROR: failed to build lint kernel TB --- 2005-12-08 23:26:17 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Thu Dec 8 23:55:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6EDAA16A41F for ; Thu, 8 Dec 2005 23:55:30 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABCCA43D4C for ; Thu, 8 Dec 2005 23:55:26 +0000 (GMT) (envelope-from joao.barros@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so540047wxc for ; Thu, 08 Dec 2005 15:55:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=jt9nPGrLf1d5+IP9rYBJse9Ov3JOw/zXoXUWi9s5UqdhSqGjZc2nCXpYH9gSQdfQ8ANjlfTYt5YyV2ZNGJZf8/qHpXbQosaW5MsUFsTE4xt6UoKxBKscqjTwSGrOPWK3/+D/HBK44SFgBCTEY04ns5x3i23cxQo7+sU/cNIIx34= Received: by 10.70.15.13 with SMTP id 13mr4541764wxo; Thu, 08 Dec 2005 15:55:23 -0800 (PST) Received: by 10.70.36.7 with HTTP; Thu, 8 Dec 2005 15:55:23 -0800 (PST) Message-ID: <70e8236f0512081555h1f9be18fq57b9ed73d96cddb2@mail.gmail.com> Date: Thu, 8 Dec 2005 23:55:23 +0000 From: Joao Barros To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cc: Subject: [dhclient] connection closed, exiting X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 23:55:30 -0000 I have a Sun Ultra5 as my home gateway. After upgrading to 6.0 from 5.4 I started getting problems with dhclient (I know it went from v3 to v2 imported from OpenBSD) If my cablemodem dies without signal or something of the sort dhclient exits like this: Dec 8 18:38:24 ultra5 dhclient[198]: connection closed Dec 8 18:38:24 ultra5 dhclient[198]: exiting. Some cablemodems reset the ethernet interface on their bootup or sync sequence but since the machine is connected to a switch I take it it's not an interface connection we're talking about. On 5.4 I could kill the modem for hours and dhclient would stay there (as it should) trying to get a lease. On 6.0 I just have to silence the modem for a few moments and dhclient gives up and goes away. I couldn't find a knob for this on the manual. Sometimes it gets even better, when dhclient has saved (but already expired leases) and uses them setting the IP on the interface, but since the IP is not valid it doesn't work. And it stays with that lease until I restart it and it gets a valid one. I had signal problems the last few days and the leases db it's like this: ultra5# grep lease /var/db/dhclient.leases.fxp1 | wc -l 10 How can I: - tell dhclient not to exit. - tell dhclient not to use expired leases, or not to use saved leases at al= l. -- Joao Barros From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 01:04:27 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E459816A41F; Fri, 9 Dec 2005 01:04:27 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2546743D6A; Fri, 9 Dec 2005 01:04:26 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jB914Pse028988; Thu, 8 Dec 2005 20:04:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB914Pwe076978; Thu, 8 Dec 2005 20:04:25 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 514D67302F; Thu, 8 Dec 2005 20:04:25 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209010425.514D67302F@freebsd-current.sentex.ca> Date: Thu, 8 Dec 2005 20:04:25 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 01:04:28 -0000 TB --- 2005-12-08 23:26:18 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-08 23:26:18 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-08 23:26:18 - cleaning the object tree TB --- 2005-12-08 23:26:55 - checking out the source tree TB --- 2005-12-08 23:26:55 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-08 23:26:55 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-08 23:33:00 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-08 23:33:00 - cd /src TB --- 2005-12-08 23:33:00 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-09 01:03:54 - generating LINT kernel config TB --- 2005-12-09 01:03:54 - cd /src/sys/amd64/conf TB --- 2005-12-09 01:03:54 - /usr/bin/make -B LINT TB --- 2005-12-09 01:03:54 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 01:03:54 - cd /src TB --- 2005-12-09 01:03:54 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 01:03:55 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/amd64/amd64/genassym.c:60: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 01:04:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 01:04:25 - ERROR: failed to build lint kernel TB --- 2005-12-09 01:04:25 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 02:16:20 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65EAA16A41F; Fri, 9 Dec 2005 02:16:20 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9A4643D76; Fri, 9 Dec 2005 02:16:13 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB92GCcH086564; Thu, 8 Dec 2005 21:16:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB92GC1I056471; Thu, 8 Dec 2005 21:16:12 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 8DBA37302F; Thu, 8 Dec 2005 21:16:12 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> Date: Thu, 8 Dec 2005 21:16:12 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 02:16:21 -0000 TB --- 2005-12-09 01:04:25 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 01:04:25 - starting HEAD tinderbox run for i386/i386 TB --- 2005-12-09 01:04:25 - cleaning the object tree TB --- 2005-12-09 01:05:01 - checking out the source tree TB --- 2005-12-09 01:05:01 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-12-09 01:05:01 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 01:10:52 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 01:10:52 - cd /src TB --- 2005-12-09 01:10:52 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-09 02:15:40 - generating LINT kernel config TB --- 2005-12-09 02:15:40 - cd /src/sys/i386/conf TB --- 2005-12-09 02:15:40 - /usr/bin/make -B LINT TB --- 2005-12-09 02:15:40 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 02:15:40 - cd /src TB --- 2005-12-09 02:15:40 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 02:15:40 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/i386/i386/genassym.c:63: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 02:16:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 02:16:12 - ERROR: failed to build lint kernel TB --- 2005-12-09 02:16:12 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 03:27:42 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66B7B16A41F; Fri, 9 Dec 2005 03:27:42 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C92C43D7C; Fri, 9 Dec 2005 03:27:37 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB93Ra9j090522; Thu, 8 Dec 2005 22:27:36 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB93RaRF031572; Thu, 8 Dec 2005 22:27:36 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 1D7227302F; Thu, 8 Dec 2005 22:27:36 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209032736.1D7227302F@freebsd-current.sentex.ca> Date: Thu, 8 Dec 2005 22:27:36 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 03:27:42 -0000 TB --- 2005-12-09 02:16:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 02:16:12 - starting HEAD tinderbox run for i386/pc98 TB --- 2005-12-09 02:16:12 - cleaning the object tree TB --- 2005-12-09 02:16:43 - checking out the source tree TB --- 2005-12-09 02:16:43 - cd /tinderbox/HEAD/i386/pc98 TB --- 2005-12-09 02:16:44 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 02:22:41 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 02:22:41 - cd /src TB --- 2005-12-09 02:22:41 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-09 03:27:06 - generating LINT kernel config TB --- 2005-12-09 03:27:06 - cd /src/sys/pc98/conf TB --- 2005-12-09 03:27:06 - /usr/bin/make -B LINT TB --- 2005-12-09 03:27:06 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 03:27:06 - cd /src TB --- 2005-12-09 03:27:06 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 03:27:06 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/i386/i386/genassym.c:63: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 03:27:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 03:27:35 - ERROR: failed to build lint kernel TB --- 2005-12-09 03:27:35 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 04:30:34 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A8A216A420 for ; Fri, 9 Dec 2005 04:30:34 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 344CC43D46 for ; Fri, 9 Dec 2005 04:30:24 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3427614 for multiple; Thu, 08 Dec 2005 23:32:18 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB94U7Rg076451; Thu, 8 Dec 2005 23:30:09 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: "Darren Pilgrim" Date: Thu, 8 Dec 2005 23:26:36 -0500 User-Agent: KMail/1.8.3 References: <000101c5fc28$f791b520$642a15ac@smiley> In-Reply-To: <000101c5fc28$f791b520$642a15ac@smiley> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512082326.37351.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-current@freebsd.org Subject: Re: can someone explain...[ PCI interrupts] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 04:30:34 -0000 On Thursday 08 December 2005 01:55 pm, Darren Pilgrim wrote: > From: John Baldwin > > > On Wednesday 07 December 2005 06:11 pm, Darren Pilgrim wrote: > > > What if the APIC was programmed to be edge-triggered just before the > > > ithread runs and programmed back to level-trigger when the ithread > > > completes? > > > > I'd rather work on my other solution which might be about 5 lines of co= de > > rather than screw around with the APICs when that might have other side > > effects. > > My apologies, I didn't intend to come off as dictating design. I'm > interested in the subject and it's rare to find people knowledgeable and > willing to converse about more advanced topics. > > Like many others here, I have a very significant investment in hardware to > which this directly relates. I wanted to find out about the details of t= he > behavior I'm observing and the impact of various solutions as both a > business man and a student of engineering. In fairness, Linux does seem to mess with the APICs this way (set to edge w= hen=20 an interrupt comes in and then reset it to level) to work around a bug on=20 some older I/O APICs. I'm not sure / can't remember if they do it for all= =20 PCI interrupts on APICs though. I need to look at the docs for the PXH=20 bridges in question again, but I think that when it does the legacy INTx=20 thing it is swizzling the interrupts to the bridge's INTx pins using the=20 standard PCI-PCI swizzle, in which case patching around the routing is a=20 simple patch of changing the $PIR and MPTable drivers to ignore such bridge= s=20 based on the devid, and changing the ACPI PCI-PCI bridge driver to ignore t= he=20 _PRT for such bridges. Fortunately, one of my recently added test machines= =20 reproduces the problem so I can test this idea and give people a patch that= =20 at least somewhat works for further testing. Maybe in a day or so. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 04:42:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7D9DB16A428; Fri, 9 Dec 2005 04:42:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 471DF43D79; Fri, 9 Dec 2005 04:42:32 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jB94gUSn045231; Thu, 8 Dec 2005 23:42:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jB94gUj3013661; Thu, 8 Dec 2005 23:42:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 7418B7302F; Thu, 8 Dec 2005 23:42:30 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209044230.7418B7302F@freebsd-current.sentex.ca> Date: Thu, 8 Dec 2005 23:42:30 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 04:42:45 -0000 TB --- 2005-12-09 03:27:36 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 03:27:36 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2005-12-09 03:27:36 - cleaning the object tree TB --- 2005-12-09 03:28:06 - checking out the source tree TB --- 2005-12-09 03:28:06 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2005-12-09 03:28:06 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 03:34:17 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 03:34:17 - cd /src TB --- 2005-12-09 03:34:17 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-09 04:39:29 - generating LINT kernel config TB --- 2005-12-09 04:39:29 - cd /src/sys/sparc64/conf TB --- 2005-12-09 04:39:29 - /usr/bin/make -B LINT TB --- 2005-12-09 04:39:29 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 04:39:29 - cd /src TB --- 2005-12-09 04:39:29 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 04:39:29 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/contrib/altq/altq/altq_cbq.c -I/src/sys/contrib/pf In file included from /src/sys/contrib/altq/altq/altq_cbq.c:47: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 04:42:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 04:42:30 - ERROR: failed to build lint kernel TB --- 2005-12-09 04:42:30 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 07:55:33 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9FF916A41F; Fri, 9 Dec 2005 07:55:33 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6063643D91; Fri, 9 Dec 2005 07:55:17 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jB97tF62094113; Fri, 9 Dec 2005 09:55:15 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 42018-03-3; Fri, 9 Dec 2005 09:55:13 +0200 (EET) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jB97sQFE094059 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Dec 2005 09:54:26 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jB97sVBx020038; Fri, 9 Dec 2005 09:54:31 +0200 (EET) (envelope-from ru) Date: Fri, 9 Dec 2005 09:54:30 +0200 From: Ruslan Ermilov To: FreeBSD Tinderbox Message-ID: <20051209075430.GG33744@ip.net.ua> References: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Qf1oXS95uex85X0R" Content-Disposition: inline In-Reply-To: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: current@freebsd.org, i386@freebsd.org Subject: Re: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 07:55:34 -0000 --Qf1oXS95uex85X0R Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 08, 2005 at 09:16:12PM -0500, FreeBSD Tinderbox wrote: > >>> Kernel build for LINT started on Fri Dec 9 02:15:40 UTC 2005 > >>> stage 1: configuring the kernel > >>> stage 2.1: cleaning up the object tree > >>> stage 2.2: rebuilding the object tree > >>> stage 2.3: build tools > >>> stage 3.1: making dependencies > [...] > from /src/sys/net/if.h:390, > from /src/sys/i386/i386/genassym.c:63: > /src/sys/sys/mbuf.h: In function `m_getjcl': > /src/sys/sys/mbuf.h:424: error: duplicate case value > /src/sys/sys/mbuf.h:421: error: previously used here > /src/sys/sys/mbuf.h: In function `m_cljget': > /src/sys/sys/mbuf.h:488: error: duplicate case value > /src/sys/sys/mbuf.h:485: error: previously used here > *** Error code 1 >=20 > Stop in /obj/src/sys/LINT. > *** Error code 1 >=20 > Stop in /src. > *** Error code 1 >=20 > Stop in /src. > TB --- 2005-12-09 02:16:12 - WARNING: /usr/bin/make returned exit code 1= =20 > TB --- 2005-12-09 02:16:12 - ERROR: failed to build lint kernel > TB --- 2005-12-09 02:16:12 - tinderbox aborted MCLBYTES is a tunable value, so I sent the following patch to Andre: %%% Index: mbuf.h =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D RCS file: /home/ncvs/src/sys/sys/mbuf.h,v retrieving revision 1.183 diff -u -p -r1.183 mbuf.h --- mbuf.h 8 Dec 2005 13:13:05 -0000 1.183 +++ mbuf.h 9 Dec 2005 07:51:50 -0000 @@ -421,15 +421,21 @@ m_getjcl(int how, short type, int flags, case MCLBYTES: zone =3D zone_clust; break; +#if MJUM4BYTES !=3D MCLBYTES case MJUM4BYTES: zone =3D zone_jumbo4; break; +#endif +#if MJUM9BYTES !=3D MCLBYTES case MJUM9BYTES: zone =3D zone_jumbo9; break; +#endif +#if MJUM16BYTES !=3D MCLBYTES case MJUM16BYTES: zone =3D zone_jumbo16; break; +#endif default: panic("%s: m_getjcl: invalid cluster type", __func__); } @@ -485,15 +491,21 @@ m_cljget(struct mbuf *m, int how, int si case MCLBYTES: zone =3D zone_clust; break; +#if MJUM4BYTES !=3D MCLBYTES case MJUM4BYTES: zone =3D zone_jumbo4; break; +#endif +#if MJUM9BYTES !=3D MCLBYTES case MJUM9BYTES: zone =3D zone_jumbo9; break; +#endif +#if MJUM16BYTES !=3D MCLBYTES case MJUM16BYTES: zone =3D zone_jumbo16; break; +#endif default: panic("%s: m_getjcl: invalid cluster type", __func__); } %%% Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Qf1oXS95uex85X0R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDmTg2qRfpzJluFF4RAjmoAJ9AoQMNgdrO7xA4LyPr5Ge5N0thdgCdH42S E1jOc78aPJn/X6liifRymNQ= =EqvO -----END PGP SIGNATURE----- --Qf1oXS95uex85X0R-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 08:03:46 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D03E916A41F; Fri, 9 Dec 2005 08:03:46 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6531A43D6B; Fri, 9 Dec 2005 08:03:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jB983eu7088311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Dec 2005 11:03:41 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jB983eOi088310; Fri, 9 Dec 2005 11:03:40 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 9 Dec 2005 11:03:39 +0300 From: Gleb Smirnoff To: Ruslan Ermilov Message-ID: <20051209080339.GH37414@FreeBSD.org> References: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> <20051209075430.GG33744@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051209075430.GG33744@ip.net.ua> User-Agent: Mutt/1.5.6i Cc: i386@FreeBSD.org, andre@FreeBSD.org, FreeBSD Tinderbox , current@FreeBSD.org Subject: Re: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 08:03:47 -0000 On Fri, Dec 09, 2005 at 09:54:30AM +0200, Ruslan Ermilov wrote: R> MCLBYTES is a tunable value, so I sent the following patch to Andre: R> R> %%% R> Index: mbuf.h Same change also required to kern_mbuf.c. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 08:09:43 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6D7CE16A41F; Fri, 9 Dec 2005 08:09:43 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (cell.sick.ru [217.72.144.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86F7D43D77; Fri, 9 Dec 2005 08:09:42 +0000 (GMT) (envelope-from glebius@FreeBSD.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.13.3/8.13.3) with ESMTP id jB989eWl088492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Dec 2005 11:09:40 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jB989e6k088491; Fri, 9 Dec 2005 11:09:40 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Fri, 9 Dec 2005 11:09:39 +0300 From: Gleb Smirnoff To: FreeBSD Tinderbox Message-ID: <20051209080939.GI37414@FreeBSD.org> References: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> User-Agent: Mutt/1.5.6i Cc: current@FreeBSD.org, davidxu@FreeBSD.org Subject: Re: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 08:09:43 -0000 btw, Andre's breakage has masked another one, by David: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/kern/kern_time.c /usr/src/sys/kern/kern_time.c:90: error: conflicting types for 'itimers_event_hook' /usr/src/sys/sys/timers.h:115: error: previous declaration of 'itimers_event_hook' was here /usr/src/sys/kern/kern_time.c:90: error: conflicting types for 'itimers_event_hook' /usr/src/sys/sys/timers.h:115: error: previous declaration of 'itimers_event_hook' was here *** Error code 1 -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 08:21:18 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8EE4216A426; Fri, 9 Dec 2005 08:21:18 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9647243D49; Fri, 9 Dec 2005 08:20:50 +0000 (GMT) (envelope-from davidxu@freebsd.org) Received: from [127.0.0.1] (davidxu@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jB98KbLD086801; Fri, 9 Dec 2005 08:20:38 GMT (envelope-from davidxu@freebsd.org) Message-ID: <43993E59.4080706@freebsd.org> Date: Fri, 09 Dec 2005 16:20:41 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20050928 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gleb Smirnoff References: <20051209021612.8DBA37302F@freebsd-current.sentex.ca> <20051209080939.GI37414@FreeBSD.org> In-Reply-To: <20051209080939.GI37414@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 08:21:18 -0000 Gleb Smirnoff wrote: > btw, Andre's breakage has masked another one, by David: > > cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror /usr/src/sys/kern/kern_time.c > /usr/src/sys/kern/kern_time.c:90: error: conflicting types for 'itimers_event_hook' > /usr/src/sys/sys/timers.h:115: error: previous declaration of 'itimers_event_hook' was here > /usr/src/sys/kern/kern_time.c:90: error: conflicting types for 'itimers_event_hook' > /usr/src/sys/sys/timers.h:115: error: previous declaration of 'itimers_event_hook' was here > *** Error code 1 > Sorry, fixed! please try again. From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 11:36:50 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6104F16A425 for ; Fri, 9 Dec 2005 11:36:50 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 968E643D67 for ; Fri, 9 Dec 2005 11:36:43 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Fri, 9 Dec 2005 14:36:34 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051209143634.09bc2d90.ai@bmc.brk.ru> In-Reply-To: <200512080951.52387.jhb@freebsd.org> References: <20051206093020.691e1483.ai@bmc.brk.ru> <200512070816.46165.jhb@freebsd.org> <20051208090835.471a5584.ai@bmc.brk.ru> <200512080951.52387.jhb@freebsd.org> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 11:36:50 -0000 On Thu, 8 Dec 2005 09:51:51 -0500 John Baldwin wrote: > > I simply do not see any way to do it with current implementation of > > ampdm(and also viapm, etc) & smbus, without modifying the smb- > > >smbus->smbus driver interface. I may be wrong, but as far as I > > >know, currently it's one > > smb for one driver (smbus_* limitation) > > Hmm, it doesn't specify the child device, just the parent. *sigh* > That's lame. You don't have to call it amdpmsub0 btw, you could just > call it amdpm1 if you wanted and have amdpm1 a child of amdpm0. All > that would need to change for that is the NF2_SUBDEV string and the > DRIVER_MODULE line (it would be DRIVER_MODULE(amdpm, amdpm, ...)). > This has the added advantage that you don't have to patch smbus.c. I remade it as you described - can't understand, why I didn't think about it myself -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 11:51:00 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E091C16A41F for ; Fri, 9 Dec 2005 11:51:00 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7AA1343D7D for ; Fri, 9 Dec 2005 11:50:58 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Fri, 9 Dec 2005 14:50:53 +0300 From: Artemiev Igor To: "Jeremy Messenger" Message-Id: <20051209145053.1cf47b3e.ai@bmc.brk.ru> In-Reply-To: References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> <20051208125359.17d7f47a.ai@bmc.brk.ru> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 11:51:01 -0000 On Thu, 08 Dec 2005 13:15:57 -0600 "Jeremy Messenger" wrote: > I can see /dev/smb* now, but I still can't use -S in mbmon. > # mbmon -S > No SMBus HWM available!! > InitMBInfo: Unknown error: 0 Try invoke mbmon with -p . Mbmon doesn`t know your monitor chip. > Have you tried to do the kldunload amdpm yet? It will get FreeBSD > crash and forced me to reboot. I don't have any debug in my kernel, > so I can't provide the backtraces. Does amdpm needs the iic* stuff? I > remember that one of my dead motherboard that use viapm required the > iic* stuff. It`s strange. kldunload is working in my case. Could your provide kernel backtrace? -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 12:35:30 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 827E416A423 for ; Fri, 9 Dec 2005 12:35:30 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4CD5343D46 for ; Fri, 9 Dec 2005 12:35:15 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) by newtrinity.zeist.de (8.12.11/8.12.11/ZEIST.DE) with ESMTP id jB9CYJrK018883; Fri, 9 Dec 2005 13:34:23 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id jB9CYEXO018882; Fri, 9 Dec 2005 13:34:14 +0100 (CET) (envelope-from marius) Date: Fri, 9 Dec 2005 13:34:13 +0100 From: Marius Strobl To: Artemiev Igor Message-ID: <20051209133413.A22673@newtrinity.zeist.de> References: <20051206093020.691e1483.ai@bmc.brk.ru> <20051207095818.0b307c89.ai@bmc.brk.ru> <20051208091422.4d1a3ee0.ai@bmc.brk.ru> <20051208125359.17d7f47a.ai@bmc.brk.ru> <20051209145053.1cf47b3e.ai@bmc.brk.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20051209145053.1cf47b3e.ai@bmc.brk.ru>; from ai@bmc.brk.ru on Fri, Dec 09, 2005 at 02:50:53PM +0300 X-AntiVirus-modified: yes X-AntiVirus: checked by AntiVir Milter (version: 1.1.1-9; AVE: 6.33.0.11; VDF: 6.33.0.15; host: newtrinity.zeist.de) Cc: Jeremy Messenger , freebsd-current@freebsd.org Subject: Re: [PATCH] nForce2 SMBus support - nForce3/4 support added. Not tested yet X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 12:35:30 -0000 On Fri, Dec 09, 2005 at 02:50:53PM +0300, Artemiev Igor wrote: > > On Thu, 08 Dec 2005 13:15:57 -0600 > "Jeremy Messenger" wrote: > > I can see /dev/smb* now, but I still can't use -S in mbmon. > > # mbmon -S > > No SMBus HWM available!! > > InitMBInfo: Unknown error: 0 > Try invoke mbmon with -p . Mbmon doesn`t know your monitor chip. > > > Have you tried to do the kldunload amdpm yet? It will get FreeBSD > > crash and forced me to reboot. I don't have any debug in my kernel, > > so I can't provide the backtraces. Does amdpm needs the iic* stuff? I > > remember that one of my dead motherboard that use viapm required the > > iic* stuff. > It`s strange. kldunload is working in my case. Could your provide kernel > backtrace? > I guess the problem is that mbmon was compiled without SMBus support. The xmbmon port checks for the presence of in order to determine whether to enable SMBus support but apparently that header was renamed to sometime while FreeBSD 5 was -CURRENT. Marius -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details. From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 12:48:57 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A07E16A41F; Fri, 9 Dec 2005 12:48:57 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6B9F43D96; Fri, 9 Dec 2005 12:48:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [192.168.1.66] (p3248-ipad30akatuka.ibaraki.ocn.ne.jp [60.33.34.248]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jB9Clsdu010363 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 9 Dec 2005 04:47:58 -0800 Message-ID: <43997CEC.1070607@root.org> Date: Fri, 09 Dec 2005 21:47:40 +0900 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> <86d5k9eric.fsf@xps.des.no> In-Reply-To: <86d5k9eric.fsf@xps.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 12:48:57 -0000 Dag-Erling Smørgrav wrote: > Nate Lawson writes: > >>I'd prefer to move forward, not backward. When using AC modes, it is >>an advantage to be devd-driven. The current implementation is not >>right, I agree, but there shouldn't be any actual problem other than >>suboptimal performance. Changing the thread to be a select() seems >>good. I welcome any patches. > > > You're welcome. > > powerd is a mess, BTW. I've tried to fix the most blatant mistakes > (poor understanding of signal handling), but it basically needs a > rewrite. My comments below. Overall I like this approach and just have a few questions. > ------------------------------------------------------------------------ > > Index: usr.sbin/powerd/Makefile > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/powerd/Makefile,v > retrieving revision 1.4 > diff -u -r1.4 Makefile > --- usr.sbin/powerd/Makefile 19 Oct 2005 04:48:44 -0000 1.4 > +++ usr.sbin/powerd/Makefile 6 Dec 2005 23:20:44 -0000 > @@ -3,9 +3,12 @@ > PROG= powerd > MAN= powerd.8 > WARNS?= 6 > -LDFLAGS+= -lpthread > > DPADD= ${LIBUTIL} > LDADD= -lutil > > +.if ${MACHINE_ARCH} == "i386" > +CFLAGS+=-DUSE_APM > +.endif > + > .include > Index: usr.sbin/powerd/powerd.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/powerd/powerd.c,v > retrieving revision 1.16 > diff -u -r1.16 powerd.c > --- usr.sbin/powerd/powerd.c 24 Oct 2005 18:34:54 -0000 1.16 > +++ usr.sbin/powerd/powerd.c 6 Dec 2005 23:23:11 -0000 > @@ -28,19 +28,18 @@ > #include > __FBSDID("$FreeBSD: src/usr.sbin/powerd/powerd.c,v 1.16 2005/10/24 18:34:54 njl Exp $"); > > -#include > #include > #include > #include > #include > #include > +#include > #include > > #include > #include > #include > #include > -#include > #include > #include > #include > @@ -55,17 +54,17 @@ > #define DEFAULT_IDLE_PERCENT 90 > #define DEFAULT_POLL_INTERVAL 500 /* Poll interval in milliseconds */ > > -enum modes_t { > +typedef enum { > MODE_MIN, > MODE_ADAPTIVE, > MODE_MAX, > -}; > +} modes_t; > > -enum power_src_t { > +typedef enum { > SRC_AC, > SRC_BATTERY, > SRC_UNKNOWN, > -}; > +} power_src_t; > > const char *modes[] = { > "AC", > @@ -82,10 +81,9 @@ > static int read_freqs(int *numfreqs, int **freqs, int **power); > static int set_freq(int freq); > static void acline_init(void); > -static int acline_read(void); > +static void acline_read(void); > static int devd_init(void); > static void devd_close(void); > -static void *devd_read(void *arg); > static void handle_sigs(int sig); > static void parse_mode(char *arg, int *mode, int ch); > static void usage(void); > @@ -96,19 +94,29 @@ > static int levels_mib[4]; > static int acline_mib[3]; > > -/* devd-cached value provided by our thread. */ > -static int devd_acline; > - > /* Configuration */ > static int cpu_running_mark; > static int cpu_idle_mark; > static int poll_ival; > static int vflag; > > -static int apm_fd; > -static int devd_pipe; > -static pthread_t devd_thread; > -static int exit_requested; > +static volatile sig_atomic_t exit_requested; > +static power_src_t acline_status; > +static enum { > + ac_none, > + ac_acpi_sysctl, > + ac_acpi_devd, > +#ifdef USE_APM > + ac_apm, > +#endif > +} acline_mode; Prefer enums be all CAPS, seems like ac_apm can be left in the enum without an #ifdef because it's only checked by code in an #ifdef below. > +#ifdef USE_APM > +static int apm_fd = -1; > +#endif > +static int devd_pipe = -1; > + > +#define DEVD_RETRY_INTERVAL 60 /* seconds */ > +static struct timeval tried_devd; > > static int > read_usage_times(long *idle, long *total) > @@ -195,168 +203,132 @@ > > /* > * Try to use ACPI to find the AC line status. If this fails, fall back > - * to APM. If nothing succeeds, we'll just run in default mode. If we are > - * using ACPI, try opening a pipe to devd to detect AC line events. > + * to APM. If nothing succeeds, we'll just run in default mode. > */ > static void > acline_init() > { > - int acline; > size_t len; > > - apm_fd = -1; > - devd_pipe = -1; > - len = sizeof(acline); > - if (sysctlbyname(ACPIAC, &acline, &len, NULL, 0) == 0) { > - len = 3; > - if (sysctlnametomib(ACPIAC, acline_mib, &len)) > - err(1, "lookup acline"); > - > - /* Read line status once so that we have an initial value. */ > - devd_acline = acline_read(); > - > - /* > - * Try connecting to the devd pipe and start a read thread > - * if we succeed. > - */ > - if ((devd_pipe = devd_init()) >= 0) { > - if (pthread_create(&devd_thread, NULL, devd_read, > - &devd_pipe)) > - err(1, "pthread_create devd thread"); > - } else if (vflag) { > - warnx( > - "unable to connect to devd pipe, using polling mode instead"); > - } > + len = 3; > + if (sysctlnametomib(ACPIAC, acline_mib, &len) == 0) { > + acline_mode = ac_acpi_sysctl; > + if (vflag) > + warnx("using sysctl for AC line status"); > +#ifdef __i386__ > + } else if ((apm_fd = open(APMDEV, O_RDONLY)) >= 0) { > + if (vflag) > + warnx("using APM for AC line status"); > + acline_mode = ac_apm; > +#endif Don't you want to use your new USE_APM define here? > } else { > - apm_fd = open(APMDEV, O_RDONLY); > - if (apm_fd == -1) > - warnx( > - "cannot read AC line status, using default settings"); > + warnx("unable to determine AC line status"); > + acline_mode = ac_none; > } > } > > -static int > -acline_read() > +static void > +acline_read(void) Is this correct? I thought only the prototype (above) should have void as an arg. > { > - int acline; > - size_t len; > -#ifdef __i386__ > - struct apm_info info; > -#endif > - > - acline = SRC_UNKNOWN; > - len = sizeof(acline); > + if (acline_mode == ac_acpi_devd) { > + char buf[DEVCTL_MAXBUF], *ptr; > + ssize_t rlen; > + int notify; Prefer variables declared at start of function. > - /* > - * Get state from our devd thread, the ACPI sysctl, or APM. We > - * prefer sources in this order. > - */ > - if (devd_pipe >= 0) > - acline = devd_acline; > - else if (sysctl(acline_mib, 3, &acline, &len, NULL, 0) == 0) > - acline = acline ? SRC_AC : SRC_BATTERY; > -#ifdef __i386__ > - else if (apm_fd != -1 && ioctl(apm_fd, APMIO_GETINFO, &info) == 0) > - acline = info.ai_acline ? SRC_AC : SRC_BATTERY; > + rlen = read(devd_pipe, buf, sizeof(buf)); > + if (rlen == 0 || (rlen < 0 && errno != EWOULDBLOCK)) { > + if (vflag) > + warnx("lost devd connection, switching to sysctl"); > + devd_close(); > + acline_mode = ac_acpi_sysctl; > + /* FALLTHROUGH */ > + } > + if (rlen > 0 && > + (ptr = strstr(buf, "system=ACPI")) != NULL && > + (ptr = strstr(ptr, "subsystem=ACAD")) != NULL && > + (ptr = strstr(ptr, "notify=")) != NULL && > + sscanf(ptr, "notify=%x", ¬ify) == 1) > + acline_status = (notify ? SRC_AC : SRC_BATTERY); > + } > + if (acline_mode == ac_acpi_sysctl) { > + int acline; > + size_t len; Prefer vars at start of function. > + len = sizeof(acline); > + if (sysctl(acline_mib, 3, &acline, &len, NULL, 0) == 0) > + acline_status = (acline ? SRC_AC : SRC_BATTERY); > + else > + acline_status = SRC_UNKNOWN; > + } > +#ifdef USE_APM > + if (acline_mode == ac_apm) { > + struct apm_info info; > + > + if (ioctl(apm_fd, APMIO_GETINFO, &info) == 0) { > + acline_status = (info.ai_acline ? SRC_AC : SRC_BATTERY); > + } else { > + close(apm_fd); > + apm_fd = -1; > + acline_mode = ac_none; > + acline_status = SRC_UNKNOWN; > + } > + } > #endif > - > - return (acline); > + /* try to (re)connect to devd */ > + if (acline_mode == ac_acpi_sysctl) { > + struct timeval now; > + > + gettimeofday(&now, NULL); > + if (now.tv_sec > tried_devd.tv_sec + DEVD_RETRY_INTERVAL) { > + if (devd_init() >= 0) { > + if (vflag) > + warnx("using devd for AC line status"); > + acline_mode = ac_acpi_devd; > + } > + tried_devd = now; > + } > + } > } > > static int > devd_init(void) > { > struct sockaddr_un devd_addr; > - int devd_sock; > > bzero(&devd_addr, sizeof(devd_addr)); > - if ((devd_sock = socket(PF_LOCAL, SOCK_STREAM, 0)) < 0) { > + if ((devd_pipe = socket(PF_LOCAL, SOCK_STREAM, 0)) < 0) { > if (vflag) > - warn("failed to create devd socket"); > + warn("%s(): socket()", __func__); > return (-1); > } > > devd_addr.sun_family = PF_LOCAL; > strlcpy(devd_addr.sun_path, DEVDPIPE, sizeof(devd_addr.sun_path)); > - if (connect(devd_sock, (struct sockaddr *)&devd_addr, > + if (connect(devd_pipe, (struct sockaddr *)&devd_addr, > sizeof(devd_addr)) == -1) { > - close(devd_sock); > + if (vflag) > + warn("%s(): connect()", __func__); > + close(devd_pipe); > + devd_pipe = -1; > return (-1); > } > > - return (devd_sock); > + if (fcntl(devd_pipe, F_SETFL, O_NONBLOCK) == -1) { > + if (vflag) > + warn("%s(): fcntl()", __func__); > + close(devd_pipe); > + return (-1); > + } > + > + return (devd_pipe); > } > > static void > devd_close(void) > { > > - if (devd_pipe < 0) > - return; > - > - pthread_kill(devd_thread, SIGTERM); > close(devd_pipe); > -} Seems like this function can go away now and we can just conditionally close devd_pipe (if != -1) at the end of main(). > - > -/* > - * This loop runs as a separate thread. It reads events from devd, but > - * spends most of its time blocked in select(2). > - */ > -static void * > -devd_read(void *arg) > -{ > - char buf[DEVCTL_MAXBUF], *ptr; > - fd_set fdset; > - int fd, notify, rlen; > - > - fd = *(int *)arg; > - notify = -1; > - FD_ZERO(&fdset); > - while (!exit_requested) { > - FD_SET(fd, &fdset); > - if (select(fd + 1, &fdset, NULL, NULL, NULL) < 0) > - break; > - if (!FD_ISSET(fd, &fdset)) > - continue; > - > - /* Read the notify string, devd NULL-terminates it. */ > - rlen = read(fd, buf, sizeof(buf)); > - if (rlen <= 0) { > - close(devd_pipe); > - devd_pipe = -1; > - if (vflag) > - warnx( > - "devd disappeared, downgrading to polling mode"); > - > - /* > - * Keep trying to reconnect to devd but sleep in > - * between to avoid wasting CPU cycles. > - */ > - while (!exit_requested && (fd = devd_init()) < 0) > - sleep(300); > - > - if (fd >= 0) { > - devd_pipe = fd; > - if (vflag) > - warnx( > - "devd came back, upgrading to event mode"); > - } > - continue; > - } > - > - /* Loosely match the notify string. */ > - if ((ptr = strstr(buf, "system=ACPI")) != NULL && > - (ptr = strstr(ptr, "subsystem=ACAD")) != NULL && > - (ptr = strstr(ptr, "notify=")) != NULL) { > - if (sscanf(ptr, "notify=%x", ¬ify) != 1) { > - warnx("bad devd notify string"); > - continue; > - } > - devd_acline = notify ? SRC_AC : SRC_BATTERY; > - } > - } > - > - return (NULL); > + devd_pipe = -1; > } > > static void > @@ -392,10 +364,13 @@ > int > main(int argc, char * argv[]) > { > + struct timeval timeout; > + fd_set fdset; > + int nfds; > struct pidfh *pfh = NULL; > const char *pidfile = NULL; > long idle, total; > - int acline, curfreq, *freqs, i, *mwatts, numfreqs; > + int curfreq, *freqs, i, *mwatts, numfreqs; > int ch, mode, mode_ac, mode_battery, mode_none; > uint64_t mjoules_used; > size_t len; > @@ -407,7 +382,6 @@ > poll_ival = DEFAULT_POLL_INTERVAL; > mjoules_used = 0; > vflag = 0; > - apm_fd = -1; > > /* User must be root to control frequencies. */ > if (geteuid() != 0) > @@ -479,15 +453,6 @@ > if (read_freqs(&numfreqs, &freqs, &mwatts)) > err(1, "error reading supported CPU frequencies"); > > - /* > - * Exit cleanly on signals; devd may send a SIGPIPE if it dies. We > - * do this before acline_init() since it may create a thread and we > - * want it to inherit our signal mask. > - */ > - signal(SIGINT, handle_sigs); > - signal(SIGTERM, handle_sigs); > - signal(SIGPIPE, SIG_IGN); > - Don't we still need SIGPIPE handling if reading from devd? Or does opening the fd nonblocking mean you're guaranteed not to get this signal? -- Nate From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 12:54:11 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8F9D216A41F for ; Fri, 9 Dec 2005 12:54:11 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67C7043D5A for ; Fri, 9 Dec 2005 12:53:56 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 3446351 for multiple; Fri, 09 Dec 2005 07:56:03 -0500 Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jB9Crp0l079193; Fri, 9 Dec 2005 07:53:52 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Fri, 9 Dec 2005 07:53:48 -0500 User-Agent: KMail/1.8.3 References: <20051206093020.691e1483.ai@bmc.brk.ru> <200512080951.52387.jhb@freebsd.org> <20051209143634.09bc2d90.ai@bmc.brk.ru> In-Reply-To: <20051209143634.09bc2d90.ai@bmc.brk.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200512090753.49989.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: Artemiev Igor Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 12:54:11 -0000 On Friday 09 December 2005 06:36 am, Artemiev Igor wrote: > On Thu, 8 Dec 2005 09:51:51 -0500 > > John Baldwin wrote: > > > I simply do not see any way to do it with current implementation of > > > ampdm(and also viapm, etc) & smbus, without modifying the smb- > > > > > > >smbus->smbus driver interface. I may be wrong, but as far as I > > > >know, currently it's one > > > > > > smb for one driver (smbus_* limitation) > > > > Hmm, it doesn't specify the child device, just the parent. *sigh* > > That's lame. You don't have to call it amdpmsub0 btw, you could just > > call it amdpm1 if you wanted and have amdpm1 a child of amdpm0. All > > that would need to change for that is the NF2_SUBDEV string and the > > DRIVER_MODULE line (it would be DRIVER_MODULE(amdpm, amdpm, ...)). > > This has the added advantage that you don't have to patch smbus.c. > > I remade it as you described - can't understand, why I didn't think > about it myself Do you have a final patch at a URL? If so, I'll go ahead and commit it for= =20 you. =2D-=20 John Baldwin =A0<>< =A0http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" =A0=3D =A0http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 13:01:06 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0F91016A41F; Fri, 9 Dec 2005 13:01:06 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 03AA543D5F; Fri, 9 Dec 2005 13:01:02 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id 735842082; Fri, 9 Dec 2005 14:00:55 +0100 (CET) X-Spam-Tests: AWL,BAYES_00,FORGED_RCVD_HELO X-Spam-Learn: ham X-Spam-Score: -3.3/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id E31332080; Fri, 9 Dec 2005 14:00:54 +0100 (CET) Received: by xps.des.no (Postfix, from userid 1001) id C1F4433C1D; Fri, 9 Dec 2005 14:00:54 +0100 (CET) To: Nate Lawson References: <43938F61.1050202@terranova.net> <4393F60E.2040106@shapeshifter.se> <86mzjflc97.fsf@xps.des.no> <439495B1.5060305@shapeshifter.se> <861x0qmuen.fsf@xps.des.no> <43956ADF.4050504@shapeshifter.se> <86slt6lb9s.fsf@xps.des.no> <4395A265.8080006@root.org> <86d5k9eric.fsf@xps.des.no> <43997CEC.1070607@root.org> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Fri, 09 Dec 2005 14:00:54 +0100 In-Reply-To: <43997CEC.1070607@root.org> (Nate Lawson's message of "Fri, 09 Dec 2005 21:47:40 +0900") Message-ID: <864q5is9vd.fsf@xps.des.no> User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: njl@freebsd.org, Fredrik Lindberg , Travis Mikalson , current@freebsd.org Subject: Re: powerd X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 13:01:06 -0000 Nate Lawson writes: > Dag-Erling Sm=F8rgrav wrote: >> +static enum { >> + ac_none, >> + ac_acpi_sysctl, >> + ac_acpi_devd, >> +#ifdef USE_APM >> + ac_apm, >> +#endif >> +} acline_mode; > > Prefer enums be all CAPS, seems like ac_apm can be left in the enum > without an #ifdef because it's only checked by code in an #ifdef below. Having the #ifdef here allows the compiler to warn us if we forget it somewhere else. >> +#ifdef __i386__ >> + } else if ((apm_fd =3D open(APMDEV, O_RDONLY)) >=3D 0) { >> + if (vflag) >> + warnx("using APM for AC line status"); >> + acline_mode =3D ac_apm; >> +#endif > > Don't you want to use your new USE_APM define here? Yes, that was an oversight. >> -static int >> -acline_read() >> +static void >> +acline_read(void) > > Is this correct? I thought only the prototype (above) should have > void as an arg. Yes, and no. >> static void >> devd_close(void) >> { >> - if (devd_pipe < 0) >> - return; >> - >> - pthread_kill(devd_thread, SIGTERM); >> close(devd_pipe); >> -} > > Seems like this function can go away now and we can just conditionally > close devd_pipe (if !=3D -1) at the end of main(). actually, devd_close() should include the line 'devd_pipe =3D -1;' and all instances of close(devd_pipe) should be replaced with devd_close(). >> - /* >> - * Exit cleanly on signals; devd may send a SIGPIPE if it dies. We >> - * do this before acline_init() since it may create a thread and we >> - * want it to inherit our signal mask. >> - */ >> - signal(SIGINT, handle_sigs); >> - signal(SIGTERM, handle_sigs); >> - signal(SIGPIPE, SIG_IGN); >> - > > Don't we still need SIGPIPE handling if reading from devd? des@xps ~% man signal | grep SIGPIPE 13 SIGPIPE terminate process write on a pipe with no reader DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 13:15:49 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 691DE16A420; Fri, 9 Dec 2005 13:15:49 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Received: from stalker.bmc.brk.ru (stalker.bmc.brk.ru [217.150.59.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 885EF43D80; Fri, 9 Dec 2005 13:15:33 +0000 (GMT) (envelope-from ai@bmc.brk.ru) Date: Fri, 9 Dec 2005 16:15:23 +0300 From: Artemiev Igor To: freebsd-current@freebsd.org Message-Id: <20051209161523.31f5b415.ai@bmc.brk.ru> In-Reply-To: <200512090753.49989.jhb@freebsd.org> References: <20051206093020.691e1483.ai@bmc.brk.ru> <200512080951.52387.jhb@freebsd.org> <20051209143634.09bc2d90.ai@bmc.brk.ru> <200512090753.49989.jhb@freebsd.org> Organization: Bryansk Medical Center X-Mailer: Sylpheed version 2.0.0beta4 (GTK+ 2.6.8; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Subject: Re: [PATCH] nForce2 SMBus support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 13:15:50 -0000 On Fri, 9 Dec 2005 07:53:48 -0500 John Baldwin wrote: > Do you have a final patch at a URL? If so, I'll go ahead and commit > it for you. My thanks. Final version of the patch lies here: http://bmc.brk.ru/~ai/patches/amdpm.nforce2_support.diff -- iprefetch ai From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 20:33:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1BB5F16A41F; Fri, 9 Dec 2005 20:33:10 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACB8643D6E; Fri, 9 Dec 2005 20:32:54 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 7B2F71FFAD4; Fri, 9 Dec 2005 21:32:43 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id C1AEE1FFAD3; Fri, 9 Dec 2005 21:32:40 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 446AB444F50; Fri, 9 Dec 2005 20:28:38 +0000 (UTC) Date: Fri, 9 Dec 2005 20:28:38 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: <20051209175607.C23668@maildrop.int.zabbadoz.net> 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: Subject: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 20:33:10 -0000 Hi, everyone out there who had only seen timeouts like nve0: device timeout (4) on nve and __never got it working at all__ please try this patch[1] which made my nve working from 0 to 99. I still can get timeouts by for example flood pinging another machine on the local LAN but it all recovers on it's own and I can work on that machine and do things like find / over ssh without losing connectivity. Fixing the timeouts will be another problem that needs to be addressed later. Greetings Bjoern A. Zeeb [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff Index: if_nve.c =================================================================== RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/nve/if_nve.c,v retrieving revision 1.19 diff -u -p -r1.19 if_nve.c --- if_nve.c 7 Dec 2005 17:38:03 -0000 1.19 +++ if_nve.c 9 Dec 2005 17:50:32 -0000 @@ -643,6 +643,10 @@ nve_init_locked(struct nve_softc *sc) nve_stop(sc); DEBUGOUT(NVE_DEBUG_INIT, "nve: do pfnInit\n"); + /* Setup multicast filter */ + nve_setmulti(sc); + nve_ifmedia_upd_locked(ifp); + /* Setup Hardware interface and allocate memory structures */ error = sc->hwapi->pfnInit(sc->hwapi->pADCX, 0, /* force speed */ @@ -661,10 +665,6 @@ nve_init_locked(struct nve_softc *sc) sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); sc->hwapi->pfnStart(sc->hwapi->pADCX); - /* Setup multicast filter */ - nve_setmulti(sc); - nve_ifmedia_upd_locked(ifp); - /* Update interface parameters */ ifp->if_drv_flags |= IFF_DRV_RUNNING; ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 21:42:46 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E673116A426; Fri, 9 Dec 2005 21:42:45 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 20F4A43D78; Fri, 9 Dec 2005 21:42:10 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB9Lg6TV072028; Fri, 9 Dec 2005 16:42:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB9Lg6ie096831; Fri, 9 Dec 2005 16:42:06 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 2157F7302F; Fri, 9 Dec 2005 16:42:06 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209214206.2157F7302F@freebsd-current.sentex.ca> Date: Fri, 9 Dec 2005 16:42:06 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 21:42:46 -0000 TB --- 2005-12-09 20:30:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 20:30:12 - starting HEAD tinderbox run for alpha/alpha TB --- 2005-12-09 20:30:12 - cleaning the object tree TB --- 2005-12-09 20:30:40 - checking out the source tree TB --- 2005-12-09 20:30:40 - cd /tinderbox/HEAD/alpha/alpha TB --- 2005-12-09 20:30:40 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 20:36:37 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 20:36:37 - cd /src TB --- 2005-12-09 20:36:37 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-09 21:41:41 - generating LINT kernel config TB --- 2005-12-09 21:41:41 - cd /src/sys/alpha/conf TB --- 2005-12-09 21:41:41 - /usr/bin/make -B LINT TB --- 2005-12-09 21:41:41 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 21:41:41 - cd /src TB --- 2005-12-09 21:41:41 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 21:41:41 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/alpha/alpha/genassym.c:61: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 21:42:05 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 21:42:05 - ERROR: failed to build lint kernel TB --- 2005-12-09 21:42:05 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 22:26:12 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B48316A41F; Fri, 9 Dec 2005 22:26:11 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <439A049E.9020907@freebsd.org> Date: Sat, 10 Dec 2005 06:26:38 +0800 From: David Xu User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.7.10) Gecko/20050806 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <20051209175607.C23668@maildrop.int.zabbadoz.net> In-Reply-To: <20051209175607.C23668@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 22:26:12 -0000 Bjoern A. Zeeb wrote: > Hi, > > everyone out there who had only seen timeouts like > nve0: device timeout (4) > on nve and __never got it working at all__ please try this patch[1] > which made my nve working from 0 to 99. > > I still can get timeouts by for example flood pinging another machine > on the local LAN but it all recovers on it's own and I can work on > that machine and do things like find / over ssh without losing > connectivity. Fixing the timeouts will be another problem that needs > to be addressed later. > > Greetings > Bjoern A. Zeeb > > > [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051209-01.diff It saves the nve on my EPOX 9nda3j board! it is a NForce3 250 GB, it is working now, oh, you are my hero! David Xu From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 23:18:13 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAC2616A41F for ; Fri, 9 Dec 2005 23:18:13 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper.zs64.net [212.12.50.230]) by mx1.FreeBSD.org (Postfix) with ESMTP id D0E0743D53 for ; Fri, 9 Dec 2005 23:18:12 +0000 (GMT) (envelope-from cracauer@schlepper.zs64.net) Received: from schlepper.zs64.net (schlepper [212.12.50.230]) by schlepper.zs64.net (8.13.3/8.12.9) with ESMTP id jB9NIBJw093604 for ; Sat, 10 Dec 2005 00:18:11 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jB9NIBtP093603 for freebsd-current@freebsd.org; Fri, 9 Dec 2005 18:18:11 -0500 (EST) (envelope-from cracauer) Date: Fri, 9 Dec 2005 18:18:11 -0500 From: Martin Cracauer To: freebsd-current@freebsd.org Message-ID: <20051209181811.A93373@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: "ad0: TIMEOUT - READ_DMA retrying" - does this mean I am fine? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 23:18:14 -0000 This is a question on IDE error recovery. I have a broken drive and while copying the data over to a new drive I have seen: Dec 9 03:09:40 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=68460463 Dec 9 03:10:10 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=70278843 Dec 9 03:10:39 grisu kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=71672863 Dec 9 03:10:49 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=72831895 Dec 9 03:11:49 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=14894591 So, it says "1 retry left" every time and there is no message saying that a hard error occured. Does that mean the files got off the drive OK? This is 6-stable. Intel ICH4 UDMA100 controller (Thinkpad). Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ FreeBSD - where you want to go, today. http://www.freebsd.org/ From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 23:20:36 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75ACE16A41F; Fri, 9 Dec 2005 23:20:36 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E8AD43D62; Fri, 9 Dec 2005 23:20:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2.sentex.ca [199.212.134.9]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jB9NKRgC078095; Fri, 9 Dec 2005 18:20:27 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jB9NKRe7034927; Fri, 9 Dec 2005 18:20:27 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 15DCD7302F; Fri, 9 Dec 2005 18:20:27 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051209232027.15DCD7302F@freebsd-current.sentex.ca> Date: Fri, 9 Dec 2005 18:20:27 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 23:20:36 -0000 TB --- 2005-12-09 21:42:06 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 21:42:06 - starting HEAD tinderbox run for amd64/amd64 TB --- 2005-12-09 21:42:06 - cleaning the object tree TB --- 2005-12-09 21:42:45 - checking out the source tree TB --- 2005-12-09 21:42:45 - cd /tinderbox/HEAD/amd64/amd64 TB --- 2005-12-09 21:42:45 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 21:48:45 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 21:48:45 - cd /src TB --- 2005-12-09 21:48:45 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2005-12-09 23:19:58 - generating LINT kernel config TB --- 2005-12-09 23:19:58 - cd /src/sys/amd64/conf TB --- 2005-12-09 23:19:58 - /usr/bin/make -B LINT TB --- 2005-12-09 23:19:58 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-09 23:19:58 - cd /src TB --- 2005-12-09 23:19:58 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Dec 9 23:19:59 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/amd64/amd64/genassym.c:60: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-09 23:20:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-09 23:20:26 - ERROR: failed to build lint kernel TB --- 2005-12-09 23:20:26 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Fri Dec 9 23:32:19 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3262616A41F for ; Fri, 9 Dec 2005 23:32:19 +0000 (GMT) (envelope-from sos@FreeBSD.org) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D9B343D46 for ; Fri, 9 Dec 2005 23:32:17 +0000 (GMT) (envelope-from sos@FreeBSD.org) Received: from [194.192.25.142] (spider.deepcore.dk [194.192.25.142]) by spider.deepcore.dk (8.13.4/8.13.4) with ESMTP id jB9NW8YN062314; Sat, 10 Dec 2005 00:32:08 +0100 (CET) (envelope-from sos@FreeBSD.org) Message-ID: <439A13F7.7020303@FreeBSD.org> Date: Sat, 10 Dec 2005 00:32:07 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <20051209181811.A93373@cons.org> In-Reply-To: <20051209181811.A93373@cons.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-current@FreeBSD.org Subject: Re: "ad0: TIMEOUT - READ_DMA retrying" - does this mean I am fine? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Dec 2005 23:32:19 -0000 Martin Cracauer wrote: >This is a question on IDE error recovery. > >I have a broken drive and while copying the data over to a new drive I >have seen: > >Dec 9 03:09:40 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=68460463 >Dec 9 03:10:10 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=70278843 >Dec 9 03:10:39 grisu kernel: ad0: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=71672863 >Dec 9 03:10:49 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=72831895 >Dec 9 03:11:49 grisu kernel: ad0: TIMEOUT - READ_DMA retrying (1 retry left) LBA=14894591 > >So, it says "1 retry left" every time and there is no message saying >that a hard error occured. > > >Does that mean the files got off the drive OK? > > Yes the retry succeeded, or you will get a "FAILURE" line logged, or at least that was the idea :) -Søren From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 00:32:01 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DFE816A41F; Sat, 10 Dec 2005 00:32:01 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F7BE43D4C; Sat, 10 Dec 2005 00:32:00 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jBA0VxSH057563; Fri, 9 Dec 2005 19:31:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.3/8.13.3) with ESMTP id jBA0Vx07019068; Fri, 9 Dec 2005 19:31:59 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 05B257302F; Fri, 9 Dec 2005 19:31:58 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051210003158.05B257302F@freebsd-current.sentex.ca> Date: Fri, 9 Dec 2005 19:31:58 -0500 (EST) X-Virus-Scanned: ClamAV version 0.85.1, clamav-milter version 0.85 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 00:32:01 -0000 TB --- 2005-12-09 23:20:27 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-09 23:20:27 - starting HEAD tinderbox run for i386/i386 TB --- 2005-12-09 23:20:27 - cleaning the object tree TB --- 2005-12-09 23:20:51 - checking out the source tree TB --- 2005-12-09 23:20:51 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-12-09 23:20:51 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-09 23:26:33 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-09 23:26:33 - cd /src TB --- 2005-12-09 23:26:33 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-10 00:31:26 - generating LINT kernel config TB --- 2005-12-10 00:31:26 - cd /src/sys/i386/conf TB --- 2005-12-10 00:31:26 - /usr/bin/make -B LINT TB --- 2005-12-10 00:31:27 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-10 00:31:27 - cd /src TB --- 2005-12-10 00:31:27 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 10 00:31:27 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/i386/i386/genassym.c:63: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-10 00:31:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-10 00:31:58 - ERROR: failed to build lint kernel TB --- 2005-12-10 00:31:58 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 01:42:53 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BB0016A41F; Sat, 10 Dec 2005 01:42:53 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2E8343D60; Sat, 10 Dec 2005 01:42:52 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jBA1gphH085451; Fri, 9 Dec 2005 20:42:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jBA1gpEb016710; Fri, 9 Dec 2005 20:42:51 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3E40B7302F; Fri, 9 Dec 2005 20:42:51 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051210014251.3E40B7302F@freebsd-current.sentex.ca> Date: Fri, 9 Dec 2005 20:42:51 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 01:42:53 -0000 TB --- 2005-12-10 00:31:59 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-10 00:31:59 - starting HEAD tinderbox run for i386/pc98 TB --- 2005-12-10 00:31:59 - cleaning the object tree TB --- 2005-12-10 00:32:19 - checking out the source tree TB --- 2005-12-10 00:32:19 - cd /tinderbox/HEAD/i386/pc98 TB --- 2005-12-10 00:32:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-10 00:38:04 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-10 00:38:04 - cd /src TB --- 2005-12-10 00:38:04 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-10 01:42:13 - generating LINT kernel config TB --- 2005-12-10 01:42:13 - cd /src/sys/pc98/conf TB --- 2005-12-10 01:42:13 - /usr/bin/make -B LINT TB --- 2005-12-10 01:42:13 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-10 01:42:13 - cd /src TB --- 2005-12-10 01:42:13 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 10 01:42:13 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] from /src/sys/net/if.h:390, from /src/sys/i386/i386/genassym.c:63: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-10 01:42:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-10 01:42:51 - ERROR: failed to build lint kernel TB --- 2005-12-10 01:42:51 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 02:57:48 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 238A716A420; Sat, 10 Dec 2005 02:57:48 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9501543D67; Sat, 10 Dec 2005 02:57:47 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.13.4/8.13.4) with ESMTP id jBA2vkPZ066591; Fri, 9 Dec 2005 21:57:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jBA2vkAm044410; Fri, 9 Dec 2005 21:57:46 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 389527302F; Fri, 9 Dec 2005 21:57:46 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051210025746.389527302F@freebsd-current.sentex.ca> Date: Fri, 9 Dec 2005 21:57:46 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 02:57:48 -0000 TB --- 2005-12-10 01:42:51 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-10 01:42:51 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2005-12-10 01:42:51 - cleaning the object tree TB --- 2005-12-10 01:43:18 - checking out the source tree TB --- 2005-12-10 01:43:18 - cd /tinderbox/HEAD/sparc64/sparc64 TB --- 2005-12-10 01:43:18 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-10 01:49:29 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-10 01:49:29 - cd /src TB --- 2005-12-10 01:49:29 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-10 02:54:55 - generating LINT kernel config TB --- 2005-12-10 02:54:55 - cd /src/sys/sparc64/conf TB --- 2005-12-10 02:54:55 - /usr/bin/make -B LINT TB --- 2005-12-10 02:54:55 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-10 02:54:55 - cd /src TB --- 2005-12-10 02:54:55 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 10 02:54:55 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medlow -msoft-float -ffreestanding -Werror /src/sys/contrib/altq/altq/altq_cbq.c -I/src/sys/contrib/pf In file included from /src/sys/contrib/altq/altq/altq_cbq.c:47: /src/sys/sys/mbuf.h: In function `m_getjcl': /src/sys/sys/mbuf.h:424: error: duplicate case value /src/sys/sys/mbuf.h:421: error: previously used here /src/sys/sys/mbuf.h: In function `m_cljget': /src/sys/sys/mbuf.h:488: error: duplicate case value /src/sys/sys/mbuf.h:485: error: previously used here *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-10 02:57:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-10 02:57:45 - ERROR: failed to build lint kernel TB --- 2005-12-10 02:57:45 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 13:02:45 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25C4316A41F for ; Sat, 10 Dec 2005 13:02:45 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1A9E43D62 for ; Sat, 10 Dec 2005 13:02:44 +0000 (GMT) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from transport.cksoft.de (localhost [127.0.0.1]) by transport.cksoft.de (Postfix) with ESMTP id 4EC041FF9AD for ; Sat, 10 Dec 2005 14:02:42 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 7B4CC1FF9A6; Sat, 10 Dec 2005 14:02:39 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 40A6C444F50 for ; Sat, 10 Dec 2005 12:56:33 +0000 (UTC) Date: Sat, 10 Dec 2005 12:56:33 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: FreeBSD current mailing list In-Reply-To: <20051209175607.C23668@maildrop.int.zabbadoz.net> Message-ID: <20051210125221.M23668@maildrop.int.zabbadoz.net> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> 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: Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 13:02:45 -0000 On Fri, 9 Dec 2005, Bjoern A. Zeeb wrote: Hi, > everyone out there who had only seen timeouts like > nve0: device timeout (4) > on nve and __never got it working at all__ please try this patch[1] > which made my nve working from 0 to 99. > > I still can get timeouts by for example flood pinging another machine > on the local LAN but it all recovers on it's own and I can work on > that machine and do things like find / over ssh without losing > connectivity. Fixing the timeouts will be another problem that needs > to be addressed later. After removing hw.physmem="3G" from my loader.conf of my 4GB RAM machine I noticed that nve again was not working. Anyone with >= 4GB RAM might want to try the updated version of the patch which helps here. [1] http://sources.zabbadoz.net/freebsd/patchset/nve-20051210-01.diff Index: if_nve.c =================================================================== RCS file: /shared/mirror/FreeBSD/r/ncvs/src/sys/dev/nve/if_nve.c,v retrieving revision 1.19 diff -u -p -r1.19 if_nve.c --- if_nve.c 7 Dec 2005 17:38:03 -0000 1.19 +++ if_nve.c 10 Dec 2005 12:53:06 -0000 @@ -643,6 +643,10 @@ nve_init_locked(struct nve_softc *sc) nve_stop(sc); DEBUGOUT(NVE_DEBUG_INIT, "nve: do pfnInit\n"); + /* Setup multicast filter */ + nve_setmulti(sc); + nve_ifmedia_upd_locked(ifp); + /* Setup Hardware interface and allocate memory structures */ error = sc->hwapi->pfnInit(sc->hwapi->pADCX, 0, /* force speed */ @@ -661,10 +665,6 @@ nve_init_locked(struct nve_softc *sc) sc->hwapi->pfnEnableInterrupts(sc->hwapi->pADCX); sc->hwapi->pfnStart(sc->hwapi->pADCX); - /* Setup multicast filter */ - nve_setmulti(sc); - nve_ifmedia_upd_locked(ifp); - /* Update interface parameters */ ifp->if_drv_flags |= IFF_DRV_RUNNING; ifp->if_drv_flags &= ~IFF_DRV_OACTIVE; @@ -1306,7 +1306,7 @@ nve_osalloc(PNV_VOID ctx, PMEMORY_BLOCK sc = (struct nve_softc *)ctx; mem->pLogical = (PVOID)contigmalloc(mem->uiLength, M_DEVBUF, - M_NOWAIT | M_ZERO, 0, ~0, PAGE_SIZE, 0); + M_NOWAIT | M_ZERO, 0, 0xffffffff, PAGE_SIZE, 0); if (!mem->pLogical) { device_printf(sc->dev, "memory allocation failed\n"); -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 14:08:03 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 17E8F16A44A for ; Sat, 10 Dec 2005 14:08:03 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from strange.daemonsecurity.com (59.Red-81-33-11.staticIP.rima-tde.net [81.33.11.59]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FC6C43D5A for ; Sat, 10 Dec 2005 14:08:02 +0000 (GMT) (envelope-from norgaard@locolomo.org) Received: from [172.16.2.1] (unknown [172.16.2.1]) by strange.daemonsecurity.com (Postfix) with ESMTP id DCFC62E041 for ; Sat, 10 Dec 2005 15:06:02 +0100 (CET) Message-ID: <439AE13D.1040800@locolomo.org> Date: Sat, 10 Dec 2005 15:07:57 +0100 From: =?ISO-8859-1?Q?Erik_N=F8rgaard?= Organization: Locolomo.ORG User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050909) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Contacts for project idea list X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 14:08:03 -0000 Hi, One on the questions-list pointed my attention to the PXE installer project on the project idea list http://www.freebsd.org/projects/ideas/ There is no responsible for the project yet, nor are there any technical contacts for the category (userland/installation tools) nor is there any contact address for the idea-list maintainer. So ... who came up with this idea? Who should I bug if I want to contribute to this? Looking at this, it seems that the sysinstall renewal project is relevant if anyone knows about that... Thanks, Erik PS: It would be great if the one who maintain the idea list had his/her address listed - just in case other contact info is missing or someone thinks up some brilliant idea. -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 15:44:15 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5063A16A41F for ; Sat, 10 Dec 2005 15:44:15 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from portpc-design.spb.ru (portpc-design.spb.ru [81.176.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EC8B43D76 for ; Sat, 10 Dec 2005 15:44:08 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [85.140.159.33] (ppp85-140-159-33.pppoe.mtu-net.ru [85.140.159.33]) (authenticated bits=0) by portpc-design.spb.ru (8.13.5/8.13.5) with ESMTP id jBAFi44q026714 for ; Sat, 10 Dec 2005 18:44:04 +0300 (MSK) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <439AF7C0.9060801@mcsi.pp.ru> Date: Sat, 10 Dec 2005 18:44:00 +0300 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051204 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on 81.176.64.226 X-Virus-Status: Clean Cc: Subject: LOR in pcm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 15:44:15 -0000 Hi all. Got this on SMP CURRENT from Sun Dec 4 22:06:46 MSK 2005. I have no recording devices, FWIW. lock order reversal: 1st 0xc35884c0 pcm0 (sound cdev) @ /usr/src/sys/dev/sound/pcm/dsp.c:277 2nd 0xc3562ac0 pcm0:record:0 (pcm record channel) @ /usr/src/sys/dev/sound/pcm/dsp.c:290 KDB: stack backtrace: kdb_backtrace(0,ffffffff,c09a4d28,c09a4cb0,c0929504) at kdb_backtrace+0x29 witness_checkorder(c3562ac0,9,c08ab43d,122) at witness_checkorder+0x580 _mtx_lock_flags(c3562ac0,0,c08ab43d,122,1) at _mtx_lock_flags+0x5b dsp_open(c3586c00,7,2000,c436cc00,c0995100) at dsp_open+0x2b2 giant_open(c3586c00,7,2000,c436cc00,c3586c00) at giant_open+0x30 devfs_open(db324a18) at devfs_open+0x223 VOP_OPEN_APV(c0921cc0,db324a18) at VOP_OPEN_APV+0x7e vn_open_cred(db324b70,db324c70,468,c3ee6b80,43) at vn_open_cred+0x448 vn_open(db324b70,db324c70,468,43,c09e2ad0) at vn_open+0x1e kern_open(c436cc00,15696050,0,7,bfbf6478) at kern_open+0xb6 open(c436cc00,db324d04,86,c06acb33,c436cc00) at open+0x1a syscall(14da003b,bf2f003b,bf2f003b,bfbf6488,15696050) at syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x28a70b5f, esp = 0xbfbf644c, ebp = 0xbfbf6478 --- -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 16:41:34 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41FA816A41F for ; Sat, 10 Dec 2005 16:41:34 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from deadcafe.de (deadcafe.de [81.169.162.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6320943D88 for ; Sat, 10 Dec 2005 16:41:24 +0000 (GMT) (envelope-from freebsd@deadcafe.de) Received: from dialin.t-online.de (p54A5E90F.dip.t-dialin.net [84.165.233.15]) by deadcafe.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jBAGfCD2049483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 10 Dec 2005 17:41:16 +0100 (CET) Received: from [172.23.7.254] (doom.rock.net [172.23.7.254]) by dialin.t-online.de (8.13.4+Sun/8.13.4/Rock) with ESMTP id jBAGf0RC007665; Sat, 10 Dec 2005 17:41:00 +0100 (CET) Message-ID: <439B051A.8050701@deadcafe.de> Date: Sat, 10 Dec 2005 17:40:58 +0100 From: Daniel Rock User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <20051209175607.C23668@maildrop.int.zabbadoz.net> <20051210125221.M23668@maildrop.int.zabbadoz.net> In-Reply-To: <20051210125221.M23668@maildrop.int.zabbadoz.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.1 required=5.5 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.4 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on deadcafe.de X-Mailman-Approved-At: Sat, 10 Dec 2005 16:44:11 +0000 Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 16:41:34 -0000 Bjoern A. Zeeb schrieb: > After removing hw.physmem="3G" from my loader.conf of my 4GB RAM > machine I noticed that nve again was not working. > > Anyone with >= 4GB RAM might want to try the updated version of the > patch which helps here. Great, now the nve driver works with all memory configured: hw.physmem: 4284805120 hw.usermem: 4247728128 hw.realmem: 5637144576 I also didn't get any nve: device timeout(xxx) yet. -- Daniel From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 17:14:10 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B414716A41F for ; Sat, 10 Dec 2005 17:14:10 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from tomoyo.MyBSD.org.my (tomoyo.mybsd.org.my [202.157.186.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5B0243D7C for ; Sat, 10 Dec 2005 17:14:02 +0000 (GMT) (envelope-from skywizard@MyBSD.org.my) Received: from localhost (localhost [127.0.0.1]) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id 59F6D6CC24; Sun, 11 Dec 2005 01:18:40 +0800 (MYT) Received: from tomoyo.MyBSD.org.my ([127.0.0.1]) by localhost (TOMOYO.MYBSD.ORG.MY [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 74937-06; Sun, 11 Dec 2005 01:18:38 +0800 (MYT) Received: from misaki (unknown [IPv6:2001:328:2002:aa2:214:a5ff:fe25:e1c7]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tomoyo.MyBSD.org.my (Postfix) with ESMTP id 8AC9B6CC22; Sun, 11 Dec 2005 01:18:37 +0800 (MYT) Date: Sun, 11 Dec 2005 01:13:55 +0800 From: Ariff Abdullah To: Maxim Maximov Message-Id: <20051211011355.4b0b3f78.skywizard@MyBSD.org.my> In-Reply-To: <439AF7C0.9060801@mcsi.pp.ru> References: <439AF7C0.9060801@mcsi.pp.ru> Organization: MyBSD X-Mailer: /usr/local/lib/ruby/1.8/net/smtp.rb Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by Amavisd AntiVirus & AntiSpam Scanner running on FreeBSD mailserver at TOMOYO.MYBSD.ORG.MY Cc: current@freebsd.org Subject: Re: LOR in pcm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 17:14:10 -0000 On Sat, 10 Dec 2005 18:44:00 +0300 Maxim Maximov wrote: > Hi all. > > Got this on SMP CURRENT from Sun Dec 4 22:06:46 MSK 2005. > I have no recording devices, FWIW. > > lock order reversal: > 1st 0xc35884c0 pcm0 (sound cdev) @ > /usr/src/sys/dev/sound/pcm/dsp.c:277 2nd 0xc3562ac0 pcm0:record:0 > (pcm record channel) @ > /usr/src/sys/dev/sound/pcm/dsp.c:290 > KDB: stack backtrace: > kdb_backtrace(0,ffffffff,c09a4d28,c09a4cb0,c0929504) at > kdb_backtrace+0x29 witness_checkorder(c3562ac0,9,c08ab43d,122) at > witness_checkorder+0x580 > _mtx_lock_flags(c3562ac0,0,c08ab43del22,1) at > _mtx_lock_flags+0x5b dsp_open(c3586c00,7,2000,c436cc00,c0995100) at > dsp_open+0x2b2 giant_open(c3586c00,7,2000,c436cc00,c3586c00) at > giant_open+0x30 devfs_open(db324a18) at devfs_open+0x223 > VOP_OPEN_APV(c0921cc0,db324a18) at VOP_OPEN_APV+0x7e > vn_open_cred(db324b70,db324c70,468,c3ee6b80,43) at > vn_open_cred+0x448 vn_open(db324b70,db324c70,468,43,c09e2ad0) at > vn_open+0x1e kern_open(c436cc00,15696050,0,7,bfbf6478) at > kern_open+0xb6 open(c436cc00,db324d04,86,c06acb33,c436cc00) at > open+0x1a syscall(14da003b,bf2f003b,bf2f003b,bfbf6488,15696050) at > syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- > syscall (5, FreeBSD ELF32, open), eip = 0x28a70b5f, esp = > 0xbfbf644c, ebp = 0xbfbf6478 --- I believe this is during playback startup, right? If so, just ignore it for a while, it is quite harmless (although a bit annoying). I'll fix it alltogether hopefully before new year. -- Ariff Abdullah MyBSD http://www.MyBSD.org.my (IPv6/IPv4) http://staff.MyBSD.org.my (IPv6/IPv4) http://tomoyo.MyBSD.org.my (IPv6/IPv4) From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 17:24:14 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 83CD816A41F for ; Sat, 10 Dec 2005 17:24:14 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from portpc-design.spb.ru (portpc-design.spb.ru [81.176.64.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFA1A43D53 for ; Sat, 10 Dec 2005 17:24:10 +0000 (GMT) (envelope-from mcsi@mcsi.pp.ru) Received: from [85.140.159.33] (ppp85-140-159-33.pppoe.mtu-net.ru [85.140.159.33]) (authenticated bits=0) by portpc-design.spb.ru (8.13.5/8.13.5) with ESMTP id jBAHO6GF014691; Sat, 10 Dec 2005 20:24:07 +0300 (MSK) (envelope-from mcsi@mcsi.pp.ru) Message-ID: <439B0F32.1060201@mcsi.pp.ru> Date: Sat, 10 Dec 2005 20:24:02 +0300 From: Maxim Maximov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051204 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: Ariff Abdullah References: <439AF7C0.9060801@mcsi.pp.ru> <20051211011355.4b0b3f78.skywizard@MyBSD.org.my> In-Reply-To: <20051211011355.4b0b3f78.skywizard@MyBSD.org.my> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on 81.176.64.226 X-Virus-Status: Clean Cc: current@freebsd.org Subject: Re: LOR in pcm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 17:24:14 -0000 Ariff Abdullah wrote: > On Sat, 10 Dec 2005 18:44:00 +0300 > Maxim Maximov wrote: > >>Hi all. >> >> Got this on SMP CURRENT from Sun Dec 4 22:06:46 MSK 2005. >> I have no recording devices, FWIW. >> >>lock order reversal: >> 1st 0xc35884c0 pcm0 (sound cdev) @ >> /usr/src/sys/dev/sound/pcm/dsp.c:277 2nd 0xc3562ac0 pcm0:record:0 >> (pcm record channel) @ >>/usr/src/sys/dev/sound/pcm/dsp.c:290 >>KDB: stack backtrace: >>kdb_backtrace(0,ffffffff,c09a4d28,c09a4cb0,c0929504) at >>kdb_backtrace+0x29 witness_checkorder(c3562ac0,9,c08ab43d,122) at >>witness_checkorder+0x580 >>_mtx_lock_flags(c3562ac0,0,c08ab43del22,1) at >>_mtx_lock_flags+0x5b dsp_open(c3586c00,7,2000,c436cc00,c0995100) at >>dsp_open+0x2b2 giant_open(c3586c00,7,2000,c436cc00,c3586c00) at >>giant_open+0x30 devfs_open(db324a18) at devfs_open+0x223 >>VOP_OPEN_APV(c0921cc0,db324a18) at VOP_OPEN_APV+0x7e >>vn_open_cred(db324b70,db324c70,468,c3ee6b80,43) at >>vn_open_cred+0x448 vn_open(db324b70,db324c70,468,43,c09e2ad0) at >>vn_open+0x1e kern_open(c436cc00,15696050,0,7,bfbf6478) at >>kern_open+0xb6 open(c436cc00,db324d04,86,c06acb33,c436cc00) at >>open+0x1a syscall(14da003b,bf2f003b,bf2f003b,bfbf6488,15696050) at >>syscall+0x27e Xint0x80_syscall() at Xint0x80_syscall+0x1f --- >>syscall (5, FreeBSD ELF32, open), eip = 0x28a70b5f, esp = >>0xbfbf644c, ebp = 0xbfbf6478 --- > > > I believe this is during playback startup, right? I'm sorry, I'm not sure. I noticed it after a while. > If so, just ignore > it for a while, it is quite harmless (although a bit annoying). I'll > fix it alltogether hopefully before new year. Thanks! -- Maxim Maximov From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 17:29:56 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A5B4316A41F for ; Sat, 10 Dec 2005 17:29:56 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (pm1.irt.drexel.edu [144.118.29.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A27843D58 for ; Sat, 10 Dec 2005 17:29:55 +0000 (GMT) (envelope-from jsmith@drexel.edu) Received: from smtp.mail.drexel.edu (localhost.localdomain [127.0.0.1]) by smtp.mail.drexel.edu (Postfix) with SMTP id 47A06225E9A for ; Sat, 10 Dec 2005 12:29:55 -0500 (EST) Received: from vorpal.math.drexel.edu (vorpal.math.drexel.edu [129.25.6.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mail.drexel.edu (Postfix) with ESMTP id 3787F225E71 for ; Sat, 10 Dec 2005 12:29:55 -0500 (EST) Received: from [IPv6:::1] (vorpal.math.drexel.edu [129.25.6.250]) by vorpal.math.drexel.edu (8.13.4/8.13.4) with ESMTP id jBAHTsAD010784 for ; Sat, 10 Dec 2005 12:29:54 -0500 (EST) (envelope-from jsmith@drexel.edu) Message-ID: <439B1092.4080400@drexel.edu> Date: Sat, 10 Dec 2005 12:29:54 -0500 From: Justin Smith User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051204) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: No xpt devices X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 17:29:56 -0000 FreeBSD jsmith.org 6.0-STABLE FreeBSD 6.0-STABLE #0: Thu Dec 8 09:31:42 EST 2005 jsmith@jsmith.org:/usr/obj/usr/src/sys/MYKERNEL i386 I'm trying to burn CD's and have my kernel configured with the pass, cd, and atapcam devices. I get /dev/cd0 and /dev/pass0 but no /dev/xpt0 Any suggestions? From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 18:38:56 2005 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E69E516A41F; Sat, 10 Dec 2005 18:38:56 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: from av9-1-sn2.hy.skanova.net (av9-1-sn2.hy.skanova.net [81.228.8.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6DDB43D5D; Sat, 10 Dec 2005 18:38:52 +0000 (GMT) (envelope-from joel@FreeBSD.org) Received: by av9-1-sn2.hy.skanova.net (Postfix, from userid 502) id 00CDF37F8D; Sat, 10 Dec 2005 19:38:50 +0100 (CET) Received: from smtp4-2-sn2.hy.skanova.net (smtp4-2-sn2.hy.skanova.net [81.228.8.93]) by av9-1-sn2.hy.skanova.net (Postfix) with ESMTP id E1A2337E4E; Sat, 10 Dec 2005 19:38:50 +0100 (CET) Received: from t3o55p46.telia.com (t3o55p46.telia.com [62.20.171.46]) by smtp4-2-sn2.hy.skanova.net (Postfix) with ESMTP id DB02937E42; Sat, 10 Dec 2005 19:38:49 +0100 (CET) From: Joel Dahl To: Erik =?ISO-8859-1?Q?N=F8rgaard?= In-Reply-To: <439AE13D.1040800@locolomo.org> References: <439AE13D.1040800@locolomo.org> Content-Type: text/plain; charset=iso8859-15 Date: Sat, 10 Dec 2005 19:38:55 +0100 Message-Id: <1134239935.685.8.camel@dude.automatvapen.se> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: netchild@FreeBSD.org, current@FreeBSD.org Subject: Re: Contacts for project idea list X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 18:38:57 -0000 On Sat, 2005-12-10 at 15:07 +0100, Erik Nørgaard wrote: > Hi, > > One on the questions-list pointed my attention to the PXE installer > project on the project idea list http://www.freebsd.org/projects/ideas/ > > There is no responsible for the project yet, nor are there any technical > contacts for the category (userland/installation tools) nor is there any > contact address for the idea-list maintainer. > > So ... who came up with this idea? Who should I bug if I want to > contribute to this? > > Looking at this, it seems that the sysinstall renewal project is > relevant if anyone knows about that... Yes, we're still looking for developers to act as technical contacts for a few projects. I think netchild@ invented the PXE installer project and the sysinstall renewal project, based upon feature requests from users... > PS: It would be great if the one who maintain the idea list had his/her > address listed - just in case other contact info is missing or someone > thinks up some brilliant idea. Done. -- Joel - joel at FreeBSD dot org From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 18:52:13 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC3B216A41F for ; Sat, 10 Dec 2005 18:52:13 +0000 (GMT) (envelope-from caelian@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA44643D53 for ; Sat, 10 Dec 2005 18:51:54 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by wproxy.gmail.com with SMTP id i22so1139971wra for ; Sat, 10 Dec 2005 10:51:52 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:to:cc:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=h8knuNuW6I4ZMYM1LzpjsSUI51nalH14mQHh1BMTs3/HbW70nL90iNptBa5E4ZlipH0P5tKef4U7X1spLs8RlzF/7viv+JRPRrg/5khxNE4F9Aa9+i9RmSW4cfPtFYkGWZ3atDYYeQFzR4YMcdUrtXlKRNTK72mlRcZD7cwFQgc= Received: by 10.65.53.6 with SMTP id f6mr4912682qbk; Sat, 10 Dec 2005 10:51:52 -0800 (PST) Received: from synergy.odyssey.homeunix.org ( [68.190.230.198]) by mx.gmail.com with ESMTP id q13sm258901qbq.2005.12.10.10.51.51; Sat, 10 Dec 2005 10:51:52 -0800 (PST) From: Pascal Hofstee To: "Bjoern A. Zeeb" In-Reply-To: <20051209175607.C23668@maildrop.int.zabbadoz.net> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> Content-Type: text/plain Date: Sat, 10 Dec 2005 10:51:41 -0800 Message-Id: <1134240701.767.3.camel@synergy.odyssey.homeunix.org> Mime-Version: 1.0 X-Mailer: Evolution 2.5.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 18:52:14 -0000 On Fri, 2005-12-09 at 20:28 +0000, Bjoern A. Zeeb wrote: > Hi, > > everyone out there who had only seen timeouts like > nve0: device timeout (4) > on nve and __never got it working at all__ please try this patch[1] > which made my nve working from 0 to 99. > > I still can get timeouts by for example flood pinging another machine > on the local LAN but it all recovers on it's own and I can work on > that machine and do things like find / over ssh without losing > connectivity. Fixing the timeouts will be another problem that needs > to be addressed later. Just thought i'd say that this patch also makes the onboard nve chip on my EPOX 9NDA3+ (likely the same chip as David Xu's 9NDA3J board). I still get the occasional sputter of an nve0 device timeout(x) though x seems to be a constant "1" .. instead of the typical climbing towards 64 i have seen happening on other nve-boards. -- Pascal Hofstee From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 18:53:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 228AE16A41F for ; Sat, 10 Dec 2005 18:53:15 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 915DC43D66 for ; Sat, 10 Dec 2005 18:52:53 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.13.4/8.13.4) with ESMTP id jBAIqq0L037724 for ; Sat, 10 Dec 2005 10:52:52 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.13.4/8.13.1/Submit) id jBAIqqfh037723 for freebsd-current@freebsd.org; Sat, 10 Dec 2005 10:52:52 -0800 (PST) (envelope-from sgk) Date: Sat, 10 Dec 2005 10:52:52 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20051210185251.GA37701@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: is hw.physmem a unsigned long X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 18:53:15 -0000 Is hw.physmem an unsigned long on all FreeBSD architectures? -- Steve From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 19:09:19 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 41ED716A41F for ; Sat, 10 Dec 2005 19:09:19 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from mail23.syd.optusnet.com.au (mail23.syd.optusnet.com.au [211.29.133.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id B838243D6D for ; Sat, 10 Dec 2005 19:09:06 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail23.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id jBAJ90ak014656 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 11 Dec 2005 06:09:01 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1]) by cirb503493.alcatel.com.au (8.12.10/8.12.10) with ESMTP id jBAJ90Hh073698; Sun, 11 Dec 2005 06:09:00 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id jBAJ90gu073697; Sun, 11 Dec 2005 06:09:00 +1100 (EST) (envelope-from pjeremy) Date: Sun, 11 Dec 2005 06:09:00 +1100 From: Peter Jeremy To: Steve Kargl Message-ID: <20051210190900.GZ32006@cirb503493.alcatel.com.au> References: <20051210185251.GA37701@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051210185251.GA37701@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.2.1i X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc Cc: freebsd-current@freebsd.org Subject: Re: is hw.physmem a unsigned long X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 19:09:19 -0000 On Sat, 2005-Dec-10 10:52:52 -0800, Steve Kargl wrote: >Is hw.physmem an unsigned long on all FreeBSD architectures? Since sysctl_hw_physmem() is in an MI file (sys/kern/kern_mib.c), yes. Interestingly, physmem in the kernel is a signed long on all architectures. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 20:16:05 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDB2716A41F; Sat, 10 Dec 2005 20:16:05 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 46D2243D60; Sat, 10 Dec 2005 20:16:04 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost2.sentex.ca (8.13.4/8.13.4) with ESMTP id jBAKG2Jg035153; Sat, 10 Dec 2005 15:16:02 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp1.sentex.ca (8.13.3/8.13.3) with ESMTP id jBAKG3ZU009275; Sat, 10 Dec 2005 15:16:03 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id E66327302F; Sat, 10 Dec 2005 15:16:02 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051210201602.E66327302F@freebsd-current.sentex.ca> Date: Sat, 10 Dec 2005 15:16:02 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.51 on 205.211.164.50 Cc: Subject: [head tinderbox] failure on alpha/alpha X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 20:16:06 -0000 TB --- 2005-12-10 18:59:54 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-12-10 18:59:54 - starting HEAD tinderbox run for alpha/alpha TB --- 2005-12-10 18:59:54 - cleaning the object tree TB --- 2005-12-10 19:00:19 - checking out the source tree TB --- 2005-12-10 19:00:19 - cd /tinderbox/HEAD/alpha/alpha TB --- 2005-12-10 19:00:19 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-12-10 19:06:16 - building world (CFLAGS=-O2 -pipe) TB --- 2005-12-10 19:06:16 - cd /src TB --- 2005-12-10 19:06:16 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2005-12-10 20:11:31 - generating LINT kernel config TB --- 2005-12-10 20:11:31 - cd /src/sys/alpha/conf TB --- 2005-12-10 20:11:31 - /usr/bin/make -B LINT TB --- 2005-12-10 20:11:32 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-12-10 20:11:32 - cd /src TB --- 2005-12-10 20:11:32 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Dec 10 20:11:32 UTC 2005 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/ata/atapi-fd.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/ata/atapi-tape.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/awi/am79c930.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/awi/awi.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/awi/if_awi_pccard.c cc -c -O2 -pipe -fno-strict-aliasing -mcpu=ev4 -mtune=ev5 -mieee -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mno-fp-regs -ffixed-8 -Wa,-mev6 -ffreestanding -Werror /src/sys/dev/bge/if_bge.c /src/sys/dev/bge/if_bge.c: In function `bge_intr': /src/sys/dev/bge/if_bge.c:3710: warning: 'status' might be used uninitialized in this function *** Error code 1 Stop in /obj/alpha/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-12-10 20:16:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-12-10 20:16:02 - ERROR: failed to build lint kernel TB --- 2005-12-10 20:16:02 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 21:18:28 2005 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77C6916A41F for ; Sat, 10 Dec 2005 21:18:28 +0000 (GMT) (envelope-from ebola@psychoholics.org) Received: from mail.psychoholics.org (www.psychoholics.org [64.185.102.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D69143D53 for ; Sat, 10 Dec 2005 21:18:27 +0000 (GMT) (envelope-from ebola@psychoholics.org) Received: from S010600e018998877.su.shawcable.net (S010600e018998877.su.shawcable.net [24.109.49.151]) by mail.psychoholics.org (Postfix) with ESMTP id B002915716B; Sat, 10 Dec 2005 15:10:03 -0800 (PST) From: Adam Gregoire To: "Bjoern A. Zeeb" In-Reply-To: <20051209175607.C23668@maildrop.int.zabbadoz.net> References: <20051209175607.C23668@maildrop.int.zabbadoz.net> Content-Type: text/plain Date: Sat, 10 Dec 2005 16:19:54 -0500 Message-Id: <1134249594.61298.5.camel@S01060080c83f4fb0.su.shawcable.net> Mime-Version: 1.0 X-Mailer: Evolution 2.5.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: FreeBSD current mailing list Subject: Re: nve(4) patch - please test! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 21:18:28 -0000 On Fri, 2005-12-09 at 20:28 +0000, Bjoern A. Zeeb wrote: > Hi, > > everyone out there who had only seen timeouts like > nve0: device timeout (4) > on nve and __never got it working at all__ please try this patch[1] > which made my nve working from 0 to 99. So far it seem to be working correctly on my Asus K8N-E Deluxe(MCP7) NIC. I will hammer away at the NIC and report any ill findings. -- Adam Gregoire From owner-freebsd-current@FreeBSD.ORG Sat Dec 10 22:39:08 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4763616A41F for ; Sat, 10 Dec 2005 22:39:08 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from avmta3-rme.xtra.co.nz (avmta3-rme.xtra.co.nz [210.86.15.158]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F1CD43D46 for ; Sat, 10 Dec 2005 22:39:05 +0000 (GMT) (envelope-from andrew@fubar.geek.nz) Received: from mta4-rme.xtra.co.nz ([210.86.15.193]) by avmta3-rme.xtra.co.nz with ESMTP id <20051210223904.WGKD1410.avmta3-rme.xtra.co.nz@mta4-rme.xtra.co.nz> for ; Sun, 11 Dec 2005 11:39:04 +1300 Received: from serv.int.fubar.geek.nz ([222.152.219.118]) by mta4-rme.xtra.co.nz with ESMTP id <20051210223904.VGMC1416.mta4-rme.xtra.co.nz@serv.int.fubar.geek.nz> for ; Sun, 11 Dec 2005 11:39:04 +1300 Received: from [192.168.1.160] (unknown [192.168.1.160]) by serv.int.fubar.geek.nz (Postfix) with ESMTP id E91FF611A for ; Sun, 11 Dec 2005 11:39:02 +1300 (NZDT) Message-ID: <439B5907.4010809@fubar.geek.nz> Date: Sun, 11 Dec 2005 11:39:03 +1300 From: Andrew Turner User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: BSDInstaller Beta 2 release X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Dec 2005 22:39:08 -0000 I am pleased to announce the second release of FreeBSD install CD's based on the BSD Installer. The new Lua backend is now being used in this release rather than the older, deprecated C version. The CD image is available from ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/bsdinstaller/7.0-BSDINSTALLER-BETA-2-i386-disc1.iso.gz or your local mirror MD5 (7.0-BSDINSTALLER-BETA-2-i386-disc1.iso) = 1becb489666ee97f5e10ebc5a0987f2d SHA256 (7.0-BSDINSTALLER-BETA-2-i386-disc1.iso) = e5f6114258e1b66adfd84636ffbd3286c7ad41dadab42e615da68f5b0cf8cbaf As with the previous Beta release there are three virtual consoles available: * ttyv0: The frontend * ttyv1: The backend * ttyv2: A standard login screen to login as root with no password Changes Since BETA-1 * Can now install Source * Can now install the Ports tree * Can now install Packages * Change to the new Lua backend Known Problems * Can only install to one drive, can't have / on ad0 and /usr on ad1 * fdisk doesn't alter the geometry Thank you to Scott Long for providing a computer to build this with.