From owner-freebsd-stable@freebsd.org Sun Jul 19 00:05:04 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D61B09A5BEE for ; Sun, 19 Jul 2015 00:05:04 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A2F812E4 for ; Sun, 19 Jul 2015 00:05:04 +0000 (UTC) (envelope-from jrm@ftfl.ca) Received: by qkfc129 with SMTP id c129so48760055qkf.1 for ; Sat, 18 Jul 2015 17:05:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftfl.ca; s=google; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=SA4T2JtcuILBHRsXdYCt1HanrsxPR+5DzRX9AMys/5s=; b=I4XLJ5eUA+bfuC0BI5RR4EzMDq3GodA5LEY58ZKDIbKCxVXMOJoKLarDVEjF3DIBLH MDqFaWLXF0Pooz5TqutOAxLr4zECysjzepv2MFzlLGKzy11gZwTrjglQ7TINNhEmwDF0 SjXMRVkICnKCHJ3lUxRIIEyASlAQ5Q0j02h4M= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=SA4T2JtcuILBHRsXdYCt1HanrsxPR+5DzRX9AMys/5s=; b=LYyMfzChu/3NmkdqRPQyLu7g/nhJb+XyDR4yV+ytlI9d+NJIXUublI86Pv8KOCdDnw gPTXVy45kfLUoD2Xd0P5KpGgpr/IeHDUUBFRkH+4DuWnUdcEruVCcwdZAwngVrXN7JYj KJvdQoKulwq0HnNkhg0pRHUHqho+9ELX9jgce7kxJK67xgWQKl2yQsHRuP5SAF9f1saK IHLDh53so7MsO0jVVdWNh9uvx+KgqAo+mp1pFizARViZEPU0zuEs5g/aflfIxcJbOUH+ IWd8DCpyiZWcCVj911T3AH1IlacZFj+t7mHkhoYoA837wQTlJCk1hTuki5Qycy+SEbYI /CdA== X-Gm-Message-State: ALoCoQkaHFeVXFXcKAI44NtnqRqaTiLx5cVKe+1G/cWN559PzAn6dtIv5DCtx1wmGmZK2xZbiUTT X-Received: by 10.140.150.78 with SMTP id 75mr30739271qhw.10.1437264303195; Sat, 18 Jul 2015 17:05:03 -0700 (PDT) Received: from gly.ftfl.ca.ftfl.ca (gly.ftfl.Ca. [129.173.34.203]) by smtp.gmail.com with ESMTPSA id h11sm5134494qgh.17.2015.07.18.17.05.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 18 Jul 2015 17:05:01 -0700 (PDT) From: Joseph Mingrone To: Kevin Oberman Cc: John Baldwin , "Brandon J. Wandersee" , Adrian Chadd , FreeBSD-STABLE Mailing List Subject: Re: suspend/resume regression References: <86oak289hv.fsf@gly.ftfl.ca> <86615mlcto.fsf@WorkBox.Home> <6951198.NGhNejXbxL@ralph.baldwin.cx> Date: Sat, 18 Jul 2015 21:04:59 -0300 In-Reply-To: (Kevin Oberman's message of "Sat, 18 Jul 2015 16:56:34 -0700") Message-ID: <86oaj9dnbo.fsf@gly.ftfl.ca> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 00:05:05 -0000 --=-=-= Content-Type: text/plain Head worked for me. Joseph Mingrone writes: > On head, resume worked, but the fn-f4 keybinding didn't suspend. I > had to use zzz. Joseph Mingrone writes: > No problem with -head on the X220 as well. Joseph --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVqumrAAoJEDakDIOw1u+ev9oQAJXyrf79tUPwSHkmgcIYefXt qffApY5UdHEvglHlHiCY3JwDIos3rcQhu1+kMGpyfijMfa4+BtTH40x4N3fCXGoU El8W3WOzL1vDDuT63ANfen7viK9CK2rLyddynTkaCCZf1rzOOvgGJKwWAc6uwOin b5Xd7LwD0R1Rk2CDbZ9hz6rGRaiR1jY6ChRGVwsfwWAaJKIGMRq3skv9zOybi/iS HNtAivYm4RQ46wg425/jt1lVUcm52sDYHdsxoX+gIDI4zQgdGi9OlpA6McJSWZMp LP19VagKIf4rVmK6cVdv0qggKwnle+i52+46hOjjyznsCeNtx1zXc4G1nO5vyFiZ 81HgMQLNoreFytDaMU6xEVjStfzBZ9be1Bfb32YlY1OcaHfVB9aof1cebP3iKaPK XI2sl7nC9uqihxjeb3JXDb/GmAJgO8JAegbHfVlYgI8QCPR+KbPwxdbrv24+Xr1h Uuh873JpN75r4w7xrAOGwlp5vY8I2SvQe/9PM3Js7EqH/z3+03QIPTTk45kk83ne H0oAyYO7aLfxmUoEqGmM1MTMT70cD9+kj8bjCkv70o5oD6BhKxJaadlkvvaY4dBA b0GdVZKltZFeAyBiho/zsl670XjKlr8nTpfVU4Y6CPq6UcTx4zQBlGCa6/I+Qo5V 4CARzIoSOEy8d7RYW/3A =KoyQ -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-stable@freebsd.org Sun Jul 19 05:22:35 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA78C9A4820 for ; Sun, 19 Jul 2015 05:22:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9BB7D1067; Sun, 19 Jul 2015 05:22:34 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by obre1 with SMTP id e1so86110448obr.1; Sat, 18 Jul 2015 22:22:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=e/sc4XZXxbLOaSrPrJIrhhYUhW1yolq4H34UbKxxeAk=; b=VBU2xnoP8rV6Gi5NFii0ykTr2UB/MVZbXQhznzIaOm99tQxZTPjvTPod6N8objIobB qFvGCTngUYeUUgh+551HJ0+zrhkmJRMEnw0yQX+IcCN1TBIWAFtCYVrobLKHYkIILXdL /rHb0czXQraw4CdtJqmX0YMOwuOtqmBxVjbhJVmxG3NB2watEfA3FY65R64PAAW0Y4YE vm5sKvQXwQpj41liKZxosEYU2JHwyuZQhU/j2qmwoMP/dM70DY4yDmky0kOeDVRH+kpu HB9k8Az+BzLJUEYkn227f8CrwrN4aKwsGdF1h9rRBNMJ3hehB5oojDhcIeQjJHKHaxEx G8kw== MIME-Version: 1.0 X-Received: by 10.182.224.164 with SMTP id rd4mr10303649obc.25.1437283353800; Sat, 18 Jul 2015 22:22:33 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Sat, 18 Jul 2015 22:22:33 -0700 (PDT) In-Reply-To: <86oaj9dnbo.fsf@gly.ftfl.ca> References: <86oak289hv.fsf@gly.ftfl.ca> <86615mlcto.fsf@WorkBox.Home> <6951198.NGhNejXbxL@ralph.baldwin.cx> <86oaj9dnbo.fsf@gly.ftfl.ca> Date: Sat, 18 Jul 2015 22:22:33 -0700 X-Google-Sender-Auth: N5Y7TfLH8rNUKCCQ_teVgYv0i54 Message-ID: Subject: Re: suspend/resume regression From: Kevin Oberman To: Joseph Mingrone Cc: John Baldwin , "Brandon J. Wandersee" , Adrian Chadd , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 05:22:35 -0000 I just confirmed that my system resumes on HEAD of July 16 but fails on 10.2-BETA2. So the problem limited to 10. I'm guessing that some other change made to pci that has not been MFCed is the cause, but it is only causing a problem on some hardware. I have seen no reports about systems other than Lenovo systems. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Sat, Jul 18, 2015 at 5:04 PM, Joseph Mingrone wrote: > Head worked for me. > > Joseph Mingrone writes: > > On head, resume worked, but the fn-f4 keybinding didn't suspend. I > > had to use zzz. > > Joseph Mingrone writes: > > No problem with -head on the X220 as well. > > Joseph > From owner-freebsd-stable@freebsd.org Sun Jul 19 15:34:36 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70E7E9A5758 for ; Sun, 19 Jul 2015 15:34:36 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0AC8B1859 for ; Sun, 19 Jul 2015 15:34:36 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by wibud3 with SMTP id ud3so77687447wib.0 for ; Sun, 19 Jul 2015 08:34:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:date:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=jKkK2+5vrcJw4U5How3dMvcP9p5jIpiP0ncYngX7VPo=; b=MjPhwkIDmBXcbnEemJmQTYP7wgjXZJ4QAaKca+7YRdQlX93TGMEO+By3Je44P6fzpm tPG4jkN+o4qSKM8AmQFXY6o3zuQAID0SCQ1+QANb52gIu1jpZ/z55frYaypqvDrR31zx yPa/YB9JYgTlxF7D6T0C6nt672EBzW3USuUBY/Ah5HF7T9r6W1v0n5VPXbEullty+Aer j0tUduM9wNbXCVm1wPvkdmWsM8HryPnZv8hokS4MCuC1dsukgxi4ltCDGJy3CpMJwD28 KtCw2OR0ubvpqqY/o/OKZXAGJsHzvExoR9305Z0ulfaMvHqIMl6wkZ5ntgSMcMSpYc90 t5nw== X-Received: by 10.180.94.7 with SMTP id cy7mr12927730wib.79.1437320074238; Sun, 19 Jul 2015 08:34:34 -0700 (PDT) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de. [188.193.109.133]) by smtp.gmail.com with ESMTPSA id ft5sm7445233wib.4.2015.07.19.08.34.33 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Jul 2015 08:34:33 -0700 (PDT) From: Marc UBM X-Google-Original-From: Marc "UBM" Bocklet Date: Sun, 19 Jul 2015 17:34:32 +0200 To: freebsd-stable Subject: problem with geli and LSI controller Message-Id: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 15:34:36 -0000 Hi all, a few weeks ago our Highpoint Rocket Raid controller (hptrr) started biting the dust (spurious channel resets). We bought a LSI 9201-16i (mps) to replace it. Connected to the hptrr were 4 external e-sata enclosures, configured in JBOD mode. Together with two disks connected to the onboard SATA controller, this formed a geli encrypted raidz-2 zpool. Just now, I connected the disks to the mps controller. They show up fine in dmesg. The problem is, when trying to attach the disks formerly connected to the hptrr controller, geli is unable to find the metadata on the disks and errors out with: "geli: Cannot read metadata from /dev/da4: Invalid argument" gpart show says "gpart: No such geom: da4" Trying to restore the geli metadata gives: "geli: Provider size mismatch: wrong backup file?" Is it possible that the hptrr controller handled the disks in some special way and it's only possible to read them there? Bye Marc From owner-freebsd-stable@freebsd.org Sun Jul 19 15:35:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A77009A57A5 for ; Sun, 19 Jul 2015 15:35:58 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 37B781971 for ; Sun, 19 Jul 2015 15:35:58 +0000 (UTC) (envelope-from ubm.freebsd@googlemail.com) Received: by wibud3 with SMTP id ud3so70826762wib.1 for ; Sun, 19 Jul 2015 08:35:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=from:date:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=Nk0rmT6EVJ6s0fV++Dtout3RsdXnBgNwbE/JgtbxA70=; b=ZmF9NVl5OlCGWRkoAtGg91mlwEEPJSdN4VF4+VdVPkx1C+AMguryY6YchWMHRQWL6u TdBVg0HLDhxxi6sHwtydeCShaekSOi/fuNU9uLxwVmwUvFs6UH99GIDFm6koYZ39592J MyQdOywSDCxVeLSZqtKjTs1GkdiA726cNw18InYBignjsqzjdZm80Dzh0e+WrrbBCfgJ 1nkHpttI/Q3XSzvwMObnWZvYkJc7mStY8s8kvYkfIddDDKW/v3M0/jI0Bk5CGUub1Z4I 3T8cIOM5vyQW8RaRUMKvN5UA5kCJP2+2V9KTU8FfJllRFvVKmZepOeN+e1+2+zO09XqG sMJg== X-Received: by 10.194.120.198 with SMTP id le6mr48261010wjb.133.1437320156115; Sun, 19 Jul 2015 08:35:56 -0700 (PDT) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de. [188.193.109.133]) by smtp.gmail.com with ESMTPSA id ma15sm7427411wic.20.2015.07.19.08.35.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Jul 2015 08:35:55 -0700 (PDT) From: Marc UBM X-Google-Original-From: Marc "UBM" Bocklet Date: Sun, 19 Jul 2015 17:35:54 +0200 To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150719173554.828f30bd2ae605897b7109e6@gmail.com> In-Reply-To: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 15:35:58 -0000 On Sun, 19 Jul 2015 17:34:32 +0200 Marc "UBM" Bocklet wrote: > Hi all, > > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > biting the dust (spurious channel resets). We bought a LSI 9201-16i > (mps) to replace it. Connected to the hptrr were 4 external e-sata > enclosures, configured in JBOD mode. Together with two disks connected > to the onboard SATA controller, this formed a geli encrypted raidz-2 > zpool. > Just now, I connected the disks to the mps controller. They show > up fine in dmesg. The problem is, when trying to attach the disks > formerly connected to the hptrr controller, geli is unable to find the > metadata on the disks and errors out with: > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > gpart show says "gpart: No such geom: da4" > > Trying to restore the geli metadata gives: > "geli: Provider size mismatch: wrong backup file?" > > Is it possible that the hptrr controller handled the disks in some > special way and it's only possible to read them there? > > Bye > Marc I forgot to add that the system is running: FreeBSD xxx 10.1-BETA1 FreeBSD 10.1-BETA1 #27 r271633: Mon Sep 15 22:34:05 CEST 2014 Bye Marc From owner-freebsd-stable@freebsd.org Sun Jul 19 16:16:54 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E01789A5118 for ; Sun, 19 Jul 2015 16:16:54 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8366E10ED for ; Sun, 19 Jul 2015 16:16:53 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t6JGGpRp080991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 19 Jul 2015 09:16:51 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t6JGGpin080990; Sun, 19 Jul 2015 09:16:51 -0700 (PDT) (envelope-from jmg) Date: Sun, 19 Jul 2015 09:16:51 -0700 From: John-Mark Gurney To: Marc UBM Cc: freebsd-stable Subject: Re: problem with geli and LSI controller Message-ID: <20150719161651.GQ8523@funkthat.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Sun, 19 Jul 2015 09:16:51 -0700 (PDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 16:16:55 -0000 Marc UBM via freebsd-stable wrote this message on Sun, Jul 19, 2015 at 17:34 +0200: > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > biting the dust (spurious channel resets). We bought a LSI 9201-16i > (mps) to replace it. Connected to the hptrr were 4 external e-sata > enclosures, configured in JBOD mode. Together with two disks connected > to the onboard SATA controller, this formed a geli encrypted raidz-2 > zpool. > Just now, I connected the disks to the mps controller. They show > up fine in dmesg. The problem is, when trying to attach the disks > formerly connected to the hptrr controller, geli is unable to find the > metadata on the disks and errors out with: > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > gpart show says "gpart: No such geom: da4" > > Trying to restore the geli metadata gives: > "geli: Provider size mismatch: wrong backup file?" > > Is it possible that the hptrr controller handled the disks in some > special way and it's only possible to read them there? This sounds like the drives were in raid0 mode, and not raw disk mode... You might be able to recover the disk w/ geli resize, assuming only space was added at the end, not at the begining, but I have never personally tried that myself... I'd recommend trying on a copy of the drive so you don't loose data if that is possible.. You can also try to find the old geli label w/ a command like: dd if= bs=1m iseek= count=5 | strings -n 9 -td And get current disk size using diskinfo... Something like: #diskinfo /dev/ada0 /dev/ada0 512 3000592982016 5860533168 4096 0 5814021 16 63 #dd if=/dev/ada0 iseek=$((3000592982016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: 1530880 GEOM::ELI 1531392 GEOM::LABEL You might have to go farther back than 1 MB... Good luck... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@freebsd.org Sun Jul 19 18:07:57 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 093489A6700 for ; Sun, 19 Jul 2015 18:07:57 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "neonpark.inter-sonic.com", Issuer "StartCom Class 2 Primary Intermediate Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C20CF1F9B; Sun, 19 Jul 2015 18:07:56 +0000 (UTC) (envelope-from peo@intersonic.se) X-Virus-Scanned: amavisd-new at Intersonic AB Message-ID: <55ABE76C.8050001@intersonic.se> Date: Sun, 19 Jul 2015 20:07:40 +0200 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org CC: James Gritton Subject: Re: jail: /etc/rc: cannot create /dev/null: Operation not supported References: <20150715215253.Horde._Uobbflf4-5sp0TjL7DgCrc@webmail.bsdlabs.com> <55A93AE0.6050204@intersonic.se> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 18:07:57 -0000 On 2015-07-18 18:29, James Gritton wrote: > On 2015-07-17 11:26, Per olof Ljungmark wrote: >> On 2015-07-17 01:41, James Gritton wrote: >>> On 2015-07-15 13:52, Per olof Ljungmark wrote: >>>> FreeBSD 10.2-PRERELEASE #0 r284949 >>>> >>>> The jail can be started, but when /etc/rc is executed: >>>> >>>> root@mar:/ # sh -x /etc/rc >>>> + stty status ^T >>>> /etc/rc: cannot create /dev/null: Operation not supported >>>> + trap : 2 >>>> + trap 'echo '\''Boot interrupted'\''; exit 1' 3 >>>> + HOME=/ >>>> + PATH=/sbin:/bin:/usr/sbin:/usr/bin >>>> + export HOME PATH >>>> + [ '' = autoboot ] >>>> + autoboot=no >>>> + _boot=quietstart >>>> + /sbin/sysctl -n vfs.nfs.diskless_valid >>>> /etc/rc: cannot create /dev/null: Operation not supported >>>> ... >>>> >>>> I have done the procedure several times before but never saw this one >>>> before and don't know how to get around it. >>>> >>>> Ideas anyone? Any recent changes that can show up like the above? >>>> >>>> Thanks! >>> >>> If it's trying to create /dev/null, I assume that the jail's /dev isn't >>> mounted when /etc/rc is running. Do you have mount.devfs set in the >>> jail.conf, or jail_foo_devfs_enable in rc.conf (depending on your >>> configuration)? For that matter, can you tell if the jail's /dev is >>> mounted? >> >> Yes, it's mounted. >> >> Because I can set up jails with an identical procedure on other boxes we >> run I suspect something is wrong with the install so I am starting from >> scratch with this one. >> >> While doing that, I am trying to sort another problem, namely to boot >> zfs on root on a HP Proliant with a P410 controller, but that is another >> story. >> >> You know, if it was easy it would not be interesting... >> >> Thanks! > > So maybe a little late since you're starting over, but another possibility > is the devfs ruleset. If something went wrong in setting that up, you > could well have a devfs mounted that shows no devices. True, although I did check the rulesets. However, since this is a box that will go into production I did not want to take any chances in case we missed something that might show up in other places later. From owner-freebsd-stable@freebsd.org Sun Jul 19 18:25:17 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06AA99A697D for ; Sun, 19 Jul 2015 18:25:17 +0000 (UTC) (envelope-from SRS0=rQ3BvDez=H3=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from vulcan.beatsnet.com (vulcan.beatsnet.com [IPv6:2001:470:1f0b:102::bea1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vulcan.beatsnet.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8ECC618E0; Sun, 19 Jul 2015 18:25:16 +0000 (UTC) (envelope-from SRS0=rQ3BvDez=H3=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from beatsnetcom-MBP15ret.local ([IPv6:2001:1620:f14:0:3417:4e06:64f8:4471]) (authenticated bits=0) by vulcan.beatsnet.com (8.14.9/8.14.9) with ESMTP id t6JIORJp002796 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Sun, 19 Jul 2015 20:24:42 +0200 (CEST) (envelope-from beat.siegenthaler@beatsnet.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=beatsnet.com; s=VULCAN_DKIM; t=1437330313; bh=jw0gdakuQ7PCIfhgtGhRrpzqyPuyb/ztrcD3K66sf7s=; h=From:Subject:To:Date; b=IBBZJ2yBZZOfHHV1xoX2xyaAXPGul4Iwlh43gJVcTbUgb2WFVdGHB2RrNQ1C4K036 1HGoxDqLdzZmTXyxiBlzEvUcTzvvZkniYONobDiTv1rJfxzCv3DcTXM/ydj+d0x+7J OBE2LDx6dG8IaYVpNUfICmlaPJDAsnRPFJlqRPvQ= From: Beat Siegenthaler Subject: cannot compile net/mosquitto port 10.1-STABLE Cc: joe@thrallingpenguin.com, ohauer@FreeBSD.org X-Enigmail-Draft-Status: N1110 To: "freebsd-stable@freebsd.org >> FreeBSD-STABLE Mailing List" Message-ID: <55ABEB59.2040000@beatsnet.com> Date: Sun, 19 Jul 2015 20:24:25 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (vulcan.beatsnet.com [IPv6:2001:470:1f0b:102::bea1]); Sun, 19 Jul 2015 20:24:42 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.98.7 at vulcan.beatsnet.com X-Virus-Status: Clean X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 18:25:17 -0000 Hi, there seems to be some problem with the port, which i cannot resolve with my poor compiler knowledge. Maintainers did not answer. Any hint? regards, Beat [root@myserver:~] # uname -a FreeBSD my.server.com 10.1-STABLE FreeBSD 10.1-STABLE #0 r282210: Wed Apr 29 17:38:56 CEST 2015 [root@myserver:/usr/ports/net/mosquitto] # make ===> License BSD3CLAUSE accepted by the user ===> Found saved configuration for mosquitto-1.3.2 ===> mosquitto-1.4.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by mosquitto-1.4.2 for building ===> Extracting for mosquitto-1.4.2 => SHA256 Checksum OK for mosquitto-1.4.2.tar.gz. ===> Patching for mosquitto-1.4.2 ===> Applying FreeBSD patches for mosquitto-1.4.2 /usr/bin/sed -i.bak -e '/ldconfig/d' /usr/ports/net/mosquitto/work/mosquitto-1.4.2/src/CMakeLists.txt /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/CMakeLists.txt /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/cpp/CMakeLists.txt ===> mosquitto-1.4.2 depends on executable: xsltproc - found ===> mosquitto-1.4.2 depends on file: /usr/local/bin/cmake - found ===> mosquitto-1.4.2 depends on file: /usr/local/bin/python2.7 - found ===> mosquitto-1.4.2 depends on executable: python2 - found ===> mosquitto-1.4.2 depends on shared library: libcares.so - found (/usr/local/lib/libcares.so) ===> Configuring for mosquitto-1.4.2 ===> Performing in-source build /bin/mkdir -p /usr/ports/net/mosquitto/work/mosquitto-1.4.2 -- The C compiler identification is Clang 3.4.1 -- The CXX compiler identification is Clang 3.4.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found OpenSSL: /usr/local/lib/libssl.so;/usr/local/lib/libcrypto.so (found version "1.0.2d") -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_CXX_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS Python_ADDITIONAL_VERSIONS THREADS_HAVE_PTHREAD_ARG -- Build files have been written to: /usr/ports/net/mosquitto/work/mosquitto-1.4.2 ===> Building for mosquitto-1.4.2 Scanning dependencies of target libmosquitto Scanning dependencies of target mosquitto [ 2%] Building C object lib/CMakeFiles/libmosquitto.dir/logging_mosq.c.o [ 4%] Building C object src/CMakeFiles/mosquitto.dir/conf.c.o /usr/ports/net/mosquitto/work/mosquitto-1.4.2/src/conf.c:1427:36: warning: comparison of unsigned expression < 0 is always false [-Wtautological-compare] [ 6%] Building C object lib/CMakeFiles/libmosquitto.dir/memory_mosq.c.o if(config->message_size_limit < 0 || config->message_size_limit > MQTT_MAX_PAYLOAD){ ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~ [ 8%] Building C object lib/CMakeFiles/libmosquitto.dir/messages_mosq.c.o [ 10%] Building C object lib/CMakeFiles/libmosquitto.dir/mosquitto.c.o /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:555:5: warning: implicit declaration of function 'mosquitto_pub_topic_check' is invalid in C99 [-Wimplicit-function-declaration] if(mosquitto_pub_topic_check(topic) != MOSQ_ERR_SUCCESS){ ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:617:5: warning: implicit declaration of function 'mosquitto_sub_topic_check' is invalid in C99 [-Wimplicit-function-declaration] if(mosquitto_sub_topic_check(sub)) return MOSQ_ERR_INVAL; ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9: error: use of undeclared identifier 'MOSQ_ERR_PROXY'; did you mean 'MOSQ_ERR_ERRNO'? case MOSQ_ERR_PROXY: ^~~~~~~~~~~~~~ MOSQ_ERR_ERRNO /usr/local/include/mosquitto.h:100:2: note: 'MOSQ_ERR_ERRNO' declared here MOSQ_ERR_ERRNO = 14, ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1011:9: error: duplicate case value 'MOSQ_ERR_ERRNO' case MOSQ_ERR_ERRNO: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9: note: previous case defined here case MOSQ_ERR_PROXY: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:53: warning: declaration of 'enum mosq_opt_t' will not be visible outside of this function [-Wvisibility] int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:64: error: variable has incomplete type 'enum mosq_opt_t' int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:53: note: forward declaration of 'enum mosq_opt_t' int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1304:8: error: use of undeclared identifier 'MOSQ_ERR_PROXY'; did you mean 'MOSQ_ERR_ERRNO'? case MOSQ_ERR_PROXY: ^~~~~~~~~~~~~~ MOSQ_ERR_ERRNO /usr/local/include/mosquitto.h:100:2: note: 'MOSQ_ERR_ERRNO' declared here MOSQ_ERR_ERRNO = 14, ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1304:8: error: duplicate case value 'MOSQ_ERR_ERRNO' case MOSQ_ERR_PROXY: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1302:8: note: previous case defined here case MOSQ_ERR_ERRNO: ^ 3 warnings and 5 errors generated. --- lib/CMakeFiles/libmosquitto.dir/mosquitto.c.o --- *** [lib/CMakeFiles/libmosquitto.dir/mosquitto.c.o] Error code 1 make[3]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 1 error make[3]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 --- lib/CMakeFiles/libmosquitto.dir/all --- *** [lib/CMakeFiles/libmosquitto.dir/all] Error code 2 make[2]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 1 warning generated. A failure has been detected in another branch of the parallel make make[3]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 --- src/CMakeFiles/mosquitto.dir/all --- *** [src/CMakeFiles/mosquitto.dir/all] Error code 2 make[2]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 2 errors make[2]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 *** [all] Error code 2 make[1]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 1 error make[1]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make: stopped in /usr/ports/net/mosquitto ######################################################################### [root@myserver:/usr/ports/net/mosquitto] # make MAKE_JOBS_UNSAFE=yes install clean ===> License BSD3CLAUSE accepted by the user ===> Found saved configuration for mosquitto-1.3.2 ===> mosquitto-1.4.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by mosquitto-1.4.2 for building ===> Extracting for mosquitto-1.4.2 => SHA256 Checksum OK for mosquitto-1.4.2.tar.gz. ===> Patching for mosquitto-1.4.2 ===> Applying FreeBSD patches for mosquitto-1.4.2 /usr/bin/sed -i.bak -e '/ldconfig/d' /usr/ports/net/mosquitto/work/mosquitto-1.4.2/src/CMakeLists.txt /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/CMakeLists.txt /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/cpp/CMakeLists.txt ===> mosquitto-1.4.2 depends on executable: xsltproc - found ===> mosquitto-1.4.2 depends on file: /usr/local/bin/cmake - found ===> mosquitto-1.4.2 depends on file: /usr/local/bin/python2.7 - found ===> mosquitto-1.4.2 depends on executable: python2 - found ===> mosquitto-1.4.2 depends on shared library: libcares.so - found (/usr/local/lib/libcares.so) ===> Configuring for mosquitto-1.4.2 ===> Performing in-source build /bin/mkdir -p /usr/ports/net/mosquitto/work/mosquitto-1.4.2 -- The C compiler identification is Clang 3.4.1 -- The CXX compiler identification is Clang 3.4.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Found OpenSSL: /usr/local/lib/libssl.so;/usr/local/lib/libcrypto.so (found version "1.0.2d") -- Configuring done -- Generating done CMake Warning: Manually-specified variables were not used by the project: CMAKE_CXX_FLAGS_DEBUG CMAKE_C_FLAGS_DEBUG CMAKE_MODULE_LINKER_FLAGS Python_ADDITIONAL_VERSIONS THREADS_HAVE_PTHREAD_ARG -- Build files have been written to: /usr/ports/net/mosquitto/work/mosquitto-1.4.2 ===> Building for mosquitto-1.4.2 Scanning dependencies of target libmosquitto [ 2%] Building C object lib/CMakeFiles/libmosquitto.dir/logging_mosq.c.o [ 4%] Building C object lib/CMakeFiles/libmosquitto.dir/memory_mosq.c.o [ 6%] Building C object lib/CMakeFiles/libmosquitto.dir/messages_mosq.c.o [ 8%] Building C object lib/CMakeFiles/libmosquitto.dir/mosquitto.c.o /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:555:5: warning: implicit declaration of function 'mosquitto_pub_topic_check' is invalid in C99 [-Wimplicit-function-declaration] if(mosquitto_pub_topic_check(topic) != MOSQ_ERR_SUCCESS){ ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:617:5: warning: implicit declaration of function 'mosquitto_sub_topic_check' is invalid in C99 [-Wimplicit-function-declaration] if(mosquitto_sub_topic_check(sub)) return MOSQ_ERR_INVAL; ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9: error: use of undeclared identifier 'MOSQ_ERR_PROXY'; did you mean 'MOSQ_ERR_ERRNO'? case MOSQ_ERR_PROXY: ^~~~~~~~~~~~~~ MOSQ_ERR_ERRNO /usr/local/include/mosquitto.h:100:2: note: 'MOSQ_ERR_ERRNO' declared here MOSQ_ERR_ERRNO = 14, ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1011:9: error: duplicate case value 'MOSQ_ERR_ERRNO' case MOSQ_ERR_ERRNO: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1009:9: note: previous case defined here case MOSQ_ERR_PROXY: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:53: warning: declaration of 'enum mosq_opt_t' will not be visible outside of this function [-Wvisibility] int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:64: error: variable has incomplete type 'enum mosq_opt_t' int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1191:53: note: forward declaration of 'enum mosq_opt_t' int mosquitto_opts_set(struct mosquitto *mosq, enum mosq_opt_t option, void *value) ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1304:8: error: use of undeclared identifier 'MOSQ_ERR_PROXY'; did you mean 'MOSQ_ERR_ERRNO'? case MOSQ_ERR_PROXY: ^~~~~~~~~~~~~~ MOSQ_ERR_ERRNO /usr/local/include/mosquitto.h:100:2: note: 'MOSQ_ERR_ERRNO' declared here MOSQ_ERR_ERRNO = 14, ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1304:8: error: duplicate case value 'MOSQ_ERR_ERRNO' case MOSQ_ERR_PROXY: ^ /usr/ports/net/mosquitto/work/mosquitto-1.4.2/lib/mosquitto.c:1302:8: note: previous case defined here case MOSQ_ERR_ERRNO: ^ 3 warnings and 5 errors generated. *** Error code 1 Stop. make[3]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 *** Error code 1 Stop. make[2]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 *** Error code 1 Stop. make[1]: stopped in /usr/ports/net/mosquitto/work/mosquitto-1.4.2 *** Error code 1 Stop. make: stopped in /usr/ports/net/mosquitto From owner-freebsd-stable@freebsd.org Sun Jul 19 20:57:28 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C30619A50A6 for ; Sun, 19 Jul 2015 20:57:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68B5119AD for ; Sun, 19 Jul 2015 20:57:28 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t6JKvMoa027228 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 19 Jul 2015 23:57:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t6JKvMoa027228 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t6JKvMQX027227; Sun, 19 Jul 2015 23:57:22 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 19 Jul 2015 23:57:22 +0300 From: Konstantin Belousov To: Andre Meiser Cc: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Message-ID: <20150719205722.GT2404@kib.kiev.ua> References: <20150603145838.GX2499@kib.kiev.ua> <20150614190504.GT2080@kib.kiev.ua> <20150616073637.GO2080@kib.kiev.ua> <20150703211111.GZ2080@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 20:57:28 -0000 On Wed, Jul 15, 2015 at 06:32:13PM +0200, Andre Meiser wrote: > Hi, > > no crash from vim or Xorg but from xterm and again at getcontext(uc) after alloca: > > % readelf -d xterm | grep NEEDED > 0x0000000000000001 (NEEDED) Shared library: [libXinerama.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libXft.so.2] > 0x0000000000000001 (NEEDED) Shared library: [libfontconfig.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libutil.so.9] > 0x0000000000000001 (NEEDED) Shared library: [libXaw.so.7] > 0x0000000000000001 (NEEDED) Shared library: [libXmu.so.6] > 0x0000000000000001 (NEEDED) Shared library: [libXt.so.6] > 0x0000000000000001 (NEEDED) Shared library: [libX11.so.6] > 0x0000000000000001 (NEEDED) Shared library: [libXpm.so.4] > 0x0000000000000001 (NEEDED) Shared library: [libICE.so.6] > 0x0000000000000001 (NEEDED) Shared library: [libulog.so.0] > 0x0000000000000001 (NEEDED) Shared library: [libncurses.so.8] > 0x0000000000000001 (NEEDED) Shared library: [libc.so.7] > > > > (gdb) bt > #0 0x0000000803038642 in check_deferred_signal (curthread=0x805006400) > at /usr/src/lib/libthr/thread/thr_sig.c:332 > #1 0x000000080303858d in _thr_ast (curthread=0x805006400) > at /usr/src/lib/libthr/thread/thr_sig.c:265 > #2 0x000000080303d367 in _thr_rtld_lock_release (lock=) > at /usr/src/lib/libthr/thread/thr_rtld.c:162 > #3 0x000000080067d94d in _r_debug_postinit () from /libexec/ld-elf.so.1 > #4 0x000000080067b15d in .text () from /libexec/ld-elf.so.1 > #5 0x0000000000438007 in ?? () > #6 0x000000000043fe77 in ?? () > #7 0x000000000041808b in ?? () > #8 0x0000000000417e0a in ?? () > #9 0x000000000042e04a in ?? () > #10 0x000000000040823f in ?? () > #11 0x0000000800697000 in ?? () > #12 0x0000000000000000 in ?? () > > > > (gdb) info locals > act = {__sigaction_u = {__sa_handler = 0x7fff00000001, > __sa_sigaction = 0x7fff00000001}, sa_flags = -6472, sa_mask = {__bits = { > 32767, 4198068, 0, 54936355}}} > info = {si_signo = 0, si_errno = 0, si_code = -6472, si_pid = 32767, > si_uid = 4294960256, si_status = 32767, si_addr = 0x800000021, si_value = { > sival_int = -6368, sival_ptr = 0x7fffffffe720, sigval_int = -6368, > sigval_ptr = 0x7fffffffe720}, _reason = {_fault = {_trapno = 15}, > _timer = {_timerid = 15, _overrun = 0}, _mesgq = {_mqd = 15}, _poll = { > _band = 15}, __spare__ = {__spare1__ = 15, __spare2__ = {0, 0, 6909952, > 8, -6496, 32767, 6806459}}}} > > > > (gdb) info registers > rax 0xf0b470 15774832 > rbx 0x805006400 34443650048 > rcx 0x0 0 > rdx 0xca0000 13238272 > rsi 0x7fffffffe6b8 140737488348856 > rdi 0x7fffff0f3150 140737472573776 > rbp 0x7fffffffe650 0x7fffffffe650 > rsp 0x7fffff0f3150 0x7fffff0f3150 > r8 0x12 18 > r9 0x7fffffffe720 140737488348960 > r10 0x4030d0 4206800 > r11 0x261 609 > r12 0x1 1 > r13 0x679320 6787872 > r14 0x7fffff0f3150 140737472573776 > r15 0x23 35 > rip 0x803038642 0x803038642 > eflags 0x10206 66054 > cs 0x43 67 > ss 0x3b 59 > ds 0x0 0 > es 0x0 0 > fs 0x0 0 > gs 0x0 0 > > > > (gdb) disassemble > Dump of assembler code for function check_deferred_signal: > 0x00000008030385f0 : push %rbp > 0x00000008030385f1 : mov %rsp,%rbp > 0x00000008030385f4 : push %r15 > 0x00000008030385f6 : push %r14 > 0x00000008030385f8 : push %rbx > 0x00000008030385f9 : sub $0x78,%rsp > 0x00000008030385fd : mov %rdi,%rbx > 0x0000000803038600 : cmpl $0x0,0x100(%rbx) > 0x0000000803038607 : je 0x803038612 > 0x0000000803038609 : cmpl $0x0,0x180(%rbx) > 0x0000000803038610 : je 0x80303861d > 0x0000000803038612 : lea -0x18(%rbp),%rsp > 0x0000000803038616 : pop %rbx > 0x0000000803038617 : pop %r14 > 0x0000000803038619 : pop %r15 > 0x000000080303861b : pop %rbp > 0x000000080303861c : retq > 0x000000080303861d : movl $0x1,0x180(%rbx) > 0x0000000803038627 : callq 0x803032dfc <__getcontextx_size@plt> > 0x000000080303862c : cltq > 0x000000080303862e : mov %rsp,%r14 > 0x0000000803038631 : add $0xf,%rax > 0x0000000803038635 : and $0xfffffffffffffff0,%rax > 0x0000000803038639 : sub %rax,%r14 > 0x000000080303863c : mov %r14,%rsp > 0x000000080303863f : mov %r14,%rdi > 0x0000000803038642 : callq 0x8030331cc > 0x0000000803038647 : cmpl $0x0,0x100(%rbx) > 0x000000080303864e : je 0x8030386db > 0x0000000803038654 : lea 0x100(%rbx),%r15 > 0x000000080303865b : mov %r14,%rdi > 0x000000080303865e : callq 0x80303301c <__fillcontextx2@plt> > 0x0000000803038663 : movups 0x160(%rbx),%xmm0 > 0x000000080303866a : movups 0x170(%rbx),%xmm1 > 0x0000000803038671 : movaps %xmm1,-0x30(%rbp) > 0x0000000803038675 : movaps %xmm0,-0x40(%rbp) > 0x0000000803038679 : movups 0x150(%rbx),%xmm0 > 0x0000000803038680 : movups %xmm0,(%r14) > 0x0000000803038684 : movups 0x40(%r15),%xmm0 > 0x0000000803038689 : movaps %xmm0,-0x50(%rbp) > 0x000000080303868d : movups (%r15),%xmm0 > 0x0000000803038691 : movups 0x10(%r15),%xmm1 > 0x0000000803038696 : movups 0x20(%r15),%xmm2 > 0x000000080303869b : movups 0x30(%r15),%xmm3 > 0x00000008030386a0 : movaps %xmm3,-0x60(%rbp) > 0x00000008030386a4 : movaps %xmm2,-0x70(%rbp) > 0x00000008030386a8 : movaps %xmm1,-0x80(%rbp) > 0x00000008030386ac : movaps %xmm0,-0x90(%rbp) > 0x00000008030386b3 : movl $0x0,0x100(%rbx) > 0x00000008030386bd : mov -0x90(%rbp),%esi > 0x00000008030386c3 : lea -0x40(%rbp),%rdi > 0x00000008030386c7 : lea -0x90(%rbp),%rdx > 0x00000008030386ce : mov %r14,%rcx > 0x00000008030386d1 : callq 0x803039330 > 0x00000008030386d6 : jmpq 0x803038612 > 0x00000008030386db : movl $0x0,0x180(%rbx) > 0x00000008030386e5 : jmpq 0x803038612 > End of assembler dump. > > > I like the system, but this thread library smells fishy... :( It seems that besides sigreturn(), ucontext symbols must be pre-resolved as well. Try this update (it includes the previous change). diff --git a/lib/libthr/thread/thr_rtld.c b/lib/libthr/thread/thr_rtld.c index 5d89988..cb20098 100644 --- a/lib/libthr/thread/thr_rtld.c +++ b/lib/libthr/thread/thr_rtld.c @@ -185,7 +185,9 @@ _thr_rtld_init(void) { struct RtldLockInfo li; struct pthread *curthread; + ucontext_t *uc; long dummy = -1; + int uc_len; curthread = _get_curthread(); @@ -231,4 +233,9 @@ _thr_rtld_init(void) _thr_signal_block(curthread); _rtld_thread_init(&li); _thr_signal_unblock(curthread); + + uc_len = __getcontextx_size(); + uc = alloca(uc_len); + getcontext(uc); + __fillcontextx2((char *)uc); } diff --git a/lib/libthr/thread/thr_sig.c b/lib/libthr/thread/thr_sig.c index a6d021f..ebb6c58 100644 --- a/lib/libthr/thread/thr_sig.c +++ b/lib/libthr/thread/thr_sig.c @@ -30,6 +30,7 @@ #include #include #include +#include #include #include #include @@ -257,7 +258,7 @@ handle_signal(struct sigaction *actp, int sig, siginfo_t *info, ucontext_t *ucp) /* reschedule cancellation */ check_cancel(curthread, &uc2); errno = err; - __sys_sigreturn(&uc2); + syscall(SYS_sigreturn, &uc2); } void From owner-freebsd-stable@freebsd.org Sun Jul 19 22:00:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F23D29A4140 for ; Sun, 19 Jul 2015 22:00:11 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.server41.configcenter.info (mail.server41.configcenter.info [31.47.242.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B986F1C32 for ; Sun, 19 Jul 2015 22:00:11 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de [188.193.109.133]) (Authenticated sender: web4) by mail.server41.configcenter.info (Postfix) with ESMTP id F27A4142A0B7 for ; Sun, 19 Jul 2015 23:32:09 +0200 (CEST) Date: Sun, 19 Jul 2015 23:32:10 +0200 From: Marc "UBM" Bocklet To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150719233210.9d08c786050491ab37e7cc01@u-boot-man.de> In-Reply-To: <20150719161651.GQ8523@funkthat.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.server41.configcenter.info [0.0.0.0]); Sun, 19 Jul 2015 23:32:10 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Jul 2015 22:00:12 -0000 On Sun, 19 Jul 2015 09:16:51 -0700 John-Mark Gurney wrote: > Marc UBM via freebsd-stable wrote this message on Sun, Jul 19, 2015 at 17:34 +0200: > > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > > biting the dust (spurious channel resets). We bought a LSI 9201-16i > > (mps) to replace it. Connected to the hptrr were 4 external e-sata > > enclosures, configured in JBOD mode. Together with two disks connected > > to the onboard SATA controller, this formed a geli encrypted raidz-2 > > zpool. > > Just now, I connected the disks to the mps controller. They show > > up fine in dmesg. The problem is, when trying to attach the disks > > formerly connected to the hptrr controller, geli is unable to find the > > metadata on the disks and errors out with: > > > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > > > gpart show says "gpart: No such geom: da4" > > > > Trying to restore the geli metadata gives: > > "geli: Provider size mismatch: wrong backup file?" > > > > Is it possible that the hptrr controller handled the disks in some > > special way and it's only possible to read them there? > > This sounds like the drives were in raid0 mode, and not raw disk > mode... You might be able to recover the disk w/ geli resize, > assuming only space was added at the end, not at the begining, but > I have never personally tried that myself... I'd recommend trying > on a copy of the drive so you don't loose data if that is possible.. > > You can also try to find the old geli label w/ a command like: > dd if= bs=1m iseek= count=5 | strings -n 9 -td > > And get current disk size using diskinfo... > > Something like: > #diskinfo /dev/ada0 > /dev/ada0 512 3000592982016 5860533168 4096 0 5814021 16 63 > #dd if=/dev/ada0 iseek=$((3000592982016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: > 1530880 GEOM::ELI > 1531392 GEOM::LABEL > > You might have to go farther back than 1 MB... > > Good luck... Thanks a lot for the input - I'll be trying that as soon as possible and will report back here! Cheers, Marc From owner-freebsd-stable@freebsd.org Mon Jul 20 05:25:56 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 320BA9A6CEF for ; Mon, 20 Jul 2015 05:25:56 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8E631BCE for ; Mon, 20 Jul 2015 05:25:55 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from [109.42.1.89] by msvc-mesg-gmx011.server.lan (via HTTP); Mon, 20 Jul 2015 07:25:31 +0200 Message-ID: From: "Olli Hauer" To: "Beat Siegenthaler" , "freebsd-stable@freebsd.org >> FreeBSD-STABLE Mailing List" Cc: joe@thrallingpenguin.com, ohauer@FreeBSD.org Reply-To: "Olli Hauer" Subject: Re: cannot compile net/mosquitto port 10.1-STABLE Date: Mon, 20 Jul 2015 07:25:31 +0200 X-Provags-ID: V03:K0:jQ6Mo5fTkCBIHu97jOsm5S+28eCV4o9oFEs2eBE0fIN 1BGQ4frZUs3AWG/8Q9NrnvhsdyddeeOkOpmo0Ewb6ExW4V73zC N/DFTbf6h5CRRZUlx4/BG1atLwx2V3mxBBybUXuP8A3BBsDH5b gNQQJnjyUmrHMirCpXUrrn/jzemnMzZiTK+whrBJMvi7qCnywb BuvBquTFBWLlhoDpfOy24NuBn1BkbYRrNQqm4i9JI775uUS918 H26z0CIXoS7GeEGEqf6xtfuZ+9rJ7Hzfko96O7yb62Wf6Qn6My WQbaeA= X-UI-Out-Filterresults: notjunk:1;V01:K0:Bw9ay9AKcNQ=:JrgWmm5BtrqJBk2g24Wxjs XhrI32ytwCkH3JjYV2Qrmo8n61GxbbbfUvn2SrwasJmv8g59K6efPmzzXD1veayzIyZKXmdQ9 /6FX7ouefYaSu5tNMIBvB+97VzRRnlCWO0cAajlT90650nhHIH+LYkVZI10ZbUC06AN77Q5fW hXe2WH4R1c5rFn6cF6cO9HffsR5s+z3EP16Qd94sPduw+G1pCyGUupUPk/1a1XSowfNh7aVub 1HAYHOqQkpharHyqZcctLnaayK2OtjpzFWkax7aQlelU5efCz0Es32D20zwDC6To2pwA9sZoE R2w6ZdtClhG1DdCR2BEmPZORWN96FWvcn+tmV3E5ikvLVXN+vFNobi/JLhwQc853/6E+PIYgK gY7bf6bC9KhziG+VaBysR7hkQJOcYupN7Cx3QfTBiFHI5eSbrs00CsLQOK8A70OTcPWWxMr3i 7bxUlTScvKuMROYjeW8AxEuwRQUBisZiskHfmmj+F6Lq/9ZxB8/J MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 05:25:56 -0000 From owner-freebsd-stable@freebsd.org Mon Jul 20 07:56:55 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C49CA9A6634 for ; Mon, 20 Jul 2015 07:56:55 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.server41.configcenter.info (mail.server41.configcenter.info [31.47.242.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8BB801DEC for ; Mon, 20 Jul 2015 07:56:55 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de [188.193.109.133]) (Authenticated sender: web4) by mail.server41.configcenter.info (Postfix) with ESMTP id BED5F142A0B7 for ; Mon, 20 Jul 2015 09:56:50 +0200 (CEST) Date: Mon, 20 Jul 2015 09:56:50 +0200 From: Marc "UBM" Bocklet To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150720095650.869f85a7f04abf5ade364be3@u-boot-man.de> In-Reply-To: <20150719161651.GQ8523@funkthat.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.server41.configcenter.info [0.0.0.0]); Mon, 20 Jul 2015 09:56:50 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 07:56:55 -0000 On Sun, 19 Jul 2015 09:16:51 -0700 John-Mark Gurney wrote: > Marc UBM via freebsd-stable wrote this message on Sun, Jul 19, 2015 at 17:34 +0200: > > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > > biting the dust (spurious channel resets). We bought a LSI 9201-16i > > (mps) to replace it. Connected to the hptrr were 4 external e-sata > > enclosures, configured in JBOD mode. Together with two disks connected > > to the onboard SATA controller, this formed a geli encrypted raidz-2 > > zpool. > > Just now, I connected the disks to the mps controller. They show > > up fine in dmesg. The problem is, when trying to attach the disks > > formerly connected to the hptrr controller, geli is unable to find the > > metadata on the disks and errors out with: > > > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > > > gpart show says "gpart: No such geom: da4" > > > > Trying to restore the geli metadata gives: > > "geli: Provider size mismatch: wrong backup file?" > > > > Is it possible that the hptrr controller handled the disks in some > > special way and it's only possible to read them there? > > This sounds like the drives were in raid0 mode, and not raw disk > mode... You might be able to recover the disk w/ geli resize, > assuming only space was added at the end, not at the begining, but > I have never personally tried that myself... I'd recommend trying > on a copy of the drive so you don't loose data if that is possible.. > > You can also try to find the old geli label w/ a command like: > dd if= bs=1m iseek= count=5 | strings -n 9 -td > > And get current disk size using diskinfo... > > Something like: > #diskinfo /dev/ada0 > /dev/ada0 512 3000592982016 5860533168 4096 0 5814021 16 63 > #dd if=/dev/ada0 iseek=$((3000592982016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: > 1530880 GEOM::ELI > 1531392 GEOM::LABEL > > You might have to go farther back than 1 MB... > > Good luck... No luck so far, diskinfo gives me: #diskinfo da4 da4 512 2000398934016 3907029168 4096 0 243201 255 63 but #dd if=/dev/da4 iseek=$((2000398934016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: yields nothing. You mentioned I'd have to seek further back than 1MB, how do I do that (I admit I'm having trouble seeing what the calculation you use for iseek does :) )? Thanks, Marc From owner-freebsd-stable@freebsd.org Mon Jul 20 09:28:43 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 172FF9A6835 for ; Mon, 20 Jul 2015 09:28:43 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC96315D7 for ; Mon, 20 Jul 2015 09:28:42 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wicmv11 with SMTP id mv11so10175781wic.0 for ; Mon, 20 Jul 2015 02:28:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=+hgAsHhv1MiMMNzxb2oXcK3HVa+gsYmROtZh8E/Csto=; b=SF3k1myuqCGCNRVQHoBgzFkFJLJsZApDY/DAkk1WaikzVINyoxrkn93RplJVov1oOR 10S8H1rGT0Iq4gTjnclWDgWNgHLJi6pgudTw+vhksE+u13XyZ4SYHKRQ65mDLeF0pkrd VIR7znfp8gqD6VaO3ICqDtlJSzCEblL5OyTcm+yCKvrjpE7EfklLcXIbDFEdVDyssiEH EBl+n2u6d287nanLB9/WxUgAjwZ/NJZuvcdERJbbDYQGwpwgNq/3r1gyCrbT5h+TmI85 +8ebaG1Lnyjs0PQ/bUvQqgv7gBmNKWN7saww9i+Xu47X7if0rS4rmGcveV4e0IWF23X8 kZiA== X-Gm-Message-State: ALoCoQlnfByEN16xowx0plpZa0qWXr125hm5r0nABXnaS/Mp1EuMdpp4AuFjqo/FNuAIMYwiVnLL X-Received: by 10.180.88.196 with SMTP id bi4mr20244110wib.70.1437384515044; Mon, 20 Jul 2015 02:28:35 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id e7sm10860905wib.22.2015.07.20.02.28.32 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jul 2015 02:28:34 -0700 (PDT) Subject: Re: Problems adding Intel 750 to zfs pool To: freebsd-stable@freebsd.org References: <55A9D79E.3070601@techtangents.com> From: Steven Hartland Message-ID: <55ACBF3C.2020208@multiplay.co.uk> Date: Mon, 20 Jul 2015 10:28:28 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55A9D79E.3070601@techtangents.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 09:28:43 -0000 This will almost certainly be due to slow TRIM support on the device. Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding the devices. On 18/07/2015 05:35, dylan@techtangents.com wrote: > Hi, > > I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running > FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. > Apologies if this is the wrong mailing list, or if this has been fixed > in STABLE since the beta. > > Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and > 357GB for l2arc. Adding the slog partition to the pool takes about 2 > minutes - machine seems hung during that time. Ping works, but I can't > open another ssh session. > > Adding the l2arc doesn't seem to complete - it's been going 10 minutes > now and nothing. Ping works, but I can't log in to the local console > or another ssh session. > > I'm adding the partitions using their gpt names. i.e. > zpool add zroot log gpt/slog > zpool add zroot cache gpt/l2arc > > The system BIOS is up-to-date. The OS was a fresh 10.1 install, then > freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms. > > Root is on zfs. > > Device was tested to be working on Windows 8.1 on a Dell T1700 > workstation. > > Any ideas? > > Cheers, > > Dylan Just > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Mon Jul 20 11:32:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 512EF9A5F53 for ; Mon, 20 Jul 2015 11:32:11 +0000 (UTC) (envelope-from will@sundivenetworks.com) Received: from mail.sundivenetworks.net (mail.sundivenetworks.net [212.13.212.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1CD451E97 for ; Mon, 20 Jul 2015 11:32:10 +0000 (UTC) (envelope-from will@sundivenetworks.com) Received: from static45-91.adsl.bogons.net ([85.158.45.91] helo=[192.168.1.127]) by mail.sundivenetworks.net with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZH8tG-000Foh-UA for freebsd-stable@freebsd.org; Mon, 20 Jul 2015 12:05:47 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Problems adding Intel 750 to zfs pool From: Will Green In-Reply-To: <55ACBF3C.2020208@multiplay.co.uk> Date: Mon, 20 Jul 2015 12:06:18 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8BB8F0CB-70D4-4663-AE3C-ECA3ECA99AAD@sundivenetworks.com> References: <55A9D79E.3070601@techtangents.com> <55ACBF3C.2020208@multiplay.co.uk> To: freebsd-stable@freebsd.org X-Mailer: Apple Mail (2.2102) X-Spam_score: -2.9 X-Spam_score_int: -28 X-Spam_bar: -- X-Spam: No X-bounce-key: sundivenetworks.net-1; will@sundivenetworks.com; 1437391931; dbed29e8; X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 11:32:11 -0000 I wonder if this is connected to NVMe? Our SATA Intel DC S3500 drives (which are not that different to the = 750s) TRIM much more quickly. What does camcontrol think the secure erase time should be? For a 600GB = S3500 camcontrol accurately gives the secure erase time as 4 minutes: # camcontrol security ada0 erase time 4 min enhanced erase time 4 min Trimming drives before addition to a system is definitely worthwhile. Will > On 20 Jul 2015, at 10:28, Steven Hartland = wrote: >=20 > This will almost certainly be due to slow TRIM support on the device. >=20 > Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding = the devices. >=20 > On 18/07/2015 05:35, dylan@techtangents.com wrote: >> Hi, >>=20 >> I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 = running FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. = Apologies if this is the wrong mailing list, or if this has been fixed = in STABLE since the beta. >>=20 >> Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and = 357GB for l2arc. Adding the slog partition to the pool takes about 2 = minutes - machine seems hung during that time. Ping works, but I can't = open another ssh session. >>=20 >> Adding the l2arc doesn't seem to complete - it's been going 10 = minutes now and nothing. Ping works, but I can't log in to the local = console or another ssh session. >>=20 >> I'm adding the partitions using their gpt names. i.e. >> zpool add zroot log gpt/slog >> zpool add zroot cache gpt/l2arc >>=20 >> The system BIOS is up-to-date. The OS was a fresh 10.1 install, then = freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms. >>=20 >> Root is on zfs. >>=20 >> Device was tested to be working on Windows 8.1 on a Dell T1700 = workstation. >>=20 >> Any ideas? >>=20 >> Cheers, >>=20 >> Dylan Just >>=20 >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Mon Jul 20 11:32:52 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4032E9A5FC2 for ; Mon, 20 Jul 2015 11:32:52 +0000 (UTC) (envelope-from SRS0=mCYFlBN9=H4=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from vulcan.beatsnet.com (vulcan.beatsnet.com [IPv6:2001:470:1f0b:102::bea1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vulcan.beatsnet.com", Issuer "CAcert Class 3 Root" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E30E6C2; Mon, 20 Jul 2015 11:32:51 +0000 (UTC) (envelope-from SRS0=mCYFlBN9=H4=beatsnet.com=beat.siegenthaler@beatsnet.com) Received: from rc.beatsnet.com (zux165-132.adsl.green.ch [80.254.165.132]) (authenticated bits=0) by vulcan.beatsnet.com (8.14.9/8.14.9) with ESMTP id t6KBWLft031457 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jul 2015 13:32:21 +0200 (CEST) (envelope-from beat.siegenthaler@beatsnet.com) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=beatsnet.com; s=VULCAN_DKIM; t=1437391969; bh=AKuOHzcUVPKA0ChDeS99UdKcucFiN3DU9VbTJgw8GOE=; h=Date:From:To:Subject; b=Bn6Xc8lp05PWR/FOAJkl/N84AZ4DOhSPwAnB6c2RPKJy0yqyymNdT5eXvN75dMHy0 cq46f9cqBkbyBZKO001IQkg552qtXOAUvlQkKSVzZR43Uqs2jIdNJM2rjwsG6uCMZ6 eDXA3jqVTbq93eCMZVBJ1LVtpsH6Ob98Pk/SHllI= MIME-Version: 1.0 Date: Mon, 20 Jul 2015 13:32:16 +0200 From: Beat Siegenthaler To: Olli Hauer Cc: freebsd-stable@freebsd.org, joe@thrallingpenguin.com, ohauer@freebsd.org Subject: Re: cannot compile net/mosquitto port 10.1-STABLE Organization: www.beatsnet.com In-Reply-To: References: Message-ID: <254c69f70c73e56c6286e2e5f7cdf1ad@rc.beatsnet.com> X-Sender: beat.siegenthaler@beatsnet.com User-Agent: Roundcube Webmail/1.1.2 X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (vulcan.beatsnet.com [193.138.215.102]); Mon, 20 Jul 2015 13:32:22 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.98.7 at vulcan.beatsnet.com X-Virus-Status: Clean Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 11:32:52 -0000 Am 2015-07-20 7:25, schrieb Olli Hauer: > Hi Beat, > > it is possible mosquitto builds against an older lib or header that is not up to date. > > Can you run the following command.to [1] create a backup > $ cd empyy_space > $ pkg create mosquitto > > Now remove the old.mosquotto package if you have a baxkup.and try to build.the new version. Ok, found it (partially) rebuilt libxslt cmake and python27 did not solve the problem. The old mosquitto version itself seeed to be the problem. then: make deinstall / make install was a success. normally i use portmaster, or years ago portupgrade for this tasks and it is very rarely that this is not working... regards, Beat Links: ------ [1] http://command.to From owner-freebsd-stable@freebsd.org Mon Jul 20 11:49:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B16D9A621D for ; Mon, 20 Jul 2015 11:49:58 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AEB2097C for ; Mon, 20 Jul 2015 11:49:57 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wibud3 with SMTP id ud3so94424812wib.0 for ; Mon, 20 Jul 2015 04:49:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=el+Hlu4tCxT3BLz99hJEzQsI5Xov5vEMCXLOfBnU96w=; b=KmtZPnYbtj1tjZGfrdcpih0iveo54z4I09T2ukDkSn2ATOC0T/yJ/giybcx/u7k5EI 55152ewXyyyFxy8+36dbbXzaI1SQ8NCIj0KG8SGXZqPGRkWhWpLeIc+m3J09QBesaOSa BUbOk+yE6NS/9KlQQme0Xwv9NTqsimqrseqQYe1Ljt4wYCFY47NKiMdVU7WnpBWnYE5T pzM8p7KVnGu089cro9imTZxar1kUMZCevnXC31sh/WdpK4KbjjUWecZ/RhbeJZoX0wQ0 ehKYh1KewNgT/3Jg0FE1ilI1eeQSw8ASP7fkdPqAWiMwAVZSbthK50hEWQJe91Ka8Bh9 qSAw== X-Gm-Message-State: ALoCoQnORhJCYBZCDYX4aPhxulIleIND+2Vj56YKTKYZFfC3BExYVGSd2v3cskR0A8j3QcnCsmTc X-Received: by 10.180.83.72 with SMTP id o8mr21118359wiy.27.1437392989690; Mon, 20 Jul 2015 04:49:49 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id pn6sm31610949wjb.36.2015.07.20.04.49.49 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jul 2015 04:49:49 -0700 (PDT) Subject: Re: Problems adding Intel 750 to zfs pool To: freebsd-stable@freebsd.org References: <55A9D79E.3070601@techtangents.com> <55ACBF3C.2020208@multiplay.co.uk> <8BB8F0CB-70D4-4663-AE3C-ECA3ECA99AAD@sundivenetworks.com> From: Steven Hartland Message-ID: <55ACE056.6040200@multiplay.co.uk> Date: Mon, 20 Jul 2015 12:49:42 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <8BB8F0CB-70D4-4663-AE3C-ECA3ECA99AAD@sundivenetworks.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 11:49:58 -0000 Those figures are often inaccurate as the actual results can vary wildly based of if the device FW thinks there is actual data on the sectors being TRIM'ed. Regards Steve On 20/07/2015 12:06, Will Green wrote: > I wonder if this is connected to NVMe? > > Our SATA Intel DC S3500 drives (which are not that different to the 750s) TRIM much more quickly. > > What does camcontrol think the secure erase time should be? For a 600GB S3500 camcontrol accurately gives the secure erase time as 4 minutes: > > # camcontrol security ada0 > > erase time 4 min > enhanced erase time 4 min > > Trimming drives before addition to a system is definitely worthwhile. > > Will > >> On 20 Jul 2015, at 10:28, Steven Hartland wrote: >> >> This will almost certainly be due to slow TRIM support on the device. >> >> Try setting the sysctl vfs.zfs.vdev.trim_on_init to 0 before adding the devices. >> >> On 18/07/2015 05:35, dylan@techtangents.com wrote: >>> Hi, >>> >>> I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. Apologies if this is the wrong mailing list, or if this has been fixed in STABLE since the beta. >>> >>> Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 357GB for l2arc. Adding the slog partition to the pool takes about 2 minutes - machine seems hung during that time. Ping works, but I can't open another ssh session. >>> >>> Adding the l2arc doesn't seem to complete - it's been going 10 minutes now and nothing. Ping works, but I can't log in to the local console or another ssh session. >>> >>> I'm adding the partitions using their gpt names. i.e. >>> zpool add zroot log gpt/slog >>> zpool add zroot cache gpt/l2arc >>> >>> The system BIOS is up-to-date. The OS was a fresh 10.1 install, then freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms. >>> >>> Root is on zfs. >>> >>> Device was tested to be working on Windows 8.1 on a Dell T1700 workstation. >>> >>> Any ideas? >>> >>> Cheers, >>> >>> Dylan Just >>> >>> _______________________________________________ >>> freebsd-stable@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Mon Jul 20 12:56:51 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D94929A63CE for ; Mon, 20 Jul 2015 12:56:51 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.server41.configcenter.info (mail.server41.configcenter.info [31.47.242.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A1427D79 for ; Mon, 20 Jul 2015 12:56:50 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de [188.193.109.133]) (Authenticated sender: web4) by mail.server41.configcenter.info (Postfix) with ESMTP id 457A5142A0B7 for ; Mon, 20 Jul 2015 14:56:46 +0200 (CEST) Date: Mon, 20 Jul 2015 14:56:46 +0200 From: Marc "UBM" Bocklet To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150720145646.987e20371fd2ba2343fc8ecb@u-boot-man.de> In-Reply-To: <20150719161651.GQ8523@funkthat.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.server41.configcenter.info [0.0.0.0]); Mon, 20 Jul 2015 14:56:46 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 12:56:51 -0000 On Sun, 19 Jul 2015 09:16:51 -0700 John-Mark Gurney wrote: > Marc UBM via freebsd-stable wrote this message on Sun, Jul 19, 2015 at 17:34 +0200: > > a few weeks ago our Highpoint Rocket Raid controller (hptrr) started > > biting the dust (spurious channel resets). We bought a LSI 9201-16i > > (mps) to replace it. Connected to the hptrr were 4 external e-sata > > enclosures, configured in JBOD mode. Together with two disks connected > > to the onboard SATA controller, this formed a geli encrypted raidz-2 > > zpool. > > Just now, I connected the disks to the mps controller. They show > > up fine in dmesg. The problem is, when trying to attach the disks > > formerly connected to the hptrr controller, geli is unable to find the > > metadata on the disks and errors out with: > > > > "geli: Cannot read metadata from /dev/da4: Invalid argument" > > > > gpart show says "gpart: No such geom: da4" > > > > Trying to restore the geli metadata gives: > > "geli: Provider size mismatch: wrong backup file?" > > > > Is it possible that the hptrr controller handled the disks in some > > special way and it's only possible to read them there? > > This sounds like the drives were in raid0 mode, and not raw disk > mode... You might be able to recover the disk w/ geli resize, > assuming only space was added at the end, not at the begining, but > I have never personally tried that myself... I'd recommend trying > on a copy of the drive so you don't loose data if that is possible.. And one more question, directed at the list: even if geli manages to move the metadata via resize, the gpart metadata is probably still lost? Cheers, Marc From owner-freebsd-stable@freebsd.org Mon Jul 20 13:29:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEDCE9A6C48 for ; Mon, 20 Jul 2015 13:29:16 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from mail.server41.configcenter.info (mail.server41.configcenter.info [31.47.242.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A68C21DB7 for ; Mon, 20 Jul 2015 13:29:16 +0000 (UTC) (envelope-from ubm@u-boot-man.de) Received: from ubm.strangled.net (ipbcc16d85.dynamic.kabel-deutschland.de [188.193.109.133]) (Authenticated sender: web4) by mail.server41.configcenter.info (Postfix) with ESMTP id C04D6142A0B7 for ; Mon, 20 Jul 2015 15:29:12 +0200 (CEST) Date: Mon, 20 Jul 2015 15:29:12 +0200 From: Marc "UBM" Bocklet To: freebsd-stable Subject: Re: problem with geli and LSI controller Message-Id: <20150720152912.b67d215afcd8bc23c39d292f@u-boot-man.de> In-Reply-To: <20150720145646.987e20371fd2ba2343fc8ecb@u-boot-man.de> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> <20150720145646.987e20371fd2ba2343fc8ecb@u-boot-man.de> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.27; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.server41.configcenter.info [0.0.0.0]); Mon, 20 Jul 2015 15:29:12 +0200 (CEST) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 13:29:17 -0000 On Mon, 20 Jul 2015 14:56:46 +0200 Marc "UBM" Bocklet wrote: > > > > This sounds like the drives were in raid0 mode, and not raw disk > > mode... You might be able to recover the disk w/ geli resize, > > assuming only space was added at the end, not at the begining, but > > I have never personally tried that myself... I'd recommend trying > > on a copy of the drive so you don't loose data if that is possible.. > > And one more question, directed at the list: even if geli manages to > move the metadata via resize, the gpart metadata is probably still > lost? Replying to myself again, it appears that the safest way is to get a Rocket Raid controller identical to the one we had, put it in another system, connect the disks, import the old pool and move the data to the new pool on the the LSI controller. Am I overlooking anything? Cheers, Marc From owner-freebsd-stable@freebsd.org Mon Jul 20 13:48:35 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60FB59A5094 for ; Mon, 20 Jul 2015 13:48:35 +0000 (UTC) (envelope-from dewayne.geraghty@consciuminternational.com.au) Received: from hermes.heuristicsystems.com.au (hermes.heuristicsystems.com.au [203.41.22.115]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "hermes.heuristicsystems.com.au", Issuer "Heuristic Systems Type 4 Host CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DAD50A32 for ; Mon, 20 Jul 2015 13:48:34 +0000 (UTC) (envelope-from dewayne.geraghty@consciuminternational.com.au) Received: from [10.0.5.3] (ewsw01.hs [10.0.5.3]) (authenticated bits=0) by hermes.heuristicsystems.com.au (8.14.6/8.13.6) with ESMTP id t6KDlCCc042490 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=FAIL); Mon, 20 Jul 2015 23:47:24 +1000 (EST) (envelope-from dewayne.geraghty@consciuminternational.com.au) Subject: Re: problem with geli and LSI controller To: Marc UBM Bocklet References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> <20150720095650.869f85a7f04abf5ade364be3@u-boot-man.de> From: Dewayne Geraghty X-Enigmail-Draft-Status: N1110 Cc: freebsd-stable Message-ID: <55ACFBED.5040408@consciuminternational.com.au> Date: Mon, 20 Jul 2015 23:47:25 +1000 User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: <20150720095650.869f85a7f04abf5ade364be3@u-boot-man.de> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 13:48:35 -0000 On 20/07/2015 5:56 PM, Marc UBM Bocklet wrote: > On Sun, 19 Jul 2015 09:16:51 -0700 > John-Mark Gurney wrote: > >> Marc UBM via freebsd-stable wrote this message on Sun, Jul 19, 2015 at 17:34 +0200: >>> a few weeks ago our Highpoint Rocket Raid controller (hptrr) started >>> biting the dust (spurious channel resets). We bought a LSI 9201-16i >>> (mps) to replace it. Connected to the hptrr were 4 external e-sata >>> enclosures, configured in JBOD mode. Together with two disks connected >>> to the onboard SATA controller, this formed a geli encrypted raidz-2 >>> zpool. >>> Just now, I connected the disks to the mps controller. They show >>> up fine in dmesg. The problem is, when trying to attach the disks >>> formerly connected to the hptrr controller, geli is unable to find the >>> metadata on the disks and errors out with: >>> >>> "geli: Cannot read metadata from /dev/da4: Invalid argument" >>> >>> gpart show says "gpart: No such geom: da4" >>> >>> Trying to restore the geli metadata gives: >>> "geli: Provider size mismatch: wrong backup file?" >>> >>> Is it possible that the hptrr controller handled the disks in some >>> special way and it's only possible to read them there? >> This sounds like the drives were in raid0 mode, and not raw disk >> mode... You might be able to recover the disk w/ geli resize, >> assuming only space was added at the end, not at the begining, but >> I have never personally tried that myself... I'd recommend trying >> on a copy of the drive so you don't loose data if that is possible.. >> >> You can also try to find the old geli label w/ a command like: >> dd if= bs=1m iseek= count=5 | strings -n 9 -td >> >> And get current disk size using diskinfo... >> >> Something like: >> #diskinfo /dev/ada0 >> /dev/ada0 512 3000592982016 5860533168 4096 0 5814021 16 63 >> #dd if=/dev/ada0 iseek=$((3000592982016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: >> 1530880 GEOM::ELI >> 1531392 GEOM::LABEL >> >> You might have to go farther back than 1 MB... >> >> Good luck... > No luck so far, diskinfo gives me: > > #diskinfo da4 > da4 512 2000398934016 3907029168 4096 0 243201 255 63 > > but > #dd if=/dev/da4 iseek=$((2000398934016/1024/1024-1)) bs=1m 2>/dev/null | strings -n 6 -td | grep GEOM:: > yields nothing. Marc, Sometimes shell scripts calculations can be daunting. Refer to this $((2000398934016/1024/1024-1)) Now the following portion which converts bytes to MB 2000398934016/1024/1024 that is, dividing bytes by 1M (first by 1KB=1024 then again, means its effectively 1Meg) and you have then subtracted 1 MB from it. To step further back from the end of the hard-disk, you could, for example go back 2MB $((2000398934016/1024/1024-2)) From owner-freebsd-stable@freebsd.org Mon Jul 20 14:01:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51F579A54A6 for ; Mon, 20 Jul 2015 14:01:20 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15377112C for ; Mon, 20 Jul 2015 14:01:20 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZHBdA-000INH-Ax; Mon, 20 Jul 2015 16:01:20 +0200 Date: Mon, 20 Jul 2015 16:01:20 +0200 From: Kurt Jaeger To: Marc UBM Bocklet Cc: freebsd-stable Subject: Re: problem with geli and LSI controller Message-ID: <20150720140120.GC49099@home.opsec.eu> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> <20150720145646.987e20371fd2ba2343fc8ecb@u-boot-man.de> <20150720152912.b67d215afcd8bc23c39d292f@u-boot-man.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150720152912.b67d215afcd8bc23c39d292f@u-boot-man.de> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 14:01:20 -0000 Hello, > Replying to myself again, it appears that the safest way is to get a > Rocket Raid controller identical to the one we had, put it in another > system, connect the disks, import the old pool and move the data to the > new pool on the the LSI controller. > > Am I overlooking anything? No, that's the way to do it. There are issues with RAID controllers and the way they store the config data. Some store it in the controller, some in some proprietary way on the disks involved. Most of the time, the config data is non-interchangeable between different manufacturers and sometime even between the same manufacturer and different models. It's a mess. -- pi@opsec.eu +49 171 3101372 5 years to go ! From owner-freebsd-stable@freebsd.org Mon Jul 20 17:00:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 154389A6F6E for ; Mon, 20 Jul 2015 17:00:06 +0000 (UTC) (envelope-from hostmaster@GTS.Net) Received: from ml.gts.net (ml.gts.net [199.246.111.135]) by mx1.freebsd.org (Postfix) with ESMTP id DF9A31439 for ; Mon, 20 Jul 2015 17:00:05 +0000 (UTC) (envelope-from hostmaster@GTS.Net) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #10 built 2013-Jun-8) from fandango.local.gts.net ([10.138.66.7:29886]) (helo=fandango) by ml.gts.net ([199.246.111.135:25]) via TCP with esmtp (/origin:L/R:inet_hosts/T:inet_zone_smtp/dest:R) id (sender ) (ident using UNIX) for (body size 156, total 899 bytes); Mon, 20 Jul 2015 12:57:00 -0400 (EDT) Date: Mon, 20 Jul 2015 12:56:59 -0400 (EDT) From: hotlips Internet admin X-X-Sender: hostmaster@fandango.local.gts.net To: freebsd-stable@freebsd.org Subject: swapcontext missing in libc.so.7 - 10.2.-BETA2 amd64 Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 17:00:06 -0000 please see bug # 201674 @ bugs.freebsd.org for details Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.Net From owner-freebsd-stable@freebsd.org Mon Jul 20 19:37:19 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 405D49A6FB0 for ; Mon, 20 Jul 2015 19:37:19 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 04AC01FA2 for ; Mon, 20 Jul 2015 19:37:18 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1ZHGs4-0003gX-Rb; Mon, 20 Jul 2015 21:37:10 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Oliver Pinter" Cc: freebsd-stable@freebsd.org Subject: Re: iwn & Intel Centrino Advanced-N 6235 support in 10-stable References: Date: Mon, 20 Jul 2015 21:37:04 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50, URIBL_BLOCKED autolearn=disabled version=3.3.1 X-Scan-Signature: 729ef2e9e2cd27dd49f9ca04774c95e6 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 19:37:19 -0000 On Mon, 15 Jun 2015 23:08:36 +0200, Oliver Pinter wrote: > On 6/15/15, Ronald Klop wrote: >> On Wed, 03 Jun 2015 14:25:23 +0200, Oliver Pinter >> wrote: >> >>> On 6/3/15, Ronald Klop wrote: >>>> Hello, >>>> >>>> I see support for the 6235 in iwn(4) is committed in Dec 2013 to >>>> CURRENT >>>> [1]. I would like to buy one of these for a reasonable price [2]. Will >>>> it >>>> be easy to use the driver from current in 10-stable? Or is there a >>>> reason >>>> support for this hardware is not MFC'ed? >>>> >>>> [1] http://svnweb.freebsd.org/base?view=revision&revision=259116 >>>> [2] >>>> http://www.routercenter.nl/product/294857/intel-centrino-advanced-n-6235.html >>>> >>>> A recommendation for a better supported card is also welcome. >>> >>> Hi Ronald! >>> >>> Try this branch: >>> https://github.com/opntr/opBSD/tree/op/stable/10-stable-hbsd-iwn . >>> >>> I backported most of the net80211 and iwn related changes till 2014. >>> August to 10-STABLE in this branch. >> >> Hi, >> >> The card is ordered. Will try your branch soon. Is there more in that >> branch or only WiFi changes? > > The changes are ontop of HardenedBSD, so there are many of changes. > >> >> Cheers, >> Ronald. >> Oliver, Thanks for your info. In the end I decided to go with 11-CURRENT which is running ok with this wifi network card while I'm typing this. Regards, Ronald. From owner-freebsd-stable@freebsd.org Mon Jul 20 21:04:26 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6F929A63F4 for ; Mon, 20 Jul 2015 21:04:26 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id C3C73105B for ; Mon, 20 Jul 2015 21:04:26 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id C0E5D9A63F3; Mon, 20 Jul 2015 21:04:26 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C07C29A63F2 for ; Mon, 20 Jul 2015 21:04:26 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E2121059; Mon, 20 Jul 2015 21:04:26 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t6KL31mb092619; Mon, 20 Jul 2015 14:03:05 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201507202103.t6KL31mb092619@gw.catspoiler.org> Date: Mon, 20 Jul 2015 14:03:01 -0700 (PDT) From: Don Lewis Subject: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? To: emaste@FreeBSD.org cc: stable@FreeBSD.org, makc@FreeBSD.org, re@FreeBSD.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 21:04:26 -0000 Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, which use clang as their base compiler and don't have gcc in base by default, the math/scilab port uses clang for cc and c++ compilation, but finds /usr/include/omp.h (and links to libgomp from lang/gcc). The build succeeds, but I suspect this may not run properly. From owner-freebsd-stable@freebsd.org Mon Jul 20 22:32:29 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0DB609A7438 for ; Mon, 20 Jul 2015 22:32:29 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C518910DE for ; Mon, 20 Jul 2015 22:32:28 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t6KMWRct007684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 20 Jul 2015 15:32:27 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t6KMWQG2007683; Mon, 20 Jul 2015 15:32:26 -0700 (PDT) (envelope-from jmg) Date: Mon, 20 Jul 2015 15:32:26 -0700 From: John-Mark Gurney To: Marc UBM Bocklet Cc: freebsd-stable Subject: Re: problem with geli and LSI controller Message-ID: <20150720223226.GC8523@funkthat.com> References: <20150719173432.16bfa3be6d110571cbc8fe2a@gmail.com> <20150719161651.GQ8523@funkthat.com> <20150720145646.987e20371fd2ba2343fc8ecb@u-boot-man.de> <20150720152912.b67d215afcd8bc23c39d292f@u-boot-man.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150720152912.b67d215afcd8bc23c39d292f@u-boot-man.de> X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Mon, 20 Jul 2015 15:32:27 -0700 (PDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jul 2015 22:32:29 -0000 Marc UBM Bocklet wrote this message on Mon, Jul 20, 2015 at 15:29 +0200: > On Mon, 20 Jul 2015 14:56:46 +0200 > Marc "UBM" Bocklet wrote: > > > > > > > This sounds like the drives were in raid0 mode, and not raw disk > > > mode... You might be able to recover the disk w/ geli resize, > > > assuming only space was added at the end, not at the begining, but > > > I have never personally tried that myself... I'd recommend trying > > > on a copy of the drive so you don't loose data if that is possible.. > > > > And one more question, directed at the list: even if geli manages to > > move the metadata via resize, the gpart metadata is probably still > > lost? It depends.. did you gpart it first and the geli it? or the other way around? If you gpart'd it first, you should be able to see your partitions, if you can't then getting a replacement controller card makes the most sense, as it's likely that the RAID card meta data is at the begining of the drive... gpart also supports the resize command... > Replying to myself again, it appears that the safest way is to get a > Rocket Raid controller identical to the one we had, put it in another > system, connect the disks, import the old pool and move the data to the > new pool on the the LSI controller. > > Am I overlooking anything? Nope... As someone else said, this is the dangers of RAID cards... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-stable@freebsd.org Tue Jul 21 02:09:01 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43D9E9A7946 for ; Tue, 21 Jul 2015 02:09:01 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-Service.CA) Received: from ml.gts.net (ml.gts.net [199.246.111.135]) by mx1.freebsd.org (Postfix) with ESMTP id 1935A16D5 for ; Tue, 21 Jul 2015 02:09:00 +0000 (UTC) (envelope-from hostmaster@GTS.Infra-Service.CA) Received: (using Smail-3.2.0.122-Pre 2005-Nov-17 #10 built 2013-Jun-8) from fandango.local.gts.net ([10.138.66.7:11661]) (helo=fandango) by ml.gts.net ([199.246.111.135:25]) via TCP with esmtp (/origin:L/R:inet_hosts/T:inet_zone_smtp/dest:R) id (sender ) (ident using UNIX) for (body size 324, total 1244 bytes); Mon, 20 Jul 2015 22:08:59 -0400 (EDT) Date: Mon, 20 Jul 2015 22:08:57 -0400 (EDT) From: hotlips Internet admin X-X-Sender: hostmaster@fandango.local.gts.net To: freebsd-stable@freebsd.org Subject: Re: swapcontext missing in libc.so.7 - 10.2.-BETA2 amd64 In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 02:09:01 -0000 On Mon, 20 Jul 2015, hotlips Internet admin wrote: | |please see bug # 201674 @ bugs.freebsd.org for details sorry for false alarm, a previously uncompleted run of subversion was the problem - PR now closed Bruce Becker +1 416 410 0879 GTS Network Administration Toronto, Ont. Email: hostmaster@GTS.Infra-service.CA From owner-freebsd-stable@freebsd.org Tue Jul 21 09:10:14 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 486659A7EE3 for ; Tue, 21 Jul 2015 09:10:14 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D701A1BB9 for ; Tue, 21 Jul 2015 09:10:13 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by wicgb10 with SMTP id gb10so49156148wic.1 for ; Tue, 21 Jul 2015 02:10:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=to:from:subject:message-id:date:user-agent:mime-version :content-type:content-transfer-encoding; bh=EMhDlpKDksM7uBVXzjXsBO+R0LknUBtsscRTYRhp6E4=; b=Xn4z1XJDZTYK1b9HFYluTIGXIPhesMjQJdqn9XGtGpDP2JGgsRc0IGtRKHcgoyJzwb 0XySnBhgXH3Nuh/zRkgWrX3KVh1SuSaSaLIwxbxsX7ALcF00/C4QAsf3flpS50J1B3uf HuNWhC+KSM7wY7a++O7jgREZioDQhno1Plg+h50Jw2Ji+AmCvs9411wH1MAOno9u9fpJ PhhcEYQYSMm+XKHTABTL/vW6ppu1KxoYTb5rPLa74sI6Nb23PEhOQNlUQ1e68ntw8Bbj ex+55J3oIa1EJfkVvauuoInUGngTk8nh9O5SEUF6MrOicXq++XUTn7W2MV9OkIb+QrrL C2kA== X-Received: by 10.194.187.170 with SMTP id ft10mr63616572wjc.26.1437469812375; Tue, 21 Jul 2015 02:10:12 -0700 (PDT) Received: from Johans-MacBook-Air.local (92-70-102-130.glasvezel.netexpo.nl. [92.70.102.130]) by smtp.googlemail.com with ESMTPSA id q4sm35932743wju.14.2015.07.21.02.10.11 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Jul 2015 02:10:11 -0700 (PDT) To: freebsd-stable@freebsd.org From: Johan Hendriks Subject: zfs allow and sharenfs X-Enigmail-Draft-Status: N1110 Message-ID: <55AE0C73.6060705@gmail.com> Date: Tue, 21 Jul 2015 11:10:11 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 09:10:14 -0000 Hello all. I try with the use of zfs allow to create zfs datasets and share them over NFS as a regular user. If I use the zfs create command with the user I get the following errer. # zfs create zroot/usr/home/test-allow cannot share 'zroot/usr/home/test-allow': share(1M) failed filesystem successfully created, but not shared. The dataset is created, but no entry is made in /etc/zfs/export It looks like it can not create the /etc/zfs/exports file and do the mountd restart. If I create the dataset as the root user it creates the dataset and it shares it over NFS, this works well I issued zfs allow username clone,create,destroy,mount,share,sharenfs zroot/usr/home Am I missing something, or is it not possible to do this as a normal user. regards From owner-freebsd-stable@freebsd.org Tue Jul 21 09:37:41 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 055249A644F; Tue, 21 Jul 2015 09:37:41 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id EB7D519F0; Tue, 21 Jul 2015 09:37:40 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 0AE16B14; Tue, 21 Jul 2015 09:37:41 +0000 (UTC) Date: Tue, 21 Jul 2015 09:37:40 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: gjb@FreeBSD.org, jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <547041354.9.1437471460883.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_9-i386 - Build #103 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_9-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 09:37:41 -0000 FreeBSD_STABLE_9-i386 - Build #103 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/103/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/103/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/103/console Change summaries: 285727 by gjb: MFC r285253 (hrs): - Add IPv6 support in quota(1). While rpc.rquotad has supported PF_INET6 for a long time, quota(1) utility supported only PF_INET. - Clean up confusing changes in f_mntfromname. - Add an entry for rquotad with rpc/udp6 to inetd.conf. PR: 194084 Sponsored by: The FreeBSD Foundation The end of the build log: Started by an SCM change Building remotely on kyua1.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_STABLE_9-i386 Updating svn://svnmir.freebsd.org/base/stable/9 at revision '2015-07-21T09:35:05.671 +0000' At revision 285738 No emails were triggered. [FreeBSD_STABLE_9-i386] $ /bin/sh -xe /tmp/hudson4172350033977189728.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_9-i386' + echo env: env: + /usr/bin/env BUILD_NUMBER=103 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_STABLE_9-i386 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/stable/9 BUILDER_JAIL_IP=2610:1c1:1:607c::101:1 jname=FreeBSD_STABLE_9-i386 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=103 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_STABLE_9-i386 BUILD_TAG=jenkins-FreeBSD_STABLE_9-i386-103 NODE_LABELS=jailer kyua1.nyi.freebsd.org BUILD_DISPLAY_NAME=#103 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/103/ SVN_URL_1=svn://svnmir.freebsd.org/base/stable/9 SVN_REVISION=285727 SVN_REVISION_1=285727 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=a4166a1e-ad66-4277-a41d-ee9c3ca86bbe BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_STABLE_9-i386 NODE_NAME=kyua1.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_STABLE_9-i386' setup jail FreeBSD_STABLE_9-i386 + fetch -m http://ftp.freebsd.org:/pub/FreeBSD/snapshots/i386/i386/11.0-CURRENT/base.txz + mkdir FreeBSD_STABLE_9-i386 + cd FreeBSD_STABLE_9-i386 + sudo tar Jxf ../base.txz + cd - + sudo mount -t devfs devfs FreeBSD_STABLE_9-i386/dev + sudo devfs -m FreeBSD_STABLE_9-i386/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_STABLE_9-i386/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_STABLE_9-i386/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::101:1 alias + sudo jail -c persist 'name=FreeBSD_STABLE_9-i386' 'path=FreeBSD_STABLE_9-i386' 'host.hostname=FreeBSD_STABLE_9-i386.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::101:1' 'ip4=disable' allow.chflags jail: "FreeBSD_STABLE_9-i386" already exists Build step 'Execute shell' marked build as failure [PostBuildScript] - Execution post build scripts. [FreeBSD_STABLE_9-i386] $ /bin/sh -xe /tmp/hudson4862749384996070557.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_9-i386' + echo 'clean up jail FreeBSD_STABLE_9-i386' clean up jail FreeBSD_STABLE_9-i386 + sudo jail -r FreeBSD_STABLE_9-i386 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::101:1 -alias + sudo umount FreeBSD_STABLE_9-i386/usr/src + sudo umount FreeBSD_STABLE_9-i386/dev + sudo rm -fr FreeBSD_STABLE_9-i386 rm: FreeBSD_STABLE_9-i386/lib/libthr.so.3: Operation not permitted rm: FreeBSD_STABLE_9-i386/lib/libc.so.7: Operation not permitted rm: FreeBSD_STABLE_9-i386/lib/libcrypt.so.5: Operation not permitted rm: FreeBSD_STABLE_9-i386/lib: Directory not empty rm: FreeBSD_STABLE_9-i386/libexec/ld-elf.so.1: Operation not permitted rm: FreeBSD_STABLE_9-i386/libexec: Directory not empty rm: FreeBSD_STABLE_9-i386/usr/lib/librt.so.1: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/lib: Directory not empty rm: FreeBSD_STABLE_9-i386/usr/bin/crontab: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/login: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/passwd: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/ypchfn: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/opiepasswd: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/ypchpass: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/ypchsh: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/opieinfo: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/yppasswd: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/su: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/chpass: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/chfn: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin/chsh: Operation not permitted rm: FreeBSD_STABLE_9-i386/usr/bin: Directory not empty rm: FreeBSD_STABLE_9-i386/usr: Directory not empty rm: FreeBSD_STABLE_9-i386/sbin/init: Operation not permitted rm: FreeBSD_STABLE_9-i386/sbin: Directory not empty rm: FreeBSD_STABLE_9-i386: Directory not empty + true + sudo chflags -R noschg FreeBSD_STABLE_9-i386 + sudo rm -fr FreeBSD_STABLE_9-i386 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-stable@freebsd.org Tue Jul 21 09:38:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 073029A648E; Tue, 21 Jul 2015 09:38:00 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id ED7981ABC; Tue, 21 Jul 2015 09:37:59 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 4F59BB15; Tue, 21 Jul 2015 09:38:00 +0000 (UTC) Date: Tue, 21 Jul 2015 09:38:00 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <33872640.11.1437471480303.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_10-i386 - Build #290 - Failure MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_10-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 09:38:00 -0000 FreeBSD_STABLE_10-i386 - Build #290 - Failure: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/290/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/290/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/290/console Change summaries: No changes The end of the build log: Started by an SCM change Building remotely on kyua5.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_STABLE_10-i386 FATAL: java.io.EOFException hudson.remoting.RequestAbortedException: java.io.EOFException at hudson.remoting.Request.abort(Request.java:296) at hudson.remoting.Channel.terminate(Channel.java:815) at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ......remote call to kyua5.nyi.freebsd.org(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1361) at hudson.remoting.Request.call(Request.java:171) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:980) at hudson.FilePath.act(FilePath.java:969) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:897) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:833) at hudson.scm.SCM.checkout(SCM.java:485) at hudson.model.AbstractProject.checkout(AbstractProject.java:1282) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1741) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Caused by: java.io.EOFException at org.jenkinsci.remoting.nio.NioChannelHub$3.run(NioChannelHub.java:613) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) [WARNINGS] Skipping publisher since build result is FAILURE [PostBuildScript] - Execution post build scripts. ERROR: Build step failed with exception java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave[kyua5.nyi.freebsd.org] which is computer hudson.slaves.SlaveComputer@feada45 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:76) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204) at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143) at org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105) at org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:85) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671) at hudson.model.Run.execute(Run.java:1766) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Build step 'Execute a set of scripts' marked build as failure Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-stable@freebsd.org Tue Jul 21 09:44:13 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AEC69A6693; Tue, 21 Jul 2015 09:44:13 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 7B4671EA8; Tue, 21 Jul 2015 09:44:13 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 6A842B16; Tue, 21 Jul 2015 09:44:13 +0000 (UTC) Date: Tue, 21 Jul 2015 09:44:13 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1566432072.13.1437471853406.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <33872640.11.1437471480303.JavaMail.jenkins@jenkins-9.freebsd.org> References: <33872640.11.1437471480303.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_10-i386 - Build #291 - Still Failing MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_10-i386 X-Jenkins-Result: FAILURE Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 09:44:13 -0000 FreeBSD_STABLE_10-i386 - Build #291 - Still Failing: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/291/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/291/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/291/console Change summaries: No changes The end of the build log: Started by user lwhsu Building remotely on kyua5.nyi.freebsd.org (jailer) in workspace /jenkins/workspace/FreeBSD_STABLE_10-i386 Updating svn://svnmir.freebsd.org/base/stable/10 at revision '2015-07-21T09:41:40.961 +0000' U sys/dev/xen/netfront/netfront.c U sys/dev/xen/blkfront/block.h U sys/dev/xen/blkfront/blkfront.c U sys/dev/xen/blkback/blkback.c U sys/dev/ixgbe/if_ix.c U sys/xen/interface/io/blkif.h U sys/xen/blkif.h U . At revision 285738 No emails were triggered. [FreeBSD_STABLE_10-i386] $ /bin/sh -xe /tmp/hudson4916912158674838341.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_10-i386' + echo env: env: + /usr/bin/env BUILD_NUMBER=291 HUDSON_SERVER_COOKIE=0657dbe3541f1b1a JOB_NAME=FreeBSD_STABLE_10-i386 LOGNAME=jenkins JAVA_HOME=/usr/local/openjdk8 SVN_URL=svn://svnmir.freebsd.org/base/stable/10 BUILDER_JAIL_IP=2610:1c1:1:607c::105:1 jname=FreeBSD_STABLE_10-i386 JENKINS_URL=https://jenkins.FreeBSD.org/ JENKINS_HOME=/usr/local/jenkins PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin HUDSON_HOME=/usr/local/jenkins OLDPWD=/ BUILD_ID=291 BUILDER_NETIF=igb0 JENKINS_SERVER_COOKIE=0657dbe3541f1b1a PWD=/jenkins/workspace/FreeBSD_STABLE_10-i386 BUILD_TAG=jenkins-FreeBSD_STABLE_10-i386-291 NODE_LABELS=jailer kyua5.nyi.freebsd.org BUILD_DISPLAY_NAME=#291 HOME=/jenkins USER=jenkins BUILD_URL=https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/291/ SVN_URL_1=svn://svnmir.freebsd.org/base/stable/10 SVN_REVISION=285738 SVN_REVISION_1=285738 JOB_URL=https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/ SHELL=/bin/sh HUDSON_URL=https://jenkins.FreeBSD.org/ HUDSON_COOKIE=f5e245b3-e766-46ec-8d4d-1d75fc660d6a BUILDER_RESOLV_CONF=nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n WORKSPACE=/jenkins/workspace/FreeBSD_STABLE_10-i386 NODE_NAME=kyua5.nyi.freebsd.org EXECUTOR_NUMBER=0 + echo 'setup jail FreeBSD_STABLE_10-i386' setup jail FreeBSD_STABLE_10-i386 + fetch -m http://ftp.freebsd.org:/pub/FreeBSD/snapshots/i386/i386/11.0-CURRENT/base.txz + mkdir FreeBSD_STABLE_10-i386 + cd FreeBSD_STABLE_10-i386 + sudo tar Jxf ../base.txz + cd - + sudo mount -t devfs devfs FreeBSD_STABLE_10-i386/dev + sudo devfs -m FreeBSD_STABLE_10-i386/dev rule -s 4 applyset + sudo mount -t nullfs src FreeBSD_STABLE_10-i386/usr/src + printf 'nameserver 2610:1c1:1:6002::100\nnameserver 2610:1c1:1:6002::200\n' + sudo tee FreeBSD_STABLE_10-i386/etc/resolv.conf nameserver 2610:1c1:1:6002::100 nameserver 2610:1c1:1:6002::200 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::105:1 alias + sudo jail -c persist 'name=FreeBSD_STABLE_10-i386' 'path=FreeBSD_STABLE_10-i386' 'host.hostname=FreeBSD_STABLE_10-i386.jail.ci.FreeBSD.org' 'ip6.addr=2610:1c1:1:607c::105:1' 'ip4=disable' allow.chflags jail: "FreeBSD_STABLE_10-i386" already exists Build step 'Execute shell' marked build as failure [WARNINGS] Skipping publisher since build result is FAILURE [PostBuildScript] - Execution post build scripts. [FreeBSD_STABLE_10-i386] $ /bin/sh -xe /tmp/hudson3456503266431942572.sh + export 'PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' + export 'jname=FreeBSD_STABLE_10-i386' + echo 'clean up jail FreeBSD_STABLE_10-i386' clean up jail FreeBSD_STABLE_10-i386 + sudo jail -r FreeBSD_STABLE_10-i386 + sudo ifconfig igb0 inet6 2610:1c1:1:607c::105:1 -alias + sudo umount FreeBSD_STABLE_10-i386/usr/src + sudo umount FreeBSD_STABLE_10-i386/dev + sudo rm -fr FreeBSD_STABLE_10-i386 rm: FreeBSD_STABLE_10-i386/lib/libthr.so.3: Operation not permitted rm: FreeBSD_STABLE_10-i386/lib/libcrypt.so.5: Operation not permitted rm: FreeBSD_STABLE_10-i386/lib/libc.so.7: Operation not permitted rm: FreeBSD_STABLE_10-i386/lib: Directory not empty rm: FreeBSD_STABLE_10-i386/libexec/ld-elf.so.1: Operation not permitted rm: FreeBSD_STABLE_10-i386/libexec: Directory not empty rm: FreeBSD_STABLE_10-i386/sbin/init: Operation not permitted rm: FreeBSD_STABLE_10-i386/sbin: Directory not empty rm: FreeBSD_STABLE_10-i386/usr/lib/librt.so.1: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/lib: Directory not empty rm: FreeBSD_STABLE_10-i386/usr/bin/su: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/chpass: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/chfn: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/chsh: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/yppasswd: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/opieinfo: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/ypchfn: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/login: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/opiepasswd: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/ypchsh: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/ypchpass: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/crontab: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin/passwd: Operation not permitted rm: FreeBSD_STABLE_10-i386/usr/bin: Directory not empty rm: FreeBSD_STABLE_10-i386/usr: Directory not empty rm: FreeBSD_STABLE_10-i386: Directory not empty + true + sudo chflags -R noschg FreeBSD_STABLE_10-i386 + sudo rm -fr FreeBSD_STABLE_10-i386 Email was triggered for: Failure - Any Sending email for trigger: Failure - Any From owner-freebsd-stable@freebsd.org Tue Jul 21 10:30:17 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 100839A759B for ; Tue, 21 Jul 2015 10:30:17 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::3001]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow 2014 CA Root Certificate" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C61F15AC for ; Tue, 21 Jul 2015 10:30:15 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801:0:0:0:4001]) by mta1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPS id t6LAU4RL005595 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 21 Jul 2015 20:30:04 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1437474604; bh=zHKVWquH2pyoHsBPnb2+Rywag5a/F3eTTE4xmWWEf+E=; h=Date:From:To:Subject; b=lxr33ow1UC3vK8ooR5ueQiuQEILawP6wnhDB5PWCf0k69rj5+/p4Ha8QZ4FKnZql2 0q8npd7VK0/a9SQse4ewvOvuBLO5PJwltIHS2S3pGqHJwlDruQhVXdmCEkK/AuTWT8 eY1L4ntpCx5IBeafPbZvzmpUUog2wLMdEmcRne3c= Received: from rwpc16.gfn.riverwillow.net.au (rwpc16.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:ae87:a3ff:fe04:b351]) (authenticated bits=56) by mail1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPSA id t6LATxVB005552 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 21 Jul 2015 20:30:00 +1000 (AEST) Date: Tue, 21 Jul 2015 20:29:58 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: 10.2-BETA2 ntpd problem with autokey Message-ID: <20150721102958.GA32853@rwpc16.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 10:30:17 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Autokey stopped working for me when I upgraded one server and two clients to 10.2-BETA2 and used the base system ntpd. I saw errors like this logged every couple of minutes: ntpd[2169]: crypto_encrypt: error:00000000:lib(0):func(0):reason(0) I build new keys using the base system ntp-keygen and then couldn't start ntpd: ntpd[91910]: crypto_key: error:06074078:digital envelope routines:EVP_PBE= _CipherInit:keygen failure I tracked the problem down to what appears to me to be a stray libmd inclusion in the LDADD assignment in usr.sbin/ntp/ntpd/Makefile. Autokey works fine after rebuilding with libmd excluded. Patch with Bug 201738 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201738 --=20 John Marshall --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWuHyYACgkQw/tAaKKahKINmgCfWU+7xHvOB79IOX2TAWa4WBL6 1s0AoIC8k/+ASmywwPmXtUlzkjb+7LA4 =7Q65 -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR-- From owner-freebsd-stable@freebsd.org Tue Jul 21 10:31:53 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9CC809A7608; Tue, 21 Jul 2015 10:31:53 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 8ADB219E4; Tue, 21 Jul 2015 10:31:53 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id EA60DB2C; Tue, 21 Jul 2015 10:31:53 +0000 (UTC) Date: Tue, 21 Jul 2015 10:31:53 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <1082755147.17.1437474713915.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <547041354.9.1437471460883.JavaMail.jenkins@jenkins-9.freebsd.org> References: <547041354.9.1437471460883.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_9-i386 - Build #104 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_9-i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 10:31:53 -0000 FreeBSD_STABLE_9-i386 - Build #104 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/104/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/104/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_9-i386/104/console Change summaries: No changes From owner-freebsd-stable@freebsd.org Tue Jul 21 10:36:53 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86E539A76DF; Tue, 21 Jul 2015 10:36:53 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (jenkins-9.freebsd.org [8.8.178.209]) by mx1.freebsd.org (Postfix) with ESMTP id 739BA1BA4; Tue, 21 Jul 2015 10:36:53 +0000 (UTC) (envelope-from jenkins-admin@FreeBSD.org) Received: from jenkins-9.freebsd.org (localhost [127.0.0.1]) by jenkins-9.freebsd.org (Postfix) with ESMTP id 6958FB2D; Tue, 21 Jul 2015 10:36:49 +0000 (UTC) Date: Tue, 21 Jul 2015 10:36:44 +0000 (GMT) From: jenkins-admin@FreeBSD.org To: jenkins-admin@FreeBSD.org, freebsd-stable@FreeBSD.org, freebsd-i386@FreeBSD.org Message-ID: <325736100.19.1437475004530.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <1566432072.13.1437471853406.JavaMail.jenkins@jenkins-9.freebsd.org> References: <1566432072.13.1437471853406.JavaMail.jenkins@jenkins-9.freebsd.org> Subject: FreeBSD_STABLE_10-i386 - Build #292 - Fixed MIME-Version: 1.0 X-Jenkins-Job: FreeBSD_STABLE_10-i386 X-Jenkins-Result: SUCCESS Precedence: bulk Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 10:36:53 -0000 FreeBSD_STABLE_10-i386 - Build #292 - Fixed: Build information: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/292/ Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/292/changes Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_STABLE_10-i386/292/console Change summaries: No changes From owner-freebsd-stable@freebsd.org Tue Jul 21 10:54:09 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 25EB89A7A65 for ; Tue, 21 Jul 2015 10:54:09 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D66AF16A9; Tue, 21 Jul 2015 10:54:08 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZHUsh-0007V9-Oq; Tue, 21 Jul 2015 13:34:39 +0300 Date: Tue, 21 Jul 2015 13:34:39 +0300 From: Slawa Olhovchenkov To: freebsd-stable@freebsd.org, Ryan Stone Subject: Re: pmcstat on selected cpu -- posible bug? Message-ID: <20150721103439.GC43740@zxy.spb.ru> References: <20150627120835.GK58397@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150627120835.GK58397@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 10:54:09 -0000 On Sat, Jun 27, 2015 at 03:08:35PM +0300, Slawa Olhovchenkov wrote: > I have dual-socket E5v3 system and try to profiling source of CPU load > on first socket. I am try some expirement and this is like incorrect CPU(socket)/core selecting: selecting '-c 0' allocate system mode PMCs on 'core 0' for all sockets, not for only 'core 0 socket 0'. > cpuset -l 1 pmcstat -S CPU_CLK_UNHALTED_CORE -l 10 -c 1 -n 500 -O sample.out > pmcstat -R sample.out -G out.txt -k /boot/kernel.VSTREAM > cat out.txt | ./stackcollapse-pmc.pl | ./flamegraph.pl --width=1200 > cpi.svg > > cpi.svg can be see at http://zxy.spb.ru/cpi.svg > > I see many times send in t4_intr, but all chelsio interrupt handlers (t4_intr) > binded to second CPU socket: > > # vmstat -i > interrupt total rate > irq9: acpi0 4 0 > irq18: ehci0 ehci1 2893412 2 > irq19: xhci0 3185327 2 > cpu0:timer 1532629922 1093 > irq264: mps0 1399546223 998 > irq265: mps1 3638584876 2595 > irq266: ahci0 3049531638 2175 > irq267: ahci1 707587584 504 > irq268: mps2 6161214642 4395 > irq270: t5nex0:evt 4 0 > irq281: t5nex0:1.0 62811267214 44810 > irq282: t5nex0:1.1 63080900542 45002 > irq283: t5nex0:1.2 62979721970 44930 > irq284: t5nex0:1.3 62968826175 44922 > irq285: t5nex0:1.4 62963754266 44918 > irq286: t5nex0:1.5 63303732253 45161 > irq287: t5nex0:1.6 63012633949 44953 > irq288: t5nex0:1.7 63538714658 45328 > irq289: t5nex0:1,0 73899 0 > irq290: t5nex0:1,1 111666 0 > cpu3:timer 1534027652 1094 > cpu6:timer 1546786165 1103 > cpu13:timer 1588099533 1132 > cpu2:timer 1534703017 1094 > cpu7:timer 1553306409 1108 > cpu9:timer 1586733982 1131 > cpu1:timer 1538685850 1097 > cpu8:timer 1587569958 1132 > cpu5:timer 1537756504 1097 > cpu12:timer 1585898180 1131 > cpu4:timer 1530812247 1092 > cpu10:timer 1586851448 1132 > cpu15:timer 1586024994 1131 > cpu11:timer 1587022608 1132 > cpu14:timer 1586503852 1131 > Total 544625692623 388539 > > # cpuset -g -x 281 > irq 281 mask: 8 > irq 282 mask: 9 > irq 283 mask: 10 > irq 284 mask: 11 > irq 285 mask: 12 > irq 286 mask: 13 > irq 287 mask: 14 > irq 288 mask: 15 > irq 289 mask: 8 > irq 290 mask: 12 > > Cross-checked by dtrace: > # dtrace -n '::t4_intr:entry { @[stringof(curthread->td_name), curthread->td_oncpu] = count(); }' > dtrace: description '::t4_intr:entry ' matched 1 probe > ^C > > irq282: t5nex0:1.1 9 361413 > irq281: t5nex0:1.0 8 361573 > irq285: t5nex0:1.4 12 364535 > irq283: t5nex0:1.2 10 365919 > irq284: t5nex0:1.3 11 366386 > irq287: t5nex0:1.6 14 367603 > irq286: t5nex0:1.5 13 368409 > irq288: t5nex0:1.7 15 371441 > > What is wrong? Bug in pmcstat? > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Tue Jul 21 15:33:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0342D9A7F3D for ; Tue, 21 Jul 2015 15:33:11 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DDF56114C for ; Tue, 21 Jul 2015 15:33:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id DA8FE9A7F3C; Tue, 21 Jul 2015 15:33:10 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D92CF9A7F3B for ; Tue, 21 Jul 2015 15:33:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id BE575114B; Tue, 21 Jul 2015 15:33:10 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id E195F1BC6; Tue, 21 Jul 2015 15:33:09 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Tue, 21 Jul 2015 15:33:07 +0000 From: Glen Barber To: Don Lewis , Ed Maste Cc: stable@FreeBSD.org, makc@FreeBSD.org, re@FreeBSD.org Subject: Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? Message-ID: <20150721153307.GA76998@FreeBSD.org> References: <201507202103.t6KL31mb092619@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PNTmBPCT7hxwcZjr" Content-Disposition: inline In-Reply-To: <201507202103.t6KL31mb092619@gw.catspoiler.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 15:33:11 -0000 --PNTmBPCT7hxwcZjr Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Jul 20, 2015 at 02:03:01PM -0700, Don Lewis wrote: > Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, > which use clang as their base compiler and don't have gcc in base by > default, the math/scilab port uses clang for cc and c++ compilation, but > finds /usr/include/omp.h (and links to libgomp from lang/gcc). The > build succeeds, but I suspect this may not run properly. >=20 Ed, do you have any input on this? Glen --PNTmBPCT7hxwcZjr Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVrmYzAAoJEAMUWKVHj+KTM8oP/Roa/yoDpwTp6sY1MBV/f+/R 4minqP8mHFbdS9IYM+OcX/vSje2AxKHWxufjeuOUO5UUXoYKzc+yeYBHICmZDJwk FQ5UkA4PwAIpSR3rGf+pSbYbXw0Za7ssFWpKQO6i3yKsAQBfB1UQR6jcgIkg07RG 3cbY4AIUD5Ig5fKrAuJv6j0IS53jfkBdgEvjPpFb2ZrQirVKrorX9mnpAXYbW7DE BFg234aNutya2Rfo3gSEV7V4ggTldY6u3wez9aHE2x9Q8q5+ZGXD4WXTGeOWclSc VYLGtnzv0rxGjwFRG215a2bYo8qkytirCvfdx/wt5Q94rznPlPIjOE0V3flTechE byRGl9xmG+HBJprgPMyF2cWX29Pdtna1LVZ9woEo+6hQUp9T6fym3yWE8zTCHFXj iD07RG26a1NRINhCa5ykq2sWCWTGjiWBYyFXGDHAwaFH1Q67XgJ24L1cKdrQQxYf Kr8n59O/Eun8KiYpAdlYtHR3viHB1MKOdKqnIRx8/JisQjnXtlzF6tx3tSsyhcVd w+4KbclhKL63CQ3ookTREM1TEEYdEIsPIJF9k2swDwocm5S7sneIAM7BywWIzuPo xvIK1wuRMvm/x6sSWDHKRHEyjbE/7RNfYCFbBjDwbjwOQn2elNATLdK+8iYfCOnN QVOKdIp6YJwUAAH72ISq =A1xp -----END PGP SIGNATURE----- --PNTmBPCT7hxwcZjr-- From owner-freebsd-stable@freebsd.org Tue Jul 21 20:54:55 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 027499A6C6C for ; Tue, 21 Jul 2015 20:54:55 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-oi0-x234.google.com (mail-oi0-x234.google.com [IPv6:2607:f8b0:4003:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF08B1FE7 for ; Tue, 21 Jul 2015 20:54:54 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: by oihq81 with SMTP id q81so131747788oih.2 for ; Tue, 21 Jul 2015 13:54:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7Kz2XZ3MUsRgVnKzqK/GgbDwwV4MvqPDZuAOSi0k8ds=; b=zOQg7fr4na2EL2+3oOP9ecJjq8At1oK98eZRmIM6cxx/GlLOF1B3vQh77j7eHUI2hy kW/twYyRCJ7fb9u55y7g6HYhz/x/wfst83c5BnG0P58bHNXNAT+IKzo5TRqaEXtt50Wz pBcoODYb1UUOYbenCfxYS9davgaMgiACaqj714VwFqRfyGxsY/XIvdof0h9p2k2Nk+E5 bueXtlFVfb8d7wJYaj9Ocw7CzmYpqPkugb/rsX4ga3WIFOZnc3aTeAr03WRK50Hv3MIa XlaL6DYtlRuI1ajT2sGtidTn7JBH1hEPQmWK4a7c9JZ4g27CjjUC8EBjM0bfekq6G2Xn UM6w== MIME-Version: 1.0 X-Received: by 10.182.236.7 with SMTP id uq7mr32826004obc.42.1437512094002; Tue, 21 Jul 2015 13:54:54 -0700 (PDT) Received: by 10.202.104.65 with HTTP; Tue, 21 Jul 2015 13:54:53 -0700 (PDT) In-Reply-To: <55A9D79E.3070601@techtangents.com> References: <55A9D79E.3070601@techtangents.com> Date: Tue, 21 Jul 2015 13:54:53 -0700 Message-ID: Subject: Re: Problems adding Intel 750 to zfs pool From: Jim Harris To: "dylan@techtangents.com" Cc: FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 20:54:55 -0000 On Fri, Jul 17, 2015 at 9:35 PM, dylan@techtangents.com < dylan@techtangents.com> wrote: > Hi, > > I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running > FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. Apologies > if this is the wrong mailing list, or if this has been fixed in STABLE > since the beta. > > Anyway, I've gparted it into 2 partitions - 16GB for slog/zil and 357GB > for l2arc. Adding the slog partition to the pool takes about 2 minutes - > machine seems hung during that time. Ping works, but I can't open another > ssh session. > > Adding the l2arc doesn't seem to complete - it's been going 10 minutes now > and nothing. Ping works, but I can't log in to the local console or another > ssh session. > > I'm adding the partitions using their gpt names. i.e. > zpool add zroot log gpt/slog > zpool add zroot cache gpt/l2arc > > The system BIOS is up-to-date. The OS was a fresh 10.1 install, then > freebsd-update to 10.2-beta2. 10.1 exhibited the same symptoms. > > Root is on zfs. > > Device was tested to be working on Windows 8.1 on a Dell T1700 workstation. > > Any ideas? > Hi Dylan, I just committed SVN r285767 which should fix this issue. I will request MFC to stable/10 after the 3 day waiting period. Thanks, -Jim > Cheers, > > Dylan Just > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > From owner-freebsd-stable@freebsd.org Tue Jul 21 21:31:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5988D9A7322 for ; Tue, 21 Jul 2015 21:31:08 +0000 (UTC) (envelope-from dylan@techtangents.com) Received: from p3plsmtpa07-04.prod.phx3.secureserver.net (p3plsmtpa07-04.prod.phx3.secureserver.net [173.201.192.233]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client CN "Bizanga Labs SMTP Client Certificate", Issuer "Bizanga Labs CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 31CA810C8 for ; Tue, 21 Jul 2015 21:31:07 +0000 (UTC) (envelope-from dylan@techtangents.com) Received: from [192.168.12.129] ([118.208.95.204]) by p3plsmtpa07-04.prod.phx3.secureserver.net with id v9VU1q0024QaD9A019VVpw; Tue, 21 Jul 2015 14:29:30 -0700 Message-ID: <55AEB9B6.1040608@techtangents.com> Date: Wed, 22 Jul 2015 07:29:26 +1000 From: "dylan@techtangents.com" User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: Jim Harris CC: FreeBSD-STABLE Mailing List Subject: Re: Problems adding Intel 750 to zfs pool References: <55A9D79E.3070601@techtangents.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Jul 2015 21:31:08 -0000 > Jim Harris > 22 July 2015 6:54 am > > > Hi Dylan, > > I just committed SVN r285767 which should fix this issue. I will > request MFC to stable/10 after the 3 day waiting period. > > Thanks, > > -Jim > Love your work, Jim! Thank you. From owner-freebsd-stable@freebsd.org Wed Jul 22 07:19:36 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6C3469A8E15 for ; Wed, 22 Jul 2015 07:19:36 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id E72BE1DD5 for ; Wed, 22 Jul 2015 07:19:35 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 1C2BB929B037 for ; Wed, 22 Jul 2015 09:10:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id pa7k-pszTyCe for ; Wed, 22 Jul 2015 09:10:18 +0200 (CEST) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 63B7F929B033 for ; Wed, 22 Jul 2015 09:10:18 +0200 (CEST) Received: by beast.freibergnet.de (Postfix, from userid 201) id 37CE14B783C; Wed, 22 Jul 2015 09:10:18 +0200 (CEST) Date: Wed, 22 Jul 2015 09:10:18 +0200 From: Holm Tiffe To: freebsd-stable@freebsd.org Subject: 10.2-Beta i386..what's wrong..? Message-ID: <20150722071018.GA8363@beast.freibergnet.de> Reply-To: holm@freibergnet.de Mail-Followup-To: Holm Tiffe , freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 07:19:36 -0000 Hi, yesterday I've decided to to put my old "Workstation" in my shack and to install a new FreeBSD on it, it is the computer I've used previously for my daily work, reading Mails, programming controllers and so on.. It is am AMD XP300+ with an Adaptec 29320 and four IBM 72GB SCSI3 Disks with only 2GB of Memory. I've replaced a bad disk, reformated it so 512 Byte sectors )they came original with 534 or so for ecc),pulled the 10.2-Beta disk1 ISO file from the german mirror and tried to install on a zfs raidz1 which was going flawlessly until the point of booting the installed system, some warnings about zfs and vm... double fault, panic. Later I've read on the net that installing zfs on a 32Bit machine isn't really a good idea, so I tried to install the system on a gvinum raid on gpt partitions. The layout was gpt-boot, 2G swap and the rest raid on every disk so that I could build a striped 8G swap and ~190G raid with gvinum. Installing that worked flawlessly with the install point "shell and doing partitioning per hand". I've made a newfs -U -L root /dev/gvinum/raid, mounted the filesystem to /mnt, activated the swap and put an fstab in /tmp/bsdsomething-etc, exited to install. The installer verified the install containers (base.txz,kernel.txz and so on) and begun to extract them. So far soo good, but while extracting the system repeatedly hung on the very same location. On vt4 I could start a top that was showing an hung bsdtar process in the state wdrain and nothing other happened, the system took a long time to react to keypresses.. I've tried to extract the distribution files per hand, same problem, tar hung on extracting kernel.symbols for example, same behavior on other files in base.txz. Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, ok tried 9.3-RELEASE .. the same! What I'm doning wrong here? Besides of the bad disk that I've changed (IBM-SSG S53D073 C61F) the hardware is very trusty, it is a gigabyte board and I want to keep this machine since it has still floppy capabilites that I need to comunicate with my old CP/M gear and PDP11's. It run for years w/o problems. Capacitors are already changed and ok. Sorry for the wishy-washy error messages above, they are from my memory and from yesterday... Next try was installing the System on a 8G ATA disk that was laying around, went flawlessly, booted it and tried to install the files on the gvinum raid from there...same problem. Changed the 29320 against a 29160 ..same problem. No messages about bad disksor something on the console. What's going on here? The machine run on 8.4-stable before w/o any problems. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, info@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Wed Jul 22 08:21:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 162669A8ACE for ; Wed, 22 Jul 2015 08:21:11 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com [209.85.212.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 998DA1B36 for ; Wed, 22 Jul 2015 08:21:10 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wibud3 with SMTP id ud3so160176001wib.0 for ; Wed, 22 Jul 2015 01:21:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=ysytWojV7WGfp/LVLL215C7998CqBm/n54xR4rF1TG8=; b=LpsOkm7qYtohWkhX9Z9sXSJAaq9K5rD8VjoZRt4BIix3sbsoBwgHytZP6JbvLYMWdw JpsntYFrGCXzTAUWDNpdXbt0c+rgZxQ845u+lirwzrGgVO+p4Y+wAsP4s1xLSLgseHtS fVksFn2fS6IKv+sU4cqMp/kmCU/B3nnyzv9HQgK7+mKiZU5mSiNbKzN2zbol3asUFTIH 1BUUZRFUUdNG8C0YigzJeaINRartCKZ7Mz+9jMwrE5KFlc7skM8JrmtCjaRTOXYWaTsV wSzxKE8y4hScqjBtr4QVOXEOcdKYCSMSG9Q2sLfvRPXGYu80gWmTyIoSWjkiDZ7hHkzK O9zw== X-Gm-Message-State: ALoCoQmTagIyM4TnxfmHnI2eMzxLfgMxICFPpiSnx/wLFAPl80AuPYOWOJpe1U5O7M/jdawNdTV8 X-Received: by 10.180.88.196 with SMTP id bi4mr40379735wib.70.1437553262217; Wed, 22 Jul 2015 01:21:02 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id s16sm20748978wib.16.2015.07.22.01.21.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2015 01:21:01 -0700 (PDT) Subject: Re: Problems adding Intel 750 to zfs pool To: freebsd-stable@freebsd.org References: <55A9D79E.3070601@techtangents.com> <55AEB9B6.1040608@techtangents.com> From: Steven Hartland Message-ID: <55AF526B.8030607@multiplay.co.uk> Date: Wed, 22 Jul 2015 09:20:59 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <55AEB9B6.1040608@techtangents.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 08:21:11 -0000 Be aware that kern.geom.dev.delete_max_sectors will still come into play here hence the large request will still get chunked. This is good to prevent excessively long running individual BIO's which would result in user operations being uncancelable. Regards Steve On 21/07/2015 22:29, dylan@techtangents.com wrote: > > >> Jim Harris >> 22 July 2015 6:54 am >> >> >> Hi Dylan, >> >> I just committed SVN r285767 which should fix this issue. I will >> request MFC to stable/10 after the 3 day waiting period. >> >> Thanks, >> >> -Jim >> > Love your work, Jim! Thank you. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Wed Jul 22 08:31:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2EA89A8DF2 for ; Wed, 22 Jul 2015 08:31:02 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63A2810E6 for ; Wed, 22 Jul 2015 08:31:02 +0000 (UTC) (envelope-from killing@multiplay.co.uk) Received: by wibxm9 with SMTP id xm9so90374953wib.1 for ; Wed, 22 Jul 2015 01:31:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-type :content-transfer-encoding; bh=spIhLdycLZgmHOcCF7CrkFPiTmJz/nvoSFksF0r16kI=; b=HTKsnepN9NLUArvAm0g9+5ZmMhl927T9mIn1X/xGPjFY4NJQ8n3UXZ3LZtA0g3W9VJ MuPzVb1YxjWj/i975Ha7k0Ad+FzPr06yBZr8LKuUoIR+CYvNSweKOQ1ZJdwWsGdYKymn jybpIjcmyDv6syLAtCNd8Zj32wMQFrRM3oSV9wMmZ7A0oErAnrlzxC+qfpTuFjg1ZjlS a9/Bg+79m0sJH2kgK/AdgA6o1SbDpszLSceH4Q1XMPYwZKNL+8WLhr0E9HSg2QNKcOUT b7v6ACi2m/w0DBvS7doTMNXEF3mEvB1bkEnK8J9uoaMoftbh4qZ161EjKfBPU7w3YKfg DO8A== X-Gm-Message-State: ALoCoQkLpwRmfs2iQu6eumCM1zAMErmehI+KH3NiMHr5LqC4jtu36XgTV7IkRIrzexs9P+PAXreq X-Received: by 10.194.235.227 with SMTP id up3mr3039865wjc.132.1437553860172; Wed, 22 Jul 2015 01:31:00 -0700 (PDT) Received: from [10.10.1.68] (82-69-141-170.dsl.in-addr.zen.co.uk. [82.69.141.170]) by smtp.gmail.com with ESMTPSA id uc16sm20806759wib.8.2015.07.22.01.30.59 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 22 Jul 2015 01:30:59 -0700 (PDT) Subject: Re: 10.2-Beta i386..what's wrong..? To: freebsd-stable@freebsd.org References: <20150722071018.GA8363@beast.freibergnet.de> From: Steven Hartland Message-ID: <55AF54C1.8050002@multiplay.co.uk> Date: Wed, 22 Jul 2015 09:30:57 +0100 User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: <20150722071018.GA8363@beast.freibergnet.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 08:31:03 -0000 What's the panic? As your using ZFS I'd lay money on the fact your blowing the stack, which would require kernel built with: options KSTACK_PAGES=4 Regards Steve On 22/07/2015 08:10, Holm Tiffe wrote: > Hi, > > yesterday I've decided to to put my old "Workstation" in my shack and > to install a new FreeBSD on it, it is the computer I've used previously > for my daily work, reading Mails, programming controllers and so on.. > > It is am AMD XP300+ with an Adaptec 29320 and four IBM 72GB SCSI3 Disks > with only 2GB of Memory. > > I've replaced a bad disk, reformated it so 512 Byte sectors )they came > original with 534 or so for ecc),pulled the 10.2-Beta disk1 ISO file from > the german mirror and tried to install on a zfs raidz1 which was going > flawlessly until the point of booting the installed system, some warnings > about zfs and vm... double fault, panic. > > Later I've read on the net that installing zfs on a 32Bit machine isn't > really a good idea, so I tried to install the system on a gvinum raid > on gpt partitions. > The layout was gpt-boot, 2G swap and the rest raid on every disk so > that I could build a striped 8G swap and ~190G raid with gvinum. > Installing that worked flawlessly with the install point "shell and doing > partitioning per hand". I've made a newfs -U -L root /dev/gvinum/raid, > mounted the filesystem to /mnt, activated the swap and put an fstab in > /tmp/bsdsomething-etc, exited to install. > > The installer verified the install containers (base.txz,kernel.txz and > so on) and begun to extract them. > So far soo good, but while extracting the system repeatedly hung on the > very same location. On vt4 I could start a top that was showing an hung > bsdtar process in the state wdrain and nothing other happened, the system > took a long time to react to keypresses.. > > I've tried to extract the distribution files per hand, same problem, tar > hung on extracting kernel.symbols for example, same behavior on other files > in base.txz. > > Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, > ok tried 9.3-RELEASE .. the same! > > What I'm doning wrong here? > > Besides of the bad disk that I've changed (IBM-SSG S53D073 C61F) the > hardware is very trusty, it is a gigabyte board and I want to keep this > machine since it has still floppy capabilites that I need to comunicate > with my old CP/M gear and PDP11's. It run for years w/o problems. > Capacitors are already changed and ok. > > Sorry for the wishy-washy error messages above, they are from my memory and > from yesterday... > > Next try was installing the System on a 8G ATA disk that was laying around, > went flawlessly, booted it and tried to install the files on the gvinum > raid from there...same problem. > Changed the 29320 against a 29160 ..same problem. > No messages about bad disksor something on the console. > > What's going on here? The machine run on 8.4-stable before w/o any > problems. > > Regards, > > Holm From owner-freebsd-stable@freebsd.org Wed Jul 22 09:51:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5F51C9A6555 for ; Wed, 22 Jul 2015 09:51:58 +0000 (UTC) (envelope-from ortadur@web.de) Received: from mout.web.de (mout.web.de [212.227.15.4]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.web.de", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E122D16DA for ; Wed, 22 Jul 2015 09:51:57 +0000 (UTC) (envelope-from ortadur@web.de) Received: from [131.169.71.113] by 3capp-webde-bs25.server.lan (via HTTP); Wed, 22 Jul 2015 11:46:35 +0200 MIME-Version: 1.0 Message-ID: From: "Andre Meiser" To: "Konstantin Belousov" Cc: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Content-Type: text/plain; charset=UTF-8 Date: Wed, 22 Jul 2015 11:46:35 +0200 Importance: normal Sensitivity: Normal In-Reply-To: <20150719205722.GT2404@kib.kiev.ua> References: <20150603145838.GX2499@kib.kiev.ua> <20150614190504.GT2080@kib.kiev.ua> <20150616073637.GO2080@kib.kiev.ua> <20150703211111.GZ2080@kib.kiev.ua> , <20150719205722.GT2404@kib.kiev.ua> X-UI-Message-Type: mail X-Priority: 3 X-Provags-ID: V03:K0:Pi0Jj8DfnXw/8nxfAhgM3FLuoejEoAZ0Z3LUuzkkiTN SEG2twUENORnjHTSyDgiUxIyg22w7qfAmNQ4z1FtvUAAwI5vDK tcNPAFmmNS2b+aQMa2Vx80eXA59XyJR4h3Z46YJmqTSli/iHIS JdbPVa4qpm34H6hJGK8dKA9H0cFNS00pWmW7HWeXoVTYRt/hBf rZ6MDB6xpuP94PbUQv4JaNiT/y61OyPdnsnKFQM7c1DWVvm+Jr LkLcYBQhENaZ4qiYm8qsq0YUMsqk2ecnulbAPUJoYonBVOwz8c bF4MzY= X-UI-Out-Filterresults: notjunk:1;V01:K0:dWALVRYcPFc=:2hw0o8AKYM1ME3F78PuJL4 2zDh5uFTEZLl7js6K772F2XcYh5/twA2sak+L6Jes3Ke3thYWjnpe8n3WR6WZnu3BBHMmTaoS v+tJY1dGoGPHbWxUPd9Su/9jLVy3bpNKdl6W3AsHKMe/7/pq23J1CfDgn38uCrYvPUVIJsHbm dK5/qfPp41ErZk7G7NrE8LTIMwqB4bS2YmY9vhD212VI2thtywofxOBWV2/cMpMggF65kvm7N vJWyrhKf1ASxP+/H31WOf2ch3hpE58vQUpNS0lO5k4INSqu4F7cUr0xljR2pbNmyodSYpikpM u6x4IkUE56g2BtRG2bvB+yG0hhpN9Et/UDWwm5j5OhH+HHljJfMq63Ly0HgxLVE2Wow7RrPqa eV8ihbq2q/aiNk5Xp0G6OarjnImydSnQupB57WRevOQ6AHwtCcpv2gfEWIPQ3X2Buocm4uPAP pRdan0twolKd6Vfsq8lrcHXc/VKDVZdsfcRnMdq9dEbjW0ti0vietwSjJzcgsFhakRirIy2U2 BRN4hhFrRNLT9ADxfiK/V0= X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 09:51:58 -0000 On Sun, Jul 19, 2015 at 22:57 +0200, Konstantin Belousov wrote: > It seems that besides sigreturn(), ucontext symbols must be pre-resolved > as well. Try this update (it includes the previous change). thanks for looking into this, but this patch wasn't funny at all. Did you tested your patch? Almost every programme crashed with a core dump. Here the example for simply starting vim: % readelf -d vim | grep NEEDED 0x0000000000000001 (NEEDED) Shared library: [libm.so.5] 0x0000000000000001 (NEEDED) Shared library: [libncurses.so.8] 0x0000000000000001 (NEEDED) Shared library: [libintl.so.8] 0x0000000000000001 (NEEDED) Shared library: [libpython2.7.so.1] 0x0000000000000001 (NEEDED) Shared library: [libthr.so.3] 0x0000000000000001 (NEEDED) Shared library: [libc.so.7] (gdb) bt #0 0x00000008014a30d4 in _thr_rtld_init () at /usr/src/lib/libthr/thread/thr_rtld.c:239 #1 0x00000008014a2f03 in _libpthread_init (curthread=) at /usr/src/lib/libthr/thread/thr_init.c:372 #2 0x00000008014a5c22 in _thread_printf () from /lib/libthr.so.3 #3 0x0000000801498d06 in _init () from /lib/libthr.so.3 #4 0x00007fffffffe000 in ?? () #5 0x000000080083d6bf in r_debug_state () from /libexec/ld-elf.so.1 #6 0x000000080083cd17 in __tls_get_addr () from /libexec/ld-elf.so.1 #7 0x000000080083b129 in .text () from /libexec/ld-elf.so.1 #8 0x0000000000000000 in ?? () (gdb) info locals li = {rtli_version = 0, lock_create = 0x8014a30f0 <_thr_rtld_lock_create>, lock_destroy = 0x8014a3160 <_thr_rtld_lock_destroy>, rlock_acquire = 0x8014a31b0 <_thr_rtld_rlock_acquire>, wlock_acquire = 0x8014a3270 <_thr_rtld_wlock_acquire>, lock_release = 0x8014a3300 <_thr_rtld_lock_release>, thread_set_flag = 0x8014a33c0 <_thr_rtld_set_flag>, thread_clr_flag = 0x8014a33d0 <_thr_rtld_clr_flag>, at_fork = 0} dummy = -1 curthread = (struct pthread *) 0x7fffff0f2650 uc_len = eflags 0x10206 66054 cs 0x43 67 ss 0x3b 59 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 (gdb) disassemble Dump of assembler code for function _thr_rtld_init: 0x00000008014a2fe0 <_thr_rtld_init+0>: push %rbp 0x00000008014a2fe1 <_thr_rtld_init+1>: mov %rsp,%rbp 0x00000008014a2fe4 <_thr_rtld_init+4>: push %rbx 0x00000008014a2fe5 <_thr_rtld_init+5>: sub $0x58,%rsp 0x00000008014a2fe9 <_thr_rtld_init+9>: movq $0xffffffffffffffff,-0x58(%rbp) 0x00000008014a2ff1 <_thr_rtld_init+17>: mov %fs:0x10,%rbx 0x00000008014a2ffa <_thr_rtld_init+26>: lea -0x58(%rbp),%rdi 0x00000008014a2ffe <_thr_rtld_init+30>: mov $0x3,%esi 0x00000008014a3003 <_thr_rtld_init+35>: mov $0x1,%edx 0x00000008014a3008 <_thr_rtld_init+40>: xor %ecx,%ecx 0x00000008014a300a <_thr_rtld_init+42>: xor %r8d,%r8d 0x00000008014a300d <_thr_rtld_init+45>: callq 0x8014a5890 <_umtx_op_err> 0x00000008014a3012 <_thr_rtld_init+50>: callq 0x80149916c <__error@plt> 0x00000008014a3017 <_thr_rtld_init+55>: xor %edi,%edi 0x00000008014a3019 <_thr_rtld_init+57>: xor %esi,%esi 0x00000008014a301b <_thr_rtld_init+59>: xor %edx,%edx 0x00000008014a301d <_thr_rtld_init+61>: callq 0x8014990ac 0x00000008014a3022 <_thr_rtld_init+66>: callq 0x8014991ac <_rtld_get_stack_prot@plt> 0x00000008014a3027 <_thr_rtld_init+71>: lea 0xc2(%rip),%rax # 0x8014a30f0 <_thr_rtld_lock_create> 0x00000008014a302e <_thr_rtld_init+78>: mov %rax,-0x48(%rbp) 0x00000008014a3032 <_thr_rtld_init+82>: lea 0x127(%rip),%rax # 0x8014a3160 <_thr_rtld_lock_destroy> 0x00000008014a3039 <_thr_rtld_init+89>: mov %rax,-0x40(%rbp) 0x00000008014a303d <_thr_rtld_init+93>: lea 0x16c(%rip),%rax # 0x8014a31b0 <_thr_rtld_rlock_acquire> 0x00000008014a3044 <_thr_rtld_init+100>: mov %rax,-0x38(%rbp) 0x00000008014a3048 <_thr_rtld_init+104>: lea 0x221(%rip),%rax # 0x8014a3270 <_thr_rtld_wlock_acquire> 0x00000008014a304f <_thr_rtld_init+111>: mov %rax,-0x30(%rbp) 0x00000008014a3053 <_thr_rtld_init+115>: lea 0x2a6(%rip),%rax # 0x8014a3300 <_thr_rtld_lock_release> 0x00000008014a305a <_thr_rtld_init+122>: mov %rax,-0x28(%rbp) 0x00000008014a305e <_thr_rtld_init+126>: lea 0x35b(%rip),%rax # 0x8014a33c0 <_thr_rtld_set_flag> 0x00000008014a3065 <_thr_rtld_init+133>: mov %rax,-0x20(%rbp) 0x00000008014a3069 <_thr_rtld_init+137>: lea 0x360(%rip),%rax # 0x8014a33d0 <_thr_rtld_clr_flag> 0x00000008014a3070 <_thr_rtld_init+144>: mov %rax,-0x18(%rbp) 0x00000008014a3074 <_thr_rtld_init+148>: movq $0x0,-0x10(%rbp) 0x00000008014a307c <_thr_rtld_init+156>: xor %edi,%edi 0x00000008014a307e <_thr_rtld_init+158>: callq 0x8014991dc <_rtld_atfork_pre@plt> 0x00000008014a3083 <_thr_rtld_init+163>: xor %edi,%edi 0x00000008014a3085 <_thr_rtld_init+165>: callq 0x801498dbc <_rtld_atfork_post@plt> 0x00000008014a308a <_thr_rtld_init+170>: callq 0x801498e3c <_malloc_prefork@plt> 0x00000008014a308f <_thr_rtld_init+175>: callq 0x80149919c <_malloc_postfork@plt> 0x00000008014a3094 <_thr_rtld_init+180>: mov $0x14,%edi 0x00000008014a3099 <_thr_rtld_init+185>: xor %eax,%eax 0x00000008014a309b <_thr_rtld_init+187>: callq 0x8014990fc 0x00000008014a30a0 <_thr_rtld_init+192>: mov %rbx,%rdi 0x00000008014a30a3 <_thr_rtld_init+195>: callq 0x80149e4f0 <_thr_signal_block> 0x00000008014a30a8 <_thr_rtld_init+200>: lea -0x50(%rbp),%rdi 0x00000008014a30ac <_thr_rtld_init+204>: callq 0x801498f3c <_rtld_thread_init@plt> 0x00000008014a30b1 <_thr_rtld_init+209>: mov %rbx,%rdi 0x00000008014a30b4 <_thr_rtld_init+212>: callq 0x80149e530 <_thr_signal_unblock> 0x00000008014a30b9 <_thr_rtld_init+217>: callq 0x801498dfc <__getcontextx_size@plt> 0x00000008014a30be <_thr_rtld_init+222>: cltq 0x00000008014a30c0 <_thr_rtld_init+224>: mov %rsp,%rbx 0x00000008014a30c3 <_thr_rtld_init+227>: add $0xf,%rax 0x00000008014a30c7 <_thr_rtld_init+231>: and $0xfffffffffffffff0,%rax 0x00000008014a30cb <_thr_rtld_init+235>: sub %rax,%rbx 0x00000008014a30ce <_thr_rtld_init+238>: mov %rbx,%rsp 0x00000008014a30d1 <_thr_rtld_init+241>: mov %rbx,%rdi 0x00000008014a30d4 <_thr_rtld_init+244>: callq 0x8014991cc 0x00000008014a30d9 <_thr_rtld_init+249>: mov %rbx,%rdi 0x00000008014a30dc <_thr_rtld_init+252>: callq 0x80149901c <__fillcontextx2@plt> 0x00000008014a30e1 <_thr_rtld_init+257>: lea -0x8(%rbp),%rsp 0x00000008014a30e5 <_thr_rtld_init+261>: pop %rbx 0x00000008014a30e6 <_thr_rtld_init+262>: pop %rbp 0x00000008014a30e7 <_thr_rtld_init+263>: retq End of assembler dump. Sincerely yours Andre. From owner-freebsd-stable@freebsd.org Wed Jul 22 10:21:02 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B7779A6CC1 for ; Wed, 22 Jul 2015 10:21:02 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDB611A1B for ; Wed, 22 Jul 2015 10:21:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id t6MAKtY1066132 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 22 Jul 2015 13:20:56 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua t6MAKtY1066132 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id t6MAKt94066130; Wed, 22 Jul 2015 13:20:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 22 Jul 2015 13:20:55 +0300 From: Konstantin Belousov To: Andre Meiser Cc: freebsd-stable@freebsd.org Subject: Re: Many core dumps in pthread_getspecific. Message-ID: <20150722102055.GA2072@kib.kiev.ua> References: <20150603145838.GX2499@kib.kiev.ua> <20150614190504.GT2080@kib.kiev.ua> <20150616073637.GO2080@kib.kiev.ua> <20150703211111.GZ2080@kib.kiev.ua> <20150719205722.GT2404@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 10:21:02 -0000 On Wed, Jul 22, 2015 at 11:46:35AM +0200, Andre Meiser wrote: > On Sun, Jul 19, 2015 at 22:57 +0200, Konstantin Belousov wrote: > > It seems that besides sigreturn(), ucontext symbols must be pre-resolved > > as well. Try this update (it includes the previous change). > > thanks for looking into this, but this patch wasn't funny at all. Did you tested your patch? Almost every programme crashed with a core dump. Here the example for simply starting vim: > > % readelf -d vim | grep NEEDED > 0x0000000000000001 (NEEDED) Shared library: [libm.so.5] > 0x0000000000000001 (NEEDED) Shared library: [libncurses.so.8] > 0x0000000000000001 (NEEDED) Shared library: [libintl.so.8] > 0x0000000000000001 (NEEDED) Shared library: [libpython2.7.so.1] > 0x0000000000000001 (NEEDED) Shared library: [libthr.so.3] > 0x0000000000000001 (NEEDED) Shared library: [libc.so.7] > > > (gdb) bt > #0 0x00000008014a30d4 in _thr_rtld_init () at /usr/src/lib/libthr/thread/thr_rtld.c:239 > #1 0x00000008014a2f03 in _libpthread_init (curthread=) at /usr/src/lib/libthr/thread/thr_init.c:372 > #2 0x00000008014a5c22 in _thread_printf () from /lib/libthr.so.3 > #3 0x0000000801498d06 in _init () from /lib/libthr.so.3 > #4 0x00007fffffffe000 in ?? () > #5 0x000000080083d6bf in r_debug_state () from /libexec/ld-elf.so.1 > #6 0x000000080083cd17 in __tls_get_addr () from /libexec/ld-elf.so.1 > #7 0x000000080083b129 in .text () from /libexec/ld-elf.so.1 > #8 0x0000000000000000 in ?? () > > > (gdb) info locals > li = {rtli_version = 0, lock_create = 0x8014a30f0 <_thr_rtld_lock_create>, lock_destroy = 0x8014a3160 <_thr_rtld_lock_destroy>, > rlock_acquire = 0x8014a31b0 <_thr_rtld_rlock_acquire>, wlock_acquire = 0x8014a3270 <_thr_rtld_wlock_acquire>, > lock_release = 0x8014a3300 <_thr_rtld_lock_release>, thread_set_flag = 0x8014a33c0 <_thr_rtld_set_flag>, > thread_clr_flag = 0x8014a33d0 <_thr_rtld_clr_flag>, at_fork = 0} > dummy = -1 > curthread = (struct pthread *) 0x7fffff0f2650 > uc_len = > > (gdb) info registers > rax 0xf0b470 15774832 > rbx 0x7fffff0f2650 140737472570960 > rcx 0x0 0 > rdx 0xca0000 13238272 > rsi 0x8024064e8 34397512936 > rdi 0x7fffff0f2650 140737472570960 > rbp 0x7fffffffdb20 0x7fffffffdb20 > rsp 0x7fffff0f2650 0x7fffff0f2650 > r8 0x0 0 > r9 0xfffff8000e35f4c0 -8795854605120 > r10 0x0 0 > r11 0x246 582 > r12 0x800a54a28 34370570792 > r13 0x800a545b0 34370569648 > r14 0x1 1 > r15 0x800855420 34368476192 > rip 0x8014a30d4 0x8014a30d4 <_thr_rtld_init+244> > eflags 0x10206 66054 > cs 0x43 67 > ss 0x3b 59 > ds 0x0 0 > es 0x0 0 > fs 0x0 0 > gs 0x0 0 %rbp-%rsp == 0xf0b4d0 == 15774928 Can you do the following: 1. Compile and run the program at the end of the message and send me the output. 2. Also send me the first 40 lines of the dmesg for bootverbose boot. 3. (Optional) Install x86info program, compiled from the sources on github, https://github.com/dankamongmen/x86info, then run, as root kldload cpuctl x86info -a #include extern int __getcontextx_size(void); int main(void) { printf("%#x\n", __getcontextx_size()); } From owner-freebsd-stable@freebsd.org Wed Jul 22 10:56:26 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6ECF9A7477 for ; Wed, 22 Jul 2015 10:56:26 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: from smtp.new-ukraine.org (smtp.new-ukraine.org [148.251.53.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.new-ukraine.org", Issuer "smtp.new-ukraine.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 567061A9C for ; Wed, 22 Jul 2015 10:56:25 +0000 (UTC) (envelope-from zeus@ibs.dn.ua) Received: on behalf of honored client by smtp.new-ukraine.org with ESMTP id t6MArwkU070270 for on Wed, 22 Jul 2015 13:54:00 +0300 (EEST) Message-ID: <20150722135353.70269@smtp.new-ukraine.org> Date: Wed, 22 Jul 2015 13:53:53 +0300 From: "Zeus Panchenko" To: cc: Subject: [panic] 10.1-RELEASE-p14 #4 r285499M sporadic reboot Organization: I.B.S. LLC Reply-To: "Zeus Panchenko" X-Attribution: zeus Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAFVBMVEWxsbGdnZ3U1NQTExN cXFzx8fG/v7+f8hyWAAACXUlEQVQ4jUWSwXYiIRBFi4yyhtjtWpmRdTL0ZC3TJOukDa6Rc+T/P2F eFepwtFvr8upVFVDua8mLWw6La4VIKTuMdAPOebdU55sQs3n/D1xFFPFGVGh4AHKttr5K0bS6g7N ZCge7qpVLB+f1Z2WAj2OKXwIWt/bXpdXSiu8KXbviWkHxF5td9+lg2e3xlI2SCvatK8YLfHyh9lw 15yrad8Va5eXg4Llr7QmAaC+dL9sDt9iad/DX3OKvLMBf+dm0A0QuMrTvYIevSik1IaSVvgjIHt5 lSCG2ynNRpEcBZ8cgDWk+Ns99qzsYYV3MZoppWzGtYlTO9+meG6m/g92iNO9LfQB2JZsMpoJs7QG ku2KtabRK0bZRwDLyBDvwlxTm6ZlP7qyOqLcfqtLexpDSB4M0H3I/PQy1emvjjzgK+A0LmMKl6Lq zlqzh0VGAw440F6MJd8cY0nI7wiF/fVIBGY7UNCAXy6DmfYGCLLI0wtDbVcDUMqtJLmAhLqODQAe riERAxXJ1/QYGpa0ymqyytpKC19MNXHjvFmEsfcHIrncFR4xdbYWgmfEGLCcZokpGbGj1egMR+6M 1BkNX1pDdhPcOXpAnAeLQUwQLYepgQoZVNGS61yaE8CYA7gYAcWKzwGstACY2HTFvvOwk4FXAG/a mKHni/EcA/GkOk7I0IK7UMIf3+SahU8/FJdiE7KcuWdM3MFocUDEEIX9LfJoo4xV5tnNKc3jJuSs SZWgnnhepgU1zN4Hii18yW4RwDX52CXUtk0Hqz6cHOIUkWaX8fDcB+J7y1y2xDHwjv/8Buu8Ekz6 7tXQAAAAASUVORK5CYII= X-Mailer: MH-E 8.3.1; GNU Mailutils 2.99.98; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-NewUkraine-Agent: mailfromd (7.99.92) X-NewUkraine-URL: https://mail.prozora-kraina.org/smtp.html X-NewUkraine-VirStat: NO X-NewUkraine-VirScan: ScanPE, ScanELF, ScanOLE2, ScanMail, PhishingSignatures, ScanHTML, ScanPDF X-NewUkraine-SpamStat: NO X-NewUkraine-SpamScore: -1.600 of 3.500 X-NewUkraine-SpamKeys: AWL,BAYES_00,NO_RECEIVED,NO_RELAYS X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 10:56:27 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, on important production server I've started to experience weird regular (once a day-two) sporadic reboots after last upgrade (2015-07-17), and would appreciate if someone could help me to analyze further and fix the issue. Collected crash information below full logs are available upon request. Thank you! backtrace: =2D ---[ quotation start ]------------------------------------------- fo02.ibs dumped core - see /var/crash/vmcore.2 Wed Jul 22 08:01:15 EEST 2015 FreeBSD fo02.ibs 10.1-RELEASE-p14 FreeBSD 10.1-RELEASE-p14 #4 r285499M: Fri= Jul 17 22:45:54 EEST 2015 root@fo02.ibs:/usr/obj/usr/src/sys/FO02.2015= 0307233500 amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain condition= s. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid =3D 3; apic id =3D 06 fault virtual address =3D 0xffff80403c82b740 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff80730e9c stack pointer =3D 0x28:0xfffffe000023d790 frame pointer =3D 0x28:0xfffffe000023d7a0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (irq283: igb3:que 3) trap number =3D 12 panic: page fault cpuid =3D 3 KDB: stack backtrace: #0 0xffffffff804fe970 at kdb_backtrace+0x60 #1 0xffffffff804c52a5 at panic+0x155 #2 0xffffffff8073f1cf at trap_fatal+0x38f #3 0xffffffff8073f4e8 at trap_pfault+0x308 #4 0xffffffff8073eb4a at trap+0x47a #5 0xffffffff80724cb2 at calltrap+0x8 #6 0xffffffff807910cb at bounce_bus_dmamap_load_buffer+0x1bb #7 0xffffffff804f9c82 at bus_dmamap_load_mbuf_sg+0x72 #8 0xffffffff810c37fe at igb_refresh_mbufs+0x19e #9 0xffffffff810c3603 at igb_rxeof+0x683 #10 0xffffffff810c3ab4 at igb_msix_que+0xe4 #11 0xffffffff80498e1b at intr_event_execute_handlers+0xab #12 0xffffffff80499266 at ithread_loop+0x96 #13 0xffffffff80496a3a at fork_exit+0x9a #14 0xffffffff807251ee at fork_trampoline+0xe Uptime: 1d10h23m19s Dumping 1191 out of 8136 MB:..2%..11%..21%..31%..41%..52%..61%..72%..81%..9= 2% Reading symbols from /boot/kernel/zfs.ko.symbols...done. Loaded symbols for /boot/kernel/zfs.ko.symbols Reading symbols from /boot/kernel/opensolaris.ko.symbols...done. Loaded symbols for /boot/kernel/opensolaris.ko.symbols Reading symbols from /boot/kernel/pf.ko.symbols...done. Loaded symbols for /boot/kernel/pf.ko.symbols Reading symbols from /boot/kernel/if_igb.ko.symbols...done. Loaded symbols for /boot/kernel/if_igb.ko.symbols Reading symbols from /boot/kernel/coretemp.ko.symbols...done. Loaded symbols for /boot/kernel/coretemp.ko.symbols Reading symbols from /boot/kernel/aesni.ko.symbols...done. Loaded symbols for /boot/kernel/aesni.ko.symbols Reading symbols from /boot/kernel/crypto.ko.symbols...done. Loaded symbols for /boot/kernel/crypto.ko.symbols Reading symbols from /boot/kernel/cryptodev.ko.symbols...done. Loaded symbols for /boot/kernel/cryptodev.ko.symbols Reading symbols from /boot/kernel/pflog.ko.symbols...done. Loaded symbols for /boot/kernel/pflog.ko.symbols Reading symbols from /boot/kernel/ichsmb.ko.symbols...done. Loaded symbols for /boot/kernel/ichsmb.ko.symbols Reading symbols from /boot/kernel/smbus.ko.symbols...done. Loaded symbols for /boot/kernel/smbus.ko.symbols Reading symbols from /boot/kernel/if_bridge.ko.symbols...done. Loaded symbols for /boot/kernel/if_bridge.ko.symbols Reading symbols from /boot/kernel/bridgestp.ko.symbols...done. Loaded symbols for /boot/kernel/bridgestp.ko.symbols Reading symbols from /boot/kernel/ums.ko.symbols...done. Loaded symbols for /boot/kernel/ums.ko.symbols #0 doadump (textdump=3D) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=3D) at pcpu.h:219 #1 0xffffffff804c4f22 in kern_reboot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:452 #2 0xffffffff804c52e4 in panic (fmt=3D) at /usr/src/sys/kern/kern_shutdown.c:759 #3 0xffffffff8073f1cf in trap_fatal (frame=3D,=20 eva=3D) at /usr/src/sys/amd64/amd64/trap.c:865 #4 0xffffffff8073f4e8 in trap_pfault (frame=3D0xfffffe000023d6e0,=20 usermode=3D) at /usr/src/sys/amd64/amd64/trap.c:676 #5 0xffffffff8073eb4a in trap (frame=3D0xfffffe000023d6e0) at /usr/src/sys/amd64/amd64/trap.c:440 #6 0xffffffff80724cb2 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0xffffffff80730e9c in pmap_kextract (va=3D729286318152418877) at /usr/src/sys/amd64/amd64/pmap.c:639 #8 0xffffffff807910cb in bounce_bus_dmamap_load_buffer ( dmat=3D0xfffff800034c1800, map=3D0xffffffff80be01e8,=20 buf=3D, buflen=3D,=20 pmap=3D0xffffffff80c52ce0, flags=3D,=20 segs=3D) at /usr/src/sys/x86/x86/busdma_bounce.c:6= 90 #9 0xffffffff804f9c82 in bus_dmamap_load_mbuf_sg (dmat=3D0xfffff800034c180= 0,=20 map=3D0x0, m0=3D, segs=3D0xfffffe000023d8b0,=20 nsegs=3D0xfffffe000023d8ac, flags=3D) at /usr/src/sys/kern/subr_bus_dma.c:110 #10 0xffffffff810c37fe in igb_refresh_mbufs (rxr=3D0xfffff8000349f330,=20 limit=3D2101) at /usr/src/sys/modules/igb/../../dev/e1000/if_igb.c:4144 #11 0xffffffff810c3603 in igb_rxeof (count=3D) at /usr/src/sys/modules/igb/../../dev/e1000/if_igb.c:4998 #12 0xffffffff810c3ab4 in igb_msix_que (arg=3D0xfffff800034a8b38) at /usr/src/sys/modules/igb/../../dev/e1000/if_igb.c:1621 #13 0xffffffff80498e1b in intr_event_execute_handlers ( p=3D, ie=3D0xfffff80003473c00) at /usr/src/sys/kern/kern_intr.c:1263 #14 0xffffffff80499266 in ithread_loop (arg=3D0xfffff800034a53e0) at /usr/src/sys/kern/kern_intr.c:1276 #15 0xffffffff80496a3a in fork_exit ( callout=3D0xffffffff804991d0 , arg=3D0xfffff800034a53e0,= =20 frame=3D0xfffffe000023dac0) at /usr/src/sys/kern/kern_fork.c:996 #16 0xffffffff807251ee in fork_trampoline () at /usr/src/sys/amd64/amd64/exception.S:606 #17 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb)=20 =2D ---[ quotation end ]------------------------------------------- #> uname -a FreeBSD 10.1-RELEASE-p14 #4 r285499M amd64 #> dmesg ... FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Xeon(R) CPU E3-1220 v3 @ 3.10GHz (3100.06-MHz K8-class CPU) ... real memory =3D 8589934592 (8192 MB) avail memory =3D 8245338112 (7863 MB) ... pcib4: irq 18 at device 28.2 on pci0 pci4: on pcib4 igb0: port 0xd000-0x= d01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 o= n pci4 igb0: Using MSIX interrupts with 5 vectors igb0: Ethernet address: 00:11:22:33:44:51 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: Bound queue 2 to cpu 2 igb0: Bound queue 3 to cpu 3 pcib5: irq 19 at device 28.3 on pci0 pci5: on pcib5 igb1: port 0xc000-0x= c01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 o= n pci5 igb1: Using MSIX interrupts with 5 vectors igb1: Ethernet address: 00:11:22:33:44:52 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb1: Bound queue 2 to cpu 2 igb1: Bound queue 3 to cpu 3 pcib6: irq 18 at device 28.6 on pci0 pci6: on pcib6 igb2: port 0xb000-0x= b01f mem 0xf7200000-0xf727ffff,0xf7280000-0xf7283fff irq 18 at device 0.0 o= n pci6 igb2: Using MSIX interrupts with 5 vectors igb2: Ethernet address: 00:11:22:33:44:53 igb2: Bound queue 0 to cpu 0 igb2: Bound queue 1 to cpu 1 igb2: Bound queue 2 to cpu 2 igb2: Bound queue 3 to cpu 3 pcib7: irq 19 at device 28.7 on pci0 pci7: on pcib7 igb3: port 0xa000-0x= a01f mem 0xf7100000-0xf717ffff,0xf7180000-0xf7183fff irq 19 at device 0.0 o= n pci7 igb3: Using MSIX interrupts with 5 vectors igb3: Ethernet address: 00:11:22:33:44:54 igb3: Bound queue 0 to cpu 0 igb3: Bound queue 1 to cpu 1 igb3: Bound queue 2 to cpu 2 igb3: Bound queue 3 to cpu 3 ... #> dmidecode ... System Information Manufacturer: Supermicro Product Name: X10SLM+-LN4F ... #> pciconf -lv ... igb0@pci0:4:0:0: class=3D0x020000 card=3D0x153315d9 chip=3D0x1533808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I210 Gigabit Network Connection' class =3D network subclass =3D ethernet igb1@pci0:5:0:0: class=3D0x020000 card=3D0x153315d9 chip=3D0x1533808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I210 Gigabit Network Connection' class =3D network subclass =3D ethernet igb2@pci0:6:0:0: class=3D0x020000 card=3D0x153315d9 chip=3D0x1533808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I210 Gigabit Network Connection' class =3D network subclass =3D ethernet igb3@pci0:7:0:0: class=3D0x020000 card=3D0x153315d9 chip=3D0x1533808= 6 rev=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'I210 Gigabit Network Connection' class =3D network subclass =3D ethernet ... =2D --=20 Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET) =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlWvdkEACgkQr3jpPg/3oyraCwCg8OZFNErBWJXmjSHLm+Qm8ruL IdcAoLG5kxdQpRjv1lPGN3UO27vFY7+H =3DahV7 =2D----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Wed Jul 22 11:58:15 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DCAF99A8484 for ; Wed, 22 Jul 2015 11:58:15 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id 3A1B02C0B for ; Wed, 22 Jul 2015 11:58:15 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 46A75929B051 for ; Wed, 22 Jul 2015 13:57:28 +0200 (CEST) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id zopI74thFlo4 for ; Wed, 22 Jul 2015 13:57:26 +0200 (CEST) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 35B38929B037 for ; Wed, 22 Jul 2015 13:57:26 +0200 (CEST) Received: by beast.freibergnet.de (Postfix, from userid 201) id 323E64B783C; Wed, 22 Jul 2015 13:57:26 +0200 (CEST) Date: Wed, 22 Jul 2015 13:57:26 +0200 From: Holm Tiffe To: freebsd-stable@freebsd.org Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150722115726.GA31634@beast.freibergnet.de> Mail-Followup-To: Holm Tiffe , freebsd-stable@freebsd.org References: <20150722071018.GA8363@beast.freibergnet.de> <55AF54C1.8050002@multiplay.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55AF54C1.8050002@multiplay.co.uk> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 11:58:16 -0000 ..uh top quoting.. Trying to mount root from zfs:zroot/ROOT/default []. Fatal double fault: eip = 0xc0b416f5 esp = 0xe2673000 ebp = 0xe2673008 cpuid =0; apic id = 00 panic: double fault cpuid = 0 KDB stack backtrace: #0 0xc0b72832 at kdb_backtrace+0x52 #1 0xc0b339cb at vpanic+0x11b #2 0xc0b338ab at panic+0x1b #3 0xc10556 at dblfault_handler+0xab Uptime: 11s .. Don't know if I've blowing the stack, nor I have currently the capabilities to build an 10.2-Beta install disk with an custom kernel. I've simply tried to install freebsd on old (trusty) hardware to do some things.. In the meantime I've tested to install on the single disks with a plain ufs in the existing gpart partitions (da?p3) und using the swapspace (da?p2). That where 4 flawless installations, all 4 installed w/o any stall and where bootable, so the hardware is ok. Next try is gmirror on 2 gpart disks. I think gvinum is broken with gpart partitions for since at least 9.3 on i386. Regards, Holm Steven Hartland wrote: > What's the panic? > > As your using ZFS I'd lay money on the fact your blowing the stack, > which would require kernel built with: > options KSTACK_PAGES=4 > > Regards > Steve > > On 22/07/2015 08:10, Holm Tiffe wrote: > >Hi, > > > >yesterday I've decided to to put my old "Workstation" in my shack and > >to install a new FreeBSD on it, it is the computer I've used previously > >for my daily work, reading Mails, programming controllers and so on.. > > > >It is am AMD XP300+ with an Adaptec 29320 and four IBM 72GB SCSI3 Disks > >with only 2GB of Memory. > > > >I've replaced a bad disk, reformated it so 512 Byte sectors )they came > >original with 534 or so for ecc),pulled the 10.2-Beta disk1 ISO file from > >the german mirror and tried to install on a zfs raidz1 which was going > >flawlessly until the point of booting the installed system, some warnings > >about zfs and vm... double fault, panic. > > > >Later I've read on the net that installing zfs on a 32Bit machine isn't > >really a good idea, so I tried to install the system on a gvinum raid > >on gpt partitions. > >The layout was gpt-boot, 2G swap and the rest raid on every disk so > >that I could build a striped 8G swap and ~190G raid with gvinum. > >Installing that worked flawlessly with the install point "shell and doing > >partitioning per hand". I've made a newfs -U -L root /dev/gvinum/raid, > >mounted the filesystem to /mnt, activated the swap and put an fstab in > >/tmp/bsdsomething-etc, exited to install. > > > >The installer verified the install containers (base.txz,kernel.txz and > >so on) and begun to extract them. > >So far soo good, but while extracting the system repeatedly hung on the > >very same location. On vt4 I could start a top that was showing an hung > >bsdtar process in the state wdrain and nothing other happened, the system > >took a long time to react to keypresses.. > > > >I've tried to extract the distribution files per hand, same problem, tar > >hung on extracting kernel.symbols for example, same behavior on other files > >in base.txz. > > > >Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, > >ok tried 9.3-RELEASE .. the same! > > > >What I'm doning wrong here? > > > >Besides of the bad disk that I've changed (IBM-SSG S53D073 C61F) the > >hardware is very trusty, it is a gigabyte board and I want to keep this > >machine since it has still floppy capabilites that I need to comunicate > >with my old CP/M gear and PDP11's. It run for years w/o problems. > >Capacitors are already changed and ok. > > > >Sorry for the wishy-washy error messages above, they are from my memory and > >from yesterday... > > > >Next try was installing the System on a 8G ATA disk that was laying around, > >went flawlessly, booted it and tried to install the files on the gvinum > >raid from there...same problem. > >Changed the 29320 against a 29160 ..same problem. > >No messages about bad disksor something on the console. > > > >What's going on here? The machine run on 8.4-stable before w/o any > >problems. > > > >Regards, > > > >Holm > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, info@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Wed Jul 22 12:31:34 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A59029A8F59 for ; Wed, 22 Jul 2015 12:31:34 +0000 (UTC) (envelope-from herbert@oslo.ath.cx) Received: from oslo.ath.cx (oslo.ath.cx [IPv6:2a01:4f8:200:42e4::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6C28011A2 for ; Wed, 22 Jul 2015 12:31:34 +0000 (UTC) (envelope-from herbert@oslo.ath.cx) Received: from oslo.ath.cx (localhost [IPv6:::1]) by oslo.ath.cx (Postfix) with SMTP id 3566917C6; Wed, 22 Jul 2015 14:31:32 +0200 (CEST) Date: Wed, 22 Jul 2015 14:31:32 +0200 From: "Herbert J. Skuhra" To: Holm Tiffe , freebsd-stable@freebsd.org Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150722123132.GA83696@oslo.ath.cx> References: <20150722071018.GA8363@beast.freibergnet.de> <55AF54C1.8050002@multiplay.co.uk> <20150722115726.GA31634@beast.freibergnet.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150722115726.GA31634@beast.freibergnet.de> User-Agent: Mutt/1.5.23+100 (79cd2f34961d) (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 12:31:34 -0000 On Wed, Jul 22, 2015 at 01:57:26PM +0200, Holm Tiffe wrote: > ..uh top quoting.. > > Trying to mount root from zfs:zroot/ROOT/default []. > > Fatal double fault: > eip = 0xc0b416f5 > esp = 0xe2673000 > ebp = 0xe2673008 > cpuid =0; apic id = 00 > panic: double fault > cpuid = 0 > KDB stack backtrace: > #0 0xc0b72832 at kdb_backtrace+0x52 > #1 0xc0b339cb at vpanic+0x11b > #2 0xc0b338ab at panic+0x1b > #3 0xc10556 at dblfault_handler+0xab > Uptime: 11s > .. Looks like the panic I received on my Soekris Net6501-70. Fixed in stable/10 in r285759: https://svnweb.freebsd.org/changeset/base/285759 Fixed in stable/9 in r285760: https://svnweb.freebsd.org/changeset/base/285760 -- Herbert From owner-freebsd-stable@freebsd.org Wed Jul 22 13:33:24 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 261109A6E12 for ; Wed, 22 Jul 2015 13:33:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D3F8E15E7 for ; Wed, 22 Jul 2015 13:33:23 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZHu91-000Bf7-6Q for freebsd-stable@freebsd.org; Wed, 22 Jul 2015 16:33:11 +0300 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Dell r730 + PERC H730P problem Message-Id: Date: Wed, 22 Jul 2015 16:33:11 +0300 To: FreeBSD stable Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 13:33:24 -0000 Hi I=E2=80=99m running a pretty new 10.2-BETA, on a freshly arrived box, and trying it out. after creating a raid5 via mfiutil, and=20 trying to restore(8) to it gives: ... Jul 22 15:48:30 store-07 kernel: mfi0: Failed to get command Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013a6440 = TIMEOUT AFTER 37 SECONDS Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013aa158 = TIMEOUT AFTER 37 SECONDS Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013a6000 = TIMEOUT AFTER 37 SECONDS =E2=80=A6 and only power cycle worked. We have several Dell/Percs with similar configuration working fine = (though the PERCs are older), this is Perc H730P Mini. From owner-freebsd-stable@freebsd.org Wed Jul 22 16:11:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C3139A7033 for ; Wed, 22 Jul 2015 16:11:16 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com [209.85.160.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5588A1259 for ; Wed, 22 Jul 2015 16:11:15 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by ykfw194 with SMTP id w194so116356000ykf.0 for ; Wed, 22 Jul 2015 09:11:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=9IKg3dtQ+pmCbHPcZmfBSLhwULztb8We6W0FdeQxRAA=; b=XjHfms1BidZA8wc9tpJ71CsNGMF9GbunDuwnNDuTmM/oR5177PrX6MuCmfYqOB+QOP gCecMy1SARIBXnwmgB9ws4AdTt9k4iictJqRMcsEbdFqHtK302TRJbkr94H9hEYQ9dcM HyIH9LeNbiVXM4c0T4fowauUeU5WcUqL+b47Am6jzcuexLPPFoviQq66FeYbkeJPx+ES 3JmfB7G17MEzqoewbVC97W0muLwoWMuTrfAb3UVTAvN3olvCEr8xefgc4LVrB/Q3BxQU CHND8niZFTYL/GGQXWYZ0QVegoxWqQgJhM4VI6zqSL4uzjFaqp4csRl7Hvg+f9YnGVUP zOUQ== X-Gm-Message-State: ALoCoQlvSeL50bjO2F7hJQ9zh6CmFXJAl+vSnEpRYotXmfOOL8hIGYRyXor1Qy2XaceDSIV/4v7a MIME-Version: 1.0 X-Received: by 10.170.48.134 with SMTP id 128mr3249870ykq.36.1437581469507; Wed, 22 Jul 2015 09:11:09 -0700 (PDT) Received: by 10.129.138.68 with HTTP; Wed, 22 Jul 2015 09:11:09 -0700 (PDT) X-Originating-IP: [38.104.68.66] Date: Wed, 22 Jul 2015 12:11:09 -0400 Message-ID: Subject: Interesting Boot failure on HEAD with a large number of IGB nics From: Mark Saad To: "freebsd-hackers@freebsd.org" , FreeBSD-Stable ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 16:11:16 -0000 All I am wondering if anyone has run into this issue before , and if there is a fix. I have a Scalable Informatics siRouter with 24 Intel I350 igb nics and 8 intel 82599ES ixgbe/ix nic . The SiRouter is a Supermicro X9DRX+-F with a bunch of intel nics. On Head I run into a boot panic out of the box while plumbing the usb controller . The box crashes with ehci0: mem 0xdd923000-0xdd9233ff irq 16 at device 26.0 on pci0 panic: Couldn't find an APIC vector for IRQ 16 However it has only probed 8 of the 24 igb when is crashes. Here is the complete boot up with some additional info. http://pastebin.com/MfbEwwg4 Now the interesting thing. DragonFly 4.2x boots fine see the dmesg here http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2778 OpenBSD boots and finds the nics as well see dmesg here http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2777 NetBSD Pukes while probing something out of the box and I cant get the serial console to work. Linux 2.6 CentOS 6.6 works OmniOS / Illumos-gate and Illumos-joyent work out of the box So my goal here is to make the box boot FreeBSD . It had been used prior running OmniOS and CentOS and well now I want to make it work. :) Any ideas here ? mark saad | nonesuch@longcount.org From owner-freebsd-stable@freebsd.org Wed Jul 22 17:00:09 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE65E9A7B3D for ; Wed, 22 Jul 2015 17:00:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA02B14AB for ; Wed, 22 Jul 2015 17:00:09 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (75-48-78-19.lightspeed.cncrca.sbcglobal.net [75.48.78.19]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id D3498B9BA; Wed, 22 Jul 2015 13:00:08 -0400 (EDT) From: John Baldwin To: Kevin Oberman Cc: Joseph Mingrone , "Brandon J. Wandersee" , Adrian Chadd , FreeBSD-STABLE Mailing List Subject: Re: suspend/resume regression Date: Tue, 21 Jul 2015 15:56:48 -0700 Message-ID: <12509399.h3RdpFfE1l@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.1-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <86oak289hv.fsf@gly.ftfl.ca> <86oaj9dnbo.fsf@gly.ftfl.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 22 Jul 2015 13:00:08 -0400 (EDT) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 17:00:10 -0000 On Saturday, July 18, 2015 10:22:33 PM Kevin Oberman wrote: > I just confirmed that my system resumes on HEAD of July 16 but fails on > 10.2-BETA2. So the problem limited to 10. I'm guessing that some other > change made to pci that has not been MFCed is the cause, but it is only > causing a problem on some hardware. I have seen no reports about systems > other than Lenovo systems. So my x220 does fail with a USB disk on 10, but I also get a weird behavior where it seems to wake up (disk lights up) and then goes back to sleep and never resumes again. I'm not sure if this is due to using a USB disk or not. I get the same result when I disable power management during suspend which was reported to fix other laptops IIRC. Please try this: Index: sys/dev/acpica/acpi.c =================================================================== --- sys/dev/acpica/acpi.c (revision 285761) +++ sys/dev/acpica/acpi.c (working copy) @@ -691,7 +691,7 @@ static void acpi_set_power_children(device_t dev, int state) { - device_t child, parent; + device_t child; device_t *devlist; struct pci_devinfo *dinfo; int dstate, i, numdevs; @@ -703,13 +703,12 @@ * Retrieve and set D-state for the sleep state if _SxD is present. * Skip children who aren't attached since they are handled separately. */ - parent = device_get_parent(dev); for (i = 0; i < numdevs; i++) { child = devlist[i]; dinfo = device_get_ivars(child); dstate = state; if (device_is_attached(child) && - acpi_device_pwr_for_sleep(parent, dev, &dstate) == 0) + acpi_device_pwr_for_sleep(dev, child, &dstate) == 0) acpi_set_powerstate(child, dstate); } free(devlist, M_TEMP); Index: sys/dev/pci/pci.c =================================================================== --- sys/dev/pci/pci.c (revision 285761) +++ sys/dev/pci/pci.c (working copy) @@ -3671,7 +3671,7 @@ child = devlist[i]; dstate = state; if (device_is_attached(child) && - PCIB_POWER_FOR_SLEEP(pcib, dev, &dstate) == 0) + PCIB_POWER_FOR_SLEEP(pcib, child, &dstate) == 0) pci_set_powerstate(child, dstate); } } Index: . =================================================================== --- . (revision 285761) +++ . (working copy) Property changes on: . ___________________________________________________________________ Modified: svn:mergeinfo Merged /head:r274386,274397 -- John Baldwin From owner-freebsd-stable@freebsd.org Wed Jul 22 17:14:22 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A48829A7E96; Wed, 22 Jul 2015 17:14:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6BC9C1DA3; Wed, 22 Jul 2015 17:14:22 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZHxb1-000OnG-Bw; Wed, 22 Jul 2015 18:14:19 +0100 Date: Wed, 22 Jul 2015 18:14:19 +0100 From: Gary Palmer To: Mark Saad Cc: "freebsd-hackers@freebsd.org" , FreeBSD-Stable ML Subject: Re: Interesting Boot failure on HEAD with a large number of IGB nics Message-ID: <20150722171419.GE41419@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 17:14:22 -0000 On Wed, Jul 22, 2015 at 12:11:09PM -0400, Mark Saad wrote: > All > I am wondering if anyone has run into this issue before , and if there is > a fix. > I have a Scalable Informatics siRouter with 24 Intel I350 igb nics and 8 > intel 82599ES ixgbe/ix nic . The SiRouter is a Supermicro X9DRX+-F with a > bunch of intel nics. > > On Head I run into a boot panic out of the box while plumbing the usb > controller . The box crashes with > > ehci0: mem 0xdd923000-0xdd9233ff irq 16 > at device 26.0 on pci0 > panic: Couldn't find an APIC vector for IRQ 16 > > However it has only probed 8 of the 24 igb when is crashes. Here is the > complete boot up with some additional info. > > http://pastebin.com/MfbEwwg4 > > Now the interesting thing. > > DragonFly 4.2x boots fine see the dmesg here > http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2778 > > OpenBSD boots and finds the nics as well see dmesg here > http://dmesgd.nycbug.org/index.cgi?action=dmesgd&do=view&id=2777 > > NetBSD Pukes while probing something out of the box and I cant get the > serial console to work. > > Linux 2.6 CentOS 6.6 works > > OmniOS / Illumos-gate and Illumos-joyent work out of the box > > > > So my goal here is to make the box boot FreeBSD . It had been used prior > running OmniOS and CentOS and well now I want to make it work. :) > > Any ideas here ? I'm no expert, but you may want to try setting hw.igb.num_queues=1 and maybe hw.ixgbe.num_queues=1 in the boot loader and trying that. Regards, Gary P.S. freebsd-net@ may be a better list than either -stable or -hackers. From owner-freebsd-stable@freebsd.org Wed Jul 22 17:54:13 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 906179A85A3; Wed, 22 Jul 2015 17:54:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 62A05107F; Wed, 22 Jul 2015 17:54:13 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by pabkd10 with SMTP id kd10so69975693pab.2; Wed, 22 Jul 2015 10:54:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R3E5tXV0GWyBLg7axpLOcC3sBApB8Wzz9n1+pg16Ag4=; b=dLNz/4Eh5op6cVyVHeR47XJUxKiO+Q0qkcKf0PKWHvtWOQnLabamGqnb6nSvOeHUlU cyvd8VGFdQkcFO6FEWJjQs97EO7DKXdEmIISH+UuBvfnKZf8GNeEd1TGhvLF0HXtoqge gMIdsoJrynSQZzuOW/OzXpNtGNQjoMPY46y90UE+vW7aWHOkGqm7hTzpJTs+EVzvM44N YaAISmuqdSEB8uY5T2h8gFkNJyW05qZeNo9KWUMMFg/ghHFLYxRAXMs8L9nEGe36f1Ak YeT6L/U4PDLtnwHI2wu4bCcnIchUVL6STOSmcGTMy2GhRlMNKpmY+in/B2CeT/3fhEdT fYxw== X-Received: by 10.66.66.40 with SMTP id c8mr8411791pat.117.1437587652867; Wed, 22 Jul 2015 10:54:12 -0700 (PDT) Received: from [33.169.126.251] ([172.56.33.170]) by smtp.gmail.com with ESMTPSA id rh11sm4482006pdb.22.2015.07.22.10.54.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 22 Jul 2015 10:54:12 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Interesting Boot failure on HEAD with a large number of IGB nics From: Garrett Cooper X-Mailer: iPhone Mail (12H143) In-Reply-To: <20150722171419.GE41419@in-addr.com> Date: Wed, 22 Jul 2015 10:54:10 -0700 Cc: Mark Saad , "freebsd-hackers@freebsd.org" , FreeBSD-Stable ML Content-Transfer-Encoding: quoted-printable Message-Id: <95653312-0F92-40E4-89EE-E8235403D3B9@gmail.com> References: <20150722171419.GE41419@in-addr.com> To: Gary Palmer X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 17:54:13 -0000 > On Jul 22, 2015, at 10:14, Gary Palmer wrote: ... > I'm no expert, but you may want to try setting >=20 > hw.igb.num_queues=3D1 >=20 > and maybe >=20 > hw.ixgbe.num_queues=3D1 >=20 > in the boot loader and trying that. There was another discussion that took place around June on current that mig= ht be helpful. I think the solution boiled down to what Gary described above= , because the driver auto tuning was broken... Thanks! -NGie= From owner-freebsd-stable@freebsd.org Wed Jul 22 18:26:37 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 881699A8C89 for ; Wed, 22 Jul 2015 18:26:37 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-yk0-f181.google.com (mail-yk0-f181.google.com [209.85.160.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F2CE1236 for ; Wed, 22 Jul 2015 18:26:36 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by ykax123 with SMTP id x123so200308058yka.1 for ; Wed, 22 Jul 2015 11:26:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=5zYNWm6b7jUYpA3Hl1oIc7eBU5ssjbVltsxKD/bPrls=; b=CAHv4m066jhOm0xUjTfIZ3oqENO9X0s3VWgMnPVPJbayUxQsOv6nvjPOD3c/Nqz7x6 ZBmsmGTF4EkSsKcSgowQ1QPGiaP1F+sQ1CfKCrIIeP6yY0BEb1g3oDAffSN3iRL9uX79 A327KevZhMVxHaN0m0+1whsSogp4JOU6NQklJOs27Laoi2jFZERNNI6BVR7qqyNuOIBv g/VFH+Xqzr8YxUdkfOjpTnv0elKplIgRkFFe1qC72iMGpnT6pzacF01r5e0qxEM+noJs LYZeXUcW4ai/5ZUKjiHbsBKdu5AHqVGKrXoS01mavgiD7ab8XU/j8rkL4GGItKWNbALI Ubng== X-Gm-Message-State: ALoCoQmOEEqtueQsDynVT2B1w0jEEuqPT0Vumh62D4ZKzKCbSy1GTNqQRVjDogtC1Y+BdQeD6Gta MIME-Version: 1.0 X-Received: by 10.170.206.139 with SMTP id x133mr3897901yke.126.1437589206763; Wed, 22 Jul 2015 11:20:06 -0700 (PDT) Received: by 10.129.138.68 with HTTP; Wed, 22 Jul 2015 11:20:06 -0700 (PDT) X-Originating-IP: [38.104.68.66] In-Reply-To: <95653312-0F92-40E4-89EE-E8235403D3B9@gmail.com> References: <20150722171419.GE41419@in-addr.com> <95653312-0F92-40E4-89EE-E8235403D3B9@gmail.com> Date: Wed, 22 Jul 2015 14:20:06 -0400 Message-ID: Subject: Re: Interesting Boot failure on HEAD with a large number of IGB nics From: Mark Saad To: Garrett Cooper Cc: Gary Palmer , "freebsd-hackers@freebsd.org" , FreeBSD-Stable ML Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 18:26:37 -0000 On Wed, Jul 22, 2015 at 1:54 PM, Garrett Cooper wrote: > > > On Jul 22, 2015, at 10:14, Gary Palmer wrote: > > ... > > > I'm no expert, but you may want to try setting > > > > hw.igb.num_queues=1 > > > > and maybe > > > > hw.ixgbe.num_queues=1 > > > > in the boot loader and trying that. > > There was another discussion that took place around June on current that > might be helpful. I think the solution boiled down to what Gary described > above, because the driver auto tuning was broken... > Thanks! > -NGie NGie I'll try the queues option but; why was does that kill my ehci hub ? Note ehci0: mem 0xdd923000-0xdd9233ff irq 16 at device 26.0 on pci0 panic: Couldn't find an APIC vector for IRQ 16 -- mark saad | nonesuch@longcount.org From owner-freebsd-stable@freebsd.org Wed Jul 22 18:34:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 063F39A8DF6; Wed, 22 Jul 2015 18:34:06 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from mail.in-addr.com (mail.in-addr.com [IPv6:2a01:4f8:191:61e8::2525:2525]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C0BF51889; Wed, 22 Jul 2015 18:34:05 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from gjp by mail.in-addr.com with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZHyqC-000Ow0-1b; Wed, 22 Jul 2015 19:34:04 +0100 Date: Wed, 22 Jul 2015 19:34:04 +0100 From: Gary Palmer To: Mark Saad Cc: Garrett Cooper , "freebsd-hackers@freebsd.org" , FreeBSD-Stable ML Subject: Re: Interesting Boot failure on HEAD with a large number of IGB nics Message-ID: <20150722183404.GF41419@in-addr.com> References: <20150722171419.GE41419@in-addr.com> <95653312-0F92-40E4-89EE-E8235403D3B9@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on mail.in-addr.com); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 18:34:06 -0000 On Wed, Jul 22, 2015 at 02:20:06PM -0400, Mark Saad wrote: > On Wed, Jul 22, 2015 at 1:54 PM, Garrett Cooper > wrote: > > > > > > On Jul 22, 2015, at 10:14, Gary Palmer wrote: > > > > ... > > > > > I'm no expert, but you may want to try setting > > > > > > hw.igb.num_queues=1 > > > > > > and maybe > > > > > > hw.ixgbe.num_queues=1 > > > > > > in the boot loader and trying that. > > > > There was another discussion that took place around June on current that > > might be helpful. I think the solution boiled down to what Gary described > > above, because the driver auto tuning was broken... > > Thanks! > > -NGie > > > NGie > I'll try the queues option but; why was does that kill my ehci hub ? Note > > ehci0: mem 0xdd923000-0xdd9233ff irq 16 > at device 26.0 on pci0 > panic: Couldn't find an APIC vector for IRQ 16 I believe the error message could be better written as "Couldn't find a free APIC vector". The IGB cards allocted multiple MSI-X interrupts for multi-queue use and exhausted the available pool, and the USB hub (ehci0) just happened to be the next thing probed by the PCI bus and tripped the panic. At least that is my understanding. Regards, Gary From owner-freebsd-stable@freebsd.org Wed Jul 22 21:53:47 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A9509A82E1 for ; Wed, 22 Jul 2015 21:53:47 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::81]) by mx1.freebsd.org (Postfix) with ESMTP id 0064B1DA3 for ; Wed, 22 Jul 2015 21:53:46 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [IPv6:2a02:6b8:0:801:1::10]) by forward11.mail.yandex.net (Yandex) with ESMTP id CC2ADE809B2 for ; Thu, 23 Jul 2015 00:53:41 +0300 (MSK) Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id 94CCF7E02B3 for ; Thu, 23 Jul 2015 00:53:41 +0300 (MSK) Received: by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id m2iBZ73R0W-rdDeb14q; Thu, 23 Jul 2015 00:53:39 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437602020; bh=jK/d9PNc2Q6FRXrbkn0CEpp95HeViuIgCJ+Or4EBJh4=; h=Message-ID:Subject:From:To:Date:Content-Type:X-Mailer: Mime-Version:Content-Transfer-Encoding; b=dq19gtndBJ5Tuoi/OySPb5ft/+ieFxm/L9mktWO+ZQ+WrFGfv8nwaQWcuL/7/9vKS O2nCLdi5PhZ4ssO/0KmjH8LgGBibSy/jPPH6LfAq8w9eWnGi7nKA/JEZGUaEnzg4qP ER41jYo/+d9VfqPf5Kutw11/sixwa6kc5awSAugg= Authentication-Results: smtp11.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-ForeignMX: US Message-ID: <1437602017.1621.5.camel@yandex.com> Subject: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: freebsd-stable@freebsd.org Date: Wed, 22 Jul 2015 17:53:37 -0400 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jul 2015 21:53:47 -0000 Hi! I upgrade 10.1-RELEASE (amd64) with freebsd-update upgrade to FreeBSD 10.2-BETA2 #0 r285646: Fri Jul 17 01:09:28 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and now I have some problems: 1. VT module doesn't load. In /boot/loader.conf I have: kern.vty=vt but it doesn't work. If I manual loada module witk kldload radeonkms I got just black screen and nothing more. 2. Fireware external disk doesn't work either. In /boot/loader.conf I have sbp_load="YES" but it doesn't load. If I run kldload sbp it load and works. 3. The same is with web camera. cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. It works if I load with kldload. In /boot/loader.conf I have also loader_logo="beastie" which doesn't show picture in menu (it is default one). In /boot/device.hints I have also some hits which are for my sound card and it doesn't read them and sound doesn't work correct too. On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. Today I update with freebsd-update fetch and the problem exist. Thank you. -- ajtiM ----- http://www.redbubble.com/people/lumiwa https://www.facebook.com/pages/Lumiwa-FARM/775292915882930?_fb_noscript=1 From owner-freebsd-stable@freebsd.org Thu Jul 23 05:43:26 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0D0B29A60F4 for ; Thu, 23 Jul 2015 05:43:26 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AECF6162B for ; Thu, 23 Jul 2015 05:43:24 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZI9Hn-0007cD-5F for freebsd-stable@freebsd.org; Thu, 23 Jul 2015 08:43:15 +0300 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: Dell r730 + PERC H730P problem fixed From: Daniel Braniss In-Reply-To: Date: Thu, 23 Jul 2015 08:43:14 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: FreeBSD stable X-Mailer: Apple Mail (2.2102) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 05:43:26 -0000 set hw.mfi.mrsas_enable=3D1 in loader.conf > On 22 Jul 2015, at 16:33, Daniel Braniss wrote: >=20 > Hi > I=E2=80=99m running a pretty new 10.2-BETA, on a freshly arrived box, > and trying it out. >=20 > after creating a raid5 via mfiutil, and=20 > trying to restore(8) to it gives: > ... > Jul 22 15:48:30 store-07 kernel: mfi0: Failed to get command > Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013a6440 = TIMEOUT AFTER 37 SECONDS > Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013aa158 = TIMEOUT AFTER 37 SECONDS > Jul 22 15:49:24 store-07 kernel: mfi0: COMMAND 0xfffffe00013a6000 = TIMEOUT AFTER 37 SECONDS > =E2=80=A6 >=20 > and only power cycle worked. >=20 > We have several Dell/Percs with similar configuration working fine = (though the PERCs are older), > this is Perc H730P Mini. >=20 >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to = "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Thu Jul 23 05:46:32 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F01C9A61AC for ; Thu, 23 Jul 2015 05:46:32 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7BAC1924; Thu, 23 Jul 2015 05:46:31 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oigd21 with SMTP id d21so116234383oig.1; Wed, 22 Jul 2015 22:46:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=E5ZT2kgUhQwSpiQejdRk2X96eSlL738oNmYzQgTtrJM=; b=dm9ZxSk4cRw85Nh/eAgzKLITW+qGtO++ofYmEXE/kwf2aeb0tU3ok/anF14UPUru55 qmTglPTVlvfFpB8zvbWJn7l+81Wx5xZ81nMDKxmAUb4XHbSgeZvs9333kIy6ZJcFbqTb 3N3ofYfdzPu9tS0zi5+5YfhlukaR45FyO5pOPP6pEwKWLhMNVeOgvPGE48bQIGtbKbCK HmulgKULAi6Kc855bi8Y6/wF7DeNWgUBNk+cxXR4Z1AA45u8Vypr6+UQd+Ol7NJr69FJ 1RMA9GQX5mE+c6r/t9ODdKrrfWPIpfzrY5lC9/mYNQ3KEF2k+Fx4ypZ2zT4VLY9+QmnN 8rZQ== MIME-Version: 1.0 X-Received: by 10.202.188.2 with SMTP id m2mr4839956oif.59.1437630391280; Wed, 22 Jul 2015 22:46:31 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Wed, 22 Jul 2015 22:46:31 -0700 (PDT) In-Reply-To: <12509399.h3RdpFfE1l@ralph.baldwin.cx> References: <86oak289hv.fsf@gly.ftfl.ca> <86oaj9dnbo.fsf@gly.ftfl.ca> <12509399.h3RdpFfE1l@ralph.baldwin.cx> Date: Wed, 22 Jul 2015 22:46:31 -0700 X-Google-Sender-Auth: VJtjJesduwLjk1YIoGgjFc4i1UE Message-ID: Subject: Re: suspend/resume regression From: Kevin Oberman To: John Baldwin Cc: Joseph Mingrone , "Brandon J. Wandersee" , Adrian Chadd , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 05:46:32 -0000 On Tue, Jul 21, 2015 at 3:56 PM, John Baldwin wrote: > On Saturday, July 18, 2015 10:22:33 PM Kevin Oberman wrote: > > I just confirmed that my system resumes on HEAD of July 16 but fails on > > 10.2-BETA2. So the problem limited to 10. I'm guessing that some other > > change made to pci that has not been MFCed is the cause, but it is only > > causing a problem on some hardware. I have seen no reports about systems > > other than Lenovo systems. > > So my x220 does fail with a USB disk on 10, but I also get a weird behavior > where it seems to wake up (disk lights up) and then goes back to sleep and > never resumes again. I'm not sure if this is due to using a USB disk or > not. I get the same result when I disable power management during suspend > which was reported to fix other laptops IIRC. > > Please try this: > > Index: sys/dev/acpica/acpi.c > =================================================================== > --- sys/dev/acpica/acpi.c (revision 285761) > +++ sys/dev/acpica/acpi.c (working copy) > @@ -691,7 +691,7 @@ > static void > acpi_set_power_children(device_t dev, int state) > { > - device_t child, parent; > + device_t child; > device_t *devlist; > struct pci_devinfo *dinfo; > int dstate, i, numdevs; > @@ -703,13 +703,12 @@ > * Retrieve and set D-state for the sleep state if _SxD is present. > * Skip children who aren't attached since they are handled > separately. > */ > - parent = device_get_parent(dev); > for (i = 0; i < numdevs; i++) { > child = devlist[i]; > dinfo = device_get_ivars(child); > dstate = state; > if (device_is_attached(child) && > - acpi_device_pwr_for_sleep(parent, dev, &dstate) == 0) > + acpi_device_pwr_for_sleep(dev, child, &dstate) == 0) > acpi_set_powerstate(child, dstate); > } > free(devlist, M_TEMP); > Index: sys/dev/pci/pci.c > =================================================================== > --- sys/dev/pci/pci.c (revision 285761) > +++ sys/dev/pci/pci.c (working copy) > @@ -3671,7 +3671,7 @@ > child = devlist[i]; > dstate = state; > if (device_is_attached(child) && > - PCIB_POWER_FOR_SLEEP(pcib, dev, &dstate) == 0) > + PCIB_POWER_FOR_SLEEP(pcib, child, &dstate) == 0) > pci_set_powerstate(child, dstate); > } > } > Index: . > =================================================================== > --- . (revision 285761) > +++ . (working copy) > > Property changes on: . > ___________________________________________________________________ > Modified: svn:mergeinfo > Merged /head:r274386,274397 > > > -- > John Baldwin > Tried both sysctls and the patch. Nothing worked. Ticket updated with the information. -- Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-stable@freebsd.org Thu Jul 23 11:06:14 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 870939A811D for ; Thu, 23 Jul 2015 11:06:14 +0000 (UTC) (envelope-from romanc0y__lecfarm_com__gb@sandu.beget.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6BBD51DEF for ; Thu, 23 Jul 2015 11:06:14 +0000 (UTC) (envelope-from romanc0y__lecfarm_com__gb@sandu.beget.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 6AACD9A811C; Thu, 23 Jul 2015 11:06:14 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 507D09A811B for ; Thu, 23 Jul 2015 11:06:14 +0000 (UTC) (envelope-from romanc0y__lecfarm_com__gb@sandu.beget.ru) Received: from m2.sandu.beget.ru (m2.sandu.beget.ru [5.101.153.32]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 150AD1DEE for ; Thu, 23 Jul 2015 11:06:13 +0000 (UTC) (envelope-from romanc0y__lecfarm_com__gb@sandu.beget.ru) Received: from romanc0y (Authenticated sender romanc0y@sandu.beget.ru) by sandu.beget.ru with local (Exim 4.76) (envelope-from ) id 1ZIEKH-0005cD-PY for stable@freebsd.org; Thu, 23 Jul 2015 14:06:09 +0300 To: stable@freebsd.org Subject: Notice to appear in Court #00000722129 Date: Thu, 23 Jul 2015 14:06:09 +0300 From: "County Court" Reply-To: "County Court" Message-ID: <438e16f7824f8b0f94303fbf39d3270b@m2.sandu.beget.ru> X-Priority: 3 MIME-Version: 1.0 Precedence: bulk Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 11:06:14 -0000 Notice to Appear, You have to appear in the Court on the July 29. Please, prepare all the documents relating to the case and bring them to Court on the specified date. Note: If you do not come, the case will be heard in your absence. You can find the Court Notice is in the attachment. Yours faithfully, Joseph Mckenna, Clerk of Court. From owner-freebsd-stable@freebsd.org Thu Jul 23 13:43:19 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F31DE9A7D0D for ; Thu, 23 Jul 2015 13:43:19 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward19j.cmail.yandex.net (forward19j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::f6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACCB11B32 for ; Thu, 23 Jul 2015 13:43:19 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web16j.yandex.ru (web16j.yandex.ru [IPv6:2a02:6b8:0:1619::316]) by forward19j.cmail.yandex.net (Yandex) with ESMTP id 949ED2188E for ; Thu, 23 Jul 2015 16:43:16 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web16j.yandex.ru (Yandex) with ESMTP id 31E273FC0049; Thu, 23 Jul 2015 16:43:16 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437658996; bh=fvqsDJpjvOfGdZfWjo6EY73xaClmhAM0B9E7wTxWSlI=; h=From:To:Subject:Date; b=XTBPesZB5iTVIm/xBG6UBZ6nGOOSY3HGDFAblbkLs/mde6W53ANYwhwG+spRPCXKI jZP4jTcVMXiUflhqDwZx5r+bxYjndjvYarGlTq1vWC5Metz8zy7XFhtEMBZI0vXUbA Q6+n0mDxfjMNbT+0PQdVkYOXfiyIqedjivCeDItg= Received: by web16j.yandex.ru with HTTP; Thu, 23 Jul 2015 16:43:15 +0300 From: deco33000@yandex.com To: freebsd-stable@freebsd.org Subject: struct timehands: th_generation field MIME-Version: 1.0 Message-Id: <464641437658995@web16j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 23 Jul 2015 15:43:15 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 13:43:20 -0000 Hi, Currently I read more about timers and clock. I am struggling on one field of a struct : http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L63 I would like to understand what th_generation means please. Thanks a lot --š Jog From owner-freebsd-stable@freebsd.org Thu Jul 23 13:51:52 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 794FA9A7EB6 for ; Thu, 23 Jul 2015 13:51:52 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 21D411EBF for ; Thu, 23 Jul 2015 13:51:52 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wibxm9 with SMTP id xm9so209525386wib.0 for ; Thu, 23 Jul 2015 06:51:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=o7lbawWbJEztWx0GWP0h27l56gw2cxBNIQ6Vjt5EYK4=; b=S0B9vFQt6hCjYkrmKXRqssSR4J63AJKh/a4eF2OazxULdQIQNBxOoZZAQa1iaT4jik rngSgnI1NmfhN4wf1tYIguSWs7TOClCr93XUogo5N8qED/4oNBpVf4jFw9FNF7Xi5KIJ GjStdZzHg/t/m+DdnrTPTLZUYMI1gSqFPsdTbxHvZ4ojaTttXV1IwotRoaDwUrzX/bx1 aRu48Rgy7pzfty0MOrtejahtENeVQJp+FOfrbR24xOAEO6DQj1UhRzHm/Ep4hnscoWU0 qqXd+/A5VMLMnVVOa4tiK9Z5WZjzvhurHWrgXk07mlFSiMgYKKxEJBH7x0hSe6l+GKF0 NnQg== MIME-Version: 1.0 X-Received: by 10.180.94.7 with SMTP id cy7mr16296975wib.79.1437659510497; Thu, 23 Jul 2015 06:51:50 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Thu, 23 Jul 2015 06:51:50 -0700 (PDT) In-Reply-To: <464641437658995@web16j.yandex.ru> References: <464641437658995@web16j.yandex.ru> Date: Thu, 23 Jul 2015 09:51:50 -0400 Message-ID: Subject: Re: struct timehands: th_generation field From: Brandon Allbery To: deco33000@yandex.com Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 13:51:52 -0000 On Thu, Jul 23, 2015 at 9:43 AM, wrote: > I am struggling on one field of a struct : > http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L63 > I would like to understand what th_generation means please. > Seems to me you get a clue from: ( http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L192) */*** * Functions for reading the time. We have to loop until we are sure that** * the timehands that we operated on was not updated under our feet. See** * the comment in for a description of these 12 functions.** */* > > #ifdef FFCLOCK > voidfbclock_binuptime (struct bintime *bt ) > { > struct timehands *th; > unsigned int gen ; > > do { > th = timehands ; > gen = th->th_generation; > *bt = th->th_offset; > bintime_addx (bt , th->th_scale * tc_delta (th)); > } while (gen == 0 || gen != th->th_generation); > } > > -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Thu Jul 23 14:38:42 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B459A9A962C for ; Thu, 23 Jul 2015 14:38:42 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward12p.cmail.yandex.net (forward12p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::ba]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C3DF194C for ; Thu, 23 Jul 2015 14:38:42 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web29g.yandex.ru (web29g.yandex.ru [95.108.253.238]) by forward12p.cmail.yandex.net (Yandex) with ESMTP id 741D721E9E; Thu, 23 Jul 2015 17:38:29 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web29g.yandex.ru (Yandex) with ESMTP id ED5052480037; Thu, 23 Jul 2015 17:38:28 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437662309; bh=CsqGSxHkSsGTyGEPn9cK3lz+LjEc5pbgIKoZazerz0Y=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=s08xRyWkWh3ZWS79hyC+Yz1vzuqWqAvXoqwTQcyWRV23IAHXYX7m5NwPhbNAI+gLZ 4Ati+PwApeaNnzHeqIeV93Zdh04++GtQ6ME4OJSbelNOZeRw4eaiVh8lWpc32gufGW Vr8TiF8JaA0/ib0/t83WjR4FpYoBSsGu+xqedJCk= Received: by web29g.yandex.ru with HTTP; Thu, 23 Jul 2015 17:38:28 +0300 From: deco33000@yandex.com To: Brandon Allbery Cc: freebsd-stable In-Reply-To: References: <464641437658995@web16j.yandex.ru> Subject: Re: struct timehands: th_generation field Message-Id: <190031437662308@web29g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 23 Jul 2015 16:38:28 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 14:38:42 -0000 From owner-freebsd-stable@freebsd.org Thu Jul 23 14:43:59 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 00C609A97B0 for ; Thu, 23 Jul 2015 14:43:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E019F1D8E; Thu, 23 Jul 2015 14:43:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 7FE4D1582; Thu, 23 Jul 2015 14:43:58 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Thu, 23 Jul 2015 14:43:56 +0000 From: Glen Barber To: freebsd-stable@FreeBSD.org Subject: Heads-up: Change to 10.2-RELEASE schedule Message-ID: <20150723144356.GX9535@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="0ywUhQCikZ2Y3PNw" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 14:43:59 -0000 --0ywUhQCikZ2Y3PNw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline At this time, re@ feels it is not necessary to have 10.2-BETA3 as part of the release cycle, so the next 10.2 builds (planned to start in just under 9 hours) will be 10.2-RC1. The 10.2-RELEASE schedule has been updated on the FreeBSD.org website to reflect this change, and is also included in this email. https://www.FreeBSD.org/releases/10.2R/schedule.html releng/10.2 branch: July 24, 2015 RC1 build starts: July 24, 2015 stable/10 thaw: July 26, 2015 ports package builds: July 27, 2015 RC2 build starts: July 31, 2015 RC3 build starts: August 7, 2015 [*] RELEASE build starts: August 21, 2015 RELEASE announcement: August 31, 2015 [*] - If needed Note, the final 10.2-RELEASE build and announcement dates have been unchanged to account for any delays for the remainder of the release cycle. These dates will be updated as necessary as the release cycle progresses. Thank you. Glen On behalf of: re@ --0ywUhQCikZ2Y3PNw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsP2sAAoJEAMUWKVHj+KTl3MQAIJSGqB6qbunJpDTtXKTSxfB FOuT8FbWomTqe9WsHbRK3TNEq3dZj1lZv6IOLeyrv5vsF6Ry9k1E3Wzz/5TFnI7o +fbsgngVms9nu0j7a1PHqNAMnXi6+WnTr3cGDtwltSiaJVaBzcSrryvgwENmU1Hw 6PTOSOSaamg5vovxkh5Mr3ask8pZgK6aZfHnWhHCgBPM2g2eoQsJJt8GvPQCfOC5 QT1IQQfn3iyh74fqdTWdCo82+heMX+f6LSZzAOE3tkpXs7yeV7hZ4a363X5dQaax AYfgl6QwHL+V3Ycy/a/yz8YKcTMqYHRzX9EdgOjI4FdOrXFGI1OCVHbyhMyvK8pi USXqYLEJNi833w5RL2BG7OjC9iTsYKpIIozjX/nPnNdMPK5IZVXixZGX8ppFbWeM 2cU1abblQmDrTpKeRuhoadogLbyuzaz+pfBmf2yBeGxz9jLKpRHvNkltmEkonAcy nqKELFgx4KOCSyj2Tdcg8xyTXBzRenab2DRF1kvxm+jCYCoxMHgNy2veIdROVUJa G5RbIIVPpzYE1HKCeuB8FIkFCYhOJ/ntB4PqsXUbZD5Y6TuUWTBFNcb1K6yC7fb0 JFHANwem+3m/xOQ5casL481BkcwJNA4RSwtZZ2NQ6ZG+V0im6v3wWRdjg0xDBTYt xSGmrZPffMkzLdMbdsUM =5mij -----END PGP SIGNATURE----- --0ywUhQCikZ2Y3PNw-- From owner-freebsd-stable@freebsd.org Thu Jul 23 14:59:27 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B487B9A9A28 for ; Thu, 23 Jul 2015 14:59:27 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E80812EE for ; Thu, 23 Jul 2015 14:59:27 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wibxm9 with SMTP id xm9so153601598wib.1 for ; Thu, 23 Jul 2015 07:59:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=D+UkGqSQJHkmkhwzavb7PBAvjZgtT7GIQRaY+xdb5g4=; b=j1W4ncgui1o0CIPqMTDh9V4LYvYWWWPgOp/eOgM/qAiY9voRljIM5oU4igY5yq6aJk 6Wg9+rf1tQWSFIaXxy6scmLe3eOUk2pJ/TfUvbAMa62h68xkaZ8N4Znd8jjcq6fO3y6D st+hbT3jCQo4rQMvOKaYKthtP0Os0o3pvnnUHElVe4I8K1L9wyC08s5YE80zgAjn8adb Gs0V9QSQjxYDpQirrvgVLGWBRNZinFFxLjhabtdlX+sxe4SIG0lbBsiCRqHELzJGtiox 1YKSCyF0007k7Rfl+SNs6ecwEcYyH+nqe61wFE0VnhowAUY7N7mgcN8ZCnE6bNqDqL/i 2jkg== MIME-Version: 1.0 X-Received: by 10.194.187.170 with SMTP id ft10mr16676286wjc.26.1437663565836; Thu, 23 Jul 2015 07:59:25 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Thu, 23 Jul 2015 07:59:25 -0700 (PDT) In-Reply-To: <190031437662308@web29g.yandex.ru> References: <464641437658995@web16j.yandex.ru> <190031437662308@web29g.yandex.ru> Date: Thu, 23 Jul 2015 10:59:25 -0400 Message-ID: Subject: Re: struct timehands: th_generation field From: Brandon Allbery To: deco33000@yandex.com Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 14:59:27 -0000 On Thu, Jul 23, 2015 at 10:38 AM, wrote: > Is the maximum value for th_generation equal to 10 ? > http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L77 > I don't think those relate to generations. Generations change on every clock tick; the multiple timehands structs relate to forcibly setting the time, as opposed to the clock moving forward normally. It does appear serve a similar purpose, since forcibly setting the time is even more "violent" (to anything currently reading the clock) than advancing the clock on a clock tick, since that's when other adjustments including possibly switching the clock source will be applied. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Thu Jul 23 15:28:49 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F55E9A819B for ; Thu, 23 Jul 2015 15:28:49 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from erouter6.ore.mailhop.org (erouter6.ore.mailhop.org [54.187.213.119]) by mx1.freebsd.org (Postfix) with SMTP id 1EF4C1FC6 for ; Thu, 23 Jul 2015 15:28:48 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound3.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 23 Jul 2015 15:26:49 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t6NFSdAT009525; Thu, 23 Jul 2015 09:28:39 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1437665319.1334.519.camel@freebsd.org> Subject: Re: struct timehands: th_generation field From: Ian Lepore To: Brandon Allbery Cc: deco33000@yandex.com, freebsd-stable Date: Thu, 23 Jul 2015 09:28:39 -0600 In-Reply-To: References: <464641437658995@web16j.yandex.ru> <190031437662308@web29g.yandex.ru> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 15:28:49 -0000 On Thu, 2015-07-23 at 10:59 -0400, Brandon Allbery wrote: > On Thu, Jul 23, 2015 at 10:38 AM, wrote: > > > Is the maximum value for th_generation equal to 10 ? > > http://fxr.watson.org/fxr/source/kern/kern_tc.c?v=FREEBSD10#L77 > > > > I don't think those relate to generations. Generations change on every > clock tick; the multiple timehands structs relate to forcibly setting the > time, as opposed to the clock moving forward normally. It does appear serve > a similar purpose, since forcibly setting the time is even more "violent" > (to anything currently reading the clock) than advancing the clock on a > clock tick, since that's when other adjustments including possibly > switching the clock source will be applied. > Ummm, no. The multiple timehands and related generation count are all about time moving forward normally, and doing so without needing mutxes or other locking primitives to obtain the current time. I think you guys need to read this... http://phk.freebsd.dk/pubs/timecounter.pdf Especially the section named "Locking, lack of..." -- Ian From owner-freebsd-stable@freebsd.org Thu Jul 23 23:21:38 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3BAFE9A992D for ; Thu, 23 Jul 2015 23:21:38 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward20h.cmail.yandex.net (forward20h.cmail.yandex.net [87.250.230.162]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E28DB1C5B for ; Thu, 23 Jul 2015 23:21:37 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp2h.mail.yandex.net (smtp2h.mail.yandex.net [84.201.187.145]) by forward20h.cmail.yandex.net (Yandex) with ESMTP id 7ED1821965 for ; Fri, 24 Jul 2015 02:21:30 +0300 (MSK) Received: from smtp2h.mail.yandex.net (localhost [127.0.0.1]) by smtp2h.mail.yandex.net (Yandex) with ESMTP id 46A8C1708C3A for ; Fri, 24 Jul 2015 02:21:30 +0300 (MSK) Received: by smtp2h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id olpoAfdPjq-LSVGO6t4; Fri, 24 Jul 2015 02:21:28 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437693689; bh=kuzYnIqFVj8KJng7yxmPn8rtAGIkmn3lUzDLRyJQM9o=; h=Message-ID:Subject:From:To:Date:Content-Type:X-Mailer: Mime-Version:Content-Transfer-Encoding; b=Z+9wL0i6mfVtHCOKrpnVm3a80I1FImJzGIRBxkrtBRSokUzqb5c/GeGZQyAUQ+F2j ai3hY7aS06V+NCuuPOCHx3/vJX9OkLQrqSDEno5BhSHfKarhtvNTEcPJfexlI+sY9a 20nHP/IR0VLz+LIkx3oT7clGXIj16ZVpjVMd/M5w= Authentication-Results: smtp2h.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437693686.78236.2.camel@yandex.com> Subject: freebsd downgrade From: Stari Karp To: freebsd-stable@freebsd.org Date: Thu, 23 Jul 2015 19:21:26 -0400 Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 23:21:38 -0000 Hi! I had a problems with FreeBSD 10.2-BETA2. I used freebsd-update ugrade and update FreeBSD 10.1-RELEASE. Is it possible to downgrade BETA2 to 10.1-RELEASE with freebsd-update upgrade -r 10.1-RELEASE, please? Thank you. From owner-freebsd-stable@freebsd.org Thu Jul 23 23:40:45 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F13069A9D0E for ; Thu, 23 Jul 2015 23:40:45 +0000 (UTC) (envelope-from jason.unovitch@gmail.com) Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B264C1A9F for ; Thu, 23 Jul 2015 23:40:45 +0000 (UTC) (envelope-from jason.unovitch@gmail.com) Received: by ykay190 with SMTP id y190so6789075yka.3 for ; Thu, 23 Jul 2015 16:40:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=XJnK9R823PdOh8swzQ+emxuh8aayWo2v7JjxSKDLv0w=; b=gKurVH7+xASw6L8dxGLjjNKpP5klwwkxsB99pLwak+MecdOu0QP3VdImSD/4uu3eXu AKKLBt+0W9rPZo607ZXdByf9yBUCxxxxLkmP0QGDRQ5wG40pnXogFRHEXimagNBhTJfg 5rEqPkz2Z9Ei/qOoqtZSBCbRXZb5CZb8zxJehuHWX7NcQZ7/+YTG8rxXQku1QVkUO9vL uq+H9VTFOh1b8+OGdNDl8Rti7n1vmBFHT/3CU9GNTYNAVymxSbSSePLOzM3OhJVQJR7l 1ar8J0RdtaZLXUvP2wfUCRF2/EqhpQMG336Dvv7rlZbA1xCfP3/NckUdXQcnGYiy36Gx sRpA== X-Received: by 10.13.196.4 with SMTP id g4mr11515236ywd.130.1437694844869; Thu, 23 Jul 2015 16:40:44 -0700 (PDT) Received: from ?IPv6:2606:a000:568e:5902:be5f:f4ff:fe5d:f28? ([2606:a000:568e:5902:be5f:f4ff:fe5d:f28]) by smtp.googlemail.com with ESMTPSA id z67sm6513311ywz.38.2015.07.23.16.40.43 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Jul 2015 16:40:44 -0700 (PDT) Message-ID: <55B17B7A.4080402@gmail.com> Date: Thu, 23 Jul 2015 19:40:42 -0400 From: Jason Unovitch User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org, holm@freibergnet.de, herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 23:40:46 -0000 >> ..uh top quoting.. >> >> Trying to mount root from zfs:zroot/ROOT/default []. >> >> Fatal double fault: >> eip = 0xc0b416f5 >> esp = 0xe2673000 >> ebp = 0xe2673008 >> cpuid =0; apic id = 00 >> panic: double fault >> cpuid = 0 >> KDB stack backtrace: >> #0 0xc0b72832 at kdb_backtrace+0x52 >> #1 0xc0b339cb at vpanic+0x11b >> #2 0xc0b338ab at panic+0x1b >> #3 0xc10556 at dblfault_handler+0xab >> Uptime: 11s >> .. > >Looks like the panic I received on my Soekris Net6501-70. > >Fixed in stable/10 in r285759: >https://svnweb.freebsd.org/changeset/base/285759 > >Fixed in stable/9 in r285760: >https://svnweb.freebsd.org/changeset/base/285760 > >-- >Herbert Herbert, in https://bugs.FreeBSD.org/201642 I had tracked down the commit that caused the issue on our Soekris 6501s. Only between r284297 -> r285662 in HEAD and between r284998 -> r285756 in stable/10 should be affected. >>>Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, >>>ok tried 9.3-RELEASE .. the same! Holm, if you are seeing this on 9.3-RELEASE and 10.1-RELEASE I'm not entirely convinced the cause is the same. -- Jason From owner-freebsd-stable@freebsd.org Thu Jul 23 23:48:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D84319A9DA4 for ; Thu, 23 Jul 2015 23:48:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C656B1D03; Thu, 23 Jul 2015 23:48:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 18EE01BCC; Thu, 23 Jul 2015 23:48:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Thu, 23 Jul 2015 23:48:06 +0000 From: Glen Barber To: Jason Unovitch Cc: freebsd-stable@freebsd.org, holm@freibergnet.de, herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150723234805.GK84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="Z9t8O/5YJLB6LEUl" Content-Disposition: inline In-Reply-To: <55B17B7A.4080402@gmail.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 23:48:08 -0000 --Z9t8O/5YJLB6LEUl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 23, 2015 at 07:40:42PM -0400, Jason Unovitch wrote: > >> ..uh top quoting.. > >> > >> Trying to mount root from zfs:zroot/ROOT/default []. > >> > >> Fatal double fault: > >> eip =3D 0xc0b416f5 > >> esp =3D 0xe2673000 > >> ebp =3D 0xe2673008 > >> cpuid =3D0; apic id =3D 00 > >> panic: double fault > >> cpuid =3D 0 > >> KDB stack backtrace: > >> #0 0xc0b72832 at kdb_backtrace+0x52 > >> #1 0xc0b339cb at vpanic+0x11b > >> #2 0xc0b338ab at panic+0x1b > >> #3 0xc10556 at dblfault_handler+0xab > >> Uptime: 11s > >> .. > > > >Looks like the panic I received on my Soekris Net6501-70. > > > >Fixed in stable/10 in r285759: > >https://svnweb.freebsd.org/changeset/base/285759 > > > >Fixed in stable/9 in r285760: > >https://svnweb.freebsd.org/changeset/base/285760 > > >=20 > Herbert, in https://bugs.FreeBSD.org/201642 I had tracked down the commit > that caused the issue on our Soekris 6501s. Only between r284297 -> r285= 662 > in HEAD and between r284998 -> r285756 in stable/10 should be affected. >=20 > >>>Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, > >>>ok tried 9.3-RELEASE .. the same! >=20 > Holm, if you are seeing this on 9.3-RELEASE and 10.1-RELEASE I'm not > entirely convinced the cause is the same. >=20 ZFS on i386 requires KSTACK_PAGES=3D4 in the kernel configuration to work properly, as noted in the 10.1-RELEASE errata (and release notes, if I remember correctly). We cannot set KSTACK_PAGES=3D4 in GENERIC by default, as it is too disruptive. If you are using ZFS on i386, you *must* build your own kernel for this. It is otherwise unsupported by default. Glen --Z9t8O/5YJLB6LEUl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsX01AAoJEAMUWKVHj+KTaHoQAI4FNxtrhQ90SpuhtMNjCoOq R7QCE2lB7viKIeFM/Xl3SX7aUFCbkf3CT6MsEMIFCqXLq/PBOW1+7lrcqKoan/GL QthtQ1b8esgzfkwj4HJcpY0yLNKDs5cWuHgROn5Nb3K8jHDO1pk3e3Gc4NpiO8nD eZuA8+B0Y5NCsK2pHH5RsfOUc90fkhP7HC+JO4bbCQkdvTwhZCVqLQpdllcJS3/j 3EHMclqlEM6wHjXNoLbMNirzc5f0vet/f5ZakHfLaCC7rqfGBJDkUw0YQBZ2gWT/ k32xDlzqWnJaC9M8IhSr7T+WsmLI1uKF19jW3Dk7ZOdITbNUKX7H28A9OI9EPh5X G03sabEOi9MDA67OnfoLE0HD/ZD2cX3v+EKiiXtxPy1kdgWg1uXug7T13/kflcZ+ /7Ae1ezxkrH9GaQO/szCaN2+D+PubQ+iXDSFIqIbeAIux+XE+oJ1M/lU8DuAcvER mS24TrzH/ye+qoLYFrj9E+1b0k8awsQEYRNYleQ7UsUiqkvJmHYMyw4RBILeEzTu gkLx2LMMvhWi3NjXUP/7DXDReE/ubbkFEbs/K9z+/VhVqw7UfuC2RZh77XUgj6l+ FVVU6PJIEXlRUl/OiSqIMVZPovK0TsjX8jXgjUfxWWnN04U+c61xaSSr14oDKXNO NqCuywIinhqBcW7l70FU =OBB1 -----END PGP SIGNATURE----- --Z9t8O/5YJLB6LEUl-- From owner-freebsd-stable@freebsd.org Thu Jul 23 23:51:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 10D669A9E63 for ; Thu, 23 Jul 2015 23:51:08 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id F0C4F103C for ; Thu, 23 Jul 2015 23:51:07 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from zeta.ixsystems.com (unknown [12.229.62.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id 7C82A1CB47; Thu, 23 Jul 2015 16:51:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1437695467; x=1437709867; bh=9ZxUDfs7YBodKonpUYxy43uwipahfdlcoEigYPwitCw=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=xa7eC9FM84GM+hwtcFoCJvRb9V2+6P1m/3EXSn+Vfw+PElAWVZhrztaIbemNbGGDX G2D6y4FP5axyAUwvVZZnsZaofan3wDKvT7MgCawq31HyCEicU4XUjINhahEb0/A8WW dhjeTG9egQetG4HLj9R/pASJQq5dFkOFomJJrhH4= Message-ID: <55B17DEB.6070302@delphij.net> Date: Thu, 23 Jul 2015 16:51:07 -0700 From: Xin Li Reply-To: d@delphij.net Organization: The FreeBSD Project MIME-Version: 1.0 To: Stari Karp , freebsd-stable@freebsd.org Subject: Re: freebsd downgrade References: <1437693686.78236.2.camel@yandex.com> In-Reply-To: <1437693686.78236.2.camel@yandex.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jul 2015 23:51:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 07/23/15 16:21, Stari Karp wrote: > Hi! > > I had a problems with FreeBSD 10.2-BETA2. I used freebsd-update > ugrade and update FreeBSD 10.1-RELEASE. Is it possible to downgrade > BETA2 to 10.1-RELEASE with freebsd-update upgrade -r 10.1-RELEASE, > please? It's not supported (because you may be running binaries that depends on new kernel). What kind of problems did you have? Please let re@ know so we can get them fixed. Cheers, - -- Xin LI https://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.1.6 (FreeBSD) iQIcBAEBCgAGBQJVsX3rAAoJEJW2GBstM+nshTsP/1gkFDhlrzElnOPfxtQEc80H 6oocZG4Upn9UbrFIq9GKU4qU8XIC8fHtYtLyXAbjj5vebEMkOAJuhzE8HrN3eh+N hZKtKRiK7fNSFWCkqmd2BY0G05IBEXgQXzbgRzc65OrRcrp5MSL109bxYjN7Ih1L wMtulWxfxyqsCZ4h6qwjZehJTkPMwiaGfhjbxAUbghzJKEyCKVGmGCE5Wbz4q++W 9bkQXElu1777WlJ3X+6tvgRkBxpYdaXSzL2UAH5cZrM7b5T09KfcgKsl+x9o1CGN PGRQZqNcdyxEebjMqJaE2BOuvtocIrlpEOtC0VT7f5pLp64pV8PYPQGzdi+01LZD w/wNvkJFqhIT42h/DDuTj7kOsrJhDA5Q2Vho9KW4YZFbDO9eglCA2KhDgrLQejl3 9z0byDWq+my638CRQIjHcf0QBokdXceK/AVjnIx9Os59OD0dQkl3ISSRhSDQPmqe urI96uQ582vo6h+Tiic119aPtmy7aTn6PqtsTEYLnb5YTFx8oF4XaBuP7a3RmcBm JX3oX5vIzOiDWtnG27yhsy5Bido91xPznnCLoC24MKuO7YFJb9Pi4x4fy8jIQkpp gZTz7AkGR8oFroisPb9DGkkhT5QcwQviEnyRA1pR0dk7Sv6mzckRRSxxMn6s1SrY 0oVGHIe54nF7T1MRZc15 =BS7Y -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Fri Jul 24 00:14:26 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CFF839A93C0 for ; Fri, 24 Jul 2015 00:14:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9EA951B4C for ; Fri, 24 Jul 2015 00:14:26 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t6O0EKWk091060 for ; Thu, 23 Jul 2015 17:14:27 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20150723234805.GK84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com>, <20150723234805.GK84931@FreeBSD.org> From: "Chris H" Subject: Re: 10.2-Beta i386..what's wrong..? Date: Thu, 23 Jul 2015 17:14:27 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <5b6f2cf186cc3ba5b968316049714f9f@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:14:26 -0000 On Thu, 23 Jul 2015 23:48:06 +0000 Glen Barber wrote > On Thu, Jul 23, 2015 at 07:40:42PM -0400, Jason Unovitch wrote: > > >> ..uh top quoting.. > > >> > > >> Trying to mount root from zfs:zroot/ROOT/default []. > > >> > > >> Fatal double fault: > > >> eip = 0xc0b416f5 > > >> esp = 0xe2673000 > > >> ebp = 0xe2673008 > > >> cpuid =0; apic id = 00 > > >> panic: double fault > > >> cpuid = 0 > > >> KDB stack backtrace: > > >> #0 0xc0b72832 at kdb_backtrace+0x52 > > >> #1 0xc0b339cb at vpanic+0x11b > > >> #2 0xc0b338ab at panic+0x1b > > >> #3 0xc10556 at dblfault_handler+0xab > > >> Uptime: 11s > > >> .. > > > > > >Looks like the panic I received on my Soekris Net6501-70. > > > > > >Fixed in stable/10 in r285759: > > >https://svnweb.freebsd.org/changeset/base/285759 > > > > > >Fixed in stable/9 in r285760: > > >https://svnweb.freebsd.org/changeset/base/285760 > > > > > > > Herbert, in https://bugs.FreeBSD.org/201642 I had tracked down the commit > > that caused the issue on our Soekris 6501s. Only between r284297 -> > > r285662 in HEAD and between r284998 -> r285756 in stable/10 should be > > affected. > > >>>Ok, it is 10.2-BETA so I've tried 10.1-Release next...exactly the same, > > >>>ok tried 9.3-RELEASE .. the same! > > > > Holm, if you are seeing this on 9.3-RELEASE and 10.1-RELEASE I'm not > > entirely convinced the cause is the same. > > > > ZFS on i386 requires KSTACK_PAGES=4 in the kernel configuration to work > properly, as noted in the 10.1-RELEASE errata (and release notes, if > I remember correctly). > > We cannot set KSTACK_PAGES=4 in GENERIC by default, as it is too > disruptive. If you are using ZFS on i386, you *must* build your own > kernel for this. It is otherwise unsupported by default. Shouldn't there be a GENERIC kernel with the KSTACK_PAGES=4 option defined, available? Maybe with one of the bootonly MEMSTICKS, or something? I know, it's (mostly) crazy to attempt ZFS on an i386. But it's pretty difficult for someone on 8.x to build a 9.x, or 10.x kernel. If all they've got is i386 hardware. Just a thought. --Chris > > Glen From owner-freebsd-stable@freebsd.org Fri Jul 24 00:19:29 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D91F39A94BF for ; Fri, 24 Jul 2015 00:19:29 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id C6DFB1EA0; Fri, 24 Jul 2015 00:19:29 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NRY00I4RUI6GN00@hades.sorbs.net>; Thu, 23 Jul 2015 17:25:20 -0700 (PDT) Message-id: <55B18488.9060602@sorbs.net> Date: Fri, 24 Jul 2015 02:19:20 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Glen Barber Cc: Jason Unovitch , freebsd-stable@freebsd.org, herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> In-reply-to: <20150723234805.GK84931@FreeBSD.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:19:29 -0000 Glen Barber wrote: > > ZFS on i386 requires KSTACK_PAGES=4 in the kernel configuration to work > properly, as noted in the 10.1-RELEASE errata (and release notes, if > I remember correctly). > > We cannot set KSTACK_PAGES=4 in GENERIC by default, as it is too > disruptive. Why? > If you are using ZFS on i386, you *must* build your own > kernel for this. It is otherwise unsupported by default. > Why is zfs on i386 so hard? Why is it even in the GENERIC kernel if it's unsupported? -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@freebsd.org Fri Jul 24 00:23:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 47A4E9A95E2 for ; Fri, 24 Jul 2015 00:23:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 3502211B1; Fri, 24 Jul 2015 00:23:08 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 895BF134A; Fri, 24 Jul 2015 00:23:07 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 00:23:05 +0000 From: Glen Barber To: Michelle Sullivan Cc: Jason Unovitch , freebsd-stable@freebsd.org, herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724002305.GL84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GeDkoc8jIzHasOdk" Content-Disposition: inline In-Reply-To: <55B18488.9060602@sorbs.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:23:08 -0000 --GeDkoc8jIzHasOdk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 02:19:20AM +0200, Michelle Sullivan wrote: > Glen Barber wrote: > > > > ZFS on i386 requires KSTACK_PAGES=3D4 in the kernel configuration to wo= rk > > properly, as noted in the 10.1-RELEASE errata (and release notes, if > > I remember correctly). > > > > We cannot set KSTACK_PAGES=3D4 in GENERIC by default, as it is too > > disruptive. =20 >=20 > Why? >=20 Because it takes resources away from userland threads. > > If you are using ZFS on i386, you *must* build your own > > kernel for this. It is otherwise unsupported by default. > > =20 > Why is zfs on i386 so hard? Why is it even in the GENERIC kernel if > it's unsupported? >=20 It is not in GENERIC by default. You have to specifically kldload(8) zfs.ko. Glen --GeDkoc8jIzHasOdk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsYVpAAoJEAMUWKVHj+KTrJEP/jKfVfpVugERU1hdctObLYaB xNtWpnb+8BBasua25hq6mmE3wZA9OeOUEkBAUIHdj701McJQapAoaNzSJ3Gy4waZ diZN6FtA3LJkL+3Na6p3Lse22BJPDgdDUPlDSOwKS34YwebAHsfFTbllp2PJSngY PDY8J9tL4zitt9lE7XwIPuhq4EB3xTDn/CerXPUMEzJb4X8gGqD1IEkw9LvVBAE+ cAW3eNHffDGcOGszEqVgIE335aV2oXFZbdixLq9VhrZ44u5HpzgwvyWOTk2uBvm3 4WHA4T0sLpQ6T1SFxGKKLNdcdLUGwTDU/S+yvGSwfm2qukT4J8aNdkqtj7fSeqaS IF8zxdSEdjOYdC6jaTgkEr7YyrvehME/HnccRrkLdoTKzSCpsqmjRdPmbN54r4/F XgcH+gdQeaaqKOIoYChoDnovZN7eAVM78Dcx0/eV30mTQ5XYc7HhmKhdbimL80Xc m0tiO2WNHlp2GJO7ZpFBKYKMK2XzFV1vr7VOfoS6lcFyPT8mAagf1mc5eT70ajV9 qjjQ1xnEnqrxP4SWMZeiku6gr4TfSUhvZs9KjXKN6wljhmzgx1maUcCsh/bGmZj4 LevdQs/BJ315UPGNRy2DUVvhN7yMWTVWVU1yk8c4C7GyM23FmolFRnmuqgDhsX0C y5Ah8k/jKoXd8Bx5m5Xy =1rUd -----END PGP SIGNATURE----- --GeDkoc8jIzHasOdk-- From owner-freebsd-stable@freebsd.org Fri Jul 24 00:40:33 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EEDBF9A9860 for ; Fri, 24 Jul 2015 00:40:33 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [66.135.54.68]) by mx1.freebsd.org (Postfix) with ESMTP id CFE251983; Fri, 24 Jul 2015 00:40:33 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id B9AD05607A; Thu, 23 Jul 2015 19:40:26 -0500 (CDT) Date: Thu, 23 Jul 2015 19:40:26 -0500 From: Mark Linimon To: Michelle Sullivan Cc: Glen Barber , freebsd-stable@freebsd.org, herbert@oslo.ath.cx, Jason Unovitch Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724004026.GA1370@lonesome.com> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B18488.9060602@sorbs.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:40:34 -0000 On Fri, Jul 24, 2015 at 02:19:20AM +0200, Michelle Sullivan wrote: > Why is zfs on i386 so hard? zfs is a resource hog. i386 is not able to handle the demand as well as amd64. I have never, ever, heard of anyone who has a deep understanding of zfs on FreeBSD recommend anything other than amd64. (Note: I am not such a person, so I am simply reporting my understanding.) FWIW, I tried it once. Once. After spending a few days inspecting all the bullet holes in my feet, I moved it off that i386 machine and all the bullet holes healed up. tl;dr: zfs/i386 Not Recommended. But YMMV. mcl From owner-freebsd-stable@freebsd.org Fri Jul 24 00:42:46 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39E7E9A997E for ; Fri, 24 Jul 2015 00:42:46 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C73251C53; Fri, 24 Jul 2015 00:42:45 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wicmv11 with SMTP id mv11so44931967wic.0; Thu, 23 Jul 2015 17:42:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UC8jE9cPR9UbRpxENE2rN6aukdDntV3Dc94MO+GH/dQ=; b=YL8cidzSuYEfk+fbp2xzQFJBnmZNUgUfzxLwQ6/45y7uwjbdL/gKNjHwkYPE5Jumw9 2SbMCESQmTPhqHP/1AcBxPLyTrAgXMYOw+DwJvHoo2D3jXBhpk5ER7Wa6a0RR8X3rixm JY/+ImYwltiIYIQW/jcCcM0d5DqhhBuO4PI1X9iPGvzvDg+YsTMIikEqyvwkkfp7H6Az ZSrFf/cr40LYfbaK8DAw29AGzsp5FP0+0XWq4g7uA14MVMti9+0SpjPzeJuefmf72K8o v3flewmsTCWKs/lBmdrC3wYk1So6CcE3jvMueF03qv60AjtIerzlR9fJX7gtIp2sTR9L EcMw== MIME-Version: 1.0 X-Received: by 10.194.121.100 with SMTP id lj4mr20978945wjb.104.1437698564397; Thu, 23 Jul 2015 17:42:44 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Thu, 23 Jul 2015 17:42:44 -0700 (PDT) In-Reply-To: <20150724004026.GA1370@lonesome.com> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> Date: Thu, 23 Jul 2015 20:42:44 -0400 Message-ID: Subject: Re: 10.2-Beta i386..what's wrong..? From: Brandon Allbery To: Mark Linimon Cc: Michelle Sullivan , Glen Barber , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:42:46 -0000 On Thu, Jul 23, 2015 at 8:40 PM, Mark Linimon wrote: > zfs is a resource hog. i386 is not able to handle the demand as well > as amd64. > Even amd64 is no guarantee. I installed one of the Illumos spinoffs on a 2GB amd64 netbook (they mostly force zfs). I think it lasted 2 days before the kernel panics started. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Fri Jul 24 00:43:46 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 81D969A99BF for ; Fri, 24 Jul 2015 00:43:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6C6E71D5D; Fri, 24 Jul 2015 00:43:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 897721632; Fri, 24 Jul 2015 00:43:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 00:43:43 +0000 From: Glen Barber To: Brandon Allbery Cc: Mark Linimon , Michelle Sullivan , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724004343.GM84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1rguoi8KZGYj2k4L" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:43:46 -0000 --1rguoi8KZGYj2k4L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 23, 2015 at 08:42:44PM -0400, Brandon Allbery wrote: > On Thu, Jul 23, 2015 at 8:40 PM, Mark Linimon wrot= e: >=20 > > zfs is a resource hog. i386 is not able to handle the demand as well > > as amd64. > > >=20 > Even amd64 is no guarantee. I installed one of the Illumos spinoffs on a > 2GB amd64 netbook (they mostly force zfs). I think it lasted 2 days before > the kernel panics started. >=20 Even on amd64, you need to tune the system with less than 4GB RAM. Glen --1rguoi8KZGYj2k4L Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsYo/AAoJEAMUWKVHj+KTHbcQAKPTvJD0z5YflC9MzPKRFc7o F33oD6Eq0+xZuo5Lx0+MxefjwsP4B3rAuP+iHYgN3kCxFiDdk+5QBkEal4m0FAkm I+ID5ViiZamfE6Omr2eXSKd2KGVlmaTaxQ7zEocD3jFCv88cA3n6KQ2CBXptCyhd yQNgb7EAwu58F3GFwPn/qsiSLQt+3HPd3Ryn1SlYYLlvI5mf37TuX4UnKu45JcsI QXz+5c55hvGFWV6UcDfhWV6WU/ChckYoheZyZLVNRX3p9mM0u8WxSTQluGMV4Noc ls1q3tlfX4BqcHJJsv9yOSaO9+epyNee3U7hGi6BqNSexEJZte9w5J9NqXktGw6S ActpsGfCgKhd+GzKZDBRJxP1t2CfqYc0Fp2RyXcw6VtIoXOp7+TedTineAuChnL0 akwhjDoHQ8lSoDI8K2Ujge6E0S/670e83G/dv7WpoNpvj2V2jQUH2RtyRnu45U/w TJEz6ACvWbAw9jn1fC0NQNavsQV87T4TOHWgHHm7vN7MKHbEgo5caSQOc8R7nXlu 3m4RxEf5JZIDwAW2eLO8iBnUCD7UHZEhZ/Pq5qpkshGBrbFqNN7iGiC6Ltxx37Hl juzdToCtvGl4wG4BzcgQ47pN9kUlePCgNax7yX+uBJMrI/1SORpWICJL27mmzVXI X2KHb/7LT6hEVjjGl5xD =FT1F -----END PGP SIGNATURE----- --1rguoi8KZGYj2k4L-- From owner-freebsd-stable@freebsd.org Fri Jul 24 00:44:44 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 735D49A9A22 for ; Fri, 24 Jul 2015 00:44:44 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [66.135.54.68]) by mx1.freebsd.org (Postfix) with ESMTP id 569071E9E; Fri, 24 Jul 2015 00:44:44 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id ED72F5607A; Thu, 23 Jul 2015 19:44:43 -0500 (CDT) Date: Thu, 23 Jul 2015 19:44:43 -0500 From: Mark Linimon To: Glen Barber Cc: Brandon Allbery , Michelle Sullivan , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724004443.GC1370@lonesome.com> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150724004343.GM84931@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:44:44 -0000 On Fri, Jul 24, 2015 at 12:43:43AM +0000, Glen Barber wrote: > Even on amd64, you need to tune the system with less than 4GB RAM. The only correct answer to "how much RAM do you need to run ZFS" is "always more" AFAICT. mcl From owner-freebsd-stable@freebsd.org Fri Jul 24 00:47:19 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A96269A9AA7 for ; Fri, 24 Jul 2015 00:47:19 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 41C551018; Fri, 24 Jul 2015 00:47:19 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wibxm9 with SMTP id xm9so6665246wib.1; Thu, 23 Jul 2015 17:47:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=NLbj0GiWiyRaDynnz751oyfxJ+AoNn+eH2nLsM/oQQA=; b=GxvsApR5P8lny3uDQgQ94xA+C5AKJ3QBoTeVyKpwQFbcN1gJpm0AKVSB0E0QSkNRWI eBGiaqhTjKZfY2Ks9qy/NFo9PsWRTED+9r/G7RUe8fTVax7v11ljlNI40uGzkUU/zTJZ x96Xr4x0fDnG9XQaf770ocz/orONAyAUDHY83O0FeK2UnbAX0iMKFmnlLj7WPHgEYyez PEaPfqCM45GVG9DJJyWo6kdUb61d5lQbL8hwEN6pWVl6pi0eX9kDKV6RBmn0toAMTbMJ KQRkMfEResg0xnWqAha4hkiCmkC9SxMp1BUuN0k9MIaLi8dTNMsWaQzFFDTpwhLHhCpo ieXA== MIME-Version: 1.0 X-Received: by 10.180.37.48 with SMTP id v16mr1623232wij.79.1437698837765; Thu, 23 Jul 2015 17:47:17 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Thu, 23 Jul 2015 17:47:17 -0700 (PDT) In-Reply-To: <20150724004343.GM84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> Date: Thu, 23 Jul 2015 20:47:17 -0400 Message-ID: Subject: Re: 10.2-Beta i386..what's wrong..? From: Brandon Allbery To: Glen Barber Cc: Mark Linimon , Michelle Sullivan , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:47:19 -0000 On Thu, Jul 23, 2015 at 8:43 PM, Glen Barber wrote: > > Even amd64 is no guarantee. I installed one of the Illumos spinoffs on a > > 2GB amd64 netbook (they mostly force zfs). I think it lasted 2 days > before > > the kernel panics started. > > > > Even on amd64, you need to tune the system with less than 4GB RAM. I knew it wasn't going to fly, in fact I looked for ways to get the installer to do ufs instead because I couldn't imagine zfs being able to work in 2GB. Somehow I don't think old netbooks are in Illumos's plans. :) -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Fri Jul 24 00:49:41 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E42E69A9B14 for ; Fri, 24 Jul 2015 00:49:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id CE0C91132; Fri, 24 Jul 2015 00:49:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 02B8F1814; Fri, 24 Jul 2015 00:49:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 00:49:39 +0000 From: Glen Barber To: Mark Linimon Cc: Brandon Allbery , Michelle Sullivan , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724004939.GN84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tpyx7gKuSYt+mjHM" Content-Disposition: inline In-Reply-To: <20150724004443.GC1370@lonesome.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:49:42 -0000 --tpyx7gKuSYt+mjHM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 23, 2015 at 07:44:43PM -0500, Mark Linimon wrote: > On Fri, Jul 24, 2015 at 12:43:43AM +0000, Glen Barber wrote: > > Even on amd64, you need to tune the system with less than 4GB RAM. >=20 > The only correct answer to "how much RAM do you need to run ZFS" is > "always more" AFAICT. >=20 There's a bit more to it than that. You *can* successfully run amd64 ZFS system with certain tunings (vfs.kmem_max IIRC), but you also need to adjust things like disabling prefetching with less than 4GB RAM (accessible to the OS). So yeah, "more RAM" is always a thing in this playing field. Glen --tpyx7gKuSYt+mjHM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsYujAAoJEAMUWKVHj+KTlWcP/RxYnX7Tkgs02S8cvzyOLQ4k lgAgNXF0Dvb4PBwaN1ZOPtRT1m/hzStzwM5nlyH4+g63H/C64WlF8++xJaSVTByr XgAEqJyeOjP0wBQYLvKfWJitXOEpr1BLyYMy/dRj1uXcNYm5X4oLIByxUGl3GJIe tUNiDdDdfxXgFMun9o4dyK/w3jYVw6uGW9tJFD/2fUGv0SMikSS7OkEylVAGL91F Q6Yb4V9ExPsfgr4WEQPVUAEeeSVpWpFyTc+r8FsPe+s3UPRcJYz7jJ4CaWg1kCRP G2EQck/VBX6TsR0JmtdHa9TP0xQSRybsQ6jc2igfq809QrFgYX39f5AwdBM+DzRE H8mBvikgJTNhr5qAzuO3b1eeyvLZArFK7rOc1m9vUxXMINRlCkH9aPvWeGiPhekh 6KEDHlFPhqGlXDI9fG838Mss9FtGW+KjSVJitvfToOBLxzmuTLkHCUbnE8FmW90s o+Yx3CvmcO6zFKjY/GMvJmzspRIOcg0Sha6dvPRAC548VQFP+utcExQPXX4cWzxV s1l9jmqICnOVw+VJncxjPf3xhv0E9c0P2ckZtDQI8ewDGTp4fKiXP5kZkK6ZqxwQ 18uvJMxuU0BaqHjqRFAd5UhCt2HlOg4bsPAj+E/yv/+0n8nZt12mK8qmqhNoC/Zo m1hUdxhX82pFlW7t58Yz =67Nj -----END PGP SIGNATURE----- --tpyx7gKuSYt+mjHM-- From owner-freebsd-stable@freebsd.org Fri Jul 24 00:54:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8941D9A9CBC for ; Fri, 24 Jul 2015 00:54:06 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 7657718D5; Fri, 24 Jul 2015 00:54:06 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NRY00I53W3YGN00@hades.sorbs.net>; Thu, 23 Jul 2015 18:00:01 -0700 (PDT) Message-id: <55B18CA8.1020909@sorbs.net> Date: Fri, 24 Jul 2015 02:54:00 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Glen Barber Cc: Mark Linimon , Brandon Allbery , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> In-reply-to: <20150724004939.GN84931@FreeBSD.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 00:54:06 -0000 Glen Barber wrote: > On Thu, Jul 23, 2015 at 07:44:43PM -0500, Mark Linimon wrote: > >> On Fri, Jul 24, 2015 at 12:43:43AM +0000, Glen Barber wrote: >> >>> Even on amd64, you need to tune the system with less than 4GB RAM. >>> >> The only correct answer to "how much RAM do you need to run ZFS" is >> "always more" AFAICT. >> >> > > There's a bit more to it than that. You *can* successfully run amd64 > ZFS system with certain tunings (vfs.kmem_max IIRC), but you also need > to adjust things like disabling prefetching with less than 4GB RAM > (accessible to the OS). > > So yeah, "more RAM" is always a thing in this playing field. > > Glen > > Actually I'm quite sucessfully running zfs on i386 (in a VM) ... here's the trick (which leads me to suspect ARC handling as the problem) - when I get to 512M of kernel space or less than 1G of RAM available system wide, I export/import the zfs pool... Using this formula I have uptimes of months... I haven't yet tried the 'ARC patch' that was proposed recently... -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@freebsd.org Fri Jul 24 01:00:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E653D9A9DA1 for ; Fri, 24 Jul 2015 01:00:05 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id CA8D51C04; Fri, 24 Jul 2015 01:00:05 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id EF8531B83; Fri, 24 Jul 2015 01:00:04 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 01:00:03 +0000 From: Glen Barber To: Michelle Sullivan Cc: Mark Linimon , Brandon Allbery , freebsd-stable , Jason Unovitch , herbert@oslo.ath.cx Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724010003.GO84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> <55B18CA8.1020909@sorbs.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="V7BlxAaPrdhzdIM1" Content-Disposition: inline In-Reply-To: <55B18CA8.1020909@sorbs.net> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 01:00:06 -0000 --V7BlxAaPrdhzdIM1 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 02:54:00AM +0200, Michelle Sullivan wrote: > Glen Barber wrote: > > On Thu, Jul 23, 2015 at 07:44:43PM -0500, Mark Linimon wrote: > > =20 > >> On Fri, Jul 24, 2015 at 12:43:43AM +0000, Glen Barber wrote: > >> =20 > >>> Even on amd64, you need to tune the system with less than 4GB RAM. > >>> =20 > >> The only correct answer to "how much RAM do you need to run ZFS" is > >> "always more" AFAICT. > >> > >> =20 > > > > There's a bit more to it than that. You *can* successfully run amd64 > > ZFS system with certain tunings (vfs.kmem_max IIRC), but you also need > > to adjust things like disabling prefetching with less than 4GB RAM > > (accessible to the OS). > > > > So yeah, "more RAM" is always a thing in this playing field. > > > > Glen > > > > =20 > Actually I'm quite sucessfully running zfs on i386 (in a VM) ... here's > the trick (which leads me to suspect ARC handling as the problem) - when > I get to 512M of kernel space or less than 1G of RAM available system > wide, I export/import the zfs pool... Using this formula I have uptimes > of months... I haven't yet tried the 'ARC patch' that was proposed > recently... >=20 Which FreeBSD version is this? Things changed since 10.1-RELEASE and what will be 10.2-RELEASE enough that I can't even get a single-disk ZFS system (in VirtualBox) to boot on i386. During 10.1-RELEASE testing, I only saw problems with multi-disk setup (mirror, raidzN), but the FreeBSD kernel grew since 10.1-RELEASE, so this is not unexpected. Glen --V7BlxAaPrdhzdIM1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsY4MAAoJEAMUWKVHj+KT8cgP/iQ4C8gNdfJrh/7TA9IXZMT6 TWpgSh6L+Xun3t4FhzyR8dgdd/Qdz5XoWvarMYjlFd1WpSFvCsfns1PxdH2NbuY0 DmZHXmwmH8E2gR8AwyjWHFvGOR2X5U0jH/7zd6KefmBj79FGwpAcCNIG1I8QZWkW x5PyOjHpLI3HklsLT5XQE72z5aX09KngUqWzeiE20EHNlPeaAg3YWFDQxDCp8g2K ufCF9N52DJqsZWJE/ChoSc6IpzFS5hEeUUkEsmT+M3Ja+ZWszjyvmMFlqmRz0QrE iww7gPfkEWZ/UnIi2AOn7SsYGu3GuOgngH9zSGluSZ5D7hfsyYyBPL74/bceFKCR +RpVxYb/mWgejIHk2eDTb8ej/a1SdgI6xVTpvpYP0s/aFfIg1MKHdX6I6vR5534H BCQq+B6awRudz1CpMqo8B/1o+tQ4TYBzdPL0tzho20yuViKygaYSGJA3bYiR0v7D 0zG2Gej9A/jaMQOQ1P3DozTxxRBjLOueLa0+t7N9FUhTVOnjEnNxkN8cbUXemlKn +Qj30cc54BJ6DdPbczEsqUmalKECfb/xONzeBJbYvopZpp7kaSuBizvGP9cf0yXj BtLyXVB5FaTH2xg1x7lr5B0RINOJlD3e5OIznpkyqeOng5E67+DTZIpE3CteWvJU taoDX4/tmru1gKI557uC =O5A2 -----END PGP SIGNATURE----- --V7BlxAaPrdhzdIM1-- From owner-freebsd-stable@freebsd.org Fri Jul 24 01:16:03 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A4FA9A80DE for ; Fri, 24 Jul 2015 01:16:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 640421237 for ; Fri, 24 Jul 2015 01:16:03 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t6O1FxEU010502 for ; Thu, 23 Jul 2015 18:16:05 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <20150724010003.GO84931@FreeBSD.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> <55B18CA8.1020909@sorbs.net>, <20150724010003.GO84931@FreeBSD.org> From: "Chris H" Subject: Re: 10.2-Beta i386..what's wrong..? Date: Thu, 23 Jul 2015 18:16:05 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 01:16:03 -0000 On Fri, 24 Jul 2015 01:00:03 +0000 Glen Barber wrote .. > FreeBSD kernel grew since 10.1-RELEASE, so this is not unexpected. Not trying to hijack the thread, or anything. But on that note; does FreeBSD keep a graph, or anything that indicates kernel [size] over major versions? I'm sure I'm not the only one that would find this interesting. :) --Chris > > Glen From owner-freebsd-stable@freebsd.org Fri Jul 24 02:27:33 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7F49A9A8A6B for ; Fri, 24 Jul 2015 02:27:33 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mta1.riverwillow.net.au (mta1.riverwillow.net.au [IPv6:2001:8000:1000:1801::3001]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mta1.riverwillow.net.au", Issuer "Riverwillow 2014 CA Root Certificate" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A8F491CB2 for ; Fri, 24 Jul 2015 02:27:32 +0000 (UTC) (envelope-from john.marshall@riverwillow.com.au) Received: from mail1.riverwillow.net.au (mail1.riverwillow.net.au [IPv6:2001:8000:1000:1801:0:0:0:4001]) by mta1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPS id t6O2RPaW047861 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 24 Jul 2015 12:27:25 +1000 (AEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=riverwillow.com.au; s=mta1002; t=1437704845; bh=P8qJNZDn7gERnkvyl7Z0NDkjsozBs8rOV7SxlfLa5jc=; h=Date:From:To:Subject; b=ubVrBzC+ftp1DCU7MYzej2fd6iP5PBbW1W2eCL4Wh3HoDpEevPM8dNhmLIPYTfuG/ V6JyqB4xkE0uceotjiUonrYqB94W0tlVxPhI6oLpzjTbWetXDXl8RW7bXwQNjNDg4H EMv3zGbrEUB+65mt08GRi3cjLz082HUPDq3pIvW8= Received: from rwpc16.gfn.riverwillow.net.au (rwpc16.gfn.riverwillow.net.au [IPv6:2001:8000:1000:18e1:ae87:a3ff:fe04:b351]) (authenticated bits=56) by mail1.riverwillow.net.au (8.15.2/8.15.2) with ESMTPSA id t6O2RHwD047859 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Fri, 24 Jul 2015 12:27:20 +1000 (AEST) Date: Fri, 24 Jul 2015 12:27:17 +1000 From: John Marshall To: freebsd-stable@freebsd.org Subject: 10.2-BETA2 patch etc/ntp.conf to enable ntpd pool client functionality Message-ID: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> Mail-Followup-To: freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MGYHOYXEY6WxJCY8" Content-Disposition: inline OpenPGP: id=A29A84A2; url=http://pki.riverwillow.com.au/pgp/johnmarshall.asc User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 02:27:33 -0000 --MGYHOYXEY6WxJCY8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have submitted a patch to the distributed ntp.conf to enable ntpd pool client functionality. This was not possible in the ancient version of ntpd shipped with FreeBSD releases over the past several years. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201803 Essentially this gives you a larger set of DYNAMIC servers from the pool. If ntpd decides one of the configured servers has become unreliable it will drop it and configure a new one. Also, there is a 'restrict source' command which provides template access restrictions for upstream servers. When a server is dynamically configured, a dynamic restrict entry is created for it from the 'restrict source' template. When a server is dynamically removed, its 'restrict' entry is also removed. This is the result on a 10.2-BETA2 (r285783) server. rwsrv02> ntpq -np remote refid st t when poll reach delay offset jit= ter =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=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D 0.freebsd.pool. .POOL. 16 p - 64 0 0.000 0.000 0.= 004 1.freebsd.pool. .POOL. 16 p - 64 0 0.000 0.000 0.= 004 2.freebsd.pool. .POOL. 16 p - 64 0 0.000 0.000 0.= 004 +125.255.139.115 130.194.1.96 2 u 27 128 377 43.168 -5.505 0.= 924 +203.23.237.200 203.35.83.242 2 u 26 128 377 29.877 -4.786 0.= 749 -121.0.0.42 23.31.237.112 3 u 212 256 377 46.560 -2.756 5.= 783 *54.252.165.245 202.21.137.10 2 u 25 128 377 30.060 -4.859 0.= 783 -2001:418:3ff::1 204.123.2.72 2 u 165 256 377 173.324 -1.592 1.= 651 -2001:df0:fe:2:: 130.102.2.123 3 u 106 256 377 44.177 4.080 3.= 690 +130.102.2.123 216.218.254.202 2 u 20 128 377 46.288 -4.332 1.= 416 The same server running an un-patched ntp.conf looks like this. rwsrv02> ntpq -np remote refid st t when poll reach delay offset jit= ter =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=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D *54.252.165.245 202.21.137.10 2 u 32 64 17 31.100 -7.764 3.= 887 +202.127.210.37 130.102.2.123 3 u 32 64 17 40.181 2.001 2.= 074 +2001:df0:fe:2:: 130.102.2.123 3 u 32 64 17 45.974 2.414 2.= 502 --=20 John Marshall --MGYHOYXEY6WxJCY8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWxooUACgkQw/tAaKKahKJ9DQCfXM+vKBd0uJq1GeMwEdDvx9hV wd8AoMK1auxlauaFmywQYcQVaw0Sw6sS =UcVr -----END PGP SIGNATURE----- --MGYHOYXEY6WxJCY8-- From owner-freebsd-stable@freebsd.org Fri Jul 24 05:20:01 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A784B9A8733 for ; Fri, 24 Jul 2015 05:20:01 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 843FA1163 for ; Fri, 24 Jul 2015 05:20:01 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: by mailman.ysv.freebsd.org (Postfix) id 8104C9A8731; Fri, 24 Jul 2015 05:20:01 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FAA19A8730 for ; Fri, 24 Jul 2015 05:20:01 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [IPv6:2a01:e0c:1:1599::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3BBDA1160; Fri, 24 Jul 2015 05:20:00 +0000 (UTC) (envelope-from mazhe@alkumuna.eu) Received: from yggdrasil.alkumuna.eu (unknown [IPv6:2a01:e35:8a74:6e70:232:36ff:fe5c:3a87]) by smtp1-g21.free.fr (Postfix) with ESMTPS id EBE6F940024; Fri, 24 Jul 2015 07:19:55 +0200 (CEST) Received: from freedom ([192.168.10.100]) (authenticated bits=0) by yggdrasil.alkumuna.eu (8.14.9/8.14.9) with ESMTP id t6O5JXMK012104 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 24 Jul 2015 07:19:39 +0200 (CEST) (envelope-from mazhe@alkumuna.eu) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=alkumuna.eu; s=default; t=1437715179; bh=nV6USXG35bLwRAOX2/z0z14mKLyYbWc99rM2cTaKktM=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=OB7PinW3C2OKGzZOg14+KRXr55FEmyvPbpOpL4eplIh9ZtYAbKZWItnpW5Ini5zJ4 jZjnwDv+fcTuvQI3DSNKTUkHjHOO660F7f0UNhhG+G9c3pMN4dNkQfPEDM/QqsiILI Sxtc7DAzCQ9zBlYdPTDSFx8VtGBwGWO77IMpaS/s= Date: Fri, 24 Jul 2015 07:19:17 +0200 From: Matthieu Volat To: Don Lewis Cc: stable@FreeBSD.org Subject: Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? Message-ID: <20150724071917.6a1fd3a3@freedom> In-Reply-To: <201507202103.t6KL31mb092619@gw.catspoiler.org> References: <201507202103.t6KL31mb092619@gw.catspoiler.org> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; amd64-portbld-freebsd10.1) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; boundary="Sig_/+pliA81zQ7ABpmLZj5QRJlz"; protocol="application/pgp-signature" X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on yggdrasil.alkumuna.eu X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 05:20:01 -0000 --Sig_/+pliA81zQ7ABpmLZj5QRJlz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Mon, 20 Jul 2015 14:03:01 -0700 (PDT) Don Lewis wrote: > Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, > which use clang as their base compiler and don't have gcc in base by > default, the math/scilab port uses clang for cc and c++ compilation, but > finds /usr/include/omp.h (and links to libgomp from lang/gcc). The > build succeeds, but I suspect this may not run properly. Does it mean the door to an openmp-enabled cc in base is closed? I'm not fond of lang/gcc as openmp "provider": if a port use c++, it will c= ause linkage headaches with libc++ (I never was able to have graphics/darkt= able working, for example). --=20 Matthieu Volat --Sig_/+pliA81zQ7ABpmLZj5QRJlz Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlWxytUACgkQ+ENDeYKZi36GTQCfYvweHOE4Cm8wHQm5ehrL0yVi LKIAnj0oVWewB9hA8CJID6ThCdVcDBzM =5oNK -----END PGP SIGNATURE----- --Sig_/+pliA81zQ7ABpmLZj5QRJlz-- From owner-freebsd-stable@freebsd.org Fri Jul 24 06:59:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFBDF9A7003 for ; Fri, 24 Jul 2015 06:59:11 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id 917161EA7; Fri, 24 Jul 2015 06:59:10 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 7C856929A514; Fri, 24 Jul 2015 08:58:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id 1L35-BkrEV0F; Fri, 24 Jul 2015 08:58:14 +0200 (CEST) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 98A6D929A4FA; Fri, 24 Jul 2015 08:58:14 +0200 (CEST) Received: by beast.freibergnet.de (Postfix, from userid 201) id 128074B783C; Fri, 24 Jul 2015 08:58:14 +0200 (CEST) Date: Fri, 24 Jul 2015 08:58:14 +0200 From: Holm Tiffe To: Glen Barber Cc: freebsd-stable Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724065814.GB11640@beast.freibergnet.de> Mail-Followup-To: Holm Tiffe , Glen Barber , freebsd-stable References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150724004343.GM84931@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 06:59:12 -0000 Glen Barber wrote: > On Thu, Jul 23, 2015 at 08:42:44PM -0400, Brandon Allbery wrote: > > On Thu, Jul 23, 2015 at 8:40 PM, Mark Linimon wrote: > > > > > zfs is a resource hog. i386 is not able to handle the demand as well > > > as amd64. > > > > > > > Even amd64 is no guarantee. I installed one of the Illumos spinoffs on a > > 2GB amd64 netbook (they mostly force zfs). I think it lasted 2 days before > > the kernel panics started. > > > > Even on amd64, you need to tune the system with less than 4GB RAM. > > Glen > ..interrestingly people here seem to focus my problem to ZFS.. but my problem was to build an raid over 4 disks on my old i386 machine and that failed with 2 different approaches. I'm accepting that ZFS is a too big thing for the i386 architecture and I possibly should leave it alone on that machine. But my 2nd try with gvinum failed also ...why? In the meantime I've set up the first two disks to a geom_mirror and installed 2x swap and a 66G ufs on the mirror, successfully installed 10.2-Beta, pulled the sources with svn and rebuild the entire world and a kernel yesterday. That worked flawlessly. So the hardware is out of the question here. It seems that geom_vinum is broken and it is broken on 9.3 10.1 and 10.2-Beta. There isn't an other possibility anymore. Can someone please confirm this with a similar machine? Proably I could atach an IDE disk and move the new build system to it to give ZFS a 2nd try on the 4 SCSI Disks to prove if something changed n the meantime or if a kernel with KSTACK_PAGES=4 would fix the ZFS problem. I had running gvinum and gmirror on that machine in the past up to 8.4-stable. It seems that we've lost this possibility now.. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, info@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Fri Jul 24 07:03:34 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DBE5C9A71F7 for ; Fri, 24 Jul 2015 07:03:34 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id 935A91454; Fri, 24 Jul 2015 07:03:34 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 6EF66929B069; Fri, 24 Jul 2015 09:02:47 +0200 (CEST) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id kf0lElkZZxlc; Fri, 24 Jul 2015 09:02:45 +0200 (CEST) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id D28C5929A4FA; Fri, 24 Jul 2015 09:02:45 +0200 (CEST) Received: by beast.freibergnet.de (Postfix, from userid 201) id 4C5954B783C; Fri, 24 Jul 2015 09:02:45 +0200 (CEST) Date: Fri, 24 Jul 2015 09:02:45 +0200 From: Holm Tiffe To: Glen Barber Cc: freebsd-stable Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724070245.GC11640@beast.freibergnet.de> Mail-Followup-To: Holm Tiffe , Glen Barber , freebsd-stable References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150724004939.GN84931@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 07:03:35 -0000 Glen Barber wrote: > On Thu, Jul 23, 2015 at 07:44:43PM -0500, Mark Linimon wrote: > > On Fri, Jul 24, 2015 at 12:43:43AM +0000, Glen Barber wrote: > > > Even on amd64, you need to tune the system with less than 4GB RAM. > > > > The only correct answer to "how much RAM do you need to run ZFS" is > > "always more" AFAICT. > > > > There's a bit more to it than that. You *can* successfully run amd64 > ZFS system with certain tunings (vfs.kmem_max IIRC), but you also need > to adjust things like disabling prefetching with less than 4GB RAM > (accessible to the OS). > > So yeah, "more RAM" is always a thing in this playing field. > > Glen > ...more RAM? Always more RAM? Reality check please, this is an i386 Machine with 2 Gbytes. It has two of 3 sockets polluted with RAM Modules (1G), there is not that much Space to give it more RAM. i386 is a supported architecture as far as I know, ok it where nice to have in i386 with 8 Gigs of RAM but there are not much motherboards out here that would support this.. This remebers me to microsofts attemts to write Software, always more RAM and more CPU to fasten up endless loops.. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, info@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Fri Jul 24 07:20:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E5AB9A75A4 for ; Fri, 24 Jul 2015 07:20:58 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0DDBE1CC1 for ; Fri, 24 Jul 2015 07:20:58 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZIXHo-000Geq-6y; Fri, 24 Jul 2015 10:20:52 +0300 Date: Fri, 24 Jul 2015 10:20:52 +0300 From: Slawa Olhovchenkov To: d@delphij.net Cc: Stari Karp , freebsd-stable@freebsd.org Subject: Re: freebsd downgrade Message-ID: <20150724072052.GF43740@zxy.spb.ru> References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B17DEB.6070302@delphij.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 07:20:58 -0000 On Thu, Jul 23, 2015 at 04:51:07PM -0700, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 07/23/15 16:21, Stari Karp wrote: > > Hi! > > > > I had a problems with FreeBSD 10.2-BETA2. I used freebsd-update > > ugrade and update FreeBSD 10.1-RELEASE. Is it possible to downgrade > > BETA2 to 10.1-RELEASE with freebsd-update upgrade -r 10.1-RELEASE, > > please? > > It's not supported (because you may be running binaries that depends > on new kernel). > > What kind of problems did you have? Please let re@ know so we can get > them fixed. For me -- degradate network performance, about 30%. I am do verification now, by downgrading kernel. From owner-freebsd-stable@freebsd.org Fri Jul 24 07:43:15 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBE1C9A7A4B for ; Fri, 24 Jul 2015 07:43:15 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "anubis.delphij.net", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BF0FC186F; Fri, 24 Jul 2015 07:43:15 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from Xins-MBP.home.us.delphij.net (unknown [IPv6:2601:646:8f00:8a91:2d46:ee4:b3f2:e3c6]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by anubis.delphij.net (Postfix) with ESMTPSA id C7BB21CAAA; Fri, 24 Jul 2015 00:43:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1437723793; x=1437738193; bh=UwHWTcdD2wJmhoecQya4GUhPkAMDaMGphshxR0P9J60=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=3wYfdhIwa1yFNNyQ4Cth/0c98U5sgLgZtG9RAhG8wRk9G5cqoREAN7T6Q6FGZ3fSA 65W3bjp34WLKjaHSjzl8mzfBsNWgslcdImNVv916CXA9GoO6zBnWveJxeYconGCqkF kv1zBYTfTqd8DlW1PYUsQa1JnPZSDNVmbvtJ4Qwo= Message-ID: <55B1EC8F.7050304@delphij.net> Date: Fri, 24 Jul 2015 00:43:11 -0700 From: Xin Li User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: Slawa Olhovchenkov , d@delphij.net CC: freebsd-stable@freebsd.org, re@FreeBSD.org Subject: Re: freebsd downgrade References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> <20150724072052.GF43740@zxy.spb.ru> In-Reply-To: <20150724072052.GF43740@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 07:43:16 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 7/24/15 00:20, Slawa Olhovchenkov wrote: > On Thu, Jul 23, 2015 at 04:51:07PM -0700, Xin Li wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 >> >> On 07/23/15 16:21, Stari Karp wrote: >>> Hi! >>> >>> I had a problems with FreeBSD 10.2-BETA2. I used >>> freebsd-update ugrade and update FreeBSD 10.1-RELEASE. Is it >>> possible to downgrade BETA2 to 10.1-RELEASE with freebsd-update >>> upgrade -r 10.1-RELEASE, please? >> >> It's not supported (because you may be running binaries that >> depends on new kernel). >> >> What kind of problems did you have? Please let re@ know so we >> can get them fixed. > > For me -- degradate network performance, about 30%. I am do > verification now, by downgrading kernel. What kind of workload and what NIC are you using? Cheers, -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVseyOAAoJEJW2GBstM+nsn5YP/jjX9IM2T7wQ8p5skZDvA5e+ e/dZ+IWKsqOIh612MyXfYbMdHbKakXdMP8K2rU6aNQmTinArSbC/xhUPXnA7029y Xz4TLTyb2y/J1oNFTU7saSnv5CeB8n/oDGxCISDqJPZDK9rypBjO7r3kMP9OLc5R c9Qtd38i2mdH3oWHbDeonBNaJ5YQ32zB5nGWEMpxFc2xQU2GK37dx4xjCJdx3L+1 WS+s2FJdWXCsclE12luHiGjD1hlIIS4yLZhSgLUy9i+rD4Zn6VOF7QvwCIAbjD8h kpZDt9YcqJy7y/gZu2iFa12nIguY9Z6pmPHu8yy/lGztfmspUWnmDspYnBhDJyoi GHrCji5O7St8w1MCUPYPsE/crvcel16FA3W1yCmYtmzX+HyEjcuqNY41vN3WqkCg thYyJxS5IVSXHFR3wbfsNM3WlG6pREE0uzjqo4rbzxRNPGHzsmoD8ImOUa3pKjgP XwgPSv8J7I4uskW6isDWuB5GBmsPk4PqZfUWvnCqYmG77HX5sl0ct+gxQQ+b6sAl 6I2FYflvrvexRhxDMc+gjoArNDOJhSVQY/fqswQXdsPYdIQnhmKLCX+G3ZOx0cho uYN6Qf6bqcSAcwKZeRI5LAOEc1XpqEo8HhxkwKgmC7m3SWJs35m9+yom7PlPdyM7 vx/huCTRA26XXuNAxqJF =Mhdf -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Fri Jul 24 07:50:13 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A79D49A7C46 for ; Fri, 24 Jul 2015 07:50:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 56B7E1E7D; Fri, 24 Jul 2015 07:50:13 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZIXkA-000HHR-Qv; Fri, 24 Jul 2015 10:50:10 +0300 Date: Fri, 24 Jul 2015 10:50:10 +0300 From: Slawa Olhovchenkov To: Xin Li Cc: d@delphij.net, re@FreeBSD.org, freebsd-stable@freebsd.org Subject: Re: freebsd downgrade Message-ID: <20150724075010.GG43740@zxy.spb.ru> References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> <20150724072052.GF43740@zxy.spb.ru> <55B1EC8F.7050304@delphij.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B1EC8F.7050304@delphij.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 07:50:13 -0000 On Fri, Jul 24, 2015 at 12:43:11AM -0700, Xin Li wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > > > On 7/24/15 00:20, Slawa Olhovchenkov wrote: > > On Thu, Jul 23, 2015 at 04:51:07PM -0700, Xin Li wrote: > > > >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 > >> > >> On 07/23/15 16:21, Stari Karp wrote: > >>> Hi! > >>> > >>> I had a problems with FreeBSD 10.2-BETA2. I used > >>> freebsd-update ugrade and update FreeBSD 10.1-RELEASE. Is it > >>> possible to downgrade BETA2 to 10.1-RELEASE with freebsd-update > >>> upgrade -r 10.1-RELEASE, please? > >> > >> It's not supported (because you may be running binaries that > >> depends on new kernel). > >> > >> What kind of problems did you have? Please let re@ know so we > >> can get them fixed. > > > > For me -- degradate network performance, about 30%. I am do > > verification now, by downgrading kernel. > > What kind of workload and what NIC are you using? Chelsio T580-LP-CR, http serving. r276179 can utilise 40Gbit, r281264 -- only 28Gbit. From owner-freebsd-stable@freebsd.org Fri Jul 24 08:54:26 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60EE09A8E07 for ; Fri, 24 Jul 2015 08:54:26 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id EC80A1D21 for ; Fri, 24 Jul 2015 08:54:25 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from ox-dell39.ox.adestra.com (no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.2/8.15.2) with ESMTPSA id t6O8orEN093738 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 24 Jul 2015 09:51:07 +0100 (BST) (envelope-from matthew@freebsd.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=freebsd.org DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t6O8orEN093738 Authentication-Results: smtp.infracaninophile.co.uk/t6O8orEN093738; dkim=none reason="no signature"; dkim-adsp=none; dkim-atps=neutral X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged) claimed to be ox-dell39.ox.adestra.com Message-ID: <55B1FC6C.8080301@freebsd.org> Date: Fri, 24 Jul 2015 09:50:52 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 10.2-Beta i386..what's wrong..? References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724065814.GB11640@beast.freibergnet.de> In-Reply-To: <20150724065814.GB11640@beast.freibergnet.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="pAOR5pN2WO875VN76ogWqaedsvb0GVO29" X-Virus-Scanned: clamav-milter 0.98.7 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 08:54:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pAOR5pN2WO875VN76ogWqaedsvb0GVO29 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 07/24/15 07:58, Holm Tiffe wrote: > ..interrestingly people here seem to focus my problem to ZFS.. but my > problem was to build an raid over 4 disks on my old i386 machine and th= at > failed with 2 different approaches. >=20 > I'm accepting that ZFS is a too big thing for the i386 architecture > and I possibly should leave it alone on that machine. >=20 > But my 2nd try with gvinum failed also ...why? I've had success using a combination of gstripe and gmirror to create a RAID10 over 4 drives: % gstripe status Name Status Components stripe/st0 UP mirror/gm2 mirror/gm1 % gmirror status Name Status Components mirror/gm2 COMPLETE da0 (ACTIVE) da1 (ACTIVE) mirror/gm1 COMPLETE da2 (ACTIVE) da3 (ACTIVE) This is a separate data area though -- system boots from some different drives. I can't remember if it is possible to boot from a gstripe. Cheers, Matthew --pAOR5pN2WO875VN76ogWqaedsvb0GVO29 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVsfxsAAoJEABRPxDgqeTnULgP/imNVH6fmgRaVK9M9WXGSIpe Vf+p/urDjh/EM6aFiwsQpudGN9OEjnEMcJw5m2CaWQ1wzhc2D8QZi1lh+Bkq2EgW 7No/fu+afw8yGIboW1P6ce85g7ZrNfLXNdll0pBJ6492boAZ3kVILjPMzX6+H7qF 4jdEvBwZrnywj0m1tAo08dqDLvzqyzDDqypXXfYmjRrtThZsu063CWwWOKgHqkMG PFW8b9Wo7Y03oS0E95NobsIjOoqSnCMdSGnideL7SOgfHnoIpW/iK/VXWOAddO/9 vbd/j+DUc49+49z5foDdVsm6cdC1Eei4wEqwsW2oW6uZ74NIMFCm8/4aJCTIYufD MEWsCg3o+mR3ScfQmHn80p4Yiucc0+20EMR1xFWMfB2DHWiMXhGWor3otpLaL5Rj J/nlUlYsEa7H0loFm3+O3tZjzs+6VRX2mY4CmJsnJXn7K5v9+ZV05RHzQs1FFMNv 4Qy6Vf6U5wPN+kTi+vbB+kMDobAaDw/vVyg/Uiz7ZYyLO3Vmn2yYy+Dnjp0hOZLr GhgrkAy6vQ9iF8xjMirYbYDNGKTSILJ/EbbEbKH7cHgZXaMQ2GNUzmC5HdkENc7p C/0Mwl4QaIzI6bK6fpJ0PrXuJruST0wRP6lfPAt217XSLgRYTquPrRzm0IGAn0rb ln6A72WfgH7sC8yxIpnl =AYXD -----END PGP SIGNATURE----- --pAOR5pN2WO875VN76ogWqaedsvb0GVO29-- From owner-freebsd-stable@freebsd.org Fri Jul 24 08:55:10 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEC319A8E62 for ; Fri, 24 Jul 2015 08:55:09 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "infracaninophile.co.uk" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EF861E2E for ; Fri, 24 Jul 2015 08:55:09 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from ox-dell39.ox.adestra.com (no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged)) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.15.2/8.15.2) with ESMTPSA id t6O8t4vR094680 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Fri, 24 Jul 2015 09:55:04 +0100 (BST) (envelope-from matthew@freebsd.org) Authentication-Results: smtp.infracaninophile.co.uk; dmarc=none header.from=freebsd.org DKIM-Filter: OpenDKIM Filter v2.9.2 smtp.infracaninophile.co.uk t6O8t4vR094680 Authentication-Results: smtp.infracaninophile.co.uk/t6O8t4vR094680; dkim=none reason="no signature"; dkim-adsp=none; dkim-atps=neutral X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host no-reverse-dns.metronet-uk.com [85.199.232.226] (may be forged) claimed to be ox-dell39.ox.adestra.com Message-ID: <55B1FD67.3000005@freebsd.org> Date: Fri, 24 Jul 2015 09:55:03 +0100 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: 10.2-Beta i386..what's wrong..? References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724065814.GB11640@beast.freibergnet.de> In-Reply-To: <20150724065814.GB11640@beast.freibergnet.de> Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="APlveX7wQftnp7WjfNsNkbJjfBRaR70av" X-Virus-Scanned: clamav-milter 0.98.7 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DCC_CHECK autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 08:55:10 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --APlveX7wQftnp7WjfNsNkbJjfBRaR70av Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 07/24/15 07:58, Holm Tiffe wrote: > ..interrestingly people here seem to focus my problem to ZFS.. but my > problem was to build an raid over 4 disks on my old i386 machine and th= at > failed with 2 different approaches. >=20 > I'm accepting that ZFS is a too big thing for the i386 architecture > and I possibly should leave it alone on that machine. >=20 > But my 2nd try with gvinum failed also ...why? I've had success using a combination of gstripe and gmirror to create a RAID10 over 4 drives: % gstripe status Name Status Components stripe/st0 UP mirror/gm2 mirror/gm1 % gmirror status Name Status Components mirror/gm2 COMPLETE da0 (ACTIVE) da1 (ACTIVE) mirror/gm1 COMPLETE da2 (ACTIVE) da3 (ACTIVE) This is a separate data area though -- system boots from some different drives. I can't remember if it is possible to boot from a gstripe. Cheers, Matthew --APlveX7wQftnp7WjfNsNkbJjfBRaR70av Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIbBAEBCgAGBQJVsf1nAAoJEABRPxDgqeTnjvAP9RMlof1Sh75jYZYws9Y5w5jj yu90s6MwsJYKYK7XhwdX43eIoWQYwLMmxul+IyzbvAJZdEpBD2jux3pHhRQucGCK R/3b1BnysW91Y2njGLZPfdSyyxIMf8+F2lfisVS1G8lpXq21pQlwqVyv8G10qNZv 2ynSeC3paQ6GrL3nGZ3pxTjpj5X6Q/TLytccmAII+OHXKd/m0oA34lC9qKnR3NMP uqcF6+9u30OdocVc7kz+55wjqDHv6nYfUWZLghEIX8wN7OcYK+lQJR3R90g0UQnL FQuGdCTLjlqKwVVC+rhjroiw0LCaHIot165wfDNp4MwhHD9VM1pDjtksbMRHnnRK hPbhvm1ItPPOUf/+aLl+5+Ff1E1rloLND3JuQQnFPCnJGeid5JJnZ2D/QP5B1UBw cSmL8UNp/HSDKNboo/5cLxYksV1pOT/W2XrSjz5jo6Vny+DEeUoqMbQvaouFvZlw 43HQ5MUMMDrfIpnSem9Lwfe3ablKbofQaRavae6P9jmuaGkzLH31SW1P8QxbLmvm FpWp0T266VVEi3IAAcQXgD3tMZCBBbDpftYaXeDk3mxvBs5xti91qUvKQQ0hAtqz HAHPJN3prdtiJD76lwn7SdqlMPrrRaoqR8xf3MBDCgicwwgyrLX/rHdza0Kl/EKw lgS7Aab9LJYW3p7qpKs= =wdSF -----END PGP SIGNATURE----- --APlveX7wQftnp7WjfNsNkbJjfBRaR70av-- From owner-freebsd-stable@freebsd.org Fri Jul 24 09:09:58 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E3BE9A992D for ; Fri, 24 Jul 2015 09:09:58 +0000 (UTC) (envelope-from ferdinand.goldmann@jku.at) Received: from emailsecure.uni-linz.ac.at (emailsecure.uni-linz.ac.at [140.78.3.66]) by mx1.freebsd.org (Postfix) with ESMTP id 2866310AC for ; Fri, 24 Jul 2015 09:09:57 +0000 (UTC) (envelope-from ferdinand.goldmann@jku.at) Received: from dyn-ant67.edvz.uni-linz.ac.at (dyn-ant67.edvz.uni-linz.ac.at [140.78.6.67]) by emailsecure.uni-linz.ac.at (Postfix) with ESMTPSA id 0B5BFFEBCD for ; Fri, 24 Jul 2015 11:02:18 +0200 (CEST) From: Ferdinand Goldmann Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Subject: local_unbound & chroot Message-Id: <5B0561C3-A820-4DB7-9C2B-5B1E90777AE7@jku.at> Date: Fri, 24 Jul 2015 11:02:18 +0200 To: freebsd-stable@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 09:09:58 -0000 Hello, I=92ve made the experience that enabling local_unbound does not play too = well if I am using a chroot=92ed unbound environment like chroot: = =93/var/unbound=94 in=20 the configuration file. In particular, there is no way to automatically mount a devfs and create = a link to the syslog socket. Also, the local_unbound service script expects a = PID file in /var/run/local_unbound.pid. So you have to create a symlink to=20 /var/unbound/unbound.pid as well. For the time being, I=92ve added a few lines to the local_unbound script = which do just that. But maybe it would be a good idea to offer this possibility via an = extra rc.conf variable, like local_unbound_chroot? Also, I=92ve noticed that it is not possible to raise the number of = threads above 1, as this seems to use more file descriptors than the builtin mini-event = library can handle. Kind regards, Ferdinand= From owner-freebsd-stable@freebsd.org Fri Jul 24 09:28:32 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 62FE99A9E6F for ; Fri, 24 Jul 2015 09:28:32 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by mx1.freebsd.org (Postfix) with ESMTP id 234531ED9; Fri, 24 Jul 2015 09:28:31 +0000 (UTC) (envelope-from holm@freibergnet.de) Received: from bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 9F106929A515; Fri, 24 Jul 2015 11:27:44 +0200 (CEST) X-Virus-Scanned: amavisd-new at freibergnet.de Received: from bmail.freibergnet.de ([46.4.195.14]) by bmail.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) (amavisd-new, port 10024) with LMTP id BcyjCVS9at4N; Fri, 24 Jul 2015 11:27:43 +0200 (CEST) Received: from beast.freibergnet.de (bmail.freibergnet.de [46.4.195.14]) by bmail.freibergnet.de (Postfix) with ESMTP id 084C8929A50E; Fri, 24 Jul 2015 11:27:43 +0200 (CEST) Received: by beast.freibergnet.de (Postfix, from userid 201) id 018D44B783C; Fri, 24 Jul 2015 11:27:42 +0200 (CEST) Date: Fri, 24 Jul 2015 11:27:42 +0200 From: Holm Tiffe To: Matthew Seaman Cc: freebsd-stable@freebsd.org Subject: Re: 10.2-Beta i386..what's wrong..? Message-ID: <20150724092742.GB24068@beast.freibergnet.de> Mail-Followup-To: Holm Tiffe , Matthew Seaman , freebsd-stable@freebsd.org References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724065814.GB11640@beast.freibergnet.de> <55B1FC6C.8080301@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <55B1FC6C.8080301@freebsd.org> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 09:28:32 -0000 Matthew Seaman wrote: > On 07/24/15 07:58, Holm Tiffe wrote: > > ..interrestingly people here seem to focus my problem to ZFS.. but my > > problem was to build an raid over 4 disks on my old i386 machine and that > > failed with 2 different approaches. > > > > I'm accepting that ZFS is a too big thing for the i386 architecture > > and I possibly should leave it alone on that machine. > > > > But my 2nd try with gvinum failed also ...why? > > I've had success using a combination of gstripe and gmirror to create a > RAID10 over 4 drives: > > % gstripe status > Name Status Components > stripe/st0 UP mirror/gm2 > mirror/gm1 > % gmirror status > Name Status Components > mirror/gm2 COMPLETE da0 (ACTIVE) > da1 (ACTIVE) > mirror/gm1 COMPLETE da2 (ACTIVE) > da3 (ACTIVE) > > This is a separate data area though -- system boots from some different > drives. I can't remember if it is possible to boot from a gstripe. > > Cheers, > > Matthew > gmirror is working for me too (as I already described), I've talking about gvinum here.., that's different. Regards, Holm -- Technik Service u. Handel Tiffe, www.tsht.de, Holm Tiffe, Freiberger Straße 42, 09600 Oberschöna, USt-Id: DE253710583 www.tsht.de, info@tsht.de, Fax +49 3731 74200, Mobil: 0172 8790 741 From owner-freebsd-stable@freebsd.org Fri Jul 24 09:35:28 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8AF259A812E for ; Fri, 24 Jul 2015 09:35:28 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: from mail.xtaz.uk (tao.xtaz.uk [IPv6:2001:8b0:202::10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 55FB615EE for ; Fri, 24 Jul 2015 09:35:28 +0000 (UTC) (envelope-from fbsd@xtaz.co.uk) Received: by mail.xtaz.uk (Postfix, from userid 1001) id C304E20AEE9B; Fri, 24 Jul 2015 10:35:25 +0100 (BST) Date: Fri, 24 Jul 2015 10:35:25 +0100 From: Matt Smith To: freebsd-stable@freebsd.org Subject: Re: 10.2-BETA2 patch etc/ntp.conf to enable ntpd pool client functionality Message-ID: <20150724093525.GA1257@xtaz.uk> Mail-Followup-To: Matt Smith , freebsd-stable@freebsd.org References: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 09:35:28 -0000 On Jul 24 12:27, John Marshall wrote: >I have submitted a patch to the distributed ntp.conf to enable ntpd pool >client functionality. This was not possible in the ancient version of >ntpd shipped with FreeBSD releases over the past several years. > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201803 > Thanks for this. But I would like to make some additional suggestions. There is no need to use multiple pools. You only need one. Pool works by using the minclock and maxclock values to work out how many peers it needs to add and keep track of. minclock is the minimum amount of * and + peers it should keep, and maxclock is the maximum amount of total peers including the actual pool itself. Also the local clock has been deprecated in favour of orphan mode. So I would suggest something like this instead: pool 0.freebsd.pool.ntp.org iburst tos minclock 3 maxclock 6 orphan 6 This will fire up a pool association and then add 5 peers from that pool and keep a minimum of 3 in * or + modes. If any become unreliable it will add more according to the min/maxclock values. For more info: http://support.ntp.org/bin/view/Support/OrphanMode http://lists.ntp.org/pipermail/questions/2010-April/026304.html -- Matt From owner-freebsd-stable@freebsd.org Fri Jul 24 10:11:12 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A71BB9A8B95 for ; Fri, 24 Jul 2015 10:11:12 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward4m.mail.yandex.net (forward4m.mail.yandex.net [IPv6:2a02:6b8:0:2519::3:13]) by mx1.freebsd.org (Postfix) with ESMTP id 5C5621D08 for ; Fri, 24 Jul 2015 10:11:12 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp4m.mail.yandex.net (smtp4m.mail.yandex.net [IPv6:2a02:6b8:0:2519::126]) by forward4m.mail.yandex.net (Yandex) with ESMTP id 13ABE23203E3; Fri, 24 Jul 2015 13:11:09 +0300 (MSK) Received: from smtp4m.mail.yandex.net (localhost [127.0.0.1]) by smtp4m.mail.yandex.net (Yandex) with ESMTP id B9302BE004B; Fri, 24 Jul 2015 13:11:09 +0300 (MSK) Received: by smtp4m.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id XjgDE4yaX9-B7c09LqK; Fri, 24 Jul 2015 13:11:08 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437732668; bh=1/Jkrm6nxVmBY3+dImcGjQcUXU4rscSqIr1Xx31C3qo=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=CW/3jg2GxpBLs4b6DrLFRvjCW2VjCf72xWndeRgWft2eXtWpyxbRMoTTytXMG2ThS HnZ2Y46vKk6kXZU7h5T5YhRIRbXDRg6tAR8KoT2sRXMczeVYl5X8mm7T1K8KSrifD3 yVL078SXorrDI1stC3sjGFZ97BRenc0CyQGx+iHs= Authentication-Results: smtp4m.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-ForeignMX: US Message-ID: <1437732664.80114.2.camel@yandex.com> Subject: Re: freebsd downgrade From: Stari Karp To: d@delphij.net Cc: freebsd-stable@freebsd.org Date: Fri, 24 Jul 2015 06:11:04 -0400 In-Reply-To: <55B17DEB.6070302@delphij.net> References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 10:11:12 -0000 On Thu, 2015-07-23 at 16:51 -0700, Xin Li wrote: > On 07/23/15 16:21, Stari Karp wrote: > > Hi! > > > > I had a problems with FreeBSD 10.2-BETA2. I used freebsd-update > > ugrade and update FreeBSD 10.1-RELEASE. Is it possible to downgrade > > BETA2 to 10.1-RELEASE with freebsd-update upgrade -r 10.1-RELEASE, > > please? > > It's not supported (because you may be running binaries that depends > on new kernel). > > What kind of problems did you have? Please let re@ know so we can get > them fixed. > > Cheers, I have a post in FreeBSD Stable maling list about my problem. A subject is: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 And I wrote: " Hi! I upgrade 10.1-RELEASE (amd64) with freebsd-update upgrade to FreeBSD 10.2-BETA2 #0 r285646: Fri Jul 17 01:09:28 UTC 2015 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 and now I have some problems: 1. VT module doesn't load. In /boot/loader.conf I have: kern.vty=vt but it doesn't work. If I manual loada module witk kldload radeonkms I got just black screen and nothing more. 2. Fireware external disk doesn't work either. In /boot/loader.conf I have sbp_load="YES" but it doesn't load. If I run kldload sbp it load and works. 3. The same is with web camera. cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. It works if I load with kldload. In /boot/loader.conf I have also loader_logo="beastie" which doesn't show picture in menu (it is default one). In /boot/device.hints I have also some hits which are for my sound card and it doesn't read them and sound doesn't work correct too. On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems." Thank you. From owner-freebsd-stable@freebsd.org Fri Jul 24 11:01:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 764729A99F6 for ; Fri, 24 Jul 2015 11:01:08 +0000 (UTC) (envelope-from michelle@sorbs.net) Received: from hades.sorbs.net (hades.sorbs.net [67.231.146.201]) by mx1.freebsd.org (Postfix) with ESMTP id 5985714A1; Fri, 24 Jul 2015 11:01:07 +0000 (UTC) (envelope-from michelle@sorbs.net) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from isux.com (firewall.isux.com [213.165.190.213]) by hades.sorbs.net (Oracle Communications Messaging Server 7.0.5.29.0 64bit (built Jul 9 2013)) with ESMTPSA id <0NRZ00IC3O7QGN00@hades.sorbs.net>; Fri, 24 Jul 2015 04:07:04 -0700 (PDT) Message-id: <55B21AF0.1030806@sorbs.net> Date: Fri, 24 Jul 2015 13:01:04 +0200 From: Michelle Sullivan User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.24) Gecko/20100301 SeaMonkey/1.1.19 To: Glen Barber Cc: herbert@oslo.ath.cx, Mark Linimon , freebsd-stable , Brandon Allbery , Jason Unovitch Subject: Re: 10.2-Beta i386..what's wrong..? References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> <55B18CA8.1020909@sorbs.net> <20150724010003.GO84931@FreeBSD.org> In-reply-to: <20150724010003.GO84931@FreeBSD.org> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 11:01:08 -0000 Glen Barber wrote: > On Fri, Jul 24, 2015 at 02:54:00AM +0200, Michelle Sullivan wrote: > >> >> Actually I'm quite sucessfully running zfs on i386 (in a VM) ... here's >> the trick (which leads me to suspect ARC handling as the problem) - when >> I get to 512M of kernel space or less than 1G of RAM available system >> wide, I export/import the zfs pool... Using this formula I have uptimes >> of months... I haven't yet tried the 'ARC patch' that was proposed >> recently... >> >> > > Which FreeBSD version is this? Things changed since 10.1-RELEASE and > what will be 10.2-RELEASE enough that I can't even get a single-disk ZFS > system (in VirtualBox) to boot on i386. During 10.1-RELEASE testing, > I only saw problems with multi-disk setup (mirror, raidzN), but the > FreeBSD kernel grew since 10.1-RELEASE, so this is not unexpected. > 9.2-i386 and 9.3-i386 - I don't run 10 on anything. -- Michelle Sullivan http://www.mhix.org/ From owner-freebsd-stable@freebsd.org Fri Jul 24 12:49:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A3B49A96BD for ; Fri, 24 Jul 2015 12:49:20 +0000 (UTC) (envelope-from freebsd@spam.lifeforms.nl) Received: from tau.lfms.nl (tau.lfms.nl [93.189.130.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DD7321C49 for ; Fri, 24 Jul 2015 12:49:19 +0000 (UTC) (envelope-from freebsd@spam.lifeforms.nl) Received: from sim.dt.lfms.nl (dt.lfms.nl [83.84.0.54]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by tau.lfms.nl (Postfix) with ESMTPS id 01047892C4; Fri, 24 Jul 2015 14:42:04 +0200 (CEST) Received: from [192.168.130.112] (borax.dt.lfms.nl [192.168.130.112]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by sim.dt.lfms.nl (Postfix) with ESMTPS id B7B169C090A1; Fri, 24 Jul 2015 14:42:03 +0200 (CEST) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\)) Subject: Re: freebsd downgrade From: Walter Hop In-Reply-To: <1437693686.78236.2.camel@yandex.com> Date: Fri, 24 Jul 2015 14:42:03 +0200 Cc: freebsd-stable@freebsd.org Message-Id: <4D753416-93CC-46C7-AE48-6841E4BC28EB@spam.lifeforms.nl> References: <1437693686.78236.2.camel@yandex.com> To: Stari Karp X-Mailer: Apple Mail (2.2102) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 12:49:20 -0000 > I had a problems with FreeBSD 10.2-BETA2. I used freebsd-update ugrade > and update FreeBSD 10.1-RELEASE. > Is it possible to downgrade BETA2 to 10.1-RELEASE with freebsd-update > upgrade -r 10.1-RELEASE, please? In my experience, downgrading with freebsd-update works fine, although I = only went back from 10.1 to 9.3, but arguably that=E2=80=99s a much = bigger jump. We=E2=80=99ve done it on around 40 machines over ssh. You = just have to skip the initial reboot, in order to stay in the new = kernel. Here is a blog post I wrote about it: = https://lifeforms.nl/20141224/downgrading-with-freebsd-update/ = I can=E2=80=99t guarantee that going back from 10.2 to 10.1 will work = too; there might be problems, but if you try it, let me know your = experiences and I=E2=80=99ll update the post. --=20 Walter Hop | PGP key: https://lifeforms.nl/pgp From owner-freebsd-stable@freebsd.org Fri Jul 24 12:57:55 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F28B19A9907 for ; Fri, 24 Jul 2015 12:57:55 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 871761140; Fri, 24 Jul 2015 12:57:55 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wibud3 with SMTP id ud3so64362589wib.1; Fri, 24 Jul 2015 05:57:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=9b6/bE70R+8gJkDXAy1tN4R3vJz4yFX2b4yMpVyitag=; b=cmVcxEoGILShgbwDhwLQ6lvQcExpoaWs3yVorwDMUPlkgiEBGyiw8seeTLVNtCPLmr I7hN0yYX72+dcxHE/Kyb3XIDSNIPyffXZKhAfSVSyLpSrSKG8iJN5vTYjan354hLVDeC 5cxLIw50klZssQy/J3LJenyJp84iE+D8sHgFFQS+Daz4Ho1rI07qsQ2xFQV7i/sXVp3B 09MR1XC93rc+ss1A5tJ9fWbyuyixka6veuUe1qB325kyDw9Dqvapr+RBTGzG9bn/vMM8 VAKC4wC4hZSeMDKOkSj8W9F7U41pWSAaZT9WwzTVl4kw8z5thew5k9IWf/T4NXXVERRe UD2A== MIME-Version: 1.0 X-Received: by 10.194.206.65 with SMTP id lm1mr26568288wjc.117.1437742674000; Fri, 24 Jul 2015 05:57:54 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Fri, 24 Jul 2015 05:57:53 -0700 (PDT) In-Reply-To: <20150724070245.GC11640@beast.freibergnet.de> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> <20150724070245.GC11640@beast.freibergnet.de> Date: Fri, 24 Jul 2015 08:57:53 -0400 Message-ID: Subject: Re: 10.2-Beta i386..what's wrong..? From: Brandon Allbery To: Holm Tiffe , Glen Barber , freebsd-stable Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 12:57:56 -0000 On Fri, Jul 24, 2015 at 3:02 AM, Holm Tiffe wrote: > ...more RAM? Always more RAM? For ZFS, yes. Stick to UFS otherwise. -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Fri Jul 24 13:02:51 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 798F49A9A9E for ; Fri, 24 Jul 2015 13:02:51 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCC5C15ED for ; Fri, 24 Jul 2015 13:02:50 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id t6OD2k2O023774; Fri, 24 Jul 2015 15:02:46 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 864BF87F; Fri, 24 Jul 2015 15:02:46 +0200 (CEST) Message-ID: <55B23775.70302@omnilan.de> Date: Fri, 24 Jul 2015 15:02:45 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Matt Smith , freebsd-stable@freebsd.org Subject: 10.2-BETA2 patch etc/ntp.conf, for upgraders utilizing ntpdc(8) [WAS: Re: 10.2-BETA2 patch etc/ntp.conf to enable ntpd pool client functionality] References: <20150724022717.GA61649@rwpc16.gfn.riverwillow.net.au> <20150724093525.GA1257@xtaz.uk> In-Reply-To: <20150724093525.GA1257@xtaz.uk> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig89BD30CEEB2CF0F2D3A0F8B9" X-Greylist: ACL 119 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Fri, 24 Jul 2015 15:02:46 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:02:51 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig89BD30CEEB2CF0F2D3A0F8B9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Bez=FCglich Matt Smith's Nachricht vom 24.07.2015 11:35 (localtime): > On Jul 24 12:27, John Marshall wrote: >> I have submitted a patch to the distributed ntp.conf to enable ntpd po= ol >> client functionality. This was not possible in the ancient version of= >> ntpd shipped with FreeBSD releases over the past several years. >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201803 >> Thank you. Hopefully this patch will be commited soon. I'd also like to make an additional, unrelated, suggestion, specific to 10.2 upgraders: --- ntp.conf.orig1 2015-07-24 14:54:23.378446000 +0200 +++ ntp.conf 2015-07-24 14:53:15.242509000 +0200 @@ -59,6 +59,12 @@ restrict 127.0.0.1 restrict ::1 =20 +# NTP mode 7 implementation-specific requests, as used by the deprecated= +# ntpdc(8) utility, are no longer processed by default (v4.2.8). +# Use ntpq(8) instead of ntpdc(8), or restore the old behaviour at the c= ost +# of additional security risks, depending on your 'restrict' options. +#enable mode7 + # # If a server loses sync with all upstream servers, NTP clients # no longer follow that server. The local clock can be configured I have been using ntpdc(8) for a very long time and unfortunately ignored ntpq(8) yet, so that it took me a significat ammount of time to find out why my 10-stable -> 10.2-Beta2 update suddenly stopped talking to me like I'd expect... Thanks, -Harry --------------enig89BD30CEEB2CF0F2D3A0F8B9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWyN3UACgkQLDqVQ9VXb8jXugCfaV+TRpLffcdH/h7fXukhtg0f WTYAn0ACG6sw3uBL6dTF5O/8Wy6xLT3I =3/98 -----END PGP SIGNATURE----- --------------enig89BD30CEEB2CF0F2D3A0F8B9-- From owner-freebsd-stable@freebsd.org Fri Jul 24 13:19:13 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 572749A9D92 for ; Fri, 24 Jul 2015 13:19:13 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D8DAA1C97; Fri, 24 Jul 2015 13:19:12 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id t6ODJA4P023897; Fri, 24 Jul 2015 15:19:10 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 95440883; Fri, 24 Jul 2015 15:19:10 +0200 (CEST) Message-ID: <55B23B4E.1080400@omnilan.de> Date: Fri, 24 Jul 2015 15:19:10 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Ian Lepore CC: Xin LI , freebsd-stable@freebsd.org Subject: Re: Will 10.2 also ship with a very stale NTP? References: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> <20150712032256.GB19305@satori.lan> <20150712050443.GA22240@server.rulingia.com> <20150712154416.b9f3713893fe28bfab1dd4d7@dec.sakura.ne.jp> <20150712184910.2d8d5f085ae659d5b9a2aba0@dec.sakura.ne.jp> <1436715703.1334.193.camel@freebsd.org> In-Reply-To: <1436715703.1334.193.camel@freebsd.org> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4A5B35E17751FBEE975CD82C" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Fri, 24 Jul 2015 15:19:11 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:19:13 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4A5B35E17751FBEE975CD82C Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Bez=FCglich Ian Lepore's Nachricht vom 12.07.2015 17:41 (localtime): > And let's all just hope that a week or two of testing is enough when > jumping a major piece of software forward several years in its > independent evolution. =85 > I wonder how many other such things could be lurking in 4.2.8, waiting > to be triggered by other peoples' non-stock configurations? We've =85 I'd like to report one, most likely an upstream problem: 'restrict' definitions in ntp.conf(5) no longer work with unqualified DNS= names. A line like "restrict time1 nomodify nopeer noquery notrap" results in: ntpd[1913]: line 7 column 7 syntax error, unexpected T_Time1 ntpd[1913]: syntax error in /etc/ntp.conf line 7, column 7 I've always been using unqualified hostnames with 'restrict', and since d= efining 'server' with unqualified hostname still works, this seems to be = a significant bug to me. People are forced to change 'restrict' definitio= ns, but not to also change other unqualified definitions, which potential= ly leads to misconfigurations, since intentionally matching definitions c= an now differ easily. Has anybody already noticed this problem? And any idea if upstream is awa= re? > On Sun, 2015-07-12 at 18:49 +0900, Tomoaki AOKI wrote: >> Wow! Thanks for your time and quick response. >> I'm looking forward to seeing it MFCed. :-) >> >> On Sun, 12 Jul 2015 08:56:26 +0000 >> Xin LI wrote: >> >>> I've spent some time on the MFC, the testing would still take some ti= me >>> (likely a day or two) and once that's finished I'll ask re@ for appro= val. Thanks, -Harry --------------enig4A5B35E17751FBEE975CD82C Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWyO04ACgkQLDqVQ9VXb8hsWgCgmN3OExFRm3VWixZXna9oA40x Px0An09FhqyzIFvgiQPmc1ZA7rctc+Jh =BMgA -----END PGP SIGNATURE----- --------------enig4A5B35E17751FBEE975CD82C-- From owner-freebsd-stable@freebsd.org Fri Jul 24 13:25:06 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1FDC09A9FA5 for ; Fri, 24 Jul 2015 13:25:06 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DCCED10ED for ; Fri, 24 Jul 2015 13:25:05 +0000 (UTC) (envelope-from bsd-lists@bsdforge.com) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t6ODP4bX094851 for ; Fri, 24 Jul 2015 06:25:10 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: In-Reply-To: <55B1FC6C.8080301@freebsd.org> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724065814.GB11640@beast.freibergnet.de>, <55B1FC6C.8080301@freebsd.org> From: "Chris H" Subject: Re: 10.2-Beta i386..what's wrong..? Date: Fri, 24 Jul 2015 06:25:10 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <777eeb0c2ccba4a2278525ad83b562bf@ultimatedns.net> Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:25:06 -0000 On Fri, 24 Jul 2015 09:50:52 +0100 Matthew Seaman wrote > On 07/24/15 07:58, Holm Tiffe wrote: > > ..interrestingly people here seem to focus my problem to ZFS.. but my > > problem was to build an raid over 4 disks on my old i386 machine and that > > failed with 2 different approaches. > > > > I'm accepting that ZFS is a too big thing for the i386 architecture > > and I possibly should leave it alone on that machine. > > > > But my 2nd try with gvinum failed also ...why? > > I've had success using a combination of gstripe and gmirror to create a > RAID10 over 4 drives: > > % gstripe status > Name Status Components > stripe/st0 UP mirror/gm2 > mirror/gm1 > % gmirror status > Name Status Components > mirror/gm2 COMPLETE da0 (ACTIVE) > da1 (ACTIVE) > mirror/gm1 COMPLETE da2 (ACTIVE) > da3 (ACTIVE) > > This is a separate data area though -- system boots from some different > drives. I can't remember if it is possible to boot from a gstripe. While it hasn't been since around the beginning of 8. I can confirm it's possible to boot from a gstripe(8). --Chris > > Cheers, > > Matthew From owner-freebsd-stable@freebsd.org Fri Jul 24 13:26:30 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CD28C9A9FFC for ; Fri, 24 Jul 2015 13:26:30 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4412411F6; Fri, 24 Jul 2015 13:26:30 +0000 (UTC) (envelope-from h.schmalzbauer@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id t6ODQSjw023979; Fri, 24 Jul 2015 15:26:28 +0200 (CEST) (envelope-from h.schmalzbauer@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 19C35886; Fri, 24 Jul 2015 15:26:28 +0200 (CEST) Message-ID: <55B23D03.5060604@omnilan.de> Date: Fri, 24 Jul 2015 15:26:27 +0200 From: Harald Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Ian Lepore CC: freebsd-stable@freebsd.org, Xin LI Subject: Re: Will 10.2 also ship with a very stale NTP? References: <20150710235810.GA76134@rwpc16.gfn.riverwillow.net.au> <20150712032256.GB19305@satori.lan> <20150712050443.GA22240@server.rulingia.com> <20150712154416.b9f3713893fe28bfab1dd4d7@dec.sakura.ne.jp> <20150712184910.2d8d5f085ae659d5b9a2aba0@dec.sakura.ne.jp> <1436715703.1334.193.camel@freebsd.org> <55B23B4E.1080400@omnilan.de> In-Reply-To: <55B23B4E.1080400@omnilan.de> X-Enigmail-Version: 1.1.2 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigF3EC2B9B91AD75FA713EDA2A" X-Greylist: ACL 119 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Fri, 24 Jul 2015 15:26:28 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:26:30 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF3EC2B9B91AD75FA713EDA2A Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Bez=FCglich Harald Schmalzbauer's Nachricht vom 24.07.2015 15:19 (localtime): > Bez=FCglich Ian Lepore's Nachricht vom 12.07.2015 17:41 (localtime): >> And let's all just hope that a week or two of testing is enough when >> jumping a major piece of software forward several years in its >> independent evolution. > =85 >> I wonder how many other such things could be lurking in 4.2.8, waiting= >> to be triggered by other peoples' non-stock configurations? We've > =85 > > I'd like to report one, most likely an upstream problem: > > 'restrict' definitions in ntp.conf(5) no longer work with unqualified D= NS names. > A line like > "restrict time1 nomodify nopeer noquery notrap" > results in: > ntpd[1913]: line 7 column 7 syntax error, unexpected T_Time1 > ntpd[1913]: syntax error in /etc/ntp.conf line 7, column 7 That report is not entirely true, sorry! It's only the case if the unqualified hostname is of type CNAME. With A or AAAA records, the problem doesn't occur. =85 > Has anybody already noticed this problem? And any idea if upstream is a= ware? =20 Any hints who to contact best? Thanks, -Harry --------------enigF3EC2B9B91AD75FA713EDA2A Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (FreeBSD) iEYEARECAAYFAlWyPQMACgkQLDqVQ9VXb8jCUwCfafGVoMDzFdy4fR7KC5hu41gU iQgAoJUWAHCY8sr31c5UNubhlw++he8I =wtGD -----END PGP SIGNATURE----- --------------enigF3EC2B9B91AD75FA713EDA2A-- From owner-freebsd-stable@freebsd.org Fri Jul 24 13:48:42 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F81F9A957F for ; Fri, 24 Jul 2015 13:48:42 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1.freebsd.org (Postfix) with ESMTP id 1D7541ED6 for ; Fri, 24 Jul 2015 13:48:41 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from msam.nabble.com (unknown [162.253.133.85]) by mbob.nabble.com (Postfix) with ESMTP id 17FAD11D50A5 for ; Fri, 24 Jul 2015 06:40:18 -0700 (PDT) Date: Fri, 24 Jul 2015 06:40:02 -0700 (MST) From: timp To: freebsd-stable@freebsd.org Message-ID: <1437745202428-6027559.post@n5.nabble.com> In-Reply-To: <1437602017.1621.5.camel@yandex.com> References: <1437602017.1621.5.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:48:42 -0000 Hi! > 1. VT module doesn't load. > In /boot/loader.conf I have: > kern.vty=vt > but it doesn't work. If I manual loada module witk kldload radeonkms I > got just black screen and nothing more. As I know it's not a module. And you can't load it. I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and have no problem. > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > and works. > 3. The same is with web camera. > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > It works if I load with kldload. > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > show picture in menu (it is default one). > > In /boot/device.hints I have also some hits which are for my sound card > and it doesn't read them and sound doesn't work correct too. > > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > Today I update with freebsd-update fetch and the problem exist. What if you load the previous kernel? Did you upgrade only kernel? What about world? Something's definitely wrong with your machine. I have % cat /boot/loader.conf zfs_load="YES" kern.geom.label.gptid.enable="0" kern.vty=vt hw.vga.textmode=1 cuse4bsd_load="YES" autoboot_delay="2" coretemp_load="YES" fuse_load="YES" kern.racct.enable=1 and it works. -- View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-10-1-RELEASE-to-FreeBSD-10-2-BETA2-tp6027186p6027559.html Sent from the freebsd-stable mailing list archive at Nabble.com. From owner-freebsd-stable@freebsd.org Fri Jul 24 13:54:33 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85B659A9750 for ; Fri, 24 Jul 2015 13:54:33 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [191.243.120.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39B7012D6 for ; Fri, 24 Jul 2015 13:54:32 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 712C830FC30 for ; Fri, 24 Jul 2015 10:44:16 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type :in-reply-to:references:subject:subject:to:mime-version :user-agent:from:from:date:date:message-id; s=dkim; t= 1437745454; x=1438609455; bh=D6hOIxU9OErriHGzkC29eFSn5HopXDQxrj1 xacL0GQo=; b=TpZYIaxr5mUfUx3CLmYXSMp3Blv5YS9Fi+0FeYR7YnyGW4IaGds e5E50KZELi+tVf7GXlxrG73sApX/JfHPviwfj7vEf0Egkrkn4TKIM3gyUN8/vbjR L38VeKr0pGOpxM5nVYusF09QrHaH3TcjWbiE51sv9vuyaP64RzikXlA4= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DzC7ycr6mfn0 for ; Fri, 24 Jul 2015 10:44:14 -0300 (BRT) Received: from [192.168.10.208] (unknown [186.193.54.69]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id 39C4E30FC2F; Fri, 24 Jul 2015 10:44:14 -0300 (BRT) Message-ID: <55B24142.7090001@bsdinfo.com.br> Date: Fri, 24 Jul 2015 10:44:34 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: "Alexander V. Chernikov" , FreeBSD Stable Mailing List Subject: Re: table with bug in ipfw References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> In-Reply-To: <1442671432126620@web6h.yandex.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 13:54:33 -0000 Hi Melifaro, Bug persists. (root@mail)[/usr/src]# ipfw table 22 list (root@mail)[/usr/src]# ipfw table 22 add 0.0.0.0/8 (root@mail)[/usr/src]# ipfw table 22 list ::/8 0 (root@mail)[/usr/src]# uname -a FreeBSD mail.stefaninogueira.com 10.2-PRERELEASE FreeBSD 10.2-PRERELEASE #1 r285832: Fri Jul 24 02:55:14 BRT 2015 root@mail.stefaninogueira.com:/usr/obj/usr/src/sys/K3AX amd64 :( On 20-05-2015 09:57, Alexander V. Chernikov wrote: > 19.05.2015, 03:22, "Marcelo Gondim" : >> Hi all, > Hi, >> I see that there is still the following bug in ipfw: >> >> # ipfw table 33 add 0.0.0.0/8 >> # ipfw table 33 list >> ::/8 0 >> >> and >> >> # ipfw table 33 add 255.255.255.255 >> # ipfw table 33 list >> ::/8 0 >> >> The IP 255.255.255.255 not appear but it's there. Look below: >> >> # ipfw table 33 add 255.255.255.255 >> ipfw: setsockopt(IP_FW_TABLE_XADD): File exists >> >> This is very ugly to see. As it was not fixed in 10.1, would be expected >> to 10.2? > It was fixed in -head but didn't get to -stable. I'll try to take a look soon. > >> Best regards, >> Gondim >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Fri Jul 24 14:10:54 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC6B99A901F for ; Fri, 24 Jul 2015 14:10:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7B6C81654; Fri, 24 Jul 2015 14:10:54 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZIdgb-000GF7-Fy; Fri, 24 Jul 2015 16:10:53 +0200 Date: Fri, 24 Jul 2015 16:10:53 +0200 From: Kurt Jaeger To: Marcelo Gondim Cc: "Alexander V. Chernikov" , FreeBSD Stable Mailing List Subject: Re: table with bug in ipfw Message-ID: <20150724141053.GH49099@home.opsec.eu> References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <55B24142.7090001@bsdinfo.com.br> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 14:10:54 -0000 Hi! > Bug persists. > > (root@mail)[/usr/src]# ipfw table 22 list > > (root@mail)[/usr/src]# ipfw table 22 add 0.0.0.0/8 > (root@mail)[/usr/src]# ipfw table 22 list > ::/8 0 Do you have a problem report for this in bugzilla ? I try to poke re@ -- pi@opsec.eu +49 171 3101372 5 years to go ! From owner-freebsd-stable@freebsd.org Fri Jul 24 14:11:52 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DFE489A90B2 for ; Fri, 24 Jul 2015 14:11:52 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E49B1A8D; Fri, 24 Jul 2015 14:11:52 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZIdhZ-000GFy-OB; Fri, 24 Jul 2015 16:11:53 +0200 Date: Fri, 24 Jul 2015 16:11:53 +0200 From: Kurt Jaeger To: Marcelo Gondim , FreeBSD Stable Mailing List , "Alexander V. Chernikov" Subject: Re: table with bug in ipfw Message-ID: <20150724141153.GI49099@home.opsec.eu> References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> <20150724141053.GH49099@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150724141053.GH49099@home.opsec.eu> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 14:11:53 -0000 Hi! > Do you have a problem report for this in bugzilla ? I try to poke re@ Found it: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200169 -- pi@opsec.eu +49 171 3101372 5 years to go ! From owner-freebsd-stable@freebsd.org Fri Jul 24 14:17:20 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBFA59A9523 for ; Fri, 24 Jul 2015 14:17:20 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from forward2h.mail.yandex.net (forward2h.mail.yandex.net [IPv6:2a02:6b8:0:f05::2]) by mx1.freebsd.org (Postfix) with ESMTP id A4679112A for ; Fri, 24 Jul 2015 14:17:20 +0000 (UTC) (envelope-from melifaro@ipfw.ru) Received: from web25h.yandex.ru (web25h.yandex.ru [84.201.187.159]) by forward2h.mail.yandex.net (Yandex) with ESMTP id 067D6700D8D; Fri, 24 Jul 2015 17:17:17 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web25h.yandex.ru (Yandex) with ESMTP id 3CEE662603E3; Fri, 24 Jul 2015 17:17:17 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfw.ru; s=mail; t=1437747437; bh=aEu2LyPFoYSPYC/wEjl3iNwELl4dQ7cjEx+A7rTcoTc=; h=From:To:In-Reply-To:References:Subject:Date; b=wcBAB+N4YXT/0tRnllAIG2teNwxM34CqMjYmgUKVPV/jDcBK7qwHNXORYmay/ejZJ r3AXbYX5LdQRLNT/64fjAe8RSi1XIrDOxHIct9KGov+Y2AmaN8KAIt3cLL4jyCWp4W T3dUwomJoOgR96pVKnkn6UJzfSsan/1y2yUUgKC8= Received: by web25h.yandex.ru with HTTP; Fri, 24 Jul 2015 17:17:16 +0300 From: Alexander V. Chernikov To: Kurt Jaeger , Marcelo Gondim , FreeBSD Stable Mailing List In-Reply-To: <20150724141153.GI49099@home.opsec.eu> References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> <20150724141053.GH49099@home.opsec.eu> <20150724141153.GI49099@home.opsec.eu> Subject: Re: table with bug in ipfw Message-Id: <17501437747436@web25h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 24 Jul 2015 17:17:16 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 14:17:21 -0000 From owner-freebsd-stable@freebsd.org Fri Jul 24 14:26:29 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 481059A9971 for ; Fri, 24 Jul 2015 14:26:29 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 080E91C41 for ; Fri, 24 Jul 2015 14:26:28 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-24-166-126-146.neo.res.rr.com [24.166.126.146]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id a449ac9b; Fri, 24 Jul 2015 10:26:18 -0400 (EDT) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id 36e44b44; TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 24 Jul 2015 10:26:18 -0400 (EDT) Message-ID: <1437748042.22741.44.camel@michaeleichorn.com> Subject: Re: 10.2-Beta i386..what's wrong..? From: "Michael B. Eichorn" To: Holm Tiffe Cc: freebsd-stable Date: Fri, 24 Jul 2015 10:27:22 -0400 In-Reply-To: <20150724070245.GC11640@beast.freibergnet.de> References: <55B17B7A.4080402@gmail.com> <20150723234805.GK84931@FreeBSD.org> <55B18488.9060602@sorbs.net> <20150724004026.GA1370@lonesome.com> <20150724004343.GM84931@FreeBSD.org> <20150724004443.GC1370@lonesome.com> <20150724004939.GN84931@FreeBSD.org> <20150724070245.GC11640@beast.freibergnet.de> Content-Type: multipart/signed; micalg="sha-512"; protocol="application/x-pkcs7-signature"; boundary="=-4dl5CrdiY+zJzptqLIkE" X-Mailer: Evolution 3.16.4 Mime-Version: 1.0 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 14:26:29 -0000 --=-4dl5CrdiY+zJzptqLIkE Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable >=20 > ...more RAM? Always more RAM? >=20 > Reality check please, this is an i386 Machine with 2 Gbytes. > It has two of 3 sockets polluted with RAM Modules (1G), there is not=20 > that > much Space to give it more RAM. >=20 > i386 is a supported architecture as far as I know, ok it where nice to > have in i386 with 8 Gigs of RAM but there are not much motherboards out > here that would support this.. >=20 > This remebers me to microsofts attemts to write Software, always more=20 > RAM > and more CPU to fasten up endless loops.. >=20 > Regards, >=20 > Holm Of course i386 is supported, but in the near future arm will be tier 1 as well. Not every arch can do everything equally well. ZFS was designed to allow huge storage sizes (files are limited to 16 EiB). At some point the storage is just too big for fsck to make sense so you use copy-on-write, and copy-on-write kills performance unless you do a significant amount of caching. Thus the tradeoff is for big storage you need big memory. For an execellent rundown why ZFS does this and some comparisons to UFS I highly recommend Dr. McKusick's "An Introduction to the Implementation of ZFS" from BSDCan 2015: Part 1, 18m https://youtu.be/UP_JfUUmDZo Part 2, 54m https://youtu.be/l-RCLgLxuSc --=-4dl5CrdiY+zJzptqLIkE Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgMFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDnzCCA5sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAwUAoIIB2zAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTA3MjQxNDI3MjJaME8GCSqGSIb3DQEJ BDFCBEBeT6kFX0/8Dc9HY+gdp0hMpSYxiFaHoz9D9XIT+YrW5r+ybm1AjJvZ7Cmd80RVem63oKmH rZQOUEFSWdqWp+RwMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQQIDDl3GMIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoT DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25p bmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50 IENBAgMOXcYwDQYJKoZIhvcNAQEBBQAEggEAY9zmKVgOFfp2XofsX14ktANpREbDGj6FkCjLFFCn 3sO1ZPkLBl4SRmz/v+U3/3HaGoZnK97CK3um0xe8wq3aRiv3x4sVfgtvr6q2U+BKcpr/sRas99h8 6PXi3sbZi+lsDIwV/5aAiPEEQAqGvEIArJp3cjaAOGsZDaEsrDXKF+UV/BspHOuXfa+RJlcsF7L/ 4dV1ZJRrpLt+q5W4mSmUQn9v+tS9rsyD3A/bxKhb5zKOmblwTNuMEaLv53oKZ0/uxGydsJjdBBwz EAshS+HkpvvlFZPe9RuqDbpfmEkEoii4QX5eIYRb1Z7ckw8GEArW4ETL3MuUvPzxH51sAuVEtQAA AAAAAA== --=-4dl5CrdiY+zJzptqLIkE-- From owner-freebsd-stable@freebsd.org Fri Jul 24 14:31:05 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07ECF9A9AB7 for ; Fri, 24 Jul 2015 14:31:05 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B84701FAE for ; Fri, 24 Jul 2015 14:31:04 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.85 (FreeBSD)) (envelope-from ) id 1ZIe07-000GJ3-G9; Fri, 24 Jul 2015 16:31:03 +0200 Date: Fri, 24 Jul 2015 16:31:03 +0200 From: Kurt Jaeger To: "Alexander V. Chernikov" Cc: Marcelo Gondim , FreeBSD Stable Mailing List Subject: Re: table with bug in ipfw Message-ID: <20150724143103.GJ49099@home.opsec.eu> References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> <20150724141053.GH49099@home.opsec.eu> <20150724141153.GI49099@home.opsec.eu> <17501437747436@web25h.yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <17501437747436@web25h.yandex.ru> X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 14:31:05 -0000 Hi! > This one was fixed in r266310 (based on bin/189471) but I haven't > merged it to -stable. Because it changes ip_fw.h, would it break KABI or ABI ? Would that prevent a merge to 10.2 ? -- pi@opsec.eu +49 171 3101372 5 years to go ! From owner-freebsd-stable@freebsd.org Fri Jul 24 15:07:52 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E2EC9AA7DC for ; Fri, 24 Jul 2015 15:07:52 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [191.243.120.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 120651929 for ; Fri, 24 Jul 2015 15:07:51 +0000 (UTC) (envelope-from gondim@bsdinfo.com.br) Received: from mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) by mail.bsdinfo.com.br (Postfix) with ESMTP id 195A230FC30 for ; Fri, 24 Jul 2015 12:06:42 -0300 (BRT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bsdinfo.com.br; h=content-transfer-encoding:content-type:content-type :in-reply-to:references:subject:subject:to:mime-version :user-agent:from:from:date:date:message-id; s=dkim; t= 1437750401; x=1438614402; bh=md71XzCFU6G3dQ+G+RS39+ujlhU0tRHTbKZ lZFT/RLU=; b=qlK1LPPhn27PpjSeJQXF6J0NlTqvAntWpFEt4YK3oEzpsDgZHNQ gv9wCjWIlcSCgnqY0+qZU+p6StVXR6JVljNRhNUUq88wHMyLJyii+z20ar357VRO Hb3GLs1uQ/bijeZnA50gAQrxB/XP9coOwoYCk8CuctWmmBxi1RdskMnc= X-Virus-Scanned: amavisd-new at mail.bsdinfo.com.br Received: from mail.bsdinfo.com.br ([127.0.0.1]) by mail.bsdinfo.com.br (mail.bsdinfo.com.br [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ll6PG9345gzK for ; Fri, 24 Jul 2015 12:06:41 -0300 (BRT) Received: from [192.168.10.208] (unknown [186.193.54.69]) by mail.bsdinfo.com.br (Postfix) with ESMTPSA id 91B4030FC2F; Fri, 24 Jul 2015 12:06:41 -0300 (BRT) Message-ID: <55B25496.1080308@bsdinfo.com.br> Date: Fri, 24 Jul 2015 12:07:02 -0300 From: Marcelo Gondim User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: Kurt Jaeger , "Alexander V. Chernikov" CC: FreeBSD Stable Mailing List Subject: Re: table with bug in ipfw References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> <20150724141053.GH49099@home.opsec.eu> <20150724141153.GI49099@home.opsec.eu> <17501437747436@web25h.yandex.ru> <20150724143103.GJ49099@home.opsec.eu> In-Reply-To: <20150724143103.GJ49099@home.opsec.eu> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:07:52 -0000 On 24-07-2015 11:31, Kurt Jaeger wrote: > Hi! > >> This one was fixed in r266310 (based on bin/189471) but I haven't >> merged it to -stable. > Because it changes ip_fw.h, would it break KABI or ABI ? > Would that prevent a merge to 10.2 ? > I do not know if it affects the rule or whether it is merely visual. But this bug has since version 10.0. I thought it would be corrected to version 10.2. From owner-freebsd-stable@freebsd.org Fri Jul 24 15:12:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BFD099AA920 for ; Fri, 24 Jul 2015 15:12:08 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57DF31C84 for ; Fri, 24 Jul 2015 15:12:08 +0000 (UTC) (envelope-from allbery.b@gmail.com) Received: by wicgb10 with SMTP id gb10so33148270wic.1 for ; Fri, 24 Jul 2015 08:12:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=365f3lfadt0nHLPcOYrujUR37/VKcaD875/VrvxlkxU=; b=SmOEMVrQMHbeM7hw0KRNwpm1sxjCUTS2FQCubbPSHpSF9ExOr7ksBsFW3wP1X6d1i6 ALOhvjRfAC/WrdTvvSghyByQmGxQymW5YAdbgPv+SXju7lZDV4QrOXihKX1sOkP76eXT Bf8yx3Y9yBs6KxRyPAaQVkt8gWroGMWSE4jDgQ8pqu0ps4nDEPCIACoMbs0/G/545nSV IYLWtgA4AHIh4k/uL0EXeaEjLiJ5qz0poeqXV0eW4CECWdOdUXJ01kLKX29WpWcduWw1 K4N3pWnHtcK6ZMGmjrFXC/f1YxEz0TzrpTAyWWrF+bH+s0e+YtsY/nZECF72xUryCqk5 IpKQ== MIME-Version: 1.0 X-Received: by 10.194.206.65 with SMTP id lm1mr27755083wjc.117.1437750726386; Fri, 24 Jul 2015 08:12:06 -0700 (PDT) Received: by 10.27.133.84 with HTTP; Fri, 24 Jul 2015 08:12:06 -0700 (PDT) In-Reply-To: <55B25496.1080308@bsdinfo.com.br> References: <555A8208.9010208@bsdinfo.com.br> <1442671432126620@web6h.yandex.ru> <55B24142.7090001@bsdinfo.com.br> <20150724141053.GH49099@home.opsec.eu> <20150724141153.GI49099@home.opsec.eu> <17501437747436@web25h.yandex.ru> <20150724143103.GJ49099@home.opsec.eu> <55B25496.1080308@bsdinfo.com.br> Date: Fri, 24 Jul 2015 11:12:06 -0400 Message-ID: Subject: Re: table with bug in ipfw From: Brandon Allbery To: Marcelo Gondim Cc: Kurt Jaeger , "Alexander V. Chernikov" , FreeBSD Stable Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:12:08 -0000 On Fri, Jul 24, 2015 at 11:07 AM, Marcelo Gondim wrote: > On 24-07-2015 11:31, Kurt Jaeger wrote: > >> Hi! >> >> This one was fixed in r266310 (based on bin/189471) but I haven't >>> merged it to -stable. >>> >> Because it changes ip_fw.h, would it break KABI or ABI ? >> Would that prevent a merge to 10.2 ? >> >> I do not know if it affects the rule or whether it is merely visual. But > this bug has since version 10.0. > I thought it would be corrected to version 10.2. > Looks to me like it's just applying an IPv6 output format (incorrectly even for IPv6, arguably) to an IPv4 address? -- brandon s allbery kf8nh sine nomine associates allbery.b@gmail.com ballbery@sinenomine.net unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net From owner-freebsd-stable@freebsd.org Fri Jul 24 15:26:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A078B9AAB61 for ; Fri, 24 Jul 2015 15:26:00 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 718DB1580; Fri, 24 Jul 2015 15:26:00 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by pachj5 with SMTP id hj5so15958180pac.3; Fri, 24 Jul 2015 08:25:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=oo1daHER6Wp1W+bm2FepRIx3p3+tNDU1gYvFkl9kczc=; b=Bq5Vb2jxKV+qqqQwQ80ihP9SGl56ypns+tzj5xFgxjoyWwBnm7NHsGM/FXbNo6XSmK G76JdgMWTe0MJQdbfk/8bKJAgoV/Xfof+Ge++Ki3gpzoN762W1W2NVnPxeC/aJ44N3pj s4w7VPne1jzqjNvEm9heCEupGqlx2Jh9Gtbe2TgCi9QvHNTG6pKk3X+WN4mUKFknaBvT NbbMswCqjRKZ5g2URAAbQzxW6DUsItTZYLus/UxlPB/EVXaaQc8ordAz5ZbCFLvkHpRm 2mvi/CCPXeh6G2YJfSX/KTp2eRwxIgj/f/E4fMeZnGQUTN9JkUS0qIpelFLDvPR5ejgm qRGQ== X-Received: by 10.70.131.73 with SMTP id ok9mr32204883pdb.109.1437751559909; Fri, 24 Jul 2015 08:25:59 -0700 (PDT) Received: from ox ([2601:641:c000:600:84cf:6e7f:7ff6:2375]) by smtp.gmail.com with ESMTPSA id j5sm15216757pdi.7.2015.07.24.08.25.57 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 24 Jul 2015 08:25:58 -0700 (PDT) Date: Fri, 24 Jul 2015 08:25:55 -0700 From: Navdeep Parhar To: Slawa Olhovchenkov Cc: Xin Li , re@FreeBSD.org, d@delphij.net, freebsd-stable@freebsd.org Subject: Re: freebsd downgrade Message-ID: <20150724152555.GB4276@ox> Mail-Followup-To: Slawa Olhovchenkov , Xin Li , re@FreeBSD.org, d@delphij.net, freebsd-stable@freebsd.org References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> <20150724072052.GF43740@zxy.spb.ru> <55B1EC8F.7050304@delphij.net> <20150724075010.GG43740@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150724075010.GG43740@zxy.spb.ru> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:26:00 -0000 On Fri, Jul 24, 2015 at 10:50:10AM +0300, Slawa Olhovchenkov wrote: > > > > > > For me -- degradate network performance, about 30%. I am do > > > verification now, by downgrading kernel. > > > > What kind of workload and what NIC are you using? > > Chelsio T580-LP-CR, http serving. > r276179 can utilise 40Gbit, r281264 -- only 28Gbit. Can you please try -RC1 when it comes out and report back if you still see degraded network performance? Regards, Navdeep From owner-freebsd-stable@freebsd.org Fri Jul 24 15:36:37 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 190DE9AAD26 for ; Fri, 24 Jul 2015 15:36:37 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C926A1C1D; Fri, 24 Jul 2015 15:36:36 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1ZIf1U-0000SO-Io; Fri, 24 Jul 2015 18:36:32 +0300 Date: Fri, 24 Jul 2015 18:36:32 +0300 From: Slawa Olhovchenkov To: Xin Li , re@FreeBSD.org, d@delphij.net, freebsd-stable@freebsd.org Subject: Re: freebsd downgrade Message-ID: <20150724153632.GH43740@zxy.spb.ru> References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> <20150724072052.GF43740@zxy.spb.ru> <55B1EC8F.7050304@delphij.net> <20150724075010.GG43740@zxy.spb.ru> <20150724152555.GB4276@ox> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150724152555.GB4276@ox> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:36:37 -0000 On Fri, Jul 24, 2015 at 08:25:55AM -0700, Navdeep Parhar wrote: > On Fri, Jul 24, 2015 at 10:50:10AM +0300, Slawa Olhovchenkov wrote: > > > > > > > > For me -- degradate network performance, about 30%. I am do > > > > verification now, by downgrading kernel. > > > > > > What kind of workload and what NIC are you using? > > > > Chelsio T580-LP-CR, http serving. > > r276179 can utilise 40Gbit, r281264 -- only 28Gbit. > > Can you please try -RC1 when it comes out and report back if you still > see degraded network performance? Now I am try revisons r276179 and compare with r281264 (for absolutly clean compare -- same hardware, same configuration, same workload) before this I am comare slighty different hardware (card instaled in different slots) and posibly different workload. After this I am try r278800 and RC1 -- one times per day. From owner-freebsd-stable@freebsd.org Fri Jul 24 15:44:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0627E9AAED5 for ; Fri, 24 Jul 2015 15:44:08 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward4h.mail.yandex.net (forward4h.mail.yandex.net [IPv6:2a02:6b8:0:f05::4]) by mx1.freebsd.org (Postfix) with ESMTP id B31741181 for ; Fri, 24 Jul 2015 15:44:07 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp4h.mail.yandex.net (smtp4h.mail.yandex.net [84.201.186.21]) by forward4h.mail.yandex.net (Yandex) with ESMTP id B45411B202A4; Fri, 24 Jul 2015 18:43:56 +0300 (MSK) Received: from smtp4h.mail.yandex.net (localhost [127.0.0.1]) by smtp4h.mail.yandex.net (Yandex) with ESMTP id 0A26D2C3195; Fri, 24 Jul 2015 18:43:55 +0300 (MSK) Received: by smtp4h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id QOw2j8MfWX-hscmTXgW; Fri, 24 Jul 2015 18:43:54 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437752635; bh=f76sc0kq2QTXP7NM6MzV8YQQ/T8/KhPNxqEH2JH242Q=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=Te4g+zef3PtOajy/qzCXcNnNEKuPwAJLEuxk6jR9hfyFjvfXkPByyHTTki08paxyM xJk0N3SLUc1dNpnN9kKIPIbL9ram/VmqxcQGuRjmT3Piay+yUxhxhIIIWrPBG7yjr8 DafVpOSj8Zkj/FkTGhlRX3h4h6vFVjbgwiaHMurE= Authentication-Results: smtp4h.mail.yandex.net; dkim=pass header.i=@yandex.com X-Yandex-ForeignMX: US Message-ID: <1437752632.11590.2.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: timp Cc: freebsd-stable@freebsd.org Date: Fri, 24 Jul 2015 11:43:52 -0400 In-Reply-To: <1437745202428-6027559.post@n5.nabble.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:44:08 -0000 On Fri, 2015-07-24 at 06:40 -0700, timp wrote: > Hi! > > > 1. VT module doesn't load. > > In /boot/loader.conf I have: > > kern.vty=vt > > but it doesn't work. If I manual loada module witk kldload radeonkms I > > got just black screen and nothing more. > > As I know it's not a module. And you can't load it. > I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and > have no problem. > > > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > > and works. > > 3. The same is with web camera. > > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > > It works if I load with kldload. > > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > > show picture in menu (it is default one). > > > > In /boot/device.hints I have also some hits which are for my sound card > > and it doesn't read them and sound doesn't work correct too. > > > > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > > Today I update with freebsd-update fetch and the problem exist. > > What if you load the previous kernel? Did you upgrade only kernel? What > about world? > Something's definitely wrong with your machine. > I have > > % cat /boot/loader.conf > zfs_load="YES" > kern.geom.label.gptid.enable="0" > kern.vty=vt > hw.vga.textmode=1 > cuse4bsd_load="YES" > autoboot_delay="2" > coretemp_load="YES" > fuse_load="YES" > kern.racct.enable=1 > > and it works. > On my system worked without problems before update. I forgot to mentoned that I have FreeBSD installed on iMac 11,1 and boot manager is rEFIT. It works without problem more than two years. What is the problem now I don't know. From owner-freebsd-stable@freebsd.org Fri Jul 24 15:58:51 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C7769A90B7 for ; Fri, 24 Jul 2015 15:58:51 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward13h.cmail.yandex.net (forward13h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::9e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E67C117D9 for ; Fri, 24 Jul 2015 15:58:50 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web15h.yandex.ru (web15h.yandex.ru [84.201.186.44]) by forward13h.cmail.yandex.net (Yandex) with ESMTP id E2AED21413 for ; Fri, 24 Jul 2015 18:58:37 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web15h.yandex.ru (Yandex) with ESMTP id 89E355900C6B; Fri, 24 Jul 2015 18:58:37 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437753517; bh=FgAxVWatxYZTKQt1N0UMBOWajqdexCCttOdqb7tvXvs=; h=From:Cc:In-Reply-To:References:Subject:Date; b=aw7c6rJ+Su/YYDD9mz+3+ZrjzMpdtST5l+NxrX+paISzHo7BnNgakQ4XrqzzlklUv 4mucUnhzPkouYM57u8PIkExvdlTwGEdSKQi20sCaYU5COOengIYNIOFFGT+Iy+7mAd jZXiiCvrGuJUUjKNEUJ91OM5uDoMw10XLK2i10hQ= Received: by web15h.yandex.ru with HTTP; Fri, 24 Jul 2015 18:58:36 +0300 From: deco33000@yandex.com Cc: freebsd-stable In-Reply-To: <1437665319.1334.519.camel@freebsd.org> References: <464641437658995@web16j.yandex.ru> <190031437662308@web29g.yandex.ru> <1437665319.1334.519.camel@freebsd.org> Subject: Re: struct timehands: th_generation field MIME-Version: 1.0 Message-Id: <1568531437753516@web15h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 24 Jul 2015 17:58:36 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 15:58:51 -0000 OK. I read the document and understood it I guess. Very interesting, and well engineered. On x86/i386/amd64, could not all this be replaced by a simple call to apic timer ? We would get the timestamp, we can even store it, make calculation on top of it. My jugement may miss something important though. That is why I ask :) --š Jog From owner-freebsd-stable@freebsd.org Fri Jul 24 16:18:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ECF89A94EB for ; Fri, 24 Jul 2015 16:18:16 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward15p.cmail.yandex.net (forward15p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::bd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5337E1138 for ; Fri, 24 Jul 2015 16:18:16 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [IPv6:2a02:6b8:0:1402::119]) by forward15p.cmail.yandex.net (Yandex) with ESMTP id 7C52F22555; Fri, 24 Jul 2015 19:18:03 +0300 (MSK) Received: from smtp18.mail.yandex.net (localhost [127.0.0.1]) by smtp18.mail.yandex.net (Yandex) with ESMTP id 287AA18A014D; Fri, 24 Jul 2015 19:18:03 +0300 (MSK) Received: by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id T91NziOxUg-I1OKHsVD; Fri, 24 Jul 2015 19:18:02 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437754682; bh=ghVSZz25UcbH1E+ESQSmhsGePf2ehXnS5Cubszb+0UY=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=neiw3IC+aQBBUeprCTyJgjQLhKpMQjA8NqiwdfrPTyM/vfeuW+K5KZ9voouuMzf91 EkUkxrl7f7m3dBdi7CzO04D4Hg44H9A6mik3M0a/1NVKFEbcPMp/j2jhfnZn7W6S8h 7r9PsFLwZKm6Fu2vfvLEVo3Kg+DUPfEpAHYhixg0= Authentication-Results: smtp18.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437754678.41896.0.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: timp Cc: freebsd-stable@freebsd.org Date: Fri, 24 Jul 2015 12:17:58 -0400 In-Reply-To: <1437745202428-6027559.post@n5.nabble.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 16:18:16 -0000 On Fri, 2015-07-24 at 06:40 -0700, timp wrote: > Hi! > > > 1. VT module doesn't load. > > In /boot/loader.conf I have: > > kern.vty=vt > > but it doesn't work. If I manual loada module witk kldload radeonkms I > > got just black screen and nothing more. > > As I know it's not a module. And you can't load it. > I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and > have no problem. > > > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > > and works. > > 3. The same is with web camera. > > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > > It works if I load with kldload. > > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > > show picture in menu (it is default one). > > > > In /boot/device.hints I have also some hits which are for my sound card > > and it doesn't read them and sound doesn't work correct too. > > > > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > > Today I update with freebsd-update fetch and the problem exist. > > What if you load the previous kernel? Did you upgrade only kernel? What > about world? > Something's definitely wrong with your machine. > I have > > % cat /boot/loader.conf > zfs_load="YES" > kern.geom.label.gptid.enable="0" > kern.vty=vt > hw.vga.textmode=1 > cuse4bsd_load="YES" > autoboot_delay="2" > coretemp_load="YES" > fuse_load="YES" > kern.racct.enable=1 > > and it works. > > > > -- > View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-10-1-RELEASE-to-FreeBSD-10-2-BETA2-tp6027186p6027559.html > Sent from the freebsd-stable mailing list archive at Nabble.com. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" I forgot... I just delete files in /boot and replace with one from 10.1 release and it works. From owner-freebsd-stable@freebsd.org Fri Jul 24 16:50:11 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 378CF9A9A79 for ; Fri, 24 Jul 2015 16:50:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04C771EEC for ; Fri, 24 Jul 2015 16:50:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by igbpg9 with SMTP id pg9so21320585igb.0 for ; Fri, 24 Jul 2015 09:50:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MNnEhBcrDHS4lov82WeO6mpMzdeyRz19ItqGG/9V9us=; b=xBbQTBupS6RFI3dh4nzYMT1sqA1im0nkFhHfX9mHaE4qM0HRIG4MqMap+4NU6X0Lvm zbQfoXkc+jDmoXN8p3n/3vAWPmgDV9FuUi6Pp21UBZZjIUtKW4eWr1DR/hy4d5XNRz6E Pr0fz50hcQ2pCYWxQAc9Khu4f4KmLQnkdxdcAy2oeEjhD14ee5oPBjaggCcAKpj5z0qV sjRK4urIknUK+m+OaX+tqWMvJGn+Y8EkrqgK7VRqXG/SEcb+bQ3cr2fobyyFKtIlPUND JdnDq3h4h4YI1KnaV5MLZutSfIabX39qbOv+86dN9p0BADuHACnBJmEQWIFYikBcbPua qycA== MIME-Version: 1.0 X-Received: by 10.107.129.215 with SMTP id l84mr23898650ioi.78.1437756610438; Fri, 24 Jul 2015 09:50:10 -0700 (PDT) Received: by 10.36.38.133 with HTTP; Fri, 24 Jul 2015 09:50:10 -0700 (PDT) In-Reply-To: <1568531437753516@web15h.yandex.ru> References: <464641437658995@web16j.yandex.ru> <190031437662308@web29g.yandex.ru> <1437665319.1334.519.camel@freebsd.org> <1568531437753516@web15h.yandex.ru> Date: Fri, 24 Jul 2015 09:50:10 -0700 Message-ID: Subject: Re: struct timehands: th_generation field From: Adrian Chadd To: deco33000@yandex.com Cc: freebsd-stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 16:50:11 -0000 accessing hardware isn't free. Locking also isn't free. That's why there's this mechanism. -adrian On 24 July 2015 at 08:58, wrote: > > OK. > > I read the document and understood it I guess. > Very interesting, and well engineered. > > On x86/i386/amd64, could not all this be replaced by a simple call to apic timer ? > We would get the timestamp, we can even store it, make calculation on top of it. > > My jugement may miss something important though. That is why I ask :) > > > -- > Jog > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Fri Jul 24 19:00:47 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B64F79A94B6 for ; Fri, 24 Jul 2015 19:00:47 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward15p.cmail.yandex.net (forward15p.cmail.yandex.net [87.250.241.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6D5201689 for ; Fri, 24 Jul 2015 19:00:46 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web24g.yandex.ru (web24g.yandex.ru [IPv6:2a02:6b8:0:1402::34]) by forward15p.cmail.yandex.net (Yandex) with ESMTP id B7D88219E0 for ; Fri, 24 Jul 2015 22:00:39 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web24g.yandex.ru (Yandex) with ESMTP id 63BD858E11CE; Fri, 24 Jul 2015 22:00:39 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437764439; bh=rxsC5cOL720eIF5AYFZjRyHW4WznyB0s0y3BC03WQfo=; h=From:Cc:Subject:Date; b=sb4VefOMPFJjPMZSAmHOesKuaZwcBDG9EzedJRfkepePorraDLH10EgY6UXOi5Ttu myMeaSHKlyCMm6SzkzlHVPs6gkFpCfEAjCp3sDugVxmgdbvORH5wENwRtrVXiUfwtf j6XA5pufDbwiWcn2CTfp5te4kNU8qm3rllHr8JEk= Received: by web24g.yandex.ru with HTTP; Fri, 24 Jul 2015 22:00:38 +0300 From: deco33000 Jog Envelope-From: deco33000@yandex.ru Cc: freebsd-stable Subject: Re: struct timehands: th_generation field Message-Id: <228251437764438@web24g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Fri, 24 Jul 2015 21:00:38 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 19:00:47 -0000 From owner-freebsd-stable@freebsd.org Fri Jul 24 20:07:24 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2B879AA5C1 for ; Fri, 24 Jul 2015 20:07:24 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x231.google.com (mail-wi0-x231.google.com [IPv6:2a00:1450:400c:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 356991F0F for ; Fri, 24 Jul 2015 20:07:24 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wicmv11 with SMTP id mv11so77140594wic.0 for ; Fri, 24 Jul 2015 13:07:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=YmEaZzWUmt3t0assZLnq8sReAgV0SaJL00OQ9RaiJU0=; b=Q2zLD+L6w+fjVhtN5rErKe3Pb9fj9B38fEvpSppafIzyE+HyauFK4bfLnwVdCXhosE KM9RhLnSxK4HAI+J88L1CAv//JTIBSqL77k8bjNicsQNzGCcSLNPcfb02jDlNvGJm/1B 4QKSF6Td3rV6JDwIcYrh9Dtf0pUAm95tz25uUvo1CyH8JJ8k7Glrv++A4ubdljjmUo7S Q+d+es09kZWwFVyiZj258DpVFVv0M1p1HMUsHFZ5AzEoglUj416rJSjZh3ybrQOjKBBq T5Aab5V0mDeqvN+pqceSQfHh/GAjo+hYAW6GS+LuKvT0eDUTwoBM9EfaWW/Rk3F+TPzk YooQ== MIME-Version: 1.0 X-Received: by 10.180.83.65 with SMTP id o1mr277232wiy.14.1437768442304; Fri, 24 Jul 2015 13:07:22 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Fri, 24 Jul 2015 13:07:22 -0700 (PDT) In-Reply-To: <1437752632.11590.2.camel@yandex.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437752632.11590.2.camel@yandex.com> Date: Fri, 24 Jul 2015 23:07:22 +0300 Message-ID: Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Pavel Timofeev To: Stari Karp Cc: freebsd-stable stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 20:07:24 -0000 2015-07-24 18:43 GMT+03:00 Stari Karp : > On Fri, 2015-07-24 at 06:40 -0700, timp wrote: >> Hi! >> >> > 1. VT module doesn't load. >> > In /boot/loader.conf I have: >> > kern.vty=vt >> > but it doesn't work. If I manual loada module witk kldload radeonkms I >> > got just black screen and nothing more. >> >> As I know it's not a module. And you can't load it. >> I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and >> have no problem. >> >> > 2. Fireware external disk doesn't work either. In /boot/loader.conf I >> > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load >> > and works. >> > 3. The same is with web camera. >> > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. >> > It works if I load with kldload. >> > In /boot/loader.conf I have also loader_logo="beastie" which doesn't >> > show picture in menu (it is default one). >> > >> > In /boot/device.hints I have also some hits which are for my sound card >> > and it doesn't read them and sound doesn't work correct too. >> > >> > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. >> > Today I update with freebsd-update fetch and the problem exist. >> >> What if you load the previous kernel? Did you upgrade only kernel? What >> about world? >> Something's definitely wrong with your machine. >> I have >> >> % cat /boot/loader.conf >> zfs_load="YES" >> kern.geom.label.gptid.enable="0" >> kern.vty=vt >> hw.vga.textmode=1 >> cuse4bsd_load="YES" >> autoboot_delay="2" >> coretemp_load="YES" >> fuse_load="YES" >> kern.racct.enable=1 >> >> and it works. >> > On my system worked without problems before update. > I forgot to mentoned that I have FreeBSD installed on iMac 11,1 and boot > manager is rEFIT. It works without problem more than two years. > What is the problem now I don't know. > > This is really important clarification, I am not kidding. I have never had such hardware. Try to load from latest ISO ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ From owner-freebsd-stable@freebsd.org Fri Jul 24 20:07:39 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D74DA9AA5DA for ; Fri, 24 Jul 2015 20:07:39 +0000 (UTC) (envelope-from timp87@gmail.com) Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7224B1FBD for ; Fri, 24 Jul 2015 20:07:39 +0000 (UTC) (envelope-from timp87@gmail.com) Received: by wicmv11 with SMTP id mv11so77146500wic.0 for ; Fri, 24 Jul 2015 13:07:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qP1pxQRRI5jwCJ+smRNGnsY77xmrBOEUm7AfT4YuL98=; b=R1VWLbDyzS/cwhej7xmIW63xF0wUtfu+zQMCHqhVA1CeCKtVKac1nyu00J2JPX7nAR MmcvcUjEnNSHXjl126IO9+VbKD9yBn06hh5V+mPPPtWlnN+rctgH8NDoA4y4v0bvRdqj jjjLP70SzWYdCrQaMlSdc47+xRxh4QgWwo3pDq9zOqFmdqTgncR5kVNB8akDp+mO4QhI DeCrXH0MUGEjKkOeye6pzWaqs5g/4TW2Va300qRBb/LTSatRKOhbuJw2TyYgqTMLEfHr BRovaOS5mlPvigvgPuZHVQq51tXPBvG57gy4EC99KR3vSCOk5RmiapUOtjZBvsEXv2nz ns6g== MIME-Version: 1.0 X-Received: by 10.194.121.34 with SMTP id lh2mr30275631wjb.101.1437768457918; Fri, 24 Jul 2015 13:07:37 -0700 (PDT) Received: by 10.28.48.207 with HTTP; Fri, 24 Jul 2015 13:07:37 -0700 (PDT) In-Reply-To: <1437754678.41896.0.camel@yandex.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437754678.41896.0.camel@yandex.com> Date: Fri, 24 Jul 2015 23:07:37 +0300 Message-ID: Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Pavel Timofeev To: Stari Karp Cc: freebsd-stable stable Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 20:07:40 -0000 2015-07-24 19:17 GMT+03:00 Stari Karp : > On Fri, 2015-07-24 at 06:40 -0700, timp wrote: >> Hi! >> >> > 1. VT module doesn't load. >> > In /boot/loader.conf I have: >> > kern.vty=vt >> > but it doesn't work. If I manual loada module witk kldload radeonkms I >> > got just black screen and nothing more. >> >> As I know it's not a module. And you can't load it. >> I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and >> have no problem. >> >> > 2. Fireware external disk doesn't work either. In /boot/loader.conf I >> > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load >> > and works. >> > 3. The same is with web camera. >> > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. >> > It works if I load with kldload. >> > In /boot/loader.conf I have also loader_logo="beastie" which doesn't >> > show picture in menu (it is default one). >> > >> > In /boot/device.hints I have also some hits which are for my sound card >> > and it doesn't read them and sound doesn't work correct too. >> > >> > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. >> > Today I update with freebsd-update fetch and the problem exist. >> >> What if you load the previous kernel? Did you upgrade only kernel? What >> about world? >> Something's definitely wrong with your machine. >> I have >> >> % cat /boot/loader.conf >> zfs_load="YES" >> kern.geom.label.gptid.enable="0" >> kern.vty=vt >> hw.vga.textmode=1 >> cuse4bsd_load="YES" >> autoboot_delay="2" >> coretemp_load="YES" >> fuse_load="YES" >> kern.racct.enable=1 >> >> and it works. >> >> >> >> -- >> View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-10-1-RELEASE-to-FreeBSD-10-2-BETA2-tp6027186p6027559.html >> Sent from the freebsd-stable mailing list archive at Nabble.com. >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > I forgot... > > I just delete files in /boot and replace with one from 10.1 release and > it works. > > That's not surprising, because /boot has kernel/ folder with kernel itself and modules for it. From owner-freebsd-stable@freebsd.org Fri Jul 24 20:15:43 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2CCD9AA790 for ; Fri, 24 Jul 2015 20:15:43 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward15p.cmail.yandex.net (forward15p.cmail.yandex.net [87.250.241.141]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 268F5150F for ; Fri, 24 Jul 2015 20:15:42 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17]) by forward15p.cmail.yandex.net (Yandex) with ESMTP id D9208228A3; Fri, 24 Jul 2015 23:15:37 +0300 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id 851D6190059D; Fri, 24 Jul 2015 23:15:37 +0300 (MSK) Received: by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id xOtb2Iym9Z-FZneQcRh; Fri, 24 Jul 2015 23:15:36 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437768936; bh=8xxkgN9+uBXD3YRnSBDEmwWu0Lt2srYExm32MfKrjjw=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=yXI6J8Lrbqx68VPWdApJoj9LZ7ujmi3nEP7s/wQNcTslVMhjaX3ngVDdkCFy+5wgK g9okS2J1l/oH+MjSquB30qLZdwridY9dawqb4IdK3Yp8gpXH/BR/2NHUP97EtKhvRl ErNdA8h0ndf4xP4U+Ow8Gxlk8Q8jcc0TZN1DgmI8= Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437768933.2088.1.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: Pavel Timofeev Cc: freebsd-stable stable Date: Fri, 24 Jul 2015 16:15:33 -0400 In-Reply-To: References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437752632.11590.2.camel@yandex.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 20:15:43 -0000 On Fri, 2015-07-24 at 23:07 +0300, Pavel Timofeev wrote: > 2015-07-24 18:43 GMT+03:00 Stari Karp : > > On Fri, 2015-07-24 at 06:40 -0700, timp wrote: > >> Hi! > >> > >> > 1. VT module doesn't load. > >> > In /boot/loader.conf I have: > >> > kern.vty=vt > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I > >> > got just black screen and nothing more. > >> > >> As I know it's not a module. And you can't load it. > >> I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and > >> have no problem. > >> > >> > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > >> > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > >> > and works. > >> > 3. The same is with web camera. > >> > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > >> > It works if I load with kldload. > >> > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > >> > show picture in menu (it is default one). > >> > > >> > In /boot/device.hints I have also some hits which are for my sound card > >> > and it doesn't read them and sound doesn't work correct too. > >> > > >> > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > >> > Today I update with freebsd-update fetch and the problem exist. > >> > >> What if you load the previous kernel? Did you upgrade only kernel? What > >> about world? > >> Something's definitely wrong with your machine. > >> I have > >> > >> % cat /boot/loader.conf > >> zfs_load="YES" > >> kern.geom.label.gptid.enable="0" > >> kern.vty=vt > >> hw.vga.textmode=1 > >> cuse4bsd_load="YES" > >> autoboot_delay="2" > >> coretemp_load="YES" > >> fuse_load="YES" > >> kern.racct.enable=1 > >> > >> and it works. > >> > > On my system worked without problems before update. > > I forgot to mentoned that I have FreeBSD installed on iMac 11,1 and boot > > manager is rEFIT. It works without problem more than two years. > > What is the problem now I don't know. > > > > > > This is really important clarification, I am not kidding. > > I have never had such hardware. Try to load from latest ISO > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ From owner-freebsd-stable@freebsd.org Fri Jul 24 20:17:37 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 316D29AA7F1 for ; Fri, 24 Jul 2015 20:17:37 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward14p.cmail.yandex.net (forward14p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::be]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B2FA1654 for ; Fri, 24 Jul 2015 20:17:36 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [IPv6:2a02:6b8:0:1402::118]) by forward14p.cmail.yandex.net (Yandex) with ESMTP id 6CE4921A68; Fri, 24 Jul 2015 23:17:33 +0300 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id 16465190059D; Fri, 24 Jul 2015 23:17:32 +0300 (MSK) Received: by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id VETQnJfMnA-HVnaFAXv; Fri, 24 Jul 2015 23:17:32 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437769052; bh=+wbUout1zqLZMQeHINAcBXWqw6+13B3r94HIoWDWuIc=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=YWF+GkKpJlyH6Kcmih5KuFvw/k8LMFlmJ/g/iFM8ZlVDXMsuE0LYfCvp6ZQNAmkwE XWTO4X/ZYJuYV90nLaYc42FDxSP1a8qNtp5Gh79CX6EB/QJ5yZkyDlc8zZXmRM2dly HsvYzmewz3DRMtnp/pg3SymtgcIG3pUa0dMeg9kA= Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437769050.2088.3.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: Pavel Timofeev Cc: freebsd-stable stable Date: Fri, 24 Jul 2015 16:17:30 -0400 In-Reply-To: References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437754678.41896.0.camel@yandex.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 20:17:37 -0000 On Fri, 2015-07-24 at 23:07 +0300, Pavel Timofeev wrote: > 2015-07-24 19:17 GMT+03:00 Stari Karp : > > On Fri, 2015-07-24 at 06:40 -0700, timp wrote: > >> Hi! > >> > >> > 1. VT module doesn't load. > >> > In /boot/loader.conf I have: > >> > kern.vty=vt > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I > >> > got just black screen and nothing more. > >> > >> As I know it's not a module. And you can't load it. > >> I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and > >> have no problem. > >> > >> > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > >> > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > >> > and works. > >> > 3. The same is with web camera. > >> > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > >> > It works if I load with kldload. > >> > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > >> > show picture in menu (it is default one). > >> > > >> > In /boot/device.hints I have also some hits which are for my sound card > >> > and it doesn't read them and sound doesn't work correct too. > >> > > >> > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > >> > Today I update with freebsd-update fetch and the problem exist. > >> > >> What if you load the previous kernel? Did you upgrade only kernel? What > >> about world? > >> Something's definitely wrong with your machine. > >> I have > >> > >> % cat /boot/loader.conf > >> zfs_load="YES" > >> kern.geom.label.gptid.enable="0" > >> kern.vty=vt > >> hw.vga.textmode=1 > >> cuse4bsd_load="YES" > >> autoboot_delay="2" > >> coretemp_load="YES" > >> fuse_load="YES" > >> kern.racct.enable=1 > >> > >> and it works. > >> > >> > >> > >> -- > >> View this message in context: http://freebsd.1045724.n5.nabble.com/FreeBSD-10-1-RELEASE-to-FreeBSD-10-2-BETA2-tp6027186p6027559.html > >> Sent from the freebsd-stable mailing list archive at Nabble.com. > >> _______________________________________________ > >> freebsd-stable@freebsd.org mailing list > >> http://lists.freebsd.org/mailman/listinfo/freebsd-stable > >> To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > > > > I forgot... > > > > I just delete files in /boot and replace with one from 10.1 release and > > it works. > > > > > > That's not surprising, because /boot has kernel/ folder with kernel > itself and modules for it. Yes, I understand but when I copied files (not kernel) from 10.1-RELEASE it works. From owner-freebsd-stable@freebsd.org Fri Jul 24 20:19:12 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC6FF9AA839 for ; Fri, 24 Jul 2015 20:19:12 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward18p.cmail.yandex.net (forward18p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::ab]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49C4218C0 for ; Fri, 24 Jul 2015 20:19:12 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp18.mail.yandex.net (smtp18.mail.yandex.net [95.108.252.18]) by forward18p.cmail.yandex.net (Yandex) with ESMTP id 7EB1021630; Fri, 24 Jul 2015 23:19:01 +0300 (MSK) Received: from smtp18.mail.yandex.net (localhost [127.0.0.1]) by smtp18.mail.yandex.net (Yandex) with ESMTP id 200B318A014D; Fri, 24 Jul 2015 23:19:01 +0300 (MSK) Received: by smtp18.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id geTEUpBdle-IxOqhjbZ; Fri, 24 Jul 2015 23:19:00 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437769140; bh=oNj748QPABWBWla/2uuIkVBPlHrFVrfO8+FlnqjJ1IU=; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=k5cC02ucO729eMf+QgHp1WYTqZWsA1ekdT9JETCuJAMoJyXsghVQpv1SvwtsPLgQA ikH4utC4M+UvmLdp1mplp5cz1rCEe95/OLKwHtKYBJbMfRaVbl61fcTzk46rLxbudH jcK+ISHZVCA5Q+UWithEVBSo/eAe/rdH6bGf6iqc= Authentication-Results: smtp18.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437769137.2088.5.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: Pavel Timofeev Cc: freebsd-stable stable Date: Fri, 24 Jul 2015 16:18:57 -0400 In-Reply-To: References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437752632.11590.2.camel@yandex.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 20:19:13 -0000 On Fri, 2015-07-24 at 23:07 +0300, Pavel Timofeev wrote: > 2015-07-24 18:43 GMT+03:00 Stari Karp : > > On Fri, 2015-07-24 at 06:40 -0700, timp wrote: > >> Hi! > >> > >> > 1. VT module doesn't load. > >> > In /boot/loader.conf I have: > >> > kern.vty=vt > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I > >> > got just black screen and nothing more. > >> > >> As I know it's not a module. And you can't load it. > >> I have a workstation under 10.2-BETA2 amd64 GENERIC with kern.vty=vt set and > >> have no problem. > >> > >> > 2. Fireware external disk doesn't work either. In /boot/loader.conf I > >> > have sbp_load="YES" but it doesn't load. If I run kldload sbp it load > >> > and works. > >> > 3. The same is with web camera. > >> > cuse4bsd_load="YES" which I have in /boot/loader.conf doesn't load. > >> > It works if I load with kldload. > >> > In /boot/loader.conf I have also loader_logo="beastie" which doesn't > >> > show picture in menu (it is default one). > >> > > >> > In /boot/device.hints I have also some hits which are for my sound card > >> > and it doesn't read them and sound doesn't work correct too. > >> > > >> > On FreeBSD 10.1-RELEASE (amd 64) I didn't have problems. > >> > Today I update with freebsd-update fetch and the problem exist. > >> > >> What if you load the previous kernel? Did you upgrade only kernel? What > >> about world? > >> Something's definitely wrong with your machine. > >> I have > >> > >> % cat /boot/loader.conf > >> zfs_load="YES" > >> kern.geom.label.gptid.enable="0" > >> kern.vty=vt > >> hw.vga.textmode=1 > >> cuse4bsd_load="YES" > >> autoboot_delay="2" > >> coretemp_load="YES" > >> fuse_load="YES" > >> kern.racct.enable=1 > >> > >> and it works. > >> > > On my system worked without problems before update. > > I forgot to mentoned that I have FreeBSD installed on iMac 11,1 and boot > > manager is rEFIT. It works without problem more than two years. > > What is the problem now I don't know. > > > > > > This is really important clarification, I am not kidding. > > I have never had such hardware. Try to load from latest ISO > ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ I am so sorry for the previous pst... I will wait for RC1 and we will see how it is going :). For now I don't have a problem anymore. Thank you. -- ajtiM ----- http://www.redbubble.com/people/lumiwa https://www.facebook.com/pages/Lumiwa-FARM/775292915882930?_fb_noscript=1 From owner-freebsd-stable@freebsd.org Fri Jul 24 21:16:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 762989AA14B for ; Fri, 24 Jul 2015 21:16:00 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 637B41E57 for ; Fri, 24 Jul 2015 21:16:00 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: by mail.lifanov.com (Postfix, from userid 58) id 7EB081F68AF; Fri, 24 Jul 2015 17:15:53 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.lifanov.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.1 Received: from app.lifanov.com (chat.lifanov.com [206.125.175.13]) by mail.lifanov.com (Postfix) with ESMTPA id F0D7A1CB366 for ; Fri, 24 Jul 2015 17:15:52 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 24 Jul 2015 17:15:52 -0400 From: Nikolai Lifanov To: freebsd-stable@freebsd.org Subject: help me understand latest->quarterly pkg.conf switch Message-ID: X-Sender: lifanov@mail.lifanov.com User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 21:16:00 -0000 I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from using latest package set to whichever one that is "quarterly" word is pointing to at the moment. What is the motivation for this change? Quarterly package sets are useful if the end-user is able to pick which one to pull from and there is some amount of time of support overlap so that the user has time to validate the new package set and switch his systems to it (like what is done with pkgsrc). As-is, "quarterly" works just like "latest" from end-user perspective, but for most of the lifecycle packages are outdated and there is a massive update bomb four times per year. Port branches are still valuable to those building their own packages, since they can support the previous (unsupported by the project) branch, backporting fixes manually, while validating and upgrading to the new one. But, what is the value of the quarterly package set as-is and what is the value of switching to this set by default? - Nikolai Lifanov From owner-freebsd-stable@freebsd.org Fri Jul 24 21:18:43 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 368F29AA1E5 for ; Fri, 24 Jul 2015 21:18:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 22F461FEA for ; Fri, 24 Jul 2015 21:18:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2209F9AA1E4; Fri, 24 Jul 2015 21:18:43 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 219CA9AA1E3 for ; Fri, 24 Jul 2015 21:18:43 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 07DB51FE9 for ; Fri, 24 Jul 2015 21:18:42 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id t6OLFSEC016398; Fri, 24 Jul 2015 14:15:33 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Message-Id: <201507242115.t6OLFSEC016398@gw.catspoiler.org> Date: Fri, 24 Jul 2015 14:15:28 -0700 (PDT) From: Don Lewis Subject: Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? To: mazhe@alkumuna.eu cc: stable@FreeBSD.org In-Reply-To: <20150724071917.6a1fd3a3@freedom> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 21:18:43 -0000 On 24 Jul, Matthieu Volat wrote: > On Mon, 20 Jul 2015 14:03:01 -0700 (PDT) > Don Lewis wrote: > >> Should r282973 and r283060 be MFCed to FreeBSD 10? On amd64 and i386, >> which use clang as their base compiler and don't have gcc in base by >> default, the math/scilab port uses clang for cc and c++ compilation, >> but finds /usr/include/omp.h (and links to libgomp from lang/gcc). >> The build succeeds, but I suspect this may not run properly. > > Does it mean the door to an openmp-enabled cc in base is closed? That is probably true for FreeBSD 10, since clang 3.4 in base doesn't support OpenMP. Even though and libgomp are present in FreeBSD 10, and using base clang to compile the test program here succeeds, the resulting executable only runs one thread. There is probably more hope for FreeBSD 11 if the runtime is imported, since clang 3.6 in base there at least knows about the -fopenmp option. > I'm not fond of lang/gcc as openmp "provider": if a port use c++, it > will cause linkage headaches with libc++ (I never was able to have > graphics/darktable working, for example). You might want to try out lang/clang-devel with devel/libiomp5-devel. See this thread on freebsd-ports@ . From owner-freebsd-stable@freebsd.org Fri Jul 24 21:28:00 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 48CAE9AA3BE for ; Fri, 24 Jul 2015 21:28:00 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 371B514CE; Fri, 24 Jul 2015 21:28:00 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id AAE6F1A56; Fri, 24 Jul 2015 21:27:59 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 21:27:57 +0000 From: Glen Barber To: Nikolai Lifanov Cc: freebsd-stable@freebsd.org Subject: Re: help me understand latest->quarterly pkg.conf switch Message-ID: <20150724212757.GE84931@FreeBSD.org> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xnH/NIbSm9ew9GxF" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 21:28:00 -0000 --xnH/NIbSm9ew9GxF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote: > I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from using > latest package set to whichever one that is "quarterly" word is pointing = to > at the moment. What is the motivation for this change? >=20 This was not done in the stable/10 branch, it was done in releng/10.2. > Quarterly package sets are useful if the end-user is able to pick which o= ne > to pull from and there is some amount of time of support overlap so that = the > user has time to validate the new package set and switch his systems to it > (like what is done with pkgsrc). As-is, "quarterly" works just like "late= st" > from end-user perspective, but for most of the lifecycle packages are > outdated and there is a massive update bomb four times per year. >=20 > Port branches are still valuable to those building their own packages, si= nce > they can support the previous (unsupported by the project) branch, > backporting fixes manually, while validating and upgrading to the new one. > But, what is the value of the quarterly package set as-is and what is the > value of switching to this set by default? >=20 In general, the quarterly package set is less prone to having build failures, since the changes in the branch are (by intent) less intrusive, while still receiving security updates. It is analogous to the stable or releng branches in src, and how they compare to head. (This will be noted in the final 10.2-RELEASE announcement, as well as the release notes, and will also include instructions on how to switch to the 'latest' branch if that is what is desired.) Glen --xnH/NIbSm9ew9GxF Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsq3dAAoJEAMUWKVHj+KTe+IP/jFJlCJziPze64l6RkSl101v zpcfNDEyV2/KhAMzjPgOF5rEU1XIgU59EjmR0cipFXYu6rIBefo273yW6fwiEQnw mVhnFSLzexBonnY9ibtVDsjoTyB0SQA1Eoes0y0nvOrlrdeDLqNkFRawjgEKipmh aZsYqLB2MClzJ8uM/xADoYFnjv0VHhv//j3bmEdUBMr5Gaoy42tPWOBMSU6M/YFw LHQBprjuqk254Q7vAeas0pnO/Nc4SHkiPQTvsZdSjnls4JWPmMUcuWdE53hkEEa1 GJt9GYAnn2k4H1H4Nv17ux9G+oqK2eAlFmcrkZTJwL1vgsh6ryUAyOGb6Cz4IE+p I+da4aw63XYmLJFUAg7KZIJtOSvZ6/OSAa/5r1Wx7/AawZ9xa1C2p4XzVdFedSs1 leAcydEzCByQY4+P9BU2PFzzWFSJKwDy3Km8exMmzco8ziaLIRRKJd0uTm54xf5M 4xUQKvLT1iZ7qTBBYXBD559K6C6OxTl5Xzr9La8xtgaSmMZ0O+jtvhyVY2lL4gf2 n5Gs2UV+XOOkdNrJdXBizOf+9k6seWiVTaQHjYj5RH7UIbsoUXbveyku2FILshEG QPwyA7WiLgDo8c2s7G3sUBSo0rUVV/0cR2qjGUBdbeUbznAja+1pnAlFWX0GWx6F y/IodzJPA86BPU+ZDFrv =EM0f -----END PGP SIGNATURE----- --xnH/NIbSm9ew9GxF-- From owner-freebsd-stable@freebsd.org Fri Jul 24 21:40:39 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5501B9AA688 for ; Fri, 24 Jul 2015 21:40:39 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3D5601CB1 for ; Fri, 24 Jul 2015 21:40:39 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by mailman.ysv.freebsd.org (Postfix) id 3A1A89AA687; Fri, 24 Jul 2015 21:40:39 +0000 (UTC) Delivered-To: stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39AF89AA685 for ; Fri, 24 Jul 2015 21:40:39 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 165931CAF; Fri, 24 Jul 2015 21:40:38 +0000 (UTC) (envelope-from brooks@spindle.one-eyed-alien.net) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 6EB295A9F27; Fri, 24 Jul 2015 21:40:32 +0000 (UTC) Date: Fri, 24 Jul 2015 21:40:32 +0000 From: Brooks Davis To: Don Lewis Cc: mazhe@alkumuna.eu, stable@FreeBSD.org Subject: Re: MFC r282973 (disable libgomp build) and r283060 (disable libgcov build)? Message-ID: <20150724214032.GB27033@spindle.one-eyed-alien.net> References: <20150724071917.6a1fd3a3@freedom> <201507242115.t6OLFSEC016398@gw.catspoiler.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PEIAKu/WMn1b1Hv9" Content-Disposition: inline In-Reply-To: <201507242115.t6OLFSEC016398@gw.catspoiler.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 21:40:39 -0000 --PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 02:15:28PM -0700, Don Lewis wrote: > On 24 Jul, Matthieu Volat wrote: > > I'm not fond of lang/gcc as openmp "provider": if a port use c++, it > > will cause linkage headaches with libc++ (I never was able to have > > graphics/darktable working, for example). >=20 > You might want to try out lang/clang-devel with devel/libiomp5-devel. > See this thread on freebsd-ports@ > . Just a heads up in case you try this next week, devel/libiomp5-devel is about to be deleted and the openmp library (as well as clang-devel) will be installed by the llvm-devel port. The clang-devel port will become a metaport to aid people in finding clang while we wait for multiple packages-per-port support. -- Brooks --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJVsrDPAAoJEKzQXbSebgfAO2cH/R6XH+pzw3G7NmsdbmifiZBz Rn9jDHd2rsGxdoVqMbxeA60vB5RYiVd+TlXfTekaR9Z2xcYcJGYNzObjEer66Ter vVIMzkFedUz35d9ky75ObnHCEBxBcORhkLFeiUEn1Lcng/+9USQg+BRq+KPRUK7T bmQPY/EkQR2c+NslbpJ75fKlXYjFDF6efAB8yCo+16X0UgiJs6uGk/xqkMeZp9dH dsk5trPP0aeDR9mFejGQOIQWBpnirMc/ThIo1tLx9UAzPk4k4U9zyrrUJeEUr/rT Wb1foZyuFgRrAMmYG37C1Mj6PY5429l1oBFoaW/A7MOvyFzgVXLym46s2L387YQ= =TllG -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9-- From owner-freebsd-stable@freebsd.org Fri Jul 24 22:31:38 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1BA99AA23F for ; Fri, 24 Jul 2015 22:31:38 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id D1FED1BAC; Fri, 24 Jul 2015 22:31:38 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 4ABD5195E; Fri, 24 Jul 2015 22:31:38 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Fri, 24 Jul 2015 22:31:36 +0000 From: Glen Barber To: freebsd-stable@FreeBSD.org Cc: FreeBSD Release Engineering Team Subject: FreeBSD 10.2-RC1 Now Available Message-ID: <20150724223136.GA40557@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2015 22:31:39 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The first RC build of the 10.2-RELEASE release cycle is now available. Installation images are available for: o amd64 GENERIC o i386 GENERIC o ia64 GENERIC o powerpc GENERIC o powerpc64 GENERIC64 o sparc64 GENERIC The image checksums follow at the end of this email. FreeBSD/arm SD card images are available for: o BEAGLEBONE o CUBOX-HUMMINGBOARD o GUMSTIX o RPI-B o PANDABOARD o WANDBOARD Note: For convenience for those without console access to supported arm devices, a default 'freebsd' user exists for ssh(1) login. The password is 'freebsd', which it is strongly recommended to change after gaining access to the system. Additionally, the 'root' user password is 'root', which is also recommended to change. All images can be downloaded from: ftp://ftp.freebsd.org/pub/FreeBSD/releases/ISO-IMAGES/10.2/ If you notice problems, please report them through the Bugzilla PR system. If you would like to use SVN to do a source based update of an existing system, use the "releng/10.2" branch. A list of changes since 10.1-RELEASE are available in the release notes: https://www.freebsd.org/releases/10.2R/relnotes.html Please note, the release notes page is not yet complete, and will be updated on an ongoing basis as the 10.2-RELEASE cycle progresses. === Changes Since 10.2-BETA2 === o tcpdump(8) has been updated to obtain capsicum(4) rights for dump file rotation. o The ixgbe(4) driver has been updated to fix setting sysctl(8) tunable entries in loader.conf(5). o The ZFS txg_quiesce() function has been updated to use __noinline(), allowing DTrace monitoring for txg_quiesce() calls. o bsdinstall(8) has been updated to align partitions on 1MB boundaries when ZFS is the selected filesystem, as well as a number of other changes, including detecting BIOS versions to determine when the 'active' flag should be set on the boot partition. o The quota(1) utility has been updated to support IPv6. o The xen(4) netfront interface has been updated to preserve configurations across virtual machine migrations. o The ggatec(8) and ggatel(8) utilities have been fixed for the i386 architecture, as well as a bug in ggated(8) that would prevent the client from receiving a notice of a connection failure. o ssh(1) has been updated to canonicalize hostnames before attempting to locate it in the hosts file. o Changes to the kernel timecounter introduced earlier in stable/10 have been reverted. o The kernel DTrace has been updated to ensure locstat_nsecs() has no effect if lockstat probes are not enabled or when the profiled lock carries the LO_NOPROFILE flag. o Resource exhaustion due to sessions stuck in LAST_ACK state has been fixed, as well as a number of additional TCP fixes. [FreeBSD-SA-15:13] o The PMC Sierra SAS/SATA driver has been merged from 11-CURRENT. o The ichwd(4) driver has been updated to recognize additional Intel Lynx Point devices. o The sfxge(4) driver has been updated to support firmware versions earlier than 4.2.1. o The ping6(8) utility has been updated to include the '-x' and '-X' options in the ping(8) utility. o A bug preventing the ND6_IFF_IFDISABLED flag from clearing when the newly-added IPv6 address was /128 has been fixed. o The gif_interfaces and gifconfig examples have been removed from the default rc.conf(5). o Group membership of a cloned device when the device is moved has been fixed. o Offset calculation in variable substitution in jail.conf(5) has been fixed. o The default pkg(8) configuration file (/etc/pkg/FreeBSD.conf) has been updated to use the packages built on the quarterly branch instead of head. === Virtual Machine Disk Images === VM disk images are available for the amd64 and i386 architectures. Disk images may be downloaded from the following URL (or any of the FreeBSD FTP mirrors): ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/10.2-RC1/ The partition layout is: ~ 512k - freebsd-boot GPT partition type (bootfs GPT label) ~ 1GB - freebsd-swap GPT partition type (swapfs GPT label) ~ ~17GB - freebsd-ufs GPT partition type (rootfs GPT label) The disk images are available in QCOW2, VMDK, and raw disk image formats The image download size is approximately 135 MB, which decompress to a 20GB sparse image. Note: An issue preventing the VHD-formatted images from booting was discovered during the BETA1 build, which is still being investigated. Notes for consumers of the dvd1.iso image: o Due to human error when updating several files when the releng/10.2 branch was created, the packages on the dvd1.iso for amd64 and i386 were fetched from the 'latest' package set instead of the 'quarterly', as was intended. If using the 'latest' set is preferred, copy the default /etc/pkg/FreeBSD.conf to /usr/local/etc/pkg/repos/, and edit the configuration file as described in the comments within. The 10.2-RC2 dvd1.iso for amd64 and i386 will contain packages from the 'quarterly' package set as was intended for the 10.2-RC1. o The bsdconfig(8) utility cannot install the packages included on the DVD, however they can be installed manually. To install packages from the dvd1.iso installer, create and mount the /dist directory: # mkdir -p /dist # mount -t cd9660 /dev/cd0 /dist Replace '/dev/cd0' with the appropriate cd(4) device as necessary. Next, bootstrap pkg(8) from the DVD: # env REPOS_DIR=/dist/packages/repos \ pkg bootstrap At this point, pkg-install(8) can be used to install additional packages from the DVD. Please note, the REPOS_DIR environment variable should be used each time using the DVD as the package repository, otherwise conflicts with packages from the upstream mirrors may occur when they are fetched. For example, to install Gnome and Xorg, run: # env REPOS_DIR=/dist/packages/repos \ pkg install xorg-server xorg gnome3 [...] === Amazon EC2 AMI Images === FreeBSD/amd64 EC2 AMIs are available in the following regions: us-east-1 region: ami-a38f51c8 us-west-1 region: ami-d5da2791 us-west-2 region: ami-85868ab5 sa-east-1 region: ami-4139b65c eu-west-1 region: ami-58377d2f eu-central-1 region: ami-12d6d30f ap-northeast-1 region: ami-fe14a2fe ap-southeast-1 region: ami-a09a98f2 ap-southeast-2 region: ami-7d185947 === Azure / VM Depot Images === FreeBSD/amd64 images are available for use within the Microsoft Azure hosting platform through VM Depot. For deployment instructions, see: https://vmdepot.msopentech.com/Vhd/Show?vhdId=56718&version=59063 === Vagrant Images === FreeBSD/amd64 images are available on the Hashicorp Atlas site for the VMWare Desktop and VirtualBox providers, and can be installed by running: % vagrant init freebsd/FreeBSD-10.2-RC1 % vagrant up === Upgrading === The freebsd-update(8) utility supports binary upgrades of amd64 and i386 systems running earlier FreeBSD releases. Systems running earlier FreeBSD releases can upgrade as follows: # freebsd-update upgrade -r 10.2-RC1 During this process, freebsd-update(8) may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly. # freebsd-update install The system must be rebooted with the newly installed kernel before continuing. # shutdown -r now After rebooting, freebsd-update needs to be run again to install the new userland components: # freebsd-update install It is recommended to rebuild and install all applications if possible, especially if upgrading from an earlier FreeBSD release, for example, FreeBSD 9.x. Alternatively, the user can install misc/compat9x and other compatibility libraries, afterwards the system must be rebooted into the new userland: # shutdown -r now Finally, after rebooting, freebsd-update needs to be run again to remove stale files: # freebsd-update install == ISO CHECKSUMS == o 10.2-RC1 amd64 GENERIC: SHA256 (FreeBSD-10.2-RC1-amd64-bootonly.iso) = ac8d8c8b5d492c55e1cb8b02ef7372f14b9419a6db56fa13884f2c4517e51ec4 SHA256 (FreeBSD-10.2-RC1-amd64-bootonly.iso.xz) = fb7f40dfec96d8b143840e46d8650361e2ce6ad074035efac551bdc716808e52 SHA256 (FreeBSD-10.2-RC1-amd64-disc1.iso) = ff1447260611b503613411a7d9e768ffc73e4597fe519504749a9f0327ea5933 SHA256 (FreeBSD-10.2-RC1-amd64-disc1.iso.xz) = c89c20a603e58e19a6e29a2e73a5ed5a04ca7d3afc690dc3522e92097034ea36 SHA256 (FreeBSD-10.2-RC1-amd64-dvd1.iso) = 042b1b06ec40d6f9b468b13270d95bb1f92545732832870bc9c9c1ed8f2c4b80 SHA256 (FreeBSD-10.2-RC1-amd64-dvd1.iso.xz) = a168e2d7e6fd666f6054e7c6e1ab78688f16565b1c9eb6debdc501e84a05a3d0 SHA256 (FreeBSD-10.2-RC1-amd64-memstick.img) = a989b7910d8a4dd3a3c19b8c56ba8a2f7d5e30665942915c36faa1e72a6346c2 SHA256 (FreeBSD-10.2-RC1-amd64-memstick.img.xz) = 379cd0309a8bce7c578f5b8b81d194e6e30b9cedc15c35d86b95b917f59147cd SHA256 (FreeBSD-10.2-RC1-amd64-mini-memstick.img) = f071fa8f7f522084de060951abf75f69e60eb0d8b75d9c23003f7cb2af139071 SHA256 (FreeBSD-10.2-RC1-amd64-mini-memstick.img.xz) = 6bfbe34c25361e1024fdbc672b8919dce56eb3067daf663458d171a4ef29aab2 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-bootonly.iso) = e1094d5a4c67d091c7028dbc5440a6637911ec43dfff62ca27119b9aa65dfd03 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-bootonly.iso.xz) = 2e78628260eb980aceedf7cda526c28610456339014ceaf7dac6b163f1c7a902 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-disc1.iso) = 62c074220976a711803e1d7cbe3af82d8777f420ef8c55b783f01829ec6f3611 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-disc1.iso.xz) = ba9977420abdd1f8b73ac19aea1d353eb4bf61ea809df02ee15b43a46c9ff085 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-dvd1.iso) = e052a8381fa09f323652757d3b2719fb247ed442a93d3d775f29565224683984 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-dvd1.iso.xz) = c07240b3b1a7a989fdbffe51a694c7761bc1203bb1d3314ee088d65a04e19218 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-memstick.img) = e23de521c7cbf2cbf0a6b8ea8db949536e1c11cc25845d513b9e43d6175f3cff SHA256 (FreeBSD-10.2-RC1-amd64-uefi-memstick.img.xz) = ade06cac39ab2173ba136f91713d7d55ad5e0e3f04cf41e98c79ab1e78e52f1a SHA256 (FreeBSD-10.2-RC1-amd64-uefi-mini-memstick.img) = 29066e238e73bd058e74e6e753853ab4f4f3ee4b794a45d1c61fc50112d55252 SHA256 (FreeBSD-10.2-RC1-amd64-uefi-mini-memstick.img.xz) = 4e80adf42946b90a4bcdb48b81ccb642c9488c1ce2ef8add1b7923d13b550d3e MD5 (FreeBSD-10.2-RC1-amd64-bootonly.iso) = b4549946a066e2ec915b3883aa77d01f MD5 (FreeBSD-10.2-RC1-amd64-bootonly.iso.xz) = 549d55ab0324f25a0b2f1ec360d70ca7 MD5 (FreeBSD-10.2-RC1-amd64-disc1.iso) = c86ac4a955a211877500232b39240574 MD5 (FreeBSD-10.2-RC1-amd64-disc1.iso.xz) = 878fcdc240acad68a3e03e813bea4fbb MD5 (FreeBSD-10.2-RC1-amd64-dvd1.iso) = dbd0e9c93f54930e08ca1794e665b510 MD5 (FreeBSD-10.2-RC1-amd64-dvd1.iso.xz) = ff13f0b96c2d7408db6fd476d034a05f MD5 (FreeBSD-10.2-RC1-amd64-memstick.img) = 2a644a8176422caa075ce38f9309b8a1 MD5 (FreeBSD-10.2-RC1-amd64-memstick.img.xz) = 5d6759f8905599ebcee685eee659ce5e MD5 (FreeBSD-10.2-RC1-amd64-mini-memstick.img) = 0498b5348d97f7b138216f5c031fb1f9 MD5 (FreeBSD-10.2-RC1-amd64-mini-memstick.img.xz) = 2d40545bd0dd7ae78ce965469d4932a8 MD5 (FreeBSD-10.2-RC1-amd64-uefi-bootonly.iso) = 19315ddcd0baa9d5f8894d6f508f57b9 MD5 (FreeBSD-10.2-RC1-amd64-uefi-bootonly.iso.xz) = 1bcc81a0b3b7e0112accdb04f89e494e MD5 (FreeBSD-10.2-RC1-amd64-uefi-disc1.iso) = 687891b06fc866330d9c56f0e41ee03e MD5 (FreeBSD-10.2-RC1-amd64-uefi-disc1.iso.xz) = 34dc5e965580fcddf45ad33f02decea5 MD5 (FreeBSD-10.2-RC1-amd64-uefi-dvd1.iso) = 0e6bbfa94f0c67d04a12e45b6f2ec1b9 MD5 (FreeBSD-10.2-RC1-amd64-uefi-dvd1.iso.xz) = 485acf7d1da530bf5095d18728e36831 MD5 (FreeBSD-10.2-RC1-amd64-uefi-memstick.img) = 7d103a381914a3fa8f1bdb5f5fd48968 MD5 (FreeBSD-10.2-RC1-amd64-uefi-memstick.img.xz) = 47cc6ecf9bb83dcb04d71cf1a4fe336a MD5 (FreeBSD-10.2-RC1-amd64-uefi-mini-memstick.img) = 23688ce6b307f127dfa329678d804f08 MD5 (FreeBSD-10.2-RC1-amd64-uefi-mini-memstick.img.xz) = 1d50d622bdd1b252c29f6fda0ee41082 o 10.2-RC1 i386 GENERIC: SHA256 (FreeBSD-10.2-RC1-i386-bootonly.iso) = 84a6b08f76cec4966c4b29476868b3e34d7df834c14f3ca9a32cc2281e570c4a SHA256 (FreeBSD-10.2-RC1-i386-bootonly.iso.xz) = 2cc871a63319bd95f5a81db56f8d3834f61e0728c5ddcdd6aad2e660fb89d4fe SHA256 (FreeBSD-10.2-RC1-i386-disc1.iso) = 5a11f985306b9ebfef3daca9de26ca2e97b946f1d25d72caa2d733860de58b6c SHA256 (FreeBSD-10.2-RC1-i386-disc1.iso.xz) = 1829b0a433f4fb49ddc77e3562794f10fa63c895066d826f3efa5e11dff58ba1 SHA256 (FreeBSD-10.2-RC1-i386-dvd1.iso) = 344b20cf24fd65c9c77d5aa136cd7333176ba43c30f26b76b7c638d601730340 SHA256 (FreeBSD-10.2-RC1-i386-dvd1.iso.xz) = 15781e342d40203d672e1071527bf353304abce20960e1e7b2de36ebd0ca49d3 SHA256 (FreeBSD-10.2-RC1-i386-memstick.img) = a78948a32d87cc626848e286345a8e575d975a3bc788e830dc0f730ab4bd3bdf SHA256 (FreeBSD-10.2-RC1-i386-memstick.img.xz) = ddda2c91a8ca0a869e2c521c6518b16348b27fb5bfbb587847f7f9d23f9ec3d0 SHA256 (FreeBSD-10.2-RC1-i386-mini-memstick.img) = f2c16f9fcb9370462eb0160a2cce948c92d6fbfa91c5e905ef55757f73beb1a4 SHA256 (FreeBSD-10.2-RC1-i386-mini-memstick.img.xz) = d230f59a2a1716f4caf852c09dc94d3c25ff89f8dd5be5da26163c811209a7bc MD5 (FreeBSD-10.2-RC1-i386-bootonly.iso) = 6a7e2536496b0a6c4aa6c3dc0ee585c0 MD5 (FreeBSD-10.2-RC1-i386-bootonly.iso.xz) = 4bf3a2e8328327986de2b8a8d1818ab9 MD5 (FreeBSD-10.2-RC1-i386-disc1.iso) = da5b61e84a8be77abeea5aff189851da MD5 (FreeBSD-10.2-RC1-i386-disc1.iso.xz) = dc950142ce4e3fa9f5e4967aae190ca2 MD5 (FreeBSD-10.2-RC1-i386-dvd1.iso) = 5c40d38441f3b2498a0f52824f27d11d MD5 (FreeBSD-10.2-RC1-i386-dvd1.iso.xz) = ad37dd99a40a8f054c717723c540f6cf MD5 (FreeBSD-10.2-RC1-i386-memstick.img) = 4b05c996aaf3d93a2718d6383ab59daa MD5 (FreeBSD-10.2-RC1-i386-memstick.img.xz) = be16c0e7f772ed8b760f6a66ae5fc881 MD5 (FreeBSD-10.2-RC1-i386-mini-memstick.img) = 38702ed0bb8b08a1e5fb150d41119705 MD5 (FreeBSD-10.2-RC1-i386-mini-memstick.img.xz) = 39f19a2119d238170afdc6fa1f530cb2 o 10.2-RC1 ia64 GENERIC: SHA256 (FreeBSD-10.2-RC1-ia64-bootonly.iso) = 96d2a7fd59dc2ebab155ca378b02fad070ba433d6c3b11c384ff9a752e775d0d SHA256 (FreeBSD-10.2-RC1-ia64-bootonly.iso.xz) = b556f80718cf99a0aa991d2673b405218626ee96533aba494906eb37adb1fb58 SHA256 (FreeBSD-10.2-RC1-ia64-disc1.iso) = 3a76ed9700f579b7061bb616e3c10efc3a639ab56a48b90c7687f00093e15eb4 SHA256 (FreeBSD-10.2-RC1-ia64-disc1.iso.xz) = 361c46623a448c355e7360484e743d24b725673f48e9c7d2468d3f33039a5c35 SHA256 (FreeBSD-10.2-RC1-ia64-dvd1.iso) = 4e8bc91a58f8cc6411266bdbca31af165021592821c6d9caf1758105d2bf8b3c SHA256 (FreeBSD-10.2-RC1-ia64-dvd1.iso.xz) = c94f2ef610eb6b5175d313398e809452af68e370748cee7c3ece8cc45afd075a SHA256 (FreeBSD-10.2-RC1-ia64-memstick.img) = 91ba72841ab21c26756d4a7b189858339fcb8ce270465da6065341a03bb86ef2 SHA256 (FreeBSD-10.2-RC1-ia64-memstick.img.xz) = e7c546a90b235a36b2468f524c8e2cade5e66093c25674500ddbc6e19a3e9ad1 SHA256 (FreeBSD-10.2-RC1-ia64-mini-memstick.img) = d9831ef141eac769c8b1ed283436529fc3dac1e605b723c856a7b163dd5b2405 SHA256 (FreeBSD-10.2-RC1-ia64-mini-memstick.img.xz) = fac5a92a93e089e3fe5130c2d3d2e3e0ed88de13ec850235101b2f1a52ef0081 MD5 (FreeBSD-10.2-RC1-ia64-bootonly.iso) = d99eab54c23698856de148987a65fbc3 MD5 (FreeBSD-10.2-RC1-ia64-bootonly.iso.xz) = f722b8d73dc0aeb5c7717b71de21dcfa MD5 (FreeBSD-10.2-RC1-ia64-disc1.iso) = a252dffe64258157ce2e24a6b49568d4 MD5 (FreeBSD-10.2-RC1-ia64-disc1.iso.xz) = a6beeb3651f62907b66001446652aa76 MD5 (FreeBSD-10.2-RC1-ia64-dvd1.iso) = 8f00b5dc64a12acb95370701183a230d MD5 (FreeBSD-10.2-RC1-ia64-dvd1.iso.xz) = cb0a258bb8e57c037add010a76078419 MD5 (FreeBSD-10.2-RC1-ia64-memstick.img) = a795279e24d18725efe60febfad18760 MD5 (FreeBSD-10.2-RC1-ia64-memstick.img.xz) = 407805cda1f52375b9c574221eea0ae3 MD5 (FreeBSD-10.2-RC1-ia64-mini-memstick.img) = 0e4019cef4c4709d9b5fe7b6e32e9471 MD5 (FreeBSD-10.2-RC1-ia64-mini-memstick.img.xz) = ee86e1d2fe8cb336cec361501d85e3ce o 10.2-RC1 powerpc GENERIC: SHA256 (FreeBSD-10.2-RC1-powerpc-bootonly.iso) = 0adfe236f92a2bd8cfa8b9865669bb5e4408eb5ffd12c5a42ef3bb405fb1a04d SHA256 (FreeBSD-10.2-RC1-powerpc-bootonly.iso.xz) = 3c3bddd0a61f20f31b8e03f66b5735ccf7b800f8d4e4a8269358c5ede453762f SHA256 (FreeBSD-10.2-RC1-powerpc-disc1.iso) = fb04a13443e853f7d22492f7c300a190e6c867b3676464e05263db4bc05b3927 SHA256 (FreeBSD-10.2-RC1-powerpc-disc1.iso.xz) = ee4d50c7e705b163975f00ad2bd851b59fdcf1b1b04e14d08b6c9c2dd6cd3dc1 SHA256 (FreeBSD-10.2-RC1-powerpc-dvd1.iso) = 68a7240e60dfe94527c6da7e5b8c3bb68beadb2c65df296a0b0763edd6bf34bd SHA256 (FreeBSD-10.2-RC1-powerpc-dvd1.iso.xz) = e2761cd6a118ce0d17a61f3435715ee9305bec2682d2103bffe0028949bc7062 SHA256 (FreeBSD-10.2-RC1-powerpc-memstick.img) = 731c5c4fd087fef9e01b069ca919e72a385b41c5b15fc4d4604d079396130145 SHA256 (FreeBSD-10.2-RC1-powerpc-memstick.img.xz) = 39740ddd24ead35442dc2eb95c1fd4f3a98ad7956f4783ae6acbfcfe30a8a293 SHA256 (FreeBSD-10.2-RC1-powerpc-mini-memstick.img) = e76f15a0991388066105bd04478fbf6989ba3559b5f71b07b310f5818408b7a1 SHA256 (FreeBSD-10.2-RC1-powerpc-mini-memstick.img.xz) = e496a0639c746116ab1b27522eca14eb5bb58c3e9b83136a9ae29a57cfe3542b MD5 (FreeBSD-10.2-RC1-powerpc-bootonly.iso) = 17f3c907b62f9ffcc5fae42e87bf27fc MD5 (FreeBSD-10.2-RC1-powerpc-bootonly.iso.xz) = a1b260dac17c5bfd78bb0de02b690446 MD5 (FreeBSD-10.2-RC1-powerpc-disc1.iso) = f2dcd4094803dea09d6f4f994b4f7ced MD5 (FreeBSD-10.2-RC1-powerpc-disc1.iso.xz) = fdc8c0ae6f8d70c2b2478c61e2512e6c MD5 (FreeBSD-10.2-RC1-powerpc-dvd1.iso) = efa42360dc71601b984d6715c41b4bb2 MD5 (FreeBSD-10.2-RC1-powerpc-dvd1.iso.xz) = 4af4b1d6af9c5cefa22a5e8e1c1cc7f7 MD5 (FreeBSD-10.2-RC1-powerpc-memstick.img) = 2a6d42abc24a555c931eb1e1968bddb8 MD5 (FreeBSD-10.2-RC1-powerpc-memstick.img.xz) = f3f65e3ffc9da3124224dae65e4b61b0 MD5 (FreeBSD-10.2-RC1-powerpc-mini-memstick.img) = 153aed772e505108125ba3896fe530ba MD5 (FreeBSD-10.2-RC1-powerpc-mini-memstick.img.xz) = 444bb67f71dee387e36ed656069fbf99 o 10.2-RC1 powerpc64 GENERIC64: SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-bootonly.iso) = 7d0c1d09252caa4935a355ee05b60e763f39a26a8307e008f9ff3774d261683c SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-bootonly.iso.xz) = 928dced6ad39d63ffedc69a4c641c69cc4e751a55146846c672a066eda1a19b8 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-disc1.iso) = 24cdbd44be2bf1c7aa67909b121e4acdc2db83e5373f1971a5b647cd16d91281 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-disc1.iso.xz) = 155bff039f36fab5548c9441c6747eb297f300a5e25a9e7803225195f735e523 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-dvd1.iso) = fee83010b822eda81a890bf12e032fb7dade2419265734ddb47ae8a7df3f3151 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-dvd1.iso.xz) = 10c21b9a259df430ac507b9d16c693b3f9934546bbf395461dae6e5b50a24155 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-memstick.img) = 244692415c563ea72fa8b3cc3af60da304e8b17e1b606e7656444ea77f8eebc0 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-memstick.img.xz) = dbac42e6370fe15292766b81c21fe3cefcf9e63c9e5bec08dc053be94580df54 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-mini-memstick.img) = 68cf6ffa0c7b37a263d73f3129fdf91d8df22da29f585479647970f1041f73c2 SHA256 (FreeBSD-10.2-RC1-powerpc-powerpc64-mini-memstick.img.xz) = c21e7fb7b7ce63d1fc712f030b4121fae43d3860f39d68896034a890a340a93f MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-bootonly.iso) = a195b429fbffddb25b94f5121e8eb306 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-bootonly.iso.xz) = 6ebc71a0873bbd77055103e2b4c74b50 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-disc1.iso) = 45484d14c2be404fd707d79ad19654df MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-disc1.iso.xz) = 337b67ff744a7ec57b762745a560fef8 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-dvd1.iso) = d0e03d6c5fc7735218bb3f76b5d6a850 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-dvd1.iso.xz) = 1ae648974c5e9406a8832d1eac24f500 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-memstick.img) = 93e9b7f89dbf169441e47a9e9134ba01 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-memstick.img.xz) = ea3b5ad2aed9fb3e2cdb2dea52c9fc0a MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-mini-memstick.img) = 27784315df5035c8334b8371730d9628 MD5 (FreeBSD-10.2-RC1-powerpc-powerpc64-mini-memstick.img.xz) = ddbdd06d199a11d749428430445f73fe o 10.2-RC1 sparc64 GENERIC: SHA256 (FreeBSD-10.2-RC1-sparc64-bootonly.iso) = b452c3041fbe2e52abd905c89e5c0507011710fb5f53e0055ae053cfe62c0c05 SHA256 (FreeBSD-10.2-RC1-sparc64-bootonly.iso.xz) = 62f040805ad3d4e85e24f091789fa6f4a85e585ee1e8c88d3f32198fc4420e3c SHA256 (FreeBSD-10.2-RC1-sparc64-disc1.iso) = 212a4d8661be95645d7221c4836f9aa6c3ef5e764a0c6f0ac331b25e0b76ad19 SHA256 (FreeBSD-10.2-RC1-sparc64-disc1.iso.xz) = 05089f036d0505a7914a85336b48c33a94eeaefb338cfab1346e324d242f0072 SHA256 (FreeBSD-10.2-RC1-sparc64-dvd1.iso) = f8f2278d7f0fd24689ee547cb3fe03c6ea79dca88617b55316ca891cefb4b724 SHA256 (FreeBSD-10.2-RC1-sparc64-dvd1.iso.xz) = 706043a783990e7c1218292d9f3b0ff4726e0152cc4e4ae64a7aafa88253edd1 MD5 (FreeBSD-10.2-RC1-sparc64-bootonly.iso) = 1e6dbfc8ebbaa2be480c5feedd9183b1 MD5 (FreeBSD-10.2-RC1-sparc64-bootonly.iso.xz) = ab43d74591869e7779a81c794e09620f MD5 (FreeBSD-10.2-RC1-sparc64-disc1.iso) = 29a6dd38f44f9dcb7c2dffd1860a2b2f MD5 (FreeBSD-10.2-RC1-sparc64-disc1.iso.xz) = 534deaf084ec62d3991f56113addd9f8 MD5 (FreeBSD-10.2-RC1-sparc64-dvd1.iso) = 7150e686233ae02731c8c479fbb263e1 MD5 (FreeBSD-10.2-RC1-sparc64-dvd1.iso.xz) = 0795d0f1cc89e97928d6a53939729d0a o 10.2-RC1 armv6 BEAGLEBONE: SHA256 (FreeBSD-10.2-RC1-arm-armv6-BEAGLEBONE.img.xz) = 03c00434cf3b5b3f578bc883c642145ffdfa8c611e29ad83482fb9e2aa85d899 MD5 (FreeBSD-10.2-RC1-arm-armv6-BEAGLEBONE.img.xz) = 1e38693776f254d3cd645aee157bb4ec o 10.2-RC1 armv6 CUBOX-HUMMINGBOARD: SHA256 (FreeBSD-10.2-RC1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = cd58be1a3deb97f0f88b63cc8b9bc11969a2b1be4439115188000106024ded85 MD5 (FreeBSD-10.2-RC1-arm-armv6-CUBOX-HUMMINGBOARD.img.xz) = 64eb3c51a41195eda16174e5ee9d3e81 o 10.2-RC1 armv6 GUMSTIX: SHA256 (FreeBSD-10.2-RC1-arm-armv6-GUMSTIX.img.xz) = aeaf2b941719352c086f97663dc0ff76225aaa3d1059aa817a97a7136d844a11 MD5 (FreeBSD-10.2-RC1-arm-armv6-GUMSTIX.img.xz) = e600d0a33d03a292c366b77be6573445 o 10.2-RC1 armv6 RPI-B: SHA256 (FreeBSD-10.2-RC1-arm-armv6-RPI-B.img.xz) = fb5752fc4636bf346dee8946abb15c4bfcc128cb5fd015f0a1818c1ea3533c59 MD5 (FreeBSD-10.2-RC1-arm-armv6-RPI-B.img.xz) = 88c7d652ac7b478270313c89144f9ffe o 10.2-RC1 armv6 PANDABOARD: SHA256 (FreeBSD-10.2-RC1-arm-armv6-PANDABOARD.img.xz) = 63fa6b8a14dfa37a5309dee2ad84bf3e90ecb49f67c2ede1f3b8a154fb1b50a8 MD5 (FreeBSD-10.2-RC1-arm-armv6-PANDABOARD.img.xz) = 19437d20fed81520b9c4204b3d240033 o 10.2-RC1 armv6 WANDBOARD: SHA256 (FreeBSD-10.2-RC1-arm-armv6-WANDBOARD.img.xz) = 10b87b102cad7ad3a8ae828c4792cd267db70d6c6106c979a2a3b65c14f0cf7b MD5 (FreeBSD-10.2-RC1-arm-armv6-WANDBOARD.img.xz) = 16f899500baaf098e232ff8e992c9101 == VM IMAGE CHECKSUMS == o 10.2-RC1 amd64: SHA256 (FreeBSD-10.2-RC1-amd64.qcow2.xz) = aa6273eb1a6d498bb4bf533c6f48b9cd87ed6890091a82f8daa39fd450a7d6e5 SHA256 (FreeBSD-10.2-RC1-amd64.raw.xz) = 74cd623bdc862a636f07b932632986da0b0ef949528371d059efdfd1a489875d SHA256 (FreeBSD-10.2-RC1-amd64.vhd.xz) = 3f407e5a358094a0e001e2b3b9e8ce16fdc411756f2a3888950a98a250c921d8 SHA256 (FreeBSD-10.2-RC1-amd64.vmdk.xz) = 7fc02b050a43bff66b947a7fb47e97502afb5e1dd1073da7167dae8dddd1c5b3 MD5 (FreeBSD-10.2-RC1-amd64.qcow2.xz) = 2ead1db242a736642464041cec667f53 MD5 (FreeBSD-10.2-RC1-amd64.raw.xz) = b52b07f89d1193625fb4843fdad4a545 MD5 (FreeBSD-10.2-RC1-amd64.vhd.xz) = ce38488866b41b4d0ac03b4c5f1c5354 MD5 (FreeBSD-10.2-RC1-amd64.vmdk.xz) = 37be40becd245aeb5318631395e6a16a o 10.2-RC1 i386: SHA256 (FreeBSD-10.2-RC1-i386.qcow2.xz) = 815fc3b2ddae7c69e9f231531490d7711da282d13c2cbc16fc4e9e1ce5d6f2ea SHA256 (FreeBSD-10.2-RC1-i386.raw.xz) = dc62f8d71c1533e5705778bd90e494e30a262c6a615ff49ebf468deefae7c41f SHA256 (FreeBSD-10.2-RC1-i386.vhd.xz) = 8ec9327fff0b3c01fc97c735bf785130db6b67e5a1147c447860fea35901f9e6 SHA256 (FreeBSD-10.2-RC1-i386.vmdk.xz) = 0e3c95799359e7077951ef341ed0b051d097017a9aa02cbab9e7301c3572b048 MD5 (FreeBSD-10.2-RC1-i386.qcow2.xz) = 3471ac076411bd0005411e032d3c3f14 MD5 (FreeBSD-10.2-RC1-i386.raw.xz) = acdf3213262bac82b56ec2035a61aa6c MD5 (FreeBSD-10.2-RC1-i386.vhd.xz) = 0cee9bd8e26ad30ac0e420dc0d974a22 MD5 (FreeBSD-10.2-RC1-i386.vmdk.xz) = 55a01cab45ad55f8dceedf07bb1e0344 Regards, Glen Love FreeBSD? Support this and future releases with a donation to the FreeBSD Foundation! https://www.freebsdfoundation.org/donate/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsrzIAAoJEAMUWKVHj+KT5kIP/j14YcUPmDDID/vdsbgYwHC0 hOh6t70ReaFUtLerAJwcf6kLoEucdiGjv7uJmnQHxgBgGevEktNrKYtr7IhJYfC6 lbqsF+qph6ieEzUgVDqog8d6MkKUaME4R3lz4tG6YrVGK5Al9wugC8264VKXJ+Pw fQNVd6yASc6vnZes91jBapblSHOWuYJMCRF2obZif7IPebu0Qxfm/MTk4ZYH4LKG +o09kBLU8o8HtDiU37LQaY++d+QF17gANROdeFXVaa/7MQmavazgOWq0tfV73Fsf gelu5puFQeXE9PPdOEhMdEMEn99HFljBzUVnQOn4RI9nbLJGXm3DJumr72xdkvUO l96JugOUuJG5P2vM4CZFWFWfCI4SJ86pJNM6A9hdCUyVCgg0mrQTrIw3grbQwwKZ TXpBqDcusDbGgpZHUvQriSwDW2AVGiOcte9jDi7gkkMnidAFUuaFz4pzmProjcX8 H8gUjusvP/fdRpGa1G2iGORplFadhlIhK8RRr3ONT24mijHXQE/zjhuQ+fM/5rvF elBPrhZvcajLaigdIk5P9O1A2yWnHRDrGtw8Dt9T3p3nMNqwU1TWgRmjpl8NECrU aOkHewYW50GpYpCgicpFN+876m2ENhRGECj60RVq0tb81Ps05ic9Z2l0RRF57KLz SkWU6UYcf6ZzNHXMfHAf =VlU8 -----END PGP SIGNATURE----- From owner-freebsd-stable@freebsd.org Sat Jul 25 01:23:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70BF39AAF0B for ; Sat, 25 Jul 2015 01:23:16 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: from mail.lifanov.com (mail.lifanov.com [206.125.175.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 557BBB25; Sat, 25 Jul 2015 01:23:16 +0000 (UTC) (envelope-from lifanov@mail.lifanov.com) Received: by mail.lifanov.com (Postfix, from userid 58) id EA0651F68B6; Fri, 24 Jul 2015 21:23:13 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.lifanov.com X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.1 Received: from app.lifanov.com (chat.lifanov.com [206.125.175.13]) by mail.lifanov.com (Postfix) with ESMTPA id 690351CB365; Fri, 24 Jul 2015 21:23:13 -0400 (EDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 24 Jul 2015 21:23:12 -0400 From: Nikolai Lifanov To: Glen Barber Cc: freebsd-stable@freebsd.org Subject: Re: help me understand latest->quarterly pkg.conf switch In-Reply-To: <20150724212757.GE84931@FreeBSD.org> References: <20150724212757.GE84931@FreeBSD.org> Message-ID: X-Sender: lifanov@mail.lifanov.com User-Agent: Roundcube Webmail/1.1.2 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 01:23:16 -0000 On 2015-07-24 17:27, Glen Barber wrote: > On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote: >> I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from >> using >> latest package set to whichever one that is "quarterly" word is >> pointing to >> at the moment. What is the motivation for this change? >> > > This was not done in the stable/10 branch, it was done in releng/10.2. > >> Quarterly package sets are useful if the end-user is able to pick >> which one >> to pull from and there is some amount of time of support overlap so >> that the >> user has time to validate the new package set and switch his systems >> to it >> (like what is done with pkgsrc). As-is, "quarterly" works just like >> "latest" >> from end-user perspective, but for most of the lifecycle packages are >> outdated and there is a massive update bomb four times per year. >> >> Port branches are still valuable to those building their own packages, >> since >> they can support the previous (unsupported by the project) branch, >> backporting fixes manually, while validating and upgrading to the new >> one. >> But, what is the value of the quarterly package set as-is and what is >> the >> value of switching to this set by default? >> > > In general, the quarterly package set is less prone to having build > failures, since the changes in the branch are (by intent) less > intrusive, while still receiving security updates. It is analogous to > the stable or releng branches in src, and how they compare to head. > > (This will be noted in the final 10.2-RELEASE announcement, as well as > the release notes, and will also include instructions on how to switch > to the 'latest' branch if that is what is desired.) > > Glen Cool, thanks for the explanation! What would be really amazing to see are quarterly branches that the end user can switch between, like pkg.freebsd.org/${ABI}/2015Q3 -> pkg.freebsd.org/${ABI}/2015Q4 when he is ready, with at least a little bit of overlap. Thanks Glen! - Nikolai Lifanov From owner-freebsd-stable@freebsd.org Sat Jul 25 02:04:42 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A741D9A95D8 for ; Sat, 25 Jul 2015 02:04:42 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7BA18DF; Sat, 25 Jul 2015 02:04:42 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 0A3A817FA; Sat, 25 Jul 2015 02:04:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 25 Jul 2015 02:04:40 +0000 From: Glen Barber To: Nikolai Lifanov Cc: freebsd-stable@freebsd.org Subject: Re: help me understand latest->quarterly pkg.conf switch Message-ID: <20150725020440.GJ84931@FreeBSD.org> References: <20150724212757.GE84931@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="U5yJ31ax00IavOwq" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 02:04:42 -0000 --U5yJ31ax00IavOwq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 09:23:12PM -0400, Nikolai Lifanov wrote: > On 2015-07-24 17:27, Glen Barber wrote: > >On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote: > >>I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from > >>using > >>latest package set to whichever one that is "quarterly" word is pointing > >>to > >>at the moment. What is the motivation for this change? > >> > > > >This was not done in the stable/10 branch, it was done in releng/10.2. > > > >>Quarterly package sets are useful if the end-user is able to pick which > >>one > >>to pull from and there is some amount of time of support overlap so that > >>the > >>user has time to validate the new package set and switch his systems to > >>it > >>(like what is done with pkgsrc). As-is, "quarterly" works just like > >>"latest" > >>from end-user perspective, but for most of the lifecycle packages are > >>outdated and there is a massive update bomb four times per year. > >> > >>Port branches are still valuable to those building their own packages, > >>since > >>they can support the previous (unsupported by the project) branch, > >>backporting fixes manually, while validating and upgrading to the new > >>one. > >>But, what is the value of the quarterly package set as-is and what is > >>the > >>value of switching to this set by default? > >> > > > >In general, the quarterly package set is less prone to having build > >failures, since the changes in the branch are (by intent) less > >intrusive, while still receiving security updates. It is analogous to > >the stable or releng branches in src, and how they compare to head. > > > >(This will be noted in the final 10.2-RELEASE announcement, as well as > >the release notes, and will also include instructions on how to switch > >to the 'latest' branch if that is what is desired.) > > > >Glen >=20 > Cool, thanks for the explanation! >=20 You're welcome. (The 'quarterly' branch is admittedly under-documented, which is a problem.) > What would be really amazing to see are quarterly branches that the end u= ser > can switch between, like pkg.freebsd.org/${ABI}/2015Q3 -> > pkg.freebsd.org/${ABI}/2015Q4 when he is ready, with at least a little bit > of overlap. >=20 I agree this would be a "nice to see" feature, but as I have insight into how the pkg(8) mirrors operate, this is an unfortunately non-trivial thing to implement. Glen --U5yJ31ax00IavOwq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsu64AAoJEAMUWKVHj+KTR7gQAJZOF/afm7a4HsmKD+L/Pk1/ HXtL6nNHxWuDCSPOd92LPSe6/mvo1phrLD9WEBA3HiwkNciidpwNxRg2Ru/sTxYl dbnzA7aG6AK+5AeWt2BuSBwCrIEEzR8pEBI8+zoNGJXoWLTRXh3CoDa9r6d3Xg5/ W+P8079ZeKiKA2RU/QdLIV20mxxWKK0Ie6zuEghvnrpbHReqkbkZsLoYkanH5NH9 ZhyaOt1A7yJ74lNvcVqByUN3BmvFVIkJTuNNVYAXKM1jLIqWyqgsHOqbj+yPi/OR LjbXZNQZyyRAxctDsB8OHX4Y3V4AbJCE11yo1hsTYZBkDWMNIapb+VKpNM7gbLYG QEb4R8Lj+Q+vdUNAUHq3E0vb6xgclwSQmFOd3hRwp9OfX+LwYwMTU28w68FKI4Sm rXkaVljmh5UrKiRJOccAgqm7DFJ2QHVhxXg62IWsNa0kWwYXl+bqa4YTmX/WwlU6 3w2xJhqSQBg+WyvsNJft3pEI9Il+MyoRwyVKs2HEJ9Hswow9f++OhKE3n8nfTHtX FFKH3i5aumyFiW3jyM4zpg2FsxC36JGEJcOcxeoqCGXHTaWENY/dFVkr3twpv1CF qwvNt58K4YExgSbgy4ffW+rKCRtoKPm9YJKanjyNSaEFpFhxYjDpgv/291BhI4Gv 4nC4M6scUzWrtFS8Pejc =Hc2Y -----END PGP SIGNATURE----- --U5yJ31ax00IavOwq-- From owner-freebsd-stable@freebsd.org Sat Jul 25 02:27:53 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80BDF9A9B2D for ; Sat, 25 Jul 2015 02:27:53 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 6CDEB39F; Sat, 25 Jul 2015 02:27:53 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 98E291C2F; Sat, 25 Jul 2015 02:27:52 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 25 Jul 2015 02:27:50 +0000 From: Glen Barber To: Slawa Olhovchenkov Cc: Xin Li , re@FreeBSD.org, d@delphij.net, freebsd-stable@freebsd.org Subject: Re: freebsd downgrade Message-ID: <20150725022750.GC33184@FreeBSD.org> References: <1437693686.78236.2.camel@yandex.com> <55B17DEB.6070302@delphij.net> <20150724072052.GF43740@zxy.spb.ru> <55B1EC8F.7050304@delphij.net> <20150724075010.GG43740@zxy.spb.ru> <20150724152555.GB4276@ox> <20150724153632.GH43740@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PuGuTyElPB9bOcsM" Content-Disposition: inline In-Reply-To: <20150724153632.GH43740@zxy.spb.ru> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 02:27:53 -0000 --PuGuTyElPB9bOcsM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 06:36:32PM +0300, Slawa Olhovchenkov wrote: > On Fri, Jul 24, 2015 at 08:25:55AM -0700, Navdeep Parhar wrote: >=20 > > On Fri, Jul 24, 2015 at 10:50:10AM +0300, Slawa Olhovchenkov wrote: > > > > >=20 > > > > > For me -- degradate network performance, about 30%. I am do > > > > > verification now, by downgrading kernel. > > > >=20 > > > > What kind of workload and what NIC are you using? > > >=20 > > > Chelsio T580-LP-CR, http serving. > > > r276179 can utilise 40Gbit, r281264 -- only 28Gbit. > >=20 > > Can you please try -RC1 when it comes out and report back if you still > > see degraded network performance?=20 >=20 > Now I am try revisons r276179 and compare with r281264 (for absolutly > clean compare -- same hardware, same configuration, same workload) > before this I am comare slighty different hardware (card instaled in > different slots) and posibly different workload. > After this I am try r278800 and RC1 -- one times per day. >=20 Please try with the 10.2-RC1 that was just released, and report back. Thanks. Glen --PuGuTyElPB9bOcsM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsvQmAAoJEAMUWKVHj+KT6aAP/1gF9h0w8OzsU2PUARUEh8o7 usbQIKfnBaUQHwz3o5DJ4cFtjPvcjc67wRF7tq3t+/1dFfEAx50c+5pjkMjsIR6E pgZPczb1LEykS/vYRt2KI4diesLT/Tc7irY1VgrujEhJJFPaDTq1LDHd2nOBInBe ftk3vH7Y0KtNBvskLX7TiDbkiCd8ObSuiKeF4gzy0bfpTz4ZYSCX9MJRBWtMxNTa 7CVVZK86BigVy0+GEGd3ss9awF4hwPd5xRqaP5zo90V9QC0fzspeTjJyvuzrI+Eb 0BK26yOqcPAHztTQYaM7ZZimzop52nySMTvL1Qkx/yawUpi3d1GWNHbyxagZpxP1 7nmZJiNTFERH1MJJA2nBk7vYafhfmdfUmlaBXt50YpUZu3X2E54EOGn6t7yRiNPI bTZgjgW8KuHuvWFOd/IZJrQfSsmDVTDI8tmEWu+zS67NwHlrk0FJkhtXqgmdLf47 SfkkIBjzHn1k1+/v1GSn6BFY2LJOY8osQo25itnTphUX6Wrtq+Z5WLhvrVkfBWgh VPdI7vUMqjYUoviYf5oz7KSFhO1ucUAll6DqqYoSkmXCMmq+7+YuPXp0hsROMMBp wuG2p6Zmqcr2gz2biOK3XrA3GrI2K7tPMGi29dfYQ1/GG6C6op6N9HN6Hh9cupsn 6VRNO7iXb03R/QWLR6fN =SwU5 -----END PGP SIGNATURE----- --PuGuTyElPB9bOcsM-- From owner-freebsd-stable@freebsd.org Sat Jul 25 09:31:12 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8C1D79A9C77 for ; Sat, 25 Jul 2015 09:31:12 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward12p.cmail.yandex.net (forward12p.cmail.yandex.net [87.250.241.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AED1C4B for ; Sat, 25 Jul 2015 09:31:11 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web13g.yandex.ru (web13g.yandex.ru [95.108.252.113]) by forward12p.cmail.yandex.net (Yandex) with ESMTP id D89C721CB5 for ; Sat, 25 Jul 2015 12:30:49 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web13g.yandex.ru (Yandex) with ESMTP id 892773300072; Sat, 25 Jul 2015 12:30:49 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437816649; bh=Cj1kHXZjVTZSye33pyNcHWbROggBUO3j/4Henk9d7PQ=; h=From:To:Subject:Date; b=lj7SpNdGoLATsC8odDmYzume3NHYqNKS+xqBCkPYT6LfAOsNF3NfzlTLW4uB/iIvB zoulxibTopXMJmU8EInyn9fAsDmxBFNBoyGpf3R9uvg84ej3WeYLdJBCISXs8MJoaA ITqZa2pSICJlX/PUHPODVwze3RObMlouUHL4jU+k= Received: by web13g.yandex.ru with HTTP; Sat, 25 Jul 2015 12:30:48 +0300 From: deco33000@yandex.com To: freebsd-stable Subject: How is the time fed between hardclocks ? MIME-Version: 1.0 Message-Id: <894501437816648@web13g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 25 Jul 2015 11:30:48 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 09:31:12 -0000 Hello, I am learning the freebsd way to keep the time up to date. We avoid to call hardware hardclock() every time we need a timestamp by applying some math. I get the idea. But, how do we know how far we are from the last hardclock()? Are the updates to the "fake" timestamps occuring at a constant rate? This is the last -and most important- point I don't get. Thanks --š Jog From owner-freebsd-stable@freebsd.org Sat Jul 25 10:27:59 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F6A49A8712 for ; Sat, 25 Jul 2015 10:27:59 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from forward16p.cmail.yandex.net (forward16p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::bf]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B3D1710D5 for ; Sat, 25 Jul 2015 10:27:58 +0000 (UTC) (envelope-from starikarp@yandex.com) Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [IPv6:2a02:6b8:0:1402::118]) by forward16p.cmail.yandex.net (Yandex) with ESMTP id 8012E21AFE for ; Sat, 25 Jul 2015 13:27:55 +0300 (MSK) Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id 4E10D1900DB7 for ; Sat, 25 Jul 2015 13:27:55 +0300 (MSK) Received: by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id hnNI5eIZZD-RqTmPgnA; Sat, 25 Jul 2015 13:27:53 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437820074; bh=N/9nNrKYTslqdNeR6r3fKrezxWXmAvM9TUNtFNDRSY8=; h=Message-ID:Subject:From:To:Date:In-Reply-To:References: Content-Type:X-Mailer:Mime-Version:Content-Transfer-Encoding; b=RTE33xxMJFkrVxpcf9UDrY8wSGSAqZsXrtKhIhZeBsWs0Rz1vjec49o1x2yCsIvoL CbmC+OLlkji2XiiZZvv0cfQQTFj2nqGzQotG6aIx3rVlevJwC+uw9KD7Gzzpv8Hmmm nNAmao3tvSMNZWZ0ydESXfkqOJvQbcLjPJ6MaywY= Authentication-Results: smtp17.mail.yandex.net; dkim=pass header.i=@yandex.com Message-ID: <1437820068.53552.3.camel@yandex.com> Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Stari Karp To: freebsd-stable@freebsd.org Date: Sat, 25 Jul 2015 06:27:48 -0400 In-Reply-To: <1437769050.2088.3.camel@yandex.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437754678.41896.0.camel@yandex.com> <1437769050.2088.3.camel@yandex.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.12.11 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 10:27:59 -0000 On Fri, 2015-07-24 at 16:17 -0400, Stari Karp wrote: > > >> > > >> > 1. VT module doesn't load. > > >> > In /boot/loader.conf I have: > > >> > kern.vty=vt > > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I > > >> > got just black screen and nothing more. > > >> I saved the problem. The BETA2 make some ">>>" and "******" in device.hints and it was error to reading them. I didn't saw before. Today I also update to RC1 and works good. Thank you for the help. -- ajtiM ----- http://www.redbubble.com/people/lumiwa https://www.facebook.com/pages/Lumiwa-FARM/775292915882930?_fb_noscript=1 From owner-freebsd-stable@freebsd.org Sat Jul 25 10:31:19 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 55E129A8945 for ; Sat, 25 Jul 2015 10:31:19 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D85A41660 for ; Sat, 25 Jul 2015 10:31:18 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by lagw2 with SMTP id w2so26303075lag.3 for ; Sat, 25 Jul 2015 03:31:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PdCmn5V/phCai72L/ZBy4Gr5TL7DO+1wpGMn9NLd7m0=; b=Ai8UhiNXIxcngaW7PZ//kOE+McsxxFj0rnCBq3b6ovsvJXenLMg0t8v5AIrAzJkmhm hZK2ekYMmLQV8a7l71K42CEWwyCwrdyZ3J7Zin/UN+CPlwbe69yl1g5dlUMSvLCoYCAi 3k2yMIXAl02QUK4dlOt8U81qJpbalINO9hTQ3aJbG41DIDvBSibxyZ6xFiXQgtHQoqS8 CLAJmKEAUhpHOkxCeqvapwYKTgNyEmbDTFt+k3TKoYfJXJ4b6UIVhagbf305HOotWwiq BDEiRGuIAx2yHhreiKHKdzopO2CYUewvPxe4kATk2zTyS9ePDEYDHw8D3Had6m38xvoA 9wJg== MIME-Version: 1.0 X-Received: by 10.112.12.102 with SMTP id x6mr18233473lbb.80.1437820275762; Sat, 25 Jul 2015 03:31:15 -0700 (PDT) Received: by 10.152.219.35 with HTTP; Sat, 25 Jul 2015 03:31:15 -0700 (PDT) In-Reply-To: <1437820068.53552.3.camel@yandex.com> References: <1437602017.1621.5.camel@yandex.com> <1437745202428-6027559.post@n5.nabble.com> <1437754678.41896.0.camel@yandex.com> <1437769050.2088.3.camel@yandex.com> <1437820068.53552.3.camel@yandex.com> Date: Sat, 25 Jul 2015 13:31:15 +0300 Message-ID: Subject: Re: FreeBSD 10.1_RELEASE to FreeBSD 10.2 BETA2 From: Kimmo Paasiala To: Stari Karp Cc: "freebsd-stable@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 10:31:19 -0000 On Sat, Jul 25, 2015 at 1:27 PM, Stari Karp wrote: > On Fri, 2015-07-24 at 16:17 -0400, Stari Karp wrote: > >> > >> >> > >> > 1. VT module doesn't load. >> > >> > In /boot/loader.conf I have: >> > >> > kern.vty=vt >> > >> > but it doesn't work. If I manual loada module witk kldload radeonkms I >> > >> > got just black screen and nothing more. >> > >> > > I saved the problem. The BETA2 make some ">>>" and "******" in > device.hints and it was error to reading them. I didn't saw before. > Today I also update to RC1 and works good. > > Thank you for the help. > > -- > ajtiM > ----- > http://www.redbubble.com/people/lumiwa > https://www.facebook.com/pages/Lumiwa-FARM/775292915882930?_fb_noscript=1 > > That's freebsd-update(8)'s doing if you skip the merge questions too hastily. Take note about them next time and make sure the merges are done correctly, otherwise you'll end up with messed up configuration files. -Kimmo From owner-freebsd-stable@freebsd.org Sat Jul 25 11:08:16 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05A689AA610 for ; Sat, 25 Jul 2015 11:08:16 +0000 (UTC) (envelope-from alnis.morics@gmail.com) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6A68D1CF1 for ; Sat, 25 Jul 2015 11:08:15 +0000 (UTC) (envelope-from alnis.morics@gmail.com) Received: by lahh5 with SMTP id h5so26592062lah.2 for ; Sat, 25 Jul 2015 04:08:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=hKXEVjHXUo+CK0LnqHYcUT3yuMRK29xRImY9v/+bCi8=; b=DWm2FU2jesk0yKg6Hb8rRmpidudzVjR8/rHWP/TlWutfBcmEx6cad149r3br8RE/9V ARnEaYx1AzusNKsUOuToZP9zkH0HYmBjiZadYoZW6GWU+0FCA46wKoeaRPXB05aZV8PX wjDE/ywIsGQCd0C9zbi5lMhQ210pwEz/hLsRXTNVI5Oe0XK/b8NXy/uY6fkfkZPZyTxX y2b8S39bmNE9ZJ1DdNIJPwJJEeyl8OXTKsCHd3225CDKN6EeaMUAaMAf0km9Fhb3UqlP SEvE0kvSon1oad/49HfegXm0j7eB91FZ1BLMLMxLNI6YIcyb9RQXjvpkutUcEmelGLJa SMGQ== X-Received: by 10.112.47.73 with SMTP id b9mr17987017lbn.46.1437822493173; Sat, 25 Jul 2015 04:08:13 -0700 (PDT) Received: from [192.168.2.192] ([78.84.244.14]) by smtp.googlemail.com with ESMTPSA id z1sm2502260lbj.11.2015.07.25.04.08.11 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 25 Jul 2015 04:08:12 -0700 (PDT) Message-ID: <55B36E1A.3040806@gmail.com> Date: Sat, 25 Jul 2015 14:08:10 +0300 From: Alnis Morics User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem References: , <20150413081348.GA965@michelle.fasterthan.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 11:08:16 -0000 On 04/16/2015 12:52 AM, Gareth Wyn Roberts wrote: > I've inserted code to print some values which show the differences between specifying 4096 or 8192 for MSK_STAT_ALIGN. In both cases the status buffer has length 0x4000 (8x2048=16K) but the alignments are different as expected, respectively start addresses 0x5c3b000 or 0xbdc2c000. > > The following values were output from functions msk_status_dma_alloc(), msk_dmamap_cb() and msk_handle_events(). > The "Break #n" refer to breaks in msk_handle_events(). "#1" occurs if ((control & HW_OWNER) == 0), "#5" is OP_RXSTAT and "#6" is OP_TXINDEXLE. > > The first output is for MSK_STAT_ALIGN=8192. It continues normally. Although not shown here, it reaches cons=2047 then cons=0 as expected. > > The second output is for MSK_STAT_ALIGN=4096. Although there can be isolated occurences of "Break #1" (e.g. cons=196) (?are these to be expected?), it continues normally until cons=512. At this point it continually invokes the "#1" block because the msk_control from msk_stat_ring[512] is always zero and the network hangs immediately. This suggests the Yukon Ultra 2 88E8057 can't access the next 4096 memory block, but why not? > > Please let me know if any further information would be helpful. > > ------------ Start of MSK_STAT_ALIGN=8192 output ----------------------------- > > mskc0: mem 0xfa000000-0xfa003fff irq 19 at device 0.0 on pci6 > mskc0: Successful creation of DMA tag > mskc0: sc->msk_stat_count=2048 > mskc0: stat_sz=16384 > mskc0: sc->msk_stat_tag=0xfffff800050b99a0 > mskc0: Successful allocation of DMA'able memory for status ring > mskc0: sc->msk_stat_map=0xfffff800050b99a8 > msk_dmamap_cb (stat): nseg=1 > msk_dmamap_cb (stat): error=0 > msk_dmamap_cb (stat): segs[0].ds_addr=3183656960=0xbdc2c000 > msk_dmamap_cb (stat): segs[0].ds_len=16384=0x4000 > mskc0: Successful load of DMA'able memory for status ring > mskc0: sc->msk_stat_ring_paddr=3183656960=0xbdc2c000 > msk0: on mskc0 > msk0: Ethernet address: 00:13:77:e9:df:eb > miibus0: on msk0 > e1000phy0: PHY 0 on miibus0 > e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > ... > mskc0: msk_handle_events: Break #6 cons=0 csrread=1 > mskc0: msk_handle_events: Break #5 cons=1 csrread=2 > mskc0: msk_handle_events: Break #6 cons=2 csrread=3 > mskc0: msk_handle_events: Break #5 cons=3 csrread=5 > mskc0: msk_handle_events: Break #6 cons=4 csrread=6 > mskc0: msk_handle_events: Break #6 cons=5 csrread=6 > mskc0: msk_handle_events: Break #6 cons=6 csrread=7 > mskc0: msk_handle_events: Break #5 cons=7 csrread=8 > mskc0: msk_handle_events: Break #5 cons=8 csrread=10 > mskc0: msk_handle_events: Break #6 cons=9 csrread=10 > ... > mskc0: msk_handle_events: Break #5 cons=510 csrread=511 > mskc0: msk_handle_events: Break #6 cons=511 csrread=512 > mskc0: msk_handle_events: Break #5 cons=512 csrread=513 > mskc0: msk_handle_events: Break #5 cons=513 csrread=514 > mskc0: msk_handle_events: Break #6 cons=514 csrread=515 > mskc0: msk_handle_events: Break #5 cons=515 csrread=516 > ...etc. > > ------------ Start of MSK_STAT_ALIGN=4096 output ----------------------------- > > mskc0: mem 0xfa000000-0xfa003fff irq 19 at device 0.0 on pci6 > mskc0: Successful creation of DMA tag > mskc0: sc->msk_stat_count=2048 > mskc0: stat_sz=16384 > mskc0: sc->msk_stat_tag=0xfffff800050b99a0 > mskc0: Successful allocation of DMA'able memory for status ring > mskc0: sc->msk_stat_map=0xfffff800050b99a8 > msk_dmamap_cb (stat): nseg=1 > msk_dmamap_cb (stat): error=0 > msk_dmamap_cb (stat): segs[0].ds_addr=96710656=0x5c3b000 > msk_dmamap_cb (stat): segs[0].ds_len=16384=0x4000 > mskc0: Successful load of DMA'able memory for status ring > mskc0: sc->msk_stat_ring_paddr=96710656=0x5c3b000 > msk0: on mskc0 > msk0: Ethernet address: 00:13:77:e9:df:eb > miibus0: on msk0 > e1000phy0: PHY 0 on miibus0 > e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow > ... > mskc0: msk_handle_events: Break #5 cons=0 csrread=2 > mskc0: msk_handle_events: Break #5 cons=1 csrread=2 > mskc0: msk_handle_events: Break #5 cons=2 csrread=3 > mskc0: msk_handle_events: Break #5 cons=3 csrread=4 > mskc0: msk_handle_events: Break #5 cons=4 csrread=5 > mskc0: msk_handle_events: Break #5 cons=5 csrread=7 > mskc0: msk_handle_events: Break #5 cons=6 csrread=7 > mskc0: msk_handle_events: Break #5 cons=7 csrread=9 > mskc0: msk_handle_events: Break #5 cons=8 csrread=9 > mskc0: msk_handle_events: Break #5 cons=9 csrread=10 > mskc0: msk_handle_events: Break #5 cons=10 csrread=11 > ... > mskc0: msk_handle_events: Break #6 cons=194 csrread=197 > mskc0: msk_handle_events: Break #5 cons=195 csrread=197 > mskc0: msk_handle_events: Break #1 cons=196 csrread=197 > mskc0: msk_handle_events: sd=0xfffffe011e23b620 sd->msk_control=1610612806 control=1610612806 > mskc0: msk_handle_events: Break #5 cons=196 csrread=197 > mskc0: msk_handle_events: Break #5 cons=197 csrread=198 > ... > mskc0: msk_handle_events: Break #5 cons=510 csrread=511 > mskc0: msk_handle_events: Break #5 cons=511 csrread=512 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=513 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > ... > mskc0: msk_handle_events: Break #1 cons=512 csrread=519 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > mskc0: msk_handle_events: Break #1 cons=512 csrread=519 > mskc0: msk_handle_events: sd=0xfffffe011e23c000 sd->msk_control=0 control=0 > ...etc > > > ________________________________________ > From: owner-freebsd-stable@freebsd.org [owner-freebsd-stable@freebsd.org] on behalf of Yonghyeon PYUN [pyunyh@gmail.com] > Sent: 13 April 2015 09:13 > To: Gareth Wyn Roberts > Cc: freebsd-stable@freebsd.org > Subject: Re: msk msk0 watchdog timeout freeze hang lock stop problem > > On Sun, Apr 12, 2015 at 05:57:34PM +0000, Gareth Wyn Roberts wrote: >> I've run in to problems using the msk device where initially it works well enough to set DHCP etc. but stops/freezes as soon as any appreciable network traffic occurs . There are several threads describing similar symptoms over the past two years or more. I've been following several false leads but have finally found a solution (at least it solves my problem). >> >> I'm running a standard FreeBSD 10.1-RELEASE and the NIC is detected as: >> >> mskc0: mem 0xfa000000-0xfa003fff irq 19 at device 0.0 on pci6 >> msk0: on mskc0 >> msk0: Ethernet address: 00:13:77:e9:df:eb >> miibus0: on msk0 >> e1000phy0: PHY 0 on miibus0 >> e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-ma >> ster, auto, auto-flow >> >> The network worked when using the i386 release, but failed for the amd64 release (as reported previously) which prompted me to disable 64-bit DMA (the patch for this is attached below). This worked for the first kernel built but mysteriously failed when another unrelated part of the kernel was changed (a usb driver) and the kernel recompiled. So identical msk driver code worked in one kernel but not the second! This suggested that alignment differences between the two kernels were causing the msk driver to fail. Others have reported varying behaviour depending on different circumstances. >> >> It transpires that changing just one value in the if_mskreg.h file solved all my problems. Subsequently I have not been able to make it fail under heavy network traffic in either 32-bit or 64-bit mode. >> I'm working on 10.1-RELEASE source, i.e. if_msk.c revision 262524 and if_mskreg.h revision 264442. > Thanks for letting me know your findings. I really appreciate > that. > I recall that the alignment requirement of status LEs(List Elements > in Marvell terms) is 2048 and the maximum size of the status LEs is > 4096 bytes(Actual alignment seems to be much lower value like 32 or > 64 bytes, but alignment 2048 is chosen to avoid silicon bugs). > Later experiments showed some variants of Yukon II require 4096 > bytes alignment and I changed the alignment to 4096 in the past. > It seems your finding indicates msk(4) needs 8192 alignment for > status LEs. > > However this does not explain how and why the same code in 8.x/9.x > works well. In addition, it's not common to require alignment size > greater than PAGE_SIZE on x86 given that the maximum size of DMA > buffer is 4096 bytes. I have to check whether there was a change > in bus_dma(9) between 8.x/9.x and 10.x but it needs more time due > to lack of spare time. Probably you can verify the DMA address of > status LEs meets the following requirements both on i386 and amd64. > - Alignment is 4096. > - Number of DMA segment is 1. > - DMA segment base address plus DMA segment size does not cross > a PAGE_SIZE boundary. > >> Here's the patch to if_mskreg.h >> --- if_mskreg.h-orig 2014-11-11 20:02:58.000000000 +0000 >> +++ if_mskreg.h 2015-04-12 18:47:20.000000000 +0100 >> @@ -2179,9 +2179,11 @@ >> * At first I guessed 8 bytes, the size of a single descriptor, would be >> * required alignment constraints. But, it seems that Yukon II have 4096 >> * bytes boundary alignment constraints. >> + * And it seems that the DMA status region for the Yukon Ultra 2 (88E8057) >> + * requires 8192 byte alignment to prevent locking. >> */ >> #define MSK_RING_ALIGN 4096 >> -#define MSK_STAT_ALIGN 4096 >> +#define MSK_STAT_ALIGN 8192 >> >> >> The patches to both files which also implement a MSK_64BIT_DMA_DISABLE flag are attached. Perhaps the developers would consider committing these as it may be useful for future debugging. >> > If you have more than 4GB memory installed and disables 64bit DMA > addressing, msk(4) shall use bounce buffers. Passing packets > through bounce buffers involves copy operation and it costs a lot. > You can check hw.busdma sysctl node to see whether there are > drivers that use bounce buffers. And if you want to disable 64bit > DMA on 64bit architectures, add '#undef MSK_64BIT_DMA' just below > BUS_SPACE_MAXADDR check in if_mskreg.h. > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" Just tried 10.2-RC1 amd64 GENERIC, and the problem seems to be gone. I was even able to scp a 500 MB file. Could it be related to this fix in BETA2, as mentioned in the announcement, "The watchdog(4) device has been fixed to print to the correct buffer."? pciconf -lv [..] mskc0@pci0:9:0:0: class=0x020000 card=0xc072144d chip=0x435411ab rev=0x00 hdr=0x00 vendor = 'Marvell Technology Group Ltd.' device = '88E8040 PCI-E Fast Ethernet Controller' class = network subclass = ethernet -Alnis From owner-freebsd-stable@freebsd.org Sat Jul 25 12:42:48 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6AC6F9AAE1B for ; Sat, 25 Jul 2015 12:42:48 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward20p.cmail.yandex.net (forward20p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1B73414BC for ; Sat, 25 Jul 2015 12:42:47 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web8g.yandex.ru (web8g.yandex.ru [IPv6:2a02:6b8:0:1402::18]) by forward20p.cmail.yandex.net (Yandex) with ESMTP id 833A421F61 for ; Sat, 25 Jul 2015 15:42:33 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web8g.yandex.ru (Yandex) with ESMTP id 1F10B5740F6E; Sat, 25 Jul 2015 15:42:33 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437828153; bh=W0QVeo8IFnXyNjxBUZj9EEf6BKX3hzXGL1Oud6dPmz0=; h=From:To:In-Reply-To:References:Subject:Date; b=TAX3CbHwYgjxeCMByhXMflyzRJGg3gZXoMyUiIM7yFNfizfoWKwwhXTRFwiVhdnKD 7dlqjolFfp2apRdc+UMkHgn5ahj6yy7Gm/9R0pJpm0oREzcCtAld+hzXVU7EuWK2Tg GXHXDqQGP9Mak+kJt2oe2LOlTij88ZZ3ev17BhGY= Received: by web8g.yandex.ru with HTTP; Sat, 25 Jul 2015 15:42:32 +0300 From: deco33000@yandex.com To: freebsd-stable In-Reply-To: <894501437816648@web13g.yandex.ru> References: <894501437816648@web13g.yandex.ru> Subject: Re: How is the time fed between hardclocks ? MIME-Version: 1.0 Message-Id: <1184321437828152@web8g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 25 Jul 2015 14:42:32 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 12:42:48 -0000 Is my question clear, or would you like me to give further info (and which) ? Thanks --š Jog From owner-freebsd-stable@freebsd.org Sat Jul 25 13:11:22 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D58739AA375 for ; Sat, 25 Jul 2015 13:11:22 +0000 (UTC) (envelope-from artemrts@ukr.net) Received: from frv189.fwdcdn.com (frv189.fwdcdn.com [212.42.77.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 954C7128D for ; Sat, 25 Jul 2015 13:11:22 +0000 (UTC) (envelope-from artemrts@ukr.net) Received: from [10.10.1.26] (helo=frv197.fwdcdn.com) by frv189.fwdcdn.com with esmtp ID 1ZIyx0-0006sk-Ku for freebsd-stable@freebsd.org; Sat, 25 Jul 2015 15:53:14 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ukr.net; s=ffe; h=Content-Transfer-Encoding:Content-Type:MIME-Version:References:In-Reply-To:Message-Id:Cc:To:Subject:From:Date; bh=NFmrrw1pkxt8VSiT+C6zTI8AA4CrcqvxtWkB6yysLZA=; b=q3GfknSVD1Shx0CoEKd9sqCLCGYzhpfhUQjX+pUqSy9u89F04+3Jj9IH48AGbeymqS2jpL5LnF0vZie4fMpNsy4dZar+VNsXKMiGuaU3D8N8UYo6dh+WXQWtTv0xLM8uzYqlwMjGa4ALvE16nJRhky/clAzR3vcwiJ6mHaMf72c=; Received: from [10.10.10.34] (helo=frv34.fwdcdn.com) by frv197.fwdcdn.com with smtp ID 1ZIywt-000HcB-4Q for freebsd-stable@freebsd.org; Sat, 25 Jul 2015 15:53:07 +0300 Date: Sat, 25 Jul 2015 15:53:06 +0300 From: wishmaster Subject: Re[2]: How is the time fed between hardclocks ? To: deco33000@yandex.com Cc: freebsd-stable X-Mailer: mail.ukr.net 5.0 Message-Id: <1437828639.577689319.3gdwqqbx@frv34.fwdcdn.com> In-Reply-To: <1184321437828152@web8g.yandex.ru> References: <894501437816648@web13g.yandex.ru> <894501437816648@web13g.yandex.ru> <1184321437828152@web8g.yandex.ru> X-Reply-Action: reply Received: from artemrts@ukr.net by frv34.fwdcdn.com; Sat, 25 Jul 2015 15:53:06 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: binary Content-Disposition: inline X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 13:11:22 -0000 Do you really think this is appropriate ML? I think you should send your question  to freebsd-hackers. Cheers, Vit  --- Original message --- From: deco33000@yandex.com Date: 25 July 2015, 15:43:04 > Is my question clear, or would you like me to give further info (and which) ? > > Thanks > --  > Jog > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" From owner-freebsd-stable@freebsd.org Sat Jul 25 13:16:39 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 887B29AA472 for ; Sat, 25 Jul 2015 13:16:39 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward20p.cmail.yandex.net (forward20p.cmail.yandex.net [IPv6:2a02:6b8:0:1465::a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4230E15E1 for ; Sat, 25 Jul 2015 13:16:39 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web8g.yandex.ru (web8g.yandex.ru [IPv6:2a02:6b8:0:1402::18]) by forward20p.cmail.yandex.net (Yandex) with ESMTP id D67FC21301 for ; Sat, 25 Jul 2015 16:16:35 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web8g.yandex.ru (Yandex) with ESMTP id 85FC357420BD; Sat, 25 Jul 2015 16:16:35 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1437830195; bh=AdbSODR9YTS4MA+CO991jbRk6WOLOF7pVYyu7u9l2hw=; h=From:Cc:In-Reply-To:References:Subject:Date; b=KsU6v1SuyOjjfzBytDj/nibTcl46O8sKZ7FR6vvpQbnrY4IsEnbSTRWHNjuCCrdgo 2OWeszMsmbgsoLSaVS2UuRRdMIk1HgTzsFEIlA9i/q8qdu5215pHE4HEP9FOV+VLOl iYDZpZQZJz6hAlufxD2qFA9dr2/TnmPFLdkhYvCg= Received: by web8g.yandex.ru with HTTP; Sat, 25 Jul 2015 16:16:34 +0300 From: deco33000@yandex.com Cc: freebsd-stable In-Reply-To: <1437828639.577689319.3gdwqqbx@frv34.fwdcdn.com> References: <894501437816648@web13g.yandex.ru> <894501437816648@web13g.yandex.ru> <1184321437828152@web8g.yandex.ru> <1437828639.577689319.3gdwqqbx@frv34.fwdcdn.com> Subject: Re: How is the time fed between hardclocks ? MIME-Version: 1.0 Message-Id: <1218491437830194@web8g.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sat, 25 Jul 2015 15:16:34 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 13:16:39 -0000 Ok and I am sorry btw ! --š Jog From owner-freebsd-stable@freebsd.org Sat Jul 25 22:54:41 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EFF99AA208 for ; Sat, 25 Jul 2015 22:54:41 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0A18CE16; Sat, 25 Jul 2015 22:54:41 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by oigd21 with SMTP id d21so35698124oig.1; Sat, 25 Jul 2015 15:54:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=scCHRaBu/C69H1QzD38gRf00TC+uEGlIrnhX7LQ4wHs=; b=mkziP6GXW8AdPgVWnjHPJCkMPN/OPNLbaSA/3us5FOyOdE4wRt+VhbOaeNrB1+tChY DOvkBF4w1kXbbyzwNfWzawCS2eLfFw8W+PZpvRWUyUMEOpqj8ledkztr3TrasBBzUdWS 7lT0SauVz8m7n+Z8gHhAzI/cr+fhhlYWVtOM9pHFQDvsbYvlDwOtjujeO9OW8fzw2b+t i+MEa2YxqtSBZfOMMyPtOLxcjJrhMu+kfSlUYBsbfmNzbCi4QJ02FfAbUPdw1gaSzWpg Cw20JA2gcPy1HWu+Qgu0XAykE2QffD23QS55lr4jxUFGA/ABxGUeq++6+uJLOOvSOPm1 20Xw== MIME-Version: 1.0 X-Received: by 10.202.169.212 with SMTP id s203mr7891812oie.71.1437864880272; Sat, 25 Jul 2015 15:54:40 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.202.221.69 with HTTP; Sat, 25 Jul 2015 15:54:40 -0700 (PDT) In-Reply-To: References: <86oak289hv.fsf@gly.ftfl.ca> <86oaj9dnbo.fsf@gly.ftfl.ca> <12509399.h3RdpFfE1l@ralph.baldwin.cx> Date: Sat, 25 Jul 2015 15:54:40 -0700 X-Google-Sender-Auth: rNtxnBJWFQkM1h-KxRVsENjkDaE Message-ID: Subject: Re: suspend/resume regression From: Kevin Oberman To: John Baldwin Cc: Joseph Mingrone , "Brandon J. Wandersee" , Adrian Chadd , FreeBSD-STABLE Mailing List Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 22:54:41 -0000 John, I'm concerned that two issues may be getting conflated. The issue I thought we were looking at was the failure of some systems (T520, X220, T430) to resume after a number of PCI enhancements were MFCed. This is completely unrelated to the USB issue I was experiencing when trying to test the problem on HEAD. The more I think about it, the more I think that the USB "issue" is just how things need to work. Specifically, if you are booting a full, multi-user system from a USB connected drive, suspending and resuming will leave the system in an untenable condition that will force a panic. At least I don't see how the OS can determine that the disk present on resume is unchanged from that present when the system was suspended. Modern disk IDs greatly improve the situation, but I am unaware of any way to be sure that a removable drive (such as a USB) has not been removed and plugged into some other system that might have written to it. My knowledge of such things is very dated, going back to my days doing kernel programming about 25-30 year ago on VMS, so someone may have resolved the issue, but I don't understand exactly how. I guess that the risk might be low enough to just go ahead and pray that nobody did something really, really stupid like unplugging the drive, plugging it in elsewhere, and writing to it. The real issue is just resuming the system after r281874 was MFCed as a part of 284034. No USB connected file systems are involved. I m happy to see that it has been reverted for 10.2, but clearly, these changes are needed down the line and I hope the issue can be resolved well before 11.0. (This assumes a 10.3 before 11.0 happens next year.) Thanks for the time you have spent on this and I'll be happy to help out with testing in the future. Things will be easier now that I have a disk with head on it. I wasted way too much time trying to get HEAD to work in a USB drive and with related issues. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Wed, Jul 22, 2015 at 10:46 PM, Kevin Oberman wrote: > On Tue, Jul 21, 2015 at 3:56 PM, John Baldwin wrote: > >> On Saturday, July 18, 2015 10:22:33 PM Kevin Oberman wrote: >> > I just confirmed that my system resumes on HEAD of July 16 but fails on >> > 10.2-BETA2. So the problem limited to 10. I'm guessing that some other >> > change made to pci that has not been MFCed is the cause, but it is only >> > causing a problem on some hardware. I have seen no reports about systems >> > other than Lenovo systems. >> >> So my x220 does fail with a USB disk on 10, but I also get a weird >> behavior >> where it seems to wake up (disk lights up) and then goes back to sleep and >> never resumes again. I'm not sure if this is due to using a USB disk or >> not. I get the same result when I disable power management during suspend >> which was reported to fix other laptops IIRC. >> >> Please try this: >> >> Index: sys/dev/acpica/acpi.c >> =================================================================== >> --- sys/dev/acpica/acpi.c (revision 285761) >> +++ sys/dev/acpica/acpi.c (working copy) >> @@ -691,7 +691,7 @@ >> static void >> acpi_set_power_children(device_t dev, int state) >> { >> - device_t child, parent; >> + device_t child; >> device_t *devlist; >> struct pci_devinfo *dinfo; >> int dstate, i, numdevs; >> @@ -703,13 +703,12 @@ >> * Retrieve and set D-state for the sleep state if _SxD is >> present. >> * Skip children who aren't attached since they are handled >> separately. >> */ >> - parent = device_get_parent(dev); >> for (i = 0; i < numdevs; i++) { >> child = devlist[i]; >> dinfo = device_get_ivars(child); >> dstate = state; >> if (device_is_attached(child) && >> - acpi_device_pwr_for_sleep(parent, dev, &dstate) == 0) >> + acpi_device_pwr_for_sleep(dev, child, &dstate) == 0) >> acpi_set_powerstate(child, dstate); >> } >> free(devlist, M_TEMP); >> Index: sys/dev/pci/pci.c >> =================================================================== >> --- sys/dev/pci/pci.c (revision 285761) >> +++ sys/dev/pci/pci.c (working copy) >> @@ -3671,7 +3671,7 @@ >> child = devlist[i]; >> dstate = state; >> if (device_is_attached(child) && >> - PCIB_POWER_FOR_SLEEP(pcib, dev, &dstate) == 0) >> + PCIB_POWER_FOR_SLEEP(pcib, child, &dstate) == 0) >> pci_set_powerstate(child, dstate); >> } >> } >> Index: . >> =================================================================== >> --- . (revision 285761) >> +++ . (working copy) >> >> Property changes on: . >> ___________________________________________________________________ >> Modified: svn:mergeinfo >> Merged /head:r274386,274397 >> >> >> -- >> John Baldwin >> > > Tried both sysctls and the patch. Nothing worked. Ticket updated with the > information. > -- > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > >