From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 03:12: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 5C27E16A41F for ; Sun, 27 Nov 2005 03:12:24 +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 D1A3A43D45 for ; Sun, 27 Nov 2005 03:12:23 +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 jAR3CMjv079476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 27 Nov 2005 06:12:22 +0300 (MSK) (envelope-from glebius@FreeBSD.org) Received: (from glebius@localhost) by cell.sick.ru (8.13.3/8.13.1/Submit) id jAR3CL6k079475 for current@FreeBSD.org; Sun, 27 Nov 2005 06:12:22 +0300 (MSK) (envelope-from glebius@FreeBSD.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@FreeBSD.org using -f Date: Sun, 27 Nov 2005 06:12:21 +0300 From: Gleb Smirnoff To: current@FreeBSD.org Message-ID: <20051127031221.GX25711@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.6i Cc: Subject: panic on kldunload X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 03:12:24 -0000 Today running 'kldunload ng_netflow' I have experienced the following panic: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 01 fault virtual address = 0x15 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06568cd stack pointer = 0x28:0xe889fbcc frame pointer = 0x28:0xe889fbec 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 = 91858 (kldunload) trap number = 12 panic: page fault cpuid = 1 Uptime: 15h36m21s Dumping 1023 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 1023MB (261856 pages) 1007 991 975 959 (CTRL-C to abort) 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 #0 doadump () at pcpu.h:165 During symbol reading, Incomplete CFI data; unspecified registers at 0xc051f7c2. #1 0xc051fe2f in boot (howto=0x104) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc052020e in panic (fmt=0xc06d69b8 "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc06af7b1 in trap_fatal (frame=0xe889fb8c, eva=0x0) at /usr/src/sys/i386/i386/trap.c:831 #4 0xc06af46f in trap_pfault (frame=0xe889fb8c, usermode=0x0, eva=0x15) at /usr/src/sys/i386/i386/trap.c:742 #5 0xc06aeff9 in trap (frame= {tf_fs = 0xc8d20008, tf_es = 0xe8890028, tf_ds = 0xc0540028, tf_edi = 0xc0c61960, tf_esi = 0xc0c6c8c0, tf_ebp = 0xe889fbec, tf_isp = 0xe889fbb8, tf_ebx = 0x1, tf_edx = 0xc0c6c8c8, tf_ecx = 0x0, tf_eax = 0x18, tf_trapno = 0xc, tf_err = 0x0, tf_eip = 0xc06568cd, tf_cs = 0x20, tf_eflags = 0x10202, tf_esp = 0x0, tf_ss = 0xe889fc10}) at /usr/src/sys/i386/i386/trap.c:432 #6 0xc069a5aa in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc06568cd in uma_zfree_internal (zone=0xc0c61960, item=0xcc763c00, udata=0x0, skip=SKIP_DTOR, flags=0x3) at /usr/src/sys/vm/uma_core.c:2465 #8 0xc06567c5 in uma_zfree_arg (zone=0xc0c61960, item=0xcc763c00, udata=0x0) at /usr/src/sys/vm/uma_core.c:2420 #9 0xc0512474 in malloc_uninit (data=0xcc742300) at uma.h:303 #10 0xc050cfb3 in linker_file_sysuninit (lf=0x18) at /usr/src/sys/kern/kern_linker.c:238 #11 0xc050d845 in linker_file_unload (file=0xc9238000, flags=0x0) at /usr/src/sys/kern/kern_linker.c:539 #12 0xc050e104 in kern_kldunload (td=0xc9238000, fileid=0x18, flags=0x18) at /usr/src/sys/kern/kern_linker.c:828 #13 0xc050e1ac in kldunloadf (td=0x18, uap=0xc0c6c8c8) at /usr/src/sys/kern/kern_linker.c:858 #14 0xc06afb6d in syscall (frame= {tf_fs = 0x3b, tf_es = 0x3b, tf_ds = 0x3b, tf_edi = 0x3, tf_esi = 0xbfbfed06, tf_ebp = 0xbfbfebd8, tf_isp = 0xe889fd64, tf_ebx = 0x1, tf_edx = 0xbfbfed06, tf_ecx = 0x1, tf_eax = 0x1bc, tf_trapno = 0xc, tf_err = 0x2, tf_eip = 0xe4b65eb, tf_cs = 0x33, tf_eflags = 0x246, tf_esp = 0xbfbfe76c, tf_ss = 0x3b}) at /usr/src/sys/i386/i386/trap.c:976 #15 0xc069a5ff in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 What I can't understand here, is why did it panic?! Looking at frame 7 I see a valid pointer and a cast: (kgdb) frame 7 #7 0xc06568cd in uma_zfree_internal (zone=0xc0c61960, item=0xcc763c00, udata=0x0, skip=SKIP_DTOR, flags=0x3) at /usr/src/sys/vm/uma_core.c:2465 2465 slab = (uma_slab_t)mem; (kgdb) list 2460 mem = (u_int8_t *)((unsigned long)item & (~UMA_SLAB_MASK)); 2461 if (keg->uk_flags & UMA_ZONE_HASH) 2462 slab = hash_sfind(&keg->uk_hash, mem); 2463 else { 2464 mem += keg->uk_pgoff; 2465 slab = (uma_slab_t)mem; 2466 } 2467 } else { 2468 slab = (uma_slab_t)udata; 2469 } (kgdb) p mem $9 = (u_int8_t *) 0xc0c6c8c8 "¤/qÀ LnÀs5nÀ" (kgdb) p slab $10 = 0x0 (kgdb) p *(uma_slab_t)mem $11 = { us_head = { us_keg = 0xc0712fa4, us_type = { _us_link = { le_next = 0xc06e4c20, le_prev = 0xc06e3573 }, _us_size = 0xc06e4c20 }, us_hlink = { sle_next = 0x430000 }, us_data = 0x0, us_flags = 0x0, us_freecount = 0x0, us_firstfree = 0x0 }, us_freelist = {{ us_item = 0x0 }} } (kgdb) The panic happened on 6.0-STABLE, but I don't think it isn't applicable to CURRENT. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 09:56: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 5292A16A41F for ; Sun, 27 Nov 2005 09:56:11 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from insomma.datacode.it (ip-152-166.sn2.eutelia.it [83.211.152.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 077C643D58 for ; Sun, 27 Nov 2005 09:56:09 +0000 (GMT) (envelope-from massimo@cedoc.mo.it) Received: from localhost (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with SMTP id 3D2CF2C90C for ; Sun, 27 Nov 2005 10:56:07 +0100 (CET) Received: from insomma.datacode.it (localhost.datacode.it [127.0.0.1]) by insomma.datacode.it (Postfix) with ESMTP id 78E5F2C90A for ; Sun, 27 Nov 2005 10:56:06 +0100 (CET) Received: from massimo.datacode.it (massimo.datacode.it [192.168.1.13]) by insomma.datacode.it (Postfix) with ESMTP id 382492C906 for ; Sun, 27 Nov 2005 10:56:06 +0100 (CET) From: Massimo Lusetti To: freebsd-current@freebsd.org In-Reply-To: <20051127031221.GX25711@cell.sick.ru> References: <20051127031221.GX25711@cell.sick.ru> Content-Type: text/plain Organization: CEDOC - Modena Date: Sun, 27 Nov 2005 10:56:05 +0100 Message-Id: <1133085365.4315.1.camel@massimo.datacode.it> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-7) Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: Re: panic on kldunload X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 09:56:11 -0000 On Sun, 2005-11-27 at 06:12 +0300, Gleb Smirnoff wrote: > Today running 'kldunload ng_netflow' I have experienced the > following panic: Just a note (sorry) cause i cannot produce debug but the same happens here with 'kldunload reiserfs' -- Massimo.run(); From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 10:46: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 347B416A41F for ; Sun, 27 Nov 2005 10:46:46 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from relay.xtra-net.org (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 43EF243D45 for ; Sun, 27 Nov 2005 10:46:42 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 7712 invoked from network); 27 Nov 2005 10:46:40 -0000 Received: from wbedllfs.xtra-net.org (192.168.1.21) by 0 with SMTP; 27 Nov 2005 10:46:40 -0000 From: Vincent Blondel To: current@freebsd.org Content-Type: text/plain Date: Sun, 27 Nov 2005 11:46:37 +0100 Message-Id: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 10:46:46 -0000 Hello all, I am trying to use dvd::rip but I encounter some problems and get this error message ... tcprobe output was: [tcprobe] OSS audio device No support for oss compiled in [tcprobe] summary for /dev/acd0, (*) = not default, 0 = not detected no audio track: use "null" import module for audio DVDRIP_SUCCESS at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm line 137 Has somebody any experience with dvd::rip with FreeBSD ?? Thanks to help me. Regards From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 15:34: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 7812516A420 for ; Sun, 27 Nov 2005 15:34:22 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (www.creo.hu [217.113.62.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93FCE43D6B for ; Sun, 27 Nov 2005 15:34:19 +0000 (GMT) (envelope-from csaba@beastie.creo.hu) Received: from beastie.creo.hu (localhost [127.0.0.1]) by beastie.creo.hu (8.13.3/8.13.3) with ESMTP id jARFW2DN061626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 27 Nov 2005 16:32:02 +0100 (CET) (envelope-from csaba@beastie.creo.hu) Received: (from csaba@localhost) by beastie.creo.hu (8.13.3/8.13.3/Submit) id jARFW0iA061625; Sun, 27 Nov 2005 16:32:00 +0100 (CET) (envelope-from csaba) Date: Sun, 27 Nov 2005 16:32:00 +0100 From: Csaba Henk To: Ivan Voras Message-ID: <20051127153200.GO2911@beastie.creo.hu> References: <20051126112818.E24836@geri.cc.fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051126112818.E24836@geri.cc.fer.hr> User-Agent: Mutt/1.5.9i X-Mailman-Approved-At: Sun, 27 Nov 2005 17:04:44 +0000 Cc: current@freebsd.org Subject: Re: double close strikes panic if md attaching a corrupt file X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 15:34:22 -0000 On Sat, Nov 26, 2005 at 11:30:49AM +0100, Ivan Voras wrote: > Maybe gnop GEOM class would help here? (the "-f" option) Hm, we need a regular file, not a device. Yes, the nop device can be mounted and can contain regular files, but having an fs mounted where every operation is fallible seems to be too much of this goodness :) I guess I will hack some existing fs code, as Robert Watson suggested. Thanks for the idea, I didn't know of this utility. Csaba From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 20:47: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 9281C16A41F for ; Sun, 27 Nov 2005 20:47:10 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: from valimar.ibest.com.br (mx11.ibest.com.br [200.181.68.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E13843D98 for ; Sun, 27 Nov 2005 20:46:43 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: from [127.0.0.1] (centaurus.ibest.com.br [200.181.68.107]) by valimar.ibest.com.br (Postfix) with ESMTP id D423617C1D0; Sun, 27 Nov 2005 18:46:35 -0200 (BRDT) Message-ID: <438A1B09.4030707@gmail.com> Date: Sun, 27 Nov 2005 18:46:01 -0200 From: Rainer Alves User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051105) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vincent Blondel References: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> In-Reply-To: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-iBEST-MailScanner-Information: Please contact the ISP for more information X-MailScanner-From: rainer.alves@gmail.com Cc: current@freebsd.org Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 20:47:10 -0000 Vincent Blondel wrote: >Hello all, > >I am trying to use dvd::rip but I encounter some problems and get this >error message > > ... > tcprobe output was: > > [tcprobe] OSS audio device > No support for oss compiled in > [tcprobe] summary for /dev/acd0, (*) = not default, 0 = not detected > no audio track: use "null" import module for audio > DVDRIP_SUCCESS > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm >line 137 > >Has somebody any experience with dvd::rip with FreeBSD ?? >Thanks to help me. > >Regards > > I've had the same issue here... instead of trying to read the TOC and ripping the DVD directly from /dev/acd0, first mount the DVD under /cdrom, then go to the preferences panel and change both "DVD device" and "DVD mount point" to /cdrom. This should solve your problem. -- Rainer Alves From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 20:54: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 3845216A41F for ; Sun, 27 Nov 2005 20:54:54 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0FAE143D82 for ; Sun, 27 Nov 2005 20:54:39 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EgTXi-000GBH-GQ for freebsd-current@freebsd.org; Sun, 27 Nov 2005 20:54:38 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EgTXg-0006zE-8S for freebsd-current@freebsd.org; Sun, 27 Nov 2005 12:54:36 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17290.7435.851684.533219@roam.psg.com> Date: Sun, 27 Nov 2005 10:54:35 -1000 To: FreeBSD Current Subject: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 20:54:54 -0000 cvsup at 20:39 cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/mpt/../../dev/mpt/mpt_raid.c ld -d -warn-common -r -d -o mpt.kld mpt.o mpt_cam.o mpt_debug.o mpt_pci.o mpt_raid.o touch export_syms awk -f /usr/src/sys/modules/mpt/../../conf/kmod_syms.awk mpt.kld export_syms | xargs -J% objcopy % mpt.kld ld -Bshareable -d -warn-common -o mpt.ko.debug mpt.kld objcopy --only-keep-debug mpt.ko.debug mpt.ko.symbols objcopy --strip-debug --add-gnu-debuglink=mpt.ko.symbols mpt.ko.debug mpt.ko ===> mqueue (all) cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -g -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c: In function `mq_open': /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function *** Error code 1 From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 20:55: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 187BB16A45D; Sun, 27 Nov 2005 20:55:30 +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 4107C43D83; Sun, 27 Nov 2005 20:55:05 +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 <0IQM00IQCSRHP2G0@VL-MO-MR004.ip.videotron.ca>; Sun, 27 Nov 2005 15:54:53 -0500 (EST) Date: Sun, 27 Nov 2005 15:54:42 -0500 From: Nicolas Blais In-reply-to: <438A1B09.4030707@gmail.com> To: freebsd-current@freebsd.org Message-id: <200511271554.47717.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1227557.41q7pIao8S; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> <438A1B09.4030707@gmail.com> User-Agent: KMail/1.8.3 Cc: Vincent Blondel , Rainer Alves , current@freebsd.org Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 20:55:30 -0000 --nextPart1227557.41q7pIao8S Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On November 27, 2005 03:46 pm, Rainer Alves wrote: > Vincent Blondel wrote: > >Hello all, > > > >I am trying to use dvd::rip but I encounter some problems and get this > >error message > > > > ... > > tcprobe output was: > > > > [tcprobe] OSS audio device > > No support for oss compiled in > > [tcprobe] summary for /dev/acd0, (*) =3D not default, 0 =3D not dete= cted > > no audio track: use "null" import module for audio > > DVDRIP_SUCCESS > > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm > >line 137 > > > >Has somebody any experience with dvd::rip with FreeBSD ?? > >Thanks to help me. > > > >Regards > > I've had the same issue here... instead of trying to read the TOC and > ripping the DVD directly from /dev/acd0, first mount the DVD under > /cdrom, then go to the preferences panel and change both "DVD device" > and "DVD mount point" to /cdrom. This should solve your problem. > > -- > Rainer Alves > Actually, that error message is caused by transcode not using the oss_modul= e. =20 A recent commit to the transcode port fixes that issue (transcode-1.0.1_1).= =20 Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #2: Sat Nov 26 10:55:30 EST 2005 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1227557.41q7pIao8S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQBDih0X4wTBlvcsbJURAmITAJYhec8meHLJ5Z2kCaLPeMyrkFqLAJ4xnlma wF4LcxYCnjDzNbIGqFsWPg== =kbyS -----END PGP SIGNATURE----- --nextPart1227557.41q7pIao8S-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 20: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 187BB16A45D; Sun, 27 Nov 2005 20:55:30 +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 4107C43D83; Sun, 27 Nov 2005 20:55:05 +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 <0IQM00IQCSRHP2G0@VL-MO-MR004.ip.videotron.ca>; Sun, 27 Nov 2005 15:54:53 -0500 (EST) Date: Sun, 27 Nov 2005 15:54:42 -0500 From: Nicolas Blais In-reply-to: <438A1B09.4030707@gmail.com> To: freebsd-current@freebsd.org Message-id: <200511271554.47717.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart1227557.41q7pIao8S; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit References: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> <438A1B09.4030707@gmail.com> User-Agent: KMail/1.8.3 Cc: Vincent Blondel , Rainer Alves , current@freebsd.org Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 20:55:30 -0000 --nextPart1227557.41q7pIao8S Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On November 27, 2005 03:46 pm, Rainer Alves wrote: > Vincent Blondel wrote: > >Hello all, > > > >I am trying to use dvd::rip but I encounter some problems and get this > >error message > > > > ... > > tcprobe output was: > > > > [tcprobe] OSS audio device > > No support for oss compiled in > > [tcprobe] summary for /dev/acd0, (*) =3D not default, 0 =3D not dete= cted > > no audio track: use "null" import module for audio > > DVDRIP_SUCCESS > > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm > >line 137 > > > >Has somebody any experience with dvd::rip with FreeBSD ?? > >Thanks to help me. > > > >Regards > > I've had the same issue here... instead of trying to read the TOC and > ripping the DVD directly from /dev/acd0, first mount the DVD under > /cdrom, then go to the preferences panel and change both "DVD device" > and "DVD mount point" to /cdrom. This should solve your problem. > > -- > Rainer Alves > Actually, that error message is caused by transcode not using the oss_modul= e. =20 A recent commit to the transcode port fixes that issue (transcode-1.0.1_1).= =20 Nicolas. =2D-=20 =46reeBSD 7.0-CURRENT #2: Sat Nov 26 10:55:30 EST 2005 =20 nicblais@clk01a:/usr/obj/usr/src/sys/CLK01A=20 PGP? (updated 16 Nov 05) : http://www.clkroot.net/security/nb_root.asc --nextPart1227557.41q7pIao8S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD4DBQBDih0X4wTBlvcsbJURAmITAJYhec8meHLJ5Z2kCaLPeMyrkFqLAJ4xnlma wF4LcxYCnjDzNbIGqFsWPg== =kbyS -----END PGP SIGNATURE----- --nextPart1227557.41q7pIao8S-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 21:09:05 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 9C49216A435 for ; Sun, 27 Nov 2005 21:09:04 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id C239943DD2 for ; Sun, 27 Nov 2005 21:08:20 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by wproxy.gmail.com with SMTP id i20so1592049wra for ; Sun, 27 Nov 2005 13:08:01 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=ocPB/w9T2/dCUfxfX0eMAq1Ty5UryOVJJWoffdXNYnxoHLT4zRzqJ6BmTKSn5VK4QOiC+J7Dt7Q5BXsU8d6C2REVOa2D/LAfWYt/6ZnPV7xemKJe0CDPg4brpy4DHJxx9hcVFPsRmRpK5TlIKGgw+gGqSCmLrwN84lWcUFs2VIs= Received: by 10.54.143.1 with SMTP id q1mr7735915wrd; Sun, 27 Nov 2005 13:08:01 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id d74sm27579wra.2005.11.27.13.08.00; Sun, 27 Nov 2005 13:08:01 -0800 (PST) From: "Michael C. Shultz" To: freebsd-current@freebsd.org Date: Sun, 27 Nov 2005 12:58:21 -0800 User-Agent: KMail/1.8.3 References: <17290.7435.851684.533219@roam.psg.com> In-Reply-To: <17290.7435.851684.533219@roam.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511271258.23017.ringworm01@gmail.com> Cc: Randy Bush Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 21:09:07 -0000 On Sunday 27 November 2005 12:54, Randy Bush wrote: > cvsup at 20:39 > > cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- ^^^^^^^^^^^^^ get rid of -Werror in you CFLAGS, likely you set this in /etc/make.conf -Mike > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq > -I@/../include -finline-limit=8000 -fno-common -g > -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -c > /usr/src/sys/modules/mpt/../../dev/mpt/mpt_raid.c ld -d -warn-common -r -d > -o mpt.kld mpt.o mpt_cam.o mpt_debug.o mpt_pci.o mpt_raid.o touch > export_syms > awk -f /usr/src/sys/modules/mpt/../../conf/kmod_syms.awk mpt.kld > export_syms | xargs -J% objcopy % mpt.kld ld -Bshareable -d -warn-common > -o mpt.ko.debug mpt.kld > objcopy --only-keep-debug mpt.ko.debug mpt.ko.symbols > objcopy --strip-debug --add-gnu-debuglink=mpt.ko.symbols mpt.ko.debug > mpt.ko ===> mqueue (all) > cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- > -DHAVE_KERNEL_OPTION_HEADERS -include > /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq > -I@/../include -finline-limit=8000 -fno-common -g > -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings > -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 > -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -std=c99 -c > /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c > /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c: In function > `mq_open': /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c:1832: > warning: 'mq' might be used uninitialized in this function *** Error code 1 > > _______________________________________________ > 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 Nov 27 21:12: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 F344916A41F for ; Sun, 27 Nov 2005 21:12:06 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 848BF43D75 for ; Sun, 27 Nov 2005 21:12:04 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EgToY-000GdO-Ki; Sun, 27 Nov 2005 21:12:02 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EgToW-00071v-Ck; Sun, 27 Nov 2005 13:12:00 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17290.8479.860308.161622@roam.psg.com> Date: Sun, 27 Nov 2005 11:11:59 -1000 To: "Michael C. Shultz" References: <17290.7435.851684.533219@roam.psg.com> <200511271258.23017.ringworm01@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 21:12:07 -0000 >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- > get rid of -Werror in you CFLAGS, likely you set this in /etc/make.conf it is not set in make.conf KERNCONF=MYNAME #CPUTYPE=pentium-m CPUTYPE?=i686 CFLAGS=-O -pipe #CFLAGS+=-pthread COPTFLAGS=-O -pipe NO_GAMES=true NO_PROFILE=true NO_BIND=true NO_I4B=true NO_IPFILTER=true NO_KERBEROS=true NO_MAILWRAPPER=true NO_OBJC=true NO_SENDMAIL=true MAKE_IDEA=YES X_WINDOW_SYSTEM=xorg HAVE_MOTIF=yes MOTIFLIB=-L${X11BASE}/lib -lXm USA_RESIDENT=YES FORCE_PKG_REGISTER=YES ENABLE_WPA_SUPPLICANT_EAPOL=YES MASTER_SITE_BACKUP?= \ ftp://ftp2.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ MASTER_SITE_OVERRIDE?=${MASTER_SITE_BACKUP} GNOME_DESKTOP_VERSION= 2 MASTER_SITE_GNOME= \ http://www.gtlib.cc.gatech.edu/pub/gnome/%SUBDIR%/ \ http://public.planetmirror.com/pub/gnome/%SUBDIR%/ \ ftp://ftp.cse.buffalo.edu/pub/Gnome/%SUBDIR%/ \ http://archive.progeny.com/GNOME/%SUBDIR%/ \ http://ftp.gnome.org/pub/GNOME/%SUBDIR%/ WITH_LAME= yes # added by use.perl 2005-07-07 15:22:00 PERL_VER=5.8.7 PERL_VERSION=5.8.7 From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 21:27: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 9928916A41F for ; Sun, 27 Nov 2005 21:27:16 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 554BA43D62 for ; Sun, 27 Nov 2005 21:27:01 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by wproxy.gmail.com with SMTP id i30so1585808wra for ; Sun, 27 Nov 2005 13:26:56 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=s+BzfiE6+yQYA5LDhjlHs46L4FwW4gagCfzm78mZ78lQwQjwvZInnjqg0p9tXUg1n3Mf685Ej03braan797fON72YL7ALmhZjtfWHZbiA77M59qhJBtPOSb/I4YJ9DAEtKhmFdA+XUGqG5idBNZD8qEzovG5ZDaQHVP6Y+dl/lc= Received: by 10.54.100.6 with SMTP id x6mr1147744wrb; Sun, 27 Nov 2005 13:26:56 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id 26sm76026wrl.2005.11.27.13.26.56; Sun, 27 Nov 2005 13:26:56 -0800 (PST) From: "Michael C. Shultz" To: Randy Bush Date: Sun, 27 Nov 2005 13:17:20 -0800 User-Agent: KMail/1.8.3 References: <17290.7435.851684.533219@roam.psg.com> <200511271258.23017.ringworm01@gmail.com> <17290.8479.860308.161622@roam.psg.com> In-Reply-To: <17290.8479.860308.161622@roam.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511271317.23209.ringworm01@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 21:27:16 -0000 On Sunday 27 November 2005 13:11, Randy Bush wrote: > >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc > >> -I- > > > > get rid of -Werror in you CFLAGS, likely you set this in /etc/make.conf > > it is not set in make.conf > > KERNCONF=MYNAME > #CPUTYPE=pentium-m > CPUTYPE?=i686 > CFLAGS=-O -pipe > #CFLAGS+=-pthread > COPTFLAGS=-O -pipe > NO_GAMES=true > NO_PROFILE=true > NO_BIND=true > NO_I4B=true > NO_IPFILTER=true > NO_KERBEROS=true > NO_MAILWRAPPER=true > NO_OBJC=true > NO_SENDMAIL=true > MAKE_IDEA=YES > X_WINDOW_SYSTEM=xorg > HAVE_MOTIF=yes > MOTIFLIB=-L${X11BASE}/lib -lXm > USA_RESIDENT=YES > FORCE_PKG_REGISTER=YES > ENABLE_WPA_SUPPLICANT_EAPOL=YES > MASTER_SITE_BACKUP?= \ > ftp://ftp2.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ > MASTER_SITE_OVERRIDE?=${MASTER_SITE_BACKUP} > GNOME_DESKTOP_VERSION= 2 > MASTER_SITE_GNOME= \ > http://www.gtlib.cc.gatech.edu/pub/gnome/%SUBDIR%/ \ > http://public.planetmirror.com/pub/gnome/%SUBDIR%/ \ > ftp://ftp.cse.buffalo.edu/pub/Gnome/%SUBDIR%/ \ > http://archive.progeny.com/GNOME/%SUBDIR%/ \ > http://ftp.gnome.org/pub/GNOME/%SUBDIR%/ > WITH_LAME= yes > > # added by use.perl 2005-07-07 15:22:00 > PERL_VER=5.8.7 > PERL_VERSION=5.8.7 According to http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html -Werror Make all warnings into errors. So you either need to fix all warnings or track down where this -Werror switch is comming from. -Mike From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 21: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 94B2316A41F for ; Sun, 27 Nov 2005 21:34:21 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13C0043D58 for ; Sun, 27 Nov 2005 21:34:20 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so744163nzo for ; Sun, 27 Nov 2005 13:34:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=ThCvNYj8gWjJEJZIfNoyNkllpIR82q8Tn9UAERDimPfiV3UHci+dCqeyo4Wh+Faduz/zA8CyH3vJE06SgMd76Fsq0DQx+dotoADNVVRxB5imdyBWQSbwwSKNXUxtBQ8scU0vS5d/Wwd7YpAehBsCxmY7s00sXwmowlrqCiox6S8= Received: by 10.36.177.18 with SMTP id z18mr2866893nze; Sun, 27 Nov 2005 13:34:20 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id 14sm671416nzp.2005.11.27.13.34.19; Sun, 27 Nov 2005 13:34:20 -0800 (PST) From: "Michael C. Shultz" To: Randy Bush Date: Sun, 27 Nov 2005 13:24:44 -0800 User-Agent: KMail/1.8.3 References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> In-Reply-To: <200511271317.23209.ringworm01@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511271324.45398.ringworm01@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 21:34:21 -0000 On Sunday 27 November 2005 13:17, Michael C. Shultz wrote: > On Sunday 27 November 2005 13:11, Randy Bush wrote: > > >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE -nostdinc > > >> -I- > > > > > > get rid of -Werror in you CFLAGS, likely you set this in /etc/make.conf > > > > it is not set in make.conf > > > > KERNCONF=MYNAME > > #CPUTYPE=pentium-m > > CPUTYPE?=i686 > > CFLAGS=-O -pipe > > #CFLAGS+=-pthread > > COPTFLAGS=-O -pipe > > NO_GAMES=true > > NO_PROFILE=true > > NO_BIND=true > > NO_I4B=true > > NO_IPFILTER=true > > NO_KERBEROS=true > > NO_MAILWRAPPER=true > > NO_OBJC=true > > NO_SENDMAIL=true > > MAKE_IDEA=YES > > X_WINDOW_SYSTEM=xorg > > HAVE_MOTIF=yes > > MOTIFLIB=-L${X11BASE}/lib -lXm > > USA_RESIDENT=YES > > FORCE_PKG_REGISTER=YES ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Here is something else you should fix while your hunting down that -Werror switch, Kris Kennway just posted good advice about why this is a dumb thing to do a week or two ago, you might want to search the mail archives and look it up. -Mike > > ENABLE_WPA_SUPPLICANT_EAPOL=YES > > MASTER_SITE_BACKUP?= \ > > ftp://ftp2.freebsd.org/pub/FreeBSD/ports/distfiles/${DIST_SUBDIR}/ > > MASTER_SITE_OVERRIDE?=${MASTER_SITE_BACKUP} > > GNOME_DESKTOP_VERSION= 2 > > MASTER_SITE_GNOME= \ > > http://www.gtlib.cc.gatech.edu/pub/gnome/%SUBDIR%/ \ > > http://public.planetmirror.com/pub/gnome/%SUBDIR%/ \ > > ftp://ftp.cse.buffalo.edu/pub/Gnome/%SUBDIR%/ \ > > http://archive.progeny.com/GNOME/%SUBDIR%/ \ > > http://ftp.gnome.org/pub/GNOME/%SUBDIR%/ > > WITH_LAME= yes > > > > # added by use.perl 2005-07-07 15:22:00 > > PERL_VER=5.8.7 > > PERL_VERSION=5.8.7 > > According to http://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html > > -Werror > Make all warnings into errors. > > So you either need to fix all warnings or track down where this -Werror > switch is comming from. > > -Mike From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 21:42: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 73F1E16A41F for ; Sun, 27 Nov 2005 21:42:43 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFBA243D58 for ; Sun, 27 Nov 2005 21:42:41 +0000 (GMT) (envelope-from boris@brooknet.com.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86]) by mailout1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jARLgevb003996; Mon, 28 Nov 2005 08:42:40 +1100 Received: from [192.168.0.7] (ppp212F.dyn.pacific.net.au [61.8.33.47]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3) with ESMTP id jARLgcBs019424; Mon, 28 Nov 2005 08:42:38 +1100 In-Reply-To: <200511271324.45398.ringworm01@gmail.com> References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> <200511271324.45398.ringworm01@gmail.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <02B468A9-B719-456B-8422-19005379CCCD@brooknet.com.au> Content-Transfer-Encoding: 7bit From: Sam Lawrance Date: Mon, 28 Nov 2005 08:42:37 +1100 To: "Michael C. Shultz" X-Mailer: Apple Mail (2.746.2) Cc: Randy Bush , freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 21:42:43 -0000 On 28/11/2005, at 8:24 AM, Michael C. Shultz wrote: > On Sunday 27 November 2005 13:17, Michael C. Shultz wrote: >> On Sunday 27 November 2005 13:11, Randy Bush wrote: >>>>> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE - >>>>> nostdinc >>>>> -I- >>>> >>>> get rid of -Werror in you CFLAGS, likely you set this in /etc/ >>>> make.conf >>> >>> it is not set in make.conf >>> ... >>> USA_RESIDENT=YES >>> FORCE_PKG_REGISTER=YES > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > Here is something else you should fix while your hunting down that - > Werror > switch, Kris Kennway just posted good advice about why this is a > dumb thing > to do a week or two ago, you might want to search the mail archives > and look > it up. Guess whose make.conf Kris was commenting on :-) From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:09: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 54DED16A41F for ; Sun, 27 Nov 2005 22:09:49 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAD5F43D49 for ; Sun, 27 Nov 2005 22:09:48 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EgUiS-000I6u-4b; Sun, 27 Nov 2005 22:09:48 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EgUiQ-00075d-U2; Sun, 27 Nov 2005 14:09:47 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17290.11946.415967.173429@roam.psg.com> Date: Sun, 27 Nov 2005 12:09:46 -1000 To: "Michael C. Shultz" References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> <200511271324.45398.ringworm01@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:09:49 -0000 >>> FORCE_PKG_REGISTER=YES > Here is something else you should fix while your hunting down that -Werror > switch, Kris Kennway just posted good advice about why this is a dumb thing > to do a week or two ago, you might want to search the mail archives and look > it up. he posted it in response to a msg from me, so i saw it for sure problem is that gnome would not upgrade without it. randy From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:11: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 273AF16A41F for ; Sun, 27 Nov 2005 22:11:04 +0000 (GMT) (envelope-from sean@gothic.net.au) Received: from visi.gothic.net.au (visi.gothic.net.au [202.182.72.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2972743D73 for ; Sun, 27 Nov 2005 22:10:56 +0000 (GMT) (envelope-from sean@gothic.net.au) Received: from localhost (localhost [127.0.0.1]) by visi.gothic.net.au (Postfix) with ESMTP id 7BA92264D1; Mon, 28 Nov 2005 09:10:54 +1100 (EST) Received: from localhost ([127.0.0.1]) by localhost (visi.gothic.net.au [127.0.0.1]) (amavisd-new, port 10026) with SMTP id 30819-08; Mon, 28 Nov 2005 09:10:51 +1100 (EST) Received: from [10.99.34.33] (home.winn.id.au [202.182.72.30]) by visi.gothic.net.au (Postfix) with ESMTP id B7CFC264C2; Mon, 28 Nov 2005 09:10:50 +1100 (EST) In-Reply-To: <200511271258.23017.ringworm01@gmail.com> References: <17290.7435.851684.533219@roam.psg.com> <200511271258.23017.ringworm01@gmail.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-203426524; protocol="application/pkcs7-signature" Message-Id: <7FEAFB8D-F487-43BD-9B9F-F97A6DAC9406@gothic.net.au> From: Sean Winn Date: Mon, 28 Nov 2005 09:10:48 +1100 To: Michael C. Shultz X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at gothic.net.au X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Randy Bush , freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:11:04 -0000 --Apple-Mail-2-203426524 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On 28/11/2005, at 7:58 AM, Michael C. Shultz wrote: > On Sunday 27 November 2005 12:54, Randy Bush wrote: >> cvsup at 20:39 >> >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE - >> nostdinc -I- > ^^^^^^^^^^^^^ > > get rid of -Werror in you CFLAGS, likely you set this in /etc/ > make.conf > Unlikely seeing -Werror is the default for kernel builds and has been for a while. NO_WERROR is what turns it off. > -Mike > > >> -DHAVE_KERNEL_OPTION_HEADERS -include >> /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq >> -I@/../include -finline-limit=8000 -fno-common -g >> -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings >> -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >> -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -fformat-extensions -std=c99 -c >> /usr/src/sys/modules/mpt/../../dev/mpt/mpt_raid.c ld -d -warn- >> common -r -d >> -o mpt.kld mpt.o mpt_cam.o mpt_debug.o mpt_pci.o mpt_raid.o touch >> export_syms >> awk -f /usr/src/sys/modules/mpt/../../conf/kmod_syms.awk mpt.kld >> export_syms | xargs -J% objcopy % mpt.kld ld -Bshareable -d -warn- >> common >> -o mpt.ko.debug mpt.kld >> objcopy --only-keep-debug mpt.ko.debug mpt.ko.symbols >> objcopy --strip-debug --add-gnu-debuglink=mpt.ko.symbols mpt.ko.debug >> mpt.ko ===> mqueue (all) >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE - >> nostdinc -I- >> -DHAVE_KERNEL_OPTION_HEADERS -include >> /usr/obj/usr/src/sys/ROAM/opt_global.h -I. -I@ -I@/contrib/altq >> -I@/../include -finline-limit=8000 -fno-common -g >> -I/usr/obj/usr/src/sys/ROAM -mno-align-long-strings >> -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 >> -mno-sse3 -ffreestanding -Wall -Wredundant-decls -Wnested-externs >> -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline >> -Wcast-qual -fformat-extensions -std=c99 -c >> /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c >> /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c: In function >> `mq_open': /usr/src/sys/modules/mqueue/../../kern/uipc_mqueue.c:1832: >> warning: 'mq' might be used uninitialized in this function *** >> Error code 1 >> >> _______________________________________________ >> 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" > _______________________________________________ > 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" > --Apple-Mail-2-203426524-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:15: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 A89C416A420 for ; Sun, 27 Nov 2005 22:15:43 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FBAE43D79 for ; Sun, 27 Nov 2005 22:15:42 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EgUo9-000IHL-R9; Sun, 27 Nov 2005 22:15:42 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EgUo8-00076P-Lw; Sun, 27 Nov 2005 14:15:40 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17290.12300.152322.544851@roam.psg.com> Date: Sun, 27 Nov 2005 12:15:40 -1000 To: Sean Winn References: <17290.7435.851684.533219@roam.psg.com> <200511271258.23017.ringworm01@gmail.com> <7FEAFB8D-F487-43BD-9B9F-F97A6DAC9406@gothic.net.au> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:15:43 -0000 >> get rid of -Werror in you CFLAGS, likely you set this in /etc/ >> make.conf > Unlikely seeing -Werror is the default for kernel builds and has been > for a while. > > NO_WERROR is what turns it off. i have no desire to turn it off. what is needed it a fix to the checked in code. i'll promise to retry gnome builds without force_package_register if the code is fixed :-) randy From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:18: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 B55BA16A41F for ; Sun, 27 Nov 2005 22:18:19 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A6BD43D72 for ; Sun, 27 Nov 2005 22:17:57 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so749793nzo for ; Sun, 27 Nov 2005 14:17:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=An6EiZflEacRTH2ssEk/CjTHcfywfuHDq4j7MCwZtS1TLERzcKSFb40HZREX4Gcka+Jlc/S36stdO3B6UXkYjB/P6iXrTn1BHObxprn4ezm9gL7t3R7rkbcUwQnTs8IxFIkcnOj+NfORFSV4/YajqGP6XM3VlsmxubdkW2eWoa4= Received: by 10.36.215.21 with SMTP id n21mr2903145nzg; Sun, 27 Nov 2005 14:17:51 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id 38sm1806583nzk.2005.11.27.14.17.50; Sun, 27 Nov 2005 14:17:51 -0800 (PST) From: "Michael C. Shultz" To: Sean Winn Date: Sun, 27 Nov 2005 14:08:17 -0800 User-Agent: KMail/1.8.3 References: <17290.7435.851684.533219@roam.psg.com> <200511271258.23017.ringworm01@gmail.com> <7FEAFB8D-F487-43BD-9B9F-F97A6DAC9406@gothic.net.au> In-Reply-To: <7FEAFB8D-F487-43BD-9B9F-F97A6DAC9406@gothic.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511271408.17874.ringworm01@gmail.com> Cc: Randy Bush , freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:18:19 -0000 On Sunday 27 November 2005 14:10, Sean Winn wrote: > On 28/11/2005, at 7:58 AM, Michael C. Shultz wrote: > > On Sunday 27 November 2005 12:54, Randy Bush wrote: > >> cvsup at 20:39 > >> > >> cc -O -pipe -march=pentiumpro -Werror -D_KERNEL -DKLD_MODULE - > >> nostdinc -I- > > > > ^^^^^^^^^^^^^ > > > > get rid of -Werror in you CFLAGS, likely you set this in /etc/ > > make.conf > > Unlikely seeing -Werror is the default for kernel builds and has been > for a while. > > NO_WERROR is what turns it off. Thanks for the info -Mike From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:20: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 876EC16A41F for ; Sun, 27 Nov 2005 22:20:04 +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 2A90843D81 for ; Sun, 27 Nov 2005 22:19:43 +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 496C01A3C28; Sun, 27 Nov 2005 14:19:42 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id DC2C151527; Sun, 27 Nov 2005 17:19:40 -0500 (EST) Date: Sun, 27 Nov 2005 17:19:40 -0500 From: Kris Kennaway To: Randy Bush Message-ID: <20051127221940.GA5560@xor.obsecurity.org> References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> <200511271324.45398.ringworm01@gmail.com> <17290.11946.415967.173429@roam.psg.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7JfCtLOvnd9MIVvH" Content-Disposition: inline In-Reply-To: <17290.11946.415967.173429@roam.psg.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, "Michael C. Shultz" Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:20:04 -0000 --7JfCtLOvnd9MIVvH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 27, 2005 at 12:09:46PM -1000, Randy Bush wrote: > >>> FORCE_PKG_REGISTER=3DYES > > Here is something else you should fix while your hunting down that -Wer= ror=20 > > switch, Kris Kennway just posted good advice about why this is a dumb t= hing > > to do a week or two ago, you might want to search the mail archives and= look=20 > > it up. >=20 > he posted it in response to a msg from me, so i saw it for sure >=20 > problem is that gnome would not upgrade without it. Then you're still doing something wrong, but hey, it's your system to mess up any way you feel like :-) Kris --7JfCtLOvnd9MIVvH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDijD8Wry0BWjoQKURAoheAKCxUX1Ej2LShfSDlLhC+rz/CpLxkwCfceyI V1rPoL+HQQbvrsKOXa0y6EQ= =dkof -----END PGP SIGNATURE----- --7JfCtLOvnd9MIVvH-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:21: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 6257E16A41F for ; Sun, 27 Nov 2005 22:21:50 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B25E43D64 for ; Sun, 27 Nov 2005 22:21:45 +0000 (GMT) (envelope-from ringworm01@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so750259nzo for ; Sun, 27 Nov 2005 14:21:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:cc:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=geAGwHOEf4rVXpSaFV2Lq6hPzbHuE4feJQs3cUC0HU2Ylmkane8f5NwrM1gI9Py2T1FMDVpdjT95sAzuhPMcwaGzee5mHdTagZc09jSLn6tggaYiMANUAZM7pbCEtM5phly+g8vVkfDqjigCj5AWthSlAR/8xyMLw2m0esDoiXc= Received: by 10.36.18.9 with SMTP id 9mr2904651nzr; Sun, 27 Nov 2005 14:21:43 -0800 (PST) Received: from ?192.168.1.10? ( [71.102.14.129]) by mx.gmail.com with ESMTP id 7sm1638056nzn.2005.11.27.14.21.42; Sun, 27 Nov 2005 14:21:43 -0800 (PST) From: "Michael C. Shultz" To: Randy Bush Date: Sun, 27 Nov 2005 14:12:09 -0800 User-Agent: KMail/1.8.3 References: <17290.7435.851684.533219@roam.psg.com> <200511271324.45398.ringworm01@gmail.com> <17290.11946.415967.173429@roam.psg.com> In-Reply-To: <17290.11946.415967.173429@roam.psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511271412.10225.ringworm01@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:21:50 -0000 On Sunday 27 November 2005 14:09, Randy Bush wrote: > >>> FORCE_PKG_REGISTER=YES > > > > Here is something else you should fix while your hunting down that > > -Werror switch, Kris Kennway just posted good advice about why this is a > > dumb thing to do a week or two ago, you might want to search the mail > > archives and look it up. > > he posted it in response to a msg from me, so i saw it for sure > > problem is that gnome would not upgrade without it. > > randy It isn't a proper fix, my opinion is you should track down and fix the real reason why gnome wouldn't upgrade and get rid of this sooner rather than later. -Mike From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:22: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 912C116A424 for ; Sun, 27 Nov 2005 22:22:31 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id D4A8543D64 for ; Sun, 27 Nov 2005 22:22:23 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EgUua-000ISg-W4; Sun, 27 Nov 2005 22:22:21 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EgUuZ-0007EC-R4; Sun, 27 Nov 2005 14:22:19 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17290.12699.234034.327984@roam.psg.com> Date: Sun, 27 Nov 2005 12:22:19 -1000 To: Kris Kennaway References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> <200511271324.45398.ringworm01@gmail.com> <17290.11946.415967.173429@roam.psg.com> <20051127221940.GA5560@xor.obsecurity.org> Cc: freebsd-current@freebsd.org, "Michael C. Shultz" Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:22:31 -0000 >>>>> FORCE_PKG_REGISTER=YES >> problem is that gnome would not upgrade without it. > Then you're still doing something wrong, but hey, it's your system to > mess up any way you feel like :-) that is my one true talent. randy, having a go at gnome without it From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:37: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 7DDF416A41F for ; Sun, 27 Nov 2005 22:37:13 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from centrmmtao06.cox.net (centrmmtao06.cox.net [70.168.83.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id B716C43D62 for ; Sun, 27 Nov 2005 22:37:12 +0000 (GMT) (envelope-from mezz7@cox.net) Received: from mezz.mezzweb.com ([68.103.32.140]) by centrmmtao06.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051127223550.BZHY13557.centrmmtao06.cox.net@mezz.mezzweb.com>; Sun, 27 Nov 2005 17:35:50 -0500 Date: Sun, 27 Nov 2005 16:38:13 -0600 To: "Randy Bush" References: <17290.7435.851684.533219@roam.psg.com> <17290.8479.860308.161622@roam.psg.com> <200511271317.23209.ringworm01@gmail.com> <200511271324.45398.ringworm01@gmail.com> <17290.11946.415967.173429@roam.psg.com> 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: <17290.11946.415967.173429@roam.psg.com> User-Agent: Opera M2/8.51 (Linux, build 1462) Cc: freebsd-current@freebsd.org, "Michael C. Shultz" Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:37:13 -0000 On Sun, 27 Nov 2005 16:09:46 -0600, Randy Bush wrote: >>>> FORCE_PKG_REGISTER=YES >> Here is something else you should fix while your hunting down that >> -Werror >> switch, Kris Kennway just posted good advice about why this is a dumb >> thing >> to do a week or two ago, you might want to search the mail archives and >> look >> it up. > > he posted it in response to a msg from me, so i saw it for sure > > problem is that gnome would not upgrade without it. You are creating more problems than solve it. Cheers, Mezz > randy -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:49: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 4433816A422 for ; Sun, 27 Nov 2005 22:49:53 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from smtp.xtra-net.be (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 3B7B243D5C for ; Sun, 27 Nov 2005 22:49:49 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 1925 invoked from network); 27 Nov 2005 22:49:46 -0000 Received: from wbedllfs.xtra-net.org (HELO wbedllfs.xtra-net.be) (192.168.1.21) by 0 with SMTP; 27 Nov 2005 22:49:46 -0000 From: Vincent Blondel To: current@freebsd.org In-Reply-To: <200511271554.47717.nb_root@videotron.ca> References: <1133088397.1126.11.camel@wbedllfs.xtra-net.org> <438A1B09.4030707@gmail.com> <200511271554.47717.nb_root@videotron.ca> Content-Type: text/plain Date: Sun, 27 Nov 2005 23:49:43 +0100 Message-Id: <1133131783.1021.3.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 22:49:53 -0000 On Sun, 2005-11-27 at 15:54 -0500, Nicolas Blais wrote: > On November 27, 2005 03:46 pm, Rainer Alves wrote: > > Vincent Blondel wrote: > > >Hello all, > > > > > >I am trying to use dvd::rip but I encounter some problems and get this > > >error message > > > > > > ... > > > tcprobe output was: > > > > > > [tcprobe] OSS audio device > > > No support for oss compiled in > > > [tcprobe] summary for /dev/acd0, (*) = not default, 0 = not detected > > > no audio track: use "null" import module for audio > > > DVDRIP_SUCCESS > > > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm > > >line 137 > > > > > >Has somebody any experience with dvd::rip with FreeBSD ?? > > >Thanks to help me. > > > > > >Regards > > > > I've had the same issue here... instead of trying to read the TOC and > > ripping the DVD directly from /dev/acd0, first mount the DVD under > > /cdrom, then go to the preferences panel and change both "DVD device" > > and "DVD mount point" to /cdrom. This should solve your problem. > > > > -- > > Rainer Alves > > > > Actually, that error message is caused by transcode not using the oss_module. > A recent commit to the transcode port fixes that issue (transcode-1.0.1_1). > > Nicolas. I updated transcode to the last version (transcode-1.0.1_1) but now I get another error message when I tcprobe my device wbedllfs # tcprobe -H 10 -i /dev/acd0 [tcprobe] OSS audio device SNDCTL_DSP_SETFMT: Inappropriate ioctl for device [tcprobe] failed to probe source From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 22:55: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 C289316A420 for ; Sun, 27 Nov 2005 22:55:15 +0000 (GMT) (envelope-from cianlists@cian.ws) Received: from oppy.cian.ws (cian.ws [62.231.45.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA43F43D5E for ; Sun, 27 Nov 2005 22:55:08 +0000 (GMT) (envelope-from cianlists@cian.ws) Received: from localhost (localhost.cian.ws [127.0.0.1]) by oppy.cian.ws (Postfix) with ESMTP id F2EE133C57 for ; Sun, 27 Nov 2005 22:55:05 +0000 (GMT) Received: from oppy.cian.ws ([127.0.0.1]) by localhost (oppy.cian.ws [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 49176-03 for ; Sun, 27 Nov 2005 22:55:04 +0000 (GMT) Received: from [10.0.1.5] (g5.cian.ws [10.0.1.5]) by oppy.cian.ws (Postfix) with ESMTP id 6BAA033C48 for ; Sun, 27 Nov 2005 22:55:04 +0000 (GMT) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: Cian Hughes Date: Sun, 27 Nov 2005 22:55:02 +0000 X-Pgp-Agent: GPGMail 1.1.1 (Tiger) X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at cian.ws Subject: 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: Sun, 27 Nov 2005 22:55:15 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey, I'm in no rush on this one, but I'm planning on building a new Athlon AMD64 machine, It's primarily as a voip server and file storage box for home use and will have 8 SATA (possibly SATA-II) drives attached to a RAID 5 card, probably Highpoint (but i'm open on this). I am wondering, what have people on this list built recently, within these bounds, I'm looking to choose a motherboard with one or two 1000Base-T Ethernet ports (to keep PCI's free for other things, ISDN card, TV Tuner, etc...), if possible what has and hasn't worked, i'm not too worried about onboard HD controllers, etc. Basically, before I buy I want to avoid any mistakes that people have already hit, I know there is a supported hardware list, but is their an advised hardware list for FreeBSD, especially with regard to RAID Cards and Motherboards. Thanks for your help, Cian Hughes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDijlHaVVfOlCF0TQRAmt5AJ91t0eqg7sH1hECCvQ9JbHN03VlnQCeNJi3 NE74VX0k7Z1HGa/+MCtk+lA= =i8Hd -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 23:09: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 A9CE616A438 for ; Sun, 27 Nov 2005 23:09:27 +0000 (GMT) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E49543D45 for ; Sun, 27 Nov 2005 23:09:18 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Sun, 27 Nov 2005 15:09:14 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 493DA5D04; Sun, 27 Nov 2005 15:09:14 -0800 (PST) To: Vincent Blondel In-reply-to: Your message of "Sun, 27 Nov 2005 23:49:43 +0100." <1133131783.1021.3.camel@wbedllfs.xtra-net.org> Date: Sun, 27 Nov 2005 15:09:14 -0800 From: "Kevin Oberman" Message-Id: <20051127230914.493DA5D04@ptavv.es.net> Cc: current@freebsd.org Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 23:09:27 -0000 > From: Vincent Blondel > Date: Sun, 27 Nov 2005 23:49:43 +0100 > Sender: owner-freebsd-current@freebsd.org > > On Sun, 2005-11-27 at 15:54 -0500, Nicolas Blais wrote: > > On November 27, 2005 03:46 pm, Rainer Alves wrote: > > > Vincent Blondel wrote: > > > >Hello all, > > > > > > > >I am trying to use dvd::rip but I encounter some problems and get this > > > >error message > > > > > > > > ... > > > > tcprobe output was: > > > > > > > > [tcprobe] OSS audio device > > > > No support for oss compiled in > > > > [tcprobe] summary for /dev/acd0, (*) = not default, 0 = not detected > > > > no audio track: use "null" import module for audio > > > > DVDRIP_SUCCESS > > > > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm > > > >line 137 > > > > > > > >Has somebody any experience with dvd::rip with FreeBSD ?? > > > >Thanks to help me. > > > > > > > >Regards > > > > > > I've had the same issue here... instead of trying to read the TOC and > > > ripping the DVD directly from /dev/acd0, first mount the DVD under > > > /cdrom, then go to the preferences panel and change both "DVD device" > > > and "DVD mount point" to /cdrom. This should solve your problem. > > > > > > -- > > > Rainer Alves > > > > > > > Actually, that error message is caused by transcode not using the oss_module. > > A recent commit to the transcode port fixes that issue (transcode-1.0.1_1). > > > > Nicolas. > > I updated transcode to the last version (transcode-1.0.1_1) but now I > get another error message when I tcprobe my device > > wbedllfs # tcprobe -H 10 -i /dev/acd0 > [tcprobe] OSS audio device > SNDCTL_DSP_SETFMT: Inappropriate ioctl for device > [tcprobe] failed to probe source What do you have configured in dvd::rip as the "DVD device" and "DVD mount point"? While it seems wrong, to get it to work I ended up pointing both to the mount point I use for ripping (~/dvd). If you are mounting it on /cdrom, than try just putting that in both fields and see if it works. -- R. Kevin Oberman, Network Engineer E-mail: oberman@es.net From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 23:29: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 2B16B16A422 for ; Sun, 27 Nov 2005 23:29:00 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: from smtp.xtra-net.be (cable-195-162-200-89.customer.tvd.be [195.162.200.89]) by mx1.FreeBSD.org (Postfix) with SMTP id 5750943D68 for ; Sun, 27 Nov 2005 23:28:39 +0000 (GMT) (envelope-from vincent@xtra-net.org) Received: (qmail 2206 invoked from network); 27 Nov 2005 23:28:10 -0000 Received: from wbedllfs.xtra-net.org (HELO wbedllfs.xtra-net.be) (192.168.1.21) by 0 with SMTP; 27 Nov 2005 23:28:10 -0000 From: Vincent Blondel To: current@freebsd.org In-Reply-To: <20051127230914.493DA5D04@ptavv.es.net> References: <20051127230914.493DA5D04@ptavv.es.net> Content-Type: text/plain Date: Mon, 28 Nov 2005 00:28:07 +0100 Message-Id: <1133134087.13379.2.camel@wbedllfs.xtra-net.org> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: Subject: Re: dvd::rip - table of contents problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 27 Nov 2005 23:29:00 -0000 On Sun, 2005-11-27 at 15:09 -0800, Kevin Oberman wrote: > > From: Vincent Blondel > > Date: Sun, 27 Nov 2005 23:49:43 +0100 > > Sender: owner-freebsd-current@freebsd.org > > > > On Sun, 2005-11-27 at 15:54 -0500, Nicolas Blais wrote: > > > On November 27, 2005 03:46 pm, Rainer Alves wrote: > > > > Vincent Blondel wrote: > > > > >Hello all, > > > > > > > > > >I am trying to use dvd::rip but I encounter some problems and get this > > > > >error message > > > > > > > > > > ... > > > > > tcprobe output was: > > > > > > > > > > [tcprobe] OSS audio device > > > > > No support for oss compiled in > > > > > [tcprobe] summary for /dev/acd0, (*) = not default, 0 = not detected > > > > > no audio track: use "null" import module for audio > > > > > DVDRIP_SUCCESS > > > > > at /usr/local/lib/perl5/site_perl/5.8.7/Video/DVDRip/GUI/Pipe.pm > > > > >line 137 > > > > > > > > > >Has somebody any experience with dvd::rip with FreeBSD ?? > > > > >Thanks to help me. > > > > > > > > > >Regards > > > > > > > > I've had the same issue here... instead of trying to read the TOC and > > > > ripping the DVD directly from /dev/acd0, first mount the DVD under > > > > /cdrom, then go to the preferences panel and change both "DVD device" > > > > and "DVD mount point" to /cdrom. This should solve your problem. > > > > > > > > -- > > > > Rainer Alves > > > > > > > > > > Actually, that error message is caused by transcode not using the oss_module. > > > A recent commit to the transcode port fixes that issue (transcode-1.0.1_1). > > > > > > Nicolas. > > > > I updated transcode to the last version (transcode-1.0.1_1) but now I > > get another error message when I tcprobe my device > > > > wbedllfs # tcprobe -H 10 -i /dev/acd0 > > [tcprobe] OSS audio device > > SNDCTL_DSP_SETFMT: Inappropriate ioctl for device > > [tcprobe] failed to probe source > > What do you have configured in dvd::rip as the "DVD device" and "DVD > mount point"? > > While it seems wrong, to get it to work I ended up pointing both to the > mount point I use for ripping (~/dvd). If you are mounting it on /cdrom, > than try just putting that in both fields and see if it works. Ok, upgrading to the last version of transcode is not enough, we also have to mount the dvd ( strange behaviour ??? ). Now it is working :) Thanks a lot From owner-freebsd-current@FreeBSD.ORG Sun Nov 27 23:42:25 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from [127.0.0.1] (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C9C116A41F; Sun, 27 Nov 2005 23:42:23 +0000 (GMT) (envelope-from davidxu@freebsd.org) Message-ID: <438A445F.8070005@freebsd.org> Date: Mon, 28 Nov 2005 07:42:23 +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: Cian Hughes References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> In-Reply-To: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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: Sun, 27 Nov 2005 23:42:25 -0000 Cian Hughes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey, I'm in no rush on this one, but I'm planning on building a new > Athlon AMD64 machine, It's primarily as a voip server and file > storage box for home use and will have 8 SATA (possibly SATA-II) > drives attached to a RAID 5 card, probably Highpoint (but i'm open on > this). The nve driver(NVidia network adapter) does not work, take care this. David Xu From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 00: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 3085316A41F for ; Mon, 28 Nov 2005 00:39:12 +0000 (GMT) (envelope-from ebm-freebsd-current@swervinghead.com) Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99C2A43D5D for ; Mon, 28 Nov 2005 00:39:11 +0000 (GMT) (envelope-from ebm-freebsd-current@swervinghead.com) Received: from remote.swervinghead.com (swervinghead.com[24.17.196.146]) by comcast.net (sccrmhc11) with SMTP id <200511280033250110008ivve>; Mon, 28 Nov 2005 00:33:34 +0000 Received: (qmail 49818 invoked from network); 28 Nov 2005 00:33:05 -0000 Received: from unknown (HELO ?192.168.1.102?) (192.168.1.102) by remote.swervinghead.com with SMTP; 28 Nov 2005 00:33:05 -0000 Message-ID: <438A504F.7060702@swervinghead.com> Date: Sun, 27 Nov 2005 16:33:19 -0800 From: ebm User-Agent: Mozilla Thunderbird 1.0.7-1.4.1.centos4 (X11/20051007) 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: Freebsd 5.3 screw up.... deleted /lib/libc.so.5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 00:39:12 -0000 After I deleted this very valuable file I realized what I did. Since I don't have a old boot disk laying around is my only option to upgrade to a newer version of freebsd? From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 02:55:17 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 4D08716A41F for ; Mon, 28 Nov 2005 02:55:17 +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 9197E43D55 for ; Mon, 28 Nov 2005 02:55:16 +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 jAS2tABU017257; Mon, 28 Nov 2005 03:55:10 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jAS2tAis017256; Sun, 27 Nov 2005 21:55:10 -0500 (EST) (envelope-from cracauer) Date: Sun, 27 Nov 2005 21:55:10 -0500 From: Martin Cracauer To: Cian Hughes Message-ID: <20051127215510.A17131@cons.org> References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws>; from cianlists@cian.ws on Sun, Nov 27, 2005 at 10:55:02PM +0000 Cc: 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: Mon, 28 Nov 2005 02:55:17 -0000 Cian Hughes wrote on Sun, Nov 27, 2005 at 10:55:02PM +0000: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey, I'm in no rush on this one, but I'm planning on building a new > Athlon AMD64 machine, It's primarily as a voip server and file > storage box for home use and will have 8 SATA (possibly SATA-II) > drives attached to a RAID 5 card, probably Highpoint (but i'm open on > this). > > I am wondering, what have people on this list built recently, within > these bounds, I'm looking to choose a motherboard with one or two > 1000Base-T Ethernet ports (to keep PCI's free for other things, ISDN > card, TV Tuner, etc...), if possible what has and hasn't worked, i'm > not too worried about onboard HD controllers, etc. I have a DFI SLI-DRI which is NForce 4 based and I am overall amazed how well it works. In particular the SATA controller (only tested the first 4 ports). As noted, right now the NVidia port doesn't work, and in Linux the Broadcom port doesn't work, so right now there's no way around a PCI slot. Temperature monitoring doesn't work in FreeBSD but does work in Linux so there's hope. Here are my software RAID results: http://cracauer-forum.cons.org/forum/viewtopic.php?t=29 The other recent 939 board I have is a Asus A8V-E SE (note SE, otherwise it won't do dual-core) which is nice but underpowered. The GbE also doesn't work in FreeBSD (some other broadcom junk than on the SLI-DR). Having said all that, the Asus does ECC memory and the DFI does not, so DFI is out for my choices for important machines. What does work perfectly is my K8V-X, every device including temperature monitoring, but it is socket 754. Let me know if you have further questions. 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 Mon Nov 28 03:01:33 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 961B216A420 for ; Mon, 28 Nov 2005 03:01:33 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from ant.bwct.de (ant.bwct.de [85.159.14.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CE7643D49 for ; Mon, 28 Nov 2005 03:01:31 +0000 (GMT) (envelope-from ticso@cicely12.cicely.de) Received: from cicely5.cicely.de ([10.1.1.7]) by ant.bwct.de (8.12.11/8.12.11) with ESMTP id jAS31Rhq021717; Mon, 28 Nov 2005 04:01:27 +0100 (CET) Received: from cicely12.cicely.de (cicely12.cicely.de [10.1.1.14]) by cicely5.cicely.de (8.13.4/8.13.4) with ESMTP id jAS31L1R082581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 04:01:22 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: from cicely12.cicely.de (localhost [127.0.0.1]) by cicely12.cicely.de (8.13.4/8.13.3) with ESMTP id jAS31LHs034786; Mon, 28 Nov 2005 04:01:21 +0100 (CET) (envelope-from ticso@cicely12.cicely.de) Received: (from ticso@localhost) by cicely12.cicely.de (8.13.4/8.13.3/Submit) id jAS31KX2034785; Mon, 28 Nov 2005 04:01:20 +0100 (CET) (envelope-from ticso) Date: Mon, 28 Nov 2005 04:01:20 +0100 From: Bernd Walter To: ebm Message-ID: <20051128030119.GD32065@cicely12.cicely.de> References: <438A504F.7060702@swervinghead.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <438A504F.7060702@swervinghead.com> X-Operating-System: FreeBSD cicely12.cicely.de 5.4-STABLE alpha User-Agent: Mutt/1.5.9i X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.4 X-Spam-Report: * -3.3 ALL_TRUSTED Did not pass through any untrusted hosts * -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% * [score: 0.0000] X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on cicely12.cicely.de Cc: freebsd-current@freebsd.org Subject: Re: Freebsd 5.3 screw up.... deleted /lib/libc.so.5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Nov 2005 03:01:33 -0000 On Sun, Nov 27, 2005 at 04:33:19PM -0800, ebm wrote: > After I deleted this very valuable file I realized what I did. Since I > don't have a old boot disk laying around is my only option to upgrade to > a newer version of freebsd? Use /rescue/sh as shell and the other tools from /rescue to restore the missing lib file. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 03:04:29 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 420AE16A41F for ; Mon, 28 Nov 2005 03:04:29 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA98C43D5E for ; Mon, 28 Nov 2005 03:04:28 +0000 (GMT) (envelope-from caiquanqing@gmail.com) Received: by xproxy.gmail.com with SMTP id t12so865044wxc for ; Sun, 27 Nov 2005 19:04:27 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=N44XwGOuTW5J6UI+i9+Ljl3WqkPYiGYe2nlJDerqAD4Qd5RINWdnemCzspXELLXxY1VrDq/Yr4jD6iqOGP1qYqIDCZ6/NPW2c5L2hfV4f1MJ957Cx0LE+zyQ3XXifMvBawUV0TirGLTgLD4tz7qAyZsPsG4QCBkRH3t0NdXB5LI= Received: by 10.70.46.13 with SMTP id t13mr749336wxt; Sun, 27 Nov 2005 19:04:27 -0800 (PST) Received: by 10.70.12.10 with HTTP; Sun, 27 Nov 2005 19:04:27 -0800 (PST) Message-ID: <2b22951e0511271904v5ad80delc6cd8b944b3e9e16@mail.gmail.com> Date: Sun, 27 Nov 2005 19:04:27 -0800 From: "Cai, Quanqing" To: Eric Anholt In-Reply-To: <1132903752.1197.95.camel@leguin> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1132743283.1197.55.camel@leguin> <1132780093.1197.60.camel@leguin> <2b22951e0511241259y513b74c3x9a81ad2ff7e47c36@mail.gmail.com> <1132903752.1197.95.camel@leguin> Cc: current@freebsd.org 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, 28 Nov 2005 03:04:29 -0000 Thanks. I build xorg-server, mesa and dri-devel userland from cvs.freedesktop.org, everything works OK. glxinfo reports: direct rendering: Yes. BR Cai, Quanqing On 11/24/05, Eric Anholt wrote: > On Thu, 2005-11-24 at 12:59 -0800, Cai, Quanqing wrote: > > I have an on-board video chip: > > pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x5333 device 0x8d04 > > S3 Inc. VT8375 [ProSavage8 KM266/KL266] > > > > The kernel driver is OK, and I can kldload it or compile it into > > kernel. dmesg shows: > > drm0: mem > > 0xed000000-0xed07ffff,0xe0000000-0xe7ffffff at device 0.0 on pci1 > > info: [drm] AGP at 0xe8000000 64MB > > info: [drm] Initialized savage 2.4.1 20050313 > > > > But there is no DRI in Xorg, here is glxinfo: > > name of display: :0.0 > > display: :0 screen: 0 > > direct rendering: No > > New DRM drivers aren't enough -- you need new userland. That means > xorg-server-snap and dri-devel. If that's not enough, > http://dri.freedesktop.org/wiki/DriTroubleshooting > > -- > Eric Anholt eta@lclark.edu > http://people.freebsd.org/~anholt/ anholt@FreeBSD.org > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.2 (FreeBSD) > > iD8DBQBDhr1IHUdvYGzw6vcRAkcqAKCNhRg2Nv0CXz8d4opk46+O4VwZLwCfZ9bA > tXKGQyXksyJaNUbHYb8SPQM=3D > =3D71Oi > -----END PGP SIGNATURE----- > > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 05:23: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 5E1F816A41F; Mon, 28 Nov 2005 05:23:04 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from its-mu-mail3.its.rmit.edu.au (its-mu-mail3.its.rmit.edu.au [131.170.1.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE95D43D49; Mon, 28 Nov 2005 05:22:44 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by its-mu-mail3.its.rmit.edu.au (8.13.1/8.12.11/mail3) with ESMTP id jAS5MeAN012000; Mon, 28 Nov 2005 16:22:40 +1100 (EST) Received: from goanna.cs.rmit.edu.au (goanna.cs.rmit.edu.au [131.170.24.40]) by wombat.cs.rmit.edu.au (8.12.10/8.12.10/cshub) with ESMTP id jAS5Mefj021028; Mon, 28 Nov 2005 16:22:40 +1100 (EST) Received: (from emil@localhost) by goanna.cs.rmit.edu.au (8.11.3/8.9.3/csnode) id jAS5MdQ14430; Mon, 28 Nov 2005 16:22:39 +1100 (EST) Date: Mon, 28 Nov 2005 16:22:39 +1100 From: Emil Mikulic To: Gleb Smirnoff Message-ID: <20051128052238.GH6610@cs.rmit.edu.au> References: <20051125022040.GA9150@cs.rmit.edu.au> <20051125132228.GN25711@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051125132228.GN25711@cell.sick.ru> X-Operating-System: SunOS 5.9 X-PGP-Fingerprint: D2B4 7C14 0C41 9AE5 8D2B 16B0 D3D6 F910 8E4C 5D35 X-Authentication-Warning: localhost: emil pwned teh intarweb User-Agent: Mutt/1.5.9i X-Scanned-By: MIMEDefang 2.44 Cc: freebsd-current@FreeBSD.org Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 05:23:04 -0000 On Fri, Nov 25, 2005 at 04:22:28PM +0300, Gleb Smirnoff wrote: > On Fri, Nov 25, 2005 at 01:20:41PM +1100, Emil Mikulic wrote: > E> The other problem is that bge will never negotiate a working link speed. > E> ifconfig will always return "status: no carrier" > E> > E> If I force the media to 10baseT/UTP or 100baseTX (either mediaopt > E> full-duplex or not), it will issue a couple more MII_TICKs then stop, > E> ifconfig will return "status: active", there will be no more stalls, > E> and, most importantly, the network connection will actually work. > > Please try out the attached patch. No effect. It still can't autoselect a working media, and I still get loops in miibus. miibus0: looped 4013 miibus0: looped 0 miibus0: looped 4570 miibus0: looped 0 miibus0: looped 3952 miibus0: looped 0 miibus0: looped 3921 miibus0: looped 0 miibus0: looped 3007 miibus0: looped 0 miibus0: looped 0 miibus0: looped 4141 miibus0: looped 0 miibus0: looped 4114 miibus0: looped 0 miibus0: looped 4082 miibus0: looped 0 miibus0: looped 3464 miibus0: looped 0 miibus0: looped 0 miibus0: looped 3714 miibus0: looped 0 miibus0: looped 4270 miibus0: looped 0 Anything else I can try? --Emil From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 06:01: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 468C116A41F for ; Mon, 28 Nov 2005 06:01:15 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: from turing.cs.hmc.edu (turing.cs.hmc.edu [134.173.42.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52BE243D46 for ; Mon, 28 Nov 2005 06:01:14 +0000 (GMT) (envelope-from nge@cs.hmc.edu) Received: by turing.cs.hmc.edu (Postfix, from userid 26983) id EABFF53207; Sun, 27 Nov 2005 22:01:13 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by turing.cs.hmc.edu (Postfix) with ESMTP id D51975A8DE; Sun, 27 Nov 2005 22:01:13 -0800 (PST) Date: Sun, 27 Nov 2005 22:01:13 -0800 (PST) From: Nate Eldredge X-X-Sender: nate@turing To: Cian Hughes In-Reply-To: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> Message-ID: References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: 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: Mon, 28 Nov 2005 06:01:15 -0000 On Sun, 27 Nov 2005, Cian Hughes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hey, I'm in no rush on this one, but I'm planning on building a new Athlon > AMD64 machine, It's primarily as a voip server and file storage box for home > use and will have 8 SATA (possibly SATA-II) drives attached to a RAID 5 card, > probably Highpoint (but i'm open on this). > > I am wondering, what have people on this list built recently, within these > bounds, I'm looking to choose a motherboard with one or two 1000Base-T > Ethernet ports (to keep PCI's free for other things, ISDN card, TV Tuner, > etc...), if possible what has and hasn't worked, i'm not too worried about > onboard HD controllers, etc. > > Basically, before I buy I want to avoid any mistakes that people have already > hit, I know there is a supported hardware list, but is their an advised > hardware list for FreeBSD, especially with regard to RAID Cards and > Motherboards. Hi Cian, I put together a machine a couple months ago. I used a Tyan S2875ANRF ("Tiger K8W") dual-Opteron motherboard and a single Opteron 244 (1.8 GHz) cpu (second one may come in the future). I am running 5.4 and have been very happy with it. I decided it was worth going for Opteron over Athlon 64. They seem to have better performance (wider memory bus, etc), obviously SMP ability, and as I understand it the regular Athlon 64s don't support ECC memory which I insist upon. The Athlon 64FX appear to be similar to the fastest Opterons and differ mainly for price marketing purposes (sold to gamers). I had a disk-related panic/crash once, I cannot remember the details. It never recurred. The board has a SiI 3114 SATA controller, and I believe support for SiI is not perfect, so that may be the cause; or the dirt-cheap disk. If you are going to use your own controller then this probably has nothing to do with you. I don't know anything about RAID hardware, sorry. It has an onboard 1000BaseT port with em controller. This works perfectly, though I only use it at 100Mb since I don't have a gigabit switch. There are 5 pci slots and 1 agp. No vga on board. I threw in an old junk pci vga card because I only use it for text (no X on the box, it's mostly headless). It also has serial ports which could be useful for headless operation. Supposedly the BIOS setup also supports a serial console. Sound, USB and Firewire are on board. I have not tried them. It doesn't support dual-core opteron, if that's something you wanted. The only other thing that didn't work immediately is the cpu temperature sensor (Winbond W83627HF). There is a hardware bit you have to twiddle to enable it, which mbmon doesn't do. I wrote my own utility to read the sensor after reading the datasheet, which of course you are welcome to if you wind up with this board. So I would recommend this board/cpu based on my experience so far. It's a good value for the money. I hope this is of some value to you. Let me know if you want to know any more. -- Nate Eldredge nge@cs.hmc.edu From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 09:17:58 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.org Received: by hub.freebsd.org (Postfix, from userid 618) id BD80316A424; Mon, 28 Nov 2005 09:17:58 +0000 (GMT) In-Reply-To: <20051128052238.GH6610@cs.rmit.edu.au> from Emil Mikulic at "Nov 28, 2005 04:22:39 pm" To: emil@cs.rmit.edu.au (Emil Mikulic) Date: Mon, 28 Nov 2005 09:17:58 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051128091758.BD80316A424@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@FreeBSD.org, glebius@FreeBSD.org Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 09:17:58 -0000 > On Fri, Nov 25, 2005 at 04:22:28PM +0300, Gleb Smirnoff wrote: > > On Fri, Nov 25, 2005 at 01:20:41PM +1100, Emil Mikulic wrote: > > E> The other problem is that bge will never negotiate a working link speed. > > E> ifconfig will always return "status: no carrier" > > E> > > E> If I force the media to 10baseT/UTP or 100baseTX (either mediaopt > > E> full-duplex or not), it will issue a couple more MII_TICKs then stop, > > E> ifconfig will return "status: active", there will be no more stalls, > > E> and, most importantly, the network connection will actually work. > > > > Please try out the attached patch. > > No effect. In your original e-mail, you write: > I have a network port with bad wiring in the walls - a cable tester > shows only wires 1,2,3 and 6 are actually connected. Actually, this is not 'bad' wiring. It's correct for 10/100 ethernet as long as a) the cabling is actually cat5, and not moldy old cat3 or something, and b) the four wires are actually connected in the right sequence. Pins 1 and 2 form one pair, and pins 3 and 6 form the second pair. A typical installation may have the orange/orange+white pair on pins 1 and 2, and the blue/blue+white pair on 3 and 6. And both sides must match. If it's not done this way, then while you may have a DC path between all 4 pins on each side, you won't be getting the proper noise cancellation effect of twisted pair cabling. This can cause signal distortion, dropped packets, and possibly botched autoneg. You didn't say if you checked for this though, so we can't speculate if this is really the problem. If the pairs are wrong, then that could be why autoneg is failing. It's also the least of your worries, since even if you could convince the software to establish a link, you might end up with rotten performance. A couple things you neglected to mention (and which Gleb failed to ask you about): - Exactly what kind of switch is on the other end of this wiring? - Is the port that corresponds to this wall jack a gigabit ethernet port, or just 10/100? If it is a gigE port, then you're being silly. 4 pairs are required for gigE. Period. The NWAY autonegotiation exchange can take place over just 2 pairs, but the gigE signalling scheme requires all 4 pairs to be present in order to establish a link. If there's just two pairs connected, both sides will can announce that they support gigabit speeds, and both sides will try configuring themselves for gigE operation, but no link will ever be established. If you manually override the autonegotiation in this case, you should do "ifconfig bge0 media 100baseTX" only. Do not specify full duplex. This won't work. When you manually select the mode, autoneg will be turned off, and the other side will rely on parallel detection to select the appropriate link speed, but it won't be able to sense if the link partner is in full or half duplex mode, so it will default to half. If you manually specify full, this will create a duplex mismatch, and you'll get rotten throughput. If the switch port is 10/100 and not gigE, then autoneg should be working properly, and I don't know why it isn't. As an aside, I really don't understand the purpose of the brgphy_loop() function. (I didn't write it.) It looks like it tries to put the PHY into loopback mode, and then waits for the PHY to report that there's a good link. I'm not really sure of the point here. I mean, you can do that, but I don't understand why. Also, the DELAY(10) here can probably be replaced with a tsleep() or something, which will allow the CPU to do other work while waiting for the PHY instead of hard busywaiting and blocking up the whole system (allowing a reschedule here should not hurt). > It still can't autoselect a working media, and I still get loops in > miibus. [...] > Anything else I can try? > > --Emil If the switch port really is 10/100, then maybe, just maybe, you can try increasing the autoneg timeout. In brgphy_service(), you'll see this: /* * Only retry autonegotiation every 5 seconds. */ if (++sc->mii_ticks <= 5) break; Change the 5 to a 10 and see if that helps. But if you really are trying to autoneg a link with a gigE switch port, this won't make any difference. If the switch is managed, and you have the password to it, you can try programming it to only announce 10/100 support on that port until such time as you can recable the place for gigE. Alternatively, you can attempt to steal two pairs from a neighboring cable that leads to the same jack. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 10:07: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 36CF616A41F; Mon, 28 Nov 2005 10:07:36 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from its-mu-mail3.its.rmit.edu.au (its-mu-mail3.its.rmit.edu.au [131.170.1.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BA2C43D62; Mon, 28 Nov 2005 10:07:35 +0000 (GMT) (envelope-from emil@cs.rmit.edu.au) Received: from wombat.cs.rmit.edu.au (wombat.cs.rmit.edu.au [131.170.24.41]) by its-mu-mail3.its.rmit.edu.au (8.13.1/8.12.11/mail3) with ESMTP id jASA7WoA013632; Mon, 28 Nov 2005 21:07:32 +1100 (EST) Received: from goanna.cs.rmit.edu.au (goanna.cs.rmit.edu.au [131.170.24.40]) by wombat.cs.rmit.edu.au (8.12.10/8.12.10/cshub) with ESMTP id jASA7Wfj018359; Mon, 28 Nov 2005 21:07:32 +1100 (EST) Received: (from emil@localhost) by goanna.cs.rmit.edu.au (8.11.3/8.9.3/csnode) id jASA7WT20012; Mon, 28 Nov 2005 21:07:32 +1100 (EST) Date: Mon, 28 Nov 2005 21:07:32 +1100 From: Emil Mikulic To: Bill Paul Message-ID: <20051128100731.GA9802@cs.rmit.edu.au> References: <20051128052238.GH6610@cs.rmit.edu.au> <20051128091758.BD80316A424@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051128091758.BD80316A424@hub.freebsd.org> X-Operating-System: SunOS 5.9 X-PGP-Fingerprint: D2B4 7C14 0C41 9AE5 8D2B 16B0 D3D6 F910 8E4C 5D35 X-Authentication-Warning: localhost: emil pwned teh intarweb User-Agent: Mutt/1.5.9i X-Scanned-By: MIMEDefang 2.44 Cc: freebsd-current@FreeBSD.ORG, glebius@FreeBSD.ORG Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 10:07:36 -0000 On Mon, Nov 28, 2005 at 09:17:58AM +0000, Bill Paul wrote: > > On Fri, Nov 25, 2005 at 04:22:28PM +0300, Gleb Smirnoff wrote: > > > On Fri, Nov 25, 2005 at 01:20:41PM +1100, Emil Mikulic wrote: > In your original e-mail, you write: > > > I have a network port with bad wiring in the walls - a cable tester > > shows only wires 1,2,3 and 6 are actually connected. > > Actually, this is not 'bad' wiring. It's correct for 10/100 ethernet That was probably the thinking when the office got wired up initially. > as long as a) the cabling is actually cat5, and not moldy old cat3 > or something, and b) the four wires are actually connected in the right > sequence. Pins 1 and 2 form one pair, and pins 3 and 6 form the second > pair. A typical installation may have the orange/orange+white pair > on pins 1 and 2, and the blue/blue+white pair on 3 and 6. And both > sides must match. If it's not done this way, then while you may have > a DC path between all 4 pins on each side, you won't be getting the > proper noise cancellation effect of twisted pair cabling. This can > cause signal distortion, dropped packets, and possibly botched autoneg. > > You didn't say if you checked for this though, so we can't speculate > if this is really the problem. I can't see what's in the walls but I attached the two parts of the cable tester to both ends of the line and 1-2-3-6 on one end was 1-2-3-6 on the other end. > A couple things you neglected to mention (and which Gleb failed to > ask you about): (yeah, sorry about that. I spent like an hour with the original message in a text editor then after I sent it I kept remembering things I'd forgotten) > - Exactly what kind of switch is on the other end of this wiring? The switch is managed, and does gigabit. It's a Nortel but I don't know the exact model off by heart (I can look it up tomorrow if it matters) > - Is the port that corresponds to this wall jack a gigabit ethernet > port, or just 10/100? All the wiring in the walls is, as you said, for 100Mbit. The switch and my network card are gigabit. > If it is a gigE port, then you're being silly. Yeah, I thought so. =( > 4 pairs are required for gigE. Period. The NWAY autonegotiation > exchange can take place over just 2 pairs, but the gigE signalling > scheme requires all 4 pairs to be present in order to establish a > link. If there's just two pairs connected, both sides will can > announce that they support gigabit speeds, and both sides will try > configuring themselves for gigE operation, but no link will ever be > established. I understand that gigabit will never work over the current wiring. I've accepted that and moved on. =) But are you saying the autonegotiation will never work over the current wiring either? As in, it can't try a slower link speed? > If you manually override the autonegotiation in this case, you should > do "ifconfig bge0 media 100baseTX" only. Do not specify full duplex. > This won't work. > > [...] > > If you manually specify full, this will create a duplex mismatch, and > you'll get rotten throughput. 10baseT/UTP and 100baseTX worked in both half-duplex and full-duplex but I didn't check throughput... Important bit: > Also, the DELAY(10) here can probably be replaced with a tsleep() or > something, which will allow the CPU to do other work while waiting for > the PHY instead of hard busywaiting and blocking up the whole system > (allowing a reschedule here should not hurt). This would be cool! I realise that I am doing stupid things with broken wiring and that it won't work, but if the "periodic lockup" problem could be fixed, that would be an improvement to the bge(4) driver, IMO. When I first noticed this symptom, it took quite a while to go from "FreeBSD is doing this annoying lockup thing every few seconds and I keep losing keypresses" to "oh, it's the network card / cabling / driver" > If the switch is managed, and you have the password to it, you can try > programming it to only announce 10/100 support on that port until such > time as you can recable the place for gigE. As I wrote in the original message, I'm currently connecting the machine directly to the switch (fortunately it's right above my desk). And the place -is- going to get re-cabled sometime soon, which is cool. It's just that I was in a situation where I could reproduce a problem I had some time ago, and hoped that I could use the opportunity to get it fixed. Also, thanks a lot for the autoneg explanation, Bill. --Emil From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 07:40: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 E5A1116A41F for ; Mon, 28 Nov 2005 07:40:58 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from forrie.com (c-24-62-224-187.hsd1.nh.comcast.net [24.62.224.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6FAE443D5E for ; Mon, 28 Nov 2005 07:40:58 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.98] ([192.168.1.98]) (authenticated bits=0) by forrie.com (8.13.4/8.13.4) with ESMTP id jAS7evoh062109 for ; Mon, 28 Nov 2005 02:40:57 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <438AB4FD.60703@forrie.com> Date: Mon, 28 Nov 2005 02:42:53 -0500 From: Forrest Aldrich User-Agent: Thunderbird 1.5 (Windows/20051123) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1195/Fri Nov 25 04:29:55 2005 on forrie.com X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 28 Nov 2005 12:23:21 +0000 Subject: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 07:40:59 -0000 Odd error with building FreeBSD-6 (cvsup'd today): ===> include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Though clearly "touch" is in PATH and is found otherwise. Bug or typo somewhere? _F From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 12:46:57 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 5BC5316A420 for ; Mon, 28 Nov 2005 12:46:57 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: from mail.bitdefender.com (ns.bitdefender.com [217.156.83.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C67F43D60 for ; Mon, 28 Nov 2005 12:46:55 +0000 (GMT) (envelope-from apircalabu@bitdefender.com) Received: (qmail 17937 invoked by uid 1010); 28 Nov 2005 14:46:21 +0200 Received: from apircalabu.dsd.ro (10.10.15.22) by mail.bitdefender.com with AES256-SHA encrypted SMTP; 28 Nov 2005 14:46:21 +0200 Date: Mon, 28 Nov 2005 14:50:12 +0200 From: Adi Pircalabu To: Forrest Aldrich Message-ID: <20051128145012.074181f0@apircalabu.dsd.ro> In-Reply-To: <438AB4FD.60703@forrie.com> References: <438AB4FD.60703@forrie.com> Organization: BitDefender X-Mailer: Sylpheed-Claws 1.9.100 (GTK+ 2.8.7; i386-portbld-freebsd5.4) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BitDefender-SpamStamp: 1.1.4 049000040111AAAAAAE X-BitDefender-Scanner: Clean, Agent: BitDefender Qmail 1.6.2 on mail.bitdefender.com X-BitDefender-Spam: No (0) Cc: freebsd-current@freebsd.org Subject: Re: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 12:46:57 -0000 On Mon, 28 Nov 2005 02:42:53 -0500 Forrest Aldrich wrote: > Odd error with building FreeBSD-6 (cvsup'd today): > > ===> include (install) > creating osreldate.h from newvers.sh > touch: not found > *** Error code 127 > > Though clearly "touch" is in PATH and is found otherwise. > > Bug or typo somewhere? Did you use -j option during install? Try without it. -- Adi Pircalabu (PGP Key ID 0x04329F5E) -- This message was scanned for spam and viruses by BitDefender. For more information please visit http://www.bitdefender.com/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 13:44: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 2A56316A420 for ; Mon, 28 Nov 2005 13:44:24 +0000 (GMT) (envelope-from bsam@ns.kfs.ru) Received: from ns.kfs.ru (kfs.kfs.ru [62.183.117.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE03F43D76 for ; Mon, 28 Nov 2005 13:44:20 +0000 (GMT) (envelope-from bsam@ns.kfs.ru) Received: from bsam by ns.kfs.ru with local (Exim 4.54 (FreeBSD)) id 1EgjIY-000Gsx-6m; Mon, 28 Nov 2005 16:44:02 +0300 To: Forrest Aldrich References: <438AB4FD.60703@forrie.com> From: Boris Samorodov Date: Mon, 28 Nov 2005 16:44:02 +0300 In-Reply-To: <438AB4FD.60703@forrie.com> (Forrest Aldrich's message of "Mon, 28 Nov 2005 02:42:53 -0500") Message-ID: <39563421@serv3.int.kfs.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: "Boris B. Samorodov" Cc: freebsd-current@freebsd.org Subject: Re: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 13:44:24 -0000 On Mon, 28 Nov 2005 02:42:53 -0500 Forrest Aldrich wrote: > Odd error with building FreeBSD-6 (cvsup'd today): > ===> include (install) > creating osreldate.h from newvers.sh > touch: not found > *** Error code 127 > Though clearly "touch" is in PATH and is found otherwise. > Bug or typo somewhere? How did you upgrade the system? WBR -- Boris B. Samorodov, Research Engineer InPharmTech Co, http://www.ipt.ru Telephone & Internet Service Provider From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 14:07: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 71F2416A41F for ; Mon, 28 Nov 2005 14:07:46 +0000 (GMT) (envelope-from lreid@cs.okstate.edu) Received: from a.cs.okstate.edu (a.cs.okstate.edu [139.78.113.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 02F7B43D4C for ; Mon, 28 Nov 2005 14:07:43 +0000 (GMT) (envelope-from lreid@cs.okstate.edu) Received: from [192.168.220.32] (unknown [164.58.79.195]) by a.cs.okstate.edu (Postfix) with ESMTP id A3217A022C; Mon, 28 Nov 2005 08:07:38 -0600 (CST) Message-ID: <438B0F11.2000209@cs.okstate.edu> Date: Mon, 28 Nov 2005 08:07:13 -0600 From: Reid Linnemann User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051118) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin R. Smith" References: <4386FD58.3080308@drexel.edu> <200511252103.57059.lofi@freebsd.org> <43886492.20702@drexel.edu> In-Reply-To: <43886492.20702@drexel.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: A4Tech Wireless mouse wheel not detected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 14:07:46 -0000 Justin R. Smith wrote: > Michael Nottebrock wrote: > >> >> You need to run moused with the -z4 argument to activate axis mapping >> (put moused_flags=-z4 into /etc/rc.conf), but since you already tried >> in X and said it didn't work ... might be worth a try though, less >> opportunities for typos with moused compared to xorg.conf >> >> I myself use an A4 Tech Office 8K wireless mouse with moused, >> connected to a USB port however, and had to change the default >> usbd.conf line that runs moused to include the axis mapping switch. >> >> >> > Thank you1 I've tried this and nothing changes. I get the impression > that the events are not being picked up at the /dev/psm0 level. > > After trying this, I changed my xorg.conf file and replaced > /dev/sysmouse by /dev/psm0 (bypassing moused completely). X worked but > the wheel didn't. > > If I find the time, I'll look at the psm driver myself. It looks as > though it takes some special actions with A4Tech mice and the solution > might be to force it to regard them as generic PS/2 mice... > _______________________________________________ > 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" change your Mouse0 InputDevice section in xorg.conf: ------------------------------------------------- Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/sysmouse" Option "Buttons" "5" Option "ZAxisMapping" "4 5" EndSection ------------------------------------------------- Mapping the z-axis for moused shouldn't be expected to affect X (and thus xev) if the X mouse driver still believes the device only has 3 buttons. I have never seen a time when a wheel mouse is automagically fully functional with X on FreeBSD. AFIK, these xorg.conf options have always been necessary to enable the z axis. -- Reid Linnemann Senior Systems Analyst Oklahoma Department of CareerTech 405-743-5422 rlinn@okcareertech.org -Ars longa, vita brevis- From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 14:12: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 A781416A41F; Mon, 28 Nov 2005 14:12:53 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from people.fsn.hu (people.fsn.hu [195.228.252.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2BE9F43D68; Mon, 28 Nov 2005 14:12:50 +0000 (GMT) (envelope-from bra@fsn.hu) Received: from localhost (localhost [127.0.0.1]) by people.fsn.hu (Postfix) with ESMTP id 635128444F; Mon, 28 Nov 2005 10:15:11 +0100 (CET) Received: from people.fsn.hu ([127.0.0.1]) by localhost (people.fsn.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 76914-04-5; Mon, 28 Nov 2005 10:15:05 +0100 (CET) Received: from [172.16.151.70] (fw.axelero.hu [195.228.243.120]) by people.fsn.hu (Postfix) with ESMTP id D6EAC8444C; Mon, 28 Nov 2005 10:15:04 +0100 (CET) Message-ID: <438ACA94.6090606@fsn.hu> Date: Mon, 28 Nov 2005 10:15:00 +0100 From: Attila Nagy User-Agent: Debian Thunderbird 1.0.2 (X11/20050602) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: amavisd-new at fsn.hu Cc: Scott Long , =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= Subject: DMA failures on AMD64 with 4 GB RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 14:12:53 -0000 Hello, There is a problem with recent ATA drivers on (at least) AMD64 with 4 GB of RAM, which can be triggered by synchronizing a geom mirror provider to another one (or generally a bigger disk I/O, I guess). The machine dies instantly with the following: GEOM_MIRROR: Device hars: rebuilding provider ad6. ad6: setting up DMA failed ad6: setting up DMA failed This is true either on RELENG_6 and on HEAD as of today. There are two workarounds: - use the ata driver from RELENG_6 which is not older than 2005.10.08 - set hw.physmem smaller than 4G Are there any chances to resolve this issue? Thank you. ps: there was some discussion about this: http://marc.theaimsgroup.com/?l=freebsd-amd64&m=113034973432742&w=2 where Søren said it might be busdma, not the ata driver and Scott promised to look into that. -- Attila Nagy e-mail: Attila.Nagy@fsn.hu Free Software Network (FSN.HU) phone: +3630 306 6758 ISOs: http://www.fsn.hu/?f=download From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 14:23: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 4E13B16A41F; Mon, 28 Nov 2005 14:23:49 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 00F9543D73; Mon, 28 Nov 2005 14:23:40 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 jASENcgd098136; Mon, 28 Nov 2005 15:23:39 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <438B12EA.6030100@deepcore.dk> Date: Mon, 28 Nov 2005 15:23:38 +0100 From: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Attila Nagy References: <438ACA94.6090606@fsn.hu> In-Reply-To: <438ACA94.6090606@fsn.hu> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: freebsd-current@FreeBSD.ORG, Scott Long , =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= Subject: Re: DMA failures on AMD64 with 4 GB RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 14:23:49 -0000 Attila Nagy wrote: > Hello, > > There is a problem with recent ATA drivers on (at least) AMD64 with 4 GB > of RAM, which can be triggered by synchronizing a geom mirror provider > to another one (or generally a bigger disk I/O, I guess). > > The machine dies instantly with the following: > GEOM_MIRROR: Device hars: rebuilding provider ad6. > ad6: setting up DMA failed > ad6: setting up DMA failed > > This is true either on RELENG_6 and on HEAD as of today. > > There are two workarounds: > - use the ata driver from RELENG_6 which is not older than 2005.10.08 > - set hw.physmem smaller than 4G > > Are there any chances to resolve this issue? > > Thank you. > > ps: there was some discussion about this: > http://marc.theaimsgroup.com/?l=freebsd-amd64&m=113034973432742&w=2 > where Søren said it might be busdma, not the ata driver and Scott > promised to look into that. The resolution was that busdma doesn't work as advertised in the man page, and that scottl would look into it. -Søren > From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 15:07: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 4E5B616A41F for ; Mon, 28 Nov 2005 15:07:37 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E28043D75 for ; Mon, 28 Nov 2005 15:07:34 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jASF7P5N005371; Mon, 28 Nov 2005 15:07:25 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jASF7PJm042388; Mon, 28 Nov 2005 15:07:25 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jASF7OkN042387; Mon, 28 Nov 2005 15:07:24 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Martin Cracauer In-Reply-To: <20051127215510.A17131@cons.org> References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> <20051127215510.A17131@cons.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Mon, 28 Nov 2005 15:07:23 +0000 Message-Id: <1133190443.41553.18.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: 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: Mon, 28 Nov 2005 15:07:37 -0000 On Sun, 2005-11-27 at 21:55 -0500, Martin Cracauer wrote: > Cian Hughes wrote on Sun, Nov 27, 2005 at 10:55:02PM +0000: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hey, I'm in no rush on this one, but I'm planning on building a new > > Athlon AMD64 machine, It's primarily as a voip server and file > > storage box for home use and will have 8 SATA (possibly SATA-II) > > drives attached to a RAID 5 card, probably Highpoint (but i'm open on > > this). > > > > I am wondering, what have people on this list built recently, within > > these bounds, I'm looking to choose a motherboard with one or two > > 1000Base-T Ethernet ports (to keep PCI's free for other things, ISDN > > card, TV Tuner, etc...), if possible what has and hasn't worked, i'm > > not too worried about onboard HD controllers, etc. > > I have a DFI SLI-DRI which is NForce 4 based and I am overall amazed > how well it works. In particular the SATA controller (only tested the > first 4 ports). Out of interest, does FreeBSD correctly notice the hot-inserting of SATA drives on this board? I'm fighting with an NForce 4 based system at the moment which notices the hot removal but needs a reboot before it notices a new drive has been inserted (under FreeBSD, Linux and Solaris). Gavin From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 15:17:47 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 F09D516A443 for ; Mon, 28 Nov 2005 15:17:47 +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 4662B43D5A for ; Mon, 28 Nov 2005 15:17:47 +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 jASFHaCt037515; Mon, 28 Nov 2005 16:17:36 +0100 (CET) (envelope-from sos@FreeBSD.org) Message-ID: <438B1F90.3090708@FreeBSD.org> Date: Mon, 28 Nov 2005 16:17:36 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gavin Atkinson References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> <20051127215510.A17131@cons.org> <1133190443.41553.18.camel@buffy.york.ac.uk> In-Reply-To: <1133190443.41553.18.camel@buffy.york.ac.uk> 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: 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: Mon, 28 Nov 2005 15:17:48 -0000 Gavin Atkinson wrote: >On Sun, 2005-11-27 at 21:55 -0500, Martin Cracauer wrote: > > >>Cian Hughes wrote on Sun, Nov 27, 2005 at 10:55:02PM +0000: >> >> >>>-----BEGIN PGP SIGNED MESSAGE----- >>>Hash: SHA1 >>> >>>Hey, I'm in no rush on this one, but I'm planning on building a new >>>Athlon AMD64 machine, It's primarily as a voip server and file >>>storage box for home use and will have 8 SATA (possibly SATA-II) >>>drives attached to a RAID 5 card, probably Highpoint (but i'm open on >>>this). >>> >>>I am wondering, what have people on this list built recently, within >>>these bounds, I'm looking to choose a motherboard with one or two >>>1000Base-T Ethernet ports (to keep PCI's free for other things, ISDN >>>card, TV Tuner, etc...), if possible what has and hasn't worked, i'm >>>not too worried about onboard HD controllers, etc. >>> >>> >>I have a DFI SLI-DRI which is NForce 4 based and I am overall amazed >>how well it works. In particular the SATA controller (only tested the >>first 4 ports). >> >> > >Out of interest, does FreeBSD correctly notice the hot-inserting of SATA >drives on this board? I'm fighting with an NForce 4 based system at the >moment which notices the hot removal but needs a reboot before it >notices a new drive has been inserted (under FreeBSD, Linux and >Solaris). > > That used to work on my MSI nf4 board on 6.0 forward. -Søren From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 15:26: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 4DEA916A41F; Mon, 28 Nov 2005 15:26:36 +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 C0CEE43D6A; Mon, 28 Nov 2005 15:26:32 +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 jASFQRdv031670; Mon, 28 Nov 2005 16:26:27 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jASFQRaX031669; Mon, 28 Nov 2005 10:26:27 -0500 (EST) (envelope-from cracauer) Date: Mon, 28 Nov 2005 10:26:27 -0500 From: Martin Cracauer To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Message-ID: <20051128102626.A31626@cons.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 User-Agent: Mutt/1.2.5i In-Reply-To: <438B1F90.3090708@FreeBSD.org>; from sos@FreeBSD.org on Mon, Nov 28, 2005 at 04:17:36PM +0100 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: Mon, 28 Nov 2005 15:26:36 -0000 > >>I have a DFI SLI-DRI which is NForce 4 based and I am overall amazed > >>how well it works. In particular the SATA controller (only tested the > >>first 4 ports). > >> > >> > > > >Out of interest, does FreeBSD correctly notice the hot-inserting of SATA > >drives on this board? I'm fighting with an NForce 4 based system at the > >moment which notices the hot removal but needs a reboot before it > >notices a new drive has been inserted (under FreeBSD, Linux and > >Solaris). > > > > > That used to work on my MSI nf4 board on 6.0 forward. Can I safely test this by just plugging in a SATA cable with drive and board on? 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 Mon Nov 28 15:31: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 BA49D16A420; Mon, 28 Nov 2005 15:31:09 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 B93F843D73; Mon, 28 Nov 2005 15:31:04 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 jASFUrfG047094; Mon, 28 Nov 2005 16:30:53 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <438B22AD.2030106@deepcore.dk> Date: Mon, 28 Nov 2005 16:30:53 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> <20051127215510.A17131@cons.org> <1133190443.41553.18.camel@buffy.york.ac.uk> <438B1F90.3090708@FreeBSD.org> <20051128102626.A31626@cons.org> In-Reply-To: <20051128102626.A31626@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, =?ISO-8859-1?Q?S=F8ren_Schmidt?= 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: Mon, 28 Nov 2005 15:31:09 -0000 Martin Cracauer wrote: >>That used to work on my MSI nf4 board on 6.0 forward. > > > Can I safely test this by just plugging in a SATA cable with drive and > board on? define safely ? -Søren From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 15:35: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 6415C16A41F for ; Mon, 28 Nov 2005 15:35:34 +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 A3B8443D4C for ; Mon, 28 Nov 2005 15:35:33 +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 jASFZLhQ031954; Mon, 28 Nov 2005 16:35:21 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jASFZK0R031952; Mon, 28 Nov 2005 10:35:20 -0500 (EST) (envelope-from cracauer) Date: Mon, 28 Nov 2005 10:35:20 -0500 From: Martin Cracauer To: Nate Eldredge Message-ID: <20051128103520.A31684@cons.org> References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from nge@cs.hmc.edu on Sun, Nov 27, 2005 at 10:01:13PM -0800 Cc: Cian Hughes , 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: Mon, 28 Nov 2005 15:35:34 -0000 > I put together a machine a couple months ago. I used a Tyan S2875ANRF > ("Tiger K8W") dual-Opteron motherboard and a single Opteron 244 (1.8 GHz) > cpu (second one may come in the future). I am running 5.4 and have been > very happy with it. Note that the Tiger K8W (PCI) does not support dual-core CPUs, where the newest revisions(!) of the Thunder K8W (PCI-X) do. The Thunder is an oversize ATX board, though, and expensive. > I decided it was worth going for Opteron over Athlon 64. They seem to > have better performance (wider memory bus, etc), obviously SMP ability, Sorry, the memory bus is not wider than on socket 939. You do have additional Hyperlinks in the socket 940 CPUs (real-life performance effect unknown to me) and the better boards have seperate memory banks for the CPUs. > and as I understand it the regular Athlon 64s don't support ECC memory > which I insist upon. All AMD64 CPUs support ECC. But only socket 940 requires registered memory. ECC support in socket 754 and 939 is a function of board, but all or almost all Asus boards support it (unregistered ECC of course). > The Athlon 64FX appear to be similar to the fastest > Opterons and differ mainly for price marketing purposes (sold to gamers). The one feature of the FX CPUs is that the LDT->CPU frequency multiplier is unlocked, which allows for freer combining of frequency settings when overclocking. Plus they have high base clocks and many seem to be binned to overclock well. 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 Mon Nov 28 15:39: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 9BC6316A41F; Mon, 28 Nov 2005 15:39:22 +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 EBEEA43D58; Mon, 28 Nov 2005 15:39:21 +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 jASFdEc1032099; Mon, 28 Nov 2005 16:39:14 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jASFdEVf032098; Mon, 28 Nov 2005 10:39:14 -0500 (EST) (envelope-from cracauer) Date: Mon, 28 Nov 2005 10:39:14 -0500 From: Martin Cracauer To: =?iso-8859-1?Q?S=F8ren_Schmidt?= Message-ID: <20051128103914.B31684@cons.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> <20051128102626.A31626@cons.org> <438B22AD.2030106@deepcore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <438B22AD.2030106@deepcore.dk>; from sos@deepcore.dk on Mon, Nov 28, 2005 at 04:30:53PM +0100 Cc: Martin Cracauer , freebsd-current@freebsd.org, =?iso-8859-1?Q?S=F8ren_Schmidt?= 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: Mon, 28 Nov 2005 15:39:22 -0000 Søren Schmidt wrote on Mon, Nov 28, 2005 at 04:30:53PM +0100: > Martin Cracauer wrote: > > >>That used to work on my MSI nf4 board on 6.0 forward. > > > > > > Can I safely test this by just plugging in a SATA cable with drive and > > board on? > > define safely ? Very small chance to damage port or disk. The smallest SATA drive I have is 400 GB so I wouldn't like to risk it, not to mention my best board. While SATA seems to have been designed with hot-plug capabilities in mind, it is unclear to me whether the normal SATA cabeling is actually implementing this. The cables seem to be designed to reliably connect ground first when plugging in, so the answer might be yes. I thought you might know. 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 Mon Nov 28 15:44:51 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 2AE5B16A423; Mon, 28 Nov 2005 15:44:51 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 01C3A43D78; Mon, 28 Nov 2005 15:44:31 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 jASFiGkZ056782; Mon, 28 Nov 2005 16:44:16 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <438B25D0.3050109@deepcore.dk> Date: Mon, 28 Nov 2005 16:44:16 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Martin Cracauer References: <61FBEC57-424E-450F-A775-10E1F5E8DF92@cian.ws> <20051127215510.A17131@cons.org> <1133190443.41553.18.camel@buffy.york.ac.uk> <438B1F90.3090708@FreeBSD.org> <20051128102626.A31626@cons.org> <438B22AD.2030106@deepcore.dk> <20051128103914.B31684@cons.org> In-Reply-To: <20051128103914.B31684@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, =?ISO-8859-1?Q?S=F8ren_Schmidt?= 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: Mon, 28 Nov 2005 15:44:51 -0000 Martin Cracauer wrote: > Søren Schmidt wrote on Mon, Nov 28, 2005 at 04:30:53PM +0100: > >>Martin Cracauer wrote: >> >> >>>>That used to work on my MSI nf4 board on 6.0 forward. >>> >>> >>>Can I safely test this by just plugging in a SATA cable with drive and >>>board on? >> >>define safely ? > > > Very small chance to damage port or disk. The smallest SATA drive I > have is 400 GB so I wouldn't like to risk it, not to mention my best > board. > > While SATA seems to have been designed with hot-plug capabilities in > mind, it is unclear to me whether the normal SATA cabeling is actually > implementing this. The cables seem to be designed to reliably connect > ground first when plugging in, so the answer might be yes. I thought > you might know. That should be perfectly safe yes. The SATA connector was designed with this in mind including the power connector. However, some SATA drives also has the old 4 pin power connector, that one is by no definition safe to hotplug... -Søren From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 15:48:02 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: by hub.freebsd.org (Postfix, from userid 618) id 428F516A422; Mon, 28 Nov 2005 15:48:02 +0000 (GMT) In-Reply-To: <20051128100731.GA9802@cs.rmit.edu.au> from Emil Mikulic at "Nov 28, 2005 09:07:32 pm" To: emil@cs.rmit.edu.au (Emil Mikulic) Date: Mon, 28 Nov 2005 15:48:02 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051128154802.428F516A422@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-current@FreeBSD.ORG, glebius@FreeBSD.ORG Subject: Re: bge driver autoneg failure and system-wide stalls X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 15:48:02 -0000 > On Mon, Nov 28, 2005 at 09:17:58AM +0000, Bill Paul wrote: > > > On Fri, Nov 25, 2005 at 04:22:28PM +0300, Gleb Smirnoff wrote: > > > > On Fri, Nov 25, 2005 at 01:20:41PM +1100, Emil Mikulic wrote: > > In your original e-mail, you write: > > > > > I have a network port with bad wiring in the walls - a cable tester > > > shows only wires 1,2,3 and 6 are actually connected. > > > > Actually, this is not 'bad' wiring. It's correct for 10/100 ethernet > > That was probably the thinking when the office got wired up initially. > > > as long as a) the cabling is actually cat5, and not moldy old cat3 > > or something, and b) the four wires are actually connected in the right > > sequence. Pins 1 and 2 form one pair, and pins 3 and 6 form the second > > pair. A typical installation may have the orange/orange+white pair > > on pins 1 and 2, and the blue/blue+white pair on 3 and 6. And both > > sides must match. If it's not done this way, then while you may have > > a DC path between all 4 pins on each side, you won't be getting the > > proper noise cancellation effect of twisted pair cabling. This can > > cause signal distortion, dropped packets, and possibly botched autoneg. > > > > You didn't say if you checked for this though, so we can't speculate > > if this is really the problem. > > I can't see what's in the walls but I attached the two parts of the > cable tester to both ends of the line and 1-2-3-6 on one end was 1-2-3-6 > on the other end. It sounds correct then. > > A couple things you neglected to mention (and which Gleb failed to > > ask you about): > > (yeah, sorry about that. I spent like an hour with the original > message in a text editor then after I sent it I kept remembering things > I'd forgotten) > > > - Exactly what kind of switch is on the other end of this wiring? > > The switch is managed, and does gigabit. It's a Nortel but I don't > know the exact model off by heart (I can look it up tomorrow if it > matters) It may, only if that helps determine whether the management API lets you turn off the ability to announce gigE support. > > - Is the port that corresponds to this wall jack a gigabit ethernet > > port, or just 10/100? > > All the wiring in the walls is, as you said, for 100Mbit. The switch > and my network card are gigabit. Okay, that's what I suspected. > > If it is a gigE port, then you're being silly. > > Yeah, I thought so. =( > > > 4 pairs are required for gigE. Period. The NWAY autonegotiation > > exchange can take place over just 2 pairs, but the gigE signalling > > scheme requires all 4 pairs to be present in order to establish a > > link. If there's just two pairs connected, both sides will can > > announce that they support gigabit speeds, and both sides will try > > configuring themselves for gigE operation, but no link will ever be > > established. > > I understand that gigabit will never work over the current wiring. > I've accepted that and moved on. =) > > But are you saying the autonegotiation will never work over the current > wiring either? As in, it can't try a slower link speed? Well, that's just it: autoneg is working just fine. Both link partners are happily autonegotiating a gigabit link -- a gigabit link which will never be established thanks to the two missing pairs. So both sides are endlessly retrying over and over without getting anywhere. The autoneg behavior is for both sides to announce all the modes they support, and for both to compare what the link partner supports versus what it supports itself, and choose the best common mode. The selection algorithm is to try 1000Mbps first, then 100 full duplex, then 100 half duplex, then 10 full duplex, and finally 10 half duplex. Since both sides claim they support 1000Mbps, that's the mode they'll try to use. Unfortunately, when you do 'ifconfig bge0 media autoselect' on FreeBSD, the interface will announce that it supports all three speeds (10, 100 and 1000). There's no ifconfig option to make it announce just 10 and 100, which is what you'd need to do since those are the only modes which will work on your existing cabling. And the switch will do the same. So both sides will think they should be trying for the best possible mode, which is 1000Mbps. But that mode won't work since those two pairs aren't available. So somehow, you have to convince one side or the other to only announce 10/100. If the switch has a management option to turn off gigE mode on one of its ports, then that would be one way. If not, you can try modifying brgphy.c as follows: - Find the brgphy_mii_phy_auto() routine. - It looks like this: int ktcr = 0; brgphy_loop(mii); brgphy_reset(mii); ktcr = BRGPHY_1000CTL_AFD|BRGPHY_1000CTL_AHD; if (brgphy_mii_model == MII_MODEL_xxBROADCOM_BCM5701) ktcr |= BRGPHY_1000CTL_MSE|BRGPHY_1000CTL_MSC; PHY_WRITE(mii, BRGPHY_MII_1000CTL, ktcr); ktcr = PHY_READ(mii, BRGPHY_MII_1000CTL); DELAY(1000); PHY_WRITE(mii, BRGPHY_MII_ANAR, BMSR_MEDIA_TO_ANAR(mii->mii_capabilities) | ANAR_CSMA); DELAY(1000); PHY_WRITE(mii, BRGPHY_MII_BMCR, BRGPHY_BMCR_AUTOEN | BRGPHY_BMCR_STARTNEG); PHY_WRITE(mii, BRGPHY_MII_IMR, 0xFF00); return (EJUSTRETURN); - Make it look like this: int ktcr = 0; #define ANNOUNCE_10_100_ONLY brgphy_loop(mii); brgphy_reset(mii); #ifndef ANNOUNCE_10_100_ONLY ktcr = BRGPHY_1000CTL_AFD|BRGPHY_1000CTL_AHD; if (brgphy_mii_model == MII_MODEL_xxBROADCOM_BCM5701) ktcr |= BRGPHY_1000CTL_MSE|BRGPHY_1000CTL_MSC; #endif PHY_WRITE(mii, BRGPHY_MII_1000CTL, ktcr); ktcr = PHY_READ(mii, BRGPHY_MII_1000CTL); DELAY(1000); PHY_WRITE(mii, BRGPHY_MII_ANAR, BMSR_MEDIA_TO_ANAR(mii->mii_capabilities) | ANAR_CSMA); DELAY(1000); PHY_WRITE(mii, BRGPHY_MII_BMCR, BRGPHY_BMCR_AUTOEN | BRGPHY_BMCR_STARTNEG); PHY_WRITE(mii, BRGPHY_MII_IMR, 0xFF00); return (EJUSTRETURN); This should force it to announce that it only supports 10/100 modes. In theory, this should get you a 100Mbps full duplex link with the switch. When you actually get gigE cabling, remove the '#define ANNOUNCE_10_100_ONLY' line. > > If you manually override the autonegotiation in this case, you should > > do "ifconfig bge0 media 100baseTX" only. Do not specify full duplex. > > This won't work. > > > > [...] > > > > If you manually specify full, this will create a duplex mismatch, and > > you'll get rotten throughput. > > 10baseT/UTP and 100baseTX worked in both half-duplex and full-duplex > but I didn't check throughput... > > Important bit: > > > Also, the DELAY(10) here can probably be replaced with a tsleep() or > > something, which will allow the CPU to do other work while waiting for > > the PHY instead of hard busywaiting and blocking up the whole system > > (allowing a reschedule here should not hurt). > > This would be cool! > > I realise that I am doing stupid things with broken wiring and that it > won't work, but if the "periodic lockup" problem could be fixed, that > would be an improvement to the bge(4) driver, IMO. > > When I first noticed this symptom, it took quite a while to go from > "FreeBSD is doing this annoying lockup thing every few seconds and I > keep losing keypresses" to "oh, it's the network card / cabling / > driver" The above change should get you a link and will prevent the periodic lockup from occuring. I need to actually test the tsleep() change before I can give you a patch to try. -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 16:05: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 3006816A41F for ; Mon, 28 Nov 2005 16:05:08 +0000 (GMT) (envelope-from randy@psg.com) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D84243D6E for ; Mon, 28 Nov 2005 16:04:58 +0000 (GMT) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=roam.psg.com) by rip.psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54 (FreeBSD)) id 1EglUr-0002Do-4x for freebsd-current@freebsd.org; Mon, 28 Nov 2005 16:04:53 +0000 Received: from localhost ([127.0.0.1] helo=roam.psg.com) by roam.psg.com with esmtp (Exim 4.54 (FreeBSD)) id 1EglUq-000FRr-19 for freebsd-current@freebsd.org; Mon, 28 Nov 2005 06:04:52 -1000 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17291.10915.626736.209690@roam.psg.com> Date: Mon, 28 Nov 2005 06:04:51 -1000 To: FreeBSD Current References: <17290.7435.851684.533219@roam.psg.com> Subject: Re: uipc_mqueue.c:1832: warning: 'mq' might be used uninitialized in this function X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 16:05:08 -0000 fwiw, new cvsup with new version of mqueue fixed the problem randy From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 16:44: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 B66B016A41F; Mon, 28 Nov 2005 16:44:48 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE21F43D4C; Mon, 28 Nov 2005 16:44:46 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw0.york.ac.uk (8.12.10/8.12.10) with ESMTP id jASGiO6B000486; Mon, 28 Nov 2005 16:44:24 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jASGiOee042752; Mon, 28 Nov 2005 16:44:24 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jASGiNKS042751; Mon, 28 Nov 2005 16:44:23 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: =?ISO-8859-1?Q?S=F8ren?= Schmidt In-Reply-To: <438B1F90.3090708@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> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Nov 2005 16:44:23 +0000 Message-Id: <1133196263.41553.54.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk 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: Mon, 28 Nov 2005 16:44:48 -0000 On Mon, 2005-11-28 at 16:17 +0100, S=F8ren Schmidt wrote: > Gavin Atkinson wrote: >=20 > >On Sun, 2005-11-27 at 21:55 -0500, Martin Cracauer wrote: > > =20 > > > >>Cian Hughes wrote on Sun, Nov 27, 2005 at 10:55:02PM +0000:=20 > >> =20 > >> > >>>-----BEGIN PGP SIGNED MESSAGE----- > >>>Hash: SHA1 > >>> > >>>Hey, I'm in no rush on this one, but I'm planning on building a new =20 > >>>Athlon AMD64 machine, It's primarily as a voip server and file =20 > >>>storage box for home use and will have 8 SATA (possibly SATA-II) =20 > >>>drives attached to a RAID 5 card, probably Highpoint (but i'm open on = =20 > >>>this). > >>> > >>>I am wondering, what have people on this list built recently, within =20 > >>>these bounds, I'm looking to choose a motherboard with one or two =20 > >>>1000Base-T Ethernet ports (to keep PCI's free for other things, ISDN =20 > >>>card, TV Tuner, etc...), if possible what has and hasn't worked, i'm =20 > >>>not too worried about onboard HD controllers, etc. > >>> =20 > >>> > >>I have a DFI SLI-DRI which is NForce 4 based and I am overall amazed > >>how well it works. In particular the SATA controller (only tested the > >>first 4 ports). > >> =20 > >> > > > >Out of interest, does FreeBSD correctly notice the hot-inserting of SATA > >drives on this board? I'm fighting with an NForce 4 based system at the > >moment which notices the hot removal but needs a reboot before it > >notices a new drive has been inserted (under FreeBSD, Linux and > >Solaris). > > =20 > > > That used to work on my MSI nf4 board on 6.0 forward. Hmm, well that's promising. This is with: atapci1@pci0:7:0: class=3D0x010485 card=3D0x5348108e chip=3D0x005410d= e rev=3D0xf3 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' device =3D 'nForce4 Serial ATA Controller' class =3D mass storage subclass =3D RAID I don't know if it makes any difference, but the board has on-board NVIDIA RAID, which I'm considerably less than impressed with. I'll build one of them without the on-board RAID support and see if hot-insert works. I don't have the logs (long story, but basically the RAID bios hosed my data) but I think it failed to notice the inserted disk, and was timing out while trying to select the channel when forced with an atacontrol reinit. Gavin From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 17:04: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 69E9916A51E; Mon, 28 Nov 2005 17:04:24 +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 F2BE043D67; Mon, 28 Nov 2005 17:04:18 +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 jASH43OU075630; Mon, 28 Nov 2005 10:04:04 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <438B3883.7090205@samsco.org> Date: Mon, 28 Nov 2005 10:04:03 -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: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= References: <438ACA94.6090606@fsn.hu> <438B12EA.6030100@deepcore.dk> In-Reply-To: <438B12EA.6030100@deepcore.dk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Attila Nagy , freebsd-current@FreeBSD.ORG, Scott Long , =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= Subject: Re: DMA failures on AMD64 with 4 GB RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 17:04:24 -0000 Søren Schmidt wrote: > Attila Nagy wrote: > >> Hello, >> >> There is a problem with recent ATA drivers on (at least) AMD64 with 4 >> GB of RAM, which can be triggered by synchronizing a geom mirror >> provider to another one (or generally a bigger disk I/O, I guess). >> >> The machine dies instantly with the following: >> GEOM_MIRROR: Device hars: rebuilding provider ad6. >> ad6: setting up DMA failed >> ad6: setting up DMA failed >> >> This is true either on RELENG_6 and on HEAD as of today. >> >> There are two workarounds: >> - use the ata driver from RELENG_6 which is not older than 2005.10.08 >> - set hw.physmem smaller than 4G >> >> Are there any chances to resolve this issue? >> >> Thank you. >> >> ps: there was some discussion about this: >> http://marc.theaimsgroup.com/?l=freebsd-amd64&m=113034973432742&w=2 >> where Søren said it might be busdma, not the ata driver and Scott >> promised to look into that. > > > The resolution was that busdma doesn't work as advertised in the man > page, and that scottl would look into it. > > -Søren Well, the more accurate statement is that the manpage is not the authoritative design document, but rather a poorly adapted representation of how the subsystem might work on NetBSD =-) So busdma needs to be fixed to provide what the drivers need, and the manpage needs to be fixed to reflect how things actually work. In any case ATA still doesn't come anywhere close to conforming to the busdma API, and I doubt that me rewriting the manpage will fix that. Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 17:04: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 B8B3F16A53B for ; Mon, 28 Nov 2005 17:04: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 7318743D58 for ; Mon, 28 Nov 2005 17:04:43 +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 2741939 for multiple; Mon, 28 Nov 2005 12:04:33 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASH3rCQ058457; Mon, 28 Nov 2005 12:04:19 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Matthew Dillon Date: Mon, 28 Nov 2005 12:03:59 -0500 User-Agent: KMail/1.8.2 References: <200511231406.06282.jhb@freebsd.org> <20051125142713.M23990@maildrop.int.zabbadoz.net> <200511251609.jAPG9TRQ059536@apollo.backplane.com> In-Reply-To: <200511251609.jAPG9TRQ059536@apollo.backplane.com> MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200511281204.01545.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit 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: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: nve locking fixes round 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 17:04:53 -0000 On Friday 25 November 2005 11:09 am, Matthew Dillon wrote: > :... > : > :> The reason I set sc->pending_txs to 0 in DFly after the reinit is > :> because when a watchdog timeout occurs and you reset the device, > :> *ALL* mbufs still sitting in the transmit ring are lost. They will > :> never be acknowledged, ever. So pending_txs will never drop back to > :> 0 on its own. This is what led to continuous watchdog timeout reports > :> when, in fact, only one timeout actually occured. > : > :the problem is that with some versions of the hardware you are not > :even able to get the first packet out. > : > :-- > :Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT > > I'm not sure if its the same as what happened to me, but I believe > I have observed this as well. But at least in my case it turned out > to be a bug in (if_nv.c for DFly) that issued ABI calls before > resetting the hardware. I think it had something to do with nv_stop() > being called before the initial hardware reset and nv_stop() then making an > ABI call or two that expected the hardware to already be in a sane state > (when it wasn't). You'd have to look at the DFly commit to see for sure. Yes, I have that patch in my tree though I'm not sure it is in the patch I posted. I'll update the patch to include that. Actually, try the first hunk in the patch at http://www.FreeBSD.org/~jhb/patches/nve_dffixes.patch it is the change Matt is referring to. -- 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 Nov 28 17:20: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 422AD16A41F; Mon, 28 Nov 2005 17:20:34 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 89BE243D5D; Mon, 28 Nov 2005 17:20:33 +0000 (GMT) (envelope-from sos@deepcore.dk) 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 jASHKW8s026277; Mon, 28 Nov 2005 18:20:32 +0100 (CET) (envelope-from sos@deepcore.dk) Message-ID: <438B3C5F.2060500@deepcore.dk> Date: Mon, 28 Nov 2005 18:20:31 +0100 From: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051013) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Scott Long References: <438ACA94.6090606@fsn.hu> <438B12EA.6030100@deepcore.dk> <438B3883.7090205@samsco.org> In-Reply-To: <438B3883.7090205@samsco.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-mail-scanned: by DeepCore Virus & Spam killer v1.16 Cc: Attila Nagy , freebsd-current@FreeBSD.ORG, Scott Long Subject: Re: DMA failures on AMD64 with 4 GB RAM X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 17:20:34 -0000 Scott Long wrote: > Søren Schmidt wrote: > >> Attila Nagy wrote: >> >>> Hello, >>> >>> There is a problem with recent ATA drivers on (at least) AMD64 with 4 >>> GB of RAM, which can be triggered by synchronizing a geom mirror >>> provider to another one (or generally a bigger disk I/O, I guess). >>> >>> The machine dies instantly with the following: >>> GEOM_MIRROR: Device hars: rebuilding provider ad6. >>> ad6: setting up DMA failed >>> ad6: setting up DMA failed >>> >>> This is true either on RELENG_6 and on HEAD as of today. >>> >>> There are two workarounds: >>> - use the ata driver from RELENG_6 which is not older than 2005.10.08 >>> - set hw.physmem smaller than 4G >>> >>> Are there any chances to resolve this issue? >>> >>> Thank you. >>> >>> ps: there was some discussion about this: >>> http://marc.theaimsgroup.com/?l=freebsd-amd64&m=113034973432742&w=2 >>> where Søren said it might be busdma, not the ata driver and Scott >>> promised to look into that. >> >> The resolution was that busdma doesn't work as advertised in the man >> page, and that scottl would look into it > > Well, the more accurate statement is that the manpage is not the > authoritative design document, but rather a poorly adapted > representation of how the subsystem might work on NetBSD =-) So > busdma needs to be fixed to provide what the drivers need, and > the manpage needs to be fixed to reflect how things actually work. > > In any case ATA still doesn't come anywhere close to conforming to > the busdma API, and I doubt that me rewriting the manpage will fix > that. Hmm, thats not how I recall the conclusion, but anyway.. Please mark ATA as broken for > 4G of memory then, I have no immediate plans to rework the entire logic to bend over backwards for busdma's callback centric world just yet. -Søren From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 17:27: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 B932816A41F for ; Mon, 28 Nov 2005 17:27:19 +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 6BB0B43DAF for ; Mon, 28 Nov 2005 17:26:57 +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 jASHQjDY039992; Mon, 28 Nov 2005 19:26:45 +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 23042-04-2; Mon, 28 Nov 2005 19:26:44 +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 jASHNF2A039880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Nov 2005 19:23:15 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jASHNGl9063122; Mon, 28 Nov 2005 19:23:16 +0200 (EET) (envelope-from ru) Date: Mon, 28 Nov 2005 19:23:16 +0200 From: Ruslan Ermilov To: Forrest Aldrich Message-ID: <20051128172316.GE62631@ip.net.ua> References: <438AB4FD.60703@forrie.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CGDBiGfvSTbxKZlW" Content-Disposition: inline In-Reply-To: <438AB4FD.60703@forrie.com> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-current@freebsd.org Subject: Re: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 17:27:19 -0000 --CGDBiGfvSTbxKZlW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 02:42:53AM -0500, Forrest Aldrich wrote: > Odd error with building FreeBSD-6 (cvsup'd today): >=20 > =3D=3D=3D> include (install) > creating osreldate.h from newvers.sh > touch: not found > *** Error code 127 >=20 > Though clearly "touch" is in PATH and is found otherwise. >=20 > Bug or typo somewhere? >=20 This is a FAQ (but not in a FAQ document). Please search the mailing list archives. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --CGDBiGfvSTbxKZlW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDiz0EqRfpzJluFF4RArO0AJ9KThyLJqFbodWecBNACFqYqu6H7gCeNUEr HSBtFb2btcLwVfmwZFA00hI= =W6ES -----END PGP SIGNATURE----- --CGDBiGfvSTbxKZlW-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 18:05:41 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 E151316A41F; Mon, 28 Nov 2005 18:05:41 +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 17D5443D69; Mon, 28 Nov 2005 18:05:22 +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 jASI5G1u036219; Mon, 28 Nov 2005 19:05:16 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jASI5GNW036218; Mon, 28 Nov 2005 13:05:16 -0500 (EST) (envelope-from cracauer) Date: Mon, 28 Nov 2005 13:05:16 -0500 From: Martin Cracauer To: Gavin Atkinson Message-ID: <20051128130516.A36114@cons.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> <1133196263.41553.54.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1133196263.41553.54.camel@buffy.york.ac.uk>; from gavin.atkinson@ury.york.ac.uk on Mon, Nov 28, 2005 at 04:44:23PM +0000 Cc: Martin Cracauer , freebsd-current@freebsd.org, =?iso-8859-1?Q?S=F8ren_Schmidt?= 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: Mon, 28 Nov 2005 18:05:42 -0000 > Hmm, well that's promising. This is with: > atapci1@pci0:7:0: class=0x010485 card=0x5348108e chip=0x005410de > rev=0xf3 hdr=0x00 > vendor = 'NVIDIA Corporation' > device = 'nForce4 Serial ATA Controller' > class = mass storage > subclass = RAID > > I don't know if it makes any difference, but the board has on-board > NVIDIA RAID, which I'm considerably less than impressed with. I'll > build one of them without the on-board RAID support and see if > hot-insert works. I don't have the logs (long story, but basically the > RAID bios hosed my data) but I think it failed to notice the inserted > disk, and was timing out while trying to select the channel when forced > with an atacontrol reinit. Do not use this for safety/raid1. I have seen several reports that the NVidia software raid wipes out the intact drive on warm boot when the machine reboots with one drive bad. Seems to do a random pick which drive to mirror to which other. gmirror will do fine for raid1, and performs adequately (not as well as Linux software raid1, but probably better than NVidia anyway). 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 Mon Nov 28 20:14: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 EC1BF16A422 for ; Mon, 28 Nov 2005 20:14:31 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2D343D77 for ; Mon, 28 Nov 2005 20:14:15 +0000 (GMT) (envelope-from swhetzel@gmail.com) Received: by xproxy.gmail.com with SMTP id s9so2180277wxc for ; Mon, 28 Nov 2005 12:14:11 -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=r24N8k86DVBchSP6JkqWrPP6pORIw2yoGqKZom++0iGgv3obS/CGRcFBy8mdjnzh3PQpxn2lRMQrpjShSoGPCPFUaFfVWP9IQKuCbDAKb8idK7ZAEq1robyPR6fQCm1KrTPHbIOiCxN74N4SpRxfbWpJbfCZBjHPfln0ct1rBCU= Received: by 10.70.60.12 with SMTP id i12mr984730wxa; Mon, 28 Nov 2005 12:14:11 -0800 (PST) Received: by 10.70.31.5 with HTTP; Mon, 28 Nov 2005 12:14:11 -0800 (PST) Message-ID: <790a9fff0511281214h64d4dc95k2ecfca0a30da5b8d@mail.gmail.com> Date: Mon, 28 Nov 2005 14:14:11 -0600 From: Scot Hetzel To: "Justin R. Smith" In-Reply-To: <4388E376.5010605@drexel.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4388E376.5010605@drexel.edu> Cc: freebsd-current@freebsd.org Subject: Re: A4Tech mouse problem solved (but strangely!) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 20:14:32 -0000 On 11/26/05, Justin R. Smith wrote: > I had a problem with the mouse wheel being detected on my wireless > A4Tech mouse. It is supposed to emulate a generic Intellimouse. > > The solution is to run moused with NO type parameter. A parameter of > "auto" or "ps/2" or "microsoft" won't work. You must have a command line = of: > > /usr/sbin/moused -p /dev/psm0 > > (with NO -t parameter) > Unfortunately, one cannot use the automatic scripts in rc.conf to do > this because they always use a parameter and fill in "microsoft" if one > leaves the mouse type blank. > Make the following changes to /etc/rc.d/moused Add this if statement before "echo -n "Starting ${ms} moused:" : fi if "${mytype}" =3D=3D "NONE" ; then mytype=3D"" fi echo -n "Starting ${ms} moused:" : Then change: /usr/sbin/moused ${myflags} -p ${myport} -t ${mytype} ${_pidarg} to /usr/sbin/moused ${myflags} -p ${myport} ${mytype:+-t} ${mytype} ${_pidarg} Now add to /etc/rc.conf: moused_psm0_type=3D"NONE" or moused_type=3D"NONE" ${mytype:+-t} will modify the commands flags only, when ${mytype} is unset or null, null is substituted; otherwise -t substituted. I haven't checked if this works, but if you could make the changes, verify that it works for you and submit a PR with the patch. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:29: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 5E48316A424 for ; Mon, 28 Nov 2005 21:29:53 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDB7243D4C for ; Mon, 28 Nov 2005 21:29:52 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id jASLSV0U004402; Mon, 28 Nov 2005 13:28:32 -0800 From: Kent Stewart To: freebsd-current@freebsd.org Date: Mon, 28 Nov 2005 13:28:48 -0800 User-Agent: KMail/1.8.3 References: <438AB4FD.60703@forrie.com> <39563421@serv3.int.kfs.ru> In-Reply-To: <39563421@serv3.int.kfs.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281328.48486.kstewart@owt.com> Cc: Boris Samorodov , Forrest Aldrich Subject: Re: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 21:29:53 -0000 On Monday 28 November 2005 05:44 am, Boris Samorodov wrote: > On Mon, 28 Nov 2005 02:42:53 -0500 Forrest Aldrich wrote: > > Odd error with building FreeBSD-6 (cvsup'd today): > > > > ===> include (install) > > creating osreldate.h from newvers.sh > > touch: not found > > *** Error code 127 > > > > Though clearly "touch" is in PATH and is found otherwise. > > > > Bug or typo somewhere? > > How did you upgrade the system? > His system clock is mostly likely off and he created files that are older than he got with cvsup. Then, make thinks he needs to generate them again before it does the install. All he has to do is set the system clock to the right time and redo the update. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:35: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 9010616A41F; Mon, 28 Nov 2005 21:35: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 03F2B43D7D; Mon, 28 Nov 2005 21:35:11 +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 jASLZAho022401; Mon, 28 Nov 2005 16:35:10 -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 jASLZ9uv052976; Mon, 28 Nov 2005 16:35:10 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 253D77302F; Mon, 28 Nov 2005 16:35:09 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051128213509.253D77302F@freebsd-current.sentex.ca> Date: Mon, 28 Nov 2005 16:35:09 -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 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: Mon, 28 Nov 2005 21:35:27 -0000 TB --- 2005-11-28 20:14:14 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-28 20:14:14 - starting HEAD tinderbox run for i386/i386 TB --- 2005-11-28 20:14:14 - cleaning the object tree TB --- 2005-11-28 20:14:48 - checking out the source tree TB --- 2005-11-28 20:14:48 - cd /tinderbox/HEAD/i386/i386 TB --- 2005-11-28 20:14:48 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-28 20:20:59 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-28 20:20:59 - cd /src TB --- 2005-11-28 20:20:59 - /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-11-28 21:25:33 - generating LINT kernel config TB --- 2005-11-28 21:25:33 - cd /src/sys/i386/conf TB --- 2005-11-28 21:25:33 - /usr/bin/make -B LINT TB --- 2005-11-28 21:25:34 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-28 21:25:34 - cd /src TB --- 2005-11-28 21:25:34 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 28 21:25:34 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_mbuf2.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_proto.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_sem.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_socket.c /src/sys/kern/uipc_socket.c: In function `sosend_copyin': /src/sys/kern/uipc_socket.c:631: error: `so_zerocp_stats' undeclared (first use in this function) /src/sys/kern/uipc_socket.c:631: error: (Each undeclared identifier is reported only once /src/sys/kern/uipc_socket.c:631: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-28 21:35:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-28 21:35:08 - ERROR: failed to build lint kernel TB --- 2005-11-28 21:35:08 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:37: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 9B7E916A420 for ; Mon, 28 Nov 2005 21:37:22 +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 A515A43D6E for ; Mon, 28 Nov 2005 21:37:10 +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 2756546 for multiple; Mon, 28 Nov 2005 16:37:16 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASLaw2R063566; Mon, 28 Nov 2005 16:37:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 28 Nov 2005 16:26:32 -0500 User-Agent: KMail/1.8.2 References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> In-Reply-To: <20051124062711.GA15961@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281626.33591.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 , Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 21:37:22 -0000 On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: > > Until this gets "fixed" in FreeBSD, what should those of us who are > > effectively stuck with this hardware do to avoid the problem? Does the > > problem exist in RELENG_4? > > Yes, on the same machine I first mentioned. This is the first I've heard that the problem occurs on 4.x as well. :( -- 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 Nov 28 21:37: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 310D816A41F for ; Mon, 28 Nov 2005 21:37:24 +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 6207443DA3 for ; Mon, 28 Nov 2005 21:37:10 +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 2756543 for multiple; Mon, 28 Nov 2005 16:37:13 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASLaw2Q063566; Mon, 28 Nov 2005 16:36:58 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 28 Nov 2005 16:25:52 -0500 User-Agent: KMail/1.8.2 References: <002801c5f081$f01ff200$642a15ac@smiley> <20051124071405.GA15743@pit.databus.com> <4387EC9E.5040709@elischer.org> In-Reply-To: <4387EC9E.5040709@elischer.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281625.53629.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 Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 21:37:24 -0000 On Saturday 26 November 2005 12:03 am, Julian Elischer wrote: > So I haven't been paying too much attention to this thread and now > suddenly I find that > I may have a variant of this problem. > > I have been tasked with adding a 4 port intel (em) based card into a > Dell 2850 based system. > It is based on the intel E7525 chipset and running 4.11. > > I have noticed that this system has irq's in use from 16 down (Maybe in > -current it may use higher) > but that some interrupt counts seem to move together, as if they are > wired to gether. > > I also have the problem that the system seems to get completely wedged > sometimes > as it seems to get into the em driver interupt routine and never get out > again, > or if it does get out it gets called right back in again. > > Can someone who was following this tell me if this is the same problem? > > I can get into the kernel debugger and it usually shows the > amr interrupt handler, having been interrupted by the em driver, (and > that interrupted by > the keyboard interrupt handler for the KDB entry.) > > It seems that no matter how hard it tries or how often it is called the em > driver is unable to clear this interrupt. > > > Am I reading this correctly in that it seems to be the same problem as was > being discussed here? It could be. 4.x handles interrupt storms much more poorly (more prone to deadlock) than 5.x and later, and it still masks level-triggerred interrupts in the APIC while it waits for the handler to run. -- 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 Nov 28 21:55: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 A4D7F16A41F; Mon, 28 Nov 2005 21:55: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 5B73A43D5F; Mon, 28 Nov 2005 21:55: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 401971A3C28; Mon, 28 Nov 2005 13:55:12 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 9799F515B3; Mon, 28 Nov 2005 16:55:11 -0500 (EST) Date: Mon, 28 Nov 2005 16:55:11 -0500 From: Kris Kennaway To: John Baldwin Message-ID: <20051128215511.GA29717@xor.obsecurity.org> References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ReaqsoxgOBHFXBhH" Content-Disposition: inline In-Reply-To: <200511281626.33591.jhb@freebsd.org> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org, Darren Pilgrim , Kris Kennaway Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 21:55:12 -0000 --ReaqsoxgOBHFXBhH Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 28, 2005 at 04:26:32PM -0500, John Baldwin wrote: > On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > > On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: > > > Until this gets "fixed" in FreeBSD, what should those of us who are > > > effectively stuck with this hardware do to avoid the problem? Does t= he > > > problem exist in RELENG_4? > > > > Yes, on the same machine I first mentioned. >=20 > This is the first I've heard that the problem occurs on 4.x as well. :( Yeah..maybe the problem is not what was first believed, since that would apparently exclude 4.x? Kris --ReaqsoxgOBHFXBhH Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDi3y/Wry0BWjoQKURAvDLAKDjhve63sD7K9sHKHDTmoKoNlTfkwCgku0Q xCKkNgtzyAV0iB7FQKoHgmI= =KGRw -----END PGP SIGNATURE----- --ReaqsoxgOBHFXBhH-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 22:06:56 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 B2FB916A41F for ; Mon, 28 Nov 2005 22:06:56 +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 1925943D49 for ; Mon, 28 Nov 2005 22:06: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 2758366 for multiple; Mon, 28 Nov 2005 17:07:03 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jASM6jwn063754; Mon, 28 Nov 2005 17:06:49 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: Kris Kennaway Date: Mon, 28 Nov 2005 17:06:18 -0500 User-Agent: KMail/1.8.2 References: <43842D41.1050401@samsco.org> <200511281626.33591.jhb@freebsd.org> <20051128215511.GA29717@xor.obsecurity.org> In-Reply-To: <20051128215511.GA29717@xor.obsecurity.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511281706.19695.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, Darren Pilgrim Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 22:06:56 -0000 On Monday 28 November 2005 04:55 pm, Kris Kennaway wrote: > On Mon, Nov 28, 2005 at 04:26:32PM -0500, John Baldwin wrote: > > On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > > > On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: > > > > Until this gets "fixed" in FreeBSD, what should those of us who are > > > > effectively stuck with this hardware do to avoid the problem? Does > > > > the problem exist in RELENG_4? > > > > > > Yes, on the same machine I first mentioned. > > > > This is the first I've heard that the problem occurs on 4.x as well. :( > > Yeah..maybe the problem is not what was first believed, since that > would apparently exclude 4.x? Well, 4.x does mask level-triggered APIC interrupts, but I'm not sure the boot interrupt is the issue as people have tried to turn the boot interrupt off and that didn't help. :( I'm not sure why the interrupt aliasing is occurring. I do wonder if it happens on Windows or other OS's and nobody notices. -- 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 Nov 28 22:11:29 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 8331216A41F for ; Mon, 28 Nov 2005 22:11:29 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3F6243D68 for ; Mon, 28 Nov 2005 22:11:26 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 0C3D6BC66 for ; Mon, 28 Nov 2005 22:11:24 +0000 (UTC) To: current@freebsd.org From: Poul-Henning Kamp Date: Mon, 28 Nov 2005 23:11:24 +0100 Message-ID: <6592.1133215884@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Subject: proof-of-concept patch for cpu accounting speedup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 22:11:29 -0000 http://phk.freebsd.dk/patch/context_time.patch This is just a proof of concept, it doesn't have all the tricky bits for determining max TSC rate on machines where the cpu clock is fiddled with and it doesn't have a fallback for machines without TSC etc etc. But in your average i386 (and probably amd64) system it should work. I am very interested to hear feedback and benchmarks of this patch. The two most critical measurements are: * "how does it affect workloads which do many context switches" and * "how does this affect CPU time accounting." To measure the latter, make absolutely sure your machine doesn't play power saving tricks with the TSC/cpu clock. A quick sanity check reveals no obvious bogons in cpu time accounting and unixbench's context1 switch shows 23% improvement on my testbox: x _reference + _patched +--------------------------------------------------------------------------+ |x xx x + ++ ++| | |_AM_| |____A___|| +--------------------------------------------------------------------------+ N Min Max Median Avg Stddev x 5 48370 49433 48997 48959.8 380.65693 + 5 59107 61079 60536 60376.4 786.45458 Difference at 95.0% confidence 11416.6 +/- 901.059 23.3183% +/- 1.84041% (Student's t, pooled s = 617.823) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 21:51:23 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 3AE5316A41F for ; Mon, 28 Nov 2005 21:51:23 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from forrie.com (c-24-62-224-187.hsd1.nh.comcast.net [24.62.224.187]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7122543D88 for ; Mon, 28 Nov 2005 21:51:14 +0000 (GMT) (envelope-from forrie@forrie.com) Received: from [192.168.1.98] ([192.168.1.98]) (authenticated bits=0) by forrie.com (8.13.4/8.13.4) with ESMTP id jASLpCUS002909; Mon, 28 Nov 2005 16:51:12 -0500 (EST) (envelope-from forrie@forrie.com) Message-ID: <438B7C43.4060506@forrie.com> Date: Mon, 28 Nov 2005 16:53:07 -0500 From: Forrest Aldrich User-Agent: Thunderbird 1.5 (Windows/20051123) MIME-Version: 1.0 To: Kent Stewart References: <438AB4FD.60703@forrie.com> <39563421@serv3.int.kfs.ru> <200511281328.48486.kstewart@owt.com> In-Reply-To: <200511281328.48486.kstewart@owt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.87/1197/Mon Nov 28 13:09:01 2005 on forrie.com X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 28 Nov 2005 22:32:29 +0000 Cc: Boris Samorodov , freebsd-current@freebsd.org Subject: Re: touch: not found X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 28 Nov 2005 21:51:23 -0000 This may have been the problem. What I did was run a buildworld on a faster machine - then, installworld via an NFS mount and it worked. Thanks for everyone's help. Kent Stewart wrote: > On Monday 28 November 2005 05:44 am, Boris Samorodov wrote: > >> On Mon, 28 Nov 2005 02:42:53 -0500 Forrest Aldrich wrote: >> >>> Odd error with building FreeBSD-6 (cvsup'd today): >>> >>> ===> include (install) >>> creating osreldate.h from newvers.sh >>> touch: not found >>> *** Error code 127 >>> >>> Though clearly "touch" is in PATH and is found otherwise. >>> >>> Bug or typo somewhere? >>> >> How did you upgrade the system? >> >> > > His system clock is mostly likely off and he created files that are > older than he got with cvsup. Then, make thinks he needs to generate > them again before it does the install. > > All he has to do is set the system clock to the right time and redo the > update. > > Kent > > From owner-freebsd-current@FreeBSD.ORG Mon Nov 28 22:54:39 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 9592716A41F; Mon, 28 Nov 2005 22:54:39 +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 1696543D62; Mon, 28 Nov 2005 22:54:36 +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 jASMsYL2048397; Mon, 28 Nov 2005 17:54:35 -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 jASMsYWk096898; Mon, 28 Nov 2005 17:54:34 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id A14E47302F; Mon, 28 Nov 2005 17:54:34 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20051128225434.A14E47302F@freebsd-current.sentex.ca> Date: Mon, 28 Nov 2005 17:54:34 -0500 (EST) X-Virus-Scanned: ClamAV version 0.86, clamav-milter version 0.86 on clamscanner1 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: Mon, 28 Nov 2005 22:54:39 -0000 TB --- 2005-11-28 21:35:09 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2005-11-28 21:35:09 - starting HEAD tinderbox run for i386/pc98 TB --- 2005-11-28 21:35:09 - cleaning the object tree TB --- 2005-11-28 21:35:39 - checking out the source tree TB --- 2005-11-28 21:35:39 - cd /tinderbox/HEAD/i386/pc98 TB --- 2005-11-28 21:35:39 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2005-11-28 21:41:33 - building world (CFLAGS=-O2 -pipe) TB --- 2005-11-28 21:41:33 - cd /src TB --- 2005-11-28 21:41: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-11-28 22:46:04 - generating LINT kernel config TB --- 2005-11-28 22:46:04 - cd /src/sys/pc98/conf TB --- 2005-11-28 22:46:04 - /usr/bin/make -B LINT TB --- 2005-11-28 22:46:05 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2005-11-28 22:46:05 - cd /src TB --- 2005-11-28 22:46:05 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 28 22:46:05 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_mbuf2.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_proto.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_sem.c cc -c -O2 -pipe -fno-strict-aliasing -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -finstrument-functions -Wno-inline /src/sys/kern/uipc_socket.c /src/sys/kern/uipc_socket.c: In function `sosend_copyin': /src/sys/kern/uipc_socket.c:631: error: `so_zerocp_stats' undeclared (first use in this function) /src/sys/kern/uipc_socket.c:631: error: (Each undeclared identifier is reported only once /src/sys/kern/uipc_socket.c:631: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2005-11-28 22:54:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2005-11-28 22:54:34 - ERROR: failed to build lint kernel TB --- 2005-11-28 22:54:34 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 00:20: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 257DB16A432; Tue, 29 Nov 2005 00:20:25 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EEF043D73; Tue, 29 Nov 2005 00:20:07 +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 F413022956C; Mon, 28 Nov 2005 16:20:00 -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 jAT0K0R9073182; Mon, 28 Nov 2005 16:20:00 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <438B9EA8.60703@elischer.org> Date: Mon, 28 Nov 2005 16:19:52 -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: John Baldwin References: <43842D41.1050401@samsco.org> <002801c5f081$f01ff200$642a15ac@smiley> <20051124062711.GA15961@xor.obsecurity.org> <200511281626.33591.jhb@freebsd.org> In-Reply-To: <200511281626.33591.jhb@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Kris Kennaway , freebsd-current@freebsd.org, Darren Pilgrim Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 00:20:25 -0000 John Baldwin wrote: >On Thursday 24 November 2005 01:27 am, Kris Kennaway wrote: > > >>On Wed, Nov 23, 2005 at 03:02:05PM -0800, Darren Pilgrim wrote: >> >> >>>Until this gets "fixed" in FreeBSD, what should those of us who are >>>effectively stuck with this hardware do to avoid the problem? Does the >>>problem exist in RELENG_4? >>> >>> >>Yes, on the same machine I first mentioned. >> >> > >This is the first I've heard that the problem occurs on 4.x as well. :( > > As I said, I think it's hitting me on a dell 2850 running 4.10++ as well. and Matt is getting hit with it in dragonfly with 4.x roots. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 07:06: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 B316516A423 for ; Tue, 29 Nov 2005 07:06:14 +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 9052943D5A for ; Tue, 29 Nov 2005 07:06:11 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id 9EA5D5E48F4; Mon, 28 Nov 2005 23:06:06 -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 1E1DA5E48B0 for ; Mon, 28 Nov 2005 23:06:01 -0800 (PST) Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: current@freebsd.org From: Jason Evans Date: Mon, 28 Nov 2005 23:05:57 -0800 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: Subject: 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: Tue, 29 Nov 2005 07:06:14 -0000 There is a patch that contains a new libc malloc implementation at: http://www.canonware.com/~jasone/jemalloc/jemalloc_20051127a.diff This implementation is very different from the current libc malloc. Probably the most important difference is that this one is designed with threads and SMP in mind. The patch has been tested for stability quite a bit already, thanks mainly to Kris Kennaway. However, any help with performance testing would be greatly appreciated. Specifically, I'd like to know how well this malloc holds up to threaded workloads on SMP systems. If you have an application that relies on threads, please let me know how performance is affected. Naturally, if you notice horrible performance or ridiculous resident memory usage, that's a bad thing and I'd like to hear about it. Thanks, Jason === Important notes: * You need to do a full buildworld/installworld in order for the patch to work correctly, due to various integration issues with the threads libraries and rtld. * The virtual memory size of processes, as reported in the SIZE field by top, will appear astronomical for almost all processes (32+ MB). This is expected; it is merely an artifact of using large mmap()ed regions rather than sbrk(). * In keeping with the default option settings for CURRENT, the A and J flags are enabled by default. When conducting performance tests, specify MALLOC_OPTIONS="aj" . From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 08:13: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 6339B16A41F for ; Tue, 29 Nov 2005 08:13:30 +0000 (GMT) (envelope-from olivier@larkine.org) Received: from smtp4-g19.free.fr (smtp4-g19.free.fr [212.27.42.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 093E143D5F for ; Tue, 29 Nov 2005 08:13:29 +0000 (GMT) (envelope-from olivier@larkine.org) Received: from [192.168.1.29] (roa76-5-82-234-252-139.fbx.proxad.net [82.234.252.139]) by smtp4-g19.free.fr (Postfix) with ESMTP id 4492940046 for ; Tue, 29 Nov 2005 09:13:28 +0100 (CET) Message-ID: <438C0E1D.9000907@larkine.org> Date: Tue, 29 Nov 2005 09:15:25 +0100 From: Olivier Regnier User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: fr, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Acer Aspire 3002WLMI - DVDRW X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: olivier@larkine.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 08:13:30 -0000 Hello, I have a Aspire 3002WLMI laptop. I try to install FreeBSD 6.0 with my cd but i got the following error. The problem is the same with 5.4 and 5.3. Here is some info: % Here the message: % acd0: DVDR at ata1-master UDMA33 acd0: unknown transfer phase acd0: FAILURE - PREVENT_ALLOW timed out I can't install FreeBSD with my cd on my laptop but it works fine on my PC. I don't know what happened to my laptop. Regards, Olivier. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 10:52:08 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 C052616A41F for ; Tue, 29 Nov 2005 10:52:08 +0000 (GMT) (envelope-from hiten.pandya@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB15E43D5C for ; Tue, 29 Nov 2005 10:52:07 +0000 (GMT) (envelope-from hiten.pandya@gmail.com) Received: by wproxy.gmail.com with SMTP id i3so116367wra for ; Tue, 29 Nov 2005 02:52:07 -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=UmEPsPN6YeykpIVc1iF/9yufAOF0dEuhAC/LCGA/28c/KL2EzlwcerMBrrYBBx/2Hza+d1VX6ViKXvsV/0N0Ij2dXYF2TFJSZdRKxOAdXMn1J9ZnfYx34mq82pBBQxnQcIpvvQH5beGWSrONMAKODp5sgJg1OjPNh9s/St7hLrA= Received: by 10.65.159.5 with SMTP id l5mr2805808qbo; Tue, 29 Nov 2005 02:52:07 -0800 (PST) Received: by 10.65.203.19 with HTTP; Tue, 29 Nov 2005 02:52:07 -0800 (PST) Message-ID: <9b1858120511290252w1e6d3458m@mail.gmail.com> Date: Tue, 29 Nov 2005 10:52:07 +0000 From: Hiten Pandya To: Jason Evans In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: 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: Tue, 29 Nov 2005 10:52:08 -0000 Jason, I see that you have included an implementation of red-black tree CPP macros, but wouldn't it be better if you were to use the ones in ? I have only had a precursory look, but I would have thought that would be the way to go. Just a suggestion. Best regards, -- Hiten Pandya hmp at freebsd.org On 29/11/05, Jason Evans wrote: > There is a patch that contains a new libc malloc implementation at: > > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051127a.diff > > This implementation is very different from the current libc malloc. > Probably the most important difference is that this one is designed > with threads and SMP in mind. > > The patch has been tested for stability quite a bit already, thanks > mainly to Kris Kennaway. However, any help with performance testing > would be greatly appreciated. Specifically, I'd like to know how > well this malloc holds up to threaded workloads on SMP systems. If > you have an application that relies on threads, please let me know > how performance is affected. > > Naturally, if you notice horrible performance or ridiculous resident > memory usage, that's a bad thing and I'd like to hear about it. > > Thanks, > Jason > > =3D=3D=3D Important notes: > > * You need to do a full buildworld/installworld in order for the > patch to work correctly, due to various integration issues with the > threads libraries and rtld. > > * The virtual memory size of processes, as reported in the SIZE field > by top, will appear astronomical for almost all processes (32+ MB). > This is expected; it is merely an artifact of using large mmap()ed > regions rather than sbrk(). > > * In keeping with the default option settings for CURRENT, the A and > J flags are enabled by default. When conducting performance tests, > specify MALLOC_OPTIONS=3D"aj" . > From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 11:07:38 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 A7F0216A41F; Tue, 29 Nov 2005 11:07:38 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1D5043D53; Tue, 29 Nov 2005 11:07:37 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.2] (S0106000f3d63befd.vs.shawcable.net [70.71.19.119]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id jATB7VEw083667 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 12:07:33 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <438C3672.1010700@portaone.com> Date: Tue, 29 Nov 2005 03:07:30 -0800 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: phk@freebsd.org Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.86.2/1198/Tue Nov 29 11:05:20 2005 on www.portaone.com X-Virus-Status: Clean X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on www.portaone.com Cc: "current@freebsd.org" Subject: Correct usage of g_read_data() API X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Maxim.Sobolev@portaone.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 11:07:38 -0000 Hi Poul, After making a fix for geom_label (rev.1.4 of g_label_ntfs.c) I have decided to check if there are any other places which don't check return values of g_read_data(9). What I found however is that there are several different usage patterns, some of which rely on undocumented internal properties of the said API, particularly: --- 1 --- error = random(); data = g_read_data(..., &error); if (error != 0) handle_error(error); --------- --- 2 --- error = random(); data = g_read_data(..., &error); if (buf == NULL || error != 0) handle_error(error); --------- --- 3 --- error = random(); data = g_read_data(..., &error); if (buf == NULL) handle_error(error); --------- According to my reading of g_read_data(9) only (3) is valid, since both (1) and (2) assume that error will always be cleared on successful completion, while (1) also assumes that error will be set to non-zero value in all cases when error happens and (2) assumes that non-NULL value can be returned even on error. Therefore, either documentation should be extended to match implementation or usage of g_read_data() fixed in all places where it is incorrect. Please advise. -Maxim P.S. I can do the actual changes by myself, both to documentation and/or to code. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 11:42: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 5E62F16A41F for ; Tue, 29 Nov 2005 11:42:57 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from www.portaone.com (support.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B27043D5C for ; Tue, 29 Nov 2005 11:42:55 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.2] (S0106000f3d63befd.vs.shawcable.net [70.71.19.119]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id jATBbX8A088838 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Nov 2005 12:37:51 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <438C3D7C.3000704@portaone.com> Date: Tue, 29 Nov 2005 03:37:32 -0800 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Thunderbird 1.5 (Windows/20051025) MIME-Version: 1.0 To: Jason Evans References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.86.2/1198/Tue Nov 29 11:05:20 2005 on www.portaone.com X-Virus-Status: Clean X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.0 X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on www.portaone.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 Reply-To: Maxim.Sobolev@portaone.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 11:42:57 -0000 Just curious what is the grand plan for this work? I wonder if it will make sense to have two malloc's in the system, so that user can select one which better suits his needs. -Maxim Jason Evans wrote: > There is a patch that contains a new libc malloc implementation at: > > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051127a.diff > > This implementation is very different from the current libc malloc. > Probably the most important difference is that this one is designed with > threads and SMP in mind. > > The patch has been tested for stability quite a bit already, thanks > mainly to Kris Kennaway. However, any help with performance testing > would be greatly appreciated. Specifically, I'd like to know how well > this malloc holds up to threaded workloads on SMP systems. If you have > an application that relies on threads, please let me know how > performance is affected. > > Naturally, if you notice horrible performance or ridiculous resident > memory usage, that's a bad thing and I'd like to hear about it. > > Thanks, > Jason > > === Important notes: > > * You need to do a full buildworld/installworld in order for the patch > to work correctly, due to various integration issues with the threads > libraries and rtld. > > * The virtual memory size of processes, as reported in the SIZE field by > top, will appear astronomical for almost all processes (32+ MB). This > is expected; it is merely an artifact of using large mmap()ed regions > rather than sbrk(). > > * In keeping with the default option settings for CURRENT, the A and J > flags are enabled by default. When conducting performance tests, > specify MALLOC_OPTIONS="aj" . > > _______________________________________________ > 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 Nov 29 12:51:39 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 9E32D16A4DD for ; Tue, 29 Nov 2005 12:51:34 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from efacilitas.de (smtp.efacilitas.de [85.10.196.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5FF46440F5 for ; Tue, 29 Nov 2005 12:24:19 +0000 (GMT) (envelope-from bkoenig@cs.tu-berlin.de) Received: from eurystheus.local (port-212-202-37-121.dynamic.qsc.de [212.202.37.121]) by efacilitas.de (Postfix) with ESMTP id DF8BA4B199 for ; Tue, 29 Nov 2005 13:32:17 +0100 (CET) Received: from [192.168.1.2] (muhkuh.local [192.168.1.2]) by eurystheus.local (Postfix) with ESMTP id AD08A508AF for ; Tue, 29 Nov 2005 13:23:10 +0100 (CET) Message-ID: <438C487F.1090606@cs.tu-berlin.de> Date: Tue, 29 Nov 2005 13:24:31 +0100 From: =?ISO-8859-15?Q?Bj=F6rn_K=F6nig?= User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: de-DE, de, en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Cc: Subject: some manpage reference cleanups X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 12:51:39 -0000 Hello, there are some references to manpages that should be reviewed. slstat(8) refers to ststat(1) but means systat(1). This typo crept in nine years ago with version 1.4 of src/usr.sbin/slstat/slstat.8. da(4) refers two times to bsdlabel(5) which has been exempted some years ago. There is a reference to a manpage p1003_1b(9) in hier(7) that has never existed for the last six years. vinvalbuf(9) refers to brelse(9) and bremfree(9) but there are no such manpages for the last four years. Maybe somebody will write them in future. :) periodic.conf(5) refers to rdist(1) which was removed four years ago. In fact the whole paragraph concerning "daily_distfile_enable" is obsolete. intro(6) refers to dm(8) which was removed three years ago. ports(7) refers to pib(1) which probably means the program sysutils/pib from ports collection, but this port doesn't install a manpage. fixmount(8) refers to rmtab(5) but this manpage exist nowhere. Maybe you want to leave this untouched, because it's contributed. libarchive-formats(3) should refer to mkisofs(8) instead of mkisofs(1) vinum(8) is still referred by ccdconfig(8), ffsinfo(8), gconcat(8), gmirror(8), graid3(8), gstripe(8), growfs(8), newfs(8), ccd(4), vinum(4), tuning(7). I suppose we need a gvinum(8). There are some further references that you may want to remove or fix: - security(7) -> ksu(1) - kiconv(3) -> iconv(9) - mount_smbfs(8) -> nsmb(8) - device_set_driver(9) -> isa(4) - pam_opie(8) -> opiechallenge(3) - pf.conf(5) -> securelevel(7) Regards Björn From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 13:37: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 3929D16A41F; Tue, 29 Nov 2005 13:37:26 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECE4B43D49; Tue, 29 Nov 2005 13:37:24 +0000 (GMT) (envelope-from gavin.atkinson@ury.york.ac.uk) Received: from buffy.york.ac.uk (buffy-128.york.ac.uk [144.32.128.160]) by mail-gw1.york.ac.uk (8.12.10/8.12.10) with ESMTP id jATDbF5N009001; Tue, 29 Nov 2005 13:37:15 GMT Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.13.4/8.13.4) with ESMTP id jATDbF3Z046326; Tue, 29 Nov 2005 13:37:15 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) Received: (from ga9@localhost) by buffy.york.ac.uk (8.13.4/8.13.4/Submit) id jATDbE5b046325; Tue, 29 Nov 2005 13:37:15 GMT (envelope-from gavin.atkinson@ury.york.ac.uk) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin.atkinson@ury.york.ac.uk using -f From: Gavin Atkinson To: Martin Cracauer In-Reply-To: <20051128130516.A36114@cons.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> <1133196263.41553.54.camel@buffy.york.ac.uk> <20051128130516.A36114@cons.org> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 29 Nov 2005 13:37:14 +0000 Message-Id: <1133271434.46168.9.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin.atkinson@ury.york.ac.uk Cc: freebsd-current@freebsd.org, =?ISO-8859-1?Q?S=F8ren?= Schmidt 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, 29 Nov 2005 13:37:26 -0000 On Mon, 2005-11-28 at 13:05 -0500, Martin Cracauer wrote: > > Hmm, well that's promising. This is with: > > atapci1@pci0:7:0: class=0x010485 card=0x5348108e chip=0x005410de > > rev=0xf3 hdr=0x00 > > vendor = 'NVIDIA Corporation' > > device = 'nForce4 Serial ATA Controller' > > class = mass storage > > subclass = RAID > > > > I don't know if it makes any difference, but the board has on-board > > NVIDIA RAID, which I'm considerably less than impressed with. I'll > > build one of them without the on-board RAID support and see if > > hot-insert works. I don't have the logs (long story, but basically the > > RAID bios hosed my data) but I think it failed to notice the inserted > > disk, and was timing out while trying to select the channel when forced > > with an atacontrol reinit. > > Do not use this for safety/raid1. > > I have seen several reports that the NVidia software raid wipes out > the intact drive on warm boot when the machine reboots with one drive > bad. Seems to do a random pick which drive to mirror to which other. Thanks for confirming this - that is exactly the same behaviour as I have witnessed. I've even managed to lose data from the disks without any OS involvement, purely by using the RAID BIOS. I'm amazed how bad this controller is. > gmirror will do fine for raid1, and performs adequately (not as well > as Linux software raid1, but probably better than NVidia anyway). I've built one of the servers using native ataraid ("FreeBSD PseudoRAID"), which seems to work fine (except for the lack of hot-swap, which as I say, apparently doesn't work under any non-XP operating system anyway). Gavin From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 16:41:47 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 71C8716A420 for ; Tue, 29 Nov 2005 16:41:47 +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 AAB9343D73 for ; Tue, 29 Nov 2005 16:41:36 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id 2CC6B5E48F6; Tue, 29 Nov 2005 08:41:36 -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 ABF5E5E48EA; Tue, 29 Nov 2005 08:41:32 -0800 (PST) In-Reply-To: <9b1858120511290252w1e6d3458m@mail.gmail.com> References: <9b1858120511290252w1e6d3458m@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7AA89647-5ABE-43C9-8BB0-57E04D2F66A4@canonware.com> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Tue, 29 Nov 2005 08:41:11 -0800 To: Hiten Pandya 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: Tue, 29 Nov 2005 16:41:48 -0000 On Nov 29, 2005, at 2:52 AM, Hiten Pandya wrote: > I see that you have included an implementation of red-black tree CPP > macros, but wouldn't it be better if you were to use the ones in > ? I have only had a precursory look, but I would have > thought that would be the way to go. There is a feature missing from sys/tree.h that I need (rb_nsearch() in the patch), but you are right that it would probably be best to use sys/tree.h. I am going to work on adding RB_NFIND(), and will then try switching to sys/tree.h. Thanks, Jason From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 16:56:50 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 0A5F016A422 for ; Tue, 29 Nov 2005 16:56:50 +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 38F5C43D5A for ; Tue, 29 Nov 2005 16:55:40 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id D2D605E48B0; Tue, 29 Nov 2005 08:55:36 -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 1C9665E48B0; Tue, 29 Nov 2005 08:55:34 -0800 (PST) In-Reply-To: <438C3D7C.3000704@portaone.com> References: <438C3D7C.3000704@portaone.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <1A7D4B98-9474-42B6-8A21-4C9AB8582EC1@canonware.com> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Tue, 29 Nov 2005 08:55:13 -0800 To: Maxim.Sobolev@portaone.com 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: Tue, 29 Nov 2005 16:56:50 -0000 On Nov 29, 2005, at 3:37 AM, Maxim Sobolev wrote: > Just curious what is the grand plan for this work? I wonder if it > will make sense to have two malloc's in the system, so that user > can select one which better suits his needs. The plan for this work is to replace the current malloc, rather than augmenting it. There is a long history in Unix of using shared library tricks to override the system malloc, and the patch does not change the ability to do so. However, in my opinion, explicitly providing multiple implementations of malloc in the base OS misses the point of providing a general purpose memory allocator. The goal is to have a single implementation that works well for the vast majority of extant programs, and to allow applications to provide their own implementations when the general purpose allocator fails to perform adequately. phkmalloc did an excellent job in this capacity for quite some time, but now that we need to commonly support threaded programs on SMP systems, phkmalloc is being strained rather badly. This isn't an indication that we need multiple malloc implementations in the base OS; rather it indicates that the system malloc implementation needs to take into account constraints that did not exist when phkmalloc was designed. Jason From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 17:03: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 9539B16A41F; Tue, 29 Nov 2005 17:03:14 +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 302BD43D53; Tue, 29 Nov 2005 17:02:48 +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 jATH2huP065501; Tue, 29 Nov 2005 18:02:43 +0100 (CET) (envelope-from cracauer@schlepper.zs64.net) Received: (from cracauer@localhost) by schlepper.zs64.net (8.13.3/8.12.9/Submit) id jATH2hVo065500; Tue, 29 Nov 2005 12:02:43 -0500 (EST) (envelope-from cracauer) Date: Tue, 29 Nov 2005 12:02:43 -0500 From: Martin Cracauer To: Gavin Atkinson Message-ID: <20051129120243.B64864@cons.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> <1133196263.41553.54.camel@buffy.york.ac.uk> <20051128130516.A36114@cons.org> <1133271434.46168.9.camel@buffy.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <1133271434.46168.9.camel@buffy.york.ac.uk>; from gavin.atkinson@ury.york.ac.uk on Tue, Nov 29, 2005 at 01:37:14PM +0000 Cc: Martin Cracauer , freebsd-current@freebsd.org, =?iso-8859-1?Q?S=F8ren_Schmidt?= 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, 29 Nov 2005 17:03:14 -0000 Gavin Atkinson wrote on Tue, Nov 29, 2005 at 01:37:14PM +0000: > On Mon, 2005-11-28 at 13:05 -0500, Martin Cracauer wrote: > > > Hmm, well that's promising. This is with: > > > atapci1@pci0:7:0: class=0x010485 card=0x5348108e chip=0x005410de > > > rev=0xf3 hdr=0x00 > > > vendor = 'NVIDIA Corporation' > > > device = 'nForce4 Serial ATA Controller' > > > class = mass storage > > > subclass = RAID > > > > > > I don't know if it makes any difference, but the board has on-board > > > NVIDIA RAID, which I'm considerably less than impressed with. I'll > > > build one of them without the on-board RAID support and see if > > > hot-insert works. I don't have the logs (long story, but basically the > > > RAID bios hosed my data) but I think it failed to notice the inserted > > > disk, and was timing out while trying to select the channel when forced > > > with an atacontrol reinit. > > > > Do not use this for safety/raid1. > > > > I have seen several reports that the NVidia software raid wipes out > > the intact drive on warm boot when the machine reboots with one drive > > bad. Seems to do a random pick which drive to mirror to which other. > > Thanks for confirming this - that is exactly the same behaviour as I > have witnessed. I've even managed to lose data from the disks without > any OS involvement, purely by using the RAID BIOS. I'm amazed how bad > this controller is. Just to make that clear: the controller works well (well, no NCQ), it is just the BIOS support for the pseudo-hardware RAID on top that is -uh- questionable. 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 Tue Nov 29 17:30: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 AA12916A41F for ; Tue, 29 Nov 2005 17:30:40 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3AA5D43D76 for ; Tue, 29 Nov 2005 17:30:25 +0000 (GMT) (envelope-from dunstan@freebsd.czest.pl) Received: from freebsd.czest.pl (freebsd.czest.pl [80.48.250.4]) by freebsd.czest.pl (8.12.10/8.12.9) with ESMTP id jATHW5Px037894; Tue, 29 Nov 2005 17:32:05 GMT (envelope-from dunstan@freebsd.czest.pl) Received: (from dunstan@localhost) by freebsd.czest.pl (8.13.4/8.12.9/Submit) id jATHW504037893; Tue, 29 Nov 2005 17:32:05 GMT (envelope-from dunstan) Date: Tue, 29 Nov 2005 17:32:05 +0000 From: "Wojciech A. Koszek" To: Scot Hetzel Message-ID: <20051129173205.GA37877@freebsd.czest.pl> References: <20051121162544.GB94958@freebsd.czest.pl> <790a9fff0511250903q931b66cte7a3e6555dc38f83@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <790a9fff0511250903q931b66cte7a3e6555dc38f83@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: Linking basesystem with additional libraries. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 17:30:40 -0000 On Fri, Nov 25, 2005 at 11:03:42AM -0600, Scot Hetzel wrote: > On 11/21/05, Wojciech A. Koszek wrote: > > Hello, > > > > Is there any reason why we couldn't have LDADD honored in "buildworld" > > process? If there are no negative implications, I volunteer to do the > > work. I'd find it really useful. > > > What do you want to link the base system with? > > Currently, the base sendmail can be linked with the > security/cyrus-sasl* ports by setting: > > # SENDMAIL_CFLAGS=-I/usr/local/include -DSASL2 > # SENDMAIL_LDFLAGS=-L/usr/local/lib > # SENDMAIL_LDADD=-lsasl2 > > in /etc/make.conf. You could possibly link sendmail with one of the > openldap ports also. Haven't tried it myself yet. > > Note: This may cause a busted sendmail, especially during a major > version upgrade. A rebuild of the security/cyrus-sasl* port, and > sendmail will fix it. Hello, Sorry for late response. Truly speaking I want to use this functionality to link basesystem with alternative malloc(9) implementation, just like this from libefence. This is how I discovered one of the allocation problems in FreeBSD basesystem. Doing this kind of tests does not work in some cases when LD_* variables are used. Looking at recent posts, I think new malloc implementation (patch posted by Jason Evans) could also be tested in this way. I also use SENDMAIL_* macros and although difficulties you've written about, choice. I think it's advantage to have them. And please note, that it's system administrator choice to play with custom libraries. -- * Wojciech A. Koszek && dunstan@FreeBSD.czest.pl From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 18:37: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 72CC016A424 for ; Tue, 29 Nov 2005 18:37:07 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD58243D5E for ; Tue, 29 Nov 2005 18:37:06 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jATIb5J18991 for ; Tue, 29 Nov 2005 13:37:05 -0500 Message-ID: <438C9FCF.7080405@savvis.net> Date: Tue, 29 Nov 2005 10:37:03 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) 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: problems with -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, 29 Nov 2005 18:37:07 -0000 dear hackers, after cvsup'ing recent current (as of yesterday evening pst) and building/installing new kernel/world i started having problems: problem 1: startx simply reboots my laptop. i can see x coming up, then after just a few seconds my laptop reboots. no window manager, no nothing. my laptop is a dell with some radeon video card. will provide more details on request. problem 2: when system is booted and filesystem is not clean fsck is started and checks all dirty filesystems. then boot process continues as usual, however root filesystem is still mounted read-only, i.e. ---> /dev/ad0s1a on / (ufs, local, read-only) <--- devfs on /dev (devfs, local) /dev/ad0s1d on /tmp (ufs, local, soft-updates) /dev/ad0s1f on /usr (ufs, local, soft-updates) /dev/ad0s1e on /var (ufs, local, soft-updates) linprocfs on /usr/compat/linux/proc (linprocfs, local) devfs on /var/named/dev (devfs, local) so, anyone sees this as well or its just me. thanks, max From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 19:14: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 B2AEF16A420 for ; Tue, 29 Nov 2005 19:14:06 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.FreeBSD.org (Postfix) with ESMTP id DDCDD43D67 for ; Tue, 29 Nov 2005 19:14:04 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.48.2]) by phk.freebsd.dk (Postfix) with ESMTP id 0DC55BC50; Tue, 29 Nov 2005 19:14:01 +0000 (UTC) To: Jason Evans From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 29 Nov 2005 08:55:13 PST." <1A7D4B98-9474-42B6-8A21-4C9AB8582EC1@canonware.com> Date: Tue, 29 Nov 2005 20:14:00 +0100 Message-ID: <3340.1133291640@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Maxim.Sobolev@portaone.com, 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: Tue, 29 Nov 2005 19:14:06 -0000 In message <1A7D4B98-9474-42B6-8A21-4C9AB8582EC1@canonware.com>, Jason Evans wr ites: >[...] phkmalloc did an excellent job in this capacity >for quite some time, but now that we need to commonly support >threaded programs on SMP systems, phkmalloc is being strained rather >badly. This isn't an indication that we need multiple malloc >implementations in the base OS; rather it indicates that the system >malloc implementation needs to take into account constraints that did >not exist when phkmalloc was designed. The malloc phkmalloc replaced was written at some point in the 1980ies on a VAX, and more or less assumed the Vax was effectively a single user machine and without effective paging algorithms. Phkmalloc was written in 1994/5 where I had 4MB of RAM in my "Gateway Handbook 486" and very strongly assumed that with the RAM prices of the day, I could not afford an upgrade. I gave a talk about phkmalloc at USENIX ATC 1998 in New Orleans. One of the central points in the talk was that infrastructure code should have regular service overhauls, to check that the assumptions in the design is still valid. In addition to assumptions phkmalloc makes which are no longer relevant, there are many assumptions which should be made today which phkmalloc is not aware of, multi-threading being but one of them. Cache line effects, pipeline prefetching, multi-cpu systems, different VM system algorithms, larger address spaces etc etc etc. Once Jason is done, I have no doubts that "jemalloc" will beat phkalloc in all relevant benchmarking thereby neatly rendering any discussion about having multiple mallocs in the tree pointless. A big thank you from the author of phkmalloc to Jason for following the service manual to the letter :-) Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 19:41:05 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 513DA16A41F for ; Tue, 29 Nov 2005 19:41:05 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9690343D95 for ; Tue, 29 Nov 2005 19:40:53 +0000 (GMT) (envelope-from shoesoft@gmx.net) Received: (qmail invoked by alias); 29 Nov 2005 19:40:43 -0000 Received: from h081217094006.dyn.cm.kabsi.at (EHLO h081217094006.dyn.cm.kabsi.at) [81.217.94.6] by mail.gmx.net (mp019) with SMTP; 29 Nov 2005 20:40:43 +0100 X-Authenticated: #16703784 From: Stefan Ehmann To: Maksim Yevmenkin In-Reply-To: <438C9FCF.7080405@savvis.net> References: <438C9FCF.7080405@savvis.net> Content-Type: text/plain Date: Tue, 29 Nov 2005 20:40:06 +0100 Message-Id: <1133293206.1392.6.camel@taxman.pepperland> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org Subject: Re: problems with -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, 29 Nov 2005 19:41:05 -0000 On Tue, 2005-11-29 at 10:37 -0800, Maksim Yevmenkin wrote: > dear hackers, > > after cvsup'ing recent current (as of yesterday evening pst) and > building/installing new kernel/world i started having problems: > > problem 1: startx simply reboots my laptop. i can see x coming up, then > after just a few seconds my laptop reboots. no window manager, no > nothing. my laptop is a dell with some radeon video card. will provide > more details on request. > > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues as > usual, however root filesystem is still mounted read-only, i.e. I've seen the problem with the ro-only / fs too. I can't get it to mount rw manually either - only rebooting helps. I remember seeing some changes to mount some days ago, I guess they cause this. CVS log says: Remove UFS-specific parts from mount(8). For mounting UFS, all mount options are passed directly to nmount(), without any UFS-specific logic. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 19:53: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 495B116A420 for ; Tue, 29 Nov 2005 19:53:06 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76E6143D5D for ; Tue, 29 Nov 2005 19:53:05 +0000 (GMT) (envelope-from rainer.alves@gmail.com) Received: by zproxy.gmail.com with SMTP id q3so213290nzb for ; Tue, 29 Nov 2005 11:53:04 -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=aTN/qis/iCzVD3bzuz2NU93kVR1/Xbwkh08GZuaQvWi0XLEFrKcTaMG9iPjii6LBilVPRMl50nrcz50yp0rbaTg41HmGTngd6Im8Ha41QjLPSmAMIpffkxgiTlzppC02kZqi7X9wUhZUrlNqXKi+F2Vj7QDQF2kC/mVYRfrmeVc= Received: by 10.65.239.12 with SMTP id q12mr7118594qbr; Tue, 29 Nov 2005 11:53:04 -0800 (PST) Received: by 10.65.148.19 with HTTP; Tue, 29 Nov 2005 11:53:04 -0800 (PST) Message-ID: Date: Tue, 29 Nov 2005 16:53:04 -0300 From: Rainer Alves To: Maksim Yevmenkin In-Reply-To: <438C9FCF.7080405@savvis.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <438C9FCF.7080405@savvis.net> Cc: freebsd-current@freebsd.org Subject: Re: problems with -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, 29 Nov 2005 19:53:06 -0000 On 11/29/05, Maksim Yevmenkin wrote: > dear hackers, > > after cvsup'ing recent current (as of yesterday evening pst) and > building/installing new kernel/world i started having problems: > > problem 1: startx simply reboots my laptop. i can see x coming up, then > after just a few seconds my laptop reboots. no window manager, no > nothing. my laptop is a dell with some radeon video card. will provide > more details on request. > > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues as > usual, however root filesystem is still mounted read-only, i.e. > > ---> /dev/ad0s1a on / (ufs, local, read-only) <--- > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > devfs on /var/named/dev (devfs, local) > > so, anyone sees this as well or its just me. > > thanks, > max > Same thing here.. it's probably related to the huge DRM changes commited yesterday by anholt@. I'll try to enable some debugging stuff and see what's going on... -- Rainer From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 19:57:33 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 4457016A41F for ; Tue, 29 Nov 2005 19:57:33 +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 8062F43D62 for ; Tue, 29 Nov 2005 19:57:17 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EhBXi-0001dJ-6L for freebsd-current@freebsd.org; Tue, 29 Nov 2005 20:53:34 +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 ; Tue, 29 Nov 2005 20:53:34 +0100 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 29 Nov 2005 20:53:34 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Tue, 29 Nov 2005 11:51:20 -0800 Lines: 39 Message-ID: References: <438C9FCF.7080405@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en In-Reply-To: <438C9FCF.7080405@savvis.net> Sender: news Subject: Re: problems with -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, 29 Nov 2005 19:57:33 -0000 Maksim Yevmenkin wrote: > dear hackers, > > after cvsup'ing recent current (as of yesterday evening pst) and > building/installing new kernel/world i started having problems: > > problem 1: startx simply reboots my laptop. i can see x coming up, then > after just a few seconds my laptop reboots. no window manager, no > nothing. my laptop is a dell with some radeon video card. will provide > more details on request. I cvsup'd this morning and build/installed. But it didn't go so well. I see this as well, on my desktop (also a dell but with a intel graphics chipset. I note that I can do Xorg -config /etc/X11/xorg.conf and exit out (ctrl-alt-backspace). If I change my windows manager in .xinitrc to exec twm. I can open and close a few xterms just fine, but if I ctrl-alt-backspace out the machine will reboot. > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues as > usual, however root filesystem is still mounted read-only, i.e. > > ---> /dev/ad0s1a on / (ufs, local, read-only) <--- > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > devfs on /var/named/dev (devfs, local) > > so, anyone sees this as well or its just me. mount options are broken it seems. -o rw, which is what everyone here uses, no longer works. Only -w -u / seems to work. Then again sometimes that doesn't and it will complain about the ad0s1a device being invalid. -Mark From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 20:01: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 22C3716A41F for ; Tue, 29 Nov 2005 20:01:11 +0000 (GMT) (envelope-from rnoland@2hip.net) Received: from mailserver1.internap.com (mailserver1.internap.com [63.251.68.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BC1D43D8B for ; Tue, 29 Nov 2005 20:01:05 +0000 (GMT) (envelope-from rnoland@2hip.net) Received: from [63.251.67.32] (account rnoland@mail.internap.com HELO bbeng-laptop.acs.internap.com) by mailserver1.internap.com (CommuniGate Pro SMTP 4.2.10) with ESMTP-TLS id 56088936; Tue, 29 Nov 2005 15:01:04 -0500 From: "Robert C. Noland III" To: Maksim Yevmenkin In-Reply-To: <438C9FCF.7080405@savvis.net> References: <438C9FCF.7080405@savvis.net> Content-Type: text/plain Organization: 2 Hip Networks Date: Tue, 29 Nov 2005 15:00:49 -0500 Message-Id: <1133294449.985.6.camel@bbeng-laptop.acs.internap.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: problems with -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, 29 Nov 2005 20:01:11 -0000 On Tue, 2005-11-29 at 10:37 -0800, Maksim Yevmenkin wrote: > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues > as > usual, however root filesystem is still mounted read-only, i.e. > > ---> /dev/ad0s1a on / (ufs, local, read-only) <--- > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > devfs on /var/named/dev (devfs, local) > > so, anyone sees this as well or its just me. I have also seen this issue. The machine in question wasn't running X. I am not convinced that the panics (trap 12: page faults) were not somehow hardware related, but the results after the panics were as you described. robert. From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 20:06: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 36F0A16A41F for ; Tue, 29 Nov 2005 20:06:43 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D691043D69 for ; Tue, 29 Nov 2005 20:06:42 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id E6336E8AC; Tue, 29 Nov 2005 12:06:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by regurgitate.ugcs.caltech.edu (Postfix) with ESMTP id DC2C0E8AB; Tue, 29 Nov 2005 12:06:39 -0800 (PST) Date: Tue, 29 Nov 2005 12:06:39 -0800 (PST) From: Jon Dama To: Jason Evans In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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: Tue, 29 Nov 2005 20:06:43 -0000 I have a rather strong objection to make to this proposal (read: if this change goes in I'm going to have to go through the effort of ripping it out locally...): There exists a problem right now--localized to i386 and any other arch based on 32-bit pointers: address space is simply too scarce. Your decision to switch to using mmap as the exclusive source of malloc buckets is admirable for its modernity but it simply cannot stand unless someone steps up to change the way mmap and brk interact within the kernel. The trouble arises from the need to set MAXDSIZ and the resulting effect it has in determining the start of the mmap region--which I might add is the location that the shared library loader is placed. This effectively (and explicitly) sets the limit for how large of a contiguous region can be allocated with brk. What you've done by switching the system malloc to exclusively using mmap is induced a lot of motivation on the part of the sysadmin to push that brk/mmap boundary down. This wouldn't be a problem except that you've effectively shot in the foot dozens of alternative c malloc implementations, not to mention the memory allocator routines used in obscure languages such as Modula-3 and Haskell that rely on brk derived buckets. This isn't playing very nicely! I looked into the issues and limitations with phkmalloc several months ago and concluded that simply adopting ptmalloc2 (the linux malloc) was the better approach--notably it is willing to draw from both brk and mmap, and it also implements per-thread arenas. There is also cause for concern about your "cache-line" business. Simply on the face of it there is the problem that the scheduler does not do a good job of pinning threads to individual CPUs. The threads are already bounding from cpu to cpu and thrashing (really thrashing) each CPU cache along the way. Second, you've forgotten that there is a layer of indirection between your address space and the cache: the mapping of logical pages (what you can see in userspace) to physical pages (the addresses of which actually matter for the purposes of the cache). I don't recall off-hand whether or not the L1 cache on i386 is based on tags of the virtual addresses, but I am certain that the L2 and L3 caches tag the physical addresses not the virtual addresses. This means that your careful address selection based on cache-lines will only work out if it is done in the vm codepath: remember the mapping of physical addresses to the virtual addresses that come back from mmap can be delayed arbitrarily long into the future depending on when the program actually goes to touch that memory. Furthermore, the answer may vary depending on the architecture or even the processor version. -Jon On Mon, 28 Nov 2005, Jason Evans wrote: > There is a patch that contains a new libc malloc implementation at: > > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051127a.diff > > This implementation is very different from the current libc malloc. > Probably the most important difference is that this one is designed > with threads and SMP in mind. > > The patch has been tested for stability quite a bit already, thanks > mainly to Kris Kennaway. However, any help with performance testing > would be greatly appreciated. Specifically, I'd like to know how > well this malloc holds up to threaded workloads on SMP systems. If > you have an application that relies on threads, please let me know > how performance is affected. > > Naturally, if you notice horrible performance or ridiculous resident > memory usage, that's a bad thing and I'd like to hear about it. > > Thanks, > Jason > > === Important notes: > > * You need to do a full buildworld/installworld in order for the > patch to work correctly, due to various integration issues with the > threads libraries and rtld. > > * The virtual memory size of processes, as reported in the SIZE field > by top, will appear astronomical for almost all processes (32+ MB). > This is expected; it is merely an artifact of using large mmap()ed > regions rather than sbrk(). > > * In keeping with the default option settings for CURRENT, the A and > J flags are enabled by default. When conducting performance tests, > specify MALLOC_OPTIONS="aj" . > > _______________________________________________ > 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 Nov 29 20:16:57 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 59CD516A41F for ; Tue, 29 Nov 2005 20:16:57 +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 80F8443D68 for ; Tue, 29 Nov 2005 20:16:41 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EhBqL-0003n9-12 for freebsd-current@freebsd.org; Tue, 29 Nov 2005 21:12:49 +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 ; Tue, 29 Nov 2005 21:12:49 +0100 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 29 Nov 2005 21:12:49 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Tue, 29 Nov 2005 12:08:56 -0800 Lines: 45 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en Sender: news Subject: LOR: so_snd @ /usr/src/sys/kern/uipc_coket.c:780 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 20:16:57 -0000 this one seems new, and doesn't seem to match anything on the known list. Typed by hand. Single processor, no hyperthreading. The last thing it was doing was doing a 'test' command on a file over nfs. Lock order reversal: 1st 0xc5ef0ec so_snd (so_snd) @ /usr/src/sys/kern/uipc_socket.c:780 2nd 0xc0ac15ec tcp (tcp) @ /usr/src/sys/netinet/tcp_usrreq.c:580 KDB: stack backstrace: kdb_backtrace() at kdb_backtrace+0x2e witness_checkorder() at witness_checkorder+0x6d3 _mtx_lock_flags() at _mtx_lock_flags+0x8a tcp_usr_shutdown() at tcp_usr_shutdown+0x3d soshutdown() at soshutdown+0x41 nfs_disconnect() at nfs_disconnect+0xd5 nfs_reconnect() at nfs_reconnect+0x1c nfs_reply() at nfs_reply+0x170 nfs_request() at nfs_request+0x451 nfs3_access_otw() at nfs3_access_otw+0xde nfs_access() at nfs_access+0x120 VOP_ACCESS_APV() at VOP_ACCESS_APV+0xac nfs_lookup() at nfs_lookup+0xe5 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xb4 lookup() at lookup+0x468 namei() at namei+0x468 kern_stat() at kern_stat+0x3d stat() at stat+0x2f syscall() at Xint0x80_syscall+0x1f --- syscall (188, FreeBSD ELF32, stat, eip = 0x2819ad63, esp = 0xbfbfe8cc, ebp = 0xbfbfe9c8 --- panic: _mtx_lock_sleep: recursed on non-recursive mutex so_snd @ /usr/src/sys/kern/uipc_socket.c:391 cpuid = 0 KDB: enter: panic Stopped at kdb_enter+0x30: leave db> db> show alllocks Process 54517 (sh) thread 0xc5f1fd80 (100100) exclusive sleep mutex so_snd r = 0 (0xc5aef0ec) locked @ /usr/src/sys/kern/uipc_socket.c:780 exclusive sleep mutex Giant r = 0 (0xc0a713c0) locked @ /usr/src/sys/kern/vfs_lookup.c:619 Process 54515 (cc1) thread 0xc5eac600 (100093) exclusive sx user map r = 0 (0xc5fa2170) locked @ /usr/src/sys/vm/vm_map:2996 From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 20:51: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 B0CEA16A41F for ; Tue, 29 Nov 2005 20:51:12 +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 D020E43D67 for ; Tue, 29 Nov 2005 20:51:11 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1EhCNl-0005ku-DK for freebsd-current@freebsd.org; Tue, 29 Nov 2005 21:47:21 +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 ; Tue, 29 Nov 2005 21:47:21 +0100 Received: from atkin901 by gw205.f5.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 29 Nov 2005 21:47:21 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Mark Atkinson Date: Tue, 29 Nov 2005 12:44:57 -0800 Lines: 54 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: gw205.f5.com User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en In-Reply-To: Sender: news Subject: Re: LOR: so_snd @ /usr/src/sys/kern/uipc_socket.c:780 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 20:51:12 -0000 Sorry about fat-fingering the title. -current build from this morning. Mark Atkinson wrote: > this one seems new, and doesn't seem to match anything on the known > list. Typed by hand. Single processor, no hyperthreading. The last > thing it was doing was doing a 'test' command on a file over nfs. > > Lock order reversal: > 1st 0xc5ef0ec so_snd (so_snd) @ /usr/src/sys/kern/uipc_socket.c:780 > 2nd 0xc0ac15ec tcp (tcp) @ /usr/src/sys/netinet/tcp_usrreq.c:580 > KDB: stack backstrace: > kdb_backtrace() at kdb_backtrace+0x2e > witness_checkorder() at witness_checkorder+0x6d3 > _mtx_lock_flags() at _mtx_lock_flags+0x8a > tcp_usr_shutdown() at tcp_usr_shutdown+0x3d > soshutdown() at soshutdown+0x41 > nfs_disconnect() at nfs_disconnect+0xd5 > nfs_reconnect() at nfs_reconnect+0x1c > nfs_reply() at nfs_reply+0x170 > nfs_request() at nfs_request+0x451 > nfs3_access_otw() at nfs3_access_otw+0xde > nfs_access() at nfs_access+0x120 > VOP_ACCESS_APV() at VOP_ACCESS_APV+0xac > nfs_lookup() at nfs_lookup+0xe5 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xb4 > lookup() at lookup+0x468 > namei() at namei+0x468 > kern_stat() at kern_stat+0x3d > stat() at stat+0x2f > syscall() at Xint0x80_syscall+0x1f > --- syscall (188, FreeBSD ELF32, stat, eip = 0x2819ad63, esp = > 0xbfbfe8cc, ebp = 0xbfbfe9c8 --- > panic: _mtx_lock_sleep: recursed on non-recursive mutex so_snd @ > /usr/src/sys/kern/uipc_socket.c:391 > > cpuid = 0 > KDB: enter: panic > Stopped at kdb_enter+0x30: leave > db> > db> show alllocks > Process 54517 (sh) thread 0xc5f1fd80 (100100) > exclusive sleep mutex so_snd r = 0 (0xc5aef0ec) locked @ > /usr/src/sys/kern/uipc_socket.c:780 > exclusive sleep mutex Giant r = 0 (0xc0a713c0) locked @ > /usr/src/sys/kern/vfs_lookup.c:619 > Process 54515 (cc1) thread 0xc5eac600 (100093) > exclusive sx user map r = 0 (0xc5fa2170) locked @ > /usr/src/sys/vm/vm_map:2996 > > _______________________________________________ > 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 Nov 29 20:58: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 01CF816A434 for ; Tue, 29 Nov 2005 20:58:22 +0000 (GMT) (envelope-from pete@altadena.net) Received: from gooney.altadena.net (gooney.altadena.net [207.215.170.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC50D43E5E for ; Tue, 29 Nov 2005 20:56:05 +0000 (GMT) (envelope-from pete@altadena.net) Received: from nat-gw.home.altadena.net ([66.127.158.99] helo=[192.168.169.28]) by gooney.altadena.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.54) id 1EhCVE-000B1C-78 for current@freebsd.org; Tue, 29 Nov 2005 12:55:04 -0800 Message-ID: <438CC026.9080908@altadena.net> Date: Tue, 29 Nov 2005 12:55:02 -0800 From: Pete Carah Organization: Altadena Internet Communications User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050921) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <438C9FCF.7080405@savvis.net> In-Reply-To: <438C9FCF.7080405@savvis.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: problems with -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, 29 Nov 2005 20:58:23 -0000 Maksim Yevmenkin wrote: > dear hackers, > > after cvsup'ing recent current (as of yesterday evening pst) and > building/installing new kernel/world i started having problems: > > problem 1: startx simply reboots my laptop. i can see x coming up, then > after just a few seconds my laptop reboots. no window manager, no > nothing. my laptop is a dell with some radeon video card. will provide > more details on request. On mine (I865 integrated controller) the system hangs on startx; I did see one panic but couldn't tell what it was since system booted directly from graphics mode. > > problem 2: when system is booted and filesystem is not clean fsck is > started and checks all dirty filesystems. then boot process continues as > usual, however root filesystem is still mounted read-only, i.e. > > ---> /dev/ad0s1a on / (ufs, local, read-only) <--- > devfs on /dev (devfs, local) > /dev/ad0s1d on /tmp (ufs, local, soft-updates) > /dev/ad0s1f on /usr (ufs, local, soft-updates) > /dev/ad0s1e on /var (ufs, local, soft-updates) > linprocfs on /usr/compat/linux/proc (linprocfs, local) > devfs on /var/named/dev (devfs, local) The RW update happens right if there was no fsck, but fails if there was one. This goes back to the pre-mid-1990's thing about doing an immediate reboot after any fsck... In addition, there was an API change that didn't make it into UPDATING: if mount(8) and friends (mount_*) are recompiled and tried with an old kernel, NOTHING related to mount options seems to work; the interface for options changed. (this has happened slowly; mount_msdos picked up the change last week sometime but ufs only recently). Made things so that I couldn't use noauto since it got presented to the driver which rejected the mount. Not serious for usb drives since all it does with msdosfs is not mount anyhow, and not hang the boot or drop into single-user. BUT this kind of change is supposed to go into UPDATING *BEFORE COMMIT*, since it requires sync between userland and kernel. Not to speak of apparently not being finished!!!! > > so, anyone sees this as well or its just me. Yes. -- Pete From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 21:00: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 E26FB16A428 for ; Tue, 29 Nov 2005 21:00:04 +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 8794643E41 for ; Tue, 29 Nov 2005 20:58:02 +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 0FF1A1FFACA; Tue, 29 Nov 2005 21:57:59 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 650731FF9AC; Tue, 29 Nov 2005 21:57:56 +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 3355D444F6B; Tue, 29 Nov 2005 20:52:20 +0000 (UTC) Date: Tue, 29 Nov 2005 20:52:20 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Mark Atkinson In-Reply-To: Message-ID: <20051129205137.M23990@maildrop.int.zabbadoz.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Cc: freebsd-current@freebsd.org Subject: Re: LOR: so_snd @ /usr/src/sys/kern/uipc_coket.c:780 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 21:00:05 -0000 On Tue, 29 Nov 2005, Mark Atkinson wrote: > this one seems new, and doesn't seem to match anything on the known list. > Typed by hand. Single processor, no hyperthreading. The last thing it was > doing was doing a 'test' command on a file over nfs. > > Lock order reversal: > 1st 0xc5ef0ec so_snd (so_snd) @ /usr/src/sys/kern/uipc_socket.c:780 > 2nd 0xc0ac15ec tcp (tcp) @ /usr/src/sys/netinet/tcp_usrreq.c:580 I added this to the LOR page with ID 173: http://sources.zabbadoz.net/freebsd/lor.html#173 -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 21:08: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 1166716A424 for ; Tue, 29 Nov 2005 21:08:55 +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 790B043D72 for ; Tue, 29 Nov 2005 21:08:41 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id DBDB55E4891; Tue, 29 Nov 2005 13:07:43 -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 CF5035E4891; Tue, 29 Nov 2005 13:07:35 -0800 (PST) In-Reply-To: References: 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: Tue, 29 Nov 2005 13:07:06 -0800 To: Jon Dama 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: Tue, 29 Nov 2005 21:08:55 -0000 Jon, Thanks for your comments. Fortunately, I don't think things are quite as hopeless as you think, though you may be right that some adjustments are necessary. Specific replies follow. On Nov 29, 2005, at 12:06 PM, Jon Dama wrote: > There exists a problem right now--localized to i386 and any other arch > based on 32-bit pointers: address space is simply too scarce. > > Your decision to switch to using mmap as the exclusive source of > malloc > buckets is admirable for its modernity but it simply cannot stand > unless > someone steps up to change the way mmap and brk interact within the > kernel. > > The trouble arises from the need to set MAXDSIZ and the resulting > effect > it has in determining the start of the mmap region--which I might > add is > the location that the shared library loader is placed. This > effectively > (and explicitly) sets the limit for how large of a contiguous > region can > be allocated with brk. > > What you've done by switching the system malloc to exclusively using > mmap is induced a lot of motivation on the part of the sysadmin to > push > that brk/mmap boundary down. > > This wouldn't be a problem except that you've effectively shot in > the foot > dozens of alternative c malloc implementations, not to mention the > memory > allocator routines used in obscure languages such as Modula-3 and > Haskell > that rely on brk derived buckets. > > This isn't playing very nicely! Where should MAXDSIZ be? Given scarce address space, the best we can hope for is setting it to the "least bad" default, as measured by what programs we care about do. No matter what we do, some programs lose. That said, it turns out that adding the ability to allocate via brk isn't hard. The code already contains the logic to recycle address ranges, in order to reduce mmap system call overhead. All of the locking infrastructure is also already in place. The only necessary modifications are 1) explicit use of brk until all data segment space is consumed, 2) special case code for addresses in the brk range, so that madvise() is used instead of munmap(), and 3) preferential re- use of the brk address space over mmap'ed memory. Do you agree that there is no need for using brk on 64-bit systems? > I looked into the issues and limitations with phkmalloc several > months ago > and concluded that simply adopting ptmalloc2 (the linux malloc) was > the > better approach--notably it is willing to draw from both brk and > mmap, and > it also implements per-thread arenas. ptmalloc takes a different approach to per-thread arenas that has been shown in multiple papers to not scale as well as the approach I took. The difference isn't significant until you get to 8+ CPUs, but we already have systems running with enough CPUs that this is an issue. > There is also cause for concern about your "cache-line" business. > Simply > on the face of it there is the problem that the scheduler does not > do a > good job of pinning threads to individual CPUs. The threads are > already > bounding from cpu to cpu and thrashing (really thrashing) each CPU > cache > along the way. > > Second, you've forgotten that there is a layer of indirection > between your > address space and the cache: the mapping of logical pages (what you > can > see in userspace) to physical pages (the addresses of which actually > matter for the purposes of the cache). I don't recall off-hand > whether or > not the L1 cache on i386 is based on tags of the virtual addresses, > but I > am certain that the L2 and L3 caches tag the physical addresses not > the > virtual addresses. > > This means that your careful address selection based on cache-lines > will > only work out if it is done in the vm codepath: remember the > mapping of > physical addresses to the virtual addresses that come back from > mmap can > be delayed arbitrarily long into the future depending on when the > program > actually goes to touch that memory. > > Furthermore, the answer may vary depending on the architecture or > even the > processor version. I don't think you understand the intent for the "cache-line business". There is only one intention: avoid storing data structures in the same cache line if they are likely to be accessed simultaneously by multiple threads. For example, if two independent structures are stored right next to each other, although they do not require synchronization protection from each other, the hardware will send a cache line invalidation message to other CPUs every time anything in the cache line is modified. This means horrible cache performance if the data are modified often. As a particular example, there are per-arena data structures that are modified quite often (arena_t). If two arenas were right next to each other, then they could share a cache line, and performance would potentially be severly impacted. |---arena_t---|---arena_t---| | | | | | | | | ^^^ BAD! Thanks, Jason From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 21:29: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 E301716A426 for ; Tue, 29 Nov 2005 21:29: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 B32DB43D53 for ; Tue, 29 Nov 2005 21:29:09 +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 2827616 for multiple; Tue, 29 Nov 2005 16:28:54 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jATLSuFW074701; Tue, 29 Nov 2005 16:29:01 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 29 Nov 2005 16:29:07 -0500 User-Agent: KMail/1.8.2 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511291629.09069.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: Mark Atkinson Subject: Re: LOR: so_snd @ /usr/src/sys/kern/uipc_coket.c:780 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 21:29:46 -0000 On Tuesday 29 November 2005 03:08 pm, Mark Atkinson wrote: > this one seems new, and doesn't seem to match anything on the known > list. Typed by hand. Single processor, no hyperthreading. The last > thing it was doing was doing a 'test' command on a file over nfs. > > Lock order reversal: > 1st 0xc5ef0ec so_snd (so_snd) @ /usr/src/sys/kern/uipc_socket.c:780 > 2nd 0xc0ac15ec tcp (tcp) @ /usr/src/sys/netinet/tcp_usrreq.c:580 > KDB: stack backstrace: > kdb_backtrace() at kdb_backtrace+0x2e > witness_checkorder() at witness_checkorder+0x6d3 > _mtx_lock_flags() at _mtx_lock_flags+0x8a > tcp_usr_shutdown() at tcp_usr_shutdown+0x3d > soshutdown() at soshutdown+0x41 > nfs_disconnect() at nfs_disconnect+0xd5 > nfs_reconnect() at nfs_reconnect+0x1c > nfs_reply() at nfs_reply+0x170 > nfs_request() at nfs_request+0x451 > nfs3_access_otw() at nfs3_access_otw+0xde > nfs_access() at nfs_access+0x120 > VOP_ACCESS_APV() at VOP_ACCESS_APV+0xac > nfs_lookup() at nfs_lookup+0xe5 > VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0xb4 > lookup() at lookup+0x468 > namei() at namei+0x468 > kern_stat() at kern_stat+0x3d > stat() at stat+0x2f > syscall() at Xint0x80_syscall+0x1f > --- syscall (188, FreeBSD ELF32, stat, eip = 0x2819ad63, esp = > 0xbfbfe8cc, ebp = 0xbfbfe9c8 --- > panic: _mtx_lock_sleep: recursed on non-recursive mutex so_snd @ > /usr/src/sys/kern/uipc_socket.c:391 > > cpuid = 0 > KDB: enter: panic > Stopped at kdb_enter+0x30: leave > db> > db> show alllocks > Process 54517 (sh) thread 0xc5f1fd80 (100100) > exclusive sleep mutex so_snd r = 0 (0xc5aef0ec) locked @ > /usr/src/sys/kern/uipc_socket.c:780 > exclusive sleep mutex Giant r = 0 (0xc0a713c0) locked @ > /usr/src/sys/kern/vfs_lookup.c:619 > Process 54515 (cc1) thread 0xc5eac600 (100093) > exclusive sx user map r = 0 (0xc5fa2170) locked @ > /usr/src/sys/vm/vm_map:2996 Try this patch: Index: uipc_socket.c =================================================================== RCS file: /usr/cvs/src/sys/kern/uipc_socket.c,v retrieving revision 1.254 diff -u -r1.254 uipc_socket.c --- uipc_socket.c 28 Nov 2005 21:45:36 -0000 1.254 +++ uipc_socket.c 29 Nov 2005 21:28:16 -0000 @@ -716,7 +716,7 @@ } #define SBLOCKWAIT(f) (((f) & MSG_DONTWAIT) ? M_NOWAIT : M_WAITOK) -#define snderr(errno) { error = (errno); goto out; } +#define snderr(errno) { error = (errno); goto release; } /* * Send on a socket. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 29 21:35: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 B431716A41F for ; Tue, 29 Nov 2005 21:35:13 +0000 (GMT) (envelope-from julian@elischer.org) Received: from delight.idiom.com (outbound.idiom.com [216.240.47.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08F1D43D8D for ; Tue, 29 Nov 2005 21:34:38 +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 CCC45223C69; Tue, 29 Nov 2005 13:34:34 -0800 (PST) Received: from [192.168.2.4] (home.elischer.org [216.240.48.38]) by idiom.com (8.12.11/8.12.11) with ESMTP id jATLYWEI021868; Tue, 29 Nov 2005 13:34:34 -0800 (PST) (envelope-from julian@elischer.org) Message-ID: <438CC968.6090203@elischer.org> Date: Tue, 29 Nov 2005 13:34:32 -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: FreeBSD current mailing list Content-Type: multipart/mixed; boundary="------------090303060402000807010506" Cc: Subject: Re: em interrupt storm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 29 Nov 2005 21:35:13 -0000 This is a multi-part message in MIME format. --------------090303060402000807010506 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit This is not really a -current question as I'm seeing it on 4.x on a Dell 2850 with a PCI-express card, but the previous discussion was here so I thought I'd put it here to continue the thread. The system locks up when the em driver em_intr() is called from irq 2 (em3) but the interrupt was actually generated by em4. as you can see from the vmstat below :root 27] vmstat -i interrupt total rate amr0 irq10 46825 52 em0 irq11 68724 76 em3 irq2 186292 207 em4 irq14 186509 207 atkbd0 irq1 1 0 sio0 irq4 2205 2 clk irq0 89622 99 rtc irq8 114722 127 Total 694900 774 :root 28] em3 and em4 have basically the same interrupt count and rate, however em3 is not active and is not up. The interrupts are coming from em4 which is a standard em type chip on the Dell 2850 motherboard. because em3 didn't make the interrupt, calling it's interrupt routine doesn't clear the interrupt and so it hits again as soon as the interrupt routine returns. thus the system locks up spinning in and out of the interrupt handler for em3 on irq2. However there is something a bit strange about it. If it were as simple as this, and irq2 always copied irq14 then one would expect to freeze up immediatly upon activating em4, but that is not the case. It only sems to freeze up if the system is already in a disk driver (bio mask) when the interrupt happens. (?) em3 and em4 are not connected in any way I know of. em4 is onth emotherboard em3 is on an intel 4-port PCI-express card that is not being used. I can make the system, work reliably by adding code to the em driver so that when any of the em interrupts happen it checks ALL the em interfaces. But this is notthe answer and if there were some OTHER drive on irq2 I'd still be just as hosed. I include the dmesg. Just for fun I might see what happens with dragnfly, though as the machine has no removable media I need to do that over the net so it may take some seting up. Anyone who has any ideas as to why irq14 is being deliverred on irq2, let me know! and let me know why teh prsence of disk IO makes a difference? julian --------------090303060402000807010506 Content-Type: text/plain; name="dmesg" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg" Copyright (c) 1992-2004 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 4.10-RELEASE #5: Tue Nov 29 12:41:48 GMT 2005 root@trafmon1.wga:/usr/build/godspeed/freebsd/mods/src/sys/compile/MESSAGING_GATEWAY Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Xeon(TM) CPU 3.60GHz (3591.25-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 3489398784 (3407616K bytes) avail memory = 3400192000 (3320500K bytes) Changing APIC ID for IO APIC #0 from 0 to 8 on chip Changing APIC ID for IO APIC #1 from 0 to 9 on chip Changing APIC ID for IO APIC #2 from 0 to 10 on chip Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 SCI INT 9 Set apic 0 pin 9, level, active low Set apic 0 pin 9, level, active high FreeBSD/SMP: Multiprocessor motherboard: 4 CPUs cpu0 (BSP): apic id: 0, version: 0x00050014, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00050014, at 0xfee00000 cpu2 (AP): apic id: 6, version: 0x00050014, at 0xfee00000 cpu3 (AP): apic id: 7, version: 0x00050014, at 0xfee00000 io0 (APIC): apic id: 8, version: 0x00178020, at 0xfec00000 io1 (APIC): apic id: 9, version: 0x00178020, at 0xfec80000 io2 (APIC): apic id: 10, version: 0x00178020, at 0xfec83000 Preloaded elf kernel "k2" at 0xc0397000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 18 entries at 0xc00fb6c0 acpi0: on motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_cpu2: on acpi0 acpi_cpu3: on acpi0 npx0: on motherboard npx0: INT 16 interface dell_bios0: Found Dell signature dell_bios0: at iomem 0xf99f0-0xf9a0e on motherboard dell_bios0: Version: 2.03, Revision: 2.03 dell_bios0: Enable 0 dell_bios0: Disable 1 dell_bios0: Size 1025K dell_bios0: Completion Code 0x0000 Success dell_bios0: Updated on: 8/15/05 at 23:44 dell_bios0: Version A03 dell_bios0: Min. Version A03 dell_bios0: Manufacturer IronPort dell_bios0: System ID 32824 [8038] ipmi0: Found Dell signature ipmi0: at iomem 0xf99f0-0xf9a0e on motherboard ipmi0: Version: 2.03, Revision: 2.03 ipmi0: KCS mode found ipmi0: Address 0xca8 ipmi0: Allignment 0x4 ipmi0: I/O mode ipmi0: Device Rev. 0 ipmi0: Firmware Rev. 1.81 ipmi0: Version 1.5 ipmi0: Number of channels 4 pcib0: on motherboard IOAPIC #0 intpin 16 -> irq 2 Hello 8f6f Hello 8f6f pci0: on pcib0 pcib1: irq 2 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 IOAPIC #1 intpin 14 -> irq 10 pci2: on pcib2 amr0: mem 0xdfec0000-0xdfefffff,0xd80f0000-0xd80fffff irq 10 at device 14.0 on pci2 amr0: delete logical drives supported by controller created DEVICE***************** amr0: Firmware 516A, BIOS H418, 256MB RAM pcib3: at device 0.2 on pci1 pci3: on pcib3 pcib4: irq 2 at device 4.0 on pci0 pci4: on pcib4 pcib5: mem 0xdf6e0000-0xdf6fffff irq 2 at device 0.0 on pci4 pci5: on pcib5 pcib6: irq 0 at device 1.0 on pci5 pci6: on pcib6 pcib7: irq 0 at device 2.0 on pci5 IOAPIC #0 intpin 18 -> irq 11 IOAPIC #0 intpin 19 -> irq 13 pci7: on pcib7 em0: port 0xece0-0xecff mem 0xdfbc0000-0xdfbdffff,0xdfbe0000-0xdfbfffff irq 11 at device 0.0 on pci7 em0 00:0e:0c:a1:6a:28, em0: Speed:N/A Duplex:N/A em1: port 0xecc0-0xecdf mem 0xdfb80000-0xdfb9ffff,0xdfba0000-0xdfbbffff irq 13 at device 0.1 on pci7 em0 00:0e:0c:a1:6a:28,em1 00:0e:0c:a1:6a:29, em1: Speed:N/A Duplex:N/A pcib8: irq 0 at device 3.0 on pci5 pci8: on pcib8 em2: port 0xdce0-0xdcff mem 0xdf9c0000-0xdf9dffff,0xdf9e0000-0xdf9fffff irq 13 at device 0.0 on pci8 em0 00:0e:0c:a1:6a:28,em1 00:0e:0c:a1:6a:29,em2 00:0e:0c:a1:6a:2a, em2: Speed:N/A Duplex:N/A em3: port 0xdcc0-0xdcdf mem 0xdf980000-0xdf99ffff,0xdf9a0000-0xdf9bffff irq 2 at device 0.1 on pci8 em0 00:0e:0c:a1:6a:28,em1 00:0e:0c:a1:6a:29,em2 00:0e:0c:a1:6a:2a,em3 00:0e:0c:a1:6a:2b, em3: Speed:N/A Duplex:N/A pcib9: irq 2 at device 5.0 on pci0 pci9: on pcib9 pcib10: at device 0.0 on pci9 IOAPIC #2 intpin 0 -> irq 14 pci10: on pcib10 em4: port 0xccc0-0xccff mem 0xdf4e0000-0xdf4fffff irq 14 at device 7.0 on pci10 em0 00:0e:0c:a1:6a:28,em1 00:0e:0c:a1:6a:29,em2 00:0e:0c:a1:6a:2a,em3 00:0e:0c:a1:6a:2b,em4 00:14:22:0f:45:2f, em4: Speed:N/A Duplex:N/A pcib11: at device 0.2 on pci9 IOAPIC #2 intpin 1 -> irq 15 pci11: on pcib11 em5: port 0xbcc0-0xbcff mem 0xdf2e0000-0xdf2fffff irq 15 at device 8.0 on pci11 em0 00:0e:0c:a1:6a:28,em1 00:0e:0c:a1:6a:29,em2 00:0e:0c:a1:6a:2a,em3 00:0e:0c:a1:6a:2b,em4 00:14:22:0f:45:2f,em5 00:14:22:0f:45:30, em5: Speed:N/A Duplex:N/A pcib12: irq 2 at device 6.0 on pci0 pci12: on pcib12 pcib13: at device 30.0 on pci0 pci13: on pcib13 pci13: at 13.0 irq 11 isab0: at device 31.0 on pci0 isa0: on isab0 orm0: cpuid =3D 0; apic id =3D 00 instruction pointer =3D 0x8:0xffffffff803e9a40 stack pointer =3D 0x10:0xffffffff80e36d00 frame pointer =3D 0x10:0xffffffff80e36d20 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, IOPL =3D 0 current process =3D 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 =2D-=20 Anish Mistry --nextPart5054464.LVOyaC6orN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDke32xqA5ziudZT0RAnUOAKCXKWCous3JZfmOExHFXSprQYklRwCdFyWG Oy16gRhZAB3IYlKHHCDQCt8= =xd1J -----END PGP SIGNATURE----- --nextPart5054464.LVOyaC6orN-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 20:19:44 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.ORG Delivered-To: freebsd-current@FreeBSD.ORG Received: by hub.freebsd.org (Postfix, from userid 618) id D8DBF16A420; Sat, 3 Dec 2005 20:19:44 +0000 (GMT) In-Reply-To: <20051203110534.N98873@fledge.watson.org> from Robert Watson at "Dec 3, 2005 11:36:28 am" To: rwatson@FreeBSD.org (Robert Watson) Date: Sat, 3 Dec 2005 20:19:44 +0000 (GMT) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051203201944.D8DBF16A420@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Cc: freebsd-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: Sat, 03 Dec 2005 20:19:45 -0000 > I was able to get the atheros card working with the NDIS Project Evil > magic. You can find the AR5211.SYS and NET5211.INF files on the Windows > partition (I mounted the partition using ntfs support in FreeBSD without a > hitch to copy them over). I had to tweak the INF file so that it could be > parsed by ndisgen to comment out the following two lines: > > [5211.reg.security] > "D:ARAI(A;;GA;;;BA)(A;;GA;;;SY)(A;CI;GA;;;IO) I'm not sure how to fix the lex/yacc parser to avoid this. Suggestions welcome. For now, I just edit the .inf file too. > However, I was unable to get the card to go into both 802.11b mode and ad > hoc mode at the same time. I need to send Bill Paul a useful report, > although possibly once I'm back from travel. You don't "get the card to go into both 802.11b mode and ad hoc mode" at the same time. You just do "ifconfig ndis0 ssid moo mediaopt adhoc" and if there's another station in ad-hoc mode around on ssid moo, it'll associate with it with no further tweaking, whether it's 802.11b or 802.11g. For 802.11a ad-hoc cells, you may have to change the channel (it's been a while since I've tried it). I set up an 802.11b only ad-hoc net for some friends at their house recently, and my laptop with Atheros-based cardbus card and Project Evil was able to associate with it without any problems (with WEP too). So I have no idea what your problem is. It should "just work." -Bill -- ============================================================================= -Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu wpaul@windriver.com | Wind River Systems ============================================================================= you're just BEGGING to face the moose ============================================================================= From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 20:45:54 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 A587516A41F for ; Sat, 3 Dec 2005 20:45:54 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id D579643D4C for ; Sat, 3 Dec 2005 20:45:53 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id i11so767564nzh for ; Sat, 03 Dec 2005 12:45:53 -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=IixpE14XOXiz9T0qXRA6tjvVJqSW7wDMEThRGVIHgUhuprTS98LVX/F9rPf3ZkwoFD3VK5tl7U+mEaLkxiyz0Qlk7QwX2sC5PCpDqxXs1arczG4H+C1Tx7WeXgBpC/we1lcxAM0aKlxwz664oKpIzaWQ6knhj/bYynCtbki3Bts= Received: by 10.65.188.8 with SMTP id q8mr2099551qbp; Sat, 03 Dec 2005 12:45:53 -0800 (PST) Received: by 10.65.192.14 with HTTP; Sat, 3 Dec 2005 12:45:53 -0800 (PST) Message-ID: Date: Sat, 3 Dec 2005 21:45:53 +0100 From: Claus Guttesen To: Jason Evans In-Reply-To: <0B746373-8C29-4ADF-9218-311AE08F3834@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> 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: Sat, 03 Dec 2005 20:45:54 -0000 > There's a new version of the patch available at: > http://www.canonware.com/~jasone/jemalloc/jemalloc_20051202b.diff When I do a make buildworld I get: cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=3Dathlon64 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/stdlib/malloc.c -o malloc.So cc -O2 -fno-strict-aliasing -pipe -march=3Dathlon64 -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/lib/libc/stdlib/merge.c /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_lock': /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c:853: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_unlock': /usr/src/lib/libc/stdlib/malloc.c:894: warning: cast from pointer to integer of different size *** Error code 1 /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_lock': /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c:853: warning: cast from pointer to integer of different size /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_unlock': /usr/src/lib/libc/stdlib/malloc.c:894: warning: cast from pointer to integer of different size *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error make -j 3 buildworld 763,54s user 150,98s system 173% cpu 8:48,62 total twin/usr/src#>uname -a FreeBSD twin.gnome.no 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Dec 1 21:38:11 CET 2005 root@twin.gnome.no:/usr/obj/usr/src/sys/TWIN=20 amd64 regards Claus From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 21:05: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 6F1BC16A41F for ; Sat, 3 Dec 2005 21:05:45 +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 093DD43D66 for ; Sat, 3 Dec 2005 21:05:44 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id B81305E48C5; Sat, 3 Dec 2005 13:05:44 -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 ED34D5E4885; Sat, 3 Dec 2005 13:05:41 -0800 (PST) In-Reply-To: References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <7318D807-9086-4817-A40B-50D6960880FB@canonware.com> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Sat, 3 Dec 2005 13:04:38 -0800 To: Claus Guttesen 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: Sat, 03 Dec 2005 21:05:45 -0000 On Dec 3, 2005, at 12:45 PM, Claus Guttesen wrote: >> There's a new version of the patch available at: >> http://www.canonware.com/~jasone/jemalloc/jemalloc_20051202b.diff > > When I do a make buildworld I get: > > cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=athlon64 > -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include > -I/usr/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE > -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 > -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale > -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP > -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/lib/libc/stdlib/malloc.c -o malloc.So > cc -O2 -fno-strict-aliasing -pipe -march=athlon64 > -I/usr/src/lib/libc/include -I/usr/src/lib/libc/../../include > -I/usr/src/lib/libc/amd64 -D__DBINTERFACE_PRIVATE > -I/usr/src/lib/libc/../../contrib/gdtoa -DINET6 > -I/usr/obj/usr/src/lib/libc -DPOSIX_MISTAKE -I/usr/src/lib/libc/locale > -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP > -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c > /usr/src/lib/libc/stdlib/merge.c > /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_lock': > /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c:853: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_unlock': > /usr/src/lib/libc/stdlib/malloc.c:894: warning: cast from pointer to > integer of different size > *** Error code 1 > /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_lock': > /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c:846: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c:853: warning: cast from pointer to > integer of different size > /usr/src/lib/libc/stdlib/malloc.c: In function `malloc_mutex_unlock': > /usr/src/lib/libc/stdlib/malloc.c:894: warning: cast from pointer to > integer of different size > *** Error code 1 > 2 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > make -j 3 buildworld 763,54s user 150,98s system 173% cpu 8:48,62 > total > > twin/usr/src#>uname -a > FreeBSD twin.gnome.no 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Dec 1 > 21:38:11 CET 2005 root@twin.gnome.no:/usr/obj/usr/src/sys/TWIN > amd64 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. Thanks, Jason From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 21:10:03 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 7A33416A41F for ; Sat, 3 Dec 2005 21:10:03 +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 5A4EA43D8B for ; Sat, 3 Dec 2005 21:09:52 +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 <0IQX00225XGDLI50@VL-MO-MR004.ip.videotron.ca> for freebsd-current@freebsd.org; Sat, 03 Dec 2005 16:09:49 -0500 (EST) Date: Sat, 03 Dec 2005 16:09:36 -0500 From: Nicolas Blais To: freebsd-current@freebsd.org Message-id: <200512031609.48962.nb_root@videotron.ca> MIME-version: 1.0 Content-type: multipart/signed; boundary=nextPart3870280.5jmme37tBO; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-transfer-encoding: 7bit User-Agent: KMail/1.8.3 Subject: [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: Sat, 03 Dec 2005 21:10:03 -0000 --nextPart3870280.5jmme37tBO Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline After a cvsup/buildworld today, sshd (and cupsd, reported in PR ports/89892= )=20 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 not= =20 start, nor does it seem like it even tried as there are no error messages: Starting rpcbind. ELF ldconfig=20 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/aout 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. =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 --nextPart3870280.5jmme37tBO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDkgmc4wTBlvcsbJURAnBMAJ9W8yPtNwf1B0AeYii885m3TCNRMQCggqeL Z51KDDr+ksbfLJ7EyUasVP4= =91IM -----END PGP SIGNATURE----- --nextPart3870280.5jmme37tBO-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 21:10:19 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 E72D216A44F; Sat, 3 Dec 2005 21:10:19 +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 9984843D73; Sat, 3 Dec 2005 21:10:06 +0000 (GMT) (envelope-from jasone@canonware.com) Received: by lh.synack.net (Postfix, from userid 100) id 672EE5E48A3; Sat, 3 Dec 2005 13:10:04 -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 4B0635E4885; Sat, 3 Dec 2005 13:09:55 -0800 (PST) In-Reply-To: <4391569A.7080808@freebsd.org> References: <0B746373-8C29-4ADF-9218-311AE08F3834@canonware.com> <4391569A.7080808@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 13:08:51 -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: Sat, 03 Dec 2005 21:10:20 -0000 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 From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 21:15:59 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 6BC1116A41F for ; Sat, 3 Dec 2005 21:15:59 +0000 (GMT) (envelope-from kometen@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE1FF43D49 for ; Sat, 3 Dec 2005 21:15:58 +0000 (GMT) (envelope-from kometen@gmail.com) Received: by zproxy.gmail.com with SMTP id j2so603829nzf for ; Sat, 03 Dec 2005 13:15: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:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WMqRuuHULQuuqp2cvb16xcPEWv/9PxE6A9BrSy7rgPW61BLaEqYAjLm9Cd4+R89JX4iu0PSu4Xh0avixAUrj7LfgxijQucEH5+kpIVHUgfEUKFQFrlCeFvoiRIEAJ5swMvh/O5AkkdIZjIxdGmqjG4HJPr2QiUFieG8VRjiBGhI= Received: by 10.65.11.9 with SMTP id o9mr2116975qbi; Sat, 03 Dec 2005 13:15:58 -0800 (PST) Received: by 10.65.192.14 with HTTP; Sat, 3 Dec 2005 13:15:58 -0800 (PST) Message-ID: Date: Sat, 3 Dec 2005 22:15:58 +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: Sat, 03 Dec 2005 21:15:59 -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. Yes. I'll do the test that you want me to do :-) Thank you! regards Claus From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 21:51: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 9D95016A41F for ; Sat, 3 Dec 2005 21:51:21 +0000 (GMT) (envelope-from psientist@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E229243D5D for ; Sat, 3 Dec 2005 21:51:20 +0000 (GMT) (envelope-from psientist@gmail.com) Received: by zproxy.gmail.com with SMTP id 8so398980nzo for ; Sat, 03 Dec 2005 13:51:20 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:subject:from:reply-to:to:in-reply-to:references:content-type:date:message-id:mime-version:x-mailer:content-transfer-encoding; b=Ct5IHJdtBZTZsg+AjHbmDGrizNxM3eO0snkRBqCOsoRvOBF8yFon4aoCupDMopsY6NmkgsExTp9OxiUw/UbhK3EkTZ3tjs/cF7RKd7HkCRkX0rchcBLaqhmQDwE0ChGmm+xCSAU2aDNIrbnl4WzOBfbGjF4nQiHZX3YQfjkhSBk= Received: by 10.36.251.17 with SMTP id y17mr3947488nzh; Sat, 03 Dec 2005 13:51:20 -0800 (PST) Received: from ?192.168.2.2? ( [66.235.60.121]) by mx.gmail.com with ESMTP id e1sm2587400nzd.2005.12.03.13.51.19; Sat, 03 Dec 2005 13:51:20 -0800 (PST) From: discord To: freebsd-current@freebsd.org In-Reply-To: <20051203120031.BC03216A420@hub.freebsd.org> References: <20051203120031.BC03216A420@hub.freebsd.org> Content-Type: text/plain Date: Sat, 03 Dec 2005 13:51:22 -0800 Message-Id: <1133646682.20455.1.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 Content-Transfer-Encoding: 7bit Subject: Re: freebsd-current Digest, Vol 123, Issue 10 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: psientist@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 21:51:21 -0000 I need to make a bootable freeBSD install cd in the El Torito format. Does anybody know how I go about doing that? From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 22:05:59 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 2BF8916A41F for ; Sat, 3 Dec 2005 22:05:59 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 715FD43D78 for ; Sat, 3 Dec 2005 22:05:50 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7E57A46B06; Sat, 3 Dec 2005 17:05:42 -0500 (EST) Date: Sat, 3 Dec 2005 22:05:42 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Vladimir Egorin In-Reply-To: <20051203182746.GA972@math.uic.edu> Message-ID: <20051203220113.U22189@fledge.watson.org> References: <20051203110534.N98873@fledge.watson.org> <20051203182746.GA972@math.uic.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Sat, 03 Dec 2005 22:05:59 -0000 On Sat, 3 Dec 2005, Vladimir Egorin wrote: > On Sat, Dec 03, 2005 at 11:36:28AM +0000, Robert Watson wrote: > > > > Last week, I ordered byself a new notebook -- for reasons of price, stock, > > features, etc, I went with the Lenovo z60t 2511. This is IBM part number > > UM3EJUK, and comes with a 14" display (1280x768 widescreen), 1.86GHz > > Pentium M, 512M of memory, and a 60GB hard disk. It also has hardware > > fingerprint scanner, bluetooth, SD card reader, broadcom gig-e, firewire, > > atheros 802.11 chipset, and various other neat things. Obviously, I > > installed FreeBSD on it. Throughout, I found the > > http://www.thinkwiki.org/ site useful. > > how good is the build quality of the laptop? The software bundling is terrible -- it seemed like it hadn't even been tested. When I first booted the notebook, it decided to spend several minutes converting from FAT to NTFS. Maybe this is a standard thing, but it strikes me as silly to ship with one file system only to have to wait for it to convert when the notebook is first used (!). After that XP popped up lots of dialog boxes about various things, got confused registering fingerprints for users as it claimed they didn't have accounts, and soon. However, since I plan to use almost the notebook almost entirely with FreeBSD, this is all pretty much ignorable. :-) The hardware in the machine seems solid -- the case is sturdy, there's not undue flexing of the case (a common problem for Dells, for example). As to how well it lasts under real-world stress, I'll let you know after a month of travelling around India in January :-). Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 22:25: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 2D2DC16A41F; Sat, 3 Dec 2005 22:25:06 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AB1443D69; Sat, 3 Dec 2005 22:25:05 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 925E046B84; Sat, 3 Dec 2005 17:25:03 -0500 (EST) Date: Sat, 3 Dec 2005 22:25:03 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: andre@FreeBSD.org Message-ID: <20051203150119.B3216@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@FreeBSD.org Subject: mbuf cluster leaks in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 22:25:06 -0000 Yesterday I sat down to run some benchmarks on phk's changes to the process time measurement system for scheduling, and discovered SMP boxes were wedging in [zonelimit] when running netperf tests. I quickly tracked this down to an mbuf cluster leak: /zoo/rwatson/netperf/bin/netserver while (1) echo "" netstat -m | grep mbuf /zoo/rwatson/netperf/bin/netperf -l 30 >& /dev/null end Result of: CVS Date Description Leak? 2005/12/3 sample yes 2005/11/28-2005/11/29 rwatson sosend changes - 2005/11/25 sample yes 2005/11/15 sample yes 2005/11/02-2005/11/05 andre cluster changes - 2005/10/25 sample no 2005/10/15 sample no 2005/10/1 sample no 2005/09/27 rwatson removes mbuf counters - 2005/09/16 sample no The reason for the wedge is that NFS based systems don't like running out of mbuf clusters. It turns out that the reason I likely didn't notice this previously was that I was running the test boxes in question without ACPI, and for whatever reason, the race becomes many times more serious with ACPI turned on. It was leaking without ACPI, but since it was slower, I wasn't noticing since I had the machines up for much shorter tests. Here's a sampling of kernel dates and whether or not the leak was present in a kernel from the date, as well as the dates of a few changes I was worried were likely causes: 769/641/1410 mbufs in use (current/cache/total) 768/204/972/25600 mbuf clusters in use (current/cache/total/max) 769/4991/5760 mbufs in use (current/cache/total) 4341/905/5246/25600 mbuf clusters in use (current/cache/total/max) 769/8456/9225 mbufs in use (current/cache/total) 7901/801/8702/25600 mbuf clusters in use (current/cache/total/max) 769/11786/12555 mbufs in use (current/cache/total) 11242/788/12030/25600 mbuf clusters in use (current/cache/total/max) 769/15236/16005 mbufs in use (current/cache/total) 14570/916/15486/25600 mbuf clusters in use (current/cache/total/max) 769/18566/19335 mbufs in use (current/cache/total) 17948/866/18814/25600 mbuf clusters in use (current/cache/total/max) I've not really had a chance to investigate the details of the leak -- the number of used (allocated) mbufs remains low, but the cache number grows steadily. However, the dates suggest that it was the mbuf cluster cleanup work you did that introduced the problem (although don't guarantee it). Thanks, Robert N M Watson From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 22:45:49 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 C2B0716A41F for ; Sat, 3 Dec 2005 22:45:49 +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 661EE43D5A for ; Sat, 3 Dec 2005 22:45:47 +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 jB3MjkCG003274 for ; Sun, 4 Dec 2005 00:45:46 +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 02977-02-3 for ; Sun, 4 Dec 2005 00:45:45 +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 jB3MjFm2003241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 4 Dec 2005 00:45:16 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jB3MjIgA072493 for current@FreeBSD.org; Sun, 4 Dec 2005 00:45:18 +0200 (EET) (envelope-from ru) Date: Sun, 4 Dec 2005 00:45:18 +0200 From: Ruslan Ermilov To: current@FreeBSD.org Message-ID: <20051203224518.GJ960@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vbzKE9fGfpHIBC6T" Content-Disposition: inline User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: Subject: Beware of subtle bugs due to cpp(1) limitations! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 03 Dec 2005 22:45:49 -0000 --vbzKE9fGfpHIBC6T Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi there, cpp(1) only supports integer expressions, so the following #define FOO foo #if FOO =3D=3D bar will always evaluate to true, because "foo" and "bar" will be treated as zeroes, as explained in cpp.info. I've only scanned for _MACHINE_ARCH, because that's how I discovered it, and there's a couple of places where the code is broken: sys/dev/isp/isp_freebsd.h:#if _MACHINE_ARCH =3D=3D sparc64 sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 sys/gnu/fs/reiserfs/reiserfs_fs.h:#if (_MACHINE_ARCH =3D=3D amd64) sys/netgraph/ng_vjc.c:#if _MACHINE_ARCH =3D=3D i386 sys/netgraph/ng_vjc.c:#elif _MACHINE_ARCH =3D=3D alpha sys/netgraph/ng_vjc.c:#error Unspported _MACHINE_ARCH In these cases, the right tests would be #ifdef __sparc64__. Other instances (of not _MACHINE_ARCH) may be harder to fix. The ng_vjc.c is a nice example that clearly demonstrates (without compiling the code) that it's broken -- it's compiled on all architectures, but has the following code: #if _MACHINE_ARCH =3D=3D i386 #define NG_VJC_TSTATE_PTR_TYPE &ng_parse_uint32_type #elif _MACHINE_ARCH =3D=3D alpha #define NG_VJC_TSTATE_PTR_TYPE &ng_parse_uint64_type #else #error Unspported _MACHINE_ARCH #endif The season for more bugs of this type is declared open! :-) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --vbzKE9fGfpHIBC6T Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkh/+qRfpzJluFF4RAsuQAJ409WxCpqOhYfOCaOtDp2mKX3a54wCeOj1A lcbvVVME7PjIrinGnefue0A= =suSU -----END PGP SIGNATURE----- --vbzKE9fGfpHIBC6T-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 22:55: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 CE8C816A41F for ; Sat, 3 Dec 2005 22:55:56 +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 A9BED43D64 for ; Sat, 3 Dec 2005 22:55:55 +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 jB3Mtr00003508 for ; Sun, 4 Dec 2005 00:55:53 +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 02977-04-2 for ; Sun, 4 Dec 2005 00:55:51 +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 jB3MtEWl003467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 4 Dec 2005 00:55:14 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jB3MtHos087486 for current@FreeBSD.org; Sun, 4 Dec 2005 00:55:17 +0200 (EET) (envelope-from ru) Date: Sun, 4 Dec 2005 00:55:17 +0200 From: Ruslan Ermilov To: current@FreeBSD.org Message-ID: <20051203225517.GK960@ip.net.ua> References: <20051203224518.GJ960@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="c8JyeaiReRNoiMDS" Content-Disposition: inline In-Reply-To: <20051203224518.GJ960@ip.net.ua> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: Subject: Re: Beware of subtle bugs due to cpp(1) limitations! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 03 Dec 2005 22:55:56 -0000 --c8JyeaiReRNoiMDS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 04, 2005 at 12:45:18AM +0200, Ruslan Ermilov wrote: > Hi there, >=20 > cpp(1) only supports integer expressions, so the following >=20 > #define FOO foo > #if FOO =3D=3D bar >=20 > will always evaluate to true, because "foo" and "bar" will > be treated as zeroes, as explained in cpp.info. >=20 > I've only scanned for _MACHINE_ARCH, because that's how I > discovered it, and there's a couple of places where the > code is broken: >=20 > sys/dev/isp/isp_freebsd.h:#if _MACHINE_ARCH =3D=3D sparc64 > sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 > sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 > sys/dev/ispfw/ispfw.c:#if _MACHINE_ARCH =3D=3D sparc64 > sys/gnu/fs/reiserfs/reiserfs_fs.h:#if (_MACHINE_ARCH =3D=3D amd64) > sys/netgraph/ng_vjc.c:#if _MACHINE_ARCH =3D=3D i386 > sys/netgraph/ng_vjc.c:#elif _MACHINE_ARCH =3D=3D alpha > sys/netgraph/ng_vjc.c:#error Unspported _MACHINE_ARCH >=20 > In these cases, the right tests would be #ifdef __sparc64__. > Other instances (of not _MACHINE_ARCH) may be harder to > fix. The ng_vjc.c is a nice example that clearly > demonstrates (without compiling the code) that it's > broken -- it's compiled on all architectures, but has > the following code: >=20 > #if _MACHINE_ARCH =3D=3D i386 > #define NG_VJC_TSTATE_PTR_TYPE &ng_parse_uint32_type > #elif _MACHINE_ARCH =3D=3D alpha > #define NG_VJC_TSTATE_PTR_TYPE &ng_parse_uint64_type > #else > #error Unspported _MACHINE_ARCH > #endif >=20 > The season for more bugs of this type is declared open! :-) >=20 ``cpp -Wundef'' will allow us to find all these bugs. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --c8JyeaiReRNoiMDS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkiJVqRfpzJluFF4RAn9FAJoC9GIS0riMKZb15/V5ouUl3V0BCACgjh++ a4TXSeJM94K9pUB1gNFdEIU= =gowy -----END PGP SIGNATURE----- --c8JyeaiReRNoiMDS-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 22:59: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 2642916A420 for ; Sat, 3 Dec 2005 22:59:16 +0000 (GMT) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28A1F43D55 for ; Sat, 3 Dec 2005 22:59:14 +0000 (GMT) (envelope-from andre@freebsd.org) Received: (qmail 95738 invoked from network); 3 Dec 2005 22:56:34 -0000 Received: from c00l3r.networx.ch (HELO freebsd.org) ([62.48.2.2]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 3 Dec 2005 22:56:34 -0000 Message-ID: <43922340.4CAF7157@freebsd.org> Date: Sat, 03 Dec 2005 23:59:12 +0100 From: Andre Oppermann X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Robert Watson References: <20051203150119.B3216@fledge.watson.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@FreeBSD.org Subject: Re: mbuf cluster leaks in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2005 22:59:16 -0000 Robert Watson wrote: > > Yesterday I sat down to run some benchmarks on phk's changes to the process > time measurement system for scheduling, and discovered SMP boxes were wedging > in [zonelimit] when running netperf tests. I quickly tracked this down to an > mbuf cluster leak: > > /zoo/rwatson/netperf/bin/netserver > while (1) > echo "" > netstat -m | grep mbuf > /zoo/rwatson/netperf/bin/netperf -l 30 >& /dev/null > end > > Result of: > > CVS Date Description Leak? > 2005/12/3 sample yes > 2005/11/28-2005/11/29 rwatson sosend changes - > 2005/11/25 sample yes > 2005/11/15 sample yes > 2005/11/02-2005/11/05 andre cluster changes - > 2005/10/25 sample no > 2005/10/15 sample no > 2005/10/1 sample no > 2005/09/27 rwatson removes mbuf counters - > 2005/09/16 sample no > > The reason for the wedge is that NFS based systems don't like running out of > mbuf clusters. It turns out that the reason I likely didn't notice this > previously was that I was running the test boxes in question without ACPI, and > for whatever reason, the race becomes many times more serious with ACPI turned > on. It was leaking without ACPI, but since it was slower, I wasn't noticing > since I had the machines up for much shorter tests. Here's a sampling of > kernel dates and whether or not the leak was present in a kernel from the > date, as well as the dates of a few changes I was worried were likely causes: > > 769/641/1410 mbufs in use (current/cache/total) > 768/204/972/25600 mbuf clusters in use (current/cache/total/max) > > 769/4991/5760 mbufs in use (current/cache/total) > 4341/905/5246/25600 mbuf clusters in use (current/cache/total/max) > > 769/8456/9225 mbufs in use (current/cache/total) > 7901/801/8702/25600 mbuf clusters in use (current/cache/total/max) > > 769/11786/12555 mbufs in use (current/cache/total) > 11242/788/12030/25600 mbuf clusters in use (current/cache/total/max) > > 769/15236/16005 mbufs in use (current/cache/total) > 14570/916/15486/25600 mbuf clusters in use (current/cache/total/max) > > 769/18566/19335 mbufs in use (current/cache/total) > 17948/866/18814/25600 mbuf clusters in use (current/cache/total/max) > > I've not really had a chance to investigate the details of the leak -- the > number of used (allocated) mbufs remains low, but the cache number grows > steadily. However, the dates suggest that it was the mbuf cluster cleanup > work you did that introduced the problem (although don't guarantee it). This seems to be the same problem I described in rev. 1.14 of kern_mbuf.c where mbuf+clusters from the packet zone (pre-combined m+c) never get free'd back to their original pools. The numbers from netstat -m support that assumption. It doesn't (and can't) show the number of cached m+c in the packet zone. Mbuf's in packet zone account as cached in the mbuf zone because the packet zone is a secondary zone to it. The clusters in use are not leaked but attached to all those mbufs in the packet zone. The cluster zone doesn't know about the packet zone and accounts them as used. This pseudo-leak is not from my changes (as it is a UMA bug) but gets amplified by use of kernel subsystems which make heavy use of m+c from the packet zone. While my changes triggered this problem too by changing the way packets get free'd back to the UMA mbuf, cluster and packet zones it was reverted in 1.14. The other refcount changes do not cause any such effect. It may very well be that some part of the network stack switched from allocating mbuf and cluster separately to pre-combined packets. That would explain the 'sudden' appearance of the problem. The right fix is to have UMA free back mbuf+clusters from the packet zone to their native zones. This should not be done with high/low watermarks but a median and positive/negative deviation method. Refills and drains to/from the packet zone should happen in batches and not for single requests or free's to be efficient. I'll look into it tomorrow. I may have to summon Bosko for some help on the secondary zone stuff as he introduced this feature. -- Andre From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 23:06: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 0DF8C16A41F; Sat, 3 Dec 2005 23:06:12 +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 0740C43D53; Sat, 3 Dec 2005 23:06:10 +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 jB3N69cM003790; Sun, 4 Dec 2005 01:06:09 +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 03184-02-3; Sun, 4 Dec 2005 01:06:07 +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 jB3N4SJv003741 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 4 Dec 2005 01:04:28 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id jB3N4VwD098096; Sun, 4 Dec 2005 01:04:31 +0200 (EET) (envelope-from ru) Date: Sun, 4 Dec 2005 01:04:31 +0200 From: Ruslan Ermilov To: current@FreeBSD.org Message-ID: <20051203230431.GL960@ip.net.ua> References: <20051203224518.GJ960@ip.net.ua> <20051203225517.GK960@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="LJm8egi4vkexsie5" Content-Disposition: inline In-Reply-To: <20051203225517.GK960@ip.net.ua> User-Agent: Mutt/1.5.9i X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: re@FreeBSD.org Subject: Re: Beware of subtle bugs due to cpp(1) limitations! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: 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, 03 Dec 2005 23:06:12 -0000 --LJm8egi4vkexsie5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 04, 2005 at 12:55:17AM +0200, Ruslan Ermilov wrote: > On Sun, Dec 04, 2005 at 12:45:18AM +0200, Ruslan Ermilov wrote: > > Hi there, > >=20 > > cpp(1) only supports integer expressions, so the following > >=20 > > #define FOO foo > > #if FOO =3D=3D bar > >=20 > > will always evaluate to true, because "foo" and "bar" will > > be treated as zeroes, as explained in cpp.info. [...] > > The season for more bugs of this type is declared open! :-) > >=20 > ``cpp -Wundef'' will allow us to find all these bugs. >=20 Here we go: %%% Index: share/mk/bsd.sys.mk =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/share/mk/bsd.sys.mk,v retrieving revision 1.37 diff -u -r1.37 bsd.sys.mk --- share/mk/bsd.sys.mk 16 Jan 2005 21:18:16 -0000 1.37 +++ share/mk/bsd.sys.mk 3 Dec 2005 22:57:36 -0000 @@ -11,7 +11,7 @@ .if !defined(NO_WARNS) && ${CC} !=3D "icc" . if defined(WARNS) . if ${WARNS} >=3D 1 -CWARNFLAGS +=3D -Wsystem-headers +CWARNFLAGS +=3D -Wsystem-headers -Wundef . if !defined(NO_WERROR) CWARNFLAGS +=3D -Werror . endif Index: sys/conf/kern.mk =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/conf/kern.mk,v retrieving revision 1.46 diff -u -r1.46 kern.mk --- sys/conf/kern.mk 15 Jul 2005 11:45:30 -0000 1.46 +++ sys/conf/kern.mk 3 Dec 2005 22:58:41 -0000 @@ -12,7 +12,7 @@ .else CWARNFLAGS?=3D -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototype= s \ -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual \ - -fformat-extensions -std=3Dc99 + -Wundef -fformat-extensions -std=3Dc99 .endif # # The following flags are next up for working on: %%% Should I commit it to force a thorough fixing? (The #ifdef notdef/notyet are not affected by this change.) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --LJm8egi4vkexsie5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkiR/qRfpzJluFF4RAuMlAKCNQUZjJoYid3yNHugda2NNT5Z1tgCdF7ya L1L9gThFFm4iuEMNxYBZHSU= =bmc7 -----END PGP SIGNATURE----- --LJm8egi4vkexsie5-- From owner-freebsd-current@FreeBSD.ORG Sat Dec 3 23:47: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 83BEA16A41F; Sat, 3 Dec 2005 23:47:20 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [70.88.158.93]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFB2643D6B; Sat, 3 Dec 2005 23:47:19 +0000 (GMT) (envelope-from mdodd@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [70.88.158.93]) by sasami.jurai.net (8.13.1/8.13.1) with ESMTP id jB3NlCsc045245; Sat, 3 Dec 2005 18:47:18 -0500 (EST) (envelope-from mdodd@FreeBSD.ORG) Date: Sat, 3 Dec 2005 18:47:12 -0500 (EST) From: "Matthew N. Dodd" X-X-Sender: winter@sasami.jurai.net To: Bill Paul In-Reply-To: <20051203201944.D8DBF16A420@hub.freebsd.org> Message-ID: <20051203184409.O52622@sasami.jurai.net> References: <20051203201944.D8DBF16A420@hub.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.6 (sasami.jurai.net [70.88.158.93]); Sat, 03 Dec 2005 18:47:18 -0500 (EST) Cc: freebsd-current@FreeBSD.ORG, Robert Watson 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: Sat, 03 Dec 2005 23:47:20 -0000 On Sat, 3 Dec 2005, Bill Paul wrote: >> >> [5211.reg.security] >> "D:ARAI(A;;GA;;;BA)(A;;GA;;;SY)(A;CI;GA;;;IO) > > I'm not sure how to fix the lex/yacc parser to avoid this. Suggestions > welcome. For now, I just edit the .inf file too. I'm not sure if this patch causes any collateral damage, but it appears to work for my trivial tests. Index: inf-token.l =================================================================== RCS file: /home/cvs/src/usr.sbin/ndiscvt/inf-token.l,v retrieving revision 1.3 diff -u -u -r1.3 inf-token.l --- inf-token.l 11 Jan 2004 21:10:35 -0000 1.3 +++ inf-token.l 3 Dec 2005 23:43:54 -0000 @@ -116,7 +116,7 @@ yylval.str = strdup(yytext+1); return SECTION; } -[a-zA-Z0-9%&\{\}\-\.\/_\\\*]+ { +[a-zA-Z0-9%&\{\}\-\.\/_\\\*\"\:\;\(\)]+ { yylval.str = strdup(yytext); return WORD; }