From owner-freebsd-hackers@freebsd.org Sun Sep 20 07:03:27 2015 Return-Path: Delivered-To: freebsd-hackers@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 8F84BA05E8C for ; Sun, 20 Sep 2015 07:03:27 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward2h.mail.yandex.net (forward2h.mail.yandex.net [IPv6:2a02:6b8:0:f05::2]) by mx1.freebsd.org (Postfix) with ESMTP id 423A61DC7 for ; Sun, 20 Sep 2015 07:03:26 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web10h.yandex.ru (web10h.yandex.ru [IPv6:2a02:6b8:0:f05::20]) by forward2h.mail.yandex.net (Yandex) with ESMTP id DBE75700809 for ; Sun, 20 Sep 2015 10:03:17 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web10h.yandex.ru (Yandex) with ESMTP id 6EC2C1000188; Sun, 20 Sep 2015 10:03:17 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1442732597; bh=ypfJV7CTNIqg6aGyoqaaEsf463ehLVpr6X722nB5aVw=; h=From:To:In-Reply-To:References:Subject:Date; b=hElA5IBmIfFUaRUChnrK9z8hHI28YMwiNiFO3sdRceoM79kniCEFo1DKuyUsjKTtH +rIZDbJvtsNnAG18z0ZK4+iFuOZH5MZSUmOQSRSAvuBUsiGVV0U+9b39GzKaBpKQP9 ttKk/2RIr6sEbvwCLgdHALVecDKZHW5Z+w5fsFTQ= Received: by web10h.yandex.ru with HTTP; Sun, 20 Sep 2015 10:03:16 +0300 From: deco33000 Jog To: freebsd-hackers@freebsd.org In-Reply-To: References: <1490691442694243@web19g.yandex.ru> <7A263699-EB13-4371-AE93-17E305CD915D@longcount.org> Subject: Re: Avrdude & arduino Message-Id: <403021442732596@web10h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 20 Sep 2015 09:03:16 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 07:03:27 -0000 From owner-freebsd-hackers@freebsd.org Sun Sep 20 14:42:57 2015 Return-Path: Delivered-To: freebsd-hackers@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 A6C73A05A04 for ; Sun, 20 Sep 2015 14:42:57 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 163E21A4B for ; Sun, 20 Sep 2015 14:42:56 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id t8KEcXk5061814 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 20 Sep 2015 16:38:34 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.15.2/8.15.2) with ESMTP id t8KEcUZh018040 for ; Sun, 20 Sep 2015 16:38:30 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.15.2/8.15.2/Submit) with ESMTP id t8KEcPtZ018037 for ; Sun, 20 Sep 2015 16:38:25 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Sun, 20 Sep 2015 16:38:25 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: freebsd-hackers@freebsd.org Subject: mess with i915drm after update to latest releng-10 Message-ID: User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Sun, 20 Sep 2015 16:38:34 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Sep 2015 14:42:57 -0000 While system is running stable i'm constantly getting kernel errors like below every minute or more often. error: [drm:pid632:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 14070000, was 14000000 error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid7:i915_gem_object_unbind] *ERROR* Attempting to unbind pinned buffer error: [drm:pid632:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 14070000, was 14000000 error: [drm:pid632:gen6_sanitize_pm] *ERROR* Power management discrepancy: GEN6_RP_INTERRUPT_LIMITS expected 14070000, was 14000000 any ideas how to fix it? # kldstat Id Refs Address Size Name 1 23 0xffffffff80200000 bef5f0 kernel 2 1 0xffffffff80df0000 6cf30 vboxdrv.ko 3 2 0xffffffff80e5d000 7b460 drm2.ko 4 1 0xffffffff80ed9000 c5178 i915kms.ko 5 1 0xffffffff81011000 42d2 geom_label.ko From owner-freebsd-hackers@freebsd.org Mon Sep 21 03:41:15 2015 Return-Path: Delivered-To: freebsd-hackers@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 C0264A059B7 for ; Mon, 21 Sep 2015 03:41:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6824E1DB5 for ; Mon, 21 Sep 2015 03:41:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.15.2/8.15.2) with ESMTPS id t8L3fDTt006741 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 20 Sep 2015 21:41:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.15.2/8.15.2/Submit) with ESMTP id t8L3fDNJ006738; Sun, 20 Sep 2015 21:41:13 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 20 Sep 2015 21:41:13 -0600 (MDT) From: Warren Block To: deco33000 Jog cc: freebsd-hackers@freebsd.org Subject: Re: Avrdude & arduino In-Reply-To: <1490691442694243@web19g.yandex.ru> Message-ID: References: <1490691442694243@web19g.yandex.ru> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 20 Sep 2015 21:41:13 -0600 (MDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 03:41:15 -0000 On Sat, 19 Sep 2015, deco33000 Jog wrote: > Hello, > > Did any of you had issues coding for arduino on freebsd 10.2? (avrdude, usb permissions..) See the pkg-message for the Arduino port or package: % pkg info -D arduino From owner-freebsd-hackers@freebsd.org Mon Sep 21 10:14:54 2015 Return-Path: Delivered-To: freebsd-hackers@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 6C7E0A06984 for ; Mon, 21 Sep 2015 10:14:54 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward17j.cmail.yandex.net (forward17j.cmail.yandex.net [IPv6:2a02:6b8:0:1630::f4]) (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 24A6E1C0F for ; Mon, 21 Sep 2015 10:14:53 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web15j.yandex.ru (web15j.yandex.ru [IPv6:2a02:6b8:0:1619::315]) by forward17j.cmail.yandex.net (Yandex) with ESMTP id EFD9021105; Mon, 21 Sep 2015 13:14:49 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web15j.yandex.ru (Yandex) with ESMTP id 325A21C41756; Mon, 21 Sep 2015 13:14:49 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1442830489; bh=5gE7RL5HTZoJ0ucXMAwhazSFlzMLcbTVkcWH0FHgiz0=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=B7fCPl1CymYSkoq/3RaAD9hhwbbTABF8WqTW2H3ub54wRNvefJmWiLigw5t4bYJSO dRyZIe7DQyEFSDrY0M1O98m1UwGKtvXjop/HHIV8BHWqIevi8paoTGEvTt4/+51rHS cviqhXtR7Tjtou137uJFflQbXIyJoGJgky9eElQc= Received: by web15j.yandex.ru with HTTP; Mon, 21 Sep 2015 13:14:47 +0300 From: deco33000 Jog To: Warren Block Cc: "freebsd-hackers@freebsd.org" In-Reply-To: References: <1490691442694243@web19g.yandex.ru> Subject: Re: Avrdude & arduino MIME-Version: 1.0 Message-Id: <1694721442830487@web15j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 21 Sep 2015 12:14:47 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 10:14:54 -0000 Will do that, thanks Warren. --š Jog From owner-freebsd-hackers@freebsd.org Mon Sep 21 20:49:58 2015 Return-Path: Delivered-To: freebsd-hackers@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 10A35A06392 for ; Mon, 21 Sep 2015 20:49:58 +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 C1C901BD6 for ; Mon, 21 Sep 2015 20:49:57 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web10h.yandex.ru (web10h.yandex.ru [IPv6:2a02:6b8:0:f05::20]) by forward13h.cmail.yandex.net (Yandex) with ESMTP id 580242131C for ; Mon, 21 Sep 2015 23:49:46 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web10h.yandex.ru (Yandex) with ESMTP id 06E6510001C8; Mon, 21 Sep 2015 23:49:45 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1442868586; bh=d/h32GzcVSA6hyGIcST2TslV+hGKIplMkJ/oARNlgBY=; h=From:To:Subject:Date; b=xHDgVxLlb6qIzPFXeQFnIp+fTgqY+w5k5GDVR42DTZYbW/wrbuHqMr0tse+P2Mzy6 XtzZayAotPNLC+1Bjbfvf66/T6ZFKYdyeLO+ujByYY6TXo1p4w03dozKck24BQ4Lzl KhKFZiDQrmb/IiTp4TuqUMjwQj/t4ladoxfPfQkI= Received: by web10h.yandex.ru with HTTP; Mon, 21 Sep 2015 23:49:45 +0300 From: deco33000 Jog To: freebsd-hackers@freebsd.org Subject: Virtual images and qemu MIME-Version: 1.0 Message-Id: <730481442868585@web10h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Mon, 21 Sep 2015 22:49:45 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 20:49:58 -0000 Hi, I just downloaded the freebsd 10.2 virtual image for amd64. It runs on Linux mint. I use qemu v.1.7.0 (because of linux mint, but plan to manually install the 2.4.0 version, and ditch Mint altogether). I use the following command: qemu-system-x86_64 myfreebsdimage.qcow2 When doing the pkg command, at some point it says it cannot fetch because of read only file system. Ok, but how did you fix this? (I am not very used to virtualization). The plan is to compile a custom freebsd system (faster memory management, and tcp stack) inside qemu because at the moment, I have no other choice :( Thanks and sorry for asking such a question. --š Jog From owner-freebsd-hackers@freebsd.org Mon Sep 21 22:53:28 2015 Return-Path: Delivered-To: freebsd-hackers@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 841879D031A for ; Mon, 21 Sep 2015 22:53:28 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) (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 489BA10E5 for ; Mon, 21 Sep 2015 22:53:27 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: by qgt47 with SMTP id 47so103018626qgt.2 for ; Mon, 21 Sep 2015 15:53:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=4vIP2xg5rjN6KLITAdI8emE+gDOelExEkrsf+3KrcEI=; b=b8c3DSrdo2UX+nJvPXU2GtN/ftrr3KrAX9gxdVNDOOKSRlPqrmQT9glfOftSzcqiD2 gDWv9VVY+j9kHWRH39F1BMIdtb3X/ZZy3katsoBdMNAzzF6mmm1Xv7PGSLM2T7xxwmWZ ujFNokBZP776l8UWyeBDcv5iuG2wk623e/CxbvYtOSkbWp+APYT2hnAjk5wdb7YNrUSp +/koUR9bli1xIhil4FtDEx7E0TwhEUNfyfSZJT+keZUzaIHJrr7VXn4lmtSE9QUq4rhq ZB86TyjKAQgnWGOPHGVw0HYwc6q3qtlj4JCUMtIPGftlXpcFimD1lB+TRq1z4TZ9+X3g jn5Q== X-Gm-Message-State: ALoCoQkDNk319DXfdo4ZbDy5SkjMHwPsj0NFMoOIZ4ndM0R37R7KbQYd2I0SpB1KgJrpYca3Cx4t X-Received: by 10.140.93.53 with SMTP id c50mr25461128qge.59.1442876000832; Mon, 21 Sep 2015 15:53:20 -0700 (PDT) Received: from ?IPv6:2600:1017:b41e:6bd3:74cc:cdea:26ef:d1fa? ([2600:1017:b41e:6bd3:74cc:cdea:26ef:d1fa]) by smtp.gmail.com with ESMTPSA id n23sm10854551qkl.17.2015.09.21.15.53.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Sep 2015 15:53:20 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Virtual images and qemu From: Mark Saad X-Mailer: iPhone Mail (13A344) In-Reply-To: <730481442868585@web10h.yandex.ru> Date: Mon, 21 Sep 2015 18:53:18 -0400 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <04F9A7F5-9E39-4ADC-9BC8-7B2B33089D7F@longcount.org> References: <730481442868585@web10h.yandex.ru> To: deco33000 Jog X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Sep 2015 22:53:28 -0000 Jog Maybe you can begin to describe how you installed FreeBSD , so we may bett= er understand what and where the issue is .=20 So after you boot up the image up did you make any changes ? Also could you p= ost the dmesg to dmesg dmesgd.nycbug.org.=20 --- Mark Saad | nonesuch@longcount.org > On Sep 21, 2015, at 4:49 PM, deco33000 Jog wrote: >=20 > Hi, >=20 > I just downloaded the freebsd 10.2 virtual image for amd64. It runs on Lin= ux mint. > I use qemu v.1.7.0 (because of linux mint, but plan to manually install th= e 2.4.0 version, and ditch Mint altogether). >=20 > I use the following command: > qemu-system-x86_64 myfreebsdimage.qcow2 >=20 > When doing the pkg command, at some point it says it cannot fetch because o= f read only file system. >=20 > Ok, but how did you fix this? (I am not very used to virtualization). >=20 > The plan is to compile a custom freebsd system (faster memory management, a= nd tcp stack) inside qemu because at the moment, I have no other choice :( >=20 > Thanks and sorry for asking such a question. >=20 >=20 > --=20 > Jog > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"= From owner-freebsd-hackers@freebsd.org Tue Sep 22 06:36:15 2015 Return-Path: Delivered-To: freebsd-hackers@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 C0F8DA0336E for ; Tue, 22 Sep 2015 06:36:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (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 9BDD018EA for ; Tue, 22 Sep 2015 06:36:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-224-161.lns20.per1.internode.on.net [121.45.224.161]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id t8M6aABo005322 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 21 Sep 2015 23:36:13 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: Virtual images and qemu To: deco33000 Jog , freebsd-hackers@freebsd.org References: <730481442868585@web10h.yandex.ru> From: Julian Elischer Message-ID: <5600F6D4.5040007@freebsd.org> Date: Tue, 22 Sep 2015 14:36:04 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <730481442868585@web10h.yandex.ru> Content-Type: text/plain; charset=koi8-r; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 06:36:15 -0000 On 9/22/15 4:49 AM, deco33000 Jog wrote: > Hi, > > I just downloaded the freebsd 10.2 virtual image for amd64. It runs on Linux mint. > I use qemu v.1.7.0 (because of linux mint, but plan to manually install the 2.4.0 version, and ditch Mint altogether). > > I use the following command: > qemu-system-x86_64 myfreebsdimage.qcow2 > > When doing the pkg command, at some point it says it cannot fetch because of read only file system. > > Ok, but how did you fix this? (I am not very used to virtualization). > virtualization should not give you a read-only filesystem. there are a few possibilities.. off the top of my head... 1/ you are in single user mode, in which case you need to let it finish booting. or you can do 'mount -u /' to make it read-write 2/ something failed in mounting /tmp and it's read-only? you need to tell us more about what has happened up to this point. From owner-freebsd-hackers@freebsd.org Tue Sep 22 10:09:50 2015 Return-Path: Delivered-To: freebsd-hackers@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 2379EA05638 for ; Tue, 22 Sep 2015 10:09:50 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward15h.cmail.yandex.net (forward15h.cmail.yandex.net [87.250.230.157]) (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 CC10419C4; Tue, 22 Sep 2015 10:09:49 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web12h.yandex.ru (web12h.yandex.ru [IPv6:2a02:6b8:0:f05::22]) by forward15h.cmail.yandex.net (Yandex) with ESMTP id E63F821493; Tue, 22 Sep 2015 13:09:34 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web12h.yandex.ru (Yandex) with ESMTP id 58AA9C22754; Tue, 22 Sep 2015 13:09:34 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1442916574; bh=cUmxDe5ASVht1opEZe8+XUG5GYm9UFbRpBUUNCRjDdo=; h=From:To:In-Reply-To:References:Subject:Date; b=A8eWezboQF79QOjoJmYRvqrhW0l4hV1hpTmkoEvI73CDGeJzyE5MF76SkETNm8jq/ zrwoVOlWkYzq0fMQTvSlppynQ4b90McoR6BmqlarFBWXVhRn24j2gNQpJaASz8mt6d M26CMxwbqlXh17jFGeo5mDlhz+jBR+e6J4t2pBbI= Received: by web12h.yandex.ru with HTTP; Tue, 22 Sep 2015 13:09:33 +0300 From: deco33000 Jog To: Julian Elischer , "freebsd-hackers@freebsd.org" In-Reply-To: <5600F6D4.5040007@freebsd.org> References: <730481442868585@web10h.yandex.ru> <5600F6D4.5040007@freebsd.org> Subject: Re: Virtual images and qemu MIME-Version: 1.0 Message-Id: <184701442916573@web12h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 22 Sep 2015 12:09:33 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 10:09:50 -0000 OK, Now it is fully working. I switched to virtualbox and chose a nat paravirt network. I really hate virtualization but will bear with it anyway. Thanks for you help, Bye 22.09.2015, 08:36, "Julian Elischer" : > On 9/22/15 4:49 AM, deco33000 Jog wrote: >> šHi, >> >> šI just downloaded the freebsd 10.2 virtual image for amd64. It runs on Linux mint. >> šI use qemu v.1.7.0 (because of linux mint, but plan to manually install the 2.4.0 version, and ditch Mint altogether). >> >> šI use the following command: >> šqemu-system-x86_64 myfreebsdimage.qcow2 >> >> šWhen doing the pkg command, at some point it says it cannot fetch because of read only file system. >> >> šOk, but how did you fix this? (I am not very used to virtualization). > > virtualization should not give you a read-only filesystem. > there are a few possibilities.. > off the top of my head... > 1/ you are in single user mode, in which case you need to let it > finish booting. or you can do 'mount -u /' > to make it read-write > 2/ something failed in mounting /tmp and it's read-only? > > you need to tell us more about what has happened up to this point. From owner-freebsd-hackers@freebsd.org Tue Sep 22 19:14:46 2015 Return-Path: Delivered-To: freebsd-hackers@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 57A44A0773C for ; Tue, 22 Sep 2015 19:14:46 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D863715B2 for ; Tue, 22 Sep 2015 19:14:45 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id t8MJEY6g004535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Sep 2015 21:14:35 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.15.2/8.15.2) with ESMTP id t8MJEVhv004273; Tue, 22 Sep 2015 21:14:31 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.15.2/8.15.2/Submit) with ESMTP id t8MJEPML004270; Tue, 22 Sep 2015 21:14:25 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Tue, 22 Sep 2015 21:14:25 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: deco33000 Jog cc: freebsd-hackers@freebsd.org Subject: Re: Virtual images and qemu In-Reply-To: <730481442868585@web10h.yandex.ru> Message-ID: References: <730481442868585@web10h.yandex.ru> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Tue, 22 Sep 2015 21:14:35 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 19:14:46 -0000 > qemu-system-x86_64 myfreebsdimage.qcow2 > qemu-system-x86_64 -m -hda myfreebsdimage.qcow2 even better: man qemu > When doing the pkg command, at some point it says it cannot fetch because of read only file system. > > Ok, but how did you fix this? (I am not very used to virtualization). > > The plan is to compile a custom freebsd system (faster memory management, and tcp stack) inside qemu because at the moment, I have no other choice :( > > Thanks and sorry for asking such a question. > > > -- ?? Jog > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@freebsd.org Tue Sep 22 19:28:58 2015 Return-Path: Delivered-To: freebsd-hackers@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 272A3A07F26 for ; Tue, 22 Sep 2015 19:28:58 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [188.252.31.250]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AD1A1E2F; Tue, 22 Sep 2015 19:28:57 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.14.9/8.14.9) with ESMTP id t8MJSs4u005013 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 22 Sep 2015 21:28:54 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from laptop.wojtek.intra (localhost [127.0.0.1]) by laptop.wojtek.intra (8.15.2/8.15.2) with ESMTP id t8MJSpoH004308; Tue, 22 Sep 2015 21:28:51 +0200 (CEST) (envelope-from wojtek@puchar.net) Received: from localhost (wojtek@localhost) by laptop.wojtek.intra (8.15.2/8.15.2/Submit) with ESMTP id t8MJSj1a004305; Tue, 22 Sep 2015 21:28:45 +0200 (CEST) (envelope-from wojtek@puchar.net) X-Authentication-Warning: laptop.wojtek.intra: wojtek owned process doing -bs Date: Tue, 22 Sep 2015 21:28:45 +0200 (CEST) From: Wojciech Puchar X-X-Sender: wojtek@laptop.wojtek.intra To: deco33000 Jog cc: Julian Elischer , "freebsd-hackers@freebsd.org" Subject: Re: Virtual images and qemu In-Reply-To: <184701442916573@web12h.yandex.ru> Message-ID: References: <730481442868585@web10h.yandex.ru> <5600F6D4.5040007@freebsd.org> <184701442916573@web12h.yandex.ru> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (puchar.net [10.0.1.1]); Tue, 22 Sep 2015 21:28:55 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 19:28:58 -0000 > Now it is fully working. I switched to virtualbox and chose a nat paravirt network. anyway FreeBSD 10.2 works fine under qemu - both amd64 and i386. tested. Anyway i never used qcow2 images, always raw. > I really hate virtualization but will bear with it anyway. instead of hate it's better to understand. Cases where virtualization is useful: - quick test of operating system (probably your case) - OS/kernel development - avoids reboot as well as provide freeze and memory dump. - when you have to run more than 1 different OS on one machine. For example: FreeBSD server but needs to run some server software under windows. Run windows virtual machine on this server with this software in it. - preparing software disk image for different architecture (often used be me for FreeBSD/mips, qemu on fast PC runs faster than actual machine and it's easier). - recovery of data from disks or disk images - may be few more. Cases where it is not useful, or suboptimal: - running multiple images of same unix system (eg. FreeBSD, linux) on one computer. Use jails or similar mechanism under other unix-alike. - magic way to enhance security. No it isn't. - running windows desktops for terminal systems, one virtual machine per user. Suboptimal and costly, run multiple users on single windows computer. - REALLY lots of other uses just because virtualization is popular. Virtualbox is MUCH faster, qemu is much more universal. Virtualization always make performance overhead, and always bigger than authors claim. Still - it is much better running some software set even with 50% overhead, than buying separate machine that would be 1% utilized. From owner-freebsd-hackers@freebsd.org Tue Sep 22 19:34:08 2015 Return-Path: Delivered-To: freebsd-hackers@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 663CAA062EA for ; Tue, 22 Sep 2015 19:34:08 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from forward20h.cmail.yandex.net (forward20h.cmail.yandex.net [IPv6:2a02:6b8:0:f35::a5]) (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 1D69B128A; Tue, 22 Sep 2015 19:34:07 +0000 (UTC) (envelope-from deco33000@yandex.com) Received: from web20h.yandex.ru (web20h.yandex.ru [84.201.186.49]) by forward20h.cmail.yandex.net (Yandex) with ESMTP id 3FFB421263; Tue, 22 Sep 2015 22:33:55 +0300 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web20h.yandex.ru (Yandex) with ESMTP id 9238D13204F3; Tue, 22 Sep 2015 22:33:54 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1442950434; bh=kYNVIbI0iCD9sUOsVhfsr1vDitJUj66cGeHSbkXmY9g=; h=From:To:Cc:In-Reply-To:References:Subject:Date; b=g3GwTW+Xtfyg5XYEEkjXLa3E3wyDrsnBFLbz3oksmZen9B34kxnbHFzgDSmNYTrRd +hd3SK+9cNbtv3OvYUdXL6QzaSq2inqMAnM24pjBUC7pJOCbFwdlbKfS/ys7i9znph z/BGAj+Fr6HZ5jWdLcsHWGiV1h1MXfuhBj4PR8uc= Received: by web20h.yandex.ru with HTTP; Tue, 22 Sep 2015 22:33:53 +0300 From: deco33000 Jog To: Wojciech Puchar Cc: Julian Elischer , "freebsd-hackers@freebsd.org" In-Reply-To: References: <730481442868585@web10h.yandex.ru> <5600F6D4.5040007@freebsd.org> <184701442916573@web12h.yandex.ru> Subject: Re: Virtual images and qemu MIME-Version: 1.0 Message-Id: <903401442950433@web20h.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Tue, 22 Sep 2015 21:33:53 +0200 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2015 19:34:08 -0000 You are right, and I understand the paramount of virtualization. Hence my use of it now. But it doesn't change a hair of my position: I hate it but still use it. --š Jog 22.09.2015, 21:29, "Wojciech Puchar" : >> šNow it is fully working. I switched to virtualbox and chose a nat paravirt network. > > anyway FreeBSD 10.2 works fine under qemu - both amd64 and i386. tested. > Anyway i never used qcow2 images, always raw. > >> šI really hate virtualization but will bear with it anyway. > > instead of hate it's better to understand. > > Cases where virtualization is useful: > > - quick test of operating system (probably your case) > - OS/kernel development - avoids reboot as well as provide freeze and > memory dump. > - when you have to run more than 1 different OS on one machine. For > example: FreeBSD server but needs to run some server software under windows. Run > windows virtual machine on this server with this software in it. > - preparing software disk image for different architecture (often used > be me for FreeBSD/mips, qemu on fast PC runs faster than actual machine > and it's easier). > - recovery of data from disks or disk images > - may be few more. > > Cases where it is not useful, or suboptimal: > > - running multiple images of same unix system (eg. FreeBSD, linux) on one > computer. Use jails or similar mechanism under other unix-alike. > - magic way to enhance security. No it isn't. > - running windows desktops for terminal systems, one virtual machine per > user. Suboptimal and costly, run multiple users on single windows > computer. > - REALLY lots of other uses just because virtualization is popular. > > Virtualbox is MUCH faster, qemu is much more universal. Virtualization > always make performance overhead, and always bigger than authors claim. > Still - it is much better running some software set even with 50% overhead, than buying > separate machine that would be 1% utilized. From owner-freebsd-hackers@freebsd.org Wed Sep 23 09:05:36 2015 Return-Path: Delivered-To: freebsd-hackers@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 CF9DDA05ACC for ; Wed, 23 Sep 2015 09:05:36 +0000 (UTC) (envelope-from phk@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 BC66F1A98 for ; Wed, 23 Sep 2015 09:05:36 +0000 (UTC) (envelope-from phk@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B934EA05ACB; Wed, 23 Sep 2015 09:05:36 +0000 (UTC) Delivered-To: hackers@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 B8C97A05AC9 for ; Wed, 23 Sep 2015 09:05:36 +0000 (UTC) (envelope-from phk@freebsd.org) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 855E01A97 for ; Wed, 23 Sep 2015 09:05:36 +0000 (UTC) (envelope-from phk@freebsd.org) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id E4E774F86D for ; Wed, 23 Sep 2015 09:05:28 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id t8N95RHq039338 for ; Wed, 23 Sep 2015 09:05:28 GMT (envelope-from phk@freebsd.org) To: hackers@freebsd.org Subject: What IS the right NTP behaviour ? From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <39336.1442999127.1@critter.freebsd.dk> Date: Wed, 23 Sep 2015 09:05:27 +0000 Message-ID: <39337.1442999127@critter.freebsd.dk> X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 09:05:36 -0000 As you probably know I'm working on a new NTP client called Ntimed. It is no surprise that people have different expectations of how timekeeping should behave, and I'm trying to figure out what Do What I Want is. I think I have identified three variations of "DWIW", which I have named "eCommerce", "SCADA" and "Workstation" Please let me know (private email to keep list noise down) if your needs would not be served by any of these three variations or for that matter any other comment or input on this topic. Thanks Poul-Henning eCommerce --------- Correct system time is mandatory. Bootup fails if correct time cannot established. What do we mean by "fails" ? Does it hang until success ? Does it fail into single-user ? Does it raise a big red flag ? Stepping time after bootup is *never* allowed. If time drifts out of tolerance: Raise Alarm How ? Signal init(8) into single-user mode ? Slew clock, no matter how far. Syslog periodically how wrong system time is SCADA ----- We don't need the system clock to be on time, as long as we know exactly how wrong it is. Startup should be as quick and reliable as possible. Configurable timer for how long we hold up startup. Startup step only allowed during this time interval. Stepping time after bootup is never allowed. If time drifts out of tolerance: Slew clock, no matter how far. Syslog periodically how wrong system time is Raise Alarm (optional) How ? Workstation ----------- Startup should be fast-ish Steps are allowed any time necessary suspend/resume change in network topology clock drift -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@freebsd.org Wed Sep 23 15:09:20 2015 Return-Path: Delivered-To: freebsd-hackers@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 372A5A0771E for ; Wed, 23 Sep 2015 15:09:20 +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 13F731356 for ; Wed, 23 Sep 2015 15:09:20 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A0873B913; Wed, 23 Sep 2015 11:09:18 -0400 (EDT) From: John Baldwin To: "Pokala, Ravi" Cc: "freebsd-hackers@freebsd.org" Subject: Re: bus_.*_resource() and rid Date: Wed, 23 Sep 2015 08:07:55 -0700 Message-ID: <1637146.Rv3dkk0gMi@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-PRERELEASE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <1685918.WyYIclYTSg@ralph.baldwin.cx> 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, 23 Sep 2015 11:09:18 -0400 (EDT) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 15:09:20 -0000 On Friday, September 11, 2015 02:37:58 AM Pokala, Ravi wrote: > -----Original Message----- > From: John Baldwin > Date: 2015-09-10, Thursday at 17:24 > To: "freebsd-hackers@freebsd.org" > Cc: Ravi Pokala > Subject: Re: bus_.*_resource() and rid > > >Each bus decides how to manage RIDs. For PCI devices, RIDs are the > >address of the corresponding BAR for memory and I/O port resources and > >follow a different convention for interrupts (0 == INTx, 1...N == > >MSI/MSI-X). For ISA devices (and ACPI) RIDs are 0...N. If a device is > >enumerated via the firmware (e.g. ACPI DSDT entry with _CRS or PNPBIOS > >data for non-ACPI) then the firmware assigned resources are set for you > >by the parent bus and start at 0 (if you have two I/O port resources > >you'd have the second one at rid 1). > > I see the address ranges w/ `devinfo -r', but they don't list RIDs. Yes, you'd have to grumble around with kgdb to see rids. We might store rids in 'struct resouce *' now so we could possibly expose those to devinfo. > >If you are doing this on the LPC, then that it is actually a PCI device, > >and I don't know if the PCI bus is really going to let you create a rid > >at 0 via bus_set_resource(). Hmm, it should, but it's kind of a bit > >hacky. It might be somewhat cleaner if instead you treat this as an ISA > >device that is a child of isa0 below the LPC device. You can use an > >identify routine that looks at the grandparent isab0 device and then > >allocates this. > > My understanding was that the *only* way to treat devices hanging off the > LPC was as an ISA device, so that's what I've been doing. That is, the LPC > controller is a transparent bridge to allow ISA devices to connect to > modern systems. (In several cases, the LPC controller also has some BARs > which point at integrated ISA devices, like GPIO controllers, but that's > beside the point.) Some drivers take over the LPC (e.g. I think some of the smb controllers do this) and provide functionality directly in the driver attached to the LPC rather than as a child. In general I think it is cleaner to provide these extended functionalities as pseudo-ISA devices that are children of the LPC instead. The relevant SMB drivers that do the other way: viapm/viapm.c:DRIVER_MODULE(isa, viapm, isa_driver, isa_devclass, 0, 0); viapm/viapm.c:DRIVER_MODULE(isa, viapropm, isa_driver, isa_devclass, 0, 0); > >However, a rid of 0 "should" work. You can check the resource list of > >the device in kgdb to see if there's a valid resource entry for rid 0. > >You could also try calling bus_get_resource() in your attach routine to > >see if the bus_set_resource() "worked". > > I'll look into bus_get_resource(). Oh, look - there's no manpage > (share/man/man9/bus_get_resource.9 does not exist, despite being a "see > also" entry in bus_set_resource.9). :-S Time for Someone(tm) to write one. :-/ -- John Baldwin From owner-freebsd-hackers@freebsd.org Wed Sep 23 17:39:30 2015 Return-Path: Delivered-To: freebsd-hackers@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 414ABA0678D for ; Wed, 23 Sep 2015 17:39:30 +0000 (UTC) (envelope-from tim@kientzle.com) 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 26391161A for ; Wed, 23 Sep 2015 17:39:30 +0000 (UTC) (envelope-from tim@kientzle.com) Received: by mailman.ysv.freebsd.org (Postfix) id 22F6EA0678C; Wed, 23 Sep 2015 17:39:30 +0000 (UTC) Delivered-To: hackers@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 2285FA06789 for ; Wed, 23 Sep 2015 17:39:30 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (kientzle.com [142.254.26.11]) (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 D84111619; Wed, 23 Sep 2015 17:39:29 +0000 (UTC) (envelope-from tim@kientzle.com) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t8NHaUO4000204; Wed, 23 Sep 2015 17:36:30 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.108] (192.168.1.101 [192.168.1.101]) by kientzle.com with SMTP id 6v62my2a2ak8r3bcgz3whqasws; Wed, 23 Sep 2015 17:36:29 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: What IS the right NTP behaviour ? From: Tim Kientzle In-Reply-To: <39337.1442999127@critter.freebsd.dk> Date: Wed, 23 Sep 2015 10:35:54 -0700 Cc: hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <39337.1442999127@critter.freebsd.dk> To: Poul-Henning Kamp X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 17:39:30 -0000 I like your outline here. One concern I keep running into: Using NTP in VMs that are frequently = suspended/resumed. Though I suppose this may be covered by your = 'workstation' scenario (just step it after VM resume when you see the = large skew). Tim > On Sep 23, 2015, at 2:05 AM, Poul-Henning Kamp = wrote: >=20 > As you probably know I'm working on a new NTP client called Ntimed. >=20 > It is no surprise that people have different expectations of how > timekeeping should behave, and I'm trying to figure out > what Do What I Want is. >=20 > I think I have identified three variations of "DWIW", which I have > named "eCommerce", "SCADA" and "Workstation" >=20 > Please let me know (private email to keep list noise down) if your > needs would not be served by any of these three variations or for > that matter any other comment or input on this topic. >=20 > Thanks >=20 > Poul-Henning >=20 >=20 > eCommerce > --------- >=20 > Correct system time is mandatory. >=20 > Bootup fails if correct time cannot established. > What do we mean by "fails" ? > Does it hang until success ? > Does it fail into single-user ? > Does it raise a big red flag ? >=20 > Stepping time after bootup is *never* allowed. > If time drifts out of tolerance: > Raise Alarm > How ? > Signal init(8) into single-user mode ? > Slew clock, no matter how far. > Syslog periodically how wrong system time is >=20 > SCADA > ----- >=20 > We don't need the system clock to be on time, as long as > we know exactly how wrong it is. >=20 > Startup should be as quick and reliable as possible. > Configurable timer for how long we hold up startup. >=20 > Startup step only allowed during this time interval. >=20 > Stepping time after bootup is never allowed. > If time drifts out of tolerance: > Slew clock, no matter how far. > Syslog periodically how wrong system time is > Raise Alarm (optional) > How ? >=20 > Workstation > ----------- >=20 > Startup should be fast-ish >=20 > Steps are allowed any time necessary > suspend/resume > change in network topology > clock drift >=20 > --=20 > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > phk@FreeBSD.ORG | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by = incompetence. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 From owner-freebsd-hackers@freebsd.org Wed Sep 23 18:35:32 2015 Return-Path: Delivered-To: freebsd-hackers@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 40DE3A0647B for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) 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 226AF1B3A for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: by mailman.ysv.freebsd.org (Postfix) id 1EE95A0647A; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) Delivered-To: hackers@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 1E7E5A06479 for ; Wed, 23 Sep 2015 18:35:32 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: from mail-io0-f182.google.com (mail-io0-f182.google.com [209.85.223.182]) (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 E8BAF1B39 for ; Wed, 23 Sep 2015 18:35:31 +0000 (UTC) (envelope-from bmvince1@asu.edu) Received: by ioiz6 with SMTP id z6so52156452ioi.2 for ; Wed, 23 Sep 2015 11:35:31 -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=pKCjXpBkcl3JBMe8b9xx2qnsdj/sYpCEWqJHyP24hfQ=; b=Gg4FkqbYem/vKNJ3KPbexNjxRNkourcBv6uPXadr2bnqoDa0vuPMQ62O/fGErfXlmb 2tGGjuXfkDCfx6LorFCLnhGnrlL0cMDUj8HGC3QH+H3hrx2PFtXiJC5/yVrc8KrbZhsH GOllfR/83/Nq5vb59GHGLQ1pXOFhlJ53iH4F31gd4hs0W1S/lNKYGnmGXxALM7K4OMC/ 7LK0SxP0CE4YyCNvabJwIBOr29x3XwBCkxCW1RlEK7ovX1/jq1ahxw930KRezHzzb0Zb BFUADP4HW5NSdKPl3XKL6U8/thLapsUa2UCZ2Sslg75IAIDTE3KScOVS1R09ryfsqm6l 2C5Q== X-Gm-Message-State: ALoCoQn0SX4Er9CeTtNK6tCfx586M1SUTnSkfUYzYEM2Y82LEZr7/uHwBLimvioTyvCP+bpggbFf MIME-Version: 1.0 X-Received: by 10.107.129.104 with SMTP id c101mr39147926iod.141.1443031483667; Wed, 23 Sep 2015 11:04:43 -0700 (PDT) Received: by 10.36.71.18 with HTTP; Wed, 23 Sep 2015 11:04:43 -0700 (PDT) In-Reply-To: References: <39337.1442999127@critter.freebsd.dk> Date: Wed, 23 Sep 2015 11:04:43 -0700 Message-ID: Subject: Re: What IS the right NTP behaviour ? From: Brandon Vincent To: Tim Kientzle Cc: Poul-Henning Kamp , hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 18:35:32 -0000 On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle wrote: > One concern I keep running into: Using NTP in VMs that are frequently suspended/resumed. Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew). I would assume your hypervisor would sync the clock upon VM events. Does it not? Brandon Vincent From owner-freebsd-hackers@freebsd.org Wed Sep 23 19:43:52 2015 Return-Path: Delivered-To: freebsd-hackers@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 0CD84A08639 for ; Wed, 23 Sep 2015 19:43:52 +0000 (UTC) (envelope-from dirkx@webweaving.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 E59DC17D6 for ; Wed, 23 Sep 2015 19:43:51 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id E4052A08638; Wed, 23 Sep 2015 19:43:51 +0000 (UTC) Delivered-To: hackers@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 E3A3CA08637 for ; Wed, 23 Sep 2015 19:43:51 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 72F8A17D3 for ; Wed, 23 Sep 2015 19:43:51 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from [192.168.1.21] (s55978988.adsl.online.nl [85.151.137.136]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id t8NJXnpI051532 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Sep 2015 21:33:50 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host s55978988.adsl.online.nl [85.151.137.136] claimed to be [192.168.1.21] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: What IS the right NTP behaviour ? From: dirkx@webweaving.org In-Reply-To: Date: Wed, 23 Sep 2015 21:33:50 +0200 Cc: Tim Kientzle , hackers@freebsd.org, Poul-Henning Kamp Content-Transfer-Encoding: quoted-printable Message-Id: References: <39337.1442999127@critter.freebsd.dk> To: Brandon Vincent X-Mailer: Apple Mail (2.2104) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Wed, 23 Sep 2015 21:33:51 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 19:43:52 -0000 > On 23 Sep 2015, at 20:04, Brandon Vincent = wrote: >=20 > On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = wrote: >> One concern I keep running into: Using NTP in VMs that are = frequently suspended/resumed. Though I suppose this may be covered by = your 'workstation' scenario (just step it after VM resume when you see = the large skew). >=20 > I would assume your hypervisor would sync the clock upon VM events. = Does it not? We have a fair number of problems; both with suspended VMs and moving = VMs - the hypervisor does the right thing - but things like can still = spot a step change; even backward. Dw.= From owner-freebsd-hackers@freebsd.org Wed Sep 23 19:53:27 2015 Return-Path: Delivered-To: freebsd-hackers@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 19C9AA08A6A for ; Wed, 23 Sep 2015 19:53:27 +0000 (UTC) (envelope-from reichert@numachi.com) 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 0469B1DDF for ; Wed, 23 Sep 2015 19:53:27 +0000 (UTC) (envelope-from reichert@numachi.com) Received: by mailman.ysv.freebsd.org (Postfix) id 02BA2A08A69; Wed, 23 Sep 2015 19:53:27 +0000 (UTC) Delivered-To: hackers@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 02587A08A68 for ; Wed, 23 Sep 2015 19:53:27 +0000 (UTC) (envelope-from reichert@numachi.com) Received: from away.numachi.com (away.numachi.com [66.228.38.138]) by mx1.freebsd.org (Postfix) with SMTP id B0CEB1DDE for ; Wed, 23 Sep 2015 19:53:26 +0000 (UTC) (envelope-from reichert@numachi.com) Received: (qmail 1978 invoked from network); 23 Sep 2015 19:46:44 -0000 Received: from unknown (HELO meisai.numachi.com) (71.181.44.212) by away.numachi.com with SMTP; 23 Sep 2015 19:46:44 -0000 Received: (qmail 24291 invoked by uid 1001); 23 Sep 2015 19:27:29 -0000 Date: Wed, 23 Sep 2015 15:27:29 -0400 From: Brian Reichert To: Brandon Vincent Cc: Tim Kientzle , hackers@freebsd.org, Poul-Henning Kamp Subject: Re: What IS the right NTP behaviour ? Message-ID: <20150923192729.GB78209@numachi.com> References: <39337.1442999127@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 19:53:27 -0000 On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: > On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle wrote: > > One concern I keep running into: Using NTP in VMs that are frequently suspended/resumed. Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew). > > I would assume your hypervisor would sync the clock upon VM events. Does it not? In my VMs that run an NTP client, I keep the hypervisor out of the loop, and let the guest's NTP client to it's work. E.g.: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 NTP Recommendations VMware recommends using NTP instead of VMware Tools periodic time synchronization. NTP is an industry standard and ensures accurate timekeeping in your guest. It may be necessary to open the firewall (UDP 123) to allow NTP traffic. > > Brandon Vincent > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" -- Brian Reichert BSD admin/developer at large From owner-freebsd-hackers@freebsd.org Wed Sep 23 20:35:11 2015 Return-Path: Delivered-To: freebsd-hackers@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 1F71BA074B7 for ; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) (envelope-from dirkx@webweaving.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 03EB91E2E for ; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 000DBA074B6; Wed, 23 Sep 2015 20:35:11 +0000 (UTC) Delivered-To: hackers@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 F3C33A074B5 for ; Wed, 23 Sep 2015 20:35:10 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A57A1E2D for ; Wed, 23 Sep 2015 20:35:09 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from [192.168.1.21] (s55978988.adsl.online.nl [85.151.137.136]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id t8NKXjLm052927 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Sep 2015 22:33:47 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host s55978988.adsl.online.nl [85.151.137.136] claimed to be [192.168.1.21] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: What IS the right NTP behaviour ? From: dirkx@webweaving.org In-Reply-To: <20150923192729.GB78209@numachi.com> Date: Wed, 23 Sep 2015 22:33:45 +0200 Cc: Brandon Vincent , hackers@freebsd.org, Poul-Henning Kamp Content-Transfer-Encoding: quoted-printable Message-Id: References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> To: Brian Reichert X-Mailer: Apple Mail (2.2104) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Wed, 23 Sep 2015 22:33:47 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Sep 2015 20:35:11 -0000 > On 23 Sep 2015, at 21:27, Brian Reichert wrote: >=20 > On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: >> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = wrote: >>> One concern I keep running into: Using NTP in VMs that are = frequently suspended/resumed. Though I suppose this may be covered by = your 'workstation' scenario (just step it after VM resume when you see = the large skew). >>=20 >> I would assume your hypervisor would sync the clock upon VM events. = Does it not? >=20 > In my VMs that run an NTP client, I keep the hypervisor out of the > loop, and let the guest's NTP client to it's work. > = ..http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&c= md=3DdisplayKC&externalId=3D1006427 Aye - but I=E2=80=99ve not found any clean way of doing that =E2=80=94 = now a small rc.d file does a stop of ntpd, an ntpdate (because the jumps = are bigger than what ntpd by default will accomodate) and a restart of = ntpd. You=E2=80=99d perhaps want the kernel or userland (ntpd) to understand = more of this. Dw. From owner-freebsd-hackers@freebsd.org Thu Sep 24 03:04:21 2015 Return-Path: Delivered-To: freebsd-hackers@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 D9B8DA06B04 for ; Thu, 24 Sep 2015 03:04:21 +0000 (UTC) (envelope-from gsuryacse7k@gmail.com) Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::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 A477B1948 for ; Thu, 24 Sep 2015 03:04:21 +0000 (UTC) (envelope-from gsuryacse7k@gmail.com) Received: by vkao3 with SMTP id o3so39903067vka.2 for ; Wed, 23 Sep 2015 20:04:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=IgW5Y9cPy2640zCzhpmQBaIjnfPUQ+rI2R1HdQNX4FY=; b=Uo+p6p8FBVYmXUCxPOAKlZ+Wb1RZqGB67t8Ia4/U5mC1Vwn/AfNPpXIpN+k0SNt3fN LkMbb5g0hN+2xkcDXxNvRy1lFkLGnUvXS6ATNJgo1G/oTscDHrsENzSVeb70sT1WNE69 5cB3Rrza9Ob04+zAgvaqT6Gsew8fC2AfTsbgo6EO1iZA2iJ/mliR3YbR9/Zx8dLyYIVO Kh6L66/S8d3BRjUioTUl7NwPfnHOqcPzR46Ic20Q87nkAfbKDeOcCxXGeT5x/6O79Wiv eDu6/jbTUxTyBHw4zQiZBTAKawF4bwA3ESwVtsQthtvHMSo6DWztCYaU0Wo5t39X1sqd 2GEQ== MIME-Version: 1.0 X-Received: by 10.31.49.67 with SMTP id x64mr25021269vkx.133.1443063859851; Wed, 23 Sep 2015 20:04:19 -0700 (PDT) Received: by 10.103.26.3 with HTTP; Wed, 23 Sep 2015 20:04:19 -0700 (PDT) Date: Wed, 23 Sep 2015 23:04:19 -0400 Message-ID: Subject: system map mutex and zone mutex witness warning From: suresh gumpula To: "freebsd-hackers@freebsd.org" X-Mailman-Approved-At: Thu, 24 Sep 2015 03:50:51 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 03:04:22 -0000 Hi, I am seeing the following witness warning while booting on 8.1. Is it a known issue and resolved in later kernels ? Can somebody please comment on this ? isitmychild: rmatrix mismatch between system map (index 43) and UMA zone (index 57): w_rmatrix[43][57] == 1 but w_rmatrix[57][43] == 0 KDB: stack backtrace: kdb_backtrace() at kdb_backtrace+0x3e witness_line() at witness_line+0xca4 witness_line() at witness_line+0xcf9 witness_releaseok() at witness_releaseok+0x1623 witness_checkorder() at witness_checkorder+0x37e _mtx_lock_flags() at _mtx_lock_flags+0x113 uma_zalloc_arg() at uma_zalloc_arg+0x1449 vmspace_swap_count() at vmspace_swap_count+0xc52 uma_zalloc_arg() at uma_zalloc_arg+0x10e6 uma_zalloc_arg() at uma_zalloc_arg+0x5ef vmspace_alloc() at vmspace_alloc+0x180 vm_map_init() at vm_map_init+0xec vm_map_insert() at vm_map_insert+0x4cb kmem_malloc() at kmem_malloc+0x3de zone_drain() at zone_drain+0x822 uma_large_malloc() at uma_large_malloc+0x4e malloc() at malloc+0x251 swap_pager_swap_init() at swap_pager_swap_init+0x219 vm_pageout_oom() at vm_pageout_oom+0x952 fork_exit() at fork_exit+0x185 fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff806bb61d30, rbp = 0 --- Witness disabled. Thanks Suresh From owner-freebsd-hackers@freebsd.org Thu Sep 24 09:13:41 2015 Return-Path: Delivered-To: freebsd-hackers@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 CB5A5A075B6 for ; Thu, 24 Sep 2015 09:13:41 +0000 (UTC) (envelope-from erik+lists@cederstrand.dk) 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 AD8541C19 for ; Thu, 24 Sep 2015 09:13:41 +0000 (UTC) (envelope-from erik+lists@cederstrand.dk) Received: by mailman.ysv.freebsd.org (Postfix) id AB3E8A075B4; Thu, 24 Sep 2015 09:13:41 +0000 (UTC) Delivered-To: hackers@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 AAD77A075B3 for ; Thu, 24 Sep 2015 09:13:41 +0000 (UTC) (envelope-from erik+lists@cederstrand.dk) Received: from mailrelay8.public.one.com (mailrelay8.public.one.com [91.198.169.216]) (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 D1D711C18 for ; Thu, 24 Sep 2015 09:13:40 +0000 (UTC) (envelope-from erik+lists@cederstrand.dk) X-HalOne-Cookie: 84d5acdb8e57486aa7e01f59dee47e0b22d14416 X-HalOne-ID: 606e74b3-629c-11e5-9643-b82a72cffc46 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cederstrand.dk; s=20140924; h=from:subject:date:message-id:to:cc:mime-version:content-type: content-transfer-encoding:in-reply-to:references; bh=VrJP1OsTi5oOxEXq1g45p5rBi9pridzWiZJHwfUyVJ0=; b=XaOfJ2vxgEWgOoz1syYm/7cepXG6hd0AZ4h7AVsgvXvSKg7+bXdZnV5PX18ME5pJjJ7xLEwQbi9sX bsAJzMi8ZiL7quGlc2SXv9r12+ZAJt7R1E/PNYhQuqorxWqWnAQoBj1iZ7E9rl8NAbMgw2qOf8tJ7F 50NqjQCtxIoXqCTQ= Received: from [192.168.187.69] (unknown [87.54.33.251]) by smtpfilter4.public.one.com (Halon Mail Gateway) with ESMTPSA; Thu, 24 Sep 2015 09:12:27 +0000 (GMT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: What IS the right NTP behaviour ? From: Erik Cederstrand In-Reply-To: Date: Thu, 24 Sep 2015 11:12:29 +0200 Cc: FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <0CAEE340-B9DF-4772-8600-8A0904636452@cederstrand.dk> References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> To: dirkx@webweaving.org X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 09:13:41 -0000 > Den 23/09/2015 kl. 22.33 skrev dirkx@webweaving.org: >=20 >=20 >> On 23 Sep 2015, at 21:27, Brian Reichert = wrote: >>=20 >> On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: >>> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = wrote: >>>> One concern I keep running into: Using NTP in VMs that are = frequently suspended/resumed. Though I suppose this may be covered by = your 'workstation' scenario (just step it after VM resume when you see = the large skew). >>>=20 >>> I would assume your hypervisor would sync the clock upon VM events. = Does it not? >>=20 >> In my VMs that run an NTP client, I keep the hypervisor out of the >> loop, and let the guest's NTP client to it's work. >=20 >> = ..http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&c= md=3DdisplayKC&externalId=3D1006427 >=20 > Aye - but I=E2=80=99ve not found any clean way of doing that =E2=80=94 = now a small rc.d file does a stop of ntpd, an ntpdate (because the jumps = are bigger than what ntpd by default will accomodate) and a restart of = ntpd. Does "tinker panic 0" in /etc/ntp.conf not work for you? Erik From owner-freebsd-hackers@freebsd.org Thu Sep 24 09:29:05 2015 Return-Path: Delivered-To: freebsd-hackers@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 3E33CA07F8E for ; Thu, 24 Sep 2015 09:29:05 +0000 (UTC) (envelope-from dirkx@webweaving.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 1D91212D8 for ; Thu, 24 Sep 2015 09:29:05 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1B4A5A07F8D; Thu, 24 Sep 2015 09:29:05 +0000 (UTC) Delivered-To: hackers@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 F412DA07F8C for ; Thu, 24 Sep 2015 09:29:04 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9776512D7 for ; Thu, 24 Sep 2015 09:29:03 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from [10.11.0.122] (5ED29D98.cm-7-3c.dynamic.ziggo.nl [94.210.157.152]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id t8O9Rh9N045874 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Sep 2015 11:27:44 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED29D98.cm-7-3c.dynamic.ziggo.nl [94.210.157.152] claimed to be [10.11.0.122] Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3093\)) Subject: Re: What IS the right NTP behaviour ? From: Dirk-Willem van Gulik In-Reply-To: <0CAEE340-B9DF-4772-8600-8A0904636452@cederstrand.dk> Date: Thu, 24 Sep 2015 11:27:43 +0200 Cc: FreeBSD Hackers Message-Id: <05581AEE-5A92-49B0-8F35-FE96BE15CF2A@webweaving.org> References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> <0CAEE340-B9DF-4772-8600-8A0904636452@cederstrand.dk> To: Erik Cederstrand X-Mailer: Apple Mail (2.3093) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Thu, 24 Sep 2015 11:27:44 +0200 (CEST) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 09:29:05 -0000 On 24 Sep 2015, at 11:12, Erik Cederstrand = wrote: >=20 >> Den 23/09/2015 kl. 22.33 skrev dirkx@webweaving.org: >>=20 >>> On 23 Sep 2015, at 21:27, Brian Reichert = wrote: >>>=20 >>> On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: >>>> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = wrote: >>>>> One concern I keep running into: Using NTP in VMs that are = frequently suspended/resumed. Though I suppose this may be covered by = your 'workstation' scenario (just step it after VM resume when you see = the large skew). >>>>=20 >>>> I would assume your hypervisor would sync the clock upon VM events. = Does it not? >>>=20 >>> In my VMs that run an NTP client, I keep the hypervisor out of the >>> loop, and let the guest's NTP client to it's work. >>=20 >>> = ..http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&c= md=3DdisplayKC&externalId=3D1006427 >>=20 >> Aye - but I=E2=80=99ve not found any clean way of doing that =E2=80=94 = now a small rc.d file does a stop of ntpd, an ntpdate (because the jumps = are bigger than what ntpd by default will accomodate) and a restart of = ntpd. >=20 > Does "tinker panic 0" in /etc/ntp.conf not work for you? Yes and no - it would work; but we have another set of issues (largely = legacy with bad security that waits for equipment to be old enough to be = replaced) that wants us to have it the panic threshold set to something = sensible (we set it to 10 second) as the result to a string of incidents = in the past (and recent past). So I guess what we=E2=80=99d want is something like =E2=80=98tinker = panic 0=E2=80=99. Dw From owner-freebsd-hackers@freebsd.org Thu Sep 24 09:33:48 2015 Return-Path: Delivered-To: freebsd-hackers@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 4ED08A08257 for ; Thu, 24 Sep 2015 09:33:48 +0000 (UTC) (envelope-from dirkx@webweaving.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 300AC17C1 for ; Thu, 24 Sep 2015 09:33:48 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: by mailman.ysv.freebsd.org (Postfix) id 2D990A08256; Thu, 24 Sep 2015 09:33:48 +0000 (UTC) Delivered-To: hackers@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 1362FA08254 for ; Thu, 24 Sep 2015 09:33:48 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from weser.webweaving.org (weser.webweaving.org [148.251.234.232]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.webweaving.org", Issuer "RapidSSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 979A617C0 for ; Thu, 24 Sep 2015 09:33:47 +0000 (UTC) (envelope-from dirkx@webweaving.org) Received: from [10.11.0.122] (5ED29D98.cm-7-3c.dynamic.ziggo.nl [94.210.157.152]) (authenticated bits=0) by weser.webweaving.org (8.15.2/8.15.2) with ESMTPSA id t8O9WSRh045967 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Sep 2015 11:32:28 +0200 (CEST) (envelope-from dirkx@webweaving.org) X-Authentication-Warning: weser.webweaving.org: Host 5ED29D98.cm-7-3c.dynamic.ziggo.nl [94.210.157.152] claimed to be [10.11.0.122] Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3093\)) Subject: Re: What IS the right NTP behaviour ? From: Dirk-Willem van Gulik In-Reply-To: <05581AEE-5A92-49B0-8F35-FE96BE15CF2A@webweaving.org> Date: Thu, 24 Sep 2015 11:32:28 +0200 Cc: FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <2E0C3E03-127C-4765-B359-7809B4B057F0@webweaving.org> References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> <0CAEE340-B9DF-4772-8600-8A0904636452@cederstrand.dk> <05581AEE-5A92-49B0-8F35-FE96BE15CF2A@webweaving.org> To: Erik Cederstrand X-Mailer: Apple Mail (2.3093) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (weser.webweaving.org [148.251.234.232]); Thu, 24 Sep 2015 11:32:28 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 09:33:48 -0000 > On 24 Sep 2015, at 11:27, Dirk-Willem van Gulik = wrote: >=20 > On 24 Sep 2015, at 11:12, Erik Cederstrand = wrote: >>=20 >>> Den 23/09/2015 kl. 22.33 skrev dirkx@webweaving.org: >>>=20 >>>> On 23 Sep 2015, at 21:27, Brian Reichert = wrote: >>>>=20 >>>> On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: >>>>> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle = wrote: >>>>>> One concern I keep running into: Using NTP in VMs that are = frequently suspended/resumed. Though I suppose this may be covered by = your 'workstation' scenario (just step it after VM resume when you see = the large skew). >>>>>=20 >>>>> I would assume your hypervisor would sync the clock upon VM = events. Does it not? >>>>=20 >>>> In my VMs that run an NTP client, I keep the hypervisor out of the >>>> loop, and let the guest's NTP client to it's work. >>>=20 >>>> = ..http://kb.vmware.com/selfservice/microsites/search.do?language=3Den_US&c= md=3DdisplayKC&externalId=3D1006427 >>>=20 >>> Aye - but I=E2=80=99ve not found any clean way of doing that =E2=80=94= now a small rc.d file does a stop of ntpd, an ntpdate (because the = jumps are bigger than what ntpd by default will accomodate) and a = restart of ntpd. >>=20 >> Does "tinker panic 0" in /etc/ntp.conf not work for you? >=20 > Yes and no - it would work; but we have another set of issues (largely = legacy with bad security that waits for equipment to be old enough to be = replaced) that wants us to have it the panic threshold set to something = sensible (we set it to 10 second) as the result to a string of incidents = in the past (and recent past). >=20 > So I guess what we=E2=80=99d want is something like =E2=80=98tinker = panic 0=E2=80=99. Actually - reviewing the incident logs - I take that back. The issue is = that panic allows a delta in BOTH directions: if (fabs(fp_offset) > clock_panic && clock_panic > 0 && = !allow_panic) { =E2=80=A6 I guess having two types of panic; one which only allows a large = =E2=80=98panic =E2=80=99s the positive direction would give you the best = of both worlds in VM Land. As across the estate - in my experience; upon = the move of a VM - the clock rarely jumps back more than seconds; if = that. And those hypervisor clocks are in those cases all > 10 seconds = off; so bailing is fair game. Dw From owner-freebsd-hackers@freebsd.org Thu Sep 24 13:07:52 2015 Return-Path: Delivered-To: freebsd-hackers@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 BDD22A07879; Thu, 24 Sep 2015 13:07:52 +0000 (UTC) (envelope-from joerg@britannica.bec.de) Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.smtp.rzone.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C5A41CF9; Thu, 24 Sep 2015 13:07:51 +0000 (UTC) (envelope-from joerg@britannica.bec.de) X-RZG-AUTH: :JiIXek6mfvEEUpFQdo7Fj1/zg48CFjWjQuEfXeSt/nWoxcg0dfabJPmkcf8ZVw== X-RZG-CLASS-ID: mo00 Received: from britannica.bec.de (ip-2-207-231-56.web.vodafone.de [2.207.231.56]) by smtp.strato.de (RZmta 37.12 DYNA|AUTH) with ESMTPSA id 603a87r8OD7mNcp (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Thu, 24 Sep 2015 15:07:48 +0200 (CEST) Date: Thu, 24 Sep 2015 15:07:47 +0200 From: Joerg Sonnenberger To: freebsd-hackers@freebsd.org, hackers@freebsd.org Subject: Re: What IS the right NTP behaviour ? Message-ID: <20150924130747.GB10913@britannica.bec.de> Mail-Followup-To: freebsd-hackers@freebsd.org, hackers@freebsd.org References: <39337.1442999127@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <39337.1442999127@critter.freebsd.dk> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 13:07:52 -0000 On Wed, Sep 23, 2015 at 09:05:27AM +0000, Poul-Henning Kamp wrote: > It is no surprise that people have different expectations of how > timekeeping should behave, and I'm trying to figure out > what Do What I Want is. > > I think I have identified three variations of "DWIW", which I have > named "eCommerce", "SCADA" and "Workstation" I think there is a class of network devices similar to SCADA, where the correct system time is a bonus, highly desirable, but still a bonus. Many entry class switches or routers often come without battery buffered RTC. For those, startup should not wait for NTP to become ready at all. Time drifts beyond a certain limit are better served by just stepping. The primary intention here is to have logfiles that can be correlated. Joerg From owner-freebsd-hackers@freebsd.org Thu Sep 24 14:24:37 2015 Return-Path: Delivered-To: freebsd-hackers@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 402C6A08DE4 for ; Thu, 24 Sep 2015 14:24:37 +0000 (UTC) (envelope-from ian@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 255241B60 for ; Thu, 24 Sep 2015 14:24:37 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 23CB1A08DE3; Thu, 24 Sep 2015 14:24:37 +0000 (UTC) Delivered-To: hackers@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 099C2A08DE2 for ; Thu, 24 Sep 2015 14:24:37 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from pmta2.delivery6.ore.mailhop.org (pmta2.delivery6.ore.mailhop.org [54.200.129.228]) (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 D393D1B5E for ; Thu, 24 Sep 2015 14:24:36 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from ilsoft.org (unknown [73.34.117.227]) by outbound2.ore.mailhop.org (Halon Mail Gateway) with ESMTPSA; Thu, 24 Sep 2015 14:24:07 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t8OENRuu003304; Thu, 24 Sep 2015 08:23:27 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1443104607.1224.265.camel@freebsd.org> Subject: Re: What IS the right NTP behaviour ? From: Ian Lepore To: Dirk-Willem van Gulik Cc: Erik Cederstrand , FreeBSD Hackers Date: Thu, 24 Sep 2015 08:23:27 -0600 In-Reply-To: <05581AEE-5A92-49B0-8F35-FE96BE15CF2A@webweaving.org> References: <39337.1442999127@critter.freebsd.dk> <20150923192729.GB78209@numachi.com> <0CAEE340-B9DF-4772-8600-8A0904636452@cederstrand.dk> <05581AEE-5A92-49B0-8F35-FE96BE15CF2A@webweaving.org> Content-Type: text/plain; charset="windows-1251" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 14:24:37 -0000 On Thu, 2015-09-24 at 11:27 +0200, Dirk-Willem van Gulik wrote: > On 24 Sep 2015, at 11:12, Erik Cederstrand wrote: > > > >> Den 23/09/2015 kl. 22.33 skrev dirkx@webweaving.org: > >> > >>> On 23 Sep 2015, at 21:27, Brian Reichert wrote: > >>> > >>> On Wed, Sep 23, 2015 at 11:04:43AM -0700, Brandon Vincent wrote: > >>>> On Wed, Sep 23, 2015 at 10:35 AM, Tim Kientzle wrote: > >>>>> One concern I keep running into: Using NTP in VMs that are frequently suspended/resumed. Though I suppose this may be covered by your 'workstation' scenario (just step it after VM resume when you see the large skew). > >>>> > >>>> I would assume your hypervisor would sync the clock upon VM events. Does it not? > >>> > >>> In my VMs that run an NTP client, I keep the hypervisor out of the > >>> loop, and let the guest's NTP client to it's work. > >> > >>> ..http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006427 > >> > >> Aye - but I’ve not found any clean way of doing that — now a small rc.d file does a stop of ntpd, an ntpdate (because the jumps are bigger than what ntpd by default will accomodate) and a restart of ntpd. > > > > Does "tinker panic 0" in /etc/ntp.conf not work for you? > > Yes and no - it would work; but we have another set of issues (largely legacy with bad security that waits for equipment to be old enough to be replaced) that wants us to have it the panic threshold set to something sensible (we set it to 10 second) as the result to a string of incidents in the past (and recent past). > > So I guess what we’d want is something like ‘tinker panic 0’. > > Dw The drawback to using tinker to allow stepping is that the logic for stepping is different at startup and after being in-sync. A startup step happens very quickly (as long as a drift frequency was obtained from a file). Once sync has been achieved a step will happen only after the stepout period has elapsed, and the default stepout period is 900 seconds iirc. You can lower that with tinker, but there's a limit to how low you can go. If you set stepout too low and your clock drift rate is high, you can end up in a situation where ntpd can never "capture" the drifting clock and steer it to be on-time. (The stepout period is effectively the time constant for the PLL.) What I've wanted more than once is the ability to "re-arm" that startup-time stepout logic programatically (like with an ntp control message using ntpq). Right now the only way I know to do that is to kill and restart ntpd. -- Ian From owner-freebsd-hackers@freebsd.org Thu Sep 24 16:50:07 2015 Return-Path: Delivered-To: freebsd-hackers@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 67DA6A062FE for ; Thu, 24 Sep 2015 16:50:07 +0000 (UTC) (envelope-from bdrewery@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 501FC1902; Thu, 24 Sep 2015 16:50:07 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 48FFC13E6; Thu, 24 Sep 2015 16:50:07 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id E7FCBBFDE; Thu, 24 Sep 2015 16:50:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id KbSwX99X1_t0; Thu, 24 Sep 2015 16:50:04 +0000 (UTC) Subject: Re: system map mutex and zone mutex witness warning DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com A14FFBFD6 To: suresh gumpula , "freebsd-hackers@freebsd.org" References: From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <560429BA.6030307@FreeBSD.org> Date: Thu, 24 Sep 2015 09:50:02 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NxnAujICcIq68KTFi4cIsBEDrPmEsECup" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 16:50:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NxnAujICcIq68KTFi4cIsBEDrPmEsECup Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/23/2015 8:04 PM, suresh gumpula wrote: > Hi, > I am seeing the following witness warning while booting on 8.1. = Is > it a known issue and > resolved in later kernels ? Can somebody please comment on this ? This may be obvious, but 8.1 is long unsupported. 8.4 just expired a few months ago as well. The knowledge of 8.1 is going to be pretty low at this point. You should try using a newer release to see if you still have the problem. 8.1 -> 8.4 is a pretty safe upgrade if you can manage it and have reasons to not go to 9 or 10. --=20 Regards, Bryan Drewery --NxnAujICcIq68KTFi4cIsBEDrPmEsECup 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 iQEcBAEBAgAGBQJWBCm7AAoJEDXXcbtuRpfPOvIH/2Kpbs9AuQywZCI4NenrfE+K 1UIT5fJK1SzAEn5afGsoGOrkVuKtifa4ykXam/2I97fvyeUJVhFj/O0f+5Dywud8 PdIFeG+Z6aWes/AjPqpESei2VwAlxmTsyHK8cQCPWGvn+KhBTCqYdNEWUu4YkN7E 9en+X/RVgq02hTBnteNtCoiq1FhVNqk6OBx4PxKYZcub9fRL/7z+8oCCVAZED4rJ srNWPADbQ4JyEE2F0odoKqoaS/ArOVR6tx3ce6Y3GkBfipEpbOc20FWYw5EqVoGY nNhPWgSiuT7O4kxa/x3sFo5g+3cvxFvg79dB4ET7nmwIrjqVbLPZ0lm8Vi8zhZc= =eP3t -----END PGP SIGNATURE----- --NxnAujICcIq68KTFi4cIsBEDrPmEsECup-- From owner-freebsd-hackers@freebsd.org Thu Sep 24 17:41:48 2015 Return-Path: Delivered-To: freebsd-hackers@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 0851FA08719 for ; Thu, 24 Sep 2015 17:41:48 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 B780A1BFB for ; Thu, 24 Sep 2015 17:41:47 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by qkdw123 with SMTP id w123so32687882qkd.0 for ; Thu, 24 Sep 2015 10:41:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=iqTzwZr/zQt/NYFZuAsS4a+I3ThG9b/1p1Wf0A471Sw=; b=WYKQ/9zZqMJ9tWB82ciEZiJejUgp2u+ByuDUXMBxkA0GCaFF2SOStizICqaqWPhNnD c9B/AzFq+vE+bQKjZnr3O3fdec05PnWEHnyyEH7U2+Awu7asEnGBBfuy2bGAsI7HpYIv NzkuOSi7xGgQpibsuC6Pl1VBW490MMoIE+hgYRPkEORdGY+A+S7Br3XiM7JbQuiPcAlz Z4H+l1M+tlg3NiiSAHU29PWQo/1WYV16jWSVElCBc+Jd5O5EKVvopyZo1qyvXa++UD+Q 94KaBa5rGZJXGa5fjzC/zNnep0WzapLB+/zJ8Kv7LkVknJpM1eeY/srtSNvjxcyf6WM+ tSSA== X-Received: by 10.55.17.12 with SMTP id b12mr1123519qkh.69.1443116506867; Thu, 24 Sep 2015 10:41:46 -0700 (PDT) Received: from muskytusk ([104.236.250.12]) by smtp.gmail.com with ESMTPSA id t48sm3851188qgd.15.2015.09.24.10.41.45 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Sep 2015 10:41:46 -0700 (PDT) Sender: Mark Johnston Date: Thu, 24 Sep 2015 17:41:11 +0000 From: Mark Johnston To: suresh gumpula Cc: "freebsd-hackers@freebsd.org" Subject: Re: system map mutex and zone mutex witness warning Message-ID: <20150924173916.GA78083@muskytusk> References: 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-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2015 17:41:48 -0000 On Wed, Sep 23, 2015 at 11:04:19PM -0400, suresh gumpula wrote: > Hi, > I am seeing the following witness warning while booting on 8.1. Is > it a known issue and > resolved in later kernels ? Can somebody please comment on this ? I've seen this occur when multiple threads race to establish a lock order: https://svnweb.freebsd.org/changeset/base/284127 The change should apply to 8.1, but there may be other relevant bug fixes missing. > > isitmychild: rmatrix mismatch between system map (index 43) and UMA zone > (index 57): w_rmatrix[43][57] == 1 but w_rmatrix[57][43] == 0 > KDB: stack backtrace: > kdb_backtrace() at kdb_backtrace+0x3e > witness_line() at witness_line+0xca4 > witness_line() at witness_line+0xcf9 > witness_releaseok() at witness_releaseok+0x1623 > witness_checkorder() at witness_checkorder+0x37e > _mtx_lock_flags() at _mtx_lock_flags+0x113 > uma_zalloc_arg() at uma_zalloc_arg+0x1449 > vmspace_swap_count() at vmspace_swap_count+0xc52 > uma_zalloc_arg() at uma_zalloc_arg+0x10e6 > uma_zalloc_arg() at uma_zalloc_arg+0x5ef > vmspace_alloc() at vmspace_alloc+0x180 > vm_map_init() at vm_map_init+0xec > vm_map_insert() at vm_map_insert+0x4cb > kmem_malloc() at kmem_malloc+0x3de > zone_drain() at zone_drain+0x822 > uma_large_malloc() at uma_large_malloc+0x4e > malloc() at malloc+0x251 > swap_pager_swap_init() at swap_pager_swap_init+0x219 > vm_pageout_oom() at vm_pageout_oom+0x952 > fork_exit() at fork_exit+0x185 > fork_trampoline() at fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff806bb61d30, rbp = 0 --- > Witness disabled. > > > Thanks > Suresh > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Fri Sep 25 00:56:29 2015 Return-Path: Delivered-To: freebsd-hackers@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 AA6C1A08891 for ; Fri, 25 Sep 2015 00:56:29 +0000 (UTC) (envelope-from gsuryacse7k@gmail.com) Received: from mail-vk0-x233.google.com (mail-vk0-x233.google.com [IPv6:2607:f8b0: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 66C001924; Fri, 25 Sep 2015 00:56:29 +0000 (UTC) (envelope-from gsuryacse7k@gmail.com) Received: by vkfp126 with SMTP id p126so47537121vkf.3; Thu, 24 Sep 2015 17:56:28 -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=CZX538BfE0soG+txhnQyzP63W3G1Z2BnRKPZXi5wS4U=; b=QHf7Sfwsa/BNCAs659oXKXiaLoZJHQEKwmxRDngUvNv4XuChOFtJep7GQw6nqS/t6U DmzVSyYu/UJptyC3xUtsLJLbunOqmfG1dpwrUDSRK7JtCQKubcY3RK1cYLipq6W0fq9C nX+RigwTZMdfFPfUpKogHYrwhYAjzZDD5ASKmco+cJdsGDhxalZqQzZ3BHhmbJokcd1I 5L9v9TGvd0gxR2ThtivCJIlJPH1ne3O7BcnQ6L4MoTNdoGTnnztVYAI7mjUbGd11uWbG 7wkIxkmcgv9R1e2LYUdDPezdR2c9sbwRl9pTURNOPyDTsVYPhPcvNk7ks7tSHdACGcf2 NpKw== MIME-Version: 1.0 X-Received: by 10.31.134.193 with SMTP id i184mr1512184vkd.64.1443142588382; Thu, 24 Sep 2015 17:56:28 -0700 (PDT) Received: by 10.103.26.3 with HTTP; Thu, 24 Sep 2015 17:56:28 -0700 (PDT) In-Reply-To: <20150924173916.GA78083@muskytusk> References: <20150924173916.GA78083@muskytusk> Date: Thu, 24 Sep 2015 20:56:28 -0400 Message-ID: Subject: Re: system map mutex and zone mutex witness warning From: suresh gumpula To: Mark Johnston Cc: "freebsd-hackers@freebsd.org" X-Mailman-Approved-At: Fri, 25 Sep 2015 01:32:08 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Sep 2015 00:56:29 -0000 Thanks Mark and Bryan. I will apply this change and see if it goes away. Thanks Suresh On Thu, Sep 24, 2015 at 1:41 PM, Mark Johnston wrote: > On Wed, Sep 23, 2015 at 11:04:19PM -0400, suresh gumpula wrote: > > Hi, > > I am seeing the following witness warning while booting on 8.1. > Is > > it a known issue and > > resolved in later kernels ? Can somebody please comment on this ? > > I've seen this occur when multiple threads race to establish a lock > order: https://svnweb.freebsd.org/changeset/base/284127 > > The change should apply to 8.1, but there may be other relevant bug > fixes missing. > > > > > isitmychild: rmatrix mismatch between system map (index 43) and UMA zone > > (index 57): w_rmatrix[43][57] == 1 but w_rmatrix[57][43] == 0 > > KDB: stack backtrace: > > kdb_backtrace() at kdb_backtrace+0x3e > > witness_line() at witness_line+0xca4 > > witness_line() at witness_line+0xcf9 > > witness_releaseok() at witness_releaseok+0x1623 > > witness_checkorder() at witness_checkorder+0x37e > > _mtx_lock_flags() at _mtx_lock_flags+0x113 > > uma_zalloc_arg() at uma_zalloc_arg+0x1449 > > vmspace_swap_count() at vmspace_swap_count+0xc52 > > uma_zalloc_arg() at uma_zalloc_arg+0x10e6 > > uma_zalloc_arg() at uma_zalloc_arg+0x5ef > > vmspace_alloc() at vmspace_alloc+0x180 > > vm_map_init() at vm_map_init+0xec > > vm_map_insert() at vm_map_insert+0x4cb > > kmem_malloc() at kmem_malloc+0x3de > > zone_drain() at zone_drain+0x822 > > uma_large_malloc() at uma_large_malloc+0x4e > > malloc() at malloc+0x251 > > swap_pager_swap_init() at swap_pager_swap_init+0x219 > > vm_pageout_oom() at vm_pageout_oom+0x952 > > fork_exit() at fork_exit+0x185 > > fork_trampoline() at fork_trampoline+0xe > > --- trap 0, rip = 0, rsp = 0xffffff806bb61d30, rbp = 0 --- > > Witness disabled. > > > > > > Thanks > > Suresh > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to " > freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Sat Sep 26 11:03:19 2015 Return-Path: Delivered-To: freebsd-hackers@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 141DD9B84C5 for ; Sat, 26 Sep 2015 11:03:19 +0000 (UTC) (envelope-from ftigeot@wolfpond.org) Received: from gw.zefyris.com (sabik.zefyris.com [IPv6:2001:7a8:3c67:2::254]) (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 9B1C582A; Sat, 26 Sep 2015 11:03:17 +0000 (UTC) (envelope-from ftigeot@wolfpond.org) Received: from sekishi.zefyris.com (sekishi.zefyris.com [IPv6:2001:7a8:3c67:2:0:0:0:12]) by gw.zefyris.com (8.15.1/8.14.5) with ESMTP id t8QB39Dc095876; Sat, 26 Sep 2015 13:03:10 +0200 (CEST) Date: Sat, 26 Sep 2015 13:03:09 +0200 From: Francois Tigeot To: John Baldwin Cc: "Pokala, Ravi" , "freebsd-hackers@freebsd.org" Subject: Re: bus_.*_resource() and rid Message-ID: <20150926110308.GA14568@sekishi.zefyris.com> References: <1685918.WyYIclYTSg@ralph.baldwin.cx> <1637146.Rv3dkk0gMi@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1637146.Rv3dkk0gMi@ralph.baldwin.cx> User-Agent: Mutt/1.5.23 (2014-03-12) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gw.zefyris.com [IPv6:2001:7a8:3c67:2:0:0:0:254]); Sat, 26 Sep 2015 13:03:12 +0200 (CEST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 11:03:19 -0000 On Wed, Sep 23, 2015 at 08:07:55AM -0700, John Baldwin wrote: > On Friday, September 11, 2015 02:37:58 AM Pokala, Ravi wrote: > > > > I'll look into bus_get_resource(). Oh, look - there's no manpage > > (share/man/man9/bus_get_resource.9 does not exist, despite being a "see > > also" entry in bus_set_resource.9). :-S > > Time for Someone(tm) to write one. :-/ I'm a bit late to the party but you could just grab DragonFly's version: http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/share/man/man9/bus_get_resource.9 -- Francois Tigeot From owner-freebsd-hackers@freebsd.org Sat Sep 26 14:54:15 2015 Return-Path: Delivered-To: freebsd-hackers@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 2EF42A0AE00 for ; Sat, 26 Sep 2015 14:54:15 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-yk0-f177.google.com (mail-yk0-f177.google.com [209.85.160.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 F0B8CF6F for ; Sat, 26 Sep 2015 14:54:14 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by ykdz138 with SMTP id z138so139264239ykd.2 for ; Sat, 26 Sep 2015 07:54:08 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=2hzMwrxghzISZNLIXh72S634BRq4aj39tNQUVcsAIOw=; b=QNnaTulBgnoiV/Mk9YLYx+YcAAvq9MbXlaVLIdIwigupLZoC4ylTlova1Ve5tKCdPd dZ9T6jjXUBRDgLprr1C0iybVbBEeQjktd/HFD6CJg6K7bqrLqEBGgGSK3s8lnJeIGxl7 fKjYpgxwGfRXVqrHyA/pp2ePabe33mt0QQ4+JTw/Cbnm1UC1VfGHtr/7MK6gwGhXC+Sp Gz6F9Iuk1NPWLhDeG+qUQJyEaFKjkatZ12yPrkXBwJp9LQxVnZMpmpRrZYQpbYuj61iT sPa79aMm+vedBUd3GQpZk38a7QysZa/B1g9llN8dze4g13BkbuDoZ/5f/OioXGrpwgwB 7cFg== X-Received: by 10.129.77.9 with SMTP id a9mr7616200ywb.150.1443279248328; Sat, 26 Sep 2015 07:54:08 -0700 (PDT) Received: from mail-yk0-f171.google.com (mail-yk0-f171.google.com. [209.85.160.171]) by smtp.gmail.com with ESMTPSA id j67sm6425803ywg.52.2015.09.26.07.54.07 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 26 Sep 2015 07:54:08 -0700 (PDT) Received: by ykdt18 with SMTP id t18so139338205ykd.3 for ; Sat, 26 Sep 2015 07:54:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.170.127.203 with SMTP id t194mr9338289ykb.41.1443279247657; Sat, 26 Sep 2015 07:54:07 -0700 (PDT) Reply-To: cem@FreeBSD.org Received: by 10.37.60.198 with HTTP; Sat, 26 Sep 2015 07:54:07 -0700 (PDT) In-Reply-To: <20150926110308.GA14568@sekishi.zefyris.com> References: <1685918.WyYIclYTSg@ralph.baldwin.cx> <1637146.Rv3dkk0gMi@ralph.baldwin.cx> <20150926110308.GA14568@sekishi.zefyris.com> Date: Sat, 26 Sep 2015 07:54:07 -0700 Message-ID: Subject: Re: bus_.*_resource() and rid From: Conrad Meyer To: Francois Tigeot Cc: "freebsd-hackers@freebsd.org" , "Pokala, Ravi" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Sep 2015 14:54:15 -0000 On Sat, Sep 26, 2015 at 4:03 AM, Francois Tigeot wro= te: > I'm a bit late to the party but you could just grab DragonFly's version: > http://gitweb.dragonflybsd.org/dragonfly.git/blob/HEAD:/share/man/man9/bu= s_get_resource.9 Works for me =E2=80=94 r288271. Best, Conrad