From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 26 15:50:19 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E6A1316A420; Sun, 26 Feb 2006 15:50:19 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E86B43D46; Sun, 26 Feb 2006 15:50:17 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k1QFoBrx009345; Sun, 26 Feb 2006 18:50:11 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k1QFoAZ4009340; Sun, 26 Feb 2006 18:50:10 +0300 (MSK) (envelope-from yar) Date: Sun, 26 Feb 2006 18:50:09 +0300 From: Yar Tikhiy To: hackers@freebsd.org Message-ID: <20060226155009.GB6435@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.9i Cc: Subject: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 15:50:20 -0000 Hi all, Yesterday I hit the following problem: - was given an Athlon XP machine with a fresh CURRENT built with CPUTYPE=athlon-xp; - used it to build a fresh RELENG_6 world with no customizations at all -- __MAKE_CONF=/dev/null; - tried to install the world over NFS on an old Pentium machine with some 5.3-BETA; - "make installkernel" failed instantly because install(1) died on signal 4, illegal instruction. Quick investigation showed that the world was built using generic i386 code, as expected, but its toolchain was linked against the builder system libs contaminated by Athlon-specific code. It was sufficient to rebuild and reinstall all libs on the builder machine with no particular CPUTYPE set and then to rebuild the world's toolchain again to make the latter run well on the Pentium. I used to be under impression that a world's toolchain should be fairly independent from the builder system. However, this case showed that it wasn't quite true. Is it a known issue, or am I missing a key point? Thanks! -- Yar From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 26 15:57:16 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B03C16A420 for ; Sun, 26 Feb 2006 15:57:16 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.197]) by mx1.FreeBSD.org (Postfix) with ESMTP id AEAF043D6B for ; Sun, 26 Feb 2006 15:57:07 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id i30so457461wxd for ; Sun, 26 Feb 2006 07:57:07 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FioDF6UAzZ12oBOq5krXRbhOh/uO1TFog8H7Z5cArHP7uaWSm7jQWxtT0SxzpW3G/2OahJdjHDBhJHXnIozhZfok7mBo2yMaZ2DSRsy/dY3rlOQGjgMGhMIjNEJbx9Zj9m+oKrXwPRzOKhIZirjnh09zJw//PhMjtotUc9aFr7g= Received: by 10.70.126.12 with SMTP id y12mr5050334wxc; Sun, 26 Feb 2006 07:57:06 -0800 (PST) Received: by 10.70.116.16 with HTTP; Sun, 26 Feb 2006 07:57:06 -0800 (PST) Message-ID: <84dead720602260757l7ddd181l90abf345b9d65210@mail.gmail.com> Date: Sun, 26 Feb 2006 21:27:06 +0530 From: "Joseph Koshy" To: "Yar Tikhiy" In-Reply-To: <20060226155009.GB6435@comp.chem.msu.su> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <20060226155009.GB6435@comp.chem.msu.su> Cc: hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 15:57:16 -0000 yt> - tried to install the world over NFS on an old Pentium yt> machine with some 5.3-BETA; AFAIK, the only 'supported' installation mode is to have the installworld step running on the same machine that did the build. I.e., you need to export '/' from the old Pentium box, mount it somewhere on your Athlon and run a make installworld (on the Athlon) with the appropriate DESTDIR value. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 26 18:25:31 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 881C216A420 for ; Sun, 26 Feb 2006 18:25:31 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from mail20.syd.optusnet.com.au (mail20.syd.optusnet.com.au [211.29.132.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 658FE43D4C for ; Sun, 26 Feb 2006 18:25:30 +0000 (GMT) (envelope-from peterjeremy@optushome.com.au) Received: from turion.vk2pj.dyndns.org (c220-239-19-236.belrs4.nsw.optusnet.com.au [220.239.19.236]) by mail20.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k1QIOgiT025774 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 27 Feb 2006 05:24:42 +1100 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.4/8.13.4) with ESMTP id k1QIOgYE010648; Mon, 27 Feb 2006 05:24:42 +1100 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.4/8.13.4/Submit) id k1QIOgc0010647; Mon, 27 Feb 2006 05:24:42 +1100 (EST) (envelope-from peter) Date: Mon, 27 Feb 2006 05:24:42 +1100 From: Peter Jeremy To: Yar Tikhiy Message-ID: <20060226182442.GD707@turion.vk2pj.dyndns.org> References: <20060226155009.GB6435@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060226155009.GB6435@comp.chem.msu.su> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 18:25:31 -0000 On Sun, 2006-Feb-26 18:50:09 +0300, Yar Tikhiy wrote: >- tried to install the world over NFS on an old Pentium machine > with some 5.3-BETA; This isn't supported in general. It should work if: - Both the buildhost and install target are running the same OS date - The installed OS on buildhost was built to the lowest common denominator of both hosts (ie CPU_TYPE=pentium or lower in your case) - src and obj have the same absolute pathnames (including symlink expansions in src). The supported approach is to NFS mount the target onto the buildhost and use "make DESTDIR=/target installworld" >Quick investigation showed that the world was built using generic >i386 code, as expected, Good. > but its toolchain was linked against the >builder system libs contaminated by Athlon-specific code. Also, as expected. >I used to be under impression that a world's toolchain should be >fairly independent from the builder system. Not true. The buildworld toolchain is a cross-compilation system designed to run on the existing host OS version whilst building executables that will run on the target OS version. Of necessity, the toolchain compiles and links against the installed include files and libraries on the host system. -- Peter Jeremy From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 26 19:39:55 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FDAF16A420 for ; Sun, 26 Feb 2006 19:39:55 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id DABB543D6E for ; Sun, 26 Feb 2006 19:39:49 +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 k1QJchnT079586; Sun, 26 Feb 2006 21:38:43 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ip.net.ua [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 76435-01-8; Sun, 26 Feb 2006 21:38: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 k1QJ8PVa078895 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Feb 2006 21:08:25 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id k1QJ8YIu047020; Sun, 26 Feb 2006 21:08:34 +0200 (EET) (envelope-from ru) Date: Sun, 26 Feb 2006 21:08:34 +0200 From: Ruslan Ermilov To: Peter Jeremy Message-ID: <20060226190834.GI42677@ip.net.ua> References: <20060226155009.GB6435@comp.chem.msu.su> <20060226182442.GD707@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Z8yxTSU1mh2gsre7" Content-Disposition: inline In-Reply-To: <20060226182442.GD707@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.5.11 X-Virus-Scanned: amavisd-new at ip.net.ua Cc: Yar Tikhiy , hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 19:39:55 -0000 --Z8yxTSU1mh2gsre7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 27, 2006 at 05:24:42AM +1100, Peter Jeremy wrote: [...] > The supported approach is to NFS mount the target onto the buildhost > and use "make DESTDIR=3D/target installworld" >=20 =2E.. and to make it work, make sure to "chflags -R noschg" the target / on the target host first. (I upgrade all my animals in a zoo this way, from the Hammer.) Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Z8yxTSU1mh2gsre7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEAfyyqRfpzJluFF4RAg85AKCBJCE7MhBHw3xgfq/YV05WR4h/eACeKaL9 44aCKdPemGogTfK3jwEuc9w= =bHQO -----END PGP SIGNATURE----- --Z8yxTSU1mh2gsre7-- From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 26 19:50:05 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8D9B916A420 for ; Sun, 26 Feb 2006 19:50:05 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7641943D4C for ; Sun, 26 Feb 2006 19:50:03 +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 k1QJnaqw080156; Sun, 26 Feb 2006 21:49:36 +0200 (EET) (envelope-from ru@ip.net.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ip.net.ua [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 77068-01-3; Sun, 26 Feb 2006 21:49:10 +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 k1QIvBCD078485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 26 Feb 2006 20:57:12 +0200 (EET) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.4/8.13.4) id k1QIvL68046610; Sun, 26 Feb 2006 20:57:21 +0200 (EET) (envelope-from ru) Date: Sun, 26 Feb 2006 20:57:21 +0200 From: Ruslan Ermilov To: Yar Tikhiy Message-ID: <20060226185721.GF42677@ip.net.ua> References: <20060226155009.GB6435@comp.chem.msu.su> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sw7tCqrGA+HQ0/zt" Content-Disposition: inline In-Reply-To: <20060226155009.GB6435@comp.chem.msu.su> User-Agent: Mutt/1.5.11 X-Virus-Scanned: amavisd-new at ip.net.ua Cc: hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 19:50:05 -0000 --Sw7tCqrGA+HQ0/zt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Feb 26, 2006 at 06:50:09PM +0300, Yar Tikhiy wrote: > Hi all, >=20 > Yesterday I hit the following problem: >=20 > - was given an Athlon XP machine with a fresh CURRENT built with > CPUTYPE=3Dathlon-xp; >=20 > - used it to build a fresh RELENG_6 world with no customizations > at all -- __MAKE_CONF=3D/dev/null; >=20 > - tried to install the world over NFS on an old Pentium machine > with some 5.3-BETA; >=20 > - "make installkernel" failed instantly because install(1) died on > signal 4, illegal instruction. >=20 > Quick investigation showed that the world was built using generic > i386 code, as expected, but its toolchain was linked against the > builder system libs contaminated by Athlon-specific code. It was > sufficient to rebuild and reinstall all libs on the builder machine > with no particular CPUTYPE set and then to rebuild the world's > toolchain again to make the latter run well on the Pentium. >=20 > I used to be under impression that a world's toolchain should be > fairly independent from the builder system. However, this case > showed that it wasn't quite true. Is it a known issue, or am I > missing a key point? Thanks! >=20 Simple answer: we just don't support installing "from" NFS, but we do support installing "to" NFS. Any documentation that says it's supported is lying. More details: during the install, part of the toolchain and some special install tools that were built on the "build" host are used. They have been built using that host's toolchain, CFLAGS, libraries, etc., but libraries is the most important factor. That means that the "install" host should be CPU/syscall/etc. compatible with the "build" host. When "build" =3D=3D "install", all these conditions are met. When CPUs match, kernels may be different enough so there will be missing syscalls. And so far... Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Sw7tCqrGA+HQ0/zt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFEAfoRqRfpzJluFF4RAjqFAJ9JIcqPmWyB27/BhcJoqqe0m6KLmwCfRi+R xPH+DEQNcblcxiDZDXIVxFA= =rxqO -----END PGP SIGNATURE----- --Sw7tCqrGA+HQ0/zt-- From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 06:56:24 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2478E16A420 for ; Mon, 27 Feb 2006 06:56:24 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from server.absolute-media.de (server.absolute-media.de [213.239.231.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CF9043D46 for ; Mon, 27 Feb 2006 06:56:23 +0000 (GMT) (envelope-from NKoch@demig.de) Received: from localhost (unknown [127.0.0.1]) by server.absolute-media.de (Postfix) with ESMTP id 89F69A535D; Mon, 27 Feb 2006 07:56:21 +0100 (CET) Received: from server.absolute-media.de ([127.0.0.1]) by localhost (server [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25779-02; Mon, 27 Feb 2006 07:56:16 +0100 (CET) Received: from firewall.demig (p5083BE0A.dip0.t-ipconnect.de [80.131.190.10]) by server.absolute-media.de (Postfix) with ESMTP id 8B87F561B; Mon, 27 Feb 2006 07:56:16 +0100 (CET) Received: from ws-ew-3 (ws-ew-3.demig.intra [192.168.1.72]) by firewall.demig (8.13.5/8.13.5) with SMTP id k1R6tl5n079269; Mon, 27 Feb 2006 07:55:47 +0100 (CET) (envelope-from NKoch@demig.de) From: "Norbert Koch" To: "Maksim Yevmenkin" Date: Mon, 27 Feb 2006 07:55:47 +0100 Message-ID: <000001c63b6a$d6241960$4801a8c0@ws-ew-3.demig.intra> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <43FF2632.3040409@savvis.net> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2120.0 Importance: Normal X-Virus-Scanned: by amavisd-new X-Virus-Scanned: by amavisd-new at absolute-media.de Cc: freebsd-hackers@freebsd.org Subject: RE: [PATCH] does ukbd delay break scan codes? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 06:56:24 -0000 > > yes I too looked at ukbd code and found the same. > > I already put a patch on the bug list yesterday. > > good. does it fix your problem, i.e. keyboard freeze? if it does then i > can commit it for you. It doeos at least for me and my environment (FreeBSD 4). From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 07:03:56 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3725516A420; Mon, 27 Feb 2006 07:03:56 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id A63A443D48; Mon, 27 Feb 2006 07:03:55 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k1R73EfJ065820; Mon, 27 Feb 2006 00:03:14 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 27 Feb 2006 00:03:17 -0700 (MST) Message-Id: <20060227.000317.123334621.imp@bsdimp.com> To: ru@freebsd.org From: "M. Warner Losh" In-Reply-To: <20060226185721.GF42677@ip.net.ua> References: <20060226155009.GB6435@comp.chem.msu.su> <20060226185721.GF42677@ip.net.ua> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 27 Feb 2006 00:03:15 -0700 (MST) Cc: yar@comp.chem.msu.su, hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 07:03:56 -0000 In message: <20060226185721.GF42677@ip.net.ua> Ruslan Ermilov writes: : On Sun, Feb 26, 2006 at 06:50:09PM +0300, Yar Tikhiy wrote: : > Hi all, : > : > Yesterday I hit the following problem: : > : > - was given an Athlon XP machine with a fresh CURRENT built with : > CPUTYPE=athlon-xp; : > : > - used it to build a fresh RELENG_6 world with no customizations : > at all -- __MAKE_CONF=/dev/null; : > : > - tried to install the world over NFS on an old Pentium machine : > with some 5.3-BETA; : > : > - "make installkernel" failed instantly because install(1) died on : > signal 4, illegal instruction. : > : > Quick investigation showed that the world was built using generic : > i386 code, as expected, but its toolchain was linked against the : > builder system libs contaminated by Athlon-specific code. It was : > sufficient to rebuild and reinstall all libs on the builder machine : > with no particular CPUTYPE set and then to rebuild the world's : > toolchain again to make the latter run well on the Pentium. : > : > I used to be under impression that a world's toolchain should be : > fairly independent from the builder system. However, this case : > showed that it wasn't quite true. Is it a known issue, or am I : > missing a key point? Thanks! : > : Simple answer: we just don't support installing "from" NFS, : but we do support installing "to" NFS. Any documentation : that says it's supported is lying. : : More details: during the install, part of the toolchain and : some special install tools that were built on the "build" : host are used. They have been built using that host's : toolchain, CFLAGS, libraries, etc., but libraries is the : most important factor. That means that the "install" host : should be CPU/syscall/etc. compatible with the "build" : host. When "build" == "install", all these conditions are : met. When CPUs match, kernels may be different enough so : there will be missing syscalls. And so far... I've never had issues with doing the install from NFS to a local disk. However, I make sure that all the make config variables are identical, the CPUTYPE is unset, and the systems are otherwise as identical as possible before trying. Also make sure that the file systems are mounted identically as well. I also try to set BOOTSTRAPPING=0 on the build host, which forces the maximum number of helper tools to be built. So while not strictly supported, it can be made to work if you know what you are doing, and take precautions, and live with the limitiations. Setting CPUTYPE falls outside the limitations in the build system. What's really fun is tricking the build system so you can cross build on one system, but native install on another from the same tree... Warner From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 08:26:35 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DFDA416A420 for ; Mon, 27 Feb 2006 08:26:35 +0000 (GMT) (envelope-from tanmayinamdar@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 49A2A43D45 for ; Mon, 27 Feb 2006 08:26:34 +0000 (GMT) (envelope-from tanmayinamdar@gmail.com) Received: by zproxy.gmail.com with SMTP id v1so904314nzb for ; Mon, 27 Feb 2006 00:26:34 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=fj/eQYRrPrc35lyZ6s9uTIAAv2TbZIKfshpEWlMYXSWtXZGRBsh0irUB+hzYnRkDDPYDAFEwZD+kFDW3SVeVbq18f7kRfWwXdwkyPs690zBbLAMBbDmzm4ogBQhCU/bCpnJJRnm2cFdJAsNhTpc9JubShyOuL2B0EkpajXSvjzo= Received: by 10.35.123.10 with SMTP id a10mr1728863pyn; Mon, 27 Feb 2006 00:26:34 -0800 (PST) Received: by 10.35.13.10 with HTTP; Mon, 27 Feb 2006 00:26:34 -0800 (PST) Message-ID: Date: Mon, 27 Feb 2006 13:56:34 +0530 From: Tanmay To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Accessing address space of a process through kld!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 08:26:36 -0000 Hello, How do I access the address space ie text,data and stack of a (user level)process whose pid I know from my kld. for eg: Suppose 'vi' is running and I want to access its address space through my kld, then how do I do it? TIA, Tanmay From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 10:15:18 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2066316A420; Mon, 27 Feb 2006 10:15:18 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (comp.chem.msu.su [158.250.32.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id B2DDA43D48; Mon, 27 Feb 2006 10:15:14 +0000 (GMT) (envelope-from yar@comp.chem.msu.su) Received: from comp.chem.msu.su (localhost [127.0.0.1]) by comp.chem.msu.su (8.13.3/8.13.3) with ESMTP id k1RAF3X9031707; Mon, 27 Feb 2006 13:15:03 +0300 (MSK) (envelope-from yar@comp.chem.msu.su) Received: (from yar@localhost) by comp.chem.msu.su (8.13.3/8.13.3/Submit) id k1RAF3X7031702; Mon, 27 Feb 2006 13:15:03 +0300 (MSK) (envelope-from yar) Date: Mon, 27 Feb 2006 13:15:02 +0300 From: Yar Tikhiy To: "M. Warner Losh" Message-ID: <20060227101502.GJ6435@comp.chem.msu.su> References: <20060226155009.GB6435@comp.chem.msu.su> <20060226185721.GF42677@ip.net.ua> <20060227.000317.123334621.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060227.000317.123334621.imp@bsdimp.com> User-Agent: Mutt/1.5.9i Cc: hackers@freebsd.org Subject: Re: world's toolchain & CPUTYPE X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 10:15:18 -0000 On Mon, Feb 27, 2006 at 12:03:17AM -0700, M. Warner Losh wrote: > In message: <20060226185721.GF42677@ip.net.ua> > Ruslan Ermilov writes: > : On Sun, Feb 26, 2006 at 06:50:09PM +0300, Yar Tikhiy wrote: > : > Hi all, > : > > : > Yesterday I hit the following problem: > : > > : > - was given an Athlon XP machine with a fresh CURRENT built with > : > CPUTYPE=athlon-xp; > : > > : > - used it to build a fresh RELENG_6 world with no customizations > : > at all -- __MAKE_CONF=/dev/null; > : > > : > - tried to install the world over NFS on an old Pentium machine > : > with some 5.3-BETA; > : > > : > - "make installkernel" failed instantly because install(1) died on > : > signal 4, illegal instruction. > : > > : > Quick investigation showed that the world was built using generic > : > i386 code, as expected, but its toolchain was linked against the > : > builder system libs contaminated by Athlon-specific code. It was > : > sufficient to rebuild and reinstall all libs on the builder machine > : > with no particular CPUTYPE set and then to rebuild the world's > : > toolchain again to make the latter run well on the Pentium. > : > > : > I used to be under impression that a world's toolchain should be > : > fairly independent from the builder system. However, this case > : > showed that it wasn't quite true. Is it a known issue, or am I > : > missing a key point? Thanks! > : > > : Simple answer: we just don't support installing "from" NFS, > : but we do support installing "to" NFS. Any documentation > : that says it's supported is lying. > : > : More details: during the install, part of the toolchain and > : some special install tools that were built on the "build" > : host are used. They have been built using that host's > : toolchain, CFLAGS, libraries, etc., but libraries is the > : most important factor. That means that the "install" host > : should be CPU/syscall/etc. compatible with the "build" > : host. When "build" == "install", all these conditions are > : met. When CPUs match, kernels may be different enough so > : there will be missing syscalls. And so far... > > I've never had issues with doing the install from NFS to a local disk. > However, I make sure that all the make config variables are identical, > the CPUTYPE is unset, and the systems are otherwise as identical as > possible before trying. Also make sure that the file systems are > mounted identically as well. I also try to set BOOTSTRAPPING=0 on the > build host, which forces the maximum number of helper tools to be > built. > > So while not strictly supported, it can be made to work if you know > what you are doing, and take precautions, and live with the > limitiations. Setting CPUTYPE falls outside the limitations in the > build system. Thank everyone for clarifying this issue! I was short-sighted. Indeed, the toolchain is to work on the builder host in the first place, so it should use the builder's MACHINE_ARCH, CPUTYPE, etc. Therefore it won't be generally possible to run it on the target system. > What's really fun is tricking the build system so you can cross build > on one system, but native install on another from the same tree... I wondered, too, if it would be possible to cross-build install tools so that they could run on the target system, but I haven't investigated this way yet. Do you have any ideas/recipes? Thanks! -- Yar From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 10:42:01 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C39116A420 for ; Mon, 27 Feb 2006 10:42:01 +0000 (GMT) (envelope-from V.Ovsyannikov@kr.ru) Received: from ns.kr.ru (ns.kr.ru [84.22.128.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1E1BD43D48 for ; Mon, 27 Feb 2006 10:42:00 +0000 (GMT) (envelope-from V.Ovsyannikov@kr.ru) Received: from gravis.ncux.ru (gravis.ncux.ru [84.22.128.254]) by ns.kr.ru (Postfix) with ESMTP id 227F922E94 for ; Mon, 27 Feb 2006 17:41:57 +0700 (KRAT) Date: Mon, 27 Feb 2006 17:41:32 +0700 From: Vitaliy Ovsyannikov X-Priority: 3 (Normal) Message-ID: <1602933046.20060227174132@kr.ru> To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Vitaliy Ovsyannikov List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 10:42:01 -0000 Hello, freebsd-hackers. I've stuck with the unable to make watchdogs for daemons running via startup rc-scripts. In linux we can just put the process in the inittab. Does FreeBSD contains ability like this? -- Sincerely, Vitaliy Ovsyannikov JSC Skala, Krasnoyarsk, Russia From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 10:43:52 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3041816A420 for ; Mon, 27 Feb 2006 10:43:52 +0000 (GMT) (envelope-from rohitj@purpe.com) Received: from fed1rmmtao04.cox.net (fed1rmmtao04.cox.net [68.230.241.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id B78BF43D55 for ; Mon, 27 Feb 2006 10:43:50 +0000 (GMT) (envelope-from rohitj@purpe.com) Received: from serv01.n1.purpe.com ([68.0.152.17]) by fed1rmmtao04.cox.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060227104035.LJRS17690.fed1rmmtao04.cox.net@serv01.n1.purpe.com> for ; Mon, 27 Feb 2006 05:40:35 -0500 Received: from desk01.n2.purpe.com (desk01.n2.purpe.com [192.168.19.1]) by serv01.n1.purpe.com (8.12.10/8.12.10) with ESMTP id k1RAhjcU020510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Mon, 27 Feb 2006 03:43:48 -0700 (MST) (envelope-from rohitj@desk01.n2.purpe.com) Received: from desk01.n2.purpe.com (localhost [127.0.0.1]) by desk01.n2.purpe.com (8.13.4/8.13.4) with ESMTP id k1RAhgCe006721 for ; Mon, 27 Feb 2006 16:13:42 +0530 (IST) (envelope-from rohitj@desk01.n2.purpe.com) Received: (from rohitj@localhost) by desk01.n2.purpe.com (8.13.4/8.13.4/Submit) id k1RAhfWH006720 for hackers@freebsd.org; Mon, 27 Feb 2006 16:13:41 +0530 (IST) (envelope-from rohitj) Date: Mon, 27 Feb 2006 16:13:41 +0530 From: Rohit Jalan To: hackers@freebsd.org Message-ID: <20060227104341.GA6671@desk01.n2.purpe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Archived: msg.ZtYTtlJ3c@serv01.n1.purpe.com Cc: Subject: UMA zone allocator memory fragmentation questions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 10:43:52 -0000 Hi, Is there an upper limit on the amount of fragmentation / wastage that can occur in a UMA zone? Is there a method to know the total number of pages used by a UMA zone at some instance of time? Thanks, rohit -- From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 11:24:29 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B83DC16A420 for ; Mon, 27 Feb 2006 11:24:29 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0448343D58 for ; Mon, 27 Feb 2006 11:24:27 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp143-122.lns2.adl2.internode.on.net [59.167.143.122]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k1RBOEYI085159 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 21:54:19 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-hackers@freebsd.org, Vitaliy Ovsyannikov Date: Mon, 27 Feb 2006 21:53:17 +1030 User-Agent: KMail/1.9.1 References: <1602933046.20060227174132@kr.ru> In-Reply-To: <1602933046.20060227174132@kr.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1475258.Vg3Qzcomrq"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200602272154.03459.doconnor@gsoft.com.au> X-Spam-Score: -2.186 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 11:24:29 -0000 --nextPart1475258.Vg3Qzcomrq Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 27 February 2006 21:11, Vitaliy Ovsyannikov wrote: > I've stuck with the unable to make watchdogs for daemons running via > startup rc-scripts. In linux we can just put the process in the > inittab. Does FreeBSD contains ability like this? Create a script for /etc/rc.d (or /usr/local/etc/rc.d) - with a suitable en= try=20 in rc.conf it will be started at boot. man rc.subr plus a look through /etc/rc.d should get you started :) =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 --nextPart1475258.Vg3Qzcomrq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEAuFT5ZPcIHs/zowRAo9FAKCZ0damd2g+9FVsGoL7XlmsL6kNWwCfVprR md1p6lgFFixtiKy3hux1t70= =cExY -----END PGP SIGNATURE----- --nextPart1475258.Vg3Qzcomrq-- From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 12:03:41 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EEA516A422 for ; Mon, 27 Feb 2006 12:03:41 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from mailhub04.unibe.ch (mailhub04.unibe.ch [130.92.9.71]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4F9C43D58 for ; Mon, 27 Feb 2006 12:03:40 +0000 (GMT) (envelope-from roth@droopy.unibe.ch) Received: from localhost (scanhub01-eth0.unibe.ch [130.92.254.65]) by mailhub04.unibe.ch (Postfix) with ESMTP id D87A11C327; Mon, 27 Feb 2006 13:03:38 +0100 (CET) Received: from mailhub04.unibe.ch ([130.92.9.71]) by localhost (scanhub01.unibe.ch [130.92.254.65]) (amavisd-new, port 10024) with LMTP id 11476-06-100; Mon, 27 Feb 2006 13:03:37 +0100 (CET) Received: from asterix.unibe.ch (asterix.unibe.ch [130.92.64.4]) by mailhub04.unibe.ch (Postfix) with ESMTP id 36F9C1C33E; Mon, 27 Feb 2006 13:03:37 +0100 (CET) Received: from droopy.unibe.ch (droopy [130.92.64.20]) by asterix.unibe.ch (8.12.10+Sun/8.12.10) with ESMTP id k1RC3b8Z021287; Mon, 27 Feb 2006 13:03:37 +0100 (MET) Received: (from roth@localhost) by droopy.unibe.ch (8.12.10+Sun/8.12.9/Submit) id k1RC3bcZ004247; Mon, 27 Feb 2006 13:03:37 +0100 (MET) Date: Mon, 27 Feb 2006 13:03:36 +0100 From: Tobias Roth To: "Daniel O'Connor" Message-ID: <20060227120336.GA4233@droopy.unibe.ch> References: <1602933046.20060227174132@kr.ru> <200602272154.03459.doconnor@gsoft.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200602272154.03459.doconnor@gsoft.com.au> User-Agent: Mutt/1.4i X-message-flag: Warning! Using Outlook is insecure and promotes virus distribution. Please use a different email client. X-Virus-checked: by University of Berne Cc: freebsd-hackers@freebsd.org Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 12:03:41 -0000 On Mon, Feb 27, 2006 at 09:53:17PM +1030, Daniel O'Connor wrote: > On Monday 27 February 2006 21:11, Vitaliy Ovsyannikov wrote: > > I've stuck with the unable to make watchdogs for daemons running via > > startup rc-scripts. In linux we can just put the process in the > > inittab. Does FreeBSD contains ability like this? > > Create a script for /etc/rc.d (or /usr/local/etc/rc.d) - with a suitable entry > in rc.conf it will be started at boot. > > man rc.subr plus a look through /etc/rc.d should get you started :) Can you explain in more detail how one can handle the watchdog part of the equation? I can't find that information in the rc.subr manpage. thanks, Tobias From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 12:42:36 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C633416A420 for ; Mon, 27 Feb 2006 12:42:36 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31C2143D45 for ; Mon, 27 Feb 2006 12:42:33 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp143-122.lns2.adl2.internode.on.net [59.167.143.122]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k1RCgQEr086227 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 23:12:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Tobias Roth Date: Mon, 27 Feb 2006 23:12:03 +1030 User-Agent: KMail/1.9.1 References: <1602933046.20060227174132@kr.ru> <200602272154.03459.doconnor@gsoft.com.au> <20060227120336.GA4233@droopy.unibe.ch> In-Reply-To: <20060227120336.GA4233@droopy.unibe.ch> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1657134.SZl7bElGAp"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200602272312.17567.doconnor@gsoft.com.au> X-Spam-Score: -2.188 () AWL,BAYES_00 X-Scanned-By: MIMEDefang 2.54 on 203.31.81.10 Cc: freebsd-hackers@freebsd.org Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 12:42:36 -0000 --nextPart1657134.SZl7bElGAp Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 27 February 2006 22:33, Tobias Roth wrote: > > man rc.subr plus a look through /etc/rc.d should get you started :) > > Can you explain in more detail how one can handle the watchdog part of > the equation? I can't find that information in the rc.subr manpage. Ahh sorry I think I misunderstood the question :( I was thinking a program to reset a hardware watchdog timer.. As to answer the question - I am not aware of any facility for automaticall= y=20 restarting things (unless you can get init to do it via /etc/ttys somehow) I don't think it would be too hard to create a shell wrapper script though= =20 (kind of annoying I admit) =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 --nextPart1657134.SZl7bElGAp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBEAvOp5ZPcIHs/zowRAptfAJwOr92jcUiyuzWykdDrDGdcdIWn0QCfb2D3 vf96I2MuJlP3kHrruWo784w= =rQM1 -----END PGP SIGNATURE----- --nextPart1657134.SZl7bElGAp-- From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 13:20:46 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 26EFD16A420 for ; Mon, 27 Feb 2006 13:20:46 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE87F43D46 for ; Mon, 27 Feb 2006 13:20:45 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms071.mailsrvcs.net ([192.168.1.4]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IVC004BNL2LCUV8@vms046.mailsrvcs.net> for freebsd-hackers@freebsd.org; Mon, 27 Feb 2006 07:20:45 -0600 (CST) Date: Mon, 27 Feb 2006 07:20:45 -0600 (CST) From: Sergey Babkin To: Daniel O'Connor , Tobias Roth Message-id: <21474364.1141046445548.JavaMail.root@vms071.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 27 Feb 2006 13:22:14 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 13:20:46 -0000 >From: Daniel O'Connor >On Monday 27 February 2006 22:33, Tobias Roth wrote: >> > man rc.subr plus a look through /etc/rc.d should get you started :) >> >> Can you explain in more detail how one can handle the watchdog part of >> the equation? I can't find that information in the rc.subr manpage. > >Ahh sorry I think I misunderstood the question :( > >I was thinking a program to reset a hardware watchdog timer.. > >As to answer the question - I am not aware of any facility for automatically >restarting things (unless you can get init to do it via /etc/ttys somehow) Would a port of a Linux init do ? :-) You know, it's all separate packages on Linux and there is no reason why they can't be ported and used separately. Here is the package name from RedHat: $ rpm -qf /sbin/init SysVinit-2.85-4.2 I don't know if there is a ready port but it should be not THAT difficult to do. >I don't think it would be too hard to create a shell wrapper script though >(kind of annoying I admit) Well, it's been a long story now. Every time someone comes with the idea of adding init to BSD, other people feel very strongly that they hate init and that it must not be in BSD. -SB From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 13:29:37 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFC7916A420 for ; Mon, 27 Feb 2006 13:29:37 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3FEA143D46 for ; Mon, 27 Feb 2006 13:29:37 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id s13so562447wxc for ; Mon, 27 Feb 2006 05:29:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hl4okevtlegTYOxxpPNuPoBLMUwcfjZDpab9QQl9EM0rh6/YJCykGYeUNrxNe9uqQXKKeWNxSfgh4PwLOLH38RTjdStS3TR5PqqkTUzEJqy96hf/ZzNe1JmEPR6/W74z19tejD5VHI0CcS9WVq1lLdGJHZichF0xfgL3suwFgZw= Received: by 10.70.124.12 with SMTP id w12mr4409934wxc; Mon, 27 Feb 2006 05:29:36 -0800 (PST) Received: by 10.70.116.16 with HTTP; Mon, 27 Feb 2006 05:29:36 -0800 (PST) Message-ID: <84dead720602270529s3c1d5004m13487cd1dfd1ff9d@mail.gmail.com> Date: Mon, 27 Feb 2006 18:59:36 +0530 From: "Joseph Koshy" To: "Daniel O'Connor" In-Reply-To: <200602272312.17567.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <1602933046.20060227174132@kr.ru> <200602272154.03459.doconnor@gsoft.com.au> <20060227120336.GA4233@droopy.unibe.ch> <200602272312.17567.doconnor@gsoft.com.au> Cc: freebsd-hackers@freebsd.org, Tobias Roth Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 13:29:37 -0000 dc> As to answer the question - I am not aware of any facility for dc> automatically restarting things (unless you can get init to do dc> it via /etc/ttys somehow) Wasn't there a port of launchd in the wings? -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 13:38:02 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF7E716A420 for ; Mon, 27 Feb 2006 13:38:02 +0000 (GMT) (envelope-from myself@rojer.pp.ru) Received: from hermes.hw.ru (hermes.hw.ru [80.68.240.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id 992DF43D4C for ; Mon, 27 Feb 2006 13:38:00 +0000 (GMT) (envelope-from myself@rojer.pp.ru) Received: from [80.68.240.83] (HELO smtp.rbc.ru) by hermes.hw.ru (CommuniGate Pro SMTP 4.1.8) with ESMTP id 107492619; Mon, 27 Feb 2006 16:37:59 +0300 Received: from localhost.localdomain (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 6A5433A009; Mon, 27 Feb 2006 16:37:59 +0300 (MSK) X-Spam-Checker-Version: SpamAssassin 3.1.0-rojer (2005-09-13) on goover.rbc.ru X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40 autolearn=ham version=3.1.0-rojer Received: from mx3.rbc.ru (mx3.rbc.ru [194.186.36.203]) by smtp.rbc.ru (Postfix) with ESMTP id C874A3A019; Mon, 27 Feb 2006 16:37:57 +0300 (MSK) Received: from [80.68.243.98] (ws-80-68-243-98.rbc.ru [80.68.243.98]) by mx3.rbc.ru (Postfix) with ESMTP id 80C1A770950; Mon, 27 Feb 2006 16:37:57 +0300 (MSK) Message-ID: <440300B5.4070402@rojer.pp.ru> Date: Mon, 27 Feb 2006 16:37:57 +0300 From: Deomid Ryabkov User-Agent: Thunderbird 1.6a1 (X11/20060215) MIME-Version: 1.0 To: Vitaliy Ovsyannikov References: <1602933046.20060227174132@kr.ru> In-Reply-To: <1602933046.20060227174132@kr.ru> Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms060609040903010206030001" X-SpamTest-Info: Profile: Formal (323/060222) X-SpamTest-Info: Profile: Detect Standard No RBL (4/030526) X-SpamTest-Info: Profile: SysLog X-SpamTest-Info: Profile: Marking Spam - Subject (2/030321) X-SpamTest-Status: Not detected X-SpamTest-Version: SMTP-Filter Version 2.0.0 [0125], KAS/Release Cc: freebsd-hackers@freebsd.org Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 13:38:03 -0000 This is a cryptographically signed message in MIME format. --------------ms060609040903010206030001 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Vitaliy Ovsyannikov wrote: > Hello, freebsd-hackers. > > I've stuck with the unable to make watchdogs for daemons running via > startup rc-scripts. In linux we can just put the process in the > inittab. Does FreeBSD contains ability like this? > > try sysutils/daemontools -- Deomid Ryabkov aka Rojer myself@rojer.pp.ru rojer@sysadmins.ru ICQ: 8025844 --------------ms060609040903010206030001 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 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIJIzCC AuwwggJVoAMCAQICAw5jHTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UE ChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNv bmFsIEZyZWVtYWlsIElzc3VpbmcgQ0EwHhcNMDUwNDAxMDkwNjQzWhcNMDYwNDAxMDkwNjQz WjBfMRAwDgYDVQQEEwdSeWFia292MQ8wDQYDVQQqEwZEZW9taWQxFzAVBgNVBAMTDkRlb21p ZCBSeWFia292MSEwHwYJKoZIhvcNAQkBFhJteXNlbGZAcm9qZXIucHAucnUwggEiMA0GCSqG SIb3DQEBAQUAA4IBDwAwggEKAoIBAQDEKoweumUc1/YHtlscU5xKozcKOd3lLyAZ1SM3rZvn iJ9VAuj9TafODcu+SoJ6sU+Crshl2Nkq/oCs6dynEqyn/jZxGm/mEYxJ+KekBQceLejdFktQ rOuXmjLpipESMO7w1amFn6w3pJgWXex2mcN6hcET2cUdSHjSYxLUXKCQTtzJbcPEHZ+vgEq9 1TA4UcFeZ3d1Ax6q2A2Fs/wvFxtLUC46fq80R7lOxsJA6mxKNOJnbZTCqf8sWF5SyEnNBBj0 yyIHfKl+iMwsqSESg5hc0l9/m6aLV24KtKtvWIEu3RQXflc380xZanF4gvAq8/NADlfEH4Rx SpNOJdgxZga1AgMBAAGjLzAtMB0GA1UdEQQWMBSBEm15c2VsZkByb2plci5wcC5ydTAMBgNV HRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBAEaynMcbL7KaxmVMfJWXD7X4ftDolZ2CpPPN yoVJAIXaIHpI0JuiCnQSZivL6BvtYUNyzNAR6ceh87yWoQEJxw1cV2IgUlQ+Z3/+7brumNdb YwCuf3C/LlamOP5zpHDOH1euXLJe8664lC5lIaf70yO6jN7LXHwBNs73qyB7tvY/MIIC7DCC AlWgAwIBAgIDDmMdMA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQTAeFw0wNTA0MDEwOTA2NDNaFw0wNjA0MDEwOTA2NDNaMF8x EDAOBgNVBAQTB1J5YWJrb3YxDzANBgNVBCoTBkRlb21pZDEXMBUGA1UEAxMORGVvbWlkIFJ5 YWJrb3YxITAfBgkqhkiG9w0BCQEWEm15c2VsZkByb2plci5wcC5ydTCCASIwDQYJKoZIhvcN AQEBBQADggEPADCCAQoCggEBAMQqjB66ZRzX9ge2WxxTnEqjNwo53eUvIBnVIzetm+eIn1UC 6P1Np84Ny75KgnqxT4KuyGXY2Sr+gKzp3KcSrKf+NnEab+YRjEn4p6QFBx4t6N0WS1Cs65ea MumKkRIw7vDVqYWfrDekmBZd7HaZw3qFwRPZxR1IeNJjEtRcoJBO3Mltw8Qdn6+ASr3VMDhR wV5nd3UDHqrYDYWz/C8XG0tQLjp+rzRHuU7GwkDqbEo04mdtlMKp/yxYXlLISc0EGPTLIgd8 qX6IzCypIRKDmFzSX3+bpotXbgq0q29YgS7dFBd+VzfzTFlqcXiC8Crz80AOV8QfhHFKk04l 2DFmBrUCAwEAAaMvMC0wHQYDVR0RBBYwFIESbXlzZWxmQHJvamVyLnBwLnJ1MAwGA1UdEwEB /wQCMAAwDQYJKoZIhvcNAQEEBQADgYEARrKcxxsvsprGZUx8lZcPtfh+0OiVnYKk883KhUkA hdogekjQm6IKdBJmK8voG+1hQ3LM0BHpx6HzvJahAQnHDVxXYiBSVD5nf/7tuu6Y11tjAK5/ cL8uVqY4/nOkcM4fV65csl7zrriULmUhp/vTI7qM3stcfAE2zverIHu29j8wggM/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 IEZyZWVtYWlsIElzc3VpbmcgQ0ECAw5jHTAJBgUrDgMCGgUAoIIBpzAYBgkqhkiG9w0BCQMx CwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNjAyMjcxMzM3NTdaMCMGCSqGSIb3DQEJ BDEWBBR+V0ncY70Rk9+T/sigx9357Lc95zBSBgkqhkiG9w0BCQ8xRTBDMAoGCCqGSIb3DQMH MA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIB KDB4BgkrBgEEAYI3EAQxazBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwg SXNzdWluZyBDQQIDDmMdMHoGCyqGSIb3DQEJEAILMWugaTBiMQswCQYDVQQGEwJaQTElMCMG A1UEChMcVGhhd3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBl cnNvbmFsIEZyZWVtYWlsIElzc3VpbmcgQ0ECAw5jHTANBgkqhkiG9w0BAQEFAASCAQB07RQ2 2opnTkiyMDm+809olPVsRVqdpEiLZ4GtEoeTtgZoHCYr9+tRKdlUomPihbyt+8OgnCYfxk6x YWg8QTUKcfbuSd9aCihBppBqbmU/r2QGlpvCBlP2UIIij4NdVfPIfYcn7+XZ3R7WX0Brazns 566kcNCip+qJkilWKppab3G3sgpFzBd7DVTg0Vm3H20t+E543yrhaRtsqMR0HRVqFwQqfTtS m8DKiM7U5w1wOeafBojXbTzdETTOS+OLdHE32KZb/RYNv4Ym9EJK1giDEG/Fd+UlemXpdUc4 VlpcVSehaowDaKjN4CGPi4URA/3QNbCk4V7gJk9ZyZVHwq3DAAAAAAAA --------------ms060609040903010206030001-- From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 14:40:05 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54E5016A420 for ; Mon, 27 Feb 2006 14:40:05 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from hydra.bec.de (www.ostsee-abc.de [62.206.222.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BDA243D58 for ; Mon, 27 Feb 2006 14:40:03 +0000 (GMT) (envelope-from joerg@britannica.bec.de) Received: from britannica.bec.de (unknown [139.30.252.72]) by hydra.bec.de (Postfix) with ESMTP id 4872835707 for ; Mon, 27 Feb 2006 15:40:01 +0100 (CET) Received: by britannica.bec.de (Postfix, from userid 1000) id 2B3DD6C1E5; Mon, 27 Feb 2006 15:39:55 +0100 (CET) Date: Mon, 27 Feb 2006 15:39:55 +0100 From: joerg@britannica.bec.de To: freebsd-hackers@freebsd.org Message-ID: <20060227143954.GA812@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org References: <21474364.1141046445548.JavaMail.root@vms071.mailsrvcs.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <21474364.1141046445548.JavaMail.root@vms071.mailsrvcs.net> User-Agent: Mutt/1.5.11 Subject: Re: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 14:40:05 -0000 On Mon, Feb 27, 2006 at 07:20:45AM -0600, Sergey Babkin wrote: > Well, it's been a long story now. Every time someone comes > with the idea of adding init to BSD, other people feel very > strongly that they hate init and that it must not be in BSD. /sbin/init existed on BSD almost forever. You could fake a tty to use it for restarting the programs. But the real issue is what restart functionality the OP really wants. There's more than one way to do it and whether the SysV init approach is appropiate depends. E.g. what happens if some part of the configuration is rejected and the daemon just spins? Joerg From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 16:09:27 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 95E5A16A420 for ; Mon, 27 Feb 2006 16:09:27 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30FAB43D45 for ; Mon, 27 Feb 2006 16:09:27 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by zproxy.gmail.com with SMTP id x3so923299nzd for ; Mon, 27 Feb 2006 08:09:26 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=oV7WCmgTlkhA6u7p31EhJfT8o0EV5/Z/3cCRNndkXUQBeKcTcvDke3QTxUPSB8daC2I8K0DqXbrM7Yu2LAk4kAWEOnBXDyO0vbgbhFRu8fsTpgHQwk3yGFdKEzNPJ+Bf0xbp/5cT1b/VWN1kAn7d9C6qeBtn6w68eWFug3nB++o= Received: by 10.35.49.4 with SMTP id b4mr2068604pyk; Mon, 27 Feb 2006 08:09:26 -0800 (PST) Received: by 10.35.38.9 with HTTP; Mon, 27 Feb 2006 08:09:26 -0800 (PST) Message-ID: <79722fad0602270809p2229db83i5cb4cf0b24f91828@mail.gmail.com> Date: Mon, 27 Feb 2006 18:09:26 +0200 From: "Vlad GALU" To: "freebsd hackers" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Fastest timecounter ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 16:09:27 -0000 Dear hackers, I'm in a dilemma (more like a trilemma, actually). While following the 5.x and 6.x development cycle I observed that the default timecounter varies from one machine from another (for instance on my home desktop which is an AMD Athlon 2400+ it uses ACPI-fast, whereas on my Centrino-powered lappie it likes TSC better). I wrote a piece of software that has to get the current timestamp, one way or the other, a huge number of times per second. Apart from the empyrical tests one can perform to find out the timekeeping scheme with the less performance impact, is there any rule of thumb as to what choice to go for ? Any kind of advice is most welcome, especially reading material. P.S. I know that some of you may say that calling gettimeofday() that often is braindead, and at some point I agree. Unfortunatley, right now I can't do anything better. I need timekeeping to comb the algorithms that deal with my data structures a bit more, after which I can switch to time-related optimizations. -- If it's there, and you can see it, it's real. If it's not there, and you can see it, it's virtual. If it's there, and you can't see it, it's transparent. If it's not there, and you can't see it, you erased it. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 16:23:48 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 54E8516A420 for ; Mon, 27 Feb 2006 16:23:48 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: from xproxy.gmail.com (xproxy.gmail.com [66.249.82.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4527743D98 for ; Mon, 27 Feb 2006 16:23:30 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by xproxy.gmail.com with SMTP id i30so590566wxd for ; Mon, 27 Feb 2006 08:23:29 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=XL4XXRRzoYbWhbxMtzya5beJPgVqZULvnNtqRQq+cBCvHjwNFpJtM4P7LRt/efXNIZ/QBz+hWb2i+p9MoiXtjknnjxS8AopynLiZaQmSAUMjR63NAj2TWzhWAd0jbeznBG8OhgA9cAHtA4FS7DLKNt3v9Z5gbEUE4665+ljDQko= Received: by 10.70.54.20 with SMTP id c20mr544461wxa; Mon, 27 Feb 2006 08:23:29 -0800 (PST) Received: by 10.70.116.16 with HTTP; Mon, 27 Feb 2006 08:23:29 -0800 (PST) Message-ID: <84dead720602270823s34c18107te6e45a413dec5da7@mail.gmail.com> Date: Mon, 27 Feb 2006 21:53:29 +0530 From: "Joseph Koshy" To: "Vlad GALU" In-Reply-To: <79722fad0602270809p2229db83i5cb4cf0b24f91828@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <79722fad0602270809p2229db83i5cb4cf0b24f91828@mail.gmail.com> Cc: freebsd hackers Subject: Re: Fastest timecounter ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 16:23:48 -0000 vg> I wrote a piece of software that has to get the current vg> timestamp, one way or the other, a huge number of times per vg> second. Apart from the empyrical tests one can perform to vg> find out the timekeeping scheme with the less performance vg> impact, is there any rule of thumb as to what choice to go vg> for ? vg> Any kind of advice is most welcome, especially reading vg> material. vg> P.S. I know that some of you may say that calling vg> gettimeofday() that often is braindead, and at some vg> point I agree. Unfortunatley, right now I can't do vg> anything better. I need timekeeping to comb the vg> algorithms that deal with my data structures a bit more, vg> after which I can switch to time-related optimizations. If you just want a relative count (i.e., not absolute time) and if your machine's aren't going to be in sleep modes, you could use the RDTSC instruction directly. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 17:07:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31CBC16A420; Mon, 27 Feb 2006 17:07:18 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 441F443D60; Mon, 27 Feb 2006 17:07:17 +0000 (GMT) (envelope-from killing@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002332311.msg; Mon, 27 Feb 2006 17:06:58 +0000 Message-ID: <01c701c63bc0$36feb6a0$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , Date: Mon, 27 Feb 2006 17:06:51 -0000 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.2670 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Mon, 27 Feb 2006 17:06:58 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: killing@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Mon, 27 Feb 2006 17:06:59 +0000 Cc: Subject: HP Smart Array 6i opinions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 17:07:18 -0000 Has anyone had any dealings with the HP Smart Array 6i? Specifically looking for info on: * Performance * Disk failure recover * Available tools for monitoring etc. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 17:04:32 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 219AE16A420; Mon, 27 Feb 2006 17:04:32 +0000 (GMT) (envelope-from steven@multiplay.co.uk) Received: from multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 418D643D5E; Mon, 27 Feb 2006 17:04:24 +0000 (GMT) (envelope-from steven@multiplay.co.uk) Received: from vader ([212.135.219.179]) by multiplay.co.uk (multiplay.co.uk [85.236.96.23]) (MDaemon.PRO.v8.1.3.R) with ESMTP id md50002332304.msg; Mon, 27 Feb 2006 17:03:57 +0000 Message-ID: <01ba01c63bbf$cd7ea820$b3db87d4@multiplay.co.uk> From: "Steven Hartland" To: , Date: Mon, 27 Feb 2006 17:03:54 -0000 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.2670 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2670 X-Spam-Processed: multiplay.co.uk, Mon, 27 Feb 2006 17:03:57 +0000 (not processed: message from valid local sender) X-MDRemoteIP: 212.135.219.179 X-Return-Path: steven@multiplay.co.uk X-MDAV-Processed: multiplay.co.uk, Mon, 27 Feb 2006 17:04:00 +0000 X-Mailman-Approved-At: Mon, 27 Feb 2006 17:15:38 +0000 Cc: Subject: HP Smart Array 6i opinions X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 17:04:32 -0000 Has anyone had any dealings with the HP Smart Array 6i? Specifically looking for info on: * Performance * Disk failure recover * Available tools for monitoring etc. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone (023) 8024 3137 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 18:16:18 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 955A816A420 for ; Mon, 27 Feb 2006 18:16:18 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2C23343D48 for ; Mon, 27 Feb 2006 18:16:17 +0000 (GMT) (envelope-from pranav.sawargaonkar@gmail.com) Received: by wproxy.gmail.com with SMTP id 55so1218141wri for ; Mon, 27 Feb 2006 10:16:17 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=sYF4n/ws3z4oCnLc2E0L1vbUG11XATcE7KsBJPcNBUqCm5OAEhjFQrnH6JfRiaQzm+mlk4fJRBkmbdmBLvczn5Tk0D6oDU8K7LlfilXkqr0LTe2xNP9mKfruNOSs3MGKwmVPdUWZXtDdFWK2weDFrmeRMNr2GZCePjNpiBkW+Tk= Received: by 10.54.104.6 with SMTP id b6mr4436817wrc; Mon, 27 Feb 2006 10:16:17 -0800 (PST) Received: by 10.54.118.4 with HTTP; Mon, 27 Feb 2006 10:16:17 -0800 (PST) Message-ID: <5007e1a40602271016q1e85b782j88e5591358ce686e@mail.gmail.com> Date: Mon, 27 Feb 2006 23:46:17 +0530 From: "Pranav Sawargaonkar" To: freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Difference between signal related structures X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 18:16:18 -0000 Hi I am studying signaling related work in FreeBSD kernel just for learning. Can anybody tell me that why there are two different structures named 1)struct sigcontext 2)struct osigcontext are defined in /sys/i386/include/signal.h I want to know what is basic difference between them? Thanks in advance -Pranav Sawargaonkar From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 18:16:53 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9126D16A420 for ; Mon, 27 Feb 2006 18:16:53 +0000 (GMT) (envelope-from jos@catnook.com) Received: from w250.z064001178.sjc-ca.dsl.cnc.net (209-204-181-78.dsl.static.sonic.net [209.204.181.78]) by mx1.FreeBSD.org (Postfix) with SMTP id E075A43D60 for ; Mon, 27 Feb 2006 18:16:52 +0000 (GMT) (envelope-from jos@catnook.com) Received: (qmail 78288 invoked by uid 1000); 27 Feb 2006 18:20:03 -0000 Date: Mon, 27 Feb 2006 10:19:41 -0801 From: Jos Backus To: freebsd-hackers@freebsd.org Message-ID: <20060227182003.GB72394@lizzy.catnook.local> Mail-Followup-To: freebsd-hackers@freebsd.org References: <1602933046.20060227174132@kr.ru> <440300B5.4070402@rojer.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <440300B5.4070402@rojer.pp.ru> User-Agent: Mutt/1.5.11 Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jos@catnook.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 18:16:53 -0000 On Mon, Feb 27, 2006 at 04:37:57PM +0300, Deomid Ryabkov wrote: > Vitaliy Ovsyannikov wrote: > >Hello, freebsd-hackers. > > > > I've stuck with the unable to make watchdogs for daemons running via > >startup rc-scripts. In linux we can just put the process in the > >inittab. Does FreeBSD contains ability like this? > > > > > try sysutils/daemontools Or sysutils/mktool, which carries an "Apacheish" license. -- Jos Backus jos at catnook.com From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 18:31:50 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4711616A420 for ; Mon, 27 Feb 2006 18:31:50 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 99DF543D58 for ; Mon, 27 Feb 2006 18:31:44 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (iqc2mdz5jbblsey9@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k1RIVhTA037294; Mon, 27 Feb 2006 10:31:43 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k1RIVg2I037293; Mon, 27 Feb 2006 10:31:42 -0800 (PST) (envelope-from jmg) Date: Mon, 27 Feb 2006 10:31:42 -0800 From: John-Mark Gurney To: Tanmay Message-ID: <20060227183142.GJ840@funkthat.com> Mail-Followup-To: Tanmay , freebsd-hackers@freebsd.org References: 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-Operating-System: FreeBSD 5.4-RELEASE-p6 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-hackers@freebsd.org Subject: Re: Accessing address space of a process through kld!! X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 18:31:50 -0000 Tanmay wrote this message on Mon, Feb 27, 2006 at 13:56 +0530: > How do I access the address space ie text,data and stack of a (user > level)process whose pid I know from my kld. for eg: Suppose 'vi' is running > and I want to access its address space through my kld, then how do I do it? You look up the process with pfind(9), and then you can use uio(9) to transfer data into kernel space... Don't forget to PROC_UNLOCK the struct once you are done referencing it. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 19:19:08 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C88D16A42A for ; Mon, 27 Feb 2006 19:19:08 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms044pub.verizon.net (vms044pub.verizon.net [206.46.252.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 541F643D45 for ; Mon, 27 Feb 2006 19:19:08 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms075.mailsrvcs.net ([192.168.1.4]) by vms044.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IVD004RN1NVFEY3@vms044.mailsrvcs.net> for freebsd-hackers@freebsd.org; Mon, 27 Feb 2006 13:19:08 -0600 (CST) Date: Mon, 27 Feb 2006 13:19:07 -0600 (CST) From: Sergey Babkin To: Pranav Sawargaonkar , freebsd-hackers@freebsd.org Message-id: <31344186.1141067948033.JavaMail.root@vms075.mailsrvcs.net> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Mailman-Approved-At: Mon, 27 Feb 2006 19:26:55 +0000 Cc: Subject: Re: Difference between signal related structures X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 19:19:08 -0000 >From: Pranav Sawargaonkar >Hi >I am studying signaling related work in FreeBSD kernel just for learning. >Can anybody tell me that why there are two different structures named >1)struct sigcontext >2)struct osigcontext >are defined in /sys/i386/include/signal.h >I want to know what is basic difference between them? The one with "o" is "old". At some point the structure has been extended, and the old version got "o" added to its name. It's probably used for binary compatibility of the old programs, to convert the data between the old and new format. -SB From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 27 19:34:28 2006 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.ORG Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9001F16A424 for ; Mon, 27 Feb 2006 19:34:28 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5578343D70 for ; Mon, 27 Feb 2006 19:34:27 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (kqkxrlyaj90ah6pb@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.3/8.13.3) with ESMTP id k1RJYPfj039233; Mon, 27 Feb 2006 11:34:25 -0800 (PST) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.3/8.13.3/Submit) id k1RJYOn0039232; Mon, 27 Feb 2006 11:34:24 -0800 (PST) (envelope-from jmg) Date: Mon, 27 Feb 2006 11:34:23 -0800 From: John-Mark Gurney To: Vitaliy Ovsyannikov Message-ID: <20060227193423.GL840@funkthat.com> Mail-Followup-To: Vitaliy Ovsyannikov , freebsd-hackers@FreeBSD.ORG References: <1602933046.20060227174132@kr.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1602933046.20060227174132@kr.ru> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 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-hackers@FreeBSD.ORG Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 19:34:28 -0000 Vitaliy Ovsyannikov wrote this message on Mon, Feb 27, 2006 at 17:41 +0700: > I've stuck with the unable to make watchdogs for daemons running via > startup rc-scripts. In linux we can just put the process in the > inittab. Does FreeBSD contains ability like this? yes, you can use ttys(5) for this... You will get an extra argument or two... but a wrapper script can handle that for you... Though you need to have the daemon run in foreground mode, so that when it dies init knows it did, and restarts it... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 28 00:09:59 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4852316A420 for ; Tue, 28 Feb 2006 00:09:59 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id D476043D46 for ; Tue, 28 Feb 2006 00:09:58 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1] (may be forged)) by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id k1S07OW1078971; Mon, 27 Feb 2006 17:07:29 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 27 Feb 2006 17:07:29 -0700 (MST) Message-Id: <20060227.170729.122315042.imp@bsdimp.com> To: doconnor@gsoft.com.au From: "M. Warner Losh" In-Reply-To: <200602272312.17567.doconnor@gsoft.com.au> References: <200602272154.03459.doconnor@gsoft.com.au> <20060227120336.GA4233@droopy.unibe.ch> <200602272312.17567.doconnor@gsoft.com.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 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0 (harmony.bsdimp.com [127.0.0.1]); Mon, 27 Feb 2006 17:07:31 -0700 (MST) Cc: freebsd-hackers@freebsd.org, roth@iam.unibe.ch Subject: Re: unversal watchdog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 00:09:59 -0000 In message: <200602272312.17567.doconnor@gsoft.com.au> "Daniel O'Connor" writes: : As to answer the question - I am not aware of any facility for automatically : restarting things (unless you can get init to do it via /etc/ttys somehow) : : I don't think it would be too hard to create a shell wrapper script though : (kind of annoying I admit) Actually, putting it in /etc/ttys with a fake device name is the canonical way to get this functionality. We do it all the time at work and it works out well. Warner From owner-freebsd-hackers@FreeBSD.ORG Tue Feb 28 01:53:00 2006 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A65B16A420 for ; Tue, 28 Feb 2006 01:53:00 +0000 (GMT) (envelope-from me@carrollkong.com) Received: from mail.faerunconsulting.com (vzdsl-jcnj-216-182-31-61.static.tellurian.net [216.182.31.61]) by mx1.FreeBSD.org (Postfix) with SMTP id 2220543D48 for ; Tue, 28 Feb 2006 01:52:58 +0000 (GMT) (envelope-from me@carrollkong.com) Received: (qmail 88741 invoked from network); 28 Feb 2006 01:52:57 -0000 Received: from unknown (HELO athena) (192.168.0.2) by dmz.faerunhome.com with SMTP; 28 Feb 2006 01:52:57 -0000 From: "Carroll Kong" To: Date: Mon, 27 Feb 2006 20:52:57 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Thread-Index: AcY8CbIWzZo0izQhTH+KVM6Em5BJow== Message-Id: <20060228015258.2220543D48@mx1.FreeBSD.org> Cc: Subject: FreeBSD 4.11 P13 Crash X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Feb 2006 01:53:01 -0000 Okay this time my kernel was recompiled so there are no modules to make = it easier to see all of the symbols. Sometimes the box cycles through the fatal traps 12. Other times it = does not. Based on my other Fatal trap errors, it seems to interrupt more = often with the m_tag_delete function. I don't think this necessarily means = the problem is with IPFilter or PPP mostly because this box acts as a = firewall and logs constantly. Therefore, it is not surprising it always fails = after logging with IPFilter, but I am always open to the possibility. This box was stable before I upgraded from 4.9->4.11. Among one of the software changes was probably the change of IPFilter. I used to use the IPFilter 3.4.33pre modules, but after I moved to 4.11 I just used the distribution packaged 3.4.35. This might be the source of the problem, = but I could not google for relevant entries. I have since swapped the RAM, motherboard, RAM again (I bought another = stick thinking maybe my new RAM was coincidentally bugged), one of the Intel = NICs, and my 3Ware controller. The problem still occurred and actually more frequently. The usual frequency was about 14 days or so. It just = crashed in less than 23 hours and then again within 25 minutes. The final pieces of hardware that still can be swapped is the other = Intel NIC (but this NIC is NOT connected to the PPPoE), CPU, Power Supply, = CDROM (not used), Harddisks, or Case. :) I tried disabling physical swap completely, and the system still = crashed, so I doubt it is the 3Ware, but who knows. So far I am thinking - IPFilter intermittent bug with some packets, but I run a box with 112 = days of uptime with the same version of IPFilter, albeit not with 4 NICs. - 3Ware driver is flakey, but I have a 4.10 box with 3Ware that is = somewhat stable - CPU (I would tend to think this would result in HARD lock ups vs Fatal Trap 12s though) - PowerSupply (I suppose anything is possible, please note it is on an = APC UPS, but the power supply might be delivering bad juice?) - Harddisks and 3Ware driver have incompatible firmware issue, I doubt = this is it though since I purchased new Seagates in 9/2004 for the RAID1, = then I added another Seagate as a JBOD, and that disk is not being written to during the crash. I am tempted to consider upgrading to 5.X, but I am a conservative = person and somehow doubt 4.X is the source of the problem as the system worked = fine for over a year. The box does a lot of things however I omitted this information to avoid flooding the list with too much information since it has worked fine for = a year in the past. As a note, the problem is NOT load related. In fact, = one time the fatal panic said the running process was "idle". :) = Furthermore, I haven't really updated the software unnecessarily except for security issues and the system has been stable in the past with the same hardware = and same software. I am very conservative when it comes to servers, so this seems like a hardware issue but I already swapped so much of it, I am beginning to wonder. I am going to buy a new CPU and power supply as I have replaced nearly = every other part by now. I have included my dmesg, nm greps for the functions, a backtrace, uname output. I have the kernel dump so if there are any commands someone = needs me to punch through, I will gladly do so. I included some of my own = feeble debugging. I didn't like the line that said "address is out of bounds" = in one of the mbuf structures. I am guessing that means the mbuf was = already corrupted way before we got there. Any suggestions and advice are = welcome. Thanks in advance! Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc11e4402 fault code =3D supervisor write, page not present instruction pointer =3D 0x8:0xc018ffcf stack pointer =3D 0x10:0xc02fa6f0 frame pointer =3D 0x10:0xc02fa704 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D Idle interrupt mask =3D net tty bio cam=20 trap number =3D 12 panic: page fault Uptime: 6h5m10s twe0: Cannot delete unit. error =3D 16 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xc11e4402 fault code =3D supervisor write, page not present instruction pointer =3D 0x8:0xc018ffcf stack pointer =3D 0x10:0xc02fa444 frame pointer =3D 0x10:0xc02fa458 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D Idle interrupt mask =3D net tty bio cam=20 tx0, limit 0xfffff, type 0x1b nm -n /kernel | grep c018f=20 c018f058 T accept_filt_del c018f07c T accept_filt_get c018f0b4 T accept_filt_generic_mod_event c018f134 t net_init_domain c018f1bc T net_add_domain c018f1ec t domaininit c018f244 T pffindtype c018f290 T pffindproto c018f304 T pfctlinput c018f34c T pfctlinput2 c018f3a4 t pfslowtimo c018f3fc t pffasttimo c018f45c t tunable_mbinit c018f4ac t mbinit c018f53c T m_mballoc c018f5f8 T m_mballoc_wait c018f7e8 T m_clalloc c018f8b4 T m_clalloc_wait c018f9a0 T m_retry c018fa74 T m_retryhdr c018fb60 t m_reclaim c018fbb0 T m_get c018fc54 T m_gethdr c018fd0c T m_getclr c018fdd0 T m_getcl ------------------------------------------------------------------- Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0x28067100 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc0192696 stack pointer =3D 0x10:0xd71cbbd0 frame pointer =3D 0x10:0xd71cbbd8 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 110 (ppp) interrupt mask =3D net tty=20 trap number =3D 12 panic: page fault syncing disks... 7=20 done Uptime: 25m51s twe0: Cannot delete unit. error =3D 16 dumping to dev #twed/0x20001, offset 3146240 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 = 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 = 475 474 473 472 471 470 469 468 467 466 465 464 463 462 461 460 459 458 457 = 456 455 454 453 452 451 450 449 448 447 446 445 444 443 442 441 440 439 438 = 437 436 435 434 433 432 431 430 429 428 427 426 425 424 423 422 421 420 419 = 418 417 416 415 414 413 412 411 410 409 408 407 406 405 404 403 402 401 400 = 399 398 397 396 395 394 393 392 391 390 389 388 387 386 385 384 383 382 381 = 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 364 363 362 = 361 360 359 358 357 356 355 354 353 352 351 350 349 348 347 346 345 344 343 = 342 341 340 339 338 337 336 335 334 333 332 331 330 329 328 327 326 325 324 = 323 322 321 320 319 318 317 316 315 314 313 312 311 310 309 308 307 306 305 = 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 289 288 287 286 = 285 284 283 282 281 280 279 278 277 276 275 274 273 272 271 270 269 268 267 = 266 265 264 263 262 261 260 259 258 257 256 255 254 253 252 251 250 249 248 = 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 231 230 229 = 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 210 = 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 = 190 189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 = 171 170 169 168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 = 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 = 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 = 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 = 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 = 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 = 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 = 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 succeeded Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... nm -n /kernel | grep c01926=20 c0192600 T m_tag_free c0192614 T m_tag_prepend c0192628 T m_tag_unlink c0192658 T m_tag_delete c0192674 T m_tag_delete_chain c01926ac T m_tag_locate c01926e8 T m_tag_copy --------------- (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:487 #1 0xc0173f3f in boot (howto=3D256) at ../../kern/kern_shutdown.c:316 #2 0xc0174364 in poweroff_wait (junk=3D0xc02f2aac, howto=3D-1070651985) = at ../../kern/kern_shutdown.c:595 #3 0xc02a77ba in trap_fatal (frame=3D0xd71cbb90, eva=3D671510784) at ../../i386/i386/trap.c:974 #4 0xc02a748d in trap_pfault (frame=3D0xd71cbb90, usermode=3D0, = eva=3D671510784) at ../../i386/i386/trap.c:867 #5 0xc02a704b in trap (frame=3D{tf_fs =3D -1072562160, tf_es =3D 16, = tf_ds =3D -686030832, tf_edi =3D 6757530, tf_esi =3D -1055667456,=20 tf_ebp =3D -685982760, tf_isp =3D -685982788, tf_ebx =3D = 671510784, tf_edx =3D 6757530, tf_ecx =3D -1056411648, tf_eax =3D 28672,=20 tf_trapno =3D 12, tf_err =3D 0, tf_eip =3D -1072093546, tf_cs =3D = 8, tf_eflags =3D 66054, tf_esp =3D -1055667456, tf_ss =3D -1055667456}) at ../../i386/i386/trap.c:466 #6 0xc0192696 in m_tag_delete_chain (m=3D0xc113cb00, t=3D0x0) at ../../kern/uipc_mbuf2.c:358 #7 0xc01904d3 in m_free (m=3D0xc113cb00) at ../../kern/uipc_mbuf.c:734 #8 0xc0190606 in m_freem (m=3D0xc1094000) at ../../kern/uipc_mbuf.c:763 #9 0xc0127df8 in fr_check (ip=3D0xc1094030, hlen=3D20, = ifp=3D0xc21a7008, out=3D0, mp=3D0xd71cbce8) at ../../contrib/ipfilter/netinet/fil.c:1387 #10 0xc01d7d06 in ip_input (m=3D0xc1094000) at = ../../netinet/ip_input.c:478 #11 0xc01d838b in ipintr () at ../../netinet/ip_input.c:971 #12 0xc0299ee9 in swi_net_next () #13 0xc016e7c8 in lockmgr (lkp=3D0xc21a7100, flags=3D16973826, interlkp=3D0xd71c0bac, p=3D0xd48bd5a0) at ../../kern/kern_lock.c:355 #14 0xc019fda8 in vop_stdlock (ap=3D0xd71cbdd0) at ../../kern/vfs_default.c:256 #15 0xc025a9c9 in ufs_vnoperatespec (ap=3D0xd71cbdd0) at ../../ufs/ufs/ufs_vnops.c:2394 #16 0xc01a9ffd in vn_lock (vp=3D0xd71c0b40, flags=3D131074, = p=3D0xd48bd5a0) at vnode_if.h:861 #17 0xc01ad842 in spec_write (ap=3D0xd71cbe64) at ../../miscfs/specfs/spec_vnops.c:284 #18 0xc025a3ac in ufsspec_write (ap=3D0xd71cbe64) at ../../ufs/ufs/ufs_vnops.c:1827 #19 0xc025a9c9 in ufs_vnoperatespec (ap=3D0xd71cbe64) at ../../ufs/ufs/ufs_vnops.c:2394 #20 0xc01a9b9a in vn_write (fp=3D0xc219b100, uio=3D0xd71cbed4, = cred=3D0xc2197080, flags=3D0, p=3D0xd48bd5a0) at vnode_if.h:363 #21 0xc018330d in dofilewrite (p=3D0xd48bd5a0, fp=3D0xc219b100, fd=3D9, buf=3D0xbfbfe89c, nbyte=3D580, offset=3D-1, flags=3D0) at ../../sys/file.h:163 #22 0xc01831c6 in write (p=3D0xd48bd5a0, uap=3D0xd71cbf80) at ../../kern/sys_generic.c:329 #23 0xc02a7a69 in syscall2 (frame=3D{tf_fs =3D -1078001617, tf_es =3D = 134938671, tf_ds =3D -1078001617, tf_edi =3D 135090176, tf_esi =3D 580,=20 tf_ebp =3D -1077940064, tf_isp =3D -685981740, tf_ebx =3D = -1077942112, tf_edx =3D 0, tf_ecx =3D 13, tf_eax =3D 4, tf_trapno =3D 7,=20 tf_err =3D 2, tf_eip =3D 673683504, tf_cs =3D 31, tf_eflags =3D = 663, tf_esp =3D -1077942172, tf_ss =3D 47}) at ../../i386/i386/trap.c:1175 #24 0xc0298a85 in Xint0x80_syscall () #25 0x80655de in ?? () #26 0x806c2fb in ?? () #27 0x806c21d in ?? () #28 0x807470a in ?? () #29 0x8083a78 in ?? () #30 0x805b84b in ?? () #31 0x804d484 in ?? () #32 0x806ed77 in ?? () #33 0x806e967 in ?? () #34 0x804b62a in ?? () (kgdb) f 11 #11 0xc01d838b in ipintr () at ../../netinet/ip_input.c:971 971 ip_input(m); (kgdb) print *m $13 =3D {m_hdr =3D {mh_next =3D 0xc1128100, mh_nextpkt =3D 0x0, mh_data = =3D 0xc1094030 "E", mh_len =3D 208, mh_type =3D 0, mh_flags =3D 2},=20 M_dat =3D {MH =3D {MH_pkthdr =3D {rcvif =3D 0xc21a7008, len =3D 576, = header =3D 0x0, csum_flags =3D 0, csum_data =3D 0, tags =3D { slh_first =3D 0x0}}, MH_dat =3D {MH_ext =3D {ext_buf =3D = 0x2000000
, ext_free =3D 0x2400045,=20 ext_size =3D 28454, ext_ref =3D 0x6d3d012e},=20 MH_databuf =3D "\000\000\000\002E\000@\002&o\000\000.\001=3Dm;=BD=F30=D8=B6\037=3D\003\0= 01=BA\006\000\000 \000\000E\000\005=C8=E9=BA@\000/\006=A2t=D8=B6\037=3D=C0=A8\001e'B\rmy=BB= 6\216^\222@\002P\020=E1\0 00=B1=A1\000\000\000\000@\t\a\000\000\002r\000\003=C0\000\227=AB\212!\225= @\204]\001\ 214\027=C1=F9\177\232=F9=E3=F2\222\016\000=F9au1=3D\216=DD\204=A8\207O\00= 2+=F80=E9H=F0\eD\2056n\001=F7 U\025=E0\222=FE\f:S=F5PI\037)T=D8(=FD=A8\r=D3@\210=EA\217(S=F5c=E2=E9=B8\= n?\217%x&=B5\177=F4UqX\222\020\ 225\\=D1=D9~\fh=EA=A9\036\t\"Az\206=E1p=FE+}=C7=A3=A3=A2"...}},=20 M_databuf =3D "\bp\032=C2@\002", '\000' , "\002E\000@\002&o\000\000.\001=3Dm;=BD=F30=D8=B6\037=3D\003\001=BA\006\00= 0\000\000\000E\00 0\005=C8=E9=BA@\000/\006=A2t=D8=B6\037=3D=C0=A8\001e'B\rmy=BB6\216^\222@\= 002P\020=E1\000=B1=A1\000\000 \000\000@\t\a\000\000\002r\000\003=C0\000\227=AB\212!\225@\204]\001\214\0= 27=C1=F9\17 7\232=F9=E3=F2\222\016\000=F9au1=3D\216=DD\204=A8\207O\002+=F80=E9H=F0\eD= \2056n\001=F7U\025=E0\222=FE\ f:S=F5PI\037)T=D8(=FD=A8\r=D3@\210=EA\217(S=F5c=E2=E9=B8\n?\217%x&=B5\177= =F4UqX\222\020\225\\=D1=D9~\fh=EA =A9\036\t"...}} (kgdb) f 6 #6 0xc0192696 in m_tag_delete_chain (m=3D0xc113cb00, t=3D0x0) at ../../kern/uipc_mbuf2.c:358 358 m_tag_delete(m, q); (kgdb) print *m $14 =3D {m_hdr =3D {mh_next =3D 0xc113ca00, mh_nextpkt =3D 0x280ef4cd, = mh_data =3D 0x14
, mh_len =3D 663,=20 mh_type =3D 28672, mh_flags =3D 10246}, M_dat =3D {MH =3D {MH_pkthdr = =3D {rcvif =3D 0x280ef492, len =3D 672120748, header =3D 0x2,=20 csum_flags =3D 16384, csum_data =3D 1, tags =3D {slh_first =3D = 0x28067100}}, MH_dat =3D {MH_ext =3D { ext_buf =3D 0x28067200
, = ext_free =3D 0x280541fd, ext_size =3D 134516476,=20 ext_ref =3D 0x280819da},=20 MH_databuf =3D "\000r\006(=FDA\005(=FC\216\004\b=DA\031\b(\000\000\000\000=A2A\005(=A8:\= 006(@\200\006 (\000\000\000\000\000\000\000\000`=FB=BF=BF@\200\006\001\234=FB=BF=BFOA\0= 05(=FC\216\004\b\ 004=CFe\000\000r\006(\001\000\000\000=A8:\006(\000p\006(=FC\216\004\b=FDA= \005(=FC\216\ 004\b\t\013\005(\200=E6\020(=A2A\005(=A8:\006(\000=E9\a(\200=3D\006(\227?= \005(5(\005(=A8 :\006(\f=FC=BF=BF=CF@\005( \006\005(\004=CFe\000\200=3D\006(\001\000\000\000\000p\006(\000q\006(\000= r\006(=DA >\005(=A8:\006(\000p\006(=FC\216\004\b=D0=FC=BF=BFS=D4\004\b\200=E6\020(@= \005\b\000r\006("...}},=20 M_databuf =3D "\222=F4\016(=AC=BF\017(\002\000\000\000\000@\000\000\001\000\000\000\000= q\006(\00 0r\006(=FDA\005(=FC\216\004\b=DA\031\b(\000\000\000\000=A2A\005(=A8:\006(= @\200\006(\00 0\000\000\000\000\000\000\000`=FB=BF=BF@\200\006\001\234=FB=BF=BFOA\005(=FC= \216\004\b\004=CF e\000\000r\006(\001\000\000\000=A8:\006(\000p\006(=FC\216\004\b=FDA\005(=FC= \216\004\ b\t\013\005(\200=E6\020(=A2A\005(=A8:\006(\000=E9\a(\200=3D\006(\227?\005= (5(\005(=A8:\00 6(\f=FC=BF=BF=CF@\005( \006\005(\004=CFe\000\200=3D\006(\001\000\000\000\000p\006(\000q\006(\000= r\006(=DA >\005(=A8:\006(\000p\006("...}} (kgdb) print *q Cannot access memory at address 0x0. (kgdb)=20 ---------------------------- Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD 4.11-RELEASE-p13 #3: Thu Feb 23 13:09:31 EST 2006 damascus@daemon.faerunhome.com:/usr/src/sys/compile/DAEMON Timecounter "i8254" frequency 1193182 Hz CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1993.54-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0xf24 Stepping =3D 4 =20 Features=3D0x3febfbff real memory =3D 536608768 (524032K bytes) avail memory =3D 518377472 (506228K bytes) Preloaded elf kernel "kernel" at 0xc03af000. Warning: Pentium 4 CPU: PSE disabled Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 11 entries at 0xc00f28c0 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pcib2: at device 30.0 on = pci0 pci2: on pcib2 twe0: <3ware Storage Controller driver ver. 1.40.01.002> port = 0xdfa0-0xdfaf mem 0xfe000000-0xfe7fffff,0xfeafec00-0xfeafec0f irq 9 at device 9.0 on = pci2 twe0: 4 ports, Firmware FE7X 1.05.00.068, BIOS BE7X 1.08.00.048 fxp0: port 0xdf00-0xdf3f mem 0xfeaa0000-0xfeabffff,0xfeafd000-0xfeafdfff irq 11 at device 10.0 on = pci2 fxp0: Ethernet address 00:02:b3:d0:e3:73 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0xde80-0xdebf mem 0xfea80000-0xfea9ffff,0xfeafc000-0xfeafcfff irq 10 at device 11.0 on = pci2 fxp1: Ethernet address 00:02:b3:ee:65:88 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp2: port 0xdd80-0xddbf mem 0xfea40000-0xfea5ffff,0xfeafb000-0xfeafbfff irq 11 at device 12.0 on = pci2 fxp2: Ethernet address 00:11:11:c1:a2:e5 inphy2: on miibus2 inphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp3: port 0xdd00-0xdd3f mem 0xfea20000-0xfea3ffff,0xfeafa000-0xfeafafff irq 11 at device 13.0 on = pci2 fxp3: Ethernet address 00:11:11:c1:a2:e7 inphy3: on miibus3 inphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci0: port 0xdcc0-0xdcff,0xdfe0-0xdfe3,0xdf98-0xdf9f,0xdfe4-0xdfe7,0xdff0-0xdff7 = mem 0xfe9e0000-0xfe9fffff irq 11 at device 14.0 on pci2 ata2: at 0xdff0 on atapci0 ata3: at 0xdf98 on atapci0 pci2: at 15.0 irq 11 isab0: at device 31.0 on = pci0 isa0: on isab0 atapci1: port 0xffa0-0xffaf at device = 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: at 0x170 irq 15 on atapci1 uhci0: port = 0xef40-0xef5f irq 11 at device 31.2 on pci0 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 pci0: (vendor=3D0x8086, dev=3D0x2443) at 31.3 irq 11 uhci1: port = 0xef80-0xef9f irq 10 at device 31.4 on pci0 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 orm0: