From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 00:17:22 2004 Return-Path: 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 E13CC16A4CE for ; Sun, 14 Nov 2004 00:17:22 +0000 (GMT) Received: from vsmtp2.tin.it (vsmtp2alice.tin.it [212.216.176.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39CC943D31 for ; Sun, 14 Nov 2004 00:17:22 +0000 (GMT) (envelope-from rionda@gufi.org) Received: from kaiser.sig11.org (82.50.122.174) by vsmtp2.tin.it (7.0.027) id 4195EF2F0002FDB3 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 01:17:22 +0100 Received: from [127.0.0.1] (localhost [127.0.0.1]) by kaiser.sig11.org (Postfix) with ESMTP id BD300106 for ; Sun, 14 Nov 2004 01:17:19 +0100 (CET) From: Matteo Riondato To: freebsd-current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-MURoUJ6aZlwgQkBeZXFi" Message-Id: <1100391439.92272.16.camel@kaiser.sig11.org> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 14 Nov 2004 01:17:19 +0100 Subject: Can anyone MFC /usr/bin/mkuzip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: rionda@gufi.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 00:17:23 -0000 --=-MURoUJ6aZlwgQkBeZXFi Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Well, Subject can tell you whatever you may need to know ;) This utility is there since Fri Sep 10 20:17:31 2004 UTC and has not been MFC yet. I think it should be merged to allow people to use a native "compressed filesystem creator" instead of sysutils/cloop-utils, which is Linux derived, AFAIK. Thanks in advance. Best Regards --=20 Rionda aka Matteo Riondato GUFI Staff Member (http://www.gufi.org) FreeSBIE Developer (http://www.freesbie.org) BSD-FAQ-it Main Developer (http://utenti.gufi.org/~rionda) Sent from: kaiser.sig11.org running FreeBSD-6.0-CURRENT --=-MURoUJ6aZlwgQkBeZXFi Content-Type: application/pgp-signature; name=signature.asc Content-Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQBBlqQP2Mp4pR7Fa+wRAkFYAKCjfK2d17M8qbL5a8a8RApMTM0PAQCeKNtE RihheQA+TEk7G1uX4Sy3BBY= =3kAN -----END PGP SIGNATURE----- --=-MURoUJ6aZlwgQkBeZXFi-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 00:29:06 2004 Return-Path: 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 43CBD16A4CE; Sun, 14 Nov 2004 00:29:06 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B019943D2D; Sun, 14 Nov 2004 00:29:05 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAE0SOh4049006; Sat, 13 Nov 2004 17:28:24 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 13 Nov 2004 17:28:38 -0700 (MST) Message-Id: <20041113.172838.18695811.imp@bsdimp.com> To: tinderbox@freebsd.org From: "M. Warner Losh" In-Reply-To: <20041113214203.331EF7306E@freebsd-current.sentex.ca> References: <20041113214203.331EF7306E@freebsd-current.sentex.ca> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: i386@freebsd.org Subject: Re: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 00:29:06 -0000 In message: <20041113214203.331EF7306E@freebsd-current.sentex.ca> FreeBSD Tinderbox writes: : /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c:115: error: `_COMPONENT' undeclared (first use in this function) OK. That's my fault . I believe I've fixed this. Warner From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 00:42:55 2004 Return-Path: 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 43F1116A4CE; Sun, 14 Nov 2004 00:42:55 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB09543D2D; Sun, 14 Nov 2004 00:42:54 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) iAE0gowB009200; Sat, 13 Nov 2004 19:42:50 -0500 (EST) Date: Sat, 13 Nov 2004 19:42:50 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andrew Moran In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 00:42:55 -0000 On Sat, 13 Nov 2004, Andrew Moran wrote: > > I made the jump from 5.21 to 5.3 earlier and started getting the > infamous "Fatal error 'Spinlock called when not threaded.' at line 83 > in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" > everytime I ran gnucash. I suggest you move /usr/lib/libc_r.so* and /usr/lib/libthr.so* out of the way and see what happens. You also want to make sure you're not using a statically built program. -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 00:46:00 2004 Return-Path: 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 BD0C216A4CE for ; Sun, 14 Nov 2004 00:46:00 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 65C2043D2D for ; Sun, 14 Nov 2004 00:46:00 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CT8Uj-000FF8-00 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 03:43:53 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CT8Ui-000FEr-00; Sun, 14 Nov 2004 03:43:52 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CT8Ui-000FEn-00 for goblin@nnt.ru; Sun, 14 Nov 2004 03:43:52 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 6AECB570D8; Sun, 14 Nov 2004 00:43:10 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6DDC216A526; Sun, 14 Nov 2004 00:43:05 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43F1116A4CE; Sun, 14 Nov 2004 00:42:55 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB09543D2D; Sun, 14 Nov 2004 00:42:54 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) iAE0gowB009200; Sat, 13 Nov 2004 19:42:50 -0500 (EST) Date: Sat, 13 Nov 2004 19:42:50 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Andrew Moran In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-ports@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.547117, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 00:46:00 -0000 On Sat, 13 Nov 2004, Andrew Moran wrote: > > I made the jump from 5.21 to 5.3 earlier and started getting the > infamous "Fatal error 'Spinlock called when not threaded.' at line 83 > in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" > everytime I ran gnucash. I suggest you move /usr/lib/libc_r.so* and /usr/lib/libthr.so* out of the way and see what happens. You also want to make sure you're not using a statically built program. -- Dan Eischen _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 04:30:13 2004 Return-Path: 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 43EDD16A4D0; Sun, 14 Nov 2004 04:30:13 +0000 (GMT) Received: from celebrian.forsythia.net (galadriel.forsythia.net [64.81.65.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id D913F43D64; Sun, 14 Nov 2004 04:30:12 +0000 (GMT) (envelope-from amoran@forsythia.net) Received: from [10.200.1.101] (cerberus.forsythia.net [64.81.65.55]) iAE4TqES050880; Sat, 13 Nov 2004 20:29:57 -0800 (PST) (envelope-from amoran@forsythia.net) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Moran Date: Sat, 13 Nov 2004 20:29:52 -0800 To: Daniel Eischen X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 04:30:13 -0000 Okay this is weird! If I move libc_r.* out of /usr/lib and into /tmp, then gnucash will run without a problem! if I move it back, it crashes again. I moved it out of the way and recompiled it (portupgrade -fR gnucash).. It built fine (like it did before) and runs.. but as soon as I move libc_r.* back into /usr/lib, it crashes. :( Do I need libc_r in /usr/lib? is it safe to move them? Everytime I rebuild world, it'll just put it back, I'm guessing. Ugh. --Andy On Nov 13, 2004, at 4:42 PM, Daniel Eischen wrote: > On Sat, 13 Nov 2004, Andrew Moran wrote: > >> >> I made the jump from 5.21 to 5.3 earlier and started getting the >> infamous "Fatal error 'Spinlock called when not threaded.' at line 83 >> in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" >> everytime I ran gnucash. > > I suggest you move /usr/lib/libc_r.so* and /usr/lib/libthr.so* out > of the way and see what happens. You also want to make sure you're > not using a statically built program. > > -- > Dan Eischen > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 04:35:41 2004 Return-Path: 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 296FA16A4D0 for ; Sun, 14 Nov 2004 04:35:41 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF01C43D1F for ; Sun, 14 Nov 2004 04:35:40 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTC2I-000K5D-00 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 07:30:46 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTC2H-000K4q-00; Sun, 14 Nov 2004 07:30:45 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTC2G-000K4f-00 for goblin@nnt.ru; Sun, 14 Nov 2004 07:30:45 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 9F23A55D1E; Sun, 14 Nov 2004 04:30:38 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 97FE716A501; Sun, 14 Nov 2004 04:30:20 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 43EDD16A4D0; Sun, 14 Nov 2004 04:30:13 +0000 (GMT) Received: from celebrian.forsythia.net (galadriel.forsythia.net [64.81.65.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id D913F43D64; Sun, 14 Nov 2004 04:30:12 +0000 (GMT) (envelope-from amoran@forsythia.net) Received: from [10.200.1.101] (cerberus.forsythia.net [64.81.65.55]) iAE4TqES050880; Sat, 13 Nov 2004 20:29:57 -0800 (PST) (envelope-from amoran@forsythia.net) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Moran Date: Sat, 13 Nov 2004 20:29:52 -0800 To: Daniel Eischen X-Mailer: Apple Mail (2.619) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-ports@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.516922, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 04:35:41 -0000 Okay this is weird! If I move libc_r.* out of /usr/lib and into /tmp, then gnucash will run without a problem! if I move it back, it crashes again. I moved it out of the way and recompiled it (portupgrade -fR gnucash).. It built fine (like it did before) and runs.. but as soon as I move libc_r.* back into /usr/lib, it crashes. :( Do I need libc_r in /usr/lib? is it safe to move them? Everytime I rebuild world, it'll just put it back, I'm guessing. Ugh. --Andy On Nov 13, 2004, at 4:42 PM, Daniel Eischen wrote: > On Sat, 13 Nov 2004, Andrew Moran wrote: > >> >> I made the jump from 5.21 to 5.3 earlier and started getting the >> infamous "Fatal error 'Spinlock called when not threaded.' at line 83 >> in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" >> everytime I ran gnucash. > > I suggest you move /usr/lib/libc_r.so* and /usr/lib/libthr.so* out > of the way and see what happens. You also want to make sure you're > not using a statically built program. > > -- > Dan Eischen > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-unsubscribe@freebsd.org" _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 08:04:20 2004 Return-Path: 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 A87D216A4CE for ; Sun, 14 Nov 2004 08:04:20 +0000 (GMT) Received: from ns2.cksoft.de (mx21.cksoft.de [217.115.158.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC2A643D2D for ; Sun, 14 Nov 2004 08:04:19 +0000 (GMT) (envelope-from ck-lists@cksoft.de) Received: from vesihiisi.cksoft.de (unknown [192.168.64.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ns2.cksoft.de (Postfix) with ESMTP id DB9F42A461; Sun, 14 Nov 2004 09:04:17 +0100 (CET) Received: from vesihiisi.cksoft.de (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 379FD1EBD; Sun, 14 Nov 2004 09:04:17 +0100 (CET) Received: by vesihiisi.cksoft.de (Postfix, from userid 1000) id 97F491EBC; Sun, 14 Nov 2004 09:04:14 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by vesihiisi.cksoft.de (Postfix) with ESMTP id 909C51EB0; Sun, 14 Nov 2004 09:04:14 +0100 (CET) Date: Sun, 14 Nov 2004 09:04:14 +0100 (CET) From: Christian Kratzer X-X-Sender: ck@vesihiisi.cksoft.de To: Ivan Voras In-Reply-To: <4196440A.7050706@fer.hr> Message-ID: <20041114090240.S58652@vesihiisi.cksoft.de> References: <4196398D.2030000@fer.hr> <32180.1100365616@critter.freebsd.dk> <4196440A.7050706@fer.hr> X-Spammer-Kill-Ratio: 75% MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on vesihiisi.cksoft.de cc: current@freebsd.org Subject: Re: Passwd format? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Christian Kratzer List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 08:04:20 -0000 Hi, On Sat, 13 Nov 2004, Ivan Voras wrote: > Poul-Henning Kamp wrote: >> In message <4196398D.2030000@fer.hr>, Ivan Voras writes: >> >>> The Handbook and crypt(3) say passwords in master.passwd are MD5 hashes >>> if they start with $1$, for example: >>> >>> $1$DP.s8oCc$VJo0/026/S5ng6HlD1Sz8/ >>> >>> the format is $1$salt$rest. I have several questions: >>> >>> How are the values encoded? This looks something like base64. > >> Search for "md5crypt.c" in google and you'll find the source. > > This looks like it: > http://mia.ece.uic.edu/cgi-bin/lxr/http/source/md5crypt.c?v=openssh-3.5p1 > > It seems it's definitely NOT reusable in LDAP :( openldap handles md5 password hashes out of the box. See the slapd.conf man page for details. Greetings Christian -- Christian Kratzer ck@cksoft.de CK Software GmbH http://www.cksoft.de/ Phone: +49 7452 889 135 Fax: +49 7452 889 136 From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 09:03:24 2004 Return-Path: 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 A258216A4CE; Sun, 14 Nov 2004 09:03:24 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5E2B43D5A; Sun, 14 Nov 2004 09:03:23 +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 iAE93Mfb084100; Sun, 14 Nov 2004 11:03:22 +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 61921-16; Sun, 14 Nov 2004 11:03:22 +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 iAE93M8c084097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Nov 2004 11:03:22 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAE93MuR084686; Sun, 14 Nov 2004 11:03:22 +0200 (EET) (envelope-from ru) Date: Sun, 14 Nov 2004 11:03:22 +0200 From: Ruslan Ermilov To: Matteo Riondato , Maxim Sobolev Message-ID: <20041114090322.GC84553@ip.net.ua> References: <1100391439.92272.16.camel@kaiser.sig11.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QRj9sO5tAVLaXnSD" Content-Disposition: inline In-Reply-To: <1100391439.92272.16.camel@kaiser.sig11.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-current@FreeBSD.org Subject: Re: Can anyone MFC /usr/bin/mkuzip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 09:03:24 -0000 --QRj9sO5tAVLaXnSD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 14, 2004 at 01:17:19AM +0100, Matteo Riondato wrote: > Well, Subject can tell you whatever you may need to know ;) >=20 > This utility is there since Fri Sep 10 20:17:31 2004 UTC and has not > been MFC yet. I think it should be merged to allow people to use a > native "compressed filesystem creator" instead of sysutils/cloop-utils, > which is Linux derived, AFAIK. > Thanks in advance. >=20 Why not ask Maxim directly about this? ;) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --QRj9sO5tAVLaXnSD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBlx9aqRfpzJluFF4RAktQAJ4qGGHgQMUg/ZQ6pyNH/VXVFPZWMACfe6N/ l2v7R59lKKGmN/B0ssmKZ/U= =Qobw -----END PGP SIGNATURE----- --QRj9sO5tAVLaXnSD-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 09:07:46 2004 Return-Path: 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 39DBF16A4CE for ; Sun, 14 Nov 2004 09:07:46 +0000 (GMT) Received: from anduin.net (anduin.net [212.12.46.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD3B443D1F for ; Sun, 14 Nov 2004 09:07:45 +0000 (GMT) (envelope-from ltning@anduin.net) Received: from mailnull by anduin.net with dspam-scanned (Exim 4.43 (FreeBSD)) id 1CTGJ1-000OBQ-GM for current@freebsd.org; Sun, 14 Nov 2004 10:04:19 +0100 Received: from mailnull by anduin.net with spamassassin-scanned (Exim 4.43 (FreeBSD)) id 1CTGIy-000OBE-Aw for current@freebsd.org; Sun, 14 Nov 2004 10:04:19 +0100 Received: from ranger.anduin.net ([81.0.162.52] helo=[192.168.1.10]) by anduin.net with esmtp (Exim 4.43 (FreeBSD)) id 1CTGIy-000OBB-5t; Sun, 14 Nov 2004 10:04:16 +0100 In-Reply-To: <4196398D.2030000@fer.hr> References: <4196398D.2030000@fer.hr> Mime-Version: 1.0 (Apple Message framework v675) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <9317D906-361C-11D9-A154-000D9335BCEC@anduin.net> Content-Transfer-Encoding: 7bit From: =?ISO-8859-1?Q?Eirik_=D8verby?= Date: Sun, 14 Nov 2004 10:07:13 +0100 To: Ivan Voras X-Mailer: Apple Mail (2.675) X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on anduin.net X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=7.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 cc: current@freebsd.org Subject: Re: Passwd format? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 09:07:46 -0000 Hi, On the OpenLDAP homepages are a collection of tools that can be used to import existing passwd (and other) data sources into LDAP. I have done this on my ex-NIS-server, and am now using LDAP on all the other servers to authenticate. The passwords were imported just fine, and are working just fine. Took me a while to find those tools though; look here: http://www.padl.com/OSS/MigrationTools.html You might have to hack the scripts slightly to have them run on FreeBSD, but it took me about 2 minutes to do so. Amazing how easy it was after having tried myself for the last 2 days... ;) Good luck! /Eirik On 13. Nov 2004, at 17:42, Ivan Voras wrote: > The Handbook and crypt(3) say passwords in master.passwd are MD5 > hashes if they start with $1$, for example: > > $1$DP.s8oCc$VJo0/026/S5ng6HlD1Sz8/ > > the format is $1$salt$rest. I have several questions: > > How are the values encoded? This looks something like base64. > > Is it possible to actually verify the password against this format > using only a bare implementation of the md5 algorithm? > > Actually, the reason for these questions is that I'm considering using > LDAP authentication on a machine with lots of users and I'm wondering > if existing passwd information could be transported to LDAP. Any > experiences/docs on this? > > Thanks! > _______________________________________________ > 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" > > > Hi, On the OpenLDAP homepages are a collection of tools that can be used to import existing passwd (and other) data sources into LDAP. I have done this on my ex-NIS-server, and am now using LDAP on all the other servers to authenticate. The passwords were imported just fine, and are working just fine. Took me a while to find those tools though; look here: http://www.padl.com/OSS/MigrationTools.html You might have to hack the scripts slightly to have them run on FreeBSD, but it took me about 2 minutes to do so. Amazing how easy it was after having tried myself for the last 2 days... ;) Good luck! /Eirik On 13. Nov 2004, at 17:42, Ivan Voras wrote: The Handbook and crypt(3) say passwords in master.passwd are MD5 hashes if they start with $1$, for example: $1$DP.s8oCc$VJo0/026/S5ng6HlD1Sz8/ the format is $1$salt$rest. I have several questions: How are the values encoded? This looks something like base64. Is it possible to actually verify the password against this format using only a bare implementation of the md5 algorithm? Actually, the reason for these questions is that I'm considering using LDAP authentication on a machine with lots of users and I'm wondering if existing passwd information could be transported to LDAP. Any experiences/docs on this? Thanks! _______________________________________________ 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 14 09:27:35 2004 Return-Path: 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 2D39B16A4CE; Sun, 14 Nov 2004 09:27:35 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1163E43D5A; Sun, 14 Nov 2004 09:27:34 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id 6BD4281DB; Sun, 14 Nov 2004 10:27:32 +0100 (CET) In-Reply-To: <4195E1FF.5090906@DeepCore.dk> References: <25983.1100341229@critter.freebsd.dk> <4195E1FF.5090906@DeepCore.dk> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <69854275-361F-11D9-B78A-000A95A9A574@nordahl.net> Content-Transfer-Encoding: quoted-printable From: Frode Nordahl Date: Sun, 14 Nov 2004 10:27:32 +0100 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= X-Mailer: Apple Mail (2.619) cc: Robert Watson cc: Zoltan Frombach cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: Garance A Drosihn Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 09:27:35 -0000 On Nov 13, 2004, at 11:29, S=F8ren Schmidt wrote: > Poul-Henning Kamp wrote: >> In message <4195DB3E.2040807@DeepCore.dk>,=20 >> =3D?ISO-8859-1?Q?S=3DF8ren_Schmidt?=3D wri >> tes: >>>> It is not really the task of the ata driver to fail requests at = that >>>> time. How long is the timeout anyway ? >>> >>> Oh, ATA doesn't fail them, it just yells that the request hasn't=20 >>> been finished yet by the upper layers, it doesn't do anything to the=20= >>> request. >>> >>> Timeout is 5 secs, which is a pretty long time in this context = IMHO.. >> Five seconds counted from when ? > > Now thats the nasty part :) > ATA starts the timeout when the request is issued to the device, so=20 > theoretically the disk could take 4.9999 secs to complete the request=20= > and then the timeout fires before the taskqueue gets its chance at it,=20= > but IMHO thats pretty unlikely... > > Anyhow, I can just remove the warning from ATA if that makes anyone=20 > happy, since its just a warning and ATA doesn't do anything with it at=20= > all. > However, IMNHO this points at a problem somewhere that we should=20 > better understand and fix instead. Please don't remove the warning until we can find and fix this problem!=20= Even if it may not be ATA related, your warning is by now the only way=20= to tell me when the problem occurs :-) I have two brand new systems which I have installed 5.3-R on who show=20 this problem. They are two way 3.06GHz Xeons, and when run in SMP mode,=20= the system will often panic shortly after these warnings occur, most=20 often in UFS code. Since we don't know what or where the problem is, the traces might be=20 completely bogus, but I include them anyway:=20 http://home.powertech.no/frode/freebsd/ I have just installed CURRENT on one of them, haven't gotten around to=20= make it crash yet, but I get this: ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D119959919 ad4: FAILURE - WRITE_DMA timed out g_vfs_done():ad4s1f[WRITE(offset=3D43971141632, length=3D2048)]error =3D = 5 initiate_write_filepage: already started ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D120428639 ad4: FAILURE - WRITE_DMA timed out g_vfs_done():ad4s1f[WRITE(offset=3D44211126272, length=3D16384)]error =3D = 5 =46rom ffs_softdep.c: if (pagedep->pd_state & IOSTARTED) { /* * This can only happen if there is a driver that does=20= not * understand chaining. Here biodone will reissue the=20= call * to strategy for the incomplete buffers. */ printf("initiate_write_filepage: already started\n"); return; } Mvh, Frode Nordahl > --=20 > > -S=F8ren > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to=20 > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 09:47:56 2004 Return-Path: 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 52EAB16A4CE for ; Sun, 14 Nov 2004 09:47:56 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0EB743D48 for ; Sun, 14 Nov 2004 09:47:55 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id 5030F8149 for ; Sun, 14 Nov 2004 10:47:54 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: current@freebsd.org From: Frode Nordahl Date: Sun, 14 Nov 2004 10:47:54 +0100 X-Mailer: Apple Mail (2.619) Subject: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 09:47:56 -0000 Hello, I have a Intel SE7505VB2 board with two 3.06GHz Xeons I have disabled HTT in BIOS, but FreeBSD says this during boot anyway: Hyperthreading: 2 logical CPUs Is this harmless, or does this mean the scheduler is running with HTT awareness? Mvh, Frode Nordahl 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 6.0-CURRENT #1: Sun Nov 14 08:37:55 CET 2004 frode@xxx.yyy.zzz.no:/usr/obj/usr/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 4025942016 (3839 MB) avail memory = 3942326272 (3759 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pcib1: mem 0xf8000000-0xfbffffff at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 2.0 on pci0 pci2: on pcib2 pci2: at device 28.0 (no driver attached) pcib3: at device 29.0 on pci2 pci3: on pcib3 pci2: at device 30.0 (no driver attached) pcib4: at device 31.0 on pci2 pci4: on pcib4 em0: port 0x7000-0x703f mem 0xf0200000-0xf021ffff irq 52 at device 2.0 on pci4 em0: Ethernet address: 00:04:23:ab:d9:bf em0: Speed:N/A Duplex:N/A pci0: at device 2.1 (no driver attached) uhci0: port 0x6800-0x681f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x6820-0x683f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x6840-0x685f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib5: at device 30.0 on pci0 pci5: on pcib5 pci5: at device 2.0 (no driver attached) fxp0: port 0x8400-0x843f mem 0xf0300000-0xf031ffff,0xf0321000-0xf0321fff irq 18 at device 3.0 on pci5 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:04:23:ab:d5:90 atapci0: port 0x8440-0x844f,0x8450-0x8453,0x8458-0x845f,0x8454-0x8457,0x8460-0x8467 mem 0xf0322000-0xf03221ff irq 19 at device 4.0 on pci5 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0x6860-0x686f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xe2000-0xe27ff,0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec witness_get: witness exhausted ad0: 29325MB [59582/16/63] at ata0-master UDMA100 ad4: 78167MB [158816/16/63] at ata2-master SATA150 ad6: 78167MB [158816/16/63] at ata3-master SATA150 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad4s1a From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 09:54:58 2004 Return-Path: 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 AC85516A4CE for ; Sun, 14 Nov 2004 09:54:58 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2777C43D49 for ; Sun, 14 Nov 2004 09:54:58 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAE9upuo013068; Sun, 14 Nov 2004 02:56:51 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41972BA2.3090609@freebsd.org> Date: Sun, 14 Nov 2004 02:55:46 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Frode Nordahl References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> In-Reply-To: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 09:54:58 -0000 Frode Nordahl wrote: > Hello, > > I have a Intel SE7505VB2 board with two 3.06GHz Xeons > > I have disabled HTT in BIOS, but FreeBSD says this during boot anyway: > > Hyperthreading: 2 logical CPUs > > Is this harmless, or does this mean the scheduler is running with HTT > awareness? It's harmless and means that the system _detected_ two logical cores. It doesn't mean that the system used them, and if you look a bit further down you'll see that it mentions cpu0 and cpu1, and no more. Scott > > > Mvh, > Frode Nordahl > > 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 6.0-CURRENT #1: Sun Nov 14 08:37:55 CET 2004 > frode@xxx.yyy.zzz.no:/usr/obj/usr/src/sys/GENERIC > WARNING: WITNESS option enabled, expect reduced performance. > ACPI APIC Table: > Timecounter "i8254" frequency 1193182 Hz quality 0 > CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.50-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbff ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 4025942016 (3839 MB) > avail memory = 3942326272 (3759 MB) > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 6 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-47 on motherboard > ioapic2 irqs 48-71 on motherboard > npx0: [FAST] > npx0: on motherboard > npx0: INT 16 interface > acpi0: on motherboard > acpi0: Power Button (fixed) > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 > cpu0: on acpi0 > cpu1: on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > agp0: mem 0xf4000000-0xf7ffffff at > device 0.0 on pci0 > pci0: at device 0.1 (no driver attached) > pcib1: mem 0xf8000000-0xfbffffff at device 1.0 on > pci0 > pci1: on pcib1 > pcib2: at device 2.0 on pci0 > pci2: on pcib2 > pci2: at device 28.0 (no driver > attached) > pcib3: at device 29.0 on pci2 > pci3: on pcib3 > pci2: at device 30.0 (no driver > attached) > pcib4: at device 31.0 on pci2 > pci4: on pcib4 > em0: port > 0x7000-0x703f mem 0xf0200000-0xf021ffff irq 52 at device 2.0 on pci4 > em0: Ethernet address: 00:04:23:ab:d9:bf > em0: Speed:N/A Duplex:N/A > pci0: at device 2.1 (no driver attached) > uhci0: port 0x6800-0x681f > irq 16 at device 29.0 on pci0 > uhci0: [GIANT-LOCKED] > usb0: on uhci0 > usb0: USB revision 1.0 > uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > uhci1: port 0x6820-0x683f > irq 19 at device 29.1 on pci0 > uhci1: [GIANT-LOCKED] > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > uhci2: port 0x6840-0x685f > irq 18 at device 29.2 on pci0 > uhci2: [GIANT-LOCKED] > usb2: on uhci2 > usb2: USB revision 1.0 > uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub2: 2 ports with 2 removable, self powered > pcib5: at device 30.0 on pci0 > pci5: on pcib5 > pci5: at device 2.0 (no driver attached) > fxp0: port 0x8400-0x843f mem > 0xf0300000-0xf031ffff,0xf0321000-0xf0321fff irq 18 at device 3.0 on pci5 > miibus0: on fxp0 > inphy0: on miibus0 > inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fxp0: Ethernet address: 00:04:23:ab:d5:90 > atapci0: port > 0x8440-0x844f,0x8450-0x8453,0x8458-0x845f,0x8454-0x8457,0x8460-0x8467 > mem 0xf0322000-0xf03221ff irq 19 at device 4.0 on pci5 > ata2: channel #0 on atapci0 > ata3: channel #1 on atapci0 > isab0: at device 31.0 on pci0 > isa0: on isab0 > atapci1: port > 0x6860-0x686f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 > ata0: channel #0 on atapci1 > ata1: channel #1 on atapci1 > pci0: at device 31.3 (no driver attached) > acpi_button0: on acpi0 > atkbdc0: port 0x64,0x60 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq > 6 drq 2 on acpi0 > fdc0: [FAST] > sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on > acpi0 > sio0: type 16550A, console > sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 > sio1: type 16550A > ppc0: port 0x778-0x77b,0x378-0x37f irq 7 > drq 3 on acpi0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > ppbus0: on ppc0 > plip0: on ppbus0 > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > orm0: at iomem > 0xe2000-0xe27ff,0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 > pmtimer0 on isa0 > sc0: at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=0x100> > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > Timecounters tick every 1.000 msec > witness_get: witness exhausted > ad0: 29325MB [59582/16/63] at ata0-master > UDMA100 > ad4: 78167MB [158816/16/63] at ata2-master > SATA150 > ad6: 78167MB [158816/16/63] at ata3-master > SATA150 > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/ad4s1a > > _______________________________________________ > 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 14 10:01:22 2004 Return-Path: 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 7AE3416A4CE for ; Sun, 14 Nov 2004 10:01:22 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 045EC43D39 for ; Sun, 14 Nov 2004 10:01:22 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so541811rnf for ; Sun, 14 Nov 2004 02:01:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=KAPJHD2/3YRFZX1FMNQeLHKXnGTIc+oDqQ7oszYUtS6Y6yKgvzii99wDHg0LYR878i6/xWCSt8N8CfV0cxMpVs9rAa1kquLjp0Kk9lOGNtp0rmPwsHxos7oRIi2Yo7iIsR18DfM5dsDIKaZRCspUeVUUC4/HElokFtZBXJWG5rk= Received: by 10.38.89.50 with SMTP id m50mr306560rnb; Sun, 14 Nov 2004 02:01:21 -0800 (PST) Received: by 10.38.79.65 with HTTP; Sun, 14 Nov 2004 02:01:21 -0800 (PST) Message-ID: Date: Sun, 14 Nov 2004 02:01:21 -0800 From: Pascal Hofstee To: Scott Long In-Reply-To: <41972BA2.3090609@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> cc: Frode Nordahl cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pascal Hofstee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 10:01:22 -0000 On Sun, 14 Nov 2004 02:55:46 -0700, Scott Long wrote: > It's harmless and means that the system _detected_ two logical cores. > It doesn't mean that the system used them, and if you look a bit > further down you'll see that it mentions cpu0 and cpu1, and no more. and if you look at the bottom of that log ... you notice SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad4s1a this is definately SMP kicking in and "launching" the 2nd logical CPU .. CPU #0 being the first logical CPU. From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 10:46:45 2004 Return-Path: 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 365F216A4CE for ; Sun, 14 Nov 2004 10:46:45 +0000 (GMT) Received: from santiago.pacific.net.sg (santiago.pacific.net.sg [203.120.90.135]) by mx1.FreeBSD.org (Postfix) with SMTP id 0E96243D55 for ; Sun, 14 Nov 2004 10:46:44 +0000 (GMT) (envelope-from oceanare@pacific.net.sg) Received: (qmail 7822 invoked from network); 14 Nov 2004 10:46:42 -0000 Received: from unknown (HELO maxwell6.pacific.net.sg) (203.120.90.212) by santiago with SMTP; 14 Nov 2004 10:46:42 -0000 Received: from [192.168.0.109] ([210.24.202.7]) by maxwell6.pacific.net.sg with ESMTP <20041114104642.VPXM17051.maxwell6.pacific.net.sg@[192.168.0.109]>; Sun, 14 Nov 2004 18:46:42 +0800 Message-ID: <419737C4.3000300@pacific.net.sg> Date: Sun, 14 Nov 2004 18:47:32 +0800 From: Erich Dollansky Organization: oceanare pte ltd User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pascal Hofstee References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Frode Nordahl cc: Scott Long cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 10:46:45 -0000 Hi, Pascal Hofstee wrote: > On Sun, 14 Nov 2004 02:55:46 -0700, Scott Long wrote: > >>It's harmless and means that the system _detected_ two logical cores. >>It doesn't mean that the system used them, and if you look a bit >>further down you'll see that it mentions cpu0 and cpu1, and no more. > > > and if you look at the bottom of that log ... you notice > > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/ad4s1a > > this is definately SMP kicking in and "launching" the 2nd logical CPU > .. CPU #0 being the first logical CPU. He said that there are two CPUs in the box. So, he uses an SMP kernel to make use of them but he does not use HTT. Erich From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 11:10:05 2004 Return-Path: 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 D1DCB16A4CE for ; Sun, 14 Nov 2004 11:10:05 +0000 (GMT) Received: from moya.lambermont.dyndns.org (j226018.upc-j.chello.nl [24.132.226.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 716A843D2F for ; Sun, 14 Nov 2004 11:10:05 +0000 (GMT) (envelope-from hans@lambermont.dyndns.org) Received: from localhost (localhost [127.0.0.1]) by moya.lambermont.dyndns.org (Postfix) with ESMTP id C050636402; Sun, 14 Nov 2004 12:10:09 +0100 (CET) Received: from moya.lambermont.dyndns.org ([127.0.0.1])port 10024) with ESMTP id 15790-01; Sun, 14 Nov 2004 12:10:09 +0100 (CET) Received: by moya.lambermont.dyndns.org (Postfix, from userid 1001) id 13C3A36401; Sun, 14 Nov 2004 12:10:09 +0100 (CET) Date: Sun, 14 Nov 2004 12:10:08 +0100 To: "Bjoern A. Zeeb" Message-ID: <20041114111008.GG40364@moya.lambermont.dyndns.org> References: <200411121739.40804.peter@wemm.org> <20041113194849.GE40364@moya.lambermont.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i From: hans@lambermont.dyndns.org (Hans Lambermont) X-Virus-Scanned: by amavisd-new-20030616.p5 at lambermont.dyndns.org cc: FreeBSD current mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 11:10:05 -0000 Bjoern A. Zeeb wrote: > On Sat, 13 Nov 2004, Hans Lambermont wrote: >> I have a Marvell Semiconductor, Inc. Yukon 88E8000 on my Asus P4P800-E >> (according to dmesg that is, the booklet claims it's a 88E8001). >> >> Using the patch on a stock 5.3R system did not help (could not even get > > could you please also apply the patches from > http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk_vpd.diff > and > http://sources.zabbadoz.net/freebsd/patchset/EXPERIMENTAL/if_sk_eprom_debug.diff > and send me the output ? Thanks. skc0: port 0xd800-0xd8ff mem 0xfeaf8000-0xfeafbfff irq 22 at device 5.0 on pci2 skc0: type = YUKON skc0: SK_EPROM0 = 0x10 skc0: SRAM size = 0x010000 skc0: chip ver 0xb1 skc0: chip conf 0x73 skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter skc0: PN: Yukon 88E8001 skc0: EC: Rev. 1.3 skc0: MN: Marvell skc0: SN: AbCdEfG334454 sk0: on skc0 sk0: Ethernet address: 00:11:2f:98:06:4a miibus0: on sk0 e1000phy0: on miibus0 e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX, auto skc0: [GIANT-LOCKED] It's connected to a 100baseTX NetGear hub and it autoselects to 100baseTX but only half-duplex. regards, Hans ps. weird serial number ;-) -- http://lambermont.webhop.org/ () ASCII-ribbon campaign against vCards, /\ HTML-mail and proprietary formats. From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 11:51:09 2004 Return-Path: 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 3516916A4CE for ; Sun, 14 Nov 2004 11:51:09 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E8D043D64 for ; Sun, 14 Nov 2004 11:51:08 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id 64E3282D8; Sun, 14 Nov 2004 12:51:06 +0100 (CET) In-Reply-To: <69854275-361F-11D9-B78A-000A95A9A574@nordahl.net> References: <25983.1100341229@critter.freebsd.dk> <4195E1FF.5090906@DeepCore.dk> <69854275-361F-11D9-B78A-000A95A9A574@nordahl.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/mixed; boundary=Apple-Mail-1--280701881 Message-Id: <777BB005-3633-11D9-B78A-000A95A9A574@nordahl.net> From: Frode Nordahl Date: Sun, 14 Nov 2004 12:51:05 +0100 To: Frode Nordahl X-Mailer: Apple Mail (2.619) cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 11:51:09 -0000 --Apple-Mail-1--280701881 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Hello, Got my -CURRENT panic now, while running bonnie++ -r 4096 ad4: FAILURE - WRITE_DMA timed out ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131246815 ad4: FAILURE - WRITE_DMA timed out g_vfs_done():ad4s1f[WRITE(offset=49750032384, length=131072)]error = 5 ad4: timeout state=0 unexpected ad4: timeout state=0 unexpected ad4: timeout state=0 unexpected ad4: FAILURE - unknown BIO operation Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 06 fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc05de440 stack pointer = 0x10:0xe9389c18 frame pointer = 0x10:0xe9389c24 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 = 4 (g_down) [thread 100073] Stopped at g_disk_done+0xcc: movl 0xc(%eax),%eax db> trace g_disk_done(c6254420,0,5,c077d824,e9389c6c) at g_disk_done+0xcc ad_start(c55644ac,0,c6254420,c580ce80,e9389cd0) at ad_start+0x7c ata_start(c5564400,0,0,0,0) at ata_start+0x265 g_disk_start(c6254420,15740000,13,c580cb00,5b07e00) at g_disk_start+0x88 g_io_schedule_down(c549c480,c54aa000,e9389d34,c05ff130,0) at g_io_schedule_down+0xac g_down_procbody(0,e9389d48,0,c05e0724,0) at g_down_procbody+0x1a fork_exit(c05e0724,0,e9389d48) at fork_exit+0x58 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe9389d7c, ebp = 0 --- db> dmesg: --Apple-Mail-1--280701881 Content-Transfer-Encoding: 7bit Content-Type: text/plain; x-unix-mode=0644; name="dmesg.txt" Content-Disposition: attachment; filename=dmesg.txt 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 6.0-CURRENT #1: Sun Nov 14 12:10:59 CET 2004 frode@xxx.yyy.zzz.no:/usr/obj/usr/src/sys/PT ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.06GHz (3056.50-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 4025942016 (3839 MB) avail memory = 3942326272 (3759 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 6 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: on acpi0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf4000000-0xf7ffffff at device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pcib1: mem 0xf8000000-0xfbffffff at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 2.0 on pci0 pci2: on pcib2 pci2: at device 28.0 (no driver attached) pcib3: at device 29.0 on pci2 pci3: on pcib3 pci2: at device 30.0 (no driver attached) pcib4: at device 31.0 on pci2 pci4: on pcib4 em0: port 0x7000-0x703f mem 0xf0200000-0xf021ffff irq 52 at device 2.0 on pci4 em0: Ethernet address: 00:04:23:ab:d9:bf em0: Speed:N/A Duplex:N/A pci0: at device 2.1 (no driver attached) uhci0: port 0x6800-0x681f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0x6820-0x683f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0x6840-0x685f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pcib5: at device 30.0 on pci0 pci5: on pcib5 pci5: at device 2.0 (no driver attached) fxp0: port 0x8400-0x843f mem 0xf0300000-0xf031ffff,0xf0321000-0xf0321fff irq 18 at device 3.0 on pci5 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:04:23:ab:d5:90 atapci0: port 0x8440-0x844f,0x8450-0x8453,0x8458-0x845f,0x8454-0x8457,0x8460-0x8467 mem 0xf0322000-0xf03221ff irq 19 at device 4.0 on pci5 ata2: channel #0 on atapci0 ata3: channel #1 on atapci0 isab0: at device 31.0 on pci0 isa0: on isab0 atapci1: port 0x6860-0x686f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on pci0 ata0: channel #0 on atapci1 ata1: channel #1 on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: port 0x3f7,0x3f4-0x3f5,0x3f0-0x3f3 irq 6 drq 2 on acpi0 fdc0: [FAST] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A, console sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 orm0: at iomem 0xe2000-0xe27ff,0xc8000-0xcc7ff,0xc0000-0xc7fff on isa0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec ad0: 29325MB [59582/16/63] at ata0-master UDMA100 ad4: 78167MB [158816/16/63] at ata2-master SATA150 ad6: 78167MB [158816/16/63] at ata3-master SATA150 SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted WARNING: /tmp was not properly dismounted WARNING: /usr was not properly dismounted WARNING: /var was not properly dismounted --Apple-Mail-1--280701881 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed Mvh, Frode Nordahl --Apple-Mail-1--280701881-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 13:47:32 2004 Return-Path: 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 240D716A4CE for ; Sun, 14 Nov 2004 13:47:32 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4417343D41 for ; Sun, 14 Nov 2004 13:47:31 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id 00AFE81E4; Sun, 14 Nov 2004 14:47:30 +0100 (CET) In-Reply-To: <777BB005-3633-11D9-B78A-000A95A9A574@nordahl.net> References: <25983.1100341229@critter.freebsd.dk> <4195E1FF.5090906@DeepCore.dk> <69854275-361F-11D9-B78A-000A95A9A574@nordahl.net> <777BB005-3633-11D9-B78A-000A95A9A574@nordahl.net> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sun, 14 Nov 2004 14:47:28 +0100 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= X-Mailer: Apple Mail (2.619) cc: Poul-Henning Kamp cc: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 13:47:32 -0000 Hello, This was on a kernel running with the small patch you posted earlier in this thread, so this is bogus :-( I haven't made clean -CURRENT panic in conjunction with these messages yet. But does it tell us anything, or is this just noise? Mvh, Frode Nordahl On Nov 14, 2004, at 12:51, Frode Nordahl wrote: > Hello, > > Got my -CURRENT panic now, while running bonnie++ -r 4096 > > ad4: FAILURE - WRITE_DMA timed out > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=131246815 > ad4: FAILURE - WRITE_DMA timed out > g_vfs_done():ad4s1f[WRITE(offset=49750032384, length=131072)]error = 5 > ad4: timeout state=0 unexpected > ad4: timeout state=0 unexpected > ad4: timeout state=0 unexpected > ad4: FAILURE - unknown BIO operation > > Fatal trap 12: page fault while in kernel mode > cpuid = 1; apic id = 06 > fault virtual address = 0xc > fault code = supervisor read, page not present > instruction pointer = 0x8:0xc05de440 > stack pointer = 0x10:0xe9389c18 > frame pointer = 0x10:0xe9389c24 > 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 = 4 (g_down) > [thread 100073] > Stopped at g_disk_done+0xcc: movl 0xc(%eax),%eax > > db> trace > g_disk_done(c6254420,0,5,c077d824,e9389c6c) at g_disk_done+0xcc > ad_start(c55644ac,0,c6254420,c580ce80,e9389cd0) at ad_start+0x7c > ata_start(c5564400,0,0,0,0) at ata_start+0x265 > g_disk_start(c6254420,15740000,13,c580cb00,5b07e00) at > g_disk_start+0x88 > g_io_schedule_down(c549c480,c54aa000,e9389d34,c05ff130,0) at > g_io_schedule_down+0xac > g_down_procbody(0,e9389d48,0,c05e0724,0) at g_down_procbody+0x1a > fork_exit(c05e0724,0,e9389d48) at fork_exit+0x58 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xe9389d7c, ebp = 0 --- > db> > > dmesg: > > > > Mvh, > Frode Nordahl From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 14:25:19 2004 Return-Path: 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 B6A1D16A4CE; Sun, 14 Nov 2004 14:25:19 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73FCE43D46; Sun, 14 Nov 2004 14:25:19 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAEEP1hl032343; Sun, 14 Nov 2004 06:25:01 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAEEP1LG032342; Sun, 14 Nov 2004 06:25:01 -0800 (PST) (envelope-from sgk) Date: Sun, 14 Nov 2004 06:25:01 -0800 From: Steve Kargl To: Andrew Moran Message-ID: <20041114142501.GA32313@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: Daniel Eischen cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 14:25:19 -0000 On Sat, Nov 13, 2004 at 08:29:52PM -0800, Andrew Moran wrote: > > Do I need libc_r in /usr/lib? is it safe to move them? Everytime I > rebuild world, it'll just put it back, I'm guessing. Ugh. > Add "NOLIBC_R=true" to /etc/make.conf. rm /usr/lib/libc_r* make world -- Steve From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 14:31:09 2004 Return-Path: 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 B712816A4CE for ; Sun, 14 Nov 2004 14:31:09 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B68E43D55 for ; Sun, 14 Nov 2004 14:31:09 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTLKj-000LvV-00 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 17:26:25 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTLKi-000Lv1-00; Sun, 14 Nov 2004 17:26:24 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTLKi-000Lu7-00 for goblin@nnt.ru; Sun, 14 Nov 2004 17:26:24 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 649B6576EB; Sun, 14 Nov 2004 14:25:38 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AF1D316A4E5; Sun, 14 Nov 2004 14:25:34 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B6A1D16A4CE; Sun, 14 Nov 2004 14:25:19 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73FCE43D46; Sun, 14 Nov 2004 14:25:19 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAEEP1hl032343; Sun, 14 Nov 2004 06:25:01 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAEEP1LG032342; Sun, 14 Nov 2004 06:25:01 -0800 (PST) (envelope-from sgk) Date: Sun, 14 Nov 2004 06:25:01 -0800 From: Steve Kargl To: Andrew Moran Message-ID: <20041114142501.GA32313@troutmask.apl.washington.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-ports@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.938052, version=0.92.8 cc: Daniel Eischen cc: freebsd-current@freebsd.org cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 14:31:09 -0000 On Sat, Nov 13, 2004 at 08:29:52PM -0800, Andrew Moran wrote: > > Do I need libc_r in /usr/lib? is it safe to move them? Everytime I > rebuild world, it'll just put it back, I'm guessing. Ugh. > Add "NOLIBC_R=true" to /etc/make.conf. rm /usr/lib/libc_r* make world -- Steve _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Nov 13 22:56:41 2004 Return-Path: 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 87B7C16A4CE for ; Sat, 13 Nov 2004 22:56:41 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 392E943D2D for ; Sat, 13 Nov 2004 22:56:41 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CT6kj-000OYs-00 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 01:52:17 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CT6kj-000OYN-00; Sun, 14 Nov 2004 01:52:17 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CT6ki-000OXi-00 for goblin@nnt.ru; Sun, 14 Nov 2004 01:52:16 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 53B5155E0D; Sat, 13 Nov 2004 22:52:00 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7405F16A4D3; Sat, 13 Nov 2004 22:51:58 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E13316A4CE for ; Sat, 13 Nov 2004 22:51:54 +0000 (GMT) Received: from smz.com.ua (smz.com.ua [193.138.84.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC05143D46 for ; Sat, 13 Nov 2004 22:51:52 +0000 (GMT) (envelope-from sla@smz.com.ua) Received: from mailhub (localhost.smz.com.ua [127.0.0.1]) by localhost (Postfix) with ESMTP id E1D60FDD2 for ; Sun, 14 Nov 2004 00:52:27 +0200 (EET) Received: from localhost (localhost.smz.com.ua [127.0.0.1]) by localhost (Postfix) with ESMTP id 6A203FDA1; Sun, 14 Nov 2004 00:52:25 +0200 (EET) Received: from smz.com.ua ([127.0.0.1]) by localhost (smz.com.ua [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03525-10; Sun, 14 Nov 2004 00:52:23 +0200 (EET) Received: from deep.msu0 (unknown [192.168.0.129]) by smz.com.ua (Postfix) with ESMTP id 5AB3AFD9D; Sun, 14 Nov 2004 00:52:22 +0200 (EET) From: Slava To: freebsd-ports@freebsd.org Date: Sun, 14 Nov 2004 00:51:41 +0200 User-Agent: KMail/1.7 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: <200411140051.42438.sla@smz.com.ua> X-Virus-Scanned: by amavisd-clamav at smz.com.ua X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-ports@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.569380, version=0.92.8 X-Mailman-Approved-At: Sun, 14 Nov 2004 14:31:35 +0000 cc: freebsd-current@freebsd.org cc: Andrew Moran Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 22:56:41 -0000 more /usr/src/UPDATING /20040303 man libmap.conf > I made the jump from 5.21 to 5.3 earlier and started getting the > infamous "Fatal error 'Spinlock called when not threaded.' at line 83 > in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" > everytime I ran gnucash. > I asked the freebsd-questions list but have gotten no response. So > in desperation, I'm broadening my quest. I don't want to reinstall > the server from scratch if there is another way to fix this error. > Could there be something in my kernel configuration causing this? I > can't find a reference to libc_r or libkse *anywhere*. :/ > > Does anyone have any ideas for me to try? Thank you for your time. > > --And > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Vyacheslav Bocharov VB29-UANIC _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 16:39:41 2004 Return-Path: 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 74EB716A4CE for ; Sun, 14 Nov 2004 16:39:41 +0000 (GMT) Received: from web.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5C6B43D39 for ; Sun, 14 Nov 2004 16:39:40 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.1.100] (xDSL-2-2.united.net.ua [193.111.9.226]) (authenticated bits=0) by web.portaone.com (8.12.11/8.12.11) with ESMTP id iAEGdZhf041329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Nov 2004 17:39:38 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <41978A3E.30606@portaone.com> Date: Sun, 14 Nov 2004 18:39:26 +0200 From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: rionda@gufi.org References: <1100391439.92272.16.camel@kaiser.sig11.org> In-Reply-To: <1100391439.92272.16.camel@kaiser.sig11.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.ORG Subject: Re: Can anyone MFC /usr/bin/mkuzip? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 16:39:41 -0000 Done. Have phun! -Maxim Matteo Riondato wrote: > Well, Subject can tell you whatever you may need to know ;) > > This utility is there since Fri Sep 10 20:17:31 2004 UTC and has not > been MFC yet. I think it should be merged to allow people to use a > native "compressed filesystem creator" instead of sysutils/cloop-utils, > which is Linux derived, AFAIK. > Thanks in advance. > Best Regards From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 17:57:18 2004 Return-Path: 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 C2B4016A4CE for ; Sun, 14 Nov 2004 17:57:18 +0000 (GMT) Received: from mail-fs.sunrise.ch (mta-fs-be-04.sunrise.ch [194.158.229.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A588643D2F for ; Sun, 14 Nov 2004 17:57:17 +0000 (GMT) (envelope-from triulzi@freesurf.ch) Received: from [62.167.186.99] (62.167.186.99) by mail-fs.sunrise.ch (7.0.036) id 418ABE17003D71BB for freebsd-current@freebsd.org; Sun, 14 Nov 2004 18:57:16 +0100 Message-ID: <41979C79.6070602@freesurf.ch> Date: Sun, 14 Nov 2004 18:57:13 +0100 From: Mauro Triulzi User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) 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: NDIS miniport wrapper: routines probably not implemented X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 17:57:18 -0000 Hallo, I have a problem with the ndis miniport wrapper for my thinkpad T42p: My WLAN Card is a built in (IBM) MiniPCI 802.11a/b/g WLAN Card in the IBM Thinkpad T42-2373-WBZ P-M/1.7. I downloaded the drivers for Windows 2000/XP from http://www-307.ibm.com/pc/support/site.wss/document.do?lndocid=MIGR-55386 and created ndis_driver_data.h in the canonical way as ndiscvt -i /path/to/NET5211.INF -s /path/to/AR5211.SYS -o ndis_driver_data.h (I had to delete some rows in NET5211.INF to do that) Now kldload if_ndis let the kernel panic (sorry, but could't copy and paste ;-)) ndis0: <11a/b/g Wireless LAN 802.11.a/b/g Mini PCI Adapter> no match for MmUnmapIoSpace no match for MmMapIoSpace ndis0: NDIS API version: 5.1 I think that the reason is that the the two functions above are not implemented (yet). I would be very grateful if someone (Bill?) could implement these functions. Many thanks and kind regards, Mauro From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 18:07:05 2004 Return-Path: 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 607FC16A4D0; Sun, 14 Nov 2004 18:07:05 +0000 (GMT) Received: from celebrian.forsythia.net (galadriel.forsythia.net [64.81.65.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01DB243D1D; Sun, 14 Nov 2004 18:07:05 +0000 (GMT) (envelope-from amoran@forsythia.net) Received: from [10.200.1.101] (cerberus.forsythia.net [64.81.65.55]) iAEI6rgl060129; Sun, 14 Nov 2004 10:06:54 -0800 (PST) (envelope-from amoran@forsythia.net) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041114142501.GA32313@troutmask.apl.washington.edu> References: <20041114142501.GA32313@troutmask.apl.washington.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Moran Date: Sun, 14 Nov 2004 10:06:56 -0800 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.619) Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 18:07:05 -0000 Okay I'll try that and just live without libc_r. Thanks for all your help guys! --Andy On Nov 14, 2004, at 6:25 AM, Steve Kargl wrote: > On Sat, Nov 13, 2004 at 08:29:52PM -0800, Andrew Moran wrote: >> >> Do I need libc_r in /usr/lib? is it safe to move them? Everytime I >> rebuild world, it'll just put it back, I'm guessing. Ugh. >> > > Add "NOLIBC_R=true" to /etc/make.conf. > rm /usr/lib/libc_r* > make world > > -- > Steve > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-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" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 18:11:07 2004 Return-Path: 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 6CB5916A4CE for ; Sun, 14 Nov 2004 18:11:07 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0CB3743D49 for ; Sun, 14 Nov 2004 18:11:07 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTOn9-000OtE-00 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 21:07:59 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTOn9-000Ot5-00; Sun, 14 Nov 2004 21:07:59 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTOn9-000Ot2-00 for goblin@nnt.ru; Sun, 14 Nov 2004 21:07:59 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 70FCA57067; Sun, 14 Nov 2004 18:07:20 +0000 (GMT) (envelope-from owner-freebsd-ports@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 77E7516A521; Sun, 14 Nov 2004 18:07:16 +0000 (GMT) Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 607FC16A4D0; Sun, 14 Nov 2004 18:07:05 +0000 (GMT) Received: from celebrian.forsythia.net (galadriel.forsythia.net [64.81.65.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01DB243D1D; Sun, 14 Nov 2004 18:07:05 +0000 (GMT) (envelope-from amoran@forsythia.net) Received: from [10.200.1.101] (cerberus.forsythia.net [64.81.65.55]) iAEI6rgl060129; Sun, 14 Nov 2004 10:06:54 -0800 (PST) (envelope-from amoran@forsythia.net) Mime-Version: 1.0 (Apple Message framework v619) In-Reply-To: <20041114142501.GA32313@troutmask.apl.washington.edu> References: <20041114142501.GA32313@troutmask.apl.washington.edu> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Andrew Moran Date: Sun, 14 Nov 2004 10:06:56 -0800 To: freebsd-current@freebsd.org, freebsd-ports@freebsd.org X-Mailer: Apple Mail (2.619) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-ports@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.569185, version=0.92.8 Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 18:11:07 -0000 Okay I'll try that and just live without libc_r. Thanks for all your help guys! --Andy On Nov 14, 2004, at 6:25 AM, Steve Kargl wrote: > On Sat, Nov 13, 2004 at 08:29:52PM -0800, Andrew Moran wrote: >> >> Do I need libc_r in /usr/lib? is it safe to move them? Everytime I >> rebuild world, it'll just put it back, I'm guessing. Ugh. >> > > Add "NOLIBC_R=true" to /etc/make.conf. > rm /usr/lib/libc_r* > make world > > -- > Steve > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to > "freebsd-ports-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" _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 18:27:29 2004 Return-Path: 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 371DD16A4CE; Sun, 14 Nov 2004 18:27:29 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF47A43D1D; Sun, 14 Nov 2004 18:27:28 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAEIRSvk037024; Sun, 14 Nov 2004 13:27:28 -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.1/8.13.1) with ESMTP id iAEIRRJF036355; Sun, 14 Nov 2004 13:27:27 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id AB0497306E; Sun, 14 Nov 2004 13:27:27 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041114182727.AB0497306E@freebsd-current.sentex.ca> Date: Sun, 14 Nov 2004 13:27:27 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/585/Thu Nov 11 07:22:42 2004 clamav-milter version 0.80j on clamscanner3 X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 18:27:29 -0000 TB --- 2004-11-14 16:44:37 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-14 16:44:37 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-11-14 16:44:38 - checking out the source tree TB --- 2004-11-14 16:44:38 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-11-14 16:44:38 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-14 16:50:51 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-14 16:50:51 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-14 16:50:51 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2004-11-14 17:57:17 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-14 17:57:17 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-14 17:57:17 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Sun Nov 14 17:57:17 UTC 2004 >>> 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 >>> Kernel build for GENERIC completed on Sun Nov 14 18:13:43 UTC 2004 TB --- 2004-11-14 18:13:43 - generating LINT kernel config TB --- 2004-11-14 18:13:43 - cd /home/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- 2004-11-14 18:13:43 - /usr/bin/make -B LINT TB --- 2004-11-14 18:13:43 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-14 18:13:43 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-14 18:13:43 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sun Nov 14 18:13:43 UTC 2004 >>> 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 [...] ===> acpi/acpi_snc (all) cc -O2 -pipe -I@/contrib/dev/acpica -D_KERNEL -DKLD_MODULE -nostdinc -I- -I@/contrib/dev/acpica -include /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c: In function `acpi_snc_attach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c:128: error: `_Dbg' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c:128: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c:128: error: for each function it appears in.) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c: In function `acpi_snc_detach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc/../../../dev/acpica/acpi_snc.c:134: error: `_Dbg' undeclared (first use in this function) *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_snc. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-11-14 18:27:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-14 18:27:27 - ERROR: failed to build lint kernel TB --- 2004-11-14 18:27:27 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 18:30:37 2004 Return-Path: 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 41BA216A4CE for ; Sun, 14 Nov 2004 18:30:37 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id D678B43D1D for ; Sun, 14 Nov 2004 18:30:36 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAEIWWbC014820; Sun, 14 Nov 2004 11:32:32 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <4197A47D.1070205@freebsd.org> Date: Sun, 14 Nov 2004 11:31:25 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Pascal Hofstee References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Frode Nordahl cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 18:30:37 -0000 Pascal Hofstee wrote: > On Sun, 14 Nov 2004 02:55:46 -0700, Scott Long wrote: > >>It's harmless and means that the system _detected_ two logical cores. >>It doesn't mean that the system used them, and if you look a bit >>further down you'll see that it mentions cpu0 and cpu1, and no more. > > > and if you look at the bottom of that log ... you notice > > SMP: AP CPU #1 Launched! > Mounting root from ufs:/dev/ad4s1a > > this is definately SMP kicking in and "launching" the 2nd logical CPU > .. CPU #0 being the first logical CPU. So are there two physical CPUs in the machine or not? The VB2 motherboard certainly supports two physical CPUs, and I do believe that the original poster mentioned having them. Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 18:31:24 2004 Return-Path: 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 E2DBA16A4CE for ; Sun, 14 Nov 2004 18:31:24 +0000 (GMT) Received: from mta08-winn.mailhost.ntl.com (mailhost.ntl.com [212.250.162.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D26843D1D for ; Sun, 14 Nov 2004 18:31:24 +0000 (GMT) (envelope-from scott@fishballoon.org) Received: from aamta03-winn.mailhost.ntl.com ([212.250.162.8]) by mta08-winn.mailhost.ntl.com with ESMTP <20041114183123.ILKA18909.mta08-winn.mailhost.ntl.com@aamta03-winn.mailhost.ntl.com> for ; Sun, 14 Nov 2004 18:31:23 +0000 Received: from llama.fishballoon.org ([82.4.146.133]) by aamta03-winn.mailhost.ntl.com with ESMTP <20041114183122.FJLH16823.aamta03-winn.mailhost.ntl.com@llama.fishballoon.org> for ; Sun, 14 Nov 2004 18:31:22 +0000 Received: from tuatara.fishballoon.org ([192.168.1.6]) by llama.fishballoon.org with esmtp (Exim 4.43 (FreeBSD)) id 1CTP9k-000F56-8T for freebsd-current@freebsd.org; Sun, 14 Nov 2004 18:31:20 +0000 Received: (from scott@localhost) by tuatara.fishballoon.org (8.13.1/8.13.1/Submit) id iAEIVIuG049519 for freebsd-current@freebsd.org; Sun, 14 Nov 2004 18:31:18 GMT (envelope-from scott) Date: Sun, 14 Nov 2004 18:31:18 +0000 From: Scott Mitchell To: freebsd-current@freebsd.org Message-ID: <20041114183118.GA57138@tuatara.fishballoon.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 4.10-STABLE i386 Subject: Panic mounting root (bundirty) on yesterday's -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 18:31:25 -0000 Hi all, I upgraded my ancient ThinkPad 380D from some 5.2-CURRENT to yesterdays 6.0-CURRENT. Booting GENERIC I get: Mounting root from ufs:/dev/ad0s2a g_vfs_done():ad0s2a[WRITE(offset=65536, length=8192)]error = 1 panic: bundirty: buffer 0xc290a170 still on queue 1 With a custom kernel (no INVARIANTS or WITNESS) I still get the g_vfs_done() message, but no panic, and the machine seems to run normally. I see somebody else was asking about the same message here yesterday: http://lists.freebsd.org/pipermail/freebsd-current/2004-November/043012.html Any ideas? Full dmesg and traceback from DDB below. Unfortunately I haven't been able to get remote debugging working on this machine (it hangs at the boot: prompt with -d in /boot.config) so I don't know what further debugging I can do... Cheers, Scott ----- cut here ----- GDB: no debug ports present KDB: debugger backends: ddb KDB: current backend: ddb 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 6.0-CURRENT #0: Sat Nov 13 16:18:14 GMT 2004 scott@tuatara.fishballoon.org:/local/obj/local/-CURRENT/src/sys/GENERIC WARNING: WITNESS option enabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P54C (152.13-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping = 12 Features=0x1bf real memory = 33554432 (32 MB) avail memory = 23445504 (22 MB) Intel Pentium detected, installing workaround for F00F bug npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 pci0: at device 1.0 (no driver attached) pci0: at device 3.0 (no driver attached) pci0: at device 19.0 (no driver attached) cpu0 on motherboard isa0: on motherboard orm0: at iomem 0xc0000-0xc7fff on isa0 pmtimer0 on isa0 ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: at port 0x3bc-0x3c3 irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounter "TSC" frequency 152132018 Hz quality 800 Timecounters tick every 1.000 msec ad0: 1376MB [2796/16/63] at ata0-master PIO4 acd0: CDROM at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a g_vfs_done():ad0s2a[WRITE(offset=65536, length=8192)]error = 1 panic: bundirty: buffer 0xc290a170 still on queue 1 cpuid = 0 KDB: enter: panic [thread 100063] Stopped at kdb_enter+0x2c: leave db> tr kdb_enter(c080e5a0,100,c126d480,c290a170,c290a170) at kdb_enter+0x2c panic(c08158f0,c290a170,1,c290a170,c44a26bc) at panic+0x17f bundirty(c290a170,0,c08157f8,ed2,c290a170) at bundirty+0xbd brelse(c290a170,c290a170,c290a170,2090022,0) at brelse+0x7ba bufwrite(c290a170) at bufwrite+0x3b8 getblk(c1284cf0,80,0,4000,0) at getblk+0x175 breadn(c1284cf0,80,0,4000,0) at breadn+0x2e bread(c1284cf0,80,0,4000,0,c44a283c) at bread+0x20 ffs_vget(c1270c00,80,2,c44a28c4) at ffs_vget+0x20d ufs_lookup(c44a2974) at ufs_lookup+0x81e vfs_cache_lookup(c44a29e4,c080d96f,c44a2bf8,c126d480,0) at vfs_cache_lookup+0x25d lookup(c44a2be4,c126d480,c08d8840,c44a2a2c,c062adb5) at lookup+0x269 namei(c44a2be4,c062ade4,c126d480,c08dee40,2) at namei+0x215 vn_open_cred(c44a2be4,c44a2ce4,0,c112a180,3) at vn_open_cred+0x145 vn_open(c44a2be4,c44a2ce4,0,3,c08cf980,8,c0817888,3bc) at vn_open+0x1e kern_open(c126d480,2807ade4,0,1,0) at kern_open+0xd7 open(c126d480,c44a2d14,3,e,286) at open+0x18 syscall(2f,2f,2f,28085000,8048d51) at syscall+0x128 Xint0x80_syscall() at Xint0x80_syscall+0x1f --- syscall (5, FreeBSD ELF32, open), eip = 0x2806a14b, esp = 0xbfbfec54, ebp = 0xbfbfed00 --- db> panic panic: from debugger cpuid = 0 Uptime: 4s Cannot dump. No dump device defined. Automatic reboot in 15 seconds - press a key on the console to abort -- =========================================================================== Scott Mitchell | PGP Key ID | "Eagles may soar, but weasels Cambridge, England | 0x54B171B9 | don't get sucked into jet engines" scott at fishballoon.org | 0xAA775B8B | -- Anon From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 20:47:44 2004 Return-Path: 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 C222B16A4CE for ; Sun, 14 Nov 2004 20:47:44 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79ED743D3F for ; Sun, 14 Nov 2004 20:47:44 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 2462 invoked from network); 14 Nov 2004 20:47:44 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Nov 2004 20:47:43 -0000 Received: from hydrogen.funkthat.com (wluzyr@localhost.funkthat.com [127.0.0.1])iAEKlgB6042594; Sun, 14 Nov 2004 12:47:43 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAEKlavT042593; Sun, 14 Nov 2004 12:47:36 -0800 (PST) Date: Sun, 14 Nov 2004 12:47:35 -0800 From: John-Mark Gurney To: "Marcos Biscaysaqu - ThePacific.net" Message-ID: <20041114204735.GF57546@funkthat.com> Mail-Followup-To: "Marcos Biscaysaqu - ThePacific.net" , freebsd-current@freebsd.org References: <4190EE1D.8030702@ThePacific.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4190EE1D.8030702@ThePacific.Net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: freebsd-current@freebsd.org Subject: Re: split rx and tx traffic on Atheros crads..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 20:47:44 -0000 Marcos Biscaysaqu - ThePacific.net wrote this message on Tue, Nov 09, 2004 at 16:19 +0000: > One of the biggest problems on the wireless traffic in WISPs start when > the Access Point start to get a lot incoming and outgoing traffic in the > same time, I was thinking if we could run 2 wireless cards both as > Access Point but one card as rx only and another as tx mode, plus if we > could just set 2 ssid in a Bsd client one for rx and other as tx we > could increase the bandwidth on the Access point in two times and make > the connections work a lot smooth and faster ( im not sure if this is > possible I could be very wrong) at the same time If this it is possible > we could run 2 wireless cards each end with the rx and the tx separeted > and get for example 108mb each way (with dual polarization antennas). Nope, you are not crazy, this is entirely doable... You just need to make sure your routing gets handled properly at both ends... (On a system, when I would plug into the wired network, but leave my wireless up, I would send my wireless traffic out the wired interface, because of the new default route, and receive the responses via wireless. Just a modified version of what you talk about.) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 21:02:29 2004 Return-Path: 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 6290016A4CE for ; Sun, 14 Nov 2004 21:02:29 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33B2643D49 for ; Sun, 14 Nov 2004 21:02:29 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D98CAF18B4 for ; Sun, 14 Nov 2004 13:02:26 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 79579-01 for ; Sun, 14 Nov 2004 13:02:18 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 3E7E2F18AF for ; Sun, 14 Nov 2004 13:02:18 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8JlgIrd2QKun+KJZsrq7" Date: Sun, 14 Nov 2004 13:02:17 -0800 Message-Id: <1100466137.48774.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: bsdtar doesn't work with ports backup of libsigc++20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 21:02:29 -0000 --=-8JlgIrd2QKun+KJZsrq7 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I was doing a complete rebuild of my system and ran into a problem with bsdtar: portupgrade -f libsigc++-2.0.3 ---> Backing up the old version tar: share/doc/libsigc-2.0/docs/reference/html/classsigc_1_1signal_3_01T__r= eturn_00_01T__arg1_00_01T__arg2_00_01T__arg3_00_01T__arg4_00_01T__arg5_00_0= 1T__arg6_01_4-members.html: (null) ** Backup failed. switching over to gtar and it works. Cheers, Sean --=-8JlgIrd2QKun+KJZsrq7 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBl8fZyQsGN30uGE4RAre9AJ9YxpSPLLmFvrbBY35di0Jr2zBvkACg4Lx0 ZDe4n1wpg8/07fQfoVfLdzw= =D7y2 -----END PGP SIGNATURE----- --=-8JlgIrd2QKun+KJZsrq7-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 21:36:40 2004 Return-Path: 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 1E04E16A4CE; Sun, 14 Nov 2004 21:36:40 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54AA243D3F; Sun, 14 Nov 2004 21:36:39 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [192.168.1.34] (ti211110a080-4342.bb.online.no [80.213.176.248]) by smtp1.powertech.no (Postfix) with ESMTP id F03917E79; Sun, 14 Nov 2004 22:36:37 +0100 (CET) In-Reply-To: <4197A47D.1070205@freebsd.org> References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> Content-Transfer-Encoding: 7bit From: Frode Nordahl Date: Sun, 14 Nov 2004 22:36:39 +0100 To: Scott Long X-Mailer: Apple Mail (2.619) cc: current@freebsd.org cc: Pascal Hofstee Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 21:36:40 -0000 On Nov 14, 2004, at 19:31, Scott Long wrote: > Pascal Hofstee wrote: >> On Sun, 14 Nov 2004 02:55:46 -0700, Scott Long >> wrote: >>> It's harmless and means that the system _detected_ two logical cores. >>> It doesn't mean that the system used them, and if you look a bit >>> further down you'll see that it mentions cpu0 and cpu1, and no more. >> and if you look at the bottom of that log ... you notice >> SMP: AP CPU #1 Launched! >> Mounting root from ufs:/dev/ad4s1a >> this is definately SMP kicking in and "launching" the 2nd logical CPU >> .. CPU #0 being the first logical CPU. > > So are there two physical CPUs in the machine or not? The VB2 > motherboard certainly supports two physical CPUs, and I do believe > that the original poster mentioned having them. There are two physical CPUs in there, yes. Mvh, Frode > Scott From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 22:04:03 2004 Return-Path: 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 4602F16A4CE for ; Sun, 14 Nov 2004 22:04:03 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CFA343D31 for ; Sun, 14 Nov 2004 22:04:03 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D6C1BF18AF for ; Sun, 14 Nov 2004 14:04:02 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57503-05 for ; Sun, 14 Nov 2004 14:03:54 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 9734CF1802 for ; Sun, 14 Nov 2004 14:03:54 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-tgvR2FwkfZ2Jo8j0Y6Gx" Date: Sun, 14 Nov 2004 14:03:54 -0800 Message-Id: <1100469834.23915.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: missing weak symbol for pthread_equal in libc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 22:04:03 -0000 --=-tgvR2FwkfZ2Jo8j0Y6Gx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I think pthread_equal should be added to libc. I found it is used in libxml2 and a link to that library fails without -pthread. Cheers, Sean --=-tgvR2FwkfZ2Jo8j0Y6Gx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBl9ZKyQsGN30uGE4RAqhnAJ49zeBj9qY/oGPwbbs9auQ/+EzM0ACeICzZ 82F1CvtcF4kqfYcmS7CZyKM= =6wFI -----END PGP SIGNATURE----- --=-tgvR2FwkfZ2Jo8j0Y6Gx-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 22:22:49 2004 Return-Path: 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 4CA1416A4D0 for ; Sun, 14 Nov 2004 22:22:49 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18D8243D2D for ; Sun, 14 Nov 2004 22:22:49 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5EF03511D3; Sun, 14 Nov 2004 14:25:33 -0800 (PST) Date: Sun, 14 Nov 2004 14:25:33 -0800 From: Kris Kennaway To: Ivan Voras Message-ID: <20041114222533.GA17027@xor.obsecurity.org> References: <4196398D.2030000@fer.hr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bp/iNruPH9dso1Pn" Content-Disposition: inline In-Reply-To: <4196398D.2030000@fer.hr> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: Passwd format? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 22:22:49 -0000 --bp/iNruPH9dso1Pn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 13, 2004 at 05:42:53PM +0100, Ivan Voras wrote: > The Handbook and crypt(3) say passwords in master.passwd are MD5 hashes= =20 > if they start with $1$, for example: >=20 > $1$DP.s8oCc$VJo0/026/S5ng6HlD1Sz8/ >=20 > the format is $1$salt$rest. I have several questions: >=20 > How are the values encoded? This looks something like base64. >=20 > Is it possible to actually verify the password against this format using= =20 > only a bare implementation of the md5 algorithm? >=20 > Actually, the reason for these questions is that I'm considering using=20 > LDAP authentication on a machine with lots of users and I'm wondering if= =20 > existing passwd information could be transported to LDAP. Any=20 > experiences/docs on this? man 3 crypt, or see the source code Kris --bp/iNruPH9dso1Pn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBl9tdWry0BWjoQKURAp5KAJ9G252dF9rGh3WYPAnOBOtigubfBgCgq8ql D+q6F+fMikWEbqwR2mEafoE= =Tlsz -----END PGP SIGNATURE----- --bp/iNruPH9dso1Pn-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 22:24:06 2004 Return-Path: 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 78BDC16A4CE for ; Sun, 14 Nov 2004 22:24:06 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA2C543D49 for ; Sun, 14 Nov 2004 22:24:05 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iAEMO36g117934 for ; Sun, 14 Nov 2004 17:24:04 -0500 Message-ID: <4197DB02.8050601@elischer.org> Date: Sun, 14 Nov 2004 14:24:02 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 22:24:06 -0000 I upgraded my Dell Inspiron 7500 to RELENG_5 and have been seeing all sorts of problems. Previously it was running 5.3 beta7 and seemed happy with that. the symptoms.. boot to single user succeeds. however if the filesyste,s do not need cleaning (?) it will freeze solit part way through going to multi-user.. usually just after printing "preserving vi files" (or whatever the actual message is). However if the filesystems DO need checking. it says that te filesyste, wil be checked in background, and that background fsck will be started in 60 seconds, and teh boot succeeds all the way to multi user mode. Once there, though I have to live with the slowdown of the fsck running... Even before fsck starts however, everything appears VERY slow. The mouse reponds slowly and jerkily. This was all not true with 5.3B7 so it's a recent change.. From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 22:25:01 2004 Return-Path: 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 BBD1C16A4CE for ; Sun, 14 Nov 2004 22:25:01 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 843BF43D58 for ; Sun, 14 Nov 2004 22:25:01 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 00FF4511D3; Sun, 14 Nov 2004 14:27:45 -0800 (PST) Date: Sun, 14 Nov 2004 14:27:45 -0800 From: Kris Kennaway To: Sean McNeil Message-ID: <20041114222745.GB17027@xor.obsecurity.org> References: <1100466137.48774.4.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wq9mPyueHGvFACwf" Content-Disposition: inline In-Reply-To: <1100466137.48774.4.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: bsdtar doesn't work with ports backup of libsigc++20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 22:25:01 -0000 --wq9mPyueHGvFACwf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 14, 2004 at 01:02:17PM -0800, Sean McNeil wrote: > I was doing a complete rebuild of my system and ran into a problem with > bsdtar: >=20 > portupgrade -f libsigc++-2.0.3 >=20 > ---> Backing up the old version > tar: share/doc/libsigc-2.0/docs/reference/html/classsigc_1_1signal_3_01T_= _return_00_01T__arg1_00_01T__arg2_00_01T__arg3_00_01T__arg4_00_01T__arg5_00= _01T__arg6_01_4-members.html: (null) > ** Backup failed. >=20 > switching over to gtar and it works. I saw a similar error on one machine, but not others, so my hypothesis is that it was only broken for a short period of time. You didn't mention how old your world is, but try rebuilding it. Kris --wq9mPyueHGvFACwf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBl9vhWry0BWjoQKURAp8lAKCCvcJAXrA/aTQIHOzgkNS1W7Z8qQCgvjwP K+Vf7l8zpW3LC/OAXxoKFiI= =GBW0 -----END PGP SIGNATURE----- --wq9mPyueHGvFACwf-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 22:31:18 2004 Return-Path: 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 E6A8A16A4CE for ; Sun, 14 Nov 2004 22:31:17 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8FC3E43D39 for ; Sun, 14 Nov 2004 22:31:17 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 5ADE4F2074; Sun, 14 Nov 2004 14:31:17 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 57503-08; Sun, 14 Nov 2004 14:31:09 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 05220F2020; Sun, 14 Nov 2004 14:31:09 -0800 (PST) From: Sean McNeil To: Kris Kennaway In-Reply-To: <20041114222745.GB17027@xor.obsecurity.org> References: <1100466137.48774.4.camel@server.mcneil.com> <20041114222745.GB17027@xor.obsecurity.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-jh2y8/wHsoMf603ymu5y" Date: Sun, 14 Nov 2004 14:31:08 -0800 Message-Id: <1100471468.45413.0.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: bsdtar doesn't work with ports backup of libsigc++20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 22:31:18 -0000 --=-jh2y8/wHsoMf603ymu5y Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-11-14 at 14:27 -0800, Kris Kennaway wrote: > On Sun, Nov 14, 2004 at 01:02:17PM -0800, Sean McNeil wrote: > > I was doing a complete rebuild of my system and ran into a problem with > > bsdtar: > >=20 > > portupgrade -f libsigc++-2.0.3 > >=20 > > ---> Backing up the old version > > tar: share/doc/libsigc-2.0/docs/reference/html/classsigc_1_1signal_3_01= T__return_00_01T__arg1_00_01T__arg2_00_01T__arg3_00_01T__arg4_00_01T__arg5_= 00_01T__arg6_01_4-members.html: (null) > > ** Backup failed. > >=20 > > switching over to gtar and it works. >=20 > I saw a similar error on one machine, but not others, so my hypothesis > is that it was only broken for a short period of time. You didn't > mention how old your world is, but try rebuilding it. Rebuild was Today. --=-jh2y8/wHsoMf603ymu5y Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBl9ysyQsGN30uGE4RAhaSAJ4ipJUd5PrHEmBUeRDVpAFskmTnhACgycma YEnA3SOApZDz+nCjA5bbyAI= =8B/7 -----END PGP SIGNATURE----- --=-jh2y8/wHsoMf603ymu5y-- From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 23:40:01 2004 Return-Path: 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 8AA8316A4CE; Sun, 14 Nov 2004 23:40:01 +0000 (GMT) Received: from hotmail.com (bay2-dav16.bay2.hotmail.com [65.54.246.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6372643D1F; Sun, 14 Nov 2004 23:40:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 15:40:01 -0800 Received: from 24.24.201.219 by BAY2-DAV16.phx.gbl with DAV; Sun, 14 Nov 2004 23:39:00 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: , Date: Sun, 14 Nov 2004 15:39:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 14 Nov 2004 23:40:01.0086 (UTC) FILETIME=[421C7DE0:01C4CAA3] Subject: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 23:40:01 -0000 I'm trying to use sed under FreeBSD 5.3-RELEASE in a new 'netqmail' port I am currently working on. I want to replace a bunch of digits (in plain English: a decimal number) in a text file at the beginning of a line. Here is how the original file looks before I do anything (this file is part of the netqmail-1.05 package, but it is unimportant): --- file conf-split begins 23 This is the queue subdirectory split. --- file conf-split ends Okay, so I try to replace 23 (or whatever number is there!) at the beginning of the first line to let's say 199 in this file using sed. I would expect this to work: sed -e "s/^[0-9]+/199/" conf-split > conf-split.new But it doesn't change anything in conf-spilt.new!! My regexp ^[0-9]+ doesn't match anything! After spending like an hour investigating this, I realized that the + after my bracket expression ( I'm talking about this part here: [0-9]+ ) does not match! If I omit the use of + and use * instead, I can make my regexp to match. So this works - but IMHO it's ugly: sed -e "s/^[0-9][0-9]*/199/" conf-split > conf-split.new It gives this output, which is what I always wanted: --- file conf-split.new begins 199 This is the queue subdirectory split. --- file conf-split.new ends According to the sed man page, the regexp syntax that is used by sed is documented in the re_format man page. And according to the re_format man page: "A piece is an atom possibly followed by a single= `*', `+', `?', or bound. An atom followed by `*' matches a sequence of 0 or more matches of the atom. An atom followed by `+' matches a sequence of 1 or more matches of the atom. ..." And the definition of an "atom" is (quoted from the same man page): "An atom is a regular expression enclosed in `()' (matching a match for the regular expression), an empty set of `()' (matching the null string)=, a bracket expression (see below) ..." So either my bracket expression ( [0-9] ) in my first sed command was not recognized as an atom, or if it was recognized as an atom then the + that followed it was not interpreted properly... Can anyone please tell me why? I believe this is a bug in sed or in the regexp library which sed uses. If it is a regexp library issue, then there is a chance that it affects other programs that use it, as well! At least it can break all programs that use sed regexps, especially ports... My uname -a is: FreeBSD www.xxxxxxxx.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 12 01:07:41 PST 2004 xxx@www.xxxxxxxx.com:/usr/obj/usr/src/sys/XXXXXXXX i386 Zoltan From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 23:41:05 2004 Return-Path: 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 15A1D16A4DC for ; Sun, 14 Nov 2004 23:40:55 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BAD2B43D31 for ; Sun, 14 Nov 2004 23:40:53 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTTz5-000Gk2-00 for freebsd-current@freebsd.org; Mon, 15 Nov 2004 02:40:39 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTTz5-000Gjn-00; Mon, 15 Nov 2004 02:40:39 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTTz4-000Gjj-00 for goblin@nnt.ru; Mon, 15 Nov 2004 02:40:38 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 403BF55FE7; Sun, 14 Nov 2004 23:40:35 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0312916A530; Sun, 14 Nov 2004 23:40:11 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8AA8316A4CE; Sun, 14 Nov 2004 23:40:01 +0000 (GMT) Received: from hotmail.com (bay2-dav16.bay2.hotmail.com [65.54.246.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6372643D1F; Sun, 14 Nov 2004 23:40:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 15:40:01 -0800 Received: from 24.24.201.219 by BAY2-DAV16.phx.gbl with DAV; Sun, 14 Nov 2004 23:39:00 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: , Date: Sun, 14 Nov 2004 15:39:00 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 14 Nov 2004 23:40:01.0086 (UTC) FILETIME=[421C7DE0:01C4CAA3] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-stable@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.596929, version=0.92.8 Subject: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 23:41:06 -0000 I'm trying to use sed under FreeBSD 5.3-RELEASE in a new 'netqmail' port I am currently working on. I want to replace a bunch of digits (in plain English: a decimal number) in a text file at the beginning of a line. Here is how the original file looks before I do anything (this file is part of the netqmail-1.05 package, but it is unimportant): --- file conf-split begins 23 This is the queue subdirectory split. --- file conf-split ends Okay, so I try to replace 23 (or whatever number is there!) at the beginning of the first line to let's say 199 in this file using sed. I would expect this to work: sed -e "s/^[0-9]+/199/" conf-split > conf-split.new But it doesn't change anything in conf-spilt.new!! My regexp ^[0-9]+ doesn't match anything! After spending like an hour investigating this, I realized that the + after my bracket expression ( I'm talking about this part here: [0-9]+ ) does not match! If I omit the use of + and use * instead, I can make my regexp to match. So this works - but IMHO it's ugly: sed -e "s/^[0-9][0-9]*/199/" conf-split > conf-split.new It gives this output, which is what I always wanted: --- file conf-split.new begins 199 This is the queue subdirectory split. --- file conf-split.new ends According to the sed man page, the regexp syntax that is used by sed is documented in the re_format man page. And according to the re_format man page: "A piece is an atom possibly followed by a single= `*', `+', `?', or bound. An atom followed by `*' matches a sequence of 0 or more matches of the atom. An atom followed by `+' matches a sequence of 1 or more matches of the atom. ..." And the definition of an "atom" is (quoted from the same man page): "An atom is a regular expression enclosed in `()' (matching a match for the regular expression), an empty set of `()' (matching the null string)=, a bracket expression (see below) ..." So either my bracket expression ( [0-9] ) in my first sed command was not recognized as an atom, or if it was recognized as an atom then the + that followed it was not interpreted properly... Can anyone please tell me why? I believe this is a bug in sed or in the regexp library which sed uses. If it is a regexp library issue, then there is a chance that it affects other programs that use it, as well! At least it can break all programs that use sed regexps, especially ports... My uname -a is: FreeBSD www.xxxxxxxx.com 5.3-RELEASE FreeBSD 5.3-RELEASE #0: Fri Nov 12 01:07:41 PST 2004 xxx@www.xxxxxxxx.com:/usr/obj/usr/src/sys/XXXXXXXX i386 Zoltan _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 23:46:34 2004 Return-Path: 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 427F516A4CE for ; Sun, 14 Nov 2004 23:46:34 +0000 (GMT) Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B258C43D48 for ; Sun, 14 Nov 2004 23:46:33 +0000 (GMT) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) iAENkSX3017741; Sun, 14 Nov 2004 18:46:32 -0500 (EST) Date: Sun, 14 Nov 2004 18:46:28 -0500 (EST) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net To: Sean McNeil In-Reply-To: <1100469834.23915.1.camel@server.mcneil.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net) cc: current@freebsd.org Subject: Re: missing weak symbol for pthread_equal in libc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Eischen List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 23:46:34 -0000 On Sun, 14 Nov 2004, Sean McNeil wrote: > > I think pthread_equal should be added to libc. I found it is used in > libxml2 and a link to that library fails without -pthread. The pthread_foo() in libc are mainly for libc usage. If applications want to use pthread_foo(), they really should be linking to the (a) threads library. Look at it this way -- if we didn't use any pthread functions in libc, there wouldn't be _any_ pthread stubs in libc. Also, we could have used __libc_lock(), __libc_unlock(), etc, in libc and have the threads libraries override those functions instead of using _pthread_*(). pthread_equal() would be kinda harmless in libc, but you get my point above, no? -- Dan Eischen From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 23:48:31 2004 Return-Path: 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 A883D16A4CE; Sun, 14 Nov 2004 23:48:31 +0000 (GMT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EAAB43D48; Sun, 14 Nov 2004 23:48:31 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id BA8E582; Sun, 14 Nov 2004 18:48:28 -0500 (EST) From: "Brandon S. Allbery KF8NH" To: Zoltan Frombach In-Reply-To: References: Content-Type: text/plain Message-Id: <1100476106.10768.4.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 14 Nov 2004 18:48:27 -0500 Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 14 Nov 2004 23:48:31 -0000 On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote: > match anything! After spending like an hour investigating this, I realized > that the + after my bracket expression ( I'm talking about this part here: Normal. > According to the sed man page, the regexp syntax that is used by sed is > documented in the re_format man page. And according to the re_format man > page: "A piece is an atom possibly followed by a single= `*', `+', `?', or You need to read it more carefully. There are two kinds of regular expressions, "basic" and "extended". sed, ed, and grep speak BRE syntax, whereas awk and egrep speak ERE syntax. + is special only in ERE syntax. (And then there's GNU, where the difference between BRE and ERE is that some things use a preceding backslash in BRE and don't in ERE, and vice versa, so GNU sed does what you want if you use \+ instead of +.) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH From owner-freebsd-current@FreeBSD.ORG Sun Nov 14 23:50:58 2004 Return-Path: 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 EE7F116A4E4 for ; Sun, 14 Nov 2004 23:50:54 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7390243D46 for ; Sun, 14 Nov 2004 23:50:54 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTU7n-000Hwg-00 for freebsd-current@freebsd.org; Mon, 15 Nov 2004 02:49:39 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTU7m-000HwR-00; Mon, 15 Nov 2004 02:49:38 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTU7m-000HwL-00 for goblin@nnt.ru; Mon, 15 Nov 2004 02:49:38 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 1EAA15795E; Sun, 14 Nov 2004 23:48:53 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5BFC016A4EC; Sun, 14 Nov 2004 23:48:45 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A883D16A4CE; Sun, 14 Nov 2004 23:48:31 +0000 (GMT) Received: from bache.ece.cmu.edu (BACHE.ECE.CMU.EDU [128.2.129.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EAAB43D48; Sun, 14 Nov 2004 23:48:31 +0000 (GMT) (envelope-from allbery@ece.cmu.edu) Received: from [10.9.204.1] (dsl093-061-215.pit1.dsl.speakeasy.net [66.93.61.215]) by bache.ece.cmu.edu (Postfix) with ESMTP id BA8E582; Sun, 14 Nov 2004 18:48:28 -0500 (EST) From: "Brandon S. Allbery KF8NH" To: Zoltan Frombach In-Reply-To: References: Content-Type: text/plain Message-Id: <1100476106.10768.4.camel@rushlight.kf8nh.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Sun, 14 Nov 2004 18:48:27 -0500 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-stable@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.662650, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2004 23:51:01 -0000 On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote: > match anything! After spending like an hour investigating this, I realized > that the + after my bracket expression ( I'm talking about this part here: Normal. > According to the sed man page, the regexp syntax that is used by sed is > documented in the re_format man page. And according to the re_format man > page: "A piece is an atom possibly followed by a single= `*', `+', `?', or You need to read it more carefully. There are two kinds of regular expressions, "basic" and "extended". sed, ed, and grep speak BRE syntax, whereas awk and egrep speak ERE syntax. + is special only in ERE syntax. (And then there's GNU, where the difference between BRE and ERE is that some things use a preceding backslash in BRE and don't in ERE, and vice versa, so GNU sed does what you want if you use \+ instead of +.) -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 00:06:02 2004 Return-Path: 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 7930F16A4CE; Mon, 15 Nov 2004 00:06:02 +0000 (GMT) Received: from hotmail.com (bay2-dav8.bay2.hotmail.com [65.54.246.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 580E643D1D; Mon, 15 Nov 2004 00:06:02 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 16:06:01 -0800 Received: from 24.24.201.219 by BAY2-DAV8.phx.gbl with DAV; Mon, 15 Nov 2004 00:05:14 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Brandon S. Allbery KF8NH" References: <1100476106.10768.4.camel@rushlight.kf8nh.com> Date: Sun, 14 Nov 2004 16:05:15 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 15 Nov 2004 00:06:01.0905 (UTC) FILETIME=[E46E9210:01C4CAA6] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 00:06:02 -0000 You are right. My mistake. This indeed works: sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new Thanks for clearing this up. Zoltan > On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote: >> match anything! After spending like an hour investigating this, I >> realized >> that the + after my bracket expression ( I'm talking about this part >> here: > > Normal. > >> According to the sed man page, the regexp syntax that is used by sed is >> documented in the re_format man page. And according to the re_format man >> page: "A piece is an atom possibly followed by a single= `*', `+', `?', >> or > > You need to read it more carefully. There are two kinds of regular > expressions, "basic" and "extended". sed, ed, and grep speak BRE > syntax, whereas awk and egrep speak ERE syntax. + is special only in > ERE syntax. > > (And then there's GNU, where the difference between BRE and ERE is that > some things use a preceding backslash in BRE and don't in ERE, and vice > versa, so GNU sed does what you want if you use \+ instead of +.) > > -- > brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com > system administrator [WAY too many hats] allbery@ece.cmu.edu > electrical and computer engineering, carnegie mellon univ. KF8NH From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 00:07:57 2004 Return-Path: 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 5F58F16A4CE; Mon, 15 Nov 2004 00:07:57 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32C0543D1D; Mon, 15 Nov 2004 00:07:57 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id C5942F2077; Sun, 14 Nov 2004 16:07:54 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 98808-05; Sun, 14 Nov 2004 16:07:46 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 763C8F1802; Sun, 14 Nov 2004 16:07:46 -0800 (PST) From: Sean McNeil To: Daniel Eischen In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-aZWYRMzwF80bujqZbo62" Date: Sun, 14 Nov 2004 16:07:46 -0800 Message-Id: <1100477266.89074.15.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: missing weak symbol for pthread_equal in libc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 00:07:57 -0000 --=-aZWYRMzwF80bujqZbo62 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sun, 2004-11-14 at 18:46 -0500, Daniel Eischen wrote: > On Sun, 14 Nov 2004, Sean McNeil wrote: >=20 > > > > I think pthread_equal should be added to libc. I found it is used in > > libxml2 and a link to that library fails without -pthread. >=20 > The pthread_foo() in libc are mainly for libc usage. If applications > want to use pthread_foo(), they really should be linking to the (a) > threads library. Look at it this way -- if we didn't use any pthread > functions in libc, there wouldn't be _any_ pthread stubs in libc. > Also, we could have used __libc_lock(), __libc_unlock(), etc, in > libc and have the threads libraries override those functions instead > of using _pthread_*(). >=20 > pthread_equal() would be kinda harmless in libc, but you get my > point above, no? After some thought, I agree as pthread_equal is not used within libc, but this brings up the question as to why there are any pthread_* symbols in libc. This is kind of a sore point for me. I actually believe that there should be no weak symbols of pthread_* in libc. A program that uses pthread_cond_init, for example, should not compile without the pthread library. weak symbols to the _pthread_* functions are fine as they are required to provide thread-safe functionality within libs. IMHO, it should be setup as follows: 1) libpthread.so has routines _pthread_* and references as pthread_* (I think they should be strong, but others think weak ;-) - suppose to be funny, not offensive). 2) libc.so accesses those (_pthread_*) functions and has weak symbols for the ones it use to work without libpthread. --=-aZWYRMzwF80bujqZbo62 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBl/NSyQsGN30uGE4RAvChAJ9qyFQR3hMbn8UZFv9btR6Eed6hfQCePV5E fo9SY4UFwYVjoh8evRVlhPA= =h5VB -----END PGP SIGNATURE----- --=-aZWYRMzwF80bujqZbo62-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 00:12:02 2004 Return-Path: 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 D423316A4CE for ; Mon, 15 Nov 2004 00:12:02 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7FA5543D2F for ; Mon, 15 Nov 2004 00:12:02 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTUOt-000Ksa-00 for freebsd-current@freebsd.org; Mon, 15 Nov 2004 03:07:19 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTUOr-000Kqx-00; Mon, 15 Nov 2004 03:07:17 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTUOq-000Kp1-00 for goblin@nnt.ru; Mon, 15 Nov 2004 03:07:17 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id A025A579CD; Mon, 15 Nov 2004 00:06:32 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 392FC16A5AC; Mon, 15 Nov 2004 00:06:15 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7930F16A4CE; Mon, 15 Nov 2004 00:06:02 +0000 (GMT) Received: from hotmail.com (bay2-dav8.bay2.hotmail.com [65.54.246.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id 580E643D1D; Mon, 15 Nov 2004 00:06:02 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 16:06:01 -0800 Received: from 24.24.201.219 by BAY2-DAV8.phx.gbl with DAV; Mon, 15 Nov 2004 00:05:14 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Brandon S. Allbery KF8NH" References: <1100476106.10768.4.camel@rushlight.kf8nh.com> Date: Sun, 14 Nov 2004 16:05:15 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 15 Nov 2004 00:06:01.0905 (UTC) FILETIME=[E46E9210:01C4CAA6] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-stable@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.543619, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 00:12:03 -0000 You are right. My mistake. This indeed works: sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new Thanks for clearing this up. Zoltan > On Sun, 2004-11-14 at 18:39, Zoltan Frombach wrote: >> match anything! After spending like an hour investigating this, I >> realized >> that the + after my bracket expression ( I'm talking about this part >> here: > > Normal. > >> According to the sed man page, the regexp syntax that is used by sed is >> documented in the re_format man page. And according to the re_format man >> page: "A piece is an atom possibly followed by a single= `*', `+', `?', >> or > > You need to read it more carefully. There are two kinds of regular > expressions, "basic" and "extended". sed, ed, and grep speak BRE > syntax, whereas awk and egrep speak ERE syntax. + is special only in > ERE syntax. > > (And then there's GNU, where the difference between BRE and ERE is that > some things use a preceding backslash in BRE and don't in ERE, and vice > versa, so GNU sed does what you want if you use \+ instead of +.) > > -- > brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com > system administrator [WAY too many hats] allbery@ece.cmu.edu > electrical and computer engineering, carnegie mellon univ. KF8NH _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:29:53 2004 Return-Path: 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 737C316A4CE; Mon, 15 Nov 2004 01:29:53 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1001443D1D; Mon, 15 Nov 2004 01:29:53 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id iAF1Tq90004972; Sun, 14 Nov 2004 17:29:52 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41980690.5030405@freebsd.org> Date: Sun, 14 Nov 2004 17:29:52 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Joe Marcus Clarke References: <4193C9E5.2090004@FreeBSD.org> In-Reply-To: <4193C9E5.2090004@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: BSD tar cannot archive files with setuid bit on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 01:29:53 -0000 Joe Marcus Clarke wrote: > > After upgrading to 6-CURRENT from November 10, I found bsdtar cannot > archive files with setuid bits anymore. .... > > This problem can be reproduced by: > > # cd /tmp > # tar cvf xxx.tar /bin/rcp This is now fixed. (The problem was actually with the schg flag, not the setuid bit. Forcing ustar format with --format=ustar is a workaround.) Thanks for the report, Tim From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:41:30 2004 Return-Path: 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 50C6416A4CE for ; Mon, 15 Nov 2004 01:41:30 +0000 (GMT) Received: from rosebud.otenet.gr (rosebud.otenet.gr [195.170.0.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7166F43D2D for ; Mon, 15 Nov 2004 01:41:29 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b157.otenet.gr [212.205.244.165]) iAF1fQp4008127; Mon, 15 Nov 2004 03:41:27 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id iAF1fDeZ002826; Mon, 15 Nov 2004 03:41:13 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id iAF1fCO6002825; Mon, 15 Nov 2004 03:41:12 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Mon, 15 Nov 2004 03:41:12 +0200 From: Giorgos Keramidas To: Zoltan Frombach Message-ID: <20041115014112.GB2694@gothmog.gr> References: <1100476106.10768.4.camel@rushlight.kf8nh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: cc: freebsd-current@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 01:41:30 -0000 On 2004-11-14 16:05, Zoltan Frombach wrote: > You are right. My mistake. This indeed works: > > sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new FYI, the -e option is not necessary when -E is present: $ echo '123foo' | sed -E 's/^[0-9]+//' foo $ From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:42:21 2004 Return-Path: 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 7845B16A4CE; Mon, 15 Nov 2004 01:42:21 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E53E43D2D; Mon, 15 Nov 2004 01:42:21 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 52F475CA3E; Sun, 14 Nov 2004 17:42:21 -0800 (PST) Date: Mon, 15 Nov 2004 02:42:21 +0100 From: Maxime Henrion To: Zoltan Frombach Message-ID: <20041115014221.GF32839@elvis.mu.org> References: <1100476106.10768.4.camel@rushlight.kf8nh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 01:42:21 -0000 Zoltan Frombach wrote: > You are right. My mistake. This indeed works: > > sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new > > Thanks for clearing this up. For what it's worth, there is another way to write this regexp without using the -E flag. Since x+ == xx*, you can write it: "s/^[0-9][0-9]*/199/". The reason for not using -E is that it's not portable, since it's not specified by the standard. GNU sed uses -r for extended REs. Cheers, Maxime From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:46:31 2004 Return-Path: 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 14D8716A4D4 for ; Mon, 15 Nov 2004 01:46:31 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id B745743D1F for ; Mon, 15 Nov 2004 01:46:30 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTVtu-0007G3-00 for freebsd-current@freebsd.org; Mon, 15 Nov 2004 04:43:26 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTVtu-0007Fo-00; Mon, 15 Nov 2004 04:43:26 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTVtt-0007Fj-00 for goblin@nnt.ru; Mon, 15 Nov 2004 04:43:25 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 7202057AF1; Mon, 15 Nov 2004 01:42:50 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5552316A4D2; Mon, 15 Nov 2004 01:42:50 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7845B16A4CE; Mon, 15 Nov 2004 01:42:21 +0000 (GMT) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E53E43D2D; Mon, 15 Nov 2004 01:42:21 +0000 (GMT) (envelope-from mux@freebsd.org) Received: by elvis.mu.org (Postfix, from userid 1920) id 52F475CA3E; Sun, 14 Nov 2004 17:42:21 -0800 (PST) Date: Mon, 15 Nov 2004 02:42:21 +0100 From: Maxime Henrion To: Zoltan Frombach Message-ID: <20041115014221.GF32839@elvis.mu.org> References: <1100476106.10768.4.camel@rushlight.kf8nh.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-stable@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.904903, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 01:46:31 -0000 Zoltan Frombach wrote: > You are right. My mistake. This indeed works: > > sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new > > Thanks for clearing this up. For what it's worth, there is another way to write this regexp without using the -E flag. Since x+ == xx*, you can write it: "s/^[0-9][0-9]*/199/". The reason for not using -E is that it's not portable, since it's not specified by the standard. GNU sed uses -r for extended REs. Cheers, Maxime _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 01:52:49 2004 Return-Path: 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 B8CB816A4CE for ; Mon, 15 Nov 2004 01:52:49 +0000 (GMT) Received: from kientzle.com (h-66-166-149-50.snvacaid.covad.net [66.166.149.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6AFE643D4C for ; Mon, 15 Nov 2004 01:52:49 +0000 (GMT) (envelope-from kientzle@freebsd.org) Received: from freebsd.org (p54.kientzle.com [66.166.149.54]) by kientzle.com (8.12.9/8.12.9) with ESMTP id iAF1qg90005103; Sun, 14 Nov 2004 17:52:49 -0800 (PST) (envelope-from kientzle@freebsd.org) Message-ID: <41980BEA.2030405@freebsd.org> Date: Sun, 14 Nov 2004 17:52:42 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.4) Gecko/20031006 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Sean McNeil References: <1100466137.48774.4.camel@server.mcneil.com> <20041114222745.GB17027@xor.obsecurity.org> <1100471468.45413.0.camel@server.mcneil.com> In-Reply-To: <1100471468.45413.0.camel@server.mcneil.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: Kris Kennaway Subject: Re: bsdtar doesn't work with ports backup of libsigc++20 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 01:52:50 -0000 Sean McNeil wrote: > >I was doing a complete rebuild of my system and ran into a problem with >bsdtar: > >portupgrade -f libsigc++-2.0.3 > >---> Backing up the old version >tar: share/doc/libsigc-2.0/docs/reference/html/classsigc_1_1signal_3_01T__return_00_01T__arg1_00_01T__arg2_00_01T__arg3_00_01T__arg4_00_01T__arg5_00_01T__arg6_01_4-members.html: (null) >** Backup failed. I just committed a couple of changes to -CURRENT that seem to address this: Look for rev 1.21 of archive_write_set_format_pax.c (Same problem as Joe Marcus Clarke reported: long filenames and file flags are handled through the same "extended attribute" mechanism, which appears to have been broken since November 4.) Let me know. Tim From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 02:11:19 2004 Return-Path: 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 BE12816A4CE; Mon, 15 Nov 2004 02:11:18 +0000 (GMT) Received: from hotmail.com (bay2-dav16.bay2.hotmail.com [65.54.246.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F9F43D49; Mon, 15 Nov 2004 02:11:18 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 18:11:17 -0800 Received: from 24.24.201.219 by BAY2-DAV16.phx.gbl with DAV; Mon, 15 Nov 2004 02:10:37 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Maxime Henrion" References: <1100476106.10768.4.camel@rushlight.kf8nh.com> <20041115014221.GF32839@elvis.mu.org> Date: Sun, 14 Nov 2004 18:10:40 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 15 Nov 2004 02:11:17.0798 (UTC) FILETIME=[6440D460:01C4CAB8] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 02:11:19 -0000 Thanks. I will not use the -E flag then. Zoltan > Zoltan Frombach wrote: >> You are right. My mistake. This indeed works: >> >> sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new >> >> Thanks for clearing this up. > > For what it's worth, there is another way to write this regexp without > using the -E flag. Since x+ == xx*, you can write it: > "s/^[0-9][0-9]*/199/". The reason for not using -E is that it's not > portable, since it's not specified by the standard. GNU sed uses -r for > extended REs. > > Cheers, > Maxime From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 02:20:54 2004 Return-Path: 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 B328616A4CE for ; Mon, 15 Nov 2004 02:20:54 +0000 (GMT) Received: from ns.nnt.ru (ns.nnt.ru [217.72.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 655C243D1D for ; Mon, 15 Nov 2004 02:20:54 +0000 (GMT) (envelope-from nobody@ns.nnt.ru) Received: from drweb by ns.nnt.ru with drweb-scanned (Exim 3.36 #1) id 1CTWPU-000BWY-00 for freebsd-current@freebsd.org; Mon, 15 Nov 2004 05:16:04 +0300 Received: from nobody by ns.nnt.ru with local (Exim 3.36 #1) id 1CTWPT-000BWB-00; Mon, 15 Nov 2004 05:16:03 +0300 Received: from mx2.freebsd.org ([216.136.204.119]) by ns.nnt.ru with esmtp (Exim 3.36 #1) id 1CTWPT-000BVt-00 for goblin@nnt.ru; Mon, 15 Nov 2004 05:16:03 +0300 Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 0C8E457B7F; Mon, 15 Nov 2004 02:14:59 +0000 (GMT) (envelope-from owner-freebsd-stable@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 51AAD16A4F2; Mon, 15 Nov 2004 02:14:53 +0000 (GMT) Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE12816A4CE; Mon, 15 Nov 2004 02:11:18 +0000 (GMT) Received: from hotmail.com (bay2-dav16.bay2.hotmail.com [65.54.246.120]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99F9F43D49; Mon, 15 Nov 2004 02:11:18 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 14 Nov 2004 18:11:17 -0800 Received: from 24.24.201.219 by BAY2-DAV16.phx.gbl with DAV; Mon, 15 Nov 2004 02:10:37 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: "Maxime Henrion" References: <1100476106.10768.4.camel@rushlight.kf8nh.com> <20041115014221.GF32839@elvis.mu.org> Date: Sun, 14 Nov 2004 18:10:40 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Message-ID: X-OriginalArrivalTime: 15 Nov 2004 02:11:17.0798 (UTC) FILETIME=[6440D460:01C4CAB8] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Errors-To: owner-freebsd-stable@freebsd.org X-bogoflag: true X-2Bogosity: No, tests=bogofilter, spamicity=0.686832, version=0.92.8 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Either I do something wrong or there is a regexp bug in sed !! X-BeenThere: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 02:20:54 -0000 Thanks. I will not use the -E flag then. Zoltan > Zoltan Frombach wrote: >> You are right. My mistake. This indeed works: >> >> sed -E -e "s/^[0-9]+/199/" conf-split > conf-split.new >> >> Thanks for clearing this up. > > For what it's worth, there is another way to write this regexp without > using the -E flag. Since x+ == xx*, you can write it: > "s/^[0-9][0-9]*/199/". The reason for not using -E is that it's not > portable, since it's not specified by the standard. GNU sed uses -r for > extended REs. > > Cheers, > Maxime _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 02:56:44 2004 Return-Path: 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 C647F16A4D1 for ; Mon, 15 Nov 2004 02:56:44 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68A1243D31 for ; Mon, 15 Nov 2004 02:56:44 +0000 (GMT) (envelope-from caelian@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so578372rnf for ; Sun, 14 Nov 2004 18:56:44 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=jnlSOqOI9EwOFAWaXnVe9GUuuLieQjtXOM6yRVkJL7qzrYbVrrDO4sJ95UcImVnKLB6VKdUAldgwcvNlpHI1tFSejdlIuhaGnhZbf+46UAsFvLYqtnXdVd35cM11g0GvnAJ0Y7eP6GU1Nbz1G8RzWSPMvDXnu2NIOF1pv/e9e4o= Received: by 10.38.96.12 with SMTP id t12mr237052rnb; Sun, 14 Nov 2004 18:56:43 -0800 (PST) Received: by 10.38.79.65 with HTTP; Sun, 14 Nov 2004 18:56:43 -0800 (PST) Message-ID: Date: Sun, 14 Nov 2004 18:56:43 -0800 From: Pascal Hofstee To: Frode Nordahl In-Reply-To: <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> cc: Scott Long cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Pascal Hofstee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 02:56:44 -0000 On Sun, 14 Nov 2004 22:36:39 +0100, Frode Nordahl wrote: > There are two physical CPUs in there, yes. Pardon my sloppy reading ... i apparently completely missed the mention of there being two physical CPUs. From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 03:47:21 2004 Return-Path: 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 E9AF716A4CE for ; Mon, 15 Nov 2004 03:47:21 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41C4E43D1D for ; Mon, 15 Nov 2004 03:47:20 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAF3kLZg022479 for ; Mon, 15 Nov 2004 14:16:21 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Mon, 15 Nov 2004 14:17:09 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAF3eKh28277 for ; Mon, 15 Nov 2004 14:10:21 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDLAQA; Mon, 15 Nov 2004 14:10:14 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAF3f1HH052310 for ; Mon, 15 Nov 2004 14:11:01 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAF3f1xU052309 for current@freebsd.org; Mon, 15 Nov 2004 14:11:01 +1030 (CST) (envelope-from wilkinsa) Date: Mon, 15 Nov 2004 14:11:01 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041115034101.GF51636@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 03:47:22 -0000 Why is HTT turned off out of the box ? I thought HTT was meant to be a hardware 'performance enhancing' feature. Why do we disable it ? - aW 0n Sun, Nov 14, 2004 at 06:56:43PM -0800, Pascal Hofstee wrote: On Sun, 14 Nov 2004 22:36:39 +0100, Frode Nordahl wrote: > There are two physical CPUs in there, yes. Pardon my sloppy reading ... i apparently completely missed the mention of there being two physical CPUs. _______________________________________________ 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 Mon Nov 15 04:04:56 2004 Return-Path: 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 C38B616A4CE for ; Mon, 15 Nov 2004 04:04:56 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99A1F43D39 for ; Mon, 15 Nov 2004 04:04:56 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 8E54E512F3; Sun, 14 Nov 2004 20:07:42 -0800 (PST) Date: Sun, 14 Nov 2004 20:07:42 -0800 From: Kris Kennaway To: current@freebsd.org Message-ID: <20041115040742.GA50559@xor.obsecurity.org> References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> <20041115034101.GF51636@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline In-Reply-To: <20041115034101.GF51636@squash.dsto.defence.gov.au> User-Agent: Mutt/1.4.2.1i Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 04:04:56 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Nov 15, 2004 at 02:11:01PM +1030, Wilkinson, Alex wrote: > Why is HTT turned off out of the box ? I thought HTT was meant to be a > hardware 'performance enhancing' feature. Only in the Intel marketing literature. > Why do we disable it ? Because it's not, for general workloads. Consult the archives for further discussion of this topic, which comes up frequently. Kris --AhhlLboLdkugWU4S Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBmCuOWry0BWjoQKURAoYwAKCOPv1ZZwbz7KBWReI20on6x1i3pwCg2kJB Q7omwiWPSLTX/s+YcSCnXQ0= =IoxC -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 04:06:28 2004 Return-Path: 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 C2F3C16A4D6 for ; Mon, 15 Nov 2004 04:06:28 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57A1143D48 for ; Mon, 15 Nov 2004 04:06:28 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAF48NUd016658; Sun, 14 Nov 2004 21:08:23 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41982B70.4020508@freebsd.org> Date: Sun, 14 Nov 2004 21:07:12 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> <20041115034101.GF51636@squash.dsto.defence.gov.au> In-Reply-To: <20041115034101.GF51636@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 04:06:28 -0000 Wilkinson, Alex wrote: > Why is HTT turned off out of the box ? I thought HTT was meant to be a > hardware 'performance enhancing' feature. > > Why do we disable it ? > > - aW FreeBSD will use HTT if the system has it enabled (usually controlled in the BIOS) and the kernel is compiled for SMP. There are ways to manually disable HTT but leave SMP enabled in the OS, but the default is to use it if the above two requirements are met. However, the OS scheduler is not HTT-aware, so HTT will give a somewhat mixed performance. Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 04:19:29 2004 Return-Path: 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 B888016A4CE for ; Mon, 15 Nov 2004 04:19:29 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FA2643D39 for ; Mon, 15 Nov 2004 04:19:29 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so495983rns for ; Sun, 14 Nov 2004 20:19:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=rO5KiLCbm+Sx/RYakNS5rfNYf9uO4qQMAxXlO2LjdTsVvZgxMRj6dGA5G6pQeZAVmxZLX9drPgpRVt1AkYi48gm5TE0ROQVxHivlaqeMVCf5UUguhtCv2d40KN4jENplC4FqgyTEp7zYmffE8ksW44/dUvWF/HQc2GnoRwKEi14= Received: by 10.38.26.40 with SMTP id 40mr820350rnz; Sun, 14 Nov 2004 20:19:28 -0800 (PST) Received: by 10.38.8.55 with HTTP; Sun, 14 Nov 2004 20:19:28 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 12:19:28 +0800 From: Jiawei Ye To: current@freebsd.org In-Reply-To: <20041115034101.GF51636@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4197C217-3622-11D9-B78A-000A95A9A574@nordahl.net> <41972BA2.3090609@freebsd.org> <4197A47D.1070205@freebsd.org> <4487F0CE-3685-11D9-B78A-000A95A9A574@nordahl.net> <20041115034101.GF51636@squash.dsto.defence.gov.au> Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 04:19:29 -0000 On Mon, 15 Nov 2004 14:11:01 +1030, Wilkinson, Alex wrote: > Why is HTT turned off out of the box ? I thought HTT was meant to be a > hardware 'performance enhancing' feature. > > Why do we disable it ? > > - aW Because it benefits only certain types of load and slows down the machine otherwise. Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 04:57:24 2004 Return-Path: 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 0286416A4CE for ; Mon, 15 Nov 2004 04:57:24 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D6AC43D31 for ; Mon, 15 Nov 2004 04:57:18 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAF4uGZg000966 for ; Mon, 15 Nov 2004 15:26:16 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Mon, 15 Nov 2004 15:27:06 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAF4r4h06654 for ; Mon, 15 Nov 2004 15:23:04 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDL1V7; Mon, 15 Nov 2004 15:22:58 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAF4rnqQ052684 for ; Mon, 15 Nov 2004 15:23:49 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAF4rnqb052683 for current@freebsd.org; Mon, 15 Nov 2004 15:23:49 +1030 (CST) (envelope-from wilkinsa) Date: Mon, 15 Nov 2004 15:23:49 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041115045349.GK51636@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <20041112054741.GY40520@squash.dsto.defence.gov.au> <200411120946.iAC9kAsX008350@peedub.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <200411120946.iAC9kAsX008350@peedub.jennejohn.org> User-Agent: Mutt/1.5.6i Subject: Re: dealing with interupt storms ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 04:57:24 -0000 Okay, well then why does top(1) display 85% CPU time dealing with interrupts ? - aW 0n Fri, Nov 12, 2004 at 10:46:10AM +0100, Gary Jennejohn wrote: "Wilkinson, Alex" writes: > Hi all, > > How does one stop an interrupt storm in RELENG_5 ? > > >From top(1) > > CPU states: 10.9% user, 0.0% nice, 3.9% system, 85.3% interrupt, 0.0% idle > > >From vmstat(1) > > total rate > ----- ---- > irq18: uhci2 bt0++ 9187313 426 > > 426 interrupts/sec isn't exactly a storm. I have 999/sec on my clock alone and see very low interrupt values in top. Is your top in step with your kernel? --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de _______________________________________________ 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 Mon Nov 15 06:46:42 2004 Return-Path: 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 EB3A316A4CE for ; Mon, 15 Nov 2004 06:46:42 +0000 (GMT) Received: from auk1.snu.ac.kr (auk1.snu.ac.kr [147.46.100.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8640143D41 for ; Mon, 15 Nov 2004 06:46:42 +0000 (GMT) (envelope-from spamrefuse@yahoo.com) Received: from [147.46.44.181] (spamrefuse@yahoo.com) by auk1.snu.ac.kr (Terrace Internet Messaging Server) with ESMTP id 2004111515:46:27:787278.29903.2917424048 for ; Mon, 15 Nov 2004 15:46:27 +0900 (KST) Message-ID: <419850CE.8090209@yahoo.com> Date: Mon, 15 Nov 2004 15:46:38 +0900 From: Rob User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current References: <20041109190853.GA9301@nunotex.local> In-Reply-To: <20041109190853.GA9301@nunotex.local> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-TERRACE-SPAMMARK: YES-__TRSYS_LV__3 (SR:-0.43) (SRN:SPAMROBOT) ----------------- Subject: Re: /etc/ntp.conf doesn't exist X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 06:46:43 -0000 Nuno Teixeira wrote: > Hello to all, > > I've noticed that /etc/ntp.conf doesn't exist. It's strange because > exists an empty /etc/ntp directory instead. I wonder if a very basic setup like below could serve this purpose, to have a working conf file, but might need optimizing to local conditions (server list, what to send to syslog etc.). An additional advantage, by using the pidfile and driftfile keywords here, the default ntpd_flags variable in /etc/defaults/rc.conf should become an empty string. # Process ID file, so that the daemon can be signalled from scripts pidfile /var/run/ntpd.pid # The correction calculated by ntpd(8) for the local system clock's # drift is stored here. driftfile /var/db/ntp.drift # Public servers from the pool.ntp.org project. Volunteer's servers # are dynamically assigned to the CNAMES below via DNS round-robin. # The pool.ntp.org project needs more volunteers! The only criteria to # join are a nailed-up connection and a static IP address. For details, # see the web page: # # http://www.pool.ntp.org/ # server 0.pool.ntp.org server 1.pool.ntp.org server 2.pool.ntp.org Maybe one more comment could be added here that it is better to choose servers from a list of nearby time servers; although the manpage on ntp.conf also can explain this. Rob. From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 07:04:11 2004 Return-Path: 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 7336116A4CE; Mon, 15 Nov 2004 07:04:11 +0000 (GMT) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4605643D41; Mon, 15 Nov 2004 07:04:10 +0000 (GMT) (envelope-from riggs@rrr.de) Received: from mail.m-online.net (svr8.m-online.net [192.168.3.138]) by mail-out.m-online.net (Postfix) with ESMTP id DAC904926; Mon, 15 Nov 2004 08:04:08 +0100 (CET) Received: from marvin.riggiland.au (ppp-62-245-210-9.mnet-online.de [62.245.210.9]) by mail.m-online.net (Postfix) with ESMTP id 0074221D89; Mon, 15 Nov 2004 08:04:06 +0100 (CET) Received: from marvin.riggiland.au (localhost [127.0.0.1]) by marvin.riggiland.au (8.13.1/8.13.1) with ESMTP id iAF745ZV097982; Mon, 15 Nov 2004 08:04:05 +0100 (CET) (envelope-from riggs@marvin.riggiland.au) Received: (from riggs@localhost) by marvin.riggiland.au (8.13.1/8.13.1/Submit) id iAF745HY097981; Mon, 15 Nov 2004 08:04:05 +0100 (CET) (envelope-from riggs) Date: Mon, 15 Nov 2004 08:04:04 +0100 From: "Thomas E. Zander" To: "Bjoern A. Zeeb" Message-ID: <20041115070404.GP64152@marvin.riggiland.au> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="n+lFg1Zro7sl44OB" Content-Disposition: inline In-Reply-To: Organization: RiggiServ - Ihr Partner =?iso-8859-15?Q?f?= =?iso-8859-15?Q?=FCr?= alles Delikate X-PGP-KeyID: 0xC85996CD X-PGP-URI: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xC85996CD X-PGP-Fingerprint: 4F59 75B4 4CE3 3B00 BC61 5400 8DD4 8929 C859 96CD X-Mailer: Riggisoft Ausguck Eggsbress (Build 1100500688) X-Operating-System: Riggiland BSD 5.3-RELEASE (To serve and protect.) cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 07:04:11 -0000 --n+lFg1Zro7sl44OB Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Good morning, On Sat, 13. Nov 2004, at 0:47 +0000, Bjoern A. Zeeb wrote according to [[PATCH] if_sk(4) rx/tx "hangs"]: > Any feedback appreciated. Unfortunately, it does not do the trick here (Asus P4P800SE, Marvell 88E1000, RELENG_5), but it does something else :-) I don't see watchdog timeouts anymore; instead trying to fetch a large file (> 1MB) just hangs. It starts and after 500-900k the ftp client doesn't receive further packets. ssh doesn't like this patch at all. After typing some (say, 10) chars into an ssh connection, the ssh client exits with "Bad packet length " hth, Riggs --=20 - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. --n+lFg1Zro7sl44OB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFBmFTkjdSJKchZls0RAiLrAKCHBVjbH4f+cA868+AJqCEYHh1WSACfYo4v FJELaKOyF4SsMtidy7z7Ozo= =obdE -----END PGP SIGNATURE----- --n+lFg1Zro7sl44OB-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 07:12:10 2004 Return-Path: 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 A872016A4CE for ; Mon, 15 Nov 2004 07:12:10 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id 551CC43D3F for ; Mon, 15 Nov 2004 07:12:10 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so500327rns for ; Sun, 14 Nov 2004 23:12:09 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=jOuIwCM70Gc0KRK7KJnmPjOX8wI+bGdS4FGQcudziFe12jZCDxe+XaX4V3ksYBmWRLXCKUfmywcABonQiYzwM5ntnOiUyKTRE/f7yJ52xvhkYmyp9R1t3trZ8YShNi8a1qIUhEijjgyWiaeHp2wInrE2Ey/6w6EV8fAYKGmbBQE= Received: by 10.38.26.40 with SMTP id 40mr864927rnz; Sun, 14 Nov 2004 23:12:09 -0800 (PST) Received: by 10.38.8.55 with HTTP; Sun, 14 Nov 2004 23:12:09 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 15:12:09 +0800 From: Jiawei Ye To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 07:12:10 -0000 In -current, the base for cvsup has been changed to /var/db per share/example/cvsup/ports-supfile. But setting "ports/INDEX*" in /var/db/sup/refuse does not work as advertised. cvsup still nukes my INDEX-5 when doing 'make update' in $PORTS_DIR. Any ideas? Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 07:43:52 2004 Return-Path: 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 6C08816A4CE for ; Mon, 15 Nov 2004 07:43:52 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F19C43D39 for ; Mon, 15 Nov 2004 07:43:51 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAF7hlR9066002 for ; Mon, 15 Nov 2004 08:43:48 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Mon, 15 Nov 2004 08:43:45 +0100 Message-ID: <66001.1100504625@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: config LINT fails... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 07:43:52 -0000 bang# make LINT `LINT' is up to date. bang# config LINT WARNING: kernel contains GPL contaminated ext2fs filesystem WARNING: COMPAT_SVR4 is broken and should be avoided config: Error: device "acpi_asus" is unknown config: Error: device "acpi_panasonic" is unknown config: Error: device "acpi_toshiba" is unknown config: 3 errors bang# -- 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 15 08:00:10 2004 Return-Path: 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 39A5816A4CE; Mon, 15 Nov 2004 08:00:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C49943D46; Mon, 15 Nov 2004 08:00:09 +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 E6A781FF9A8; Mon, 15 Nov 2004 09:00:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 048F51FF931; Mon, 15 Nov 2004 09:00:06 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id AA87815380; Mon, 15 Nov 2004 07:58:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 9FA5215329; Mon, 15 Nov 2004 07:58:59 +0000 (UTC) Date: Mon, 15 Nov 2004 07:58:59 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: "Thomas E. Zander" In-Reply-To: <20041115070404.GP64152@marvin.riggiland.au> Message-ID: References: <20041115070404.GP64152@marvin.riggiland.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:00:10 -0000 On Mon, 15 Nov 2004, Thomas E. Zander wrote: Hi, > On Sat, 13. Nov 2004, at 0:47 +0000, Bjoern A. Zeeb wrote > according to [[PATCH] if_sk(4) rx/tx "hangs"]: > > > Any feedback appreciated. > > Unfortunately, it does not do the trick here (Asus P4P800SE, > Marvell 88E1000, RELENG_5), but it does something else :-) personal note: subsitute Marvell 88E1000 by PN from VPD data if available. > I don't see watchdog timeouts anymore; instead trying to fetch a large good :) > file (> 1MB) just hangs. It starts and after 500-900k the ftp client > doesn't receive further packets. not so good. > ssh doesn't like this patch at all. After typing some (say, 10) chars > into an ssh connection, the ssh client exits with > "Bad packet length " what other patches did you apply ? could you please get the version from HEAD (should also work just fine with 5-STABLE) and tell me the results (including the additional dmesg lines but only the sk* parts). From the output I had already seen from you it seems we both have exactly the same chip so this is a bit strange. -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:01:57 2004 Return-Path: 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 D5BC316A4CE for ; Mon, 15 Nov 2004 08:01:57 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C4B543D1F for ; Mon, 15 Nov 2004 08:01:57 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 22362 invoked from network); 15 Nov 2004 08:01:57 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2004 08:01:57 -0000 Received: from hydrogen.funkthat.com (mzebix@localhost.funkthat.com [127.0.0.1])iAF81uB6059483; Mon, 15 Nov 2004 00:01:56 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAF81td6059482; Mon, 15 Nov 2004 00:01:55 -0800 (PST) Date: Mon, 15 Nov 2004 00:01:55 -0800 From: John-Mark Gurney To: Scott Long Message-ID: <20041115080155.GH57546@funkthat.com> Mail-Followup-To: Scott Long , "M. Warner Losh" , current@freebsd.org References: <20041112.143439.33211003.imp@bsdimp.com> <41952FBD.40602@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41952FBD.40602@freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: current@freebsd.org cc: "M. Warner Losh" Subject: Re: usb with fast interrupts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 08:01:57 -0000 Scott Long wrote this message on Fri, Nov 12, 2004 at 14:48 -0700: > M. Warner Losh wrote: > >Our usb system supports soft interrupts, but we currently don't make > >productive use of them. The following makes interrupts fast > >interrupts and uses taskqueues to queue data to a SWI. > > > >Lemme know if it works for you. > > Taskqueues aren't good for timing-sensitive operations. Even though USB > may not be terribly sensitive, I bet you'll actually see performance > drops with things like umass with this. Could you instead just put the > real handler into a kthread and wake it up, or use a swi? If you need low latency, I made taskqueue's easier to create: TASKQUEUE_DEFINE_THREAD(kqueue); and then use: taskqueue_enqueue(taskqueue_kqueue, &kq->kq_task); of course replace kqueue w/ your own string... Check the taskqueue(9) man page for more details. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:04:50 2004 Return-Path: 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 8E37C16A4CE for ; Mon, 15 Nov 2004 08:04:50 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A64B43D48 for ; Mon, 15 Nov 2004 08:04:50 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAF86mEI017365; Mon, 15 Nov 2004 01:06:48 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41986351.2070806@freebsd.org> Date: Mon, 15 Nov 2004 01:05:37 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John-Mark Gurney References: <20041112.143439.33211003.imp@bsdimp.com> <41952FBD.40602@freebsd.org> <20041115080155.GH57546@funkthat.com> In-Reply-To: <20041115080155.GH57546@funkthat.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org cc: "M. Warner Losh" Subject: Re: usb with fast interrupts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:04:50 -0000 John-Mark Gurney wrote: > Scott Long wrote this message on Fri, Nov 12, 2004 at 14:48 -0700: > >>M. Warner Losh wrote: >> >>>Our usb system supports soft interrupts, but we currently don't make >>>productive use of them. The following makes interrupts fast >>>interrupts and uses taskqueues to queue data to a SWI. >>> >>>Lemme know if it works for you. >> >>Taskqueues aren't good for timing-sensitive operations. Even though USB >>may not be terribly sensitive, I bet you'll actually see performance >>drops with things like umass with this. Could you instead just put the >>real handler into a kthread and wake it up, or use a swi? > > > If you need low latency, I made taskqueue's easier to create: > TASKQUEUE_DEFINE_THREAD(kqueue); > > and then use: > taskqueue_enqueue(taskqueue_kqueue, &kq->kq_task); > > of course replace kqueue w/ your own string... Check the taskqueue(9) > man page for more details. > So the only problem with TASKQUEUE_DEFINE_THREAD() is that it appears impossible at the moment to clean up the thread that this creates when the driver wants to unload. Scott From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:16:02 2004 Return-Path: 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 17D2916A4CE for ; Mon, 15 Nov 2004 08:16:02 +0000 (GMT) Received: from pimout1-ext.prodigy.net (pimout1-ext.prodigy.net [207.115.63.77]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88BEC43D2D for ; Mon, 15 Nov 2004 08:16:01 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [192.168.1.102] (adsl-68-123-122-146.dsl.snfc21.pacbell.net [68.123.122.146])iAF8Fs6g070038; Mon, 15 Nov 2004 03:15:55 -0500 Message-ID: <419865B9.8010205@elischer.org> Date: Mon, 15 Nov 2004 00:15:53 -0800 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8a3) Gecko/20041017 X-Accept-Language: en, hu MIME-Version: 1.0 To: Julian Elischer References: <4197DB02.8050601@elischer.org> In-Reply-To: <4197DB02.8050601@elischer.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:16:02 -0000 Julian Elischer wrote: > > I upgraded my Dell Inspiron 7500 to RELENG_5 and have been seeing all > sorts of problems. > Previously it was running 5.3 beta7 and seemed happy with that. > > the symptoms.. > boot to single user succeeds. > however if the filesyste,s do not need cleaning (?) > it will freeze solit part way through going to multi-user.. > usually just after printing "preserving vi files" (or whatever the > actual message is). > > However if the filesystems DO need checking. > it says that te filesyste, wil be checked in background, > and that background fsck will be started in 60 seconds, and teh boot > succeeds > all the way to multi user mode. > > Once there, though I have to live with the slowdown of the fsck running... > > Even before fsck starts however, everything appears VERY slow. The mouse > reponds slowly and jerkily. > > This was all not true with 5.3B7 so it's a recent change.. Going back to 5.3RELEASE fixes it.. I have no clue as to the problem.. the system freezes absolutly from yesterday's RELENG_5 or doesn't fail. No debugger, no dump etc.. > > > _______________________________________________ > 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 Mon Nov 15 08:10:06 2004 Return-Path: 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 B07FC16A4CE; Mon, 15 Nov 2004 08:10:06 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9123C43D49; Mon, 15 Nov 2004 08:10:05 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) iAF89QU600362; Mon, 15 Nov 2004 09:09:26 +0100 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) iAF89QI229786; Mon, 15 Nov 2004 09:09:26 +0100 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id iAF8A0u29719; Mon, 15 Nov 2004 09:10:01 +0100 (MET) Date: Mon, 15 Nov 2004 09:15:00 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Alexander Leidinger In-Reply-To: <20041113092215.7a40f133@Magellan.Leidinger.net> Message-ID: <20041115091059.L51863@beagle.kn.op.dlr.de> References: <6857.1100271323@critter.freebsd.dk> <20041112160137.X42945@beagle.kn.op.dlr.de> <20041112171024.P42945@beagle.kn.op.dlr.de> <20041113092215.7a40f133@Magellan.Leidinger.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: [TEST] make -j patch [take 2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 08:10:06 -0000 On Sat, 13 Nov 2004, Alexander Leidinger wrote: AL>On Fri, 12 Nov 2004 17:11:37 +0100 (CET) AL>Harti Brandt wrote: AL> AL>> On Fri, 12 Nov 2004 Alexander@Leidinger.net wrote: AL>> AL>> > Zitat von Harti Brandt : AL>> > AL>> >> PK>>If yes: we have some ports which aren't -j safe, so this would violate AL>> >> PK>>POLA. AL>> >> PK> AL>> >> PK>That is what "make -B" is for. AL>> >> AL>> >> Or .NOTPARALLEL AL>> > AL>> > I'm not talking about /usr/ports/category/port/Makefile, I'm talking about AL>> > /usr/ports/category/port/work/tarball_dir/**/Makefile. We don't have AL>> > control about those Makefiles. AL>> > AL>> > As much as I like a flag in the Makefile of a port which indicates AL>> > that a port can't be build with -j, we don't have this and the last time AL>> > this topic was discussed there was a strong objection to something like AL>> > this. AL>> > AL>> > So this change may break procedures which worked so far. AL>> AL>> How? If you specify -j on the port's make the -j gets passed down to all AL>> sub-makes via MAKEFLAGS and they use it. The difference is just that the AL>> overall number of jobs started is now limited by the original -j. AL> AL>In my first mail I made an example where a portupgrade is in between two AL>make processes. make runs several portupgrade processes in parallel and AL>portupgrade calls make. AFAIK this doesn't result in in an invocation of AL>portupgrades child-make with -j. With phk's changes the child-make of AL>portupgrade uses the FIFO (at least this is what I read implicitly in AL>phk's response above). Unless you reset MAKEFLAGS along the call path to the portupgrade's make they'll see the -j, because the top-level make will stuff the -j into MAKEFLAGS and that is probably inherited through portupgrade. harti From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:17:59 2004 Return-Path: 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 1134E16A4CE for ; Mon, 15 Nov 2004 08:17:59 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47A4343D2D for ; Mon, 15 Nov 2004 08:17:58 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAF8HvNE094278 for ; Mon, 15 Nov 2004 09:17:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 15 Nov 2004 08:43:45 +0100." <66001.1100504625@critter.freebsd.dk> Date: Mon, 15 Nov 2004 09:17:57 +0100 Message-ID: <94277.1100506677@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: config LINT fails... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:17:59 -0000 In message <66001.1100504625@critter.freebsd.dk>, Poul-Henning Kamp writes: > >bang# make LINT >`LINT' is up to date. >bang# config LINT >WARNING: kernel contains GPL contaminated ext2fs filesystem >WARNING: COMPAT_SVR4 is broken and should be avoided >config: Error: device "acpi_asus" is unknown >config: Error: device "acpi_panasonic" is unknown >config: Error: device "acpi_toshiba" is unknown >config: 3 errors >bang# Wow, our maillists are a bit behind today. Anyway: fixed. -- 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 15 08:31:22 2004 Return-Path: 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 3B9EE16A4CE for ; Mon, 15 Nov 2004 08:31:22 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01ADE43D2D for ; Mon, 15 Nov 2004 08:31:22 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: (qmail 26324 invoked from network); 15 Nov 2004 08:31:21 -0000 Received: from gate.funkthat.com (HELO hydrogen.funkthat.com) ([69.17.45.168]) (envelope-sender ) by mail3.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 15 Nov 2004 08:31:21 -0000 Received: from hydrogen.funkthat.com (gfelop@localhost.funkthat.com [127.0.0.1])iAF8VKB6060220; Mon, 15 Nov 2004 00:31:20 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.10/8.12.10/Submit) id iAF8VKua060219; Mon, 15 Nov 2004 00:31:20 -0800 (PST) Date: Mon, 15 Nov 2004 00:31:20 -0800 From: John-Mark Gurney To: Scott Long Message-ID: <20041115083120.GI57546@funkthat.com> Mail-Followup-To: Scott Long , "M. Warner Losh" , current@freebsd.org References: <20041112.143439.33211003.imp@bsdimp.com> <41952FBD.40602@freebsd.org> <20041115080155.GH57546@funkthat.com> <41986351.2070806@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41986351.2070806@freebsd.org> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html cc: current@freebsd.org cc: "M. Warner Losh" Subject: Re: usb with fast interrupts X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 08:31:22 -0000 Scott Long wrote this message on Mon, Nov 15, 2004 at 01:05 -0700: > John-Mark Gurney wrote: > >Scott Long wrote this message on Fri, Nov 12, 2004 at 14:48 -0700: > > > >>M. Warner Losh wrote: > >> > >>>Our usb system supports soft interrupts, but we currently don't make > >>>productive use of them. The following makes interrupts fast > >>>interrupts and uses taskqueues to queue data to a SWI. > >>> > >>>Lemme know if it works for you. > >> > >>Taskqueues aren't good for timing-sensitive operations. Even though USB > >>may not be terribly sensitive, I bet you'll actually see performance > >>drops with things like umass with this. Could you instead just put the > >>real handler into a kthread and wake it up, or use a swi? > > > > > >If you need low latency, I made taskqueue's easier to create: > >TASKQUEUE_DEFINE_THREAD(kqueue); > > > >and then use: > > taskqueue_enqueue(taskqueue_kqueue, &kq->kq_task); > > > >of course replace kqueue w/ your own string... Check the taskqueue(9) > >man page for more details. > > > > So the only problem with TASKQUEUE_DEFINE_THREAD() is that it appears > impossible at the moment to clean up the thread that this creates when > the driver wants to unload. That shouldn't be too hard to fix. :) -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:40:48 2004 Return-Path: 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 3592416A4CE for ; Mon, 15 Nov 2004 08:40:48 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73A2843D41 for ; Mon, 15 Nov 2004 08:40:47 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id iAF8e0Lc032614; Mon, 15 Nov 2004 00:40:01 -0800 From: Kent Stewart To: freebsd-current@freebsd.org, Jiawei Ye Date: Mon, 15 Nov 2004 00:40:45 -0800 User-Agent: KMail/1.7.1 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: <200411150040.45281.kstewart@owt.com> Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:40:48 -0000 On Sunday 14 November 2004 11:12 pm, Jiawei Ye wrote: > In -current, the base for cvsup has been changed to /var/db per > share/example/cvsup/ports-supfile. But setting "ports/INDEX*" in > /var/db/sup/refuse does not work as advertised. cvsup still nukes my > INDEX-5 when doing 'make update' in $PORTS_DIR. > > Any ideas? It won't download a new one. It just deletes the old one. It goes along with removing INDEX[-5] from cvs. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:47:13 2004 Return-Path: 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 A026A16A4CE; Mon, 15 Nov 2004 08:47:13 +0000 (GMT) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 066DD43D1F; Mon, 15 Nov 2004 08:47:13 +0000 (GMT) (envelope-from riggs@rrr.de) Received: from mail.m-online.net (svr8.m-online.net [192.168.3.138]) by mail-out.m-online.net (Postfix) with ESMTP id DB9C94FFB; Mon, 15 Nov 2004 09:47:11 +0100 (CET) Received: from marvin.riggiland.au (ppp-62-245-210-9.mnet-online.de [62.245.210.9]) by mail.m-online.net (Postfix) with ESMTP id 8DF382096D; Mon, 15 Nov 2004 09:47:09 +0100 (CET) Received: from marvin.riggiland.au (localhost [127.0.0.1]) by marvin.riggiland.au (8.13.1/8.13.1) with ESMTP id iAF8l8nK099695; Mon, 15 Nov 2004 09:47:08 +0100 (CET) (envelope-from riggs@marvin.riggiland.au) Received: (from riggs@localhost) by marvin.riggiland.au (8.13.1/8.13.1/Submit) id iAF8l7G6099694; Mon, 15 Nov 2004 09:47:07 +0100 (CET) (envelope-from riggs) Date: Mon, 15 Nov 2004 09:47:05 +0100 From: "Thomas E. Zander" To: "Bjoern A. Zeeb" Message-ID: <20041115084705.GQ64152@marvin.riggiland.au> References: <20041115070404.GP64152@marvin.riggiland.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L2Brqb15TUChFOBK" Content-Disposition: inline In-Reply-To: Organization: RiggiServ - Ihr Partner =?iso-8859-15?Q?f?= =?iso-8859-15?Q?=FCr?= alles Delikate X-PGP-KeyID: 0xC85996CD X-PGP-URI: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xC85996CD X-PGP-Fingerprint: 4F59 75B4 4CE3 3B00 BC61 5400 8DD4 8929 C859 96CD X-Mailer: Riggisoft Ausguck Eggsbress (Build 1100508070) X-Operating-System: Riggiland BSD 5.3-RELEASE (To serve and protect.) cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:47:13 -0000 --L2Brqb15TUChFOBK Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, On Mon, 15. Nov 2004, at 7:58 +0000, Bjoern A. Zeeb wrote according to [Re: [PATCH] if_sk(4) rx/tx "hangs"]: > what other patches did you apply ? This morning just the ram patch. > could you please get the version from HEAD (should also work just fine > with 5-STABLE) and tell me the results (including the additional dmesg > lines but only the sk* parts). Of course, I'll do it tonight asap. > From the output I had already seen from you it seems we both have > exactly the same chip so this is a bit strange. Well, afair you haven't got the "watchdog timeout" messages, have you? That's another strange difference considering our chips should be identical. Riggs --=20 - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. --L2Brqb15TUChFOBK Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFBmG0JjdSJKchZls0RAmWUAJoCsADwwX8eqKSjkMboZUrXHX+w6QCffzLd Pa0iJXr7BQl/ct3YrfRJiDk= =mOxa -----END PGP SIGNATURE----- --L2Brqb15TUChFOBK-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:53:59 2004 Return-Path: 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 3C79716A4CE for ; Mon, 15 Nov 2004 08:53:59 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id C399B43D45 for ; Mon, 15 Nov 2004 08:53:58 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so502058rns for ; Mon, 15 Nov 2004 00:53:58 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=dWDwT/RcwL34A3VU9IVgk9xzmhcWzAg5rDH9BwuG/RqsF89sKWZDi4CSQULHF+IcpUs418oxqPPZSlthkA0K2Zd1EZId37XMpAKoGQIM7qwWzZ8KYbC8G88UHqN9NzrWQIihqsaadPB3ioc4cTp71mdrC4sgfo03Fmc1W00xR+E= Received: by 10.38.206.14 with SMTP id d14mr396146rng; Mon, 15 Nov 2004 00:53:58 -0800 (PST) Received: by 10.38.8.55 with HTTP; Mon, 15 Nov 2004 00:53:58 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 16:53:58 +0800 From: Jiawei Ye To: Kent Stewart In-Reply-To: <200411150040.45281.kstewart@owt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200411150040.45281.kstewart@owt.com> cc: freebsd-current@freebsd.org Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 08:53:59 -0000 On Mon, 15 Nov 2004 00:40:45 -0800, Kent Stewart wrote: > On Sunday 14 November 2004 11:12 pm, Jiawei Ye wrote: > > In -current, the base for cvsup has been changed to /var/db per > > share/example/cvsup/ports-supfile. But setting "ports/INDEX*" in > > /var/db/sup/refuse does not work as advertised. cvsup still nukes my > > INDEX-5 when doing 'make update' in $PORTS_DIR. > > > > Any ideas? > > It won't download a new one. It just deletes the old one. It goes along with > removing INDEX[-5] from cvs. > > Kent Then we really need to update our cvsup man page: " The patterns are separated by whitespace, and multiple patterns are permitted on each line. Files and directories matching the patterns are neither updated nor deleted; they are simply ignored." The advertised behaviour is different from what actually happened. -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:55:24 2004 Return-Path: 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 B5ACD16A4CE for ; Mon, 15 Nov 2004 08:55:24 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A13943D2F for ; Mon, 15 Nov 2004 08:55:24 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so502075rns for ; Mon, 15 Nov 2004 00:55:24 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Uq5A9srBaCYgXaT0ZLZMzsxR8UaCUyFsqTJpzvpB0ZENVFYcHX4YnpXXScdiPCzW5OEQgfzcGQf5SHT2hrrYVxfEZr9gCXEZ4eSgCbJNH9ZHkM8etyMfMfopIB+90l+shHfuHsZIXq2d0BCAVK9KThXLsJeSI/ZgJDsDp1uCb1E= Received: by 10.38.179.67 with SMTP id b67mr899683rnf; Mon, 15 Nov 2004 00:55:23 -0800 (PST) Received: by 10.38.8.55 with HTTP; Mon, 15 Nov 2004 00:55:23 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 16:55:23 +0800 From: Jiawei Ye To: freebsd-current@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 08:55:24 -0000 On Mon, 15 Nov 2004 15:12:09 +0800, Jiawei Ye wrote: > In -current, the base for cvsup has been changed to /var/db per > share/example/cvsup/ports-supfile. But setting "ports/INDEX*" in > /var/db/sup/refuse does not work as advertised. cvsup still nukes my > INDEX-5 when doing 'make update' in $PORTS_DIR. I don't like replying to my own post, but to quote cvsup manpage: " The patterns are separated by whitespace, and multiple patterns are permitted on each line. Files and directories matching the patterns are neither updated nor deleted; they are simply ignored." Which is not true since the file *does* get removed (since the removal of INDEX* in cvs). -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 09:20:32 2004 Return-Path: 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 6359116A4CE for ; Mon, 15 Nov 2004 09:20:32 +0000 (GMT) Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3F6D143D58 for ; Mon, 15 Nov 2004 09:20:30 +0000 (GMT) (envelope-from andreas@klemm.apsfilter.org) Received: from srv1.cosmo-project.de (localhost [IPv6:::1]) iAF9KIL9038841 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 15 Nov 2004 10:20:18 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: (from uucp@localhost)iAF9KHRh038840; Mon, 15 Nov 2004 10:20:17 +0100 (CET) (envelope-from andreas@klemm.apsfilter.org) Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org [127.0.0.1]) by klemm.apsfilter.org (8.13.1/8.13.1) with ESMTP id iAF9F2Y8010102; Mon, 15 Nov 2004 10:15:02 +0100 (CET) (envelope-from andreas@titan.klemm.apsfilter.org) Received: (from andreas@localhost) by titan.klemm.apsfilter.org (8.13.1/8.13.1/Submit) id iAF9F0Mq010098; Mon, 15 Nov 2004 10:15:00 +0100 (CET) (envelope-from andreas) Date: Mon, 15 Nov 2004 10:15:00 +0100 From: Andreas Klemm To: Julian Elischer Message-ID: <20041115091500.GA9959@titan.klemm.apsfilter.org> References: <4197DB02.8050601@elischer.org> <419865B9.8010205@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419865B9.8010205@elischer.org> X-Operating-System: FreeBSD 5.3-STABLE X-Disclaimer: A free society is one where it is safe to be unpopular User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 09:20:32 -0000 On Mon, Nov 15, 2004 at 12:15:53AM -0800, Julian Elischer wrote: > I have no clue as to the problem.. the system freezes absolutly > from yesterday's RELENG_5 or doesn't fail. No debugger, no dump etc.. Same for me. Left the system in X11 (fvwm2) yesterday evening and 2-3 hours later it kind of freezed. Its the 2nd or 3rd time in the last week. This morning I only saw a black screen not more. Powercycled and only found this in messages: Nov 15 02:06:47 titan postgres[8020]: [12-1] ERROR: duplicate key violates uniq ue constraint "dspam_token_data_token_key" Nov 15 02:07:37 titan postgres[8020]: [13-1] ERROR: duplicate key violates uniq ue constraint "dspam_token_data_token_key" Nov 15 02:35:21 titan postgres[9339]: [2-1] ERROR: duplicate key violates uniqu e constraint "dspam_token_data_token_key" Nov 15 02:35:21 titan postgres[9339]: [3-1] ERROR: duplicate key violates uniqu e constraint "dspam_token_data_token_key" Nov 15 08:54:18 titan syslogd: kernel boot file is /boot/kernel/kernel Nov 15 08:54:18 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project. Nov 15 08:54:18 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 15 08:54:18 titan kernel: The Regents of the University of California. All r Andreas /// am I maybe using bad kernel options ? ADAPTIVE_GIANT ? See kernel options and /var/log/messages of today. The fsck was needed since I had to hit reset. FreeBSD titan.klemm.apsfilter.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004 root@titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN i386 options KTRACE #ktrace(1) support options PANIC_REBOOT_WAIT_TIME=-1 machine i386 cpu I686_CPU ident TITAN options INCLUDE_CONFIG_FILE # Include this file in kernel options SCHED_4BSD #4BSD scheduler options ADAPTIVE_GIANT # Giant mutex is adaptive. options VFS_AIO # vmware options INET #InterNETworking options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support options UFS_EXTATTR options UFS_ACL #Support for access control lists options UFS_DIRHASH #Improve performance on big directories options MD_ROOT #MD is a potential root device options CD9660 #ISO 9660 Filesystem options PSEUDOFS #Pseudo-filesystem framework options PROCFS #Process filesystem (requires PSEUDOFS) options FDESCFS #File descriptor filesystem options MSDOSFS #MS DOS File System (FAT, FAT32) options GEOM_GPT #Disk Encryption options GEOM_BDE #Disk Encryption options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 #Compatible with FreeBSD4 options _KPOSIX_PRIORITY_SCHEDULING #Posix P1003_1B real-time extensions options KBD_INSTALL_CDEV # install a CDEV entry in /dev options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #enable logging to syslogd(8) options IPDIVERT #divert sockets options IPSTEALTH #support for stealth forwarding options DUMMYNET options ZERO_COPY_SOCKETS options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options ALTQ options ALTQ_CBQ # Class Bases Queueing options ALTQ_RED # Random Early Drop options ALTQ_RIO # RED In/Out options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing # Postgresql database options SYSVSHM options SYSVSEM options SYSVMSG options SHMMAXPGS=65536 options SEMMNI=40 options SEMMNS=240 options SEMUME=40 options SEMMNU=120 device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives options ATA_STATIC_ID #Static device numbering # SCSI bus device scbus # base SCSI code device da # SCSI direct access devices (aka disks) device cd # device pass # CAM passthrough driver device atapicam # emulate ATAPI devices as SCSI ditto via CAM # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc options SC_HISTORY_SIZE=512 # number of history buffer lines options SC_PIXEL_MODE # add support for the raster text mode device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocate. device random # Entropy device device loop # Network loopback device ether # Ethernet support device pty # Pseudo-ttys (telnet etc) device md # Memory "disks" # The `bpf' device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! device bpf # Berkeley packet filter # new 5.3 device mem # Memory and kernel memory devices device io # I/O device # USB support #options USB_DEBUG device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device ehci # OHCI PCI->USB interface device usb # USB Bus (required) #device udbp # USB Double Bulk Pipe devices device ugen # Generic device uhid # "Human Interface Devices" device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device urio # Diamond Rio 500 MP3 player device uscanner # Scanners device ucom # USB serial support Nov 15 00:19:52 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project. Nov 15 00:19:52 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 15 00:19:52 titan kernel: The Regents of the University of California. All rights reserved. Nov 15 00:19:52 titan kernel: FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004 Nov 15 00:19:52 titan kernel: root@titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN Nov 15 00:19:52 titan kernel: WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant Nov 15 00:19:52 titan kernel: WARNING: MPSAFE network stack disabled, expect reduced performance. Nov 15 00:19:52 titan kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Nov 15 00:19:52 titan kernel: CPU: Intel Pentium III (997.46-MHz 686-class CPU) Nov 15 00:19:52 titan kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Nov 15 00:19:52 titan kernel: Features=0x383f9ff Nov 15 00:19:52 titan kernel: real memory = 536854528 (511 MB) Nov 15 00:19:52 titan kernel: avail memory = 519884800 (495 MB) Nov 15 00:19:52 titan kernel: npx0: [FAST] Nov 15 00:19:52 titan kernel: npx0: on motherboard Nov 15 00:19:52 titan kernel: npx0: INT 16 interface Nov 15 00:19:52 titan kernel: acpi0: on motherboard Nov 15 00:19:52 titan kernel: acpi0: Power Button (fixed) Nov 15 00:19:52 titan kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Nov 15 00:19:52 titan kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 Nov 15 00:19:52 titan kernel: cpu0: on acpi0 Nov 15 00:19:52 titan kernel: acpi_button0: on acpi0 Nov 15 00:19:52 titan kernel: pcib0: port 0xcf8-0xcff on acpi0 Nov 15 00:19:52 titan kernel: pci0: on pcib0 Nov 15 00:19:52 titan kernel: agp0: mem 0xf0000000-0xf7ffffff at device 0.0 on pci0 Nov 15 00:19:52 titan kernel: pcib1: at device 1.0 on pci0 Nov 15 00:19:52 titan kernel: pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.AGP_ - AE_NOT_FOUND Nov 15 00:19:52 titan kernel: pci1: on pcib1 Nov 15 00:19:52 titan kernel: pcib0: no PRT entry for 0.1.INTA Nov 15 00:19:52 titan kernel: pci1: at device 0.0 (no driver attached) Nov 15 00:19:52 titan kernel: pci1: at device 0.1 (no driver attached) Nov 15 00:19:52 titan kernel: isab0: at device 4.0 on pci0 Nov 15 00:19:52 titan kernel: isa0: on isab0 Nov 15 00:19:52 titan kernel: atapci0: port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 Nov 15 00:19:52 titan kernel: ata0: channel #0 on atapci0 Nov 15 00:19:52 titan kernel: ata1: channel #1 on atapci0 Nov 15 00:19:52 titan kernel: uhci0: port 0xb400-0xb41f irq 11 at device 4.2 on pci0 Nov 15 00:19:52 titan kernel: uhci0: [GIANT-LOCKED] Nov 15 00:19:52 titan kernel: usb0: on uhci0 Nov 15 00:19:52 titan kernel: usb0: USB revision 1.0 Nov 15 00:19:52 titan kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Nov 15 00:19:52 titan kernel: uhub0: 2 ports with 2 removable, self powered Nov 15 00:19:52 titan kernel: ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 255/204 Nov 15 00:19:52 titan kernel: ulpt0: using bi-directional mode Nov 15 00:19:52 titan kernel: umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2 Nov 15 00:19:52 titan kernel: ugen0: Syncrosoft Protected Executer, rev 1.10/1.01, addr 3 Nov 15 00:19:52 titan kernel: uhci1: port 0xb000-0xb01f irq 11 at device 4.3 on pci0 Nov 15 00:19:52 titan kernel: uhci1: [GIANT-LOCKED] Nov 15 00:19:52 titan kernel: usb1: on uhci1 Nov 15 00:19:52 titan kernel: usb1: USB revision 1.0 Nov 15 00:19:52 titan kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Nov 15 00:19:52 titan kernel: uhub1: 2 ports with 2 removable, self powered Nov 15 00:19:52 titan kernel: fxp0: port 0xa800-0xa83f mem 0xd5800000-0xd58fffff,0xd6000000-0xd6000fff irq 10 at device 9.0 on pci0 Nov 15 00:19:52 titan kernel: miibus0: on fxp0 Nov 15 00:19:52 titan kernel: inphy0: on miibus0 Nov 15 00:19:52 titan kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Nov 15 00:19:52 titan kernel: fxp0: Ethernet address: 00:d0:b7:ba:c1:c2 Nov 15 00:19:52 titan kernel: fxp0: [GIANT-LOCKED] Nov 15 00:19:52 titan kernel: pci0: at device 10.0 (no driver attached) Nov 15 00:19:52 titan kernel: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 Nov 15 00:19:52 titan kernel: fdc0: [FAST] Nov 15 00:19:52 titan kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Nov 15 00:19:52 titan kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Nov 15 00:19:52 titan kernel: sio0: type 16550A Nov 15 00:19:52 titan kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Nov 15 00:19:52 titan kernel: atkbd0: irq 1 on atkbdc0 Nov 15 00:19:52 titan kernel: kbd0 at atkbd0 Nov 15 00:19:52 titan kernel: atkbd0: [GIANT-LOCKED] Nov 15 00:19:52 titan kernel: psm0: irq 12 on atkbdc0 Nov 15 00:19:52 titan kernel: psm0: [GIANT-LOCKED] Nov 15 00:19:52 titan kernel: psm0: model IntelliMouse Explorer, device ID 4 Nov 15 00:19:52 titan kernel: orm0: at iomem 0xd0000-0xd17ff,0xc0000-0xccfff on isa0 Nov 15 00:19:52 titan kernel: sc0: at flags 0x100 on isa0 Nov 15 00:19:52 titan kernel: sc0: VGA <16 virtual consoles, flags=0x300> Nov 15 00:19:52 titan kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Nov 15 00:19:52 titan kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Nov 15 00:19:52 titan kernel: sio1: port may not be enabled Nov 15 00:19:52 titan kernel: Timecounter "TSC" frequency 997461263 Hz quality 800 Nov 15 00:19:52 titan kernel: Timecounters tick every 10.000 msec Nov 15 00:19:52 titan kernel: IPsec: Initialized Security Association Processing. Nov 15 00:19:52 titan kernel: ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited Nov 15 00:19:52 titan kernel: acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% Nov 15 00:19:52 titan kernel: ad0: 176700MB [359010/16/63] at ata0-master UDMA66 Nov 15 00:19:52 titan kernel: acd0: DVDROM at ata0-slave UDMA33 Nov 15 00:19:52 titan kernel: ad2: 176700MB [359010/16/63] at ata1-master UDMA66 Nov 15 00:19:52 titan kernel: acd1: DVDR at ata1-slave UDMA33 Nov 15 00:19:52 titan kernel: cd0 at ata0 bus 0 target 1 lun 0 Nov 15 00:19:52 titan kernel: cd0: Removable CD-ROM SCSI-0 device Nov 15 00:19:52 titan kernel: cd0: 33.000MB/s transfers Nov 15 00:19:52 titan kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Nov 15 00:19:52 titan kernel: cd1 at ata1 bus 0 target 1 lun 0 Nov 15 00:19:52 titan kernel: cd1: Removable CD-ROM SCSI-0 device Nov 15 00:19:52 titan kernel: cd1: 33.000MB/s transfers Nov 15 00:19:52 titan kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present Nov 15 00:19:52 titan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 15 00:19:52 titan kernel: da0: Removable Direct Access SCSI-2 device Nov 15 00:19:52 titan kernel: da0: 1.000MB/s transfers Nov 15 00:19:52 titan kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 00:19:52 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 00:19:52 titan kernel: Opened disk da0 -> 6 Nov 15 00:19:52 titan kernel: Mounting root from ufs:/dev/ad2s1a Nov 15 00:19:52 titan savecore: no dumps found Nov 15 00:19:53 titan named[330]: starting BIND 9.3.0 -u bind -t /var/named Nov 15 00:19:53 titan named[330]: command channel listening on 127.0.0.1#953 Nov 15 00:20:02 titan rpcbind: cannot create socket for udp6 Nov 15 00:20:03 titan lpd[491]: lpd startup: logging=0 Nov 15 00:20:03 titan ntpd[503]: ntpd 4.2.0-a Wed Nov 10 11:31:07 CET 2004 (1) Nov 15 00:20:03 titan ntpd[503]: no IPv6 interfaces found Nov 15 00:20:10 titan kernel: WARNING: driver "vmmon" used unreserved major device number 200 Nov 15 00:20:10 titan kernel: vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 (3.2.x mvm) $ Nov 15 00:20:10 titan kernel: vmmon: Module vmmon: initialized Nov 15 00:22:20 titan su: andreas to root on /dev/ttyp0 Nov 15 00:23:16 titan ntpd[503]: kernel time sync disabled 2041 Nov 15 00:24:19 titan ntpd[503]: kernel time sync enabled 2001 Nov 15 00:40:13 titan sm-mta[3643]: iAENUQAK003576: Truncated MIME Content-Type header due to field size (length = 129) (possible attack) Nov 15 00:47:05 titan postgres[5415]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:47:05 titan postgres[5415]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5625]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:25 titan postgres[5618]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5625]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5618]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5618]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5618]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5625]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5625]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:26 titan postgres[5618]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5625]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5625]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5618]: [14-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:27 titan postgres[5625]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5618]: [15-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [14-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [15-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [16-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5618]: [16-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [17-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [18-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5618]: [17-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5618]: [18-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5618]: [19-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:28 titan postgres[5625]: [19-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5618]: [20-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5618]: [21-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [20-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [21-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [22-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5618]: [22-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [23-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [24-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [25-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [26-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5618]: [23-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [27-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:29 titan postgres[5625]: [28-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [29-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [24-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [30-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [25-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [31-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [32-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [26-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [27-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [28-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [33-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [29-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [34-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [35-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5618]: [30-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:30 titan postgres[5625]: [36-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5618]: [31-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5618]: [32-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5625]: [37-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5625]: [38-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5625]: [39-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5618]: [33-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5618]: [34-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5625]: [40-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5625]: [41-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 00:50:31 titan postgres[5618]: [35-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:12:00 titan postgres[6697]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:15:09 titan postgres[6633]: [2-1] ERROR: deadlock detected Nov 15 01:15:09 titan postgres[6633]: [2-2] DETAIL: Process 6633 waits for ShareLock on transaction 1158996; blocked by process 5748. Nov 15 01:15:09 titan postgres[6633]: [2-3] Process 5748 waits for ShareLock on transaction 1163189; blocked by process 6633. Nov 15 01:48:32 titan postgres[7490]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:48:45 titan postgres[7490]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:48:53 titan postgres[7490]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:49:15 titan postgres[7490]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:49:15 titan postgres[7490]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:49:53 titan postgres[7490]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:50:15 titan postgres[7490]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 01:50:36 titan postgres[7490]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:10 titan postgres[8020]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:15 titan postgres[8020]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:26 titan postgres[8020]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:35 titan postgres[8020]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:47 titan postgres[8020]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:05:56 titan postgres[8020]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:06:05 titan postgres[8020]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:06:07 titan postgres[8020]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:06:40 titan postgres[8020]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:06:47 titan postgres[8020]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:06:47 titan postgres[8020]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:07:37 titan postgres[8020]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:35:21 titan postgres[9339]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 02:35:21 titan postgres[9339]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 08:54:18 titan syslogd: kernel boot file is /boot/kernel/kernel Nov 15 08:54:18 titan kernel: Copyright (c) 1992-2004 The FreeBSD Project. Nov 15 08:54:18 titan kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Nov 15 08:54:18 titan kernel: The Regents of the University of California. All rights reserved. Nov 15 08:54:18 titan kernel: FreeBSD 5.3-STABLE #0: Wed Nov 10 10:37:30 CET 2004 Nov 15 08:54:18 titan kernel: root@titan.klemm.apsfilter.org:/usr/src/sys/i386/compile/TITAN Nov 15 08:54:18 titan kernel: WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant Nov 15 08:54:18 titan kernel: WARNING: MPSAFE network stack disabled, expect reduced performance. Nov 15 08:54:18 titan kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Nov 15 08:54:18 titan kernel: CPU: Intel Pentium III (997.46-MHz 686-class CPU) Nov 15 08:54:18 titan kernel: Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Nov 15 08:54:18 titan kernel: Features=0x383f9ff Nov 15 08:54:18 titan kernel: real memory = 536854528 (511 MB) Nov 15 08:54:18 titan kernel: avail memory = 519884800 (495 MB) Nov 15 08:54:18 titan kernel: npx0: [FAST] Nov 15 08:54:18 titan kernel: npx0: on motherboard Nov 15 08:54:18 titan kernel: npx0: INT 16 interface Nov 15 08:54:18 titan kernel: acpi0: on motherboard Nov 15 08:54:18 titan kernel: acpi0: Power Button (fixed) Nov 15 08:54:18 titan kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Nov 15 08:54:18 titan kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0 Nov 15 08:54:18 titan kernel: cpu0: on acpi0 Nov 15 08:54:18 titan kernel: acpi_button0: on acpi0 Nov 15 08:54:18 titan kernel: pcib0: port 0xcf8-0xcff on acpi0 Nov 15 08:54:18 titan kernel: pci0: on pcib0 Nov 15 08:54:18 titan kernel: agp0: mem 0xf0000000-0xf7ffffff at device 0.0 on pci0 Nov 15 08:54:18 titan kernel: pcib1: at device 1.0 on pci0 Nov 15 08:54:18 titan kernel: pcib1: could not get PCI interrupt routing table for \_SB_.PCI0.AGP_ - AE_NOT_FOUND Nov 15 08:54:18 titan kernel: pci1: on pcib1 Nov 15 08:54:18 titan kernel: pcib0: no PRT entry for 0.1.INTA Nov 15 08:54:18 titan kernel: pci1: at device 0.0 (no driver attached) Nov 15 08:54:18 titan kernel: pci1: at device 0.1 (no driver attached) Nov 15 08:54:18 titan kernel: isab0: at device 4.0 on pci0 Nov 15 08:54:18 titan kernel: isa0: on isab0 Nov 15 08:54:18 titan kernel: atapci0: port 0xb800-0xb80f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 4.1 on pci0 Nov 15 08:54:18 titan kernel: ata0: channel #0 on atapci0 Nov 15 08:54:18 titan kernel: ata1: channel #1 on atapci0 Nov 15 08:54:18 titan kernel: uhci0: port 0xb400-0xb41f irq 11 at device 4.2 on pci0 Nov 15 08:54:18 titan kernel: uhci0: [GIANT-LOCKED] Nov 15 08:54:18 titan kernel: usb0: on uhci0 Nov 15 08:54:18 titan kernel: usb0: USB revision 1.0 Nov 15 08:54:18 titan kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Nov 15 08:54:18 titan kernel: uhub0: 2 ports with 2 removable, self powered Nov 15 08:54:18 titan kernel: ulpt0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2, iclass 255/204 Nov 15 08:54:18 titan kernel: ulpt0: using bi-directional mode Nov 15 08:54:18 titan kernel: umass0: Hewlett-Packard PSC 2200 Series, rev 2.00/1.00, addr 2 Nov 15 08:54:18 titan kernel: ugen0: Syncrosoft Protected Executer, rev 1.10/1.01, addr 3 Nov 15 08:54:18 titan kernel: uhci1: port 0xb000-0xb01f irq 11 at device 4.3 on pci0 Nov 15 08:54:18 titan kernel: uhci1: [GIANT-LOCKED] Nov 15 08:54:18 titan kernel: usb1: on uhci1 Nov 15 08:54:18 titan kernel: usb1: USB revision 1.0 Nov 15 08:54:18 titan kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Nov 15 08:54:18 titan kernel: uhub1: 2 ports with 2 removable, self powered Nov 15 08:54:18 titan kernel: fxp0: port 0xa800-0xa83f mem 0xd5800000-0xd58fffff,0xd6000000-0xd6000fff irq 10 at device 9.0 on pci0 Nov 15 08:54:18 titan kernel: miibus0: on fxp0 Nov 15 08:54:18 titan kernel: inphy0: on miibus0 Nov 15 08:54:18 titan kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Nov 15 08:54:18 titan kernel: fxp0: Ethernet address: 00:d0:b7:ba:c1:c2 Nov 15 08:54:18 titan kernel: fxp0: [GIANT-LOCKED] Nov 15 08:54:18 titan kernel: pci0: at device 10.0 (no driver attached) Nov 15 08:54:18 titan kernel: fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 Nov 15 08:54:18 titan kernel: fdc0: [FAST] Nov 15 08:54:18 titan kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Nov 15 08:54:18 titan kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Nov 15 08:54:18 titan kernel: sio0: type 16550A Nov 15 08:54:18 titan kernel: atkbdc0: port 0x64,0x60 irq 1 on acpi0 Nov 15 08:54:18 titan kernel: atkbd0: irq 1 on atkbdc0 Nov 15 08:54:18 titan kernel: kbd0 at atkbd0 Nov 15 08:54:18 titan kernel: atkbd0: [GIANT-LOCKED] Nov 15 08:54:18 titan kernel: psm0: irq 12 on atkbdc0 Nov 15 08:54:18 titan kernel: psm0: [GIANT-LOCKED] Nov 15 08:54:18 titan kernel: psm0: model IntelliMouse Explorer, device ID 4 Nov 15 08:54:18 titan kernel: orm0: at iomem 0xd0000-0xd17ff,0xc0000-0xccfff on isa0 Nov 15 08:54:18 titan kernel: sc0: at flags 0x100 on isa0 Nov 15 08:54:18 titan kernel: sc0: VGA <16 virtual consoles, flags=0x300> Nov 15 08:54:18 titan kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Nov 15 08:54:18 titan kernel: sio1: configured irq 3 not in bitmap of probed irqs 0 Nov 15 08:54:18 titan kernel: sio1: port may not be enabled Nov 15 08:54:18 titan kernel: Timecounter "TSC" frequency 997461023 Hz quality 800 Nov 15 08:54:18 titan kernel: Timecounters tick every 10.000 msec Nov 15 08:54:18 titan kernel: IPsec: Initialized Security Association Processing. Nov 15 08:54:18 titan kernel: ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited Nov 15 08:54:18 titan kernel: acpi_cpu: throttling enabled, 16 steps (100% to 6.2%), currently 100.0% Nov 15 08:54:18 titan kernel: ad0: 176700MB [359010/16/63] at ata0-master UDMA66 Nov 15 08:54:18 titan kernel: acd0: DVDROM at ata0-slave UDMA33 Nov 15 08:54:18 titan kernel: ad2: 176700MB [359010/16/63] at ata1-master UDMA66 Nov 15 08:54:18 titan kernel: acd1: DVDR at ata1-slave UDMA33 Nov 15 08:54:18 titan kernel: cd0 at ata0 bus 0 target 1 lun 0 Nov 15 08:54:18 titan kernel: cd0: Removable CD-ROM SCSI-0 device Nov 15 08:54:18 titan kernel: cd0: 33.000MB/s transfers Nov 15 08:54:18 titan kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Nov 15 08:54:18 titan kernel: cd1 at ata1 bus 0 target 1 lun 0 Nov 15 08:54:18 titan kernel: cd1: Removable CD-ROM SCSI-0 device Nov 15 08:54:18 titan kernel: cd1: 33.000MB/s transfers Nov 15 08:54:18 titan kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present Nov 15 08:54:18 titan kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Nov 15 08:54:18 titan kernel: da0: Removable Direct Access SCSI-2 device Nov 15 08:54:18 titan kernel: da0: 1.000MB/s transfers Nov 15 08:54:18 titan kernel: da0: Attempt to query device size failed: NOT READY, Medium not present Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): SCSI Status: Check Condition Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Medium not present Nov 15 08:54:18 titan kernel: (da0:umass-sim0:0:0:0): Unretryable error Nov 15 08:54:18 titan kernel: Opened disk da0 -> 6 Nov 15 08:54:18 titan kernel: Mounting root from ufs:/dev/ad2s1a Nov 15 08:54:18 titan kernel: WARNING: / was not properly dismounted Nov 15 08:54:18 titan kernel: WARNING: /home was not properly dismounted Nov 15 08:54:18 titan kernel: /home: mount pending error: blocks 8 files 1 Nov 15 08:54:18 titan kernel: /home: superblock summary recomputed Nov 15 08:54:18 titan kernel: WARNING: /usr was not properly dismounted Nov 15 08:54:18 titan kernel: /usr: mount pending error: blocks 100 files 48 Nov 15 08:54:18 titan kernel: /usr: superblock summary recomputed Nov 15 08:54:18 titan kernel: WARNING: /var was not properly dismounted Nov 15 08:54:18 titan kernel: /var: superblock summary recomputed Nov 15 08:54:18 titan savecore: no dumps found Nov 15 08:54:19 titan named[336]: starting BIND 9.3.0 -u bind -t /var/named Nov 15 08:54:19 titan named[336]: command channel listening on 127.0.0.1#953 Nov 15 08:54:28 titan rpcbind: cannot create socket for udp6 Nov 15 08:54:29 titan lpd[497]: lpd startup: logging=0 Nov 15 08:54:29 titan ntpd[509]: ntpd 4.2.0-a Wed Nov 10 11:31:07 CET 2004 (1) Nov 15 08:54:29 titan ntpd[509]: no IPv6 interfaces found Nov 15 08:54:45 titan kernel: WARNING: driver "vmmon" used unreserved major device number 200 Nov 15 08:54:45 titan kernel: vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 (3.2.x mvm) $ Nov 15 08:54:45 titan kernel: vmmon: Module vmmon: initialized Nov 15 08:54:46 titan postgres[1567]: [2-1] FATAL: the database system is starting up Nov 15 08:54:46 titan postgres[1581]: [2-1] FATAL: the database system is starting up Nov 15 08:54:46 titan postgres[1595]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1613]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1618]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1623]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1636]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1650]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1664]: [2-1] FATAL: the database system is starting up Nov 15 08:54:47 titan postgres[1680]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1694]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1699]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1715]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1716]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1733]: [2-1] FATAL: the database system is starting up Nov 15 08:54:48 titan postgres[1749]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1763]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1768]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1773]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1789]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1792]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1807]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1821]: [2-1] FATAL: the database system is starting up Nov 15 08:54:49 titan postgres[1836]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1851]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1865]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1874]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1883]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1898]: [2-1] FATAL: the database system is starting up Nov 15 08:54:50 titan postgres[1913]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1927]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1941]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1957]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1959]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1975]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[1989]: [2-1] FATAL: the database system is starting up Nov 15 08:54:51 titan postgres[2003]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2018]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2033]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2047]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2056]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2065]: [2-1] FATAL: the database system is starting up Nov 15 08:54:52 titan postgres[2081]: [2-1] FATAL: the database system is starting up Nov 15 08:54:53 titan postgres[2095]: [2-1] FATAL: the database system is starting up Nov 15 08:54:53 titan postgres[2109]: [2-1] FATAL: the database system is starting up Nov 15 08:54:53 titan postgres[2119]: [2-1] FATAL: the database system is starting up Nov 15 08:54:53 titan postgres[2125]: [2-1] FATAL: the database system is starting up Nov 15 08:54:53 titan postgres[2137]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2149]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2163]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2175]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2187]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2200]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2204]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2217]: [2-1] FATAL: the database system is starting up Nov 15 08:54:54 titan postgres[2229]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2241]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2253]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2267]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2279]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2290]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2295]: [2-1] FATAL: the database system is starting up Nov 15 08:54:55 titan postgres[2308]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2321]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2333]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2345]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2359]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2370]: [2-1] FATAL: the database system is starting up Nov 15 08:54:56 titan postgres[2375]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2388]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2403]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2417]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2431]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2443]: [2-1] FATAL: the database system is starting up Nov 15 08:54:57 titan postgres[2450]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2465]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2479]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2493]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2507]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2523]: [2-1] FATAL: the database system is starting up Nov 15 08:54:58 titan postgres[2528]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2541]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2555]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2569]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2584]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2599]: [2-1] FATAL: the database system is starting up Nov 15 08:54:59 titan postgres[2613]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2627]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2631]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2669]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2670]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2705]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2732]: [2-1] FATAL: the database system is starting up Nov 15 08:55:00 titan postgres[2736]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2762]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2767]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2787]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2792]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2816]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2817]: [2-1] FATAL: the database system is starting up Nov 15 08:55:01 titan postgres[2833]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2849]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2864]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2878]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2890]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2899]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2914]: [2-1] FATAL: the database system is starting up Nov 15 08:55:02 titan postgres[2928]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[2945]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[2960]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[2974]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[2986]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[2995]: [2-1] FATAL: the database system is starting up Nov 15 08:55:03 titan postgres[3010]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3024]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3038]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3054]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3071]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3072]: [2-1] FATAL: the database system is starting up Nov 15 08:55:04 titan postgres[3088]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3102]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3118]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3134]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3148]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3162]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3176]: [2-1] FATAL: the database system is starting up Nov 15 08:55:05 titan postgres[3180]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3196]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3212]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3226]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3240]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3255]: [2-1] FATAL: the database system is starting up Nov 15 08:55:06 titan postgres[3262]: [2-1] FATAL: the database system is starting up Nov 15 08:55:07 titan postgres[3276]: [2-1] FATAL: the database system is starting up Nov 15 08:55:07 titan postgres[3290]: [2-1] FATAL: the database system is starting up Nov 15 08:55:07 titan postgres[3305]: [2-1] FATAL: the database system is starting up Nov 15 08:55:07 titan postgres[3315]: [2-1] FATAL: the database system is starting up Nov 15 08:55:08 titan postgres[3326]: [2-1] FATAL: the database system is starting up Nov 15 08:55:08 titan postgres[3340]: [2-1] FATAL: the database system is starting up Nov 15 08:55:08 titan postgres[3358]: [2-1] FATAL: the database system is starting up Nov 15 08:55:08 titan postgres[3372]: [2-1] FATAL: the database system is starting up Nov 15 08:55:08 titan postgres[3386]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3393]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3408]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3422]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3436]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3452]: [2-1] FATAL: the database system is starting up Nov 15 08:55:09 titan postgres[3475]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3493]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3507]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3508]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3524]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3529]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3556]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3561]: [2-1] FATAL: the database system is starting up Nov 15 08:55:10 titan postgres[3579]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3591]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3613]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3621]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3635]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3649]: [2-1] FATAL: the database system is starting up Nov 15 08:55:11 titan postgres[3653]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3679]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3683]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3707]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3717]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3727]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3732]: [2-1] FATAL: the database system is starting up Nov 15 08:55:12 titan postgres[3751]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3763]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3780]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3791]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3815]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3819]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3834]: [2-1] FATAL: the database system is starting up Nov 15 08:55:13 titan postgres[3837]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3861]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3863]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3886]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3900]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3905]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3918]: [2-1] FATAL: the database system is starting up Nov 15 08:55:14 titan postgres[3932]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[3946]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[3960]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[3974]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[3979]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[3992]: [2-1] FATAL: the database system is starting up Nov 15 08:55:15 titan postgres[4006]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4020]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4034]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4048]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4062]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4077]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4080]: [2-1] FATAL: the database system is starting up Nov 15 08:55:16 titan postgres[4094]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4108]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4122]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4137]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4151]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4165]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4176]: [2-1] FATAL: the database system is starting up Nov 15 08:55:17 titan postgres[4183]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4197]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4211]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4225]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4240]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4255]: [2-1] FATAL: the database system is starting up Nov 15 08:55:18 titan postgres[4258]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4272]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4286]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4300]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4314]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4328]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4342]: [2-1] FATAL: the database system is starting up Nov 15 08:55:19 titan postgres[4345]: [2-1] FATAL: the database system is starting up Nov 15 08:55:20 titan postgres[4360]: [2-1] FATAL: the database system is starting up Nov 15 08:55:20 titan postgres[4374]: [2-1] FATAL: the database system is starting up Nov 15 08:55:20 titan postgres[4388]: [2-1] FATAL: the database system is starting up Nov 15 08:55:20 titan postgres[4402]: [2-1] FATAL: the database system is starting up Nov 15 08:55:20 titan postgres[4416]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4427]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4434]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4448]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4462]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4476]: [2-1] FATAL: the database system is starting up Nov 15 08:55:21 titan postgres[4490]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4504]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4507]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4522]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4535]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4553]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4557]: [2-1] FATAL: the database system is starting up Nov 15 08:55:22 titan postgres[4581]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4585]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4602]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4605]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4626]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4629]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4645]: [2-1] FATAL: the database system is starting up Nov 15 08:55:23 titan postgres[4658]: [2-1] FATAL: the database system is starting up Nov 15 08:55:24 titan postgres[4680]: [2-1] FATAL: the database system is starting up Nov 15 08:55:24 titan postgres[4694]: [2-1] FATAL: the database system is starting up Nov 15 08:55:24 titan postgres[4709]: [2-1] FATAL: the database system is starting up Nov 15 08:55:24 titan postgres[4710]: [2-1] FATAL: the database system is starting up Nov 15 08:55:24 titan postgres[4726]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4740]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4754]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4768]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4780]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4786]: [2-1] FATAL: the database system is starting up Nov 15 08:55:25 titan postgres[4800]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4814]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4828]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4842]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4856]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4867]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4874]: [2-1] FATAL: the database system is starting up Nov 15 08:55:26 titan postgres[4888]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4902]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4916]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4931]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4934]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4948]: [2-1] FATAL: the database system is starting up Nov 15 08:55:27 titan postgres[4962]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[4976]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[4990]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[5004]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[5018]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[5026]: [2-1] FATAL: the database system is starting up Nov 15 08:55:28 titan postgres[5036]: [2-1] FATAL: the database system is starting up Nov 15 08:55:29 titan postgres[5050]: [2-1] FATAL: the database system is starting up Nov 15 08:55:29 titan postgres[5064]: [2-1] FATAL: the database system is starting up Nov 15 08:55:29 titan postgres[5078]: [2-1] FATAL: the database system is starting up Nov 15 08:55:29 titan postgres[5093]: [2-1] FATAL: the database system is starting up Nov 15 08:55:29 titan postgres[5094]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5110]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5124]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5138]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5147]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5163]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5178]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5184]: [2-1] FATAL: the database system is starting up Nov 15 08:55:30 titan postgres[5196]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5197]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5217]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5227]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5247]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5253]: [2-1] FATAL: the database system is starting up Nov 15 08:55:31 titan postgres[5274]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5279]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5290]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5306]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5307]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5321]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5339]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5351]: [2-1] FATAL: the database system is starting up Nov 15 08:55:32 titan postgres[5365]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5373]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5391]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5401]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5405]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5428]: [2-1] FATAL: the database system is starting up Nov 15 08:55:33 titan postgres[5433]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5457]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5458]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5475]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5478]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5492]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5506]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5520]: [2-1] FATAL: the database system is starting up Nov 15 08:55:34 titan postgres[5534]: [2-1] FATAL: the database system is starting up Nov 15 08:55:35 titan postgres[5548]: [2-1] FATAL: the database system is starting up Nov 15 08:55:35 titan postgres[5553]: [2-1] FATAL: the database system is starting up Nov 15 08:55:35 titan postgres[5566]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5580]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5594]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5609]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5610]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5626]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5640]: [2-1] FATAL: the database system is starting up Nov 15 08:55:36 titan postgres[5654]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5668]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5682]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5696]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5707]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5714]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5728]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5742]: [2-1] FATAL: the database system is starting up Nov 15 08:55:37 titan postgres[5756]: [2-1] FATAL: the database system is starting up Nov 15 08:55:38 titan postgres[5770]: [2-1] FATAL: the database system is starting up Nov 15 08:55:39 titan postgres[5774]: [2-1] FATAL: the database system is starting up Nov 15 08:55:39 titan postgres[5779]: [2-1] FATAL: the database system is starting up Nov 15 08:55:39 titan postgres[5792]: [2-1] FATAL: the database system is starting up Nov 15 08:55:39 titan postgres[5806]: [2-1] FATAL: the database system is starting up Nov 15 08:55:39 titan postgres[5820]: [2-1] FATAL: the database system is starting up Nov 15 08:55:40 titan postgres[5834]: [2-1] FATAL: the database system is starting up Nov 15 08:55:40 titan postgres[5848]: [2-1] FATAL: the database system is starting up Nov 15 08:55:41 titan postgres[5861]: [2-1] FATAL: the database system is starting up Nov 15 08:55:41 titan postgres[5867]: [2-1] FATAL: the database system is starting up Nov 15 08:55:42 titan postgres[5872]: [2-1] FATAL: the database system is starting up Nov 15 08:55:42 titan postgres[5893]: [2-1] FATAL: the database system is starting up Nov 15 08:55:43 titan postgres[5899]: [2-1] FATAL: the database system is starting up Nov 15 08:55:43 titan postgres[5902]: [2-1] FATAL: the database system is starting up Nov 15 08:55:44 titan postgres[5906]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5943]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5944]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5967]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5969]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5968]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[5989]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[6011]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[6017]: [2-1] FATAL: the database system is starting up Nov 15 08:55:45 titan postgres[6023]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6052]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6055]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6069]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6092]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6105]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6106]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6109]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6133]: [2-1] FATAL: the database system is starting up Nov 15 08:55:46 titan postgres[6144]: [2-1] FATAL: the database system is starting up Nov 15 08:57:43 titan ntpd[509]: kernel time sync disabled 2041 Nov 15 08:58:49 titan ntpd[509]: kernel time sync enabled 2001 Nov 15 09:10:14 titan fsck: /dev/ad2s1f: INCORRECT BLOCK COUNT I=2001921 (20832 should be 20864) (CORRECTED) Nov 15 09:10:14 titan fsck: /dev/ad2s1f: UNREF FILE I=2001921 OWNER=root MODE=100440 Nov 15 09:10:14 titan fsck: /dev/ad2s1f: SIZE=17179869944 MTIME=Nov 15 04:57 2004 (CLEARED) Nov 15 09:10:14 titan fsck: /dev/ad2s1f: Reclaimed: 0 directories, 1 files, 0 fragments Nov 15 09:10:14 titan fsck: /dev/ad2s1f: 108049 files, 5416049 used, 2706118 free (31662 frags, 334307 blocks, 0.4% fragmentation) Nov 15 09:11:49 titan postgres[7761]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:50 titan postgres[7761]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [14-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [15-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [16-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [17-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [18-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [19-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [20-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [21-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:11:51 titan postgres[7761]: [22-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:12:47 titan postgres[7826]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:12:47 titan postgres[7826]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:12:47 titan postgres[7826]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:12:47 titan postgres[7826]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:12:47 titan postgres[7826]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:07 titan postgres[8060]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:07 titan postgres[8060]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:07 titan postgres[8060]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [14-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [15-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:08 titan postgres[8060]: [16-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [17-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [18-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [19-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [20-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [21-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [22-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [23-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [24-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [25-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [26-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [27-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [28-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [29-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [30-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [31-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:09 titan postgres[8060]: [32-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:10 titan postgres[8060]: [33-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:16:10 titan postgres[8060]: [34-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [2-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [3-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [4-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [5-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [6-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [7-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [8-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [9-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [10-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:24 titan postgres[8187]: [11-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [12-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [13-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [14-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [15-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [16-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [17-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [18-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:25 titan postgres[8187]: [19-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [20-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [21-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [22-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [23-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [24-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:18:26 titan postgres[8187]: [25-1] ERROR: duplicate key violates unique constraint "dspam_token_data_token_key" Nov 15 09:20:03 titan sendmail[8287]: iAF8F9Uu007983: Truncated MIME Content-Type header due to field size (length = 144) (possible attack) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26387 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=168 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26392 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=169 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26393 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=168 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=26396 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=177 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=989284 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=170 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: UNREF FILE I=989285 OWNER=root MODE=100644 Nov 15 09:34:02 titan fsck: /dev/ad2s1e: SIZE=172 MTIME=Nov 12 04:42 2004 (CLEARED) Nov 15 09:34:02 titan fsck: /dev/ad2s1e: Reclaimed: 11 directories, 22 files, 16 fragments Nov 15 09:34:02 titan fsck: /dev/ad2s1e: 338362 files, 1393331 used, 2667716 free (69044 frags, 324834 blocks, 1.7% fragmentation) Nov 15 09:35:58 titan fsck: /dev/ad2s1d: UNREF FILE I=188572 OWNER=root MODE=140666 Nov 15 09:35:58 titan fsck: /dev/ad2s1d: SIZE=0 MTIME=Nov 15 00:19 2004 (CLEARED) Nov 15 09:35:58 titan fsck: /dev/ad2s1d: Reclaimed: 0 directories, 2 files, 11 fragments Nov 15 09:35:58 titan fsck: /dev/ad2s1d: 50753 files, 1189501 used, 839519 free (32543 frags, 100872 blocks, 1.6% fragmentation) Nov 15 10:03:53 titan su: andreas to root on /dev/ttyp0 -- Andreas Klemm - Powered by FreeBSD 5.1-CURRENT Need a magic printfilter today ? -> http://www.apsfilter.org/ From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 09:26:22 2004 Return-Path: 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 33E5616A4CE for ; Mon, 15 Nov 2004 09:26:22 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id B854C43D1D for ; Mon, 15 Nov 2004 09:26:21 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id iAF9PZLc002009; Mon, 15 Nov 2004 01:25:36 -0800 From: Kent Stewart To: Jiawei Ye Date: Mon, 15 Nov 2004 01:26:20 -0800 User-Agent: KMail/1.7.1 References: <200411150040.45281.kstewart@owt.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411150126.20446.kstewart@owt.com> cc: freebsd-current@freebsd.org Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 09:26:22 -0000 On Monday 15 November 2004 12:53 am, Jiawei Ye wrote: > On Mon, 15 Nov 2004 00:40:45 -0800, Kent Stewart wrote: > > On Sunday 14 November 2004 11:12 pm, Jiawei Ye wrote: > > > In -current, the base for cvsup has been changed to /var/db per > > > share/example/cvsup/ports-supfile. But setting "ports/INDEX*" in > > > /var/db/sup/refuse does not work as advertised. cvsup still nukes my > > > INDEX-5 when doing 'make update' in $PORTS_DIR. > > > > > > Any ideas? > > > > It won't download a new one. It just deletes the old one. It goes along > > with removing INDEX[-5] from cvs. > > > > Kent > > Then we really need to update our cvsup man page: > " The patterns are separated by whitespace, and multiple patterns are > permitted on each line. Files and directories matching the patterns > are neither updated nor deleted; they are simply ignored." > > The advertised behaviour is different from what actually happened. I agree. I don't know the mechanism but when the moved INDEX to attic, things happen and the delete on our end is one of the symptoms. I think the refuse just stopped it from downloading a new version but the delete is being handled differently. It really messed up my backup script because I keep the last 4 old versions of INDEX[-5] and it was deleting them before I bzip2'ed them. Other than being slightly annoying, it didn't matter to me because I always generate a new INDEX everytime I cvsup ports-all. I have downloaded Seaman's FreeBSB-Portindex and use it to do a fast generate of INDEX. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 09:38:42 2004 Return-Path: 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 3AFC316A4CE for ; Mon, 15 Nov 2004 09:38:42 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7050B43D54 for ; Mon, 15 Nov 2004 09:38:41 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iAF9cavj078101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 15 Nov 2004 12:38:37 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iAF9cW7j092989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2004 12:38:35 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iAF9cSSp092988; Mon, 15 Nov 2004 12:38:29 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Mon, 15 Nov 2004 12:38:26 +0300 From: Gleb Smirnoff To: Julian Elischer Message-ID: <20041115093826.GA92911@cell.sick.ru> References: <4197DB02.8050601@elischer.org> <419865B9.8010205@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <419865B9.8010205@elischer.org> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 09:38:42 -0000 On Mon, Nov 15, 2004 at 12:15:53AM -0800, Julian Elischer wrote: J> Going back to 5.3RELEASE fixes it.. J> I have no clue as to the problem.. the system freezes absolutly J> from yesterday's RELENG_5 or doesn't fail. No debugger, no dump etc.. You need to do a binary search. A boring, but effective procedure :( -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 11:29:48 2004 Return-Path: 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 900A716A4CE; Mon, 15 Nov 2004 11:29:48 +0000 (GMT) Received: from mailout09.sul.t-online.com (mailout09.sul.t-online.com [194.25.134.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id E06BA43D1F; Mon, 15 Nov 2004 11:29:47 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd06.aul.t-online.de by mailout09.sul.t-online.com with smtp id 1CTf3K-0006uR-03; Mon, 15 Nov 2004 12:29:46 +0100 Received: from Andro-Beta.Leidinger.net (JJrXxZZLZeskW3WCXaoqQn7x5ChCTSLbtqz5sRGhZaktEw2hYhNCro@[84.128.192.148]) by fmrl06.sul.t-online.com with esmtp id 1CTf36-0sUQsK0; Mon, 15 Nov 2004 12:29:32 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iAFBTqfp067600; Mon, 15 Nov 2004 12:29:52 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iAFBTqAF067599; Mon, 15 Nov 2004 12:29:52 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Mon, 15 Nov 2004 12:29:51 +0100 Message-ID: <1100518191.4198932fc1dd4@netchild.homeip.net> Date: Mon, 15 Nov 2004 12:29:51 +0100 From: Alexander Leidinger To: Harti Brandt , knu@freebsd.org References: <6857.1100271323@critter.freebsd.dk> <20041112160137.X42945@beagle.kn.op.dlr.de> <1100274897.4194dcd1d67d6@netchild.homeip.net> <20041112171024.P42945@beagle.kn.op.dlr.de> <20041113092215.7a40f133@Magellan.Leidinger.net> <20041115091059.L51863@beagle.kn.op.dlr.de> In-Reply-To: <20041115091059.L51863@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: JJrXxZZLZeskW3WCXaoqQn7x5ChCTSLbtqz5sRGhZaktEw2hYhNCro@t-dialin.net X-TOI-MSGID: b4d4bf4f-b8dc-4fdd-99c2-c36f5ebf9cf3 cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: [TEST] make -j patch [take 2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 11:29:48 -0000 Zitat von Harti Brandt : [knu CCed because he should know how portupgrade operates :-)] > Unless you reset MAKEFLAGS along the call path to the portupgrade's make > they'll see the -j, because the top-level make will stuff the -j into > MAKEFLAGS and that is probably inherited through portupgrade. I don't know how ruby handles exec()ing of external programs, but unless it inherits the environment by default, portupgrade doesn't seems to inherit MAKEFLAGS ("grep MAKEFLAGS /usr/local/lib/ruby/site_ruby/1.8/* /usr/local/sbin/port*" shows no hits). So if portupgrade inherits MAKEFLAGS somehow, phk's patch shouldn't cause unexpected harm in this szenario, if portupgrade doesn't inherit MAKEFLAGS, his patch violates POLA in this case. Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 12:07:48 2004 Return-Path: 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 32B2E16A4CE for ; Mon, 15 Nov 2004 12:07:48 +0000 (GMT) Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EC6343D46 for ; Mon, 15 Nov 2004 12:07:47 +0000 (GMT) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id iAFC7dXY098087 for ; Mon, 15 Nov 2004 13:07:40 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 15 Nov 2004 13:07:39 +0100 (CET) From: Martin Blapp To: current@freebsd.org Message-ID: <20041115125640.D53544@cvs.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Spam-Checksum: 7d648825f17a807ba33b4c6f169011cb X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0012 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="3.5572 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 192.168.0.2 Subject: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 12:07:48 -0000 Hi all, I'm experiencing on 6.X SMP still some deadlocks. The are not easy to trigger, but each time it happens after killing some PID's: This time it was named. I just did this 5 times: /etc/rc.d/named start (/etc/rc.d/named is broken and does not work) ps -auxwww | grep "sbin/named" | grep bind | awk '{ print $2 }' ¦ xargs kill and boom, it deadlocked and I was not able to get into DDB. Any ideas where the problem could be located ? I've also seen the same problems on 5.X. Martin Martin Blapp, ------------------------------------------------------------------ ImproWare AG, UNIXSP & ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 61 826 93 00 Fax: +41 61 826 93 01 PGP: PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E ------------------------------------------------------------------ From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 12:51:42 2004 Return-Path: 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 75A9216A4CE for ; Mon, 15 Nov 2004 12:51:42 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DFA943D2F for ; Mon, 15 Nov 2004 12:51:42 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAFCoIGs080543; Mon, 15 Nov 2004 07:50:18 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAFCoII6080540; Mon, 15 Nov 2004 12:50:18 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 15 Nov 2004 12:50:18 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Martin Blapp In-Reply-To: <20041115125640.D53544@cvs.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 12:51:42 -0000 On Mon, 15 Nov 2004, Martin Blapp wrote: > and boom, it deadlocked and I was not able to get into DDB. Are you able to get into DDB using a serial console? Not getting in via syscons is typically a sign that some thread holding Giant is spinning, or that Giant has been leaked. Alternatively, some other lock is leaked, and a thread with Giant waits on that lock. You may be able to get into DDB using the serial console as it doesn't require Giant (or you might not). But that would be a useful first step. Are you able to reproduce this problem with INVARIANTS and/or WITNESS compiled in, btw? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 12:53:13 2004 Return-Path: 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 EB0D016A4CE for ; Mon, 15 Nov 2004 12:53:13 +0000 (GMT) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F49F43D2D for ; Mon, 15 Nov 2004 12:53:12 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAFCr7Sj098575; Mon, 15 Nov 2004 07:53:07 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca ([127.0.0.1]) by localhost (avscan1.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 97903-09; Mon, 15 Nov 2004 07:53:07 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAFCr73S098511; Mon, 15 Nov 2004 07:53:07 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id iAFCqxgm047713; Mon, 15 Nov 2004 07:53:00 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.1.2.0.0.20041115075917.12684480@64.7.153.2> X-Sender: mdtpop@64.7.153.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Mon, 15 Nov 2004 08:00:07 -0500 To: "Wilkinson, Alex" , current@freebsd.org From: Mike Tancsa In-Reply-To: <20041112054741.GY40520@squash.dsto.defence.gov.au> References: <20041112054741.GY40520@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan1b Subject: Re: dealing with interupt storms ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 12:53:14 -0000 At 12:47 AM 12/11/2004, Wilkinson, Alex wrote: >Hi all, > >How does one stop an interrupt storm in RELENG_5 ? Is this an SMP machine ? What does dmesg show as well as pciconf -v ? ---Mike From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:04:03 2004 Return-Path: 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 7212D16A4CE; Mon, 15 Nov 2004 13:04:03 +0000 (GMT) Received: from n33.kp.t-systems-sfr.com (n33.kp.t-systems-sfr.com [129.247.16.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2B81D43D1D; Mon, 15 Nov 2004 13:04:02 +0000 (GMT) (envelope-from harti@freebsd.org) Received: from n81.sp.op.dlr.de (n81g.sp.op.dlr.de [129.247.163.1]) iAFD3nU371998; Mon, 15 Nov 2004 14:03:49 +0100 Received: from zeus.nt.op.dlr.de (zeus.nt.op.dlr.de [129.247.173.3]) iAFD3nI346870; Mon, 15 Nov 2004 14:03:49 +0100 Received: from beagle.kn.op.dlr.de (opkndnwsbsd178 [129.247.173.178]) by zeus.nt.op.dlr.de (8.11.7+Sun/8.9.1) with ESMTP id iAFD4Ou05744; Mon, 15 Nov 2004 14:04:24 +0100 (MET) Date: Mon, 15 Nov 2004 14:10:42 +0100 (CET) From: Harti Brandt X-X-Sender: brandt@beagle.kn.op.dlr.de To: Alexander Leidinger In-Reply-To: <1100518191.4198932fc1dd4@netchild.homeip.net> Message-ID: <20041115140821.A51863@beagle.kn.op.dlr.de> References: <6857.1100271323@critter.freebsd.dk> <20041112160137.X42945@beagle.kn.op.dlr.de> <20041112171024.P42945@beagle.kn.op.dlr.de> <20041115091059.L51863@beagle.kn.op.dlr.de> <1100518191.4198932fc1dd4@netchild.homeip.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: [TEST] make -j patch [take 2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Harti Brandt List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 13:04:03 -0000 On Mon, 15 Nov 2004, Alexander Leidinger wrote: AL>Zitat von Harti Brandt : AL> AL>[knu CCed because he should know how portupgrade operates :-)] AL> AL>> Unless you reset MAKEFLAGS along the call path to the portupgrade's make AL>> they'll see the -j, because the top-level make will stuff the -j into AL>> MAKEFLAGS and that is probably inherited through portupgrade. AL> AL>I don't know how ruby handles exec()ing of external programs, but unless AL>it inherits the environment by default, portupgrade doesn't seems to AL>inherit MAKEFLAGS ("grep MAKEFLAGS /usr/local/lib/ruby/site_ruby/1.8/* AL>/usr/local/sbin/port*" shows no hits). AL> AL>So if portupgrade inherits MAKEFLAGS somehow, phk's patch shouldn't AL>cause unexpected harm in this szenario, if portupgrade doesn't inherit AL>MAKEFLAGS, his patch violates POLA in this case. At least portinstall doesn't touch MAKEFLAGS: insert something like FOO!=echo -- ${MAKEFLAGS} >/tmp/A into a port's makefile and call portinstall for than port: MAKEFLAGS=-j2 portinstall ... Would be strange if portupgrade would be different from portinstall. So nothing is broken that wasn't already. harti From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:09:03 2004 Return-Path: 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 2B29B16A4CE for ; Mon, 15 Nov 2004 13:09:03 +0000 (GMT) Received: from post2.wesleyan.edu (post2.wesleyan.edu [129.133.6.128]) by mx1.FreeBSD.org (Postfix) with ESMTP id C82D843D2F for ; Mon, 15 Nov 2004 13:09:02 +0000 (GMT) (envelope-from vsavichev@wesleyan.edu) Received: from localhost.localdomain (pony4.wesleyan.edu [129.133.6.195]) by post2.wesleyan.edu (8.12.11/8.12.11) with ESMTP id iAFD90mA023064 for ; Mon, 15 Nov 2004 08:09:00 -0500 Received: from localhost.localdomain (pony4 [127.0.0.1]) iAFD90uj025082 for ; Mon, 15 Nov 2004 08:09:00 -0500 Received: (from apache@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id iAFD90jR025080; Mon, 15 Nov 2004 08:09:00 -0500 Received: from 81.30.200.207 (SquirrelMail authenticated user vsavichev); by webmail.wesleyan.edu with HTTP; Mon, 15 Nov 2004 08:09:00 -0500 (EST) Message-ID: <60598.81.30.200.207.1100524140.squirrel@81.30.200.207> Date: Mon, 15 Nov 2004 08:09:00 -0500 (EST) From: vsavichev@wesleyan.edu To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.3a-0.e3.1 X-Mailer: SquirrelMail/1.4.3a-0.e3.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Wesleyan-MailScanner-Information: Please contact the ISP for more information X-Wesleyan-MailScanner: Found to be clean X-MailScanner-From: vsavichev@wesleyan.edu Subject: 5.3.R fails to load kernel modules on startup X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:09:03 -0000 after fresh 5.3R booting up linprocfs fails to mount in fstab kldstat shows no add-on modules like linux.ko linprocfs.ko acpi.ko loaded. I have linux_enable="YES" in rc.conf, AFAIK acpi.ko should be loaded automatically but loader fails to find it. The same goes for ipfilter ipnat enabled in rc.conf. I can load everyth. manually, though. Everyth. worked fine on 5.2.1. Did I miss someth.? Vlad From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 08:40:55 2004 Return-Path: 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 424C916A4CE for ; Mon, 15 Nov 2004 08:40:55 +0000 (GMT) Received: from proxy1.ufanet.ru (proxy1.ufanet.ru [81.30.199.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8873043D1F for ; Mon, 15 Nov 2004 08:40:54 +0000 (GMT) (envelope-from cybermart@ufanet.ru) Received: from mail.ufanet.ru (mail.ufanet.ru [213.24.120.70]) by proxy1.ufanet.ru (Postfix) with ESMTP id BFB2E1D2F4D for ; Mon, 15 Nov 2004 13:40:53 +0500 (YEKT) Received: from www1.ufanet.ru (www1.ufanet.ru [81.30.199.65]) by mail.ufanet.ru (8.13.1/8.13.1) with ESMTP id iAF8emir000943 for ; Mon, 15 Nov 2004 13:40:51 +0500 (YEKT) (envelope-from cybermart@ufanet.ru) Message-ID: <29391588.1100508048805.JavaMail.root@www1.ufanet.ru> Date: Mon, 15 Nov 2004 13:40:48 +0500 (YEKT) From: cybermart@ufanet.ru To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Scanned-By: milter-spamc/0.13.216 (mail.ufanet.ru [213.24.120.70]); Mon, 15 Nov 2004 13:40:51 +0500 X-Spam-Flag: NO X-Spam-Status: NO, hits=0.30 required=5.00 X-Spam-Level: X-Mailman-Approved-At: Mon, 15 Nov 2004 13:10:13 +0000 Subject: FreeBSD 5.3R Fails to load kernel modules on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 08:40:55 -0000 just got fresh 5.3R. Boot process aborted while failing to mount linprocfs in fstab, kldstat shows no linux.ko linprocfs.ko loaded. It is enabled in rc.conf enable_linux="YES". Everything goes straight manually, though. So I see problem loading kernel modules on startup on 5.3R. It worked fine on 5.2.1. Same happened with ipfilter/ipnat. Did I miss something ? Vlad From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 09:42:59 2004 Return-Path: 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 57EC216A4CE for ; Mon, 15 Nov 2004 09:42:59 +0000 (GMT) Received: from volt.iem.pw.edu.pl (volt.iem.pw.edu.pl [194.29.146.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8759343D1F for ; Mon, 15 Nov 2004 09:42:58 +0000 (GMT) (envelope-from wielebap@volt.iem.pw.edu.pl) Received: from volt.iem.pw.edu.pl (wielebap@localhost [127.0.0.1]) by volt.iem.pw.edu.pl (8.13.1/8.13.1) with ESMTP id iAF9gt48022880 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Nov 2004 10:42:55 +0100 (CET) (envelope-from wielebap@volt.iem.pw.edu.pl) Received: (from wielebap@localhost) by volt.iem.pw.edu.pl (8.13.1/8.12.10/Submit) id iAF9gtDk022879; Mon, 15 Nov 2004 10:42:55 +0100 (CET) (envelope-from wielebap) Date: Mon, 15 Nov 2004 10:42:55 +0100 From: Pawel Wieleba To: freebsd-current@freebsd.org Message-ID: <20041115094255.GA19206@volt.iem.pw.edu.pl> References: <4196398D.2030000@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4196398D.2030000@fer.hr> User-Agent: Mutt/1.5.6i X-Mailman-Approved-At: Mon, 15 Nov 2004 13:10:13 +0000 cc: Ivan Voras Subject: Re: Passwd format? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 09:42:59 -0000 On Sat, Nov 13, 2004 at 05:42:53PM +0100, Ivan Voras wrote: > The Handbook and crypt(3) say passwords in master.passwd are MD5 hashes > if they start with $1$, for example: > > $1$DP.s8oCc$VJo0/026/S5ng6HlD1Sz8/ > > the format is $1$salt$rest. I have several questions: > > How are the values encoded? This looks something like base64. > > Is it possible to actually verify the password against this format using > only a bare implementation of the md5 algorithm? No. > > Actually, the reason for these questions is that I'm considering using > LDAP authentication on a machine with lots of users and I'm wondering if > existing passwd information could be transported to LDAP. Any > experiences/docs on this? Yes of course. I have migrated from /etc/master.passwd to LDAP. I've used MigrationTools and changed them to support FreeBSD /etc/master.passwd file. www.padl.com/download/MigrationTools.tgz A patch to migrate_common.ph is available from my web: www.iem.pw.edu.pl/~wielebap/ldap/migrationtools/migrate_common.ph.diff A have created a new migrate_masterpasswd.pl (changed migrate_passwd.pl) www.iem.pw.edu.pl/~wielebap/ldap/migrationtools/migrate_masterpasswd.pl You can also use pam_ldap to migrate password hash from one to another hash format: http://www.freebsd.org/cgi/query-pr.cgi?pr=71289 www.iem.pw.edu.pl/~wielebap/ldap/pam_ldap/pam_ldap_doc.pdf (section 1) It may be helpful to see PRs: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/73448 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/72867 Pawel Wieleba P.Wieleba@iem.pw.edu.pl From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 11:09:59 2004 Return-Path: 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 537EB16A4CE for ; Mon, 15 Nov 2004 11:09:59 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A64043D48 for ; Mon, 15 Nov 2004 11:09:58 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CTek9-0000qt-00 for ; Mon, 15 Nov 2004 12:09:57 +0100 Received: from 231.98.121.148.in-addr.arpa ([148.121.98.231]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Nov 2004 12:09:57 +0100 Received: from solskogen by 231.98.121.148.in-addr.arpa with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Nov 2004 12:09:57 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Christer Solskogen Date: Mon, 15 Nov 2004 12:09:53 +0100 Lines: 10 Message-ID: References: <200411150040.45281.kstewart@owt.com> <200411150126.20446.kstewart@owt.com> 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: 231.98.121.148.in-addr.arpa User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en In-Reply-To: <200411150126.20446.kstewart@owt.com> Sender: news X-Mailman-Approved-At: Mon, 15 Nov 2004 13:10:13 +0000 Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 11:09:59 -0000 Kent Stewart wrote: > Other than being slightly annoying, it didn't matter to me because I always > generate a new INDEX everytime I cvsup ports-all. I have downloaded Seaman's > FreeBSB-Portindex and use it to do a fast generate of INDEX. What is INDEX for these days? -- cso From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:21:46 2004 Return-Path: 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 3075F16A4CE; Mon, 15 Nov 2004 13:21:46 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4197D43D1F; Mon, 15 Nov 2004 13:21:45 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id D5B9780F7; Mon, 15 Nov 2004 14:21:43 +0100 (CET) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <4BF12A73-3709-11D9-B78A-000A95A9A574@nordahl.net> Content-Transfer-Encoding: quoted-printable From: Frode Nordahl Date: Mon, 15 Nov 2004 14:21:45 +0100 To: Robert Watson X-Mailer: Apple Mail (2.619) cc: freebsd-current@freebsd.org Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout - what does it mean? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:21:46 -0000 On Nov 10, 2004, at 11:34, Robert Watson wrote: > > On Wed, 10 Nov 2004, S=F8ren Schmidt wrote: > >>> I'm still a bit skeptical that the task queue is at fault -- I run = my >>> notebook with continuous measurement of the latency to schedule=20 >>> tasks, >>> generating a warning for any latency > .5 seconds, and the only time=20= >>> I >>> ever see that sort of latency is during the boot process when ACPI=20= >>> has >>> scheduled a task to run, but the task queue thread has not yet been >>> allowed to run: >> >> Right, the timeout is 5 secs. I havn't looked into how the taskqueues >> are handled recently, but in case of ATA read/writes it is the >> bio_taskqueue handled by geom thats in use not the catchall ones, = does >> your timing cover that as well? > > Nope -- I had assumed that the suggested task problems in question was=20= > the > use of taskqueue_enqueue() in ata-queue for the timeout, rather than=20= > the > bio_taskqueue() ata_completed() call. Do you have a patch that covers these as well? I have two systems not going production anytime soon, and I will be=20 more than happy to put these to work to help find this problem in the=20 mean time. I can make them panic at will, but I think the panics are useless for=20 finding the problem, since the panic probably occurs after errors made=20= to the filesystem because of this bug. Mvh, Frode Nordahl > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee=20 > Research > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to=20 > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:22:56 2004 Return-Path: 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 9ECC416A4CE; Mon, 15 Nov 2004 13:22:56 +0000 (GMT) Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 685EC43D1D; Mon, 15 Nov 2004 13:22:55 +0000 (GMT) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id iAFDMkXY010351; Mon, 15 Nov 2004 14:22:47 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 15 Nov 2004 14:22:46 +0100 (CET) From: Martin Blapp To: Robert Watson In-Reply-To: Message-ID: <20041115142036.D53544@cvs.imp.ch> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checksum: 5718ad17193357f5ffefbc32e69012c1 X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0012 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="3.5415 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 192.168.0.2 cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:22:56 -0000 Hi, > Are you able to get into DDB using a serial console? Not getting in via > syscons is typically a sign that some thread holding Giant is spinning, or > that Giant has been leaked. Alternatively, some other lock is leaked, and > a thread with Giant waits on that lock. You may be able to get into DDB > using the serial console as it doesn't require Giant (or you might not). I was not able to get into DDB over serial console. Sorry for not saying this exactly. Hardlock. But that would be a useful first step. Are you able to reproduce this > problem with INVARIANTS and/or WITNESS compiled in, btw? Since this is a production box I have no chance testing it out. The second and third box we have are now in production too. On different boxes I was not able to reproduce it. So this problem seems only to happen on high load situations. Martin From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:35:42 2004 Return-Path: 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 A6B0416A4CE; Mon, 15 Nov 2004 13:35:42 +0000 (GMT) Received: from mailout01.sul.t-online.com (mailout01.sul.t-online.com [194.25.134.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C0E43D5C; Mon, 15 Nov 2004 13:35:41 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from fwd03.aul.t-online.de by mailout01.sul.t-online.com with smtp id 1CTh1A-0007tw-00; Mon, 15 Nov 2004 14:35:40 +0100 Received: from Andro-Beta.Leidinger.net (SmFEtyZHYehAhRN6px6TgYUr05fhDH4yC+Jw1sGz1Nt+rb5I6AXBQ5@[84.128.192.148]) by fmrl03.sul.t-online.com with esmtp id 1CTh17-2Cfr840; Mon, 15 Nov 2004 14:35:37 +0100 Received: from Andro-Beta.Leidinger.net (localhost [127.0.0.1]) iAFDZvxa085553; Mon, 15 Nov 2004 14:35:57 +0100 (CET) (envelope-from Alexander@Leidinger.net) Received: (from www@localhost)iAFDZvOa085552; Mon, 15 Nov 2004 14:35:57 +0100 (CET) (envelope-from Alexander@Leidinger.net) X-Authentication-Warning: Andro-Beta.Leidinger.net: www set sender to Alexander@Leidinger.net using -f Received: from 141.113.101.32 ([141.113.101.32]) by netchild.homeip.net (IMP) with HTTP for ; Mon, 15 Nov 2004 14:35:56 +0100 Message-ID: <1100525756.4198b0bc994e4@netchild.homeip.net> Date: Mon, 15 Nov 2004 14:35:56 +0100 From: Alexander Leidinger To: Harti Brandt References: <6857.1100271323@critter.freebsd.dk> <20041112160137.X42945@beagle.kn.op.dlr.de> <1100274897.4194dcd1d67d6@netchild.homeip.net> <20041112171024.P42945@beagle.kn.op.dlr.de> <20041113092215.7a40f133@Magellan.Leidinger.net> <20041115091059.L51863@beagle.kn.op.dlr.de> <1100518191.4198932fc1dd4@netchild.homeip.net> <20041115140821.A51863@beagle.kn.op.dlr.de> In-Reply-To: <20041115140821.A51863@beagle.kn.op.dlr.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.6 / FreeBSD-4.10 X-Originating-IP: 141.113.101.32 X-ID: SmFEtyZHYehAhRN6px6TgYUr05fhDH4yC+Jw1sGz1Nt+rb5I6AXBQ5@t-dialin.net X-TOI-MSGID: 111fd41b-d565-4a16-9210-5b7b56af3249 cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: [TEST] make -j patch [take 2] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:35:42 -0000 Zitat von Harti Brandt : > AL>So if portupgrade inherits MAKEFLAGS somehow, phk's patch shouldn't > AL>cause unexpected harm in this szenario, if portupgrade doesn't inherit > AL>MAKEFLAGS, his patch violates POLA in this case. > > At least portinstall doesn't touch MAKEFLAGS: insert something like > FOO!=echo -- ${MAKEFLAGS} >/tmp/A > into a port's makefile and call portinstall for than port: > > MAKEFLAGS=-j2 portinstall ... I've tested it now in the scenario I had described in my previous mail. Yes, portupgrade inherits MAKEFLAGS. Bye, Alexander. -- http://www.Leidinger.net/ Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org/ netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:36:50 2004 Return-Path: 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 C307616A4CE for ; Mon, 15 Nov 2004 13:36:50 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4116E43D49 for ; Mon, 15 Nov 2004 13:36:50 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAFDZQEY081081; Mon, 15 Nov 2004 08:35:26 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAFDZQah081078; Mon, 15 Nov 2004 13:35:26 GMT (envelope-from robert@fledge.watson.org) Date: Mon, 15 Nov 2004 13:35:26 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Martin Blapp In-Reply-To: <20041115142036.D53544@cvs.imp.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:36:50 -0000 On Mon, 15 Nov 2004, Martin Blapp wrote: > > syscons is typically a sign that some thread holding Giant is spinning, or > > that Giant has been leaked. Alternatively, some other lock is leaked, and > > a thread with Giant waits on that lock. You may be able to get into DDB > > using the serial console as it doesn't require Giant (or you might not). > > I was not able to get into DDB over serial console. Sorry for not saying > this exactly. Hardlock. Any chance that any of the boxes has an NMI button? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 13:15:51 2004 Return-Path: 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 6372216A4CE for ; Mon, 15 Nov 2004 13:15:51 +0000 (GMT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id E347143D1D for ; Mon, 15 Nov 2004 13:15:50 +0000 (GMT) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.34) id 1CTgkM-00029v-8w for current@freebsd.org; Mon, 15 Nov 2004 19:18:18 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.13.1/8.13.1) with ESMTP id iAFDFogf002523 for ; Mon, 15 Nov 2004 19:15:50 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.13.1/8.13.1/Submit) id iAFC3tOq077898 for current@freebsd.org; Mon, 15 Nov 2004 18:03:55 +0600 (NOVT) (envelope-from danfe) Date: Mon, 15 Nov 2004 18:03:55 +0600 From: Alexey Dokuchaev To: current@freebsd.org Message-ID: <20041115120355.GA74977@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Mailman-Approved-At: Mon, 15 Nov 2004 13:41:28 +0000 Subject: 6-CURRENT, threads, hangs are still there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 13:15:51 -0000 Hello there, Updated world + kernel on Nov 12. Sticking to ULE + PREEMPTION + DEBUG STUFF in kernel. Running sim, psi, xmms, mozilla etc. hangs on startup, unless `libpthread' mapped to `libc_r' via /etc/libmap.conf. GDB is unable to attach, process is unkillable even with SIGKILL. Very reproducible. CPU: Intel 2.8GHz, HTT enabled. Does anyone have a clue on this? Using ULE on purpose to help hunt down its bugs. What debugging info can/should I get? Thanks. Dmesg et al. available on demand. ./danfe From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 14:05:37 2004 Return-Path: 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 D89F616A4E6; Mon, 15 Nov 2004 14:05:37 +0000 (GMT) Received: from mail.imp.ch (ns1.imp.ch [157.161.1.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3345843D31; Mon, 15 Nov 2004 14:05:37 +0000 (GMT) (envelope-from mb@imp.ch) Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by mail.imp.ch (8.12.9p2/8.12.3) with ESMTP id iAFE5TXY017816; Mon, 15 Nov 2004 15:05:30 +0100 (CET) (envelope-from Martin.Blapp@imp.ch) Date: Mon, 15 Nov 2004 15:05:29 +0100 (CET) From: Martin Blapp To: current@freebsd.org In-Reply-To: <20041115145739.B53544@cvs.imp.ch> Message-ID: <20041115150229.U53544@cvs.imp.ch> References: <20041115145739.B53544@cvs.imp.ch> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checksum: ab3a2afb9801f9b47bf2a82dccb2f73d X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0012 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="3.7275 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 192.168.0.2 Subject: vmware 3.x broken on FreeBSD 5.x / 6.x with IDE devices X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 14:05:38 -0000 Hi, Since FreeBSD 5.2.1 we get the following error: > Nov 15 14:54:39: VMX|OPROM: OpromPowerOff > Nov 15 14:54:39: VMX|AIOPowerOff ide0:0 It looks like ad0 gets disconnected by vmware. It is still not clear how this can happen. Of course this leads to a deadlock if ad0 is the root disk. rtc: 100 > kern.hz: Timing will be inaccurate, please increase hz. ad0: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=5724133 ad0: FAILURE - ATA_IDENTIFY timed out ad0: FAILURE - ATA_IDENTIFY timed out ad0: WARNING - removed from configuration ata0-master: FAILURE - WRITE_DMA timed out swap_pager: I/O error - pagein failed; blkno 2,size 4096, error 0 vm_fault: pager read error, pid 2882 (amd) vm_fault: pager read error, pid 2767 (vmware-mks) Nov 15 15:01:10 chohira kernel: pid 2882 (amd), uid 0: exited on signal 11 Nov 15 15:01:10 chohira amd[411]: Process 2882 exited with signal 11 Nov 15 15:01:10 chohira amd[411]: mount for /host/nbs got signal 11 initiate_write_filepage: already started Martin From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 14:58:39 2004 Return-Path: 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 E5C8716A4CE; Mon, 15 Nov 2004 14:58:39 +0000 (GMT) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 805AB43D3F; Mon, 15 Nov 2004 14:58:39 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.1/8.13.1) with ESMTP id iAFEwdsR051667; Mon, 15 Nov 2004 09:58:39 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.12.11/8.12.11) with ESMTP id iAFEwchW076419; Mon, 15 Nov 2004 09:58:38 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id AE5BA7306E; Mon, 15 Nov 2004 09:58:38 -0500 (EST) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20041115145838.AE5BA7306E@freebsd-current.sentex.ca> Date: Mon, 15 Nov 2004 09:58:38 -0500 (EST) X-Virus-Scanned: ClamAV 0.80/585/Thu Nov 11 07:22:42 2004 clamav-milter version 0.80j on avscan2 X-Virus-Status: Clean Subject: [current tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 14:58:40 -0000 TB --- 2004-11-15 13:15:12 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2004-11-15 13:15:12 - starting CURRENT tinderbox run for i386/i386 TB --- 2004-11-15 13:15:12 - checking out the source tree TB --- 2004-11-15 13:15:12 - cd /home/tinderbox/CURRENT/i386/i386 TB --- 2004-11-15 13:15:12 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2004-11-15 13:21:30 - building world (CFLAGS=-O2 -pipe) TB --- 2004-11-15 13:21:30 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-15 13:21:30 - /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 --- 2004-11-15 14:27:55 - building generic kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-15 14:27:55 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-15 14:27:55 - /usr/bin/make buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Mon Nov 15 14:27:56 UTC 2004 >>> 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 >>> Kernel build for GENERIC completed on Mon Nov 15 14:44:30 UTC 2004 TB --- 2004-11-15 14:44:30 - generating LINT kernel config TB --- 2004-11-15 14:44:30 - cd /home/tinderbox/CURRENT/i386/i386/src/sys/i386/conf TB --- 2004-11-15 14:44:30 - /usr/bin/make -B LINT TB --- 2004-11-15 14:44:30 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2004-11-15 14:44:30 - cd /home/tinderbox/CURRENT/i386/i386/src TB --- 2004-11-15 14:44:30 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Nov 15 14:44:30 UTC 2004 >>> 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 [...] ld -Bshareable -d -warn-common -o acpi_panasonic.ko acpi_panasonic.kld objcopy --strip-debug acpi_panasonic.ko ===> acpi/acpi_sony (all) cc -O2 -pipe -I/tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../contrib/dev/acpica -D_KERNEL -DKLD_MODULE -nostdinc -I- -I/tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../contrib/dev/acpica -include /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../dev/acpi_support/acpi_sony.c /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../dev/acpi_support/acpi_sony.c: In function `acpi_snc_detach': /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../dev/acpi_support/acpi_sony.c:133: error: `_Dbg' undeclared (first use in this function) /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../dev/acpi_support/acpi_sony.c:133: error: (Each undeclared identifier is reported only once /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony/../../../dev/acpi_support/acpi_sony.c:133: error: for each function it appears in.) *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi/acpi_sony. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules/acpi. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src/sys/modules. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/obj/tinderbox/CURRENT/i386/i386/src/sys/LINT. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. *** Error code 1 Stop in /tinderbox/CURRENT/i386/i386/src. TB --- 2004-11-15 14:58:38 - WARNING: /usr/bin/make returned exit code 1 TB --- 2004-11-15 14:58:38 - ERROR: failed to build lint kernel TB --- 2004-11-15 14:58:38 - tinderbox aborted From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 15:35:27 2004 Return-Path: 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 DB2C716A4CE for ; Mon, 15 Nov 2004 15:35:27 +0000 (GMT) Received: from smtp1.powertech.no (smtp1.powertech.no [195.159.0.145]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0460443D31 for ; Mon, 15 Nov 2004 15:35:27 +0000 (GMT) (envelope-from frode@nordahl.net) Received: from [195.159.6.24] (ws24.ns5.powertech.no [195.159.6.24]) by smtp1.powertech.no (Postfix) with ESMTP id D9A857E66 for ; Mon, 15 Nov 2004 16:35:25 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v619) Content-Transfer-Encoding: 7bit Message-Id: Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-current@freebsd.org From: Frode Nordahl Date: Mon, 15 Nov 2004 16:35:25 +0100 X-Mailer: Apple Mail (2.619) Subject: Reproducible panic in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 15:35:28 -0000 Hello, Whenver I do a 'make -j8 buildworld' I get this panic on todays -CURRENT. I dumped, newfsed and restored the /usr filesystem and got the exact same panic during restore, so it's not filesystem corruption from earlier crashes. This is a SMP system. ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=67200479 ad4: FAILURE - WRITE_DMA timed out g_vfs_done():ad4s1f[WRITE(offset=16958308352, length=16384)]error = 5 panic: initiate_write_inodeblock_ufs2: already started cpuid = 0 boot() called on cpu#0 Uptime: 18m7s telnet> send brk KDB: enter: Line break on console [thread 100128] Stopped at kdb_enter+0x2c: leave db> trace kdb_enter(c0844393,0,c5841c00,c5611800,c53f9490) at kdb_enter+0x2c siointr1(c5614740,c5453b80,ed6a4948,c07b96e9,c5611800) at siointr1+0x3be siointr(c5611800,c5841c00,4,c76c7114,c5841c00) at siointr+0x4f intr_execute_handlers(c53f9490,ed6a4964,4,ed6a49b4,c07b61f3) at intr_execute_handlers+0xad lapic_handle_intr(34) at lapic_handle_intr+0x23 Xapic_isr1() at Xapic_isr1+0x33 --- interrupt, eip = 0xc05ef7e2, esp = 0xed6a49a8, ebp = 0xed6a49b4 --- cv_wait(c76c7138,c76c7114,c76c7114,c5564800,ed6a49ec) at cv_wait+0x16 _sema_wait(c76c7114,0,0) at _sema_wait+0x3b ata_queue_request(c76c70cc,0,3d00,c5564800,0) at ata_queue_request+0x1a9 ata_controlcmd(c55648ac,e7,0,0,0,0) at ata_controlcmd+0x7a ata_shutdown(0,104,c54bd08c,c5453d0c,ed6a4a74) at ata_shutdown+0xa5 boot(104,c5841c00,c581b800,d9659ba8,200200a4) at boot+0x23e panic(c083e414,18d50000,c08e0000,c5841d50,0) at panic+0x174 softdep_disk_io_initiation(d9659ba8,d9659ba8,c5885d24,ed6a4c2c,c07561da) at softdep_disk_io_initiation+0x1081 softdep_disk_prewrite(d9659ba8,20020024,d9659ba8,ed6a4c48,c065f0bd) at softdep_disk_prewrite+0x64 ffs_geom_strategy(c5885d24,d9659ba8,4000,4,d9659ba8) at ffs_geom_strategy+0x2a bufwrite(d9659ba8,c5841c00,ed6a4c7c,c06099ce,100500) at bufwrite+0x1a9 vfs_bio_awrite(d9659ba8,64,0,c5885cf0,c5885d24) at vfs_bio_awrite+0x4b vop_stdfsync(ed6a4ce0,1f3,4198c550,1,0) at vop_stdfsync+0x231 sched_sync(0,ed6a4d48,0,c066a410,0) at sched_sync+0x397 fork_exit(c066a410,0,ed6a4d48) at fork_exit+0x58 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xed6a4d7c, ebp = 0 --- db> Mvh, Frode Nordahl From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 16:17:23 2004 Return-Path: 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 E88D916A4CE for ; Mon, 15 Nov 2004 16:17:23 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C2F343D3F for ; Mon, 15 Nov 2004 16:17:23 +0000 (GMT) (envelope-from kasparsk@gmail.com) Received: by rproxy.gmail.com with SMTP id b11so670577rne for ; Mon, 15 Nov 2004 08:17:23 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=dTNvdNHXBrotSTW06TTh1bUNOvEbt0Q3BhW/dDfdEsobDG0R5RX16zAzC924CR/KQs7fMQTyeUnGZFo29SzZwxcaPiFlx+iMGeZj2I1RqIENOP3J/GI4Mwy2mRoi/86digV+y//AU4IRMFeNSQ4p/zt8TZQsVHVn66mU0AcLr00= Received: by 10.38.86.38 with SMTP id j38mr621561rnb; Mon, 15 Nov 2004 08:17:22 -0800 (PST) Received: by 10.39.1.29 with HTTP; Mon, 15 Nov 2004 08:17:22 -0800 (PST) Message-ID: <92d8c1ed0411150817395e10d0@mail.gmail.com> Date: Mon, 15 Nov 2004 18:17:22 +0200 From: Kaspars To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Warning: Pentium 4 CPU: PSE disabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kaspars@os.lv List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 16:17:24 -0000 Hi all, I just installed new pc with FreeBSD 4.10 and updated to FreeBSD 4.10-RELEASE-p3 and found in dmesg: CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff Hyperthreading: 2 logical CPUs real memory = 520028160 (507840K bytes) avail memory = 502751232 (490968K bytes) Preloaded elf kernel "kernel" at 0xc0329000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Tryed to google, tryed in ircnet #freebsd but nobody can`t say what realy wrong :) thanks all, Casper From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 16:57:44 2004 Return-Path: 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 52C0C16A4CE; Mon, 15 Nov 2004 16:57:44 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FC6B43D45; Mon, 15 Nov 2004 16:57:44 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 0D3E12A8DD; Mon, 15 Nov 2004 08:57:44 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 8C4A8E2B3; Mon, 15 Nov 2004 08:57:43 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iAFGvhH5060176; Mon, 15 Nov 2004 08:57:43 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAFGvgtl060175; Mon, 15 Nov 2004 08:57:42 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Mon, 15 Nov 2004 08:57:42 -0800 User-Agent: KMail/1.7 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: <200411150857.42423.peter@wemm.org> cc: Martin Blapp cc: Robert Watson cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 16:57:44 -0000 On Monday 15 November 2004 05:35 am, Robert Watson wrote: > On Mon, 15 Nov 2004, Martin Blapp wrote: > > > syscons is typically a sign that some thread holding Giant is > > > spinning, or that Giant has been leaked. Alternatively, some > > > other lock is leaked, and a thread with Giant waits on that lock. > > > You may be able to get into DDB using the serial console as it > > > doesn't require Giant (or you might not). > > > > I was not able to get into DDB over serial console. Sorry for not > > saying this exactly. Hardlock. > > Any chance that any of the boxes has an NMI button? I had this problem too BTW, but it didn't prevent DDB. Once named or rndc got stuck, trying to kill them was Really Bad(TM). Both use libpthread. The programs were stuck in "runnable" state according to CTRL-T (siginfo). No, I haven't looked closer. That system was built about when the last round of libpthread turmoil was happening. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 16:57:44 2004 Return-Path: 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 52C0C16A4CE; Mon, 15 Nov 2004 16:57:44 +0000 (GMT) Received: from canning.wemm.org (canning.wemm.org [192.203.228.65]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FC6B43D45; Mon, 15 Nov 2004 16:57:44 +0000 (GMT) (envelope-from peter@wemm.org) Received: from fw.wemm.org (canning.wemm.org [192.203.228.65]) by canning.wemm.org (Postfix) with ESMTP id 0D3E12A8DD; Mon, 15 Nov 2004 08:57:44 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (overcee.wemm.org [10.0.0.3]) by fw.wemm.org (Postfix) with ESMTP id 8C4A8E2B3; Mon, 15 Nov 2004 08:57:43 -0800 (PST) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (localhost [127.0.0.1]) by overcee.wemm.org (8.13.1/8.13.1) with ESMTP id iAFGvhH5060176; Mon, 15 Nov 2004 08:57:43 -0800 (PST) (envelope-from peter@wemm.org) Received: from localhost (localhost [[UNIX: localhost]]) by overcee.wemm.org (8.13.1/8.13.1/Submit) id iAFGvgtl060175; Mon, 15 Nov 2004 08:57:42 -0800 (PST) (envelope-from peter@wemm.org) X-Authentication-Warning: overcee.wemm.org: peter set sender to peter@wemm.org using -f From: Peter Wemm To: freebsd-current@freebsd.org Date: Mon, 15 Nov 2004 08:57:42 -0800 User-Agent: KMail/1.7 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: <200411150857.42423.peter@wemm.org> cc: Martin Blapp cc: Robert Watson cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 16:57:44 -0000 On Monday 15 November 2004 05:35 am, Robert Watson wrote: > On Mon, 15 Nov 2004, Martin Blapp wrote: > > > syscons is typically a sign that some thread holding Giant is > > > spinning, or that Giant has been leaked. Alternatively, some > > > other lock is leaked, and a thread with Giant waits on that lock. > > > You may be able to get into DDB using the serial console as it > > > doesn't require Giant (or you might not). > > > > I was not able to get into DDB over serial console. Sorry for not > > saying this exactly. Hardlock. > > Any chance that any of the boxes has an NMI button? I had this problem too BTW, but it didn't prevent DDB. Once named or rndc got stuck, trying to kill them was Really Bad(TM). Both use libpthread. The programs were stuck in "runnable" state according to CTRL-T (siginfo). No, I haven't looked closer. That system was built about when the last round of libpthread turmoil was happening. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 17:03:58 2004 Return-Path: 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 3A0C816A4D0; Mon, 15 Nov 2004 17:03:58 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB1743D41; Mon, 15 Nov 2004 17:03:55 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id iAFH3hx2058287; Mon, 15 Nov 2004 18:03:44 +0100 (CET) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iAFH3eLi067374; Mon, 15 Nov 2004 18:03:41 +0100 (CET) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id iAFH3eJG067371; Mon, 15 Nov 2004 18:03:40 +0100 (CET) (envelope-from mb@imp.ch) X-Authentication-Warning: mx2.imp.ch: clamav set sender to using -f Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id iAFH3aXY045890; Mon, 15 Nov 2004 18:03:40 +0100 (CET) Date: Mon, 15 Nov 2004 18:03:36 +0100 (CET) From: Martin Blapp To: Peter Wemm In-Reply-To: <200411150857.42423.peter@wemm.org> Message-ID: <20041115180045.B53544@cvs.imp.ch> References: <200411150857.42423.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: 746e0eaaf5076b0e7c5f49d4b0befca1 X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0018 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="5.9418 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 157.161.9.18 cc: freebsd-current@freebsd.org cc: Robert Watson cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 17:03:58 -0000 Hi, > I had this problem too BTW, but it didn't prevent DDB. Once named or > rndc got stuck, trying to kill them was Really Bad(TM). Both use > libpthread. The programs were stuck in "runnable" state according to > CTRL-T (siginfo). > > No, I haven't looked closer. That system was built about when the last > round of libpthread turmoil was happening. Now if you say it. I had to kill named manually since it has lost his ARGV: Instead of bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 /usr/sbin/named -u bind -t /var/named I just had this at the time the box crashed: bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [/usr/sbin/named] or bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [named] after recovery from the crash, now everything is ok again. Martin From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 17:03:58 2004 Return-Path: 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 3A0C816A4D0; Mon, 15 Nov 2004 17:03:58 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB1743D41; Mon, 15 Nov 2004 17:03:55 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id iAFH3hx2058287; Mon, 15 Nov 2004 18:03:44 +0100 (CET) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iAFH3eLi067374; Mon, 15 Nov 2004 18:03:41 +0100 (CET) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id iAFH3eJG067371; Mon, 15 Nov 2004 18:03:40 +0100 (CET) (envelope-from mb@imp.ch) X-Authentication-Warning: mx2.imp.ch: clamav set sender to using -f Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id iAFH3aXY045890; Mon, 15 Nov 2004 18:03:40 +0100 (CET) Date: Mon, 15 Nov 2004 18:03:36 +0100 (CET) From: Martin Blapp To: Peter Wemm In-Reply-To: <200411150857.42423.peter@wemm.org> Message-ID: <20041115180045.B53544@cvs.imp.ch> References: <200411150857.42423.peter@wemm.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: 746e0eaaf5076b0e7c5f49d4b0befca1 X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0018 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="5.9418 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 157.161.9.18 cc: freebsd-current@freebsd.org cc: Robert Watson cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 17:03:58 -0000 Hi, > I had this problem too BTW, but it didn't prevent DDB. Once named or > rndc got stuck, trying to kill them was Really Bad(TM). Both use > libpthread. The programs were stuck in "runnable" state according to > CTRL-T (siginfo). > > No, I haven't looked closer. That system was built about when the last > round of libpthread turmoil was happening. Now if you say it. I had to kill named manually since it has lost his ARGV: Instead of bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 /usr/sbin/named -u bind -t /var/named I just had this at the time the box crashed: bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [/usr/sbin/named] or bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [named] after recovery from the crash, now everything is ok again. Martin From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 17:28:29 2004 Return-Path: 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 4679416A4CE; Mon, 15 Nov 2004 17:28:29 +0000 (GMT) Received: from ptcnat.era.pl (ptcnat.era.pl [213.158.197.100]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBA0143D46; Mon, 15 Nov 2004 17:28:28 +0000 (GMT) (envelope-from zaks@era.pl) Received: by localhost (Postfix, from userid 1001) id 3E28911445; Mon, 15 Nov 2004 18:28:26 +0100 (CET) From: =?iso-8859-2?Q?S=B3awek_=AFak?= To: net@freebsd.org, current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-Id: <20041115172826.3E28911445@localhost> Date: Mon, 15 Nov 2004 18:28:26 +0100 (CET) Subject: route add -host ... -iface issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 17:28:29 -0000 Hi, I'd like to ask why a static arp entry is added when direct route to host is added like this? route add -host target -iface interface The route(8) manpage says, that such route entry is for hosts directly reachable over interface. But when packets go out on this interface, the MAC address of target host in each packet is set to local MAC for the interface, which effectively stops the target host from receiving the packet. Another thing is the order of adding routes in /etc/rc.d/routing of FreeBSD 5.3. The default gateway is added *before* other static routes are setup. Sometimes the default router is unreachable before other static routes are set configured. Is there any reason to not change the line: static_routes="default ${static_routes}" to: static_routes="${static_routes} default" ? /S From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 17:54:47 2004 Return-Path: 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 BF8F316A4CE; Mon, 15 Nov 2004 17:54:47 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32E4943D45; Mon, 15 Nov 2004 17:54:47 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTl3s-000L9w-VH; Mon, 15 Nov 2004 20:54:45 +0300 From: Vladimir Grebenschikov To: =?iso-8859-2?Q?S=B3awek_=AFak?= In-Reply-To: <20041115172826.3E28911445@localhost> References: <20041115172826.3E28911445@localhost> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 15 Nov 2004 20:54:43 +0300 Message-Id: <1100541283.935.30.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "current@freebsd.org" cc: freebsd-net Subject: Re: route add -host ... -iface issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 17:54:47 -0000 =D0=92 =D0=BF=D0=BD, 15/11/2004 =D0=B2 18:28 +0100, S=C5=82awek =C5=BBak = =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Hi, >=20 > I'd like to ask why a static arp entry is added when direct route to = host is > added like this? >=20 > route add -host target -iface interface >=20 > The route(8) manpage says, that such route entry is for hosts directl= y > reachable over interface. But when packets go out on this interface, = the MAC > address of target host in each packet is set to local MAC for the int= erface, > which effectively stops the target host from receiving the packet. Actually you should instruct routing engine to do ARP lookup if you want to reach some IP address via ethrenet interface directly, like: route add a.b.c.0/24 -iface fxp0 -cloning or, for single host: route add a.b.c.d/32 -iface fxp0 -cloning /32 is important, it actually this enforces network route with netmask 255.255.255.255 to be added into routing table, from my practice, only network routes can be ARP-resolved. > Another thing is the order of adding routes in /etc/rc.d/routing of F= reeBSD > 5.3. The default gateway is added *before* other static routes are > setup. Sometimes the default router is unreachable before other stati= c > routes are set configured. Is there any reason to not change the line= : >=20 > static_routes=3D"default ${static_routes}" >=20 > to: >=20 > static_routes=3D"${static_routes} default" > ? Probably.=20 But looks like you want to install interface-specific routes,=20 I guess it is better to put anything interface-specific in ifconfig_[_alias*] or /etc/start_if. > /S =20 --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 18:08:52 2004 Return-Path: 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 990DF16A4CE; Mon, 15 Nov 2004 18:08:52 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4463243D4C; Mon, 15 Nov 2004 18:08:52 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTlHW-000LC7-Rd; Mon, 15 Nov 2004 21:08:50 +0300 From: Vladimir Grebenschikov To: =?iso-8859-2?Q?S=B3awek_=AFak?= In-Reply-To: <20041115172826.3E28911445@localhost> References: <20041115172826.3E28911445@localhost> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Mon, 15 Nov 2004 21:08:50 +0300 Message-Id: <1100542130.935.39.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "current@freebsd.org" cc: freebsd-net Subject: Re: route add -host ... -iface issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 18:08:52 -0000 =D0=92 =D0=BF=D0=BD, 15/11/2004 =D0=B2 18:28 +0100, S=C5=82awek =C5=BBak = =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Hi, >=20 > I'd like to ask why a static arp entry is added when direct route to = host is > added like this? >=20 > route add -host target -iface interface >=20 > The route(8) manpage says, that such route entry is for hosts directl= y > reachable over interface. But when packets go out on this interface, = the MAC > address of target host in each packet is set to local MAC for the int= erface, > which effectively stops the target host from receiving the packet. But anyway, I have question to our routing gurus, why we need install broken routes in case of ethernet interfaces ? Like: # route add 172.1.1.1 -iface fxp0 add host 172.1.1.1: gateway fxp0 # netstat -rn | fgrep 172 172.1.1.1 08:00:46:c8:45:b3 UHLS 0 0 fxp0 # ifconfig fxp0 ether fxp0: flags=3D8843 mtu 1500 options=3D8 ether 08:00:46:c8:45:b3 # Installed routing entry is definitely broken, and can't be used, probably /sbin/route should add cloning flag automatically when direct route added for some ethernet (and like) interface ? I guess it is common mistake. Also, everyone going to add route-entry via specific MAC address will be puzzled. I know it is possible, but just now I can't remember how, and route(8) does not show any light on this question.=20 > /S =20 --=20 Vladimir B. Grebenchikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 18:35:21 2004 Return-Path: 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 4A40C16A4CE for ; Mon, 15 Nov 2004 18:35:21 +0000 (GMT) Received: from smtp.owt.com (smtp.owt.com [204.118.6.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB20143D3F for ; Mon, 15 Nov 2004 18:35:20 +0000 (GMT) (envelope-from kstewart@owt.com) Received: from [207.41.94.233] (owt-207-41-94-233.owt.com [207.41.94.233]) by smtp.owt.com (8.12.8/8.12.8) with ESMTP id iAFIYKLc027880; Mon, 15 Nov 2004 10:34:21 -0800 From: Kent Stewart To: freebsd-current@freebsd.org Date: Mon, 15 Nov 2004 10:35:05 -0800 User-Agent: KMail/1.7.1 References: <200411150126.20446.kstewart@owt.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411151035.05819.kstewart@owt.com> cc: Christer Solskogen Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 18:35:21 -0000 On Monday 15 November 2004 03:09 am, Christer Solskogen wrote: > Kent Stewart wrote: > > Other than being slightly annoying, it didn't matter to me because I > > always generate a new INDEX everytime I cvsup ports-all. I have > > downloaded Seaman's FreeBSB-Portindex and use it to do a fast generate of > > INDEX. > > What is INDEX for these days? Some of portupgrades features depend on INDEX.db. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 19:45:06 2004 Return-Path: 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 22D8D16A4CE for ; Mon, 15 Nov 2004 19:45:06 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id E781F43D45 for ; Mon, 15 Nov 2004 19:45:05 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13636 invoked from network); 15 Nov 2004 19:45:05 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 19:45:05 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFJj0s5076045; Mon, 15 Nov 2004 14:45:01 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 14:04:37 -0500 User-Agent: KMail/1.6.2 References: <20041111212920.30198.qmail@web54609.mail.yahoo.com> <4193E183.3000406@error404.nls.net> In-Reply-To: <4193E183.3000406@error404.nls.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151404.37030.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: "Ketrien I. Saihr-Kesenchedra" cc: Nik Azim Azam cc: Stephan Uphoff Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:45:06 -0000 On Thursday 11 November 2004 05:02 pm, Ketrien I. Saihr-Kesenchedra wrote: > Nik Azim Azam wrote: > >--- Stephan Uphoff wrote: > >> OK - now we have to play the thousand questions game > >> > >>;-) > >> > >>This happens after the system is up? > >>Can you send me the startup messages (With verbose > >>enabled)? Are there known issues with other operating systems? > >>Do you have a serial console / serial line for gdb / firewire for > >> debugging ? > >> > >>If I read your first posting correctly you have 6 pentium II overdrive > >> processors in your system (overdrive = PII with PPRO pinout). > >>Can you supply information about the vendor / chipset of your system? > > We have a very big problem here though; we're detecting 7 processors. > The ALR has a LOT of on-board logic. Handling it is very tricky; these > things required a special version of Windows NT or SCO, as I recall. We > should only be detecting 6 CPUs; we may be erroneously accepting part of > the bridging logic as a processor. (ISTR that the CPU board bridge > appears very similar to a processor.) I think an mptable dump would be > very helpful here; I'm wondering if we're not letting the board fake us > out with bridge logic presenting as a processor. It's only finding 6 processors, but the local APIC IDs are 0, 1, 2, 4, 5, and 6. I'm guessing that the I/O APIC is using APIC ID 3. -- 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 15 19:45:13 2004 Return-Path: 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 EC8BA16A552 for ; Mon, 15 Nov 2004 19:45:12 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7308043D4C for ; Mon, 15 Nov 2004 19:45:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13762 invoked from network); 15 Nov 2004 19:45:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 19:45:11 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFJj0s6076045; Mon, 15 Nov 2004 14:45:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 14:24:49 -0500 User-Agent: KMail/1.6.2 References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> In-Reply-To: <20041111223705.GL582@hub.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151424.49790.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Alexander@Leidinger.net cc: Kris Kennaway cc: Joe Marcus Clarke cc: Robert Watson cc: current@FreeBSD.org Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:45:13 -0000 On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: > On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: > > Zitat von Joe Marcus Clarke : > > > I noticed the interrupt storm detection line in dmesg. In previous > > > builds, this worked, but it doesn't seem to be taking effect anymore. > > > > AFAIK the interrupt storm detection was removed (at least partially). > > s/removed/fixed so it doesn't give so many false positives/ > > (at least partially) ;-) > > Talk to jhb.. Please try this patch out and let me know if it does any better: --- //depot/vendor/freebsd/src/sys/kern/kern_intr.c 2004/11/05 19:15:40 +++ //depot/projects/smpng/sys/kern/kern_intr.c 2004/11/15 19:20:11 @@ -485,7 +485,7 @@ struct intrhand *ih; /* and our interrupt handler chain */ struct thread *td; struct proc *p; - int count, warned; + int count, warned, storming; td = curthread; p = td->td_proc; @@ -494,6 +494,7 @@ ("%s: ithread and proc linkage out of sync", __func__)); count = 0; warned = 0; + storming = 0; /* * As long as we have interrupts outstanding, go through the @@ -549,10 +550,26 @@ } /* - * If we detect an interrupt storm, pause with the - * source masked until the next hardclock tick. + * Interrupt storm handling: + * + * If this interrupt source is currently storming, + * then throttle it to only fire the handler once + * per clock tick. Each second we go out of storming + * mode to see if the storm has subsided. + * + * If this interrupt source is not currently + * storming, but the number of back to back + * interrupts exceeds the storm threshold, then + * enter storming mode. */ - if (intr_storm_threshold != 0 && + if (storming) { + tsleep(&count, td->td_priority, "istorm", 1); + if (count > hz) { + storming = 0; + count = 0; + } else + count++; + } else if (intr_storm_threshold != 0 && count >= intr_storm_threshold) { if (!warned) { printf( @@ -560,7 +577,7 @@ p->p_comm); warned = 1; } - tsleep(&count, td->td_priority, "istorm", 1); + storming = 1; count = 0; } else count++; @@ -580,6 +597,7 @@ if (!ithd->it_need) { TD_SET_IWAIT(td); count = 0; + storming = 0; CTR2(KTR_INTR, "%s: pid %d: done", __func__, p->p_pid); mi_switch(SW_VOL, NULL); CTR2(KTR_INTR, "%s: pid %d: resumed", __func__, p->p_pid); -- 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 15 19:45:13 2004 Return-Path: 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 145AF16A55C for ; Mon, 15 Nov 2004 19:45:13 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 713A043D1D for ; Mon, 15 Nov 2004 19:45:12 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13762 invoked from network); 15 Nov 2004 19:45:12 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 19:45:11 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFJj0s6076045; Mon, 15 Nov 2004 14:45:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 14:24:49 -0500 User-Agent: KMail/1.6.2 References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> In-Reply-To: <20041111223705.GL582@hub.freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151424.49790.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Alexander@Leidinger.net cc: Kris Kennaway cc: Joe Marcus Clarke cc: Robert Watson cc: current@FreeBSD.org Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:45:13 -0000 On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: > On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: > > Zitat von Joe Marcus Clarke : > > > I noticed the interrupt storm detection line in dmesg. In previous > > > builds, this worked, but it doesn't seem to be taking effect anymore. > > > > AFAIK the interrupt storm detection was removed (at least partially). > > s/removed/fixed so it doesn't give so many false positives/ > > (at least partially) ;-) > > Talk to jhb.. Please try this patch out and let me know if it does any better: --- //depot/vendor/freebsd/src/sys/kern/kern_intr.c 2004/11/05 19:15:40 +++ //depot/projects/smpng/sys/kern/kern_intr.c 2004/11/15 19:20:11 @@ -485,7 +485,7 @@ struct intrhand *ih; /* and our interrupt handler chain */ struct thread *td; struct proc *p; - int count, warned; + int count, warned, storming; td = curthread; p = td->td_proc; @@ -494,6 +494,7 @@ ("%s: ithread and proc linkage out of sync", __func__)); count = 0; warned = 0; + storming = 0; /* * As long as we have interrupts outstanding, go through the @@ -549,10 +550,26 @@ } /* - * If we detect an interrupt storm, pause with the - * source masked until the next hardclock tick. + * Interrupt storm handling: + * + * If this interrupt source is currently storming, + * then throttle it to only fire the handler once + * per clock tick. Each second we go out of storming + * mode to see if the storm has subsided. + * + * If this interrupt source is not currently + * storming, but the number of back to back + * interrupts exceeds the storm threshold, then + * enter storming mode. */ - if (intr_storm_threshold != 0 && + if (storming) { + tsleep(&count, td->td_priority, "istorm", 1); + if (count > hz) { + storming = 0; + count = 0; + } else + count++; + } else if (intr_storm_threshold != 0 && count >= intr_storm_threshold) { if (!warned) { printf( @@ -560,7 +577,7 @@ p->p_comm); warned = 1; } - tsleep(&count, td->td_priority, "istorm", 1); + storming = 1; count = 0; } else count++; @@ -580,6 +597,7 @@ if (!ithd->it_need) { TD_SET_IWAIT(td); count = 0; + storming = 0; CTR2(KTR_INTR, "%s: pid %d: done", __func__, p->p_pid); mi_switch(SW_VOL, NULL); CTR2(KTR_INTR, "%s: pid %d: resumed", __func__, p->p_pid); -- 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 15 19:45:21 2004 Return-Path: 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 0DEA516A585 for ; Mon, 15 Nov 2004 19:45:21 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id A645743D1F for ; Mon, 15 Nov 2004 19:45:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 23940 invoked from network); 15 Nov 2004 19:45:19 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 19:45:19 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFJj0s7076045; Mon, 15 Nov 2004 14:45:10 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 14:29:56 -0500 User-Agent: KMail/1.6.2 References: <200411091747.iA9Hl81Q075289@marlena.vvi.at> In-Reply-To: <200411091747.iA9Hl81Q075289@marlena.vvi.at> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151429.56336.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: ALeine Subject: Re: FreeBSD 5.3-RELEASE boot failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:45:21 -0000 On Tuesday 09 November 2004 12:47 pm, ALeine wrote: > I installed FreeBSD 5.3-RELEASE from the ISO CD image, but it won't > boot: > > F1 DOS > F2 Linux > F3 FreeBSD > > Default: F3 > > _ > int=00000006 err=00000000 efl=00000282 eip=000947cf > eax=000000c1 ebx=0000273b ecx=fe510821 edx=00000000 > esi=00000006 edi=00098db6 ebp=00090000 esp=00000000 > cs=002b ds=0033 es=0033 fs=0033 gs=0033 ss=0033 > cs:eip=f0 2b 92 00 00 00 00 bc-89 00 00 af f1 e6 f8 00 > 00 00 00 00 00 00 00 00-00 54 3d 00 00 00 00 00 > ss:esp=2b 00 00 01 1b f6 13 50-08 19 f6 f4 f7 f3 c3 f9 > 6f 91 6c 2c f8 ef 0d 6c-10 f2 7b 77 08 59 2e f9 > BTX halted > > This was with the HDD as ad0. I changed it to ad2 and used my > other drive with FreeBSD 4.10 as ad0 to see what was going on. > Here's the beef: Your BIOS is in lala land perhaps. Note that the stack pointer is 0, so it's hard to tell how it got into such a funk. I'm not sure how you can debug this, except perhaps to try turning off things like network cards as boot devices and turning off DMA mode in the BIOS for your hard drives. -- 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 15 19:45:21 2004 Return-Path: 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 AD8DA16A588 for ; Mon, 15 Nov 2004 19:45:21 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 451C943D46 for ; Mon, 15 Nov 2004 19:45:21 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 13980 invoked from network); 15 Nov 2004 19:45:21 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 19:45:20 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFJj0s8076045; Mon, 15 Nov 2004 14:45:17 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org, Anurekh Saxena Date: Mon, 15 Nov 2004 14:33:57 -0500 User-Agent: KMail/1.6.2 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151433.57236.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Robert Watson Subject: Re: kernel: return from interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:45:21 -0000 On Thursday 11 November 2004 10:59 pm, Anurekh Saxena wrote: > > > > Even normal "options PREEMPTION" should do this. I know from tracing > > > > the kernel in 6.x that that's the way the system behaves out of the > > > > box; with PREEMPTION turned on in 5.x you should see the same > > > > behavior. One thing I often do see, FWIW, is that if you're on an > > > > SMP box, the ithread will get scheduled to run immediately on another > > > > CPU that's idle, so you won't actually preempt the thread on the > > > > current CPU other than for the interrupt handler. What behavior are > > > > you seeing that suggests this isn't happening with PREEMPTION > > > > compiled in? > > > > > > I may be missing something fundamental here, but, doreti (exceptions.s) > > > does not call 'ast' for an interrupted task, that does not have RPL of > > > 3 (user). So, even if an interrupt is pending, and the 'NEEDRESCHED' > > > is set, the scheduling decision is delayed till the kernel thread or > > > whatever was running in the kernel sleeps, or give up the cpu(call > > > mi_switch), or returns to user mode. > > > > > > AFAIK this is the only return path from an interrupt. Unless there is > > > another return path for the interrupts, the scheduler is not invoked on > > > a return. > > > > Assuming we're talking about i386, lapic_handle_intr() will call > > intr_execute_handlers(), which will walk the list of handlers for the > > interrupt, and either directly invoke the fast handlers of the > > interrupts, or call ithread_schedule() to schedule the ithread. > > ithread_schedule() will invoke setrunqueue(), which enters the scheduler > > and is a preemption point. If you dig down a bit, you'll find a call to > > maybe_preempt(), which may preempt if appropriate, resulting in a call to > > mi_switch() to the ithread. The maybe_preempt() code will only kick in > > to actually switch if PREEMPTION is defined. > > Yeah, I got it wrong. Without the FULL_PREEMPTION enabled, it does not > preempt unless the current thread is in the idle priority band. > I was expecting the NEEDRESCHED flag to be used for preemption on > return paths, especially for interrupt context. I think this method > works better since preemption points become well defined in the > kernel. > Thanks for helping me figure this out. NEEDRESCHED (albeit rather broken at the moment) is used to implement preemptino of user threads. As Robert mentioned above, in-kernel preemption is managed via either direct switches in setrunqueue() or deferred preemptions via TDF_OWEPREEMPT in critical_exit(). -- 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 15 19:52:19 2004 Return-Path: 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 CCF4C16A4D0 for ; Mon, 15 Nov 2004 19:52:19 +0000 (GMT) Received: from chantry.devlix.dk (chantry.devlix.dk [195.41.43.228]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48ED443D1F for ; Mon, 15 Nov 2004 19:52:19 +0000 (GMT) (envelope-from spamtrap1@devlix.dk) Received: by chantry.devlix.dk (Postfix, from userid 1002) id AB7E8630A; Mon, 15 Nov 2004 20:52:23 +0100 (CET) Received: from localhost (localhost.devlix.dk [127.0.0.1]) by chantry.devlix.dk (Postfix) with ESMTP id 7183261FB; Mon, 15 Nov 2004 20:52:18 +0100 (CET) Received: from chantry.devlix.dk ([127.0.0.1]) by localhost (chantry.devlix.dk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11034-10; Mon, 15 Nov 2004 20:52:16 +0100 (CET) Received: from 192.168.1.175 (unknown [192.168.1.175]) by chantry.devlix.dk (Postfix) with ESMTP id DC70961F8; Mon, 15 Nov 2004 20:52:15 +0100 (CET) From: Jimmy Selgen To: Frode Nordahl In-Reply-To: References: Content-Type: text/plain Date: Mon, 15 Nov 2004 20:52:08 +0100 Message-Id: <1100548328.5241.2.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at devlix.dk X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on chantry.devlix.dk X-Spam-Level: X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=ham version=3.0.1 cc: freebsd-current@freebsd.org Subject: Re: Reproducible panic in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 19:52:20 -0000 On Mon, 2004-11-15 at 16:35 +0100, Frode Nordahl wrote: > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=67200479 > ad4: FAILURE - WRITE_DMA timed out > g_vfs_done():ad4s1f[WRITE(offset=16958308352, length=16384)]error = 5 > panic: initiate_write_inodeblock_ufs2: already started > cpuid = 0 > boot() called on cpu#0 > Uptime: 18m7s This looks an awful lot like the error i'm getting when waking one of my disks from powersave (bios hd spin down), although mine will just give me a "Bad file descriptor" and then wait with the panic until i reboot. Strange thing though is that it's only happening with my maxtor disk, not my WD1600 drive. Both spin down, but only the WD "survives". Perhaps the WD is just faster at spinning up so the timeout never occurs. /Jimmy From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 20:35:23 2004 Return-Path: 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 325E716A4ED; Mon, 15 Nov 2004 20:35:23 +0000 (GMT) Received: from rooster.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE6E43D31; Mon, 15 Nov 2004 20:35:22 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from [171.69.125.188] (dhcp-171-69-125-188.cisco.com [171.69.125.188]) by rooster.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id iAFKZLe13187; Mon, 15 Nov 2004 15:35:21 -0500 (EST) Message-ID: <41991309.2050000@FreeBSD.org> Date: Mon, 15 Nov 2004 15:35:21 -0500 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> <200411151424.49790.jhb@FreeBSD.org> In-Reply-To: <200411151424.49790.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Robert Watson cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 20:35:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: | |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |> |>>Zitat von Joe Marcus Clarke : |>> |>>>I noticed the interrupt storm detection line in dmesg. In previous |>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>> |>>AFAIK the interrupt storm detection was removed (at least partially). |> |>s/removed/fixed so it doesn't give so many false positives/ |> |>(at least partially) ;-) |> |>Talk to jhb.. | | | Please try this patch out and let me know if it does any better: Will do. I'm on the road now, but I'll apply this to the machine tonight, and test. If it doesn't come back up, I'll have to give you feedback when I get home on Saturday ;-). Joe - -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmRMJb2iPiv4Uz4cRAv9IAKCsH2as3FftNSZc+BkrjhTxAulorgCfQCNZ EX7uWJ0XfpZn1m4E4WHCRLY= =IMG/ -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 20:35:23 2004 Return-Path: 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 325E716A4ED; Mon, 15 Nov 2004 20:35:23 +0000 (GMT) Received: from rooster.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE6E43D31; Mon, 15 Nov 2004 20:35:22 +0000 (GMT) (envelope-from marcus@FreeBSD.org) Received: from [171.69.125.188] (dhcp-171-69-125-188.cisco.com [171.69.125.188]) by rooster.cisco.com (8.11.7+Sun/8.8.8) with ESMTP id iAFKZLe13187; Mon, 15 Nov 2004 15:35:21 -0500 (EST) Message-ID: <41991309.2050000@FreeBSD.org> Date: Mon, 15 Nov 2004 15:35:21 -0500 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> <200411151424.49790.jhb@FreeBSD.org> In-Reply-To: <200411151424.49790.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: Robert Watson cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 20:35:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: | |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |> |>>Zitat von Joe Marcus Clarke : |>> |>>>I noticed the interrupt storm detection line in dmesg. In previous |>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>> |>>AFAIK the interrupt storm detection was removed (at least partially). |> |>s/removed/fixed so it doesn't give so many false positives/ |> |>(at least partially) ;-) |> |>Talk to jhb.. | | | Please try this patch out and let me know if it does any better: Will do. I'm on the road now, but I'll apply this to the machine tonight, and test. If it doesn't come back up, I'll have to give you feedback when I get home on Saturday ;-). Joe - -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmRMJb2iPiv4Uz4cRAv9IAKCsH2as3FftNSZc+BkrjhTxAulorgCfQCNZ EX7uWJ0XfpZn1m4E4WHCRLY= =IMG/ -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 21:16:39 2004 Return-Path: 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 10F2416A4CE; Mon, 15 Nov 2004 21:16:39 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E3AF43D39; Mon, 15 Nov 2004 21:16:38 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id C7B6D240CE; Mon, 15 Nov 2004 22:16:37 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id C53A5240C9; Mon, 15 Nov 2004 22:16:36 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAFLGaLE001249; Mon, 15 Nov 2004 22:16:36 +0100 Received: (nullmailer pid 1981 invoked by uid 1001); Mon, 15 Nov 2004 21:16:36 -0000 Date: Mon, 15 Nov 2004 22:16:36 +0100 From: Mark Santcroos To: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Message-ID: <20041115211636.GA1540@laptop.6bone.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: U 0.223372 / -5.9 X-RIPE-Signature: fa78ef1f21f9d026bb08be89b6c62864 Subject: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:16:39 -0000 If the following patch doesn't burn down too many systems, it will be committed to HEAD in the near future. http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 21:18:52 2004 Return-Path: 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 41FCC16A4CE for ; Mon, 15 Nov 2004 21:18:52 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1887F43D1F for ; Mon, 15 Nov 2004 21:18:52 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 5000 invoked from network); 15 Nov 2004 21:18:51 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 21:18:51 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFLIlvu076672; Mon, 15 Nov 2004 16:18:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 15:46:15 -0500 User-Agent: KMail/1.6.2 References: <20041112123343.GA12048@peter.osted.lan> In-Reply-To: <20041112123343.GA12048@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151546.15533.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:18:52 -0000 On Friday 12 November 2004 07:33 am, Peter Holm wrote: > GENERIC HEAD from Nov 11 08:05 UTC > > The following stack traces etc. was done before my first > cup of coffee, so it's not so informative as it could have been :-( > > The test box appeared to have been frozen for more than 6 hours, > but was pingable. > > http://www.holm.cc/stress/log/cons86.html A weak guess is that you have the system in some sort of livelock due to fork()? Have you tried running with 'debug.mpsafevm=1' set from the loader? -- 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 15 21:18:55 2004 Return-Path: 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 40B7116A4CE for ; Mon, 15 Nov 2004 21:18:55 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEB5743D45 for ; Mon, 15 Nov 2004 21:18:54 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10245 invoked from network); 15 Nov 2004 21:18:54 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 21:18:54 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFLIlvv076672; Mon, 15 Nov 2004 16:18:50 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 16:06:45 -0500 User-Agent: KMail/1.6.2 References: <200411150857.42423.peter@wemm.org> <20041115180045.B53544@cvs.imp.ch> In-Reply-To: <20041115180045.B53544@cvs.imp.ch> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151606.45640.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Martin Blapp cc: Robert Watson cc: current@FreeBSD.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:18:55 -0000 On Monday 15 November 2004 12:03 pm, Martin Blapp wrote: > Hi, > > > I had this problem too BTW, but it didn't prevent DDB. Once named or > > rndc got stuck, trying to kill them was Really Bad(TM). Both use > > libpthread. The programs were stuck in "runnable" state according to > > CTRL-T (siginfo). > > > > No, I haven't looked closer. That system was built about when the last > > round of libpthread turmoil was happening. > > Now if you say it. I had to kill named manually since it has lost his > ARGV: > > Instead of > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 > /usr/sbin/named -u bind -t /var/named > > I just had this at the time the box crashed: > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 > [/usr/sbin/named] > > or > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [named] > > after recovery from the crash, now everything is ok again. Was the box swapping at the time? It could be that named was swapped out when you tried to kill it. -- 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 15 21:18:55 2004 Return-Path: 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 4462716A4D1 for ; Mon, 15 Nov 2004 21:18:55 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE56A43D3F for ; Mon, 15 Nov 2004 21:18:54 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10245 invoked from network); 15 Nov 2004 21:18:54 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 21:18:54 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFLIlvv076672; Mon, 15 Nov 2004 16:18:50 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Mon, 15 Nov 2004 16:06:45 -0500 User-Agent: KMail/1.6.2 References: <200411150857.42423.peter@wemm.org> <20041115180045.B53544@cvs.imp.ch> In-Reply-To: <20041115180045.B53544@cvs.imp.ch> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151606.45640.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Martin Blapp cc: Robert Watson cc: current@FreeBSD.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:18:55 -0000 On Monday 15 November 2004 12:03 pm, Martin Blapp wrote: > Hi, > > > I had this problem too BTW, but it didn't prevent DDB. Once named or > > rndc got stuck, trying to kill them was Really Bad(TM). Both use > > libpthread. The programs were stuck in "runnable" state according to > > CTRL-T (siginfo). > > > > No, I haven't looked closer. That system was built about when the last > > round of libpthread turmoil was happening. > > Now if you say it. I had to kill named manually since it has lost his > ARGV: > > Instead of > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 > /usr/sbin/named -u bind -t /var/named > > I just had this at the time the box crashed: > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 > [/usr/sbin/named] > > or > > bind 5068 0.0 1.4 30108 28440 ?? Ss 11:51AM 14:54.01 [named] > > after recovery from the crash, now everything is ok again. Was the box swapping at the time? It could be that named was swapped out when you tried to kill it. -- 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 15 21:18:57 2004 Return-Path: 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 8512116A4E9 for ; Mon, 15 Nov 2004 21:18:57 +0000 (GMT) Received: from mail4.speakeasy.net (mail4.speakeasy.net [216.254.0.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5845943D1D for ; Mon, 15 Nov 2004 21:18:57 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 10317 invoked from network); 15 Nov 2004 21:18:57 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 15 Nov 2004 21:18:56 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAFLIlvw076672; Mon, 15 Nov 2004 16:18:53 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org, kaspars@os.lv Date: Mon, 15 Nov 2004 16:14:21 -0500 User-Agent: KMail/1.6.2 References: <92d8c1ed0411150817395e10d0@mail.gmail.com> In-Reply-To: <92d8c1ed0411150817395e10d0@mail.gmail.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411151614.21983.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx Subject: Re: Warning: Pentium 4 CPU: PSE disabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:18:57 -0000 On Monday 15 November 2004 11:17 am, Kaspars wrote: > Hi all, > > I just installed new pc with FreeBSD 4.10 and updated to FreeBSD > 4.10-RELEASE-p3 and found in dmesg: > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 520028160 (507840K bytes) > avail memory = 502751232 (490968K bytes) > Preloaded elf kernel "kernel" at 0xc0329000. > Warning: Pentium 4 CPU: PSE disabled > Pentium Pro MTRR support enabled > md0: Malloc disk > > Tryed to google, tryed in ircnet #freebsd but nobody can`t say what > realy wrong :) There is a bug in how some of the Pentium4 chips handle PSE that 5.x works around already. However, the fix was too large to backport to 4.x, so instead the PSE feature is turned off in 4.x. I wouldn't worry about it, your machine will still work fine without PSE. -- 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 15 21:27:06 2004 Return-Path: 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 D264B16A4D0 for ; Mon, 15 Nov 2004 21:27:06 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 243C643D54 for ; Mon, 15 Nov 2004 21:27:06 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 19821 invoked by uid 89); 15 Nov 2004 21:27:02 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 15 Nov 2004 21:27:02 -0000 Received: (qmail 19693 invoked by uid 89); 15 Nov 2004 21:27:01 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 15 Nov 2004 21:27:01 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iAFLR05R001970; Mon, 15 Nov 2004 16:27:00 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: "i386@freebsd.org" , "current@freebsd.org" Content-Type: text/plain Message-Id: <1100554020.90130.241.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Mon, 15 Nov 2004 16:27:00 -0500 Content-Transfer-Encoding: 7bit Subject: patch for "Previous IPI is stuck" - please test X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 21:27:07 -0000 There have been several complains about "Previous IPI is stuck" panics on i386 based multiprocessor systems. In general all affected systems seem to have four or more real (no HTT) processors. Probable cause: The local APIC used for IPIs can only queue two interrupts per interrupt priority class (interrupt vector / 16). Since all IPIs share the same interrupt priority class more than two IPIs pending to the same processor will fill the interrupt fifo for the IPI priority class. I believe the "Previous IPI is stuck" is a deadlock between sending an AST IPI with sched lock held to a CPU trying to acquire the sched lock with interrupt disabled and with full interrupt fifo. Unfortunately I can not reproduce the problem on my dual Xeon with HTT enabled :-( To test the theory I wrote a patch that replaces multiple IPI interrupt handlers with a single hander and uses a bitmap to avoid redundant IPI interrupt requests to the interrupt fifo. The patch is a proof of concept and therefore not optimized (to put it mildly ;-). It probably increases the cost for TLB shootdown IPIs substantially. You can download the patch at: http://people.freebsd.org/~ups/ipi4_patch Please make sure that exception.o is rebuild. ( Makefile seems to miss the dependency to apic_vector.s) Any feedback is appreciated. Stephan From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:01:54 2004 Return-Path: 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 7D17716A4CE for ; Mon, 15 Nov 2004 22:01:54 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 469FC43D2F for ; Mon, 15 Nov 2004 22:01:54 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D8C5DF206F for ; Mon, 15 Nov 2004 14:01:51 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02647-01 for ; Mon, 15 Nov 2004 14:01:48 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 7FA8AF1BC2 for ; Mon, 15 Nov 2004 14:01:48 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-LC5DWwo714BFrJeTkUbV" Date: Mon, 15 Nov 2004 14:01:48 -0800 Message-Id: <1100556108.3025.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: natd panics are back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:01:54 -0000 --=-LC5DWwo714BFrJeTkUbV Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This was fixed a while ago and now it has made its way back into current: server# uname -a FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #58: Mon Nov 15 0= 8:40:01 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd= 64 Nov 15 13:56:16 server kernel: Fatal trap 12: page fault while in kernel mo= de Nov 15 13:56:16 server kernel: fault virtual address =3D 0x18 Nov 15 13:56:16 server kernel: fault code =3D supervisor read= , page not present Nov 15 13:56:16 server kernel: instruction pointer =3D 0x8:0xffffffff8= 0354810Nov 15 13:56:16 server kernel: stack pointer =3D 0x10:0xf= fffffffb1c71620 Nov 15 13:56:16 server kernel: frame pointer =3D 0x10:0xffffffff= b1c71680 Nov 15 13:56:16 server kernel: code segment =3D base 0x0, limit= 0xfffff, type 0x1b Nov 15 13:56:16 server kernel: =3D DPL 0, pres 1, long 1, def32 0, gran 1 Nov 15 13:56:16 server kernel: processor eflags =3D interrupt enabled, resu= me, IOPL =3D 0 Nov 15 13:56:16 server kernel: current process =3D 212 (natd) Nov 15 13:56:16 server kernel: trap number =3D 12 Nov 15 13:56:16 server kernel: panic: page fault Nov 15 13:56:16 server kernel: KDB: enter: panic (gdb) l *0xffffffff80354810 0xffffffff80354810 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). 368 MBUF_CHECKSLEEP(wait); 369 if (off =3D=3D 0 && m->m_flags & M_PKTHDR) 370 copyhdr =3D 1; 371 while (off > 0) { 372 KASSERT(m !=3D NULL, ("m_copym, offset > size of mb= uf chain")); 373 if (off < m->m_len) 374 break; 375 off -=3D m->m_len; 376 m =3D m->m_next; 377 } --=-LC5DWwo714BFrJeTkUbV Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmSdLyQsGN30uGE4RAkDDAKDDy4qGunNNQ9JXE68fTxa7rGNdFgCg0VVY tyYrZMZ2lqvxGEk4F/GFauM= =bkF/ -----END PGP SIGNATURE----- --=-LC5DWwo714BFrJeTkUbV-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:02:58 2004 Return-Path: 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 E728616A4CE; Mon, 15 Nov 2004 22:02:58 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F9FB43D31; Mon, 15 Nov 2004 22:02:58 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAFM1v0c023965; Mon, 15 Nov 2004 15:01:58 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 15:02:15 -0700 (MST) Message-Id: <20041115.150215.05160797.imp@bsdimp.com> To: marks@ripe.net From: "M. Warner Losh" In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:02:59 -0000 What are the big features of ACPI since the last import? Warner From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:05:57 2004 Return-Path: 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 21DB516A4CE; Mon, 15 Nov 2004 22:05:57 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id ABCDE43D1F; Mon, 15 Nov 2004 22:05:56 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 183EB241DF; Mon, 15 Nov 2004 23:05:56 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 25F2F241DE; Mon, 15 Nov 2004 23:05:54 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAFM5sLE014458; Mon, 15 Nov 2004 23:05:54 +0100 Received: (nullmailer pid 2922 invoked by uid 1001); Mon, 15 Nov 2004 22:05:53 -0000 Date: Mon, 15 Nov 2004 23:05:53 +0100 From: Mark Santcroos To: "M. Warner Losh" Message-ID: <20041115220553.GB731@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <20041115.150215.05160797.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041115.150215.05160797.imp@bsdimp.com> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Status: N 0.001077 / -5.9 X-RIPE-Signature: 84debc40111f8d37fe7b10eff2b08494 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:05:57 -0000 On Mon, Nov 15, 2004 at 03:02:15PM -0700, M. Warner Losh wrote: > What are the big features of ACPI since the last import? See the diff of CHANGES.txt included in the patchset. Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:14:04 2004 Return-Path: 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 5427316A4CE for ; Mon, 15 Nov 2004 22:14:04 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADDB743D41 for ; Mon, 15 Nov 2004 22:14:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAFME3p6030118 for ; Mon, 15 Nov 2004 23:14:03 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 15 Nov 2004 22:11:09 GMT." <200411152211.iAFMB9YF016201@repoman.freebsd.org> Date: Mon, 15 Nov 2004 23:14:03 +0100 Message-ID: <30117.1100556843@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [HEADSUP] vnode bypass for devices: "ON" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:14:04 -0000 Vnode bypass is now ON by default in -current. Please report any problems and performance observations. Please also try setting "vfs.fifofs.fops=1" if you run a machine which uses fifos for anything. Poul-Henning In message <200411152211.iAFMB9YF016201@repoman.freebsd.org>, Poul-Henning Kamp writes: >phk 2004-11-15 22:11:09 UTC > > FreeBSD src repository > > Modified files: > sys/fs/devfs devfs_vnops.c > Log: > Make vnode bypass the default for devices. > > Can be disabled in case of problems with > vfs.devfs.fops=0 > in loader.conf > > Revision Changes Path > 1.85 +1 -1 src/sys/fs/devfs/devfs_vnops.c > -- 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 15 22:28:17 2004 Return-Path: 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 51E6916A4CE for ; Mon, 15 Nov 2004 22:28:17 +0000 (GMT) Received: from ms-dienst.rz.rwth-aachen.de (ms-1.rz.RWTH-Aachen.DE [134.130.3.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAF8843D31 for ; Mon, 15 Nov 2004 22:28:16 +0000 (GMT) (envelope-from chris@unixpages.org) Received: from r220-1 (r220-1.rz.RWTH-Aachen.DE [134.130.3.31]) by ms-dienst.rz.rwth-aachen.de (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0I78002V4RO1VO@ms-dienst.rz.rwth-aachen.de> for current@freebsd.org; Mon, 15 Nov 2004 23:26:26 +0100 (MET) Received: from relay.rwth-aachen.de ([134.130.3.1]) by r220-1 (MailMonitor for SMTP v1.2.2 ) ; Mon, 15 Nov 2004 23:26:25 +0100 (MET) Received: from haakonia.hitnet.rwth-aachen.de (haakonia.hitnet.RWTH-Aachen.DE [137.226.181.92])iAFMQOJ9011736; Mon, 15 Nov 2004 23:26:24 +0100 (MET) Received: from gondor.middleearth (gondor.middleearth [192.168.1.42]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))(Postfix) with ESMTP id 4B91628449; Mon, 15 Nov 2004 23:26:19 +0100 (CET) Received: by gondor.middleearth (Postfix, from userid 1001) id BEBD02281E; Mon, 15 Nov 2004 23:26:18 +0100 (CET) Date: Mon, 15 Nov 2004 23:26:18 +0100 From: Christian Brueffer In-reply-to: <38677.1100390114@critter.freebsd.dk> To: Poul-Henning Kamp Message-id: <20041115222618.GB579@unixpages.org> MIME-version: 1.0 Content-type: multipart/signed; boundary="kXdP64Ggrk/fb43R"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-disposition: inline User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.0-CURRENT X-PGP-Key: http://people.freebsd.org/~brueffer/brueffer.key.asc X-PGP-Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D References: <38677.1100390114@critter.freebsd.dk> cc: current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:28:17 -0000 --kXdP64Ggrk/fb43R Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Nov 14, 2004 at 12:55:14AM +0100, Poul-Henning Kamp wrote: >=20 > I have uploaded a snapshot patch of my p4 phk_bufwork branch relative > to -current as of right now: >=20 > http://phk.freebsd.dk/patch/phk_bufwork20041113.patch >=20 > The patch contains four changes which I need help to test before > it goes into -current. >=20 > Select(2)/Poll(2) runs giant free on network/fifos. >=20 > Could be tested on a busy server (web/mail/etc). >=20 > Vnode bypass for devices (same code as in -current, only not disabled) >=20 > Could be tested with database accessing raw disk partition, > fsck of large filesystems etc etc. >=20 > Please test HW crypto support if at all possible. >=20 > Vnode bypass for fifos. >=20 > Test with anything using fifos (such as make -j N :-) >=20 > VOP_BMAP backing vnode -> backing bufobj >=20 > UFS/FFS file activity will test this. >=20 > Any and all benchmarking will be very welcome! >=20 I've been running this on my desktop for two days now with no ill effects. At the moment I don't have time for benchmarking though. - Christian --=20 Christian Brueffer chris@unixpages.org brueffer@FreeBSD.org GPG Key: http://people.freebsd.org/~brueffer/brueffer.key.asc GPG Fingerprint: A5C8 2099 19FF AACA F41B B29B 6C76 178C A0ED 982D --kXdP64Ggrk/fb43R Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBmS0KbHYXjKDtmC0RAk9eAKCxZXzu1CTLtAvxSkUL48wPiEvvlgCgn0BT 7m0JQ+iPAGmyP/4V5qnhUMM= =hp8i -----END PGP SIGNATURE----- --kXdP64Ggrk/fb43R-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:28:33 2004 Return-Path: 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 5066A16A4CE for ; Mon, 15 Nov 2004 22:28:33 +0000 (GMT) Received: from vbook.fbsd.ru (user142.hovrino.net [82.179.232.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8A73443D4C for ; Mon, 15 Nov 2004 22:28:31 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTpKd-0000XD-VY; Tue, 16 Nov 2004 01:28:19 +0300 From: Vladimir Grebenschikov To: "current@freebsd.org" In-Reply-To: <1098773925.1071.9.camel@localhost> References: <1098564131.1064.3.camel@localhost> <20041025.212820.60925870.imp@bsdimp.com> <1098773925.1071.9.camel@localhost> Content-Type: multipart/mixed; boundary="=-ksCPmSf7n9oDW+jHzbTV" Organization: SWsoft Date: Tue, 16 Nov 2004 01:28:19 +0300 Message-Id: <1100557699.1098.16.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "M. Warner Losh" cc: Mike Tancsa Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:28:33 -0000 --=-ksCPmSf7n9oDW+jHzbTV Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable =F7 =D7=D4, 26/10/2004 =D7 10:58 +0400, Vladimir Grebenschikov =D0=C9=DB=C5= =D4:=20 > =F7 =D0=CE, 25/10/2004 =D7 21:28 -0600, M. Warner Losh =D0=C9=DB=C5=D4: > > In message: <1098564131.1064.3.camel@localhost> > > Vladimir Grebenschikov writes: >=20 > > : fxp0: DMA timeout > > : fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > : fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > > :=20 > > : any clues ? > > :=20 > > : With about week-old kernel all is ok. > >=20 > > Uggg. Maybe this is due to the address that is assigned to it. I'm > > having horrible luck with your machine, no? >=20 > Not sure, I think some development glitches is normal living on - > CURRENT. >=20 > Playing with problem I have found that week-day old kernel report same > problem and them problem disappear. Problem is here again, on fresh current, no influence by another OS this time: fxp0: port 0x4000-0x403f mem 0xd0200000-0xd0200fff irq 9 at device 8.0 on pci2 fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0xfffd fxp0: EEPROM checksum @ 0xff: 0xffff -> 0xbbb9 fxp0: Ethernet address: ff:ff:ff:ff:ff:ff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: DMA timeout fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: DMA timeout fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff fxp0: SCB timeout: 0xff 0xff 0xff 0xffff Output of 'devinfo -r' and 'pciconf -l -v' attached. Probably this is due to removed IPSEC from kernel config, this can cause MPSAFE on entire net stack. Will turn it off and try again.=20 --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com --=-ksCPmSf7n9oDW+jHzbTV Content-Disposition: attachment; filename=devinfo-r.txt Content-Type: text/plain; name=devinfo-r.txt; charset=KOI8-R Content-Transfer-Encoding: base64 bmV4dXMwDQogIGFjcGkwDQogICAgICBJbnRlcnJ1cHQgcmVxdWVzdCBsaW5lczoNCiAgICAgICAg ICAweDkNCiAgICAgIEkvTyBwb3J0czoNCiAgICAgICAgICAweDJlLTB4MmYNCiAgICAgICAgICAw eDYxDQogICAgICAgICAgMHg2Mw0KICAgICAgICAgIDB4NjUNCiAgICAgICAgICAweDY3DQogICAg ICAgICAgMHg4MA0KICAgICAgICAgIDB4OTINCiAgICAgICAgICAweGIyLTB4YjMNCiAgICAgICAg ICAweDYwMC0weDYwZg0KICAgICAgICAgIDB4NzAwLTB4NzBmDQogICAgICAgICAgMHgxMDAwLTB4 MTA3Zg0KICAgICAgICAgIDB4MTE4MC0weDExYmYNCiAgICAgICAgICAweGZlMDAtMHhmZTAxDQog ICAgICAgICAgMHhmZTEwLTB4ZmUxNw0KICAgICAgSS9PIG1lbW9yeSBhZGRyZXNzZXM6DQogICAg ICAgICAgMHhmZWJmZTAwMC0weGZlYmZlZmZmDQogICAgICAgICAgMHhmZWJmZjAwMC0weGZlYmZm ZmZmDQogICAgICAgICAgMHhmZWMwMDAwMC0weGZlYzAwZmZmDQogICAgY3B1MA0KICAgICAgICBJ L08gcG9ydHM6DQogICAgICAgICAgICAweDEwMTAtMHgxMDEzDQogICAgICAgICAgICAweDEwMTQN CiAgICBhY3BpX3R6MA0KICAgIGFjcGlfbGlkMA0KICAgIGFjcGlfYnV0dG9uMA0KICAgIHBjaWIw DQogICAgICBwY2kwDQogICAgICAgIGFncDANCiAgICAgICAgICAgIEkvTyBtZW1vcnkgYWRkcmVz c2VzOg0KICAgICAgICAgICAgICAgIDB4ZTAwMDAwMDAtMHhlZmZmZmZmZg0KICAgICAgICBwY2li MQ0KICAgICAgICAgIHBjaTENCiAgICAgICAgICAgIGRybTANCiAgICAgICAgICAgICAgICBJL08g cG9ydHM6DQogICAgICAgICAgICAgICAgICAgIDB4MzAwMC0weDMwZmYNCiAgICAgICAgICAgICAg ICBJL08gbWVtb3J5IGFkZHJlc3NlczoNCiAgICAgICAgICAgICAgICAgICAgMHhkMDEwMDAwMC0w eGQwMTBmZmZmDQogICAgICAgICAgICAgICAgICAgIDB4ZDgwMDAwMDAtMHhkZmZmZmZmZg0KICAg ICAgICB1aGNpMA0KICAgICAgICAgICAgSS9PIHBvcnRzOg0KICAgICAgICAgICAgICAgIDB4MTgw MC0weDE4MWYNCiAgICAgICAgICB1c2IwDQogICAgICAgICAgICB1aHViMA0KICAgICAgICB1aGNp MQ0KICAgICAgICAgICAgSS9PIHBvcnRzOg0KICAgICAgICAgICAgICAgIDB4MTgyMC0weDE4M2YN CiAgICAgICAgICB1c2IxDQogICAgICAgICAgICB1aHViMQ0KICAgICAgICAgICAgICB1bXMwDQog ICAgICAgIHVoY2kyDQogICAgICAgICAgICBJL08gcG9ydHM6DQogICAgICAgICAgICAgICAgMHgx ODQwLTB4MTg1Zg0KICAgICAgICAgIHVzYjINCiAgICAgICAgICAgIHVodWIyDQogICAgICAgICAg ICAgIHVidDANCiAgICAgICAgZWhjaTANCiAgICAgICAgICAgIEkvTyBtZW1vcnkgYWRkcmVzc2Vz Og0KICAgICAgICAgICAgICAgIDB4ZDAwMDAwMDAtMHhkMDAwMDNmZg0KICAgICAgICAgIHVzYjMN CiAgICAgICAgICAgIHVodWIzDQogICAgICAgICAgICAgIHVtYXNzMQ0KICAgICAgICBwY2liMg0K ICAgICAgICAgIHBjaTINCiAgICAgICAgICAgIGNiYjANCiAgICAgICAgICAgICAgICBJL08gbWVt b3J5IGFkZHJlc3NlczoNCiAgICAgICAgICAgICAgICAgICAgMHhkMDIwMzAwMC0weGQwMjAzZmZm DQogICAgICAgICAgICAgIGNhcmRidXMwDQogICAgICAgICAgICBmd29oY2kwDQogICAgICAgICAg ICAgICAgSS9PIG1lbW9yeSBhZGRyZXNzZXM6DQogICAgICAgICAgICAgICAgICAgIDB4ZDAyMDIw MDAtMHhkMDIwMjdmZg0KICAgICAgICAgICAgICBmaXJld2lyZTANCiAgICAgICAgICAgICAgICBz YnAwDQogICAgICAgICAgICBuZGlzMA0KICAgICAgICAgICAgICAgIEkvTyBtZW1vcnkgYWRkcmVz c2VzOg0KICAgICAgICAgICAgICAgICAgICAweGQwMjAxMDAwLTB4ZDAyMDFmZmYNCiAgICAgICAg aXNhYjANCiAgICAgICAgICBpc2EwDQogICAgICAgICAgICBwbXRpbWVyMA0KICAgICAgICAgICAg c2MwDQogICAgICAgICAgICB2Z2EwDQogICAgICAgICAgICAgICAgSS9PIHBvcnRzOg0KICAgICAg ICAgICAgICAgICAgICAweDNjMC0weDNkZg0KICAgICAgICAgICAgICAgIEkvTyBtZW1vcnkgYWRk cmVzc2VzOg0KICAgICAgICAgICAgICAgICAgICAweGEwMDAwLTB4YmZmZmYNCiAgICAgICAgICAg IG9ybTANCiAgICAgICAgICAgICAgICBJL08gbWVtb3J5IGFkZHJlc3NlczoNCiAgICAgICAgICAg ICAgICAgICAgMHhjMDAwMC0weGNmZmZmDQogICAgICAgICAgICAgICAgICAgIDB4ZDgwMDAtMHhk YmZmZg0KICAgICAgICAgICAgICAgICAgICAweGRjMDAwLTB4ZGZmZmYNCiAgICAgICAgYXRhcGNp MA0KICAgICAgICAgICAgSS9PIHBvcnRzOg0KICAgICAgICAgICAgICAgIDB4MTcwLTB4MTc3DQog ICAgICAgICAgICAgICAgMHgxZjAtMHgxZjcNCiAgICAgICAgICAgICAgICAweDM3Ng0KICAgICAg ICAgICAgICAgIDB4M2Y2DQogICAgICAgICAgICAgICAgMHgxODYwLTB4MTg2Zg0KICAgICAgICAg IGF0YTANCiAgICAgICAgICAgICAgSW50ZXJydXB0IHJlcXVlc3QgbGluZXM6DQogICAgICAgICAg ICAgICAgICAweGUNCiAgICAgICAgICBhdGExDQogICAgICAgICAgICAgIEludGVycnVwdCByZXF1 ZXN0IGxpbmVzOg0KICAgICAgICAgICAgICAgICAgMHhmDQogICAgICAgIHBjbTANCiAgICAgICAg ICAgIEkvTyBwb3J0czoNCiAgICAgICAgICAgICAgICAweDE4YzAtMHgxOGZmDQogICAgICAgICAg ICAgICAgMHgxYzAwLTB4MWNmZg0KICAgICAgICAgICAgSS9PIG1lbW9yeSBhZGRyZXNzZXM6DQog ICAgICAgICAgICAgICAgMHhkMDAwMDgwMC0weGQwMDAwOGZmDQogICAgICAgICAgICAgICAgMHhk MDAwMGMwMC0weGQwMDAwZGZmDQogICAgYXR0aW1lcjANCiAgICBhdHBpYzANCiAgICBhdHRpbWVy MQ0KICAgIG5weGlzYTANCiAgICBhdGRtYTANCiAgICBhY3BpX3N5c3Jlc291cmNlMA0KICAgIGFj cGlfZWMwDQogICAgICAgIEkvTyBwb3J0czoNCiAgICAgICAgICAgIDB4NjINCiAgICAgICAgICAg IDB4NjYNCiAgICBhY3BpX2NtYmF0MA0KICAgIGFjcGlfYWNhZDANCiAgICBhY3BpX3NuYzANCiAg ICBhdGtiZGMwDQogICAgICAgIEkvTyBwb3J0czoNCiAgICAgICAgICAgIDB4NjANCiAgICAgICAg ICAgIDB4NjQNCiAgICAgIGF0a2JkMA0KICAgICAgICAgIEludGVycnVwdCByZXF1ZXN0IGxpbmVz Og0KICAgICAgICAgICAgICAweDENCiAgICAgIHBzbTANCiAgICAgICAgICBJbnRlcnJ1cHQgcmVx dWVzdCBsaW5lczoNCiAgICAgICAgICAgICAgMHhjDQogICAgcHNtY3BucDANCiAgICBhY3BpX3Rp bWVyMA0KICAgICAgICBJL08gcG9ydHM6DQogICAgICAgICAgICAweDEwMDgtMHgxMDBiDQogIG5w eDANCiAgICAgIEludGVycnVwdCByZXF1ZXN0IGxpbmVzOg0KICAgICAgICAgIDB4ZA0K --=-ksCPmSf7n9oDW+jHzbTV Content-Disposition: attachment; filename=pciconf-lv Content-Type: text/plain; name=pciconf-lv; charset=KOI8-R Content-Transfer-Encoding: base64 YWdwMEBwY2kwOjA6MDoJY2xhc3M9MHgwNjAwMDAgY2FyZD0weDgxNDAxMDRkIGNoaXA9MHgzMzQw ODA4NiByZXY9MHgwMyBoZHI9MHgwMA0KICAgIHZlbmRvciAgID0gJ0ludGVsIENvcnBvcmF0aW9u Jw0KICAgIGRldmljZSAgID0gJzgyODU1UE0gT2RlbSBIb3N0LUh1YiBJbnRlcmZhY2UgQnJpZGdl Jw0KICAgIGNsYXNzICAgID0gYnJpZGdlDQogICAgc3ViY2xhc3MgPSBIT1NULVBDSQ0KcGNpYjFA cGNpMDoxOjA6CWNsYXNzPTB4MDYwNDAwIGNhcmQ9MHgwMDAwMDAwMCBjaGlwPTB4MzM0MTgwODYg cmV2PTB4MDMgaGRyPTB4MDENCiAgICB2ZW5kb3IgICA9ICdJbnRlbCBDb3Jwb3JhdGlvbicNCiAg ICBkZXZpY2UgICA9ICc4Mjg1NVBNIE9kZW0gQUdQIEJyaWRnZScNCiAgICBjbGFzcyAgICA9IGJy aWRnZQ0KICAgIHN1YmNsYXNzID0gUENJLVBDSQ0KdWhjaTBAcGNpMDoyOTowOgljbGFzcz0weDBj MDMwMCBjYXJkPTB4ODE0MDEwNGQgY2hpcD0weDI0YzI4MDg2IHJldj0weDAzIGhkcj0weDAwDQog ICAgdmVuZG9yICAgPSAnSW50ZWwgQ29ycG9yYXRpb24nDQogICAgZGV2aWNlICAgPSAnODI4MDFE Qi9EQkwvREJNIChJQ0g0L0lDSDQtTC9JQ0g0LU0pIFVTQiBVSENJIENvbnRyb2xsZXIgIzEnDQog ICAgY2xhc3MgICAgPSBzZXJpYWwgYnVzDQogICAgc3ViY2xhc3MgPSBVU0INCnVoY2kxQHBjaTA6 Mjk6MToJY2xhc3M9MHgwYzAzMDAgY2FyZD0weDgxNDAxMDRkIGNoaXA9MHgyNGM0ODA4NiByZXY9 MHgwMyBoZHI9MHgwMA0KICAgIHZlbmRvciAgID0gJ0ludGVsIENvcnBvcmF0aW9uJw0KICAgIGRl dmljZSAgID0gJzgyODAxREIvREJML0RCTSAoSUNINC9JQ0g0LUwvSUNINC1NKSBVU0IgVUhDSSBD b250cm9sbGVyICMyJw0KICAgIGNsYXNzICAgID0gc2VyaWFsIGJ1cw0KICAgIHN1YmNsYXNzID0g VVNCDQp1aGNpMkBwY2kwOjI5OjI6CWNsYXNzPTB4MGMwMzAwIGNhcmQ9MHg4MTQwMTA0ZCBjaGlw PTB4MjRjNzgwODYgcmV2PTB4MDMgaGRyPTB4MDANCiAgICB2ZW5kb3IgICA9ICdJbnRlbCBDb3Jw b3JhdGlvbicNCiAgICBkZXZpY2UgICA9ICc4MjgwMURCL0RCTC9EQk0gKElDSDQvSUNINC1ML0lD SDQtTSkgVVNCIFVIQ0kgQ29udHJvbGxlciAjMycNCiAgICBjbGFzcyAgICA9IHNlcmlhbCBidXMN CiAgICBzdWJjbGFzcyA9IFVTQg0KZWhjaTBAcGNpMDoyOTo3OgljbGFzcz0weDBjMDMyMCBjYXJk PTB4ODE0MDEwNGQgY2hpcD0weDI0Y2Q4MDg2IHJldj0weDAzIGhkcj0weDAwDQogICAgdmVuZG9y ICAgPSAnSW50ZWwgQ29ycG9yYXRpb24nDQogICAgZGV2aWNlICAgPSAnODI4MDFEQi9EQkwvREJN IChJQ0g0L0lDSDQtTC9JQ0g0LU0pIFVTQiBFSENJIENvbnRyb2xsZXInDQogICAgY2xhc3MgICAg PSBzZXJpYWwgYnVzDQogICAgc3ViY2xhc3MgPSBVU0INCnBjaWIyQHBjaTA6MzA6MDoJY2xhc3M9 MHgwNjA0MDAgY2FyZD0weDAwMDAwMDAwIGNoaXA9MHgyNDQ4ODA4NiByZXY9MHg4MyBoZHI9MHgw MQ0KICAgIHZlbmRvciAgID0gJ0ludGVsIENvcnBvcmF0aW9uJw0KICAgIGRldmljZSAgID0gJzgy ODAxQkFNL0NBTS9EQk0gKElDSDItTS8zLU0vNC1NKSBIdWIgSW50ZXJmYWNlIHRvIFBDSSBCcmlk Z2UnDQogICAgY2xhc3MgICAgPSBicmlkZ2UNCiAgICBzdWJjbGFzcyA9IFBDSS1QQ0kNCmlzYWIw QHBjaTA6MzE6MDoJY2xhc3M9MHgwNjAxMDAgY2FyZD0weDAwMDAwMDAwIGNoaXA9MHgyNGNjODA4 NiByZXY9MHgwMyBoZHI9MHgwMA0KICAgIHZlbmRvciAgID0gJ0ludGVsIENvcnBvcmF0aW9uJw0K ICAgIGRldmljZSAgID0gJzgyODAxREJNIChJQ0g0LU0pIExQQyBJbnRlcmZhY2UgQnJpZGdlJw0K ICAgIGNsYXNzICAgID0gYnJpZGdlDQogICAgc3ViY2xhc3MgPSBQQ0ktSVNBDQphdGFwY2kwQHBj aTA6MzE6MToJY2xhc3M9MHgwMTAxOGEgY2FyZD0weDgxNDAxMDRkIGNoaXA9MHgyNGNhODA4NiBy ZXY9MHgwMyBoZHI9MHgwMA0KICAgIHZlbmRvciAgID0gJ0ludGVsIENvcnBvcmF0aW9uJw0KICAg IGRldmljZSAgID0gJzgyODAxREJNIChJQ0g0LU0pIFVsdHJhQVRBLzEwMCBFSURFIENvbnRyb2xs ZXInDQogICAgY2xhc3MgICAgPSBtYXNzIHN0b3JhZ2UNCiAgICBzdWJjbGFzcyA9IEFUQQ0Kbm9u ZTBAcGNpMDozMTozOgljbGFzcz0weDBjMDUwMCBjYXJkPTB4ODE0MDEwNGQgY2hpcD0weDI0YzM4 MDg2IHJldj0weDAzIGhkcj0weDAwDQogICAgdmVuZG9yICAgPSAnSW50ZWwgQ29ycG9yYXRpb24n DQogICAgZGV2aWNlICAgPSAnODI4MDFEQi9EQkwvREJNIChJQ0g0L0lDSDQtTC9JQ0g0LU0pIFNN QnVzIENvbnRyb2xsZXInDQogICAgY2xhc3MgICAgPSBzZXJpYWwgYnVzDQogICAgc3ViY2xhc3Mg PSBTTUJ1cw0KcGNtMEBwY2kwOjMxOjU6CWNsYXNzPTB4MDQwMTAwIGNhcmQ9MHg4MTQwMTA0ZCBj aGlwPTB4MjRjNTgwODYgcmV2PTB4MDMgaGRyPTB4MDANCiAgICB2ZW5kb3IgICA9ICdJbnRlbCBD b3Jwb3JhdGlvbicNCiAgICBkZXZpY2UgICA9ICc4MjgwMURCL0RCTC9EQk0gKElDSDQvSUNINC1M L0lDSDQtTSkgQUMnOTcgQXVkaW8gQ29udHJvbGxlcicNCiAgICBjbGFzcyAgICA9IG11bHRpbWVk aWENCiAgICBzdWJjbGFzcyA9IGF1ZGlvDQpub25lMUBwY2kwOjMxOjY6CWNsYXNzPTB4MDcwMzAw IGNhcmQ9MHg4MTQwMTA0ZCBjaGlwPTB4MjRjNjgwODYgcmV2PTB4MDMgaGRyPTB4MDANCiAgICB2 ZW5kb3IgICA9ICdJbnRlbCBDb3Jwb3JhdGlvbicNCiAgICBkZXZpY2UgICA9ICc4MjgwMURCL0RC TC9EQk0gKElDSDQvSUNINC1ML0lDSDQtTSkgQUMnOTcgTW9kZW0gQ29udHJvbGxlcicNCiAgICBj bGFzcyAgICA9IHNpbXBsZSBjb21tcw0KZHJtMEBwY2kxOjA6MDoJY2xhc3M9MHgwMzAwMDAgY2Fy ZD0weDgxNDAxMDRkIGNoaXA9MHg0YzU5MTAwMiByZXY9MHgwMCBoZHI9MHgwMA0KICAgIHZlbmRv ciAgID0gJ0FUSSBUZWNobm9sb2dpZXMgSW5jLicNCiAgICBkZXZpY2UgICA9ICdNb2JpbGl0eSA2 IFJhZGVvbiBNb2JpbGl0eSBNNiBMWScNCiAgICBjbGFzcyAgICA9IGRpc3BsYXkNCiAgICBzdWJj bGFzcyA9IFZHQQ0KY2JiMEBwY2kyOjU6MDoJY2xhc3M9MHgwNjA3MDAgY2FyZD0weDgxNDAxMDRk IGNoaXA9MHgwNDc1MTE4MCByZXY9MHhiOCBoZHI9MHgwMg0KICAgIHZlbmRvciAgID0gJ1JpY29o IENvIEx0ZCcNCiAgICBkZXZpY2UgICA9ICdSTDVjNDc1IENhcmRCdXMgQ29udHJvbGxlcicNCiAg ICBjbGFzcyAgICA9IGJyaWRnZQ0KICAgIHN1YmNsYXNzID0gUENJLUNhcmRCdXMNCmZ3b2hjaTBA cGNpMjo1OjE6CWNsYXNzPTB4MGMwMDEwIGNhcmQ9MHg4MTQwMTA0ZCBjaGlwPTB4MDU1MTExODAg cmV2PTB4MDAgaGRyPTB4MDANCiAgICB2ZW5kb3IgICA9ICdSaWNvaCBDbyBMdGQnDQogICAgY2xh c3MgICAgPSBzZXJpYWwgYnVzDQogICAgc3ViY2xhc3MgPSBGaXJlV2lyZQ0Kbm9uZTJAcGNpMjo4 OjA6CWNsYXNzPTB4MDIwMDAwIGNhcmQ9MHg4MTQwMTA0ZCBjaGlwPTB4MTAzZDgwODYgcmV2PTB4 ODMgaGRyPTB4MDANCiAgICB2ZW5kb3IgICA9ICdJbnRlbCBDb3Jwb3JhdGlvbicNCiAgICBkZXZp Y2UgICA9ICc4MjgwMURCIChJQ0g0KSBQUk8vMTAwIFZFIE5ldHdvcmsgQ29ubmVjdGlvbicNCiAg ICBjbGFzcyAgICA9IG5ldHdvcmsNCiAgICBzdWJjbGFzcyA9IGV0aGVybmV0DQpuZGlzMEBwY2ky OjExOjA6CWNsYXNzPTB4MDI4MDAwIGNhcmQ9MHgyNzUxODA4NiBjaGlwPTB4NDIyMDgwODYgcmV2 PTB4MDUgaGRyPTB4MDANCiAgICB2ZW5kb3IgICA9ICdJbnRlbCBDb3Jwb3JhdGlvbicNCiAgICBk ZXZpY2UgICA9ICdQUk8vV2lyZWxlc3MgMjIwMEJHIE5ldHdvcmsgQ29ubmVjdGlvbicNCiAgICBj bGFzcyAgICA9IG5ldHdvcmsNCg== --=-ksCPmSf7n9oDW+jHzbTV-- From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:38:41 2004 Return-Path: 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 6730C16A4CE for ; Mon, 15 Nov 2004 22:38:41 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECCB543D4C for ; Mon, 15 Nov 2004 22:38:40 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAFMZdOB024422; Mon, 15 Nov 2004 15:35:39 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 15:35:57 -0700 (MST) Message-Id: <20041115.153557.128618461.imp@bsdimp.com> To: vova@sw.ru From: "M. Warner Losh" In-Reply-To: <1100557699.1098.16.camel@localhost> References: <20041025.212820.60925870.imp@bsdimp.com> <1098773925.1071.9.camel@localhost> <1100557699.1098.16.camel@localhost> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: mike@sentex.net Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 22:38:41 -0000 Can you also provide pciconf -r pci2:5:0 0:0xff Warner From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 22:46:05 2004 Return-Path: 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 56FEC16A4D0 for ; Mon, 15 Nov 2004 22:46:05 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id B10E343D41 for ; Mon, 15 Nov 2004 22:46:04 +0000 (GMT) (envelope-from anurekh@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so539882rns for ; Mon, 15 Nov 2004 14:46:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=I8qsnUlcWqKbL86v/kA31AQmn4T7DA9vXBoxczT51TPfuu52T23fT8wiCzxGwBTmaj+TQtABxDsMJ2xa1U77y1SnySPs7RlRBTvHoDRbWUKB90VrVFy6bebrF904usUaxJ1ejiThRxCV85B+TKm51EHvd4PAYWWtsThYt53+Mko= Received: by 10.38.179.67 with SMTP id b67mr1221831rnf; Mon, 15 Nov 2004 14:46:03 -0800 (PST) Received: by 10.38.8.23 with HTTP; Mon, 15 Nov 2004 14:46:03 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 17:46:03 -0500 From: Anurekh Saxena To: John Baldwin In-Reply-To: <200411151433.57236.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200411151433.57236.jhb@FreeBSD.org> cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: kernel: return from interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Anurekh Saxena List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 22:46:05 -0000 On Mon, 15 Nov 2004 14:33:57 -0500, John Baldwin wrote: > On Thursday 11 November 2004 10:59 pm, Anurekh Saxena wrote: > > > > > > > Even normal "options PREEMPTION" should do this. I know from tracing > > > > > the kernel in 6.x that that's the way the system behaves out of the > > > > > box; with PREEMPTION turned on in 5.x you should see the same > > > > > behavior. One thing I often do see, FWIW, is that if you're on an > > > > > SMP box, the ithread will get scheduled to run immediately on another > > > > > CPU that's idle, so you won't actually preempt the thread on the > > > > > current CPU other than for the interrupt handler. What behavior are > > > > > you seeing that suggests this isn't happening with PREEMPTION > > > > > compiled in? > > > > > > > > I may be missing something fundamental here, but, doreti (exceptions.s) > > > > does not call 'ast' for an interrupted task, that does not have RPL of > > > > 3 (user). So, even if an interrupt is pending, and the 'NEEDRESCHED' > > > > is set, the scheduling decision is delayed till the kernel thread or > > > > whatever was running in the kernel sleeps, or give up the cpu(call > > > > mi_switch), or returns to user mode. > > > > > > > > AFAIK this is the only return path from an interrupt. Unless there is > > > > another return path for the interrupts, the scheduler is not invoked on > > > > a return. > > > > > > Assuming we're talking about i386, lapic_handle_intr() will call > > > intr_execute_handlers(), which will walk the list of handlers for the > > > interrupt, and either directly invoke the fast handlers of the > > > interrupts, or call ithread_schedule() to schedule the ithread. > > > ithread_schedule() will invoke setrunqueue(), which enters the scheduler > > > and is a preemption point. If you dig down a bit, you'll find a call to > > > maybe_preempt(), which may preempt if appropriate, resulting in a call to > > > mi_switch() to the ithread. The maybe_preempt() code will only kick in > > > to actually switch if PREEMPTION is defined. > > > > Yeah, I got it wrong. Without the FULL_PREEMPTION enabled, it does not > > preempt unless the current thread is in the idle priority band. > > I was expecting the NEEDRESCHED flag to be used for preemption on > > return paths, especially for interrupt context. I think this method > > works better since preemption points become well defined in the > > kernel. > > Thanks for helping me figure this out. > > NEEDRESCHED (albeit rather broken at the moment) is used to implement > preemptino of user threads. As Robert mentioned above, in-kernel preemption > is managed via either direct switches in setrunqueue() or deferred > preemptions via TDF_OWEPREEMPT in critical_exit(). > Yeah, I think I get the way its done, but it would be nice to be able to use the NEEDRESCHED flag as a general way to say... we need to resched, irrespective of which mode we are returning to. I don't know how much of the code expecrs the current behavior. I can think of atleast two ways in which the generic flag could be used. I don't know whether its a good idea or not. Just a thought. 1> The generic return-from-'some form of interrupt' path can simply call the scheduler if the flag is set. Though I cant think of any examples to provide, but it may be used as a defer flag, just like the TDF_OWEPREEMPT is used at the moment. 2> A kernel thread that wants to be able to do as much work as it can, may keep checking this flag and know when to preempt. Thanks, -Anurekh From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 00:15:06 2004 Return-Path: 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 5B89D16A4CE; Tue, 16 Nov 2004 00:15:06 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2D0143D2D; Tue, 16 Nov 2004 00:15:00 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id iAG0Epes067421; Tue, 16 Nov 2004 01:14:52 +0100 (CET) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iAG0Emu0075542; Tue, 16 Nov 2004 01:14:49 +0100 (CET) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id iAG0Em9v075531; Tue, 16 Nov 2004 01:14:48 +0100 (CET) (envelope-from mb@imp.ch) X-Authentication-Warning: mx2.imp.ch: clamav set sender to using -f Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id iAG0EhXY097069; Tue, 16 Nov 2004 01:14:48 +0100 (CET) Date: Tue, 16 Nov 2004 01:14:43 +0100 (CET) From: Martin Blapp To: John Baldwin In-Reply-To: <200411151606.45640.jhb@FreeBSD.org> Message-ID: <20041116011054.M53544@cvs.imp.ch> References: <200411150857.42423.peter@wemm.org> <20041115180045.B53544@cvs.imp.ch> <200411151606.45640.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: b21dfb9d029dbd772bbac835b9e4afcd X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0010 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="2.8355 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 157.161.9.18 cc: freebsd-current@FreeBSD.org cc: Robert Watson cc: current@FreeBSD.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:15:06 -0000 Hi, > Was the box swapping at the time? It could be that named was swapped out when > you tried to kill it. No. The load was ~ 3 this time and there was a lot of IO going on. But the box did not swap at all, it was untouched. We have 2GB ram in this server so it does not swap at all usually: Mem: 504M Active, 1178M Inact, 182M Wired, 95M Cache, 112M Buf, 43M Free Swap: 4096M Total, 60K Used, 4096M Free Martin From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 00:15:06 2004 Return-Path: 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 5B89D16A4CE; Tue, 16 Nov 2004 00:15:06 +0000 (GMT) Received: from mx1.imp.ch (mx1.imp.ch [157.161.9.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2D0143D2D; Tue, 16 Nov 2004 00:15:00 +0000 (GMT) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (mx2o [157.161.9.17]) by mx1.imp.ch (8.12.11/8.12.11) with ESMTP id iAG0Epes067421; Tue, 16 Nov 2004 01:14:52 +0100 (CET) (envelope-from mb@imp.ch) Received: from mx2.imp.ch (localhost [127.0.0.1]) by mx2.imp.ch (8.12.11/8.12.11/Submit) with ESMTP id iAG0Emu0075542; Tue, 16 Nov 2004 01:14:49 +0100 (CET) (envelope-from mb@imp.ch) Received: (from clamav@localhost) by mx2.imp.ch (8.12.11/8.12.11/Submit) id iAG0Em9v075531; Tue, 16 Nov 2004 01:14:48 +0100 (CET) (envelope-from mb@imp.ch) X-Authentication-Warning: mx2.imp.ch: clamav set sender to using -f Received: from cvs.imp.ch (cvs.imp.ch [157.161.4.9]) by ns1.imp.ch (MIMEDefang) with ESMTP id iAG0EhXY097069; Tue, 16 Nov 2004 01:14:48 +0100 (CET) Date: Tue, 16 Nov 2004 01:14:43 +0100 (CET) From: Martin Blapp To: John Baldwin In-Reply-To: <200411151606.45640.jhb@FreeBSD.org> Message-ID: <20041116011054.M53544@cvs.imp.ch> References: <200411150857.42423.peter@wemm.org> <20041115180045.B53544@cvs.imp.ch> <200411151606.45640.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Resent: Yes X-Spam-Checksum: b21dfb9d029dbd772bbac835b9e4afcd X-Virus-Message-Status: No X-Virus-Status: No, scantime="0.0010 seconds" X-Spam-Status: No, hits=-4.9 required=5 scantime="2.8355 seconds" tests=BAYES_00 X-Scanned-By: MIMEDefang 2.48 on 157.161.9.18 cc: freebsd-current@FreeBSD.org cc: Robert Watson cc: current@FreeBSD.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:15:06 -0000 Hi, > Was the box swapping at the time? It could be that named was swapped out when > you tried to kill it. No. The load was ~ 3 this time and there was a lot of IO going on. But the box did not swap at all, it was untouched. We have 2GB ram in this server so it does not swap at all usually: Mem: 504M Active, 1178M Inact, 182M Wired, 95M Cache, 112M Buf, 43M Free Swap: 4096M Total, 60K Used, 4096M Free Martin From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 00:17:18 2004 Return-Path: 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 D482B16A4CE for ; Tue, 16 Nov 2004 00:17:18 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAE4143D3F for ; Tue, 16 Nov 2004 00:17:17 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG0GJZg006214 for ; Tue, 16 Nov 2004 10:46:19 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 10:47:11 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG0Axh00856 for ; Tue, 16 Nov 2004 10:40:59 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMS5B; Tue, 16 Nov 2004 10:40:52 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG0BllS056438 for ; Tue, 16 Nov 2004 10:41:47 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG0Bk8o056437 for current@freebsd.org; Tue, 16 Nov 2004 10:41:46 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 10:41:46 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041116001146.GB56252@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <200411152211.iAFMB9YF016201@repoman.freebsd.org> <30117.1100556843@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <30117.1100556843@critter.freebsd.dk> User-Agent: Mutt/1.5.6i Subject: Re: [HEADSUP] vnode bypass for devices: "ON" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:17:18 -0000 Do u mind explaining what this actually means ? I'm "assuming" we are now by-passing the vnode layer for performance reasons ? - aW 0n Mon, Nov 15, 2004 at 11:14:03PM +0100, Poul-Henning Kamp wrote: Vnode bypass is now ON by default in -current. From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 00:22:29 2004 Return-Path: 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 CA5AF16A4CE for ; Tue, 16 Nov 2004 00:22:29 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CAB443D53 for ; Tue, 16 Nov 2004 00:22:29 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG0LUZg006845 for ; Tue, 16 Nov 2004 10:51:30 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 10:52:20 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG0Fph22221 for ; Tue, 16 Nov 2004 10:45:51 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMTFL; Tue, 16 Nov 2004 10:45:44 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG0GdxO056470 for ; Tue, 16 Nov 2004 10:46:39 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG0Gda8056469 for current@freebsd.org; Tue, 16 Nov 2004 10:46:39 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 10:46:39 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041116001638.GC56252@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <20041112054741.GY40520@squash.dsto.defence.gov.au> <6.1.2.0.0.20041115075917.12684480@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <6.1.2.0.0.20041115075917.12684480@64.7.153.2> User-Agent: Mutt/1.5.6i Subject: Re: dealing with interupt storms ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:22:29 -0000 No, it is UP. hostb0@pci0:0:0: class=0x060000 card=0x12bc103c chip=0x25708086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82865G/PE/P, 82848P DRAM Controller / Host-Hub Interface' class = bridge subclass = HOST-PCI pcib1@pci0:1:0: class=0x060400 card=0x00000000 chip=0x25718086 rev=0x02 hdr=0x01 vendor = 'Intel Corporation' device = '82865G/PE/P, 82848P PCI-to-AGP Bridge' class = bridge subclass = PCI-PCI uhci0@pci0:29:0: class=0x0c0300 card=0x12bc103c chip=0x24d28086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1' class = serial bus subclass = USB uhci1@pci0:29:1: class=0x0c0300 card=0x12bc103c chip=0x24d48086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2' class = serial bus subclass = USB uhci2@pci0:29:2: class=0x0c0300 card=0x12bc103c chip=0x24d78086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB UHCI Controller #3' class = serial bus subclass = USB none0@pci0:29:7: class=0x0c0320 card=0x12bc103c chip=0x24dd8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) USB EHCI Controller' class = serial bus subclass = USB pcib2@pci0:30:0: class=0x060400 card=0x00000000 chip=0x244e8086 rev=0xc2 hdr=0x01 vendor = 'Intel Corporation' device = '82801BA/CA/DB/DBL/EB/ER (ICH2/3/4/4-L/5/5R), 6300ESB Hub Interface to PCI Bridge' class = bridge subclass = PCI-PCI isab0@pci0:31:0: class=0x060100 card=0x00000000 chip=0x24d08086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) LPC Interface Bridge' class = bridge subclass = PCI-ISA atapci0@pci0:31:1: class=0x01018a card=0x12bc103c chip=0x24db8086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) EIDE Controller' class = mass storage subclass = ATA atapci1@pci0:31:2: class=0x01018f card=0x12bc103c chip=0x24d18086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB (ICH5) SATA Controller' class = mass storage subclass = ATA none1@pci0:31:5: class=0x040100 card=0x12bc103c chip=0x24d58086 rev=0x02 hdr=0x00 vendor = 'Intel Corporation' device = '82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller' class = multimedia subclass = audio nvidia0@pci1:0:0: class=0x030000 card=0x80e31043 chip=0x032210de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GeForce FX 5200 [NV34.3]' class = display subclass = VGA bge0@pci5:2:0: class=0x020000 card=0x12bc103c chip=0x169614e4 rev=0x03 hdr=0x00 vendor = 'Broadcom Corporation' device = 'BCM5782 Broadcom NetXtreme Gigabit Ethernet for hp' class = network subclass = ethernet bt0@pci5:9:0: class=0x010000 card=0x00000000 chip=0x1040104b rev=0x00 hdr=0x00 vendor = 'Buslogic' device = 'BA80c30 PCI-SCSI MultiMaster' class = mass storage subclass = SCSI 0n Mon, Nov 15, 2004 at 08:00:07AM -0500, Mike Tancsa wrote: At 12:47 AM 12/11/2004, Wilkinson, Alex wrote: >Hi all, > >How does one stop an interrupt storm in RELENG_5 ? Is this an SMP machine ? What does dmesg show as well as pciconf -v ? ---Mike From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 00:32:20 2004 Return-Path: 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 0744016A4CE for ; Tue, 16 Nov 2004 00:32:20 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FAA443D1F for ; Tue, 16 Nov 2004 00:32:19 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG0VKZg007991 for ; Tue, 16 Nov 2004 11:01:20 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 11:02:11 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG0Rnh25372 for ; Tue, 16 Nov 2004 10:57:49 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMT5M; Tue, 16 Nov 2004 10:57:42 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG0SbGo056556 for ; Tue, 16 Nov 2004 10:58:37 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG0SbqE056555 for current@freebsd.org; Tue, 16 Nov 2004 10:58:37 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 10:58:37 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041116002837.GE56252@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <20041115142036.D53544@cvs.imp.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:32:20 -0000 Robert, what is an NMI button ? - aW 0n Mon, Nov 15, 2004 at 01:35:26PM +0000, Robert Watson wrote: On Mon, 15 Nov 2004, Martin Blapp wrote: > > syscons is typically a sign that some thread holding Giant is spinning, or > > that Giant has been leaked. Alternatively, some other lock is leaked, and > > a thread with Giant waits on that lock. You may be able to get into DDB > > using the serial console as it doesn't require Giant (or you might not). > > I was not able to get into DDB over serial console. Sorry for not saying > this exactly. Hardlock. Any chance that any of the boxes has an NMI button? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research _______________________________________________ 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 16 00:43:38 2004 Return-Path: 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 E95DE16A4CE for ; Tue, 16 Nov 2004 00:43:38 +0000 (GMT) Received: from mail.dt.e-technik.uni-dortmund.de (mail.dt.e-technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D12443D1D for ; Tue, 16 Nov 2004 00:43:38 +0000 (GMT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from localhost (localhost [127.0.0.1])9BF073F912 for ; Tue, 16 Nov 2004 01:43:37 +0100 (CET) Received: from mail.dt.e-technik.uni-dortmund.de ([127.0.0.1]) by localhost (krusty [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21237-02-2 for ; Tue, 16 Nov 2004 01:43:37 +0100 (CET) Received: from m2a2.dyndns.org (pD9FFB35C.dip.t-dialin.net [217.255.179.92]) 56CAE3F90A for ; Tue, 16 Nov 2004 01:43:37 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id 911F9C9768 for ; Tue, 16 Nov 2004 01:43:36 +0100 (CET) Received: from merlin.emma.line.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 06728-07 for ; Tue, 16 Nov 2004 01:43:35 +0100 (CET) Received: by merlin.emma.line.org (Postfix, from userid 500) id BD919C92CA; Tue, 16 Nov 2004 01:43:35 +0100 (CET) To: current@freebsd.org In-Reply-To: <20041116002837.GE56252@squash.dsto.defence.gov.au> (Alex Wilkinson's message of "Tue, 16 Nov 2004 10:58:37 +1030") References: <20041115142036.D53544@cvs.imp.ch> <20041116002837.GE56252@squash.dsto.defence.gov.au> From: Matthias Andree Date: Tue, 16 Nov 2004 01:43:35 +0100 Message-ID: User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at dt.e-technik.uni-dortmund.de Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 00:43:39 -0000 "Wilkinson, Alex" writes: > Robert, what is an NMI button ? A button - usually on server and high-availability hardware, next to the RESET button. NMI is a non-maskable interrupt, i. e. one that software cannot opt out of. The serious part of this mail ends in this line. On your Commodore 64, it's labeled "RESTORE". :-) -- Matthias Andree From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 01:47:22 2004 Return-Path: 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 915AB16A4CE for ; Tue, 16 Nov 2004 01:47:22 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC70C43D53 for ; Tue, 16 Nov 2004 01:47:16 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG1kIZg016188 for ; Tue, 16 Nov 2004 12:16:18 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 12:17:10 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG1eXh30909 for ; Tue, 16 Nov 2004 12:10:33 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMXRT; Tue, 16 Nov 2004 12:10:26 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG1fLZW056912 for ; Tue, 16 Nov 2004 12:11:21 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG1fLLY056911 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 12:11:21 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 12:11:21 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116014121.GJ56252@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <20041115043907.GI51636@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041115043907.GI51636@squash.dsto.defence.gov.au> User-Agent: Mutt/1.5.6i Subject: Re: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 01:47:22 -0000 Is it possible to find out whether HTT is turned on in the BIOS without having to reboot ? acpidump(8) ? It's just that I notice that I have a HTT capable CPU: CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 Features=0xbfebfbff And options SMP compiled into the kernel, but lack any message in /var/run/dmesg about HTT being enabled. - aW Wilkinson, Alex wrote: >Why is HTT turned off out of the box ? I thought HTT was meant to be a >hardware 'performance enhancing' feature. > >Why do we disable it ? > > - aW FreeBSD will use HTT if the system has it enabled (usually controlled in the BIOS) and the kernel is compiled for SMP. There are ways to manually disable HTT but leave SMP enabled in the OS, but the default is to use it if the above two requirements are met. However, the OS scheduler is not HTT-aware, so HTT will give a somewhat mixed performance. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 02:08:17 2004 Return-Path: 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 39D8116A4CE for ; Tue, 16 Nov 2004 02:08:17 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4B2B843D45 for ; Tue, 16 Nov 2004 02:08:16 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 9625 invoked by uid 65534); 16 Nov 2004 02:08:14 -0000 Received: from pD9E24053.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.226.64.83) by mail.gmx.net (mp023) with SMTP; 16 Nov 2004 03:08:14 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAG28Apa023247 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 16 Nov 2004 03:08:11 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Tue, 16 Nov 2004 03:08:05 +0100 User-Agent: KMail/1.7 References: <20041115043907.GI51636@squash.dsto.defence.gov.au> <20041116014121.GJ56252@squash.dsto.defence.gov.au> In-Reply-To: <20041116014121.GJ56252@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1648240.FTuJLW4orN"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411160308.10451.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: "Wilkinson, Alex" Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 02:08:17 -0000 --nextPart1648240.FTuJLW4orN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 16. November 2004 02:41, Wilkinson, Alex wrote: > Is it possible to find out whether HTT is turned on in the BIOS without > having to reboot ? acpidump(8) ? > > It's just that I notice that I have a HTT capable CPU: > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0xf29 Stepping =3D 9 > =20 > Features=3D0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS, HTT,TM,PBE> Not all CPUs that advertise 'HTT' do actually offer multiple logical=20 processors. sysutils/x86info is a nice utility which can provide this=20 information ... =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart1648240.FTuJLW4orN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmWEKXhc68WspdLARAsFgAJ47FL4eqFJMIXp9ufi3LwVszwvCnQCfV3Qs Znmh+y16a259NlF/Kgye3R0= =LYXg -----END PGP SIGNATURE----- --nextPart1648240.FTuJLW4orN-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 02:17:33 2004 Return-Path: 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 69BA716A4CE; Tue, 16 Nov 2004 02:17:33 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 620EC43D49; Tue, 16 Nov 2004 02:17:31 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG2GWZg019104; Tue, 16 Nov 2004 12:46:32 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Tue, 16 Nov 2004 12:47:19 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG2DXh20967; Tue, 16 Nov 2004 12:43:33 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMZCF; Tue, 16 Nov 2004 12:43:26 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG2ELd7057053 ; Tue, 16 Nov 2004 12:44:21 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG2ELJC057052; Tue, 16 Nov 2004 12:44:21 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 12:44:21 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116021421.GK56252@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, wpaul@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i cc: wpaul@freebsd.org Subject: bge(4) watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 02:17:33 -0000 On a FreeBSD 5.3-STABLE #8: Fri Nov 12 09:37:11 CST 2004 box with the following hardware : bge0: mem 0xf8400000-0xf840ffff irq 20 at device 2.0 on pci5 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:11:0a:40:d2:dd I get the following errors, however, although it states that there is no carrier, there is. bge0: firmware handshake timed out bge0: RX CPU self-diagnostics failed! bge0: flags=8843 mtu 1500 options=1a inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 ether 00:11:0a:40:d2:dd media: Ethernet autoselect (none) status: no carrier Mounting NFS file systems:bge0: watchdog timeout -- resetting Here is ifconfig(8) output after fully booted: bge0: flags=8843 mtu 1500 options=1a inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 ether 00:11:0a:40:d2:dd media: Ethernet autoselect (100baseTX ) status: active Seems odd enough, to email the wizards about it. - aW From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 02:32:26 2004 Return-Path: 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 539C516A4CE for ; Tue, 16 Nov 2004 02:32:26 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B49943D46 for ; Tue, 16 Nov 2004 02:32:25 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG2VRZg020827 for ; Tue, 16 Nov 2004 13:01:27 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 13:02:15 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG2Sch18205 for ; Tue, 16 Nov 2004 12:58:38 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDMZ6T; Tue, 16 Nov 2004 12:58:31 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG2TQAT057131 for ; Tue, 16 Nov 2004 12:59:26 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG2TQrE057130 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 12:59:26 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 12:59:26 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116022926.GB57056@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <200411160308.10451.michaelnottebrock@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <200411160308.10451.michaelnottebrock@gmx.net> User-Agent: Mutt/1.5.6i Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 02:32:26 -0000 Yes you're right ! This sux ! What the hell is Intel claiming that I have a HTT capable CPU, but really I have only 1 core ! shell> sudo x86info -f x86info v1.12b. Dave Jones 2001-2003 Feedback to . Found 1 CPU -------------------------------------------------------------------------- Family: 15 Model: 2 Stepping: 9 Type: 0 Brand: 9 CPU Model: Pentium 4 (Northwood) [D1] Original OEM Processor name string: Intel(R) Pentium(R) 4 CPU 2.80GHz Feature flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflsh dtes acpi mmx fxsr sse sse2 selfsnoop ht acc pbe Extended feature flags: cntx-id Instruction TLB: 4K, 2MB or 4MB pages, fully associative, 128 entries. Data TLB: 4KB or 4MB pages, fully associative, 64 entries. L1 Data cache: Size: 8KB Sectored, 4-way associative. line size=64 bytes. No level 2 cache or no level 3 cache if valid 2nd level cache. Instruction trace cache: Size: 12K uOps 8-way associative. L2 unified cache: Size: 512KB Sectored, 8-way associative. line size=64 bytes. Number of logical processors supported within the physical package: 0 - aW 0n Tue, Nov 16, 2004 at 12:38:05PM +1030, Michael Nottebrock wrote: On Tuesday, 16. November 2004 02:41, Wilkinson, Alex wrote: > Is it possible to find out whether HTT is turned on in the BIOS without > having to reboot ? acpidump(8) ? > > It's just that I notice that I have a HTT capable CPU: > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS, HTT,TM,PBE> Not all CPUs that advertise 'HTT' do actually offer multiple logical processors. sysutils/x86info is a nice utility which can provide this information ... -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 03:10:08 2004 Return-Path: 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 76C7E16A4CE for ; Tue, 16 Nov 2004 03:10:08 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3888743D53 for ; Tue, 16 Nov 2004 03:10:08 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 2179E72DF4; Mon, 15 Nov 2004 19:10:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1F01772DD4; Mon, 15 Nov 2004 19:10:08 -0800 (PST) Date: Mon, 15 Nov 2004 19:10:08 -0800 (PST) From: Doug White To: Stephan Uphoff In-Reply-To: <1100277911.78635.480.camel@palm.tree.com> Message-ID: <20041115190644.X7416@carver.gumbysoft.com> References: <20041112141930.21592.qmail@web54607.mail.yahoo.com> <1100277911.78635.480.camel@palm.tree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Ketrien I. Saihr-Kesenchedra" cc: Nik Azim Azam cc: freebsd-current@freebsd.org Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 03:10:08 -0000 On Fri, 12 Nov 2004, Stephan Uphoff wrote: > On Fri, 2004-11-12 at 09:19, Nik Azim Azam wrote: > > Win2K Advanced Server works just fine here. > > The root cause seems to be a misunderstanding of the interrupt delivery > and buffering mechanism. The fix may take a few days since it probably > requires extensive changes to the IPI layer. [getting in late on this] Tomorrow I will have access to a Dell PowerEdge 6500 (4x500MHz) I can use to capture info or test patches. Or see if the bug reproduces there in the first place :) rwatson mumbled something about wanting to determine what triggered the prior IPI that the panic later trips over. I'll have to find a sutiable place to hide that information... -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 03:24:05 2004 Return-Path: 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 94F6E16A4CE for ; Tue, 16 Nov 2004 03:24:05 +0000 (GMT) Received: from omoikane.mb.skyweb.ca (omoikane.mb.skyweb.ca [64.42.246.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2741D43D45 for ; Tue, 16 Nov 2004 03:24:05 +0000 (GMT) (envelope-from mark@skyweb.ca) Received: by omoikane.mb.skyweb.ca (Postfix, from userid 1001) id 2DFF461D07; Mon, 15 Nov 2004 21:24:03 -0600 (CST) From: Mark Johnston To: current@freebsd.org, freebsd-cvs-summary@lists.enderunix.org Date: Mon, 15 Nov 2004 21:24:03 -0600 User-Agent: KMail/1.6.1 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200411152124.03359.mjohnston@skyweb.ca> Subject: cvs-src summary for November 8-15 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 03:24:05 -0000 FreeBSD cvs-src summary for 08/11/04 to 15/11/04 ++++++++++++++++++++++++++++++++++++++++++++++++ This is a regular weekly summary of FreeBSD's cutting-edge development. It is intended to help the FreeBSD community keep up with the fast-paced work going on in FreeBSD-CURRENT by distilling the deluge of data from the CVS mailing list into a (hopefully) easy-to-read newsletter. This newsletter is marked up in reStructuredText_, so any odd punctuation that you see is likely intended for the reST parser. .. _reStructuredText: http://docutils.sourceforge.net/rst.html You can get old summaries, and an HTML version of this one, at http://www.xl0.org/FreeBSD/. Please send any comments to Mark Johnston (mark at xl0.org). For Lukasz Dudek and Szymon Roczniak's Polish translations of these summaries, which may lag the English ones slightly, please see http://mocart.pinco.pl/FreeBSD/. .. contents:: ============ New features ============ Regression test enhancements ---------------------------- Nik Clayton (nik) enhanced the system regression tests, found in src/tools/regression, to use the "ok/not ok" output style that Perl's Test::Harness module supports. He also added .t files to be used with Perl's testing suite to run the tests. http://www.freebsd.org/cgi/mid.cgi?200411111947.iABJlt3N034088 Device vnode bypass on by default --------------------------------- Poul-Henning Kamp (phk) turned the device vnode bypass functionality mentioned `last week`_ on by default. You can disable it by setting vfs.devfs.fops=0 in /boot/loader.conf. .. _`last week`: http://excel.xl0.org/FreeBSD/08-11-04.html#device-vnode-bypass-added http://www.freebsd.org/cgi/mid.cgi?200411152211.iAFMB9YF016201 sf driver gets polling and ALTQ support --------------------------------------- Christian Brueffer (brueffer) committed support to the sf driver, for Adaptec AIC-6915 "Starfire"-based Ethernet cards, for device polling, allowing the kernel to poll the NIC rather than interrupting every time data is received. Later, he also added support for the ALTQ packet shaper to the driver. The polling patch was assisted by Ruslan Ermilof (ru), and the ALTQ patch written by Max Laier (mlaier). http://www.freebsd.org/cgi/mid.cgi?200411102304.iAAN4d85055590 http://www.freebsd.org/cgi/mid.cgi?200411121812.iACIC5Aw021346 NO_NIS knob added ----------------- Bjoern A. Zeeb (bz) added support for a NO_NIS knob when building the system. You can set NO_NIS in /etc/make.conf or while building the system to prevent YP/NIS support, which allows centralized management of authentication and other system files, from being compiled. This closes `PR 68303`_. .. _`PR 68303`: http://www.freebsd.org/cgi/query-pr.cgi?pr=68303 http://www.freebsd.org/cgi/mid.cgi?200411132040.iADKeWri018969 =============== Notable changes =============== Automatic read-write mounting of md* disks removed -------------------------------------------------- Poul-Henning Kamp (phk) removed a hack that had been in the mount code that would automatically remount a memory-loaded root filesystem as read-write, instead of read-only. If you were relying on this automatic remounting, you may need to add the command "/sbin/mount -u -o rw /dev/md0 /", or other appropriate mount incantation, to your startup scripts. http://www.freebsd.org/cgi/mid.cgi?200411100736.iAA7a9CT093469 AutoFS removed -------------- Mark Murray (markm) removed AutoFS, an alternate package for integrating automounting, at the author's request. It may return later. http://www.freebsd.org/cgi/mid.cgi?200411101954.iAAJsIQo040022 =================== Important bug fixes =================== Potential DoS in pppd fixed --------------------------- Xin Li (delphij) committed a fix to pppd, the PPP daemon, to a bug causing a denial-of-service vulnerability. This fix was adapted from DragonflyBSD, who in turn ported it from OpenBSD. The bug was initially reported by infamous41md at hotpop dot com. http://www.freebsd.org/cgi/mid.cgi?200411100549.iAA5nqXn089222 =============== Other bug fixes =============== Poul-Henning Kamp (phk) fixed a design problem in make that resulted in more processess being spawned than were desired. If make -j was used to run more than one concurrent subprocess, the submakes could run submakes of their own, creating more processes than specified. http://www.freebsd.org/cgi/mid.cgi?200411120858.iAC8w7ng088956 Robert Watson (rwatson) fixed a bug in the em driver, for Intel PRO/1000 Gigabit Ethernet cards, that would result in VLAN support breaking when the card was put into promiscuous mode. http://www.freebsd.org/cgi/mid.cgi?200411121103.iACB37ov092603 Gleb Smirnoff (glebius) fixed a bug in syslogd that could result in lost messages when under heavy load. The bug was reported by Chris Gabe in `PR 72366`_, and the fix was obtained from OpenBSD. .. _`PR 72366`: http://www.freebsd.org/cgi/query-pr.cgi?pr=72366 http://www.freebsd.org/cgi/mid.cgi?200411110939.iAB9d5xe096326 Robert Watson (rwatson) fixed a panic in the NFS code when working with some clients. The problem was reported with a Sun 3 and a Unixware client. This fix closes `PR 73208`_ and `PR 73807`_. .. _`PR 73208`: http://www.freebsd.org/cgi/query-pr.cgi?pr=73208 .. _`PR 73807`: http://www.freebsd.org/cgi/query-pr.cgi?pr=73807 http://www.freebsd.org/cgi/mid.cgi?200411112130.iABLUrZe044946 Hartmut Brandt (harti) fixed an interrupt handling bug in make that could cause a core dump. This closes `PR 29103`_. .. _`PR 29103`: http://www.freebsd.org/cgi/query-pr.cgi?pr=29103 http://www.freebsd.org/cgi/mid.cgi?200411120757.iAC7vHKI080512 From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 03:48:03 2004 Return-Path: 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 482FC16A4CE for ; Tue, 16 Nov 2004 03:48:03 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E534843D45 for ; Tue, 16 Nov 2004 03:48:01 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG3jnen027588; Mon, 15 Nov 2004 20:45:55 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 20:46:08 -0700 (MST) Message-Id: <20041115.204608.13771454.imp@bsdimp.com> To: alex.wilkinson@dsto.defence.gov.au From: "M. Warner Losh" In-Reply-To: <20041116022926.GB57056@squash.dsto.defence.gov.au> References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 03:48:03 -0000 In message: <20041116022926.GB57056@squash.dsto.defence.gov.au> "Wilkinson, Alex" writes: : Yes you're right ! This sux ! What the hell is Intel claiming that I have a : HTT capable CPU, but really I have only 1 core ! I seem to recall at the time HTT was introduced that you could put an HTT into a non-HTT ready mobo. Maybe that's what's happend? Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 03:48:28 2004 Return-Path: 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 4B4B816A4D1 for ; Tue, 16 Nov 2004 03:48:28 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 93D1843D46 for ; Tue, 16 Nov 2004 03:48:27 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG3igi3027572; Mon, 15 Nov 2004 20:44:42 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 15 Nov 2004 20:45:01 -0700 (MST) Message-Id: <20041115.204501.27780819.imp@bsdimp.com> To: ma@dt.e-technik.uni-dortmund.de From: "M. Warner Losh" In-Reply-To: References: <20041116002837.GE56252@squash.dsto.defence.gov.au> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 03:48:28 -0000 In message: Matthias Andree writes: : "Wilkinson, Alex" writes: : : > Robert, what is an NMI button ? : : A button - usually on server and high-availability hardware, : next to the RESET button. NMI is a non-maskable interrupt, : i. e. one that software cannot opt out of. Or you take a paperclip, and short out A1 and B1 together on the ISA bus. I have an old, cast off ISA card that I have rigged up in two ways. One: I have a switch, and two I have a one shot detector on the // port that also brings #IOCHK low and then high... Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 04:10:16 2004 Return-Path: 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 1467616A521 for ; Tue, 16 Nov 2004 04:10:16 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF2D243D3F for ; Tue, 16 Nov 2004 04:10:15 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAG4B3co002489; Mon, 15 Nov 2004 20:11:03 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAG4B3Qr002487; Mon, 15 Nov 2004 20:11:03 -0800 Date: Mon, 15 Nov 2004 20:11:03 -0800 From: Brooks Davis To: "M. Warner Losh" Message-ID: <20041116041103.GA28063@odin.ac.hmc.edu> References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> <20041115.204608.13771454.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="d6Gm4EdcadzBjdND" Content-Disposition: inline In-Reply-To: <20041115.204608.13771454.imp@bsdimp.com> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org cc: alex.wilkinson@dsto.defence.gov.au Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 04:10:16 -0000 --d6Gm4EdcadzBjdND Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 15, 2004 at 08:46:08PM -0700, M. Warner Losh wrote: > In message: <20041116022926.GB57056@squash.dsto.defence.gov.au> > "Wilkinson, Alex" writes: > : Yes you're right ! This sux ! What the hell is Intel claiming that I ha= ve a > : HTT capable CPU, but really I have only 1 core ! >=20 > I seem to recall at the time HTT was introduced that you could put an > HTT into a non-HTT ready mobo. Maybe that's what's happend? I think that's usually a BIOS issue, but not always. There are also some early P4s that set the HTT flag but only have one core. That's valid since all the flag means is that you have the extra instruction which says how many cores you have. I'm pretty sure that doens't apply to 2.8GHz CPUs though. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --d6Gm4EdcadzBjdND Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBmX3WXY6L6fI4GtQRAsF8AJwMJk4fbimRtZ5FFexOySDsks4npwCfVIQn +1CIJznhndhO5C67SIbugYw= =k9+G -----END PGP SIGNATURE----- --d6Gm4EdcadzBjdND-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 04:11:19 2004 Return-Path: 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 24E9F16A4CE for ; Tue, 16 Nov 2004 04:11:19 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D4F543D3F for ; Tue, 16 Nov 2004 04:11:18 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAG4DCDb023338; Mon, 15 Nov 2004 21:13:18 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41997E0B.6030604@freebsd.org> Date: Mon, 15 Nov 2004 21:11:55 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> In-Reply-To: <20041116022926.GB57056@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 04:11:19 -0000 Intel is claiming that your CPU has the registers that will let software easily find out how many logical cores you have. Scott Wilkinson, Alex wrote: > Yes you're right ! This sux ! What the hell is Intel claiming that I have a > HTT capable CPU, but really I have only 1 core ! > > > shell> sudo x86info -f > > x86info v1.12b. Dave Jones 2001-2003 > Feedback to . > > Found 1 CPU > -------------------------------------------------------------------------- > Family: 15 Model: 2 Stepping: 9 Type: 0 Brand: 9 > CPU Model: Pentium 4 (Northwood) [D1] Original OEM > Processor name string: Intel(R) Pentium(R) 4 CPU 2.80GHz > > Feature flags: > fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 > clflsh dtes acpi mmx fxsr sse sse2 selfsnoop ht acc pbe > Extended feature flags: > cntx-id > Instruction TLB: 4K, 2MB or 4MB pages, fully associative, 128 entries. > Data TLB: 4KB or 4MB pages, fully associative, 64 entries. > L1 Data cache: > Size: 8KB Sectored, 4-way associative. > line size=64 bytes. > No level 2 cache or no level 3 cache if valid 2nd level cache. > Instruction trace cache: > Size: 12K uOps 8-way associative. > L2 unified cache: > Size: 512KB Sectored, 8-way associative. > line size=64 bytes. > Number of logical processors supported within the physical package: 0 > > - aW > > > 0n Tue, Nov 16, 2004 at 12:38:05PM +1030, Michael Nottebrock wrote: > > On Tuesday, 16. November 2004 02:41, Wilkinson, Alex wrote: > > Is it possible to find out whether HTT is turned on in the BIOS > without > > having to reboot ? acpidump(8) ? > > > > It's just that I notice that I have a HTT capable CPU: > > > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > > > > Features=0xbfebfbff ,MC > >A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS, HTT,TM,PBE> > > Not all CPUs that advertise 'HTT' do actually offer multiple logical > processors. sysutils/x86info is a nice utility which can provide this > information ... > > -- > ,_, | Michael Nottebrock | lofi@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.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" From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 04:24:33 2004 Return-Path: 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 E7FA916A4CE for ; Tue, 16 Nov 2004 04:24:33 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BC8F43D46 for ; Tue, 16 Nov 2004 04:24:33 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAG4QTkX023393; Mon, 15 Nov 2004 21:26:29 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41998127.5090506@freebsd.org> Date: Mon, 15 Nov 2004 21:25:11 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "M. Warner Losh" References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> <20041115.204608.13771454.imp@bsdimp.com> In-Reply-To: <20041115.204608.13771454.imp@bsdimp.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: alex.wilkinson@dsto.defence.gov.au Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 04:24:34 -0000 M. Warner Losh wrote: > In message: <20041116022926.GB57056@squash.dsto.defence.gov.au> > "Wilkinson, Alex" writes: > : Yes you're right ! This sux ! What the hell is Intel claiming that I have a > : HTT capable CPU, but really I have only 1 core ! > > I seem to recall at the time HTT was introduced that you could put an > HTT into a non-HTT ready mobo. Maybe that's what's happend? > > Warner The HTT flag in the CPUID word only says that the CPU supports the MSRs that tell you how many logical cores are in the CPU. A value of 1 in these registers is perfectly acceptable, and doesn't mean that Intel is ripping you off or that your BIOS is wrong or whatever. This really needs to be made into a FAQ, I guess. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 04:52:31 2004 Return-Path: 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 993E816A4CE for ; Tue, 16 Nov 2004 04:52:31 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id CEA2343D39 for ; Tue, 16 Nov 2004 04:52:25 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG4pNZg007121 for ; Tue, 16 Nov 2004 15:21:23 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 15:22:14 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG4mIh14542 for ; Tue, 16 Nov 2004 15:18:18 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDNB37; Tue, 16 Nov 2004 15:18:11 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG4n70q057897 for ; Tue, 16 Nov 2004 15:19:07 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG4n7t0057896 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 15:19:07 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 15:19:06 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116044906.GC57615@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> <20041115.204608.13771454.imp@bsdimp.com> <41998127.5090506@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <41998127.5090506@freebsd.org> User-Agent: Mutt/1.5.6i Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 04:52:31 -0000 Cool, thanks Scott. Question: What is an MSR ? [I'm suspecting the R is 'Register']. - aW 0n Mon, Nov 15, 2004 at 09:25:11PM -0700, Scott Long wrote: M. Warner Losh wrote: >In message: <20041116022926.GB57056@squash.dsto.defence.gov.au> > "Wilkinson, Alex" writes: >: Yes you're right ! This sux ! What the hell is Intel claiming that I >have a >: HTT capable CPU, but really I have only 1 core ! > >I seem to recall at the time HTT was introduced that you could put an >HTT into a non-HTT ready mobo. Maybe that's what's happend? > >Warner The HTT flag in the CPUID word only says that the CPU supports the MSRs that tell you how many logical cores are in the CPU. A value of 1 in these registers is perfectly acceptable, and doesn't mean that Intel is ripping you off or that your BIOS is wrong or whatever. This really needs to be made into a FAQ, I guess. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 05:02:20 2004 Return-Path: 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 2497F16A4CE for ; Tue, 16 Nov 2004 05:02:20 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id BABA543D48 for ; Tue, 16 Nov 2004 05:02:19 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAG54Lq1023473; Mon, 15 Nov 2004 22:04:22 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41998A08.8000700@freebsd.org> Date: Mon, 15 Nov 2004 22:03:04 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <200411160308.10451.michaelnottebrock@gmx.net> <20041116022926.GB57056@squash.dsto.defence.gov.au> <20041115.204608.13771454.imp@bsdimp.com> <41998127.5090506@freebsd.org> <20041116044906.GC57615@squash.dsto.defence.gov.au> In-Reply-To: <20041116044906.GC57615@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 05:02:20 -0000 Wilkinson, Alex wrote: > Cool, thanks Scott. > > Question: What is an MSR ? [I'm suspecting the R is 'Register']. > > - aW A Model Specific Register. They are registers within the CPU. Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 05:06:49 2004 Return-Path: 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 E4B7116A4CE for ; Tue, 16 Nov 2004 05:06:49 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id E1DF443D31 for ; Tue, 16 Nov 2004 05:06:48 +0000 (GMT) (envelope-from michaelnottebrock@gmx.net) Received: (qmail 29659 invoked by uid 65534); 16 Nov 2004 05:06:47 -0000 Received: from pD9E24053.dip.t-dialin.net (EHLO lofi.dyndns.org) (217.226.64.83) by mail.gmx.net (mp019) with SMTP; 16 Nov 2004 06:06:47 +0100 X-Authenticated: #443188 Received: from [192.168.8.4] (lofi@kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.10/8.12.10) with ESMTP id iAG56epa027754 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 16 Nov 2004 06:06:41 +0100 (CET) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: freebsd-current@freebsd.org Date: Tue, 16 Nov 2004 06:06:32 +0100 User-Agent: KMail/1.7 References: <200411160308.10451.michaelnottebrock@gmx.net> <20041115.204608.13771454.imp@bsdimp.com> <20041116041103.GA28063@odin.ac.hmc.edu> In-Reply-To: <20041116041103.GA28063@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2005381.ZneMmbErJP"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411160606.39998.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: alex.wilkinson@dsto.defence.gov.au cc: "M. Warner Losh" Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 05:06:50 -0000 --nextPart2005381.ZneMmbErJP Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday, 16. November 2004 05:11, Brooks Davis wrote: > There are also > some early P4s that set the HTT flag but only have one core. That's > valid since all the flag means is that you have the extra instruction > which says how many cores you have. I'm pretty sure that doens't apply > to 2.8GHz CPUs though. P4s without HTT are/were available in the 1.3-2.8 GHz range (HTT actually w= as=20 introduced quite late in non-Xeon P4s). =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2005381.ZneMmbErJP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmYrfXhc68WspdLARAnSgAJ9fDwcJIPUd9WoANeCo+bEb1RxbbgCgmWfn Xkik4egPvQGJFFbV7hCh1tg= =y4Us -----END PGP SIGNATURE----- --nextPart2005381.ZneMmbErJP-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 05:12:37 2004 Return-Path: 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 5B92116A4CE for ; Tue, 16 Nov 2004 05:12:37 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB6B243D41 for ; Tue, 16 Nov 2004 05:12:22 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG5BOZg009359 for ; Tue, 16 Nov 2004 15:41:24 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 15:42:15 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG56Bh28429 for ; Tue, 16 Nov 2004 15:36:11 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDNC3M; Tue, 16 Nov 2004 15:36:04 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG570K9057996 for ; Tue, 16 Nov 2004 15:37:00 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG56xWZ057995 for current@freebsd.org; Tue, 16 Nov 2004 15:36:59 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 15:36:59 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041116050659.GD57615@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <20041115142036.D53544@cvs.imp.ch> <20041116002837.GE56252@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 05:12:37 -0000 Okay, trying to see the purpose of this button ? Why have an NMI button to break into DDB when you can just use CTRL-ALT-ESC ? - aW 0n Tue, Nov 16, 2004 at 01:43:35AM +0100, Matthias Andree wrote: "Wilkinson, Alex" writes: > Robert, what is an NMI button ? A button - usually on server and high-availability hardware, next to the RESET button. NMI is a non-maskable interrupt, i. e. one that software cannot opt out of. The serious part of this mail ends in this line. On your Commodore 64, it's labeled "RESTORE". :-) -- Matthias Andree _______________________________________________ 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 16 05:24:54 2004 Return-Path: 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 7B2C316A4CE for ; Tue, 16 Nov 2004 05:24:54 +0000 (GMT) Received: from vbook.fbsd.ru (user142.hovrino.net [82.179.232.142]) by mx1.FreeBSD.org (Postfix) with ESMTP id C48F243D2D for ; Tue, 16 Nov 2004 05:24:53 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTvpc-0001By-3F; Tue, 16 Nov 2004 08:24:44 +0300 From: Vladimir Grebenschikov To: "M. Warner Losh" In-Reply-To: <20041115.153557.128618461.imp@bsdimp.com> References: <20041025.212820.60925870.imp@bsdimp.com> <1100557699.1098.16.camel@localhost> <20041115.153557.128618461.imp@bsdimp.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 16 Nov 2004 08:24:43 +0300 Message-Id: <1100582683.1098.18.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "current@freebsd.org" cc: mike@sentex.net Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 05:24:54 -0000 =F7 =D0=CE, 15/11/2004 =D7 15:35 -0700, M. Warner Losh =D0=C9=DB=C5=D4: > Can you also provide >=20 > pciconf -r pci2:5:0 0:0xff Please: # pciconf -r pci2:5:0 0:0xff 04751180 02100007 060700b8 00824000 d0203000 020000dc 40040302 fffff000=20 00000000 fffff000 00000000 fffffffc 00000000 fffffffc 00000000 07000109=20 8140104d 00000001 00000000 00000000 00000000 00000000 00000000 00000000=20 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000=20 24a00001 00000000 04630463 00000000 00000000 00000000 00000000 00000000=20 80000046 00000000 00000000 00000000 00000000 00000000 00000000 00000000=20 8140104d 00000000 00000000 00000000 00000000 00000000 00000000 fe0a0001=20 24c04000 00000000 00000000 00000000 00000000 00000000 00000000 00000000=20 # > Warner --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 05:27:30 2004 Return-Path: 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 C054F16A4CE for ; Tue, 16 Nov 2004 05:27:30 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D600443D49 for ; Tue, 16 Nov 2004 05:27:29 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG5QVZg011038 for ; Tue, 16 Nov 2004 15:56:31 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 15:57:22 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG5Mlh09145 for ; Tue, 16 Nov 2004 15:52:47 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDNDMW; Tue, 16 Nov 2004 15:52:40 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG5NaPj058076 for ; Tue, 16 Nov 2004 15:53:36 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG5NaUT058075 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 15:53:36 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 15:53:36 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116052336.GF57615@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <92d8c1ed0411150817395e10d0@mail.gmail.com> <200411151614.21983.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <200411151614.21983.jhb@FreeBSD.org> User-Agent: Mutt/1.5.6i Subject: Re: Warning: Pentium 4 CPU: PSE disabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 05:27:30 -0000 John, what is the benefit of Page Size Extensions ? - aW 0n Mon, Nov 15, 2004 at 04:14:21PM -0500, John Baldwin wrote: On Monday 15 November 2004 11:17 am, Kaspars wrote: > Hi all, > > I just installed new pc with FreeBSD 4.10 and updated to FreeBSD > 4.10-RELEASE-p3 and found in dmesg: > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > real memory = 520028160 (507840K bytes) > avail memory = 502751232 (490968K bytes) > Preloaded elf kernel "kernel" at 0xc0329000. > Warning: Pentium 4 CPU: PSE disabled > Pentium Pro MTRR support enabled > md0: Malloc disk > > Tryed to google, tryed in ircnet #freebsd but nobody can`t say what > realy wrong :) There is a bug in how some of the Pentium4 chips handle PSE that 5.x works around already. However, the fix was too large to backport to 4.x, so instead the PSE feature is turned off in 4.x. I wouldn't worry about it, your machine will still work fine without PSE. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.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" From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 06:15:41 2004 Return-Path: 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 71A9316A4CE for ; Tue, 16 Nov 2004 06:15:41 +0000 (GMT) Received: from dglawrence.com (c-24-21-223-117.client.comcast.net [24.21.223.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28A4F43D1F for ; Tue, 16 Nov 2004 06:15:41 +0000 (GMT) (envelope-from dg@dglawrence.com) Received: from ncore.dglawrence.com (localhost [127.0.0.1]) by dglawrence.com (8.13.1/8.13.1) with ESMTP id iAG6FeQw023148 for ; Mon, 15 Nov 2004 22:15:40 -0800 (PST) (envelope-from dg@dglawrence.com) Received: (from dg@localhost) by ncore.dglawrence.com (8.13.1/8.13.1/Submit) id iAG6Fe4P023147 for current@freebsd.org; Mon, 15 Nov 2004 22:15:40 -0800 (PST) (envelope-from dg@dglawrence.com) Date: Mon, 15 Nov 2004 22:15:40 -0800 From: "David G. Lawrence" To: current@freebsd.org Message-ID: <20041116061540.GC3411@ncore.dglawrence.com> References: <20041115142036.D53544@cvs.imp.ch> <20041116002837.GE56252@squash.dsto.defence.gov.au> <20041116050659.GD57615@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041116050659.GD57615@squash.dsto.defence.gov.au> Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 06:15:41 -0000 > Okay, trying to see the purpose of this button ? > > Why have an NMI button to break into DDB when you can just use CTRL-ALT-ESC ? NMI is "Non Maskable Interrupt", which means that it cannot be blocked by the OS. Keyboard interrupts can be blocked (masked), and thus may not work under some conditions - especially while the kernel is already processing an interrupt. -DG David G. Lawrence President Download Technologies, Inc. - http://www.downloadtech.com - (866) 399 8500 TeraSolutions, Inc. - http://www.terasolutions.com - (888) 346 7175 The FreeBSD Project - http://www.freebsd.org Pave the road of life with opportunities. From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 06:27:22 2004 Return-Path: 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 14FAB16A4CE for ; Tue, 16 Nov 2004 06:27:22 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 56A9843D31 for ; Tue, 16 Nov 2004 06:27:21 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAG6R9c9037415; Tue, 16 Nov 2004 07:27:12 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Wilkinson, Alex" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Nov 2004 10:41:46 +1030." <20041116001146.GB56252@squash.dsto.defence.gov.au> Date: Tue, 16 Nov 2004 07:27:09 +0100 Message-ID: <37414.1100586429@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: [HEADSUP] vnode bypass for devices: "ON" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 06:27:22 -0000 In message <20041116001146.GB56252@squash.dsto.defence.gov.au>, "Wilkinson, Ale x" writes: >Do u mind explaining what this actually means ? > >I'm "assuming" we are now by-passing the vnode layer for performance reasons ? yes. -- 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 16 06:27:22 2004 Return-Path: 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 3F8A516A4CE for ; Tue, 16 Nov 2004 06:27:22 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D84943D39 for ; Tue, 16 Nov 2004 06:27:21 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAG6TOEW023665; Mon, 15 Nov 2004 23:29:24 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <41999DF6.4000405@freebsd.org> Date: Mon, 15 Nov 2004 23:28:06 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <92d8c1ed0411150817395e10d0@mail.gmail.com> <200411151614.21983.jhb@FreeBSD.org> <20041116052336.GF57615@squash.dsto.defence.gov.au> In-Reply-To: <20041116052336.GF57615@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org Subject: Re: Warning: Pentium 4 CPU: PSE disabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 06:27:22 -0000 PSE allows you to map 4MB of memory into a single page table entry instead of just 4KB. This is good when you have a lot of data that operates in the same address space and doesn't need to be swapped out to disk. It's also more efficient for the CPU since only one TLB cache entry is needed for the 4MB chunk instead of 1024 4KB entries. Where this comes in really handy is with mapping the kernel onto a single 4MB PSE page, since you know that it will never be swapped out and you don't want to pollute the 4KB TLB cache with kernel page entries. So, consider it an optimization, but not a requirement for operation. Scott Wilkinson, Alex wrote: > John, what is the benefit of Page Size Extensions ? > > - aW > > 0n Mon, Nov 15, 2004 at 04:14:21PM -0500, John Baldwin wrote: > > On Monday 15 November 2004 11:17 am, Kaspars wrote: > > Hi all, > > > > I just installed new pc with FreeBSD 4.10 and updated to FreeBSD > > 4.10-RELEASE-p3 and found in dmesg: > > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbff >A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Hyperthreading: 2 logical CPUs > > real memory = 520028160 (507840K bytes) > > avail memory = 502751232 (490968K bytes) > > Preloaded elf kernel "kernel" at 0xc0329000. > > Warning: Pentium 4 CPU: PSE disabled > > Pentium Pro MTRR support enabled > > md0: Malloc disk > > > > Tryed to google, tryed in ircnet #freebsd but nobody can`t say what > > realy wrong :) > > There is a bug in how some of the Pentium4 chips handle PSE that 5.x works > around already. However, the fix was too large to backport to 4.x, so > instead the PSE feature is turned off in 4.x. I wouldn't worry about it, > your machine will still work fine without PSE. > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.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" > > _______________________________________________ > 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 16 06:27:28 2004 Return-Path: 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 35AFA16A4FE for ; Tue, 16 Nov 2004 06:27:28 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24A6C43D1F for ; Tue, 16 Nov 2004 06:27:25 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG6QQZg017056 for ; Tue, 16 Nov 2004 16:56:26 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 16:57:18 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG6NNh30375 for ; Tue, 16 Nov 2004 16:53:24 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDNGFT; Tue, 16 Nov 2004 16:53:16 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG6OCK4058382 for ; Tue, 16 Nov 2004 16:54:12 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG6OCkh058381 for current@freebsd.org; Tue, 16 Nov 2004 16:54:12 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 16:54:12 +1030 From: "Wilkinson, Alex" To: current@freebsd.org Message-ID: <20041116062412.GD58198@squash.dsto.defence.gov.au> Mail-Followup-To: current@freebsd.org References: <4197DB02.8050601@elischer.org> <419865B9.8010205@elischer.org> <20041115093826.GA92911@cell.sick.ru> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20041115093826.GA92911@cell.sick.ru> User-Agent: Mutt/1.5.6i Subject: Re: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 06:27:28 -0000 how does one do a "binary search" ? - aW 0n Mon, Nov 15, 2004 at 12:38:26PM +0300, Gleb Smirnoff wrote: On Mon, Nov 15, 2004 at 12:15:53AM -0800, Julian Elischer wrote: J> Going back to 5.3RELEASE fixes it.. J> I have no clue as to the problem.. the system freezes absolutly J> from yesterday's RELENG_5 or doesn't fail. No debugger, no dump etc.. You need to do a binary search. A boring, but effective procedure :( -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE _______________________________________________ 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 16 06:36:28 2004 Return-Path: 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 8405616A4CE for ; Tue, 16 Nov 2004 06:36:28 +0000 (GMT) Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F0AD43D31 for ; Tue, 16 Nov 2004 06:36:25 +0000 (GMT) (envelope-from PeterJeremy@optushome.com.au) Received: from cirb503493.alcatel.com.au (c211-30-75-229.belrs2.nsw.optusnet.com.au [211.30.75.229]) iAG6a1ht021401 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Tue, 16 Nov 2004 17:36:16 +1100 Received: from cirb503493.alcatel.com.au (localhost.alcatel.com.au [127.0.0.1])iAG6ZnxP034893 for ; Tue, 16 Nov 2004 17:35:54 +1100 (EST) (envelope-from pjeremy@cirb503493.alcatel.com.au) Received: (from pjeremy@localhost) by cirb503493.alcatel.com.au (8.12.10/8.12.9/Submit) id iAG6Zl71034892 for current@freebsd.org; Tue, 16 Nov 2004 17:35:47 +1100 (EST) (envelope-from pjeremy) Date: Tue, 16 Nov 2004 17:35:47 +1100 From: Peter Jeremy To: current@freebsd.org Message-ID: <20041116063547.GR79646@cirb503493.alcatel.com.au> References: <20041115142036.D53544@cvs.imp.ch> <20041116002837.GE56252@squash.dsto.defence.gov.au> <20041116050659.GD57615@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041116050659.GD57615@squash.dsto.defence.gov.au> User-Agent: Mutt/1.4.2i Subject: Re: Deadlock problems with 'kill PID' on CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 06:36:28 -0000 On Tue, 2004-Nov-16 15:36:59 +1030, Wilkinson, Alex wrote: >Why have an NMI button to break into DDB when you can just use CTRL-ALT-ESC ? For when Ctrl-Alt-Esc doesn't work. Ctrl-Alt-Esc relies on the system being healthy enough to be processing keyboard interrupts. -- Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:27:29 2004 Return-Path: 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 2F0E316A4CE for ; Tue, 16 Nov 2004 07:27:29 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1967F43D1F for ; Tue, 16 Nov 2004 07:27:28 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAG7QSZg021616 for ; Tue, 16 Nov 2004 17:56:28 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Tue, 16 Nov 2004 17:57:16 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAG7KCh20802 for ; Tue, 16 Nov 2004 17:50:12 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDN2HA; Tue, 16 Nov 2004 17:50:05 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAG7L14c058669 for ; Tue, 16 Nov 2004 17:51:01 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAG7L1eA058668 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 17:51:01 +1030 (CST) (envelope-from wilkinsa) Date: Tue, 16 Nov 2004 17:51:01 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041116072101.GJ58198@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <92d8c1ed0411150817395e10d0@mail.gmail.com> <200411151614.21983.jhb@FreeBSD.org> <20041116052336.GF57615@squash.dsto.defence.gov.au> <41999DF6.4000405@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <41999DF6.4000405@freebsd.org> User-Agent: Mutt/1.5.6i Subject: Re: Warning: Pentium 4 CPU: PSE disabled X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:27:29 -0000 Thanks Scott, -aW 0n Mon, Nov 15, 2004 at 11:28:06PM -0700, Scott Long wrote: PSE allows you to map 4MB of memory into a single page table entry instead of just 4KB. This is good when you have a lot of data that operates in the same address space and doesn't need to be swapped out to disk. It's also more efficient for the CPU since only one TLB cache entry is needed for the 4MB chunk instead of 1024 4KB entries. Where this comes in really handy is with mapping the kernel onto a single 4MB PSE page, since you know that it will never be swapped out and you don't want to pollute the 4KB TLB cache with kernel page entries. So, consider it an optimization, but not a requirement for operation. Scott Wilkinson, Alex wrote: >John, what is the benefit of Page Size Extensions ? > > - aW > > 0n Mon, Nov 15, 2004 at 04:14:21PM -0500, John Baldwin wrote: > > On Monday 15 November 2004 11:17 am, Kaspars wrote: > > Hi all, > > > > I just installed new pc with FreeBSD 4.10 and updated to FreeBSD > > 4.10-RELEASE-p3 and found in dmesg: > > CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU) > > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > > Features=0xbfebfbff >A,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > Hyperthreading: 2 logical CPUs > > real memory = 520028160 (507840K bytes) > > avail memory = 502751232 (490968K bytes) > > Preloaded elf kernel "kernel" at 0xc0329000. > > Warning: Pentium 4 CPU: PSE disabled > > Pentium Pro MTRR support enabled > > md0: Malloc disk > > > > Tryed to google, tryed in ircnet #freebsd but nobody can`t say what > > realy wrong :) > > There is a bug in how some of the Pentium4 chips handle PSE that 5.x > works around already. However, the fix was too large to backport to > 4.x, so instead the PSE feature is turned off in 4.x. I wouldn't > worry about it, your machine will still work fine without PSE. > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.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" > >_______________________________________________ >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 16 07:35:56 2004 Return-Path: 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 D799F16A4D1 for ; Tue, 16 Nov 2004 07:35:56 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77ECB43D45 for ; Tue, 16 Nov 2004 07:35:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAG7Xadw030017; Tue, 16 Nov 2004 00:33:36 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 16 Nov 2004 00:33:55 -0700 (MST) Message-Id: <20041116.003355.22956581.imp@bsdimp.com> To: vova@sw.ru From: "M. Warner Losh" In-Reply-To: <1100582683.1098.18.camel@localhost> References: <1100557699.1098.16.camel@localhost> <20041115.153557.128618461.imp@bsdimp.com> <1100582683.1098.18.camel@localhost> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable cc: current@freebsd.org cc: mike@sentex.net Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:35:57 -0000 In message: <1100582683.1098.18.camel@localhost> Vladimir Grebenschikov writes: : =F7 =D0=CE, 15/11/2004 =D7 15:35 -0700, M. Warner Losh =D0=C9=DB=C5=D4= : : > Can you also provide : > = : > pciconf -r pci2:5:0 0:0xff : = : Please: : = : = : # pciconf -r pci2:5:0 0:0xff : 04751180 02100007 060700b8 00824000 : d0203000 020000dc 40040302 fffff000 = 02 is PRIBUS 03 is SECBUS 04 is SUBBUS From=20your previous mail, we know that fxp0 is on pci2. Since it really appears to be on the same bus as the cbb, one theory that I had is busted, I think. I'd thought that maybe there was a problem with how pccbb assigns the bus numbers. But unless I've misread something there, it looks like this isn't happening... Warner From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:36:11 2004 Return-Path: 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 202A016A4CE for ; Tue, 16 Nov 2004 07:36:11 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B39243D2D for ; Tue, 16 Nov 2004 07:36:10 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTxXe-0000G9-8H; Tue, 16 Nov 2004 10:14:18 +0300 From: Vladimir Grebenschikov To: "M. Warner Losh" In-Reply-To: <1100582683.1098.18.camel@localhost> References: <20041025.212820.60925870.imp@bsdimp.com> <1100557699.1098.16.camel@localhost> <20041115.153557.128618461.imp@bsdimp.com> <1100582683.1098.18.camel@localhost> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 16 Nov 2004 10:14:17 +0300 Message-Id: <1100589258.931.3.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "current@freebsd.org" cc: mike@sentex.net Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:36:11 -0000 =F7 =D7=D4, 16/11/2004 =D7 08:24 +0300, Vladimir Grebenschikov =D0=C9=DB=C5= =D4: > > Can you also provide > >=20 > > pciconf -r pci2:5:0 0:0xff Also I have found that kldunload if_fxp && kldload if_fxp fixes situation :( fxp0: port 0x4000-0x403f mem 0xd0200000-0xd0200fff irq 9 at device 8.0 on pci2 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 08:00:46:c8:45:b3 All reported output does not significant changed: % diff -u pciconf-lv.{before,after} \ diff -u devinfo-r.{before,after} \ diff -u pciconf-r_pci2:5:0_0:0xff.{before,after} --- devinfo-r.before Tue Nov 16 10:07:49 2004 +++ devinfo-r.after Tue Nov 16 10:09:45 2004 @@ -81,6 +81,8 @@ 0x4000-0x403f I/O memory addresses: 0xd0200000-0xd0200fff + miibus0 + inphy0 ndis0 I/O memory addresses: 0xd0201000-0xd0201fff % > Please: >=20 >=20 > # pciconf -r pci2:5:0 0:0xff > 04751180 02100007 060700b8 00824000 > d0203000 020000dc 40040302 fffff000=20 > 00000000 fffff000 00000000 fffffffc > 00000000 fffffffc 00000000 07000109=20 > 8140104d 00000001 00000000 00000000 > 00000000 00000000 00000000 00000000=20 > 00000000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000=20 > 24a00001 00000000 04630463 00000000 > 00000000 00000000 00000000 00000000=20 > 80000046 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000=20 > 8140104d 00000000 00000000 00000000 > 00000000 00000000 00000000 fe0a0001=20 > 24c04000 00000000 00000000 00000000 > 00000000 00000000 00000000 00000000=20 > # >=20 > > Warner --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:39:57 2004 Return-Path: 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 7B6FC16A4CE; Tue, 16 Nov 2004 07:39:57 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D9DE43D45; Tue, 16 Nov 2004 07:39:57 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.207] (vpn-client-207.marcuscom.com [10.2.1.207]) iAG7e1k2034328; Tue, 16 Nov 2004 02:40:01 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <4199AEC8.1070608@marcuscom.com> Date: Tue, 16 Nov 2004 02:39:52 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> <200411151424.49790.jhb@FreeBSD.org> In-Reply-To: <200411151424.49790.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: Robert Watson cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:39:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: | |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |> |>>Zitat von Joe Marcus Clarke : |>> |>>>I noticed the interrupt storm detection line in dmesg. In previous |>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>> |>>AFAIK the interrupt storm detection was removed (at least partially). |> |>s/removed/fixed so it doesn't give so many false positives/ |> |>(at least partially) ;-) |> |>Talk to jhb.. | | | Please try this patch out and let me know if it does any better: Yes, this patch makes a world of difference. The interrupt storm is still there, but the ata0 (irq 14) rate is down to 1480 per second, and the interrupt load is only ~2%. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBma7Ib2iPiv4Uz4cRAkYEAKCTgjJvkRbvbtYndCuYb3rMWTUyPACdFlZV CJFFhxLxnTVVawIr6gjqohw= =z8iV -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:39:57 2004 Return-Path: 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 7B6FC16A4CE; Tue, 16 Nov 2004 07:39:57 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0D9DE43D45; Tue, 16 Nov 2004 07:39:57 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.207] (vpn-client-207.marcuscom.com [10.2.1.207]) iAG7e1k2034328; Tue, 16 Nov 2004 02:40:01 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <4199AEC8.1070608@marcuscom.com> Date: Tue, 16 Nov 2004 02:39:52 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <1100176749.41935d6d12032@netchild.homeip.net> <20041111223705.GL582@hub.freebsd.org> <200411151424.49790.jhb@FreeBSD.org> In-Reply-To: <200411151424.49790.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: Robert Watson cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:39:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: | |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |> |>>Zitat von Joe Marcus Clarke : |>> |>>>I noticed the interrupt storm detection line in dmesg. In previous |>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>> |>>AFAIK the interrupt storm detection was removed (at least partially). |> |>s/removed/fixed so it doesn't give so many false positives/ |> |>(at least partially) ;-) |> |>Talk to jhb.. | | | Please try this patch out and let me know if it does any better: Yes, this patch makes a world of difference. The interrupt storm is still there, but the ata0 (irq 14) rate is down to 1480 per second, and the interrupt load is only ~2%. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBma7Ib2iPiv4Uz4cRAkYEAKCTgjJvkRbvbtYndCuYb3rMWTUyPACdFlZV CJFFhxLxnTVVawIr6gjqohw= =z8iV -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:41:20 2004 Return-Path: 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 2398516A4CE for ; Tue, 16 Nov 2004 07:41:20 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id B4B5143D53 for ; Tue, 16 Nov 2004 07:41:19 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD)) id 1CTxxm-0000KR-Tm; Tue, 16 Nov 2004 10:41:18 +0300 From: Vladimir Grebenschikov To: "M. Warner Losh" In-Reply-To: <20041116.003355.22956581.imp@bsdimp.com> References: <1100557699.1098.16.camel@localhost> <20041115.153557.128618461.imp@bsdimp.com> <1100582683.1098.18.camel@localhost> <20041116.003355.22956581.imp@bsdimp.com> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 16 Nov 2004 10:41:18 +0300 Message-Id: <1100590878.931.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: "current@freebsd.org" cc: mike@sentex.net Subject: Re: fxp does not work after upgrade to latest current (again) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:41:20 -0000 =F7 =D7=D4, 16/11/2004 =D7 00:33 -0700, M. Warner Losh =D0=C9=DB=C5=D4: > In message: <1100582683.1098.18.camel@localhost> > Vladimir Grebenschikov writes: > : =F7 =D0=CE, 15/11/2004 =D7 15:35 -0700, M. Warner Losh =D0=C9=DB=C5=D4: > : > Can you also provide > : >=20 > : > pciconf -r pci2:5:0 0:0xff > :=20 > : Please: > :=20 > :=20 > : # pciconf -r pci2:5:0 0:0xff > : 04751180 02100007 060700b8 00824000 > : d0203000 020000dc 40040302 fffff000=20 >=20 > 02 is PRIBUS > 03 is SECBUS > 04 is SUBBUS >=20 > >From your previous mail, we know that fxp0 is on pci2. Since it > really appears to be on the same bus as the cbb, one theory that I had > is busted, I think. I'd thought that maybe there was a problem with > how pccbb assigns the bus numbers. But unless I've misread something > there, it looks like this isn't happening... How I can help to fix situation ?=20 (kernel debugging, trying patches, everything else ?) Unfortunately I have no knowledge about cbb & buses interaction :( > Warner --=20 Vladimir B. Grebenschikov SWsoft Inc. vova@sw-soft.com From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:44:43 2004 Return-Path: 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 1DF2816A4CE for ; Tue, 16 Nov 2004 07:44:43 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 535FD43D2F for ; Tue, 16 Nov 2004 07:44:42 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iAG7iZEe096592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Nov 2004 10:44:36 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iAG7iYA5001395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 10:44:35 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iAG7iY9D001394; Tue, 16 Nov 2004 10:44:34 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Tue, 16 Nov 2004 10:44:33 +0300 From: Gleb Smirnoff To: "Wilkinson, Alex" Message-ID: <20041116074433.GB859@cell.sick.ru> References: <4197DB02.8050601@elischer.org> <419865B9.8010205@elischer.org> <20041115093826.GA92911@cell.sick.ru> <20041116062412.GD58198@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20041116062412.GD58198@squash.dsto.defence.gov.au> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: is RELENG_5 Borked? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:44:43 -0000 On Tue, Nov 16, 2004 at 04:54:12PM +1030, Wilkinson, Alex wrote: W> how does one do a "binary search" ? You do a recursive halving of time period when a particular problem appeared. For example you know that problem appeared before yesterday and day of 5.3-RELEASE. You obtain kernel sources for a middle of that period using cvsup or cvs, build kernel and test it. If problem persists you half the first half of the period and build another kernel. If problem disappaers on this kernel, then you half second half of the period. -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 07:46:26 2004 Return-Path: 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 21D4616A4CE for ; Tue, 16 Nov 2004 07:46:26 +0000 (GMT) Received: from relay.bestcom.ru (relay.bestcom.ru [217.72.144.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3D98B43D39 for ; Tue, 16 Nov 2004 07:46:25 +0000 (GMT) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (root@cell.sick.ru [217.72.144.68]) by relay.bestcom.ru (8.13.1/8.12.9) with ESMTP id iAG7kNlH096623 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 16 Nov 2004 10:46:24 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: from cell.sick.ru (glebius@localhost [127.0.0.1]) by cell.sick.ru (8.12.11/8.12.8) with ESMTP id iAG7kMDo001434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Nov 2004 10:46:22 +0300 (MSK) (envelope-from glebius@freebsd.org) Received: (from glebius@localhost) by cell.sick.ru (8.12.11/8.12.11/Submit) id iAG7kHSE001433; Tue, 16 Nov 2004 10:46:18 +0300 (MSK) (envelope-from glebius@freebsd.org) X-Authentication-Warning: cell.sick.ru: glebius set sender to glebius@freebsd.org using -f Date: Tue, 16 Nov 2004 10:46:17 +0300 From: Gleb Smirnoff To: Sean McNeil Message-ID: <20041116074617.GC859@cell.sick.ru> References: <1100556108.3025.1.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <1100556108.3025.1.camel@server.mcneil.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: clamd / ClamAV version devel-20041013, clamav-milter version 0.75l on 127.0.0.1 X-Virus-Status: Clean cc: current@freebsd.org Subject: Re: natd panics are back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 07:46:26 -0000 Sean, do you have core for this crash? On Mon, Nov 15, 2004 at 02:01:48PM -0800, Sean McNeil wrote: S> This was fixed a while ago and now it has made its way back into S> current: S> S> server# uname -a S> FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #58: Mon Nov 15 08:40:01 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 S> S> Nov 15 13:56:16 server kernel: Fatal trap 12: page fault while in kernel mode S> Nov 15 13:56:16 server kernel: fault virtual address = 0x18 S> Nov 15 13:56:16 server kernel: fault code = supervisor read, page S> not present S> Nov 15 13:56:16 server kernel: instruction pointer = 0x8:0xffffffff80354810Nov 15 13:56:16 server kernel: stack pointer = 0x10:0xffffffffb1c71620 S> Nov 15 13:56:16 server kernel: frame pointer = 0x10:0xffffffffb1c71680 S> Nov 15 13:56:16 server kernel: code segment = base 0x0, limit 0xfffff, type 0x1b S> Nov 15 13:56:16 server kernel: = DPL 0, pres 1, long 1, def32 0, gran 1 S> Nov 15 13:56:16 server kernel: processor eflags = interrupt enabled, resume, IOPL = 0 S> Nov 15 13:56:16 server kernel: current process = 212 (natd) S> Nov 15 13:56:16 server kernel: trap number = 12 S> Nov 15 13:56:16 server kernel: panic: page fault S> Nov 15 13:56:16 server kernel: KDB: enter: panic S> S> S> (gdb) l *0xffffffff80354810 S> 0xffffffff80354810 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). S> 368 MBUF_CHECKSLEEP(wait); S> 369 if (off == 0 && m->m_flags & M_PKTHDR) S> 370 copyhdr = 1; S> 371 while (off > 0) { S> 372 KASSERT(m != NULL, ("m_copym, offset > size of mbuf chain")); S> 373 if (off < m->m_len) S> 374 break; S> 375 off -= m->m_len; S> 376 m = m->m_next; S> 377 } S> -- Totus tuus, Glebius. GLEBIUS-RIPN GLEB-RIPE From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 08:02:26 2004 Return-Path: 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 7342216A4CE for ; Tue, 16 Nov 2004 08:02:26 +0000 (GMT) Received: from relay.pair.com (relay00.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id B364C43D1D for ; Tue, 16 Nov 2004 08:02:25 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 82711 invoked from network); 16 Nov 2004 08:02:24 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 16 Nov 2004 08:02:24 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAG82NKA008956; Tue, 16 Nov 2004 09:02:23 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAG82NgX008955; Tue, 16 Nov 2004 09:02:23 +0100 (CET) (envelope-from pho) Date: Tue, 16 Nov 2004 09:02:22 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041116080222.GA8900@peter.osted.lan> References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411151546.15533.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:02:26 -0000 On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: > On Friday 12 November 2004 07:33 am, Peter Holm wrote: > > GENERIC HEAD from Nov 11 08:05 UTC > > > > The following stack traces etc. was done before my first > > cup of coffee, so it's not so informative as it could have been :-( > > > > The test box appeared to have been frozen for more than 6 hours, > > but was pingable. > > > > http://www.holm.cc/stress/log/cons86.html > > A weak guess is that you have the system in some sort of livelock due to > fork()? Have you tried running with 'debug.mpsafevm=1' set from the loader? > Thank you for your reply. I have only seen this problem once. I will try to focus my testing effort on fork() to see if I can recreate the freeze. > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 08:16:50 2004 Return-Path: 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 3BEDA16A4CE for ; Tue, 16 Nov 2004 08:16:50 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 5FC7C43D41 for ; Tue, 16 Nov 2004 08:16:49 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 19910 invoked by uid 65534); 16 Nov 2004 08:16:48 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp016) with SMTP; 16 Nov 2004 09:16:48 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Tue, 16 Nov 2004 09:16:40 +0100 User-Agent: KMail/1.7 References: <38677.1100390114@critter.freebsd.dk> <20041115222618.GB579@unixpages.org> In-Reply-To: <20041115222618.GB579@unixpages.org> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7162852.ZKrXdzz5IJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411160916.47131.Emanuel.Strobl@gmx.net> cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:16:50 -0000 --nextPart7162852.ZKrXdzz5IJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Montag, 15. November 2004 23:26 schrieb Christian Brueffer: > On Sun, Nov 14, 2004 at 12:55:14AM +0100, Poul-Henning Kamp wrote: > > I have uploaded a snapshot patch of my p4 phk_bufwork branch relative > > to -current as of right now: > > > > http://phk.freebsd.dk/patch/phk_bufwork20041113.patch [...] > > > > Any and all benchmarking will be very welcome! > > I've been running this on my desktop for two days now with no ill > effects. At the moment I don't have time for benchmarking though. I'd love to do some benchmarks, but unfortunately I don't have a spare mach= ine=20 for 6-curr, but a 5.3-stable wich will go in production next week. Is it=20 possible to apply the framework to -stable? My intents are to make storage available for jails via regular files which = is=20 at the moment no option since performance gets horrible. If I understand=20 things right then this framework should improove performance dramatically=20 when e. g. copying /sys to /vnode_backed_md0. Thanks, =2DHarry > > - Christian --nextPart7162852.ZKrXdzz5IJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmbdvBylq0S4AzzwRAnKtAKCI1ay+XWWPTyaHSxImvpdSVLQxSACdGq0A nEoO2wpXdUcvOKZ059sgSIw= =qSyj -----END PGP SIGNATURE----- --nextPart7162852.ZKrXdzz5IJ-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 08:16:50 2004 Return-Path: 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 3CBFC16A4D0 for ; Tue, 16 Nov 2004 08:16:50 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 37BF743D31 for ; Tue, 16 Nov 2004 08:16:49 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 19910 invoked by uid 65534); 16 Nov 2004 08:16:48 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp016) with SMTP; 16 Nov 2004 09:16:48 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Tue, 16 Nov 2004 09:16:40 +0100 User-Agent: KMail/1.7 References: <38677.1100390114@critter.freebsd.dk> <20041115222618.GB579@unixpages.org> In-Reply-To: <20041115222618.GB579@unixpages.org> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7162852.ZKrXdzz5IJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411160916.47131.Emanuel.Strobl@gmx.net> cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:16:50 -0000 --nextPart7162852.ZKrXdzz5IJ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Montag, 15. November 2004 23:26 schrieb Christian Brueffer: > On Sun, Nov 14, 2004 at 12:55:14AM +0100, Poul-Henning Kamp wrote: > > I have uploaded a snapshot patch of my p4 phk_bufwork branch relative > > to -current as of right now: > > > > http://phk.freebsd.dk/patch/phk_bufwork20041113.patch [...] > > > > Any and all benchmarking will be very welcome! > > I've been running this on my desktop for two days now with no ill > effects. At the moment I don't have time for benchmarking though. I'd love to do some benchmarks, but unfortunately I don't have a spare mach= ine=20 for 6-curr, but a 5.3-stable wich will go in production next week. Is it=20 possible to apply the framework to -stable? My intents are to make storage available for jails via regular files which = is=20 at the moment no option since performance gets horrible. If I understand=20 things right then this framework should improove performance dramatically=20 when e. g. copying /sys to /vnode_backed_md0. Thanks, =2DHarry > > - Christian --nextPart7162852.ZKrXdzz5IJ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmbdvBylq0S4AzzwRAnKtAKCI1ay+XWWPTyaHSxImvpdSVLQxSACdGq0A nEoO2wpXdUcvOKZ059sgSIw= =qSyj -----END PGP SIGNATURE----- --nextPart7162852.ZKrXdzz5IJ-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 08:19:01 2004 Return-Path: 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 26B2A16A4D0; Tue, 16 Nov 2004 08:19:01 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BC2143D2F; Tue, 16 Nov 2004 08:19:00 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAG8Iu6D039262; Tue, 16 Nov 2004 09:18:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Emanuel Strobl From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Nov 2004 09:16:40 +0100." <200411160916.47131.Emanuel.Strobl@gmx.net> Date: Tue, 16 Nov 2004 09:18:56 +0100 Message-ID: <39261.1100593136@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:19:01 -0000 In message <200411160916.47131.Emanuel.Strobl@gmx.net>, Emanuel Strobl writes: >for 6-curr, but a 5.3-stable wich will go in production next week. Is it >possible to apply the framework to -stable? Not without some work. >My intents are to make storage available for jails via regular files which >is at the moment no option since performance gets horrible. If I understand >things right then this framework should improove performance dramatically >when e. g. copying /sys to /vnode_backed_md0. Not particularly. -- 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 16 08:19:01 2004 Return-Path: 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 26B2A16A4D0; Tue, 16 Nov 2004 08:19:01 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7BC2143D2F; Tue, 16 Nov 2004 08:19:00 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAG8Iu6D039262; Tue, 16 Nov 2004 09:18:56 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Emanuel Strobl From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Nov 2004 09:16:40 +0100." <200411160916.47131.Emanuel.Strobl@gmx.net> Date: Tue, 16 Nov 2004 09:18:56 +0100 Message-ID: <39261.1100593136@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org cc: current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:19:01 -0000 In message <200411160916.47131.Emanuel.Strobl@gmx.net>, Emanuel Strobl writes: >for 6-curr, but a 5.3-stable wich will go in production next week. Is it >possible to apply the framework to -stable? Not without some work. >My intents are to make storage available for jails via regular files which >is at the moment no option since performance gets horrible. If I understand >things right then this framework should improove performance dramatically >when e. g. copying /sys to /vnode_backed_md0. Not particularly. -- 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 16 08:28:30 2004 Return-Path: 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 D152816A4CE; Tue, 16 Nov 2004 08:28:30 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E7D843D45; Tue, 16 Nov 2004 08:28:30 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 009A4F1BB8; Tue, 16 Nov 2004 00:28:30 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 43929-03; Tue, 16 Nov 2004 00:28:23 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 02612F1819; Tue, 16 Nov 2004 00:28:22 -0800 (PST) From: Sean McNeil To: Gleb Smirnoff In-Reply-To: <20041116074617.GC859@cell.sick.ru> References: <1100556108.3025.1.camel@server.mcneil.com> <20041116074617.GC859@cell.sick.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-gECKhOnM59V4jvPj6Pwo" Date: Tue, 16 Nov 2004 00:28:22 -0800 Message-Id: <1100593702.44310.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: natd panics are back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 08:28:31 -0000 --=-gECKhOnM59V4jvPj6Pwo Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-11-16 at 10:46 +0300, Gleb Smirnoff wrote: > Sean, >=20 > do you have core for this crash? No, sorry. I just turned it on (I think). I will report if I get another reboot. All I have to do is set dumpdev=3D"AUTO" in /etc/rc.conf, right? I did that and then ran "/etc/rc.d/dumpon start". > On Mon, Nov 15, 2004 at 02:01:48PM -0800, Sean McNeil wrote: > S> This was fixed a while ago and now it has made its way back into > S> current: > S>=20 > S> server# uname -a > S> FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #58: Mon Nov= 15 08:40:01 PST 2004 root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64= amd64 > S>=20 > S> Nov 15 13:56:16 server kernel: Fatal trap 12: page fault while in kern= el mode > S> Nov 15 13:56:16 server kernel: fault virtual address =3D 0x18 > S> Nov 15 13:56:16 server kernel: fault code =3D supervisor= read, page > S> not present > S> Nov 15 13:56:16 server kernel: instruction pointer =3D 0x8:0xffff= ffff80354810Nov 15 13:56:16 server kernel: stack pointer =3D 0x1= 0:0xffffffffb1c71620 > S> Nov 15 13:56:16 server kernel: frame pointer =3D 0x10:0xfff= fffffb1c71680 > S> Nov 15 13:56:16 server kernel: code segment =3D base 0x0, = limit 0xfffff, type 0x1b > S> Nov 15 13:56:16 server kernel: =3D DPL 0, pres 1, long 1, def32 0, gra= n 1 > S> Nov 15 13:56:16 server kernel: processor eflags =3D interrupt enabled,= resume, IOPL =3D 0 > S> Nov 15 13:56:16 server kernel: current process =3D 212 (natd) > S> Nov 15 13:56:16 server kernel: trap number =3D 12 > S> Nov 15 13:56:16 server kernel: panic: page fault > S> Nov 15 13:56:16 server kernel: KDB: enter: panic > S>=20 > S>=20 > S> (gdb) l *0xffffffff80354810 > S> 0xffffffff80354810 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). > S> 368 MBUF_CHECKSLEEP(wait); > S> 369 if (off =3D=3D 0 && m->m_flags & M_PKTHDR) > S> 370 copyhdr =3D 1; > S> 371 while (off > 0) { > S> 372 KASSERT(m !=3D NULL, ("m_copym, offset > size = of mbuf chain")); > S> 373 if (off < m->m_len) > S> 374 break; > S> 375 off -=3D m->m_len; > S> 376 m =3D m->m_next; > S> 377 } > S>=20 >=20 >=20 >=20 --=-gECKhOnM59V4jvPj6Pwo Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmbomyQsGN30uGE4RAmZ2AKCBQEv7iAIdon7bvGsBaLm8bVFaagCgvYo4 1d/owv42XJWE22JkTXSIpyU= =KELD -----END PGP SIGNATURE----- --=-gECKhOnM59V4jvPj6Pwo-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 10:27:39 2004 Return-Path: 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 22C6C16A4CE for ; Tue, 16 Nov 2004 10:27:39 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AD9243D48 for ; Tue, 16 Nov 2004 10:27:38 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAGARNV4020426 for ; Tue, 16 Nov 2004 11:27:23 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <4199D60A.2010208@fer.hr> Date: Tue, 16 Nov 2004 11:27:22 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org References: <32653.1100366976@critter.freebsd.dk> In-Reply-To: <32653.1100366976@critter.freebsd.dk> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Passwd format? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 10:27:39 -0000 Poul-Henning Kamp wrote: >>It seems it's definitely NOT reusable in LDAP :( > > > Why not ? > > Cisco uses it in their routers, Juniper uses it in their routers. > It's used in Flash animations, FreeBSD systems and Linux systems > alike. As others pointed out, I'm probably wrong on that :) I thought LDAP passwords are just plain hashes of plaintext passwords, but it seems it's not so. Thanks, all! From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 12:58:10 2004 Return-Path: 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 E511016A4CE for ; Tue, 16 Nov 2004 12:58:10 +0000 (GMT) Received: from avscan1.sentex.ca (avscan1.sentex.ca [199.212.134.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47F5743D64 for ; Tue, 16 Nov 2004 12:58:10 +0000 (GMT) (envelope-from mike@sentex.net) Received: from localhost (localhost.sentex.ca [127.0.0.1]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCw4EO049558; Tue, 16 Nov 2004 07:58:04 -0500 (EST) (envelope-from mike@sentex.net) Received: from avscan1.sentex.ca ([127.0.0.1]) by localhost (avscan1.sentex.ca [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 49417-02; Tue, 16 Nov 2004 07:58:03 -0500 (EST) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by avscan1.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCw3Kr049540; Tue, 16 Nov 2004 07:58:03 -0500 (EST) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id iAGCvuoi051127; Tue, 16 Nov 2004 07:57:57 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <6.1.2.0.0.20041116080135.08dd3aa8@64.7.153.2> X-Sender: mdtpop@64.7.153.2 (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Tue, 16 Nov 2004 08:04:52 -0500 To: "Wilkinson, Alex" , current@freebsd.org From: Mike Tancsa In-Reply-To: <20041116001638.GC56252@squash.dsto.defence.gov.au> References: <20041112054741.GY40520@squash.dsto.defence.gov.au> <6.1.2.0.0.20041115075917.12684480@64.7.153.2> <20041116001638.GC56252@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at avscan1b Subject: Re: dealing with interupt storms ..... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 12:58:11 -0000 At 07:16 PM 15/11/2004, Wilkinson, Alex wrote: >No, it is UP. I would try disabling USB 2.0 and the sound in the BIOS if you are not using them. Also, try commenting out #device apic # I/O APIC in your kernel. On my machines, I can easily cause an interrupt storm by making a hardware device fire an interrupt that is not handled by the OS. Not sure if it will help you, but its worth a shot. ---Mike From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 20:44:07 2004 Return-Path: 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 B5F5B16A4D1 for ; Mon, 15 Nov 2004 20:44:07 +0000 (GMT) Received: from main.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0286D43D58 for ; Mon, 15 Nov 2004 20:44:07 +0000 (GMT) (envelope-from freebsd-current@m.gmane.org) Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1CTnhl-0005WR-00 for ; Mon, 15 Nov 2004 21:44:05 +0100 Received: from ti400720a080-9342.bb.online.no ([83.108.228.126]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Nov 2004 21:44:05 +0100 Received: from solskogen by ti400720a080-9342.bb.online.no with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 15 Nov 2004 21:44:05 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Christer Solskogen Date: Mon, 15 Nov 2004 21:44:02 +0100 Organization: jduB Lines: 14 Message-ID: References: <200411150126.20446.kstewart@owt.com> <200411151035.05819.kstewart@owt.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ti400720a080-9342.bb.online.no User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) Sender: news X-Mailman-Approved-At: Tue, 16 Nov 2004 13:22:37 +0000 Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 20:44:07 -0000 On Mon, 15 Nov 2004 10:35:05 -0800, Kent Stewart wrote: > Some of portupgrades features depend on INDEX.db. Okay, now I`m confused. We got INDEX(-5), and INDEX.db, What do they all do? :) wont these files contribute to bloat? We only need one of them, dont we? -- cso It's always the wrong time of the month. From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 23:46:03 2004 Return-Path: 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 2BD6616A4CE for ; Mon, 15 Nov 2004 23:46:03 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED32543D41 for ; Mon, 15 Nov 2004 23:46:02 +0000 (GMT) (envelope-from david.kleiner@gmail.com) Received: by mproxy.gmail.com with SMTP id w67so203771cwb for ; Mon, 15 Nov 2004 15:46:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=gSeuizUv5X44zwtuEBS0Bwy0JzxyuJsvOL75hne0Pv/PJgUCplaBw2CFRqbFF5Emmbi/GcZ+kjSVKbgzK1oFqyyll4WUbmjMmNcx1EtbydizRBOvT+JSV+DwudttNExgg1Akjm8M0sYqi48UKLar3Cwoas1+B6JcQ4XVNSePJ9c= Received: by 10.11.117.6 with SMTP id p6mr232048cwc; Mon, 15 Nov 2004 15:46:02 -0800 (PST) Received: by 10.11.117.23 with HTTP; Mon, 15 Nov 2004 15:46:02 -0800 (PST) Message-ID: Date: Mon, 15 Nov 2004 15:46:02 -0800 From: David Kleiner To: FreeBSD current mailing list , FreeBSD amd64 mailing list In-Reply-To: <20041115084705.GQ64152@marvin.riggiland.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041115070404.GP64152@marvin.riggiland.au> <20041115084705.GQ64152@marvin.riggiland.au> X-Mailman-Approved-At: Tue, 16 Nov 2004 13:22:37 +0000 Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Kleiner List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Nov 2004 23:46:03 -0000 Hi, Another data point. Having given up on getting a good sk NIC on a -current box, I installed a realtek rl-identified card. Here is what I get when trying to load up the if_sk.ko module: Nov 15 15:31:58 macropus kernel: skc0: port 0xa800-0xa8ff mem 0xfab00000-0xfab03fff irq 17 at device 10.0 on pci0 Nov 15 15:31:58 macropus kernel: skc0: Yukon Gigabit Ethernet 10/100/1000Base-T Adapter Nov 15 15:31:58 macropus kernel: skc0: PN: Yukon 88E8001 Nov 15 15:31:58 macropus kernel: skc0: EC: Rev. 1.3 Nov 15 15:31:58 macropus kernel: skc0: MN: Marvell Nov 15 15:31:58 macropus kernel: skc0: SN: AbCdEfG334454 Nov 15 15:31:58 macropus kernel: sk0: on skc0 Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers! Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12 This is an Asus "A8V Deluxe (v. 2.0) K8T800 No-WiFi/A" and 6.0-CURRENT built on Sat Nov 13 12:08:59 PST 2004. I also had it crashed while running a 700MB bittorrent transfer (stock py-bittorrent) but did not get a crash dump. The stack trace pointed at problem with networking and calling "panic" at the db> prompt wedged it solid. Thank you, David From owner-freebsd-current@FreeBSD.ORG Mon Nov 15 23:57:39 2004 Return-Path: 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 8423816A4CE; Mon, 15 Nov 2004 23:57:39 +0000 (GMT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 570C743D48; Mon, 15 Nov 2004 23:57:39 +0000 (GMT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id D7325148F3; Mon, 15 Nov 2004 17:57:38 -0600 (CST) Date: Mon, 15 Nov 2004 17:57:38 -0600 (CST) From: Mark Linimon X-X-Sender: linimon@pancho To: John Baldwin In-Reply-To: <200411151433.57236.jhb@FreeBSD.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Tue, 16 Nov 2004 13:22:37 +0000 cc: freebsd-current@FreeBSD.org cc: Robert Watson cc: Anurekh Saxena Subject: Re: kernel: return from interrupt X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 15 Nov 2004 23:57:39 -0000 On Mon, 15 Nov 2004, John Baldwin wrote: > NEEDRESCHED (albeit rather broken at the moment) is used to implement > preemptino of user threads. Are preemptinos the subatomic particles which, when they collide, create preemption events? mcl From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 14:54:47 2004 Return-Path: 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 DB0FB16A4CE for ; Tue, 16 Nov 2004 14:54:47 +0000 (GMT) Received: from gunfright.epcdirect.co.uk (gunfright.epcdirect.co.uk [195.10.242.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id 26EC943D5A for ; Tue, 16 Nov 2004 14:54:47 +0000 (GMT) (envelope-from bsd-current@epcdirect.co.uk) Received: from lfarr (l-farr.int.epcdirect.co.uk [192.168.6.200]) by gunfright.epcdirect.co.uk (Postfix) with ESMTP id EC71167E2B for ; Tue, 16 Nov 2004 14:54:45 +0000 (GMT) From: "Lawrence Farr" To: Date: Tue, 16 Nov 2004 14:54:44 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTLHGlWZh7yKLb7TG2O9AZvmYATAAAzw31A In-Reply-To: <20041115150229.U53544@cvs.imp.ch> Message-Id: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> Subject: Marvell SATA Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 14:54:48 -0000 Hello All, I have a Supermicro P4SCT+ with an onboard Marvell SATA controller, which also has the Adaptec Hostraid software raid functionality. Are there any patches to support the marvell controller as a plain controller anywhere? pciconf output if anyones interested: none4@pci2:4:0: class=0x010000 card=0x504111ab chip=0x504111ab rev=0x03 hdr=0x00 vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' device = '88SX504 4-port SATA I PCI-X Controller' class = mass storage subclass = SCSI From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 14:57:10 2004 Return-Path: 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 DE3CC16A4CE for ; Tue, 16 Nov 2004 14:57:10 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id 55BD043D1F for ; Tue, 16 Nov 2004 14:57:10 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 2239 invoked by uid 89); 16 Nov 2004 14:57:08 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 16 Nov 2004 14:57:08 -0000 Received: (qmail 2167 invoked by uid 89); 16 Nov 2004 14:57:07 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 16 Nov 2004 14:57:07 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id iAGEv55R006158; Tue, 16 Nov 2004 09:57:05 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Doug White In-Reply-To: <20041115190644.X7416@carver.gumbysoft.com> References: <20041112141930.21592.qmail@web54607.mail.yahoo.com> <1100277911.78635.480.camel@palm.tree.com> <20041115190644.X7416@carver.gumbysoft.com> Content-Type: text/plain Message-Id: <1100617025.2456.27.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 16 Nov 2004 09:57:05 -0500 Content-Transfer-Encoding: 7bit cc: "Ketrien I. Saihr-Kesenchedra" cc: Nik Azim Azam cc: freebsd-current@freebsd.org Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 14:57:11 -0000 On Mon, 2004-11-15 at 22:10, Doug White wrote: > On Fri, 12 Nov 2004, Stephan Uphoff wrote: > > > On Fri, 2004-11-12 at 09:19, Nik Azim Azam wrote: > > > Win2K Advanced Server works just fine here. > > > > The root cause seems to be a misunderstanding of the interrupt delivery > > and buffering mechanism. The fix may take a few days since it probably > > requires extensive changes to the IPI layer. > > [getting in late on this] > > Tomorrow I will have access to a Dell PowerEdge 6500 (4x500MHz) I can use > to capture info or test patches. Or see if the bug reproduces there in the > first place :) > > rwatson mumbled something about wanting to determine what triggered the > prior IPI that the panic later trips over. I'll have to find a sutiable > place to hide that information... Hopefully we can skip the debugging phase and go directly to the testing phase. However it would be helpful to know if the PowerEdge 6500 encounters any problems without the patch. The feedback I have received so far looks promising: Andy Farkas wrote: >> You can download the patch at: >> http://people.freebsd.org/~ups/ipi4_patch >> >> Any feedback is appreciated. >> >> Stephan >> > I have been hammering the box for the last 4 hours without > a panic. > > Without your patch, I could easily get a panic by boot -s then > fsck. I did this twice (without panic) using your patch. > > Without your patch, I would usually get a panic during make > buildworld -j4. So far with your patch its already done a > buildworld -j8, and its about to finish a buildworld -j4. > (2 buildworld in a row) > > This is good indeed. > > -andyf > > ps. ok to post to list. From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 16:06:57 2004 Return-Path: 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 C1FEF16A4CE for ; Tue, 16 Nov 2004 16:06:57 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E98643D2F for ; Tue, 16 Nov 2004 16:06:57 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from pcle2.cc.univie.ac.at (pcle2.cc.univie.ac.at [131.130.2.177]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAGG6oam215504 for ; Tue, 16 Nov 2004 17:06:52 +0100 Date: Tue, 16 Nov 2004 17:06:50 +0100 (CET) From: Lukas Ertl To: freebsd-current@FreeBSD.org Message-ID: <20041116170615.K92983@pcle2.cc.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx8 4248; Body=1 Fuz1=1 Fuz2=1 Subject: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:06:57 -0000 Hi, I'm having a rather specific problem with a -CURRENT from yesterday. My crashbox is an HP DL380 G3, with two Xeon processors, and one of the nice features of this box is the so called iLO service module, which offers remote console access via the net. Now, with the new kernel, this iLO remote console seems to lock up in the boot process at this point (from boot -v): acpi0: on motherboard acpi0: [MPSAFE] acpi0: Power Button (fixed) pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=00141166) pcibios: BIOS version 2.10 AcpiOsDerivePciId: bus 0 dev 0 func 0 ACPI timer: 0/5 0/5 0/6 The boot process itself finishes fine, and the 'real' console also works as expected. It's just that iLO console that locks up. A kernel from Nov 4 doesn't show this behaviour, so I somehow don't believe it's a hardware problem. Anyone out there with such a machine who can confirm this behaviour? cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 16:28:09 2004 Return-Path: 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 D549A16A4CE for ; Tue, 16 Nov 2004 16:28:09 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 70EFE43D2F for ; Tue, 16 Nov 2004 16:28:09 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 6264 invoked from network); 16 Nov 2004 16:28:09 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 16:28:08 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGGRue6082873; Tue, 16 Nov 2004 11:28:04 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 16 Nov 2004 10:57:16 -0500 User-Agent: KMail/1.6.2 References: <20041115043907.GI51636@squash.dsto.defence.gov.au> <20041116014121.GJ56252@squash.dsto.defence.gov.au> In-Reply-To: <20041116014121.GJ56252@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161057.16324.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: "Wilkinson, Alex" Subject: Re: Detection of HTT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:28:10 -0000 On Monday 15 November 2004 08:41 pm, Wilkinson, Alex wrote: > Is it possible to find out whether HTT is turned on in the BIOS without > having to reboot ? acpidump(8) ? > > It's just that I notice that I have a HTT capable CPU: > > CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2793.19-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > > Features=0xbfebfbffA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS, HTT,TM,PBE> > > And > > options SMP > > compiled into the kernel, > > but lack any message in /var/run/dmesg about HTT being enabled. FAQ (please search the archives in the future). The 'HTT' bit in the Features line just means that your processor implements the registers that enumerate logical processors. In other words, that feature means that we can ask the processor how many logical cores it has. It can claim to only have one core though. If it actually has multiple cores then we print the message during boot that you noticed in the other guy's dmesg. -- 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 16 16:28:19 2004 Return-Path: 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 3B3CA16A4D9 for ; Tue, 16 Nov 2004 16:28:19 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id D246543D5A for ; Tue, 16 Nov 2004 16:28:18 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4251 invoked from network); 16 Nov 2004 16:28:18 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 16:28:18 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGGRue7082873; Tue, 16 Nov 2004 11:28:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 16 Nov 2004 11:05:43 -0500 User-Agent: KMail/1.6.2 References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> In-Reply-To: <4199AEC8.1070608@marcuscom.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161105.43475.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: Kris Kennaway cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:28:19 -0000 On Tuesday 16 November 2004 02:39 am, Joe Marcus Clarke wrote: > John Baldwin wrote: > | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: > |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: > |>>Zitat von Joe Marcus Clarke : > |>>>I noticed the interrupt storm detection line in dmesg. In previous > |>>>builds, this worked, but it doesn't seem to be taking effect anymore. > |>> > |>>AFAIK the interrupt storm detection was removed (at least partially). > |> > |>s/removed/fixed so it doesn't give so many false positives/ > |> > |>(at least partially) ;-) > |> > |>Talk to jhb.. > | > | Please try this patch out and let me know if it does any better: > > Yes, this patch makes a world of difference. The interrupt storm is > still there, but the ata0 (irq 14) rate is down to 1480 per second, and > the interrupt load is only ~2%. Thanks. Can you tweak it a bit and see if it works even better if you put an #if 0 around the lines that read: + if (count > hz) { + storming = 0; + count = 0; + } else + count++; -- 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 16 16:28:19 2004 Return-Path: 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 5F8EB16A4D8 for ; Tue, 16 Nov 2004 16:28:19 +0000 (GMT) Received: from mail2.speakeasy.net (mail2.speakeasy.net [216.254.0.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A21A43D5C for ; Tue, 16 Nov 2004 16:28:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 4251 invoked from network); 16 Nov 2004 16:28:18 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 16 Nov 2004 16:28:18 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAGGRue7082873; Tue, 16 Nov 2004 11:28:07 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 16 Nov 2004 11:05:43 -0500 User-Agent: KMail/1.6.2 References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> In-Reply-To: <4199AEC8.1070608@marcuscom.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411161105.43475.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: current@FreeBSD.org cc: Kris Kennaway cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:28:19 -0000 On Tuesday 16 November 2004 02:39 am, Joe Marcus Clarke wrote: > John Baldwin wrote: > | On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: > |>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: > |>>Zitat von Joe Marcus Clarke : > |>>>I noticed the interrupt storm detection line in dmesg. In previous > |>>>builds, this worked, but it doesn't seem to be taking effect anymore. > |>> > |>>AFAIK the interrupt storm detection was removed (at least partially). > |> > |>s/removed/fixed so it doesn't give so many false positives/ > |> > |>(at least partially) ;-) > |> > |>Talk to jhb.. > | > | Please try this patch out and let me know if it does any better: > > Yes, this patch makes a world of difference. The interrupt storm is > still there, but the ata0 (irq 14) rate is down to 1480 per second, and > the interrupt load is only ~2%. Thanks. Can you tweak it a bit and see if it works even better if you put an #if 0 around the lines that read: + if (count > hz) { + storming = 0; + count = 0; + } else + count++; -- 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 16 16:30:22 2004 Return-Path: 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 968D116A4CE; Tue, 16 Nov 2004 16:30:22 +0000 (GMT) Received: from sv02.webonaut.com (kirk.webonaut.com [212.41.243.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id E219843D41; Tue, 16 Nov 2004 16:30:21 +0000 (GMT) (envelope-from klammer@webonaut.com) Received: from localhost (localhost [127.0.0.1]) by sv02.webonaut.com (Postfix) with ESMTP id 623FD76440; Tue, 16 Nov 2004 17:30:19 +0100 (CET) Received: from sv02.webonaut.com ([127.0.0.1]) by localhost (sv02.webonaut.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46017-08; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Received: from mail.webonaut.com (localhost [127.0.0.1]) by sv02.webonaut.com (Postfix) with SMTP id 82A7776449; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Received: from fw-axxess.ycn.com ([213.147.173.194]) (SquirrelMail authenticated user klammer) by mail.webonaut.com with HTTP; Tue, 16 Nov 2004 17:29:59 +0100 (CET) Message-ID: <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> Date: Tue, 16 Nov 2004 17:29:59 +0100 (CET) From: "Franz Klammer" To: "Mark Santcroos" User-Agent: SquirrelMail/1.4.2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 Importance: Normal X-Virus-Scanned: by amavisd-new at webonaut.com cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:30:22 -0000 Mark Santcroos: > If the following patch doesn't burn down too many systems, it will be > committed to HEAD in the near future. > does this patch also work with 5.3 or only with -CURRENT? i yes, i will try it: i miss the thermal zones and hope for a better suspend/resume support - currently is only S1 "working". franz. > http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz > > Mark From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 16:32:54 2004 Return-Path: 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 24FA416A4CE; Tue, 16 Nov 2004 16:32:54 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8758C43D49; Tue, 16 Nov 2004 16:32:53 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.2] (vpn-client-2.marcuscom.com [10.2.1.2]) iAGGWuxK039398; Tue, 16 Nov 2004 11:32:56 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <419A2BB0.7090302@marcuscom.com> Date: Tue, 16 Nov 2004 11:32:48 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> <200411161105.43475.jhb@FreeBSD.org> In-Reply-To: <200411161105.43475.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:32:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Tuesday 16 November 2004 02:39 am, Joe Marcus Clarke wrote: | |>John Baldwin wrote: |>| On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: |>|>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |>|>>Zitat von Joe Marcus Clarke : |>|>>>I noticed the interrupt storm detection line in dmesg. In previous |>|>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>|>> |>|>>AFAIK the interrupt storm detection was removed (at least partially). |>|> |>|>s/removed/fixed so it doesn't give so many false positives/ |>|> |>|>(at least partially) ;-) |>|> |>|>Talk to jhb.. |>| |>| Please try this patch out and let me know if it does any better: |> |>Yes, this patch makes a world of difference. The interrupt storm is |>still there, but the ata0 (irq 14) rate is down to 1480 per second, and |>the interrupt load is only ~2%. Thanks. | | | Can you tweak it a bit and see if it works even better if you put an #if 0 | around the lines that read: | | + if (count > hz) { | + storming = 0; | + count = 0; | + } else | + count++; | | Sure. I'll give this a shot as soon as my current package build is done. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmiuwb2iPiv4Uz4cRAk3oAJ426k42CTG58AAQZh1a25aalfpR6ACfRxBS 1HWfU44wNqXXi7I/mFlKFtA= =Gdnd -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 16:32:54 2004 Return-Path: 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 24FA416A4CE; Tue, 16 Nov 2004 16:32:54 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8758C43D49; Tue, 16 Nov 2004 16:32:53 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.2] (vpn-client-2.marcuscom.com [10.2.1.2]) iAGGWuxK039398; Tue, 16 Nov 2004 11:32:56 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <419A2BB0.7090302@marcuscom.com> Date: Tue, 16 Nov 2004 11:32:48 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> <200411161105.43475.jhb@FreeBSD.org> In-Reply-To: <200411161105.43475.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 16:32:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: | On Tuesday 16 November 2004 02:39 am, Joe Marcus Clarke wrote: | |>John Baldwin wrote: |>| On Thursday 11 November 2004 05:37 pm, Kris Kennaway wrote: |>|>On Thu, Nov 11, 2004 at 01:39:09PM +0100, Alexander@Leidinger.net wrote: |>|>>Zitat von Joe Marcus Clarke : |>|>>>I noticed the interrupt storm detection line in dmesg. In previous |>|>>>builds, this worked, but it doesn't seem to be taking effect anymore. |>|>> |>|>>AFAIK the interrupt storm detection was removed (at least partially). |>|> |>|>s/removed/fixed so it doesn't give so many false positives/ |>|> |>|>(at least partially) ;-) |>|> |>|>Talk to jhb.. |>| |>| Please try this patch out and let me know if it does any better: |> |>Yes, this patch makes a world of difference. The interrupt storm is |>still there, but the ata0 (irq 14) rate is down to 1480 per second, and |>the interrupt load is only ~2%. Thanks. | | | Can you tweak it a bit and see if it works even better if you put an #if 0 | around the lines that read: | | + if (count > hz) { | + storming = 0; | + count = 0; | + } else | + count++; | | Sure. I'll give this a shot as soon as my current package build is done. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmiuwb2iPiv4Uz4cRAk3oAJ426k42CTG58AAQZh1a25aalfpR6ACfRxBS 1HWfU44wNqXXi7I/mFlKFtA= =Gdnd -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 17:15:26 2004 Return-Path: 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 A8AAC16A4CE for ; Tue, 16 Nov 2004 17:15:26 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 568A943D5C for ; Tue, 16 Nov 2004 17:15:26 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so581343rns for ; Tue, 16 Nov 2004 09:15:22 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=R6HXRNqBWhfetAnqoZ31ylBIGJ6MJzOOyeysYEaLx08L1oEIJBaGrD9eJ0BZk7IZQXycSJVUZk4DBcsBoteKsWrEQ6wLsiVuV9jIR8SEeH9fgNEok0+mKnYMCrZd7I1GXCU6PWSb/XXrDvjPZA06wxyQb159nVbUtT0bJm5aAbI= Received: by 10.38.26.40 with SMTP id 40mr1594006rnz; Tue, 16 Nov 2004 09:15:22 -0800 (PST) Received: by 10.38.8.55 with HTTP; Tue, 16 Nov 2004 09:15:22 -0800 (PST) Message-ID: Date: Wed, 17 Nov 2004 01:15:22 +0800 From: Jiawei Ye To: Christer Solskogen In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <200411150126.20446.kstewart@owt.com> <200411151035.05819.kstewart@owt.com> cc: freebsd-current@freebsd.org Subject: Re: refuse file for cvsup being ignored X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 17:15:26 -0000 On Mon, 15 Nov 2004 21:44:02 +0100, Christer Solskogen wrote: > On Mon, 15 Nov 2004 10:35:05 -0800, Kent Stewart wrote: > > > Some of portupgrades features depend on INDEX.db. > > Okay, now I`m confused. > We got INDEX(-5), and INDEX.db, What do they all do? :) > wont these files contribute to bloat? We only need one of them, dont we? > > -- > cso Not if you use the portupgrade suite. portupgrade relies on INDEX* to generate INDEX.db. man portsdb for details. -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 17:46:18 2004 Return-Path: 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 9618E16A4CE for ; Tue, 16 Nov 2004 17:46:18 +0000 (GMT) Received: from nerve.riss-telecom.ru (nerve.riss-telecom.ru [80.66.65.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8234B43D49 for ; Tue, 16 Nov 2004 17:46:17 +0000 (GMT) (envelope-from frol@nerve.riss-telecom.ru) Received: from nerve.riss-telecom.ru (nqnpulf0mxxrzz00@localhost [127.0.0.1]) by nerve.riss-telecom.ru (8.13.1/8.13.1) with ESMTP id iAGHjb7l017791 for ; Tue, 16 Nov 2004 23:45:37 +0600 (NOVT) (envelope-from frol@nerve.riss-telecom.ru) Received: (from frol@localhost) by nerve.riss-telecom.ru (8.13.1/8.13.1/Submit) id iAGHjaUm017790 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 23:45:36 +0600 (NOVT) (envelope-from frol) Date: Tue, 16 Nov 2004 23:45:36 +0600 From: Dmitry Frolov To: freebsd-current@freebsd.org Message-ID: <20041116174536.GA17279@nerve.riss-telecom.ru> Mail-Followup-To: freebsd-current@freebsd.org References: <200411160916.47131.Emanuel.Strobl@gmx.net> <39261.1100593136@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39261.1100593136@critter.freebsd.dk> Organization: RISS-Telecom, JSC X-PGP-Fingerprint: 5232 98E7 596E 21C2 52B5 FCAE 8088 3F87 88BC 27B0 User-Agent: Mutt/1.5.6i Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 17:46:18 -0000 * Poul-Henning Kamp [16.11.2004 14:19]: > >My intents are to make storage available for jails via regular files which > >is at the moment no option since performance gets horrible. If I understand > >things right then this framework should improove performance dramatically > >when e. g. copying /sys to /vnode_backed_md0. > > Not particularly. Performance issue with a file backed filesystems is a major showstopper for me too. Since I'm not a kernel hacker, I'm currenly waiting for someone to fix this. If I understand issue correctly, fixing it requires much work on syncer (probably some sort of "layering"?). Does anybody working or planning to work on this? wbr&w, dmitry. -- Dmitry Frolov RISS-Telecom Network, Novosibirsk, Russia 66415911@ICQ, +7 3832 NO WA1T, DVF-RIPE From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:00:10 2004 Return-Path: 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 946C416A4CE; Tue, 16 Nov 2004 19:00:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6FE743D5C; Tue, 16 Nov 2004 19:00:09 +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 C698A1FF9AC; Tue, 16 Nov 2004 20:00:07 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id DFF001FF9AB; Tue, 16 Nov 2004 20:00:05 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 7FBB7153C4; Tue, 16 Nov 2004 18:55:34 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 7CD3B1538C; Tue, 16 Nov 2004 18:55:35 +0000 (UTC) Date: Tue, 16 Nov 2004 18:55:35 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: David Kleiner In-Reply-To: Message-ID: References: <20041115070404.GP64152@marvin.riggiland.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 19:00:10 -0000 On Mon, 15 Nov 2004, David Kleiner wrote: Hi, > Here is what I get when trying to load up the if_sk.ko module: > ... > Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers! > Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed > Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12 I had seen this too some weeks ago when loading and unloading the if_sk.ko repeatedly but I haven't been able to reproduce afterwards. > This is an Asus "A8V Deluxe (v. 2.0) K8T800 No-WiFi/A" and 6.0-CURRENT > built on Sat Nov 13 12:08:59 PST 2004. > > I also had it crashed while running a 700MB bittorrent transfer (stock > py-bittorrent) but did not get a crash dump. The stack trace pointed > at problem with networking and calling "panic" at the db> prompt > wedged it solid. you may perhaps want to update to lastest version which adds some locking in the jumbo buffer memory functions. This should hopefully help you. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:08:34 2004 Return-Path: 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 CACFD16A4CE; Tue, 16 Nov 2004 19:08:34 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 655D743D3F; Tue, 16 Nov 2004 19:08:34 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id EA1692528B; Tue, 16 Nov 2004 20:08:04 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 74B9F250E4; Tue, 16 Nov 2004 20:08:03 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAGJ83LE023390; Tue, 16 Nov 2004 20:08:03 +0100 Received: (nullmailer pid 2028 invoked by uid 1001); Tue, 16 Nov 2004 19:08:03 -0000 Date: Tue, 16 Nov 2004 20:08:03 +0100 From: Mark Santcroos To: Franz Klammer Message-ID: <20041116190803.GC736@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000207 / -5.9 X-RIPE-Signature: 2408c6b86b2a17b6bb1fac1a44baad5d cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 19:08:34 -0000 On Tue, Nov 16, 2004 at 05:29:59PM +0100, Franz Klammer wrote: > does this patch also work with 5.3 or only with -CURRENT? It probably wouldn't be too hard to get it to work for 5.3 in case of this particular patch. In general I don't know yet what the policy will be regarding 5-STABLE and ACPI. Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:40:27 2004 Return-Path: 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 20F5716A4D1 for ; Tue, 16 Nov 2004 19:40:27 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EF2043D5A for ; Tue, 16 Nov 2004 19:40:27 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 01B2A72DD4; Tue, 16 Nov 2004 11:40:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id F0A0A72DCB; Tue, 16 Nov 2004 11:40:26 -0800 (PST) Date: Tue, 16 Nov 2004 11:40:26 -0800 (PST) From: Doug White To: Stephan Uphoff In-Reply-To: <1100617025.2456.27.camel@palm.tree.com> Message-ID: <20041116114004.K13866@carver.gumbysoft.com> References: <20041112141930.21592.qmail@web54607.mail.yahoo.com> <20041115190644.X7416@carver.gumbysoft.com> <1100617025.2456.27.camel@palm.tree.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "Ketrien I. Saihr-Kesenchedra" cc: Nik Azim Azam cc: freebsd-current@freebsd.org Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 19:40:27 -0000 On Tue, 16 Nov 2004, Stephan Uphoff wrote: > Hopefully we can skip the debugging phase and go directly to the testing > phase. However it would be helpful to know if the PowerEdge 6500 > encounters any problems without the patch. > > The feedback I have received so far looks promising: > > Andy Farkas wrote: > >> You can download the patch at: > >> http://people.freebsd.org/~ups/ipi4_patch > >> > >> Any feedback is appreciated. > >> > >> Stephan > >> > > I have been hammering the box for the last 4 hours without > > a panic. OK, I'll see if it reproduces then try your patch. Thanks! -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:49:51 2004 Return-Path: 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 13EC416A4CE; Tue, 16 Nov 2004 19:49:51 +0000 (GMT) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6F66343D3F; Tue, 16 Nov 2004 19:49:50 +0000 (GMT) (envelope-from riggs@rrr.de) Received: from mail.m-online.net (svr8.m-online.net [192.168.3.138]) by mail-out.m-online.net (Postfix) with ESMTP id AE70D458A; Tue, 16 Nov 2004 20:49:48 +0100 (CET) Received: from marvin.riggiland.au (ppp-62-245-163-197.mnet-online.de [62.245.163.197]) by mail.m-online.net (Postfix) with ESMTP; Tue, 16 Nov 2004 20:49:47 +0100 (CET) Received: from marvin.riggiland.au (localhost [127.0.0.1]) by marvin.riggiland.au (8.13.1/8.13.1) with ESMTP id iAGJnkOD097632; Tue, 16 Nov 2004 20:49:46 +0100 (CET) (envelope-from riggs@marvin.riggiland.au) Received: (from riggs@localhost) by marvin.riggiland.au (8.13.1/8.13.1/Submit) id iAGJnj9g097631; Tue, 16 Nov 2004 20:49:45 +0100 (CET) (envelope-from riggs) Date: Tue, 16 Nov 2004 20:49:44 +0100 From: "Thomas E. Zander" To: "Bjoern A. Zeeb" Message-ID: <20041116194944.GE64152@marvin.riggiland.au> References: <20041115070404.GP64152@marvin.riggiland.au> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SLfjTIIQuAzj8yil" Content-Disposition: inline In-Reply-To: Organization: RiggiServ - Ihr Partner =?iso-8859-15?Q?f?= =?iso-8859-15?Q?=FCr?= alles Delikate X-PGP-KeyID: 0xC85996CD X-PGP-URI: http://blackhole.pca.dfn.de:11371/pks/lookup?op=get&search=0xC85996CD X-PGP-Fingerprint: 4F59 75B4 4CE3 3B00 BC61 5400 8DD4 8929 C859 96CD X-Mailer: Riggisoft Ausguck Eggsbress (Build 1100633313) X-Operating-System: Riggiland BSD 5.3-RELEASE (To serve and protect.) cc: David Kleiner cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 19:49:51 -0000 --SLfjTIIQuAzj8yil Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, 16. Nov 2004, at 18:55 +0000, Bjoern A. Zeeb wrote according to [Re: [PATCH] if_sk(4) rx/tx "hangs"]: > you may perhaps want to update to lastest version which adds some > locking in the jumbo buffer memory functions. This should hopefully > help you. Well, I'm trying now for hours to reproduce any of the problems before. No success :-) if_sk from this morning's HEAD seems to be an awesome step! Good work! Regards, Riggs --=20 - "[...] I talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. ---- "It committed suicide." said Marvin. --SLfjTIIQuAzj8yil Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFBmlnYjdSJKchZls0RAoL7AJ9IpFbsf/KQ42CWWxCawo4Ljc8sbwCfQbtK 48x56Mxne4zhDZ695J/Xnlw= =oQ7q -----END PGP SIGNATURE----- --SLfjTIIQuAzj8yil-- From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 19:50:59 2004 Return-Path: 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 4453B16A4CE for ; Tue, 16 Nov 2004 19:50:59 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25E6E43D46 for ; Tue, 16 Nov 2004 19:50:59 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 1029272DF4; Tue, 16 Nov 2004 11:50:59 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 0DE8372DD4; Tue, 16 Nov 2004 11:50:59 -0800 (PST) Date: Tue, 16 Nov 2004 11:50:59 -0800 (PST) From: Doug White To: ALeine In-Reply-To: <200411110104.iAB149kv097307@marlena.vvi.at> Message-ID: <20041116114809.S13866@carver.gumbysoft.com> References: <200411110104.iAB149kv097307@marlena.vvi.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: FreeBSD 5.3-RELEASE boot failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 19:50:59 -0000 On Wed, 10 Nov 2004, ALeine wrote: > Doug White wrote: > > > Hm... we'll need to disassemble the code there, but typically > > these types of crashes are caused by BIOS bugs. Try upgrading > > your BIOS. > > When I try to boot directly the machine reboots too quickly for > me to be able to catch the error message. The register dump is > from VMWare trying to boot the said FreeBSD 5.3-RELEASE as guest > OS using the mentioned disk in raw disk mode on a friend's > machine. FreeBSD 4.10-STABLE runs just fine that way on his > system. This makes me think it might not be BIOS related. Well VMware isn't the same hardware so thats a totally unrelated problem :) I'd suggest setting up a serial console and capturing the output that way. Connect another machine via null-modem cable to COM1 on the crashing system. At the first spinning bar hit a key and you'll get a boot: prompt. At that prompt enter "-h" and press Return and that should cause the loader (and the error output) to go to the serial port. > > What brand/model machine is this? > > i386, Athlon XP CPU, Chaintech 7SID (Sis 735 chipset) motherboard > with the latest official BIOS. So something fairly recent ... hm. > > Other things you might try: > > > > . Turn off 'Legacy USB' if you don't have a USB keyboard > > . Disable DMA on IDE disks (Known issue on older compaqs) > > I've tried it with USB on and off, it makes no difference. > I'll look into the DMA issue. Thanks for your quick reply. > > > ALeine > ___________________________________________________________________ > WebMail FREE http://mail.austrosearch.net > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 20:05:56 2004 Return-Path: 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 718B316A4CE for ; Tue, 16 Nov 2004 20:05:56 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62B6E43D3F for ; Tue, 16 Nov 2004 20:05:56 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 543FA72DD4; Tue, 16 Nov 2004 12:05:56 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 51F1772DCB; Tue, 16 Nov 2004 12:05:56 -0800 (PST) Date: Tue, 16 Nov 2004 12:05:56 -0800 (PST) From: Doug White To: Poul-Henning Kamp In-Reply-To: <80546.1100202141@critter.freebsd.dk> Message-ID: <20041116120515.J13866@carver.gumbysoft.com> References: <80546.1100202141@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: [TEST] make -j patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 20:05:56 -0000 On Thu, 11 Nov 2004, Poul-Henning Kamp wrote: > > This patch makes the '-j' argument to make(1) become a global limit > on number of jobs launched for all submakes in the build. > > Today a "make -j 12" may start many more than 12 jobs because each > submake interprets the 12 without reference to other makes. Ah, this is the thing I've noticed with the rescue build where it create -j^2 jobs. :) -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 20:38:02 2004 Return-Path: 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 919D716A4CE for ; Tue, 16 Nov 2004 20:38:02 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B54F43D49 for ; Tue, 16 Nov 2004 20:38:02 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAGKdxKB026765; Tue, 16 Nov 2004 13:40:00 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <419A654D.6060200@freebsd.org> Date: Tue, 16 Nov 2004 13:38:37 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <80546.1100202141@critter.freebsd.dk> <20041116120515.J13866@carver.gumbysoft.com> In-Reply-To: <20041116120515.J13866@carver.gumbysoft.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: Poul-Henning Kamp cc: current@freebsd.org Subject: Re: [TEST] make -j patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 20:38:02 -0000 Doug White wrote: > On Thu, 11 Nov 2004, Poul-Henning Kamp wrote: > > >>This patch makes the '-j' argument to make(1) become a global limit >>on number of jobs launched for all submakes in the build. >> >>Today a "make -j 12" may start many more than 12 jobs because each >>submake interprets the 12 without reference to other makes. > > > Ah, this is the thing I've noticed with the rescue build where it create > -j^2 jobs. :) > And people like Warner thought I was a raving lunatic when I reported this a year ago. Oh wait, they think I'm a raving lunatic anyways. But at least I'm vindicated on this one =-) Scott From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 20:49:29 2004 Return-Path: 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 C548A16A4CE for ; Tue, 16 Nov 2004 20:49:29 +0000 (GMT) Received: from web54606.mail.yahoo.com (web54606.mail.yahoo.com [68.142.225.190]) by mx1.FreeBSD.org (Postfix) with SMTP id 585CE43D69 for ; Tue, 16 Nov 2004 20:49:29 +0000 (GMT) (envelope-from nskyline_r35@yahoo.com) Received: (qmail 61311 invoked by uid 60001); 16 Nov 2004 20:49:28 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=cf/e9QbmLmYRHXZ1opU4w7pftaMoN3jRGQjF0C5SyTx7EopPVvSvspYuzVPfehrP6OPgVRpcpOYtoZ9nSC6U60Y+nEaougbRyfN3iFR3Maw+MyF6KrwAXP+PAbxiVuXsJlay8dQ0ZWe4tSvcBeRtxPtkHUTvtyJMmpbKInufLfM= ; Message-ID: <20041116204928.61309.qmail@web54606.mail.yahoo.com> Received: from [82.44.96.53] by web54606.mail.yahoo.com via HTTP; Tue, 16 Nov 2004 12:49:28 PST Date: Tue, 16 Nov 2004 12:49:28 -0800 (PST) From: Nik Azim Azam To: Stephan Uphoff , Doug White In-Reply-To: <1100617025.2456.27.camel@palm.tree.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: "Ketrien I. Saihr-Kesenchedra" cc: freebsd-current@freebsd.org Subject: Re: number of CPUs and IPI panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 20:49:29 -0000 my box survived a make buildworld with the patch. without the patch, it will crash after 20-30 mins. i will test the patch further. good work, Stephan. thanks, nik. --- Stephan Uphoff wrote: > On Mon, 2004-11-15 at 22:10, Doug White wrote: > > On Fri, 12 Nov 2004, Stephan Uphoff wrote: > > > > > On Fri, 2004-11-12 at 09:19, Nik Azim Azam > wrote: > > > > Win2K Advanced Server works just fine here. > > > > > > The root cause seems to be a misunderstanding of > the interrupt delivery > > > and buffering mechanism. The fix may take a few > days since it probably > > > requires extensive changes to the IPI layer. > > > > [getting in late on this] > > > > Tomorrow I will have access to a Dell PowerEdge > 6500 (4x500MHz) I can use > > to capture info or test patches. Or see if the bug > reproduces there in the > > first place :) > > > > rwatson mumbled something about wanting to > determine what triggered the > > prior IPI that the panic later trips over. I'll > have to find a sutiable > > place to hide that information... > > Hopefully we can skip the debugging phase and go > directly to the testing > phase. However it would be helpful to know if the > PowerEdge 6500 > encounters any problems without the patch. > > The feedback I have received so far looks promising: > > Andy Farkas wrote: > >> You can download the patch at: > >> http://people.freebsd.org/~ups/ipi4_patch > >> > >> Any feedback is appreciated. > >> > >> Stephan > >> > > I have been hammering the box for the last 4 hours > without > > a panic. > > > > Without your patch, I could easily get a panic by > boot -s then > > fsck. I did this twice (without panic) using your > patch. > > > > Without your patch, I would usually get a panic > during make > > buildworld -j4. So far with your patch its already > done a > > buildworld -j8, and its about to finish a > buildworld -j4. > > (2 buildworld in a row) > > > > This is good indeed. > > > > -andyf > > > > ps. ok to post to list. > > > __________________________________ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 21:44:23 2004 Return-Path: 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 711F416A4CE for ; Tue, 16 Nov 2004 21:44:23 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.244]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06A3943D55 for ; Tue, 16 Nov 2004 21:44:22 +0000 (GMT) (envelope-from david.kleiner@gmail.com) Received: by mproxy.gmail.com with SMTP id w67so224249cwb for ; Tue, 16 Nov 2004 13:44:21 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=k9gx1pGLAZrW0ff9biHDfyBBrRbarCj0BtHAQVsHnodMPWJkWvQqU9JJpNqAHo41h2Kp0WCzbTdtxsIgsyMV3L0MCtD0O12/F1QZPCkt16kfHNej8ZSmZhDI4NR+SuZoJY+qa+jEaqfbN+EmaOZwby8tMlnb5MkV1bSwWUOEkFI= Received: by 10.11.117.43 with SMTP id p43mr848482cwc; Tue, 16 Nov 2004 13:44:21 -0800 (PST) Received: by 10.11.117.23 with HTTP; Tue, 16 Nov 2004 13:44:21 -0800 (PST) Message-ID: Date: Tue, 16 Nov 2004 13:44:21 -0800 From: David Kleiner To: "Bjoern A. Zeeb" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041115070404.GP64152@marvin.riggiland.au> <20041115084705.GQ64152@marvin.riggiland.au> cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: David Kleiner List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Nov 2004 21:44:23 -0000 Bjoern, Thank you for the update. I re-sync'ed to the latest -HEAD, re-added sk to the kernel statically and it's been running for 5 hours fine, although it "feels" a bit sluggish over the network. Will see how it goes. Cheers, David On Tue, 16 Nov 2004 18:55:35 +0000 (UTC), Bjoern A. Zeeb wrote: > On Mon, 15 Nov 2004, David Kleiner wrote: > > Hi, > > > Here is what I get when trying to load up the if_sk.ko module: > > > ... > > Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers! > > Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed > > Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12 > > I had seen this too some weeks ago when loading and unloading the > if_sk.ko repeatedly but I haven't been able to reproduce afterwards. > > > This is an Asus "A8V Deluxe (v. 2.0) K8T800 No-WiFi/A" and 6.0-CURRENT > > built on Sat Nov 13 12:08:59 PST 2004. > > > > I also had it crashed while running a 700MB bittorrent transfer (stock > > py-bittorrent) but did not get a crash dump. The stack trace pointed > > at problem with networking and calling "panic" at the db> prompt > > wedged it solid. > > you may perhaps want to update to lastest version which adds some > locking in the jumbo buffer memory functions. This should hopefully > help you. > > -- > > > Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT > From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 21:46:10 2004 Return-Path: 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 0EEB316A4CE for ; Tue, 16 Nov 2004 21:46:09 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32CA943D48 for ; Tue, 16 Nov 2004 21:46:09 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAGLk6KY011778; Tue, 16 Nov 2004 22:46:07 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Doug White From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Nov 2004 12:05:56 PST." <20041116120515.J13866@carver.gumbysoft.com> Date: Tue, 16 Nov 2004 22:46:06 +0100 Message-ID: <11777.1100641566@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@freebsd.org Subject: Re: [TEST] make -j patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 21:46:10 -0000 In message <20041116120515.J13866@carver.gumbysoft.com>, Doug White writes: >On Thu, 11 Nov 2004, Poul-Henning Kamp wrote: > >> >> This patch makes the '-j' argument to make(1) become a global limit >> on number of jobs launched for all submakes in the build. >> >> Today a "make -j 12" may start many more than 12 jobs because each >> submake interprets the 12 without reference to other makes. > >Ah, this is the thing I've noticed with the rescue build where it create >-j^2 jobs. :) -j^(depth of directories) actually, but that is even worse. -- 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 16 23:07:17 2004 Return-Path: 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 7459816A4CE for ; Tue, 16 Nov 2004 23:07:17 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C363843D2F for ; Tue, 16 Nov 2004 23:07:16 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAGN7C3C013093; Wed, 17 Nov 2004 00:07:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Dmitry Frolov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Tue, 16 Nov 2004 23:45:36 +0600." <20041116174536.GA17279@nerve.riss-telecom.ru> Date: Wed, 17 Nov 2004 00:07:12 +0100 Message-ID: <13092.1100646432@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: TEST: phk_bufwork patchfile X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 23:07:17 -0000 In message <20041116174536.GA17279@nerve.riss-telecom.ru>, Dmitry Frolov writes : >* Poul-Henning Kamp [16.11.2004 14:19]: > >> >My intents are to make storage available for jails via regular files which >> >is at the moment no option since performance gets horrible. If I understand >> >things right then this framework should improove performance dramatically >> >when e. g. copying /sys to /vnode_backed_md0. >> >> Not particularly. > >Performance issue with a file backed filesystems is a major showstopper >for me too. Since I'm not a kernel hacker, I'm currenly waiting for >someone to fix this. If I understand issue correctly, fixing it requires >much work on syncer (probably some sort of "layering"?). Does anybody >working or planning to work on this? We're getting there, but things take time. -- 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 16 23:18:05 2004 Return-Path: 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 3E7D616A4CE; Tue, 16 Nov 2004 23:18:05 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0697443D2F; Tue, 16 Nov 2004 23:18:05 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAGNI3C4005998 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 16 Nov 2004 15:18:03 -0800 Message-ID: <419A8AA9.3070808@root.org> Date: Tue, 16 Nov 2004 15:18:01 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> <3183.213.147.173.194.1100622599.squirrel@mail.webonaut.com> <20041116190803.GC736@laptop.6bone.nl> In-Reply-To: <20041116190803.GC736@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 23:18:05 -0000 Mark Santcroos wrote: > On Tue, Nov 16, 2004 at 05:29:59PM +0100, Franz Klammer wrote: >>does this patch also work with 5.3 or only with -CURRENT? > > It probably wouldn't be too hard to get it to work for 5.3 in case of > this particular patch. > > In general I don't know yet what the policy will be regarding 5-STABLE > and ACPI. My current understanding of how things should work in RELENG_5 is that ACPI-CA imports will be tested in 6-current for a minimum of 1 week. Patches will be posted to freebsd-acpi@ for about 5 days before an import to 6-current. Changes, additions, etc. to acpi in general can be committed to 6-current immediately if not too drastic and MFCd after 2 days to 1 week. I intend for RELENG_5 to never diverge from 6-current unless required by external API changes. If minimal, we'll ifdef around the interface changes with __FreeBSD_version__. Hope that answers the question. -- Nate From owner-freebsd-current@FreeBSD.ORG Tue Nov 16 23:27:08 2004 Return-Path: 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 2197816A4D0; Tue, 16 Nov 2004 23:27:08 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C96343D4C; Tue, 16 Nov 2004 23:27:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAGNPtok042145; Tue, 16 Nov 2004 16:25:55 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Tue, 16 Nov 2004 16:26:15 -0700 (MST) Message-Id: <20041116.162615.51355677.imp@bsdimp.com> To: scottl@freebsd.org From: "M. Warner Losh" In-Reply-To: <419A654D.6060200@freebsd.org> References: <80546.1100202141@critter.freebsd.dk> <20041116120515.J13866@carver.gumbysoft.com> <419A654D.6060200@freebsd.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: phk@phk.freebsd.dk cc: current@freebsd.org Subject: Re: [TEST] make -j patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 16 Nov 2004 23:27:08 -0000 In message: <419A654D.6060200@freebsd.org> Scott Long writes: : Doug White wrote: : > On Thu, 11 Nov 2004, Poul-Henning Kamp wrote: : > : > : >>This patch makes the '-j' argument to make(1) become a global limit : >>on number of jobs launched for all submakes in the build. : >> : >>Today a "make -j 12" may start many more than 12 jobs because each : >>submake interprets the 12 without reference to other makes. : > : > : > Ah, this is the thing I've noticed with the rescue build where it create : > -j^2 jobs. :) : > : : And people like Warner thought I was a raving lunatic when I reported : this a year ago. Oh wait, they think I'm a raving lunatic anyways. But : at least I'm vindicated on this one =-) I thought you were crazy when you said that there were duplicated jobs being created. I've know that I've seen j^depth behavior for a long time... Warner From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 00:35:18 2004 Return-Path: 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 D990116A4CE for ; Wed, 17 Nov 2004 00:35:18 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B584E43D2D for ; Wed, 17 Nov 2004 00:35:18 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAH0ZIfN047300 for ; Tue, 16 Nov 2004 16:35:18 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAH0ZI99047299 for freebsd-current@freebsd.org; Tue, 16 Nov 2004 16:35:18 -0800 (PST) (envelope-from sgk) Date: Tue, 16 Nov 2004 16:35:18 -0800 From: Steve Kargl To: freebsd-current@freebsd.org Message-ID: <20041117003518.GA47238@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 00:35:19 -0000 I'm trying to set up my wireless NIC (Netgear WG511) to connect to the internet through my wireless route (Netgear WGR614). When I set up the router, I choose the 128-bit WEP key feature. To my chagrin, Windows XP works well with the WG511, but I prefer FreeBSD. I tried to give my WEP key to ifconfig, which does not work. %ifconfig ndis0 inet 192.168.0.3 broadcast 192.168.0.1 netmask 255.255.255.0 ssid YADA channel 11 wepmode on wepkey abcdefghijklmnopqrstuvwxyz ndis0: set wepkey failed: 19 ndis0: set wepkey failed: 19 ifconfig: string too long ndis0: set wepkey failed: 19 Other than using a 64-bit key, is there some way to force FreeBSD to work? -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 00:48:34 2004 Return-Path: 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 CF82016A4CE for ; Wed, 17 Nov 2004 00:48:34 +0000 (GMT) Received: from thingy.tbd.co.nz (thingy.tbd.co.nz [210.48.70.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id D579843D46 for ; Wed, 17 Nov 2004 00:48:33 +0000 (GMT) (envelope-from andy@fud.org.nz) Received: from thingy.tbd.co.nz (localhost [127.0.0.1]) iAH0nJAX024535; Wed, 17 Nov 2004 13:49:19 +1300 Received: (from thompsa@localhost) by thingy.tbd.co.nz (8.12.3/8.12.3/Debian-7.1) id iAH0nH4P024502; Wed, 17 Nov 2004 13:49:17 +1300 X-Authentication-Warning: thingy.tbd.co.nz: thompsa set sender to andy@fud.org.nz using -f Date: Wed, 17 Nov 2004 13:49:17 +1300 From: Andrew Thompson To: Steve Kargl Message-ID: <20041117004917.GC24087@thingy.tbd.co.nz> References: <20041117003518.GA47238@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117003518.GA47238@troutmask.apl.washington.edu> User-Agent: Mutt/1.3.28i cc: freebsd-current@freebsd.org Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 00:48:35 -0000 On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > I'm trying to set up my wireless NIC (Netgear WG511) to > connect to the internet through my wireless route (Netgear > WGR614). When I set up the router, I choose the 128-bit > WEP key feature. To my chagrin, Windows XP works well > with the WG511, but I prefer FreeBSD. I tried to give > my WEP key to ifconfig, which does not work. > > %ifconfig ndis0 inet 192.168.0.3 broadcast 192.168.0.1 > netmask 255.255.255.0 ssid YADA channel 11 wepmode on > wepkey abcdefghijklmnopqrstuvwxyz > The wep key should be hex, not ascii. -- Andrew From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 00:51:46 2004 Return-Path: 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 0787616A4CE for ; Wed, 17 Nov 2004 00:51:46 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id C798843D39 for ; Wed, 17 Nov 2004 00:51:45 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAH0qlPl016442; Tue, 16 Nov 2004 16:52:47 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAH0qlpu016441; Tue, 16 Nov 2004 16:52:47 -0800 Date: Tue, 16 Nov 2004 16:52:47 -0800 From: Brooks Davis To: Steve Kargl Message-ID: <20041117005247.GB13628@odin.ac.hmc.edu> References: <20041117003518.GA47238@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XOIedfhf+7KOe/yw" Content-Disposition: inline In-Reply-To: <20041117003518.GA47238@troutmask.apl.washington.edu> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-current@freebsd.org Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 00:51:46 -0000 --XOIedfhf+7KOe/yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > I'm trying to set up my wireless NIC (Netgear WG511) to > connect to the internet through my wireless route (Netgear > WGR614). When I set up the router, I choose the 128-bit > WEP key feature. To my chagrin, Windows XP works well > with the WG511, but I prefer FreeBSD. I tried to give > my WEP key to ifconfig, which does not work. >=20 > %ifconfig ndis0 inet 192.168.0.3 broadcast 192.168.0.1 > netmask 255.255.255.0 ssid YADA channel 11 wepmode on > wepkey abcdefghijklmnopqrstuvwxyz >=20 > ndis0: set wepkey failed: 19 > ndis0: set wepkey failed: 19 > ifconfig: string too long > ndis0: set wepkey failed: 19 >=20 > Other than using a 64-bit key, is there some way to > force FreeBSD to work? 128-bit WEP actually uses 104-bits of key material which corresponds to 13 ASCII characters or a 26-digit hex key. Shorter, zero-padded keys will work, but you appear to be using something longer. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --XOIedfhf+7KOe/yw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBmqCfXY6L6fI4GtQRApycAKCc/GieFBuld8rpJqGT0hrVi2JilwCdGFgx fjNLL5ygHbpPOLGqXbDyYKw= =chYF -----END PGP SIGNATURE----- --XOIedfhf+7KOe/yw-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 01:00:37 2004 Return-Path: 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 D99AC16A4CE for ; Wed, 17 Nov 2004 01:00:37 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id B3F4A43D62 for ; Wed, 17 Nov 2004 01:00:37 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) iAH10bQo047506; Tue, 16 Nov 2004 17:00:37 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)iAH10acB047505; Tue, 16 Nov 2004 17:00:36 -0800 (PST) (envelope-from sgk) Date: Tue, 16 Nov 2004 17:00:36 -0800 From: Steve Kargl To: Brooks Davis Message-ID: <20041117010036.GA47474@troutmask.apl.washington.edu> References: <20041117003518.GA47238@troutmask.apl.washington.edu> <20041117005247.GB13628@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117005247.GB13628@odin.ac.hmc.edu> User-Agent: Mutt/1.4.1i cc: freebsd-current@freebsd.org Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 01:00:38 -0000 On Tue, Nov 16, 2004 at 04:52:47PM -0800, Brooks Davis wrote: > On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > > > > Other than using a 64-bit key, is there some way to > > force FreeBSD to work? > > 128-bit WEP actually uses 104-bits of key material which corresponds to > 13 ASCII characters or a 26-digit hex key. Shorter, zero-padded keys > will work, but you appear to be using something longer. > Thanks, Brooks. Netgear's docs aren't the greatest. It wasn't clear whether the string was ascii or hex, (it was given without the 0x prefix). -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 02:11:22 2004 Return-Path: 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 86C7B16A4CE for ; Wed, 17 Nov 2004 02:11:22 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6384343D54 for ; Wed, 17 Nov 2004 02:11:22 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 9AE4BF1B73 for ; Tue, 16 Nov 2004 18:11:19 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60572-04 for ; Tue, 16 Nov 2004 18:11:13 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id DE26AF1819 for ; Tue, 16 Nov 2004 18:11:12 -0800 (PST) From: Sean McNeil To: current@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-4jA90FQLMvHkt8IyL79D" Date: Tue, 16 Nov 2004 18:11:12 -0800 Message-Id: <1100657472.74795.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com Subject: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 02:11:22 -0000 --=-4jA90FQLMvHkt8IyL79D Content-Type: text/plain Content-Transfer-Encoding: quoted-printable This has been happening for a long time with current and hasn't been resolved. When I start up slapd, I cannot stop it without kill -9 ing it. It would appear stuck in kse and probably has something to do with kill -0: (gdb) bt #0 0x000000080142e914 in kse_release () at kse_release.S:2 #1 0x0000000801428e49 in kse_wait (kse=3D0x62a000, td_wait=3D0x0, sigseqno=3D0) at /usr/src/lib/libpthread/thread/thr_kern.c:1843 #2 0x0000000801427078 in kse_sched_multi (kmbx=3D0x62efa0) at /usr/src/lib/libpthread/thread/thr_kern.c:1039 #3 0x000000080142afbf in _amd64_enter_uts () at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 #4 0x0000000000000000 in ?? () #5 0x000000000062f000 in ?? () #6 0x000000000062a000 in ?? () #7 0x0000000000000000 in ?? () #8 0x0000000000000000 in ?? () #9 0x0000000000000000 in ?? () #10 0x0000000000000000 in ?? () #11 0x0000000000000000 in ?? () #12 0x0000000000000001 in ?? () #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () at /usr/src/lib/libpthread/thread/thr_kern.c:904 Previous frame inner to this frame (corrupt stack?) --=-4jA90FQLMvHkt8IyL79D Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmrNAyQsGN30uGE4RAl4wAJ4ntyRO5M2Zs4NqL8GFkR4Uqd3B5gCgs3Mu V6sZwRnnzvthTT0nCbmUIIU= =EQA7 -----END PGP SIGNATURE----- --=-4jA90FQLMvHkt8IyL79D-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 02:43:06 2004 Return-Path: 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 89D3416A4CE; Wed, 17 Nov 2004 02:43:06 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83FE243D2F; Wed, 17 Nov 2004 02:42:58 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iAH2gsZY054951; Wed, 17 Nov 2004 13:12:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 17 Nov 2004 13:12:53 +1030 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1460959.hL2vnYa13u"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411171312.54406.doconnor@gsoft.com.au> X-Spam-Score: -2.8 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: "Bjoern A. Zeeb" cc: David Kleiner cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 02:43:06 -0000 --nextPart1460959.hL2vnYa13u Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 17 Nov 2004 05:25, Bjoern A. Zeeb wrote: > > Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers! > > Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed > > Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12 > > I had seen this too some weeks ago when loading and unloading the > if_sk.ko repeatedly but I haven't been able to reproduce afterwards. This happens "all the time" in 4.x - presumably because contiguous memory i= s=20 much harder to get post-boot. Let me know if you need a crash box to try it on :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1460959.hL2vnYa13u Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmrqu5ZPcIHs/zowRAlh7AJ4qVD5+Zy7/yKCthXwugMfTKrntOgCfT4Ia LcYRl9+n+2Wo2uhvs5yRwJs= =AcE8 -----END PGP SIGNATURE----- --nextPart1460959.hL2vnYa13u-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 02:43:06 2004 Return-Path: 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 89D3416A4CE; Wed, 17 Nov 2004 02:43:06 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 83FE243D2F; Wed, 17 Nov 2004 02:42:58 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iAH2gsZY054951; Wed, 17 Nov 2004 13:12:55 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 17 Nov 2004 13:12:53 +1030 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1460959.hL2vnYa13u"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411171312.54406.doconnor@gsoft.com.au> X-Spam-Score: -2.8 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_01_02,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: "Bjoern A. Zeeb" cc: David Kleiner cc: FreeBSD current mailing list cc: FreeBSD amd64 mailing list Subject: Re: [PATCH] if_sk(4) rx/tx "hangs" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 02:43:06 -0000 --nextPart1460959.hL2vnYa13u Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 17 Nov 2004 05:25, Bjoern A. Zeeb wrote: > > Nov 15 15:31:58 macropus kernel: sk0: no memory for jumbo buffers! > > Nov 15 15:31:58 macropus kernel: sk0: jumbo buffer allocation failed > > Nov 15 15:31:58 macropus kernel: device_attach: sk0 attach returned 12 > > I had seen this too some weeks ago when loading and unloading the > if_sk.ko repeatedly but I haven't been able to reproduce afterwards. This happens "all the time" in 4.x - presumably because contiguous memory i= s=20 much harder to get post-boot. Let me know if you need a crash box to try it on :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1460959.hL2vnYa13u Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmrqu5ZPcIHs/zowRAlh7AJ4qVD5+Zy7/yKCthXwugMfTKrntOgCfT4Ia LcYRl9+n+2Wo2uhvs5yRwJs= =AcE8 -----END PGP SIGNATURE----- --nextPart1460959.hL2vnYa13u-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 06:51:24 2004 Return-Path: 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 0BC5A16A4CE; Wed, 17 Nov 2004 06:51:24 +0000 (GMT) Received: from mwinf0301.wanadoo.fr (smtp3.wanadoo.fr [193.252.22.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94F7943D2F; Wed, 17 Nov 2004 06:51:21 +0000 (GMT) (envelope-from aurelien.nephtali@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0301.wanadoo.fr (SMTP Server) with SMTP id 4C5201C0056B; Wed, 17 Nov 2004 07:51:20 +0100 (CET) Received: from [192.168.2.30] (ca-sqy-1-210.w80-8.abo.wanadoo.fr [80.8.54.210]) by mwinf0301.wanadoo.fr (SMTP Server) with ESMTP id 07C631C00566; Wed, 17 Nov 2004 07:51:19 +0100 (CET) Message-ID: <419AF4E7.5000206@wanadoo.fr> Date: Wed, 17 Nov 2004 07:51:19 +0100 From: Aurelien Nephtali User-Agent: Mozilla Thunderbird 0.9 (X11/20041112) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> In-Reply-To: <20041115211636.GA1540@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 06:51:24 -0000 Mark Santcroos wrote: > If the following patch doesn't burn down too many systems, it will be > committed to HEAD in the near future. > > http://www.santcroos.net/mark/freebsd/files/acpi_import_20041105.diff.gz > > Mark > Hello, The patch applies fine but it sill doesn't fix two long standing bugs :/ The first one is a resume problem, when I suspend my laptop with 'zzz' it works, but when I resume it the LCD stays black and that's all. I've tested setting reset_video to 0 but it's the same. The secong bug is relatted to battery. Sometimes when I unplug the AC, the system catch it and ma battery % falls to 98% and stays stuck on this value. It means no warning when battery is critical :/ Tell me if you need technical informations. Thanks. -- NEPHTALI 'dak' Aurelien From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 07:50:52 2004 Return-Path: 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 E63D516A4CE; Wed, 17 Nov 2004 07:50:52 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4441043D45; Wed, 17 Nov 2004 07:50:52 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.2] (vpn-client-2.marcuscom.com [10.2.1.2]) iAH7p2dq047511; Wed, 17 Nov 2004 02:51:02 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <419B02DC.3060508@marcuscom.com> Date: Wed, 17 Nov 2004 02:50:52 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> <200411161105.43475.jhb@FreeBSD.org> In-Reply-To: <200411161105.43475.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 07:50:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: |>Yes, this patch makes a world of difference. The interrupt storm is |>still there, but the ata0 (irq 14) rate is down to 1480 per second, and |>the interrupt load is only ~2%. Thanks. | | | Can you tweak it a bit and see if it works even better if you put an #if 0 | around the lines that read: | | + if (count > hz) { | + storming = 0; | + count = 0; | + } else | + count++; Removing these lines brings the storm down to ~978 per second, so yes, this is better. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmwLbb2iPiv4Uz4cRAr7TAKCEc30+Vw3yDvQl0/mNzNyA92PeHgCgk3Je DSBCE3CQn33rnwxFh5oupp4= =+7Og -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 07:50:52 2004 Return-Path: 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 E63D516A4CE; Wed, 17 Nov 2004 07:50:52 +0000 (GMT) Received: from creme-brulee.marcuscom.com (creme-brulee.marcuscom.com [24.172.16.118]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4441043D45; Wed, 17 Nov 2004 07:50:52 +0000 (GMT) (envelope-from marcus@marcuscom.com) Received: from [10.2.1.2] (vpn-client-2.marcuscom.com [10.2.1.2]) iAH7p2dq047511; Wed, 17 Nov 2004 02:51:02 -0500 (EST) (envelope-from marcus@marcuscom.com) Message-ID: <419B02DC.3060508@marcuscom.com> Date: Wed, 17 Nov 2004 02:50:52 -0500 From: Joe Marcus Clarke Organization: MarcusCom, Inc. User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200411151424.49790.jhb@FreeBSD.org> <4199AEC8.1070608@marcuscom.com> <200411161105.43475.jhb@FreeBSD.org> In-Reply-To: <200411161105.43475.jhb@FreeBSD.org> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-5.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on creme-brulee.marcuscom.com cc: current@FreeBSD.org cc: Kris Kennaway cc: freebsd-current@FreeBSD.org cc: Joe Marcus Clarke cc: Alexander@Leidinger.net cc: Robert Watson Subject: Re: 6-CURRENT unbelievably slow? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 07:50:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 John Baldwin wrote: |>Yes, this patch makes a world of difference. The interrupt storm is |>still there, but the ata0 (irq 14) rate is down to 1480 per second, and |>the interrupt load is only ~2%. Thanks. | | | Can you tweak it a bit and see if it works even better if you put an #if 0 | around the lines that read: | | + if (count > hz) { | + storming = 0; | + count = 0; | + } else | + count++; Removing these lines brings the storm down to ~978 per second, so yes, this is better. Thanks. Joe - -- PGP Key : http://www.marcuscom.com/pgp.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (Darwin) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBmwLbb2iPiv4Uz4cRAr7TAKCEc30+Vw3yDvQl0/mNzNyA92PeHgCgk3Je DSBCE3CQn33rnwxFh5oupp4= =+7Og -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 08:10:10 2004 Return-Path: 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 922AB16A4CE; Wed, 17 Nov 2004 08:10:10 +0000 (GMT) Received: from postman.ripe.net (postman.ripe.net [193.0.0.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2AA4943D41; Wed, 17 Nov 2004 08:10:10 +0000 (GMT) (envelope-from marks@ripe.net) Received: by postman.ripe.net (Postfix, from userid 8) id 923DF25542; Wed, 17 Nov 2004 09:10:09 +0100 (CET) Received: from birch.ripe.net (birch.ripe.net [193.0.1.96]) by postman.ripe.net (Postfix) with ESMTP id 8229525541; Wed, 17 Nov 2004 09:10:08 +0100 (CET) Received: from ripe.net (cow.ripe.net [193.0.1.239]) by birch.ripe.net (8.12.10/8.11.6) with SMTP id iAH8A8LE026244; Wed, 17 Nov 2004 09:10:08 +0100 Received: (nullmailer pid 46993 invoked by uid 1001); Wed, 17 Nov 2004 08:10:07 -0000 Date: Wed, 17 Nov 2004 09:10:07 +0100 From: Mark Santcroos To: Aurelien Nephtali Message-ID: <20041117081007.GC95090@laptop.6bone.nl> References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419AF4E7.5000206@wanadoo.fr> User-Agent: Mutt/1.4.2.1i X-Handles: MS6-6BONE, MS18417-RIPE X-RIPE-Spam-Level: X-RIPE-Spam-Tests: ALL_TRUSTED,BAYES_00 X-RIPE-Spam-Status: N 0.000114 / -5.9 X-RIPE-Signature: 287b25f4cf29664b3d95328be8e6cd27 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 08:10:10 -0000 On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: > The patch applies fine but it sill doesn't fix two long standing bugs :/ At least there are no regressions, thats good news. > The first one is a resume problem, when I suspend my laptop with 'zzz' > it works, but when I resume it the LCD stays black and that's all. I've > tested setting reset_video to 0 but it's the same. So it is only the display that doesn't come back? Is this in X or at the console? Have you tried jhb's acpi_video patches that have the dpms patches included? (They are in the archive of this list) > The secong bug is relatted to battery. Sometimes when I unplug the AC, > the system catch it and ma battery % falls to 98% and stays stuck on > this value. It means no warning when battery is critical :/ What happens if you plug the AC back after a while? Mark -- RIPE NCC - Delft University of Technology - The FreeBSD Project marks@ripe.net - m.a.santcroos@ewi.tudelft.nl - marks@freebsd.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 08:39:12 2004 Return-Path: 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 2AB1816A4CE for ; Wed, 17 Nov 2004 08:39:12 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 19E3643D5A for ; Wed, 17 Nov 2004 08:39: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 iAH8d7Px076650; Wed, 17 Nov 2004 10:39:07 +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 02596-20; Wed, 17 Nov 2004 10:39:06 +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 iAH8d657076647 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 10:39:06 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAH8d8fi024166; Wed, 17 Nov 2004 10:39:08 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 10:39:07 +0200 From: Ruslan Ermilov To: Poul-Henning Kamp Message-ID: <20041117083907.GA24067@ip.net.ua> References: <20041116120515.J13866@carver.gumbysoft.com> <11777.1100641566@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <11777.1100641566@critter.freebsd.dk> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@FreeBSD.org Subject: Re: [TEST] make -j patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 08:39:12 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 16, 2004 at 10:46:06PM +0100, Poul-Henning Kamp wrote: > In message <20041116120515.J13866@carver.gumbysoft.com>, Doug White write= s: > >On Thu, 11 Nov 2004, Poul-Henning Kamp wrote: > > > >> > >> This patch makes the '-j' argument to make(1) become a global limit > >> on number of jobs launched for all submakes in the build. > >> > >> Today a "make -j 12" may start many more than 12 jobs because each > >> submake interprets the 12 without reference to other makes. > > > >Ah, this is the thing I've noticed with the rescue build where it create > >-j^2 jobs. :) >=20 > -j^(depth of directories) actually, but that is even worse. >=20 In the "make buildworld" case only. Like I told you, bsd.subdir.mk is constructed so that subdirs are NOT built in parallel, and there is a reason for this. Makefile.inc1 creates special par-* targets to build things in subdirs in parallel. There are a lot of places that depend on a particular order of directories listed in SUBDIR. Hopefully, after we created libs and headers, we can build top-level directories in parallel. Anyway, thanks for looking into it and finally fixing this! Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBmw4rqRfpzJluFF4RAslWAJ94J+GThTTGOgPPKPLLDFu5t1HoAgCeJ66c umDljGK1jgLbaFTWG2TiJR0= =bY5h -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 09:18:03 2004 Return-Path: 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 EEA7616A4CE for ; Wed, 17 Nov 2004 09:18:03 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40E2043D67 for ; Wed, 17 Nov 2004 09:18:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAH9I1kW022757 for ; Wed, 17 Nov 2004 10:18:01 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org From: Poul-Henning Kamp Date: Wed, 17 Nov 2004 10:18:01 +0100 Message-ID: <22756.1100683081@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [HEADSDOWN] I'm done for now. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 09:18:04 -0000 Giant is now pushed down through select/poll/ioctl. Please test and report problems. -- 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 Wed Nov 17 09:19:50 2004 Return-Path: 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 36D8F16A4CE for ; Wed, 17 Nov 2004 09:19:50 +0000 (GMT) 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 8B96043D48 for ; Wed, 17 Nov 2004 09:19:49 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAH9JhGF072864; Wed, 17 Nov 2004 10:19:45 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419B177D.2090206@DeepCore.dk> Date: Wed, 17 Nov 2004 10:18:53 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Lawrence Farr References: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> In-Reply-To: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: current@freebsd.org Subject: Re: Marvell SATA Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 09:19:50 -0000 Lawrence Farr wrote: > Hello All, >=20 > I have a Supermicro P4SCT+ with an onboard Marvell > SATA controller, which also has the Adaptec Hostraid > software raid functionality. Are there any patches to > support the marvell controller as a plain controller > anywhere? >=20 > pciconf output if anyones interested: >=20 > none4@pci2:4:0: class=3D0x010000 card=3D0x504111ab chip=3D0x504111ab re= v=3D0x03 > hdr=3D0x00 > vendor =3D 'Marvell Semiconductor (Was: Galileo Technology Ltd)' > device =3D '88SX504 4-port SATA I PCI-X Controller' > class =3D mass storage > subclass =3D SCSI Not yet, but I'm working on it, actually on the exact same board. Maybe, just maybe, you could hack the Highpoint hptmv driver, I havn't=20 tried but unless they put in "tricks" to prohibit that it should work. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 09:27:32 2004 Return-Path: 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 BBC4416A4CE; Wed, 17 Nov 2004 09:27:32 +0000 (GMT) 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 122BE43D3F; Wed, 17 Nov 2004 09:27:32 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAH9RRdn072976; Wed, 17 Nov 2004 10:27:29 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419B194E.5090800@DeepCore.dk> Date: Wed, 17 Nov 2004 10:26:38 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> <20041117081007.GC95090@laptop.6bone.nl> In-Reply-To: <20041117081007.GC95090@laptop.6bone.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: Aurelien Nephtali Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 09:27:32 -0000 Mark Santcroos wrote: > On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: >=20 >>The patch applies fine but it sill doesn't fix two long standing bugs := / >=20 > At least there are no regressions, thats good news. >=20 >>The first one is a resume problem, when I suspend my laptop with 'zzz' = >>it works, but when I resume it the LCD stays black and that's all. I've= =20 >>tested setting reset_video to 0 but it's the same. >=20 > So it is only the display that doesn't come back? Is this in X or at th= e=20 > console? Have you tried jhb's acpi_video patches that have the dpms pat= ches > included? (They are in the archive of this list) The problem here has been known since mid august (3 months), I have 3=20 different laptops here that all fails in this manner (ASUS, Acer, IBM),=20 however they lockup solid on resume which might be why ;) >>The secong bug is relatted to battery. Sometimes when I unplug the AC, = >>the system catch it and ma battery % falls to 98% and stays stuck on=20 >>this value. It means no warning when battery is critical :/ >=20 > What happens if you plug the AC back after a while? There are nasties in the bat stuff, I have to comment out various parts=20 of it to get the ASUS to boot at all :( This brings up the question: do we have a maintainer for ACPI and why=20 arent these issues being dealt with ? I for one have reported these=20 issue for ages including as much debug as is possible, but it seems to=20 be silently ignored (and yes 5.3-RELEASE is just as broken)... --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 09:41:17 2004 Return-Path: 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 1088216A4D0 for ; Wed, 17 Nov 2004 09:41:17 +0000 (GMT) Received: from mail.newlines.ru (mail.newlines.ru [195.54.211.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 11BA843D48 for ; Wed, 17 Nov 2004 09:41:15 +0000 (GMT) (envelope-from anton@nikiforov.ru) Received: from mail.newlines.ru (root@localhost) by mail.newlines.ru (8.12.10/8.12.9) with SMTP id iAH9fBVS085633 for ; Wed, 17 Nov 2004 09:41:11 GMT (envelope-from anton@nikiforov.ru) Received: from [213.252.67.117] (master-hosting.newlines.ru [213.252.67.117] (may be forged)) (authenticated bits=0) by mail.newlines.ru (8.12.10/8.12.9) with ESMTP id iAH9fBck085627; Wed, 17 Nov 2004 09:41:11 GMT (envelope-from anton@nikiforov.ru) Message-ID: <419B2B0F.4070401@nikiforov.ru> Date: Wed, 17 Nov 2004 13:42:23 +0300 From: Anton Nikiforov User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040907 X-Accept-Language: ru, en-us, en MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030408010602010205090905" cc: freebsd-ports-bugs@freebsd.org cc: stable@freebsd.org cc: current@freebsd.org Subject: pam-pgsql X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: anton@nikiforov.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 09:41:17 -0000 This is a cryptographically signed message in MIME format. --------------ms030408010602010205090905 Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 8bit Dear All I was trying to find updates for pam-pgsql port to compile it under 5.3, but was not succseeded. Could you please give me the direction where to search for updated sources or alternative? I need to run SASL2 and authenticate users recorded in PGSql. I was trying to fix and compile the module myself, but looks like pams for 4.x and 5.x are different and it is too hard for me to complete this. -- ó Õ×ÁÖÅÎÉÅÍ (Best regads), áÎÔÏÎ îÉËÉÆÏÒÏ× (Anton Nikiforov) --------------ms030408010602010205090905 Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIII7TCC AtEwggI6oAMCAQICAwvaFTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDQwMzA1MjExMjI4WhcNMDUwMzA1MjExMjI4 WjBEMR8wHQYDVQQDExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMSEwHwYJKoZIhvcNAQkBFhJh bnRvbkBuaWtpZm9yb3YucnUwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC1Ps7E cf3xTnaY72Aip/U5HeUmGwQ6QmbCjMcqS3XfO6EsA+5ol526JvhQ1XStpDX/kh8R8MDELUJD SVooXFiDInspw5tmPOlXV1C60xH4VWf5Gh+2y3yDGzHyWBAalul7LbhC1p8zDNUA12pAu4Ry 1k1A0Yepomr8CRbh/Z9JryfJcqHYDL+z1qgLzQlpJsao9E3Zld5ZfgJPORcFoRB7Z6jvqVLh pLNmSrvfDbSw6WK/K9EbZT9zlOTlmOnt4uLBy3hKZMcvkaFrYVYTRXLMegJHFPAp3sxLYef2 iW9fEUKgrs4W7d5c8UWlmiGurVt1Xdzc58W8X3vekMLqu9elAgMBAAGjLzAtMB0GA1UdEQQW MBSBEmFudG9uQG5pa2lmb3Jvdi5ydTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GB ABINGnCD0TGnBHqGYbJHSwjFfxEsVS1ygSUVIyb0Q1S0SphgUSeRWIZ4+joWR9TzxFGqLtYM TEQvRTQ7VJcugjn2o2nTgQ4EPhze0O5ki2eUWHE9dViHboQWOWI0r1vurUTkDnmloeM8mpMo CAAtXbjyhz7AVKUwI7vULQKuE+imMIIC0TCCAjqgAwIBAgIDC9oVMA0GCSqGSIb3DQEBBAUA MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQu MSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNDAz MDUyMTEyMjhaFw0wNTAzMDUyMTEyMjhaMEQxHzAdBgNVBAMTFlRoYXd0ZSBGcmVlbWFpbCBN ZW1iZXIxITAfBgkqhkiG9w0BCQEWEmFudG9uQG5pa2lmb3Jvdi5ydTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBALU+zsRx/fFOdpjvYCKn9Tkd5SYbBDpCZsKMxypLdd87oSwD 7miXnbom+FDVdK2kNf+SHxHwwMQtQkNJWihcWIMieynDm2Y86VdXULrTEfhVZ/kaH7bLfIMb MfJYEBqW6XstuELWnzMM1QDXakC7hHLWTUDRh6miavwJFuH9n0mvJ8lyodgMv7PWqAvNCWkm xqj0TdmV3ll+Ak85FwWhEHtnqO+pUuGks2ZKu98NtLDpYr8r0RtlP3OU5OWY6e3i4sHLeEpk xy+RoWthVhNFcsx6AkcU8CnezEth5/aJb18RQqCuzhbt3lzxRaWaIa6tW3Vd3Nznxbxfe96Q wuq716UCAwEAAaMvMC0wHQYDVR0RBBYwFIESYW50b25AbmlraWZvcm92LnJ1MAwGA1UdEwEB /wQCMAAwDQYJKoZIhvcNAQEEBQADgYEAEg0acIPRMacEeoZhskdLCMV/ESxVLXKBJRUjJvRD VLRKmGBRJ5FYhnj6OhZH1PPEUaou1gxMRC9FNDtUly6COfajadOBDgQ+HN7Q7mSLZ5RYcT11 WIduhBY5YjSvW+6tROQOeaWh4zyakygIAC1duPKHPsBUpTAju9QtAq4T6KYwggM/MIICqKAD AgECAgENMA0GCSqGSIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVy biBDYXBlMRIwEAYDVQQHEwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5n MSgwJgYDVQQLEx9DZXJ0aWZpY2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtU aGF3dGUgUGVyc29uYWwgRnJlZW1haWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZy ZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMwNzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQsw CQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoG A1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcN AQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUEcJ3f6f+jHuy9zfVb8hp2vX8MOmHy v1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/EfkTYkKhPPK9Xzgnc9A74r/rsY Pge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMBAAGjgZQwgZEwEgYDVR0T AQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3JsLnRoYXd0ZS5jb20v VGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYDVR0RBCIwIKQe MBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GBAEiM0VCD 6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+hLGZ GwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC 3CEZNd4ksdMdRv9dX2VPMYIDOzCCAzcCAQEwaTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMc VGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFs IEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvaFTAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDExMTcxMDQyMjNaMCMGCSqGSIb3DQEJ BDEWBBSV7oIY5D34+JIdNjwZpiI8H3S2lTBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIDC9oVMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAwvaFTANBgkqhkiG9w0BAQEFAASCAQCPEsan YJs0Zm/1Bm0ASJBJ+3B7eJmGnI3okvbfRcCp7HnIpfjrV+zJyCICww9XwCsKfW049wZ+QCll FgrzGmrGWsANpDoD/Poyzpo3Me0k/aSW6DYz3+ak/HIvwHzjUJTLE0Hy/UXN1AUfNHB7bUfZ whwGdGi/aaA6XS64cNQ31qOm1hPOmpPChJUvigLQMF4h6s3oz5PzqwnW+fvuR7kAN6wnddtt Tc42nBLHPFqrb5V1LBS+GI0zurxcLYtlLn27b/pcayoKqq8jZ5eKjjWf0IG0xadCADRNf3/R IoDtabuB1DcuLa9UwFLtjguxz1kQuqShqDgQhVR0MKea3nBjAAAAAAAA --------------ms030408010602010205090905-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 10:42:13 2004 Return-Path: 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 A5DA416A4CE for ; Wed, 17 Nov 2004 10:42:13 +0000 (GMT) Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 323F443D45 for ; Wed, 17 Nov 2004 10:42:13 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from ppp83-237-163-231.pppoe.mtu-net.ru ([83.237.163.231]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1CUNGJ-000CNw-Nj for current@freebsd.org; Wed, 17 Nov 2004 13:42:11 +0300 Message-ID: <419B2B01.9050803@FreeBSD.org> Date: Wed, 17 Nov 2004 13:42:09 +0300 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 2.9 (++) X-Spam-Report: Spam detection software, running on the system "proxy.ciam.ru", hasmessagelabel similar future email. If you have any questions, see the administrator of that system for details. Content preview: I've bought a KVM switchoutputwith this options: options KBD_INSTALL_CDEV device uhci device ohci device device ums # Mouse [...] Content analysis details: (2.9 points, 5.0 required) pts rule name description --------------------------------------------------addr 1)address [83.237.163.231 listed in dnsbl.sorbs.net] Subject: two devices on one USB channel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 10:42:13 -0000 I've bought a KVM switch (2computers->1display,mouse,keyboard(PS/2 both)). It has one USB output (Windows sees USB mouse and USB keyboard). I've rebuilt my kernel with this options: options KBD_INSTALL_CDEV device uhci device ohci device usb device ugen device uhid device umass device ukbd # Keyboard device ums # Mouse Keyboard is working now. But mouse don't. dmesg: usb1: OHCI version 1.0, legacy support usb1: SMM does not respond, resetting usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 3 ports with 3 removable, self powered ukbd0: vendor 0x10d5 M02 1.6, rev 1.10/0.00, addr 2, iclass 3/1 kbd1 at ukbd0 ums0: vendor 0x10d5 M02 1.6, rev 1.10/0.00, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. usbdevs -vd: Controller /dev/usb0: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), nVidia(0x0000), rev 1.00 uhub0 port 1 powered port 2 powered port 3 powered Controller /dev/usb1: addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), nVidia(0x0000), rev 1.00 uhub1 port 1 powered port 2 addr 2: low speed, power 100 mA, config 1, M02 1.6(0x0116), vendor 0x10d5(0x10d5), rev 0.00 ukbd0 ums0 port 3 powered moused is runned by usbd (/usr/sbin/moused -p /dev/ums0 -I /var/run/moused.ums0.pid ; /usr/sbin/vidcontrol -m on). How can I fix it please? -- Sem. From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 10:46:45 2004 Return-Path: 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 8976416A4D0 for ; Wed, 17 Nov 2004 10:46:45 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3911943D2F for ; Wed, 17 Nov 2004 10:46:45 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAHAjGo7071185; Wed, 17 Nov 2004 05:45:16 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAHAjGAI071182; Wed, 17 Nov 2004 10:45:16 GMT (envelope-from robert@fledge.watson.org) Date: Wed, 17 Nov 2004 10:45:16 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <22756.1100683081@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: [HEADSDOWN] I'm done for now. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 10:46:45 -0000 On Wed, 17 Nov 2004, Poul-Henning Kamp wrote: > Giant is now pushed down through select/poll/ioctl. > > Please test and report problems. Great! This should hopefully both reduce contention on Giant in interesting cases (such as select-intensive socket stuff), as well as reduce the overal number of locking operations for some interesting paths (i.e., select on sockets, which previously paid the cost of locking/unlocking Giant but didn't need it). FWIW, I would not be surprised if we see some bug reports come in now that ioctl() is being run without Giant for the network stack back default. While some of those ioctl's are already running without Giant due to sharing code paths with set/getsockopt() and internal use of ioctl in the kernel, others have probably not seen as much exposure. Likewise, while the pipe ioctl code should be MPSAFE (and is pretty innocuous), that's not been confirmed. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 10:48:34 2004 Return-Path: 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 4E32E16A4CE for ; Wed, 17 Nov 2004 10:48:34 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id E808443D2F for ; Wed, 17 Nov 2004 10:48:33 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAHAob99029500; Wed, 17 Nov 2004 03:50:37 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <419B2CA6.3010401@freebsd.org> Date: Wed, 17 Nov 2004 03:49:10 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> <419B177D.2090206@DeepCore.dk> In-Reply-To: <419B177D.2090206@DeepCore.dk> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org Subject: Re: Marvell SATA Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 10:48:34 -0000 Søren Schmidt wrote: > Lawrence Farr wrote: > >> Hello All, >> >> I have a Supermicro P4SCT+ with an onboard Marvell >> SATA controller, which also has the Adaptec Hostraid >> software raid functionality. Are there any patches to >> support the marvell controller as a plain controller >> anywhere? >> >> pciconf output if anyones interested: >> >> none4@pci2:4:0: class=0x010000 card=0x504111ab chip=0x504111ab rev=0x03 >> hdr=0x00 >> vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' >> device = '88SX504 4-port SATA I PCI-X Controller' >> class = mass storage >> subclass = SCSI > > > Not yet, but I'm working on it, actually on the exact same board. > Maybe, just maybe, you could hack the Highpoint hptmv driver, I havn't > tried but unless they put in "tricks" to prohibit that it should work. > The hptmv driver only exports raid devices, not single disks, and those raid devices have to have HPT metadata on them. The magic here is buried in the binary object file along with the Herc programming details, so I don't think it'll be possible to get anything useful out of it. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 11:07:10 2004 Return-Path: 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 DF3B316A4CE for ; Wed, 17 Nov 2004 11:07:09 +0000 (GMT) Received: from av3-2-sn3.vrr.skanova.net (av3-2-sn3.vrr.skanova.net [81.228.9.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF09743D54 for ; Wed, 17 Nov 2004 11:07:08 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av3-2-sn3.vrr.skanova.net (Postfix, from userid 502) id DA08F37F62; Wed, 17 Nov 2004 12:07:07 +0100 (CET) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av3-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 585B337F61 for ; Wed, 17 Nov 2004 12:07:07 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 2C1A93800D for ; Wed, 17 Nov 2004 12:07:07 +0100 (CET) From: "Daniel Eriksson" To: Date: Wed, 17 Nov 2004 12:06:52 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTMlYq7bsZgjuZ/Qn2QnvJiCjO8Ng== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: uma_zfree_internal crash, if_em related? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 11:07:10 -0000 After upgrading my 6-CURRENT box to 2004.11.14.16.00.00 (and also 2004.11.16.19.15.00), I have encountered this crash twice in 24 hours. A system built from sources dated 2004.11.07.07.00.00 stayed up a week straight without a hitch. The system is a dual AthlonMP system. The dmesg from the last boot is attached at the bottom (ACPI disabled). The first crash came with ACPI enabled, the second with it disabled. I do have a dump from the first crash in case someone needs further info. Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 01 fault virtual address = 0x0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc06c57ac stack pointer = 0x10:0xe32bbbf0 frame pointer = 0x10:0xe32bbc18 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 = 26 (irq16: em0 atapci1+) [thread 100000] Stopped at uma_zfree_internal+0xcc: movl %edx,0(%eax) db> tr uma_zfree_internal(0,1,0,c2388800,e32bbc4c,0,1,c227a3c0) at uma_zfree_internal+0xcc uma_zfree_arg(c10469a0,c3de8a00,0,c239e950,e32bbc8c) at uma_zfree_arg+0x3d6 m_freem(c3de8a00,0,0,c26a5ca8,a5) at m_freem+0x49 em_clean_transmit_interrupts(c2388800,c3b2a900,6b35f445,ffc03014,c2285000) at em_clean_transmit_interrupts+0xb7 em_intr(c2388800,0,0,0,0) at em_intr+0x376 ithread_loop(c2272780,e32bbd48,0,0,0) at ithread_loop+0xb3 fork_exit(c054e5e0,c2272780,e32bbd48) at fork_exit+0x62 fork_trampoline() at fork_trampoline+0x8 --- trap 0x1, eip = 0, esp = 0xe32bbd7c, ebp = 0 --- Here's a few system options and the dmesg: ------------------------------------------ * SCHED_4BSD, PREEMPTION, HZ=2000, ZERO_COPY_SOCKETS, AHC_ALLOW_MEMIO, GEOM_BDE, SMP, apic * CFLAGS= -O2 -pipe, COPTFLAGS= -O2 -pipe, CPUTYPE?=athlon-xp * debug.mpsafenet=1, vfs.devfs.fops=1, kern.ipc.nmbclusters=32768, kern.ipc.nsfbufs=16384 * net.inet.tcp.sendspace=524288, net.inet.tcp.recvspace=524288, kern.ipc.maxsockbuf=2097152, kern.ipc.somaxconn=512, net.inet.tcp.rfc3390=1, net.inet.ip.intr_queue_maxlen=200, net.inet.tcp.sack.enable=1, net.isr.enable=0, vfs.hirunningspace=16777216 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 6.0-CURRENT #0: Tue Nov 16 22:26:50 CET 2004 daniel@xxx.xxx.xxx:/usr/obj/usr/src/sys/XXX Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) MP 2600+ (2000.08-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x6a0 Stepping = 0 Features=0x383fbff AMD Features=0xc0480000 real memory = 1073217536 (1023 MB) avail memory = 1041547264 (993 MB) MPTable: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 1 cpu1 (AP): APIC ID: 0 ioapic0: Assuming intbase of 0 ioapic0 irqs 0-23 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 agp0: port 0x1490-0x1493 mem 0xea100000-0xea100fff,0xec000000-0xedffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 5.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 pci0: at device 7.3 (no driver attached) em0: port 0x1400-0x143f mem 0xe8000000-0xe803ffff,0xe8080000-0xe809ffff irq 16 at device 8.0 on pci0 em0: Ethernet address: 00:04:23:ac:20:8a em0: Speed:N/A Duplex:N/A em1: port 0x1440-0x147f mem 0xe8040000-0xe807ffff,0xe80a0000-0xe80bffff irq 17 at device 8.1 on pci0 em1: Ethernet address: 00:04:23:ac:20:8b em1: Speed:N/A Duplex:N/A ahc0: port 0x1000-0x10ff mem 0xe80c0000-0xe80c0fff irq 17 at device 9.0 on pci0 ahc0: [GIANT-LOCKED] aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs pcib2: at device 16.0 on pci0 pci2: on pcib2 atapci1: port 0x2000-0x20ff,0x30d0-0x30d3,0x30d8-0x30df,0x30d4-0x30d7,0x30e0-0x30e7 irq 16 at device 4.0 on pci2 ata2: channel #0 on atapci1 ata3: channel #1 on atapci1 atapci2: port 0x2400-0x24ff,0x30e8-0x30eb,0x30f0-0x30f7,0x30ec-0x30ef,0x30f8-0x30ff irq 16 at device 4.1 on pci2 ata4: channel #0 on atapci2 ata5: channel #1 on atapci2 atapci3: port 0x3000-0x307f,0x30c0-0x30cf,0x3080-0x30bf mem 0xea000000-0xea01ffff,0xea021000-0xea021fff irq 18 at device 6.0 on pci2 atapci3: failed: rid 0x20 is memory, requested 4 ata6: channel #0 on atapci3 ata7: channel #1 on atapci3 ata8: channel #2 on atapci3 ata9: channel #3 on atapci3 atapci4: port 0x2800-0x28ff,0x3400-0x3403,0x3408-0x340f,0x3404-0x3407,0x3410-0x3417 irq 19 at device 7.0 on pci2 ata10: channel #0 on atapci4 ata11: channel #1 on atapci4 atapci5: port 0x2c00-0x2cff,0x3418-0x341b,0x3420-0x3427,0x341c-0x341f,0x3428-0x342f irq 19 at device 7.1 on pci2 ata12: channel #0 on atapci5 ata13: channel #1 on atapci5 cpu0 on motherboard cpu1 on motherboard orm0: at iomem 0xe0000-0xe3fff,0xc0000-0xcafff on isa0 pmtimer0 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x100> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (port) unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) Timecounters tick every 1.000 msec ipfw2 initialized, divert loadable, rule-based forwarding disabled, default to accept, logging unlimited ad0: 117800MB [239340/16/63] at ata0-master UDMA100 ad1: 117800MB [239340/16/63] at ata0-slave UDMA100 ad2: 117800MB [239340/16/63] at ata1-master UDMA100 ad3: 117800MB [239340/16/63] at ata1-slave UDMA100 ad4: 238475MB [484521/16/63] at ata2-master UDMA100 ad5: 238475MB [484521/16/63] at ata2-slave UDMA100 ad6: 239372MB [486344/16/63] at ata3-master UDMA133 ad7: 239372MB [486344/16/63] at ata3-slave UDMA133 ad8: 194481MB [395136/16/63] at ata4-master UDMA133 ad9: 194481MB [395136/16/63] at ata4-slave UDMA133 ad10: 194481MB [395136/16/63] at ata5-master UDMA133 ad11: 239372MB [486344/16/63] at ata5-slave UDMA133 ad12: 239372MB [486344/16/63] at ata6-master SATA150 ad14: 238475MB [484521/16/63] at ata7-master SATA150 ad16: 239372MB [486344/16/63] at ata8-master SATA150 ad20: 114473MB [232581/16/63] at ata10-master UDMA100 ad21: 114473MB [232581/16/63] at ata10-slave UDMA100 ad22: 117246MB [238216/16/63] at ata11-master UDMA133 ad23: 117246MB [238216/16/63] at ata11-slave UDMA133 ad24: 114473MB [232581/16/63] at ata12-master UDMA100 ad25: 117800MB [239340/16/63] at ata12-slave UDMA100 ad26: 239372MB [486344/16/63] at ata13-master UDMA133 ar0: 476950MB [60802/255/63] status: READY subdisks: disk0 READY on ad4 at ata2-master disk1 READY on ad5 at ata2-slave ar1: 478744MB [61031/255/63] status: READY subdisks: disk0 READY on ad6 at ata3-master disk1 READY on ad7 at ata3-slave ar2: 583443MB [74378/255/63] status: READY subdisks: disk0 READY on ad8 at ata4-master disk1 READY on ad9 at ata4-slave disk2 READY on ad10 at ata5-master ar3: 234493MB [29893/255/63] status: READY subdisks: disk0 READY on ad22 at ata11-master disk1 READY on ad25 at ata12-slave ar4: 228946MB [29186/255/63] status: READY subdisks: disk0 READY on ad23 at ata11-slave disk1 READY on ad24 at ata12-master Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8759MB (17938986 512 byte sectors: 255H 63S/T 1116C) da2 at ahc0 bus 0 target 10 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da3 at ahc0 bus 0 target 11 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da4 at ahc0 bus 0 target 12 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da4: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da5 at ahc0 bus 0 target 13 lun 0 da5: Fixed Direct Access SCSI-3 device da5: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled da5: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a WARNING: DEVFS uses fops From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 11:48:29 2004 Return-Path: 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 5AF0316A4CE; Wed, 17 Nov 2004 11:48:29 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id B232F43D31; Wed, 17 Nov 2004 11:48:28 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iAHBT2UJ004704 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 17 Nov 2004 06:29:04 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-current@freebsd.org Date: Wed, 17 Nov 2004 06:51:05 -0500 User-Agent: KMail/1.7 References: <419B2B01.9050803@FreeBSD.org> In-Reply-To: <419B2B01.9050803@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3118907.eLkp9xaBRL"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411170651.17091.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: Sergey Matveychuk Subject: Re: two devices on one USB channel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 11:48:29 -0000 --nextPart3118907.eLkp9xaBRL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 17 November 2004 05:42 am, Sergey Matveychuk wrote: > I've bought a KVM switch (2computers->1display,mouse,keyboard(PS/2 > both)). It has one USB output (Windows sees USB mouse and USB keyboard). > > I've rebuilt my kernel with this options: > options KBD_INSTALL_CDEV > device uhci > device ohci > device usb > device ugen > device uhid > device umass > device ukbd # Keyboard > device ums # Mouse > > Keyboard is working now. But mouse don't. > > dmesg: > usb1: OHCI version 1.0, legacy support > usb1: SMM does not respond, resetting > usb1: on ohci1 > usb1: USB revision 1.0 > uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 3 ports with 3 removable, self powered > ukbd0: vendor 0x10d5 M02 1.6, rev 1.10/0.00, addr 2, iclass 3/1 > kbd1 at ukbd0 > ums0: vendor 0x10d5 M02 1.6, rev 1.10/0.00, addr 2, iclass 3/1 > ums0: 5 buttons and Z dir. > > usbdevs -vd: > Controller /dev/usb0: > addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), > nVidia(0x0000), rev 1.00 > uhub0 > port 1 powered > port 2 powered > port 3 powered > Controller /dev/usb1: > addr 1: full speed, self powered, config 1, OHCI root hub(0x0000), > nVidia(0x0000), rev 1.00 > uhub1 > port 1 powered > port 2 addr 2: low speed, power 100 mA, config 1, M02 1.6(0x0116), > vendor 0x10d5(0x10d5), rev 0.00 > ukbd0 > ums0 > port 3 powered > > moused is runned by usbd (/usr/sbin/moused -p /dev/ums0 -I > /var/run/moused.ums0.pid ; /usr/sbin/vidcontrol -m on). > > How can I fix it please? The patch I posted here should fix your problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/63837 =2D-=20 Anish Mistry --nextPart3118907.eLkp9xaBRL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBmzs1xqA5ziudZT0RAlkyAKCj/AG2m4QYLsM1hD9mE67RUNopeACfcHrQ MCeGDxlTaORTQdDDwxc5V5E= =ss6O -----END PGP SIGNATURE----- --nextPart3118907.eLkp9xaBRL-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 12:02:04 2004 Return-Path: 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 1423216A4CE for ; Wed, 17 Nov 2004 12:02:04 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 207A843D1F for ; Wed, 17 Nov 2004 12:02:03 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAHC1kUT030199 for ; Wed, 17 Nov 2004 13:01:46 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <419B3DA9.8020202@fer.hr> Date: Wed, 17 Nov 2004 13:01:45 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: openldap slapd startup delay X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 12:02:04 -0000 I'm running pam_ldap & nss_ldap fine, but there's a huge delay when slapd starts (upto 30sec.). During the delay there's no load on the machine, and it's listening on hosts that are name-resolvable via /etc/hosts (it has priority in /etc/nsswitch.conf). Any ideas? From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 08:28:52 2004 Return-Path: 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 8159216A4CE for ; Wed, 17 Nov 2004 08:28:52 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.192]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6FEF43D55 for ; Wed, 17 Nov 2004 08:28:51 +0000 (GMT) (envelope-from aurelien.nephtali@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so636819rns for ; Wed, 17 Nov 2004 00:28:51 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=uKHmvyzIk9kV1NOqmRYhv6ODlpS5qIRGU+Tnx3nXLwwqxxOUjesBRKJzAfBbYWGaeus0YHzsR2yc0f80AcFI6ZnbjNywuzVRPDk3tBuVvYPs4mCVS8jGdUpDzuc7H2CmZS7xjnv6oeWSkGF88/MwHUX/dp8QXd01cmsD55sp3Hk= Received: by 10.38.179.4 with SMTP id b4mr165771rnf; Wed, 17 Nov 2004 00:28:51 -0800 (PST) Received: by 10.38.179.71 with HTTP; Wed, 17 Nov 2004 00:28:51 -0800 (PST) Message-ID: <5334c8b041117002821dd5c65@mail.gmail.com> Date: Wed, 17 Nov 2004 09:28:51 +0100 From: Aurelien Nephtali To: freebsd-current@freebsd.org, freebsd-acpi@freebsd.org In-Reply-To: <5334c8b041117002779c899d9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041115211636.GA1540@laptop.6bone.nl> <20041117081007.GC95090@laptop.6bone.nl> <5334c8b041117002779c899d9@mail.gmail.com> X-Mailman-Approved-At: Wed, 17 Nov 2004 13:03:30 +0000 Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Aurelien Nephtali List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 08:28:52 -0000 On Wed, 17 Nov 2004 09:10:07 +0100, Mark Santcroos wrote: > On Wed, Nov 17, 2004 at 07:51:19AM +0100, Aurelien Nephtali wrote: > > The patch applies fine but it sill doesn't fix two long standing bugs :/ > > At least there are no regressions, thats good news. :) > > > The first one is a resume problem, when I suspend my laptop with 'zzz' > > it works, but when I resume it the LCD stays black and that's all. I've > > tested setting reset_video to 0 but it's the same. > > So it is only the display that doesn't come back? Is this in X or at the > console? Have you tried jhb's acpi_video patches that have the dpms patches > included? (They are in the archive of this list) I have not recently tested with X but the tests I've done yesterday was with the console. The laptop seems to come back from suspend mode but the LCD stays black as if the laptop wasn't powered (but the system seems to come back correctly from suspend mode but, of course, I can't be sure of that). I'll search through the list for these patches and test when I'll come back home. > > > The secong bug is relatted to battery. Sometimes when I unplug the AC, > > the system catch it and ma battery % falls to 98% and stays stuck on > > this value. It means no warning when battery is critical :/ > > What happens if you plug the AC back after a while? If I plug the AC back, ACPI code detects it, the correct % went back and the battery is correctly detected as charging . -- Aurelien 'dak' Nephtali From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 12:57:50 2004 Return-Path: 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 A073416A4D0 for ; Wed, 17 Nov 2004 12:57:50 +0000 (GMT) Received: from av5-2-sn3.vrr.skanova.net (av5-2-sn3.vrr.skanova.net [81.228.9.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id E511B43D5F for ; Wed, 17 Nov 2004 12:57:49 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av5-2-sn3.vrr.skanova.net (Postfix, from userid 502) id 5119C37F94; Wed, 17 Nov 2004 13:57:49 +0100 (CET) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av5-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 42FC837EF9 for ; Wed, 17 Nov 2004 13:57:49 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 15B1C38003 for ; Wed, 17 Nov 2004 13:57:49 +0100 (CET) From: "Daniel Eriksson" To: Date: Wed, 17 Nov 2004 13:57:46 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTMpQjVQN40H2OqTmqyb2XRZwq6AA== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: CVS / cvsup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 12:57:50 -0000 After having problems with a kernel compiled from sources from yesterday I decided to go back to a known good kernel from 2004.11.07.07.00.00. Unfortunately I cannot seem to compile it: ===> autofs (depend) make: don't know how to make autofs_vfsops.c. Stop *** Error code 2 I recall a commit-message from last week with the wrong date. Could it be that a recent commit having to do with vfsops got the wrong timestamp, thus messing up the source repository? /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 13:28:10 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from green.homeunix.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9841016A4CE; Wed, 17 Nov 2004 13:28:10 +0000 (GMT) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id iAHDS9i6059571; Wed, 17 Nov 2004 08:28:09 -0500 (EST) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id iAHDS8HN059570; Wed, 17 Nov 2004 08:28:08 -0500 (EST) (envelope-from green) Date: Wed, 17 Nov 2004 08:28:08 -0500 From: Brian Fundakowski Feldman To: Alexey Dokuchaev Message-ID: <20041117132808.GL997@green.homeunix.org> References: <20041115120355.GA74977@regency.nsu.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041115120355.GA74977@regency.nsu.ru> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: 6-CURRENT, threads, hangs are still there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 13:28:11 -0000 On Mon, Nov 15, 2004 at 06:03:55PM +0600, Alexey Dokuchaev wrote: > Hello there, > > Updated world + kernel on Nov 12. Sticking to ULE + PREEMPTION + DEBUG > STUFF in kernel. Running sim, psi, xmms, mozilla etc. hangs on startup, > unless `libpthread' mapped to `libc_r' via /etc/libmap.conf. > GDB is unable to attach, process is unkillable even with SIGKILL. > Very reproducible. CPU: Intel 2.8GHz, HTT enabled. > > Does anyone have a clue on this? Using ULE on purpose to help hunt down > its bugs. What debugging info can/should I get? > > Thanks. Dmesg et al. available on demand. Out of curiousity, as I'm in no position to hack on this stuff now either, does it happen without PREEMPTION? Does it happen if you force libpthread to single-cpu-threading? -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 13:51:00 2004 Return-Path: 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 66B2A16A4CE for ; Wed, 17 Nov 2004 13:51:00 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 034D043D1F for ; Wed, 17 Nov 2004 13:51:00 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1CUQD4-0007kO-U5; Wed, 17 Nov 2004 13:50:58 +0000 Date: Wed, 17 Nov 2004 13:50:58 +0000 From: Dick Davies To: Ivan Voras Message-ID: <20041117135058.GB28461@lb.tenfour> References: <419B3DA9.8020202@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419B3DA9.8020202@fer.hr> User-Agent: Mutt/1.4.2.1i Sender: Rasputin cc: FreeBSD Current Users Subject: Re: openldap slapd startup delay X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dick Davies List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 13:51:00 -0000 * Ivan Voras [1124 13:24]: > I'm running pam_ldap & nss_ldap fine, but there's a huge delay when > slapd starts (upto 30sec.). During the delay there's no load on the > machine, and it's listening on hosts that are name-resolvable via > /etc/hosts (it has priority in /etc/nsswitch.conf). I saw this for the past three weeks - it appears to be a problem with the rc script. If you run 'ps awwux'and copy the command line shown to a script, it starts straight away. I replaced it with this, which starts instantly : root@eris exim # less /usr/local/etc/rc.d/000._slappy.sh #!/bin/sh # please don't mistake me for someone who gives a shit that I check a pidfile # twice in the stop function, I am too old and lazy to learn shell. DAEMON="/usr/local/libexec/slapd" PIDFILE="/var/run/openldap/slapd.pid" CFG="/usr/local/etc/openldap/slapd.conf" FLAGS='-h ldaps://ldap.domain/ ldap://ldap.domain -u ldap -g ldap' case $1 in start) [ -x ${DAEMON} ] && { echo -n ' starting slapd' ${DAEMON} ${FLAGS} } ;; stop) [ -f ${PIDFILE} ] || ( echo ' slapd not running? (no ${PIDFILE})' && exit ) [ -f ${PIDFILE} ] && { echo -n ' stopping slapd' kill `cat ${PIDFILE}` } ;; restart) stop start ;; *) echo "usage: `basename $0` {start|stop|restart}" >&2 exit 64 ;; esac -- And if you think you're going to bleed all over me you're even wronger than you normally be - The Specials, 'Little Bitch' Rasputin :: Jack of All Trades - Master of Nuns From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 15:45:59 2004 Return-Path: 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 6B04B16A4CE for ; Wed, 17 Nov 2004 15:45:59 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7876343D2D for ; Wed, 17 Nov 2004 15:45:58 +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 iAHFjpeY026378; Wed, 17 Nov 2004 17:45:51 +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 50514-01; Wed, 17 Nov 2004 17:45:50 +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 iAHFjoD6026375 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 17:45:50 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHFjpEk026294; Wed, 17 Nov 2004 17:45:51 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 17:45:51 +0200 From: Ruslan Ermilov To: Daniel Eriksson Message-ID: <20041117154551.GE25995@ip.net.ua> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Oiv9uiLrevHtW1RS" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: freebsd-current@freebsd.org Subject: Re: CVS / cvsup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 15:45:59 -0000 --Oiv9uiLrevHtW1RS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 01:57:46PM +0100, Daniel Eriksson wrote: >=20 > After having problems with a kernel compiled from sources from yesterday I > decided to go back to a known good kernel from 2004.11.07.07.00.00. > Unfortunately I cannot seem to compile it: >=20 > =3D=3D=3D> autofs (depend) > make: don't know how to make autofs_vfsops.c. Stop > *** Error code 2 >=20 >=20 > I recall a commit-message from last week with the wrong date. Could it be > that a recent commit having to do with vfsops got the wrong timestamp, th= us > messing up the source repository? >=20 You should have: ls: /sys/modules/autofs: No such file or directory Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Oiv9uiLrevHtW1RS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm3IvqRfpzJluFF4RAuPKAKCQje99trxgjLc7sYB09XZTRmNeWACgga51 rfgBjQ5NQu+xwJbX0OwnL7Y= =o0U8 -----END PGP SIGNATURE----- --Oiv9uiLrevHtW1RS-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 16:09:06 2004 Return-Path: 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 1C71316A4CE for ; Wed, 17 Nov 2004 16:09:06 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2CA43D48 for ; Wed, 17 Nov 2004 16:09:05 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id C539E51281; Wed, 17 Nov 2004 08:12:15 -0800 (PST) Date: Wed, 17 Nov 2004 08:12:15 -0800 From: Kris Kennaway To: Alexey Dokuchaev Message-ID: <20041117161215.GA84085@xor.obsecurity.org> References: <20041115120355.GA74977@regency.nsu.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9amGYk9869ThD9tj" Content-Disposition: inline In-Reply-To: <20041115120355.GA74977@regency.nsu.ru> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: 6-CURRENT, threads, hangs are still there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 16:09:06 -0000 --9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 15, 2004 at 06:03:55PM +0600, Alexey Dokuchaev wrote: > Hello there, >=20 > Updated world + kernel on Nov 12. Sticking to ULE + PREEMPTION + DEBUG > STUFF in kernel. Running sim, psi, xmms, mozilla etc. hangs on startup, > unless `libpthread' mapped to `libc_r' via /etc/libmap.conf. > GDB is unable to attach, process is unkillable even with SIGKILL. > Very reproducible. CPU: Intel 2.8GHz, HTT enabled. >=20 > Does anyone have a clue on this? Using ULE on purpose to help hunt down > its bugs. What debugging info can/should I get? You should try with 4BSD too to see if it's a bug in ULE, or in generic parts of the kernel. Kris --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm3hfWry0BWjoQKURAlmHAKCIu+Yxdb3wO0vmkZR6gSGXEDlaagCg8V/P xCKN6DgwZP2JEL/e2nzcx5Y= =e83+ -----END PGP SIGNATURE----- --9amGYk9869ThD9tj-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 17:00:52 2004 Return-Path: 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 7BBEF16A4CE; Wed, 17 Nov 2004 17:00:52 +0000 (GMT) Received: from av9-1-sn1.fre.skanova.net (av9-1-sn1.fre.skanova.net [81.228.11.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C9AF43D2D; Wed, 17 Nov 2004 17:00:52 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av9-1-sn1.fre.skanova.net (Postfix, from userid 502) id F21A93811A; Wed, 17 Nov 2004 18:00:50 +0100 (CET) Received: from smtp3-2-sn1.fre.skanova.net (smtp3-2-sn1.fre.skanova.net [81.228.11.164]) by av9-1-sn1.fre.skanova.net (Postfix) with ESMTP id E3760380EA; Wed, 17 Nov 2004 18:00:50 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-2-sn1.fre.skanova.net (Postfix) with ESMTP id CAAE237E44; Wed, 17 Nov 2004 18:00:50 +0100 (CET) From: "Daniel Eriksson" To: "'Ruslan Ermilov'" Date: Wed, 17 Nov 2004 18:00:46 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20041117154551.GE25995@ip.net.ua> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTMvTaX4wNltwyhSQKwfa7Q98eQ9QACMarw cc: freebsd-current@freebsd.org Subject: RE: CVS / cvsup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 17:00:52 -0000 Ruslan Ermilov wrote: > > I > > decided to go back to a known good kernel from 2004.11.07.07.00.00. > > Unfortunately I cannot seem to compile it: > > > > ===> autofs (depend) > > make: don't know how to make autofs_vfsops.c. Stop > > *** Error code 2 > > > > > > I recall a commit-message from last week with the wrong > date. Could it be > > that a recent commit having to do with vfsops got the wrong > timestamp, thus > > messing up the source repository? > > > You should have: > > ls: /sys/modules/autofs: No such file or directory This is what I did: 1. System running CURRENT from 2 days ago 2. rm -r /usr/obj/* /usr/src/* 3. cvsup source dated 2004.11.07.07.00.00 (this is a version I have run before) 4. ln -s /root/kernels/XXX /usr/src/sys/i386/conf/XXX 5. cd /usr/src; make buildkernel 6. fail... I don't see how I could have messed anything up. I even tried another version that I also know have worked before (2004.11.05.07.00.00) with exactly the same result. I'll try this on another machine I have that is running CURRENT. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 17:23:38 2004 Return-Path: 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 4F45E16A4CE; Wed, 17 Nov 2004 17:23:38 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 775E643D46; Wed, 17 Nov 2004 17:23:37 +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 iAHHNaNX032486; Wed, 17 Nov 2004 19:23:36 +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 61352-11; Wed, 17 Nov 2004 19:23:35 +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 iAHHNZGP032483 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 19:23:35 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAHHNbMk026796; Wed, 17 Nov 2004 19:23:37 +0200 (EET) (envelope-from ru) Date: Wed, 17 Nov 2004 19:23:37 +0200 From: Ruslan Ermilov To: Daniel Eriksson Message-ID: <20041117172337.GA26593@ip.net.ua> References: <20041117154551.GE25995@ip.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+QahgC5+KEYLbs62" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: Mark Murray cc: current@FreeBSD.org Subject: Re: CVS / cvsup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 17:23:38 -0000 --+QahgC5+KEYLbs62 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Daniel, On Wed, Nov 17, 2004 at 06:00:46PM +0100, Daniel Eriksson wrote: [...] > This is what I did: >=20 > 1. System running CURRENT from 2 days ago > 2. rm -r /usr/obj/* /usr/src/* > 3. cvsup source dated 2004.11.07.07.00.00 (this is a version I have run > before) > 4. ln -s /root/kernels/XXX /usr/src/sys/i386/conf/XXX > 5. cd /usr/src; make buildkernel > 6. fail... >=20 > I don't see how I could have messed anything up. I even tried another > version that I also know have worked before (2004.11.05.07.00.00) with > exactly the same result. >=20 > I'll try this on another machine I have that is running CURRENT. >=20 Ah, I see now. CVS meisters did a repo-surgery and removed the contents of /home/ncvs/src/sys/fs/autofs/ completely. What this means is that checkouts with -D2004/11/07 won't produce files that were present at that point in the past. More precisely, this means that builds using HEAD sources from day one when autofs was connected to the build (2004/09/02) and up to 2004/11/10 are now broken, FWIW. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --+QahgC5+KEYLbs62 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm4kYqRfpzJluFF4RAjI6AJ4zZJ1BPdgJNomtWWo4o7G8qcjslwCfQcyW aJG4mqJNfeVaigPcFwejSTU= =NGzw -----END PGP SIGNATURE----- --+QahgC5+KEYLbs62-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 17:33:49 2004 Return-Path: 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 0A6B116A4CE; Wed, 17 Nov 2004 17:33:49 +0000 (GMT) Received: from av7-1-sn4.m-sp.skanova.net (av7-1-sn4.m-sp.skanova.net [81.228.10.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5FD043D2F; Wed, 17 Nov 2004 17:33:48 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id 640E437F32; Wed, 17 Nov 2004 18:33:47 +0100 (CET) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av7-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 561BB37EEC; Wed, 17 Nov 2004 18:33:47 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 2042737E5B; Wed, 17 Nov 2004 18:33:47 +0100 (CET) From: "Daniel Eriksson" To: "'Ruslan Ermilov'" Date: Wed, 17 Nov 2004 18:33:44 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20041117172337.GA26593@ip.net.ua> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTMytHjSAgNUHhNTj+foe/bj+Q6pgAAG26g cc: current@freebsd.org Subject: RE: CVS / cvsup problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 17:33:49 -0000 Ruslan Ermilov wrote: > Ah, I see now. CVS meisters did a repo-surgery and removed the > contents of /home/ncvs/src/sys/fs/autofs/ completely. What this > means is that checkouts with -D2004/11/07 won't produce files > that were present at that point in the past. More precisely, > this means that builds using HEAD sources from day one when > autofs was connected to the build (2004/09/02) and up to > 2004/11/10 are now broken, FWIW. That sucks bit, especially since I feel the need to back down to 2004.11.07.07.00.00 due to stability concerns. I guess it's time to learn more about the build magic so I can get this working myself... /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 17:56:24 2004 Return-Path: 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 F2C1A16A4CE for ; Wed, 17 Nov 2004 17:56:23 +0000 (GMT) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A9B043D1F for ; Wed, 17 Nov 2004 17:56:23 +0000 (GMT) (envelope-from arno@heho.snv.jussieu.fr) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.184.22]) by shiva.jussieu.fr (8.12.11/jtpda-5.4) with ESMTP id iAHHuH2T095663 ; Wed, 17 Nov 2004 18:56:17 +0100 (CET) X-Ids: 166 Received: from heho.snv.jussieu.fr (localhost [127.0.0.1]) iAHHuGsA004838 ; Wed, 17 Nov 2004 18:56:16 +0100 (MET) Received: (from arno@localhost) by heho.snv.jussieu.fr (8.13.1/8.13.1/Submit) id iAHHuEId004833; Wed, 17 Nov 2004 18:56:14 +0100 (MET) (envelope-from arno) To: "Wilkinson, Alex" References: <20041116021421.GK56252@squash.dsto.defence.gov.au> From: "Arno J. Klaassen" Date: 17 Nov 2004 18:56:13 +0100 In-Reply-To: <20041116021421.GK56252@squash.dsto.defence.gov.au> Message-ID: Lines: 33 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-1.5.11 (shiva.jussieu.fr [134.157.0.166]); Wed, 17 Nov 2004 18:56:17 +0100 (CET) X-Miltered: at shiva.jussieu.fr with ID 419B90C1.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Antivirus: scanned by sophie at shiva.jussieu.fr cc: freebsd-current@freebsd.org Subject: Re: bge(4) watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 17:56:24 -0000 "Wilkinson, Alex" writes: > I get the following errors, however, although it states that there is no > carrier, there is. > > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: flags=8843 mtu 1500 > options=1a > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > ether 00:11:0a:40:d2:dd > media: Ethernet autoselect (none) > status: no carrier > > Mounting NFS file systems:bge0: watchdog timeout -- resetting > > > Here is ifconfig(8) output after fully booted: > > bge0: flags=8843 mtu 1500 > options=1a > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > ether 00:11:0a:40:d2:dd > media: Ethernet autoselect (100baseTX ) > status: active > > Seems odd enough, to email the wizards about it. one of my co-workers had a similar problem (PR 73538). Leaving out "device apic" from the kernel-config "fixed" the problem. YMMV Arno From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:01:58 2004 Return-Path: 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 BCE8616A4CE for ; Wed, 17 Nov 2004 18:01:58 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 801FD43D1D for ; Wed, 17 Nov 2004 18:01:58 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id C26211B0; Wed, 17 Nov 2004 12:01:57 -0600 (CST) Date: Wed, 17 Nov 2004 12:01:57 -0600 From: Tillman Hodgson To: FreeBSD -CURRENT Message-ID: <20041117180157.GO76234@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:01:58 -0000 SYNOPSIS: kldload doesn't seem to be able to find the pf module in spite of it being it the normal place. DETAILS: root@thoth# kldstat Id Refs Address Size Name 1 3 0xc0400000 441524 kernel 2 1 0xc17f3000 3000 daemon_saver.ko root@thoth# ls -l /boot/kernel/pf.ko -r-xr-xr-x 1 root wheel 170068 Nov 9 19:12 /boot/kernel/pf.ko root@thoth# kldload -v pf kldload: can't load pf: No such file or directory root@thoth# kldload -v /boot/kernel/pf.ko kldload: can't load /boot/kernel/pf.ko: No such file or directory root@thoth# sysctl kern.bootfile kern.module_path kern.bootfile: /boot/kernel/kernel root@thoth# uname -a FreeBSD thoth.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Nov 9 17:44:22 CST 2004 toor@thoth.seekingfire.com:/usr/obj/usr/src/sys/THOTH i386 Thanks for any assistance, -T -- Page 30: Leaving a terminal logged in is like leaving your car unlocked with the keys in the ignition. - Harley Hahn, _The Unix Companion_ From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:10:20 2004 Return-Path: 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 04DC316A4D0; Wed, 17 Nov 2004 18:10:20 +0000 (GMT) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id D44CA43D45; Wed, 17 Nov 2004 18:10:19 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.247.57] (helo=[192.168.99.66]) by hobbiton.shire.net with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.43) id 1CUUG3-000DsG-Dd; Wed, 17 Nov 2004 11:10:19 -0700 In-Reply-To: <419B2CA6.3010401@freebsd.org> References: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> <419B177D.2090206@DeepCore.dk> <419B2CA6.3010401@freebsd.org> Mime-Version: 1.0 (Apple Message framework v619) Message-Id: From: "Chad Leigh -- Shire.Net LLC" Date: Wed, 17 Nov 2004 11:10:14 -0700 To: Scott Long X-Mailer: Apple Mail (2.619) X-SA-Exim-Connect-IP: 67.161.247.57 X-SA-Exim-Mail-From: chad@shire.net Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on hobbiton.shire.net X-Spam-Status: No, score=-0.3 required=5.0 tests=AWL,BAYES_50 autolearn=disabled version=3.0.0 X-Spam-Level: X-SA-Exim-Version: 4.1+cvs (built Mon, 23 Aug 2004 08:44:05 -0700) X-SA-Exim-Scanned: Yes (on hobbiton.shire.net) cc: current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Marvell SATA Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:10:20 -0000 On Nov 17, 2004, at 3:49 AM, Scott Long wrote: > S=F8ren Schmidt wrote: >> Lawrence Farr wrote: >>> Hello All, >>> >>> I have a Supermicro P4SCT+ with an onboard Marvell >>> SATA controller, which also has the Adaptec Hostraid >>> software raid functionality. Are there any patches to >>> support the marvell controller as a plain controller >>> anywhere? >>> >>> pciconf output if anyones interested: >>> >>> none4@pci2:4:0: class=3D0x010000 card=3D0x504111ab chip=3D0x504111ab=20= >>> rev=3D0x03 >>> hdr=3D0x00 >>> vendor =3D 'Marvell Semiconductor (Was: Galileo Technology = Ltd)' >>> device =3D '88SX504 4-port SATA I PCI-X Controller' >>> class =3D mass storage >>> subclass =3D SCSI >> Not yet, but I'm working on it, actually on the exact same board. >> Maybe, just maybe, you could hack the Highpoint hptmv driver, I=20 >> havn't tried but unless they put in "tricks" to prohibit that it=20 >> should work. > > The hptmv driver only exports raid devices, not single disks, and = those > raid devices have to have HPT metadata on them. The magic here is > buried in the binary object file along with the Herc programming > details, so I don't think it'll be possible to get anything useful out > of it. > uhh, on my system (5.3-STABLE) it exports single disks... I have the=20 RocketRaid1820A and without configuring ANY RAID devices, I got the 3=20 disks showing up and working fine as da0 da1 and da2... Chad From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:11:15 2004 Return-Path: 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 2FE9116A4CE for ; Wed, 17 Nov 2004 18:11:15 +0000 (GMT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17EAB43D41 for ; Wed, 17 Nov 2004 18:11:15 +0000 (GMT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id iAHIB8K24666; Wed, 17 Nov 2004 10:11:08 -0800 (PST) Date: Wed, 17 Nov 2004 10:11:08 -0800 From: Mike Hunter To: Tillman Hodgson Message-ID: <20041117181108.GA24426@ack.Berkeley.EDU> References: <20041117180157.GO76234@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117180157.GO76234@seekingfire.com> User-Agent: Mutt/1.5.6i cc: FreeBSD -CURRENT Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:11:15 -0000 On Nov 17, "Tillman Hodgson" wrote: Check dmesg. There's a bug somewhere that causes kldload to report "file not found" to the user even though it was some other error that caused the problem. That real error can sometimes be spit out to the console / syslog / whatever. > SYNOPSIS: > > kldload doesn't seem to be able to find the pf module in spite of it > being it the normal place. > > DETAILS: > > root@thoth# kldstat > Id Refs Address Size Name > 1 3 0xc0400000 441524 kernel > 2 1 0xc17f3000 3000 daemon_saver.ko > > root@thoth# ls -l /boot/kernel/pf.ko > -r-xr-xr-x 1 root wheel 170068 Nov 9 19:12 /boot/kernel/pf.ko > > root@thoth# kldload -v pf > kldload: can't load pf: No such file or directory > > root@thoth# kldload -v /boot/kernel/pf.ko > kldload: can't load /boot/kernel/pf.ko: No such file or directory > > root@thoth# sysctl kern.bootfile kern.module_path > kern.bootfile: /boot/kernel/kernel > > root@thoth# uname -a > FreeBSD thoth.seekingfire.prv 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Tue Nov 9 17:44:22 CST 2004 > toor@thoth.seekingfire.com:/usr/obj/usr/src/sys/THOTH i386 From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:17:30 2004 Return-Path: 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 BA91816A4CE for ; Wed, 17 Nov 2004 18:17:30 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2104B43D55 for ; Wed, 17 Nov 2004 18:17:30 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAHIJbuh031035; Wed, 17 Nov 2004 11:19:37 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <419B95E1.5030503@freebsd.org> Date: Wed, 17 Nov 2004 11:18:09 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Chad Leigh -- Shire.Net LLC" References: <20041116145445.EC71167E2B@gunfright.epcdirect.co.uk> <419B177D.2090206@DeepCore.dk> <419B2CA6.3010401@freebsd.org> In-Reply-To: X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: Marvell SATA Support X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:17:30 -0000 Chad Leigh -- Shire.Net LLC wrote: > > On Nov 17, 2004, at 3:49 AM, Scott Long wrote: > >> Søren Schmidt wrote: >> >>> Lawrence Farr wrote: >>> >>>> Hello All, >>>> >>>> I have a Supermicro P4SCT+ with an onboard Marvell >>>> SATA controller, which also has the Adaptec Hostraid >>>> software raid functionality. Are there any patches to >>>> support the marvell controller as a plain controller >>>> anywhere? >>>> >>>> pciconf output if anyones interested: >>>> >>>> none4@pci2:4:0: class=0x010000 card=0x504111ab chip=0x504111ab rev=0x03 >>>> hdr=0x00 >>>> vendor = 'Marvell Semiconductor (Was: Galileo Technology Ltd)' >>>> device = '88SX504 4-port SATA I PCI-X Controller' >>>> class = mass storage >>>> subclass = SCSI >>> >>> Not yet, but I'm working on it, actually on the exact same board. >>> Maybe, just maybe, you could hack the Highpoint hptmv driver, I >>> havn't tried but unless they put in "tricks" to prohibit that it >>> should work. >> >> >> The hptmv driver only exports raid devices, not single disks, and those >> raid devices have to have HPT metadata on them. The magic here is >> buried in the binary object file along with the Herc programming >> details, so I don't think it'll be possible to get anything useful out >> of it. >> > > uhh, on my system (5.3-STABLE) it exports single disks... I have the > RocketRaid1820A and without configuring ANY RAID devices, I got the 3 > disks showing up and working fine as da0 da1 and da2... > > Chad > > Bah, you're right, I wasn't thinking correctly when I wrote that. Sorry. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 18:28:38 2004 Return-Path: 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 863DD16A4CE for ; Wed, 17 Nov 2004 18:28:38 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 709FB43D58 for ; Wed, 17 Nov 2004 18:28:38 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4761272DD4; Wed, 17 Nov 2004 10:28:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 4585172DCB; Wed, 17 Nov 2004 10:28:38 -0800 (PST) Date: Wed, 17 Nov 2004 10:28:38 -0800 (PST) From: Doug White To: Sean McNeil In-Reply-To: <1100657472.74795.2.camel@server.mcneil.com> Message-ID: <20041117102623.P25028@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 18:28:38 -0000 On Tue, 16 Nov 2004, Sean McNeil wrote: > This has been happening for a long time with current and hasn't been > resolved. When I start up slapd, I cannot stop it without kill -9 ing > it. It would appear stuck in kse and probably has something to do with > kill -0: Mind expanding on this? The backtrace looks normal for a pthread process. kill -0 just tests signal delivery; the process is completely unaware that the probe occured, though. The process may also be unkillable if its stuck in some sort of I/O wait. Is the server busy when you signal it? > > (gdb) bt > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > #1 0x0000000801428e49 in kse_wait (kse=0x62a000, td_wait=0x0, > sigseqno=0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > #2 0x0000000801427078 in kse_sched_multi (kmbx=0x62efa0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > #3 0x000000080142afbf in _amd64_enter_uts () > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > #4 0x0000000000000000 in ?? () > #5 0x000000000062f000 in ?? () > #6 0x000000000062a000 in ?? () > #7 0x0000000000000000 in ?? () > #8 0x0000000000000000 in ?? () > #9 0x0000000000000000 in ?? () > #10 0x0000000000000000 in ?? () > #11 0x0000000000000000 in ?? () > #12 0x0000000000000001 in ?? () > #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () > at /usr/src/lib/libpthread/thread/thr_kern.c:904 > Previous frame inner to this frame (corrupt stack?) > > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 19:31:29 2004 Return-Path: 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 B099C16A4CE for ; Wed, 17 Nov 2004 19:31:29 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E90A643D39 for ; Wed, 17 Nov 2004 19:31:19 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 6B8311C1; Wed, 17 Nov 2004 13:31:19 -0600 (CST) Date: Wed, 17 Nov 2004 13:31:19 -0600 From: Tillman Hodgson To: FreeBSD -CURRENT Message-ID: <20041117193119.GP76234@seekingfire.com> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117181108.GA24426@ack.Berkeley.EDU> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 19:31:29 -0000 On Wed, Nov 17, 2004 at 10:11:08AM -0800, Mike Hunter wrote: > Check dmesg. There's a bug somewhere that causes kldload to report "file > not found" to the user even though it was some other error that caused the > problem. That real error can sometimes be spit out to the console / > syslog / whatever. Oh! I should have checked syslog, my apologies. Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. My custom kernel doesn't include IPv6. Does pf truly require IPv6?: -T -- In the beginner's mind there are many possibilities. In the expert's mind there are few. - Suzuki-roshi From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 20:14:36 2004 Return-Path: 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 F05D816A4D0; Wed, 17 Nov 2004 20:14:36 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 75CAE43D1D; Wed, 17 Nov 2004 20:14:36 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222])iAHKELDU032024; Wed, 17 Nov 2004 15:14:22 -0500 Message-ID: <419BB117.4070802@root.org> Date: Wed, 17 Nov 2004 12:14:15 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?S=F8ren_Schmidt?= References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr> <20041117081007.GC95090@laptop.6bone.nl> <419B194E.5090800@DeepCore.dk> In-Reply-To: <419B194E.5090800@DeepCore.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:14:37 -0000 Søren Schmidt wrote: > There are nasties in the bat stuff, I have to comment out various parts > of it to get the ASUS to boot at all :( > > > This brings up the question: do we have a maintainer for ACPI and why > arent these issues being dealt with ? I for one have reported these > issue for ages including as much debug as is possible, but it seems to > be silently ignored (and yes 5.3-RELEASE is just as broken)... > cvs logs will show who is active in each area of acpi. I'm sure that's a rhetorical question though. As for your particular problems, the battery issue may be related to your system not operating according to the locking model. I fixed one thermal problem for brooks@ where his ASL generated notifies every time we read the temperature and the notify handler read the temperature. It may be something similar. Send me the ASL and I'll take a look. The suspend/resume issue has not been isolated but you can start by checking where it gets with a serial console attached (if it gets that far) or by putting some beep code in the resume handler to see if it even gets called (Warner has the patch in his tree, it may make sense to commit it under some option to help with debugging.) I'd love it if more people would help with debugging. I'm sure you can relate to maintaining a subsystem where behavior is widely divergent even among the same model device, OEM bugs are rampant and undocumented, and you don't have access to a system that can repeat the behavior that the submitter is reporting. As donations@ shows, I'm willing to accept problem laptops on loan or for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit SMP. All work correctly including suspend/resume to RAM for the laptops. -Nate From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 20:35:57 2004 Return-Path: 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 706DA16A4CE for ; Wed, 17 Nov 2004 20:35:57 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 223BA43D2F for ; Wed, 17 Nov 2004 20:35:57 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id D0130F20CC; Wed, 17 Nov 2004 12:35:56 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13696-07; Wed, 17 Nov 2004 12:35:48 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id CFD5DF207C; Wed, 17 Nov 2004 12:35:47 -0800 (PST) From: Sean McNeil To: Dick Davies In-Reply-To: <20041117135058.GB28461@lb.tenfour> References: <419B3DA9.8020202@fer.hr> <20041117135058.GB28461@lb.tenfour> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-xRiI3PtSTGkJadsgLx3i" Date: Wed, 17 Nov 2004 12:35:47 -0800 Message-Id: <1100723747.18003.4.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: FreeBSD Current Users cc: Ivan Voras Subject: Re: openldap slapd startup delay X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:35:57 -0000 --=-xRiI3PtSTGkJadsgLx3i Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-11-17 at 13:50 +0000, Dick Davies wrote: > * Ivan Voras [1124 13:24]: > > I'm running pam_ldap & nss_ldap fine, but there's a huge delay when=20 > > slapd starts (upto 30sec.). During the delay there's no load on the=20 > > machine, and it's listening on hosts that are name-resolvable via=20 > > /etc/hosts (it has priority in /etc/nsswitch.conf). >=20 > I saw this for the past three weeks - it appears to be a problem with > the rc script. If you run 'ps awwux'and copy the command line shown to > a script, it starts straight away. >=20 >=20 > I replaced it with this, which starts instantly : >=20 >=20 > root@eris exim # less /usr/local/etc/rc.d/000._slappy.sh=20 > #!/bin/sh >=20 > # please don't mistake me for someone who gives a shit that I check a pid= file > # twice in the stop function, I am too old and lazy to learn shell. >=20 >=20 > DAEMON=3D"/usr/local/libexec/slapd" > PIDFILE=3D"/var/run/openldap/slapd.pid" > CFG=3D"/usr/local/etc/openldap/slapd.conf" > FLAGS=3D'-h ldaps://ldap.domain/ ldap://ldap.domain -u ldap -g ldap' >=20 >=20 > case $1 in > start) > [ -x ${DAEMON} ] && { > echo -n ' starting slapd' > ${DAEMON} ${FLAGS} > } > ;; >=20 > stop) > [ -f ${PIDFILE} ] || ( echo ' slapd not running? (no ${PIDFILE})' && = exit ) > [ -f ${PIDFILE} ] && { > echo -n ' stopping slapd' > kill `cat ${PIDFILE}` > } > ;; >=20 > restart) > stop > start > ;; >=20 > *) > echo "usage: `basename $0` {start|stop|restart}" >&2 > exit 64 > ;; > esac Does this fix the start delay, or the problem with stop? I have traced through the start delay and found it is because slapd is opening the socket and then there is a lookup on group which causes it to try to read from slapd and you are in a deadlock until the socket times out. This has always been normal for me (the delay on startup) and others. Sean --=-xRiI3PtSTGkJadsgLx3i Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm7YjyQsGN30uGE4RAhwUAJ4oDJ4Nra9FrtGmKdEhjSGLKQQkqwCfeF3m qasohNBcY3dd6i5NggK6Jgs= =TSCg -----END PGP SIGNATURE----- --=-xRiI3PtSTGkJadsgLx3i-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 20:56:51 2004 Return-Path: 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 66FDB16A4CE for ; Wed, 17 Nov 2004 20:56:51 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1BF1943D45 for ; Wed, 17 Nov 2004 20:56:51 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id CF865F2082; Wed, 17 Nov 2004 12:56:50 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 13391-10; Wed, 17 Nov 2004 12:56:48 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id C0221F1802; Wed, 17 Nov 2004 12:56:48 -0800 (PST) From: Sean McNeil To: Doug White In-Reply-To: <20041117102623.P25028@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> <20041117102623.P25028@carver.gumbysoft.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Bsflrd6qJ12gUDoJBBUP" Date: Wed, 17 Nov 2004 12:56:48 -0800 Message-Id: <1100725008.21333.2.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 20:56:51 -0000 --=-Bsflrd6qJ12gUDoJBBUP Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-11-17 at 10:28 -0800, Doug White wrote:=20 > On Tue, 16 Nov 2004, Sean McNeil wrote: >=20 > > This has been happening for a long time with current and hasn't been > > resolved. When I start up slapd, I cannot stop it without kill -9 ing > > it. It would appear stuck in kse and probably has something to do with > > kill -0: >=20 > Mind expanding on this? The backtrace looks normal for a pthread process. > kill -0 just tests signal delivery; the process is completely unaware tha= t > the probe occured, though. The process may also be unkillable if its > stuck in some sort of I/O wait. >=20 > Is the server busy when you signal it? Oh, OK. I didn't look at /usr/local/etc/rc.subr too closely. I have additional information, though.... It appears that all the threads are destroyed yet it is still in the thread processing loop. The process is no longer active at all. I just had a similar problem happen with vlc where I closed it yet it is hanging in the same place as slapd with all the threads gone. Here is the one from vlc: (gdb) bt full #0 _thr_sched_switch_unlocked (curthread=3D0x955000) at pthread_md.h:226 psf =3D {psf_valid =3D 0, psf_flags =3D 0, psf_cancelflags =3D 2995= 2806, psf_interrupted =3D 8, psf_timeout =3D 11279168, psf_signo =3D 0, psf_state =3D 11279168, psf_wait_data =3D {mutex =3D 0x8, cond =3D 0x8, l= ock =3D 0x8, sigwait =3D 0x8}, psf_wakeup_time =3D {tv_sec =3D 0, tv_nsec =3D 0}, psf_sigset =3D { __bits =3D {29950366, 8, 9860096, 0}}, psf_sigmask =3D {__bits =3D {9752576, 1, 9860096, 0}}, psf_seqno =3D 29995347} curkse =3D (struct kse *) 0x952000 resume_once =3D 0 #1 0x0000000801c925e0 in _thr_sched_switch (curthread=3D0x955000) at /usr/src/lib/libpthread/thread/thr_kern.c:607 No locals. #2 0x0000000801c85cb4 in _pthread_join (pthread=3D0x967400, thread_return=3D0x0) at /usr/src/lib/libpthread/thread/thr_join.c:133 curthread =3D (struct pthread *) 0x955000 tmp =3D (void *) 0x0 crit =3D 0x0 ret =3D 0 #3 0x0000000000431749 in __vlc_thread_join (p_this=3D0xad4800, psz_file=3D0x6a283c "src/playlist/playlist.c", i_line=3D130) at src/misc/threads.c:716 i_ret =3D 1 #4 0x000000000040ee1a in playlist_Destroy (p_playlist=3D0xad4800) ---Type to continue, or q to quit--- at src/playlist/playlist.c:130 No locals. #5 0x000000000040c400 in VLC_CleanUp (i_object=3D0) at src/libvlc.c:831 p_intf =3D (intf_thread_t *) 0xad4800 p_playlist =3D (playlist_t *) 0xad4800 p_vout =3D (vout_thread_t *) 0xad4800 p_aout =3D (aout_instance_t *) 0xad4800 p_announce =3D (announce_handler_t *) 0xad4800 p_vlc =3D (vlc_t *) 0x94d400 #6 0x0000000000407415 in main (i_argc=3D1, ppsz_argv=3D0x7fffffffe940) at src/vlc.c:108 i_ret =3D 0 and here is a full trace of slapd: (gdb) bt full #0 0x000000080142e914 in kse_release () at kse_release.S:2 No locals. #1 0x0000000801428e49 in kse_wait (kse=3D0x62a000, td_wait=3D0x0, sigseqno=3D0) at /usr/src/lib/libpthread/thread/thr_kern.c:1843 ts =3D {tv_sec =3D 7647232, tv_nsec =3D 7647232} ts_sleep =3D {tv_sec =3D 60, tv_nsec =3D 0} saved_flags =3D 0 #2 0x0000000801427078 in kse_sched_multi (kmbx=3D0x62efa0) at /usr/src/lib/libpthread/thread/thr_kern.c:1039 curkse =3D (struct kse *) 0x62a000 curthread =3D (struct pthread *) 0x0 td_wait =3D (struct pthread *) 0x62a068 curframe =3D (struct pthread_sigframe *) 0x17f ret =3D 383 #3 0x000000080142afbf in _amd64_enter_uts () at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 No locals. #4 0x0000000000000000 in ?? () No symbol table info available. #5 0x000000000062f000 in ?? () No symbol table info available. #6 0x000000000062a000 in ?? () No symbol table info available. ---Type to continue, or q to quit--- #7 0x0000000000000000 in ?? () No symbol table info available. #8 0x0000000000000000 in ?? () No symbol table info available. #9 0x0000000000000000 in ?? () No symbol table info available. #10 0x0000000000000000 in ?? () No symbol table info available. #11 0x0000000000000000 in ?? () No symbol table info available. #12 0x0000000000000001 in ?? () No symbol table info available. #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () at /usr/src/lib/libpthread/thread/thr_kern.c:904 free_kseq =3D {tqh_first =3D 0x0, tqh_last =3D 0x801534810} gc_ksegq =3D {tqh_first =3D 0x0, tqh_last =3D 0x801534840} next_uniqueid =3D 7 active_kse_groupq =3D {tqh_first =3D 0x62f100, tqh_last =3D 0x74802= 0} active_kse_count =3D 2 free_threadq =3D {tqh_first =3D 0x0, tqh_last =3D 0x801534890} free_kse_count =3D 0 active_kseq =3D {tqh_first =3D 0x62a000, tqh_last =3D 0x6c9220} free_kse_groupq =3D {tqh_first =3D 0x0, tqh_last =3D 0x801534820} ---Type to continue, or q to quit--- kse_lock =3D {l_head =3D 0x6291c0, l_tail =3D 0x6291c0, l_type =3D LCK_ADAPTIVE, l_wait =3D 0x801426150 <_kse_lock_wait>, l_wakeup =3D 0x8014261e0 <_kse_lock_wakeup>} active_kseg_count =3D 2 inited =3D 1 free_thread_count =3D 0 free_kseg_count =3D 0 thr_hashtable =3D {{lh_first =3D 0x0} , { lh_first =3D 0x6c3c00}, {lh_first =3D 0x0}, {lh_first =3D 0x0}, { lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first =3D 0x1874400}, { lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first = =3D 0x0}, { lh_first =3D 0x74b000}, {lh_first =3D 0x0} , { lh_first =3D 0x74b800}, {lh_first =3D 0x0}, {lh_first =3D 0x0}, { lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first = =3D 0x0}, { lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first =3D 0x632000}, { lh_first =3D 0x0} , {lh_first =3D 0x29ab400}, { lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first =3D 0x0}, {lh_first = =3D 0x0}, { lh_first =3D 0x0}, {lh_first =3D 0x2983c00}, { lh_first =3D 0x0} } thread_lock =3D {l_head =3D 0x6291e0, l_tail =3D 0x6291e0, l_type =3D LCK_ADAPTIVE, l_wait =3D 0x801426150 <_kse_lock_wait>, l_wakeup =3D 0x8014261e0 <_kse_lock_wakeup>} _tcb_mutex =3D 0x628380 Previous frame inner to this frame (corrupt stack?) which looks like total garbage. Looking at each thread I see that there is only a thread 1,2, and 3: (gdb) thread 1 [Switching to thread 1 (Thread 6 (LWP 100177))]#0 0x000000080142e914 in kse_release () at kse_release.S:2 2 RSYSCALL(kse_release) (gdb) bt #0 0x000000080142e914 in kse_release () at kse_release.S:2 #1 0x000000080141d926 in sig_daemon (arg=3D0x7fffffefef70) at /usr/src/lib/libpthread/thread/thr_sig.c:216 #2 0x0000000801426db5 in kse_sched_single (kmbx=3D0x7fffffefef70) at /usr/src/lib/libpthread/thread/thr_kern.c:902 (gdb) thread 2 [Switching to thread 2 (Thread 7 (sleeping))]#0 _thr_sched_switch_unlocked ( curthread=3D0x632000) at pthread_md.h:226 226 if (ret =3D=3D 0) { Current language: auto; currently c (gdb) bt #0 _thr_sched_switch_unlocked (curthread=3D0x632000) at pthread_md.h:226 #1 0x00000008014265e0 in _thr_sched_switch (curthread=3D0x632000) at /usr/src/lib/libpthread/thread/thr_kern.c:607 #2 0x0000000801419cb4 in _pthread_join (pthread=3D0x74b000, thread_return=3D0x0) at /usr/src/lib/libpthread/thread/thr_join.c:133 #3 0x0000000800719d09 in ldap_pvt_thread_join (thread=3D0x800609070, thread_return=3D0x62a068) at thr_posix.c:165 (gdb) thread 3 [Switching to thread 3 (LWP 100148)]#0 0x000000080142e914 in kse_release () at kse_release.S:2 2 RSYSCALL(kse_release) Current language: auto; currently asm (gdb) bt #0 0x000000080142e914 in kse_release () at kse_release.S:2 #1 0x0000000801428e49 in kse_wait (kse=3D0x62a000, td_wait=3D0x0, sigseqno=3D0) at /usr/src/lib/libpthread/thread/thr_kern.c:1843 #2 0x0000000801427078 in kse_sched_multi (kmbx=3D0x62efa0) at /usr/src/lib/libpthread/thread/thr_kern.c:1039 #3 0x000000080142afbf in _amd64_enter_uts () at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > > > > (gdb) bt > > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > > #1 0x0000000801428e49 in kse_wait (kse=3D0x62a000, td_wait=3D0x0, > > sigseqno=3D0) > > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > > #2 0x0000000801427078 in kse_sched_multi (kmbx=3D0x62efa0) > > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > > #3 0x000000080142afbf in _amd64_enter_uts () > > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > > #4 0x0000000000000000 in ?? () > > #5 0x000000000062f000 in ?? () > > #6 0x000000000062a000 in ?? () > > #7 0x0000000000000000 in ?? () > > #8 0x0000000000000000 in ?? () > > #9 0x0000000000000000 in ?? () > > #10 0x0000000000000000 in ?? () > > #11 0x0000000000000000 in ?? () > > #12 0x0000000000000001 in ?? () > > #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () > > at /usr/src/lib/libpthread/thread/thr_kern.c:904 > > Previous frame inner to this frame (corrupt stack?) > > > > >=20 --=-Bsflrd6qJ12gUDoJBBUP Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm7sQyQsGN30uGE4RAuPxAJ9L47eUGY0C1AVjeU1NDPsB4eoQ9gCeK2Bs zy6uxbU+YyeznhOvYDbfL4A= =ENVQ -----END PGP SIGNATURE----- --=-Bsflrd6qJ12gUDoJBBUP-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 21:19:45 2004 Return-Path: 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 F0A9A16A4D0; Wed, 17 Nov 2004 21:19:44 +0000 (GMT) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9873243D58; Wed, 17 Nov 2004 21:19:44 +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 id IBA74465; Wed, 17 Nov 2004 13:19:44 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E583E5D0A; Wed, 17 Nov 2004 13:19:43 -0800 (PST) To: Nate Lawson In-reply-to: Your message of "Wed, 17 Nov 2004 12:14:15 PST." <419BB117.4070802@root.org> Date: Wed, 17 Nov 2004 13:19:43 -0800 From: "Kevin Oberman" Message-Id: <20041117211943.E583E5D0A@ptavv.es.net> cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:19:45 -0000 > Date: Wed, 17 Nov 2004 12:14:15 -0800 > From: Nate Lawson > Sender: owner-freebsd-acpi@freebsd.org > > Søren Schmidt wrote: > > There are nasties in the bat stuff, I have to comment out various parts > > of it to get the ASUS to boot at all :( > > > > > > This brings up the question: do we have a maintainer for ACPI and why > > arent these issues being dealt with ? I for one have reported these > > issue for ages including as much debug as is possible, but it seems to > > be silently ignored (and yes 5.3-RELEASE is just as broken)... > > > > cvs logs will show who is active in each area of acpi. I'm sure that's > a rhetorical question though. > > As for your particular problems, the battery issue may be related to > your system not operating according to the locking model. I fixed one > thermal problem for brooks@ where his ASL generated notifies every time > we read the temperature and the notify handler read the temperature. It > may be something similar. Send me the ASL and I'll take a look. The > suspend/resume issue has not been isolated but you can start by checking > where it gets with a serial console attached (if it gets that far) or by > putting some beep code in the resume handler to see if it even gets > called (Warner has the patch in his tree, it may make sense to commit it > under some option to help with debugging.) > > I'd love it if more people would help with debugging. I'm sure you can > relate to maintaining a subsystem where behavior is widely divergent > even among the same model device, OEM bugs are rampant and undocumented, > and you don't have access to a system that can repeat the behavior that > the submitter is reporting. > > As donations@ shows, I'm willing to accept problem laptops on loan or > for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit > SMP. All work correctly including suspend/resume to RAM for the laptops. Nate, Does the sound work properly on the R32 and T23 after S3 resume? I suspect the problem with my system is limited to very few models, maybe just the T30 and R40. It only shows up in that sound plays too fast (at the raw device rate rather then the programmed rate). I do suspect that this is a PCI power issue and not an ACPI issue, but I'd like to know if it shows up on more models. It is most obvious when playing a stream as the buffers keep emptying and the sound stops after a short time. Music is clearly too fast and high pitched, but at 10% overspeed, some may not notice. (Does Dr. Dre sound much different 10% faster?) -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 21:26:21 2004 Return-Path: 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 4F25616A4CE; Wed, 17 Nov 2004 21:26:21 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1336243D55; Wed, 17 Nov 2004 21:26:21 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAHLQ1C4010485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 13:26:02 -0800 Message-ID: <419BC1DC.7080603@root.org> Date: Wed, 17 Nov 2004 13:25:48 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kevin Oberman References: <20041117211943.E583E5D0A@ptavv.es.net> In-Reply-To: <20041117211943.E583E5D0A@ptavv.es.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 21:26:21 -0000 Kevin Oberman wrote: >>Date: Wed, 17 Nov 2004 12:14:15 -0800 >>From: Nate Lawson >>I'd love it if more people would help with debugging. I'm sure you can >>relate to maintaining a subsystem where behavior is widely divergent >>even among the same model device, OEM bugs are rampant and undocumented, >>and you don't have access to a system that can repeat the behavior that >>the submitter is reporting. >> >>As donations@ shows, I'm willing to accept problem laptops on loan or >>for donation. Currently, I own an IBM R32, T23, Sony PCG-F390, and Abit >>SMP. All work correctly including suspend/resume to RAM for the laptops. > > Does the sound work properly on the R32 and T23 after S3 resume? I > suspect the problem with my system is limited to very few models, maybe > just the T30 and R40. It only shows up in that sound plays too fast (at > the raw device rate rather then the programmed rate). > > I do suspect that this is a PCI power issue and not an ACPI issue, but > I'd like to know if it shows up on more models. It is most obvious when > playing a stream as the buffers keep emptying and the sound stops after > a short time. Music is clearly too fast and high pitched, but at 10% > overspeed, some may not notice. (Does Dr. Dre sound much different 10% > faster?) I've tested sound thoroughly on my ICH3M system (T23) and it works exactly the same before and after suspend. I had a problem about a year ago where it would hang and stop delivering interrupts a short time after playing music after resume but that was fixed by Warner's pci power commit. I haven't tested the R32 sound after resume but will check it. It's probably similar to your R40 so it may exhibit the same problem. It's my wife's so I have to be able to grab it from her and reboot to FreeBSD to test. :) -- Nate From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:12:38 2004 Return-Path: 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 C194E16A4CE for ; Wed, 17 Nov 2004 22:12:38 +0000 (GMT) Received: from av7-2-sn1.fre.skanova.net (av7-2-sn1.fre.skanova.net [81.228.11.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 166A343D54 for ; Wed, 17 Nov 2004 22:12:36 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-2-sn1.fre.skanova.net (Postfix, from userid 502) id 3F86338106; Wed, 17 Nov 2004 23:12:35 +0100 (CET) Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163]) by av7-2-sn1.fre.skanova.net (Postfix) with ESMTP id 3053A37EA6 for ; Wed, 17 Nov 2004 23:12:35 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp3-1-sn1.fre.skanova.net (Postfix) with ESMTP id 1C6FD37E46 for ; Wed, 17 Nov 2004 23:12:35 +0100 (CET) From: "Daniel Eriksson" To: Date: Wed, 17 Nov 2004 23:12:31 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Thread-Index: AcTMlYq7bsZgjuZ/Qn2QnvJiCjO8NgAXIgwg In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Subject: RE: uma_zfree_internal crash, if_em related? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:12:38 -0000 I wrote: > After upgrading my 6-CURRENT box to 2004.11.14.16.00.00 (and also > 2004.11.16.19.15.00), I have encountered this crash twice in > 24 hours. [...] > Stopped at uma_zfree_internal+0xcc: movl %edx,0(%eax) It is possible that this error was hardware related. Earlier today one stick of RAM went completely nuts and had to be replaced. The errors I reported could have been early effects of the RAM going bad. If I see the same problem again I'll post another report in this thread. /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:57:51 2004 Return-Path: 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 EB02A16A4FB for ; Wed, 17 Nov 2004 22:57:51 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 91D0243D2F for ; Wed, 17 Nov 2004 22:57:50 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 30150 invoked by uid 65534); 17 Nov 2004 22:57:49 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp010) with SMTP; 17 Nov 2004 23:57:49 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Wed, 17 Nov 2004 23:57:41 +0100 User-Agent: KMail/1.7 X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart8094321.VeYSp2vXmv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411172357.47735.Emanuel.Strobl@gmx.net> cc: freebsd-current@freebsd.org Subject: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:57:52 -0000 --nextPart8094321.VeYSp2vXmv Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear best guys, I really love 5.3 in many ways but here're some unbelievable transfer rates= ,=20 after I went out and bought a pair of Intel GigaBit Ethernet Cards to solve= =20 my performance problem (*laugh*): (In short, see *** below) Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit PCI=20 Desktop adapter MT) connected directly without a switch/hub and "device=20 polling" compiled into a custom kernel with HZ set to 256 and=20 kern.polling.enabled set to "1": LOCAL: (/samsung is ufs2 on /dev/ad4p1, a SAMSUNG SP080N2) test3:~#7: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k ^C10524+0 records in 10524+0 records out 172425216 bytes transferred in 3.284735 secs (52492882 bytes/sec) =2D> ^^^^^^^^ ~ 52MB/s NFS(udp,polling): (/samsung is nfs on test3:/samsung, via em0, x-over, polling enabled) test2:/#21: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k ^C1858+0 records in 1857+0 records out 30425088 bytes transferred in 8.758475 secs (3473788 bytes/sec) =2D> ^^^^^^^ ~ 3,4MB/s This example shows that using NFS over GigaBit Ethernet decimates performan= ce=20 by the factor of 15, in words fifteen! GGATE with MTU 16114 and polling: test2:/dev#28: ggatec create 10.0.0.2 /dev/ad4p1 ggate0 test2:/dev#29: mount /dev/ggate0 /samsung/ test2:/dev#30: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k ^C2564+0 records in 2563+0 records out 41992192 bytes transferred in 15.908581 secs (2639594 bytes/sec) =2D> ^^^^^^^ ~ 2,6MB/s GGATE without polling and MTU 16114: test2:~#12: ggatec create 10.0.0.2 /dev/ad4p1 ggate0 test2:~#13: mount /dev/ggate0 /samsung/ test2:~#14: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D128k ^C1282+0 records in 1281+0 records out 167903232 bytes transferred in 11.274768 secs (14891945 bytes/sec) =2D> ^^^^^^^^ ~ 15MB/s =2E....and with 1m blocksize: test2:~#17: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D1m ^C61+0 records in 60+0 records out 62914560 bytes transferred in 4.608726 secs (13651182 bytes/sec) =2D> ^^^^^^^^ ~ 13,6MB/s I can't imagine why there seems to be a absolute limit of 15MB/s that can b= e=20 transfered over the network But it's even worse, here two excerpts of NFS (udp) with jumbo Frames=20 (mtu=3D16114): test2:~#23: mount 10.0.0.2:/samsung /samsung/ test2:~#24: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D1m ^C89+0 records in 88+0 records out 92274688 bytes transferred in 13.294708 secs (6940708 bytes/sec) =2D> ^^^^^^^ ~7MB/s =2E....and with 64k blocksize: test2:~#25: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k ^C848+0 records in 847+0 records out 55508992 bytes transferred in 8.063415 secs (6884055 bytes/sec) And with TCP-NFS (and Jumbo Frames): test2:~#30: mount_nfs -T 10.0.0.2:/samsung /samsung/ test2:~#31: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k ^C1921+0 records in 1920+0 records out 125829120 bytes transferred in 7.461226 secs (16864403 bytes/sec) =2D> ^^^^^^^^ ~ 17MB/s Again NFS (udp) but with MTU 1500: test2:~#9: mount_nfs 10.0.0.2:/samsung /samsung/ test2:~#10: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D8k ^C12020+0 records in 12019+0 records out 98459648 bytes transferred in 10.687460 secs (9212633 bytes/sec) =2D> ^^^^^^^ ~ 10MB/s And TCP-NFS with MTU 1500: test2:~#12: mount_nfs -T 10.0.0.2:/samsung /samsung/ test2:~#13: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D8k ^C19352+0 records in 19352+0 records out 158531584 bytes transferred in 12.093529 secs (13108794 bytes/sec) =2D> ^^^^^^^^ ~ 13MB/s GGATE with default MTU of 1500, polling disabled: test2:~#14: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k ^C971+0 records in 970+0 records out 63569920 bytes transferred in 6.274578 secs (10131346 bytes/sec) =2D> ^^^^^^^^ ~ 10M/s Conclusion: *** =2D It seems that GEOM_GATE is less efficient with GigaBit (em) than NFS vi= a TCP=20 is. =2D em seems to have problems with MTU greater than 1500 =2D UDP seems to have performance disadvantages over TCP regarding NFS whic= h=20 should be vice versa AFAIK =2D polling and em (GbE) with HZ=3D256 is definitly no good idea, even 10Ba= se-2=20 can compete =2D NFS over TCP with MTU of 16114 gives the maximum transferrate for large= =20 files over GigaBit Ethernet with a value of 17MB/s, a quarter of what I'd=20 expect with my test equipment. =2D overall network performance (regarding large file transfers) is horrible Please, if anybody has the knowledge to dig into these problems, let me kno= w=20 if I can do any tests to help getting ggate and NFS useful in fast 5.3-stab= le=20 environments. Best regards, =2DHarry --nextPart8094321.VeYSp2vXmv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm9drBylq0S4AzzwRAljpAJ0VnUnFyfiS6xz2NyErHaS1mdnz0QCaAuyR wSvMpSbvASM/3eTX2OEQ3tU= =wF3T -----END PGP SIGNATURE----- --nextPart8094321.VeYSp2vXmv-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 22:57:59 2004 Return-Path: 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 319C316A52F for ; Wed, 17 Nov 2004 22:57:59 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5D4ED43D5D for ; Wed, 17 Nov 2004 22:57:58 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b207.otenet.gr [212.205.244.215]) iAHMvskQ000639; Thu, 18 Nov 2004 00:57:55 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id iAHMvZrC002212; Thu, 18 Nov 2004 00:57:35 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id iAHMvZ8H002211; Thu, 18 Nov 2004 00:57:35 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 18 Nov 2004 00:57:35 +0200 From: Giorgos Keramidas To: Tillman Hodgson Message-ID: <20041117225735.GA2148@gothmog.gr> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> <20041117193119.GP76234@seekingfire.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117193119.GP76234@seekingfire.com> cc: freebsd-current@freebsd.org Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 22:57:59 -0000 On 2004-11-17 13:31, Tillman Hodgson wrote: > On Wed, Nov 17, 2004 at 10:11:08AM -0800, Mike Hunter wrote: > > Check dmesg. There's a bug somewhere that causes kldload to report "file > > not found" to the user even though it was some other error that caused the > > problem. That real error can sometimes be spit out to the console / > > syslog / whatever. > > Oh! I should have checked syslog, my apologies. > > Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined > Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. > > My custom kernel doesn't include IPv6. Does pf truly require IPv6?: Yes, if you want to load it as a module. This is exactly the same thing I bumped into last night. Compiling a kernel with INET6 support will let you load pf as a module. I'm not sure if this is a `bug' that neds fixing though ;-) From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 23:17:24 2004 Return-Path: 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 3D09416A4CE; Wed, 17 Nov 2004 23:17:24 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF39343D39; Wed, 17 Nov 2004 23:17:23 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 9AB14F20AD; Wed, 17 Nov 2004 15:17:21 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22381-07; Wed, 17 Nov 2004 15:17:19 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id A0F8EF18DB; Wed, 17 Nov 2004 15:17:19 -0800 (PST) From: Sean McNeil To: Emanuel Strobl In-Reply-To: <200411172357.47735.Emanuel.Strobl@gmx.net> References: <200411172357.47735.Emanuel.Strobl@gmx.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-hcHwgO70AgenjjKR2nD0" Date: Wed, 17 Nov 2004 15:17:19 -0800 Message-Id: <1100733439.21798.36.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 23:17:24 -0000 --=-hcHwgO70AgenjjKR2nD0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-11-17 at 23:57 +0100, Emanuel Strobl wrote: > Dear best guys, >=20 > I really love 5.3 in many ways but here're some unbelievable transfer rat= es,=20 > after I went out and bought a pair of Intel GigaBit Ethernet Cards to sol= ve=20 > my performance problem (*laugh*): >=20 > (In short, see *** below) >=20 > Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit PCI= =20 > Desktop adapter MT) connected directly without a switch/hub and "device=20 > polling" compiled into a custom kernel with HZ set to 256 and=20 > kern.polling.enabled set to "1": >=20 > LOCAL: > (/samsung is ufs2 on /dev/ad4p1, a SAMSUNG SP080N2) > test3:~#7: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k > ^C10524+0 records in > 10524+0 records out > 172425216 bytes transferred in 3.284735 secs (52492882 bytes/sec) > -> > ^^^^^^^^ ~ 52MB/s > NFS(udp,polling): > (/samsung is nfs on test3:/samsung, via em0, x-over, polling enabled) > test2:/#21: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k > ^C1858+0 records in > 1857+0 records out > 30425088 bytes transferred in 8.758475 secs (3473788 bytes/sec) > -> ^^^^^^^ ~ 3,4MB/s >=20 > This example shows that using NFS over GigaBit Ethernet decimates perform= ance=20 > by the factor of 15, in words fifteen! >=20 > GGATE with MTU 16114 and polling: > test2:/dev#28: ggatec create 10.0.0.2 /dev/ad4p1 > ggate0 > test2:/dev#29: mount /dev/ggate0 /samsung/ > test2:/dev#30: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D16k > ^C2564+0 records in > 2563+0 records out > 41992192 bytes transferred in 15.908581 secs (2639594 bytes/sec) > -> ^^^^^^^ ~ 2,6MB/s >=20 > GGATE without polling and MTU 16114: > test2:~#12: ggatec create 10.0.0.2 /dev/ad4p1 > ggate0 > test2:~#13: mount /dev/ggate0 /samsung/ > test2:~#14: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D128k > ^C1282+0 records in > 1281+0 records out > 167903232 bytes transferred in 11.274768 secs (14891945 bytes/sec) > -> ^^^^^^^^ ~ 15MB/s > .....and with 1m blocksize: > test2:~#17: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D1m > ^C61+0 records in > 60+0 records out > 62914560 bytes transferred in 4.608726 secs (13651182 bytes/sec) > -> ^^^^^^^^ ~ 13,6MB/s >=20 > I can't imagine why there seems to be a absolute limit of 15MB/s that can= be=20 > transfered over the network > But it's even worse, here two excerpts of NFS (udp) with jumbo Frames=20 > (mtu=3D16114): > test2:~#23: mount 10.0.0.2:/samsung /samsung/ > test2:~#24: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D1m > ^C89+0 records in > 88+0 records out > 92274688 bytes transferred in 13.294708 secs (6940708 bytes/sec) > -> ^^^^^^^ ~7MB/s > .....and with 64k blocksize: > test2:~#25: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k > ^C848+0 records in > 847+0 records out > 55508992 bytes transferred in 8.063415 secs (6884055 bytes/sec) >=20 > And with TCP-NFS (and Jumbo Frames): > test2:~#30: mount_nfs -T 10.0.0.2:/samsung /samsung/ > test2:~#31: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k > ^C1921+0 records in > 1920+0 records out > 125829120 bytes transferred in 7.461226 secs (16864403 bytes/sec) > -> ^^^^^^^^ ~ 17MB/s >=20 > Again NFS (udp) but with MTU 1500: > test2:~#9: mount_nfs 10.0.0.2:/samsung /samsung/ > test2:~#10: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D8k > ^C12020+0 records in > 12019+0 records out > 98459648 bytes transferred in 10.687460 secs (9212633 bytes/sec) > -> ^^^^^^^ ~ 10MB/s > And TCP-NFS with MTU 1500: > test2:~#12: mount_nfs -T 10.0.0.2:/samsung /samsung/ > test2:~#13: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D8k > ^C19352+0 records in > 19352+0 records out > 158531584 bytes transferred in 12.093529 secs (13108794 bytes/sec) > -> ^^^^^^^^ ~ 13MB/s >=20 > GGATE with default MTU of 1500, polling disabled: > test2:~#14: dd if=3D/dev/zero of=3D/samsung/testfile bs=3D64k > ^C971+0 records in > 970+0 records out > 63569920 bytes transferred in 6.274578 secs (10131346 bytes/sec) > -> ^^^^^^^^ ~ 10M/s >=20 >=20 > Conclusion: >=20 > *** >=20 > - It seems that GEOM_GATE is less efficient with GigaBit (em) than NFS vi= a TCP=20 > is. >=20 > - em seems to have problems with MTU greater than 1500 >=20 > - UDP seems to have performance disadvantages over TCP regarding NFS whic= h=20 > should be vice versa AFAIK >=20 > - polling and em (GbE) with HZ=3D256 is definitly no good idea, even 10Ba= se-2=20 > can compete >=20 > - NFS over TCP with MTU of 16114 gives the maximum transferrate for large= =20 > files over GigaBit Ethernet with a value of 17MB/s, a quarter of what I'd= =20 > expect with my test equipment. >=20 > - overall network performance (regarding large file transfers) is horribl= e >=20 > Please, if anybody has the knowledge to dig into these problems, let me k= now=20 > if I can do any tests to help getting ggate and NFS useful in fast 5.3-st= able=20 > environments. I am very interested in this as I have similar issues with the re driver. It it horrible when operating at gigE vs. 100BT. Have you tried plugging the machines into a 100BT instead? Cheers, Sean --=-hcHwgO70AgenjjKR2nD0 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm9v/yQsGN30uGE4RAta1AKDpkmg7f8fr8fPb79RLQdFncL7x0ACfZynv OBS1581vPaKgaB9QZjxu4fM= =7134 -----END PGP SIGNATURE----- --=-hcHwgO70AgenjjKR2nD0-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 23:26:00 2004 Return-Path: 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 2AFE016A4CE; Wed, 17 Nov 2004 23:26:00 +0000 (GMT) Received: from www.mmlab.cse.yzu.edu.tw (www.mmlab.cse.yzu.edu.tw [140.138.145.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDB0443D41; Wed, 17 Nov 2004 23:25:59 +0000 (GMT) (envelope-from avatar@mmlab.cse.yzu.edu.tw) Received: by www.mmlab.cse.yzu.edu.tw (qmail, from userid 1000) id 8C0CB4EFCDC; Thu, 18 Nov 2004 07:25:58 +0800 (CST) Received: from localhost (localhost [127.0.0.1]) by www.mmlab.cse.yzu.edu.tw (qmail) with ESMTP id 85D7E4EFCDA; Thu, 18 Nov 2004 07:25:58 +0800 (CST) Date: Thu, 18 Nov 2004 07:25:58 +0800 (CST) From: Tai-hwa Liang To: Giorgos Keramidas In-Reply-To: <20041117225735.GA2148@gothmog.gr> Message-ID: <04111807243512.21298@www.mmlab.cse.yzu.edu.tw> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> <20041117225735.GA2148@gothmog.gr> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed cc: Tillman Hodgson cc: freebsd-current@freebsd.org Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 23:26:00 -0000 On Thu, 18 Nov 2004, Giorgos Keramidas wrote: > On 2004-11-17 13:31, Tillman Hodgson wrote: [...] >> Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined >> Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. >> >> My custom kernel doesn't include IPv6. Does pf truly require IPv6?: > > Yes, if you want to load it as a module. This is exactly the same thing > I bumped into last night. Compiling a kernel with INET6 support will > let you load pf as a module. Does define "NOINET6=yes" in your /etc/make.conf and rebuild the kernel work for you? > I'm not sure if this is a `bug' that neds fixing though ;-) From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 23:31:41 2004 Return-Path: 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 48AD716A4CE for ; Wed, 17 Nov 2004 23:31:41 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4472243D45 for ; Wed, 17 Nov 2004 23:31:40 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 10221 invoked by uid 65534); 17 Nov 2004 23:31:39 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp028) with SMTP; 18 Nov 2004 00:31:39 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Thu, 18 Nov 2004 00:31:30 +0100 User-Agent: KMail/1.7 References: <200411172357.47735.Emanuel.Strobl@gmx.net> <1100733439.21798.36.camel@server.mcneil.com> In-Reply-To: <1100733439.21798.36.camel@server.mcneil.com> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1261566.XGPEXi19aq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411180031.36222.Emanuel.Strobl@gmx.net> cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 23:31:41 -0000 --nextPart1261566.XGPEXi19aq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 18. November 2004 00:17 schrieb Sean McNeil: > On Wed, 2004-11-17 at 23:57 +0100, Emanuel Strobl wrote: > > Dear best guys, > > > > I really love 5.3 in many ways but here're some unbelievable transfer > > rates, after I went out and bought a pair of Intel GigaBit Ethernet Car= ds > > to solve my performance problem (*laugh*): > > > > (In short, see *** below) [...] > > Conclusion: > > > > *** > > > > - It seems that GEOM_GATE is less efficient with GigaBit (em) than NFS > > via TCP is. > > > > - em seems to have problems with MTU greater than 1500 > > > > - UDP seems to have performance disadvantages over TCP regarding NFS > > which should be vice versa AFAIK > > > > - polling and em (GbE) with HZ=3D256 is definitly no good idea, even > > 10Base-2 can compete > > > > - NFS over TCP with MTU of 16114 gives the maximum transferrate for lar= ge > > files over GigaBit Ethernet with a value of 17MB/s, a quarter of what I= 'd > > expect with my test equipment. > > > > - overall network performance (regarding large file transfers) is > > horrible > > > > Please, if anybody has the knowledge to dig into these problems, let me > > know if I can do any tests to help getting ggate and NFS useful in fast > > 5.3-stable environments. > > I am very interested in this as I have similar issues with the re > driver. It it horrible when operating at gigE vs. 100BT. Have you > tried plugging the machines into a 100BT instead? No, because I observed similar bad performance with my fileserver which is= =20 almost the same HW and it's em (Intel GbE) is connected to the local=20 100baseTX segment. I explicitly avoided to go via any switch/hub to eliminate further problems. I wonder if anybody has ever been able to transfer more than 17MB/s via IP= =20 anyway? I need this performance for mirroring via ggate, so I'm thinking about fwe = (IP=20 over Firewire). Perhaps somebody has tried this already? If fwe gives reasonable transferra= tes=20 I guess the perfomance problem won't be found in ethernet but in IP. Thanks, =2DHarry > > Cheers, > Sean --nextPart1261566.XGPEXi19aq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm99YBylq0S4AzzwRAq2/AKCABpOjptOKVBd0nLKr0SO/R7UZiQCfe+m+ vtc5HdRy4JiesX3TYF6aSbk= =kjFa -----END PGP SIGNATURE----- --nextPart1261566.XGPEXi19aq-- From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 23:33:16 2004 Return-Path: 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 A187A16A4CE; Wed, 17 Nov 2004 23:33:16 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ED17A43D54; Wed, 17 Nov 2004 23:33:15 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iAHNZTP3033270; Wed, 17 Nov 2004 16:35:30 -0700 (MST) (envelope-from scottl@freebsd.org) Message-ID: <419BDFE7.9090402@freebsd.org> Date: Wed, 17 Nov 2004 16:33:59 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040929 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Emanuel Strobl References: <200411172357.47735.Emanuel.Strobl@gmx.net> In-Reply-To: <200411172357.47735.Emanuel.Strobl@gmx.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 23:33:16 -0000 Emanuel Strobl wrote: > Dear best guys, > > I really love 5.3 in many ways but here're some unbelievable transfer rates, > after I went out and bought a pair of Intel GigaBit Ethernet Cards to solve > my performance problem (*laugh*): > > (In short, see *** below) > > Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit PCI > Desktop adapter MT) connected directly without a switch/hub and "device > polling" compiled into a custom kernel with HZ set to 256 and > kern.polling.enabled set to "1": > > LOCAL: > (/samsung is ufs2 on /dev/ad4p1, a SAMSUNG SP080N2) > test3:~#7: dd if=/dev/zero of=/samsung/testfile bs=16k > ^C10524+0 records in > 10524+0 records out > 172425216 bytes transferred in 3.284735 secs (52492882 bytes/sec) > -> > ^^^^^^^^ ~ 52MB/s > NFS(udp,polling): > (/samsung is nfs on test3:/samsung, via em0, x-over, polling enabled) > test2:/#21: dd if=/dev/zero of=/samsung/testfile bs=16k > ^C1858+0 records in > 1857+0 records out > 30425088 bytes transferred in 8.758475 secs (3473788 bytes/sec) > -> ^^^^^^^ ~ 3,4MB/s > > This example shows that using NFS over GigaBit Ethernet decimates performance > by the factor of 15, in words fifteen! > > GGATE with MTU 16114 and polling: > test2:/dev#28: ggatec create 10.0.0.2 /dev/ad4p1 > ggate0 > test2:/dev#29: mount /dev/ggate0 /samsung/ > test2:/dev#30: dd if=/dev/zero of=/samsung/testfile bs=16k > ^C2564+0 records in > 2563+0 records out > 41992192 bytes transferred in 15.908581 secs (2639594 bytes/sec) > -> ^^^^^^^ ~ 2,6MB/s > > GGATE without polling and MTU 16114: > test2:~#12: ggatec create 10.0.0.2 /dev/ad4p1 > ggate0 > test2:~#13: mount /dev/ggate0 /samsung/ > test2:~#14: dd if=/dev/zero of=/samsung/testfile bs=128k > ^C1282+0 records in > 1281+0 records out > 167903232 bytes transferred in 11.274768 secs (14891945 bytes/sec) > -> ^^^^^^^^ ~ 15MB/s > .....and with 1m blocksize: > test2:~#17: dd if=/dev/zero of=/samsung/testfile bs=1m > ^C61+0 records in > 60+0 records out > 62914560 bytes transferred in 4.608726 secs (13651182 bytes/sec) > -> ^^^^^^^^ ~ 13,6MB/s > > I can't imagine why there seems to be a absolute limit of 15MB/s that can be > transfered over the network > But it's even worse, here two excerpts of NFS (udp) with jumbo Frames > (mtu=16114): > test2:~#23: mount 10.0.0.2:/samsung /samsung/ > test2:~#24: dd if=/dev/zero of=/samsung/testfile bs=1m > ^C89+0 records in > 88+0 records out > 92274688 bytes transferred in 13.294708 secs (6940708 bytes/sec) > -> ^^^^^^^ ~7MB/s > .....and with 64k blocksize: > test2:~#25: dd if=/dev/zero of=/samsung/testfile bs=64k > ^C848+0 records in > 847+0 records out > 55508992 bytes transferred in 8.063415 secs (6884055 bytes/sec) > > And with TCP-NFS (and Jumbo Frames): > test2:~#30: mount_nfs -T 10.0.0.2:/samsung /samsung/ > test2:~#31: dd if=/dev/zero of=/samsung/testfile bs=64k > ^C1921+0 records in > 1920+0 records out > 125829120 bytes transferred in 7.461226 secs (16864403 bytes/sec) > -> ^^^^^^^^ ~ 17MB/s > > Again NFS (udp) but with MTU 1500: > test2:~#9: mount_nfs 10.0.0.2:/samsung /samsung/ > test2:~#10: dd if=/dev/zero of=/samsung/testfile bs=8k > ^C12020+0 records in > 12019+0 records out > 98459648 bytes transferred in 10.687460 secs (9212633 bytes/sec) > -> ^^^^^^^ ~ 10MB/s > And TCP-NFS with MTU 1500: > test2:~#12: mount_nfs -T 10.0.0.2:/samsung /samsung/ > test2:~#13: dd if=/dev/zero of=/samsung/testfile bs=8k > ^C19352+0 records in > 19352+0 records out > 158531584 bytes transferred in 12.093529 secs (13108794 bytes/sec) > -> ^^^^^^^^ ~ 13MB/s > > GGATE with default MTU of 1500, polling disabled: > test2:~#14: dd if=/dev/zero of=/samsung/testfile bs=64k > ^C971+0 records in > 970+0 records out > 63569920 bytes transferred in 6.274578 secs (10131346 bytes/sec) > -> ^^^^^^^^ ~ 10M/s > > > Conclusion: > > *** > > - It seems that GEOM_GATE is less efficient with GigaBit (em) than NFS via TCP > is. > > - em seems to have problems with MTU greater than 1500 > > - UDP seems to have performance disadvantages over TCP regarding NFS which > should be vice versa AFAIK > > - polling and em (GbE) with HZ=256 is definitly no good idea, even 10Base-2 > can compete You should be setting HZ to 1000 or higher. > > - NFS over TCP with MTU of 16114 gives the maximum transferrate for large > files over GigaBit Ethernet with a value of 17MB/s, a quarter of what I'd > expect with my test equipment. > > - overall network performance (regarding large file transfers) is horrible > > Please, if anybody has the knowledge to dig into these problems, let me know > if I can do any tests to help getting ggate and NFS useful in fast 5.3-stable > environments. if_em in 5.3 has a large performance penalty in the common case due to a programming error. I fixed it in 6-CURRENT and 5.3-STABLE. You might want to try updating to the RELENG_5 branch to see if you get better results. Scott From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 23:37:37 2004 Return-Path: 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 A539616A4E5 for ; Wed, 17 Nov 2004 23:37:37 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 970EB43D48 for ; Wed, 17 Nov 2004 23:37:36 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 26258 invoked by uid 65534); 17 Nov 2004 23:37:35 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp006) with SMTP; 18 Nov 2004 00:37:35 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Thu, 18 Nov 2004 00:37:33 +0100 User-Agent: KMail/1.7 References: <200411172357.47735.Emanuel.Strobl@gmx.net> <419BDFE7.9090402@freebsd.org> In-Reply-To: <419BDFE7.9090402@freebsd.org> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart10899064.5k2Jlo1tdq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411180037.34807.Emanuel.Strobl@gmx.net> cc: freebsd-stable@freebsd.org cc: Scott Long Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 23:37:37 -0000 --nextPart10899064.5k2Jlo1tdq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Am Donnerstag, 18. November 2004 00:33 schrieb Scott Long: > Emanuel Strobl wrote: > > Dear best guys, > > > > I really love 5.3 in many ways but here're some unbelievable transfer > > rates, after I went out and bought a pair of Intel GigaBit Ethernet Cards > > to solve my performance problem (*laugh*): > > > > (In short, see *** below) [...] > > > > - overall network performance (regarding large file transfers) is > > horrible > > > > Please, if anybody has the knowledge to dig into these problems, let me > > know if I can do any tests to help getting ggate and NFS useful in fast > > 5.3-stable environments. > > if_em in 5.3 has a large performance penalty in the common case due to a > programming error. I fixed it in 6-CURRENT and 5.3-STABLE. You might > want to try updating to the RELENG_5 branch to see if you get better > results. The test machines work with RELENG_5 from today. When have you merged the fixes exactly? Thanks a lot, -Harry > > Scott > _______________________________________________ > 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" --nextPart10899064.5k2Jlo1tdq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD4DBQBBm+C+Bylq0S4AzzwRAtLAAJ0f2HpfUcOdZTaRhSit7sF4Udmz7wCYx0QU lOiA39tvkB6vj0AWHVlvzw== =xDON -----END PGP SIGNATURE----- --nextPart10899064.5k2Jlo1tdq-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 00:02:12 2004 Return-Path: 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 EECF316A4CE; Thu, 18 Nov 2004 00:02:12 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F35943D41; Thu, 18 Nov 2004 00:02:12 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAI01jaw065246 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 19:01:57 -0500 (EST) Message-ID: <419BE654.6020705@mac.com> Date: Wed, 17 Nov 2004 19:01:24 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 Followup-To: freebsd-current@freebsd.org To: Emanuel Strobl References: <200411172357.47735.Emanuel.Strobl@gmx.net> In-Reply-To: <200411172357.47735.Emanuel.Strobl@gmx.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.3 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:02:13 -0000 Emanuel Strobl wrote: [ ... ] > Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit PCI > Desktop adapter MT) connected directly without a switch/hub If filesharing via NFS is your primary goal, it's reasonable to test that, however it would be easier to make sense of your results by testing your network hardware at a lower level. Since you're already running portmap/RPC, consider using spray to blast some packets rapidly and see what kind of bandwidth you max out using that. Or use ping with -i & -s set to reasonable values depending on whether you're using jumbo frames or not. If the problem is your connection is dropping a few packets, this will show up better here. Using "ping -f" is also a pretty good troubleshooter. If you can dig up a gigabit switch with management capabilities to test with, taking a look at the per-port statistics for errors would also be worth doing. A dodgy network cable can still work well enough for the cards to have a green link light, but fail to handle high traffic properly. [ ... ] > - em seems to have problems with MTU greater than 1500 Have you tried using an MTU of 3K or 7K? I also seem to recall that there were performance problems with em in 5.3 and a fix is being tested in -CURRENT. [I just saw Scott's response to the list, and your answer, so maybe nevermind this point.] > - UDP seems to have performance disadvantages over TCP regarding NFS which > should be vice versa AFAIK Hmm, yeah...again, this makes me wonder whether you are dropping packets. NFS over TCP does better than UDP does in lossy network conditions. > - polling and em (GbE) with HZ=256 is definitly no good idea, even 10Base-2 > can compete You should be setting HZ to 1000, 2000, or so when using polling, and a higher HZ is definitely recommmended when you add in jumbo frames and GB speeds. -- -Chuck PS: followup-to set to reduce crossposting... From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 00:30:08 2004 Return-Path: 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 BA99516A4CE for ; Thu, 18 Nov 2004 00:30:08 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0983A43D5E for ; Thu, 18 Nov 2004 00:29:58 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAI0TWk3082541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 19:29:43 -0500 (EST) Message-ID: <419BECD6.8010008@mac.com> Date: Wed, 17 Nov 2004 19:29:10 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Emanuel Strobl References: <200411172357.47735.Emanuel.Strobl@gmx.net> <1100733439.21798.36.camel@server.mcneil.com> <200411180031.36222.Emanuel.Strobl@gmx.net> In-Reply-To: <200411180031.36222.Emanuel.Strobl@gmx.net> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.3 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:30:08 -0000 Emanuel Strobl wrote: [ ... ] > No, because I observed similar bad performance with my fileserver which is > almost the same HW and it's em (Intel GbE) is connected to the local > 100baseTX segment. Can you mention a little more about your hardware, or perhaps put a dmesg on a website somewhere? If you don't have PCI-E hardware, especially if you are using classic 32-bit/33MHz PCI rather than a GbE adaptor via your mainboard's chipset, you're going to be limited by PCI bus throughput. [I'd still expect you to be going faster if this was the case, however.] Also, have you done any tuning of NMBCLUSTERS or the net.inet sysctls? > I explicitly avoided to go via any switch/hub to eliminate further problems. > I wonder if anybody has ever been able to transfer more than 17MB/s via IP > anyway? Sure. I've got a pair of Apple Xserves in a rack which got ~90 MB/s FTP for five ~600MB CD-ROM ISO images via a 3com gigabit switch. The machine doing the writing was using a four-disk RAID-10 setup via the internal SATA-150 drive bays, but I paused between each transfer so some of that transfer rate may be due to stuff in RAM but not yet flushed to disk, so take that number cum grano salis. > I need this performance for mirroring via ggate, so I'm thinking about fwe (IP > over Firewire). > Perhaps somebody has tried this already? If fwe gives reasonable transferrates > I guess the perfomance problem won't be found in ethernet but in IP. Well, I think Firewire is great and FreeBSD seems to have a very good implementation, so this might well be a reasonable alternative path. That being said, gigabit ethernet ought to do as well or better than Firewire if you can resolve this performance issue. -- -Chuck From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 00:32:40 2004 Return-Path: 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 A5FD216A4D0; Thu, 18 Nov 2004 00:32:40 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id F015043D41; Thu, 18 Nov 2004 00:32:39 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAI0VeZg019823; Thu, 18 Nov 2004 11:01:40 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Thu, 18 Nov 2004 11:02:29 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAI0Qlh25935; Thu, 18 Nov 2004 10:56:47 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDQLXZ; Thu, 18 Nov 2004 10:56:37 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAI0RgB1066781 ; Thu, 18 Nov 2004 10:57:42 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAI0RfR0066780; Thu, 18 Nov 2004 10:57:41 +1030 (CST) (envelope-from wilkinsa) Date: Thu, 18 Nov 2004 10:57:41 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Message-ID: <20041118002741.GC66483@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <200411172357.47735.Emanuel.Strobl@gmx.net> <419BE654.6020705@mac.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <419BE654.6020705@mac.com> User-Agent: Mutt/1.5.6i Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:32:40 -0000 ping only tests latency *not* throughput. So it is not really a good test. - aW 0n Wed, Nov 17, 2004 at 07:01:24PM -0500, Chuck Swiger wrote: Emanuel Strobl wrote: [ ... ] >Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit PCI >Desktop adapter MT) connected directly without a switch/hub what kind of bandwidth you max out using that. Or use ping with -i & -s set to reasonable values depending on whether you're using jumbo frames or not. If the problem is your connection is dropping a few packets, this will show up better here. Using "ping -f" is also a pretty good troubleshooter. From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 00:58:01 2004 Return-Path: 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 C4B4B16A4CE for ; Thu, 18 Nov 2004 00:58:01 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E97043D41 for ; Thu, 18 Nov 2004 00:58:01 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.250] (pool-68-161-115-118.ny325.east.verizon.net [68.161.115.118]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iAI0vmLn099887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 17 Nov 2004 19:57:51 -0500 (EST) Message-ID: <419BF377.9090800@mac.com> Date: Wed, 17 Nov 2004 19:57:27 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <200411172357.47735.Emanuel.Strobl@gmx.net> <419BE654.6020705@mac.com> <20041118002741.GC66483@squash.dsto.defence.gov.au> In-Reply-To: <20041118002741.GC66483@squash.dsto.defence.gov.au> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=-4.4 required=5.5 tests=AWL,BAYES_00 autolearn=ham version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on pi.codefab.com cc: freebsd-current@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:58:01 -0000 Wilkinson, Alex wrote: > ping only tests latency *not* throughput. So it is not really a good test. You can utilize a decent amount of a 100Mbs link via ping: 42-sec# time ping -q -c 10240 -i 0.00001 -s 1004 cube PING cube.local (192.168.1.6): 1004 data bytes --- cube.local ping statistics --- 10240 packets transmitted, 10240 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.455/0.793/4.491/0.418 ms 1.48s real 0.05s user 0.60s system 43% ...which works out to about 7MB/s. Hmph. I should have mentioned in my previous message that that one ought to do something like: sysctl -w net.inet.icmp.icmplim=10000 # or zero, maybe? ...as well, or else ping will be limited to some ~250 pps. It would be interesting for Emanuel to try ping -s with a bigger value suitable to fill jumbo frames. -- -Chuck PS: I just tested several varieties of ping until I got a: ping: sendto: No buffer space available ...so I perhaps I need do some additional tuning, myself. :-) From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:04:57 2004 Return-Path: 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 8584F16A4D0 for ; Thu, 18 Nov 2004 01:04:57 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0A03743D54 for ; Thu, 18 Nov 2004 01:04:57 +0000 (GMT) (envelope-from vincepoy@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so970141rnf for ; Wed, 17 Nov 2004 17:04:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=oI4NDcmy7Iy3+mNJVX1rtwJIO3SCRlZUOLa97hnX4z42RyBRJ5i1nOxlElDGsjj/1dcEqfzaoX1Bckj2lxAKZSWobVTsjatWk2rbS1MbXbQYZvJeHBGs9iTz38f3VxrouvCxR39cFeAAij33GFV9/VnUum+aXv7nT9VFCXLop+I= Received: by 10.38.15.33 with SMTP id 33mr306132rno; Wed, 17 Nov 2004 17:04:46 -0800 (PST) Received: by 10.38.14.49 with HTTP; Wed, 17 Nov 2004 17:04:46 -0800 (PST) Message-ID: <429af92e041117170475721c3@mail.gmail.com> Date: Wed, 17 Nov 2004 17:04:46 -0800 From: Vincent Poy To: Andrew Thompson In-Reply-To: <20041117004917.GC24087@thingy.tbd.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041117003518.GA47238@troutmask.apl.washington.edu> <20041117004917.GC24087@thingy.tbd.co.nz> cc: sam@freebsd.org cc: freebsd-current@freebsd.org cc: Steve Kargl Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vincent Poy List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:04:57 -0000 On Wed, 17 Nov 2004 13:49:17 +1300, Andrew Thompson wrote: > On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > > I'm trying to set up my wireless NIC (Netgear WG511) to > > connect to the internet through my wireless route (Netgear > > WGR614). When I set up the router, I choose the 128-bit > > WEP key feature. To my chagrin, Windows XP works well > > with the WG511, but I prefer FreeBSD. I tried to give > > my WEP key to ifconfig, which does not work. > > > > %ifconfig ndis0 inet 192.168.0.3 broadcast 192.168.0.1 > > netmask 255.255.255.0 ssid YADA channel 11 wepmode on > > wepkey abcdefghijklmnopqrstuvwxyz > > > > The wep key should be hex, not ascii. I'm having a different problem. I'm trying to connect my notebook's Atheros A/B/G Mini-PCI card to the Netgear FWAG114 Dual-Band A/G ProSafe VPN Wireless Firewall which is configured for 128bit Shared WEP. It works correctly under Windows XP when I swap the HD with the Windows XP HD but couldn't get it working under FreeBSD. boot messages contains: ath0: mem 0xf8fe0000-0xf8feffff irq 11 at device 3.0 on pci2 ath0: [GIANT-LOCKED] ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 ath0: Ethernet address: 00:80:c8:12:03:dd ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36M bps 48Mbps 54Mbps This is how I tried to configure it: ifconfig ath0 inet 192.168.2.3 netmask 255.255.255.0 ssid DNALOGIC-NETGEAR11G wepmode on wepkey 0xD4B1F086AF47A4A35DF4F4604E ifconfig ath0 output: ath0: flags=8843 mtu 1500 inet6 fe80::280:c8ff:fe12:3dd%ath0 prefixlen 64 scopeid 0x3 ether 00:80:c8:12:03:dd media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid DNALOGIC-NETGEAR11G 1:DNALOGIC-NETGEAR11G channel 6 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode MIXED weptxkey 1 wepkey 1:104-bit Anyone have any ideas since the status keeps saying no carrier. Also, how does one make it so that it will get the IP via DHCP instead from the Wireless Router? Thanks. Cheers, Vince From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:09:55 2004 Return-Path: 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 9B87516A4CE for ; Thu, 18 Nov 2004 01:09:55 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 9612543D58 for ; Thu, 18 Nov 2004 01:09:54 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 21687 invoked by uid 65534); 18 Nov 2004 01:09:53 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp018) with SMTP; 18 Nov 2004 02:09:53 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-stable@freebsd.org Date: Thu, 18 Nov 2004 02:09:46 +0100 User-Agent: KMail/1.7 References: <200411172357.47735.Emanuel.Strobl@gmx.net> <419BE654.6020705@mac.com> In-Reply-To: <419BE654.6020705@mac.com> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1764708.j2PJtahPCE"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411180209.52817.Emanuel.Strobl@gmx.net> cc: Chuck Swiger cc: freebsd-current@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:09:55 -0000 --nextPart1764708.j2PJtahPCE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 18. November 2004 01:01 schrieb Chuck Swiger: > Emanuel Strobl wrote: > [ ... ] > > > Tests were done with two Intel GigaBit Ethernet cards (82547EI, 32bit P= CI > > Desktop adapter MT) connected directly without a switch/hub > > If filesharing via NFS is your primary goal, it's reasonable to test that, GEOM_GATE is my primary goal, and I can remember that when Pavel wrote this= =20 great feature, he took care about performance and easyly outperformed NFS=20 (with 100baseTX AFAIK) > however it would be easier to make sense of your results by testing your > network hardware at a lower level. Since you're already running > portmap/RPC, consider using spray to blast some packets rapidly and see > what kind of bandwidth you max out using that. Or use ping with -i & -s > set to reasonable values depending on whether you're using jumbo frames or > not. > > If the problem is your connection is dropping a few packets, this will sh= ow > up better here. Using "ping -f" is also a pretty good troubleshooter. If > you can dig up a gigabit switch with management capabilities to test with, > taking a look at the per-port statistics for errors would also be worth > doing. A dodgy network cable can still work well enough for the cards to > have a green link light, but fail to handle high traffic properly. I'll do some tests regarding these issues to make sure I'm not suffering fr= om=20 ill conditions, but I'm quite sure my testbed's feeling fine. I don't have= =20 one of these nice managed GigaBit switches, just a x-over cable.... > > [ ... ] > > > - em seems to have problems with MTU greater than 1500 > > Have you tried using an MTU of 3K or 7K? > > I also seem to recall that there were performance problems with em in 5.3 > and a fix is being tested in -CURRENT. [I just saw Scott's response to t= he > list, and your answer, so maybe nevermind this point.] > > > - UDP seems to have performance disadvantages over TCP regarding NFS > > which should be vice versa AFAIK > > Hmm, yeah...again, this makes me wonder whether you are dropping packets. > NFS over TCP does better than UDP does in lossy network conditions. Of course, but If I connect two GbE cards (wich implies that auto-mdi-X and= =20 full duplex is mandatory in 1000baseTX mode) I don't expect any UDP packet = to=20 get lost. But I'll verify tomorrow. > > > - polling and em (GbE) with HZ=3D256 is definitly no good idea, even > > 10Base-2 can compete > > You should be setting HZ to 1000, 2000, or so when using polling, and a Yep, I know that HZ set to 256 with polling enabled isn't really useful, bu= t I=20 don't want to drive my GbE card in polling mode at all, instead I try to=20 prevent my machine from spending time doing nothing, so HZ shouldn't be too= =20 high. Thank you, =2DHarry > higher HZ is definitely recommmended when you add in jumbo frames and GB > speeds. --nextPart1764708.j2PJtahPCE Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBm/ZgBylq0S4AzzwRAm9jAJ0ZO2P8GyFYlpLba5UWijZKEPjyhACfUeVT 6MNXIn3mODVb/sCa/ZD0FzM= =6OzF -----END PGP SIGNATURE----- --nextPart1764708.j2PJtahPCE-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:16:10 2004 Return-Path: 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 9E4BB16A4CE; Thu, 18 Nov 2004 01:16:10 +0000 (GMT) Received: from av5-1-sn3.vrr.skanova.net (av5-1-sn3.vrr.skanova.net [81.228.9.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 548BD43D5C; Thu, 18 Nov 2004 01:16:10 +0000 (GMT) (envelope-from pawel.worach@telia.com) Received: by av5-1-sn3.vrr.skanova.net (Postfix, from userid 502) id 884F837E61; Thu, 18 Nov 2004 02:16:09 +0100 (CET) Received: from smtp1-1-sn3.vrr.skanova.net (smtp1-1-sn3.vrr.skanova.net [81.228.9.177]) by av5-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 77C1C37E4A; Thu, 18 Nov 2004 02:16:09 +0100 (CET) Received: from [192.168.1.1] (h65n2fls35o895.telia.com [217.211.109.65]) by smtp1-1-sn3.vrr.skanova.net (Postfix) with ESMTP id EC9E738003; Thu, 18 Nov 2004 02:16:01 +0100 (CET) Message-ID: <419BF6DD.20205@telia.com> Date: Thu, 18 Nov 2004 02:11:57 +0100 From: Pawel Worach User-Agent: Mozilla Thunderbird 0.9 (X11/20041110) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Vincent Poy References: <20041117003518.GA47238@troutmask.apl.washington.edu> <20041117004917.GC24087@thingy.tbd.co.nz> <429af92e041117170475721c3@mail.gmail.com> In-Reply-To: <429af92e041117170475721c3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: sam@freebsd.org cc: Steve Kargl cc: freebsd-current@freebsd.org Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:16:10 -0000 Vincent Poy wrote: > ath0: mem 0xf8fe0000-0xf8feffff irq 11 at device 3.0 on pci2 > ath0: [GIANT-LOCKED] > ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 > ath0: Ethernet address: 00:80:c8:12:03:dd > ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps > ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps > ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36M > bps 48Mbps 54Mbps > I also have problems with this card on an IBM ThinkPad T41. The funny thing is that it only lists 802.11a and 11g rates, no 11b. Anyway, if I fire up tcpdump I can see traffic in clear text so my wep key and stuff works but I can not send anything and the status is always "no carrier". Could it be an issue with the radio being off (like just the transmitter was off)? The radio-switch only seems to turn on/off bluetooth but not the wireless radio in FreeBSD, is there any software that can do this? Any ideas? More info? -- Pawel From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:19:50 2004 Return-Path: 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 0319316A4CE for ; Thu, 18 Nov 2004 01:19:50 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BDA643D2D for ; Thu, 18 Nov 2004 01:19:49 +0000 (GMT) (envelope-from vincepoy@gmail.com) Received: by rproxy.gmail.com with SMTP id a36so971641rnf for ; Wed, 17 Nov 2004 17:19:43 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=Hn7nce7GMg8akmP0x/yYkXkygbVlEn6ormB2bZXLMpcjPQPtg8rtV9MdyuHVpJpWS+l7NTfgvWZA7gtKlLC4FO3a7aOF1MthJ3KdArxGMXsF9rzCi4vri6+EqYSmSv6DD+3XG0ZJSJKAidYL26fHNi0To4/Ctwf9qCRVBiOE4fg= Received: by 10.39.3.46 with SMTP id f46mr318427rni; Wed, 17 Nov 2004 16:19:38 -0800 (PST) Received: by 10.38.14.49 with HTTP; Wed, 17 Nov 2004 16:19:29 -0800 (PST) Message-ID: <429af92e04111716192acf046f@mail.gmail.com> Date: Wed, 17 Nov 2004 16:19:29 -0800 From: Vincent Poy To: Andrew Thompson In-Reply-To: <20041117004917.GC24087@thingy.tbd.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041117003518.GA47238@troutmask.apl.washington.edu> <20041117004917.GC24087@thingy.tbd.co.nz> cc: sam@freebsd.org cc: freebsd-current@freebsd.org cc: Steve Kargl Subject: Re: 128bit WEP keys and ifconfig X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Vincent Poy List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:19:50 -0000 On Wed, 17 Nov 2004 13:49:17 +1300, Andrew Thompson wrote: > On Tue, Nov 16, 2004 at 04:35:18PM -0800, Steve Kargl wrote: > > I'm trying to set up my wireless NIC (Netgear WG511) to > > connect to the internet through my wireless route (Netgear > > WGR614). When I set up the router, I choose the 128-bit > > WEP key feature. To my chagrin, Windows XP works well > > with the WG511, but I prefer FreeBSD. I tried to give > > my WEP key to ifconfig, which does not work. > > > > %ifconfig ndis0 inet 192.168.0.3 broadcast 192.168.0.1 > > netmask 255.255.255.0 ssid YADA channel 11 wepmode on > > wepkey abcdefghijklmnopqrstuvwxyz > > > > The wep key should be hex, not ascii. I'm having a different problem. I'm trying to connect my notebook's Atheros A/B/G Mini-PCI card to the Netgear FWAG114 Dual-Band A/G ProSafe VPN Wireless Firewall which is configured for 128bit Shared WEP. It works correctly under Windows XP when I swap the HD with the Windows XP HD but couldn't get it working under FreeBSD. boot messages contains: ath0: mem 0xf8fe0000-0xf8feffff irq 11 at device 3.0 on pci2 ath0: [GIANT-LOCKED] ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3 ath0: Ethernet address: 00:80:c8:12:03:dd ath0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36M bps 48Mbps 54Mbps This is how I tried to configure it: ifconfig ath0 inet 192.168.2.3 netmask 255.255.255.0 ssid DNALOGIC-NETGEAR11G wepmode on wepkey 0xD4B1F086AF47A4A35DF4F4604E ifconfig ath0 output: ath0: flags=8843 mtu 1500 inet6 fe80::280:c8ff:fe12:3dd%ath0 prefixlen 64 scopeid 0x3 ether 00:80:c8:12:03:dd media: IEEE 802.11 Wireless Ethernet autoselect (DS/1Mbps) status: no carrier ssid DNALOGIC-NETGEAR11G 1:DNALOGIC-NETGEAR11G channel 6 authmode OPEN powersavemode OFF powersavesleep 100 rtsthreshold 2312 protmode CTS wepmode MIXED weptxkey 1 wepkey 1:104-bit Anyone have any ideas since the status keeps saying no carrier. Also, how does one make it so that it will get the IP via DHCP instead from the Wireless Router? Thanks. Cheers, Vince From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:24:17 2004 Return-Path: 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 ED94316A4CE; Thu, 18 Nov 2004 01:24:17 +0000 (GMT) Received: from wonkity.com (wonkity.com [65.173.111.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F7A843D2D; Thu, 18 Nov 2004 01:24:17 +0000 (GMT) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.13.1/8.13.1) with ESMTP id iAI1O623015432; Wed, 17 Nov 2004 18:24:06 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.13.1/8.13.1/Submit) with ESMTP id iAI1O6rv015429; Wed, 17 Nov 2004 18:24:06 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 17 Nov 2004 18:24:06 -0700 (MST) From: Warren Block To: Nate Lawson In-Reply-To: <419BB117.4070802@root.org> Message-ID: <20041117181754.W12541@wonkity.com> References: <20041115211636.GA1540@laptop.6bone.nl> <419AF4E7.5000206@wanadoo.fr><419B194E.5090800@DeepCore.dk> <419BB117.4070802@root.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 (wonkity.com [127.0.0.1]); Wed, 17 Nov 2004 18:24:06 -0700 (MST) cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org cc: =?ISO-8859-1?Q?S=F8ren_Schmidt?= Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:24:18 -0000 On Wed, 17 Nov 2004, Nate Lawson wrote: > I'd love it if more people would help with debugging. I'm sure you can > relate to maintaining a subsystem where behavior is widely divergent even > among the same model device, OEM bugs are rampant and undocumented, and you > don't have access to a system that can repeat the behavior that the submitter > is reporting. Is there a test suite or procedure for what to test to verify ACPI function? Put something like that on the FLCL web site, and you may have more help than you want. 8-) http://gerda.univie.ac.at/freebsd-laptops/ -Warren Block * Rapid City, South Dakota USA From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 01:54:13 2004 Return-Path: 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 458E716A4CE; Thu, 18 Nov 2004 01:54:13 +0000 (GMT) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0965743D4C; Thu, 18 Nov 2004 01:54:13 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.34] (adsl-67-119-74-222.dsl.sntc01.pacbell.net [67.119.74.222]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id iAI1rvC4018177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Nov 2004 17:53:58 -0800 Message-ID: <419C00A7.7030300@root.org> Date: Wed, 17 Nov 2004 17:53:43 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <419BB117.4070802@root.org> <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> In-Reply-To: <20041117.173409.104092741.imp@harmony.village.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 01:54:13 -0000 Warner Losh wrote: >>I do suspect that this is a PCI power issue and not an ACPI issue, but >>I'd like to know if it shows up on more models. It is most obvious when >>playing a stream as the buffers keep emptying and the sound stops after >>a short time. Music is clearly too fast and high pitched, but at 10% >>overspeed, some may not notice. (Does Dr. Dre sound much different 10% >>faster?) > > I've flipped the sense of the PCI power sysctl in current. Once > that's sanner, we should investigate setting the power states on > resume. Not sure what to do about suspend, since I think that acpi > has different notions of what D level to put a device in for different > S levels and it would likely have to take care of that after giving > the device a chance to save state. > > Warner I have a patch in my tree to do this. I'll post it once it's well-tested. At the moment, setting UART to D3 appears to hang the system and I'm not sure why. -- Nate From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 02:36:10 2004 Return-Path: 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 85E9216A4CE for ; Thu, 18 Nov 2004 02:36:10 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3ED9643D1D for ; Thu, 18 Nov 2004 02:36:10 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 310F872DD4; Wed, 17 Nov 2004 18:36:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2BC9372DCB; Wed, 17 Nov 2004 18:36:10 -0800 (PST) Date: Wed, 17 Nov 2004 18:36:10 -0800 (PST) From: Doug White To: Sean McNeil In-Reply-To: <1100725008.21333.2.camel@server.mcneil.com> Message-ID: <20041117183453.C29048@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> <1100725008.21333.2.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 02:36:10 -0000 On Wed, 17 Nov 2004, Sean McNeil wrote: > On Wed, 2004-11-17 at 10:28 -0800, Doug White wrote: > > On Tue, 16 Nov 2004, Sean McNeil wrote: > > > > > This has been happening for a long time with current and hasn't been > > > resolved. When I start up slapd, I cannot stop it without kill -9 ing > > > it. It would appear stuck in kse and probably has something to do with > > > kill -0: > > > > Mind expanding on this? The backtrace looks normal for a pthread process. > > kill -0 just tests signal delivery; the process is completely unaware that > > the probe occured, though. The process may also be unkillable if its > > stuck in some sort of I/O wait. > > > > Is the server busy when you signal it? > > Oh, OK. I didn't look at /usr/local/etc/rc.subr too closely. I have > additional information, though.... > > It appears that all the threads are destroyed yet it is still in the > thread processing loop. The process is no longer active at all. I just > had a similar problem happen with vlc where I closed it yet it is > hanging in the same place as slapd with all the threads gone. Interesting... what scheduler are you using? > > Here is the one from vlc: > > (gdb) bt full > #0 _thr_sched_switch_unlocked (curthread=0x955000) at pthread_md.h:226 I can't find a reference to this in that file. Can you run ldd against your vlc binary? I('m curious what thread library it thinks its running. > psf = {psf_valid = 0, psf_flags = 0, psf_cancelflags = 29952806, > psf_interrupted = 8, psf_timeout = 11279168, psf_signo = 0, > psf_state = 11279168, psf_wait_data = {mutex = 0x8, cond = 0x8, lock = > 0x8, > sigwait = 0x8}, psf_wakeup_time = {tv_sec = 0, tv_nsec = 0}, > psf_sigset = { > __bits = {29950366, 8, 9860096, 0}}, psf_sigmask = {__bits = > {9752576, 1, > 9860096, 0}}, psf_seqno = 29995347} > curkse = (struct kse *) 0x952000 > resume_once = 0 > #1 0x0000000801c925e0 in _thr_sched_switch (curthread=0x955000) > at /usr/src/lib/libpthread/thread/thr_kern.c:607 > No locals. > #2 0x0000000801c85cb4 in _pthread_join (pthread=0x967400, > thread_return=0x0) > at /usr/src/lib/libpthread/thread/thr_join.c:133 > curthread = (struct pthread *) 0x955000 > tmp = (void *) 0x0 > crit = 0x0 > ret = 0 > #3 0x0000000000431749 in __vlc_thread_join (p_this=0xad4800, > psz_file=0x6a283c "src/playlist/playlist.c", i_line=130) > at src/misc/threads.c:716 > i_ret = 1 > #4 0x000000000040ee1a in playlist_Destroy (p_playlist=0xad4800) > ---Type to continue, or q to quit--- > at src/playlist/playlist.c:130 > No locals. > #5 0x000000000040c400 in VLC_CleanUp (i_object=0) at src/libvlc.c:831 > p_intf = (intf_thread_t *) 0xad4800 > p_playlist = (playlist_t *) 0xad4800 > p_vout = (vout_thread_t *) 0xad4800 > p_aout = (aout_instance_t *) 0xad4800 > p_announce = (announce_handler_t *) 0xad4800 > p_vlc = (vlc_t *) 0x94d400 > #6 0x0000000000407415 in main (i_argc=1, ppsz_argv=0x7fffffffe940) > at src/vlc.c:108 > i_ret = 0 > > and here is a full trace of slapd: > > (gdb) bt full > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > No locals. > #1 0x0000000801428e49 in kse_wait (kse=0x62a000, td_wait=0x0, > sigseqno=0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > ts = {tv_sec = 7647232, tv_nsec = 7647232} > ts_sleep = {tv_sec = 60, tv_nsec = 0} > saved_flags = 0 > #2 0x0000000801427078 in kse_sched_multi (kmbx=0x62efa0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > curkse = (struct kse *) 0x62a000 > curthread = (struct pthread *) 0x0 > td_wait = (struct pthread *) 0x62a068 > curframe = (struct pthread_sigframe *) 0x17f > ret = 383 > #3 0x000000080142afbf in _amd64_enter_uts () > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > No locals. > #4 0x0000000000000000 in ?? () > No symbol table info available. > #5 0x000000000062f000 in ?? () > No symbol table info available. > #6 0x000000000062a000 in ?? () > No symbol table info available. > ---Type to continue, or q to quit--- > #7 0x0000000000000000 in ?? () > No symbol table info available. > #8 0x0000000000000000 in ?? () > No symbol table info available. > #9 0x0000000000000000 in ?? () > No symbol table info available. > #10 0x0000000000000000 in ?? () > No symbol table info available. > #11 0x0000000000000000 in ?? () > No symbol table info available. > #12 0x0000000000000001 in ?? () > No symbol table info available. > #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () > at /usr/src/lib/libpthread/thread/thr_kern.c:904 > free_kseq = {tqh_first = 0x0, tqh_last = 0x801534810} > gc_ksegq = {tqh_first = 0x0, tqh_last = 0x801534840} > next_uniqueid = 7 > active_kse_groupq = {tqh_first = 0x62f100, tqh_last = 0x748020} > active_kse_count = 2 > free_threadq = {tqh_first = 0x0, tqh_last = 0x801534890} > free_kse_count = 0 > active_kseq = {tqh_first = 0x62a000, tqh_last = 0x6c9220} > free_kse_groupq = {tqh_first = 0x0, tqh_last = 0x801534820} > ---Type to continue, or q to quit--- > kse_lock = {l_head = 0x6291c0, l_tail = 0x6291c0, > l_type = LCK_ADAPTIVE, l_wait = 0x801426150 <_kse_lock_wait>, > l_wakeup = 0x8014261e0 <_kse_lock_wakeup>} > active_kseg_count = 2 > inited = 1 > free_thread_count = 0 > free_kseg_count = 0 > thr_hashtable = {{lh_first = 0x0} , { > lh_first = 0x6c3c00}, {lh_first = 0x0}, {lh_first = 0x0}, { > lh_first = 0x0}, {lh_first = 0x0}, {lh_first = 0x1874400}, { > lh_first = 0x0}, {lh_first = 0x0}, {lh_first = 0x0}, {lh_first = > 0x0}, { > lh_first = 0x74b000}, {lh_first = 0x0} , { > lh_first = 0x74b800}, {lh_first = 0x0}, {lh_first = 0x0}, { > lh_first = 0x0}, {lh_first = 0x0}, {lh_first = 0x0}, {lh_first = > 0x0}, { > lh_first = 0x0}, {lh_first = 0x0}, {lh_first = 0x632000}, { > lh_first = 0x0} , {lh_first = 0x29ab400}, { > lh_first = 0x0}, {lh_first = 0x0}, {lh_first = 0x0}, {lh_first = > 0x0}, { > lh_first = 0x0}, {lh_first = 0x2983c00}, { > lh_first = 0x0} } > thread_lock = {l_head = 0x6291e0, l_tail = 0x6291e0, > l_type = LCK_ADAPTIVE, l_wait = 0x801426150 <_kse_lock_wait>, > l_wakeup = 0x8014261e0 <_kse_lock_wakeup>} > _tcb_mutex = 0x628380 > Previous frame inner to this frame (corrupt stack?) > > which looks like total garbage. Looking at each thread I see that there > is only a thread 1,2, and 3: > > (gdb) thread 1 > [Switching to thread 1 (Thread 6 (LWP 100177))]#0 0x000000080142e914 in > kse_release () at kse_release.S:2 > 2 RSYSCALL(kse_release) > (gdb) bt > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > #1 0x000000080141d926 in sig_daemon (arg=0x7fffffefef70) > at /usr/src/lib/libpthread/thread/thr_sig.c:216 > #2 0x0000000801426db5 in kse_sched_single (kmbx=0x7fffffefef70) > at /usr/src/lib/libpthread/thread/thr_kern.c:902 > > (gdb) thread 2 > [Switching to thread 2 (Thread 7 (sleeping))]#0 > _thr_sched_switch_unlocked ( > curthread=0x632000) at pthread_md.h:226 > 226 if (ret == 0) { > Current language: auto; currently c > (gdb) bt > #0 _thr_sched_switch_unlocked (curthread=0x632000) at pthread_md.h:226 > #1 0x00000008014265e0 in _thr_sched_switch (curthread=0x632000) > at /usr/src/lib/libpthread/thread/thr_kern.c:607 > #2 0x0000000801419cb4 in _pthread_join (pthread=0x74b000, > thread_return=0x0) > at /usr/src/lib/libpthread/thread/thr_join.c:133 > #3 0x0000000800719d09 in ldap_pvt_thread_join (thread=0x800609070, > thread_return=0x62a068) at thr_posix.c:165 > > (gdb) thread 3 > [Switching to thread 3 (LWP 100148)]#0 0x000000080142e914 in > kse_release () > at kse_release.S:2 > 2 RSYSCALL(kse_release) > Current language: auto; currently asm > (gdb) bt > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > #1 0x0000000801428e49 in kse_wait (kse=0x62a000, td_wait=0x0, > sigseqno=0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > #2 0x0000000801427078 in kse_sched_multi (kmbx=0x62efa0) > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > #3 0x000000080142afbf in _amd64_enter_uts () > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > > > > > > > (gdb) bt > > > #0 0x000000080142e914 in kse_release () at kse_release.S:2 > > > #1 0x0000000801428e49 in kse_wait (kse=0x62a000, td_wait=0x0, > > > sigseqno=0) > > > at /usr/src/lib/libpthread/thread/thr_kern.c:1843 > > > #2 0x0000000801427078 in kse_sched_multi (kmbx=0x62efa0) > > > at /usr/src/lib/libpthread/thread/thr_kern.c:1039 > > > #3 0x000000080142afbf in _amd64_enter_uts () > > > at /usr/src/lib/libpthread/arch/amd64/amd64/enter_uts.S:40 > > > #4 0x0000000000000000 in ?? () > > > #5 0x000000000062f000 in ?? () > > > #6 0x000000000062a000 in ?? () > > > #7 0x0000000000000000 in ?? () > > > #8 0x0000000000000000 in ?? () > > > #9 0x0000000000000000 in ?? () > > > #10 0x0000000000000000 in ?? () > > > #11 0x0000000000000000 in ?? () > > > #12 0x0000000000000001 in ?? () > > > #13 0x0000000801426dd0 in _thr_sched_switch_unlocked () > > > at /usr/src/lib/libpthread/thread/thr_kern.c:904 > > > Previous frame inner to this frame (corrupt stack?) > > > > > > > > > -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 03:02:56 2004 Return-Path: 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 26B4D16A4CE for ; Thu, 18 Nov 2004 03:02:56 +0000 (GMT) Received: from neo.redjade.org (neo.redjade.org [219.254.21.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7181243D49 for ; Thu, 18 Nov 2004 03:02:55 +0000 (GMT) (envelope-from ssw@neo.redjade.org) Received: from neo.redjade.org (localhost [127.0.0.1]) by neo.redjade.org (8.13.1/8.13.1) with ESMTP id iAI336nS060203; Thu, 18 Nov 2004 12:03:06 +0900 (KST) (envelope-from ssw@neo.redjade.org) Received: (from ssw@localhost) by neo.redjade.org (8.13.1/8.13.1/Submit) id iAI336vY060202; Thu, 18 Nov 2004 12:03:06 +0900 (KST) (envelope-from ssw) Date: Thu, 18 Nov 2004 12:03:06 +0900 From: Sangwoo Shim To: Tai-hwa Liang Message-ID: <20041118030306.GA59867@neo.redjade.org> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> <20041117225735.GA2148@gothmog.gr> <04111807243512.21298@www.mmlab.cse.yzu.edu.tw> Mime-Version: 1.0 Content-Type: text/plain; charset=euc-kr Content-Disposition: inline In-Reply-To: <04111807243512.21298@www.mmlab.cse.yzu.edu.tw> User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:02:56 -0000 On Thu, Nov 18, 2004 at 07:25:58AM +0800, Tai-hwa Liang wrote: > On Thu, 18 Nov 2004, Giorgos Keramidas wrote: > >On 2004-11-17 13:31, Tillman Hodgson wrote: > [...] > >>Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined > >>Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. > >> > >>My custom kernel doesn't include IPv6. Does pf truly require IPv6?: > > > >Yes, if you want to load it as a module. This is exactly the same thing > >I bumped into last night. Compiling a kernel with INET6 support will > >let you load pf as a module. > > Does define "NOINET6=yes" in your /etc/make.conf and rebuild the kernel > work for you? I think that should work. And to save him from compiling entire kernel, Just compiling (and installing) pf module by doing "make NOINET6=yes" in /sys/modules/pf will also work. :-) Regards, Sangwoo Shim From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 03:44:20 2004 Return-Path: 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 B51D716A4CE; Thu, 18 Nov 2004 03:44:20 +0000 (GMT) Received: from ylpvm29.prodigy.net (ylpvm29-ext.prodigy.net [207.115.57.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B06A43D31; Thu, 18 Nov 2004 03:44:20 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAI3i2DU010770; Wed, 17 Nov 2004 22:44:03 -0500 Message-ID: <419C1A7A.6050000@root.org> Date: Wed, 17 Nov 2004 19:43:54 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> In-Reply-To: <20041117.202521.74694027.imp@harmony.village.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:44:20 -0000 Warner Losh wrote: > From: Nate Lawson > Subject: Re: [PATCH] Please test: new ACPI release (20041105) import > Date: Wed, 17 Nov 2004 17:53:43 -0800 > > >>Warner Losh wrote: >> >>>>I do suspect that this is a PCI power issue and not an ACPI issue, but >>>>I'd like to know if it shows up on more models. It is most obvious when >>>>playing a stream as the buffers keep emptying and the sound stops after >>>>a short time. Music is clearly too fast and high pitched, but at 10% >>>>overspeed, some may not notice. (Does Dr. Dre sound much different 10% >>>>faster?) >>> >>>I've flipped the sense of the PCI power sysctl in current. Once >>>that's sanner, we should investigate setting the power states on >>>resume. Not sure what to do about suspend, since I think that acpi >>>has different notions of what D level to put a device in for different >>>S levels and it would likely have to take care of that after giving >>>the device a chance to save state. >>> >>>Warner >> >>I have a patch in my tree to do this. I'll post it once it's >>well-tested. At the moment, setting UART to D3 appears to hang the >>system and I'm not sure why. > > > What do you mean 'UART'? I'm confused... My serial port. It's named UART in the AML, that's all. Setting it to D3 hangs the system. -Nate From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 04:57:56 2004 Return-Path: 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 450F016A4CE for ; Thu, 18 Nov 2004 04:57:56 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id E484043D3F for ; Thu, 18 Nov 2004 04:57:55 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 7A290F20B8; Wed, 17 Nov 2004 20:57:55 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36126-04; Wed, 17 Nov 2004 20:57:49 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 6E7D9F18DB; Wed, 17 Nov 2004 20:57:49 -0800 (PST) From: Sean McNeil To: Doug White In-Reply-To: <20041117183453.C29048@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> <20041117102623.P25028@carver.gumbysoft.com> <1100725008.21333.2.camel@server.mcneil.com> <20041117183453.C29048@carver.gumbysoft.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-q4eF2oGgZ5IDtK5zVx5W" Date: Wed, 17 Nov 2004 20:57:49 -0800 Message-Id: <1100753869.21798.74.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 04:57:56 -0000 --=-q4eF2oGgZ5IDtK5zVx5W Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-11-17 at 18:36 -0800, Doug White wrote: > On Wed, 17 Nov 2004, Sean McNeil wrote: >=20 > > On Wed, 2004-11-17 at 10:28 -0800, Doug White wrote: > > > On Tue, 16 Nov 2004, Sean McNeil wrote: > > > > > > > This has been happening for a long time with current and hasn't bee= n > > > > resolved. When I start up slapd, I cannot stop it without kill -9 = ing > > > > it. It would appear stuck in kse and probably has something to do = with > > > > kill -0: > > > > > > Mind expanding on this? The backtrace looks normal for a pthread proc= ess. > > > kill -0 just tests signal delivery; the process is completely unaware= that > > > the probe occured, though. The process may also be unkillable if its > > > stuck in some sort of I/O wait. > > > > > > Is the server busy when you signal it? > > > > Oh, OK. I didn't look at /usr/local/etc/rc.subr too closely. I have > > additional information, though.... > > > > It appears that all the threads are destroyed yet it is still in the > > thread processing loop. The process is no longer active at all. I jus= t > > had a similar problem happen with vlc where I closed it yet it is > > hanging in the same place as slapd with all the threads gone. >=20 > Interesting... what scheduler are you using? 4BSD with PREEMPTION on. -CURRENT as of yesterday. This has been an issue for quite some time now, however. > > > > Here is the one from vlc: > > > > (gdb) bt full > > #0 _thr_sched_switch_unlocked (curthread=3D0x955000) at pthread_md.h:2= 26 >=20 > I can't find a reference to this in that file. Can you run ldd against > your vlc binary? I('m curious what thread library it thinks its running. /usr/X11R6/bin/vlc: libiconv.so.3 =3D> /usr/local/lib/libiconv.so.3 (0x800955000) libintl.so.6 =3D> /usr/local/lib/libintl.so.6 (0x800b48000) libz.so.2 =3D> /lib/libz.so.2 (0x800c52000) libxvidcore.so.4 =3D> /usr/local/lib/libxvidcore.so.4 (0x800d65000) libfaad.so.0 =3D> /usr/local/lib/libfaad.so.0 (0x800f3f000) libvorbis.so.3 =3D> /usr/local/lib/libvorbis.so.3 (0x801087000) libvorbisenc.so.2 =3D> /usr/local/lib/libvorbisenc.so.2 (0x8011b3000) libmp3lame.so.0 =3D> /usr/local/lib/libmp3lame.so.0 (0x801491000) libm.so.3 =3D> /lib/libm.so.3 (0x80162c000) liba52.so.0 =3D> /usr/local/lib/liba52.so.0 (0x80174e000) libtheora.so.0 =3D> /usr/local/lib/libtheora.so.0 (0x80185a000) libogg.so.5 =3D> /usr/local/lib/libogg.so.5 (0x801979000) libstdc++.so.4 =3D> /usr/lib/libstdc++.so.4 (0x801a7e000) libpthread.so.1 =3D> /usr/lib/libpthread.so.1 (0x801c7c000) libc.so.6 =3D> /lib/libc.so.6 (0x801da6000) I just ran it again and had a thread sitting at _thr_sched_switch_unlocked. Here is the trace for that thread: (gdb) bt #0 _thr_sched_switch_unlocked (curthread=3D0x1b38c00) at pthread_md.h:226 #1 0x0000000801c8da8f in _nanosleep (time_to_sleep=3D0x7fffffe8df50, time_remaining=3D0x0) at /usr/src/lib/libpthread/thread/thr_nanosleep.c:71 #2 0x0000000801c8dbd3 in __nanosleep (time_to_sleep=3D0x7fffffe8df50, time_remaining=3D0x0) at /usr/src/lib/libpthread/thread/thr_nanosleep.c:125 #3 0x000000000042b1f9 in msleep (delay=3D34369437808) at src/misc/mtime.c:309 #4 0x0000000806a51e02 in OSSThread (p_aout=3D0x1b38800) at oss.c:624 #5 0x0000000801c87139 in thread_start (curthread=3D0x800940070, start_routine=3D0x94d068, arg=3D0x800940070) at /usr/src/lib/libpthread/thread/thr_create.c:343 #6 0x0000000801df1ff4 in makectx_wrapper (ucp=3D0x800940060, func=3D0x6636= , args=3D0x1) at /usr/src/lib/libc/amd64/gen/makecontext.c:100 --=-q4eF2oGgZ5IDtK5zVx5W Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnCvNyQsGN30uGE4RAix9AKCtUnxpRDUfDqfx5hGA2ZPtzPg6RgCgt0Ha aggkSUONSWqSXc0lhabbeZk= =6ZmJ -----END PGP SIGNATURE----- --=-q4eF2oGgZ5IDtK5zVx5W-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 05:10:28 2004 Return-Path: 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 0C96516A4CE for ; Thu, 18 Nov 2004 05:10:28 +0000 (GMT) Received: from imf20aec.mail.bellsouth.net (imf20aec.mail.bellsouth.net [205.152.59.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CFE343D55 for ; Thu, 18 Nov 2004 05:10:27 +0000 (GMT) (envelope-from ahze@ahze.net) Received: from [192.168.1.5] ([68.209.163.3]) by imf20aec.mail.bellsouth.netESMTP <20041118051026.JSAS2350.imf20aec.mail.bellsouth.net@[192.168.1.5]>; Thu, 18 Nov 2004 00:10:26 -0500 In-Reply-To: <1100753869.21798.74.camel@server.mcneil.com> References: <1100657472.74795.2.camel@server.mcneil.com> <20041117102623.P25028@carver.gumbysoft.com> <1100725008.21333.2.camel@server.mcneil.com> <20041117183453.C29048@carver.gumbysoft.com> <1100753869.21798.74.camel@server.mcneil.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Apple-Mail-9-40853896" Message-Id: <25A791B2-3920-11D9-96CC-000A958C81C6@ahze.net> Content-Transfer-Encoding: 7bit From: Michael Johnson Date: Thu, 18 Nov 2004 00:10:21 -0500 To: Sean McNeil X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 05:10:28 -0000 --Apple-Mail-9-40853896 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; format=flowed On Nov 17, 2004, at 11:57 PM, Sean McNeil wrote: > On Wed, 2004-11-17 at 18:36 -0800, Doug White wrote: >> On Wed, 17 Nov 2004, Sean McNeil wrote: >> >>> On Wed, 2004-11-17 at 10:28 -0800, Doug White wrote: >>>> On Tue, 16 Nov 2004, Sean McNeil wrote: >>>> >>>>> This has been happening for a long time with current and hasn't >>>>> been >>>>> resolved. When I start up slapd, I cannot stop it without kill -9 >>>>> ing >>>>> it. It would appear stuck in kse and probably has something to do >>>>> with >>>>> kill -0: >>>> >>>> Mind expanding on this? The backtrace looks normal for a pthread >>>> process. >>>> kill -0 just tests signal delivery; the process is completely >>>> unaware that >>>> the probe occured, though. The process may also be unkillable if >>>> its >>>> stuck in some sort of I/O wait. >>>> >>>> Is the server busy when you signal it? >>> >>> Oh, OK. I didn't look at /usr/local/etc/rc.subr too closely. I have >>> additional information, though.... >>> >>> It appears that all the threads are destroyed yet it is still in the >>> thread processing loop. The process is no longer active at all. I >>> just >>> had a similar problem happen with vlc where I closed it yet it is >>> hanging in the same place as slapd with all the threads gone. >> >> Interesting... what scheduler are you using? > > 4BSD with PREEMPTION on. -CURRENT as of yesterday. This has been an > issue for quite some time now, however. > >>> >>> Here is the one from vlc: >>> >>> (gdb) bt full >>> #0 _thr_sched_switch_unlocked (curthread=0x955000) at >>> pthread_md.h:226 >> >> I can't find a reference to this in that file. Can you run ldd >> against >> your vlc binary? I('m curious what thread library it thinks its >> running. > Is this vlc 0.7.2 or 0.8.1? > /usr/X11R6/bin/vlc: > libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x800955000) > libintl.so.6 => /usr/local/lib/libintl.so.6 (0x800b48000) > libz.so.2 => /lib/libz.so.2 (0x800c52000) > libxvidcore.so.4 => /usr/local/lib/libxvidcore.so.4 > (0x800d65000) > libfaad.so.0 => /usr/local/lib/libfaad.so.0 (0x800f3f000) > libvorbis.so.3 => /usr/local/lib/libvorbis.so.3 (0x801087000) > libvorbisenc.so.2 => /usr/local/lib/libvorbisenc.so.2 > (0x8011b3000) > libmp3lame.so.0 => /usr/local/lib/libmp3lame.so.0 (0x801491000) > libm.so.3 => /lib/libm.so.3 (0x80162c000) > liba52.so.0 => /usr/local/lib/liba52.so.0 (0x80174e000) > libtheora.so.0 => /usr/local/lib/libtheora.so.0 (0x80185a000) > libogg.so.5 => /usr/local/lib/libogg.so.5 (0x801979000) > libstdc++.so.4 => /usr/lib/libstdc++.so.4 (0x801a7e000) > libpthread.so.1 => /usr/lib/libpthread.so.1 (0x801c7c000) > libc.so.6 => /lib/libc.so.6 (0x801da6000) > > I just ran it again and had a thread sitting at > _thr_sched_switch_unlocked. Here is the trace for that thread: > > (gdb) bt > #0 _thr_sched_switch_unlocked (curthread=0x1b38c00) at > pthread_md.h:226 > #1 0x0000000801c8da8f in _nanosleep (time_to_sleep=0x7fffffe8df50, > time_remaining=0x0) > at /usr/src/lib/libpthread/thread/thr_nanosleep.c:71 > #2 0x0000000801c8dbd3 in __nanosleep (time_to_sleep=0x7fffffe8df50, > time_remaining=0x0) > at /usr/src/lib/libpthread/thread/thr_nanosleep.c:125 > #3 0x000000000042b1f9 in msleep (delay=34369437808) at > src/misc/mtime.c:309 > #4 0x0000000806a51e02 in OSSThread (p_aout=0x1b38800) at oss.c:624 > #5 0x0000000801c87139 in thread_start (curthread=0x800940070, > start_routine=0x94d068, arg=0x800940070) > at /usr/src/lib/libpthread/thread/thr_create.c:343 > #6 0x0000000801df1ff4 in makectx_wrapper (ucp=0x800940060, > func=0x6636, > args=0x1) at /usr/src/lib/libc/amd64/gen/makecontext.c:100 > > --Apple-Mail-9-40853896 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: This is a digitally signed message part content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFBnC69n4uqfTwEb9YRAkPeAJ9EeECY8ciZN+ebhMQqpUEHRrqA8wCeKjnf 6+62SpV1SP1eCjfGl49sYlE= =ZALX -----END PGP SIGNATURE----- --Apple-Mail-9-40853896-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 05:42:45 2004 Return-Path: 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 AB74316A4CE; Thu, 18 Nov 2004 05:42:45 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD32343D1D; Thu, 18 Nov 2004 05:42:44 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAI5fjZg028980; Thu, 18 Nov 2004 16:11:45 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id ; Thu, 18 Nov 2004 16:12:33 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAI5aSh07235; Thu, 18 Nov 2004 16:06:29 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDQ9WC; Thu, 18 Nov 2004 16:06:18 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAI5bOTQ068357 ; Thu, 18 Nov 2004 16:07:24 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAI5bOxb068356; Thu, 18 Nov 2004 16:07:24 +1030 (CST) (envelope-from wilkinsa) Date: Thu, 18 Nov 2004 16:07:24 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041118053724.GS66822@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org, jhb@FreeBSD.org References: <20041116021421.GK56252@squash.dsto.defence.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6i Subject: Re: bge(4) watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 05:42:46 -0000 Well, if I do that I will be using the old AT-PIC. Which as far as I am aware is old and crusty ;-\ Is this correct john ? -aW 0n Wed, Nov 17, 2004 at 06:56:13PM +0100, Arno J. Klaassen wrote: "Wilkinson, Alex" writes: > I get the following errors, however, although it states that there is no > carrier, there is. > > bge0: firmware handshake timed out > bge0: RX CPU self-diagnostics failed! > bge0: flags=8843 mtu 1500 > options=1a > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > ether 00:11:0a:40:d2:dd > media: Ethernet autoselect (none) > status: no carrier > > Mounting NFS file systems:bge0: watchdog timeout -- resetting > > > Here is ifconfig(8) output after fully booted: > > bge0: flags=8843 mtu 1500 > options=1a > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > ether 00:11:0a:40:d2:dd > media: Ethernet autoselect (100baseTX ) > status: active > > Seems odd enough, to email the wizards about it. one of my co-workers had a similar problem (PR 73538). Leaving out "device apic" from the kernel-config "fixed" the problem. YMMV Arno From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 05:47:38 2004 Return-Path: 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 75F4616A4CE for ; Thu, 18 Nov 2004 05:47:38 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29BFE43D53 for ; Thu, 18 Nov 2004 05:47:38 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id E360CF20AE; Wed, 17 Nov 2004 21:47:37 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 36126-06; Wed, 17 Nov 2004 21:47:36 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 11EF6F1983; Wed, 17 Nov 2004 21:47:36 -0800 (PST) From: Sean McNeil To: Michael Johnson In-Reply-To: <25A791B2-3920-11D9-96CC-000A958C81C6@ahze.net> References: <1100657472.74795.2.camel@server.mcneil.com> <20041117102623.P25028@carver.gumbysoft.com> <1100725008.21333.2.camel@server.mcneil.com> <20041117183453.C29048@carver.gumbysoft.com> <1100753869.21798.74.camel@server.mcneil.com> <25A791B2-3920-11D9-96CC-000A958C81C6@ahze.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NKMMcdICEJHXLOvR21oL" Date: Wed, 17 Nov 2004 21:47:35 -0800 Message-Id: <1100756855.21798.77.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 05:47:38 -0000 --=-NKMMcdICEJHXLOvR21oL Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-11-18 at 00:10 -0500, Michael Johnson wrote: > On Nov 17, 2004, at 11:57 PM, Sean McNeil wrote: >=20 > > On Wed, 2004-11-17 at 18:36 -0800, Doug White wrote: > >> On Wed, 17 Nov 2004, Sean McNeil wrote: > >> > >>> On Wed, 2004-11-17 at 10:28 -0800, Doug White wrote: > >>>> On Tue, 16 Nov 2004, Sean McNeil wrote: > >>>> > >>>>> This has been happening for a long time with current and hasn't=20 > >>>>> been > >>>>> resolved. When I start up slapd, I cannot stop it without kill -9=20 > >>>>> ing > >>>>> it. It would appear stuck in kse and probably has something to do=20 > >>>>> with > >>>>> kill -0: > >>>> > >>>> Mind expanding on this? The backtrace looks normal for a pthread=20 > >>>> process. > >>>> kill -0 just tests signal delivery; the process is completely=20 > >>>> unaware that > >>>> the probe occured, though. The process may also be unkillable if=20 > >>>> its > >>>> stuck in some sort of I/O wait. > >>>> > >>>> Is the server busy when you signal it? > >>> > >>> Oh, OK. I didn't look at /usr/local/etc/rc.subr too closely. I have > >>> additional information, though.... > >>> > >>> It appears that all the threads are destroyed yet it is still in the > >>> thread processing loop. The process is no longer active at all. I=20 > >>> just > >>> had a similar problem happen with vlc where I closed it yet it is > >>> hanging in the same place as slapd with all the threads gone. > >> > >> Interesting... what scheduler are you using? > > > > 4BSD with PREEMPTION on. -CURRENT as of yesterday. This has been an > > issue for quite some time now, however. > > > >>> > >>> Here is the one from vlc: > >>> > >>> (gdb) bt full > >>> #0 _thr_sched_switch_unlocked (curthread=3D0x955000) at=20 > >>> pthread_md.h:226 > >> > >> I can't find a reference to this in that file. Can you run ldd=20 > >> against > >> your vlc binary? I('m curious what thread library it thinks its=20 > >> running. > > >=20 >=20 > Is this vlc 0.7.2 or 0.8.1? VLC media player 0.8.1 Janus built Nov 16 23:05 amd64/current machine. --=-NKMMcdICEJHXLOvR21oL Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnDd3yQsGN30uGE4RAu5gAJ9/7OlxWo1HNHUOAqCx7ltkHwpjkwCfXCFw SpS204qiTTzfZXEd+m6TSyE= =VRmI -----END PGP SIGNATURE----- --=-NKMMcdICEJHXLOvR21oL-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 06:01:54 2004 Return-Path: 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 DAF0816A4CE; Thu, 18 Nov 2004 06:01:54 +0000 (GMT) Received: from ylpvm15.prodigy.net (ylpvm15-ext.prodigy.net [207.115.57.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9350D43D2D; Thu, 18 Nov 2004 06:01:54 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-186-185.dsl.snfc21.pacbell.net [64.171.186.185])iAI61rdl019655; Thu, 18 Nov 2004 01:01:53 -0500 Message-ID: <419C3AC2.5010505@root.org> Date: Wed, 17 Nov 2004 22:01:38 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040901) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Warner Losh References: <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> <419C1A7A.6050000@root.org> <20041117.204804.71148446.imp@harmony.village.org> In-Reply-To: <20041117.204804.71148446.imp@harmony.village.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 06:01:55 -0000 Warner Losh wrote: >>My serial port. It's named UART in the AML, that's all. Setting it to >>D3 hangs the system. > > Is it a PCI device too? If not, then maybe you need to disable > interrupts in the UART before setting the power state. Chances are > its interrupt cause register is returning 0xff, which hangs sio, since > it never breaks out of the loop when this happens. It is not, it's a legacy device: sio0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC_.UART The power methods for it are: Method (_PS0, 0, NotSerialized) { Store (0x03, LDN) Store (0x01, LDA) Store (0x01, SSBY) } Method (_PS3, 0, NotSerialized) { Store (0x03, LDN) Store (0x00, LDA) Store (0x00, SSBY) } The regions accessed by these Store ops are as follows, and all appear to be mapped to the ICH: OperationRegion (IMGA, SystemIO, 0x15E0, 0x10) OperationRegion (NCFG, SystemIO, 0x2E, 0x02) Is there a standard for how to do power transitions for non-PCI devices? I thought you just call the acpi methods if present. -Nate From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 08:25:34 2004 Return-Path: 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 A3B2116A4CE; Thu, 18 Nov 2004 08:25:34 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A567E43D62; Thu, 18 Nov 2004 08:25:33 +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 iAI8PWGm081711; Thu, 18 Nov 2004 10:25:32 +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 16653-17; Thu, 18 Nov 2004 10:25:31 +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 iAI8PVLY081708 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Nov 2004 10:25:31 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAI8PX3u071664; Thu, 18 Nov 2004 10:25:33 +0200 (EET) (envelope-from ru) Date: Thu, 18 Nov 2004 10:25:33 +0200 From: Ruslan Ermilov To: Giorgos Keramidas Message-ID: <20041118082533.GE60828@ip.net.ua> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> <20041117193119.GP76234@seekingfire.com> <20041117225735.GA2148@gothmog.gr> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="AH+kv8CCoFf6qPuz" Content-Disposition: inline In-Reply-To: <20041117225735.GA2148@gothmog.gr> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: current@freebsd.org Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 08:25:34 -0000 --AH+kv8CCoFf6qPuz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Nov 18, 2004 at 12:57:35AM +0200, Giorgos Keramidas wrote: > On 2004-11-17 13:31, Tillman Hodgson wrote: > > On Wed, Nov 17, 2004 at 10:11:08AM -0800, Mike Hunter wrote: > > > Check dmesg. There's a bug somewhere that causes kldload to report "file > > > not found" to the user even though it was some other error that caused the > > > problem. That real error can sometimes be spit out to the console / > > > syslog / whatever. > > > > Oh! I should have checked syslog, my apologies. > > > > Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined > > Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. > > > > My custom kernel doesn't include IPv6. Does pf truly require IPv6?: > > Yes, if you want to load it as a module. This is exactly the same thing > I bumped into last night. Compiling a kernel with INET6 support will > let you load pf as a module. > > I'm not sure if this is a `bug' that neds fixing though ;-) > I've been investigating this problem recently. It's a royal PITA that modules that get compiled with the kernel cannot be linked into it. I tried to brute-force it by applying an attached patch (it has a portion for modules/pf/Makefile), but it soon became clear that it's not that all simple. The real fix would involve carefully looking into every module makefile that generates opt_*.h files (currently, 63 makefiles), and in the case of a module build with the kernel (KERNBUILDDIR is defined), generate only those headers that this "device" is responsible for. For example, the portion for if_disc in the attached makefile is correct, as disc(4) can be compiled with any combination of INET and INET6 options, even when both are undefined. And the portion for pf/Makefile should look like this, i.e., always generate opt_pf.h, but take opt_inet[6].h and opt_bpf.h from the kernel. %%% Index: Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/pf/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- Makefile 1 Sep 2004 07:39:12 -0000 1.5 +++ Makefile 18 Nov 2004 08:06:31 -0000 @@ -16,6 +16,7 @@ echo "#define DEV_PF 1" > opt_pf.h echo "#define DEV_PFLOG 1" >> opt_pf.h +.if !defined(KERNBUILDDIR) opt_inet.h: echo "#define INET 1" > opt_inet.h @@ -28,5 +29,6 @@ opt_bpf.h: echo "#define DEV_BPF 1" > opt_bpf.h +.endif .include %%% Unfortunately, while it's indeed correct for opt_*.h files, the SRCS list still assumes that option INET is present in the kernel (in4_cksum.c is compiled unconditionally), and some things are just not designed to work without some options, like option INET in this case, but their dependency is incorrect. For example, attempting to build a pf module with this patch and a kernel without INET option results in: : In file included from /usr/src/sys/modules/pf/../../contrib/pf/net/if_pflog.c:81: : ./machine/in_cksum.h:54: warning: "struct ip" declared inside parameter list : ./machine/in_cksum.h:54: warning: its scope is only this definition or declaration, which is probably not what you want : ./machine/in_cksum.h:80: warning: "struct ip" declared inside parameter list : ./machine/in_cksum.h: In function `in_cksum_update': : ./machine/in_cksum.h:83: error: dereferencing pointer to incomplete type : ./machine/in_cksum.h:84: error: dereferencing pointer to incomplete type : *** Error code 1 But if_pflog.c doesn't show a dependency on "option INET" in sys/conf/files: # grep if_pflog.c /sys/conf/files contrib/pf/net/if_pflog.c optional pflog I think everyone who has looked into it knows how broken the current module system is in this respect. But then we think about opt_bpf.h... If pf had a module dependency on bpf, then we could unconditionally compile BPF support into the pf module. In the end I gave up on this, as it became clear that modules build system needs a good redesign. My current feeling is that sys/modules should die, and modules build infrastructure should be generated by config(8). For example, you create a config file and either tell it to build everything statically into one kernel object, or build all (or part) that it can as modules. Cheers, -- Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --AH+kv8CCoFf6qPuz Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: if_disc/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_disc/Makefile,v retrieving revision 1.17 diff -u -r1.17 Makefile --- if_disc/Makefile 11 Jan 2002 15:48:40 -0000 1.17 +++ if_disc/Makefile 3 Nov 2004 20:17:20 -0000 @@ -5,10 +5,12 @@ KMOD= if_disc SRCS= if_disc.c opt_inet.h opt_inet6.h +.if !defined(KERNBUILDDIR) opt_inet.h: echo "#define INET 1" > ${.TARGET} -#opt_inet6.h: -# echo "#define INET6 1" > ${.TARGET} +opt_inet6.h: + echo "#define INET6 1" > ${.TARGET} +.endif .include Index: if_ef/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_ef/Makefile,v retrieving revision 1.11 diff -u -r1.11 Makefile --- if_ef/Makefile 19 Jan 2004 14:00:26 -0000 1.11 +++ if_ef/Makefile 3 Nov 2004 20:25:06 -0000 @@ -16,11 +16,13 @@ CFLAGS+= -DEF_DEBUG .endif +.if !defined(KERNBUILDDIR) opt_inet.h: echo "#define INET 1" > opt_inet.h opt_ipx.h: echo "#define IPX 1" > opt_ipx.h +.endif opt_ef.h: .for frame in ETHER_II ETHER_8023 ETHER_8022 ETHER_SNAP Index: if_faith/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_faith/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- if_faith/Makefile 11 Jan 2002 15:48:46 -0000 1.2 +++ if_faith/Makefile 3 Nov 2004 20:26:19 -0000 @@ -5,10 +5,12 @@ KMOD= if_faith SRCS= if_faith.c opt_inet.h opt_inet6.h +.if !defined(KERNBUILDDIR) opt_inet.h: echo "#define INET 1" > ${.TARGET} opt_inet6.h: echo "#define INET6 1" > ${.TARGET} +.endif .include Index: if_gif/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/if_gif/Makefile,v retrieving revision 1.3 diff -u -r1.3 Makefile --- if_gif/Makefile 12 Aug 2002 15:27:17 -0000 1.3 +++ if_gif/Makefile 3 Nov 2004 20:33:32 -0000 @@ -6,6 +6,7 @@ SRCS= if_gif.c in_gif.c in6_gif.c opt_inet.h opt_inet6.h opt_mac.h \ opt_mrouting.h +.if !defined(KERNBUILDDIR) opt_inet.h: echo "#define INET 1" > ${.TARGET} @@ -14,5 +15,6 @@ opt_mrouting.h: echo "#define MROUTING 1" > ${.TARGET} +.endif .include Index: netgraph/bluetooth/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/netgraph/bluetooth/Makefile,v retrieving revision 1.2 diff -u -r1.2 Makefile --- netgraph/bluetooth/Makefile 10 May 2003 21:44:37 -0000 1.2 +++ netgraph/bluetooth/Makefile 24 Oct 2004 06:26:10 -0000 @@ -3,13 +3,12 @@ SUBDIR= \ bluetooth \ - hci \ - l2cap \ - socket \ - bt3c \ - h4 \ - ubt \ + bt3c \ + h4 \ + hci \ + l2cap \ + socket \ + ubt \ ubtbcmfw .include - Index: pf/Makefile =================================================================== RCS file: /home/ncvs/src/sys/modules/pf/Makefile,v retrieving revision 1.5 diff -u -r1.5 Makefile --- pf/Makefile 1 Sep 2004 07:39:12 -0000 1.5 +++ pf/Makefile 3 Nov 2004 15:26:53 -0000 @@ -12,6 +12,7 @@ CFLAGS+= -I${.CURDIR}/../../contrib/pf +.if !defined(KERNBUILDDIR) opt_pf.h: echo "#define DEV_PF 1" > opt_pf.h echo "#define DEV_PFLOG 1" >> opt_pf.h @@ -28,5 +29,6 @@ opt_bpf.h: echo "#define DEV_BPF 1" > opt_bpf.h +.endif .include --AH+kv8CCoFf6qPuz-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 09:43:00 2004 Return-Path: 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 0BE6816A4CE; Thu, 18 Nov 2004 09:43:00 +0000 (GMT) Received: from darkness.comp.waw.pl (darkness.comp.waw.pl [195.117.238.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 833E443D46; Thu, 18 Nov 2004 09:42:59 +0000 (GMT) (envelope-from pjd@darkness.comp.waw.pl) Received: by darkness.comp.waw.pl (Postfix, from userid 1009) id 00031ACC5F; Thu, 18 Nov 2004 10:42:57 +0100 (CET) Date: Thu, 18 Nov 2004 10:42:57 +0100 From: Pawel Jakub Dawidek To: Emanuel Strobl Message-ID: <20041118094257.GB8120@darkness.comp.waw.pl> References: <200411172357.47735.Emanuel.Strobl@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xNzB6LhEaj9ZrCy/" Content-Disposition: inline In-Reply-To: <200411172357.47735.Emanuel.Strobl@gmx.net> User-Agent: Mutt/1.4.2i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 5.2.1-RC2 i386 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 09:43:00 -0000 --xNzB6LhEaj9ZrCy/ Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 11:57:41PM +0100, Emanuel Strobl wrote: +> Dear best guys, +>=20 +> I really love 5.3 in many ways but here're some unbelievable transfer ra= tes,=20 +> after I went out and bought a pair of Intel GigaBit Ethernet Cards to so= lve=20 +> my performance problem (*laugh*): [...] I done some test in the past with ggate and PCI64/GBit NICs and I get ~38MB/s AFAIR. Remember that when using 32bit PCIs you can get transfer about 500Mbit/s. Please run those test with netperf (/usr/ports/benchmarks/netperf) and send results. --=20 Pawel Jakub Dawidek http://www.FreeBSD.org pjd@FreeBSD.org http://garage.freebsd.pl FreeBSD committer Am I Evil? Yes, I Am! --xNzB6LhEaj9ZrCy/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFBnG6hForvXbEpPzQRAiWEAKCCCs0Bunrps3dD5uNxQMiwVi5YkACgkWyk UPTBOoSdpRDWGubIY7lq80o= =UeDX -----END PGP SIGNATURE----- --xNzB6LhEaj9ZrCy/-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 12:29:17 2004 Return-Path: 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 71CBF16A4CE; Thu, 18 Nov 2004 12:29:17 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id F30E043D54; Thu, 18 Nov 2004 12:29:16 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAICRi9L069152; Thu, 18 Nov 2004 07:27:44 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAICRiVU069149; Thu, 18 Nov 2004 12:27:44 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 18 Nov 2004 12:27:44 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Emanuel Strobl In-Reply-To: <200411172357.47735.Emanuel.Strobl@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 12:29:17 -0000 On Wed, 17 Nov 2004, Emanuel Strobl wrote: > I really love 5.3 in many ways but here're some unbelievable transfer > rates, after I went out and bought a pair of Intel GigaBit Ethernet > Cards to solve my performance problem (*laugh*): I think the first thing you want to do is to try and determine whether the problem is a link layer problem, network layer problem, or application (file sharing) layer problem. Here's where I'd start looking: (1) I'd first off check that there wasn't a serious interrupt problem on the box, which is often triggered by ACPI problems. Get the box to be as idle as possible, and then use vmstat -i or stat -vmstat to see if anything is spewing interrupts. (2) Confirm that your hardware is capable of the desired rates: typically this involves looking at whether you have a decent card (most if_em cards are decent), whether it's 32-bit or 64-bit PCI, and so on. For unidirectional send on 32-bit PCI, be aware that it is not possible to achieve gigabit performance because the PCI bus isn't fast enough, for example. (3) Next, I'd use a tool like netperf (see ports collection) to establish three characteristics: round trip latency from user space to user space (UDP_RR), TCP throughput (TCP_STREAM), and large packet throughput (UDP_STREAM). With decent boxes on 5.3, you should have no trouble at all maxing out a single gig-e with if_em, assuming all is working well hardware wise and there's no software problem specific to your configuration. (4) Note that router latency (and even switch latency) can have a substantial impact on gigabit performance, even with no packet loss, in part due to stuff like ethernet flow control. You may want to put the two boxes back-to-back for testing purposes. (5) Next, I'd measure CPU consumption on the end box -- in particular, use top -S and systat -vmstat 1 to compare the idle condition of the system and the system under load. If you determine there is a link layer or IP layer problem, we can start digging into things like the error statistics in the card, negotiation issues, etc. If not, you want to move up the stack to try and characterize where it is you're hitting the performance issue. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 12:33:54 2004 Return-Path: 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 2B28216A4CE; Thu, 18 Nov 2004 12:33:54 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B736243D31; Thu, 18 Nov 2004 12:33:53 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAICWMup069220; Thu, 18 Nov 2004 07:32:22 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAICWLPl069217; Thu, 18 Nov 2004 12:32:22 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 18 Nov 2004 12:32:21 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Pawel Jakub Dawidek In-Reply-To: <20041118094257.GB8120@darkness.comp.waw.pl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Emanuel Strobl cc: freebsd-current@FreeBSD.org cc: freebsd-stable@FreeBSD.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 12:33:54 -0000 On Thu, 18 Nov 2004, Pawel Jakub Dawidek wrote: > On Wed, Nov 17, 2004 at 11:57:41PM +0100, Emanuel Strobl wrote: > +> Dear best guys, > +> > +> I really love 5.3 in many ways but here're some unbelievable transfer rates, > +> after I went out and bought a pair of Intel GigaBit Ethernet Cards to solve > +> my performance problem (*laugh*): > [...] > > I done some test in the past with ggate and PCI64/GBit NICs and I get > ~38MB/s AFAIR. > > Remember that when using 32bit PCIs you can get transfer about > 500Mbit/s. > > Please run those test with netperf (/usr/ports/benchmarks/netperf) and > send results. Be aware, btw, that while netperf is a pretty decent tool, it performs a lot of socket select and timing operations, so isn't always a good measure of maximum capabilities of a system. I.e., it is not unusual to see that a netperf send test will only see send() as one in three or one in four system calls -- as a result, it uses a measurable amount of CPU on things other than sending. In an environment with CPU constraints (slower CPU or faster network), this can impact the performance results substantially. For example, when measuring maximum packet send performance using minimal packet sizes from user space, several of my test boxes are constrained with 64-bit gig-e PCI cards based on CPU. In particular, the combined cost of the additional system calls and operations cuts into available CPU for send. By eliminating the misc. overheads of netperf using netsend, I can improve performance by 20%-30%. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 12:49:05 2004 Return-Path: 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 4845016A4CE; Thu, 18 Nov 2004 12:49:05 +0000 (GMT) Received: from smtp-vbr15.xs4all.nl (smtp-vbr15.xs4all.nl [194.109.24.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 80A4F43D41; Thu, 18 Nov 2004 12:49:04 +0000 (GMT) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) iAICn27q065672; Thu, 18 Nov 2004 13:49:02 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.13.1/8.12.9) with ESMTP id iAICn2Pl075639; Thu, 18 Nov 2004 13:49:02 +0100 (CET) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.13.1/8.13.1/Submit) id iAICn2He075638; Thu, 18 Nov 2004 13:49:02 +0100 (CET) (envelope-from wb) Date: Thu, 18 Nov 2004 13:49:02 +0100 From: Wilko Bulte To: Robert Watson Message-ID: <20041118124902.GC75559@freebie.xs4all.nl> References: <200411172357.47735.Emanuel.Strobl@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="qjNfmADvan18RZcF" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 4.10-STABLE X-PGP: finger wilko@freebsd.org User-Agent: Mutt/1.5.6i X-Virus-Scanned: by XS4ALL Virus Scanner cc: Emanuel Strobl cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 12:49:05 -0000 --qjNfmADvan18RZcF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 18, 2004 at 12:27:44PM +0000, Robert Watson wrote.. >=20 > On Wed, 17 Nov 2004, Emanuel Strobl wrote: >=20 > > I really love 5.3 in many ways but here're some unbelievable transfer > > rates, after I went out and bought a pair of Intel GigaBit Ethernet > > Cards to solve my performance problem (*laugh*):=20 >=20 > I think the first thing you want to do is to try and determine whether the > problem is a link layer problem, network layer problem, or application > (file sharing) layer problem. Here's where I'd start looking: And you definitely want to look at polling(4) --=20 Wilko Bulte wilko@FreeBSD.org --qjNfmADvan18RZcF Content-Type: application/x-pkcs7-signature Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIIOfwYJKoZIhvcNAQcCoIIOcDCCDmwCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHAaCC C+swggSmMIICjqADAgECAgMAxq4wDQYJKoZIhvcNAQEEBQAweTEQMA4GA1UEChMHUm9vdCBD QTEeMBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNp Z25pbmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwHhcN MDQxMTA2MjI0MzE2WhcNMDUxMTA2MjI0MzE2WjAlMSMwIQYJKoZIhvcNAQkBFhR3YkBmcmVl YmllLnhzNGFsbC5ubDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANtHavP0Bn9g xcTO+rGscZxb/+LZcFdERZcV6d358KOHsrysbvvpElwbTgSL4QpviV9a5ju+3dze7YRi0iB7 3JzWbl1G29Q45nydX58eWX++w+RAFlHI0kAwTY612bIqhP+MmRon7W70lw45gQfUzGz/DqdR M/FRNNYhOVYp2wbp6f2ytEaierTv8p201+mLB4SjVJ1vQtu3oVfYZVZeJDoxYn49SrjVejuA yq/lDEO9ykNTp4l7rGJcK+FRAdag5Oi7Tev6cq5DzJiON74W9MR5aqvOLtYo/bh3zKXf5ygy sN8+hJnkAwlaAJ38SnsxKfpy3aFLUuZEn+Ul3oUcarkCAwEAAaOBijCBhzAMBgNVHRMBAf8E AjAAMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuQ0FjZXJ0Lm9yZzAfBgNVHREEGDAWgRR3YkBm cmVlYmllLnhzNGFsbC5ubDANBgkqhkiG9w0BAQQFAAOCAgEAlKQNnSd8Jdt58NFTEaY202Qb XEdESmsRBaydVid6K956unv0rtp3GhkegEJEjhSKoN0K0rIIoYeHgiArmZu2wtMoNvKJG7kN bXQ+R8uWJ5CLMbQ8HbEommF2ptrkR72GrXwOnDyjInEB/1lTtLjoBGmk7A+sTpvaB/gUpvRZ ydr7h8XhNwTcYdBEUXBeKkR7N+FzzSHfmYH288i65fmKQX91F/ewoaB627sDLKH/Vt/M8Z/I NcqyPlmGuFSKlR184PKWY78VaA8RtHSsQrr97eSRIa6MOWlvYQyq8fUfcPUfxl45qLlH8s2n FP0O7ZMAHhbypjnRWNg/r+HGsUqUh6EKFRdp70MmSSWYnM3ZzxGBIb9UV1n4+nPUCUx9r1fa DIAc/1LEvcjLSlW6vHus48VAOJelNGfMsdr8VlVafJE0F0nIXRiUdoe5sO45RKCSefqgRSW/ 7nLb7mvBg8u9q5+7VLuCsXEkpgc65dIIUD+2FTXpA2Zb0LSeey5zKC+RYdCYYvLAl9sQwx5E 6FMCkHOMDu5MEJLI0oyjrHjDbt/aE+fUQlJrFmfIUUX4CeQCdvFqrHDRjOT7JVSQB6EqA8VZ zBFLYUlTKdunvFcwR+2gJyHOTqLbM8b+Qb972jaBE6bGPWbK6t9PSdUsf2g1B9CpDSMiuWe7 Ek/XJFe6NY0wggc9MIIFJaADAgECAgEAMA0GCSqGSIb3DQEBBAUAMHkxEDAOBgNVBAoTB1Jv b3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEiMCAGA1UEAxMZQ0EgQ2Vy dCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJARYSc3VwcG9ydEBjYWNlcnQub3Jn MB4XDTAzMDMzMDEyMjk0OVoXDTMzMDMyOTEyMjk0OVoweTEQMA4GA1UEChMHUm9vdCBDQTEe MBwGA1UECxMVaHR0cDovL3d3dy5jYWNlcnQub3JnMSIwIAYDVQQDExlDQSBDZXJ0IFNpZ25p bmcgQXV0aG9yaXR5MSEwHwYJKoZIhvcNAQkBFhJzdXBwb3J0QGNhY2VydC5vcmcwggIiMA0G CSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDOIsDiRn3sNigHUJbyoDNAjEvxO2Y/MeVrAjbb 1nz28YiPTnc2BUGV+QnwEs9GhnNgt25+6MBYZK7NsK1FFwxj+mcK6NbSvz7nmMTwTPrgA7s1 XWwh3p4g2brNZjI3cvr3CPXHzVjJjucOXuo+/hyhFAoVbIaEW2RmKnqpS1N59Yiie+4vCmEr jbJ+TValE+zq2pKerERBHlhgZQVm+MBEvcuU90J+C/dlaJhRBfDzBZEEHRsXguzIV7vDa3qI 8bByzCVbIJHsFgISjzLpFxhI0McFLgIwQrglnAVrP6o6p+tTSPfo0rYHmNwbxjR/f8kcgnoF WCsIW/M4oqsXXWbJmNeeEIui0t10mvdxDHJg381vmDOdljR2PiR6krAOlR5v5qBFOEeq10Ht SrcS9tcbg4oPLtgJtlnXqgT/0pN9aC7di0urWLovjeqVp6DDVIml+9uLUSKdssO+Eb4skYaL lnitINOKLxo/xtBRZYchsRkBZX9FHIf1fNBBTE8pmCH9Mx91DARR+hl329QUHO6Bwx31mLdp BpEi3QBQzIExrBIHezjaaFvmK9R+yV+t6OtyTPMB5Usgv5qmV8qRAAGLoXUhN7VjDWc+Rk9w IGfOxdZZ2wLg8NLLzbpit5BB6N0g5Cm8ZClCyCLceJr/Q+yYGwlRS1pawnHxxMtzqeWhCwID AQABo4IBzjCCAcowHQYDVR0OBBYEFBa1MhvUx/Pg5o7zvdKwOu6yORjRMIGjBgNVHSMEgZsw gZiAFBa1MhvUx/Pg5o7zvdKwOu6yORjRoX2kezB5MRAwDgYDVQQKEwdSb290IENBMR4wHAYD VQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNBIENlcnQgU2lnbmluZyBB dXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0Lm9yZ4IBADAPBgNVHRMB Af8EBTADAQH/MDIGA1UdHwQrMCkwJ6AloCOGIWh0dHBzOi8vd3d3LmNhY2VydC5vcmcvcmV2 b2tlLmNybDAwBglghkgBhvhCAQQEIxYhaHR0cHM6Ly93d3cuY2FjZXJ0Lm9yZy9yZXZva2Uu Y3JsMDQGCWCGSAGG+EIBCAQnFiVodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lk PTEwMFYGCWCGSAGG+EIBDQRJFkdUbyBnZXQgeW91ciBvd24gY2VydGlmaWNhdGUgZm9yIEZS RUUgaGVhZCBvdmVyIHRvIGh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzANBgkqhkiG9w0BAQQFAAOC AgEAKMfunIICulyAEso1Ch2Bb4lqmczyaA9/p+GNWJU+vfIGw5BarLVg9plDAaOIcJydYp2k h69nWA0wNjvmrUjTy3QChnE+4isDaPE0YkBGO1PqKPSs+2aVU4pNXf072WDXynlpO7FlkqbG gYJcnM3rTQGKpd8RVaoVyh83wIKYcGHbanyWo44uVD5PIamQ79yCv9zoRa1NkHMIPJRlsASZ dn/ivMJqFaqXBDck2B6UTm0OUb7WxI/Klm33Q9/oMGUnO3u7Q0NjxEP3suxozOEZjiL7mOF7 Wj4BNzuLCLCi85VOGsubzZqx27Jw8C1K29iw429FSDMS//48MipU98T3ivCII8JH/mR6ccDR HqZjsAd+pC/TAY/cnyu2xgipD5NIJfwS/Z9C3PPEPvZXsNfdadEGdzQKS9LKoP8cxozJFr7E zDI3aHNfCPtR90lTNgUKlQJM8nkaEPbYOnWc8x3xog1wZ4Ybsxb1L+Wk63mG+T0LwnMLpZms b/xnuOUvC6YYJI170Ug1KRhArJNg4ZaGULR6WdiPIQufz4KRxju/a9wHkbmXViOqtmyUxkgG POTOTqrk9i8J3FNvLvx06zpjmcKmrIm8p7JEoA2KEONs8iTL+pufcEcu3hSL1LIgCZaiZPEk HNyhNZwVstS8VS59BvWcDlX0WtaT2natJXNMxUMxggJcMIICWAIBATCBgDB5MRAwDgYDVQQK EwdSb290IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNB IENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRAY2FjZXJ0 Lm9yZwIDAMauMAkGBSsOAwIaBQCggbEwGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkq hkiG9w0BCQUxDxcNMDQxMTE4MTI0OTAyWjAjBgkqhkiG9w0BCQQxFgQUxkKuY95Rid2mDd6G RW3cdc6ZF9cwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAw DQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAE ggEAaFF/wDpSIWER9cs/OwE3z6f9RXRs9AgpTelEmyDGlijauiRK6BMfH9YbCm+NiKfPrLlN PWE8XNc+xSPptao3a+zJC1578YfzCsYN4CwNZtBalsVXYMiZKxoyKQuGXJa7Hh53sxuFeaql Yd85yE8PF0bpLL1aJSw790hSxDJ9OK667rsKlREXJYv750waT5EPkbmP3RfApVpg6+PdIKaK z++3Or5YXXbbd1U7m6ZAP45OBAG+bUNYkichCjg/Smr17P4YnU8A0/hFaEx54NLqs01seRE5 8saxnYcOp+CjJq+H5rxJOTvidar5AM0ey8mXTg4Sn0dq2YnRY7khX0yORg== --qjNfmADvan18RZcF-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 12:54:55 2004 Return-Path: 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 0F00916A4CE for ; Thu, 18 Nov 2004 12:54:55 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9435B43D58 for ; Thu, 18 Nov 2004 12:54:54 +0000 (GMT) (envelope-from assadbsd@gmail.com) Received: by rproxy.gmail.com with SMTP id j1so464482rnf for ; Thu, 18 Nov 2004 04:54:53 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=gXKPcYCmWSQAcZ7dTn0BCfhkVqSzeEO+UC3wOtbKCJJ8qDdE8TilONcLF8S5h13waqmTytFfcy/CxGTuRjGzyw0I9T+soeKypCnnGE/Y93owBMSnTOTQI1F7fO0E8I0O0R3O7ejLIav+6+A1jn4ZpsSeqInUYD7XKlujr/HM1fA= Received: by 10.38.104.80 with SMTP id b80mr422369rnc; Thu, 18 Nov 2004 04:54:53 -0800 (PST) Received: by 10.38.75.13 with HTTP; Thu, 18 Nov 2004 04:54:53 -0800 (PST) Message-ID: Date: Thu, 18 Nov 2004 04:54:53 -0800 From: Maseed To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Maseed List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 12:54:55 -0000 Hi, I've been trying to install FreeBSD on my system that has an onboard Silicon Image sil3112a SATA controller and a Western Digital Raptor WD740 74GB HD, for a few months now, with no luck. First I tried 5.2.1, which installs fine but starts to spew DMA timeout messages when put under any kind of HD related stress and eventually the system becomes totally unusable. I tried a second time with 5.3-BETA7, the behaviour was exactly the same. I was just browsing freebsd-current archives after a google.com search and happened upon this e-mail: <--quoted e-mail begin--> To: current@freebsd.org Date: Tue, 30 Sep 2003 22:06:40 +0200 (CEST) I have now found a way to reproduce the DMA problems some setups seems to be having with the SiI3112A SATA chip. Now, if I use real SATA drives, (and I mean real SATA drives, the WD Raptor fx is not a real SATA device but just a PATA device with a build in PATA->SATA converter chip) it works just fine no matter what I try. If however I use an older PATA drive and a certain PATA->SATA "dongle" (in this case 1 out of 4 samples) I can reproduce the problem pretty easily. This suggests to me that we are looking at a timing problem of sorts the question is where. I'll work on the problem as time permits... -S=F8ren=20 <--quoted e-mail end--> I have to point out in the above e-mail that the problem is not just confined to the 36GB Raptor, which might be a PATA drive with a Marvel chip to make it work with SATA drives, but it also plagues *real* native SATA drives as well, since the 74GB Western Digital Raptor I have is a true SATA150 drive with TCQ. Anyhow, I am wondering if this issue has been resolved yet or not, either in FreeBSD-current or 5.3-RELEASE-px. I don't want to discard my current OS to install FreeBSD only to find out that the problem is still there. If any sort of error logs or dmesg output is required by a potential developer from this setup of mine, I'll go so far as to resize my partition and install FreeBSD 5.3 and provide them, but the reason why I'm hesitant in doing that is the fact that I run a web-server on my computer that cannot stay down for long, as some friends of mine depend on it. Any feedback will be highly appreciated. Thank You, -Assad From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 13:02:13 2004 Return-Path: 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 0C5FE16A4CE; Thu, 18 Nov 2004 13:02:13 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6821F43D58; Thu, 18 Nov 2004 13:02:12 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAID0dGC069640; Thu, 18 Nov 2004 08:00:39 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAID0cLp069637; Thu, 18 Nov 2004 13:00:38 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 18 Nov 2004 13:00:38 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Wilko Bulte In-Reply-To: <20041118124902.GC75559@freebie.xs4all.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Emanuel Strobl cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 13:02:13 -0000 On Thu, 18 Nov 2004, Wilko Bulte wrote: > On Thu, Nov 18, 2004 at 12:27:44PM +0000, Robert Watson wrote.. > > > > On Wed, 17 Nov 2004, Emanuel Strobl wrote: > > > > > I really love 5.3 in many ways but here're some unbelievable transfer > > > rates, after I went out and bought a pair of Intel GigaBit Ethernet > > > Cards to solve my performance problem (*laugh*): > > > > I think the first thing you want to do is to try and determine whether the > > problem is a link layer problem, network layer problem, or application > > (file sharing) layer problem. Here's where I'd start looking: > > And you definitely want to look at polling(4) He did, but he set the HZ at 256, which is sufficiently low as to guarantee a substantial increase in latency, and likely guarantee interface and socket queue overruns (although I haven't done the math to verify that is the case). Between the very finite sizes of ifnet send queues, socket buffers, and if_em descriptors, and on-board buffers on the card, high latency polling can result in lots of packet loss and delay under load. Hence the recommendation of a relatively high value of HZ so that the queues in the driver are drained regularly, and sends acknowledged so that the sent mbufs can be reclaimed and reused. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Wed Nov 17 19:07:24 2004 Return-Path: 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 6F34416A525 for ; Wed, 17 Nov 2004 19:07:23 +0000 (GMT) Received: from out003.verizon.net (out003pub.verizon.net [206.46.170.103]) by mx1.FreeBSD.org (Postfix) with ESMTP id E261443D48 for ; Wed, 17 Nov 2004 19:07:22 +0000 (GMT) (envelope-from Mikhail.Teterin@murex.com) Received: from corbulon.video-collage.com ([151.204.231.237]) by out003.verizon.netESMTP <20041117190722.RPUV3485.out003.verizon.net@corbulon.video-collage.com> for ; Wed, 17 Nov 2004 13:07:22 -0600 Received: from 250-217.customer.cloud9.net (195-11.customer.cloud9.net [168.100.195.11])iAHJ7Hh1034327 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Wed, 17 Nov 2004 14:07:18 -0500 (EST) (envelope-from Mikhail.Teterin@murex.com) Received: from 250-217.customer.cloud9.net (mteterin@localhost [127.0.0.1]) iAHJ7CiA001273 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 17 Nov 2004 14:07:12 -0500 (EST) (envelope-from Mikhail.Teterin@murex.com) Received: from localhost (localhost [[UNIX: localhost]]) iAHJ7BF4001272 for freebsd-current@freebsd.org; Wed, 17 Nov 2004 14:07:11 -0500 (EST) (envelope-from Mikhail.Teterin@murex.com) X-Authentication-Warning: mteterin.us.murex.com: mteterin set sender to Mikhail.Teterin@murex.com using -f From: Mikhail Teterin Organization: Murex North America To: freebsd-current@freebsd.org User-Agent: KMail/1.7.1 MIME-Version: 1.0 Content-Disposition: inline X-UID: 6291 X-Length: 1249 Date: Wed, 17 Nov 2004 14:07:11 -0500 Content-Type: Multipart/Mixed; boundary="Boundary-00=_fF6mByMcCkZoh78" Message-Id: <200411171407.11793.Mikhail.Teterin@murex.com> X-Virus-Scanned: clamd / ClamAV version devel-20040615, clamav-milter version 0.73a on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 X-Authentication-Info: Submitted using SMTP AUTH at out003.verizon.net from [151.204.231.237] at Wed, 17 Nov 2004 13:07:19 -0600 X-Mailman-Approved-At: Thu, 18 Nov 2004 13:20:40 +0000 X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: open(), mmap(), sendfile() vs. the file's access time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 19:07:24 -0000 --Boundary-00=_fF6mByMcCkZoh78 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Hello! It appears, only read() modifies a file's atime. Otherwise, a file can be open()-ed and subsequently _accessed_ through mmap or sendfile()-ed away without atime being changed. Does not seem right... Should open() update atime? My first reaction would be yes, but on Linux and Solaris the behaviour is the same (try attached program). Should sendfile()? What about mmap() -- there are some hairy usages?.. All I'm trying to do is track the last time a file was downloaded from the web-server. But Apache uses sendfile() (zero copy and what not) and thus no luck :-( Thanks! Yours, -mi --Boundary-00=_fF6mByMcCkZoh78-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 00:36:50 2004 Return-Path: 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 244CA16A4CE; Thu, 18 Nov 2004 00:36:50 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id B91F843D31; Thu, 18 Nov 2004 00:36:49 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI0Y91v059494; Wed, 17 Nov 2004 17:34:10 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 17:34:09 -0700 (MST) Message-Id: <20041117.173409.104092741.imp@harmony.village.org> To: oberman@es.net From: Warner Losh In-Reply-To: <20041117211943.E583E5D0A@ptavv.es.net> References: <419BB117.4070802@root.org> <20041117211943.E583E5D0A@ptavv.es.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 18 Nov 2004 13:20:40 +0000 cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk cc: nate@root.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 00:36:50 -0000 > I do suspect that this is a PCI power issue and not an ACPI issue, but > I'd like to know if it shows up on more models. It is most obvious when > playing a stream as the buffers keep emptying and the sound stops after > a short time. Music is clearly too fast and high pitched, but at 10% > overspeed, some may not notice. (Does Dr. Dre sound much different 10% > faster?) I've flipped the sense of the PCI power sysctl in current. Once that's sanner, we should investigate setting the power states on resume. Not sure what to do about suspend, since I think that acpi has different notions of what D level to put a device in for different S levels and it would likely have to take care of that after giving the device a chance to save state. Warner From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 03:27:43 2004 Return-Path: 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 0E88C16A4CE; Thu, 18 Nov 2004 03:27:43 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id A087843D31; Thu, 18 Nov 2004 03:27:42 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI3PMsx060941; Wed, 17 Nov 2004 20:25:22 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 20:25:21 -0700 (MST) Message-Id: <20041117.202521.74694027.imp@harmony.village.org> To: nate@root.org From: Warner Losh In-Reply-To: <419C00A7.7030300@root.org> References: <20041117211943.E583E5D0A@ptavv.es.net> <20041117.173409.104092741.imp@harmony.village.org> <419C00A7.7030300@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 18 Nov 2004 13:20:40 +0000 cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:27:43 -0000 From: Nate Lawson Subject: Re: [PATCH] Please test: new ACPI release (20041105) import Date: Wed, 17 Nov 2004 17:53:43 -0800 > Warner Losh wrote: > >>I do suspect that this is a PCI power issue and not an ACPI issue, but > >>I'd like to know if it shows up on more models. It is most obvious when > >>playing a stream as the buffers keep emptying and the sound stops after > >>a short time. Music is clearly too fast and high pitched, but at 10% > >>overspeed, some may not notice. (Does Dr. Dre sound much different 10% > >>faster?) > > > > I've flipped the sense of the PCI power sysctl in current. Once > > that's sanner, we should investigate setting the power states on > > resume. Not sure what to do about suspend, since I think that acpi > > has different notions of what D level to put a device in for different > > S levels and it would likely have to take care of that after giving > > the device a chance to save state. > > > > Warner > > I have a patch in my tree to do this. I'll post it once it's > well-tested. At the moment, setting UART to D3 appears to hang the > system and I'm not sure why. What do you mean 'UART'? I'm confused... Warner From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 03:48:38 2004 Return-Path: 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 0677416A4CE; Thu, 18 Nov 2004 03:48:38 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 542DD43D2D; Thu, 18 Nov 2004 03:48:36 +0000 (GMT) (envelope-from imp@harmony.village.org) Received: from localhost (localhost [IPv6:::1]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAI3m494061144; Wed, 17 Nov 2004 20:48:04 -0700 (MST) (envelope-from imp@harmony.village.org) Date: Wed, 17 Nov 2004 20:48:04 -0700 (MST) Message-Id: <20041117.204804.71148446.imp@harmony.village.org> To: nate@root.org From: Warner Losh In-Reply-To: <419C1A7A.6050000@root.org> References: <419C00A7.7030300@root.org> <20041117.202521.74694027.imp@harmony.village.org> <419C1A7A.6050000@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 18 Nov 2004 13:20:40 +0000 cc: imp@rover.village.org cc: freebsd-acpi@FreeBSD.org cc: freebsd-current@FreeBSD.org cc: sos@DeepCore.dk Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 03:48:38 -0000 > My serial port. It's named UART in the AML, that's all. Setting it to > D3 hangs the system. Is it a PCI device too? If not, then maybe you need to disable interrupts in the UART before setting the power state. Chances are its interrupt cause register is returning 0xff, which hangs sio, since it never breaks out of the loop when this happens. Warner From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 13:23:23 2004 Return-Path: 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 9972F16A4CE for ; Thu, 18 Nov 2004 13:23:23 +0000 (GMT) Received: from mail.bonivet.net (mail.bonivet.net [81.56.185.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96DC343D46 for ; Thu, 18 Nov 2004 13:23:22 +0000 (GMT) (envelope-from gstewart@bonivet.net) X-ConnectingHost: 192.168.1.254 Received: from dragonfly.bonivet.net (dragonfly.bonivet.net [192.168.1.254]) by mail.bonivet.net (8.13.1/8.13.1) with SMTP id iAIDNJUZ011988 for ; Thu, 18 Nov 2004 14:23:19 +0100 Date: Thu, 18 Nov 2004 14:23:19 +0100 From: Godwin Stewart To: freebsd-current@freebsd.org Message-Id: <20041118142319.7fcb88d9.gstewart@bonivet.net> In-Reply-To: <200411171407.11793.Mikhail.Teterin@murex.com> References: <200411171407.11793.Mikhail.Teterin@murex.com> Organization: Nope, none here, it's a mess ;o) X-Mailer: Sylpheed version 1.0.0beta3 (GTK+ 1.2.10; i386-unknown-freebsd5.3) X-MS-SUX: As if we didn't know... X-Curious: You just *HAD* to look at these headers, didn't you! X-Face: #T;eJks=B[`71qrwp`l6BW8xI&hP8S*4Kd%e?8o"rL02ZYf"rWa41l83a)L,*; S).Ukq$U% II{-z#5%i&X8"%{$)ZWmE7WBDF)?wK1^7]u9T;@jqdZo?IT!d-L`!@&vW)F_1 Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: open(), mmap(), sendfile() vs. the file's access time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 13:23:23 -0000 On Wed, 17 Nov 2004 14:07:11 -0500, Mikhail Teterin wrote: > All I'm trying to do is track the last time a file was downloaded from the > web-server. Aren't apache's logs any good for that? -- The item you had your eye on the minute you walked in will be taken by the person in front of you. From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 13:41:13 2004 Return-Path: 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 3D09016A4CE for ; Thu, 18 Nov 2004 13:41:13 +0000 (GMT) Received: from maxlor.mine.nu (c-213-160-32-54.customer.ggaweb.ch [213.160.32.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id B24FA43D3F for ; Thu, 18 Nov 2004 13:41:12 +0000 (GMT) (envelope-from benlutz@datacomm.ch) Received: from localhost (localhost [127.0.0.1]) by maxlor.mine.nu (Postfix) with ESMTP id 2EF841EC for ; Thu, 18 Nov 2004 14:41:11 +0100 (CET) Received: from maxlor.mine.nu ([127.0.0.1]) by localhost (midgard [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 80452-10 for ; Thu, 18 Nov 2004 14:41:10 +0100 (CET) Received: from merlin.intranet (merlin.intranet [10.0.0.16]) by maxlor.mine.nu (Postfix) with ESMTP id E7E5D94 for ; Thu, 18 Nov 2004 14:41:09 +0100 (CET) From: Benjamin Lutz To: freebsd-current@freebsd.org Date: Thu, 18 Nov 2004 14:41:03 +0100 User-Agent: KMail/1.7.1 References: <200411091747.iA9Hl81Q075289@marlena.vvi.at> <200411151429.56336.jhb@FreeBSD.org> In-Reply-To: <200411151429.56336.jhb@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2009823.ARQ185g4PL"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411181441.09471.benlutz@datacomm.ch> X-Virus-Scanned: by amavisd-new at maxlor.mine.nu Subject: Re: FreeBSD 5.3-RELEASE boot failure X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 13:41:13 -0000 --nextPart2009823.ARQ185g4PL Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 15 November 2004 20:29, John Baldwin wrote: > On Tuesday 09 November 2004 12:47 pm, ALeine wrote: > > I installed FreeBSD 5.3-RELEASE from the ISO CD image, but it won't > > boot: > > > > F1 DOS > > F2 Linux > > F3 FreeBSD > > > > Default: F3 > > > > _ > > int=3D00000006 err=3D00000000 efl=3D00000282 eip=3D000947cf > > eax=3D000000c1 ebx=3D0000273b ecx=3Dfe510821 edx=3D00000000 > > esi=3D00000006 edi=3D00098db6 ebp=3D00090000 esp=3D00000000 > > cs=3D002b ds=3D0033 es=3D0033 fs=3D0033 gs=3D0033 ss=3D0033 > > cs:eip=3Df0 2b 92 00 00 00 00 bc-89 00 00 af f1 e6 f8 00 > > 00 00 00 00 00 00 00 00-00 54 3d 00 00 00 00 00 > > ss:esp=3D2b 00 00 01 1b f6 13 50-08 19 f6 f4 f7 f3 c3 f9 > > 6f 91 6c 2c f8 ef 0d 6c-10 f2 7b 77 08 59 2e f9 > > BTX halted > > > > This was with the HDD as ad0. I changed it to ad2 and used my > > other drive with FreeBSD 4.10 as ad0 to see what was going on. > > Here's the beef: > > Your BIOS is in lala land perhaps. Note that the stack pointer is 0, > so it's hard to tell how it got into such a funk. I'm not sure how you > can debug this, except perhaps to try turning off things like network > cards as boot devices and turning off DMA mode in the BIOS for your > hard drives. I got an error like this when I accidentally tried to use FreeBSD/amd64 on= =20 an i386-only machine. Maybe the BIOS is broken, but the chance that using vmware instead of his=20 native hardware would produce the same error is low, isn't it? Benjamin --nextPart2009823.ARQ185g4PL Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnKZ1gShs4qbRdeQRAsEKAJsE4aPEWKLslKHqagnSgjAuWL5JEwCfcw43 M/OYQT/+6TIZ8jl54YaNpMM= =+9bd -----END PGP SIGNATURE----- --nextPart2009823.ARQ185g4PL-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 13:45:44 2004 Return-Path: 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 403C716A4CE for ; Thu, 18 Nov 2004 13:45:44 +0000 (GMT) Received: from av6-1-sn2.hy.skanova.net (av6-1-sn2.hy.skanova.net [81.228.8.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id F18E143D1D for ; Thu, 18 Nov 2004 13:45:42 +0000 (GMT) (envelope-from ertr1013@student.uu.se) Received: by av6-1-sn2.hy.skanova.net (Postfix, from userid 502) id 9A6F437E45; Thu, 18 Nov 2004 14:45:41 +0100 (CET) Received: from smtp2-1-sn2.hy.skanova.net (smtp2-1-sn2.hy.skanova.net [81.228.8.177]) by av6-1-sn2.hy.skanova.net (Postfix) with ESMTP id 84F2C37E43 for ; Thu, 18 Nov 2004 14:45:41 +0100 (CET) Received: from falcon.midgard.homeip.net (h201n1fls24o1048.bredband.comhem.se [212.181.162.201]) by smtp2-1-sn2.hy.skanova.net (Postfix) with SMTP id 3B28E37E43 for ; Thu, 18 Nov 2004 14:45:41 +0100 (CET) Received: (qmail 26645 invoked by uid 1001); 18 Nov 2004 13:45:40 -0000 Date: Thu, 18 Nov 2004 14:45:40 +0100 From: Erik Trulsson To: Mikhail Teterin Message-ID: <20041118134539.GA26538@falcon.midgard.homeip.net> Mail-Followup-To: Mikhail Teterin , freebsd-current@freebsd.org References: <200411171407.11793.Mikhail.Teterin@murex.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411171407.11793.Mikhail.Teterin@murex.com> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: open(), mmap(), sendfile() vs. the file's access time X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 13:45:44 -0000 On Wed, Nov 17, 2004 at 02:07:11PM -0500, Mikhail Teterin wrote: > Hello! > > It appears, only read() modifies a file's atime. Otherwise, a file can be > open()-ed and subsequently _accessed_ through mmap or sendfile()-ed away > without atime being changed. Does not seem right... > > Should open() update atime? My first reaction would be yes, but on Linux and > Solaris the behaviour is the same (try attached program). > > Should sendfile()? What about mmap() -- there are some hairy usages?.. I don't know if the current behaviour is "right", but it is certainly consistent with the documentation. From the manpage for stat(2): The time-related fields of struct stat are as follows: st_atime Time when file data last accessed. Changed by the mknod(2), utimes(2) and read(2) system calls. st_mtime Time when file data last modified. Changed by the mknod(2), utimes(2) and write(2) system calls. st_ctime Time when file status was last changed (inode data modification). Changed by the chmod(2), chown(2), link(2), mknod(2), rename(2), unlink(2), utimes(2) and write(2) system calls. The Solaris stat(2) manpage says: st_atime Time when file data was last accessed. Changed by the following functions: creat(), mknod(), pipe(), utime(2), and read(2). st_mtime Time when data was last modified. Changed by the fol- lowing functions: creat(), mknod(), pipe(), utime(), and write(2). st_ctime Time when file status was last changed. Changed by the following functions: chmod(), chown(), creat(), link(2), mknod(), pipe(), unlink(2), utime(), and write(). And on Linux stat(2) says: The field st_atime is changed by file accesses, e.g. by execve(2), mknod(2), pipe(2), utime(2) and read(2) (of more than zero bytes). Other routines, like mmap(2), may or may not update st_atime. The field st_mtime is changed by file modifications, e.g. by mknod(2), truncate(2), utime(2) and write(2) (of more than zero bytes). Moreover, st_mtime of a directory is changed by the creation or deletion of files in that directory. The st_mtime field is not changed for changes in owner, group, hard link count, or mode. The field st_ctime is changed by writing or by setting inode information (i.e., owner, group, link count, mode, etc.). It seems that one should definitely not depend on atime being changed by mmap() or sendfile(). -- Erik Trulsson ertr1013@student.uu.se From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:02:37 2004 Return-Path: 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 4170F16A4CE for ; Thu, 18 Nov 2004 16:02:37 +0000 (GMT) Received: from lakermmtao04.cox.net (lakermmtao04.cox.net [68.230.240.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id A073643D46 for ; Thu, 18 Nov 2004 16:02:36 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao04.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041118160233.LTFF4706.lakermmtao04.cox.net@dolphin.local.net>; Thu, 18 Nov 2004 11:02:33 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAIG2Ue5019252; Thu, 18 Nov 2004 10:02:34 -0600 (CST) (envelope-from conrads@cox.net) Date: Thu, 18 Nov 2004 10:02:24 -0600 From: "Conrad J. Sabatier" To: Sean McNeil Message-ID: <20041118100224.2428c9d9@dolphin.local.net> In-Reply-To: <1100556108.3025.1.camel@server.mcneil.com> References: <1100556108.3025.1.camel@server.mcneil.com> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: natd panics are back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:02:37 -0000 On Mon, 15 Nov 2004 14:01:48 -0800, Sean McNeil wrote: > This was fixed a while ago and now it has made its way back into > current: > > server# uname -a > FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #58: Mon Nov > 15 08:40:01 PST 2004 > root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 > > Nov 15 13:56:16 server kernel: Fatal trap 12: page fault while in > kernel mode Nov 15 13:56:16 server kernel: fault virtual address = > 0x18 Nov 15 13:56:16 server kernel: fault code = > supervisor read, page not present > Nov 15 13:56:16 server kernel: instruction pointer = > 0x8:0xffffffff80354810Nov 15 13:56:16 server kernel: stack pointer > = 0x10:0xffffffffb1c71620 > Nov 15 13:56:16 server kernel: frame pointer = > 0x10:0xffffffffb1c71680 Nov 15 13:56:16 server kernel: code segment > = base 0x0, limit 0xfffff, type 0x1b > Nov 15 13:56:16 server kernel: = DPL 0, pres 1, long 1, def32 0, gran > 1 Nov 15 13:56:16 server kernel: processor eflags = interrupt enabled, > resume, IOPL = 0 Nov 15 13:56:16 server kernel: current process > = 212 (natd) > Nov 15 13:56:16 server kernel: trap number = 12 > Nov 15 13:56:16 server kernel: panic: page fault > Nov 15 13:56:16 server kernel: KDB: enter: panic > > > (gdb) l *0xffffffff80354810 > 0xffffffff80354810 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). > 368 MBUF_CHECKSLEEP(wait); > 369 if (off == 0 && m->m_flags & M_PKTHDR) > 370 copyhdr = 1; > 371 while (off > 0) { > 372 KASSERT(m != NULL, ("m_copym, offset > size of > mbuf chain")); 373 if (off < m->m_len) > 374 break; > 375 off -= m->m_len; > 376 m = m->m_next; > 377 } Are you still having this problem? I went a few days without upgrading, then cvsupped and built a new world/kernel yesterday. No panic on boot with natd. This is on my amd64 box. Haven't upgraded my i386 box yet. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:14:03 2004 Return-Path: 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 840D716A4CE for ; Thu, 18 Nov 2004 16:14:03 +0000 (GMT) Received: from lakermmtao12.cox.net (lakermmtao12.cox.net [68.230.240.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B48C43D39 for ; Thu, 18 Nov 2004 16:14:03 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao12.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP id <20041118161402.KGND8344.lakermmtao12.cox.net@dolphin.local.net> for ; Thu, 18 Nov 2004 11:14:02 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAIGE1xu019400 for ; Thu, 18 Nov 2004 10:14:01 -0600 (CST) (envelope-from conrads@cox.net) Date: Thu, 18 Nov 2004 10:13:56 -0600 From: "Conrad J. Sabatier" To: freebsd-current@freebsd.org Message-ID: <20041118101356.53ed3f78@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:14:03 -0000 Noticed this during a cvs update today: dolphin:root:/usr/src/usr.bin# cvs -R update ? lex/lib/.depend ? lex/lib/libln.a ? lex/lib/libmain.o ? lex/lib/libyywrap.o I'm assuming, of course, that this is *not* the desired behavior. -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:15:48 2004 Return-Path: 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 EFB8A16A4CE; Thu, 18 Nov 2004 16:15:48 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40C9043D58; Thu, 18 Nov 2004 16:15:48 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAIGD6cb070490; Thu, 18 Nov 2004 09:13:06 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 18 Nov 2004 09:13:32 -0700 (MST) Message-Id: <20041118.091332.71089191.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <419C3AC2.5010505@root.org> References: <419C1A7A.6050000@root.org> <20041117.204804.71148446.imp@harmony.village.org> <419C3AC2.5010505@root.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-acpi@freebsd.org cc: freebsd-current@freebsd.org Subject: Re: [PATCH] Please test: new ACPI release (20041105) import X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:15:49 -0000 In message: <419C3AC2.5010505@root.org> Nate Lawson writes: : Warner Losh wrote: : >>My serial port. It's named UART in the AML, that's all. Setting it to : >>D3 hangs the system. : > : > Is it a PCI device too? If not, then maybe you need to disable : > interrupts in the UART before setting the power state. Chances are : > its interrupt cause register is returning 0xff, which hangs sio, since : > it never breaks out of the loop when this happens. : : It is not, it's a legacy device: : sio0 pnpinfo _HID=PNP0501 _UID=0 at handle=\_SB_.PCI0.LPC_.UART : : The power methods for it are: : Method (_PS0, 0, NotSerialized) : { : Store (0x03, LDN) : Store (0x01, LDA) : Store (0x01, SSBY) : } : : Method (_PS3, 0, NotSerialized) : { : Store (0x03, LDN) : Store (0x00, LDA) : Store (0x00, SSBY) : } : : The regions accessed by these Store ops are as follows, and all appear : to be mapped to the ICH: : OperationRegion (IMGA, SystemIO, 0x15E0, 0x10) : OperationRegion (NCFG, SystemIO, 0x2E, 0x02) : : Is there a standard for how to do power transitions for non-PCI devices? : I thought you just call the acpi methods if present. There might be some driver stuff that will need to be done on top of the calling these things. I don't know what the behavior of the device is, but many pci devices read 0xffffffff when in d3 mode. Warner From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:39:46 2004 Return-Path: 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 CDE9316A4CE for ; Thu, 18 Nov 2004 16:39:46 +0000 (GMT) Received: from lakermmtao03.cox.net (lakermmtao03.cox.net [68.230.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D2B443D48 for ; Thu, 18 Nov 2004 16:39:46 +0000 (GMT) (envelope-from conrads@cox.net) Received: from dolphin.local.net ([68.11.30.24]) by lakermmtao03.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with ESMTP <20041118163945.MUUD14730.lakermmtao03.cox.net@dolphin.local.net>; Thu, 18 Nov 2004 11:39:45 -0500 Received: from dolphin.local.net (localhost.local.net [127.0.0.1]) by dolphin.local.net (8.13.1/8.13.1) with SMTP id iAIGdjCJ026947; Thu, 18 Nov 2004 10:39:45 -0600 (CST) (envelope-from conrads@cox.net) Date: Thu, 18 Nov 2004 10:39:40 -0600 From: "Conrad J. Sabatier" To: "Conrad J. Sabatier" Message-ID: <20041118103940.7f2309bd@dolphin.local.net> In-Reply-To: <20041118101356.53ed3f78@dolphin.local.net> References: <20041118101356.53ed3f78@dolphin.local.net> X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; amd64-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:39:46 -0000 On Thu, 18 Nov 2004 10:13:56 -0600, "Conrad J. Sabatier" wrote: > > Noticed this during a cvs update today: > > dolphin:root:/usr/src/usr.bin# cvs -R update > ? lex/lib/.depend > ? lex/lib/libln.a > ? lex/lib/libmain.o > ? lex/lib/libyywrap.o > > I'm assuming, of course, that this is *not* the desired behavior. Hmmm, also seeing this now: ? usr.sbin/pcvt/keycap/.depend ? usr.sbin/pcvt/keycap/keycap.o ? usr.sbin/pcvt/keycap/libkeycap.a -- Conrad J. Sabatier -- "In Unix veritas" From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:39:55 2004 Return-Path: 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 6454316A4DE for ; Thu, 18 Nov 2004 16:39:55 +0000 (GMT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3EA243D39 for ; Thu, 18 Nov 2004 16:39:54 +0000 (GMT) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 712361CF; Thu, 18 Nov 2004 10:39:54 -0600 (CST) Date: Thu, 18 Nov 2004 10:39:54 -0600 From: Tillman Hodgson To: current@freebsd.org Message-ID: <20041118163954.GA76234@seekingfire.com> References: <20041117180157.GO76234@seekingfire.com> <20041117181108.GA24426@ack.Berkeley.EDU> <20041117225735.GA2148@gothmog.gr> <04111807243512.21298@www.mmlab.cse.yzu.edu.tw> <20041118030306.GA59867@neo.redjade.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041118030306.GA59867@neo.redjade.org> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/personal/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers X-Tillman-rules: yes he does User-Agent: Mutt/1.5.6i Subject: Re: `kldload` doesn't find pf.ko, though `ls` finds it easily enough X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:39:55 -0000 On Thu, Nov 18, 2004 at 12:03:06PM +0900, Sangwoo Shim wrote: > On Thu, Nov 18, 2004 at 07:25:58AM +0800, Tai-hwa Liang wrote: > > On Thu, 18 Nov 2004, Giorgos Keramidas wrote: > > >On 2004-11-17 13:31, Tillman Hodgson wrote: > > [...] > > >>Nov 17 11:54:41 thoth kernel: link_elf: symbol in6_cksum undefined > > >>Nov 17 11:54:41 thoth toor: /etc/rc.d/pf: ERROR: pf module failed to load. > > >> > > >>My custom kernel doesn't include IPv6. Does pf truly require IPv6?: > > > > > >Yes, if you want to load it as a module. This is exactly the same thing > > >I bumped into last night. Compiling a kernel with INET6 support will > > >let you load pf as a module. > > > > Does define "NOINET6=yes" in your /etc/make.conf and rebuild the kernel > > work for you? > > I think that should work. And to save him from compiling entire kernel, > Just compiling (and installing) pf module by doing "make NOINET6=yes" in > /sys/modules/pf will also work. :-) I tried this, and it work beautifully, thanks! Thanks also to Giorgos and Ruslan for providing more background on the problem. I always appreciate understanding a problem -- often more than getting the problem fixed ;-) -T -- As long as your email program is sending mine ASCII text through an SMTP server [..] we're pretty much covered. (Some people believe in throwing in HTML support, which is a bit like using colored paper and glitter ink to improve your resume, but it takes all kinds.) -- Rob Landley, linuxandmain.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:43:59 2004 Return-Path: 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 0DB3016A4CE for ; Thu, 18 Nov 2004 16:43:59 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 359D343D5C for ; Thu, 18 Nov 2004 16:43:58 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iAIGhuAU012471 for ; Thu, 18 Nov 2004 18:43:56 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iAIGhuS3046268 for ; Thu, 18 Nov 2004 18:43:56 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)iAIGhurH046267 for freebsd-current@freebsd.org; Thu, 18 Nov 2004 18:43:56 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 18 Nov 2004 18:43:56 +0200 From: Giorgos Keramidas To: freebsd-current@freebsd.org Message-ID: <20041118164356.GA46185@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:43:59 -0000 The screen-4.0.2 version that misc/screen installs is apparently the latest version of screen available. It also contains a zillion bugs, is written in a very insecure style, it uses an antiquated version of autoconf script, etc. I'm in the process of fixing some of these bugs, and mailing them back to the screen maintainers (if they still work on screen at all, that is). This post is just the description of a workaround for a recent breakage I noticed. When screen runs under xterm/X11 in recent FreeBSD 6.0-CURRENT versions, resizing the containing xterm results in an immediate panic with: BLOCK fcntl This is apparently the result of the following code from screen/socket.c: 793 #ifdef NAMEDPIPE 794 debug("Ha, there was someone knocking on my fifo??\n"); 795 if (fcntl(ServerSocket, F_SETFL, 0) == -1) 796 Panic(errno, "BLOCK fcntl"); 797 #else 798 struct sockaddr_un a; 799 800 len = sizeof(a); 801 debug("Ha, there was someone knocking on my socket??\n"); 802 if ((ns = accept(ns, (struct sockaddr *) &a, &len)) < 0) 803 { 804 Msg(errno, "accept"); 805 return; 806 } 807 #endif /* NAMEDPIPE */ At line 795, screen attempts to set blocking mode on a FIFO and fails. I've added the following patch in my local ports tree and tested screen(1) with (effectively forced) UNIX domain sockets instead of FIFOs: % --- config.h.in.orig Thu Nov 18 18:14:02 2004 % +++ config.h.in Thu Nov 18 18:14:12 2004 % @@ -526,11 +526,6 @@ % #undef SELECT_BROKEN % % /* % - * Define this if your system supports named pipes. % - */ % -#undef NAMEDPIPE % - % -/* % * Define this if your system exits select() immediatly if a pipe is % * opened read-only and no writer has opened it. % */ This seems to have solved the crashes I was seeing. But is this correct? Is fcntl() really supposed to fail on FIFOs or is this a FreeBSD bug? - Giorgos From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:47:04 2004 Return-Path: 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 ABC7C16A4CE; Thu, 18 Nov 2004 16:47:04 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3D9B43D55; Thu, 18 Nov 2004 16:47:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAIGl1wg051653; Thu, 18 Nov 2004 17:47:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Giorgos Keramidas From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 18 Nov 2004 18:43:56 +0200." <20041118164356.GA46185@orion.daedalusnetworks.priv> Date: Thu, 18 Nov 2004 17:47:01 +0100 Message-ID: <51652.1100796421@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:47:04 -0000 In message <20041118164356.GA46185@orion.daedalusnetworks.priv>, Giorgos Kerami das writes: > BLOCK fcntl > >This is apparently the result of the following code from screen/socket.c: > > 793 #ifdef NAMEDPIPE > 794 debug("Ha, there was someone knocking on my fifo??\n"); > 795 if (fcntl(ServerSocket, F_SETFL, 0) == -1) > 796 Panic(errno, "BLOCK fcntl"); > 797 #else > >At line 795, screen attempts to set blocking mode on a FIFO and fails. Can you get me the exact errno value ? -- 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 Thu Nov 18 16:49:19 2004 Return-Path: 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 2FEA216A4CE for ; Thu, 18 Nov 2004 16:49:19 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id C09F143D4C for ; Thu, 18 Nov 2004 16:49:18 +0000 (GMT) (envelope-from leafy7382@gmail.com) Received: by rproxy.gmail.com with SMTP id 34so43308rns for ; Thu, 18 Nov 2004 08:49:13 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=a5p4tOowZQ6zHkTikGAWzqTGs2iiEFEpsEhuM24OQL2GV9+ACYVmxefeydLK9Mx9UCJL+eZkwzo0Sm9ztFvSNu0td1zePa02BNbwk1/WJ3bkADUaMKuT4WVmmtKv4lvbiMVOfN7sRgkHO0FLkz+0EU8g9qn7gU9QkLwJdgMeCY4= Received: by 10.38.179.4 with SMTP id b4mr238127rnf; Thu, 18 Nov 2004 08:49:12 -0800 (PST) Received: by 10.38.8.55 with HTTP; Thu, 18 Nov 2004 08:49:12 -0800 (PST) Message-ID: Date: Fri, 19 Nov 2004 00:49:12 +0800 From: Jiawei Ye To: Giorgos Keramidas In-Reply-To: <20041118164356.GA46185@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <20041118164356.GA46185@orion.daedalusnetworks.priv> cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Jiawei Ye List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:49:19 -0000 On Thu, 18 Nov 2004 18:43:56 +0200, Giorgos Keramidas wrote: > When screen runs under xterm/X11 in recent FreeBSD 6.0-CURRENT versions, > resizing the containing xterm results in an immediate panic with: > > BLOCK fcntl > > This is apparently the result of the following code from screen/socket.c: Me, too (TM) Also, postfix reports a "postfix/master[546]: fatal: fcntl: set non-blocking flag on: Inappropriate ioctl for device", which I believe is related as well. Anything I can do to diagnose this problem? Jiawei -- "Without the userland, the kernel is useless." --inspired by The Tao of Programming From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:51:53 2004 Return-Path: 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 10E6816A4CE for ; Thu, 18 Nov 2004 16:51:53 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1188943D46 for ; Thu, 18 Nov 2004 16:51:52 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAIGpWAN041234 for ; Thu, 18 Nov 2004 17:51:32 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <419CD314.80900@fer.hr> Date: Thu, 18 Nov 2004 17:51:32 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:51:53 -0000 Hi! I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works fine, but it would be nice to replace /usr/bin/passwd with smbldap-passwd (which changes both NTLM and Unix password fields in LDAP, while passwd is unaware of LDAP, at least according to man page). Is there a clean way of doing it so I don't have to replace it by hand after each installworld? From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:52:47 2004 Return-Path: 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 3929816A4CE for ; Thu, 18 Nov 2004 16:52:47 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 661AE43D39 for ; Thu, 18 Nov 2004 16:52:46 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iAIGqiRT013923; Thu, 18 Nov 2004 18:52:45 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iAIGqiSj046422; Thu, 18 Nov 2004 18:52:44 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)iAIGqic1046421; Thu, 18 Nov 2004 18:52:44 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 18 Nov 2004 18:52:44 +0200 From: Giorgos Keramidas To: Poul-Henning Kamp Message-ID: <20041118165244.GA46388@orion.daedalusnetworks.priv> References: <20041118164356.GA46185@orion.daedalusnetworks.priv> <51652.1100796421@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51652.1100796421@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:52:47 -0000 On 2004-11-18 17:47, Poul-Henning Kamp wrote: > In message <20041118164356.GA46185@orion.daedalusnetworks.priv>, > Giorgos Keramidas writes: > > > BLOCK fcntl > > > >This is apparently the result of the following code from screen/socket.c: > > > > 793 #ifdef NAMEDPIPE > > 794 debug("Ha, there was someone knocking on my fifo??\n"); > > 795 if (fcntl(ServerSocket, F_SETFL, 0) == -1) > > 796 Panic(errno, "BLOCK fcntl"); > > 797 #else > > > >At line 795, screen attempts to set blocking mode on a FIFO and fails. > > Can you get me the exact errno value ? Sure. It's ENOTTY. From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 16:54:51 2004 Return-Path: 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 0DDD416A4CE; Thu, 18 Nov 2004 16:54:51 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DAB343D45; Thu, 18 Nov 2004 16:54:49 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAIGrLuK070996; Thu, 18 Nov 2004 09:53:21 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Thu, 18 Nov 2004 09:53:48 -0700 (MST) Message-Id: <20041118.095348.103081513.imp@bsdimp.com> To: rwatson@freebsd.org From: "M. Warner Losh" In-Reply-To: References: <200411172357.47735.Emanuel.Strobl@gmx.net> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: Emanuel.Strobl@gmx.net cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 16:54:51 -0000 In message: Robert Watson writes: : (1) I'd first off check that there wasn't a serious interrupt problem on : the box, which is often triggered by ACPI problems. Get the box to be : as idle as possible, and then use vmstat -i or stat -vmstat to see if : anything is spewing interrupts. Also, make sure that you aren't sharing interrupts between GIANT-LOCKED and non-giant-locked cards. This might be exposing bugs in the network layer that debug.mpsafenet=0 might correct. Just noticed that our setup here has that setup, so I'll be looking into that area of things. Warner From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 17:01:04 2004 Return-Path: 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 23E0716A4CE; Thu, 18 Nov 2004 17:01:03 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C01C43D49; Thu, 18 Nov 2004 17:01:03 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAIH12xc052049; Thu, 18 Nov 2004 18:01:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Giorgos Keramidas From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 18 Nov 2004 18:52:44 +0200." <20041118165244.GA46388@orion.daedalusnetworks.priv> Date: Thu, 18 Nov 2004 18:01:02 +0100 Message-ID: <52048.1100797262@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:01:04 -0000 In message <20041118165244.GA46388@orion.daedalusnetworks.priv>, Giorgos Kerami das writes: >On 2004-11-18 17:47, Poul-Henning Kamp wrote: >> In message <20041118164356.GA46185@orion.daedalusnetworks.priv>, >> Giorgos Keramidas writes: >> >> > BLOCK fcntl >> > >> >This is apparently the result of the following code from screen/socket.c: >> > >> > 793 #ifdef NAMEDPIPE >> > 794 debug("Ha, there was someone knocking on my fifo??\n"); >> > 795 if (fcntl(ServerSocket, F_SETFL, 0) == -1) >> > 796 Panic(errno, "BLOCK fcntl"); >> > 797 #else >> > >> >At line 795, screen attempts to set blocking mode on a FIFO and fails. >> >> Can you get me the exact errno value ? > >Sure. It's ENOTTY. Ok, found it, my bug, can you try this patch: Index: fs/fifofs/fifo_vnops.c =================================================================== RCS file: /home/ncvs/src/sys/fs/fifofs/fifo_vnops.c,v retrieving revision 1.105 diff -u -r1.105 fifo_vnops.c --- fs/fifofs/fifo_vnops.c 17 Nov 2004 07:30:02 -0000 1.105 +++ fs/fifofs/fifo_vnops.c 18 Nov 2004 16:59:25 -0000 @@ -566,8 +566,27 @@ static int fifo_ioctl_f(struct file *fp, u_long com, void *data, struct ucred *cred, struct thread *td) { + struct fifoinfo *fi; + struct file filetmp; /* Local, so need not be locked. */ + int error; - return (vnops.fo_ioctl(fp, com, data, cred, td)); + error = ENOTTY; + fi = fp->f_data; + if (com == FIONBIO) + return (0); + if (fp->f_flag & FREAD) { + filetmp.f_data = fi->fi_readsock; + filetmp.f_cred = cred; + error = soo_ioctl(&filetmp, com, data, cred, td); + if (error) + return (error); + } + if (fp->f_flag & FWRITE) { + filetmp.f_data = fi->fi_writesock; + filetmp.f_cred = cred; + error = soo_ioctl(&filetmp, com, data, cred, td); + } + return (error); } static int -- 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 Thu Nov 18 17:10:25 2004 Return-Path: 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 B4A0216A4CE for ; Thu, 18 Nov 2004 17:10:25 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 393AB43D2F for ; Thu, 18 Nov 2004 17:10:25 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAIHACkC030906; Thu, 18 Nov 2004 11:10:12 -0600 (CST) (envelope-from dan) Date: Thu, 18 Nov 2004 11:10:12 -0600 From: Dan Nelson To: Ivan Voras Message-ID: <20041118171012.GB19265@dan.emsphone.com> References: <419CD314.80900@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419CD314.80900@fer.hr> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:10:25 -0000 In the last episode (Nov 18), Ivan Voras said: > I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works > fine, but it would be nice to replace /usr/bin/passwd with > smbldap-passwd (which changes both NTLM and Unix password fields in > LDAP, while passwd is unaware of LDAP, at least according to man > page). Is there a clean way of doing it so I don't have to replace > it by hand after each installworld? passwd just uses PAM to set passwords, so the cleanest way would be to have a pam_smb module that does the password changes, and add it to /etc/pam.d/passwd , or maybe tell have pam_ldap do it. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 17:18:12 2004 Return-Path: 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 D65EF16A4D6 for ; Thu, 18 Nov 2004 17:18:10 +0000 (GMT) Received: from lara.cc.fer.hr (lara.cc.fer.hr [161.53.72.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FEE243D53 for ; Thu, 18 Nov 2004 17:18:10 +0000 (GMT) (envelope-from ivoras@fer.hr) Received: from [127.0.0.1] (localhost.cc.fer.hr [127.0.0.1]) by lara.cc.fer.hr (8.13.1/8.13.1) with ESMTP id iAIHHlf1041395; Thu, 18 Nov 2004 18:17:47 +0100 (CET) (envelope-from ivoras@fer.hr) Message-ID: <419CD93B.8010906@fer.hr> Date: Thu, 18 Nov 2004 18:17:47 +0100 From: Ivan Voras User-Agent: Mozilla Thunderbird 0.9 (X11/20041111) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dan Nelson References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> In-Reply-To: <20041118171012.GB19265@dan.emsphone.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:18:12 -0000 Dan Nelson wrote: > In the last episode (Nov 18), Ivan Voras said: > passwd just uses PAM to set passwords, so the cleanest way would be to I see in the source that it calls some pam_* functions (I'm not an expert...), so it should probably be documented in the man page. > have a pam_smb module that does the password changes, and add it to > /etc/pam.d/passwd , or maybe tell have pam_ldap do it. The LDAP user entry contains both password used for unix (userPassword) and NT passwords (sambaNTPassword, sambaLMPassword) - can PAM modules be "stacked" to update all those fields? (if so, how? :) ) I still feel that installing pam_smb would not be a good idea since I'm authenticating on the FreeBSD machine just fine using only pam_ldap. From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 17:18:58 2004 Return-Path: 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 14D9516A4EC for ; Thu, 18 Nov 2004 17:18:58 +0000 (GMT) Received: from av9-1-sn4.m-sp.skanova.net (av9-1-sn4.m-sp.skanova.net [81.228.10.108]) by mx1.FreeBSD.org (Postfix) with ESMTP id C2F8543D53 for ; Thu, 18 Nov 2004 17:18:57 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av9-1-sn4.m-sp.skanova.net (Postfix, from userid 502) id 288093805E; Thu, 18 Nov 2004 18:18:57 +0100 (CET) Received: from smtp2-1-sn4.m-sp.skanova.net (smtp2-1-sn4.m-sp.skanova.net [81.228.10.183]) by av9-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id 19BFB37E69; Thu, 18 Nov 2004 18:18:57 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-1-sn4.m-sp.skanova.net (Postfix) with ESMTP id ED81737E47; Thu, 18 Nov 2004 18:18:56 +0100 (CET) From: "Daniel Eriksson" To: "'Poul-Henning Kamp'" , Date: Thu, 18 Nov 2004 18:18:51 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <38192.1100388485@critter.freebsd.dk> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTJ2QAZlsZiMv9WQxWk4PcPSMqLPwDuSTIg Subject: DEVFS problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:18:58 -0000 With a system compiled from sources from yesterday (2004.11.17.12.00.00), hiding and unhiding devfs devices does not work. Normally I do something like this to only expose the devices I really want in the chroot/jail environment: mount_devfs devfs /some/path/dev devfs -m /some/path/dev rule apply hide devfs -m /some/path/dev rule apply path null unhide devfs -m /some/path/dev rule apply path zero unhide devfs -m /some/path/dev rule apply path random unhide With recent CURRENT, the devfs rules results in this error message: devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device Am I doing something wrong, or has a bug crept into the code? /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 17:19:59 2004 Return-Path: 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 9EB4716A4CE for ; Thu, 18 Nov 2004 17:19:59 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4CC043D41 for ; Thu, 18 Nov 2004 17:19:58 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAIHJvJf052422; Thu, 18 Nov 2004 18:19:57 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Daniel Eriksson" From: "Poul-Henning Kamp" In-Reply-To: Your message of "Thu, 18 Nov 2004 18:18:51 +0100." Date: Thu, 18 Nov 2004 18:19:57 +0100 Message-ID: <52421.1100798397@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: freebsd-current@freebsd.org Subject: Re: DEVFS problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:19:59 -0000 In message , "Daniel Eriksson" writes: > >With a system compiled from sources from yesterday (2004.11.17.12.00.00), >hiding and unhiding devfs devices does not work. > >Normally I do something like this to only expose the devices I really want >in the chroot/jail environment: > >mount_devfs devfs /some/path/dev >devfs -m /some/path/dev rule apply hide >devfs -m /some/path/dev rule apply path null unhide >devfs -m /some/path/dev rule apply path zero unhide >devfs -m /some/path/dev rule apply path random unhide > >With recent CURRENT, the devfs rules results in this error message: >devfs rule: ioctl DEVFSIO_RAPPLY: Inappropriate ioctl for device My bug, just fixed a minute ago. -- 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 Thu Nov 18 17:33:09 2004 Return-Path: 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 C417E16A4F8 for ; Thu, 18 Nov 2004 17:33:07 +0000 (GMT) Received: from kane.otenet.gr (kane.otenet.gr [195.170.0.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09E5B43D2F for ; Thu, 18 Nov 2004 17:33:07 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iAIHX5rO029148; Thu, 18 Nov 2004 19:33:05 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iAIHX4KW000784; Thu, 18 Nov 2004 19:33:04 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)iAIHX2is000783; Thu, 18 Nov 2004 19:33:02 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Thu, 18 Nov 2004 19:33:02 +0200 From: Giorgos Keramidas To: Poul-Henning Kamp Message-ID: <20041118173302.GA750@orion.daedalusnetworks.priv> References: <20041118165244.GA46388@orion.daedalusnetworks.priv> <52048.1100797262@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52048.1100797262@critter.freebsd.dk> cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:33:09 -0000 On 2004-11-18 18:01, Poul-Henning Kamp wrote: > In message <20041118165244.GA46388@orion.daedalusnetworks.priv>, Giorgos Kerami > das writes: > >On 2004-11-18 17:47, Poul-Henning Kamp wrote: > >> In message <20041118164356.GA46185@orion.daedalusnetworks.priv>, > >> Giorgos Keramidas writes: > >> > >> > BLOCK fcntl > >> > > >> >This is apparently the result of the following code from screen/socket.c: > >> > > >> > 793 #ifdef NAMEDPIPE > >> > 794 debug("Ha, there was someone knocking on my fifo??\n"); > >> > 795 if (fcntl(ServerSocket, F_SETFL, 0) == -1) > >> > 796 Panic(errno, "BLOCK fcntl"); > >> > 797 #else > >> > > >> >At line 795, screen attempts to set blocking mode on a FIFO and fails. > >> > >> Can you get me the exact errno value ? > > > >Sure. It's ENOTTY. > > Ok, found it, my bug, can you try this patch: Magnificent! Everything works now with fifos too :-) > Index: fs/fifofs/fifo_vnops.c > =================================================================== > RCS file: /home/ncvs/src/sys/fs/fifofs/fifo_vnops.c,v > retrieving revision 1.105 > diff -u -r1.105 fifo_vnops.c > --- fs/fifofs/fifo_vnops.c 17 Nov 2004 07:30:02 -0000 1.105 > +++ fs/fifofs/fifo_vnops.c 18 Nov 2004 16:59:25 -0000 > @@ -566,8 +566,27 @@ > static int > fifo_ioctl_f(struct file *fp, u_long com, void *data, struct ucred *cred, struct thread *td) > { > + struct fifoinfo *fi; > + struct file filetmp; /* Local, so need not be locked. */ > + int error; > > - return (vnops.fo_ioctl(fp, com, data, cred, td)); > + error = ENOTTY; > + fi = fp->f_data; > + if (com == FIONBIO) > + return (0); > + if (fp->f_flag & FREAD) { > + filetmp.f_data = fi->fi_readsock; > + filetmp.f_cred = cred; > + error = soo_ioctl(&filetmp, com, data, cred, td); > + if (error) > + return (error); > + } > + if (fp->f_flag & FWRITE) { > + filetmp.f_data = fi->fi_writesock; > + filetmp.f_cred = cred; > + error = soo_ioctl(&filetmp, com, data, cred, td); > + } > + return (error); > } > > static int From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 17:49:15 2004 Return-Path: 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 6CE5F16A4CE; Thu, 18 Nov 2004 17:49:15 +0000 (GMT) Received: from av7-2-sn4.m-sp.skanova.net (av7-2-sn4.m-sp.skanova.net [81.228.10.109]) by mx1.FreeBSD.org (Postfix) with ESMTP id DF8BF43D58; Thu, 18 Nov 2004 17:49:14 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av7-2-sn4.m-sp.skanova.net (Postfix, from userid 502) id 1C7C738128; Thu, 18 Nov 2004 18:49:14 +0100 (CET) Received: from smtp2-2-sn4.m-sp.skanova.net (smtp2-2-sn4.m-sp.skanova.net [81.228.10.182]) by av7-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id 0BC803811E; Thu, 18 Nov 2004 18:49:14 +0100 (CET) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp2-2-sn4.m-sp.skanova.net (Postfix) with ESMTP id D471D37E49; Thu, 18 Nov 2004 18:49:13 +0100 (CET) From: "Daniel Eriksson" To: "'M. Warner Losh'" Date: Thu, 18 Nov 2004 18:49:08 +0100 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 In-Reply-To: <20041118.095348.103081513.imp@bsdimp.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcTNj/SLjGIxsillTd6Wa8mCXkRe+QABFJuw cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: RE: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 17:49:15 -0000 M. Warner Losh wrote: > Also, make sure that you aren't sharing interrupts between > GIANT-LOCKED and non-giant-locked cards. This might be exposing bugs > in the network layer that debug.mpsafenet=0 might correct. Just > noticed that our setup here has that setup, so I'll be looking into > that area of things. I have a Tyan Tiger MPX board (dual AthlonMP) that has two 64bit PCI slots. I have an Adaptec 29160 and a dual port Intel Pro/1000 MT plugged into those slots. As can be seen from the vmstat -i output below, em1 shares ithread with ahc0. This is with ACPI disabled. With ACPI enabled all devices get their own ithread (I think, not 100% sure). However, because of some hardware problem (interrupt routing?), em0 interrupts will somehow leak into atapci1+, generating a higher interrupt load. I'm not sure how expensive this is. Finally, my question. What would you recommend: 1) Run with ACPI disabled and debug.mpsafenet=1 and hope that the mix of giant-safe and giant-locked (em and ahc) doesn't trigger any bugs. This is what I currently do. 2) Run with ACPI disabled and debug.mpsafenet=0 and accept lower network performance (it is a high-traffic server, so I'm not sure this is a valid option). 3) Run with ACPI enabled and debug.mpsafenet=1 and accept that em0 interrupts "leak" to the atapci1+ ithread. This I have done in the past. # vmstat -i interrupt total rate irq1: atkbd0 2 0 irq4: sio0 710 0 irq6: fdc0 8 0 irq8: rtc 11470937 127 irq13: npx0 1 0 irq14: ata0 1744545 19 irq15: ata1 1749617 19 irq16: em0 atapci1+ 186062858 2074 irq17: em1 ahc0 27028088 301 irq18: atapci3 7393468 82 irq19: atapci4+ 7129446 79 irq0: clk 179054582 1995 Total 421634262 4699 /Daniel Eriksson From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 18:09:26 2004 Return-Path: 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 8FE7316A4CE; Thu, 18 Nov 2004 18:09:26 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 189D343D1F; Thu, 18 Nov 2004 18:09:26 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAII7lca075651; Thu, 18 Nov 2004 13:07:47 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAII7lsn075648; Thu, 18 Nov 2004 18:07:47 GMT (envelope-from robert@fledge.watson.org) Date: Thu, 18 Nov 2004 18:07:47 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Daniel Eriksson In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org cc: "'M. Warner Losh'" Subject: RE: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 18:09:26 -0000 On Thu, 18 Nov 2004, Daniel Eriksson wrote: > I have a Tyan Tiger MPX board (dual AthlonMP) that has two 64bit PCI > slots. I have an Adaptec 29160 and a dual port Intel Pro/1000 MT > plugged into those slots. > > As can be seen from the vmstat -i output below, em1 shares ithread with > ahc0. This is with ACPI disabled. With ACPI enabled all devices get > their own ithread (I think, not 100% sure). However, because of some > hardware problem (interrupt routing?), em0 interrupts will somehow leak > into atapci1+, generating a higher interrupt load. I'm not sure how > expensive this is. I see precisely this problem on several motherboards, including the Intel Westville. There's some speculation on the source of the problem, but I see related problems in 4.x as well. Either I get them on different interrupts but both fire, or on the same interrupt. FYI, picking the right one depends a bit on your configuration, but generally scheduling multiple ithreads is more expensive than running multiple handlers in the same ithread, so I think it's generally preferable to run with them on the same interrupt. Especially if nothing on the same interrupt is acquiring Giant. Acquiring and dropping Giant uncontended is cheaper than context switching, however. > Finally, my question. What would you recommend: > 1) Run with ACPI disabled and debug.mpsafenet=1 and hope that the mix of > giant-safe and giant-locked (em and ahc) doesn't trigger any bugs. This is > what I currently do. This shouldn't cause bugs; the ithread handler is smart and will acquire Giant around the ahc code. That will also make it slower due to the extra mutex operations, however. > 2) Run with ACPI disabled and debug.mpsafenet=0 and accept lower network > performance (it is a high-traffic server, so I'm not sure this is a valid > option). > 3) Run with ACPI enabled and debug.mpsafenet=1 and accept that em0 > interrupts "leak" to the atapci1+ ithread. This I have done in the past. I think you want to run the ahc stuff, unfortunately. The good news is that the higher the load, the more interrupt mitigation/coalescing will kick in for if_em, so the fewer you'll see. Under load, usually my boxes hang out at 4k-6k interrupts/sec for if_em and don't go much above that. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 18:53:53 2004 Return-Path: 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 69B3216A4CE; Thu, 18 Nov 2004 18:53:53 +0000 (GMT) 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 B6C8643D2F; Thu, 18 Nov 2004 18:53:52 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAIIrk6a097551; Thu, 18 Nov 2004 19:53:50 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419CEFB9.7060604@DeepCore.dk> Date: Thu, 18 Nov 2004 19:53:45 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maseed References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org cc: freebsd-questions@freebsd.org Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 18:53:53 -0000 Maseed wrote: [SNIP] > I have to point out in the above e-mail that the problem is not just > confined to the 36GB Raptor, which might be a PATA drive with a Marvel > chip to make it work with SATA drives, but it also plages *real* > native SATA drives as well, since the 74GB Western Digital Raptor I > have is a true SATA150 drive with TCQ. Correction, the 74GB Raptor is still not a pure or native SATA device,=20 it still uses the marvell PATA-SATA converter chip. Its true that it=20 supports TCQ but thats the same old way as the IBM deathstars used, and=20 not directly comaprable to the new true SATA NCQ way of things. > Anyhow, I am wondering if this issue has been resolved yet or not, > either in FreeBSD-current or 5.3-RELEASE-px. I don't want to discard > my current OS to install FreeBSD only to find out that the problem is > still there. If any sort of error logs or dmesg output is required by > a potential developer from this setup of mine, I'll go so far as to > resize my partition and install FreeBSD 5.3 and provide them, but the > reason why I'm hesitant in doing that is the fact that I run a > web-server on my computer that cannot stay down for long, as some > friends of mine depend on it. If you want 24/7 uptime, you *really* should be bying hardware of a=20 quality that matches that, the SiI3112 is *not* in that league, not even = close. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 19:32:04 2004 Return-Path: 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 2AE7916A4CE for ; Thu, 18 Nov 2004 19:32:04 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id C3D9C43D41 for ; Thu, 18 Nov 2004 19:32:03 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id iAIJW1RF025175; Thu, 18 Nov 2004 13:32:01 -0600 (CST) (envelope-from dan) Date: Thu, 18 Nov 2004 13:32:01 -0600 From: Dan Nelson To: Ivan Voras Message-ID: <20041118193201.GD19265@dan.emsphone.com> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> <419CD93B.8010906@fer.hr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <419CD93B.8010906@fer.hr> X-OS: FreeBSD 5.3-STABLE X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 19:32:04 -0000 In the last episode (Nov 18), Ivan Voras said: > Dan Nelson wrote: > >In the last episode (Nov 18), Ivan Voras said: > >passwd just uses PAM to set passwords, so the cleanest way would be to > > I see in the source that it calls some pam_* functions (I'm not an > expert...), so it should probably be documented in the man page. > > >have a pam_smb module that does the password changes, and add it to > >/etc/pam.d/passwd , or maybe tell have pam_ldap do it. > > The LDAP user entry contains both password used for unix (userPassword) > and NT passwords (sambaNTPassword, sambaLMPassword) - can PAM modules be > "stacked" to update all those fields? (if so, how? :) ) Sure. Just mark both as required, and it'll run them. > I still feel that installing pam_smb would not be a good idea since I'm > authenticating on the FreeBSD machine just fine using only pam_ldap. If you only configure the "password" service, it won't use pam_smb for authentication at all. -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 20:41:35 2004 Return-Path: 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 CB40316A4CE for ; Thu, 18 Nov 2004 20:41:35 +0000 (GMT) Received: from smtp4.server.rpi.edu (smtp4.server.rpi.edu [128.113.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6093C43D58 for ; Thu, 18 Nov 2004 20:41:35 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp4.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iAIKfS0u006817; Thu, 18 Nov 2004 15:41:29 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <419CEFB9.7060604@DeepCore.dk> References: <419CEFB9.7060604@DeepCore.dk> Date: Thu, 18 Nov 2004 15:41:28 -0500 To: =?iso-8859-1?Q?S=F8ren?= Schmidt , Maseed From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 20:41:35 -0000 At 7:53 PM +0100 11/18/04, S=F8ren Schmidt wrote: >Maseed wrote: > >[SNIP] >>I have to point out in the above e-mail that the problem is not just >>confined to the 36GB Raptor, which might be a PATA drive with a Marvel >>chip to make it work with SATA drives, but it also plages *real* >>native SATA drives as well, since the 74GB Western Digital Raptor I >>have is a true SATA150 drive with TCQ. > >Correction, the 74GB Raptor is still not a pure or native SATA device, >it still uses the marvell PATA-SATA converter chip. Its true that it >supports TCQ but thats the same old way as the IBM deathstars used, >and not directly comaprable to the new true SATA NCQ way of things. > >>Anyhow, I am wondering if this issue has been resolved yet or not, >>either in FreeBSD-current or 5.3-RELEASE-px. > >If you want 24/7 uptime, you *really* should be bying hardware of >a quality that matches that, the SiI3112 is *not* in that league, >not even close. I am trying to pin down problems "FAILURE - WRITE_DMA timed out" in a new PC that I have. I had some local shop build this for me, and apparently there were "a few" miscommunications in what I thought I asked for, and what they actually built. The machine ended up with two SATA controllers: atapci0: -- on the motherboard atapci1: -- on a PCI card The hard disk is connected to the PCI card. Would that be more reliable quality hardware than the SiI3112? Also, the disk is a Western Digital WDC WD1200JD-00GBB0/02.05D02 120-gig drive. I *thought* I was ordering a Seagate drive, but it is quite likely that there was some confusion on that. Would that Western Digital SATA drive be a problem? I do have a Seagate Barracuda 7200.7 hard drive that I could use (after shuffling a few things around). -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 21:11:30 2004 Return-Path: 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 570EE16A4CE for ; Thu, 18 Nov 2004 21:11:30 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01D8643D62 for ; Thu, 18 Nov 2004 21:11:30 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id 9C24FF20B2; Thu, 18 Nov 2004 13:11:29 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 58731-02; Thu, 18 Nov 2004 13:11:26 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id B6B96F1983; Thu, 18 Nov 2004 13:11:22 -0800 (PST) From: Sean McNeil To: "Conrad J. Sabatier" In-Reply-To: <20041118100224.2428c9d9@dolphin.local.net> References: <1100556108.3025.1.camel@server.mcneil.com> <20041118100224.2428c9d9@dolphin.local.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-KNDnulq4baWcjwTcPIrA" Date: Thu, 18 Nov 2004 13:11:22 -0800 Message-Id: <1100812282.96668.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: natd panics are back X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 21:11:30 -0000 --=-KNDnulq4baWcjwTcPIrA Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Thu, 2004-11-18 at 10:02 -0600, Conrad J. Sabatier wrote: > On Mon, 15 Nov 2004 14:01:48 -0800, Sean McNeil wrote: >=20 > > This was fixed a while ago and now it has made its way back into > > current: > >=20 > > server# uname -a > > FreeBSD server.mcneil.com 6.0-CURRENT FreeBSD 6.0-CURRENT #58: Mon Nov > > 15 08:40:01 PST 2004 =20 > > root@server.mcneil.com:/usr/obj/usr/src/sys/AMD64 amd64 > >=20 > > Nov 15 13:56:16 server kernel: Fatal trap 12: page fault while in > > kernel mode Nov 15 13:56:16 server kernel: fault virtual address =3D > > 0x18 Nov 15 13:56:16 server kernel: fault code =3D > > supervisor read, page not present > > Nov 15 13:56:16 server kernel: instruction pointer =3D > > 0x8:0xffffffff80354810Nov 15 13:56:16 server kernel: stack pointer =20 > > =3D 0x10:0xffffffffb1c71620 > > Nov 15 13:56:16 server kernel: frame pointer =3D > > 0x10:0xffffffffb1c71680 Nov 15 13:56:16 server kernel: code segment =20 > > =3D base 0x0, limit 0xfffff, type 0x1b > > Nov 15 13:56:16 server kernel: =3D DPL 0, pres 1, long 1, def32 0, gran > > 1 Nov 15 13:56:16 server kernel: processor eflags =3D interrupt enabled= , > > resume, IOPL =3D 0 Nov 15 13:56:16 server kernel: current process = =20 > > =3D 212 (natd) > > Nov 15 13:56:16 server kernel: trap number =3D 12 > > Nov 15 13:56:16 server kernel: panic: page fault > > Nov 15 13:56:16 server kernel: KDB: enter: panic > >=20 > >=20 > > (gdb) l *0xffffffff80354810 > > 0xffffffff80354810 is in m_copym (/usr/src/sys/kern/uipc_mbuf.c:373). > > 368 MBUF_CHECKSLEEP(wait); > > 369 if (off =3D=3D 0 && m->m_flags & M_PKTHDR) > > 370 copyhdr =3D 1; > > 371 while (off > 0) { > > 372 KASSERT(m !=3D NULL, ("m_copym, offset > size o= f > > mbuf chain")); 373 if (off < m->m_len) > > 374 break; > > 375 off -=3D m->m_len; > > 376 m =3D m->m_next; > > 377 } >=20 > Are you still having this problem? I went a few days without upgrading, > then cvsupped and built a new world/kernel yesterday. No panic on boot > with natd. >=20 > This is on my amd64 box. Haven't upgraded my i386 box yet. No, this problem has not reared its ugly head again. I hope I have it setup correctly for crash dumps now, so if it does happen again I should be able to get more info. --=-KNDnulq4baWcjwTcPIrA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnQ/6yQsGN30uGE4RAkjhAJ9bG9NYebMjqPFWfYKbdgLcwKsR9QCeMmDL TPpSnpZ2Nsq3LuomKSbRob0= =7WGB -----END PGP SIGNATURE----- --=-KNDnulq4baWcjwTcPIrA-- From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 21:12:30 2004 Return-Path: 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 7E04516A4CE; Thu, 18 Nov 2004 21:12:30 +0000 (GMT) Received: from mailhost.schluting.com (schluting.com [131.252.214.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6136743D58; Thu, 18 Nov 2004 21:12:30 +0000 (GMT) (envelope-from charlie@schluting.com) Received: from localhost (localhost [127.0.0.1]) by mailhost.schluting.com (Postfix) with ESMTP id 04C84248A; Thu, 18 Nov 2004 13:12:30 -0800 (PST) Received: from mailhost.schluting.com ([127.0.0.1]) by localhost (schluting.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 67418-06; Thu, 18 Nov 2004 13:12:07 -0800 (PST) Received: from [131.252.209.122] (smelly.cat.pdx.edu [131.252.209.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailhost.schluting.com (Postfix) with ESMTP id B3C5D243F; Thu, 18 Nov 2004 13:12:05 -0800 (PST) Message-ID: <419D1025.40309@schluting.com> Date: Thu, 18 Nov 2004 13:12:05 -0800 From: Charlie Schluting User-Agent: Mozilla Thunderbird 0.6 (X11/20040519) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-gnats-submit@FreeBSD.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by your mom at schluting.com cc: current@freebsd.org Subject: Re: i386/17800:PATCH problem with statclock initialization (NEW Patch) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 21:12:30 -0000 I had the same problem described in this PR with a Dell Latitude CPt. I believe its the same motherboard, or very similar. In both 5.2.1 and 6-CURRENT I couldn't get cpu usage stats. Jose's patch fixes it... though the patch is no longer valid in 6-CURRENT (from cvs 2 days ago). New patch. Same content, different location: --------------------------------------------------------------------- --- sys/i386/isa/clock.c.old Thu Nov 18 11:18:59 2004 +++ sys/i386/isa/clock.c Thu Nov 18 11:12:10 2004 @@ -946,6 +946,7 @@ /* Initialize RTC. */ writertc(RTC_STATUSA, rtc_statusa); writertc(RTC_STATUSB, RTCSB_24HR); + rtcin(RTC_INTR); /* clear any pending interrupt */ /* Don't bother enabling the statistics clock. */ if (!statclock_disable) { --------------------------------------------------------------------- Tested, and it works. Please commit :) -Charlie Schluting From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 21:30:12 2004 Return-Path: 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 E21D216A4CE for ; Thu, 18 Nov 2004 21:30:12 +0000 (GMT) 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 3BC0843D2D for ; Thu, 18 Nov 2004 21:30:12 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAILU7C6099406; Thu, 18 Nov 2004 22:30:09 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419D145E.8090108@DeepCore.dk> Date: Thu, 18 Nov 2004 22:30:06 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: <419CEFB9.7060604@DeepCore.dk> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: Maseed cc: freebsd-current@freebsd.org Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 21:30:13 -0000 Garance A Drosihn wrote: > I am trying to pin down problems "FAILURE - WRITE_DMA timed out" > in a new PC that I have. I had some local shop build this for me, > and apparently there were "a few" miscommunications in what I > thought I asked for, and what they actually built. >=20 > The machine ended up with two SATA controllers: > atapci0: -- on the motherboard > atapci1: -- on a PCI card I think its the other way around, the VIA chip is part of the=20 motherboard chipset, the SiI is a "loose" PCI compatible chip. > The hard disk is connected to the PCI card. Would that be more > reliable quality hardware than the SiI3112? I'd say so. > Also, the disk is a Western Digital WDC WD1200JD-00GBB0/02.05D02 > 120-gig drive. I *thought* I was ordering a Seagate drive, but it is > quite likely that there was some confusion on that. Would that Western= > Digital SATA drive be a problem? I do have a Seagate Barracuda 7200.7 > hard drive that I could use (after shuffling a few things around). From observation I'd say that those drives that are native SATA devices = has significantly less problems than those that arent. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 21:31:22 2004 Return-Path: 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 996E716A4CF; Thu, 18 Nov 2004 21:31:22 +0000 (GMT) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6D81343D48; Thu, 18 Nov 2004 21:31:22 +0000 (GMT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) iAILVKcW032004; Thu, 18 Nov 2004 13:31:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id iAILVJ1T032003; Thu, 18 Nov 2004 13:31:19 -0800 (PST) (envelope-from dillon) Date: Thu, 18 Nov 2004 13:31:19 -0800 (PST) From: Matthew Dillon Message-Id: <200411182131.iAILVJ1T032003@apollo.backplane.com> To: Wilko Bulte References: <200411172357.47735.Emanuel.Strobl@gmx.net> <20041118124902.GC75559@freebie.xs4all.nl> cc: Emanuel Strobl cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 21:31:22 -0000 Polling should not produce any improvement over interrupts for EM0. The EM0 card will aggregate 8-14+ packets per interrupt, or more. which is only around 8000 interrupts/sec. I've got a ton of these cards installed. # mount_nfs -a 4 dhcp61:/home /mnt # dd if=/mnt/x of=/dev/null bs=32k # netstat -in 1 input (Total) output packets errs bytes packets errs bytes colls 66401 0 93668746 5534 0 962920 0 66426 0 94230092 5537 0 1007108 0 66424 0 93699848 5536 0 963268 0 66422 0 94222372 5536 0 1007290 0 66391 0 93654846 5534 0 962746 0 66375 0 94154432 5532 0 1006404 0 zfod Interrupts Proc:r p d s w Csw Trp Sys Int Sof Flt cow 8100 total 1 9 6211 7 75 8100 4 12 88864 wire 7873 mux irq10 10404 act ata0 irq14 19.2%Sys 0.0%Intr 0.0%User 0.0%Nice 80.8%Idl 864476 inact ata1 irq15 | | | | | | | | | | 58152 cache mux irq11 ========== 2992 free 227 clk irq0 Note that the interrupt rate is only 7873 interrupts per second while I am transfering 94 MBytes/sec over NFS (UDP) and receiving over 66000 packets per second (~8 packets per interrupt). If I use a TCP mount I get just about the same thing: # mount_nfs -T -a 4 dhcp61:/home /mnt # dd if=/mnt/x of=/dev/null bs=32k # netstat -in 1 input (Total) output packets errs bytes packets errs bytes colls 61752 0 93978800 8091 0 968618 0 61780 0 93530484 8098 0 904370 0 61710 0 93917880 8093 0 968128 0 61754 0 93491260 8095 0 903940 0 61756 0 93986320 8097 0 968336 0 Proc:r p d s w Csw Trp Sys Int Sof Flt cow 8145 total 5 8 22828 13 5490 8146 13 11 141556 wire 7917 mux irq10 7800 act ata0 irq14 26.4%Sys 0.0%Intr 0.0%User 0.0%Nice 73.6%Idl 244872 inact ata1 irq15 | | | | | | | | | | 8 cache mux irq11 ============= 630780 free 228 clk irq0 In this case around 8000 interrupts per second with 61700 packet per second incoming on the interface (around ~8 packets per interrupt). The extra interrupts are due to the additional outgoing TCP ack traffic. If I look at the systat -vm 1 output on the NFS server it also sees only around 8000 interrupts per second, which isn't saying much other then it's transmit path (61700 pps outoging) is not creating an undue interrupt burden relative to the receive path. -Matt From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 22:42:47 2004 Return-Path: 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 5C67816A4CE for ; Thu, 18 Nov 2004 22:42:47 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id C59D143D58 for ; Thu, 18 Nov 2004 22:42:45 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAIMfjZg017399 for ; Fri, 19 Nov 2004 09:11:45 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.10) with ESMTP id for ; Fri, 19 Nov 2004 09:12:37 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id iAIMZih17242 for ; Fri, 19 Nov 2004 09:05:45 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDSGQQ; Fri, 19 Nov 2004 09:05:33 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.12.11/8.12.11) with ESMTP id iAIMahVj071515 for ; Fri, 19 Nov 2004 09:06:43 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.12.11/8.12.11/Submit) id iAIMah0Y071514 for freebsd-current@freebsd.org; Fri, 19 Nov 2004 09:06:43 +1030 (CST) (envelope-from wilkinsa) Date: Fri, 19 Nov 2004 09:06:43 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041118223639.GA71388@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline User-Agent: Mutt/1.5.6i Subject: stray IRQ .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 22:42:47 -0000 Hi all, Whenever I do a shutdown I notice the following warning/error: Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...4 4 3 3 3 0 0 0 0 done No buffers busy after final sync Uptime: 16h6m31s Shutting down ACPI stray irq9 <------- This is what I am concerned about. Rebooting... Is this anything to be concerned about ? What does this actually mean ? FYI # vmstat -i interrupt total rate irq1: atkbd0 10 0 irq4: sio0 372 2 irq6: fdc0 10 0 irq8: rtc 17283 127 irq13: npx0 1 0 irq14: ata0 2524 18 irq15: ata1 105 0 irq18: uhci2 bt0++ 5728 42 irq20: bge0 625 4 irq0: clk 13502 99 Total 40160 295 Thanks - aW From owner-freebsd-current@FreeBSD.ORG Thu Nov 18 23:55:33 2004 Return-Path: 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 913FB16A4CE for ; Thu, 18 Nov 2004 23:55:33 +0000 (GMT) Received: from postal1.es.net (postal1.es.net [198.128.3.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E07543D46 for ; Thu, 18 Nov 2004 23:55:33 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP id IBA74465; Thu, 18 Nov 2004 15:55:32 -0800 Received: from ptavv (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 4BA8E5D04; Thu, 18 Nov 2004 15:55:32 -0800 (PST) To: "Wilkinson, Alex" In-reply-to: Your message of "Fri, 19 Nov 2004 09:06:43 +1030." <20041118223639.GA71388@squash.dsto.defence.gov.au> Date: Thu, 18 Nov 2004 15:55:32 -0800 From: "Kevin Oberman" Message-Id: <20041118235532.4BA8E5D04@ptavv.es.net> cc: freebsd-current@freebsd.org Subject: Re: stray IRQ .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2004 23:55:33 -0000 > Date: Fri, 19 Nov 2004 09:06:43 +1030 > From: "Wilkinson, Alex" > Sender: owner-freebsd-current@freebsd.org > > Hi all, > > Whenever I do a shutdown I notice the following warning/error: > > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...4 4 3 3 3 0 0 0 0 done > No buffers busy after final sync > Uptime: 16h6m31s > Shutting down ACPI > stray irq9 <------- This is what I am concerned about. > Rebooting... > > Is this anything to be concerned about ? > > What does this actually mean ? IRQ 9 is commonly used by ACPI and there seems to be a race where it generates an interrupt after the ACPI handler has gone away. It is common to many platforms and is not of great concern, although I think Nate is hoping to get rid of it some day. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 00:03:31 2004 Return-Path: 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 78BF916A4CE for ; Fri, 19 Nov 2004 00:03:31 +0000 (GMT) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8138843D3F for ; Fri, 19 Nov 2004 00:03:30 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (localhost [127.0.0.1]) (authenticated bits=0) by cain.gsoft.com.au (8.12.11/8.12.10) with ESMTP id iAJ03HIs014598; Fri, 19 Nov 2004 10:33:18 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 19 Nov 2004 10:33:16 +1030 User-Agent: KMail/1.7 References: <20041118223639.GA71388@squash.dsto.defence.gov.au> In-Reply-To: <20041118223639.GA71388@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3059034.WOac7fD51S"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411191033.17282.doconnor@gsoft.com.au> X-Spam-Score: -2.5 () IN_REP_TO,PGP_SIGNATURE_2,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_00_01,USER_AGENT X-Scanned-By: MIMEDefang 2.16 (www . roaringpenguin . com / mimedefang) cc: "Wilkinson, Alex" Subject: Re: stray IRQ .... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 00:03:31 -0000 --nextPart3059034.WOac7fD51S Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 19 Nov 2004 09:06, Wilkinson, Alex wrote: > Waiting (max 60 seconds) for system process `vnlru' to stop...done > Waiting (max 60 seconds) for system process `bufdaemon' to stop...done > Waiting (max 60 seconds) for system process `syncer' to stop... > Syncing disks, vnodes remaining...4 4 3 3 3 0 0 0 0 done > No buffers busy after final sync > Uptime: 16h6m31s > Shutting down ACPI > stray irq9 <------- This is what I am concerned about. > Rebooting... > > Is this anything to be concerned about ? > > What does this actually mean ? It means an irq was generated but there is no device attached to it (ie it= =20 came from nowhere). I'd ignore it. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart3059034.WOac7fD51S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnThF5ZPcIHs/zowRAtbSAJ9zmh/mO2B9e49LYQxFRkSXuEoY0gCgmXyo e6gSbw35A16oqrr7rm5TuZE= =CSpX -----END PGP SIGNATURE----- --nextPart3059034.WOac7fD51S-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 03:02:10 2004 Return-Path: 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 388FF16A4D1; Fri, 19 Nov 2004 03:02:10 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CC2243D39; Fri, 19 Nov 2004 03:02:09 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id 855C02A; Fri, 19 Nov 2004 12:02:07 +0900 (JST) Date: Fri, 19 Nov 2004 12:02:07 +0900 From: Shunsuke SHINOMIYA To: Matthew Dillon In-Reply-To: <200411182131.iAILVJ1T032003@apollo.backplane.com> References: <20041118124902.GC75559@freebie.xs4all.nl> <200411182131.iAILVJ1T032003@apollo.backplane.com> Message-Id: <20041119114233.C43B.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.11.02 [ja] cc: Emanuel Strobl cc: Wilko Bulte cc: Robert Watson cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re[2]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 03:02:10 -0000 Hi list, if you suppose your computer has sufficient performance, please try to disable or adjust parameters of Interrupt Moderation of em. In my router(Xeon 2.4GHz and on-board two em interfaces) case, it improves a router's packet forwarding performance. I think the interrupt delay by Interrupt Moderation caused NIF's input buffer overflow or output buffer underrun in this case. In order to disable Interrupt Moderation, modify src/sys/dev/em/if_em.c like the following patch and set hw.em.{rx,tx}_{,abs_}int_delay zero by sysctl. *** if_em.c-1.44.2.3.orig Fri Nov 19 11:22:48 2004 --- if_em.c Fri Nov 19 11:23:39 2004 *************** em_initialize_receive_unit(struct adapte *** 2611,2618 **** --- 2611,2622 ---- /* Set the interrupt throttling rate. Value is calculated * as DEFAULT_ITR = 1/(MAX_INTS_PER_SEC * 256ns) */ + #if 1 + #define DEFAULT_ITR 0 + #else #define MAX_INTS_PER_SEC 8000 #define DEFAULT_ITR 1000000000/(MAX_INTS_PER_SEC * 256) + #endif E1000_WRITE_REG(&adapter->hw, ITR, DEFAULT_ITR); } -- Shunsuke SHINOMIYA From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 03:34:01 2004 Return-Path: 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 C16FF16A4CE; Fri, 19 Nov 2004 03:34:01 +0000 (GMT) Received: from hotmail.com (bay2-dav17.bay2.hotmail.com [65.54.246.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id A12AA43D49; Fri, 19 Nov 2004 03:34:01 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Thu, 18 Nov 2004 19:34:01 -0800 Message-ID: Received: from 24.24.201.219 by BAY2-DAV17.phx.gbl with DAV; Fri, 19 Nov 2004 03:33:14 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , "Poul-Henning Kamp" References: <26249.1100342074@critter.freebsd.dk> <4195E5DB.2070302@DeepCore.dk> Date: Thu, 18 Nov 2004 19:33:14 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 19 Nov 2004 03:34:01.0006 (UTC) FILETIME=[9C3544E0:01C4CDE8] cc: Garance A Drosihn cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 03:34:01 -0000 For your information, I applied this patch just now to my kernel. Sorry about the delay! I will send an update in a few days once I see if those DMA_WRITE warnings are still happening or not. Zoltan Poul-Henning Kamp wrote: > In message <4195E1FF.5090906@DeepCore.dk>, > =?ISO-8859-1?Q?S=F8ren_Schmidt?= wri > tes: > > >>>>Timeout is 5 secs, which is a pretty long time in this context IMHO.. >>> >>>Five seconds counted from when ? >> >>Now thats the nasty part :) >>ATA starts the timeout when the request is issued to the device, so >>theoretically the disk could take 4.9999 secs to complete the request and >>then the timeout fires before the taskqueue gets its chance at it, but >>IMHO thats pretty unlikely... > > I find that far more likely than kernel threads being stalled for that > long. ATA disks doing bad-block stuff takes several seconds on some > of the disks I've had my hands on. > >>Anyhow, I can just remove the warning from ATA if that makes anyone happy, >>since its just a warning and ATA doesn't do anything with it at all. >>However, IMNHO this points at a problem somewhere that we should better >>understand and fix instead. > > I would prefer you reset the timer to five seconds in your interrupt > routine so we can see exactly on which side of that the time is spent. It would be even better to time how long both ops take and be able to get that via a sysctl or something (I have that on my TODO list but its loooong :) ). Anyhow resetting it is easy (patch against 5.3R): Index: ata-queue.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-queue.c,v retrieving revision 1.32.2.5 diff -u -r1.32.2.5 ata-queue.c --- ata-queue.c 24 Oct 2004 09:27:37 -0000 1.32.2.5 +++ ata-queue.c 13 Nov 2004 10:44:40 -0000 @@ -216,6 +216,9 @@ ata_completed(request, 0); } else { + if (!dumping) + callout_reset(&request->callout, request->timeout * hz, + (timeout_t*)ata_timeout, request); if (request->bio && !(request->flags & ATA_R_TIMEOUT)) { ATA_DEBUG_RQ(request, "finish bio_taskqueue"); bio_taskqueue(request->bio, (bio_task_t *)ata_completed, request); -- -Søren From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 04:07:47 2004 Return-Path: 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 7C62716A4CE for ; Fri, 19 Nov 2004 04:07:47 +0000 (GMT) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 059E943D2F for ; Fri, 19 Nov 2004 04:07:46 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw503.dsto.defence.gov.au (ednmsw503.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id iAJ46jZg026032 for ; Fri, 19 Nov 2004 14:36:45 +1030 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw503.dsto.defence.gov.au for ; Fri, 19 Nov 2004 14:37:36 +1030 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81])iAJ44Ih19636 for ; Fri, 19 Nov 2004 14:34:18 +1030 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id RZJDSY3L; Fri, 19 Nov 2004 14:34:06 +1030 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) iAJ44Ign000972 for ; Fri, 19 Nov 2004 14:34:18 +1030 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost)iAJ44IpJ000971 for freebsd-current@freebsd.org; Fri, 19 Nov 2004 14:34:18 +1030 (CST) (envelope-from wilkinsa) Date: Fri, 19 Nov 2004 14:34:18 +1030 From: "Wilkinson, Alex" To: freebsd-current@freebsd.org Message-ID: <20041119040417.GC768@squash.dsto.defence.gov.au> Mail-Followup-To: freebsd-current@freebsd.org References: <419CEFB9.7060604@DeepCore.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <419CEFB9.7060604@DeepCore.dk> User-Agent: Mutt/1.5.6i Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 04:07:47 -0000 Soren, I know that TCQ stands for 'Tagged Command Queing', but how about NCQ ? And how does one find out if their SATA disk is really using a PATA-SATA converter chip ? smartmon ? - aW 0n Thu, Nov 18, 2004 at 07:53:45PM +0100, Søren Schmidt wrote: Maseed wrote: [SNIP] >I have to point out in the above e-mail that the problem is not just >confined to the 36GB Raptor, which might be a PATA drive with a Marvel >chip to make it work with SATA drives, but it also plages *real* >native SATA drives as well, since the 74GB Western Digital Raptor I >have is a true SATA150 drive with TCQ. Correction, the 74GB Raptor is still not a pure or native SATA device, it still uses the marvell PATA-SATA converter chip. Its true that it supports TCQ but thats the same old way as the IBM deathstars used, and not directly comaprable to the new true SATA NCQ way of things. >Anyhow, I am wondering if this issue has been resolved yet or not, >either in FreeBSD-current or 5.3-RELEASE-px. I don't want to discard >my current OS to install FreeBSD only to find out that the problem is >still there. If any sort of error logs or dmesg output is required by >a potential developer from this setup of mine, I'll go so far as to >resize my partition and install FreeBSD 5.3 and provide them, but the >reason why I'm hesitant in doing that is the fact that I run a >web-server on my computer that cannot stay down for long, as some >friends of mine depend on it. If you want 24/7 uptime, you *really* should be bying hardware of a quality that matches that, the SiI3112 is *not* in that league, not even close. -- -Søren _______________________________________________ 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 Fri Nov 19 04:51:28 2004 Return-Path: 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 CDD3916A4CE for ; Fri, 19 Nov 2004 04:51:28 +0000 (GMT) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F07B43D53 for ; Fri, 19 Nov 2004 04:51:28 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iAJ4pKl0026169; Thu, 18 Nov 2004 23:51:22 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <419D145E.8090108@DeepCore.dk> References: <419CEFB9.7060604@DeepCore.dk> <419D145E.8090108@DeepCore.dk> Date: Thu, 18 Nov 2004 23:51:19 -0500 To: =?iso-8859-1?Q?S=F8ren?= Schmidt From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: Maseed cc: freebsd-current@freebsd.org Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 04:51:29 -0000 At 10:30 PM +0100 11/18/04, S=F8ren Schmidt wrote: >Garance A Drosihn wrote: > >>I am trying to pin down problems "FAILURE - WRITE_DMA timed out" >>in a new PC that I have. I had some local shop build this for me, >>and apparently there were "a few" miscommunications in what I >>thought I asked for, and what they actually built. >> >>The machine ended up with two SATA controllers: >> atapci0: -- on the motherboard >> atapci1: -- on a PCI card > >I think its the other way around, the VIA chip is part of the >motherboard chipset, the SiI is a "loose" PCI compatible chip. Ugh. You are correct. Somewhere along the line I got the two mixed up. So now have I removed the PCI-based SATA card, and connected the Western Digital hard disk to the on-board SATA. I have just done a complete buildworld/installworld cycle for 5.3-STABLE. I did not see a single WRITE_DMA time-out message. I was *always* seeing at least a few of those before, especially if I specified -j2 (or more) on a `make buildworld'. Many times those messages were benign, but sometimes they would trigger a failure in buildworld, or even more severe problems (including system panics -- which would then leave the file system in a corrupted state...). >>The hard disk is connected to the PCI card. Would that be >>more reliable quality hardware than the SiI3112? > >I'd say so. You are obviously correct... Now I will have to go to the place that built this, and ask them why on earth they added a PCI card for SATA which was *worse* than what was on the motherboard! When I ordered this, I expected it to use the on-board SATA. I never asked for a SATA card. >>Also, the disk is a Western Digital WDC WD1200JD-00GBB0/02.05D02 >>120-gig drive. I *thought* I was ordering a Seagate drive, but it is >>quite likely that there was some confusion on that. Would that Western >>Digital SATA drive be a problem? I do have a Seagate Barracuda 7200.7 >>hard drive that I could use (after shuffling a few things around). > >From observation I'd say that those drives that are native SATA >devices has significantly less problems than those that aren't. Well, I am sure that is a true statement, but it does not answer the question I was trying to ask... :-) I did not know anything about this western digital drive that I ended up with, so I didn't know if it was a native SATA drive. But looking around the web for awhile, it looks like this model of Western Digital is not a native SATA drive. So I think I will replace it just to avoid any further hassles, even though I did not get any errors with this drive once I was using the right controller. I had *intended* to get a Seagate SATA drive in the first place, so swamping the drive will just get me back to what my original plans for hardware. Thanks. Now that I may finally be past these hardware problems, maybe I can get back to writing some actual code! -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 05:17:53 2004 Return-Path: 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 1466216A4CE; Fri, 19 Nov 2004 05:17:53 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5A1A43D1F; Fri, 19 Nov 2004 05:17:52 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id iAJ5HiZc022530; Fri, 19 Nov 2004 00:17:45 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: <26249.1100342074@critter.freebsd.dk> <4195E5DB.2070302@DeepCore.dk> Date: Fri, 19 Nov 2004 00:17:43 -0500 To: "Zoltan Frombach" , =?iso-8859-1?Q?S=F8ren?= Schmidt , "Poul-Henning Kamp" From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 05:17:53 -0000 At 7:33 PM -0800 11/18/04, Zoltan Frombach wrote: >For your information, I applied this patch just now to my kernel. >Sorry about the delay! I will send an update in a few days once I >see if those DMA_WRITE warnings are still happening or not. For those who may have missed my other message, it looks like all of my problems were related to a PCI-based SATA controller which was added by the store that built my machine. This card was added even though I had selected a motherboard with on-board SATA. The problem controller was a: and it has been causing me enough problems that I couldn't get through a buildworld to even try the suggested patch. I have now switched to the on-board: and so far I have not seen any more of these WRITE_DMA messages. None. And I have been pounding the disk pretty hard with a variety of work for a few hours now. So, now there is no point in me adding the patch, because I no longer see the message! It would still be nice if FreeBSD would react better to whatever problems this card causes. I still have this stupid card, and I would be happy to mail it off to anyone who might want to debug the problems with it. And if we *can't* fix it, then maybe we should just remove support for it. I have had to rebuild my freebsd partitions several times now due to these problems, and certainly that wasn't much fun. Although I guess my problems might also be partially due to the Western Digital drive I was using, when it is used in combination with this card. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 07:59:28 2004 Return-Path: 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 4C30F16A4CF for ; Fri, 19 Nov 2004 07:59:28 +0000 (GMT) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 60F1443D46 for ; Fri, 19 Nov 2004 07:59:27 +0000 (GMT) (envelope-from pho@holm.cc) Received: (qmail 40111 invoked from network); 19 Nov 2004 07:59:26 -0000 Received: from unknown (HELO peter.osted.lan) (unknown) by unknown with SMTP; 19 Nov 2004 07:59:26 -0000 X-pair-Authenticated: 80.164.63.199 Received: from peter.osted.lan (localhost.osted.lan [127.0.0.1]) by peter.osted.lan (8.13.1/8.13.1) with ESMTP id iAJ7xPLj022354; Fri, 19 Nov 2004 08:59:25 +0100 (CET) (envelope-from pho@peter.osted.lan) Received: (from pho@localhost) by peter.osted.lan (8.13.1/8.13.1/Submit) id iAJ7xPWX022353; Fri, 19 Nov 2004 08:59:25 +0100 (CET) (envelope-from pho) Date: Fri, 19 Nov 2004 08:59:24 +0100 From: Peter Holm To: John Baldwin Message-ID: <20041119075924.GA22320@peter.osted.lan> References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200411151546.15533.jhb@FreeBSD.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@FreeBSD.org Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 07:59:28 -0000 On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: > On Friday 12 November 2004 07:33 am, Peter Holm wrote: > > GENERIC HEAD from Nov 11 08:05 UTC > > > > The following stack traces etc. was done before my first > > cup of coffee, so it's not so informative as it could have been :-( > > > > The test box appeared to have been frozen for more than 6 hours, > > but was pingable. > > > > http://www.holm.cc/stress/log/cons86.html > > A weak guess is that you have the system in some sort of livelock due to > fork()? Have you tried running with 'debug.mpsafevm=1' set from the loader? > > -- > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > "Power Users Use the Power to Serve" = http://www.FreeBSD.org OK, I've got some more info: http://www.holm.cc/stress/log/cons88.html Looks like a spin in uma_zone_slab() when slab_zalloc() fails? -- Peter Holm From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 08:03:33 2004 Return-Path: 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 588C116A4CE for ; Fri, 19 Nov 2004 08:03:33 +0000 (GMT) Received: from mail.ciam.ru (mail.ciam.ru [213.147.57.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D647443D4C for ; Fri, 19 Nov 2004 08:03:32 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from ppp83-237-164-98.pppoe.mtu-net.ru ([83.237.164.98]) by mail.ciam.ru with esmtpa (Exim 4.x) id 1CV3jo-000Fog-8p; Fri, 19 Nov 2004 11:03:26 +0300 Message-ID: <419DA8D1.3090702@FreeBSD.org> Date: Fri, 19 Nov 2004 11:03:29 +0300 From: Sergey Matveychuk User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Anish Mistry , current@freebsd.org References: <419B2B01.9050803@FreeBSD.org> <200411170651.17091.mistry.7@osu.edu> In-Reply-To: <200411170651.17091.mistry.7@osu.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 2.9 (++) X-Spam-Report: Spam detection software, running on the system "proxy.ciam.ru", hasmessagelabel similar future email. If you have any questions, see the administrator of that system for details. Content preview: Anish Mistry wrote: >On Wednesday 17 November 2004 05:42 am, Sergey Matveychuk wrote: >> I've bought a KVM switch (2computers->1display,mouse,keyboard(PS/2 >> both)). It has one USB output (Windows sees USB mouse and USB keyboard). > > The patch I posted here should fix your problem: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/63837 > [...] Content analysis details: (2.9 points, 5.0 required) pts rule name description --------------------------------------------------addr 1)address [83.237.164.98 listed in dnsbl.sorbs.net] Subject: Re: two devices on one USB channel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 08:03:33 -0000 Anish Mistry wrote: >On Wednesday 17 November 2004 05:42 am, Sergey Matveychuk wrote: >> I've bought a KVM switch (2computers->1display,mouse,keyboard(PS/2 >> both)). It has one USB output (Windows sees USB mouse and USB keyboard). > > The patch I posted here should fix your problem: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/63837 > I've tried both patch from the PR, but both do not help me. Nothing changed when I've applied the patches. -- Sem. From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 08:12:18 2004 Return-Path: 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 DF7A416A4CE; Fri, 19 Nov 2004 08:12:18 +0000 (GMT) Received: from caine.easynet.fr (smarthost161.mail.easynet.fr [212.180.1.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15D1E43D53; Fri, 19 Nov 2004 08:12:18 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by caine.easynet.fr with esmtp (Exim 4.34) id 1CV3sL-0003jy-Fr; Fri, 19 Nov 2004 09:12:13 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id 6AD80408E; Fri, 19 Nov 2004 09:09:57 +0100 (CET) Date: Fri, 19 Nov 2004 09:09:57 +0100 From: Jeremie Le Hen To: Shunsuke SHINOMIYA Message-ID: <20041119080957.GL69710@obiwan.tataz.chchile.org> References: <20041118124902.GC75559@freebie.xs4all.nl> <200411182131.iAILVJ1T032003@apollo.backplane.com> <20041119114233.C43B.SHINO@fornext.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041119114233.C43B.SHINO@fornext.org> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 08:12:19 -0000 > if you suppose your computer has sufficient performance, please try to > disable or adjust parameters of Interrupt Moderation of em. Nice ! It would be even better if there was a boot-time sysctl to configure the behaviour of this feature, or something like ifconfig link0 option of the fxp(4) driver. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 08:17:37 2004 Return-Path: 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 5015016A4CE; Fri, 19 Nov 2004 08:17:37 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4EA743D55; Fri, 19 Nov 2004 08:17:36 +0000 (GMT) (envelope-from philip@nixsys.be) Received: from loge.nixsys.be (loge.nixsys.be [195.144.77.45]) by gateway.nixsys.be (Postfix) with ESMTP id 3B76F200; Fri, 19 Nov 2004 09:17:35 +0100 (CET) Received: from loge.nixsys.be (philip@localhost [127.0.0.1]) by loge.nixsys.be (8.13.1/8.13.1) with ESMTP id iAJ8HYNX000983; Fri, 19 Nov 2004 09:17:34 +0100 (CET) (envelope-from philip@loge.nixsys.be) Received: (from philip@localhost) by loge.nixsys.be (8.13.1/8.13.1/Submit) id iAJ8HYFs000982; Fri, 19 Nov 2004 09:17:34 +0100 (CET) (envelope-from philip) Date: Fri, 19 Nov 2004 09:17:34 +0100 From: Philip Paeps To: Giorgos Keramidas Message-ID: <20041119081734.GC676@loge.nixsys.be> Mail-Followup-To: Giorgos Keramidas , freebsd-current@freebsd.org References: <20041118164356.GA46185@orion.daedalusnetworks.priv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041118164356.GA46185@orion.daedalusnetworks.priv> X-Date-in-Rome: ante diem XIII Kalendas Decembres MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 08:17:37 -0000 On 2004-11-18 18:43:56 (+0200), Giorgos Keramidas wrote: > The screen-4.0.2 version that misc/screen installs is apparently the latest > version of screen available. It also contains a zillion bugs, is written in > a very insecure style, it uses an antiquated version of autoconf script, > etc. Unrelated, perhaps, but has anyone else noticed that on sparc64, the date stuck in utmp seems to always be '19700101': | (philip@wotan)~% w | 9:16am up 7 days, 7:52, 1 user, load averages: 0.08, 0.02, 0.01 | USER TTY FROM LOGIN@ IDLE WHAT | philip p1 loge:S.0 01Jan70 - w I've not seen this happen on any other platforms... - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. The speed of an oncoming vehicle is directly proportional to the length of the passing zone. From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 08:32:41 2004 Return-Path: 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 A34F616A4D0 for ; Fri, 19 Nov 2004 08:32:41 +0000 (GMT) Received: from mx.nsu.ru (mx.nsu.ru [212.192.164.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FE4943D5C for ; Fri, 19 Nov 2004 08:32:40 +0000 (GMT) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.34) id 1CV4F8-0007SW-Ko; Fri, 19 Nov 2004 14:35:46 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.13.1/8.13.1) with ESMTP id iAJ8WooP050240; Fri, 19 Nov 2004 14:32:50 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.13.1/8.13.1/Submit) id iAJ8Wm8F050192; Fri, 19 Nov 2004 14:32:48 +0600 (NOVT) (envelope-from danfe) Date: Fri, 19 Nov 2004 14:32:48 +0600 From: Alexey Dokuchaev To: Kris Kennaway Message-ID: <20041119083248.GA48756@regency.nsu.ru> References: <20041115120355.GA74977@regency.nsu.ru> <20041117161215.GA84085@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041117161215.GA84085@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: current@freebsd.org Subject: Re: 6-CURRENT, threads, hangs are still there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 08:32:41 -0000 On Wed, Nov 17, 2004 at 08:12:15AM -0800, Kris Kennaway wrote: > On Mon, Nov 15, 2004 at 06:03:55PM +0600, Alexey Dokuchaev wrote: > > Hello there, > > > > Updated world + kernel on Nov 12. Sticking to ULE + PREEMPTION + DEBUG > > STUFF in kernel. Running sim, psi, xmms, mozilla etc. hangs on startup, > > unless `libpthread' mapped to `libc_r' via /etc/libmap.conf. > > GDB is unable to attach, process is unkillable even with SIGKILL. > > Very reproducible. CPU: Intel 2.8GHz, HTT enabled. > > > > Does anyone have a clue on this? Using ULE on purpose to help hunt down > > its bugs. What debugging info can/should I get? > > You should try with 4BSD too to see if it's a bug in ULE, or in > generic parts of the kernel. 4BSD + PREEMPTION works fine, so it looks like this is ULE problem. ./danfe From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 08:51:19 2004 Return-Path: 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 2DD3816A4CE for ; Fri, 19 Nov 2004 08:51:19 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5990343D5C for ; Fri, 19 Nov 2004 08:51:18 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.gr (patr530-b126.otenet.gr [212.205.244.134]) iAJ8pFda027689 for ; Fri, 19 Nov 2004 10:51:16 +0200 Received: from gothmog.gr (gothmog [127.0.0.1]) by gothmog.gr (8.13.1/8.13.1) with ESMTP id iAJ8osCN084118 for ; Fri, 19 Nov 2004 10:50:54 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.gr (8.13.1/8.13.1/Submit) id iAJ8osKP084117 for freebsd-current@freebsd.org; Fri, 19 Nov 2004 10:50:54 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Fri, 19 Nov 2004 10:50:54 +0200 From: Giorgos Keramidas To: freebsd-current@freebsd.org Message-ID: <20041119085054.GB83736@gothmog.gr> References: <20041118164356.GA46185@orion.daedalusnetworks.priv> <20041119081734.GC676@loge.nixsys.be> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041119081734.GC676@loge.nixsys.be> Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 08:51:19 -0000 On 2004-11-19 09:17, Philip Paeps wrote: > On 2004-11-18 18:43:56 (+0200), Giorgos Keramidas wrote: > > The screen-4.0.2 version that misc/screen installs is apparently the latest > > version of screen available. It also contains a zillion bugs, is written in > > a very insecure style, it uses an antiquated version of autoconf script, > > etc. > > Unrelated, perhaps, but has anyone else noticed that on sparc64, the date > stuck in utmp seems to always be '19700101': I'll have a look later today and this weekend to the utmp handling of screen. It may be just a bug that shows up on 64-bit architectures. > | (philip@wotan)~% w > | 9:16am up 7 days, 7:52, 1 user, load averages: 0.08, 0.02, 0.01 > | USER TTY FROM LOGIN@ IDLE WHAT > | philip p1 loge:S.0 01Jan70 - w > > I've not seen this happen on any other platforms... Does anyone on amd64 use screen to see if this happens there too? From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:00:23 2004 Return-Path: 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 5D2DB16A4CE for ; Fri, 19 Nov 2004 09:00:23 +0000 (GMT) Received: from mail19.syd.optusnet.com.au (mail19.syd.optusnet.com.au [211.29.132.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0405A43D31 for ; Fri, 19 Nov 2004 09:00:22 +0000 (GMT) (envelope-from fbsd-current@mawer.org) Received: from c211-30-90-140.belrs3.nsw.optusnet.com.au (c211-30-95-252.belrs3.nsw.optusnet.com.au [211.30.95.252]) iAJ90K8X016404 for ; Fri, 19 Nov 2004 20:00:20 +1100 Received: (qmail 57256 invoked from network); 19 Nov 2004 09:00:20 -0000 Received: from unknown (HELO ?10.1.1.1?) (unknown) by unknown with SMTP; 19 Nov 2004 09:00:20 -0000 Message-ID: <419DB630.6060402@mawer.org> Date: Fri, 19 Nov 2004 20:00:32 +1100 From: Antony Mawer User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Holm References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> <20041119075924.GA22320@peter.osted.lan> In-Reply-To: <20041119075924.GA22320@peter.osted.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@FreeBSD.org cc: John Baldwin Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:00:23 -0000 On 19/11/2004 6:59 PM, Peter Holm wrote: > On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: >>On Friday 12 November 2004 07:33 am, Peter Holm wrote: >>>GENERIC HEAD from Nov 11 08:05 UTC >>> >>>The following stack traces etc. was done before my first >>>cup of coffee, so it's not so informative as it could have been :-( >>> >>>The test box appeared to have been frozen for more than 6 hours, >>>but was pingable. >>> >>>http://www.holm.cc/stress/log/cons86.html >> >>A weak guess is that you have the system in some sort of livelock due to >>fork()? Have you tried running with 'debug.mpsafevm=1' set from the loader? > > OK, I've got some more info: > > http://www.holm.cc/stress/log/cons88.html > > Looks like a spin in uma_zone_slab() when slab_zalloc() fails? I thought that sounded vaguely familiar -- not sure if it's relevant but I did see that Lukas (le@) had pointed to freezes that looked to be in the similar area (going off the backtrace he posted). I haven't looked into it at all but thought it might be relevant to someone looking at the issue: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=413571+0+current/freebsd-stable Cheers Antony From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:20:58 2004 Return-Path: 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 D65C716A4CE; Fri, 19 Nov 2004 09:20:58 +0000 (GMT) Received: from eddie.nitro.dk (port324.ds1-khk.adsl.cybercity.dk [212.242.113.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3190043D31; Fri, 19 Nov 2004 09:20:58 +0000 (GMT) (envelope-from simon@eddie.nitro.dk) Received: by eddie.nitro.dk (Postfix, from userid 1000) id 79C04119CD9; Fri, 19 Nov 2004 10:20:56 +0100 (CET) Date: Fri, 19 Nov 2004 10:20:56 +0100 From: "Simon L. Nielsen" To: Giorgos Keramidas Message-ID: <20041119092055.GA86796@eddie.nitro.dk> References: <20041118164356.GA46185@orion.daedalusnetworks.priv> <20041119081734.GC676@loge.nixsys.be> <20041119085054.GB83736@gothmog.gr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sm4nu43k4a2Rpi4c" Content-Disposition: inline In-Reply-To: <20041119085054.GB83736@gothmog.gr> User-Agent: Mutt/1.5.6i cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:20:59 -0000 --sm4nu43k4a2Rpi4c Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2004.11.19 10:50:54 +0200, Giorgos Keramidas wrote: > On 2004-11-19 09:17, Philip Paeps wrote: > > | (philip@wotan)~% w > > | 9:16am up 7 days, 7:52, 1 user, load averages: 0.08, 0.02, 0.01 > > | USER TTY FROM LOGIN@ IDLE WHAT > > | philip p1 loge:S.0 01Jan70 - w > > > > I've not seen this happen on any other platforms... >=20 > Does anyone on amd64 use screen to see if this happens there too? I just tried to install screen on a FreeBSD/amd64 and it seems to work as expected (with the correct login date). --=20 Simon L. Nielsen --sm4nu43k4a2Rpi4c Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBnbr3h9pcDSc1mlERAjwCAJ9UhXxb0fzxz3G4fRjvF2RnrdozRwCguWyQ nkpcw6B/o/ILQljXKr/XaH4= =rwXl -----END PGP SIGNATURE----- --sm4nu43k4a2Rpi4c-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:38:00 2004 Return-Path: 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 7F8DE16A4CE; Fri, 19 Nov 2004 09:38:00 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C50B943D1D; Fri, 19 Nov 2004 09:37:59 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id iAJ9bvaU076634; Fri, 19 Nov 2004 10:37:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org, current@freebsd.org From: Poul-Henning Kamp Date: Fri, 19 Nov 2004 10:37:57 +0100 Message-ID: <76633.1100857077@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Subject: [REVIEW/TEST] nanodelay() vs DELAY() X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:38:00 -0000 A number of device drivers need to have predictable small delays and today they largely rely on DELAY() for that. Problem is, DELAY sucks for durations below 10-20 usec. I have written a first cut of a self-calibrating nanodelay() which is better three orders of magnitude further down. The patch can be found at in p4::phk_dev or http://phk.freebsd.dk/patch/nanodelay.patch nanodelay() takes a nanosecond argument and will try to sleep exactly that many nanoseconds but never less than that. With a primed cache, the performance is close to perfect from 200nsec and up, and below that it depends a lot on the speed of the machine. Without a primed cache, an unpredictable jitter will be superimposed on the delay duration. Here is a plot which shows how DELAY() and nanodelay() perform on two of my test-machines: http://phk.freebsd.dk/misc/nanodelay.png I would appreciate if driver writers could play with this and see if makes any difference anywhere. Please notice that this is a timed cpu-spin, it does not allow another thread to use the CPU, so it should only be used for short (< 1/hz) delays. How it works: A default routine spins on the timecounter using nanouptime(). How well this works depends on which timecounter we use, but in general we can trust it to be OK above a few microseconds. An array contains function+arg to use for delays less than 8 usec, for longer delays the timecounter routine is always called. Each bucket in the array spans 8 nanoseconds, so delays of 0-7 nanoseconds use bucket 0, 8-15 nsec use bucket 1 etc. A number of cpu based spin routines are calibrated against the timecounter for various argument values and plugged into the array accordingly. The array takes up 9000 bytes on 32 bit and 17000 on 64 bit. This can be reduced at the cost of reduced precision in nanodelay(), we need to determine the correct tradeoff there. -- 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 Fri Nov 19 09:47:42 2004 Return-Path: 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 A1E3016A4CE for ; Fri, 19 Nov 2004 09:47:42 +0000 (GMT) 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 F407A43D62 for ; Fri, 19 Nov 2004 09:47:41 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [172.18.2.1] (axiell-gw1.novi.dk [130.225.63.24]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id iAJ9lWom008495; Fri, 19 Nov 2004 10:47:34 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <419DC132.2000707@DeepCore.dk> Date: Fri, 19 Nov 2004 10:47:30 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 0.7.2 (X11/20040802) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Wilkinson, Alex" References: <419CEFB9.7060604@DeepCore.dk> <20041119040417.GC768@squash.dsto.defence.gov.au> In-Reply-To: <20041119040417.GC768@squash.dsto.defence.gov.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: freebsd-current@freebsd.org Subject: Re: sil3112a SATA Controller, current status X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:47:42 -0000 Wilkinson, Alex wrote: > Soren, I know that TCQ stands for 'Tagged Command Queing',=20 > but how about NCQ ? NCQ =3D Native Command Queueing, semilar to TCQ but with different=20 commands and sematics, still limitted to 32 tags. IIRC there is no "bus=20 release" cycle in NCQ as SATA only has one device pr chain (well, as=20 long as you dont use port multipliers that is). > And how does one find out if their SATA disk is really using a > PATA-SATA converter chip ? smartmon ? Either by asking then vendor or by visual inspection, you cannot tell pr = software, at least not in any reliable way AFAIK. --=20 -S=F8ren From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:50:55 2004 Return-Path: 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 25D9F16A4CE; Fri, 19 Nov 2004 09:50:55 +0000 (GMT) Received: from aiolos.otenet.gr (aiolos.otenet.gr [195.170.0.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 510AC43D5C; Fri, 19 Nov 2004 09:50:54 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from orion.daedalusnetworks.priv (aris.bedc.ondsl.gr [62.103.39.226])iAJ9oqDj011941; Fri, 19 Nov 2004 11:50:52 +0200 Received: from orion.daedalusnetworks.priv (orion [127.0.0.1]) iAJ9orDw001036; Fri, 19 Nov 2004 11:50:53 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost)iAJ9orXY001035; Fri, 19 Nov 2004 11:50:53 +0200 (EET) (envelope-from keramida@freebsd.org) Date: Fri, 19 Nov 2004 11:50:52 +0200 From: Giorgos Keramidas To: "Simon L. Nielsen" Message-ID: <20041119095052.GA1008@orion.daedalusnetworks.priv> References: <20041118164356.GA46185@orion.daedalusnetworks.priv> <20041119081734.GC676@loge.nixsys.be> <20041119085054.GB83736@gothmog.gr> <20041119092055.GA86796@eddie.nitro.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041119092055.GA86796@eddie.nitro.dk> cc: freebsd-current@freebsd.org Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:50:55 -0000 On 2004-11-19 10:20, "Simon L. Nielsen" wrote: >On 2004.11.19 10:50:54 +0200, Giorgos Keramidas wrote: >>On 2004-11-19 09:17, Philip Paeps wrote: >>> | (philip@wotan)~% w >>> | 9:16am up 7 days, 7:52, 1 user, load averages: 0.08, 0.02, 0.01 >>> | USER TTY FROM LOGIN@ IDLE WHAT >>> | philip p1 loge:S.0 01Jan70 - w >>> >>> I've not seen this happen on any other platforms... >> >> Does anyone on amd64 use screen to see if this happens there too? > > I just tried to install screen on a FreeBSD/amd64 and it seems to work > as expected (with the correct login date). Hmmm, nice to know. Thanks :-) From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 09:53:03 2004 Return-Path: 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 4615616A4CE; Fri, 19 Nov 2004 09:53:03 +0000 (GMT) Received: from hotmail.com (bay2-dav7.bay2.hotmail.com [65.54.246.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 165FE43D5C; Fri, 19 Nov 2004 09:53:03 +0000 (GMT) (envelope-from tssajo@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 19 Nov 2004 01:53:01 -0800 Message-ID: Received: from 24.24.201.219 by BAY2-DAV7.phx.gbl with DAV; Fri, 19 Nov 2004 09:52:25 +0000 X-Originating-IP: [24.24.201.219] X-Originating-Email: [tssajo@hotmail.com] X-Sender: tssajo@hotmail.com From: "Zoltan Frombach" To: =?iso-8859-1?Q?S=F8ren_Schmidt?= , "Poul-Henning Kamp" , "Garance A Drosihn" References: <26249.1100342074@critter.freebsd.dk> <4195E5DB.2070302@DeepCore.dk> Date: Fri, 19 Nov 2004 01:52:27 -0800 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-OriginalArrivalTime: 19 Nov 2004 09:53:01.0559 (UTC) FILETIME=[8EA24870:01C4CE1D] cc: freebsd-current@freebsd.org cc: Robert Watson Subject: Re: 5.3-RELEASE: WARNING - WRITE_DMA interrupt timout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 09:53:03 -0000 My problem is not related to a SATA controller. I use the onboard UDMA133 controller (pretty rare) with a Maxtor UDMA133 drive. It is a new ABIT motherboard that uses SiS chipset. The hard drive is not new, but previously I used it in UDMA100 mode only, with another motherboard. See: atapci0: port 0x4000-0x400f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 2.5 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ad0: 78167MB [158816/16/63] at ata0-master UDMA133 Everything works pretty well on this server. Except that these DMA_WRITE warning messages make me worrying. However, I was not getting too many of them lately, and none since I installed Soren's patch a few hours ago. I also figured out why my system became so unresponsive at times. I host about 150 domains on this server, with email and everything. I use qmail as the MTA, and by default it accepts all email on all hosted domains, even when the mail is addressed to a non-existing user. It will try to bounce those messages but only later in the process. IMO, it is very poor design of the qmail MTA, an otherwise pretty powerful email program. I also use qmail-scanner with clamav and spamassassin. The qmail-scanner program and spamassassin are written in Perl. So every single message that qmail accepts gets through qmail-scanner (and therefore gets through clamav and spamassassin as well), even the ones that are addressed to non-existing users... Some of the hosted domains at times get hit really hard with extensive spam and around that time the server becomes very unresponsive. Not surprisingly though, because according to my maillog, time to time some spammer send literally hundreds of junk mail to non-existing users, all within a few seconds of time. Right then the server comes to a crawl. Last time, I couldn't access any hosted web sites via HTTP nor FTP for minutes. It took me like 3 minutes to be able to get in via SSH because of the slowness. Finally I was able to see the reason: all those Perl processes scanning the junk mail... The server became a victim of a DOS attack caused by excessive spam. So I believe that this was the reason of the unresponsiveness. And it could be the reason why I received those DMA_WRITE warnings at those times! I'm not a 100% sure about it though, but I think it is possible. I'm going to apply a patch to qmail in a few days. That makes qmail to reject messages sent to unexsiting users immediately, so they won't need to get scanned. This way, I believe, I will greatly reduce the load caused by this flood of junk mail. Then hopefully these DMA_WARNING messages will be gone, too... We'll see. Zoltan > At 7:33 PM -0800 11/18/04, Zoltan Frombach wrote: >>For your information, I applied this patch just now to my kernel. >>Sorry about the delay! I will send an update in a few days once I >>see if those DMA_WRITE warnings are still happening or not. > > For those who may have missed my other message, it looks like all > of my problems were related to a PCI-based SATA controller which > was added by the store that built my machine. This card was added > even though I had selected a motherboard with on-board SATA. > > The problem controller was a: > and it has been causing me enough problems that I couldn't get > through a buildworld to even try the suggested patch. > > I have now switched to the on-board: > and so far I have not seen any more of these WRITE_DMA messages. > None. And I have been pounding the disk pretty hard with a > variety of work for a few hours now. So, now there is no point > in me adding the patch, because I no longer see the message! > > It would still be nice if FreeBSD would react better to whatever > problems this card causes. I still have this stupid card, and I > would be happy to mail it off to anyone who might want to debug the > problems with it. And if we *can't* fix it, then maybe we should > just remove support for it. I have had to rebuild my freebsd > partitions several times now due to these problems, and certainly > that wasn't much fun. Although I guess my problems might also be > partially due to the Western Digital drive I was using, when it is > used in combination with this card. > > -- > Garance Alistair Drosehn = gad@gilead.netel.rpi.edu > Senior Systems Programmer or gad@freebsd.org > Rensselaer Polytechnic Institute or drosih@rpi.edu From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 10:17:50 2004 Return-Path: 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 BC60616A4CE; Fri, 19 Nov 2004 10:17:50 +0000 (GMT) Received: from juniper.fornext.org (53.35.138.210.xn.2iij.net [210.138.35.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 17B9F43D2F; Fri, 19 Nov 2004 10:17:50 +0000 (GMT) (envelope-from shino@fornext.org) Received: from [127.0.0.1] (ariel.net.ss.titech.ac.jp [131.112.21.25]) by juniper.fornext.org (Postfix) with ESMTP id 2445F2A; Fri, 19 Nov 2004 19:17:48 +0900 (JST) Date: Fri, 19 Nov 2004 19:17:49 +0900 From: Shunsuke SHINOMIYA To: Jeremie Le Hen In-Reply-To: <20041119080957.GL69710@obiwan.tataz.chchile.org> References: <20041119114233.C43B.SHINO@fornext.org> <20041119080957.GL69710@obiwan.tataz.chchile.org> Message-Id: <20041119185315.C43D.SHINO@fornext.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="------_419DC28AC49304CD3548_MULTIPART_MIXED_" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.11.02 [ja] cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re[2]: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 10:17:50 -0000 --------_419DC28AC49304CD3548_MULTIPART_MIXED_ Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Hi, Jeremie, how is this? To disable Interrupt Moderation, sysctl hw.em?.int_throttle_valve=0. However, because this patch is just made now, it is not fully tested. > > if you suppose your computer has sufficient performance, please try to > > disable or adjust parameters of Interrupt Moderation of em. > > Nice ! It would be even better if there was a boot-time sysctl to > configure the behaviour of this feature, or something like ifconfig > link0 option of the fxp(4) driver. -- Shunsuke SHINOMIYA --------_419DC28AC49304CD3548_MULTIPART_MIXED_ Content-Type: application/octet-stream; name="if_em.diff" Content-Disposition: attachment; filename="if_em.diff" Content-Transfer-Encoding: base64 LS0tIGlmX2VtLmMtMS40NC4yLjMub3JpZwlUdWUgTm92ICA5IDA1OjA2OjE0IDIwMDQKKysrIGlm X2VtLmMJRnJpIE5vdiAxOSAxOTowMToxMSAyMDA0CkBAIC0xODIsNiArMTgyLDkgQEAgc3RhdGlj IGludCAgZW1fc3lzY3RsX2ludF9kZWxheShTWVNDVExfSAogc3RhdGljIHZvaWQgZW1fYWRkX2lu dF9kZWxheV9zeXNjdGwoc3RydWN0IGFkYXB0ZXIgKiwgY29uc3QgY2hhciAqLAogCQkJCSAgICBj b25zdCBjaGFyICosIHN0cnVjdCBlbV9pbnRfZGVsYXlfaW5mbyAqLAogCQkJCSAgICBpbnQsIGlu dCk7CisjaWYgMQorc3RhdGljIGludCBlbV9zeXNjdGxfdGhyb3R0bGVfdmFsdmUoU1lTQ1RMX0hB TkRMRVJfQVJHUyk7CisjZW5kaWYKIAogLyoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgogICogIEZyZWVCU0QgRGV2aWNl IEludGVyZmFjZSBFbnRyeSBQb2ludHMgICAgICAgICAgICAgICAgICAgIApAQCAtMzU4LDYgKzM2 MSwxMyBAQCBlbV9hdHRhY2goZGV2aWNlX3QgZGV2KQogCQkgICAgJmFkYXB0ZXItPnR4X2Fic19p bnRfZGVsYXksCiAJCSAgICBFMTAwMF9SRUdfT0ZGU0VUKCZhZGFwdGVyLT5odywgVEFEViksCiAJ CSAgICBlbV90eF9hYnNfaW50X2RlbGF5X2RmbHQpOworI2lmIDEKKwkJU1lTQ1RMX0FERF9QUk9D KCZhZGFwdGVyLT5zeXNjdGxfY3R4LAorCQkgICAgU1lTQ1RMX0NISUxEUkVOKGFkYXB0ZXItPnN5 c2N0bF90cmVlKSwgT0lEX0FVVE8sCisJCSAgICAiaW50X3Rocm90dGxlX3ZhbHZlIiwgQ1RMVFlQ RV9JTlR8Q1RMRkxBR19SVywKKwkJICAgIGFkYXB0ZXIsIDAsIGVtX3N5c2N0bF90aHJvdHRsZV92 YWx2ZSwgIklVIiwKKwkJICAgICJpbnRlcnJ1cHQgdGhyb3R0bGluZyByYXRlIik7CisjZW5kaWYK IAl9CiAgICAgICAKIAkvKiBQYXJhbWV0ZXJzICh0byBiZSByZWFkIGZyb20gdXNlcikgKi8gICAK QEAgLTQwMyw2ICs0MTMsMTAgQEAgZW1fYXR0YWNoKGRldmljZV90IGRldikKIAkgKi8KIAlhZGFw dGVyLT5ody5yZXBvcnRfdHhfZWFybHkgPSAxOwogCisjaWYgMQorI2RlZmluZSBNQVhfSU5UU19Q RVJfU0VDICAgICAgICA4MDAwCisJYWRhcHRlci0+dGhyb3R0bGVfdmFsdmUgPSBNQVhfSU5UU19Q RVJfU0VDOworI2VuZGlmCiAKIAlpZiAoZW1fYWxsb2NhdGVfcGNpX3Jlc291cmNlcyhhZGFwdGVy KSkgewogCQlwcmludGYoImVtJWQ6IEFsbG9jYXRpb24gb2YgUENJIHJlc291cmNlcyBmYWlsZWRc biIsIApAQCAtMjYwOCwxMiArMjYyMiwxNiBAQCBlbV9pbml0aWFsaXplX3JlY2VpdmVfdW5pdChz dHJ1Y3QgYWRhcHRlCiAJaWYoYWRhcHRlci0+aHcubWFjX3R5cGUgPj0gZW1fODI1NDApIHsKIAkJ RTEwMDBfV1JJVEVfUkVHKCZhZGFwdGVyLT5odywgUkFEViwKIAkJICAgIGFkYXB0ZXItPnJ4X2Fi c19pbnRfZGVsYXkudmFsdWUpOwotCisjaWYgMQorICAgICAgICAgICAgICAgIEUxMDAwX1dSSVRF X1JFRygmYWRhcHRlci0+aHcsIElUUiwKKwkJICAgIDEwMDAwMDAwMDAgLyAoYWRhcHRlci0+dGhy b3R0bGVfdmFsdmUgKiAyNTYpKTsKKyNlbHNlCiAgICAgICAgICAgICAgICAgLyogU2V0IHRoZSBp bnRlcnJ1cHQgdGhyb3R0bGluZyByYXRlLiAgVmFsdWUgaXMgY2FsY3VsYXRlZAogICAgICAgICAg ICAgICAgICAqIGFzIERFRkFVTFRfSVRSID0gMS8oTUFYX0lOVFNfUEVSX1NFQyAqIDI1Nm5zKSAq LwogI2RlZmluZSBNQVhfSU5UU19QRVJfU0VDICAgICAgICA4MDAwCiAjZGVmaW5lIERFRkFVTFRf SVRSICAgICAgICAgICAgIDEwMDAwMDAwMDAvKE1BWF9JTlRTX1BFUl9TRUMgKiAyNTYpCiAgICAg ICAgICAgICAgICAgRTEwMDBfV1JJVEVfUkVHKCZhZGFwdGVyLT5odywgSVRSLCBERUZBVUxUX0lU Uik7CisjZW5kaWYKICAgICAgICAgfSAgICAgICAKIAogCS8qIFNldHVwIHRoZSBCYXNlIGFuZCBM ZW5ndGggb2YgdGhlIFJ4IERlc2NyaXB0b3IgUmluZyAqLwpAQCAtMzM4Myw0ICszNDAxLDM1IEBA IGVtX2FkZF9pbnRfZGVsYXlfc3lzY3RsKHN0cnVjdCBhZGFwdGVyICoKIAkgICAgU1lTQ1RMX0NI SUxEUkVOKGFkYXB0ZXItPnN5c2N0bF90cmVlKSwKIAkgICAgT0lEX0FVVE8sIG5hbWUsIENUTFRZ UEVfSU5UfENUTEZMQUdfUlcsCiAJICAgIGluZm8sIDAsIGVtX3N5c2N0bF9pbnRfZGVsYXksICJJ IiwgZGVzY3JpcHRpb24pOworfQorCitzdGF0aWMgaW50CitlbV9zeXNjdGxfdGhyb3R0bGVfdmFs dmUoU1lTQ1RMX0hBTkRMRVJfQVJHUykKK3sKKwlzdHJ1Y3QgYWRhcHRlciAqYWRhcHRlcjsKKwlp bnQgZXJyb3I7CisJdV9pbnQzMl90IHZhbHZlOworCWludCBzOworCWludCB2YWx1ZTsKKworCWFk YXB0ZXIgPSAoc3RydWN0IGFkYXB0ZXIgKilhcmcxOworCXZhbHZlID0gIGFkYXB0ZXItPnRocm90 dGxlX3ZhbHZlOworCWVycm9yID0gc3lzY3RsX2hhbmRsZV9pbnQob2lkcCwgJnZhbHZlLCAwLCBy ZXEpOworCWlmIChlcnJvciAhPSAwIHx8IHJlcS0+bmV3cHRyID09IE5VTEwpCisJCXJldHVybiBl cnJvcjsKKwlhZGFwdGVyLT50aHJvdHRsZV92YWx2ZSA9IHZhbHZlOworCQorCXMgPSBzcGxpbXAo KTsKKworCS8qIFNldCB0aGUgaW50ZXJydXB0IHRocm90dGxpbmcgcmF0ZS4gIFZhbHVlIGlzIGNh bGN1bGF0ZWQKKwkgKiBhcyBJVFIgPSAxLyhJTlRTX1BFUl9TRUMgKiAyNTZucykgKi8KKwlpZih2 YWx2ZSA+IDApCisJCXZhbHVlID0gMTAwMDAwMDAwMC8odmFsdmUgKiAyNTYpOworCWVsc2UKKwkJ dmFsdWUgPSAwOworCUUxMDAwX1dSSVRFX1JFRygmYWRhcHRlci0+aHcsIElUUiwgdmFsdWUpOwor CisJc3BseChzKTsKKworCXJldHVybiAwOwogfQotLS0gaWZfZW0uaC0xLjI1LjIuMS5vcmlnCUZy aSBOb3YgMTkgMTk6MDA6MDMgMjAwNAorKysgaWZfZW0uaAlGcmkgTm92IDE5IDE4OjE4OjU3IDIw MDQKQEAgLTM1Myw2ICszNTMsOSBAQAogCXVfaW50MTZfdCAgICAgICBsaW5rX3NwZWVkOwogCXVf aW50MTZfdCAgICAgICBsaW5rX2R1cGxleDsKIAl1X2ludDMyX3QgICAgICAgc21hcnRzcGVlZDsK KyNpZiAxCisJdV9pbnQzMl90CXRocm90dGxlX3ZhbHZlOworI2VuZGlmCiAJc3RydWN0IGVtX2lu dF9kZWxheV9pbmZvIHR4X2ludF9kZWxheTsKIAlzdHJ1Y3QgZW1faW50X2RlbGF5X2luZm8gdHhf YWJzX2ludF9kZWxheTsKIAlzdHJ1Y3QgZW1faW50X2RlbGF5X2luZm8gcnhfaW50X2RlbGF5Owo= --------_419DC28AC49304CD3548_MULTIPART_MIXED_-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 11:39:50 2004 Return-Path: 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 E88F316A4CE; Fri, 19 Nov 2004 11:39:50 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id B843043D2D; Fri, 19 Nov 2004 11:39:50 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 707E75130D; Fri, 19 Nov 2004 03:43:17 -0800 (PST) Date: Fri, 19 Nov 2004 03:43:17 -0800 From: Kris Kennaway To: Alexey Dokuchaev Message-ID: <20041119114317.GA87532@xor.obsecurity.org> References: <20041115120355.GA74977@regency.nsu.ru> <20041117161215.GA84085@xor.obsecurity.org> <20041119083248.GA48756@regency.nsu.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <20041119083248.GA48756@regency.nsu.ru> User-Agent: Mutt/1.4.2.1i cc: jeff@FreeBSD.org cc: current@freebsd.org cc: Kris Kennaway Subject: Re: 6-CURRENT, threads, hangs are still there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 11:39:51 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 02:32:48PM +0600, Alexey Dokuchaev wrote: > On Wed, Nov 17, 2004 at 08:12:15AM -0800, Kris Kennaway wrote: > > On Mon, Nov 15, 2004 at 06:03:55PM +0600, Alexey Dokuchaev wrote: > > > Hello there, > > >=20 > > > Updated world + kernel on Nov 12. Sticking to ULE + PREEMPTION + DEB= UG > > > STUFF in kernel. Running sim, psi, xmms, mozilla etc. hangs on start= up, > > > unless `libpthread' mapped to `libc_r' via /etc/libmap.conf. > > > GDB is unable to attach, process is unkillable even with SIGKILL. > > > Very reproducible. CPU: Intel 2.8GHz, HTT enabled. > > >=20 > > > Does anyone have a clue on this? Using ULE on purpose to help hunt d= own > > > its bugs. What debugging info can/should I get? > >=20 > > You should try with 4BSD too to see if it's a bug in ULE, or in > > generic parts of the kernel. >=20 > 4BSD + PREEMPTION works fine, so it looks like this is ULE problem. OK, hopefully Jeff has time to look at this. Kris --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBndxVWry0BWjoQKURAv51AJ9OVPDqX/CPkLdKxjBE/ZvcYH9/vACgojtD aVJTjoHr0h2vzA5wN2CASVs= =q3O5 -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 11:49:46 2004 Return-Path: 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 8D61816A4CE; Fri, 19 Nov 2004 11:49:46 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C85A43D1D; Fri, 19 Nov 2004 11:49:46 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-68-250-184-205.dsl.wotnoh.ameritech.net [68.250.184.205]) (authenticated bits=0)iAJBU8UJ055139 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 19 Nov 2004 06:30:11 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Sergey Matveychuk Date: Fri, 19 Nov 2004 06:52:25 -0500 User-Agent: KMail/1.7 References: <419B2B01.9050803@FreeBSD.org> <200411170651.17091.mistry.7@osu.edu> <419DA8D1.3090702@FreeBSD.org> In-Reply-To: <419DA8D1.3090702@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4170704.LIQkOomnzK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411190652.34416.mistry.7@osu.edu> X-Spam-Status: No, hits=0.8 required=5.0 tests=BIZ_TLD autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-current@freebsd.org Subject: Re: two devices on one USB channel X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 11:49:46 -0000 --nextPart4170704.LIQkOomnzK Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 19 November 2004 03:03 am, you wrote: > Anish Mistry wrote: > >On Wednesday 17 November 2004 05:42 am, Sergey Matveychuk wrote: > > > >> I've bought a KVM switch (2computers->1display,mouse,keyboard(PS/2 > >> both)). It has one USB output (Windows sees USB mouse and USB > >> keyboard). > > > > The patch I posted here should fix your problem: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/63837 > > I've tried both patch from the PR, but both do not help me. Nothing > changed when I've applied the patches. How about this patch? http://am-productions.biz/docs/hid-update-part1.patch =2D-=20 Anish Mistry --nextPart4170704.LIQkOomnzK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnd6CxqA5ziudZT0RAsveAJ9Q3O59GX67NO1A02GA7e5/TDXcKgCgg2m7 MPoy7yYzGy1whUYBN5sKeWc= =AVzY -----END PGP SIGNATURE----- --nextPart4170704.LIQkOomnzK-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 12:03:28 2004 Return-Path: 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 6041416A4FF; Fri, 19 Nov 2004 12:03:28 +0000 (GMT) Received: from caine.easynet.fr (smarthost161.mail.easynet.fr [212.180.1.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 92AA843D2D; Fri, 19 Nov 2004 12:03:27 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from [212.180.127.72] (helo=tatooine.tataz.chchile.org) by caine.easynet.fr with esmtp (Exim 4.34) id 1CV7U0-0007pt-2M; Fri, 19 Nov 2004 13:03:20 +0100 Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id F09EB408F; Fri, 19 Nov 2004 13:01:03 +0100 (CET) Date: Fri, 19 Nov 2004 13:01:03 +0100 From: Jeremie Le Hen To: Shunsuke SHINOMIYA Message-ID: <20041119120102.GM69710@obiwan.tataz.chchile.org> References: <20041119114233.C43B.SHINO@fornext.org> <20041119080957.GL69710@obiwan.tataz.chchile.org> <20041119185315.C43D.SHINO@fornext.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041119185315.C43D.SHINO@fornext.org> User-Agent: Mutt/1.5.6i X-Broken-Reverse-DNS: no host name found for IP address 212.180.127.72 cc: freebsd-stable@freebsd.org cc: freebsd-current@freebsd.org cc: Jeremie Le Hen Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 12:03:28 -0000 > Hi, Jeremie, how is this? > To disable Interrupt Moderation, sysctl hw.em?.int_throttle_valve=0. Great, I would have called it "int_throttle_ceil", but that's a detail and my opinion is totally subjective. > However, because this patch is just made now, it is not fully tested. I'll give it a try this weekend although I won't be able to make performance mesurements. -- Jeremie Le Hen jeremie@le-hen.org From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 12:18:50 2004 Return-Path: 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 7AF4616A4CF for ; Fri, 19 Nov 2004 12:18:50 +0000 (GMT) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 515F643D5A for ; Fri, 19 Nov 2004 12:18:49 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 24872 invoked by uid 65534); 19 Nov 2004 12:18:48 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp022) with SMTP; 19 Nov 2004 13:18:48 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Fri, 19 Nov 2004 13:18:40 +0100 User-Agent: KMail/1.7 References: In-Reply-To: X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1648706.zu1aVHYG7D"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411191318.46405.Emanuel.Strobl@gmx.net> cc: freebsd-stable@freebsd.org cc: Robert Watson Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 12:18:50 -0000 --nextPart1648706.zu1aVHYG7D Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Donnerstag, 18. November 2004 13:27 schrieb Robert Watson: > On Wed, 17 Nov 2004, Emanuel Strobl wrote: > > I really love 5.3 in many ways but here're some unbelievable transfer =46irst, thanks a lot to all of you paying attention to my problem again. I'll use this as a cumulative answer to the many postings of you, first=20 answering Roberts questions and at the bottom those of the others. I changed cables and couldn't reproduce that bad results so I changed cable= s=20 back but also cannot reproduce them, especially the ggate write, formerly=20 with 2,6MB/s now performs at 15MB/s, but I haven't done any polling tests=20 anymore, just interrupt driven, since Matt explained that em doesn't benefi= t=20 of polling in any way. Results don't indicate a serious problem now but are still about a third of= =20 what I'd expected with my hardware. Do I really need Gigahertz Class CPUs t= o=20 transfer 30MB/s over GbE? > > I think the first thing you want to do is to try and determine whether the > problem is a link layer problem, network layer problem, or application > (file sharing) layer problem. Here's where I'd start looking: > > (1) I'd first off check that there wasn't a serious interrupt problem on > the box, which is often triggered by ACPI problems. Get the box to be > as idle as possible, and then use vmstat -i or stat -vmstat to see if > anything is spewing interrupts. Everything is fine > > (2) Confirm that your hardware is capable of the desired rates: typically > this involves looking at whether you have a decent card (most if_em > cards are decent), whether it's 32-bit or 64-bit PCI, and so on. For > unidirectional send on 32-bit PCI, be aware that it is not possible to > achieve gigabit performance because the PCI bus isn't fast enough, for > example. I'm aware that my 32bit/33MHz PCI bus is a "bottleneck", but I saw almost=20 80MByte/s running over the bus to my test-stripe-set (over the HPT372). So= =20 I'm pretty sure the system is good for 40MB/s ober the GbE line, which was= =20 sufficient for me. > > (3) Next, I'd use a tool like netperf (see ports collection) to establish > three characteristics: round trip latency from user space to user > space (UDP_RR), TCP throughput (TCP_STREAM), and large packet > throughput (UDP_STREAM). With decent boxes on 5.3, you should have no > trouble at all maxing out a single gig-e with if_em, assuming all is > working well hardware wise and there's no software problem specific to > your configuration. Please find the results on http://www.schmalzbauer.de/document.php?id=3D21 There is also a lot of additional information and more test results > > (4) Note that router latency (and even switch latency) can have a > substantial impact on gigabit performance, even with no packet loss, > in part due to stuff like ethernet flow control. You may want to put > the two boxes back-to-back for testing purposes. > I was aware of that and because of lacking a GbE switch anyway I decided to= =20 use a simple cable ;) > (5) Next, I'd measure CPU consumption on the end box -- in particular, use > top -S and systat -vmstat 1 to compare the idle condition of the > system and the system under load. > I additionally added these values to the netperf results. > If you determine there is a link layer or IP layer problem, we can start > digging into things like the error statistics in the card, negotiation > issues, etc. If not, you want to move up the stack to try and > characterize where it is you're hitting the performance issue. Am Donnerstag, 18. November 2004 17:53 schrieb M. Warner Losh: > In message: > > =A0 =A0 =A0 =A0 =A0 =A0 Robert Watson writes: > : (1) I'd first off check that there wasn't a serious interrupt problem on > : =A0 =A0 the box, which is often triggered by ACPI problems. =A0Get the = box to > : be as idle as possible, and then use vmstat -i or stat -vmstat to see if > : anything is spewing interrupts. > > Also, make sure that you aren't sharing interrupts between > GIANT-LOCKED and non-giant-locked cards. =A0This might be exposing bugs > in the network layer that debug.mpsafenet=3D0 might correct. =A0Just > noticed that our setup here has that setup, so I'll be looking into > that area of things. As you can see on the link above, no shared IRQs --nextPart1648706.zu1aVHYG7D Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBneSmBylq0S4AzzwRAkDcAJ40RoyPKUrK+40jHAcTfNqoj+mHvgCfSeNs f4mOm2aRdKjE2yN6spBoFJU= =R0oN -----END PGP SIGNATURE----- --nextPart1648706.zu1aVHYG7D-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 12:57:41 2004 Return-Path: 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 EB9D216A4CE; Fri, 19 Nov 2004 12:57:40 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84F1643D49; Fri, 19 Nov 2004 12:57:40 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAJCu5Wb093626; Fri, 19 Nov 2004 07:56:06 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)iAJCu5wa093623; Fri, 19 Nov 2004 12:56:05 GMT (envelope-from robert@fledge.watson.org) Date: Fri, 19 Nov 2004 12:56:05 +0000 (GMT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Emanuel Strobl In-Reply-To: <200411191318.46405.Emanuel.Strobl@gmx.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 12:57:41 -0000 On Fri, 19 Nov 2004, Emanuel Strobl wrote: > Am Donnerstag, 18. November 2004 13:27 schrieb Robert Watson: > > On Wed, 17 Nov 2004, Emanuel Strobl wrote: > > > I really love 5.3 in many ways but here're some unbelievable transfer > > First, thanks a lot to all of you paying attention to my problem again. > I'll use this as a cumulative answer to the many postings of you, first > answering Roberts questions and at the bottom those of the others. > > I changed cables and couldn't reproduce that bad results so I changed > cables back but also cannot reproduce them, especially the ggate write, > formerly with 2,6MB/s now performs at 15MB/s, but I haven't done any > polling tests anymore, just interrupt driven, since Matt explained that > em doesn't benefit of polling in any way. > > Results don't indicate a serious problem now but are still about a third > of what I'd expected with my hardware. Do I really need Gigahertz Class > CPUs to transfer 30MB/s over GbE? Well, the claim that if_em doesn't benefit from polling is inaccurate in the general case, but quite accurate in the specific case. In a box with multiple NIC's, using polling can make quite a big difference, not just by mitigating interrupt load, but also by helping to prioritize and manage the load, preventing live lock. As I indicated in my earlier e-mail, however, on your system it shouldn't make much difference -- 4k-8k interrupts/second is not a big deal, and quite normal for use of an if_em card in the interrupt-driven configuration. It looks like the netperf TCP test is getting just under 27MB/s, or 214Mb/s. That does seem on the low side for the PCI bus, but it's also instructive to look at the netperf UDP_STREAM results, which indicate that the box believes it is transmitting 417Mb/s but only 67Mb/s are being received or processed fast enough by netserver on the remote box. This means you've achieved a send rate to the card of about 54Mb/s. Note that you can actually do the math on cycles/packet or cycles/byte here -- with TCP_STREAM, it looks like some combination of recipient CPU and latency overhead is the limiting factor, with netserver running at 94% busy. Could you try using geom gate to export a malloc-backed md device, and see what performance you see there? This would eliminate the storage round trip and guarantee the source is in memory, eliminating some possible sources of synchronous operation (which would increase latency, reducing throughput). Looking at CPU consumption here would also be helpful, as it would allow us to reason about where the CPU is going. > I was aware of that and because of lacking a GbE switch anyway I decided > to use a simple cable ;) Yes, this is my favorite configuration :-). > > (5) Next, I'd measure CPU consumption on the end box -- in particular, use > > top -S and systat -vmstat 1 to compare the idle condition of the > > system and the system under load. > > > > I additionally added these values to the netperf results. Thanks for your very complete and careful testing and reporting :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 03:10:55 2004 Return-Path: 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 AD92C16A4CE for ; Fri, 19 Nov 2004 03:10:55 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 384F543D45 for ; Fri, 19 Nov 2004 03:10:55 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJ3b69n038393 for ; Thu, 18 Nov 2004 22:37:06 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJ3b5te038390 for ; Thu, 18 Nov 2004 22:37:06 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Thu, 18 Nov 2004 22:37:05 -0500 (EST) From: Chuck Robey To: FreeBSD-current@FreeBSD.org Message-ID: <20041118222536.R38351@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Fri, 19 Nov 2004 12:59:33 +0000 Subject: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 03:10:55 -0000 OK, I've done my homework this time, read all the mail archives, looked at the man pages, I may not know the answer but I'm not embarrassed to ask anymore. The assumption I'm working on is that there is a conflict between the usb keyboard&mouse combination and a competing PS/2 keyboard/mouse combination. [g'wan, correct me if I'm wrong, from the mail archives, there are a LOT of folks who will be reading this, and you will be doing a lot of olks a big favor] Just my own problem is on a amd64, but tit doesn't look to me like the problem connects to that platform alone. Apparently it connects more with driver design/modifications; it has occurred sometime after 5.2.1 became 5.3, and affected a large range of users. I would like now to experiment ... I was reading the man pages, the atkb driver, and it appears that one can disable the PS/2 keyboard. The problem is, such a procedure is mildly dangerous; you might not be able to reconnect, if you screw it up; you might have to reinstall. Because of that, I would appreciate it if someone who has more recent driver experience than I do would please help me (and all of the community, believe me) by making me a full and (hopefully) correct task list, things that need to be done, to turn off the PS/2 keyboard and enable the usb keyboard (mouse also at the same time, please). I will take the risk and try it for us, but please take as much care as you can. You do your best, and I promise not to come gunning after you if it breaks anyhow. Well, can I find any takers? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 13:38:35 2004 Return-Path: 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 CBFD516A4CF for ; Fri, 19 Nov 2004 13:38:35 +0000 (GMT) Received: from mail.gmx.net (imap.gmx.net [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id AB1EC43D3F for ; Fri, 19 Nov 2004 13:38:34 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 22009 invoked by uid 65534); 19 Nov 2004 13:38:33 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp025) with SMTP; 19 Nov 2004 14:38:33 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Date: Fri, 19 Nov 2004 14:38:27 +0100 User-Agent: KMail/1.7 X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4421872.GSYVYNt3Lz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411191438.32755.Emanuel.Strobl@gmx.net> Subject: fwe and fwip not working with fwohci0: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 13:38:35 -0000 --nextPart4421872.GSYVYNt3Lz Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Dear lists, since I couldn't get the speed I need with GbE em cards I bought a pair of= =20 firewire 1394a cards and a 6-to-6-Cable. I tried fwe, could ping the other host and also transfer very little files = via=20 ftp, but as soon as I try to shovel a view hundred kByte files the connecti= on=20 stalles. Of course, same with NFS, there I can't transfer any file. Then I compiled a kernel with ipfw but it's exactly the same. Also one machine hangs sometimes at boot when the cable is connected to bot= h=20 cards and the other machine is running, with the following lines: fwohci0: port 0xd800-0xd87f mem 0xe2041000-0xe20417f= f=20 irq 5 at device 10.0 on pci0 fwohci0: OHCI version 1.0 (ROM=3D1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:11:06:00:00:00:75:86 fwohci0: Phy 1394a available S400, 3 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:11:06:00:75:86 fwe0: Ethernet address: 02:11:06:00:75:86 fwe0: if_start running deferred for Giant sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: node_id=3D0xc800ffc1, gen=3D1, CYCLEMASTER mode firewire0: 2 nodes, maxhop <=3D 1, cable IRM =3D 1 (me) firewire0: bus manager 1 (me) [...] firewire0: New S400 device ID:0011060000007587 firewire0: split transaction timeout dst=3D0xffc0 tl=3D0x7 state=3D3 firewire0: bus_explore node=3D0 addr=3D0x40c resp=3D60 retry=3D1 Then nothing happens but the system isn't frozen since "numlock" key is=20 toggling the keyboard LED. =46or a verbose boot or a full dmesg please see=20 http://www.schmalzbauer.de/document.php?id=3D22 I have no idea where to start finding the real problem. Has anybody out there ever been able to use tcp/ip over the VIA VT6306=20 firewire link? Thanks, =2DHarry --nextPart4421872.GSYVYNt3Lz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnfdYBylq0S4AzzwRAlBkAKCETtphc/syVjv+NTwsaFNeLxO6/gCghWiX Fcw/ytfMb1lZRVHXQQHW8ys= =+QNu -----END PGP SIGNATURE----- --nextPart4421872.GSYVYNt3Lz-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 14:10:32 2004 Return-Path: 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 425FF16A4DE for ; Fri, 19 Nov 2004 14:10:32 +0000 (GMT) Received: from mail.gmx.net (pop.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 716CE43D4C for ; Fri, 19 Nov 2004 14:10:30 +0000 (GMT) (envelope-from Emanuel.Strobl@gmx.net) Received: (qmail 30982 invoked by uid 65534); 19 Nov 2004 14:10:29 -0000 Received: from flb.schmalzbauer.de (EHLO cale.flintsbach.schmalzbauer.de) (62.245.232.135) by mail.gmx.net (mp020) with SMTP; 19 Nov 2004 15:10:29 +0100 X-Authenticated: #301138 From: Emanuel Strobl To: freebsd-current@freebsd.org Date: Fri, 19 Nov 2004 15:10:17 +0100 User-Agent: KMail/1.7 References: In-Reply-To: X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4186532.iQCMD9Znuz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411191510.23551.Emanuel.Strobl@gmx.net> cc: freebsd-stable@freebsd.org cc: Robert Watson Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 14:10:32 -0000 --nextPart4186532.iQCMD9Znuz Content-Type: multipart/mixed; boundary="Boundary-01=_L7fnBSoXBK1mVkt" Content-Transfer-Encoding: 7bit Content-Disposition: inline --Boundary-01=_L7fnBSoXBK1mVkt Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Freitag, 19. November 2004 13:56 schrieb Robert Watson: > On Fri, 19 Nov 2004, Emanuel Strobl wrote: > > Am Donnerstag, 18. November 2004 13:27 schrieb Robert Watson: > > > On Wed, 17 Nov 2004, Emanuel Strobl wrote: > > > > I really love 5.3 in many ways but here're some unbelievable transf= er [...] > Well, the claim that if_em doesn't benefit from polling is inaccurate in > the general case, but quite accurate in the specific case. In a box with > multiple NIC's, using polling can make quite a big difference, not just by > mitigating interrupt load, but also by helping to prioritize and manage > the load, preventing live lock. As I indicated in my earlier e-mail, I understand, thanks for the explanation > It looks like the netperf TCP test is getting just under 27MB/s, or > 214Mb/s. That does seem on the low side for the PCI bus, but it's also Nut sure if I understand that sentence correctly, does it mean the "slow"=20 400MHz PII is causing this limit? (low side for the PCI bus?) > instructive to look at the netperf UDP_STREAM results, which indicate that > the box believes it is transmitting 417Mb/s but only 67Mb/s are being > received or processed fast enough by netserver on the remote box. This > means you've achieved a send rate to the card of about 54Mb/s. Note that > you can actually do the math on cycles/packet or cycles/byte here -- with > TCP_STREAM, it looks like some combination of recipient CPU and latency > overhead is the limiting factor, with netserver running at 94% busy. Hmm, I can't puzzle a picture out of this.=20 > > Could you try using geom gate to export a malloc-backed md device, and see > what performance you see there? This would eliminate the storage round It's a pleasure: test2:~#15: dd if=3D/dev/zero of=3D/mdgate/testfile bs=3D16k count=3D6000 6000+0 records in 6000+0 records out 98304000 bytes transferred in 5.944915 secs (16535812 bytes/sec) test2:~#17: dd if=3D/mdgate/testfile of=3D/dev/null bs=3D16k 6000+0 records in 6000+0 records out 98304000 bytes transferred in 5.664384 secs (17354755 bytes/sec) This time it's no difference between disk and memory filesystem, but on=20 another machine with a ich2 chipset and a 3ware controller (my current=20 productive system which I try to replace with this project) there was a big= =20 difference. Attached is the corresponding message. Thanks, =2DHarry > trip and guarantee the source is in memory, eliminating some possible > sources of synchronous operation (which would increase latency, reducing > throughput). Looking at CPU consumption here would also be helpful, as it > would allow us to reason about where the CPU is going. > > > I was aware of that and because of lacking a GbE switch anyway I decided > > to use a simple cable ;) > > Yes, this is my favorite configuration :-). > > > > (5) Next, I'd measure CPU consumption on the end box -- in particular, > > > use top -S and systat -vmstat 1 to compare the idle condition of the > > > system and the system under load. > > > > I additionally added these values to the netperf results. > > Thanks for your very complete and careful testing and reporting :-). > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Resear= ch > > _______________________________________________ > 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" --Boundary-01=_L7fnBSoXBK1mVkt Content-Type: message/rfc822; name="forwarded message" Content-Transfer-Encoding: 7bit Content-Description: Emanuel Strobl : Re: asymmetric NFS transfer rates Content-Disposition: inline From: Emanuel Strobl To: freebsd-current@freebsd.org Subject: Re: asymmetric NFS transfer rates Date: Mon, 8 Nov 2004 04:29:11 +0100 User-Agent: KMail/1.7 Cc: Doug White , Robert Watson References: <20041102105534.K63929@carver.gumbysoft.com> In-Reply-To: <20041102105534.K63929@carver.gumbysoft.com> X-OS: FreeBSD X-Birthday: 10/06/72 X-Address: Munich, 80686 X-Tel: +49 89 18947781 X-CelPhone: +49 173 9967781 X-Country: Germany MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1243660.JDKRhvq51c"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200411080429.12846.Emanuel.Strobl@gmx.net> X-UID: 3906 X-Length: 4558 --nextPart1243660.JDKRhvq51c Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Dienstag, 2. November 2004 19:56 schrieb Doug White: > On Tue, 2 Nov 2004, Robert Watson wrote: > > On Tue, 2 Nov 2004, Emanuel Strobl wrote: > > > It's a IDE Raid controller (3ware 7506-4, a real one) and the file is > > > indeed huge, but not abnormally. I have a harddisk video recorder, so= I > > > have lots of 700MB files. Also if I copy my photo collection from the > > > server it takes 5 Minutes but copying _to_ the server it takes almost > > > 15 Minutes and the average file size is 5 MB. Fast Ethernet isn't > > > really suitable for my needs, but at least the 10MB/s should be > > > reached. I can't imagine I get better speeds when I upgrade to GbE, > > > (which the important boxes are already, just not the switch) because > > > NFS in it's current state isn't able to saturate a 100baseTX line, at > > > least in one direction. That's the real anstonishing thing for me. Why > > > does reading staurate 100BaseTX but writes only a third? > > > > Have you tried using tcpdump/ethereal to see if there's any significant > > packet loss (for good reasons or not) going on? Lots of RPC retransmits > > would certainly explain the lower performance, and if that's not it, it > > would be good to rule out. The traces might also provide some insight > > into the specific I/O operations, letting you see what block sizes are = in > > use, etc. I've found that dumping to a file with tcpdump and reading > > with ethereal is a really good way to get a picture of what's going on > > with NFS: ethereal does a very nice job decoding the RPCs, as well as > > figuring out what packets are related to each other, etc. > > It'd also be nice to know the mount options (nfs blocksizes in > particular). I haven't done intensive wire-dumps yet, but I figured out some oddities. My main problem seems to be the 3ware controller in combination with NFS. I= f I=20 create a malloc backed md0 I can push more than 9MB/s to it with UDP and mo= re=20 that 10MB/s with TCP (both without modifying r/w-size). I can also copy a 100M file from twed0s1d to twed0s1e (so from and to the s= ame=20 RAID5 array which is worst rate) with 15MB/s so the array can't be the=20 bottleneck. Only when I push to the RAID5 array via NFS I only get 4MB/s, no matter if = I=20 use UDP, TCP or nonstandard r/w-sizes. Next thing I found is that if I tune -w to anything higher than the standar= d=20 8192 the average transfer rate of one big file degrades with UDP but=20 increases with TCP (like I would expect). UDP transfer seems to hic-up with -w tuned, transfer rates peak at 8MB/s bu= t=20 the next second they stay at 0-2MB/s (watched with systat -vm 1) but with T= CP=20 everything runs smooth, regardless of the -w value. Now back to my real problem: Can you imagine that NFS and twe are blocking= =20 each other or something like that? Why do I get such really bad transfer=20 rates when both parts are in use but every single part on its own seems to= =20 work fine? Thanks for any help, =2DHarry --nextPart1243660.JDKRhvq51c Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBjugIBylq0S4AzzwRAnX+AJ0TC2LI6GsiX/L3SHfxdQWwzfdvDwCdEMhq Ndcd6c3XokaY1ksXnJ2jRcU= =pPRL -----END PGP SIGNATURE----- --nextPart1243660.JDKRhvq51c-- --Boundary-01=_L7fnBSoXBK1mVkt-- --nextPart4186532.iQCMD9Znuz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnf7PBylq0S4AzzwRAoCZAJ4jB/GnTqOM3G/J9bzhOMLY1Y5PmgCcCDAj ebL9TYVVBAJn40IwFs36X1M= =sjxG -----END PGP SIGNATURE----- --nextPart4186532.iQCMD9Znuz-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 14:29:41 2004 Return-Path: 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 63C5616A4CE for ; Fri, 19 Nov 2004 14:29:41 +0000 (GMT) Received: from mail-fs.sunrise.ch (mta-fs-be-01.sunrise.ch [194.158.229.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id A347B43D46 for ; Fri, 19 Nov 2004 14:29:40 +0000 (GMT) (envelope-from triulzi@freesurf.ch) Received: from [62.167.35.210] (62.167.35.210) by mail-fs.sunrise.ch (7.0.036) id 418ABDFA005EC801; Fri, 19 Nov 2004 15:28:36 +0100 Message-ID: <419E034F.90203@freesurf.ch> Date: Fri, 19 Nov 2004 15:29:35 +0100 From: Mauro Triulzi User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hartzell@kestrel.alerce.com References: <41979C79.6070602@freesurf.ch> <16792.5784.627730.453035@satchel.alerce.com> In-Reply-To: <16792.5784.627730.453035@satchel.alerce.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: NDIS miniport wrapper: routines probably not implemented X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 14:29:41 -0000 George Hartzell wrote: >Mauro Triulzi writes: > > Hallo, > > > > I have a problem with the ndis miniport wrapper for my thinkpad T42p: > > > > My WLAN Card is a built in (IBM) MiniPCI 802.11a/b/g WLAN Card in the > > IBM Thinkpad T42-2373-WBZ P-M/1.7. > > I downloaded the drivers for Windows 2000/XP from > > [...] > >I know that I'm not answering the question you answered, but I use the >atheros driver on my T42p w/ it's a/b/g mini-pci card. Have you tried >it? > >g. > > > Hello George, thank you for your advice. I tried the atheros driver from http://www.phoenixnetworks.net/atheros.php The version 3.1.1.50 (recommended) doesn't work. I've tried also the driver for the CM-9 series but it doesn't work neither. The module if_ndis loads in every case nicely in the kernel (no page fault here), but the card doesn't show up in the output of dmesg. So I stick with my opinion that I tried the right driver (see my 1st E-mail), but the the ndis module doesn't implement enough API to support it (I bought my Thinkpad very recently). Kind regards, Mauro From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 14:29:52 2004 Return-Path: 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 B261D16A4CE for ; Fri, 19 Nov 2004 14:29:52 +0000 (GMT) Received: from abigail.blackend.org (blackend.org [212.11.35.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7291243D31 for ; Fri, 19 Nov 2004 14:29:51 +0000 (GMT) (envelope-from marc@blackend.org) Received: from abigail.blackend.org (localhost [127.0.0.1]) iAJEUKoS033331; Fri, 19 Nov 2004 15:30:20 +0100 (CET) (envelope-from marc@abigail.blackend.org) Received: (from marc@localhost) by abigail.blackend.org (8.12.11/8.12.11/Submit) id iAJEUEwU033328; Fri, 19 Nov 2004 15:30:14 +0100 (CET) (envelope-from marc) Date: Fri, 19 Nov 2004 15:30:14 +0100 From: Marc Fonvieille To: Chuck Robey Message-ID: <20041119143014.GB31660@abigail.blackend.org> References: <20041118222536.R38351@april.chuckr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041118222536.R38351@april.chuckr.org> User-Agent: Mutt/1.4.2.1i X-Useless-Header: blackend.org X-Operating-System: FreeBSD 4.10-PRERELEASE cc: FreeBSD-current@FreeBSD.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 14:29:52 -0000 Hello Chuck, I'm not sure I understood your problem. There is a known issue when installing 5.3-R with a USB keyboard, you should look at the errata: http://www.freebsd.org/releases/5.3R/errata.html Marc PS: well there are chances you already read the errata, in that case forget my advice. From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 15:49:13 2004 Return-Path: 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 9D90E16A4CE; Fri, 19 Nov 2004 15:49:13 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6C1743D1D; Fri, 19 Nov 2004 15:49:12 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAJFmk7C086006; Fri, 19 Nov 2004 08:48:47 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Fri, 19 Nov 2004 08:49:14 -0700 (MST) Message-Id: <20041119.084914.26958488.imp@bsdimp.com> To: daniel_k_eriksson@telia.com From: "M. Warner Losh" In-Reply-To: References: <20041118.095348.103081513.imp@bsdimp.com> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 15:49:13 -0000 In message: "Daniel Eriksson" writes: : Finally, my question. What would you recommend: : 1) Run with ACPI disabled and debug.mpsafenet=1 and hope that the mix of : giant-safe and giant-locked (em and ahc) doesn't trigger any bugs. This is : what I currently do. : 2) Run with ACPI disabled and debug.mpsafenet=0 and accept lower network : performance (it is a high-traffic server, so I'm not sure this is a valid : option). : 3) Run with ACPI enabled and debug.mpsafenet=1 and accept that em0 : interrupts "leak" to the atapci1+ ithread. This I have done in the past. I don't know if I'm to a 'recommendation' so much as a 'I'd try your normal configuration with mpsetfet=0' to see if that makes a difference in the performance that you see. Warner From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 16:00:16 2004 Return-Path: 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 1676D16A4CE; Fri, 19 Nov 2004 16:00:16 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA6243D31; Fri, 19 Nov 2004 16:00:15 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJGQHXF041531; Fri, 19 Nov 2004 11:26:17 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJGQHr6041528; Fri, 19 Nov 2004 11:26:17 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Fri, 19 Nov 2004 11:26:16 -0500 (EST) From: Chuck Robey To: Marc Fonvieille In-Reply-To: <20041119143014.GB31660@abigail.blackend.org> Message-ID: <20041119105620.J38351@april.chuckr.org> References: <20041118222536.R38351@april.chuckr.org> <20041119143014.GB31660@abigail.blackend.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 16:00:16 -0000 On Fri, 19 Nov 2004, Marc Fonvieille wrote: > Hello Chuck, > > I'm not sure I understood your problem. There is a known issue when > installing 5.3-R with a USB keyboard, you should look at the errata: > > http://www.freebsd.org/releases/5.3R/errata.html > > Marc > > PS: well there are chances you already read the errata, in that case > forget my advice. I had (I have done a good bit of reading by now). Following the advice in that errata, about setting the hint, does (did) cause the single forward movement, change, in my status: now, I see a mouse cursor in the period between when rc begins executing (after probing is done, when the screen stops being extra bright), but the moment I hit any key on the keyboard at all (as in the login) the mouse cursor disappears, and I cannot resurrect it (tried restarting mouse, tried vidcontrol -m on). I think what is required is a more complete flushing of all the PS/2 keyboard and mouse drivers, and what I'm asking for is help in performing that erasure more safely, because I'm likely (without a bit of help) to misfigure the actions, and end up with neither a usb keyboard/mouse NOR a PS/2 keyboard/mouse. I just need someone who has done this to tell me all the steps, if that's ok. If you read the mail archives, there are a large contingent of folks who would be helped by this. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 16:24:37 2004 Return-Path: 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 99D4616A4CE; Fri, 19 Nov 2004 16:24:37 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68A7343D3F; Fri, 19 Nov 2004 16:24:37 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAJGOs2V015641; Fri, 19 Nov 2004 08:24:54 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAJGOs8J015640; Fri, 19 Nov 2004 08:24:54 -0800 Date: Fri, 19 Nov 2004 08:24:54 -0800 From: Brooks Davis To: Chuck Robey Message-ID: <20041119162454.GA14789@odin.ac.hmc.edu> References: <20041118222536.R38351@april.chuckr.org> <20041119143014.GB31660@abigail.blackend.org> <20041119105620.J38351@april.chuckr.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB" Content-Disposition: inline In-Reply-To: <20041119105620.J38351@april.chuckr.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 16:24:37 -0000 --tThc/1wpZn/ma/RB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 11:26:16AM -0500, Chuck Robey wrote: > On Fri, 19 Nov 2004, Marc Fonvieille wrote: >=20 > > Hello Chuck, > > > > I'm not sure I understood your problem. There is a known issue when > > installing 5.3-R with a USB keyboard, you should look at the errata: > > > > http://www.freebsd.org/releases/5.3R/errata.html > > > > Marc > > > > PS: well there are chances you already read the errata, in that case > > forget my advice. >=20 > I had (I have done a good bit of reading by now). Following the advice in > that errata, about setting the hint, does (did) cause the single forward > movement, change, in my status: now, I see a mouse cursor in the period > between when rc begins executing (after probing is done, when the screen > stops being extra bright), but the moment I hit any key on the keyboard at > all (as in the login) the mouse cursor disappears, and I cannot resurrect > it (tried restarting mouse, tried vidcontrol -m on). >=20 > I think what is required is a more complete flushing of all the PS/2 > keyboard and mouse drivers, and what I'm asking for is help in performing > that erasure more safely, because I'm likely (without a bit of help) to > misfigure the actions, and end up with neither a usb keyboard/mouse NOR a > PS/2 keyboard/mouse. >=20 > I just need someone who has done this to tell me all the steps, if that's > ok. If you read the mail archives, there are a large contingent of folks > who would be helped by this. There aren't any steps in the general case.. Both my USB mouse and my PS/2 mouse work fine with two moused's running: [8:20am] brooks@minya (~): ps ax | grep moused 394 ?? Ss 0:01.09 /usr/sbin/moused -p /dev/ums0 -I /var/run/moused.= ums0 533 ?? Is 0:00.01 /usr/sbin/moused -p /dev/psm0 -t auto The PS/2 mouse is configured in /etc/rc.conf with the lines: moused_enable=3D"YES" moused_flags=3D"" and the USB mouse is handled by the default entrly in usbd.conf which is enabled in rc.conf with: usbd_enable=3D"YES" -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --tThc/1wpZn/ma/RB Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBnh30XY6L6fI4GtQRAk7KAKC5N+m5Wx037pNyNlIimpeMHbjxQACeK2tr oy1J17/eZWejOdYcQOZPOTk= =nEXe -----END PGP SIGNATURE----- --tThc/1wpZn/ma/RB-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 16:40:25 2004 Return-Path: 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 9CB4616A4CE for ; Fri, 19 Nov 2004 16:40:25 +0000 (GMT) Received: from gateway.nixsys.be (gateway.nixsys.be [195.144.77.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 341A643D58 for ; Fri, 19 Nov 2004 16:40:25 +0000 (GMT) (envelope-from philip@paeps.cx) Received: from wotan.home.paeps.cx (wotan.home.paeps.cx [IPv6:2001:838:37f:10:a00:20ff:fe9b:138c]) by gateway.nixsys.be (Postfix) with ESMTP id 65CB22D6 for ; Fri, 19 Nov 2004 17:40:23 +0100 (CET) Received: from fasolt.home.paeps.cx (fasolt.home.paeps.cx [IPv6:2001:838:37f:10:20a:e6ff:fe7d:c08]) by wotan.home.paeps.cx (Postfix) with ESMTP id B9D49618B for ; Fri, 19 Nov 2004 17:40:22 +0100 (CET) Received: from fasolt.home.paeps.cx (philip@localhost [127.0.0.1]) by fasolt.home.paeps.cx (8.13.1/8.13.1) with ESMTP id iAJGeMpB034952 for ; Fri, 19 Nov 2004 17:40:22 +0100 (CET) (envelope-from philip@fasolt.home.paeps.cx) Received: (from philip@localhost) by fasolt.home.paeps.cx (8.13.1/8.13.1/Submit) id iAJGeM0c034951 for freebsd-current@freebsd.org; Fri, 19 Nov 2004 17:40:22 +0100 (CET) (envelope-from philip) Date: Fri, 19 Nov 2004 17:40:21 +0100 From: Philip Paeps To: freebsd-current@freebsd.org Message-ID: <20041119164021.GA34887@fasolt.home.paeps.cx> Mail-Followup-To: freebsd-current@freebsd.org References: <20041118164356.GA46185@orion.daedalusnetworks.priv> <20041119081734.GC676@loge.nixsys.be> <20041119085054.GB83736@gothmog.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041119085054.GB83736@gothmog.gr> X-Date-in-Rome: ante diem XIII Kalendas Decembres MMDCCLVII ab Urbe Condida X-PGP-Fingerprint: FA74 3C27 91A6 79D5 F6D3 FC53 BF4B D0E6 049D B879 X-Message-Flag: Get a proper mailclient! Organization: Happily Disorganized User-Agent: Mutt/1.5.6i Subject: Re: bug of misc/screen and fifos or ours? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 16:40:25 -0000 On 2004-11-19 10:50:54 (+0200), Giorgos Keramidas wrote: > On 2004-11-19 09:17, Philip Paeps wrote: > > On 2004-11-18 18:43:56 (+0200), Giorgos Keramidas wrote: > > > The screen-4.0.2 version that misc/screen installs is apparently the latest > > > version of screen available. It also contains a zillion bugs, is written in > > > a very insecure style, it uses an antiquated version of autoconf script, > > > etc. > > > > Unrelated, perhaps, but has anyone else noticed that on sparc64, the date > > stuck in utmp seems to always be '19700101': > > I'll have a look later today and this weekend to the utmp handling of > screen. It may be just a bug that shows up on 64-bit architectures. It works on Alpha and AMD64. So it's more likely something showing up only on bigendian systems. Anyone tried on PPC? :-) - Philip -- Philip Paeps Please don't Cc me, I am philip@freebsd.org subscribed to the list. BOFH Excuse #419: Repeated reboots of the system failed to solve problem From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 16:57:49 2004 Return-Path: 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 D8A5916A4CE for ; Fri, 19 Nov 2004 16:57:49 +0000 (GMT) Received: from bizet.nethelp.no (bizet.nethelp.no [195.1.209.33]) by mx1.FreeBSD.org (Postfix) with SMTP id 4FD5943D58 for ; Fri, 19 Nov 2004 16:57:48 +0000 (GMT) (envelope-from sthaug@nethelp.no) Received: (qmail 79376 invoked by uid 1001); 19 Nov 2004 16:57:46 -0000 To: Emanuel.Strobl@gmx.net From: sthaug@nethelp.no In-Reply-To: Your message of "Fri, 19 Nov 2004 13:18:40 +0100" References: <200411191318.46405.Emanuel.Strobl@gmx.net> X-Mailer: Mew version 1.05+ on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 19 Nov 2004 17:57:46 +0100 Message-ID: <79374.1100883466@bizet.nethelp.no> cc: freebsd-current@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: serious networking (em) performance (ggate and NFS) problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 16:57:50 -0000 > I changed cables and couldn't reproduce that bad results so I changed cables > back but also cannot reproduce them, especially the ggate write, formerly > with 2,6MB/s now performs at 15MB/s, but I haven't done any polling tests > anymore, just interrupt driven, since Matt explained that em doesn't benefit > of polling in any way. > > Results don't indicate a serious problem now but are still about a third of > what I'd expected with my hardware. Do I really need Gigahertz Class CPUs to > transfer 30MB/s over GbE? I would be highly surprised if you did. When I tested this a while ago (around FreeBSD 4.8) with a pair of Intel ISP 1100 1U servers using Pentium 700 and Intel GigE cards (em driver), I was able to get around 700 Mbps using ttcp. This was done with a normal 32 bit 33 MHz PCI bus. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 17:12:37 2004 Return-Path: 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 3AE7916A4CE for ; Fri, 19 Nov 2004 17:12:37 +0000 (GMT) Received: from lakermmtao09.cox.net (lakermmtao09.cox.net [68.230.240.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id AA77543D4C for ; Fri, 19 Nov 2004 17:12:36 +0000 (GMT) (envelope-from mkucenski@cox.net) Received: from smtp.east.cox.net ([172.18.52.53]) by lakermmtao09.cox.net (InterMail vM.6.01.04.00 201-2131-117-20041022) with SMTP id <20041119171236.DNZH20678.lakermmtao09.cox.net@smtp.east.cox.net> for ; Fri, 19 Nov 2004 12:12:36 -0500 X-Mailer: Openwave WebEngine, version 2.8.15 (webedge20-101-1103-20040528) From: Matt Kucenski To: Date: Fri, 19 Nov 2004 12:12:36 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Message-Id: <20041119171236.DNZH20678.lakermmtao09.cox.net@smtp.east.cox.net> Subject: ATAng support for reading from register on ATAREQUEST command? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: m.kucenski@computer.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 17:12:37 -0000 I am trying to develop a program that will allow modifications to the Host Protected Area settings and one of the commands (READ NATIVE MAX ADDRESS) returns the native max address back in the register (LBA high, low, mid). I have been looking at the smartmontools project for pointers on how to write this code and according to that source, this is not possible yet with ATAng. There is a comment in their code that another command (ATA_CMD_READ_REG) patch has been submitted to ATAng, but it does not appear to have made it into any of the latest sources. Can anyone offer any information on this? Thanks, -Matt From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 17:14:44 2004 Return-Path: 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 715B716A4CE; Fri, 19 Nov 2004 17:14:44 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id CB91C43D58; Fri, 19 Nov 2004 17:14:43 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJHejtN041889; Fri, 19 Nov 2004 12:40:45 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJHeiIO041886; Fri, 19 Nov 2004 12:40:44 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Fri, 19 Nov 2004 12:40:43 -0500 (EST) From: Chuck Robey To: Brooks Davis In-Reply-To: <20041119162454.GA14789@odin.ac.hmc.edu> Message-ID: <20041119122917.V38351@april.chuckr.org> References: <20041118222536.R38351@april.chuckr.org> <20041119105620.J38351@april.chuckr.org> <20041119162454.GA14789@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 17:14:44 -0000 On Fri, 19 Nov 2004, Brooks Davis wrote: > > I just need someone who has done this to tell me all the steps, if that's > > ok. If you read the mail archives, there are a large contingent of folks > > who would be helped by this. > > There aren't any steps in the general case.. Both my USB mouse and my > PS/2 mouse work fine with two moused's running: > > [8:20am] brooks@minya (~): ps ax | grep moused > 394 ?? Ss 0:01.09 /usr/sbin/moused -p /dev/ums0 -I /var/run/moused.ums0 > 533 ?? Is 0:00.01 /usr/sbin/moused -p /dev/psm0 -t auto > > The PS/2 mouse is configured in /etc/rc.conf with the lines: > > moused_enable="YES" > moused_flags="" > > and the USB mouse is handled by the default entrly in usbd.conf which is > enabled in rc.conf with: > > usbd_enable="YES" VERY good, thanks for the response, please work with me here. First, I'm working with a brand new amd64 install, so my etc is hopefully (and more properly, my rc.conf) up to date, it has a mouse_ports, but not a moused_flags at all, so you may be working witha customized etc ... no big surprise. I interpolated, tried your settings, on reboot I have no /dev/psm0 device. I looked at the psm man page, and I dolled up the /boot/loader.conf as instructed. on reboot, kenv reports what I would want to see, but still no /dev/psm0 (which is why, I suppose, I have only a single moused process running, the usbd.conf inspired one. That one, the mouse cursor still disappears the moment I touch the keyboard.. That info I did, I tried both with and without the atkbdc hint in the mail archives. I notice, btw, that the usb (ums0) gets probed by the kernel well, well before rc.conf gets asked about psm0 ... I bet that timing is something that, if I could change, might help things. I would like the psm to get started before the usb one. > > -- Brooks > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 17:45:16 2004 Return-Path: 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 C734B16A4CE for ; Fri, 19 Nov 2004 17:45:16 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1D0B43D58 for ; Fri, 19 Nov 2004 17:45:15 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (korben.prv.univie.ac.at [131.130.7.98]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAJHj6ZO132462 for ; Fri, 19 Nov 2004 18:45:09 +0100 Date: Fri, 19 Nov 2004 18:45:07 +0100 (CET) From: Lukas Ertl To: freebsd-current@FreeBSD.org In-Reply-To: <20041116170615.K92983@pcle2.cc.univie.ac.at> Message-ID: <20041119184422.K578@korben.in.tern> References: <20041116170615.K92983@pcle2.cc.univie.ac.at> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx9.univie.ac.at 4248; Body=1 Fuz1=1 Fuz2=1 Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 17:45:16 -0000 On Tue, 16 Nov 2004, Lukas Ertl wrote: > The boot process itself finishes fine, and the 'real' console also works as > expected. It's just that iLO console that locks up. A kernel from > Nov 4 doesn't show this behaviour, so I somehow don't believe it's a hardware > problem. OK, I found the culprit: Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 17:48:53 2004 Return-Path: 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 2B1E316A4CE for ; Fri, 19 Nov 2004 17:48:53 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9535843D2D for ; Fri, 19 Nov 2004 17:48:52 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJIErRo042062; Fri, 19 Nov 2004 13:14:53 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJIEqYl042059; Fri, 19 Nov 2004 13:14:53 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Fri, 19 Nov 2004 13:14:52 -0500 (EST) From: Chuck Robey To: Brooks Davis In-Reply-To: <20041119122917.V38351@april.chuckr.org> Message-ID: <20041119130644.G38351@april.chuckr.org> References: <20041118222536.R38351@april.chuckr.org> <20041119105620.J38351@april.chuckr.org> <20041119122917.V38351@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 17:48:53 -0000 On Fri, 19 Nov 2004, Chuck Robey wrote: > > The PS/2 mouse is configured in /etc/rc.conf with the lines: > > > > moused_enable="YES" > > moused_flags="" > > > > and the USB mouse is handled by the default entrly in usbd.conf which is > > enabled in rc.conf with: > > > > usbd_enable="YES" > > VERY good, thanks for the response, please work with me here. First, I'm > working with a brand new amd64 install, so my etc is hopefully (and more > properly, my rc.conf) up to date, it has a mouse_ports, but not a > moused_flags at all, so you may be working witha customized etc ... no big > surprise. I interpolated, tried your settings, on reboot I have no > /dev/psm0 device. I looked at the psm man page, and I dolled up the > /boot/loader.conf as instructed. on reboot, kenv reports what I would > want to see, but still no /dev/psm0 (which is why, I suppose, I have only > a single moused process running, the usbd.conf inspired one. That one, > the mouse cursor still disappears the moment I touch the keyboard.. > > That info I did, I tried both with and without the atkbdc hint in the mail > archives. > > I notice, btw, that the usb (ums0) gets probed by the kernel well, well > before rc.conf gets asked about psm0 ... I bet that timing is something > that, if I could change, might help things. I would like the psm to get > started before the usb one. Bad etiquete to reply to myself, but I had more ideas, and I tried them. I'm again at an end, but I have this to add: I went in and deleted the ums0 entry from usbd.conf, so that it won't get attached; if I use the serial converter so that my keyboard and mouse are serial, then /dev/psm0 does get created; if ums0 is being cteaed first, then /dev/psm0 is unavailble to the system for some reason, I can't get it created later on. I need some method to delay the usb processing for the keyboard and mouse combo UNTIL all of the PS/2 processing is finished. Obviously, /dev/psm0 and /dev/ums0 get along poorly. BTW, yes, I tried adding the ums0 back after I had the good (?) /dev/psm0, again, the mouse cursor disappears the moment I touch the keyboard. It flickers to life, and is immediately gone. I don't understand abou that, your notion about running two moused processes was aluring. Funny point? for the PS/2 case, rc.conf is NOT making a moused process. That's not working. OK, that's something I can investigate. Again, if anyone thinks they know all of the steps to completely delete the ps/2 mouse an dkeyboard from the system (leaving me the usb ones) let me know, I'll try anything that looks like a complete task list. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 18:27:21 2004 Return-Path: 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 CF5C516A4CE for ; Fri, 19 Nov 2004 18:27:21 +0000 (GMT) Received: from april.chuckr.org (april.chuckr.org [66.92.151.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 075AA43D2F for ; Fri, 19 Nov 2004 18:27:21 +0000 (GMT) (envelope-from chuckr@chuckr.org) Received: from april.chuckr.org (localhost [127.0.0.1]) by april.chuckr.org (8.12.11/8.12.11) with ESMTP id iAJIrLjN042193; Fri, 19 Nov 2004 13:53:21 -0500 (EST) (envelope-from chuckr@chuckr.org) Received: from localhost (chuckr@localhost)iAJIrK7N042190; Fri, 19 Nov 2004 13:53:21 -0500 (EST) (envelope-from chuckr@chuckr.org) X-Authentication-Warning: april.chuckr.org: chuckr owned process doing -bs Date: Fri, 19 Nov 2004 13:53:20 -0500 (EST) From: Chuck Robey To: Brooks Davis In-Reply-To: <20041119130644.G38351@april.chuckr.org> Message-ID: <20041119134152.P38351@april.chuckr.org> References: <20041118222536.R38351@april.chuckr.org> <20041119105620.J38351@april.chuckr.org> <20041119130644.G38351@april.chuckr.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems --WORKAROUND!! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 18:27:21 -0000 On Fri, 19 Nov 2004, Chuck Robey wrote: This one stinks, but until a better solution comes around, this gets me off the ground. What did it take? Brooks (and I think one other person, but I forget who) had reported they had no problem in running both, and by god, that IS what works! Run both! That gets you at least a single mouse running, which is a whole lot better than bupkis. Who knows, maybe the extremely ill look of this fix might motivate a more elegant solution from someone. Maybe a miracle wil happen and I'll get a chance to fix it myself (don't hold your breath). OK, for those who've been bored, I'm finished. For any of the horde of folks I saw on the net, write me privately if you need to know more, I offer whatever help I can, but do it soon, I get yet another surgery on Monday, I won't be answering up so well on Tuesday. With all these problems, FreeBSD still compares awfully well against Linux. I will take a chance to make one Linux-comment, tho, and all my recent Linux exposure might make this more useful. FreeBSD has done a good job of improving rc, but I saw a better one. The rc implementation done by the folks at Linux's gentoo, well, its a programmer's wet dream. They have no business having such a nice rc, it's so BSD-ish it's funny. Honestly, it's well worth a strong peak. Someone at gentoo knows how to code in sh. If anyone is more than curious about that, I migth be willing to see if I can place some working examples on the net for you. Strong curiosity, from real programmers, is enough to motivate me (send me a ssh line). > On Fri, 19 Nov 2004, Chuck Robey wrote: > > > > The PS/2 mouse is configured in /etc/rc.conf with the lines: > > > > > > moused_enable="YES" > > > moused_flags="" > > > > > > and the USB mouse is handled by the default entrly in usbd.conf which is > > > enabled in rc.conf with: > > > > > > usbd_enable="YES" > > > > VERY good, thanks for the response, please work with me here. First, I'm > > working with a brand new amd64 install, so my etc is hopefully (and more > > properly, my rc.conf) up to date, it has a mouse_ports, but not a > > moused_flags at all, so you may be working witha customized etc ... no big > > surprise. I interpolated, tried your settings, on reboot I have no > > /dev/psm0 device. I looked at the psm man page, and I dolled up the > > /boot/loader.conf as instructed. on reboot, kenv reports what I would > > want to see, but still no /dev/psm0 (which is why, I suppose, I have only > > a single moused process running, the usbd.conf inspired one. That one, > > the mouse cursor still disappears the moment I touch the keyboard.. > > > > That info I did, I tried both with and without the atkbdc hint in the mail > > archives. > > > > I notice, btw, that the usb (ums0) gets probed by the kernel well, well > > before rc.conf gets asked about psm0 ... I bet that timing is something > > that, if I could change, might help things. I would like the psm to get > > started before the usb one. > > Bad etiquete to reply to myself, but I had more ideas, and I tried them. > I'm again at an end, but I have this to add: I went in and deleted the > ums0 entry from usbd.conf, so that it won't get attached; if I use the > serial converter so that my keyboard and mouse are serial, then /dev/psm0 > does get created; if ums0 is being cteaed first, then /dev/psm0 is > unavailble to the system for some reason, I can't get it created later on. > I need some method to delay the usb processing for the keyboard and mouse > combo UNTIL all of the PS/2 processing is finished. > > Obviously, /dev/psm0 and /dev/ums0 get along poorly. > > BTW, yes, I tried adding the ums0 back after I had the good (?) > /dev/psm0, again, the mouse cursor disappears the moment I touch the > keyboard. It flickers to life, and is immediately gone. I don't > understand abou that, your notion about running two moused processes was > aluring. > > Funny point? for the PS/2 case, rc.conf is NOT making a moused process. > That's not working. OK, that's something I can investigate. > > Again, if anyone thinks they know all of the steps to completely delete > the ps/2 mouse an dkeyboard from the system (leaving me the usb ones) let > me know, I'll try anything that looks like a complete task list. > > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C & Java programming, FreeBSD, > chuckr@chuckr.org | electronics, communications, and SF/Fantasy. > > New Year's Resolution: I will not sphroxify gullible people into looking up > fictitious words in the dictionary (on the wall at my old fraternity, > Signa Phi Nothing). > ---------------------------------------------------------------------------- > _______________________________________________ > 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" > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@chuckr.org | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ---------------------------------------------------------------------------- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 18:28:51 2004 Return-Path: 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 E879516A4CE for ; Fri, 19 Nov 2004 18:28:50 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A29C943D1F for ; Fri, 19 Nov 2004 18:28:50 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iAJIT9qX030649; Fri, 19 Nov 2004 10:29:09 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iAJIT9Xt030648; Fri, 19 Nov 2004 10:29:09 -0800 Date: Fri, 19 Nov 2004 10:29:09 -0800 From: Brooks Davis To: Chuck Robey Message-ID: <20041119182909.GB14789@odin.ac.hmc.edu> References: <20041118222536.R38351@april.chuckr.org> <20041119105620.J38351@april.chuckr.org> <20041119162454.GA14789@odin.ac.hmc.edu> <20041119122917.V38351@april.chuckr.org> <20041119130644.G38351@april.chuckr.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CUfgB8w4ZwR/yMy5" Content-Disposition: inline In-Reply-To: <20041119130644.G38351@april.chuckr.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 18:28:51 -0000 --CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 01:14:52PM -0500, Chuck Robey wrote: > On Fri, 19 Nov 2004, Chuck Robey wrote: >=20 > > > The PS/2 mouse is configured in /etc/rc.conf with the lines: > > > > > > moused_enable=3D"YES" > > > moused_flags=3D"" > > > > > > and the USB mouse is handled by the default entrly in usbd.conf which= is > > > enabled in rc.conf with: > > > > > > usbd_enable=3D"YES" > > > > VERY good, thanks for the response, please work with me here. First, I= 'm > > working with a brand new amd64 install, so my etc is hopefully (and more > > properly, my rc.conf) up to date, it has a mouse_ports, but not a > > moused_flags at all, so you may be working witha customized etc ... no = big > > surprise. I interpolated, tried your settings, on reboot I have no > > /dev/psm0 device. I looked at the psm man page, and I dolled up the > > /boot/loader.conf as instructed. on reboot, kenv reports what I would > > want to see, but still no /dev/psm0 (which is why, I suppose, I have on= ly > > a single moused process running, the usbd.conf inspired one. That one, > > the mouse cursor still disappears the moment I touch the keyboard.. > > > > That info I did, I tried both with and without the atkbdc hint in the m= ail > > archives. > > > > I notice, btw, that the usb (ums0) gets probed by the kernel well, well > > before rc.conf gets asked about psm0 ... I bet that timing is something > > that, if I could change, might help things. I would like the psm to get > > started before the usb one. >=20 > Bad etiquete to reply to myself, but I had more ideas, and I tried them. > I'm again at an end, but I have this to add: I went in and deleted the > ums0 entry from usbd.conf, so that it won't get attached; if I use the > serial converter so that my keyboard and mouse are serial, then /dev/psm0 > does get created; if ums0 is being cteaed first, then /dev/psm0 is > unavailble to the system for some reason, I can't get it created later on. > I need some method to delay the usb processing for the keyboard and mouse > combo UNTIL all of the PS/2 processing is finished. >=20 > Obviously, /dev/psm0 and /dev/ums0 get along poorly. >=20 > BTW, yes, I tried adding the ums0 back after I had the good (?) > /dev/psm0, again, the mouse cursor disappears the moment I touch the > keyboard. It flickers to life, and is immediately gone. I don't > understand abou that, your notion about running two moused processes was > aluring. >=20 > Funny point? for the PS/2 case, rc.conf is NOT making a moused process. > That's not working. OK, that's something I can investigate. >=20 > Again, if anyone thinks they know all of the steps to completely delete > the ps/2 mouse an dkeyboard from the system (leaving me the usb ones) let > me know, I'll try anything that looks like a complete task list. Does your BIOS have a legacy mode setting? If so, please try disabling it. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBnjt1XY6L6fI4GtQRAgYyAJ98AWYoHPcj9NZnJvDDhAq4xfBgywCfVQ6m a2/6BJhqg5nol6DXN5nzwBg= =XRIN -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5-- From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 22:11:28 2004 Return-Path: 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 2FCE116A4CE for ; Fri, 19 Nov 2004 22:11:28 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7E8343D55 for ; Fri, 19 Nov 2004 22:11:27 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21226 invoked from network); 19 Nov 2004 22:11:27 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Nov 2004 22:11:26 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAJMBJbr008149; Fri, 19 Nov 2004 17:11:22 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: "Wilkinson, Alex" Date: Fri, 19 Nov 2004 16:57:42 -0500 User-Agent: KMail/1.6.2 References: <20041116021421.GK56252@squash.dsto.defence.gov.au> <20041118053724.GS66822@squash.dsto.defence.gov.au> In-Reply-To: <20041118053724.GS66822@squash.dsto.defence.gov.au> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411191657.42735.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org Subject: Re: bge(4) watchdog timeout X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 22:11:28 -0000 On Thursday 18 November 2004 12:37 am, Wilkinson, Alex wrote: > Well, if I do that I will be using the old AT-PIC. > Which as far as I am aware is old and crusty ;-\ > > Is this correct john ? It will still work ok. The only major downside is that PCI devices will probably have to share IRQ lines whereas they usually don't with APICs. > -aW > > 0n Wed, Nov 17, 2004 at 06:56:13PM +0100, Arno J. Klaassen wrote: > > "Wilkinson, Alex" writes: > > I get the following errors, however, although it states that there is no > > carrier, there is. > > > > bge0: firmware handshake timed out > > bge0: RX CPU self-diagnostics failed! > > bge0: flags=8843 mtu 1500 > > options=1a > > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > > ether 00:11:0a:40:d2:dd > > media: Ethernet autoselect (none) > > status: no carrier > > > > Mounting NFS file systems:bge0: watchdog timeout -- resetting > > > > > > Here is ifconfig(8) output after fully booted: > > > > bge0: flags=8843 mtu 1500 > > options=1a > > inet 131.185.40.211 netmask 0xfffffc00 broadcast 131.185.43.255 > > ether 00:11:0a:40:d2:dd > > media: Ethernet autoselect (100baseTX ) > > status: active > > > > Seems odd enough, to email the wizards about it. > > one of my co-workers had a similar problem (PR 73538). > Leaving out "device apic" from the kernel-config "fixed" the > problem. YMMV > > Arno -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 22:11:30 2004 Return-Path: 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 D42BB16A4D0 for ; Fri, 19 Nov 2004 22:11:30 +0000 (GMT) Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B6B443D55 for ; Fri, 19 Nov 2004 22:11:30 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 21469 invoked from network); 19 Nov 2004 22:11:30 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 19 Nov 2004 22:11:29 -0000 Received: from [10.50.41.235] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iAJMBJbs008149; Fri, 19 Nov 2004 17:11:25 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Peter Holm Date: Fri, 19 Nov 2004 17:10:19 -0500 User-Agent: KMail/1.6.2 References: <20041112123343.GA12048@peter.osted.lan> <200411151546.15533.jhb@FreeBSD.org> <20041119075924.GA22320@peter.osted.lan> In-Reply-To: <20041119075924.GA22320@peter.osted.lan> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200411191710.19215.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-current@FreeBSD.org cc: bmilekic@FreeBSD.org cc: jeffr@FreeBSD.org Subject: Re: Freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 22:11:30 -0000 On Friday 19 November 2004 02:59 am, Peter Holm wrote: > On Mon, Nov 15, 2004 at 03:46:15PM -0500, John Baldwin wrote: > > On Friday 12 November 2004 07:33 am, Peter Holm wrote: > > > GENERIC HEAD from Nov 11 08:05 UTC > > > > > > The following stack traces etc. was done before my first > > > cup of coffee, so it's not so informative as it could have been :-( > > > > > > The test box appeared to have been frozen for more than 6 hours, > > > but was pingable. > > > > > > http://www.holm.cc/stress/log/cons86.html > > > > A weak guess is that you have the system in some sort of livelock due to > > fork()? Have you tried running with 'debug.mpsafevm=1' set from the > > loader? > > > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > > OK, I've got some more info: > > http://www.holm.cc/stress/log/cons88.html > > Looks like a spin in uma_zone_slab() when slab_zalloc() fails? Yes, I think if you specify M_WAITOK, then that might happen. slab_zalloc() can fail if any of the init functions fail for example, in which case it would loop forever. You can try this hack (though it may very well be wrong) to return failure if that is what is triggering: Index: uma_core.c =================================================================== RCS file: /usr/cvs/src/sys/vm/uma_core.c,v retrieving revision 1.110 diff -u -r1.110 uma_core.c --- uma_core.c 6 Nov 2004 11:43:30 -0000 1.110 +++ uma_core.c 19 Nov 2004 22:08:26 -0000 @@ -1998,6 +1998,10 @@ */ if (flags & M_NOWAIT) flags |= M_NOVM; + + /* XXXHACK */ + if (flags & M_WAITOK) + break; } return (slab); } -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Fri Nov 19 23:50:10 2004 Return-Path: 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 828B416A4CE for ; Fri, 19 Nov 2004 23:50:10 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id E08BB43D2D for ; Fri, 19 Nov 2004 23:50:09 +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 4DD2E1FF9AC for ; Sat, 20 Nov 2004 00:50:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 669CD1FF92F; Sat, 20 Nov 2004 00:50:06 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id D6EAD155DD; Fri, 19 Nov 2004 23:49:20 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id CB0161539F for ; Fri, 19 Nov 2004 23:49:21 +0000 (UTC) Date: Fri, 19 Nov 2004 23:49:21 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: FreeBSD current mailing list Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de Subject: mem leak in mii ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Nov 2004 23:50:10 -0000 Hi, in sys/dev/mii/mii.c there are two calls to malloc for ivars; see for example mii_phy_probe: v = malloc(sizeof(vm_offset_t) * 2, M_DEVBUF, M_NOWAIT); if (v == 0) { return (ENOMEM); } v[0] = ifmedia_upd; v[1] = ifmedia_sts; *child = device_add_child(dev, "miibus", -1); device_set_ivars(*child, v); Where is the free for this malloc ? I cannot find it. analogous: miibus_probe ? -- Greetings Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 00:41:08 2004 Return-Path: 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 C182A16A4CF for ; Sat, 20 Nov 2004 00:41:08 +0000 (GMT) Received: from mail-fs.sunrise.ch (mta-fs-be-04.sunrise.ch [194.158.229.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id BCD2943D1F for ; Sat, 20 Nov 2004 00:41:07 +0000 (GMT) (envelope-from triulzi@freesurf.ch) Received: from [62.167.215.78] (62.167.215.78) by mail-fs.sunrise.ch (7.0.036) id 418ABE170062E197 for freebsd-current@freebsd.org; Sat, 20 Nov 2004 01:41:06 +0100 Message-ID: <419E92A1.2040000@freesurf.ch> Date: Sat, 20 Nov 2004 01:41:05 +0100 From: Mauro Triulzi User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) 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 usb if you unload and reload kernel modules X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 00:41:08 -0000 Hello, I noticed, that if you kldunload and kldload any kernel module, usb hotplugging doesn't work anymore. uname -a FreeBSD triulzi 6.0-CURRENT FreeBSD 6.0-CURRENT #1: Sat Nov 20 01:04:34 CET 2004 triulzi@triulzi:/usr/obj/usr/src/sys/GENERIC i386 world built about 1 hour ago. To reproduce the problem: i) verify that usb hotplug works (I mean /dev/da0, /dev/da0s1 are being created when you plug the usb memory stick in) ii) kldunload snd_ich (or any other kernel module) iii) kldload snd_ich iv) plug your usb memory stick in again: nothing will happen Is there a special reason for that? How could I in this case use the memory stick without booting? Regards, Mauro From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 01:21:40 2004 Return-Path: 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 C3C8816A4CE for ; Sat, 20 Nov 2004 01:21:40 +0000 (GMT) Received: from dragon.nuxi.com (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BC4043D31 for ; Sat, 20 Nov 2004 01:21:40 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.13.1/8.13.1) with ESMTP id iAK1LYdW020902; Fri, 19 Nov 2004 17:21:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.13.1/8.13.1/Submit) id iAK1LYlB020901; Fri, 19 Nov 2004 17:21:34 -0800 (PST) (envelope-from obrien) Date: Fri, 19 Nov 2004 17:21:34 -0800 From: "David O'Brien" To: "Conrad J. Sabatier" Message-ID: <20041120012134.GF20068@dragon.nuxi.com> References: <20041118101356.53ed3f78@dolphin.local.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041118101356.53ed3f78@dolphin.local.net> User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 cc: freebsd-current@freebsd.org Subject: Re: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-current@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 01:21:40 -0000 On Thu, Nov 18, 2004 at 10:13:56AM -0600, Conrad J. Sabatier wrote: > Noticed this during a cvs update today: > dolphin:root:/usr/src/usr.bin# cvs -R update > ? lex/lib/.depend > ? lex/lib/libln.a > ? lex/lib/libmain.o > ? lex/lib/libyywrap.o How did you build your system? At one time you maybe cd'ed into usr.bin/lex and just typed 'make' without 'make obj'? The fix is to: rm -rf /usr/obj/* cd /usr/src make cleandir make buildworld cvs -q up and you shouldn't see this again. -- -- David (obrien@FreeBSD.org) From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 02:36:42 2004 Return-Path: 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 7EDE716A4CE; Sat, 20 Nov 2004 02:36:42 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3425443D58; Sat, 20 Nov 2004 02:36:42 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 1F24172DF4; Fri, 19 Nov 2004 18:36:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 1CD2F72DD4; Fri, 19 Nov 2004 18:36:42 -0800 (PST) Date: Fri, 19 Nov 2004 18:36:42 -0800 (PST) From: Doug White To: Lukas Ertl In-Reply-To: <20041119184422.K578@korben.in.tern> Message-ID: <20041119183614.N49832@carver.gumbysoft.com> References: <20041116170615.K92983@pcle2.cc.univie.ac.at> <20041119184422.K578@korben.in.tern> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@FreeBSD.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 02:36:42 -0000 On Fri, 19 Nov 2004, Lukas Ertl wrote: > On Tue, 16 Nov 2004, Lukas Ertl wrote: > > > The boot process itself finishes fine, and the 'real' console also works as > > expected. It's just that iLO console that locks up. A kernel from > > Nov 4 doesn't show this behaviour, so I somehow don't believe it's a hardware > > problem. > > OK, I found the culprit: > > Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. Interesting... does iLO show up as a PCI device or something? -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 02:55:54 2004 Return-Path: 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 4DDD316A4CE for ; Sat, 20 Nov 2004 02:55:54 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F87D43D45 for ; Sat, 20 Nov 2004 02:55:54 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 232C172DD4; Fri, 19 Nov 2004 18:55:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 2158872DCB; Fri, 19 Nov 2004 18:55:54 -0800 (PST) Date: Fri, 19 Nov 2004 18:55:54 -0800 (PST) From: Doug White To: Sean McNeil In-Reply-To: <1100753869.21798.74.camel@server.mcneil.com> Message-ID: <20041119184253.R49832@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> <1100725008.21333.2.camel@server.mcneil.com> <1100753869.21798.74.camel@server.mcneil.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 02:55:54 -0000 On Wed, 17 Nov 2004, Sean McNeil wrote: > > > It appears that all the threads are destroyed yet it is still in the > > > thread processing loop. The process is no longer active at all. I just > > > had a similar problem happen with vlc where I closed it yet it is > > > hanging in the same place as slapd with all the threads gone. > > > > Interesting... what scheduler are you using? > > 4BSD with PREEMPTION on. -CURRENT as of yesterday. This has been an > issue for quite some time now, however. Fairly standard defaults then ... > > > Here is the one from vlc: > > > > > > (gdb) bt full > > > #0 _thr_sched_switch_unlocked (curthread=0x955000) at pthread_md.h:226 > > > > I can't find a reference to this in that file. Can you run ldd against > > your vlc binary? I('m curious what thread library it thinks its running. > > /usr/X11R6/bin/vlc: > libpthread.so.1 => /usr/lib/libpthread.so.1 (0x801c7c000) OK so not using libthr... > I just ran it again and had a thread sitting at > _thr_sched_switch_unlocked. Here is the trace for that thread: > > (gdb) bt > #0 _thr_sched_switch_unlocked (curthread=0x1b38c00) at pthread_md.h:226 > #1 0x0000000801c8da8f in _nanosleep (time_to_sleep=0x7fffffe8df50, > time_remaining=0x0) > at /usr/src/lib/libpthread/thread/thr_nanosleep.c:71 > #2 0x0000000801c8dbd3 in __nanosleep (time_to_sleep=0x7fffffe8df50, > time_remaining=0x0) > at /usr/src/lib/libpthread/thread/thr_nanosleep.c:125 > #3 0x000000000042b1f9 in msleep (delay=34369437808) at > src/misc/mtime.c:309 > #4 0x0000000806a51e02 in OSSThread (p_aout=0x1b38800) at oss.c:624 > #5 0x0000000801c87139 in thread_start (curthread=0x800940070, > start_routine=0x94d068, arg=0x800940070) > at /usr/src/lib/libpthread/thread/thr_create.c:343 > #6 0x0000000801df1ff4 in makectx_wrapper (ucp=0x800940060, func=0x6636, > args=0x1) at /usr/src/lib/libc/amd64/gen/makecontext.c:100 Ah ha. I think we're on to something here. You didn't make it clear before this is an amd64 machine, which is why I couldn't find the reference on i386. :) The argument to msleep looks like a 64-bit extension bug. The thread is sleeping properly, just for a few thousand years or something :) So the problems with slapd and vlc may just be 64-but uncleanliness. Although slapd is wierd since it works fine on sparc64 under solaris 8 (we run it at work) so I doubt that its something that silly. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 03:26:45 2004 Return-Path: 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 87BEC16A4CE for ; Sat, 20 Nov 2004 03:26:45 +0000 (GMT) Received: from mail.mcneil.com (mcneil.com [24.199.45.54]) by mx1.FreeBSD.org (Postfix) with ESMTP id 39D5743D1D for ; Sat, 20 Nov 2004 03:26:45 +0000 (GMT) (envelope-from sean@mcneil.com) Received: from localhost (localhost.mcneil.com [127.0.0.1]) by mail.mcneil.com (Postfix) with ESMTP id EFDDAF2098; Fri, 19 Nov 2004 19:26:44 -0800 (PST) Received: from mail.mcneil.com ([127.0.0.1]) by localhost (server.mcneil.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 50510-09; Fri, 19 Nov 2004 19:26:43 -0800 (PST) Received: from mcneil.com (mcneil.com [24.199.45.54]) by mail.mcneil.com (Postfix) with ESMTP id 4161FF182A; Fri, 19 Nov 2004 19:26:43 -0800 (PST) From: Sean McNeil To: Doug White In-Reply-To: <20041119184253.R49832@carver.gumbysoft.com> References: <1100657472.74795.2.camel@server.mcneil.com> <20041117102623.P25028@carver.gumbysoft.com> <1100725008.21333.2.camel@server.mcneil.com> <20041117183453.C29048@carver.gumbysoft.com> <1100753869.21798.74.camel@server.mcneil.com> <20041119184253.R49832@carver.gumbysoft.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-VoTzL8FTNiU3GZBAzMwN" Date: Fri, 19 Nov 2004 19:26:43 -0800 Message-Id: <1100921203.82948.1.camel@server.mcneil.com> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 FreeBSD GNOME Team Port X-Virus-Scanned: by amavisd-new at mcneil.com cc: current@freebsd.org Subject: Re: Why won't slapd shutdown (kill -0)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 03:26:45 -0000 --=-VoTzL8FTNiU3GZBAzMwN Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Fri, 2004-11-19 at 18:55 -0800, Doug White wrote: > Ah ha. I think we're on to something here. You didn't make it clear befor= e > this is an amd64 machine, which is why I couldn't find the reference on > i386. :) >=20 > The argument to msleep looks like a 64-bit extension bug. The thread is > sleeping properly, just for a few thousand years or something :) >=20 > So the problems with slapd and vlc may just be 64-but uncleanliness. > Although slapd is wierd since it works fine on sparc64 under solaris 8 (w= e > run it at work) so I doubt that its something that silly. This is only a problem with shutdown. Both of these programs work just fine under amd64 yet fail to properly terminate without killing them with -9. --=-VoTzL8FTNiU3GZBAzMwN Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBnrlzyQsGN30uGE4RAuJiAKCyP4Z7OS8ZPJerRXoyAX+lUqTWmgCg3Lx1 Z3npSYwboiDBXkmWa+eFbHk= =tmEJ -----END PGP SIGNATURE----- --=-VoTzL8FTNiU3GZBAzMwN-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 07:07:21 2004 Return-Path: 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 1D53F16A4CE; Sat, 20 Nov 2004 07:07:21 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EB9F43D39; Sat, 20 Nov 2004 07:07:20 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (harmony.village.org [10.0.0.6]) by harmony.village.org (8.13.1/8.13.1) with ESMTP id iAK75sCf002750; Sat, 20 Nov 2004 00:05:54 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Sat, 20 Nov 2004 00:06:24 -0700 (MST) Message-Id: <20041120.000624.122832691.imp@bsdimp.com> To: le@freebsd.org From: "M. Warner Losh" In-Reply-To: <20041119184422.K578@korben.in.tern> References: <20041116170615.K92983@pcle2.cc.univie.ac.at> <20041119184422.K578@korben.in.tern> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 07:07:21 -0000 In message: <20041119184422.K578@korben.in.tern> Lukas Ertl writes: : On Tue, 16 Nov 2004, Lukas Ertl wrote: : : > The boot process itself finishes fine, and the 'real' console also works as : > expected. It's just that iLO console that locks up. A kernel from : > Nov 4 doesn't show this behaviour, so I somehow don't believe it's a hardware : > problem. : : OK, I found the culprit: : : Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. Dang. I missed the earlier part of this thread. You shouldn't need to do this if I coded things up right. But, alas, you do. Can you send me the details? Warner From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 09:08:42 2004 Return-Path: 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 BF5E416A4CE for ; Sat, 20 Nov 2004 09:08:42 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2F7AB43D55 for ; Sat, 20 Nov 2004 09:08:42 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (korben.prv.univie.ac.at [131.130.7.98]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAK98VZO463624; Sat, 20 Nov 2004 10:08:34 +0100 Date: Sat, 20 Nov 2004 10:08:33 +0100 (CET) From: Lukas Ertl To: Doug White In-Reply-To: <20041119183614.N49832@carver.gumbysoft.com> Message-ID: <20041120100758.C566@korben.prv.univie.ac.at> References: <20041116170615.K92983@pcle2.cc.univie.ac.at> <20041119183614.N49832@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx9.univie.ac.at 4248; Body=2 Fuz1=2 Fuz2=2 cc: freebsd-current@FreeBSD.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 09:08:42 -0000 On Fri, 19 Nov 2004, Doug White wrote: > On Fri, 19 Nov 2004, Lukas Ertl wrote: >> >> OK, I found the culprit: >> >> Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. > > Interesting... does iLO show up as a PCI device or something? Yes: none1@pci0:4:0: class=0x088000 card=0xb2060e11 chip=0xb2030e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'iLo Integrated Lights Out Processor' class = base peripheral none2@pci0:4:2: class=0x088000 card=0xb2060e11 chip=0xb2040e11 rev=0x01 hdr=0x00 vendor = 'Compaq Computer Corp (Now owned by Hewlett-Packard)' device = 'iLo Integrated Lights Out Processor' class = base peripheral cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 09:46:42 2004 Return-Path: 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 EACAA16A4CE for ; Sat, 20 Nov 2004 09:46:42 +0000 (GMT) Received: from imap.univie.ac.at (mail.univie.ac.at [131.130.1.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA2643D31 for ; Sat, 20 Nov 2004 09:46:42 +0000 (GMT) (envelope-from le@FreeBSD.org) Received: from korben.prv.univie.ac.at (korben.prv.univie.ac.at [131.130.7.98]) by imap.univie.ac.at (8.12.10/8.12.10) with ESMTP id iAK9kOZO062046; Sat, 20 Nov 2004 10:46:31 +0100 Date: Sat, 20 Nov 2004 10:46:25 +0100 (CET) From: Lukas Ertl To: "M. Warner Losh" In-Reply-To: <20041120.000624.122832691.imp@bsdimp.com> Message-ID: <20041120104224.E566@korben.prv.univie.ac.at> References: <20041116170615.K92983@pcle2.cc.univie.ac.at> <20041120.000624.122832691.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-DCC-ZID-Univie-Metrics: mx7.univie.ac.at 4247; Body=2 Fuz1=2 Fuz2=2 cc: freebsd-current@FreeBSD.org Subject: Re: Problem with HP DL380 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 09:46:43 -0000 On Sat, 20 Nov 2004, M. Warner Losh wrote: > : Setting hw.pci.do_powerstate=0 in /boot/loader.conf fixes this problem. > > Dang. I missed the earlier part of this thread. You shouldn't need > to do this if I coded things up right. But, alas, you do. Can you > send me the details? No, I think you did everything right. If I understand it correctly, then hw.pci.do_powerstate puts a device into C3 state if no driver attaches. That's just what happens here. That iLO service processor of the DL380s shows up as normal PCI device, but exports the console to the network even without specific driver (as there is none for FreeBSD), so that it works independent of the OS. So, since there is no driver, the device gets powered down as soon as the kernel initializes its ACPI parts, and then the iLO console stops working. cheers, le -- Lukas Ertl http://homepage.univie.ac.at/l.ertl/ le@FreeBSD.org http://people.freebsd.org/~le/ From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 10:01:43 2004 Return-Path: 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 DB0BC16A4CE for ; Sat, 20 Nov 2004 10:01:43 +0000 (GMT) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8AC943D46 for ; Sat, 20 Nov 2004 10:01:42 +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 iAKA1RtA058467; Sat, 20 Nov 2004 12:01:27 +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 21372-08; Sat, 20 Nov 2004 12:01:26 +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 iAKA1QmA058458 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 20 Nov 2004 12:01:26 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.1/8.13.1) id iAKA1TX3026101; Sat, 20 Nov 2004 12:01:29 +0200 (EET) (envelope-from ru) Date: Sat, 20 Nov 2004 12:01:29 +0200 From: Ruslan Ermilov To: freebsd-current@FreeBSD.org Message-ID: <20041120100129.GA26009@ip.net.ua> References: <20041118101356.53ed3f78@dolphin.local.net> <20041120012134.GF20068@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gBBFr7Ir9EOA20Yy" Content-Disposition: inline In-Reply-To: <20041120012134.GF20068@dragon.nuxi.com> User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at ip.net.ua cc: "Conrad J. Sabatier" Subject: Re: usr.bin/lex/lib object files not being placed under MAKEOBJDIRPREFIX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 10:01:44 -0000 --gBBFr7Ir9EOA20Yy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 05:21:34PM -0800, David O'Brien wrote: > On Thu, Nov 18, 2004 at 10:13:56AM -0600, Conrad J. Sabatier wrote: > > Noticed this during a cvs update today: > > dolphin:root:/usr/src/usr.bin# cvs -R update > > ? lex/lib/.depend > > ? lex/lib/libln.a > > ? lex/lib/libmain.o > > ? lex/lib/libyywrap.o >=20 > How did you build your system? At one time you maybe cd'ed into > usr.bin/lex and just typed 'make' without 'make obj'? >=20 > The fix is to: >=20 > rm -rf /usr/obj/* > cd /usr/src > make cleandir > make buildworld > cvs -q up >=20 > and you shouldn't see this again. >=20 Also may worth it finding any stray "obj" directories in the src/ tree. rm -rf /usr/obj/usr/src cd /usr/src find . -name obj -type d | xargs rm -rf make cleandir make cleandir "make cleandir" is run twice because if there's an "obj" symlink, the first cleandir will only remove the symlink but won't clean any object files, if there are any. A faster alternative to the above is: rm -rf /usr/obj/usr/src cd /usr/src find . -name obj | xargs rm -rfv make cleandir Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --gBBFr7Ir9EOA20Yy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBnxX5qRfpzJluFF4RAhQ9AJ0Te92LCPA2jV5eY+yOrWC/ci+i9ACfRVWA kiCiy4E9NiRVGomhRULESUc= =gEeE -----END PGP SIGNATURE----- --gBBFr7Ir9EOA20Yy-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 10:04:07 2004 Return-Path: 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 7719316A4CE for ; Sat, 20 Nov 2004 10:04:07 +0000 (GMT) Received: from mail-fs.sunrise.ch (mta-fs-be-04.sunrise.ch [194.158.229.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id CDD6943D48 for ; Sat, 20 Nov 2004 10:04:06 +0000 (GMT) (envelope-from triulzi@freesurf.ch) Received: from [84.226.34.243] (84.226.34.243) by mail-fs.sunrise.ch (7.0.036) id 418ABE170064EE25; Sat, 20 Nov 2004 11:04:03 +0100 Message-ID: <419F1691.2060703@freesurf.ch> Date: Sat, 20 Nov 2004 11:04:01 +0100 From: Mauro Triulzi User-Agent: Mozilla Thunderbird 0.9 (X11/20041114) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mauro Triulzi References: <41979C79.6070602@freesurf.ch> <16792.5784.627730.453035@satchel.alerce.com> <419E034F.90203@freesurf.ch> In-Reply-To: <419E034F.90203@freesurf.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: NDIS miniport wrapper: routines probably not implemented X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 10:04:07 -0000 Mauro Triulzi wrote: > George Hartzell wrote: > >> Mauro Triulzi writes: >> > Hallo, >> > > I have a problem with the ndis miniport wrapper for my thinkpad >> T42p: >> > > My WLAN Card is a built in (IBM) MiniPCI 802.11a/b/g WLAN Card in >> the > IBM Thinkpad T42-2373-WBZ P-M/1.7. >> > I downloaded the drivers for Windows 2000/XP from >> > [...] >> >> I know that I'm not answering the question you answered, but I use the >> atheros driver on my T42p w/ it's a/b/g mini-pci card. Have you tried >> it? >> >> g. >> >> >> > Hello George, > > thank you for your advice. I tried the atheros driver from > > http://www.phoenixnetworks.net/atheros.php > > The version 3.1.1.50 (recommended) doesn't work. I've tried also the > driver for the CM-9 series > but it doesn't work neither. The module if_ndis loads in every case > nicely in the kernel > (no page fault here), but the card doesn't show up in the output of > dmesg. > > So I stick with my opinion that I tried the right driver (see my 1st > E-mail), but the the ndis module > doesn't implement enough API to support it (I bought my Thinkpad very > recently). > > Kind regards, > Mauro > OK, I know, I made me the life more complicated than it should be ;-) device ath device ath_hl device wlan did the job and works great! Greetings, Mauro From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 10:55:16 2004 Return-Path: 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 374F216A4CE for ; Sat, 20 Nov 2004 10:55:16 +0000 (GMT) Received: from transport.cksoft.de (transport.cksoft.de [62.111.66.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 954CB43D46 for ; Sat, 20 Nov 2004 10:55:15 +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 54DE01FF9AC; Sat, 20 Nov 2004 11:55:08 +0100 (CET) Received: by transport.cksoft.de (Postfix, from userid 66) id 5A1AB1FF91D; Sat, 20 Nov 2004 11:55:06 +0100 (CET) Received: by mail.int.zabbadoz.net (Postfix, from userid 1060) id 1E050156B6; Sat, 20 Nov 2004 10:51:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.int.zabbadoz.net (Postfix) with ESMTP id 1AF241539F; Sat, 20 Nov 2004 10:51:29 +0000 (UTC) Date: Sat, 20 Nov 2004 10:51:29 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@e0-0.zab2.int.zabbadoz.net To: Jeremie Le Hen In-Reply-To: <20041119120102.GM69710@obiwan.tataz.chchile.org> Message-ID: References: <20041119114233.C43B.SHINO@fornext.org> <20041119185315.C43D.SHINO@fornext.org> <20041119120102.GM69710@obiwan.tataz.chchile.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS cksoft-s20020300-20031204bz on transport.cksoft.de cc: freebsd-current@freebsd.org cc: Shunsuke SHINOMIYA Subject: Re: interrupt moderation for if_* [was: serious networking (em) ...] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 10:55:16 -0000 On Fri, 19 Nov 2004, Jeremie Le Hen wrote: > > Hi, Jeremie, how is this? > > To disable Interrupt Moderation, sysctl hw.em?.int_throttle_valve=0. > > Great, I would have called it "int_throttle_ceil", but that's a detail > and my opinion is totally subjective. > > > However, because this patch is just made now, it is not fully tested. > > I'll give it a try this weekend although I won't be able to make > performance mesurements. when thinking about this could there be some "global" way for interrupt moderation; For if_sk there is this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/41220 something 'unique' to all NIC drivers would be good I guess ? -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 11:02:41 2004 Return-Path: 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 285F316A4CE for ; Sat, 20 Nov 2004 11:02:41 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8BF243D5C for ; Sat, 20 Nov 2004 11:02:40 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1CVT0p-00079L-Dm; Sat, 20 Nov 2004 11:02:39 +0000 Date: Sat, 20 Nov 2004 11:02:39 +0000 From: Dick Davies To: Sean McNeil Message-ID: <20041120110238.GA11995@lb.tenfour> References: <419B3DA9.8020202@fer.hr> <20041117135058.GB28461@lb.tenfour> <1100723747.18003.4.camel@server.mcneil.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <1100723747.18003.4.camel@server.mcneil.com> User-Agent: Mutt/1.4.2.1i Sender: Rasputin cc: FreeBSD Current Users Subject: Re: openldap slapd startup delay X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dick Davies List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 11:02:41 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Sean McNeil [1136 20:36]: >=20 > Does this fix the start delay, or the problem with stop? I have traced Don't know about a stop problem, I don't see that (but I checkpoint the db fairly often). This cuts the start to about a second. (For some reason if you specify 2 listen sockets that rises to about 8sec, but nothing like the 30+ sec delay (was > 1min on my ME6000 ). > through the start delay and found it is because slapd is opening the > socket and then there is a lookup on group which causes it to try to > read from slapd and you are in a deadlock until the socket times out. > This has always been normal for me (the delay on startup) and others. You mean you store the ldap group as a posixGroup in LDAP? --=20 If we can hit that bull's-eye, the rest of the dominoes will fall like a house of cards... Checkmate! - Zapp. Brannigan Rasputin :: Jack of All Trades - Master of Nuns --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (NetBSD) iD8DBQFBnyROVFnamZKfe00RAu7tAJ4uJsjB+dSdzU33+srDEcHwaMpybgCfd7D5 kzvWU4/81QYQvjmrUiU15VQ= =prw3 -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 05:24:12 2004 Return-Path: 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 6B15316A4CE for ; Sat, 20 Nov 2004 05:24:12 +0000 (GMT) Received: from mail.chesapeake.net (chesapeake.net [208.142.252.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5D7743D46 for ; Sat, 20 Nov 2004 05:24:11 +0000 (GMT) (envelope-from jroberson@chesapeake.net) Received: from mail.chesapeake.net (localhost [127.0.0.1]) by mail.chesapeake.net (8.12.10/8.12.10) with ESMTP id iAK5OBPV058643 for ; Sat, 20 Nov 2004 00:24:11 -0500 (EST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost)iAK5OB89058639 for ; Sat, 20 Nov 2004 00:24:11 -0500 (EST) (envelope-from jroberson@chesapeake.net) X-Authentication-Warning: mail.chesapeake.net: jroberson owned process doing -bs Date: Sat, 20 Nov 2004 00:24:10 -0500 (EST) From: Jeff Roberson To: current@freebsd.org Message-ID: <20041120000743.G18094@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Mailman-Approved-At: Sat, 20 Nov 2004 13:28:46 +0000 Subject: Giantless VFS. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 05:24:12 -0000 I have a patch that I would like people to test and review. It's available here: http://www.chesapeake.net/~jroberson/smpffs.diff The short description: This patch removes Giant from the read(), write(), and fstat() syscalls, as well as page faults, and bufdone (io interrupts) when using FFS. It adds a considerable amount of locking to FFS and softupdates. You may also use non ffs filesystems concurrently, but they will be protected by Giant. If you are using quotas you should not yet run this patch. I have done some buildworlds, but any heavy filesystem activity would be appreciated. Long description: There is now a per mount-point mutex in struct ufsmount that covers ffs's struct fs related allocation routines. The rest of the filesystem was already covered by the buffer locks on cgs, indirs, etc, as well as a few mutexes that were already in place. I made great attempts to minimize the number of lock operations for the common cases which resulted in a couple of functions which may be entered with the UFS lock held, but return without it held. Where this is not already done, it will be documented in comments. The softupdate lk lock has been turned into a mutex, and it now protects all global worklists, inode and page dep hash buckets, etc. interlocked_sleep() is gone now that BUF_LOCK() and msleep() take interlock arguments. getdirtybuf() has been slightly changed to solve some sleep related races that I disucssed with Kirk. For now there is a single softupdates mutex, but eventually it will be made per-mountpoint and potentially merged with the ufsmount lock. On the infrastructure side, the buffer cache was locked some time ago, and now the vm is safe to run without Giant, so there are simply a lot of removed GIANT_REQUIRED lines. I added some locking to vn_start_write() and friends, and made some changes for LORs there. There is a pair of new macros called VFS_(UN)LOCK_GIANT(mp) which inspects a new flag on the mount-point to determine if we have to acquire giant. This is done very early in the syscall path before we call any VOPs. The mountpoints should be safe to inspect as we always own a reference to the vnode in the cases that I have unwound for now. Cheers, Jeff From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 21:11:39 2004 Return-Path: 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 570AB16A4CE for ; Sat, 20 Nov 2004 21:11:39 +0000 (GMT) Received: from mproxy.gmail.com (mproxy.gmail.com [216.239.56.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0F26143D1D for ; Sat, 20 Nov 2004 21:11:39 +0000 (GMT) (envelope-from egemukan@gmail.com) Received: by mproxy.gmail.com with SMTP id u33so75569cwc for ; Sat, 20 Nov 2004 13:11:39 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:return-path:message-id:from:to:subject:date:mime-version:content-type:x-priority:x-msmail-priority:x-mailer:x-mimeole; b=ApK+RVuaywjr3ugecgdBMoDM8TfGR5qTrH4M7U6RSr+tCp+RXgKbLQ5mHzLt5sdYI5eBX6+bbIs9MT6mUotNwMqdKN97UdJGX7ni7oXuv/mAESsrNK0jvGL1wLubzNPXtGjYRUHE2lf78tnHQkeDcvx0tcGuSwFSxjLBAwDEE88= Received: by 10.11.100.61 with SMTP id x61mr23733cwb; Sat, 20 Nov 2004 13:11:38 -0800 (PST) Received: from redbaron ([195.174.144.149]) by smtp.gmail.com with ESMTP id v71sm1616cwb; Sat, 20 Nov 2004 13:11:38 -0800 (PST) Message-ID: <003801c4cf45$86860680$9590aec3@redbaron> From: =?iso-8859-9?Q?Ege_M=FCkan?= To: Date: Sat, 20 Nov 2004 23:11:24 +0200 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Content-Type: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 Subject: Floppy Boot ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 21:11:39 -0000 Hi,=20 Is there way to install FreeBSD 5.3 without install boot loader to HDD = but with creating boot floppies to start your system which is installed = on your HDD ?? Thanx=20 Ege. From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 22:13:15 2004 Return-Path: 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 17D7B16A4CE for ; Sat, 20 Nov 2004 22:13:15 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id E37ED43D58 for ; Sat, 20 Nov 2004 22:13:14 +0000 (GMT) (envelope-from freebsd-current-local@be-well.ilk.org) Received: (qmail 15587 invoked from network); 20 Nov 2004 22:13:14 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 20 Nov 2004 22:13:14 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 32E8E68; Sat, 20 Nov 2004 17:13:14 -0500 (EST) Sender: lowell@be-well.ilk.org To: =?iso-8859-1?q?Ege_M=FCkan?= References: <003801c4cf45$86860680$9590aec3@redbaron> From: Lowell Gilbert Date: 20 Nov 2004 17:13:13 -0500 In-Reply-To: <003801c4cf45$86860680$9590aec3@redbaron> Message-ID: <444qjkkw3q.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable cc: freebsd-current@freebsd.org Subject: Re: Floppy Boot ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 22:13:15 -0000 Ege M=FCkan writes: > Is there way to install FreeBSD 5.3 without install boot loader to HDD bu= t with creating boot floppies to start your system which is installed on yo= ur HDD ?? This question would be more appropriate on freebsd-questions, but the answer would be the same on a -CURRENT system. I think you can just take the installation boot floppy and set up the boot.config file to boot the appropriate disk and the appropriate kernel. There are many "boot manager" programs that can be installed to floppies, as well. From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 22:23:27 2004 Return-Path: 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 8134016A4CE for ; Sat, 20 Nov 2004 22:23:27 +0000 (GMT) Received: from 9.hellooperator.net (cpc3-cdif2-3-0-cust202.cdif.cable.ntl.com [81.103.32.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D7D943D46 for ; Sat, 20 Nov 2004 22:23:27 +0000 (GMT) (envelope-from rasputin@hellooperator.net) Received: from rasputin by 9.hellooperator.net with local (Exim 4.43) id 1CVddd-0001Lc-H4; Sat, 20 Nov 2004 22:23:25 +0000 Date: Sat, 20 Nov 2004 22:23:25 +0000 From: Dick Davies To: Dan Nelson Message-ID: <20041120222325.GC17297@lb.tenfour> References: <419CD314.80900@fer.hr> <20041118171012.GB19265@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041118171012.GB19265@dan.emsphone.com> User-Agent: Mutt/1.4.2.1i Sender: Rasputin cc: FreeBSD Current Users Subject: Re: Replacing passwd? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Dick Davies List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 22:23:27 -0000 * Dan Nelson [1110 17:10]: > In the last episode (Nov 18), Ivan Voras said: > > I've setup pam_ldap and nss_ldap and samba3 and smbldap, and it works > > fine, but it would be nice to replace /usr/bin/passwd with > > smbldap-passwd (which changes both NTLM and Unix password fields in > > LDAP, while passwd is unaware of LDAP, at least according to man > > page). Is there a clean way of doing it so I don't have to replace > > it by hand after each installworld? > > passwd just uses PAM to set passwords When did that come in? I can't get passwd(1) to change an ldap password, I get: rasputnik@eris:rasputnik$ passwd passwd: Sorry, `passwd' can only change passwords for local or NIS users. rasputnik@eris:rasputnik$ uname -a FreeBSD eris 5.3-STABLE FreeBSD 5.3-STABLE #4: Mon Oct 25 18:03:11 BST 2004 root@eris:/usr/obj/usr/src/sys/ERIS i386 rasputnik@eris:rasputnik$ - this is an nss_ldap nsswitched account, logged in over ssh (pam_ldap auth). -- This must be Thursday. I never could get the hang of Thursdays. - Arthur Dent Rasputin :: Jack of All Trades - Master of Nuns From owner-freebsd-current@FreeBSD.ORG Sat Nov 20 22:25:29 2004 Return-Path: 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 9D0E216A4E2 for ; Sat, 20 Nov 2004 22:25:29 +0000 (GMT) Received: from out002.verizon.net (out002pub.verizon.net [206.46.170.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5A9543DA3 for ; Sat, 20 Nov 2004 22:25:18 +0000 (GMT) (envelope-from ringworm@inbox.lv) Received: from ringworm.mechee.com ([4.26.226.89]) by out002.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20041120222518.IHJP3388.out002.verizon.net@ringworm.mechee.com> for ; Sat, 20 Nov 2004 16:25:18 -0600 Received: by ringworm.mechee.com (Postfix, from userid 1001) id 5CD962CE7D3; Sat, 20 Nov 2004 14:23:21 -0800 (PST) From: "Michael C. Shultz" To: freebsd-current@freebsd.org Date: Sat, 20 Nov 2004 14:23:20 -0800 User-Agent: KMail/1.7.1 References: <003801c4cf45$86860680$9590aec3@redbaron> In-Reply-To: <003801c4cf45$86860680$9590aec3@redbaron> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-9" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200411201423.20426.ringworm@inbox.lv> X-Authentication-Info: Submitted using SMTP AUTH at out002.verizon.net from [4.26.226.89] at Sat, 20 Nov 2004 16:25:17 -0600 Subject: Re: Floppy Boot ?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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, 20 Nov 2004 22:25:29 -0000 On Saturday 20 November 2004 01:11 pm, Ege M=FCkan wrote: > Hi, > > Is there way to install FreeBSD 5.3 without install boot loader to > HDD but with creating boot floppies to start your system which is > installed on your HDD ?? > > Thanx > > Ege. Take a look at /usr/ports/sysutils/grub. It lets you boot a variety of OS's using a floppy as a bootloader. =2DMike