From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 00:12:00 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A6801065671 for ; Sun, 8 Jun 2008 00:12:00 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id C5BDA8FC17 for ; Sun, 8 Jun 2008 00:11:59 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 4990 invoked by uid 399); 8 Jun 2008 00:11:54 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 8 Jun 2008 00:11:54 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <484B23C8.3040408@FreeBSD.org> Date: Sat, 07 Jun 2008 17:11:52 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <80D7EE2D-A970-407B-A42C-AD17500BC463@netconsonance.com> <861w3cf2pj.fsf@ds4.des.no> <2892DF94-B346-4F36-9D32-165A2EA462D1@netconsonance.com> <484AF52A.108@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 00:12:00 -0000 Jo Rhett wrote: > On Jun 7, 2008, at 1:52 PM, Doug Barton wrote: >>> I'd said nearly a dozen times that the issues I have aren't >>> specifics. I am questioning the overall policy for EoL here. >> >> Your concerns have been noted. You seem unwilling or unable to accept >> the explanation that no matter what you think about the situation, we >> don't have the resources to support 6.2. > > I haven't been given an explanation. I was given that bare statement. > An explanation might help me understand where I can help improve the > situation. The only message in this thread that you have NOT responded to was the one where I answered these questions for you (again) in simple terms. The people that do the work of supporting branches do not have the time to support 6.2. You're not going to get another answer because there isn't one. It's clear from you rhetorical style that you are uninterested in anything in the vicinity of a constructive conversation, so this is my last response to you. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 00:57:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 275371065676; Sun, 8 Jun 2008 00:57:06 +0000 (UTC) (envelope-from bri@brianwhalen.net) Received: from entwistle.sonicboom.org (entwistle.sonicboom.org [66.93.34.170]) by mx1.freebsd.org (Postfix) with ESMTP id 168AF8FC1A; Sun, 8 Jun 2008 00:57:06 +0000 (UTC) (envelope-from bri@brianwhalen.net) Received: from [127.0.0.1] (localhost.sonicboom.org [127.0.0.1]) by entwistle.sonicboom.org (8.14.2/8.14.2) with ESMTP id m580MkIG076100; Sat, 7 Jun 2008 17:22:46 -0700 (PDT) (envelope-from bri@brianwhalen.net) Message-ID: <484B2653.2050600@brianwhalen.net> Date: Sat, 07 Jun 2008 17:22:43 -0700 From: Brian User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: "Patrick M. Hausen" References: <4846E14C.709@FreeBSD.org> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4847FFDE.8000209@FreeBSD.org> <48480473.3010009@rxsec.com> <484808B8.8070506@FreeBSD.org> <5CCF0D6E-56C1-4EBD-B8A6-955311F7851E@netconsonance.com> <20080607204408.GA39103@hugo10.ka.punkt.de> In-Reply-To: <20080607204408.GA39103@hugo10.ka.punkt.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jo Rhett , Kris Kennaway , Doug Barton , FreeBSD Stable , Chris Marlatt Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 00:57:06 -0000 > >> >> However, the fixes are not available in a -RELEASE version of the operating >> system. >> > > Does freebsd-update not address these? Brian From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 01:01:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81786106564A for ; Sun, 8 Jun 2008 01:01:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.229]) by mx1.freebsd.org (Postfix) with ESMTP id 6682C8FC13 for ; Sun, 8 Jun 2008 01:01:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2006883rvf.43 for ; Sat, 07 Jun 2008 18:01:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=3zUbCIG7w6cY6LNtlxkUJzLHz3+jv3MAZ8sPiembANk=; b=BkOF24Ejl8Aq0PrSsLZ6MMbHeKSXyKBcQL3xbzxFeT0vXRVLLxT6vE9Jga+sRkM9qu 2k1llCJYjdc6XPDYhFhRQeSkWFt/1lWaPlmPhxL5h4uOYsHvQvMNl90gpuD+U5Dgqxxa +hqK5Lk0dz/iVpmJloLdtz9oQ0taYWEfbiLRM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=KNf8RsHLjTt6C60RkdwqatzgmP+BdFOQIc4Dr58CjGKqbpn0YZY4Os9jiGYWXS3Q4d ewcgRa/pvFdf3sDzUG3eYLvBZ4tuIIu2tA0xId4mHXZmsD92gc9BPs6VDd5cNn3dOKd2 VxStLgXY+SZy8LzlRwjZxYKKJMlUbuotcaMf8= Received: by 10.141.36.10 with SMTP id o10mr1087564rvj.176.1212886906200; Sat, 07 Jun 2008 18:01:46 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Sat, 7 Jun 2008 18:01:46 -0700 (PDT) Message-ID: Date: Sun, 8 Jun 2008 09:01:46 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <20080604204325.GD4701@lava.net> <20080604234532.GA89656@k7.mavetju> <458FE12C-AE4D-48F9-8193-4663079CEEF8@netconsonance.com> <84EBEA5D3A1F47E79E8E12C4CF4D0314@multiplay.co.uk> <7B8FD1A1E7DA49DFA68252BF9C74AE6F@multiplay.co.uk> <1A050712-3D0F-4263-A9F8-EE4AD042486E@netconsonance.com> X-Google-Sender-Auth: 906573887d3969ca Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 01:01:46 -0000 2008/6/8 Jo Rhett : >> If stability is your main concern then you could throw some resources >> at fixing 6.3 or throw some resources at backporting security fixes to >> 6.2. > > I will apparently be backporting the security fixes myself until 6.4 ships. And if you do, someone (or me, if noone bothers) will be quite happy to commit them to the release branch. >> I'm sure noone has an agenda to squish the FreeBSD version you're >> using for any reason other than there aren't enough people >> volunteering / being paid to work on back-porting security fixes. > > > This is perhaps the real topic that needs to be addressed. Can we get some > more details on the issues involved here? .. There isn't much to say. There aren't enough people putting in their volunteer time to work on this. If you / your company is willing to begin fixing this problem by contributing back to the community, I bet the security team will be quite happy to work with you to get the work done. And you get that fuzzy, warm feeling from contributing to an open source project. :) If everyone who wants 6.2 to be maintained longer wants to put in a couple hours a week of time to help maintain and backport stuff, I think we as a project would be stupid to say no. You just have to be prepared to do the work and be honest enough to say when you're unable to do it anymore. Anyway, this thread is making people upset. :) Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 01:03:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 21B10106567E for ; Sun, 8 Jun 2008 01:03:33 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id 070698FC18 for ; Sun, 8 Jun 2008 01:03:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2007261rvf.43 for ; Sat, 07 Jun 2008 18:03:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=QhQRwbbT1IIWX1Se+5zEHTMuqdbKhFkaZ3FaOWORZ0U=; b=frm5vfPw1MTGAqwy/UUBpjPFDs7+MXKrfEkWhca1958YWLXt+QvylQE6UcYruieGEo pHTgKEfq3M1/WEQQG+fFLBMCISVAMKvNCsFk+kSw5uxt2G4BEllps1cGIgQIBXqUk6is StV42DEm1Q6dLCJrAXeHnR6Xm2QHcucP0lpKA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=ET3f+G4Q88AY7EgKpunp0QXd3QVWxj+K5ARaU+JBQHVPVcI+nuVfnx8SM75K6ZLbk9 rIjrwib/zINCp+drn5G1XA3P0omhxhHpMZ/ga0mmwmHw1wWukmmWA+Xz8vsnoywolTnW CX4j/qKAZttgj49jKd0va99ymy/UInvUourFo= Received: by 10.141.169.11 with SMTP id w11mr1101009rvo.76.1212887012665; Sat, 07 Jun 2008 18:03:32 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Sat, 7 Jun 2008 18:03:32 -0700 (PDT) Message-ID: Date: Sun, 8 Jun 2008 09:03:32 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "Jo Rhett" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4848073C.2060509@rxsec.com> X-Google-Sender-Auth: 8a055b98ceeafd5f Cc: FreeBSD Stable , Chris Marlatt Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 01:03:33 -0000 2008/6/8 Jo Rhett : > On Jun 5, 2008, at 8:39 AM, Adrian Chadd wrote: >> >> The OP stated "argh argh sky is falling with 6.3!" but hasn't yet >> listed PRs which indicate this to be happening. >> He's offered hardware in a week or two - which is great! - but what >> irks the developers is the large amount of noise and absolutely no >> useful information. Anyone can say "its broken!".. > > > Adrian, your other comments are smart and valid. Why is this kind of > hyperbole necessary? Oh don't mind me, I occasionally get pissed off too. :) I have this exact problem with the other project I work on (Squid), and it just gets mto me sometimes. Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 01:32:50 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2E671065672 for ; Sun, 8 Jun 2008 01:32:50 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id B18F08FC16 for ; Sun, 8 Jun 2008 01:32:50 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id F0CC5D00EB; Sat, 7 Jun 2008 15:32:47 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 7654C153882; Sat, 7 Jun 2008 15:32:47 -1000 (HST) Date: Sat, 7 Jun 2008 15:32:47 -1000 From: Clifton Royston To: Jo Rhett Message-ID: <20080608013246.GB8955@lava.net> Mail-Followup-To: Jo Rhett , FreeBSD Stable References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846E637.9080101@samsco.org> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <484736E0.6090004@samsco.org> <4847D5F8.80605@FreeBSD.org> <37414AAF-C75A-4292-A174-2198BEF2A7DF@netconsonance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37414AAF-C75A-4292-A174-2198BEF2A7DF@netconsonance.com> User-Agent: Mutt/1.4.2.2i Cc: FreeBSD Stable Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 01:32:51 -0000 On Sat, Jun 07, 2008 at 12:53:10PM -0700, Jo Rhett wrote: ... > The question I raised is simply: given the number of bugs opened and > fixed since 6.3-RELEASE shipped, why is 6.3 the only supported > version? Why does it make sense for FreeBSD to stop supporting a > stable version and force people to choose between two different > unstable versions? Is this really the right thing to do? In what sense do you consider 6.2 stable? Stable as compared to what? I think a part of the problem here - not the only part - is that you are using idiosyncratic definitions of terms. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 01:33:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9C231065678; Sun, 8 Jun 2008 01:33:12 +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 8C4ED8FC1B; Sun, 8 Jun 2008 01:33:12 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 32C522049; Sun, 8 Jun 2008 03:33:10 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <4846E14C.709@FreeBSD.org> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4847FFDE.8000209@FreeBSD.org> <1212683649.90048.43.camel@bauer.cse.buffalo.edu> Date: Sun, 08 Jun 2008 03:33:09 +0200 In-Reply-To: (Jo Rhett's message of "Sat\, 7 Jun 2008 13\:51\:28 -0700") Message-ID: <86zlpwk8x6.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Kris Kennaway , Ken Smith , FreeBSD Stable , Chris Marlatt , Doug Barton Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 01:33:12 -0000 Jo Rhett writes: > 2 years would be perfectly fine in my mind. I'd love to see 2 years > of support for 6.2-RELEASE. Well, you're getting two years for 6.3. > 6.2 was (and *is* AFAIK) the most stable release of FreeBSD since 4.11 > and it came out the door with less than 12 months of support intended. 6.2 was released on 2007-01-15. The original EoL date was 2008-01-31, and was later pushed back to 2008-05-31. How is that "less than 12 months of support intended"? DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 02:02:39 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FDCE1065679; Sun, 8 Jun 2008 02:02:39 +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 447D38FC16; Sun, 8 Jun 2008 02:02:39 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 15D5F2083; Sun, 8 Jun 2008 04:02:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Jo Rhett References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <80D7EE2D-A970-407B-A42C-AD17500BC463@netconsonance.com> <861w3cf2pj.fsf@ds4.des.no> <2892DF94-B346-4F36-9D32-165A2EA462D1@netconsonance.com> Date: Sun, 08 Jun 2008 04:02:36 +0200 In-Reply-To: <2892DF94-B346-4F36-9D32-165A2EA462D1@netconsonance.com> (Jo Rhett's message of "Sat\, 7 Jun 2008 13\:04\:16 -0700") Message-ID: <86ve0kk7k3.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Doug Barton , FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 02:02:39 -0000 Jo Rhett writes: > Dag-Erling Sm=C3=B8rgrav writes: > > If you have issues with 6.3, your time would be better spent > > reporting them (by which I mean describe them in detail) than waving > > your hands in the air and yelling at people. > Must you resort to nonsense and hyperbole? I'll stop the minute you start backing your claims with data - by which I mean PR numbers at the very least, and preferably information about the outcome of your own tests. > I'd said nearly a dozen times that the issues I have aren't specifics. You mean apart from this: > gmirror failures, 3ware raid driver timeouts, bge0 problems. All > three in production use on dozens of systems. or this: > The bugs in question were very well documented. Sounds to me like you have something pretty specific in mind - yet you consistently refuse to share any of it with us. Every time someone asks you for more information, you dodge the issue with nonsense like the following: > I am questioning the overall policy for EoL here. Even if it was known > to work properly on my hardware the overwhelming amount of bugs in 6.3 > indicates an unstable release. Which overwhelming amount of bugs? Mark Linimon gave you the numbers: > Finally, here are some statistics about PR count: >=20 > rel all kern > --- --- ---- > 6.0 210 91 > 6.1 217 81 > 6.2 396 102 > 6.3 167 56 > 7.0 563 140 >=20 > To me, this doesn't look like an overwhelming case for 6.3 being worse > off than 6.2. Yes, I'm sure there are regressions: there are in any > release. Looks like there are significantly fewer open PRs against 6.3 than against 6.2. > The diffs between 6.3 and 6-STABLE are greater than the diffs between > 6.2 and 6.3 last time I checked. Yet another claim that is simply not supported by evidence: des@ds4 ~/projects/freebsd/releng_6/src% ncvs diff -Nu -rRELENG_6_2_BP -rRE= LENG_6_3_BP >/tmp/releng62-releng63.diff des@ds4 ~/projects/freebsd/releng_6/src% ncvs diff -Nu -rRELENG_6_3_BP -rRE= LENG_6 >/tmp/releng63-releng6.diff des@ds4 ~/projects/freebsd/releng_6/src% wc /tmp/releng6* 1177219 4227294 48994670 /tmp/releng62-releng63.diff 481059 2094131 16180209 /tmp/releng63-releng6.diff 1658278 6321425 65174879 total > I can't understand the logic in having only a single supported version > of the OS, especially one which so many known/reported/fixed-post-=20 > release bugs. As you have been repeatedly told: we do what we can with the resources we have. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 02:17:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A09F01065674 for ; Sun, 8 Jun 2008 02:17:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 8A3E18FC14 for ; Sun, 8 Jun 2008 02:17:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so2017986rvf.43 for ; Sat, 07 Jun 2008 19:17:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition:x-google-sender-auth; bh=xlqeC4elw60WWfHXXvH7oph8NAdyqf3a4OoUCbZy7D8=; b=WsD9e8UwY2eypGd8o2nH7nr4ibEwjDSCQFLZAaxP+pQFM2bVOfes06GoWb8ds8EBUt 1lVCSVwVCA0msX0bAPmRB2nweH0Bg5soiClv9a1+b86feOOAQXWcxzYb4LCDWt3ZrYpU Qt/MV5BKk66AQY10LopkEBBku9trNjiqG+1bg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition:x-google-sender-auth; b=tTRtx7rDglxXRVvafAlf+cLSuB42MRSoip4zijrZUlvI2OVzcoKtp1ZiAfj3ph50rk x02KXUJP+ms7NufSm2q33MczIsxhDuFXSMKe3Bl0xWKCoJs9LcxJbPDtX8yB99UEcfKX RArx+7M+75mtQ5yuNj98MpCx44xd/3HxDBvaA= Received: by 10.141.75.17 with SMTP id c17mr1112460rvl.212.1212891440317; Sat, 07 Jun 2008 19:17:20 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Sat, 7 Jun 2008 19:17:20 -0700 (PDT) Message-ID: Date: Sun, 8 Jun 2008 10:17:20 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: "FreeBSD Stable" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Google-Sender-Auth: c2775be204d4313b Subject: 6.2; 6.3; EOL; combustible discussions 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, 08 Jun 2008 02:17:20 -0000 Ok everyone, I think thats enough about this for now. I think the developers and users have made their points clear, and they're no going to agree any more (but they may agree less) over time. For now, I think we should wait for the following: * Some users standing up, stating "yes, 6.2 lifetime means a lot to us, we'll happily contribute back security fixes and/or bug fixes for our hardware so we can continue using it!", and then doing so. * Some users (Jo, in particular) providing hardware which 6.2 runs on but 6.3 may or may not, and allowing interested developers to jump on and test/debug, so this whole discussion can be ejected out the nearest airlock. * Users figuring out they can contribute back to the community. It isn't hard, honest. How do you think some of us learnt how stuff works? :) Anything else, really, is just going to continue upsetting people. Yes, users want stability in their specific environments. Yes, developers are mere mortals, and users should be happy that there's even a project here they can get access to without some kind of warez-like upload/download ratio. further discussion is just going to upset people even further. :) Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 02:38:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 843821065680 for ; Sun, 8 Jun 2008 02:38:10 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 4D3828FC0C for ; Sun, 8 Jun 2008 02:38:10 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so835335ywe.13 for ; Sat, 07 Jun 2008 19:38:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=llg+ERR3UN4OySm8DmfUPrAJGSdJCgEbPK2Hemj3IJ8=; b=d2YvDSyJADEA6qkoiDerLpZz/Sp4ag30/7nICiV5JLae45pE67sZda5HW0tpwKcmOV nDEeHa6wFGayz/kybCiAHSgZAJjP37EDT85p58FdgRsLCagvkIFLWOtU/ZLsSN3r++7C bzdNTlqXQmZrxrdSNAEFzI9NJ94E1vCDTTyq8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:cc:in-reply-to :mime-version:content-type:content-transfer-encoding :content-disposition:references; b=pCAmBj2nLU+My27klYdQVy6YzQVdro5RccgKkdOtkl7H8b1X7x8siVs+3eTzT+DuoQ B4/Sp4T3FLiDZij/EXoEZ3W9xyXtQConLShRtVo0jBrpeu0SWmMbnYghDve6QZR4lpOP HK1mU5d6yLYFVlQWe8Da+uTtaIOWmdFSP/yv4= Received: by 10.150.206.21 with SMTP id d21mr3351262ybg.227.1212892689474; Sat, 07 Jun 2008 19:38:09 -0700 (PDT) Received: by 10.150.140.14 with HTTP; Sat, 7 Jun 2008 19:38:09 -0700 (PDT) Message-ID: <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com> Date: Sat, 7 Jun 2008 22:38:09 -0400 From: "Josh Carroll" To: "Adrian Chadd" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: Cc: FreeBSD Stable Subject: Re: 6.2; 6.3; EOL; combustible discussions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 02:38:10 -0000 > I think the developers and users have made their points clear, and > they're no going to agree any more (but they may agree less) over > time. You make it sound as if all users are of the same opinion as Jo. The majority of the responses from users running 6.3 in the thread(s) have been positive feedback of its operating properly. I know what you meant, though. Just don't want anyone to think there is somehow a line being drawn in the sand between users and developers. :) > * Some users standing up, stating "yes, 6.2 lifetime means a lot to > us, we'll happily contribute back security fixes and/or bug fixes for > our hardware so we can continue using it!", and then doing so. While it would be interesting to see the response here, it still doesn't necessarily provide a solution. It will still involved developers' time to QA the user-submitted patches, so it won't entirely eliminate the additional workload for maintainers. There is also zero (enforceable) accountability. If X people commit to this, what happens when only a fraction of them actually do end up helping? > * Some users (Jo, in particular) providing hardware which 6.2 runs on > but 6.3 may or may not, and allowing interested developers to jump on > and test/debug, so this whole discussion can be ejected out the > nearest airlock. That would, of course, require that Jo actually try to run 6.3 on his particular hardware, something he said he does not have the time (currently) to do. As others have pointed out, hardware often has numerous revisions and it's quite possible 6.3 will work fine for him. > Anything else, really, is just going to continue upsetting people. > Yes, users want stability in their specific environments. Yes, > developers are mere mortals, and users should be happy that there's > even a project here they can get access to without some kind of > warez-like upload/download ratio. further discussion is just going to > upset people even further. :) I agree, the horse has been beaten to death numerous times. I guess the one thing that I've taken away from this entire discussion is that perhaps it would be useful to the end users to have a managed/tracked list of regressions between releases. I know there are known bugs published, but is there a list of items that are strictly regressions? Even if it doesn't solve the problem of users with particular hardware configurations being able to run the new release, at least it's something people can use in deciding when/if to upgrade or whether they want to go the route of self-supporting security/errata fixes until they find a release they feel comfortable migrating to? Just my two cents, and hopefully I'm not throwing wood on the fire here. Regards, Josh From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 02:56:52 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D2C2106567B for ; Sun, 8 Jun 2008 02:56:52 +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 E3D378FC0A for ; Sun, 8 Jun 2008 02:56:51 +0000 (UTC) (envelope-from des@des.no) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 58FB9208C; Sun, 8 Jun 2008 04:40:44 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Pete French References: Date: Sun, 08 Jun 2008 04:40:43 +0200 In-Reply-To: (Pete French's message of "Fri\, 06 Jun 2008 16\:16\:24 +0100") Message-ID: <86r6b8k5sk.fsf@ds4.des.no> User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: stable@freebsd.org, 000.fbsd@quip.cz, terry@sucked-in.com Subject: Re: gmirror patches 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, 08 Jun 2008 02:56:52 -0000 Pete French writes: > Ah, yes, sorry about that - thought it would be obvious. I always > submit changes that way as I find that whitespace has a habit > of breaking otherwise. > [...] > How would I set about doing that without the whitespace being messed up > by email transit ? I have always found in the past that tabs end up as > spaces and then patch gets upset hwne you try to apply it. "email transit" does not mess up whitespace, though perhaps your web browser does (when you copy-paste the patch from the web interface). If the patches were submitted as PR attachments (using 'send-pr -a'), you can download them separately from the web interface, and avoid the entire copy-paste issue: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/113799 Finally, if you do end up with a patch with messed-up whitespace, you can still apply it using 'patch -l'. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 03:17:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74ADE106566B for ; Sun, 8 Jun 2008 03:17:13 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 4888C8FC0C for ; Sun, 8 Jun 2008 03:17:13 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id 79D6311438F; Sat, 7 Jun 2008 22:17:05 -0500 (CDT) Date: Sat, 07 Jun 2008 22:17:11 -0500 From: Paul Schmehl To: Jo Rhett , freebsd-stable@freebsd.org Message-ID: <449CAA5455C15CA79034C5D2@Macintosh.local> In-Reply-To: References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <200806051023.56065.jhb@freebsd.org> <200806051910.20319.pieter@degoeje.nl> <3E1DBCBBB1C614B1DBD0F166@utd65257.utdallas.edu> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========4C6C9B90129CF6A2C0E2==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: console access X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 03:17:13 -0000 --==========4C6C9B90129CF6A2C0E2========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 7, 2008 2:16:26 PM -0700 Jo Rhett =20 wrote: > On Jun 5, 2008, at 11:35 AM, Paul Schmehl wrote: >> It's not quite that simple. To do that, I have to block out time to >> drive 45 miles during my supposed "off" hours and do the upgrade >> there. Because, if it breaks networking and I'm at home, the server >> will be down for at least an hour until I can drive to the hosting >> company, get access to the server and restore the old kernel. > > Paul, you should arrange with your colocation provider to get an out of > band serial connection to the system, and configure the console to go to > the serial port. We provide that for free at $EMPLOYER and most other > places I know of do it for free or nominal charge. > I was not aware of that. Thanks for the suggestion. Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========4C6C9B90129CF6A2C0E2==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 03:46:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A7AB106566B for ; Sun, 8 Jun 2008 03:46:21 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB3A8FC1D for ; Sun, 8 Jun 2008 03:46:20 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id D1BEC11438F for ; Sat, 7 Jun 2008 22:46:12 -0500 (CDT) Date: Sat, 07 Jun 2008 22:46:18 -0500 From: Paul Schmehl To: freebsd-stable@freebsd.org Message-ID: <1CB0175143266C386F4593B9@Macintosh.local> In-Reply-To: References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <200806050248.59229.max@love2party.net> <20080605083907.GD1028@server.vk2pj.dyndns.org> <902E9703E6E50776A17E9F92@utd65257.utdallas.edu> <20080605220244.GP1028@server.vk2pj.dyndns.org> <34E9F0D46D7B9F45EDA38F4C@utd65257.utdallas.edu> <86tzg6aeye.fsf@ds4.des.no> <5B0709D83455470DA46533C4@Macintosh.local> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========931817CF8F8B8EBAF4D1==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 03:46:21 -0000 --==========931817CF8F8B8EBAF4D1========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 7, 2008 2:41:32 PM +0800 Adrian Chadd = wrote: > 2008/6/7 Paul Schmehl : > >> Not only is this wrong, but it completely misses the point. Why should >> Jo have to upgrade to find out if his servers will fail under the >> conditions already articulated in existing, unresolved PRs that affect >> hardware that he is presently using? That's a bit like saying, "Buy >> this new car. Sure it has bugs that could easily directly affect you, >> but what's the chance you'll encounter them? in the off chance that >> they do, then you can help us resolve them." > > The software is Free. The car was Bought (or suggested to be bought.) > > Re-visit the analogy with a free car that a friend wants to give you. > (Car analogies suck.) > Yes, they do. It was the best I could come up with on the spur of the=20 moment. > >> Trust me. From a server admin's perspective, a bug affects you if it >> exists in hardware you use. Whether or not you're actually using the >> OS is completely irrelevant. Upgrading to the OS would be foolhardy. >> Even testing it on a handful of boxes will not prove that it won't fail >> under load in production. Anyone who has done testing knows it can >> only simulate, not duplicate, the conditions under which production >> servers run. I personally have experienced catastrophic failures after >> extensive testing that revealed no problems. > > You're using free software. This translates to "lots of people have > put in a lot of effort to provide something to the community which > they can use, at no cost, if it suits them." > Of course. What it *shouldn't* translate to is STFU and eat our dog food=20 or go somewhere else. >> >> I've lectured enough. If anyone doesn't get the point by now further >> explanation isn't going to help. > > I still don't think you get it. FreeBSD is a community. A community > works when enough people contribute positively towards furthering the > goals of the project. Jo is a user. He sounds like he is using it in > some reasonably critical and money-earning roles. Jo can participate > by testing stuff on test hardware, reporting back issues and working > with the community. Bitching about there being no long-term support > for releases isn't constructive. Some developer comments may not be > constructive either, but this is a -community project-. Join the > -community- and help out. > Here's a hint for you. Jo already contributes. So do I. Furthermore,=20 both of us deeply appreciate the work that the developers do to produce=20 FreeBSD and have stated so repeatedly. > It doesn't matter if running a long-term support project would be > beneficial for a certain subset of the userbase, its a losing > situation to cater to them unless they somehow contribute back to the > community. > This is precisely the attitude that I am objecting to. Translated for the = average user it states, "If you're using and not contributing, then shut=20 up. You haven't earned the right to complain." Open source projects are not free. They cost the developers in time and=20 effort. They also cost the users in dealing with untested bugs, dealing=20 with making many disparate pieces of software work together rather than=20 using a fully integrated commercial package. Open source projects also have benefits. Developers get the benefit of a=20 huge plus on their resumes. This translates directly into increased=20 income for some of them and could for all of them. They also benefit from = intangibles such as the pride of a job well done, the respect of their=20 peers and the admiration of their users. Users get benefits as well.=20 They get to use a system that works better than many commercial products=20 and has a great deal more flexibility. But don't think for one minute that open source is free for users and only = costs developers. Neither "side" deserves to be insulted and talked down to. Maybe some developers need to quit. If the work is so difficult and=20 stressful that they can't behave in a professional manner, perhaps it's an = indication that they've overextended themselves and need to take a step=20 back. There are few that have displayed an attitude that clearly states=20 that they think they are doing all the contributing and users are doing=20 nothing. Nothing could be further from the truth. Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========931817CF8F8B8EBAF4D1==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 05:30:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4824106567D for ; Sun, 8 Jun 2008 05:30:23 +0000 (UTC) (envelope-from zkolic@sbb.co.yu) Received: from smtp3.sbb.co.yu (smtp3.sbb.co.yu [82.117.194.23]) by mx1.freebsd.org (Postfix) with ESMTP id 2C0FB8FC0A for ; Sun, 8 Jun 2008 05:30:22 +0000 (UTC) (envelope-from zkolic@sbb.co.yu) Received: from faust.net (cable-89-216-102-229.dynamic.sbb.rs [89.216.102.229]) by smtp3.sbb.co.yu (8.14.0/8.14.0) with ESMTP id m585UK70014343 for ; Sun, 8 Jun 2008 07:30:20 +0200 Received: by faust.net (Postfix, from userid 1001) id 71F8D1CC2F; Sun, 8 Jun 2008 07:30:37 +0200 (CEST) Date: Sun, 8 Jun 2008 07:30:37 +0200 From: Zoran Kolic To: freebsd-stable@freebsd.org Message-ID: <20080608053037.GA831@faust.net> References: <20080607234754.0443A106578D@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080607234754.0443A106578D@hub.freebsd.org> X-SMTP-Vilter-Version: 1.3.2 X-SBB-Virus-Status: clean X-SBB-Spam-Score: -2.0 Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 05:30:23 -0000 This thread solves nothing. Two positions are clear. Also, I recall harder words on openbsd list, with a lot shorter thread. The whole thing is finished and should stay in that state. All next posts could be written, but no need to be sent. Best regards Zoran From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 06:42:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44E44106567F for ; Sun, 8 Jun 2008 06:42:39 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 208788FC14 for ; Sun, 8 Jun 2008 06:42:38 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1232472wah.3 for ; Sat, 07 Jun 2008 23:42:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=tXn+ntzlG9Yrzl6sNTiHzmab0YgSyHoTH//skBEXqwM=; b=SgLdRtpq5pHDlWQxP6to+n0phudwo1iPG6qjj3dYlclBVaD2ftipDYbt4pS/PATiRi qv2u6fWk/J/7ZNz5Acd+8JY/bChbhAFrOorv9Z7lPTi5SkdpqocbS6IwHEBv7Z+4XDip RDR6wnm/J8iqAc8sblVF+WHsZoKjM13YaNUG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=kYOLFLl2Wgz+y/7a5Im6RDhp0NniwA5H8yTUi94iUxkkb/4P0qSHrtB8pDKXJJNUml DH8946g996z/1pYpIqWb48kVeN+WD6O9OS1L8i4DfctmVvYVzDteFDyhshJikzK8tEVH rZmzV5iCi6EycPUxYaPyNRx3Wv+EMxJcStRrk= Received: by 10.114.89.1 with SMTP id m1mr1992095wab.146.1212907358380; Sat, 07 Jun 2008 23:42:38 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Sat, 7 Jun 2008 23:42:38 -0700 (PDT) Message-ID: <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> Date: Sat, 7 Jun 2008 23:42:38 -0700 From: "Jack Vogel" To: "Daniel Ponticello" In-Reply-To: <484AFEF1.4040500@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484AFEF1.4040500@skytek.it> Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 06:42:39 -0000 On Sat, Jun 7, 2008 at 2:34 PM, Daniel Ponticello wrote: > Hello, > i'm experiencing periodic kernel panics on a server with FreeBSD 7.0-STABLE > #0: Tue May 20 19:09:43 CEST 2008. > My big problem is that the system is not performing memory dumping and/or > automatic reoboot, > it just stays there. > > Here' console output: > > em0: watchdog timeout -- resetting > kernel trap 12 with interrupts disabled > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic_id = 00 > fault virtual address = 0x14 > fault code = supervisor read, page not present > intruction pointerr = 0x20:0xc056e2ce > stack pointer = 0x28:0xe537fc08 > frame pointer = 0x28:0xe537fc28 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = resume, IOPL = 0 > current process = 29 (em0 taskq) > trap number = 12 > panic: page fault > cpuid = 0 > > > It just stays there, unresponsive (no automatic reboot). > > > > Any ideas? There was a problem in the watchdog path, I don't recall if it was checked in to STABLE, I will check after the weekend. But, there is also the question of why you are in the watchdog path in the first place. Jack From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 06:56:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 35F351065681 for ; Sun, 8 Jun 2008 06:56:17 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id E79FE8FC13 for ; Sun, 8 Jun 2008 06:56:16 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so853253ywe.13 for ; Sat, 07 Jun 2008 23:56:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=brIk2r2ajScUoW5kOPwQcnHdZ/iGQ2/Uwn6YLYhseU0=; b=IUK1K484jEpV/ezSuWjeATJCoFhntoAJ+w+o1idD/bxJ9UXaapLCqc7N47D6ZvJzbP 5y8Ise6DkTNoTkB8oSd78It4joFKxhTD3eTI9kSKko5z3vv1dp9atL+b/nKsEH8xq5at vEE+0i1i/1U96aqNpc4cXSmIk65fMXJNN5Aaw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SK2y2vzTbQzVogOkaooHLHPehFtvGTEvXnnUMnevHRj/jVdyNjAShzRMetl6NrML+2 g8XaZaTM48xJceGl6gwG3GK4BDjQQ+v94i5TTDptvLxVFuaRQoRIKnR+0SpIYaZDWfAA nXTzEh5N5zf6Y0BQjAVtczYrDeuGtrWPrVHpI= Received: by 10.150.229.16 with SMTP id b16mr3681953ybh.123.1212906558705; Sat, 07 Jun 2008 23:29:18 -0700 (PDT) Received: by 10.151.51.5 with HTTP; Sat, 7 Jun 2008 23:29:18 -0700 (PDT) Message-ID: Date: Sat, 7 Jun 2008 23:29:18 -0700 From: "Freddie Cash" To: "FreeBSD Stable" In-Reply-To: <37414AAF-C75A-4292-A174-2198BEF2A7DF@netconsonance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846E637.9080101@samsco.org> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <484736E0.6090004@samsco.org> <4847D5F8.80605@FreeBSD.org> <37414AAF-C75A-4292-A174-2198BEF2A7DF@netconsonance.com> Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 06:56:17 -0000 On 6/7/08, Jo Rhett wrote: > The question I raised is simply: given the number of bugs opened and > fixed since 6.3-RELEASE shipped, why is 6.3 the only supported > version? Why does it make sense for FreeBSD to stop supporting a > stable version and force people to choose between two different > unstable versions? Is this really the right thing to do? Define the terms "stable" and "unstable", how you measure said "stability" and "instability", and what you are comparing them against. Only then can people understand what you are talking about, and can any kind of meaningful dialog occur. Right now, you are saying one thing, people are hearing another, and responding with something else. Oh, and be sure to back things up with actual data, otherwise there's no point in going any further with this. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 07:31:08 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E9CA106564A for ; Sun, 8 Jun 2008 07:31:08 +0000 (UTC) (envelope-from robert@ml.erje.net) Received: from smtpout-2.iphouse.net (smtpout-2.iphouse.net [216.250.188.191]) by mx1.freebsd.org (Postfix) with ESMTP id E74578FC13 for ; Sun, 8 Jun 2008 07:31:07 +0000 (UTC) (envelope-from robert@ml.erje.net) Received: from smtpout-2.iphouse.net (localhost [127.0.0.1]) by outbound-clamsmtpd.iphouse.net (Postfix) with ESMTP id B4FD82AC559 for ; Sun, 8 Jun 2008 02:13:57 -0500 (CDT) Received: from ziemel.erje.net (erje.net [80.126.62.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpout-2.iphouse.net (Postfix) with ESMTP id 5D6672AC556 for ; Sun, 8 Jun 2008 02:13:57 -0500 (CDT) Received: from ismet.erje.net (ismet.erje.net [IPv6:2001:888:1f33::8e45:5e]) by ziemel.erje.net (PostFix 2.5.2) with ESMTP id E5124CA0B26 for ; Sun, 8 Jun 2008 09:13:17 +0200 (CEST) Received: (from robert@localhost) by ismet.erje.net (8.14.2/8.14.2/Submit) id m587DHJf002960 for stable@freebsd.org; Sun, 8 Jun 2008 09:13:17 +0200 (CEST) (envelope-from robert@ml.erje.net) X-Authentication-Warning: ismet.erje.net: robert set sender to robert@ml.erje.net using -f Date: Sun, 8 Jun 2008 09:13:17 +0200 From: Robert Joosten To: stable@freebsd.org Message-ID: <20080608071316.GC973@iphouse.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-ICQ: 13643672 X-geek-code-v3.1: G!>CS@O dx>--@ s: a32(33) C+++ UBL++++$ P++ L-@+++$ !E W(+) N+++(*) o-- K- w- O- M- V- PS+@ PE- Y+ PGP++ t- 5- X- R* !tv b++@ DI++ D G-- e@ h*(+) r>+@ z+c X-FreeBSD: 026746 X-Mobile/GSM/cell: +3162526777 X-msn: BlixKater X-No-rights-can-be-derived: Indeed X-Face: 0[uRd;X4=_;G;$DL6Wm=\]R/TWu1f+t|,Li1Q-maBcUyCJsAw(Nmj-(aDA!Kk#hLr#njX9T@U-rQm?Z53 "_]SBYab3-NCkCN/{1-#0T4U1Ry"TPY~dtpzfxs$9"BrXKPylt/#5QQb/y+|LF}; X-bored-?-crack-this: b938b801a0bfbd5ca4825715039e7574e73af36376314c7c0022cb 1d204f76b3b938b801a0bfbd5ca4825715039e7574fd3ba6fa132c34aff2476c18fe 9286682cd6ee2c70b0bde53fbe6cac3c8b8bb1e73af36376314c7c0022cb1d204f76 b3fe13119fb084fe8bbf5fe3ab7cc89b3bf5302386464f953ed581edac03556e5572 cfd272ace172fa35026445fbef9b0360b725f10c9c85c70d97880dfe8191b3b7269f a2508548e4032c455818f1e321e85dde330c34efb0e526ee3082e4353b12f54a96f6 4443246930da001cafda8b60b725f10c9c85c70d97880dfe8191b3557b444e04c313 4f026cd0055caa1725e73af36376314c7c0022cb1d204f76b3fe13119fb084fe8bbf 5fe3ab7cc89b3bf4d5d0c0671be202bc241807c243e80b User-Agent: Mutt/1.5.17 (2007-11-01) X-ziemel.erje.net-MailScanner: Ok, found to be clean X-Spam-Status: No X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: gmirror patches 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, 08 Jun 2008 07:31:08 -0000 Hi, > Has anybody else had a chance to try the gmirror patches I posted here a > few weeks ago ? > http://www.freebsd.org/cgi/query-pr.cgi?pr=123630 I ran that patch against 7-stable, build flawless. I currently build a kernel, by accident I made a small mistake. I installworld'd but forgot to rebuild/install the kernel, a reboot in between... oh well. That box does collect syslog of abount 8 boxes, mysql in replication modus for backup purposes to a NFS share and is internal fallback mx server so it's somewhat I/O bound. It's a HP LH3 SMP box deployed with gmirror because it lacks scsi raid. So far it runs okay. Any hints I should look for or put into stress ? It's not very important to get this box up ;-) Cheers, Robert From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 09:06:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B9C931065672; Sun, 8 Jun 2008 09:06:00 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id D5A7F8FC18; Sun, 8 Jun 2008 09:05:59 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OPN14158; Sun, 08 Jun 2008 11:05:58 +0200 Message-ID: <484BA0FD.40706@skytek.it> Date: Sun, 08 Jun 2008 11:06:05 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jack Vogel References: <484AFEF1.4040500@skytek.it> <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> In-Reply-To: <2a41acea0806072342q518ac2afo663c91e730c16db@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 09:06:00 -0000 Hello Jack! > > There was a problem in the watchdog path, I don't recall if > it was checked in to STABLE, I will check after the weekend. > > But, there is also the question of why you are in the watchdog > path in the first place. > I tried to apply the latest patch 1.184.2.3 2008/05/21 21:34:05 which includes the watchdog fix you mentioned. Let's see if it helps! No idea of why i'm in the watchdog path, but I forgot to add that this is virtualized VM on VmWare ESX (it emulates em interface)... so i guess it might the cause of why i am in the watchdog path. Do you have any ideas of why i wasn't able to collect dump and the system did not reboot automatically? Thanks, Daniel -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 09:17:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B0081065678 for ; Sun, 8 Jun 2008 09:17:08 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id C99E68FC17 for ; Sun, 8 Jun 2008 09:17:07 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1260254wah.3 for ; Sun, 08 Jun 2008 02:17:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=IAzuZVueFl3Ew8ejo9nKQjc+2P203tN48OCujkCajEg=; b=tRe2kURwmVviusqoPGFZkttLnTOh0LLtcjz83VYVU55+NLb9MvGKSIts9qw1kJlZZo 4CiPkNnfRrhyL0U3f5vEXimlLyW+Y/klx1+Pv+jODjZTk0V0dL9QJ7mgWoZiOlrXMFCL lQHL4+sYUnU33doBVp7K9s5Gnt+ztXk8GaOfk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=SqzUYOdyDK9PANOA4do9nVulGB6O2rzm9+K3a0LI8AoHehXG3YerwlZuikxdCl523D 7beM2+vX52JfIXWrVblM7wb9NNVipayx/dAz6iC1sZNNJPqelFpbEQmX2CVRu1GmJIzm JmZhNm0DjBhcsVwPDcGNicDjowuKpwkZF3w8c= Received: by 10.114.197.10 with SMTP id u10mr2114216waf.47.1212916627122; Sun, 08 Jun 2008 02:17:07 -0700 (PDT) Received: by 10.114.112.6 with HTTP; Sun, 8 Jun 2008 02:17:07 -0700 (PDT) Message-ID: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> Date: Sun, 8 Jun 2008 11:17:07 +0200 From: "Andy Kosela" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: console access 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, 08 Jun 2008 09:17:08 -0000 --On June 7, 2008 2:16:26 PM -0700 Jo Rhett wrote: > On Jun 5, 2008, at 11:35 AM, Paul Schmehl wrote: >> It's not quite that simple. To do that, I have to block out time to >> drive 45 miles during my supposed "off" hours and do the upgrade >> there. Because, if it breaks networking and I'm at home, the server >> will be down for at least an hour until I can drive to the hosting >> company, get access to the server and restore the old kernel. > > Paul, you should arrange with your colocation provider to get an out of > band serial connection to the system, and configure the console to go to > the serial port. We provide that for free at $EMPLOYER and most other > places I know of do it for free or nominal charge. > or if your colocation provider is using any modern server hardware (HP, Dell, IBM) and I bet they do, they should give you lights-out access (HP's ILO2, Dell's DRAC). Then you can even remotely mount iso images from your laptop at home directly on the server (very handy sometimes). -- Andy Kosela ora et labora From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 09:30:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B6B11065673 for ; Sun, 8 Jun 2008 09:30:34 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from nagual.nl (cc20684-a.assen1.dr.home.nl [82.74.10.158]) by mx1.freebsd.org (Postfix) with ESMTP id CBC118FC1F for ; Sun, 8 Jun 2008 09:30:33 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from westmark (westmark.nagual.nl [192.168.11.22]) by nagual.nl (8.13.8+Sun/8.13.8/yanta) with ESMTP id m589V05D017409 for ; Sun, 8 Jun 2008 11:31:00 +0200 (CEST) Date: Sun, 8 Jun 2008 11:30:18 +0200 From: Dick Hoogendijk To: freebsd-stable@freebsd.org Message-ID: <20080608113018.0000228f@westmark> In-Reply-To: References: Organization: de nagual X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.1; i386-pc-solaris2.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 192.168.11.35 Subject: Re: 6.2; 6.3; EOL; combustible discussions 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, 08 Jun 2008 09:30:34 -0000 On Sun, 8 Jun 2008 10:17:20 +0800 "Adrian Chadd" wrote: > and users should be happy that there's even a project here they can > get access to without some kind of warez-like upload/download ratio. Although I agree that FreeBSD's availability to the public is great I do not agree with this "you are a user, so just be happy" attitude. If developers get pissed off by (some) user comments I might understand that, but if they can't deal with "users" and their POVs they might better quit being a developer to an -open- project like FreeBSD and start developing products just for themselves. You have developers in 'flavours'; you also have all sorts of users ;-) > further discussion is just going to upset people even further. :) Being/geeting upset is -always- ones own fault. After all, it's only a discussion, not a war. So why be upset about words? -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D ++ http://nagual.nl/ + SunOS sxde 01/08 ++ From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 09:45:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81D70106567B for ; Sun, 8 Jun 2008 09:45:37 +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 D4EB08FC1B for ; Sun, 8 Jun 2008 09:45:36 +0000 (UTC) (envelope-from hausen@punkt.de) Received: from hugo10.ka.punkt.de (hugo10.ka.punkt.de [10.0.0.110]) by kagate1.punkt.de with ESMTP id m589jZLW069077 for ; Sun, 8 Jun 2008 11:45:35 +0200 (CEST) Received: from hugo10.ka.punkt.de (localhost [127.0.0.1]) by hugo10.ka.punkt.de (8.14.2/8.14.2) with ESMTP id m589jZS7058453; Sun, 8 Jun 2008 11:45:35 +0200 (CEST) (envelope-from ry93@hugo10.ka.punkt.de) Received: (from ry93@localhost) by hugo10.ka.punkt.de (8.14.2/8.14.2/Submit) id m589jYBo058448; Sun, 8 Jun 2008 11:45:34 +0200 (CEST) (envelope-from ry93) Date: Sun, 8 Jun 2008 11:45:34 +0200 From: "Patrick M. Hausen" To: Jo Rhett Message-ID: <20080608094534.GA58022@hugo10.ka.punkt.de> References: <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4847FFDE.8000209@FreeBSD.org> <48480473.3010009@rxsec.com> <484808B8.8070506@FreeBSD.org> <5CCF0D6E-56C1-4EBD-B8A6-955311F7851E@netconsonance.com> <20080607204408.GA39103@hugo10.ka.punkt.de> <4004D1C8-58E4-46E7-B735-4F1CDC5BCCB4@netconsonance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4004D1C8-58E4-46E7-B735-4F1CDC5BCCB4@netconsonance.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 09:45:37 -0000 Hello, On Sat, Jun 07, 2008 at 03:11:42PM -0700, Jo Rhett wrote: > On Jun 7, 2008, at 1:44 PM, Patrick M. Hausen wrote: >> Upgrading your systems to 6.3 takes _precisely_ the same amount >> of work as upgrading to "6-STABLE as of today 00:00 GMT". > > No, it doesn't. You can get to 6.3 with freebsd-update. And you can stay > patched with freebsd-update on a -RELEASE. For a corporation to choose to > stick with -RELEASE makes perfect sense, and it specifically what the > -RELEASE versions were intended for. Correct, that's why we are running RELENG_6_3 on ~40 machines. >> People who have issues with RELENG_6_3 should upgrade to RELENG_6 >> which is perfectly supported. > > I'm sorry, but you clearly don't run RELENG_6 on anything. I run it on two > home computers, and grabbing it on any given day and trying to run with it > in production is insanity. That's not true. I'm running FreeBSD since 1994 and I've run RELENG_N in production at various stages including N = 3, 4, 5 and 6. > Lots and lots of things are committed, > reverted, recommitted, reverted and then finally redesigned. Each of those > steps are often committed to the source tree. Big changes that affect various parts of the system are announced by HEADS UP messages on the -stable mainling list. And by naming "today 00:00" I did not mean to suggest an _arbitrary_ state of the source tree but one you are to _pick_ based on commits and mailing list information. For example, when Jack comitted his fixes for em(4), we set the checkout date to just past he did precisely that. cvsup, make world, reboot, test (!), rollout ... I have never ever had a single problem caused by running RELENG_N. We changed that only because as the number of machines increases it pays to run the same software on all of them, and "RELEASE" provides a convenient (!) reference point for that. Yet, if I were affected by a particular bug in RELENG_6_3, I would simply pick my own later reference point at which the bug is fixed. Kind regards, Patrick -- punkt.de GmbH * Kaiserallee 13a * 76133 Karlsruhe Tel. 0721 9109 0 * Fax 0721 9109 100 info@punkt.de http://www.punkt.de Gf: Jürgen Egeling AG Mannheim 108285 From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 09:53:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 83681106564A for ; Sun, 8 Jun 2008 09:53:40 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD968FC13 for ; Sun, 8 Jun 2008 09:53:39 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 2B50417D26; Sun, 8 Jun 2008 19:53:38 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 1DA6117D9F for ; Sun, 8 Jun 2008 19:53:34 +1000 (EST) Message-ID: <484BAC1C.8080300@modulus.org> Date: Sun, 08 Jun 2008 19:53:32 +1000 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> In-Reply-To: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: console access 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, 08 Jun 2008 09:53:40 -0000 Andy Kosela wrote: > Then you can even > remotely mount iso images from your laptop at home directly on the > server (very handy sometimes). Incidentally, when I tried to use a Supermicro IPMI card for networked remote media, FreeBSD boot loader crashed the machine (video went haywire and it didnt boot). The same thing happened when trying to use a USB CDROM drive, so I suspect USB boot support is at fault somehow. - Andrew From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 11:31:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 230631065672 for ; Sun, 8 Jun 2008 11:31:13 +0000 (UTC) (envelope-from prvs=10451ca0e0=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (core6.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8A5E08FC1B for ; Sun, 8 Jun 2008 11:31:12 +0000 (UTC) (envelope-from prvs=10451ca0e0=killing@multiplay.co.uk) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1212923909; x=1213528709; q=dns/txt; h=Received: Message-ID:From:To:Cc:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=A+KOq6M/2X42AQPHDEC0U eHk6tTJ+x8rnvjz5whoFAM=; b=ahGS3Vz231ZLPLOOrW1b4KV2FwzwxANJ1eS8m 7fKtJbdcORKiVeyimxrSOJN/7AoMq6kZdDWYQncVu+jorsSgb3lR4WhDLrjPwakT 5sc0I6gvjVOzsDWAg7RcMHZHdC5Ljfp/QF2jzgoscN5EeLrN5MBNWgJkc5VZGtpT Z/Ygy4= X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on mail1.multiplay.co.uk X-Spam-Level: X-Spam-Status: No, score=-14.7 required=6.0 tests=BAYES_00, FORGED_MUA_OUTLOOK, USER_IN_WHITELIST,USER_IN_WHITELIST_TO autolearn=ham version=3.1.8 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v9.6.5) with ESMTP id md50005729580.msg for ; Sun, 08 Jun 2008 12:18:28 +0100 X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 212.135.219.182 X-Return-Path: prvs=10451ca0e0=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-stable@freebsd.org Message-ID: <650DAC4C127C447BA6215850F906CC09@multiplay.co.uk> From: "Steven Hartland" To: "Patrick M. Hausen" , "Jo Rhett" References: <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com><4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com><4847FFDE.8000209@FreeBSD.org> <48480473.3010009@rxsec.com><484808B8.8070506@FreeBSD.org><5CCF0D6E-56C1-4EBD-B8A6-955311F7851E@netconsonance.com><20080607204408.GA39103@hugo10.ka.punkt.de><4004D1C8-58E4-46E7-B735-4F1CDC5BCCB4@netconsonance.com> <20080608094534.GA58022@hugo10.ka.punkt.de> Date: Sun, 8 Jun 2008 12:18:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Spam-Processed: mail1.multiplay.co.uk, Sun, 08 Jun 2008 12:18:28 +0100 X-MDAV-Processed: mail1.multiplay.co.uk, Sun, 08 Jun 2008 12:18:29 +0100 Cc: FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 11:31:13 -0000 ----- Original Message ----- From: "Patrick M. Hausen" > I have never ever had a single problem caused by running RELENG_N. > We changed that only because as the number of machines increases > it pays to run the same software on all of them, and "RELEASE" > provides a convenient (!) reference point for that. Yet, if I were > affected by a particular bug in RELENG_6_3, I would simply pick > my own later reference point at which the bug is fixed. An alternative to this is to maintain a specific set of patches to -RELEASE for only the issues / fixes that you are experiencing. This has worked very well for us over the years so I can recommend it as well. Either way you get stable release which you can test and certify in your own environment, keeping regression risks to an absolute minimum. Regards Steve ================================================ This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337 or return the E.mail to postmaster@multiplay.co.uk. From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 11:37:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 970661065674 for ; Sun, 8 Jun 2008 11:37:05 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (core.byshenk.net [62.58.73.230]) by mx1.freebsd.org (Postfix) with ESMTP id 104F88FC14 for ; Sun, 8 Jun 2008 11:37:04 +0000 (UTC) (envelope-from byshenknet@byshenk.net) Received: from core.byshenk.net (localhost.aoes.com [127.0.0.1]) by core.byshenk.net (8.14.2/8.14.2) with ESMTP id m58Bb2Cp001879; Sun, 8 Jun 2008 13:37:02 +0200 (CEST) (envelope-from byshenknet@core.byshenk.net) Received: (from byshenknet@localhost) by core.byshenk.net (8.14.2/8.14.2/Submit) id m58Bb2t4001878; Sun, 8 Jun 2008 13:37:02 +0200 (CEST) (envelope-from byshenknet) Date: Sun, 8 Jun 2008 13:37:02 +0200 From: Greg Byshenk To: FreeBSD Stable Message-ID: <20080608113701.GF1381@core.byshenk.net> References: <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4847FFDE.8000209@FreeBSD.org> <48480473.3010009@rxsec.com> <484808B8.8070506@FreeBSD.org> <5CCF0D6E-56C1-4EBD-B8A6-955311F7851E@netconsonance.com> <20080607204408.GA39103@hugo10.ka.punkt.de> <4004D1C8-58E4-46E7-B735-4F1CDC5BCCB4@netconsonance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4004D1C8-58E4-46E7-B735-4F1CDC5BCCB4@netconsonance.com> User-Agent: Mutt/1.4.2.3i X-Spam-Status: No, score=-1.4 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on core.byshenk.net Cc: Jo Rhett Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 11:37:05 -0000 On Sat, Jun 07, 2008 at 03:11:42PM -0700, Jo Rhett wrote: > On Jun 7, 2008, at 1:44 PM, Patrick M. Hausen wrote: > >>This is why EoLing 6.2 and forcing people to upgrade to a release > >>with lots of known issues is a problem. > >People who have issues with RELENG_6_3 should upgrade to RELENG_6 > >which is perfectly supported. > I'm sorry, but you clearly don't run RELENG_6 on anything. I run it > on two home computers, and grabbing it on any given day and trying to > run with it in production is insanity. Lots and lots of things are > committed, reverted, recommitted, reverted and then finally > redesigned. Each of those steps are often committed to the source > tree. The -RELEASE versions prevent this kind of insanity. I can't speak for Patrick, but I can ad that I very definitely _do_ run RELENG_6 on ~40 machines (web, mail, file, and applications servers), and do so without any serious problems. Which is not to say that there are never problems, but that when there have been problems, they have been uncovered during testing. Of course it is true that "grabbing" something and "trying to run with it in production is insanity". But this (at least IMO) has nothing at all to do with RELENG_X _per_ _se_, as it applies equally to X-RELEASE, and also to any production systems running any other OS. Before we roll out a new RELENG_6 build, we test it first to discover any potential problems -- but this is standard practice for _everything_ that goes into production, including changes to Linux, Solaris, and Windows systems, and also changes to samba, apache, or any other software running on the systems. My point here is that it is the "grabbing" something and throwing it into production without testing that is "insanity", and that this has nothing specifically to do with RELENG_6. I might also add that I have machines that "grab" (actually, pretty much randomly -- that is, "on a given day" and without particular concern from me) RELENG_6 and RELENG_7, and even these machines very rarely exhibit any problems. Of course, these are just test machines, and without the full pre-production testing it is possible that there are some problems in these cases that just don't manifest themselves, but my experience (and, I suspect, that of many others) indicates that your description of RELENG_6 as a seething cauldron of uncertainty is inaccurate. > I'm struggling to find a phrase here that can't be taken to be an > insult, so forgive me and try to understand when I say that you really > should try watching the cvs tree for a bit before making a nonsense > comment like that. You don't seem to have struggled very hard. After all, you could have mad the same point by noting that you consider it a mistake to run RELENG_6 in production. And by not doing this, you have undermined your own position, as it seems clear that there are _many_ people and organizations who run RELENG_6 in production (by which I mean, some version of RELENG_6, and not the tracking of daily changes to RELENG_6), which means that your assertion that such is "nonsense" is itself mistaken. Somewhat more generally, this sort of thing may be why you are getting the amount of push-back you see. That is, what you are claiming seems to match the experience of few (if any) others. As you may have noticed from this thread, the general view (a consensus, seemingly, apart from yourself) is that 6.3 is _better_ (more stable, etc.) than 6.2. Given that such is the case (as it seems very much to be), then the response to your statement that 6.3 isn't good enough of "what exactly is wrong?" seems (at least to me) to be entirely reasonable. When one of my people comes to me and says that something is wrong with X (and particularly when my experience is that there is nothing wrong with X), my first response is almost invariably: "what, specifically, is wrong with X?" -- greg byshenk - gbyshenk@byshenk.net - Leiden, NL From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 11:49:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4AF33106574C for ; Sun, 8 Jun 2008 11:49:36 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 079078FC23 for ; Sun, 8 Jun 2008 11:49:35 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1288457wah.3 for ; Sun, 08 Jun 2008 04:49:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=c4FF8OlmXAvGMOepVAJ0hOIkRrV2dHyWBA5ptiPqPwg=; b=tWexVyz7SXil95r8YMERzBs3HDIy7adIEpX2hxgwA82zMC23nkgnumpcSuRjZrY0mp IVxv2e6n9n5ejMqrO8Lz9iCySYOZ5B3NfUkogQ0j+v+IFWTJxaOxhQFcKOYoOR8U+ApS DQml6hRZP9hoaaPaXLSIpQ93XYxDd0ro13CKM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=G2Y8SpZVYfXBwX1c4Wi4ZdHTBL550vYspwRoRWk38L72DiuGJeQjHZsauOqMuTuPTA AsDQ0yNxqG2msyz198GxMn6QJ45OwlMQB1u57HCJydLn03yjNBUTOEZ/YmddBNY5U3V2 3KVzr8C8azIddvBPUvpZZDLFixAMm6j4F8nRw= Received: by 10.114.148.2 with SMTP id v2mr2149329wad.173.1212925775768; Sun, 08 Jun 2008 04:49:35 -0700 (PDT) Received: by 10.114.112.6 with HTTP; Sun, 8 Jun 2008 04:49:35 -0700 (PDT) Message-ID: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> Date: Sun, 8 Jun 2008 13:49:35 +0200 From: "Andy Kosela" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 11:49:36 -0000 On 6/8/08, Freddie Cash wrote: >>On 6/7/08, Jo Rhett wrote: >> The question I raised is simply: given the number of bugs opened and >> fixed since 6.3-RELEASE shipped, why is 6.3 the only supported >> version? Why does it make sense for FreeBSD to stop supporting a >> stable version and force people to choose between two different >> unstable versions? Is this really the right thing to do? > >Define the terms "stable" and "unstable", how you measure said >"stability" and "instability", and what you are comparing them >against. This whole discussion is really interesting as it clearly showcases two common trends in computing (rapid development vs stability) On the one side we got people (let's call them developers or computer scientists) who are more interested in development than stabilization of the existing code base. It's natural for them to think more about new features, researching new ideas and implementing them. It resembles an academic project, research project.Those computer scientists do not care much about stability, they are mainly interested in hacking on the code for the fun of it. It is open source after all as someone wisely remarked. From my own experience most if not all community based projects are more interested in following this trend than stabilization of the code. Although they do care about stability of their code base, their focus is more on implementing new features and moving rapidly forward. In today's quickly changing world we see this trend as prevailing. On the other hand though, there is a trend which focuses on maximum long term stabilization of the code base. Usually we see this trend in high end commercial companies serving the needs of mission critical businesses where even a minute of downtime can cause loss of thousands of dollars or even loss of lives of people (imagine stock exchanges, banks, financial & insurance institutions, army and police facilities, hospitals, nuclear plants etc.). Those types of businesses/institutions truly needs a maximum stable operating system. They really do not care about "new features", but they do care about maximum stability of the existing code, security, and nonstop business continuity even in the face of natural disasters. There is only one operating system I know of that survived 9/11 attacks - this is OpenVMS. It's not uncommon to see VMS uptimes of more than 10 years (you can ask Amsterdam police for evidence). Now that is a true stability! On the other note though, stability is the direct opposition of development and change. Something which is *stable* cannot change or must change very slowly in the long term. On the other hand something which is changing rapidly cannot by the very definition of it be stable but rather is...unstable. Plato said it very wisely in Timaeus: "What is that which always is and has no becoming; and what is that which is always becoming and never is?". In other words one could say - what is that which is always the same and stable and what is that which is always changing and is unstable? This elaborate thinking is directly connected even with the trends in todays computing. When the code base is changing rapidly and quickly you cannot say it's very stable. Something stable is always something heavy tested and unchanging. So on the one hand we got users like Jo who wants long term stabilization, who depends on FreeBSD to run their mission critical systems, and on the other the developers who are more interested in the *development* than maintaining and supporting older releases for many years. I got to agree with the developers -this is open source project with limited resources. In order to offer long term support the whole focus of the project would have to be changed - and you can't force people to do something they don't want to do in the open source world. It's more fun to work on implementing new code, than squashing bugs or fanatically audit the code in search of security flaws in old releases. The open source is moving very rapidly forward and it's not only FreeBSD. Look at Linux. There is more than 10,000 messages each month on LKML. Kernel.org peoples also do not care much about stability (recent problems with vanilla kernels do support my thesis) - they commit so fast and massively that it becomes real hard to maintain this "beast" even for seasoned hackers. But someone who is sane will not be using kernel.org kernels in mission critical production environments but rather commercial distro kernels like Red Hat's versions. Also they won't be using 8-CURRENT on production systems either. Those are more research projects than operating environments for data centers. But when Red Hat is taking kernel.org kernel and put it out as part of their distro they give 7 (read: seven) years support for that particular kernel, userland and any third party application they support. They backport all security and bug fixes to the "so called" stable release during those seven years. That is a long time in the open source world, as in the general computing world. They can do this because they have resources for that - they are operating as a commercial company. In FreeBSD even if you upgraded cleanly base system (this is very easy and fast now with freebsd-update(8)) there is always problem with ports. I'm perfectly aware that developers are more focused on the base system and ports are served on "as is" basis but most of the production systems deployed worldwide are using ports and depends on them most of their time. I also understand ports team in saying that there is no resources to have many branches of ports tree at the same time, but this little example will show that in the long term sometimes things are not working very smoothly for people who are running mission critical systems. Let's say some hypothetical 6.x-RELEASE comes out in January. The Apache port is freezed at hypothetical 2.0.40 version. Now in April someone discloses some very critical security flaw which affects all versions of Apache prior to 2.0.43. Now what you can do? You can update your Apache port to 2.0.43 fixing a security hole. But at the same time you don't know the upstream team changed dramatically some internal things in code, added tons of new features and at the same time introduced a ton of new bugs and possibly new security flaws which will be founded at a later time. Those changes in code can also very well break your applications which depended on the specific code in 2.0.40 version. So you are left with headaches and backup tapes (of course you would first test the upgrade process on the test machines). But my issue here is that ports really do not offer real stability for mission critical systems who often depends for years on specific versions of particular software (like banks). Red Hat in that case backports new security patches to those old stable versions and it seems it is some solution for such businesses. Of course I know there is no resources for creating supported -SECURITY branch of ports tree which would backport those patches. FreeBSD has always been known for its legendary stability and mature code base which is why many commercial companies depend on it every day. "The anomaly" as someone said of long term support for 4.x releases only helped to see FreeBSD as more stable and viable solution than Linux by many businesses. Mission critical systems needs long term support (read: at least backporting security patches) and stable systems that can run for years without interruption. When it comes to stability vs development maybe there is time to rethink FreeBSD overall strategy and goals. Major companies using FreeBSD in their infrastructure like Yahoo! or Juniper Networks would definetly benefit from such moves focused on long term support of stable releases. I honestly think it is in their interest to support, even financially -- Andy Kosela ora et labora From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:06:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D16151065677; Sun, 8 Jun 2008 12:06:55 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id A31BC8FC20; Sun, 8 Jun 2008 12:06:55 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id B47F41CC031; Sun, 8 Jun 2008 05:06:55 -0700 (PDT) Date: Sun, 8 Jun 2008 05:06:55 -0700 From: Jeremy Chadwick To: Evren Yurtesen Message-ID: <20080608120655.GA50122@eos.sc1.parodius.com> References: <4847072E.5000709@ispro.net> <484713B2.5030200@ispro.net> <48471834.30905@modulus.org> <200806051040.28319.jhb@freebsd.org> <484AA07A.2010308@ispro.net> <20080607164812.GA11072@eos.sc1.parodius.com> <484AEA18.4030901@ispro.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484AEA18.4030901@ispro.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, John Baldwin , Andrew Snow Subject: Re: cpufreq broken on core2duo 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, 08 Jun 2008 12:06:55 -0000 On Sat, Jun 07, 2008 at 11:05:44PM +0300, Evren Yurtesen wrote: > I have tested if it is working or not without using powerd. However you are > right, SpeedStep in bios seem to be adding some ACPI support which looks > like kind of broken. > > In either case, I get error when I have HTT as powerd (powerd -v) is only > able to change 1 CPUs speed (obviously). Perhaps this can be fixed in > future hopefully. I believe you can only adjust the clock frequency of both CPUs/cores on Intel platforms. At least that's how it is under Windows, and under PC BIOSes. If you have a CPU that has dual cores, both cores will have their frequency adjusted. If you have dual physical CPUs that have dual cores, any frequency adjustment should apply to all CPUs. > In the bios, there is also Enhanced C1 support which seems to be reducing > the vcore voltage at the same clock speed. (is this normal even?) Enhanced C1 support allows the CPU to go into a deeper sleep state during idle periods. I recommend enabling it, even on server systems. You can safely enable it on systems using FreeBSD. You might be interested in the utility for Windows called RMClock, which provides an incredible amount of low-level information about CPUs and chipsets. Yes, I know it's for Windows, but if you ever boot Windows, it's a fantastic utility. > This is the motherboard (information from the datacenter): > http://www.supermicro.com/products/motherboard/PD/E7230/PDSML-LN2.cfm > Although kenv | grep smbios show PDSBM can this be or the datacenter is wrong? I can add support for this motherboard to bsdhwmon(8), assuming you can get me a few pieces of information. (Edit: Actually, seems you've already contacted me with this information! Thanks!) I'll need to contact Supermicro to get Winbond interface details, however. That can take a couple weeks. > I just went to bios and says 1.264v so I guess it is safe to assume that > mbmon was showing double. mbmon is showing you invalid values. The fact that it's a value that happens to be double in value is pure chance. mbmon is not properly working with your motherboard. It's that simple. :-) -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:08:52 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD1A61065675; Sun, 8 Jun 2008 12:08:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id B266B8FC0C; Sun, 8 Jun 2008 12:08:52 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id C3AF41CC031; Sun, 8 Jun 2008 05:08:52 -0700 (PDT) Date: Sun, 8 Jun 2008 05:08:52 -0700 From: Jeremy Chadwick To: Daniel Ponticello Message-ID: <20080608120852.GB50122@eos.sc1.parodius.com> References: <484AFEF1.4040500@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484AFEF1.4040500@skytek.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 12:08:53 -0000 On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: > Hello, > i'm experiencing periodic kernel panics on a server with FreeBSD > 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. > My big problem is that the system is not performing memory dumping and/or > automatic reoboot, > it just stays there. Try adjusting some of these sysctl values: hw.acpi.disable_on_reboot hw.acpi.handle_reboot You're using VMware, which may or may not behave properly anyways. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:11:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49D691065675 for ; Sun, 8 Jun 2008 12:11: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 5472C8FC12 for ; Sun, 8 Jun 2008 12:11:24 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-32-123.lns10.adl2.internode.on.net [121.45.32.123]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m58CBLWA059383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 8 Jun 2008 21:41:22 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Sun, 8 Jun 2008 21:41:09 +0930 User-Agent: KMail/1.9.7 References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> In-Reply-To: <484BAC1C.8080300@modulus.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart11337904.sLivlKfHIn"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806082141.16653.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Andrew Snow Subject: Re: console access 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, 08 Jun 2008 12:11:26 -0000 --nextPart11337904.sLivlKfHIn Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 8 Jun 2008, Andrew Snow wrote: > Andy Kosela wrote: > > Then you can even > > remotely mount iso images from your laptop at home directly on the > > server (very handy sometimes). > > Incidentally, when I tried to use a Supermicro IPMI card for > networked remote media, FreeBSD boot loader crashed the machine > (video went haywire and it didnt boot). > > The same thing happened when trying to use a USB CDROM drive, so I > suspect USB boot support is at fault somehow. Try a snapshot made after this commit.. http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/boot/i386/btx/btx/btx.S?rev= =3D1.46;content-type=3Dtext%2Fx-cvsweb-markup (it was MFC'd to RELENG_6 & others on the 18th of March) =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 --nextPart11337904.sLivlKfHIn Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIS8xk5ZPcIHs/zowRAgoeAJ4qIip8wBUjh4mNVlGk9PczhizoTgCfQba4 FSCJTY435i2fX8UCd+YQy9A= =LZ4K -----END PGP SIGNATURE----- --nextPart11337904.sLivlKfHIn-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:12:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8899B1065672 for ; Sun, 8 Jun 2008 12:12:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 535058FC0A for ; Sun, 8 Jun 2008 12:12:34 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 6E4961CC033; Sun, 8 Jun 2008 05:12:34 -0700 (PDT) Date: Sun, 8 Jun 2008 05:12:34 -0700 From: Jeremy Chadwick To: Andrew Snow Message-ID: <20080608121234.GC50122@eos.sc1.parodius.com> References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484BAC1C.8080300@modulus.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: console access 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, 08 Jun 2008 12:12:34 -0000 On Sun, Jun 08, 2008 at 07:53:32PM +1000, Andrew Snow wrote: > Andy Kosela wrote: >> Then you can even >> remotely mount iso images from your laptop at home directly on the >> server (very handy sometimes). > > Incidentally, when I tried to use a Supermicro IPMI card for networked > remote media, FreeBSD boot loader crashed the machine (video went haywire > and it didnt boot). Supermicro IPMI cards are notoriously buggy. A few of the system engineers at Yahoo! who I know continually bitch and moan about how horrible they are. My advice: do not install the IPMI card which is causing your problems. Additionally, the IPMI card which "piggyback" on top of one of the onboard Ethernet ports are going to force the use of something called ASF (at least in Broadcom land it's called that), where the NIC then has two physical MAC addresses -- yes, you read that right! The OS has to have support for that feature for it to work properly, and your local LAN will probably freak out, ARP-wise. > The same thing happened when trying to use a USB CDROM drive, so I suspect > USB boot support is at fault somehow. Booting FreeBSD off of USB devices is known to be broken; see "BTX, boot2, and loader" section at the below URL: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:52:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 155931065682 for ; Sun, 8 Jun 2008 12:52:46 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id 9D0268FC0C for ; Sun, 8 Jun 2008 12:52:45 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id DD72E17DB1; Sun, 8 Jun 2008 22:52:43 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 98A2F171A6; Sun, 8 Jun 2008 22:52:39 +1000 (EST) Message-ID: <484BD615.2020702@modulus.org> Date: Sun, 08 Jun 2008 22:52:37 +1000 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> <20080608121234.GC50122@eos.sc1.parodius.com> In-Reply-To: <20080608121234.GC50122@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: console access 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, 08 Jun 2008 12:52:46 -0000 Jeremy Chadwick wrote: > Supermicro IPMI cards are notoriously buggy. A few of the system > engineers at Yahoo! who I know continually bitch and moan about how > horrible they are. My advice: do not install the IPMI card which is > causing your problems. The remote KVM control feature was an important requirement so the card is staying. Luckily it uses the Intel gigabit NIC which seems to work well in 7-STABLE, I have no complaints so far. Every feature works well except virtual media. > Booting FreeBSD off of USB devices is known to be broken; see "BTX, > boot2, and loader" section at the below URL: > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues Thats interesting - I regularly use USB sticks to boot freebsd as its easier for installation on cluster machines/routers that lack CDROM drives. I've used it on, I think, half a dozen different motherboards/architectures and its worked well on all of them, the Supermicro box was the only broken one. Because virtual media emulates a USB device I'm pretty sure thats why it wasnt working - the USB problem, not a problem with the IPMI card. - Andrew From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 12:58:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5F3AF1065671; Sun, 8 Jun 2008 12:58:55 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 371F48FC15; Sun, 8 Jun 2008 12:58:54 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OSO96953; Sun, 08 Jun 2008 14:58:53 +0200 Message-ID: <484BD795.80502@skytek.it> Date: Sun, 08 Jun 2008 14:59:01 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> In-Reply-To: <20080608120852.GB50122@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 12:58:55 -0000 Hello, disabling acpi is not an option, since i'm running SMP. I have several other systems running 7.0 Release without problems, so it might be something on 7-Stable. Thanks, Daniel Jeremy Chadwick ha scritto: > On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: > >> Hello, >> i'm experiencing periodic kernel panics on a server with FreeBSD >> 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. >> My big problem is that the system is not performing memory dumping and/or >> automatic reoboot, >> it just stays there. >> > > Try adjusting some of these sysctl values: > > hw.acpi.disable_on_reboot > hw.acpi.handle_reboot > > You're using VMware, which may or may not behave properly anyways. > > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:07:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01069106567C; Sun, 8 Jun 2008 13:07:03 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id EB6358FC17; Sun, 8 Jun 2008 13:07:01 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OTP60901; Sun, 08 Jun 2008 15:07:01 +0200 Message-ID: <484BD97C.5000009@skytek.it> Date: Sun, 08 Jun 2008 15:07:08 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> In-Reply-To: <484BD795.80502@skytek.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 13:07:03 -0000 Sorry, I did not read well you suggestion ;) Anyway, the system reboots correctly if I issue the reboot command from command line. Should i adjust those values anyway? Thanks, Daniel Daniel Ponticello ha scritto: > Hello, > disabling acpi is not an option, since i'm running SMP. > I have several other systems running 7.0 Release without problems, > so it might be something on 7-Stable. > > > Thanks, > > Daniel > > > Jeremy Chadwick ha scritto: >> On Sat, Jun 07, 2008 at 11:34:41PM +0200, Daniel Ponticello wrote: >> >>> Hello, >>> i'm experiencing periodic kernel panics on a server with FreeBSD >>> 7.0-STABLE #0: Tue May 20 19:09:43 CEST 2008. >>> My big problem is that the system is not performing memory dumping >>> and/or automatic reoboot, >>> it just stays there. >>> >> >> Try adjusting some of these sysctl values: >> >> hw.acpi.disable_on_reboot >> hw.acpi.handle_reboot >> >> You're using VMware, which may or may not behave properly anyways. >> >> > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:25:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C721B106564A for ; Sun, 8 Jun 2008 13:25:04 +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 550028FC16 for ; Sun, 8 Jun 2008 13:25:03 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from root by ciao.gmane.org with local (Exim 4.43) id 1K5KtK-0005QW-V8 for freebsd-stable@freebsd.org; Sun, 08 Jun 2008 13:25:02 +0000 Received: from 4be54-4-82-234-154-189.fbx.proxad.net ([82.234.154.189]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Jun 2008 13:25:02 +0000 Received: from jaj by 4be54-4-82-234-154-189.fbx.proxad.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 08 Jun 2008 13:25:02 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Jona Joachim Date: Sun, 8 Jun 2008 13:19:00 +0000 (UTC) Lines: 81 Message-ID: X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 4be54-4-82-234-154-189.fbx.proxad.net User-Agent: slrn/0.9.8.1 (FreeBSD) Sender: news Subject: pkg_delete core dump when removing linux-tiff 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, 08 Jun 2008 13:25:05 -0000 Hi! pkg_delete core dumps on me when it tries to remove linux-tiff. I can reproduce this reliably. nirvana# pkg_delete linux-tiff-3.7.1 pkg_delete: file '/compat/linux/usr/bin/bmp2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/fax2ps' doesn't exist pkg_delete: file '/compat/linux/usr/bin/fax2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/gif2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/pal2rgb' doesn't exist pkg_delete: file '/compat/linux/usr/bin/ppm2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/ras2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/raw2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/rgb2ycbcr' doesn't exist pkg_delete: file '/compat/linux/usr/bin/thumbnail' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2bw' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2pdf' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2ps' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2rgba' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffcmp' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffcp' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffdither' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffdump' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffinfo' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffgt' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffmedian' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffset' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffsplit' doesn't exist pkg_delete: file '/compat/linux/usr/lib/libtiff.so.3' doesn't exist pkg_delete: file '/compat/linux/usr/lib/libtiff.so.3.7.1' doesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/COPYRIGHT' doesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/README' doesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/RELEASE-DATE' doesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/VERSION' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/bmp2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/fax2ps.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/fax2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/gif2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/pal2rgb.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/ppm2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/ras2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/raw2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/rgb2ycbcr.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/sgi2tiff.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/thumbnail.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2bw.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2pdf.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2ps.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2rgba.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffcmp.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffcp.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffdither.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffdump.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffinfo.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffgt.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffmedian.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffset.1.gz' doesn't exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffsplit.1.gz' doesn't exist Segmentation fault (core dumped) nirvana# I got caught by this when I was removing a large number of packages using pkg_cutleaves. Not sure why all those files are missing, perhaps pkg_delete removed them the first time before core dumping. It doesn't actually unregister the package. FWIW you can find the core dump here: http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core uname -a FreeBSD nirvana.my.domain 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed May 28 19:35:33 CEST 2008 root@nirvana.my.domain:/usr/obj/usr/src/sys/HYPOCENTER i386 Best regards, Jona -- Pond-erosa Puff wouldn't take no guff Water oughta be clean and free So he fought the fight and he set things right With his OpenBSD From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:31:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1B361065673; Sun, 8 Jun 2008 13:31:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7348FC0C; Sun, 8 Jun 2008 13:31:14 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 470131CC031; Sun, 8 Jun 2008 06:31:14 -0700 (PDT) Date: Sun, 8 Jun 2008 06:31:14 -0700 From: Jeremy Chadwick To: Daniel Ponticello Message-ID: <20080608133114.GA61781@eos.sc1.parodius.com> References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> <484BD97C.5000009@skytek.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484BD97C.5000009@skytek.it> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 13:31:14 -0000 On Sun, Jun 08, 2008 at 03:07:08PM +0200, Daniel Ponticello wrote: > Sorry, I did not read well you suggestion ;) > > Anyway, the system reboots correctly if I issue the reboot command from > command line. > Should i adjust those values anyway? I'd recommend adjusting them and see if the bug (not automatically rebooting on panic) changes. I'm guessing it won't (especially if reboot(8) works fine), but it's worth trying. You're the 2nd person I've seen who has reported this problem (re: FreeBSD not properly rebooting on panic). The other person: http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042250.html I'll add this to my Commonly reported issues Wiki. As for the problem itself, sorry, I have no idea what's causing it. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:36:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E175106564A for ; Sun, 8 Jun 2008 13:36:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 686408FC0C for ; Sun, 8 Jun 2008 13:36:41 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 62E391CC031; Sun, 8 Jun 2008 06:36:41 -0700 (PDT) Date: Sun, 8 Jun 2008 06:36:41 -0700 From: Jeremy Chadwick To: Andrew Snow Message-ID: <20080608133641.GB61781@eos.sc1.parodius.com> References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> <20080608121234.GC50122@eos.sc1.parodius.com> <484BD615.2020702@modulus.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484BD615.2020702@modulus.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: console access 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, 08 Jun 2008 13:36:41 -0000 On Sun, Jun 08, 2008 at 10:52:37PM +1000, Andrew Snow wrote: > Jeremy Chadwick wrote: >> Supermicro IPMI cards are notoriously buggy. A few of the system >> engineers at Yahoo! who I know continually bitch and moan about how >> horrible they are. My advice: do not install the IPMI card which is >> causing your problems. > > The remote KVM control feature was an important requirement so the card is > staying. Luckily it uses the Intel gigabit NIC which seems to work well in > 7-STABLE, I have no complaints so far. Every feature works well except > virtual media. > >> Booting FreeBSD off of USB devices is known to be broken; see "BTX, >> boot2, and loader" section at the below URL: >> >> http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues > > Thats interesting - I regularly use USB sticks to boot freebsd as its > easier for installation on cluster machines/routers that lack CDROM drives. > I've used it on, I think, half a dozen different > motherboards/architectures and its worked well on all of them, the > Supermicro box was the only broken one. Okay, so then your original comment ("The same thing happened when trying to use a USB CDROM drive, so I suspect USB boot support is at fault somehow") might actually not be caused by FreeBSD at all? The reason I say that: > Because virtual media emulates a USB device I'm pretty sure thats why it > wasnt working - the USB problem, not a problem with the IPMI card. What Supermicro box is having USB booting problems? I'm currently in a battle with Supermicro regarding the PDSMi+ not properly booting certain models of USB flash drives: http://koitsu.wordpress.com/2008/04/05/supermicro-pdsmi-bios-bugs/ http://koitsu.wordpress.com/2008/04/26/supermicro-pdsmi-bios-bugs-part-2/ Supermicro currently has both of my USB flash drives which I reported (two different) problems with, and they have confirmed the bug, but are "unsure what's causing it". The last time I heard from them was 3 weeks ago, stating "we're still working on it". (I'd really like my USB drives back......) I would not be surprised if the same problem affected USB CDROMs. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:46:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E62831065687 for ; Sun, 8 Jun 2008 13:46:29 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id A07798FC14 for ; Sun, 8 Jun 2008 13:46:29 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 5D8DE17D98; Sun, 8 Jun 2008 23:46:28 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.20.30.101] (60.218.233.220.exetel.com.au [220.233.218.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id 5C70C171DC; Sun, 8 Jun 2008 23:46:24 +1000 (EST) Message-ID: <484BE2AE.9060604@modulus.org> Date: Sun, 08 Jun 2008 23:46:22 +1000 From: Andrew Snow User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jeremy Chadwick , freebsd-stable@freebsd.org References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> <20080608121234.GC50122@eos.sc1.parodius.com> <484BD615.2020702@modulus.org> <20080608133641.GB61781@eos.sc1.parodius.com> In-Reply-To: <20080608133641.GB61781@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: console access 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, 08 Jun 2008 13:46:30 -0000 Jeremy Chadwick wrote: > Okay, so then your original comment ("The same thing happened when > trying to use a USB CDROM drive, so I suspect USB boot support is at > fault somehow") might actually not be caused by FreeBSD at all? The > reason I say that: OK, good point. I didn't try any other OS, I just tried FreeBSD 6 and 7 off a USB CDROM drive, virtual media CDROM, and virtual media floppy, both of which use USB emulation. I assumed that if I tried, say, a Windows CD, it would just work because that's usually Supermicro's target market. > What Supermicro box is having USB booting problems? Its a rather new X7DWT motherboard (Intel 5400 chipset, Xeon CPU) Good luck with getting your USB drives back :-) - Andrew From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:49:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93F561065676 for ; Sun, 8 Jun 2008 13:49:04 +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 E27DE8FC1A for ; Sun, 8 Jun 2008 13:49:03 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-32-123.lns10.adl2.internode.on.net [121.45.32.123]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m58DmuR5062574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 8 Jun 2008 23:18:57 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Sun, 8 Jun 2008 23:18:46 +0930 User-Agent: KMail/1.9.7 References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <20080608121234.GC50122@eos.sc1.parodius.com> <484BD615.2020702@modulus.org> In-Reply-To: <484BD615.2020702@modulus.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1414166.iciXDZ9TNj"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806082318.47656.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Jeremy Chadwick , Andrew Snow Subject: Re: console access 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, 08 Jun 2008 13:49:04 -0000 --nextPart1414166.iciXDZ9TNj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sun, 8 Jun 2008, Andrew Snow wrote: > Thats interesting - I regularly use USB sticks to boot freebsd as its > easier for installation on cluster machines/routers that lack CDROM > drives. I've used it on, I think, half a dozen different > motherboards/architectures and its worked well on all of them, the > Supermicro box was the only broken one. > > Because virtual media emulates a USB device I'm pretty sure thats why > it wasnt working - the USB problem, not a problem with the IPMI card. Lucky you, every system I've tried it on bar my Dell i8600 laptop failed=20 to boot :) With the btx.S r1.46 commit I was much more successful though. =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 --nextPart1414166.iciXDZ9TNj Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIS+M/5ZPcIHs/zowRAvjSAKCFYPw/KEx48xUPrA+PUJVgr4ClbgCeJhaG TOdEEV90StZYa671t1gL6WQ= =ugCP -----END PGP SIGNATURE----- --nextPart1414166.iciXDZ9TNj-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 13:57:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8816F1065674 for ; Sun, 8 Jun 2008 13:57:57 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED7998FC1A; Sun, 8 Jun 2008 13:57:54 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <484BE563.90102@FreeBSD.org> Date: Sun, 08 Jun 2008 15:57:55 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Jona Joachim References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 08 Jun 2008 13:57:57 -0000 Jona Joachim wrote: > Hi! > > pkg_delete core dumps on me when it tries to remove linux-tiff. > I can reproduce this reliably. > FWIW you can find the core dump here: > http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core You need to obtain the backtrace, see the developers handbook. Kris From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 15:28:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 709A3106566B for ; Sun, 8 Jun 2008 15:28:41 +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 3737D8FC16 for ; Sun, 8 Jun 2008 15:28:41 +0000 (UTC) (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 F413F46C15; Sun, 8 Jun 2008 11:10:28 -0400 (EDT) Date: Sun, 8 Jun 2008 16:10:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Chris Marlatt In-Reply-To: <4848073C.2060509@rxsec.com> Message-ID: <20080608160550.C16871@fledge.watson.org> References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <4846D849.2090005@FreeBSD.org> <4846E14C.709@FreeBSD.org> <48472CCF.8080101@FreeBSD.org> <4847EF62.1070709@rxsec.com> <4847F814.10409@FreeBSD.org> <4847FB1D.1050400@rxsec.com> <4848073C.2060509@rxsec.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Adrian Chadd , FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 15:28:41 -0000 On Thu, 5 Jun 2008, Chris Marlatt wrote: > Adrian Chadd wrote: >> The project is doing what it can with what people are contributing. If > > What if it can accomplish the same or more by simply reorganizing what it's > already doing? I completely understand the apparent situation - if you look > at it from all angles it appears to be no different than that of the people > apposed to the recent scheduling changes FreeBSD has made. There's a limited > amount of people and time to do everything. It's an order-of-magnitude question. The work required to support a release for 48 months is more than double the work required to support a release for 24 months. The current regular and extended support releases reflect a practical balance with respect to how long a release can be support. We provide a much longer timeline of support for *branches*, however, and that's generally the support mechanism recommended for people looking for 4-6 years of support for a version of FreeBSD. If you look at what other OS vendors do -- Microsoft is a particularly easy example to inspect -- they require occasional large-scale updates while you live on a particular branch. For example, if you're going to keep running Win2k for six years, you must install their service packs, not just hot fixes for specific vulnerabilities. Our minor releases on a branch are a *lot* less disruptive than service packs for Windows, and are much more conservative. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 15:52:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1174E1065670; Sun, 8 Jun 2008 15:52:38 +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 B4E9E8FC1A; Sun, 8 Jun 2008 15:52:37 +0000 (UTC) (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 0B45246C06; Sun, 8 Jun 2008 11:52:37 -0400 (EDT) Date: Sun, 8 Jun 2008 16:52:36 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Josh Carroll In-Reply-To: <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com> Message-ID: <20080608164928.L16871@fledge.watson.org> References: <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Adrian Chadd , FreeBSD Stable Subject: Re: 6.2; 6.3; EOL; combustible discussions 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, 08 Jun 2008 15:52:38 -0000 On Sat, 7 Jun 2008, Josh Carroll wrote: > While it would be interesting to see the response here, it still doesn't > necessarily provide a solution. It will still involved developers' time to > QA the user-submitted patches, so it won't entirely eliminate the additional > workload for maintainers. There is also zero (enforceable) accountability. > If X people commit to this, what happens when only a fraction of them > actually do end up helping? Just to be clear here, Adrian's claim that if someone else provided patches for 6.2, they would be committed, is incorrect. The cost of committing the patch is almost zero -- the cost of QA'ing the patch, doing freebsd-update rebuilds, preparing security or errata notices, etc, is extremely real, and the reason that we carefully limit the number of releases we support at once. In fact, I'd argue that we have been supporting too many releases at once, as I think our latency for shipping errata notices and advisories is too high. By reducing the number of releases we support, we improve the speed and attention we can give each notice/advisory, which is an important consideration. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 16:02:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8669B1065685 for ; Sun, 8 Jun 2008 16:02:38 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 077D48FC1D for ; Sun, 8 Jun 2008 16:02:37 +0000 (UTC) (envelope-from michel@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.2/jtpda-5.4) with ESMTP id m58Fn2rY089465 for ; Sun, 8 Jun 2008 17:49:02 +0200 (CEST) X-Ids: 166 Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 0933F23718F for ; Sun, 8 Jun 2008 17:49:01 +0200 (CEST) Received: by niobe.lpthe.jussieu.fr (Postfix, from userid 2005) id B7FDD30; Sun, 8 Jun 2008 17:49:20 +0200 (CEST) Date: Sun, 8 Jun 2008 17:49:20 +0200 From: Michel Talon To: freebsd-stable@freebsd.org Message-ID: <20080608154920.GA8266@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.166]); Sun, 08 Jun 2008 17:49:02 +0200 (CEST) X-Virus-Scanned: ClamAV 0.92/7403/Sun Jun 8 15:52:50 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail.jussieu.fr with ID 484BFF6E.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 484BFF6E.003/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ X-j-chkmail-Score: MSGID : 484BFF6E.003 on jchkmail.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.036 -> S=0.036 X-j-chkmail-Status: Ham Subject: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 16:02:38 -0000 Andy Kosela wrote: ... a really beutiful and elaborate post on the subject ... However, being an ordinary user with few machines running FreeBSD, i have seen on my limited sample that 2 machines worked better with 6.3 than 6.2 (two old Athlon machines, which work perfectly OK in fact) and one worked much worse (a P4 which used to be perfectly stable and suddenly panicked 3 times in a week). So i upgraded this last one to 7.0 and it is now working perfectly well without any trouble. The only "gotcha" is the slowness of X problem when compiling, but i live with that. Moral of the story: the developer base of FreeBSD is not large enough to maintain a large number of releases. In my humble opinion, having 8.0 7.0 and 6.* is even too much. The developers are working on 8.0, they still have a very good grasp of 7.0 but 6.* becomes old stuff, more or less forgotten. It then occurs that things are merged to the 6.* branch which are perhaps susceptible of destabilising it. Personnally i have seen the same occurring with 6.0, 5.0 and 4.*, for me the last releases of the 4.* were very poor on my laptop while the early 4.* releases were perfectly OK. I think it is very unreasonable for end users to ask maintaining, e.g. 6.2 ad vitam eternam. The real stable branch is now 7.* and diverting effort to polish the 6.* is a waste of time. People wanting a very stable system should simply use something else, like Debian stable, official RedHat, etc. whose aim is precisely to offer the maximum stability, with only security and bug fixes, and for extended periods of time. The price you pay is obsoleted and "unsexy" systems, which is probably OK for the intended use. On the other hand i have no business running such a system. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 17:18:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D76391065679; Sun, 8 Jun 2008 17:18:17 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [91.103.162.4]) by mx1.freebsd.org (Postfix) with ESMTP id 82BE28FC2E; Sun, 8 Jun 2008 17:18:17 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from localhost (localhost.codelab.cz [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id C764E19E023; Sun, 8 Jun 2008 19:18:15 +0200 (CEST) Received: from [192.168.1.2] (r5bb235.net.upc.cz [86.49.61.235]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id 9D40319E019; Sun, 8 Jun 2008 19:18:13 +0200 (CEST) Message-ID: <484C1468.6020403@quip.cz> Date: Sun, 08 Jun 2008 19:18:32 +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: cz, cs, en, en-us MIME-Version: 1.0 To: Jeremy Chadwick References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> <20080608121234.GC50122@eos.sc1.parodius.com> In-Reply-To: <20080608121234.GC50122@eos.sc1.parodius.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Andrew Snow Subject: Re: console access 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, 08 Jun 2008 17:18:17 -0000 Jeremy Chadwick wrote: > On Sun, Jun 08, 2008 at 07:53:32PM +1000, Andrew Snow wrote: [...] > Additionally, the IPMI card which "piggyback" on top of one of the > onboard Ethernet ports are going to force the use of something called > ASF (at least in Broadcom land it's called that), where the NIC then > has two physical MAC addresses -- yes, you read that right! The OS has > to have support for that feature for it to work properly, and your local > LAN will probably freak out, ARP-wise. It would be nice to have it better documented in manpage for bge (I know hw.bge.allow_asf is mentioned, but the words does not make it clear to me). It took me a long time before I discovered that I need to add hw.bge.allow_asf="1" in to loader.conf. Since that my eLOM on Sun Fire X2100 M2 servers works nicely without any lockups (mentioned in manpage) >>The same thing happened when trying to use a USB CDROM drive, so I suspect >>USB boot support is at fault somehow. > > > Booting FreeBSD off of USB devices is known to be broken; see "BTX, > boot2, and loader" section at the below URL: > > http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues I am using USB flashdisks with FreeBSD installer with GRUB on HW where older BTX failed. Miroslav Lachman From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 18:04:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF9DC1065678 for ; Sun, 8 Jun 2008 18:04:09 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id 94A818FC13 for ; Sun, 8 Jun 2008 18:04:09 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: by yw-out-2324.google.com with SMTP id 9so909899ywe.13 for ; Sun, 08 Jun 2008 11:04:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to :to:subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=N088f5E9d4VcUL/mgResg8a9Lt0Fdvd/3862lDsfJxY=; b=n3Qs/0afrZGmsBJfSkKd4Rv3cBmxbCPNq8K7gwxZQXwi3jsmtwTIx5QCoemWfAnAFl pw9lbD8CE/7Ggyooyaod9IXMBHm5a/gCE6H0ViWJCOYqZ5TxxHd3nGKk3BMHayJ2wGnQ vqlY6M23PHuxYG3BFDO9urS9QTHmdoUS1agvg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:reply-to:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=p8AS7ms2+E4pjSuTSf6Jh/5tI2p2b3kJ/zP6zwXROtIFv9CwrbE1/jNqfKXN95Ljl0 IDfBs1lXDMbm2SgkYjeVmNSVcrXWcBlpLYtgGuu5oZp8+tsA0rqyyTuxRKK6M4U26D0J dE8JjuOTk/gMgFAB2aMfGaBs9U+wbSmcIoyKY= Received: by 10.150.83.22 with SMTP id g22mr4638467ybb.152.1212948248868; Sun, 08 Jun 2008 11:04:08 -0700 (PDT) Received: by 10.150.53.16 with HTTP; Sun, 8 Jun 2008 11:04:08 -0700 (PDT) Message-ID: Date: Sun, 8 Jun 2008 19:04:08 +0100 From: "Chris Rees" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 18:04:10 -0000 > Zoran Kolic wrote: > > This thread solves nothing. Two positions are clear. > Also, I recall harder words on openbsd list, with a > lot shorter thread. The whole thing is finished and > should stay in that state. All next posts could be > written, but no need to be sent. Aha, perhaps we need to get Theo in to finish it off! Chris From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 18:28:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 365B71065670; Sun, 8 Jun 2008 18:28:45 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 178FD8FC1F; Sun, 8 Jun 2008 18:28:43 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id OYK23444; Sun, 08 Jun 2008 20:28:44 +0200 Message-ID: <484C24E4.5040108@skytek.it> Date: Sun, 08 Jun 2008 20:28:52 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Jeremy Chadwick References: <484AFEF1.4040500@skytek.it> <20080608120852.GB50122@eos.sc1.parodius.com> <484BD795.80502@skytek.it> <484BD97C.5000009@skytek.it> <20080608133114.GA61781@eos.sc1.parodius.com> In-Reply-To: <20080608133114.GA61781@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, freebsd-stable@freebsd.org Subject: Re: kernel panic on em0/taskq 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, 08 Jun 2008 18:28:45 -0000 I just checked the link you have reported. It looks like the problem is present only on SMP machines with both ULE and 4BSD scheduler. I can confirm that the problem is also present on 6.3-Stable. Basically, it freezes before collecting dump and before being able to reboot. I wish i could have more informations to open a PR. Thanks, Daniel Jeremy Chadwick ha scritto: > On Sun, Jun 08, 2008 at 03:07:08PM +0200, Daniel Ponticello wrote: > >> Sorry, I did not read well you suggestion ;) >> >> Anyway, the system reboots correctly if I issue the reboot command from >> command line. >> Should i adjust those values anyway? >> > > I'd recommend adjusting them and see if the bug (not automatically > rebooting on panic) changes. I'm guessing it won't (especially if > reboot(8) works fine), but it's worth trying. > > You're the 2nd person I've seen who has reported this problem (re: > FreeBSD not properly rebooting on panic). The other person: > > http://lists.freebsd.org/pipermail/freebsd-stable/2008-May/042250.html > > I'll add this to my Commonly reported issues Wiki. As for the problem > itself, sorry, I have no idea what's causing it. > > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 18:31:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 597481065671 for ; Sun, 8 Jun 2008 18:31:20 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id EE7EB8FC15 for ; Sun, 8 Jun 2008 18:31:19 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id 59B0AD00F0; Sun, 8 Jun 2008 08:31:17 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id D38FA153882; Sun, 8 Jun 2008 08:31:15 -1000 (HST) Date: Sun, 8 Jun 2008 08:31:15 -1000 From: Clifton Royston To: Steven Hartland Message-ID: <20080608183114.GA3049@lava.net> Mail-Followup-To: Steven Hartland , "Patrick M. Hausen" , Jo Rhett , FreeBSD Stable References: <48472CCF.8080101@FreeBSD.org> <20080608094534.GA58022@hugo10.ka.punkt.de> <650DAC4C127C447BA6215850F906CC09@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <650DAC4C127C447BA6215850F906CC09@multiplay.co.uk> User-Agent: Mutt/1.4.2.2i Cc: Jo Rhett , FreeBSD Stable Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 18:31:20 -0000 On Sun, Jun 08, 2008 at 12:18:22PM +0100, Steven Hartland wrote: > ----- Original Message ----- > From: "Patrick M. Hausen" > > >I have never ever had a single problem caused by running RELENG_N. > >We changed that only because as the number of machines increases > >it pays to run the same software on all of them, and "RELEASE" > >provides a convenient (!) reference point for that. Yet, if I were > >affected by a particular bug in RELENG_6_3, I would simply pick > >my own later reference point at which the bug is fixed. > > An alternative to this is to maintain a specific set of patches > to -RELEASE for only the issues / fixes that you are experiencing. > > This has worked very well for us over the years so I can recommend > it as well. I've done this too. I kept a private 4.8 for years updated with driver and security patches from 4.9 et seq. once 4.8 support was discontinued. Just do the source checkout via CVS and create your own CVS branch. It is more work than I'm prepared for now, where the FreeBSD systems I'm supporting is part-time consulting; that's why I decided to jump to a release line. However, it's a reasonable option for someone who's maintaining their own larger groups of systems. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 18:58:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3056E1065673 for ; Sun, 8 Jun 2008 18:58:55 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id EFA878FC0C for ; Sun, 8 Jun 2008 18:58:54 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id E0EA911438F for ; Sun, 8 Jun 2008 13:58:49 -0500 (CDT) Date: Sun, 08 Jun 2008 13:58:46 -0500 From: Paul Schmehl To: freebsd-stable@freebsd.org Message-ID: In-Reply-To: <484BAC1C.8080300@modulus.org> References: <3cc535c80806080217m413995dej4037fd2aac22ef4b@mail.gmail.com> <484BAC1C.8080300@modulus.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========26717E5BC959D5FAE525==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: console access X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 18:58:55 -0000 --==========26717E5BC959D5FAE525========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 8, 2008 7:53:32 PM +1000 Andrew Snow wrote: > Andy Kosela wrote: >> Then you can even >> remotely mount iso images from your laptop at home directly on the >> server (very handy sometimes). > > Incidentally, when I tried to use a Supermicro IPMI card for networked > remote media, FreeBSD boot loader crashed the machine (video went > haywire and it didnt boot). > > The same thing happened when trying to use a USB CDROM drive, so I > suspect USB boot support is at fault somehow. > Interesting. I have a umass USB drive that causes kernel panics during=20 boot. The rest of the time it works fine. So, I unplug the USB cable to=20 reboot, then plug it back in and mount the drive after I login. Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========26717E5BC959D5FAE525==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 19:04:42 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3B371065672 for ; Sun, 8 Jun 2008 19:04:42 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.250]) by mx1.freebsd.org (Postfix) with ESMTP id 55CFB8FC17 for ; Sun, 8 Jun 2008 19:04:42 +0000 (UTC) (envelope-from gaijin.k@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so451654ana.13 for ; Sun, 08 Jun 2008 12:04:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:cc :in-reply-to:references:content-type:date:message-id:mime-version :x-mailer:content-transfer-encoding; bh=wodIzki5WWc+wqPO3jF8ck0X8/rgLsEIexTOno19/ic=; b=XT4J7zHKuRv3XWUnyn5OR5dzl3SfB7DW35t8y0xAaD5QXkSNQKD8YRaeInItMMRWgx 7+vCUlO7tKe69uhntcfmsVldn9mDDxH5lTBThOT921gLY43COnrPQIshf8CEM8Gv9zNW 5/aKaFlSenCyHUWsmQlL7RxmIUhgkTZzwPhHM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:x-mailer:content-transfer-encoding; b=XHDymWCgPduYIOgWxURH2WF3829PqBLotxQLXK0DqaoI82zC/tnk4I825iUaJHKf/0 iSx4pZC1ywDo1hqLuFJJofeMIHOd6zQqhLXREuWf6zYVGAaNz4XgooTuPE1jnWga8b0M SJPehVAFvn6HWtnqB81omIXRH9ojKu+bEbFcM= Received: by 10.100.128.20 with SMTP id a20mr2538448and.153.1212951881464; Sun, 08 Jun 2008 12:04:41 -0700 (PDT) Received: from ?10.0.3.231? ( [71.250.38.145]) by mx.google.com with ESMTPS id 9sm8088531yxs.5.2008.06.08.12.04.40 (version=SSLv3 cipher=RC4-MD5); Sun, 08 Jun 2008 12:04:40 -0700 (PDT) From: "Alexandre \"Sunny\" Kovalenko" To: Josh Paetzel In-Reply-To: <200806040745.19637.josh@tcbug.org> References: <18501.12329.638264.761303@cs.wpi.edu> <1212506007.48455f97a3788@webmail.vt.edu> <20080604122513.GA24093@eos.sc1.parodius.com> <200806040745.19637.josh@tcbug.org> Content-Type: text/plain; charset=utf-8 Date: Sun, 08 Jun 2008 15:03:33 -0400 Message-Id: <1212951813.1139.0.camel@RabbitsDen> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: Lenovo Thinkpad t61p and FreeBSD? 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, 08 Jun 2008 19:04:42 -0000 On Wed, 2008-06-04 at 07:45 -0500, Josh Paetzel wrote: > On Wednesday 04 June 2008 07:25:13 am Jeremy Chadwick wrote: > > On Tue, Jun 03, 2008 at 11:13:27AM -0400, nlaroche@vt.edu wrote: > > > Quoting nlaroche@vt.edu: > > > > Quoting Jeremy Chadwick : > > > > > Based on my experiences with my workplace-provided T60p, it's safe to > > > > > say I'll never recommend a Lenovo product. The temperatures of these > > > > > laptops are absolutely insane, supported by an incredibly loud fan. > > > > > I'm not interested in a product that can have a GPU reaching > > > > > temperatures of almost 70C **while idling**. > > > > > > > > I purchased a T60p about two months ago and I haven't had any of these > > > > happen (yet?) running Ubuntu 7.10. The machine only gets slightly warm > > > > to the touch after a few hours idling. > > > > > > > > Does your fan run all the time that loud? I'm wondering if there were > > > > changes made at the factory to fix this type of problem if it was wide > > > > spread. > > > > > > > > Regards, > > > > Nick LaRoche > > > > > > That was a T61p not a T60p > > > > It really doesn't matter in this case; T60p, T60p (widescreen), T61p, > > X60p, etc... They all behave the same way when it comes to > > temperatures: incredibly high, sometimes to the point of the system > > shutting off (for some). > > My T60p is really unusable for anything cpu intensive under FreeBSD. Even > with the ibm acpi addons loaded and the fan set to it's highest setting it > only turns at 3700rpm, which isn't enough to keep it from shutting down due > to heat. (eg over 100C) > > I'm interested in whatever cooling solutions people have... > You can read through this thread: http://www.freebsd.org/cgi/getmsg.cgi?fetch=141019+0 +/usr/local/www/db/text/2008/freebsd-acpi/20080217.freebsd-acpi which mentions at least two ways to approach it -- the right one is from the referenced message forward. HTH, -- Alexandre "Sunny" Kovalenko (ОлекÑандр Коваленко) From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 19:11:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1AFF2106564A for ; Sun, 8 Jun 2008 19:11:39 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id DC7C88FC27 for ; Sun, 8 Jun 2008 19:11:38 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id 1E68511438F for ; Sun, 8 Jun 2008 14:11:32 -0500 (CDT) Date: Sun, 08 Jun 2008 14:11:36 -0500 From: Paul Schmehl To: freebsd-stable@freebsd.org Message-ID: <4C198A92A6055152F92E8C36@Macintosh.local> In-Reply-To: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========17181458DAC5857FD966==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 19:11:39 -0000 --==========17181458DAC5857FD966========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 8, 2008 1:49:35 PM +0200 Andy Kosela =20 wrote: > > FreeBSD has always been known for its legendary stability and mature > code base which is why many commercial companies depend on it every > day. "The anomaly" as someone said of long term support for 4.x releases > only helped to see FreeBSD as more stable and viable solution than Linux > by many businesses. Mission critical systems needs long term support > (read: at least backporting security patches) and stable systems that > can run for years without interruption. When it comes to stability vs > development maybe there is time to rethink FreeBSD overall strategy and > goals. Major companies using FreeBSD in their infrastructure like Yahoo! > or Juniper Networks would definetly benefit from such moves focused on > long term support of stable releases. I honestly think it is in their > interest to support, even financially Interesting thoughts. Maybe the time is ripe for a RedHat-like support=20 company for FreeBSD. Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========17181458DAC5857FD966==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 19:25:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3E4681065680 for ; Sun, 8 Jun 2008 19:25:31 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id 0DFCA8FC0C for ; Sun, 8 Jun 2008 19:25:30 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id 2AF9611438F for ; Sun, 8 Jun 2008 14:25:25 -0500 (CDT) Date: Sun, 08 Jun 2008 14:25:28 -0500 From: Paul Schmehl To: FreeBSD Stable Message-ID: <5A8D6D5A88275154227302D9@Macintosh.local> In-Reply-To: <20080608164928.L16871@fledge.watson.org> References: <8cb6106e0806071938x6a524ba4o969fbc4f0c85206@mail.gmail.com> <20080608164928.L16871@fledge.watson.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========2D940CB77D2C2B1992C1==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: 6.2; 6.3; EOL; combustible discussions X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 19:25:31 -0000 --==========2D940CB77D2C2B1992C1========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 8, 2008 4:52:36 PM +0100 Robert Watson =20 wrote: > > Just to be clear here, Adrian's claim that if someone else provided > patches for 6.2, they would be committed, is incorrect. The cost of > committing the patch is almost zero -- the cost of QA'ing the patch, > doing freebsd-update rebuilds, preparing security or errata notices, > etc, is extremely real, and the reason that we carefully limit the > number of releases we support at once. In fact, I'd argue that we have > been supporting too many releases at once, as I think our latency for > shipping errata notices and advisories is too high. By reducing the > number of releases we support, we improve the speed and attention we can > give each notice/advisory, which is an important consideration. > What would be the most beneficial boost to FreeBSD? Would it be cash?=20 Additional developers? Does FreeBSD have anyone who works fulltime (IOW, is paid)? Would more fulltime workers alleviate the issues you've articulated? Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========2D940CB77D2C2B1992C1==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 19:29:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F32C11065671 for ; Sun, 8 Jun 2008 19:29:55 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from mail.stovebolt.com (mail.stovebolt.com [66.221.101.249]) by mx1.freebsd.org (Postfix) with ESMTP id C47DF8FC1F for ; Sun, 8 Jun 2008 19:29:55 +0000 (UTC) (envelope-from pschmehl_lists@tx.rr.com) Received: from [192.168.2.102] (cpe-24-175-90-48.tx.res.rr.com [24.175.90.48]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.stovebolt.com (Postfix) with ESMTPSA id A466811438F for ; Sun, 8 Jun 2008 14:29:49 -0500 (CDT) Date: Sun, 08 Jun 2008 14:29:53 -0500 From: Paul Schmehl To: freebsd-stable@freebsd.org Message-ID: In-Reply-To: <20080608154920.GA8266@lpthe.jussieu.fr> References: <20080608154920.GA8266@lpthe.jussieu.fr> X-Mailer: Mulberry/4.0.8 (Mac OS X) X-Munged-Reply-To: To reply - figure it out MIME-Version: 1.0 Content-Type: multipart/signed; micalg=sha1; protocol="application/pkcs7-signature"; boundary="==========7250A5E0FE510BDA8521==========" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 19:29:56 -0000 --==========7250A5E0FE510BDA8521========== Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --On June 8, 2008 5:49:20 PM +0200 Michel Talon =20 wrote: > > I think it is very unreasonable for end users to ask maintaining, e.g. > 6.2 ad vitam eternam. The real stable branch is now 7.* and diverting > effort to polish the 6.* is a waste of time. People wanting a very > stable system should simply use something else, like Debian stable, > official RedHat, etc. whose aim is precisely to offer the maximum > stability, with only security and bug fixes, and for extended periods of > time. The price you pay is obsoleted and "unsexy" systems, which is > probably OK for the intended use. On the other hand i have no business > running such a system. Please do understand that for some of us, these are not choices. I wiped=20 a FreeBSD machine and bought and installed RedHat because a vendor's=20 software would only run on RedHat. The experience was a painful one.=20 RedHat's updates are a pure PITA. The box now runs FreeBSD again, and I=20 doubt I will ever experiment with something else again. If I can't have FreeBSD, I won't run a server. I don't think I'm alone. Paul Schmehl If it isn't already obvious, my opinions are my own and not those of my employer. --==========7250A5E0FE510BDA8521==========-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 19:49:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0525C106573C; Sun, 8 Jun 2008 19:49:01 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from outgoing01.lava.net (cake.lava.net [IPv6:2001:1888:0:1:230:48ff:fe5b:3b50]) by mx1.freebsd.org (Postfix) with ESMTP id 3BF708FC1D; Sun, 8 Jun 2008 19:49:01 +0000 (UTC) (envelope-from cliftonr@lava.net) Received: from malasada.lava.net (malasada.lava.net [64.65.64.17]) by outgoing01.lava.net (Postfix) with ESMTP id B2ED2D0087; Sun, 8 Jun 2008 09:49:00 -1000 (HST) Received: by malasada.lava.net (Postfix, from userid 102) id 65B9E153882; Sun, 8 Jun 2008 09:49:00 -1000 (HST) Date: Sun, 8 Jun 2008 09:49:00 -1000 From: Clifton Royston To: Adrian Chadd Message-ID: <20080608194859.GC3049@lava.net> Mail-Followup-To: Adrian Chadd , FreeBSD Stable References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.2i Cc: FreeBSD Stable Subject: Re: 6.2; 6.3; EOL; combustible discussions 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, 08 Jun 2008 19:49:03 -0000 On Sun, Jun 08, 2008 at 10:17:20AM +0800, Adrian Chadd wrote: > Ok everyone, I think thats enough about this for now. > > I think the developers and users have made their points clear, and > they're no going to agree any more (but they may agree less) over > time. Well, *please* don't assume all users agree with Jo. Some of us actually read the EOL date on 6.2, assumed it meant what it said, and made an informed decision to use 6.2 as the best candidate available at that date, even knowing we'd be forced to upgrade sooner rather than later. If as an admin/user I could give a message to the developers, it would be a very different one: I would like to one day see a -STABLE line, perhaps 8.x, perhaps later, which would by *design* be strong enough and incorporate enough flexibility in its core design that it could be continued for as many as 5 years of minor releases (rather than by *default* as 4.x was due to the difficulty of the SMP model transition and the 5.x stability problems.) If I knew that were an eventual development goal, I'd be even happier with the FreeBSD development team. I have no damn idea how to achieve that goal, and as a software developer I know it's ridiculously, insanely difficult to design to a goal like that, but I do think that continuation is one of the main factors behind the nostalgia for the 4.x line. -- Clifton -- Clifton Royston -- cliftonr@iandicomputing.com / cliftonr@lava.net President - I and I Computing * http://www.iandicomputing.com/ Custom programming, network design, systems and network consulting services From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 20:43:17 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D14F1065684 for ; Sun, 8 Jun 2008 20:43:17 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from cenn-smtp.mc.mpls.visi.com (cenn.mc.mpls.visi.com [208.42.156.9]) by mx1.freebsd.org (Postfix) with ESMTP id E39B58FC28 for ; Sun, 8 Jun 2008 20:43:16 +0000 (UTC) (envelope-from josh@tcbug.org) Received: from mail.tcbug.org (mail.tcbug.org [208.42.70.163]) by cenn-smtp.mc.mpls.visi.com (Postfix) with ESMTP id 6079E8126; Sun, 8 Jun 2008 15:13:47 -0500 (CDT) Received: from build64.tcbug.org (unknown [208.42.70.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tcbug.org (Postfix) with ESMTPS id 2BC575589CC; Sun, 8 Jun 2008 15:13:47 -0500 (CDT) From: Josh Paetzel To: "Alexandre \"Sunny\" Kovalenko" Date: Sun, 8 Jun 2008 15:13:36 -0500 User-Agent: KMail/1.9.7 References: <18501.12329.638264.761303@cs.wpi.edu> <200806040745.19637.josh@tcbug.org> <1212951813.1139.0.camel@RabbitsDen> In-Reply-To: <1212951813.1139.0.camel@RabbitsDen> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4720874.lf9a3LYWdm"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806081513.41554.josh@tcbug.org> Cc: stable@freebsd.org Subject: Re: Lenovo Thinkpad t61p and FreeBSD? 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, 08 Jun 2008 20:43:17 -0000 --nextPart4720874.lf9a3LYWdm Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Sunday 08 June 2008 02:03:33 pm Alexandre "Sunny" Kovalenko wrote: > On Wed, 2008-06-04 at 07:45 -0500, Josh Paetzel wrote: > > On Wednesday 04 June 2008 07:25:13 am Jeremy Chadwick wrote: > > > On Tue, Jun 03, 2008 at 11:13:27AM -0400, nlaroche@vt.edu wrote: > > > > Quoting nlaroche@vt.edu: > > > > > Quoting Jeremy Chadwick : > > > > > > Based on my experiences with my workplace-provided T60p, it's > > > > > > safe to say I'll never recommend a Lenovo product. The > > > > > > temperatures of these laptops are absolutely insane, supported = by > > > > > > an incredibly loud fan. I'm not interested in a product that can > > > > > > have a GPU reaching temperatures of almost 70C **while idling**. > > > > > > > > > > I purchased a T60p about two months ago and I haven't had any of > > > > > these happen (yet?) running Ubuntu 7.10. The machine only gets > > > > > slightly warm to the touch after a few hours idling. > > > > > > > > > > Does your fan run all the time that loud? I'm wondering if there > > > > > were changes made at the factory to fix this type of problem if it > > > > > was wide spread. > > > > > > > > > > Regards, > > > > > Nick LaRoche > > > > > > > > That was a T61p not a T60p > > > > > > It really doesn't matter in this case; T60p, T60p (widescreen), T61p, > > > X60p, etc... They all behave the same way when it comes to > > > temperatures: incredibly high, sometimes to the point of the system > > > shutting off (for some). > > > > My T60p is really unusable for anything cpu intensive under FreeBSD.=20 > > Even with the ibm acpi addons loaded and the fan set to it's highest > > setting it only turns at 3700rpm, which isn't enough to keep it from > > shutting down due to heat. (eg over 100C) > > > > I'm interested in whatever cooling solutions people have... > > =EF=BB=BFYou can read through this thread: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=3D141019+0 > +/usr/local/www/db/text/2008/freebsd-acpi/20080217.freebsd-acpi > > which mentions at least two ways to approach it -- the right one is from > the referenced message forward. > > HTH, So in doing some more research I finally got together the nerve to disassem= ble=20 my laptop. After cleaning a massive amount of thermal paste off the cpu an= d=20 heatsink it's operating around 60C after multiple make -j4 buildworlds, whe= re=20 it used to shut down due to going over 100C. It seems I'm not the first person to discover this was the root cause of th= eir=20 heat and noise problems with their Lenovo T60/61 laptop. I've also been able to turn over control of the fan back to the BIOS as=20 opposed to running it full out all the time. =2D-=20 Thanks, Josh Paetzel PGP: 8A48 EF36 5E9F 4EDA 5A8C 11B4 26F9 01F1 27AF AECB --nextPart4720874.lf9a3LYWdm Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEABECAAYFAkhMPXUACgkQJvkB8Sevrsv7iwCeJI5Xnrm9g6uxqv7FtZKZKE5c nqcAoIod/MjVP3jfQkbIHwVJ69VYb12G =lcFC -----END PGP SIGNATURE----- --nextPart4720874.lf9a3LYWdm-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 20:55:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1872B106566C for ; Sun, 8 Jun 2008 20:55:12 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 9C3858FC19 for ; Sun, 8 Jun 2008 20:55:11 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m58Kt7PJ004343 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 9 Jun 2008 06:55:09 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m58Kt7ST071185; Mon, 9 Jun 2008 06:55:07 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m58Kt7LC071184; Mon, 9 Jun 2008 06:55:07 +1000 (EST) (envelope-from peter) Date: Mon, 9 Jun 2008 06:55:06 +1000 From: Peter Jeremy To: Michel Talon , freebsd-stable@freebsd.org Message-ID: <20080608205506.GI67629@server.vk2pj.dyndns.org> References: <20080608154920.GA8266@lpthe.jussieu.fr> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="x1F0m3RQhDZyj8sd" Content-Disposition: inline In-Reply-To: <20080608154920.GA8266@lpthe.jussieu.fr> X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 20:55:12 -0000 --x1F0m3RQhDZyj8sd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-08 17:49:20 +0200, Michel Talon wrote: >and it is now working perfectly well without any trouble. The only >"gotcha" is the slowness of X problem when compiling, but i live with that. Have you tried SCHED_ULE? In my experience, it does a better job of scdeduling than SCHED_4BSD, even on UP machines (YMMV). >which are perhaps susceptible of destabilising it. Personnally i have >seen the same occurring with 6.0, 5.0 and 4.*, for me the last releases >of the 4.* were very poor on my laptop while the early 4.* releases were >perfectly OK. =20 The difficulty with the later 4.x releases was that there were major differences between the 4.x and later kernels and this made it increasingly difficult to backport bugfixes. This is less of an issue with now 4.x is out of the way. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --x1F0m3RQhDZyj8sd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhMRyoACgkQ/opHv/APuIfVrACgxBeYGtq6kuqyRCquTq968eON pXwAnjrIcz0s8Yv0ZLXV1KLDY5cH4DUg =zbJz -----END PGP SIGNATURE----- --x1F0m3RQhDZyj8sd-- From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 21:26:20 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CAE3106567A for ; Sun, 8 Jun 2008 21:26:20 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from exchfe01.datapipe-corp.net (exchfe01.datapipe-corp.net [64.106.130.69]) by mx1.freebsd.org (Postfix) with ESMTP id D68408FC0A for ; Sun, 8 Jun 2008 21:26:19 +0000 (UTC) (envelope-from msaad@datapipe.com) Received: from cookbook.lan (192.168.128.20) by exchfe01.datapipe-corp.net (64.106.130.71) with Microsoft SMTP Server id 8.0.783.2; Sun, 8 Jun 2008 17:26:17 -0400 Message-ID: <484C4E6D.7060306@datapipe.com> Date: Sun, 8 Jun 2008 17:26:05 -0400 From: Mark Saad User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: References: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> In-Reply-To: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Andy Kosela Subject: Re: Current status of support for high end SAN hardware X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: msaad@datapipe.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jun 2008 21:26:20 -0000 Andy I am currently using HP MSA1500cs SAN setups on FreeBSD 7 and 6.3 using qlogic cards in HP DL380G4 and G5 servers. I am not yet using multipath fiber channel which is supported in 7 and I want to test this out soon. As for Redhat ES 4 and 5 I am also using the same hardware setup , I have to say that RedHat ES4 works better for me the Enterprise 5 . ES5 has some odd ball networking issues, when you upgrade from say update 0 -> 1 or 1 -> 2. For some reason Redhat decided that it needed to remove your configs for eth0 as part of the upgrade. I would say to look at using 64Bit FreeBSD 7-RELEASE and ZFS as the filesystem on the SAN. ZFS is hands down better then EXT3+LVM . Andy Kosela wrote: > Hi all, > What is the current status of support for high end SAN hardware in FreeBS= D? > I'm especially interested in support for HP EVA/XP disk arrays, Qlogic > HBAs, multipathing. > How FreeBSD compares in this environment to RHEL 5? > > -- > Andy Kosela > ora et labora > _______________________________________________ > 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 Saad Managed UNIX Support DataPipe Managed Global IT Services () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments This message may contain confidential or privileged information. If you ar= e not the intended recipient, please advise us immediately and delete this = message. See http://www.datapipe.com/emaildisclaimer.aspx for further info= rmation on confidentiality and the risks of non-secure electronic communica= tion. If you cannot access these links, please notify us by reply message a= nd we will send the contents to you. From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 22:13:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5AE3D106566C for ; Sun, 8 Jun 2008 22:13:37 +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 02E708FC18 for ; Sun, 8 Jun 2008 22:13:36 +0000 (UTC) (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 E531E46C3B; Sun, 8 Jun 2008 18:13:35 -0400 (EDT) Date: Sun, 8 Jun 2008 23:13:35 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andy Kosela In-Reply-To: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> Message-ID: <20080608230037.F84920@fledge.watson.org> References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 22:13:37 -0000 On Sun, 8 Jun 2008, Andy Kosela wrote: >> Define the terms "stable" and "unstable", how you measure said "stability" >> and "instability", and what you are comparing them against. > > This whole discussion is really interesting as it clearly showcases two > common trends in computing (rapid development vs stability) On the one side > we got people (let's call them developers or computer scientists) who are > more interested in development than stabilization of the existing code base. > It's natural for them to think more about new features, researching new > ideas and implementing them. It resembles an academic project, research > project. ... > On the other hand though, there is a trend which focuses on maximum long > term stabilization of the code base. Usually we see this trend in high end > commercial companies serving the needs of mission critical businesses where > even a minute of downtime can cause loss of thousands of dollars or even > loss of lives of people (imagine stock exchanges, banks, financial & > insurance institutions, army and police facilities, hospitals, nuclear > plants etc.). Those types of businesses/institutions truly needs a maximum > stable operating system. They really do not care about "new features", but > they do care about maximum stability of the existing code, security, and > nonstop business continuity even in the face of natural disasters. I think there are some important truths to your observations, but let me present a contrarian view: I think you are presenting a false dichotomy, unnecessarily pitting developers and users at odds with respect to the goals of the project. There are definitely points of conflict along these lines, but much of the time the reason that people use FreeBSD is precisely because there *is* agreement on these points. There are many FreeBSD developers who work on FreeBSD precisely because their employer uses FreeBSD, and hence directly represent interests of long-term support, stability, etc. And indeed, as you observe, these are the interests of large web hosts, appliance companies, etc, being required to build their products. We have a highly branched development in order to reflect the varying degrees of both investment in and tolerance for different levels of feature development vs. stability. If FreeBSD developers only hung around to do adventurous new feature development, we wouldn't have -STABLE branches, errata/security branches, freebsd-update, and so on. Instead, we have a very large infrastructure and a lot of developer time invested in those areas, and this has been growing over time. For example, we introduced RELENG_X_Y errata/security branches in the 4.x timeframe to better serve communities with a low tolerance for feature change. Prior to that time, users had to directly manage patches themselves if they wanted to avoid sliding forward on -STABLE. Likewise, in the mid-5.x timeframe, we added Perforce so that developers wanting to work on projects with very high levels of instability could do so without disrupting HEAD as much, which both improved the pace of development and lead to a more stable product by avoiding allowing the HEAD to become extremely unstable. The recent and rather contentious discussion is not taking place because FreeBSD developers feel that, philosophically, longer support timelines for releases are undesirable. Rather, the argument being made is that, given the underlying assumption of finite resources already committed to particular ends, we should moderate the degree to which we support old releases so that we can keep producing new ones. Don't think that the same trade-offs and hard choices don't have to be made in the development HEAD: in the past, we've pushed back several major features over time due to concerns about stability or availability of developers, which have been far more contentious. Just a thought... :-) Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 22:18:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 123611065670 for ; Sun, 8 Jun 2008 22:18:24 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by mx1.freebsd.org (Postfix) with ESMTP id 308D38FC12 for ; Sun, 8 Jun 2008 22:18:23 +0000 (UTC) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.14.2/jtpda-5.4) with ESMTP id m58LY3jP047023 ; Sun, 8 Jun 2008 23:34:03 +0200 (CEST) X-Ids: 165 Received: from asmodee.lpthe.jussieu.fr (asmodee.lpthe.jussieu.fr [134.157.10.34]) by parthe.lpthe.jussieu.fr (Postfix) with ESMTP id 46D6A2377A0; Sun, 8 Jun 2008 23:34:02 +0200 (CEST) Received: by asmodee.lpthe.jussieu.fr (Postfix, from userid 2005) id 43AAB42F9; Sun, 8 Jun 2008 23:34:02 +0200 (CEST) Date: Sun, 8 Jun 2008 23:34:02 +0200 From: Michel Talon To: Peter Jeremy Message-ID: <20080608213401.GA74048@lpthe.jussieu.fr> Mail-Followup-To: Michel Talon , Peter Jeremy , freebsd-stable@freebsd.org References: <20080608154920.GA8266@lpthe.jussieu.fr> <20080608205506.GI67629@server.vk2pj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080608205506.GI67629@server.vk2pj.dyndns.org> User-Agent: Mutt/1.4.2.2i X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (shiva.jussieu.fr [134.157.0.165]); Sun, 08 Jun 2008 23:34:03 +0200 (CEST) X-Virus-Scanned: ClamAV 0.92/7404/Sun Jun 8 18:19:18 2008 on shiva.jussieu.fr X-Virus-Status: Clean X-Miltered: at jchkmail2.jussieu.fr with ID 484C342D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 484C342D.000/134.157.10.1/parthe.lpthe.jussieu.fr/parthe.lpthe.jussieu.fr/ X-j-chkmail-Score: MSGID : 484C342D.000 on jchkmail2.jussieu.fr : j-chkmail score : . : R=. U=. O=. B=0.037 -> S=0.037 X-j-chkmail-Status: Ham Cc: freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 22:18:24 -0000 On Mon, Jun 09, 2008 at 06:55:06AM +1000, Peter Jeremy wrote: > On 2008-Jun-08 17:49:20 +0200, Michel Talon wrote: > >and it is now working perfectly well without any trouble. The only > >"gotcha" is the slowness of X problem when compiling, but i live with that. > > Have you tried SCHED_ULE? In my experience, it does a better job of > scdeduling than SCHED_4BSD, even on UP machines (YMMV). Yes, i run with SCHED_ULE, the machine is less interactive than with 6.2 when compiling, but, as i said, i don't care much about that. What i really don't like is panicking, and with 7.0 my machine is perfectly stable. On the other hand, many tasks run very fast under 7.0, so, overall i am very happy with this version. -- Michel TALON From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 22:27:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9E74106568E for ; Sun, 8 Jun 2008 22:27:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.28]) by mx1.freebsd.org (Postfix) with ESMTP id 7DFD58FC16 for ; Sun, 8 Jun 2008 22:27:56 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so940592ywe.13 for ; Sun, 08 Jun 2008 15:27:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=iqwwbYDTvlnTHDzwCIryvXFcIWv/y9eiI3TJXsPKi6E=; b=lFFk916arcsGzD3DssdfBepuWbJyQG/7a7bp+1yXb6cGSMgHMO5V66oHwSSZZ31U4J tAz07bHqauK7XF9GMJIF3KFAOKbx1EqyMJHAQ9NqUWnNV+xf9m9JWCcsXm4OByz0SRJS PJM/n+KxQUFFUiAfjrEl/bEG2cChpOFOGJDtQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=wAj+DMtwYj/pDJiZAjS0msU2l1h71L3fIYEKG5mmFJ+ARoXC2Zr+G7G67yY6Ykyy5J ZVhM6iqoc5smwYPBMxVl848e2OH9XZcKpCMT/fnoVHk9aNNNXeCLVWUqxzbIBaikZYK1 w9Ntan0rAcW/Zad3BorzTjKVK68b6hzQewNQU= Received: by 10.151.109.11 with SMTP id l11mr5024279ybm.138.1212964075176; Sun, 08 Jun 2008 15:27:55 -0700 (PDT) Received: by 10.151.51.5 with HTTP; Sun, 8 Jun 2008 15:27:55 -0700 (PDT) Message-ID: Date: Sun, 8 Jun 2008 15:27:55 -0700 From: "Freddie Cash" To: freebsd-stable@freebsd.org In-Reply-To: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 22:27:56 -0000 On Sun, Jun 8, 2008 at 4:49 AM, Andy Kosela wrote: > On 6/8/08, Freddie Cash wrote: >>>On 6/7/08, Jo Rhett wrote: >>> The question I raised is simply: given the number of bugs opened and >>> fixed since 6.3-RELEASE shipped, why is 6.3 the only supported >>> version? Why does it make sense for FreeBSD to stop supporting a >>> stable version and force people to choose between two different >>> unstable versions? Is this really the right thing to do? >> >>Define the terms "stable" and "unstable", how you measure said >>"stability" and "instability", and what you are comparing them >>against. > > This whole discussion is really interesting as it clearly showcases two > common trends in computing (rapid development vs stability) Like I said, you have to define what you mean by "stable" and "unstable" before the discussion can continue. "stable" can mean many things to many people. You talk about feature stability. Other may talk about "number of open bugs" as being unstable. Others may talk of API/ABI stability. Other may mean "code that don't crash a system". Your view of "stable" meaning "features don't change" is no where near my definition of stable (systems that don't crash, and where I can run binaries from older point releases on newer point releases). The joy of English is that words are overloaded with multiple meanings. And until everyone agrees on which meaning of the words they are using, there's very little point in discussing things ... as everyone will be talking about something different. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Sun Jun 8 22:41:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70D33106566B for ; Sun, 8 Jun 2008 22:41:26 +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 445418FC14 for ; Sun, 8 Jun 2008 22:41:26 +0000 (UTC) (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 D86D346BA9; Sun, 8 Jun 2008 18:41:25 -0400 (EDT) Date: Sun, 8 Jun 2008 23:41:25 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Freddie Cash In-Reply-To: Message-ID: <20080608233332.R84920@fledge.watson.org> References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 08 Jun 2008 22:41:26 -0000 On Sun, 8 Jun 2008, Freddie Cash wrote: >>> Define the terms "stable" and "unstable", how you measure said "stability" >>> and "instability", and what you are comparing them against. >> >> This whole discussion is really interesting as it clearly showcases two >> common trends in computing (rapid development vs stability) > > Like I said, you have to define what you mean by "stable" and "unstable" > before the discussion can continue. > > "stable" can mean many things to many people. You talk about feature > stability. Other may talk about "number of open bugs" as being unstable. > Others may talk of API/ABI stability. Other may mean "code that don't crash > a system". > > Your view of "stable" meaning "features don't change" is no where near my > definition of stable (systems that don't crash, and where I can run binaries > from older point releases on newer point releases). I think very few companies that use FreeBSD want it to be like OpenVMS -- otherwise they'd be using OpenVMS. Companies, and users generally, come to FreeBSD not just because they want system stability over time, but also because they expect us to keep producing new (yet mature) features. Sure, they may claim otherwise, but in practice they discover they do want FreeBSD to support the latest rev of an ethernet chipset on a motherboard because the replacement parts they received from their hardware vendor have it, support for larger disk sizes, support for a new POSIX API, being able to boot on systems that require (rather than just support) ACPI, etc. And those changes, perhaps individually incremental, add up to significant changes requiring new releases quite quickly. Again, I wouldn't argue that we couldn't further improve things, but at the same time, we have to recognize that any discussion about "improvement" in a world of finite resources requires a change in the set of trade-offs we accept. This is one reason why such discussions get contention, because one person's easy win from a change becomes another person's loss. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 01:10:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9DD41065670; Mon, 9 Jun 2008 01:10:47 +0000 (UTC) (envelope-from SRS0=7ca34fec728a97891ad7365ef9e258cbb21b2d75=726=es.net=oberman@es.net) Received: from postal1.es.net (postal3.es.net [IPv6:2001:400:14:3::8]) by mx1.freebsd.org (Postfix) with ESMTP id B278B8FC18; Mon, 9 Jun 2008 01:10:47 +0000 (UTC) (envelope-from SRS0=7ca34fec728a97891ad7365ef9e258cbb21b2d75=726=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal3.es.net (Postal Node 3) with ESMTP (SSL) id PHT47546; Sun, 08 Jun 2008 18:10:46 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 0DDA74500F; Sun, 8 Jun 2008 18:10:45 -0700 (PDT) To: Doug Barton In-Reply-To: Your message of "Wed, 04 Jun 2008 10:01:47 PDT." <4846CA7B.5070308@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1212973845_87733P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 08 Jun 2008 18:10:45 -0700 From: "Kevin Oberman" Message-Id: <20080609011045.0DDA74500F@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; ; ; X-Sender: X-To_Name: Doug Barton X-To_Domain: freebsd.org X-To: Doug Barton X-To_Email: dougb@FreeBSD.org X-To_Alias: dougb Cc: Josh Paetzel , Jeremy Chadwick , nlaroche@vt.edu, freebsd-stable@freebsd.org Subject: Re: Lenovo Thinkpad t61p and FreeBSD? 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, 09 Jun 2008 01:10:48 -0000 --==_Exmh_1212973845_87733P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Wed, 04 Jun 2008 10:01:47 -0700 > From: Doug Barton > Sender: owner-freebsd-stable@freebsd.org > > Richard Arends wrote: > > On Wed, Jun 04, 2008 at 07:45:12AM -0500, Josh Paetzel wrote: > > > > Hi, > > > >> I'm interested in whatever cooling solutions people have... > > I didn't follow this thread earlier because I don't have this laptop, > but I wonder if anyone has offered the suggestion to blow out all the > vents and heatsinks with compressed air yet? Even in a fairly "healthy" > environment at home my laptop gets a non-trivial amount of dust buildup. > I blow it clean about once a month and get visible results each time. Amen, Doug. I post this advise fairly routinely. For my ThinkPad, I just remove the keyboard (4 screws) and blow into the exhaust ports. I know that I would be better off with compressed air, but my lungs are hand and available and, the small amount of contamination they input is dwarfed by the massive cloud of dust that blasts out of the air intake in the heat sink assembly. Low tech and only takes about 15 minutes. I do it annually or when the CPU temp hits 90 during a big build (such as buildworld or gnome). -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1212973845_87733P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFITIMVkn3rs5h7N1ERAn1wAJ9ze9fMDIbsdNjtYJyNzCkCI+8R3ACfXc0O NH7QmZzw1A5JkCp2nyDBmU4= =sWtY -----END PGP SIGNATURE----- --==_Exmh_1212973845_87733P-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 03:24:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6ABC106564A for ; Mon, 9 Jun 2008 03:24:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id CD4368FC15 for ; Mon, 9 Jun 2008 03:24:10 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id B617D1A4D82; Sun, 8 Jun 2008 20:24:10 -0700 (PDT) Date: Sun, 8 Jun 2008 20:24:10 -0700 From: Alfred Perlstein To: Mike Edenfield Message-ID: <20080609032410.GQ48790@elvis.mu.org> References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <200806050248.59229.max@love2party.net> <20080605083907.GD1028@server.vk2pj.dyndns.org> <902E9703E6E50776A17E9F92@utd65257.utdallas.edu> <20080605220244.GP1028@server.vk2pj.dyndns.org> <34E9F0D46D7B9F45EDA38F4C@utd65257.utdallas.edu> <48488D1A.9070105@kutulu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48488D1A.9070105@kutulu.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable@freebsd.org, Paul Schmehl Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 09 Jun 2008 03:24:11 -0000 Y'know, I've been sort of skimming this thread, and I think a lot of this time could be better spent by just looking at the PRs and giving the original poster tips and encouragement for providing the information needed by FreeBSD to solve his problems. Really... -Alfred * Mike Edenfield [080605 18:04] wrote: > Paul Schmehl wrote: > >I think that's an unfair characterization. He stated that he had > >noted numerous bugs in 6.3 (submitted PRs) that he perceived affected > >him personally and so he chose not to update to 6.3. He then asked if > >6.2 couldn't be extended farther. That seems like a reasonable > >question to ask. A simple, professional answer would have settled the > >matter quickly. > > Part of the problem is that a few of us (including myself) *have* looked > for the PRs he referenced and can't find them. There are only three > critical PR's opened on the hardware devices he mentioned that are filed > specifically against version 6.3: one each for bge, gmirror, and 3ware. > Of those, one of them appears to be sporadic, one of them appears to be > specific to a particular obscure BIOS, and one of them involved a > specific dual-card setup on a specific type of motherboard. And none of > those *specifically* say that they cannot be reproduced on 6.2 -- one of > them is actually filed against version 5 through 7. Since we also know > very little about the specific hardware setup of the OP, it's impossible > to determine if these are, in fact, the PRs he's looking at, or if he's > actually looking at other less-critical PRs that may need to be bumped > up to critical, or if they're misfiled, or who knows what. > > In short, the problem reports that the OP is looking at are not > immediately obvious to someone who doesn't already know what they are, > and he's not doing himself any favors by insisting that everyone else > "already knows" about these problems. If he's seen these bug reports, > presumably he knows what their PR #'s are, or at the very least the > description of the bugs, and it would be many many times faster for him > to just say so than continue to insist that other people read his mind. > > --Mike > > _______________________________________________ > 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" -- - Alfred Perlstein From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 03:32:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D80D1065678 for ; Mon, 9 Jun 2008 03:32:51 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id E77758FC15 for ; Mon, 9 Jun 2008 03:32:50 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id D38BA1A4D8C; Sun, 8 Jun 2008 20:32:50 -0700 (PDT) Date: Sun, 8 Jun 2008 20:32:50 -0700 From: Alfred Perlstein To: Jo Rhett Message-ID: <20080609033250.GR48790@elvis.mu.org> References: <48472DB6.5030909@samsco.org> <6010676B-91B0-4AF8-ACF8-039A59B29331@netconsonance.com> <200806050248.59229.max@love2party.net> <20080605083907.GD1028@server.vk2pj.dyndns.org> <902E9703E6E50776A17E9F92@utd65257.utdallas.edu> <20080605220244.GP1028@server.vk2pj.dyndns.org> <34E9F0D46D7B9F45EDA38F4C@utd65257.utdallas.edu> <48488D1A.9070105@kutulu.org> <52E265BB-BBB1-439D-B375-D6C6AA04697C@netconsonance.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52E265BB-BBB1-439D-B375-D6C6AA04697C@netconsonance.com> User-Agent: Mutt/1.4.2.3i Cc: Mike Edenfield , freebsd-stable@freebsd.org, Paul Schmehl Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 09 Jun 2008 03:32:51 -0000 * Jo Rhett [080607 14:37] wrote: > > Mike, could you do me a favor and provide me with a set of words that > will make what I am trying to say on this topic clear? I keep saying > the same thing over and over again and nobody is hearing me, so could > you perhaps help me translate this? > > These are the raw issues without any friendly wording. > > 1. Bugs in 6.3 that are patched aren't available in any other -RELEASE. Jo, sorry to jump in here, but what are these bugs that you are concerned about? Can you give specific PR#s? Can you confirm that these bugs are still issues? > 2. Bugs in 6.3 outstanding that don't affect 6.2 This is a bit of a stretch honestly, there may be bugs in 6.3 that are also in 6.2, however they have only been reported in 6.3 because of time. > 3. Overall amount of bugs. See previous. > 4. Difference in code base between 6.3 and 6-STABLE is > than 6.2 and > 6.3 Well, that's good! (or should be, see below.) > These combine to produce a release which will never be "stable" for > production needs. Let's not go there. Let's work with what we have. In theory people should only be pushing bugfixes and drivers in the -stable series, however sometimes changes are made for performance too when the risk is "low". Larger changesets in the later versions of -stable for a particular major release is to be expected as the number of users migrating from the previous major release (5.x) start to come over. > Obviously the FreeBSD team(s) involved have to make choices. Perhaps > there's nothing we can do to improve it other than work on the > specific bugs. But does it hurt to ask why 6.2 was dropped so fast? > What the real cost of supporting 6.2 until 6.4 ships is? I can understand your upset, I have been there, I found that later versions of 5.x had regressions for me that forced me to decide to either downgrade to 5.3 or go to 6.x. You may need to stick to 6.2 and keep a local set of patches (this is much easier now with svn and svk). OR you can try 7.x. The fact of the matter is that as an individual you have many options: 1) work to figure out why 6.3 (or -stable) isn't working. 2) stick with 6.2 with your own mods. 3) try 7-stable. Trust me, I know you've been pretty frustrated by this thread, but from my experience you're not going to get what you want, but you may get what you need (if you take my advice). best of luck, -Alfred From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 03:48:45 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 80F3B106566C for ; Mon, 9 Jun 2008 03:48:45 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id E16658FC20 for ; Mon, 9 Jun 2008 03:48:43 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with ESMTP id NAA02451; Mon, 9 Jun 2008 13:48:22 +1000 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 9 Jun 2008 13:48:21 +1000 (EST) From: Ian Smith To: "Alexandre \"Sunny\" Kovalenko" In-Reply-To: <1212951813.1139.0.camel@RabbitsDen> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Cc: Josh Paetzel , stable@freebsd.org Subject: Re: Lenovo Thinkpad t61p and FreeBSD? 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, 09 Jun 2008 03:48:45 -0000 On Sun, 8 Jun 2008, Alexandre "Sunny" Kovalenko wrote: > On Wed, 2008-06-04 at 07:45 -0500, Josh Paetzel wrote: > > On Wednesday 04 June 2008 07:25:13 am Jeremy Chadwick wrote: > > > On Tue, Jun 03, 2008 at 11:13:27AM -0400, nlaroche@vt.edu wrote: > > > > Quoting nlaroche@vt.edu: > > > > > Quoting Jeremy Chadwick : > > > > > > Based on my experiences with my workplace-provided T60p, it's safe to > > > > > > say I'll never recommend a Lenovo product. The temperatures of these > > > > > > laptops are absolutely insane, supported by an incredibly loud fan. > > > > > > I'm not interested in a product that can have a GPU reaching > > > > > > temperatures of almost 70C **while idling**. > > > > > > > > > > I purchased a T60p about two months ago and I haven't had any of these > > > > > happen (yet?) running Ubuntu 7.10. The machine only gets slightly warm > > > > > to the touch after a few hours idling. > > > > > > > > > > Does your fan run all the time that loud? I'm wondering if there were > > > > > changes made at the factory to fix this type of problem if it was wide > > > > > spread. > > > > > > > > > > Regards, > > > > > Nick LaRoche > > > > > > > > That was a T61p not a T60p > > > > > > It really doesn't matter in this case; T60p, T60p (widescreen), T61p, > > > X60p, etc... They all behave the same way when it comes to > > > temperatures: incredibly high, sometimes to the point of the system > > > shutting off (for some). > > > > My T60p is really unusable for anything cpu intensive under FreeBSD. Even > > with the ibm acpi addons loaded and the fan set to it's highest setting it > > only turns at 3700rpm, which isn't enough to keep it from shutting down due > > to heat. (eg over 100C) > > > > I'm interested in whatever cooling solutions people have... > > > You can read through this thread: > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=141019+0 > +/usr/local/www/db/text/2008/freebsd-acpi/20080217.freebsd-acpi > > which mentions at least two ways to approach it -- the right one is from > the referenced message forward. Hi Alex, glad to see you're still keeping track of these issues .. In there ume@ says that his patch was committed .. do you know if it was MFC'd back to 7.x? 6.x? Perhaps the docs haven't caught up yet? There are only going to be a lot more of these around .. cheers, Ian From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 05:13:47 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A89E51065678; Mon, 9 Jun 2008 05:13:47 +0000 (UTC) (envelope-from SRS0=7ca34fec728a97891ad7365ef9e258cbb21b2d75=726=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id EE7B88FC1D; Mon, 9 Jun 2008 05:13:46 +0000 (UTC) (envelope-from SRS0=7ca34fec728a97891ad7365ef9e258cbb21b2d75=726=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id PLW14145; Sun, 08 Jun 2008 22:13:45 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id CFD4D45010; Sun, 8 Jun 2008 22:13:43 -0700 (PDT) To: Jeremy Chadwick In-Reply-To: Your message of "Sat, 07 Jun 2008 09:48:12 PDT." <20080607164812.GA11072@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1212988423_87733P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Sun, 08 Jun 2008 22:13:43 -0700 From: "Kevin Oberman" Message-Id: <20080609051343.CFD4D45010@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; ; X-Sender: X-To_Name: Jeremy Chadwick X-To_Domain: freebsd.org X-To: Jeremy Chadwick X-To_Email: koitsu@FreeBSD.org X-To_Alias: koitsu Cc: Evren Yurtesen , freebsd-stable@freebsd.org, John Baldwin , Andrew Snow Subject: Re: cpufreq broken on core2duo 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, 09 Jun 2008 05:13:47 -0000 --==_Exmh_1212988423_87733P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Sat, 7 Jun 2008 09:48:12 -0700 > From: Jeremy Chadwick > Sender: owner-freebsd-stable@freebsd.org > > On Sat, Jun 07, 2008 at 05:51:38PM +0300, Evren Yurtesen wrote: > > By the way, there is another thing I am wondering about. If I enable HTT > > and Intel Enhanced SpeedStep in bios on a 3.00GHZ p4 CPU I see: > > > > cpu0: on acpi0 > > acpi_perf0: on cpu0 > > p4tcc0: on cpu0 > > cpu1: on acpi0 > > est1: on cpu1 > > est: CPU supports Enhanced Speedstep, but is not recognized. > > est: cpu_vendor GenuineIntel, msr f2700000f27 > > device_attach: est1 attach returned 6 > > p4tcc1: on cpu1 > > > > dev.cpu.0.freq_levels: 1500/27000 1312/23625 1200/13000 1050/11375 900/9750 > > 750/8125 600/6500 450/4875 300/3250 150/1625 > > dev.acpi_perf.0.freq_settings: 1500/27000 1200/13000 > > dev.cpufreq.0.%driver: cpufreq > > dev.cpufreq.0.%parent: cpu0 > > dev.cpufreq.1.%driver: cpufreq > > dev.cpufreq.1.%parent: cpu1 > > dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > 2500/-1 1250/-1 > > dev.p4tcc.1.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > 2500/-1 1250/-1 > > > > and it does not allow me to set the freq. of the cpu. > > How are you setting the frequency? Are you using powerd? You do not > have to enable SpeedStep in your BIOS to achieve throttling CPU clock > speed. In fact, I would highly recommend leaving EIST/SpeedStep in the > BIOS *disabled*, and let powerd adjust the clock frequency via ACPI. I must strongly recommend against this. EST is MUCH more efficient on its control of power use than simple throttling. So much so that on my systems that support EST, I remove cpufreq from the kernel. (In all cases, throttling means either simple throttling or throttling by using TCC.) I did quite a bit of testing on power management a year or so ago and found that throttling was of value only for controlling CPU temperature. For real power management, EST works far better as it adjust frequency (actual clock rate) and CPU voltage while throttling just stops and starts the clock without changing its actual frequency. (This came as a surprise to me about 5 years ago when I first discovered it.) At idle, throttling does exactly nothing. EST reduces voltage on the CPU and saves power even when idle. At full CPU load, throttling reduces performance and power consumption equally. EST beats it by a slim margin. The big win is at moderate load. Throttling can result is very poor results for aps like video and music which will place a continuous load on the system, but only 20-60% (in the case of my test system). It tended to make the system seem sluggish. EST does a much better job in this case as it lowers CP voltage and clock rate to maximize performance while minimizing power. If your only concern is keeping the system cool, throttling will do the job, but if you want efficient power utilization, use EST if possible. -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1212988423_87733P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFITLwHkn3rs5h7N1ERApXwAJ4se7iwJndrmqZIen+JOb1ckcTcSgCglZck war9A/b4cFQcgxmSvhvw2Sg= =65cM -----END PGP SIGNATURE----- --==_Exmh_1212988423_87733P-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 05:30:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2E841065670; Mon, 9 Jun 2008 05:30:35 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE1D8FC0C; Mon, 9 Jun 2008 05:30:35 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 624F91CC031; Sun, 8 Jun 2008 22:30:35 -0700 (PDT) Date: Sun, 8 Jun 2008 22:30:35 -0700 From: Jeremy Chadwick To: Kevin Oberman Message-ID: <20080609053035.GA6859@eos.sc1.parodius.com> References: <20080607164812.GA11072@eos.sc1.parodius.com> <20080609051343.CFD4D45010@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080609051343.CFD4D45010@ptavv.es.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Evren Yurtesen , freebsd-stable@freebsd.org, John Baldwin , Andrew Snow Subject: Re: cpufreq broken on core2duo 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, 09 Jun 2008 05:30:35 -0000 On Sun, Jun 08, 2008 at 10:13:43PM -0700, Kevin Oberman wrote: > > Date: Sat, 7 Jun 2008 09:48:12 -0700 > > From: Jeremy Chadwick > > Sender: owner-freebsd-stable@freebsd.org > > > > On Sat, Jun 07, 2008 at 05:51:38PM +0300, Evren Yurtesen wrote: > > > By the way, there is another thing I am wondering about. If I enable HTT > > > and Intel Enhanced SpeedStep in bios on a 3.00GHZ p4 CPU I see: > > > > > > cpu0: on acpi0 > > > acpi_perf0: on cpu0 > > > p4tcc0: on cpu0 > > > cpu1: on acpi0 > > > est1: on cpu1 > > > est: CPU supports Enhanced Speedstep, but is not recognized. > > > est: cpu_vendor GenuineIntel, msr f2700000f27 > > > device_attach: est1 attach returned 6 > > > p4tcc1: on cpu1 > > > > > > dev.cpu.0.freq_levels: 1500/27000 1312/23625 1200/13000 1050/11375 900/9750 > > > 750/8125 600/6500 450/4875 300/3250 150/1625 > > > dev.acpi_perf.0.freq_settings: 1500/27000 1200/13000 > > > dev.cpufreq.0.%driver: cpufreq > > > dev.cpufreq.0.%parent: cpu0 > > > dev.cpufreq.1.%driver: cpufreq > > > dev.cpufreq.1.%parent: cpu1 > > > dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > > 2500/-1 1250/-1 > > > dev.p4tcc.1.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > > 2500/-1 1250/-1 > > > > > > and it does not allow me to set the freq. of the cpu. > > > > How are you setting the frequency? Are you using powerd? You do not > > have to enable SpeedStep in your BIOS to achieve throttling CPU clock > > speed. In fact, I would highly recommend leaving EIST/SpeedStep in the > > BIOS *disabled*, and let powerd adjust the clock frequency via ACPI. > > I must strongly recommend against this. EST is MUCH more efficient on > its control of power use than simple throttling. So much so that on my > systems that support EST, I remove cpufreq from the kernel. (In all > cases, throttling means either simple throttling or throttling by using > TCC.) The reality of the situation is that users cannot use EIST reliably on FreeBSD. I cannot imagine removing cpufreq would solve the "runtime went backwards" issue. The EIST problem needs to be fixed. If the folks who work on it do not have present-day hardware (C2Ds, etc.), I will be more than happy to purchase them whatever they need. > I did quite a bit of testing on power management a year or so ago and > found that throttling was of value only for controlling CPU temperature. > For real power management, EST works far better as it adjust frequency > (actual clock rate) and CPU voltage while throttling just stops and > starts the clock without changing its actual frequency. (This came as a > surprise to me about 5 years ago when I first discovered it.) As far as I know, the ACPI frequency toggling does in fact adjust the CPU clock rate -- because the values in dev.cpu.0.freq_levels are defined by the ACPI configuration on the machine. I'd confirm this, but looking at the kernel code doesn't help -- I cannot find the definition of the CPUFREQ_LEVELS function or macro. > At idle, throttling does exactly nothing. EST reduces voltage on the > CPU and saves power even when idle. At full CPU load, throttling reduces > performance and power consumption equally. EST beats it by a slim > margin. I thought the power-saving modes of the CPU (C1E/C2E/C3E/C4E) could be used *without* enabling EIST. I don't think FreeBSD has kernel or userland support utilities to enable/disable CPU-level features. Something like RMClock for Windows would be quite useful. (If you have the opportunity to run it, do so; you'll see what I mean, re: all the features being toggleable individually). > The big win is at moderate load. Throttling can result is very poor > results for aps like video and music which will place a continuous load > on the system, but only 20-60% (in the case of my test system). It > tended to make the system seem sluggish. EST does a much better job in > this case as it lowers CP voltage and clock rate to maximize performance > while minimizing power. > > If your only concern is keeping the system cool, throttling will do the > job, but if you want efficient power utilization, use EST if possible. In the case est does not attach (e.g. no EIST support enabled in FreeBSD), the throttling method resorts to simply suspending the system, then yes I completely agree -- EIST is significantly better than that. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 07:46:31 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 58DD21065674 for ; Mon, 9 Jun 2008 07:46:31 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from dsl254-019-221.sea1.dsl.speakeasy.net (dsl254-019-221.sea1.dsl.speakeasy.net [216.254.19.221]) by mx1.freebsd.org (Postfix) with ESMTP id 2AEFC8FC15 for ; Mon, 9 Jun 2008 07:46:31 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 38955 invoked from network); 9 Jun 2008 07:19:49 -0000 Received: from localhost (HELO zircon.zircon.seattle.wa.us) (127.0.0.1) by localhost with ESMTP; 9 Jun 2008 07:19:49 -0000 Message-ID: <484CD995.3040002@zircon.seattle.wa.us> Date: Mon, 09 Jun 2008 00:19:49 -0700 From: Joe Kelsey User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: 6.3-RELEASE versus 5.2-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: Mon, 09 Jun 2008 07:46:31 -0000 I think I have finally decoded Jo Rhett's issue. It is very hard to decipher because the poster refuses to exactly identify their problem. The entire problem comes down to the definition of -RELEASE. Jo apparantly feels that they can ONLY run -RELEASE branded code at their workplace. That means that they cannot run any form of -STABLE. Therefore, they can only ever run 6.3-RELEASE and then only if no bugs were fixed after the official branding of 6.3-RELEASE. I cannot speak at all about the branding of 6.3-RELEASE. I run 7.0-STABLE here. What Jo seems to thik is that a certain sequence of events occurred during the 6.3-RELEASE branding. 6.3-RELEASE was marked in the tree. Sometime after this marking event occurred, bugs were ientified and subsequently fixed in the -STABLE branch. These bugs have been identified by Jo as SHOWSTOPPER bugs which will prevent him from ever using 6.3-RELEASE, since by their definition, they can only ever use the exact thing identified by the cvs tag of 6.3-RELEASE. Therefore, by Jo's definition, they can never run 6.3-anything at their shop and are forced to wait for 6.4-RELEASE, whenever that happens. Therefore, they must take on the onerous duty of examining all security fixes target for 6.3 and redo them for 6.2. Basically, they do not wish to do this and protest the EoL status given to 6.2 because they are physically prevented from using 6.3. They refuse to even try to identify whether or not 6.3-RELEASE actually has any bugs that affect them, they just assume that the presence of bugs fixed AFTER the tagging of 6.3-RELEASE in cvs certifies their inability to use the actual 6.3-RELEASE code, since they can apparantly only run binary releases direct from FreeBSD and cannot "roll their own" for some unknown reason. They are also, apparantly, prohibited from testing any code locally due to some unknowable reason. Can anyone verify that some number of bugs related to either a) gmirror, b) bge and/or c)twe were fixed after the release of 6.3? That is as far as I can tell the reason that Jo objets to EoL of 6.2, the fact that 6.3 is unusable due to these late-fixed bugs. /Joe From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 07:51:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02FF7106566B for ; Mon, 9 Jun 2008 07:51:00 +0000 (UTC) (envelope-from andrew@modulus.org) Received: from email.octopus.com.au (host-122-100-2-232.octopus.com.au [122.100.2.232]) by mx1.freebsd.org (Postfix) with ESMTP id AA8EB8FC1A for ; Mon, 9 Jun 2008 07:50:59 +0000 (UTC) (envelope-from andrew@modulus.org) Received: by email.octopus.com.au (Postfix, from userid 1002) id 075B217D82; Mon, 9 Jun 2008 17:50:58 +1000 (EST) X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on email.octopus.com.au X-Spam-Level: X-Spam-Status: No, score=-1.4 required=10.0 tests=ALL_TRUSTED autolearn=failed version=3.2.3 Received: from [10.1.50.60] (142.19.96.58.exetel.com.au [58.96.19.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: admin@email.octopus.com.au) by email.octopus.com.au (Postfix) with ESMTP id DBA9417D7F for ; Mon, 9 Jun 2008 17:50:53 +1000 (EST) Message-ID: <484CE0C6.2000308@modulus.org> Date: Mon, 09 Jun 2008 17:50:30 +1000 From: Andrew Snow User-Agent: Thunderbird 2.0.0.14 (X11/20080523) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <484CD995.3040002@zircon.seattle.wa.us> In-Reply-To: <484CD995.3040002@zircon.seattle.wa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: 6.3-RELEASE versus 5.2-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: Mon, 09 Jun 2008 07:51:00 -0000 Joe Kelsey wrote: > The entire problem comes down to the definition of -RELEASE. Jo > apparantly feels that they can ONLY run -RELEASE branded code at their > workplace. That means that they cannot run any form of -STABLE. Interesting, and unfortunate. Empirically, I always felt that the -STABLE branch shortly after each -RELEASE is the most stable. I suspect the reason is large numbers of people install or upgrade to a -RELEASE, discover and report a number of bugs which subsequently get fixed. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 08:58:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 666F0106566B for ; Mon, 9 Jun 2008 08:58:12 +0000 (UTC) (envelope-from john@ctipc01.mby.riverwillow.net.au) Received: from mail2.riverwillow.net.au (ns2.riverwillow.net.au [203.58.93.41]) by mx1.freebsd.org (Postfix) with ESMTP id D4F6E8FC18 for ; Mon, 9 Jun 2008 08:58:11 +0000 (UTC) (envelope-from john@ctipc01.mby.riverwillow.net.au) Received: from ctipc01.mby.riverwillow.net.au (ctipc01.mby.riverwillow.net.au [172.25.24.168]) by mail2.riverwillow.net.au (8.14.3/8.14.3) with ESMTP id m598h5eT088185 for ; Mon, 9 Jun 2008 18:43:05 +1000 (AEST) Received: from ctipc01.mby.riverwillow.net.au (localhost [127.0.0.1]) by ctipc01.mby.riverwillow.net.au (8.14.2/8.14.2) with ESMTP id m598h4TI002485 for ; Mon, 9 Jun 2008 18:43:04 +1000 (AEST) (envelope-from john@ctipc01.mby.riverwillow.net.au) Received: (from john@localhost) by ctipc01.mby.riverwillow.net.au (8.14.2/8.14.2/Submit) id m598h4wC002484 for freebsd-stable@freebsd.org; Mon, 9 Jun 2008 18:43:04 +1000 (AEST) (envelope-from john) Date: Mon, 9 Jun 2008 18:43:03 +1000 From: John Marshall To: FreeBSD Stable Message-ID: <20080609084303.GA1229@ctipc01.mby.riverwillow.net.au> Mail-Followup-To: FreeBSD Stable References: <484736E0.6090004@samsco.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy6.3 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, 09 Jun 2008 08:58:12 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Picking one of the many posts from the OP in this thread... On Wed, 04 Jun 2008, 22:33 -0700, Jo Rhett wrote: > I am suggesting that given that the current bug list for 6.3-RELEASE =20 > is both (a) too large and (b) breaks things that work fine in 6.2 ... =20 > that I think pushing 6.2 (the real stable release) into EoL is a bit =20 > rushed. I sympathize with the development costs of maintaining old =20 > versions. Again, I will help in any way I can. It seems to me that the underlying grievance may be lack of faith in the latest RELEASEs; promtping the suggestion that $FAVOURITE_RELEASE support be extended. I believe that the best way to acquire confidence in the FreeBSD RELEASEs is to participate in the release cycles. Those of us who are not developers can make a significant contribution by taking the time to build the BETA and RC builds on our own systems with our own peculiar mix of CPU's, motherboards and peripherals. If we find problems we can feed them back to the team and improve the quality of the release; and then we'll be confident about deploying RELEASE on our systems rather than regarding it with suspicion. > On my return next week I would happily build and provide 6.3-RELEASE =20 > systems for any developer who needs a test environment for reported =20 > bugs that affect hardware I have in my possession. Free boxes, free =20 > bandwidth, power, etc. No problem. Free my time in whatever way I =20 > can help. This is the system which should have been used for building the 6.3 BETAs and RCs. Offering it for others to use for debugging, while a generous gesture and no doubt greatly appreciated, is a bit like shutting the gate after the horse has bolted. This will not achieve a better 6.3-RELEASE. The release has already happened. > But until such time as the current bug list for 6.3 hardware reduces =20 > to somewhere less than 100% likelyhood of experiencing failures after =20 > an upgrade, there's just no way I can take our production environment =20 > forward. Going "bravely forward" to guaranteed failure isn't a great =20 > way to enjoy your job :-( Which means I'll be doing our security =20 > patches by hand. Because it may be time intensive, but it's less =20 > likely to cause a production failure. 6.3-RELEASE will never improve. Since the OP emphasised deploying only RELEASEs, I suggest that his effort should go into making sure that 7.1 meets his requirements BEFORE it is released. For the record, I am running 6.3-RELEASE on hosted systems interstate and internationally and have had no problems at all: locally I am running a mixture of 6.3-RELEASE and 7.0-RELEASE with no problem. I hope this discussion provides a catalyst for more of us to become more involved in pre-RELEASE testing to ensure an even higher standard of RELEASEs from the FreeBSD project. --=20 John Marshall --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhM7RUACgkQw/tAaKKahKLzmQCgnbxxBUA/AsdFn28tygUIOYzy UXkAoMIGhGrmq3IPJZEVKZ3HRdyO7vbD =mT6l -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 09:03:35 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8BA410656AF for ; Mon, 9 Jun 2008 09:03:35 +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 89F2E8FC15 for ; Mon, 9 Jun 2008 09:03:35 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K5dHp-0003ob-Pu for freebsd-stable@freebsd.org; Mon, 09 Jun 2008 09:03:33 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 Jun 2008 09:03:33 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 09 Jun 2008 09:03:33 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Mon, 09 Jun 2008 11:03:18 +0200 Lines: 27 Message-ID: References: <47713ee10806061443v3e44576am2facb75df031f47e@mail.gmail.com> <47713ee10806062148l4a4c4550hcd8c70a422343c2a@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9929F3E2319898608AD8DEEF" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: <47713ee10806062148l4a4c4550hcd8c70a422343c2a@mail.gmail.com> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: TMPFS: File System is Full 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, 09 Jun 2008 09:03:36 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9929F3E2319898608AD8DEEF Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Lin Jui-Nan Eric wrote: > I think there should be a "lower bound" size limit. Does TMPFS use > kernel-space memory? Yes, tmpfs does use kmem and competes with ZFS. --------------enig9929F3E2319898608AD8DEEF 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.6 (GNU/Linux) iD8DBQFITPHdldnAQVacBcgRAtlLAKCk4x9zLncoxNfwKyOgA5+anBglQgCfQKgv w8+rzZGe8ENs0jxQ5cJJmMw= =unzJ -----END PGP SIGNATURE----- --------------enig9929F3E2319898608AD8DEEF-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 09:44:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AFFE106564A for ; Mon, 9 Jun 2008 09:44:55 +0000 (UTC) (envelope-from ruben@verweg.com) Received: from erg.verweg.com (erg.verweg.com [217.77.141.129]) by mx1.freebsd.org (Postfix) with ESMTP id 12E158FC12 for ; Mon, 9 Jun 2008 09:44:54 +0000 (UTC) (envelope-from ruben@verweg.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verweg.com; s=verweg; t=1213004078; bh=/SLjpUOhSU9WjwyGAPBVft090NcJjPyaimEL1gNGYjk=; h=Message-Id:From:To:In-Reply-To:Content-Type: Content-Transfer-Encoding:Mime-Version:Subject:Date:References: X-Mailer; b=Zmfxyot8WhvWUBUo0h94S185MMmsncoi2sTsAvCbIHKKYOKmAX3NNN pTMY/bVJeBOm61oLIFIfcsiBOBUJdTTHjN2++yQiBnKjFQFsXQd5lVQdM4BUMORJXwR TwrFD6MVU6hqoHJ/tuyDAxjT+1NTPOS3DJgSvcfQv/QnLCnFws= Received: from [IPv6:::1] (chimp.ripe.net [193.0.1.199]) (authenticated bits=0) by erg.verweg.com (8.14.2/8.14.2) with ESMTP id m599YWWv013961 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Mon, 9 Jun 2008 09:34:38 GMT (envelope-from ruben@verweg.com) X-Authentication-Warning: erg.verweg.com: Host chimp.ripe.net [193.0.1.199] claimed to be [IPv6:::1] Message-Id: <07D0EBB8-77B3-4593-85C5-A38E94DD0DDD@verweg.com> From: Ruben van Staveren To: freebsd-stable@freebsd.org In-Reply-To: <200806072254.43405.max@love2party.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 9 Jun 2008 11:34:26 +0200 References: <9B7FE91B-9C2E-4732-866C-930AC6022A40@netconsonance.com> <200806072254.43405.max@love2party.net> X-Mailer: Apple Mail (2.924) X-Virus-Scanned: ClamAV 0.93/6805/Wed Apr 16 19:57:54 2008 on erg.verweg.com X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-3.0 (erg.verweg.com [217.77.141.129]); Mon, 09 Jun 2008 09:34:39 +0000 (UTC) Subject: Re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 09 Jun 2008 09:44:55 -0000 On 7 Jun 2008, at 22:54, Max Laier wrote: > Here is a cluebat for you: Here is another one: Currently 176 messages, posted by 51 unique participants (25 % by Jo himself) Given the fact that at least these 51 persons are actually reading all the mails, and taking some 5 minutes for it you'll see that this thread already consumed a whole man month worth of time. The amount of passive readers might stretch up to a good portion of the subscriber base. I probably do not have to mention this time was better spent on other things. So far I have seen nothing else than the community at large addressing FUD of one poster, which was a genuine remark when it started, but became irrational as there was no room for compromise. I started with RELENG_7 when it was 4 days of age, and impressed by the stability from the start. Yet still we going to get our production servers up to 6.3 and go for 7.1 instead as we make use (by design) of MyISAM tables in MySQL, though I do believe I saw a fix in cvs for the issue mentioned here: http://jeffr-tech.livejournal.com/20425.html Overall, the days of RELENG_4 and RELENG_5 are over and the 15 years or so of cvs history contributes to the quality of development inside the FreeBSD project, which I was using since 2.2.4-stable. Thanks! - Ruben From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 12:32:52 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F31A41065685 for ; Mon, 9 Jun 2008 12:32:52 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 9F0258FC23 for ; Mon, 9 Jun 2008 12:32:52 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id 78EEE1B10EF3; Mon, 9 Jun 2008 14:32:51 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on malcho.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 412991B10EF2; Mon, 9 Jun 2008 14:32:46 +0200 (CEST) Message-ID: <484D22ED.5060500@moneybookers.com> Date: Mon, 09 Jun 2008 15:32:45 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: Daniel Ponticello References: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> <484AE6E1.2050504@skytek.it> In-Reply-To: <484AE6E1.2050504@skytek.it> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on blah.cmotd.com X-Virus-Status: Clean Cc: Andy Kosela , freebsd-stable@FreeBSD.org Subject: Re: Current status of support for high end SAN hardware 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, 09 Jun 2008 12:32:53 -0000 Daniel Ponticello wrote: > On FreeBSD7, i'm succesfully using Qlogic 4gb fibre channel HBAs (ISP > driver) > attached to Fibre Brocade Switch and IBM DS4700 (14 disks array) using > 4 way multipath > with gmultipath. So far the support in gmultipath is active/passive only? I think in RH5 you can have active/active. Am I right? > > Regards, > > Daniel > > Andy Kosela ha scritto: >> Hi all, >> What is the current status of support for high end SAN hardware in >> FreeBSD? >> I'm especially interested in support for HP EVA/XP disk arrays, Qlogic >> HBAs, multipathing. >> How FreeBSD compares in this environment to RHEL 5? >> >> > -- Best Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 12:37:27 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64AC41065678; Mon, 9 Jun 2008 12:37:27 +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 374078FC28; Mon, 9 Jun 2008 12:37:26 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CbIxC093496; Mon, 9 Jun 2008 08:37:19 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CbIx8090900; Mon, 9 Jun 2008 08:37:18 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id C268C1B5078; Mon, 9 Jun 2008 08:37:18 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080609123718.C268C1B5078@freebsd-stable.sentex.ca> Date: Mon, 9 Jun 2008 08:37:18 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner2 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_7 tinderbox] failure on powerpc/powerpc 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: Mon, 09 Jun 2008 12:37:27 -0000 TB --- 2008-06-09 11:19:40 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-06-09 11:19:40 - starting RELENG_7 tinderbox run for powerpc/powerpc TB --- 2008-06-09 11:19:40 - cleaning the object tree TB --- 2008-06-09 11:19:56 - cvsupping the source tree TB --- 2008-06-09 11:19:56 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/powerpc/powerpc/supfile TB --- 2008-06-09 11:20:04 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-09 11:20:04 - cd /src TB --- 2008-06-09 11:20:04 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 9 11:20:05 UTC 2008 >>> 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 >>> World build completed on Mon Jun 9 12:27:15 UTC 2008 TB --- 2008-06-09 12:27:15 - generating LINT kernel config TB --- 2008-06-09 12:27:15 - cd /src/sys/powerpc/conf TB --- 2008-06-09 12:27:15 - /usr/bin/make -B LINT TB --- 2008-06-09 12:27:15 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-06-09 12:27:15 - cd /src TB --- 2008-06-09 12:27:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 9 12:27:16 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/nfsserver/nfs_srvsubs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/nfsserver/nfs_syscalls.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/nlm/nlm_prot_clnt.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -ffreestanding -Werror /src/sys/nlm/nlm_prot_impl.c /src/sys/nlm/nlm_prot_impl.c: In function 'nlm_check_idle': /src/sys/nlm/nlm_prot_impl.c:697: error: 'nlm_global_lock' undeclared (first use in this function) /src/sys/nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-09 12:37:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-09 12:37:18 - ERROR: failed to build lint kernel TB --- 2008-06-09 12:37:18 - tinderbox aborted TB --- 3843.69 user 367.57 system 4658.09 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-powerpc-powerpc.full From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 12:41:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 699C91065672 for ; Mon, 9 Jun 2008 12:41:25 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.183]) by mx1.freebsd.org (Postfix) with ESMTP id 3845B8FC28 for ; Mon, 9 Jun 2008 12:41:25 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so1629782wah.3 for ; Mon, 09 Jun 2008 05:41:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=ESTyVRL4bnX8SQXMI3Pt2O1s/aBecrTc5/XqWdmILlc=; b=k1p2/l13Hie6MMn/HL3a4az3Hbgr55zg55NEQ8oioFNsIDssQwA0X6N2CLxia20SBq oaggeBBrNj8qOmzKulS8w67Hh6byhvoqUPDYHwWm2OIRZxxOmtmgTRGfecPXH7NpGn72 q9CZzuXrniq8XMO+YfEbJtPEYi86mLwo+4Ckc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=qdD3sfyuxub/CY11hjAUhMBa4zl/b+77roYibgiLtsW6HJZqm6iU9843AyXpOTfMIt 53pcyjGPdyKSzbN1Fl9S9Oa0ODWPiWaZNB/k/GcKY0MVJMpNsHLf0oObDfWDITVRqocE pEaUvlO005ggVlbyg/P11/Gjh1av4JA05ShNw= Received: by 10.114.197.10 with SMTP id u10mr3189156waf.47.1213015284561; Mon, 09 Jun 2008 05:41:24 -0700 (PDT) Received: by 10.114.112.6 with HTTP; Mon, 9 Jun 2008 05:41:24 -0700 (PDT) Message-ID: <3cc535c80806090541g15c03c24mf1c47a9b92ff166a@mail.gmail.com> Date: Mon, 9 Jun 2008 14:41:24 +0200 From: "Andy Kosela" To: freebsd-stable@freebsd.org In-Reply-To: <20080609103610.GA36227@riffraff.plig.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> <484C4E6D.7060306@datapipe.com> <20080609103610.GA36227@riffraff.plig.net> Cc: msaad@datapipe.com, rv@openusenet.org Subject: Re: Current status of support for high end SAN hardware 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, 09 Jun 2008 12:41:25 -0000 On Mon, Jun 9, 2008 at 12:36 PM, Russell Vincent wrote: > > The FreeBSD support for multipath/SAN is fairly poor. It's fiddly > to get to work and boot times are a little variable (into the > minutes) as it tries to discover the devices. Once it is configured > and booted, it just works as long as things don't go wrong. SAN > outages cause the machine to hang up until the issue is resolved > (in which case it just seems to continue) or it doesn't recover at > all and requires a reboot. Note that I don't spend a significant > amount of time on this, so it may be that I could do things a little > better. I have also not tested the failover stuff very well (I > only upgraded this machine to 7-STABLE fairly recently). Disk > access seems to be restricted to a single path at a time. Problem > solving is very tricky as there is very little information to trace > which path/disk refers to which fabric/storage device/LUN. > Russell, Thank you for your insights. It's good to see you have no problems with isp(4) and Qlogic HBAs. Though I'm concerned about multipathing. We run 6.x-RELEASE releases so it seems we have to upgrade to 7.0-RELEASE to achieve that goal. gmultipath(8) code is fairly new so I suppose it's not that mature yet as in Linux. Unfortunately it is only an active/passive approach with no load balancing (the active path is active until a BIO request is failed with EIO or ENXIO) Good support for high end SAN environment is essential in todays data centers, as most servers are connected to storage using FC based storage area network. I hope things will improve as 7.x-STABLE will be polished over time. Mark, I completely agree with you that ZFS is much better than Ext3+LVM2. Ext3 is still lacking internal snapshoting capability, so it's even inferior to UFS2. As a matter of fact I'm watching Oracle's btrfs development as it seems it will change many things on Linux filesystems scene. Though I still fear ZFS on FreeBSD is not as yet mature to the point of using it in a mission critical 24x7 production environments. But it's definetly something to watch out for. -- Andy Kosela ora et labora From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 12:51:43 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEF291065676; Mon, 9 Jun 2008 12:51:43 +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 B25B08FC14; Mon, 9 Jun 2008 12:51:43 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CpcV0099408; Mon, 9 Jun 2008 08:51:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CpcsB023670; Mon, 9 Jun 2008 08:51:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id 95E8E241A2; Mon, 9 Jun 2008 08:51:52 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080609125152.95E8E241A2@freebsd-legacy.sentex.ca> Date: Mon, 9 Jun 2008 08:51:52 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner3 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_6 tinderbox] failure on i386/i386 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: Mon, 09 Jun 2008 12:51:44 -0000 TB --- 2008-06-09 11:40:12 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-09 11:40:12 - starting RELENG_6 tinderbox run for i386/i386 TB --- 2008-06-09 11:40:12 - cleaning the object tree TB --- 2008-06-09 11:40:43 - cvsupping the source tree TB --- 2008-06-09 11:40:43 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/i386/i386/supfile TB --- 2008-06-09 11:40:52 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-09 11:40:52 - cd /src TB --- 2008-06-09 11:40:52 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything TB --- 2008-06-09 12:34:00 - generating LINT kernel config TB --- 2008-06-09 12:34:00 - cd /src/sys/i386/conf TB --- 2008-06-09 12:34:00 - /usr/bin/make -B LINT TB --- 2008-06-09 12:34:01 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-06-09 12:34:01 - cd /src TB --- 2008-06-09 12:34:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 9 12:34:01 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug nfsclient.ko ===> nfslockd (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/obj/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_clnt.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -I/obj/src/sys/LINT -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c: In function `nlm_check_idle': /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: `nlm_global_lock' undeclared (first use in this function) /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /src/sys/modules/nfslockd. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-09 12:51:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-09 12:51:52 - ERROR: failed to build lint kernel TB --- 2008-06-09 12:51:52 - tinderbox aborted TB --- 3464.66 user 380.66 system 4299.67 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-i386-i386.full From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 12:55:50 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8F4E010656AC; Mon, 9 Jun 2008 12:55:50 +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 62FE38FC18; Mon, 9 Jun 2008 12:55:50 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp1.sentex.ca (smtp1c.sentex.ca [64.7.153.10]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CtkoW000953; Mon, 9 Jun 2008 08:55:46 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-legacy.sentex.ca (freebsd-legacy.sentex.ca [64.7.128.104]) by smtp1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59CtjWv029026; Mon, 9 Jun 2008 08:55:45 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-legacy.sentex.ca (Postfix, from userid 666) id 3EFBC241A2; Mon, 9 Jun 2008 08:56:00 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080609125600.3EFBC241A2@freebsd-legacy.sentex.ca> Date: Mon, 9 Jun 2008 08:56:00 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner1 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_6 tinderbox] failure on amd64/amd64 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: Mon, 09 Jun 2008 12:55:50 -0000 TB --- 2008-06-09 11:22:52 - tinderbox 2.3 running on freebsd-legacy.sentex.ca TB --- 2008-06-09 11:22:52 - starting RELENG_6 tinderbox run for amd64/amd64 TB --- 2008-06-09 11:22:52 - cleaning the object tree TB --- 2008-06-09 11:23:29 - cvsupping the source tree TB --- 2008-06-09 11:23:30 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_6/amd64/amd64/supfile TB --- 2008-06-09 11:23:36 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-09 11:23:36 - cd /src TB --- 2008-06-09 11:23:36 - /usr/bin/make -B buildworld >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries TB --- 2008-06-09 12:40:20 - generating LINT kernel config TB --- 2008-06-09 12:40:20 - cd /src/sys/amd64/conf TB --- 2008-06-09 12:40:20 - /usr/bin/make -B LINT TB --- 2008-06-09 12:40:20 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-06-09 12:40:20 - cd /src TB --- 2008-06-09 12:40:20 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 9 12:40:20 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] objcopy --strip-debug nfsclient.ko ===> nfslockd (all) cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_clnt.c cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I- -DHAVE_KERNEL_OPTION_HEADERS -include /obj/amd64/src/sys/LINT/opt_global.h -I. -I@ -I@/contrib/altq -I@/../include -finline-limit=8000 -fno-common -fno-omit-frame-pointer -I/obj/amd64/src/sys/LINT -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c: In function `nlm_check_idle': /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: `nlm_global_lock' undeclared (first use in this function) /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/modules/nfslockd/../../nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /src/sys/modules/nfslockd. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-09 12:56:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-09 12:56:00 - ERROR: failed to build lint kernel TB --- 2008-06-09 12:56:00 - tinderbox aborted TB --- 4486.69 user 532.27 system 5587.97 real http://tinderbox.des.no/tinderbox-releng_6-RELENG_6-amd64-amd64.full From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 13:35:14 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D3451065679; Mon, 9 Jun 2008 13:35:14 +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 2CD668FC1C; Mon, 9 Jun 2008 13:35:14 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from smtp2.sentex.ca (smtp2c.sentex.ca [64.7.153.30]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m59DZ9tr017411; Mon, 9 Jun 2008 09:35:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: from freebsd-stable.sentex.ca (freebsd-stable.sentex.ca [64.7.128.103]) by smtp2.sentex.ca (8.14.2/8.14.2) with ESMTP id m59DZ9Ka051233; Mon, 9 Jun 2008 09:35:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: by freebsd-stable.sentex.ca (Postfix, from userid 666) id 85EC91B5078; Mon, 9 Jun 2008 09:35:09 -0400 (EDT) Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Message-Id: <20080609133509.85EC91B5078@freebsd-stable.sentex.ca> Date: Mon, 9 Jun 2008 09:35:09 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93/7040/Mon May 5 21:52:15 2008 clamav-milter version 0.93 on clamscanner4 X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: [releng_7 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: Mon, 09 Jun 2008 13:35:14 -0000 TB --- 2008-06-09 12:25:44 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-06-09 12:25:44 - starting RELENG_7 tinderbox run for sparc64/sparc64 TB --- 2008-06-09 12:25:44 - cleaning the object tree TB --- 2008-06-09 12:26:02 - cvsupping the source tree TB --- 2008-06-09 12:26:02 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/sparc64/sparc64/supfile TB --- 2008-06-09 12:26:09 - building world (CFLAGS=-O2 -pipe) TB --- 2008-06-09 12:26:09 - cd /src TB --- 2008-06-09 12:26:09 - /usr/bin/make -B buildworld >>> World build started on Mon Jun 9 12:26:10 UTC 2008 >>> 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 >>> World build completed on Mon Jun 9 13:25:00 UTC 2008 TB --- 2008-06-09 13:25:00 - generating LINT kernel config TB --- 2008-06-09 13:25:00 - cd /src/sys/sparc64/conf TB --- 2008-06-09 13:25:00 - /usr/bin/make -B LINT TB --- 2008-06-09 13:25:00 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-06-09 13:25:00 - cd /src TB --- 2008-06-09 13:25:00 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Jun 9 13:25:00 UTC 2008 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/nfsserver/nfs_srvsubs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/nfsserver/nfs_syscalls.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/nlm/nlm_prot_clnt.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -Werror /src/sys/nlm/nlm_prot_impl.c /src/sys/nlm/nlm_prot_impl.c: In function 'nlm_check_idle': /src/sys/nlm/nlm_prot_impl.c:697: error: 'nlm_global_lock' undeclared (first use in this function) /src/sys/nlm/nlm_prot_impl.c:697: error: (Each undeclared identifier is reported only once /src/sys/nlm/nlm_prot_impl.c:697: error: for each function it appears in.) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-06-09 13:35:09 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-06-09 13:35:09 - ERROR: failed to build lint kernel TB --- 2008-06-09 13:35:09 - tinderbox aborted TB --- 3645.91 user 357.34 system 4165.30 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-sparc64-sparc64.full From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 13:49:31 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA4EF1065680 for ; Mon, 9 Jun 2008 13:49:31 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from mail.skytek.it (mail.skytek.it [217.194.176.18]) by mx1.freebsd.org (Postfix) with ESMTP id 3B6B08FC27 for ; Mon, 9 Jun 2008 13:49:31 +0000 (UTC) (envelope-from daniel@skytek.it) Received: from [192.168.30.100] ([192.168.30.100]) by mail.skytek.it (Skytek Mail Server v.11.47-p9) with ASMTP id PTG64029; Mon, 09 Jun 2008 15:49:29 +0200 Message-ID: <484D34F4.4050902@skytek.it> Date: Mon, 09 Jun 2008 15:49:40 +0200 From: Daniel Ponticello User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Stefan Lambrev References: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> <484AE6E1.2050504@skytek.it> <484D22ED.5060500@moneybookers.com> In-Reply-To: <484D22ED.5060500@moneybookers.com> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit Cc: Andy Kosela , freebsd-stable@FreeBSD.org Subject: Re: Current status of support for high end SAN hardware 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, 09 Jun 2008 13:49:32 -0000 man gmultipath is your friend ;) MULTIPATH ARCHITECTURE This is an active/passive multiple path architecture with no device knowledge or presumptions other than size matching built in. Therefore the user must exercise some care in selecting providers that do indeed represent multiple paths to the same underlying disk device. The reason for this is that there are several criteria across multiple underlying transport types that can indicate identity, but in all respects such identity can rarely be considered definitive. Regards, Daniel Stefan Lambrev ha scritto: > > > Daniel Ponticello wrote: >> On FreeBSD7, i'm succesfully using Qlogic 4gb fibre channel HBAs (ISP >> driver) >> attached to Fibre Brocade Switch and IBM DS4700 (14 disks array) >> using 4 way multipath >> with gmultipath. > So far the support in gmultipath is active/passive only? I think in > RH5 you can have active/active. > Am I right? >> >> Regards, >> >> Daniel >> >> Andy Kosela ha scritto: >>> Hi all, >>> What is the current status of support for high end SAN hardware in >>> FreeBSD? >>> I'm especially interested in support for HP EVA/XP disk arrays, Qlogic >>> HBAs, multipathing. >>> How FreeBSD compares in this environment to RHEL 5? >>> >>> >> > -- WBR, Cordiali Saluti, Daniel Ponticello, VP of Engineering Network Coordination Centre of Skytek --- - For further information about our services: - Please visit our website at http://www.Skytek.it --- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 16:58:03 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0E271065674 for ; Mon, 9 Jun 2008 16:58:03 +0000 (UTC) (envelope-from prvs=pschmehl_lists=039a102a6@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 940288FC1F for ; Mon, 9 Jun 2008 16:58:03 +0000 (UTC) (envelope-from prvs=pschmehl_lists=039a102a6@tx.rr.com) X-IronPort-AV: E=Sophos;i="4.27,613,1204524000"; d="scan'208";a="1186004" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 09 Jun 2008 11:29:18 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id C7D5423DEA for ; Mon, 9 Jun 2008 11:29:18 -0500 (CDT) Date: Mon, 09 Jun 2008 11:29:18 -0500 From: Paul Schmehl To: stable@freebsd.org Message-ID: <89AE69A6C6BB0B0E02487A45@utd65257.utdallas.edu> In-Reply-To: References: <200805081730.m48HUNjh001532@symbion.zaytman.com> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Re: [nvidia | shared irq] umass disconnects [was: panic dd-ing from a USB "disk" ] X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 16:58:03 -0000 --On Friday, June 06, 2008 19:36:46 +0200 "Arno J. Klaassen" wrote: > > > I can easily produce a similar panic on a dual Opteron 185 with > 3G of RAM and running 7-stable-amd64 on a (cheap) nvidia-based MB. > It runs gmirror on atapci1 and I attach a geli-encrypted > disk via usb. Both share irq 23. > > Under heavy load ("periodic security" is enough ) it panics after > having disconnected umass0 ( kgdb trace below ) : > > Unread portion of the kernel message buffer: > umass0: at uhub1 port 1 (addr 2) disconnected > (da1:umass-sim0:0:0:0): lost device > (pass1:umass-sim0:0:0:0): lost device > (pass1:umass-sim0:0:0:0): removing device entry > I have problems with umass during reboot. It causes a kernel panic and a forced reboot. To work around the problem, I disconnect the usb cable to reboot. Once the system comes back up, I can map the drive with no problems. If someone can tell me how to capture the information, I'd be glad to do so. I have no idea how to do it, and, after I disconnect the cable and reboot again, dmesg.boot looks perfectly normal. I've looked for core files but haven't found any. savecore -C returns "No dump exists". This is my workstation, so I can fiddle with it as need be to capture useful information. I just need someone knowledgeable to walk me through it, because this type of work is definitely out of my league. # uname -a FreeBSD utd65257.utdallas.edu 7.0-STABLE FreeBSD 7.0-STABLE #7: Sun Jun 8 15:58:57 CDT 2008 root@utd65257.utdallas.edu:/usr/obj/usr/src/sys/GENERIC i386 I just rebuilt world and kernel again, hoping the latest patches would solve the problem, but it didn't. -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer. From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 17:44:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D35B81065679 for ; Mon, 9 Jun 2008 17:44:44 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr2.xs4all.nl (smtp-vbr2.xs4all.nl [194.109.24.22]) by mx1.freebsd.org (Postfix) with ESMTP id 857E18FC28 for ; Mon, 9 Jun 2008 17:44:44 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [82.95.250.254]) by smtp-vbr2.xs4all.nl (8.13.8/8.13.8) with ESMTP id m59HicKg047243; Mon, 9 Jun 2008 19:44:38 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.14.2/8.13.3) with ESMTP id m59HicCO031160; Mon, 9 Jun 2008 19:44:38 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.14.2/8.14.2/Submit) id m59HibYM031159; Mon, 9 Jun 2008 19:44:37 +0200 (CEST) (envelope-from wb) Date: Mon, 9 Jun 2008 19:44:37 +0200 From: Wilko Bulte To: Andy Kosela Message-ID: <20080609174437.GB31050@freebie.xs4all.nl> References: <3cc535c80806071158h44ec9be1pbe72ca6711016bde@mail.gmail.com> <484C4E6D.7060306@datapipe.com> <20080609103610.GA36227@riffraff.plig.net> <3cc535c80806090541g15c03c24mf1c47a9b92ff166a@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3cc535c80806090541g15c03c24mf1c47a9b92ff166a@mail.gmail.com> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: msaad@datapipe.com, rv@openusenet.org, freebsd-stable@freebsd.org Subject: Re: Current status of support for high end SAN hardware 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, 09 Jun 2008 17:44:44 -0000 Quoting Andy Kosela, who wrote on Mon, Jun 09, 2008 at 02:41:24PM +0200 .. > On Mon, Jun 9, 2008 at 12:36 PM, Russell Vincent wrote: > > > > The FreeBSD support for multipath/SAN is fairly poor. It's fiddly > > to get to work and boot times are a little variable (into the > > minutes) as it tries to discover the devices. Once it is configured > > and booted, it just works as long as things don't go wrong. SAN > > outages cause the machine to hang up until the issue is resolved > > (in which case it just seems to continue) or it doesn't recover at > > all and requires a reboot. Note that I don't spend a significant > > amount of time on this, so it may be that I could do things a little > > better. I have also not tested the failover stuff very well (I > > only upgraded this machine to 7-STABLE fairly recently). Disk > > access seems to be restricted to a single path at a time. Problem > > solving is very tricky as there is very little information to trace > > which path/disk refers to which fabric/storage device/LUN. > > > > Russell, > Thank you for your insights. It's good to see you have no problems > with isp(4) and Qlogic HBAs. Though I'm concerned about > multipathing. We run 6.x-RELEASE releases so it seems we have > to upgrade to 7.0-RELEASE to achieve that goal. gmultipath(8) > code is fairly new so I suppose it's not that mature yet as in > Linux. Unfortunately it is only an active/passive approach with > no load balancing (the active path is active until a BIO request is > failed with EIO or ENXIO) Well, it is worse than that: HP EVA arrays have 2 different multipath behaviours. VCS 3.x firmware is active/passive, whereas VCS 4.x is active/active. Active/active as well are all XCS firmware versions. All newer EVAs run XCS. To properly do multipathing on active/active EVAs your multipathing software should be aware of the ALUA stuff. On active/active EVAs you should fire your read commands to the right HSV controller, if you take the other HSV things will work, but the controller you sent the read to will have to do a proxy read to the HSV controller that "owns" the LUN. This will be slower that taking the right HSV in one go. It also consumes bandwith on the HSV controller's mirror port(s). Writes do not matter, they are mirrored to the write cache in each HSV anyway. Linux devicemapper is sort-of getting there now. For the longest time HP did not support devicemapper, and for good reasons too. To make things interesting I think I remember Matt (the isp(4) author) telling me that some ispfw(4) versions not getting it right. If the adapter firmware does not properly inform the isp(4) driver of SAN disruptions you are obviously doomed as a multipathing driver that depends on the underlying HBA drivers to feed SAN problems/status upstream. In short: if you use isp(4), always load ispfw(4) too. Getting all the components in a FC SAN to DTRT is unfortunately still a major pain in the backside. hth Wilko -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 17:45:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 513791065684; Mon, 9 Jun 2008 17:45:17 +0000 (UTC) (envelope-from SRS0=89848692e707ddf517b3c4300980b862705f40ce=727=es.net=oberman@es.net) Received: from postal1.es.net (postal4.es.net [IPv6:2001:400:6000:1::66]) by mx1.freebsd.org (Postfix) with ESMTP id EF1398FC2B; Mon, 9 Jun 2008 17:45:16 +0000 (UTC) (envelope-from SRS0=89848692e707ddf517b3c4300980b862705f40ce=727=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal4.es.net (Postal Node 4) with ESMTP (SSL) id PXC89913; Mon, 09 Jun 2008 10:45:13 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 60E124501A; Mon, 9 Jun 2008 10:45:12 -0700 (PDT) To: Jeremy Chadwick In-Reply-To: Your message of "Sun, 08 Jun 2008 22:30:35 PDT." <20080609053035.GA6859@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213033512_82978P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Mon, 09 Jun 2008 10:45:12 -0700 From: "Kevin Oberman" Message-Id: <20080609174512.60E124501A@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ; ; ; ; ; X-Sender: X-To_Name: Jeremy Chadwick X-To_Domain: freebsd.org X-To: Jeremy Chadwick X-To_Email: koitsu@FreeBSD.org X-To_Alias: koitsu Cc: Evren Yurtesen , freebsd-stable@freebsd.org, John Baldwin , Andrew Snow Subject: Re: cpufreq broken on core2duo 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, 09 Jun 2008 17:45:17 -0000 --==_Exmh_1213033512_82978P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Sun, 8 Jun 2008 22:30:35 -0700 > From: Jeremy Chadwick > > On Sun, Jun 08, 2008 at 10:13:43PM -0700, Kevin Oberman wrote: > > > Date: Sat, 7 Jun 2008 09:48:12 -0700 > > > From: Jeremy Chadwick > > > Sender: owner-freebsd-stable@freebsd.org > > > > > > On Sat, Jun 07, 2008 at 05:51:38PM +0300, Evren Yurtesen wrote: > > > > By the way, there is another thing I am wondering about. If I enable HTT > > > > and Intel Enhanced SpeedStep in bios on a 3.00GHZ p4 CPU I see: > > > > > > > > cpu0: on acpi0 > > > > acpi_perf0: on cpu0 > > > > p4tcc0: on cpu0 > > > > cpu1: on acpi0 > > > > est1: on cpu1 > > > > est: CPU supports Enhanced Speedstep, but is not recognized. > > > > est: cpu_vendor GenuineIntel, msr f2700000f27 > > > > device_attach: est1 attach returned 6 > > > > p4tcc1: on cpu1 > > > > > > > > dev.cpu.0.freq_levels: 1500/27000 1312/23625 1200/13000 1050/11375 900/9750 > > > > 750/8125 600/6500 450/4875 300/3250 150/1625 > > > > dev.acpi_perf.0.freq_settings: 1500/27000 1200/13000 > > > > dev.cpufreq.0.%driver: cpufreq > > > > dev.cpufreq.0.%parent: cpu0 > > > > dev.cpufreq.1.%driver: cpufreq > > > > dev.cpufreq.1.%parent: cpu1 > > > > dev.p4tcc.0.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > > > 2500/-1 1250/-1 > > > > dev.p4tcc.1.freq_settings: 10000/-1 8750/-1 7500/-1 6250/-1 5000/-1 3750/-1 > > > > 2500/-1 1250/-1 > > > > > > > > and it does not allow me to set the freq. of the cpu. > > > > > > How are you setting the frequency? Are you using powerd? You do not > > > have to enable SpeedStep in your BIOS to achieve throttling CPU clock > > > speed. In fact, I would highly recommend leaving EIST/SpeedStep in the > > > BIOS *disabled*, and let powerd adjust the clock frequency via ACPI. > > > > I must strongly recommend against this. EST is MUCH more efficient on > > its control of power use than simple throttling. So much so that on my > > systems that support EST, I remove cpufreq from the kernel. (In all > > cases, throttling means either simple throttling or throttling by using > > TCC.) > > The reality of the situation is that users cannot use EIST reliably on > FreeBSD. I cannot imagine removing cpufreq would solve the "runtime > went backwards" issue. The EIST problem needs to be fixed. If the > folks who work on it do not have present-day hardware (C2Ds, etc.), I > will be more than happy to purchase them whatever they need. > > > I did quite a bit of testing on power management a year or so ago and > > found that throttling was of value only for controlling CPU temperature. > > For real power management, EST works far better as it adjust frequency > > (actual clock rate) and CPU voltage while throttling just stops and > > starts the clock without changing its actual frequency. (This came as a > > surprise to me about 5 years ago when I first discovered it.) > > As far as I know, the ACPI frequency toggling does in fact adjust the > CPU clock rate -- because the values in dev.cpu.0.freq_levels are > defined by the ACPI configuration on the machine. It claims to adjust clock speed, but it actually simply "skips" cycles. The system clocks at its standard rate or that provided by other power management tools. Since throttling (whether done by the external throttling or TCC) will provide 8 "frequencies". If SpeedStep, EST, or PowerNow is available, it will show 8 times the number of "true" frequencies provided by any of those. (Actually, on my system EST provides 16 "frequencies" of which 4 are actual changes in the clock and the others are from 4 voltages it uses. 4**2 = 16. If you see exactly eight "frequencies" with cpufreq, you have no "true" frequency adjustment. > I'd confirm this, but looking at the kernel code doesn't help -- I > cannot find the definition of the CPUFREQ_LEVELS function or macro. > > > At idle, throttling does exactly nothing. EST reduces voltage on the > > CPU and saves power even when idle. At full CPU load, throttling reduces > > performance and power consumption equally. EST beats it by a slim > > margin. > > I thought the power-saving modes of the CPU (C1E/C2E/C3E/C4E) could be > used *without* enabling EIST. I don't think FreeBSD has kernel or > userland support utilities to enable/disable CPU-level features. > Something like RMClock for Windows would be quite useful. (If you have > the opportunity to run it, do so; you'll see what I mean, re: all the > features being toggleable individually). Yes, C-states are not tied to EST or any "frequency-like" things. And they are a really significant factor in power saving. I'll have to look at RMClock. I am not familiar with it. (I don't normally use Windows, but I can boot it on my laptop.) > > The big win is at moderate load. Throttling can result is very poor > > results for aps like video and music which will place a continuous load > > on the system, but only 20-60% (in the case of my test system). It > > tended to make the system seem sluggish. EST does a much better job in > > this case as it lowers CP voltage and clock rate to maximize performance > > while minimizing power. > > > > If your only concern is keeping the system cool, throttling will do the > > job, but if you want efficient power utilization, use EST if possible. > > In the case est does not attach (e.g. no EIST support enabled in > FreeBSD), the throttling method resorts to simply suspending the system, > then yes I completely agree -- EIST is significantly better than that. If you have no better method than throttling, you have to go with it, but it's way to primitive to be a really big help. FWIW, on my ThinkPad (uni-processor), with no cpufreq in the system, I see: dev.cpu.0.freq_levels: 2000/27000 1750/23625 1600/22600 1400/19775 1333/19666 1166/17207 1066/16733 932/14641 800/13800 700/12075 600/10350 500/8625 400/6900 300/5175 200/3450 100/1725 It is running EST and P4TCC is explicitly disabled in loader.conf. Oh, and my testing showed that TCC did a slightly better job than simple throttling, though they do about the same thing, so the difference is probably not significant. With the current code, if P4TCC is available, it will be used in preference to throttling. Both will never be used together. (That was a good way to lock up your system during the time both were used.) -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213033512_82978P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFITWwokn3rs5h7N1ERAm85AKCYpIStWHoj49HzALQjnT5XUdThTgCfSJnK ol+L6HF6LWyy92txK4MHdKM= =EYtG -----END PGP SIGNATURE----- --==_Exmh_1213033512_82978P-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 18:33:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9319F106564A for ; Mon, 9 Jun 2008 18:33:21 +0000 (UTC) (envelope-from spomerg@cwu.EDU) Received: from donald.cts.cwu.edu (donald.cts.cwu.edu [198.104.67.147]) by mx1.freebsd.org (Postfix) with ESMTP id 791668FC14 for ; Mon, 9 Jun 2008 18:33:21 +0000 (UTC) (envelope-from spomerg@cwu.EDU) Received: from CONVERSION-CWU-DAEMON.DONALD.CTS.CWU.EDU by DONALD.CTS.CWU.EDU (PMDF V6.4-b2 #31513) id <01MVSB94QF1S0002YF@DONALD.CTS.CWU.EDU> for freebsd-stable@freebsd.org; Mon, 09 Jun 2008 11:33:20 -0700 (PDT) Received: from hermes.cwu.edu (hermes.cwu.edu [172.16.21.28]) by DONALD.CTS.CWU.EDU (PMDF V6.4-b2 #31513) with ESMTP id <01MVSB94DIQ60002K6@DONALD.CTS.CWU.EDU> for freebsd-stable@freebsd.org; Mon, 09 Jun 2008 11:33:20 -0700 (PDT) Received: from cwugate1-MTA by hermes.cwu.edu with Novell_GroupWise; Mon, 09 Jun 2008 11:33:20 -0700 Date: Mon, 09 Jun 2008 11:33:06 -0700 From: Gavin Spomer To: freebsd-stable@freebsd.org Message-id: <484D14F20200009000019CBD@hermes.cwu.edu> MIME-version: 1.0 X-Mailer: Novell GroupWise Internet Agent 7.0.2 HP Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Content-disposition: inline Subject: Re: 6.2-STABLE => 7.0-STABLE Upgrade root partition more full 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, 09 Jun 2008 18:33:21 -0000 >>> Skip Ford 06/06/08 1:39 PM >>> Gavin Spomer wrote: > I successfully did my first FreeBSD upgrade yesterday after looking at = the manual, and cross referencing with Googling and getting help from our = network engineer here at CWU. Before the upgrade, running df showed: >=20 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 77662 389358 17% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 588 466432 0% /tmp > /dev/da0s1f 268217320 4866120 241893816 2% /usr > /dev/da0s1d 4298926 162066 3792946 4% /var >=20 > Now it shows: >=20 > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 507630 184834 282186 40% / > devfs 1 1 0 100% /dev > /dev/da0s1e 507630 426 466594 0% /tmp > /dev/da0s1f 268217320 5514844 241245092 2% /usr > /dev/da0s1d 4298926 187570 3767442 5% /var >=20 > Notice the the increase in the root partition. Should I have made this = partition bigger when I first installed? Is there any cleaning up I can do = after version upgrades? I would've thought /usr would be the one that grew = more, but then again my /usr partition is fairly sizeable. Does 7.0 just = take up a lot more of the root partition than 6.2? 7.0 installs debugging symbols for the kernel and modules by default. You can avoid that by defining INSTALL_NODEBUG during installkernel. If already installed, you can delete the symbol files without causing problems as long as you don't need to debug the kernel. Also, when you install a new kernel, the old kernel is saved as kernel.old so you now have 2 kernels in /boot instead of one. If you're positive the new kernel works fine, the old kernel can be removed as that's only used to recover from a new kernel with problems. But, your space really isn't that close to the limit, IMO. You appear to have enough space to have an old and new kernel installed both with symbols, so I'd leave it as is in case you need to debug something or boot the old kernel. You can always take care of it later if you're about to run out of space. Why do today what you can put off 'til tomorrow? Also, consider reading UPDATING before every upgrade. The entry for 20060118 covers this issue. --=20 Skip Thanks a bunch for the info, it is helpful. Also, sorry for the lateness = of my reply. Any suggestions for selectively reading UPDATING? It IS a = rather long file. I'd rather be reading a good R.A. Salvatore novel if I'm = going to read for that long. ;) Thanks for you reply as well, Clifton. - Gavin From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 18:34:04 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 703811065678 for ; Mon, 9 Jun 2008 18:34:04 +0000 (UTC) (envelope-from peter@wemm.org) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.249]) by mx1.freebsd.org (Postfix) with ESMTP id 30A9A8FC17 for ; Mon, 9 Jun 2008 18:34:03 +0000 (UTC) (envelope-from peter@wemm.org) Received: by an-out-0708.google.com with SMTP id b33so549669ana.13 for ; Mon, 09 Jun 2008 11:34:03 -0700 (PDT) Received: by 10.100.213.4 with SMTP id l4mr4102364ang.53.1213034746927; Mon, 09 Jun 2008 11:05:46 -0700 (PDT) Received: by 10.100.154.11 with HTTP; Mon, 9 Jun 2008 11:05:46 -0700 (PDT) Message-ID: Date: Mon, 9 Jun 2008 11:05:46 -0700 From: "Peter Wemm" To: "Joe Kelsey" In-Reply-To: <484CD995.3040002@zircon.seattle.wa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484CD995.3040002@zircon.seattle.wa.us> Cc: stable@freebsd.org Subject: Re: 6.3-RELEASE versus 5.2-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: Mon, 09 Jun 2008 18:34:04 -0000 On Mon, Jun 9, 2008 at 12:19 AM, Joe Kelsey wrote: > Can anyone verify that some number of bugs related to either a) gmirror, b) > bge and/or c)twe were fixed after the release of 6.3? That is as far as I > can tell the reason that Jo objets to EoL of 6.2, the fact that 6.3 is > unusable due to these late-fixed bugs. I can't speak for gmirror. But I suspect the bigger problem with bge and 3ware is that the drivers attempt to provide coverage for many many variants of hardware. The bge driver covers (at last count) 59 different chips and variants. New variants keep on arriving, with new bugs and new fixes, so our driver requires updates for these *new* chips. There's the catch. The same driver in 6.2 would require the same updates. If Joe's hardware worked with 6.2, it would work with 6.3 as well. The situation is similar with 3ware. There are even two different drivers. twe and twa. twe supports two different hardware interfaces. twa has 4 different hardware interfaces. twa has been getting frequent updates to handle new variations of the 9000 series cards. Again, it seems likely that Joe's hardware would run fine with 6.3-R if it already works with 6.2-R. So far we don't even know which of the 59 variants of bge hardware Jo wants to run with, nor which 3ware driver.. let alone the 3ware variants. I don't recall him mentioning whether it is twe or twa. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 "If Java had true garbage collection, most programs would delete themselves upon execution." -- Robert Sewell From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 18:48:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37F6E1065672 for ; Mon, 9 Jun 2008 18:48:59 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) Received: from mx1-a.inoc.net (mx1-a.inoc.net [64.246.131.30]) by mx1.freebsd.org (Postfix) with ESMTP id D9A8C8FC15 for ; Mon, 9 Jun 2008 18:48:58 +0000 (UTC) (envelope-from rblayzor.bulk@inoc.net) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=inoc.net; h=Received:From:To:Subject:Date; b=lHJmHVms8M82LfG0Nxk51mIMP2kt1F4JjGseOI7LNcqGJzGJyFHoV1pJE0HrzeD8o4OzvYx5i/aa3QuCMYdhlhO8QtmDdryA2k+y7qocNa6Lrr61hflMxxD82sB8pwf337BFfD85onne/Ncrzv36Ck3xYyKLPbqWPaan2wibJgI=; Received: from void.ops.inoc.net (vanguard.noc.albyny.inoc.net [64.246.135.8]) by mx1-a.inoc.net (build v8.3.29) with ESMTP id 150419829-1941382 for ; Mon, 09 Jun 2008 18:48:58 +0000 (UTC) Message-Id: <0D67AF88-6593-47F3-9774-BE1875795B80@inoc.net> From: Robert Blayzor To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 9 Jun 2008 14:48:57 -0400 X-Mailer: Apple Mail (2.924) Subject: BOOTP and no default route 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, 09 Jun 2008 18:48:59 -0000 Is there any way to prevent the BOOTP client from injecting a default route? When I originally set things up our DHCP server would not send a default route because there was no gateway, local only. If you leave out the default route, the server will try proxy-arp when ends up putting a default route to itself in the routing table. The problem is that on startup the servers actually setup static networks with default routes out another interface. The problem is, if the BOOTP client puts in a default route, we cannot easily add another default because one already exists. The only way I've found around this behavior was to error the BOOTP client out and send it a default gateway that does not exist on the local net the DHCP server provides. This causes the BOOTP client not to set a default route and all works fine. Obviously this seems like a cobb/hack and was wondering if there was a BOOTP option or kernel tweak that can be done to tell the BOOTP client not to use proxy-arp. -- Robert Blayzor, BOFH INOC, LLC rblayzor@inoc.net http://www.inoc.net/~rblayzor/ From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 19:02:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB1FC106564A for ; Mon, 9 Jun 2008 19:02:21 +0000 (UTC) (envelope-from tss@iki.fi) Received: from dovecot.org (dovecot.org [82.118.211.50]) by mx1.freebsd.org (Postfix) with ESMTP id 6F2518FC13 for ; Mon, 9 Jun 2008 19:02:21 +0000 (UTC) (envelope-from tss@iki.fi) Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118]) by dovecot.org (Postfix) with ESMTP id 21FE1FA8A12 for ; Mon, 9 Jun 2008 21:40:58 +0300 (EEST) From: Timo Sirainen To: freebsd-stable@freebsd.org Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-P5dWbwhPQ5WN/kDDEBIO" Date: Mon, 09 Jun 2008 21:40:54 +0300 Message-Id: <1213036854.3904.967.camel@hurina> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Subject: Environment clearing broken in 7.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: Mon, 09 Jun 2008 19:02:21 -0000 --=-P5dWbwhPQ5WN/kDDEBIO Content-Type: text/plain Content-Transfer-Encoding: quoted-printable I think clearing environment using: environ[0] =3D NULL; has been kind of a semi-standard for a while now. At least Dovecot and Postfix clears their environment this way. But this no longer works in FreeBSD 7.0 (putenv(), environ[0]=3DNULL, putenv() -> everything is visible again). Was this change intended, or will this be fixed? Looks like I could work around this by using: environ =3D NULL; but I'm afraid what other OSes that change would break. I guess going through environ and unsetenv()ing everything would work too, but it feels annoyingly slow for such a simple operation. --=-P5dWbwhPQ5WN/kDDEBIO Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBITXk2yUhSUUBViskRAqQaAKCHRzyGcbn6gvwoE+WnEhOcs4yvMACgkrsT QNcYAgT8cy1CMbc/dq3VBTk= =FPt5 -----END PGP SIGNATURE----- --=-P5dWbwhPQ5WN/kDDEBIO-- From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 19:03:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 076CB1065777 for ; Mon, 9 Jun 2008 19:03:06 +0000 (UTC) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.179]) by mx1.freebsd.org (Postfix) with ESMTP id 92A9B8FC1B for ; Mon, 9 Jun 2008 19:03:05 +0000 (UTC) (envelope-from max@love2party.net) Received: from vampire.homelinux.org (dslb-088-064-176-094.pools.arcor-ip.net [88.64.176.94]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1K5me01tbV-0005Qn; Mon, 09 Jun 2008 21:03:04 +0200 Received: (qmail 31018 invoked from network); 9 Jun 2008 19:01:03 -0000 Received: from myhost.laiers.local (192.168.4.151) by ns1.laiers.local with SMTP; 9 Jun 2008 19:01:03 -0000 From: Max Laier Organization: FreeBSD To: freebsd-hackers@freebsd.org Date: Mon, 9 Jun 2008 21:02:16 +0200 User-Agent: KMail/1.9.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200806092102.16651.max@love2party.net> X-Provags-ID: V01U2FsdGVkX181e7jQfF6iYMJoNnzGgArt9O2xN9oWncBjdNf r0D+DrNpqQSmJgHD6oFWdsSWaIWSoEOtP/6opl9kMB9dzt6ZNK t1VM67aMgCZfTZl9S7sgw== Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: New Mailinglist: freebsd-wip-status@ X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@freebsd.org List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jun 2008 19:03:06 -0000 Hello everybody, SHORT SUMMARY: http://lists.freebsd.org/mailman/listinfo/freebsd-wip-status Subscribe today!! Tell all your friends, co-workers and everybody you know who's interested in FreeBSD. Post this on your blog! ;) LONG VERSION: if you've been around lately you might already know about our effort to provide periodical status reports about ongoing FreeBSD related WIPs. The past reports can be found at: http://www.freebsd.org/news/status This system has some shortcomings however. The biggest one is that due to the collection overhead and the high rate of exciting development under the FreeBSD umbrella most of the reports are somewhat outdated by the time they get to "print". Other projects never are announced in the status reports because they happen in-between and fall through the cracks. In order to improve this situation we have created a new mailing list that should receive status reports from now on. This list will be moderated in order to keep it close to the subject. The intend is to make this an inviting place for people with little time to still stay on top of the latest and greatest in and around FreeBSD, but where one can avoid the chatter that comes with the technical debates on the normal lists. For all developers, contributors, conference organizers, 3rd party distributions, SoC-students and whoeverelse has exciting news about their FreeBSD related project this means little work. Most of you already are sending out announcement- and update-emails to lists like current@, net@ or whichever fits your project in order to inform the world about the progress you've made. Now we would like to invite you to BCC: this email to freebsd-wip-status@ as well for maximum exposure. Emails with a lot of gory, technical details are probably not suited for this list, but the usual: "Hey, I've got these cool patches to test. Here is what they do: ..." most certainly is. So this is really like the status reports before, but everybody subscribed can get the news when they happen (and not three month later when the next status reports are due). I hope for your support in bootstrapping this idea. During the next few weeks I'll keep a close eye on the lists I'm subscribed to and will encourage people to forward matching posts to freebsd-wip-status@ You are welcome to do the same. We also plan to keep the status reports as is, but collecting the reports from this new list, too. This should give the best of both worlds, we hope. If you have any questions or would like to help with editing the status reports, please contact monthly@FreeBSD.org (reply-to set) or myself directly. -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 23:05:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19C471065687 for ; Mon, 9 Jun 2008 23:05:43 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id C200D8FC20 for ; Mon, 9 Jun 2008 23:05:42 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1185574ywe.13 for ; Mon, 09 Jun 2008 16:05:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=0BoX+4UYOoM/O00JcY8D3CMaDSxOPWANp0jl+EL1TJE=; b=YX+PGkXGYFPE+C9CdY7EOoODcRhPlK2cOTpYalqnNDM+7b5ZuwrfZdkO6LuXLiJ84y hiAgnr44d57kEONIuY8Bm2o2rO7P8D8PKDF3lQ1Bwddxj+gVB+LTjlIV6UOj+U71X7q+ Hez8IIdc5w4CqVM9N5jTFuphnNeuHb2I45IG0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=ldAONaLAsznf34YklIByQ/OtDsb1HgNdbiSFvjVCG6x0FdFZgJBzLExY3Z2GDswFiQ rSPb/q3tYKvduM4jXZ0+d5/cFKprJ5D0KIeONkXiINqOar3xeeZMQQQ6ZaUysoGiXGfZ 9fI3rLb1mJlBeuA0Z1yLZe8zMCDlLMuSryJkQ= Received: by 10.151.112.1 with SMTP id p1mr7204447ybm.29.1213052738089; Mon, 09 Jun 2008 16:05:38 -0700 (PDT) Received: by 10.151.51.5 with HTTP; Mon, 9 Jun 2008 16:05:38 -0700 (PDT) Message-ID: Date: Mon, 9 Jun 2008 16:05:38 -0700 From: "Freddie Cash" To: "FreeBSD Stable" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 09 Jun 2008 23:05:43 -0000 On Mon, Jun 9, 2008 at 3:25 PM, Jo Rhett wrote: > On Jun 8, 2008, at 3:27 PM, Freddie Cash wrote: >> Like I said, you have to define what you mean by "stable" and >> "unstable" before the discussion can continue. >> >> "stable" can mean many things to many people. You talk about feature >> stability. Other may talk about "number of open bugs" as being >> unstable. Others may talk of API/ABI stability. Other may mean "code >> that don't crash a system". >> >> Your view of "stable" meaning "features don't change" is no where near >> my definition of stable (systems that don't crash, and where I can run >> binaries from older point releases on newer point releases). > > I don't care about features, I care about uptime. "stable" in my brain > means that there isn't 150 revisions to the cvs tree in the 2 months post > release regarding kernel and core drivers. "stable" is also overloaded with > meaning "will be around long enough that I can focus on other projects > instead of replacing it nearly instantly with a new release" > > FWIW, since you clearly misunderstood my point of view. Actually, I believe you misunderstood me, as you quoted me out of context, and quoted my reply to someone else. :) My message to you was "define what you mean by stable and unstable". Which, if I follow correctly, you define as "never having any commits to the codebase". I care about uptime as well (along with performance and maintainability). And so far, none of our systems using em(4) cards, bge(4) cards, twa(4) cards, gmirror(8) (although I've since moved those to 7-STABLE with ZFS alongside), running on bare metal or in VMs have any issues with 6.3-RELEASE or 7.0-RELEASE. But, how does "the number of commits since release" have any bearing on uptime of a system you haven't tested? ;) Those seem to be completely unrelated to me. -- Freddie Cash fjwcash@gmail.com From owner-freebsd-stable@FreeBSD.ORG Mon Jun 9 23:25:28 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9165C106567A for ; Mon, 9 Jun 2008 23:25:28 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from dsl254-019-221.sea1.dsl.speakeasy.net (dsl254-019-221.sea1.dsl.speakeasy.net [216.254.19.221]) by mx1.freebsd.org (Postfix) with ESMTP id 5D53E8FC0C for ; Mon, 9 Jun 2008 23:25:28 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 84928 invoked from network); 9 Jun 2008 23:25:28 -0000 Received: from localhost (HELO zircon.zircon.seattle.wa.us) (127.0.0.1) by localhost with ESMTP; 9 Jun 2008 23:25:28 -0000 Message-ID: <484DBBE7.6080908@zircon.seattle.wa.us> Date: Mon, 09 Jun 2008 16:25:27 -0700 From: Joe Kelsey User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Closing the Jo Rhett argument 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, 09 Jun 2008 23:25:28 -0000 Jo Rhett has clearly stated (in offline reply) that they do not participate in the -BETA and-RC cycles leading up to -RELEASE, so they therefore do not have any issues with -RELEASE and EoL to raise. Actually, they still have the same complaints to raise about EoL, but since they refuse to participate in the -RELEASE process, they do not have valid points to raise. I ask that everyone please stop communicating with the persona known on this list as "Jo Rhett" unless and until they participate in the -BETA, -RC, and -RELEASE process. You cannot raise any sort of valid complaint about -RELEASE, EoL or bugs if you do not participate in finding bugs during the -BETA and -RC stages prior to the -RELEASE. If you instead choose to try to run -RELEASE and find bugs then, then complain about the bugs you found and continue to complain that these bugs were not found by someone else and fixed ahead of time, you have no issues and do not deserve an answer, no matter how much you try to frame it as a "policy" question. /Joe From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 00:50:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4530B1065673; Tue, 10 Jun 2008 00:50:45 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id AE7FE8FC18; Tue, 10 Jun 2008 00:50:44 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from nirvana.my.domain (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTPS id 1E21F5FB8228; Tue, 10 Jun 2008 00:32:27 +0000 (UTC) Received: by nirvana.my.domain (Postfix, from userid 1000) id 557127DB8; Tue, 10 Jun 2008 02:32:24 +0200 (CEST) Date: Tue, 10 Jun 2008 02:32:24 +0200 From: Jona Joachim To: Kris Kennaway Message-ID: <20080610003222.GA3822@nirvana.my.domain> References: <484BE563.90102@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline In-Reply-To: <484BE563.90102@FreeBSD.org> X-PGP-Key: http://www.hcl-club.lu/~jaj/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 00:50:45 -0000 --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > Jona Joachim wrote: > > Hi! > >=20 > > pkg_delete core dumps on me when it tries to remove linux-tiff. > > I can reproduce this reliably. >=20 > > FWIW you can find the core dump here: > > http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core >=20 > You need to obtain the backtrace, see the developers handbook. I built pkg_delete with -g but gdb says 'no debugging symbols found'. Is the following information sufficient or do I need to rebuild everything = with debugging information turned on? Script started on Tue Jun 10 02:18:04 2008 nirvana% sudo gdb pkg_delete GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"...(no debugging symbols fo= und)... (gdb) run linux-tiff-3.7.1 Starting program: /usr/sbin/pkg_delete linux-tiff-3.7.1 (no debugging symbols found)...(no debugging symbols found)...(no debugging= symbols found)...pkg_delete: file '/compat/linux/usr/bin/bmp2tiff' doesn't= exist pkg_delete: file '/compat/linux/usr/bin/fax2ps' doesn't exist pkg_delete: file '/compat/linux/usr/bin/fax2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/gif2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/pal2rgb' doesn't exist pkg_delete: file '/compat/linux/usr/bin/ppm2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/ras2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/raw2tiff' doesn't exist pkg_delete: file '/compat/linux/usr/bin/rgb2ycbcr' doesn't exist pkg_delete: file '/compat/linux/usr/bin/thumbnail' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2bw' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2pdf' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2ps' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiff2rgba' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffcmp' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffcp' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffdither' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffdump' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffinfo' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffgt' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffmedian' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffset' doesn't exist pkg_delete: file '/compat/linux/usr/bin/tiffsplit' doesn't exist pkg_delete: file '/compat/linux/usr/lib/libtiff.so.3' doesn't exist pkg_delete: file '/compat/linux/usr/lib/libtiff.so.3.7.1' doesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/COPYRIGHT' does= n't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/README' doesn't= exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/RELEASE-DATE' d= oesn't exist pkg_delete: file '/compat/linux/usr/share/doc/libtiff-3.7.1/VERSION' doesn'= t exist pkg_delete: file '/compat/linux/usr/share/man/man1/bmp2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/fax2ps.1.gz' doesn't exi= st pkg_delete: file '/compat/linux/usr/share/man/man1/fax2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/gif2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/pal2rgb.1.gz' doesn't ex= ist pkg_delete: file '/compat/linux/usr/share/man/man1/ppm2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/ras2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/raw2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/rgb2ycbcr.1.gz' doesn't = exist pkg_delete: file '/compat/linux/usr/share/man/man1/sgi2tiff.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/thumbnail.1.gz' doesn't = exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2bw.1.gz' doesn't ex= ist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2pdf.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2ps.1.gz' doesn't ex= ist pkg_delete: file '/compat/linux/usr/share/man/man1/tiff2rgba.1.gz' doesn't = exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffcmp.1.gz' doesn't ex= ist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffcp.1.gz' doesn't exi= st pkg_delete: file '/compat/linux/usr/share/man/man1/tiffdither.1.gz' doesn't= exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffdump.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffinfo.1.gz' doesn't e= xist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffgt.1.gz' doesn't exi= st pkg_delete: file '/compat/linux/usr/share/man/man1/tiffmedian.1.gz' doesn't= exist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffset.1.gz' doesn't ex= ist pkg_delete: file '/compat/linux/usr/share/man/man1/tiffsplit.1.gz' doesn't = exist Program received signal SIGSEGV, Segmentation fault. 0x0804c6b4 in ?? () (gdb) bt #0 0x0804c6b4 in ?? () #1 0xbfbfdd7b in ?? () #2 0x0804efac in ?? () #3 0x08112130 in ?? () #4 0x0811a440 in ?? () #5 0x0810b160 in ?? () #6 0x08112130 in ?? () #7 0x0811a440 in ?? () #8 0xffffffff in ?? () #9 0x00000000 in ?? () #10 0x0810b200 in ?? () #11 0x08112130 in ?? () #12 0x00000000 in ?? () #13 0x08126580 in ?? () #14 0x0804ef9c in ?? () #15 0x081252e4 in ?? () #16 0x081258f8 in ?? () #17 0x081252c4 in ?? () #18 0x0810b160 in ?? () #19 0x00000007 in ?? () #20 0x081258fc in ?? () #21 0x0812534c in ?? () #22 0x00000000 in ?? () #23 0x7261762f in ?? () #24 0x2f62642f in ?? () #25 0x2f676b70 in ?? () #26 0x756e696c in ?? () #27 0x61625f78 in ?? () #28 0x662d6573 in ?? () #29 0x5f342d63 in ?? () #30 0x2b2f3331 in ?? () #31 0x55514552 in ?? () #32 0x44455249 in ?? () #33 0x2e59425f in ?? () #34 0x6c585956 in ?? () #35 0x0000756e in ?? () #36 0x000d7c44 in ?? () #37 0x08052c44 in ?? () #38 0x00001000 in ?? () #39 0xfffffffc in ?? () #40 0x480fb02e in malloc () from /lib/libc.so.7 #41 0x0804a4bb in ?? () #42 0x00000000 in ?? () #43 0x00000000 in ?? () #44 0x080523c0 in optind () #45 0x00000001 in ?? () #46 0x08124a48 in ?? () #47 0x00000002 in ?? () #48 0x00000004 in ?? () #49 0x0810b360 in ?? () #50 0x081121c0 in ?? () #51 0x08114070 in ?? () #52 0x08114078 in ?? () #53 0x00000002 in ?? () #54 0x00000000 in ?? () #55 0x00000000 in ?? () #56 0x00000002 in ?? () #57 0x00000018 in ?? () #58 0x00000014 in ?? () #59 0x08124914 in ?? () #60 0x7273752f in ?? () ---Type to continue, or q to quit--- #61 0x6d6f682f in ?? () #62 0x616a2f65 in ?? () #63 0x0000006a in ?? () #64 0x08124a44 in ?? () #65 0x08124a60 in ?? () #66 0x08124728 in ?? () #67 0x08124734 in ?? () #68 0x0812490c in ?? () #69 0x08124914 in ?? () #70 0x08124910 in ?? () #71 0x08124918 in ?? () #72 0x081242e4 in ?? () #73 0x081248f8 in ?? () #74 0x081242c4 in ?? () #75 0x08124a48 in ?? () #76 0x08124728 in ?? () #77 0x081248fc in ?? () #78 0x0812434c in ?? () #79 0x08124334 in ?? () #80 0x08124928 in ?? () #81 0x08124730 in ?? () #82 0x00000001 in ?? () #83 0x08124924 in ?? () #84 0xbfbfe268 in ?? () #85 0x480d7c5f in fts_set_clientptr () from /lib/libc.so.7 #86 0x0804a931 in ?? () #87 0x08114068 in ?? () #88 0x00000008 in ?? () #89 0xbfbfe648 in ?? () #90 0x48162417 in wcrtomb () from /lib/libc.so.7 #91 0x08049ab7 in ?? () #92 0x08114068 in ?? () #93 0xbfbfe66c in ?? () #94 0x0805109c in __progname () #95 0x00000065 in ?? () #96 0x00003ee1 in ?? () #97 0x02bc41ed in ?? () #98 0x00000000 in ?? () #99 0x00000000 in ?? () #100 0x00010258 in ?? () #101 0x484dc842 in ?? () #102 0x00000000 in ?? () #103 0x484d92b0 in ?? () #104 0x00000000 in ?? () #105 0x484d92b0 in ?? () #106 0x00000000 in ?? () #107 0x00006c00 in ?? () #108 0x00000000 in ?? () #109 0x00000038 in ?? () #110 0x00000000 in ?? () #111 0x00001000 in ?? () #112 0x00000000 in ?? () #113 0xf000f1e2 in ?? () #114 0x00000000 in ?? () #115 0x4369c5b1 in ?? () #116 0x00000000 in ?? () #117 0x00000000 in ?? () #118 0x00000000 in ?? () #119 0x00000000 in ?? () #120 0xbfbfeb5c in ?? () #121 0x00000000 in ?? () ---Type to continue, or q to quit--- #122 0xbfbfeb18 in ?? () #123 0x0804ab0c in ?? () #124 0x00000002 in ?? () #125 0xbfbfeb5c in ?? () #126 0xbfbfe968 in ?? () #127 0x48055660 in dladdr () from /libexec/ld-elf.so.1 Previous frame inner to this frame (corrupt stack?) (gdb) quit The program is running. Exit anyway? (y or n) y nirvana%=20 Script done on Tue Jun 10 02:19:05 2008 --KsGdsel6WgEHnImy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhNy5YACgkQBLVThWGOYx5gnQCghqHnKqTSV2g6bMxB4JcYqg5d YjAAn1ar1HHKZam73dpwKnx2hePz3hIf =8Bf/ -----END PGP SIGNATURE----- --KsGdsel6WgEHnImy-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 01:14:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FD71065671 for ; Tue, 10 Jun 2008 01:14:13 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 992C18FC0C; Tue, 10 Jun 2008 01:14:12 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <484DD565.2010700@FreeBSD.org> Date: Tue, 10 Jun 2008 03:14:13 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Jona Joachim References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> In-Reply-To: <20080610003222.GA3822@nirvana.my.domain> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 01:14:13 -0000 Jona Joachim wrote: > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: >> Jona Joachim wrote: >>> Hi! >>> >>> pkg_delete core dumps on me when it tries to remove linux-tiff. >>> I can reproduce this reliably. >>> FWIW you can find the core dump here: >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core >> You need to obtain the backtrace, see the developers handbook. > > I built pkg_delete with -g but gdb says 'no debugging symbols found'. > Is the following information sufficient or do I need to rebuild everything with debugging information turned on? It was probably stripped at install, I think you can set STRIP= (i.e. empty value) but doesn't it also explain this in the handbook? Kris From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 01:15:53 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 093151065673 for ; Tue, 10 Jun 2008 01:15:53 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from mail.netconsonance.com (mail.netconsonance.com [198.207.204.4]) by mx1.freebsd.org (Postfix) with ESMTP id E20948FC19 for ; Tue, 10 Jun 2008 01:15:52 +0000 (UTC) (envelope-from jrhett@netconsonance.com) Received: from velocipes.trackintel.com (adsl-69-232-169-173.dsl.chi2ca.pacbell.net [69.232.169.173]) (authenticated bits=0) by mail.netconsonance.com (8.14.1/8.14.1) with ESMTP id m5A0qPtc077639 for ; Mon, 9 Jun 2008 17:52:25 -0700 (PDT) (envelope-from jrhett@netconsonance.com) X-Virus-Scanned: amavisd-new at netconsonance.com X-Spam-Flag: NO X-Spam-Score: -1.322 X-Spam-Level: X-Spam-Status: No, score=-1.322 tagged_above=-999 required=3.5 tests=[ALL_TRUSTED=-1.44, AWL=0.118] Message-Id: <86021481-1BCB-4E16-8DD5-EC14B8597C10@netconsonance.com> From: Jo Rhett To: stable@freebsd.org In-Reply-To: <484DBBE7.6080908@zircon.seattle.wa.us> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 9 Jun 2008 17:52:24 -0700 References: <484DBBE7.6080908@zircon.seattle.wa.us> X-Mailer: Apple Mail (2.924) Cc: Subject: Re: Closing the Jo Rhett argument 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, 10 Jun 2008 01:15:53 -0000 On Jun 9, 2008, at 4:25 PM, Joe Kelsey wrote: > Jo Rhett has clearly stated (in offline reply) that they do not > participate in the -BETA and-RC cycles leading up to -RELEASE, so > they therefore do not have any issues with -RELEASE and EoL to raise. > Actually, they still have the same complaints to raise about EoL, > but since they refuse to participate in the -RELEASE process, they > do not have valid points to raise. > > I ask that everyone please stop communicating with the persona known > on this list as "Jo Rhett" unless and until they participate in the - > BETA, -RC, and -RELEASE process. You cannot raise any sort of valid I'd really like to ignore this post because it would appear Joe Kelsey is insane (not kidding, read below). But just in case someone believes this, I have quoted here my entire reply to Joe Kelsey (only one reply). You'll notice that there is no mention of the release cycles. It wasn't part of the topic at all. > Um, no. My post was not titled "I can't upgrade to 6.3" for a > reason. The problem is the very limited EoL times set for the > releases. > > And I'm not talking about reading the CVS logs and "assuming" > anything. I have a customer using the exact same hardware we are > using who is the reporter of some serious problems with 6.3. They > were forced to stop rollout of 6.3 because of them. Their untouched > 6.2 machines continue to run fine. This is why I said "guaranteed > to fail". > > The main problem is the constant release churn. There *were* a lot > of people willing to invest time/money/machines to provide longer > EoL for releases. I was asking for information to determine what > resources were necessary and how to best apply them. (this detail > is necessary because we were going to put together a proposal to > take to our respective $EMPLOYERs and get financial support behind > this) > > I suspect your heart is in the right place, but your actual post is > of the nature of > > 1. Take the stated information and resolve it to something else > 2. Make the stated person sound like an idiot for your own > interpretation of it > 3. repeat again and again for a few more paragraphs. > > Perhaps you should just once assume that the poster is competent, > knows exactly what they saying, and means what they say? I didn't > say "guaranteed to fail" because I had a bad dream about it. I said > it because I have a 6.3 system in the test lab showing the exact > same failure. Why was I not showing the output in this thread? > BECAUSE THE THREAD WAS SUPPOSED TO BE ABOUT POLICY AND SUPPORT > RESOURCES. > > Seriously, next time you find yourself thinking that someone else is > an idiot, take a step back and try, just try to put yourself in > their shoes. Try and imagine that this person is competent, and is > being honest about what they say. And before you ask, I did do this > when I wrote this message. "I suspect your heart is in the right > place". I usually believe this in other people, it makes my world a > happier place to be. The first time mention of BETA and RC cycles came up was in his reply to me, which was full of personal insults and attacks like the following, so I discarded it without reply: > I see no reason to assume competence on your part since you have > demonstrated no competence. ... > I don't need to assume anything about you. You have demonstrated > your idiocy to everyone on the list. Please keep your insane rants > to yourself in the future. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 03:38:32 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4E641065683 for ; Tue, 10 Jun 2008 03:38:32 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 83A4B8FC15 for ; Tue, 10 Jun 2008 03:38:32 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m5A3R0ct083439; Mon, 9 Jun 2008 22:27:00 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Mon, 9 Jun 2008 22:27:00 -0500 (CDT) From: "Sean C. Farley" To: Timo Sirainen In-Reply-To: <1213036854.3904.967.camel@hurina> Message-ID: References: <1213036854.3904.967.camel@hurina> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: freebsd-stable@FreeBSD.org Subject: Re: Environment clearing broken in 7.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, 10 Jun 2008 03:38:32 -0000 On Mon, 9 Jun 2008, Timo Sirainen wrote: > I think clearing environment using: > > environ[0] = NULL; > > has been kind of a semi-standard for a while now. At least Dovecot and > Postfix clears their environment this way. But this no longer works in > FreeBSD 7.0 (putenv(), environ[0]=NULL, putenv() -> everything is > visible again). Was this change intended, or will this be fixed? It is more or less intended. When a program sets an environment variable, the environment is copied for faster/leaner usage. Changing individual values within environ is not checked else every pointer would need to be checked for consistency. What I did was to write the code to detect if environ is replaced (NULL or new array of variables). I suggest reading the two paragraphs from Open Group's getenv()[1] documentation starting at "Conforming applications are required not to modify environ directly, ..." for the rationale in the new design. Obviously, applications are not required to conform, but the documentation talks about what an OS may be doing under the covers to environ. Out of curiosity, do Dovecot and Postfix check that environ is not NULL before setting environ[0]? environ may be set to NULL at the start but not by FreeBSD's /usr/bin/env -i. > Looks like I could work around this by using: > > environ = NULL; That will work on the *BSD's, OpenSolaris and Linux. Also, this will work: environ = calloc(1, sizeof(*environ)); > but I'm afraid what other OSes that change would break. I guess going > through environ and unsetenv()ing everything would work too, but it > feels annoyingly slow for such a simple operation. OpenSolaris does something similar with environ[2]. It also detects in initenv() a replacement of environ but not changes to individual entries. Sean 1. http://www.opengroup.org/onlinepubs/000095399/functions/getenv.html 2. http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/lib/libc/port/gen/getenv.c -- scf@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 04:14:50 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6728106567B for ; Tue, 10 Jun 2008 04:14:50 +0000 (UTC) (envelope-from tss@iki.fi) Received: from dovecot.org (dovecot.org [82.118.211.50]) by mx1.freebsd.org (Postfix) with ESMTP id 68B148FC17 for ; Tue, 10 Jun 2008 04:14:48 +0000 (UTC) (envelope-from tss@iki.fi) Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118]) by dovecot.org (Postfix) with ESMTP id 9C10416471E7; Tue, 10 Jun 2008 07:14:17 +0300 (EEST) From: Timo Sirainen To: "Sean C. Farley" In-Reply-To: References: <1213036854.3904.967.camel@hurina> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-I+sIyPBBrbdbStxzgCqS" Date: Tue, 10 Jun 2008 07:14:17 +0300 Message-Id: <1213071257.3904.991.camel@hurina> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Cc: freebsd-stable@FreeBSD.org Subject: Re: Environment clearing broken in 7.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, 10 Jun 2008 04:14:51 -0000 --=-I+sIyPBBrbdbStxzgCqS Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2008-06-09 at 22:27 -0500, Sean C. Farley wrote: > On Mon, 9 Jun 2008, Timo Sirainen wrote: >=20 > > I think clearing environment using: > > > > environ[0] =3D NULL; > > > > has been kind of a semi-standard for a while now. At least Dovecot and > > Postfix clears their environment this way. But this no longer works in > > FreeBSD 7.0 (putenv(), environ[0]=3DNULL, putenv() -> everything is > > visible again). Was this change intended, or will this be fixed? >=20 > It is more or less intended. When a program sets an environment > variable, the environment is copied for faster/leaner usage. Changing > individual values within environ is not checked else every pointer would > need to be checked for consistency. What I did was to write the code to > detect if environ is replaced (NULL or new array of variables). OK, so perhaps Sendmail's way of clearing environment would be the best solution: static char *emptyenv[1] =3D { NULL }; environ =3D emptyenv; > I suggest reading the two paragraphs from Open Group's getenv()[1] > documentation starting at "Conforming applications are required not to > modify environ directly, ..." for the rationale in the new design. > Obviously, applications are not required to conform, but the > documentation talks about what an OS may be doing under the covers to > environ. How about implementing clearenv()? I'm using it now if it's available. > Out of curiosity, do Dovecot and Postfix check that environ is not NULL > before setting environ[0]? environ may be set to NULL at the start but > not by FreeBSD's /usr/bin/env -i. Yes, both check if it's NULL. (I think I originally copied my code's logic from Postfix.) > > Looks like I could work around this by using: > > > > environ =3D NULL; >=20 > That will work on the *BSD's, OpenSolaris and Linux. But not on OS X. It crashes there. > Also, this will work: > environ =3D calloc(1, sizeof(*environ)); Is this any better than using a static emptyenv[1]? BTW. I wonder if this change breaks any applications where not clearing environment could result in a security hole. As far as I know FreeBSD 7.0 is the only modern OS where environ[0]=3DNULL doesn't work. --=-I+sIyPBBrbdbStxzgCqS Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBITf+ZyUhSUUBViskRAgpiAJwLskiHlm3fBJUtOAT0Dw1i+N9eaACfQG4r w1BFns+UqmPLDvP7aJh3yMY= =ewlv -----END PGP SIGNATURE----- --=-I+sIyPBBrbdbStxzgCqS-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 07:07:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50B3410656FC for ; Tue, 10 Jun 2008 07:07:20 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from fep08.mfe.bur.connect.com.au (fep08.mfe.bur.connect.com.au [203.63.86.28]) by mx1.freebsd.org (Postfix) with ESMTP id 065F08FC1D for ; Tue, 10 Jun 2008 07:07:19 +0000 (UTC) (envelope-from quakenet1@optusnet.com.au) Received: from beastie.pamada.com (unknown [210.11.0.118]) by fep08.mfe.bur.connect.com.au (Postfix) with ESMTP id E1428F1C8 for ; Tue, 10 Jun 2008 15:58:43 +1000 (EST) Received: from [192.168.0.42] ([210.11.0.118]) (authenticated bits=0) by beastie.pamada.com (8.14.2/8.13.8) with ESMTP id m5A5wgrg002396 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Tue, 10 Jun 2008 15:58:43 +1000 (EST) (envelope-from quakenet1@optusnet.com.au) Message-Id: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> From: Jerahmy Pocott To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Tue, 10 Jun 2008 15:58:37 +1000 X-Mailer: Apple Mail (2.924) Subject: DVD-RW doesn't write 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, 10 Jun 2008 07:07:20 -0000 Hello all, I'v been trying to get this dvd burner to burn, but there seems to be something wrong with the driver for the controller or the drive.. On boot it is detected as: acd0: DMA limited to UDMA33, controller found non-ATA66 cable acd0: DVDR at ata0-master UDMA33 It is connected to: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 The message that the controller found a non-ata66 cable is an error, the cable is most certainly ata66 compatible and I'v switched it out to make sure it wasn't faulty.. The drive is able to mount and read cds/dvds fine, but on trying to use burncd it says: acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 Any further attempts produce the above message with no delay to read from the drive, resetting the ata0 channel makes it check the drive again before producing the message. On loading atapicam module it says: acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 So I wasn't able to try cdrecord with it.. I also dropped it back ti PIO4 mode in case there was a DMA issue, but I had the same results in PIO. Any more ideas? J. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 07:10:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7694A1065671 for ; Tue, 10 Jun 2008 07:10:51 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from smtp-vbr16.xs4all.nl (smtp-vbr16.xs4all.nl [194.109.24.36]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB058FC18 for ; Tue, 10 Jun 2008 07:10:50 +0000 (UTC) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (freebie.xs4all.nl [82.95.250.254]) by smtp-vbr16.xs4all.nl (8.13.8/8.13.8) with ESMTP id m5A7AIe0090545; Tue, 10 Jun 2008 09:10:19 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.14.2/8.13.3) with ESMTP id m5A7AI6v034622; Tue, 10 Jun 2008 09:10:18 +0200 (CEST) (envelope-from wb@freebie.xs4all.nl) Received: (from wb@localhost) by freebie.xs4all.nl (8.14.2/8.14.2/Submit) id m5A7AISB034621; Tue, 10 Jun 2008 09:10:18 +0200 (CEST) (envelope-from wb) Date: Tue, 10 Jun 2008 09:10:18 +0200 From: Wilko Bulte To: Jerahmy Pocott Message-ID: <20080610071018.GD34459@freebie.xs4all.nl> References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 07:10:51 -0000 Quoting Jerahmy Pocott, who wrote on Tue, Jun 10, 2008 at 03:58:37PM +1000 .. > Hello all, > > I'v been trying to get this dvd burner to burn, but there seems to be > something wrong with the driver for the controller or the drive.. > > On boot it is detected as: > acd0: DMA limited to UDMA33, controller found non-ATA66 cable > acd0: DVDR at ata0-master UDMA33 > > It is connected to: > atapci0: port > 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf irq 16 at device > 31.1 on pci0 > ata0: on atapci0 > ata1: on atapci0 > > The message that the controller found a non-ata66 cable is an error, > the cable is most certainly ata66 compatible and I'v switched it out > to make sure it wasn't faulty.. > > The drive is able to mount and read cds/dvds fine, but on trying to > use burncd it says: > acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 > > Any further attempts produce the above message with no delay to read > from the drive, resetting the ata0 channel makes it check the drive > again before producing the message. > > On loading atapicam module it says: > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > So I wasn't able to try cdrecord with it.. > > I also dropped it back ti PIO4 mode in case there was a DMA issue, but > I had the same results in PIO. > > Any more ideas? Are you sure the drive hardware is OK? I recently had this funny drive that could do everything except write. Very strange but true. -- Wilko Bulte wilko@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 07:54:00 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C04D81065677 for ; Tue, 10 Jun 2008 07:54:00 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: from dsl254-019-221.sea1.dsl.speakeasy.net (dsl254-019-221.sea1.dsl.speakeasy.net [216.254.19.221]) by mx1.freebsd.org (Postfix) with ESMTP id 7397E8FC13 for ; Tue, 10 Jun 2008 07:54:00 +0000 (UTC) (envelope-from joe@zircon.seattle.wa.us) Received: (qmail 1395 invoked from network); 10 Jun 2008 07:27:19 -0000 Received: from localhost (HELO zircon.zircon.seattle.wa.us) (127.0.0.1) by localhost with ESMTP; 10 Jun 2008 07:27:19 -0000 Message-ID: <484E2CD7.3070201@zircon.seattle.wa.us> Date: Tue, 10 Jun 2008 00:27:19 -0700 From: Joe Kelsey User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: Jerahmy Pocott References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> In-Reply-To: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 07:54:00 -0000 Jerahmy Pocott wrote: > > On loading atapicam module it says: > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 I have never managed to use burncd with any drive. In order to use atapicam, you must enable the pass? devices. My devfs.conf contains: # Commonly used by many ports link acd0 cdrom link acd0 dvd # Allow a user in the wheel group to query the smb0 device #perm smb0 0660 perm xpt0 0660 perm pass0 0660 perm pass1 0660 The xpt0 is left over from other experiments. The pass? is required to allow general access to use of growisofs. /Joe From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 08:12:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDDA9106566B for ; Tue, 10 Jun 2008 08:12:06 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: from blah.sun-fish.com (blah.sun-fish.com [217.18.249.150]) by mx1.freebsd.org (Postfix) with ESMTP id 9F6938FC25 for ; Tue, 10 Jun 2008 08:12:06 +0000 (UTC) (envelope-from stefan.lambrev@moneybookers.com) Received: by blah.sun-fish.com (Postfix, from userid 1002) id D7D0E1B10E4E; Tue, 10 Jun 2008 10:12:04 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on malcho.cmotd.com X-Spam-Level: X-Spam-Status: No, score=-10.6 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.4 Received: from hater.haters.org (hater.cmotd.com [192.168.3.125]) by blah.sun-fish.com (Postfix) with ESMTP id 886F71B10CAA; Tue, 10 Jun 2008 10:12:02 +0200 (CEST) Message-ID: <484E3752.3030702@moneybookers.com> Date: Tue, 10 Jun 2008 11:12:02 +0300 From: Stefan Lambrev User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: Joe Kelsey References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> In-Reply-To: <484E2CD7.3070201@zircon.seattle.wa.us> Content-Type: text/plain; charset=windows-1251; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93, clamav-milter version 0.93 on blah.cmotd.com X-Virus-Status: Clean Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 08:12:07 -0000 Joe Kelsey wrote: > Jerahmy Pocott wrote: >> >> On loading atapicam module it says: >> acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > I have never managed to use burncd with any drive. > > In order to use atapicam, you must enable the pass? devices. My > devfs.conf contains: > > > # Commonly used by many ports > link acd0 cdrom > link acd0 dvd > > # Allow a user in the wheel group to query the smb0 device > #perm smb0 0660 > perm xpt0 0660 > perm pass0 0660 > perm pass1 0660 > > The xpt0 is left over from other experiments. The pass? is required > to allow general access to use of growisofs. Actually xpt is needed too :) I always find ports/sysutils/k3b/pkg-message one of the most helpful "howto" regarding atapicam and burning DVDs > > /Joe > > _______________________________________________ > 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 Wishes, Stefan Lambrev ICQ# 24134177 From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 08:30:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 467EB1065676 for ; Tue, 10 Jun 2008 08:30:04 +0000 (UTC) (envelope-from freebsd-nospam@yaxom.com) Received: from gw.yaxom.com (gw.yaxom.com [59.167.217.197]) by mx1.freebsd.org (Postfix) with SMTP id 75C798FC12 for ; Tue, 10 Jun 2008 08:30:03 +0000 (UTC) (envelope-from freebsd-nospam@yaxom.com) Received: (qmail 48753 invoked from network); 10 Jun 2008 18:03:21 +1000 Received: from joker.yaxom.com (172.16.1.10) by iliad.yaxom.com with SMTP; 10 Jun 2008 18:03:21 +1000 Received: (qmail 149 invoked by uid 1001); 10 Jun 2008 18:03:21 +1000 Message-ID: Date: Tue, 10 Jun 2008 18:03:21 +1000 From: Greg Black To: Joe Kelsey References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484E2CD7.3070201@zircon.seattle.wa.us> User-Agent: Mutt/1.4.2.2i; gjb-muttsend.sh 1.7 2004-10-05 X-Uptime: 74 days X-Operating-System: FreeBSD 6.2-RELEASE-p5 i386 X-Location: Brisbane, Australia; 27.49841S 152.98439E X-URL: http://www.yaxom.com/gjb.html X-Blog: http://www.yaxom.com/gjb/blog/ X-Image-URL: http://www.yaxom.com/gjb/gjb-auug048.gif X-PGP-Key-Fingerprint: EBB2 2A92 A79D 1533 AC00 3C46 5D83 B6FB 4B04 B7D6 X-Request-PGP: http://www.yaxom.com/keys/4B04B7D6.asc Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 08:30:04 -0000 On 2008-06-10, Joe Kelsey wrote: > I have never managed to use burncd with any drive. Just for the record, I've been using burncd successfully with a variety of drives from the early days of FreeBSD through to at least 7.0-R, so I doubt if the above means very much. Greg From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 08:40:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40C04106567C for ; Tue, 10 Jun 2008 08:40:48 +0000 (UTC) (envelope-from johans@stack.nl) Received: from mx1.stack.nl (meestal-mk5.stack.nl [IPv6:2001:610:1108:5010::149]) by mx1.freebsd.org (Postfix) with ESMTP id ECA1D8FC17 for ; Tue, 10 Jun 2008 08:40:47 +0000 (UTC) (envelope-from johans@stack.nl) Received: by mx1.stack.nl (Postfix, from userid 65534) id 9CFF83FA30; Tue, 10 Jun 2008 10:40:46 +0200 (CEST) X-Spam-DCC: dcc.uncw.edu: meestal-mk5.stack.nl 1201; Body=1 Fuz1=1 Fuz2=1 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on meestal-mk5.stack.nl X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.3 X-Spam-Relay-Country: Received: from mud.stack.nl (mud.stack.nl [IPv6:2001:610:1108:5011:2e0:81ff:fe03:c4bf]) by mx1.stack.nl (Postfix) with ESMTP id 7243B3F786; Tue, 10 Jun 2008 10:40:44 +0200 (CEST) Received: by mud.stack.nl (Postfix, from userid 801) id 5421BB8F7; Tue, 10 Jun 2008 10:40:44 +0200 (CEST) Date: Tue, 10 Jun 2008 10:40:44 +0200 From: Johan van Selst To: Greg Black Message-ID: <20080610084044.GA19070@mud.stack.nl> References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-30) Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 08:40:48 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Greg Black wrote: > On 2008-06-10, Joe Kelsey wrote: > > I have never managed to use burncd with any drive. > Just for the record, I've been using burncd successfully with a variety > of drives from the early days of FreeBSD through to at least 7.0-R, so I > doubt if the above means very much. I have had lots of problems with burncd as well: it works fine with some CD burners, not with others; and hardly ever with the (cheap) DVD drives that I use. However using atapicam and growisofs as outlined in http://www.freebsd.org/doc/en/books/handbook/creating-dvds.html works just fine with all my hardware. Ciao, Johan --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iEYEAREIAAYFAkhOPgsACgkQaOElK32lxTvdEgCeKNGfatgO+raN1JHZeI5qWLBj NVAAoMIG72+xnnwqpkL4wWeROsj6EmT3 =nENe -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 08:46:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7491A106566C for ; Tue, 10 Jun 2008 08:46:30 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id CA9D78FC21 for ; Tue, 10 Jun 2008 08:46:29 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m5A8kQJJ019499; Tue, 10 Jun 2008 16:46:26 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m5A8kQwb019498; Tue, 10 Jun 2008 16:46:26 +0800 (KRAST) (envelope-from eugen) Date: Tue, 10 Jun 2008 16:46:26 +0800 From: Eugene Grosbein To: Johan van Selst Message-ID: <20080610084626.GA19069@svzserv.kemerovo.su> References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> <20080610084044.GA19070@mud.stack.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080610084044.GA19070@mud.stack.nl> User-Agent: Mutt/1.4.2.3i Cc: Greg Black , freebsd-stable@freebsd.org, Jerahmy Pocott Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 08:46:30 -0000 On Tue, Jun 10, 2008 at 10:40:44AM +0200, Johan van Selst wrote: > I have had lots of problems with burncd as well: it works fine with some > CD burners, not with others; and hardly ever with the (cheap) DVD drives > that I use. However using atapicam and growisofs as outlined in > http://www.freebsd.org/doc/en/books/handbook/creating-dvds.html > works just fine with all my hardware. burncd burns CDs fine in RELENG_4. It was and is stll broken in all of RELENG_5 code, ATA maintainer refused to fix it there. It is fixed in RELENG_6, ELENG_7 and HEAD and burns CDs fine again. And yes, do not even think about burning DVDs with burncd, just use atapicam and growisofs. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 10:10:07 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FCBB1065686 for ; Tue, 10 Jun 2008 10:10:07 +0000 (UTC) (envelope-from skip@menantico.com) Received: from vms173005pub.verizon.net (vms173005pub.verizon.net [206.46.173.5]) by mx1.freebsd.org (Postfix) with ESMTP id E67358FC32 for ; Tue, 10 Jun 2008 10:10:06 +0000 (UTC) (envelope-from skip@menantico.com) Received: from mx.menantico.com ([71.168.197.98]) by vms173005.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0K28006JERXQVD3H@vms173005.mailsrvcs.net> for freebsd-stable@freebsd.org; Tue, 10 Jun 2008 05:03:27 -0500 (CDT) Date: Tue, 10 Jun 2008 06:13:05 -0400 From: Skip Ford In-reply-to: To: Greg Black Message-id: <20080610101305.GE858@menantico.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> User-Agent: Mutt/1.4.2.3i Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 10:10:07 -0000 Greg Black wrote: > On 2008-06-10, Joe Kelsey wrote: > > > I have never managed to use burncd with any drive. > > Just for the record, I've been using burncd successfully with a variety > of drives from the early days of FreeBSD through to at least 7.0-R, so I > doubt if the above means very much. I certainly used to use burncd(8) to burn anything on any drive, but it hasn't worked for me for years now. Last I knew, it was known to be broken for 5.0 with a fix in the works at some point after that, but I've checked occasionally since then with different drives and it's still never worked. Using atapicam(4) with burning tools from ports always works. -- Skip From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 12:02:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D10211065710; Tue, 10 Jun 2008 12:02:43 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 9081B8FC26; Tue, 10 Jun 2008 12:02:43 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from nirvana.my.domain (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTPS id 7CED3BFB0032; Tue, 10 Jun 2008 12:02:42 +0000 (UTC) Received: by nirvana.my.domain (Postfix, from userid 1000) id 212617DD1; Tue, 10 Jun 2008 14:02:41 +0200 (CEST) Date: Tue, 10 Jun 2008 14:02:40 +0200 From: Jona Joachim To: Kris Kennaway Message-ID: <20080610120240.GA2964@nirvana.my.domain> References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> <484DD565.2010700@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TB36FDmn/VVEgNH/" Content-Disposition: inline In-Reply-To: <484DD565.2010700@FreeBSD.org> X-PGP-Key: http://www.hcl-club.lu/~jaj/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 12:02:44 -0000 --TB36FDmn/VVEgNH/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote: > Jona Joachim wrote: > > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > >> Jona Joachim wrote: > >>> Hi! > >>> > >>> pkg_delete core dumps on me when it tries to remove linux-tiff. > >>> I can reproduce this reliably. > >>> FWIW you can find the core dump here: > >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core > >> You need to obtain the backtrace, see the developers handbook. > >=20 > > I built pkg_delete with -g but gdb says 'no debugging symbols found'. > > Is the following information sufficient or do I need to rebuild everyth= ing with debugging information turned on? >=20 > It was probably stripped at install, I think you can set STRIP=3D (i.e.= =20 > empty value) but doesn't it also explain this in the handbook? Program received signal SIGSEGV, Segmentation fault. 0x48165a73 in strncmp () from /lib/libc.so.7 (gdb) bt #0 0x48165a73 in strncmp () from /lib/libc.so.7 #1 0x0804dad4 in delete_package (ign_err=3D0, nukedirs=3D0, pkg=3D0x805354= 0) at plist.c:462 #2 0x0804a91d in pkg_do (pkg=3D0x810b160 "linux-tiff-3.7.1") at perform.c:= 319 #3 0x08049f50 in pkg_perform (pkgs=3D0x8113068) at perform.c:112 #4 0x08049b93 in real_main (argc=3D1, argv=3D0xbfbfeb98) at main.c:145 #5 0x0804b0d5 in main (argc=3D2, argv=3D0xbfbfeb90) at pkgwrap.c:88 (gdb)=20 --TB36FDmn/VVEgNH/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhObWAACgkQBLVThWGOYx4h6QCZAS6d055YntcI98X4FYqxG6jy a4UAnjE+C5oEYqncUw2rv9s+9Vvzk18x =eFxN -----END PGP SIGNATURE----- --TB36FDmn/VVEgNH/-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 12:42:45 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B10D1065674; Tue, 10 Jun 2008 12:42:45 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 301398FC2B; Tue, 10 Jun 2008 12:42:45 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 149D31CC05F; Tue, 10 Jun 2008 05:42:45 -0700 (PDT) Date: Tue, 10 Jun 2008 05:42:45 -0700 From: Jeremy Chadwick To: Jona Joachim Message-ID: <20080610124245.GA42745@eos.sc1.parodius.com> References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> <484DD565.2010700@FreeBSD.org> <20080610120240.GA2964@nirvana.my.domain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080610120240.GA2964@nirvana.my.domain> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: Kris Kennaway , freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 12:42:45 -0000 On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote: > On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote: > > Jona Joachim wrote: > > > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > > >> Jona Joachim wrote: > > >>> Hi! > > >>> > > >>> pkg_delete core dumps on me when it tries to remove linux-tiff. > > >>> I can reproduce this reliably. > > >>> FWIW you can find the core dump here: > > >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core > > >> You need to obtain the backtrace, see the developers handbook. > > > > > > I built pkg_delete with -g but gdb says 'no debugging symbols found'. > > > Is the following information sufficient or do I need to rebuild everything with debugging information turned on? > > > > It was probably stripped at install, I think you can set STRIP= (i.e. > > empty value) but doesn't it also explain this in the handbook? > > Program received signal SIGSEGV, Segmentation fault. > 0x48165a73 in strncmp () from /lib/libc.so.7 > (gdb) bt > #0 0x48165a73 in strncmp () from /lib/libc.so.7 > #1 0x0804dad4 in delete_package (ign_err=0, nukedirs=0, pkg=0x8053540) at plist.c:462 > #2 0x0804a91d in pkg_do (pkg=0x810b160 "linux-tiff-3.7.1") at perform.c:319 > #3 0x08049f50 in pkg_perform (pkgs=0x8113068) at perform.c:112 > #4 0x08049b93 in real_main (argc=1, argv=0xbfbfeb98) at main.c:145 > #5 0x0804b0d5 in main (argc=2, argv=0xbfbfeb90) at pkgwrap.c:88 > (gdb) How about 'bt full' ? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 13:26:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0BE59106566B for ; Tue, 10 Jun 2008 13:26:34 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 5E0068FC26 for ; Tue, 10 Jun 2008 13:26:33 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from nirvana.my.domain (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTPS id 0C69D5FB8074; Tue, 10 Jun 2008 13:26:32 +0000 (UTC) Received: by nirvana.my.domain (Postfix, from userid 1000) id A73477DF9; Tue, 10 Jun 2008 15:26:30 +0200 (CEST) Date: Tue, 10 Jun 2008 15:26:30 +0200 From: Jona Joachim To: Jeremy Chadwick Message-ID: <20080610132629.GA15963@nirvana.my.domain> References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> <484DD565.2010700@FreeBSD.org> <20080610120240.GA2964@nirvana.my.domain> <20080610124245.GA42745@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="J/dobhs11T7y2rNN" Content-Disposition: inline In-Reply-To: <20080610124245.GA42745@eos.sc1.parodius.com> X-PGP-Key: http://www.hcl-club.lu/~jaj/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 13:26:34 -0000 --J/dobhs11T7y2rNN Content-Type: text/plain; charset=unknown-8bit Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 10, 2008 at 05:42:45AM -0700, Jeremy Chadwick wrote: > On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote: > > On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote: > > > Jona Joachim wrote: > > > > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > > > >> Jona Joachim wrote: > > > >>> Hi! > > > >>> > > > >>> pkg_delete core dumps on me when it tries to remove linux-tiff. > > > >>> I can reproduce this reliably. > > > >>> FWIW you can find the core dump here: > > > >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core > > > >> You need to obtain the backtrace, see the developers handbook. > > > >=20 > > > > I built pkg_delete with -g but gdb says 'no debugging symbols found= '. > > > > Is the following information sufficient or do I need to rebuild eve= rything with debugging information turned on? > > >=20 > > > It was probably stripped at install, I think you can set STRIP=3D (i.= e.=20 > > > empty value) but doesn't it also explain this in the handbook? > >=20 (snip bt) >=20 > How about 'bt full' ? Here you go. linux-tiff depends on graphics/linux-jpeg, which isn't installed however. Something must have gone wrong there, I didn't pkg_delete -f linux-jpeg. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... (gdb) run linux-tiff-3.7.1 Starting program: /usr/sbin/pkg_delete linux-tiff-3.7.1 Program received signal SIGSEGV, Segmentation fault. 0x48165a73 in strncmp () from /lib/libc.so.7 (gdb) bt full #0 0x48165a73 in strncmp () from /lib/libc.so.7 No symbol table info available. #1 0x0804dad4 in delete_package (ign_err=3D0, nukedirs=3D0, pkg=3D0x805354= 0) at plist.c:462 p =3D 0x8119420 Where =3D 0x8111130 "/compat/linux" last_file =3D 0x8119440 "usr/share/man/man1/tiffsv.1.gz" fail =3D 4294967295 preserve =3D 0 tmp =3D "/compat/linux/usr/share/man/man1/tiffsv.1.gz\000gz\000\000\000DAT= E\000+REQUIRED_BY\0005\000\000=BF\211\006\025HX=D8\027H=FC=E3=BF=BF\210=E4= =BF=BF=F9=F5\025H", '\0' , "=C8{\027H\224=E3=BF=BF", '\0'= , "\020\000\000\000\000\000\000\000=F4=E3=BF=BF", '\0' <= repeats 28 times>, "=A8=C2\022\b\000\000\000\000\020\000\000\000\000\000\00= 0\000=FF=FF=FF=FF\000\000\000\000=D2D\027H", '\0' , "\020= \000\000\000\000\000\000\000\002", '\0' , "=AC"... name =3D 0x810b200 "linux-tiff-3.7.1" prefix =3D 0x8111130 "/compat/linux" #2 0x0804a91d in pkg_do (pkg=3D0x810b160 "linux-tiff-3.7.1") at perform.c:= 319 cfile =3D (FILE *) 0x48190e80 deporigin =3D 0x810b360 "graphics/linux-jpeg" deporigins =3D (char **) 0x81111c0 depnames =3D (char **) 0x8113070 depmatches =3D (char ***) 0x8113078 home =3D "/usr/home/jaj\000\022\b\004\000\000\000D\214\rH\000\000\000\000= =FC=FF=FF=FF=FC=FF=FF=FF=FC=FF=FF=FF\v\000\000\000\\:\022\b0\000\000\000\03= 0\000\000\000\024\000\000\000\0249\022\b\0243\022\b$9\022\b\030\000\000\000= \000\000\000\000D:\022\b`:\022\b(7\022\b47\022\b\f9\022\b\0249\022\b\0209\0= 22\b\0309\022\b=E42\022\b=F88\022\b=C42\022\bH:\022\b(7\022\b=FC8\022\bL3\0= 22\b43\022\b(9\022\b=CE=CA\004\b=F8P\022\bh\217\022\b\210=E2=BF=BF_\214\rH`= :\022\bd:\022\b8=E3=BF=BF=DE\027\025H`:\022\bd:\022\b\004\000\000\000D\214\= rH"... p =3D 0x0 i =3D 2 len =3D 16 isinstalled =3D 1 new_m =3D 0 dep_count =3D 2 pre_script =3D 0x805005c "+DEINSTALL" post_script =3D 0x0 pre_arg =3D 0x0 post_arg =3D 0x0 rb_entry =3D (struct reqr_by_entry *) 0x8134080 rb_list =3D (struct reqr_by_head *) 0x8052240 __func__ =3D "pkg_do" #3 0x08049f50 in pkg_perform (pkgs=3D0x8113068) at perform.c:112 matched =3D (char **) 0x8112080 rb =3D (char **) 0x4807e000 rbtmp =3D (char **) 0x248 errcode =3D 0 i =3D 0 j =3D 9 err_cnt =3D 0 rb_entry =3D (struct reqr_by_entry *) 0x246 rb_list =3D (struct reqr_by_head *) 0x0 __func__ =3D "pkg_perform" #4 0x08049b93 in real_main (argc=3D1, argv=3D0xbfbfeb98) at main.c:145 ch =3D -1 error =3D 135332000 pkgs =3D (char **) 0xbfbfeb94 start =3D (char **) 0xbfbfeb90 pkgs_split =3D 0x0 tmp =3D 0x804fe53 "/var/db/pkg" stat_s =3D {st_dev =3D 101, st_ino =3D 16097, st_mode =3D 16877, st_nlink = =3D 700, st_uid =3D 0, st_gid =3D 0, st_rdev =3D 66136, st_atimespec =3D {t= v_sec =3D 1213102114,=20 tv_nsec =3D 0}, st_mtimespec =3D {tv_sec =3D 1213043376, tv_nsec =3D 0}= , st_ctimespec =3D {tv_sec =3D 1213043376, tv_nsec =3D 0}, st_size =3D 2764= 8, st_blocks =3D 56,=20 st_blksize =3D 4096, st_flags =3D 0, st_gen =3D 4026593762, st_lspare =3D= 0, st_birthtimespec =3D {tv_sec =3D 1131005361, tv_nsec =3D 0}} #5 0x0804b0d5 in main (argc=3D2, argv=3D0xbfbfeb90) at pkgwrap.c:88 f =3D (FILE *) 0x0 buffer =3D " =DA\aH", '\0' , "kU\005H=C4=F4\nH=C4=F4\nH"= , '\0' , "=E4(\aH\200\235\nH\000\000\000\000\000\000\000\= 000\002\000\002\000;S\005Hp=F2\aHx=E8=BF=BF\024=E8=BF=BF\223W\005H\236=F4\n= H=FC\234=B0\006\000=E4\aH `\bH\001\000\000\000\000\000\000\000=E4(\aH\234#\= 005H\000\000\000\000\000\000\000\000\000=E4\aH4q\aH\000\000\000\000 =FE\tH\= 224=E8=BF=BF=D7Y\005H\236=F4\nH=FC\234=B0\006=E0t\aH `\bH\001\000\000\000\0= 00=E0\aH\000=E2\aH\000=E4\aH `\bH\000\000\000\000\000\000\000\000=E4(\aHG= =B7=A1\n=DC=DC\nH\000\235\nH"... cp =3D 0xbfbfeb68 "\210=EB=BF=BF\223\230\004\b\002" verstr =3D 0x4814a252 "=C9=C3S\213D$\b\212L$\f\220\212\0308=D9t\a@\204=DBu= =F51=C0[=C3\220\220\220U\211=E5V\211=C6\017=BE" len =3D 608 (gdb) The program is running. Exit anyway? (y or n)=20 Oh and here is the content of /var/db/pkg/linux-tiff-3.7.1: total 40 -rw-r--r-- 1 root wheel 32 Mar 17 2007 +COMMENT -rw-r--r-- 1 root wheel 4098 Jun 8 14:21 +CONTENTS -rw-r--r-- 1 root wheel 229 Mar 17 2007 +DESC drwxr-xr-x 2 root wheel 512 Jun 9 11:05 . drwxr-xr-x 700 root wheel 27648 Jun 9 22:29 .. --J/dobhs11T7y2rNN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkhOgQUACgkQBLVThWGOYx7vbQCgsPkreD+OzwVT5JTT+MkchxI5 sFMAni3WrijWyEPHFCnsLre60idcbKnL =LcIh -----END PGP SIGNATURE----- --J/dobhs11T7y2rNN-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 13:48:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED91A1065690 for ; Tue, 10 Jun 2008 13:48:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id E2B828FC30 for ; Tue, 10 Jun 2008 13:48:40 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 4B6C11CC038; Tue, 10 Jun 2008 06:48:40 -0700 (PDT) Date: Tue, 10 Jun 2008 06:48:40 -0700 From: Jeremy Chadwick To: Jona Joachim Message-ID: <20080610134840.GA44581@eos.sc1.parodius.com> References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> <484DD565.2010700@FreeBSD.org> <20080610120240.GA2964@nirvana.my.domain> <20080610124245.GA42745@eos.sc1.parodius.com> <20080610132629.GA15963@nirvana.my.domain> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080610132629.GA15963@nirvana.my.domain> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 13:48:41 -0000 On Tue, Jun 10, 2008 at 03:26:30PM +0200, Jona Joachim wrote: > On Tue, Jun 10, 2008 at 05:42:45AM -0700, Jeremy Chadwick wrote: > > On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote: > > > On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote: > > > > Jona Joachim wrote: > > > > > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > > > > >> Jona Joachim wrote: > > > > >>> Hi! > > > > >>> > > > > >>> pkg_delete core dumps on me when it tries to remove linux-tiff. > > > > >>> I can reproduce this reliably. > > > > >>> FWIW you can find the core dump here: > > > > >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core > > > > >> You need to obtain the backtrace, see the developers handbook. > > > > > > > > > > I built pkg_delete with -g but gdb says 'no debugging symbols found'. > > > > > Is the following information sufficient or do I need to rebuild everything with debugging information turned on? > > > > > > > > It was probably stripped at install, I think you can set STRIP= (i.e. > > > > empty value) but doesn't it also explain this in the handbook? > > > > (snip bt) > > > > How about 'bt full' ? > > Here you go. > > linux-tiff depends on graphics/linux-jpeg, which isn't installed however. > Something must have gone wrong there, I didn't pkg_delete -f linux-jpeg. Thanks. A couple things: 1) Can you perform the same pkg_delete but with the -v flag? This should cause quite a bit more output, but will help track this down. 2) Output from cat /var/db/pkg/linux-tiff-3.7.1/+CONTENTS 3) Can you put the below files up someplace on the web, preferrably in a tarball? I'd ask for them, but the mailing list strips attachments. I'm wondering if there's some binary data in one of the files (e.g. interested in why +CONTENTS has a newer mtime than +COMMENT and +DESC). Have you had any filesystem problems as of late? dmesg -a show any filesystem issues or disk issues? > Oh and here is the content of /var/db/pkg/linux-tiff-3.7.1: > > total 40 > -rw-r--r-- 1 root wheel 32 Mar 17 2007 +COMMENT > -rw-r--r-- 1 root wheel 4098 Jun 8 14:21 +CONTENTS > -rw-r--r-- 1 root wheel 229 Mar 17 2007 +DESC > drwxr-xr-x 2 root wheel 512 Jun 9 11:05 . > drwxr-xr-x 700 root wheel 27648 Jun 9 22:29 .. The code in usr.sbin/pkg_install/lib/plist.c which is causing the segfault: 462 if (p->next && p->next->type == PLIST_COMMENT && !strncmp(p->next->name, "MD5:", 4)) { 4) What date are your system sources (specifically src/usr.sbin/pkg_install)? The reason I ask is that there were some recent speed optimisations applied to the pkg_* tools, and I'm curious what "version" of the sources you have. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 15:10:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B430B1065677; Tue, 10 Jun 2008 15:10:37 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from 0b10111.de (hcl-club.lu [62.75.155.129]) by mx1.freebsd.org (Postfix) with ESMTP id 4F8228FC13; Tue, 10 Jun 2008 15:10:37 +0000 (UTC) (envelope-from jaj@hcl-club.lu) Received: from nirvana.my.domain (4be54-4-82-234-154-189.fbx.proxad.net [82.234.154.189]) by 0b10111.de (Postfix) with ESMTPS id 16FEBBFB0032; Tue, 10 Jun 2008 15:10:36 +0000 (UTC) Received: by nirvana.my.domain (Postfix, from userid 1000) id C18A27DD1; Tue, 10 Jun 2008 17:10:34 +0200 (CEST) Date: Tue, 10 Jun 2008 17:10:34 +0200 From: Jona Joachim To: Jeremy Chadwick Message-ID: <20080610151033.GA1415@nirvana.my.domain> References: <484BE563.90102@FreeBSD.org> <20080610003222.GA3822@nirvana.my.domain> <484DD565.2010700@FreeBSD.org> <20080610120240.GA2964@nirvana.my.domain> <20080610124245.GA42745@eos.sc1.parodius.com> <20080610132629.GA15963@nirvana.my.domain> <20080610134840.GA44581@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080610134840.GA44581@eos.sc1.parodius.com> X-PGP-Key: http://www.hcl-club.lu/~jaj/pubkey.asc User-Agent: Mutt/1.5.18 (2008-05-17) Cc: freebsd-stable@freebsd.org Subject: Re: pkg_delete core dump when removing linux-tiff 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, 10 Jun 2008 15:10:37 -0000 On Tue, Jun 10, 2008 at 06:48:40AM -0700, Jeremy Chadwick wrote: > On Tue, Jun 10, 2008 at 03:26:30PM +0200, Jona Joachim wrote: > > On Tue, Jun 10, 2008 at 05:42:45AM -0700, Jeremy Chadwick wrote: > > > On Tue, Jun 10, 2008 at 02:02:40PM +0200, Jona Joachim wrote: > > > > On Tue, Jun 10, 2008 at 03:14:13AM +0200, Kris Kennaway wrote: > > > > > Jona Joachim wrote: > > > > > > On Sun, Jun 08, 2008 at 03:57:55PM +0200, Kris Kennaway wrote: > > > > > >> Jona Joachim wrote: > > > > > >>> Hi! > > > > > >>> > > > > > >>> pkg_delete core dumps on me when it tries to remove linux-tiff. > > > > > >>> I can reproduce this reliably. > > > > > >>> FWIW you can find the core dump here: > > > > > >>> http://www.hcl-club.lu/~jaj/stuff/pkg_delete.core > > > > > >> You need to obtain the backtrace, see the developers handbook. > > > > > > > > > > > > I built pkg_delete with -g but gdb says 'no debugging symbols found'. > > > > > > Is the following information sufficient or do I need to rebuild everything with debugging information turned on? > > > > > > > > > > It was probably stripped at install, I think you can set STRIP= (i.e. > > > > > empty value) but doesn't it also explain this in the handbook? > > > > > > (snip bt) > > > > > > How about 'bt full' ? > > > > Here you go. > > > > linux-tiff depends on graphics/linux-jpeg, which isn't installed however. > > Something must have gone wrong there, I didn't pkg_delete -f linux-jpeg. > > Thanks. A couple things: > > 1) Can you perform the same pkg_delete but with the -v flag? This > should cause quite a bit more output, but will help track this down. > > 2) Output from cat /var/db/pkg/linux-tiff-3.7.1/+CONTENTS > > 3) Can you put the below files up someplace on the web, preferrably in a > tarball? I'd ask for them, but the mailing list strips attachments. > I'm wondering if there's some binary data in one of the files (e.g. > interested in why +CONTENTS has a newer mtime than +COMMENT and +DESC). You can find it all in there: http://www.hcl-club.lu/~jaj/stuff/pkg_delete-segv.tar.gz > Have you had any filesystem problems as of late? dmesg -a show any > filesystem issues or disk issues? No, I didn't have any disk issues I'm aware of. dmesg -a doesn't show anything suspect. > > Oh and here is the content of /var/db/pkg/linux-tiff-3.7.1: > > > > total 40 > > -rw-r--r-- 1 root wheel 32 Mar 17 2007 +COMMENT > > -rw-r--r-- 1 root wheel 4098 Jun 8 14:21 +CONTENTS > > -rw-r--r-- 1 root wheel 229 Mar 17 2007 +DESC > > drwxr-xr-x 2 root wheel 512 Jun 9 11:05 . > > drwxr-xr-x 700 root wheel 27648 Jun 9 22:29 .. > > The code in usr.sbin/pkg_install/lib/plist.c which is causing the > segfault: > > 462 if (p->next && p->next->type == PLIST_COMMENT && !strncmp(p->next->name, "MD5:", 4)) { The last line of +CONTENTS has an @comment line with no MD5 following. On Jun 8 (timestamp of +CONTENTS) I was doing a portupgrade -a. > 4) What date are your system sources (specifically > src/usr.sbin/pkg_install)? The reason I ask is that there were some > recent speed optimisations applied to the pkg_* tools, and I'm curious > what "version" of the sources you have. My sources are pretty much up to date. I have the latest changes flz@ checked in one week ago into pkg_install. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 16:51:53 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C7741065674 for ; Tue, 10 Jun 2008 16:51:53 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by mx1.freebsd.org (Postfix) with ESMTP id 687CA8FC1E for ; Tue, 10 Jun 2008 16:51:53 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2025358wah.3 for ; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=mLVLbQP6D6fy4mLaKkct/rs4Y/3KA2takR6zpJO4U/Y=; b=BpPzdv3n6kFRkPmljXGKmoJ/XnlAtgF/kXKhutu9UOeZ5+p+Tmlt1VpgmMX8MM19aP 8cgmVD1xoHgaJOUzTqO0HA1dzBeUvWzuABcXDgZfFbwfn+m1CKV0VHvtR1v+CMrx7G+w tS0OqkPoS0tSm72KRZnbKLdy1fdoqtgCkD24w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=AqW9yynGCP05ps9t2XQKLoxDCRmsFLIiH++tM6sBxyBaRzdHQ6MgsRyFuVBTUq8BN2 B1AYIHDoM2hSTaXaY1oD6oIfQfaSpa7l4qn/q9Q9BUaZW83Na2idldpL/4H46OZNUgB9 7gYCOFbJFDDg8fqVFqTDnk7UhuIveHsDEYoAw= Received: by 10.115.47.1 with SMTP id z1mr5211645waj.129.1213116713062; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Tue, 10 Jun 2008 09:51:53 -0700 (PDT) Message-ID: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Date: Tue, 10 Jun 2008 09:51:53 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Current" , "FreeBSD Stable List" , "Sam Leffler" MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: Subject: Vlan EVENT patch 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, 10 Jun 2008 16:51:53 -0000 This is a small patch that Sam came up with for me, it will allow drivers to know when a vlan attaches. It is transparent to any code that doesn't want to change, but this will allow my drivers to finally utilize the vlan hardware filter (something Linux has had for ever but we lacked). My test group has done some basic testing of this and it is working great. But we wanted to give any vlan users a chance to see, ask questions, or whatever before its committed. Jack From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:17:27 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 999961065678 for ; Tue, 10 Jun 2008 17:17:27 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 66E3F8FC16 for ; Tue, 10 Jun 2008 17:17:27 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m5AHHOjn008584; Tue, 10 Jun 2008 12:17:24 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Tue, 10 Jun 2008 12:17:24 -0500 (CDT) From: "Sean C. Farley" To: Timo Sirainen In-Reply-To: <1213071257.3904.991.camel@hurina> Message-ID: References: <1213036854.3904.967.camel@hurina> <1213071257.3904.991.camel@hurina> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail.farley.org Cc: freebsd-stable@FreeBSD.org Subject: Re: Environment clearing broken in 7.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, 10 Jun 2008 17:17:27 -0000 On Tue, 10 Jun 2008, Timo Sirainen wrote: > On Mon, 2008-06-09 at 22:27 -0500, Sean C. Farley wrote: >> On Mon, 9 Jun 2008, Timo Sirainen wrote: >> >>> I think clearing environment using: >>> >>> environ[0] = NULL; >>> >>> has been kind of a semi-standard for a while now. At least Dovecot >>> and Postfix clears their environment this way. But this no longer >>> works in FreeBSD 7.0 (putenv(), environ[0]=NULL, putenv() -> >>> everything is visible again). Was this change intended, or will this >>> be fixed? >> >> It is more or less intended. When a program sets an environment >> variable, the environment is copied for faster/leaner usage. >> Changing individual values within environ is not checked else every >> pointer would need to be checked for consistency. What I did was to >> write the code to detect if environ is replaced (NULL or new array of >> variables). > > OK, so perhaps Sendmail's way of clearing environment would be the > best solution: > > static char *emptyenv[1] = { NULL }; > environ = emptyenv; That works too. >> I suggest reading the two paragraphs from Open Group's getenv()[1] >> documentation starting at "Conforming applications are required not >> to modify environ directly, ..." for the rationale in the new design. >> Obviously, applications are not required to conform, but the >> documentation talks about what an OS may be doing under the covers to >> environ. > > How about implementing clearenv()? I'm using it now if it's available. It is a thought. It is not part of SUSv3, but there are many API calls in our libc that are not part of that spec. Interestingly, clearenv() on Linux ends up setting environ=NULL. Also, from the Linux man page: The DG/UX and Tru64 manpages write: If environ has been modified by anything other than the putenv(), getenv(), or clearenv() functions, then clearenv() will return an error and the process environment will remain unchanged. Hopefully, no libraries on these systems are manipulating environ else clearenv() will not work. >> Out of curiosity, do Dovecot and Postfix check that environ is not >> NULL before setting environ[0]? environ may be set to NULL at the >> start but not by FreeBSD's /usr/bin/env -i. > > Yes, both check if it's NULL. (I think I originally copied my code's > logic from Postfix.) Good. I asked because I could see myself making that mistake awhile back before I truly understood how environ interacted with applications from start (exec()) to finish. >>> Looks like I could work around this by using: >>> >>> environ = NULL; >> >> That will work on the *BSD's, OpenSolaris and Linux. > > But not on OS X. It crashes there. Grrrr. >> Also, this will work: >> environ = calloc(1, sizeof(*environ)); > > Is this any better than using a static emptyenv[1]? Not exactly but see below about Haiku as an example. > BTW. I wonder if this change breaks any applications where not > clearing environment could result in a security hole. As far as I know > FreeBSD 7.0 is the only modern OS where environ[0]=NULL doesn't work. OpenSolaris also does not detect environ[0]=NULL. Haiku[1], like MacOS, does not handle environ=NULL. *sigh* To support the most OS's I recommend the environ replacement such as in the static environ above. IMHO, mixing direct usage of the internals of environ and calling *env() is not safe. I really wish that environ could not be touched directly by any application. To be safe with all implementations of environ, I recommend using a method that replaces environ with a NULL terminated array such as you have with emptyenv. This will work on all platforms. Oops! Actually, it may break on Haiku since it will realloc() environ if it has copied environ previously with a call to putenv(), setenv() or unsetenv(). No guarantees, but I will do some research about detecting a NULL at environ[0] as another means of clearing the environment and/or writing an implementation of clearenv(). Of course, you will still have problems on OpenSolaris. What are you planning to do there, or does it support cleanenv()? Does anyone know why clearenv() was rejected? There is hardly a peep on the OpenGroup web site. To consolidate the notes: environ = NULL does not work on: 1. MacOS/Darwin 2. Haiku environ[0] = NULL does not work on: 1. FreeBSD 7+ 2. OpenSolaris static char *emptyenv[1] = { NULL }; environ = emptyenv; does not work on: 1. Haiku 2. MacOS? environ = calloc(1, sizeof(*environ)); should work on all assuming NULL was not returned. cleanenv() works on all systems that support it with caveats concerning: 1. DG/UX and Tru64 Sean 1. http://dev.haiku-os.org/browser/haiku/trunk/src/system/libroot/posix/stdlib/env.c -- scf@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:20:56 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADD11106568D; Tue, 10 Jun 2008 17:20:56 +0000 (UTC) (envelope-from jimpc@geihoma.demon.co.uk) Received: from geihoma.demon.co.uk (geihoma.demon.co.uk [80.177.124.198]) by mx1.freebsd.org (Postfix) with ESMTP id 2955E8FC19; Tue, 10 Jun 2008 17:20:55 +0000 (UTC) (envelope-from jimpc@geihoma.demon.co.uk) Received: from geihoma.demon.co.uk (localhost [127.0.0.1]) by geihoma.demon.co.uk (8.14.2/8.13.8) with ESMTP id m5AGjo8K001064; Tue, 10 Jun 2008 17:45:50 +0100 (BST) (envelope-from jimpc@geihoma.demon.co.uk) Received: (from jimpc@localhost) by geihoma.demon.co.uk (8.14.2/8.13.8/Submit) id m5AGjohs001063; Tue, 10 Jun 2008 17:45:50 +0100 (BST) (envelope-from jimpc) Date: Tue, 10 Jun 2008 17:45:27 +0100 From: Jim McGuire To: freebsd-stable@freebsd.org Message-ID: <20080610164527.GA1008@geihoma.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.2i Cc: freebsd-current@freebsd.org Subject: pkg-config 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, 10 Jun 2008 17:20:56 -0000 yesterday, as a newbie in his dotage, i was trying to get packages, re cups, under freebsd 7.0... got the message that pkg-config later than 0.22, which is available in packages, was needed... please advise of any workaround.... but should not packages be internally consistent? From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:26:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 39F841065677 for ; Tue, 10 Jun 2008 17:26:49 +0000 (UTC) (envelope-from nakal@web.de) Received: from fmmailgate01.web.de (fmmailgate01.web.de [217.72.192.221]) by mx1.freebsd.org (Postfix) with ESMTP id F02268FC20 for ; Tue, 10 Jun 2008 17:26:48 +0000 (UTC) (envelope-from nakal@web.de) Received: from smtp08.web.de (fmsmtp08.dlan.cinetic.de [172.20.5.216]) by fmmailgate01.web.de (Postfix) with ESMTP id AFED4E38838E; Tue, 10 Jun 2008 18:55:25 +0200 (CEST) Received: from [217.236.54.228] (helo=zelda.local) by smtp08.web.de with asmtp (TLSv1:AES256-SHA:256) (WEB.DE 4.109 #226) id 1K6781-0000sg-00; Tue, 10 Jun 2008 18:55:25 +0200 Date: Tue, 10 Jun 2008 18:55:21 +0200 From: Martin To: Greg Black Message-ID: <20080610185521.1560974b@zelda.local> In-Reply-To: References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> <484E2CD7.3070201@zircon.seattle.wa.us> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.10; amd64-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: nakal@web.de X-Sender: nakal@web.de X-Provags-ID: V01U2FsdGVkX1+shqqpqq5tayfnMe7GkeO92YjLKJ/459bGA7Td DLgmTOM6AWoavcA7YngQsVtqXJu2ixqghiT/byCQ6AWZGIUbNg uaZ2LcQ14= Cc: Jerahmy Pocott , freebsd-stable@freebsd.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 17:26:49 -0000 Am Tue, 10 Jun 2008 18:03:21 +1000 schrieb Greg Black : > Just for the record, I've been using burncd successfully with a > variety of drives from the early days of FreeBSD through to at least > 7.0-R, so I doubt if the above means very much. Hi. I have 2 drives here that don't work properly. Burning CDs/DVDs is quite broken on both of them. First drive (LG HL-DT-ST DVDRAM GSA-4167B DL13): I can burn a CD with 5x as maximal speed. cdrecord reports something about DMA not working as expected. A can be burnt, too, but also very slow. Most drives have difficulties to read a DVD burnt with this drive. One workaround would be to enable burnfree, but this results in the DVD being unreadable. I have severe problems playing DVD movies (originals!). Even trying to insert such a DVD results in extreme slow system, load going up through the ceiling so that my mouse cursor does not move anymore. Forcing an eject will crash the whole system. Second drive is the one in my Thinkpad T60p: I can burn CDs. Also only very slowly. I can burn DVDs but they will be unreadable everywhere. Systems are: FreeBSD-7-STABLE i386 and amd64. I had problems with CD/DVD burning since 5.2 AFAIR somewhere in RC phase. I reported them and till now waiting patiently for corrections ;) New is that playing movies can make your system unusable. I just wanted to say "Me too!". -- Thanks, Martin From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:28:05 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7EAF1065676 for ; Tue, 10 Jun 2008 17:28:05 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 7545F8FC15 for ; Tue, 10 Jun 2008 17:28:05 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m5AHS2wN008791; Tue, 10 Jun 2008 12:28:02 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Tue, 10 Jun 2008 12:28:02 -0500 (CDT) From: "Sean C. Farley" To: Jerahmy Pocott In-Reply-To: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> Message-ID: References: <36421019-B667-42FD-8069-98B7BFFED920@optusnet.com.au> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail.farley.org Cc: freebsd-stable@FreeBSD.org Subject: Re: DVD-RW doesn't write 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, 10 Jun 2008 17:28:05 -0000 On Tue, 10 Jun 2008, Jerahmy Pocott wrote: *snip* > The drive is able to mount and read cds/dvds fine, but on trying to > use burncd it says: > acd0: FAILURE - READ_TRACK_INFO ILLEGAL REQUEST asc=0x24 ascq=0x00 > > Any further attempts produce the above message with no delay to read > from the drive, resetting the ata0 channel makes it check the drive > again before producing the message. > > On loading atapicam module it says: > acd0: FAILURE - INQUIRY ILLEGAL REQUEST asc=0x24 ascq=0x00 > > So I wasn't able to try cdrecord with it.. I had problems with burncd and my DVD drive when burning CD-RW's. When I tried atapicam and cdrecord, it gave me problems. I believe it was using burncd prior to atapicam that caused it because it works now if I do not use burncd first. You could try a reboot and use atapicam first; the DVD drive may be in a funny state. Just a guess. Sean -- scf@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:30:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B6BB106568C for ; Tue, 10 Jun 2008 17:30:37 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.179]) by mx1.freebsd.org (Postfix) with ESMTP id B72C38FC26 for ; Tue, 10 Jun 2008 17:30:36 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1279935pyb.10 for ; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type:references; bh=41PC+Mdi7jkKb4JeclWr1DnNU6tg5wr5HbAVnyv4AZc=; b=DGX7P4oSZr9QXUdLcn9R8G5sWF8xLvGmqvVeq6tkCQ58JBVGZHhk/A8UpatIh+mFDm N835sWG6fJdixr9Uytxz4SqZapnDAeJzf9YVv0eGVzTdezzvn/FPFMR5d+QkKNgXkhXB uWspvVn54C+BhmM7E6kzjjT5hztgwU/K/kb0Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:references; b=q+GY2PopnJORYeqzEq0ZJKcOxWGo8d7L9zVc8R9Q/Tl7xOvHYB3acO9XZsemJMjN3F rZBCKxRkivgYuOZohq9wtjzhxMXNQQQYVmE58UUiLy3H/p7cakehOOL0ZNdtA+fKa2FA LsPEcku5nOXiNA2BJVi4zeM96dQAlLEzWQXiQ= Received: by 10.114.92.2 with SMTP id p2mr5244201wab.223.1213119035228; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Tue, 10 Jun 2008 10:30:35 -0700 (PDT) Message-ID: <2a41acea0806101030xa9f0689k663709a4595b1771@mail.gmail.com> Date: Tue, 10 Jun 2008 10:30:35 -0700 From: "Jack Vogel" To: "freebsd-net@freebsd.org" , "FreeBSD Current" , "FreeBSD Stable List" , "Sam Leffler" In-Reply-To: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_32711_23637119.1213119035234" References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Cc: Subject: Re: Vlan EVENT patch 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, 10 Jun 2008 17:30:37 -0000 ------=_Part_32711_23637119.1213119035234 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/10/08, Jack Vogel wrote: > This is a small patch that Sam came up with for me, it will allow > drivers to know > when a vlan attaches. > > It is transparent to any code that doesn't want to change, but this > will allow my > drivers to finally utilize the vlan hardware filter (something Linux has had > for > ever but we lacked). > > My test group has done some basic testing of this and it is working great. > But we wanted to give any vlan users a chance to see, ask questions, or > whatever before its committed. > > Jack > Sigh, sorry, here's the actual patch :) Jack ------=_Part_32711_23637119.1213119035234 Content-Type: text/x-patch; name=vlan.patch Content-Transfer-Encoding: base64 X-Attachment-Id: file0 Content-Disposition: attachment; filename=vlan.patch LS0tIGlmX3ZsYW4uZGlzdC5jCTIwMDgtMDYtMDQgMDk6MzU6MDUuMDAwMDAwMDAwIC0wNzAwCisr KyBpZl92bGFuLmMJMjAwOC0wNi0wNSAxNDo0ODowNC4wMDAwMDAwMDAgLTA3MDAKQEAgLTEwNjIs NiArMTA2Miw4IEBACiAJaWZwLT5pZl9kcnZfZmxhZ3MgfD0gSUZGX0RSVl9SVU5OSU5HOwogZG9u ZToKIAlUUlVOS19VTkxPQ0sodHJ1bmspOworCWlmIChlcnJvciA9PSAwKQorCQlFVkVOVEhBTkRM RVJfSU5WT0tFKHZsYW5fY29uZmlnLCBwLCBpZnYtPmlmdl90YWcpOwogCVZMQU5fVU5MT0NLKCk7 CiAKIAlyZXR1cm4gKGVycm9yKTsKQEAgLTEwODQsMTIgKzEwODYsMTQgQEAKIAlzdHJ1Y3QgaWZ2 bGFudHJ1bmsgKnRydW5rOwogCXN0cnVjdCB2bGFuX21jX2VudHJ5ICptYzsKIAlzdHJ1Y3QgaWZ2 bGFuICppZnY7CisJc3RydWN0IGlmbmV0ICAqcGFyZW50OwogCWludCBlcnJvcjsKIAogCVZMQU5f TE9DS19BU1NFUlQoKTsKIAogCWlmdiA9IGlmcC0+aWZfc29mdGM7CiAJdHJ1bmsgPSBpZnYtPmlm dl90cnVuazsKKwlwYXJlbnQgPSBQQVJFTlQoaWZ2KTsKIAogCWlmICh0cnVuaykgewogCQlzdHJ1 Y3Qgc29ja2FkZHJfZGwgc2RsOwpAQCAtMTE1Myw2ICsxMTU3LDggQEAKIAlpZnAtPmlmX2xpbmtf c3RhdGUgPSBMSU5LX1NUQVRFX1VOS05PV047CiAJaWZwLT5pZl9kcnZfZmxhZ3MgJj0gfklGRl9E UlZfUlVOTklORzsKIAorCUVWRU5USEFORExFUl9JTlZPS0Uodmxhbl91bmNvbmZpZywgcGFyZW50 LCBpZnYtPmlmdl90YWcpOworCiAJcmV0dXJuICgwKTsKIH0KIAotLS0gZXZlbnRoYW5kbGVyLmRp c3QuaAkyMDA4LTA2LTA1IDA5OjI0OjE2LjAwMDAwMDAwMCAtMDcwMAorKysgZXZlbnRoYW5kbGVy LmgJMjAwOC0wNi0wNSAwOToyNzozNi4wMDAwMDAwMDAgLTA3MDAKQEAgLTE3NSw2ICsxNzUsMTMg QEAKIHR5cGVkZWYgdm9pZCAoKm1vdW50cm9vdF9oYW5kbGVyX3QpKHZvaWQgKik7CiBFVkVOVEhB TkRMRVJfREVDTEFSRShtb3VudHJvb3QsIG1vdW50cm9vdF9oYW5kbGVyX3QpOwogCisvKiBWTEFO IHN0YXRlIGNoYW5nZSBldmVudHMgKi8KK3N0cnVjdCBpZm5ldDsKK3R5cGVkZWYgdm9pZCAoKnZs YW5fY29uZmlnX2ZuKSh2b2lkICosIHN0cnVjdCBpZm5ldCAqLCB1aW50MTZfdCk7Cit0eXBlZGVm IHZvaWQgKCp2bGFuX3VuY29uZmlnX2ZuKSh2b2lkICosIHN0cnVjdCBpZm5ldCAqLCB1aW50MTZf dCk7CitFVkVOVEhBTkRMRVJfREVDTEFSRSh2bGFuX2NvbmZpZywgdmxhbl9jb25maWdfZm4pOwor RVZFTlRIQU5ETEVSX0RFQ0xBUkUodmxhbl91bmNvbmZpZywgdmxhbl91bmNvbmZpZ19mbik7CisK IC8qCiAgKiBQcm9jZXNzIGV2ZW50cwogICogcHJvY2Vzc19mb3JrIGFuZCBleGl0IGhhbmRsZXJz IGFyZSBjYWxsZWQgd2l0aG91dCBHaWFudC4K ------=_Part_32711_23637119.1213119035234-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 17:37:07 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EC753106566B; Tue, 10 Jun 2008 17:37:07 +0000 (UTC) (envelope-from tss@iki.fi) Received: from dovecot.org (dovecot.org [82.118.211.50]) by mx1.freebsd.org (Postfix) with ESMTP id 7F1678FC27; Tue, 10 Jun 2008 17:37:07 +0000 (UTC) (envelope-from tss@iki.fi) Received: from [192.168.10.2] (xdsl-177-118.nblnetworks.fi [217.30.177.118]) by dovecot.org (Postfix) with ESMTP id 1AC56FA8B09; Tue, 10 Jun 2008 20:36:36 +0300 (EEST) From: Timo Sirainen To: "Sean C. Farley" In-Reply-To: References: <1213036854.3904.967.camel@hurina> <1213071257.3904.991.camel@hurina> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-0POc766UTTBQl/zWvWFI" Date: Tue, 10 Jun 2008 20:36:35 +0300 Message-Id: <1213119395.3904.1047.camel@hurina> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1 Cc: freebsd-stable@FreeBSD.org Subject: Re: Environment clearing broken in 7.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, 10 Jun 2008 17:37:08 -0000 --=-0POc766UTTBQl/zWvWFI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-06-10 at 12:17 -0500, Sean C. Farley wrote: > >> I suggest reading the two paragraphs from Open Group's getenv()[1] > >> documentation starting at "Conforming applications are required not > >> to modify environ directly, ..." for the rationale in the new design. > >> Obviously, applications are not required to conform, but the > >> documentation talks about what an OS may be doing under the covers to > >> environ. > > > > How about implementing clearenv()? I'm using it now if it's available. >=20 > It is a thought. It is not part of SUSv3, but there are many API calls > in our libc that are not part of that spec. >=20 > Interestingly, clearenv() on Linux ends up setting environ=3DNULL. Also, > from the Linux man page: >=20 > The DG/UX and Tru64 manpages write: If environ has been modified by > anything other than the putenv(), getenv(), or clearenv() functions, > then clearenv() will return an error and the process environment > will remain unchanged. >=20 > Hopefully, no libraries on these systems are manipulating environ else > clearenv() will not work. I don't think there's any other reason to do it than clearing it. > > BTW. I wonder if this change breaks any applications where not > > clearing environment could result in a security hole. As far as I know > > FreeBSD 7.0 is the only modern OS where environ[0]=3DNULL doesn't work. >=20 > OpenSolaris also does not detect environ[0]=3DNULL. Haiku[1], like MacOS= , > does not handle environ=3DNULL. *sigh* To support the most OS's I > recommend the environ replacement such as in the static environ above. Oh. I don't have OpenSolaris installed, but I would have thought that since it worked in Solaris 10 it would have worked in OpenSolaris too. > No guarantees, but I will do some research about detecting a NULL at > environ[0] as another means of clearing the environment and/or writing > an implementation of clearenv(). Of course, you will still have > problems on OpenSolaris. What are you planning to do there, or does it > support cleanenv()? I've changed my code now to do: > environ =3D calloc(1, sizeof(*environ)); should work on all assuming NULL > was not returned. Hopefully that'll work for a few years. (I also use clearenv() if detected by configure.) > Does anyone know why clearenv() was rejected? There is hardly a peep > on > the OpenGroup web site. No idea, but I don't really understand why it returns int instead of void. It shouldn't do more than free memory. --=-0POc766UTTBQl/zWvWFI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBITrujyUhSUUBViskRAih+AKClGqs4h0amcYYHuEI9w0MYj4oFcgCgnlXh haashtxia7QJZIrucgx+zXs= =6rV0 -----END PGP SIGNATURE----- --=-0POc766UTTBQl/zWvWFI-- From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 18:56:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0D4C0106566B for ; Tue, 10 Jun 2008 18:56:26 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from nagual.nl (cc20684-a.assen1.dr.home.nl [82.74.10.158]) by mx1.freebsd.org (Postfix) with ESMTP id 9C8118FC13 for ; Tue, 10 Jun 2008 18:56:25 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from westmark (westmark.nagual.nl [192.168.11.22]) by nagual.nl (8.13.8+Sun/8.13.8/yanta) with ESMTP id m5AIuwm7027851 for ; Tue, 10 Jun 2008 20:56:58 +0200 (CEST) Date: Tue, 10 Jun 2008 20:56:10 +0200 From: Dick Hoogendijk To: freebsd-stable@freebsd.org Message-ID: <20080610205610.00002cbe@westmark> In-Reply-To: <86021481-1BCB-4E16-8DD5-EC14B8597C10@netconsonance.com> References: <484DBBE7.6080908@zircon.seattle.wa.us> <86021481-1BCB-4E16-8DD5-EC14B8597C10@netconsonance.com> Organization: de nagual X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.1; i386-pc-solaris2.11) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.63 on 192.168.11.35 Subject: Re: Closing the Jo Rhett argument 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, 10 Jun 2008 18:56:26 -0000 On Mon, 9 Jun 2008 17:52:24 -0700 Jo Rhett wrote: > The first time mention of BETA and RC cycles came up was in his > reply to me, which was full of personal insults and attacks like the > following, so I discarded it without reply: > > > I see no reason to assume competence on your part since you have > > demonstrated no competence. > ... > > I don't need to assume anything about you. You have demonstrated > > your idiocy to everyone on the list. Please keep your insane > > rants to yourself in the future. If the above quotes are true, the writer should be ashamed of himself. Your POV has stirred some dust ;-) But to call you names is weird. BTW ever meet a sane person? And, did you like it? Whatever my pov on you issues are I don't think people should start insulting one another. -- Dick Hoogendijk -- PGP/GnuPG key: 01D2433D ++ http://nagual.nl/ + SunOS sxde 01/08 ++ From owner-freebsd-stable@FreeBSD.ORG Tue Jun 10 19:51:59 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B1C8C1065673 for ; Tue, 10 Jun 2008 19:51:59 +0000 (UTC) (envelope-from liste.bsd@gmail.com) Received: from mu-out-0910.google.com (mu-out-0910.google.com [209.85.134.190]) by mx1.freebsd.org (Postfix) with ESMTP id 37B288FC1D for ; Tue, 10 Jun 2008 19:51:58 +0000 (UTC) (envelope-from liste.bsd@gmail.com) Received: by mu-out-0910.google.com with SMTP id i2so1787977mue.3 for ; Tue, 10 Jun 2008 12:51:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:mime-version:in-reply-to :references:content-type:message-id:content-transfer-encoding:from :subject:date:to:x-mailer; bh=w5nZEUaTXqaIQDkw7AAa2w68qSNRJz4bavzgACGN5+g=; b=N0vOMtwRSAsdJn8ozSUCkhE4/iGuTU4BhknKRmsVxCiDte+n93lEeThN/eyZOnzAkm //OF0+DyTaQjce1+2cD4deVpCFZRea6bECy3D24ekGYkCGsVBXP7WH3iFr8H6roCXafN Q8ACE8jDoj/4fXngVQcv2pd9CrKd3n1LkSSRU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:content-type:message-id :content-transfer-encoding:from:subject:date:to:x-mailer; b=qPz6y1W+Nk7ZsRZTg/+GxSgseqG1xnTdMaFxNGeaOaquIjgpVL3W2e+rl4byjEjZqY o7T0DYULY9aJ5vF6+bKUsOx9MHcO0NyksB0YGP0JlAET/qO0W58X49yYOcBIAWsQL6kZ Mr3EwxQb5KuDSC7zkKL2AJ6d0ySK5eupHrFaE= Received: by 10.103.170.6 with SMTP id x6mr3627857muo.42.1213125964258; Tue, 10 Jun 2008 12:26:04 -0700 (PDT) Received: from ?192.168.0.10? ( [82.51.126.129]) by mx.google.com with ESMTPS id u9sm28325348muf.12.2008.06.10.12.26.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Jun 2008 12:26:03 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v753.1) In-Reply-To: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Daniele Bastianini Date: Tue, 10 Jun 2008 21:26:44 +0200 To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.753.1) Subject: Re: broken re(4) 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, 10 Jun 2008 19:51:59 -0000 Il giorno 27/mag/08, alle ore 16:52, Gerrit K=FChn ha scritto: > Hi folks, > > I have four identical ITX boards from Jetway here, each having two =20 > re(4) > onboard nics: > > re0@pci0:0:9:0: class=3D0x020000 card=3D0x10ec16f3 chip=3D0x816710ec =20= > rev=3D0x10 > hdr=3D0x00 vendor =3D 'Realtek Semiconductor' > device =3D 'RTL8169/8110 Family Gigabit Ethernet NIC' > class =3D network > subclass =3D ethernet > re1@pci0:0:11:0: class=3D0x020000 card=3D0x10ec16f3 = chip=3D0x816710ec > rev=3D0x10 hdr=3D0x00 vendor =3D 'Realtek Semiconductor' > device =3D 'RTL8169/8110 Family Gigabit Ethernet NIC' > class =3D network > subclass =3D ethernet > atapci0@pci0:0:15:0: class=3D0x01018f card=3D0x31491106 = chip=3D0x31491106 > rev=3D0x80 > > > I run FreeBSD 7-stable from early March 08 on three of these > machines and noticed no problems with networking with that so far. > Some days ago I installed a fourth machine with 7-stable from early =20= > May > (and some days later -because of the problems described below- to May > 17th). With this new machine I see several networking problems. The =20= > most > prominent are these two: > > - heavy networking traffic (in this case backup via tar & NFS) =20 > causes hangs > for about 10s-30s and sometimes also leads to watchdog timeouts: > May 27 09:04:07 protoserve kernel: re0: watchdog timeout > May 27 09:04:07 protoserve kernel: re0: link state changed to DOWN > May 27 09:04:10 protoserve kernel: re0: link state changed to UP > > - copying large files (more than some 100MB) via ssh/scp drops the > connection due to "corrupted MAC on input": > Disconnecting: Corrupted MAC on input. > lost connection I had the same problem. I fixed it (for now) making a buildworld with *default date=3D2008.03.01.00.00.00 in my src csup configuration. I'm not so skilled to investigate in the sources but the problem is =20 after this date. Regards Daniele Bastianini= From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 00:27:23 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 541401065673 for ; Wed, 11 Jun 2008 00:27:23 +0000 (UTC) (envelope-from bermejator@hotmail.com) Received: from blu0-omc2-s28.blu0.hotmail.com (blu0-omc2-s28.blu0.hotmail.com [65.55.111.103]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA6C8FC17 for ; Wed, 11 Jun 2008 00:27:23 +0000 (UTC) (envelope-from bermejator@hotmail.com) Received: from BLU118-W21 ([65.55.111.73]) by blu0-omc2-s28.blu0.hotmail.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 10 Jun 2008 17:15:22 -0700 Message-ID: X-Originating-IP: [83.61.11.151] From: Ruben Lara To: Date: Wed, 11 Jun 2008 00:15:22 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 11 Jun 2008 00:15:22.0674 (UTC) FILETIME=[3D572120:01C8CB58] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: /usr/obj/usr/src/tmp/usr/bin/ld: crti.o: No such file 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, 11 Jun 2008 00:27:23 -0000 Hi, While make buildworld to upgrade: BerMeJo% uname -a FreeBSD=0A= BERMEJO-BSD 7.0-RELEASE FreeBSD 7.0-RELEASE #2: Fri Mar 14 20:46:53 CET=0A= 2008 root@BERMEJO-BSD:/usr/obj/usr/src/sys/BERMEJO-BSD i386 Get next error: ..... cc=0A= -fpic -DPIC -O -pipe -march=3Dathlon-mp -I/usr/src/lib/libc/include=0A= -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/i386=0A= -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa=0A= -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -DPOSIX_MISTAKE=0A= -I/usr/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN=0A= -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING=0A= -Wsystem-headers -Wall -Wno-format-y2k -Wno-uninitialized=0A= -Wno-pointer-sign -c crypt_xdr.c -o crypt_xdr.So building static c library building special pic c library building shared library libc.so.7 ranlib libc_pic.a ranlib libc.a /usr/obj/usr/src/tmp/usr/bin/ld: crti.o: No such file: No such file or dire= ct error *** Error code 2 1 error *** Error code 2 1 error BerMeJo%=20 Anybody can help me? Thank you in advance. Rub=E9n Lara BerMeJo _________________________________________________________________ MSN Video.=20 http://video.msn.com/?mkt=3Des-es= From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 01:04:37 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E6151065675 for ; Wed, 11 Jun 2008 01:04:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 6D28F8FC12 for ; Wed, 11 Jun 2008 01:04:37 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3454155rvf.43 for ; Tue, 10 Jun 2008 18:04:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+IDigIehaiNooXOtW2SY/xchblhboDityaomO3CGiTs=; b=Sp1BPHDA9TuaAX5P83UxhcMoWeSyyQN927jhwQbddodqC/uaNHohrBCTkP/2WXMtgL uZvv5C54QHbt8ZFQCVHYQza1mUSnkvT1y1+bGK/saDWPaVIZqnhdHqtnUWzfCqhOp7tx pE+HeGwK5VJHIfNHolUrk9URQYqnkQBXGQ1IA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=gojWahdoNxsMRUguu2SnhbnZfySE5y21u3jh1WL/gN1l4OugY5bc3nqt7ajVRdDbET /usQxyIYgn7vP4CTwlcnUShbJRn/5FZGVw9pShUIt72UR+TaGLP+rT89edMdKygoz1m2 GtXhPJGE48EnDmCAiw004efD4wohWv3OZR5iU= Received: by 10.141.152.8 with SMTP id e8mr3489097rvo.19.1213146277130; Tue, 10 Jun 2008 18:04:37 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b39sm16406787rvf.8.2008.06.10.18.04.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 10 Jun 2008 18:04:36 -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 m5B12NSC003607 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 10:02:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5B12NDh003606; Wed, 11 Jun 2008 10:02:23 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 11 Jun 2008 10:02:23 +0900 From: Pyun YongHyeon To: Daniele Bastianini Message-ID: <20080611010223.GB3529@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: broken re(4) 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: Wed, 11 Jun 2008 01:04:37 -0000 On Tue, Jun 10, 2008 at 09:26:44PM +0200, Daniele Bastianini wrote: > > Il giorno 27/mag/08, alle ore 16:52, Gerrit K?hn ha scritto: > > >Hi folks, > > > >I have four identical ITX boards from Jetway here, each having two > >re(4) > >onboard nics: > > > >re0@pci0:0:9:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec > >rev=0x10 > >hdr=0x00 vendor = 'Realtek Semiconductor' > > device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > >re1@pci0:0:11:0: class=0x020000 card=0x10ec16f3 chip=0x816710ec > >rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' > > device = 'RTL8169/8110 Family Gigabit Ethernet NIC' > > class = network > > subclass = ethernet > >atapci0@pci0:0:15:0: class=0x01018f card=0x31491106 chip=0x31491106 > >rev=0x80 > > > > > >I run FreeBSD 7-stable from early March 08 on three of these > >machines and noticed no problems with networking with that so far. > >Some days ago I installed a fourth machine with 7-stable from early > >May > >(and some days later -because of the problems described below- to May > >17th). With this new machine I see several networking problems. The > >most > >prominent are these two: > > > >- heavy networking traffic (in this case backup via tar & NFS) > >causes hangs > >for about 10s-30s and sometimes also leads to watchdog timeouts: > >May 27 09:04:07 protoserve kernel: re0: watchdog timeout > >May 27 09:04:07 protoserve kernel: re0: link state changed to DOWN > >May 27 09:04:10 protoserve kernel: re0: link state changed to UP > > > >- copying large files (more than some 100MB) via ssh/scp drops the > >connection due to "corrupted MAC on input": > >Disconnecting: Corrupted MAC on input. > >lost connection > > I had the same problem. > I fixed it (for now) making a buildworld with > *default date=2008.03.01.00.00.00 in my src csup configuration. > > I'm not so skilled to investigate in the sources but the problem is > after this date. > I guess you're using RELENG_7. Would you try a WIP in the following URL? http://people.freebsd.org/~yongari/re/re.HEAD.20080610 Please also make sure to post dmesg output related with re(4). -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 03:47:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 410371065682 for ; Wed, 11 Jun 2008 03:47:01 +0000 (UTC) (envelope-from dennis_flynn@yahoo.com) Received: from web54011.mail.re2.yahoo.com (web54011.mail.re2.yahoo.com [206.190.37.185]) by mx1.freebsd.org (Postfix) with SMTP id E0BAD8FC20 for ; Wed, 11 Jun 2008 03:47:00 +0000 (UTC) (envelope-from dennis_flynn@yahoo.com) Received: (qmail 31122 invoked by uid 60001); 11 Jun 2008 03:20:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=GjnIgZgPFTuY6HUKnz0wPXEgSKlJ+BNWLjtoYgfS+EC5erjg+hMMb+lIt2p4nZEAna/2E8RcfNUGaL93j90AQXQ3ak40Xn+dEtn/iOnB5Z1vNVDcRdaWP2AEo5NfBI8mw7FhXqKzUX4lBsxCJ6cbdr8UiyCqTgOLMqPTtissinI=; X-YMail-OSG: prN9pikVM1mFjCXmCV0cvrWKtQoY4hkhU5Gb0uhJLg11uvjptvgXD5zXJ2uGhvEuk4j_drPle2IdVSAHWOXsRBOc7yvfs5ydWjxf1YYQppItnN6Kz17odvWNVA-- Received: from [71.172.52.194] by web54011.mail.re2.yahoo.com via HTTP; Tue, 10 Jun 2008 20:20:19 PDT Date: Tue, 10 Jun 2008 20:20:19 -0700 (PDT) From: Dennis Flynn To: freebsd-stable@freebsd.org MIME-Version: 1.0 Message-ID: <437286.30504.qm@web54011.mail.re2.yahoo.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 7.0 Stable and the CP2101 driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dennis_flynn@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 03:47:01 -0000 I/m new to FreeBSD (but not Unix in general) and I am setting up an embedded server to acquire data from a weather station. The data comes from the weather station console via the USB port on the server. The USB device is a Silicon Labs CP2102 USB to UART Bridge Controller. Apparently this driver has been added to FreeBSD 7.0-STABLE - http://people.freebsd.org/~bmah/relnotes/7-STABLE/relnotes.html. I tried installing the update, e.g. "freebsd-update -r 7.0-STABLE fetch", then "freebsd-update -r 7.0-STABLE upgrade". Seemed to work. But I do not seem to have the device driver loaded when I plug in the USB device. I get the folowwing in the messages log: Jun 10 16:48:02 wx kernel: ugen0: on uhub0 But I don't see a device that I think I should see, like /dev/ttyU0. If I do a "uname -a" I see the following: FreeBSD wx.dennis-flynn.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 That doesn't seem right to me. Shouldn't I see something like 7.0-RELEASE-p1 or 7.0-STABLE? Did I do something wrong in my update to RELEASE? How do I know if I'm running the STABLE kernel with the driver I want? How can I tell if the driver (uslcom) is there and/or loaded? Thanks in advance for all help. -Dennis Dennis Flynn Home Work From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 05:37:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 847C81065677 for ; Wed, 11 Jun 2008 05:37:01 +0000 (UTC) (envelope-from maho.nakata@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.174]) by mx1.freebsd.org (Postfix) with ESMTP id 5EEEA8FC26 for ; Wed, 11 Jun 2008 05:37:01 +0000 (UTC) (envelope-from maho.nakata@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so2795412wfg.7 for ; Tue, 10 Jun 2008 22:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:message-id:to:cc:subject :from:in-reply-to:references:x-mailer:mime-version:content-type :content-transfer-encoding:sender; bh=28bnD+4+LOCOOnkIORDJPYYqEtbQEDiLpnWSGg8GsJw=; b=BhTlRBBMQReMXNRfcWqZ0pVKb33Id/6cPBMWugSGuWyrtuh4k4iOs4Q8WlOb3bk7eJ lmL8hCMNkagOLjbhecRTKxf9KOzBTJybJFKk7GIkp/SaOGOuUthiFDGYoksZW2psd2l2 3D8GQXY5tC79XjochE3gZsApS5N4dX0PJ0mhY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:message-id:to:cc:subject:from:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding:sender; b=U2wicb9RM7r65MwhVb8IHoHDFVtgh56y88Xw8k19zlAYKT8Z2QPjSpYUFZ3LpKPMnC G3S21c71F7SuPvYDHEEo09VdD3sEPyDyfZGbiNtGtO7j2i7/+rOi7bxzjRdG6gbkjzFM AOUBTJuvtaYoPn3B9szb8D5/9F1hRkvJH0vfQ= Received: by 10.143.32.7 with SMTP id k7mr2414232wfj.305.1213162588923; Tue, 10 Jun 2008 22:36:28 -0700 (PDT) Received: from localhost ( [134.160.214.85]) by mx.google.com with ESMTPS id 22sm13590563wfd.19.2008.06.10.22.36.23 (version=SSLv3 cipher=RC4-MD5); Tue, 10 Jun 2008 22:36:26 -0700 (PDT) Date: Wed, 11 Jun 2008 14:35:18 +0900 (JST) Message-Id: <20080611.143518.232910747.chat95@mac.com> To: bazzoola@gmail.com From: Maho NAKATA In-Reply-To: <6601D6DC-AD09-4028-A25A-59899C9A57E4@gmail.com> References: <20080513054223.2CAC95B4B@mail.bitblocks.com> <6601D6DC-AD09-4028-A25A-59899C9A57E4@gmail.com> X-Mailer: Mew version 5.2 on Emacs 22.1 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: Maho NAKATA Cc: maho@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Auto bridge for qemu network 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, 11 Jun 2008 05:37:01 -0000 From: bazzoola Subject: Auto bridge for qemu network [was: kqemu support: not compiled] Date: Thu, 15 May 2008 03:06:25 -0400 > Thanks for updating the port! > > I have few suggestions: > > #cat /etc/rc.conf > [...] > #KQEMU for qemu > kqemu_enable="YES" > > #Bridge for qemu > cloned_interfaces="bridge0" > ifconfig_bridge0="up addm sk0" > autobridge_interfaces="bridge0" > autobridge_bridge0="tap*" > > This should take care of the network connection between qemu virtual > host and the host instead of doing it manually. Assuming that qemu is > using tap and the default "if" on the host is sk0. > > Also, is it possible to update this page, it has some outdated info: > http://people.freebsd.org/~maho/qemu/qemu.html > *It is the 1st answer from google when asked "freebsd qemu" > Thanks and sorry for inconvenience. bazzoola had already asked me to create a wiki. Now I have some time to do so. I created an account long before, but I cannot edit. Of course I've already asked this issue simon@. -- Nakata Maho http://accc.riken.jp/maho/ From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 05:40:22 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AB821065686 for ; Wed, 11 Jun 2008 05:40:22 +0000 (UTC) (envelope-from jcw@highperformance.net) Received: from mx1.highperformance.net (s3.stradamotorsports.com [64.81.163.125]) by mx1.freebsd.org (Postfix) with ESMTP id 5A3F98FC25 for ; Wed, 11 Jun 2008 05:40:22 +0000 (UTC) (envelope-from jcw@highperformance.net) Received: from [192.168.1.16] (w16.stradamotorsports.com [192.168.1.16]) by mx1.highperformance.net (8.13.8/8.13.8) with ESMTP id m5B578gU017877; Tue, 10 Jun 2008 22:07:09 -0700 (PDT) (envelope-from jcw@highperformance.net) Message-ID: <484F5D80.1000803@highperformance.net> Date: Tue, 10 Jun 2008 22:07:12 -0700 From: "Jason C. Wells" User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: dennis_flynn@yahoo.com References: <437286.30504.qm@web54011.mail.re2.yahoo.com> In-Reply-To: <437286.30504.qm@web54011.mail.re2.yahoo.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.4 required=2.5 tests=ALL_TRUSTED,BAYES_00 autolearn=failed version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on s4.stradamotorsports.com Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.0 Stable and the CP2101 driver 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, 11 Jun 2008 05:40:22 -0000 Dennis Flynn wrote: > That doesn't seem right to me. Shouldn't I see something like > 7.0-RELEASE-p1 or 7.0-STABLE? Did I do something wrong in my update > to RELEASE? How do I know if I'm running the STABLE kernel with the > driver I want? How can I tell if the driver (uslcom) is there and/or > loaded? To tell if a driver is loaded: dmesg | grep uslcom You'll also want to know about kldstat(1). I've never used freebsd-update. I do suspect that the standard MO in FreeBSD land is to _not_ update the kernel unless explicitly requested. You might want to snoop around the docs with that in mind. Also, FreeBSD may support your driver, but not build it into the GENERIC kernel by default. If the driver you want does not appear in the GENERIC kernel, then you will have to compile a kernel or load a kernel module. There is good documentation on building a kernel in the handbook. Regards, Jason From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 07:25:01 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 655101065671 for ; Wed, 11 Jun 2008 07:25:01 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id F01478FC0A for ; Wed, 11 Jun 2008 07:25:00 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m5B7OvCj031661; Wed, 11 Jun 2008 09:24:58 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 4953F1E5; Wed, 11 Jun 2008 09:24:57 +0200 (CEST) Date: Wed, 11 Jun 2008 09:24:57 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: Daniele Bastianini Message-Id: <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> In-Reply-To: <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.6.11.927 Cc: freebsd-stable@freebsd.org Subject: Re: broken re(4) 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, 11 Jun 2008 07:25:01 -0000 On Tue, 10 Jun 2008 20:43:04 +0200 Daniele Bastianini wrote about Re: broken re(4): DB> > - copying large files (more than some 100MB) via ssh/scp drops the DB> > connection due to "corrupted MAC on input": DB> > Disconnecting: Corrupted MAC on input. DB> > lost connection DB> I had the same problem. DB> I fixed it (for now) making a buildworld with DB> *default date=2008.03.01.00.00.00 in my src csup configuration. DB> I'm not so skilled to investigate in the sources but the problem is DB> after this date. For me all versions from cvs and all patches from Pyun are working now, after I have solved the issue with the bad riser card. I still think it's funny that the riser causes this kind of trouble for the networking chips. On the other hand, I have not been able to get more than about 10MByte/s through the interfaces of this particular system. I have 1GBit-networking equipment, and the other systems (which are used as router) have no problem doing a throughput of >20MB/s. Even bonding the two interfaces using lagg(4) does not improve the performance - where else could be the bottleneck? The only difference here is that I have the extra SATA-controller with disks in there. However, the disks appear to be as fast as I can expect from a SATA150-interface. cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 07:35:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B95B71065673 for ; Wed, 11 Jun 2008 07:35:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.226]) by mx1.freebsd.org (Postfix) with ESMTP id 8B24E8FC20 for ; Wed, 11 Jun 2008 07:35:25 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so3591239rvf.43 for ; Wed, 11 Jun 2008 00:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=j5iGNU9J2VOCURcUab29KfFq5Rv7H7zjHUGxb8kl2KM=; b=pRL/88RrzejejCmgzNKxteM3u7pqbxdcreYYo2kYTG/AbwNxc0OH6zYgZwvYHhPFHb XGJutPS+uF7RQ3h6U1dpHEZ9/dk67eVzGo1pCNOfvsKeOZTH7PM0eL0efSyVjpaT5tWg zqOni0TmAb19hAq2nmsTxWo7YpzGnxS6WW3Wg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ixJljoerE+Ocmxj5tJqY+we08zaiJSLe/67Hd1zsR6ASIRI+ZM8pfxaUd8Wg7wcERr quzuzfQ7jE1F+HNJQS6w6njbAhss3FOrXTSdB+Q8LO9tVXGS+9BbuuTrmJoUcon8PpvA PGxV4dfX5O7umivw4VW2K8zc+RFX9Kl2Mz5vY= Received: by 10.140.144.1 with SMTP id r1mr3631680rvd.199.1213169725142; Wed, 11 Jun 2008 00:35:25 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm18085938rvf.9.2008.06.11.00.35.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 00:35:24 -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 m5B7XFqJ004608 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 16:33:15 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5B7XEGi004607; Wed, 11 Jun 2008 16:33:14 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Wed, 11 Jun 2008 16:33:14 +0900 From: Pyun YongHyeon To: Jack Vogel Message-ID: <20080611073313.GF3529@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch 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: Wed, 11 Jun 2008 07:35:25 -0000 On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > This is a small patch that Sam came up with for me, it will allow > drivers to know > when a vlan attaches. > > It is transparent to any code that doesn't want to change, but this > will allow my > drivers to finally utilize the vlan hardware filter (something Linux has had for > ever but we lacked). > Just curious, is there any rule how to use that new capability? Because drivers will receive events whenever VLAN tags are added/removed they would know how to act for these events. If promiscuous mode is on for interface, driver should not filter any VLAN tagged frames, right? If users want to disable VLAN hardware filtering feature what is best way to perform this? Introducing a new flag like IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? I guess VIA Rhine III also have VLAN hardware filtering capability so it would be even better if we have a way to share common part. > My test group has done some basic testing of this and it is working great. > But we wanted to give any vlan users a chance to see, ask questions, or > whatever before its committed. > > Jack -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 09:36:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EDFF51065676 for ; Wed, 11 Jun 2008 09:36:16 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 771948FC22 for ; Wed, 11 Jun 2008 09:36:16 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from orphanage.alkar.net (account mav@alkar.net [212.86.226.11] verified) by cmail.optima.ua (CommuniGate Pro SMTP 5.1.14) with ESMTPA id 145497848; Wed, 11 Jun 2008 12:36:15 +0300 Message-ID: <484F9C8E.1080202@FreeBSD.org> Date: Wed, 11 Jun 2008 12:36:14 +0300 From: Alexander Motin User-Agent: Thunderbird 2.0.0.0 (X11/20070424) MIME-Version: 1.0 To: Kostik Belousov References: <48470853.6080807@FreeBSD.org> <20080605110447.GB94309@deviant.kiev.zoral.com.ua> In-Reply-To: <20080605110447.GB94309@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Crashes in devfs. Possibly on interface creation/destruction. 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, 11 Jun 2008 09:36:17 -0000 Kostik Belousov wrote: > Try the following patch. It is against current, there might be further > races at the device destruction, but may be not. Also, please note that > devfs in RELENG_6 and RELENG_7/CURRENT are diverged enough to make MFC > of most bugfixes to RELENG_6 nearly impossible. > > diff --git a/sys/kern/kern_conf.c b/sys/kern/kern_conf.c > index e9d0f7b..af9a47d 100644 > --- a/sys/kern/kern_conf.c > +++ b/sys/kern/kern_conf.c > @@ -825,9 +825,9 @@ make_dev_alias(struct cdev *pdev, const char *fmt, ...) > va_end(ap); > > devfs_create(dev); > + dev_dependsl(pdev, dev); > clean_unrhdrl(devfs_inos); > dev_unlock(); > - dev_depends(pdev, dev); > > notify_create(dev); Looks reasonable. For RELENG_6 it also applies with minor differences. Put it to the production. As soon as problem shows itself not very often, positive result probably will be seen only after several weeks of successive operation. Thank you. -- Alexander Motin From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 10:09:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45C3F1065670 for ; Wed, 11 Jun 2008 10:09:41 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id A01008FC13 for ; Wed, 11 Jun 2008 10:09:39 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [10.0.1.101] (unknown [195.34.104.214]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id CB7031522C59; Wed, 11 Jun 2008 12:53:07 +0300 (EEST) Message-ID: <484FA07E.60103@lozenetz.org> Date: Wed, 11 Jun 2008 12:53:02 +0300 From: Anton - Valqk User-Agent: Mozilla-Thunderbird 2.0.0.9 (X11/20080110) MIME-Version: 1.0 To: Andy Kosela References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> In-Reply-To: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Found to be clean X-HostIT-MailScanner-From: lists@lozenetz.org Cc: freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 11 Jun 2008 10:09:41 -0000 Just my 5cents (some thoughts), I fully agree with the lines below. As noticed below there is more attention to developing new features, than making releases rock solid stable. As mentioned in reply posts the 3 branches 6.X 7.X and 8.X takes too many resources and is very hard to support. I, personally, will be waiting for 7.2 release (noticed that .2 over few (3-4 years)) are most stable ones. My main drama with FreeBSD is that ports don't have -SECURITY patches, and if I there is a bug in php I have to rerbuild and populate the latest version. Another _very important_ thing is that there is no binary support to packages that has vulns, and you have to rebuild them from ports. Just a simple example: I have 4-5 fbsd machines and about 15-20 debian stable machines. To administer fbsd machines when there are ports bugs(bugs in ports I use) it takes me at least about 4times more time than update _all_ debian machines... Well...I have other things to do too, too many... now guess what I will choose? I'll use debian, and that's not because I don't have will to use freebsd, it's simply because I do my tasks 4 times slower than when I choose debian. Someone will say "FreeBSD is not for you, then back off". That's not the point, I like fbsd, but as more busy I get, as less I'll be able to use it, takes too much of my time. Once I've told that there is no binary support (but I didn't expressed myself correctly). There is no ports VULNS binary support. If there is (and I've never heard of it), I'll be very happy someone to point me out this, because I'll continue running fbsd. Ah, another thing, I'm waiting for virtualization networking layer for jails for quite long. I've tested it on a test server, worked perfect, but on production I don't want to patch my base. there are few other features to jals that never got commited in base, and as I said I don't want to patch it... in linux (debian for me) there is xen that works with 'new' intel hardware virtualization, that's another red point for debian.... there are other things that I'll leave unsaid....so... that's all for now. sorry for my bad english, it's not my native. these are just my thoughts and don't want to force anyone to agree with them, but I'll be happy to read your thoughts on this. cheers, valqk. Andy Kosela wrote: > On 6/8/08, Freddie Cash wrote: > >>> On 6/7/08, Jo Rhett wrote: >>> The question I raised is simply: given the number of bugs opened and >>> fixed since 6.3-RELEASE shipped, why is 6.3 the only supported >>> version? Why does it make sense for FreeBSD to stop supporting a >>> stable version and force people to choose between two different >>> unstable versions? Is this really the right thing to do? >>> >> Define the terms "stable" and "unstable", how you measure said >> "stability" and "instability", and what you are comparing them >> against. >> > > This whole discussion is really interesting as it clearly showcases two > common trends in computing (rapid development vs stability) On the one > side we got people (let's call them developers or computer scientists) > who are more interested in development than stabilization of the existing > code base. It's natural for them to think more about new features, > researching new ideas and implementing them. It resembles an > academic project, research project.Those computer scientists do not > care much about stability, they are mainly interested in hacking on the > code for the fun of it. It is open source after all as someone wisely > remarked. From my own experience most if not all community based > projects are more interested in following this trend than stabilization of > the code. Although they do care about stability of their code base, their > focus is more on implementing new features and moving rapidly forward. > In today's quickly changing world we see this trend as prevailing. > > On the other hand though, there is a trend which focuses on maximum > long term stabilization of the code base. Usually we see this trend in high > end commercial companies serving the needs of mission critical > businesses where even a minute of downtime can cause loss of > thousands of dollars or even loss of lives of people (imagine stock > exchanges, banks, financial & insurance institutions, army and police > facilities, hospitals, nuclear plants etc.). Those types of > businesses/institutions truly needs a maximum stable operating system. > They really do not care about "new features", but they do care about > maximum stability of the existing code, security, and nonstop business > continuity even in the face of natural disasters. There is only one operating > system I know of that survived 9/11 attacks - this is OpenVMS. > It's not uncommon to see VMS uptimes of more than 10 years (you can ask > Amsterdam police for evidence). Now that is a true stability! On the other > note though, stability is the direct opposition of development and change. > Something which is *stable* cannot change or must change very slowly in > the long term. On the other hand something which is changing rapidly cannot > by the very definition of it be stable but rather is...unstable. Plato said it > very wisely in Timaeus: "What is that which always is and has no becoming; > and what is that which is always becoming and never is?". In other words > one could say - what is that which is always the same and stable and what > is that which is always changing and is unstable? This elaborate thinking > is directly connected even with the trends in todays computing. When the > code base is changing rapidly and quickly you cannot say it's very stable. > Something stable is always something heavy tested and unchanging. > > So on the one hand we got users like Jo who wants long term stabilization, > who depends on FreeBSD to run their mission critical systems, and on the > other the developers who are more interested in the *development* than > maintaining and supporting older releases for many years. I got to agree > with the developers -this is open source project with limited resources. In > order to offer long term support the whole focus of the project would have > to be changed - and you can't force people to do something they don't want > to do in the open source world. > It's more fun to work on implementing new code, than squashing bugs or > fanatically audit the code in search of security flaws in old releases. The > open source is moving very rapidly forward and it's not only FreeBSD. Look > at Linux. There is more than 10,000 messages each month on LKML. > Kernel.org peoples also do not care much about stability (recent problems > with vanilla kernels do support my thesis) - they commit so fast and massively > that it becomes real hard to maintain this "beast" even for seasoned hackers. > But someone who is sane will not be using kernel.org kernels in mission critical > production environments but rather commercial distro kernels like Red Hat's > versions. Also they won't be using 8-CURRENT on production systems either. > Those are more research projects than operating environments for data > centers. But when Red Hat is taking kernel.org kernel and put it out as part > of their distro they give 7 (read: seven) years support for that particular > kernel, userland and any third party application they support. They backport > all security and bug fixes to the "so called" stable release during those seven > years. That is a long time in the open source world, as in the general > computing world. They can do this because they have resources for > that - they are operating as a commercial company. > > In FreeBSD even if you upgraded cleanly base system (this is very easy > and fast now with freebsd-update(8)) there is always problem with ports. > I'm perfectly aware that developers are more focused on the base system > and ports are served on "as is" basis but most of the production systems > deployed worldwide are using ports and depends on them most of their time. > I also understand ports team in saying that there is no resources to have > many branches of ports tree at the same time, but this little example will > show that in the long term sometimes things are not working very smoothly > for people who are running mission critical systems. Let's say some > hypothetical 6.x-RELEASE comes out in January. The Apache port is > freezed at hypothetical 2.0.40 version. Now in April someone discloses > some very critical security flaw which affects all versions of Apache prior > to 2.0.43. Now what you can do? You can update your Apache port to > 2.0.43 fixing a security hole. But at the same time you don't know the > upstream team changed dramatically some internal things in code, added > tons of new features and at the same time introduced a ton of new bugs > and possibly new security flaws which will be founded at a later time. > Those changes in code can also very well break your applications which > depended on the specific code in 2.0.40 version. So you are left with > headaches and backup tapes (of course you would first test the upgrade > process on the test machines). But my issue here is that ports really do > not offer real stability for mission critical systems who often depends for > years on specific versions of particular software (like banks). Red Hat in > that case backports new security patches to those old stable versions and > it seems it is some solution for such businesses. Of course I know there is > no resources for creating supported -SECURITY branch of ports tree which > would backport those patches. > > FreeBSD has always been known for its legendary stability and mature > code base which is why many commercial companies depend on it every > day. "The anomaly" as someone said of long term support for 4.x releases > only helped to see FreeBSD as more stable and viable solution than Linux by > many businesses. Mission critical systems needs long term support (read: at > least backporting security patches) and stable systems that can run for years > without interruption. When it comes to stability vs development maybe there is > time to rethink FreeBSD overall strategy and goals. Major companies using > FreeBSD in their infrastructure like Yahoo! or Juniper Networks would > definetly benefit from such moves focused on long term support of stable > releases. I honestly think it is in their interest to support, even financially > > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 11:44:10 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0669106564A for ; Wed, 11 Jun 2008 11:44:10 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.kernel32.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 461468FC14 for ; Wed, 11 Jun 2008 11:44:09 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from www.terrorteam.de (localhost [127.0.0.1]) by crivens.kernel32.de (Postfix) with ESMTP id 16A2CB0290; Wed, 11 Jun 2008 13:26:13 +0200 (CEST) MIME-Version: 1.0 Date: Wed, 11 Jun 2008 13:26:13 +0200 From: Marian Hettwer To: Anton - Valqk In-Reply-To: <484FA07E.60103@lozenetz.org> References: <484FA07E.60103@lozenetz.org> Message-ID: X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1-rc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 11:44:10 -0000 Hi there, some thoughts to your problem in regards to Debian administration time needed vs. FreeBSD administration time needed. I believe I can make a point there, since I have 600 debian boxes under my hood but still am a FreeBSD advocate ;-) On Wed, 11 Jun 2008 12:53:02 +0300, Anton - Valqk wrote: > > My main drama with FreeBSD is that ports don't have -SECURITY patches, > and if I there is a bug in php > I have to rerbuild and populate the latest version. Thats unfortunatly true. But there is a way around. As soon as you have several FreeBSD boxes, I'd advise you to install your own FreeBSD box for packages building. So if you need to update your php installations, go to your build box (which has the very same versions of programs installed as your production boxes), update your ports tree and do a "make package" of your new php port. If the new php package works fine on your build box, roll it out via "pkg_add -r $NEWPHPTHINGY" and off you go. > Another _very important_ thing is that there is no binary support to > packages that has vulns, > and you have to rebuild them from ports. > Well, its one time doing a make package... Even debian has no plus point there (at least in our environment at work). We pretty much always need our Apache 2 custom build, not the way the Debian projects build it. Thus we have a Debian build box around and build our own Apache 2.2 package. This is, indeed, the same amount of effort you would have when using FreeBSD. IMO the overhead in Debian to build a package is higher than in FreeBSD, but YMMV. > Just a simple example: > I have 4-5 fbsd machines and about 15-20 debian stable machines. > To administer fbsd machines when there are ports bugs(bugs in ports I > use) it takes me at > least about 4times more time than update _all_ debian machines... depends on the way you go. Genereally speaking, you really really want a build and test machine before you deploy a security update or even a new version of your software (in this case: php). Even with Debian boxes you really shouldn't just "apt-get upgrade && apt-get update" but test before! > Well...I have other things to do too, too many... now guess what I will > choose? > I'll use debian, and that's not because I don't have will to use > freebsd, it's simply because I do my tasks 4 times slower than when I > choose debian. hhmm... I really can't agree on that statement. If you do your admin work in a clean and sane way, most of the time spend for updating boxes is spent on testing the change before upgrading. The difference between a "debuild" for building a new package, and then apt-get upgrade / update them on your box vs. "make package" and pkg_add -r them on your box is really slim... > Someone will say "FreeBSD is not for you, then back off". That's not the I wouldn't say that :) > > Once I've told that there is no binary support (but I didn't expressed > myself correctly). There is no ports VULNS binary support. > If there is (and I've never heard of it), I'll be very happy someone to > point me out this, because I'll continue running fbsd. > If you take a close look onto how the debian project is backporting security fixes you would probably agree that pretty often it's more desireable to jump to a newer version of that software than instead just security fixing it. Examples needed? MySQL 4.1.11 was the "stable" MySQL 4.1 in Debian Sarge. Of course it got security fixed, but not bugfixed. You get a secure version of MySQL 4.1 in Debian but not a stable one, because important bugfixes are missing. I'd rather upgrade to the latest MySQL 4.1.xx instead. And of course, do your testing before jumping version numbers. I hope that my impressions will help you in working with FreeBSD in a server environment. Cheerio, Marian From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 12:36:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7A2C106566B for ; Wed, 11 Jun 2008 12:36:32 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 6AD928FC13 for ; Wed, 11 Jun 2008 12:36:32 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1386341pyb.10 for ; Wed, 11 Jun 2008 05:36:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=mdTpUGpPouxvRWkJKgWZ1K+9g3n8VMuLSFYoLkmHQ8E=; b=gZxZ1fmETKhTG/9n7ee2UdHiPpu793KVvj+JKO5O1zqgCGwoMwwjzkhTjbnlMo3g6C Fr3Iv/+GRovWz1Qh8AOxNfj4O4OjR9eZfKVsJ6PHRfnJO6jgCdKeGZ27tphka59YdsRy 5+Qi59ooxjD+iNpReOJg0NCtoHm3oTdKrQ6/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=uD+gOjqICIlVu1fG1GCpcQ7QxZRmSpmf4msJ4FvyssUuqXsmlsCbfz05sf50NihzBa ERwiKUigGK3PzLq2a3kNBrbPvmhkatyuGOCiyLHr8POXhddHKb8WbIOMrEoWjBbFTai+ +QIEYp/M3xFGNvZWc80g3XK9sVaXm5CWBooIU= Received: by 10.114.134.20 with SMTP id h20mr6432784wad.91.1213187790863; Wed, 11 Jun 2008 05:36:30 -0700 (PDT) Received: by 10.114.112.6 with HTTP; Wed, 11 Jun 2008 05:36:30 -0700 (PDT) Message-ID: <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> Date: Wed, 11 Jun 2008 14:36:30 +0200 From: "Andy Kosela" To: freebsd-stable@freebsd.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <484FA07E.60103@lozenetz.org> Cc: rwatson@freebsd.org, lists@lozenetz.org, mh@kernel32.de Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 12:36:32 -0000 Robert, Thank you for your insights. I think that this agreement between users and developers does occur. The proper balance between rapid development vs long term stability is the platform through which such agreement can be achieved. It's up to the Core Team to reasonably steer the Project in such a way as to achieve the greatest results. FreeBSD has always been focused on creating simple, stable and reliable operating system for system administrators and let's keep it that way. Longer term support for -RELEASE gives many companies a stable platform to develop and maintain their infrastructure. I think 5 years support for major FreeBSD release (like major 6 or 7) would be really perfect for many of us. On Wed, Jun 11, 2008 at 1:26 PM, Marian Hettwer wrote: > But there is a way around. As soon as you have several FreeBSD boxes, I'd > advise you to install your own FreeBSD box for packages building. > So if you need to update your php installations, go to your build box > (which has the very same versions of programs installed as your production > boxes), update your ports tree and do a "make package" of your new php > port. > If the new php package works fine on your build box, roll it out via > "pkg_add -r $NEWPHPTHINGY" and off you go. I think Anton raised a valid and reasonable point here by analyzing my previous statements. Every data center environment test the upgrade process before deploying it on production machines, but my point circulated around the whole different theme. Backporting Backporting security and bug fixes to *STABLE* versions of ports would definetly render the whole ports framework infrastructure more solid and trustworthy for organizations that need mission critical stable and reliable environment to work in. Creating -SECURITY branch of ports tree with support *just* for common server applications like apache, postfix, mysql or vsftpd (definetly not for all available ports) would very well encourage more companies now stuck with the only alternative (redhat/centos or debian) to trust this ports tree branch in deploying their applications which very often needs specific versions of the software to run properly. Right now it's sometimes very risky to jump to the latest available upstream version as it very often breaks compatibility with older versions. I've been toying with the idea to create such -SECURITY branch, at least just for ports I use extensively. I'm not aware of no such project (open source, commercial) that is doing that. I'm curious how many people out there would be also interested in such an idea. > If you take a close look onto how the debian project is backporting > security fixes you would probably agree that pretty often it's more > desireable to jump to a newer version of that software than instead just > security fixing it. > Examples needed? > MySQL 4.1.11 was the "stable" MySQL 4.1 in Debian Sarge. Of course it got > security fixed, but not bugfixed. You get a secure version of MySQL 4.1 in > Debian but not a stable one, because important bugfixes are missing. > I'd rather upgrade to the latest MySQL 4.1.xx instead. > And of course, do your testing before jumping version numbers. Redhat/CentOS is more reliable here as backports involves both security and bug fixes, plus even new hardware enhancements. -- Andy Kosela ora et labora From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:26:33 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4F3041065677 for ; Wed, 11 Jun 2008 15:26:33 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (unknown [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id B5D9B8FC19 for ; Wed, 11 Jun 2008 15:26:32 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.1/8.14.1) with ESMTP id m5BFQUAe059131; Wed, 11 Jun 2008 17:26:30 +0200 (CEST) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.1/8.14.1/Submit) id m5BFQT2p059130; Wed, 11 Jun 2008 17:26:29 +0200 (CEST) (envelope-from olli) Date: Wed, 11 Jun 2008 17:26:29 +0200 (CEST) Message-Id: <200806111526.m5BFQT2p059130@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, gerrit@pmp.uni-hannover.de In-Reply-To: <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (FreeBSD/6.2-STABLE-20070808 (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Wed, 11 Jun 2008 17:26:30 +0200 (CEST) Cc: Subject: Re: broken re(4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, gerrit@pmp.uni-hannover.de List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 15:26:33 -0000 Gerrit Kühn wrote: > On the other hand, I have not been able to get more than about 10MByte/s > through the interfaces of this particular system. I have 1GBit-networking > equipment, and the other systems (which are used as router) have no > problem doing a throughput of >20MB/s. Even bonding the two interfaces > using lagg(4) does not improve the performance - where else could be the > bottleneck? A few questions or hints ... - What is the CPU usage during your network test (user, sys, intr, idle)? - Do you see errors in "netstat -i"? - Do you use jumbo frames? - Is polling enabled? - Are there any network-related sysctls (/etc/sysctl.conf) or kernel settings? Have you enabled kernel debugging features (INVARIANTS, WITNESS etc.)? - Do you have any packet filter rules (PF, IPF, IPFW)? Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C++ is the only current language making COBOL look good." -- Bertrand Meyer From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:37:59 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 181AB106567D for ; Wed, 11 Jun 2008 15:37:59 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 924458FC0A for ; Wed, 11 Jun 2008 15:37:58 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m5BFbtMA000516; Wed, 11 Jun 2008 17:37:56 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 24A7F72; Wed, 11 Jun 2008 17:37:55 +0200 (CEST) Date: Wed, 11 Jun 2008 17:37:55 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: freebsd-stable@FreeBSD.ORG Message-Id: <20080611173755.e381fcf0.gerrit@pmp.uni-hannover.de> In-Reply-To: <200806111526.m5BFQT2p059130@lurza.secnetix.de> References: <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> <200806111526.m5BFQT2p059130@lurza.secnetix.de> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.6.11.82437 Cc: Oliver Fromme Subject: Re: broken re(4) 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, 11 Jun 2008 15:37:59 -0000 On Wed, 11 Jun 2008 17:26:29 +0200 (CEST) Oliver Fromme wrote about Re: broken re(4): OF> > On the other hand, I have not been able to get more than about OF> > 10MByte/s through the interfaces of this particular system. I have OF> > 1GBit-networking equipment, and the other systems (which are used OF> > as router) have no problem doing a throughput of >20MB/s. Even OF> > bonding the two interfaces using lagg(4) does not improve the OF> > performance - where else could be the bottleneck? OF> A few questions or hints ... OF> - What is the CPU usage during your network test (user, OF> sys, intr, idle)? I will test and report that tomorrow. OF> - Do you see errors in "netstat -i"? None. OF> - Do you use jumbo frames? No. OF> - Is polling enabled? No. I tested polling on a lot of different machines earlier and never found it to improve performance so far (same for jumbo frames, btw). OF> - Are there any network-related sysctls (/etc/sysctl.conf) OF> or kernel settings? Have you enabled kernel debugging OF> features (INVARIANTS, WITNESS etc.)? No, stock GENERIC, only with a lot of things disabled. OF> - Do you have any packet filter rules (PF, IPF, IPFW)? No, not on this machine. The faster machines are router/firewalls, they do filtering; so it should be something different... cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:39:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36A1F106564A; Wed, 11 Jun 2008 15:39:20 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (raats.xs4all.nl [82.95.230.43]) by mx1.freebsd.org (Postfix) with ESMTP id DF3818FC1C; Wed, 11 Jun 2008 15:39:19 +0000 (UTC) (envelope-from jack@jarasoft.net) Received: from raats.xs4all.nl (localhost.jarasoft.net [127.0.0.1]) by raats.xs4all.nl (Postfix) with ESMTP id ADB3F16A566; Wed, 11 Jun 2008 17:28:27 +0200 (CEST) Received: from jara3 (unknown [192.168.1.101]) by raats.xs4all.nl (Postfix) with ESMTPA id 4856C16A477; Wed, 11 Jun 2008 17:28:27 +0200 (CEST) Message-ID: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> From: "Jack Raats" To: "freebsd-stable" , Date: Wed, 11 Jun 2008 17:28:26 +0200 Organization: JaRaSoft, Steenbergen, Nederland MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Signed-With-GnuPG: GPGrelay Version 0.959 (Win32) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: FreeBSD 7 and Apache 1.3.41 PROBLEM X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jack Raats List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 15:39:20 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On a server I was running FreeBSD 6.3-STABLE together with = apache 1.3.41 without any problem. After upgrading FreeBSD to FreeBSD 7.0-STABLE using a source = upgrade, compiling, and a full recompile of all the ports = apache refuses to start, or starts and exits with a .core dump. In httpd-error.log [Wed Jun 11 17:01:04 2008] [info] mod_unique_id: using ip addr = 10.10.10.10 [Wed Jun 11 17:01:05 2008] [info] (2)No such file or directory:= make_sock: for port 80, setsockopt: (SO_ACCEPTFILTER) [Wed Jun 11 17:01:05 2008] [warn] pid file /var/run/httpd.pid = overwritten -- Unclean shutdown of previous Apache run? After hashing out #LoadModule unique_id_module libexec/apache/mod_unique_id.so #AddModule mod_unique_id.c Apache starts normally Can anyone explain this? Jack -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) - GPGrelay v0.959 iD8DBQFIT+8bPh5RwW/NzC4RAn9aAKCVKIvHFmFzpeaveqvHYbXjIRrhuACg0vxr f5f3FDGYigHPRaqGz+ZkDok=3D =3DTZvG -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:49:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4A4151065676 for ; Wed, 11 Jun 2008 15:49:51 +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 EE4A18FC16 for ; Wed, 11 Jun 2008 15:49:50 +0000 (UTC) (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 9D37346B88; Wed, 11 Jun 2008 11:49:49 -0400 (EDT) Date: Wed, 11 Jun 2008 16:49:49 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Anton - Valqk In-Reply-To: <484FA07E.60103@lozenetz.org> Message-ID: <20080611164704.J40102@fledge.watson.org> References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <484FA07E.60103@lozenetz.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 11 Jun 2008 15:49:51 -0000 On Wed, 11 Jun 2008, Anton - Valqk wrote: > I fully agree with the lines below. > As noticed below there is more attention to developing new features, > than making releases rock solid stable. ... > Ah, another thing, > I'm waiting for virtualization networking layer for jails for quite long. > I've tested it on a test server, worked perfect, but on production I don't > want to patch my base. > there are few other features to jals that never got commited in base, and as > I said I don't want to patch it... The reason that the virtualization patches aren't in the tree is precisely *because* we care about stability and are willing to slow down feature development in order to accomplish it. Some features take years to stabilize, and just because a patch works OK in your environment doesn't mean it will work in everyone's. Moderating the rate at which we adopt agressive new features is part of an intentional strategy to avoid letting development trees destabilize to a point where it's unproductive. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:51:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C48871065670 for ; Wed, 11 Jun 2008 15:51:09 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id 227058FC1D for ; Wed, 11 Jun 2008 15:51:08 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [10.0.1.101] (unknown [87.121.18.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id 933BD1522C59; Wed, 11 Jun 2008 18:51:06 +0300 (EEST) Message-ID: <484FF461.6000306@lozenetz.org> Date: Wed, 11 Jun 2008 18:50:57 +0300 From: Anton - Valqk User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Marian Hettwer References: <484FA07E.60103@lozenetz.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Found to be clean X-HostIT-MailScanner-From: lists@lozenetz.org Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 15:51:09 -0000 Thanks for the answer! I'm glad someone answered me a human way, because two times before, I wasn't answered that way (well... my posts were angry and incomplete but...that's why i didn't continued to post...my bad). now on topic: Marian Hettwer wrote: > Hi there, > > some thoughts to your problem in regards to Debian administration time > needed vs. FreeBSD administration time needed. > I believe I can make a point there, since I have 600 debian boxes under my > hood but still am a FreeBSD advocate ;-) > > > On Wed, 11 Jun 2008 12:53:02 +0300, Anton - Valqk > wrote: > >> My main drama with FreeBSD is that ports don't have -SECURITY patches, >> and if I there is a bug in php >> I have to rerbuild and populate the latest version. >> > Thats unfortunatly true. > But there is a way around. As soon as you have several FreeBSD boxes, I'd > advise you to install your own FreeBSD box for packages building. > So if you need to update your php installations, go to your build box > (which has the very same versions of programs installed as your production > boxes), update your ports tree and do a "make package" of your new php > port. > If the new php package works fine on your build box, roll it out via > "pkg_add -r $NEWPHPTHINGY" and off you go. > > I do have a build server(well a jail but works for me), also I have test eviornment (jailed too). I use this jail to build all my pkgs and use pkg_add -r (sweeet!!). For most of the ports this works, but sometimes something in make package breaks and i get a port installed partially (last case - apache22 got installed but no /usr/local/etc/rc.d/apache22 rc script, previous - pg_ctl never got installed) and in +CONTENTS file the missing files claimed to be there. I've had to rebuild that kind of port so I can install it again (after pkg_delete) to have the port working. This happens most often when I do make install package-recursive (so I can get all needed ports installed). I've tried to tell this in ports@ and I was answered that "everything is working for us" or kind of. no one tried to investigate... Another strange thing is that when I use php-extensions to build all that I need (this takes most of my time when build/install new php) breaks because of the ?'bug'? described few lines above. as I said noone got interested in this problem... I have another complain from fbsd but I'll tell about it at the end. >> Another _very important_ thing is that there is no binary support to >> packages that has vulns, >> and you have to rebuild them from ports. >> >> > Well, its one time doing a make package... > Even debian has no plus point there (at least in our environment at work). > We pretty much always need our Apache 2 custom build, not the way the > Debian projects build it. Thus we have a Debian build box around and build > our own Apache 2.2 package. > This is, indeed, the same amount of effort you would have when using > FreeBSD. > IMO the overhead in Debian to build a package is higher than in FreeBSD, > but YMMV. > If you build packages from source then debian just sux (much more complex and long procedure), but there is a tell - "if you do it with debian - do it THE DEBIAN WAY"... :-). I totally agree with that, but on all debian machines I use packages provided from debian, because they've made it very modular, and I was able to config them the way I need and everything is working for me. In 99.99% of the cases when I do apt-get dist-upgrade the machine works like a charm after it, and that's a fact (in fbsd when make installworld too, but not for ports - which is the focus here). Actually that's what *BSD prouds with - building everything from source (like gentoo), well it's a must to be simplified then (debian where everything is supposed to be used from bin .deb) :). About the bug fixes, I think if that's a SECURITY backport it shouldn't fix bugs, because I've saw few devs deploying an app and the were using 'known bug' in ruby to work with. so they were unable to use higher version of ruby that got this bug fixed. (we'll obviously a developer mistake in design but if it's in a production will take months to redesign - not an option). Which is why maybe it's better not to fix bugs but just vulns in SECURITY backports (according to me of course) - if you need that bug fixed, then install new version. > > >> Just a simple example: >> I have 4-5 fbsd machines and about 15-20 debian stable machines. >> To administer fbsd machines when there are ports bugs(bugs in ports I >> use) it takes me at >> least about 4times more time than update _all_ debian machines... >> > depends on the way you go. > Genereally speaking, you really really want a build and test machine before > you deploy a security update or even a new version of your software (in > this case: php). > Even with Debian boxes you really shouldn't just "apt-get upgrade && > apt-get update" but test before! > > >> Well...I have other things to do too, too many... now guess what I will >> choose? >> I'll use debian, and that's not because I don't have will to use >> freebsd, it's simply because I do my tasks 4 times slower than when I >> choose debian. >> > hhmm... I really can't agree on that statement. > If you do your admin work in a clean and sane way, most of the time spend > for updating boxes is spent on testing the change before upgrading. The > difference between a "debuild" for building a new package, and then apt-get > upgrade / update them on your box vs. "make package" and pkg_add -r them on > your box is really slim... > > If you build from src on debian - yes, but as I explained i use debian .debs and for me it's much faster, because on fbsd ports I have the problem described before, and is very common case to rebuild and rebuild port until it puts all the files in the .tgz :( >> Someone will say "FreeBSD is not for you, then back off". That's not the >> > I wouldn't say that :) > > >> Once I've told that there is no binary support (but I didn't expressed >> myself correctly). There is no ports VULNS binary support. >> If there is (and I've never heard of it), I'll be very happy someone to >> point me out this, because I'll continue running fbsd. >> >> > If you take a close look onto how the debian project is backporting > security fixes you would probably agree that pretty often it's more > desireable to jump to a newer version of that software than instead just > security fixing it. > Examples needed? > MySQL 4.1.11 was the "stable" MySQL 4.1 in Debian Sarge. Of course it got > security fixed, but not bugfixed. You get a secure version of MySQL 4.1 in > Debian but not a stable one, because important bugfixes are missing. > I'd rather upgrade to the latest MySQL 4.1.xx instead. > And of course, do your testing before jumping version numbers. > > I hope that my impressions will help you in working with FreeBSD in a > server environment. > > Cheerio, > Marian So, a story happened recently: I've had a disk down (ad2) of course it was in gmirror and the situation was 'ah, damn, but it's ok'... but... when I rebooted the server it occured that ad2 was ACTIVE and maybe last fresh and ad0 was DIRTY, ad2 didn't failed at 100% it was responding and found by the bios (and kernel) but when files were requested it timed out. The problem occured when tried to boot from the second disk (ad0) attached with ad2 (at this moment i didn't know that it fails when disk io occurs). because the ad2 was fresh and ad0 was dirty the gmirror failed to mount and boot OS because it was trying to sync data from partly failed disk, and it wasn't able to. I've shutdowned the machine, plugged out the ad2 disk and fired up again hoping gmirror will be smart enough to boot from ad0... but no luck, I was forced to mount root filesystem with no mirror (ad0s1a) and run the server in no mirror mode so I can have this critical machine running while I find a new disk (few hours later I got it). And the nightmare's just began... when I placed the new disk, the gmirrored volume was still trying to sync from ad2, ofcourse, the ad2 had no info on it (thanks god gmirror was smart enough to not copy the empty disk). I've had to rebuild the whole gmirror partiions, copy the info from a non-mirrored disk (ad0) and etc.etc... you know the procedure... this took me more than 10 hours and about 5hours downtime on a critical machine.... I suppose this has something to do with the priority in gmirror but I don't have the broken disk to test - it's being replaced because it's in warranty.... but anyways... 10 hours lost and 5hours downtime... now I'm purchaseing a 3ware hw raid because I know that I can't trust gmirror... Another strange thing, I've used to use apache22-worker cutom compiled and thread_safe perl, the apache-worker stopped working on a jail (only on one!) and I had to add replacements ot pthread.so in /etc/libmap, I've been adviced not to use worker (as I did) but why the heck after upgrading from 6.3-STABLE to 6.3-STABLE-p3 I got my apache broken and also cron stopped working. strange uh? and all this is in only one jail (I'm using ez-jail to update the world)... if anyone can help me to fix my cron without reinstalling this jail I'd be thanksful! too long mail, that's enough :) cheers, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:54:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 471D31065673 for ; Wed, 11 Jun 2008 15:54:03 +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 168C58FC12 for ; Wed, 11 Jun 2008 15:54:03 +0000 (UTC) (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 B5C4446B17; Wed, 11 Jun 2008 11:54:02 -0400 (EDT) Date: Wed, 11 Jun 2008 16:54:02 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Andy Kosela In-Reply-To: <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> Message-ID: <20080611165009.O40102@fledge.watson.org> References: <484FA07E.60103@lozenetz.org> <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, mh@kernel32.de, lists@lozenetz.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 15:54:03 -0000 On Wed, 11 Jun 2008, Andy Kosela wrote: > Redhat/CentOS is more reliable here as backports involves both security and > bug fixes, plus even new hardware enhancements. In the FreeBSD environment, we call the place that gets a blend of security and bug fixes, plus new minor feature and driver enhancements "-STABLE", and the releases that pick up these changes "point releases". They happen more requently and with less risk than major releases, but still see enough development to represent functional improvements. I guess here's my concern: we offer a spectrum of choice for "I want the most bleeding edge" to "I want no feature changes, just security fixes", and several points in between. We can argue about the exact placement of this points, but the reality is that the balance we have today seems to work well for many developers and users, and reflects a fairly carefully planned use of the available revision control and distribution technology. The place for volunteers to come in is where they see an obvious niche for improvement -- for example, a few years ago this guy named Colin Percival turned up with a binary update system. After a couple of years of enhancement, breaking it in, etc, it's now a standard tool for maintaining FreeBSD systems, and he's our security officer. Similar opportunities exist for offering easier updates to packages, etc, but require people who have a clear need and the technical ability to do the work to turn up and do it. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 15:54:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E040E1065686 for ; Wed, 11 Jun 2008 15:54:20 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id C97DE8FC1A for ; Wed, 11 Jun 2008 15:54:20 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id AD77C1CC068; Wed, 11 Jun 2008 08:54:20 -0700 (PDT) Date: Wed, 11 Jun 2008 08:54:20 -0700 From: Jeremy Chadwick To: Jack Raats Message-ID: <20080611155420.GA65168@eos.sc1.parodius.com> References: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable Subject: Re: FreeBSD 7 and Apache 1.3.41 PROBLEM 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, 11 Jun 2008 15:54:21 -0000 On Wed, Jun 11, 2008 at 05:28:26PM +0200, Jack Raats wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On a server I was running FreeBSD 6.3-STABLE together with apache 1.3.41 without any problem. > > After upgrading FreeBSD to FreeBSD 7.0-STABLE using a source upgrade, compiling, and a full recompile of all the ports apache refuses to start, or starts and exits with a .core dump. > > In httpd-error.log > [Wed Jun 11 17:01:04 2008] [info] mod_unique_id: using ip addr 10.10.10.10 > [Wed Jun 11 17:01:05 2008] [info] (2)No such file or directory: make_sock: for port 80, setsockopt: (SO_ACCEPTFILTER) > [Wed Jun 11 17:01:05 2008] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run? > > After hashing out > #LoadModule unique_id_module libexec/apache/mod_unique_id.so > #AddModule mod_unique_id.c > > Apache starts normally > > Can anyone explain this? If by "this" you're referring to the setsockopt() error, yes. If by "this" you're referring to the coredump, no, not without more information. The problem in your error logs indicate some sort of issue relating to the accept filter in FreeBSD, which Apache can use (accf_http). I don't think Apache 1.3.x has this functionality (rc-script-wise), but on 2.2.x on RELENG_6, we use this in rc.conf to load the accept module prior to Apache starting: apache22_http_accept_enable="yes" You can try loading the module yourself using "kldload accf_http.ko", then restarting (stop/start, not graceful or restart!) Apache. P.S. -- I've removed freebsd-questions@ from the CC, since cross- posting is looked down upon. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:07:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6975E1065677 for ; Wed, 11 Jun 2008 16:07:09 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from smtp01.cdmon.com (smtp01.cdmon.com [212.36.75.232]) by mx1.freebsd.org (Postfix) with ESMTP id 25B068FC1A for ; Wed, 11 Jun 2008 16:07:08 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from [192.168.0.29] (62.Red-217-126-43.staticIP.rima-tde.net [217.126.43.62]) by smtp01.cdmon.com (Postfix) with ESMTP id E6310F7458; Wed, 11 Jun 2008 17:51:20 +0200 (CEST) Message-ID: <484FF478.8010405@minibofh.org> Date: Wed, 11 Jun 2008 17:51:20 +0200 From: Jordi Espasa Clofent User-Agent: Thunderbird 1.5.0.12 (X11/20080430) MIME-Version: 1.0 To: freebsd-apache@freebsd.org References: <4846B64F.4090700@minibofh.org> <484775D4.4090509@p6m7g8.com> <48481A02.2050502@minibofh.org> In-Reply-To: <48481A02.2050502@minibofh.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 11 Jun 2008 16:07:09 -0000 It seems a php-extensions bug. If you comment the mhash.so in /usr/local/etc/php/extensions.ini as: ;entension=mhash.so all works fine and you don't get anymore httpd crash (signal 11) if you use 'apachectl graceful'. Maybe will be a good idea to open PR for this? I hope it helps someone.... (I'm very surprised that this isn't a documented bug in 7.0 yet) -- Thanks, Jordi Espasa Clofent From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:10:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FA21106564A for ; Wed, 11 Jun 2008 16:10:48 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 75E6A8FC13 for ; Wed, 11 Jun 2008 16:10:48 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 617561CC060; Wed, 11 Jun 2008 09:10:48 -0700 (PDT) Date: Wed, 11 Jun 2008 09:10:48 -0700 From: Jeremy Chadwick To: Jordi Espasa Clofent Message-ID: <20080611161048.GA66773@eos.sc1.parodius.com> References: <4846B64F.4090700@minibofh.org> <484775D4.4090509@p6m7g8.com> <48481A02.2050502@minibofh.org> <484FF478.8010405@minibofh.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <484FF478.8010405@minibofh.org> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 11 Jun 2008 16:10:48 -0000 On Wed, Jun 11, 2008 at 05:51:20PM +0200, Jordi Espasa Clofent wrote: > It seems a php-extensions bug. > If you comment the mhash.so in /usr/local/etc/php/extensions.ini as: > > ;entension=mhash.so > > all works fine and you don't get anymore httpd crash (signal 11) if you > use 'apachectl graceful'. > > Maybe will be a good idea to open PR for this? > > I hope it helps someone.... (I'm very surprised that this isn't a > documented bug in 7.0 yet) Many people have reported that the *order* of the extensions in extensions.ini has adverse (positive) effects on PHP segfaults on FreeBSD. I myself haven't ever run into extension ordering issues like those described (and we've done hosting for years), but I don't doubt those who have experienced such. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:17:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28CDB106566B for ; Wed, 11 Jun 2008 16:17:34 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.kernel32.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id 914D48FC0C for ; Wed, 11 Jun 2008 16:17:33 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from www.terrorteam.de (localhost [127.0.0.1]) by crivens.kernel32.de (Postfix) with ESMTP id 08C08B0290; Wed, 11 Jun 2008 18:17:31 +0200 (CEST) MIME-Version: 1.0 Date: Wed, 11 Jun 2008 18:17:31 +0200 From: Marian Hettwer To: Anton - Valqk In-Reply-To: <484FF461.6000306@lozenetz.org> References: <484FF461.6000306@lozenetz.org> Message-ID: X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1-rc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is prematurewithbuggy 6.3 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, 11 Jun 2008 16:17:34 -0000 On Wed, 11 Jun 2008 18:50:57 +0300, Anton - Valqk wrote: > Thanks for the answer! > I'm glad someone answered me a human way, > because two times before, I wasn't answered that way > (well... my posts were angry and incomplete but...that's why i didn't > continued to post...my bad). > Well then, lets continue answering in a human way. Which is, funnily enough, usually the more productive way too ;-) > now on topic: > yeah! >> Thats unfortunatly true. >> But there is a way around. As soon as you have several FreeBSD boxes, > I'd >> advise you to install your own FreeBSD box for packages building. >> So if you need to update your php installations, go to your build box >> (which has the very same versions of programs installed as your > production >> boxes), update your ports tree and do a "make package" of your new php >> port. >> If the new php package works fine on your build box, roll it out via >> "pkg_add -r $NEWPHPTHINGY" and off you go. >> >> > I do have a build server(well a jail but works for me), also I have test > eviornment (jailed too). > I use this jail to build all my pkgs and use pkg_add -r (sweeet!!). > For most of the ports this works, but sometimes something in make > package breaks and i get a port installed partially > (last case - apache22 got installed but no /usr/local/etc/rc.d/apache22 > rc script, previous - pg_ctl never got installed) > and in +CONTENTS file the missing files claimed to be there. hm... sounds like a bug to me. On the other hand, you have to try to get it to be reproducable. If it's a one timer then yes, it's annoying, but really really hard to reproduce and therefor to fix. > I've had to rebuild that kind of port so I can install it again (after > pkg_delete) to have the port working. yeah, annoying. > This happens most often when I do make install package-recursive (so I > can get all needed ports installed). If you can reproduce it step by step, it may be worth posting to ports@ again with what you did and what happened. Either you're doing something wrong, or something is broken. However, it needs to be reproducable. At least in your environment. As a starter, so to say :) The more detailed your steps are written down, the more likely someone will either follow those steps or give you a direct hint on "humm, could be something bad over there... hm hm). > Another strange thing is that when I use php-extensions to build all > that I need (this takes most of my time when build/install new php) > breaks because of the ?'bug'? described few lines above. as I said noone > got interested in this problem... I can't say anything specific about the php problem you said. I'm not using php, or well, very rarely. I'll give it a try to update it the make package way next time. Unluckily this is a one-box only system. hmmm... If I find the time to test, I'll drop you mail. But time is rare (admin life vs. normal life). To cut that short: Yeah, I can understand that this is annoying. But I'm sure as hell: - if it's a bug it can be fixed - if it's a user error, it can be changed - and all this has happened to me when trying to build my own debian packages too ;) And it happened to me with Gentoo, too. Nothing new at all. Just the regular annoyances in sysadmins life. IMO :) >>> Another _very important_ thing is that there is no binary support to >>> packages that has vulns, >>> and you have to rebuild them from ports. >>> >>> >> Well, its one time doing a make package... >> Even debian has no plus point there (at least in our environment at > work). >> We pretty much always need our Apache 2 custom build, not the way the >> Debian projects build it. Thus we have a Debian build box around and > build >> our own Apache 2.2 package. >> This is, indeed, the same amount of effort you would have when using >> FreeBSD. >> IMO the overhead in Debian to build a package is higher than in FreeBSD, >> but YMMV. >> > If you build packages from source then debian just sux (much more > complex and long procedure), but there is a tell - "if you do it with > debian - do it THE DEBIAN WAY"... :-). I am doing it the debian way. Using the debian source package and try to update from there. Still its a more complex procedure then upgrading a FreeBSD port. I just can't use the prebuilt debian packages. So where's the Debian way from that point?! > I totally agree with that, but on all debian machines I use packages > provided from debian, because they've made it very modular, > and I was able to config them the way I need and everything is working > for me. You're lucky then :) > In 99.99% of the cases when I do apt-get dist-upgrade the machine works > like a charm after it, and that's a fact (in fbsd when make installworld > too, but not for ports - which is the focus here). Right. One should never mix up, that Debian is, well, a kernel and a whole lot of software, whereas in FreeBSD you really have a line between the base OS and later installed software (ports). > Actually that's what *BSD prouds with - building everything from source > (like gentoo), well it's a must to be simplified then (debian where > everything is supposed to be used from bin .deb) :). > I really don't think that *BSD is proud about building everything from source. Since we now even have freebsd-update to binary update FreeBSD itself. And you usally find prebuilt packages too. No, No. IMO FreeBSD isn't proud about building everything from source :) I do have that feeling about Gentoo users, though *g* > > About the bug fixes, I think if that's a SECURITY backport it shouldn't > fix bugs, because I've saw few devs deploying an app and the were using > 'known bug' in ruby to work with. > so they were unable to use higher version of ruby that got this bug > fixed. (we'll obviously a developer mistake in design but if it's in a > production will take months to redesign - not an option). hhhmm... but then you're really in trouble. This is a situation... well, hell no. I don't wanna be in this game. A bug in a peace of software can lead to uncontrolled shutdown or could even evolve into a security whole. If possible I don't want bugs. If there's an application which just runs with the buggy version of ruby (perl, python, whatever), then lets start beating the devs. Literally speaking ;) > Which is why maybe it's better not to fix bugs but just vulns in > SECURITY backports (according to me of course) - if you need that bug > fixed, then install new version. > Opinions really will vary on this topic. In my MySQL example, we want to have the bugfixed version, 'cause those bugs are really bad. Same counts for Apache (not as often as MySQL, though). >> hhmm... I really can't agree on that statement. >> If you do your admin work in a clean and sane way, most of the time > spend >> for updating boxes is spent on testing the change before upgrading. The >> difference between a "debuild" for building a new package, and then > apt-get >> upgrade / update them on your box vs. "make package" and pkg_add -r them > on >> your box is really slim... >> >> > If you build from src on debian - yes, but as I explained i use debian > .debs and for me it's much faster, because on fbsd ports I have the > problem described before, > and is very common case to rebuild and rebuild port until it puts all > the files in the .tgz :( Well yes, thats true. However, take a look at the Latest packages on FreeBSD's ftp mirror. There are new versions available pretty often. On the other hand, you said, you want to have the same version, just security fixed. Well, I bet the FreeBSD ports team just can't do that, due to a lack of manpower. Really. Throw in a whole lotta money to employ a few people, or do it your own. The existing team is doing a wonderful job in keeping the ports tree up to date and trying to keep the pr-database as low as possible. But from what I know the existing team really doesn't look like it can handle -security branches of the ports tree. > > So, a story happened recently: > I've had a disk down (ad2) of course it was in gmirror and the situation > was 'ah, damn, but it's ok'... > but... when I rebooted the server it occured that ad2 was ACTIVE and > maybe last fresh and ad0 was DIRTY, > ad2 didn't failed at 100% it was responding and found by the bios (and > kernel) but when files were requested it timed out. > The problem occured when tried to boot from the second disk (ad0) > attached with ad2 (at this moment i didn't know that it fails when disk > io occurs). > because the ad2 was fresh and ad0 was dirty the gmirror failed to mount > and boot OS because it was trying to sync data from partly failed disk, > and it wasn't able to. > I've shutdowned the machine, plugged out the ad2 disk and fired up again > hoping gmirror will be smart enough to boot from ad0... but no luck, > I was forced to mount root filesystem with no mirror (ad0s1a) and run > the server in no mirror mode so I can have this critical machine running > while I find a new disk (few hours later I got it). > And the nightmare's just began... when I placed the new disk, the > gmirrored volume was still trying to sync from ad2, ofcourse, the ad2 > had no info on it (thanks god gmirror was smart enough to not copy the > empty disk). > I've had to rebuild the whole gmirror partiions, copy the info from a > non-mirrored disk (ad0) and etc.etc... you know the procedure... this > took me more than 10 hours and about 5hours downtime on a critical > machine.... Shocking story. huuu... I can't comment on that story though, because - at work, we're on Debian with hardware raids, no software raid even there - my own experiments with gmirror never lead to such a scenario. I should try to beat the disk to death, next time I test gmirror ;) > I suppose this has something to do with the priority in gmirror but I > don't have the broken disk to test - it's being replaced because it's in > warranty.... but anyways... 10 hours lost and 5hours downtime... > now I'm purchaseing a 3ware hw raid because I know that I can't trust > gmirror... > We don't trust LVM and co either. But don't ask me why. I believe it's more like a "feeling" than real facts. So I better don't start to discuss this matter. > Another strange thing, I've used to use apache22-worker cutom compiled > and thread_safe perl, the apache-worker stopped working on a jail (only > on one!) and I had to add replacements ot pthread.so in /etc/libmap, > I've been adviced not to use worker (as I did) but why the heck after > upgrading from 6.3-STABLE to 6.3-STABLE-p3 I got my apache broken and > also cron stopped working. To few facts. Never happened to me and without details I really can't comment. > strange uh? and all this is in only one jail (I'm using ez-jail to > update the world)... if anyone can help me to fix my cron without > reinstalling this jail I'd be thanksful! > You should open another mail thread on that topic and try to gather as much facts as you can. Cheers, Marian From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:20:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A97F106566B for ; Wed, 11 Jun 2008 16:20:03 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from crivens.kernel32.de (crivens.terrorteam.de [81.169.171.191]) by mx1.freebsd.org (Postfix) with ESMTP id DFBFB8FC1C for ; Wed, 11 Jun 2008 16:20:02 +0000 (UTC) (envelope-from mh@kernel32.de) Received: from www.terrorteam.de (localhost [127.0.0.1]) by crivens.kernel32.de (Postfix) with ESMTP id 1508EB0290; Wed, 11 Jun 2008 18:20:02 +0200 (CEST) MIME-Version: 1.0 Date: Wed, 11 Jun 2008 18:20:02 +0200 From: Marian Hettwer To: Robert Watson In-Reply-To: <20080611165009.O40102@fledge.watson.org> References: <20080611165009.O40102@fledge.watson.org> Message-ID: <97e6a5a3b509e35b8bfdab138ecf6b19@localhost> X-Sender: mh@kernel32.de User-Agent: RoundCube Webmail/0.1-rc2 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Cc: Andy Kosela , freebsd-stable@freebsd.org, lists@lozenetz.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy6.3 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, 11 Jun 2008 16:20:03 -0000 On Wed, 11 Jun 2008 16:54:02 +0100 (BST), Robert Watson wrote: > The place for volunteers to come in is where they see an obvious niche for > improvement -- for example, a few years ago this guy named Colin Percival > turned up with a binary update system. After a couple of years of > enhancement, breaking it in, etc, it's now a standard tool for maintaining > FreeBSD systems, and he's our security officer. Similar opportunities > exist > for offering easier updates to packages, etc, but require people who have > a > clear need and the technical ability to do the work to turn up and do it. > Very Well Spoken! :) Fact is, that it's okay to ask about a security branch for ports/packages. And if the answer is, no, we don't have enough manpower, then the road is clear. Either throw loads of money around you, or start doing it yourself and see wether someone hops on :) Cheers, ./Marian From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:41:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66B3F106567D for ; Wed, 11 Jun 2008 16:41:29 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.freebsd.org (Postfix) with ESMTP id 9D5928FC22 for ; Wed, 11 Jun 2008 16:41:27 +0000 (UTC) (envelope-from eugen@kuzbass.ru) Received: from www.svzserv.kemerovo.su (eugen@localhost [127.0.0.1]) by www.svzserv.kemerovo.su (8.13.8/8.13.8) with ESMTP id m5BGfOc0036689; Thu, 12 Jun 2008 00:41:24 +0800 (KRAST) (envelope-from eugen@www.svzserv.kemerovo.su) Received: (from eugen@localhost) by www.svzserv.kemerovo.su (8.13.8/8.13.8/Submit) id m5BGfNGY036688; Thu, 12 Jun 2008 00:41:23 +0800 (KRAST) (envelope-from eugen) Date: Thu, 12 Jun 2008 00:41:23 +0800 From: Eugene Grosbein To: Jeremy Chadwick Message-ID: <20080611164123.GA36521@svzserv.kemerovo.su> References: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> <20080611155420.GA65168@eos.sc1.parodius.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080611155420.GA65168@eos.sc1.parodius.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-stable Subject: Re: FreeBSD 7 and Apache 1.3.41 PROBLEM 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, 11 Jun 2008 16:41:29 -0000 On Wed, Jun 11, 2008 at 08:54:20AM -0700, Jeremy Chadwick wrote: > The problem in your error logs indicate some sort of issue relating to > the accept filter in FreeBSD, which Apache can use (accf_http). > > I don't think Apache 1.3.x has this functionality (rc-script-wise) It has. Eugene Grosbein From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 16:52:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7450C1065672 for ; Wed, 11 Jun 2008 16:52:25 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.177]) by mx1.freebsd.org (Postfix) with ESMTP id 255FF8FC14 for ; Wed, 11 Jun 2008 16:52:24 +0000 (UTC) (envelope-from jfvogel@gmail.com) Received: by py-out-1112.google.com with SMTP id p76so1475089pyb.10 for ; Wed, 11 Jun 2008 09:52:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=4CZz+RjpATxrplvNyIDq0c/BsrSqyJxtDzH1/elFkcE=; b=j/BdZ0aTo09vrD2INYsCBuVOxdHZfRSiBgzzc7jtPM5njjZj2QfJlu0Kq9Yyjdugk2 F1IwMEM1ht3Tl7Kcjb1qDp+xGYqYMSV39E+Qzc61q2uCFaku9P30dtKotxSikb5PLCcF PS4WLIQoPCZbNsK/Loq6n+PWsZxy3DQyF8k9M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=hWXuYB8G5lFCkHy9KJj+ECuRWL3C/6m2+qPolU8nAbvPNctvTlQIOyBR47fj2zUmFL SIeBub6K/xWO96NrvnOUFQ8ZhAlBIkSbKjBdP8AIeDlT2L0G7/lfejg3wuw3uPl5iGNA tErC8neptakdX2lYccZgeVdEUUMp1x4xk+8x4= Received: by 10.114.132.5 with SMTP id f5mr16189wad.201.1213203144069; Wed, 11 Jun 2008 09:52:24 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Wed, 11 Jun 2008 09:52:23 -0700 (PDT) Message-ID: <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> Date: Wed, 11 Jun 2008 09:52:23 -0700 From: "Jack Vogel" To: pyunyh@gmail.com In-Reply-To: <20080611073313.GF3529@cdnetworks.co.kr> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch 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, 11 Jun 2008 16:52:25 -0000 On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon wrote: > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > This is a small patch that Sam came up with for me, it will allow > > drivers to know > > when a vlan attaches. > > > > It is transparent to any code that doesn't want to change, but this > > will allow my > > drivers to finally utilize the vlan hardware filter (something Linux has had for > > ever but we lacked). > > > > Just curious, is there any rule how to use that new capability? > Because drivers will receive events whenever VLAN tags are > added/removed they would know how to act for these events. If > promiscuous mode is on for interface, driver should not filter any > VLAN tagged frames, right? > If users want to disable VLAN hardware filtering feature what is > best way to perform this? Introducing a new flag like > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > I guess VIA Rhine III also have VLAN hardware filtering capability > so it would be even better if we have a way to share common part. All the patch does is have the vlan driver generate events when it attaches or detaches from a NIC, there are no rules, however I can tell you what I'm coding into this in the Intel drivers. The way it works is the driver registers a callback for each event, I will call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. Right now, the drivers just generically enable VLAN capability because there is never a trigger to know IF and WHEN you need to do so, but with this change the VLAN capability will only get turned on by the registration routine. Most significantly, now when the pseudo device it gives the driver the VLAN tag, this will mean the driver will be able from the start to use the VFTA, the hardware filter, for each vlan attach the driver will add the ID into this table. The unregister event will turn the table entry off, and if this is the last VLAN being detached it will then disable the features. Oh yes, these routines will also take care of the size change of the frame due to the tag. I already have the changes in place in the igb drive, and they are working great. I do not understand why you think you need a flag to disable this, yes it could be done, but why? If you need to do some sort of debugging won't a system not using vlans and in promiscuous mode do just fine? It just seems to violate the whole reason for doing vlans in the first place, however perhaps I am missing something? I do not believe the Linux driver has some way to disable use of the table but I'll double check on that. Remember, this change requires NO driver changes unless they wish to take advantage of the ability. Cheers, Jack From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 17:07:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18BFF106564A; Wed, 11 Jun 2008 17:07:16 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (wojtek.tensor.gdynia.pl [IPv6:2001:4070:101:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2F2108FC12; Wed, 11 Jun 2008 17:07:10 +0000 (UTC) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from wojtek.tensor.gdynia.pl (localhost [IPv6:::1]) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2) with ESMTP id m5BH6u7O060947; Wed, 11 Jun 2008 19:06:57 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Received: from localhost (wojtek@localhost) by wojtek.tensor.gdynia.pl (8.14.2/8.14.2/Submit) with ESMTP id m5BH6tF9060944; Wed, 11 Jun 2008 19:06:56 +0200 (CEST) (envelope-from wojtek@wojtek.tensor.gdynia.pl) Date: Wed, 11 Jun 2008 19:06:54 +0200 (CEST) From: Wojciech Puchar To: Jack Raats In-Reply-To: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> Message-ID: <20080611190609.H60134@wojtek.tensor.gdynia.pl> References: <087EAA726CFA4573BF9B39E69A5F3AE8@jarasoft.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable , freebsd-questions@freebsd.org Subject: Re: FreeBSD 7 and Apache 1.3.41 PROBLEM 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, 11 Jun 2008 17:07:16 -0000 > In httpd-error.log > [Wed Jun 11 17:01:04 2008] [info] mod_unique_id: using ip addr 10.10.10.10 > [Wed Jun 11 17:01:05 2008] [info] (2)No such file or directory: make_sock: for port 80, setsockopt: (SO_ACCEPTFILTER) > [Wed Jun 11 17:01:05 2008] [warn] pid file /var/run/httpd.pid overwritten -- Unclean shutdown of previous Apache run? > > After hashing out > #LoadModule unique_id_module libexec/apache/mod_unique_id.so > #AddModule mod_unique_id.c > > Apache starts normally > > Can anyone explain this? are you sure you use the same apache version as with 6.*? From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 18:03:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 000BF1065682 for ; Wed, 11 Jun 2008 18:03:08 +0000 (UTC) (envelope-from bsdlist@cogeco.ca) Received: from fep5.cogeco.net (smtp.cogeco.net [216.221.81.25]) by mx1.freebsd.org (Postfix) with ESMTP id CCB888FC0A for ; Wed, 11 Jun 2008 18:03:08 +0000 (UTC) (envelope-from bsdlist@cogeco.ca) Received: from elehost-can.cogeco.ca (d36-192-94.home1.cgocable.net [24.36.192.94]) by fep5.cogeco.net (Postfix) with ESMTP id A899C1E9E for ; Wed, 11 Jun 2008 13:32:11 -0400 (EDT) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 11 Jun 2008 13:32:42 -0400 To: freebsd-stable@freebsd.org From: Paul Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-Id: <20080611173211.A899C1E9E@fep5.cogeco.net> Subject: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 11 Jun 2008 18:03:09 -0000 Hello, I have a RAID-6 Partition with the Areca ARC-1231 card on a S5000PAL Intel system with 6 disks as part of the raid volume. The system has been set up as Write-back cache and the raid card has a 2 GIG memory cache on it. It is installed on Freebsd 7.0 STABLE with SCHED_ULE enabled. I have a folder with a lot of small and big files in it that total 3009 files. In the user system we have 2200 users in the password file. 1) When I do a ls -lh on the raid 6 array with 6 disks in the array it takes aver 16 seconds before it starts to display anything on the screen. 2) While running a tar command on another shell, the time goes to 28 seconds for the same list to start showing. 3) When I do a ls (with no other options) it starts to list right away. 4) When I do a ls -ln it displays right away as well pointing to the slowdown being the mapping of the users in the db lookup. I have the same directory with the same number of files on a Raid 5 SCSI partition on Freebsd 4.X and it only takes 2 seconds to start displaying the list with the command ls -lh. Any ideas why it takes so long for this on Freebsd 7.0 stable? The partition this folder is on it /dev/da0s1f with a total size of 1.7T and a usage of 63G Any suggestions or help on this would be greatly appreciated. Thanks, Paul From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 18:22:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D41281065675 for ; Wed, 11 Jun 2008 18:22:36 +0000 (UTC) (envelope-from prvs=pschmehl_lists=041eb2bf1@tx.rr.com) Received: from ip-relay-002.utdallas.edu (ip-relay-002.utdallas.edu [129.110.20.112]) by mx1.freebsd.org (Postfix) with ESMTP id 9DC998FC1E for ; Wed, 11 Jun 2008 18:22:36 +0000 (UTC) (envelope-from prvs=pschmehl_lists=041eb2bf1@tx.rr.com) X-IronPort-AV: E=Sophos;i="4.27,625,1204524000"; d="scan'208";a="1441938" Received: from smtp3.utdallas.edu ([129.110.20.110]) by ip-relay-002.utdallas.edu with ESMTP; 11 Jun 2008 12:54:02 -0500 Received: from utd65257.utdallas.edu (utd65257.utdallas.edu [129.110.3.28]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp3.utdallas.edu (Postfix) with ESMTPSA id 4A6BD23DEA; Wed, 11 Jun 2008 12:54:02 -0500 (CDT) Date: Wed, 11 Jun 2008 12:54:02 -0500 From: Paul Schmehl To: freebsd-stable@freebsd.org Message-ID: <4E2C3BF30A4BC75D1D837828@utd65257.utdallas.edu> In-Reply-To: <20080611165009.O40102@fledge.watson.org> References: <484FA07E.60103@lozenetz.org> <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> <20080611165009.O40102@fledge.watson.org> X-Mailer: Mulberry/4.0.6 (Linux/x86) X-Munged-Reply-To: Figure it out MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: mh@kernel32.de Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Paul Schmehl List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 18:22:36 -0000 --On Wednesday, June 11, 2008 16:54:02 +0100 Robert Watson wrote: > > On Wed, 11 Jun 2008, Andy Kosela wrote: > >> Redhat/CentOS is more reliable here as backports involves both security and >> bug fixes, plus even new hardware enhancements. > > In the FreeBSD environment, we call the place that gets a blend of security > and bug fixes, plus new minor feature and driver enhancements "-STABLE", and > the releases that pick up these changes "point releases". They happen more > requently and with less risk than major releases, but still see enough > development to represent functional improvements. > > I guess here's my concern: we offer a spectrum of choice for "I want the most > bleeding edge" to "I want no feature changes, just security fixes", and > several points in between. We can argue about the exact placement of this > points, but the reality is that the balance we have today seems to work well > for many developers and users, and reflects a fairly carefully planned use of > the available revision control and distribution technology. > > The place for volunteers to come in is where they see an obvious niche for > improvement -- for example, a few years ago this guy named Colin Percival > turned up with a binary update system. After a couple of years of > enhancement, breaking it in, etc, it's now a standard tool for maintaining > FreeBSD systems, and he's our security officer. Similar opportunities exist > for offering easier updates to packages, etc, but require people who have a > clear need and the technical ability to do the work to turn up and do it. > >From a security standport, backporting fixes to previous versions of ports creates a difficulty. It's much harder to tell, for example, if a RedHat "port" is vulnerable or not, because RedHat uses their own proprietary versioning system to define "where" a particular "port" is at. So, while your system might *say* it's running php version 5.2, it's really *not* vulnerable because in RedHatese it's version 5.2.1.6.92000.p-2.1 (I'm just making that up.) If this idea ever gets off the ground, I *hope* the folks involved with find a rational, logical way to define the versioning so that it's not hieroglyphics to the average person. -- Paul Schmehl As if it wasn't already obvious, my opinions are my own and not those of my employer. From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 18:36:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA5B61065675 for ; Wed, 11 Jun 2008 18:36:29 +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 77AA88FC0C for ; Wed, 11 Jun 2008 18:36:29 +0000 (UTC) (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 E98C246C4A; Wed, 11 Jun 2008 14:36:28 -0400 (EDT) Date: Wed, 11 Jun 2008 19:36:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Paul Schmehl In-Reply-To: <4E2C3BF30A4BC75D1D837828@utd65257.utdallas.edu> Message-ID: <20080611193123.N40102@fledge.watson.org> References: <484FA07E.60103@lozenetz.org> <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> <20080611165009.O40102@fledge.watson.org> <4E2C3BF30A4BC75D1D837828@utd65257.utdallas.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org, mh@kernel32.de Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 18:36:29 -0000 On Wed, 11 Jun 2008, Paul Schmehl wrote: > From a security standport, backporting fixes to previous versions of ports > creates a difficulty. It's much harder to tell, for example, if a RedHat > "port" is vulnerable or not, because RedHat uses their own proprietary > versioning system to define "where" a particular "port" is at. > > So, while your system might *say* it's running php version 5.2, it's really > *not* vulnerable because in RedHatese it's version 5.2.1.6.92000.p-2.1 (I'm > just making that up.) > > If this idea ever gets off the ground, I *hope* the folks involved with find > a rational, logical way to define the versioning so that it's not > hieroglyphics to the average person. I hope not to offend the ports folks in saying this, but it seems clear to me that the narrower scope and better-defined components of the base system have (over time) lead to a much easier incremental upgrade path than ports and packages. It's not clear to me how you could apply the same level of attention to something as large as the ports collection, except perhaps to select a subset of ports you care "more" about, and provide a higher quality of service for them. In effect, try to find a semantically richer middle ground between "it's someone else's problem, our role is primarily to bundle" and "it's entirely our problem and in revision control". We already do this for some ports, in that the people involved in adapting and maintaining some of the larger/more critical parts, such as X.org, KDE, Gnome, and quite a few others, spend vast amounts of time ensuring that things work well, but largely without the help of revision control in the ports tree. I'm not proposing we incorporate X.org into CVS (SVN?) or the like, but perhaps there is a way we could better present the choices reflected there. That doesn't help users of random tiny software packages, and I'm not sure anything can, but perhaps we can provide a smoother incremental maintenance path for some key packages. Mind you, ports really isn't my area, so I am at significant risk speculating in this area. Experience with the base system shows that the real work is always in the details, and hardly ever in the big ideas, and so only by truly implementing a system and trying it out can you determine whether it really works in practice. It's easy to wave ones hands at a high level (as I've done), but it's the proof-of-concept that matters. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 18:50:44 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24C5A1065670 for ; Wed, 11 Jun 2008 18:50:44 +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 DB4078FC1D for ; Wed, 11 Jun 2008 18:50:43 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5BIBNwQ088186; Wed, 11 Jun 2008 14:11:23 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m5BIBMkl074039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 14:11:23 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200806111811.m5BIBMkl074039@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 11 Jun 2008 14:11:23 -0400 To: Paul , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20080611173211.A899C1E9E@fep5.cogeco.net> References: <20080611173211.A899C1E9E@fep5.cogeco.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 11 Jun 2008 18:50:44 -0000 At 01:32 PM 6/11/2008, Paul wrote: >Any ideas why it takes so long for this on Freebsd 7.0 stable? > >The partition this folder is on it /dev/da0s1f with a total size of >1.7T and a usage of 63G > >Any suggestions or help on this would be greatly appreciated. Couple of things to check In /etc/nsswitch.conf try changing to group: files passwd: files and check to make sure vfs.ufs.dirhash_maxmem is > than vfs.ufs.dirhash_mem. If vfs.ufs.dirhash_mem is hit the max, increase the maxmem value ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 19:36:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D9EC2106567B; Wed, 11 Jun 2008 19:36:29 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (in-addr.broker.freenet6.net [IPv6:2001:5c0:8fff:fffe::214d]) by mx1.freebsd.org (Postfix) with ESMTP id 8BCFD8FC1E; Wed, 11 Jun 2008 19:36:29 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by noop.in-addr.com with local (Exim 4.54 (FreeBSD)) id 1K6W7Q-000Bcm-Jy; Wed, 11 Jun 2008 15:36:28 -0400 Date: Wed, 11 Jun 2008 15:36:28 -0400 From: Gary Palmer To: Robert Watson Message-ID: <20080611193628.GC998@in-addr.com> References: <484FA07E.60103@lozenetz.org> <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> <20080611165009.O40102@fledge.watson.org> <4E2C3BF30A4BC75D1D837828@utd65257.utdallas.edu> <20080611193123.N40102@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080611193123.N40102@fledge.watson.org> Cc: freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 19:36:30 -0000 On Wed, Jun 11, 2008 at 07:36:28PM +0100, Robert Watson wrote: > > On Wed, 11 Jun 2008, Paul Schmehl wrote: > > >From a security standport, backporting fixes to previous versions of ports > >creates a difficulty. It's much harder to tell, for example, if a RedHat > >"port" is vulnerable or not, because RedHat uses their own proprietary > >versioning system to define "where" a particular "port" is at. > > > >So, while your system might *say* it's running php version 5.2, it's > >really *not* vulnerable because in RedHatese it's version > >5.2.1.6.92000.p-2.1 (I'm just making that up.) > > > >If this idea ever gets off the ground, I *hope* the folks involved with > >find a rational, logical way to define the versioning so that it's not > >hieroglyphics to the average person. > > I hope not to offend the ports folks in saying this, but it seems clear to > me that the narrower scope and better-defined components of the base system > have (over time) lead to a much easier incremental upgrade path than ports > and packages. > > It's not clear to me how you could apply the same level of attention to > something as large as the ports collection, except perhaps to select a > subset of ports you care "more" about, and provide a higher quality of > service for them. In effect, try to find a semantically richer middle > ground between "it's someone else's problem, our role is primarily to > bundle" and "it's entirely our problem and in revision control". We > already do this for some ports, in that the people involved in adapting and > maintaining some of the larger/more critical parts, such as X.org, KDE, > Gnome, and quite a few others, spend vast amounts of time ensuring that > things work well, but largely without the help of revision control in the > ports tree. I'm not proposing we incorporate X.org into CVS (SVN?) or the > like, but perhaps there is a way we could better present the choices > reflected there. That doesn't help users of random tiny software packages, > and I'm not sure anything can, but perhaps we can provide a smoother > incremental maintenance path for some key packages. > > Mind you, ports really isn't my area, so I am at significant risk > speculating in this area. Experience with the base system shows that the > real work is always in the details, and hardly ever in the big ideas, and > so only by truly implementing a system and trying it out can you determine > whether it really works in practice. It's easy to wave ones hands at a > high level (as I've done), but it's the proof-of-concept that matters. I think a large part of the shortcomings of the ports infrastructure when it comes to security releases could be mitigated if there was a rapid building and availability of packages on FTP mirrors to prevent everyone from doing "portupgrade -P" and then having to wait for the build as the packages don't show up for days, and people can't wait that long for the fix. I know a discussion was recently started about package distribution and how to address its shortcomings and hopefully the need for rapid security package distribution will be taken into account Regards, Gary From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 19:53:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D7A6106567C for ; Wed, 11 Jun 2008 19:53:50 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx23.fluidhosting.com [204.14.89.6]) by mx1.freebsd.org (Postfix) with ESMTP id B7D738FC29 for ; Wed, 11 Jun 2008 19:53:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: (qmail 17631 invoked by uid 399); 11 Jun 2008 19:53:49 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 11 Jun 2008 19:53:49 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <48502D4B.3040201@FreeBSD.org> Date: Wed, 11 Jun 2008 12:53:47 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 2.0.0.14 (X11/20080606) MIME-Version: 1.0 To: Gary Palmer References: <484FA07E.60103@lozenetz.org> <3cc535c80806110536w1c8af6efq8d5470ce6de8cb38@mail.gmail.com> <20080611165009.O40102@fledge.watson.org> <4E2C3BF30A4BC75D1D837828@utd65257.utdallas.edu> <20080611193123.N40102@fledge.watson.org> <20080611193628.GC998@in-addr.com> In-Reply-To: <20080611193628.GC998@in-addr.com> X-Enigmail-Version: 0.95.6 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, Robert Watson Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 11 Jun 2008 19:53:50 -0000 Gary Palmer wrote: > I think a large part of the shortcomings of the ports infrastructure when > it comes to security releases could be mitigated if there was a rapid > building and availability of packages on FTP mirrors to prevent everyone > from doing "portupgrade -P" and then having to wait for the build as > the packages don't show up for days, and people can't wait that long > for the fix. I raised that issue recently on freebsd-ports@ and was told that there are no resources for that right now, although everyone agreed that it is definitely something that would be nice-to-have. Doug -- This .signature sanitized for your protection From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 20:03:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C91B7106564A for ; Wed, 11 Jun 2008 20:03:43 +0000 (UTC) (envelope-from bsdlist@cogeco.ca) Received: from fep1.cogeco.net (smtp.cogeco.net [216.221.81.25]) by mx1.freebsd.org (Postfix) with ESMTP id A01238FC22 for ; Wed, 11 Jun 2008 20:03:43 +0000 (UTC) (envelope-from bsdlist@cogeco.ca) Received: from elehost-can.cogeco.ca (d36-192-94.home1.cgocable.net [24.36.192.94]) by fep1.cogeco.net (Postfix) with ESMTP id A53901DEF for ; Wed, 11 Jun 2008 16:03:42 -0400 (EDT) X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 11 Jun 2008 16:04:18 -0400 To: freebsd-stable@freebsd.org From: Paul In-Reply-To: <200806111811.m5BIBMkl074039@lava.sentex.ca> References: <20080611173211.A899C1E9E@fep5.cogeco.net> <200806111811.m5BIBMkl074039@lava.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Message-Id: <20080611200342.A53901DEF@fep1.cogeco.net> Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 11 Jun 2008 20:03:43 -0000 At 02:11 PM 11/06/2008, Mike Tancsa wrote: >>Any ideas why it takes so long for this on Freebsd 7.0 stable? >> >>The partition this folder is on it /dev/da0s1f with a total size >>of 1.7T and a usage of 63G >> >>Any suggestions or help on this would be greatly appreciated. > >Couple of things to check > >In /etc/nsswitch.conf try changing to > >group: files >passwd: files > >and check to make sure >vfs.ufs.dirhash_maxmem is > than vfs.ufs.dirhash_mem. If >vfs.ufs.dirhash_mem is hit the max, increase the maxmem value > > ---Mike Thanks a lot for the quick reply. Changing from compat to files fixes the problem. It is now superfast when running ls -lh. Thanks again! Cheers Paul From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 20:15:57 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4DAF106564A for ; Wed, 11 Jun 2008 20:15:57 +0000 (UTC) (envelope-from pgollucci@p6m7g8.com) Received: from EXHUB015-4.exch015.msoutlookonline.net (exhub015-4.exch015.msoutlookonline.net [207.5.72.96]) by mx1.freebsd.org (Postfix) with ESMTP id B954A8FC20 for ; Wed, 11 Jun 2008 20:15:57 +0000 (UTC) (envelope-from pgollucci@p6m7g8.com) Received: from philip.hq.rws (74.93.213.161) by smtpx15.msoutlookonline.net (207.5.72.103) with Microsoft SMTP Server (TLS) id 8.1.278.0; Wed, 11 Jun 2008 13:05:54 -0700 Message-ID: <48503020.7010600@p6m7g8.com> Date: Wed, 11 Jun 2008 16:05:52 -0400 From: "Philip M. Gollucci" Organization: P6M7G8 Consulting User-Agent: Thunderbird 2.0.0.12 (X11/20080414) MIME-Version: 1.0 To: Jordi Espasa Clofent References: <4846B64F.4090700@minibofh.org> <484775D4.4090509@p6m7g8.com> <48481A02.2050502@minibofh.org> <484FF478.8010405@minibofh.org> In-Reply-To: <484FF478.8010405@minibofh.org> X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 11 Jun 2008 20:15:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordi Espasa Clofent wrote: | It seems a php-extensions bug. | If you comment the mhash.so in /usr/local/etc/php/extensions.ini as: | | ;entension=mhash.so | | all works fine and you don't get anymore httpd crash (signal 11) if you | use 'apachectl graceful'. | | Maybe will be a good idea to open PR for this? | | I hope it helps someone.... (I'm very surprised that this isn't a | documented bug in 7.0 yet) It might make more sense to follow up with php..... Just b/c it happens in 7.x and not 6.x doesn't mean its a FreeBSD issue. - -- - ------------------------------------------------------------------------ Philip M. Gollucci (philip@ridecharge.com) o:703.549.2050x206 Senior System Admin - Riderway, Inc. http://riderway.com / http://ridecharge.com 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C Work like you don't need the money, love like you'll never get hurt, and dance like nobody's watching. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQFIUDAgdbiP+9ubjBwRAskiAJ993ELYL3AP5HkVtDSk2JQx9OuJzACfdORO rnTL1Ecdd4MNwlcrNKhwLYM= =lX0o -----END PGP SIGNATURE----- From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 20:26:39 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFD1C106567E for ; Wed, 11 Jun 2008 20:26:39 +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 91FAD8FC22 for ; Wed, 11 Jun 2008 20:26:39 +0000 (UTC) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by smarthost1.sentex.ca (8.14.2/8.14.2) with ESMTP id m5BKQbR7020986; Wed, 11 Jun 2008 16:26:37 -0400 (EDT) (envelope-from mike@sentex.net) Received: from mdt-xp.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.8/8.13.3) with ESMTP id m5BKQaOB074653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 11 Jun 2008 16:26:36 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <200806112026.m5BKQaOB074653@lava.sentex.ca> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Wed, 11 Jun 2008 16:26:37 -0400 To: Paul , freebsd-stable@freebsd.org From: Mike Tancsa In-Reply-To: <20080611200342.A53901DEF@fep1.cogeco.net> References: <20080611173211.A899C1E9E@fep5.cogeco.net> <200806111811.m5BIBMkl074039@lava.sentex.ca> <20080611200342.A53901DEF@fep1.cogeco.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Scanned-By: MIMEDefang 2.64 on 64.7.153.18 Cc: Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 11 Jun 2008 20:26:39 -0000 At 04:04 PM 6/11/2008, Paul wrote: >Changing from compat to files fixes the problem. > >It is now superfast when running ls -lh. Hi, Not sure, but a more "proper" fix might be to look at the nscd caching daemon. Take a look at nscd and nscd.conf. I havent used it myself, but I seem to recall others suggesting this as a "fix" as well. ---Mike From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 20:50:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67B8B1065673 for ; Wed, 11 Jun 2008 20:50:36 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.180]) by mx1.freebsd.org (Postfix) with ESMTP id 37E028FC21 for ; Wed, 11 Jun 2008 20:50:35 +0000 (UTC) (envelope-from andy.kosela@gmail.com) Received: by wa-out-1112.google.com with SMTP id j4so2417901wah.3 for ; Wed, 11 Jun 2008 13:50:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:mime-version:content-type:content-transfer-encoding :content-disposition; bh=Zb9/L4v9Nb4+yyC9t/lNAGdF7R23l5aFNyMsnKZY5Lg=; b=anIOgRmMZIIOJQm8EChEZhOFrLIJi0Ep99hu1u2LPJfmHoJNRbUwPvUIUUkKaasD84 JixuqN+v1jHk4100TSq35sA8W4YjEh4bYfu6JdD0sQshugrQlLTMBP/JSM4WRtEQbdwn DRul0UmL+1tJjXe0U7xpIrKO67vm0IBkXXLmI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:mime-version:content-type :content-transfer-encoding:content-disposition; b=M9+i8C01NVYLYqAdNQN5h03Ly9s9HPD0WPi7lURujCMBBGBEmoUpUOe2fCY2N3QMrJ 6a0EhlkKTN69iJbQWL+pxpVox0vrcvF0KkAnHv8scI5r9G/iGweYOvEJFO26/u8qT9kv +YJbL9wQxzyK+JtZoLQVsENUn1UE/DTDBbB7Y= Received: by 10.114.159.6 with SMTP id h6mr509670wae.65.1213217435043; Wed, 11 Jun 2008 13:50:35 -0700 (PDT) Received: by 10.114.112.6 with HTTP; Wed, 11 Jun 2008 13:50:34 -0700 (PDT) Message-ID: <3cc535c80806111350x237e2a4ewe1429b7a3f5b720@mail.gmail.com> Date: Wed, 11 Jun 2008 22:50:34 +0200 From: "Andy Kosela" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Cc: pschmehl_lists@tx.rr.com, rwatson@freebsd.org Subject: CLARITY re: challenge: end of life for 6.2 is premature withbuggy 6.3 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, 11 Jun 2008 20:50:36 -0000 On Wed, Jun 11 2008, Robert Watson wrote: On Wed, 11 Jun 2008, Paul Schmehl wrote: >> From a security standport, backporting fixes to previous versions of ports >> creates a difficulty. It's much harder to tell, for example, if a RedHat >> "port" is vulnerable or not, because RedHat uses their own proprietary >> versioning system to define "where" a particular "port" is at. >> >> So, while your system might *say* it's running php version 5.2, it's really >> *not* vulnerable because in RedHatese it's version 5.2.1.6.92000.p-2.1 (I'm >> just making that up.) >> >> If this idea ever gets off the ground, I *hope* the folks involved with find >> a rational, logical way to define the versioning so that it's not >> hieroglyphics to the average person. Egyptian hieroglyphics was a very noble system the secret of which was, in the days of old, in the possession only of the Hierogrammatists, or initiated Egyptian priests. Many occult alphabets and ciphers derived its origin from egyptian sacred ciphers, as also everything we know as cryptography today. I guess our english alphabet would be equally strange and uknown to them. But reading widely available documentation on Redhat's versioning system would definetly help in understanding its details. Everything after second - (dash) like in ftp-0.17-33 is Redhat's release version. In this case this is thirty third release or patch. It is similar to FreeBSD's naming convention. You can check changelog and see what has changed since release 1 by issuing: $ rpm -q --changelog So the system is very clear and precise, just like FreeBSD system. The only difference is that upstream version of the package changes a lot more often than on redhat/centos. > We already do this for some >ports, in that the people involved in adapting and maintaining some of the >larger/more critical parts, such as X.org, KDE, Gnome, and quite a few others, >spend vast amounts of time ensuring that things work well, but largely without >the help of revision control in the ports tree. I'm not proposing we >incorporate X.org into CVS (SVN?) or the like, but perhaps there is a way we >could better present the choices reflected there. That doesn't help users of >random tiny software packages, and I'm not sure anything can, but perhaps we >can provide a smoother incremental maintenance path for some key packages. I think that most system administrators who maintain many FreeBSD servers in data center environments do not really care about "X.org, KDE, Gnome" and other desktop applications having those -SECURITY patches backported. The real concern here is about common server applications. I think that cutting edge users who run FreeBSD on their workstations are perfectly aware that things can sometimes break, and to a degree they accept that risk. But system administrators running mission critical nonstop systems 24/7 cannot accept such risk with the server ports they are using. So if anything can be improved in ease of upgrading, backporting etc. this is the main area to investigate, so as to make FreeBSD the most stable and reliable Unix operating system out there. -- Andy Kosela ora et labora From owner-freebsd-stable@FreeBSD.ORG Wed Jun 11 22:10:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 481891065677 for ; Wed, 11 Jun 2008 22:10:05 +0000 (UTC) (envelope-from newsletter@purecomponents.com) Received: from purecomp.purecomponents.com (purecomponents.cust.ignum.cz [217.31.51.48]) by mx1.freebsd.org (Postfix) with ESMTP id AEF258FC12 for ; Wed, 11 Jun 2008 22:10:04 +0000 (UTC) (envelope-from newsletter@purecomponents.com) Received: from purecomponents.com ([127.0.0.1]) by purecomp.purecomponents.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 11 Jun 2008 23:26:18 +0200 From: "PureComponents Newsletter" To: freebsd-stable@freebsd.org Message-ID: Date: Wed, 11 Jun 2008 23:26:18 +0200 Page-id: f667265656273642d737461626c6540667265656273642e6f7267e MIME-Version: 1.0 X-OriginalArrivalTime: 11 Jun 2008 21:26:18.0539 (UTC) FILETIME=[C960B7B0:01C8CC09] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: PureComponents Ultimate Suite V2008.1 - 79 .NET WinForms Components for $79 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: PureComponents Sales List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Jun 2008 22:10:05 -0000 PureComponents Ultimate Suite V2008=2E1 - The cheapest component suite = there is! PureComponents offer you component suite for excellent price of 1 USD p= er component=2E Purchase the set of 79 components for 79 USD=2E Purchase 1 year subscription by June 30, and save 30%! http://www=2Epurecomponents=2Ecom/ -----------------------------------------------------------------------= ------------------------------------------------- If you would not like to receive these messages, please visit: http://www=2Epurecomponents=2Ecom/unsubscribe=2Easpx From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 00:11:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8AC0C1065671 for ; Thu, 12 Jun 2008 00:11:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.231]) by mx1.freebsd.org (Postfix) with ESMTP id 4B7668FC21 for ; Thu, 12 Jun 2008 00:11:53 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4044891rvf.43 for ; Wed, 11 Jun 2008 17:11:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=+liliLsBgAr2ccjerdXDwDsBUZbdULe8sqQjoUiiA9w=; b=oYxeOVt9Y0FeHwoQ0O7jn+scK0RJOzxJmYwnlneDaV8J9qSf3j1+u1YXaGjk3aLOVj FmQzHYRHP8N7zVhZgA4CqYvsAverCng1KVD8Svwh0XP9lpVbxjlWhEp0ON4ZcAa5HY1O 9aaUnjrmgm09QlEWOcLwHyxZP6CjewgFGDaHQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=kgvGrmg9IWd3yOAv80ytbPBk/mKmaaGu4NMueQLuaUtTXLBeVK6O7kAaKFTyuhohQB 0bZ2CuM2qaI90f5BrQrTrXeRiWoe/lPbwOpVp2gJRTOZGOH/bMkJ6SxvXp/OV3Ebp2A7 pBGpGhD3zEkU2V62vDnZpUtaW8aXhbj9nhzrM= Received: by 10.141.71.14 with SMTP id y14mr468893rvk.24.1213229513601; Wed, 11 Jun 2008 17:11:53 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id b8sm686167rvf.9.2008.06.11.17.11.50 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 17:11:52 -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 m5C09iEU007424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 09:09:44 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5C09h3E007423; Thu, 12 Jun 2008 09:09:43 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 12 Jun 2008 09:09:43 +0900 From: Pyun YongHyeon To: Jack Vogel Message-ID: <20080612000943.GA7250@cdnetworks.co.kr> References: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com> <20080611073313.GF3529@cdnetworks.co.kr> <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2a41acea0806110952n2851415dyf3b3213249779bf1@mail.gmail.com> User-Agent: Mutt/1.4.2.1i Cc: "freebsd-net@freebsd.org" , FreeBSD Current , FreeBSD Stable List Subject: Re: Vlan EVENT patch 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: Thu, 12 Jun 2008 00:11:54 -0000 On Wed, Jun 11, 2008 at 09:52:23AM -0700, Jack Vogel wrote: > On Wed, Jun 11, 2008 at 12:33 AM, Pyun YongHyeon wrote: > > On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote: > > > This is a small patch that Sam came up with for me, it will allow > > > drivers to know > > > when a vlan attaches. > > > > > > It is transparent to any code that doesn't want to change, but this > > > will allow my > > > drivers to finally utilize the vlan hardware filter (something Linux has had for > > > ever but we lacked). > > > > > > > Just curious, is there any rule how to use that new capability? > > Because drivers will receive events whenever VLAN tags are > > added/removed they would know how to act for these events. If > > promiscuous mode is on for interface, driver should not filter any > > VLAN tagged frames, right? > > If users want to disable VLAN hardware filtering feature what is > > best way to perform this? Introducing a new flag like > > IFCAP_VLAN_HWFILT or add a new sysctl that control this feature? > > I guess VIA Rhine III also have VLAN hardware filtering capability > > so it would be even better if we have a way to share common part. > > All the patch does is have the vlan driver generate events when it attaches > or detaches from a NIC, there are no rules, however I can tell you what > I'm coding into this in the Intel drivers. > > The way it works is the driver registers a callback for each event, I will > call that [igb,em,ixgbe]_register_vlan(), and unregister obviously. > > Right now, the drivers just generically enable VLAN capability because > there is never a trigger to know IF and WHEN you need to do so, but > with this change the VLAN capability will only get turned on by the > registration routine. > > Most significantly, now when the pseudo device it gives the driver > the VLAN tag, this will mean the driver will be able from the start > to use the VFTA, the hardware filter, for each vlan attach the driver > will add the ID into this table. > > The unregister event will turn the table entry off, and if this is the > last VLAN being detached it will then disable the features. > > Oh yes, these routines will also take care of the size change of > the frame due to the tag. I already have the changes in place in > the igb drive, and they are working great. > > I do not understand why you think you need a flag to disable this, > yes it could be done, but why? If you need to do some sort of > debugging won't a system not using vlans and in promiscuous > mode do just fine? > I guess this would be the same reason why FreeBSD have a way to disable checksum offload for buggy hardware. Diabling all hardware VLAN assistance due to broken VLAN filtering doesn't look right. > It just seems to violate the whole reason for doing vlans in the > first place, however perhaps I am missing something? I do not > believe the Linux driver has some way to disable use of the table > but I'll double check on that. > > Remember, this change requires NO driver changes unless they > wish to take advantage of the ability. Yes. > > Cheers, > > Jack Thanks. -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 01:46:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 300CE1065679 for ; Thu, 12 Jun 2008 01:46:31 +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 7F8368FC2A for ; Thu, 12 Jun 2008 01:46:30 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C1kNii083187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 11:16:23 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 12 Jun 2008 11:16:20 +0930 User-Agent: KMail/1.9.7 References: <20080611173211.A899C1E9E@fep5.cogeco.net> <20080611200342.A53901DEF@fep1.cogeco.net> <200806112026.m5BKQaOB074653@lava.sentex.ca> In-Reply-To: <200806112026.m5BKQaOB074653@lava.sentex.ca> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3634284.SzPfiIiOag"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121116.21657.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Paul Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 12 Jun 2008 01:46:31 -0000 --nextPart3634284.SzPfiIiOag Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Mike Tancsa wrote: > At 04:04 PM 6/11/2008, Paul wrote: > >Changing from compat to files fixes the problem. > > > >It is now superfast when running ls -lh. > > Hi, > Not sure, but a more "proper" fix might be to look at the > nscd caching daemon. Take a look at nscd and nscd.conf. I havent used > it myself, but I seem to recall others suggesting this as a "fix" as > well. Why is 'compat' so slow? (ie what's the difference between it and file=20 anyway) =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 --nextPart3634284.SzPfiIiOag Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUH/t5ZPcIHs/zowRAkUrAJ9uqCqTgPoJJ6hv8WBu1eqNSRf2bwCgjSmG X7jjUsDRyNj3PtvXwzHGf/8= =er3k -----END PGP SIGNATURE----- --nextPart3634284.SzPfiIiOag-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 01:48:49 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCEBF1065681; Thu, 12 Jun 2008 01:48:49 +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 1620B8FC17; Thu, 12 Jun 2008 01:48:48 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C1mjLv083249 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 11:18:46 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-stable@freebsd.org Date: Thu, 12 Jun 2008 11:18:43 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <484FF478.8010405@minibofh.org> <20080611161048.GA66773@eos.sc1.parodius.com> In-Reply-To: <20080611161048.GA66773@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1291148.QBSeYktV6V"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121118.45137.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Jordi Espasa Clofent , Jeremy Chadwick , freebsd-apache@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 01:48:49 -0000 --nextPart1291148.QBSeYktV6V Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > I myself haven't ever run into extension ordering issues like those > described (and we've done hosting for years), but I don't doubt those > who have experienced such. I am currently experiencing this :( In the past I shuffled the order until it worked but that's not a real=20 solution. Also if you have gone from 6.x to 7.x make sure that you don't have any=20 old stuff linked against libc.so.6 loaded into a binary using=20 libc.so.7. It mostly works except with threaded programs and then *kaboom* =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 --nextPart1291148.QBSeYktV6V Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUIB95ZPcIHs/zowRAvA7AJ0V0DCyB1YPyZ97wM+KBtCxwYSA8ACfQoiM 123kv9/sYA38RlXO36/jEc8= =KYue -----END PGP SIGNATURE----- --nextPart1291148.QBSeYktV6V-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 02:24:51 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B40F51065672 for ; Thu, 12 Jun 2008 02:24:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.233]) by mx1.freebsd.org (Postfix) with ESMTP id 7F51B8FC14 for ; Thu, 12 Jun 2008 02:24:51 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4096245rvf.43 for ; Wed, 11 Jun 2008 19:24:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=xmIemrNMsacqWHKpPhEV5rMq9wXvdr07eTk1jJiwd/U=; b=alKkenkTXqldgc7AExe2yF9Yq9EyH7CHPHJnyHsLapidWT+vse7QWNETuHObymDcvM 4Nfq2Ka/T9fFrPXQE9d30QFA2GsVN8qZlXCucMts2+XcdcijgMFNLD7ezUvSE8mSicb6 8P3Yhy6lrxd8w1HLGa6aJIK+6aHm2ohGGjGYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=irSp0n8oLFOdeJW1f9yl9msZ81p2M9CpPNQ9LQEkVOeUd5dq0SiyYUCMegyaTF31hY oQxxOcZg3Fl1ukb6kzxeXz92lbllFR34bqB/H7dRUfk8/L3qGzxH9Qbd1pwvZImpnZoN Zf2NfeNoGHOhlqqka6noeTtR3tDMxEDnfvYx8= Received: by 10.141.88.3 with SMTP id q3mr524858rvl.3.1213237491087; Wed, 11 Jun 2008 19:24:51 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Wed, 11 Jun 2008 19:24:24 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 10:24:24 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: Paul In-Reply-To: <20080611173211.A899C1E9E@fep5.cogeco.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080611173211.A899C1E9E@fep5.cogeco.net> X-Google-Sender-Auth: 6ef4054d1c82bc36 Cc: freebsd-stable@freebsd.org Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 12 Jun 2008 02:24:51 -0000 2008/6/12 Paul : > 1) When I do a ls -lh on the raid 6 array with 6 disks in the array it takes > aver 16 seconds before it starts to display anything on the screen. > 2) While running a tar command on another shell, the time goes to 28 seconds > for the same list to start showing. > 3) When I do a ls (with no other options) it starts to list right away. > 4) When I do a ls -ln it displays right away as well pointing to the > slowdown being the mapping of the users in the db lookup. > > I have the same directory with the same number of files on a Raid 5 SCSI > partition on Freebsd 4.X and it only takes 2 seconds to start displaying the > list with the command ls -lh. > > Any ideas why it takes so long for this on Freebsd 7.0 stable? > > The partition this folder is on it /dev/da0s1f with a total size of 1.7T > and a usage of 63G > > Any suggestions or help on this would be greatly appreciated. Could you please do a couple of other tests, if you're able to? I've got a PR to look into this issue. Could you see if using a smaller password file makes the ls start/run quicker? Could you possibly run ls inside "truss" on both FreeBSD-4 and FreeBSD-7 and email me a snippet of the output (say, a few hundred lines) ? Something like: truss ls >foo 2>&1 Thanks, Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 02:25:42 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DBD6106567B for ; Thu, 12 Jun 2008 02:25:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.237]) by mx1.freebsd.org (Postfix) with ESMTP id CCF748FC1F for ; Thu, 12 Jun 2008 02:25:41 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4096543rvf.43 for ; Wed, 11 Jun 2008 19:25:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=xmIemrNMsacqWHKpPhEV5rMq9wXvdr07eTk1jJiwd/U=; b=aEjF4tr/79bgcFYF/kRQxeKDv1McZnNWSfCd5kTMG179fdKG+uuGAYCmKXA2wuri7y 7zpO+N9JiUmiuD5AY5nuqeyEgDrQ4ay4ypaSFeLcb137dxTDBL7xRpmDrESq07vYGT6j Xpn+AOc9l2UtJZoHoriZ+Gm8AtIn8gIFcpt8I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=irSp0n8oLFOdeJW1f9yl9msZ81p2M9CpPNQ9LQEkVOeUd5dq0SiyYUCMegyaTF31hY oQxxOcZg3Fl1ukb6kzxeXz92lbllFR34bqB/H7dRUfk8/L3qGzxH9Qbd1pwvZImpnZoN Zf2NfeNoGHOhlqqka6noeTtR3tDMxEDnfvYx8= Received: by 10.141.122.20 with SMTP id z20mr481245rvm.160.1213237464092; Wed, 11 Jun 2008 19:24:24 -0700 (PDT) Received: by 10.141.70.11 with HTTP; Wed, 11 Jun 2008 19:24:24 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 10:24:24 +0800 From: "Adrian Chadd" Sender: adrian.chadd@gmail.com To: Paul In-Reply-To: <20080611173211.A899C1E9E@fep5.cogeco.net> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080611173211.A899C1E9E@fep5.cogeco.net> X-Google-Sender-Auth: 6ef4054d1c82bc36 Cc: freebsd-stable@freebsd.org Subject: Re: Areca Raid 6 ARC-1231 Raid 6 Slow LS Listing Performance on large directory 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, 12 Jun 2008 02:25:42 -0000 2008/6/12 Paul : > 1) When I do a ls -lh on the raid 6 array with 6 disks in the array it takes > aver 16 seconds before it starts to display anything on the screen. > 2) While running a tar command on another shell, the time goes to 28 seconds > for the same list to start showing. > 3) When I do a ls (with no other options) it starts to list right away. > 4) When I do a ls -ln it displays right away as well pointing to the > slowdown being the mapping of the users in the db lookup. > > I have the same directory with the same number of files on a Raid 5 SCSI > partition on Freebsd 4.X and it only takes 2 seconds to start displaying the > list with the command ls -lh. > > Any ideas why it takes so long for this on Freebsd 7.0 stable? > > The partition this folder is on it /dev/da0s1f with a total size of 1.7T > and a usage of 63G > > Any suggestions or help on this would be greatly appreciated. Could you please do a couple of other tests, if you're able to? I've got a PR to look into this issue. Could you see if using a smaller password file makes the ls start/run quicker? Could you possibly run ls inside "truss" on both FreeBSD-4 and FreeBSD-7 and email me a snippet of the output (say, a few hundred lines) ? Something like: truss ls >foo 2>&1 Thanks, Adrian -- Adrian Chadd - adrian@freebsd.org From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 03:24:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CC45A1065670 for ; Thu, 12 Jun 2008 03:24:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.234]) by mx1.freebsd.org (Postfix) with ESMTP id 8D2128FC0C for ; Thu, 12 Jun 2008 03:24:38 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4116004rvf.43 for ; Wed, 11 Jun 2008 20:24:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=CMH6CBcPQS33eMT4odDbX+e+ROk9lqfupeBEr1SIDvc=; b=KMQsfaXvQeXiJBdjPYK0Ftjsoq34naF945WRDzhtJH7408FsxcDOIRn0PqFM03FH4E 5W2xdw4/LWUCFMhhYQnczZvocewb/kslJvH2FwhTyl1m/O+4tnVxtrdeoYVvjjyrlaCL mph3/f+J2UhiDRKnXq8nr9910vbmFR8+Hq7Q8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=ujV8KpCXH9ONBn1UKynUlNj4Bow/yZUeeDmzYeuCgGu8NBlT5h79hPfeC4Z2MNnsV3 ZXW6Bri0w83tYLRa+Qrx1HQ+hD3N0RajvZZLPYUnU5lvBtvTrgBIfyN0TQ+E+onnHa+E +RQrnmcvN0JLewPSvUaRjIw1SyQi6jY9DN4l8= Received: by 10.141.193.1 with SMTP id v1mr531407rvp.73.1213241078436; Wed, 11 Jun 2008 20:24:38 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id g31sm910063rvb.2.2008.06.11.20.24.36 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 20:24:37 -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 m5C3MTDO007985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 12:22:29 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5C3MS8i007984; Thu, 12 Jun 2008 12:22:28 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 12 Jun 2008 12:22:28 +0900 From: Pyun YongHyeon To: Gerrit K?hn Message-ID: <20080612032228.GD7250@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> User-Agent: Mutt/1.4.2.1i Cc: Daniele Bastianini , freebsd-stable@freebsd.org Subject: Re: broken re(4) 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: Thu, 12 Jun 2008 03:24:39 -0000 On Wed, Jun 11, 2008 at 09:24:57AM +0200, Gerrit K?hn wrote: > On Tue, 10 Jun 2008 20:43:04 +0200 Daniele Bastianini > wrote about Re: broken re(4): > > DB> > - copying large files (more than some 100MB) via ssh/scp drops the > DB> > connection due to "corrupted MAC on input": > DB> > Disconnecting: Corrupted MAC on input. > DB> > lost connection > > DB> I had the same problem. > DB> I fixed it (for now) making a buildworld with > DB> *default date=2008.03.01.00.00.00 in my src csup configuration. > > DB> I'm not so skilled to investigate in the sources but the problem is > DB> after this date. > > For me all versions from cvs and all patches from Pyun are working now, > after I have solved the issue with the bad riser card. I still think it's > funny that the riser causes this kind of trouble for the networking chips. > > On the other hand, I have not been able to get more than about 10MByte/s > through the interfaces of this particular system. I have 1GBit-networking > equipment, and the other systems (which are used as router) have no > problem doing a throughput of >20MB/s. Even bonding the two interfaces > using lagg(4) does not improve the performance - where else could be the > bottleneck? Before checking performance of network controller you had to rule out other factors like disk I/O. Use one of benchmark programs in ports/benchmark. > The only difference here is that I have the extra SATA-controller with > disks in there. However, the disks appear to be as fast as I can expect > from a SATA150-interface. > -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 03:30:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9EAF1065686; Thu, 12 Jun 2008 03:30:55 +0000 (UTC) (envelope-from lists@pingle.org) Received: from willow.pingle.org (willow.pingle.org [208.149.144.13]) by mx1.freebsd.org (Postfix) with ESMTP id 755038FC20; Thu, 12 Jun 2008 03:30:55 +0000 (UTC) (envelope-from lists@pingle.org) Received: from localhost (unknown [127.0.0.1]) by willow.pingle.org (Postfix) with ESMTP id 90EB01145B; Wed, 11 Jun 2008 23:12:29 -0400 (EDT) X-Virus-Scanned: amavisd-new at pingle.org Received: from willow.pingle.org ([127.0.0.1]) by localhost (willow.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCs4aEmbxz+e; Wed, 11 Jun 2008 23:12:27 -0400 (EDT) Received: from [127.0.0.1] (josie.pingle.org [209.125.59.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by willow.pingle.org (Postfix) with ESMTPSA id 3A81B1145A; Wed, 11 Jun 2008 23:12:26 -0400 (EDT) Message-ID: <48509419.6060206@pingle.org> Date: Wed, 11 Jun 2008 23:12:25 -0400 From: Jim Pingle User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Daniel O'Connor References: <4846B64F.4090700@minibofh.org> <484FF478.8010405@minibofh.org> <20080611161048.GA66773@eos.sc1.parodius.com> <200806121118.45137.doconnor@gsoft.com.au> In-Reply-To: <200806121118.45137.doconnor@gsoft.com.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 03:30:55 -0000 Daniel O'Connor wrote: > On Thu, 12 Jun 2008, Jeremy Chadwick wrote: >> I myself haven't ever run into extension ordering issues like those >> described (and we've done hosting for years), but I don't doubt those >> who have experienced such. > > I am currently experiencing this :( > In the past I shuffled the order until it worked but that's not a real > solution. > [snip] I've mentioned this on the lists a couple times, but I have a shell script I worked out that puts the extensions into a known-working order. http://www.pingle.org/2007/09/22/php-crashes-extensions-workaround It's based on things I've come across with respect to this issue over the last couple years. It's not a new problem by a long shot. It's been happening to me for years with PHP4 and PHP5, Apache 1.3.x and 2.x. See also my previous posts on my site: http://www.pingle.org/2006/10/18/php-crashes-extensions http://www.pingle.org/2007/05/13/php-crashes-extensions-2 And some previous threads on the topic: http://lists.freebsd.org/pipermail/freebsd-stable/2006-November/030951.html http://lists.freebsd.org/mailman/htdig/freebsd-ports/2006-November/036849.html (I thought there were more but I can't find them at the moment...) I need to see if I can improve the script any (suggestions are most welcome) then open a PR to see if it -- or logic like it -- can be included in the php-extensions meta port. Jim From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 03:57:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B5C61065671 for ; Thu, 12 Jun 2008 03:57:25 +0000 (UTC) (envelope-from zhpalt@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.188]) by mx1.freebsd.org (Postfix) with ESMTP id DFDA38FC17 for ; Thu, 12 Jun 2008 03:57:24 +0000 (UTC) (envelope-from zhpalt@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so958086tid.3 for ; Wed, 11 Jun 2008 20:57:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:to:content-type :date:message-id:mime-version:x-mailer:content-transfer-encoding; bh=3hgA4rwQjcgHbi7p4Kerd/WcYbwzyEfpqSfaEmxx4VY=; b=c3+vhmZ4x/3sKWHlwM8kI9//GfHP0cpF1EhZM2GL+TucYrADh1yEkuhjeu3zufDZNS 2+qqKJahQia4uy9fMZNQA3KSO4tMOydYpOuABv5zblUPWoBYs0ZHDkMXFb08SsqQcTm5 6xXbc18z7/8aZiR0xObQ2hI69/39Z7MNsVWPA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:to:content-type:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=TawxVv7A+6ILhxCkiE2WOrRJhI0uuWQXec1refXcmYDt9+HM0achCYxRA93AD0ZWow kA6k/0o8a7iToGM1bcoWgv5XGIb3advKggcVm4tr0XuSWpG1lQCrk1wu27d1ug0og8sG xY6x+65qAEID8LvX+u0TSsqQbVBl+G2fzroOo= Received: by 10.110.84.3 with SMTP id h3mr389599tib.43.1213241522066; Wed, 11 Jun 2008 20:32:02 -0700 (PDT) Received: from ?192.168.1.100? ( [222.172.214.52]) by mx.google.com with ESMTPS id 2sm912875tif.7.2008.06.11.20.32.00 (version=SSLv3 cipher=RC4-MD5); Wed, 11 Jun 2008 20:32:01 -0700 (PDT) From: Pallt To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=UTF-8 Date: Thu, 12 Jun 2008 11:31:59 +0800 Message-Id: <1213241519.54120.9.camel@Tiger.domain> Mime-Version: 1.0 X-Mailer: Evolution 2.22.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Subject: Under gnome-2.22.2, can not lock the screen 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, 12 Jun 2008 03:57:25 -0000 Hi! The version of the freebsd is 7.0-stable(June 9 2008), and the gnome was also updated to 2.22.2. But, I can not lock the screen, when I click the "Lock Screen" button under System Menu(The acpi can works well). I can't find the right way to let it work. Thanks any way From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 05:15:38 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53AA61065673; Thu, 12 Jun 2008 05:15:38 +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 9395B8FC2A; Thu, 12 Jun 2008 05:15:36 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C5FYtY088574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 14:45:35 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jim Pingle Date: Thu, 12 Jun 2008 14:45:21 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> <48509419.6060206@pingle.org> In-Reply-To: <48509419.6060206@pingle.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2883667.1orHJxJZAt"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121445.30864.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 05:15:38 -0000 --nextPart2883667.1orHJxJZAt Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Jim Pingle wrote: > I need to see if I can improve the script any (suggestions are most > welcome) then open a PR to see if it -- or logic like it -- can be > included in the php-extensions meta port. Adding the script to the port seems like the way to go (baring an=20 upstream fix but it seems like a difficult problem to solve). Unfortunately it doesn't help me :( If I disable everything except either pgsql or mhash (either separately=20 or together) Apache crashes with.. #0 0x28ad6d40 in ?? () #1 0x281c6f2e in _pthread_main_np () from /lib/libc.so.7 #2 0x2819fa0c in puts () from /lib/libc.so.7 #3 0x281a0177 in gethostbyname () from /lib/libc.so.7 #4 0x08069a12 in ap_get_local_host () #5 0x08068b9c in ap_fini_vhost_config () #6 0x0805639c in ap_read_config () #7 0x0805f133 in standalone_main () #8 0x08060c1f in main () I don't understand why gethostbyname() would call puts() - and why that=20 would then crash! Seems like some threading related wrinkle though as pgsql & mhash are=20 the only extensions I have that are linked to libthr.so =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 --nextPart2883667.1orHJxJZAt Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIULDy5ZPcIHs/zowRAviZAJ0a7JoL4wqn8MwwZ2JBR8laEXJukACfSJFh KOQch/Yk+NEEzRJkNBjVPms= =giON -----END PGP SIGNATURE----- --nextPart2883667.1orHJxJZAt-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 05:59:19 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDB11065671; Thu, 12 Jun 2008 05:59:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 750198FC16; Thu, 12 Jun 2008 05:59:19 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 0BE3F1CC068; Wed, 11 Jun 2008 22:59:19 -0700 (PDT) Date: Wed, 11 Jun 2008 22:59:19 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20080612055919.GA27267@eos.sc1.parodius.com> References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> <48509419.6060206@pingle.org> <200806121445.30864.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200806121445.30864.doconnor@gsoft.com.au> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org, freebsd-apache@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 05:59:19 -0000 On Thu, Jun 12, 2008 at 02:45:21PM +0930, Daniel O'Connor wrote: > On Thu, 12 Jun 2008, Jim Pingle wrote: > > I need to see if I can improve the script any (suggestions are most > > welcome) then open a PR to see if it -- or logic like it -- can be > > included in the php-extensions meta port. > > Adding the script to the port seems like the way to go (baring an > upstream fix but it seems like a difficult problem to solve). > > Unfortunately it doesn't help me :( > If I disable everything except either pgsql or mhash (either separately > or together) Apache crashes with.. > > #0 0x28ad6d40 in ?? () > #1 0x281c6f2e in _pthread_main_np () from /lib/libc.so.7 > #2 0x2819fa0c in puts () from /lib/libc.so.7 > #3 0x281a0177 in gethostbyname () from /lib/libc.so.7 > #4 0x08069a12 in ap_get_local_host () > #5 0x08068b9c in ap_fini_vhost_config () > #6 0x0805639c in ap_read_config () > #7 0x0805f133 in standalone_main () > #8 0x08060c1f in main () > > I don't understand why gethostbyname() would call puts() - and why that > would then crash! I can't explain why it's calling puts() directly either. Bad RAM could cause something bizarre like this, or a corrupt/broken binary. The libc code I'm looking at (src/lib/libc/net/gethostnameadr.c and gethostbydns.c) don't call puts) don't appear to call puts() directly. Of course, there may be macros used which do this. There are some places in the resolver code where printing to stdout or stderr can occur. I'd expect to see a longer stack trace (meaning more functions between gethostbyname() and puts()) if that were the case, though. There's a decent document on how to debug httpd below. You'll need to start httpd with -X or with "MaxClients 1", to keep it from forking. You can do that through gdb if you want, or (what I prefer, since I'm not very good with gdb) use truss. http://httpd.apache.org/dev/debugging.html If you go the truss route, be sure to use -a -s 4096. You'd be able to see what actual string is being output via puts(), assuming it gets as far as to start writing data to the fd. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 06:47:20 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16558106567C for ; Thu, 12 Jun 2008 06:47:20 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id BCAF88FC0A for ; Thu, 12 Jun 2008 06:47:19 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by an-out-0708.google.com with SMTP id b33so867146ana.13 for ; Wed, 11 Jun 2008 23:47:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=OpFp8B669axtV7f/d7Lr0m2bECTXO3eLHbZoUpuqU1s=; b=dW53IdC9pNno+M6sUJyWFPS36cjEvdUkDM8Fg1OvpC/Za57ZvOE3tspxKfSEMBubq0 zBMZ8Jne8r7KRdvXC6HL4LwjQSQuoschehEn+sztzvl8JXPCDy5MsTt5QnoXZfY6doQe cEne8fxIEz5MRHeq/IssXCc/4EpDyZ4NmsSrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=aGKPmRHpGVTqmtWDRiMmcrauj3C4P8HfJbxB+gs1zsimmB/hvIcSVLnFySithXhfz3 MRwQHWeHbLoaYWsfoG9veqvwl6/gnGw88z7BqFgS2ZnsWPxYhqlIl3ai0maoGNzm1TJY T5nBEc8SUg+F+ZtFitKp3yy+YYpcxh102gZhU= Received: by 10.100.110.15 with SMTP id i15mr1272721anc.130.1213251675223; Wed, 11 Jun 2008 23:21:15 -0700 (PDT) Received: by 10.90.96.4 with HTTP; Wed, 11 Jun 2008 23:21:15 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 10:21:15 +0400 From: pluknet To: dennis_flynn@yahoo.com In-Reply-To: <437286.30504.qm@web54011.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <437286.30504.qm@web54011.mail.re2.yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: FreeBSD 7.0 Stable and the CP2101 driver 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, 12 Jun 2008 06:47:20 -0000 2008/6/11 Dennis Flynn : [trim] > I tried installing the update, e.g. "freebsd-update -r 7.0-STABLE fetch", then "freebsd-update -r 7.0-STABLE upgrade". Seemed to work. But I do not seem to have the device driver loaded when I plug in the USB device. I get the folowwing in the messages log: > > Jun 10 16:48:02 wx kernel: ugen0: on uhub0 > > But I don't see a device that I think I should see, like /dev/ttyU0. If I do a "uname -a" I see the following: > > FreeBSD wx.dennis-flynn.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 > > That doesn't seem right to me. Shouldn't I see something like 7.0-RELEASE-p1 or 7.0-STABLE? Did I do something wrong in my update to RELEASE? How do I know if I'm running the STABLE kernel with the driver I want? How can I tell if the driver (uslcom) is there and/or loaded? > uslcom(4) appeared somewhere in 7.0-STABLE in GENERIC, and you are running 7.0-RELEASE, that is older. freebsd-update works only with releases (plus sec.patches), and 7.0-STABLE is not a release (obviously because you cannot definitely say to what date it corresponds). So you should update it to STABLE manually or wait until 7.1 is out. wbr, pluknet From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 06:58:14 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 27E691065673 for ; Thu, 12 Jun 2008 06:58:14 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id 89D808FC0C for ; Thu, 12 Jun 2008 06:58:13 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m5C6wAWx017485; Thu, 12 Jun 2008 08:58:11 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 58B1772; Thu, 12 Jun 2008 08:58:10 +0200 (CEST) Date: Thu, 12 Jun 2008 08:58:10 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: pyunyh@gmail.com Message-Id: <20080612085810.072d705d.gerrit@pmp.uni-hannover.de> In-Reply-To: <20080612032228.GD7250@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> <20080612032228.GD7250@cdnetworks.co.kr> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.6.11.233906 Cc: freebsd-stable@freebsd.org Subject: Re: broken re(4) 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, 12 Jun 2008 06:58:14 -0000 On Thu, 12 Jun 2008 12:22:28 +0900 Pyun YongHyeon wrote about Re: broken re(4): PY> Before checking performance of network controller you had to rule PY> out other factors like disk I/O. Use one of benchmark programs in PY> ports/benchmark. I already did simple benchmarking by using "dd if=/dev/zero of=file" which gave me several 10s of MByte/s under all circumstances. Can you recommend one of the benchmarking programs for more detailed testing? cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 07:03:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A5571065671 for ; Thu, 12 Jun 2008 07:03:36 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.239]) by mx1.freebsd.org (Postfix) with ESMTP id DFCEF8FC1B for ; Thu, 12 Jun 2008 07:03:35 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4174818rvf.43 for ; Thu, 12 Jun 2008 00:03:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:received:date:from :to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=7kTVwhfjVGYCno5YhwjO/sunZWt9ob8+WIBk57kQZAY=; b=jCdsL3Ge41OWwQnQO2tH3nJbJxaq8chmOO3Tq0r1jiLqphxpz55EX/l7q/5Jp7EEnm QQ6T+haL4Czpcfm85/wUn8K6CSILvHg64wUCHuhjB/3TusoGCwf6XZt0hNdQ4qViBjhc 5MVIPUMzCEL3X/u6mfDUmPY/aiDc/go1EVPHA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=hGmto1CAMh7MVq+uau1yog7UA3sWdwItVbADlOuyWLnaGWS1jZlkQ7f1Ox+o6ZeVJa ogKuw5HNMsMlERj2nb0K+OpJ+kxb1gr2Rb7/yLO7xD7YK5LoeYKwtVwvgDveITn468vZ RZhi03j+9Bdw9G8DfxUG3+3D2cRggIqCRg50s= Received: by 10.140.166.21 with SMTP id o21mr594998rve.167.1213254215782; Thu, 12 Jun 2008 00:03:35 -0700 (PDT) Received: from michelle.cdnetworks.co.kr ( [211.53.35.84]) by mx.google.com with ESMTPS id g31sm1205796rvb.2.2008.06.12.00.03.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 12 Jun 2008 00:03:34 -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 m5C71Qfb008619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 16:01:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Received: (from yongari@localhost) by michelle.cdnetworks.co.kr (8.13.5/8.13.5/Submit) id m5C71QbX008618; Thu, 12 Jun 2008 16:01:26 +0900 (KST) (envelope-from pyunyh@gmail.com) Date: Thu, 12 Jun 2008 16:01:26 +0900 From: Pyun YongHyeon To: Gerrit K?hn Message-ID: <20080612070126.GF7250@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> <20080612032228.GD7250@cdnetworks.co.kr> <20080612085810.072d705d.gerrit@pmp.uni-hannover.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080612085810.072d705d.gerrit@pmp.uni-hannover.de> User-Agent: Mutt/1.4.2.1i Cc: freebsd-stable@freebsd.org Subject: Re: broken re(4) 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: Thu, 12 Jun 2008 07:03:36 -0000 On Thu, Jun 12, 2008 at 08:58:10AM +0200, Gerrit K?hn wrote: > On Thu, 12 Jun 2008 12:22:28 +0900 Pyun YongHyeon wrote > about Re: broken re(4): > > PY> Before checking performance of network controller you had to rule > PY> out other factors like disk I/O. Use one of benchmark programs in > PY> ports/benchmark. > > I already did simple benchmarking by using "dd if=/dev/zero of=file" which > gave me several 10s of MByte/s under all circumstances. > Can you recommend one of the benchmarking programs for more detailed > testing? > Try netperf or iperf in ports/benchmark. > > cu > Gerrit -- Regards, Pyun YongHyeon From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 07:05:50 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98BEE106566C; Thu, 12 Jun 2008 07:05:50 +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 D55368FC19; Thu, 12 Jun 2008 07:05:44 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C75dCN092815 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 16:35:40 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jeremy Chadwick Date: Thu, 12 Jun 2008 16:35:26 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121445.30864.doconnor@gsoft.com.au> <20080612055919.GA27267@eos.sc1.parodius.com> In-Reply-To: <20080612055919.GA27267@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1909476.ZFXFlsEv8K"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121635.36998.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-stable@freebsd.org, freebsd-apache@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 07:05:50 -0000 --nextPart1909476.ZFXFlsEv8K Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > > I don't understand why gethostbyname() would call puts() - and why > > that would then crash! > > I can't explain why it's calling puts() directly either. Bad RAM > could cause something bizarre like this, or a corrupt/broken binary. Yeah.. I have rebuilt lots of stuff, although not libc. This machine has build world, kernel, KDE, etc.. I am pretty sure the hardw= are is OK as none of the builds had an issue. > The libc code I'm looking at (src/lib/libc/net/gethostnameadr.c and > gethostbydns.c) don't call puts) don't appear to call puts() > directly. Of course, there may be macros used which do this. I had a look - there certainly isn't anywhere obvious it's hapening. I gues= s the only thing now is to rebuild with debugging. > There are some places in the resolver code where printing to stdout > or stderr can occur. I'd expect to see a longer stack trace (meaning > more functions between gethostbyname() and puts()) if that were the > case, though. > > There's a decent document on how to debug httpd below. You'll need > to start httpd with -X or with "MaxClients 1", to keep it from > forking. You can do that through gdb if you want, or (what I prefer, > since I'm not very good with gdb) use truss. OK thanks. > http://httpd.apache.org/dev/debugging.html > > If you go the truss route, be sure to use -a -s 4096. You'd be able > to see what actual string is being output via puts(), assuming it > gets as far as to start writing data to the fd. Hmm I had a go with gdb but it doesn't work properly.. I got this.. [midget 16:33] /tmp/work/usr/ports/www/apache13-modssl/work/apache_1.3.41 >= sudo gdb src/httpd Password: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd"... (gdb) run -X Starting program: /data/tmp/work/usr/ports/www/apache13-modssl/work/apache_= 1.3.41/src/httpd -X [New LWP 100212] [New Thread 0x819d300 (LWP 100212)] [New LWP 100212] suspend error: generic error [Switching to LWP 100212] Stopped due to shared library event (gdb) info thread Cannot find new threads: generic error (gdb) bt #0 0x2807fda0 in r_debug_state () from /libexec/ld-elf.so.1 #1 0x2808367d in dlclose () from /libexec/ld-elf.so.1 #2 0x28706164 in zend_hash_apply_deleter () from /usr/local/libexec/apache/libphp5.so #3 0x287063a8 in zend_hash_graceful_reverse_destroy () from /usr/local/libexec/apache/libphp5.so #4 0x286fc89e in zend_shutdown () from /usr/local/libexec/apache/libphp5.so #5 0x286bb5bf in php_module_shutdown () from /usr/local/libexec/apache/lib= php5.so #6 0x286bb66b in php_module_shutdown_wrapper () from /usr/local/libexec/apache/libphp5.so #7 0x28776aaa in apache_php_module_shutdown_wrapper () from /usr/local/libexec/apache/libphp5.so #8 0x080524d9 in ap_clear_pool (a=3D0x8106010) at alloc.c:1937 #9 0x0805f0f6 in standalone_main (argc=3DVariable "argc" is not available. ) at http_main.c:5480 #10 0x08060c1f in main (argc=3D-716130182, argv=3D0x1) at http_main.c:5883 I tried truss and it seemed to be taking a long time (5-10 minutes) and generating a lot of seemingly identical logging :( =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 --nextPart1909476.ZFXFlsEv8K Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUMrA5ZPcIHs/zowRAu78AJ0YmAppa7JFaxyQ06SPy7gFgAO8PwCgqfRB oZX+QiZ8daKQrmhahdTVfx8= =tLwM -----END PGP SIGNATURE----- --nextPart1909476.ZFXFlsEv8K-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 07:28:12 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB3D81065678; Thu, 12 Jun 2008 07:28:12 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 92C158FC0A; Thu, 12 Jun 2008 07:28:12 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 7EAA11CC060; Thu, 12 Jun 2008 00:28:12 -0700 (PDT) Date: Thu, 12 Jun 2008 00:28:12 -0700 From: Jeremy Chadwick To: Daniel O'Connor Message-ID: <20080612072812.GA35851@eos.sc1.parodius.com> References: <4846B64F.4090700@minibofh.org> <200806121445.30864.doconnor@gsoft.com.au> <20080612055919.GA27267@eos.sc1.parodius.com> <200806121635.36998.doconnor@gsoft.com.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200806121635.36998.doconnor@gsoft.com.au> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 07:28:12 -0000 On Thu, Jun 12, 2008 at 04:35:26PM +0930, Daniel O'Connor wrote: > On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > > > I don't understand why gethostbyname() would call puts() - and why > > > that would then crash! > > > > I can't explain why it's calling puts() directly either. Bad RAM > > could cause something bizarre like this, or a corrupt/broken binary. > > Yeah.. I have rebuilt lots of stuff, although not libc. Huh? > This machine has build world, kernel, KDE, etc.. I am pretty sure the hardware is OK as none of the builds had an issue. libc is part of world. *Every* program relies (is linked with) on libc. > > If you go the truss route, be sure to use -a -s 4096. You'd be able > > to see what actual string is being output via puts(), assuming it > > gets as far as to start writing data to the fd. > > Hmm I had a go with gdb but it doesn't work properly.. I got this.. > [midget 16:33] /tmp/work/usr/ports/www/apache13-modssl/work/apache_1.3.41 >sudo gdb src/httpd > Password: > GNU gdb 6.1.1 [FreeBSD] > Copyright 2004 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and you are > welcome to change it and/or distribute copies of it under certain conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for details. > This GDB was configured as "i386-marcel-freebsd"... > (gdb) run -X > Starting program: /data/tmp/work/usr/ports/www/apache13-modssl/work/apache_1.3.41/src/httpd -X > [New LWP 100212] > [New Thread 0x819d300 (LWP 100212)] > [New LWP 100212] > suspend error: generic error > [Switching to LWP 100212] > Stopped due to shared library event > (gdb) info thread > Cannot find new threads: generic error > (gdb) bt > #0 0x2807fda0 in r_debug_state () from /libexec/ld-elf.so.1 > #1 0x2808367d in dlclose () from /libexec/ld-elf.so.1 > #2 0x28706164 in zend_hash_apply_deleter () > from /usr/local/libexec/apache/libphp5.so > #3 0x287063a8 in zend_hash_graceful_reverse_destroy () > from /usr/local/libexec/apache/libphp5.so > #4 0x286fc89e in zend_shutdown () from /usr/local/libexec/apache/libphp5.so > #5 0x286bb5bf in php_module_shutdown () from /usr/local/libexec/apache/libphp5.so > #6 0x286bb66b in php_module_shutdown_wrapper () > from /usr/local/libexec/apache/libphp5.so > #7 0x28776aaa in apache_php_module_shutdown_wrapper () > from /usr/local/libexec/apache/libphp5.so > #8 0x080524d9 in ap_clear_pool (a=0x8106010) at alloc.c:1937 > #9 0x0805f0f6 in standalone_main (argc=Variable "argc" is not available. > ) at http_main.c:5480 > #10 0x08060c1f in main (argc=-716130182, argv=0x1) at http_main.c:5883 I can't say much about this, but I'm willing to bet it's the result of some Apache + PHP weirdness. I've never known gdb on FreeBSD to be as reliable/useful as, say, on Linux or Solaris. Always odd/strange things happening with gdb on FreeBSD. > I tried truss and it seemed to be taking a long time (5-10 minutes) and > generating a lot of seemingly identical logging :( Okay, let's backtrack here. The OP states that he can induce a segfault of httpd when doing "apachectl graceful". Is that the exact problem you're seeing, or are you seeing problems where PHP/Apache segfaults during operation? I just want to be clear. If the latter, then truss "generating lots of seemingly identical logging" is probably expected. I'm guessing it's select() or poll() or something related to kqueue/kevent, as it'd be waiting for I/O on the HTTP socket. You'd have to submit the HTTP request to the PHP script to get it to crash. In either case, you may have to resort to using ktrace + kdump, which may or may not help narrow this down. Use "ktrace -i -t+ httpd -X" (I hope that'll work; I'm not sure if ktrace allows you to pass arguments to a command), which will start populating a file called ktrace.out. You should then do the "apachectl graceful" in another window (or if the latter, submit the HTTP request), and ktrace may exit when the segfault happens (I'm not sure about this; it may sit there indefinitely). In the case it doesn't exit, and you've confirmed the core happened (check "dmesg"), you should ^C the ktrace and then do "ktrace -C" just to be sure nothing got wedged. You'll then have to use kdump to decode the contents of ktrace.out. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 08:18:34 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E5D7106567E; Thu, 12 Jun 2008 08:18:34 +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 A28F98FC22; Thu, 12 Jun 2008 08:18:33 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C8IUiR096022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 17:48:31 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jeremy Chadwick Date: Thu, 12 Jun 2008 17:48:26 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121635.36998.doconnor@gsoft.com.au> <20080612072812.GA35851@eos.sc1.parodius.com> In-Reply-To: <20080612072812.GA35851@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2561461.soqbAt2eX5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121748.28133.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 08:18:34 -0000 --nextPart2561461.soqbAt2eX5 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > > Yeah.. I have rebuilt lots of stuff, although not libc. > > Huh? Sorry, I meant that I have to explicitly rebuilt it since I did a=20 buildworld to make sure it wasn't fubar'd somehow. I haven't done that mainly because I find it extremely unlikely it would=20 only break Apache in this manner but nothing else. I might rebuild it to get debug symbols though.. > > This machine has build world, kernel, KDE, etc.. I am pretty sure > > the hardware is OK as none of the builds had an issue. > > libc is part of world. *Every* program relies (is linked with) on > libc. Yes, sorry for my confusing turn of phrase! :) > > #10 0x08060c1f in main (argc=3D-716130182, argv=3D0x1) at > > http_main.c:5883 > > I can't say much about this, but I'm willing to bet it's the result > of some Apache + PHP weirdness. I've never known gdb on FreeBSD to > be as reliable/useful as, say, on Linux or Solaris. Always > odd/strange things happening with gdb on FreeBSD. Yeah :( > > I tried truss and it seemed to be taking a long time (5-10 minutes) > > and generating a lot of seemingly identical logging :( > > Okay, let's backtrack here. > > The OP states that he can induce a segfault of httpd when doing > "apachectl graceful". Is that the exact problem you're seeing, or > are you seeing problems where PHP/Apache segfaults during operation?=20 > I just want to be clear. > > If the latter, then truss "generating lots of seemingly identical > logging" is probably expected. I'm guessing it's select() or poll() > or something related to kqueue/kevent, as it'd be waiting for I/O on > the HTTP socket. You'd have to submit the HTTP request to the PHP > script to get it to crash. > > In either case, you may have to resort to using ktrace + kdump, which > may or may not help narrow this down. > > Use "ktrace -i -t+ httpd -X" (I hope that'll work; I'm not sure if > ktrace allows you to pass arguments to a command), which will start > populating a file called ktrace.out. You should then do the > "apachectl graceful" in another window (or if the latter, submit the > HTTP request), and ktrace may exit when the segfault happens (I'm not > sure about this; it may sit there indefinitely). > > In the case it doesn't exit, and you've confirmed the core happened > (check "dmesg"), you should ^C the ktrace and then do "ktrace -C" > just to be sure nothing got wedged. > > You'll then have to use kdump to decode the contents of ktrace.out. =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 --nextPart2561461.soqbAt2eX5 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUNvU5ZPcIHs/zowRAnXaAKCTsHVjsPNFNTxTVR1R/nQ+CU2eUQCeIfzn kNajhS04+47Gqfl3OK80WkU= =hN6U -----END PGP SIGNATURE----- --nextPart2561461.soqbAt2eX5-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 08:20:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 665061065678; Thu, 12 Jun 2008 08:20:54 +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 991488FC14; Thu, 12 Jun 2008 08:20:53 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (inchoate.gsoft.com.au [203.31.81.30]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5C8KpVc096072 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 17:50:52 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jeremy Chadwick Date: Thu, 12 Jun 2008 17:50:49 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121635.36998.doconnor@gsoft.com.au> <20080612072812.GA35851@eos.sc1.parodius.com> In-Reply-To: <20080612072812.GA35851@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2691996.7NjXRzuLca"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121750.50756.doconnor@gsoft.com.au> X-Spam-Score: -3.977 () ALL_TRUSTED,BAYES_00 X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 08:20:54 -0000 --nextPart2691996.7NjXRzuLca Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline [This is a continuation of my last message, I accidentally mashed the=20 send key] On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > > I tried truss and it seemed to be taking a long time (5-10 minutes) > > and generating a lot of seemingly identical logging :( > > Okay, let's backtrack here. > > The OP states that he can induce a segfault of httpd when doing > "apachectl graceful". Is that the exact problem you're seeing, or > are you seeing problems where PHP/Apache segfaults during operation?=20 > I just want to be clear. No, I don't see a problem with 'apachectl graceful' - it doesn't get=20 that far. > If the latter, then truss "generating lots of seemingly identical > logging" is probably expected. I'm guessing it's select() or poll() > or something related to kqueue/kevent, as it'd be waiting for I/O on > the HTTP socket. You'd have to submit the HTTP request to the PHP > script to get it to crash. I get a crash when Apache starts up. I wasn't sure if it was related to OPs problem or not, I should have=20 been clearer though. > In either case, you may have to resort to using ktrace + kdump, which > may or may not help narrow this down. > > Use "ktrace -i -t+ httpd -X" (I hope that'll work; I'm not sure if > ktrace allows you to pass arguments to a command), which will start Yes ktrace does allow that. =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 --nextPart2691996.7NjXRzuLca Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUNxi5ZPcIHs/zowRAtlSAJ4nHwYI6ZYWzl3NXF4rL0X1llk4GACaA+64 Box3PMfBf3W/AzeEtpH4SrE= =s07G -----END PGP SIGNATURE----- --nextPart2691996.7NjXRzuLca-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 08:32:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5A85F106564A for ; Thu, 12 Jun 2008 08:32:46 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id 08E9E8FC0C for ; Thu, 12 Jun 2008 08:32:45 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [10.0.1.101] (unknown [87.121.18.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id E6E781522CE3; Thu, 12 Jun 2008 11:32:39 +0300 (EEST) Message-ID: <4850DF22.9080802@lozenetz.org> Date: Thu, 12 Jun 2008 11:32:34 +0300 From: Anton - Valqk User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Robert Watson References: <3cc535c80806080449q3ec6e623v8603e9eccc3ab1f2@mail.gmail.com> <484FA07E.60103@lozenetz.org> <20080611164704.J40102@fledge.watson.org> In-Reply-To: <20080611164704.J40102@fledge.watson.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Found to be clean X-HostIT-MailScanner-From: lists@lozenetz.org Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is premature with buggy 6.3 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, 12 Jun 2008 08:32:46 -0000 Robert Watson wrote: > > On Wed, 11 Jun 2008, Anton - Valqk wrote: > >> I fully agree with the lines below. >> As noticed below there is more attention to developing new features, >> than making releases rock solid stable. > ... >> Ah, another thing, >> I'm waiting for virtualization networking layer for jails for quite >> long. >> I've tested it on a test server, worked perfect, but on production I >> don't want to patch my base. >> there are few other features to jals that never got commited in base, >> and as I said I don't want to patch it... > > The reason that the virtualization patches aren't in the tree is > precisely *because* we care about stability and are willing to slow > down feature development in order to accomplish it. Some features take > years to stabilize, and just because a patch works OK in your > environment doesn't mean it will work in everyone's. Moderating the > rate at which we adopt agressive new features is part of an > intentional strategy to avoid letting development trees destabilize to > a point where it's unproductive. > I totally agree with that point, just commented that it's been year(s) since its appearence an maybe not enought effort in it (just an outsider thought, can't know if it is) and the fueature is a really really great and nice one! > Robert N M Watson > Computer Laboratory > University of Cambridge > _______________________________________________ > 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" > -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 08:37:17 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABB12106566C for ; Thu, 12 Jun 2008 08:37:17 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from fmailhost01.isp.att.net (fmailhost01.isp.att.net [207.115.11.51]) by mx1.freebsd.org (Postfix) with ESMTP id 98BED8FC20 for ; Thu, 12 Jun 2008 08:37:17 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from [65.7.33.240] (host-65-7-33-240.mem.bellsouth.net?[65.7.33.240]) by isp.att.net (frfwmhc01) with ESMTP id <20080612082303H0100mff6le>; Thu, 12 Jun 2008 08:23:03 +0000 X-Originating-IP: [65.7.33.240] Message-ID: <4850DCA8.6000709@classic-games.com> Date: Thu, 12 Jun 2008 03:22:00 -0500 From: Greg Miller User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Adesso AKB-430UG keyboard on 7.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, 12 Jun 2008 08:37:17 -0000 I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD 7.0-release-p1, or trying to. The keyboard works fine in Windows, but with FreeBSD I get the same sort of problems people have described previous with the Genius SlimStar Pro: the keys behave as if CTRL is always pressed. I'd hate to have to switch to a different keyboard, because it took me years to find a good alternative to my old Cirque Input Center keyboard/glidepoint combo. -- http://www.velocityvector.com/ | http://www.classic-games.com/ I'd rather hunt with Dick Cheney than ride with Ted Kennedy. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 08:59:48 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7872D1065675 for ; Thu, 12 Jun 2008 08:59:48 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from mail.webreality.org (mailserver.webreality.org [217.75.141.5]) by mx1.freebsd.org (Postfix) with ESMTP id 857FC8FC14 for ; Thu, 12 Jun 2008 08:59:46 +0000 (UTC) (envelope-from lists@lozenetz.org) Received: from [10.0.1.101] (unknown [87.121.18.230]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.webreality.org (Postfix) with ESMTP id 95BB21522CD0; Thu, 12 Jun 2008 11:59:40 +0300 (EEST) Message-ID: <4850E577.4000503@lozenetz.org> Date: Thu, 12 Jun 2008 11:59:35 +0300 From: Anton - Valqk User-Agent: Mozilla-Thunderbird 2.0.0.14 (X11/20080509) MIME-Version: 1.0 To: Marian Hettwer References: <484FF461.6000306@lozenetz.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-HostIT-MailScanner-Information: Please contact the ISP for more information X-HostIT-MailScanner: Found to be clean X-HostIT-MailScanner-From: lists@lozenetz.org Cc: Andy Kosela , freebsd-stable@freebsd.org Subject: Re: CLARITY re: challenge: end of life for 6.2 is prematurewithbuggy 6.3 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, 12 Jun 2008 08:59:48 -0000 Thanks for the answer, so lets tell what I think :) Marian Hettwer wrote: > On Wed, 11 Jun 2008 18:50:57 +0300, Anton - Valqk > wrote: > >> Thanks for the answer! >> I'm glad someone answered me a human way, >> because two times before, I wasn't answered that way >> (well... my posts were angry and incomplete but...that's why i didn't >> continued to post...my bad). >> >> > Well then, lets continue answering in a human way. Which is, funnily > enough, usually the more productive way too ;-) > > >> now on topic: >> >> > yeah! > > >>> Thats unfortunatly true. >>> But there is a way around. As soon as you have several FreeBSD boxes, >>> >> I'd >> >>> advise you to install your own FreeBSD box for packages building. >>> So if you need to update your php installations, go to your build box >>> (which has the very same versions of programs installed as your >>> >> production >> >>> boxes), update your ports tree and do a "make package" of your new php >>> port. >>> If the new php package works fine on your build box, roll it out via >>> "pkg_add -r $NEWPHPTHINGY" and off you go. >>> >>> >>> >> I do have a build server(well a jail but works for me), also I have test >> eviornment (jailed too). >> I use this jail to build all my pkgs and use pkg_add -r (sweeet!!). >> For most of the ports this works, but sometimes something in make >> package breaks and i get a port installed partially >> (last case - apache22 got installed but no /usr/local/etc/rc.d/apache22 >> rc script, previous - pg_ctl never got installed) >> and in +CONTENTS file the missing files claimed to be there. >> > hm... sounds like a bug to me. On the other hand, you have to try to get it > to be reproducable. If it's a one timer then yes, it's annoying, but really > really hard to reproduce and therefor to fix. > > the problem is that I don't have enought time to setup a testing server and find out when the problem occurs, because it's random seen, on 10-15th build of the new port this happens, I've noticed that if I make #> make deinstall distclean install pakcage-recursive the problem occurs much more rare compared to just #> make deinstall ditsclean package-recursive I simply currently don't have time for test setup ;( >> I've had to rebuild that kind of port so I can install it again (after >> pkg_delete) to have the port working. >> > yeah, annoying. > > >> This happens most often when I do make install package-recursive (so I >> can get all needed ports installed). >> > If you can reproduce it step by step, it may be worth posting to ports@ > again with what you did and what happened. > Either you're doing something wrong, or something is broken. > However, it needs to be reproducable. At least in your environment. As a > starter, so to say :) > The more detailed your steps are written down, the more likely someone will > either follow those steps or give you a direct hint on "humm, could be > something bad over there... hm hm). > > I understand that, that's why I didn't posted again because, as I said i don't have time to sitdown and setup and try to reproduce it. >> Another strange thing is that when I use php-extensions to build all >> that I need (this takes most of my time when build/install new php) >> breaks because of the ?'bug'? described few lines above. as I said noone >> got interested in this problem... >> > I can't say anything specific about the php problem you said. I'm not using > php, or well, very rarely. I'll give it a try to update it the make package > way next time. > Unluckily this is a one-box only system. hmmm... If I find the time to > test, I'll drop you mail. But time is rare (admin life vs. normal life). > > To cut that short: Yeah, I can understand that this is annoying. But I'm > sure as hell: > - if it's a bug it can be fixed > - if it's a user error, it can be changed > - and all this has happened to me when trying to build my own debian > packages too ;) > And it happened to me with Gentoo, too. > Nothing new at all. Just the regular annoyances in sysadmins life. IMO :) > > agree with that, just my effort with debian is much smaller than fbsd ports. >>>> Another _very important_ thing is that there is no binary support to >>>> packages that has vulns, >>>> and you have to rebuild them from ports. >>>> >>>> >>>> >>> Well, its one time doing a make package... >>> Even debian has no plus point there (at least in our environment at >>> >> work). >> >>> We pretty much always need our Apache 2 custom build, not the way the >>> Debian projects build it. Thus we have a Debian build box around and >>> >> build >> >>> our own Apache 2.2 package. >>> This is, indeed, the same amount of effort you would have when using >>> FreeBSD. >>> IMO the overhead in Debian to build a package is higher than in FreeBSD, >>> but YMMV. >>> >>> >> If you build packages from source then debian just sux (much more >> complex and long procedure), but there is a tell - "if you do it with >> debian - do it THE DEBIAN WAY"... :-). >> > I am doing it the debian way. Using the debian source package and try to > update from there. Still its a more complex procedure then upgrading a > FreeBSD port. > I just can't use the prebuilt debian packages. So where's the Debian way > from that point?! > deb-src ;-) that's why I like debian when using standartized .debs and prefer fbsd when need custom stuff. > >> I totally agree with that, but on all debian machines I use packages >> provided from debian, because they've made it very modular, >> and I was able to config them the way I need and everything is working >> for me. >> > You're lucky then :) > > >> In 99.99% of the cases when I do apt-get dist-upgrade the machine works >> like a charm after it, and that's a fact (in fbsd when make installworld >> too, but not for ports - which is the focus here). >> > Right. One should never mix up, that Debian is, well, a kernel and a whole > lot of software, whereas in FreeBSD you really have a line between the base > OS and later installed software (ports). > > agree :) >> Actually that's what *BSD prouds with - building everything from source >> (like gentoo), well it's a must to be simplified then (debian where >> everything is supposed to be used from bin .deb) :). >> >> > I really don't think that *BSD is proud about building everything from > source. Since we now even have freebsd-update to binary update FreeBSD > itself. And you usally find prebuilt packages too. > No, No. IMO FreeBSD isn't proud about building everything from source :) > > I do have that feeling about Gentoo users, though *g* > > about gentoo :) YES YES YES ~:) they are VERY proud to build everything from src... :) about fbsd - the most opinions I've heard are argumented with that you get 3-12% percents performance from building srcs with cpu and machine optimizations. That's why I said it. >> About the bug fixes, I think if that's a SECURITY backport it shouldn't >> fix bugs, because I've saw few devs deploying an app and the were using >> 'known bug' in ruby to work with. >> so they were unable to use higher version of ruby that got this bug >> fixed. (we'll obviously a developer mistake in design but if it's in a >> production will take months to redesign - not an option). >> > hhhmm... but then you're really in trouble. This is a situation... well, > hell no. I don't wanna be in this game. > A bug in a peace of software can lead to uncontrolled shutdown or could > even evolve into a security whole. > If possible I don't want bugs. > If there's an application which just runs with the buggy version of ruby > (perl, python, whatever), then lets start beating the devs. Literally > speaking ;) > > agree but when you host VPSes you can't beat the devs... :( >> Which is why maybe it's better not to fix bugs but just vulns in >> SECURITY backports (according to me of course) - if you need that bug >> fixed, then install new version. >> >> > Opinions really will vary on this topic. > In my MySQL example, we want to have the bugfixed version, 'cause those > bugs are really bad. > Same counts for Apache (not as often as MySQL, though). > > right, everything depends on the situations. >>> hhmm... I really can't agree on that statement. >>> If you do your admin work in a clean and sane way, most of the time >>> >> spend >> >>> for updating boxes is spent on testing the change before upgrading. The >>> difference between a "debuild" for building a new package, and then >>> >> apt-get >> >>> upgrade / update them on your box vs. "make package" and pkg_add -r them >>> >> on >> >>> your box is really slim... >>> >>> >>> >> If you build from src on debian - yes, but as I explained i use debian >> .debs and for me it's much faster, because on fbsd ports I have the >> problem described before, >> and is very common case to rebuild and rebuild port until it puts all >> the files in the .tgz :( >> > Well yes, thats true. > However, take a look at the Latest packages on FreeBSD's ftp mirror. There > are new versions available pretty often. > On the other hand, you said, you want to have the same version, just > security fixed. > Well, I bet the FreeBSD ports team just can't do that, due to a lack of > manpower. > Really. Throw in a whole lotta money to employ a few people, or do it your > own. > The existing team is doing a wonderful job in keeping the ports tree up to > date and trying to keep the pr-database as low as possible. > But from what I know the existing team really doesn't look like it can > handle -security branches of the ports tree. > > pretty often? I'm testing almost everytime when portaudit (resp. jailaudit) says there are vluns in some ports, and never get new fixed versions, anyway, I understand that there is not enough manpower that's why I simply say that I'm not satisfied with the current situation, but yes, the ports crew is making a great job. I'm not forcing anyone to do anything, I rescue myself how I can, simply telling my opinion. :) >> So, a story happened recently: >> I've had a disk down (ad2) of course it was in gmirror and the situation >> was 'ah, damn, but it's ok'... >> but... when I rebooted the server it occured that ad2 was ACTIVE and >> maybe last fresh and ad0 was DIRTY, >> ad2 didn't failed at 100% it was responding and found by the bios (and >> kernel) but when files were requested it timed out. >> The problem occured when tried to boot from the second disk (ad0) >> attached with ad2 (at this moment i didn't know that it fails when disk >> io occurs). >> because the ad2 was fresh and ad0 was dirty the gmirror failed to mount >> and boot OS because it was trying to sync data from partly failed disk, >> and it wasn't able to. >> I've shutdowned the machine, plugged out the ad2 disk and fired up again >> hoping gmirror will be smart enough to boot from ad0... but no luck, >> I was forced to mount root filesystem with no mirror (ad0s1a) and run >> the server in no mirror mode so I can have this critical machine running >> while I find a new disk (few hours later I got it). >> And the nightmare's just began... when I placed the new disk, the >> gmirrored volume was still trying to sync from ad2, ofcourse, the ad2 >> had no info on it (thanks god gmirror was smart enough to not copy the >> empty disk). >> I've had to rebuild the whole gmirror partiions, copy the info from a >> non-mirrored disk (ad0) and etc.etc... you know the procedure... this >> took me more than 10 hours and about 5hours downtime on a critical >> machine.... >> > Shocking story. huuu... > I can't comment on that story though, because > - at work, we're on Debian with hardware raids, no software raid even there > - my own experiments with gmirror never lead to such a scenario. I should > try to beat the disk to death, next time I test gmirror ;) > > >> I suppose this has something to do with the priority in gmirror but I >> don't have the broken disk to test - it's being replaced because it's in >> warranty.... but anyways... 10 hours lost and 5hours downtime... >> now I'm purchaseing a 3ware hw raid because I know that I can't trust >> gmirror... >> >> > We don't trust LVM and co either. > But don't ask me why. I believe it's more like a "feeling" than real facts. > So I better don't start to discuss this matter. > I've just got my 3ware raid, I'll get 2 more spare ones and I'm migrating to hw raids too. :) I think the same now. > > >> Another strange thing, I've used to use apache22-worker cutom compiled >> and thread_safe perl, the apache-worker stopped working on a jail (only >> on one!) and I had to add replacements ot pthread.so in /etc/libmap, >> I've been adviced not to use worker (as I did) but why the heck after >> upgrading from 6.3-STABLE to 6.3-STABLE-p3 I got my apache broken and >> also cron stopped working. >> > To few facts. Never happened to me and without details I really can't > comment. > > >> strange uh? and all this is in only one jail (I'm using ez-jail to >> update the world)... if anyone can help me to fix my cron without >> reinstalling this jail I'd be thanksful! >> >> > You should open another mail thread on that topic and try to gather as much > facts as you can. > same problem here, much less effort to migrate to apache22-prefork instead debugging :( - simply no time, I've posted a thread about cron but got stuck, because ktrace doesn't work for the debugging and that's a production and can't compile with debugging symbols.... > > Cheers, > Marian > > > cheer, valqk. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 09:21:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CC921065686 for ; Thu, 12 Jun 2008 09:21:24 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from mrelay1.uni-hannover.de (mrelay1.uni-hannover.de [130.75.2.106]) by mx1.freebsd.org (Postfix) with ESMTP id AB4458FC1A for ; Thu, 12 Jun 2008 09:21:23 +0000 (UTC) (envelope-from gerrit@pmp.uni-hannover.de) Received: from www.pmp.uni-hannover.de (www.pmp.uni-hannover.de [130.75.117.2]) by mrelay1.uni-hannover.de (8.14.2/8.14.2) with ESMTP id m5C9LKXi027879; Thu, 12 Jun 2008 11:21:21 +0200 Received: from pmp.uni-hannover.de (arc.pmp.uni-hannover.de [130.75.117.1]) by www.pmp.uni-hannover.de (Postfix) with SMTP id 47B114F; Thu, 12 Jun 2008 11:21:20 +0200 (CEST) Date: Thu, 12 Jun 2008 11:21:20 +0200 From: Gerrit =?ISO-8859-1?Q?K=FChn?= To: pyunyh@gmail.com Message-Id: <20080612112120.d1b8d059.gerrit@pmp.uni-hannover.de> In-Reply-To: <20080612070126.GF7250@cdnetworks.co.kr> References: <20080527165232.2acbb00f.gerrit@pmp.uni-hannover.de> <3C916EEA-5A2B-4C88-B834-0F47D7D525FA@gmail.com> <20080611092457.82c83083.gerrit@pmp.uni-hannover.de> <20080612032228.GD7250@cdnetworks.co.kr> <20080612085810.072d705d.gerrit@pmp.uni-hannover.de> <20080612070126.GF7250@cdnetworks.co.kr> Organization: Albert-Einstein-Institut (MPI =?ISO-8859-1?Q?f=FCr?= Gravitationsphysik & IGP =?ISO-8859-1?Q?Universit=E4t?= Hannover) X-Mailer: Sylpheed 2.4.8 (GTK+ 2.12.9; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-PMX-Version: 5.4.1.325704, Antispam-Engine: 2.6.0.325393, Antispam-Data: 2008.6.12.20531 Cc: freebsd-stable@freebsd.org Subject: Re: broken re(4) 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, 12 Jun 2008 09:21:24 -0000 On Thu, 12 Jun 2008 16:01:26 +0900 Pyun YongHyeon wrote about Re: broken re(4): PY> > I already did simple benchmarking by using "dd if=/dev/zero PY> > of=file" which gave me several 10s of MByte/s under all PY> > circumstances. Can you recommend one of the benchmarking programs PY> > for more detailed testing? PY> Try netperf or iperf in ports/benchmark. The machine in question as client: ------------------------------------------------------------ Client connecting to 130.75.117.1, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 130.75.117.112 port 56513 connected with 130.75.117.1 port 5001 [ 3] 0.0-10.0 sec 211 MBytes 177 Mbits/sec On the server side: ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 130.75.117.1 port 5001 connected with 130.75.117.112 port 56513 [ 4] 0.0-10.3 sec 211 MBytes 172 Mbits/sec As server: ------------------------------------------------------------ Server listening on TCP port 5001 TCP window size: 64.0 KByte (default) ------------------------------------------------------------ [ 4] local 130.75.117.112 port 5001 connected with 130.75.117.1 port 53843 [ 4] 0.0-10.1 sec 399 MBytes 331 Mbits/sec On the client side: ------------------------------------------------------------ Client connecting to 130.75.117.112, TCP port 5001 TCP window size: 32.5 KByte (default) ------------------------------------------------------------ [ 3] local 130.75.117.1 port 53843 connected with 130.75.117.112 port 5001 [ 3] 0.0-10.1 sec 399 MBytes 331 Mbits/sec Hm, being a server seems to work better? The machine on the other side is also having a re-interface and usually transfers data with 20-30MByte/s. The ITX machine I'm testing is using both of it's re-interfaces in a lagg-configuration right now (laggproto loadbalance). Is this the expected performance? cu Gerrit From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 09:49:17 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B50911065676 for ; Thu, 12 Jun 2008 09:49:17 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id 48C048FC0C for ; Thu, 12 Jun 2008 09:49:17 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id m5C9nAff003523; Thu, 12 Jun 2008 10:49:11 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1K6jQc-0000FR-E9; Thu, 12 Jun 2008 10:49:10 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m5C9nAme065198; Thu, 12 Jun 2008 10:49:10 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m5C9n913065197; Thu, 12 Jun 2008 10:49:09 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Greg Miller In-Reply-To: <4850DCA8.6000709@classic-games.com> References: <4850DCA8.6000709@classic-games.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 12 Jun 2008 10:49:08 +0100 Message-Id: <1213264148.65108.6.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-stable@FreeBSD.org Subject: Re: Adesso AKB-430UG keyboard on 7.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, 12 Jun 2008 09:49:17 -0000 On Thu, 2008-06-12 at 03:22 -0500, Greg Miller wrote: > I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD > 7.0-release-p1, or trying to. The keyboard works fine in Windows, but > with FreeBSD I get the same sort of problems people have described > previous with the Genius SlimStar Pro: the keys behave as if CTRL is > always pressed. > > I'd hate to have to switch to a different keyboard, because it took me > years to find a good alternative to my old Cirque Input Center > keyboard/glidepoint combo. Can you try the following patch please? --- ukbd.c 2008-06-02 14:09:45.000000000 +0100 +++ ukbd.c 2008-06-12 10:44:16.000000000 +0100 @@ -1423,6 +1423,7 @@ init_keyboard(ukbd_state_t *state, int *type, int flags) { usb_endpoint_descriptor_t *ed; + usbd_status err; *type = KB_OTHER; @@ -1447,6 +1448,14 @@ printf("ukbd: unexpected endpoint\n"); return EINVAL; } + + err = usbd_set_protocol(state->ks_iface, 0); + if (err) { + printf("ukbd: set boot protocol failed\n"); + return EIO; + } else { + DPRINTFN(5, ("boot protocol set\n")); + } /* Ignore if SETIDLE fails since it is not crucial. */ usbd_set_idle(state->ks_iface, 0, 0); Thanks, Gavin From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 10:42:24 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C2AD1065671 for ; Thu, 12 Jun 2008 10:42:24 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from fmailhost03.isp.att.net (fmailhost03.isp.att.net [207.115.11.53]) by mx1.freebsd.org (Postfix) with ESMTP id 39E7F8FC15 for ; Thu, 12 Jun 2008 10:42:24 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from [65.7.41.232] (host-65-7-41-232.mem.bellsouth.net?[65.7.41.232]) by isp.att.net (frfwmhc03) with ESMTP id <20080612104222H03000jc00e>; Thu, 12 Jun 2008 10:42:23 +0000 X-Originating-IP: [65.7.41.232] Message-ID: <4850FD50.10503@classic-games.com> Date: Thu, 12 Jun 2008 05:41:20 -0500 From: Greg Miller User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Gavin Atkinson References: <4850DCA8.6000709@classic-games.com> <1213264148.65108.6.camel@buffy.york.ac.uk> In-Reply-To: <1213264148.65108.6.camel@buffy.york.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: Adesso AKB-430UG keyboard on 7.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, 12 Jun 2008 10:42:24 -0000 Gavin Atkinson wrote: > On Thu, 2008-06-12 at 03:22 -0500, Greg Miller wrote: >> I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD >> 7.0-release-p1, or trying to. The keyboard works fine in Windows, but >> with FreeBSD I get the same sort of problems people have described >> previous with the Genius SlimStar Pro: the keys behave as if CTRL is >> always pressed. > Can you try the following patch please? With this patch, it works great as a keyboard. However, the GlidePoint touchpad isn't being detected as a USB mouse and the data is being interpreted as keystrokes. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 10:51:33 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36773106566C for ; Thu, 12 Jun 2008 10:51:33 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id BB3B08FC12 for ; Thu, 12 Jun 2008 10:51:32 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw6.york.ac.uk (mail-gw6.york.ac.uk [144.32.129.26]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id m5CApQ0S012766; Thu, 12 Jun 2008 11:51:26 +0100 (BST) Received: from buffy-128.york.ac.uk ([144.32.128.160] helo=buffy.york.ac.uk) by mail-gw6.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1K6kOs-0001ov-OF; Thu, 12 Jun 2008 11:51:26 +0100 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.2/8.14.2) with ESMTP id m5CApQKs065402; Thu, 12 Jun 2008 11:51:26 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.2/8.14.2/Submit) id m5CApQ5r065401; Thu, 12 Jun 2008 11:51:26 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: buffy.york.ac.uk: ga9 set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson To: Greg Miller In-Reply-To: <4850FD50.10503@classic-games.com> References: <4850DCA8.6000709@classic-games.com> <1213264148.65108.6.camel@buffy.york.ac.uk> <4850FD50.10503@classic-games.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Thu, 12 Jun 2008 11:51:25 +0100 Message-Id: <1213267885.65108.8.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-stable@FreeBSD.org Subject: Re: Adesso AKB-430UG keyboard on 7.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, 12 Jun 2008 10:51:33 -0000 On Thu, 2008-06-12 at 05:41 -0500, Greg Miller wrote: > Gavin Atkinson wrote: > > > On Thu, 2008-06-12 at 03:22 -0500, Greg Miller wrote: > >> I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD > >> 7.0-release-p1, or trying to. The keyboard works fine in Windows, but > >> with FreeBSD I get the same sort of problems people have described > >> previous with the Genius SlimStar Pro: the keys behave as if CTRL is > >> always pressed. > > > > Can you try the following patch please? > > With this patch, it works great as a keyboard. However, the GlidePoint > touchpad isn't being detected as a USB mouse and the data is being > interpreted as keystrokes. Can you confirm that the GlidePoint was working correctly before the patch? Gavin From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 10:53:58 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8B6710656CA for ; Thu, 12 Jun 2008 10:53:58 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from gidgate.gid.co.uk (host-83-146-60-88.dslgb.com [83.146.60.88]) by mx1.freebsd.org (Postfix) with ESMTP id 698B18FC22 for ; Thu, 12 Jun 2008 10:53:58 +0000 (UTC) (envelope-from rb@gid.co.uk) Received: from rbPBP.gid.co.uk ([194.32.164.6]) by gidgate.gid.co.uk (8.13.8/8.13.8) with ESMTP id m5CAgx05071549 for ; Thu, 12 Jun 2008 11:43:07 +0100 (BST) (envelope-from rb@gid.co.uk) Message-Id: <27CFC8F5-F83E-445D-A430-24C3E76A5B72@gid.co.uk> From: Bob Bishop To: stable@freebsd.org Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Thu, 12 Jun 2008 11:43:00 +0100 X-Mailer: Apple Mail (2.924) Cc: Subject: PAE vs USB 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, 12 Jun 2008 10:53:59 -0000 Hi, Is anyone successfully using USB (particularly umass) under PAE on 7.0R? Or, can anyone say for sure that it's not safe? TIA -- Bob Bishop +44 (0)118 940 1243 rb@gid.co.uk fax +44 (0)118 940 1295 From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 10:57:09 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 157851065682 for ; Thu, 12 Jun 2008 10:57:09 +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 BE3C88FC1C for ; Thu, 12 Jun 2008 10:57:08 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K6kUH-00056M-OH for freebsd-stable@freebsd.org; Thu, 12 Jun 2008 10:57:01 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Jun 2008 10:57:01 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Jun 2008 10:57:01 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Thu, 12 Jun 2008 12:56:52 +0200 Lines: 31 Message-ID: References: <27CFC8F5-F83E-445D-A430-24C3E76A5B72@gid.co.uk> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB0778A26D704E8897DEE145A" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: <27CFC8F5-F83E-445D-A430-24C3E76A5B72@gid.co.uk> X-Enigmail-Version: 0.95.0 Sender: news Subject: Re: PAE vs USB 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, 12 Jun 2008 10:57:09 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB0778A26D704E8897DEE145A Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Bob Bishop wrote: > Hi, >=20 > Is anyone successfully using USB (particularly umass) under PAE on 7.0R= ? >=20 > Or, can anyone say for sure that it's not safe? TIA I'm using it on 6-STABLE (PAE+SMP). No problems so far, but it's not very heavily used. --------------enigB0778A26D704E8897DEE145A 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.6 (GNU/Linux) iD8DBQFIUQD0ldnAQVacBcgRAu+bAKDl9+fbIqOxSnnDzlB3ZU3eoDntZgCfWy9B BXBeXC58x794/yusRlhvpbE= =1AkA -----END PGP SIGNATURE----- --------------enigB0778A26D704E8897DEE145A-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 11:21:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A687A1065676; Thu, 12 Jun 2008 11:21:31 +0000 (UTC) (envelope-from lists@pingle.org) Received: from willow.pingle.org (willow.pingle.org [208.149.144.13]) by mx1.freebsd.org (Postfix) with ESMTP id 7AB7B8FC12; Thu, 12 Jun 2008 11:21:31 +0000 (UTC) (envelope-from lists@pingle.org) Received: from localhost (unknown [127.0.0.1]) by willow.pingle.org (Postfix) with ESMTP id 0F7B21145B; Thu, 12 Jun 2008 07:21:31 -0400 (EDT) X-Virus-Scanned: amavisd-new at pingle.org Received: from willow.pingle.org ([127.0.0.1]) by localhost (willow.pingle.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPlkSdO2A3lY; Thu, 12 Jun 2008 07:21:29 -0400 (EDT) Received: from [127.0.0.1] (josie.pingle.org [209.125.59.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jim) by willow.pingle.org (Postfix) with ESMTPSA id 952331145A; Thu, 12 Jun 2008 07:21:27 -0400 (EDT) Message-ID: <485106B6.7050805@pingle.org> Date: Thu, 12 Jun 2008 07:21:26 -0400 From: Jim Pingle User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: Daniel O'Connor References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> <48509419.6060206@pingle.org> <200806121445.30864.doconnor@gsoft.com.au> In-Reply-To: <200806121445.30864.doconnor@gsoft.com.au> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 11:21:31 -0000 Daniel O'Connor wrote: > On Thu, 12 Jun 2008, Jim Pingle wrote: >> I need to see if I can improve the script any (suggestions are most >> welcome) then open a PR to see if it -- or logic like it -- can be >> included in the php-extensions meta port. > > Adding the script to the port seems like the way to go (baring an > upstream fix but it seems like a difficult problem to solve). > > Unfortunately it doesn't help me :( > If I disable everything except either pgsql or mhash (either separately > or together) Apache crashes with.. > > #0 0x28ad6d40 in ?? () > #1 0x281c6f2e in _pthread_main_np () from /lib/libc.so.7 > #2 0x2819fa0c in puts () from /lib/libc.so.7 > #3 0x281a0177 in gethostbyname () from /lib/libc.so.7 > #4 0x08069a12 in ap_get_local_host () > #5 0x08068b9c in ap_fini_vhost_config () > #6 0x0805639c in ap_read_config () > #7 0x0805f133 in standalone_main () > #8 0x08060c1f in main () > > I don't understand why gethostbyname() would call puts() - and why that > would then crash! > > Seems like some threading related wrinkle though as pgsql & mhash are > the only extensions I have that are linked to libthr.so > I'm afraid I wouldn't be much help with this one in that case. I have a vague recollection of gethostbyname() crashing for someone else, though. I thought it had something to do with the ServerName directive and/or an entry in /etc/hosts -- but unfortunately I don't recall the specifics and my Google-fu seems to be failing me this morning. Jim From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 12:57:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88EB11065684 for ; Thu, 12 Jun 2008 12:57:43 +0000 (UTC) (envelope-from SRS0=MY_uw0=W2=webzone.net.au=andrewd@smtp.webzone.net.au) Received: from smtp.webzone.net.au (smtp.webzone.net.au [210.8.36.14]) by mx1.freebsd.org (Postfix) with ESMTP id 44CBF8FC24 for ; Thu, 12 Jun 2008 12:57:43 +0000 (UTC) (envelope-from SRS0=MY_uw0=W2=webzone.net.au=andrewd@smtp.webzone.net.au) Received: from ppp121-45-117-111.lns11.adl6.internode.on.net ([121.45.117.111] helo=[192.168.202.99]) by smtp.webzone.net.au with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1K6mCe-000F1a-1j for freebsd-stable@freebsd.org; Thu, 12 Jun 2008 22:16:56 +0930 Message-ID: <48511ABE.9040207@webzone.net.au> Date: Thu, 12 Jun 2008 22:16:54 +0930 From: Andrew D User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> <48509419.6060206@pingle.org> <200806121445.30864.doconnor@gsoft.com.au> <485106B6.7050805@pingle.org> In-Reply-To: <485106B6.7050805@pingle.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AUTH-WEBZONE: andrewd@webzone.net.au successfully authed as username:andrewd Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 12:57:43 -0000 Jim Pingle wrote: > Daniel O'Connor wrote: >> On Thu, 12 Jun 2008, Jim Pingle wrote: >>> I need to see if I can improve the script any (suggestions are most >>> welcome) then open a PR to see if it -- or logic like it -- can be >>> included in the php-extensions meta port. >> >> Adding the script to the port seems like the way to go (baring an >> upstream fix but it seems like a difficult problem to solve). >> >> Unfortunately it doesn't help me :( >> If I disable everything except either pgsql or mhash (either >> separately or together) Apache crashes with.. >> >> #0 0x28ad6d40 in ?? () >> #1 0x281c6f2e in _pthread_main_np () from /lib/libc.so.7 >> #2 0x2819fa0c in puts () from /lib/libc.so.7 >> #3 0x281a0177 in gethostbyname () from /lib/libc.so.7 >> #4 0x08069a12 in ap_get_local_host () >> #5 0x08068b9c in ap_fini_vhost_config () >> #6 0x0805639c in ap_read_config () >> #7 0x0805f133 in standalone_main () >> #8 0x08060c1f in main () >> >> I don't understand why gethostbyname() would call puts() - and why >> that would then crash! >> >> Seems like some threading related wrinkle though as pgsql & mhash are >> the only extensions I have that are linked to libthr.so >> > > I'm afraid I wouldn't be much help with this one in that case. I have a > vague recollection of gethostbyname() crashing for someone else, though. > I thought it had something to do with the ServerName directive and/or an > entry in /etc/hosts -- but unfortunately I don't recall the specifics > and my Google-fu seems to be failing me this morning. > I'm 99.5% sure that the ServerName Directive has to resolve. > Jim > _______________________________________________ > 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 Thu Jun 12 13:16:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEC8D1065671; Thu, 12 Jun 2008 13:16:16 +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 4113F8FC1B; Thu, 12 Jun 2008 13:16:15 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-123-76.lns11.adl6.internode.on.net [121.45.123.76]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5CDGDRu009612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 12 Jun 2008 22:46:13 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Jim Pingle Date: Thu, 12 Jun 2008 22:46:08 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121445.30864.doconnor@gsoft.com.au> <485106B6.7050805@pingle.org> In-Reply-To: <485106B6.7050805@pingle.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3580763.SdHeTJl9Qx"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806122246.09852.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 13:16:17 -0000 --nextPart3580763.SdHeTJl9Qx Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thu, 12 Jun 2008, Jim Pingle wrote: > > Seems like some threading related wrinkle though as pgsql & mhash > > are the only extensions I have that are linked to libthr.so > > I'm afraid I wouldn't be much help with this one in that case. I have > a vague recollection of gethostbyname() crashing for someone else, > though. I thought it had something to do with the ServerName > directive and/or an entry in /etc/hosts -- but unfortunately I don't > recall the specifics and my Google-fu seems to be failing me this > morning. I did some googling on the stack trace and found.. http://www.nabble.com/php5-and-postgresql-8.2-8.3-td16744979.html I think I'll try switching to Apache 2.. (Right after I upgrade my mail system so I can ditch any 6.x cruft=20 ) =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 --nextPart3580763.SdHeTJl9Qx Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIUSGZ5ZPcIHs/zowRAkuhAJ4usqhG0dtZsF/wk8B9p4fkRCvfOACghsEt 8tkrXJylZjvVKEssEI4iQx4= =yMdy -----END PGP SIGNATURE----- --nextPart3580763.SdHeTJl9Qx-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 14:05:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B07A71065680 for ; Thu, 12 Jun 2008 14:05:54 +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 66D8B8FC12 for ; Thu, 12 Jun 2008 14:05:54 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K6nQy-0005KM-LP for freebsd-stable@freebsd.org; Thu, 12 Jun 2008 14:05:49 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Jun 2008 14:05:48 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 12 Jun 2008 14:05:48 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Thu, 12 Jun 2008 16:05:35 +0200 Lines: 34 Message-ID: References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> <48509419.6060206@pingle.org> <200806121445.30864.doconnor@gsoft.com.au> <485106B6.7050805@pingle.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig2264E0A376F4EE50082C7D94" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.14 (X11/20080505) In-Reply-To: <485106B6.7050805@pingle.org> X-Enigmail-Version: 0.95.0 Sender: news Cc: freebsd-apache@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 14:05:54 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig2264E0A376F4EE50082C7D94 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Jim Pingle wrote: >> Seems like some threading related wrinkle though as pgsql & mhash are >> the only extensions I have that are linked to libthr.so Do you really need threading in pgsql and mhash? Some years ago I had the same problem with apache crashing misterously (not on restart, though) which I've traced to having threading libraries hard-referenced in PHP libraries. If you're not absolutely sure you need it, remove threading libraries from your PHP libraries (for pgsql there's a make config option). --------------enig2264E0A376F4EE50082C7D94 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.6 (GNU/Linux) iD8DBQFIUS0vldnAQVacBcgRAkWaAKCUsbqXYdLc6vBLsGjvQ7vpQ7e1DwCfaso/ 11kPo+Rp41LTxb9Rwl1n9FA= =0Tix -----END PGP SIGNATURE----- --------------enig2264E0A376F4EE50082C7D94-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 15:05:14 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84CBB106567A for ; Thu, 12 Jun 2008 15:05:14 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from mail.farley.org (farley.org [67.64.95.201]) by mx1.freebsd.org (Postfix) with ESMTP id 4BDA08FC13 for ; Thu, 12 Jun 2008 15:05:14 +0000 (UTC) (envelope-from scf@FreeBSD.org) Received: from thor.farley.org (HPooka@thor.farley.org [192.168.1.5]) by mail.farley.org (8.14.3/8.14.3) with ESMTP id m5CF5AaD085433; Thu, 12 Jun 2008 10:05:11 -0500 (CDT) (envelope-from scf@FreeBSD.org) Date: Thu, 12 Jun 2008 10:05:10 -0500 (CDT) From: "Sean C. Farley" To: "Daniel O'Connor" In-Reply-To: <200806121118.45137.doconnor@gsoft.com.au> Message-ID: References: <4846B64F.4090700@minibofh.org> <484FF478.8010405@minibofh.org> <20080611161048.GA66773@eos.sc1.parodius.com> <200806121118.45137.doconnor@gsoft.com.au> User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Spam-Status: No, score=-4.4 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.4 X-Spam-Checker-Version: SpamAssassin 3.2.4 (2008-01-01) on mail.farley.org Cc: Jordi Espasa Clofent , Jeremy Chadwick , freebsd-apache@FreeBSD.org, freebsd-stable@FreeBSD.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 12 Jun 2008 15:05:14 -0000 On Thu, 12 Jun 2008, Daniel O'Connor wrote: > On Thu, 12 Jun 2008, Jeremy Chadwick wrote: >> I myself haven't ever run into extension ordering issues like those >> described (and we've done hosting for years), but I don't doubt those >> who have experienced such. > > I am currently experiencing this :( In the past I shuffled the order > until it worked but that's not a real solution. > > Also if you have gone from 6.x to 7.x make sure that you don't have > any old stuff linked against libc.so.6 loaded into a binary using > libc.so.7. > > It mostly works except with threaded programs and then *kaboom* Also, please try rebuilding PHP5 that has this fix[1] (in ports tree after June 9th). It may or may not help your issue. Sean 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/123911 -- scf@FreeBSD.org From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 15:29:13 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 933F91065675 for ; Thu, 12 Jun 2008 15:29:13 +0000 (UTC) (envelope-from fbsd2@yahoo.com) Received: from web51502.mail.re2.yahoo.com (web51502.mail.re2.yahoo.com [206.190.38.194]) by mx1.freebsd.org (Postfix) with SMTP id 2D4E98FC19 for ; Thu, 12 Jun 2008 15:29:13 +0000 (UTC) (envelope-from fbsd2@yahoo.com) Received: (qmail 57679 invoked by uid 60001); 12 Jun 2008 15:02:31 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Message-ID; b=JSXVpgJxswk+36f4OrGgfSJNdZ4b7Nxf1pyxz2LnW5la2Wfzso50Bm9L73sLutnzgaCCs0/KmyRNAT9/v1loji77FNajORKKNL5KxORD3mPqONJidM5P67ruN5ZJ9taJj5vrUecNhtK0mSFZjATFtEUFeGZHdRYfFwmKhF42G0Q=; Received: from [128.231.88.7] by web51502.mail.re2.yahoo.com via HTTP; Thu, 12 Jun 2008 08:02:31 PDT X-Mailer: YahooMailWebService/0.7.199 Date: Thu, 12 Jun 2008 08:02:31 -0700 (PDT) From: fbsd2 To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Message-ID: <372128.56919.qm@web51502.mail.re2.yahoo.com> X-Mailman-Approved-At: Thu, 12 Jun 2008 15:33:44 +0000 Subject: 80 Mb / enough for 7.x? OK to delete /stand/ and /modules/ ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fbsd2@yahoo.com List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2008 15:29:13 -0000 Greetings list, Given recent EOL announcements, I'm trying to upgrade an ancient machine from 5.5 to 7. It has 80 Mb total in the root partition, /home/, /var/, /usr/, and /tmp/ on other partitions, and NFS mounts /usr/src, /usr/obj, and /usr/ports from a slightly newer/faster box. I've seen http://www.freebsd.org/releases/7.0R/relnotes.html and http://marc.info/?l=freebsd-stable&m=121278826119286&w=2 which seem to suggest that even with INSTALL_NODEBUG during buildkernel, 7 might not fit in an 80 Mb /. Must I partition a new disk to give more space to /, or can I find more space by deleting /stand/, /modules/, and possibly /rescue/ to shoehorn a custom 7.x kernel in the available space? TIA Alex __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 18:33:16 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B550106566C for ; Thu, 12 Jun 2008 18:33:16 +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 0EC068FC15 for ; Thu, 12 Jun 2008 18:33:15 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (adsl-68-252-58-163.dsl.wotnoh.ameritech.net [68.252.58.163]) (authenticated bits=0) by mail.united-ware.com (8.14.2/8.14.2) with ESMTP id m5CIUlFm015478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 12 Jun 2008 14:30:48 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-stable@freebsd.org, fbsd2@yahoo.com Date: Thu, 12 Jun 2008 14:16:38 -0400 User-Agent: KMail/1.9.7 References: <372128.56919.qm@web51502.mail.re2.yahoo.com> In-Reply-To: <372128.56919.qm@web51502.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2364415.1Zd2VII2kH"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806121416.46040.mistry.7@osu.edu> X-Virus-Scanned: ClamAV 0.93/7451/Thu Jun 12 09:28:58 2008 on mail.united-ware.com X-Virus-Status: Clean Cc: Subject: Re: 80 Mb / enough for 7.x? OK to delete /stand/ and /modules/ ? 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, 12 Jun 2008 18:33:16 -0000 --nextPart2364415.1Zd2VII2kH Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 12 June 2008, fbsd2 wrote: > Greetings list, > > Given recent EOL announcements, I'm trying to upgrade an ancient > machine from 5.5 to 7. It has 80 Mb total in the root partition, > /home/, /var/, /usr/, and /tmp/ on other partitions, and NFS mounts > /usr/src, /usr/obj, and /usr/ports from a slightly newer/faster > box. I've seen > > http://www.freebsd.org/releases/7.0R/relnotes.html and > http://marc.info/?l=3Dfreebsd-stable&m=3D121278826119286&w=3D2 > > which seem to suggest that even with INSTALL_NODEBUG during > buildkernel, 7 might not fit in an 80 Mb /. Must I partition a new > disk to give more space to /, or can I find more space by deleting > /stand/, /modules/, and possibly /rescue/ to shoehorn a custom 7.x > kernel in the available space? TIA It should fit, though you may have issues with kernel.old pushing you=20 over the limit. =2D-=20 Anish Mistry --nextPart2364415.1Zd2VII2kH Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAkhRaAYACgkQxqA5ziudZT20vQCgvLhfMLfl/aZcrnor3yvpbIGG zdIAoJ04L10aaBu+ibgb8p01tm7X0pE8 =OE1H -----END PGP SIGNATURE----- --nextPart2364415.1Zd2VII2kH-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 18:42:06 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A73771065674 for ; Thu, 12 Jun 2008 18:42:06 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 7DB9A8FC19 for ; Thu, 12 Jun 2008 18:42:06 +0000 (UTC) (envelope-from illoai@gmail.com) Received: by rv-out-0506.google.com with SMTP id b25so4472085rvf.43 for ; Thu, 12 Jun 2008 11:42:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=gOKyLYrvekUNeLGP6rW2L34hs5iu0hcbachr0GCj350=; b=SSoS0/9fajOPM2u+i+27bbn8lX5pNMVgAtBDheZwp6+7LBiN/kxLD+HZE4QLNW8j6x /bc8ROcb0YllPw0jljcSiaJw9Hio5ioozssVGTQ6Dtx+b7lGWr5J2SOJklxEACqh7upt pEnJIMBcyxOgxr6WknrWE07a/dvugSqLtbIVE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=EIWGCI3IhIlXVFUfp6zfUElBt/Yj8PZEZC1kwDvyAxOdjfHAZigGeqcc0gK5YC4pAH aQQIWu1SHFZeEdQmw4im9hVjettvXkwBmh9Fhb4/8pP1P7g6unChqC1f+uAS7LYE4Nxm QVxbfzgENoCsOB7CoZtscevzEhqqR+UWAXXio= Received: by 10.140.144.1 with SMTP id r1mr1264456rvd.10.1213294371118; Thu, 12 Jun 2008 11:12:51 -0700 (PDT) Received: by 10.141.189.12 with HTTP; Thu, 12 Jun 2008 11:12:50 -0700 (PDT) Message-ID: Date: Thu, 12 Jun 2008 13:12:50 -0500 From: "illoai@gmail.com" To: fbsd2@yahoo.com In-Reply-To: <372128.56919.qm@web51502.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <372128.56919.qm@web51502.mail.re2.yahoo.com> Cc: freebsd-stable@freebsd.org Subject: Re: 80 Mb / enough for 7.x? OK to delete /stand/ and /modules/ ? 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, 12 Jun 2008 18:42:06 -0000 2008/6/12 fbsd2 : > Greetings list, > > Given recent EOL announcements, I'm trying to upgrade an ancient machine from 5.5 to 7. It has 80 Mb total in the root partition, /home/, /var/, /usr/, and /tmp/ on other partitions, and NFS mounts /usr/src, /usr/obj, and /usr/ports from a slightly newer/faster box. I've seen > > http://www.freebsd.org/releases/7.0R/relnotes.html and > http://marc.info/?l=freebsd-stable&m=121278826119286&w=2 > > which seem to suggest that even with INSTALL_NODEBUG during buildkernel, 7 might not fit in an 80 Mb /. Must I partition a new disk to give more space to /, or can I find more space by deleting /stand/, /modules/, and possibly /rescue/ to shoehorn a custom 7.x kernel in the available space? TIA > If you know you do not need the modules, by all means, to do away with them is space back to you. If you are building from source, you can use the: MODULES_OVERRIDE= variable in /etc/make.conf When you are at the # make installworld stage you can likely delete /stand (I believe it is not used on >=6.x) (Though I am not sitting at the machine now) I believe that / on my 7.x box is about 46M. -- -- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 20:35:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07173106564A for ; Thu, 12 Jun 2008 20:35:25 +0000 (UTC) (envelope-from attos.janus@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.31]) by mx1.freebsd.org (Postfix) with ESMTP id AA48A8FC13 for ; Thu, 12 Jun 2008 20:35:24 +0000 (UTC) (envelope-from attos.janus@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so1904989ywe.13 for ; Thu, 12 Jun 2008 13:35:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=0WFTbB45x/T8Sx6HbgisPgYdW57btE7GnSgUiRhg7uQ=; b=tdaHioMIBHyhFXZlIy1YBRC/YBscQe9dbExpuHQGl1tk08jRHa/RePxNSxg11BwUY8 /BraBTBuDWE0io+kzKleJOkEk7UBAeo4VeKUnKrdFhy9fyK3bQMk7gXLeQN02+tPfH3F IniMas68U8ipaAn9UHb0ISFWncC+hjRmwHs4I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=js1MvnRLCFBU19yklyUP1kc+/+9M0Ml6PWG/QfW6NmycgZLCwaWv1B5yTTO+qbm/TR Dj8rPmh9Yw27iNnpZ++DcOJVGVT3Lr81ZGUKOtTZVc62Zp1/V0Nt2GWy/ahK1ehlu3uc ZCERCrdMNE8UJ/Ye1MxQB9H8QWcuZUYwJ0PpE= Received: by 10.151.51.18 with SMTP id d18mr2961681ybk.88.1213301313107; Thu, 12 Jun 2008 13:08:33 -0700 (PDT) Received: by 10.151.158.14 with HTTP; Thu, 12 Jun 2008 13:08:33 -0700 (PDT) Message-ID: <5297d6fd0806121308s3c5185ebs9717b8c14f7a7deb@mail.gmail.com> Date: Thu, 12 Jun 2008 16:08:33 -0400 From: Attos To: freebsd-stable@freebsd.org In-Reply-To: <5297d6fd0806111510p15358eb0idc03c81d9fe38e87@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <5297d6fd0806111510p15358eb0idc03c81d9fe38e87@mail.gmail.com> Subject: How to upgrade openssl after upgrading from 6.2 to 7.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, 12 Jun 2008 20:35:25 -0000 Hello list, I just upgraded my workstation from 6.2 to 7.0 but I haven't been able to upgrade all the ports. OpenSSL is giving me problems when trying to upgrade (with portupgrade). The message I get is that the it's marked as ignore because it conflicts with the base: # portupgrade security/openssl-stable ** Port marked as IGNORE: security/openssl-stable: Conflicts with version in the base ** Listing the failed packages (-:ignored / *:skipped / !:failed) - security/openssl-stable (marked as IGNORE) How do I fix this? TIA -- Attos Janus From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 20:56:30 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CBFE1065671 for ; Thu, 12 Jun 2008 20:56:30 +0000 (UTC) (envelope-from SRS0=8394e90614c9f2b93eebb5b1ce31ce2f911bcafc=730=es.net=oberman@es.net) Received: from postal1.es.net (postal1.es.net [IPv6:2001:400:14:3::6]) by mx1.freebsd.org (Postfix) with ESMTP id 6C4B98FC14 for ; Thu, 12 Jun 2008 20:56:30 +0000 (UTC) (envelope-from SRS0=8394e90614c9f2b93eebb5b1ce31ce2f911bcafc=730=es.net=oberman@es.net) Received: from ptavv.es.net (ptavv.es.net [198.128.4.29]) by postal1.es.net (Postal Node 1) with ESMTP (SSL) id SAQ04429; Thu, 12 Jun 2008 13:56:29 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 3D0ED4500E; Thu, 12 Jun 2008 13:56:29 -0700 (PDT) To: Attos In-Reply-To: Your message of "Thu, 12 Jun 2008 16:08:33 EDT." <5297d6fd0806121308s3c5185ebs9717b8c14f7a7deb@mail.gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1213304189_21466P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Thu, 12 Jun 2008 13:56:29 -0700 From: "Kevin Oberman" Message-Id: <20080612205629.3D0ED4500E@ptavv.es.net> X-Sender-IP: 198.128.4.29 X-Sender-Domain: es.net X-Recipent: ;; X-Sender: X-To_Name: Attos X-To_Domain: gmail.com X-To: Attos X-To_Email: attos.janus@gmail.com X-To_Alias: attos.janus Cc: freebsd-stable@freebsd.org Subject: Re: How to upgrade openssl after upgrading from 6.2 to 7.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, 12 Jun 2008 20:56:30 -0000 --==_Exmh_1213304189_21466P Content-Type: text/plain; charset=us-ascii Content-Disposition: inline > Date: Thu, 12 Jun 2008 16:08:33 -0400 > From: Attos > Sender: owner-freebsd-stable@freebsd.org > > Hello list, > I just upgraded my workstation from 6.2 to 7.0 but I haven't been able > to upgrade all the ports. > OpenSSL is giving me problems when trying to upgrade (with > portupgrade). The message I get is that the it's marked as ignore > because it conflicts with the base: > > # portupgrade security/openssl-stable > ** Port marked as IGNORE: security/openssl-stable: > Conflicts with version in the base > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > - security/openssl-stable (marked as IGNORE) > > How do I fix this? You don't. openssl-stable is the same version of openssl that is already in the base system in 7.0, so you should remove the port (pkg_deinstall openssl-\*). -- 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 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 --==_Exmh_1213304189_21466P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) Comment: Exmh version 2.5 06/03/2002 iD8DBQFIUY19kn3rs5h7N1ERAqw8AJ4l5GC0r8cAulzia1Vpj6FGVYzyywCcDrgt 4BZF7gnOvYKkRMjRliJZk9I= =jeJ+ -----END PGP SIGNATURE----- --==_Exmh_1213304189_21466P-- From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 23:08:31 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 110B81065674 for ; Thu, 12 Jun 2008 23:08:31 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id C52208FC13 for ; Thu, 12 Jun 2008 23:08:30 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (78.6.192-77.rev.gaoland.net [77.192.6.78]) by smtp.lamaiziere.net (Postfix) with ESMTP id 9C5D411805A8 for ; Fri, 13 Jun 2008 00:48:50 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 919A7445B5C for ; Fri, 13 Jun 2008 00:48:49 +0200 (CEST) Date: Fri, 13 Jun 2008 00:48:47 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: freebsd-stable@freebsd.org Message-ID: <20080613004847.09f9b089@baby-jane-lamaiziere-net.local> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [7-STABLE] ping -s 4000 with ipsec 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: Thu, 12 Jun 2008 23:08:31 -0000 [FreeBSD 7-STABLE/i386] Hello, I've got a 100 % reproductible panic with ipsec when using a 'ping -s 4000'. It works without ipsec My ipsec setup is very simple, i just use setkey: /etc/ipsec.conf flush; spdflush; add 192.168.1.21 192.168.1.200 esp 1011 -E rijndael-cbc "0123456789012345"; add 192.168.1.200 192.168.1.21 esp 1012 -E rijndael-cbc "0123456789012345"; spdadd 192.168.1.200 192.168.1.21 any -P out ipsec esp/transport//require; spdadd 192.168.1.21 192.168.1.200 any -P in ipsec esp/transport//require; I tried to use des-cbc with the same panic. -------------------- Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x4100be00 fault code = supervisor read, page not present instruction pointer = 0x20:0xc079985e stack pointer = 0x28:0xd61a0744 frame pointer = 0x28:0xd61a076c code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1175 (ping) trap number = 12 panic: page fault Uptime: 9m5s Physical memory: 503 MB Dumping 87 MB: 72 56 40 24 8 #0 doadump () at pcpu.h:195 195 pcpu.h: No such file or directory. in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0556273 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055646f in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc079b91c in trap_fatal (frame=0xd61a0704, eva=1090567680) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc079bba0 in trap_pfault (frame=0xd61a0704, usermode=0, eva=1090567680) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc079c529 in trap (frame=0xd61a0704) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0789f2b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc079985e in generic_bcopy () at /usr/src/sys/i386/i386/support.s:498 #8 0xc1f7267e in ?? () #9 0x8fb82d87 in ?? () #10 0x361fe9de in ?? () #11 0x39402686 in ?? () #12 0x00000fa0 in ?? () #13 0xc29cf380 in ?? () #14 0xc2ea9654 in ?? () #15 0x00000000 in ?? () #16 0xd61a095c in ?? () #17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950, hint=-1616994916) at cryptodev_if.h:53 Previous frame inner to this frame (corrupt stack?) (kgdb) ------------- Thansk, regards. From owner-freebsd-stable@FreeBSD.ORG Thu Jun 12 23:57:36 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 151371065670 for ; Thu, 12 Jun 2008 23:57:36 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED9A48FC0A; Thu, 12 Jun 2008 23:57:33 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <4851B7EF.7060905@FreeBSD.org> Date: Fri, 13 Jun 2008 01:57:35 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Patrick_Lamaizi=E8re?= References: <20080613004847.09f9b089@baby-jane-lamaiziere-net.local> In-Reply-To: <20080613004847.09f9b089@baby-jane-lamaiziere-net.local> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: [7-STABLE] ping -s 4000 with ipsec 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: Thu, 12 Jun 2008 23:57:36 -0000 Patrick Lamaizière wrote: > generic_bcopy () at /usr/src/sys/i386/i386/support.s:498 #8 0xc1f7267e > in ?? () #9 0x8fb82d87 in ?? () > #10 0x361fe9de in ?? () > #11 0x39402686 in ?? () > #12 0x00000fa0 in ?? () > #13 0xc29cf380 in ?? () > #14 0xc2ea9654 in ?? () > #15 0x00000000 in ?? () > #16 0xd61a095c in ?? () > #17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950, > hint=-1616994916) at cryptodev_if.h:53 > Previous frame inner to this frame (corrupt stack?) > (kgdb) Unfortunately the trace is bogus. Try to rebuild with -O instead of -O2 and reproduce the panic. Kris From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 06:04:05 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46ED5106566B for ; Fri, 13 Jun 2008 06:04:05 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1EB8D8FC12 for ; Fri, 13 Jun 2008 06:04:04 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from [192.168.1.104] (modemcable125.163-21-96.mc.videotron.ca [96.21.163.125]) by smtp.cyberfingers.net (Postfix) with ESMTP id BA52EAB6C32 for ; Fri, 13 Jun 2008 02:04:13 -0400 (EDT) Message-ID: <48520DD5.7080409@pldrouin.net> Date: Fri, 13 Jun 2008 02:04:05 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.14 (X11/20080502) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: boot0 is hanging... 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, 13 Jun 2008 06:04:05 -0000 Hi, I just did two different installations of 7.0-stable on a new machine and I have some issues with the boot0 boot loader. I have two identical drives on that machine. The first two slices on the drives are supposed to be bootable and they are mirrored with gmirror: gmirror label -v -h -b load boot1 ad4s1a ad6s1a gmirror label -v -h -b load boot2 ad6s2a ad4s2a The problem I have is that I can only boot the second slice from ad6, not from ad4. boot0 does nothing when I press F2 from the menu for the first drive. I don't get any error message. It does nothing until I select another item in the menu. I can boot the first slice from either ad4 or ad6. I have tried rebuilding the raid and changing the priority of the drive with gmirror, but it didn't change anything. I also tried to remove ad6s2a from the mirror, but it didn't fix it either. To install boot0, I used: sysctl kern.geom.debugflags=16 boot0cfg -B -m 0x3 -s 1 ad4 boot0cfg -B -m 0x3 -s 1 ad6 What could be causing this exactly? Thank you! From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 07:15:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E475106567A for ; Fri, 13 Jun 2008 07:15:03 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from smtp02.cdmon.com (smtp02.cdmon.com [212.36.74.229]) by mx1.freebsd.org (Postfix) with ESMTP id 38B158FC22 for ; Fri, 13 Jun 2008 07:15:03 +0000 (UTC) (envelope-from jespasac@minibofh.org) Received: from [192.168.0.29] (62.Red-217-126-43.staticIP.rima-tde.net [217.126.43.62]) by smtp02.cdmon.com (Postfix) with ESMTP id 7DE7A454CC for ; Fri, 13 Jun 2008 09:15:01 +0200 (CEST) Message-ID: <48521E74.90708@minibofh.org> Date: Fri, 13 Jun 2008 09:15:00 +0200 From: Jordi Espasa Clofent User-Agent: Thunderbird 1.5.0.12 (X11/20080430) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4846B64F.4090700@minibofh.org> <484775D4.4090509@p6m7g8.com> <48481A02.2050502@minibofh.org> <484FF478.8010405@minibofh.org> <20080611161048.GA66773@eos.sc1.parodius.com> In-Reply-To: <20080611161048.GA66773@eos.sc1.parodius.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 13 Jun 2008 07:15:03 -0000 > Many people have reported that the *order* of the extensions in > extensions.ini has adverse (positive) effects on PHP segfaults on > FreeBSD. > > I myself haven't ever run into extension ordering issues like those > described (and we've done hosting for years), but I don't doubt those > who have experienced such. Yes Jeremy, I known. I also don't doubt your words, but in my case the order of the extensions seems not any effect. The only solution has been comment the mentioned mbash extension. -- Thanks, Jordi Espasa Clofent From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 08:57:32 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17A101065671; Fri, 13 Jun 2008 08:57:32 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from fmailhost02.isp.att.net (fmailhost02.isp.att.net [204.127.217.102]) by mx1.freebsd.org (Postfix) with ESMTP id EB8228FC1B; Fri, 13 Jun 2008 08:57:31 +0000 (UTC) (envelope-from gmiller@classic-games.com) Received: from [65.7.37.126] (host-65-7-37-126.mem.bellsouth.net?[65.7.37.126]) by isp.att.net (frfwmhc02) with ESMTP id <20080613085728H02005ufa9e>; Fri, 13 Jun 2008 08:57:30 +0000 X-Originating-IP: [65.7.37.126] Message-ID: <48523634.4000909@classic-games.com> Date: Fri, 13 Jun 2008 03:56:20 -0500 From: Greg Miller User-Agent: Thunderbird 2.0.0.14 (X11/20080609) MIME-Version: 1.0 To: Gavin Atkinson References: <4850DCA8.6000709@classic-games.com> <1213264148.65108.6.camel@buffy.york.ac.uk> <4850FD50.10503@classic-games.com> <1213267885.65108.8.camel@buffy.york.ac.uk> In-Reply-To: <1213267885.65108.8.camel@buffy.york.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Adesso AKB-430UG keyboard on 7.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: Fri, 13 Jun 2008 08:57:32 -0000 Gavin Atkinson wrote: > On Thu, 2008-06-12 at 05:41 -0500, Greg Miller wrote: >> Gavin Atkinson wrote: >> >>> On Thu, 2008-06-12 at 03:22 -0500, Greg Miller wrote: >>>> I'm using an AKB-430UG USB keyboard ("Win-Touch Pro") on FreeBSD >>>> 7.0-release-p1, or trying to. The keyboard works fine in Windows, but >>>> with FreeBSD I get the same sort of problems people have described >>>> previous with the Genius SlimStar Pro: the keys behave as if CTRL is >>>> always pressed. >> >>> Can you try the following patch please? >> With this patch, it works great as a keyboard. However, the GlidePoint >> touchpad isn't being detected as a USB mouse and the data is being >> interpreted as keystrokes. > > Can you confirm that the GlidePoint was working correctly before the > patch? No. Connecting the keyboard generates a console message indicating the ukbd device attached, but doesn't generate a ums attach message, so I'm thinking that it doesn't work with or without the patch. -- http://www.velocityvector.com/ | http://www.classic-games.com/ I'd rather hunt with Dick Cheney than ride with Ted Kennedy. From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 09:06:46 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF9C51065675 for ; Fri, 13 Jun 2008 09:06:46 +0000 (UTC) (envelope-from timothy.wilson87@gmail.com) Received: from ti-out-0910.google.com (ti-out-0910.google.com [209.85.142.190]) by mx1.freebsd.org (Postfix) with ESMTP id 467568FC1A for ; Fri, 13 Jun 2008 09:06:46 +0000 (UTC) (envelope-from timothy.wilson87@gmail.com) Received: by ti-out-0910.google.com with SMTP id d27so1217218tid.3 for ; Fri, 13 Jun 2008 02:06:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=hco2pAAwsHcYcAl5Jggk0/K4icC6YlR4gcPjRVPthOQ=; b=GxRAQP8YxqbMj4Dnat5l1aYSUJGhSIeivSdzOjDx4xykjuZbAiwOYPRGzbNEAgeXgq bjwJ8YnLlUiu6daNHTgZotXqHSaptAnJYChn3FPUZu5WO8pQlrMcZ6GoHkAv9dHW8F1u +lxRiYi0noc3aI8IKC0coeHIM0OS3VIUo+QBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=iwib977WhbwNdB58rFkcX5ILrCmThwXqZXbVpG0Z/k8tjSC52YDwK5FJNQRXnMgo4z arZwrXkhGQ1ZhdzcUusU3eLAvNHaa2fwSdtSHHK2XhdBBBXt/ko24pIvZ74q6ac1958Y C8LrMwNt3IyF8YaqMbaGC6iw6J02c9/7+zG7c= Received: by 10.110.70.5 with SMTP id s5mr1514069tia.27.1213346422198; Fri, 13 Jun 2008 01:40:22 -0700 (PDT) Received: by 10.110.28.6 with HTTP; Fri, 13 Jun 2008 01:40:22 -0700 (PDT) Message-ID: Date: Fri, 13 Jun 2008 18:40:22 +1000 From: "Timothy Wilson" To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: ZFS version 8 on 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, 13 Jun 2008 09:06:46 -0000 Hello everyone, I know -stable is supposed to be, well, stable, but I seem to be in a bit of a pickle. I'm trying to import my zfs file system from a Macintosh machine. It was created at version 8. Being new to zfs, I did not realise that FreeBSD would be running at a lower version; I thought zfs was zfs! Of course, trying to import my zpool fails, complaining that the version is too new. freebsd# zpool import bigstore cannot import 'bigstore': pool is formatted using a newer ZFS version So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. Does anyone know if I'll be able to import zfs v8, or am I wasting my time? I'd prefer to follow -stable, but if I must follow -current, then golly goshkins, I'll have no choice! Kind regards, Timothy. From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 09:32:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9C6D106567B for ; Fri, 13 Jun 2008 09:32:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: from mx01.sc1.parodius.com (mx01.sc1.parodius.com [72.20.106.3]) by mx1.freebsd.org (Postfix) with ESMTP id 906258FC0A for ; Fri, 13 Jun 2008 09:32:25 +0000 (UTC) (envelope-from jdc@parodius.com) Received: by mx01.sc1.parodius.com (Postfix, from userid 1000) id 56A991CC060; Fri, 13 Jun 2008 02:32:25 -0700 (PDT) Date: Fri, 13 Jun 2008 02:32:25 -0700 From: Jeremy Chadwick To: Timothy Wilson Message-ID: <20080613093225.GA45459@eos.sc1.parodius.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on 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, 13 Jun 2008 09:32:25 -0000 On Fri, Jun 13, 2008 at 06:40:22PM +1000, Timothy Wilson wrote: > Hello everyone, > > I know -stable is supposed to be, well, stable, but I seem to be in a > bit of a pickle. > > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. > > freebsd# zpool import bigstore > cannot import 'bigstore': pool is formatted using a newer ZFS version > > So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. > Does anyone know if I'll be able to import zfs v8, or am I wasting my > time? I'd prefer to follow -stable, but if I must follow -current, > then golly goshkins, I'll have no choice! I don't know what the current migration status is of ZFS on FreeBSD to a newer version. I don't think -CURRENT/HEAD has a newer ZFS either, so I think you're out of luck with regards to an "easy" migration. If I was in your shoes, I would not downgrade the pool -- I would simply stop using ZFS and use a filesystem that is fully compatible between OS X and FreeBSD. *cue someone chiming in with the usual "ZFS is experimental on FreeBSD, blah blah blah" rhetoric* :-) Summary: you're out of luck. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 09:54:04 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD7901065672 for ; Fri, 13 Jun 2008 09:54:04 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 285F68FC12; Fri, 13 Jun 2008 09:54:03 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <485243BB.7050604@FreeBSD.org> Date: Fri, 13 Jun 2008 11:54:03 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: Timothy Wilson References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on 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, 13 Jun 2008 09:54:04 -0000 Timothy Wilson wrote: > Hello everyone, > > I know -stable is supposed to be, well, stable, but I seem to be in a > bit of a pickle. > > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. > > freebsd# zpool import bigstore > cannot import 'bigstore': pool is formatted using a newer ZFS version > > So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. > Does anyone know if I'll be able to import zfs v8, or am I wasting my > time? I'd prefer to follow -stable, but if I must follow -current, > then golly goshkins, I'll have no choice! It is planned to update to a newer ZFS release in HEAD, but this has not happened yet (let alone in 7.x). I don't know if it is possible to downgrade a pool - you should check the ZFS documentation/support materials. Kris From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 09:56:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD0581065676 for ; Fri, 13 Jun 2008 09:56:21 +0000 (UTC) (envelope-from kometen@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.155]) by mx1.freebsd.org (Postfix) with ESMTP id 5F70C8FC13 for ; Fri, 13 Jun 2008 09:56:20 +0000 (UTC) (envelope-from kometen@gmail.com) Received: by fg-out-1718.google.com with SMTP id l26so3226554fgb.35 for ; Fri, 13 Jun 2008 02:56:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=CJ+f1870681UZ/eVaD+PW6Nu59LNw3/3FCjyz87qAuk=; b=eezo8OxMGhmZWujrhqtASIp07Qr9WrginJAC8OT0ljBPrw11cJoJgOPbi3l+WPhsKi S3wem3a0Kt+0As74VSp1Pza1vYRLDFd7QSBZNqYfkC8lCK5r6WVIJN3CT3tf6XeH9nkd cqeLMAy+Tij0MAE6bQS43iq3FpMdlDjXtTFzc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=IvH0eauBa452IrVX4pGPD/1ELOweDO+AY3RrllktTK5p8QqI+eqkr9+eHcG2tHWEai lIJoF/7kFbaNMVRx7+bRrh3i6K57JQe9vyiRs7HFHyUE8kksYvq3q8YTV/JYJgxasdF+ K9HUsSGWsLJV5vXuy84wpW15ViJ+MFhQXqGpc= Received: by 10.86.100.19 with SMTP id x19mr3663812fgb.61.1213350979966; Fri, 13 Jun 2008 02:56:19 -0700 (PDT) Received: by 10.86.79.5 with HTTP; Fri, 13 Jun 2008 02:56:19 -0700 (PDT) Message-ID: Date: Fri, 13 Jun 2008 11:56:19 +0200 From: "Claus Guttesen" To: "Jeremy Chadwick" In-Reply-To: <20080613093225.GA45459@eos.sc1.parodius.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080613093225.GA45459@eos.sc1.parodius.com> Cc: Timothy Wilson , freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on 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, 13 Jun 2008 09:56:21 -0000 >> So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. >> Does anyone know if I'll be able to import zfs v8, or am I wasting my >> time? I'd prefer to follow -stable, but if I must follow -current, >> then golly goshkins, I'll have no choice! > > I don't know what the current migration status is of ZFS on FreeBSD to a > newer version. I don't think -CURRENT/HEAD has a newer ZFS either, so I > think you're out of luck with regards to an "easy" migration. > > If I was in your shoes, I would not downgrade the pool -- I would simply > stop using ZFS and use a filesystem that is fully compatible between OS > X and FreeBSD. *cue someone chiming in with the usual "ZFS is > experimental on FreeBSD, blah blah blah" rhetoric* :-) I tried to create a zfs-pool on Solaris and was unable to import it to FreeBSD. So there are still some issues in relation to OS-platform-migrations. But other than that is this not a somewhat pessimistic approach not to try things out? :-) Many years ago (os x 10.0 or 10.1 I think) I tried to create an UFS-volume on os x but this was not recognized by FreeBSD (ver. 4.x). What other fs-type will work between os x and FreeBSD? FAT comes to my mind. -- regards Claus When lenity and cruelty play for a kingdom, the gentlest gamester is the soonest winner. Shakespeare From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 10:07:54 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DCA161065671 for ; Fri, 13 Jun 2008 10:07:54 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from nagual.nl (cc20684-a.assen1.dr.home.nl [82.74.10.158]) by mx1.freebsd.org (Postfix) with ESMTP id A069B8FC16 for ; Fri, 13 Jun 2008 10:07:53 +0000 (UTC) (envelope-from dick@nagual.nl) Received: from nagual.nl (midgard.nagual.nl [192.168.11.32]) by nagual.nl (8.13.8+Sun/8.13.8/yanta) with ESMTP id m5DA8Ro9008918; Fri, 13 Jun 2008 12:08:27 +0200 (CEST) Received: from 82.92.9.111 (SquirrelMail authenticated user dick) by nagual.nl with HTTP; Fri, 13 Jun 2008 12:08:27 +0200 (CEST) Message-ID: <26867.82.92.9.111.1213351707.squirrel@nagual.nl> In-Reply-To: References: Date: Fri, 13 Jun 2008 12:08:27 +0200 (CEST) From: "dick hoogendijk" To: "Timothy Wilson" User-Agent: SquirrelMail/1.4.13 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Scanned-By: MIMEDefang 2.63 on 192.168.11.35 Cc: freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on 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, 13 Jun 2008 10:07:55 -0000 Timothy Wilson wrote: > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. Have you tried to send a snapshot on you Mac and receive that snapshot on your FreeBSD machine? -- Dick Hoogendijk -- PGP/GnuPG key: F86289CE ++ http://nagual.nl/ | SunOS 10u5 05/08 ++ From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 12:34:43 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C9D11065682 for ; Fri, 13 Jun 2008 12:34:43 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from smtp.cyberfingers.net (smtp.cyberfingers.net [198.177.254.227]) by mx1.freebsd.org (Postfix) with ESMTP id 51BC48FC1C for ; Fri, 13 Jun 2008 12:34:43 +0000 (UTC) (envelope-from pldrouin@pldrouin.net) Received: from ldaemon.pldrouin.net (modemcable125.163-21-96.mc.videotron.ca [96.21.163.125]) by smtp.cyberfingers.net (Postfix) with ESMTP id 4E025AB6C6F for ; Fri, 13 Jun 2008 08:34:52 -0400 (EDT) Message-ID: <4852695D.5030206@pldrouin.net> Date: Fri, 13 Jun 2008 08:34:37 -0400 From: Pierre-Luc Drouin User-Agent: Thunderbird 2.0.0.14 (X11/20080503) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: boot0 is hanging... 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, 13 Jun 2008 12:34:43 -0000 Hi, I just did two different installations of 7.0-stable on a new machine and I have some issues with the boot0 boot loader. I have two identical drives on that machine. The first two slices on the drives are supposed to be bootable and they are mirrored with gmirror: gmirror label -v -h -b load boot1 ad4s1a ad6s1a gmirror label -v -h -b load boot2 ad6s2a ad4s2a The problem I have is that I can only boot the second slice from ad6, not from ad4. boot0 does nothing when I press F2 from the menu for the first drive. I don't get any error message. It does nothing until I select another item in the menu. I can boot the first slice from either ad4 or ad6. I have tried rebuilding the raid and changing the priority of the drive with gmirror, but it didn't change anything. I also tried to remove ad6s2a from the mirror, but it didn't fix it either. To install boot0, I used: sysctl kern.geom.debugflags=16 boot0cfg -B -m 0x3 -s 1 ad4 boot0cfg -B -m 0x3 -s 1 ad6 What could be causing this exactly? Thank you! From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 14:13:25 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 63CDF10656AA for ; Fri, 13 Jun 2008 14:13:25 +0000 (UTC) (envelope-from lists@loveturtle.net) Received: from loveturtle.net (loveturtle.net [216.89.228.174]) by mx1.freebsd.org (Postfix) with ESMTP id 2C1478FC1A for ; Fri, 13 Jun 2008 14:13:25 +0000 (UTC) (envelope-from lists@loveturtle.net) Received: from localhost (localhost [127.0.0.1]) by loveturtle.net (Postfix) with ESMTP id 2689530F6 for ; Fri, 13 Jun 2008 09:54:51 -0400 (EDT) X-Virus-Scanned: amavisd-new at loveturtle.net Received: from loveturtle.net ([127.0.0.1]) by localhost (loveturtle.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eVRwYaJAchbo for ; Fri, 13 Jun 2008 09:54:50 -0400 (EDT) Received: from minispork.loveturtle.net (minispork.loveturtle.net [216.182.254.141]) by loveturtle.net (Postfix) with ESMTP id E816430E5 for ; Fri, 13 Jun 2008 09:54:49 -0400 (EDT) Message-ID: <48527C29.20508@loveturtle.net> Date: Fri, 13 Jun 2008 09:54:49 -0400 From: Dillon Kass User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421) MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: ZFS version 8 on 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, 13 Jun 2008 14:13:25 -0000 There's nothing you can do right now except for wait. By default the zfs implementation on osx will create a zfs version 6 zpool (to retain compat with the read-only kext that ships with 10.5) but once you've upgraded you can't go back. There is a newer version of zfs for freebsd but it hasn't been commited yet. See http://kerneltrap.org/FreeBSD/BSDCan_2008_ZFS_Internals Your only option is to wait until this is committed or patches are offered at least. pjd is the man so it shouldn't be too long :-) Timothy Wilson wrote: > Hello everyone, > > I know -stable is supposed to be, well, stable, but I seem to be in a > bit of a pickle. > > I'm trying to import my zfs file system from a Macintosh machine. It > was created at version 8. Being new to zfs, I did not realise that > FreeBSD would be running at a lower version; I thought zfs was zfs! Of > course, trying to import my zpool fails, complaining that the version > is too new. > > freebsd# zpool import bigstore > cannot import 'bigstore': pool is formatted using a newer ZFS version > > So either I want to downgrade the zpool, or upgrade zfs on FreeBSD. > Does anyone know if I'll be able to import zfs v8, or am I wasting my > time? I'd prefer to follow -stable, but if I must follow -current, > then golly goshkins, I'll have no choice! > > Kind regards, > Timothy. > _______________________________________________ > 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 Jun 13 21:16:18 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 907B4106566C for ; Fri, 13 Jun 2008 21:16:18 +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 34ED58FC1A for ; Fri, 13 Jun 2008 21:16:18 +0000 (UTC) (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 4316146C8A; Fri, 13 Jun 2008 17:16:13 -0400 (EDT) Date: Fri, 13 Jun 2008 22:16:13 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: fbsd2 In-Reply-To: <372128.56919.qm@web51502.mail.re2.yahoo.com> Message-ID: <20080613221247.J95545@fledge.watson.org> References: <372128.56919.qm@web51502.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-stable@freebsd.org Subject: Re: 80 Mb / enough for 7.x? OK to delete /stand/ and /modules/ ? 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, 13 Jun 2008 21:16:18 -0000 On Thu, 12 Jun 2008, fbsd2 wrote: > Given recent EOL announcements, I'm trying to upgrade an ancient machine > from 5.5 to 7. It has 80 Mb total in the root partition, /home/, /var/, > /usr/, and /tmp/ on other partitions, and NFS mounts /usr/src, /usr/obj, and > /usr/ports from a slightly newer/faster box. I've seen > > http://www.freebsd.org/releases/7.0R/relnotes.html and > http://marc.info/?l=freebsd-stable&m=121278826119286&w=2 > > which seem to suggest that even with INSTALL_NODEBUG during buildkernel, 7 > might not fit in an 80 Mb /. Must I partition a new disk to give more space > to /, or can I find more space by deleting /stand/, /modules/, and possibly > /rescue/ to shoehorn a custom 7.x kernel in the available space? TIA My Kerberos server runs 7-STABLE and has a 93M root with 25M free. It's a bit tight -- I have to remember to disable the installation of debugging symbols for the kernel and modules, for example. However, it does work fine, and that's even with modules installed. The bigger problem is my old /var now that I have audit enabled. Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 23:11:29 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB5DF1065675 for ; Fri, 13 Jun 2008 23:11:29 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from toq12-srv.bellnexxia.net (toq12.bellnexxia.net [209.226.175.119]) by mx1.freebsd.org (Postfix) with ESMTP id 59C1E8FC3A for ; Fri, 13 Jun 2008 23:11:29 +0000 (UTC) (envelope-from dmagda@ee.ryerson.ca) Received: from toip4.srvr.bell.ca ([209.226.175.87]) by tomts5-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20080613225506.LGQY1572.tomts5-srv.bellnexxia.net@toip4.srvr.bell.ca> for ; Fri, 13 Jun 2008 18:55:06 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ah8BAEqVUkhMQR06/2dsb2JhbAAIrkQ Received: from bas1-toronto09-1279335738.dsl.bell.ca (HELO [192.168.1.133]) ([76.65.29.58]) by toip4.srvr.bell.ca with ESMTP; 13 Jun 2008 18:55:39 -0400 In-Reply-To: <48527C29.20508@loveturtle.net> References: <48527C29.20508@loveturtle.net> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: David Magda Date: Fri, 13 Jun 2008 18:55:00 -0400 To: Dillon Kass X-Mailer: Apple Mail (2.753) Cc: freebsd-stable@freebsd.org Subject: Re: ZFS version 8 on stable? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: David Magda List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2008 23:11:29 -0000 On Jun 13, 2008, at 09:54, Dillon Kass wrote: > Your only option is to wait until this is committed or patches are > offered at least. > pjd is the man so it shouldn't be too long :-) Another option could be to see if you can help with the coding. :) From owner-freebsd-stable@FreeBSD.ORG Fri Jun 13 23:52:33 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D23951065675 for ; Fri, 13 Jun 2008 23:52:33 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [213.186.42.107]) by mx1.freebsd.org (Postfix) with ESMTP id 79C698FC0C for ; Fri, 13 Jun 2008 23:52:33 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from baby-jane.lamaiziere.net (15.10.87-79.rev.gaoland.net [79.87.10.15]) by smtp.lamaiziere.net (Postfix) with ESMTP id 7E88E118059C; Sat, 14 Jun 2008 01:52:31 +0200 (CEST) Received: from baby-jane-lamaiziere-net.local (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 56915446528; Sat, 14 Jun 2008 01:52:30 +0200 (CEST) Date: Sat, 14 Jun 2008 01:52:29 +0200 From: Patrick =?ISO-8859-15?Q?Lamaizi=E8re?= To: Kris Kennaway Message-ID: <20080614015229.1c4afbe7@baby-jane-lamaiziere-net.local> In-Reply-To: <4851B7EF.7060905@FreeBSD.org> References: <20080613004847.09f9b089@baby-jane-lamaiziere-net.local> <4851B7EF.7060905@FreeBSD.org> Organization: /dave/nulle X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i386-apple-darwin9.2.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit Cc: freebsd-stable@freebsd.org Subject: Re: [7-STABLE] ping -s 4000 with ipsec 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: Fri, 13 Jun 2008 23:52:33 -0000 Le Fri, 13 Jun 2008 01:57:35 +0200, Kris Kennaway a écrit : Hello, [...] > > #17 0xc0700746 in crypto_invoke (cap=0x8, crp=0xd61a0950, > > hint=-1616994916) at cryptodev_if.h:53 > > Previous frame inner to this frame (corrupt stack?) > > (kgdb) > > Unfortunately the trace is bogus. Try to rebuild with -O instead of > -O2 and reproduce the panic. Hmm, i've got no luck with -O. I made few tests and the panic occurs with a -s of 3989 bytes. ping -s 3988 => ok ping -s 3989 => panic The coredump seems to be ok. http://user.lamaiziere.net/patrick/coredump.txt I will try with a kernel and DEBUG_REDZONE and INVARIANT. ----------------------- Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x9350ef1e fault code = supervisor read, page not present instruction pointer = 0x20:0xc05a0579 stack pointer = 0x28:0xd61635cc frame pointer = 0x28:0xd61635d0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 1101 (ping) trap number = 12 panic: page fault Uptime: 7m47s Physical memory: 503 MB Dumping 88 MB: 73 57 41 25 9 #0 doadump () at pcpu.h:195 in pcpu.h (kgdb) bt #0 doadump () at pcpu.h:195 #1 0xc0556273 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc055646f in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc079b91c in trap_fatal (frame=0xd616358c, eva=2471554846) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc079bba0 in trap_pfault (frame=0xd616358c, usermode=0, eva=2471554846) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc079c529 in trap (frame=0xd616358c) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0789f2b in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc05a0579 in mb_dupcl (n=0xc2b02000, m=0xc2b02d00) at /usr/src/sys/kern/uipc_mbuf.c:293 #8 0xc05a157a in m_copym (m=0xc2b02d00, off0=2980, len=3, wait=1) at /usr/src/sys/kern/uipc_mbuf.c:570 #9 0xc0614055 in ip_fragment (ip=0xc2e5a038, m_frag=0xd61636d0, mtu=1500, if_hwassist_flags=7, sw_csum=0) at /usr/src/sys/netinet/ip_output.c:728 #10 0xc0614d38 in ip_output (m=0xc2b02600, opt=0x0, ro=0xd6163694, flags=2, imo=0x0, inp=0x0) at /usr/src/sys/netinet/ip_output.c:567 #11 0xc06acd9d in ipsec_process_done (m=0xc2b02600, isr=0xc2bacd80) at /usr/src/sys/netipsec/ipsec_output.c:177 #12 0xc06bbf5c in esp_output_cb (crp=0xc2e5c708) at /usr/src/sys/netipsec/xform_esp.c:965 #13 0xc06ff730 in crypto_done (crp=0xc2e5c708) at /usr/src/sys/opencrypto/crypto.c:1148 #14 0xc0702afe in swcr_process (dev=0xc29cf380, crp=0xc2e5c708, hint=0) at /usr/src/sys/opencrypto/cryptosoft.c:975 #15 0xc0700746 in crypto_invoke (cap=0xc29cf380, crp=0xc2e5c708, hint=0) at cryptodev_if.h:53 #16 0xc070118c in crypto_dispatch (crp=0xc2e5c708) at /usr/src/sys/opencrypto/crypto.c:798 #17 0xc06bc5c6 in esp_output (m=0xc2b02600, isr=0xc2bacd80, mp=0x0, skip=20, protoff=9) at /usr/src/sys/netipsec/xform_esp.c:875 #18 0xc06ad112 in ipsec4_process_packet (m=0xc2b02600, isr=0xc2bacd80, flags=32, tunalready=0) at /usr/src/sys/netipsec/ipsec_output.c:491 #19 0xc0612f95 in ip_ipsec_output (m=0xd6163b04, inp=0xc2e07870, flags=0xd6163b10, error=0xd6163ae4, ro=0xd6163b0c, iproute=0xd6163ac8, dst=0xd6163ae0, ia=0xd6163adc, ifp=0xd6163aec) at /usr/src/sys/netinet/ip_ipsec.c:331 #20 0xc0614ab9 in ip_output (m=0xc2b02600, opt=0x0, ro=0xd6163ac8, flags=32, imo=0x0, inp=0xc2e07870) at /usr/src/sys/netinet/ip_output.c:420 #21 0xc0615e1b in rip_output (m=0xc2b02600, so=0xc2ddfad4, dst=352430272) at /usr/src/sys/netinet/raw_ip.c:336 #22 0xc0615efc in rip_send (so=0xc2ddfad4, flags=0, m=0xc2b02600, nam=0xc29f9800, control=0x0, td=0xc2b77000) at /usr/src/sys/netinet/raw_ip.c:806 #23 0xc05a97f5 in sosend_generic (so=0xc2ddfad4, addr=0xc29f9800, uio=0xd6163be8, top=0xc2b02600, control=0x0, flags=0, td=0xc2b77000) at /usr/src/sys/kern/uipc_socket.c:1240 #24 0xc05a580f in sosend (so=0xc2ddfad4, addr=0xc29f9800, uio=0xd6163be8, top=0x0, control=0x0, flags=0, td=0xc2b77000) at /usr/src/sys/kern/uipc_socket.c:1286 #25 0xc05abf16 in kern_sendit (td=0xc2b77000, s=3, mp=0xd6163c64, flags=0, control=0x0, segflg=UIO_USERSPACE) at /usr/src/sys/kern/uipc_syscalls.c:789 #26 0xc05af031 in sendit (td=0xc2b77000, s=3, mp=0xd6163c64, flags=0) at /usr/src/sys/kern/uipc_syscalls.c:730 #27 0xc05af148 in sendto (td=0xc2b77000, uap=0xd6163cfc) at /usr/src/sys/kern/uipc_syscalls.c:841 #28 0xc079bef5 in syscall (frame=0xd6163d38) at /usr/src/sys/i386/i386/trap.c:1035 #29 0xc0789f90 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:196 #30 0x00000033 in ?? () (kgdb) quit -------------- Thanks, regards. From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 05:37:55 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C6D91065677 for ; Sat, 14 Jun 2008 05:37:55 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id 97ED88FC0A for ; Sat, 14 Jun 2008 05:37:54 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id D185C33C02 for ; Sat, 14 Jun 2008 07:17:57 +0200 (CEST) DKIM-Signature: v=0.5; a=rsa-sha1; c=relaxed; d=ismobile.com; h=received:date:from:to:subject:message-id:x-mailer:mime-version:content-type; q=dns/txt; s=selector1; bh=TCjoFq8TBD7Rm6fRQpdqg9iYmAY=; b=oZofbfCGDuAtjHFfONf7IZnFRM+oekQwCrSDQ3Cd+PRHUeeOFiLnSGVLGiD0zKTyfWToUubSXjvo6vWqwmGdQjElhHj8S5kH98S7rDsdOyvKQXaKdkVvoQ1VW35VHyh8hTT27QvbGizfMcLkXxpnNmCg4oJMA/xId16M2oOrCqg= Received: from [10.255.253.2] (modgunn.iii-norr.com [213.242.135.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id 95F1833C01 for ; Sat, 14 Jun 2008 07:17:57 +0200 (CEST) Date: Sat, 14 Jun 2008 07:17:56 +0200 From: Goran Lowkrantz To: freebsd-stable@freebsd.org Message-ID: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="==========8D27D79BF1C51FCE3DC8==========" Subject: Unusually large directory - 2.0 peta bytes 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, 14 Jun 2008 05:37:55 -0000 --==========8D27D79BF1C51FCE3DC8========== Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline While preparing to upgrade to latest stable, I ran some scripts to verify=20 that the target was OK and found something that I think I need to fix but=20 have no clue to how. This is the essence of what I found: # ls /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* autosplit.ix # ls -la /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* ls: : No such file or directory ls: autosplit.ix: No such file or directory total 8 drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. # stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO 163 5229427 drwxr-xr-x 2 root wheel 20894350 2251799813685760 "Jun 14=20 07:07:43 2008" "Jun 14 04:06:44 2008" "Jun 14 04:06:44 2008" "Mar 29=20 10:33:10 2008" 4096 4 0=20 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO # stat=20 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix stat:=20 /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix:=20 stat: No such file or directory # od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more 0000000 s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 0000020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t 0000040 P e r l I O . s o \0 217 300 u 313 O \0 0000060 324 001 \b \t P e r l I O . b s \0 217 300 0000100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0001020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0002000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0002020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0003000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0003020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0004000 v 313 O \0 \f \0 004 001 . \0 \0 \0 335 312 O \0 0004020 \f \0 004 002 . . \0 \0 w 313 O \0 350 001 \b \f 0004040 a u t o s p l i t . i x \0 231 - 351 0004060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0005000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0005020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0006000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0006020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0007000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 0007020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 * 0010000 177 E L F 001 001 001 \t \0 \0 \0 \0 \0 \0 \0 \0 0010020 003 \0 003 \0 001 \0 \0 \0 240 \t \0 \0 4 \0 \0 \0 0010040 330 025 \0 \0 \0 \0 \0 \0 4 \0 \0 003 \0 ( \0 This does not look like a directory, it looks like a shared library,=20 PerlIO.so, that somehow got the directory bit set. First, am I correct in my analysis? Second, how do I remove the directory bit so I can delete the file? Host info, dmesg.boot attached: # uname -a FreeBSD balder.glz.hidden-powers.com 6.3-STABLE FreeBSD 6.3-STABLE #1: Thu=20 Feb 28 02:14:05 CET 2008=20 root@midgard.glz.hidden-powers.com:/usr/obj/usr/src/sys/BALDER i386 Cheers, G=F6ran ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ............................................... --==========8D27D79BF1C51FCE3DC8========== Content-Type: application/octet-stream; name="dmesg.boot" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="dmesg.boot"; size=7426 Q29weXJpZ2h0IChjKSAxOTkyLTIwMDggVGhlIEZyZWVCU0QgUHJvamVjdC4KQ29weXJpZ2h0IChj KSAxOTc5LCAxOTgwLCAxOTgzLCAxOTg2LCAxOTg4LCAxOTg5LCAxOTkxLCAxOTkyLCAxOTkzLCAx OTk0CglUaGUgUmVnZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLgpGcmVlQlNEIGlzIGEgcmVnaXN0ZXJlZCB0cmFkZW1hcmsgb2YgVGhlIEZy ZWVCU0QgRm91bmRhdGlvbi4KRnJlZUJTRCA2LjMtU1RBQkxFICMxOiBUaHUgRmViIDI4IDAyOjE0 OjA1IENFVCAyMDA4CiAgICByb290QG1pZGdhcmQuZ2x6LmhpZGRlbi1wb3dlcnMuY29tOi91c3Iv b2JqL3Vzci9zcmMvc3lzL0JBTERFUgpUaW1lY291bnRlciAiaTgyNTQiIGZyZXF1ZW5jeSAxMTkz MTgyIEh6IHF1YWxpdHkgMApDUFU6IEludGVsKFIpIFBlbnRpdW0oUikgNCBDUFUgMy4wNkdIeiAo MzA2Ni42Ny1NSHogNjg2LWNsYXNzIENQVSkKICBPcmlnaW4gPSAiR2VudWluZUludGVsIiAgSWQg PSAweGY0OSAgU3RlcHBpbmcgPSA5CiAgRmVhdHVyZXM9MHhiZmViZmJmZjxGUFUsVk1FLERFLFBT RSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LEFQSUMsU0VQLE1UUlIsUEdFLE1DQSxDTU9WLFBBVCxQU0Uz NixDTEZMVVNILERUUyxBQ1BJLE1NWCxGWFNSLFNTRSxTU0UyLFNTLEhUVCxUTSxQQkU+CiAgRmVh dHVyZXMyPTB4NjUxZDxTU0UzLFJTVkQyLE1PTixEU19DUEwsVE0yLENOWFQtSUQsQ1gxNix4VFBS PgogIEFNRCBGZWF0dXJlcz0weDIwMTAwMDAwPE5YLExNPgogIEFNRCBGZWF0dXJlczI9MHgxPExB SEY+CiAgTG9naWNhbCBDUFVzIHBlciBjb3JlOiAyCnJlYWwgbWVtb3J5ICA9IDMzNDYxOTg1Mjgg KDMxOTEgTUIpCmF2YWlsIG1lbW9yeSA9IDMyNjk4OTQxNDQgKDMxMTggTUIpCkFDUEkgQVBJQyBU YWJsZTogPElOVEVMICBEOTE1R0FWID4KaW9hcGljMCA8VmVyc2lvbiAyLjA+IGlycXMgMC0yMyBv biBtb3RoZXJib2FyZAprYmQxIGF0IGtiZG11eDAKaWNod2QgbW9kdWxlIGxvYWRlZApocHRycjog SFBUIFJvY2tldFJBSUQgY29udHJvbGxlciBkcml2ZXIgdjEuMSAoRmViIDI4IDIwMDggMDI6MTM6 MzYpCmFjcGkwOiA8SU5URUwgRDkxNUdBVj4gb24gbW90aGVyYm9hcmQKYWNwaTA6IFBvd2VyIEJ1 dHRvbiAoZml4ZWQpClRpbWVjb3VudGVyICJBQ1BJLWZhc3QiIGZyZXF1ZW5jeSAzNTc5NTQ1IEh6 IHF1YWxpdHkgMTAwMAphY3BpX3RpbWVyMDogPDI0LWJpdCB0aW1lciBhdCAzLjU3OTU0NU1Iej4g cG9ydCAweDQwOC0weDQwYiBvbiBhY3BpMApjcHUwOiA8QUNQSSBDUFU+IG9uIGFjcGkwCnA0dGNj MDogPENQVSBGcmVxdWVuY3kgVGhlcm1hbCBDb250cm9sPiBvbiBjcHUwCnBjaWIwOiA8QUNQSSBI b3N0LVBDSSBicmlkZ2U+IHBvcnQgMHhjZjgtMHhjZmYgb24gYWNwaTAKcGNpMDogPEFDUEkgUENJ IGJ1cz4gb24gcGNpYjAKcGNpYjE6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgMS4w IG9uIHBjaTAKcGNpMTogPEFDUEkgUENJIGJ1cz4gb24gcGNpYjEKYWdwMDogPEludGVsIDgyOTE1 RyAoOTE1RyBHTUNIKSBTVkdBIGNvbnRyb2xsZXI+IHBvcnQgMHhlYzAwLTB4ZWMwNyBtZW0gMHhm ZjQ4MDAwMC0weGZmNGZmZmZmLDB4ZDAwMDAwMDAtMHhkZmZmZmZmZiwweGZmNDQwMDAwLTB4ZmY0 N2ZmZmYgaXJxIDE2IGF0IGRldmljZSAyLjAgb24gcGNpMAphZ3AwOiBkZXRlY3RlZCA3OTMyayBz dG9sZW4gbWVtb3J5CmFncDA6IGFwZXJ0dXJlIHNpemUgaXMgMjU2TQpwY2liMjogPEFDUEkgUENJ LVBDSSBicmlkZ2U+IGF0IGRldmljZSAyOC4wIG9uIHBjaTAKcGNpNTogPEFDUEkgUENJIGJ1cz4g b24gcGNpYjIKZW0wOiA8SW50ZWwoUikgUFJPLzEwMDAgTmV0d29yayBDb25uZWN0aW9uIFZlcnNp b24gLSA2LjcuMz4gcG9ydCAweDljMDAtMHg5YzFmIG1lbSAweGZmNjAwMDAwLTB4ZmY2MWZmZmYs MHhmZjYyMDAwMC0weGZmNjNmZmZmIGlycSAxNiBhdCBkZXZpY2UgMC4wIG9uIHBjaTUKZW0wOiBV c2luZyBNU0kgaW50ZXJydXB0CmVtMDogRXRoZXJuZXQgYWRkcmVzczogMDA6MWI6MjE6MDA6NDg6 YzQKcGNpYjM6IDxBQ1BJIFBDSS1QQ0kgYnJpZGdlPiBhdCBkZXZpY2UgMjguMSBvbiBwY2kwCnBj aTQ6IDxBQ1BJIFBDSSBidXM+IG9uIHBjaWIzCnBjaWI0OiA8QUNQSSBQQ0ktUENJIGJyaWRnZT4g YXQgZGV2aWNlIDI4LjIgb24gcGNpMApwY2kzOiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2liNApwY2li NTogPEFDUEkgUENJLVBDSSBicmlkZ2U+IGF0IGRldmljZSAyOC4zIG9uIHBjaTAKcGNpMjogPEFD UEkgUENJIGJ1cz4gb24gcGNpYjUKdWhjaTA6IDxJbnRlbCA4MjgwMUZCL0ZSL0ZXL0ZSVyAoSUNI NikgVVNCIGNvbnRyb2xsZXIgVVNCLUE+IHBvcnQgMHhjODAwLTB4YzgxZiBpcnEgMjMgYXQgZGV2 aWNlIDI5LjAgb24gcGNpMAp1aGNpMDogW0dJQU5ULUxPQ0tFRF0KdXNiMDogPEludGVsIDgyODAx RkIvRlIvRlcvRlJXIChJQ0g2KSBVU0IgY29udHJvbGxlciBVU0ItQT4gb24gdWhjaTAKdXNiMDog VVNCIHJldmlzaW9uIDEuMAp1aHViMDogSW50ZWwgVUhDSSByb290IGh1YiwgY2xhc3MgOS8wLCBy ZXYgMS4wMC8xLjAwLCBhZGRyIDEKdWh1YjA6IDIgcG9ydHMgd2l0aCAyIHJlbW92YWJsZSwgc2Vs ZiBwb3dlcmVkCnVoY2kxOiA8SW50ZWwgODI4MDFGQi9GUi9GVy9GUlcgKElDSDYpIFVTQiBjb250 cm9sbGVyIFVTQi1CPiBwb3J0IDB4Y2MwMC0weGNjMWYgaXJxIDE5IGF0IGRldmljZSAyOS4xIG9u IHBjaTAKdWhjaTE6IFtHSUFOVC1MT0NLRURdCnVzYjE6IDxJbnRlbCA4MjgwMUZCL0ZSL0ZXL0ZS VyAoSUNINikgVVNCIGNvbnRyb2xsZXIgVVNCLUI+IG9uIHVoY2kxCnVzYjE6IFVTQiByZXZpc2lv biAxLjAKdWh1YjE6IEludGVsIFVIQ0kgcm9vdCBodWIsIGNsYXNzIDkvMCwgcmV2IDEuMDAvMS4w MCwgYWRkciAxCnVodWIxOiAyIHBvcnRzIHdpdGggMiByZW1vdmFibGUsIHNlbGYgcG93ZXJlZAp1 aGNpMjogPEludGVsIDgyODAxRkIvRlIvRlcvRlJXIChJQ0g2KSBVU0IgY29udHJvbGxlciBVU0It Qz4gcG9ydCAweGQwMDAtMHhkMDFmIGlycSAxOCBhdCBkZXZpY2UgMjkuMiBvbiBwY2kwCnVoY2ky OiBbR0lBTlQtTE9DS0VEXQp1c2IyOiA8SW50ZWwgODI4MDFGQi9GUi9GVy9GUlcgKElDSDYpIFVT QiBjb250cm9sbGVyIFVTQi1DPiBvbiB1aGNpMgp1c2IyOiBVU0IgcmV2aXNpb24gMS4wCnVodWIy OiBJbnRlbCBVSENJIHJvb3QgaHViLCBjbGFzcyA5LzAsIHJldiAxLjAwLzEuMDAsIGFkZHIgMQp1 aHViMjogMiBwb3J0cyB3aXRoIDIgcmVtb3ZhYmxlLCBzZWxmIHBvd2VyZWQKdWhjaTM6IDxJbnRl bCA4MjgwMUZCL0ZSL0ZXL0ZSVyAoSUNINikgVVNCIGNvbnRyb2xsZXIgVVNCLUQ+IHBvcnQgMHhk NDAwLTB4ZDQxZiBpcnEgMTYgYXQgZGV2aWNlIDI5LjMgb24gcGNpMAp1aGNpMzogW0dJQU5ULUxP Q0tFRF0KdXNiMzogPEludGVsIDgyODAxRkIvRlIvRlcvRlJXIChJQ0g2KSBVU0IgY29udHJvbGxl ciBVU0ItRD4gb24gdWhjaTMKdXNiMzogVVNCIHJldmlzaW9uIDEuMAp1aHViMzogSW50ZWwgVUhD SSByb290IGh1YiwgY2xhc3MgOS8wLCByZXYgMS4wMC8xLjAwLCBhZGRyIDEKdWh1YjM6IDIgcG9y dHMgd2l0aCAyIHJlbW92YWJsZSwgc2VsZiBwb3dlcmVkCnBjaWI2OiA8QUNQSSBQQ0ktUENJIGJy aWRnZT4gYXQgZGV2aWNlIDMwLjAgb24gcGNpMApwY2k2OiA8QUNQSSBQQ0kgYnVzPiBvbiBwY2li NgphaGMwOiA8QWRhcHRlYyAyOTQwIFVsdHJhIFNDU0kgYWRhcHRlcj4gcG9ydCAweGI4MDAtMHhi OGZmIG1lbSAweGZmNTkwMDAwLTB4ZmY1OTBmZmYgaXJxIDIxIGF0IGRldmljZSAwLjAgb24gcGNp NgphaGMwOiBbR0lBTlQtTE9DS0VEXQphaWM3ODgwOiBVbHRyYSBXaWRlIENoYW5uZWwgQSwgU0NT SSBJZD03LCAxNi8yNTMgU0NCcwpycDA6IDxSb2NrZXRQb3J0IFBDST4gcG9ydCAweGJjMDAtMHhi YzNmIGlycSAyMiBhdCBkZXZpY2UgMS4wIG9uIHBjaTYKUm9ja2V0UG9ydDAgKFZlcnNpb24gMy4w MikgNCBwb3J0cy4KcnAxOiA8Um9ja2V0UG9ydCBQQ0k+IHBvcnQgMHhiNDAwLTB4YjQzZiBpcnEg MTggYXQgZGV2aWNlIDIuMCBvbiBwY2k2ClJvY2tldFBvcnQxIChWZXJzaW9uIDMuMDIpIDQgcG9y dHMuCmF0YXBjaTA6IDxTaUkgU2lJIDMxMTQgU0FUQTE1MCBjb250cm9sbGVyPiBwb3J0IDB4YjAw MC0weGIwMDcsMHhhYzAwLTB4YWMwMywweGE4MDAtMHhhODA3LDB4YTQwMC0weGE0MDMsMHhhMDAw LTB4YTAwZiBtZW0gMHhmZjU5MTAwMC0weGZmNTkxM2ZmIGlycSAxOSBhdCBkZXZpY2UgMy4wIG9u IHBjaTYKYXRhMjogPEFUQSBjaGFubmVsIDA+IG9uIGF0YXBjaTAKYXRhMzogPEFUQSBjaGFubmVs IDE+IG9uIGF0YXBjaTAKYXRhNDogPEFUQSBjaGFubmVsIDI+IG9uIGF0YXBjaTAKYXRhNTogPEFU QSBjaGFubmVsIDM+IG9uIGF0YXBjaTAKaXNhYjA6IDxQQ0ktSVNBIGJyaWRnZT4gYXQgZGV2aWNl IDMxLjAgb24gcGNpMAppc2EwOiA8SVNBIGJ1cz4gb24gaXNhYjAKYXRhcGNpMTogPEludGVsIElD SDYgVURNQTEwMCBjb250cm9sbGVyPiBwb3J0IDB4MWYwLTB4MWY3LDB4M2Y2LDB4MTcwLTB4MTc3 LDB4Mzc2LDB4ZmZhMC0weGZmYWYgYXQgZGV2aWNlIDMxLjEgb24gcGNpMAphdGEwOiA8QVRBIGNo YW5uZWwgMD4gb24gYXRhcGNpMQphdGExOiA8QVRBIGNoYW5uZWwgMT4gb24gYXRhcGNpMQphdGFw Y2kyOiA8SW50ZWwgSUNINiBTQVRBMTUwIGNvbnRyb2xsZXI+IHBvcnQgMHhlODAwLTB4ZTgwNyww eGU0MDAtMHhlNDAzLDB4ZTAwMC0weGUwMDcsMHhkYzAwLTB4ZGMwMywweGQ4MDAtMHhkODBmIGly cSAxOSBhdCBkZXZpY2UgMzEuMiBvbiBwY2kwCmF0YTY6IDxBVEEgY2hhbm5lbCAwPiBvbiBhdGFw Y2kyCmF0YTc6IDxBVEEgY2hhbm5lbCAxPiBvbiBhdGFwY2kyCmljaHNtYjA6IDxJbnRlbCA4Mjgw MUZCIChJQ0g2KSBTTUJ1cyBjb250cm9sbGVyPiBwb3J0IDB4YzQwMC0weGM0MWYgaXJxIDE5IGF0 IGRldmljZSAzMS4zIG9uIHBjaTAKaWNoc21iMDogW0dJQU5ULUxPQ0tFRF0Kc21idXMwOiA8U3lz dGVtIE1hbmFnZW1lbnQgQnVzPiBvbiBpY2hzbWIwCnNtYjA6IDxTTUJ1cyBnZW5lcmljIEkvTz4g b24gc21idXMwCmFjcGlfYnV0dG9uMDogPFBvd2VyIEJ1dHRvbj4gb24gYWNwaTAKYXRrYmRjMDog PEtleWJvYXJkIGNvbnRyb2xsZXIgKGk4MDQyKT4gcG9ydCAweDYwLDB4NjQgaXJxIDEgb24gYWNw aTAKYXRrYmQwOiA8QVQgS2V5Ym9hcmQ+IGlycSAxIG9uIGF0a2JkYzAKa2JkMCBhdCBhdGtiZDAK YXRrYmQwOiBbR0lBTlQtTE9DS0VEXQpwc20wOiA8UFMvMiBNb3VzZT4gaXJxIDEyIG9uIGF0a2Jk YzAKcHNtMDogW0dJQU5ULUxPQ0tFRF0KcHNtMDogbW9kZWwgR2VuZXJpYyBQUy8yIG1vdXNlLCBk ZXZpY2UgSUQgMApzaW8wOiA8MTY1NTBBLWNvbXBhdGlibGUgQ09NIHBvcnQ+IHBvcnQgMHgzZjgt MHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBhY3BpMApzaW8wOiB0eXBlIDE2NTUwQQpwbXRpbWVy MCBvbiBpc2EwCmljaHdkMDogPEludGVsIDgyODAxRkIvRlIgd2F0Y2hkb2cgdGltZXI+IG9uIGlz YTAKaWNod2QwOiBJbnRlbCA4MjgwMUZCL0ZSIHdhdGNoZG9nIHRpbWVyIChJQ0g2IG9yIGVxdWl2 YWxlbnQpCm9ybTA6IDxJU0EgT3B0aW9uIFJPTXM+IGF0IGlvbWVtIDB4Y2IwMDAtMHhjYjdmZiww eGNiODAwLTB4ZDA3ZmYgb24gaXNhMApwcGMwOiBwYXJhbGxlbCBwb3J0IG5vdCBmb3VuZC4Kc2Mw OiA8U3lzdGVtIGNvbnNvbGU+IGF0IGZsYWdzIDB4MTAwIG9uIGlzYTAKc2MwOiBWR0EgPDE2IHZp cnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MzAwPgp2Z2EwOiA8R2VuZXJpYyBJU0EgVkdBPiBhdCBw b3J0IDB4M2MwLTB4M2RmIGlvbWVtIDB4YTAwMDAtMHhiZmZmZiBvbiBpc2EwClRpbWVjb3VudGVy ICJUU0MiIGZyZXF1ZW5jeSAzMDY2NjY5MjM1IEh6IHF1YWxpdHkgODAwClRpbWVjb3VudGVycyB0 aWNrIGV2ZXJ5IDEuMDAwIG1zZWMKaHB0cnI6IG5vIGNvbnRyb2xsZXIgZGV0ZWN0ZWQuCldhaXRp bmcgNSBzZWNvbmRzIGZvciBTQ1NJIGRldmljZXMgdG8gc2V0dGxlCmFjZDA6IENEUk9NIDxNQVRT SElUQSBDUi01ODUvWlMxNT4gYXQgYXRhMC1tYXN0ZXIgUElPMwphZDQ6IDIzOTM3Mk1CIDxNYXh0 b3IgNkIyNTBTMCBCQU5DMUI3MD4gYXQgYXRhMi1tYXN0ZXIgU0FUQTE1MAphZDY6IDIzODQ3NU1C IDxTZWFnYXRlIFNUMzI1MDYyMEFTIDMuQUFFPiBhdCBhdGEzLW1hc3RlciBTQVRBMTUwCmFkODog MjM5MzcyTUIgPE1heHRvciA2QjI1MFMwIEJBTkMxQjcwPiBhdCBhdGE0LW1hc3RlciBTQVRBMTUw CmFkMTA6IDIzODQ3NU1CIDxTZWFnYXRlIFNUMzI1MDYyMEFTIDMuQUFFPiBhdCBhdGE1LW1hc3Rl ciBTQVRBMTUwCmFkMTI6IDc2MzE5TUIgPFNBTVNVTkcgSEQwODBISiBaSDEwMC00Nz4gYXQgYXRh Ni1tYXN0ZXIgU0FUQTE1MAphZDE0OiA3NjM1MU1CIDxTQU1TVU5HIFNQMDgxMkMgU1UxMDAtMzA+ IGF0IGF0YTctbWFzdGVyIFNBVEExNTAKR0VPTV9NSVJST1I6IERldmljZSBnbTBzMSBjcmVhdGVk IChpZD0xODE2NTI0MzYyKS4KR0VPTV9NSVJST1I6IERldmljZSBnbTBzMTogcHJvdmlkZXIgYWQx MnMxIGRldGVjdGVkLgpHRU9NX01JUlJPUjogRGV2aWNlIGdtMHMxOiBwcm92aWRlciBhZDE0czEg ZGV0ZWN0ZWQuCkdFT01fTUlSUk9SOiBEZXZpY2UgZ20wczE6IHByb3ZpZGVyIGFkMTRzMSBhY3Rp dmF0ZWQuCkdFT01fTUlSUk9SOiBEZXZpY2UgZ20wczE6IHByb3ZpZGVyIGFkMTJzMSBhY3RpdmF0 ZWQuCkdFT01fTUlSUk9SOiBEZXZpY2UgZ20wczE6IHByb3ZpZGVyIG1pcnJvci9nbTBzMSBsYXVu Y2hlZC4KR0VPTV9MQUJFTDogTGFiZWwgZm9yIHByb3ZpZGVyIGFkNHMxYSBpcyB1ZnMvZHVtcDEu CkdFT01fTEFCRUw6IExhYmVsIGZvciBwcm92aWRlciBhZDZzMWEgaXMgdWZzL2R1bXAyLgpHRU9N X0xBQkVMOiBMYWJlbCBmb3IgcHJvdmlkZXIgYWQ4czFhIGlzIHVmcy9kdW1wMy4KR0VPTV9MQUJF TDogTGFiZWwgZm9yIHByb3ZpZGVyIGFkMTBzMWEgaXMgdWZzL2R1bXA0LgpzYTAgYXQgYWhjMCBi dXMgMCB0YXJnZXQgNiBsdW4gMApzYTA6IDxERUMgVFo4ODUgICAgKEMpIERFQyBDRDUwPiBSZW1v dmFibGUgU2VxdWVudGlhbCBBY2Nlc3MgU0NTSS0yIGRldmljZSAKc2EwOiAxMC4wMDBNQi9zIHRy YW5zZmVycyAoMTAuMDAwTUh6LCBvZmZzZXQgMTUpCmNoMCBhdCBhaGMwIGJ1cyAwIHRhcmdldCA2 IGx1biAxCmNoMDogPERFQyBUWiBNZWRpYSBDaGFuZ2VyIENENTA+IFJlbW92YWJsZSBDaGFuZ2Vy IFNDU0ktMiBkZXZpY2UgCmNoMDogMTAuMDAwTUIvcyB0cmFuc2ZlcnMgKDEwLjAwME1Ieiwgb2Zm c2V0IDE1KQpjaDA6IDUgc2xvdHMsIDEgZHJpdmUsIDEgcGlja2VyLCAwIHBvcnRhbHMKVHJ5aW5n IHRvIG1vdW50IHJvb3QgZnJvbSB1ZnM6L2Rldi9taXJyb3IvZ20wczFhCmVtMDogbGluayBzdGF0 ZSBjaGFuZ2VkIHRvIFVQCg== --==========8D27D79BF1C51FCE3DC8==========-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 06:25:41 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7358E106567A for ; Sat, 14 Jun 2008 06:25:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id 34F268FC1A for ; Sat, 14 Jun 2008 06:25:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id m5E6PUVl028057; Sat, 14 Jun 2008 00:25:30 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 14 Jun 2008 00:27:03 -0600 (MDT) Message-Id: <20080614.002703.-1142020417.imp@bsdimp.com> To: rock_on_the_web@comcen.com.au From: "M. Warner Losh" In-Reply-To: <1207010488.30698.42.camel@laptop2.herveybayaustralia.com.au> References: <20080330.005823.-432836004.imp@bsdimp.com> <1207010488.30698.42.camel@laptop2.herveybayaustralia.com.au> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Texas Instruments Card Reader. 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, 14 Jun 2008 06:25:41 -0000 In message: <1207010488.30698.42.camel@laptop2.herveybayaustralia.com.au> Da Rock writes: : : On Sun, 2008-03-30 at 09:18 -0300, Carlos A. M. dos Santos wrote: : > On Sun, Mar 30, 2008 at 3:58 AM, M. Warner Losh wrote: : > > In message: <1206767583.4015.12.camel@laptop2.herveybayaustralia.com.au> : > > Da Rock writes: : > > : Did anyone end up getting this to work? I'm suffering the same woes... : > > : > > Which device is this, specifically? : > > : > > Warner : > : > It is an SD, MS/Pro, MMC, SM and XD card reader. It is recognized by : > the Linux "sdhci" driver. There was an email thread some time ago : > discussing an homonymous driver for FreeBSD: : > : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000243.html : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000248.html : > : : Thats right- I believe you were working with a ricoh card reader though. : Is there any update to this project? A todo journal maybe? I've a working card reader for ricoh that I've not been able to adapt to TI so I've never committed from a couple of difference sources... I should find time to fix that... Warner From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 07:10:26 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F10D106567C for ; Sat, 14 Jun 2008 07:10:26 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (mail.ismobile.com [62.119.44.68]) by mx1.freebsd.org (Postfix) with ESMTP id 9BC1C8FC16 for ; Sat, 14 Jun 2008 07:10:25 +0000 (UTC) (envelope-from goran.lowkrantz@ismobile.com) Received: from mail.ismobile.com (localhost [127.0.0.1]) by mail.ismobile.com (Postfix) with ESMTP id 5EE4F33C02 for ; Sat, 14 Jun 2008 09:10:24 +0200 (CEST) DKIM-Signature: v=0.5; a=rsa-sha1; c=relaxed; d=ismobile.com; h=received:date:from:to:subject:message-id:in-reply-to:references:x-mailer:mime-version:content-type:content-transfer-encoding:content-disposition; q=dns/txt; s=selector1; bh=txRjKr10eFk0WmXYuq9yKrC3sNE=; b=UncMGxzMCFCxWj0P1PQ81iz3Sx/EvqJMeDTMc7HdQPqDJu4hzoIAaA9IrwEaX6KWkDAippUIttU+5ccmrT041XpuXp+QO14SzQHz6Osm3GFTqAc7MDaoGw7hSRR2+SvhIZUz6h6OkSvloz5IEfnlRR+EwYPkiE8fw4ZPklkiu50= Received: from [10.255.253.2] (modgunn.iii-norr.com [213.242.135.174]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.ismobile.com (Postfix) with ESMTPSA id 3EFF233C01 for ; Sat, 14 Jun 2008 09:10:24 +0200 (CEST) Date: Sat, 14 Jun 2008 09:10:23 +0200 From: Goran Lowkrantz To: freebsd-stable@freebsd.org Message-ID: In-Reply-To: References: X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Subject: Re: Unusually large directory - 2.0 peta bytes (SOLVED) 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, 14 Jun 2008 07:10:26 -0000 The initial fsck didn't clear it but using fsdb to remove the entry from=20 the parent directory, an fsck -y /usr in singleuser cleard the problem. Thanks to Joseph Koshy for directing me to fsdb. Cheers, G=F6ran --On Saturday, June 14, 2008 07:17 +0200 Goran Lowkrantz=20 wrote: > While preparing to upgrade to latest stable, I ran some scripts to verify > that the target was OK and found something that I think I need to fix but > have no clue to how. > > This is the essence of what I found: > ># ls /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* > autosplit.ix ># ls -la /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/* > ls: : No such file or directory > ls: autosplit.ix: No such file or directory > total 8 > drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . > drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . > drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. > drwxr-xr-x 24 root wheel 512 Mar 29 10:33 .. ># stat /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO > 163 5229427 drwxr-xr-x 2 root wheel 20894350 2251799813685760 "Jun 14 > 07:07:43 2008" "Jun 14 04:06:44 2008" "Jun 14 04:06:44 2008" "Mar 29 > 10:33:10 2008" 4096 4 0 > /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO ># stat ># /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix > stat: > /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO/autosplit.ix: > stat: No such file or directory ># od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more > 0000000 s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 > 0000020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t > 0000040 P e r l I O . s o \0 217 300 u 313 O \0 > 0000060 324 001 \b \t P e r l I O . b s \0 217 300 > 0000100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0001020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0002000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0002020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0003000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0003020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0004000 v 313 O \0 \f \0 004 001 . \0 \0 \0 335 312 O \0 > 0004020 \f \0 004 002 . . \0 \0 w 313 O \0 350 001 \b \f > 0004040 a u t o s p l i t . i x \0 231 - 351 > 0004060 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0005000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0005020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0006000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0006020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0007000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > 0007020 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 > * > 0010000 177 E L F 001 001 001 \t \0 \0 \0 \0 \0 \0 \0 \0 > 0010020 003 \0 003 \0 001 \0 \0 \0 240 \t \0 \0 4 \0 \0 \0 > 0010040 330 025 \0 \0 \0 \0 \0 \0 4 \0 \0 003 \0 ( \0 > > > This does not look like a directory, it looks like a shared library, > PerlIO.so, that somehow got the directory bit set. > > First, am I correct in my analysis? > Second, how do I remove the directory bit so I can delete the file? > > Host info, dmesg.boot attached: ># uname -a > FreeBSD balder.glz.hidden-powers.com 6.3-STABLE FreeBSD 6.3-STABLE #1: > Thu Feb 28 02:14:05 CET 2008 > root@midgard.glz.hidden-powers.com:/usr/obj/usr/src/sys/BALDER i386 > > > Cheers, > G=F6ran > > > ................................................... the future isMobile > > Goran Lowkrantz > System Architect, isMobile AB > Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden > Mobile: +46(0)70-587 87 82 > http://www.ismobile.com ............................................... ................................................... the future isMobile Goran Lowkrantz System Architect, isMobile AB Sandviksgatan 81, PO Box 58, S-971 03 Lule=E5, Sweden Mobile: +46(0)70-587 87 82 http://www.ismobile.com ............................................... From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 07:16:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87C62106564A for ; Sat, 14 Jun 2008 07:16:21 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from mail17.syd.optusnet.com.au (mail17.syd.optusnet.com.au [211.29.132.198]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8238FC1E for ; Sat, 14 Jun 2008 07:16:20 +0000 (UTC) (envelope-from peterjeremy@optushome.com.au) Received: from server.vk2pj.dyndns.org (c122-106-215-175.belrs3.nsw.optusnet.com.au [122.106.215.175]) by mail17.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id m5E7GIXr019398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Jun 2008 17:16:19 +1000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.2/8.14.2) with ESMTP id m5E7GIA4048604; Sat, 14 Jun 2008 17:16:18 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.2/8.14.2/Submit) id m5E7GIQ7048603; Sat, 14 Jun 2008 17:16:18 +1000 (EST) (envelope-from peter) Date: Sat, 14 Jun 2008 17:16:18 +1000 From: Peter Jeremy To: Goran Lowkrantz Message-ID: <20080614071617.GJ13734@server.vk2pj.dyndns.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-stable@freebsd.org Subject: Re: Unusually large directory - 2.0 peta bytes 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, 14 Jun 2008 07:16:21 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2008-Jun-14 07:17:56 +0200, Goran Lowkrantz wrote: >drwxr-xr-x 2 root wheel 2251799813685760 Jun 14 04:06 . This is 0x8000000000200 ># od -c /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/APR/PerlIO | more >0000000 s 313 O \0 \f \0 004 001 . \0 \0 \0 1 313 O \0 >0000020 364 001 004 002 . . \0 \0 t 313 O \0 024 \0 \b \t >0000040 P e r l I O . s o \0 217 300 u 313 O \0 >0000060 324 001 \b \t P e r l I O . b s \0 217 300 >0000100 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 >* >0001000 \0 \0 \0 \0 \0 002 \0 \0 \0 \0 \0 \0 \0 \0 \0 \0 =2E.. >This does not look like a directory, it looks like a shared library,=20 >PerlIO.so, that somehow got the directory bit set. Actually, no. It looks like a valid directory that somehow managed to get the high bit in its length set (random bit flip). The od output makes it look like it contains (or used to contain) PerlIO.so and PerlIO.bs. >Second, how do I remove the directory bit so I can delete the file? I'd try a fsck - that may detect the inconsistency and fix it to the point where rm works. If not, then you'll need to use fsdb(8) - just be careful with the latter - you can do major damage with it. Your second issue is how you got a random bit-flip - you might like to check your hardware. --=20 Peter Jeremy Please excuse any delays as the result of my ISP's inability to implement an MTA that is either RFC2821-compliant or matches their claimed behaviour. --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEUEARECAAYFAkhTcEEACgkQ/opHv/APuIeDmwCgo0F3JOOPLt18DR680rr9oLlx fhIAmM+ot+4EIgtWT94GgRDtF+2omvY= =Efmw -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 14:54:21 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40FE71065676; Sat, 14 Jun 2008 14:54:21 +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 7423F8FC0C; Sat, 14 Jun 2008 14:54:20 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from inchoate.gsoft.com.au (ppp121-45-20-55.lns10.adl2.internode.on.net [121.45.20.55]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id m5EEsFG5031754 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 15 Jun 2008 00:24:16 +0930 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Sean C. Farley" Date: Sun, 15 Jun 2008 00:24:03 +0930 User-Agent: KMail/1.9.7 References: <4846B64F.4090700@minibofh.org> <200806121118.45137.doconnor@gsoft.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart21670620.Q4mYicbNYT"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200806150024.13198.doconnor@gsoft.com.au> X-Spam-Score: -2.212 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.63 on 203.31.81.10 Cc: Jordi Espasa Clofent , Jeremy Chadwick , freebsd-apache@freebsd.org, freebsd-stable@freebsd.org Subject: Re: apachectl gracefult causes Signal 11 crash after 6.3 to 7.0 upgrade [SOLVED] 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, 14 Jun 2008 14:54:21 -0000 --nextPart21670620.Q4mYicbNYT Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 13 Jun 2008, Sean C. Farley wrote: > On Thu, 12 Jun 2008, Daniel O'Connor wrote: > > On Thu, 12 Jun 2008, Jeremy Chadwick wrote: > >> I myself haven't ever run into extension ordering issues like > >> those described (and we've done hosting for years), but I don't > >> doubt those who have experienced such. > > > > I am currently experiencing this :( In the past I shuffled the > > order until it worked but that's not a real solution. > > > > Also if you have gone from 6.x to 7.x make sure that you don't have > > any old stuff linked against libc.so.6 loaded into a binary using > > libc.so.7. > > > > It mostly works except with threaded programs and then *kaboom* > > Also, please try rebuilding PHP5 that has this fix[1] (in ports tree > after June 9th). It may or may not help your issue. > > Sean > 1. http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/123911 I tried that but no luck :( I can build php5 with pgsql (ie modify the port Makefile) and then it=20 works and so does mhash(?!) - I am using that as a work around ATM. =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 --nextPart21670620.Q4mYicbNYT Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.8 (FreeBSD) iD8DBQBIU9uV5ZPcIHs/zowRAiPHAKCUEm7OwvO/xms/GtD9H8NIZzyUUQCfRtTg BRwhcxC5km15RxX7ctbGN2Q= =2gIy -----END PGP SIGNATURE----- --nextPart21670620.Q4mYicbNYT-- From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 17:38:37 2008 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7ADF31065677 for ; Sat, 14 Jun 2008 17:38:37 +0000 (UTC) (envelope-from robert@ml.erje.net) Received: from smtpout-1.iphouse.net (smtpout-1.iphouse.net [216.250.188.190]) by mx1.freebsd.org (Postfix) with ESMTP id 51B538FC19 for ; Sat, 14 Jun 2008 17:38:37 +0000 (UTC) (envelope-from robert@ml.erje.net) Received: from smtpout-1.iphouse.net (localhost [127.0.0.1]) by outbound-clamsmtpd.iphouse.net (Postfix) with ESMTP id 85E892AC6D4 for ; Sat, 14 Jun 2008 12:38:36 -0500 (CDT) Received: from ziemel.erje.net (erje.net [80.126.62.176]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtpout-1.iphouse.net (Postfix) with ESMTP id 3D2BC2AC6BB for ; Sat, 14 Jun 2008 12:38:36 -0500 (CDT) Received: from ismet.erje.net (ismet.erje.net [IPv6:2001:888:1f33::8e45:5e]) by ziemel.erje.net (PostFix 2.5.2) with ESMTP id 2CD31CA0906 for ; Sat, 14 Jun 2008 19:37:50 +0200 (CEST) Received: (from robert@localhost) by ismet.erje.net (8.14.2/8.14.2/Submit) id m5EHbmIT006223 for stable@freebsd.org; Sat, 14 Jun 2008 19:37:48 +0200 (CEST) (envelope-from robert@ml.erje.net) X-Authentication-Warning: ismet.erje.net: robert set sender to robert@ml.erje.net using -f Date: Sat, 14 Jun 2008 19:37:48 +0200 From: Robert Joosten To: stable@freebsd.org Message-ID: <20080614173748.GB6061@iphouse.com> References: <20080608071316.GC973@iphouse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080608071316.GC973@iphouse.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-ziemel.erje.net-MailScanner: Ok, found to be clean X-Spam-Status: No X-Virus-Scanned: ClamAV using ClamSMTP Cc: Subject: Re: gmirror patches 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, 14 Jun 2008 17:38:37 -0000 > So far it runs okay. Well a week passed by: - no answer to my question, but - no issues to report either Fwiw. Cheers, Robert From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 19:10:40 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 951601065679 for ; Sat, 14 Jun 2008 19:10:40 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 1D7A68FC0C for ; Sat, 14 Jun 2008 19:10:39 +0000 (UTC) (envelope-from unixmania@gmail.com) Received: by ug-out-1314.google.com with SMTP id q2so237687uge.37 for ; Sat, 14 Jun 2008 12:10:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=klVGfLbBQ8huX/LxIfFey3s0NwKsL8kGD7UOC/bA8mQ=; b=E7+8J7RLa4V22Pe/4UC2r9fr1q+q/hlAoDstR0GZAVESdZXJ6QC57bQS1/EClj22Ll 5OuwfE7N8rvRGl7abfZEp714SHsnFDyWWKAu4cypO2vjro2qrQiPVb/o8hf/CpP5JLV0 1b5r7BMhshnnGOcgZoU+Jb8DCArEPZvc+eWSs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=xv317oZOdewMFqv/mk42BYFNykZzUM11QweD9mb3cEvUh0yY/8gs3thw2CuU6cZBA5 51QYlPWsJAINupFhaALTDkhppHEtzI0dYEKBd4rFN6ltD5KlWD7qbT5qKRb1ezGgaKCP wGN1+/qTmvLsBP1rFKctmkjwUZdF/BcnVtmCk= Received: by 10.66.233.10 with SMTP id f10mr3288392ugh.17.1213470638790; Sat, 14 Jun 2008 12:10:38 -0700 (PDT) Received: by 10.66.234.1 with HTTP; Sat, 14 Jun 2008 12:10:38 -0700 (PDT) Message-ID: Date: Sat, 14 Jun 2008 16:10:38 -0300 From: "Carlos A. M. dos Santos" To: "M. Warner Losh" In-Reply-To: <20080614.002703.-1142020417.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080330.005823.-432836004.imp@bsdimp.com> <1207010488.30698.42.camel@laptop2.herveybayaustralia.com.au> <20080614.002703.-1142020417.imp@bsdimp.com> Cc: freebsd-stable@freebsd.org, rock_on_the_web@comcen.com.au Subject: Re: Texas Instruments Card Reader. 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, 14 Jun 2008 19:10:40 -0000 On Sat, Jun 14, 2008 at 3:27 AM, M. Warner Losh wrote: > In message: <1207010488.30698.42.camel@laptop2.herveybayaustralia.com.au> > Da Rock writes: > : > : On Sun, 2008-03-30 at 09:18 -0300, Carlos A. M. dos Santos wrote: > : > On Sun, Mar 30, 2008 at 3:58 AM, M. Warner Losh wrote: > : > > In message: <1206767583.4015.12.camel@laptop2.herveybayaustralia.com.au> > : > > Da Rock writes: > : > > : Did anyone end up getting this to work? I'm suffering the same woes... > : > > > : > > Which device is this, specifically? > : > > > : > > Warner > : > > : > It is an SD, MS/Pro, MMC, SM and XD card reader. It is recognized by > : > the Linux "sdhci" driver. There was an email thread some time ago > : > discussing an homonymous driver for FreeBSD: > : > > : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000243.html > : > http://lists.freebsd.org/pipermail/freebsd-drivers/2006-September/000248.html > : > > : > : Thats right- I believe you were working with a ricoh card reader though. > : Is there any update to this project? A todo journal maybe? > > I've a working card reader for ricoh that I've not been able to adapt > to TI so I've never committed from a couple of difference sources... > I should find time to fix that... I have Compaq nx6320 with the TI card reader that can be used for some testing. I also have Compaq 6910p which has a Ricoh card reader. This isthe output of "pciconf -lv": none3@pci0:2:6:3: class=0x080500 card=0x30be103c chip=0x08221180 rev=0x20 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'R5C832, R5C843 SDA Standard Compliant SD Host Controller' class = base peripheral none4@pci0:2:6:4: class=0x088000 card=0x30be103c chip=0x08431180 rev=0x10 hdr=0x00 vendor = 'Ricoh Company, Ltd.' device = 'unknown Ricoh MMC Host Controller' class = base peripheral -- If you think things can't get worse it's probably only because you lack sufficient imagination. From owner-freebsd-stable@FreeBSD.ORG Sat Jun 14 23:36:03 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 175141065670 for ; Sat, 14 Jun 2008 23:36:03 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from mail1.psrk.com (64.147.114.45.static.nyinternet.net [64.147.114.45]) by mx1.freebsd.org (Postfix) with ESMTP id B75AB8FC18 for ; Sat, 14 Jun 2008 23:36:02 +0000 (UTC) (envelope-from sorin.panca@psrk.com) Received: from [62.217.213.161] (port=54517 helo=[10.80.3.229]) by mail1.psrk.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1K7etz-00005l-2C for freebsd-stable@freebsd.org; Sat, 14 Jun 2008 19:11:21 -0400 Message-ID: <48545003.7020805@psrk.com> Date: Sun, 15 Jun 2008 02:10:59 +0300 From: Sorin Panca User-Agent: Thunderbird 2.0.0.14 (X11/20080614) MIME-Version: 1.0 CC: freebsd-stable@freebsd.org References: <1213241519.54120.9.camel@Tiger.domain> In-Reply-To: <1213241519.54120.9.camel@Tiger.domain> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Antivirus-Scanner: Clean mail though you should still use an Antivirus Subject: Re: Under gnome-2.22.2, can not lock the screen 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, 14 Jun 2008 23:36:03 -0000 hald not running? I had the same problem when using Gentoo. HTH, Sorin. Pallt wrote: > Hi! > The version of the freebsd is 7.0-stable(June 9 2008), and the gnome was > also updated to 2.22.2. > But, I can not lock the screen, when I click the "Lock Screen" button > under System Menu(The acpi can works well). I can't find the right way > to let it work. > Thanks any way > > _______________________________________________ > 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" >