From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 03:03:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C32016A4DA for ; Sun, 9 Jul 2006 03:03:26 +0000 (UTC) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id A657843D49 for ; Sun, 9 Jul 2006 03:03:25 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.4) id k6933PVJ005412; Sat, 8 Jul 2006 22:03:25 -0500 (CDT) (envelope-from dan) Date: Sat, 8 Jul 2006 22:03:25 -0500 From: Dan Nelson To: Kim Culhan Message-ID: <20060709030324.GA87129@dan.emsphone.com> References: <89dbfdc30607081352g2c9eca00n738ee4e77dd3335d@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <89dbfdc30607081352g2c9eca00n738ee4e77dd3335d@mail.gmail.com> X-OS: FreeBSD 5.5-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.11 Cc: freebsd-stable@freebsd.org Subject: Re: gmake: virtual memory exhausted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 03:03:26 -0000 In the last episode (Jul 08), Kim Culhan said: > Greetings- > > Compiling Asterisk on 6.1-STABLE: > > gmake -C db1-ast libdb1.a > gmake[1]: Entering directory `/usr/local/src/asterisk/asterisk/db1-ast' > gmake[1]: *** virtual memory exhausted. Stop. > > Any suggestion of a tuning parameter to work around this is > greatly appreciated. Does the port compile? -- Dan Nelson dnelson@allantgroup.com From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 07:44:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 673F116A4DA for ; Sun, 9 Jul 2006 07:44:27 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd4mo1so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0AA7F43D45 for ; Sun, 9 Jul 2006 07:44:26 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mr2so.prod.shaw.ca (pd2mr2so-qfe3.prod.shaw.ca [10.0.141.109]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J2400LSYLF27W80@l-daemon> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 01:42:38 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd2mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J2400AYOLF2G9C0@pd2mr2so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 01:42:38 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0J2400GK7LF1T2W0@l-daemon> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 01:42:38 -0600 (MDT) Received: (qmail 39924 invoked from network); Sun, 09 Jul 2006 07:42:32 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Sun, 09 Jul 2006 07:42:32 +0000 Date: Sun, 09 Jul 2006 00:42:31 -0700 From: Colin Percival To: FreeBSD Stable Message-id: <44B0B367.1020406@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 User-Agent: Thunderbird 1.5 (X11/20060416) Subject: FreeBSD 6.0->6.1 binary upgrade script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 07:44:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear FreeBSD 6.0 users, Those of you who read my blog (http://www.daemonology.net/blog/) will have seen this already; but for those of you who don't: I have written an automatic script for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. This script will install exactly the same files as are distributed on the ISO image, and it will attempt to automatically merge configuration file changes (in the very unlikely case that it cannot automatically merge changes, it will ask you to merge the changes for it). The script takes approximately 15 minutes, and typically downloads under 20MB of files and binary patches. Naturally, the cryptographic hashes of all the files are verified against values stored in the script, so as long as you trust the FreeBSD Security Officer (and if you don't, why are you running FreeBSD?), the process is entirely secure. The script can be obtained from http://www.daemonology.net/freebsd-upgrade-6.0-to-6.1/ and the SHA256 hash of the download is 29075fc5711e0b20d879c69d12bbe5414c1c56d597c8116da7acc0d291116d2f . Colin Percival FreeBSD Security Officer -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEsLNnMt4ezdCTR/wRAmRUAKDQFOFxK3y58/vy0Vzx8sov8synWgCg4sYG UfDhAxNjWRq7+zawVvM8cp0= =3gBy -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 08:46:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C05716A4E1; Sun, 9 Jul 2006 08:46:51 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail25.syd.optusnet.com.au (mail25.syd.optusnet.com.au [211.29.133.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id C958043D46; Sun, 9 Jul 2006 08:46:50 +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 mail25.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k698kmNH020839 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sun, 9 Jul 2006 18:46:49 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k698kmvj028562; Sun, 9 Jul 2006 18:46:48 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k698kmVD028561; Sun, 9 Jul 2006 18:46:48 +1000 (EST) (envelope-from peter) Date: Sun, 9 Jul 2006 18:46:48 +1000 From: Peter Jeremy To: Colin Percival Message-ID: <20060709084648.GC719@turion.vk2pj.dyndns.org> References: <44B0B367.1020406@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="w7PDEPdKQumQfZlR" Content-Disposition: inline In-Reply-To: <44B0B367.1020406@freebsd.org> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: FreeBSD Stable Subject: Re: FreeBSD 6.0->6.1 binary upgrade script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 08:46:51 -0000 --w7PDEPdKQumQfZlR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2006-Jul-09 00:42:31 -0700, Colin Percival wrote: > I have written an automatic script >for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. That sounds useful. Are you intending to provide this for future FreeBSD minor-revision releases? >Naturally, the cryptographic hashes of all the files are verified >against values stored in the script, so as long as you trust the >FreeBSD Security Officer (and if you don't, why are you running >FreeBSD?), the process is entirely secure. But how can I tell that the script came from the FreeBSD Security Officer? You have signed your mail with a key (ID 0xD09347FC) that claims to be a Colin Percival with an Oxford Uni address (whereas this mail has a freebsd.org address) but the key that I downloaded from a PGP keyserver has no other signatures. You don't have a key in the FreeBSD CVS repository that I can locate and I can't find any keys on www.daemonology.net. Basically, I only have your word that you are who you claim to be. (Of course, I still need to be able to trust the FreeBSD CVS repository but if I can't trust that, I can't trust my OS either). If you really are the FreeBSD Security Officer why can't I find copies of your key and FreeBSD SO key (0xCA6CDFB2) that are counter-signed by each other? --=20 Peter Jeremy --w7PDEPdKQumQfZlR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsMJ3/opHv/APuIcRAvOdAJ0ZwnMVKJ5RXXKmblnkio0ei52uMQCfSEno nat0bDmI97NSKK170/bBB0c= =1DFq -----END PGP SIGNATURE----- --w7PDEPdKQumQfZlR-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 08:58:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8286D16A4DE for ; Sun, 9 Jul 2006 08:58:36 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd4mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1CF1143D45 for ; Sun, 9 Jul 2006 08:58:36 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd2mr2so.prod.shaw.ca (pd2mr2so-qfe3.prod.shaw.ca [10.0.141.109]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J2400HQ0OXN7RC0@l-daemon> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 02:58:35 -0600 (MDT) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd2mr2so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0J2400M9KOXNDO20@pd2mr2so.prod.shaw.ca> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 02:58:35 -0600 (MDT) Received: from hexahedron.daemonology.net ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with SMTP id <0J2400GGAOXMT2X0@l-daemon> for freebsd-stable@freebsd.org; Sun, 09 Jul 2006 02:58:35 -0600 (MDT) Received: (qmail 40164 invoked from network); Sun, 09 Jul 2006 08:58:29 +0000 Received: from unknown (HELO ?127.0.0.1?) (127.0.0.1) by localhost with SMTP; Sun, 09 Jul 2006 08:58:29 +0000 Date: Sun, 09 Jul 2006 01:58:28 -0700 From: Colin Percival In-reply-to: <20060709084648.GC719@turion.vk2pj.dyndns.org> To: Peter Jeremy Message-id: <44B0C534.5030207@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 References: <44B0B367.1020406@freebsd.org> <20060709084648.GC719@turion.vk2pj.dyndns.org> User-Agent: Thunderbird 1.5 (X11/20060416) Cc: FreeBSD Stable Subject: Re: FreeBSD 6.0->6.1 binary upgrade script X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 08:58:36 -0000 Peter Jeremy wrote: > On Sun, 2006-Jul-09 00:42:31 -0700, Colin Percival wrote: >> I have written an automatic script >> for performing binary FreeBSD 6.0 -> FreeBSD 6.1 upgrades. > > That sounds useful. Are you intending to provide this for future > FreeBSD minor-revision releases? Yes. This is made much easier by the work I'm doing rewriting FreeBSD Update. > But how can I tell that the script came from the FreeBSD Security > Officer? You have signed your mail with a key (ID 0xD09347FC) that > claims to be a Colin Percival with an Oxford Uni address (whereas this > mail has a freebsd.org address) but the key that I downloaded from a > PGP keyserver has no other signatures. You don't have a key in the > FreeBSD CVS repository that I can locate Oops. I really ought to add my key there some day -- it hasn't mattered until now since I've always signed security-related emails with the SO key. Here's my PGP public key, which you will note is signed with the FreeBSD Security Officer key. -----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.4.3 (FreeBSD) mQGiBD5ST1YRBADxgAihxhkd5+87xPxAD3OvMzKKrAhWX9VPaABzjrQmDJrJ0cyb Boa6+aHlnaFZYEIv7DVDylNg5aUDRRDJOrKeWnSXs9Kizg9+ek/3V6202Z5mZiBG YjShN2nhApkTHTN0QfogOEXmY9BHzJzHix75fJZ5wk4q4X28FKVCReoeAwCg/2p/ rgnDBQFkJy/0Lnj6MZQw2KkEAKQ/nNK/KlKNlfA5KAuqS16l1WQKgOP+ispUoaVN arhTU7NCB+UKBAJHPQVeVAe+UvgeUhjh7psCp9C1Au0hmxnpluF1ljknRUzF2WlX ql38/1cHT2RxHr9i/fG8hHQCQkRLp1k01n7rVTzXX3j/K0V+CVbGWIJK7h47ceEL 4tk9A/0T7H1vCeuiu50aMDaigCOmd1XQb+dZlEs50mzLlC1mwtTodRBLqo3Ol78R nZ7DN73AHH7w2197kJ0I10dA6Q5MpScfXKUtnUuItSxv59E9O7SDus6ya77L0lCR cooYL49EuB/pwL/P+c/p+Ki9TmzauGE3Wji6gDH7kH/aVMFwwbQvQ29saW4gUGVy Y2l2YWwgPGNvbGluLnBlcmNpdmFsQHdhZGhhbS5veC5hYy51az6IWAQQEQIAGAUC PlJPVggLCQgHAwIBCgIZAQUbAwAAAAAKCRAy3h7N0JNH/EDpAKDEN7HNTjpDEf0K hlVxk8c868mrLwCcDDQ7TEi4XqeonghuoWYRE/oooq+IRgQQEQIABgUCQnhSngAK CRAV1ogEymzfsiShAJ4yFvxZXVWbuzG9lyZLgoUVeQ55FACfeVwS0Clf+93BByQq U0E8HE4rXsm0JUNvbGluIFBlcmNpdmFsIDxjcGVyY2l2YUBmcmVlYnNkLm9yZz6I TwQQEQIADwUCQSYZ3AgLCQgHAwIBCgAKCRAy3h7N0JNH/JU9AKCZEbOE4KD5FRmz xUhoJRJOKS6prwCeNNqyRB+lTg9006K7LAgMLYuUrDuIRgQQEQIABgUCQnhSpQAK CRAV1ogEymzfsivAAJ97Vk22Grq9IrmnKfQY3DHlReLBrQCeO7KaNWoct9y8t2FG pAiqEM02Kl25Ag0EPlJPVhAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg 2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvO meFXklnN/biudE/F/Ha8g8VHMGHOfMlm/xX5u/2RXscBqtNbno2gpXI61Brwv0YA WCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMcfFstjvbzySPAQ/ClWxiNjrtV jLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZ lp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVekyCzsAAgIIAPIwHNo3BY8l 8T54p1GbRXqGxw10B7/wuxc6XgdfDfJOMOjn48+O0LNwyWXWLPR5apGaqlubzG+O okQNP8okLQ5W6vRh09/Y3XfAlHh5nx5bwEFOmrRJPKvyZIY/KjvAA8PAgCIRKVfH IzUqvXbjESrzMuskkxoVRVyrx52FHx6XqQWGY+DJJV9VFDSxzwfq9K4JHQ3yRm7G 75hrPXUB8VC28mOLCEwwkKNyh9PQj27PEwjErPLJ0gKkkK0cfnvcv6pMBkRAHfL7 RqM4Z4yqqfaofS3B50Nr6dvpPx2Xyus3y03Zr9QZuKfFVYJ6Gb3oZuJnRXT5XIwD 5Fiw/V3xaD6ITAQYEQIADAUCPlJPVgUbDAAAAAAKCRAy3h7N0JNH/BntAKD/JPN0 g8NrWUVUfiKonbtL1vgMEgCdH+G2T8UJC2wyRTdp4+Io42+tsA0= =7ABx -----END PGP PUBLIC KEY BLOCK----- Colin Percival From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 13:23:58 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04BD516A4DA for ; Sun, 9 Jul 2006 13:23:58 +0000 (UTC) (envelope-from w8hdkim@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 57FA443D45 for ; Sun, 9 Jul 2006 13:23:57 +0000 (GMT) (envelope-from w8hdkim@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so1293333uge for ; Sun, 09 Jul 2006 06:23:56 -0700 (PDT) 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=XG/YJW7s5HOqDoYtMcMGEQyrmgnRKR4BaXGRBZK+VHBr9viBozS8YT2wKE/7ibmFm6nFqU8a6rb2Gcl4ccwMLy7dwULhUYHi1jYkWkXxW3nER2gCltHP9wgCZj0V18yd3JkWPcFRxvWzEjwJmImwlhdl3WWDRC9PR9D2CAAHb0Y= Received: by 10.78.165.16 with SMTP id n16mr1336354hue; Sun, 09 Jul 2006 06:23:56 -0700 (PDT) Received: by 10.78.49.6 with HTTP; Sun, 9 Jul 2006 06:23:56 -0700 (PDT) Message-ID: <89dbfdc30607090623l285b49b8g558a70b594a9cbeb@mail.gmail.com> Date: Sun, 9 Jul 2006 09:23:56 -0400 From: "Kim Culhan" To: "Dan Nelson" In-Reply-To: <20060709030324.GA87129@dan.emsphone.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <89dbfdc30607081352g2c9eca00n738ee4e77dd3335d@mail.gmail.com> <20060709030324.GA87129@dan.emsphone.com> Cc: freebsd-stable@freebsd.org Subject: Re: gmake: virtual memory exhausted X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 13:23:58 -0000 On 7/8/06, Dan Nelson wrote: > In the last episode (Jul 08), Kim Culhan said: > > Greetings- > > > > Compiling Asterisk on 6.1-STABLE: > > > > gmake -C db1-ast libdb1.a > > gmake[1]: Entering directory `/usr/local/src/asterisk/asterisk/db1-ast' > > gmake[1]: *** virtual memory exhausted. Stop. > > > > Any suggestion of a tuning parameter to work around this is > > greatly appreciated. > > Does the port compile? This is Asterisk HEAD I've tried setting several memory parameters to unlimited but this did not work. Also ran the configure script with the --with-low-memory flag but this does not help either. -kim -- w8hdkim@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 20:49:33 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2C2F516A4DA for ; Sun, 9 Jul 2006 20:49:33 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id C61BE43D45 for ; Sun, 9 Jul 2006 20:49:32 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 00704114EC for ; Sun, 9 Jul 2006 16:50:00 -0400 (EDT) Message-ID: <44B16BE9.60508@rogers.com> Date: Sun, 09 Jul 2006 16:49:45 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: Subject: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 20:49:33 -0000 I just setup a new system with MySQL 5.0.22, and to my surprise i get this error in MySQL's log. /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) The system has 1GB of ram, which is plenty for MySQLs configuration (its using the my-large.cnf, which is tuned for a system of 512MB) Why am i getting this error? I read somewhere that FreeBSD by default limits process size to 512MB, however the variables used to tune it do not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more memory? From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 20:56:45 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 910E716A4DF for ; Sun, 9 Jul 2006 20:56:45 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2FA9443D49 for ; Sun, 9 Jul 2006 20:56:44 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id 154864FF9B5; Sun, 9 Jul 2006 22:56:44 +0200 (CEST) Date: Sun, 09 Jul 2006 22:56:41 +0200 From: Mathieu Arnold To: Mike Jakubik , stable@freebsd.org Message-ID: In-Reply-To: <44B16BE9.60508@rogers.com> References: <44B16BE9.60508@rogers.com> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========64711100E0026705A59E==========" Cc: Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 20:56:45 -0000 --==========64711100E0026705A59E========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : | I just setup a new system with MySQL 5.0.22, and to my surprise i get | this error in MySQL's log. | | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) | | The system has 1GB of ram, which is plenty for MySQLs configuration (its | using the my-large.cnf, which is tuned for a system of 512MB) | | | Why am i getting this error? I read somewhere that FreeBSD by default | limits process size to 512MB, however the variables used to tune it do | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more | memory? If you're using a i386, the max process memory size limit is at 512M, you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. -- Mathieu Arnold --==========64711100E0026705A59E========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFEsW2KJqR8av5thQ8RAm91AJ9tfq4YM7JrsBKvBTFSqtPIDtPdjACgqd9k JrH50nDrWK3fipiE45wGL6M= =Ia3D -----END PGP SIGNATURE----- --==========64711100E0026705A59E==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:14:19 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CEF2916A4DA; Sun, 9 Jul 2006 21:14:19 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4DA3443D45; Sun, 9 Jul 2006 21:14:18 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [10.242.169.24] (c-67-171-135-169.hsd1.or.comcast.net [67.171.135.169]) by mail.twinthornes.com (Postfix) with ESMTP id CFE264F; Sun, 9 Jul 2006 14:14:17 -0700 (PDT) Message-ID: <44B171AA.9080400@bitfreak.org> Date: Sun, 09 Jul 2006 14:14:18 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mathieu Arnold References: <44B16BE9.60508@rogers.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:14:19 -0000 Mathieu Arnold wrote: > +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : > | I read somewhere that FreeBSD by default > | limits process size to 512MB, however the variables used to tune it do > | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more > | memory? > > If you're using a i386, the max process memory size limit is at 512M, > you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. That OID doesn't seem to exist: > uname -pr 6.0-RELEASE-p1 i386 > sysctl -N kern | grep max kern.maxvnodes kern.maxproc kern.maxfiles kern.argmax kern.maxfilesperproc kern.maxprocperuid kern.ipc.maxsockbuf kern.ipc.somaxconn kern.ipc.max_linkhdr kern.ipc.max_protohdr kern.ipc.max_hdr kern.ipc.max_datalen kern.ipc.maxpipekva kern.ipc.msgmax kern.ipc.shmmax kern.ipc.maxsockets kern.iov_max kern.kq_calloutmax kern.maxusers kern.threads.max_threads_per_proc kern.threads.max_groups_per_proc kern.threads.max_threads_hits kern.smp.maxcpus -- Darren Pilgrim From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:17:08 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5CEB116A4DA; Sun, 9 Jul 2006 21:17:08 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA99D43D6D; Sun, 9 Jul 2006 21:17:07 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id F03B74FF633; Sun, 9 Jul 2006 23:17:06 +0200 (CEST) Date: Sun, 09 Jul 2006 23:17:05 +0200 From: Mathieu Arnold To: Darren Pilgrim , Mathieu Arnold Message-ID: <6C05189234026592B01C2703@[192.168.1.5]> In-Reply-To: <44B171AA.9080400@bitfreak.org> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========3AEF3F46EB7D8CD9A4E3==========" Cc: Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:17:08 -0000 --==========3AEF3F46EB7D8CD9A4E3========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-Le 09/07/2006 14:14 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : | > | I read somewhere that FreeBSD by default |> | limits process size to 512MB, however the variables used to tune it do |> | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use |> | more memory? |> |> If you're using a i386, the max process memory size limit is at 512M, |> you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. | | That OID doesn't seem to exist: | | > uname -pr | 6.0-RELEASE-p1 i386 | > sysctl -N kern | grep max That's not a sysctl, it's a tunable thing, which don't appear in sysctl. -- Mathieu Arnold --==========3AEF3F46EB7D8CD9A4E3========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFEsXJRJqR8av5thQ8RAmmsAJ4iFMQ+UwQ2eL6WkpgYuxYjPHN8FwCgtIyP /lKF7BWbiBNjAUBghjrnR84= =OldM -----END PGP SIGNATURE----- --==========3AEF3F46EB7D8CD9A4E3==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:25:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2364116A4DA; Sun, 9 Jul 2006 21:25:14 +0000 (UTC) (envelope-from darren.pilgrim@bitfreak.org) Received: from mail.twinthornes.com (mail.twinthornes.com [65.75.198.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6843943D4C; Sun, 9 Jul 2006 21:25:13 +0000 (GMT) (envelope-from darren.pilgrim@bitfreak.org) Received: from [10.242.169.24] (c-67-171-135-169.hsd1.or.comcast.net [67.171.135.169]) by mail.twinthornes.com (Postfix) with ESMTP id 32A9A4F; Sun, 9 Jul 2006 14:25:12 -0700 (PDT) Message-ID: <44B17437.5010506@bitfreak.org> Date: Sun, 09 Jul 2006 14:25:11 -0700 From: Darren Pilgrim User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mathieu Arnold References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> In-Reply-To: <6C05189234026592B01C2703@[192.168.1.5]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:25:14 -0000 Mathieu Arnold wrote: > [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't > appear in sysctl. Gotta love namespace collisions. -- Darren Pilgrim From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:29:35 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DDF5516A4E0 for ; Sun, 9 Jul 2006 21:29:35 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41AF643D5C for ; Sun, 9 Jul 2006 21:29:35 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id 606504FD475; Sun, 9 Jul 2006 23:29:34 +0200 (CEST) Date: Sun, 09 Jul 2006 23:29:32 +0200 From: Mathieu Arnold To: Darren Pilgrim Message-ID: <7215DBE558702ADFC8718798@[192.168.1.5]> In-Reply-To: <44B17437.5010506@bitfreak.org> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========8805B722464D02370049==========" Cc: Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:29:35 -0000 --==========8805B722464D02370049========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : | Mathieu Arnold wrote: |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> appear in sysctl. | | Gotta love namespace collisions. Well, in fact, most of the tunables do have a read only sysctl so that people don't have to search the code for the value it has/takes :-) Not this one though :-) -- Mathieu Arnold --==========8805B722464D02370049========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFEsXU8JqR8av5thQ8RApbZAJ49OisqQvdQO9glHvgcSF/VqObHuwCgrPi0 rg/OZKOrpmAJQ9NCmZW7MME= =np+M -----END PGP SIGNATURE----- --==========8805B722464D02370049==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:39:17 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C051416A4EB; Sun, 9 Jul 2006 21:39:17 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1675843F67; Sun, 9 Jul 2006 21:36:06 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 9A6ED114F1; Sun, 9 Jul 2006 17:36:32 -0400 (EDT) Message-ID: <44B176D2.3080501@rogers.com> Date: Sun, 09 Jul 2006 17:36:18 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mathieu Arnold References: <44B16BE9.60508@rogers.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:39:17 -0000 Mathieu Arnold wrote: > +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : > | I just setup a new system with MySQL 5.0.22, and to my surprise i get > | this error in MySQL's log. > | > | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) > | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) > | > | The system has 1GB of ram, which is plenty for MySQLs configuration (its > | using the my-large.cnf, which is tuned for a system of 512MB) > | > | > | Why am i getting this error? I read somewhere that FreeBSD by default > | limits process size to 512MB, however the variables used to tune it do > | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use more > | memory? > > If you're using a i386, the max process memory size limit is at 512M, > you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. > > Why are the limits so low by default? In any case, this is what i found in LINT. options MAXDSIZ=(1024UL*1024*1024) options MAXSSIZ=(128UL*1024*1024) options DFLDSIZ=(1024UL*1024*1024) I have no idea what those values mean, what should i set them to to be safe? A limit 768MB should work for me. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:39:58 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2FAD16A5DD; Sun, 9 Jul 2006 21:39:58 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 76D9443F87; Sun, 9 Jul 2006 21:36:41 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 34EE611519; Sun, 9 Jul 2006 17:37:08 -0400 (EDT) Message-ID: <44B176F5.2050409@rogers.com> Date: Sun, 09 Jul 2006 17:36:53 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mathieu Arnold References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> In-Reply-To: <7215DBE558702ADFC8718798@[192.168.1.5]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, AWL 0.00, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: Darren Pilgrim , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:39:59 -0000 Mathieu Arnold wrote: > +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : > | Mathieu Arnold wrote: > |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't > |> appear in sysctl. > | > | Gotta love namespace collisions. > > Well, in fact, most of the tunables do have a read only sysctl so that > people don't have to search the code for the value it has/takes :-) > Not this one though :-) > Exactly, its nice being able to see the current values. How else can i see what the values are set to? From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:45:48 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D521616A4DA for ; Sun, 9 Jul 2006 21:45:48 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8250043D5A for ; Sun, 9 Jul 2006 21:45:47 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id A62F64FFAC0; Sun, 9 Jul 2006 23:45:46 +0200 (CEST) Date: Sun, 09 Jul 2006 23:45:44 +0200 From: Mathieu Arnold To: Mike Jakubik Message-ID: <2B636EF151DC536C47555034@[192.168.1.5]> In-Reply-To: <44B176F5.2050409@rogers.com> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========A373EEC2681DAE3ADA71==========" Cc: Darren Pilgrim , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:45:48 -0000 --==========A373EEC2681DAE3ADA71========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : |> | Mathieu Arnold wrote: |> |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't |> |> appear in sysctl. |> | |> | Gotta love namespace collisions. |> |> Well, in fact, most of the tunables do have a read only sysctl so that |> people don't have to search the code for the value it has/takes :-) |> Not this one though :-) |> | | Exactly, its nice being able to see the current values. How else can i | see what the values are set to? As I previously said, it's 512M on i386, and 1G on 64 bit platforms. -- Mathieu Arnold --==========A373EEC2681DAE3ADA71========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFEsXkIJqR8av5thQ8RAoAgAJ9+Aac5pl5oEU/ungemaSEjbRCKkgCfTybX kX4RIzz2JuubVO8AXhjzORM= =BZb8 -----END PGP SIGNATURE----- --==========A373EEC2681DAE3ADA71==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:52:05 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 376AB16A4DD for ; Sun, 9 Jul 2006 21:52:05 +0000 (UTC) (envelope-from mat@FreeBSD.org) Received: from plouf.absolight.net (plouf.absolight.net [193.30.224.136]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A29F43D60 for ; Sun, 9 Jul 2006 21:52:03 +0000 (GMT) (envelope-from mat@FreeBSD.org) Received: from pouet.in.mat.cc (pouet.in.mat.cc [193.30.224.122]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by plouf.absolight.net (Postfix) with ESMTP id 483924B3331; Sun, 9 Jul 2006 23:52:02 +0200 (CEST) Date: Sun, 09 Jul 2006 23:52:00 +0200 From: Mathieu Arnold To: Mike Jakubik Message-ID: <146D5072D1FBB23E25430AD6@[192.168.1.5]> In-Reply-To: <44B176D2.3080501@rogers.com> References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> X-Mailer: Mulberry/4.0.4 (Win32) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="==========F735760550EA3754F2F7==========" Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:52:05 -0000 --==========F735760550EA3754F2F7========== Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline +-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : | Mathieu Arnold wrote: |> +-Le 09/07/2006 16:49 -0400, Mike Jakubik a dit : |> | I just setup a new system with MySQL 5.0.22, and to my surprise i get |> | this error in MySQL's log. |> | |> | /usr/local/libexec/mysqld: Out of memory (Needed 237527040 bytes) |> | /usr/local/libexec/mysqld: Out of memory (Needed 178145280 bytes) |> | |> | The system has 1GB of ram, which is plenty for MySQLs configuration |> | (its using the my-large.cnf, which is tuned for a system of 512MB) |> | |> | |> | Why am i getting this error? I read somewhere that FreeBSD by default |> | limits process size to 512MB, however the variables used to tune it do |> | not seems to exist in FreeBSD-6.1 any more. How can i let MySQL use |> | more memory? |> |> If you're using a i386, the max process memory size limit is at 512M, |> you'll have to tune kern.maxdsiz in /boot/loader.conf to say 1G. |> |> | | Why are the limits so low by default? In any case, this is what i found | in LINT. | | options MAXDSIZ=(1024UL*1024*1024) | options MAXSSIZ=(128UL*1024*1024) | options DFLDSIZ=(1024UL*1024*1024) That's the LINT value, the *real* default values are in /include/vmparam.h that is, 1G on alpha, ia64 and sparc64, 512K on i386, powerpc and arm and 32G (?) on amd64 | I have no idea what those values mean, what should i set them to to be | safe? A limit 768MB should work for me. You can put 1G and you'd be safe for some time. It has no real, hum, relation with the amount of ram you get, because some parts of your process will get swapped out : PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMAND 9860 mysql 18 96 0 614M 257M ucond 1 1:22 1.22% mysqld so, as I understand it, mysqld has 614M allocated, from which 257 are actually in RAM (the rest being swapped out.) -- Mathieu Arnold --==========F735760550EA3754F2F7========== Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (MingW32) iD8DBQFEsXqAJqR8av5thQ8RAg/8AKCAcbrO7LekY1zUVZzE9RKaygkVeQCcDg1E D5jKQtT312DhZois6TNuuso= =yoSS -----END PGP SIGNATURE----- --==========F735760550EA3754F2F7==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:53:27 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F19C316A4DD; Sun, 9 Jul 2006 21:53:27 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 517AE43D53; Sun, 9 Jul 2006 21:53:27 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 6BD7A114F1; Sun, 9 Jul 2006 17:53:52 -0400 (EDT) Message-ID: <44B17AE2.5020908@rogers.com> Date: Sun, 09 Jul 2006 17:53:38 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mathieu Arnold References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> <2B636EF151DC536C47555034@[192.168.1.5]> In-Reply-To: <2B636EF151DC536C47555034@[192.168.1.5]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: Darren Pilgrim , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:53:28 -0000 Mathieu Arnold wrote: > | Exactly, its nice being able to see the current values. How else can i > | see what the values are set to? > > As I previously said, it's 512M on i386, and 1G on 64 bit platforms. > > Right, this explains why my amd64 system works just fine. Shouldn't this be a dynamic value based on total amount of ram? Say 70% of RAM, I mean servers have plenty of RAM nowadays, this seems like an old hard limit, which many new users will trip over.... I set my value to 805306368, and mysql seems to be happy now. From owner-freebsd-stable@FreeBSD.ORG Sun Jul 9 21:54:38 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5A5716A4DE; Sun, 9 Jul 2006 21:54:38 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from sccmmhc92.asp.att.net (sccmmhc92.asp.att.net [204.127.203.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A06E43D53; Sun, 9 Jul 2006 21:54:38 +0000 (GMT) (envelope-from stephen@math.missouri.edu) Received: from [10.0.0.4] (12-216-254-44.client.mchsi.com[12.216.254.44]) by sccmmhc92.asp.att.net (sccmmhc92) with ESMTP id <20060709215432m92002rm95e>; Sun, 9 Jul 2006 21:54:36 +0000 Message-ID: <44B17B18.8070906@math.missouri.edu> Date: Sun, 09 Jul 2006 16:54:32 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060707 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> In-Reply-To: <44B176F5.2050409@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: Mathieu Arnold , Darren Pilgrim , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Jul 2006 21:54:38 -0000 Mike Jakubik wrote: > Mathieu Arnold wrote: > >> +-Le 09/07/2006 14:25 -0700, Darren Pilgrim a dit : >> | Mathieu Arnold wrote: >> |> [kern.maxdsiz is not] a sysctl, it's a tunable thing, which don't >> |> appear in sysctl. >> | | Gotta love namespace collisions. >> >> Well, in fact, most of the tunables do have a read only sysctl so that >> people don't have to search the code for the value it has/takes :-) >> Not this one though :-) >> > > > Exactly, its nice being able to see the current values. How else can i > see what the values are set to? The commands limit and limits (one of them is a csh only command) will tell you (although they might be set lower for a particular user via /etc/login.conf, or for a particular process, but that's unlikely). Stephen From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 02:02:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F18C116A4DA for ; Mon, 10 Jul 2006 02:02:16 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 45AC543D45 for ; Mon, 10 Jul 2006 02:02:15 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id v1so44595nzb for ; Sun, 09 Jul 2006 19:02:14 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=XL2fy0arzOFQmk+tuUL21b9WekLdaewRN4Jv0Z6EOYqWFAxP7dTz4gdjNvEx64ppwD8ZuVfiJyu/UTS8EDVFri0eRv6EVatrOO9oiRSqkTAyul3unP9bZKwdsENokK9uIoIQ+AHA91EI/CrhFLuBA30eagJxnUiUBW6VIeGDMrI= Received: by 10.36.138.15 with SMTP id l15mr4128704nzd; Sun, 09 Jul 2006 19:02:14 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id c12sm1059458nzc.2006.07.09.19.02.10; Sun, 09 Jul 2006 19:02:14 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6A227nu001728 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 11:02:08 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6A21xLo001727; Mon, 10 Jul 2006 11:01:59 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Mon, 10 Jul 2006 11:01:59 +0900 From: Pyun YongHyeon To: Ruslan Ermilov Message-ID: <20060710020158.GA1128@cdnetworks.co.kr> References: <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060708172001.GB77281@ip.net.ua> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 02:02:17 -0000 On Sat, Jul 08, 2006 at 08:20:01PM +0300, Ruslan Ermilov wrote: > On Sat, Jul 08, 2006 at 12:32:55PM +0900, Pyun YongHyeon wrote: > > On Fri, Jul 07, 2006 at 10:38:01PM +0100, Robert Watson wrote: > > > > > > On Fri, 7 Jul 2006, User Freebsd wrote: > > > > > > >>I think that I have patched, built and loaded the em(4) kernel module > > > >>correctly. After applying the patch there were no rejects, before > > > >>building the module I intentionally appended " (patched)" to its version > > > >>string in if_em.c, and could see that in dmesg every time I loaded the > > > >>module: em1: > > >>(patched)> > > > > > > > >Is it possible that we're going at this issue backwards? It isn't the > > > >lack of ARP packet going out that is causing the problems with moving IPs, > > > >but that delay that we're seeing when aliasing a new IP on the stack? The > > > >ARP packet *is* being attempted, but is timing out before the re-init is > > > >completing? > > > > > > Yes -- basically, there are two problems: > > > > > > (1) A little problem, in which an arp announcement is sent before the link > > > has > > > settled after reset. > > > > > > (2) A big problem, in which the interface is gratuitously recent requiring > > > long settling times. > > > > > > I'd really like to see a fix to the second of these problems (not resetting > > > when an IP is added or removed, resulting in link renegotiation); the first > > > one I'm less concerned about, although it would make some amount of sense > > > to do an arp announcement when the link goes up. > > > > > > > Ah, I see. Thanks for the insight. > > How about the attached patch? > > > I've been working on this problem for Mike Tancsa about a year ago, > and my fix was naive. I ended up not committing it because I found > that it broke something else, but I don't remember what exactly now. > Ahh, I seem to remember now -- setting a different MAC address was > not programmed into a hardware with my patch applied. > > I guess, in some cases(FIFO overrun/underrun, link duplex changes, hardware malfunction or watchdog error etc) the hardware needs a global reset which in turn needs em_hardware_init(). If we can invoke em_hardware_init() under absolutely required condition it would work as expected. This will also eliminates long time delay needed to add alias addresses. See my other post in the list.( It has a layering violation, handled protocol specific operation in a driver, but I failed to find a better way to fix the issue without rewriting bunch of hardware specific parts of 8254x.) -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 04:00:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2395916A4F1; Mon, 10 Jul 2006 04:00:36 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 879B643D45; Mon, 10 Jul 2006 04:00:35 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k6A40UKA027185; Mon, 10 Jul 2006 00:00:30 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k6A40V15045824 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 00:00:31 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060709234941.12531860@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 10 Jul 2006 00:00:02 -0400 To: Ruslan Ermilov , Pyun YongHyeon From: Mike Tancsa In-Reply-To: <20060708172001.GB77281@ip.net.ua> References: <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 04:00:36 -0000 At 01:20 PM 08/07/2006, Ruslan Ermilov wrote: > > > > Ah, I see. Thanks for the insight. > > How about the attached patch? > > >I've been working on this problem for Mike Tancsa about a year ago, >and my fix was naive. I ended up not committing it because I found >that it broke something else, but I don't remember what exactly now. >Ahh, I seem to remember now -- setting a different MAC address was >not programmed into a hardware with my patch applied. For my uses, this was a non issue. Having STP block for 20 seconds because I add or remove an alias made it kind of a non issue. ---Mike From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 04:06:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EB74B16A4DF; Mon, 10 Jul 2006 04:06:18 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63C0843D46; Mon, 10 Jul 2006 04:06:18 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id ED07E290C2B; Mon, 10 Jul 2006 01:06:16 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 44556-05; Mon, 10 Jul 2006 04:06:17 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 59C83290C25; Mon, 10 Jul 2006 01:06:16 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 1ABCB4A449; Mon, 10 Jul 2006 01:06:16 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 1976249BE7; Mon, 10 Jul 2006 01:06:16 -0300 (ADT) Date: Mon, 10 Jul 2006 01:06:16 -0300 (ADT) From: User Freebsd To: Mike Tancsa In-Reply-To: <6.2.3.4.0.20060709234941.12531860@64.7.153.2> Message-ID: <20060710010540.G1799@ganymede.hub.org> References: <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 04:06:19 -0000 On Mon, 10 Jul 2006, Mike Tancsa wrote: > At 01:20 PM 08/07/2006, Ruslan Ermilov wrote: >> > >> > Ah, I see. Thanks for the insight. >> > How about the attached patch? >> > >> I've been working on this problem for Mike Tancsa about a year ago, >> and my fix was naive. I ended up not committing it because I found >> that it broke something else, but I don't remember what exactly now. >> Ahh, I seem to remember now -- setting a different MAC address was >> not programmed into a hardware with my patch applied. > > > For my uses, this was a non issue. Having STP block for 20 seconds because I > add or remove an alias made it kind of a non issue. Not sure what STP is, but I've not noticed any blocking on removing an alias, only on adding one ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 04:12:08 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 109A116A4DA; Mon, 10 Jul 2006 04:12:08 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72B9143D46; Mon, 10 Jul 2006 04:12:07 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k6A4C3mA027465; Mon, 10 Jul 2006 00:12:03 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k6A4C5Jb045896 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 00:12:05 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 10 Jul 2006 00:11:36 -0400 To: User Freebsd From: Mike Tancsa In-Reply-To: <20060710010540.G1799@ganymede.hub.org> References: <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 04:12:08 -0000 At 12:06 AM 10/07/2006, User Freebsd wrote: >Not sure what STP is Spanning Tree Protocol. Having the link go up and down would cause the switch port to block traffic for a period of time. ---Mike From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 04:41:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE7F016A4DE for ; Mon, 10 Jul 2006 04:41:09 +0000 (UTC) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35CC943D46 for ; Mon, 10 Jul 2006 04:41:08 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 99569 invoked by uid 0); 10 Jul 2006 04:41:08 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 Jul 2006 04:41:08 -0000 Date: Mon, 10 Jul 2006 00:41:07 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: freebsd-stable@freebsd.org In-Reply-To: <20060708085132.GD98476@over-yonder.net> Message-ID: References: <20060708085132.GD98476@over-yonder.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 04:41:10 -0000 On Sat, 8 Jul 2006, Matthew D. Fuller wrote: > On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of > Charles Sprickman, and lo! it spake thus: >> >> Trying again, it reported the same inconsistencies then sat there >> for more than an hour taking up all the available CPU on the box >> until I killed it. The mtime on quota.user had not changed during >> the run. > > FWIW, I saw this on a box I setup running a late November -CURRENT > last year; I could never get the quotas setup and running right > because the check always just looped itself up. The partition they're > on has about 3 gig used out of ~45, with maybe a dozen users. I never > spent much time on it, since it's just a personal box, and the quotas > are mostly just to provide a handy measure of who's using what (no > limits set). I just gave it up and decided to worry about it later. What should I do here? It's consistently failing. What information should I gather to forumulate a PR that won't burden the assignee with lots of troubleshooting mess? The machine is not in production, but there is user data on it. I could allow a trusted developer access to it, or even create another jail to illustrate the problem. Thanks, Charles > > -- > Matthew Fuller (MF4839) | fullermd@over-yonder.net > Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ > On the Internet, nobody can hear you scream. > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 04:53:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5BA5A16A4DE for ; Mon, 10 Jul 2006 04:53:39 +0000 (UTC) (envelope-from SRS0=qRry+6=A3=vvelox.net=vvelox@yourhostingaccount.com) Received: from mailout15.yourhostingaccount.com (outmail121.yourhostingaccount.com [65.254.253.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id D814743D45 for ; Mon, 10 Jul 2006 04:53:38 +0000 (GMT) (envelope-from SRS0=qRry+6=A3=vvelox.net=vvelox@yourhostingaccount.com) Received: from scan02.yourhostingaccount.com ([10.1.1.232] helo=scan02.yourhostingaccount.com) by mailout15.yourhostingaccount.com with esmtp (Exim) id 1Fznm5-000244-Jn for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 00:53:37 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] ident=exim) by scan02.yourhostingaccount.com with spamscanlookuphost (Exim) id 1Fznm5-0006Cy-GV for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 00:53:37 -0400 Received: from authsmtp08.yourhostingaccount.com ([10.1.18.8] helo=authsmtp08.yourhostingaccount.com) by scan02.yourhostingaccount.com with esmtp (Exim) id 1Fznm3-0006Cq-33 for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 00:53:35 -0400 Received: from 24-119-225-24.cpe.cableone.net ([24.119.225.24] helo=vixen42.vulpes) by authsmtp08.yourhostingaccount.com with esmtpa (Exim) id 1Fznm2-000396-KC for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 00:53:34 -0400 Date: Sun, 9 Jul 2006 23:54:30 +0000 From: "Z.C.B." To: freebsd-stable@freebsd.org Message-ID: <20060709235430.49d30de5@vixen42.vulpes> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.20; i386-portbld-freebsd6.1) Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_JK.LqK/RUiAO9Y.sYyTRTNA"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-EN-UserInfo: f1c157ec5ebebd12a8182d58c6ceecd9:1570f0de6936c69fef9e164fffc541bc X-EN-AuthUser: vvelox3 Sender: "Z.C.B." Subject: interrupt oddity X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 04:53:39 -0000 --Sig_JK.LqK/RUiAO9Y.sYyTRTNA Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I just installed 6.1 on a dual core amd machine. That went fine and it was using the generic SMP kernel. I created a custom kernel using my previous config but forgot to add the SMP line. It worked well except for one odd thing. The nvidia card would start using up a nice chunk of processor time with interrupts and intterupts seem to use a lot more time in general. I added the line, recompiled, rebooted, and every thing worked well. Any one else ever seen any thing like this before or have any idea what happened or why? --Sig_JK.LqK/RUiAO9Y.sYyTRTNA Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsZc4C1tfcMGJid4RAiq7AJ9uDYsL0Y7NhpjkwBYUcO0noBWOVwCgkeks w+uTIZZP0W/JO9o21LyjELY= =PaLS -----END PGP SIGNATURE----- --Sig_JK.LqK/RUiAO9Y.sYyTRTNA-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 05:25:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEE3A16A5D3 for ; Mon, 10 Jul 2006 05:25:22 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A126D43D4C for ; Mon, 10 Jul 2006 05:25:21 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k6A5PEgj010662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 08:25:14 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k6A5PEUj087325; Mon, 10 Jul 2006 08:25:14 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k6A5PDEk087324; Mon, 10 Jul 2006 08:25:13 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2006 08:25:13 +0300 From: Kostik Belousov To: Charles Sprickman Message-ID: <20060710052513.GF37822@deviant.kiev.zoral.com.ua> References: <20060708085132.GD98476@over-yonder.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EcSFpNr6Vcxykj4g" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 05:25:22 -0000 --EcSFpNr6Vcxykj4g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: > On Sat, 8 Jul 2006, Matthew D. Fuller wrote: >=20 > >On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of > >Charles Sprickman, and lo! it spake thus: > >> > >>Trying again, it reported the same inconsistencies then sat there > >>for more than an hour taking up all the available CPU on the box > >>until I killed it. The mtime on quota.user had not changed during > >>the run. > > > >FWIW, I saw this on a box I setup running a late November -CURRENT > >last year; I could never get the quotas setup and running right > >because the check always just looped itself up. The partition they're > >on has about 3 gig used out of ~45, with maybe a dozen users. I never > >spent much time on it, since it's just a personal box, and the quotas > >are mostly just to provide a handy measure of who's using what (no > >limits set). I just gave it up and decided to worry about it later. >=20 > What should I do here? It's consistently failing. What information=20 > should I gather to forumulate a PR that won't burden the assignee with=20 > lots of troubleshooting mess? The machine is not in production, but ther= e=20 > is user data on it. I could allow a trusted developer access to it, or= =20 > even create another jail to illustrate the problem. It is not clear from your report whether you run fsck on the problem partition. I think (and my view is backed by "unexpected inconsistencies" message) that this is the must. --EcSFpNr6Vcxykj4g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEseS3C3+MBN1Mb4gRAs2sAJ4yJ77URWpC3V1CzMhV0QWN50hw2ACffWR6 3zECtBVI3lc7wXQWM0+5/m0= =Q9MP -----END PGP SIGNATURE----- --EcSFpNr6Vcxykj4g-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 05:39:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F3216A4DA for ; Mon, 10 Jul 2006 05:39:04 +0000 (UTC) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3C75443D53 for ; Mon, 10 Jul 2006 05:39:04 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 58622 invoked by uid 0); 10 Jul 2006 05:39:03 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 10 Jul 2006 05:39:03 -0000 Date: Mon, 10 Jul 2006 01:39:01 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: Kostik Belousov In-Reply-To: <20060710052513.GF37822@deviant.kiev.zoral.com.ua> Message-ID: References: <20060708085132.GD98476@over-yonder.net> <20060710052513.GF37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 05:39:04 -0000 On Mon, 10 Jul 2006, Kostik Belousov wrote: > On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: >> On Sat, 8 Jul 2006, Matthew D. Fuller wrote: >> >>> On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of >>> Charles Sprickman, and lo! it spake thus: >>>> >>>> Trying again, it reported the same inconsistencies then sat there >>>> for more than an hour taking up all the available CPU on the box >>>> until I killed it. The mtime on quota.user had not changed during >>>> the run. >>> >>> FWIW, I saw this on a box I setup running a late November -CURRENT >>> last year; I could never get the quotas setup and running right >>> because the check always just looped itself up. The partition they're >>> on has about 3 gig used out of ~45, with maybe a dozen users. I never >>> spent much time on it, since it's just a personal box, and the quotas >>> are mostly just to provide a handy measure of who's using what (no >>> limits set). I just gave it up and decided to worry about it later. >> >> What should I do here? It's consistently failing. What information >> should I gather to forumulate a PR that won't burden the assignee with >> lots of troubleshooting mess? The machine is not in production, but there >> is user data on it. I could allow a trusted developer access to it, or >> even create another jail to illustrate the problem. > > It is not clear from your report whether you run fsck on the problem > partition. I think (and my view is backed by "unexpected inconsistencies" > message) that this is the must. Sorry about that, I did not mention it, but thinking the same thing you did, I unmounted the partition and fsck'd twice for good measure. Both runs came back clean. I think its quotacheck complaining about the quota.user file... Thanks, Charles From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 06:27:48 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 244D016A4DD for ; Mon, 10 Jul 2006 06:27:48 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5F3743D45 for ; Mon, 10 Jul 2006 06:27:47 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1FzpEj-00065z-Ok; Mon, 10 Jul 2006 10:27:17 +0400 Message-ID: <44B1F345.8030303@FreeBSD.org> Date: Mon, 10 Jul 2006 10:27:17 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Miroslav Lachman <000.fbsd@quip.cz> References: <44AFA561.4020104@quip.cz> <20060708184732.GJ18199@wananchi.com> <44B00793.2080302@quip.cz> In-Reply-To: <44B00793.2080302@quip.cz> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Odhiambo Washington , freebsd-stable@freebsd.org Subject: Re: portupgrade-2.1.3.2,2 doesn't work with db42 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 06:27:48 -0000 Miroslav Lachman wrote: > Odhiambo Washington wrote: >> rm /usr/local/lib/ruby/site_ruby/1.8/i386-freebsd6/bdb.so >> >> then tell me what happens if you run portupgrade again! >> >> I've gone through this today, so it's still fresh in my mind! > > After removing bdb.so portupgrade is working again. Thank you! > > Just for my knowledge - from where goes this error? What should be > fixed? Ruby-bdb or portupgrade? ports/99697 Please note the topic is ports@ relate. And was discussed there. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 07:09:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D495616A4DA; Mon, 10 Jul 2006 07:09:55 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 203CD43D4C; Mon, 10 Jul 2006 07:09:54 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k6A79rHR010559; Mon, 10 Jul 2006 09:09:53 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k6A79p6G023950; Mon, 10 Jul 2006 09:09:51 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k6A79pjV023949; Mon, 10 Jul 2006 09:09:51 +0200 (CEST) (envelope-from ry93) Date: Mon, 10 Jul 2006 09:09:51 +0200 From: "Patrick M. Hausen" To: Mike Tancsa Message-ID: <20060710070951.GA23181@hugo10.ka.punkt.de> References: <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> User-Agent: Mutt/1.5.10i Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 07:09:55 -0000 Mornin'! On Mon, Jul 10, 2006 at 12:11:36AM -0400, Mike Tancsa wrote: > >Not sure what STP is > > Spanning Tree Protocol. Having the link go up and down would cause > the switch port to block traffic for a period of time. Of course, any reasonable administrator would configure interface FastEthernet0/1 spanning-tree portfast for all ports connected to hosts. (shown syntax is Cisco's). Regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 07:29:13 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6DE816A4DA; Mon, 10 Jul 2006 07:29:13 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B051A43D60; Mon, 10 Jul 2006 07:29:09 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k6A7Sieu032461; Mon, 10 Jul 2006 03:28:44 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k6A7SkkP047297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 03:28:46 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060710032828.1258f788@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 10 Jul 2006 03:29:15 -0400 To: "Patrick M. Hausen" From: Mike Tancsa In-Reply-To: <20060710070951.GA23181@hugo10.ka.punkt.de> References: <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> <20060710070951.GA23181@hugo10.ka.punkt.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Status: Clean Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 07:29:13 -0000 At 03:09 AM 10/07/2006, Patrick M. Hausen wrote: >Of course, any reasonable administrator would configure > > interface FastEthernet0/1 > spanning-tree portfast > >for all ports connected to hosts. (shown syntax is Cisco's). Yes, its great if you have access to the cisco... Not always possible in a colo. ---Mike From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 07:35:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15ABC16A4DD for ; Mon, 10 Jul 2006 07:35:35 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id A6E7543D7D for ; Mon, 10 Jul 2006 07:34:52 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k6A7YhAn013746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 10:34:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k6A7YhVE009250; Mon, 10 Jul 2006 10:34:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k6A7YgJO009228; Mon, 10 Jul 2006 10:34:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2006 10:34:42 +0300 From: Kostik Belousov To: Charles Sprickman Message-ID: <20060710073442.GG37822@deviant.kiev.zoral.com.ua> References: <20060708085132.GD98476@over-yonder.net> <20060710052513.GF37822@deviant.kiev.zoral.com.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="djTb5EnuS5qMpC9h" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 07:35:35 -0000 --djTb5EnuS5qMpC9h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2006 at 01:39:01AM -0400, Charles Sprickman wrote: > On Mon, 10 Jul 2006, Kostik Belousov wrote: >=20 > >On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: > >>On Sat, 8 Jul 2006, Matthew D. Fuller wrote: > >> > >>>On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of > >>>Charles Sprickman, and lo! it spake thus: > >>>> > >>>>Trying again, it reported the same inconsistencies then sat there > >>>>for more than an hour taking up all the available CPU on the box > >>>>until I killed it. The mtime on quota.user had not changed during > >>>>the run. > >>> > >>>FWIW, I saw this on a box I setup running a late November -CURRENT > >>>last year; I could never get the quotas setup and running right > >>>because the check always just looped itself up. The partition they're > >>>on has about 3 gig used out of ~45, with maybe a dozen users. I never > >>>spent much time on it, since it's just a personal box, and the quotas > >>>are mostly just to provide a handy measure of who's using what (no > >>>limits set). I just gave it up and decided to worry about it later. > >> > >>What should I do here? It's consistently failing. What information > >>should I gather to forumulate a PR that won't burden the assignee with > >>lots of troubleshooting mess? The machine is not in production, but th= ere > >>is user data on it. I could allow a trusted developer access to it, or > >>even create another jail to illustrate the problem. > > > >It is not clear from your report whether you run fsck on the problem > >partition. I think (and my view is backed by "unexpected inconsistencies" > >message) that this is the must. >=20 > Sorry about that, I did not mention it, but thinking the same thing you= =20 > did, I unmounted the partition and fsck'd twice for good measure. Both= =20 > runs came back clean. I think its quotacheck complaining about the=20 > quota.user file... Ok, please, show me uname -a, dmesg, /etc/fstab, mount -v. --djTb5EnuS5qMpC9h Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsgMRC3+MBN1Mb4gRAljPAKDo0HBrLl4PocFGkHKs7/5s6V6j1wCgui2t XuBXClUZ6DwWehntu9ycN+A= =ru/x -----END PGP SIGNATURE----- --djTb5EnuS5qMpC9h-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 07:42:25 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4444716A4F3; Mon, 10 Jul 2006 07:42:25 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail27.syd.optusnet.com.au (mail27.syd.optusnet.com.au [211.29.133.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 88BB143D83; Mon, 10 Jul 2006 07:41:19 +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 mail27.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6A7fHv7004906 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Mon, 10 Jul 2006 17:41:17 +1000 Received: from turion.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by turion.vk2pj.dyndns.org (8.13.6/8.13.6) with ESMTP id k6A7fHeF000820; Mon, 10 Jul 2006 17:41:17 +1000 (EST) (envelope-from peter@turion.vk2pj.dyndns.org) Received: (from peter@localhost) by turion.vk2pj.dyndns.org (8.13.6/8.13.6/Submit) id k6A7fGos000819; Mon, 10 Jul 2006 17:41:16 +1000 (EST) (envelope-from peter) Date: Mon, 10 Jul 2006 17:41:16 +1000 From: Peter Jeremy To: Mathieu Arnold Message-ID: <20060710074116.GA723@turion.vk2pj.dyndns.org> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> <2B636EF151DC536C47555034@[192.168.1.5]> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="6TrnltStXW4iwmi0" Content-Disposition: inline In-Reply-To: <2B636EF151DC536C47555034@[192.168.1.5]> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.11 Cc: Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 07:42:25 -0000 --6TrnltStXW4iwmi0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, 2006-Jul-09 23:45:44 +0200, Mathieu Arnold wrote: >+-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : >| Exactly, its nice being able to see the current values. How else can i >| see what the values are set to? > >As I previously said, it's 512M on i386, and 1G on 64 bit platforms. That doesn't answer Mike's question. The _default_ i386 size is 512M, the _current_ values can be found using ulimit (getrlimit(2)). Note that on non-PAE i386, the maximum process size is limited by the kernel size - there is a total of 4GB address space available and by default, the kernel has 2GB allocated to it. This isn't quite enough if you have 4GB RAM. --=20 Peter Jeremy --6TrnltStXW4iwmi0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsgSc/opHv/APuIcRAt4UAJ9MRExSvJ2TpNiC/dUozUK9ReOTuACgiGur fABvWv9FFDh4gSgI8lgY5kY= =i4kY -----END PGP SIGNATURE----- --6TrnltStXW4iwmi0-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 07:51:01 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0451216A4DA; Mon, 10 Jul 2006 07:51:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id E19F843D45; Mon, 10 Jul 2006 07:50:59 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k6A7osCM014243 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 10:50:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k6A7osLj009729; Mon, 10 Jul 2006 10:50:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k6A7orNT009728; Mon, 10 Jul 2006 10:50:53 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 10 Jul 2006 10:50:53 +0300 From: Kostik Belousov To: Peter Jeremy Message-ID: <20060710075053.GH37822@deviant.kiev.zoral.com.ua> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> <2B636EF151DC536C47555034@[192.168.1.5]> <20060710074116.GA723@turion.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ULkDCyeHsmlwbqED" Content-Disposition: inline In-Reply-To: <20060710074116.GA723@turion.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: Mathieu Arnold , Mike Jakubik , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 07:51:01 -0000 --ULkDCyeHsmlwbqED Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2006 at 05:41:16PM +1000, Peter Jeremy wrote: > On Sun, 2006-Jul-09 23:45:44 +0200, Mathieu Arnold wrote: > >+-Le 09/07/2006 17:36 -0400, Mike Jakubik a dit : > >| Exactly, its nice being able to see the current values. How else can i > >| see what the values are set to? > > > >As I previously said, it's 512M on i386, and 1G on 64 bit platforms. >=20 > That doesn't answer Mike's question. The _default_ i386 size is > 512M, the _current_ values can be found using ulimit (getrlimit(2)). >=20 > Note that on non-PAE i386, the maximum process size is limited by the > kernel size - there is a total of 4GB address space available and by > default, the kernel has 2GB allocated to it. This isn't quite enough ^^^^^^^^^^^^^ 1Gb+4Mb. > if you have 4GB RAM. >=20 > --=20 > Peter Jeremy --ULkDCyeHsmlwbqED Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsgbdC3+MBN1Mb4gRAuCCAKDCu8e2bqnG9tsl6y8zWgWGK7m2rACfUEC/ 4TEqivFsonAiPov8gkVhMt0= =CDo1 -----END PGP SIGNATURE----- --ULkDCyeHsmlwbqED-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 09:08:59 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A87F16A4DF for ; Mon, 10 Jul 2006 09:08:59 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 84C7D43D49 for ; Mon, 10 Jul 2006 09:08:58 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout1-sn1.fre.skanova.net (7.2.075) id 44A1364D002AAD11 for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 11:08:57 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id 3E2D161D64 for ; Mon, 10 Jul 2006 11:08:55 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TI5etfLGDnwQ for ; Mon, 10 Jul 2006 11:08:53 +0200 (CEST) Received: from [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01] (unknown [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01]) by elfi.stromnet.org (Postfix) with ESMTP id B4AA461D62 for ; Mon, 10 Jul 2006 11:08:53 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Mon, 10 Jul 2006 11:09:07 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.750) Subject: Re: GEOM problems again... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 09:08:59 -0000 On 21 maj 2006, at 11.16, Johan Str=F6m wrote: > Hi > > I've had problems before with GEOM mirror and my SATA drives, and =20 > i've posted about it here before too. The solution seemd to be a =20 > change of motherboard, this reduced the crash very much (and also =20 > the speeds archieved was greatly improved, from 10-15MB/s to =20 > 40-50MB/s..). > However after the change i had one or two crashes, but now it has =20 > been running for well over 50-60 days or so without any problems. > Then, 11 days ago I upgraded to 6.1... And now I got these =20 > "crashe"s again (the mirror is crashed that is, the system still =20 > runs fine): > > May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached > May 21 02:04:58 elfi kernel: subdisk6: detached > May 21 02:04:58 elfi kernel: ad6: detached > May 21 02:04:58 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad6s1 disconnected. > May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 > (offset=3D11006308352, length=3D2048)]error =3D 6 > May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 > (offset=3D164847927296, length=3D131072)]error =3D 6 > May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 > (offset=3D256680296448, length=3D32768)]error =3D 6 > > > Some info about the controller and disks: > > May 9 22:46:52 elfi kernel: ata1: on atapci0 > May 9 22:46:52 elfi kernel: atapci1: controller> port =20 > 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0x7f00-0x7f0f,=20= > 0x7c0 > 0-0x7c7f irq 22 at device 11.0 on pci0 > > May 9 22:46:52 elfi kernel: ad4: 286188MB BANC1G10> at ata2-master SATA150 > May 9 22:46:52 elfi kernel: ad6: 286188MB BANC1G10> at ata3-master SATA150 > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1 created =20 > (id=3D4118114647). > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad4s1 detected. > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad6s1 detected. > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad6s1 activated. > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad4s1 activated. > May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > mirror/gm0s1 launched. > May 9 22:46:52 elfi kernel: Trying to mount root from ufs:/dev/=20 > mirror/gm0s1a > > Anyone got any new clues? Afaik the disks should be working fine =20 > (they are 6 months old and this same problem has occured multiple =20 > times...) > > Hope to solve this ;) > > Thanks > Johan > Here we go again Jul 7 16:20:09 elfi kernel: ad4: FAILURE - device detached Jul 7 16:20:09 elfi kernel: subdisk4: detached Jul 7 16:20:09 elfi kernel: ad4: detached Jul 7 16:20:09 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 ad4s1 disconnected. Jul 7 16:20:09 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 (offset=3D88896847872, length=3D32768)]error =3D 6 However no read read timeouts etc as before, just this. 18 days =20 uptime this time (i've rebooted for other reasons since last mail). =20 It always seems to be ad4 that is disconnecting.. I'm going to do =20 some disk tests on it but i doubt it will give anything since i've =20 had similiar problems from day one (did tests at that time w/o =20 problems) with this gmirror setup (new disks). Johan From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 09:27:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 316A816A4E1 for ; Mon, 10 Jul 2006 09:27:09 +0000 (UTC) (envelope-from mt@smtp.top.net.ua) Received: from smtp.top.net.ua (smtp.top.net.ua [88.81.254.198]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B16C43D64 for ; Mon, 10 Jul 2006 09:27:06 +0000 (GMT) (envelope-from mt@smtp.top.net.ua) Received: from smtp.top.net.ua (localhost [127.0.0.1]) by smtp.top.net.ua (Postfix) with ESMTP id 6BA5660A155 for ; Mon, 10 Jul 2006 12:27:04 +0300 (EEST) Received: by smtp.top.net.ua (Postfix, from userid 1012) id 483E760A0B9; Mon, 10 Jul 2006 12:27:04 +0300 (EEST) Date: Mon, 10 Jul 2006 12:27:04 +0300 From: Maxim Tuliuk To: freebsd-stable@freebsd.org Message-ID: <20060710092704.GA34395@top.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV using ClamSMTP Subject: troubles with acpi in 6.1-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 09:27:09 -0000 Hello! I've upgraded my computer to 6.1-stable and during booting seen this: Jul 7 11:21:41 zoo kernel: port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Jul 7 11:21:41 zoo kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Jul 7 11:21:41 zoo kernel: cpu0: on acpi0 Jul 7 11:21:41 zoo kernel: acpi_throttle0: on cpu0 Jul 7 11:21:41 zoo kernel: acpi_button0: on acpi0 Jul 7 11:21:41 zoo kernel: pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f,0x6000-0x607f on acpi0 Jul 7 11:21:41 zoo kernel: pci0: on pcib0 Jul 7 11:21:41 zoo kernel: agp0: mem 0xe5000000-0xe5ffffff at device 0.0 on pci0 Jul 7 11:21:41 zoo kernel: pcib1: at device 1.0 on pci0 Jul 7 11:21:41 zoo kernel: pci1: on pcib1 Jul 7 11:21:41 zoo kernel: drm0: mem 0xe0000000-0xe1ffffff,0xe2000000-0xe2003fff,0xe3000000-0xe37fffff irq 11 at device 0.0 on pci1 Jul 7 11:21:41 zoo kernel: info: [drm] AGP at 0xe5000000 16MB Jul 7 11:21:41 zoo kernel: info: [drm] Initialized mga 3.2.2 20060319 Jul 7 11:21:41 zoo kernel: isab0: at device 7.0 on pci0 Jul 7 11:21:41 zoo kernel: isa0: on isab0 Jul 7 11:21:41 zoo kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 7.1 on pci0 Jul 7 11:21:41 zoo kernel: ata0: on atapci0 Jul 7 11:21:41 zoo kernel: ata1: on atapci0 Jul 7 11:21:41 zoo kernel: uhci0: port 0xc400-0xc41f irq 5 at device 7.2 on pci0 Jul 7 11:21:41 zoo kernel: uhci0: [GIANT-LOCKED] Jul 7 11:21:41 zoo kernel: usb0: on uhci0 Jul 7 11:21:41 zoo kernel: usb0: USB revision 1.0 Jul 7 11:21:41 zoo kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:21:41 zoo kernel: uhub0: 2 ports with 2 removable, self powered Jul 7 11:21:41 zoo kernel: uhci1: port 0xc800-0xc81f irq 5 at device 7.3 on pci0 Jul 7 11:21:41 zoo kernel: uhci1: [GIANT-LOCKED] Jul 7 11:21:41 zoo kernel: usb1: on uhci1 Jul 7 11:21:41 zoo kernel: usb1: USB revision 1.0 Jul 7 11:21:41 zoo kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:21:41 zoo kernel: uhub1: 2 ports with 2 removable, self powered Jul 7 11:21:41 zoo kernel: pci0: at device 7.4 (no driver attached) Jul 7 11:21:41 zoo kernel: pcm0: port 0xcc00-0xccff,0xd000-0xd003,0xd400-0xd403 irq 10 at device 7.5 on pci0 Jul 7 11:21:41 zoo kernel: pcm0: Jul 7 11:21:41 zoo kernel: fxp0: port 0xdc00-0xdc3f mem 0xe7041000-0xe7041fff,0xe7000000-0xe701ffff irq 10 at device 10.0 on pci0 Jul 7 11:21:41 zoo kernel: miibus0: on fxp0 Jul 7 11:21:41 zoo kernel: inphy0: on miibus0 Jul 7 11:21:41 zoo kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:21:41 zoo kernel: fxp0: Ethernet address: 00:02:b3:60:20:2b Jul 7 11:21:41 zoo kernel: fxp1: port 0xe000-0xe03f mem 0xe7040000-0xe7040fff,0xe7020000-0xe703ffff irq 11 at device 12.0 on pci0 Jul 7 11:21:41 zoo kernel: miibus1: on fxp1 Jul 7 11:21:41 zoo kernel: inphy1: on miibus1 Jul 7 11:21:41 zoo kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:21:41 zoo kernel: fxp1: Ethernet address: 00:02:b3:60:2c:8e Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: fdc0: [FAST] Jul 7 11:21:41 zoo kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Jul 7 11:21:41 zoo kernel: sio0: type 16550A Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 Jul 7 11:21:41 zoo kernel: sio1: type 16550A Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: ppc0: port 0x378-0x37f irq 7 on acpi0 Jul 7 11:21:41 zoo kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jul 7 11:21:41 zoo kernel: ppbus0: on ppc0 Jul 7 11:21:41 zoo kernel: plip0: on ppbus0 Jul 7 11:21:41 zoo kernel: lpt0: on ppbus0 Jul 7 11:21:41 zoo kernel: lpt0: Interrupt-driven port Jul 7 11:21:41 zoo kernel: ppi0: on ppbus0 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Jul 7 11:21:41 zoo kernel: atkbd0: irq 1 on atkbdc0 Jul 7 11:21:41 zoo kernel: kbd0 at atkbd0 Jul 7 11:21:41 zoo kernel: atkbd0: [GIANT-LOCKED] Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:21:41 zoo kernel: pmtimer0 on isa0 Jul 7 11:21:41 zoo kernel: orm0: at iomem 0xc0000-0xc87ff,0xcc000-0xcffff on isa0 Jul 7 11:21:41 zoo kernel: sc0: at flags 0x100 on isa0 Jul 7 11:21:41 zoo kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jul 7 11:21:41 zoo kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 7 11:21:41 zoo kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 2, iclass 3/1 Jul 7 11:21:41 zoo kernel: ums0: 3 buttons and Z dir. Jul 7 11:21:41 zoo kernel: Timecounter "TSC" frequency 800037596 Hz quality 800 Jul 7 11:21:41 zoo kernel: Timecounters tick every 1.000 msec Jul 7 11:21:41 zoo kernel: ad0: 76351MB at ata0-master UDMA66 Jul 7 11:21:41 zoo kernel: acd0: CDROM at ata1-master UDMA33 Jul 7 11:21:41 zoo kernel: Trying to mount root from ufs:/dev/ad0s1a Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:21:41 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:21:41 zoo kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Jul 7 11:23:58 zoo kernel: 3884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Jul 7 11:23:58 zoo kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Jul 7 11:23:58 zoo kernel: cpu0: on acpi0 Jul 7 11:23:58 zoo kernel: acpi_throttle0: on cpu0 Jul 7 11:23:58 zoo kernel: acpi_button0: on acpi0 Jul 7 11:23:58 zoo kernel: pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f,0x6000-0x607f on acpi0 Jul 7 11:23:58 zoo kernel: pci0: on pcib0 Jul 7 11:23:58 zoo kernel: agp0: mem 0xe5000000-0xe5ffffff at device 0.0 on pci0 Jul 7 11:23:58 zoo kernel: pcib1: at device 1.0 on pci0 Jul 7 11:23:58 zoo kernel: pci1: on pcib1 Jul 7 11:23:58 zoo kernel: drm0: mem 0xe0000000-0xe1ffffff,0xe2000000-0xe2003fff,0xe3000000-0xe37fffff irq 11 at device 0.0 on pci1 Jul 7 11:23:58 zoo kernel: info: [drm] AGP at 0xe5000000 16MB Jul 7 11:23:58 zoo kernel: info: [drm] Initialized mga 3.2.2 20060319 Jul 7 11:23:58 zoo kernel: isab0: at device 7.0 on pci0 Jul 7 11:23:58 zoo kernel: isa0: on isab0 Jul 7 11:23:58 zoo kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 7.1 on pci0 Jul 7 11:23:58 zoo kernel: ata0: on atapci0 Jul 7 11:23:58 zoo kernel: ata1: on atapci0 Jul 7 11:23:58 zoo kernel: uhci0: port 0xc400-0xc41f irq 5 at device 7.2 on pci0 Jul 7 11:23:58 zoo kernel: uhci0: [GIANT-LOCKED] Jul 7 11:23:58 zoo kernel: usb0: on uhci0 Jul 7 11:23:58 zoo kernel: usb0: USB revision 1.0 Jul 7 11:23:58 zoo kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:23:58 zoo kernel: uhub0: 2 ports with 2 removable, self powered Jul 7 11:23:58 zoo kernel: uhci1: port 0xc800-0xc81f irq 5 at device 7.3 on pci0 Jul 7 11:23:58 zoo kernel: uhci1: [GIANT-LOCKED] Jul 7 11:23:58 zoo kernel: usb1: on uhci1 Jul 7 11:23:58 zoo kernel: usb1: USB revision 1.0 Jul 7 11:23:58 zoo kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:23:58 zoo kernel: uhub1: 2 ports with 2 removable, self powered Jul 7 11:23:58 zoo kernel: pci0: at device 7.4 (no driver attached) Jul 7 11:23:58 zoo kernel: pcm0: port 0xcc00-0xccff,0xd000-0xd003,0xd400-0xd403 irq 10 at device 7.5 on pci0 Jul 7 11:23:58 zoo kernel: pcm0: Jul 7 11:23:58 zoo kernel: fxp0: port 0xdc00-0xdc3f mem 0xe7041000-0xe7041fff,0xe7000000-0xe701ffff irq 10 at device 10.0 on pci0 Jul 7 11:23:58 zoo kernel: miibus0: on fxp0 Jul 7 11:23:58 zoo kernel: inphy0: on miibus0 Jul 7 11:23:58 zoo kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:23:58 zoo kernel: fxp0: Ethernet address: 00:02:b3:60:20:2b Jul 7 11:23:58 zoo kernel: fxp1: port 0xe000-0xe03f mem 0xe7040000-0xe7040fff,0xe7020000-0xe703ffff irq 11 at device 12.0 on pci0 Jul 7 11:23:58 zoo kernel: miibus1: on fxp1 Jul 7 11:23:58 zoo kernel: inphy1: on miibus1 Jul 7 11:23:58 zoo kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:23:58 zoo kernel: fxp1: Ethernet address: 00:02:b3:60:2c:8e Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: fdc0: [FAST] Jul 7 11:23:58 zoo kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Jul 7 11:23:58 zoo kernel: sio0: type 16550A Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 Jul 7 11:23:58 zoo kernel: sio1: type 16550A Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: ppc0: port 0x378-0x37f irq 7 on acpi0 Jul 7 11:23:58 zoo kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jul 7 11:23:58 zoo kernel: ppbus0: on ppc0 Jul 7 11:23:58 zoo kernel: plip0: on ppbus0 Jul 7 11:23:58 zoo kernel: lpt0: on ppbus0 Jul 7 11:23:58 zoo kernel: lpt0: Interrupt-driven port Jul 7 11:23:58 zoo kernel: ppi0: on ppbus0 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Jul 7 11:23:58 zoo kernel: atkbd0: irq 1 on atkbdc0 Jul 7 11:23:58 zoo kernel: kbd0 at atkbd0 Jul 7 11:23:58 zoo kernel: atkbd0: [GIANT-LOCKED] Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:23:58 zoo kernel: pmtimer0 on isa0 Jul 7 11:23:58 zoo kernel: orm0: at iomem 0xc0000-0xc87ff,0xcc000-0xcffff on isa0 Jul 7 11:23:58 zoo kernel: sc0: at flags 0x100 on isa0 Jul 7 11:23:58 zoo kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jul 7 11:23:58 zoo kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 7 11:23:58 zoo kernel: umass0: Transcend T.sonic 310, rev 2.00/0.02, addr 2 Jul 7 11:23:58 zoo kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 3, iclass 3/1 Jul 7 11:23:58 zoo kernel: ums0: 3 buttons and Z dir. Jul 7 11:23:58 zoo kernel: Timecounter "TSC" frequency 800036283 Hz quality 800 Jul 7 11:23:58 zoo kernel: Timecounters tick every 1.000 msec Jul 7 11:23:58 zoo kernel: ad0: 76351MB at ata0-master UDMA66 Jul 7 11:23:58 zoo kernel: acd0: CDROM at ata1-master UDMA33 Jul 7 11:23:58 zoo kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jul 7 11:23:58 zoo kernel: da0: Removable Direct Access SCSI-0 device Jul 7 11:23:58 zoo kernel: da0: 1.000MB/s transfers Jul 7 11:23:58 zoo kernel: da0: 995MB (2039296 512 byte sectors: 64H 32S/T 995C) Jul 7 11:23:58 zoo kernel: Trying to mount root from ufs:/dev/ad0s1a Jul 7 11:23:58 zoo kernel: WARNING: / was not properly dismounted Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:23:58 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:23:58 zoo kernel: WARNING: /tmp was not properly dismounted Jul 7 11:23:58 zoo kernel: WARNING: /usr was not properly dismounted Jul 7 11:23:58 zoo kernel: WARNING: /var was not properly dismounted Jul 7 11:23:58 zoo kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Jul 7 11:26:03 zoo kernel: 0003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Jul 7 11:26:03 zoo kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Jul 7 11:26:03 zoo kernel: cpu0: on acpi0 Jul 7 11:26:03 zoo kernel: acpi_throttle0: on cpu0 Jul 7 11:26:03 zoo kernel: acpi_button0: on acpi0 Jul 7 11:26:03 zoo kernel: pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f,0x6000-0x607f on acpi0 Jul 7 11:26:03 zoo kernel: pci0: on pcib0 Jul 7 11:26:03 zoo kernel: agp0: mem 0xe5000000-0xe5ffffff at device 0.0 on pci0 Jul 7 11:26:03 zoo kernel: pcib1: at device 1.0 on pci0 Jul 7 11:26:03 zoo kernel: pci1: on pcib1 Jul 7 11:26:03 zoo kernel: drm0: mem 0xe0000000-0xe1ffffff,0xe2000000-0xe2003fff,0xe3000000-0xe37fffff irq 11 at device 0.0 on pci1 Jul 7 11:26:03 zoo kernel: info: [drm] AGP at 0xe5000000 16MB Jul 7 11:26:03 zoo kernel: info: [drm] Initialized mga 3.2.2 20060319 Jul 7 11:26:03 zoo kernel: isab0: at device 7.0 on pci0 Jul 7 11:26:03 zoo kernel: isa0: on isab0 Jul 7 11:26:03 zoo kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 7.1 on pci0 Jul 7 11:26:03 zoo kernel: ata0: on atapci0 Jul 7 11:26:03 zoo kernel: ata1: on atapci0 Jul 7 11:26:03 zoo kernel: uhci0: port 0xc400-0xc41f irq 5 at device 7.2 on pci0 Jul 7 11:26:03 zoo kernel: uhci0: [GIANT-LOCKED] Jul 7 11:26:03 zoo kernel: usb0: on uhci0 Jul 7 11:26:03 zoo kernel: usb0: USB revision 1.0 Jul 7 11:26:03 zoo kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:26:03 zoo kernel: uhub0: 2 ports with 2 removable, self powered Jul 7 11:26:03 zoo kernel: uhci1: port 0xc800-0xc81f irq 5 at device 7.3 on pci0 Jul 7 11:26:03 zoo kernel: uhci1: [GIANT-LOCKED] Jul 7 11:26:03 zoo kernel: usb1: on uhci1 Jul 7 11:26:03 zoo kernel: usb1: USB revision 1.0 Jul 7 11:26:03 zoo kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:26:03 zoo kernel: uhub1: 2 ports with 2 removable, self powered Jul 7 11:26:03 zoo kernel: pci0: at device 7.4 (no driver attached) Jul 7 11:26:03 zoo kernel: pcm0: port 0xcc00-0xccff,0xd000-0xd003,0xd400-0xd403 irq 10 at device 7.5 on pci0 Jul 7 11:26:03 zoo kernel: pcm0: Jul 7 11:26:03 zoo kernel: fxp0: port 0xdc00-0xdc3f mem 0xe7041000-0xe7041fff,0xe7000000-0xe701ffff irq 10 at device 10.0 on pci0 Jul 7 11:26:03 zoo kernel: miibus0: on fxp0 Jul 7 11:26:03 zoo kernel: inphy0: on miibus0 Jul 7 11:26:03 zoo kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:26:03 zoo kernel: fxp0: Ethernet address: 00:02:b3:60:20:2b Jul 7 11:26:03 zoo kernel: fxp1: port 0xe000-0xe03f mem 0xe7040000-0xe7040fff,0xe7020000-0xe703ffff irq 11 at device 12.0 on pci0 Jul 7 11:26:03 zoo kernel: miibus1: on fxp1 Jul 7 11:26:03 zoo kernel: inphy1: on miibus1 Jul 7 11:26:03 zoo kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:26:03 zoo kernel: fxp1: Ethernet address: 00:02:b3:60:2c:8e Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: fdc0: [FAST] Jul 7 11:26:03 zoo kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Jul 7 11:26:03 zoo kernel: sio0: type 16550A Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 Jul 7 11:26:03 zoo kernel: sio1: type 16550A Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: ppc0: port 0x378-0x37f irq 7 on acpi0 Jul 7 11:26:03 zoo kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jul 7 11:26:03 zoo kernel: ppbus0: on ppc0 Jul 7 11:26:03 zoo kernel: plip0: on ppbus0 Jul 7 11:26:03 zoo kernel: lpt0: on ppbus0 Jul 7 11:26:03 zoo kernel: lpt0: Interrupt-driven port Jul 7 11:26:03 zoo kernel: ppi0: on ppbus0 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Jul 7 11:26:03 zoo kernel: atkbd0: irq 1 on atkbdc0 Jul 7 11:26:03 zoo kernel: kbd0 at atkbd0 Jul 7 11:26:03 zoo kernel: atkbd0: [GIANT-LOCKED] Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:26:03 zoo kernel: pmtimer0 on isa0 Jul 7 11:26:03 zoo kernel: orm0: at iomem 0xc0000-0xc87ff,0xcc000-0xcffff on isa0 Jul 7 11:26:03 zoo kernel: sc0: at flags 0x100 on isa0 Jul 7 11:26:03 zoo kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jul 7 11:26:03 zoo kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 7 11:26:03 zoo kernel: umass0: Transcend T.sonic 310, rev 2.00/0.02, addr 2 Jul 7 11:26:03 zoo kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 3, iclass 3/1 Jul 7 11:26:03 zoo kernel: ums0: 3 buttons and Z dir. Jul 7 11:26:03 zoo kernel: Timecounter "TSC" frequency 800034309 Hz quality 800 Jul 7 11:26:03 zoo kernel: Timecounters tick every 1.000 msec Jul 7 11:26:03 zoo kernel: ad0: 76351MB at ata0-master UDMA66 Jul 7 11:26:03 zoo kernel: acd0: CDROM at ata1-master UDMA33 Jul 7 11:26:03 zoo kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jul 7 11:26:03 zoo kernel: da0: Removable Direct Access SCSI-0 device Jul 7 11:26:03 zoo kernel: da0: 1.000MB/s transfers Jul 7 11:26:03 zoo kernel: da0: 995MB (2039296 512 byte sectors: 64H 32S/T 995C) Jul 7 11:26:03 zoo kernel: Trying to mount root from ufs:/dev/ad0s1a Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:26:03 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:26:03 zoo kernel: WARNING: /tmp was not properly dismounted Jul 7 11:26:03 zoo kernel: WARNING: /usr was not properly dismounted Jul 7 11:26:03 zoo kernel: WARNING: /var was not properly dismounted Jul 7 11:26:03 zoo kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Jul 7 11:38:17 zoo kernel: cpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Jul 7 11:38:17 zoo kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Jul 7 11:38:17 zoo kernel: cpu0: on acpi0 Jul 7 11:38:17 zoo kernel: acpi_throttle0: on cpu0 Jul 7 11:38:17 zoo kernel: acpi_button0: on acpi0 Jul 7 11:38:17 zoo kernel: pcib0: port 0xcf8-0xcff,0x4000-0x407f,0x4080-0x40ff,0x5000-0x500f,0x6000-0x607f on acpi0 Jul 7 11:38:17 zoo kernel: pci0: on pcib0 Jul 7 11:38:17 zoo kernel: agp0: mem 0xe5000000-0xe5ffffff at device 0.0 on pci0 Jul 7 11:38:17 zoo kernel: pcib1: at device 1.0 on pci0 Jul 7 11:38:17 zoo kernel: pci1: on pcib1 Jul 7 11:38:17 zoo kernel: drm0: mem 0xe0000000-0xe1ffffff,0xe2000000-0xe2003fff,0xe3000000-0xe37fffff irq 11 at device 0.0 on pci1 Jul 7 11:38:17 zoo kernel: info: [drm] AGP at 0xe5000000 16MB Jul 7 11:38:17 zoo kernel: info: [drm] Initialized mga 3.2.2 20060319 Jul 7 11:38:17 zoo kernel: isab0: at device 7.0 on pci0 Jul 7 11:38:17 zoo kernel: isa0: on isab0 Jul 7 11:38:17 zoo kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 7.1 on pci0 Jul 7 11:38:17 zoo kernel: ata0: on atapci0 Jul 7 11:38:17 zoo kernel: ata1: on atapci0 Jul 7 11:38:17 zoo kernel: uhci0: port 0xc400-0xc41f irq 5 at device 7.2 on pci0 Jul 7 11:38:17 zoo kernel: uhci0: [GIANT-LOCKED] Jul 7 11:38:17 zoo kernel: usb0: on uhci0 Jul 7 11:38:17 zoo kernel: usb0: USB revision 1.0 Jul 7 11:38:17 zoo kernel: uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:38:17 zoo kernel: uhub0: 2 ports with 2 removable, self powered Jul 7 11:38:17 zoo kernel: uhci1: port 0xc800-0xc81f irq 5 at device 7.3 on pci0 Jul 7 11:38:17 zoo kernel: uhci1: [GIANT-LOCKED] Jul 7 11:38:17 zoo kernel: usb1: on uhci1 Jul 7 11:38:17 zoo kernel: usb1: USB revision 1.0 Jul 7 11:38:17 zoo kernel: uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 Jul 7 11:38:17 zoo kernel: uhub1: 2 ports with 2 removable, self powered Jul 7 11:38:17 zoo kernel: pci0: at device 7.4 (no driver attached) Jul 7 11:38:17 zoo kernel: pcm0: port 0xcc00-0xccff,0xd000-0xd003,0xd400-0xd403 irq 10 at device 7.5 on pci0 Jul 7 11:38:17 zoo kernel: pcm0: Jul 7 11:38:17 zoo kernel: fxp0: port 0xdc00-0xdc3f mem 0xe7041000-0xe7041fff,0xe7000000-0xe701ffff irq 10 at device 10.0 on pci0 Jul 7 11:38:17 zoo kernel: miibus0: on fxp0 Jul 7 11:38:17 zoo kernel: inphy0: on miibus0 Jul 7 11:38:17 zoo kernel: inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:38:17 zoo kernel: fxp0: Ethernet address: 00:02:b3:60:20:2b Jul 7 11:38:17 zoo kernel: fxp1: port 0xe000-0xe03f mem 0xe7040000-0xe7040fff,0xe7020000-0xe703ffff irq 11 at device 12.0 on pci0 Jul 7 11:38:17 zoo kernel: miibus1: on fxp1 Jul 7 11:38:17 zoo kernel: inphy1: on miibus1 Jul 7 11:38:17 zoo kernel: inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jul 7 11:38:17 zoo kernel: fxp1: Ethernet address: 00:02:b3:60:2c:8e Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: fdc0: [FAST] Jul 7 11:38:17 zoo kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 Jul 7 11:38:17 zoo kernel: sio0: type 16550A Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 Jul 7 11:38:17 zoo kernel: sio1: type 16550A Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: ppc0: port 0x378-0x37f irq 7 on acpi0 Jul 7 11:38:17 zoo kernel: ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode Jul 7 11:38:17 zoo kernel: ppbus0: on ppc0 Jul 7 11:38:17 zoo kernel: plip0: on ppbus0 Jul 7 11:38:17 zoo kernel: lpt0: on ppbus0 Jul 7 11:38:17 zoo kernel: lpt0: Interrupt-driven port Jul 7 11:38:17 zoo kernel: ppi0: on ppbus0 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0 Jul 7 11:38:17 zoo kernel: atkbd0: irq 1 on atkbdc0 Jul 7 11:38:17 zoo kernel: kbd0 at atkbd0 Jul 7 11:38:17 zoo kernel: atkbd0: [GIANT-LOCKED] Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0x070 (8), val 0x43 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0x071 (8) Jul 7 11:38:17 zoo kernel: pmtimer0 on isa0 Jul 7 11:38:17 zoo kernel: orm0: at iomem 0xc0000-0xc87ff,0xcc000-0xcffff on isa0 Jul 7 11:38:17 zoo kernel: sc0: at flags 0x100 on isa0 Jul 7 11:38:17 zoo kernel: sc0: VGA <16 virtual consoles, flags=0x300> Jul 7 11:38:17 zoo kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jul 7 11:38:17 zoo kernel: umass0: Transcend T.sonic 310, rev 2.00/0.02, addr 2 Jul 7 11:38:17 zoo kernel: ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/20.00, addr 3, iclass 3/1 Jul 7 11:38:17 zoo kernel: ums0: 3 buttons and Z dir. Jul 7 11:38:17 zoo kernel: Timecounter "TSC" frequency 800036972 Hz quality 800 Jul 7 11:38:17 zoo kernel: Timecounters tick every 1.000 msec Jul 7 11:38:17 zoo kernel: ad0: 76351MB at ata0-master UDMA66 Jul 7 11:38:17 zoo kernel: acd0: CDROM at ata1-master UDMA33 Jul 7 11:38:17 zoo kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Jul 7 11:38:17 zoo kernel: da0: Removable Direct Access SCSI-0 device Jul 7 11:38:17 zoo kernel: da0: 1.000MB/s transfers Jul 7 11:38:17 zoo kernel: da0: 995MB (2039296 512 byte sectors: 64H 32S/T 995C) Jul 7 11:38:17 zoo kernel: Trying to mount root from ufs:/dev/ad0s1a Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0xb00 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad read from port 0xcfc (32) Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcf8 (32), val 0x80003884 Jul 7 11:38:17 zoo kernel: acpi: bad write to port 0xcfc (32), val 0x900 Jul 7 11:38:17 zoo kernel: WARNING: /usr was not properly dismounted Jul 7 11:38:17 zoo kernel: WARNING: /var was not properly dismounted Jul 7 11:38:17 zoo kernel: ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding disabled, default to deny, logging disabled Jul 7 11:43:43 zoo kernel: info: [drm] Initialized card for AGP DMA. Jul 7 11:44:34 zoo kernel: pid 846 (gaim), uid 1012: exited on signal 6 (core dumped) I had no problems on 6.1-release. Any suggestions? -- Maxim Tuliuk WWW: http://primats.org.ua/~mt/ ICQ: 21134222 Bike is the freedom of moving From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 09:55:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22F0D16A4E6 for ; Mon, 10 Jul 2006 09:55:44 +0000 (UTC) (envelope-from quetzal@zone3000.net) Received: from mx1.sitevalley.com (sitevalley.com [209.67.60.43]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F8DA43D45 for ; Mon, 10 Jul 2006 09:55:43 +0000 (GMT) (envelope-from quetzal@zone3000.net) Received: from zone3000.kharkov.ua (HELO localhost) (217.144.68.98) by 209.67.61.254 with SMTP; 10 Jul 2006 09:55:41 -0000 Date: Mon, 10 Jul 2006 12:55:13 +0300 From: Nikolay Pavlov To: freebsd-stable@freebsd.org Message-ID: <20060710095513.GA4471@zone3000.net> Mail-Followup-To: Nikolay Pavlov , freebsd-stable@freebsd.org References: <20060707134026.GA1750@zone3000.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060707134026.GA1750@zone3000.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 6.1-RELEASE Subject: Re: Processes in block state in vmstat. X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 09:55:44 -0000 On Friday, 7 July 2006 at 16:40:26 +0300, Nikolay Pavlov wrote: > Hi, folks. > I want to add some additional information about problem related > processes in block state. I see it on my server Dual CPU: Intel(R) > Xeon(TM) CPU 2.40GHz (2399.33-MHz 686-class CPU) with amrd device. It seems my issue could be related this PR http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/94139 i have submitted follow-up report with backtraces. > > FreeBSD 6.1-RELEASE-p1 > > I see some httpd daemons in D state: > > procs memory page disk faults cpu > r b w avm fre flt re pi po fr sr am0 in sy cs us sy > id > 0 527 0 2173832 94028 49 0 0 0 2722 2658 0 9219 4140 17350 1 7 92 > 0 528 0 2172836 93636 66 0 0 0 218 0 6 504 512 1221 0 2 98 > 0 523 0 2171828 93360 56 0 0 0 188 0 6 551 298 1286 0 2 98 > 0 523 0 2171972 92612 29 0 0 0 189 0 6 520 395 1250 0 2 98 > 30 494 0 2170976 91836 92 0 0 0 333 0 11 448 250 970 0 2 98 > 0 518 0 2171156 90580 43 1 0 0 314 0 10 640 758 1676 0 3 97 > 0 510 0 2170244 89452 61 0 0 0 402 0 14 615 644 1667 0 3 97 > 1 512 0 2170420 89292 1 0 0 0 0 0 0 493 307 1133 0 2 98 > 0 517 0 2169560 86868 110 0 0 0 735 0 27 623 852 1584 0 3 96 > 0 514 0 2168552 87176 53 0 0 0 198 0 0 487 200 1078 0 1 99 > 0 517 0 2178752 84040 1523 0 0 0 1261 0 0 512 2660 1320 2 3 96 > > vmstat -s > > 3129790854 cpu context switches > 1663101011 device interrupts > 5504551 software interrupts > 9321603 traps > 746764672 system calls > 54 kernel threads created > 66887 fork() calls > 9669 vfork() calls > 0 rfork() calls > 4784 swap pager pageins > 5635 swap pager pages paged in > 1902 swap pager pageouts > 3590 swap pager pages paged out > 24668 vnode pager pageins > 64050 vnode pager pages paged in > 0 vnode pager pageouts > 0 vnode pager pages paged out > 28140 page daemon wakeups > 479450699 pages examined by the page daemon > 75270 pages reactivated > 2461680 copy-on-write faults > 3805 copy-on-write optimized faults > 4531914 zero fill pages zeroed > 2732630 zero fill pages prezeroed > 18095 intransit blocking page faults > 8922821 total VM faults taken > 0 pages affected by kernel thread creation > 8018826 pages affected by fork() > 1107169 pages affected by vfork() > 0 pages affected by rfork() > 491039188 pages freed > 393 pages freed by daemon > 5744590 pages freed by exiting processes > 201969 pages active > 184930 pages inactive > 17190 pages in VM cache > 107624 pages wired down > 750 pages free > 4096 bytes per page > 30979017 total name lookups > cache hits (82% pos + 1% neg) system 1% per-directory > deletions 0%, falsehits 0%, toolong 0% > > > vmstat -z > > ITEM SIZE LIMIT USED FREE REQUESTS > > UMA Kegs: 140, 0, 83, 13, 83 > UMA Zones: 480, 0, 83, 5, 83 > UMA Slabs: 64, 0, 2537, 177, 225611 > UMA RCntSlabs: 104, 0, 32769, 13, 2949442 > UMA Hash: 128, 0, 3, 27, 6 > 16 Bucket: 76, 0, 27, 23, 73 > 32 Bucket: 140, 0, 23, 33, 64 > 64 Bucket: 268, 0, 17, 39, 100 > 128 Bucket: 524, 0, 223, 71, 1036 > VM OBJECT: 132, 0, 30655, 2318, 1833813 > MAP: 192, 0, 7, 33, 7 > KMAP ENTRY: 68, 65520, 285, 11251, 78210624 > MAP ENTRY: 68, 0, 215821, 8011, 3882740 > PV ENTRY: 24, 2155135, 1391603, 119877, 42095182 > DP fakepg: 72, 0, 0, 53, 6 > mt_zone: 1024, 0, 174, 126, 174 > 16: 16, 0, 2158, 684, 578060 > 32: 32, 0, 3343, 386, 87211 > 64: 64, 0, 7323, 819, 1449967 > 128: 128, 0, 3507, 333, 519528 > 256: 256, 0, 6226, 509, 181376 > 512: 512, 0, 64, 96, 77544 > 1024: 1024, 0, 55, 73, 38283 > 2048: 2048, 0, 141, 27, 25379 > 4096: 4096, 0, 1990, 135, 84846 > Files: 72, 0, 2924, 1475, 1665330 > PROC: 524, 0, 1936, 220, 76612 > THREAD: 372, 0, 2156, 14, 2156 > KSEGRP: 88, 0, 2156, 84, 2156 > UPCALL: 44, 0, 0, 0, 0 > VMSPACE: 300, 0, 1886, 337, 76512 > mbuf_packet: 256, 0, 66135, 0, 1979970489 > mbuf: 256, 0, 7, 1253, 3511131461 > mbuf_cluster: 2048, 65536, 65538, 0, 1966671403 > mbuf_jumbo_pagesize: 4096, 0, 0, 0, 0 > mbuf_jumbo_9k: 9216, 0, 0, 0, 0 > mbuf_jumbo_16k: 16384, 0, 0, 0, 0 > ACL UMA zone: 388, 0, 0, 0, 0 > g_bio: 132, 0, 0, 87, 79264695 > ata_request: 204, 0, 0, 0, 0 > ata_composite: 196, 0, 0, 0, 0 > VNODE: 272, 0, 27508, 7072, 4868108 > VNODEPOLL: 76, 0, 1, 49, 1 > S VFS Cache: 68, 0, 27595, 2869, 4582987 > L VFS Cache: 291, 0, 1708, 203, 314868 > NAMEI: 1024, 0, 3, 129, 12912949 > DIRHASH: 1024, 0, 495, 41, 4186 > NFSMOUNT: 480, 0, 2, 14, 3 > NFSNODE: 460, 0, 13, 27, 1525 > PIPE: 408, 0, 28, 35, 31594 > KNOTE: 68, 0, 0, 168, 5762 > socket: 356, 16434, 2327, 1699, 277319 > unpcb: 140, 65548, 42, 70, 12935 > ipq: 32, 2147, 0, 0, 2235 > udpcb: 180, 16434, 5, 127, 5531 > inpcb: 180, 16434, 2259, 1393, 258840 > tcpcb: 464, 16424, 2258, 1454, 258840 > tcptw: 48, 3354, 1, 389, 38232 > syncache: 100, 15366, 17, 334, 322283 > hostcache: 76, 15400, 246, 304, 6938 > tcpreass: 20, 4225, 1, 168, 4936 > sackhole: 20, 0, 8, 499, 23975962 > ripcb: 180, 16434, 0, 44, 11 > rtentry: 132, 0, 5, 53, 54 > pfsrctrpl: 100, 0, 0, 0, 0 > pfrulepl: 604, 0, 0, 0, 0 > pfstatepl: 260, 10005, 0, 0, 0 > pfaltqpl: 128, 0, 0, 0, 0 > pfpooladdrpl: 68, 0, 0, 0, 0 > pfrktable: 1240, 0, 0, 0, 0 > pfrkentry: 156, 0, 0, 0, 0 > pfrkentry2: 156, 0, 0, 0, 0 > pffrent: 16, 5075, 0, 0, 0 > pffrag: 48, 0, 0, 0, 0 > pffrcache: 48, 10062, 0, 0, 0 > pffrcent: 12, 50141, 0, 0, 0 > pfstatescrub: 28, 0, 0, 0, 0 > pfiaddrpl: 92, 0, 0, 0, 0 > pfospfen: 108, 0, 0, 0, 0 > pfosfp: 28, 0, 0, 0, 0 > IPFW dynamic rule zone: 108, 0, 0, 0, 0 > SWAPMETA: 276, 121576, 36, 20, 1613 > FFS inode: 132, 0, 27459, 1280, 4866112 > FFS1 dinode: 128, 0, 0, 0, 0 > FFS2 dinode: 256, 0, 27459, 1206, 4866112 > > Intresting thing that everytime i use "vmstat 1" problem gone > and i save my uptime. > > Server is still under load and i see only one process in D state > > 85815 ?? D 0:00.00 /usr/local/sbin/megarc -ldInfo -LAll -a0 > > Also i have found that it's much easy to trigger this state for httpd > when i use low (default) value for MaxSpareServers (I have about > 300 ~ 500 connections all the time) > > > -- > ========================================================================= > = Best regards, Nikolay Pavlov. <<<------------------------------------ = > ========================================================================= > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- ========================================================================= = Best regards, Nikolay Pavlov. <<<------------------------------------ = ========================================================================= From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 10:32:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6EB116A4DE for ; Mon, 10 Jul 2006 10:32:47 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00E0343D76 for ; Mon, 10 Jul 2006 10:32:39 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1Fzt4h-0007Tk-GP for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 03:33:17 -0700 From: Dominik Zalewski Organization: OpenCraft To: freebsd-stable@freebsd.org Date: Mon, 10 Jul 2006 13:27:23 +0300 User-Agent: KMail/1.9.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607101327.23403.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Subject: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 10:32:48 -0000 Hi, I'm using FreeBSD 6.1-STABLE on i386. I have installed openldap-server , pam_ldap , nss_ldap. During booting and when I do /usr/local/etc/rc.d/slapd.sh start , its taking very long time to start. Here is what I'm getting in logfile: slapd[43485]: daemon: shutdown requested and initiated. slapd[43485]: slapd shutdown: waiting for 0 threads to terminate slapd[43485]: slapd stopped. slapd[52141]: @(#) $OpenLDAP: slapd 2.3.24 (Jul 5 2006 14:04:36) $ root@silicon.opencraft.local:/usr/ports/net/openldap23-server/work/openldap-2.3.24/servers/slapd slapd[52141]: nss_ldap: failed to bind to LDAP server ldap://127.0.0.1: Can't contact LDAP server Here is my /etc/nsswitch.conf : group: files ldap < - - group_compat: nis hosts: files dns networks: files passwd: files ldap < - - passwd_compat: nis shells: files When I change it back to : group: compat < - - group_compat: nis hosts: files dns networks: files passwd: compat < - - passwd_compat: nis shells: files then slapd started fine but I without ldap in nsswitch.conf I cant authenticate users via pam_ldap. /etc/rc.conf : slapd_enable="YES" slapd_flags='-h "ldapi://%2fvar%2frun%2fopenldap%2fldapi/ ldap://0.0.0.0/"' slapd_sockets="/var/run/openldap/ldapi" Installed packages: nss_ldap-1.250 openldap-sasl-client-2.3.24 openldap-server-2.3.24 pam_ldap-1.8.2 /usr/local/etc/openldap/slapd.conf # Global section include /usr/local/etc/openldap/schema/core.schema include /usr/local/etc/openldap/schema/cosine.schema include /usr/local/etc/openldap/schema/inetorgperson.schema include /usr/local/etc/openldap/schema/nis.schema include /usr/local/etc/openldap/schema/samba.schema include /usr/local/etc/openldap/schema/phpgwaccount.schema include /usr/local/etc/openldap/schema/phpgwcontact.schema ## Added logging parameters loglevel 256 pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args ## Misc security settings password-hash {MD5} # Load dynamic backend modules: modulepath /usr/local/libexec/openldap moduleload back_bdb ####################################################################### # BDB database definitions ####################################################################### database bdb suffix "dc=opencraft,dc=local" rootdn "cn=Manager,dc=opencraft,dc=local" rootpw directory /var/db/openldap-data mode 0600 # Indices to maintain index objectClass eq index cn,uid,uidNumber,gidNumber,loginShell eq,pres index memberUid eq,pres,sub index phpgwContactOwner pres,eq,sub cachesize 2000 ## ACLs access to dn.exact="" by * read access to dn.children="ou=People,dc=opencraft,dc=local" attrs=userPassword by self write by dn="cn=Manager,ou=People,dc=opencraft,dc=local" write by anonymous auth by * none access to dn.children="ou=People,dc=opencraft,dc=local" attrs=entry,children,posixAccount by dn="cn=Manager,ou=People,dc=opencraft,dc=local" write by users read by anonymous read access to dn.children="ou=Group,dc=opencraft,dc=local" attrs=entry,children,posixGroup by dn="cn=Manager,ou=People,dc=opencraft,dc=local" write by users read by anonymous read access to dn.children="ou=People,dc=opencraft,dc=local" attrs=mail,telephoneNumber by self write by dn="cn=Manager,ou=People,dc=opencraft,dc=local" write by users read by anonymous read access to dn.children="ou=Contacts,dc=opencraft,dc=local" by anonymous read by users write access to * by * read Here are my ldap.conf and nss_ldap.conf # @(#)$Id: ldap.conf,v 1.36 2005/03/23 08:29:59 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). host 127.0.0.1 # The distinguished name of the search base. base dc=opencraft,dc=local # Another way to specify your LDAP server is to provide an # uri with the server name. This allows to use # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) #ldap_version 3 # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn cn=proxyuser,dc=padl,dc=com # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) #rootbinddn cn=manager,dc=padl,dc=com # The port. # Optional: default is 389. #port 389 # The search scope. #scope sub #scope one #scope base # Search timelimit #timelimit 30 # Bind/connect timelimit #bind_timelimit 30 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 # Filter to AND with uid=%s #pam_filter objectclass=account # The user ID attribute (defaults to uid) #pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) #pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. #pam_check_host_attr yes # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn cn=PAM,ou=Groups,dc=padl,dc=com # Group member attribute #pam_member_attribute uniquemember # Specify a minium or maximum UID number allowed #pam_min_uid 0 #pam_max_uid 0 # Template login attribute, default template user # (can be overriden by value of former attribute # in user's entry) #pam_login_attribute userPrincipalName #pam_template_login_attribute uid #pam_template_login nobody # HEADS UP: the pam_crypt, pam_nds_passwd, # and pam_ad_passwd options are no # longer supported. # # If you are using XAD, you can set pam_password # to racf, ad, or exop. Make sure that you have # SSL enabled. # Do not hash the password at all; presume # the directory server will do it, if # necessary. This is the default. #pam_password clear # Hash password locally; required for University of # Michigan LDAP server, and works with Netscape # Directory Server if you're using the UNIX-Crypt # hash mechanism and not using the NT Synchronization # service. #pam_password crypt # Remove old password first, then update in # cleartext. Necessary for use with Novell # Directory Services (NDS) #pam_password clear_remove_old #pam_password nds # RACF is an alias for the above. For use with # IBM RACF #pam_password racf # Update Active Directory password, by # creating Unicode password and updating # unicodePwd attribute. #pam_password ad # Use the OpenLDAP password change # extended operation to update the password. #pam_password exop # Redirect users to a URL or somesuch on password # changes. #pam_password_prohibit_message Please visit http://internal to change your password. # RFC2307bis naming contexts # Syntax: # nss_base_XXX base?scope?filter # where scope is {base,one,sub} # and filter is a filter to be &'d with the # default filter. # You can omit the suffix eg: # nss_base_passwd ou=People, # to append the default base DN but this # may incur a small performance impact. nss_base_passwd ou=People,dc=opencraft,dc=local?one nss_base_shadow ou=People,dc=opencraft,dc=local?one nss_base_group ou=Group,dc=opencraft,dc=local?one #nss_base_hosts ou=Hosts,dc=padl,dc=com?one #nss_base_services ou=Services,dc=padl,dc=com?one #nss_base_networks ou=Networks,dc=padl,dc=com?one #nss_base_protocols ou=Protocols,dc=padl,dc=com?one #nss_base_rpc ou=Rpc,dc=padl,dc=com?one #nss_base_ethers ou=Ethers,dc=padl,dc=com?one #nss_base_netmasks ou=Networks,dc=padl,dc=com?ne #nss_base_bootparams ou=Ethers,dc=padl,dc=com?one #nss_base_aliases ou=Aliases,dc=padl,dc=com?one #nss_base_netgroup ou=Netgroup,dc=padl,dc=com?one # attribute/objectclass mapping # Syntax: #nss_map_attribute rfc2307attribute mapped_attribute #nss_map_objectclass rfc2307objectclass mapped_objectclass # configure --enable-nds is no longer supported. # NDS mappings #nss_map_attribute uniqueMember member # Services for UNIX 3.5 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount User #nss_map_attribute uid msSFU30Name #nss_map_attribute uniqueMember msSFU30PosixMember #nss_map_attribute userPassword msSFU30Password #nss_map_attribute homeDirectory msSFU30HomeDirectory #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_objectclass posixGroup Group #pam_login_attribute msSFU30Name #pam_filter objectclass=User #pam_password ad # configure --enable-mssfu-schema is no longer supported. # Services for UNIX 2.0 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount user #nss_map_attribute uid msSFUName #nss_map_attribute uniqueMember posixMember #nss_map_attribute userPassword msSFUPassword #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup Group #nss_map_attribute cn msSFUName #pam_login_attribute msSFUName #pam_filter objectclass=User #pam_password ad # RFC 2307 (AD) mappings #nss_map_objectclass posixAccount user #nss_map_objectclass shadowAccount user #nss_map_attribute uid sAMAccountName #nss_map_attribute homeDirectory unixHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup group #nss_map_attribute uniqueMember member #pam_login_attribute sAMAccountName #pam_filter objectclass=User #pam_password ad # configure --enable-authpassword is no longer supported # AuthPassword mappings #nss_map_attribute userPassword authPassword # AIX SecureWay mappings #nss_map_objectclass posixAccount aixAccount #nss_base_passwd ou=aixaccount,?one #nss_map_attribute uid userName #nss_map_attribute gidNumber gid #nss_map_attribute uidNumber uid #nss_map_attribute userPassword passwordChar #nss_map_objectclass posixGroup aixAccessGroup #nss_base_group ou=aixgroup,?one #nss_map_attribute cn groupName #nss_map_attribute uniqueMember member #pam_login_attribute userName #pam_filter objectclass=aixAccount #pam_password clear # Netscape SDK LDAPS #ssl on # Netscape SDK SSL options #sslpath /etc/ssl/certs/cert7.db # OpenLDAP SSL mechanism # start_tls mechanism uses the normal LDAP port, LDAPS typically 636 #ssl start_tls #ssl on # OpenLDAP SSL options # Require and verify server certificate (yes/no) # Default is to use libldap's default behavior, which can be configured in # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes". #tls_checkpeer yes # CA certificates for server certificate verification # At least one of these are required if tls_checkpeer is "yes" #tls_cacertfile /etc/ssl/ca.cert #tls_cacertdir /etc/ssl/certs # Seed the PRNG if /dev/urandom is not provided #tls_randfile /var/run/egd-pool # SSL cipher suite # See man ciphers for syntax #tls_ciphers TLSv1 # Client certificate and key # Use these, if your server requires client authentication. #tls_cert #tls_key # Disable SASL security layers. This is needed for AD. #sasl_secprops maxssf=0 # Override the default Kerberos ticket cache location. #krb5_ccname FILE:/etc/.ldapcache # SASL mechanism for PAM authentication - use is experimental # at present and does not support password policy control #pam_sasl_mech DIGEST-MD5 Any ideas ? Thank you in advance, Dominik Zalewski From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 11:43:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8145516A4DA for ; Mon, 10 Jul 2006 11:43:26 +0000 (UTC) (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 0D41543D5C for ; Mon, 10 Jul 2006 11:43:23 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp141-127.lns2.adl2.internode.on.net [59.167.141.127]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k6ABhEPw036098 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 21:13:16 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Mon, 10 Jul 2006 21:13:12 +0930 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> In-Reply-To: <200607101327.23403.dzalewski@open-craft.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1180699.gkfRUXPWi6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607102113.14004.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Dominik Zalewski Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 11:43:26 -0000 --nextPart1180699.gkfRUXPWi6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 10 July 2006 19:57, Dominik Zalewski wrote: > I'm using FreeBSD 6.1-STABLE on i386. I have installed openldap-server , > pam_ldap , nss_ldap. During booting and when I > do /usr/local/etc/rc.d/slapd.sh start , its taking very long time to star= t. > Here is what I'm getting in logfile: You might want to move the file to /etc/rc.d so it can get started earlier. I changed the headers to look like so too.. # PROVIDE: slapd # REQUIRE: NETWORKING # BEFORE: securelevel # KEYWORD: FreeBSD shutdown My /etc/nsswitch.conf is.. group: files ldap hosts: files dns networks: files passwd: files ldap shells: files =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 --nextPart1180699.gkfRUXPWi6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEsj1R5ZPcIHs/zowRAkkmAJ9Mr/rkszSwqM1JVf2GYr+k+vPQmwCeNIfZ LpHGOMAilSpCUaqZ5KZ9KMw= =2HzJ -----END PGP SIGNATURE----- --nextPart1180699.gkfRUXPWi6-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 11:50:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 91B4A16A4DD for ; Mon, 10 Jul 2006 11:50:15 +0000 (UTC) (envelope-from maenaka@pluto.dti.ne.jp) Received: from smtp11.dti.ne.jp (smtp11.dti.ne.jp [202.216.231.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF45E43D5F for ; Mon, 10 Jul 2006 11:50:09 +0000 (GMT) (envelope-from maenaka@pluto.dti.ne.jp) Received: from towerrecords.minidns.net (221x254x158x92.ap221.ftth.ucom.ne.jp [221.254.158.92]) by smtp11.dti.ne.jp (3.11s) with ESMTP AUTH id k6ABo8J9025643 for ; Mon, 10 Jul 2006 20:50:08 +0900 (JST) Received: from [127.0.0.1] (towerrecords.minidns.net [192.168.0.1]) by towerrecords.minidns.net (Postfix) with ESMTP id 2B87F4832 for ; Mon, 10 Jul 2006 20:50:08 +0900 (JST) From: "UEMURA (fka. MAENAKA) Tetsuya" To: freebsd-stable@freebsd.org In-Reply-To: <200607101327.23403.dzalewski@open-craft.com> References: <200607101327.23403.dzalewski@open-craft.com> X-DBMail-PhysMessage-ID: 155474 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.24.02 [ja] Message-Id: <20060710115008.2B87F4832@towerrecords.minidns.net> Date: Mon, 10 Jul 2006 20:50:08 +0900 (JST) Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 11:50:15 -0000 Posted on Mon, 10 Jul 2006 13:27:23 +0300 by author Dominik Zalewski > Here are my ldap.conf and nss_ldap.conf > #bind_policy hard Change "hard" to "soft" and your problem would go away. -- UEMURA (fka. MAENAKA) Tetsuya From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 11:59:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89C7616A4DD for ; Mon, 10 Jul 2006 11:59:24 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout1-sn1.fre.skanova.net (pne-smtpout1-sn1.fre.skanova.net [81.228.11.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id E690D43D45 for ; Mon, 10 Jul 2006 11:59:13 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout1-sn1.fre.skanova.net (7.2.075) id 44A1364D002B3EA3 for freebsd-stable@freebsd.org; Mon, 10 Jul 2006 13:59:12 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id 547A461D58 for ; Mon, 10 Jul 2006 13:59:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxMVrCMsYnVE for ; Mon, 10 Jul 2006 13:59:08 +0200 (CEST) Received: from [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01] (unknown [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01]) by elfi.stromnet.org (Postfix) with ESMTP id 6EE4961D36 for ; Mon, 10 Jul 2006 13:59:08 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Mon, 10 Jul 2006 13:59:20 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.750) Subject: Re: GEOM problems again... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 11:59:24 -0000 On 10 jul 2006, at 11.09, Johan Str=F6m wrote: > > On 21 maj 2006, at 11.16, Johan Str=F6m wrote: > >> Hi >> >> I've had problems before with GEOM mirror and my SATA drives, and =20 >> i've posted about it here before too. The solution seemd to be a =20 >> change of motherboard, this reduced the crash very much (and also =20 >> the speeds archieved was greatly improved, from 10-15MB/s to =20 >> 40-50MB/s..). >> However after the change i had one or two crashes, but now it has =20 >> been running for well over 50-60 days or so without any problems. >> Then, 11 days ago I upgraded to 6.1... And now I got these =20 >> "crashe"s again (the mirror is crashed that is, the system still =20 >> runs fine): >> >> May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached >> May 21 02:04:58 elfi kernel: subdisk6: detached >> May 21 02:04:58 elfi kernel: ad6: detached >> May 21 02:04:58 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad6s1 disconnected. >> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >> (offset=3D11006308352, length=3D2048)]error =3D 6 >> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >> (offset=3D164847927296, length=3D131072)]error =3D 6 >> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >> (offset=3D256680296448, length=3D32768)]error =3D 6 >> >> >> Some info about the controller and disks: >> >> May 9 22:46:52 elfi kernel: ata1: on atapci0 >> May 9 22:46:52 elfi kernel: atapci1: > controller> port =20 >> 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0x7f00-0x7f0f=20= >> ,0x7c0 >> 0-0x7c7f irq 22 at device 11.0 on pci0 >> >> May 9 22:46:52 elfi kernel: ad4: 286188MB > BANC1G10> at ata2-master SATA150 >> May 9 22:46:52 elfi kernel: ad6: 286188MB > BANC1G10> at ata3-master SATA150 >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1 created =20 >> (id=3D4118114647). >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad4s1 detected. >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad6s1 detected. >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad6s1 activated. >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad4s1 activated. >> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> mirror/gm0s1 launched. >> May 9 22:46:52 elfi kernel: Trying to mount root from ufs:/dev/=20 >> mirror/gm0s1a >> >> Anyone got any new clues? Afaik the disks should be working fine =20 >> (they are 6 months old and this same problem has occured multiple =20 >> times...) >> >> Hope to solve this ;) >> >> Thanks >> Johan >> > > Here we go again > > Jul 7 16:20:09 elfi kernel: ad4: FAILURE - device detached > Jul 7 16:20:09 elfi kernel: subdisk4: detached > Jul 7 16:20:09 elfi kernel: ad4: detached > Jul 7 16:20:09 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 > ad4s1 disconnected. > Jul 7 16:20:09 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 > (offset=3D88896847872, length=3D32768)]error =3D 6 > > However no read read timeouts etc as before, just this. 18 days =20 > uptime this time (i've rebooted for other reasons since last mail). =20= > It always seems to be ad4 that is disconnecting.. I'm going to do =20 > some disk tests on it but i doubt it will give anything since i've =20 > had similiar problems from day one (did tests at that time w/o =20 > problems) with this gmirror setup (new disks). > > Johan Followup, I ran over the disk with Maxtors own test program, full =20 length test. Not a single problem. After reboot the raid is rebuilding fine: GEOM_MIRROR: Device gm0s1: rebuilding provider ad4s1. As usual it seems i cannot get the controller/driver to redetect the =20 disk using atacontrol etc.. Johan > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-=20 > unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 12:20:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6480616A4DF for ; Mon, 10 Jul 2006 12:20:51 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1178443D5F for ; Mon, 10 Jul 2006 12:20:49 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1FzulT-0008Ms-Uz; Mon, 10 Jul 2006 05:21:28 -0700 From: Dominik Zalewski Organization: OpenCraft To: "Daniel O'Connor" Date: Mon, 10 Jul 2006 15:15:47 +0300 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> In-Reply-To: <200607102113.14004.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607101515.48081.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 12:20:51 -0000 On Monday 10 July 2006 14:43, Daniel O'Connor wrote: > On Monday 10 July 2006 19:57, Dominik Zalewski wrote: > > I'm using FreeBSD 6.1-STABLE on i386. I have installed openldap-server , > > pam_ldap , nss_ldap. During booting and when I > > do /usr/local/etc/rc.d/slapd.sh start , its taking very long time to > > start. Here is what I'm getting in logfile: > > You might want to move the file to /etc/rc.d so it can get started earlier. > > I changed the headers to look like so too.. > # PROVIDE: slapd > # REQUIRE: NETWORKING > # BEFORE: securelevel > # KEYWORD: FreeBSD shutdown > > My /etc/nsswitch.conf is.. > group: files ldap > hosts: files dns > networks: files > passwd: files ldap > shells: files I did it. No results. Same error messages in logfile. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 12:21:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C148F16A4E1 for ; Mon, 10 Jul 2006 12:21:10 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7ACEA43D53 for ; Mon, 10 Jul 2006 12:21:04 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1Fzuli-0008Q8-K5; Mon, 10 Jul 2006 05:21:43 -0700 From: Dominik Zalewski Organization: OpenCraft To: "UEMURA (fka. MAENAKA) Tetsuya" Date: Mon, 10 Jul 2006 15:16:02 +0300 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> <20060710114942.1D6464831@towerrecords.minidns.net> In-Reply-To: <20060710114942.1D6464831@towerrecords.minidns.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607101516.02857.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-stable@freebsd.org Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 12:21:10 -0000 On Monday 10 July 2006 14:49, UEMURA (fka. MAENAKA) Tetsuya wrote: > Posted on Mon, 10 Jul 2006 13:27:23 +0300 > by author Dominik Zalewski > > > Here are my ldap.conf and nss_ldap.conf > > #bind_policy hard > > Change "hard" to "soft" and your problem would go away. I did it. No results. Same error messages in logfile. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 13:06:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1821E16A4DA for ; Mon, 10 Jul 2006 13:06:01 +0000 (UTC) (envelope-from dzalewski@open-craft.com) Received: from zeus.lunarpages.com (zeus.lunarpages.com [216.193.211.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFF0943D49 for ; Mon, 10 Jul 2006 13:06:00 +0000 (GMT) (envelope-from dzalewski@open-craft.com) Received: from [196.218.200.205] (helo=[10.0.0.189]) by zeus.lunarpages.com with esmtpa (Exim 4.52) id 1FzvT8-0001sV-MR; Mon, 10 Jul 2006 06:06:35 -0700 From: Dominik Zalewski Organization: OpenCraft To: freebsd-stable@freebsd.org Date: Mon, 10 Jul 2006 16:00:56 +0300 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> In-Reply-To: <200607102113.14004.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607101600.56911.dzalewski@open-craft.com> X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - zeus.lunarpages.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - open-craft.com X-Source: X-Source-Args: X-Source-Dir: Cc: "UEMURA \(fka. MAENAKA\) Tetsuya" Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 13:06:01 -0000 On Monday 10 July 2006 14:43, Daniel O'Connor wrote: > On Monday 10 July 2006 19:57, Dominik Zalewski wrote: > > I'm using FreeBSD 6.1-STABLE on i386. I have installed openldap-server , > > pam_ldap , nss_ldap. During booting and when I > > do /usr/local/etc/rc.d/slapd.sh start , its taking very long time to > > start. Here is what I'm getting in logfile: > > You might want to move the file to /etc/rc.d so it can get started earlier. > > I changed the headers to look like so too.. > # PROVIDE: slapd > # REQUIRE: NETWORKING > # BEFORE: securelevel > # KEYWORD: FreeBSD shutdown > > My /etc/nsswitch.conf is.. > group: files ldap > hosts: files dns > networks: files > passwd: files ldap > shells: files Still the same problem. I tried also to change bind_policy to soft. Can you show me your nss_ldap.conf ? Problem is after I change things in /dev/nsswitch.conf. If I live it like this: group: compat hosts: files dns networks: files passwd: compat shells: files I start slapd using /etc/rc.d/slapd start , then I change /etc/nsswitch.conf to: group: files ldap hosts: files dns networks: files passwd: files ldap shells: files Everything is fine and users can login via ssh using their ldap password. I can boot server with first configuration and run some script that will copy second nsswitch.conf , but I dont like this solution and I dont understand why its not working. Any help welcome :) Dominik From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 13:27:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DB96D16A4DA for ; Mon, 10 Jul 2006 13:27:44 +0000 (UTC) (envelope-from e-masson@kisoft-services.com) Received: from kraid.nerim.net (smtp-101-monday.nerim.net [62.4.16.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5505C43D46 for ; Mon, 10 Jul 2006 13:27:43 +0000 (GMT) (envelope-from e-masson@kisoft-services.com) Received: from srvbsdnanssv.interne.kisoft-services.com (kisoft.net1.nerim.net [62.212.107.51]) by kraid.nerim.net (Postfix) with ESMTP id 693764106D; Mon, 10 Jul 2006 15:27:38 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by srvbsdnanssv.interne.kisoft-services.com (Postfix) with ESMTP id F15B9C8D2; Mon, 10 Jul 2006 15:27:43 +0200 (CEST) X-Virus-Scanned: amavisd-new at interne.kisoft-services.com Received: from srvbsdnanssv.interne.kisoft-services.com ([127.0.0.1]) by localhost (srvbsdnanssv.interne.kisoft-services.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rvuRtpun8SFq; Mon, 10 Jul 2006 15:27:39 +0200 (CEST) Received: by srvbsdnanssv.interne.kisoft-services.com (Postfix, from userid 1001) id 61F4DC8D0; Mon, 10 Jul 2006 15:27:39 +0200 (CEST) To: Dominik Zalewski From: Eric Masson In-Reply-To: <200607101600.56911.dzalewski@open-craft.com> (Dominik Zalewski's message of "Mon, 10 Jul 2006 16:00:56 +0300") References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> <200607101600.56911.dzalewski@open-craft.com> X-Operating-System: FreeBSD 5.5-RELEASE-p1 i386 Date: Mon, 10 Jul 2006 15:27:39 +0200 Message-ID: <86fyh9tws4.fsf@srvbsdnanssv.interne.kisoft-services.com> User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b27 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org, "UEMURA \(fka. MAENAKA\) Tetsuya" Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 13:27:44 -0000 Dominik Zalewski writes: Hi, > Problem is after I change things in /dev/nsswitch.conf. If I live it like > this: > > group: compat > passwd: compat > > I start slapd using /etc/rc.d/slapd start , then I change /etc/nsswitch.conf > to: > > group: files ldap > passwd: files ldap > > Everything is fine and users can login via ssh using their ldap password. I > can boot server with first configuration and run some script that will copy > second nsswitch.conf , but I dont like this solution and I dont understand > why its not working. Chicken & Egg problem, the system queries the ldap backend to get informations about the account it will use to start the ldap backend. I've made a change to /etc/rc.d/slapd that copies a ldap disabled nsswitch.conf to /etc in start_precmd() and then a ldap enabled nsswitch.conf to /etc in start_postcmd(). I've tried to toy with backend options in nsswitch.conf but no luck atm. Seems I'm not alone, see <20060707161801.GB42118@dimma.mow.oilspace.com> regarding "nsswitch.conf problem with group status code" group: files [success=return notfound=continue unavail=continue tryagain=continue] ldap passwd: files [success=return notfound=continue unavail=continue tryagain=continue] ldap Regards Éric Masson -- l'anarchie, c'est pt'etre pas genial comme mode de gouvernement, mais c'est mieux que pas de gouvernement du tout. -+- Kevin in -+- Ni Root, ni Maître. -+- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 14:40:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DEEB216A4DD for ; Mon, 10 Jul 2006 14:40:10 +0000 (UTC) (envelope-from vladgalu@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD8D643D4C for ; Mon, 10 Jul 2006 14:40:09 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by nf-out-0910.google.com with SMTP id c29so788324nfb for ; Mon, 10 Jul 2006 07:40:08 -0700 (PDT) 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=MO+s8n+egBkIUn4g2hLujhU8CjojKdRdHOASIJHhdOLhEOF2Fj++3trqa5NRx66IQxCMxnIiXKIWQESaHTHzr3mFSdKRqoQcb8ka4h/sK5S9ypAEkULTXJKokFGCiO3KY7tVfjX+dRF7l/esjfJIdLg2n+zjjbiD/lDH+S6CMjw= Received: by 10.49.87.7 with SMTP id p7mr3806522nfl; Mon, 10 Jul 2006 07:40:08 -0700 (PDT) Received: by 10.48.250.2 with HTTP; Mon, 10 Jul 2006 07:40:08 -0700 (PDT) Message-ID: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> Date: Mon, 10 Jul 2006 17:40:08 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 14:40:11 -0000 Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm using 1.36 along with a RELENG_6 tree, since it works better (read: it works). From the HEAD commit messages I understand that some MFCs would've been in order by now. Are there any show-stoppers that push that schedule ahead ? -- 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-stable@FreeBSD.ORG Mon Jul 10 15:15:49 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2516216A4DA for ; Mon, 10 Jul 2006 15:15:49 +0000 (UTC) (envelope-from maenaka@pluto.dti.ne.jp) Received: from smtp11.dti.ne.jp (smtp11.dti.ne.jp [202.216.231.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id A189B43D49 for ; Mon, 10 Jul 2006 15:15:48 +0000 (GMT) (envelope-from maenaka@pluto.dti.ne.jp) Received: from towerrecords.minidns.net (221x254x158x92.ap221.ftth.ucom.ne.jp [221.254.158.92]) by smtp11.dti.ne.jp (3.11s) with ESMTP AUTH id k6AFFlDD014793 for ; Tue, 11 Jul 2006 00:15:47 +0900 (JST) Received: from [127.0.0.1] (towerrecords.minidns.net [192.168.0.1]) by towerrecords.minidns.net (Postfix) with ESMTP id CC8714849 for ; Tue, 11 Jul 2006 00:15:46 +0900 (JST) From: "UEMURA (fka. MAENAKA) Tetsuya" To: freebsd-stable@freebsd.org In-Reply-To: <86fyh9tws4.fsf@srvbsdnanssv.interne.kisoft-services.com> References: <200607101600.56911.dzalewski@open-craft.com> <86fyh9tws4.fsf@srvbsdnanssv.interne.kisoft-services.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.24.02 [ja] Message-Id: <20060710151546.CC8714849@towerrecords.minidns.net> Date: Tue, 11 Jul 2006 00:15:46 +0900 (JST) Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 15:15:49 -0000 Posted on Mon, 10 Jul 2006 15:27:39 +0200 by author Eric Masson > Chicken & Egg problem, the system queries the ldap backend to get > informations about the account it will use to start the ldap backend. Indeed. So that by adding `bind_policy soft' to nss_ldap.conf to force nss to quit querying immediately if LDAP server isn't ready. Note that by default, LDAP server tries to resolv user:ldap and group:ldap, and of course both must be resolvable without LDAP server itself, add user:ldap and group:ldap to /etc files. Anyway, my nss_ldap.conf has only the follwing 4 lines, FYI. maenaka@~> grep -vE '^#|^$' < /usr/local/etc/nss_ldap.conf base dc=ldapserver uri ldapi://%2fvar%2frun%2fopenldap%2fldapi/ bind_timelimit 5 bind_policy soft maenaka@~> ls -laR /var/run/openldap/ total 8 drwxrwxr-x 2 root ldap 512 Jul 9 00:13 . drwxr-xr-x 8 root wheel 1024 Jul 11 00:14 .. srwxrwxrwx 1 root ldap 0 Jul 9 00:13 ldapi -rw-r--r-- 1 ldap ldap 94 Jul 9 00:13 slapd.args -rw-r--r-- 1 ldap ldap 6 Jul 9 00:13 slapd.pid -- UEMURA (fka. MAENAKA) Tetsuya From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 15:49:22 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E582116A4E1 for ; Mon, 10 Jul 2006 15:49:22 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C28843D4C for ; Mon, 10 Jul 2006 15:49:22 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id A32A25F36; Mon, 10 Jul 2006 11:49:21 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j+QsvqYh6mlM; Mon, 10 Jul 2006 11:49:18 -0400 (EDT) Received: from [192.168.1.251] (pool-68-161-117-245.ny325.east.verizon.net [68.161.117.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 86D0D5D9C; Mon, 10 Jul 2006 11:49:18 -0400 (EDT) Message-ID: <44B276F7.4070507@mac.com> Date: Mon, 10 Jul 2006 11:49:11 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mike Jakubik References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> In-Reply-To: <44B176D2.3080501@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 15:49:23 -0000 Mike Jakubik wrote: [ ... ] > Why are the limits so low by default? In any case, this is what i found > in LINT. > > options MAXDSIZ=(1024UL*1024*1024) > options MAXSSIZ=(128UL*1024*1024) > options DFLDSIZ=(1024UL*1024*1024) > > I have no idea what those values mean, what should i set them to to be > safe? A limit 768MB should work for me. 512MB is more than enough for almost all processes to run just fine, and is only really inappropriate for the case where you've got 1-plus GB of physical RAM and want to dedicate the system to a single large task, or perhaps a single-digit number of processes if you've got several GB of physical RAM. -- -Chuck PS: On the other hand, as time passes and 64-bit hardware with 4+ GB of RAM becomes more common, this 512MB limit starts resembling the "640K is more than enough" comment from years past. Core memory used to cost a dollar a bit, rather than a dollar a megabit today, but that was before my time... :-) From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 15:52:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FE7E16A4E0 for ; Mon, 10 Jul 2006 15:52:14 +0000 (UTC) (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 A17FF43D49 for ; Mon, 10 Jul 2006 15:52:09 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp141-127.lns2.adl2.internode.on.net [59.167.141.127]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k6AFpvmD040710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jul 2006 01:22:02 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Dominik Zalewski Date: Tue, 11 Jul 2006 01:21:55 +0930 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> <200607101600.56911.dzalewski@open-craft.com> In-Reply-To: <200607101600.56911.dzalewski@open-craft.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3804819.KZSUNaP6QS"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607110121.57051.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, "UEMURA \(fka. MAENAKA\) Tetsuya" Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 15:52:14 -0000 --nextPart3804819.KZSUNaP6QS Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 10 July 2006 22:30, Dominik Zalewski wrote: > Still the same problem. I tried also to change bind_policy to soft. > Can you show me your nss_ldap.conf ? Ah yes, that's the fix.. I have these in nss_ldap.conf timeout 5 bind_timeout 5 bind_policy soft =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 --nextPart3804819.KZSUNaP6QS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEsned5ZPcIHs/zowRAqzoAJ4ynJSvZ9/6Y05Zede+nWlRKm8Z1QCfdCXK q/JWr995FHZ1AZTUVaXeTqQ= =t1nP -----END PGP SIGNATURE----- --nextPart3804819.KZSUNaP6QS-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 15:56:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C5D5F16A4DA for ; Mon, 10 Jul 2006 15:56:44 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id 341FC43D5C for ; Mon, 10 Jul 2006 15:56:40 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.181.175] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1Fzy7i2vWG-0002O2; Mon, 10 Jul 2006 17:56:39 +0200 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Mon, 10 Jul 2006 17:56:31 +0200 User-Agent: KMail/1.9.1 References: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> In-Reply-To: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1810287.HyVczxoQsk"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607101756.37607.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Vlad GALU Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 15:56:44 -0000 --nextPart1810287.HyVczxoQsk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 10 July 2006 16:40, Vlad GALU wrote: > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm > using 1.36 along with a RELENG_6 tree, since it works better (read: it > works). From the HEAD commit messages I understand that some MFCs > would've been in order by now. Are there any show-stoppers that push > that schedule ahead ? no. The only thing that bugs me a bit, is that the change will break POLA = for=20 people using the old version. I have yet to hear from somebody using that= =20 successfully, though. I will get on MFCing it later today. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1810287.HyVczxoQsk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEsni1XyyEoT62BG0RAlfPAJsHilPI56tvaMioe3qAlY9F1u8I7ACfe8XX 8GtPyNMN+wV5b6oA5H8y6gk= =EN/v -----END PGP SIGNATURE----- --nextPart1810287.HyVczxoQsk-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 16:13:09 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 57D0216A4E0 for ; Mon, 10 Jul 2006 16:13:09 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-d5debe68.catv.broadband.hu [213.222.190.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3624C43D6D for ; Mon, 10 Jul 2006 16:13:06 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <44B27CD0.3050701@antiszoc.hu> Date: Mon, 10 Jul 2006 18:14:08 +0200 From: Andras Got User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060404 SeaMonkey/1.0.1 MIME-Version: 1.0 To: stable@freebsd.org References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> <44B276F7.4070507@mac.com> In-Reply-To: <44B276F7.4070507@mac.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Cc: Mike Jakubik Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 16:13:09 -0000 Hi, IMHO on servers 2G is common these these days, and 4G will be common very soon. As people use the websites and the internet more, the needed resources are growing fast. This 512MB will be soon revised imho. :) For example I run a little hosting server for my company and 2 years ago a 2,4Ghz xeon was more than enough. This year I had to replace that machine with an X2100 with 2G RAM because of the customer needs. The number of the pages hadn't grown significally, just the number of served pages and of course the mysql databases. Andras Chuck Swiger wrote: > Mike Jakubik wrote: > [ ... ] >> Why are the limits so low by default? In any case, this is what i >> found in LINT. >> >> options MAXDSIZ=(1024UL*1024*1024) >> options MAXSSIZ=(128UL*1024*1024) >> options DFLDSIZ=(1024UL*1024*1024) >> >> I have no idea what those values mean, what should i set them to to be >> safe? A limit 768MB should work for me. > > 512MB is more than enough for almost all processes to run just fine, and > is only really inappropriate for the case where you've got 1-plus GB of > physical RAM and want to dedicate the system to a single large task, or > perhaps a single-digit number of processes if you've got several GB of > physical RAM. > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 16:14:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D87E16A4DA for ; Mon, 10 Jul 2006 16:14:41 +0000 (UTC) (envelope-from yraffah@savola.com) Received: from heathrow.savoladns.com (heathrow.savoladns.com [212.12.174.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 2A27943D5C for ; Mon, 10 Jul 2006 16:14:32 +0000 (GMT) (envelope-from yraffah@savola.com) Received: from ocs.savola.com (ocs.savola.com [222.22.1.211]) by heathrow.savoladns.com (Postfix) with ESMTP id E0CD195868 for ; Mon, 10 Jul 2006 19:14:29 +0300 (AST) Received: from 212.12.174.2 by ocs.savola.com with ESMTP id 66909301152547380; Mon, 10 Jul 2006 19:03:00 +0300 From: Yousef Raffah To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-bBdgdaT0ZR66eZLaO9ux" Organization: The Savola Group Date: Mon, 10 Jul 2006 19:14:47 +0300 Message-Id: <1152548087.831.7.camel@redevil.savola.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 FreeBSD GNOME Team Port Subject: rdesktop fails on 6.1-RELEASE-p3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: yraffah@savola.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 16:14:41 -0000 --=-bBdgdaT0ZR66eZLaO9ux Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, net/rdesktop is failing no matter what I do, I just portsnapped my ports and here is what I get: =3D=3D=3D> Building for rdesktop-1.4.1 cc -O -pipe -march=3Dpentium3 -Wall -I/usr/local/include -I/usr/X11R6/include -DPACKAGE_NAME=3D\"rdesktop\" -DPACKAGE_TARNAME=3D \"rdesktop\" -DPACKAGE_VERSION=3D\"1.4.1\" -DPACKAGE_STRING=3D\"rdesktop\ 1.4.1\" -DPACKAGE_BUGREPORT=3D\"\" -DSTDC_HEADERS=3D1 -DL_ENDIAN=3D1 -DHAVE_SYS_TYPES_H=3D1 -DHAVE_SYS_STAT_H=3D1 -DHAVE_STDLIB_H=3D1 -DHAVE_STRING_H=3D1 -DHAVE_MEMORY_H=3D1 -DHAVE_STRINGS_H=3D1 -DHAVE_INTTYPES_H=3D1 -DHAVE_STDINT_H=3D1 -DHAVE_UNISTD_H=3D1 -DHAVE_SYS_SELECT_H=3D1 -DHAVE_SYS_FILIO_H=3D1 -DHAVE_LOCALE_H=3D1 -DHAVE_LANGINFO_H=3D1 -Dssldir=3D\"/usr/local\" -DEGD_SOCKET=3D \"/var/run/egd-pool\" -DWITH_RDPSND=3D1 -DHAVE_DIRENT_H=3D1 -DHAVE_DECL_DIRFD=3D1 -DHAVE_ICONV=3D1 -DICONV_CONST=3Dconst -DHAVE_SYS_STATVFS_H=3D1 -DHAVE_SYS_PARAM_H=3D1 -DHAVE_SYS_MOUNT_H=3D1 -DSTAT_STATVFS=3D1 -DHAVE_STRUCT_STATVFS_F_NAMEMAX=3D1 -DKEYMAP_PATH=3D \"/usr/local/share/rdesktop/keymaps/\" -o rdp.o -c rdp.c rdp.c: In function `rdp_out_unistr': rdp.c:164: error: syntax error before "iconv_h" rdp.c:171: error: `iconv_h' undeclared (first use in this function) rdp.c:171: error: (Each undeclared identifier is reported only once rdp.c:171: error: for each function it appears in.) rdp.c:171: error: `iconv_t' undeclared (first use in this function) rdp.c:174: warning: implicit declaration of function `iconv_open' rdp.c:183: warning: implicit declaration of function `iconv' rdp.c:186: warning: implicit declaration of function `iconv_close' rdp.c: In function `rdp_in_unistr': rdp.c:239: error: syntax error before "iconv_h" rdp.c:243: error: `iconv_h' undeclared (first use in this function) rdp.c:243: error: `iconv_t' undeclared (first use in this function) gmake: *** [rdp.o] Error 1 *** Error code 2 I guess you need: uname -a FreeBSD redevil 6.1-RELEASE-p3 FreeBSD 6.1-RELEASE-p3 #1: Mon Jul 10 17:55:45 AST 2006 root@redevil:/usr/obj/usr/src/sys/LAPTOP i386 pkg_info -x gettext Information for gettext-0.14.5_2: Comment: GNU gettext package Required by: ORBit-0.5.17_3 ORBit2-2.14.0_1 acroread7-7.0.1_2,1 akode-plugins-mpc-2.0,1 anjuta-1.2.4_5 arts-1.5.3_1,1 aspell-0.60.4_3 at-spi-1.7.7_1 atk-1.11.4_1 avahi-0.6.10_3 bash-3.1.17 bison-1.75_2,1 bonobo-1.0.22_2 bugbuddy-2.14.0 cdparanoia-3.9.8_8 cdrtools-2.01_5 coreutils-5.2.1 cssed-0.4.0 cups-1.2.0 cups-base-1.2.0_2 cups-pstoraster-8.15 dbus-0.62 desktop-file-utils-0.11 dirmngr-0.9.3_2 dvd+rw-tools-6.1 dvdrip-0.52.7 e17-theme-blokkie-0.1 e17-theme-cthulhain-0.2.1 e17-theme-detour-0.4 e17-theme-japan2007-0.9.5 eel-2.14.1 ekiga-2.0.1_2 en-openoffice.org-US-2.0.2 enchant-1.2.5 enlightenment-0.16.999.027 eog-2.14.2 ettercap-gtk2-0.7.3_3,1 evolution-2.6.2_1 evolution-data-server-1.6.2 file-roller-2.14.3,1 firefox-1.5.0.4,1 firefox-2.0.a3_1,1 fontforge-20060413 gail-1.8.11_1 gaim-1.5.0_5 gal-0.24_2 gamin-0.1.7_2 gcalctool-5.7.32,2 gconf-1.0.9_8 gconf2-2.14.0_2 gdbm-1.8.3_2 gdk-pixbuf-0.22.0_4 gdm-2.14.8 gedit-2.14.3 gftp-2.0.18_2 gimp-2.2.11,1 glib-2.10.3 glibmm-2.10.4 glibwww-0.2_3 gmake-3.81_1 gnet2-2.0.7_2 gnome-cups-manager-0.31_3,1 gnome-desktop-2.14.2_1 gnome-doc-utils-0.6.1 gnome-icon-theme-2.14.2 gnome-keyring-0.4.9 gnome-libs-1.4.2_5 gnome-menus-2.14.0 gnome-mime-data-2.4.2 gnome-print-0.37_2 gnome-spell-1.0.7_1 gnome-vfs-2.14.2_3 gnupg-1.4.3 gnupg-devel-1.9.20_1 gnutls-1.4.0 gpgme-1.0.3_1 gqview-2.0.1_1 gstreamer-0.10.8 gstreamer-ffmpeg-0.10.1 gstreamer-plugins-0.10.8,1 gstreamer-plugins-a52dec-0.10.3_1,1 gstreamer-plugins-cdparanoia-0.10.8_2,1 gstreamer-plugins-core-0.10_6 gstreamer-plugins-dts-0.10.3_1,1 gstreamer-plugins-dts80-0.8.12_1 gstreamer-plugins-dvd-0.10.3,1 gstreamer-plugins-dvd80-0.8.12_2 gstreamer-plugins-esound-0.10.3_1,1 gstreamer-plugins-flac-0.10.3_1,1 gstreamer-plugins-gconf-0.10.3_3,1 gstreamer-plugins-gnomevfs-0.10.8_1,1 gstreamer-plugins-good-0.10.3_4,1 gstreamer-plugins-jpeg-0.10.3_1,1 gstreamer-plugins-libpng-0.10.3_1,1 gstreamer-plugins-mad-0.10.3_2,1 gstreamer-plugins-ogg-0.10.8_1,1 gstreamer-plugins-pango-0.10.8_1,1 gstreamer-plugins-theora-0.10.8_2,1 gstreamer-plugins-vorbis-0.10.8_1,1 gstreamer-plugins-xvid-0.10.3,1 gstreamer-plugins-xvid80-0.8.12_1 gstreamer-plugins80-0.8.12_2 gstreamer80-0.8.12_1 gtar-1.15.1_2 gthumb-2.6.9_1 gtk-1.2.10_15 gtk-2.8.19 gtk-engines2-2.6.9 gtk-gnutella-0.96.1 gtk-sharp-1.0.10_8 gtkglext-1.2.0 gtkhtml-1.1.10_5 gtkhtml3-3.10.2 gtkmm-2.2.12_6 gtkmm-2.8.8 gtksourceview-1.6.1_1 gtkspell2-2.0.11_3 help2man-1.36.4_1 hydra-5.2 imlib-1.9.15_3 inkscape-0.44 inti-1.2_6 irssi-0.8.10_2 iso-codes-0.51.1.1 k3b-0.12.16 kdeaddons-konq-plugins-3.5.3 kdebase-3.5.3_4 kdebase-kompmgr-3.5.3 kdelibs-3.5.3 kdemultimedia-3.5.3 kdemultimedia-mpeglib_artsplug-3.5.3 kdenetwork-3.5.3_2 kdepim-3.5.3 libIDL-0.8.6_2 liba52-0.7.4_1 libbonobo-2.14.0_2 libbonoboui-2.14.0_1 libcapplet-1.4.0.5_3 libcdio-0.77 libcroco-0.6.1 libdnet-1.10_1 libdv-0.104_1 libdvdcss-1.2.9_2 libexif-0.6.13 libgcrypt-1.2.2_1 libgda-0.2.96_4 libglade-0.17_4 libglade2-2.5.1_5 libgnome-2.14.1_1 libgnomecanvas-2.14.0_1 libgnomecups-0.2.2_1,1 libgnomeprint-2.12.1_2 libgnomeprintui-2.12.1_1 libgnomesu-1.0.0_2 libgnomeui-2.14.1_1 libgpg-error-1.3 libgphoto2-2.2.1_1 libgsf-1.14.1 libgtkhtml-2.11.0_1 libgtop-2.14.1_1 libidn-0.6.3 libksba-0.9.13_1 libnotify-0.4.0 liboil-0.3.9_1 librsvg2-2.14.4 libsoup-2.2.94_1 libvisual-plugins-0.2.0_2 libwnck-2.14.2_1 libwww-5.4.0_2 linc-1.0.3_6 linux-winetools-1.25a_2 linuxpluginwrapper-20051113_4 metacity-2.14.5 minicom-2.1 mono-1.1.13.6_1 monodoc-1.1.13 mozilla-1.7.13,2 mplayer-gtk-esound-0.99.7_15 mplayerplug-in-3.25 nano-1.2.5 nspr-4.6.1 nss-3.11.1 oaf-0.6.10_3 opal-2.2.1_1 orbitcpp-1.3.9_3 p5-GdkPixbuf-0.7009_3 p5-Gtk-0.7009_2 p5-Locale-libintl-1.16 p5-Mail-SpamAssassin-3.1.3 p5-gettext-1.05_1 pango-1.12.3 pkg-config-0.20_2 poppler-gtk-0.5.3 popt-1.7_1 pwlib-1.10.0_1,1 py24-gobject-2.10.1 py24-gtk-2.8.6 py24-orbit-2.14.1 rpm-3.0.6_13 samba-3.0.22,1 scrollkeeper-0.3.14_4,1 sdl-1.2.9_2,2 sdl_mixer-1.2.6_2 shared-mime-info-0.17_1 smpeg-0.4.4_5 soup-0.7.11_2 subtitleripper-0.3.4_1 svgalib-1.4.3_5 swt-3.1.1 system-tools-backends-1.4.2 taskjuggler-2.2.0 totem-gstreamer-1.4.0 transcode-1.0.2_3 vcdimager-0.7.23_3 vorbis-tools-1.1.1,3 vte-0.12.2 wget-1.10.2 wine-0.9.16,1 xmms-esound-1.2.10_6 xvid4conf-1.12 yelp-2.14.2 zenity-2.14.2 vpnc-0.3.3_2 gnome-menu-editor-0.6 gnome-panel-2.14.2_2 Description: This is the GNU gettext package. It is interesting for authors or maintainers of other packages or programs which they want to see internationalized. As one step the handling of messages in different languages should be implemented. For this task GNU gettext provides the needed tools and library functions. WWW: http://www.gnu.org/software/gettext/ Information for p5-gettext-1.05_1: Comment: Message handling functions Required by: help2man-1.36.4_1 Description: This module permits from perl to the gettext() family of functions for retreiving message strings from databases constructed to internationalize software. --Dima. dima@Chg.RU pkg_info -x libiconv Information for libiconv-1.9.2_2: Comment: A character set conversion library Required by: ImageMagick-6.2.7.7_1 ORBit-0.5.17_3 ORBit2-2.14.0_1 acroread7-7.0.1_2,1 akode-2.0,1 akode-plugins-resampler-2.0,1 akode-plugins-xiph-2.0,1 anjuta-1.2.4_5 arts-1.5.3_1,1 aspell-0.60.4_3 at-spi-1.7.7_1 atk-1.11.4_1 avahi-0.6.10_3 bash-3.1.17 bison-1.75_2,1 bonobo-1.0.22_2 bugbuddy-2.14.0 cdrtools-2.01_5 coreutils-5.2.1 cssed-0.4.0 cups-1.2.0 cups-base-1.2.0_2 cups-pstoraster-8.15 dbus-0.62 dirmngr-0.9.3_2 dvd+rw-tools-6.1 dvdrip-0.52.7 e17-theme-blokkie-0.1 e17-theme-cthulhain-0.2.1 e17-theme-detour-0.4 e17-theme-japan2007-0.9.5 ecore-0.9.9.027 edje-0.5.0.027 eel-2.14.1 ekiga-2.0.1_2 en-openoffice.org-US-2.0.2 enchant-1.2.5 enlightenment-0.16.999.027 eog-2.14.2 ettercap-gtk2-0.7.3_3,1 evolution-2.6.2_1 evolution-data-server-1.6.2 file-roller-2.14.3,1 firefox-1.5.0.4,1 firefox-2.0.a3_1,1 flac-1.1.2_1 fontforge-20060413 gail-1.8.11_1 gaim-1.5.0_5 gal-0.24_2 gcalctool-5.7.32,2 gconf-1.0.9_8 gconf2-2.14.0_2 gdk-pixbuf-0.22.0_4 gdm-2.14.8 gedit-2.14.3 gettext-0.14.5_2 gftp-2.0.18_2 gimp-2.2.11,1 glib-2.10.3 glibmm-2.10.4 glibwww-0.2_3 gmake-3.81_1 gnet2-2.0.7_2 gnome-cups-manager-0.31_3,1 gnome-desktop-2.14.2_1 gnome-doc-utils-0.6.1 gnome-icon-theme-2.14.2 gnome-keyring-0.4.9 gnome-libs-1.4.2_5 gnome-menus-2.14.0 gnome-mime-data-2.4.2 gnome-print-0.37_2 gnome-spell-1.0.7_1 gnome-vfs-2.14.2_3 gnupg-1.4.3 gnupg-devel-1.9.20_1 gnutls-1.4.0 gpgme-1.0.3_1 gqview-2.0.1_1 gstreamer-0.10.8 gstreamer-ffmpeg-0.10.1 gstreamer-plugins-0.10.8,1 gstreamer-plugins-a52dec-0.10.3_1,1 gstreamer-plugins-cdparanoia-0.10.8_2,1 gstreamer-plugins-core-0.10_6 gstreamer-plugins-dts-0.10.3_1,1 gstreamer-plugins-dts80-0.8.12_1 gstreamer-plugins-dvd-0.10.3,1 gstreamer-plugins-dvd80-0.8.12_2 gstreamer-plugins-esound-0.10.3_1,1 gstreamer-plugins-flac-0.10.3_1,1 gstreamer-plugins-gconf-0.10.3_3,1 gstreamer-plugins-gnomevfs-0.10.8_1,1 gstreamer-plugins-good-0.10.3_4,1 gstreamer-plugins-jpeg-0.10.3_1,1 gstreamer-plugins-libpng-0.10.3_1,1 gstreamer-plugins-mad-0.10.3_2,1 gstreamer-plugins-ogg-0.10.8_1,1 gstreamer-plugins-pango-0.10.8_1,1 gstreamer-plugins-theora-0.10.8_2,1 gstreamer-plugins-vorbis-0.10.8_1,1 gstreamer-plugins-xvid-0.10.3,1 gstreamer-plugins-xvid80-0.8.12_1 gstreamer-plugins80-0.8.12_2 gstreamer80-0.8.12_1 gtar-1.15.1_2 gthumb-2.6.9_1 gtk-1.2.10_15 gtk-2.8.19 gtk-engines2-2.6.9 gtk-gnutella-0.96.1 gtk-sharp-1.0.10_8 gtkglext-1.2.0 gtkhtml-1.1.10_5 gtkhtml3-3.10.2 gtkmm-2.2.12_6 gtkmm-2.8.8 gtksourceview-1.6.1_1 gtkspell2-2.0.11_3 help2man-1.36.4_1 hydra-5.2 imlib-1.9.15_3 inkscape-0.44 inti-1.2_6 intltool-0.35.0 irssi-0.8.10_2 iso-codes-0.51.1.1 jackit-0.101.1_1 k3b-0.12.16 kdeaddons-konq-plugins-3.5.3 kdebase-3.5.3_4 kdebase-kompmgr-3.5.3 kdelibs-3.5.3 kdemultimedia-3.5.3 kdemultimedia-mpeglib_artsplug-3.5.3 kdenetwork-3.5.3_2 kdepim-3.5.3 libIDL-0.8.6_2 libbonobo-2.14.0_2 libbonoboui-2.14.0_1 libcapplet-1.4.0.5_3 libcdio-0.77 libcroco-0.6.1 libdv-0.104_1 libexif-0.6.13 libgcrypt-1.2.2_1 libgda-0.2.96_4 libglade-0.17_4 libglade2-2.5.1_5 libgnome-2.14.1_1 libgnomecanvas-2.14.0_1 libgnomecups-0.2.2_1,1 libgnomeprint-2.12.1_2 libgnomeprintui-2.12.1_1 libgnomesu-1.0.0_2 libgnomeui-2.14.1_1 libgpg-error-1.3 libgphoto2-2.2.1_1 libgsf-1.14.1 libgtkhtml-2.11.0_1 libgtop-2.14.1_1 libidn-0.6.3 libksba-0.9.13_1 libmal-0.40 libnotify-0.4.0 liboil-0.3.9_1 librsvg2-2.14.4 libsamplerate-0.1.2_2 libsndfile-1.0.16 libsoup-2.2.94_1 libsvg-0.1.4 libsvg-cairo-0.1.6_2 libtunepimp-0.4.2_2,1 libvisual-plugins-0.2.0_2 libwmf-0.2.8.4 libwnck-2.14.2_1 libxklavier-2.2_1,1 libxml2-2.6.26 libxslt-1.1.17 linux-winetools-1.25a_2 linuxpluginwrapper-20051113_4 metacity-2.14.5 minicom-2.1 mono-1.1.13.6_1 monodoc-1.1.13 mozilla-1.7.13,2 mplayer-gtk-esound-0.99.7_15 mplayerplug-in-3.25 nano-1.2.5 oaf-0.6.10_3 opal-2.2.1_1 orbitcpp-1.3.9_3 p5-GdkPixbuf-0.7009_3 p5-Gtk-0.7009_2 p5-Locale-libintl-1.16 p5-Mail-SpamAssassin-3.1.3 p5-gettext-1.05_1 pango-1.12.3 pilot-link-0.11.8_4,1 poppler-gtk-0.5.3 popt-1.7_1 pure-ftpd-1.0.21_1 pwlib-1.10.0_1,1 py24-cairo-1.0.2_1 py24-gobject-2.10.1 py24-gtk-2.8.6 py24-libxml2-2.6.26 py24-orbit-2.14.1 rpm-3.0.6_13 samba-3.0.22,1 samba-libsmbclient-3.0.22 scrollkeeper-0.3.14_4,1 sdl-1.2.9_2,2 sdl_mixer-1.2.6_2 shared-mime-info-0.17_1 smpeg-0.4.4_5 soup-0.7.11_2 subtitleripper-0.3.4_1 swt-3.1.1 system-tools-backends-1.4.2 taskjuggler-2.2.0 totem-gstreamer-1.4.0 transcode-1.0.2_3 vcdimager-0.7.23_3 vorbis-tools-1.1.1,3 vte-0.12.2 wget-1.10.2 wine-0.9.16,1 xmms-esound-1.2.10_6 xvid4conf-1.12 yelp-2.14.2 zenity-2.14.2 vpnc-0.3.3_2 gnome-menu-editor-0.6 gnome-panel-2.14.2_2 Description: This library provides an iconv() implementation, for use on systems which don't have one, or whose implementation cannot convert from/to Unicode. It can convert from any of these encodings to any other, through Unicode conversion. It has also some limited support for transliteration, i.e. when a character cannot be represented in the target character set, it can be approximated through one or several similarly looking characters. libiconv is for you if your application needs to support multiple character encodings, but that support lacks from your system. See in either README or website for the list of support encodings. WWW: http://www.gnu.org/software/libiconv/ ls -la /usr/local/include/iconv.h -r--r--r-- 1 root wheel 4760 Jul 9 14:32 /usr/local/include/iconv.h nm /usr/local/lib/libiconv.a | grep iconv_open 00012670 T iconv_open 00012670 T libiconv_open cat /etc/make.conf CPUTYPE=3Dpentium3 CFLAGS=3D -O -pipe CXXFLAGS+=3D -fconserve-space NO_PROFILE=3Dtrue NO_I4B=3Dtrue NO_INET6=3Dtrue NO_RCMDS=3Dtrue NO_SHAREDOCS=3Dtrue NO_ACPI=3Dtrue ENABLE_WPA_SUPPLICANT_EAPOL=3Dtrue # added by use.perl 2006-07-09 13:53:19 PERL_VER=3D5.8.8 PERL_VERSION=3D5.8.8 -- Sincerely, Yousef Raffah Senior Systems Administrator -- Aren't you using Firefox? Get it at http://www.getfirefox.com --=-bBdgdaT0ZR66eZLaO9ux Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEsnz3H9IXMb4e6CMRAk6fAJ9GkLEeGkWHgXmQdJRfKSdhyb3HGgCff3do T8gJEAnm6v68NwdExdMgDUA= =VPOo -----END PGP SIGNATURE----- --=-bBdgdaT0ZR66eZLaO9ux-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 17:16:36 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB18616A4DD for ; Mon, 10 Jul 2006 17:16:36 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 365A543D70 for ; Mon, 10 Jul 2006 17:16:36 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id C97E1114AA; Mon, 10 Jul 2006 13:17:00 -0400 (EDT) Message-ID: <44B28B7F.1000507@rogers.com> Date: Mon, 10 Jul 2006 13:16:47 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Chuck Swiger References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> <44B276F7.4070507@mac.com> In-Reply-To: <44B276F7.4070507@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 17:16:36 -0000 Chuck Swiger wrote: > 512MB is more than enough for almost all processes to run just fine, > and is only really inappropriate for the case where you've got 1-plus > GB of physical RAM and want to dedicate the system to a single large > task, or perhaps a single-digit number of processes if you've got > several GB of physical RAM. > Such as a database server. I just think it would be nicer if this limit was dynamically set, based on your configuration. Just like MAXUSERS was a kernel variable, it is now dynamically set based on your resources. From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 18:05:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CB1DB16A4DD for ; Mon, 10 Jul 2006 18:05:00 +0000 (UTC) (envelope-from vladgalu@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2147043D45 for ; Mon, 10 Jul 2006 18:04:59 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by nf-out-0910.google.com with SMTP id x37so543941nfc for ; Mon, 10 Jul 2006 11:04:59 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MROd31VhH7Pd9SoQkAXWWOjAOpNu4EcFsl0duW5hHqJhOS3eqKUwLVmR1jxKpBjjIBzL1H2xLjgUAxegmAmtkqG1PpHLv1/1dfb7LU3TU8oRoysLSAMs+bzZ1gHAdtIurMv83y0pCCvb/0a0MdACot2RFoNv6dGi1IXi+ms3ucs= Received: by 10.49.7.3 with SMTP id k3mr63154nfi; Mon, 10 Jul 2006 11:03:17 -0700 (PDT) Received: by 10.48.250.2 with HTTP; Mon, 10 Jul 2006 11:03:17 -0700 (PDT) Message-ID: <79722fad0607101103nd5955e7wc61b5288d79941db@mail.gmail.com> Date: Mon, 10 Jul 2006 21:03:17 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org In-Reply-To: <200607101756.37607.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> <200607101756.37607.max@love2party.net> Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 18:05:00 -0000 On 7/10/06, Max Laier wrote: > On Monday 10 July 2006 16:40, Vlad GALU wrote: > > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm > > using 1.36 along with a RELENG_6 tree, since it works better (read: it > > works). From the HEAD commit messages I understand that some MFCs > > would've been in order by now. Are there any show-stoppers that push > > that schedule ahead ? > > no. The only thing that bugs me a bit, is that the change will break POLA for > people using the old version. I have yet to hear from somebody using that > successfully, though. > > I will get on MFCing it later today. > Thanks, Max! > -- > /"\ Best regards, | mlaier@freebsd.org > \ / Max Laier | ICQ #67774661 > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > -- 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-stable@FreeBSD.ORG Mon Jul 10 18:06:33 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BFD9D16A4DD for ; Mon, 10 Jul 2006 18:06:33 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8928043D5C for ; Mon, 10 Jul 2006 18:06:16 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 865676075; Mon, 10 Jul 2006 14:06:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at codefab.com Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jdEVdCtXYVEk; Mon, 10 Jul 2006 14:06:14 -0400 (EDT) Received: from [192.168.1.251] (pool-68-161-117-245.ny325.east.verizon.net [68.161.117.245]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 13F7C5C14; Mon, 10 Jul 2006 14:06:13 -0400 (EDT) Message-ID: <44B2970E.7000501@mac.com> Date: Mon, 10 Jul 2006 14:06:06 -0400 From: Chuck Swiger User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mike Jakubik References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> <44B276F7.4070507@mac.com> <44B28B7F.1000507@rogers.com> In-Reply-To: <44B28B7F.1000507@rogers.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 18:06:33 -0000 Mike Jakubik wrote: > Chuck Swiger wrote: >> 512MB is more than enough for almost all processes to run just fine, >> and is only really inappropriate for the case where you've got 1-plus >> GB of physical RAM and want to dedicate the system to a single large >> task, or perhaps a single-digit number of processes if you've got >> several GB of physical RAM. > > Such as a database server. Yes, exactly. :-) Database servers are a rather specialized role which differs in tuning requirements from normal "general purpose"/"interactive use" workloads substantially, and it is common for databases to work much better after the system has been tuned appropriately. This is partially because many databases want to do their own filesystem management and control their own VM/paging behavior, which are uncommon requirements. > I just think it would be nicer if this limit > was dynamically set, based on your configuration. Just like MAXUSERS was > a kernel variable, it is now dynamically set based on your resources. Yes, well, autotuning is nice but sometimes there isn't an "obviously correct value" for this limit which is appropriate for all circumstances. Anyone doing virtual hosting needs to keep this kind of thing under tighter control, for example. Setting the value lower is beneficial for some cases because it prevents memory leaks in C code or the system libraries, or bloated Java VM's, etc, from stealing too many resources from other processes. -- -Chuck From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 18:16:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 846E416A4DA for ; Mon, 10 Jul 2006 18:16:43 +0000 (UTC) (envelope-from mihir.sanghavi@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9B7A43D45 for ; Mon, 10 Jul 2006 18:16:42 +0000 (GMT) (envelope-from mihir.sanghavi@gmail.com) Received: by nf-out-0910.google.com with SMTP id x29so595638nfb for ; Mon, 10 Jul 2006 11:16:41 -0700 (PDT) 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=STnarAx+MMiB6USODh4ybXhJM6u87M1ginAJ+ZLiSWHFqFZj/xBkR4qPAompuzqWpwoe7wkwyTfMQgLzJxuV1WZRohUvgUuu/i5mr2n2zNJHOW5n3x70PraHCSLGdaHbmPEKKGm6m68ia3Nwn6UjtLeYZs4I2sgu/8t+6pAm58Q= Received: by 10.78.136.7 with SMTP id j7mr1809563hud; Mon, 10 Jul 2006 11:16:41 -0700 (PDT) Received: by 10.78.184.14 with HTTP; Mon, 10 Jul 2006 11:16:40 -0700 (PDT) Message-ID: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> Date: Mon, 10 Jul 2006 11:16:41 -0700 From: "Mihir Sanghavi" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Writing application X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 18:16:43 -0000 Hi, I have installed freeBSD 5.5 and am connected to the net now. I would like to install apache and devlop some application from there. How should i start writing my application, execute it. I even make to figure out what folder to write application and how to deal with it. Thank you -- What we see depends mainly on what we look for. -MIHIR From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 18:21:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2681D16A4DA for ; Mon, 10 Jul 2006 18:21:09 +0000 (UTC) (envelope-from mike@jellydonut.org) Received: from mail.secureworks.net (mail.secureworks.net [65.114.32.155]) by mx1.FreeBSD.org (Postfix) with SMTP id C2B7743D78 for ; Mon, 10 Jul 2006 18:21:04 +0000 (GMT) (envelope-from mike@jellydonut.org) Received: (qmail 82684 invoked from network); 10 Jul 2006 18:21:04 -0000 Received: from unknown (HELO ?192.168.14.135?) (63.239.86.253) by 0 with SMTP; 10 Jul 2006 18:21:04 -0000 Message-ID: <44B29A90.7050405@jellydonut.org> Date: Mon, 10 Jul 2006 14:21:04 -0400 From: Michael Proto User-Agent: Thunderbird 1.5.0.4 (X11/20060627) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> In-Reply-To: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: Writing application X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 18:21:09 -0000 Mihir Sanghavi wrote: > Hi, > I have installed freeBSD 5.5 and am connected to the net now. I would like > to install apache and devlop some application from there. How should i > start > writing my application, execute it. I even make to figure out what > folder to > write application and how to deal with it. Thank you > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ Provides a good start -Proto From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 18:25:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D114E16A4E5 for ; Mon, 10 Jul 2006 18:25:00 +0000 (UTC) (envelope-from greenwood.andy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4924343D77 for ; Mon, 10 Jul 2006 18:24:55 +0000 (GMT) (envelope-from greenwood.andy@gmail.com) Received: by nf-out-0910.google.com with SMTP id c2so765726nfe for ; Mon, 10 Jul 2006 11:24:54 -0700 (PDT) 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=mU057sGfuhAj38P20uYzFLXvYxnwzJj6Gh+GfdR95iv5pCGzbh6WxuWUGONLfdP9rxIipHjH3Rl7mF9nqaLWYTzzwCS9Imy5oxOMmHrvQR7Htyhah8EDQLv7v5NwKfKdXZKPeDNIy0h8TQHZRMd4EwpFEQoMGRMFl9K69jVq/5k= Received: by 10.78.156.6 with SMTP id d6mr1822199hue; Mon, 10 Jul 2006 11:24:53 -0700 (PDT) Received: by 10.78.200.16 with HTTP; Mon, 10 Jul 2006 11:24:53 -0700 (PDT) Message-ID: <3ee9ca710607101124x3d4b060x1e41bdd00c3694a0@mail.gmail.com> Date: Mon, 10 Jul 2006 14:24:53 -0400 From: "Andy Greenwood" To: "Mihir Sanghavi" In-Reply-To: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> Cc: freebsd-stable@freebsd.org Subject: Re: Writing application X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 18:25:00 -0000 cd /usr/ports/www/apache13 && make install clean should install apache and all it's dependancies for you. As for writing your applications, I can't even begin to help without more info. Perhaps you should search for information on your programming language of choice. You can write your application in any folder you want, but a likely place might be either your home directory or a subdirectory of your apache's document root (depending on the application's...uh...application) which defaults to /usr/local/www/data-dist/ On 7/10/06, Mihir Sanghavi wrote: > Hi, > I have installed freeBSD 5.5 and am connected to the net now. I would like > to install apache and devlop some application from there. How should i start > writing my application, execute it. I even make to figure out what folder to > write application and how to deal with it. Thank you > > -- > What we see depends mainly on what we look for. > -MIHIR > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 20:40:53 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B36C916A4E6; Mon, 10 Jul 2006 20:40:53 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E994743D46; Mon, 10 Jul 2006 20:40:52 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6AKemVp084464 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 13:40:49 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B2BCDB.7050403@asd.aplus.net> Date: Mon, 10 Jul 2006 13:47:23 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: pyunyh@gmail.com References: <44AC6793.2070608@asd.aplus.net> <20060706021444.GA76865@cdnetworks.co.kr> <44AD7297.7080605@asd.aplus.net> <20060707010341.GD82406@cdnetworks.co.kr> <44ADC2ED.4070904@asd.aplus.net> <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> In-Reply-To: <20060708033254.GB87930@cdnetworks.co.kr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: Peter Jeremy , Robert Watson , Michael Vince , freebsd-stable@freebsd.org, User Freebsd Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 20:40:53 -0000 Pyun YongHyeon said the following on 7/7/06 8:32 PM: > On Fri, Jul 07, 2006 at 10:38:01PM +0100, Robert Watson wrote: > > > > Yes -- basically, there are two problems: > > > > (1) A little problem, in which an arp announcement is sent before the link > > has > > settled after reset. > > > > (2) A big problem, in which the interface is gratuitously recent requiring > > long settling times. > > > > I'd really like to see a fix to the second of these problems (not resetting > > when an IP is added or removed, resulting in link renegotiation); the first > > one I'm less concerned about, although it would make some amount of sense > > to do an arp announcement when the link goes up. > > > > Ah, I see. Thanks for the insight. > How about the attached patch? > This patch seems to fix both of the issues, or at least this is what I see now: - the card no longer gets reset when adding an alias; - the arp packet gets delivered; - adding 250 aliases takes less than a second; I haven't fully tested whether all 250 IP aliases were accessible (I used non-routable IP addresses), but I suppose so. Also I couldn't stress the patched driver enough to see whether it performs as expected. But in overall it looks good. I guess some more testing might be needed in order to merge the patch into the source tree. Regards, Atanas > > > ------------------------------------------------------------------------ > > Index: if_em.c > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.c,v > retrieving revision 1.116 > diff -u -r1.116 if_em.c > --- if_em.c 6 Jun 2006 08:03:49 -0000 1.116 > +++ if_em.c 8 Jul 2006 03:30:36 -0000 > @@ -67,6 +67,7 @@ > > #include > #include > +#include > #include > #include > #include > @@ -692,6 +693,9 @@ > > EM_LOCK_ASSERT(sc); > > + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != > + IFF_DRV_RUNNING) > + return; > if (!sc->link_active) > return; > > @@ -745,6 +749,7 @@ > { > struct em_softc *sc = ifp->if_softc; > struct ifreq *ifr = (struct ifreq *)data; > + struct ifaddr *ifa = (struct ifaddr *)data; > int error = 0; > > if (sc->in_detach) > @@ -752,9 +757,22 @@ > > switch (command) { > case SIOCSIFADDR: > - case SIOCGIFADDR: > - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); > - ether_ioctl(ifp, command, data); > + if (ifa->ifa_addr->sa_family == AF_INET) { > + /* > + * XXX > + * Since resetting hardware takes a very long time > + * we only initialize the hardware only when it is > + * absolutely required. > + */ > + ifp->if_flags |= IFF_UP; > + if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + EM_LOCK(sc); > + em_init_locked(sc); > + EM_UNLOCK(sc); > + } > + arp_ifinit(ifp, ifa); > + } else > + error = ether_ioctl(ifp, command, data); > break; > case SIOCSIFMTU: > { > @@ -802,17 +820,19 @@ > IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); > EM_LOCK(sc); > if (ifp->if_flags & IFF_UP) { > - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_flags ^ sc->if_flags) & > + IFF_PROMISC) { > + em_disable_promisc(sc); > + em_set_promisc(sc); > + } > + } else > em_init_locked(sc); > - } > - > - em_disable_promisc(sc); > - em_set_promisc(sc); > } else { > - if (ifp->if_drv_flags & IFF_DRV_RUNNING) { > + if (ifp->if_drv_flags & IFF_DRV_RUNNING) > em_stop(sc); > - } > } > + sc->if_flags = ifp->if_flags; > EM_UNLOCK(sc); > break; > case SIOCADDMULTI: > @@ -878,8 +898,8 @@ > break; > } > default: > - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); > - error = EINVAL; > + error = ether_ioctl(ifp, command, data); > + break; > } > > return (error); > Index: if_em.h > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.h,v > retrieving revision 1.44 > diff -u -r1.44 if_em.h > --- if_em.h 15 Feb 2006 08:39:50 -0000 1.44 > +++ if_em.h 8 Jul 2006 03:30:43 -0000 > @@ -259,6 +259,7 @@ > struct callout timer; > struct callout tx_fifo_timer; > int io_rid; > + int if_flags; > struct mtx mtx; > int em_insert_vlan_header; > struct task link_task; > > > ------------------------------------------------------------------------ > > Index: if_em.c > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.c,v > retrieving revision 1.65.2.16 > diff -u -r1.65.2.16 if_em.c > --- if_em.c 19 May 2006 00:19:57 -0000 1.65.2.16 > +++ if_em.c 8 Jul 2006 03:29:16 -0000 > @@ -657,8 +657,9 @@ > > mtx_assert(&adapter->mtx, MA_OWNED); > > - if (!adapter->link_active) > - return; > + if ((ifp->if_drv_flags & (IFF_DRV_RUNNING|IFF_DRV_OACTIVE)) != > + IFF_DRV_RUNNING) > + return; > > while (!IFQ_DRV_IS_EMPTY(&ifp->if_snd)) { > > @@ -714,15 +715,29 @@ > { > struct ifreq *ifr = (struct ifreq *) data; > struct adapter * adapter = ifp->if_softc; > + struct ifaddr *ifa = (struct ifaddr *)data; > int error = 0; > > if (adapter->in_detach) return(error); > > switch (command) { > case SIOCSIFADDR: > - case SIOCGIFADDR: > - IOCTL_DEBUGOUT("ioctl rcv'd: SIOCxIFADDR (Get/Set Interface Addr)"); > - ether_ioctl(ifp, command, data); > + if (ifa->ifa_addr->sa_family == AF_INET) { > + /* > + * XXX > + * Since resetting hardware takes a very long time > + * we only initialize the hardware only when it is > + * absolutely required. > + */ > + ifp->if_flags |= IFF_UP; > + if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + EM_LOCK(adapter); > + em_init_locked(adapter); > + EM_UNLOCK(adapter); > + } > + arp_ifinit(ifp, ifa); > + } else > + error = ether_ioctl(ifp, command, data); > break; > case SIOCSIFMTU: > { > @@ -760,12 +775,14 @@ > IOCTL_DEBUGOUT("ioctl rcv'd: SIOCSIFFLAGS (Set Interface Flags)"); > EM_LOCK(adapter); > if (ifp->if_flags & IFF_UP) { > - if (!(ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_drv_flags & IFF_DRV_RUNNING)) { > + if ((ifp->if_flags ^ adapter->if_flags) & > + IFF_PROMISC) { > + em_disable_promisc(adapter); > + em_set_promisc(adapter); > + } > + } else > em_init_locked(adapter); > - } > - > - em_disable_promisc(adapter); > - em_set_promisc(adapter); > } else { > if (ifp->if_drv_flags & IFF_DRV_RUNNING) { > em_stop(adapter); > @@ -835,8 +852,8 @@ > break; > } > default: > - IOCTL_DEBUGOUT1("ioctl received: UNKNOWN (0x%x)", (int)command); > - error = EINVAL; > + error = ether_ioctl(ifp, command, data); > + break; > } > > return(error); > Index: if_em.h > =================================================================== > RCS file: /pool/ncvs/src/sys/dev/em/if_em.h,v > retrieving revision 1.32.2.2 > diff -u -r1.32.2.2 if_em.h > --- if_em.h 25 Nov 2005 14:11:59 -0000 1.32.2.2 > +++ if_em.h 8 Jul 2006 03:29:25 -0000 > @@ -65,6 +65,7 @@ > > #include > #include > +#include > #include > #include > #include > @@ -331,6 +332,7 @@ > struct callout timer; > struct callout tx_fifo_timer; > int io_rid; > + int if_flags; > u_int8_t unit; > struct mtx mtx; > int em_insert_vlan_header; > > > ------------------------------------------------------------------------ > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 20:55:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A14BA16A4E0; Mon, 10 Jul 2006 20:55:24 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 631B643D49; Mon, 10 Jul 2006 20:55:23 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id A1C88290C20; Mon, 10 Jul 2006 17:55:19 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 16014-08; Mon, 10 Jul 2006 20:55:22 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 9E4FE290C1E; Mon, 10 Jul 2006 17:55:18 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 2ED4B4A1D1; Mon, 10 Jul 2006 17:55:23 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 2DC5C49AB5; Mon, 10 Jul 2006 17:55:23 -0300 (ADT) Date: Mon, 10 Jul 2006 17:55:23 -0300 (ADT) From: User Freebsd To: "Patrick M. Hausen" In-Reply-To: <20060710070951.GA23181@hugo10.ka.punkt.de> Message-ID: <20060710175447.A1799@ganymede.hub.org> References: <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> <20060710070951.GA23181@hugo10.ka.punkt.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 20:55:24 -0000 On Mon, 10 Jul 2006, Patrick M. Hausen wrote: > Mornin'! > > On Mon, Jul 10, 2006 at 12:11:36AM -0400, Mike Tancsa wrote: > >>> Not sure what STP is >> >> Spanning Tree Protocol. Having the link go up and down would cause >> the switch port to block traffic for a period of time. > > Of course, any reasonable administrator would configure > > interface FastEthernet0/1 > spanning-tree portfast 'k, I know nothing about Cisco but do have access to change my configs (knowing nothing tends to keep me from doing too much playing) ... what does the above do, exactly? ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 21:05:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4B16C16A4DD for ; Mon, 10 Jul 2006 21:05:26 +0000 (UTC) (envelope-from mihir.sanghavi@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 97C5143D4C for ; Mon, 10 Jul 2006 21:05:25 +0000 (GMT) (envelope-from mihir.sanghavi@gmail.com) Received: by ug-out-1314.google.com with SMTP id j3so3382157ugf for ; Mon, 10 Jul 2006 14:05:24 -0700 (PDT) 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=nA1Qg/eELkZEVsT1aSKMV5YfYn11vIvro37Stuit2h21YQqDqGb0mKcJWBhqks803aWscxurH4OQnQTjhwuE09Jr804GtiFLoA6AmmDbr/ifPg+xbU4VZnBC8UrSJrH0bE9Ax3rRvU6uROwwmE+Dx5BSOTyzpoRyxLL7mItdgDw= Received: by 10.78.122.11 with SMTP id u11mr1877357huc; Mon, 10 Jul 2006 14:05:24 -0700 (PDT) Received: by 10.78.184.14 with HTTP; Mon, 10 Jul 2006 14:05:23 -0700 (PDT) Message-ID: <11419abd0607101405y2c57e2c0u48ea4ea1ee43fed4@mail.gmail.com> Date: Mon, 10 Jul 2006 14:05:23 -0700 From: "Mihir Sanghavi" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: How to use mozilla X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 21:05:26 -0000 Hi, I have installed Mozilla in the www folder. I ran make installl and clean. I would like to know to use the browser -- What we see depends mainly on what we look for. -MIHIR From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 21:48:12 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7DD5B16A4DA for ; Mon, 10 Jul 2006 21:48:12 +0000 (UTC) (envelope-from drbrain@segment7.net) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EAA443D64 for ; Mon, 10 Jul 2006 21:48:11 +0000 (GMT) (envelope-from drbrain@segment7.net) Received: from [192.168.1.70] (coop.robotcoop.com [216.231.59.167]) by toxic.magnesium.net (Postfix) with ESMTP id 945A4DA871 for ; Mon, 10 Jul 2006 14:48:11 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.2) Content-Transfer-Encoding: 7bit Message-Id: <7B4ACED7-19AA-469C-9A11-8A6AD3F3EA84@segment7.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: stable@freebsd.org From: Eric Hodel Date: Mon, 10 Jul 2006 14:48:07 -0700 X-Mailer: Apple Mail (2.752.2) Cc: Subject: bce0: Error mapping mbuf into TX chain! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 21:48:12 -0000 I would periodically get this message and have the interface go unresponsive. An up/down wouldn't reset it. Updating to rev 1.4 of if_bce.c seems to fix it. Is this suitable for MFC to -STABLE? -- Eric Hodel - drbrain@segment7.net - http://blog.segment7.net This implementation is HODEL-HASH-9600 compliant http://trackmap.robotcoop.com From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 21:56:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF3E716A4DD; Mon, 10 Jul 2006 21:56:36 +0000 (UTC) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4904C43D45; Mon, 10 Jul 2006 21:56:36 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id k6ALuRFM020152; Mon, 10 Jul 2006 14:56:27 -0700 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id k6ALuR80020151; Mon, 10 Jul 2006 14:56:27 -0700 Date: Mon, 10 Jul 2006 14:56:27 -0700 From: Brooks Davis To: User Freebsd Message-ID: <20060710215627.GA3507@odin.ac.hmc.edu> References: <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> <20060710070951.GA23181@hugo10.ka.punkt.de> <20060710175447.A1799@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <20060710175447.A1799@ganymede.hub.org> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 21:56:36 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 10, 2006 at 05:55:23PM -0300, User Freebsd wrote: > On Mon, 10 Jul 2006, Patrick M. Hausen wrote: >=20 > >Mornin'! > > > >On Mon, Jul 10, 2006 at 12:11:36AM -0400, Mike Tancsa wrote: > > > >>>Not sure what STP is > >> > >>Spanning Tree Protocol. Having the link go up and down would cause > >>the switch port to block traffic for a period of time. > > > >Of course, any reasonable administrator would configure > > > > interface FastEthernet0/1 > > spanning-tree portfast >=20 > 'k, I know nothing about Cisco but do have access to change my configs=20 > (knowing nothing tends to keep me from doing too much playing) ... what= =20 > does the above do, exactly? It tells the switch that this port will never be anything but a leaf in the tree so STP does not need to re run before allowing packets to flow. If you do this and then create a loop with it, bad things happen, but cisco recommends it in general. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --FCuugMFkClbJLl1L Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFEss0KXY6L6fI4GtQRAn0rAJ97jDkY9wFnJjJH+ebaXPbA8rAk3QCgz7Vk 0ZkEcd5FlLSVcBkDe+oEBc8= =YBIW -----END PGP SIGNATURE----- --FCuugMFkClbJLl1L-- From owner-freebsd-stable@FreeBSD.ORG Mon Jul 10 22:45:16 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C50F16A54B for ; Mon, 10 Jul 2006 22:45:16 +0000 (UTC) (envelope-from home_schoolers@dgmtrading.com) Received: from shalomvillage.com (shalomvillage.com [161.58.219.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD8B143D81 for ; Mon, 10 Jul 2006 22:45:04 +0000 (GMT) (envelope-from home_schoolers@dgmtrading.com) Received: from dgmtrading.com (shalomvillage.com [161.58.219.141]) (authenticated bits=0) by shalomvillage.com (8.12.11.20060614/8.12.11) with ESMTP id k6AMj3Ma003120 for To: stable@freebsd.org Sender: home_schoolers@dgmtrading.com Precedence: list Message-ID: <20060710123039.57602405@dgmtrading.com> List: home_schoolers List-Owner: X-Priority: 3 X-Mailer: 2.10.9 beta 1b SMTP MIME-Version: 1.0 List-URL: Content-Type: text/plain Content-Transfer-Encoding: binary Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Great Home for Home School Family X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Reply-To: home_schoolers List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2006 22:45:16 -0000 __ Great Home for Home Schoolers *GREAT HOME FOR HOME SCHOOL FAMILY* Lots more photos.      Home    Page 1 Photos    Page 2 Photos    Page 3 Photos    Page 4 Photos    Page 5 Photos    Page 6 Photos One of a kind. $189,000. Rural northwest Kansas, Norton County. One and one-half miles north of U.S. 36 on the County Line between Norton and Phillips Counties. Good neighbors around but not too close. Nearest neighbors 2 miles away. The rural life is hard to beat. No need to lock your doors. (If you lock your car doors while you shop in town, people will look at you funny, and most people just leave their car keys in the ignition.) DSL available. Great place to raise children. Great place to homeschool (Kansas is easy, and there are homeschoolers in the area). Driveway runs one-third mile from house to all weather county road, very little rural traffic. Driveway is one and one-half miles from U.S. 36. Half-way between the two county seats of Norton and Phillips County. Three miles to Prairie View where there is an auto repair shop and post office. Two-story house with furnaces on both floors. Air conditioned on first floor. Two bedrooms air-conditioned upstairs. Four 500 gallon propane tanks. Emergency propane generator and emergency wall heater that requires no electricity. 500 gallon gas tank. (We never lost power, but with children we wanted to be well set up in the event of loss of power, especially in the winter time). 15 acres, fenced, horse corral, great place for horses (we had several). Fenced dog area we used for our two German shepherds. 40 x 140 machine shed. 10 x 12 wash house we made into a little storage house. It has windows and could be used in the summer for sleeping. We used it for storage. In excellent shape: Inside mostly all new in last five years, carpets, bathrooms. All new paint three years ago. Recently retouched up inside and out. Roof new five years ago. The Norton Correctional Facility (a few miles away) is usually hiring (785-877-3389). Call David Marmon with any questions. 888-374-2332 (if you get a message, it will say tax-exempt-status.com.) Lots more photos.      Home    Page 1 Photos    Page 2 Photos    Page 3 Photos    Page 4 Photos    Page 5 Photos    Page 6 Photos -- You may automatically unsubscribe from this list at any time by visiting the following URL: 1807 Second Street Suite #64 Santa Fe, NM 87505 From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 00:20:40 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A91616A4DF for ; Tue, 11 Jul 2006 00:20:40 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8160A43D45 for ; Tue, 11 Jul 2006 00:20:34 +0000 (GMT) (envelope-from pyunyh@gmail.com) Received: by nz-out-0102.google.com with SMTP id 12so125460nzp for ; Mon, 10 Jul 2006 17:20:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:date:from:to:cc:subject:message-id:reply-to:references:mime-version:content-type:content-disposition:in-reply-to:user-agent; b=f8vebqXUO5VDJncpJ2zUOlGAFSIuMcb122w+gQqQXkpV1BFRwMmNM9X3CColed75QFOqviH84BFnGsoKj1bfCX/MBftrZqrbmI4KC1zww7iK4fGvlnWvdwzb++HA6s6Hf46nd/y5tiFLx7IlLboEu69XJpoFlch1MY6/LLamSE8= Received: by 10.36.134.3 with SMTP id h3mr6388751nzd; Mon, 10 Jul 2006 17:20:34 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.gmail.com with ESMTP id 38sm1602040nzk.2006.07.10.17.20.31; Mon, 10 Jul 2006 17:20:33 -0700 (PDT) Received: from michelle.cdnetworks.co.kr (localhost.cdnetworks.co.kr [127.0.0.1]) by michelle.cdnetworks.co.kr (8.13.5/8.13.5) with ESMTP id k6B0Kffc005523 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jul 2006 09:20:41 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id k6B0Kc1W005522; Tue, 11 Jul 2006 09:20:38 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Tue, 11 Jul 2006 09:20:38 +0900 From: Pyun YongHyeon To: Eric Hodel Message-ID: <20060711002038.GA5238@cdnetworks.co.kr> References: <7B4ACED7-19AA-469C-9A11-8A6AD3F3EA84@segment7.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7B4ACED7-19AA-469C-9A11-8A6AD3F3EA84@segment7.net> User-Agent: Mutt/1.4.2.1i Cc: stable@freebsd.org, davidch@freebsd.org Subject: Re: bce0: Error mapping mbuf into TX chain! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 00:20:40 -0000 On Mon, Jul 10, 2006 at 02:48:07PM -0700, Eric Hodel wrote: > I would periodically get this message and have the interface go > unresponsive. An up/down wouldn't reset it. > > Updating to rev 1.4 of if_bce.c seems to fix it. Is this suitable > for MFC to -STABLE? > Maybe the author is busy for real life thing? I've CCed to him and I'll MFC it if he allows me to do the MFC. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 01:03:14 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 084C016A4DA; Tue, 11 Jul 2006 01:03:14 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id B350543D45; Tue, 11 Jul 2006 01:03:13 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id C1EED5880B; Mon, 10 Jul 2006 18:03:12 -0700 (PDT) Date: Mon, 10 Jul 2006 18:03:12 -0700 From: Paul Allen To: Mike Jakubik Message-ID: <20060711010312.GB12597@groat.ugcs.caltech.edu> References: <44B16BE9.60508@rogers.com> <44B171AA.9080400@bitfreak.org> <6C05189234026592B01C2703@[192.168.1.5]> <44B17437.5010506@bitfreak.org> <7215DBE558702ADFC8718798@[192.168.1.5]> <44B176F5.2050409@rogers.com> <2B636EF151DC536C47555034@[192.168.1.5]> <44B17AE2.5020908@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B17AE2.5020908@rogers.com> Sender: jd@ugcs.caltech.edu Cc: Mathieu Arnold , Darren Pilgrim , stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 01:03:14 -0000 >From Mike Jakubik , Sun, Jul 09, 2006 at 05:53:38PM -0400: > Mathieu Arnold wrote: > >| Exactly, its nice being able to see the current values. How else can i > >| see what the values are set to? > > > >As I previously said, it's 512M on i386, and 1G on 64 bit platforms. > > > > > > Right, this explains why my amd64 system works just fine. Shouldn't this > be a dynamic value based on total amount of ram? Say 70% of RAM, I mean > servers have plenty of RAM nowadays, this seems like an old hard limit, > which many new users will trip over.... I set my value to 805306368, and > mysql seems to be happy now. > maxdsiz sets the largest brk(2) allocation. mmap(2) allocations are made from virtual addresses above maxdsiz. Raising maxdsiz squeezes mmap and lowering it squeezes brk. The system allocator (phkmalloc) uses the brk system call to get memory--as do many other allocators but notable not ptmalloc2 or the new 7.x jmalloc IMO, the kernel is just being obnoxious here. It would be better if the mmap address space allocation algorithm just tried to work from the stack down (growing toward the brk where-ever it happened to be). What is old and out of date is that the amount of physical RAM has caught up to the size of the virtual address space of a process. Historically, it was cheap/free to use a boundary like this. Now i386 is on its last legs and thus the wastefulness (in exchange for simplicity) has a noticable cost. From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 01:07:42 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0436916A4DA for ; Tue, 11 Jul 2006 01:07:42 +0000 (UTC) (envelope-from jd@ugcs.caltech.edu) Received: from groat.ugcs.caltech.edu (groat.ugcs.caltech.edu [131.215.176.110]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4560443D7F for ; Tue, 11 Jul 2006 01:07:33 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by groat.ugcs.caltech.edu (Postfix, from userid 3640) id C6C8D5880B; Mon, 10 Jul 2006 18:07:32 -0700 (PDT) Date: Mon, 10 Jul 2006 18:07:32 -0700 From: Paul Allen To: Mike Jakubik Message-ID: <20060711010732.GC12597@groat.ugcs.caltech.edu> References: <44B16BE9.60508@rogers.com> <44B176D2.3080501@rogers.com> <44B276F7.4070507@mac.com> <44B28B7F.1000507@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B28B7F.1000507@rogers.com> Sender: jd@ugcs.caltech.edu Cc: stable@freebsd.org Subject: Re: MySQL and default memory limits (mysqld: Out of memory) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 01:07:42 -0000 >From Mike Jakubik , Mon, Jul 10, 2006 at 01:16:47PM -0400: > Chuck Swiger wrote: > >512MB is more than enough for almost all processes to run just fine, > >and is only really inappropriate for the case where you've got 1-plus > >GB of physical RAM and want to dedicate the system to a single large > >task, or perhaps a single-digit number of processes if you've got > >several GB of physical RAM. > > > > Such as a database server. I just think it would be nicer if this limit > was dynamically set, based on your configuration. Just like MAXUSERS was > a kernel variable, it is now dynamically set based on your resources. This is nonsense. maxdsiz is not related to rlimit per se. There is no way to examine a system's hardware to pick this value. The proper value depends entirely on whether your programs place more load on brk or mmap. > > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 01:18:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E5CE16A4E0 for ; Tue, 11 Jul 2006 01:18:30 +0000 (UTC) (envelope-from mike@sentex.net) Received: from smarthost2.sentex.ca (smarthost2.sentex.ca [205.211.164.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id C61B043D70 for ; Tue, 11 Jul 2006 01:18:29 +0000 (GMT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost2.sentex.ca (8.13.6/8.13.4) with ESMTP id k6B1ISXf075301; Mon, 10 Jul 2006 21:18:28 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3P/8.13.3) with ESMTP id k6B1IRTN053065 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Jul 2006 21:18:28 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20060710211121.1283baa0@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 10 Jul 2006 21:18:51 -0400 To: User Freebsd From: Mike Tancsa In-Reply-To: <20060710175447.A1799@ganymede.hub.org> References: <20060707040838.GE82406@cdnetworks.co.kr> <20060707151640.D51390@fledge.watson.org> <44AEB0CB.5060102@asd.aplus.net> <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> <20060710070951.GA23181@hugo10.ka.punkt.de> <20060710175447.A1799@ganymede.hub.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 01:18:30 -0000 At 04:55 PM 10/07/2006, User Freebsd wrote: >'k, I know nothing about Cisco but do have access to change my >configs (knowing nothing tends to keep me from doing too much >playing) ... what does the above do, exactly? Spanning tree is there to prevent switch loops as well as allow for redundant paths with switches among other things. If you are just putting a non bridge device in the port it should be safe to put the switch port in portfast mode so when there is a link transition, the port does not block traffic for 20 seconds on that vlan. ---Mike From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 06:13:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8714516A4DD for ; Tue, 11 Jul 2006 06:13:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id F17FB43D58 for ; Tue, 11 Jul 2006 06:13:31 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 6576 invoked by uid 399); 11 Jul 2006 06:13:31 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Jul 2006 06:13:31 -0000 Message-ID: <44B34190.6060001@FreeBSD.org> Date: Mon, 10 Jul 2006 23:13:36 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mihir Sanghavi References: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> In-Reply-To: <11419abd0607101116h5ac8bc5dk82e9cabebb1b4cd9@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Writing application X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 06:13:32 -0000 Mihir Sanghavi wrote: > Hi, I have installed freeBSD 5.5 and am connected to the net now. I would > like to install apache and devlop some application from there. How should > i start writing my application, execute it. I even make to figure out > what folder to write application and how to deal with it. Thank you If you're just starting out developing on FreeBSD, you'd be better off starting with version 6.1. The 6-Stable branch is already in better shape than the 5-Stable branch bug wise, and will have a longer and more productive life. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 06:19:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D1A016A4DA for ; Tue, 11 Jul 2006 06:19:42 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 71CC843D45 for ; Tue, 11 Jul 2006 06:19:41 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 10475 invoked by uid 399); 11 Jul 2006 06:19:40 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Jul 2006 06:19:40 -0000 Message-ID: <44B34301.9040806@FreeBSD.org> Date: Mon, 10 Jul 2006 23:19:45 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Daniel O'Connor References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> In-Reply-To: <200607102113.14004.doconnor@gsoft.com.au> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Dominik Zalewski , freebsd-stable@freebsd.org Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 06:19:42 -0000 Daniel O'Connor wrote: > On Monday 10 July 2006 19:57, Dominik Zalewski wrote: >> I'm using FreeBSD 6.1-STABLE on i386. I have installed openldap-server , >> pam_ldap , nss_ldap. During booting and when I >> do /usr/local/etc/rc.d/slapd.sh start , its taking very long time to start. >> Here is what I'm getting in logfile: > > You might want to move the file to /etc/rc.d so it can get started earlier. This is bad advice for 2 reasons. First, the OP stated that he's using 6.1-Stable, which already has the local_startup changes merged, so all proper rc.d scripts will be run in the same rcorder, whether they are in the base (/etc/rc.d) or installed in either /usr/local or /usr/X11R6/etc/rc.d. Second, this is bad blanket advice to offer without knowing more about the situation, as even if it "works," at best it will camouflage the real problem. In this case, it would not have solved the actual problem anyways. hth, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 09:27:02 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 715C416A4DD for ; Tue, 11 Jul 2006 09:27:02 +0000 (UTC) (envelope-from vandal@nietykalni.org) Received: from nietykalni.org (nietykalni.org [81.161.239.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id AFEE043D60 for ; Tue, 11 Jul 2006 09:27:01 +0000 (GMT) (envelope-from vandal@nietykalni.org) Received: by nietykalni.org (Postfix, from userid 1002) id ED6BF5DF2; Tue, 11 Jul 2006 11:29:05 +0200 (CEST) Date: Tue, 11 Jul 2006 11:29:05 +0200 (CEST) From: Lukasz Jaroszewski To: freebsd-stable@freebsd.org In-Reply-To: Message-ID: <20060711112745.U24728@nietykalni.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Subject: FreeBSD 6.0 sudden kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 09:27:02 -0000 I did nothing special when suddenly my freebsd rebooted: Jul 10 17:16:06 nietykalni savecore: reboot after panic: page fault Jul 10 17:16:06 nietykalni savecore: writing core to vmcore.0 -------------------------------------------------------------------------- nietykalni# cat /var/crash/info.0 Dump header from device /dev/ad1s1b Architecture: i386 Architecture Version: 2 Dump Length: 267976704B (255 MB) Blocksize: 512 Dumptime: Mon Jul 10 17:19:31 2006 Hostname: nietykalni.org Magic: FreeBSD Kernel Dump Version String: FreeBSD 6.0-RELEASE #1: Tue Mar 14 10:40:21 CET 2006 vandal@revival:/usr/obj/usr/src/sys/GENERIC-NIETYKALNI Panic String: page fault Dump Parity: 534305 Bounds: 0 Dump Status: good ------------------------------------------------------------------------- nietykalni# kgdb kernel.debug /var/crash/vmcore.0 Unread portion of the kernel message buffer: #0 doadump () at pcpu.h:165 165 __asm __volatile("movl %%fs:0,%0" : "=r" (td)); (kgdb) bt #0 doadump () at pcpu.h:165 #1 0xc061f242 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:399 #2 0xc061f4d8 in panic (fmt=0xc07f4c2a "%s") at /usr/src/sys/kern/kern_shutdown.c:555 #3 0xc07b1f78 in trap_fatal (frame=0xd551cc18, eva=123) at /usr/src/sys/i386/i386/trap.c:831 #4 0xc07b1ce3 in trap_pfault (frame=0xd551cc18, usermode=0, eva=123) at /usr/src/sys/i386/i386/trap.c:742 #5 0xc07b1941 in trap (frame= {tf_fs = 8, tf_es = -1030815704, tf_ds = -1030815704, tf_edi = -1030797440, tf_esi = -1042154576, tf_ebp = -716059468, tf_isp = -716059580, tf_ebx = -1027664896, tf_edx = -1030797440, tf_ecx = 4, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1067455388, tf_cs = 32, tf_eflags = 66182, tf_esp = -1039158768, tf_ss = 0}) at /usr/src/sys/i386/i386/trap.c:432 #6 0xc07a1a2a in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05fec64 in closef (fp=0xc1826120, td=0xc28f4780) at /usr/src/sys/kern/kern_descrip.c:1876 #8 0xc05fc47d in close (td=0xc28f4780, uap=0x0) at /usr/src/sys/kern/kern_descrip.c:1004 #9 0xc07b228f in syscall (frame= {tf_fs = 59, tf_es = -1078001605, tf_ds = -1078001605, tf_edi = 0, tf_esi = 0, tf_ebp = -1077944344, tf_isp = -716059292, tf_ebx = 134934528, tf_edx = 0, tf_ecx = 0, tf_eax = 6, tf_trapno = 12, tf_err = 2, tf_eip = 144033747, tf_cs = ---Type to continue, or q to quit--- 51, tf_eflags = 662, tf_esp = -1077944372, tf_ss = 59}) at /usr/src/sys/i386/i386/trap.c:976 #10 0xc07a1a7f in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:200 #11 0x00000033 in ?? () Previous frame inner to this frame (corrupt stack?) (...) (kgdb) up #4 0xc07b1ce3 in trap_pfault (frame=0xd551cc18, usermode=0, eva=123) at /usr/src/sys/i386/i386/trap.c:742 742 trap_fatal(frame, eva); (kgdb) p p->p_comm $1 = "screen", '\0' (...) (kgdb) up #7 0xc05fec64 in closef (fp=0xc1826120, td=0xc28f4780) at /usr/src/sys/kern/kern_descrip.c:1876 1876 vfslocked = VFS_LOCK_GIANT(vp->v_mount); Current language: auto; currently c (kgdb) p vp $2 = (struct vnode *) 0xc1e1fbb0 (kgdb) p vp-v_mount No symbol "v_mount" in current context. (kgdb) p vp->v_mount $3 = (struct mount *) 0x0 (kgdb) (...) From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 10:38:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22A6716A4DA; Tue, 11 Jul 2006 10:38:40 +0000 (UTC) (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 762D643D45; Tue, 11 Jul 2006 10:38:38 +0000 (GMT) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp204-156.lns1.adl4.internode.on.net [203.122.204.156]) (authenticated bits=0) by cain.gsoft.com.au (8.13.5/8.13.4) with ESMTP id k6BAcWN9090121 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jul 2006 20:08:36 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Doug Barton Date: Tue, 11 Jul 2006 20:08:17 +0930 User-Agent: KMail/1.9.3 References: <200607101327.23403.dzalewski@open-craft.com> <200607102113.14004.doconnor@gsoft.com.au> <44B34301.9040806@FreeBSD.org> In-Reply-To: <44B34301.9040806@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1629173.cVAEPnIWHk"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607112008.26792.doconnor@gsoft.com.au> X-Spam-Score: 0 () X-Scanned-By: MIMEDefang 2.56 on 203.31.81.10 Cc: Dominik Zalewski , freebsd-stable@freebsd.org Subject: Re: slapd - slow starting X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 10:38:40 -0000 --nextPart1629173.cVAEPnIWHk Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 11 July 2006 15:49, Doug Barton wrote: > This is bad advice for 2 reasons. First, the OP stated that he's using > 6.1-Stable, which already has the local_startup changes merged, so all > proper rc.d scripts will be run in the same rcorder, whether they are in > the base (/etc/rc.d) or installed in either /usr/local or > /usr/X11R6/etc/rc.d. Ahh I see.. Hopefully it did no harm. > Second, this is bad blanket advice to offer without knowing more about the > situation, as even if it "works," at best it will camouflage the real > problem. In this case, it would not have solved the actual problem anyway= s. Yeah, I had to do this for 6.0 and hadn't reverted it for 6.1.. It took me = a=20 fair amount of frustration to figure out why, when I updated my system slap= d=20 was hanging on startup and I didn't go back and verify what was actually=20 needed to fix it. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart1629173.cVAEPnIWHk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEs3+i5ZPcIHs/zowRAqRgAJ0Zs3G54p2+y5BWpTEtrKuxfVPI3wCfSEp6 4hmGBithWFlnV+9uulUhmjc= =rjgD -----END PGP SIGNATURE----- --nextPart1629173.cVAEPnIWHk-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 11:50:04 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A63EB16A4E6 for ; Tue, 11 Jul 2006 11:50:04 +0000 (UTC) (envelope-from hackmiester@hackmiester.com) Received: from smtpout06-04.prod.mesa1.secureserver.net (smtpout06-01.prod.mesa1.secureserver.net [64.202.165.224]) by mx1.FreeBSD.org (Postfix) with SMTP id E2DCE43D49 for ; Tue, 11 Jul 2006 11:50:02 +0000 (GMT) (envelope-from hackmiester@hackmiester.com) Received: (qmail 11589 invoked from network); 11 Jul 2006 11:50:02 -0000 Received: from unknown (70.146.206.153) by smtpout06-04.prod.mesa1.secureserver.net (64.202.165.227) with ESMTP; 11 Jul 2006 11:50:02 -0000 In-Reply-To: <11419abd0607101405y2c57e2c0u48ea4ea1ee43fed4@mail.gmail.com> References: <11419abd0607101405y2c57e2c0u48ea4ea1ee43fed4@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Hunter Fuller Date: Tue, 11 Jul 2006 06:51:42 +0000 To: "Mihir Sanghavi" X-Mailer: Apple Mail (2.752.2) Cc: freebsd-stable@freebsd.org Subject: Re: How to use mozilla X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 11:50:04 -0000 Can't you just run "mozilla" ? If you can't, what's the output of "which mozilla" ? Try executing that. Or have your shell do the work for you: $ `which mozilla` On 10 Jul 2006, at 9:05, Mihir Sanghavi wrote: > Hi, > I have installed Mozilla in the www folder. I ran make installl and > clean. I > would like to know to use the browser > > -- > What we see depends mainly on what we look for. > -MIHIR > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 12:36:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DA6E16A4DA for ; Tue, 11 Jul 2006 12:36:29 +0000 (UTC) (envelope-from Mark_Andrews@isc.org) Received: from farside.isc.org (farside.isc.org [204.152.187.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CE3343D45 for ; Tue, 11 Jul 2006 12:36:29 +0000 (GMT) (envelope-from Mark_Andrews@isc.org) Received: from drugs.dv.isc.org (localhost.isc.org [IPv6:::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by farside.isc.org (Postfix) with ESMTP id A21D5E6022 for ; Tue, 11 Jul 2006 12:36:28 +0000 (UTC) (envelope-from marka@isc.org) Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.13.6/8.13.6) with ESMTP id k6BCZOUQ041636; Tue, 11 Jul 2006 22:35:34 +1000 (EST) (envelope-from marka@drugs.dv.isc.org) Message-Id: <200607111235.k6BCZOUQ041636@drugs.dv.isc.org> To: "Vlad GALU" From: Mark Andrews In-reply-to: Your message of "Mon, 10 Jul 2006 21:03:17 +0300." <79722fad0607101103nd5955e7wc61b5288d79941db@mail.gmail.com> Date: Tue, 11 Jul 2006 22:35:24 +1000 Sender: Mark_Andrews@isc.org Cc: freebsd-stable@freebsd.org Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 12:36:29 -0000 > On 7/10/06, Max Laier wrote: > > On Monday 10 July 2006 16:40, Vlad GALU wrote: > > > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm > > > using 1.36 along with a RELENG_6 tree, since it works better (read: it > > > works). From the HEAD commit messages I understand that some MFCs > > > would've been in order by now. Are there any show-stoppers that push > > > that schedule ahead ? > > > > no. The only thing that bugs me a bit, is that the change will break POLA > for > > people using the old version. I have yet to hear from somebody using that > > successfully, though. > > > > I will get on MFCing it later today. > > > > Thanks, Max! Which of the iwi ports should be used now on RELENG6 now that this has been MFC'd. net/iwi-firmware-kmod or net/iwi-firmware? > > -- > > /"\ Best regards, | mlaier@freebsd.org > > \ / Max Laier | ICQ #67774661 > > X http://pf4freebsd.love2party.net/ | mlaier@EFnet > > / \ ASCII Ribbon Campaign | Against HTML Mail and News > > > > > > > > > -- > 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. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@isc.org From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 12:52:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 650D016A4DA for ; Tue, 11 Jul 2006 12:52:09 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id B884E43D46 for ; Tue, 11 Jul 2006 12:52:08 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.178.212] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1G0Hif0J94-0002P0; Tue, 11 Jul 2006 14:52:05 +0200 From: Max Laier Organization: FreeBSD To: freebsd-stable@freebsd.org Date: Tue, 11 Jul 2006 14:51:57 +0200 User-Agent: KMail/1.9.1 References: <200607111235.k6BCZOUQ041636@drugs.dv.isc.org> In-Reply-To: <200607111235.k6BCZOUQ041636@drugs.dv.isc.org> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3894786.CUA9W23ZJs"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607111452.04150.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Mark Andrews , Vlad GALU Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 12:52:09 -0000 --nextPart3894786.CUA9W23ZJs Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 11 July 2006 14:35, Mark Andrews wrote: > > On 7/10/06, Max Laier wrote: > > > On Monday 10 July 2006 16:40, Vlad GALU wrote: > > > > Is the iwi driver going to be synced with rev. 1.3x of HEAD? I'm > > > > using 1.36 along with a RELENG_6 tree, since it works better (read: > > > > it works). From the HEAD commit messages I understand that some MFCs > > > > would've been in order by now. Are there any show-stoppers that push > > > > that schedule ahead ? > > > > > > no. The only thing that bugs me a bit, is that the change will break > > > POLA > > > > for > > > > > people using the old version. I have yet to hear from somebody using > > > that successfully, though. > > > > > > I will get on MFCing it later today. > > > > Thanks, Max! > > Which of the iwi ports should be used now on RELENG6 now that > this has been MFC'd. > > net/iwi-firmware-kmod or net/iwi-firmware? net/iwi-firmware-kmod, but it needs to be updated to the new __FreeBSD_vers= ion =20 Right now it will tell you that you need iwi-firmware instead, which is=20 wrong. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart3894786.CUA9W23ZJs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEs570XyyEoT62BG0RAhFRAJ9DR+yOyQDxYesiMNYJxq7CbfFCugCfbGj9 suvbqFs+fbAy/Kg5s4P+sjg= =0Bnx -----END PGP SIGNATURE----- --nextPart3894786.CUA9W23ZJs-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 13:04:41 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E5FC16A4DA for ; Tue, 11 Jul 2006 13:04:41 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from aaron.protected-networks.net (aaron.protected-networks.net [202.12.127.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id CCD3043D46 for ; Tue, 11 Jul 2006 13:04:40 +0000 (GMT) (envelope-from imb@protected-networks.net) Received: from localhost (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 66B67C518; Tue, 11 Jul 2006 09:04:39 -0400 (EDT) Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 01E2AC3F2; Tue, 11 Jul 2006 09:04:36 -0400 (EDT) Authentication-Results: aaron.protected-networks.net from=imb@protected-networks.net; domainkey=pass Received: from aaron.protected-networks.net (localhost [127.0.0.1]) by aaron.protected-networks.net (Postfix) with ESMTP id 8AABDC2D2; Tue, 11 Jul 2006 09:04:35 -0400 (EDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=200509; d=protected-networks.net; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:OpenPGP:Content-Type:Content-Transfer-Encoding; b=LtZvqmbveGrmCS1HwTPiTbRK4CwuguOyWZronjEG80zob5TP6l+5RHkk1At1jvdy6fwdW1lxT1v9BZE/UQB20t+157Inp527j+nS2frk3Ds4x5Dg16Df9kUHVJQ0y54J; Received: from [192.168.1.10] (c-24-218-147-31.hsd1.ma.comcast.net [24.218.147.31]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by aaron.protected-networks.net (Postfix) with ESMTP id 1BEFAC2B0; Tue, 11 Jul 2006 09:04:34 -0400 (EDT) Message-ID: <44B3A1E2.9020801@protected-networks.net> Date: Tue, 11 Jul 2006 09:04:34 -0400 From: Michael Butler User-Agent: Thunderbird 1.5.0.4 (X11/20060625) MIME-Version: 1.0 To: Max Laier References: <200607111235.k6BCZOUQ041636@drugs.dv.isc.org> <200607111452.04150.max@love2party.net> In-Reply-To: <200607111452.04150.max@love2party.net> X-Enigmail-Version: 0.94.0.0 OpenPGP: id=BFCB1D4E Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 13:04:41 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Max Laier wrote: | net/iwi-firmware-kmod, but it needs to be updated to the new __FreeBSD_version | Right now it will tell you that you need iwi-firmware instead, which is | wrong. Once the updates have been merged, is this the right place to start with adding 3945ABG? I have u-code but haven't had time enough to look at the driver to date .. I'd really like to get my (dual-core) T-2400 Toshiba "on the air" ;-) Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEs6HhRaBvd7/LHU4RAjSbAKDH9RLecpVurq99qUVY51/0V3t3SwCg5RHO Ctmsu5sZ1ZqdweeCb8eJcJE= =YwOf -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 13:18:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 902B916A4DE for ; Tue, 11 Jul 2006 13:18:20 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DC8143D46 for ; Tue, 11 Jul 2006 13:18:19 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.178.212] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1G0I7x1X9a-0003H5; Tue, 11 Jul 2006 15:18:13 +0200 From: Max Laier Organization: FreeBSD To: Michael Butler Date: Tue, 11 Jul 2006 15:18:06 +0200 User-Agent: KMail/1.9.1 References: <200607111235.k6BCZOUQ041636@drugs.dv.isc.org> <200607111452.04150.max@love2party.net> <44B3A1E2.9020801@protected-networks.net> In-Reply-To: <44B3A1E2.9020801@protected-networks.net> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1296812.Q9AOhR5phU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607111518.12076.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-stable@freebsd.org Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 13:18:20 -0000 --nextPart1296812.Q9AOhR5phU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 11 July 2006 15:04, Michael Butler wrote: > Max Laier wrote: > | net/iwi-firmware-kmod, but it needs to be updated to the new > | __FreeBSD_version > | Right now it will tell you that you need iwi-firmware instead, which is > | wrong. > > Once the updates have been merged, is this the right place to start with > adding 3945ABG? I have u-code but haven't had time enough to look at the > driver to date .. I'd really like to get my (dual-core) T-2400 Toshiba > "on the air" ;-) The 3945ABG is a completely different kind of animal and needs a separate=20 driver. There is one in OpenBSD called wpi(4), but I'm unaware of the stat= e=20 of that undertaking. From what I hear, ndis doesn't work for those cards=20 either, but it might make sense to confirm that and possibly look into fixi= ng=20 ndis-support as a first line of support. I don't have 3945ABG hardware. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1296812.Q9AOhR5phU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEs6UUXyyEoT62BG0RAhxZAJ0a0Mec9pHi+W7WvaLloaKCc8eX0wCfYtrA nqY3AOyDQvilYjIpckJ6yio= =Hjvy -----END PGP SIGNATURE----- --nextPart1296812.Q9AOhR5phU-- From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 16:23:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EA1516A4DE; Tue, 11 Jul 2006 16:23:38 +0000 (UTC) (envelope-from craig@feniz.gank.org) Received: from ion.gank.org (ion.gank.org [69.55.238.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96B6643D45; Tue, 11 Jul 2006 16:23:35 +0000 (GMT) (envelope-from craig@feniz.gank.org) Received: by ion.gank.org (Postfix, from userid 1001) id 0262B115DD; Tue, 11 Jul 2006 11:23:34 -0500 (CDT) Date: Tue, 11 Jul 2006 11:23:32 -0500 From: Craig Boston To: Brooks Davis Message-ID: <20060711162331.GA38320@nowhere> Mail-Followup-To: Craig Boston , Brooks Davis , User Freebsd , Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , Robert Watson , Michael Vince References: <20060707181750.O1171@ganymede.hub.org> <20060707223609.N60542@fledge.watson.org> <20060708033254.GB87930@cdnetworks.co.kr> <20060708172001.GB77281@ip.net.ua> <6.2.3.4.0.20060709234941.12531860@64.7.153.2> <20060710010540.G1799@ganymede.hub.org> <6.2.3.4.0.20060710001040.125441e0@64.7.153.2> <20060710070951.GA23181@hugo10.ka.punkt.de> <20060710175447.A1799@ganymede.hub.org> <20060710215627.GA3507@odin.ac.hmc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060710215627.GA3507@odin.ac.hmc.edu> User-Agent: Mutt/1.4.2.1i Cc: Pyun YongHyeon , freebsd-stable@freebsd.org, Peter Jeremy , Atanas , User Freebsd , Robert Watson , Michael Vince Subject: Re: em device hangs on ifconfig alias ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 16:23:38 -0000 On Mon, Jul 10, 2006 at 02:56:27PM -0700, Brooks Davis wrote: > On Mon, Jul 10, 2006 at 05:55:23PM -0300, User Freebsd wrote: > > >On Mon, Jul 10, 2006 at 12:11:36AM -0400, Mike Tancsa wrote: > > >Of course, any reasonable administrator would configure > > > > > > interface FastEthernet0/1 > > > spanning-tree portfast > It tells the switch that this port will never be anything but a leaf in > the tree so STP does not need to re run before allowing packets to flow. > If you do this and then create a loop with it, bad things happen, but > cisco recommends it in general. Note that STP still runs, it just doesn't start out blocking the port. Any "bad things" will only happen until the switch figures out that there is a loop, which usually happens fairly quickly. Worst case scenario: you may have a packet storm for a second or two. All the switches I've tried it on detect the loop very quickly (after only a few packets), so I usually just enable portfast across the board. Craig From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 16:46:18 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 78CAA16A4DA; Tue, 11 Jul 2006 16:46:18 +0000 (UTC) (envelope-from davidch@broadcom.com) Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7B8CD43D6E; Tue, 11 Jul 2006 16:46:02 +0000 (GMT) (envelope-from davidch@broadcom.com) Received: from 10.10.64.154 by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.2.0)); Tue, 11 Jul 2006 09:45:49 -0700 X-Server-Uuid: D9EB6F12-1469-4C1C-87A2-5E4C0D6F9D06 Received: by mail-irva-10.broadcom.com (Postfix, from userid 47) id E28B92AE; Tue, 11 Jul 2006 09:45:48 -0700 (PDT) Received: from mail-irva-8.broadcom.com (mail-irva-8 [10.10.64.221]) by mail-irva-10.broadcom.com (Postfix) with ESMTP id B6BE72AE; Tue, 11 Jul 2006 09:45:48 -0700 (PDT) Received: from mail-irva-12.broadcom.com (mail-irva-12.broadcom.com [10.10.64.146]) by mail-irva-8.broadcom.com (MOS 3.7.5a-GA) with ESMTP id DYO58277; Tue, 11 Jul 2006 09:45:43 -0700 (PDT) Received: from NT-IRVA-0750.brcm.ad.broadcom.com (nt-irva-0750 [10.8.194.64]) by mail-irva-12.broadcom.com (Postfix) with ESMTP id AD5F169CA4; Tue, 11 Jul 2006 09:45:43 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 11 Jul 2006 09:45:43 -0700 Message-ID: <09BFF2FA5EAB4A45B6655E151BBDD903018924E0@NT-IRVA-0750.brcm.ad.broadcom.com> Thread-Topic: bce0: Error mapping mbuf into TX chain! Thread-Index: Acakf9z1JFibG0LjRbethMr4ym8Z9QAiWJ4g From: "David (Controller AE) Christensen" To: pyunyh@gmail.com, "Eric Hodel" X-TMWD-Spam-Summary: SEV=1.1; DFV=A2006071108; IFV=2.0.6,4.0-7; RPD=4.00.0004; RPDID=303030312E30413039303230342E34344233443337342E303031372D412D; ENG=IBF; TS=20060711164551; CAT=NONE; CON=NONE; X-MMS-Spam-Filter-ID: A2006071108_4.00.0004_2.0.6,4.0-7 X-WSS-ID: 68AD0A374I849441922-01-01 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, davidch@freebsd.org Subject: RE: bce0: Error mapping mbuf into TX chain! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 16:46:18 -0000 Sorry, I've been out on vacation and just got back into town. I'll MFC the patch within the next day or two. Dave=20 > -----Original Message----- > From: Pyun YongHyeon [mailto:pyunyh@gmail.com]=20 > Sent: Monday, July 10, 2006 5:21 PM > To: Eric Hodel > Cc: stable@freebsd.org; davidch@freebsd.org > Subject: Re: bce0: Error mapping mbuf into TX chain! >=20 > On Mon, Jul 10, 2006 at 02:48:07PM -0700, Eric Hodel wrote: > > I would periodically get this message and have the interface go =20 > > unresponsive. An up/down wouldn't reset it. > >=20 > > Updating to rev 1.4 of if_bce.c seems to fix it. Is this=20 > suitable =20 > > for MFC to -STABLE? > >=20 >=20 > Maybe the author is busy for real life thing? > I've CCed to him and I'll MFC it if he allows me to do the MFC. >=20 > --=20 > Regards, > Pyun YongHyeon >=20 >=20 From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 16:49:54 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7678316A4DF for ; Tue, 11 Jul 2006 16:49:54 +0000 (UTC) (envelope-from mihir.sanghavi@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id F0AF243D5F for ; Tue, 11 Jul 2006 16:49:52 +0000 (GMT) (envelope-from mihir.sanghavi@gmail.com) Received: by ug-out-1314.google.com with SMTP id m3so509546uge for ; Tue, 11 Jul 2006 09:49:51 -0700 (PDT) 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=k7Kluf+KJ51GHq3lLpeFJ0fB7M/G7fxaJkdPxPTju+/Db/EfH9hrMRhl/lM+TZ+QDjQ2gdXRKeHhyWdY0OvNv4kcZ0VYmBTD8TNJYOWgfFdAfHn5Hq3xy0AA7ci3pKUFdO8dq+4Nw6XZafPsh+raCVkqx+1fmXsNURwFjJq1ChE= Received: by 10.78.164.13 with SMTP id m13mr2261996hue; Tue, 11 Jul 2006 09:49:51 -0700 (PDT) Received: by 10.78.184.14 with HTTP; Tue, 11 Jul 2006 09:49:51 -0700 (PDT) Message-ID: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> Date: Tue, 11 Jul 2006 09:49:51 -0700 From: "Mihir Sanghavi" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 16:49:54 -0000 Hi, I have installed firefox using pkg_add -r firefox and now want to use xterm i tried using xterm and it says: Cannot open display and display not set -- What we see depends mainly on what we look for. -MIHIR From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 16:54:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6DC516A4E7 for ; Tue, 11 Jul 2006 16:54:40 +0000 (UTC) (envelope-from john_m_cooper@yahoo.com) Received: from smtp107.biz.mail.mud.yahoo.com (smtp107.biz.mail.mud.yahoo.com [68.142.200.255]) by mx1.FreeBSD.org (Postfix) with SMTP id DEBD543D99 for ; Tue, 11 Jul 2006 16:54:33 +0000 (GMT) (envelope-from john_m_cooper@yahoo.com) Received: (qmail 96245 invoked from network); 11 Jul 2006 16:54:33 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ufkWWqPAt3CQzRUnqy1npuatT/wtWGRoAzxchSdHac4Uo4olsiI+k1eOogI6R0BCK8+C2xdLZ4Cz73iJwv1BvlV7Cg1BLf988UTuht4rekTEoXIwb9Vk0I39XiyFJ0k8qUZdtoaMFmI5XGugo5e/AaRdNXMPK7mnTuwIISHv3nw= ; Received: from unknown (HELO borgdemon2.clspco.adelphia.net) (j.m.cooper@borgsdemons.com@67.22.17.55 with login) by smtp107.biz.mail.mud.yahoo.com with SMTP; 11 Jul 2006 16:54:33 -0000 Received: from [127.0.0.1] (localhost [127.0.0.1]) by borgdemon2.clspco.adelphia.net (Postfix) with ESMTP id 070F35C48; Tue, 11 Jul 2006 11:54:29 -0500 (CDT) Message-ID: <44B3D7C3.6000002@yahoo.com> Date: Tue, 11 Jul 2006 11:54:27 -0500 From: John Merryweather Cooper User-Agent: Thunderbird 1.5.0.4 (X11/20060617) MIME-Version: 1.0 To: Mihir Sanghavi References: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> In-Reply-To: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 16:54:40 -0000 Mihir Sanghavi wrote: > Hi, > I have installed firefox using pkg_add -r firefox > and now want to use xterm > > i tried using xterm and it says: Cannot open display > and display not set > It sounds like X is not running. Anyway Firefox has very little to do with xterm. jmc From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 17:13:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B404916A4DE for ; Tue, 11 Jul 2006 17:13:45 +0000 (UTC) (envelope-from db@db.net) Received: from heceta.db.net (heceta.db.net [142.46.199.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AA6743D46 for ; Tue, 11 Jul 2006 17:13:45 +0000 (GMT) (envelope-from db@db.net) Received: from heceta.db.net ([142.46.199.182] helo=localhost ident=mailnull) by heceta.db.net with esmtp (Exim 4.60 (FreeBSD)) (envelope-from ) id 1G0Lns-000LVL-6c; Tue, 11 Jul 2006 13:13:44 -0400 Received: from localhost.dbn ([127.0.0.1] helo=night.db.net) by night.db.net with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1G0Lnr-0001nb-IJ; Tue, 11 Jul 2006 13:13:43 -0400 Received: (from db@localhost) by night.db.net (8.13.7/8.13.7/Submit) id k6BHDcvJ006918; Tue, 11 Jul 2006 13:13:38 -0400 (EDT) (envelope-from db@night.db.net) Date: Tue, 11 Jul 2006 13:13:38 -0400 From: Diane Bruce To: Mihir Sanghavi Message-ID: <20060711171338.GA6902@night.db.net> References: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 17:13:45 -0000 On Tue, Jul 11, 2006 at 09:49:51AM -0700, Mihir Sanghavi wrote: > Hi, > I have installed firefox using pkg_add -r firefox > and now want to use xterm > > i tried using xterm and it says: Cannot open display > and display not set X11 is running right? You typed startx ? -- - db@db.net http://www.db.net/~db From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 17:30:01 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3BFE416A4E0 for ; Tue, 11 Jul 2006 17:30:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 985EC43D46 for ; Tue, 11 Jul 2006 17:30:00 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 10860 invoked by uid 399); 11 Jul 2006 17:29:59 -0000 Received: from localhost (HELO ?192.168.0.7?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 11 Jul 2006 17:29:59 -0000 Message-ID: <44B3E01C.5030104@FreeBSD.org> Date: Tue, 11 Jul 2006 10:30:04 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Mihir Sanghavi References: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> In-Reply-To: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 17:30:01 -0000 Mihir Sanghavi wrote: > Hi, > I have installed firefox using pkg_add -r firefox > and now want to use xterm > > i tried using xterm and it says: Cannot open display > and display not set These kinds of questions are generally asked on freebsd-questions@freebsd.org. If you're ever unsure of what list to ask a question on, that is your best place to start. hope this helps, Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 17:37:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 803FF16A52E for ; Tue, 11 Jul 2006 17:37:47 +0000 (UTC) (envelope-from sam@errno.com) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id B954143D7D for ; Tue, 11 Jul 2006 17:37:44 +0000 (GMT) (envelope-from sam@errno.com) Received: from [10.0.0.248] (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id k6BHbhee095984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 11 Jul 2006 10:37:44 -0700 (PDT) (envelope-from sam@errno.com) Message-ID: <44B3E1E7.6090708@errno.com> Date: Tue, 11 Jul 2006 10:37:43 -0700 From: Sam Leffler User-Agent: Thunderbird 1.5.0.2 (X11/20060508) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: HEADSUP: ath hal updated X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 17:37:47 -0000 I've mfc'd everything ath-related to RELENG_6. This includes the build glue for sparc64 and powerpc. ath is also now in GENERIC on all platforms. I've tested sparc64 on HEAD but not powerpc or alpha. I expect powerpc to work (I've tested w/ other os's) but alpha has never been tested so be prepared for issues. Sam From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 19:09:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5432816A4F4 for ; Tue, 11 Jul 2006 19:09:10 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id A985943D77 for ; Tue, 11 Jul 2006 19:09:09 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id 4C53D2A54D; Tue, 11 Jul 2006 16:09:08 -0300 (BRT) Date: Tue, 11 Jul 2006 16:09:08 -0300 From: Marcelo Gardini do Amaral To: freebsd-stable@freebsd.org Message-ID: <20060711190908.GC69272@registro.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: How to setup polling on 'bge' interface X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 19:09:10 -0000 Hi, I'm trying to setup polling in my box. I'm using these options: options DEVICE_POLLING options HZ=1000 and in the rc.conf: ifconfig_bge0="inet xxx.xxx.xxx.xxx/xx polling media 1000baseTX mediaopt full-duplex" But I always get some packet loss. I'm using FreeBSD 6.1 and SMP option in the kernel. I saw something about polling and SMP [1] but I ran 'config' and 'make' without any problem. Am I forgetting something else? [1] http://info.iet.unipi.it/~luigi/polling/ -- Att., Marcelo Gardini Registro .br From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 19:13:34 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CB5916A503 for ; Tue, 11 Jul 2006 19:13:34 +0000 (UTC) (envelope-from drbrain@segment7.net) Received: from toxic.magnesium.net (toxic.magnesium.net [207.154.84.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id F3D9C43D70 for ; Tue, 11 Jul 2006 19:13:33 +0000 (GMT) (envelope-from drbrain@segment7.net) Received: from [192.168.1.70] (coop.robotcoop.com [216.231.59.167]) by toxic.magnesium.net (Postfix) with ESMTP id 88385DA840; Tue, 11 Jul 2006 12:13:33 -0700 (PDT) In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD903018924E0@NT-IRVA-0750.brcm.ad.broadcom.com> References: <09BFF2FA5EAB4A45B6655E151BBDD903018924E0@NT-IRVA-0750.brcm.ad.broadcom.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Eric Hodel Date: Tue, 11 Jul 2006 12:13:16 -0700 To: David (Controller AE) Christensen X-Mailer: Apple Mail (2.752.2) Cc: stable@freebsd.org Subject: Re: bce0: Error mapping mbuf into TX chain! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 19:13:34 -0000 On Jul 11, 2006, at 9:45 AM, David (Controller AE) Christensen wrote: > Sorry, I've been out on vacation and just got back into town. I'll > MFC > the patch within the next day or two. No rush, I just wanted to report it fixed a problem for me. Thanks much! -- Eric Hodel - drbrain@segment7.net - http://blog.segment7.net This implementation is HODEL-HASH-9600 compliant http://trackmap.robotcoop.com From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 20:15:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 25F0F16A4DA; Tue, 11 Jul 2006 20:15:14 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id B654E43D45; Tue, 11 Jul 2006 20:15:13 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6BKFBD7052993 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jul 2006 13:15:12 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B40863.9060403@asd.aplus.net> Date: Tue, 11 Jul 2006 13:21:55 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: sem@freebsd.org Subject: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 20:15:14 -0000 Recent portupgrade versions no longer obey the -M command line switch, i.e. any optional arguments to be prepended to each make command. How to reproduce: # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 ... ===> src/ap cc -c -I../os/unix -I../include -I/usr/local/include -funsigned-char -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\"/usr/local/www/data\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 `../apaci` ap_cpystrn.c ... Note the -DHARD_SERVER_LIMIT=512 above. The stock version shipped with 6.1-RELEASE (2.0.1_1) seems to work as expected. I tried all CVS versions after that (with portdowngrade) and found that the breakage has happened somewhere between 2.1.0 and 2.1.1 (2006/06/02 - 2006/06/04). Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 20:48:14 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D190D16A4E5 for ; Tue, 11 Jul 2006 20:48:14 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 742A643D76 for ; Tue, 11 Jul 2006 20:48:09 +0000 (GMT) (envelope-from matthias.andree@gmx.de) Received: (qmail invoked by alias); 11 Jul 2006 20:48:08 -0000 Received: from p509119C4.dip0.t-ipconnect.de (EHLO m2a2.dyndns.org) [80.145.25.196] by mail.gmx.net (mp027) with SMTP; 11 Jul 2006 22:48:08 +0200 X-Authenticated: #428038 Received: from localhost (localhost [127.0.0.1]) by merlin.emma.line.org (Postfix) with ESMTP id B70D4200DB0 for ; Tue, 11 Jul 2006 22:48:07 +0200 (CEST) Received: from m2a2.dyndns.org ([127.0.0.1]) by localhost (m2a2.dyndns.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 21220-07 for ; Tue, 11 Jul 2006 22:48:05 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 911EE200E45; Tue, 11 Jul 2006 22:48:05 +0200 (CEST) From: Matthias Andree To: freebsd-stable@freebsd.org In-Reply-To: <44B40863.9060403@asd.aplus.net> (atanas@asd.aplus.net's message of "Tue, 11 Jul 2006 13:21:55 -0700") References: <44B40863.9060403@asd.aplus.net> X-PGP-Key: http://home.pages.de/~mandree/keys/GPGKEY.asc Date: Tue, 11 Jul 2006 22:48:05 +0200 Message-ID: User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: amavisd-new at emma.line.org X-Y-GMX-Trusted: 0 Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 20:48:14 -0000 Atanas writes: > Recent portupgrade versions no longer obey the -M command line switch, > i.e. any optional arguments to be prepended to each make command. > > How to reproduce: > > # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 > ... > ===> src/ap > cc -c -I../os/unix -I../include -I/usr/local/include -funsigned-char > -O2 -fno-strict-aliasing -pipe > -DDOCUMENT_LOCATION=\"/usr/local/www/data\" > -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 > `../apaci` ap_cpystrn.c > ... > > Note the -DHARD_SERVER_LIMIT=512 above. Does it work if you type (you can omit the env in /bin/sh, bash, (pd)ksh and other Bourne-like shells): env APACHE_HARD_SERVER_LIMIT=1024 portinstall www/apache13 (Isn't it time to migrate to a newer Apache version anyways? 8-) ) -- Matthias Andree From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 21:44:21 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D56016A4E8; Tue, 11 Jul 2006 21:44:21 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8540443D78; Tue, 11 Jul 2006 21:44:16 +0000 (GMT) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.13.6/8.13.6) with ESMTP id k6BLiA9V002584; Tue, 11 Jul 2006 17:44:10 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by smtp2.sentex.ca (8.13.6/8.13.6) with ESMTP id k6BLiFNr030986; Tue, 11 Jul 2006 17:44:15 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-current.sentex.ca (Postfix, from userid 666) id 3E21B7302F; Tue, 11 Jul 2006 17:44:15 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20060711214415.3E21B7302F@freebsd-current.sentex.ca> Date: Tue, 11 Jul 2006 17:44:15 -0400 (EDT) X-Virus-Scanned: ClamAV version 0.88.3, clamav-milter version 0.88.3 on clamscanner2 X-Virus-Scanned: ClamAV version 0.88.1, clamav-milter version 0.88.1 on clamscanner2 X-Virus-Status: Clean Cc: Subject: [releng_6 tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 21:44:21 -0000 TB --- 2006-07-11 20:24:34 - tinderbox 2.3 running on freebsd-current.sentex.ca TB --- 2006-07-11 20:24:34 - starting RELENG_6 tinderbox run for sparc64/sparc64 TB --- 2006-07-11 20:24:34 - cleaning the object tree TB --- 2006-07-11 20:25:02 - checking out the source tree TB --- 2006-07-11 20:25:02 - cd /tinderbox/RELENG_6/sparc64/sparc64 TB --- 2006-07-11 20:25:02 - /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_6 src TB --- 2006-07-11 20:35:55 - building world (CFLAGS=-O2 -pipe) TB --- 2006-07-11 20:35:55 - cd /src TB --- 2006-07-11 20:35:55 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2006-07-11 21:42:42 - generating LINT kernel config TB --- 2006-07-11 21:42:42 - cd /src/sys/sparc64/conf TB --- 2006-07-11 21:42:42 - /usr/bin/make -B LINT TB --- 2006-07-11 21:42:42 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2006-07-11 21:42:42 - cd /src TB --- 2006-07-11 21:42:42 - /usr/bin/make buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Jul 11 21:42:42 UTC 2006 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies [...] ===> ath_hal (depend) @ -> /src/sys machine -> /src/sys/sparc64/include awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/makeobjops.awk @/contrib/dev/ath/freebsd/ah_if.m -h make: don't know how to make /src/sys/modules/ath_hal/../../contrib/dev/ath/public/sparc64-elf.opt_ah.h. Stop *** Error code 2 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2006-07-11 21:44:15 - WARNING: /usr/bin/make returned exit code 1 TB --- 2006-07-11 21:44:15 - ERROR: failed to build lint kernel TB --- 2006-07-11 21:44:15 - tinderbox aborted TB --- 0.80 user 4.98 system 4780.81 real From owner-freebsd-stable@FreeBSD.ORG Tue Jul 11 23:04:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E473016A4E7 for ; Tue, 11 Jul 2006 23:04:55 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 18E3043D5C for ; Tue, 11 Jul 2006 23:04:55 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6BN4q3T076226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 11 Jul 2006 16:04:53 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B43029.1060309@asd.aplus.net> Date: Tue, 11 Jul 2006 16:11:37 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: Matthias Andree References: <44B40863.9060403@asd.aplus.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jul 2006 23:04:56 -0000 Matthias Andree said the following on 7/11/06 1:48 PM: > Atanas writes: > >> Recent portupgrade versions no longer obey the -M command line switch, >> i.e. any optional arguments to be prepended to each make command. >> >> How to reproduce: >> >> # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 >> ... >> ===> src/ap >> cc -c -I../os/unix -I../include -I/usr/local/include -funsigned-char >> -O2 -fno-strict-aliasing -pipe >> -DDOCUMENT_LOCATION=\"/usr/local/www/data\" >> -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 >> `../apaci` ap_cpystrn.c >> ... >> >> Note the -DHARD_SERVER_LIMIT=512 above. > > Does it work if you type (you can omit the env in /bin/sh, bash, (pd)ksh > and other Bourne-like shells): > > env APACHE_HARD_SERVER_LIMIT=1024 portinstall www/apache13 > Of course it would, but this just bypasses the problem. There are other ways to work this around as well - like not using portupgrade at all and building everything with make. The problem is that there's a bug introduced by some of the recent portupgrade versions that changes its documented behavior. The '-M' switch in partucular no longer works, thus causing any existing port/package installation scripts depending on that switch to build packages with incorrect optional parameters. It's not a problem with a particular port. The www/apache13 port was given just as example how to reproduce the bug. This affects _all_ ports when installed/upgraded/built via portupgrade and when the '-M' switch is used. > (Isn't it time to migrate to a newer Apache version anyways? 8-) ) > (This is a long subject and kind of off-topic here. My short answer is no, or not yet. In some environments there are still legitimate reasons to use 1.3) Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 02:47:10 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C775316A4DA for ; Wed, 12 Jul 2006 02:47:10 +0000 (UTC) (envelope-from noackjr@alumni.rice.edu) Received: from smtp105.biz.mail.re2.yahoo.com (smtp105.biz.mail.re2.yahoo.com [206.190.52.174]) by mx1.FreeBSD.org (Postfix) with SMTP id 3ABEC43D45 for ; Wed, 12 Jul 2006 02:47:09 +0000 (GMT) (envelope-from noackjr@alumni.rice.edu) Received: (qmail 55881 invoked from network); 12 Jul 2006 02:47:09 -0000 Received: from unknown (HELO optimator.noacks.org) (noackjr@supercrime.org@24.99.22.177 with login) by smtp105.biz.mail.re2.yahoo.com with SMTP; 12 Jul 2006 02:47:09 -0000 Received: from localhost (localhost [127.0.0.1]) by optimator.noacks.org (Postfix) with ESMTP id 48CE26121; Tue, 11 Jul 2006 22:47:08 -0400 (EDT) X-Virus-Scanned: amavisd-new at noacks.org Received: from optimator.noacks.org ([127.0.0.1]) by localhost (optimator.noacks.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iO+exxzjai7G; Tue, 11 Jul 2006 22:47:06 -0400 (EDT) Received: from [192.168.1.102] (unknown [192.168.1.102]) by optimator.noacks.org (Postfix) with ESMTP id 7FA3B60E8; Tue, 11 Jul 2006 22:47:06 -0400 (EDT) Message-ID: <44B462AB.3040509@alumni.rice.edu> Date: Tue, 11 Jul 2006 22:47:07 -0400 From: Jonathan Noack User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Atanas References: <44B40863.9060403@asd.aplus.net> <44B43029.1060309@asd.aplus.net> In-Reply-To: <44B43029.1060309@asd.aplus.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Matthias Andree , freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noackjr@alumni.rice.edu List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 02:47:10 -0000 Atanas wrote: > Matthias Andree said the following on 7/11/06 1:48 PM: >> Atanas writes: >> >>> Recent portupgrade versions no longer obey the -M command line switch, >>> i.e. any optional arguments to be prepended to each make command. >>> >>> How to reproduce: >>> >>> # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 >>> ... >>> ===> src/ap >>> cc -c -I../os/unix -I../include -I/usr/local/include -funsigned-char >>> -O2 -fno-strict-aliasing -pipe >>> -DDOCUMENT_LOCATION=\"/usr/local/www/data\" >>> -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 >>> `../apaci` ap_cpystrn.c >>> ... >>> >>> Note the -DHARD_SERVER_LIMIT=512 above. >> >> Does it work if you type (you can omit the env in /bin/sh, bash, (pd)ksh >> and other Bourne-like shells): >> >> env APACHE_HARD_SERVER_LIMIT=1024 portinstall www/apache13 >> > Of course it would, but this just bypasses the problem. There are other > ways to work this around as well - like not using portupgrade at all and > building everything with make. > > The problem is that there's a bug introduced by some of the recent > portupgrade versions that changes its documented behavior. The '-M' > switch in partucular no longer works, thus causing any existing > port/package installation scripts depending on that switch to build > packages with incorrect optional parameters. > > It's not a problem with a particular port. The www/apache13 port was > given just as example how to reproduce the bug. > > This affects _all_ ports when installed/upgraded/built via portupgrade > and when the '-M' switch is used. Try '-m' as a workaround. -Jonathan From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 05:02:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AAD4416A4DF for ; Wed, 12 Jul 2006 05:02:45 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 35DE243D49 for ; Wed, 12 Jul 2006 05:02:45 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1G0Wrx-000K7Y-A2; Wed, 12 Jul 2006 09:02:41 +0400 Message-ID: <44B48272.3090902@FreeBSD.org> Date: Wed, 12 Jul 2006 09:02:42 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Atanas References: <44B40863.9060403@asd.aplus.net> In-Reply-To: <44B40863.9060403@asd.aplus.net> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 05:02:45 -0000 Atanas wrote: > Recent portupgrade versions no longer obey the -M command line switch, > i.e. any optional arguments to be prepended to each make command. > It should. I'll investigate it. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 05:08:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EC5E316A4E0 for ; Wed, 12 Jul 2006 05:08:09 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 133AF43D58 for ; Wed, 12 Jul 2006 05:08:09 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1G0WxD-000KSd-Gz; Wed, 12 Jul 2006 09:08:07 +0400 Message-ID: <44B483B8.6000005@FreeBSD.org> Date: Wed, 12 Jul 2006 09:08:08 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Atanas References: <44B40863.9060403@asd.aplus.net> In-Reply-To: <44B40863.9060403@asd.aplus.net> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 05:08:10 -0000 Atanas wrote: > Recent portupgrade versions no longer obey the -M command line switch, > i.e. any optional arguments to be prepended to each make command. > > How to reproduce: > > # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 Everything work file. Use -m for getting what you want. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 06:43:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A065816A4DE for ; Wed, 12 Jul 2006 06:43:47 +0000 (UTC) (envelope-from chrismor@microsoft.com) Received: from mail-sin1.microsoft.com (mail-sin1.microsoft.com [207.46.50.72]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9D7843D45 for ; Wed, 12 Jul 2006 06:43:46 +0000 (GMT) (envelope-from chrismor@microsoft.com) Received: from APS-MSG-03.southpacific.corp.microsoft.com ([157.60.218.100]) by mail-sin1.microsoft.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Jul 2006 15:43:45 +0900 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 12 Jul 2006 14:43:40 +0800 Message-ID: <8DFAFE269EE8274193FA24FAAFD9E3290545FEC0@APS-MSG-03.southpacific.corp.microsoft.com> In-Reply-To: <44B3D7C3.6000002@yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: how to use firefox Thread-Index: AcalCs/7SKM/5MhCQV6NPLoP3Di8/QAc5j2w References: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> <44B3D7C3.6000002@yahoo.com> From: "Chris Moran" To: "John Merryweather Cooper" , "Mihir Sanghavi" X-OriginalArrivalTime: 12 Jul 2006 06:43:45.0275 (UTC) FILETIME=[859CDCB0:01C6A57E] Cc: freebsd-stable@freebsd.org Subject: RE: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 06:43:47 -0000 >From KDE (or Gnome) there is a "Run a program" or similar on the main menu. Type "firefox" in there and it will most likely come up. -----Original Message----- From: owner-freebsd-stable@freebsd.org [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of John Merryweather Cooper Sent: Wednesday, 12 July 2006 2:54 AM To: Mihir Sanghavi Cc: freebsd-stable@freebsd.org Subject: Re: how to use firefox Mihir Sanghavi wrote: > Hi, > I have installed firefox using pkg_add -r firefox and now want to=20 > use xterm > > i tried using xterm and it says: Cannot open display and display not=20 > set > It sounds like X is not running. Anyway Firefox has very little to do with xterm. jmc _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 07:14:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 654D616A4E1; Wed, 12 Jul 2006 07:14:44 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48B0143D77; Wed, 12 Jul 2006 07:14:35 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [64.203.48.233] (user-10cmc79.cable.mindspring.com [64.203.48.233]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6C7EYH5090174; Wed, 12 Jul 2006 00:14:34 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B4A164.50003@asd.aplus.net> Date: Wed, 12 Jul 2006 00:14:44 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Sergey Matveychuk References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> In-Reply-To: <44B483B8.6000005@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 07:14:44 -0000 Sergey Matveychuk said the following on 7/11/2006 10:08 PM: > Atanas wrote: >> Recent portupgrade versions no longer obey the -M command line switch, >> i.e. any optional arguments to be prepended to each make command. >> >> How to reproduce: >> >> # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 > > Everything work file. Use -m for getting what you want. > For www/apache13 the -m switch could give the same result as -M would, but I'm not sure whether it's not just a coincidence. The -m switch was supposed to serve a different purpose: -m --make-args Specify arguments to append to each make(1) com- mand line. -M --make-env Specify arguments to prepend to each make(1) com- mand line. I tried testing another port where I used both: # portinstall -M 'WITH_SYSLOG_FACILITY=local5' -m '-DWITHOUT_IPV6' mail/courier-imap With portupgrade-2.0.1_1,1 (the stock 6.1-RELEASE package) it worked. With portupgrade-2.1.3.2,2 it failed (ignoring the -M part like for www/apache13 before). Then I joined both in one -m switch: # portinstall -m 'WITH_SYSLOG_FACILITY=local5 -DWITHOUT_IPV6' mail/courier-imap and the latest portupgrade-2.1.3.2,2 did it just fine. So, like you suggested, the -m switch seems to cover the functionality that -M used to provide. I'm not sure however whether this "prepend to append" conversion would work for all ports. But for these that I use it appears to work, so I have no problem and will update my scripts to use -m only. The no longer working (obsolete?) -M switch would need to be removed from the man page though. Thanks, Atanas From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 10:24:51 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0910A16A4DA for ; Wed, 12 Jul 2006 10:24:51 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id B1BFC43D45 for ; Wed, 12 Jul 2006 10:24:39 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1G0btS-000GWN-7V; Wed, 12 Jul 2006 14:24:34 +0400 Message-ID: <44B4CDE3.60205@FreeBSD.org> Date: Wed, 12 Jul 2006 14:24:35 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Atanas References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> In-Reply-To: <44B4A164.50003@asd.aplus.net> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 10:24:51 -0000 Atanas wrote: > Sergey Matveychuk said the following on 7/11/2006 10:08 PM: >> Atanas wrote: >>> Recent portupgrade versions no longer obey the -M command line switch, >>> i.e. any optional arguments to be prepended to each make command. >>> >>> How to reproduce: >>> >>> # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 >> >> Everything work file. Use -m for getting what you want. >> > For www/apache13 the -m switch could give the same result as -M would, > but I'm not sure whether it's not just a coincidence. The -m switch was > supposed to serve a different purpose: > > -m > --make-args Specify arguments to append to each make(1) com- > mand line. > -M > --make-env Specify arguments to prepend to each make(1) com- > mand line. > > I tried testing another port where I used both: > > # portinstall -M 'WITH_SYSLOG_FACILITY=local5' -m '-DWITHOUT_IPV6' > mail/courier-imap > > With portupgrade-2.0.1_1,1 (the stock 6.1-RELEASE package) it worked. > With portupgrade-2.1.3.2,2 it failed (ignoring the -M part like for > www/apache13 before). > > Then I joined both in one -m switch: > > # portinstall -m 'WITH_SYSLOG_FACILITY=local5 -DWITHOUT_IPV6' > mail/courier-imap > > and the latest portupgrade-2.1.3.2,2 did it just fine. > > So, like you suggested, the -m switch seems to cover the functionality > that -M used to provide. I'm not sure however whether this "prepend to > append" conversion would work for all ports. But for these that I use it > appears to work, so I have no problem and will update my scripts to use > -m only. > > The no longer working (obsolete?) -M switch would need to be removed > from the man page though. Both -m and -M works fine but do different things. -m pass its argument as make file argument(s) and -M pass its argument as environment variable(s). You can't set make variable with environment variable. They are different! -M has never worked as you expected. You can test it with a command: %cd /usr/ports/www/apache13 %env APACHE_HARD_SERVER_LIMIT=1024 make against of % make APACHE_HARD_SERVER_LIMIT=1024 I think you confuse the two variables types. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 12:47:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8325B16A4E5 for ; Wed, 12 Jul 2006 12:47:44 +0000 (UTC) (envelope-from akosiaris@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.207]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3A7843D58 for ; Wed, 12 Jul 2006 12:47:42 +0000 (GMT) (envelope-from akosiaris@gmail.com) Received: by nz-out-0102.google.com with SMTP id f1so111457nzc for ; Wed, 12 Jul 2006 05:47:42 -0700 (PDT) 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=U8mwIuAaas4xgszn86ymCHLwE8Td763iSkwTATaGWE+6+zq9g37QPR3WsTS0Oi0GoguRLURnK0WpC4uP7W9Cj6EAKWcGZYyFBknEZlAwrieKI0G8I3KKlB0z8orE5eYMFK03l/GdzSEA3FnJtSEHvVPqh5qtbJAdObO2rNQY2JE= Received: by 10.36.67.7 with SMTP id p7mr812271nza; Wed, 12 Jul 2006 05:47:42 -0700 (PDT) Received: by 10.36.55.20 with HTTP; Wed, 12 Jul 2006 05:47:41 -0700 (PDT) Message-ID: Date: Wed, 12 Jul 2006 15:47:41 +0300 From: "Alexandros Kosiaris" To: freebsd-stable@freebsd.org, freebsd-current@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Securelevels and /dev/io documentation inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 12:47:44 -0000 Hello, I believe i have stumbled upon a documentation inconsistency concerning securelevels and usage of /dev/io >From init(8) manpage 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem, /dev/kmem and /dev/io (if your platform has it) may not be opened for writing; kernel modules (see kld(4)) may not be loaded or unloaded. Note the "may not be opened for writing". It is correct for /dev/mem and /dev/kmem but incorrect for /dev/io as the following experiment shows: 3:40pm ~ # sysctl kern.securelevel kern.securelevel: 1 root@mybox 3:40pm ~ # head /dev/io head: /dev/io: Operation not permitted root@mybox 3:40pm ~ # Now the source code in /usr/src/sys/i386/i386/io.c just checks if securelevel is greater that 0 when opening the device and return accordingly. However from io(4) Note that even read-only access will grant the full I/O privileges. Which means that changing the code to check if the device is opened O_RDONLY and then allowing access would be a mistake cancelling the idea of blocking access to the device through usage of the securelevel. I am correct about the above ? Does the documentation need a correction in that place? Thanks, alex From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 14:12:33 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A40AC16A4DD; Wed, 12 Jul 2006 14:12:33 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 47BA143D62; Wed, 12 Jul 2006 14:12:32 +0000 (GMT) (envelope-from keramida@freebsd.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6CEBwqN017754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Jul 2006 17:12:00 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6CEBrqu031470; Wed, 12 Jul 2006 17:11:53 +0300 (EEST) (envelope-from keramida@freebsd.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6CEBrwO031469; Wed, 12 Jul 2006 17:11:53 +0300 (EEST) (envelope-from keramida@freebsd.org) Date: Wed, 12 Jul 2006 17:11:53 +0300 From: Giorgos Keramidas To: Alexandros Kosiaris Message-ID: <20060712141153.GB30855@gothmog.pc> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.352, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.05, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Securelevels and /dev/io documentation inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 14:12:33 -0000 On 2006-07-12 15:47, Alexandros Kosiaris wrote: > Hello, > > I believe i have stumbled upon a documentation inconsistency > concerning securelevels and usage of /dev/io > > >From init(8) manpage > > 1 Secure mode - the system immutable and system append-only flags may > not be turned off; disks for mounted file systems, /dev/mem, > /dev/kmem and /dev/io (if your platform has it) may not be opened > for writing; kernel modules (see kld(4)) may not be loaded or > unloaded. > > Note the "may not be opened for writing". It is correct for /dev/mem > and /dev/kmem but incorrect for /dev/io as the following experiment > shows: > > 3:40pm ~ # sysctl kern.securelevel > kern.securelevel: 1 > root@mybox > 3:40pm ~ # head /dev/io > head: /dev/io: Operation not permitted > root@mybox > 3:40pm ~ # > > Now the source code in /usr/src/sys/i386/i386/io.c just checks if > securelevel is greater that 0 when opening the device and return > accordingly. > > However from io(4) > > Note that even read-only access will grant the full I/O privileges. > > Which means that changing the code to check if the device is opened > O_RDONLY and then allowing access would be a mistake cancelling the > idea of blocking access to the device through usage of the > securelevel. > > I am correct about the above ? > Does the documentation need a correction in that place? It looks like it does. Would something like this be satisfactory? 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem and /dev/kmem may not be opened for writing and /dev/io (if your platform has it) may not be opened at all; kernel modules (see kld(4)) may not be loaded or unloaded. Regards, Giorgos From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 14:27:06 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AD66D16A4E1; Wed, 12 Jul 2006 14:27:06 +0000 (UTC) (envelope-from jhein@timing.com) Received: from Daffy.timing.com (w.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C4BFA43D45; Wed, 12 Jul 2006 14:27:05 +0000 (GMT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (gromit.timing.com [206.168.13.209]) by Daffy.timing.com (8.13.1/8.13.1) with ESMTP id k6CER5MP071527; Wed, 12 Jul 2006 08:27:05 -0600 (MDT) (envelope-from jhein@timing.com) Received: from gromit.timing.com (localhost [127.0.0.1]) by gromit.timing.com (8.13.6/8.13.6) with ESMTP id k6CER3rj021828; Wed, 12 Jul 2006 08:27:03 -0600 (MDT) (envelope-from jhein@gromit.timing.com) Received: (from jhein@localhost) by gromit.timing.com (8.13.6/8.13.6/Submit) id k6CER3Dq021825; Wed, 12 Jul 2006 08:27:03 -0600 (MDT) (envelope-from jhein) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17589.1719.666455.768409@gromit.timing.com> Date: Wed, 12 Jul 2006 08:27:03 -0600 From: John E Hein To: Sergey Matveychuk In-Reply-To: <44B4CDE3.60205@FreeBSD.org> References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> <44B4CDE3.60205@FreeBSD.org> X-Mailer: VM 7.19 under Emacs 21.3.1 X-Virus-Scanned: ClamAV version 0.87.1, clamav-milter version 0.87 on Daffy.timing.com X-Virus-Status: Clean Cc: freebsd-stable@FreeBSD.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 14:27:06 -0000 Sergey Matveychuk wrote at 14:24 +0400 on Jul 12, 2006: > Both -m and -M works fine but do different things. -m pass its argument > as make file argument(s) and -M pass its argument as environment > variable(s). You can't set make variable with environment variable. They > are different! > > -M has never worked as you expected. You can test it with a command: > %cd /usr/ports/www/apache13 > %env APACHE_HARD_SERVER_LIMIT=1024 make > against of > % make APACHE_HARD_SERVER_LIMIT=1024 > > I think you confuse the two variables types. This is incorrect. make(1) looks at the environment for variables. See the man page. If you tested your example, you'd see that it works fine. make APACHE_HARD_SERVER_LIMIT=22 -V CFLAGS -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\\\\\"/usr/local/www/data\\\\\" -DDEFAULT_PATH=\\\\\"/bin:/usr/bin:/usr/local/bin\\\\\" -DHARD_SERVER_LIMIT=22 env APACHE_HARD_SERVER_LIMIT=22 make -V CFLAGS -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\\\\\"/usr/local/www/data\\\\\" -DDEFAULT_PATH=\\\\\"/bin:/usr/bin:/usr/local/bin\\\\\" -DHARD_SERVER_LIMIT=22 From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 15:55:02 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7731B16A4E0 for ; Wed, 12 Jul 2006 15:55:02 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CDD243D79 for ; Wed, 12 Jul 2006 15:55:00 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1G0h38-000E8k-FI; Wed, 12 Jul 2006 19:54:54 +0400 Message-ID: <44B51B4F.8090805@FreeBSD.org> Date: Wed, 12 Jul 2006 19:54:55 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John E Hein References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> <44B4CDE3.60205@FreeBSD.org> <17589.1719.666455.768409@gromit.timing.com> In-Reply-To: <17589.1719.666455.768409@gromit.timing.com> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 15:55:02 -0000 John E Hein wrote: > This is incorrect. > make(1) looks at the environment for variables. > See the man page. OK, something really broke in portupgrade then. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 17:35:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6A50116A4E0 for ; Wed, 12 Jul 2006 17:35:22 +0000 (UTC) (envelope-from akosiaris@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28CF043D58 for ; Wed, 12 Jul 2006 17:35:21 +0000 (GMT) (envelope-from akosiaris@gmail.com) Received: by nz-out-0102.google.com with SMTP id 13so174487nzn for ; Wed, 12 Jul 2006 10:35:20 -0700 (PDT) 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=fBy1+cRHZbf5RG4cF3iGBT5DvCXaTakekdaCHefJMj29pNkbBpA5sCT79+g0rturDwMh5COT7fseb11QzjQhvPqyPWYDKHzq1fj5hY9J4Wz0VnwD+HDtQCbdjCJaU0b6UhCeU3WRWMf09yudP2u12J1Rn3ze/EQIxWVuEjQYgxc= Received: by 10.36.74.19 with SMTP id w19mr1194875nza; Wed, 12 Jul 2006 10:35:20 -0700 (PDT) Received: by 10.36.55.20 with HTTP; Wed, 12 Jul 2006 10:35:20 -0700 (PDT) Message-ID: Date: Wed, 12 Jul 2006 20:35:20 +0300 From: "Alexandros Kosiaris" To: "Giorgos Keramidas" In-Reply-To: <20060712141153.GB30855@gothmog.pc> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20060712141153.GB30855@gothmog.pc> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Securelevels and /dev/io documentation inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 17:35:22 -0000 > It looks like it does. Would something like this be satisfactory? > > 1 Secure mode - the system immutable and system > append-only flags may not be turned off; disks for > mounted file systems, /dev/mem and /dev/kmem may not be > opened for writing and /dev/io (if your platform has it) > may not be opened at all; kernel modules (see kld(4)) > may not be loaded or unloaded. > > Regards, > Giorgos > Yes it would be. Thank you. From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 17:53:10 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2CE7116A4DD; Wed, 12 Jul 2006 17:53:10 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90CBB43D55; Wed, 12 Jul 2006 17:53:09 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6CHr6N5096564 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Jul 2006 10:53:06 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B5389D.9020808@asd.aplus.net> Date: Wed, 12 Jul 2006 10:59:57 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: Sergey Matveychuk References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> <44B4CDE3.60205@FreeBSD.org> In-Reply-To: <44B4CDE3.60205@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@FreeBSD.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 17:53:10 -0000 Sergey Matveychuk said the following on 7/12/06 3:24 AM: > Atanas wrote: >> Sergey Matveychuk said the following on 7/11/2006 10:08 PM: >>> Atanas wrote: >>>> Recent portupgrade versions no longer obey the -M command line switch, >>>> i.e. any optional arguments to be prepended to each make command. >>>> >>>> How to reproduce: >>>> >>>> # portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 >>> Everything work file. Use -m for getting what you want. >>> >> For www/apache13 the -m switch could give the same result as -M would, >> but I'm not sure whether it's not just a coincidence. The -m switch was >> supposed to serve a different purpose: >> >> -m >> --make-args Specify arguments to append to each make(1) com- >> mand line. >> -M >> --make-env Specify arguments to prepend to each make(1) com- >> mand line. >> >> I tried testing another port where I used both: >> >> # portinstall -M 'WITH_SYSLOG_FACILITY=local5' -m '-DWITHOUT_IPV6' >> mail/courier-imap >> >> With portupgrade-2.0.1_1,1 (the stock 6.1-RELEASE package) it worked. >> With portupgrade-2.1.3.2,2 it failed (ignoring the -M part like for >> www/apache13 before). >> >> Then I joined both in one -m switch: >> >> # portinstall -m 'WITH_SYSLOG_FACILITY=local5 -DWITHOUT_IPV6' >> mail/courier-imap >> >> and the latest portupgrade-2.1.3.2,2 did it just fine. >> >> So, like you suggested, the -m switch seems to cover the functionality >> that -M used to provide. I'm not sure however whether this "prepend to >> append" conversion would work for all ports. But for these that I use it >> appears to work, so I have no problem and will update my scripts to use >> -m only. >> >> The no longer working (obsolete?) -M switch would need to be removed >> from the man page though. > > Both -m and -M works fine but do different things. -m pass its argument > as make file argument(s) and -M pass its argument as environment > variable(s). You can't set make variable with environment variable. They > are different! > Yes, I know that. That's why I quoted the man page in my previous post (see above). > -M has never worked as you expected. > I expected -M to work exactly as documented, like it has been doing so for years. > You can test it with a command: > %cd /usr/ports/www/apache13 > %env APACHE_HARD_SERVER_LIMIT=1024 make > Sure, the port build works: % cd /usr/ports/www/apache13 % env APACHE_HARD_SERVER_LIMIT=1024 make ===> src/os/unixcc -c -I../../os/unix -I../../include -I/usr/local/include -funsigned-char -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\"/usr/local/www/data\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=1024 `../../apaci` os.c while portupgrade -M fails: % portinstall -M "APACHE_HARD_SERVER_LIMIT=1024" www/apache13 ===> src/os/unixcc -c -I../../os/unix -I../../include -I/usr/local/include -funsigned-char -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\"/usr/local/www/data\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 `../../apaci` os.c > against of > % make APACHE_HARD_SERVER_LIMIT=1024 > This doesn't make much sense to me. Perhaps you meant: % make -DAPACHE_HARD_SERVER_LIMIT=1024 But I wouldn't expect this to succeed either: ===> src/os/unixcc -c -I../../os/unix -I../../include -I/usr/local/include -funsigned-char -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\"/usr/local/www/data\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=512 `../../apaci` os.c Your suggestion however (to replace -M with -m) surprisingly worked: cc -c -I../../os/unix -I../../include -I/usr/local/include -funsigned-char -O2 -fno-strict-aliasing -pipe -DDOCUMENT_LOCATION=\"/usr/local/www/data\" -DDEFAULT_PATH=\"/bin:/usr/bin:/usr/local/bin\" -DHARD_SERVER_LIMIT=1024 `../../apaci` os.c And this is what's confusing. > I think you confuse the two variables types. > No, I think I know what these are for. But trying your suggestion to replace -M with -m and finding it to work (for some ports?), just threw some more fog into the case. Let's say it clear again - I have found that all recent versions of portupgrade (2.1.0+) fail to obey the -M switch and ignore any optional port parameters (i.e. arguments to prepend to each make command line) supplied there. Please, don't get me wrong. I'm not asking for help or for a workaround. I'm actually trying to help identifying a problem or regression. If this is not a bug, but a feature change, please have it documented. What the portupgrade(1) man page says about the -M switch is incorrect, as it no longer prepends any arguments specified to each make(1) command line. Regards, Atanas From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 18:07:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 51EAC16A4DA for ; Wed, 12 Jul 2006 18:07:25 +0000 (UTC) (envelope-from freebsd@chillt.de) Received: from dd2718.kasserver.com (dd2718.kasserver.com [81.209.184.159]) by mx1.FreeBSD.org (Postfix) with ESMTP id E2CB743D45 for ; Wed, 12 Jul 2006 18:07:24 +0000 (GMT) (envelope-from freebsd@chillt.de) Received: from [127.0.0.1] (dslb-084-061-197-230.pools.arcor-ip.net [84.61.197.230]) by dd2718.kasserver.com (Postfix) with ESMTP id 334A2EE03B; Wed, 12 Jul 2006 20:07:19 +0200 (CEST) Message-ID: <44B53A58.3010302@chillt.de> Date: Wed, 12 Jul 2006 20:07:20 +0200 From: Bartosz Fabianowski User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: Max Laier References: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> <200607101756.37607.max@love2party.net> In-Reply-To: <200607101756.37607.max@love2party.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Vlad GALU Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 18:07:25 -0000 Since the iwi driver has been MFC'd, I cannot build a kernel any more. I csupped my src/sys to RELENG_6 a couple of hours ago. Everything compiles fine, but when linking the kernel, make barfs: linking kernel if_iwi.o(.text+0x29c4): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x29d3): In function `iwi_getfw': : undefined reference to `firmware_get' if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': : undefined reference to `firmware_put' if_iwi.o(.text+0x49a5): In function `iwi_init_locked': : undefined reference to `firmware_get' I have "device iwi" in my kernel configuration. Should I remove it and use a module instead? Or is this supposed to work? - Bartosz From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 18:12:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 527C116A580 for ; Wed, 12 Jul 2006 18:12:30 +0000 (UTC) (envelope-from vladgalu@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id CE3F743D45 for ; Wed, 12 Jul 2006 18:12:28 +0000 (GMT) (envelope-from vladgalu@gmail.com) Received: by nf-out-0910.google.com with SMTP id n15so126811nfc for ; Wed, 12 Jul 2006 11:12:27 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=napXWL60/Fq9iehpBc/zronMmv54bnddCUM4CoDMltZQHbBJhGqhO7WHMpc3gvengdzIF2mHfgAjES/fqQmRViFAooHxISZEwE/ksiCdh3JsAkj+oJqIWH9cUklumzl6Sc6NUCvjjpk4Z3+ooniYRb10J62HEdLl6IOm2BLDFjc= Received: by 10.48.161.1 with SMTP id j1mr1604nfe; Wed, 12 Jul 2006 11:12:26 -0700 (PDT) Received: by 10.48.239.9 with HTTP; Wed, 12 Jul 2006 11:12:26 -0700 (PDT) Message-ID: <79722fad0607121112g459c3511tc856758e07e188c9@mail.gmail.com> Date: Wed, 12 Jul 2006 21:12:26 +0300 From: "Vlad GALU" To: freebsd-stable@freebsd.org In-Reply-To: <44B53A58.3010302@chillt.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> <200607101756.37607.max@love2party.net> <44B53A58.3010302@chillt.de> Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 18:12:30 -0000 On 7/12/06, Bartosz Fabianowski wrote: > Since the iwi driver has been MFC'd, I cannot build a kernel any more. I > csupped my src/sys to RELENG_6 a couple of hours ago. Everything > compiles fine, but when linking the kernel, make barfs: > > linking kernel > if_iwi.o(.text+0x29c4): In function `iwi_getfw': > : undefined reference to `firmware_get' > if_iwi.o(.text+0x29d3): In function `iwi_getfw': > : undefined reference to `firmware_get' > if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': > : undefined reference to `firmware_put' > if_iwi.o(.text+0x49a5): In function `iwi_init_locked': > : undefined reference to `firmware_get' > > I have "device iwi" in my kernel configuration. Should I remove it and > use a module instead? Or is this supposed to work? > You need to add "device firmware" to your kernel configuration file as well. This driver uses the new firmware(9) framework. > - Bartosz > -- 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-stable@FreeBSD.ORG Wed Jul 12 18:14:45 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D938E16A4DF; Wed, 12 Jul 2006 18:14:45 +0000 (UTC) (envelope-from keramida@FreeBSD.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD25F43D55; Wed, 12 Jul 2006 18:14:35 +0000 (GMT) (envelope-from keramida@FreeBSD.org) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k6CIEMQa029850 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 12 Jul 2006 21:14:22 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k6CIEGja038993; Wed, 12 Jul 2006 21:14:16 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k6CIEGu6038992; Wed, 12 Jul 2006 21:14:16 +0300 (EEST) (envelope-from keramida@FreeBSD.org) Date: Wed, 12 Jul 2006 21:14:16 +0300 From: Giorgos Keramidas To: Alexandros Kosiaris Message-ID: <20060712181416.GB38615@gothmog.pc> References: <20060712141153.GB30855@gothmog.pc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-4.353, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.05, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-current@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: Securelevels and /dev/io documentation inconsistency X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 18:14:46 -0000 On 2006-07-12 20:35, Alexandros Kosiaris wrote: >>It looks like it does. Would something like this be satisfactory? >> >> 1 Secure mode - the system immutable and system >> append-only flags may not be turned off; disks for >> mounted file systems, /dev/mem and /dev/kmem may not be >> opened for writing and /dev/io (if your platform has it) >> may not be opened at all; kernel modules (see kld(4)) >> may not be loaded or unloaded. >> >>Regards, >>Giorgos > > Yes it would be. Thank you. It should be fixed in HEAD now, with this commit: Revision Changes Path 1.47 +4 -3 src/share/man/man7/security.7 After a short period (3 days or so), if there are no objections, corrections or other changes by fellow committers, I'll merge the change to RELENG_6 too. Thanks :) From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 18:28:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F84316A4DE for ; Wed, 12 Jul 2006 18:28:22 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 992E743D45 for ; Wed, 12 Jul 2006 18:28:21 +0000 (GMT) (envelope-from max@love2party.net) Received: from [88.64.180.59] (helo=amd64.laiers.local) by mrelayeu.kundenserver.de (node=mrelayeu4) with ESMTP (Nemesis), id 0ML21M-1G0jRb330Y-00051t; Wed, 12 Jul 2006 20:28:20 +0200 From: Max Laier Organization: FreeBSD To: Bartosz Fabianowski Date: Wed, 12 Jul 2006 20:28:12 +0200 User-Agent: KMail/1.9.1 References: <79722fad0607100740q16492166m3cf644f3134bcd8f@mail.gmail.com> <200607101756.37607.max@love2party.net> <44B53A58.3010302@chillt.de> In-Reply-To: <44B53A58.3010302@chillt.de> X-Face: ,,8R(x[kmU]tKN@>gtH1yQE4aslGdu+2]; R]*pL,U>^H?)gW@49@wdJ`H<=?utf-8?q?=25=7D*=5FBD=0A=09U=5For=3D=5CmOZf764=26nYj=3DJYbR1PW0ud?=>|!~,,CPC.1-D$FG@0h3#'5"k{V]a~.<=?utf-8?q?mZ=7D44=23Se=7Em=0A=09Fe=7E=5C=5DX5B=5D=5Fxj?=(ykz9QKMw_l0C2AQ]}Ym8)fU MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7715067.8pDgtPMssn"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607122028.18913.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: freebsd-stable@freebsd.org, Vlad GALU Subject: Re: iwi(4) in RELENG_6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 18:28:22 -0000 --nextPart7715067.8pDgtPMssn Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 12 July 2006 20:07, Bartosz Fabianowski wrote: > Since the iwi driver has been MFC'd, I cannot build a kernel any more. I > csupped my src/sys to RELENG_6 a couple of hours ago. Everything > compiles fine, but when linking the kernel, make barfs: > > linking kernel > > if_iwi.o(.text+0x29c4): In function `iwi_getfw': > : undefined reference to `firmware_get' > > if_iwi.o(.text+0x29d3): In function `iwi_getfw': > : undefined reference to `firmware_get' > > if_iwi.o(.text+0x2a1d): In function `iwi_put_fw': > : undefined reference to `firmware_put' > > if_iwi.o(.text+0x49a5): In function `iwi_init_locked': > : undefined reference to `firmware_get' > > I have "device iwi" in my kernel configuration. Should I remove it and > use a module instead? Or is this supposed to work? This is from the firmware(9) support code. Add "options firmware" and you= =20 should be fine. You will still need to load the firmware blobs as modules,= =20 but that's another story. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart7715067.8pDgtPMssn Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQBEtT9CXyyEoT62BG0RAs1XAJ4jNn2+ygsoSepSQzn4qr5+IRMmLwCbBljU xV1Kk7N5QvR+Pf5ALIdLxvc= =aDfv -----END PGP SIGNATURE----- --nextPart7715067.8pDgtPMssn-- From owner-freebsd-stable@FreeBSD.ORG Wed Jul 12 18:55:45 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7718016A4DE for ; Wed, 12 Jul 2006 18:55:45 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 958E843D69 for ; Wed, 12 Jul 2006 18:55:41 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1G0jrS-00039u-EE for freebsd-stable@freebsd.org; Wed, 12 Jul 2006 20:55:02 +0200 Received: from sdgate2.cvjetno.sczg.hr ([193.198.8.211]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Jul 2006 20:55:02 +0200 Received: from ivoras by sdgate2.cvjetno.sczg.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 12 Jul 2006 20:55:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Wed, 12 Jul 2006 20:45:02 +0200 Lines: 20 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: sdgate2.cvjetno.sczg.hr User-Agent: Thunderbird 1.5.0.4 (X11/20060615) Sender: news Subject: cpufreq not working on AMD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jul 2006 18:55:45 -0000 Loading cpufreq.ko results in these messages: powernow0: on cpu0 device_attach: powernow0 attach returned 6 powernow0: on cpu0 device_attach: powernow0 attach returned 6 I've googled for it - there are many similar problems but no solution. This is: CPU: AMD Athlon(tm) 64 Processor 3000+ (1795.32-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 Features=0x78bfbff Features2=0x1 AMD Features=0xe2500800 AMD Features2=0x1 in i386 mode, and setting cpu frequency works in Windows. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 04:09:11 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C940016A4DA for ; Thu, 13 Jul 2006 04:09:11 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C6D243D45 for ; Thu, 13 Jul 2006 04:09:11 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 12 Jul 2006 21:07:26 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id k6D49Aic071483; Wed, 12 Jul 2006 21:09:10 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id k6D49Ajk071482; Wed, 12 Jul 2006 21:09:10 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200607130409.k6D49Ajk071482@ambrisko.com> In-Reply-To: <20060706183253.GC61190@abcjr.net> To: "Arnold Cavazos Jr." Date: Wed, 12 Jul 2006 21:09:10 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: freebsd-stable@freebsd.org Subject: Re: Dell PowerEdge 750 & 850 environtmental monitoring X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 04:09:11 -0000 Arnold Cavazos Jr. writes: | Does anybody have temperature and fan monitoring working on Dell | PowerEdge 750's & 850's? I have done my share of googling without much | luck. The PE850 should just work with ipmi(4) in 6.1-stable/-current and ipmitool. The PE750 will work with ipmi if you have the Drac card. It is possible to get thermal stuff on the PE750 via smbus but that is more complicated. Doug A. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 05:13:31 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A067D16A4E0; Thu, 13 Jul 2006 05:13:31 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0084843D46; Thu, 13 Jul 2006 05:13:30 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail.ambrisko.com with ESMTP; 12 Jul 2006 22:11:46 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.13.1/8.12.11) with ESMTP id k6D5DTcP074873; Wed, 12 Jul 2006 22:13:29 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.13.1/8.13.1/Submit) id k6D5DTdb074868; Wed, 12 Jul 2006 22:13:29 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200607130513.k6D5DTdb074868@ambrisko.com> In-Reply-To: <09BFF2FA5EAB4A45B6655E151BBDD903018924E0@NT-IRVA-0750.brcm.ad.broadcom.com> To: "David (Controller AE) Christensen" Date: Wed, 12 Jul 2006 22:13:29 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Cc: pyunyh@gmail.com, stable@freebsd.org, davidch@freebsd.org, Eric Hodel Subject: Re: bce0: Error mapping mbuf into TX chain! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 05:13:31 -0000 David (Controller AE) Christensen writes: | Sorry, I've been out on vacation and just got back into town. I'll MFC | the patch within the next day or two. I'll let you merge in the down/up fix that I put into -current. Doug A. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 05:29:47 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 89F1616A4DE for ; Thu, 13 Jul 2006 05:29:47 +0000 (UTC) (envelope-from pinoyskull@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2410B43D46 for ; Thu, 13 Jul 2006 05:29:45 +0000 (GMT) (envelope-from pinoyskull@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so43086nzh for ; Wed, 12 Jul 2006 22:29:44 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type:content-transfer-encoding; b=gMpMQU38cTY4AUopuSxO2HkIpeDY2Huq8hL07axQuURZizabYj1/STpZK0mZZeUcdgcaji0orEv1Q4EjEEiisjvgVHG7TcGaGKaauUB5Edsda/ox9oljAK45N5KNYhNPL627amjqzUmwvF1rtIiWAVurl5O87ylU5JiU70rFfLs= Received: by 10.36.113.8 with SMTP id l8mr615604nzc; Wed, 12 Jul 2006 22:29:44 -0700 (PDT) Received: from ?202.70.97.6? ( [202.70.97.6]) by mx.gmail.com with ESMTP id c12sm1305606nzc.2006.07.12.22.29.43; Wed, 12 Jul 2006 22:29:44 -0700 (PDT) Message-ID: <44B5DA43.8030505@gmail.com> Date: Thu, 13 Jul 2006 13:29:39 +0800 From: pinoyskull User-Agent: Thunderbird 1.5.0.4 (X11/20060615) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: missing mod_php4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 05:29:47 -0000 Hi, Im trying to install Apache+ssl succesfully then i want to add mod_php4, the problem is, it is missing, /usr/ports/www/mod_php4 is non-existent, i tried running cvsup again just to make sure there's no error, but still it is missing. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 05:32:55 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B79EE16A4E8 for ; Thu, 13 Jul 2006 05:32:55 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from kagate.punkt.de (kagate.punkt.de [217.29.33.131]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4670043D58 for ; Thu, 13 Jul 2006 05:32:37 +0000 (GMT) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate2.punkt.de with ESMTP id k6D5WaM5003166 for ; Thu, 13 Jul 2006 07:32:36 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.12.10/8.12.10) with ESMTP id k6D5Wa6G053111; Thu, 13 Jul 2006 07:32:36 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.12.10/8.12.10/Submit) id k6D5WZ3p053110; Thu, 13 Jul 2006 07:32:35 +0200 (CEST) (envelope-from ry93) Date: Thu, 13 Jul 2006 07:32:35 +0200 From: "Patrick M. Hausen" To: pinoyskull Message-ID: <20060713053235.GA53077@hugo10.ka.punkt.de> References: <44B5DA43.8030505@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B5DA43.8030505@gmail.com> User-Agent: Mutt/1.5.10i Cc: freebsd-stable@freebsd.org Subject: Re: missing mod_php4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 05:32:55 -0000 Hi! > Im trying to install Apache+ssl succesfully then i want to add mod_php4, > the problem is, it is missing, /usr/ports/www/mod_php4 is non-existent, > i tried running cvsup again just to make sure there's no error, but > still it is missing. The php ports have been reorganized and cleaned up (IMHO for the better) - see /usr/ports/lang/php4 HTH, Patrick M. Hausen Leiter Netzwerke und Sicherheit -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25 Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 05:51:38 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2916B16A4EC for ; Thu, 13 Jul 2006 05:51:38 +0000 (UTC) (envelope-from pinoyskull@gmail.com) Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8CC1943D49 for ; Thu, 13 Jul 2006 05:51:31 +0000 (GMT) (envelope-from pinoyskull@gmail.com) Received: by nz-out-0102.google.com with SMTP id i11so44171nzh for ; Wed, 12 Jul 2006 22:51:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type; b=TyVftBxI3NHwKR2gmDSjCzRr6ivfp2Kq++NEyi3Ntwy+QVnhXiUz8m9eONKguSFfSxO5rq3UORL0SVTjd52JLj+KWvmbniUUE77guWxCv0/JCo5Jh4Syr8BnYzP1/YlV/3xgdGSaj9HYxGUIvwpt5/lbLmliLkAKuc6bCZLNVdw= Received: by 10.36.139.3 with SMTP id m3mr644314nzd; Wed, 12 Jul 2006 22:51:31 -0700 (PDT) Received: from ?202.70.97.6? ( [202.70.97.6]) by mx.gmail.com with ESMTP id 37sm863997nzf.2006.07.12.22.51.28; Wed, 12 Jul 2006 22:51:29 -0700 (PDT) Message-ID: <44B5DF5D.80106@gmail.com> Date: Thu, 13 Jul 2006 13:51:25 +0800 From: pinoyskull User-Agent: Thunderbird 1.5.0.4 (X11/20060615) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <44B5DA43.8030505@gmail.com> <20060713053235.GA53077@hugo10.ka.punkt.de> In-Reply-To: <20060713053235.GA53077@hugo10.ka.punkt.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: missing mod_php4 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 05:51:38 -0000 Patrick M. Hausen wrote: > Hi! > > >> Im trying to install Apache+ssl succesfully then i want to add mod_php4, >> the problem is, it is missing, /usr/ports/www/mod_php4 is non-existent, >> i tried running cvsup again just to make sure there's no error, but >> still it is missing. >> > > The php ports have been reorganized and cleaned up (IMHO > for the better) - see > > /usr/ports/lang/php4 > > HTH, > > Patrick M. Hausen > Leiter Netzwerke und Sicherheit > thanks From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 05:57:51 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 22DE716A4DA for ; Thu, 13 Jul 2006 05:57:51 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5A1BB43D45 for ; Thu, 13 Jul 2006 05:57:50 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1G0uCm-000CzL-H0; Thu, 13 Jul 2006 09:57:44 +0400 Message-ID: <44B5E0D8.1030000@FreeBSD.org> Date: Thu, 13 Jul 2006 09:57:44 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: Atanas References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> <44B4CDE3.60205@FreeBSD.org> <44B5389D.9020808@asd.aplus.net> In-Reply-To: <44B5389D.9020808@asd.aplus.net> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 05:57:51 -0000 Atanas wrote: > Please, don't get me wrong. I'm not asking for help or for a workaround. > I'm actually trying to help identifying a problem or regression. > > If this is not a bug, but a feature change, please have it documented. It was a bug. Fixed. Thanks. -- Dixi. Sem. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 10:10:17 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A0CF16A4DA for ; Thu, 13 Jul 2006 10:10:17 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout1-sn2.hy.skanova.net (pne-smtpout1-sn2.hy.skanova.net [81.228.8.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id DB30743D45 for ; Thu, 13 Jul 2006 10:10:16 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout1-sn2.hy.skanova.net (7.2.075) id 44A2E86F002E1A83 for freebsd-stable@freebsd.org; Thu, 13 Jul 2006 12:10:15 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id B7B4861D51 for ; Thu, 13 Jul 2006 12:10:14 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WllgMts8+gRJ for ; Thu, 13 Jul 2006 12:10:13 +0200 (CEST) Received: from [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01] (unknown [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01]) by elfi.stromnet.org (Postfix) with ESMTP id 3ABB361D53 for ; Thu, 13 Jul 2006 12:10:13 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v750) In-Reply-To: <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Thu, 13 Jul 2006 12:10:30 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.750) Subject: Re: GEOM problems again... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 10:10:17 -0000 On 10 jul 2006, at 13.59, Johan Str=F6m wrote: > > On 10 jul 2006, at 11.09, Johan Str=F6m wrote: > >> >> On 21 maj 2006, at 11.16, Johan Str=F6m wrote: >> >>> Hi >>> >>> I've had problems before with GEOM mirror and my SATA drives, and =20= >>> i've posted about it here before too. The solution seemd to be a =20 >>> change of motherboard, this reduced the crash very much (and also =20= >>> the speeds archieved was greatly improved, from 10-15MB/s to =20 >>> 40-50MB/s..). >>> However after the change i had one or two crashes, but now it has =20= >>> been running for well over 50-60 days or so without any problems. >>> Then, 11 days ago I upgraded to 6.1... And now I got these =20 >>> "crashe"s again (the mirror is crashed that is, the system still =20 >>> runs fine): >>> >>> May 21 02:04:58 elfi kernel: ad6: FAILURE - device detached >>> May 21 02:04:58 elfi kernel: subdisk6: detached >>> May 21 02:04:58 elfi kernel: ad6: detached >>> May 21 02:04:58 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> ad6s1 disconnected. >>> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >>> (offset=3D11006308352, length=3D2048)]error =3D 6 >>> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >>> (offset=3D164847927296, length=3D131072)]error =3D 6 >>> May 21 02:04:58 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >>> (offset=3D256680296448, length=3D32768)]error =3D 6 >>> >>> >>> Some info about the controller and disks: >>> >>> May 9 22:46:52 elfi kernel: ata1: on atapci0 >>> May 9 22:46:52 elfi kernel: atapci1: >> controller> port =20 >>> 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0x7f00-0x7f0=20= >>> f,0x7c0 >>> 0-0x7c7f irq 22 at device 11.0 on pci0 >>> >>> May 9 22:46:52 elfi kernel: ad4: 286188MB >> BANC1G10> at ata2-master SATA150 >>> May 9 22:46:52 elfi kernel: ad6: 286188MB >> BANC1G10> at ata3-master SATA150 >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1 created =20 >>> (id=3D4118114647). >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> ad4s1 detected. >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> ad6s1 detected. >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> ad6s1 activated. >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> ad4s1 activated. >>> May 9 22:46:52 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >>> mirror/gm0s1 launched. >>> May 9 22:46:52 elfi kernel: Trying to mount root from ufs:/dev/=20 >>> mirror/gm0s1a >>> >>> Anyone got any new clues? Afaik the disks should be working fine =20 >>> (they are 6 months old and this same problem has occured multiple =20= >>> times...) >>> >>> Hope to solve this ;) >>> >>> Thanks >>> Johan >>> >> >> Here we go again >> >> Jul 7 16:20:09 elfi kernel: ad4: FAILURE - device detached >> Jul 7 16:20:09 elfi kernel: subdisk4: detached >> Jul 7 16:20:09 elfi kernel: ad4: detached >> Jul 7 16:20:09 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad4s1 disconnected. >> Jul 7 16:20:09 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >> (offset=3D88896847872, length=3D32768)]error =3D 6 >> >> However no read read timeouts etc as before, just this. 18 days =20 >> uptime this time (i've rebooted for other reasons since last =20 >> mail). It always seems to be ad4 that is disconnecting.. I'm going =20= >> to do some disk tests on it but i doubt it will give anything =20 >> since i've had similiar problems from day one (did tests at that =20 >> time w/o problems) with this gmirror setup (new disks). >> >> Johan > > Followup, I ran over the disk with Maxtors own test program, full =20 > length test. Not a single problem. > After reboot the raid is rebuilding fine: > > GEOM_MIRROR: Device gm0s1: rebuilding provider ad4s1. > > As usual it seems i cannot get the controller/driver to redetect =20 > the disk using atacontrol etc.. > > Johan And now again... raid gone degraded only 2 days after reboot! Jul 12 22:22:50 elfi kernel: ad4: FAILURE - device detached Jul 12 22:22:50 elfi kernel: subdisk4: detached Jul 12 22:22:50 elfi kernel: ad4: detached Jul 12 22:22:50 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 ad4s1 disconnected. Jul 12 22:22:50 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 (offset=3D120776474624, length=3D32768)]error =3D 6 $ uname -a FreeBSD elfi.stromnet.org 6.1-RELEASE FreeBSD 6.1-RELEASE #3: Tue =20 May 9 20:40:23 CEST 2006 johan@elfi.stromnet.org:/usr/obj/usr/src/=20 sys/GENERIC i386 Still no luck with atacontrol... Is there any way to debug this further ?? I've tested the disk, the =20 SATA cables are new... I've had similar problems with other =20 motherboard... I dont think this is related to hw problems, but rather a =20 softwareproblem that needs to be solved, this is not something one =20 can call stable ;) So, any pointers how to enable more debugging or anything that could =20 give some clues? Johan From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 10:16:50 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3FEFB16A4DA for ; Thu, 13 Jul 2006 10:16:50 +0000 (UTC) (envelope-from ducrot@poupinou.org) Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96]) by mx1.FreeBSD.org (Postfix) with ESMTP id E233843D45 for ; Thu, 13 Jul 2006 10:16:49 +0000 (GMT) (envelope-from ducrot@poupinou.org) Received: from ducrot by poup.poupinou.org with local (Exim) id 1G0yFU-0000Ep-00; Thu, 13 Jul 2006 12:16:48 +0200 Date: Thu, 13 Jul 2006 12:16:48 +0200 To: Ivan Voras Message-ID: <20060713101648.GJ17014@poupinou.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i From: Bruno Ducrot Cc: freebsd-stable@freebsd.org Subject: Re: cpufreq not working on AMD X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 10:16:50 -0000 Hi, On Wed, Jul 12, 2006 at 08:45:02PM +0200, Ivan Voras wrote: > Loading cpufreq.ko results in these messages: > > powernow0: on cpu0 > device_attach: powernow0 attach returned 6 > powernow0: on cpu0 > device_attach: powernow0 attach returned 6 > > I've googled for it - there are many similar problems but no solution. > > This is: > > CPU: AMD Athlon(tm) 64 Processor 3000+ (1795.32-MHz 686-class CPU) > Origin = "AuthenticAMD" Id = 0x20ff0 Stepping = 0 > > Features=0x78bfbff > Features2=0x1 > AMD Features=0xe2500800 > AMD Features2=0x1 > > in i386 mode, and setting cpu frequency works in Windows. Is acpi loaded on that system? Could you please provide a dmesg after a boot -v? Cheers, -- Bruno Ducrot -- Which is worse: ignorance or apathy? -- Don't know. Don't care. From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 12:23:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6C0516A4DA for ; Thu, 13 Jul 2006 12:23:16 +0000 (UTC) (envelope-from dennis.melentyev@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 875F143D49 for ; Thu, 13 Jul 2006 12:23:13 +0000 (GMT) (envelope-from dennis.melentyev@gmail.com) Received: by ug-out-1314.google.com with SMTP id o2so255505uge for ; Thu, 13 Jul 2006 05:23:12 -0700 (PDT) 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:references; b=jCtzONJJ2VcYKPGng6I/49RiI7abXLJIFdcYGxGqXawyOg7jY1q9Xu31l1q4cvF/rQ48OVZ0Kpr1k2QhjymXbhBZulwS/ESvNASWNY6Fc+KoFlQ7EBDZTITp7IST6lJ2LRuJ8XRSg2+SdDQMDDwqU32p7q753ZfmYsxjhMoMYtc= Received: by 10.78.177.11 with SMTP id z11mr489946hue; Thu, 13 Jul 2006 05:23:12 -0700 (PDT) Received: by 10.78.136.9 with HTTP; Thu, 13 Jul 2006 05:23:11 -0700 (PDT) Message-ID: Date: Thu, 13 Jul 2006 15:23:11 +0300 From: "Dennis Melentyev" To: "Mihir Sanghavi" In-Reply-To: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> MIME-Version: 1.0 References: <11419abd0607110949j441ad8a8u803768fbaa131ddf@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 12:23:16 -0000 2006/7/11, Mihir Sanghavi : > > Hi, > I have installed firefox using pkg_add -r firefox > and now want to use xterm > > i tried using xterm and it says: Cannot open display > and display not set Exit root shell back to user's one. -- > What we see depends mainly on what we look for. > -MIHIR > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Dennis Melentyev From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 12:26:30 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 318FA16A531 for ; Thu, 13 Jul 2006 12:26:30 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 86ABE43E1C for ; Thu, 13 Jul 2006 12:26:05 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 133FE46B0E; Thu, 13 Jul 2006 08:26:05 -0400 (EDT) Date: Thu, 13 Jul 2006 13:26:04 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: =?ISO-8859-1?Q?Johan_Str=F6m?= In-Reply-To: <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> Message-ID: <20060713132357.Y61840@fledge.watson.org> References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1838797900-1152793564=:61840" Cc: freebsd-stable@freebsd.org Subject: ATA problems again ... (was: Re: GEOM problems again...) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 12:26:30 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-1838797900-1152793564=:61840 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Thu, 13 Jul 2006, Johan Str=F6m wrote: > And now again... raid gone degraded only 2 days after reboot! > > Jul 12 22:22:50 elfi kernel: ad4: FAILURE - device detached > Jul 12 22:22:50 elfi kernel: subdisk4: detached > Jul 12 22:22:50 elfi kernel: ad4: detached > Jul 12 22:22:50 elfi kernel: GEOM_MIRROR: Device gm0s1: provider ad4s1=20 > disconnected. > Jul 12 22:22:50 elfi kernel:=20 > g_vfs_done():mirror/gm0s1f[READ(offset=3D120776474624, length=3D32768)]er= ror =3D 6 > > $ uname -a > FreeBSD elfi.stromnet.org 6.1-RELEASE FreeBSD 6.1-RELEASE #3: Tue May 9= =20 > 20:40:23 CEST 2006 johan@elfi.stromnet.org:/usr/obj/usr/src/sys/GENERIC = i386 > > Still no luck with atacontrol... > > Is there any way to debug this further ?? I've tested the disk, the SATA= =20 > cables are new... I've had similar problems with other motherboard... I d= ont=20 > think this is related to hw problems, but rather a softwareproblem that= =20 > needs to be solved, this is not something one can call stable ;) > > So, any pointers how to enable more debugging or anything that could give= =20 > some clues? I don't have a whole lot to add to this thread, but have changed the subjec= t=20 to make sure that the right people are reading this. This is likely either= a=20 hardware problem (motherboard/cable/drive) or driver problem. GEOM and the= =20 mirror driver seems to be behaving as desired (it detaches a drive reported= by=20 the driver as being bad). Could you post the dmesg -v output for the probi= ng=20 of the ata controller and driver? Robert N M Watson Computer Laboratory University of Cambridge --0-1838797900-1152793564=:61840-- From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 15:30:24 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66D6016A4EE for ; Thu, 13 Jul 2006 15:30:24 +0000 (UTC) (envelope-from dom@helenmarks.co.uk) Received: from mail.goodforbusiness.co.uk (mail.goodforbusiness.co.uk [81.19.179.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6A74343D73 for ; Thu, 13 Jul 2006 15:29:25 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id 4014D11462 for ; Thu, 13 Jul 2006 16:29:22 +0100 (BST) X-Virus-Scanned: mail.goodforbusiness.co.uk Received: from mail.goodforbusiness.co.uk ([127.0.0.1]) by localhost (mail.goodforbusiness.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zldSTxrmiMwu for ; Thu, 13 Jul 2006 16:29:22 +0100 (BST) Received: from mail.helenmarks.co.uk (unknown [192.168.100.1]) by mail.goodforbusiness.co.uk (Postfix) with ESMTP id DBCFB1141E for ; Thu, 13 Jul 2006 16:29:21 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 8BA591714D; Thu, 13 Jul 2006 16:29:21 +0100 (BST) X-Virus-Scanned: amavisd-new at helenmarks.co.uk Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VL7LX6cBix5P; Thu, 13 Jul 2006 16:29:20 +0100 (BST) Received: by mail.helenmarks.co.uk (Postfix, from userid 80) id 152C0170EB; Thu, 13 Jul 2006 16:29:20 +0100 (BST) Received: from mailhost.graphdata.co.uk ([195.12.22.194]) (SquirrelMail authenticated user dom) by mail.helenmarks.co.uk with HTTP; Thu, 13 Jul 2006 16:29:20 +0100 (BST) Message-ID: <3049.195.12.22.194.1152804560.squirrel@mail.helenmarks.co.uk> Date: Thu, 13 Jul 2006 16:29:20 +0100 (BST) From: "Dominic Marks" To: freebsd-stable@freebsd.org User-Agent: SquirrelMail/1.4.6 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: ACPI related crash on a Dell PowerEdge SC1420 regression since 6.1-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 15:30:24 -0000 Hello, I upgraded a PowerEdge SC1420 which had been installed with 6.1-R to 6.1-S today and now it no longer boots with ACPI enabled. It doesn't give a crash dump so here is the information I managed to note down before it rebooted: This happens after em and twe in the boot process. FVA 0x20:0xc0afce73 SP 0x28:0xc0c20944 FP 0x28:0xc0c20958 Trap 12 in swapper. I've no idea how useful this information is, hopeful it is a clue. Full dmesg below (from a non-ACPI boot, of course), please let me know if there is any other information I can provide. Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #0: Thu Jul 13 15:22:54 UTC 2006 dom@gdc083.internal.graphdata.co.uk:/usr/obj/usr/src/sys/GENERIC Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 3.00GHz (2992.52-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf4a Stepping = 10 Features=0xbfebfbff Features2=0x641d> AMD Features=0x20100000 AMD Features2=0x1 Logical CPUs per core: 2 real memory = 1072218112 (1022 MB) avail memory = 1040330752 (992 MB) MPTable: ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic1: Changing APIC ID to 9 ioapic1: Assuming intbase of 24 ioapic2: Changing APIC ID to 10 ioapic2: Assuming intbase of 48 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard ioapic2 irqs 48-71 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) cpu0 on motherboard pcib0: pcibus 0 on motherboard pci0: on pcib0 pcib0: unable to route slot 2 INTA pcib0: unable to route slot 3 INTA pcib0: unable to route slot 4 INTA pci0: at device 0.1 (no driver attached) pcib1: irq 11 at device 2.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 pci2: at device 12.0 (no driver attached) pcib3: at device 0.2 on pci1 pci3: on pcib3 twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xccb0-0xccbf mem 0xdd800000-0xddffffff irq 49 at device 13.0 on pci3 twe0: [GIANT-LOCKED] twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 em0: port 0xccc0-0xccff mem 0xdd6e0000-0xdd6fffff irq 48 at device 14.0 on pci3 em0: Ethernet address: 00:13:72:8b:3c:a9 pcib4: irq 11 at device 3.0 on pci0 pci4: on pcib4 pcib5: irq 11 at device 4.0 on pci0 pci5: on pcib5 uhci0: port 0xff80-0xff9f irq 16 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xff60-0xff7f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xff40-0xff5f irq 18 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered uhci3: port 0xff20-0xff3f irq 16 at device 29.3 on pci0 uhci3: [GIANT-LOCKED] usb3: on uhci3 usb3: USB revision 1.0 uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub3: 2 ports with 2 removable, self powered ehci0: mem 0xffa80800-0xffa80bff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb4: waiting for BIOS to give up control usb4: EHCI version 1.0 usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3 usb4: on ehci0 usb4: USB revision 2.0 uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub4: 8 ports with 8 removable, self powered umass0: FREECOM. ATAPI-6 Bridge Controller, rev 2.00/0.00, addr 2 umass1: Freecom Classic Mobile 2.5' Hard Disk, rev 2.00/0.33, addr 3 pcib6: at device 30.0 on pci0 pci6: on pcib6 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf mem 0xdffffc00-0xdfffffff irq 18 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xfe00-0xfe07,0xfe10-0xfe13,0xfe20-0xfe27,0xfe30-0xfe33,0xfea0-0xfeaf irq 18 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 pci0: at device 31.3 (no driver attached) pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff,0xc8800-0xc9fff,0xca000-0xcbfff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 unknown: can't assign resources (memory) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) ukbd0: Dell Dell USB Keyboard, rev 1.10/2.00, addr 2, iclass 3/1 kbd2 at ukbd0 ums0: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), rev 1.10/3.00, addr 3, iclass 3/1 ums0: 5 buttons and Z dir. Timecounter "TSC" frequency 2992515172 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata1-master UDMA33 ad4: 76293MB at ata2-master SATA150 da1 at umass-sim1 bus 1 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: 40.000MB/s transfers da1: 28615MB (58605120 512 byte sectors: 255H 63S/T 3648C) da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 38154MB (78140160 512 byte sectors: 255H 63S/T 4864C) Trying to mount root from ufs:/dev/ad4s1a Thanks! Dominic From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 16:58:56 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AF38416A4E1; Thu, 13 Jul 2006 16:58:56 +0000 (UTC) (envelope-from atanas@asd.aplus.net) Received: from pro20.abac.com (pro20.abac.com [66.226.64.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D28E943D8E; Thu, 13 Jul 2006 16:58:49 +0000 (GMT) (envelope-from atanas@asd.aplus.net) Received: from [216.55.129.5] (asd2.aplus.net [216.55.129.5]) (authenticated bits=0) by pro20.abac.com (8.13.6/8.13.6) with ESMTP id k6DGwjC5023599 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 13 Jul 2006 09:58:46 -0700 (PDT) (envelope-from atanas@asd.aplus.net) Message-ID: <44B67D6A.7030308@asd.aplus.net> Date: Thu, 13 Jul 2006 10:05:46 -0700 From: Atanas User-Agent: Thunderbird 1.5.0.4 (Macintosh/20060516) MIME-Version: 1.0 To: Sergey Matveychuk References: <44B40863.9060403@asd.aplus.net> <44B483B8.6000005@FreeBSD.org> <44B4A164.50003@asd.aplus.net> <44B4CDE3.60205@FreeBSD.org> <44B5389D.9020808@asd.aplus.net> <44B5E0D8.1030000@FreeBSD.org> In-Reply-To: <44B5E0D8.1030000@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 1.47 (SPF_SOFTFAIL) Cc: freebsd-stable@FreeBSD.org Subject: Re: portupgrade bug: -M no longer works after v2.1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 16:58:56 -0000 Sergey Matveychuk said the following on 7/12/06 10:57 PM: > Atanas wrote: >> Please, don't get me wrong. I'm not asking for help or for a workaround. >> I'm actually trying to help identifying a problem or regression. >> >> If this is not a bug, but a feature change, please have it documented. > > It was a bug. Fixed. Thanks. > Thank you! Atanas From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 17:19:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D235D16A4DD; Thu, 13 Jul 2006 17:19:35 +0000 (UTC) (envelope-from johan@stromnet.org) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2DA6E43D49; Thu, 13 Jul 2006 17:19:34 +0000 (GMT) (envelope-from johan@stromnet.org) Received: from elfi.stromnet.org (213.67.205.103) by pne-smtpout2-sn2.hy.skanova.net (7.2.075) id 44A2F19F002F7129; Thu, 13 Jul 2006 19:19:34 +0200 Received: from localhost (localhost [127.0.0.1]) by elfi.stromnet.org (Postfix) with ESMTP id 1DBAB61D51; Thu, 13 Jul 2006 19:19:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at stromnet.org Received: from elfi.stromnet.org ([127.0.0.1]) by localhost (elfi.stromnet.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X42dSLngr8nD; Thu, 13 Jul 2006 19:19:31 +0200 (CEST) Received: from [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01] (unknown [IPv6:2001:16d8:ff20:2:211:24ff:fea2:8e01]) by elfi.stromnet.org (Postfix) with ESMTP id 2122761D1B; Thu, 13 Jul 2006 19:19:31 +0200 (CEST) In-Reply-To: <20060713132357.Y61840@fledge.watson.org> References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> <20060713132357.Y61840@fledge.watson.org> Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: =?ISO-8859-1?Q?Johan_Str=F6m?= Date: Thu, 13 Jul 2006 19:19:48 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.750) Cc: Robert Watson Subject: Re: ATA problems again ... (was: Re: GEOM problems again...) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 17:19:36 -0000 On 13 jul 2006, at 14.26, Robert Watson wrote: > > On Thu, 13 Jul 2006, Johan Str=F6m wrote: > >> And now again... raid gone degraded only 2 days after reboot! >> >> Jul 12 22:22:50 elfi kernel: ad4: FAILURE - device detached >> Jul 12 22:22:50 elfi kernel: subdisk4: detached >> Jul 12 22:22:50 elfi kernel: ad4: detached >> Jul 12 22:22:50 elfi kernel: GEOM_MIRROR: Device gm0s1: provider =20 >> ad4s1 disconnected. >> Jul 12 22:22:50 elfi kernel: g_vfs_done():mirror/gm0s1f[READ=20 >> (offset=3D120776474624, length=3D32768)]error =3D 6 >> >> $ uname -a >> FreeBSD elfi.stromnet.org 6.1-RELEASE FreeBSD 6.1-RELEASE #3: Tue =20 >> May 9 20:40:23 CEST 2006 johan@elfi.stromnet.org:/usr/obj/usr/src/=20= >> sys/GENERIC i386 >> >> Still no luck with atacontrol... >> >> Is there any way to debug this further ?? I've tested the disk, =20 >> the SATA cables are new... I've had similar problems with other =20 >> motherboard... I dont think this is related to hw problems, but =20 >> rather a softwareproblem that needs to be solved, this is not =20 >> something one can call stable ;) >> >> So, any pointers how to enable more debugging or anything that =20 >> could give some clues? > > I don't have a whole lot to add to this thread, but have changed =20 > the subject to make sure that the right people are reading this. =20 > This is likely either a hardware problem (motherboard/cable/drive) =20 > or driver problem. GEOM and the mirror driver seems to be behaving =20= > as desired (it detaches a drive reported by the driver as being =20 > bad). Could you post the dmesg -v output for the probing of the =20 > ata controller and driver? dmesg -v? I got the full dmesg from dmesg.boot (this has been posted earlier in =20= this thread too) Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights =20 reserved. FreeBSD 6.1-RELEASE #3: Tue May 9 20:40:23 CEST 2006 johan@elfi.stromnet.org:/usr/obj/usr/src/sys/GENERIC ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP (1200.01-MHz 686-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x662 Stepping =3D 2 =20 Features=3D0x383fbff AMD Features=3D0xc0480800 real memory =3D 536674304 (511 MB) avail memory =3D 515805184 (491 MB) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf8000000-0xfbffffff at =20 device 0.0 on pci0 pci0: at device 0.1 (no driver attached) pci0: at device 0.2 (no driver attached) pci0: at device 0.3 (no driver attached) pci0: at device 0.4 (no driver attached) pci0: at device 0.5 (no driver attached) isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.1 (no driver attached) ohci0: mem 0xfebfb000-0xfebfbfff irq =20 20 at device 2.0 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ohci1: mem 0xfebfc000-0xfebfcfff irq =20 21 at device 2.1 on pci0 ohci1: [GIANT-LOCKED] usb1: OHCI version 1.0, legacy support usb1: on ohci1 usb1: USB revision 1.0 uhub1: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 4 ports with 4 removable, self powered ehci0: mem =20 0xfebfdc00-0xfebfdcff irq 22 at device 2.2 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 4 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 8 ports with 8 removable, self powered nve0: port 0xdc00-0xdc07 mem =20 0xfebfe000-0xfebfefff irq 20 at device 4.0 on pci0 nve0: Ethernet address 00:13:d4:bf:5b:79 miibus0: on nve0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto nve0: Ethernet address: 00:13:d4:bf:5b:79 pci0: at device 6.0 (no driver attached) pcib1: at device 8.0 on pci0 pci2: on pcib1 pci2: at device 6.0 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xcc00-0xcc7f mem =20 0xfeafec00-0xfeafec7f irq 17 at device 9.0 on pci2 miibus1: on xl0 xlphy0: <3c905C 10/100 internal PHY> on miibus1 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:ef:c6:36 atapci0: port =20 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 9.0 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port =20 0xec00-0xec07,0xe880-0xe883,0xe800-0xe807,0xe480-0xe483,0x7f00-0x7f0f,=20= 0x7c00-0x7c7f irq 22 at device 11. 0 on pci0 ata2: on atapci1 ata3: on atapci1 pcib2: at device 30.0 on pci0 pci1: on pcib2 acpi_button0: on acpi0 fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 =20 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37f,0x778-0x77f irq 7 =20 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 =20 on acpi0 sio0: type 16550A pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on =20 isa0 Timecounter "TSC" frequency 1200007723 Hz quality 800 Timecounters tick every 1.000 msec acd0: CDROM at ata0-master PIO4 ad4: 286188MB at ata2-master SATA150 ad6: 286188MB at ata3-master SATA150 GEOM_MIRROR: Device gm0s1 created (id=3D4118114647). GEOM_MIRROR: Device gm0s1: provider ad4s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 detected. GEOM_MIRROR: Device gm0s1: provider ad6s1 activated. GEOM_MIRROR: Device gm0s1: provider mirror/gm0s1 launched. GEOM_MIRROR: Device gm0s1: rebuilding provider ad4s1. Trying to mount root from ufs:/dev/mirror/gm0s1a nve0: device timeout (6) The mobo is an Asus A7N8X-XE NF ULTRA 400, onboard SATA controller used. Johan From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 17:53:44 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5D84916A4DA for ; Thu, 13 Jul 2006 17:53:44 +0000 (UTC) (envelope-from oberman@es.net) Received: from postal2.es.net (postal2.es.net [198.128.3.206]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1F28E43D45 for ; Thu, 13 Jul 2006 17:53:44 +0000 (GMT) (envelope-from oberman@es.net) Received: from ptavv.es.net ([198.128.4.29]) by postal2.es.net (Postal Node 2) with ESMTP (SSL) id IBA74465; Thu, 13 Jul 2006 10:50:18 -0700 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id B891B45047; Thu, 13 Jul 2006 10:50:17 -0700 (PDT) To: "Dennis Melentyev" In-reply-to: Your message of "Thu, 13 Jul 2006 15:23:11 +0300." Date: Thu, 13 Jul 2006 10:50:17 -0700 From: "Kevin Oberman" Message-Id: <20060713175017.B891B45047@ptavv.es.net> Cc: freebsd-stable@freebsd.org, Mihir Sanghavi Subject: Re: how to use firefox X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 17:53:44 -0000 > Date: Thu, 13 Jul 2006 15:23:11 +0300 > From: "Dennis Melentyev" > Sender: owner-freebsd-stable@freebsd.org > > 2006/7/11, Mihir Sanghavi : > > > > Hi, > > I have installed firefox using pkg_add -r firefox > > and now want to use xterm > > > > i tried using xterm and it says: Cannot open display > > and display not set > > Exit root shell back to user's one. Or "setenv XAUTHORITY ~login/.Xauthority" where 'login' is your login username. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 From owner-freebsd-stable@FreeBSD.ORG Thu Jul 13 19:03:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 79A3016A4DD; Thu, 13 Jul 2006 19:03:18 +0000 (UTC) (envelope-from GMcCaughan@synaptics-uk.com) Received: from mx2.synaptics-uk.com (mx2.synaptics-uk.com [194.203.111.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id C28AC43D49; Thu, 13 Jul 2006 19:03:16 +0000 (GMT) (envelope-from GMcCaughan@synaptics-uk.com) Received: from firewall.synaptics-uk.com ([194.203.111.212] helo=ukexchange2k.synaptics-inc.local) by mx2.synaptics-uk.com with esmtp (Exim 4.20) id 1G16v8-0008Hx-SS; Thu, 13 Jul 2006 20:32:22 +0100 Received: from lists.synaptics-uk.com ([172.20.11.6]) by ukexchange2k.synaptics-inc.local with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 Jul 2006 20:02:45 +0100 Received: from [172.20.11.5] (unknown [172.20.11.5]) by lists.synaptics-uk.com (Postfix) with ESMTP id 18F7E17030; Thu, 13 Jul 2006 19:43:02 +0100 (BST) From: Gareth McCaughan To: freebsd-questions@freebsd.org, freebsd-stable@freebsd.org Date: Thu, 13 Jul 2006 20:02:42 +0100 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607132002.43637.gmccaughan@synaptics-uk.com> X-OriginalArrivalTime: 13 Jul 2006 19:02:45.0128 (UTC) FILETIME=[ECA34080:01C6A6AE] Cc: Subject: "swiN: clock sio" process taking 75% CPU X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Jul 2006 19:03:18 -0000 (Approximately the same question as I'm about to ask seems to have come up many times in -questions and -stable, but I haven't found a useful answer to it.) I have a box running 6-STABLE, cvsupped yesterday. Until recently it was running 5.something and showed exactly the same peculiar behaviour as I'm about to describe. About 6 minutes after booting (on two occasions; I don't guarantee that this doesn't vary), a process that appears in the output of "ps" as "[swi4: clock sio]" begins to use about 3/4 of the machine's CPU. I think it does so more or less instantaneously. It continues to do so indefinitely, so far as I can tell. I'm not aware of anything specific that triggers this, though I suppose there must *be* something. It happens apparently spontaneously, on a lightly loaded machine. Those cycles are genuinely being consumed; other processes run much more slowly, and take much more wall time than CPU time. I've tried diddling my kernel's HZ value; the behaviour with HZ=100 and with HZ=1000 is the same, so far as I'm able to tell. I've no idea whether it might be relevant, but I have option DEVICE_POLLING turned on; toggling sysctl kern.polling.enable doesn't seem to make any difference. The machine is a very uninteresting single-CPU Athlon box, clocked at 1.6GHz, several years old. It used to run 4.x once upon a time, and I'm fairly sure it was fine then. As I mentioned above, it's running a recent 6-STABLE but showed the same pathology under 5.x. Here's its dmesg output, with a few uninteresting bits of information leakage elided. ---------- dmesg output begins ---------- Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-STABLE #3: Thu Jul 13 16:46:07 BST 2006 root@xxxxxxx.xxxxxxxx.com:/usr/obj/usr/src/sys/xxxxxxxx ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: AMD Athlon(tm) XP 1900+ (1599.73-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x662 Stepping = 2 Features=0x383fbff AMD Features=0xc0480800 real memory = 536805376 (511 MB) avail memory = 515944448 (492 MB) ioapic0 irqs 0-23 on motherboard netsmb_dev: loaded acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xec00-0xec7f mem 0xdfffff80-0xdfffffff irq 17 at device 6.0 on pci0 miibus0: on xl0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:75:7e:54:fd isab0: at device 17.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfc00-0xfc0f at device 17.1 on pci0 ata0: on atapci0 ata1: on atapci0 uhci0: port 0xdc00-0xdc1f irq 5 at device 17.2 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe000-0xe01f irq 5 at device 17.3 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xe400-0xe41f irq 5 at device 17.4 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered pci0: at device 17.5 (no driver attached) acpi_button1: on acpi0 fdc0: port 0x3f2-0x3f3,0x3f4-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0: port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 pmtimer0 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounter "TSC" frequency 1599730245 Hz quality 800 Timecounters tick every 10.000 msec ad0: 38166MB at ata0-master UDMA100 acd0: DVDROM at ata1-master UDMA33 Trying to mount root from ufs:/dev/ad0s1a ---------- dmesg output ends ---------- I would be grateful for any insight into what's going wrong and how (if at all) it can be fixed or worked around. I'm not subscribed to -questions or to -stable, so would prefer to be cc'ed, but I'll check the web archives and should therefore see any responses that go only to the list(s). Thanks in advance! -- Gareth McCaughan From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 07:58:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CF81516A4DD for ; Fri, 14 Jul 2006 07:58:16 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.de [213.165.64.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 4DC3D43D45 for ; Fri, 14 Jul 2006 07:58:15 +0000 (GMT) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 14 Jul 2006 07:58:14 -0000 Received: from p54A7E055.dip.t-dialin.net (EHLO [192.168.0.12]) [84.167.224.85] by mail.gmx.net (mp036) with SMTP; 14 Jul 2006 09:58:14 +0200 X-Authenticated: #5465401 Message-ID: <44B74E79.1040100@gmx.de> Date: Fri, 14 Jul 2006 09:57:45 +0200 From: "[LoN]Kamikaze" Organization: Lords of Nightmare User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: freebsd-stable@freebsd.org X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Subject: .MAKEFLAGS confuses buildworld X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 07:58:16 -0000 # make -j 5 buildworld works fine on my Releng_6 system, but # make buildworld with .MAKEFLAGS= -j 5 in my make.conf stops when buildworld arrives at the legacy target. According to the man page of make, it should be exactly the same. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 12:07:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CA3916A4DF; Fri, 14 Jul 2006 12:07:43 +0000 (UTC) (envelope-from GMcCaughan@synaptics-uk.com) Received: from mx2.synaptics-uk.com (mx2.synaptics-uk.com [194.203.111.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBF4143D6A; Fri, 14 Jul 2006 12:07:36 +0000 (GMT) (envelope-from GMcCaughan@synaptics-uk.com) Received: from firewall.synaptics-uk.com ([194.203.111.212] helo=ukexchange2k.synaptics-inc.local) by mx2.synaptics-uk.com with esmtp (Exim 4.20) id 1G1MuQ-0007Id-2x; Fri, 14 Jul 2006 13:36:42 +0100 Received: from lists.synaptics-uk.com ([172.20.11.6]) by ukexchange2k.synaptics-inc.local with Microsoft SMTPSVC(5.0.2195.6713); Fri, 14 Jul 2006 13:06:59 +0100 Received: from [172.20.11.5] (unknown [172.20.11.5]) by lists.synaptics-uk.com (Postfix) with ESMTP id A88C317030; Fri, 14 Jul 2006 12:47:19 +0100 (BST) From: Gareth McCaughan To: freebsd-questions@freebsd.org Date: Fri, 14 Jul 2006 13:06:58 +0100 User-Agent: KMail/1.9.1 References: <200607132002.43637.gmccaughan@synaptics-uk.com> In-Reply-To: <200607132002.43637.gmccaughan@synaptics-uk.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607141306.58682.gmccaughan@synaptics-uk.com> X-OriginalArrivalTime: 14 Jul 2006 12:06:59.0480 (UTC) FILETIME=[02493180:01C6A73E] Cc: freebsd-stable@freebsd.org Subject: Re: "swiN: clock sio" process taking 75% CPU X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 12:07:43 -0000 I wrote, inter alia, > About 6 minutes after booting (on two occasions; I don't > guarantee that this doesn't vary), a process that appears > in the output of "ps" as "[swi4: clock sio]" begins to > use about 3/4 of the machine's CPU. I think it does so > more or less instantaneously. It continues to do so > indefinitely, so far as I can tell. David Wolfskill e-mailed me off-list to suggest looking at the output of "vmstat -i". Answer: the interrupt rates all appear to be normal, or at least similar to those he observes on his machines which don't exhibit my problem. More specifically ... ---------- excerpt from my reply to David begins ---------- I get this: | interrupt total rate | irq1: atkbd0 3 0 | irq6: fdc0 10 0 | irq14: ata0 2913 1 | irq15: ata1 47 0 | irq17: xl0 7342 4 | cpu0: timer 302649 199 | Total 312964 206 (so the rate of timer interrupts doesn't appear to be insane) and | 7:56PM up 26 mins, 1 user, load averages: 1.87, 1.45, 1.08 (so the cost in CPU cycles of servicing them -- if that's what the rogue process is doing, which seems somewhat plausible -- *does* appear to be insane). ---------- excerpt from my reply to David ends ---------- -- g From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 13:10:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 190AE16A4DA for ; Fri, 14 Jul 2006 13:10:05 +0000 (UTC) (envelope-from neca@boox.co.yu) Received: from server.boox.co.yu (server.boox.co.yu [194.247.202.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 27A5543D45 for ; Fri, 14 Jul 2006 13:10:03 +0000 (GMT) (envelope-from neca@boox.co.yu) Received: (qmail 25353 invoked by uid 0); 14 Jul 2006 12:47:52 -0000 Received: from neca.boox.co.yu (HELO ?194.247.202.241?) (194.247.202.241) by server.boox.co.yu with SMTP; 14 Jul 2006 12:47:52 -0000 Message-ID: <44B7979C.1030206@boox.co.yu> Date: Fri, 14 Jul 2006 15:09:48 +0200 From: Nenad Gavrilovic User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Problem in src/lib/libpam/modules/pam_ssh/Makefile X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 13:10:05 -0000 New src/lib/libpam/modules/pam_ssh/Makefile Revision 1.20.2.1 have changes that isn't OK. And becouse of that compile failed!!! From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 13:27:27 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8478816A4E0 for ; Fri, 14 Jul 2006 13:27:27 +0000 (UTC) (envelope-from neca@boox.co.yu) Received: from server.boox.co.yu (server.boox.co.yu [194.247.202.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E002743D5C for ; Fri, 14 Jul 2006 13:27:25 +0000 (GMT) (envelope-from neca@boox.co.yu) Received: (qmail 25568 invoked by uid 0); 14 Jul 2006 13:05:18 -0000 Received: from neca.boox.co.yu (HELO ?194.247.202.241?) (194.247.202.241) by server.boox.co.yu with SMTP; 14 Jul 2006 13:05:18 -0000 Message-ID: <44B79BB2.1080104@boox.co.yu> Date: Fri, 14 Jul 2006 15:27:14 +0200 From: Nenad Gavrilovic User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <44B7979C.1030206@boox.co.yu> In-Reply-To: <44B7979C.1030206@boox.co.yu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: Problem in src/lib/libpam/modules/pam_ssh/Makefile X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 13:27:27 -0000 Nenad Gavrilovic wrote: > New src/lib/libpam/modules/pam_ssh/Makefile Revision 1.20.2.1 have > changes that isn't OK. > > And becouse of that compile failed!!! > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > Looking in other Makefiles I think that correction: CFLAGS+= -I${SSHSRC} -include ssh_namespace. to: CFLAGS+= -I${SSHDIR} -include ssh_namespace. bye From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 16:27:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6331D16A4DD for ; Fri, 14 Jul 2006 16:27:22 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33A7443D46 for ; Fri, 14 Jul 2006 16:27:18 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id k6EGRF9A044542; Fri, 14 Jul 2006 09:27:15 -0700 (PDT) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id k6EGRFeh044541; Fri, 14 Jul 2006 09:27:15 -0700 (PDT) (envelope-from david) Date: Fri, 14 Jul 2006 09:27:15 -0700 From: David Wolfskill To: Nenad Gavrilovic Message-ID: <20060714162715.GL41150@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , Nenad Gavrilovic , freebsd-stable@freebsd.org References: <44B7979C.1030206@boox.co.yu> <44B79BB2.1080104@boox.co.yu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="T4IYkFBVPN84tP7K" Content-Disposition: inline In-Reply-To: <44B79BB2.1080104@boox.co.yu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Problem in src/lib/libpam/modules/pam_ssh/Makefile X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 16:27:22 -0000 --T4IYkFBVPN84tP7K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable [-current removed from recipient list, since rev. 1.20.2.1 of the file in question is on the RELENG_6 branch, which is not CURRENT. -- dhw] On Fri, Jul 14, 2006 at 03:27:14PM +0200, Nenad Gavrilovic wrote: > ... > Looking in other Makefiles I think that correction: >=20 > CFLAGS+=3D -I${SSHSRC} -include ssh_namespace. >=20 > to: >=20 > CFLAGS+=3D -I${SSHDIR} -include ssh_namespace. That change allowed my buildworld to complete; my laptop is now running the newly-built & -installed system: g1-18(6.1-S)[1] uname -a FreeBSD g1-18.catwhisker.org. 6.1-STABLE FreeBSD 6.1-STABLE #121: Fri Jul 1= 4 08:56:01 PDT 2006 root@g1-18.catwhisker.org.:/common/S1/obj/usr/src/s= ys/LAPTOP_30W i386 g1-18(6.1-S)[2]=20 Peace, david --=20 David H. Wolfskill david@catwhisker.org Doing business with spammers only encourages them. Please boycott spammers. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --T4IYkFBVPN84tP7K Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iEYEARECAAYFAkS3xeEACgkQmprOCmdXAD1s8QCfbC03dajLXwKzTpQ7c+ukM6P+ 274AniJYU0CXVbCFz2a5QRZ9uoj7fSlJ =fum5 -----END PGP SIGNATURE----- --T4IYkFBVPN84tP7K-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 16:51:08 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 77B8216A4DF; Fri, 14 Jul 2006 16:51:08 +0000 (UTC) (envelope-from ru@frdp.freebsd.org.ua) Received: from frdp.freebsd.org.ua (82.193.106.18.ipnet.kiev.ua [82.193.106.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9B8CE43D5A; Fri, 14 Jul 2006 16:51:06 +0000 (GMT) (envelope-from ru@frdp.freebsd.org.ua) Received: from frdp.freebsd.org.ua (localhost [127.0.0.1]) by frdp.freebsd.org.ua (8.13.6/8.13.6) with ESMTP id k6EGq5kD093928; Fri, 14 Jul 2006 19:52:05 +0300 (EEST) (envelope-from ru@frdp.freebsd.org.ua) Received: (from ru@localhost) by frdp.freebsd.org.ua (8.13.6/8.13.6/Submit) id k6EGq5DY093927; Fri, 14 Jul 2006 19:52:05 +0300 (EEST) (envelope-from ru) Date: Fri, 14 Jul 2006 19:52:05 +0300 From: Ruslan Ermilov To: Dag-Erling Smorgrav Message-ID: <20060714165205.GA93889@ip.net.ua> References: <44B7979C.1030206@boox.co.yu> <44B79BB2.1080104@boox.co.yu> <20060714162715.GL41150@bunrab.catwhisker.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gKMricLos+KVdGMg" Content-Disposition: inline In-Reply-To: <20060714162715.GL41150@bunrab.catwhisker.org> User-Agent: Mutt/1.5.11 Cc: freebsd-stable@FreeBSD.org, Nenad Gavrilovic Subject: Re: Problem in src/lib/libpam/modules/pam_ssh/Makefile X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 16:51:08 -0000 --gKMricLos+KVdGMg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 14, 2006 at 09:27:15AM -0700, David Wolfskill wrote: > [-current removed from recipient list, since rev. 1.20.2.1 of the file > in question is on the RELENG_6 branch, which is not CURRENT. -- dhw] >=20 > On Fri, Jul 14, 2006 at 03:27:14PM +0200, Nenad Gavrilovic wrote: > > ... > > Looking in other Makefiles I think that correction: > >=20 > > CFLAGS+=3D -I${SSHSRC} -include ssh_namespace. > >=20 > > to: > >=20 > > CFLAGS+=3D -I${SSHDIR} -include ssh_namespace. >=20 > That change allowed my buildworld to complete; my laptop is now running > the newly-built & -installed system: >=20 I've just committed a more complete fix for this. Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --gKMricLos+KVdGMg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEt8u1qRfpzJluFF4RAkt6AJ9LokLzcNqFel9zGSkfwx6lBlXNwACeKnuM UIqeaAmo0CXemxNGwj1vXbE= =8GA7 -----END PGP SIGNATURE----- --gKMricLos+KVdGMg-- From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 19:02:32 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7A67D16A4DA for ; Fri, 14 Jul 2006 19:02:32 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from retezat.tovarna.cz (retezat.tovarna.cz [88.86.106.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id AADDC43D5D for ; Fri, 14 Jul 2006 19:02:25 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.tovarna.cz [127.0.0.1]) by retezat.tovarna.cz (Postfix) with ESMTP id 0DF8FF1850 for ; Fri, 14 Jul 2006 21:00:25 +0200 (CEST) Received: from [192.168.1.2] (unknown [85.132.172.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by retezat.tovarna.cz (Postfix) with ESMTP id F0B94F210A for ; Fri, 14 Jul 2006 21:00:20 +0200 (CEST) Message-ID: <44B7EA39.4060509@quip.cz> Date: Fri, 14 Jul 2006 21:02:17 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <8D08DDB6-6AC1-45B6-B2CE-08782F54968A@stromnet.org> <884C01BC-3E97-46EC-AA8B-E70C3931F3A4@stromnet.org> <36895211-2796-4213-B336-6279AB3AC3CB@stromnet.org> <20060713132357.Y61840@fledge.watson.org> In-Reply-To: <20060713132357.Y61840@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ATA problems again ... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 19:02:32 -0000 Robert Watson wrote: > I don't have a whole lot to add to this thread, but have changed the > subject to make sure that the right people are reading this. This is > likely either a hardware problem (motherboard/cable/drive) or driver > problem. GEOM and the mirror driver seems to be behaving as desired (it > detaches a drive reported by the driver as being bad). Could you post > the dmesg -v output for the probing of the ata controller and driver? Same problem here first (ad4) or second (ad8) disk disappear from the system about once a day. Independent of disk / CPU load. Sometimes without any load, today when I was stress testing the disks with copying /usr/ports to another slice in cycle - after 3 hours I got: Jul 14 19:05:45 track kernel: ad8: FAILURE - device detached Jul 14 19:05:45 track kernel: subdisk8: detached Jul 14 19:05:45 track kernel: ad8: detached Jul 14 19:05:45 track kernel: GEOM_MIRROR: Device gm0: provider ad8 disconnected. Jul 14 19:05:45 track kernel: g_vfs_done():mirror/gm0s1h[READ(offset=6345932800, length=65536)]error = 6 Jul 14 19:05:45 track kernel: vnode_pager_getpages: I/O read error Jul 14 19:05:45 track kernel: vm_fault: pager read error, pid 5108 (cp) After reboot (command reboot), system boot up with both disks attached and start autosynchronization. I do not know, if this is hw or sw error, I got two same machines with almost equal SW setup and realy equal HW setup, but this errors ocurres on one of them only. dmesg.boot before ad8 failure (rebuilding ad4 from previous failure): Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Sun May 7 04:42:56 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.12-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf43 Stepping = 3 Features=0xbfebfbff Features2=0x649d> AMD Features=0x20100000 Logical CPUs per core: 2 real memory = 1073610752 (1023 MB) avail memory = 1041489920 (993 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 bge0: mem 0xfc8f0000-0xfc8fffff irq 16 at device 0.0 on pci3 miibus0: on bge0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:15:f2:ec:43:69 pcib4: irq 17 at device 28.5 on pci0 pci4: on pcib4 bge1: mem 0xfc9f0000-0xfc9fffff irq 17 at device 0.0 on pci4 miibus1: on bge1 brgphy1: on miibus1 brgphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge1: Ethernet address: 00:15:f2:ec:43:6a uhci0: port 0xec00-0xec1f irq 23 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xe880-0xe89f irq 19 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered ehci0: mem 0xfebffc00-0xfebfffff irq 23 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] usb2: EHCI version 1.0 usb2: companion controllers, 2 ports each: usb0 usb1 usb2: on ehci0 usb2: USB revision 2.0 uhub2: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub2: 4 ports with 4 removable, self powered pcib5: at device 30.0 on pci0 pci5: on pcib5 pci5: at device 2.0 (no driver attached) isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 atapci1: port 0xe800-0xe807,0xe480-0xe483,0xe400-0xe407,0xe080-0xe083,0xe000-0xe00f mem 0xfebff800-0xfebffbff irq 19 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 ata4: on atapci1 ata5: on atapci1 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 fdc0: [FAST] ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppbus0: on ppc0 plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] pmtimer0 on isa0 orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Timecounters tick every 1.000 msec acd0: DVDROM at ata0-slave UDMA100 ad4: 238475MB at ata2-master SATA150 GEOM_MIRROR: Device gm0 created (id=565164480). GEOM_MIRROR: Device gm0: provider ad4 detected. ad8: 238475MB at ata4-master SATA150 SMP: AP CPU #1 Launched! GEOM_MIRROR: Device gm0: provider ad8 detected. GEOM_MIRROR: Device gm0: provider ad8 activated. GEOM_MIRROR: Device gm0: provider mirror/gm0 launched. GEOM_MIRROR: Device gm0: rebuilding provider ad4. Trying to mount root from ufs:/dev/mirror/gm0s1a bge0: link state changed to UP uname: FreeBSD 6.1-RELEASE #0: Sun May 7 04:42:56 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP i386 Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 20:59:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AFD2516A4DF for ; Fri, 14 Jul 2006 20:59:20 +0000 (UTC) (envelope-from minter@mail.skiltech.com) Received: from mail.skiltech.com (bunning.skiltech.com [65.36.251.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A8B743D45 for ; Fri, 14 Jul 2006 20:59:19 +0000 (GMT) (envelope-from minter@mail.skiltech.com) Received: from localhost (localhost.skiltech.com [127.0.0.1]) by mail.skiltech.com (Postfix) with ESMTP id 1601E4D9F8 for ; Fri, 14 Jul 2006 16:59:19 -0400 (EDT) Received: from mail.skiltech.com ([127.0.0.1]) by localhost (bunning.skiltech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 16726-06 for ; Fri, 14 Jul 2006 16:59:17 -0400 (EDT) Received: by mail.skiltech.com (Postfix, from userid 1001) id 7D57C4D9F0; Fri, 14 Jul 2006 16:59:17 -0400 (EDT) Date: Fri, 14 Jul 2006 16:59:17 -0400 (EDT) From: "H. Wade Minter" X-X-Sender: minter@bunning.skiltech.com To: freebsd-stable@freebsd.org Message-ID: <20060714165735.L15214@bunning.skiltech.com> x-gpg-fingerprint: 24460EC7 x-gpg-key: http://www.lunenburg.org/wade/pgp.php MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at skiltech.com Subject: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 20:59:20 -0000 I'm considering ordering some of these servers to run FreeBSD 6.1 or 6-STABLE on, but they have Intel ICH7R RAID controllers on them. Googling around, I'm seeing conflicting information as to whether or they work, or work well enough to use in production. The server specs are here: http://store.ebizpc.com/su5018.html Can anyone confirm or deny its support under FreeBSD? Thanks, Wade From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 21:10:43 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF7DA16A4DA for ; Fri, 14 Jul 2006 21:10:43 +0000 (UTC) (envelope-from andrej@antiszoc.hu) Received: from andrej.mine.nu (catv-d5debe68.catv.broadband.hu [213.222.190.104]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9313843D46 for ; Fri, 14 Jul 2006 21:10:42 +0000 (GMT) (envelope-from andrej@antiszoc.hu) Message-ID: <44B80899.90706@antiszoc.hu> Date: Fri, 14 Jul 2006 23:11:53 +0200 From: Andras Got User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060404 SeaMonkey/1.0.1 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20060714165735.L15214@bunning.skiltech.com> In-Reply-To: <20060714165735.L15214@bunning.skiltech.com> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 21:10:44 -0000 Hi, I found these: http://www.freebsd.org/cgi/man.cgi?query=ata&apropos=0&sektion=0&manpath=FreeBSD+6.1-RELEASE&format=html http://www.freebsd.org/cgi/man.cgi?query=ataraid&apropos=0&sektion=0&manpath=FreeBSD+6.1-RELEASE&format=html These look promising imho. Of course real world experience would be appriciated. Andras H. Wade Minter wrote: > I'm considering ordering some of these servers to run FreeBSD 6.1 or > 6-STABLE on, but they have Intel ICH7R RAID controllers on them. > Googling around, I'm seeing conflicting information as to whether or > they work, or work well enough to use in production. > > The server specs are here: > > http://store.ebizpc.com/su5018.html > > Can anyone confirm or deny its support under FreeBSD? > > Thanks, > Wade > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 21:14:26 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 744A816A4DA for ; Fri, 14 Jul 2006 21:14:26 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1497743D45 for ; Fri, 14 Jul 2006 21:14:26 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id C38611157D; Fri, 14 Jul 2006 17:14:12 -0400 (EDT) Message-ID: <44B8094C.3040007@rogers.com> Date: Fri, 14 Jul 2006 17:14:52 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: "H. Wade Minter" References: <20060714165735.L15214@bunning.skiltech.com> In-Reply-To: <20060714165735.L15214@bunning.skiltech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No Cc: freebsd-stable@freebsd.org Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 21:14:26 -0000 H. Wade Minter wrote: > I'm considering ordering some of these servers to run FreeBSD 6.1 or > 6-STABLE on, but they have Intel ICH7R RAID controllers on them. > Googling around, I'm seeing conflicting information as to whether or > they work, or work well enough to use in production. The chipset is supported, but i wouldn't recommend onboard raid for any production server. Get a real raid controller, or use gmirror if you plan to mirror. I use several of these board sin production with gmirror. From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 21:16:20 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93E4B16A4DE for ; Fri, 14 Jul 2006 21:16:20 +0000 (UTC) (envelope-from minter@mail.skiltech.com) Received: from mail.skiltech.com (bunning.skiltech.com [65.36.251.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id A260A43D6A for ; Fri, 14 Jul 2006 21:16:19 +0000 (GMT) (envelope-from minter@mail.skiltech.com) Received: from localhost (localhost.skiltech.com [127.0.0.1]) by mail.skiltech.com (Postfix) with ESMTP id F0D264DFE3; Fri, 14 Jul 2006 17:16:18 -0400 (EDT) Received: from mail.skiltech.com ([127.0.0.1]) by localhost (bunning.skiltech.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19805-08; Fri, 14 Jul 2006 17:16:18 -0400 (EDT) Received: by mail.skiltech.com (Postfix, from userid 1001) id 3C77A4DFE1; Fri, 14 Jul 2006 17:16:18 -0400 (EDT) Date: Fri, 14 Jul 2006 17:16:18 -0400 (EDT) From: "H. Wade Minter" X-X-Sender: minter@bunning.skiltech.com To: Mike Jakubik In-Reply-To: <44B8094C.3040007@rogers.com> Message-ID: <20060714171555.X15214@bunning.skiltech.com> References: <20060714165735.L15214@bunning.skiltech.com> <44B8094C.3040007@rogers.com> x-gpg-fingerprint: 24460EC7 x-gpg-key: http://www.lunenburg.org/wade/pgp.php MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at skiltech.com Cc: freebsd-stable@freebsd.org Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 21:16:20 -0000 On Fri, 14 Jul 2006, Mike Jakubik wrote: > H. Wade Minter wrote: >> I'm considering ordering some of these servers to run FreeBSD 6.1 or >> 6-STABLE on, but they have Intel ICH7R RAID controllers on them. Googling >> around, I'm seeing conflicting information as to whether or they work, or >> work well enough to use in production. > > The chipset is supported, but i wouldn't recommend onboard raid for any > production server. Get a real raid controller, or use gmirror if you plan to > mirror. I use several of these board sin production with gmirror. So if I run the disks in non-RAID mode, and/or use software RAID, they should work? --Wade From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 22:26:07 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 05A2916A4DE for ; Fri, 14 Jul 2006 22:26:07 +0000 (UTC) (envelope-from spork@bway.net) Received: from mail.bway.net (xena.bway.net [216.220.96.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 55B0743D53 for ; Fri, 14 Jul 2006 22:26:06 +0000 (GMT) (envelope-from spork@bway.net) Received: (qmail 70974 invoked by uid 0); 14 Jul 2006 22:26:04 -0000 Received: from unknown (HELO white.nat.fasttrackmonkey.com) (spork@bway.net@216.220.116.154) by smtp.bway.net with (DHE-RSA-AES256-SHA encrypted) SMTP; 14 Jul 2006 22:26:04 -0000 Date: Fri, 14 Jul 2006 18:26:03 -0400 (EDT) From: Charles Sprickman X-X-Sender: spork@white.nat.fasttrackmonkey.com To: Kostik Belousov In-Reply-To: <20060710073442.GG37822@deviant.kiev.zoral.com.ua> Message-ID: References: <20060708085132.GD98476@over-yonder.net> <20060710052513.GF37822@deviant.kiev.zoral.com.ua> <20060710073442.GG37822@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: 6.1 quota issues X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 22:26:07 -0000 On Mon, 10 Jul 2006, Kostik Belousov wrote: > On Mon, Jul 10, 2006 at 01:39:01AM -0400, Charles Sprickman wrote: >> On Mon, 10 Jul 2006, Kostik Belousov wrote: >> >>> On Mon, Jul 10, 2006 at 12:41:07AM -0400, Charles Sprickman wrote: >>>> On Sat, 8 Jul 2006, Matthew D. Fuller wrote: >>>> >>>>> On Fri, Jul 07, 2006 at 10:56:47PM -0400 I heard the voice of >>>>> Charles Sprickman, and lo! it spake thus: >>>>>> >>>>>> Trying again, it reported the same inconsistencies then sat there >>>>>> for more than an hour taking up all the available CPU on the box >>>>>> until I killed it. The mtime on quota.user had not changed during >>>>>> the run. >>>>> >>>>> FWIW, I saw this on a box I setup running a late November -CURRENT >>>>> last year; I could never get the quotas setup and running right >>>>> because the check always just looped itself up. The partition they're >>>>> on has about 3 gig used out of ~45, with maybe a dozen users. I never >>>>> spent much time on it, since it's just a personal box, and the quotas >>>>> are mostly just to provide a handy measure of who's using what (no >>>>> limits set). I just gave it up and decided to worry about it later. >>>> >>>> What should I do here? It's consistently failing. What information >>>> should I gather to forumulate a PR that won't burden the assignee with >>>> lots of troubleshooting mess? The machine is not in production, but there >>>> is user data on it. I could allow a trusted developer access to it, or >>>> even create another jail to illustrate the problem. >>> >>> It is not clear from your report whether you run fsck on the problem >>> partition. I think (and my view is backed by "unexpected inconsistencies" >>> message) that this is the must. >> >> Sorry about that, I did not mention it, but thinking the same thing you >> did, I unmounted the partition and fsck'd twice for good measure. Both >> runs came back clean. I think its quotacheck complaining about the >> quota.user file... > Ok, please, show me uname -a, dmesg, /etc/fstab, mount -v. Rather than clutter the thread with all that, I'll link it up: http://www.bway.net/~spork/quota-info.html There's also a link to the bzipped quota.user file there, as I'm fairly certain that holds some secrets. Are there any utilities to poke around that file with? Thanks, Charles From owner-freebsd-stable@FreeBSD.ORG Fri Jul 14 22:47:54 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4F9216A4DA; Fri, 14 Jul 2006 22:47:54 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF8A443D6A; Fri, 14 Jul 2006 22:47:46 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id E778D2083; Sat, 15 Jul 2006 00:47:42 +0200 (CEST) X-Spam-Tests: AWL X-Spam-Learn: disabled X-Spam-Score: 0.1/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id 71B9A2082; Sat, 15 Jul 2006 00:47:42 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 595F933C31; Sat, 15 Jul 2006 00:47:42 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Ruslan Ermilov References: <44B7979C.1030206@boox.co.yu> <44B79BB2.1080104@boox.co.yu> <20060714162715.GL41150@bunrab.catwhisker.org> <20060714165205.GA93889@ip.net.ua> Date: Sat, 15 Jul 2006 00:47:42 +0200 In-Reply-To: <20060714165205.GA93889@ip.net.ua> (Ruslan Ermilov's message of "Fri, 14 Jul 2006 19:52:05 +0300") Message-ID: <86zmfbu7ld.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@FreeBSD.org, Nenad Gavrilovic Subject: Re: Problem in src/lib/libpam/modules/pam_ssh/Makefile X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jul 2006 22:47:54 -0000 Ruslan Ermilov writes: > I've just committed a more complete fix for this. Thanks. I fat-fingered 'ncvs diff -r1' and thougt what I committed was identical to what was in HEAD. Anyone got a towel to wipe the egg off my face? DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 01:11:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF47A16A4E0 for ; Sat, 15 Jul 2006 01:11:12 +0000 (UTC) (envelope-from javier@skyhawk.kjsl.com) Received: from skyhawk.kjsl.com (skyhawk.kjsl.com [69.36.241.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9448943D49 for ; Sat, 15 Jul 2006 01:11:12 +0000 (GMT) (envelope-from javier@skyhawk.kjsl.com) Received: by skyhawk.kjsl.com (Postfix, from userid 1001) id 82376B848F; Fri, 14 Jul 2006 21:11:12 -0400 (EDT) Date: Fri, 14 Jul 2006 21:11:12 -0400 From: Javier Henderson To: Mike Jakubik Message-ID: <20060715011112.GB32358@skyhawk.kjsl.com> References: <20060714165735.L15214@bunning.skiltech.com> <44B8094C.3040007@rogers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44B8094C.3040007@rogers.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 01:11:13 -0000 * Mike Jakubik [060714 17:15]: > H. Wade Minter wrote: > >I'm considering ordering some of these servers to run FreeBSD 6.1 or > >6-STABLE on, but they have Intel ICH7R RAID controllers on them. > >Googling around, I'm seeing conflicting information as to whether or > >they work, or work well enough to use in production. > > The chipset is supported, but i wouldn't recommend onboard raid for any > production server. Get a real raid controller, or use gmirror if you > plan to mirror. I use several of these board sin production with gmirror. Why do you recommend against on-board RAID controllers? -jav From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 01:13:00 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DBBBE16A4E0 for ; Sat, 15 Jul 2006 01:13:00 +0000 (UTC) (envelope-from javier@skyhawk.kjsl.com) Received: from skyhawk.kjsl.com (skyhawk.kjsl.com [69.36.241.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id C246743D70 for ; Sat, 15 Jul 2006 01:12:54 +0000 (GMT) (envelope-from javier@skyhawk.kjsl.com) Received: by skyhawk.kjsl.com (Postfix, from userid 1001) id 52331B83B6; Fri, 14 Jul 2006 21:12:54 -0400 (EDT) Date: Fri, 14 Jul 2006 21:12:54 -0400 From: Javier Henderson To: "H. Wade Minter" Message-ID: <20060715011254.GC32358@skyhawk.kjsl.com> References: <20060714165735.L15214@bunning.skiltech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060714165735.L15214@bunning.skiltech.com> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 01:13:00 -0000 * H. Wade Minter [060714 17:01]: > I'm considering ordering some of these servers to run FreeBSD 6.1 or > 6-STABLE on, but they have Intel ICH7R RAID controllers on them. Googling > around, I'm seeing conflicting information as to whether or they work, or > work well enough to use in production. > > The server specs are here: > > http://store.ebizpc.com/su5018.html > > Can anyone confirm or deny its support under FreeBSD? I've 6.1-RELEASE on an Intel D945PVS, which has the ICH7R with four 320 GB SATA drives in a RAID 5 configuration. It works fine, and I did put it through its paces before I started storing valuable data. -jav From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 03:10:37 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C52716A4DA; Sat, 15 Jul 2006 03:10:37 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id A57BE43D45; Sat, 15 Jul 2006 03:10:34 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 2DAFE29203E; Sat, 15 Jul 2006 00:10:33 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 01031-01; Sat, 15 Jul 2006 03:10:32 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 9F0ED29203D; Sat, 15 Jul 2006 00:10:30 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 485975C068; Sat, 15 Jul 2006 00:10:29 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 469185C05D; Sat, 15 Jul 2006 00:10:29 -0300 (ADT) Date: Sat, 15 Jul 2006 00:10:29 -0300 (ADT) From: User Freebsd To: Robert Watson In-Reply-To: <20060705234514.I70011@fledge.watson.org> Message-ID: <20060715000351.U1799@ganymede.hub.org> References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-345233355-1152932929=:1799" Content-ID: <20060715000910.U1799@ganymede.hub.org> Cc: freebsd-stable@freebsd.org, Michel Talon , Francisco Reyes Subject: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 03:10:37 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --0-345233355-1152932929=:1799 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; FORMAT=flowed Content-ID: <20060715000910.O1799@ganymede.hub.org> On Wed, 5 Jul 2006, Robert Watson wrote: > If you can get into DDB when the hang has occurred, output via serial console > for the following commands would be very helpful: > > show pcpu > show allpcpu > ps > trace > traceall > show locks > show alllocks > show uma > show malloc > show lockedvnods 'k, after 16 days uptime, the server that I got all the debugging turned on for finally hung up solid ... I was able to break into DDB over the serial link, and have run all of the above on it ... and the output is attached ... One thing to note is that the ps listing is not complete ... there are >6k processes running at the time, and I don't know how to get rid of the '--more--' prompt :( After 1k processes, I just hit 'q' and went onto the other commands ... Also, traceall gave me a 'No such command' error ... now that I think about it, my luck, it was supposed to be 'trace all'? If this doesn't provide enough information, please let me know what else I should do the next time through, besides the above commands ... Oh, and how do you get DDB to 'dump core' in 6.x? Back in 4.x days, I'd just do 'panic' (maybe twice) at the DDB prompt, but that didn't work with 6.x ... it just gave me a stacktrace and then the DDB> prompt both times ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 --0-345233355-1152932929=:1799 Content-Type: APPLICATION/OCTET-STREAM; NAME=typescript.gz Content-Transfer-Encoding: BASE64 Content-ID: <20060715000849.L1799@ganymede.hub.org> Content-Description: Content-Disposition: ATTACHMENT; FILENAME=typescript.gz H4sICAhbuEQAA3R5cGVzY3JpcHQA7X1tk9w2kubXuY6Y/8BY30XIMZox3gEq YjZWljRjnWVLJ9m6uduY6GCRLKlW3V01VdWyPL/+gEyQTIJVLUD27O3tqcKm moXKh0nwQSKRSIBX26Z7ULE/CF1V7bX/801/PP5cCc61rP71/fV1szv81Zcz dhuO/FCx/1YJo95dXBz7q5v++M/Vob/pqtW+b95dfPv46wdVf3Ps9w+qZ5ub Hr+utjdVu705bK/6i389vvVfddVu01WcV8fwD/MfXf314tVxu9v1XdUcK/i8 61aXAPY79kGsHlQ32x18f9Gt/FXfbn+qdu3t7jfVb/x/u9uLdnfr0eLnjxW/ aG/38WrwBfvQOi3X1rEHw+X/adNd9Q8qL8n/Kfx8165Gefahd1zJrmYX6x2B +qPX46a/CJIj+sfBH754+qh6+ngAN+Fqe39zV90xymt2cdhtbqqrbfvuUL3t r7oHF/2H9ur2sHnfV1B0fXvsP1SHzbbaB5Hqnr8qM6uVEexLkPOV9y/VV7eH /VeHffvV4efDV13//isvEP7/Q/uAS383Y+01V1c7r93FI1SlevTixwe+2tKK ZGcqsmbDvQpyr+xMRZqyijwLnlQky6vIz+TIJAewY3e4qEBRf9xvW1ALqm8H X+7e7H1DXF81b/z3h2Norj9d94dwVv3Uvm1uwJRcVFYwW3W8M9Y3cF9m/EHI 2sVjaPa+7Vf/+urZi/9RoakJVcVaLbh1fw3f/7W6bg7eAgCYQTDBgkbOg0nD /dFpxxGMfwzs7fG4Q8U0YinugtYexX+nKizJw2r325sLFAMoI1SEUpKJeGT4 iVC73U/N5uihBoEUSgaolZpphUdZqpVArZwMNV9zAMGjKIXiCNXIdrjBmut4 vOsGvUAKxRCqVa4MygvMoXhdY11N1e6/MxWWFN0g91wMF3HI0gilKywphLKo FVZ7hFIVlhRCId0d0j1AVdoNxzvqKgikUBq1mp6g5lbF43koEEihkO1uomim Vl4ghYpsn8jgvxMVlhTWFbLdkTbIBI/Hu7RatEFeA9tXmpLBuQpLCrViCDU9 QQ9lKywpg3KB7XXbU7Y7YLsrZbuLbB8pypm3RfF4V115AQL12wu8GygaiWWY FnU83oU1JxZiRb6PdMjFWtoGF/jesJ62QicrLCmsLeR7HS7uOysOIHhUpVAS oSY6OGFcPN5xg/WyQTvke006Cu7wWGjdw80A1Mgs7p+Eise7tFo2HYfWvZ6Y lQk1Z1aAsjVCTRbLfwet0Jby3SLf68nMcKF0PN6l1ZJXFuneUNtgoRXaUutu ke0NsQ0GemlT32mxmiUZLPoyDSWDhT7HlrLdItubiQysrofjXVotyWAD2xsl Z1pBw7Gl1t0iRZupOWurTTzepdWSVwbs6LqnvDLAK1PKK4O8aiYoaYWIx7u0 WnaqJvKK9oQGHBBTyisTeFX3M8tggAzGlEIhr1YT250xPB7vuMEgkBp3g8Ra jXRXQniF8HgX1pLuBoil7ewRgttgSoll0IyuxsriTKjheJdWS2fGBI6uajer dzyWug0Gzehq6utrplQ83qXVshHqQPfW1pRYGuiuS+muke6rqRHWRup4vEur ZSPUSPcVfYIazKgupbtGM7qablBYZePxLq2Wxl1rrCtq3DW0HF1qRrUCqMmV qYwNowA4ntUKBVIocBosm2kFbNelbNcCoaYuR7DQ5cDxfF2BQArFEYqyXeOx lO2aIdTEdl99Mh7v0mrJdlUjFHX7FPjbqpTtyiEUpagCiqrSIaGyCEUoqkI/ Ace7bnBJBgVst3wkg3O1B8HjHVB8bpEBSiMUHZsoYLsqYTsYd6UQa2KDZHo4 3qXW0owqpDun4xwFdFeldFdIdz6xwf8p4/EurZYGSyHd+YwNeCylu0K685EN nEvm4vEurZZskEh3QU2DBOMuS+kuke5iYoNhUsXjHVqJpWmQSHdBTYOEliNL jbtEugvSEXp3Mh7v0mppGiTSXVDTIIHustS4S2S7GMnAfd+o4/EurZZ+n0S2 C9o9S2C7LGW7BLa3pJ+QgVF4PK8VCKRQHKGQDDAo4X4IjiWFWjGEomQQSNHS CIioEYqQoQb/o77T/2hP9BPCIRRxZfKglpZBWISilkEA20Up2wWwXZPgr5H1 cDyvFQikUBD/8K411FV8ghD/EMXG3UN0bN1NfU74DjgqSgMgItC9NbMhIUZU 2B3tGQVSKAEe1mwQkAFllzFpLjhCUdMg8FhKdwF01+QGlbY2Hu94hCdukEfP ndYVh5bDS407B7qL9QTlOaPj8bxWIJBAwayCJxZCwRSMsCIeQasRKsw4rWMc uW7aoeEMMzAMQratUWycGpJ1iKXAcQ710akhBkFbTxQkPMwzseCuwbEUDAOk ops087/S8VgMZhFsmrTSKhAVjmdrTNoVW9QYBkhFh5UPemlu47FYL4VPEllv Qi8moBcTn3CTNtYYgmXSYsWUc4ubtLG+sGHDTcK8FRyL9Yo1RsZhDOwgy+bY 4fAW9YomlRgcBkE2VhpkYzZW/aRVjruMAikUOBCiJ8aZhYqHkjJDH+QAa/IB s/xlEEjV4ghFjBezeCw0qUEMoEh4OsdfBoEECmJ/jaT+MoPYHyuN/TGM/Qky wZDlL4NACmVRKzIQY8ZUWFKoFdKdBDez/GUQSKE0akWfIIQRQ0mhVgq1IiOe HH8ZBFIopPt69gR5hSWFWiFF11O1Z/nLIJBCMeyqsdrB22IaeVXo5DIdKUqG v0zbCksKoRxAdYQMGU4uCqRQFmKbdZnrjQIplMHIGDWjWldYUniDgaKuI/G6 HH8ZBVIoicHb2RPEYymvIMjmnyDxJsG4Q0khFDqmNQ3R5Pi4yXwhGHcdOUrj KllYy0eokKPUM2UK6F4aZWMKOUq0yvGXUSCFimaUEgsCdkyVmlGIsvmLkOmm DH8ZBVKoaEbJAB9C+VBSqBXGlAvTjFAghYIZFG/poOUg3RUeS+mukO6S9l4K j6V0hyCb61xZmhEKpFDAdqVJXWVAoUACJXEc5mh7lmCRS4NsDIJsDZv1XhAZ CyWFUMh2Mj2ek4WDAilUtMhlaUYokELhDAqdAwOvCEoKbzDOoExPMCdjCQVS KGS7o20QgmysNMjGJI5ZiV+bk2aEAikUx4ZD6woiY6woyAbGHaJsHot6DQI6 1dIoGxNo3CWlO8SzmCilO0TZ/L2TXIKMPCMUSKEsQs20AmKVRtmYQLrbsRFm ZRmhQAqlMegwapUHBQIplEKosjwqFEihYpCN0l2AcReldBfRuNM+VeCx1Lhj kE2TZImc3CcUSKEYQpHxREaWEQokUDyyndYVBNlYaZCNcXRlJl5lZRmhQAqF bGe0n+DQBnkp27lBqLIsIxRIoZDtNJTPOLRBXmrcObKdlWUZoUAKhcbdUv+D A9t5Kds5Gnc6e8xYXWFJIRQad5JdnpOwhAKpcWc1qlWWZoQCiVoscpT2EwyI xUodEIYOiJ1VFnQ5rJSjLHJ0aoQ5aUYokEIhR6e5iqwsIxRIoZCjdH6cMQgd ssJpD8bQIvOyLCMUSKGQo3z2BIHupVn9jGHInEyP52QZoUAKxRBqoqipa2g5 rMz/ADGAmsiQk2WEAikU+h8k3Oe/sxWWFGqFFpnE6HKyjFAghUK2k8Ca/05X WFKoFbKdBIuysozMYnrcQyHbSdTCfycrLCnUCtlOBuI5WUYokEKh/2FnvOIV lhRqhWwnA/GcLCMUSKHQ2yZrWEwdFgiYuiir/7cBy6ED4ihHHXC0MK0fVAC/ b4LKSTNCgRQK6T4N6rPSjFAghULToBAKppmc7x3xCDeYPZ1jaovGYZghF6Ge LNR8YVI4iAFUWWoJCqRQWFvDkh/UylRYUqgVGgdVllqCAikURp6GYT1qpSos KdQKjQNZp5MTKkeBFAqNw7C4BrXCY5m7BmIANdnknKA0CqRQaBz0jFfQFgun q0AMoIhNzghKo0ACZZDtmvLKANsLp6tADKAKsyVAIIVCtutIBtQK2F44XQVi AcpMFisn+osCKRR2hYay3QDbC6erQAygyrIlUCA17wbpHvNwolp4LKW7Qbqb qYfOCv+CQAqFdB+mslEfoHthqjqIAVTZek4USKAwVX1YKoxaaegKC6e+vADS 3VI2aOCoLvX8NNKdjOSyoqPGpr47aAAlhSHN5TphD4V0t9Q0aKB7Yao6iAEU ibpnhTQXiVQeCtluqWnQeCxlu0a2T35RZuzQLU0DzqKZWUeoge2FqeogBlAj GTKjdIu1r6aOk2iOdjkK2F44ieYFkO2OGhkFbC9MVQcNAGoyMllRunRp6AVq ACXElcmJ0qUrQwEK2e4orxQMTgon0byAwmqf1RUeS8Y5YNwV0p3MP+dE/FAg VQsHOnSSKSNMhwIpFNK9pnRXQPfCVHUQAygSt8gK09VLuuMs2rjIFLSSQPfC WTQvgHSvqe2TQPfCWTTQAKDIsviMMB0KpFA4Z+zKonQokEIh3WtKdwl0L5xF 8wJo3If1qgiFx9JhvUS2k/WqeVG6xXpV0ABKRl5lRumaE7xCtjczXgHbi2bR LlAMoMiy+Kwo3WKRqW97yPaGOlgCPPfCSTQQAygSD8uK0i0mOzwUsn1FySCg 4RROooEYQJGxV1aUbrGa00Mh21e0IxTA9qJUdYBCtq8oGQQei417nEUjqx3z In6L1Y6gApSQKFZWmG61NA04izaudsR7A7oXpqqDWIBqp94rL0zXLnsvTFU3 Le1yONC9cBYNxABqcrfzwnTt0jTEWbSWsoFDoLVwFs0LIN1b2uVwcLd5acw2 zqK1JDqaFaVrl2SIs2jtaBoyo3Tt0jRwZHtHTQOHQGvhLJoXQLZ3MzIARQtn 0UADgCpbVogCKRSyvSOLTDNym1EggYrzcR0lAwO2s1K2M2R7R3zkjNxmFEih kO0dtQwMjHvhfByIBSiSU56T24wCKRSyvZ8WP/jxWx1WUgzTCh+N/saFAcFr RqxxYQD3RoHHYx4WRpKDfXc4o2PJXmKwixjZS+zEioV6HTaJShRzdUwXZMNy EavDWgU8ligGYJhCZacFNn5wxT+pxlwdFzYhJzJXZdQNl+liHQ+Fcx412Xrt HNShv+rbI6hlmrVtVIrlYkbdWF9+QOHNIh5L68vhTHs93SPU1Kn6omlwkwkc 1cLQtK2L1rCEhTpLRhicZ2/IHRqvHx5L7xADrkpPC3UYr4djMZhBMOKLuLDR CJQUmQmHIVelpzScrBANCKRQOConY4sQzaiwpFAreIqKxJT9d3gs7MkcRlyV GbXKi/aAQAqF+aimMHCkzKInc3GFANnsx39nKywpu0EMkyqITuPWVv47IENp mNRhmFSZwsCRWkannUZz2pAZFAexTVe0QgCsPMZJlSkMQoFAqpZCqMKsM7WM dDuMk2qyi5T/Dmu/lKNxtQHZGcl/h8dCb8vpmKFHln/lhLP0coDvdMzQI6li OVlnejnAdxAn9SWUDeEJQEnZDWKcVNMBfk44Sy8H+C4uNmioGVXA0cLFBl4g 0p1kEzgFjVCVWmSIk64asoAvJ5yFAimUQijiemeEs1AghcIMPbKLVIiHV1hS eIPI9hXtJxQeS9kOYVKv78SrnHAWCqRQDKFGXmWFs1AggYIwqS+hvJLA9tIw qYMwqYci3XNGOAsFUihk+4p2ORBxdYU7eoCYb1I03yUrnCWTeR0w7hIzHFbU NMA4xZXGSR3GSaUrjGfJxRoI4zBOKt2sssCXKVxtAGIANd1gVgxKLtZAeCh0 k1e0n5B4LAwcOYyT0rmKrHDWibkKFxcb0MiYgzipK42TOoyT0vh7VjjrRPzd iUh3apEhTupK46RORLoXZp3JxT5gHgrZTuJ1/jtZYUmhVujK6BkUULRwRw/Q AKBIYmROOEstk3AchkmVHhtOXjgLBFIoZHtL+wmBx1K2Q5h0VZMN9HJiUCiQ QHE07rMnCGFSVxomdRyNO7nBnHAWCqRQyPaW2isObC8NkzoIk/qLTPOFOeEs FEiNO0dfpqXGHUKurnC1AYgBVNlafRRIodCXmWsFLac0TuogTuovUrZWHwVS qEh3atw5HkvpztGXackoJyMBEQUSKIZ0H2LKoA/ESV1pnNQxpHsnitbqo0AK FelOuxwGvCqNkzqGdI/hachLdgw8d1bquTNkOwlPZy2wb5bhaceQ7d1Ehkyo Jdth3YIvmdUVsL3wbQQgBlCkT81Ii0SBFCqyHaGg2m1YbAAlhVpFz51Q1NZI 0cJ1C7ZGV4bcYE6GJQqkUIHtrifNOQcKBVIoYLumqeo2vCMBSgpvENhe0x32 M5I1USAx7rZGX6ab1bussKRQrbhzwwSVk62JAilU4Gi97mfLKZBehaNLC5H3 uiepQTnJmiiQQmHkndg+Y2GFgC18h4AXixwlBsvCwgVbutjAwmID7+WQhdAZ eZ8okEJZrHZSVxlQKJBCYSylo0/Q4W0WWmQLbxCo235W7aLCkkIojG7PrIzV FZYUQmEAhEZ4MlJIUSCFwv2qyeYiOYmtKJBAwVIDXzLdYCbU8gni1liyo4NL C5bBltbVsP/8dIM5ia0okELhIMCNi1h8bxrcvnqc086fgrG4C5XiRTNWii9n rCxMm3i1EAlmhrQ08VislsCuYpxmqmodVrHAsQQMLLyOqk1oDtbEuPLN/YxV kV8EzPihOB6LwWJrnDbRs1LW8VgMhr1PTVN7ILZpS2ObFgKSdUuGdDnjARRI oRhCUTMYbhFKyrSCgKRx06r2rPEACqRQOCk6614hBdSW5m1aCEjWPVm6mjMe QIEUymBd0T4RBodWlnYZMR5J94SzkLdpS+ORFuKRXqsyJx4FUiiJUCSBMA9q 6ZjK2PtQtkussVIHSSLbaZ+YMR5AgRQKHaSejgcgiGgLNz/xYvBykF5Sigqg aGk80kI80utbttUtCqRQyHaysDMLql8u7LQCXw7CqVcjwBURpXOrVsR3LJGF Izl7d7HFZoMeCm0y2RjJfwctpzQgGcTavuvIUvSPjwcGgRQK6b6eVRbSq5Tu MSBJduDNGQ+gQAoFdGfr6b1+xkIUMZSUaYW7n7CZReZA99KApOVxa6uy8QAK pFAwZlVk2X4WFAikUDgeWM9uEOhemrdpIR7pL1LoeavlDgAW4pG+hERcLQQR Q0mhVhiPXNMuhyMlSv0PiEd6raa6ytpRTC03E7AYj1RkM4FMqGXvBfHIup9R lIErw0vZztDvJvsS5I0HlvsSWIhHeq1oR8ig4RTuowJi8ASnDJWcLCoUSKEi 22mwB0KbtigeCcadRbrPsICjha9HBRWgsspe64cCKRRydOoJs6BQIIVCjjLa 5TA8FkYRLYscLct9QoE5lMEooiLbNfnvXIUlRVqZGjla+Fo/FEihYoRmppWu sKRQK4M3SGyfgcljU7r7iYEgoteXvN4lI18JBVIohTdYlq+EAikURh3IWyr8 d6LCksIbFHiDxDRk5CuhQAoV2U76CePqCksKtWIIRWyfCS8ihZIyKHynaU/m VnPylVAghYoWmTRn44BXrtAiG4xH9jO2O2C7K2W7Q3e7MIsKBVIoNMiTX5uV ZIQCiXE3GJBUhRtuoUCqFowuezOrd6C7K6W7Q7pP6bZZCUsokEJh+N1QK+Pw WEp3h8bdkJm5jIQlFEigLNLd0EYIu9eY0t1rDOxe4x/uVO05+UookEIh3Q1t z7B7jSndvcZYpDvZDCInXwkFUqhId9oIYfcaU7p7jbHof5CNGXPylVAghUK2 25lWwPbS3WuMRbaTfSVy8pVQIIVCtlva5Vg8lrLdItvJrn45+UookEDhi1Z7 uneXx6+wpEwrE9lOmzNsOWNMqXE3yHYyIZqTr4QCKRSyfZp5zMpXQoEUCl0Z R3llZIUl+TcIxh3XUihO2QBrKUzpWgpjkO4klTEn9wkFUiikO5k9zklYQoEU Cn0ZTs2oBl+mdPcao5Gj5E3oOQlLKJBCoQPiKN1hWYYpXUthNHKUvjw0I18J BVIotH31NHHlhByOoFX+ZIcRcRgwTcNYExxuOBaDIU2HUCsQFEJ+pjTkZyAH 0etF3MiMFAAUSKEwBWAIRKJWvMKSQq04QpHpx5wUgPXi/SJhUyuEIkvkDQfG l4b8DMfXX5OIWN5k+3rZDiHk50vIOlgD0cNQUqgVMmtNgrYZwTUUSKEMQpF1 sAZCfqY05Gcw5IcXLwhjwfcplEIosijacGB7UcgPDDzG/BgZQmfFsUAgVUsg FG2EED40pWu1Dcb82DTCzItjscUrFT0UjjAlJRbE/ExpzM9gzI9Ng9W8gBFb 7J3soTDCzSixYIG1KY35GYz5qWFbdYQCjpbmIBqM+SmygXlO7AkFUiik+zSm yAoYoUAKhcZdUTPKgO6FeyeDGECVrUpDgRQKo4d091ADix5N4d7JIAa3Xrat OgqkUDifw4lWGtIZTWkOosboIZtcv6yAEQqkUOhyK2IZNOydrEv3TtaYg8iI v5a1FzpbTtZrjB4yThqOhrxBXRo91JiCqOimrbrGY+EAU9eR7TOteIUlZcZd Y/iQke2vs7aRYsvtrzVunsymebS8iBFbzqNpDB8yMvmVFTBiy8kvjeFDJijd IRKpS8OHGtMZmSB0zwgYoUAKhcZdUDZAkqUuDR9qh3Qn00w5ASMUSKGQ7oJ0 ORoikbo0nVFj+JCRHIKsgBFbzpxojB4ySXwZ7aARlqYzaodsJ+/AyQkYoUAK FY37rK6gEbpC465xSwk2ywL5eMAIBVIoZDt1ZbQFtrtStltkO3kXS07ACAVS KDTudBNmyNyAkkKtkO3E/8gJGKFACoVsb2daqQpLCrVC464pRSGLVJdGDzUm pDKSlpcTMEKB1LhjRiqb1kdlRYxQIFULjTvd3EpboLstpbtFurckmS7nbbQg kEIh3VvaExqguy2lO2bJMpK2lhMwQoEUKtKddjkQidSl4UON72pl08KFrIAR CqRQ6Llr+gRhJxZduhOLxne1MrpEICNghAIpFPoydM9xDZFIXRo91AbZTnbv ykloRYEUCtnezeoK2G5K2Y7RQ9aRkF9GQisKpFA4TtWU7RCI1IWvfQUxuAjZ PTQjoRUFUqjIdtoRQiBSlwYitY5sL0sdRYEUCtiu6ebeGraa0YWvfQWxcJHC 1FEUSKEUakX7CQ1s18Weu0a6k2njrAVgbLk0Q+uYik8NFuwPo0s3ddEa6U5f WJiXpLlshLjnCesz1i18bAswja9FZWuyL5wMY8JP2OVM4/4iLIY0ISzNtIrH PKwxLK0hC99XPfH9tMJj4eSCVjFRs7RNL4OaWqJ5oJldGrYF0aXbgmjMwuds aj1ZbRoEUiiLUKTb0bAtiC7dFkTj7smcpgXltGm+jGlqzMLnNAFHQ2eoS7Pw NWThe6iyhZgokELhVBqfaQUNu3RXEI1Z+JyVZDgPAikUR6gZr/BYynbMwuck IyErw5kvo4d6yMInE3waEvp1aRa+Fsh2Xpi1y/kJ7x23BeF0FlrDtiC6dFsQ LZDuhA1ZIXx+IlAHWfimJsNC/x3QvXRbEI1TcnwK1OUFy/mJQB1MyfmSmVZA d1FKd8zC57wwws1PRMQwC5/TF8JpgcdSumMWPheFYWl+IiIGU3KmpWvINCT0 69IsfI1Z+FyU5TGiQAoVl1jNtAK2l24LojELn4vCsDQ/EafjmCjBqcGCXUF0 6a4gmuPUOCFDXvLhifAoR+MuaEcIE1a6NAtfc8yToGsDNMdjqevHMS2Ivh1Q M+RVKdt5ZDsJEeREpfkyoV/jjBwXhXmM/ER4lEW2F6Yx8uSVfmDccUpO0DxG DbN7unRKTuOUnCjMY0SBFArpTt/KqCGjX5dm4euYhV8YlkaBFCrSnTZCWBug S7cF0QzpTvrUnLA0CqRQSPdZR8jwWEr3mNAvS/MYl0FNVeP6WZKb4r9zFZYU aaVgSs73E2X7rqFACuXZzjpLrYyCbUFUaUK/gik5TXdvyAlL6xO7NyiYR/P6 EoOlYHZPlb6DNIh1YTtp0j1/PCwdBVIooGi7nmmFx0KLrOKuIGRHAqNg7kuV ZuGrGpd4k4VfWXmMIJBAYRZ+O41T8/IY2+U4VWEWfkvHqQqm0VTpNJqKWfhs 4lVe7iFji40iVUzDZ7N61xWWFKqFFpkOVLNy85YDVeXQItOBqoJ5NFU6j6Zi Fj4ZqGbtHdAvB6oqZuFLahpgHk2VzqOpmIU/DVSzQq0okEKhRZ4GqpxJPw7G I2iVH+NRFlM141AVNge3kJ1ih/6rAEzjPjFkP7FKhQCbZ2p6k+eiYptdc9tt jgFNYVskKZZGwqSANMUplkrFJeikR1TwijlV+l44BbE/D1WYYtkuUywV7Hds HM2hBygoKdQK654sG89KsQSBFAo3XIgBScjeUPBeOFX0XjiAkniDtAUpBCx0 j5SKfU/ZqmoUSKFCY3Q9ieXnQKFACsXwBqnhgu1FVOn2Ikoi38lO6FmJnyCQ WnmJdKcvEVAQjlSl+4soiGz6OySulpLA0dLIpor7i5Ct0HOSSFEghUK6k63Q M6EW42gFkU1/g9Q0wFYlqvS9cCruL0J2oM+JZaFACiVQK+o+SGg5pfuLKIn7 i0wbtGelo6JACoV0p69oVwLrqpTuItKd3iAE61RpZFNBZNNrRdkOEbZQUgiF bKc7VitIelelgU2F+4u0sNd7fKOEEghYatwxsOkctTKQ9K5KA5tKoHFfkfS1 nAXaIJBCIdunrdDzFrODQAqFxn3avjwXatmcca1BuyqL3KJACoUDixVx2nKW jbfLl9UpXGvQTvto50It4zMKFxu0dO9kBYsNVOliAwWRTT8AnWxfTugWBVIo 9GXoVugKFhuo0sUGCiKber0uC92iQAqlEIoad1hsoEr3F1EQ2TTNRPes0C0K pFACoajtg7UGqjSyqSCy6YffZRnFKJBCgXFv6O7XCuJ+qnStgWIY6qErwBRk 9avS/Y4Vi8ad1hXsL6JK1xoEMQj1FCUUR4EUCtk+JT9lhW5RIIUCtnf0dUEZ oVsUSKE821mvZhE2GM2p0rUGCgKbunNlCcUokEJ5trN12820wmMp2yGw6WuR 9PQSFgio0sCmYsh2TRJ6MoLAKDCHChq0fS/odoUfjdwOAolxl8OGx6Srl7DY QJYuNpCw2MBDTf1ETugWBVIojGyyWb3DWLx0sYGExQZ6thY6I3SLAikUGne6 /YaEIKksDZLKGgeqJEEvJ3SLAimUgGpfzbTiFZYUaoUDVfKmkpyMYhRIoBxa ZLodsIRwpCzd71hCZNM0dHApYdcTWRrZlBDZNDWdXcgI3aJACmWwrkatskK3 KJBCaYSiG7TDBiqydL9jCYFNU5MASE7oFgVSKAlaNTOtRIUlhVpFik6WISeh GAVSqGiRidsnMYetdHsRCYFN100BkKyEYhRIoGxkO22DsL2ILNtepFv9c7Vv flP9xv933Ddt/9uLH/w/m5s31W7TedWqY/gnIOrq2AUUp+XaOnbxrltd9jfH fn+vZYbzRq2/rJpjNX79O/ZBrC4Om+3m5rjn91o/EAhb7d/3v175YQ27D3/6 AYJe3demB+Hh178L/ccgO4rSnwR0fhH+uuw/9O3tsb9829x0V/3+cC+oqFXD 7veOK9nW6r6Mf3bOX1N7y2UlgJ2U99A9v7hqdps2fncJakgNMouCoEp/8Rf4 enPwtwo/m859uZQXv//978Pl+v3+dne8X/WbXfVHeCjW1W1d+28O+M2oadWv 5t9UHuOiaXeby3Z3e9nyUPGGrwy7L+L9rZ3/M9x+GL+AGuTnXg89iW+8+vdA qmOtrxXltOrr+IdrEbATCr8RbQIXxD0g1/xiRDsvez8+i046gCEIwl2Evy53 +217b/oZsCPC4YMffxXuo7tYb/fv/KPbHKfLJhcZf+EFGoYCnuPXu+3V5qa/ N/1m+tL/0sGT8l/tfM3z8UElz6cz7fh84LGEhgQNqLm6uvh+Wx1u27dVu/Vt 76bDQt/CDm+3P8H7ZA8X/Yf26vawed9Xh93mprr2BPwQuF3tAfIeTBxAO/kS JPqu+pfqq9vD/qvDvv3q8PPhq65//5UXCP//oX3AZc3gOnANrwRe5oWvr/5w gEk5j3pz6L6sjm/3fYNNucU5t3uccVGbL6lWH6rbQ7+vvO0gKrWdNu26PafS +2v/36UX8QqJmUK3181FNfv87+1NH/98GJQ9DAV/2vf9eFL9ePCX8Z9HTfu2 HyD+9KdX3sBvbrYdQCjhxzeSh/gvnHCr6hCOwo9yIviqvs+ttWUEghOI4cM+ fsKmG/Eg1UILe1YL0E+KupakLl79z4cvvnvyw0M44WHLI9iFGE88pKoniDCb hUVK0ercH73F3f88nluJWuCJEORGOI8l3Mr5E7m92bUrLKql9YNPPp7wkLg6 fIRWUQul3Bxivxkg8GPsuZOxOo0hEIemffd2ezU8EW45vE1+eUIhpKRaHNud Z/dhIJAWvke0p04ohGZ2gni7PRzbwLbhwsZINmoRlq6aCSA44ngfenYjP98Q CBly4J09cTK/ES7m1env5fhTvK6S2g7XghPjyC9FVKl2bgExPJHQhXJmhxPr YFul4b5g1gr+cgkvNjd3QChGIIYn7DmbUKsbIRzXNgR1xxNpNfmlZgNYciNe j93f6B3bcydDdQphZhCHYLKO8KcUgvOwaV08YVayCUJJGyuGu+RGvv3++Q9P sMhY5erICzhxgvCismoAY8mNvHj6AiE8FZwQEy8sbs8dPzosd0J0binE9396 9f3zx09O3PFdJ1QLj/Dd8x+//+EXQFSPn7785uGrb6LuunZiqDR/YmFoWQ3q u3hXxjsLFLn6/uF3T55WYfWGclbysBHJeKJn9kJFCF9dA8Sz6rU3v4/GZsbD JBSL5tKfcCPc1EaUNVEl39ENEK/mEJr5LkJJZYcTJut6NHyaSQ0P1dNXk7p4 HZ7Gi+fPnhF1DScnkhJ8IAkXal4Xr4eHGrZJ8gNA7DrCiaenHR+Cd3Uklggu Emq9uVx5ByJUoa8/pbng0wlzNfmlFLGW+NDMHj56Vv343cPq71O3DJ9sXlyv bteX/3Z7vdpecvPukyAoRl0OQaR3zZv+sPn7p3btgBQ8Ie+uwxdCSslM7H78 ie/DmZgAwk7Q+HHJUwWo8K+WwoSEcDuecNrag38Q/2DjUwU1ds1gtoJLIfzA 2UwnEBscPpG4wZTM2tnr7169ePgomq3goQztIpwwJqau3asVVeJ6fiM/vnj0 cGC4d3Hq0fCHE0m5JXTkvkpa+7evnvz55YuhxsLtD1KWGcbU+EM9Vox33GYQ P3zz8snDxxFe+W6Q6eGEOU0h3OB5SV6n9vfl80fj7euQSz7WheDE/o6dvmAJ xJ82V+ihhldjeR8PjVM48fdkRl54jyV2McFnSrRQrDbxV8IbyGgiw4kUemKn d7wGlWR6I4INjpjvwuAVJuMJBNFGPQYbJqxNIEK0G4X8o/cOu5xOBH2oYecq LNJpd1ZpPjDX1sJKcjK4kAgx8MKI9EZ89ZgopAxuEY0nWlhSnbIewH0lpRBc OFTU+etyI4cTb7TrsV/mZuhVPHMWEH6QhHUSRMJOfvHEWjv58R5SD81MmgVE 1FAq33XwePv+xLc4Od0Ik6NTr9InEpSEo/eAamvQj4cTxfTETqkHe2HcrJld Hy/nJpxr6pZQw0dKyEN9/KJaN+/63ZszUjnewYvX1ZPvf3j5v8JjMbX1gwkY g8CJb2hq9OMNx5eXVo4JXZPG/t3DFwOEF7P+kTIeUi/DCXe+gxwI6fswq+MA JzhhI8S3FKKCFaKcDc4WnBjaI2L40jORifSJBCDyOTmMmZVIQq3X31XPv/7v Tx6Bs6U9J3zzxPbtT7zzO7bh8PItETuV2pEBSWD217ej7xqeveJcjidM8qmZ STf0S9yQJ+KZPYOoYPUtOVF0NCEHPEPY6fmbQlS0fVeaVqcY2G5IdXpmLyBm D0ErcjLa4lknEHyUb5rDW/LDakZweepExBsJ0i8f3RxfXTWrYYgY3qA+9sTS m2JB+9TReDiiRYChELWrec3GE6HJXeGekvBRZg4RQiBTpGOwP8OHnSxhSV18 278phXBTWOa6CaGXhPA//LzLjcxEye9/fPbMO9LX29sb+myrc5bHlwzXjKJT HEapWsCqielE3CX5NiEDpeT8mpOd/O7h4x+qH5rVVa6DONUQBEB3/X5dLImy u5/2n3TN9nrVHM//+M5rHvpr8o04W0OC9iRB8NgcZm44P3sys/6PnlbPNjdU kp9lAp/3oXCrzXAmw/5ko3ZWk1GlMHOvLAh2/XvyjaYmbXZNncYWjv31DkuY VlrG0AqezLrPJELjLxjd+6ivotbMkbboXbLkmv/1xdOX5xS843lWFY1NlUmG oC1qq4x302W0UuGE1TQwJmt6nzf9h9vDvG7nVnZ2TepWfffiE1uZ92P6664/ tLQ8p2VXV/2bpv25278/++M7aujxk9chLDzhsnr241kJkXz61fPq4Yunj+iP 82rIK+xbSk9tgqHmTlJJKZbaTpdRjs1aGacleik5XSYMbslFxLwGqE04vlt1 CRNmxnl2n3Ntv/3h5TAIjcjnngpn86ey228O2xvyhZo/fPI3HSN5z2v3pmuO Df1xprYhnL7dTQH1cZy0kAwlVHITZ1fID845jJzNnf+/b69XmxjLwtGooSc0 ikQZH6bEft/soxsQJg2MlGo8kZZEwfw4dG5v3/3ttr+N1wxxJztIwgmn1SVm NeR9j8QN45Tx/BzjfzzhJ8xvbdY76Lnk32638+eZ0bKDXLfZT36CkDpYv/GE S0kC4Xw2SD407/swSxRPna2tcKdO5tcMRvMnf9HV1dQLBn//9EmV2iEvuR/6 bOe1FcNl8GQmmYRUr9954fi35wxz7NTJ6Ws2XeSt08oPX9WJk6Xk2juF681g 47WtwxuJT5yclvQVFD1K5euSD6ZndnLmmvsmDlG9Y+Dqwf2enaSS4O1ubsYa 0s65sCxwOpn5zzPGg1jX7+Ipd4wNEQ04mXX9kzWBS3rJsBgMPn6swOzQ2c5O Fve5uj406z7MwOJVuB+oWE5OZnNASb/iCTiwj2traxFvLZ7Mngqf3ad3xcf7 rJni8NaT8WQ2YJtfM0RdR0muda2GuCie6LOS+13bXt18gn+7852F/AOnk455 fgJ+mjc7eppzze+DOWn661mP9PFrerHXsjrs36deTcY1wyW9ZJjAKtXWf26u rjc36+35H5+TDJe9Kr5mkHoMfH/6/NOumY7osq7pK9e3su26dFyGoqvNm3Xh NUd19/3fzv/43DV/wfP0TbQbbUKJpL+sqhLvLU9yPp2Nn/xW9q6/Idfk/IyX GtYKT5LpLHzuNTe7y+vt7rjZ3hzO/vj0fT75sNvuj9U3/sKFkuGyN5fXt1fH DS3P9Yy99JvrT3ie++3tsT+uruKp8x312JX4E2FJ78DrJOh+2LzZTDZBMivp yUx1fgH9Oxiu49aPsJquLw9iTBiAaZm2w4AlnHBJotsmnTsKn6uZCculX+O7 li0Nf+Q/lvYqmQvNuGZ/fNvvl1SY9dMzmPkQYLP2PthsMHg25GJSo7C+mQVW q7ORwCqdi6q+fvGnqTDsiT+duJnqM20fPfyu+ssLkkVgHfEqaLDG00/88mb2 Pngm181+HC57t5SNuRqzk0QSP/NhB2d0GCmoO+7E3JWCC1NzUs/qlro1s4SR 158WnvyEGopz1ZdhuFKtbtfrsYEqpcaxzvwkik5/v18fPsnKf+07enpNKfyg c3D7w4mp6WPRCxK9evodRS4gLkkrksoNjAsndpb0ZudG4bC9aa7hPsOkopIc vWo44YLMaoQJRCIJE/LHZjY1dnK+AVWfSfYfju1EPxtmfU+epJLh07Ttp8Sb /Wd3/JkSNzsOW1XHSZKHVW12PBGS1pBdSFaHt6PBDQle9XRiZtHUNNPMS84i 1SVMuD7MnkqB5GaL3okyktVDRkE84ecl4wYf5y5z3lPYtser7S5Ga2QYr8bB 2OzkhGT4tHP/7VxUKpQQyVePXj2tXj15RX9cMEp69uTx2R/fwb53q+769gP9 JmM+CD4/3myOQ8zFOe8eDNYZTmYBNT5d83i7vzkch9wM+FhlCVUlSawwnM52 hImOKRJWqG11ODaf5slvNvvZ/EHGUwn2svVWb6Htx695uOr94BwEy2sIEai2 qiYmdnZSLXm7v27IeHmMuYSPpPOtfOgdwn0Gri/uM8t9C9JzSe8ckCDfPJyb zOpsDk3SyvJmzMLn3Xb1b+SUuuDzmKiZ5qCCsrt+v9kRR4Gr2ez83N+Ikv37 /uYYF62QYnV25kHN7K2/R0/c0vna+Pnzk+ekz5aKSIqZE2bnTFjdHn5P4h+e cJKczKKMi3ynIDyVOkI43Gt7+Og0jxpy7Ol5/sjs9vo4WTDfVkjgP2kr5D4P Px+8jT8OYzoXXkI0dPCzk6hAKrndTPMHfJaOMJt5cEkiFQrj31KEHkycOFlc 09/kpqMRImHFlO7vT2a8TVzj3dXmehM55HwliME4O879cEATOTvW7W59uHxP IwpKOCXGVQXhZGZNRDpf2+5xUYiyfrDCakyFCid+vEKYEDYWopKH21WYLIG/ uZD+xsTpGRbOvPqpJzVIDkrRk/McOvSHw2aIFXLpO7AxrTvkmpAkZyHqdI54 92Y/RFNlLdQwQg5rfbgikp7+ZD7I1246YBFne4dZDrEn++Vuu72iP871E663 3S2d6eUnk/Jjyfw+YTpyOlXzIQqnJWn7DDMBZxU80yPB5S5f/viM5tDLs56U nPt9m5256T4hWgOS2122xzjm6OBSqzAGPVw8w2VXOCC9uGAf2lXPJNftgyoM S27Xh/vVMaTvvH789CVc/PbQtzDu5Yrdr37ab47x3J/t+/VQxnF03Hdv+30f 9V5fNW8O1b0v4eT9pe/Z4o52Lbfrxls/L++1hlzr4VYhXgwaeF0eVE/+8uhZ dS9e5Mtq9TNZfNb1WjZhUVpYaFp7myO+rH7aHN9WQvvu8MabpDdfMFghqVy3 bjtYe+nhr9+EFZeq7y6+4FCsrXDeoQir+Tz1w098uTUXXwgs7vqw158vfv38 xeWz54++vXz44nVY6WcvvpB4gXXdmDb85P3NANC0F18oLO1NbwxefvvuducL O3HxhR4KVxwKw5ByE9Z61s3FFyYqzsN7Gn1ht4Vlpu9xzWR98YUdfiB7Bstm +/3N9BNvt75w4y8U4I+F0l+8xltrW9ZZWBXrbX9zdRXWU+qVrxisOL1qGFvD atTNzdHfMbucfsjXFxf/JUxtau7C8p/7lTdTwfHpGnbgb4Bd/kk7J1wGu85y S5Ywa2VZ3XTqlzKr1is7Msv4u4vM4v/RiNV1DeC/f9OHVaotoZVYrQUslQ3d 5OXIPKkmdvWSCxT36iW/q8XAMd21tiVqPv/2xxdE0Uiz3obkU8pxZfqBZ2dI Hlmm1rLDWgQSB6cy/EL7H/DxB3YFNMUyHigqPkJhWUhhI8wpCq/9iNq0OQaS nSex9w6KDKRra7P6pTRed+v1ZCBrPySINJb/0Wj8n9s+1koYfpJbPWt4Hrd+ HfO4Xq+1a38pr9zawtb3kVdM1p/N4z/SPJ4n+WAf72B5NJNnaD4YybM8VwU8 50wZVp/0A1zfNLVTC6K/fPLnu4jOP5Xorje27edEVyeJ/uqbhy+fPCZUByab JZNbxeZMDgsk/r2YvK65aWJpaIZAADOyedWu+8iQME0af+H0SGX/A1WPBAkr 3Lv3/heGj4Zy1XZr6GJ3UVqtBvKeZUddQg7f/+gwhFiSY6Vs2Ebi41ZQnx+B 6KIBSO/kStbtL3UTG8W6aQBilP1P17+uZd+uR95cRfdL2ZE2/gcGaHNFXLNf kTZhMaKR7hRtOn/T/55ji6Zn3KlfOmoNnacZO8/wxqrPnec/dmyx4s3I4KYN u9kEy9fQ0UXTdLg5USzl+lceX4TV39rIk0Pk8PrcHOv3K9G49iNy7n6p7Wt7 0Uy2L2xh+5nG/1Aau8as401ufQ1fhhB2oKJZEyI7u+7JjwID+8kFXPOO92NT iD9YmZHK/getBAUH4WbyAM82A13UDGqpmT3pITad/fccCrWmrjvjfqkLsNJN O1pzpw3/3Aw+D4W2IRVVKSNOEb3menVqKFRAdPUxopdQuK/ZWk4OiTGfHZL/ D4Kd1tYnh2Im9OUZ43R7lpzuPDlfv7784clffjhhjKVYh2niYIzVJwzXT1D1 /+pw/TxVde3qdezIt10PGw3tB4QwsRnpqp1pHLDg/fXlurm9CjBCjAMv3a4a HNOFnSYvd8NP2n4afq2MXA2/AFeAjL3q9arBBnN1Fcs1sV2O6ZPxSlWbrCGX PD9Q/zVt18rWitiu2pkvPxurX9VYabdSo7Ha9+FH/jdrRcyVtiuo6LH01x89 KcEVPzl66lgrTjFyYbDEp/SmZw1W01s1TNDwaLB4uffoDCPzjNbaz13vZ+8R LLCW9clYabMyvsEtowUfCaRTvn90JvI/hQX2Vmmt4WH7e5gsF7d67Iq7rler 4RIvn4TNJMlFhgiobhq9tICi11MM9KQF/DWDoMqTVJx02MJrs09Fj75//n0u Hz4aOf+FcaE8Pvimy3U/GImw6uVyc3Po9+D3TLSw3KJTE1gTrREP9Rnbn3Wy aYanPpqIJkQ51GBlXG2Hp/7o4aNvnjye2Zp6Ndk2yXHW5ITdWo2TKx+xW/ZO u+Xuslt1TuxnDBCdjv0MvfTZ2M8YHDoR+/k1jRqQWC468ZCmtmtuNu0FHB9U 6/322v9gdfvGe8Zhb3hPpD/6zvXbx18/iJnyK3+AvdIfwEsExtNpP/uw+bte N43l97lvOG2jeV2r1fiCgVEk3Ep9cb25PPiOt317jw+bwDdW3efxT4X7wY+/ gkEZuzh4QnSXq81Nd294qQHuOl/XWur7kzL43oHx18HQyYvVdnu8x5m/iv9/ Ju+l6g4vGX4U2MCwdu6Fu2JKWVRsJcLrCJRcr2v4Y8VFu46Xg99Hg+dveBAf fnN/HT/xFuthl/zht1407Dt/GbegD1Wrwsvkgn6C82ZSdPijvY/aaT0ARVmg qiJgoRXt7rGhqldaxT/U8I1zCQaIhEFKG3DCiOWeDJU11Jsc/xwE46im64Aj owTi92ykQvydcxfwm1DuDSrWJ2NQw/6uwh/cs9xzib5MIgor114MIyl8L8Bs XEVeCCDpmxviw0je3CBY+uYGga8I+PzCjP8HX5jx289vzPgHvjHjH95z9Iqt 1k1b2nOwzz3H557jc8/xuef43HP8B+05wla0R3xvWXixUn+Eqtn3/q8H1Utf 1uyP4S1mX7968dupKNzTh58fVK+O292u76pHL36s+MX/AQPtKqEWMwEA --0-345233355-1152932929=:1799-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 03:28:05 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BD0C916A4DD; Sat, 15 Jul 2006 03:28:05 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42E6B43D45; Sat, 15 Jul 2006 03:28:05 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (wm.hub.org [200.46.204.128]) by hub.org (Postfix) with ESMTP id 6413A291EF2; Sat, 15 Jul 2006 00:28:04 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 01046-06; Sat, 15 Jul 2006 03:28:04 +0000 (UTC) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id DAC81291EF1; Sat, 15 Jul 2006 00:27:41 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id 049FF48830; Sat, 15 Jul 2006 00:27:40 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id F34513F0F1; Sat, 15 Jul 2006 00:27:40 -0300 (ADT) Date: Sat, 15 Jul 2006 00:27:40 -0300 (ADT) From: User Freebsd To: Robert Watson In-Reply-To: <20060715000351.U1799@ganymede.hub.org> Message-ID: <20060715002634.E1799@ganymede.hub.org> References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Michel Talon , Francisco Reyes Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 03:28:05 -0000 On Sat, 15 Jul 2006, User Freebsd wrote: > On Wed, 5 Jul 2006, Robert Watson wrote: > >> If you can get into DDB when the hang has occurred, output via serial >> console for the following commands would be very helpful: >> >> show pcpu >> show allpcpu >> ps >> trace >> traceall >> show locks >> show alllocks >> show uma >> show malloc >> show lockedvnods > > 'k, after 16 days uptime, the server that I got all the debugging turned on > for finally hung up solid ... I was able to break into DDB over the serial > link, and have run all of the above on it ... and the output is attached ... > > One thing to note is that the ps listing is not complete ... there are >6k > processes running at the time, and I don't know how to get rid of the > '--more--' prompt :( After 1k processes, I just hit 'q' and went onto the > other commands ... > > Also, traceall gave me a 'No such command' error ... now that I think about > it, my luck, it was supposed to be 'trace all'? > > If this doesn't provide enough information, please let me know what else I > should do the next time through, besides the above commands ... > > Oh, and how do you get DDB to 'dump core' in 6.x? Back in 4.x days, I'd just > do 'panic' (maybe twice) at the DDB prompt, but that didn't work with 6.x ... > it just gave me a stacktrace and then the DDB> prompt both times ... Quick appendum ... the kernel on this server is from June 28th of this year ... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 03:53:18 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0A51216A4DA; Sat, 15 Jul 2006 03:53:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (ll-227.216.82.212.sovam.net.ua [212.82.216.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4017143D45; Sat, 15 Jul 2006 03:53:16 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k6F3rAjA028465 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jul 2006 06:53:11 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k6F3rAcA018790; Sat, 15 Jul 2006 06:53:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k6F3r9AS018789; Sat, 15 Jul 2006 06:53:09 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 15 Jul 2006 06:53:08 +0300 From: Kostik Belousov To: User Freebsd Message-ID: <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jQIvE3yXcK9X9HBh" Content-Disposition: inline In-Reply-To: <20060715000351.U1799@ganymede.hub.org> User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: freebsd-stable@freebsd.org, Robert Watson , Michel Talon , Francisco Reyes Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 03:53:18 -0000 --jQIvE3yXcK9X9HBh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote: >=20 >=20 > On Wed, 5 Jul 2006, Robert Watson wrote: >=20 > >If you can get into DDB when the hang has occurred, output via serial=20 > >console for the following commands would be very helpful: > > > >show pcpu > >show allpcpu > >ps > >trace > >traceall > >show locks > >show alllocks > >show uma > >show malloc > >show lockedvnods >=20 > 'k, after 16 days uptime, the server that I got all the debugging turned= =20 > on for finally hung up solid ... I was able to break into DDB over the=20 > serial link, and have run all of the above on it ... and the output is=20 > attached ... >=20 > One thing to note is that the ps listing is not complete ... there are >6= k=20 > processes running at the time, and I don't know how to get rid of the=20 > '--more--' prompt :( After 1k processes, I just hit 'q' and went onto th= e=20 > other commands ... set lines=3D0 >=20 > Also, traceall gave me a 'No such command' error ... now that I think=20 > about it, my luck, it was supposed to be 'trace all'? It is alltrace. >=20 > If this doesn't provide enough information, please let me know what else = I=20 > should do the next time through, besides the above commands ... Missing alltrace output seems to be critical. If this is not feasible, please, provide at least the output of the bt for each pid shown in the "show lockedvnods" and "show alllocks". In you case, bt 64880 was the most interesting. It is pity that you had reset the machine. Just in case, do you use mlocked mappings ? Also, why so huge number of crons exist in the system ? The are all forking now. It may be (can not say definitely without further investigation) just a fork bomb. --jQIvE3yXcK9X9HBh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEuGajC3+MBN1Mb4gRAgQMAKDvAgylSfRASs1IbuQ/rQ4oz1Fn5gCcDfmy mG9o5gCPbvWNBVzAhUshR5U= =obot -----END PGP SIGNATURE----- --jQIvE3yXcK9X9HBh-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 04:08:39 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 44EAE16A4DA; Sat, 15 Jul 2006 04:08:39 +0000 (UTC) (envelope-from freebsd@hub.org) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id B904C43D45; Sat, 15 Jul 2006 04:08:38 +0000 (GMT) (envelope-from freebsd@hub.org) Received: from localhost (mx1.hub.org [200.46.208.251]) by hub.org (Postfix) with ESMTP id 92368290C37; Sat, 15 Jul 2006 01:08:37 -0300 (ADT) Received: from hub.org ([200.46.204.220]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 19712-04; Sat, 15 Jul 2006 01:08:37 -0300 (ADT) Received: from ganymede.hub.org (blk-224-179-167.eastlink.ca [24.224.179.167]) by hub.org (Postfix) with ESMTP id 0CC70290C29; Sat, 15 Jul 2006 01:08:37 -0300 (ADT) Received: by ganymede.hub.org (Postfix, from userid 1027) id AEC9A48CE7; Sat, 15 Jul 2006 01:08:36 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id AD84847FB2; Sat, 15 Jul 2006 01:08:36 -0300 (ADT) Date: Sat, 15 Jul 2006 01:08:36 -0300 (ADT) From: User Freebsd To: Kostik Belousov In-Reply-To: <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> Message-ID: <20060715010607.L1799@ganymede.hub.org> References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, Robert Watson , Michel Talon , Francisco Reyes Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 04:08:39 -0000 On Sat, 15 Jul 2006, Kostik Belousov wrote: > On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote: >> >> >> On Wed, 5 Jul 2006, Robert Watson wrote: >> >>> If you can get into DDB when the hang has occurred, output via serial >>> console for the following commands would be very helpful: >>> >>> show pcpu >>> show allpcpu >>> ps >>> trace >>> traceall >>> show locks >>> show alllocks >>> show uma >>> show malloc >>> show lockedvnods >> >> 'k, after 16 days uptime, the server that I got all the debugging turned >> on for finally hung up solid ... I was able to break into DDB over the >> serial link, and have run all of the above on it ... and the output is >> attached ... >> >> One thing to note is that the ps listing is not complete ... there are >6k >> processes running at the time, and I don't know how to get rid of the >> '--more--' prompt :( After 1k processes, I just hit 'q' and went onto the >> other commands ... > set lines=0 >> >> Also, traceall gave me a 'No such command' error ... now that I think >> about it, my luck, it was supposed to be 'trace all'? > It is alltrace. >> >> If this doesn't provide enough information, please let me know what else I >> should do the next time through, besides the above commands ... > Missing alltrace output seems to be critical. If this is not feasible, > please, provide at least the output of the bt for each pid > shown in the "show lockedvnods" and "show alllocks". In you case, > bt 64880 was the most interesting. It is pity that you had reset the > machine. Was down for too long as it was ... it, of course, happened while I was out with the family :( Will keep all of this in mind next time I get a chance to run through things ... Any idea why 'panic' doesn't produce core like it used to? > Just in case, do you use mlocked mappings ? Also, why so huge number of > crons exist in the system ? The are all forking now. It may be (can not > say definitely without further investigation) just a fork bomb. mlocked mappings? What are they? :) re: crons ... this, I'm not sure of, but my suspicion was that the crons weren't able to complete, since the file system was locked up, but the next one was being attempted to run ... *shrug* ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 06:05:42 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9787516A4DD; Sat, 15 Jul 2006 06:05:42 +0000 (UTC) (envelope-from fbsd-stable@mawer.org) Received: from mail18.syd.optusnet.com.au (mail18.syd.optusnet.com.au [211.29.132.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 00E5B43D46; Sat, 15 Jul 2006 06:05:41 +0000 (GMT) (envelope-from fbsd-stable@mawer.org) Received: from [127.0.0.1] (c220-239-234-69.thorn1.nsw.optusnet.com.au [220.239.234.69]) by mail18.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id k6F65ZJG027835; Sat, 15 Jul 2006 16:05:40 +1000 Message-ID: <44B88630.7040506@mawer.org> Date: Fri, 14 Jul 2006 20:07:44 -1000 From: Antony Mawer User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: User Freebsd References: <20060705100403.Y80381@fledge.watson.org> <20060705234514.I70011@fledge.watson.org> <20060715000351.U1799@ganymede.hub.org> <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> <20060715010607.L1799@ganymede.hub.org> In-Reply-To: <20060715010607.L1799@ganymede.hub.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , Robert Watson , freebsd-stable@freebsd.org, Michel Talon , Francisco Reyes Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 06:05:42 -0000 On 14/07/2006 6:08 PM, User Freebsd wrote: >> Just in case, do you use mlocked mappings ? Also, why so huge number >> of crons exist in the system ? The are all forking now. It may be (can >> not say definitely without further investigation) just a fork bomb. > > re: crons ... this, I'm not sure of, but my suspicion was that the crons > weren't able to complete, since the file system was locked up, but the > next one was being attempted to run ... *shrug* This seems consistent with behaviour I've seen in on several 6.0-RELEASE machines.. from the limited information I've been able to get from the machines, there has appeared to be multiple tasks from cron all piled up upon one another. In particular, the daily periodic tasks that run the various 'find' were one of the things I noticed (although we run numerous tasks out of cron)... If something is blocking the filesystem and causing find (and possibly other processes) to become stuck, these would just keep mounting up until it all falls over (with numerous maxproc exceeded etc errors). These are on machines without NFS, but the symptoms are very very similar.. NWFS and SMBFS are commonly used on a number of the machines I've seen the problem on, which may be relevant -- perhaps it affects more than just NFS? I may experiment with building up a test server locally and trying to reproduce similar loads to see if I can trigger the problem in-house.. at least that way I can hook up a serial console and get some more detailed information... Regards Antony From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 06:30:16 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B352416A4DD for ; Sat, 15 Jul 2006 06:30:16 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (ns0.infracaninophile.co.uk [81.187.76.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id E974543D45 for ; Sat, 15 Jul 2006 06:30:15 +0000 (GMT) (envelope-from m.seaman@infracaninophile.co.uk) Received: from [IPv6:::1] (localhost [IPv6:::1]) by smtp.infracaninophile.co.uk (8.13.6/8.13.6) with ESMTP id k6F6TiiP062573; Sat, 15 Jul 2006 07:29:47 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Authentication-Results: smtp.infracaninophile.co.uk from=m.seaman@infracaninophile.co.uk; sender-id=softfail; spf=softfail X-SenderID: Sendmail Sender-ID Filter v0.2.13 smtp.infracaninophile.co.uk k6F6TiiP062573 Message-ID: <44B88B51.10607@infracaninophile.co.uk> Date: Sat, 15 Jul 2006 07:29:37 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Thunderbird 1.5.0.4 (X11/20060610) MIME-Version: 1.0 To: Javier Henderson References: <20060714165735.L15214@bunning.skiltech.com> <44B8094C.3040007@rogers.com> <20060715011112.GB32358@skyhawk.kjsl.com> In-Reply-To: <20060715011112.GB32358@skyhawk.kjsl.com> X-Enigmail-Version: 0.94.0.0 Content-Type: multipart/signed; micalg=pgp-ripemd160; protocol="application/pgp-signature"; boundary="------------enig618647749D12E3E0995E3F0C" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (smtp.infracaninophile.co.uk [IPv6:::1]); Sat, 15 Jul 2006 07:30:08 +0100 (BST) X-Virus-Scanned: ClamAV 0.88.3/1599/Fri Jul 14 06:35:31 2006 on happy-idiot-talk.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on happy-idiot-talk.infracaninophile.co.uk Cc: Mike Jakubik , freebsd-stable@freebsd.org Subject: Re: Intel ICH7R RAID controller working on 6.1/STABLE? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 06:30:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig618647749D12E3E0995E3F0C Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Javier Henderson wrote: > * Mike Jakubik [060714 17:15]: >> The chipset is supported, but i wouldn't recommend onboard raid for an= y=20 >> production server. Get a real raid controller, or use gmirror if you=20 >> plan to mirror. I use several of these board sin production with gmirr= or. =20 > Why do you recommend against on-board RAID controllers? Think about what happens if one of your disks dies. Sure, the machine wi= ll carry on running. With an on-board controller there are two problems: i) How do you get notified that a disk has died ii) How do you replace the drive (i) you'ld likely only find out about at reboot time, or by noticing a change in the pattern of blinken-lights on the machine. (Don't laugh -- it happens) (ii) is not just about having to power off the machine and swap out the hardware: it's not uncommon for on-board RAID-1 setups to be unable to rebuild a mirror by duplicating the good disk onto the replacement one. = That means blowing everything away and recovering from backup. By which time you've had so much downtime that you might as well not have bothered with= RAID in the first place. The advantage of a good RAID controller -- like one of the 3ware cards -- or of gmirror is that combined with hot-swap disk (and pretty much all= SATA drives nowadays have hot-swap capability; you just need to find a chassis with the right sort of drive bays) then you can take out the dead= disk, replace it with a good one and rebuild the array *without taking th= e machine down*. gmirror will alert you to failures in the nightly e-mail if you enable the 406.status-gmirror periodic script. Similarly a good hardware RAID controller will have a system level control application to let you interf= ace with the card from the OS level, and it will have some mechanism for aler= ting the admin to problems. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW --------------enig618647749D12E3E0995E3F0C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEuItY8Mjk52CukIwRA0RbAJ9h8Q5lUZAbkMjJvgf/aiiOu6yHyQCfQMBc zbNyKc3sxol8+t6HHXIlFJU= =kHva -----END PGP SIGNATURE----- --------------enig618647749D12E3E0995E3F0C-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 11:13:40 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 485C116A4DE for ; Sat, 15 Jul 2006 11:13:40 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.18.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27C3943D49 for ; Sat, 15 Jul 2006 11:13:38 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 7212 invoked from network); 15 Jul 2006 11:13:37 -0000 Received: from unknown (HELO localhost) (775067@[217.50.149.8]) (envelope-sender ) by smtprelay01.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 15 Jul 2006 11:13:37 -0000 Date: Sat, 15 Jul 2006 13:13:28 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060715131328.54353f94@localhost> In-Reply-To: <20060628230255.M78211@fledge.watson.org> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060628235258.3414b074@localhost> <20060628230255.M78211@fledge.watson.org> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_5Vv0zkOyRVLTAELPelRpz4V; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 11:13:40 -0000 --Sig_5Vv0zkOyRVLTAELPelRpz4V Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Robert Watson wrote: > On Wed, 28 Jun 2006, Fabian Keil wrote: > > I just got: > > > > Jun 28 23:01:19 tor kernel: lock order reversal: > > Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) @ /usr/src/s= ys/kern/kern_event.c:1053 > > Jun 28 23:01:19 tor kernel: 2nd 0xc1043144 system map (system map) @ /u= sr/src/sys/vm/ > > Looks similar to . >=20 > Could you run "vmstat -z", "netstat -m", and "vmstat -m" please? I enabled polling three days ago and saw this lor two times since then. It may or may not be a coincidence. I log: top -S -d 2 pfctl -si netstat -ss sysctl -a vmstat -z netstat -m vmstat -m=20 every five minutes, the output before and after the lor can be found at: http://www.fabiankeil.de/tmp/lor-185.txt The system is still up at the moment, so the lor might have nothing to do with the crashes/hangs/whatever. I have the feeling that polling does increase the uptime, but I'm not sure yet. Fabian --=20 http://www.fabiankeil.de/ --Sig_5Vv0zkOyRVLTAELPelRpz4V Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEuM3fjV8GA4rMKUQRAk9uAKCJyW+sHZ8MyRbnPV2RHENMbs8QXQCeLPQV HhJZYuM3R41p2ou0ziUX7OU= =UiYB -----END PGP SIGNATURE----- --Sig_5Vv0zkOyRVLTAELPelRpz4V-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 11:20:12 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 32E0316A4E0 for ; Sat, 15 Jul 2006 11:20:12 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC0E243D4C for ; Sat, 15 Jul 2006 11:20:10 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 15075 invoked from network); 15 Jul 2006 11:20:09 -0000 Received: from unknown (HELO localhost) (775067@[217.50.149.8]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 15 Jul 2006 11:20:09 -0000 Date: Sat, 15 Jul 2006 13:20:07 +0200 From: Fabian Keil To: Robert Watson Message-ID: <20060715132007.61a5dbf5@localhost> In-Reply-To: <20060715131328.54353f94@localhost> References: <20060627175853.765a590e@localhost> <20060628101729.J50845@fledge.watson.org> <20060628235258.3414b074@localhost> <20060628230255.M78211@fledge.watson.org> <20060715131328.54353f94@localhost> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_bfwEP=TOnXH9BnRe=6R=7di"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 11:20:12 -0000 --Sig_bfwEP=TOnXH9BnRe=6R=7di Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Fabian Keil wrote: > Robert Watson wrote: >=20 > > On Wed, 28 Jun 2006, Fabian Keil wrote: >=20 > > > I just got: > > > > > > Jun 28 23:01:19 tor kernel: lock order reversal: > > > Jun 28 23:01:19 tor kernel: 1st 0xc3795000 kqueue (kqueue) @ /usr/src= /sys/kern/kern_event.c:1053 > > > Jun 28 23:01:19 tor kernel: 2nd 0xc1043144 system map (system map) @ = /usr/src/sys/vm/ >=20 > > > Looks similar to . > >=20 > > Could you run "vmstat -z", "netstat -m", and "vmstat -m" please? >=20 > I enabled polling three days ago and saw this lor two times > since then. It may or may not be a coincidence. > The system is still up at the moment, so the lor might > have nothing to do with the crashes/hangs/whatever. Actually I had to reset the box about two hours ago, I just forgot and overlooked the few minutes downtime in the logs. Fabian --=20 http://www.fabiankeil.de/ --Sig_bfwEP=TOnXH9BnRe=6R=7di Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEuM9njV8GA4rMKUQRAmG6AKDTAv/JGmNc7+GmGzYOV70fk5FGKwCghOZW gHV0jfwdD+vKShFjQqKdjpA= =+cWI -----END PGP SIGNATURE----- --Sig_bfwEP=TOnXH9BnRe=6R=7di-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 15:09:29 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 667D616A4DD for ; Sat, 15 Jul 2006 15:09:29 +0000 (UTC) (envelope-from lofi@freebsd.org) Received: from mail-in-08.arcor-online.net (mail-in-08.arcor-online.net [151.189.21.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0F9043D5D for ; Sat, 15 Jul 2006 15:09:24 +0000 (GMT) (envelope-from lofi@freebsd.org) Received: from mail-in-08-z2.arcor-online.net (mail-in-08-z2.arcor-online.net [151.189.8.20]) by mail-in-08.arcor-online.net (Postfix) with ESMTP id 384881582E2; Sat, 15 Jul 2006 17:09:23 +0200 (CEST) Received: from mail-in-03.arcor-online.net (mail-in-03.arcor-online.net [151.189.21.43]) by mail-in-08-z2.arcor-online.net (Postfix) with ESMTP id 07881552D1; Sat, 15 Jul 2006 17:09:23 +0200 (CEST) Received: from lofi.dyndns.org (dslb-084-061-133-069.pools.arcor-ip.net [84.61.133.69]) by mail-in-03.arcor-online.net (Postfix) with ESMTP id B40E6206FCC; Sat, 15 Jul 2006 17:09:22 +0200 (CEST) Received: from kiste.my.domain (root@kiste.my.domain [192.168.8.4]) by lofi.dyndns.org (8.13.4/8.13.3) with ESMTP id k6FF9GPY039524 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jul 2006 17:09:17 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from kiste.my.domain (lofi@localhost [127.0.0.1]) by kiste.my.domain (8.13.6/8.13.4) with ESMTP id k6FF9Bei002986; Sat, 15 Jul 2006 17:09:11 +0200 (CEST) (envelope-from lofi@freebsd.org) Received: from localhost (localhost [[UNIX: localhost]]) by kiste.my.domain (8.13.6/8.13.4/Submit) id k6FF98dE002985; Sat, 15 Jul 2006 17:09:08 +0200 (CEST) (envelope-from lofi@freebsd.org) X-Authentication-Warning: kiste.my.domain: lofi set sender to lofi@freebsd.org using -f From: Michael Nottebrock To: freebsd-stable@freebsd.org Date: Sat, 15 Jul 2006 17:09:04 +0200 User-Agent: KMail/1.9.3 References: <200606130103.37160.lofi@freebsd.org> <200606141826.10594.lofi@freebsd.org> In-Reply-To: <200606141826.10594.lofi@freebsd.org> X-Face: =Ym$`&q\+S2X$4`X%x%6"L4>Y,$]<":'L%c9"#7#`2tb&E&wsN31on!N\)3BD[g<=?utf-8?q?=2EjnfV=5B=0A=093=23?=>XchLK,o; >bD>c:]^; :>0>vyZ.X[,63GW`&M>}nYnr]-Fp``,[[@lJ!QL|sfW!s)=?utf-8?q?A2!*=0A=09vNkB/=7CL-?=>&QdSbQg X-Virus-Scanned: by amavisd-new Cc: freebsd-gfx-bugs@nvidia.com Subject: Re: nvidia-driver related (?) panic on 5.5-RELEASE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 15:09:29 -0000 --nextPart3583576.v44U34lq7T Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday, 14. June 2006 18:26, Michael Nottebrock wrote: > On Tuesday, 13. June 2006 01:03, Michael Nottebrock wrote: > > I'm getting similar kernel panics even when running (and quitting) much > simpler applications than secondlife in wine - for instance, this is a > panic I got quitting "foobar2000" (a very unfancy Windows audio player): > > #0 doadump () at pcpu.h:160 > #1 0xc04edd29 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c= :412 > #2 0xc04ee04d in panic (fmt=3D0xc0697a7d "%s: interrupts disabled") > at /usr/src/sys/kern/kern_shutdown.c:568 > #3 0xc064d6eb in pmap_invalidate_range (pmap=3D0xc07065a0, sva=3D3684024= 320, > eva=3D3684040704) I'm getting this on FreeBSD 6.0 as well. Can't anybode else reproduce this?= It=20 is a little alarming that a mere userland application can reliably down the= =20 system like that. =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart3583576.v44U34lq7T Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQBEuQUUXhc68WspdLARAhsEAJwO9h48B6dJvKPmNmRohYWQ+Rh3fACgleSg 2kLoU4WmzRKBLdv39vVeaD0= =rlkO -----END PGP SIGNATURE----- --nextPart3583576.v44U34lq7T-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 16:01:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8CE7616A4DE for ; Sat, 15 Jul 2006 16:01:15 +0000 (UTC) (envelope-from peter.thoenen@yahoo.com) Received: from web51902.mail.yahoo.com (web51902.mail.yahoo.com [206.190.48.65]) by mx1.FreeBSD.org (Postfix) with SMTP id B712A43D4C for ; Sat, 15 Jul 2006 16:01:14 +0000 (GMT) (envelope-from peter.thoenen@yahoo.com) Received: (qmail 45066 invoked by uid 60001); 15 Jul 2006 16:01:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=F9J3eMvOBndHkvxkTwBoZcFZxfTIlsSDHGM4bdQCu+XXFR6zSwdCCtI8/eIY26TCRmz6Cg8yfITMTrh9+Qol6WOvZLyz6aaHjsrqRX1Y915d8osUfLspGU5/21OQk4Wc4LA+y9we6p1ky7fxKBc9Hsc7p/Au8X44YAJsSxPLNsw= ; Message-ID: <20060715160110.45064.qmail@web51902.mail.yahoo.com> Received: from [70.94.10.62] by web51902.mail.yahoo.com via HTTP; Sat, 15 Jul 2006 09:01:10 PDT Date: Sat, 15 Jul 2006 09:01:10 -0700 (PDT) From: Peter Thoenen To: Fabian Keil , Robert Watson In-Reply-To: <20060715132007.61a5dbf5@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: Peter Thoenen , freebsd-stable@freebsd.org Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: eol1@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 16:01:15 -0000 Hey Fabian, To you have pf running? If so can you turn it off for a bit a see if you still crash. On my box I was getting all sorts of witness kbd backtraces on pf and since turning pf off (maybe a week ago), haven't crashed yet. Going to let it keep running unmetered for another 2 weeks and see if I crash or not. -Peter From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 17:00:06 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6785716A4DD for ; Sat, 15 Jul 2006 17:00:06 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7276B43D6A for ; Sat, 15 Jul 2006 17:00:00 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 4345 invoked from network); 15 Jul 2006 16:59:58 -0000 Received: from unknown (HELO localhost) (775067@[217.50.149.8]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 15 Jul 2006 16:59:58 -0000 Date: Sat, 15 Jul 2006 18:59:48 +0200 From: Fabian Keil To: peter.thoenen@yahoo.com Message-ID: <20060715185948.117e9024@localhost> In-Reply-To: <20060715160110.45064.qmail@web51902.mail.yahoo.com> References: <20060715132007.61a5dbf5@localhost> <20060715160110.45064.qmail@web51902.mail.yahoo.com> X-Mailer: Sylpheed-Claws 2.3.1 (GTK+ 2.8.19; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc Mime-Version: 1.0 Content-Type: multipart/signed; boundary=Sig_ufKpaotbS0ZB72RTobirz7t; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: freebsd-stable@freebsd.org, Robert Watson Subject: Re: FreeBSD 6.1 Tor issues (Once More, with Feeling) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 17:00:06 -0000 --Sig_ufKpaotbS0ZB72RTobirz7t Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Peter Thoenen wrote: > To you have pf running? If so can you turn it off for a bit a see if > you still crash. On my box I was getting all sorts of witness kbd > backtraces on pf and since turning pf off (maybe a week ago), haven't > crashed yet. Going to let it keep running unmetered for another 2 > weeks and see if I crash or not. I'm running Tor jailed and use PF for NAT, port forwarding and filtering: http://tor.fabiankeil.de/pf-stats/ So far I didn't see a single PF related complaint from witness, but I'll try disabling PF in a few days anyway. At the moment I'm still testing if enabling polling really increases the uptime. Fabian --=20 http://www.fabiankeil.de/ --Sig_ufKpaotbS0ZB72RTobirz7t Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEuR8MjV8GA4rMKUQRAnBSAKDMPj1gmi7eRFClPMyJhAis4F8sWQCeNM0A c5Zp4b6doHQuWnleDyFexd0= =z56d -----END PGP SIGNATURE----- --Sig_ufKpaotbS0ZB72RTobirz7t-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 20:54:22 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03EAD16A4DA for ; Sat, 15 Jul 2006 20:54:22 +0000 (UTC) (envelope-from rcbdyndns@bellsouth.net) Received: from imf22aec.mail.bellsouth.net (imf22aec.mail.bellsouth.net [205.152.59.70]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6739443D53 for ; Sat, 15 Jul 2006 20:54:21 +0000 (GMT) (envelope-from rcbdyndns@bellsouth.net) Received: from ibm67aec.bellsouth.net ([66.21.212.114]) by imf22aec.mail.bellsouth.net with ESMTP id <20060715205420.KCYX13979.imf22aec.mail.bellsouth.net@ibm67aec.bellsouth.net> for ; Sat, 15 Jul 2006 16:54:20 -0400 Received: from [192.168.0.102] (really [66.21.212.114]) by ibm67aec.bellsouth.net with ESMTP id <20060715205420.GCUE16552.ibm67aec.bellsouth.net@[192.168.0.102]> for ; Sat, 15 Jul 2006 16:54:20 -0400 Message-ID: <44B955FA.6030708@bellsouth.net> Date: Sat, 15 Jul 2006 15:54:18 -0500 From: B Briggs User-Agent: Thunderbird 1.5.0.4 (X11/20060605) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: burncd blank and format problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 20:54:22 -0000 Sorry to have to bring this up again, seems like it was an issue 4 years ago, but I don't know if it's really resolved. If I do: #burncd -f /dev/acd0 blank then burncd will sleep forever. (I have to Ctrl-C for it to exit) It doesn't really hang, but please read this: http://www.freebsd.org/cgi/query-pr.cgi?pr=44803 (I looked at the source code, the only thing I could figure that CDRIOCPROGRESS is ALWAYS returning 0. Inside a while(1), that will never break; Same results with erase instead of blank. On that pr (44803), user says blank worked, however, even when I Ctl-C and break after a while, any data that I write on the disk is invalid: I mean that if I copy it, it will not pass diff. Now this could be a problem with my DRD-RW device, but all of the other ports work with it. So is this my configuration problem? I doubt it, since the usr/ports stuff work ok (cdrecord, growifofs, cdrdao...) I've spent a lot of time on burncd, and it just doesn't work for me. I'm on FreeBSD 6.1R, Pioneer DVD: cd0 at ata1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 66.000MB/s transfers cd0: cd present [115847 x 2048 byte records] If you need any more config data, let me know. -- Bo Briggs From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 22:02:09 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 602EA16A4DF; Sat, 15 Jul 2006 22:02:09 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6610643D70; Sat, 15 Jul 2006 22:02:00 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (am-productions.biz [69.61.164.22]) (authenticated bits=0) by mail.united-ware.com (8.13.6/8.13.6) with ESMTP id k6FM93cS099729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 15 Jul 2006 18:09:10 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org Date: Sat, 15 Jul 2006 18:02:21 -0400 User-Agent: KMail/1.9.1 References: <20060715035308.GJ32624@deviant.kiev.zoral.com.ua> <20060715010607.L1799@ganymede.hub.org> In-Reply-To: <20060715010607.L1799@ganymede.hub.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1532528.BNfqzKaR5h"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200607151802.38187.mistry.7@osu.edu> X-Spam-Status: No, score=-7.5 required=5.0 tests=ALL_TRUSTED,BAYES_60, MYFREEBSD2,MYFREEBSD3 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.2/1600/Sat Jul 15 11:03:46 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: Kostik Belousov , Francisco Reyes , Robert Watson , Michel Talon , User Freebsd Subject: Re: vm_map.c lock up (Was: Re: NFS Locking Issue) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 22:02:09 -0000 --nextPart1532528.BNfqzKaR5h Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 15 July 2006 00:08, User Freebsd wrote: > On Sat, 15 Jul 2006, Kostik Belousov wrote: > > On Sat, Jul 15, 2006 at 12:10:29AM -0300, User Freebsd wrote: > >> On Wed, 5 Jul 2006, Robert Watson wrote: > >>> If you can get into DDB when the hang has occurred, output via > >>> serial console for the following commands would be very > >>> helpful: > >>> > >>> show pcpu > >>> show allpcpu > >>> ps > >>> trace > >>> traceall > >>> show locks > >>> show alllocks > >>> show uma > >>> show malloc > >>> show lockedvnods > >> > >> 'k, after 16 days uptime, the server that I got all the > >> debugging turned on for finally hung up solid ... I was able to > >> break into DDB over the serial link, and have run all of the > >> above on it ... and the output is attached ... > >> > >> One thing to note is that the ps listing is not complete ... > >> there are >6k processes running at the time, and I don't know > >> how to get rid of the '--more--' prompt :( After 1k processes, > >> I just hit 'q' and went onto the other commands ... > > > > set lines=3D0 > > > >> Also, traceall gave me a 'No such command' error ... now that I > >> think about it, my luck, it was supposed to be 'trace all'? > > > > It is alltrace. > > > >> If this doesn't provide enough information, please let me know > >> what else I should do the next time through, besides the above > >> commands ... > > > > Missing alltrace output seems to be critical. If this is not > > feasible, please, provide at least the output of the bt for > > each pid shown in the "show lockedvnods" and "show alllocks". In > > you case, bt 64880 was the most interesting. It is pity that you > > had reset the machine. > > Was down for too long as it was ... it, of course, happened while I > was out with the family :( > > Will keep all of this in mind next time I get a chance to run > through things ... > > Any idea why 'panic' doesn't produce core like it used to? call doadump Should force a core dump. =2D-=20 Anish Mistry --nextPart1532528.BNfqzKaR5h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEuWX+xqA5ziudZT0RAjojAJ4ujkYwSdDTzllMvj/WN6l0wW/NSACgnnZn NumGFh1KJ+5IZa1QNeabNyk= =DyuC -----END PGP SIGNATURE----- --nextPart1532528.BNfqzKaR5h-- From owner-freebsd-stable@FreeBSD.ORG Sat Jul 15 23:53:15 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4055616A4DD for ; Sat, 15 Jul 2006 23:53:15 +0000 (UTC) (envelope-from sean-freebsd@farley.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id BD15843D49 for ; Sat, 15 Jul 2006 23:53:14 +0000 (GMT) (envelope-from sean-freebsd@farley.org) Received: from thor.farley.org (thor.farley.org [IPv6:2001:470:1f01:290:1::5]) by mail.farley.org (8.13.4/8.13.1) with ESMTP id k6FNuFJO093030; Sat, 15 Jul 2006 18:56:15 -0500 (CDT) (envelope-from sean-freebsd@farley.org) Date: Sat, 15 Jul 2006 18:53:01 -0500 (CDT) From: "Sean C. Farley" To: B Briggs In-Reply-To: <44B955FA.6030708@bellsouth.net> Message-ID: <20060715181020.Y54164@thor.farley.org> References: <44B955FA.6030708@bellsouth.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: burncd blank and format problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Jul 2006 23:53:15 -0000 On Sat, 15 Jul 2006, B Briggs wrote: > Sorry to have to bring this up again, seems like it was an issue 4 > years ago, but I don't know if it's really resolved. > > If I do: > #burncd -f /dev/acd0 blank > then burncd will sleep forever. > (I have to Ctrl-C for it to exit) > It doesn't really hang, but please read this: > http://www.freebsd.org/cgi/query-pr.cgi?pr=44803 > > (I looked at the source code, the only thing I could figure that > CDRIOCPROGRESS is ALWAYS returning 0. Inside a while(1), that will > never break; > > Same results with erase instead of blank. > > On that pr (44803), user says blank worked, however, even when I Ctl-C > and break after a while, any data that I write on the disk is invalid: > I mean that if I copy it, it will not pass diff. > > Now this could be a problem with my DRD-RW device, but all of the > other ports work with it. > > So is this my configuration problem? I doubt it, since the usr/ports > stuff work ok (cdrecord, growifofs, cdrdao...) I've spent a lot of > time on burncd, and it just doesn't work for me. I have something similar[1] on my ATAPI CD-RW drive. It is the ioctl() that is the problem since it is always returning zero. The reason the ports you mention work (at least cdrecord) is that they use the SCSI emulator atapicam(4) as opposed to the ATAPI driver itself. Another burncd bug I have is kern/96171[2]. That is in case anyone wants to fix that too. :) Sean 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/83702 2. http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/96171 -- sean-freebsd@farley.org