From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 00:14:23 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3D4B41065679; Sun, 13 Dec 2009 00:14:23 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id F03108FC0C; Sun, 13 Dec 2009 00:14:22 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id B49081E00749; Sun, 13 Dec 2009 01:14:21 +0100 (CET) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.3/8.14.3) with ESMTP id nBD0BOJ0033499; Sun, 13 Dec 2009 01:11:24 +0100 (CET) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.3/8.14.3/Submit) id nBD0BNSl033498; Sun, 13 Dec 2009 01:11:23 +0100 (CET) (envelope-from nox) Date: Sun, 13 Dec 2009 01:11:23 +0100 (CET) From: Juergen Lock Message-Id: <200912130011.nBD0BNSl033498@triton8.kn-bremen.de> To: mav@FreeBSD.org X-Newsgroups: local.list.freebsd.current In-Reply-To: <4B20EDD2.5000102@FreeBSD.org> References: <4B20EA1F.5080107@icyb.net.ua> Organization: home Cc: Alexander Best , freebsd-current@FreeBSD.org, Andriy Gapon Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 00:14:23 -0000 In article <4B20EDD2.5000102@FreeBSD.org> you write: >Andriy Gapon wrote: >> on 10/12/2009 01:07 Alexander Best said the following: >>> ah. i see. thanks for the hint. sorry mav for blaming ATA_CAM. ;) would be >>> nice if this would be fixed at some point. i believe the problem also applies >>> to tape drives, usb memory card readers, etc.? so generally speaking: any >>> devices which allow new media insertion, but don't disconnect/re-attach >>> from/to CAM. >> >> Yes, we need to get some notification that media is changed and then trigger geom >> action. Right now there is no notification from hardware in most cases and there >> is no support for handling that in drivers, AFAIK. Maybe ahci driver starts to >> add support for that. So either something needs to poll media for changes or a >> user has to trigger some action explicitly. No magic. > >Both ahci and siis drivers already have SATA Asynchronous Notifications >support, that was especially made to do that. Now AN used to receive >messages from PMP about fan-out ports physical events and working fine. > >What is needed: SATA ATAPI device with AN support (haven't checked if >there are ones on the market), enable these messages, improve cd driver >to make some useful activity (have no idea how) on such events. Doesn't scsi have `unit attention' to notify media changes? Or does that not work as expected with atapi? Just wondering... :) Juergen From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 00:20:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3DBF106568D for ; Sun, 13 Dec 2009 00:20:51 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.157]) by mx1.freebsd.org (Postfix) with ESMTP id 3396A8FC12 for ; Sun, 13 Dec 2009 00:20:51 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so569914fgg.13 for ; Sat, 12 Dec 2009 16:20:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=dfCxNwa61+vkghuQj4J+L9VUfIW+Iu+HKSA3UmVePRE=; b=jFsgV8AfAgbT0U8dMfdEMmTNONDKkK37UABtoR6RUjOvp8ynBxlCbEWoNBMeS7CEDC 1RMVeAja8Glng8erAkbbPzDWmIN5qonK7QTcaebFdZf7ehGE+RkQqbwcQPIkNPN02EHQ 6l111r9y5q780WbO9rLjdRfbdNahr4tXdqRuA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=nF/2JNZy6KqyqPYLbVoZg7fqqJtggt+IpV2LsYTdE93hCN/oYK2jpB90kHa17pC1le gBjZdO9KlsdvNj0+S+yyfYI66czPRldas94CHRekJ1JBT9GL9oU2EHWvaeE7q3SSxCwl t4cdcKLepnPhgXNI0FCzE562WLvoxEfqN18jc= Received: by 10.86.195.29 with SMTP id s29mr3771434fgf.73.1260663650180; Sat, 12 Dec 2009 16:20:50 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 13sm1103907fxm.5.2009.12.12.16.20.48 (version=SSLv3 cipher=RC4-MD5); Sat, 12 Dec 2009 16:20:49 -0800 (PST) Sender: Alexander Motin Message-ID: <4B24335F.7060405@FreeBSD.org> Date: Sun, 13 Dec 2009 02:20:47 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Juergen Lock References: <4B20EA1F.5080107@icyb.net.ua> <200912130011.nBD0BNSl033498@triton8.kn-bremen.de> In-Reply-To: <200912130011.nBD0BNSl033498@triton8.kn-bremen.de> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: Alexander Best , freebsd-current@FreeBSD.org, Andriy Gapon Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 00:20:51 -0000 Juergen Lock wrote: > In article <4B20EDD2.5000102@FreeBSD.org> you write: >> Andriy Gapon wrote: >>> on 10/12/2009 01:07 Alexander Best said the following: >>>> ah. i see. thanks for the hint. sorry mav for blaming ATA_CAM. ;) would be >>>> nice if this would be fixed at some point. i believe the problem also applies >>>> to tape drives, usb memory card readers, etc.? so generally speaking: any >>>> devices which allow new media insertion, but don't disconnect/re-attach >>>> from/to CAM. >>> Yes, we need to get some notification that media is changed and then trigger geom >>> action. Right now there is no notification from hardware in most cases and there >>> is no support for handling that in drivers, AFAIK. Maybe ahci driver starts to >>> add support for that. So either something needs to poll media for changes or a >>> user has to trigger some action explicitly. No magic. >> Both ahci and siis drivers already have SATA Asynchronous Notifications >> support, that was especially made to do that. Now AN used to receive >> messages from PMP about fan-out ports physical events and working fine. >> >> What is needed: SATA ATAPI device with AN support (haven't checked if >> there are ones on the market), enable these messages, improve cd driver >> to make some useful activity (have no idea how) on such events. > > Doesn't scsi have `unit attention' to notify media changes? Or does > that not work as expected with atapi? Haven't checked. Will try it tomorrow. But any way it require device polling. SATA AN same time is device-initiated real-time event. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 01:56:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD273106568B for ; Sun, 13 Dec 2009 01:56:12 +0000 (UTC) (envelope-from matheusber@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id 8DE1E8FC08 for ; Sun, 13 Dec 2009 01:56:12 +0000 (UTC) Received: by yxe1 with SMTP id 1so1880016yxe.3 for ; Sat, 12 Dec 2009 17:56:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:received:received :message-id:in-reply-to:references:date:subject:from:to:user-agent :mime-version:content-type:content-transfer-encoding:x-priority :importance; bh=mGaT/WRIWpUhrJGNDkzzagzE0/4qDZ3KoPLjK6zPW4c=; b=vdgMaJ1cJmQiXO47Woq12Txs8Eq6TXfyf+Kp27zhtLjqh/MPXumpbiIig7GmZsIj/p xTDtVJS/OSLTHWA4SIJYM4b38c/BHmmMhCZFVDXSQEHNCtuEFO9BqizMQP5Gb3Zh5pGk yb/iweWLkzjBZi83VitClARUMovs2uh6QGDoU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:in-reply-to:references:date:subject:from:to :user-agent:mime-version:content-type:content-transfer-encoding :x-priority:importance; b=YKMcErisrU0d/P2Rla+z8jKpGsx3pfqIKJYbsAVHqwfQ2BXGpF01GQU7PcarU9BPni pS56L9o9rtl92I1lGL6Qhs4VyQcnbuTi155uXnX1m/5OliT/EmaIpUp8IpsdishGX4zW QuaqBKQYGPEp8Vc58Xl0uvdwzktVvgcYf6u/I= Received: by 10.151.24.13 with SMTP id b13mr1409382ybj.197.1260669371740; Sat, 12 Dec 2009 17:56:11 -0800 (PST) Received: from cygnus.homeunix.com ([189.71.5.3]) by mx.google.com with ESMTPS id 6sm1407519yxg.48.2009.12.12.17.56.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 12 Dec 2009 17:56:10 -0800 (PST) Sender: Nenhum_de_Nos Received: by cygnus.homeunix.com (Postfix, from userid 80) id 17522B8051; Sat, 12 Dec 2009 22:56:06 -0300 (BRT) Received: from 189.71.57.149 (SquirrelMail authenticated user matheus) by cygnus.homeunix.com with HTTP; Sat, 12 Dec 2009 23:56:06 -0200 (BRST) Message-ID: <0866f178e6604b920f9464ec6551db28.squirrel@cygnus.homeunix.com> In-Reply-To: <4B241D2A.9030905@unsane.co.uk> References: <4B241509.8060906@FreeBSD.org> <4B241D2A.9030905@unsane.co.uk> Date: Sat, 12 Dec 2009 23:56:06 -0200 (BRST) From: "Nenhum_de_Nos" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 01:56:12 -0000 On Sat, December 12, 2009 20:46, Vincent Hoffman wrote: > Doug Barton wrote: >> I'd like to test the new stuff, but my main concern at this point is >> that I am not 100% sure how to change my fstab, what will happen if I >> need to revert, etc. I'm sure I probably _could_ figure it out, but it >> would save me a lot of time if someone could write down really >> explicit step-by-step instructions ... put this in your kernel config, >> do this to fstab, do this if it blows up, etc. >> >> Any takers? :) >> >> >> Doug >> >> > For me trying ahci was very easy. > boot using the usb image, use the fixit environment. > I use ufs so I used tunefs to label all my partitions. > tunefs -L ROOTFS /path/to/rootfs I got curious about this. what I should choose, glabel or this ? I did this using glabel and so far so good. thanks, matheus -- We will call you cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 02:27:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1C33106566C for ; Sun, 13 Dec 2009 02:27:54 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 650F08FC08 for ; Sun, 13 Dec 2009 02:27:54 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NJeAm-0006K3-Cw for freebsd-current@freebsd.org; Sun, 13 Dec 2009 03:27:00 +0100 Received: from 93-138-108-186.adsl.net.t-com.hr ([93.138.108.186]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 13 Dec 2009 03:27:00 +0100 Received: from ivoras by 93-138-108-186.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 13 Dec 2009 03:27:00 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Sun, 13 Dec 2009 03:23:09 +0100 Lines: 32 Message-ID: References: <4B241509.8060906@FreeBSD.org> <4B241D2A.9030905@unsane.co.uk> <0866f178e6604b920f9464ec6551db28.squirrel@cygnus.homeunix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 93-138-108-186.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (X11/20090612) In-Reply-To: <0866f178e6604b920f9464ec6551db28.squirrel@cygnus.homeunix.com> Sender: news Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 02:27:55 -0000 Nenhum_de_Nos wrote: > On Sat, December 12, 2009 20:46, Vincent Hoffman wrote: >> Doug Barton wrote: >>> I'd like to test the new stuff, but my main concern at this point is >>> that I am not 100% sure how to change my fstab, what will happen if I >>> need to revert, etc. I'm sure I probably _could_ figure it out, but it >>> would save me a lot of time if someone could write down really >>> explicit step-by-step instructions ... put this in your kernel config, >>> do this to fstab, do this if it blows up, etc. >>> >>> Any takers? :) >>> >>> >>> Doug >>> >>> >> For me trying ahci was very easy. >> boot using the usb image, use the fixit environment. >> I use ufs so I used tunefs to label all my partitions. >> tunefs -L ROOTFS /path/to/rootfs > > I got curious about this. what I should choose, glabel or this ? Technically, both are handled by glabel. > I did this using glabel and so far so good. All variants: ufs, ufsid, glabel are handled the same - the differences are cosmetic and a matter of user's preferences. Personally, I mostly use ufsid because it is always there and doesn't require special configuration. From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 00:43:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CB0A3106566B for ; Sun, 13 Dec 2009 00:43:54 +0000 (UTC) (envelope-from listreader@lazlarlyricon.com) Received: from proxy1.bredband.net (proxy1.bredband.net [195.54.101.71]) by mx1.freebsd.org (Postfix) with ESMTP id 823F38FC08 for ; Sun, 13 Dec 2009 00:43:54 +0000 (UTC) Received: from ipb2.telenor.se (195.54.127.165) by proxy1.bredband.net (7.3.140.3) id 4AD3E1C001A862AE; Sun, 13 Dec 2009 01:23:02 +0100 X-SMTPAUTH-B2: X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmthADrCI0tV44PPPGdsb2JhbACBSpcdgkcBAQEBN7gChCsEgWKEAQ X-IronPort-AV: E=Sophos;i="4.47,389,1257116400"; d="scan'208";a="14990059" Received: from c-cf83e355.09-42-6e6b7010.cust.bredbandsbolaget.se (HELO lazlar.kicks-ass.net) ([85.227.131.207]) by ipb2.telenor.se with ESMTP; 13 Dec 2009 01:23:02 +0100 Message-ID: <4B2433E4.2040809@lazlarlyricon.com> Date: Sun, 13 Dec 2009 01:23:00 +0100 From: Rolf Nielsen User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: "Sam Fourman Jr." References: <20091210144141.GB834@mech-cluster241.men.bris.ac.uk> <20091210095122.a164bf95.wmoran@potentialtech.com> <20091212.163352.850602504923947435.imp@bsdimp.com> <11167f520912121544j471e2f15oc2b2bdba926b46ab@mail.gmail.com> In-Reply-To: <11167f520912121544j471e2f15oc2b2bdba926b46ab@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sun, 13 Dec 2009 04:17:46 +0000 Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 00:43:54 -0000 Sam Fourman Jr. wrote: >> Are you sure that OpenBSD has a better record? > > > I found this for loose reference. > http://en.wikipedia.org/wiki/OpenBSD#Security_and_code_auditing > > I will say that even though on the surface OpenBSD appears to have a > better track record security wise > I tend to use FreeBSD for my desktop needs because of things like > Nvidia Graphics (esp now that there is amd64 support) Where's that? The Nvidia site says nothing about it yet, and the makefile for x11/nvidia-driver still says ONLY_FOR_ARCHS=i386. I'm eagerly waiting for it, but I can't find anything other than a forum post (I don't have the address handy at this computer, but I know it's somewhere in the mailing list archive) from Zander at Nvidia corporation saying it's on its way. > also wine works in FreeBSD and some of my clinets still run windows apps. > > I find FreeBSD is the middle ground the world needs between Linix and OpenBSD > > Sam Fourman Jr. > Fourman Networks > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > > > From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 01:29:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3713F1065670 for ; Sun, 13 Dec 2009 01:29:25 +0000 (UTC) (envelope-from geo.liaskos@gmail.com) Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by mx1.freebsd.org (Postfix) with ESMTP id BE2D48FC08 for ; Sun, 13 Dec 2009 01:29:24 +0000 (UTC) Received: by fxm28 with SMTP id 28so456709fxm.13 for ; Sat, 12 Dec 2009 17:29:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=ZgVF05X9L/7XVdLrHYyChbVU7rUDcc79gZNuXuFOTcw=; b=tyYVqbPmkApUGK+uWIatlgOWrA50cdwhqBYJMBMMcupXmLbcUj8QERp38/Wfe4cuPU RzkUkY5Z8Uu2X7ZKGjEZRMbgTAY1+8BgSLlM0kCzyJ3+KrTIZpq3VtJQ33iyg1g1eN7Y zQTQrDcBMCVcEWdOS+ZXUNsEttQbVCzghIero= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LSZnh6zY5r90MyV9sPaomsedAS4Z0W+k9CIPFwC2S525Dv4KvCFoedFJTy55DXNXb6 O1scf/8mAqnGzOuZfMLZbC4d/C2Qn5sV88wjferXF9f1mYtaTzIK7t+G0zqxg1rYho4z M1MAGBHvmhxAu4xNPejmqPNNqc1W7M7c0mvBc= MIME-Version: 1.0 Received: by 10.223.4.216 with SMTP id 24mr3444052fas.67.1260666226043; Sat, 12 Dec 2009 17:03:46 -0800 (PST) In-Reply-To: <4B2433E4.2040809@lazlarlyricon.com> References: <20091210144141.GB834@mech-cluster241.men.bris.ac.uk> <20091210095122.a164bf95.wmoran@potentialtech.com> <20091212.163352.850602504923947435.imp@bsdimp.com> <11167f520912121544j471e2f15oc2b2bdba926b46ab@mail.gmail.com> <4B2433E4.2040809@lazlarlyricon.com> Date: Sun, 13 Dec 2009 03:03:45 +0200 Message-ID: From: George Liaskos To: Rolf Nielsen Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Sun, 13 Dec 2009 04:18:18 +0000 Cc: "Sam Fourman Jr." , freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 01:29:25 -0000 http://www.nvnews.net/vbulletin/showthread.php?t=142120 On Sun, Dec 13, 2009 at 2:23 AM, Rolf Nielsen wrote: > Sam Fourman Jr. wrote: >>> >>> Are you sure that OpenBSD has a better record? >> >> >> I found this for loose reference. >> http://en.wikipedia.org/wiki/OpenBSD#Security_and_code_auditing >> >> I will say that even though on the surface OpenBSD appears to have a >> better track record security wise >> I tend to use FreeBSD for my desktop needs because of things like >> Nvidia Graphics (esp now that there is amd64 support) > > Where's that? The Nvidia site says nothing about it yet, and the makefile > for x11/nvidia-driver still says ONLY_FOR_ARCHS=i386. I'm eagerly waiting > for it, but I can't find anything other than a forum post (I don't have the > address handy at this computer, but I know it's somewhere in the mailing > list archive) from Zander at Nvidia corporation saying it's on its way. > >> also wine works in FreeBSD and some of my clinets still run windows apps. >> >> I find FreeBSD is the middle ground the world needs between Linix and >> OpenBSD >> >> Sam Fourman Jr. >> Fourman Networks >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> >> >> > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 10:52:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0C83C106568D for ; Sun, 13 Dec 2009 10:52:24 +0000 (UTC) (envelope-from sfourman@gmail.com) Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by mx1.freebsd.org (Postfix) with ESMTP id D8DD38FC17 for ; Sun, 13 Dec 2009 10:52:23 +0000 (UTC) Received: by pwi15 with SMTP id 15so1571841pwi.3 for ; Sun, 13 Dec 2009 02:52:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=xuCQRFA6Q7PzfvN+JDlpPMg4PBUMjxa2PYKDU5yTC7c=; b=vig9Zycl5TyxMH6edcyBDUJ/izUnzec8/j3Zmwe7ay/65HCYdDHYM5T0l8fYHhRj4f O6LiiLx3Xqzk4gvsYNLfY+iXSGyX+A6dhA2fhfx+wuZXSnKy1W155XUDWhLs9kJ+I73y VWLiCFniKV8ZLZq86hXHwpX+rWPPuPFZSuYbc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bneFX06OO9lKYa1ZN4tpNktV6r7uiYcLWGPD6n31HqB1KQOauTdyQuWLF1UpreCK1h kuwhAbKNr2C2KzNTI0yk3BRZMUlmnDsvOcdbZA/ArZwPczmkIfuabsZnZHe+1YiZXTow JI6TKSMfGDgHTVzdPsekCIo0QuY1U84OHULik= MIME-Version: 1.0 Received: by 10.142.6.1 with SMTP id 1mr1107779wff.224.1260701543458; Sun, 13 Dec 2009 02:52:23 -0800 (PST) In-Reply-To: References: Date: Sun, 13 Dec 2009 04:52:23 -0600 Message-ID: <11167f520912130252g49305a1bmca4260d069bac068@mail.gmail.com> From: "Sam Fourman Jr." To: krad Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: ZFS v22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 10:52:24 -0000 On Mon, Dec 7, 2009 at 3:56 AM, krad wrote: > Hi are there any plans to port zfs v22+ to freebsd yet? Well it is in development versions of Open Solaris, my guess is that it wont be too long. I would much love to try it out as well. We will all wait and see :) Just want to take a moment to thank all who work on ZFS for FreeBSD. Sam Fourman Jr. From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 11:12:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0496E1065670; Sun, 13 Dec 2009 11:12:05 +0000 (UTC) (envelope-from simon@nitro.dk) Received: from mx.nitro.dk (unknown [77.75.165.90]) by mx1.freebsd.org (Postfix) with ESMTP id BA24C8FC15; Sun, 13 Dec 2009 11:12:04 +0000 (UTC) Received: from frankie.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 06EBB2D4897; Sun, 13 Dec 2009 11:09:29 +0000 (UTC) Received: by frankie.nitro.dk (Postfix, from userid 2000) id 60C8DE04B9; Sun, 13 Dec 2009 12:12:03 +0100 (CET) Date: Sun, 13 Dec 2009 12:12:03 +0100 From: "Simon L. Nielsen" To: Max Laier Message-ID: <20091213111202.GA1309@frankie.nitro.dk> References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <200912130032.54740.max@love2party.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912130032.54740.max@love2party.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Daniel Thiele , freebsd-current@freebsd.org, shaun@freebsd.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 11:12:05 -0000 On 2009.12.13 00:32:54 +0100, Max Laier wrote: > On Saturday 12 December 2009 23:40:53 Simon L. Nielsen wrote: > > On 2009.12.12 23:07:58 +0100, Daniel Thiele wrote: > > > Is there maybe another way to achieve onetime /tmp encryption that > > > I am missing? Preferably one that does not involve huge changes to > > > > Well, I use the simple one - make /tmp a memory file system. locate > > is sometimes not too happy with an e.g. 50MB /tmp, but otherwise it > > works very well for me. > > > > [simon@arthur:~] grep tmp /etc/rc.conf > > tmpmfs="YES" > > tmpsize="50M" > > but tmpfs pages are swappable IIRC. This would mean that the data might end > up unencrypted on secondary storage. Well, above is tmp_m_fs, which is just UFS on md(4) devices. But that can also be swapped out, so that's one reason I encrypt swap. If you care enough to encrypt /tmp you should also encrypt swap anyway. I never looked at tmpfs, as I heard that it isn't really stable yet. -- Simon L. Nielsen From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 12:00:30 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF8B41065692; Sun, 13 Dec 2009 12:00:30 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id 7B5538FC4A; Sun, 13 Dec 2009 12:00:30 +0000 (UTC) Received: from [195.4.92.12] (helo=2.mx.freenet.de) by mout0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NJn7k-0001OU-Tt; Sun, 13 Dec 2009 13:00:28 +0100 Received: from p57ae0dd2.dip0.t-ipconnect.de ([87.174.13.210]:23106 helo=ernst.jennejohn.org) by 2.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1NJn7k-0006kk-BM; Sun, 13 Dec 2009 13:00:28 +0100 Date: Sun, 13 Dec 2009 13:00:27 +0100 From: Gary Jennejohn To: "Simon L. Nielsen" Message-ID: <20091213130027.4c3d758f@ernst.jennejohn.org> In-Reply-To: <20091213111202.GA1309@frankie.nitro.dk> References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <200912130032.54740.max@love2party.net> <20091213111202.GA1309@frankie.nitro.dk> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Max Laier , Daniel Thiele , shaun@freebsd.org, freebsd-current@freebsd.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 12:00:31 -0000 On Sun, 13 Dec 2009 12:12:03 +0100 "Simon L. Nielsen" wrote: > I never looked at tmpfs, as I heard that it isn't really stable yet. > I've been using it for months without any problems. But I have lots of memory and swap. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 14:55:31 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0B9DC10656AD for ; Sun, 13 Dec 2009 14:55:31 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id B97EE8FC14 for ; Sun, 13 Dec 2009 14:55:30 +0000 (UTC) Received: from [95.27.64.15] (port=23946 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NJpr6-000BkV-VM for current@freebsd.org; Sun, 13 Dec 2009 17:55:28 +0300 Message-ID: <4B250060.3050609@lissyara.su> Date: Sun, 13 Dec 2009 17:55:28 +0300 From: Alex Keda User-Agent: Thunderbird 2.0.0.23 (X11/20091129) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Cc: Subject: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 14:55:31 -0000 hi! After latest changes in FreeBSD i have another behavior for applications such as vi, ee, vim ... Previously - if I open file for edit and close it - on screen stay file text. Now, if I close file - on screen - nothing - only 'vim /etc/rc.conf' Some behavior for top. if I set TERM=cons25r - it as an before, but, vim's behavior not adequacy - it forget about many keyboard buttons (such as arrow) I see it only with using X - in clean console - all OK. if I open ssh session to remote server - all OK. Problem exists only locally. From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 15:02:02 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB5E5106566B for ; Sun, 13 Dec 2009 15:02:02 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (mail.fujibayashi.jp [IPv6:2001:470:9954:ffff::2]) by mx1.freebsd.org (Postfix) with ESMTP id 986B38FC20 for ; Sun, 13 Dec 2009 15:02:01 +0000 (UTC) Received: from [IPv6:2001:470:9f2d:0:1::1] (omoikane.gensokyo.fujibayashi.jp [IPv6:2001:470:9f2d:0:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id 3449C10F463; Mon, 14 Dec 2009 00:01:59 +0900 (JST) Message-ID: <4B2501E4.8070403@haruhiism.net> Date: Sun, 13 Dec 2009 18:01:56 +0300 From: Kamigishi Rei User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Alex Keda References: <4B250060.3050609@lissyara.su> In-Reply-To: <4B250060.3050609@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 15:02:02 -0000 On 13.12.2009 17:55, Alex Keda wrote: > After latest changes in FreeBSD i have another behavior for applications > such as vi, ee, vim ... > Previously - if I open file for edit and close it - on screen stay > file text. Now, if I close file - on screen - nothing - only > 'vim /etc/rc.conf' > Some behavior for top. > if I set TERM=cons25r - it as an before, but, vim's behavior not > adequacy - it forget about many keyboard buttons (such as arrow) > > I see it only with using X - in clean console - all OK. > if I open ssh session to remote server - all OK. > Problem exists only locally. I guess you haven't checked the FreeBSD-CURRENT mailing list archives. Please consult the following thread: http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013273.html -- Kamigishi Rei KREI-RIPE http://fujibayashi.jp From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 15:07:59 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B6CE6106566B for ; Sun, 13 Dec 2009 15:07:59 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (unknown [IPv6:2001:470:1f09:679::1]) by mx1.freebsd.org (Postfix) with ESMTP id 83E3F8FC14 for ; Sun, 13 Dec 2009 15:07:59 +0000 (UTC) Received: from unknown (unknown [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 936DA8354; Sun, 13 Dec 2009 15:08:01 +0000 (UTC) Date: Sun, 13 Dec 2009 15:07:29 +0000 From: Bruce Cran To: Alex Keda Message-ID: <20091213150729.000015ef@unknown> In-Reply-To: <4B250060.3050609@lissyara.su> References: <4B250060.3050609@lissyara.su> X-Mailer: Claws Mail 3.7.2cvs27 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 15:07:59 -0000 On Sun, 13 Dec 2009 17:55:28 +0300 Alex Keda wrote: > hi! > After latest changes in FreeBSD i have another behavior for > applications such as vi, ee, vim ... > Previously - if I open file for edit and close it - on screen stay > file text. Now, if I close file - on screen - nothing - only > 'vim /etc/rc.conf' > Some behavior for top. > if I set TERM=cons25r - it as an before, but, vim's behavior not > adequacy - it forget about many keyboard buttons (such as arrow) > > I see it only with using X - in clean console - all OK. > if I open ssh session to remote server - all OK. > Problem exists only locally. There was a discussion on svn-src-all a few days ago, and on another mailing list a few months ago. See http://lists.freebsd.org/pipermail/svn-src-all/2009-December/016715.html for the most recent discussion, which contains links to the previous one too. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 15:31:06 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D4201065670 for ; Sun, 13 Dec 2009 15:31:06 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 449628FC1A for ; Sun, 13 Dec 2009 15:31:05 +0000 (UTC) Received: from [95.27.64.15] (port=37581 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NJqPY-000DwX-0R; Sun, 13 Dec 2009 18:31:04 +0300 Message-ID: <4B2508B7.6060203@lissyara.su> Date: Sun, 13 Dec 2009 18:31:03 +0300 From: Alex Keda User-Agent: Thunderbird 2.0.0.23 (X11/20091129) MIME-Version: 1.0 To: Bruce Cran References: <4B250060.3050609@lissyara.su> <20091213150729.000015ef@unknown> In-Reply-To: <20091213150729.000015ef@unknown> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Cc: FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 15:31:06 -0000 Bruce Cran пишет: > On Sun, 13 Dec 2009 17:55:28 +0300 > Alex Keda wrote: > >> hi! >> After latest changes in FreeBSD i have another behavior for >> applications such as vi, ee, vim ... >> Previously - if I open file for edit and close it - on screen stay >> file text. Now, if I close file - on screen - nothing - only >> 'vim /etc/rc.conf' >> Some behavior for top. >> if I set TERM=cons25r - it as an before, but, vim's behavior not >> adequacy - it forget about many keyboard buttons (such as arrow) >> >> I see it only with using X - in clean console - all OK. >> if I open ssh session to remote server - all OK. >> Problem exists only locally. > > There was a discussion on svn-src-all a few days ago, and on another > mailing list a few months ago. See > http://lists.freebsd.org/pipermail/svn-src-all/2009-December/016715.html > for the most recent discussion, which contains links to the previous > one too. and so - patch for old behavior commited? or, need wait some years? =) From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 15:33:32 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 05125106566B for ; Sun, 13 Dec 2009 15:33:32 +0000 (UTC) (envelope-from vova@parallels.com) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 7669F8FC0C for ; Sun, 13 Dec 2009 15:33:30 +0000 (UTC) Received: from vbook.fbsd.ru ([10.24.21.214]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id nBDFXOUu005625 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 13 Dec 2009 18:33:26 +0300 (MSK) Received: from vova by vbook.fbsd.ru with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NJqRn-0001uw-Ev; Sun, 13 Dec 2009 18:33:23 +0300 From: Vladimir Grebenschikov To: Andrey Chernov In-Reply-To: <20091130044130.GA55612@nagual.pp.ru> References: <20091111101207.GF64905@hoeg.nl> <20091113060021.GW64905@hoeg.nl> <20091130044130.GA55612@nagual.pp.ru> Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: quoted-printable Date: Sun, 13 Dec 2009 18:33:22 +0300 Message-ID: <1260718402.2505.37.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: Ed Schouten , FreeBSD Current Subject: Re: [Heads up] TERM=xterm is now the default (on non-i386) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 15:33:32 -0000 Hi=20 Any chance to get it fixed somehow ?=20 midnight commander does not work correctly even with no screen-maps, vidcontrol -T xterm, env TERM=3Dxterm LANG=3Dru_RU.UTF-8 also, console does not handle correctly multi-byte utf-8 characters (it should already or not ?)=20 -----Original Message----- From: Andrey Chernov To: Ed Schouten Cc: FreeBSD Current Subject: Re: [Heads up] TERM=3Dxterm is now the default (on non-i386) Date: Mon, 30 Nov 2009 07:41:30 +0300 On Fri, Nov 13, 2009 at 07:00:21AM +0100, Ed Schouten wrote: > Hi folks, >=20 > I just committed the previously mentioned patch to SVN. Please refer to > the last part of the commit message to see what you can do when you run > into trouble. It seems xterm emulator can't co-exist with screen maps, namely vidcontrol -l koi8-r2cp866 I got Russian letters everywhere instead of vt100 pseudographics due to=20 missing (i.e. default) ac=3D termcap capability (f.e. in tzsetup etc.) There are 2 ways to fix it. 1) Make separate xterm-r with corrected ac=3D (that way is ugly). 2) Don't seek for vt100 pseudographics in loaded font at all, just use=20 internal kernel font. Please decide how to fix this better. For now only fallback to '-T cons25'=20 is solution for Russian users. --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 16:15:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC220106566C for ; Sun, 13 Dec 2009 16:15:48 +0000 (UTC) (envelope-from dthiele@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 1274D8FC14 for ; Sun, 13 Dec 2009 16:15:47 +0000 (UTC) Received: (qmail invoked by alias); 13 Dec 2009 16:15:45 -0000 Received: from p548643FE.dip.t-dialin.net (EHLO impala.vnws.lan) [84.134.67.254] by mail.gmx.net (mp049) with SMTP; 13 Dec 2009 17:15:45 +0100 X-Authenticated: #19302822 X-Provags-ID: V01U2FsdGVkX18/eYo4hLU/4dycYZooq/6RkfFpkrKbJnjSIpnKAN Dx3fCOoNy5FNrD Message-ID: <4B251476.1090303@gmx.net> Date: Sun, 13 Dec 2009 17:21:10 +0100 From: Daniel Thiele User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: "Simon L. Nielsen" References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> In-Reply-To: <20091212224052.GF1417@arthur.nitro.dk> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.44 Cc: freebsd-current@freebsd.org, shaun@FreeBSD.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 16:15:48 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Simon L. Nielsen wrote: > On 2009.12.12 23:07:58 +0100, Daniel Thiele wrote: > >> Is there maybe another way to achieve onetime /tmp encryption that >> I am missing? Preferably one that does not involve huge changes to > > Well, I use the simple one - make /tmp a memory file system. locate > is sometimes not too happy with an e.g. 50MB /tmp, but otherwise it > works very well for me. > > [simon@arthur:~] grep tmp /etc/rc.conf > tmpmfs="YES" > tmpsize="50M" > Using a memory file system (together, of course, with an encrypted swap partition) also crossed my mind. While a small memory based /tmp may be sufficient for most desktop workloads, I don't think that I can chum up with it. Especially when you consider that disk space is orders of magnitudes cheaper than RAM. Since the tmpmfs option does not scale well with growing /tmp space requirements (at least not in a cost-effective way), I am keen to know why the patch I dug up in my first mail has never been committed. Was it solely a lack of interest or time, or have there been other reasons? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJLJRRyAAoJEB+84OrFyizNTRcP/0PJNcV5kZvN5kjboL1nCYvQ xXY9Q4tDpXPtQhNfp6oDPwcjawjxGWGH9OLKZNU3mO/y81/SExoNmJWhrP2Z99fP 4nP+xIPeNw9FXZEinVZYrm7QFtxdU/5F/K/XkPQOdWHnlevnhOOiSEN26Aj+DCiI aqCgPocAQ2VQs4b5MzoP7MT9uMT8j85s+B0SXThJm67qZ+HfaVdHjLOmJBLtpa/0 ZiAVMmJVs1merNB8XTG7RRaYs++oBhGqbFlFZYog+0/Qp9vBB5vGc8AkYmRwza2s MTPNcom/R1P180bdO9jjvSmuKztkVpcfVfT2zIw2JQ88a+4X5uXNEnJspTvGoEa+ X3c16Xrm85LDzpmmaxaX1dyC9Uh891O72Z2R+mZv/fNWsU3WipEZg7fJLZ9/EOLB Kj9qQexhQkYIwobi1TlN38qcUM+L/56n63ffPULtj67yyD0+lufQDfqErduvCrxL xAl8xdwEXgJGnSjMIib6ya5xpqRMK6H3mCk/eupFhUYMfLf8u07aRLS5uWTaOQH7 nX5+VlmyXJojYhxsSF/XE2B11Tgnti0gNtsVgHOn3/mPWVGirdRhrRPeJsi282AN eaBsPVsNyNQNQPuil1Rxzpd0gBzzLKUUPxu0mxBcW0t+KKxZQeCTHLUYesLaOZPt YHleJG0coB9/Gyy5WwXY =r8pS -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 16:30:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A0520106566C for ; Sun, 13 Dec 2009 16:30:39 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by mx1.freebsd.org (Postfix) with ESMTP id 334218FC13 for ; Sun, 13 Dec 2009 16:30:38 +0000 (UTC) Received: by fxm28 with SMTP id 28so713979fxm.13 for ; Sun, 13 Dec 2009 08:30:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=2N/2nLtN/962m7ioKoA0Aq4275s2vUC3nNh9/RlVF4w=; b=sB0U5F4eKlnEUiejUj/B4Eq3JjMLNxzpqL+y+rYeBDogeCAb+UJk9fbgwCxtEJq4ZU q2qxFP15fbXtHfBaQlYA8wvwAqTDP63aa43I+LTsZQmmgijFuU6MCULK3VDHRykCasg6 Sn/3IO1NGQB6Hj5X8AmefQ1u4KCiN6dQWLL3w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Tt0zkYvrIwObn041/p9CJVLNT7ePFT2xTnH2cSukPW6vp/mCqYEs/ZPC9EdJ5X1rOc K5n+Rrsz9h2E8ktX15cLTFLKKk6MuKgXwlGeXV/juOix6MdhED/YVyIiKOsBhxDpua0u BrQveqn9RT8C4bZg1Tv1iRMfPWs9BiKCS21Hk= MIME-Version: 1.0 Received: by 10.239.183.21 with SMTP id s21mr388112hbg.5.1260721838082; Sun, 13 Dec 2009 08:30:38 -0800 (PST) In-Reply-To: <11167f520912130252g49305a1bmca4260d069bac068@mail.gmail.com> References: <11167f520912130252g49305a1bmca4260d069bac068@mail.gmail.com> Date: Sun, 13 Dec 2009 16:30:38 +0000 Message-ID: From: krad To: "Sam Fourman Jr." Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: ZFS v22 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 16:30:39 -0000 2009/12/13 Sam Fourman Jr. > On Mon, Dec 7, 2009 at 3:56 AM, krad wrote: > > Hi are there any plans to port zfs v22+ to freebsd yet? > > Well it is in development versions of Open Solaris, my guess is that > it wont be too long. > I would much love to try it out as well. > > We will all wait and see :) > > Just want to take a moment to thank all who work on ZFS for FreeBSD. > > Sam Fourman Jr. > and don't forget dtrace, another killer app. Hmm smf and fms would be goodo as well 8) From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 16:45:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79C76106568F for ; Sun, 13 Dec 2009 16:45:18 +0000 (UTC) (envelope-from tmseck@netcologne.de) Received: from smtp6.netcologne.de (smtp6.netcologne.de [194.8.194.26]) by mx1.freebsd.org (Postfix) with ESMTP id 3FDED8FC17 for ; Sun, 13 Dec 2009 16:45:17 +0000 (UTC) Received: from wcfields.tmseck.homedns.org (xdsl-89-0-152-32.netcologne.de [89.0.152.32]) by smtp6.netcologne.de (Postfix) with SMTP id 923142A13B1 for ; Sun, 13 Dec 2009 17:27:12 +0100 (CET) Received: (qmail 1172 invoked by uid 1001); 13 Dec 2009 16:27:12 -0000 Date: 13 Dec 2009 16:27:12 -0000 Message-ID: <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> From: tmseck-lists@netcologne.de (Thomas-Martin Seck) To: "Johan Hendriks" In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> X-Newsgroups: gmane.os.freebsd.current X-Attribution: tms Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 16:45:18 -0000 * Johan Hendriks : (Squid breakage in the YP/NIS helper) > A long shot > Could it be that you have set the following in your src.conf > WITHOUT_NIS= yes > WITHOUT_RCMDS= yes > WITHOUT_RCS= yes > > If i set those i get a similar error with squid (on i386 and amd64 ) This is possible; the Squid 2.7 port still relies on WITHOUT_NIS/NO_NIS being set in make.conf. Due to the make.conf/src.conf split this does no longer work. I have added an OPTION to turn off NIS support to the squid 3.x ports and will merge this change into the Squid 2.7 port along with other changes soon. In the meantime you can work around this if you build www/squid with "make -DWITHOUT_NIS" or by adding WITHOUT_NIS=yes to /etc/make.conf. The same applies to systems built/installed without Heimdal support. Sorry for the breakage. From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 16:56:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF27F1065672; Sun, 13 Dec 2009 16:56:48 +0000 (UTC) (envelope-from shaun@FreeBSD.org) Received: from dione.picobyte.net (81-86-230-94.dsl.pipex.com [81.86.230.94]) by mx1.freebsd.org (Postfix) with SMTP id 057C38FC14; Sun, 13 Dec 2009 16:56:47 +0000 (UTC) Received: from charon.picobyte.net (charon.picobyte.net [IPv6:2001:770:15d::fe03]) by dione.picobyte.net (Postfix) with ESMTP id AD155B83A; Sun, 13 Dec 2009 16:38:04 +0000 (GMT) Date: Sun, 13 Dec 2009 16:38:04 +0000 From: Shaun Amott To: Olivier Smedts Message-ID: <20091213163803.GA45265@charon.picobyte.net> References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <367b2c980912121517h8e87f03x639f8a9818ae7a9e@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline In-Reply-To: <367b2c980912121517h8e87f03x639f8a9818ae7a9e@mail.gmail.com> User-Agent: Mutt/1.5.20 (FreeBSD i386) Cc: Daniel Thiele , "Simon L. Nielsen" , freebsd-current@freebsd.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 16:56:48 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 13, 2009 at 12:17:25AM +0100, Olivier Smedts wrote: >=20 > 2009/12/12 Simon L. Nielsen : > > On 2009.12.12 23:07:58 +0100, Daniel Thiele wrote: > > > >> Is there maybe another way to achieve onetime /tmp encryption that > >> I am missing? Preferably one that does not involve huge changes to > > > > Well, I use the simple one - make /tmp a memory file system. =A0locate > > is sometimes not too happy with an e.g. 50MB /tmp, but otherwise it > > works very well for me. > > > > [simon@arthur:~] grep tmp /etc/rc.conf > > tmpmfs=3D"YES" > > tmpsize=3D"50M" >=20 > What about tmpfs ? >=20 > [0:16] zozo@q 1002 ~% grep tmp /etc/fstab > tmpfs /tmp tmpfs rw,mode=3D1777 0 0 > [0:16] zozo@q 1003 ~% df -h /tmp > Filesystem Size Used Avail Capacity Mounted on > tmpfs 2.9G 12K 2.9G 0% /tmp >=20 Both good ideas, but not always an adequate solution: on at least some of the systems where I use an encrypted /tmp, the data usually occupy more space on that filesystem than would fit in RAM. This is a simple patch, and merely an extension of an idea that is already for swap partitions. Perhaps someone could commit it? --=20 Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson --2fHTh5uZTiUOsy+g Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkslGGsACgkQkmhdCGs4eppvgwCfT467qvCHYdH/s9XtsZ5ZMvBQ HeYAoMvOK1meWQqjctJiNTdMhuHA1XX5 =dp/+ -----END PGP SIGNATURE----- --2fHTh5uZTiUOsy+g-- From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 17:03:39 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1864D1065672; Sun, 13 Dec 2009 17:03:39 +0000 (UTC) (envelope-from nox@jelal.kn-bremen.de) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id C664F8FC0A; Sun, 13 Dec 2009 17:03:38 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 051DF1E0075B; Sun, 13 Dec 2009 18:03:37 +0100 (CET) Received: from triton8.kn-bremen.de (noident@localhost [127.0.0.1]) by triton8.kn-bremen.de (8.14.3/8.14.3) with ESMTP id nBDH1icr011733; Sun, 13 Dec 2009 18:01:44 +0100 (CET) (envelope-from nox@triton8.kn-bremen.de) Received: (from nox@localhost) by triton8.kn-bremen.de (8.14.3/8.14.3/Submit) id nBDH1imL011732; Sun, 13 Dec 2009 18:01:44 +0100 (CET) (envelope-from nox) From: Juergen Lock Date: Sun, 13 Dec 2009 18:01:43 +0100 To: Alexander Motin Message-ID: <20091213170143.GA11564@triton8.kn-bremen.de> References: <4B20EA1F.5080107@icyb.net.ua> <200912130011.nBD0BNSl033498@triton8.kn-bremen.de> <4B24335F.7060405@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B24335F.7060405@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Alexander Best , freebsd-current@FreeBSD.org, Juergen Lock , Andriy Gapon Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 17:03:39 -0000 On Sun, Dec 13, 2009 at 02:20:47AM +0200, Alexander Motin wrote: > Juergen Lock wrote: > > In article <4B20EDD2.5000102@FreeBSD.org> you write: > >> Andriy Gapon wrote: > >>> on 10/12/2009 01:07 Alexander Best said the following: > >>>> ah. i see. thanks for the hint. sorry mav for blaming ATA_CAM. ;) would be > >>>> nice if this would be fixed at some point. i believe the problem also applies > >>>> to tape drives, usb memory card readers, etc.? so generally speaking: any > >>>> devices which allow new media insertion, but don't disconnect/re-attach > >>>> from/to CAM. > >>> Yes, we need to get some notification that media is changed and then trigger geom > >>> action. Right now there is no notification from hardware in most cases and there > >>> is no support for handling that in drivers, AFAIK. Maybe ahci driver starts to > >>> add support for that. So either something needs to poll media for changes or a > >>> user has to trigger some action explicitly. No magic. > >> Both ahci and siis drivers already have SATA Asynchronous Notifications > >> support, that was especially made to do that. Now AN used to receive > >> messages from PMP about fan-out ports physical events and working fine. > >> > >> What is needed: SATA ATAPI device with AN support (haven't checked if > >> there are ones on the market), enable these messages, improve cd driver > >> to make some useful activity (have no idea how) on such events. > > > > Doesn't scsi have `unit attention' to notify media changes? Or does > > that not work as expected with atapi? > > Haven't checked. Will try it tomorrow. But any way it require device > polling. SATA AN same time is device-initiated real-time event. Ah ok. Cheers, Juergen From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 18:21:38 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B90FA1065670 for ; Sun, 13 Dec 2009 18:21:38 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (mail.fujibayashi.jp [IPv6:2001:470:9954:ffff::2]) by mx1.freebsd.org (Postfix) with ESMTP id 75B368FC1C for ; Sun, 13 Dec 2009 18:21:38 +0000 (UTC) Received: from [192.168.0.146] (corp.infobox.ru [77.221.128.82]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id 2EE7810FD49; Mon, 14 Dec 2009 03:21:36 +0900 (JST) Message-ID: <4B2530AE.8060901@haruhiism.net> Date: Sun, 13 Dec 2009 21:21:34 +0300 From: "K.R." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Alex Keda References: <4B250060.3050609@lissyara.su> <20091213150729.000015ef@unknown> <4B2508B7.6060203@lissyara.su> In-Reply-To: <4B2508B7.6060203@lissyara.su> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Bruce Cran , FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 18:21:38 -0000 On 13.12.2009 18:31, Alex Keda wrote: >> There was a discussion on svn-src-all a few days ago, and on another >> mailing list a few months ago. See >> http://lists.freebsd.org/pipermail/svn-src-all/2009-December/016715.html >> for the most recent discussion, which contains links to the previous >> one too. > > and so - patch for old behavior commited? > or, need wait some years? =) Why would one wait, when there's a working solution like http://lists.freebsd.org/pipermail/svn-src-head/2009-July/009102.html ? (Myself, I like the default *xterm* behaviour; it keeps my xterm sessions clean.) -- Kamigishi Rei KREI-RIPE From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 18:42:29 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE6FC1065696 for ; Sun, 13 Dec 2009 18:42:29 +0000 (UTC) (envelope-from admin@lissyara.su) Received: from hosting.lissyara.su (hosting.lissyara.su [77.221.149.162]) by mx1.freebsd.org (Postfix) with ESMTP id 8545A8FC08 for ; Sun, 13 Dec 2009 18:42:29 +0000 (UTC) Received: from [95.27.64.15] (port=43525 helo=HP.lissyara.su) by hosting.lissyara.su with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.71 (FreeBSD)) (envelope-from ) id 1NJtOl-0001Te-5z; Sun, 13 Dec 2009 21:42:27 +0300 Message-ID: <4B253592.90506@lissyara.su> Date: Sun, 13 Dec 2009 21:42:26 +0300 From: Alex Keda User-Agent: Thunderbird 2.0.0.23 (X11/20091129) MIME-Version: 1.0 To: "K.R." References: <4B250060.3050609@lissyara.su> <20091213150729.000015ef@unknown> <4B2508B7.6060203@lissyara.su> <4B2530AE.8060901@haruhiism.net> In-Reply-To: <4B2530AE.8060901@haruhiism.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Description: if spam count > 60 - this is spam X-Spam-Count: 0 X-Descriptions: powered by www.lissyara.su X-Bounce-ID: hosting.lissyara.su Cc: Bruce Cran , FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 18:42:29 -0000 K.R. пишет: > On 13.12.2009 18:31, Alex Keda wrote: >>> There was a discussion on svn-src-all a few days ago, and on another >>> mailing list a few months ago. See >>> http://lists.freebsd.org/pipermail/svn-src-all/2009-December/016715.html >>> for the most recent discussion, which contains links to the previous >>> one too. >> >> and so - patch for old behavior commited? >> or, need wait some years? =) > > Why would one wait, when there's a working solution like > http://lists.freebsd.org/pipermail/svn-src-head/2009-July/009102.html ? > > (Myself, I like the default *xterm* behaviour; it keeps my xterm > sessions clean.) for clean, use "clear" command what's use for reading man and typo command from man - second console? for reproduce command from script? default behavior for FreeBSD - stay screen on place. From owner-freebsd-current@FreeBSD.ORG Sun Dec 13 20:15:19 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6C4E1065676 for ; Sun, 13 Dec 2009 20:15:19 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 805C98FC13 for ; Sun, 13 Dec 2009 20:15:19 +0000 (UTC) Received: (qmail 10597 invoked by uid 399); 13 Dec 2009 20:15:17 -0000 Received: from localhost (HELO ?192.168.0.110?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 13 Dec 2009 20:15:17 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B254B58.8060205@FreeBSD.org> Date: Sun, 13 Dec 2009 12:15:20 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Alex Keda References: <4B250060.3050609@lissyara.su> <20091213150729.000015ef@unknown> <4B2508B7.6060203@lissyara.su> <4B2530AE.8060901@haruhiism.net> <4B253592.90506@lissyara.su> In-Reply-To: <4B253592.90506@lissyara.su> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Bruce Cran , FreeBSD Current Subject: Re: About new console driver and applications behavior X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Dec 2009 20:15:20 -0000 Alex Keda wrote: >> http://lists.freebsd.org/pipermail/svn-src-head/2009-July/009102.html ? Please read the thread till you find the solution that I posted. It's quite simple and painless. Meanwhile, the consensus seems to be forming to change it back, so at some point soon that's likely to happen, FYI. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 02:27:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ADE731065679 for ; Mon, 14 Dec 2009 02:27:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 594238FC0A for ; Mon, 14 Dec 2009 02:27:16 +0000 (UTC) Received: (qmail 30132 invoked by uid 399); 14 Dec 2009 02:27:15 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 02:27:15 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B25A28A.1040305@FreeBSD.org> Date: Sun, 13 Dec 2009 18:27:22 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Ivan Voras References: <4B241509.8060906@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 02:27:16 -0000 Ivan Voras wrote: > Doug Barton wrote: >> I'd like to test the new stuff, but my main concern at this point is >> that I am not 100% sure how to change my fstab, what will happen if I >> need to revert, etc. I'm sure I probably _could_ figure it out, but it >> would save me a lot of time if someone could write down really >> explicit step-by-step instructions ... put this in your kernel config, >> do this to fstab, do this if it blows up, etc. >> >> Any takers? :) > > Maybe > > http://ivoras.sharanet.org/blog/tree/2009-11-17.trying-ahci-in-8.0.html That has a lot of good information, but most of it is irrelevant to me (you seriously missed the "for dummies" issue). :) Also, thanks to everyone who gave suggestions related to glabel, but I don't want to use it. What I've done that's worked is: 1. Add "options ATA_CAM" to my kernel config. AFAICS it's not necessary to do anything special with ahci, that's included in ata_cam. 2. I already had atapicam in my kernel (which I commented out since it's included in ata_cam as well), but I'm assuming that at least the following are needed: device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device cd # CD device pass # Passthrough device (direct SCSI access) 3. Comment out everything ata-related EXCEPT "device ata". Without that one the kernel boots but stops cold when it tries to mount the root file system. 4. Edit fstab. I actually copied all the ad0 entries, commented out the old ones, and in the new ones I changed "ad0" to "ada0". 5. Update dumpdev in /etc/rc.conf So far so good. :) I am actually kind of curious as to why "device ata" is needed, but it doesn't seem to be hurting anything. Regarding what's on your web page Ivan, I'm confused about NCQ. I did what you suggested: camcontrol tags ada0 (pass0:ata0:0:0:0): device openings: 1 Which is different from what you got. The relevant lines from 'camcontrol identify' are: pass0: ATA-7 SATA 1.x device pass0: 100.000MB/s transfers (UDMA5, PIO size 8192bytes) protocol ATA/ATAPI-7 SATA 1.x Native Command Queuing (NCQ) yes 31/0x1F Is there something I need to change to make this work, or is NCQ not available for SATA 1.x devices? Are there any other parameters worth tweaking? Thanks, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 03:16:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FB1310656AA; Mon, 14 Dec 2009 03:16:55 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (uffner.com [66.208.243.25]) by mx1.freebsd.org (Postfix) with ESMTP id 4C13E8FC14; Mon, 14 Dec 2009 03:16:54 +0000 (UTC) Received: from xiombarg.uffner.com (static-71-162-143-94.phlapa.fios.verizon.net [71.162.143.94]) (authenticated bits=0) by eris.uffner.com (8.14.3/8.14.3) with ESMTP id nBE3Iv2X099051 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 13 Dec 2009 22:19:08 -0500 (EST) (envelope-from tom@uffner.com) Message-ID: <4B25AE1A.80206@uffner.com> Date: Sun, 13 Dec 2009 22:16:42 -0500 From: Tom Uffner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20090925 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Alexander Motin References: <4B1671EE.1010301@FreeBSD.org> In-Reply-To: <4B1671EE.1010301@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 03:16:55 -0000 Alexander Motin wrote: > Hi. > > I would like to present for testing patch, turning ata(4) controllers > drivers into native SIMs of new CAM ATA infrastructure. This patch adds > new ATA_CAM kernel option, which allows switching between legacy and new > CAM-based operation modes. To enable new mode you should add > options ATA_CAM > line to the kernel configuration file in addition to the ones required > by CAM infrastructure and rebuild/reinstall the kernel. > > In legacy mode, the only difference will be - the way in which SATA > speeds reported. Instead of mixing SATA revisions with PATA modes, they > were separated, as they should be, allowing, for example, DMA-incapable > or buggy SATA devices (usually PATA devices with built-in PATA/SATA > converter) to work in PIO mode. > > While doing it, I had to completely rewrite ata(4) mode setting code, so > legacy operation also need to be tested. I have successfully tested it > on Intel, NVidia, VIA, Marvell, JMicron PATA controllers with all > PIO/DMA modes. Different controllers feedbacks are especially welcome. this change breaks my Promise SATA card atapci0: port 0xdc00-0xdc7f,0xd800-0xd8ff mem 0xfeaff000-0xfeafffff,0xfeac0000-0xfeadffff irq 23 at device 11.0 on pci2 kernels from after the commit on 12/6 are unable to mount my drives. i get (from memory, since i can't even get to single user mode) WARNING - READ_DMA UDMA ICRC error followed by lots of SETFEATURE foo errors then a READ_DMA timeout followed by a bus reset and the cycle repeats... before this commit it worked fine. this is in the legacy mode. i am building a kernel with "options ATA_CAM" now tom From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 03:28:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA4891065692 for ; Mon, 14 Dec 2009 03:28:04 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 8F1CB8FC18 for ; Mon, 14 Dec 2009 03:28:04 +0000 (UTC) Received: (qmail 15187 invoked by uid 399); 14 Dec 2009 03:28:03 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 03:28:03 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B25B0CA.1070006@FreeBSD.org> Date: Sun, 13 Dec 2009 19:28:10 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Robert Watson References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: multipart/mixed; boundary="------------050006080001020009090704" Cc: Alex Keda , freebsd-current Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 03:28:05 -0000 This is a multi-part message in MIME format. --------------050006080001020009090704 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Robert Watson wrote: > > On Sat, 12 Dec 2009, Doug Barton wrote: > >> Alex Keda wrote: >>> For those who have recently engaged in FreeBSD, and inexperienced >>> managers who have inherited a server "by inheritance" is often the >>> question arises - where to find the configuration file in which to >>> compile your kernel? (Of course, a file by that time there =)) >> >> I actually thought that was already done, but I see now that it's not. >> I would like to see this as well, any objections? > > I'd say go for it. Ok, here is the proposed patch. I'll commit it tomorrow unless someone objects. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ --------------050006080001020009090704 Content-Type: text/plain; name="include-config-file.diff" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="include-config-file.diff" Index: powerpc/conf/GENERIC =================================================================== --- powerpc/conf/GENERIC (revision 200500) +++ powerpc/conf/GENERIC (working copy) @@ -24,6 +24,13 @@ #To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # Platform support Index: sparc64/conf/GENERIC =================================================================== --- sparc64/conf/GENERIC (revision 200500) +++ sparc64/conf/GENERIC (working copy) @@ -30,6 +30,13 @@ # # env "GENERIC.env" +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols # Platforms supported Index: ia64/conf/GENERIC =================================================================== --- ia64/conf/GENERIC (revision 200500) +++ ia64/conf/GENERIC (working copy) @@ -23,6 +23,13 @@ cpu ITANIUM ident GENERIC +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with debug information. options AUDIT # Security event auditing Index: sun4v/conf/GENERIC =================================================================== --- sun4v/conf/GENERIC (revision 200500) +++ sun4v/conf/GENERIC (working copy) @@ -23,6 +23,13 @@ cpu SUN4V ident GENERIC +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols makeoptions NO_MODULES="" # disable modules (aicasm in buildenv) Index: pc98/conf/GENERIC =================================================================== --- pc98/conf/GENERIC (revision 200500) +++ pc98/conf/GENERIC (working copy) @@ -32,6 +32,13 @@ # # env "GENERIC.env" +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_4BSD # 4BSD scheduler Index: i386/conf/GENERIC =================================================================== --- i386/conf/GENERIC (revision 200500) +++ i386/conf/GENERIC (working copy) @@ -32,6 +32,13 @@ # # env "GENERIC.env" +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler Index: amd64/conf/GENERIC =================================================================== --- amd64/conf/GENERIC (revision 200500) +++ amd64/conf/GENERIC (working copy) @@ -30,6 +30,13 @@ # # env "GENERIC.env" +# Store the plain version of this configuration file in the kernel itself. +# To store the entire file, including comments, put this in /etc/src.conf: +# CONFIGARGS= -C +# See config(8) for more details. +# +options INCLUDE_CONFIG_FILE # Include this file in kernel + makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols options SCHED_ULE # ULE scheduler --------------050006080001020009090704-- From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 05:05:52 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52069106566B; Mon, 14 Dec 2009 05:05:52 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id A91EC8FC12; Mon, 14 Dec 2009 05:05:51 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 22so789141eye.9 for ; Sun, 13 Dec 2009 21:05:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=IOPnqCeA4vKbAr3CNmsL2uc0j3ph6BOyev8lEEL7+kI=; b=YPX2A1ryzR15dIj0VTecykfgpsCc3r9G0aVS89J9mzDgtJnJ9mTEEewgW0UsBUDeK+ 9z3H3otfBXuTjD4Axy2pm6+iISx7IQO7K9vt8rtjMsvjFWKruQrUanXCRLNA2RChkoI4 Amna9r16zkfYMsF9S2tK+75l7BFhwK8vtTrpI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=jkngUtAGbpLP1d45EYcIqkARBkYXS8jSSZDkY11sZ8Fb8R9gXpCYA8EWg622IDBKoi x0vfuFxwr9Uby54Vbelmghwz7d3UnIbnbJfqfqafklMBNbJ/BtIl65LYrAeikePwTjrg M4bEvO8ebrkbTYRLA4zayI0tPXr4iwoajS9GY= MIME-Version: 1.0 Received: by 10.216.90.18 with SMTP id d18mr1710107wef.225.1260767150593; Sun, 13 Dec 2009 21:05:50 -0800 (PST) Date: Mon, 14 Dec 2009 00:05:50 -0500 Message-ID: From: "b. f." To: dougb@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@FreeBSD.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 05:05:52 -0000 >1. Add "options ATA_CAM" to my kernel config. AFAICS it's not >necessary to do anything special with ahci, that's included in ata_cam. If you have AHCI-capable hardware and compatible BIOS, then there are now *two* AHCI drivers: [1] ataahci, together with the other ata(4) code, and [2] ahci(4), which doesn't need ata(4). ahci(4) is better, so you should use that if you can. You only need ata(4) if you want to use non-AHCI hardware, or, rarely, AHCI hardware in legacy mode. If you place both in your kernel, ahci(4) should take priority over ata(4) and attach to devices where possible. See the ahci(4) manpage and http://lists.freebsd.org/pipermail/svn-src-all/2009-December/016791.html >2. I already had atapicam in my kernel (which I commented out since >it's included in ata_cam as well), but I'm assuming that at least the >following are needed: >device scbus # SCSI bus (required for SCSI) >device da # Direct Access (disks) >device cd # CD >device pass # Passthrough device (direct SCSI access) Yes. But see above -- you may want to add: device ahci >3. Comment out everything ata-related EXCEPT "device ata". Without >that one the kernel boots but stops cold when it tries to mount the >root file system. Again, see above. You may not actually need ata(4). Even if you do want it, you don't actually need all of ata(4); you can just add the portion you need: device atacore and the chipset-specific parts that correspond to your hardware. Usually, something like: atapci ataahci atanvidia for example. See src/sys/conf/NOTES. You can also have ataisa, atabus, and atacard if you need them; but you should remove device atadisk, ataraid, atapicd, atapifd, atapist, and atapicam if you have ATA_CAM, which uses other means to give equivalent functionality, except in the case of ataraid. For that, ATA_CAM has no replacement; see http://lists.freebsd.org/pipermail/freebsd-current/2009-December/013956.html where mav@ states: "The main regression of the new mode is a lack of ataraid alternative, to support cheap BIOS-based ATA RAIDs. If somebody has time and wish to port that code from inside ata(4) into GEOM module, to make it work over CAM also, I would appreciate that and propose a help, if needed." and http://lists.freebsd.org/pipermail/freebsd-arch/2009-December/009742.html ... >So far so good. :) I am actually kind of curious as to why "device >ata" is needed, but it doesn't seem to be hurting anything. It is needed if you have AHCI hardware, and are operating in AHCI mode, but don't have ahci(4) in your kernel; or if you don't have AHCI hardware, or have AHCI hardware operating in legacy mode, and still want to use ATA devices. ... >Is there something I need to change to make this work, or is NCQ not >available for SATA 1.x devices? Are there any other parameters worth >tweaking? It may be available, but you need to look at the messages regarding your other hardware, not just your disk drive. Do you have an AHCI-capable motherboard and chipset? Are you in AHCI mode? The following kinds of considerations may be relevant as well, for others, if not for your specific case (although these messages were written before the last round of revisions, and mav@ may have made some changes): http://lists.freebsd.org/pipermail/freebsd-stable/2009-December/053381.html http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013477.html http://lists.freebsd.org/pipermail/freebsd-current/2009-November/013639.html Some non-AHCI hardware can do NCQ, but needs drivers that mav@ has not written, and probably won't write. Someone willing to take the time to do so could port some of these drivers from Linux. b. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 05:31:39 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98316106566B; Mon, 14 Dec 2009 05:31:39 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 08BF78FC12; Mon, 14 Dec 2009 05:31:38 +0000 (UTC) Received: by ewy26 with SMTP id 26so3274612ewy.3 for ; Sun, 13 Dec 2009 21:31:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=CKR8mRPkNDu5EP0c1QxYgzQW7CF7uCS3AOWsBXJYluc=; b=nAKkj/amUf29qwva0Qr+EmKPB4OkUgMXOW/NVQwx1RB/TXU0F2pr5IJ0RE2JozVciM 4uf3Opn0NeGr+EE3zs7LTdqsX07d39foL938qP5+cfDWZJ8v8EXW7ebjVlQxeEHqqPEv LBzhsjFvQmpsn2QxmmrTQUtZI7i/z0bq8KTrA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gTbkilCg4RVHkIAp5gCz48hRV+6FwiyK7q5TTuLdyNSTmChBULrnTIBliylXLhjtEe rEa/25CS7wlbOt9yGv9mHhZhzkIJtvpkTqqje9ibO3uFW7jbt0XDz1vZvIQVQfsVDWji x8CET9my7G5kfzZUMLCT7ZfR9XqzP5qM7lmmA= MIME-Version: 1.0 Received: by 10.216.88.201 with SMTP id a51mr1773500wef.154.1260768697858; Sun, 13 Dec 2009 21:31:37 -0800 (PST) In-Reply-To: References: Date: Mon, 14 Dec 2009 00:31:37 -0500 Message-ID: From: "b. f." To: dougb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 05:31:39 -0000 On 12/14/09, b. f. wrote: ... >>So far so good. :) I am actually kind of curious as to why "device >>ata" is needed, but it doesn't seem to be hurting anything. > > It is needed if you have AHCI hardware, and are operating in AHCI > mode, but don't have ahci(4) in your kernel; or if you don't have AHCI > hardware, or have AHCI hardware operating in legacy mode, and still > want to use ATA devices. > I forgot to mention that ata(4) is also superfluous if you have hardware that can use the siis(4) driver, and that driver is in your kernel. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 05:49:33 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0942D106566B for ; Mon, 14 Dec 2009 05:49:33 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9857A8FC08 for ; Mon, 14 Dec 2009 05:49:32 +0000 (UTC) Received: (qmail 7341 invoked by uid 399); 14 Dec 2009 05:49:31 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 05:49:31 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B25D1ED.5060509@FreeBSD.org> Date: Sun, 13 Dec 2009 21:49:33 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: "b. f." References: In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 05:49:33 -0000 Thank you for your very informative reply. :) I left a few things out of my first post to try and keep it brief, so I'll add some more details below. You might seriously consider working something at this level up for the wiki, perhaps working with mav as well. IMO this stuff is never going to get wide testing if we don't make it a whole lot easier for people to do so. b. f. wrote: >> 1. Add "options ATA_CAM" to my kernel config. AFAICS it's not >> necessary to do anything special with ahci, that's included in ata_cam. > > If you have AHCI-capable hardware and compatible BIOS, One thing I did not include in my previous post was that I actually did try adding the ahci device to my kernel config, and didn't get any hits. Per your other message tonight I tried again adding ahci and siis and booting verbose, no joy. This is on a laptop so I'm not really surprised, just disappointed. :) > Again, see above. You may not actually need ata(4). Even if you do > want it, you don't actually need all of ata(4); you can just add the > portion you need: > > device atacore > > and the chipset-specific parts that correspond to your hardware. > Usually, something like: > > atapci > ataahci > atanvidia The only nvidia thing I have is my graphics card, so I'm assuming I could get away with just the first two? Also, how much of an advantage does stripping down the ata stuff give? Is it just a bit of kernel memory? It's working atm so I'm sort of inclined to leave it alone. :) Thanks again, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 05:54:40 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 66F10106566B for ; Mon, 14 Dec 2009 05:54:40 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outV.internet-mail-service.net (outv.internet-mail-service.net [216.240.47.245]) by mx1.freebsd.org (Postfix) with ESMTP id 522818FC08 for ; Mon, 14 Dec 2009 05:54:39 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 293CCB647 for ; Sun, 13 Dec 2009 21:54:42 -0800 (PST) X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id A35982D6011 for ; Sun, 13 Dec 2009 21:54:38 -0800 (PST) Message-ID: <4B25D32B.70306@elischer.org> Date: Sun, 13 Dec 2009 21:54:51 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: profiling kernel modules. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 05:54:40 -0000 It's been a few years since I last profiled the kernel, (probably a decade :-) but it was always a monolithic compiled kernel. Now I want to profile a module, but I'm not finding a lot of specific instructions as to how to do this, For example how to get the loaded addresses for the modules taken into account, or what arguments need to be added to the compile of the module to make sure it has any code stubs that may be needed, etc. if you know anything about these subjects, or related (e.g. usin the performance counters in the kernel/modules I'd love to get your inpout and maybe turn out a doc on how to do this. This would be for -current (9) or 8.0R. Julian. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 05:59:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A0901065672; Mon, 14 Dec 2009 05:59:05 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (mail.fujibayashi.jp [IPv6:2001:470:9954:ffff::2]) by mx1.freebsd.org (Postfix) with ESMTP id C41AA8FC14; Mon, 14 Dec 2009 05:59:04 +0000 (UTC) Received: from [192.168.0.146] (corp.infobox.ru [77.221.128.82]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id 3386A10FBBB; Mon, 14 Dec 2009 14:59:02 +0900 (JST) Message-ID: <4B25D425.4000308@haruhiism.net> Date: Mon, 14 Dec 2009 08:59:01 +0300 From: "K.R." User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091204 Thunderbird/3.0 MIME-Version: 1.0 To: Doug Barton References: <4B241509.8060906@FreeBSD.org> <4B25A28A.1040305@FreeBSD.org> In-Reply-To: <4B25A28A.1040305@FreeBSD.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Ivan Voras Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 05:59:05 -0000 On 14.12.2009 5:27, Doug Barton wrote: > Is there something I need to change to make this work, or is NCQ not > available for SATA 1.x devices? Are there any other parameters worth > tweaking? > From what I know, SATA 1 does not support NCQ. It's a feature of SATA 2. -- Kamigishi Rei KREI-RIPE From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 06:14:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF6CA1065693; Mon, 14 Dec 2009 06:14:07 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 202BE8FC13; Mon, 14 Dec 2009 06:14:06 +0000 (UTC) Received: by ewy26 with SMTP id 26so3292971ewy.3 for ; Sun, 13 Dec 2009 22:14:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=/QtDJ4r2p2+G1VFwqn7Wdn34Bu57D1RKYGhjwrPoBTs=; b=XQ2NPSZ8Lzj3eSC0NZGPqza34XyhU/NqDTN443AORGTn1bcjJGjAyfRV+rXxBtvqjL fk9T8GHp0ArP1z4k3GqdQZuEaTKOGms2nBN+38o3GGo1EPhagCBU0/kBmKpu8DgLdafg nQ/UB+Kx0E1oaC3DvL/kkDE5PUHevQfLSb0mw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=Ef/fuVTUrg76HMJGsOcQ1A4yOHoJNCPBD7ouCWY2/6TQk8Ze8cADA6vBiUGEDg73gb 8lxYPn4Ml0zg0JtYdfvbWHJfJptgoTrbxn7fl8bYsOierfBwMk1lAfohOsf4gRDs6zy9 1CptQtYMcudL1lC/Q8j05g68mNX3o0urC7qow= MIME-Version: 1.0 Received: by 10.216.88.75 with SMTP id z53mr1783168wee.46.1260771245873; Sun, 13 Dec 2009 22:14:05 -0800 (PST) In-Reply-To: <4B25D1ED.5060509@FreeBSD.org> References: <4B25D1ED.5060509@FreeBSD.org> Date: Mon, 14 Dec 2009 01:14:05 -0500 Message-ID: From: "b. f." To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 06:14:07 -0000 On 12/14/09, Doug Barton wrote: > > One thing I did not include in my previous post was that I actually > did try adding the ahci device to my kernel config, and didn't get any > hits. Per your other message tonight I tried again adding ahci and > siis and booting verbose, no joy. This is on a laptop so I'm not > really surprised, just disappointed. :) If you use 'pciconf -lv', is the subclass for your SATA controller listed as either RAID or AHCI? If not, either your hardware doesn't support AHCI, or it is switched into legacy mode (or there is a problem that mav@ would probably like to know about). Try looking in the BIOS setup for a place where you can change the mode. > >> Again, see above. You may not actually need ata(4). Even if you do >> want it, you don't actually need all of ata(4); you can just add the >> portion you need: >> >> device atacore >> >> and the chipset-specific parts that correspond to your hardware. >> Usually, something like: >> >> atapci >> ataahci >> atanvidia > > The only nvidia thing I have is my graphics card, so I'm assuming I > could get away with just the first two? Also, how much of an advantage > does stripping down the ata stuff give? Is it just a bit of kernel > memory? It's working atm so I'm sort of inclined to leave it alone. :) > I was only offering these three as an example -- the modules that you should choose depend on your IDE and ATA controller(s). atapci is the generic default module, ataahci is required for ahci without ahci(4), and then there may be a vendor-specific module as well. Yes, you save a bit of memory, compile time, and space -- but if you don't want to use the modular setup, just use the device ata catchall. b. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 06:26:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D861F106566C for ; Mon, 14 Dec 2009 06:26:11 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3AF8FC1E for ; Mon, 14 Dec 2009 06:25:51 +0000 (UTC) Received: (qmail 31451 invoked by uid 399); 14 Dec 2009 06:25:50 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 06:25:50 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B25DA75.5080807@FreeBSD.org> Date: Sun, 13 Dec 2009 22:25:57 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: "b. f." References: <4B25D1ED.5060509@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 06:26:11 -0000 b. f. wrote: > On 12/14/09, Doug Barton wrote: > >> One thing I did not include in my previous post was that I actually >> did try adding the ahci device to my kernel config, and didn't get any >> hits. Per your other message tonight I tried again adding ahci and >> siis and booting verbose, no joy. This is on a laptop so I'm not >> really surprised, just disappointed. :) > > If you use 'pciconf -lv', is the subclass for your SATA controller > listed as either RAID or AHCI? I should also have mentioned that I looked in my BIOS and didn't see anything relevant. Here is the pciconf output: atapci0@pci0:0:31:2: class=0x010180 card=0x01c21028 chip=0x27c48086 rev=0x01 hdr=0x00 vendor = 'Intel Corporation' device = '82801GBM/GHM (ICH7-M Family) Serial ATA Storage Controller' class = mass storage subclass = ATA Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 07:06:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7352A1065672; Mon, 14 Dec 2009 07:06:54 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id D6A048FC13; Mon, 14 Dec 2009 07:06:53 +0000 (UTC) Received: by ewy26 with SMTP id 26so3317768ewy.3 for ; Sun, 13 Dec 2009 23:06:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=jBL8o7oEWYtwGVFYBDIUFNkN0SoD499vhCI5Iud0V3A=; b=vXKFAbnyhPJW+kBFwZd8CrGVa2nDNZ21SOBKf3AVS1oyz/eOOquXtfSDUdPtrFufo8 mIlhbFzXvOxe6db99DFRc4fDLEDgPZ0PE4nXW7M3Zvf0R8zPBzzqlMJwJYPfWAi5Vflr sGRbphOrgqGI9oYJJE0t+sliucQ0d2mhucOJc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=GbjFatEhhWc6vNH/u9pzff5cTWvQHM3fT5GL7Om25399sd6sOCBe7O3Il4kuosTlBj fZ9+GkNIYtABTqfunpAnxUPhiEdkkEZcdVALlsfW/3p2m0b6nTZ90uhyzRc0pbESfWoB hhPCupuUJyBrJwigN00yRvSzAQ1Pyv1zKIWZY= MIME-Version: 1.0 Received: by 10.216.163.81 with SMTP id z59mr1793368wek.95.1260774412684; Sun, 13 Dec 2009 23:06:52 -0800 (PST) In-Reply-To: <4B25DA75.5080807@FreeBSD.org> References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> Date: Mon, 14 Dec 2009 02:06:52 -0500 Message-ID: From: "b. f." To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 07:06:54 -0000 On 12/14/09, Doug Barton wrote: > b. f. wrote: >> On 12/14/09, Doug Barton wrote: >> >>> One thing I did not include in my previous post was that I actually >>> did try adding the ahci device to my kernel config, and didn't get any >>> hits. Per your other message tonight I tried again adding ahci and >>> siis and booting verbose, no joy. This is on a laptop so I'm not >>> really surprised, just disappointed. :) >> >> If you use 'pciconf -lv', is the subclass for your SATA controller >> listed as either RAID or AHCI? > > I should also have mentioned that I looked in my BIOS and didn't see > anything relevant. Here is the pciconf output: > > atapci0@pci0:0:31:2: class=0x010180 card=0x01c21028 chip=0x27c48086 > rev=0x01 hdr=0x00 > vendor = 'Intel Corporation' > device = '82801GBM/GHM (ICH7-M Family) Serial ATA Storage > Controller' > class = mass storage > subclass = ATA > Hmm. From what little I know, your chipset should support AHCI, so perhaps your motherboard or bios isn't set up right?: p. 39, 44 of the pdf at: http://www.intel.com/design/chipsets/datashts/307013.htm b. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 07:43:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45B891065679 for ; Mon, 14 Dec 2009 07:43:13 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 0CCBD8FC13 for ; Mon, 14 Dec 2009 07:42:45 +0000 (UTC) Received: (qmail 28268 invoked by uid 399); 14 Dec 2009 07:42:44 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 07:42:44 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B25EC42.4090604@FreeBSD.org> Date: Sun, 13 Dec 2009 23:41:54 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: "b. f." References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 07:43:13 -0000 b. f. wrote: > Hmm. From what little I know, your chipset should support AHCI, so > perhaps your motherboard or bios isn't set up right?: > > p. 39, 44 of the pdf at: > > http://www.intel.com/design/chipsets/datashts/307013.htm On page 44 it says, "for some features, hardware support in the SATA device ..." Full output of 'camcontrol identify': pass0: ATA-7 SATA 1.x device pass0: 100.000MB/s transfers (UDMA5, PIO size 8192bytes) protocol ATA/ATAPI-7 SATA 1.x device model Hitachi HTS721010G9SA00 firmware revision MCZOC10H serial number MPCZN7Y0GZSYAL cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 195371568 sectors LBA48 supported 195371568 sectors PIO supported PIO4 DMA supported WDMA2 UDMA5 overlap not supported Feature Support Enable Value Vendor read ahead yes yes write cache yes yes flush cache yes yes Native Command Queuing (NCQ) yes 31/0x1F Tagged Command Queuing (TCQ) no no 31/0x1F SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 16512/0x4080 automatic acoustic management yes yes 254/0xFE 128/0x80 media status notification no no power-up in Standby yes no write-read-verify no no 0/0x0 unload no no free-fall no no Perhaps it does not have the requisite "hardware support" for ahci? -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 07:49:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 129F8106568D for ; Mon, 14 Dec 2009 07:49:22 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.16.84]) by mx1.freebsd.org (Postfix) with ESMTP id BCC288FC1B for ; Mon, 14 Dec 2009 07:49:21 +0000 (UTC) Received: from pampa.cs.huji.ac.il ([132.65.80.32]) by kabab.cs.huji.ac.il with esmtp id 1NK5gF-000A4q-VJ; Mon, 14 Dec 2009 09:49:19 +0200 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Doug Barton In-reply-to: <4B25EC42.4090604@FreeBSD.org> References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> Comments: In-reply-to Doug Barton message dated "Sun, 13 Dec 2009 23:41:54 -0800." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 14 Dec 2009 09:49:19 +0200 From: Daniel Braniss Message-ID: Cc: freebsd-current@freebsd.org, "b. f." Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 07:49:22 -0000 > b. f. wrote: > > Hmm. From what little I know, your chipset should support AHCI, so > > perhaps your motherboard or bios isn't set up right?: > > > > p. 39, 44 of the pdf at: > > > > http://www.intel.com/design/chipsets/datashts/307013.htm > > On page 44 it says, "for some features, hardware support in the SATA > device ..." > > Full output of 'camcontrol identify': > > pass0: ATA-7 SATA 1.x device > pass0: 100.000MB/s transfers (UDMA5, PIO size 8192bytes) > > protocol ATA/ATAPI-7 SATA 1.x > device model Hitachi HTS721010G9SA00 > firmware revision MCZOC10H > serial number MPCZN7Y0GZSYAL > cylinders 16383 > heads 16 > sectors/track 63 > sector size logical 512, physical 512, offset 0 > LBA supported 195371568 sectors > LBA48 supported 195371568 sectors > PIO supported PIO4 > DMA supported WDMA2 UDMA5 > overlap not supported > > Feature Support Enable Value Vendor > read ahead yes yes > write cache yes yes > flush cache yes yes > Native Command Queuing (NCQ) yes 31/0x1F > Tagged Command Queuing (TCQ) no no 31/0x1F > SMART yes yes > microcode download yes yes > security yes no > power management yes yes > advanced power management yes yes 16512/0x4080 > automatic acoustic management yes yes 254/0xFE 128/0x80 > media status notification no no > power-up in Standby yes no > write-read-verify no no 0/0x0 > unload no no > free-fall no no > > > Perhaps it does not have the requisite "hardware support" for ahci? probably, but have you checked the BIOS setup? my 5c. danny From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 07:50:05 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 533461065679 for ; Mon, 14 Dec 2009 07:50:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 1C8848FC0A for ; Mon, 14 Dec 2009 07:50:04 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id C6D90730A1; Mon, 14 Dec 2009 08:57:25 +0100 (CET) Date: Mon, 14 Dec 2009 08:57:25 +0100 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20091214075725.GA80173@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: need clarifications on net/radix.c usage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 07:50:05 -0000 Hi, i am revising the code in net/radix.c and there are a few things that are not completely clear to me and I would like to understand and possibly fix. I know that this code has been untouched in 15 years so it probably reflects old requirements or design ideas that have changed since then. Initial list of things: - struct radix_node_head has a number of fields that are never used (rnh_addpkt and friends, rnh_addrsize, rnh_pktsize) Unless there are objections I'd like to remove the unused fields. - there are some static variables in radix.c (max_keylen, mask_rnhead, the freelist, the allzero and allone masks, 'last_zeroed' in a function) which would probably deserve becoming members of radix_node_head, last not least for correctness of operation -- some of those fields are read-write, but there are now multiple instances of radix_node_head running under different locks. Again, if there are no objections, I'd like to move those variables into radix_node_head. cheers luigi From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 08:13:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88BC91065693; Mon, 14 Dec 2009 08:13:13 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.27]) by mx1.freebsd.org (Postfix) with ESMTP id E9F0D8FC12; Mon, 14 Dec 2009 08:13:12 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 22so810690eye.9 for ; Mon, 14 Dec 2009 00:13:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=mN8dCD0HMWJgZUpufWxeSpMRULK3UB6C8Ax1LiA8oGk=; b=Y5m3JpILhEBRCJNA5ilaIBmoyGfd0UUM6viXVXmaQNHFXLDWWJugJmahc9y8c9uuwL 8fLEtJb9V8US2/5gR7FN3gixzcr30TwJ6eCmaoWPfwimxGOHKoElv6rrKOvrRnMDJyTr w4xhOjuN95QVmwixZJe0oyNlZaop9HVyzX9uY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=a9j+UwRhlxuSLYABajLSUuVirhrIzwCq3a3vj9Ns3yT1fCFTjDu17FsqPWxhLQVKKa rvVy4TcBJKpOUaSxwMDFqAQUNQvldbCxNuDYEwNf0HndLt+QydapOmmG/cubcshIY30L BXKxsJ9nNKz6DZcTth/M3ftjq2gx0sGezakkU= MIME-Version: 1.0 Received: by 10.216.87.75 with SMTP id x53mr1837347wee.13.1260778391702; Mon, 14 Dec 2009 00:13:11 -0800 (PST) In-Reply-To: <4B25EC42.4090604@FreeBSD.org> References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> Date: Mon, 14 Dec 2009 03:13:11 -0500 Message-ID: From: "b. f." To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 08:13:13 -0000 On 12/14/09, Doug Barton wrote: > b. f. wrote: >> Hmm. From what little I know, your chipset should support AHCI, so >> perhaps your motherboard or bios isn't set up right?: >> >> p. 39, 44 of the pdf at: >> >> http://www.intel.com/design/chipsets/datashts/307013.htm > > On page 44 it says, "for some features, hardware support in the SATA > device ..." > I believe what they meant in the Intel document was that in order to use certain features supported by AHCI, such as NCQ, the disk drive must also support them. Your disk drive seems to support NCQ. > pass0: ATA-7 SATA 1.x device > pass0: 100.000MB/s transfers (UDMA5, PIO size 8192bytes) ... > Perhaps it does not have the requisite "hardware support" for ahci? This is the disk drive. AHCI is for host controllers: http://www.intel.com/technology/serialata/ahci.htm So this does not seem to explain why ahci(4) fails to attach to your SATA controller. I suspect that your bios or motherboard fails to use AHCI mode. Maybe there is a later bios revision, or some jumper settings on the board that will allow it to be enabled. You may have to talk to the manufacturer. Of course, there is a small chance that there is a problem with our drivers. Have you tried a live CD of a Linux distro, to see AHCI works with another OS? b. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 08:51:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8081106566B for ; Mon, 14 Dec 2009 08:51:54 +0000 (UTC) (envelope-from olivier.freebsd@free.fr) Received: from smtpfb2-g21.free.fr (smtpfb2-g21.free.fr [212.27.42.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6092B8FC17 for ; Mon, 14 Dec 2009 08:51:52 +0000 (UTC) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [212.27.42.6]) by smtpfb2-g21.free.fr (Postfix) with ESMTP id 7755ACA8DBD for ; Mon, 14 Dec 2009 09:35:52 +0100 (CET) Received: from smtp6-g21.free.fr (localhost [127.0.0.1]) by smtp6-g21.free.fr (Postfix) with ESMTP id 000C8E081AE for ; Mon, 14 Dec 2009 09:35:46 +0100 (CET) Received: from lon92-4-82-226-188-149.fbx.proxad.net (lon92-4-82-226-188-149.fbx.proxad.net [82.226.188.149]) by smtp6-g21.free.fr (Postfix) with ESMTP id D8FEEE081A0 for ; Mon, 14 Dec 2009 09:35:43 +0100 (CET) From: Olivier Certner To: freebsd-current@freebsd.org Date: Mon, 14 Dec 2009 09:35:30 +0100 User-Agent: KMail/1.9.10 References: <4B241509.8060906@FreeBSD.org> <0866f178e6604b920f9464ec6551db28.squirrel@cygnus.homeunix.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200912140935.30689.olivier.freebsd@free.fr> Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 08:51:54 -0000 > All variants: ufs, ufsid, glabel are handled the same - the differences > are cosmetic and a matter of user's preferences. All the variants may be handled the same, but I found that I can put a '_' in a pure glabel name (using glabel on-storage format, one sector at the provider's end, I guess) whereas I can't in a ufs-provided label (using 7.2R). Olivier From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:04:03 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9FD1106568B; Mon, 14 Dec 2009 11:04:03 +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 8AF0F8FC34; Mon, 14 Dec 2009 11:04:03 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 762C66D41C; Mon, 14 Dec 2009 11:04:01 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 82334844F3; Mon, 14 Dec 2009 12:04:00 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "M. Warner Losh" References: <20091210144141.GB834@mech-cluster241.men.bris.ac.uk> <20091210095122.a164bf95.wmoran@potentialtech.com> <20091212.163352.850602504923947435.imp@bsdimp.com> Date: Mon, 14 Dec 2009 12:04:00 +0100 In-Reply-To: <20091212.163352.850602504923947435.imp@bsdimp.com> (M. Warner Losh's message of "Sat, 12 Dec 2009 16:33:52 -0700 (MST)") Message-ID: <868wd5olzz.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@FreeBSD.org, mexas@bristol.ac.uk, wmoran@potentialtech.com, freebsd-questions@FreeBSD.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:04:03 -0000 "M. Warner Losh" writes: > Are you sure that OpenBSD has a better record? They have a record of measuring others by a different yardstick... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:07:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17BC110656A3; Mon, 14 Dec 2009 11:07:24 +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 CCCAA8FC0C; Mon, 14 Dec 2009 11:07:23 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 0A55E6D453; Mon, 14 Dec 2009 11:07:23 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id DC3D7844F3; Mon, 14 Dec 2009 12:07:22 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Kevin Oberman" References: <20091211232356.309C21CC09@ptavv.es.net> Date: Mon, 14 Dec 2009 12:07:22 +0100 In-Reply-To: <20091211232356.309C21CC09@ptavv.es.net> (Kevin Oberman's message of "Fri, 11 Dec 2009 15:23:56 -0800") Message-ID: <864ontolud.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Polytropon , Bill Moran , Matthew Seaman , "Sam Fourman Jr." , Anton Shterenlikht , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:07:24 -0000 "Kevin Oberman" writes: > I'm sure that there are systems happily running MSDOS, but I bet not too > many are networked. That's a bet you're likely to lose - most of them are POS terminals, industrial control applications etc. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:09:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DDE3106568D; Mon, 14 Dec 2009 11:09:40 +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 3E2BD8FC1B; Mon, 14 Dec 2009 11:09:40 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 734786D456; Mon, 14 Dec 2009 11:09:39 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 5227F844F3; Mon, 14 Dec 2009 12:09:39 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Doug Barton References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <4B25B0CA.1070006@FreeBSD.org> Date: Mon, 14 Dec 2009 12:09:39 +0100 In-Reply-To: <4B25B0CA.1070006@FreeBSD.org> (Doug Barton's message of "Sun, 13 Dec 2009 19:28:10 -0800") Message-ID: <86zl5ln764.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alex Keda , freebsd-current , Robert Watson Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:09:40 -0000 Doug Barton writes: > Ok, here is the proposed patch. [...] I'd put it in DEFAULTS instead... DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:20:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9970910656A7; Mon, 14 Dec 2009 11:20:22 +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 5ACE38FC25; Mon, 14 Dec 2009 11:20:22 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 555BB6D450; Mon, 14 Dec 2009 11:20:21 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 32C9A844F3; Mon, 14 Dec 2009 12:20:21 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "K.R." References: <4B241509.8060906@FreeBSD.org> <4B25A28A.1040305@FreeBSD.org> <4B25D425.4000308@haruhiism.net> Date: Mon, 14 Dec 2009 12:20:21 +0100 In-Reply-To: <4B25D425.4000308@haruhiism.net> (K. R.'s message of "Mon, 14 Dec 2009 08:59:01 +0300") Message-ID: <86pr6hn6oa.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Doug Barton , Ivan Voras , freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:20:22 -0000 "K.R." writes: > From what I know, SATA 1 does not support NCQ. It's a feature of SATA > 2. a) There is no such thing as SATA 1 or 2; there is only SATA, although marketroids sometimes incorrectly refer to drives that support 3 Gbps transfer speed as SATA II drives. b) SATA has supported NCQ from the very beginning. In fact, command queueing already existed in PATA at the time SATA was finalized. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:27:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0CE7106566C; Mon, 14 Dec 2009 11:27:59 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 18DAD8FC08; Mon, 14 Dec 2009 11:27:58 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so887079fgg.13 for ; Mon, 14 Dec 2009 03:27:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=MqPDx+aCt7zkIcrnrFTHwRoPvseclwymxdF1r+c0W4A=; b=hhK1ReA58g0QL/QB7GntnH67QRXV+wGYDG0vY8ObMNydIQwjhc7IBvu1POqlZXoLka SjkjZ4+YPxXqoH6zbZjprH2OJI1ieuvyNz7+RLvutMLo23gyqYjggT6CrR7Ehf2sKC67 SPIsvVEUsP3/kATgfwBz5Fj3QZuHfTIVlJXrI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=LEH0WME9va30YuyHmHi1azOcWF+DTPhFEKViD9ar5iKctQTZDsjDVZ/TrlwfGMpN+i 6MbxpsMqYhjU808h8X/VgCt1QHrrvirnQ4H/Eco0nnaxwpQVyebxLeDbLpjsCwn5kUv3 c5tSns3vrz7SOgZJqv74LbUxLmm+/pbRIc9X4= Received: by 10.86.6.24 with SMTP id 24mr1976623fgf.67.1260790076937; Mon, 14 Dec 2009 03:27:56 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 16sm1495332fxm.0.2009.12.14.03.27.55 (version=SSLv3 cipher=RC4-MD5); Mon, 14 Dec 2009 03:27:55 -0800 (PST) Sender: Alexander Motin Message-ID: <4B262119.6090904@FreeBSD.org> Date: Mon, 14 Dec 2009 13:27:21 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Ivan Voras References: <1258575782.00184876.1258562404@10.7.7.3> <1258579386.00184908.1258567802@10.7.7.3> <1258590193.00184983.1258579804@10.7.7.3> In-Reply-To: <1258590193.00184983.1258579804@10.7.7.3> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:27:59 -0000 Ivan Voras wrote: > 2009/11/18 Alexander Motin : >> Ivan Voras wrote: > >>> I know next to nothing about AHCI and drivers so this might be obviously >>> wrong but wouldn't a quick (i.e. MFC-able) obvious temporary fix be to say >>> >>> numslots = min(get_minimum_tags_of_all_drives(), ...) >>> ? >> Problem is that SIM driver has no idea about devices capabilities, and >> also doesn't have method to resize queue after attach. In SCSI case, >> tags are random and only simultaneous number of request is limited, and >> this is handled fine by CAM. SATA NCQ is more restrictive, allowing to >> use only tags 0..(N-1). I am planning to make XPT inform SIM about >> supported tags for each device, to allow SIM to use that information >> while scheduling requests. I didn't do it yet, just because most of >> devices able to handle all 32 tags possible on SATA. This Intel SSD is >> one of rare exceptions. > > Ok, (still thinking about something that could be MFC-able in an > emergency), how about adding a loader tunable integer instead of "32"? Just for note, it is already fixed and merged. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 11:45:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 077AE106566C; Mon, 14 Dec 2009 11:45:48 +0000 (UTC) (envelope-from ivoras@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.26]) by mx1.freebsd.org (Postfix) with ESMTP id 682E88FC15; Mon, 14 Dec 2009 11:45:47 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id d26so707852eyd.3 for ; Mon, 14 Dec 2009 03:45:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:from:date:x-google-sender-auth:message-id:subject:to:cc :content-type; bh=IutKSUz3ngZpruoPyDgoWdjqdlvopoPIS+rVjb5vpZ4=; b=Z0n2dGKf4P/4lLuYhpfP4EcxxCh8Ebl8p/Rslvx1E0w1i7yiYYLZZyZZziJtxTMzWR LpCk6uV9OVQVdxRlERGqhAqlnj2+1+U7OUBvk3gEkMakeYRzCdnd/3wrh9x/466/o9mc /s1RAv3lJ0G6ejJYnaxjEcVzBzS/Py6pmyGIU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; b=f+flCVmtoqf9CHaY0i30rAx60sOwPJDpU7yv7xB9fn5CeNpULtk8uraguwJK7u5Yae rZ+2Jw1Mct9WafIhB9w62m518n1/5QYO92ZyzQR42JmnSzF8+05AW9sicQxWZCoUqUoz wjwhcPy+mBo9dVxqs1WxXDi4uIU6Ve5UmZDwk= MIME-Version: 1.0 Sender: ivoras@gmail.com Received: by 10.216.163.81 with SMTP id z59mr1901887wek.95.1260791146213; Mon, 14 Dec 2009 03:45:46 -0800 (PST) In-Reply-To: <4B262119.6090904@FreeBSD.org> References: <1258575782.00184876.1258562404@10.7.7.3> <1258579386.00184908.1258567802@10.7.7.3> <1258590193.00184983.1258579804@10.7.7.3> <4B262119.6090904@FreeBSD.org> From: Ivan Voras Date: Mon, 14 Dec 2009 12:45:26 +0100 X-Google-Sender-Auth: 3842a3e6b93b9359 Message-ID: <9bbcef730912140345u6dada7f4g3b445b18c531ed63@mail.gmail.com> To: Alexander Motin Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD-Current Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 11:45:48 -0000 2009/12/14 Alexander Motin : > Ivan Voras wrote: >> 2009/11/18 Alexander Motin : >>> Ivan Voras wrote: >> >>>> I know next to nothing about AHCI and drivers so this might be obviously >>>> wrong but wouldn't a quick (i.e. MFC-able) obvious temporary fix be to say >>>> >>>> numslots = min(get_minimum_tags_of_all_drives(), ...) >>>> ? >>> Problem is that SIM driver has no idea about devices capabilities, and >>> also doesn't have method to resize queue after attach. In SCSI case, >>> tags are random and only simultaneous number of request is limited, and >>> this is handled fine by CAM. SATA NCQ is more restrictive, allowing to >>> use only tags 0..(N-1). I am planning to make XPT inform SIM about >>> supported tags for each device, to allow SIM to use that information >>> while scheduling requests. I didn't do it yet, just because most of >>> devices able to handle all 32 tags possible on SATA. This Intel SSD is >>> one of rare exceptions. >> >> Ok, (still thinking about something that could be MFC-able in an >> emergency), how about adding a loader tunable integer instead of "32"? > > Just for note, it is already fixed and merged. Thank you! From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 12:13:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 72E1F10656AD for ; Mon, 14 Dec 2009 12:13:04 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by mx1.freebsd.org (Postfix) with ESMTP id 0195F8FC1C for ; Mon, 14 Dec 2009 12:13:03 +0000 (UTC) Received: by mail-fx0-f228.google.com with SMTP id 28so1260476fxm.13 for ; Mon, 14 Dec 2009 04:13:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=b8DRS1TYlvj/pDDbFdb2VKG1PnUZ8gaiWsbvDXTjiT8=; b=LiilbwDLhVRBUDputrpTd5ybhqPUoNIs5cE766C8BjTxt3njmRbN25vC/tGRqyYiZi P9fBVj5vmBgWbJKJYWKYV1/5vtgvcSlV7bHBJo+F+VuzaVFBny3owmbzP1ffqXbp8DXW GQuEJt8WZYGsIpjZTi8K8jzXP3ZT0WooEDn14= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=nblma4u3AqSgGoaoIA+I4LhXjria2zZMtndOTIo71p5JN/e7ola/OqLakM/YTEXUZQ hfL7N6p80UxeCgDuzNy7cUu+/XEaWwEstj4SMZmxYRz/5hVsNwZZ0k9i4bwhCld8XQ8t rAflYPK8Ygi09TYOoEHtuLGs8I3zBb2ZjqOlA= Received: by 10.223.4.144 with SMTP id 16mr1280089far.36.1260792783656; Mon, 14 Dec 2009 04:13:03 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 14sm1511432fxm.7.2009.12.14.04.13.02 (version=SSLv3 cipher=RC4-MD5); Mon, 14 Dec 2009 04:13:02 -0800 (PST) Sender: Alexander Motin Message-ID: <4B262BAC.9040808@FreeBSD.org> Date: Mon, 14 Dec 2009 14:12:28 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20090901) MIME-Version: 1.0 To: Tom Uffner References: <4B1671EE.1010301@FreeBSD.org> <4B25AE1A.80206@uffner.com> In-Reply-To: <4B25AE1A.80206@uffner.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 12:13:04 -0000 Tom Uffner wrote: > this change breaks my Promise SATA card Are you sure that it was this change? > atapci0: port > 0xdc00-0xdc7f,0xd800-0xd8ff mem > 0xfeaff000-0xfeafffff,0xfeac0000-0xfeadffff irq 23 at device 11.0 on pci2 > > kernels from after the commit on 12/6 are unable to mount my drives. > i get (from memory, since i can't even get to single user mode) > WARNING - READ_DMA UDMA ICRC error > followed by lots of SETFEATURE foo errors then a READ_DMA timeout > followed by a bus reset and the cycle repeats... > > before this commit it worked fine. How long ago? > this is in the legacy mode. i am building a kernel with "options ATA_CAM" > now OK. Tell me if there any difference. Send me please full _verbose_ dmesg with original kernel and if possible with new. If you can't get full with new, enable verbose messages and make screenshots of drives detection and first errors. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 12:13:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 941701065670; Mon, 14 Dec 2009 12:13:45 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with ESMTP id 48FAA8FC14; Mon, 14 Dec 2009 12:13:44 +0000 (UTC) Received: from [192.168.4.11] (unknown [192.168.4.11]) (Authenticated sender: svein) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id 9DE4774; Mon, 14 Dec 2009 13:13:44 +0100 (CET) Message-ID: <4B262BF9.1010500@stillbilde.net> Date: Mon, 14 Dec 2009 13:13:45 +0100 From: "Svein Skogen (Listmail Account)" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> In-Reply-To: <864ontolud.fsf@ds4.des.no> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cc: Anton Shterenlikht , Bill Moran , Matthew Seaman , freebsd-current@freebsd.org, "Sam Fourman Jr." , Polytropon , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 12:13:45 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dag-Erling Smørgrav wrote: > "Kevin Oberman" writes: >> I'm sure that there are systems happily running MSDOS, but I bet not too >> many are networked. > > That's a bet you're likely to lose - most of them are POS terminals, > industrial control applications etc. Add to that the lot of them that are running IPX/SPX protocol... ;) //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg Østli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksmK/gACgkQODUnwSLUlKSTbACgk63bpEw587FvI+sPpiC3BORP GdoAnjT/o90mt0aNubLMsim9RfjIrtvR =Rq2S -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 12:49:03 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BABBF1065676 for ; Mon, 14 Dec 2009 12:49:03 +0000 (UTC) (envelope-from sson@FreeBSD.org) Received: from ns1.son.org (son.org [65.48.68.179]) by mx1.freebsd.org (Postfix) with ESMTP id 82AC68FC23 for ; Mon, 14 Dec 2009 12:49:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by ns1.son.org (Postfix) with ESMTP id 9314D197F30; Mon, 14 Dec 2009 06:33:52 -0600 (CST) X-Virus-Scanned: amavisd-new at son.org Received: from ns1.son.org ([127.0.0.1]) by localhost (ns1.dev-random.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NO8BP+mc2Oko; Mon, 14 Dec 2009 06:33:47 -0600 (CST) Received: from nextstepng.son.org (unknown [99.157.26.76]) by ns1.son.org (Postfix) with ESMTP id 35F73197F29; Mon, 14 Dec 2009 06:33:47 -0600 (CST) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Stacey Son In-Reply-To: <4B25D32B.70306@elischer.org> Date: Mon, 14 Dec 2009 06:33:45 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <3498D1C3-3330-463E-9D9E-2A487185F46C@FreeBSD.org> References: <4B25D32B.70306@elischer.org> To: Julian Elischer X-Mailer: Apple Mail (2.1077) Cc: FreeBSD Current Subject: Re: profiling kernel modules. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 12:49:03 -0000 On Dec 13, 2009, at 11:54 PM, Julian Elischer wrote: > It's been a few years since I last profiled the kernel, (probably a = decade :-) but it was always a monolithic compiled kernel. Now I want = to profile a module, but I'm not finding a lot of specific instructions = as to how to do this, For example how to get the loaded addresses for = the modules taken into account, or what arguments need to be added to = the compile of the module to make sure it has any code stubs that may be = needed, etc. >=20 > if you know anything about these subjects, or related (e.g. usin > the performance counters in the kernel/modules I'd love to get your = inpout and maybe turn out a doc on how to do this. >=20 > This would be for -current (9) or 8.0R. Hi Julian: You might want to take a look at using the 'lockstat' command, in = particular its '-I' option (see = http://docs.sun.com/app/docs/doc/816-5212/6mbcdgk0m?a=3Dview or = lockstat(1)). lockstat depends on the dtrace and the pseudo driver = ksyms bits in the kernel. The ksyms driver provides lockstat with a = complete symbol table (including all the symbols of any loaded kernel = modules). See http://people.freebsd.org/~sson/ksyms/ksyms.4.txt or = ksyms(4). See http://wiki.freebsd.org/DTrace for adding the dtrace bits and add = 'device ksyms' to your kernel config file. You will need to load both = the 'dtraceall' and 'ksyms' kernel modules before you can successfully = use the 'lockstat' command. Best Regards, -stacey. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 13:03:25 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB0411065676; Mon, 14 Dec 2009 13:03:25 +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 79C6A8FC13; Mon, 14 Dec 2009 13:03:25 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 26CD76D41C; Mon, 14 Dec 2009 13:03:24 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id E7CC3844D2; Mon, 14 Dec 2009 14:03:23 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Svein Skogen" References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> Date: Mon, 14 Dec 2009 14:03:23 +0100 In-Reply-To: <4B262BF9.1010500@stillbilde.net> (Svein Skogen's message of "Mon, 14 Dec 2009 13:13:45 +0100") Message-ID: <86ljh5n1wk.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Anton Shterenlikht , Bill Moran , Matthew Seaman , freebsd-current@freebsd.org, "Sam Fourman Jr." , Polytropon , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 13:03:25 -0000 "Svein Skogen" writes: > Dag-Erling Sm=C3=B8rgrav wrote: > > "Kevin Oberman" writes: > > > I'm sure that there are systems happily running MSDOS, but I bet > > > not too many are networked. > > That's a bet you're likely to lose - most of them are POS terminals, > > industrial control applications etc. > Add to that the lot of them that are running IPX/SPX protocol... ;) Damn you, I was this >< close to successfully repressing that memory! DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 14:05:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41D121065679 for ; Mon, 14 Dec 2009 14:05:40 +0000 (UTC) (envelope-from sagara@tomahawk.com.sg) Received: from us1.tomahawkonline.net (us1.tomahawkonline.net [66.98.178.56]) by mx1.freebsd.org (Postfix) with SMTP id E454A8FC27 for ; Mon, 14 Dec 2009 14:05:39 +0000 (UTC) Received: (qmail 17831 invoked from network); 14 Dec 2009 10:41:20 -0000 Received: from 116.15.193.204 (HELO ?192.168.1.64?) (sagara@tomahawk.com.sg@116.15.193.204) by us1.tomahawkonline.net with ESMTPSA (DHE-RSA-AES256-SHA encrypted, authenticated); 14 Dec 2009 10:41:20 -0000 Message-ID: <4B2645BB.2090004@tomahawk.com.sg> Date: Mon, 14 Dec 2009 22:03:39 +0800 From: Sagara Wijetunga User-Agent: Thunderbird 2.0.0.23 (X11/20091107) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-questions@freebsd.org Subject: Tomahawk Desktop 2.0 Beta1 Released X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 14:05:40 -0000 Hi FreeBSD community We are happy to announce the release of Tomahawk Desktop 2.0 Beta1. The Tomahawk Desktop is based on FreeBSD 7.2 sources. The objective of the release is, that we could not get the KDE (ver. 4.3.3) up. When try to run the KDE, the greeter crashes. Appreciate if the FreeBSD developers could help us to diagnose this issue. Tomahawk Desktop download: http://www.tomahawkcomputers.com/download.html Kind regards Sagara Wijetunga From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 15:15:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C514910656C0 for ; Mon, 14 Dec 2009 15:15:58 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop2.sarenet.es (proxypop2.sarenet.es [194.30.0.95]) by mx1.freebsd.org (Postfix) with ESMTP id 692BC8FC21 for ; Mon, 14 Dec 2009 15:15:58 +0000 (UTC) Received: from [172.16.1.204] (izaro.sarenet.es [192.148.167.11]) by proxypop2.sarenet.es (Postfix) with ESMTP id 80C2373625; Mon, 14 Dec 2009 16:15:51 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=iso-8859-1 From: Borja Marcos In-Reply-To: <86ljh5n1wk.fsf@ds4.des.no> Date: Mon, 14 Dec 2009 16:15:51 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> To: =?iso-8859-1?Q?Dag-Erling_Sm=F8rgrav?= X-Mailer: Apple Mail (2.1077) Cc: freebsd-current@freebsd.org, Polytropon , Bill Moran , Matthew Seaman , "Sam Fourman Jr." , Svein Skogen , Anton Shterenlikht , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 15:15:58 -0000 On Dec 14, 2009, at 2:03 PM, Dag-Erling Sm=F8rgrav wrote: > "Svein Skogen" writes: >> Dag-Erling Sm=F8rgrav wrote: >>> "Kevin Oberman" writes: >>>> I'm sure that there are systems happily running MSDOS, but I bet >>>> not too many are networked. >>> That's a bet you're likely to lose - most of them are POS terminals, >>> industrial control applications etc. >> Add to that the lot of them that are running IPX/SPX protocol... ;) >=20 > Damn you, I was this >< close to successfully repressing that memory! I was avoiding to jump into this, but... Maybe this hilarious proposal = will cure your pain, dude. http://ietfdocs.potaroo.net/rfc/rfc1791.txt I remember that around the early 90's I read one of those peecee = magazine authors (maybe Jerry Pournelle) asking the IETF to, please, = drop that TCP/IP thingy and instead choose a standard, widely used = protocol for the Internet: IPX. Let me touch more bad neurons for you: X.400 :) Borja. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 15:41:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BB31D106566B; Mon, 14 Dec 2009 15:41:51 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 758398FC20; Mon, 14 Dec 2009 15:41:51 +0000 (UTC) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKD3S-0001M2-AF; Mon, 14 Dec 2009 15:41:50 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKD3R-0007Cv-BU; Mon, 14 Dec 2009 15:41:45 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBEFfj5g086979; Mon, 14 Dec 2009 15:41:45 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBEFfiS4086978; Mon, 14 Dec 2009 15:41:45 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Mon, 14 Dec 2009 15:41:44 +0000 From: Anton Shterenlikht To: Thomas-Martin Seck Message-ID: <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> References: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: Johan Hendriks , freebsd-ports@freebsd.org, freebsd-current@freebsd.org Subject: Re: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 15:41:51 -0000 On Sun, Dec 13, 2009 at 04:27:12PM -0000, Thomas-Martin Seck wrote: > * Johan Hendriks : > > (Squid breakage in the YP/NIS helper) > > > A long shot > > Could it be that you have set the following in your src.conf > > WITHOUT_NIS= yes > > WITHOUT_RCMDS= yes > > WITHOUT_RCS= yes > > > > If i set those i get a similar error with squid (on i386 and amd64 ) > > This is possible; the Squid 2.7 port still relies on WITHOUT_NIS/NO_NIS > being set in make.conf. Due to the make.conf/src.conf split this does no > longer work. I have added an OPTION to turn off NIS support to the squid > 3.x ports and will merge this change into the Squid 2.7 port along with > other changes soon. In the meantime you can work around this if you > build www/squid with "make -DWITHOUT_NIS" or by adding WITHOUT_NIS=yes > to /etc/make.conf. > > The same applies to systems built/installed without Heimdal support. > Sorry for the breakage. yes, I had WITHOUT_NIS= yes in /etc/src.conf, but not the other two options. I have now rebuilt the system without this option, but I still get the NIS build error. If I build with "make -DWITHOUT_NIS", then I get this error: Making all in negotiate_auth Making all in squid_kerb_auth cc -DHAVE_CONFIG_H -I. -I../../../include -DHEIMDAL -I./spnegohelp -I. -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT squid_kerb_auth.o -MD -MP -MF .deps/squid_kerb_auth.Tpo -c -o squid_kerb_auth.o squid_kerb_auth.c squid_kerb_auth.c:70:18: error: krb5.h: No such file or directory *** Error code 1 Stop in /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/negotiate_auth/squid_kerb_auth. *** Error code 1 does it mean I also need to build kerberos? I've WITHOUT_KERBEROS=yes in /etc/src.conf many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 15:47:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F708106566C; Mon, 14 Dec 2009 15:47:01 +0000 (UTC) (envelope-from wkoszek@freebsd.czest.pl) Received: from freebsd.czest.pl (l95h.icis.pcz.pl [212.87.224.105]) by mx1.freebsd.org (Postfix) with ESMTP id 09C148FC0C; Mon, 14 Dec 2009 15:47:00 +0000 (UTC) Received: from freebsd.czest.pl (l95h.icis.pcz.pl [212.87.224.105]) by freebsd.czest.pl (8.14.2/8.14.2) with ESMTP id nBEFwsO3009809; Mon, 14 Dec 2009 16:58:54 +0100 (CET) (envelope-from wkoszek@freebsd.czest.pl) Received: (from wkoszek@localhost) by freebsd.czest.pl (8.14.2/8.14.2/Submit) id nBEFwrTf009808; Mon, 14 Dec 2009 16:58:53 +0100 (CET) (envelope-from wkoszek) Date: Mon, 14 Dec 2009 16:58:53 +0100 From: "Wojciech A. Koszek" To: Doug Barton Message-ID: <20091214155853.GC78318@FreeBSD.org> Mail-Followup-To: Doug Barton , Robert Watson , Alex Keda , freebsd-current References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <4B25B0CA.1070006@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <4B25B0CA.1070006@FreeBSD.org> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-3.0 (freebsd.czest.pl [212.87.224.105]); Mon, 14 Dec 2009 16:58:54 +0100 (CET) Cc: Alex Keda , freebsd-current , Robert Watson Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 15:47:01 -0000 On Sun, Dec 13, 2009 at 07:28:10PM -0800, Doug Barton wrote: > Robert Watson wrote: > > > > On Sat, 12 Dec 2009, Doug Barton wrote: > > > >> Alex Keda wrote: > >>> For those who have recently engaged in FreeBSD, and inexperienced > >>> managers who have inherited a server "by inheritance" is often the > >>> question arises - where to find the configuration file in which to > >>> compile your kernel? (Of course, a file by that time there =)) > >> > >> I actually thought that was already done, but I see now that it's not. > >> I would like to see this as well, any objections? > > > > I'd say go for it. > > Ok, here is the proposed patch. I'll commit it tomorrow unless someone > objects. It looks fine for the first glance. I would also reconsider putting it in DEFAULTS, as des@ pointed out. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/~wkoszek/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 15:53:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C425C10656B8; Mon, 14 Dec 2009 15:53:08 +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 7F9428FC19; Mon, 14 Dec 2009 15:53:08 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 7C9B56D41B; Mon, 14 Dec 2009 15:53:07 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 536A5844F3; Mon, 14 Dec 2009 16:53:07 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Borja Marcos References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> Date: Mon, 14 Dec 2009 16:53:07 +0100 In-Reply-To: (Borja Marcos's message of "Mon, 14 Dec 2009 16:15:51 +0100") Message-ID: <86d42hmu1o.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Polytropon , Bill Moran , Matthew Seaman , "Sam Fourman Jr." , Svein Skogen , Anton Shterenlikht , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 15:53:08 -0000 Borja Marcos writes: > http://ietfdocs.potaroo.net/rfc/rfc1791.txt Priceless! > I remember that around the early 90's I read one of those peecee > magazine authors (maybe Jerry Pournelle) asking the IETF to, please, > drop that TCP/IP thingy and instead choose a standard, widely used > protocol for the Internet: IPX. Umm, is IPX even routable? Note that we still have IPX/SPX and NCP support in the kernel... options IPX #IPX/SPX communications protocols options NCP #NetWare Core protocol DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 16:01:27 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB2D5106566B for ; Mon, 14 Dec 2009 16:01:27 +0000 (UTC) (envelope-from Johan@double-l.nl) Received: from smtp-vbr17.xs4all.nl (smtp-vbr17.xs4all.nl [194.109.24.37]) by mx1.freebsd.org (Postfix) with ESMTP id 69B198FC21 for ; Mon, 14 Dec 2009 16:01:26 +0000 (UTC) Received: from w2003s01.double-l.local (double-l.xs4all.nl [80.126.205.144]) by smtp-vbr17.xs4all.nl (8.13.8/8.13.8) with ESMTP id nBEG1K5B065350; Mon, 14 Dec 2009 17:01:22 +0100 (CET) (envelope-from Johan@double-l.nl) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 14 Dec 2009 17:01:18 +0100 Message-ID: <57200BF94E69E54880C9BB1AF714BBCBA57377@w2003s01.double-l.local> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: regression: port www/squid fails to build on ia64 head Thread-Index: Acp81Ibz5VumimPwQ1Om7FBoG65BlAAAaqTg References: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> From: "Johan Hendriks" To: "Anton Shterenlikht" X-Virus-Scanned: by XS4ALL Virus Scanner Cc: freebsd-current@FreeBSD.org Subject: RE: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:01:28 -0000 >> * Johan Hendriks : >>=20 >> (Squid breakage in the YP/NIS helper) >>=20 >> > A long shot >> > Could it be that you have set the following in your src.conf >> > WITHOUT_NIS=3D yes >> > WITHOUT_RCMDS=3D yes >> > WITHOUT_RCS=3D yes >> >=20 >> > If i set those i get a similar error with squid (on i386 and amd64 ) >>=20 >> This is possible; the Squid 2.7 port still relies on WITHOUT_NIS/NO_NIS >> being set in make.conf. Due to the make.conf/src.conf split this does no >> longer work. I have added an OPTION to turn off NIS support to the squid >> 3.x ports and will merge this change into the Squid 2.7 port along with >> other changes soon. In the meantime you can work around this if you >> build www/squid with "make -DWITHOUT_NIS" or by adding WITHOUT_NIS=3Dyes >> to /etc/make.conf. >>=20 >> The same applies to systems built/installed without Heimdal support. >> Sorry for the breakage. >yes, I had WITHOUT_NIS=3D yes in /etc/src.conf, but not the other >two options. I have now rebuilt the system without this option, >but I still get the NIS build error. >If I build with "make -DWITHOUT_NIS", then I get this error: >Making all in negotiate_auth >Making all in squid_kerb_auth >cc -DHAVE_CONFIG_H -I. -I../../../include -DHEIMDAL -I./spnegohelp -I. -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT squid_kerb_auth.o -MD -MP ->MF .deps/squid_kerb_auth.Tpo -c -o squid_kerb_auth.o squid_kerb_auth.c >squid_kerb_auth.c:70:18: error: krb5.h: No such file or directory >*** Error code 1 >Stop in /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/negotiate_auth/squid _kerb_auth. >*** Error code 1 >does it mean I also need to build kerberos? I've WITHOUT_KERBEROS=3Dyes >in /etc/src.conf >many thanks >anton Yes it could not harm to remove that one from src.conf also. Regards, Johan Hendriks From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 16:45:15 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 595F51065679 for ; Mon, 14 Dec 2009 16:45:15 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id 1288C8FC1C for ; Mon, 14 Dec 2009 16:45:14 +0000 (UTC) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKE2p-0001Fu-2x; Mon, 14 Dec 2009 16:45:13 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKE2o-0003Fn-6u; Mon, 14 Dec 2009 16:45:10 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBEGj9vI087185; Mon, 14 Dec 2009 16:45:10 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBEGj97i087184; Mon, 14 Dec 2009 16:45:09 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Mon, 14 Dec 2009 16:45:09 +0000 From: Anton Shterenlikht To: Johan Hendriks Message-ID: <20091214164509.GC87017@mech-cluster241.men.bris.ac.uk> References: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> <57200BF94E69E54880C9BB1AF714BBCBA57377@w2003s01.double-l.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57200BF94E69E54880C9BB1AF714BBCBA57377@w2003s01.double-l.local> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -4.5 X-Spam-Level: ---- Cc: freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:45:15 -0000 On Mon, Dec 14, 2009 at 05:01:18PM +0100, Johan Hendriks wrote: > > > >> * Johan Hendriks : > >> > >> (Squid breakage in the YP/NIS helper) > >> > >> > A long shot > >> > Could it be that you have set the following in your src.conf > >> > WITHOUT_NIS= yes > >> > WITHOUT_RCMDS= yes > >> > WITHOUT_RCS= yes > >> > > >> > If i set those i get a similar error with squid (on i386 and amd64 > ) > >> > >> This is possible; the Squid 2.7 port still relies on > WITHOUT_NIS/NO_NIS > >> being set in make.conf. Due to the make.conf/src.conf split this does > no > >> longer work. I have added an OPTION to turn off NIS support to the > squid > >> 3.x ports and will merge this change into the Squid 2.7 port along > with > >> other changes soon. In the meantime you can work around this if you > >> build www/squid with "make -DWITHOUT_NIS" or by adding > WITHOUT_NIS=yes > >> to /etc/make.conf. > >> > >> The same applies to systems built/installed without Heimdal support. > >> Sorry for the breakage. > > >yes, I had WITHOUT_NIS= yes in /etc/src.conf, but not the other > >two options. I have now rebuilt the system without this option, > >but I still get the NIS build error. > > >If I build with "make -DWITHOUT_NIS", then I get this error: > > >Making all in negotiate_auth > >Making all in squid_kerb_auth > >cc -DHAVE_CONFIG_H -I. -I../../../include -DHEIMDAL -I./spnegohelp > -I. -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT squid_kerb_auth.o > -MD -MP ->MF .deps/squid_kerb_auth.Tpo -c -o squid_kerb_auth.o > squid_kerb_auth.c > >squid_kerb_auth.c:70:18: error: krb5.h: No such file or directory > >*** Error code 1 > > >Stop in > /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/negotiate_auth/squid > _kerb_auth. > >*** Error code 1 > > >does it mean I also need to build kerberos? I've WITHOUT_KERBEROS=yes > >in /etc/src.conf > > >many thanks > >anton > > Yes it could not harm to remove that one from src.conf also. well, instead I built with make -DWITHOUT_NIS -DWITHOUT_KERBEROS and left WITHOUT_KERBEROS=yes WITHOUT_NIS=yes in /etc/src.conf seems to work. By the way, do you know how to disable squid accept incoming connections. I need squid only to dial out, never to accept connections. I got lost in the conf file, but maybe there is a simpler option, e.g. squid_enable="NO" in /etc/rc.conf, perhaps? This is by analogy with sendmail. The following sendmail options would let sendmail run fine, but not accept connections: sendmail_enable="NO" sendmail_submit_enable="YES" sendmail_outbound_enable="YES" sendmail_msp_queue_enable="YES" many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 16:46:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D2A2E106566C; Mon, 14 Dec 2009 16:46:18 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 8BD758FC0A; Mon, 14 Dec 2009 16:46:17 +0000 (UTC) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKE3p-0004ON-S3; Mon, 14 Dec 2009 16:46:16 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKE3p-0003J7-1Z; Mon, 14 Dec 2009 16:46:13 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBEGkCar087210; Mon, 14 Dec 2009 16:46:12 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBEGkC9C087209; Mon, 14 Dec 2009 16:46:12 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Mon, 14 Dec 2009 16:46:12 +0000 From: Anton Shterenlikht To: Anton Shterenlikht , freebsd-current@freebsd.org, freebsd-ports@freebsd.org Message-ID: <20091214164612.GA87194@mech-cluster241.men.bris.ac.uk> References: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> <20091214163600.GA2420@wcfields.tmseck.homedns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091214163600.GA2420@wcfields.tmseck.homedns.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: Subject: Re: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:46:19 -0000 On Mon, Dec 14, 2009 at 05:36:01PM +0100, Thomas-Martin Seck wrote: > * Anton Shterenlikht (mexas@bristol.ac.uk): > > > On Sun, Dec 13, 2009 at 04:27:12PM -0000, Thomas-Martin Seck wrote: > > > * Johan Hendriks : > > > > > > (Squid breakage in the YP/NIS helper) > > > > > > > A long shot > > > > Could it be that you have set the following in your src.conf > > > > WITHOUT_NIS= yes > > > > WITHOUT_RCMDS= yes > > > > WITHOUT_RCS= yes > > > > > > > > If i set those i get a similar error with squid (on i386 and amd64 ) > > > > > > This is possible; the Squid 2.7 port still relies on WITHOUT_NIS/NO_NIS > > > being set in make.conf. Due to the make.conf/src.conf split this does no > > > longer work. I have added an OPTION to turn off NIS support to the squid > > > 3.x ports and will merge this change into the Squid 2.7 port along with > > > other changes soon. In the meantime you can work around this if you > > > build www/squid with "make -DWITHOUT_NIS" or by adding WITHOUT_NIS=yes > > > to /etc/make.conf. > > > > > > The same applies to systems built/installed without Heimdal support. > > > Sorry for the breakage. > > > > yes, I had WITHOUT_NIS= yes in /etc/src.conf, but not the other > > two options. I have now rebuilt the system without this option, > > but I still get the NIS build error. > > The other options are for the port, not for the base system. (Look at > www/squid/Makefile to see how this works.) > > If you set WITHOUT_NIS and/or WITHOUT_KERBEROS in src.conf, you > currently need to set these in make.conf, too so the port can pick these > settings up. > > > If I build with "make -DWITHOUT_NIS", then I get this error: > > > > Making all in negotiate_auth > > Making all in squid_kerb_auth > > cc -DHAVE_CONFIG_H -I. -I../../../include -DHEIMDAL -I./spnegohelp -I. -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT squid_kerb_auth.o -MD -MP -MF .deps/squid_kerb_auth.Tpo -c -o squid_kerb_auth.o squid_kerb_auth.c > > squid_kerb_auth.c:70:18: error: krb5.h: No such file or directory > > *** Error code 1 > > > > Stop in /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/negotiate_auth/squid_kerb_auth. > > *** Error code 1 > > > > does it mean I also need to build kerberos? I've WITHOUT_KERBEROS=yes > > in /etc/src.conf > > No, you just need to disable Kerberos support in Squid, because it's on > by default. Rebuild the port using "make clean ; make -DNO_KERBEROS" or > put WITHOUT_KERBEROS=yes or NO_KERBEROS=yes into /etc/make.conf before > rebuilding the port. But do a "make clean" first so Squid's configure > script does actually exclude these helpers from the build. yes, that's what I did. Seems to work many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 16:47:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E93A710656B9 for ; Mon, 14 Dec 2009 16:47:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id A7BA28FC08 for ; Mon, 14 Dec 2009 16:47:00 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 5899A46B17; Mon, 14 Dec 2009 11:47:00 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 84AE28A021; Mon, 14 Dec 2009 11:46:59 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 14 Dec 2009 11:08:48 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <200912110615.28030.thierry.herbelot@free.fr> In-Reply-To: <200912110615.28030.thierry.herbelot@free.fr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912141108.48169.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Mon, 14 Dec 2009 11:46:59 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Thierry Herbelot Subject: Re: Panic in a recent kernel (cardbus/pci related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:47:01 -0000 On Friday 11 December 2009 12:15:27 am Thierry Herbelot wrote: > Hello, > > I'm seeing a panic in my latest -Current kernel (config file == GENERIC minus > INVARIANTS, WITNESS and SMP). The machine is an older notebook, with a PCMCIA > network card. Can you try reverting the recent change to sys/dev/pci/pci.c to use resource_list_reserve() just to narrow down if that is the cause? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 16:55:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 717971065695 for ; Mon, 14 Dec 2009 16:55:18 +0000 (UTC) (envelope-from tmseck-lists@netcologne.de) Received: from smtp6.netcologne.de (smtp6.netcologne.de [194.8.194.26]) by mx1.freebsd.org (Postfix) with ESMTP id 2DFCD8FC20 for ; Mon, 14 Dec 2009 16:55:17 +0000 (UTC) Received: from wcfields.tmseck.homedns.org (xdsl-89-0-186-110.netcologne.de [89.0.186.110]) by smtp6.netcologne.de (Postfix) with SMTP id A17692A1D06 for ; Mon, 14 Dec 2009 17:36:05 +0100 (CET) Received: (qmail 2621 invoked by uid 1001); 14 Dec 2009 16:36:01 -0000 Date: Mon, 14 Dec 2009 17:36:01 +0100 From: Thomas-Martin Seck To: Anton Shterenlikht Message-ID: <20091214163600.GA2420@wcfields.tmseck.homedns.org> Mail-Followup-To: Anton Shterenlikht , freebsd-current@freebsd.org, freebsd-ports@freebsd.org References: <57200BF94E69E54880C9BB1AF714BBCBA5736C@w2003s01.double-l.local> <20091213162712.1171.qmail@wcfields.tmseck.homedns.org> <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091214154144.GA86962@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Organization: a private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 X-Attribution: tms Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: regression: port www/squid fails to build on ia64 head X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 16:55:18 -0000 * Anton Shterenlikht (mexas@bristol.ac.uk): > On Sun, Dec 13, 2009 at 04:27:12PM -0000, Thomas-Martin Seck wrote: > > * Johan Hendriks : > > > > (Squid breakage in the YP/NIS helper) > > > > > A long shot > > > Could it be that you have set the following in your src.conf > > > WITHOUT_NIS= yes > > > WITHOUT_RCMDS= yes > > > WITHOUT_RCS= yes > > > > > > If i set those i get a similar error with squid (on i386 and amd64 ) > > > > This is possible; the Squid 2.7 port still relies on WITHOUT_NIS/NO_NIS > > being set in make.conf. Due to the make.conf/src.conf split this does no > > longer work. I have added an OPTION to turn off NIS support to the squid > > 3.x ports and will merge this change into the Squid 2.7 port along with > > other changes soon. In the meantime you can work around this if you > > build www/squid with "make -DWITHOUT_NIS" or by adding WITHOUT_NIS=yes > > to /etc/make.conf. > > > > The same applies to systems built/installed without Heimdal support. > > Sorry for the breakage. > > yes, I had WITHOUT_NIS= yes in /etc/src.conf, but not the other > two options. I have now rebuilt the system without this option, > but I still get the NIS build error. The other options are for the port, not for the base system. (Look at www/squid/Makefile to see how this works.) If you set WITHOUT_NIS and/or WITHOUT_KERBEROS in src.conf, you currently need to set these in make.conf, too so the port can pick these settings up. > If I build with "make -DWITHOUT_NIS", then I get this error: > > Making all in negotiate_auth > Making all in squid_kerb_auth > cc -DHAVE_CONFIG_H -I. -I../../../include -DHEIMDAL -I./spnegohelp -I. -O2 -pipe -fno-strict-aliasing -D_REENTRANT -MT squid_kerb_auth.o -MD -MP -MF .deps/squid_kerb_auth.Tpo -c -o squid_kerb_auth.o squid_kerb_auth.c > squid_kerb_auth.c:70:18: error: krb5.h: No such file or directory > *** Error code 1 > > Stop in /usr/ports/www/squid/work/squid-2.7.STABLE7/helpers/negotiate_auth/squid_kerb_auth. > *** Error code 1 > > does it mean I also need to build kerberos? I've WITHOUT_KERBEROS=yes > in /etc/src.conf No, you just need to disable Kerberos support in Squid, because it's on by default. Rebuild the port using "make clean ; make -DNO_KERBEROS" or put WITHOUT_KERBEROS=yes or NO_KERBEROS=yes into /etc/make.conf before rebuilding the port. But do a "make clean" first so Squid's configure script does actually exclude these helpers from the build. From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 18:45:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E552D1065670 for ; Mon, 14 Dec 2009 18:45:02 +0000 (UTC) (envelope-from jh@FreeBSD.org) Received: from gw02.mail.saunalahti.fi (gw02.mail.saunalahti.fi [195.197.172.116]) by mx1.freebsd.org (Postfix) with ESMTP id A61688FC28 for ; Mon, 14 Dec 2009 18:45:02 +0000 (UTC) Received: from a91-153-117-195.elisa-laajakaista.fi (a91-153-117-195.elisa-laajakaista.fi [91.153.117.195]) by gw02.mail.saunalahti.fi (Postfix) with SMTP id 33B3013964A; Mon, 14 Dec 2009 20:26:45 +0200 (EET) Date: Mon, 14 Dec 2009 20:26:45 +0200 From: Jaakko Heinonen To: Alexander Motin Message-ID: <20091214182645.GA2764@a91-153-117-195.elisa-laajakaista.fi> References: <4B1C1316.6080707@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B1C1316.6080707@FreeBSD.org> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Alexander Best , freebsd-current@freebsd.org Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 18:45:03 -0000 On 2009-12-06, Alexander Motin wrote: > Alexander Best wrote: > > i would also like to ask: what will become of burncd in the future? will it be > > adjusted to work with CAM? will it be removed/moved to ports? or will we > > replace it with cdrecord/something else? > > I don't know. In won't work any more in present state, and I don't see > much reasons to update it, as cdrecord seems to work fine. I did some work to port acd(4) functionality needed by burncd(8) to user space. My version of burncd can now burn a CD using a pass(4) device but there's still a fair amount of work to do to make it releasable. I am not sure if I have interest to develop it further. If someone wants to get the source, please contact me privately. -- Jaakko From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 19:26:35 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD0AF106568B for ; Mon, 14 Dec 2009 19:26:35 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228]) by mx1.freebsd.org (Postfix) with ESMTP id 55AEE8FC08 for ; Mon, 14 Dec 2009 19:26:34 +0000 (UTC) Received: by fxm28 with SMTP id 28so1718866fxm.13 for ; Mon, 14 Dec 2009 11:26:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=1p+HMLNKC4oedFSLjIApk1SvhQQwmVy21T/ik+uUC5I=; b=Fh+17bt12R0q8SHhUkVslwgoryebjV7JKPdqFB5B+CqS/chGUA08VZEvpkLsa/XEuo tRyLgGwWVpExMS+aVMMdI38Ry0Ci9brICT75WLZcXWr5TX3ppQ8HTuobifzaLtN4FtXA PvrfUVElMszAJcxx+0dHxOEBr5y+oN9QnN9CQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=eJsL3TcYpLPh0Ds1+y+r/7ZioXjr9en5Sf4ti3PNeviNcZDRsn3EUTwj807ZD7tP4u nQdEy6LxM5M4Sfd+L/mSbKq24LKi2geX/xUv1iaO/GGcDFYC+yx0RuF2tzwudPP2PvON qfxbLEXpzGHlPh9RlrE4MYe+3sxnlRm+xzVTM= MIME-Version: 1.0 Received: by 10.216.86.195 with SMTP id w45mr2212974wee.82.1260818793598; Mon, 14 Dec 2009 11:26:33 -0800 (PST) In-Reply-To: <4B25D32B.70306@elischer.org> References: <4B25D32B.70306@elischer.org> Date: Mon, 14 Dec 2009 14:26:32 -0500 Message-ID: From: Ryan Stone To: Julian Elischer Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: profiling kernel modules. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 19:26:35 -0000 I find that the best way to profile the kernel is with pmc. You don't need to compile anything with a special option(other than including the hwpmc hooks in the kernel with the HWPMC_HOOKS option) so you can use it at any time on the same code you'll be shipping. pmc does statistical profiling; it uses whatever performance monitoring counters are provided by the hardware. It has a pretty low overhead, especially compared with other profiling techniques. It's really easy to use, too: 1) If hwpmc is not compiled into your kernel, kldload hwpmc 2) Run pmcstat to begin taking samples(make sure that whatever you are profiling is busy doing work first!): pmcstat -S unhalted-cycles -O /tmp/samples.out The -S option specifies what event you want to use to trigger sampling. The unhalted-cycles is the best event to use if your hardware supports it; pmc will take a sample every 64K non-idle CPU cycles, which is basically equivalent to sampling based on time. If the unhalted-cycles event is not supported by your hardware then the instructions event will probably be the next best choice(although it's nowhere near as good, as it will not be able to tell you, for example, if a particular function is very expensive because it takes a lot of cache misses compared to the rest of your program). One caveat with the unhalted-cycles event is that time spent spinning on a spinlock or adaptively spinning on a MTX_DEF mutex will not be counted by this event, because most of the spinning time is spent executing an hlt instruction that idles the CPU for a short period of time. Modern Intel and AMD CPUs offer a dizzying array of events. They're mostly only useful if you suspect that a particular kind of event is hurting your performance and you would like to know what is causing those events. For example, if you suspect that data cache misses are causing you problems you can take samples on cache misses. Unfortunately on some of the newer CPUs(namely the Core2 family, because that's what I'm doing most of my profiling on nowadays) I find it difficult to figure out just what event to use to profile based on cache misses. man pmc will give you an overview of pmc, and there are manpages for every CPU family supported(eg man pmc.core2) 3) After you've run pmcstat for "long enough"(a proper definition of long enough requires a statistician, which I most certainly am not, but I find that for a busy system 10 seconds is enough), Control-C it to stop it*. You can use pmcstat to post-process the samples into human-readable text: pmcstat -R /tmp/samples.out -G /tmp/graph.txt The graph.txt file will show leaf functions on the left and their callers beneath them, indented to reflect the callchain. It's not too easy to describe and I don't have sample output available right now. Another interesting tool for post-processing the samples is pmcannotate. I've never actually used the tool before but it will annotate the program's source to show which lines are the most expensive. This of course needs unstripped modules to work. I think that it will also work if the GNU "debug link" is in the stripped module pointing to the location of the file with symbols. * Here's a tip I picked up from Joseph Koshy's blog: to collect samples for a fixed period of time(say 1 minute), have pmcstat run the sleep command: pmcstat -S unhalted-cycles -O /tmp/samples.out sleep 60 From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 19:56:10 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A477D1065679 for ; Mon, 14 Dec 2009 19:56:10 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outF.internet-mail-service.net (outf.internet-mail-service.net [216.240.47.229]) by mx1.freebsd.org (Postfix) with ESMTP id 8A7F58FC1E for ; Mon, 14 Dec 2009 19:56:10 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 303BE2439; Mon, 14 Dec 2009 11:56:10 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id AA8502D6011; Mon, 14 Dec 2009 11:56:09 -0800 (PST) Message-ID: <4B269866.2070809@elischer.org> Date: Mon, 14 Dec 2009 11:56:22 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Ryan Stone References: <4B25D32B.70306@elischer.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: profiling kernel modules. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 19:56:10 -0000 Ryan Stone wrote: > I find that the best way to profile the kernel is with pmc. You don't > need to compile anything with a special option(other than including > the hwpmc hooks in the kernel with the HWPMC_HOOKS option) so you can > use it at any time on the same code you'll be shipping. pmc does > statistical profiling; it uses whatever performance monitoring > counters are provided by the hardware. It has a pretty low overhead, > especially compared with other profiling techniques. It's really easy > to use, too: thanks for all this. BTW I just tried the old kgmon/gprof profiling as a control. it appears that on amd64 it doesn't work. gprof can't read the file that the kernel puts out. (useful!). > > 1) If hwpmc is not compiled into your kernel, kldload hwpmc > 2) Run pmcstat to begin taking samples(make sure that whatever you are > profiling is busy doing work first!): > > pmcstat -S unhalted-cycles -O /tmp/samples.out > > The -S option specifies what event you want to use to trigger > sampling. The unhalted-cycles is the best event to use if your > hardware supports it; pmc will take a sample every 64K non-idle CPU > cycles, which is basically equivalent to sampling based on time. If > the unhalted-cycles event is not supported by your hardware then the > instructions event will probably be the next best choice(although it's > nowhere near as good, as it will not be able to tell you, for example, > if a particular function is very expensive because it takes a lot of > cache misses compared to the rest of your program). One caveat with > the unhalted-cycles event is that time spent spinning on a spinlock or > adaptively spinning on a MTX_DEF mutex will not be counted by this > event, because most of the spinning time is spent executing an hlt > instruction that idles the CPU for a short period of time. > > Modern Intel and AMD CPUs offer a dizzying array of events. They're > mostly only useful if you suspect that a particular kind of event is > hurting your performance and you would like to know what is causing > those events. For example, if you suspect that data cache misses are > causing you problems you can take samples on cache misses. > Unfortunately on some of the newer CPUs(namely the Core2 family, > because that's what I'm doing most of my profiling on nowadays) I find > it difficult to figure out just what event to use to profile based on > cache misses. man pmc will give you an overview of pmc, and there are > manpages for every CPU family supported(eg man pmc.core2) > > 3) After you've run pmcstat for "long enough"(a proper definition of > long enough requires a statistician, which I most certainly am not, > but I find that for a busy system 10 seconds is enough), Control-C it > to stop it*. You can use pmcstat to post-process the samples into > human-readable text: > > pmcstat -R /tmp/samples.out -G /tmp/graph.txt > > The graph.txt file will show leaf functions on the left and their > callers beneath them, indented to reflect the callchain. It's not too > easy to describe and I don't have sample output available right now. > > > Another interesting tool for post-processing the samples is > pmcannotate. I've never actually used the tool before but it will > annotate the program's source to show which lines are the most > expensive. This of course needs unstripped modules to work. I think > that it will also work if the GNU "debug link" is in the stripped > module pointing to the location of the file with symbols. > > > * Here's a tip I picked up from Joseph Koshy's blog: to collect > samples for a fixed period of time(say 1 minute), have pmcstat run the > sleep command: > > pmcstat -S unhalted-cycles -O /tmp/samples.out sleep 60 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 20:47:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2AFD21065672 for ; Mon, 14 Dec 2009 20:47:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id C6D048FC0A for ; Mon, 14 Dec 2009 20:47:15 +0000 (UTC) Received: (qmail 26942 invoked by uid 399); 14 Dec 2009 20:47:15 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 20:47:15 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B26A45B.4020302@FreeBSD.org> Date: Mon, 14 Dec 2009 12:47:23 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: "b. f." References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 20:47:16 -0000 b. f. wrote: > On 12/14/09, Doug Barton wrote: > I believe what they meant in the Intel document was that in order to > use certain features supported by AHCI, such as NCQ, the disk drive > must also support them. Your disk drive seems to support NCQ. Ok, I believe you. :) This is clearly not my area. > So this does not seem to explain why ahci(4) fails to attach to your > SATA controller. I suspect that your bios or motherboard fails to use > AHCI mode. Maybe there is a later bios revision, There is no later BIOS available, at least not from Dell. This is a Latitude D620 laptop. And as I said previously, there are no BIOS options that mention anything even remotely similar. There are two hard drive related options. One is related to making it "slower and quieter" vs. "faster and noisier." Guess which one I picked. :) The other is related to power management (DPMI). I did look up the spec sheet on the hard drive last night, and although it does mention SATA and NCQ it does not explicitly mention AHCI. http://www.hitachigst.com/tech/techlib.nsf/techdocs/50C8DBC2A315A4C786256F400065B756/$file/7K100_SATA_FINAL_DS.pdf and http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_7K100 if you're interested. I also didn't see any mentions of jumpers on the drive to enable AHCI, which I was kind of hoping for since that's pretty easy to remove. > or some jumper > settings on the board that will allow it to be enabled. You may have > to talk to the manufacturer. I would be willing to dive into that if someone could give me clear guidance that one exists. I'm not really eager to open the case otherwise. > Of course, there is a small chance that > there is a problem with our drivers. Have you tried a live CD of a > Linux distro, to see AHCI works with another OS? No, but I'm happy to do so. Any suggestions on what distro is most likely to succeed, and what to look for? I have used Ubuntu for a project in the past with good success but I'd be willing to try anything that folks think will work. In any case I do appreciate your time on this. I run -current on purpose to try out new features, help get them fleshed out from a "regular user" perspective, and to expose bugs (often my own of course). Better performance and cool new toys don't hurt either ... Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 20:49:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E106106566C for ; Mon, 14 Dec 2009 20:49:32 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id BDEAB8FC13 for ; Mon, 14 Dec 2009 20:49:31 +0000 (UTC) Received: (qmail 30057 invoked by uid 399); 14 Dec 2009 20:49:31 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 14 Dec 2009 20:49:31 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B26A4E3.9090200@FreeBSD.org> Date: Mon, 14 Dec 2009 12:49:39 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Doug Barton , Robert Watson , Alex Keda , freebsd-current References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <4B25B0CA.1070006@FreeBSD.org> <20091214155853.GC78318@FreeBSD.org> In-Reply-To: <20091214155853.GC78318@FreeBSD.org> X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 20:49:32 -0000 Wojciech A. Koszek wrote: > It looks fine for the first glance. I would also reconsider putting it in > DEFAULTS, as des@ pointed out. Ok, no objections on my part. I thought putting it in the file itself would make it easier for those who wanted to remove it, but I'm also in agreement with those that believe that there is no real need to remove it except for extreme cases, and they (generally) already know what they are doing. :) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 21:47:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E26F106566C; Mon, 14 Dec 2009 21:47:05 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from mail-yw0-f172.google.com (mail-yw0-f172.google.com [209.85.211.172]) by mx1.freebsd.org (Postfix) with ESMTP id 0C02D8FC19; Mon, 14 Dec 2009 21:47:04 +0000 (UTC) Received: by ywh2 with SMTP id 2so3524453ywh.27 for ; Mon, 14 Dec 2009 13:47:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=j+ln1p0D6G0czQUoJFXdLZxwcB+O9d+AqHR2v9RN9LE=; b=iLKD2D0jbLxk0Zk/iITIbQPGgr2/DGIOAaa9DR8k6jm4+Y5t5tNNL27Wn5anxkiK9u Sq62WUHqRvM0dN1Ch2NV1QKnPVzFFWkxIXyL6tKswTLM/dJN81O+RQqIP5tCVAXnshpb FSoc2noJo/rphEtHPqsbYodbBbbVT9D7UB9S8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=vBfj4MYEaogCmkbr8JWx30Qa77c1f4uxiiQVjg0Q0H57Lnci0rWNDcZx3eQ1GNMLre lRGtM0AURAWfQQSIz6pL7M/jVBghYJwsqOeoVnyZ155EGMg0n+qDGHwe3PMYkYlnyj1w e4STyWENLo9OVMSpMLrUG2GP+5AEJIzi4ZvVg= MIME-Version: 1.0 Received: by 10.101.4.27 with SMTP id g27mr8053749ani.100.1260827224252; Mon, 14 Dec 2009 13:47:04 -0800 (PST) Date: Mon, 14 Dec 2009 16:47:04 -0500 Message-ID: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> From: Alexander Sack To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-scsi@freebsd.org Subject: aac(4) handling of probe when no devices are there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 21:47:05 -0000 Hello Again: I guess I have a technical question/concern that I was looking for feedback. During the probe sequence, aac(4) conditionally responds to INQUIRY commands depending on target LUN: aac_cam.c/aac_cam_complete(): 532 if (command == INQUIRY) { 533 if (ccb->ccb_h.status == CAM_REQ_CMP) { 534 device = ccb->csio.data_ptr[0] & 0x1f; 535 /* 536 * We want DASD and PROC devices to only be 537 * visible through the pass device. 538 */ 539 if ((device == T_DIRECT) || 540 (device == T_PROCESSOR) || 541 (sc->flags & AAC_FLAGS_CAM_PASSONLY)) 542 ccb->csio.data_ptr[0] = 543 ((device & 0xe0) | T_NODEVICE); 544 } else if (ccb->ccb_h.status == CAM_SEL_TIMEOUT && 545 ccb->ccb_h.target_lun != 0) { 546 /* fix for INQUIRYs on Lun>0 */ 547 ccb->ccb_h.status = CAM_DEV_NOT_THERE; 548 } 549 } Why is CAM_DEV_NOT_THERE skipped on LUN 0? This is true on my target 6.1-amd64 machine as well as CURRENT. The reason why I ask this is because now that aac(4) is sequential scanned, there are a lot of cam interrupts that come in on my 6.x machine where the threshold is only 500 and I get the interrupt storm threshold warning for swi2 pretty quickly: Interrupt storm detected on "swi2:"; throttling interrupt source Obviously its contingent on the number of adapters you have on your system. On CURRENT I didn't see this because the threshold is double (I think its a 1000 by default). The issue is the number of xpt_async(AC_LOST_DEVICE, ..) calls during the scan. The probe sequence in CURRENT as well as 6.1 handles CAM_SEL_TIMEOUT a little differently depending on context. scsi_xpt.c/probedone(): 1090 } else if (cam_periph_error(done_ccb, 0, 1091 done_ccb->ccb_h.target_lun > 0 1092 ? SF_RETRY_UA|SF_QUIET_IR 1093 : SF_RETRY_UA, 1094 &softc->saved_ccb) == ERESTART) { 1095 return; 1096 } else if ((done_ccb->ccb_h.status & CAM_DEV_QFRZN) != 0) { 1097 /* Don't wedge the queue */ 1098 xpt_release_devq(done_ccb->ccb_h.path, /*count*/1, 1099 /*run_queue*/TRUE); 1100 } 1101 /* 1102 * If we get to this point, we got an error status back 1103 * from the inquiry and the error status doesn't require 1104 * automatically retrying the command. Therefore, the 1105 * inquiry failed. If we had inquiry information before 1106 * for this device, but this latest inquiry command failed, 1107 * the device has probably gone away. If this device isn't 1108 * already marked unconfigured, notify the peripheral 1109 * drivers that this device is no more. 1110 */ 1111 if ((path->device->flags & CAM_DEV_UNCONFIGURED) == 0) 1112 /* Send the async notification. */ 1113 xpt_async(AC_LOST_DEVICE, path, NULL); 1114 1115 xpt_release_ccb(done_ccb); 1116 break; 1117 } But on cam_periph_error(), this will issue a xpt_async(AC_LOST_DEVICE, path, NULL) regardless of whether or not the device has been scene already (as per the comment above), i.e. on every initial bus scan, you will get into (on an aac(4) card with LUN > 0): cam_periph.c/cam_periph_error(): 1697 case CAM_SEL_TIMEOUT: 1698 { . . 1729 /* 1730 * Let peripheral drivers know that this device has gone 1731 * away. 1732 */ 1733 xpt_async(AC_LOST_DEVICE, newpath, NULL); 1734 xpt_free_path(newpath); 1735 break; Is this really right? This generates A LOT of interrupts noise when no devices are attached during the initial scan, i.e. we are treating the initial scan of failed INQUIRY commands on the SCSI BUS as if we really lost a device during a selection timeout. (we even generate a path to issue the async event). Obviously if aac(4) returned CAM_NO_DEVICE_THERE you avoid this but there is some history here and I've yet to fully grasp the intent of the original fix on LUNs greater than zero. What was the problem? Comments/thoughts appreciated? Thanks! -aps From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 22:09:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29FB61065672; Mon, 14 Dec 2009 22:09:10 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id C765A8FC1F; Mon, 14 Dec 2009 22:09:09 +0000 (UTC) Received: by yxe1 with SMTP id 1so3268916yxe.3 for ; Mon, 14 Dec 2009 14:09:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TYITU85RbA5zATcKmRKq31IdKLeDXE1KbMXg0bigR6E=; b=OKy2wCUcAimvYFlOp/8knMDwvDxFqs/0LlDSOM6cWUcLn5Fy9ToqRY6Bhj8UBJuilZ nBnM8qZ2XA0LsOs/lGnXkjxcyKeeDW/NIDIZ6z0bIyvoMdL+rHXywXuSif+1yjoU8bVS SoTMigs7P0SlsmN21yrN2+6FnOfFdFhDOQgOQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=D3GEPUhxKURWjUjO8wtItNAEyq+JeRVF0h6HENuPEMDFUNb36s97fEbXFf8ApIxXWY Z97C+ghwwRW0NmFcaIxJx0WmjynW9KUXyQ9dXyKSIqYhSIoUpv8h1Ik8KM6TJEhuHznh +6Kn1z+CbAq5DbsGYREwhxDbQapv3Uv0+Gg9I= MIME-Version: 1.0 Received: by 10.101.11.2 with SMTP id o2mr8217574ani.52.1260828548538; Mon, 14 Dec 2009 14:09:08 -0800 (PST) In-Reply-To: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> References: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> Date: Mon, 14 Dec 2009 17:09:08 -0500 Message-ID: <3c0b01820912141409t74a3554ctd224db485ceeb80c@mail.gmail.com> From: Alexander Sack To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-scsi@freebsd.org Subject: Re: aac(4) handling of probe when no devices are there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 22:09:10 -0000 On Mon, Dec 14, 2009 at 4:47 PM, Alexander Sack wrote: > Hello Again: > > I guess I have a technical question/concern that I was looking for > feedback. =A0 During the probe sequence, aac(4) conditionally responds > to INQUIRY commands depending on target LUN: > > aac_cam.c/aac_cam_complete(): > 532 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (command =3D=3D IN= QUIRY) { > 533 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (c= cb->ccb_h.status =3D=3D CAM_REQ_CMP) { > 534 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 devic= e =3D ccb->csio.data_ptr[0] & 0x1f; > 535 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* > 536 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* = We want DASD and PROC devices to only be > 537 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* = visible through the pass device. > 538 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*/ > 539 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((= device =3D=3D T_DIRECT) || > 540 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 (device =3D=3D T_PROCESSOR) || > 541 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 (sc->flags & AAC_FLAGS_CAM_PASSONLY)) > 542 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->csio.data_ptr[0] =3D > 543 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 ((device & 0xe0) | T_NODEVICE); > 544 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } els= e if (ccb->ccb_h.status =3D=3D > CAM_SEL_TIMEOUT && > 545 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->ccb_h.target_lun !=3D 0) { > 546 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 /* fix for INQUIRYs on Lun>0 */ > 547 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->ccb_h.status =3D > CAM_DEV_NOT_THERE; > 548 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > 549 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > > Why is CAM_DEV_NOT_THERE skipped on LUN 0? =A0This is true on my target > 6.1-amd64 machine as well as CURRENT. =A0The reason why I ask this is > because now that aac(4) is sequential scanned, there are a lot of cam > interrupts that come in on my 6.x machine where the threshold is only > 500 and I get the interrupt storm threshold warning for swi2 pretty > quickly: > > Interrupt storm detected on "swi2:"; throttling interrupt source > > Obviously its contingent on the number of adapters you have on your > system. =A0On CURRENT I didn't see this because the threshold is double > (I think its a 1000 by default). > > The issue is the number of xpt_async(AC_LOST_DEVICE, ..) calls during > the scan. =A0The probe sequence in CURRENT as well as 6.1 handles > CAM_SEL_TIMEOUT a little differently depending on context. > > scsi_xpt.c/probedone(): > 1090 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } else if (cam_periph_error(done_ccb= , 0, > 1091 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 done_ccb->ccb_h.target_lun > 0 > 1092 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 ? SF_RETRY_UA|SF_QUIET_IR > 1093 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 : SF_RETRY_UA, > 1094 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 &softc->saved_ccb) =3D=3D > ERESTART) { > 1095 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 return; > 1096 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } else if ((done_ccb->ccb_h.status &= CAM_DEV_QFRZN) !=3D 0) { > 1097 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* Don't wedge the q= ueue */ > 1098 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xpt_release_devq(don= e_ccb->ccb_h.path, /*count*/1, > 1099 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0/*run_queue*/TRUE); > 1100 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > 1101 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* > 1102 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* If we get to this point, we got= an error status back > 1103 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* from the inquiry and the error = status doesn't require > 1104 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* automatically retrying the comm= and. =A0Therefore, the > 1105 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* inquiry failed. =A0If we had in= quiry information before > 1106 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* for this device, but this lates= t inquiry command failed, > 1107 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* the device has probably gone aw= ay. =A0If this device isn't > 1108 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* already marked unconfigured, no= tify the peripheral > 1109 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* drivers that this device is no = more. > 1110 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*/ > 1111 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((path->device->flags & CAM_DEV_U= NCONFIGURED) =3D=3D 0) > 1112 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* Send the async no= tification. */ > 1113 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xpt_async(AC_LOST_DE= VICE, path, NULL); > 1114 > 1115 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xpt_release_ccb(done_ccb); > 1116 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 break; > 1117 =A0 =A0 =A0 =A0 } > > But on cam_periph_error(), this will issue a xpt_async(AC_LOST_DEVICE, > path, NULL) regardless of whether or not the device has been scene > already (as per the comment above), i.e. on every initial bus scan, > you will get into (on an aac(4) card with LUN > 0): > > cam_periph.c/cam_periph_error(): > 1697 =A0 =A0 =A0 =A0 case CAM_SEL_TIMEOUT: > 1698 =A0 =A0 =A0 =A0 { > . > . > 1729 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* > 1730 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* Let peripheral drivers know tha= t this device has gone > 1731 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0* away. > 1732 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*/ > 1733 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xpt_async(AC_LOST_DEVICE, newpath, N= ULL); > 1734 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 xpt_free_path(newpath); > 1735 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 break; > > Is this really right? This generates A LOT of interrupts noise when no > devices are attached during the initial scan, i.e. we are treating the > initial scan of failed INQUIRY commands on the SCSI BUS as if we > really lost a device during a selection timeout. =A0(we even generate a > path to issue the async event). I should have properly titled the thread a little bit better, but basically we always generate a ton of software CAM interrupts during a LUN scan for targets on aac(4) that do not really exist (i.e. nothing is truly there). We do this because we treat the initial INQUIRY sent down equivalent to a selection timeout instead of the device is not really there. There seems to be an historical workaround for part of this issue but I am trying to delve deeper in order to do the *right thing* for our 6.1 deployments (as well as 7.x and CURRENT). -aps From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 22:36:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C1BEA106566B; Mon, 14 Dec 2009 22:36:58 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-pz0-f185.google.com (mail-pz0-f185.google.com [209.85.222.185]) by mx1.freebsd.org (Postfix) with ESMTP id 8AE9A8FC08; Mon, 14 Dec 2009 22:36:58 +0000 (UTC) Received: by pzk15 with SMTP id 15so2528979pzk.3 for ; Mon, 14 Dec 2009 14:36:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=FWBpyhN5xXb0Ol2/XMCfOmvBTle/6DKhPcBTa1kc3kQ=; b=eeIiYizGj3SzguHkGDIWgafHzMF5vaz41n5S+qxe+LgHeE5D+gjIDXrYeTuZU1wPJD wFlHo7UBsO63w9am2vxWxi/f5nZpqGFp2wUI+TALLEEwdsf3FOA+YUdXIJ370w335dgT mVenbR+YKQ3n0QUJO2k7tMAshB9lAk8kSOBkc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gF8fN/vFPAWhk+Hk12qp8yqpPN/0wShAR036k8zop6bT7YbPONNlq57bdM53kKqs4N ilwOrp0kQm1mr6OKa5OTyKLOjxHSynIMogrm9EVdL4tJGtgxif2zhargIK7N10TrgA0n 7hF+Sh7k7ZoOabyQNIoph0csAuPVf4tfnP1YA= MIME-Version: 1.0 Received: by 10.142.196.1 with SMTP id t1mr3621052wff.71.1260830214749; Mon, 14 Dec 2009 14:36:54 -0800 (PST) In-Reply-To: <4B26A45B.4020302@FreeBSD.org> References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> <4B26A45B.4020302@FreeBSD.org> Date: Mon, 14 Dec 2009 16:36:54 -0600 Message-ID: <6201873e0912141436j24de325dm45aac38a89bd047c@mail.gmail.com> From: Adam Vande More To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org, "b. f." Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 22:36:58 -0000 On Mon, Dec 14, 2009 at 2:47 PM, Doug Barton wrote: > b. f. wrote: > > On 12/14/09, Doug Barton wrote: > > I believe what they meant in the Intel document was that in order to > > use certain features supported by AHCI, such as NCQ, the disk drive > > must also support them. Your disk drive seems to support NCQ. > > Ok, I believe you. :) This is clearly not my area. > > > So this does not seem to explain why ahci(4) fails to attach to your > > SATA controller. I suspect that your bios or motherboard fails to use > > AHCI mode. Maybe there is a later bios revision, > > There is no later BIOS available, at least not from Dell. This is a > Latitude D620 laptop. And as I said previously, there are no BIOS > options that mention anything even remotely similar. There are two > hard drive related options. One is related to making it "slower and > quieter" vs. "faster and noisier." Guess which one I picked. :) The > other is related to power management (DPMI). > > I did look up the spec sheet on the hard drive last night, and > although it does mention SATA and NCQ it does not explicitly mention > AHCI. > > http://www.hitachigst.com/tech/techlib.nsf/techdocs/50C8DBC2A315A4C786256F400065B756/$file/7K100_SATA_FINAL_DS.pdf > and > http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_7K100 > if you're interested. > > I also didn't see any mentions of jumpers on the drive to enable AHCI, > which I was kind of hoping for since that's pretty easy to remove. > > > or some jumper > > settings on the board that will allow it to be enabled. You may have > > to talk to the manufacturer. > > I would be willing to dive into that if someone could give me clear > guidance that one exists. I'm not really eager to open the > case otherwise. > > > Of course, there is a small chance that > > there is a problem with our drivers. Have you tried a live CD of a > > Linux distro, to see AHCI works with another OS? > > No, but I'm happy to do so. Any suggestions on what distro is most > likely to succeed, and what to look for? I have used Ubuntu for a > project in the past with good success but I'd be willing to try > anything that folks think will work. > > In any case I do appreciate your time on this. I run -current on > purpose to try out new features, help get them fleshed out from a > "regular user" perspective, and to expose bugs (often my own of > course). Better performance and cool new toys don't hurt either ... > A bit of research leads to believe you are SOL on ahci/NCQ for this system unless you're able to hack a BIOS. I believe both drive and controller are capable of running it, but Dell has disabled it as an option for some reason. -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Mon Dec 14 23:45:44 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38B401065676 for ; Mon, 14 Dec 2009 23:45:44 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 027658FC15 for ; Mon, 14 Dec 2009 23:45:43 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 0D4F973098; Tue, 15 Dec 2009 00:53:07 +0100 (CET) Date: Tue, 15 Dec 2009 00:53:07 +0100 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20091214235307.GA5345@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Dec 2009 23:45:44 -0000 The following ipfw patch (which i wrote back in 2001/2002) makes ipfw logging possible through tcpdump -- it works by passing to the fake device 'ipfw0' all packets matching rules marked 'log' . The use is very simple -- to test it just do ipfw add 100 count log ip from any to any and then tcpdump -ni ipfw0 will show all matching traffic. I think this is a quite convenient and flexible option, so if there are no objections I plan to commit it to head. cheers luigi Index: ../head/sys/netinet/ipfw/ip_fw2.c =================================================================== --- ../head/sys/netinet/ipfw/ip_fw2.c (revision 200551) +++ ../head/sys/netinet/ipfw/ip_fw2.c (working copy) @@ -65,6 +65,8 @@ #include #include /* for ETHERTYPE_IP */ #include +#include /* for IFT_ETHER */ +#include /* for BPF */ #include #include #include @@ -338,6 +340,15 @@ "Enable keepalives for dyn. rules"); #endif /* SYSCTL_NODE */ +#ifdef DEV_IPFW +static struct ifnet *ifn; /* hook to attach to bpf */ +static int +ipfw_ifnet_ioctl(struct ifnet *ifp, u_long cmd, caddr_t addr) +{ + return EINVAL; +} +#endif + /* * L3HDR maps an ipv4 pointer into a layer3 header pointer of type T * Other macros just cast void * into the appropriate type @@ -3056,6 +3067,29 @@ if (V_fw_verbose) ipfw_log(f, hlen, args, m, oif, offset, tablearg, ip); +#ifdef DEV_IPFW + else if (ifn && ifn->if_bpf != NULL) { + /* This kludge is OK; BPF treats + *the "mbuf" as read-only */ + struct m_hdr mh; + mh.mh_next = m; + mh.mh_len = ETHER_HDR_LEN; + if (args->eh) /* layer2, complete */ + mh.mh_data = (char *)args->eh; + else { + /* fake header and restore wire format*/ + mh.mh_data = "DDDDDDSSSSSS\x08\x00"; + ip->ip_off = ntohs(ip->ip_off); + ip->ip_len = ntohs(ip->ip_len); + } + BPF_MTAP(ifn, (struct mbuf *)&mh); + if (args->eh == NULL) { + /* restore IP format */ + ip->ip_off = htons(ip->ip_off); + ip->ip_len = htons(ip->ip_len); + } + } +#endif /* DEV_IPFW */ match = 1; break; @@ -4830,6 +4864,19 @@ printf("limited to %d packets/entry by default\n", V_verbose_limit); +#ifdef DEV_IPFW /** bpf code **/ + ifn = if_alloc(IFT_ETHER); + if_initname(ifn, "ipfw", 0); + ifn->if_mtu = 65536; + ifn->if_flags = IFF_UP | IFF_SIMPLEX | IFF_MULTICAST; + ifn->if_ioctl = ipfw_ifnet_ioctl; /* getaddr */ + ifn->if_addrlen = 6; + ifn->if_hdrlen = 14; + if_attach(ifn); + ifn->if_baudrate = IF_Mbps(10); + bpfattach(ifn, DLT_EN10MB, 14); +#endif /** end bpf code **/ + return (error); } @@ -4840,6 +4887,11 @@ ipfw_destroy(void) { +#ifdef DEV_IPFW + ether_ifdetach(ifn); + if_free(ifn); + ifn = NULL; +#endif uma_zdestroy(ipfw_dyn_rule_zone); IPFW_DYN_LOCK_DESTROY(); printf("IP firewall unloaded\n"); From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 03:35:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 938AE1065670; Tue, 15 Dec 2009 03:35:44 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id A26078FC0A; Tue, 15 Dec 2009 03:35:43 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so91907eyf.9 for ; Mon, 14 Dec 2009 19:35:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=jF2Cx2SUeLSfYMEe5CPUdoDuEolsDT4e11FjTAxfeDs=; b=HW7rib8+6OIeViKOSY9n3Mm9cJSuVCmxNfjyiSfOcKPMIxhoiLj692l0wBxFoBKYYU QDDaHa9D9saBmlCat962GF0/PYhzWAL1B4V+AQksjKh7jTEIcsWJ4UNE7WdxX7R4X4XC cK8vUQ72R9Y3JR7at8FsLUORaRLUNZB0BGxEQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=v2sSzD861RQ13HP+hp6ubUVvq14YICE/KQ87mqiWWtF6BeSieTN5QN+atv0/zjyxtu rJr/gOrXh3e18ecMjuN9IZgRBjdsIbQx7HdGIcj8X+ecm0U1AqZrd0u8jow3K0Kwx0gz 7Y0sn95WGDNusxAI8jA/386qM3lVh1wxwRJmo= MIME-Version: 1.0 Received: by 10.216.90.1 with SMTP id d1mr2568107wef.136.1260848142386; Mon, 14 Dec 2009 19:35:42 -0800 (PST) In-Reply-To: <6201873e0912141436j24de325dm45aac38a89bd047c@mail.gmail.com> References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> <4B26A45B.4020302@FreeBSD.org> <6201873e0912141436j24de325dm45aac38a89bd047c@mail.gmail.com> Date: Mon, 14 Dec 2009 22:35:42 -0500 Message-ID: From: "b. f." To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 Cc: mav@FreeBSD.org, Doug Barton , jhb@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 03:35:44 -0000 On 12/14/09, Adam Vande More wrote: > On Mon, Dec 14, 2009 at 2:47 PM, Doug Barton wrote: > >> b. f. wrote: >> > On 12/14/09, Doug Barton wrote: >> >> I did look up the spec sheet on the hard drive last night, and >> although it does mention SATA and NCQ it does not explicitly mention >> AHCI. This isn't surprising, because, as mentioned before, AHCI is largely concerned with the workings of host controllers, and not with most storage devices. It is reassuring to see that the specs agree with our drivers with respect to the NCQ. > > A bit of research leads to believe you are SOL on ahci/NCQ for this system > unless you're able to hack a BIOS. I believe both drive and controller are > capable of running it, but Dell has disabled it as an option for some > reason. > As Adam says, a brief look at the web shows that people have long been complaining about the fact that the BIOS of these machines does not allow users to employ AHCI. If, as you say, Dell hasn't been willing to fix this, then you are left with only a few options: 1) try to find a replacement BIOS ( maybe someone is working on coreboot support for this model? : http://www.coreboot.org/Welcome_to_coreboot ) 2) employ a driver that circumvents the crippled BIOS, and enables AHCI. With regard to 2), there have been a number of hacks for Linux that enable AHCI on these and related machines, with varying degrees of success. See, for example: http://www.mail-archive.com/linux-ide@vger.kernel.org/msg09698.html (and follow-ups!) http://tartarus.org/ds/quirk-ich-force-ahci.patch http://www.codon.org.uk/~mjg59/tmp/hack_ahci http://mjg59.livejournal.com/85504.html Maybe a knowledgeable person, like mav@ or jhb@, could exploit some of these ideas in FreeBSD to allow you and others in similar predicaments to use AHCI on your machines? Regards, b. From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 04:22:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C2C21065672 for ; Tue, 15 Dec 2009 04:22:27 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9578A8FC36 for ; Tue, 15 Dec 2009 04:22:24 +0000 (UTC) Received: (qmail 22855 invoked by uid 399); 15 Dec 2009 04:22:23 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 15 Dec 2009 04:22:23 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B270F08.4060303@FreeBSD.org> Date: Mon, 14 Dec 2009 20:22:32 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: "b. f." References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> <4B26A45B.4020302@FreeBSD.org> <6201873e0912141436j24de325dm45aac38a89bd047c@mail.gmail.com> In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adam Vande More , mav@FreeBSD.org, freebsd-current@freebsd.org, jhb@FreeBSD.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 04:22:27 -0000 b. f. wrote: > Maybe a knowledgeable person, like mav@ or jhb@, could exploit some of > these ideas in FreeBSD to allow you and others in similar predicaments > to use AHCI on your machines? Sounds good to me. :) There wasn't anything that looked promising at coreboot, and a cursory search for other BIOS sources didn't turn up anything either. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 04:03:03 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79CFF1065676; Tue, 15 Dec 2009 04:03:03 +0000 (UTC) (envelope-from barnaclewes@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id 17A228FC0C; Tue, 15 Dec 2009 04:03:02 +0000 (UTC) Received: by qyk6 with SMTP id 6so1842948qyk.3 for ; Mon, 14 Dec 2009 20:03:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=321b1/YvBz7yTRlNrOZ7GQk6CY1CNTfw1NvE06uptHA=; b=idtP9IjjzhbZI4vmULM4nRWiSpvg2fnU4X+NMYEhGnJAguug+MdwC0ku8xJb0/WkAd oqWt/WCxfmZow4jWT+SLmSZ/nHXy+muG0KyCb/zyHmq8EgOuk0xGankPUJE5K81RHFVp y7C/4vnhLOEKkmrujAzvzsDG32RiTQf2SjHgA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=FFQ2SybH9QyS+VuYig69BNNzxua59q3QlHQSWcpAXGvwx48CTuRO7+6qEViLsJ31Tz c7tybOymZUFBOb7EujVrIER+KXirkat0m2cRMUsor7ws8CAYMxHQMh9/lUaUSXZS7cf4 VjN9dQaL1OLOdOlaQgLveNS9D1KT8T6DXq+cU= MIME-Version: 1.0 Received: by 10.224.43.160 with SMTP id w32mr3549565qae.277.1260847975692; Mon, 14 Dec 2009 19:32:55 -0800 (PST) In-Reply-To: <86d42hmu1o.fsf@ds4.des.no> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> Date: Mon, 14 Dec 2009 19:32:55 -0800 Message-ID: From: Wes Peters To: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 15 Dec 2009 04:28:31 +0000 Cc: freebsd-current@freebsd.org, Anton Shterenlikht , Bill Moran , Borja Marcos , Matthew Seaman , "Sam Fourman Jr." , Svein Skogen , Polytropon , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 04:03:03 -0000 2009/12/14 Dag-Erling Sm=F8rgrav : > Borja Marcos writes: >> http://ietfdocs.potaroo.net/rfc/rfc1791.txt > > Priceless! > >> I remember that around the early 90's =A0I read one of those peecee >> magazine authors (maybe Jerry Pournelle) asking the IETF to, please, >> drop that TCP/IP thingy and instead choose a standard, widely used >> protocol for the Internet: IPX. > > Umm, is IPX even routable? Yup, it sure is. Xylan had IPX routing in their switch/routers when I worked there, done by the same group that did IP routing. It was bugly. --=20 Against stupidity the very gods Themselves contend in vain. Friedrich Schiller From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 05:19:29 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0190106568B; Tue, 15 Dec 2009 05:19:29 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id 7BAF48FC13; Tue, 15 Dec 2009 05:19:26 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id D60144C8057; Tue, 15 Dec 2009 06:19:22 +0100 (CET) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id E092C4C805B; Tue, 15 Dec 2009 06:19:19 +0100 (CET) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id nBF5JI1P028942; Tue, 15 Dec 2009 06:19:19 +0100 (CET) From: Thierry Herbelot To: John Baldwin Date: Tue, 15 Dec 2009 06:19:12 +0100 User-Agent: KMail/1.9.10 References: <200912110615.28030.thierry.herbelot@free.fr> <200912141108.48169.jhb@freebsd.org> In-Reply-To: <200912141108.48169.jhb@freebsd.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200912150619.12950.thierry.herbelot@free.fr> Cc: freebsd-current@freebsd.org Subject: Re: Panic in a recent kernel (cardbus/pci related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 05:19:29 -0000 Le Monday 14 December 2009, John Baldwin a écrit : > On Friday 11 December 2009 12:15:27 am Thierry Herbelot wrote: > > Hello, > > > > I'm seeing a panic in my latest -Current kernel (config file == GENERIC > > minus INVARIANTS, WITNESS and SMP). The machine is an older notebook, > > with a PCMCIA network card. > > Can you try reverting the recent change to sys/dev/pci/pci.c to use > resource_list_reserve() just to narrow down if that is the cause? Hello, If I revert this commit, the kernel does boot correctly : 308,309c308,309 < $FreeBSD: src/sys/dev/pci/pci.c,v 1.390 2009/11/25 20:50:43 thompsa Exp $ < $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.60 2009/05/20 22:00:39 imp Exp $ --- > $FreeBSD: src/sys/dev/pci/pci.c,v 1.392 2009/12/10 01:01:53 jkim Exp $ > $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.61 2009/12/10 01:01:53 jkim Exp $ (the diff is an extract from the change in the idents between the last working kernel and the next, non-working one) This commit seems to be about processing ACPI tables : maybe my notebook has a some bad ACPI data ? TfH From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 05:48:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFD80106566B for ; Tue, 15 Dec 2009 05:48:31 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from services.ipt.ru (services.ipt.ru [194.62.233.110]) by mx1.freebsd.org (Postfix) with ESMTP id 9C6818FC1B for ; Tue, 15 Dec 2009 05:48:31 +0000 (UTC) Received: from [85.173.16.213] (helo=izar) by services.ipt.ru with esmtpa (Exim 4.54 (FreeBSD)) id 1NKQGr-0000Jp-LQ; Tue, 15 Dec 2009 08:48:29 +0300 To: "b. f." References: <4B25D1ED.5060509@FreeBSD.org> From: Boris Samorodov Date: Tue, 15 Dec 2009 08:49:17 +0300 In-Reply-To: (b. f.'s message of "Mon\, 14 Dec 2009 01\:14\:05 -0500") Message-ID: <07604338@ipt.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-current@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 05:48:32 -0000 "b. f." writes: > If you use 'pciconf -lv', is the subclass for your SATA controller > listed as either RAID or AHCI? If I'm not mistaken that should be "RAID or SATA". -- WBR, bsam From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 05:55:26 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FAE11065693 for ; Tue, 15 Dec 2009 05:55:26 +0000 (UTC) (envelope-from dhorn2000@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 1CADB8FC14 for ; Tue, 15 Dec 2009 05:55:25 +0000 (UTC) Received: by fxm27 with SMTP id 27so3872962fxm.3 for ; Mon, 14 Dec 2009 21:55:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ONwpmEk2zZOjPj/L+MSHUInJpT9mYOuqgUKUKJSLoAs=; b=RMgIh6ThbSgQL0a8kUmrGfgymIna7125Olb/RkcGU+tQvLBxrISKl031lNJYd3G1x9 S26sDXQT+PrhwdYWcnoYzNOjdhJktcrXcNThcAweFChTDMrtul3zGnPcOzWoYRBnNJAh dIq08ywx7gJiQriQAwygTOjGIroca29dV4htk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=DkSdWJMhk91z9YxxObe2ig5Sk7ejbUt1Vu7E083hERuqmaAi+qXKprf24dosdlrzTC PkSHaJrc6J1cb1vG4lxncXGu59+UmPYi/zeAJpZ6fGD/txLhJM1CJEQKNWau76mZuFYA 4qpnHQHAg1iisd/oJA+gg0yjK3sb+i1JpPHE0= MIME-Version: 1.0 Received: by 10.239.145.163 with SMTP id s35mr610273hba.42.1260854625945; Mon, 14 Dec 2009 21:23:45 -0800 (PST) In-Reply-To: <20091214235307.GA5345@onelab2.iet.unipi.it> References: <20091214235307.GA5345@onelab2.iet.unipi.it> Date: Tue, 15 Dec 2009 00:23:45 -0500 Message-ID: <25ff90d60912142123o661097c1k1b42eb292efd8acf@mail.gmail.com> From: David Horn To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 05:55:26 -0000 On Mon, Dec 14, 2009 at 6:53 PM, Luigi Rizzo wrote: > The following ipfw patch (which i wrote back in 2001/2002) makes > ipfw logging possible through tcpdump -- it works by passing to the > fake device 'ipfw0' all packets matching rules marked 'log' . > The use is very simple -- to test it just do > > =A0 =A0 =A0 =A0ipfw add 100 count log ip from any to any > > and then > > =A0 =A0 =A0 =A0tcpdump -ni ipfw0 > > will show all matching traffic. > > I think this is a quite convenient and flexible option, so if there > are no objections I plan to commit it to head. > > =A0 =A0 =A0 =A0cheers > =A0 =A0 =A0 =A0luigi > > Index: ../head/sys/netinet/ipfw/ip_fw2.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- ../head/sys/netinet/ipfw/ip_fw2.c =A0 (revision 200551) > +++ ../head/sys/netinet/ipfw/ip_fw2.c =A0 (working copy) > @@ -65,6 +65,8 @@ > =A0#include > =A0#include /* for ETHERTYPE_IP */ > =A0#include > +#include =A0 =A0 =A0/* for IFT_ETHER */ > +#include =A0 =A0 =A0 =A0 =A0 /* for BPF */ > =A0#include > =A0#include > =A0#include > @@ -338,6 +340,15 @@ > =A0 =A0 "Enable keepalives for dyn. rules"); > =A0#endif /* SYSCTL_NODE */ > > +#ifdef DEV_IPFW > +static struct ifnet *ifn; =A0 =A0 =A0/* hook to attach to bpf */ > +static int > +ipfw_ifnet_ioctl(struct ifnet *ifp, u_long cmd, caddr_t addr) > +{ > + =A0 =A0 =A0 return EINVAL; > +} > +#endif > + > =A0/* > =A0* L3HDR maps an ipv4 pointer into a layer3 header pointer of type T > =A0* Other macros just cast void * into the appropriate type > @@ -3056,6 +3067,29 @@ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if (V_fw_v= erbose) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0ipfw_log(f, hlen, args, m, > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0oif, offset, tablearg, ip); > +#ifdef DEV_IPFW > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 else if (if= n && ifn->if_bpf !=3D NULL) { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* = This kludge is OK; BPF treats > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= *the "mbuf" as read-only */ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 str= uct m_hdr mh; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mh.= mh_next =3D m; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 mh.= mh_len =3D ETHER_HDR_LEN; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if = (args->eh) =A0 =A0 =A0 /* layer2, complete */ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 mh.mh_data =3D (char *)args->eh; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 els= e { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 /* fake header and restore wire format*/ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 mh.mh_data =3D "DDDDDDSSSSSS\x08\x00"; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ip->ip_off =3D ntohs(ip->ip_off); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ip->ip_len =3D ntohs(ip->ip_len); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 BPF= _MTAP(ifn, (struct mbuf *)&mh); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if = (args->eh =3D=3D NULL) { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 /* restore IP format */ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ip->ip_off =3D htons(ip->ip_off); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 ip->ip_len =3D htons(ip->ip_len); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > +#endif /* DEV_IPFW */ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0match =3D = 1; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0break; > > @@ -4830,6 +4864,19 @@ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0printf("limited to %d packets/entry by def= ault\n", > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0V_verbose_limit); > > +#ifdef DEV_IPFW =A0 =A0 =A0 =A0/** bpf code **/ > + =A0 =A0 =A0 ifn =3D if_alloc(IFT_ETHER); > + =A0 =A0 =A0 if_initname(ifn, "ipfw", 0); > + =A0 =A0 =A0 ifn->if_mtu =3D 65536; > + =A0 =A0 =A0 ifn->if_flags =3D IFF_UP | IFF_SIMPLEX | IFF_MULTICAST; > + =A0 =A0 =A0 ifn->if_ioctl =3D ipfw_ifnet_ioctl; =A0 =A0 =A0 =A0/* getad= dr */ > + =A0 =A0 =A0 ifn->if_addrlen =3D 6; > + =A0 =A0 =A0 ifn->if_hdrlen =3D 14; > + =A0 =A0 =A0 if_attach(ifn); > + =A0 =A0 =A0 ifn->if_baudrate =3D IF_Mbps(10); > + =A0 =A0 =A0 bpfattach(ifn, DLT_EN10MB, 14); > +#endif /** end bpf code **/ > + > =A0 =A0 =A0 =A0return (error); > =A0} > > @@ -4840,6 +4887,11 @@ > =A0ipfw_destroy(void) > =A0{ > > +#ifdef DEV_IPFW > + =A0 =A0 =A0 ether_ifdetach(ifn); > + =A0 =A0 =A0 if_free(ifn); > + =A0 =A0 =A0 ifn =3D NULL; > +#endif > =A0 =A0 =A0 =A0uma_zdestroy(ipfw_dyn_rule_zone); > =A0 =A0 =A0 =A0IPFW_DYN_LOCK_DESTROY(); > =A0 =A0 =A0 =A0printf("IP firewall unloaded\n"); Code works well for me with latest current r200562, although a bit of extra fuzz factor was needed for the patch to apply cleanly. My only comment is that I would prefer a tunable or sysctl to having to recompile with CFLAGS+=3D -DDEV_IPFW added to the ipfw module Makefile. Very useful code. ---Dave Horn From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 09:24:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB90C1065670 for ; Tue, 15 Dec 2009 09:24:52 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 78E248FC16 for ; Tue, 15 Dec 2009 09:24:51 +0000 (UTC) Received: by fxm27 with SMTP id 27so3979409fxm.3 for ; Tue, 15 Dec 2009 01:24:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:organization:to:subject :date:user-agent:mime-version:content-type:content-transfer-encoding :message-id; bh=PS4oCwiPKnzH/NkG7y2XBidXAGpeJtr1TjxR/s1NrA0=; b=fhRCqoD0BlLEnYu9zK/TsWihCu4HbA2cwrIGTm1/yQp25Dks8cvxXy5dcGSKLtK5/I ilxKJrDad9Qjiu+PoUTB+q8/pK3AnQRkTP29cECM37bdbA7gIKtVIWmTtpkj3EbS0I+u ufmbAoBRaTl7Xn4bONwzQ5O+t7nBp4b3iawcQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:organization:to:subject:date:user-agent:mime-version :content-type:content-transfer-encoding:message-id; b=e4yQZLjhpDShsaQOkevAMtJni0SWVsp58A7yUTFM4JQEmZ8m91HTq9h9Wc9ZUAJr2W utlnUgRrbe0J8F0hnV86S+JtHtqAQEmahhQhaL+3JnN5Jc2qQtQ0o+A+YAVYs8fuw2Tv aiXSvguC+iFJacOYNmXS7yohOeAXWcULkOjuQ= Received: by 10.223.54.23 with SMTP id o23mr7142047fag.72.1260869090509; Tue, 15 Dec 2009 01:24:50 -0800 (PST) Received: from dragon.dg ([41.0.54.20]) by mx.google.com with ESMTPS id 16sm1851502fxm.0.2009.12.15.01.24.48 (version=SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 01:24:49 -0800 (PST) From: David Naylor Organization: Private To: freebsd-current@freebsd.org Date: Tue, 15 Dec 2009 11:24:54 +0200 User-Agent: KMail/1.12.3 (FreeBSD/8.0-PRERELEASE; KDE/4.3.3; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1563877.DkulJleLIK"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912151124.58478.naylor.b.david@gmail.com> Subject: [regression] loader stalls on compressed module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 09:24:53 -0000 --nextPart1563877.DkulJleLIK Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, It appears that recently (~6 months) loader can no longer load compressed=20 kernel objects (gzipped) . This regression is present on both FreeBSD-8 an= d - Current. =20 This can be reproduced by doing: # cd /boot/kernel ; gzip -9 unionfs.ko (Choose option 6 from loader and enter: load unionfs) I have experienced this on both i386 and amd64. It appears that loader can= =20 handle a compressed generic kernel (and maybe other modules). =20 Regards David --nextPart1563877.DkulJleLIK Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEABECAAYFAksnVeoACgkQUaaFgP9pFrIBSgCbB0ZkG1Q6CDq6oQV6OOGLx8lV SbQAnR9yztAD47m9NyJ+yDramzpjmPFk =YdVw -----END PGP SIGNATURE----- --nextPart1563877.DkulJleLIK-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 09:36:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A68D106566B; Tue, 15 Dec 2009 09:36:28 +0000 (UTC) (envelope-from barnaclewes@gmail.com) Received: from mail-qy0-f176.google.com (mail-qy0-f176.google.com [209.85.221.176]) by mx1.freebsd.org (Postfix) with ESMTP id C403B8FC13; Tue, 15 Dec 2009 09:36:27 +0000 (UTC) Received: by qyk6 with SMTP id 6so1918398qyk.3 for ; Tue, 15 Dec 2009 01:36:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=VRQ5hyA4Mei9xR4n/Ro5APA/rjty8s96Wudr4XlfkJM=; b=vldV7kt0eFJ4YNGoCPtUzNVcOJNpU2neGaRZhIwrdg0EcsHJai90O//i3SP8C7TKTF M2dwg8tRfjZoeOPF373+kQoa+Mt8UXIuowwEAviYUDXWs/lJ5cTO32MhoaWOk76kqmki DcdnDvrrqBV3he9R0C3Jpm1ge11b26qDK2qPc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=j+mjw6JTf1NZro6TGxvteJEIfZ91ZShxHuHefaIDRWU1JUBaGCiCrbLxYS15wZP/Co ipC+SURCpa6RqTCKPl00CKvCZNOxVX2krswC0OiISPT5SztiHi/NsZ4V9X0JsnQp1kit D+HunXbKkxiodGEvW8lraLZb32n/a5ZkLEbmk= MIME-Version: 1.0 Received: by 10.224.112.5 with SMTP id u5mr3718422qap.362.1260869787033; Tue, 15 Dec 2009 01:36:27 -0800 (PST) In-Reply-To: <20091119004651.7432a6e4.nork@FreeBSD.org> References: <20091119004651.7432a6e4.nork@FreeBSD.org> Date: Tue, 15 Dec 2009 01:36:27 -0800 Message-ID: From: Wes Peters To: Norikatsu Shigemura Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Alexander Motin , freebsd-current@freebsd.org Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 09:36:28 -0000 On Wed, Nov 18, 2009 at 7:46 AM, Norikatsu Shigemura wro= te: > Hi Alexander! > > =A0 =A0 =A0 =A0I have a Intel 64GB SSD(X25-E) and a Western Digital Cavia= r Green > =A0 =A0 =A0 =A01TB HDD (WD10EADS), and use them on ahci(4). =A0ahci(4) ca= n use NCQ > =A0 =A0 =A0 =A0of WD10EADS, but doesn't use NCQ of X25-E. How useful is NCQ on an SSD? Isn't the primary thrust of NCQ to allow the disk to reorder writes to optimize the seek pattern? --=20 Against stupidity the very gods Themselves contend in vain. Friedrich Schiller From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 09:41:56 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9C260106566B for ; Tue, 15 Dec 2009 09:41:56 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id 553E78FC0A for ; Tue, 15 Dec 2009 09:41:56 +0000 (UTC) Received: from c83-253-248-99.bredband.comhem.se ([83.253.248.99]:35032 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1NKTuM-0000yc-5L; Tue, 15 Dec 2009 10:41:33 +0100 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 0176C190F93; Tue, 15 Dec 2009 10:41:29 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Thomas Backman In-Reply-To: Date: Tue, 15 Dec 2009 10:41:27 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <260900B2-1EC8-47F9-B3FE-144943ADEA70@exscape.org> References: <20091119004651.7432a6e4.nork@FreeBSD.org> To: Wes Peters X-Mailer: Apple Mail (2.1077) X-Originating-IP: 83.253.248.99 X-Scan-Result: No virus found in message 1NKTuM-0000yc-5L. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1NKTuM-0000yc-5L 715838d63d3fbb10d60d6eae0ede458b Cc: FreeBSD current Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 09:41:56 -0000 On Dec 15, 2009, at 10:36 AM, Wes Peters wrote: > On Wed, Nov 18, 2009 at 7:46 AM, Norikatsu Shigemura = wrote: >> Hi Alexander! >>=20 >> I have a Intel 64GB SSD(X25-E) and a Western Digital Caviar = Green >> 1TB HDD (WD10EADS), and use them on ahci(4). ahci(4) can use = NCQ >> of WD10EADS, but doesn't use NCQ of X25-E. >=20 > How useful is NCQ on an SSD? Isn't the primary thrust of NCQ to allow > the disk to reorder writes to optimize the seek pattern? http://en.wikipedia.org/wiki/NCQ#NCQ_in_Solid-State_Drives :) Regards, Thmas= From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 09:54:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 41C43106568B; Tue, 15 Dec 2009 09:54:27 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id E16158FC16; Tue, 15 Dec 2009 09:54:26 +0000 (UTC) Received: from [IPv6:::1] (pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.2/8.14.2) with ESMTP id nBF9sJ3a079891; Tue, 15 Dec 2009 02:54:20 -0700 (MST) (envelope-from scottl@samsco.org) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Scott Long In-Reply-To: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> Date: Tue, 15 Dec 2009 02:54:19 -0700 Content-Transfer-Encoding: 7bit Message-Id: <978BBD51-222D-42F0-9D3A-FFACCBCC886D@samsco.org> References: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> To: Alexander Sack X-Mailer: Apple Mail (2.1076) X-Spam-Status: No, score=-4.6 required=3.8 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on pooker.samsco.org Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: aac(4) handling of probe when no devices are there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 09:54:27 -0000 On Dec 14, 2009, at 2:47 PM, Alexander Sack wrote: > Hello Again: > > I guess I have a technical question/concern that I was looking for > feedback. During the probe sequence, aac(4) conditionally responds > to INQUIRY commands depending on target LUN: > > aac_cam.c/aac_cam_complete(): > 532 if (command == INQUIRY) { > 533 if (ccb->ccb_h.status == > CAM_REQ_CMP) { > 534 device = ccb->csio.data_ptr[0] & > 0x1f; > 535 /* > 536 * We want DASD and PROC devices > to only be > 537 * visible through the pass > device. > 538 */ > 539 if ((device == T_DIRECT) || > 540 (device == T_PROCESSOR) || > 541 (sc->flags & > AAC_FLAGS_CAM_PASSONLY)) > 542 ccb->csio.data_ptr[0] = > 543 ((device & 0xe0) | > T_NODEVICE); > 544 } else if (ccb->ccb_h.status == > CAM_SEL_TIMEOUT && > 545 ccb->ccb_h.target_lun != > 0) { > 546 /* fix for INQUIRYs on > Lun>0 */ > 547 ccb->ccb_h.status = > CAM_DEV_NOT_THERE; > 548 } > 549 } > > Why is CAM_DEV_NOT_THERE skipped on LUN 0? In the parallel scsi world, a selection timeout means that all LUNs within the entire target do not (or no longer) exist. So returning CAM_SEL_TIMEOUT for LUN 1 would tell CAM to invalidate LUN 0 as well. If you look higher up in this function, you'll see a note about the error/status codes from the AAC firmware coincidentally matching CAM's status codes. My guess is that somewhere along the line, someone at Adaptec stopped reading the SCSI spec and starting returning CAM_SEL_TIMEOUT for LUNs greater than 0, which is why this work-around is now in the driver. > This is true on my target > 6.1-amd64 machine as well as CURRENT. The reason why I ask this is > because now that aac(4) is sequential scanned, there are a lot of cam > interrupts that come in on my 6.x machine where the threshold is only > 500 and I get the interrupt storm threshold warning for swi2 pretty > quickly: > > Interrupt storm detected on "swi2:"; throttling interrupt source > > Obviously its contingent on the number of adapters you have on your > system. On CURRENT I didn't see this because the threshold is double > (I think its a 1000 by default). > > The issue is the number of xpt_async(AC_LOST_DEVICE, ..) calls during > the scan. The probe sequence in CURRENT as well as 6.1 handles > CAM_SEL_TIMEOUT a little differently depending on context. > It's not at all clear to me what is going on here. Can you instrument the code to record the status of everything that is being issued to the aac_cam module? Scott From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 09:55:06 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D866A1065694 for ; Tue, 15 Dec 2009 09:55:06 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id 8D53E8FC0A for ; Tue, 15 Dec 2009 09:55:06 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id EFE3941C7A5; Tue, 15 Dec 2009 10:55:05 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id 6Foc-XtXGQXA; Tue, 15 Dec 2009 10:55:05 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 8CA6941C7A4; Tue, 15 Dec 2009 10:55:05 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 2CBE34448EC; Tue, 15 Dec 2009 09:51:19 +0000 (UTC) Date: Tue, 15 Dec 2009 09:51:19 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Luigi Rizzo In-Reply-To: <20091214075725.GA80173@onelab2.iet.unipi.it> Message-ID: <20091215095044.J86040@maildrop.int.zabbadoz.net> References: <20091214075725.GA80173@onelab2.iet.unipi.it> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD current mailing list Subject: Re: need clarifications on net/radix.c usage X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 09:55:06 -0000 On Mon, 14 Dec 2009, Luigi Rizzo wrote: Hi Luigi, > Hi, > i am revising the code in net/radix.c and there are a few > things that are not completely clear to me and I would like > to understand and possibly fix. > > I know that this code has been untouched in 15 years so it > probably reflects old requirements or design ideas that have > changed since then. > > Initial list of things: > > - struct radix_node_head has a number of fields that are never used > (rnh_addpkt and friends, rnh_addrsize, rnh_pktsize) > Unless there are objections I'd like to remove the unused fields. > > - there are some static variables in radix.c (max_keylen, mask_rnhead, > the freelist, the allzero and allone masks, 'last_zeroed' in a function) > which would probably deserve becoming members of radix_node_head, > last not least for correctness of operation -- some of those fields > are read-write, but there are now multiple instances of radix_node_head > running under different locks. > Again, if there are no objections, I'd like to move those variables > into radix_node_head. I think the chances to get feedback on this might be better on net@. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 10:10:07 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F636106566B for ; Tue, 15 Dec 2009 10:10:07 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [IPv6:2001:4068:10::3]) by mx1.freebsd.org (Postfix) with ESMTP id 5DA1B8FC12 for ; Tue, 15 Dec 2009 10:10:07 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 9959D41C752; Tue, 15 Dec 2009 11:10:06 +0100 (CET) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([192.168.74.103]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id ee8-NgdzcA+E; Tue, 15 Dec 2009 11:10:06 +0100 (CET) Received: by mail.cksoft.de (Postfix, from userid 66) id 360E841C751; Tue, 15 Dec 2009 11:10:06 +0100 (CET) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 961504448EC; Tue, 15 Dec 2009 10:09:47 +0000 (UTC) Date: Tue, 15 Dec 2009 10:09:47 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Luigi Rizzo In-Reply-To: <20091214235307.GA5345@onelab2.iet.unipi.it> Message-ID: <20091215095440.U86040@maildrop.int.zabbadoz.net> References: <20091214235307.GA5345@onelab2.iet.unipi.it> X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 10:10:07 -0000 On Tue, 15 Dec 2009, Luigi Rizzo wrote: Hi, > The following ipfw patch (which i wrote back in 2001/2002) makes > ipfw logging possible through tcpdump -- it works by passing to the > fake device 'ipfw0' all packets matching rules marked 'log' . > The use is very simple -- to test it just do > > ipfw add 100 count log ip from any to any > > and then > > tcpdump -ni ipfw0 > > will show all matching traffic. > > I think this is a quite convenient and flexible option, so if there > are no objections I plan to commit it to head. pf(4) has pflog(4). Ideally calling it the same would be good though I wonder if two of the the three of our firewalls grow that feature, if we could have a common packet logging device rather than re-doing it for each implementation. Frankly, I haven't looked at the details of the implementation but I found getting rul numbers with tcpdump -e etc. was pretty cool to identify where things were blocked or permitted. Also make sure that the per-VIMAGE interface will work correctly and as expected. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 10:32:33 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E2601106566B for ; Tue, 15 Dec 2009 10:32:33 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 9DE208FC18 for ; Tue, 15 Dec 2009 10:32:33 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id E6C5073098; Tue, 15 Dec 2009 11:39:56 +0100 (CET) Date: Tue, 15 Dec 2009 11:39:56 +0100 From: Luigi Rizzo To: "Bjoern A. Zeeb" Message-ID: <20091215103956.GA14068@onelab2.iet.unipi.it> References: <20091214235307.GA5345@onelab2.iet.unipi.it> <20091215095440.U86040@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091215095440.U86040@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 10:32:34 -0000 On Tue, Dec 15, 2009 at 10:09:47AM +0000, Bjoern A. Zeeb wrote: > On Tue, 15 Dec 2009, Luigi Rizzo wrote: > > Hi, > > >The following ipfw patch (which i wrote back in 2001/2002) makes > >ipfw logging possible through tcpdump -- it works by passing to the > >fake device 'ipfw0' all packets matching rules marked 'log' . > >The use is very simple -- to test it just do > > > > ipfw add 100 count log ip from any to any > > > >and then > > > > tcpdump -ni ipfw0 > > > >will show all matching traffic. > > > >I think this is a quite convenient and flexible option, so if there > >are no objections I plan to commit it to head. > > > pf(4) has pflog(4). Ideally calling it the same would be good though > I wonder if two of the the three of our firewalls grow that feature, > if we could have a common packet logging device rather than re-doing > it for each implementation. > > Frankly, I haven't looked at the details of the implementation but I > found getting rul numbers with tcpdump -e etc. was pretty cool to > identify where things were blocked or permitted. this is something trivial which i have planned already -- stuff 10-12 bytes in the MAC header with rule numbers and actions is surely trivial. Thanks for the pointer to pflog, i'll look at that. > Also make sure that the per-VIMAGE interface will work correctly and > as expected. On this i would like more feedback -- is there anything special that I am supposed to do to create per-vimage interfaces ? Could you look at the code i sent ? "ipfw0" uses the same attach/detach code used by if_tap. cheers luigi > /bz > > -- > Bjoern A. Zeeb It will not break if you know what you are doing. From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 10:35:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5EEB3106566B; Tue, 15 Dec 2009 10:35:40 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with ESMTP id 10CD88FC1E; Tue, 15 Dec 2009 10:35:39 +0000 (UTC) Received: from [192.168.4.11] (unknown [192.168.4.11]) (Authenticated sender: svein) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id 91D1572; Tue, 15 Dec 2009 11:35:40 +0100 (CET) Message-ID: <4B276672.5090407@stillbilde.net> Date: Tue, 15 Dec 2009 11:35:30 +0100 From: "Svein Skogen (Listmail Account)" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> In-Reply-To: <20091215080637.GA8100@rink.nu> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 10:35:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rink Springer wrote: > On Mon, Dec 14, 2009 at 07:32:55PM -0800, Wes Peters wrote: >> 2009/12/14 Dag-Erling Sm?rgrav : >>> Umm, is IPX even routable? >> Yup, it sure is. Xylan had IPX routing in their switch/routers when I >> worked there, done by the same group that did IP routing. It was >> bugly. > > 3Com CoreBuilder's (at least the 3500 model) were also capable of fully > routing IPX. Never tried it though, as IPX was obsoleted by that time > anyway :-) > I cleared out some recipient adresses before answering this... So does the higher featuresets of IOS (Cisco). I've actually done a fair bit of that sort of routing (IPX, DECnet, and whatnot) for a living "back then" before my health gave up on me (landing me on disability pension). As a matter of fact, you could even route NETBEUI if you encapsulated it in something else (and thus i reality bridged it). We did that for a few customers, over frame-relay, as late as 2001 (when I moved on to a different part of the company). Basically, any signal that you can connect to an interface on a router, CAN be routed, provided your NOC team is creative enough. //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg Østli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksnZnIACgkQODUnwSLUlKR4jwCgqiT+aISY+tlUgD0mwlPQwAJp P4QAnimhUag3g63NnVSNkqYDw4LSc2BE =kMty -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 11:16:50 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4FF11065670 for ; Tue, 15 Dec 2009 11:16:50 +0000 (UTC) (envelope-from ache@nagual.pp.ru) Received: from nagual.pp.ru (nagual.pp.ru [194.87.13.69]) by mx1.freebsd.org (Postfix) with ESMTP id 29FD68FC13 for ; Tue, 15 Dec 2009 11:16:49 +0000 (UTC) Received: from nagual.pp.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.14.3/8.14.3) with ESMTP id nBFBGiq6001158; Tue, 15 Dec 2009 14:16:44 +0300 (MSK) (envelope-from ache@nagual.pp.ru) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nagual.pp.ru; s=default; t=1260875804; bh=dH99/QvCbrLO4bf/OAJEk2mpiZlwuq/DeUXaf85dDGs=; l=2058; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=iL9LZukBpS/zNXDo7pc6FoSooqkI/E2t95nSNtCL4psy2jgXCgkP/yt+2s6nxfvvx 8kZldtjEKsRtXWOQ91GdSoRx2hyFy3uTIujxz3AwSSsApjoiPn9skFrbAKak5kokC5 3m+fzjfPdumGSh57F3rZ42DL9gzBrxfmvY/vXGvo= Received: (from ache@localhost) by nagual.pp.ru (8.14.3/8.14.3/Submit) id nBFBGhpt001157; Tue, 15 Dec 2009 14:16:44 +0300 (MSK) (envelope-from ache) Date: Tue, 15 Dec 2009 14:16:43 +0300 From: Andrey Chernov To: Vladimir Grebenschikov Message-ID: <20091215111641.GA1053@nagual.pp.ru> Mail-Followup-To: Andrey Chernov , Vladimir Grebenschikov , Ed Schouten , FreeBSD Current References: <20091111101207.GF64905@hoeg.nl> <20091113060021.GW64905@hoeg.nl> <20091130044130.GA55612@nagual.pp.ru> <1260718402.2505.37.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1260718402.2505.37.camel@localhost> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Ed Schouten , FreeBSD Current Subject: Re: [Heads up] TERM=xterm is now the default (on non-i386) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 11:16:50 -0000 On Sun, Dec 13, 2009 at 06:33:22PM +0300, Vladimir Grebenschikov wrote: > Hi > > Any chance to get it fixed somehow ? It seems Ed does not read his email. I already try to submit this two bugs several times and ways and ask him for confirmation that my mails at least received, but got nothing. I don't know any other channels to contact Ed. If anybody knows please help. > > midnight commander does not work correctly even with no screen-maps, > vidcontrol -T xterm, env TERM=xterm LANG=ru_RU.UTF-8 > > > also, console does not handle correctly multi-byte utf-8 characters > (it should already or not ?) > > > -----Original Message----- > From: Andrey Chernov > To: Ed Schouten > Cc: FreeBSD Current > Subject: Re: [Heads up] TERM=xterm is now the default (on non-i386) > Date: Mon, 30 Nov 2009 07:41:30 +0300 > > On Fri, Nov 13, 2009 at 07:00:21AM +0100, Ed Schouten wrote: > > Hi folks, > > > > I just committed the previously mentioned patch to SVN. Please refer to > > the last part of the commit message to see what you can do when you run > > into trouble. > > It seems xterm emulator can't co-exist with screen maps, namely > vidcontrol -l koi8-r2cp866 > I got Russian letters everywhere instead of vt100 pseudographics due to > missing (i.e. default) ac= termcap capability (f.e. in tzsetup etc.) > There are 2 ways to fix it. > 1) Make separate xterm-r with corrected ac= (that way is ugly). > 2) Don't seek for vt100 pseudographics in loaded font at all, just use > internal kernel font. > Please decide how to fix this better. For now only fallback to '-T cons25' > is solution for Russian users. > > > > -- > Vladimir B. Grebenschikov > vova@fbsd.ru > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- http://ache.pp.ru/ From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 12:16:04 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE023106566C for ; Tue, 15 Dec 2009 12:16:04 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5C3EC8FC0A for ; Tue, 15 Dec 2009 12:16:02 +0000 (UTC) Received: from compute2.internal (compute2.internal [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id C1E98C521E; Tue, 15 Dec 2009 07:16:01 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 15 Dec 2009 07:16:01 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=message-id:date:from:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; s=smtpout; bh=L/TjA0C0qGSsIJ7yw7fVol4kwtE=; b=E74LNbPrm2TbuUBu9vV/MFCpq1lj0o3EFm6V1mEA1zIhwNHeKAi6pEPusgfQswqiIQJav4QUKIqDaAcXaki35MovD7IP2xnk83G8Jq5lxYOQ2AEAeDhMPGSgtVvHmewurEGnuTJwzWhCo0MByKzOvrwivIpAxnVf0iF6tp7KABs= X-Sasl-enc: 1Ekhm8tarOzL26NL04lUo7EYV5bX7Q+AOiAeaOPpCHu3 1260879361 Received: from anglepoise.lon.incunabulum.net (cpc2-dals7-0-0-cust253.hari.cable.virginmedia.com [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id 0E6F94AF3F0; Tue, 15 Dec 2009 07:16:00 -0500 (EST) Message-ID: <4B277DFF.2050704@incunabulum.net> Date: Tue, 15 Dec 2009 12:15:59 +0000 From: Bruce Simpson User-Agent: Thunderbird 2.0.0.23 (X11/20091210) MIME-Version: 1.0 To: "b. f." References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, dougb@FreeBSD.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 12:16:04 -0000 b. f. wrote: > "The main regression of the new mode is a lack of ataraid alternative, to > support cheap BIOS-based ATA RAIDs. If somebody has time and wish to > port that code from inside ata(4) into GEOM module, to make it work over > CAM also, I would appreciate that and propose a help, if needed." > Please search stable@ archives for my bad experiences with ataraid. IMHO, this stuff needs serious attention before it could be considered useful, so the lack of ataraid in the new world order is not that much of a loss, to my mind anyway. cheers, BMS From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 08:06:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0BC01065670 for ; Tue, 15 Dec 2009 08:06:00 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx1.rink.nu (gloom.rink.nu [213.34.49.2]) by mx1.freebsd.org (Postfix) with ESMTP id 663728FC14 for ; Tue, 15 Dec 2009 08:06:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mx1.rink.nu (Postfix) with ESMTP id B1C056D41E; Tue, 15 Dec 2009 09:06:39 +0100 (CET) X-Virus-Scanned: amavisd-new at rink.nu Received: from mx1.rink.nu ([213.34.49.2]) by localhost (gloom.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARXm2-Y3pX3f; Tue, 15 Dec 2009 09:06:37 +0100 (CET) Received: by mx1.rink.nu (Postfix, from userid 1000) id E03E46D423; Tue, 15 Dec 2009 09:06:37 +0100 (CET) Date: Tue, 15 Dec 2009 09:06:37 +0100 From: Rink Springer To: Wes Peters Message-ID: <20091215080637.GA8100@rink.nu> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Mailman-Approved-At: Tue, 15 Dec 2009 12:32:51 +0000 Cc: Polytropon , Bill Moran , Borja Marcos , freebsd-current@freebsd.org, Svein Skogen , "Sam Fourman Jr." , Dag-Erling Sm?rgrav , Matthew Seaman , Anton Shterenlikht , freebsd-questions@freebsd.org Subject: Re: Root exploit for FreeBSD X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 08:06:00 -0000 On Mon, Dec 14, 2009 at 07:32:55PM -0800, Wes Peters wrote: > 2009/12/14 Dag-Erling Sm?rgrav : > > Umm, is IPX even routable? > > Yup, it sure is. Xylan had IPX routing in their switch/routers when I > worked there, done by the same group that did IP routing. It was > bugly. 3Com CoreBuilder's (at least the 3500 model) were also capable of fully routing IPX. Never tried it though, as IPX was obsoleted by that time anyway :-) -- Rink P.W. Springer - http://rink.nu "Beauty often seduces us on the road to truth." - Dr. Wilson From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 14:02:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D053106566B for ; Tue, 15 Dec 2009 14:02:38 +0000 (UTC) (envelope-from pb@fasterix.frmug.org) Received: from fasterix.frmug.org (unknown [IPv6:2a01:e35:8b50:2c40::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5EABD8FC17 for ; Tue, 15 Dec 2009 14:02:37 +0000 (UTC) Received: from fasterix.frmug.org (localhost [127.0.0.1]) by fasterix.frmug.org (8.14.3/8.14.3) with ESMTP id nBFE2Y4v096265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 15 Dec 2009 15:02:34 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.14.3/8.14.3/Submit) id nBFE2YWI096261 for freebsd-current@freebsd.org; Tue, 15 Dec 2009 15:02:34 +0100 (CET) (envelope-from pb) Date: Tue, 15 Dec 2009 15:02:34 +0100 From: Pierre Beyssac To: freebsd-current@freebsd.org Message-ID: <20091215140234.GA94567@fasterix.frmug.org> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091215080637.GA8100@rink.nu> User-Agent: Mutt/1.4.2.3i X-message-flag: Warning! Use of Microsoft Outlook is dangerous and makes your system susceptible to worms and viruses Subject: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 14:02:38 -0000 Hello, Since upgrading my world with a -current built last night, cvsup dumps core on me. Any idea? It is a Intel/ATOM 330 box used in 64bit mode. Everything else on the box runs fixe. Recompiling cvsup + ezm3 didn't fix the problem; neither did trying a libc from October. % cvsup -gs standard-supfile Connected to cvsup3.fr.FreeBSD.org Updating collection src-all/cvs Edit src/sbin/ipfw/ipfw.8 zsh: illegal hardware instruction (core dumped) cvsup -gs standard-supfile % gdb cvsup cvsup.core 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 "amd64-marcel-freebsd"...(no debugging symbols found)... Core was generated by `cvsup'. Program terminated with signal 4, Illegal instruction. Reading symbols from /lib/libz.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /lib/libm.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.5 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000008009ffe2b in gmtime_r () from /lib/libc.so.7 (gdb) where #0 0x00000008009ffe2b in gmtime_r () from /lib/libc.so.7 #1 0x00000008009ff8be in gmtime_r () from /lib/libc.so.7 #2 0x0000000800a00596 in gmtime_r () from /lib/libc.so.7 #3 0x0000000800a007a8 in gmtime_r () from /lib/libc.so.7 #4 0x0000000800a03b98 in time () from /lib/libc.so.7 #5 0x00000008009ff53f in timeoff () from /lib/libc.so.7 #6 0x0000000800a00e17 in gmtime () from /lib/libc.so.7 #7 0x00000000004a643a in calloc () #8 0x000000000043aec7 in ?? () #9 0x0000000000448eaa in ?? () #10 0x0000000000409ece in ?? () #11 0x00000000004191a4 in ?? () #12 0x0000000000417cbe in ?? () #13 0x000000000041529f in ?? () #14 0x0000000000414d7a in ?? () #15 0x000000000049f980 in calloc () #16 0x000000000048fa3d in fnmatch () #17 0x00007fffffffd3c8 in ?? () #18 0x00007fffffffe930 in ?? () #19 0x00007fffffffea20 in ?? () #20 0x00007fffffffea00 in ?? () #21 0x0000000000000000 in ?? () #22 0x0000000000000000 in ?? () #23 0x00001fa00000037f in ?? () #24 0x0000000000000000 in ?? () #25 0x00000000006486c0 in ?? () #26 0x00000000006486c0 in ?? () #27 0x0000000000494d89 in fnmatch () -- Pierre Beyssac pb@fasterix.frmug.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 14:44:28 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8ADFE106566B; Tue, 15 Dec 2009 14:44:28 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 9A45E8FC08; Tue, 15 Dec 2009 14:44:27 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id QAA15111; Tue, 15 Dec 2009 16:44:26 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B27A0C9.4030407@icyb.net.ua> Date: Tue, 15 Dec 2009 16:44:25 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Doug Barton References: <4B25D1ED.5060509@FreeBSD.org> <4B25DA75.5080807@FreeBSD.org> <4B25EC42.4090604@FreeBSD.org> <4B26A45B.4020302@FreeBSD.org> In-Reply-To: <4B26A45B.4020302@FreeBSD.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 14:44:28 -0000 on 14/12/2009 22:47 Doug Barton said the following: > I did look up the spec sheet on the hard drive last night, and > although it does mention SATA and NCQ it does not explicitly mention > AHCI. > http://www.hitachigst.com/tech/techlib.nsf/techdocs/50C8DBC2A315A4C786256F400065B756/$file/7K100_SATA_FINAL_DS.pdf > and > http://www.hitachigst.com/tech/techlib.nsf/products/Travelstar_7K100 > if you're interested. > > I also didn't see any mentions of jumpers on the drive to enable AHCI, > which I was kind of hoping for since that's pretty easy to remove. > AHCI stands for Advanced Host Controller Interface, which means that it has to do with an interface that a controller presents to a host OS, not with an interface between the controller and a drive. OTOH, AHCI is applicable only to SATA controllers. The opposite is not true, though, not all SATA controllers are AHCI. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 15:01:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 696DB1065679; Tue, 15 Dec 2009 15:01:54 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id BC4B58FC15; Tue, 15 Dec 2009 15:01:52 +0000 (UTC) Received: by fxm27 with SMTP id 27so4276779fxm.3 for ; Tue, 15 Dec 2009 07:01:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=B9SSdLWFqt+o9Ex6VvPNyVW6iUQnGR1Lm0B7DRWrbhU=; b=mHbbBgfGSN73B1IBdtleBOTmy4Mg+fI06Ed+RsDdMZyjgntomRSO+6fYgymwohxATk JIiKL+qf5xmCY6alc4HRWKRQl7mQoDKI35z1Eu68HdlWBryq2UevPO1drT5OCAiaENzD E1DbvhHrDswMXMzLvsUsrrEwaF3abYOPqR94c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=eJHTcJeVzF5BDDDOXhpMDa0Yv/8UFSkv0fzxBTDFlNaiDmOjqNd1LQlYvxkHE6u3xZ MpJTCjJ1cAhYwLb9OCQuYbrh/W7NeFKJwqPZ0JkCs+RPhqNVGDMj/iBfAuSXZ9YMOsCo ofrPRb+STER4etYuBtp/fm5n2VIyndvo3opmM= Received: by 10.223.14.140 with SMTP id g12mr1235445faa.50.1260889311944; Tue, 15 Dec 2009 07:01:51 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 13sm1962814fxm.9.2009.12.15.07.01.50 (version=SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 07:01:51 -0800 (PST) Sender: Alexander Motin Message-ID: <4B27A4DC.7070908@FreeBSD.org> Date: Tue, 15 Dec 2009 17:01:48 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Wes Peters References: <20091119004651.7432a6e4.nork@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Norikatsu Shigemura Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 15:01:54 -0000 Wes Peters wrote: > On Wed, Nov 18, 2009 at 7:46 AM, Norikatsu Shigemura wrote: >> I have a Intel 64GB SSD(X25-E) and a Western Digital Caviar Green >> 1TB HDD (WD10EADS), and use them on ahci(4). ahci(4) can use NCQ >> of WD10EADS, but doesn't use NCQ of X25-E. > > How useful is NCQ on an SSD? Isn't the primary thrust of NCQ to allow > the disk to reorder writes to optimize the seek pattern? Many SSDs have several flash channels. Multiple parallel requests running allow controller to effectively use them in parallel. On my OCZ Vertex I am receiving about 30% speedup from using NCQ on many short read requests. If you look into Intel SSD's datasheet, you'll also see that all benchmarks are provided for maximal request queue. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 15:25:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7A24106568F for ; Tue, 15 Dec 2009 15:25:38 +0000 (UTC) (envelope-from baptiste.daroussin@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 325B38FC23 for ; Tue, 15 Dec 2009 15:25:37 +0000 (UTC) Received: by ewy26 with SMTP id 26so4984280ewy.3 for ; Tue, 15 Dec 2009 07:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition :content-transfer-encoding:user-agent; bh=u3qiBmUzz6c/ecwomrjafn9phAgC7PMrdlWCfuSs80s=; b=vjW6YTc1tXMJrCdYYBnjFqdQnPog5O4elom/gxmo1Uj8+fyQUpAWPUjgqTkqQjJXWt yFxzn96bkC2NparXfDZVk0ZRG5mTTcsSnoNaPsPcDsaWEp9hU1mBIKfcLwTNd0spUlav 7ILgX6IaQKXpbdtBWR1EvbJeVLIZaxJLofvBQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:content-transfer-encoding:user-agent; b=u7I3jxwwPxNSujFQFSXDfw7A6Inrn7ds2SJio2xyhc19VbHFC23KPY9MANMHNYLYwC ueK/FOzW/41A75DQEL9arItE0X22+mGnnQvmLse6EJvoQZs7BXp1UWRZgvRtnfFYgE4g XFYkNYLqGyAWR5h6d1/gqndhnAeS1eIimd+no= Received: by 10.213.96.223 with SMTP id i31mr2709980ebn.57.1260888869267; Tue, 15 Dec 2009 06:54:29 -0800 (PST) Received: from wicklow.lan (stc92-3-82-245-249-89.fbx.proxad.net [82.245.249.89]) by mx.google.com with ESMTPS id 15sm3773158ewy.4.2009.12.15.06.54.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 06:54:28 -0800 (PST) Received: from bapt (uid 1001) (envelope-from baptiste.daroussin@gmail.com) id 2a309 by wicklow.lan (DragonFly Mail Agent) Tue, 15 Dec 2009 15:52:43 +0100 Date: Tue, 15 Dec 2009 15:52:43 +0100 From: Baptiste Daroussin To: freebsd-current@freebsd.org Message-ID: <20091215145243.GF1016@wicklow.lan> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="ADZbWkCsHQ7r3kzd" Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Small patches for pkg_add X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 15:25:38 -0000 --ADZbWkCsHQ7r3kzd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I've written a small patch for pkg_install that removes the system call to tar in pkg_add command replacing it by some libarchive code. I'm planning to do some cleanup by time to time sending small patches on pkg_install. My very first goal is to remove most of the system call, and to understand the way the code works, not to rewrite everything. Here is the first patch : - modification of the unpack function to use libarchive to extract data - it does not modify the way things works: it does exactly the same thing without the system call - I also removed two unused function from lib/file.c It is my first patch for src, I don't know the good process for that. Hope to send more patches soon. This is not another attempt to rewrite pkgtools, I just want to improve them the time that people working on the different rewrites finish their work. the patch is join to this mail, or can be found at the following link: http://etoilebsd.net/~bapt/pkgtools-libarchive-patch1.patch regards Bapt --ADZbWkCsHQ7r3kzd Content-Type: text/x-diff; charset=iso-8859-1 Content-Disposition: attachment; filename="pkgtools-libarchive-patch1.patch" Content-Transfer-Encoding: 8bit Index: delete/Makefile =================================================================== --- delete/Makefile (révision 199967) +++ delete/Makefile (copie de travail) @@ -9,6 +9,6 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBMD} -LDADD= ${LIBINSTALL} -lmd +LDADD= ${LIBINSTALL} -lmd -larchive .include Index: create/Makefile =================================================================== --- create/Makefile (révision 199967) +++ create/Makefile (copie de travail) @@ -9,6 +9,6 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBMD} -LDADD= ${LIBINSTALL} -lmd +LDADD= ${LIBINSTALL} -lmd -larchive .include Index: version/Makefile =================================================================== --- version/Makefile (révision 199967) +++ version/Makefile (copie de travail) @@ -9,7 +9,7 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBFETCH} ${LIBMD} -LDADD= ${LIBINSTALL} -lfetch -lmd +LDADD= ${LIBINSTALL} -lfetch -lmd -larchive test: sh ${.CURDIR}/test-pkg_version.sh Index: lib/file.c =================================================================== --- lib/file.c (révision 199967) +++ lib/file.c (copie de travail) @@ -22,10 +22,13 @@ __FBSDID("$FreeBSD$"); #include "lib.h" +#include +#include #include #include #include #include +#include /* Quick check to see if a file exists */ Boolean @@ -293,68 +296,49 @@ } } -/* - * Copy a hierarchy (possibly from dir) to the current directory, or - * if "to" is TRUE, from the current directory to a location someplace - * else. - * - * Though slower, using tar to copy preserves symlinks and everything - * without me having to write some big hairy routine to do it. - */ -void -copy_hierarchy(const char *dir, const char *fname, Boolean to) -{ - char cmd[FILENAME_MAX * 3]; - - if (!to) { - /* If absolute path, use it */ - if (*fname == '/') - dir = "/"; - snprintf(cmd, FILENAME_MAX * 3, "/usr/bin/tar cf - -C %s %s | /usr/bin/tar xpf -", - dir, fname); - } - else - snprintf(cmd, FILENAME_MAX * 3, "/usr/bin/tar cf - %s | /usr/bin/tar xpf - -C %s", - fname, dir); -#ifdef DEBUG - printf("Using '%s' to copy trees.\n", cmd); -#endif - if (system(cmd)) { - cleanup(0); - errx(2, "%s: could not perform '%s'", __func__, cmd); - } -} - /* Unpack a tar file */ int unpack(const char *pkg, const char *flist) { - const char *comp, *cp; - char suff[80]; - - comp = ""; - /* - * Figure out by a crude heuristic whether this or not this is probably - * compressed and whichever compression utility was used (gzip or bzip2). - */ - if (strcmp(pkg, "-")) { - cp = strrchr(pkg, '.'); - if (cp) { - strcpy(suff, cp + 1); - if (strchr(suff, 'z') || strchr(suff, 'Z')) { - if (strchr(suff, 'b')) - comp = "-j"; - else - comp = "-z"; - } - } - } + int r; + bool whole_archive=false; + struct archive *a = archive_read_new(); + struct archive_entry *entry; + const int archive_flags = ARCHIVE_EXTRACT_OWNER| ARCHIVE_EXTRACT_PERM | ARCHIVE_EXTRACT_TIME; + if(flist == NULL) + whole_archive=true; else - comp = "-j"; - if (vsystem("/usr/bin/tar -xp %s -f '%s' %s", comp, pkg, flist ? flist : "")) { - warnx("tar extract of %s failed!", pkg); + if(strlen(flist) == 0) + whole_archive=true; + archive_read_support_compression_all(a); + archive_read_support_format_all(a); + r = archive_read_open_filename(a, pkg, 16384); + if (r != ARCHIVE_OK) { + archive_read_finish(a); return 1; - } + } + if(!whole_archive) { + while ( ( r = archive_read_next_header(a, &entry)) == ARCHIVE_OK) { + if (strcmp(archive_entry_pathname(entry), flist)==0) { + r = archive_read_extract(a, entry, archive_flags); + if (r != ARCHIVE_OK) { + warnx("tar extract of %s failed", pkg); + archive_read_finish(a); + return 1; + } + } else + archive_read_data_skip(a); + } + } else + while ((archive_read_next_header(a, &entry)) == ARCHIVE_OK) { + r = archive_read_extract(a, entry, archive_flags); + if (r != ARCHIVE_OK) { + warnx("tar extract of %s failed", pkg); + archive_read_finish(a); + return 1; + } + } + archive_read_finish(a); return 0; } Index: lib/lib.h =================================================================== --- lib/lib.h (révision 199967) +++ lib/lib.h (copie de travail) @@ -189,7 +189,6 @@ void write_file(const char *, const char *); void copy_file(const char *, const char *, const char *); void move_file(const char *, const char *, const char *); -void copy_hierarchy(const char *, const char *, Boolean); int delete_hierarchy(const char *, Boolean, Boolean); int unpack(const char *, const char *); void format_cmd(char *, int, const char *, const char *, const char *); Index: add/perform.c =================================================================== --- add/perform.c (révision 199967) +++ add/perform.c (copie de travail) @@ -128,7 +128,7 @@ warnx("can't stat package file '%s'", pkg_fullname); goto bomb; } - sprintf(extract_contents, "--fast-read %s", CONTENTS_FNAME); + sprintf(extract_contents, "%s", CONTENTS_FNAME); extract = extract_contents; } else { Index: add/Makefile =================================================================== --- add/Makefile (révision 199967) +++ add/Makefile (copie de travail) @@ -9,6 +9,6 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBFETCH} ${LIBMD} -LDADD= ${LIBINSTALL} -lfetch -lmd +LDADD= ${LIBINSTALL} -lfetch -lmd -larchive .include Index: info/Makefile =================================================================== --- info/Makefile (révision 199967) +++ info/Makefile (copie de travail) @@ -9,6 +9,6 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBFETCH} ${LIBMD} -LDADD= ${LIBINSTALL} -lfetch -lmd +LDADD= ${LIBINSTALL} -lfetch -lmd -larchive .include Index: updating/Makefile =================================================================== --- updating/Makefile (révision 199967) +++ updating/Makefile (copie de travail) @@ -9,6 +9,6 @@ WFORMAT?= 1 DPADD= ${LIBINSTALL} ${LIBFETCH} ${LIBMD} -LDADD= ${LIBINSTALL} -lfetch -lmd +LDADD= ${LIBINSTALL} -lfetch -lmd -larchive .include --ADZbWkCsHQ7r3kzd-- From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 16:43:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FC5D1065696 for ; Tue, 15 Dec 2009 16:43:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 012668FC08 for ; Tue, 15 Dec 2009 16:43:07 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id A898646B0C; Tue, 15 Dec 2009 11:43:06 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id C41348A01B; Tue, 15 Dec 2009 11:43:05 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 15 Dec 2009 09:00:20 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <200912151124.58478.naylor.b.david@gmail.com> In-Reply-To: <200912151124.58478.naylor.b.david@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200912150900.20229.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 15 Dec 2009 11:43:06 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: David Naylor Subject: Re: [regression] loader stalls on compressed module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 16:43:07 -0000 On Tuesday 15 December 2009 4:24:54 am David Naylor wrote: > Hi, > > It appears that recently (~6 months) loader can no longer load compressed > kernel objects (gzipped) . This regression is present on both FreeBSD-8 and - > Current. > > This can be reproduced by doing: > # cd /boot/kernel ; gzip -9 unionfs.ko > (Choose option 6 from loader and enter: load unionfs) > > I have experienced this on both i386 and amd64. It appears that loader can > handle a compressed generic kernel (and maybe other modules). Does a loader from TOT still exhibit this? If you build the loader w/o GPT support (LOADER_NO_GPT or some such, it's in sys/boot/i386/loader/Makefile) does that fix it? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 16:43:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B094106568D for ; Tue, 15 Dec 2009 16:43:10 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0CA178FC08 for ; Tue, 15 Dec 2009 16:43:10 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id B605846B35; Tue, 15 Dec 2009 11:43:09 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id E73778A020; Tue, 15 Dec 2009 11:43:08 -0500 (EST) From: John Baldwin To: Thierry Herbelot Date: Tue, 15 Dec 2009 11:25:45 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) References: <200912110615.28030.thierry.herbelot@free.fr> <200912141108.48169.jhb@freebsd.org> <200912150619.12950.thierry.herbelot@free.fr> In-Reply-To: <200912150619.12950.thierry.herbelot@free.fr> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <200912151125.45856.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 15 Dec 2009 11:43:09 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: freebsd-current@freebsd.org Subject: Re: Panic in a recent kernel (cardbus/pci related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 16:43:10 -0000 On Tuesday 15 December 2009 12:19:12 am Thierry Herbelot wrote: > Le Monday 14 December 2009, John Baldwin a =E9crit : > > On Friday 11 December 2009 12:15:27 am Thierry Herbelot wrote: > > > Hello, > > > > > > I'm seeing a panic in my latest -Current kernel (config file =3D=3D G= ENERIC > > > minus INVARIANTS, WITNESS and SMP). The machine is an older notebook, > > > with a PCMCIA network card. > > > > Can you try reverting the recent change to sys/dev/pci/pci.c to use > > resource_list_reserve() just to narrow down if that is the cause? >=20 > Hello, >=20 > If I revert this commit, the kernel does boot correctly : >=20 > 308,309c308,309 > < $FreeBSD: src/sys/dev/pci/pci.c,v 1.390 2009/11/25 20:50:43 thomps= a Exp=20 > $ > < $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.60 2009/05/20 22:00:39 imp= Exp=20 > $ > --- > > $FreeBSD: src/sys/dev/pci/pci.c,v 1.392 2009/12/10 01:01:53 jkim E= xp $ > > $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.61 2009/12/10 01:01:53 jki= m Exp=20 > $ > (the diff is an extract from the change in the idents between the last wo= rking=20 > kernel and the next, non-working one) >=20 > This commit seems to be about processing ACPI tables : maybe my notebook = has a=20 > some bad ACPI data ? This delta includes two changes to pci.c (1.391 and 1.392). Can you try mo= ving it up so that it applies just 1.391 of pci.c? =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 16:49:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DDAD106566B for ; Tue, 15 Dec 2009 16:49:08 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id 8EE478FC17 for ; Tue, 15 Dec 2009 16:49:07 +0000 (UTC) Received: from [195.4.92.26] (helo=16.mx.freenet.de) by mout0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NKaaA-0005jj-B8; Tue, 15 Dec 2009 17:49:06 +0100 Received: from p57ae2bc1.dip0.t-ipconnect.de ([87.174.43.193]:53603 helo=ernst.jennejohn.org) by 16.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NKaaA-0003P3-44; Tue, 15 Dec 2009 17:49:06 +0100 Date: Tue, 15 Dec 2009 17:49:05 +0100 From: Gary Jennejohn To: Pierre Beyssac Message-ID: <20091215174905.467da401@ernst.jennejohn.org> In-Reply-To: <20091215140234.GA94567@fasterix.frmug.org> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 16:49:08 -0000 On Tue, 15 Dec 2009 15:02:34 +0100 Pierre Beyssac wrote: > Since upgrading my world with a -current built last night, cvsup > dumps core on me. Any idea? > > It is a Intel/ATOM 330 box used in 64bit mode. Everything else on > the box runs fixe. > > Recompiling cvsup + ezm3 didn't fix the problem; neither did trying > a libc from October. > I reported this everal weeks ago but there was never a satisfactory resolution to the problem. One poster (scf@) reported that using a 32-bit binary solves the problem. In my experience running cvsup against a remote server (to keep a local CVS tree up to date) works just fine. Are you also running cvsupd and attaching to it? I've found that not starting cvsupd in /etc/rc.conf and instead starting it without -C in a shell script just before invoking cvsup works, so I use something like this: /usr/local/sbin/cvsupd& sleep 1 /usr/local/bin/cvsup supfile and have localhost in supfile. Otherwise I suggest using csup, which does not exhibit any bugs. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 17:03:31 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 783FD106568F for ; Tue, 15 Dec 2009 17:03:31 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout4.freenet.de (mout4.freenet.de [IPv6:2001:748:100:40::2:6]) by mx1.freebsd.org (Postfix) with ESMTP id F3F308FC1B for ; Tue, 15 Dec 2009 17:03:30 +0000 (UTC) Received: from [195.4.92.13] (helo=3.mx.freenet.de) by mout4.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NKao5-0001Do-Hk; Tue, 15 Dec 2009 18:03:29 +0100 Received: from p57ae2bc1.dip0.t-ipconnect.de ([87.174.43.193]:45971 helo=ernst.jennejohn.org) by 3.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1NKao5-0002RA-7L; Tue, 15 Dec 2009 18:03:29 +0100 Date: Tue, 15 Dec 2009 18:03:27 +0100 From: Gary Jennejohn To: Pierre Beyssac Message-ID: <20091215180327.7cab12aa@ernst.jennejohn.org> In-Reply-To: <20091215174905.467da401@ernst.jennejohn.org> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org> <20091215174905.467da401@ernst.jennejohn.org> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:03:31 -0000 On Tue, 15 Dec 2009 17:49:05 +0100 Gary Jennejohn wrote: > On Tue, 15 Dec 2009 15:02:34 +0100 > Pierre Beyssac wrote: > > > Since upgrading my world with a -current built last night, cvsup > > dumps core on me. Any idea? > > > > It is a Intel/ATOM 330 box used in 64bit mode. Everything else on > > the box runs fixe. > > > > Recompiling cvsup + ezm3 didn't fix the problem; neither did trying > > a libc from October. > > > > I reported this everal weeks ago but there was never a satisfactory > resolution to the problem. > > One poster (scf@) reported that using a 32-bit binary solves the problem. > > In my experience running cvsup against a remote server (to keep a local > CVS tree up to date) works just fine. > > Are you also running cvsupd and attaching to it? > > I've found that not starting cvsupd in /etc/rc.conf and instead starting > it without -C in a shell script just before invoking cvsup works, so > I use something like this: > > /usr/local/sbin/cvsupd& > sleep 1 > /usr/local/bin/cvsup supfile > > and have localhost in supfile. > > Otherwise I suggest using csup, which does not exhibit any bugs. > One very important thing which I forgot to mention was that removing /usr/share/zoneinfo/UTC seems to allow cvsup to run to completion. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 17:05:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24128106568F for ; Tue, 15 Dec 2009 17:05:54 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outU.internet-mail-service.net (outu.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id 078FB8FC1F for ; Tue, 15 Dec 2009 17:05:52 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id 7DC3844441; Tue, 15 Dec 2009 09:05:52 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id AA90B2D6014; Tue, 15 Dec 2009 09:05:51 -0800 (PST) Message-ID: <4B27C1FC.5030800@elischer.org> Date: Tue, 15 Dec 2009 09:06:04 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Luigi Rizzo References: <20091214235307.GA5345@onelab2.iet.unipi.it> <20091215095440.U86040@maildrop.int.zabbadoz.net> <20091215103956.GA14068@onelab2.iet.unipi.it> In-Reply-To: <20091215103956.GA14068@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:05:54 -0000 Luigi Rizzo wrote: > On Tue, Dec 15, 2009 at 10:09:47AM +0000, Bjoern A. Zeeb wrote: >> On Tue, 15 Dec 2009, Luigi Rizzo wrote: >> >> Hi, >> >>> The following ipfw patch (which i wrote back in 2001/2002) makes >>> ipfw logging possible through tcpdump -- it works by passing to the >>> fake device 'ipfw0' all packets matching rules marked 'log' . >>> The use is very simple -- to test it just do >>> >>> ipfw add 100 count log ip from any to any >>> >>> and then >>> >>> tcpdump -ni ipfw0 >>> >>> will show all matching traffic. >>> >>> I think this is a quite convenient and flexible option, so if there >>> are no objections I plan to commit it to head. >> >> pf(4) has pflog(4). Ideally calling it the same would be good though >> I wonder if two of the the three of our firewalls grow that feature, >> if we could have a common packet logging device rather than re-doing >> it for each implementation. >> >> Frankly, I haven't looked at the details of the implementation but I >> found getting rul numbers with tcpdump -e etc. was pretty cool to >> identify where things were blocked or permitted. > > this is something trivial which i have planned already -- stuff > 10-12 bytes in the MAC header with rule numbers and actions > is surely trivial. > > Thanks for the pointer to pflog, i'll look at that. > >> Also make sure that the per-VIMAGE interface will work correctly and >> as expected. > > On this i would like more feedback -- is there anything special > that I am supposed to do to create per-vimage interfaces ? > Could you look at the code i sent ? > "ipfw0" uses the same attach/detach code used by if_tap. I'm not sure we should do everything just because we can. it gives us nothing that we can't already get. you can filter using ipfw netgraph -> netgraph bpf -> ng_socket you can efficiently capture packets with divert (or tee) you can write to pcap files using phk's program. > > cheers > luigi > >> /bz >> >> -- >> Bjoern A. Zeeb It will not break if you know what you are doing. > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 17:19:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5120106566C for ; Tue, 15 Dec 2009 17:19:04 +0000 (UTC) (envelope-from pb@fasterix.frmug.org) Received: from fasterix.frmug.org (unknown [IPv6:2a01:e35:8b50:2c40::2]) by mx1.freebsd.org (Postfix) with ESMTP id 5CDB58FC18 for ; Tue, 15 Dec 2009 17:19:04 +0000 (UTC) Received: from fasterix.frmug.org (localhost [127.0.0.1]) by fasterix.frmug.org (8.14.3/8.14.3) with ESMTP id nBFHJ2oJ014637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Dec 2009 18:19:02 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.14.3/8.14.3/Submit) id nBFHJ2Xc014636; Tue, 15 Dec 2009 18:19:02 +0100 (CET) (envelope-from pb) Date: Tue, 15 Dec 2009 18:19:02 +0100 From: Pierre Beyssac To: Gary Jennejohn Message-ID: <20091215171902.GA13936@fasterix.frmug.org> References: <20091211232356.309C21CC09@ptavv.es.net> <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org> <20091215174905.467da401@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091215174905.467da401@ernst.jennejohn.org> User-Agent: Mutt/1.4.2.3i X-message-flag: Warning! Use of Microsoft Outlook is dangerous and makes your system susceptible to worms and viruses Cc: freebsd-current@freebsd.org Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:19:05 -0000 On Tue, Dec 15, 2009 at 05:49:05PM +0100, Gary Jennejohn wrote: > > Recompiling cvsup + ezm3 didn't fix the problem; neither did trying > > a libc from October. > I reported this everal weeks ago but there was never a satisfactory > resolution to the problem. > > One poster (scf@) reported that using a 32-bit binary solves the problem. Yes, I did that too, a 32bit cvsup binary I copied from another -current machine works. > In my experience running cvsup against a remote server (to keep a local > CVS tree up to date) works just fine. > Are you also running cvsupd and attaching to it? No. I don't have a local server, cvsup is running against a remote server. More info: When running from gdb, the error shows up as SIGSEGV on a callq to an invalid address. Could this be a dynamic link error? Here's a disassembly of the code; actually it seems to be somewhere inside lib/libc/stdtime/localtime:timesub() (called by gmtime_r). Program received signal SIGSEGV, Segmentation fault. 0x00000008009ffe2b in gmtime_r () from /lib/libc.so.7 0x00000008009ffe0b : mov 1364798(%rip),%r14 # 0x800b4d150 <__thr_jtable+90512> 0x00000008009ffe12 : mov %edx,%r13d 0x00000008009ffe15 : mov (%r14),%rax 0x00000008009ffe18 : mov %rax,0xee68(%rsp) 0x00000008009ffe20 : xor %eax,%eax 0x00000008009ffe22 : test %rdi,%rdi 0x00000008009ffe25 : je 0x8009fff80 0x00000008009ffe2b : callq 0x80095b4cc 0x00000008009ffe30 : test %eax,%eax 0x00000008009ffe32 : jne 0x8009fff52 (gdb) print signgam $1 = 0 > Otherwise I suggest using csup, which does not exhibit any bugs. True, I just did that following a private suggestion and it works just fine :-) -- Pierre Beyssac pb@fasterix.frmug.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 17:21:42 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFB431065672 for ; Tue, 15 Dec 2009 17:21:42 +0000 (UTC) (envelope-from pb@fasterix.frmug.org) Received: from fasterix.frmug.org (unknown [IPv6:2a01:e35:8b50:2c40::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4D78D8FC0C for ; Tue, 15 Dec 2009 17:21:42 +0000 (UTC) Received: from fasterix.frmug.org (localhost [127.0.0.1]) by fasterix.frmug.org (8.14.3/8.14.3) with ESMTP id nBFHLfio014889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Dec 2009 18:21:41 +0100 (CET) (envelope-from pb@fasterix.frmug.org) Received: (from pb@localhost) by fasterix.frmug.org (8.14.3/8.14.3/Submit) id nBFHLfVc014888; Tue, 15 Dec 2009 18:21:41 +0100 (CET) (envelope-from pb) Date: Tue, 15 Dec 2009 18:21:41 +0100 From: Pierre Beyssac To: Gary Jennejohn Message-ID: <20091215172141.GB13936@fasterix.frmug.org> References: <864ontolud.fsf@ds4.des.no> <4B262BF9.1010500@stillbilde.net> <86ljh5n1wk.fsf@ds4.des.no> <86d42hmu1o.fsf@ds4.des.no> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org> <20091215174905.467da401@ernst.jennejohn.org> <20091215180327.7cab12aa@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091215180327.7cab12aa@ernst.jennejohn.org> User-Agent: Mutt/1.4.2.3i X-message-flag: Warning! Use of Microsoft Outlook is dangerous and makes your system susceptible to worms and viruses Cc: freebsd-current@freebsd.org Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:21:43 -0000 On Tue, Dec 15, 2009 at 06:03:27PM +0100, Gary Jennejohn wrote: > > Otherwise I suggest using csup, which does not exhibit any bugs. > One very important thing which I forgot to mention was that removing > /usr/share/zoneinfo/UTC seems to allow cvsup to run to completion. Me too! So weird (even though my machine is configured with CET). So the problem definitely seems to be time-related... -- Pierre Beyssac pb@fasterix.frmug.org From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 17:36:47 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C53101065670 for ; Tue, 15 Dec 2009 17:36:47 +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 5DF6A8FC15 for ; Tue, 15 Dec 2009 17:36:47 +0000 (UTC) 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 nBFHadXY029852; Tue, 15 Dec 2009 17:36:39 GMT 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.68) (envelope-from ) id 1NKbKB-0005tq-En; Tue, 15 Dec 2009 17:36:39 +0000 Received: from buffy.york.ac.uk (localhost [127.0.0.1]) by buffy.york.ac.uk (8.14.3/8.14.3) with ESMTP id nBFHadJm063004; Tue, 15 Dec 2009 17:36:39 GMT (envelope-from gavin@FreeBSD.org) Received: (from ga9@localhost) by buffy.york.ac.uk (8.14.3/8.14.3/Submit) id nBFHac79063003; Tue, 15 Dec 2009 17:36:38 GMT (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: Baptiste Daroussin In-Reply-To: <20091215145243.GF1016@wicklow.lan> References: <20091215145243.GF1016@wicklow.lan> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 15 Dec 2009 17:36:38 +0000 Message-Id: <1260898598.9972.1.camel@buffy.york.ac.uk> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: Small patches for pkg_add X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 17:36:47 -0000 On Tue, 2009-12-15 at 15:52 +0100, Baptiste Daroussin wrote: > I've written a small patch for pkg_install that removes the system call to tar > in pkg_add command replacing it by some libarchive code. This is great! It's good to see somebody taking this on. If you get no response within the next day or two, please submit this as a PR (using either send-pr or the web form) - so that this does not get lost. Thanks, Gavin From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 18:10:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08A1710656A6 for ; Tue, 15 Dec 2009 18:10:08 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id D546D8FC12 for ; Tue, 15 Dec 2009 18:10:07 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id nBFIA9lL031279; Tue, 15 Dec 2009 18:10:09 GMT (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id uwusb2hmzkvs77tr8jd6eavg4a; Tue, 15 Dec 2009 18:10:09 +0000 (UTC) (envelope-from kientzle@freebsd.org) Message-ID: <4B27D11C.50206@freebsd.org> Date: Tue, 15 Dec 2009 10:10:36 -0800 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16 MIME-Version: 1.0 To: Baptiste Daroussin References: <20091215145243.GF1016@wicklow.lan> In-Reply-To: <20091215145243.GF1016@wicklow.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Small patches for pkg_add X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 18:10:08 -0000 Baptiste Daroussin wrote: > I've written a small patch for pkg_install that removes the system call to tar > in pkg_add command replacing it by some libarchive code. Great! This looks good, but I have a few suggestions: You should be a little more careful about error handling. In particular, after any failure, archive_error_string(a) will hold an error message that you probably want to print out for the user's benefit. In particular, you should print the error message after a failure of archive_read_open_filename(), archive_read_extract(), or archive_read_next_header(). You can also simplify slightly by omitting calls to archive_read_data_skip() (it's never needed). Tim From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 18:14:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CCAE106566B for ; Tue, 15 Dec 2009 18:14:40 +0000 (UTC) (envelope-from baptiste.daroussin@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 25A278FC08 for ; Tue, 15 Dec 2009 18:14:39 +0000 (UTC) Received: by fg-out-1718.google.com with SMTP id 16so475705fgg.13 for ; Tue, 15 Dec 2009 10:14:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=7xM9YcxKPO/v+eHbGkgbg5wqfAjivd5irAZyLkR0fBQ=; b=vWzJ7hk1FKGzn1FQ2CrkiZ81UqZukYdNBUCjjo96BDBVjQ8wm4zZYhBithvQnh/8WW QdFCqq1IPBNgDEPWDQDSU0vlalJMMCvU2fORW9blyQeb4F0y+i3SsNneHNDrTooeC3YA gZFOlP+ypMrGAjvLnUwKotC00waTz7fN1Ss38= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Ru6Y0W2xDuZCmw1A1dUULiL2JQeMoXvbIZj1evQYznlAE3gqBKdfoqETeDTx5e7dth ClEzsY6NiM1n88AnrQklh5OaA6/cFSZIfbGym3cd8i6lPJSGSC0ZZEQDDo5WwDoyfVvS kTlRNkbzAV7/9V6WqQ1Qrs46qlQTWLk7kzsbI= MIME-Version: 1.0 Received: by 10.87.58.28 with SMTP id l28mr8539083fgk.45.1260900878589; Tue, 15 Dec 2009 10:14:38 -0800 (PST) In-Reply-To: <4B27D11C.50206@freebsd.org> References: <20091215145243.GF1016@wicklow.lan> <4B27D11C.50206@freebsd.org> Date: Tue, 15 Dec 2009 18:14:38 +0000 Message-ID: From: Baptiste Daroussin To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Small patches for pkg_add X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 18:14:40 -0000 > Great! > > This looks good, but I have a few suggestions: > > You should be a little more careful about error handling. > In particular, after any failure, archive_error_string(a) > will hold an error message that you probably want to > print out for the user's benefit. > > In particular, you should print the error message > after a failure of archive_read_open_filename(), > archive_read_extract(), or archive_read_next_header(). > > You can also simplify slightly by omitting calls to > archive_read_data_skip() (it's never needed). > > Tim > Thanks, I'll do that FYI I opened a git for that work : http://git.etoilebsd.net/cgit/pkg_install/ I'll add what you advice me todo regards, Bapt From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 18:52:01 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F093B1065672 for ; Tue, 15 Dec 2009 18:52:01 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id B44AC8FC15 for ; Tue, 15 Dec 2009 18:52:01 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 2E8DC73098; Tue, 15 Dec 2009 19:59:26 +0100 (CET) Date: Tue, 15 Dec 2009 19:59:26 +0100 From: Luigi Rizzo To: Julian Elischer Message-ID: <20091215185926.GA19841@onelab2.iet.unipi.it> References: <20091214235307.GA5345@onelab2.iet.unipi.it> <20091215095440.U86040@maildrop.int.zabbadoz.net> <20091215103956.GA14068@onelab2.iet.unipi.it> <4B27C1FC.5030800@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B27C1FC.5030800@elischer.org> User-Agent: Mutt/1.4.2.3i Cc: "Bjoern A. Zeeb" , FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 18:52:02 -0000 On Tue, Dec 15, 2009 at 09:06:04AM -0800, Julian Elischer wrote: > Luigi Rizzo wrote: ... > >>>The following ipfw patch (which i wrote back in 2001/2002) makes > >>>ipfw logging possible through tcpdump -- it works by passing to the > >>>fake device 'ipfw0' all packets matching rules marked 'log' . > >>>The use is very simple -- to test it just do > >>> > >>> ipfw add 100 count log ip from any to any > >>> > >>>and then > >>> > >>> tcpdump -ni ipfw0 > >>> > >>>will show all matching traffic. > >>> > >>>I think this is a quite convenient and flexible option, so if there > >>>are no objections I plan to commit it to head. ... > I'm not sure we should do everything just because we can. > it gives us nothing that we can't already get. you can filter using > ipfw netgraph -> netgraph bpf -> ng_socket > you can efficiently capture packets with divert (or tee) > you can write to pcap files using phk's program. it's not "because we can", it is "because it costs almost nothing and gives new functionality". The cost is just 30 lines of code (including comments) and one extra compare on matching packets (those for which you already enabled the 'log' option, so were prepared to pay the price of logging. Most importantly, you don't need to change the existing ipfw configs. That is, in my opinion, the main advantage. cheers luigi From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 19:03:02 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 152D5106568B for ; Tue, 15 Dec 2009 19:03:02 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id CF0638FC22 for ; Tue, 15 Dec 2009 19:03:01 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 4E5C973098; Tue, 15 Dec 2009 20:10:26 +0100 (CET) Date: Tue, 15 Dec 2009 20:10:26 +0100 From: Luigi Rizzo To: "Bjoern A. Zeeb" Message-ID: <20091215191026.GB19841@onelab2.iet.unipi.it> References: <20091214235307.GA5345@onelab2.iet.unipi.it> <20091215095440.U86040@maildrop.int.zabbadoz.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091215095440.U86040@maildrop.int.zabbadoz.net> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 19:03:02 -0000 On Tue, Dec 15, 2009 at 10:09:47AM +0000, Bjoern A. Zeeb wrote: > On Tue, 15 Dec 2009, Luigi Rizzo wrote: > > Hi, > > >The following ipfw patch (which i wrote back in 2001/2002) makes > >ipfw logging possible through tcpdump -- it works by passing to the > >fake device 'ipfw0' all packets matching rules marked 'log' . > >The use is very simple -- to test it just do ... > pf(4) has pflog(4). Ideally calling it the same would be good though > I wonder if two of the the three of our firewalls grow that feature, > if we could have a common packet logging device rather than re-doing > it for each implementation. > > Frankly, I haven't looked at the details of the implementation but I > found getting rul numbers with tcpdump -e etc. was pretty cool to > identify where things were blocked or permitted. i checked pflog sources (contrib/pf/net/if_pflog.c) and it is almost exactly the same thing i am doing, plus a handful of lines to prepend a header with the metadata. The main function, pflog_packet(), is so short and simple that it would probably deserve going somewhere in if_ethersubr.c or bpf.c so we can use it more easily. cheers luigi From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 19:57:54 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3C08106566B; Tue, 15 Dec 2009 19:57:54 +0000 (UTC) (envelope-from thierry.herbelot@free.fr) Received: from smtp4-g21.free.fr (smtp4-g21.free.fr [212.27.42.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9FB6B8FC2B; Tue, 15 Dec 2009 19:57:51 +0000 (UTC) Received: from smtp4-g21.free.fr (localhost [127.0.0.1]) by smtp4-g21.free.fr (Postfix) with ESMTP id 3CD094C8095; Tue, 15 Dec 2009 20:57:47 +0100 (CET) Received: from mail.herbelot.nom (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp4-g21.free.fr (Postfix) with ESMTP id 448274C80B9; Tue, 15 Dec 2009 20:57:45 +0100 (CET) Received: from tulipe.herbelot.nom (tulipe.herbelot.nom [192.168.2.5]) by mail.herbelot.nom (8.14.1/8.14.1) with ESMTP id nBFJvgXL007240; Tue, 15 Dec 2009 20:57:42 +0100 (CET) From: Thierry Herbelot To: John Baldwin Date: Tue, 15 Dec 2009 20:57:36 +0100 User-Agent: KMail/1.9.10 References: <200912110615.28030.thierry.herbelot@free.fr> <200912150619.12950.thierry.herbelot@free.fr> <200912151125.45856.jhb@freebsd.org> In-Reply-To: <200912151125.45856.jhb@freebsd.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200912152057.36875.thierry.herbelot@free.fr> Cc: freebsd-current@freebsd.org Subject: Re: Panic in a recent kernel (cardbus/pci related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 19:57:54 -0000 Le Tuesday 15 December 2009, John Baldwin a écrit : > On Tuesday 15 December 2009 12:19:12 am Thierry Herbelot wrote: > > Le Monday 14 December 2009, John Baldwin a écrit : > > > On Friday 11 December 2009 12:15:27 am Thierry Herbelot wrote: > > > > Hello, > > > > > > > > I'm seeing a panic in my latest -Current kernel (config file == > > > > GENERIC minus INVARIANTS, WITNESS and SMP). The machine is an older > > > > notebook, with a PCMCIA network card. > > > > > > Can you try reverting the recent change to sys/dev/pci/pci.c to use > > > resource_list_reserve() just to narrow down if that is the cause? > > > > Hello, > > > > If I revert this commit, the kernel does boot correctly : > > > > 308,309c308,309 > > < $FreeBSD: src/sys/dev/pci/pci.c,v 1.390 2009/11/25 20:50:43 > > thompsa Exp $ > > < $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.60 2009/05/20 22:00:39 imp > > Exp $ > > --- > > > > > $FreeBSD: src/sys/dev/pci/pci.c,v 1.392 2009/12/10 01:01:53 jkim > > > Exp $ $FreeBSD: src/sys/dev/pci/pci_pci.c,v 1.61 2009/12/10 01:01:53 > > > jkim Exp > > > > $ > > (the diff is an extract from the change in the idents between the last > > working kernel and the next, non-working one) > > > > This commit seems to be about processing ACPI tables : maybe my notebook > > has a some bad ACPI data ? > > This delta includes two changes to pci.c (1.391 and 1.392). Can you try > moving it up so that it applies just 1.391 of pci.c? indeed, with revision 1.391, the panic also happens (with the same backtrace as the one I posted Friday) TfH From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 20:14:36 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49E751065676; Tue, 15 Dec 2009 20:14:36 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 21D428FC15; Tue, 15 Dec 2009 20:14:35 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nBFKEZF8060322; Tue, 15 Dec 2009 15:14:35 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nBFKEZdf060318; Tue, 15 Dec 2009 20:14:35 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 15 Dec 2009 20:14:35 GMT Message-Id: <200912152014.nBFKEZdf060318@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 20:14:36 -0000 TB --- 2009-12-15 19:05:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-12-15 19:05:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-12-15 19:05:00 - cleaning the object tree TB --- 2009-12-15 19:05:22 - cvsupping the source tree TB --- 2009-12-15 19:05:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-12-15 19:05:57 - building world TB --- 2009-12-15 19:05:57 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 19:05:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 19:05:57 - TARGET=pc98 TB --- 2009-12-15 19:05:57 - TARGET_ARCH=i386 TB --- 2009-12-15 19:05:57 - TZ=UTC TB --- 2009-12-15 19:05:57 - __MAKE_CONF=/dev/null TB --- 2009-12-15 19:05:57 - cd /src TB --- 2009-12-15 19:05:57 - /usr/bin/make -B buildworld >>> World build started on Tue Dec 15 19:05:58 UTC 2009 >>> 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 Tue Dec 15 20:05:07 UTC 2009 TB --- 2009-12-15 20:05:07 - generating LINT kernel config TB --- 2009-12-15 20:05:07 - cd /src/sys/pc98/conf TB --- 2009-12-15 20:05:07 - /usr/bin/make -B LINT TB --- 2009-12-15 20:05:07 - building LINT kernel TB --- 2009-12-15 20:05:07 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 20:05:07 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 20:05:07 - TARGET=pc98 TB --- 2009-12-15 20:05:07 - TARGET_ARCH=i386 TB --- 2009-12-15 20:05:07 - TZ=UTC TB --- 2009-12-15 20:05:07 - __MAKE_CONF=/dev/null TB --- 2009-12-15 20:05:07 - cd /src TB --- 2009-12-15 20:05:07 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Dec 15 20:05:07 UTC 2009 >>> 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ip_input.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ipfw.c /src/sys/netgraph/ng_ipfw.c: In function 'ng_ipfw_input': /src/sys/netgraph/ng_ipfw.c:275: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:295: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:296: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:297: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:299: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-12-15 20:14:35 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-12-15 20:14:35 - ERROR: failed to build lint kernel TB --- 2009-12-15 20:14:35 - 3084.53 user 703.38 system 4174.45 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 20:16:11 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B99A106566C; Tue, 15 Dec 2009 20:16:11 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 05B4F8FC18; Tue, 15 Dec 2009 20:16:10 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nBFKGAY7076404; Tue, 15 Dec 2009 15:16:10 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nBFKGAfT076393; Tue, 15 Dec 2009 20:16:10 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 15 Dec 2009 20:16:10 GMT Message-Id: <200912152016.nBFKGAfT076393@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 20:16:11 -0000 TB --- 2009-12-15 19:05:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-12-15 19:05:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-12-15 19:05:00 - cleaning the object tree TB --- 2009-12-15 19:05:24 - cvsupping the source tree TB --- 2009-12-15 19:05:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-12-15 19:05:57 - building world TB --- 2009-12-15 19:05:57 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 19:05:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 19:05:57 - TARGET=i386 TB --- 2009-12-15 19:05:57 - TARGET_ARCH=i386 TB --- 2009-12-15 19:05:57 - TZ=UTC TB --- 2009-12-15 19:05:57 - __MAKE_CONF=/dev/null TB --- 2009-12-15 19:05:57 - cd /src TB --- 2009-12-15 19:05:57 - /usr/bin/make -B buildworld >>> World build started on Tue Dec 15 19:05:58 UTC 2009 >>> 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 Tue Dec 15 20:05:09 UTC 2009 TB --- 2009-12-15 20:05:09 - generating LINT kernel config TB --- 2009-12-15 20:05:09 - cd /src/sys/i386/conf TB --- 2009-12-15 20:05:09 - /usr/bin/make -B LINT TB --- 2009-12-15 20:05:10 - building LINT kernel TB --- 2009-12-15 20:05:10 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 20:05:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 20:05:10 - TARGET=i386 TB --- 2009-12-15 20:05:10 - TARGET_ARCH=i386 TB --- 2009-12-15 20:05:10 - TZ=UTC TB --- 2009-12-15 20:05:10 - __MAKE_CONF=/dev/null TB --- 2009-12-15 20:05:10 - cd /src TB --- 2009-12-15 20:05:10 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Dec 15 20:05:10 UTC 2009 >>> 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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ip_input.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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ipfw.c /src/sys/netgraph/ng_ipfw.c: In function 'ng_ipfw_input': /src/sys/netgraph/ng_ipfw.c:275: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:295: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:296: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:297: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:299: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-12-15 20:16:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-12-15 20:16:10 - ERROR: failed to build lint kernel TB --- 2009-12-15 20:16:10 - 3190.10 user 693.29 system 4269.71 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 20:42:31 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F0E3106566B; Tue, 15 Dec 2009 20:42:31 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 48D5D8FC13; Tue, 15 Dec 2009 20:42:30 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id nBFKgUfG093375; Tue, 15 Dec 2009 15:42:30 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id nBFKgUYr093373; Tue, 15 Dec 2009 20:42:30 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 15 Dec 2009 20:42:30 GMT Message-Id: <200912152042.nBFKgUYr093373@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 20:42:31 -0000 TB --- 2009-12-15 19:05:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-12-15 19:05:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-12-15 19:05:00 - cleaning the object tree TB --- 2009-12-15 19:05:26 - cvsupping the source tree TB --- 2009-12-15 19:05:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-12-15 19:06:03 - building world TB --- 2009-12-15 19:06:03 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 19:06:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 19:06:03 - TARGET=amd64 TB --- 2009-12-15 19:06:03 - TARGET_ARCH=amd64 TB --- 2009-12-15 19:06:03 - TZ=UTC TB --- 2009-12-15 19:06:03 - __MAKE_CONF=/dev/null TB --- 2009-12-15 19:06:03 - cd /src TB --- 2009-12-15 19:06:03 - /usr/bin/make -B buildworld >>> World build started on Tue Dec 15 19:06:03 UTC 2009 >>> 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 >>> World build completed on Tue Dec 15 20:32:01 UTC 2009 TB --- 2009-12-15 20:32:01 - generating LINT kernel config TB --- 2009-12-15 20:32:01 - cd /src/sys/amd64/conf TB --- 2009-12-15 20:32:01 - /usr/bin/make -B LINT TB --- 2009-12-15 20:32:01 - building LINT kernel TB --- 2009-12-15 20:32:01 - MAKEOBJDIRPREFIX=/obj TB --- 2009-12-15 20:32:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-12-15 20:32:01 - TARGET=amd64 TB --- 2009-12-15 20:32:01 - TARGET_ARCH=amd64 TB --- 2009-12-15 20:32:01 - TZ=UTC TB --- 2009-12-15 20:32:01 - __MAKE_CONF=/dev/null TB --- 2009-12-15 20:32:01 - cd /src TB --- 2009-12-15 20:32:01 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue Dec 15 20:32:01 UTC 2009 >>> 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 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ip_input.c cc -c -O2 -frename-registers -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=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/netgraph/ng_ipfw.c /src/sys/netgraph/ng_ipfw.c: In function 'ng_ipfw_input': /src/sys/netgraph/ng_ipfw.c:275: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:295: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:296: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:297: error: dereferencing pointer to incomplete type /src/sys/netgraph/ng_ipfw.c:299: error: dereferencing pointer to incomplete type *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-12-15 20:42:30 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-12-15 20:42:30 - ERROR: failed to build lint kernel TB --- 2009-12-15 20:42:30 - 4324.87 user 966.93 system 5849.71 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Tue Dec 15 23:37:18 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34FA6106566C; Tue, 15 Dec 2009 23:37:18 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id 19CFC8FC13; Tue, 15 Dec 2009 23:37:18 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id nBFNbHq6020534; Tue, 15 Dec 2009 15:37:17 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 15 Dec 2009 15:37:06 -0800 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: net/mpd5, ppp, proxy-arp issues Thread-Index: Acp934LhgJ2LhcpOScatB1tE2Gb5UQ== From: "Li, Qing" To: , Cc: Qing Li , freebsd-current@freebsd.org Subject: net/mpd5, ppp, proxy-arp issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Dec 2009 23:37:18 -0000 Hi, Recently there have been several reports regarding issues with ppp, mpd5 and proxy-arp configuration over the ppp links. I read through the various postings and the problems seem to be: 1. Unable to add proxy-arp entries for the remote ppp clients. 2. Log showing "ifa_add_loopback_route: insertion failed" causing=20 some userland applications to fail. May I ask that you try applying patch http://people.freebsd.org/~qingli/ppp-proxy-arp-patch-121515.diff and report back if the patch fixes your problems. And if not,=20 please describe what additional issues you are having. Thanks, -- Qing From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 00:51:15 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A37D106568F; Wed, 16 Dec 2009 00:51:15 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (uffner.com [66.208.243.25]) by mx1.freebsd.org (Postfix) with ESMTP id 5424E8FC1C; Wed, 16 Dec 2009 00:51:14 +0000 (UTC) Received: from xiombarg.uffner.com (static-71-162-143-94.phlapa.fios.verizon.net [71.162.143.94]) (authenticated bits=0) by eris.uffner.com (8.14.3/8.14.3) with ESMTP id nBG0rFjM095115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 15 Dec 2009 19:53:28 -0500 (EST) (envelope-from tom@uffner.com) Message-ID: <4B282EF3.8050008@uffner.com> Date: Tue, 15 Dec 2009 19:50:59 -0500 From: Tom Uffner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20090925 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Alexander Motin References: <4B1671EE.1010301@FreeBSD.org> <4B25AE1A.80206@uffner.com> <4B262BAC.9040808@FreeBSD.org> In-Reply-To: <4B262BAC.9040808@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 00:51:15 -0000 Alexander Motin wrote: > Tom Uffner wrote: >> this change breaks my Promise SATA card > > Are you sure that it was this change? > >> atapci0: port >> 0xdc00-0xdc7f,0xd800-0xd8ff mem >> 0xfeaff000-0xfeafffff,0xfeac0000-0xfeadffff irq 23 at device 11.0 on pci2 >> >> kernels from after the commit on 12/6 are unable to mount my drives. >> i get (from memory, since i can't even get to single user mode) >> WARNING - READ_DMA UDMA ICRC error >> followed by lots of SETFEATURE foo errors then a READ_DMA timeout >> followed by a bus reset and the cycle repeats... >> >> before this commit it worked fine. > > How long ago? kernel built from cvs update to D2009.12.05.05.00.00 boots & works fine. kernels from cvs updates after the dev/ata commit on 12/6 can not mount my ufs partitions in either legacy or w/ options ATA_CAM >> this is in the legacy mode. i am building a kernel with "options ATA_CAM" >> now > > OK. Tell me if there any difference. > > Send me please full _verbose_ dmesg with original kernel and if possible > with new. If you can't get full with new, enable verbose messages and > make screenshots of drives detection and first errors. here is verbose dmesg from kernel built w/ sources updated to 12/5/2009 at midnight EST: http://xiombarg.uffner.com/dmesg_20091205.txt as soon as i can set up another PC & serial console i'll get you a verbose boot from new kernel. tom From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 02:27:51 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E64E41065679; Wed, 16 Dec 2009 02:27:51 +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 4B2BF8FC13; Wed, 16 Dec 2009 02:27:50 +0000 (UTC) Received: from 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 nBG2RSL4009201 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 Dec 2009 12:57:28 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 16 Dec 2009 12:57:24 +1030 User-Agent: KMail/1.9.10 References: <4B277DFF.2050704@incunabulum.net> In-Reply-To: <4B277DFF.2050704@incunabulum.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart7834404.hAK4hRMSN6"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912161257.26844.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: Bruce Simpson , "b. f." , dougb@freebsd.org Subject: Re: AHCI/ATA_CAM for dummies? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 02:27:52 -0000 --nextPart7834404.hAK4hRMSN6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tue, 15 Dec 2009, Bruce Simpson wrote: > b. f. wrote: > > "The main regression of the new mode is a lack of ataraid > > alternative, to support cheap BIOS-based ATA RAIDs. If somebody has > > time and wish to port that code from inside ata(4) into GEOM > > module, to make it work over CAM also, I would appreciate that and > > propose a help, if needed." > > Please search stable@ archives for my bad experiences with ataraid. > > IMHO, this stuff needs serious attention before it could be > considered useful, so the lack of ataraid in the new world order is > not that much of a loss, to my mind anyway. It worked well in 4.x in my experience, but I had issues with 6.x and=20 switched to "real" (3ware) RAID cards after that. That said even in 4.x you could get spontaneous splits which was quite=20 annoying. 6.x would do things like pick the "wrong" side of the mirror (ie one=20 that is out of date) which causes hilarity to ensue when you find data=20 for the last week has gone away.. =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 --nextPart7834404.hAK4hRMSN6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD4DBQBLKEWO5ZPcIHs/zowRAouMAJYhbsUvsOK7Lgrdug60gk0eD0hIAJ9URroN RxUkFx+s5PLu2qbu6xriUQ== =M0nN -----END PGP SIGNATURE----- --nextPart7834404.hAK4hRMSN6-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 02:30:28 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B518D1065670 for ; Wed, 16 Dec 2009 02:30:27 +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 34F1F8FC15 for ; Wed, 16 Dec 2009 02:30:26 +0000 (UTC) Received: from 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 nBG2UDa1009482 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 Dec 2009 13:00:13 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Wed, 16 Dec 2009 13:00:10 +1030 User-Agent: KMail/1.9.10 References: <20091211232356.309C21CC09@ptavv.es.net> <20091215080637.GA8100@rink.nu> <20091215140234.GA94567@fasterix.frmug.org> In-Reply-To: <20091215140234.GA94567@fasterix.frmug.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1725120.1vkPBffIGA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912161300.11703.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: Pierre Beyssac Subject: Re: "illegal hardware instruction (core dumped)" cvsup/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 02:30:28 -0000 --nextPart1725120.1vkPBffIGA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wed, 16 Dec 2009, Pierre Beyssac wrote: > Since upgrading my world with a -current built last night, cvsup > dumps core on me. Any idea? Please don't thread hijack, it breaks the flow of conversation and is=20 annoying. ie don't just pick some random message and hit reply then change the=20 subject etc.. Your mail client adds headers which cause it to appear as=20 part of the original thread even though the subject has changed (this=20 is a feature) =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 --nextPart1725120.1vkPBffIGA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLKEYz5ZPcIHs/zowRAtXPAJ9+ak6VyCQKmDcU84aj29mzOXnO/wCfdm7k n7bVvAtfPSETgQIVoXFCan8= =Bb3z -----END PGP SIGNATURE----- --nextPart1725120.1vkPBffIGA-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 03:45:38 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E59F1065670 for ; Wed, 16 Dec 2009 03:45:38 +0000 (UTC) (envelope-from gleb.kurtsou@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 871B08FC08 for ; Wed, 16 Dec 2009 03:45:37 +0000 (UTC) Received: by fxm27 with SMTP id 27so557306fxm.3 for ; Tue, 15 Dec 2009 19:45:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=K3lidzHrTbJW2/OPpFyoph+PzzyR3/bWlfcgRRl9pwU=; b=N0i5KNBqL0EZsjvU/hrx92KSoBNuDagtsKE+Po8IdiS74rj2NIOP9y47kQ2JYZsCuG WiI97SXwWiD61sLVLkiGaFaxDcCgI4lLW/dOuqQSmYByZUjN6ekonFFvFfLZeXOfIas6 mGR5+117UczcUzQSqUZ5CgJqclA8IaHZBC8yA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Kb+1nlRxyP88zzpo0afAjvFdIXjiG3n1dz0hiMFtc3Z+4/nmN0kerQvOQObaJUi8V4 W5jO/GYYv2uhHQLEkVuzqW338mg0dxP9zIB6a5I8up1pcDvzuy/TJDe/SwUI6lyTNg6i c9LhhCR1FjI4w7w8w4z/b2V5g4qNYiweA+kkU= Received: by 10.223.161.212 with SMTP id s20mr582825fax.2.1260935135818; Tue, 15 Dec 2009 19:45:35 -0800 (PST) Received: from localhost (lan-78-157-90-54.vln.skynet.lt [78.157.90.54]) by mx.google.com with ESMTPS id 1sm801988fkt.33.2009.12.15.19.45.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 15 Dec 2009 19:45:34 -0800 (PST) Date: Wed, 16 Dec 2009 05:45:20 +0200 From: Gleb Kurtsou To: Daniel Thiele Message-ID: <20091216034520.GA2368@tops.skynet.lt> References: <4B24143E.2060803@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4B24143E.2060803@gmx.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org, shaun@FreeBSD.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 03:45:38 -0000 On (12/12/2009 23:07), Daniel Thiele wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Hi, > > I am contentedly using a onetime encrypted swap partition through > the means provided by rc.d/encswap and fstab, i.e. appending '.eli' > to the swap partition's name. Since some of the things that accumulate > in /tmp over the time may contain confidential information, I would > like to encrypt this partition, too. I know of the clear_tmp_enable > rc.conf option, but this only deletes /tmp's contents simply by > utilizing rm(1), which helps but I would not consider this as a > sufficient solution for the problem of making no longer needed > /tmp-data unaccessible. So, unless I am missing something, currently > the only way to go seems to be utilizing geli together with a > passphrase (and a secret key). Now, for /tmp being a file systems > for which no guarantee towards persistence across reboots is needed, > a onetime encryption seems to be the better choice, e.g. no one can > force you to give away the passphrase or key file. I'd suggest you trying a stackable cryptographic file system (pefs) developed as a google summer of code project this year. Think of it as of nullfs + encryption. No need to create/use separate partition, etc. You can create one time passwords on boot and let rc.d scripts clean old staff: # pefs mount /tmp /tmp # dd if=/dev/random bs=16 count=1 | pefs addkey -pv -k - /tmp I use it to encrypt my home directory for some time already, works pretty good. It also works on top of tmpfs, if anybody needs it :) More info: http://gleb.blog.com/tag/pefs/ Recent sources on github: http://github.com/glk/pefs > While I was looking for a solution, I stumbled upon a patch > (conf/102700, link below) from 2006 by Shaun Amott (CC'ed) that > adds support for exactly this kind of encryption. Is there a reason > why this patch has not made it into the base system yet? I think it > would be a valuable addition to FreeBSD in regard to security. In > that context it may be even better to enhance the patch to not only > support onetime encryption for /tmp, but any kind of file system, > which a user may specify via fstab. Then, however, the issue of how > to exactly distinguish between onetime and normal encryption in > fstab needs to be solved. > > Is there maybe another way to achieve onetime /tmp encryption that > I am missing? Preferably one that does not involve huge changes to > the default config files to minimize the time spent mergmaster-ing > these files during an update. This last point is basically what keeps > me from applying conf/102700 locally or implementing my own solution. > > > Kind regards, > Daniel From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 10:03:09 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 679AF1065676 for ; Wed, 16 Dec 2009 10:03:09 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id E1A238FC0C for ; Wed, 16 Dec 2009 10:03:08 +0000 (UTC) Received: by fxm27 with SMTP id 27so730628fxm.3 for ; Wed, 16 Dec 2009 02:03:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=11bn06dG51DuqtCFnaDJjQ8ph1YXC/mv3Jyhvg0O0pM=; b=P22CRcAaoMudB2Q9nxuVd6FStvYam+Jne64YyIpX+shXf5cPYRn6iFnoYkjEL/M1kT fWLsPFsei3p+QiL+pOw0aRV2rU9YmK8Kt+RhfKHYuTOuX/84w1NJGQZk2VfrB28r8/sQ cYnwiXbN7XXcJFHyh2Kn17xlQDjNdn79HrQGE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=KQihY2ZWRTZWtGqs0AAhcD+opQVeKrzJWwnxTfaj1WF59zJfM/im37xzRj9pX4FHSb 7IlwhAUCh/5SIAZl6Onv1oNlZcDHlGCX52ZZ+ef+uLoP4YCKv8A0ooRW+dhNuqylwIGc y1KeB8lt6C9jP+nu1fNyT5Hdw9dVMxdxX22Nw= Received: by 10.223.14.150 with SMTP id g22mr998198faa.14.1260957786435; Wed, 16 Dec 2009 02:03:06 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 14sm250861fxm.3.2009.12.16.02.03.04 (version=SSLv3 cipher=RC4-MD5); Wed, 16 Dec 2009 02:03:04 -0800 (PST) Sender: Alexander Motin Message-ID: <4B28B056.60606@FreeBSD.org> Date: Wed, 16 Dec 2009 12:03:02 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Tom Uffner References: <4B1671EE.1010301@FreeBSD.org> <4B25AE1A.80206@uffner.com> <4B262BAC.9040808@FreeBSD.org> <4B282EF3.8050008@uffner.com> In-Reply-To: <4B282EF3.8050008@uffner.com> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 10:03:09 -0000 Tom Uffner wrote: > here is verbose dmesg from kernel built w/ sources updated to 12/5/2009 at > midnight EST: http://xiombarg.uffner.com/dmesg_20091205.txt > > as soon as i can set up another PC & serial console i'll get you a verbose > boot from new kernel. Try please that patch: --- ata-promise.c.prev 2009-12-15 21:35:43.000000000 +0200 +++ ata-promise.c 2009-12-15 21:35:24.000000000 +0200 @@ -957,6 +957,7 @@ ata_promise_mio_dmainit(device_t dev) ata_dmainit(dev); /* note start and stop are not used here */ ch->dma.setprd = ata_promise_mio_setprd; + ch->dma.max_iosize = 65536; } -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 13:14:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ABAEE1065672; Wed, 16 Dec 2009 13:14:08 +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 60D948FC1C; Wed, 16 Dec 2009 13:14:08 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 665C66D41B; Wed, 16 Dec 2009 13:14:07 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id F0613844F3; Wed, 16 Dec 2009 14:14:06 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Wes Peters References: <20091119004651.7432a6e4.nork@FreeBSD.org> Date: Wed, 16 Dec 2009 14:14:06 +0100 In-Reply-To: (Wes Peters's message of "Tue, 15 Dec 2009 01:36:27 -0800") Message-ID: <86zl5jjc2p.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alexander Motin , freebsd-current@freebsd.org, Norikatsu Shigemura Subject: Re: How do I use NCQ of Intel X25-E(SSD) on ahci(4)? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 13:14:08 -0000 Wes Peters writes: > How useful is NCQ on an SSD? *extremely* useful. The X25 is old (as SSDs go), yet it still blows the competition out of the water on real-world (non-sequential) workloads, precisely because it supports NCQ and most of its competitors don't. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 14:49:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5737D106566B for ; Wed, 16 Dec 2009 14:49:16 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 172098FC1C for ; Wed, 16 Dec 2009 14:49:15 +0000 (UTC) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKvBb-0004tH-1Q for freebsd-current@freebsd.org; Wed, 16 Dec 2009 14:49:15 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKvBa-0007IR-Ev for freebsd-current@freebsd.org; Wed, 16 Dec 2009 14:49:06 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBGEn6xb023350 for ; Wed, 16 Dec 2009 14:49:06 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBGEn6kX023349 for freebsd-current@freebsd.org; Wed, 16 Dec 2009 14:49:06 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Wed, 16 Dec 2009 14:49:06 +0000 From: Anton Shterenlikht To: freebsd-current@freebsd.org Message-ID: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Subject: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 14:49:16 -0000 llvm port fails to build on ia64 current: gmake[3]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc/driver' gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc' /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x1231): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': : undefined reference to `__register_frame' /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x2011): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': : undefined reference to `__register_frame' gmake[2]: *** [/usr/ports/devel/llvm/work/llvm-2.6/Release/bin/lli] Error 1 gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/lli' gmake[1]: *** [lli/.makeall] Error 2 gmake[1]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools' gmake: *** [all] Error 1 *** Error code 1 Stop in /usr/ports/devel/llvm. *** Error code 1 Anything I can do to help debug this? many thanks -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 14:52:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E82221065670 for ; Wed, 16 Dec 2009 14:52:43 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id A0DA48FC0C for ; Wed, 16 Dec 2009 14:52:42 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 4386B9CB059; Wed, 16 Dec 2009 15:50:36 +0100 (CET) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vl6jqS9Q1d3n; Wed, 16 Dec 2009 15:50:33 +0100 (CET) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id B07559CB0D6; Wed, 16 Dec 2009 15:50:33 +0100 (CET) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id nBGEoXUI069350; Wed, 16 Dec 2009 15:50:33 +0100 (CET) (envelope-from rdivacky) Date: Wed, 16 Dec 2009 15:50:33 +0100 From: Roman Divacky To: Anton Shterenlikht Message-ID: <20091216145033.GA69013@freebsd.org> References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 14:52:44 -0000 I wont comment the failure but llvm does NOT support generating IA64 code as the support for this was removed some 6 months or so ago.... what exactly do you want to use the llvm@ia64 for? On Wed, Dec 16, 2009 at 02:49:06PM +0000, Anton Shterenlikht wrote: > llvm port fails to build on ia64 current: > > gmake[3]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc/driver' > gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc' > /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x1231): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': > : undefined reference to `__register_frame' > /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x2011): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': > : undefined reference to `__register_frame' > gmake[2]: *** [/usr/ports/devel/llvm/work/llvm-2.6/Release/bin/lli] Error 1 > gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/lli' > gmake[1]: *** [lli/.makeall] Error 2 > gmake[1]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools' > gmake: *** [all] Error 1 > *** Error code 1 > > Stop in /usr/ports/devel/llvm. > *** Error code 1 > > > Anything I can do to help debug this? > > many thanks > > -- > Anton Shterenlikht > Room 2.6, Queen's Building > Mech Eng Dept > Bristol University > University Walk, Bristol BS8 1TR, UK > Tel: +44 (0)117 331 5944 > Fax: +44 (0)117 929 4423 > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 15:18:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1CF3B106566B for ; Wed, 16 Dec 2009 15:18:59 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id CED8D8FC1A for ; Wed, 16 Dec 2009 15:18:58 +0000 (UTC) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKveK-0007gc-WD; Wed, 16 Dec 2009 15:18:57 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKveK-00063Y-5D; Wed, 16 Dec 2009 15:18:48 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBGFIl82034325; Wed, 16 Dec 2009 15:18:47 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBGFIlWF034324; Wed, 16 Dec 2009 15:18:47 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Wed, 16 Dec 2009 15:18:47 +0000 From: Anton Shterenlikht To: Roman Divacky Message-ID: <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> <20091216145033.GA69013@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216145033.GA69013@freebsd.org> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:18:59 -0000 On Wed, Dec 16, 2009 at 03:50:33PM +0100, Roman Divacky wrote: > I wont comment the failure but llvm does NOT support generating IA64 > code as the support for this was removed some 6 months or so ago.... > > what exactly do you want to use the llvm@ia64 for? replacement for gcc.. gcc44 and 45 fail to build on ia64. From what I can gather (I'm a user, not a developer) after following this for some months on gcc bugzilla, gcc folks do not really have a solution, or might not even understand the problem. Lots of ports of interest to me are dependent on gcc44, e.g. gfortran, blas, lapack, calculix, code_aster, etc. So I'm looking for a possible replacement for gcc44 on ia64 many thanks > > On Wed, Dec 16, 2009 at 02:49:06PM +0000, Anton Shterenlikht wrote: > > llvm port fails to build on ia64 current: > > > > gmake[3]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc/driver' > > gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/llvmc' > > /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x1231): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': > > : undefined reference to `__register_frame' > > /usr/ports/devel/llvm/work/llvm-2.6/Release/lib/libLLVMJIT.a(JIT.o)(.text+0x2011): In function `llvm::JIT::JIT(llvm::ModuleProvider*, llvm::TargetMachine&, llvm::TargetJITInfo&, llvm::JITMemoryManager*, llvm::CodeGenOpt::Level, bool)': > > : undefined reference to `__register_frame' > > gmake[2]: *** [/usr/ports/devel/llvm/work/llvm-2.6/Release/bin/lli] Error 1 > > gmake[2]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools/lli' > > gmake[1]: *** [lli/.makeall] Error 2 > > gmake[1]: Leaving directory `/usr/ports/devel/llvm/work/llvm-2.6/tools' > > gmake: *** [all] Error 1 > > *** Error code 1 > > > > Stop in /usr/ports/devel/llvm. > > *** Error code 1 > > > > > > Anything I can do to help debug this? > > > > many thanks > > > > -- > > Anton Shterenlikht > > Room 2.6, Queen's Building > > Mech Eng Dept > > Bristol University > > University Walk, Bristol BS8 1TR, UK > > Tel: +44 (0)117 331 5944 > > Fax: +44 (0)117 929 4423 > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 15:33:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93AB9106566C; Wed, 16 Dec 2009 15:33:04 +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 50ECF8FC18; Wed, 16 Dec 2009 15:33:04 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 4F6A56D41B; Wed, 16 Dec 2009 15:33:03 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 1F320844F3; Wed, 16 Dec 2009 16:33:03 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Doug Barton References: <4B23F10F.1010608@lissyara.su> <4B23FBA1.4070002@FreeBSD.org> <4B25B0CA.1070006@FreeBSD.org> <20091214155853.GC78318@FreeBSD.org> <4B26A4E3.9090200@FreeBSD.org> Date: Wed, 16 Dec 2009 16:33:03 +0100 In-Reply-To: <4B26A4E3.9090200@FreeBSD.org> (Doug Barton's message of "Mon, 14 Dec 2009 12:49:39 -0800") Message-ID: <86ljh3j5n4.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Alex Keda , freebsd-current , Robert Watson Subject: Re: May be include in GENERIC option INCLUDE_CONFIG_FILE? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:33:04 -0000 Doug Barton writes: > Wojciech A. Koszek wrote: > > It looks fine for the first glance. I would also reconsider putting it = in > > DEFAULTS, as des@ pointed out. > Ok, no objections on my part. I thought putting it in the file itself > would make it easier for those who wanted to remove it, but I'm also > in agreement with those that believe that there is no real need to > remove it except for extreme cases, and they (generally) already know > what they are doing. :) One could argue that making it hard to disable is a feature... Anyway, adding nooption INCLUDE_CONFIG_FILE to your kernel config will disable it without having to mess with DEFAULTS. I wish we had a global DEFAULTS, though, so you didn't have to add INCLUDE_CONFIG_FILE to N different files. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 15:28:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F7D51065694; Wed, 16 Dec 2009 15:28:17 +0000 (UTC) (envelope-from proks@skylinetele.com) Received: from Harpy.sky.od.ua (harpy.sky.od.ua [81.25.224.2]) by mx1.freebsd.org (Postfix) with ESMTP id D9AED8FC0A; Wed, 16 Dec 2009 15:28:16 +0000 (UTC) Received: from logos.sky.od.ua (logos [81.25.224.11]) by Harpy.sky.od.ua (8.12.10/8.12.10) with ESMTP id nBGF9Dwi008553; Wed, 16 Dec 2009 17:09:13 +0200 Message-ID: <4B28F841.1070900@skylinetele.com> Date: Wed, 16 Dec 2009 17:09:53 +0200 From: "Prokofiev S.P." User-Agent: Thunderbird 2.0.0.21 (X11/20090410) MIME-Version: 1.0 To: "Li, Qing" References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Wed, 16 Dec 2009 16:25:10 +0000 Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Qing Li Subject: Re: net/mpd5, ppp, proxy-arp issues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:28:17 -0000 Thank you ! The problem with proxy-arp has disappeared (FreeBSD 8-STABLE amd64 with mpd5). Please, somebody fix the bug kern/141285... Li, Qing wrote: > Hi, > > Recently there have been several reports regarding issues with ppp, mpd5 > and proxy-arp configuration over the ppp links. I read through the > various postings and the problems seem to be: > > 1. Unable to add proxy-arp entries for the remote ppp clients. > > 2. Log showing "ifa_add_loopback_route: insertion failed" causing > some userland applications to fail. > > May I ask that you try applying patch > > http://people.freebsd.org/~qingli/ppp-proxy-arp-patch-121515.diff > > and report back if the patch fixes your problems. And if not, > please describe what additional issues you are having. > > Thanks, > > -- Qing > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 15:30:12 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7748B10656AD for ; Wed, 16 Dec 2009 15:30:12 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46]) by mx1.freebsd.org (Postfix) with ESMTP id 5014C8FC12 for ; Wed, 16 Dec 2009 15:30:12 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id A9A0C8C06D; Wed, 16 Dec 2009 09:30:11 -0600 (CST) Date: Wed, 16 Dec 2009 09:30:11 -0600 From: Mark Linimon To: Anton Shterenlikht Message-ID: <20091216153011.GB21610@lonesome.com> References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> <20091216145033.GA69013@freebsd.org> <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.18 (2008-05-17) X-Mailman-Approved-At: Wed, 16 Dec 2009 16:25:47 +0000 Cc: Roman Divacky , freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 15:30:12 -0000 On Wed, Dec 16, 2009 at 03:18:47PM +0000, Anton Shterenlikht wrote: > gcc44 and 45 fail to build on ia64. From what I can gather (I'm a > user, not a developer) after following this for some months on gcc > bugzilla, gcc folks do not really have a solution, or might not even > understand the problem. Well, this is a pretty serious problem, then, because IIUC the llvm back-end for ia64 was recently dropped because it had not been maintained for 6 months and no longer worked at all, without any committer interest. Perhaps someone more up-to-date with llvm will correct me. mcl From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 16:28:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4073C10656A8 for ; Wed, 16 Dec 2009 16:28:02 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id F3DA48FC1B for ; Wed, 16 Dec 2009 16:28:01 +0000 (UTC) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NKwiq-0003mB-It; Wed, 16 Dec 2009 16:28:01 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NKwiq-00004u-1X; Wed, 16 Dec 2009 16:27:32 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBGGRVha039126; Wed, 16 Dec 2009 16:27:31 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBGGRVNh039125; Wed, 16 Dec 2009 16:27:31 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Wed, 16 Dec 2009 16:27:31 +0000 From: Anton Shterenlikht To: giffunip@tutopia.com Message-ID: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -4.4 X-Spam-Level: ---- Cc: freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 16:28:02 -0000 On Wed, Dec 16, 2009 at 04:26:16PM +0000, giffunip@tutopia.com wrote: > FWIW; > > For most of the scientific/CAD stuff you need a Fortran > compiler and llvm doesn't provide it. I understand gcc frontend for llvm gives you fortran. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 16:51:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E87B31065676 for ; Wed, 16 Dec 2009 16:51:37 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id C9D3A8FC15 for ; Wed, 16 Dec 2009 16:51:37 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id nBGGp8XM066687; Wed, 16 Dec 2009 08:51:08 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id nBGGp8o0066686; Wed, 16 Dec 2009 08:51:08 -0800 (PST) (envelope-from sgk) Date: Wed, 16 Dec 2009 08:51:08 -0800 From: Steve Kargl To: Anton Shterenlikht Message-ID: <20091216165108.GA66672@troutmask.apl.washington.edu> References: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.4.2.3i Cc: giffunip@tutopia.com, freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 16:51:38 -0000 On Wed, Dec 16, 2009 at 04:27:31PM +0000, Anton Shterenlikht wrote: > On Wed, Dec 16, 2009 at 04:26:16PM +0000, giffunip@tutopia.com wrote: > > FWIW; > > > > For most of the scientific/CAD stuff you need a Fortran > > compiler and llvm doesn't provide it. > > I understand gcc frontend for llvm gives you fortran. > llvm can be used within gcc's new plugin framework. So, you would need both llvm and gcc to build on IA64. Have you tried building gcc-4.3.5 on IA64? gfortran in 4.3.5 is in fairly decent shape. -- Steve From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 17:11:01 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2CC6B106568D; Wed, 16 Dec 2009 17:11:01 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from mail-yx0-f171.google.com (mail-yx0-f171.google.com [209.85.210.171]) by mx1.freebsd.org (Postfix) with ESMTP id C757D8FC1B; Wed, 16 Dec 2009 17:11:00 +0000 (UTC) Received: by yxe1 with SMTP id 1so1172926yxe.3 for ; Wed, 16 Dec 2009 09:11:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=mDom1J2H74WpG05iDovAklbLuaLYP4jhefSVo4b4QtA=; b=NPUwMUyadFKM9xnKQyeVmUyQXP/iA96WY136tO46NxE/4nGSVd9ag/PE/CSRlYFoA2 EGwu864xBv/2CEADg+1ozH6rZP0DTZTG7c5OXnoXhk/n65L0FfIeT1Fbxd0/Kv3VUxfa /ZuLh6JS7+a4jVuEwIq1wCY7IegK380/ihNlQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=F4qTo9Yah/M3bsEoEmBXEjWPnpX+yg3i5Ut/7/8LUHgODWz5+RuVq77Nc+k/UKJ1bj 8xHORWwN09LE+6Yi2U3Lex+OOZgY9ZiQyvMOcbF/s7fJT55nz66+jNWgrS6ZaML7xGuZ EYi8E1XlyVKeeZYP15Y24/IqFTFjSufcM/oWc= MIME-Version: 1.0 Received: by 10.101.4.16 with SMTP id g16mr1993180ani.25.1260983459758; Wed, 16 Dec 2009 09:10:59 -0800 (PST) In-Reply-To: <978BBD51-222D-42F0-9D3A-FFACCBCC886D@samsco.org> References: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> <978BBD51-222D-42F0-9D3A-FFACCBCC886D@samsco.org> Date: Wed, 16 Dec 2009 12:10:59 -0500 Message-ID: <3c0b01820912160910i35e12112s4d6412d6cb174f3b@mail.gmail.com> From: Alexander Sack To: Scott Long Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: aac(4) handling of probe when no devices are there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 17:11:01 -0000 On Tue, Dec 15, 2009 at 4:54 AM, Scott Long wrote: > On Dec 14, 2009, at 2:47 PM, Alexander Sack wrote: >> >> Hello Again: >> >> I guess I have a technical question/concern that I was looking for >> feedback. =A0 During the probe sequence, aac(4) conditionally responds >> to INQUIRY commands depending on target LUN: >> >> aac_cam.c/aac_cam_complete(): >> 532 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (command =3D=3D I= NQUIRY) { >> 533 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (= ccb->ccb_h.status =3D=3D CAM_REQ_CMP) >> { >> 534 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 devi= ce =3D ccb->csio.data_ptr[0] & 0x1f; >> 535 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* >> 536 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*= We want DASD and PROC devices to >> only be >> 537 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*= visible through the pass device. >> 538 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0*= / >> 539 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (= (device =3D=3D T_DIRECT) || >> 540 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 (device =3D=3D T_PROCESSOR) || >> 541 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 (sc->flags & >> AAC_FLAGS_CAM_PASSONLY)) >> 542 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->csio.data_ptr[0] =3D >> 543 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 ((device & 0xe0) | >> T_NODEVICE); >> 544 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } el= se if (ccb->ccb_h.status =3D=3D >> CAM_SEL_TIMEOUT && >> 545 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->ccb_h.target_lun !=3D 0) { >> 546 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 /* fix for INQUIRYs on Lun>0 >> */ >> 547 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 ccb->ccb_h.status =3D >> CAM_DEV_NOT_THERE; >> 548 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> 549 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> >> Why is CAM_DEV_NOT_THERE skipped on LUN 0? > > In the parallel scsi world, a selection timeout means that all LUNs withi= n > the entire target =A0do not (or no longer) exist. =A0So returning > CAM_SEL_TIMEOUT for LUN 1 would tell CAM to invalidate LUN 0 as well. > > If you look higher up in this function, you'll see a note about the > error/status codes from the AAC firmware coincidentally matching CAM's > status codes. =A0My guess is that somewhere along the line, someone at Ad= aptec > stopped reading the SCSI spec and starting returning CAM_SEL_TIMEOUT for > LUNs greater than 0, which is why this work-around is now in the driver. Interesting. Learn something everyday. I did not know that a selection timeout on a non-zero LUN meant no other LUN was available. As a colleague noted, "Has Adaptec ever read the SCSI spec?" Just kidding (somewhat).... >> =A0This is true on my target >> 6.1-amd64 machine as well as CURRENT. =A0The reason why I ask this is >> because now that aac(4) is sequential scanned, there are a lot of cam >> interrupts that come in on my 6.x machine where the threshold is only >> 500 and I get the interrupt storm threshold warning for swi2 pretty >> quickly: >> >> Interrupt storm detected on "swi2:"; throttling interrupt source >> >> Obviously its contingent on the number of adapters you have on your >> system. =A0On CURRENT I didn't see this because the threshold is double >> (I think its a 1000 by default). >> >> The issue is the number of xpt_async(AC_LOST_DEVICE, ..) calls during >> the scan. =A0The probe sequence in CURRENT as well as 6.1 handles >> CAM_SEL_TIMEOUT a little differently depending on context. Yeah I spoke too soon. I think that is a red herring though and misinterpretation of what that was really doing (in this case just seeing the device as unconfigured and moving on). But I STILL don't understand why its treated as a AC_LOST_DEVICE event at scan time (i.e. more overhead than really necessary but perhaps I am not thinking of all the possibilities down this code path, i.e. why create a path, then call xpt_asyc, all to just set the flag as unconfigured - perhaps its more align with the model than anything else and I'm reading too much into it). > It's not at all clear to me what is going on here. =A0Can you instrument = the > code to record the status of everything that is being issued to the aac_c= am > module? Yes surely. I think what might be happening is that after the INQUIRY fails, xpt_release_ccb() which I think will also check to see if any more CCBs should be sent to the device and send them. Basically the boot -v output is I am getting a CAM_SEL_TIMEOUT for each target and just hit into the 500 interrupt storm default threshold on 6.1. Let me investigate further...I'm on the right track, but I need to instrument more...Scott its my first time playing with CAM (be gentle). :D -aps From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 16:52:59 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A9351065693 for ; Wed, 16 Dec 2009 16:52:59 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: from tutopia.com (mail08mass.ifxnetworks.com [190.60.24.78]) by mx1.freebsd.org (Postfix) with ESMTP id E3AD08FC12 for ; Wed, 16 Dec 2009 16:52:58 +0000 (UTC) Received: (qmail 17302 invoked from network); 16 Dec 2009 16:26:16 -0000 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on mail08mass.ifxnetworks.com X-Spam-Level: X-Spam-Status: No, score=0.1 required=7.0 tests=MISSING_MID,RDNS_NONE autolearn=disabled version=3.2.5 Received: from unknown (HELO mail14.ifxnetworks.com) ([190.61.128.24]) (envelope-sender ) by mail08mass.ifxnetworks.com (qmail-ldap-1.03) with SMTP for ; 16 Dec 2009 16:26:16 -0000 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 From: To: Anton Shterenlikht X-Origin: 190.60.24.4 Date: Wed, 16 Dec 2009 16:26:16 +0000 X-Uidl: 1260980776229715391 X-Mailer: AtMail 4.11 Message-Id: <20091216165259.2A9351065693@hub.freebsd.org> X-Mailman-Approved-At: Wed, 16 Dec 2009 17:18:07 +0000 Cc: freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: giffunip@tutopia.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 16:52:59 -0000 FWIW;=0D =0D For most of the scientific/CAD stuff you need a Fortran=0D compiler and llvm doesn't provide it.=0D =0D I think your best solution is to try gfortran42 or=0D gfortran43 if it's supported in your platform.=0D =0D best regards,=0D =0D Pedro.=0D =0D =0D =0D From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 17:04:04 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00325106566C for ; Wed, 16 Dec 2009 17:04:03 +0000 (UTC) (envelope-from giffunip@tutopia.com) Received: from web113516.mail.gq1.yahoo.com (web113516.mail.gq1.yahoo.com [98.136.167.56]) by mx1.freebsd.org (Postfix) with SMTP id AFD648FC0C for ; Wed, 16 Dec 2009 17:04:03 +0000 (UTC) Received: (qmail 56358 invoked by uid 60001); 16 Dec 2009 16:37:23 -0000 Message-ID: <397476.56257.qm@web113516.mail.gq1.yahoo.com> X-YMail-OSG: yqGaSksVM1lnFCriag_0fOKnbd2xx7c_h7y.9F_KnYcOLFZyhkajTFXPfyMhJArDySDwNj.AeXHXWIw99RJvgENGhRNt0MsyD17gFjOW6UqOS5wfg1wWUVShnIpt4NLc.DyGIEqL121BKt_JH8eBXuc17KNsYTHcVLmtZ7BdbiWsGDgNuQ3StT9ptve4F2YsTcuXx6nsQ94UIWM1VcVTs9KOLhBYv7mAt4biWb0YaO0cAXDGS7EVJmOAAI_5KBetnOmDksgFUT0SOb9FfxSxnVo03JV.epYqv7CTXiM5s1T2Tj3DEwEsGtmmTOFmJmeLTcbxZO04thkW9Mdxdeu9Sg3oLaILHCwOx7GMRnr9JYgx7fS8Xrplr1rx Received: from [190.157.123.47] by web113516.mail.gq1.yahoo.com via HTTP; Wed, 16 Dec 2009 08:37:23 PST X-RocketYMMF: giffunip X-Mailer: YahooMailRC/240.3 YahooMailWebService/0.8.100.260964 References: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> Date: Wed, 16 Dec 2009 08:37:23 -0800 (PST) From: "Pedro F. Giffuni" To: Anton Shterenlikht In-Reply-To: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 16 Dec 2009 17:18:18 +0000 Cc: freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 17:04:04 -0000 =0A=0A----- Original Message ----=0A...=0A> =0A> On Wed, Dec 16, 2009 at 04= :26:16PM +0000, giffunip@tutopia.com wrote:=0A> > FWIW;=0A> > =0A> > For mo= st of the scientific/CAD stuff you need a Fortran=0A> > compiler and llvm d= oesn't provide it.=0A> =0A> I understand gcc frontend for llvm gives you fo= rtran.=0A> =0A=0AIt gives you a limited implementation of=A0gfortran42. Rig= ht now It's better and=0Asimpler=A0to build gcc42 (or gcc43) with fortran s= upport.=0A=0Aregards,=0A=0APedro.=A0=0A=0A=0A From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 18:03:43 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 730A310657C6 for ; Wed, 16 Dec 2009 18:03:42 +0000 (UTC) (envelope-from bofh@redwerk.com) Received: from redwerk.com (redwerk.com [89.105.196.9]) by mx1.freebsd.org (Postfix) with ESMTP id 624718FC13 for ; Wed, 16 Dec 2009 18:03:42 +0000 (UTC) Received: from [192.168.250.5] (helo=office.redwerk.com) by redwerk.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1NKyDs-0000bp-AM for freebsd-current@freebsd.org; Wed, 16 Dec 2009 19:03:40 +0100 Received: from bofh by office.redwerk.com with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NKyDq-000Jcw-Ul for freebsd-current@freebsd.org; Wed, 16 Dec 2009 20:03:38 +0200 Date: Wed, 16 Dec 2009 20:03:38 +0200 From: Eugene Dzhurinsky To: freebsd-current@freebsd.org Message-ID: <20091216180338.GA75403@office.redwerk.com> References: <20091003110914.GB71004@office.redwerk.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dDRMvlgZJXvWKvBx" Content-Disposition: inline In-Reply-To: <20091003110914.GB71004@office.redwerk.com> Subject: Re: Atheros WIFI is not recognized on FreeBSD 8.0-RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 18:03:43 -0000 --dDRMvlgZJXvWKvBx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Oct 03, 2009 at 02:09:14PM +0300, Eugene Dzhurinsky wrote: > Hi there! >=20 > I am facing some strange issue with recognizing the wifi card on my ASUS = K40IN > laptop. >=20 > pciconf -lv shows me the following: >=20 > none5@pci0:5:0:0: class=3D0x028000 card=3D0x10891a3b chip=3D0x002b168c re= v=3D0x01 hdr=3D0x00 > vendor =3D 'Atheros Communications Inc.' > class =3D network >=20 > On wiki page http://wiki.freebsd.org/AsusEee#head-47f2e69f1dd87ec8920929c= ef682552933095ce6 >=20 > there is the statement: >=20 > Wireless Atheros 9285 (supported in 8.0 only?) class=3D0x028000 card=3D0x= 10891a3b chip=3D0x002b168c rev=3D0xc0 hdr=3D0x00=20 >=20 > the only difference is in "rev" property - 0x01 !=3D 0xc0 >=20 > The question is - is it possible to change something in the sources of ke= rnel > so the card will be recognized? And can somebody please explain what I sh= ould > to try out? Hi again! I updated to 8.0 stable - but the Atheros card still not recogniz= ed :( Can somebody please elucidate - are there any plans for supporting this dev= ice in FreeBSD? Thank you in advance! --=20 Eugene N Dzhurinsky --dDRMvlgZJXvWKvBx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkspIPEACgkQy/i/DoZLbHxsYgCfZ2DfBm/TvxndR/rJWnn5WxsE 95AAn3+gIgz5GB15MzBXT1QCP/8byovq =jwuC -----END PGP SIGNATURE----- --dDRMvlgZJXvWKvBx-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 18:09:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31D02106566C for ; Wed, 16 Dec 2009 18:09:22 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id E634E8FC22 for ; Wed, 16 Dec 2009 18:09:21 +0000 (UTC) Received: from desktop1.alchemy-networks.co.uk ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NKyL5-0006Nl-51; Wed, 16 Dec 2009 18:11:07 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Eugene Dzhurinsky" , freebsd-current@freebsd.org References: <20091003110914.GB71004@office.redwerk.com> <20091216180338.GA75403@office.redwerk.com> Date: Wed, 16 Dec 2009 18:09:10 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Message-ID: In-Reply-To: <20091216180338.GA75403@office.redwerk.com> User-Agent: Opera Mail/10.01 (FreeBSD) Cc: Subject: Re: Atheros WIFI is not recognized on FreeBSD 8.0-RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 18:09:22 -0000 Hi same problem here as well, I tried fixing it in devid.h but doing so causes a compilation error, I have no idea where to go from here either, its a shame that the card seems to be supported but the driver does not notice it. sorry about the double reply by the way Eugene I replied directly to you by accident in the first mail On Wed, 16 Dec 2009 18:03:38 -0000, Eugene Dzhurinsky wrote: > On Sat, Oct 03, 2009 at 02:09:14PM +0300, Eugene Dzhurinsky wrote: >> Hi there! >> >> I am facing some strange issue with recognizing the wifi card on my >> ASUS K40IN >> laptop. >> >> pciconf -lv shows me the following: >> >> none5@pci0:5:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c >> rev=0x01 hdr=0x00 >> vendor = 'Atheros Communications Inc.' >> class = network >> >> On wiki page >> http://wiki.freebsd.org/AsusEee#head-47f2e69f1dd87ec8920929cef682552933095ce6 >> >> there is the statement: >> >> Wireless Atheros 9285 (supported in 8.0 only?) class=0x028000 >> card=0x10891a3b chip=0x002b168c rev=0xc0 hdr=0x00 >> >> the only difference is in "rev" property - 0x01 != 0xc0 >> >> The question is - is it possible to change something in the sources of >> kernel >> so the card will be recognized? And can somebody please explain what I >> should >> to try out? > > Hi again! I updated to 8.0 stable - but the Atheros card still not > recognized > :( > > Can somebody please elucidate - are there any plans for supporting this > device > in FreeBSD? > > Thank you in advance! > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 18:17:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4009B1065693 for ; Wed, 16 Dec 2009 18:17:24 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id F119A8FC17 for ; Wed, 16 Dec 2009 18:17:23 +0000 (UTC) Received: from desktop1.alchemy-networks.co.uk ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NKySr-0006Ot-Ah; Wed, 16 Dec 2009 18:19:09 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Paul G Webster" , "Eugene Dzhurinsky" , freebsd-current@freebsd.org References: <20091003110914.GB71004@office.redwerk.com> <20091216180338.GA75403@office.redwerk.com> Date: Wed, 16 Dec 2009 18:17:16 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Message-ID: In-Reply-To: User-Agent: Opera Mail/10.01 (FreeBSD) Cc: Subject: Re: Atheros WIFI is not recognized on FreeBSD 8.0-RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 18:17:24 -0000 Would also like to say, 8.0-RELEASE. it seems that setting the correct 'rev' in the devid.h somehow conflicts with another AR card.. On Wed, 16 Dec 2009 18:09:10 -0000, Paul G Webster wrote: > Hi same problem here as well, I tried fixing it in devid.h but doing so > causes a compilation error, I have no idea where to go from here either, > its a shame that the card seems to be supported but the driver does not > notice it. sorry about the double reply by the way Eugene I replied > directly to you by accident in the first mail > > On Wed, 16 Dec 2009 18:03:38 -0000, Eugene Dzhurinsky > wrote: > >> On Sat, Oct 03, 2009 at 02:09:14PM +0300, Eugene Dzhurinsky wrote: >>> Hi there! >>> >>> I am facing some strange issue with recognizing the wifi card on my >>> ASUS K40IN >>> laptop. >>> >>> pciconf -lv shows me the following: >>> >>> none5@pci0:5:0:0: class=0x028000 card=0x10891a3b chip=0x002b168c >>> rev=0x01 hdr=0x00 >>> vendor = 'Atheros Communications Inc.' >>> class = network >>> >>> On wiki page >>> http://wiki.freebsd.org/AsusEee#head-47f2e69f1dd87ec8920929cef682552933095ce6 >>> >>> there is the statement: >>> >>> Wireless Atheros 9285 (supported in 8.0 only?) class=0x028000 >>> card=0x10891a3b chip=0x002b168c rev=0xc0 hdr=0x00 >>> >>> the only difference is in "rev" property - 0x01 != 0xc0 >>> >>> The question is - is it possible to change something in the sources of >>> kernel >>> so the card will be recognized? And can somebody please explain what I >>> should >>> to try out? >> >> Hi again! I updated to 8.0 stable - but the Atheros card still not >> recognized >> :( >> >> Can somebody please elucidate - are there any plans for supporting this >> device >> in FreeBSD? >> >> Thank you in advance! >> > > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 18:39:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DFBC71065694 for ; Wed, 16 Dec 2009 18:39:44 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outA.internet-mail-service.net (outa.internet-mail-service.net [216.240.47.224]) by mx1.freebsd.org (Postfix) with ESMTP id C4DD08FC1D for ; Wed, 16 Dec 2009 18:39:44 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by out.internet-mail-service.net (Postfix) with ESMTP id BE5C1B57E; Wed, 16 Dec 2009 10:39:45 -0800 (PST) X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 0FD552D6010; Wed, 16 Dec 2009 10:39:43 -0800 (PST) Message-ID: <4B29297D.30402@elischer.org> Date: Wed, 16 Dec 2009 10:39:57 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Mark Linimon References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> <20091216145033.GA69013@freebsd.org> <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> <20091216153011.GB21610@lonesome.com> In-Reply-To: <20091216153011.GB21610@lonesome.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Roman Divacky , freebsd-current@freebsd.org, Anton Shterenlikht Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 18:39:45 -0000 Mark Linimon wrote: > On Wed, Dec 16, 2009 at 03:18:47PM +0000, Anton Shterenlikht wrote: >> gcc44 and 45 fail to build on ia64. From what I can gather (I'm a >> user, not a developer) after following this for some months on gcc >> bugzilla, gcc folks do not really have a solution, or might not even >> understand the problem. > > Well, this is a pretty serious problem, then, because IIUC the llvm > back-end for ia64 was recently dropped because it had not been maintained > for 6 months and no longer worked at all, without any committer interest. > Perhaps someone more up-to-date with llvm will correct me. maybe the intel cc compiler? > > mcl > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 19:57:01 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 99C651065670 for ; Wed, 16 Dec 2009 19:57:01 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7E0F08FC0A for ; Wed, 16 Dec 2009 19:57:01 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id nBGJutTu014182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 16 Dec 2009 11:56:56 -0800 Received: from ptavv.es.net (localhost [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id E37FA1CC0C; Wed, 16 Dec 2009 11:56:55 -0800 (PST) To: Julian Elischer In-reply-to: Your message of "Tue, 15 Dec 2009 09:06:04 PST." <4B27C1FC.5030800@elischer.org> Date: Wed, 16 Dec 2009 11:56:55 -0800 From: "Kevin Oberman" Message-Id: <20091216195655.E37FA1CC0C@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-12-16_10:2009-12-12, 2009-12-16, 2009-12-16 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0912160158 Cc: "Bjoern A. Zeeb" , Luigi Rizzo , FreeBSD current mailing list Subject: Re: [PATCH] ipfw logging through tcpdump ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 19:57:01 -0000 > Date: Tue, 15 Dec 2009 09:06:04 -0800 > From: Julian Elischer > Sender: owner-freebsd-current@freebsd.org > > Luigi Rizzo wrote: > > On Tue, Dec 15, 2009 at 10:09:47AM +0000, Bjoern A. Zeeb wrote: > >> On Tue, 15 Dec 2009, Luigi Rizzo wrote: > >> > >> Hi, > >> > >>> The following ipfw patch (which i wrote back in 2001/2002) makes > >>> ipfw logging possible through tcpdump -- it works by passing to the > >>> fake device 'ipfw0' all packets matching rules marked 'log' . > >>> The use is very simple -- to test it just do > >>> > >>> ipfw add 100 count log ip from any to any > >>> > >>> and then > >>> > >>> tcpdump -ni ipfw0 > >>> > >>> will show all matching traffic. > >>> > >>> I think this is a quite convenient and flexible option, so if there > >>> are no objections I plan to commit it to head. > >> > >> pf(4) has pflog(4). Ideally calling it the same would be good though > >> I wonder if two of the the three of our firewalls grow that feature, > >> if we could have a common packet logging device rather than re-doing > >> it for each implementation. > >> > >> Frankly, I haven't looked at the details of the implementation but I > >> found getting rul numbers with tcpdump -e etc. was pretty cool to > >> identify where things were blocked or permitted. > > > > this is something trivial which i have planned already -- stuff > > 10-12 bytes in the MAC header with rule numbers and actions > > is surely trivial. > > > > Thanks for the pointer to pflog, i'll look at that. > > > >> Also make sure that the per-VIMAGE interface will work correctly and > >> as expected. > > > > On this i would like more feedback -- is there anything special > > that I am supposed to do to create per-vimage interfaces ? > > Could you look at the code i sent ? > > "ipfw0" uses the same attach/detach code used by if_tap. > > > I'm not sure we should do everything just because we can. > it gives us nothing that we can't already get. you can filter using > ipfw netgraph -> netgraph bpf -> ng_socket > you can efficiently capture packets with divert (or tee) > you can write to pcap files using phk's program. While I agree with the sentiment, the proposal is so simple and elegant and so easy to use that I think it would be crazy to not do it. It's just much easier to use on an impromptu basis than doing the netgraph stuff (except for those who do lots of netgraph). -- 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 From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 22:22:01 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC2EC106566C for ; Wed, 16 Dec 2009 22:22:01 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id AD11C8FC0A for ; Wed, 16 Dec 2009 22:22:01 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 63F9946B39 for ; Wed, 16 Dec 2009 17:22:01 -0500 (EST) Received: from jhbbsd.localnet (unknown [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 573C38A01B for ; Wed, 16 Dec 2009 17:22:00 -0500 (EST) From: John Baldwin To: current@freebsd.org Date: Wed, 16 Dec 2009 17:21:53 -0500 User-Agent: KMail/1.12.1 (FreeBSD/7.2-CBSD-20091103; KDE/4.3.1; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200912161721.53540.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 16 Dec 2009 17:22:00 -0500 (EST) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Subject: NOTES checker X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 22:22:01 -0000 I wrote a little script today that crawls through sys/conf/files*, sys/conf/options*, sys/conf/NOTES, and sys/*/conf/NOTES looking for devices or options that are not tested in all the places they are valid. If folks are interested I can commit it to src/tools. At the moment we have 300+ violations in HEAD. :) The first few look like this: WARN: Attempt to change type of gdc from option to device at /home/jhb/work/freebsd/svn/head/sys/pc98/conf/NOTES:307 Previous type set at /home/jhb/work/freebsd/svn/head/sys/conf/options.pc98:70 WARN: device acpi_aiboost is defined globally but only tested in i386 NOTES WARN: device acpi_asus is defined globally but only tested in i386 NOTES WARN: device acpi_dock is defined globally but only tested in i386 NOTES WARN: device acpi_fujitsu is defined globally but only tested in i386 NOTES WARN: device acpi_hp is defined globally but only tested in i386 NOTES WARN: device acpi_ibm is defined globally but only tested in i386 NOTES WARN: option ACPI_MAX_TASKS is defined globally but never tested WARN: option ACPI_MAX_THREADS is defined globally but never tested WARN: device acpi_panasonic is defined globally but only tested in i386 NOTES WARN: device acpi_sony is defined globally but only tested in i386 NOTES WARN: device acpi_toshiba is defined globally but only tested in i386 NOTES WARN: device acpi_video is defined globally but only tested in i386 NOTES WARN: device acpi_wmi is defined globally but only tested in i386 NOTES WARN: ad7418 is defined globally but never tested WARN: ada is defined globally but never tested WARN: option ADAPTIVE_LOCKMGRS is defined globally but never tested WARN: adlink is defined globally but never tested -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 22:30:00 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF063106566B for ; Wed, 16 Dec 2009 22:30:00 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id 193088FC18 for ; Wed, 16 Dec 2009 22:29:59 +0000 (UTC) Received: by ewy26 with SMTP id 26so588957ewy.3 for ; Wed, 16 Dec 2009 14:29:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:organization:to:subject :date:user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=IsLrN0QYf0I3uRPuK1Ur3vqHfRW8/tK7SN686nAfAzY=; b=YjaRjAan6M7ThXPkidQDwPGR1tPVnMZRt+z9JjW/YGMiPjQurjsh6S3ddlfjn/3IND j+1x46QfGGevSa/vwAQldnBPDGmqSP7FLBSORgTDx+iZQ2J4ofIGuT2rtfkUNT6xmRS5 XkAAkqEvbu2OHbj16+3LV2L9GbmrK1GU/Dfns= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:organization:to:subject:date:user-agent:cc:references :in-reply-to:mime-version:content-type:content-transfer-encoding :message-id; b=eTyrmplxmoVgcsxd6z8H28Hz04QgM/Dy83fbFaM2CbQvyDC+InIGEHq920E/hUzbj0 b0A+ACli+FUBM3iT2WgGc5DrTWYjjiYVS2ZDkPLIigC9QtasVnIVkKFaOkUQt2lSJujr MnRQWXzMIg40lYretmmAVLwq9bKgQFN3eHfDw= Received: by 10.213.103.137 with SMTP id k9mr1877274ebo.0.1261002598477; Wed, 16 Dec 2009 14:29:58 -0800 (PST) Received: from dragon.dg ([41.0.54.20]) by mx.google.com with ESMTPS id 5sm2284149eyh.0.2009.12.16.14.29.55 (version=SSLv3 cipher=RC4-MD5); Wed, 16 Dec 2009 14:29:56 -0800 (PST) From: David Naylor Organization: Private To: John Baldwin Date: Thu, 17 Dec 2009 00:30:03 +0200 User-Agent: KMail/1.12.3 (FreeBSD/8.0-PRERELEASE; KDE/4.3.3; amd64; ; ) References: <200912151124.58478.naylor.b.david@gmail.com> <200912150900.20229.jhb@freebsd.org> In-Reply-To: <200912150900.20229.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2328016.G2jfqD0TGX"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912170030.06523.naylor.b.david@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: [regression] loader stalls on compressed module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 22:30:00 -0000 --nextPart2328016.G2jfqD0TGX Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Tuesday 15 December 2009 16:00:20 John Baldwin wrote: > On Tuesday 15 December 2009 4:24:54 am David Naylor wrote: > > Hi, > > > > It appears that recently (~6 months) loader can no longer load compress= ed > > kernel objects (gzipped) . This regression is present on both FreeBSD-8 > > and >=20 > - >=20 > > Current. > > > > This can be reproduced by doing: > > # cd /boot/kernel ; gzip -9 unionfs.ko > > (Choose option 6 from loader and enter: load unionfs) > > > > I have experienced this on both i386 and amd64. It appears that loader > > can handle a compressed generic kernel (and maybe other modules). >=20 > Does a loader from TOT still exhibit this? If you build the loader w/o G= PT > support (LOADER_NO_GPT or some such, it's in sys/boot/i386/loader/Makefil= e) > does that fix it? What is TOT? # make clean depend all install -DLOADER_NO_GPT_SUPPORT -DLOADER_ONLY =3D> Stalled # make clean depend all install -DLOADER_BZIP2_SUPPORT -DLOADER_ONLY =3D> (With bzip2 -9 unionfs.ko) lseek failed elf64_obj_loadimage: read failed can't load file '/boot/kernel/unionfs.ko' input/output error I don't use bzip2 support so I cannot comment on past behaviour. Should I= =20 file a PR about this problem? --nextPart2328016.G2jfqD0TGX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEABECAAYFAkspX24ACgkQUaaFgP9pFrIixwCfVuZgmPZmHaJFUe+YNZVIputt 1EEAn1V+rQmhJIu8XVcoKT+KntxjKsj3 =Ig+j -----END PGP SIGNATURE----- --nextPart2328016.G2jfqD0TGX-- From owner-freebsd-current@FreeBSD.ORG Wed Dec 16 22:47:57 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5BA6E1065670 for ; Wed, 16 Dec 2009 22:47:57 +0000 (UTC) (envelope-from roberto@keltia.freenix.fr) Received: from keltia.freenix.fr (cl-180.mrs-01.fr.sixxs.net [IPv6:2a01:240:fe00:b3::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0C39D8FC08 for ; Wed, 16 Dec 2009 22:47:57 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by keltia.freenix.fr (Postfix/TLS) with ESMTP id 33C572099 for ; Wed, 16 Dec 2009 23:47:56 +0100 (CET) X-Virus-Scanned: amavisd-new at keltia.freenix.fr Received: from keltia.freenix.fr ([127.0.0.1]) by localhost (keltia.freenix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8a1s+uxb46c for ; Wed, 16 Dec 2009 23:47:55 +0100 (CET) Received: from sidhe.keltia.net (unknown [IPv6:2a01:240:fe5c:0:222:41ff:fe33:d76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: roberto) by keltia.freenix.fr (Postfix/TLS) with ESMTPSA id C45CE2098 for ; Wed, 16 Dec 2009 23:47:55 +0100 (CET) Date: Wed, 16 Dec 2009 23:51:24 +0100 From: Ollivier Robert To: freebsd-current@freebsd.org Message-ID: <20091216225124.GC85336@sidhe.keltia.net> References: <200912161721.53540.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912161721.53540.jhb@freebsd.org> X-Operating-System: MacOS X / MBP 4,1 - FreeBSD 8.0 / T3500-E5520 Nehalem User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: NOTES checker X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2009 22:47:57 -0000 According to John Baldwin: > I wrote a little script today that crawls through sys/conf/files*, > sys/conf/options*, sys/conf/NOTES, and sys/*/conf/NOTES looking for devices > or options that are not tested in all the places they are valid. If folks > are interested I can commit it to src/tools. At the moment we have 300+ > violations in HEAD. :) The first few look like this: Sounds like a perfect candidate for src/tools or regression tests. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr In memoriam to Ondine : http://ondine.keltia.net/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 01:13:54 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 317DF106566B for ; Thu, 17 Dec 2009 01:13:54 +0000 (UTC) (envelope-from wkoszek@freebsd.czest.pl) Received: from freebsd.czest.pl (l95h.icis.pcz.pl [212.87.224.105]) by mx1.freebsd.org (Postfix) with ESMTP id B947C8FC17 for ; Thu, 17 Dec 2009 01:13:52 +0000 (UTC) Received: from freebsd.czest.pl (l95h.icis.pcz.pl [212.87.224.105]) by freebsd.czest.pl (8.14.2/8.14.2) with ESMTP id nBH1PunQ060171; Thu, 17 Dec 2009 02:25:56 +0100 (CET) (envelope-from wkoszek@freebsd.czest.pl) Received: (from wkoszek@localhost) by freebsd.czest.pl (8.14.2/8.14.2/Submit) id nBH1Ptjc060170; Thu, 17 Dec 2009 02:25:55 +0100 (CET) (envelope-from wkoszek) Date: Thu, 17 Dec 2009 02:25:55 +0100 From: "Wojciech A. Koszek" To: Thierry Herbelot Message-ID: <20091217012555.GM78318@FreeBSD.org> Mail-Followup-To: Thierry Herbelot , current@freebsd.org References: <200912110615.28030.thierry.herbelot@free.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Disposition: inline In-Reply-To: <200912110615.28030.thierry.herbelot@free.fr> User-Agent: Mutt/1.5.17 (2007-11-01) X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-3.0 (freebsd.czest.pl [212.87.224.105]); Thu, 17 Dec 2009 02:25:56 +0100 (CET) Cc: current@freebsd.org Subject: Re: Panic in a recent kernel (cardbus/pci related ?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 01:13:54 -0000 On Fri, Dec 11, 2009 at 06:15:27AM +0100, Thierry Herbelot wrote: > Hello, > > I'm seeing a panic in my latest -Current kernel (config file == GENERIC minus > INVARIANTS, WITNESS and SMP). The machine is an older notebook, with a PCMCIA > network card. I think I experienced the same problem as well: cardbus0: CIS pointer is 0x5001 cardbus0: CIS in BAR 0x10 cardbus0: CIS Mapped to 0x88000000 cardbus0: CIS offset is 0x5000 cardbus0: CIS pointer is 0x5001 cardbus0: CIS in BAR 0x10 cardbus0: CIS Mapped to 0x88000000 cardbus0: CIS offset is 0x5000 TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: 71021200 TUPLE: Unknown(0x04) [6]: 03 01 00 00 00 00 TUPLE: Unknown(0x05) [14]: 41 b1 39 b5 1e 2d 4e 56 30 ff ff 02 e9 00 Product version: 7.1 Product name: Atheros Communications, Inc. | AR5001-0000-0000 | Wireless LAN Reference Card | 00 | Functions: Network Adaptor, Memory Function Extension: 02808d5b00 Function Extension: 0240548900 Function Extension: 02001bb700 Function Extension: 0280a81201 Function Extension: 0200366e01 Function Extension: 0200512502 Function Extension: 02006cdc02 Function Extension: 0280f93703 Function Extension: 0200a24a04 Function Extension: 0308 Function Extension: 040600032f555555 Function Extension: 0501 CIS reading done panic: resource_list_add: resource entry is busy cpuid = 0 KDB: enter: panic Plugging WiFi CardBus-based card. -- Wojciech A. Koszek wkoszek@FreeBSD.org http://FreeBSD.czest.pl/~wkoszek/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 04:28:59 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C03B51065670 for ; Thu, 17 Dec 2009 04:28:59 +0000 (UTC) (envelope-from bruce@cran.org.uk) Received: from muon.cran.org.uk (unknown [IPv6:2001:470:1f09:679::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED9B8FC12 for ; Thu, 17 Dec 2009 04:28:59 +0000 (UTC) Received: from unknown (unknown [87.194.158.129]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by muon.cran.org.uk (Postfix) with ESMTPSA id 2FCA881B1; Thu, 17 Dec 2009 04:29:04 +0000 (UTC) Date: Thu, 17 Dec 2009 04:27:46 +0000 From: Bruce Cran To: current@freebsd.org Message-ID: <20091217042746.000038a8@unknown> X-Mailer: Claws Mail 3.7.2cvs27 (GTK+ 2.16.0; i586-pc-mingw32msvc) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: bzeeb+freebsd+lor@zabbadoz.net Subject: lor: sctp-create vs. sctp-it X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 04:28:59 -0000 lock order reversal: 1st 0xffffff00300c5488 sctp-create (inp_create) @ /usr/src/sys/netinet/sctp_input.c:4897 2nd 0xffffffff80e11df0 sctp-it (iterator) @ /usr/src/sys/netinet/sctp_pcb.c:3102 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a _witness_debugger() at _witness_debugger+0x2e _witness_checkorder() at witness_checkorder+0x81e _mtx_lock_flags() at _mtx_lock_flags+0x78 sctp_inpcb_free() at sctp_inpcb_free+0x50 sctp_process_cookie_new() at sctp_process_cookie_new+0x646 sctp_process_control() at sctp_process_control+0x5eb2 sctp_common_input_processing() at sctp_common_input_processing+0x1b1 sctp_input_with_port() at sctp_input_with_port+0x388 ip_input() at ip_input+0xbc swi_net() at swi_net+0x151 intr_event_execute_handlers() at intr_event_execute_handlers+0x66 ithread_loop() at ithread_loop+0xb2 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff8000047d30, rbp = 0 --- Afterwards the console wouldn't respond: I could always break into the debugger and see the contents of other ttys once the kernel was stopped, but once I continued the console was frozen. -- Bruce Cran From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 07:52:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01F96106566B for ; Thu, 17 Dec 2009 07:52:11 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.freebsd.org (Postfix) with ESMTP id B25E58FC13 for ; Thu, 17 Dec 2009 07:52:10 +0000 (UTC) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirg.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NLB90-0003Fa-Ka; Thu, 17 Dec 2009 07:52:03 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NLB8z-0000kM-Ev; Thu, 17 Dec 2009 07:51:29 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBH7pTuF000128; Thu, 17 Dec 2009 07:51:29 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBH7pS8T099875; Thu, 17 Dec 2009 07:51:28 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Thu, 17 Dec 2009 07:51:28 +0000 From: Anton Shterenlikht To: Steve Kargl Message-ID: <20091217075128.GA92037@mech-cluster241.men.bris.ac.uk> References: <20091216162731.GA39118@mech-cluster241.men.bris.ac.uk> <20091216165108.GA66672@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216165108.GA66672@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: giffunip@tutopia.com, Anton Shterenlikht , freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 07:52:11 -0000 On Wed, Dec 16, 2009 at 08:51:08AM -0800, Steve Kargl wrote: > On Wed, Dec 16, 2009 at 04:27:31PM +0000, Anton Shterenlikht wrote: > > On Wed, Dec 16, 2009 at 04:26:16PM +0000, giffunip@tutopia.com wrote: > > > FWIW; > > > > > > For most of the scientific/CAD stuff you need a Fortran > > > compiler and llvm doesn't provide it. > > > > I understand gcc frontend for llvm gives you fortran. > > > > llvm can be used within gcc's new plugin framework. > So, you would need both llvm and gcc to build on > IA64. Have you tried building gcc-4.3.5 on IA64? > gfortran in 4.3.5 is in fairly decent shape. no, gcc43 fails to build as well -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 09:41:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3EE4E106566C for ; Thu, 17 Dec 2009 09:41:11 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout0.freenet.de (mout0.freenet.de [IPv6:2001:748:100:40::2:2]) by mx1.freebsd.org (Postfix) with ESMTP id CD7758FC16 for ; Thu, 17 Dec 2009 09:41:10 +0000 (UTC) Received: from [195.4.92.27] (helo=17.mx.freenet.de) by mout0.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.70 #1) id 1NLCr7-0005hn-MJ for freebsd-current@freebsd.org; Thu, 17 Dec 2009 10:41:09 +0100 Received: from p57ae2c1e.dip0.t-ipconnect.de ([87.174.44.30]:46741 helo=ernst.jennejohn.org) by 17.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1NLCr7-0005uU-EP for freebsd-current@freebsd.org; Thu, 17 Dec 2009 10:41:09 +0100 Date: Thu, 17 Dec 2009 10:41:08 +0100 From: Gary Jennejohn To: freebsd-current@freebsd.org Message-ID: <20091217104108.679728ea@ernst.jennejohn.org> X-Mailer: Claws Mail 3.7.3 (GTK+ 2.16.2; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: fsck always errors out during boot with gjournal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 09:41:11 -0000 I'm running 9-CURRENT AMD64. I decided to use gjournal on /home. I successfully did newfs -J to enable journaling anf gjournal -label to get a ada0s1f.journal device. The problem is that, unless I set fs_passno in /etc/fstab to 0, fsck always complains that it can't find the superblock and booting fails. But I always see messages that the journal is OK when booting: GEOM_JOURNAL: Journal 4260374310: ada0s1f contains data. GEOM_JOURNAL: Journal 4260374310: ada0s1f contains journal. GEOM_JOURNAL: Journal ada0s1f clean. So, is this normal behavior? Seems rather peculiar to me. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 09:27:34 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 084C8106566C for ; Thu, 17 Dec 2009 09:27:34 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8728B8FC0C for ; Thu, 17 Dec 2009 09:27:33 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLCDf-000IFk-Hg for freebsd-current@freebsd.org; Thu, 17 Dec 2009 12:00:23 +0300 From: "Alexander Zagrebin" To: Date: Thu, 17 Dec 2009 12:00:23 +0300 Message-ID: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp+9135DWsMJaevS7ORggOUhWiWmQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-Mailman-Approved-At: Thu, 17 Dec 2009 12:33:00 +0000 Subject: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 09:27:34 -0000 Hi! I use onboard ICH7 SATA controller with two disks attached: atapci1: port 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0-0x30af irq 19 at device 31.2 on pci0 atapci1: [ITHREAD] ata2: on atapci1 ata2: [ITHREAD] ata3: on atapci1 ata3: [ITHREAD] ad4: 1430799MB at ata2-master SATA150 ad6: 1430799MB at ata3-master SATA150 The disks are used for mirrored ZFS pool. I have noticed that the system periodically locks up on disk operations. After approx. 10 min of very slow disk i/o (several KB/s) the speed of disk operations restores to normal. gstat has shown that the problem is in ad6. For example, there is a filtered output of iostat -x 1: extended device statistics device r/s w/s kr/s kw/s wait svc_t %b ad6 818.6 0.0 10840.2 0.0 0 0.4 34 ad6 300.6 642.0 3518.5 24830.3 50 24.8 72 ad6 1.0 639.3 63.7 17118.3 0 62.1 98 ad6 404.5 4.0 6837.7 4.0 0 0.5 18 ad6 504.5 0.0 13667.2 0.0 1 0.7 32 ad6 633.3 0.0 13190.3 0.0 1 0.7 38 ad6 416.3 384.5 8134.7 24606.2 0 16.3 57 ad6 538.9 76.7 9772.8 2982.2 55 2.9 40 ad6 31.9 929.5 801.0 37498.6 0 27.2 82 ad6 635.5 0.0 13087.1 0.0 1 0.6 35 ad6 579.6 0.0 16669.8 0.0 0 0.8 43 ad6 603.6 0.0 11697.4 0.0 1 0.7 40 ad6 538.0 0.0 10438.7 0.0 0 0.9 47 ad6 30.9 898.4 868.6 40585.4 0 36.6 78 ad6 653.3 86.6 8566.6 202.7 1 0.8 40 ad6 737.1 0.0 6429.4 0.0 1 0.6 42 ad6 717.1 0.0 3958.7 0.0 0 0.5 36 ad6 1179.5 0.0 2058.9 0.0 0 0.1 15 ad6 1191.2 0.0 1079.6 0.0 1 0.1 15 ad6 985.1 0.0 5093.9 0.0 0 0.2 23 ad6 761.8 0.0 9801.3 0.0 1 0.4 31 ad6 698.7 0.0 9215.1 0.0 0 0.4 30 ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 ad6 3.0 762.8 191.2 28732.3 0 57.6 99 ad6 10.0 4.0 163.9 4.0 1 1.6 2 Before this line we have a normal operations. Then the behaviour of ad6 changes (pay attention to high average access time and percent of "busy" significantly greater than 100): ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 1.0 0.0 0.5 0.0 1 1798.3 179 ad6 1.0 0.0 1.5 0.0 1 1775.4 177 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 10.0 0.0 75.2 0.0 1 180.3 180 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 83.7 0.0 862.9 0.0 1 21.4 179 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 1.0 0.0 63.7 0.0 1 1707.4 170 ad6 1.0 0.0 9.0 0.0 0 1791.0 178 ad6 10.9 0.0 172.2 0.0 2 0.2 0 ad6 24.9 0.0 553.7 0.0 1 143.3 179 ad6 0.0 0.0 0.0 0.0 7 0.0 0 ad6 2.0 23.9 32.4 1529.9 1 336.3 177 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 68.7 0.0 1322.8 0.0 1 26.3 181 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 27.9 0.0 193.7 0.0 1 61.6 172 ad6 1.0 0.0 2.5 0.0 1 1777.4 177 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 1.0 0.0 2.0 0.0 1 1786.9 178 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 2.0 0.0 6.5 0.0 1 899.4 179 ad6 0.0 0.0 0.0 0.0 1 0.0 0 ad6 1.0 0.0 2.0 0.0 1 1786.7 178 ad6 0.0 0.0 0.0 0.0 1 0.0 0 And so on for about 10 minutes. Then the disk i/o is reverted to normal: ad6 139.4 0.0 8860.5 0.0 1 4.4 61 ad6 167.3 0.0 10528.7 0.0 1 3.3 55 ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 ad6 163.4 0.0 10334.9 0.0 1 4.4 72 ad6 157.4 0.0 9770.7 0.0 1 5.0 78 ad6 108.5 0.0 6886.8 0.0 0 3.9 43 ad6 101.6 0.0 6381.4 0.0 0 2.6 27 ad6 109.6 0.0 7013.9 0.0 0 2.0 22 ad6 121.4 0.0 7769.7 0.0 0 2.4 29 ad6 92.5 0.0 5922.6 0.0 1 3.4 31 ad6 122.4 19.9 7833.0 1273.7 0 3.9 54 ad6 83.6 0.0 5349.5 0.0 0 3.9 33 ad6 5.0 0.0 318.4 0.0 0 8.1 4 There are no ata error messages neither in the system log, nor on the console. The manufacture's diagnostic test is passed on ad6 without any errors. The ad6 also contains swap partition. I have tried to run several (10..20) instances of dd, which read and write data from and to the swap partition simultaneously, but it has not called the lockup. So there is a probability that this problem is ZFS related. I have been forced to switch ad6 to the offline state... :( Any suggestions on this problem? -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 13:37:41 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6385A1065670 for ; Thu, 17 Dec 2009 13:37:41 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from mail.clearchain.com (leo.clearchain.com [199.73.29.74]) by mx1.freebsd.org (Postfix) with ESMTP id 220948FC08 for ; Thu, 17 Dec 2009 13:37:40 +0000 (UTC) Received: from [192.168.155.20] (ppp121-45-107-111.lns20.adl6.internode.on.net [121.45.107.111]) (authenticated bits=0) by mail.clearchain.com (8.14.3/8.14.3) with ESMTP id nBHDbXpv042256 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 18 Dec 2009 00:07:37 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <4B2A341C.5000802@clearchain.com> Date: Fri, 18 Dec 2009 00:07:32 +1030 From: Benjamin Close User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.7pre) Gecko/20091214 Lightning/1.0b1pre Shredder/3.0.1pre MIME-Version: 1.0 To: Alexander Zagrebin References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> In-Reply-To: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.clearchain.com [199.73.29.74]); Fri, 18 Dec 2009 00:07:39 +1030 (CST) Cc: freebsd-current@freebsd.org Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 13:37:41 -0000 On 17/12/09 19:30, Alexander Zagrebin wrote: > Hi! > > I use onboard ICH7 SATA controller with two disks attached: > > atapci1: port > 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0-0x30af irq 19 > at device 31.2 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ad4: 1430799MB at ata2-master SATA150 > ad6: 1430799MB at ata3-master SATA150 > > The disks are used for mirrored ZFS pool. > I have noticed that the system periodically locks up on disk operations. > After approx. 10 min of very slow disk i/o (several KB/s) the speed of disk > operations restores to normal. > gstat has shown that the problem is in ad6. > For example, there is a filtered output of iostat -x 1: > > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 818.6 0.0 10840.2 0.0 0 0.4 34 > ad6 300.6 642.0 3518.5 24830.3 50 24.8 72 > ad6 1.0 639.3 63.7 17118.3 0 62.1 98 > ad6 404.5 4.0 6837.7 4.0 0 0.5 18 > ad6 504.5 0.0 13667.2 0.0 1 0.7 32 > ad6 633.3 0.0 13190.3 0.0 1 0.7 38 > ad6 416.3 384.5 8134.7 24606.2 0 16.3 57 > ad6 538.9 76.7 9772.8 2982.2 55 2.9 40 > ad6 31.9 929.5 801.0 37498.6 0 27.2 82 > ad6 635.5 0.0 13087.1 0.0 1 0.6 35 > ad6 579.6 0.0 16669.8 0.0 0 0.8 43 > ad6 603.6 0.0 11697.4 0.0 1 0.7 40 > ad6 538.0 0.0 10438.7 0.0 0 0.9 47 > ad6 30.9 898.4 868.6 40585.4 0 36.6 78 > ad6 653.3 86.6 8566.6 202.7 1 0.8 40 > ad6 737.1 0.0 6429.4 0.0 1 0.6 42 > ad6 717.1 0.0 3958.7 0.0 0 0.5 36 > ad6 1179.5 0.0 2058.9 0.0 0 0.1 15 > ad6 1191.2 0.0 1079.6 0.0 1 0.1 15 > ad6 985.1 0.0 5093.9 0.0 0 0.2 23 > ad6 761.8 0.0 9801.3 0.0 1 0.4 31 > ad6 698.7 0.0 9215.1 0.0 0 0.4 30 > ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 > ad6 3.0 762.8 191.2 28732.3 0 57.6 99 > ad6 10.0 4.0 163.9 4.0 1 1.6 2 > > Before this line we have a normal operations. > Then the behaviour of ad6 changes (pay attention to high average access time > and percent of "busy" significantly greater than 100): > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 0.5 0.0 1 1798.3 179 > ad6 1.0 0.0 1.5 0.0 1 1775.4 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 10.0 0.0 75.2 0.0 1 180.3 180 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 83.7 0.0 862.9 0.0 1 21.4 179 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 63.7 0.0 1 1707.4 170 > ad6 1.0 0.0 9.0 0.0 0 1791.0 178 > ad6 10.9 0.0 172.2 0.0 2 0.2 0 > ad6 24.9 0.0 553.7 0.0 1 143.3 179 > ad6 0.0 0.0 0.0 0.0 7 0.0 0 > ad6 2.0 23.9 32.4 1529.9 1 336.3 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 68.7 0.0 1322.8 0.0 1 26.3 181 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 27.9 0.0 193.7 0.0 1 61.6 172 > ad6 1.0 0.0 2.5 0.0 1 1777.4 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 2.0 0.0 1 1786.9 178 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 2.0 0.0 6.5 0.0 1 899.4 179 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 2.0 0.0 1 1786.7 178 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > And so on for about 10 minutes. > Then the disk i/o is reverted to normal: > > ad6 139.4 0.0 8860.5 0.0 1 4.4 61 > ad6 167.3 0.0 10528.7 0.0 1 3.3 55 > ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 > ad6 163.4 0.0 10334.9 0.0 1 4.4 72 > ad6 157.4 0.0 9770.7 0.0 1 5.0 78 > ad6 108.5 0.0 6886.8 0.0 0 3.9 43 > ad6 101.6 0.0 6381.4 0.0 0 2.6 27 > ad6 109.6 0.0 7013.9 0.0 0 2.0 22 > ad6 121.4 0.0 7769.7 0.0 0 2.4 29 > ad6 92.5 0.0 5922.6 0.0 1 3.4 31 > ad6 122.4 19.9 7833.0 1273.7 0 3.9 54 > ad6 83.6 0.0 5349.5 0.0 0 3.9 33 > ad6 5.0 0.0 318.4 0.0 0 8.1 4 > > There are no ata error messages neither in the system log, nor on the > console. > The manufacture's diagnostic test is passed on ad6 without any errors. > The ad6 also contains swap partition. > I have tried to run several (10..20) instances of dd, which read and write > data > from and to the swap partition simultaneously, but it has not called the > lockup. > So there is a probability that this problem is ZFS related. > > I have been forced to switch ad6 to the offline state... :( > > Any suggestions on this problem? > I also have been experiencing the same problem with a different disk/controller (via mpt on a vmware machine). During the same period I notice that system cpu usage hits 80+% and top shows the zfskern process being the main culprit. At the same time I've discovered the kstat.zfs.misc.arcstats.memory_throttle_count sysctl rising. Arc is also normally close to the arc_max limit. Looking at the code, I'm wondering if EAGAIN really should have been ERESTART in the case when a reclaim was needed: contrib/opensolaris/uts/common/fs/zfs/arc.c: line 3314 /* * If we are in pageout, we know that memory is already tight, * the arc is already going to be evicting, so we just want to * continue to let page writes occur as quickly as possible. */ if (curproc == pageproc) { if (page_load > available_memory / 4) return (ERESTART); /* Note: reserve is inflated, so we deflate */ page_load += reserve / 8; return (0); } else if (page_load > 0 && arc_reclaim_needed()) { /* memory is low, delay before restarting */ ARCSTAT_INCR(arcstat_memory_throttle_count, 1); return (EAGAIN); } From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 13:53:07 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20BD7106568D for ; Thu, 17 Dec 2009 13:53:07 +0000 (UTC) (envelope-from prvs=1602d8d4d9=killing@multiplay.co.uk) Received: from mail1.multiplay.co.uk (mail1.multiplay.co.uk [85.236.96.23]) by mx1.freebsd.org (Postfix) with ESMTP id 79B608FC2D for ; Thu, 17 Dec 2009 13:53:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=multiplay.co.uk; s=Multiplay; t=1261057348; x=1261662148; q=dns/txt; h=Received: Message-ID:From:To:References:Subject:Date:MIME-Version: Content-Type:Content-Transfer-Encoding; bh=C2bnwXmD9bwRDexGQDs4O 2nevh49Gy9Fik5EexMZBrk=; b=INPVavPw9owcVNn1Q8bgGQAp0xtqybL2lr9cz LsragszHrIsr/Bc3ADupD0UG4YFzSP+fg8DKvQfk4ssUzCJXCLY/ziZ6n6BcrRDJ E9efeRFBKjFse4ISPrYMruosm3ULeKA7mvWT6dxUcZ0JUTPITQ9E7PLgjPcz7wzN M0RV+Q= X-MDAV-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 13:42:28 +0000 Received: from r2d2 by mail1.multiplay.co.uk (MDaemon PRO v10.0.4) with ESMTP id md50008878490.msg for ; Thu, 17 Dec 2009 13:42:26 +0000 X-Spam-Processed: mail1.multiplay.co.uk, Thu, 17 Dec 2009 13:42:26 +0000 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: Killing@multiplay.co.uk X-MDRemoteIP: 213.123.247.160 X-Return-Path: prvs=1602d8d4d9=killing@multiplay.co.uk X-Envelope-From: killing@multiplay.co.uk X-MDaemon-Deliver-To: freebsd-current@freebsd.org Message-ID: <4497C65B2FB14CE781BABF07F396841D@multiplay.co.uk> From: "Steven Hartland" To: "Alexander Zagrebin" , References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> Date: Thu, 17 Dec 2009 13:42:24 -0000 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="koi8-r"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Cc: Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA relatedproblem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 13:53:07 -0000 We see a very similar pattern on straight ufs disks on an areca controller. Machine console becomes totally unresponsive 30 or so seconds at a time, so it maybe something more intergral to device operation, buffercache or something? The IO load on the machine is being generated by updating rrds files in mrtg for a few hundred switch ports and a few thousand servers. device r/s w/s kr/s kw/s wait svc_t b da0 0.0 0.0 0.0 0.0 1584 0.0 0 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 342.6 0.0 5577.1 1241 7325.5 241 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 0.0 0.0 0.0 1241 0.0 0 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 0.0 0.0 0.0 1241 0.0 0 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 930.8 0.0 15165.2 309 10483.0 322 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 267.7 0.0 4330.7 41 10952.8 41 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 232.7 0.0 3739.4 0 2207.4 158 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 0.0 0.0 0.0 0 0.0 0 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 extended device statistics device r/s w/s kr/s kw/s wait svc_t b da0 0.0 0.0 0.0 0.0 0 0.0 0 pass0 0.0 0.0 0.0 0.0 0 0.0 0 pass1 0.0 0.0 0.0 0.0 0 0.0 0 ----- Original Message ----- From: "Alexander Zagrebin" To: Sent: Thursday, December 17, 2009 9:00 AM Subject: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA relatedproblem) > Hi! > > I use onboard ICH7 SATA controller with two disks attached: > > atapci1: port > 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0-0x30af irq 19 > at device 31.2 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ad4: 1430799MB at ata2-master SATA150 > ad6: 1430799MB at ata3-master SATA150 > > The disks are used for mirrored ZFS pool. > I have noticed that the system periodically locks up on disk operations. > After approx. 10 min of very slow disk i/o (several KB/s) the speed of disk > operations restores to normal. > gstat has shown that the problem is in ad6. > For example, there is a filtered output of iostat -x 1: > > extended device statistics > device r/s w/s kr/s kw/s wait svc_t %b > ad6 818.6 0.0 10840.2 0.0 0 0.4 34 > ad6 300.6 642.0 3518.5 24830.3 50 24.8 72 > ad6 1.0 639.3 63.7 17118.3 0 62.1 98 > ad6 404.5 4.0 6837.7 4.0 0 0.5 18 > ad6 504.5 0.0 13667.2 0.0 1 0.7 32 > ad6 633.3 0.0 13190.3 0.0 1 0.7 38 > ad6 416.3 384.5 8134.7 24606.2 0 16.3 57 > ad6 538.9 76.7 9772.8 2982.2 55 2.9 40 > ad6 31.9 929.5 801.0 37498.6 0 27.2 82 > ad6 635.5 0.0 13087.1 0.0 1 0.6 35 > ad6 579.6 0.0 16669.8 0.0 0 0.8 43 > ad6 603.6 0.0 11697.4 0.0 1 0.7 40 > ad6 538.0 0.0 10438.7 0.0 0 0.9 47 > ad6 30.9 898.4 868.6 40585.4 0 36.6 78 > ad6 653.3 86.6 8566.6 202.7 1 0.8 40 > ad6 737.1 0.0 6429.4 0.0 1 0.6 42 > ad6 717.1 0.0 3958.7 0.0 0 0.5 36 > ad6 1179.5 0.0 2058.9 0.0 0 0.1 15 > ad6 1191.2 0.0 1079.6 0.0 1 0.1 15 > ad6 985.1 0.0 5093.9 0.0 0 0.2 23 > ad6 761.8 0.0 9801.3 0.0 1 0.4 31 > ad6 698.7 0.0 9215.1 0.0 0 0.4 30 > ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 > ad6 3.0 762.8 191.2 28732.3 0 57.6 99 > ad6 10.0 4.0 163.9 4.0 1 1.6 2 > > Before this line we have a normal operations. > Then the behaviour of ad6 changes (pay attention to high average access time > and percent of "busy" significantly greater than 100): > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 0.5 0.0 1 1798.3 179 > ad6 1.0 0.0 1.5 0.0 1 1775.4 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 10.0 0.0 75.2 0.0 1 180.3 180 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 83.7 0.0 862.9 0.0 1 21.4 179 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 63.7 0.0 1 1707.4 170 > ad6 1.0 0.0 9.0 0.0 0 1791.0 178 > ad6 10.9 0.0 172.2 0.0 2 0.2 0 > ad6 24.9 0.0 553.7 0.0 1 143.3 179 > ad6 0.0 0.0 0.0 0.0 7 0.0 0 > ad6 2.0 23.9 32.4 1529.9 1 336.3 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 68.7 0.0 1322.8 0.0 1 26.3 181 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 27.9 0.0 193.7 0.0 1 61.6 172 > ad6 1.0 0.0 2.5 0.0 1 1777.4 177 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 2.0 0.0 1 1786.9 178 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 2.0 0.0 6.5 0.0 1 899.4 179 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > ad6 1.0 0.0 2.0 0.0 1 1786.7 178 > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > And so on for about 10 minutes. > Then the disk i/o is reverted to normal: > > ad6 139.4 0.0 8860.5 0.0 1 4.4 61 > ad6 167.3 0.0 10528.7 0.0 1 3.3 55 > ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 > ad6 163.4 0.0 10334.9 0.0 1 4.4 72 > ad6 157.4 0.0 9770.7 0.0 1 5.0 78 > ad6 108.5 0.0 6886.8 0.0 0 3.9 43 > ad6 101.6 0.0 6381.4 0.0 0 2.6 27 > ad6 109.6 0.0 7013.9 0.0 0 2.0 22 > ad6 121.4 0.0 7769.7 0.0 0 2.4 29 > ad6 92.5 0.0 5922.6 0.0 1 3.4 31 > ad6 122.4 19.9 7833.0 1273.7 0 3.9 54 > ad6 83.6 0.0 5349.5 0.0 0 3.9 33 > ad6 5.0 0.0 318.4 0.0 0 8.1 4 > > There are no ata error messages neither in the system log, nor on the > console. > The manufacture's diagnostic test is passed on ad6 without any errors. > The ad6 also contains swap partition. > I have tried to run several (10..20) instances of dd, which read and write > data > from and to the swap partition simultaneously, but it has not called the > lockup. > So there is a probability that this problem is ZFS related. > > I have been forced to switch ad6 to the offline state... :( > > Any suggestions on this problem? > > -- > Alexander Zagrebin > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > ================================================ 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-current@FreeBSD.ORG Thu Dec 17 17:15:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D5935106566B for ; Thu, 17 Dec 2009 17:15:24 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id 951D88FC1D for ; Thu, 17 Dec 2009 17:15:24 +0000 (UTC) Received: from desktop1.alchemy-networks.co.uk ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NLJyY-000AjF-6s for freebsd-current@freebsd.org; Thu, 17 Dec 2009 17:17:18 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes References: Date: Thu, 17 Dec 2009 17:15:19 -0000 To: "freebsd-current@freebsd.org" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Message-ID: In-Reply-To: User-Agent: Opera Mail/10.01 (FreeBSD) Subject: Call for help AR5416 (AR9285) to improve freebsd's standing on latest range of netbooks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 17:15:24 -0000 Hey all, I have found an issue with the 'kite' AR9285 driver, infact it required a patch to even get the driver to hook the device, the AR9285 is present in the latest Asus EEEPC's and also the latest Acer Aspire ones, none of these networks will work with the current implementation. Im calling for help from anyone who would be able to lend a hand to get this card supported as it should be under ath_hal AR5416, I find it would be deeply beneficial to any user using a netbook, which is currently become quite a trend. Also please note that the driver is already 'implemented' in 8.0-current its just tracking down what is causing one issue: Dec 17 15:07:21 laptop3 kernel: ath_hal_wait: timeout on reg 0x9860: 0xffffffff & 0x00000001 != 0x00000000 Dec 17 15:07:21 laptop3 kernel: first cal Dec 17 15:07:21 laptop3 kernel: ar5416InitCal: offset calibration did not complete in 1ms; noisy environment? Please send me back an email or drop me a line of IRC (irc.freenode.net ##freebsd (nickname: daemon)) if you would like to help out -- Thank you for your time -- Paul G Webster -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 17:48:10 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 489241065676 for ; Thu, 17 Dec 2009 17:48:10 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 04C148FC0A for ; Thu, 17 Dec 2009 17:48:09 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NLKSM-0001bp-FU for freebsd-current@freebsd.org; Thu, 17 Dec 2009 18:48:06 +0100 Received: from 78-1-170-225.adsl.net.t-com.hr ([78.1.170.225]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Dec 2009 18:48:06 +0100 Received: from ivoras by 78-1-170-225.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 17 Dec 2009 18:48:06 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 17 Dec 2009 18:47:43 +0100 Lines: 31 Message-ID: References: <200912161721.53540.jhb@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 78-1-170-225.adsl.net.t-com.hr User-Agent: Thunderbird 2.0.0.21 (X11/20090612) In-Reply-To: <200912161721.53540.jhb@freebsd.org> Sender: news Subject: Re: NOTES checker X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 17:48:10 -0000 John Baldwin wrote: > I wrote a little script today that crawls through sys/conf/files*, > sys/conf/options*, sys/conf/NOTES, and sys/*/conf/NOTES looking for devices > or options that are not tested in all the places they are valid. If folks > are interested I can commit it to src/tools. At the moment we have 300+ > violations in HEAD. :) The first few look like this: What does "tested" mean in this context? I'm pretty sure some of the devices/drivers in the list work but that's probably not it :) > > WARN: Attempt to change type of gdc from option to device at /home/jhb/work/freebsd/svn/head/sys/pc98/conf/NOTES:307 > Previous type set at /home/jhb/work/freebsd/svn/head/sys/conf/options.pc98:70 > WARN: device acpi_aiboost is defined globally but only tested in i386 NOTES > WARN: device acpi_asus is defined globally but only tested in i386 NOTES > WARN: device acpi_dock is defined globally but only tested in i386 NOTES > WARN: device acpi_fujitsu is defined globally but only tested in i386 NOTES > WARN: device acpi_hp is defined globally but only tested in i386 NOTES > WARN: device acpi_ibm is defined globally but only tested in i386 NOTES > WARN: option ACPI_MAX_TASKS is defined globally but never tested > WARN: option ACPI_MAX_THREADS is defined globally but never tested > WARN: device acpi_panasonic is defined globally but only tested in i386 NOTES > WARN: device acpi_sony is defined globally but only tested in i386 NOTES > WARN: device acpi_toshiba is defined globally but only tested in i386 NOTES > WARN: device acpi_video is defined globally but only tested in i386 NOTES > WARN: device acpi_wmi is defined globally but only tested in i386 NOTES > WARN: ad7418 is defined globally but never tested > WARN: ada is defined globally but never tested > WARN: option ADAPTIVE_LOCKMGRS is defined globally but never tested > WARN: adlink is defined globally but never tested > From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 17:08:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 323DD1065692 for ; Thu, 17 Dec 2009 17:08:44 +0000 (UTC) (envelope-from paul.g.webster@googlemail.com) Received: from mail-ew0-f226.google.com (mail-ew0-f226.google.com [209.85.219.226]) by mx1.freebsd.org (Postfix) with ESMTP id B7DC48FC1A for ; Thu, 17 Dec 2009 17:08:43 +0000 (UTC) Received: by ewy26 with SMTP id 26so1460231ewy.3 for ; Thu, 17 Dec 2009 09:08:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:content-type:to:subject:date :mime-version:content-transfer-encoding:from:organization:message-id :user-agent; bh=Uiy4o58YUmxaGNabP8ru9aOzLk+2p7bjznjwBeLDrHQ=; b=UpgiHbEMWexD4IjjE1HzVMkSY/S/PZ3hWOhMC/2nuo7Q9+iTkYqnFGSZsZG2Jr8qvo YfznT7nJx1/H+ywiwK99EWvuIqnvW8ZRW/QIYU6g6tOqNRXOkA/0D9hOKqDpMXa39gLe zc/87onq9befxXQrsVn4e6mzSGuHyI6KZCn2w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=content-type:to:subject:date:mime-version:content-transfer-encoding :from:organization:message-id:user-agent; b=p0XfJYBd2fAZuRjlNhcSrKASLN9gIrxfGUYh7bGu9OpqsahaOYpDi4CywcCAPMqILo B+/NlJXP+AqQDzix85m9W27om94sd9niik1hSqQs/+nJgsR42aXOe4AeKbKuX8QVmfXs CYHte1EfoD0/yKfDjT9E22BJ9XpdRkQmDAaKI= Received: by 10.213.37.19 with SMTP id v19mr3145962ebd.64.1261067934172; Thu, 17 Dec 2009 08:38:54 -0800 (PST) Received: from desktop1.alchemy-networks.co.uk (cpc4-linc11-2-0-cust478.12-1.cable.virginmedia.com [86.12.85.223]) by mx.google.com with ESMTPS id 10sm3519904eyz.7.2009.12.17.08.38.52 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Dec 2009 08:38:53 -0800 (PST) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-current@freebsd.org Date: Thu, 17 Dec 2009 16:38:52 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: "Paul G Webster" Organization: WorldForMe Message-ID: User-Agent: Opera Mail/10.01 (FreeBSD) X-Mailman-Approved-At: Thu, 17 Dec 2009 18:58:36 +0000 Subject: Call for help AR5416 (AR9285) to improve freebsd's standing on latest range of netbooks X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 17:08:44 -0000 Hey all, I have found an issue with the 'kite' AR9285 driver, infact it required a patch to even get the driver to hook the device, the AR9285 is present in the latest Asus EEEPC's and also the latest Acer Aspire ones, none of these networks will work with the current implementation. Im calling for help from anyone who would be able to lend a hand to get this card supported as it should be under ath_hal AR5416, I find it would be deeply beneficial to any user using a netbook, which is currently become quite a trend. Also please note that the driver is already 'implemented' in 8.0-current its just tracking down what is causing one issue: Dec 17 15:07:21 laptop3 kernel: ath_hal_wait: timeout on reg 0x9860: 0xffffffff & 0x00000001 != 0x00000000 Dec 17 15:07:21 laptop3 kernel: first cal Dec 17 15:07:21 laptop3 kernel: ar5416InitCal: offset calibration did not complete in 1ms; noisy environment? Please send me back an email or drop me a line of IRC (irc.freenode.net ##freebsd (nickname: daemon)) if you would like to help out -- Thank you for your time -- Paul G Webster -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Thu Dec 17 22:27:35 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10C7310656EF; Thu, 17 Dec 2009 22:27:35 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (uffner.com [66.208.243.25]) by mx1.freebsd.org (Postfix) with ESMTP id C0CDE8FC25; Thu, 17 Dec 2009 22:27:34 +0000 (UTC) Received: from xiombarg.uffner.com (static-71-162-143-94.phlapa.fios.verizon.net [71.162.143.94]) (authenticated bits=0) by eris.uffner.com (8.14.3/8.14.3) with ESMTP id nBHMThj2084492 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Dec 2009 17:29:48 -0500 (EST) (envelope-from tom@uffner.com) Message-ID: <4B2AB04F.3010705@uffner.com> Date: Thu, 17 Dec 2009 17:27:27 -0500 From: Tom Uffner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20090925 SeaMonkey/1.1.18 MIME-Version: 1.0 To: Alexander Motin References: <4B1671EE.1010301@FreeBSD.org> <4B25AE1A.80206@uffner.com> <4B262BAC.9040808@FreeBSD.org> <4B282EF3.8050008@uffner.com> <4B28B056.60606@FreeBSD.org> In-Reply-To: <4B28B056.60606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Testing CAM wrapper for ata(4) controller drivers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Dec 2009 22:27:35 -0000 Alexander Motin wrote: > --- ata-promise.c.prev 2009-12-15 21:35:43.000000000 +0200 > +++ ata-promise.c 2009-12-15 21:35:24.000000000 +0200 > @@ -957,6 +957,7 @@ ata_promise_mio_dmainit(device_t dev) > ata_dmainit(dev); > /* note start and stop are not used here */ > ch->dma.setprd = ata_promise_mio_setprd; > + ch->dma.max_iosize = 65536; > } that fixes it both w/ and w/o "options ATA_CAM" Thank you very much. tom From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 08:15:24 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7EFCA106566B for ; Fri, 18 Dec 2009 08:15:24 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 028A98FC0A for ; Fri, 18 Dec 2009 08:15:23 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLXzc-000Ow8-D2; Fri, 18 Dec 2009 11:15:20 +0300 From: "Alexander Zagrebin" To: "'Benjamin Close'" , References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <4B2A341C.5000802@clearchain.com> Date: Fri, 18 Dec 2009 11:15:19 +0300 Message-ID: <6D3B0162A2134CAEA9F4DF5BC03707AA@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/Hh1AKfOChFi2RS69+nZgEwxnhgAjGiVQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4B2A341C.5000802@clearchain.com> Cc: Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 08:15:24 -0000 Big thanks for your reply! > > I use onboard ICH7 SATA controller with two disks attached: > > > > atapci1: port > > > 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0 > -0x30af irq 19 > > at device 31.2 on pci0 > > atapci1: [ITHREAD] > > ata2: on atapci1 > > ata2: [ITHREAD] > > ata3: on atapci1 > > ata3: [ITHREAD] > > ad4: 1430799MB at ata2-master SATA150 > > ad6: 1430799MB at ata3-master SATA150 > > > > The disks are used for mirrored ZFS pool. > > I have noticed that the system periodically locks up on > disk operations. > > After approx. 10 min of very slow disk i/o (several KB/s) > the speed of disk > > operations restores to normal. > > gstat has shown that the problem is in ad6. > > For example, there is a filtered output of iostat -x 1: > > > > extended device statistics > > device r/s w/s kr/s kw/s wait svc_t %b > > ad6 985.1 0.0 5093.9 0.0 0 0.2 23 > > ad6 761.8 0.0 9801.3 0.0 1 0.4 31 > > ad6 698.7 0.0 9215.1 0.0 0 0.4 30 > > ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 > > ad6 3.0 762.8 191.2 28732.3 0 57.6 99 > > ad6 10.0 4.0 163.9 4.0 1 1.6 2 > > > > Before this line we have a normal operations. > > Then the behaviour of ad6 changes (pay attention to high > average access time > > and percent of "busy" significantly greater than 100): > > > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > ad6 1.0 0.0 0.5 0.0 1 1798.3 179 > > ad6 1.0 0.0 1.5 0.0 1 1775.4 177 > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > ad6 10.0 0.0 75.2 0.0 1 180.3 180 > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > ad6 1.0 0.0 2.0 0.0 1 1786.7 178 > > ad6 0.0 0.0 0.0 0.0 1 0.0 0 > > > > And so on for about 10 minutes. > > Then the disk i/o is reverted to normal: > > > > ad6 139.4 0.0 8860.5 0.0 1 4.4 61 > > ad6 167.3 0.0 10528.7 0.0 1 3.3 55 > > ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 > > ad6 163.4 0.0 10334.9 0.0 1 4.4 72 > > ad6 157.4 0.0 9770.7 0.0 1 5.0 78 > > ad6 108.5 0.0 6886.8 0.0 0 3.9 43 > > > > There are no ata error messages neither in the system log, > nor on the > > console. > > The manufacture's diagnostic test is passed on ad6 without > any errors. > > The ad6 also contains swap partition. > > I have tried to run several (10..20) instances of dd, which > read and write > > data > > from and to the swap partition simultaneously, but it has > not called the > > lockup. > > So there is a probability that this problem is ZFS related. > > > > I have been forced to switch ad6 to the offline state... :( > > > > Any suggestions on this problem? > > > I also have been experiencing the same problem with a different > disk/controller (via mpt on a vmware machine). During the > same period I > notice that system cpu usage hits 80+% and top shows the > zfskern process > being the main culprit. At the same time I've discovered the > kstat.zfs.misc.arcstats.memory_throttle_count sysctl rising. > Arc is also > normally close to the arc_max limit. My case has differences. 1. CPU usage is near 0% 2. zfs's sysctls doesn't change significantly during "normal operation" -> "lockup" -> "normal" transition 3. ARC size is far from its limits, kstat.zfs.misc.arcstats.memory_throttle_count: 0 Here my actions, observations and conclusions: 1. I have tried to change placements of disks on sata channels. Nothing has changed - the problems still on WD15EADS, although it became ad4. So issue isn't in south bridge, sata cables and so on. 2. I have tried to detach ad6 from the pool, to zero system area, and to reattach it again. Of course, resilvering was started. During resilvering 250 GB was copied without lockups and delays. While resilvering, I have tried periodically to load drive with a read operations (dd if=/dev/ad6 of=/dev/null ...). But after resilvering and several minutes of normal mirror operation, lockups appeared again. So drive is seems to be ok and we have a software problem? 3. I have noticed that lockups often happens during postgresql activity. postgresql often uses sync. So I have tried to disable ZIL. No success. 4. "IDE LED" is constantly on during lockups. So it is really read/write delays. 5. I see two variants of zfskern's state: a) it is constantly in the vgeom:io b) it is in either zio->io_ state (when active), or in tx->tx_s (when idle). During lockups it is mostly in zio->io_. What the difference with vgeom:io and zio->io_/tx->tx_s? May be a problem is in ata? WD15EADS is a "green" series of drives. May be i have a problem with its power management? Is there a method to completely reset sata channel and drive? atacontrol reinit will do it? Any help is welcomed. -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 08:21:40 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B920106568B for ; Fri, 18 Dec 2009 08:21:40 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id EFEAE8FC34 for ; Fri, 18 Dec 2009 08:21:39 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLY5i-000PDr-6o; Fri, 18 Dec 2009 11:21:38 +0300 From: "Alexander Zagrebin" To: "'Steven Hartland'" , References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <4497C65B2FB14CE781BABF07F396841D@multiplay.co.uk> Date: Fri, 18 Dec 2009 11:21:37 +0300 Message-ID: <0A946094C9EB449CB37853E5B58F7BBE@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/HsaHeN9uzeRGSuqYOhxjGwliTgAm43rg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4497C65B2FB14CE781BABF07F396841D@multiplay.co.uk> Cc: Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA relatedproblem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 08:21:40 -0000 Big thanks for your reply! > We see a very similar pattern on straight ufs disks on an > areca controller. Machine > console becomes totally unresponsive 30 or so seconds at a > time, so it maybe > something more intergral to device operation, buffercache or > something? In my case console is responsive, but there are delays when starting command due to disk busy. > The IO load on the machine is being generated by updating > rrds files in mrtg > for a few hundred switch ports and a few thousand servers. I'm noticing delays (lockups) even if system is idle. -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 08:49:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 065DA1065679 for ; Fri, 18 Dec 2009 08:49:49 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id ADC178FC16 for ; Fri, 18 Dec 2009 08:49:48 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLYWx-0000gf-DU for freebsd-current@freebsd.org; Fri, 18 Dec 2009 11:49:47 +0300 From: "Alexander Zagrebin" To: Date: Fri, 18 Dec 2009 11:49:47 +0300 Message-ID: <398F182D4FC14D43A1CFD89C4D69817C@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/vwzdW4/7m1fFQAWi1WRgcxfirQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 Subject: ZFS and UFS on the same box. Cache memory allocation issue. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 08:49:49 -0000 There is an interesting issue when UFS and ZFS filesystems coexists on the same box. ZFS and UFS independently allocates memory for its cache. Suppose we actively used UFS. UFS allocates almost all free memory for its cache. Its size can be indirectly evaluated with "inactive" memory size. Then we began to use ZFS. It seems that ZFS allocates memory for ARC _only_ from the "free" memory. But now there is almost no no "free" memory (UFS has eaten it). So ZFS operates very ineffectively due to very little ARC, which can be indirectly evaluated with "wired" memory size. To workaround this I've tried to run small program, that simply allocates, for example, 500MB of memory and frees it. As result UFS returns memory to "free" pool and ZFS can allocate it for ARC. It significantly increases ZFS performance. Is there an another workaround? -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 08:57:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 696A91065670 for ; Fri, 18 Dec 2009 08:57:49 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from bellagio.open2view.net (bellagio.open2view.net [210.48.79.75]) by mx1.freebsd.org (Postfix) with ESMTP id 16B198FC1B for ; Fri, 18 Dec 2009 08:57:48 +0000 (UTC) Received: from [10.1.1.5] (ip-118-90-27-24.xdsl.xnet.co.nz [118.90.27.24]) (Authenticated sender: pmurray@nevada.net.nz) by bellagio.open2view.net (Postfix) with ESMTP id 3E2C6300949F; Fri, 18 Dec 2009 21:38:59 +1300 (NZDT) References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <4B2A341C.5000802@clearchain.com> <6D3B0162A2134CAEA9F4DF5BC03707AA@vosz.local> Message-Id: <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> From: Phil Murray To: Alexander Zagrebin In-Reply-To: <6D3B0162A2134CAEA9F4DF5BC03707AA@vosz.local> Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPhone Mail (7D11) Mime-Version: 1.0 (iPhone Mail 7D11) Date: Fri, 18 Dec 2009 21:39:40 +1300 Cc: "freebsd-current@freebsd.org" Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 08:57:49 -0000 On 18/12/2009, at 9:15 PM, "Alexander Zagrebin" wrote: > Big thanks for your reply! > >>> I use onboard ICH7 SATA controller with two disks attached: >>> >>> atapci1: port >>> >> 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0 >> -0x30af irq 19 >>> at device 31.2 on pci0 >>> atapci1: [ITHREAD] >>> ata2: on atapci1 >>> ata2: [ITHREAD] >>> ata3: on atapci1 >>> ata3: [ITHREAD] >>> ad4: 1430799MB at ata2-master SATA150 >>> ad6: 1430799MB at ata3-master SATA150 >>> >>> The disks are used for mirrored ZFS pool. >>> I have noticed that the system periodically locks up on >> disk operations. >>> After approx. 10 min of very slow disk i/o (several KB/s) >> the speed of disk >>> operations restores to normal. >>> gstat has shown that the problem is in ad6. >>> For example, there is a filtered output of iostat -x 1: >>> >>> extended device statistics >>> device r/s w/s kr/s kw/s wait svc_t %b >>> ad6 985.1 0.0 5093.9 0.0 0 0.2 23 >>> ad6 761.8 0.0 9801.3 0.0 1 0.4 31 >>> ad6 698.7 0.0 9215.1 0.0 0 0.4 30 >>> ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 >>> ad6 3.0 762.8 191.2 28732.3 0 57.6 99 >>> ad6 10.0 4.0 163.9 4.0 1 1.6 2 >>> >>> Before this line we have a normal operations. >>> Then the behaviour of ad6 changes (pay attention to high >> average access time >>> and percent of "busy" significantly greater than 100): >>> >>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>> ad6 1.0 0.0 0.5 0.0 1 1798.3 179 >>> ad6 1.0 0.0 1.5 0.0 1 1775.4 177 >>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>> ad6 10.0 0.0 75.2 0.0 1 180.3 180 >>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>> ad6 1.0 0.0 2.0 0.0 1 1786.7 178 >>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>> >>> And so on for about 10 minutes. >>> Then the disk i/o is reverted to normal: >>> >>> ad6 139.4 0.0 8860.5 0.0 1 4.4 61 >>> ad6 167.3 0.0 10528.7 0.0 1 3.3 55 >>> ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 >>> ad6 163.4 0.0 10334.9 0.0 1 4.4 72 >>> ad6 157.4 0.0 9770.7 0.0 1 5.0 78 >>> ad6 108.5 0.0 6886.8 0.0 0 3.9 43 >>> >>> There are no ata error messages neither in the system log, >> nor on the >>> console. >>> The manufacture's diagnostic test is passed on ad6 without >> any errors. >>> The ad6 also contains swap partition. >>> I have tried to run several (10..20) instances of dd, which >> read and write >>> data >>> from and to the swap partition simultaneously, but it has >> not called the >>> lockup. >>> So there is a probability that this problem is ZFS related. >>> >>> I have been forced to switch ad6 to the offline state... :( >>> >>> Any suggestions on this problem? >>> >> I also have been experiencing the same problem with a different >> disk/controller (via mpt on a vmware machine). During the >> same period I >> notice that system cpu usage hits 80+% and top shows the >> zfskern process >> being the main culprit. At the same time I've discovered the >> kstat.zfs.misc.arcstats.memory_throttle_count sysctl rising. >> Arc is also >> normally close to the arc_max limit. > > My case has differences. > 1. CPU usage is near 0% > 2. zfs's sysctls doesn't change significantly during > "normal operation" -> "lockup" -> "normal" transition > 3. ARC size is far from its limits, > kstat.zfs.misc.arcstats.memory_throttle_count: 0 > > Here my actions, observations and conclusions: > 1. I have tried to change placements of disks on sata channels. > Nothing has changed - the problems still on WD15EADS, although it > became > ad4. > So issue isn't in south bridge, sata cables and so on. > 2. I have tried to detach ad6 from the pool, to zero system area, > and to > reattach it again. > Of course, resilvering was started. During resilvering 250 GB was > copied > without lockups > and delays. While resilvering, I have tried periodically to load > drive > with a read > operations (dd if=/dev/ad6 of=/dev/null ...). > But after resilvering and several minutes of normal mirror > operation, > lockups appeared again. > So drive is seems to be ok and we have a software problem? > 3. I have noticed that lockups often happens during postgresql > activity. > postgresql often uses sync. So I have tried to disable ZIL. > No success. > 4. "IDE LED" is constantly on during lockups. > So it is really read/write delays. > 5. I see two variants of zfskern's state: > a) it is constantly in the vgeom:io > b) it is in either zio->io_ state (when active), or in tx->tx_s > (when > idle). > During lockups it is mostly in zio->io_. > What the difference with vgeom:io and zio->io_/tx->tx_s? > > May be a problem is in ata? WD15EADS is a "green" series of drives. The WD green drives have a feature called Time Limited Error Recovery where the disk can spend several minutes trying to read a bad block etc. It plays havoc with RAID arrays which is why WD recommend you don't use the green drives in arrays. They have more info about the "feature" in the WD FAQ/knowledgebase > May be i have a problem with its power management? > Is there a method to completely reset sata channel and drive? > atacontrol reinit will do it? > > Any help is welcomed. > > -- > Alexander Zagrebin > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org > " From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 09:11:55 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7102A106568D for ; Fri, 18 Dec 2009 09:11:55 +0000 (UTC) (envelope-from pmurray@nevada.net.nz) Received: from bellagio.open2view.net (bellagio.open2view.net [210.48.79.75]) by mx1.freebsd.org (Postfix) with ESMTP id E5AD88FC1C for ; Fri, 18 Dec 2009 09:11:54 +0000 (UTC) Received: from [10.1.1.4] (ip-118-90-27-24.xdsl.xnet.co.nz [118.90.27.24]) (Authenticated sender: pmurray@nevada.net.nz) by bellagio.open2view.net (Postfix) with ESMTP id 06DA71102BE1; Fri, 18 Dec 2009 22:11:52 +1300 (NZDT) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Phil Murray In-Reply-To: <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> Date: Fri, 18 Dec 2009 22:11:52 +1300 Content-Transfer-Encoding: quoted-printable Message-Id: <6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <4B2A341C.5000802@clearchain.com> <6D3B0162A2134CAEA9F4DF5BC03707AA@vosz.local> <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> To: Phil Murray X-Mailer: Apple Mail (2.1077) Cc: "freebsd-current@freebsd.org" , Alexander Zagrebin Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 09:11:55 -0000 On 18/12/2009, at 9:39 PM, Phil Murray wrote: >=20 >=20 > On 18/12/2009, at 9:15 PM, "Alexander Zagrebin" wrote: >=20 >> Big thanks for your reply! >>=20 >>>> I use onboard ICH7 SATA controller with two disks attached: >>>>=20 >>>> atapci1: port >>>>=20 >>> 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0 >>> -0x30af irq 19 >>>> at device 31.2 on pci0 >>>> atapci1: [ITHREAD] >>>> ata2: on atapci1 >>>> ata2: [ITHREAD] >>>> ata3: on atapci1 >>>> ata3: [ITHREAD] >>>> ad4: 1430799MB at ata2-master SATA150 >>>> ad6: 1430799MB at ata3-master = SATA150 >>>>=20 >>>> The disks are used for mirrored ZFS pool. >>>> I have noticed that the system periodically locks up on >>> disk operations. >>>> After approx. 10 min of very slow disk i/o (several KB/s) >>> the speed of disk >>>> operations restores to normal. >>>> gstat has shown that the problem is in ad6. >>>> For example, there is a filtered output of iostat -x 1: >>>>=20 >>>> extended device statistics >>>> device r/s w/s kr/s kw/s wait svc_t %b >>>> ad6 985.1 0.0 5093.9 0.0 0 0.2 23 >>>> ad6 761.8 0.0 9801.3 0.0 1 0.4 31 >>>> ad6 698.7 0.0 9215.1 0.0 0 0.4 30 >>>> ad6 434.2 513.9 5903.1 13658.3 48 10.2 55 >>>> ad6 3.0 762.8 191.2 28732.3 0 57.6 99 >>>> ad6 10.0 4.0 163.9 4.0 1 1.6 2 >>>>=20 >>>> Before this line we have a normal operations. >>>> Then the behaviour of ad6 changes (pay attention to high >>> average access time >>>> and percent of "busy" significantly greater than 100): >>>>=20 >>>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>>> ad6 1.0 0.0 0.5 0.0 1 1798.3 179 >>>> ad6 1.0 0.0 1.5 0.0 1 1775.4 177 >>>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>>> ad6 10.0 0.0 75.2 0.0 1 180.3 180 >>>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>>> ad6 1.0 0.0 2.0 0.0 1 1786.7 178 >>>> ad6 0.0 0.0 0.0 0.0 1 0.0 0 >>>>=20 >>>> And so on for about 10 minutes. >>>> Then the disk i/o is reverted to normal: >>>>=20 >>>> ad6 139.4 0.0 8860.5 0.0 1 4.4 61 >>>> ad6 167.3 0.0 10528.7 0.0 1 3.3 55 >>>> ad6 60.8 411.5 3707.6 8574.8 1 19.6 87 >>>> ad6 163.4 0.0 10334.9 0.0 1 4.4 72 >>>> ad6 157.4 0.0 9770.7 0.0 1 5.0 78 >>>> ad6 108.5 0.0 6886.8 0.0 0 3.9 43 >>>>=20 >>>> There are no ata error messages neither in the system log, >>> nor on the >>>> console. >>>> The manufacture's diagnostic test is passed on ad6 without >>> any errors. >>>> The ad6 also contains swap partition. >>>> I have tried to run several (10..20) instances of dd, which >>> read and write >>>> data >>>> from and to the swap partition simultaneously, but it has >>> not called the >>>> lockup. >>>> So there is a probability that this problem is ZFS related. >>>>=20 >>>> I have been forced to switch ad6 to the offline state... :( >>>>=20 >>>> Any suggestions on this problem? >>>>=20 >>> I also have been experiencing the same problem with a different >>> disk/controller (via mpt on a vmware machine). During the >>> same period I >>> notice that system cpu usage hits 80+% and top shows the >>> zfskern process >>> being the main culprit. At the same time I've discovered the >>> kstat.zfs.misc.arcstats.memory_throttle_count sysctl rising. >>> Arc is also >>> normally close to the arc_max limit. >>=20 >> My case has differences. >> 1. CPU usage is near 0% >> 2. zfs's sysctls doesn't change significantly during >> "normal operation" -> "lockup" -> "normal" transition >> 3. ARC size is far from its limits, >> kstat.zfs.misc.arcstats.memory_throttle_count: 0 >>=20 >> Here my actions, observations and conclusions: >> 1. I have tried to change placements of disks on sata channels. >> Nothing has changed - the problems still on WD15EADS, although it = became >> ad4. >> So issue isn't in south bridge, sata cables and so on. >> 2. I have tried to detach ad6 from the pool, to zero system area, and = to >> reattach it again. >> Of course, resilvering was started. During resilvering 250 GB was = copied >> without lockups >> and delays. While resilvering, I have tried periodically to load = drive >> with a read >> operations (dd if=3D/dev/ad6 of=3D/dev/null ...). >> But after resilvering and several minutes of normal mirror = operation, >> lockups appeared again. >> So drive is seems to be ok and we have a software problem? >> 3. I have noticed that lockups often happens during postgresql = activity. >> postgresql often uses sync. So I have tried to disable ZIL. >> No success. >> 4. "IDE LED" is constantly on during lockups. >> So it is really read/write delays. >> 5. I see two variants of zfskern's state: >> a) it is constantly in the vgeom:io >> b) it is in either zio->io_ state (when active), or in tx->tx_s = (when >> idle). >> During lockups it is mostly in zio->io_. >> What the difference with vgeom:io and zio->io_/tx->tx_s? >>=20 >> May be a problem is in ata? WD15EADS is a "green" series of drives. >=20 > The WD green drives have a feature called Time Limited Error Recovery = where the disk can spend several minutes trying to read a bad block etc. >=20 > It plays havoc with RAID arrays which is why WD recommend you don't = use the green drives in arrays. They have more info about the "feature" = in the WD FAQ/knowledgebase >=20 Sorry, TLER is the feature that 'fixes' the problem, see: = http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=3D= 1397&p_created=3D1131638613&p_sid=3DvfyE1KPj&p_accessibility=3D0&p_redirec= t=3D&p_srch=3D1&p_lva=3D&p_sp=3DcF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PS= ZwX3Jvd19jbnQ9MTcsMTcmcF9wcm9kcz0yMjcsMjk0JnBfY2F0cz0mcF9wdj0yLjI5NCZwX2N2= PSZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PXJhaWQ!&p_li=3D&p_topview=3D1 Sounds like your drive is going into the recovery procedure... >=20 >> May be i have a problem with its power management? >> Is there a method to completely reset sata channel and drive? >> atacontrol reinit will do it? >=20 >=20 >=20 >>=20 >> Any help is welcomed. >>=20 >> --=20 >> Alexander Zagrebin >>=20 >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 09:57:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6905B10656A4 for ; Fri, 18 Dec 2009 09:57:22 +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 C20F78FC19 for ; Fri, 18 Dec 2009 09:57:21 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-158-211.lns6.adl6.internode.on.net [121.45.158.211]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id nBI9vH5x082752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 18 Dec 2009 20:27:18 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: freebsd-current@freebsd.org Date: Fri, 18 Dec 2009 20:27:03 +1030 User-Agent: KMail/1.9.10 References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> <6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> In-Reply-To: <6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2587009.gNngUzBPDv"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912182027.11632.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: Alexander Zagrebin , Phil Murray Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 09:57:22 -0000 --nextPart2587009.gNngUzBPDv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 18 Dec 2009, Phil Murray wrote: > >> May be a problem is in ata? WD15EADS is a "green" series of > >> drives. > > > > The WD green drives have a feature called Time Limited Error > > Recovery where the disk can spend several minutes trying to read a > > bad block etc. > > > > It plays havoc with RAID arrays which is why WD recommend you don't > > use the green drives in arrays. They have more info about the > > "feature" in the WD FAQ/knowledgebase > > Sorry, TLER is the feature that 'fixes' the problem, see: > > http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faq >id=3D1397&p_created=3D1131638613&p_sid=3DvfyE1KPj&p_accessibility=3D0&p_re= dire >ct=3D&p_srch=3D1&p_lva=3D&p_sp=3DcF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0P= SZwX >3Jvd19jbnQ9MTcsMTcmcF9wcm9kcz0yMjcsMjk0JnBfY2F0cz0mcF9wdj0yLjI5NCZwX2N >2PSZwX3BhZ2U9MSZwX3NlYXJjaF90ZXh0PXJhaWQ!&p_li=3D&p_topview=3D1 > > > Sounds like your drive is going into the recovery procedure... I doubt this is the problem, I have WD10EADS disks in my ZFS array and I=20 see the same issue. It strikes me as extremely unlikely that both of us would have dud=20 disks.. In any case it seems to be a general problem not limited to one area of=20 the disk so a dud sector is an unlikely reason. =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 --nextPart2587009.gNngUzBPDv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLK1H35ZPcIHs/zowRArlcAJ9e1qVw7m9AwYHxTULbjKXxwBp5fQCfSVwl wi08jaz4deTvKb0fReGmJ38= =ixAF -----END PGP SIGNATURE----- --nextPart2587009.gNngUzBPDv-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 10:15:26 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1639C106568B for ; Fri, 18 Dec 2009 10:15:26 +0000 (UTC) (envelope-from emikulic@gmail.com) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [203.16.214.141]) by mx1.freebsd.org (Postfix) with ESMTP id 866348FC0A for ; Fri, 18 Dec 2009 10:15:25 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAD/kKkuWZZrw/2dsb2JhbACSFrJ2hyKIaYQtBA Received: from ppp154-240.static.internode.on.net ([150.101.154.240]) by ipmail03.adl6.internode.on.net with ESMTP; 18 Dec 2009 20:45:23 +1030 Received: by ppp154-240.static.internode.on.net (Poo-fix, from userid 1001) id 6EAB65C46; Fri, 18 Dec 2009 21:15:22 +1100 (EST) Date: Fri, 18 Dec 2009 21:15:22 +1100 From: Emil Mikulic To: Alexander Zagrebin Message-ID: <20091218101522.GD71197@dmr.ath.cx> References: <398F182D4FC14D43A1CFD89C4D69817C@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <398F182D4FC14D43A1CFD89C4D69817C@vosz.local> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org Subject: Re: ZFS and UFS on the same box. Cache memory allocation issue. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 10:15:26 -0000 On Fri, Dec 18, 2009 at 11:49:47AM +0300, Alexander Zagrebin wrote: > As result UFS returns memory to "free" pool and ZFS can allocate it for ARC. > It significantly increases ZFS performance. > > Is there an another workaround? I use: (cd /somefs && sudo umount /somefs) The umount fails, but it does clear the buffer cache! Memory reported as "inactive" by top decreases. I find this to be a really handy trick when benchmarking I/O. ;) Unfortunately, it doesn't work on the root filesystem. --Emil From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 10:25:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2E5C41065692 for ; Fri, 18 Dec 2009 10:25:14 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 4014B8FC23 for ; Fri, 18 Dec 2009 10:25:13 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLa1I-0005LQ-Im for freebsd-current@freebsd.org; Fri, 18 Dec 2009 13:25:12 +0300 From: "Alexander Zagrebin" To: References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local><4B2A341C.5000802@clearchain.com><6D3B0162A2134CAEA9F4DF5BC03707AA@vosz.local> <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> Date: Fri, 18 Dec 2009 13:25:12 +0300 Keywords: freebsd-current Message-ID: <2252F3A1382A46E9B31273F4CD30DE49@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/wFFsnbLtQRcMTEiQaKLAiGD/fgADAOjQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz> Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 10:25:16 -0000 > > May be a problem is in ata? WD15EADS is a "green" series of drives. > > The WD green drives have a feature called Time Limited Error > Recovery > where the disk can spend several minutes trying to read a bad > block etc. > > It plays havoc with RAID arrays which is why WD recommend you don't > use the green drives in arrays. They have more info about the > "feature" in the WD FAQ/knowledgebase I think this recommendation is related mostly to hardware raid controllers. Also, if to suppose the such drive errors, then "reallocated sectors count" in the SMART wouldn't be zero. But SMART data is ok. $ sudo smartctl -A /dev/ad6 | grep -e "^ID" -e "Reallocated_Sector_Ct" ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 10:33:58 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A96AF106566B; Fri, 18 Dec 2009 10:33:58 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 5C79A8FC1E; Fri, 18 Dec 2009 10:33:58 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLa9k-0005nN-Ql; Fri, 18 Dec 2009 13:33:57 +0300 From: "Alexander Zagrebin" To: "'Stefan Esser'" References: <398F182D4FC14D43A1CFD89C4D69817C@vosz.local> <4B2B52FD.7070206@FreeBSD.org> Date: Fri, 18 Dec 2009 13:33:56 +0300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/yRTxWtwX+HwHTt+R5tv7gcXixAAA5haQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4B2B52FD.7070206@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: RE: ZFS and UFS on the same box. Cache memory allocation issue. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 10:33:58 -0000 > > As result UFS returns memory to "free" pool and ZFS can > allocate it for ARC. > > It significantly increases ZFS performance. > > > > Is there an another workaround? > > do you know about the following ZFS loader tunables: > > vfs.zfs.arc_min="400M" > vfs.zfs.arc_max="500M" > > These should be added to /boot/loader.conf (and they can of course be > adjusted to make your system behave well ...) Yes, I do. vfs.zfs.arc_min would be used at this situation, but it seems that setting this sysctl doesn't help. -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 10:39:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56FD5106566B for ; Fri, 18 Dec 2009 10:39:27 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 066588FC13 for ; Fri, 18 Dec 2009 10:39:26 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLaF3-00062X-UL; Fri, 18 Dec 2009 13:39:25 +0300 From: "Alexander Zagrebin" To: "'Daniel O'Connor'" References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local><4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz><6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> <200912182027.11632.doconnor@gsoft.com.au> Date: Fri, 18 Dec 2009 13:39:25 +0300 Keywords: freebsd-current Message-ID: <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/yJtZzlq7sDI3RmqTpeKIApYg/AAAwuFw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <200912182027.11632.doconnor@gsoft.com.au> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 10:39:27 -0000 > I doubt this is the problem, I have WD10EADS disks in my ZFS > array and I > see the same issue. > > It strikes me as extremely unlikely that both of us would have dud > disks.. > > In any case it seems to be a general problem not limited to > one area of > the disk so a dud sector is an unlikely reason. Big thanks for confirmation! Your confirmation is important for me. There should be a way to define where the bug is: in the ata (or filesystem) driver or in the drive's firmware.... -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 11:31:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC6F3106566B for ; Fri, 18 Dec 2009 11:31:11 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E4CA68FC29 for ; Fri, 18 Dec 2009 11:31:10 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id NAA15400; Fri, 18 Dec 2009 13:31:07 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B2B67FB.80705@icyb.net.ua> Date: Fri, 18 Dec 2009 13:31:07 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Alexander Zagrebin References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local><4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz><6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> <200912182027.11632.doconnor@gsoft.com.au> <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> In-Reply-To: <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 11:31:11 -0000 on 18/12/2009 12:39 Alexander Zagrebin said the following: >> I doubt this is the problem, I have WD10EADS disks in my ZFS >> array and I >> see the same issue. >> >> It strikes me as extremely unlikely that both of us would have dud >> disks.. >> >> In any case it seems to be a general problem not limited to >> one area of >> the disk so a dud sector is an unlikely reason. > > Big thanks for confirmation! > Your confirmation is important for me. > There should be a way to define where the bug is: in the ata (or filesystem) > driver or in the drive's firmware.... Just another 'me too'. >From the moment I started using zfs and till this day I saw this pattern when writing lots data to zfs - first high throughput and then idle pause, and so on. I always thought that this is normal for ZFS (some buffering, grouping, etc). So I never complained :-) -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 11:48:48 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AAD7D1065676 for ; Fri, 18 Dec 2009 11:48:48 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 590A58FC13 for ; Fri, 18 Dec 2009 11:48:48 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLbK9-0009UP-WC; Fri, 18 Dec 2009 14:48:46 +0300 From: "Alexander Zagrebin" To: "'Andriy Gapon'" References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local><4C1C2598-4157-4B04-8DB8-C84F353AB8B8@nevada.net.nz><6FAA390A-1E40-4D7A-AAD5-DC72578CE974@nevada.net.nz> <200912182027.11632.doconnor@gsoft.com.au><5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> <4B2B67FB.80705@icyb.net.ua> Date: Fri, 18 Dec 2009 14:48:45 +0300 Keywords: freebsd-current Message-ID: <4F5E9203FBE0440780E31C376646F5B0@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/1bhIM7OemahPRHmeyGWtuJPGLAAAWbmQ X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4B2B67FB.80705@icyb.net.ua> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 11:48:48 -0000 > >> I doubt this is the problem, I have WD10EADS disks in my ZFS > >> array and I > >> see the same issue. > >> > >> It strikes me as extremely unlikely that both of us would have dud > >> disks.. > >> > >> In any case it seems to be a general problem not limited to > >> one area of > >> the disk so a dud sector is an unlikely reason. > > > > Big thanks for confirmation! > > Your confirmation is important for me. > > There should be a way to define where the bug is: in the > ata (or filesystem) > > driver or in the drive's firmware.... > > Just another 'me too'. > >From the moment I started using zfs and till this day I saw > this pattern when > writing lots data to zfs - first high throughput and then > idle pause, and so on. May be it usual write caching? See gstat or iostat output. At my case gstat shows abnormal value of %busy (usually approx. 180%) and very long ms/r and ms/w. -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 12:01:11 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D606B10656AA for ; Fri, 18 Dec 2009 12:01:11 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 50FC48FC26 for ; Fri, 18 Dec 2009 12:01:11 +0000 (UTC) Received: by fxm27 with SMTP id 27so2759333fxm.3 for ; Fri, 18 Dec 2009 04:01:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=4z6uGy+Kyw1/JK9sP6oJa8lVeGc4G0JGaTycUqN+9Rw=; b=TVpFAD15nBt4AxIPhgZ/a0sVR9WiVJa4WYnKlzGBCCjwOLVzWxSLY4nqW518PhiQH2 XKV7xv689iMxj2s5ZBxyPVveyHyd1LM+8/VMByZw9eg6cFJbDwkXD+q7wZdvcBJ5RaJ4 N/vMJlyupgJIZV3Y1ahejIW/JO9pCL6+hwYBw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=vERxyErR/GfL0eixelyk2eXsDXDjregLRdP96pLukMn2VJ9HO7SM2d5zDKJZ73Hlah kx21OgLxsmlt2xoVft76OTDsPPjwkAn1RoWOKon+9uIWvf599Kr0RipAUy6/yO254pZS FeacKuXKF5mtSQaLpEvtJEvbXYqPJVeoP3CGc= Received: by 10.223.14.22 with SMTP id e22mr832675faa.42.1261137670316; Fri, 18 Dec 2009 04:01:10 -0800 (PST) Received: from mavbook.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id 14sm1023880fxm.15.2009.12.18.04.01.08 (version=SSLv3 cipher=RC4-MD5); Fri, 18 Dec 2009 04:01:09 -0800 (PST) Sender: Alexander Motin Message-ID: <4B2B6F02.9050404@FreeBSD.org> Date: Fri, 18 Dec 2009 14:01:06 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Alexander Zagrebin References: <1261066981.00195934.1261053602@10.7.7.3> <1261070581.00195950.1261057201@10.7.7.3> <1261135381.00196302.1261124403@10.7.7.3> In-Reply-To: <1261135381.00196302.1261124403@10.7.7.3> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, 'Benjamin Close' Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 12:01:11 -0000 Alexander Zagrebin wrote: > May be a problem is in ata? WD15EADS is a "green" series of drives. If you don't receive TIMEOUT messages, then commands probably complete successfully. Loads above 100% may mean that requests are running for few seconds. It shouldn't happen normally. Have you tried to check whole drive surface? Have you checked SMART reports? I had a drive onece, which had so many media problems and relocated sectors, that I was unable to burn CD from it, so slow it was. Same time there was no bad sectors on that drive, reported to OS, drive handled everything. It was just extremely slow. Have you tried to rewrite _while_ drive media with dd? Some media errors could only be resolved only during write operation. > Is there a method to completely reset sata channel and drive? > atacontrol reinit will do it? Yes. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 12:05:36 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03DE41065679 for ; Fri, 18 Dec 2009 12:05:36 +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 5D6F08FC12 for ; Fri, 18 Dec 2009 12:05:34 +0000 (UTC) Received: from inchoate.gsoft.com.au (ppp121-45-158-211.lns6.adl6.internode.on.net [121.45.158.211]) (authenticated bits=0) by cain.gsoft.com.au (8.13.8/8.13.8) with ESMTP id nBIC5WQD085936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 18 Dec 2009 22:35:33 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: "Alexander Zagrebin" Date: Fri, 18 Dec 2009 22:35:18 +1030 User-Agent: KMail/1.9.10 References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <200912182027.11632.doconnor@gsoft.com.au> <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> In-Reply-To: <5C4BD0F81D1348B287B2ECD55EF283E1@vosz.local> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1351536.bXiDAqkTWd"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912182235.26915.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-current@freebsd.org Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 12:05:36 -0000 --nextPart1351536.bXiDAqkTWd Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Fri, 18 Dec 2009, Alexander Zagrebin wrote: > > I doubt this is the problem, I have WD10EADS disks in my ZFS > > array and I > > see the same issue. > > > > It strikes me as extremely unlikely that both of us would have dud > > disks.. > > > > In any case it seems to be a general problem not limited to > > one area of > > the disk so a dud sector is an unlikely reason. > > Big thanks for confirmation! > Your confirmation is important for me. > There should be a way to define where the bug is: in the ata (or > filesystem) driver or in the drive's firmware.... Yes, it would be nice to track down.. The drive is not particularly fast but single threaded sequential reads=20 and writes (on the array) are not unreasonable (220/300Mb/sec) so it=20 seems odd the penalty for accessing a busy array is so bad (of the=20 order of seconds of delay). =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 --nextPart1351536.bXiDAqkTWd Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iD8DBQBLK3AG5ZPcIHs/zowRAsOcAKCnHPImA1V+8Y9kZsolSPYKbZ7r6gCeLRdE vfvnsB6ipd0EaY32TyhEzMs= =vAA8 -----END PGP SIGNATURE----- --nextPart1351536.bXiDAqkTWd-- From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 12:27:22 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08BCB106566C; Fri, 18 Dec 2009 12:27:22 +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 C00FE8FC1A; Fri, 18 Dec 2009 12:27:21 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id DEEC06D41B; Fri, 18 Dec 2009 12:27:20 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id B28A38454E; Fri, 18 Dec 2009 13:27:20 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Ivan Voras References: <200912161721.53540.jhb@freebsd.org> Date: Fri, 18 Dec 2009 13:27:20 +0100 In-Reply-To: (Ivan Voras's message of "Thu, 17 Dec 2009 18:47:43 +0100") Message-ID: <86ljh0bh7b.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: NOTES checker X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 12:27:22 -0000 Ivan Voras writes: > John Baldwin writes: > > I wrote a little script today that crawls through sys/conf/files*, > > sys/conf/options*, sys/conf/NOTES, and sys/*/conf/NOTES looking for dev= ices > > or options that are not tested in all the places they are valid. If fo= lks > > are interested I can commit it to src/tools. At the moment we have 300+ > > violations in HEAD. :) The first few look like this: > What does "tested" mean in this context? IIUC, it means "listed in NOTES on all arches that it claims to run on". > > WARN: device acpi_aiboost is defined globally but only tested in i386 N= OTES > > WARN: device acpi_asus is defined globally but only tested in i386 NOTES > > WARN: device acpi_dock is defined globally but only tested in i386 NOTES > > WARN: device acpi_fujitsu is defined globally but only tested in i386 N= OTES > > WARN: device acpi_hp is defined globally but only tested in i386 NOTES > > WARN: device acpi_ibm is defined globally but only tested in i386 NOTES > > WARN: option ACPI_MAX_TASKS is defined globally but never tested > > WARN: option ACPI_MAX_THREADS is defined globally but never tested > > WARN: device acpi_panasonic is defined globally but only tested in i386= NOTES > > WARN: device acpi_sony is defined globally but only tested in i386 NOTES > > WARN: device acpi_toshiba is defined globally but only tested in i386 N= OTES > > WARN: device acpi_video is defined globally but only tested in i386 NOT= ES > > WARN: device acpi_wmi is defined globally but only tested in i386 NOTES The bug here is not that they aren't tested outside i386, but that they are defined globally (although some of them, perhaps even all, are also valid on amd64) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 13:31:37 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B743106566B; Fri, 18 Dec 2009 13:31:37 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id F09578FC0A; Fri, 18 Dec 2009 13:31:36 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLcve-000ESc-SF; Fri, 18 Dec 2009 16:31:34 +0300 From: "Alexander Zagrebin" To: "'Alexander Motin'" References: <1261066981.00195934.1261053602@10.7.7.3><1261070581.00195950.1261057201@10.7.7.3><1261135381.00196302.1261124403@10.7.7.3> <4B2B6F02.9050404@FreeBSD.org> Date: Fri, 18 Dec 2009 16:31:34 +0300 Keywords: freebsd-current Message-ID: <86F04BBEAAB74CE99958C520DB0C72F9@vosz.local> MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acp/2gxVSgsT1qdMTRq1x7d2XxSYvQAAVD/Q X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <4B2B6F02.9050404@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 13:31:37 -0000 > > May be a problem is in ata? WD15EADS is a "green" series of drives. > > If you don't receive TIMEOUT messages, then commands probably complete > successfully. Loads above 100% may mean that requests are running for > few seconds. It shouldn't happen normally. All right. There are no errors, but disk speed is extremely low (just several kb/s). This state suddenly comes, and suddenly ceases (after approx. 10 min). During this state gstat shows something like this: dT: 1.008s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 0 0 0 0 0.0 0 0 0.0 0.0| ad6 3 2 1 127 5377 1 4 1711 179.1| ad6 0 0 0 0 0.0 0 0 0.0 0.0| ad6 1 16 0 0 0.0 16 2038 111.6 177.6| ad6 and so on. > Have you tried to check whole drive surface? Have you checked SMART > reports? I had a drive onece, which had so many media problems and > relocated sectors, that I was unable to burn CD from it, so > slow it was. > Same time there was no bad sectors on that drive, reported to > OS, drive > handled everything. It was just extremely slow. # smartctl -A /dev/ad6 smartctl version 5.38 [amd64-portbld-freebsd8.0] Copyright (C) 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 180 180 021 Pre-fail Always - 5958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 23 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 158 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 18 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 17 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3886 194 Temperature_Celsius 0x0022 115 106 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 > Have you tried to rewrite _while_ drive media with dd? Some > media errors > could only be resolved only during write operation. I have 2GB swap partition (ad6p2) on this drive. While main zfs partition (ad6p3) is offline I have tried: 1. several times completely to rewrite/read with dd. No errors and delays. 2. to create UFS filesystem and to use it. No errors and delays (although may be more testing need). 3. to create ZFS pool (`zpool create test /dev/ad6p2` (not mirrored)) and to use it. Oops! We have the problem! After the problem has appeared, the any operation (dd, for example) on ad6 is very slow with same symptoms. At this point i have questions only... What can I do? -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 16:18:44 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DE7A1065672; Fri, 18 Dec 2009 16:18:44 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:198:206::1]) by mx1.freebsd.org (Postfix) with ESMTP id D8DA88FC1D; Fri, 18 Dec 2009 16:18:43 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id nBIGIgHQ026359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Dec 2009 17:18:42 +0100 (CET) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by acme.spoerlein.net (8.14.3/8.14.3/Submit) id nBIGIgZM026358; Fri, 18 Dec 2009 17:18:42 +0100 (CET) (envelope-from uqs@spoerlein.net) Date: Fri, 18 Dec 2009 17:18:42 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Daniel Thiele Message-ID: <20091218161842.GP55913@acme.spoerlein.net> Mail-Followup-To: Daniel Thiele , "Simon L. Nielsen" , freebsd-current@freebsd.org, shaun@freebsd.org References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <4B251476.1090303@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B251476.1090303@gmx.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org, "Simon L. Nielsen" , shaun@freebsd.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 16:18:44 -0000 On Sun, 13.12.2009 at 17:21:10 +0100, Daniel Thiele wrote: > Simon L. Nielsen wrote: > > On 2009.12.12 23:07:58 +0100, Daniel Thiele wrote: > > > >> Is there maybe another way to achieve onetime /tmp encryption that > >> I am missing? Preferably one that does not involve huge changes to > > > > Well, I use the simple one - make /tmp a memory file system. locate > > is sometimes not too happy with an e.g. 50MB /tmp, but otherwise it > > works very well for me. > > > > [simon@arthur:~] grep tmp /etc/rc.conf > > tmpmfs="YES" > > tmpsize="50M" > > > > Using a memory file system (together, of course, with an encrypted swap > partition) also crossed my mind. While a small memory based /tmp may be > sufficient for most desktop workloads, I don't think that I can chum up > with it. Especially when you consider that disk space is orders of > magnitudes cheaper than RAM. > > Since the tmpmfs option does not scale well with growing /tmp space > requirements (at least not in a cost-effective way), I am keen to know > why the patch I dug up in my first mail has never been committed. Was it > solely a lack of interest or time, or have there been other reasons? Either my understanding of the FreeBSD VM is wrong, or you fail to realize that tmpmfs will be swap-backed, so that disk usage is the same in both scenarios (but more flexible for the tmpfs). What I'm saying is that you lose almost nothing of physical RAM if you set tmpsize=1G and increase your swap accordingly. Once you fill /tmp with 1G, you will eventually use 1G swap. (medium oversimplification). Regards, Uli From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 16:34:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DBE2710656B2; Fri, 18 Dec 2009 16:34:05 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:198:206::1]) by mx1.freebsd.org (Postfix) with ESMTP id 6D2628FC41; Fri, 18 Dec 2009 16:34:05 +0000 (UTC) Received: from acme.spoerlein.net (localhost.spoerlein.net [IPv6:::1]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id nBIGY0Ld026862 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Dec 2009 17:34:00 +0100 (CET) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by acme.spoerlein.net (8.14.3/8.14.3/Submit) id nBIGY0KB026861; Fri, 18 Dec 2009 17:34:00 +0100 (CET) (envelope-from uqs@spoerlein.net) Date: Fri, 18 Dec 2009 17:34:00 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: Anton Shterenlikht Message-ID: <20091218163400.GQ55913@acme.spoerlein.net> Mail-Followup-To: Anton Shterenlikht , Roman Divacky , freebsd-current@freebsd.org References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> <20091216145033.GA69013@freebsd.org> <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Roman Divacky , freebsd-current@freebsd.org Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 16:34:05 -0000 On Wed, 16.12.2009 at 15:18:47 +0000, Anton Shterenlikht wrote: > On Wed, Dec 16, 2009 at 03:50:33PM +0100, Roman Divacky wrote: > > I wont comment the failure but llvm does NOT support generating IA64 > > code as the support for this was removed some 6 months or so ago.... > > > > what exactly do you want to use the llvm@ia64 for? > > replacement for gcc.. > > gcc44 and 45 fail to build on ia64. From what I can gather (I'm a > user, not a developer) after following this for some months on gcc bugzilla, > gcc folks do not really have a solution, or might not even understand > the problem. Lots of ports of interest to me are dependent on gcc44, > e.g. gfortran, blas, lapack, calculix, code_aster, etc. So I'm looking > for a possible replacement for gcc44 on ia64 Have you tried with a recent gcc45 port? It now depends on newer binutils, which is required to build it with -march=native on amd64, perhaps you're hitting the same base-binutils-is-too-freaking-old issue? hth, Uli From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 17:05:16 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 471DF106566C; Fri, 18 Dec 2009 17:05:16 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id A02538FC13; Fri, 18 Dec 2009 17:05:15 +0000 (UTC) Received: by fxm27 with SMTP id 27so3046310fxm.3 for ; Fri, 18 Dec 2009 09:05:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=y2QC3ouE1ENEBnc5Q0x8F8a45THBPg/Yzp43VaM2FKA=; b=hmOcxez7licM022bxW3md9g7S67idWp3tkKU4lZamPvCyK9kzYboiFb1arkdr+S9Ah Ij+eDlN9hfa4R4EwcKst6QPdTAXbAQVG4qVcFYKrGCQ8UnkI/nFCXyCrW1r1wWsL4wz1 uVNQhSVX8hHR0Dn5iYh+xTluxiJ5AwK6qFH/0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=W7cfu21tA6JlHuQc26XGn3QAx1pWTLvVudLkdNJUkKNexuxwU+fWxaxvhUcS3xuREQ NZbh99W1rHasg9Ao/t4KYH8pBJlE3Ru7IPpOkJ3Q7PXi+xLcFD8vNSoBR3YbLBg310FN Yj0QUFcZu7XoaZskW23pKrDsz2KfIWLv0vmU8= MIME-Version: 1.0 Received: by 10.239.139.154 with SMTP id t26mr459906hbt.74.1261155914278; Fri, 18 Dec 2009 09:05:14 -0800 (PST) In-Reply-To: References: <398F182D4FC14D43A1CFD89C4D69817C@vosz.local> <4B2B52FD.7070206@FreeBSD.org> Date: Fri, 18 Dec 2009 17:05:14 +0000 Message-ID: From: krad To: Alexander Zagrebin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: ZFS and UFS on the same box. Cache memory allocation issue. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 17:05:16 -0000 2009/12/18 Alexander Zagrebin > > > As result UFS returns memory to "free" pool and ZFS can > > allocate it for ARC. > > > It significantly increases ZFS performance. > > > > > > Is there an another workaround? > > > > do you know about the following ZFS loader tunables: > > > > vfs.zfs.arc_min="400M" > > vfs.zfs.arc_max="500M" > > > > These should be added to /boot/loader.conf (and they can of course be > > adjusted to make your system behave well ...) > > Yes, I do. > vfs.zfs.arc_min would be used at this situation, but it seems that setting > this sysctl doesn't help. > > -- > Alexander Zagrebin > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Not really a proper fix but what happens if you have something defined as the l2arc device? From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 17:28:17 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD3DE106566B; Fri, 18 Dec 2009 17:28:17 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 68F458FC0C; Fri, 18 Dec 2009 17:28:16 +0000 (UTC) Received: from isis.bris.ac.uk ([137.222.10.63]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1NLgcb-0002yv-Rv; Fri, 18 Dec 2009 17:28:15 +0000 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by isis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1NLgca-0002OP-Tx; Fri, 18 Dec 2009 17:28:09 +0000 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id nBIHS8JE053833; Fri, 18 Dec 2009 17:28:08 GMT (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id nBIHS8ue053832; Fri, 18 Dec 2009 17:28:08 GMT (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Fri, 18 Dec 2009 17:28:08 +0000 From: Anton Shterenlikht To: Anton Shterenlikht , Roman Divacky , freebsd-current@freebsd.org Message-ID: <20091218172808.GA53819@mech-cluster241.men.bris.ac.uk> References: <20091216144906.GA23342@mech-cluster241.men.bris.ac.uk> <20091216145033.GA69013@freebsd.org> <20091216151847.GA34025@mech-cluster241.men.bris.ac.uk> <20091218163400.GQ55913@acme.spoerlein.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091218163400.GQ55913@acme.spoerlein.net> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: Subject: Re: llvm on ia64 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 17:28:17 -0000 On Fri, Dec 18, 2009 at 05:34:00PM +0100, Ulrich Spörlein wrote: > On Wed, 16.12.2009 at 15:18:47 +0000, Anton Shterenlikht wrote: > > On Wed, Dec 16, 2009 at 03:50:33PM +0100, Roman Divacky wrote: > > > I wont comment the failure but llvm does NOT support generating IA64 > > > code as the support for this was removed some 6 months or so ago.... > > > > > > what exactly do you want to use the llvm@ia64 for? > > > > replacement for gcc.. > > > > gcc44 and 45 fail to build on ia64. From what I can gather (I'm a > > user, not a developer) after following this for some months on gcc bugzilla, > > gcc folks do not really have a solution, or might not even understand > > the problem. Lots of ports of interest to me are dependent on gcc44, > > e.g. gfortran, blas, lapack, calculix, code_aster, etc. So I'm looking > > for a possible replacement for gcc44 on ia64 > > Have you tried with a recent gcc45 port? It now depends on newer > binutils, which is required to build it with -march=native on amd64, > perhaps you're hitting the same base-binutils-is-too-freaking-old issue? checked again now. gcc45 fails as before: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40959 thank you -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 18:04:52 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75ED11065672 for ; Fri, 18 Dec 2009 18:04:52 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by mx1.freebsd.org (Postfix) with ESMTP id 0C96F8FC19 for ; Fri, 18 Dec 2009 18:04:51 +0000 (UTC) Received: by fxm27 with SMTP id 27so3103827fxm.3 for ; Fri, 18 Dec 2009 10:04:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=6a9K3AguplvWdbO4A6YUc+F4cF/BfghRpyzPg1m6NsE=; b=MjscoPLIrOLWcd17910lauKG4FPtzIjDwoEBaYiO+87Z9seGTZttMVkyMW33WYB+Bm /DJICzoNSSNnVSZbsLSPHg0Dlouf5W0lbXxvpq77SdvJtOQXiEgmum4NCoCsJSMFGVY/ A9mqDd7HTbJnH4XLfo2J9M/PJwKkt8K/RJz20= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=xVbzumXIAKwuPHW2AeT8fWS8eEK9hY568v7PGrQhyXIGsLC1JQs1JIMLfLvY1yve2g l1O4CS9oI2nAw/fsWDCuyD0N+uZa08ppXK9UmxprFvUhEx0cKTGraN4rTKzl/kerODXx xjIBVgahDmx90kPnCsnuPLK+md/52MqIcg1HA= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.161.205 with SMTP id s13mr5421691fax.70.1261159490663; Fri, 18 Dec 2009 10:04:50 -0800 (PST) In-Reply-To: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> Date: Fri, 18 Dec 2009 19:04:50 +0100 X-Google-Sender-Auth: 0fba61534d7dd9ee Message-ID: <3bbf2fe10912181004w2a1abff2re8f77fd6a8bc3233@mail.gmail.com> From: Attilio Rao To: Alexander Zagrebin Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 18:04:52 -0000 2009/12/17 Alexander Zagrebin : > Hi! > > I use onboard ICH7 SATA controller with two disks attached: > > atapci1: port > 0x30c8-0x30cf,0x30ec-0x30ef,0x30c0-0x30c7,0x30e8-0x30eb,0x30a0-0x30af irq 19 > at device 31.2 on pci0 > atapci1: [ITHREAD] > ata2: on atapci1 > ata2: [ITHREAD] > ata3: on atapci1 > ata3: [ITHREAD] > ad4: 1430799MB at ata2-master SATA150 > ad6: 1430799MB at ata3-master SATA150 > > The disks are used for mirrored ZFS pool. > I have noticed that the system periodically locks up on disk operations. > After approx. 10 min of very slow disk i/o (several KB/s) the speed of disk > operations restores to normal. > gstat has shown that the problem is in ad6. Want you try this patch and report?: http://people.freebsd.org/~attilio/lockmgr_lostwake.diff It should apply to STABLE_8 and if not, just report and I will help. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 18:29:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6FACE1065672; Fri, 18 Dec 2009 18:29:13 +0000 (UTC) (envelope-from simon@nitro.dk) Received: from mx.nitro.dk (unknown [77.75.165.90]) by mx1.freebsd.org (Postfix) with ESMTP id 30E4F8FC08; Fri, 18 Dec 2009 18:29:13 +0000 (UTC) Received: from frankie.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 6720F2D4897; Fri, 18 Dec 2009 18:26:37 +0000 (UTC) Received: by frankie.nitro.dk (Postfix, from userid 2000) id E1BB8E04B7; Fri, 18 Dec 2009 19:29:11 +0100 (CET) Date: Fri, 18 Dec 2009 19:29:11 +0100 From: "Simon L. Nielsen" To: Daniel Thiele Message-ID: <20091218182910.GA1309@frankie.nitro.dk> References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <4B251476.1090303@gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B251476.1090303@gmx.net> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: freebsd-current@freebsd.org, shaun@FreeBSD.org Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 18:29:13 -0000 On 2009.12.13 17:21:10 +0100, Daniel Thiele wrote: > Since the tmpmfs option does not scale well with growing /tmp space > requirements (at least not in a cost-effective way), I am keen to know > why the patch I dug up in my first mail has never been committed. Was it > solely a lack of interest or time, or have there been other reasons? There is no discussion in the audit trail, so I think it's most likely no committer ever looked that much at it. I took a brief look, and at the very least the patch is missing an update to the rc.conf manual page. I'm not entirely convinced the way the patch goes about creating the devices etc. is the best way to do it, but I don't see any obvious problems. That said, personally I unfortunately have too many other things on my plate to commit the patch. -- Simon L. Nielsen From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 20:04:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81C98106566B for ; Fri, 18 Dec 2009 20:04:27 +0000 (UTC) (envelope-from alexz@visp.ru) Received: from mail.visp.ru (srv1.visp.ru [91.215.204.2]) by mx1.freebsd.org (Postfix) with ESMTP id 33A0E8FC18 for ; Fri, 18 Dec 2009 20:04:26 +0000 (UTC) Received: from 91-215-205-255.static.visp.ru ([91.215.205.255] helo=zagrebin) by mail.visp.ru with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1NLj3p-0004C5-7r; Fri, 18 Dec 2009 23:04:25 +0300 From: "Alexander Zagrebin" To: "'Attilio Rao'" References: <39309F560B98453EBB9AEA0F29D9D80E@vosz.local> <3bbf2fe10912181004w2a1abff2re8f77fd6a8bc3233@mail.gmail.com> Date: Fri, 18 Dec 2009 23:04:24 +0300 Keywords: freebsd-current Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcqADL4NqIpFFA21Q0+GHM/Zys5L2AAD79yg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 In-Reply-To: <3bbf2fe10912181004w2a1abff2re8f77fd6a8bc3233@mail.gmail.com> Cc: freebsd-current@freebsd.org Subject: RE: 8.0-RELEASE: disk IO temporarily hangs up (ZFS or ATA related problem) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 20:04:27 -0000 > > The disks are used for mirrored ZFS pool. > > I have noticed that the system periodically locks up on > disk operations. > > After approx. 10 min of very slow disk i/o (several KB/s) > the speed of disk > > operations restores to normal. > > gstat has shown that the problem is in ad6. > > Want you try this patch and report?: > http://people.freebsd.org/~attilio/lockmgr_lostwake.diff > > It should apply to STABLE_8 and if not, just report and I will help. Thanks fo your attempt to help! I've successfully applied this patch to RELENG_8_0, recompiled kernel and required modules (krpc, opensolaris,zfs), but nothing has changed. The problem still exist. -- Alexander Zagrebin From owner-freebsd-current@FreeBSD.ORG Fri Dec 18 20:13:27 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A42D1106566C for ; Fri, 18 Dec 2009 20:13:27 +0000 (UTC) (envelope-from dthiele@gmx.net) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 0FEE28FC08 for ; Fri, 18 Dec 2009 20:13:26 +0000 (UTC) Received: (qmail invoked by alias); 18 Dec 2009 20:13:24 -0000 Received: from p54867289.dip.t-dialin.net (EHLO impala.vnws.lan) [84.134.114.137] by mail.gmx.net (mp041) with SMTP; 18 Dec 2009 21:13:24 +0100 X-Authenticated: #19302822 X-Provags-ID: V01U2FsdGVkX18gUilgk6ggkvz8CHRGEb1V7Bzef+RPCo9z9otdd7 K5vEAttrbj3gwt Message-ID: <4B2BE3B8.2@gmx.net> Date: Fri, 18 Dec 2009 21:19:04 +0100 From: Daniel Thiele User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Daniel Thiele , =?ISO-8859-1?Q?Ulrich_Sp=F6rlein?= , freebsd-current@freebsd.org, shaun@freebsd.org References: <4B24143E.2060803@gmx.net> <20091212224052.GF1417@arthur.nitro.dk> <4B251476.1090303@gmx.net> <20091218161842.GP55913@acme.spoerlein.net> In-Reply-To: <20091218161842.GP55913@acme.spoerlein.net> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.43 Cc: Subject: Re: Support for geli onetime encryption for /tmp? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Dec 2009 20:13:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Ulrich Spörlein wrote: > On Sun, 13.12.2009 at 17:21:10 +0100, Daniel Thiele wrote: >> Simon L. Nielsen wrote: >>> On 2009.12.12 23:07:58 +0100, Daniel Thiele wrote: >>> >>>> Is there maybe another way to achieve onetime /tmp encryption that >>>> I am missing? Preferably one that does not involve huge changes to >>> Well, I use the simple one - make /tmp a memory file system. locate >>> is sometimes not too happy with an e.g. 50MB /tmp, but otherwise it >>> works very well for me. >>> >>> [simon@arthur:~] grep tmp /etc/rc.conf >>> tmpmfs="YES" >>> tmpsize="50M" >>> >> Using a memory file system (together, of course, with an encrypted swap >> partition) also crossed my mind. While a small memory based /tmp may be >> sufficient for most desktop workloads, I don't think that I can chum up >> with it. Especially when you consider that disk space is orders of >> magnitudes cheaper than RAM. >> >> Since the tmpmfs option does not scale well with growing /tmp space >> requirements (at least not in a cost-effective way), I am keen to know >> why the patch I dug up in my first mail has never been committed. Was it >> solely a lack of interest or time, or have there been other reasons? > > Either my understanding of the FreeBSD VM is wrong, or you fail to > realize that tmpmfs will be swap-backed, so that disk usage is the same > in both scenarios (but more flexible for the tmpfs). > > What I'm saying is that you lose almost nothing of physical RAM if you > set tmpsize=1G and increase your swap accordingly. Once you fill /tmp > with 1G, you will eventually use 1G swap. (medium oversimplification). > Well, it seems that I really overlooked the fact that tmpmfs will indeed be swap-based. To my shame I have to admit that I stopped reading at rc.conf(5), which does not mention that tmpmfs will by default be swap-based. Thank you for pointing that out. In that case I was wrong and tmpmfs really provides an interesting solution to my initial problem. Best regards, Daniel -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJLK+O2AAoJEB+84OrFyizNBPgQALKc0X/v/+70JGasEivYNIf9 ZgCZjqyK5WXh5oQLcRI6FOTrz4pr5u81O7B8KC2jw9+GDfuGzm+DiI3Znc78Syo9 x7DVRXEaasJ7fahinxJ6tQrDm58tHLSKjY++PO2DL9v8zJaL3WTW/uPU5J7crbLf 6u9vsGW+CNrm6dBNfvbr8NdoyjNoRBM+CpDaf3gLw56eRYkAeJWJrdlYxZb7RdAh MKvT/VcwXKLsLzVUmEvcYBhc9fj8GYO60exTiwSVRXgvZ0Rm5wFJjou9SOlVen9o uG/sKv9c5VU1qL5bt+5MebiZmVh0YFYYu4SqV3IbgRk+djdHEFd9OfYZKmv1R34s BxLHp6fOqQIdM0WTrPLDCpx6Lz2n92KrQqHu0pu0zvA1KEqkIFPuetkQ9G5qW0Dy zP94tnNWq6OecLU0gu7u7TaZYQAHR6vrBnwmyLBOvXr0gWwkE9eagp63vxE6eM4D ew8MDM20vjWvT91AgggjViB3tQAzsmzu1YEW2tdc+fKHSFnrC4DAnvxaCIkXUw8u nAZPkaebnrM2AsOHJrL0YmK+wh2Dh+p5oGykbXf1mzA9c4LOD0tpjloME45ERb8+ z9bpG6kyeUqeHjFvTzfhr2ne13atON5o9mdEiqSuNmAk8FkOeZKpNTTg4jQdS96C Gizpkg0y7T2DFTgqtJGh =dydc -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Dec 19 14:37:32 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 659361065670 for ; Sat, 19 Dec 2009 14:37:32 +0000 (UTC) (envelope-from bounces@nabble.com) Received: from kuber.nabble.com (kuber.nabble.com [216.139.236.158]) by mx1.freebsd.org (Postfix) with ESMTP id 483898FC17 for ; Sat, 19 Dec 2009 14:37:32 +0000 (UTC) Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1NM0R1-00025M-U0 for freebsd-current@freebsd.org; Sat, 19 Dec 2009 06:37:31 -0800 Message-ID: <26855510.post@talk.nabble.com> Date: Sat, 19 Dec 2009 06:37:31 -0800 (PST) From: henter2009 To: freebsd-current@freebsd.org In-Reply-To: <24477244.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jeronimocalvop@googlemail.com References: <24477244.post@talk.nabble.com> X-Mailman-Approved-At: Sat, 19 Dec 2009 18:01:34 +0000 Subject: Re: Build error "am_ET.UTF-8.out: Inappropriate ioctl for device"" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 14:37:32 -0000 hi folks, Im getting this error as well when building world for RELENG_8 wich seems to be the 8 STABLE, any ideas for skip that? Jakub Lach wrote: > > Hello fellow CURRENT users & venerable hackers. > > I'm running FreeBSD 8.0-BETA1 #0 r195642M amd64, > any attempt of source-upgrade results in : > > ===> share/mklocale (all) > mklocale -o UTF-8.out /usr/src/share/mklocale/UTF-8.src > mklocale -o am_ET.UTF-8.out /usr/src/share/mklocale/am_ET.UTF-8.src > am_ET.UTF-8.out: Inappropriate ioctl for device > *** Error code 1 > > Stop in /usr/src/share/mklocale. > *** Error code 1 > > Stop in /usr/src/share. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Same for GENERIC as custom kernel. Couldn't trace origin of this breakage, > any ideas? > > -best regards, > Jakub Lach > ----- _ ASCII ribbon campaign ( ) against HTML e-mail X / \ -- View this message in context: http://old.nabble.com/Build-error-%22am_ET.UTF-8.out%3A-Inappropriate-ioctl-for-device%22%22-tp24477244p26855510.html Sent from the freebsd-current mailing list archive at Nabble.com. From owner-freebsd-current@FreeBSD.ORG Sat Dec 19 18:06:14 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 34E541065670 for ; Sat, 19 Dec 2009 18:06:14 +0000 (UTC) (envelope-from serenity@exscape.org) Received: from ch-smtp01.sth.basefarm.net (ch-smtp01.sth.basefarm.net [80.76.149.212]) by mx1.freebsd.org (Postfix) with ESMTP id E4B938FC0C for ; Sat, 19 Dec 2009 18:06:13 +0000 (UTC) Received: from c83-253-248-99.bredband.comhem.se ([83.253.248.99]:39291 helo=mx.exscape.org) by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68) (envelope-from ) id 1NM3gc-0003ys-5O; Sat, 19 Dec 2009 19:05:52 +0100 Received: from [192.168.1.5] (macbookpro [192.168.1.5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mx.exscape.org (Postfix) with ESMTPSA id 8674234C75; Sat, 19 Dec 2009 19:05:50 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii From: Thomas Backman In-Reply-To: <26855510.post@talk.nabble.com> Date: Sat, 19 Dec 2009 19:05:48 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8B23AD0E-ABC7-44C5-9589-CA0A6A6E51CE@exscape.org> References: <24477244.post@talk.nabble.com> <26855510.post@talk.nabble.com> To: henter2009 X-Mailer: Apple Mail (2.1077) X-Originating-IP: 83.253.248.99 X-Scan-Result: No virus found in message 1NM3gc-0003ys-5O. X-Scan-Signature: ch-smtp01.sth.basefarm.net 1NM3gc-0003ys-5O b223bda3c68f6570b6166c091ce9ea17 Cc: freebsd-current@freebsd.org Subject: Re: Build error "am_ET.UTF-8.out: Inappropriate ioctl for device"" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 18:06:14 -0000 On Dec 19, 2009, at 3:37 PM, henter2009 wrote: >=20 > hi folks, >=20 > Im getting this error as well when building world for RELENG_8 wich = seems to > be the 8 STABLE, any ideas for skip that? >=20 >=20 > Jakub Lach wrote: >>=20 >> mklocale -o am_ET.UTF-8.out /usr/src/share/mklocale/am_ET.UTF-8.src >> am_ET.UTF-8.out: Inappropriate ioctl for device >> *** Error code 1 IIRC, rebuild mklocale manually (cd /usr/src/usr.bin/mklocale && make && = make install) and then try again. If not, this was up on the lists back when it was actual: = http://www.google.com/search?q=3D%2B"am_ET.UTF-8.out%3A+Inappropriate+ioct= l+for+device"&ie=3Dutf-8&oe=3Dutf-8&aq=3Dt Regards, Thomas= From owner-freebsd-current@FreeBSD.ORG Sat Dec 19 21:53:21 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DCA11065672 for ; Sat, 19 Dec 2009 21:53:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 1BCCF8FC14 for ; Sat, 19 Dec 2009 21:53:21 +0000 (UTC) Received: (qmail 5102 invoked by uid 399); 19 Dec 2009 21:53:20 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 19 Dec 2009 21:53:20 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4B2D4B53.1060503@FreeBSD.org> Date: Sat, 19 Dec 2009 13:53:23 -0800 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: freebsd-current@freebsd.org X-Enigmail-Version: 0.96.0 OpenPGP: id=D5B2F0FB Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Systems running hot? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 21:53:21 -0000 In the last weeks (I generally update to the latest HEAD daily) It seems that my -current laptop is running hot temperature wise, even when it's idle, or nearly so. The temperature sensor (via wmbsdbatt) generally stays in the 80s C, as opposed to the 70s, and the fan is regularly on its "medium" speed as opposed to the low speed. Also, the keyboard area sometimes becomes so hot that it's actually uncomfortable. If I boot windows and let it run that way for a while everything goes back to normal. I've got the back end of the laptop propped up an inch or so to improve ventilation which helps some, but it's still running hotter than usual. And before someone suggests it, yes, I've blown out all the fans/heatsinks. This is a Dell Latitude D620 with a C2D, running i386 SMP in case any of that matters. :) Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Sat Dec 19 21:59:49 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C085010656C0; Sat, 19 Dec 2009 21:59:49 +0000 (UTC) (envelope-from mailinglists@alchemy-networks.co.uk) Received: from mail.alchemy-networks.co.uk (cl-595.lon-02.gb.sixxs.net [IPv6:2a01:348:6:252::2]) by mx1.freebsd.org (Postfix) with ESMTP id 85BE28FC28; Sat, 19 Dec 2009 21:59:49 +0000 (UTC) Received: from desktop1.alchemy-networks.co.uk ([10.0.0.33]) by mail.alchemy-networks.co.uk with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NM7NB-000KNZ-92; Sat, 19 Dec 2009 22:02:01 +0000 Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: "Doug Barton" , freebsd-current@freebsd.org References: <4B2D4B53.1060503@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Paul G Webster" Organization: WorldForMe Date: Sat, 19 Dec 2009 21:59:51 -0000 Message-ID: In-Reply-To: <4B2D4B53.1060503@FreeBSD.org> User-Agent: Opera Mail/10.01 (FreeBSD) Cc: Subject: Re: Systems running hot? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 21:59:49 -0000 tried running powerd on it? On Sat, 19 Dec 2009 21:53:23 -0000, Doug Barton wrote: > In the last weeks (I generally update to the latest HEAD daily) It > seems that my -current laptop is running hot temperature wise, even > when it's idle, or nearly so. The temperature sensor (via wmbsdbatt) > generally stays in the 80s C, as opposed to the 70s, and the fan is > regularly on its "medium" speed as opposed to the low speed. Also, the > keyboard area sometimes becomes so hot that it's actually > uncomfortable. If I boot windows and let it run that way for a while > everything goes back to normal. > > I've got the back end of the laptop propped up an inch or so to > improve ventilation which helps some, but it's still running hotter > than usual. And before someone suggests it, yes, I've blown out all > the fans/heatsinks. > > This is a Dell Latitude D620 with a C2D, running i386 SMP in case any > of that matters. :) > > > Doug > -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ From owner-freebsd-current@FreeBSD.ORG Sat Dec 19 23:35:05 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F93C1065693; Sat, 19 Dec 2009 23:35:05 +0000 (UTC) (envelope-from pisymbol@gmail.com) Received: from mail-yw0-f172.google.com (mail-yw0-f172.google.com [209.85.211.172]) by mx1.freebsd.org (Postfix) with ESMTP id 1F8828FC0A; Sat, 19 Dec 2009 23:35:04 +0000 (UTC) Received: by ywh2 with SMTP id 2so4430823ywh.27 for ; Sat, 19 Dec 2009 15:35:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rARAH7Z2BVfemmWyu3Axi3BJgd1SwG+0DA7H29TYefI=; b=O/0BzaWWdbMMu1Io1Nd/NJbk9gGEuizy6o2TEpJutwzBw7AzvDOzTdijm5itLPSIK+ UcXdYh9SVUd5Qj3HJzS6gTjNOIJud1BGFwullT1wpS3BrM82mQlZ85/7bp4dZfJjdtE6 jhi1fcpR7kz+UXCkxPLAxZz/ioV3hZtmhZtsY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=YcjCxk3ETxUjEj+wQrsraKxthQmM2MFgsMNbT5jsLSUTsmHlE5AbtDNh0sBJzhm0by k1TJUmTooRQb0FeKxkxCdn5zRahS5pFYQdHhWr9sbPBahyZQXeIshwtLKC04QZ2dqpmS F2jQqo1zTIbnCVA/OiLUEkzVgqYeuw17KF8rE= MIME-Version: 1.0 Received: by 10.101.10.20 with SMTP id n20mr8918816ani.66.1261265704151; Sat, 19 Dec 2009 15:35:04 -0800 (PST) In-Reply-To: <3c0b01820912160910i35e12112s4d6412d6cb174f3b@mail.gmail.com> References: <3c0b01820912141347y366a7252y5d9711b1141b9b70@mail.gmail.com> <978BBD51-222D-42F0-9D3A-FFACCBCC886D@samsco.org> <3c0b01820912160910i35e12112s4d6412d6cb174f3b@mail.gmail.com> Date: Sat, 19 Dec 2009 18:35:04 -0500 Message-ID: <3c0b01820912191535j4e43f4f8i48ea5239add8fa0e@mail.gmail.com> From: Alexander Sack To: Scott Long Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-scsi@freebsd.org, freebsd-current@freebsd.org Subject: Re: aac(4) handling of probe when no devices are there X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Dec 2009 23:35:05 -0000 On Wed, Dec 16, 2009 at 12:10 PM, Alexander Sack wrote= : > On Tue, Dec 15, 2009 at 4:54 AM, Scott Long wrote: >> On Dec 14, 2009, at 2:47 PM, Alexander Sack wrote: > Yes surely. =A0 I think what might be happening is that after the > INQUIRY fails, xpt_release_ccb() which I think will also check to see > if any more CCBs should be sent to the device and send them. > Basically the boot -v output is I am getting a CAM_SEL_TIMEOUT for > each target and just hit into the 500 interrupt storm default > threshold on 6.1. Sorry for the delay. Its the holidays and a bunch of stuff going on. Alright, honestly, it looks like everything is FINE minus the fact that camisr() is going to get called a lot given the number of buses and targest on the system. I instrumented aac_cam_action() and it appears to be normal: mfid0: on mfi0 mfid0: 238418MB (488280064 sectors) RAID aacd0: on aac0 aacd0: 9533430MB (19524464640 sectors) aacd1: on aac1 aacd1: 9533430MB (19524464640 sectors) GEOM: new disk mfid0 GEOM: new disk aacd0 GEOM: new disk aacd1 GEOM_LABEL: Label for provider mfid0 is label/disk0. GEOM_LABEL: Label for provider aacd0 is label/disk1. GEOM_LABEL: Label for provider aacd1 is label/disk2. (probe5:aacp5:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe5:aacp5:0:0:0): Retrying Command (probe2:aacp2:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe2:aacp2:0:0:0): Retrying Command (probe5:aacp5:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe5:aacp5:0:0:0): Retrying Command (probe2:aacp2:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe2:aacp2:0:0:0): Retrying Command (probe5:aacp5:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe5:aacp5:0:0:0): Retrying Command (probe2:aacp2:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe2:aacp2:0:0:0): Retrying Command (probe0:aacp3:0:8:1): error 22 (probe0:aacp3:0:8:1): Unretryable Error (probe5:aacp5:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe5:aacp5:0:0:0): Retrying Command (probe4:aacp0:0:8:1): error 22 (probe4:aacp0:0:8:1): Unretryable Error (probe2:aacp2:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe2:aacp2:0:0:0): Retrying Command (probe0:aacp3:0:8:2): error 22 (probe0:aacp3:0:8:2): Unretryable Error (probe5:aacp5:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe5:aacp5:0:0:0): error 5 (probe5:aacp5:0:0:0): Retries Exausted (probe4:aacp0:0:8:2): error 22 (probe4:aacp0:0:8:2): Unretryable Error (probe2:aacp2:0:0:0): Request completed with CAM_REQ_CMP_ERR (probe2:aacp2:0:0:0): error 5 (probe2:aacp2:0:0:0): Retries Exausted (probe0:aacp3:0:8:3): error 22 (probe0:aacp3:0:8:3): Unretryable Error . . . (probe0:aacp0:0:19:3): Unretryable Error (probe2:aacp3:0:19:2): error 22 (probe2:aacp3:0:19:2): Unretryable Error (probe1:aacp0:0:19:4): error 22 (probe1:aacp0:0:19:4): Unretryable Error (probe2:aacp3:0:19:3): error 22 (probe2:aacp3:0:19:3): Unretryable Error (probe0:aacp0:0:19:5): error 22 (probe0:aacp0:0:19:5): Unretryable Error (probe2:aacp3:0:19:4): error 22 (probe2:aacp3:0:19:4): Unretryable Error (probe1:aacp0:0:19:6): error 22 (probe1:aacp0:0:19:6): Unretryable Error (probe2:aacp3:0:19:5): error 22 (probe2:aacp3:0:19:5): Unretryable Error (probe0:aacp0:0:19:7): error 22 (probe0:aacp0:0:19:7): Unretryable Error (probe2:aacp3:0:19:6): error 22 (probe2:aacp3:0:19:6): Unretryable Error (probe2:aacp3:0:19:7): error 22 (probe2:aacp3:0:19:7): Unretryable Error Interrupt storm detected on "swi2:"; throttling interrupt source If you look at aac_cam_action()/aac_cam_complete() via KTR: 5:0:1 CAM_DEV_NOT_THERE 144 5:0:1 op: 12 143 4:17:0 0xa 142 4:17:0 op: 12 141 3:8:4 CAM_DEV_NOT_THERE 140 3:8:4 op: 12 139 0:8:3 CAM_DEV_NOT_THERE 138 0:8:3 op: 12 137 1:13:0 0xa 136 1:13:0 op: 12 135 2:0:0 op: 0 134 4:16:0 0xa 133 4:16:0 op: 12 132 3:8:3 CAM_DEV_NOT_THERE 131 3:8:3 op: 12 130 5:0:0 op: 0 129 2:0:0 0x84 128 0:8:2 CAM_DEV_NOT_THERE 127 1:12:0 0xa 126 0:8:2 op: 12 125 1:12:0 op: 12 124 5:0:0 0x84 123 4:15:0 0xa 122 3:8:2 CAM_DEV_NOT_THERE 121 2:0:0 op: 12 120 4:15:0 op: 12 119 3:8:2 op: 12 118 5:0:0 op: 12 117 2:0:0 0x84 116 0:8:1 CAM_DEV_NOT_THERE 115 1:11:0 0xa 114 5:0:0 0x84 113 4:14:0 0xa 112 3:8:1 CAM_DEV_NOT_THERE 111 0:8:1 op: 12 110 1:11:0 op: 12 109 4:14:0 op: 12 108 3:8:1 op: 12 107 2:0:0 op: 12 106 2:0:0 0x84 105 1:10:0 0xa 104 5:0:0 op: 12 103 4:13:0 0xa 102 4:13:0 op: 12 101 5:0:0 0x84 100 4:12:0 0xa 99 0:8:0 op: 0 98 1:10:0 op: 12 97 4:12:0 op: 12 96 2:0:0 op: 12 95 3:8:0 op: 0 94 2:0:0 0x84 93 1:9:0 0xa 92 5:0:0 op: 12 91 4:11:0 0xa 90 4:11:0 op: 12 89 5:0:0 0x84 88 4:10:0 0xa 87 0:8:0 op: 12 86 1:9:0 op: 12 85 4:10:0 op: 12 84 3:8:0 op: 12 83 2:0:0 op: 12 82 0:8:0 op: 1a 81 5:0:0 op: 12 80 2:0:0 0x84 79 1:8:0 0xa 78 4:9:0 0xa 77 4:9:0 op: 12 76 5:0:0 0x84 75 4:8:0 0xa 74 3:8:0 op: 1a 73 1:8:0 op: 12 72 0:8:0 op: 12 71 4:8:0 op: 12 70 3:8:0 op: 12 69 1:7:0 0xa 68 1:7:0 op: 12 67 0:7:0 0xa 66 0:7:0 op: 12 65 4:7:0 0xa 64 4:7:0 op: 12 63 3:7:0 0xa 62 3:7:0 op: 12 61 1:6:0 0xa 60 1:6:0 op: 12 59 0:6:0 0xa 58 0:6:0 op: 12 57 4:6:0 0xa 56 4:6:0 op: 12 55 3:6:0 0xa 54 3:6:0 op: 12 53 1:5:0 0xa 52 1:5:0 op: 12 51 0:5:0 0xa 50 0:5:0 op: 12 49 4:5:0 0xa 48 4:5:0 op: 12 47 3:5:0 0xa 46 3:5:0 op: 12 45 1:4:0 0xa 44 1:4:0 op: 12 43 0:4:0 0xa 42 0:4:0 op: 12 41 4:4:0 0xa 40 2:0:0 op: 12 39 5:0:0 op: 12 38 4:4:0 op: 12 37 3:4:0 0xa 36 3:4:0 op: 12 35 1:3:0 0xa 34 1:3:0 op: 12 33 0:3:0 0xa 32 5:0:0 op: 12 31 2:0:0 op: 12 30 0:3:0 op: 12 29 4:3:0 0xa 28 4:3:0 op: 12 27 3:3:0 0xa 26 3:3:0 op: 12 25 1:2:0 0xa 24 1:2:0 op: 12 23 0:2:0 0xa 22 0:2:0 op: 12 21 4:2:0 0xa 20 4:2:0 op: 12 19 3:2:0 0xa 18 3:2:0 op: 12 17 1:1:0 0xa 16 0:1:0 0xa 15 4:1:0 0xa 14 3:1:0 0xa 13 1:1:0 op: 12 12 4:1:0 op: 12 11 3:1:0 op: 12 10 0:1:0 op: 12 9 1:0:0 0xa 8 4:0:0 0xa 7 3:0:0 0xa 6 0:0:0 0xa 5 5:0:0 op: 12 4 4:0:0 op: 12 3 3:0:0 op: 12 2 2:0:0 op: 12 1 1:0:0 op: 12 0 0:0:0 op: 12 At a limit of 500 on 6.1, it was easy to hit this threshold. I assumed before that the CAM_REQ_CMP_ERR's were CAM_SEL_TIMEOUT and confused the issues. Sorry for that, its been a long week dealing with several issues. With enough cards, you will even hit the 1000 limit in CURRENT (though I admit its not really that serious). Right? -aps