From owner-freebsd-current@freebsd.org Sun Aug 12 11:21:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0967D106CDFB for ; Sun, 12 Aug 2018 11:21:29 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 98A3183696 for ; Sun, 12 Aug 2018 11:21:28 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x232.google.com with SMTP id h23-v6so9042840ita.5 for ; Sun, 12 Aug 2018 04:21:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Uo3PbApSEUepwdrgUDYu1FjJNSJl4FEbbHdvCW9fiD8=; b=INcLAblEh/Ce5rlWCPQ6GPPgqCEVL1fE7vOJiKKrZ3ipnN6ixZ7H+5yTfzMFrF5R56 wV8U6qbDEcEaGDNVaQpGY7uL2YykKIoHP0bRlpnmV5A1Dc375qu684VMc91uHekbIZ8n jEhXjkH6HVCP2oON+SB8FlaqAWYYk7MFT9WddWRnf6GWq7Y8VutCMpuNbPu1Y+zNOSdJ Kub744P6/nUzzFPnfn9mb7tYUinsxCfS4QGjtFZ/3YCOKhdqIwHXEjqYzCDVy6ZLo71v 1Zo9dS//x9Gn+diA7X0m4dUw752xxcMOSRNFM8l+B/hBjlwArnXtJxYBkryPSLvTPMkv KPWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Uo3PbApSEUepwdrgUDYu1FjJNSJl4FEbbHdvCW9fiD8=; b=tqXXkiL0wIMB1wYnKaMOmGeW1ZJwzSbJeTzZxbWqRE+B1tfIh6DdaFpozCWHNr7xnl SLNLbffPuz0yXUjH00VLWvTuhdkEzwnODDdHGqRwaHJ7Vmdgons7DZV5uNlU6t+BEwxl KFoKbFtBMnmne78RLI7ie0MxZNfweParpL5gmt1xA3SNPsAGwLe1I4kWxVq/32H0DmCl 8g75D9+wq7EshR5UpFBj9lKW3iwLepopuP44arITE+rIUCmHnuBiQTWO5gOkRfps8Iql TKoqVY8KWlky9V66/BmbeEUBjkiNtnZTmo7Vms4Wy5SOllIHGfWWsF6Im892BFltEUu0 3UyA== X-Gm-Message-State: AOUpUlFa5Ss7nm9Ow11xXVvwOF76tV2kjtZUO7sjsXSt7j33evUCGWpa qnYvtDOwGLsP539AuzRudgukp+M5AX8W1AIweFHRpFG3 X-Google-Smtp-Source: AA+uWPwf+6CxaUa7KlmRp0SNOmoEICNfOi75JRJ+77jCSiWvB5qtlYkoXl/IJ67Znjvz5DSDwnP/O/I322e2EeYug5w= X-Received: by 2002:a02:6a2f:: with SMTP id l47-v6mr11677696jac.71.1534072887736; Sun, 12 Aug 2018 04:21:27 -0700 (PDT) MIME-Version: 1.0 From: blubee blubeeme Date: Sun, 12 Aug 2018 19:21:16 +0800 Message-ID: Subject: FreeBSD elf_machine_id To: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 11:21:29 -0000 What's the elf_machine_id for FreeBSD amd64 systems? How can I find this info? Best, Owen From owner-freebsd-current@freebsd.org Sun Aug 12 11:38:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0057E106D34C for ; Sun, 12 Aug 2018 11:38:42 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr1-x42c.google.com (mail-wr1-x42c.google.com [IPv6:2a00:1450:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 698D083D63 for ; Sun, 12 Aug 2018 11:38:42 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr1-x42c.google.com with SMTP id f12-v6so11847660wrv.12 for ; Sun, 12 Aug 2018 04:38:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=PK0qjQ1TRQIpSV/+E+PmjRv7fAhZe9L0REHCbubry5U=; b=oGG3rrlK3Ab1rK1jzxRy90tX5kgtrQv/I54YUbkSM7u6NtOqOSkRe17E1jA8ZB9kqT GS4lE7zgN30vSQ2ukj2PAqeDP9+1Xymz4dWO2jSMt7mLc9qAsbLfgLLaGs3CJSHIhAJh rbQT1F6R2OmAjdhX/eBDZ3eC5LZzGT3h3e0A/xZ2rO7bi77NqTJNcUO50upIhFWBOWbE 2W87EpQKEhRYtXqZQQqKUkvXP0RvkkDmhf7xdclyXIkAqu5CEZHOmPOERYI2NJxF6pf/ OfDW1Rzd4pEwSQ2eDfu7h3AnYBDd240+WK/NIQm8bNBvxFaar9Hq/HYUjpHz4rzF3PCp gwPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=PK0qjQ1TRQIpSV/+E+PmjRv7fAhZe9L0REHCbubry5U=; b=OSg8N8EQjVep+vD/GHW8C0CShrU+KTITLLPxsEq4/BouBharG8wkThH16u03HhDY09 DNvX51QsB6qCgj6/Xyq3OHzIbZjVk+GJeDDuIv7dD/w9QXFA7lWZJFlZMky6ewibCddy 5ViDg/HJxXZHcJAY0o8Ieaq0A7QAyKBhjQG9zPpOypm1z2HGE9dQ/ctgqwLH6tbzZf1g huXTmJ2khFd6QVvqhR1FxBfuc3GyfUk/TBJwzCQZY13Rjw80VGzRTLlhZCxNtyLb7QjQ BKZO0BOfxuXOMp66RJXMQTMsdVLdgL0vj3emV6jQEMIVVmmbjjkMYE6jP+zij2W2zA/1 enag== X-Gm-Message-State: AOUpUlHR8KPtl0K0nUXRQzzeUCnXc90csfXDQuIovlNDB46IbSnG+zc2 /zWEUyFUPjRjxI5eYA37/OcTk7uB X-Google-Smtp-Source: AA+uWPz5jdTb2jcOvVbHjMF4rGdTAEcaU712ggBpHEImf09i92M0MULQr27ZX5hdU9mYjvs/D/s+ag== X-Received: by 2002:adf:9aa3:: with SMTP id a32-v6mr8164596wrc.75.1534073921401; Sun, 12 Aug 2018 04:38:41 -0700 (PDT) Received: from ernst.home (pD9E23F86.dip0.t-ipconnect.de. [217.226.63.134]) by smtp.gmail.com with ESMTPSA id p13-v6sm10991709wrj.20.2018.08.12.04.38.39 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 12 Aug 2018 04:38:40 -0700 (PDT) Date: Sun, 12 Aug 2018 13:38:39 +0200 From: Gary Jennejohn To: blubee blubeeme Cc: FreeBSD current Subject: Re: FreeBSD elf_machine_id Message-ID: <20180812133839.749cea08@ernst.home> In-Reply-To: References: Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 11:38:43 -0000 On Sun, 12 Aug 2018 19:21:16 +0800 blubee blubeeme wrote: > What's the elf_machine_id for FreeBSD amd64 systems? > > How can I find this info? > elfdump -a /bin/ls | grep machine -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Aug 12 11:40:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C17DE106D424 for ; Sun, 12 Aug 2018 11:40:31 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3D72683E54 for ; Sun, 12 Aug 2018 11:40:31 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id r24-v6so5240394wmh.0 for ; Sun, 12 Aug 2018 04:40:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=foJt1OSsgkbIOocJaQVP23Gu/AlwK9No5WJWlZSvs1M=; b=SZrFgPvwBbxBhtzMxtfFoNz3l8YAAQ2kEQWtACknGr11qhnnLSt/BwJ4zwwDGDbDkO yrtcGoU5mTxrQcRqWTXgbus8hgicH/DuITVJxiJKl7KhfBLv5ne4YVIRN/wBDbMtl90N upKG7Z0w8FcqStJxmX+HCu95WuqtYUw8wdu1ZCI1ylVmPG62bqJABgmqZBhmzFvDTc9D 0bDm8JCS+/50vgwPaYUN3TXSUSkxi01eX3yGRw1Pasb6E/NbXVVqvis0DIObU93PdWwL sPAI8uizcGDRyA4IFE2CzYCV9K6QeijTbExdyIY2fPYChPHCI9HX7ZsisPjaCODKLQWR MZuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=foJt1OSsgkbIOocJaQVP23Gu/AlwK9No5WJWlZSvs1M=; b=o6Ev5ksK4YHhRPWt1eO0lwN+Z0dASR//LBZ12Kod8+sBP+m3BKz8ysG9IGiL2GpRoe q+itUETjGGmrBiXdG6/nxjngH8w9UsB9352CKB3R2zL3CGBcPs88zaXCYnKwjSFDvtOS +cwSmDJ2LfBIHY8FTdR3i5mIzUKQNxbyLbAmorNbQ88QXX3cmC8neCWuFaTGCWwT/qQx 4OezmAuGJLt7GUg2+TBFtFbYpNc4V3Z3PM662BKd3FqRyQoYmth5zgzgpsMTph826ovI rCHE4+eGnxEW5MsPur+KFQWtN6U9QnL+e5LrId4KoXL6aI2+yxdT0GWQmqD7ZHvTaUGF fo0A== X-Gm-Message-State: AOUpUlGWyPn0KpwTQvMPGPPQnyoOUwB3joHtG3bTBj2a1soh/PWdyijL ySInNzwmCtqmKjCQzPD20cI= X-Google-Smtp-Source: AA+uWPybAdzNlWsu8yE+I3sxNyuwKWa6OnookdOfremreghbcdpqojpnxmk4BnIqrnoV3xlOBoiaAA== X-Received: by 2002:a1c:c14:: with SMTP id 20-v6mr6054709wmm.117.1534074030188; Sun, 12 Aug 2018 04:40:30 -0700 (PDT) Received: from ernst.home (pD9E23F86.dip0.t-ipconnect.de. [217.226.63.134]) by smtp.gmail.com with ESMTPSA id 198-v6sm13651112wmm.0.2018.08.12.04.40.29 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 12 Aug 2018 04:40:29 -0700 (PDT) Date: Sun, 12 Aug 2018 13:40:28 +0200 From: Gary Jennejohn To: blubee blubeeme Cc: FreeBSD current Subject: Re: FreeBSD elf_machine_id Message-ID: <20180812134028.179b25c3@ernst.home> In-Reply-To: <20180812133839.749cea08@ernst.home> References: <20180812133839.749cea08@ernst.home> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 11:40:31 -0000 On Sun, 12 Aug 2018 13:38:39 +0200 Gary Jennejohn wrote: > On Sun, 12 Aug 2018 19:21:16 +0800 > blubee blubeeme wrote: > > > What's the elf_machine_id for FreeBSD amd64 systems? > > > > How can I find this info? > > > > elfdump -a /bin/ls | grep machine > Oops! In case you don't any AMD64 machines handy: e_machine: EM_X86_64 -- Gary Jennejohn From owner-freebsd-current@freebsd.org Sun Aug 12 11:43:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A349106D6EC for ; Sun, 12 Aug 2018 11:43:25 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D9CB08424A for ; Sun, 12 Aug 2018 11:43:24 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 5EB4639986; Sun, 12 Aug 2018 13:43:21 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_E6584D6E-2B3A-4C67-AC90-AF7B53AACE3E"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: FreeBSD elf_machine_id Date: Sun, 12 Aug 2018 13:43:17 +0200 In-Reply-To: Cc: FreeBSD current To: blubee blubeeme References: X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 11:43:25 -0000 --Apple-Mail=_E6584D6E-2B3A-4C67-AC90-AF7B53AACE3E Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 12 Aug 2018, at 13:21, blubee blubeeme wrote: > > What's the elf_machine_id for FreeBSD amd64 systems? > > How can I find this info? There isn't any FreeBSD-specific machine ID, just a machine ID for x86-64 (aka amd64) in general: $ grep x86-64 /usr/include/sys/elf_common.h #define EM_X86_64 62 /* Advanced Micro Devices x86-64 */ #define EM_AMD64 EM_X86_64 /* Advanced Micro Devices x86-64 (compat) */ -Dimitry --Apple-Mail=_E6584D6E-2B3A-4C67-AC90-AF7B53AACE3E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCW3AdVQAKCRCwXqMKLiCW o0snAKCOTQy6vjpPmBfkT10W9Q+Ejzl5fACbBUIS/uo/hObnaK69JlArbi/PBj8= =84pA -----END PGP SIGNATURE----- --Apple-Mail=_E6584D6E-2B3A-4C67-AC90-AF7B53AACE3E-- From owner-freebsd-current@freebsd.org Sun Aug 12 12:26:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A11FC106EFC6 for ; Sun, 12 Aug 2018 12:26:00 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660082.outbound.protection.outlook.com [40.107.66.82]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F44585B9C for ; Sun, 12 Aug 2018 12:25:59 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB1210.CANPRD01.PROD.OUTLOOK.COM (52.132.43.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1017.15; Sun, 12 Aug 2018 12:25:58 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127%2]) with mapi id 15.20.1017.022; Sun, 12 Aug 2018 12:25:58 +0000 From: Rick Macklem To: Konstantin Belousov CC: "freebsd-current@FreeBSD.org" , "peter@holm.cc" Subject: Re: ffs_truncate3 panics Thread-Topic: ffs_truncate3 panics Thread-Index: AQHULkj8zfSrFB+Dkkqu0NmeGvZbQKS0RKaAgAGEoXWAAKUlgIAANVYCgACitwCAAJvZIoABYIyAgAEw+G+AAA/YgIABir2A Date: Sun, 12 Aug 2018 12:25:58 +0000 Message-ID: References: <20180807131445.GC1884@kib.kiev.ua> <20180808221647.GH1884@kib.kiev.ua> <20180809111004.GK1884@kib.kiev.ua> <20180810172941.GA2113@kib.kiev.ua> , <20180811123755.GD2113@kib.kiev.ua> In-Reply-To: <20180811123755.GD2113@kib.kiev.ua> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1210; 6:haUFWb3mmgDGH2mSr9HpzCVgsYcqYyYKDVNR4mOMgpXg5rvtb9DOc2eAq5OqkwTowG6okrGVrQsYVau8aB4vILA4hA9tg1TYIVI4wQJ7J/FuW4CcWPzU701jZ2sKEIOOHgjg+fb2knPf9K+qefVSRXKyq2MhFruMPUGBLOXqNvWHKFX9550KYHlyMTW74xhyPRqJVvZWZFke1oJVnlfl9Z22fpd8UJ6VL+eZwe3dkARkycy7o7NShJZYQZDpFk41f/obnJSnLnipTKze/bFlpC0K97ETuISDg1MXwixu1VCxpgK+oryRL4m+2ZEDabzSjh2Ivj7/INO32dr7wUHrjjxi5l/PKIgh8cVggcuzYdo1g97QB8uW80dcaeMQmDnZzBIHMW0Hc0S0JvcLHx/PWo/dyXDJVDRsN6AUf+JUc8NxRQEjPSNiyeOZKzVaBx/kZmAnOwVPjwC2SQ212q41SA==; 5:MhBf7zv369QxmSYMok/b92zVustg3qiQFk/n/FuwkFE5UtIxByRSBHadKistc5+00DVP25a8rDnywTawsAGS/Jro8ySsBInPCeSbexFtbA2hgIGZvum/dqhKh21doSGYWq5jxmgHK9h8YfiSNeuOZqK/8tK9iylRqo7qtbKtVms=; 7:n1AzGoOiugJL2xnWoRm5DBPYsD2SvXGUoNe2olJ/fTE7N5rfne3bj8mbqw+ATuqJAuTbKKgAiTCX+QHpFQjWAsz7yocqNyNCipfgq+eQdm/ahfaAxsMw39GyQVQZj1dwt3E/lals6sYYlPDA6wHBzvqGrLTOBhgIalY/vURm97EImJqieSm/3HCH693MQuNeWAjkiBx5NLYscICY5va7ZFC5EGDBQl34fD8NYwDARvUuG2Q2dTgmozHHDbAYe9cq x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 7e8e4980-0d24-42eb-576d-08d6004ec241 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1210; x-ms-traffictypediagnostic: YTOPR0101MB1210: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(3231311)(944501410)(52105095)(93006095)(93001095)(149027)(150027)(6041310)(20161123564045)(20161123558120)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB1210; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1210; x-forefront-prvs: 0762FFD075 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(346002)(366004)(136003)(39860400002)(396003)(189003)(199004)(106356001)(105586002)(478600001)(25786009)(6506007)(486006)(316002)(786003)(476003)(74316002)(305945005)(33656002)(5250100002)(11346002)(446003)(14454004)(26005)(99286004)(7116003)(5660300001)(74482002)(2900100001)(53936002)(54906003)(186003)(229853002)(8936002)(9686003)(55016002)(76176011)(6436002)(1411001)(93886005)(6916009)(102836004)(7696005)(6246003)(86362001)(4326008)(39060400002)(14444005)(68736007)(97736004)(8676002)(81166006)(256004)(81156014)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1210; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: cfJHVCbSktdHZiBGTskQcK/HaqNodMsPmafnNJlecmJPTdgOUfNLgTHwBcWcuA2daTm4yg0728J1DyQuhoE/SSvqIZUN9lfpp/aoxmu859R6R7gNnRWkwI4BH86OVEMt8ZcozFKQ7ky9UkjpD4FRa5sK2Z4hBKoaXs7vEmg4TnbbDRHEN1rJaxl6NlPaYoxDnH4WbKdOmZylCDnycp0r6V4YSpwMz/bh8KFQHK18+NCiVj32PJ7opaJv9KSdlmiseqTIF8m+AgTqz6WiBlnbXcKAiqusrvltfl+cnJLbwBpATAlbAeVRHCjNbIc0CA1h2EiYQGmvIfV6AdS9PFRrmXbLpQoCZY7k6mZ7EolxaCY= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 7e8e4980-0d24-42eb-576d-08d6004ec241 X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Aug 2018 12:25:58.5077 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1210 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 12:26:00 -0000 Konstantin Belousov wrote: [stuff snipped] >Problem with this buffer is that BX_ALTDATA bit is not set. >This is the reason why vinvalbuf(V_ALT) skips it. [more stuff snipped] >The vnode is exclusively locked. Other thread must not be able to >instantiate a buffer under us. That's what I thought, but I wasn't sure that UFS never did anything to the= buffers without the vnode lock. [more stuff snipped] >This is the patch that I posted long time ago. It is obviously related >to missed BX_ALTDATA. Can you add this patch to your kernel ? > >diff --git a/sys/ufs/ffs/ffs_balloc.c b/sys/ufs/ffs/ffs_balloc.c >index 552c295753d..6d89a229ea7 100644 >--- a/sys/ufs/ffs/ffs_balloc.c >+++ b/sys/ufs/ffs/ffs_balloc.c >@@ -682,8 +682,16 @@ ffs_balloc_ufs2(struct vnode *vp, off_t startoffset, = int size, > ffs_blkpref_ufs2(ip, lbn, (int)lbn, > &dp->di_extb[0]), osize, nsize, flags, > cred, &bp); >- if (error) >+ if (error !=3D 0) { >+ /* getblk does truncation, if need= ed */ >+ bp =3D getblk(vp, -1 - lbn, osize,= 0, 0, >+ GB_NOCREAT); >+ if (bp !=3D NULL) { >+ bp->b_xflags |=3D BX_ALTDA= TA; >+ brelse(bp); >+ } > return (error); >+ } > bp->b_xflags |=3D BX_ALTDATA; > if (DOINGSOFTDEP(vp)) > softdep_setup_allocext(ip, lbn, >@@ -699,8 +707,17 @@ ffs_balloc_ufs2(struct vnode *vp, off_t startoffset, = int size, > error =3D ffs_alloc(ip, lbn, > ffs_blkpref_ufs2(ip, lbn, (int)lbn, &dp->di_ext= b[0]), > nsize, flags, cred, &newb); >- if (error) >+ if (error !=3D 0) { >+ bp =3D getblk(vp, -1 - lbn, nsize, 0, 0, >+ GB_NOCREAT); >+ if (bp !=3D NULL) { >+ bp->b_xflags |=3D BX_ALTDATA; >+ bp->b_flags |=3D B_RELBUF | B_INVA= L; >+ bp->b_flags &=3D ~B_ASYNC; >+ brelse(bp); >+ } > return (error); >+ } > bp =3D getblk(vp, -1 - lbn, nsize, 0, 0, gbflags); > bp->b_blkno =3D fsbtodb(fs, newb); > bp->b_xflags |=3D BX_ALTDATA; I don't think this patch helped. I still get printf()s with b_xflags =3D=3D= clear with it applied. I haven't gotten one that would cause the panic yet, but it didn't make the BX_ALTDATA flag get set. However, I have narrowed down how the ones that cause a panic() occur. Turns out I was wrong when I said di_size =3D=3D 0 for all these files. They don't store any data, but if an application does a truncate(2) with le= ngth > 0, the di_size does get set non-zero. It is when one of these files hits the ffs_truncate() with the extended att= ribute buffer on it, that the panic() happens. (Most of them have di_size =3D=3D 0 and return from the function in the cod= e block that starts with "if (ip->I_size =3D=3D length)" at around line#299, befor= e the panic() check.) rick From owner-freebsd-current@freebsd.org Sun Aug 12 13:38:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB47010709B0 for ; Sun, 12 Aug 2018 13:38:05 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 50B8488AA5 for ; Sun, 12 Aug 2018 13:38:05 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1534081075; bh=mpDkQicmpRDJbOo2BJOy6Fh+DMQwnqECr6FHNLp /+7c=; b=bnuGg+aHUWsVn/HFBBzQm/iv4ogvaZWN1uRrZ0zNC6RZPkCIqaNe26z waosxiSU4KnPbZBdy7hNwPyD6Hk+YNtOybpYbpnoZ2tgzbvRO5zli0+YtEcFjU+Y yhBT5Zr/xwV+3R7rA0K5K6cf0tzkxLVhlFd6S/QjikVX14XBCoY0= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id ADAA53B278; Sun, 12 Aug 2018 09:37:55 -0400 (EDT) To: FreeBSD Current , Matthew Macy From: Michael Butler Subject: kernel build failure Openpgp: preference=signencrypt Message-ID: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> Date: Sun, 12 Aug 2018 09:37:54 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 13:38:05 -0000 Is anyone else seeing this when building a new kernel with ZFS compiled in? Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel --- kernel --- linking kernel ld: error: undefined symbol: dbuf_stats_init >>> referenced by dbuf.c >>> dbuf.o:(dbuf_init) ld: error: undefined symbol: dbuf_stats_destroy >>> referenced by dbuf.c >>> dbuf.o:(dbuf_fini) *** [kernel] Error code 1 imb From owner-freebsd-current@freebsd.org Sun Aug 12 13:59:47 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A58E10711D8 for ; Sun, 12 Aug 2018 13:59:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x232.google.com (mail-it0-x232.google.com [IPv6:2607:f8b0:4001:c0b::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C34E89584; Sun, 12 Aug 2018 13:59:47 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x232.google.com with SMTP id d9-v6so8959966itf.2; Sun, 12 Aug 2018 06:59:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Xd+500u7mO3ZP6Gt67nX/xEFtNUFT1kvs/xrF4JN1Xw=; b=nWFppkSHAk25mxHrA22DczvmRtODBRUuKzFohWKQI7u6/k80fmOOvjEM6GsPB502CA BYFRd2jPreDgSiE8pOYaEveaGz2xT1Oxl0oK4YOqAR9JXgApRTc3Pd6LEdGvzAvDUoIM MRq5pKr6Nab2hwcoBE1myX1M///z4HtZOzuGq8SUPCDZgkqQtOpH9TElW1Crkt4ZdeRY /YAmtBO0ERxl1auM7DdaZUJY1UBJNXQC/ZABHnsJltibrHN6NN2kk1O/HHwXHLvZpCwE k850iXeb34uA358lO1b1O7MqvUvxWhhxkuztBH/KI0GaNtT53UnzwZ2H0Nqa+mYAmljf HEIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Xd+500u7mO3ZP6Gt67nX/xEFtNUFT1kvs/xrF4JN1Xw=; b=hCvtGJrlWhpAsxMbqpzKcaVV4Q0Y0imBIr0HD3UPA0Qmd7CfrLBwuNDAHqMSkTDqPR l4eZrYsR84EXrt8sp/YnFvQP2iex85k0po7EDvcZeEPrEdSTXAGjwrD6XHKu7G3bivya iYuy8PMVNjKepUOZv+8vbKifyGCVerJOwbtTSFxfoEqYpxWnyugZaBA14heUfDpjttv/ 5TN88B/oiQ6EzG/OpIGtaHpV8eCxW5F1rPukCADQ1TRxc6ryWXw/LCtSGgjMqyRHQu6c vWYa5Qsvq5psPCmLL4HerD94+0jd0R6i0cFx0Hipo+vty2yuQazjJt6rg6xV+t0rrAfT gEJA== X-Gm-Message-State: AOUpUlEjQgjNtkSvlwiLp05hV9rRpuFN+q6z4DnJI5+6GbEOHFdE9d8W ctZ9yAsTn/1e2cZCFv9K1A7qZE+jd/lw7dP/xIo8IQ== X-Google-Smtp-Source: AA+uWPxvUBwrtoGbwtxQuIwIKm6YE6UbSA18PfSTdm3NrlgPgf6EVtOQSyDzP/MsfIagS3y77I7igQzs9pcH4BC6o1c= X-Received: by 2002:a02:6a2f:: with SMTP id l47-v6mr12054794jac.71.1534082386428; Sun, 12 Aug 2018 06:59:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: blubee blubeeme Date: Sun, 12 Aug 2018 21:59:35 +0800 Message-ID: Subject: Re: FreeBSD elf_machine_id To: Dimitry Andric Cc: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 13:59:47 -0000 On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: > On 12 Aug 2018, at 13:21, blubee blubeeme wrote: > > > > What's the elf_machine_id for FreeBSD amd64 systems? > > > > How can I find this info? > > There isn't any FreeBSD-specific machine ID, just a machine ID for > x86-64 (aka amd64) in general: > > $ grep x86-64 /usr/include/sys/elf_common.h > #define EM_X86_64 62 /* Advanced Micro Devices x86-64 */ > #define EM_AMD64 EM_X86_64 /* Advanced Micro Devices x86-64 > (compat) */ > > -Dimitry > > Thank you for the clarification. I think in this case I was looking for 62. Best, Owen From owner-freebsd-current@freebsd.org Sun Aug 12 14:02:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98162107141C for ; Sun, 12 Aug 2018 14:02:56 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5BE7B899AB; Sun, 12 Aug 2018 14:02:53 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id d10-v6so8934501itj.5; Sun, 12 Aug 2018 07:02:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xwjZnn90pQI9Eqci2U13Klp+HHFOVIBR7x+t1DRSccA=; b=P3IPSf/W32Nm3UU7nrHMcsmI75sPDe+i9pCAzljF5vkMOuPEdpyWEKkDqC4MxfIP7p guf22/8D+DUJ7Fa8+zO87eySzLJgcc3b/WsrpzXrROKy/yMBZzvVkSUuP7nLCA1Rmm5R 9UhwaiCW+RxmgHeAp3Emnz8oPQ+n5x8uA7GXqjWKT27uTHLigfGrtqglwLeN3m4I2+4E JQZcek5q8NgnfjlgweT0EKoFLhWhDa0bSJrnGgYEok1LbUgSRX8uj2YOkgYOFTeNOu1k Lx5NWYGEZaZ0LsWiY4Ym8EJ+pYoN0tgrz8r69zBEBFSf/mV0Ef0iJHSyQNyLuceugOj5 d7fA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xwjZnn90pQI9Eqci2U13Klp+HHFOVIBR7x+t1DRSccA=; b=n9k/aRPkH6B2mSKcGfSmgfEfOSDjJ5l8JErwhcSqmNWW4+/CN8gXXO/AfpatDtRdHJ JKJq4uAKGjVxXCVuCuTRg+lheoaZ9nESznPXZ8uqKjelRqBxvgEZbRa/n5paxOVvAu7K vOvfaGJba/us8Dsvkz0Jd9UITOGFY+SRsDBx+MI+rKE6jAv++1jKGPEVLhxPEhUfdPvY DHt3X8qd3bXfp0a/zvb+PBOPtOZPUtSgO+62dN+3V7eTUjEYCgv2vmP8InKY8r+rZpmx 5uVBG597FxpkD92CqlVoMfVqxdytzpUYWrQj4enAz1ka40w68zszSySYv+60kJszBmF8 Kwiw== X-Gm-Message-State: AOUpUlG1whlx36KiOvev+lA/K4VTfTdpEsLr8jGrGopupgD3DB/kDObK pP7xuxn3t5t47bp9cS8Z49oIpr1Vz4snVn9a7JnTFw== X-Google-Smtp-Source: AA+uWPxEdUXuXt1voYfeXBPRJ5XW0l1DNQ6w02nWNFdXrCRgq0ZgFIYYXW8hlG/ueQnrQM7NNfU9VoRJbVmPbNZlVHE= X-Received: by 2002:a02:6a2f:: with SMTP id l47-v6mr12066945jac.71.1534082572215; Sun, 12 Aug 2018 07:02:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: blubee blubeeme Date: Sun, 12 Aug 2018 22:02:41 +0800 Message-ID: Subject: Re: FreeBSD elf_machine_id To: Dimitry Andric Cc: FreeBSD current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 14:02:56 -0000 On Sun, Aug 12, 2018 at 9:59 PM blubee blubeeme wrote: > > > On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: > >> On 12 Aug 2018, at 13:21, blubee blubeeme wrote: >> > >> > What's the elf_machine_id for FreeBSD amd64 systems? >> > >> > How can I find this info? >> >> There isn't any FreeBSD-specific machine ID, just a machine ID for >> x86-64 (aka amd64) in general: >> >> $ grep x86-64 /usr/include/sys/elf_common.h >> #define EM_X86_64 62 /* Advanced Micro Devices x86-64 */ >> #define EM_AMD64 EM_X86_64 /* Advanced Micro Devices x86-64 >> (compat) */ >> >> -Dimitry >> >> Thank you for the clarification. > > I think in this case I was looking for 62. > > Best, > Owen > Actually I had another quick question along these lines. if x86_64 is already defined should I bother changing those to amd64 or just use x86_64 and make FreeBSD modifications where Linux specifics are defined? Best, Owen From owner-freebsd-current@freebsd.org Sun Aug 12 14:51:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5ABF1072F93 for ; Sun, 12 Aug 2018 14:51:44 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3269F8B745 for ; Sun, 12 Aug 2018 14:51:43 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w7CEpR1i031938 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 12 Aug 2018 16:51:27 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w7CEpR97031935; Sun, 12 Aug 2018 16:51:27 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Sun, 12 Aug 2018 16:51:27 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Michael Butler cc: FreeBSD Current , Matthew Macy Subject: Re: kernel build failure In-Reply-To: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> Message-ID: References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 14:51:44 -0000 On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > --- kernel --- > linking kernel > ld: error: undefined symbol: dbuf_stats_init > >>> referenced by dbuf.c > >>> dbuf.o:(dbuf_init) > > ld: error: undefined symbol: dbuf_stats_destroy > >>> referenced by dbuf.c > >>> dbuf.o:(dbuf_fini) > *** [kernel] Error code 1 I was just about to create a thread of my own. I suspect r337670 didn't add everything cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See lines 652 and 697. Meanwhile, I'll attempt to revert to r337669. -- Trond. From owner-freebsd-current@freebsd.org Sun Aug 12 15:51:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AA351074B13 for ; Sun, 12 Aug 2018 15:51:12 +0000 (UTC) (envelope-from tuexen@FreeBSD.org) Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E95918DD10 for ; Sun, 12 Aug 2018 15:51:11 +0000 (UTC) (envelope-from tuexen@FreeBSD.org) Received: from [172.18.127.168] (unknown [46.183.103.8]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 1397372106C13 for ; Sun, 12 Aug 2018 17:51:09 +0200 (CEST) From: Michael Tuexen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Problem with lastest version of indent Message-Id: <608CC109-3625-466D-8698-D945F7249806@FreeBSD.org> Date: Sun, 12 Aug 2018 17:51:08 +0200 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.3445.9.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 15:51:12 -0000 Dear all, the up-to-date indent translates a line like bla._blub =3D 1; into a line like bla._ blub =3D 1; (insert whitespace after _) which breaks C code... Older versions didn't = do that Is this change intended? If yes, is there a command line option to turn = it off? Best regards Michael= From owner-freebsd-current@freebsd.org Sun Aug 12 16:09:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ED68010754D9 for ; Sun, 12 Aug 2018 16:09:53 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69F5E8E5D6 for ; Sun, 12 Aug 2018 16:09:52 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: by mail-ed1-x52f.google.com with SMTP id r4-v6so7050640edp.9 for ; Sun, 12 Aug 2018 09:09:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=eybcIkiIRoFkRIbwcuaa+JIBzdBiPUALr57A7xl1cWk=; b=U9ykRfCBLn7OB/b/9K5DOrg+bDPs1lJ03GnYVVKFYrd3nuQRUk2NNDDACxMfI4190v cPu3vz2A27NAbr8udUuygzo4LLaTJmtSbrZqkOP1L1stJbx2g1nYlE03Fp+oUrZpoE23 uNIXuDwU6aOYCX4myeDjtoUUHoqGx9CIodAihVMWfQPKtdcDYvT3ul/c39ZD2OrET5De 47aF7DH2bosysZcGzpKPuUcdQIJExf3MeldC0bQ+K1xdrTFJChXjYlPzlDVDTU9qP+7b Ja7hQwhNzkq8p64Xoofa7ILy0kEahEOhlsBy4zp/Yb7Igkdu4I1EXXo+LND73K1x6NAT YQ5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=eybcIkiIRoFkRIbwcuaa+JIBzdBiPUALr57A7xl1cWk=; b=pFvN8rwU5BAEZDHsUt1iEg+HaEUds0sZ7/VzQsaYO25niR62kmr5vxTtGeG6WAZLBK b4C1VuEHjDFwShuYLrVMpcWJ2e1P7OKo/fd9k3Y3xomVbCtxtm82nphwWFkfjG2eBB+2 EdyZ8pXdbF9L/448B0SGaiG8Tp+qP7UDfcsfA2eVcSQeKscQELN4a9hqBC8BvtS9zJOB 4cUVTolf4v7ZlpCKxziOkby7Z2fb8FuOc2scblWujeR/JuUB0lTGT5tM4+QUIqnRj1Mh 6E1Z23H/aiSYG1bAk+x6F+o+9UJ7eNdA8NBlJe+W4oJi3xz0k+GPZSqmaImCVth05RPd DwMQ== X-Gm-Message-State: AOUpUlH3IERXp8GDV6JKiEkCi1NmzjaWDGvGq2zHMRxc/vASdcX4hrJU hcV0dcOERguOLmjZyLq+JJd70gAXjs8a2g== X-Google-Smtp-Source: AA+uWPyiP/8gnELqJcKn5WninvK3G/DAB+nY3Exko2hZZA1kx1lufsNiev5cqucUAWTsO+IxxIAkXg== X-Received: by 2002:a50:9a02:: with SMTP id o2-v6mr18368650edb.236.1534090191600; Sun, 12 Aug 2018 09:09:51 -0700 (PDT) Received: from mutt-hbsd ([185.125.33.114]) by smtp.gmail.com with ESMTPSA id x13-v6sm23206421edx.17.2018.08.12.09.09.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Aug 2018 09:09:50 -0700 (PDT) Date: Sun, 12 Aug 2018 12:09:02 -0400 From: Shawn Webb To: "Alex V. Petrov" Cc: freebsd-current Subject: Re: zpool scrub. Wtf? Message-ID: <20180812160902.x47qaieqist46a6h@mutt-hbsd> References: <216d0fd3-c833-e01b-cf6f-7b8360bf9905@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7undpbvzwmez5q2w" Content-Disposition: inline In-Reply-To: <216d0fd3-c833-e01b-cf6f-7b8360bf9905@gmail.com> X-Operating-System: FreeBSD mutt-hbsd 12.0-CURRENT FreeBSD 12.0-CURRENT X-PGP-Key: http://pgp.mit.edu/pks/lookup?op=vindex&search=0x6A84658F52456EEE User-Agent: NeoMutt/20180622 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 16:09:54 -0000 --7undpbvzwmez5q2w Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 07, 2018 at 10:50:13PM +0700, Alex V. Petrov wrote: > # zpool status > pool: zroot > state: ONLINE > scan: scrub in progress since Tue Aug 7 21:21:51 2018 > 804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total > 0 repaired, 129,87% done, 929637 days 13:43:01 to go > config: >=20 > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > ada0p4 ONLINE 0 0 0 >=20 > errors: No known data errors >=20 > smart is OK >=20 > FreeBSD 12.0-CURRENT #3 r337364: Mon Aug 6 07:01:42 +07 2018 amd64 I'm seeing the same issue. --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE --7undpbvzwmez5q2w Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEKrq2ve9q9Ia+iT2eaoRlj1JFbu4FAltwW5kACgkQaoRlj1JF bu7uKhAAo66wHv51A0m5v5yqIQlR29OnnQN4NlIKP2ck+qovK9yatbzTMSDiL5bk vuNtM0LX0ojN3NWiQp/+JWwdSwJBfzTqv1esszM1ERg0jw4ilNv3k9l9oX068Z8x 39p0d6bSGRKnRn5DNMQY3R9AjElxe5mkj6nsI2KLyhGSp/Nq5E9me/tfKnMxqr1r K+2SPqS0qA3c7LxjDK1u9O432UwSl2pjVIeLaJ6RMAEXaTVh//qlM//RL1qzRt84 htUe0lbs662tHPnskcohDOEgyUlEdPX9RrI7c08OfOq4TyIb2dyBzD4EC90MMdFD LZEUD9LgRaXj8w0JtnfZLtuPO/F2PJ7vItaHoOdltPTjTfluKbKLVFKTrJq+kQQy DF0YrvhWjTd75y7JNrlsRVWJKS9G+8l5sHvF2y0Pb+jtKFVx8lDSTDtXC5VYdTnY jwFHfcfFPmFik4DC/W12F3MRvo3hPPX50+tKIz2uywJy+UGOTGTud4a0u0Rdn8Ff 7NPtuVVBZbX/jOFQ23KLLMLpLB7tbAGR3SzIYM7sLZYYCLl3tNi49R2URpGXdj8m pnaXeNJEMeNL71E2Y7K/ioSmfgfTbIWQNVK+SMBiN8SjRnmByDcxs/fFF+EvTwh7 etDUX6IVHFMW3vZMveeNwvdlRpLX1FPeyuzoKGJRnoxJ9SctkhA= =3Z1D -----END PGP SIGNATURE----- --7undpbvzwmez5q2w-- From owner-freebsd-current@freebsd.org Sun Aug 12 16:50:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54EC31076112 for ; Sun, 12 Aug 2018 16:50:25 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:146]) (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 D6ED28F96E for ; Sun, 12 Aug 2018 16:50:24 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 298262782D8 for ; Mon, 13 Aug 2018 01:50:20 +0900 (JST) Received: by mail-io0-f178.google.com with SMTP id l7-v6so8345535iok.6 for ; Sun, 12 Aug 2018 09:50:20 -0700 (PDT) X-Gm-Message-State: AOUpUlEnX4G1MF8SoWBp7cTlAhppQezJhkEbefhxt8QhJ9VX8AsCHkCd 2d/BjTfNWbiyVzHFJ/ljMUlmuuDfD9nIKnKlVN0= X-Google-Smtp-Source: AA+uWPweI7WvgrNeW4bcI2zRDnz4YzqslJIs1V+P4iI++cQ+62HlATXPRn7Eb9nRIezFam+lio+4fgJ0yo03/ie4Plo= X-Received: by 2002:a6b:3757:: with SMTP id e84-v6mr12547386ioa.151.1534092618480; Sun, 12 Aug 2018 09:50:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4f:1007:0:0:0:0:0 with HTTP; Sun, 12 Aug 2018 09:50:17 -0700 (PDT) From: Honda Michio Date: Sun, 12 Aug 2018 18:50:17 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: TCP server app performance To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 16:50:25 -0000 Hi, I'm measuring TCP server app performance using my toy web server. It just accept TCP connections and responds back HTTP OK to the clients. It monitors sockets using kqueue, and processes each ready descriptor using a pair of read() and write(). (in more detail, it's https://github.com/micchie/netmap/tree/paste/apps/phttpd) Using 100 persistent TCP connections (the client sends 44 B HTTP GET and the server responds with 151 B of HTTP OK) and a single CPU core, I only get 152K requests per second, which is 2.5x slower than Linux that runs the same app (except that it uses epoll instead of kqueue). I cannot justify this by myself. Does anybody has some intuition about how much FreeBSD would get with such workloads? I tried disabling TCP delayed ack and changing interrupt rates, but no significant difference was observed. I use FreeBSD-CURRENT with GENERIC-NODEBUG (git commit hash: 3015145c3aa4b). For hardware, the server has Xeon Silver 4110 and Intel X540 NIC (activate only a single queue as I test with a single CPU core). All the offloadings are disabled. Cheers, - Michio From owner-freebsd-current@freebsd.org Sun Aug 12 17:42:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72EFD1077EC1 for ; Sun, 12 Aug 2018 17:42:42 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-lf1-x133.google.com (mail-lf1-x133.google.com [IPv6:2a00:1450:4864:20::133]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CE095731A2 for ; Sun, 12 Aug 2018 17:42:41 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-lf1-x133.google.com with SMTP id l16-v6so9701880lfc.13 for ; Sun, 12 Aug 2018 10:42:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=+v9NjBhwLAaJe/EbVJhx9vAYTfxFlbRRAjgjSkyUqxY=; b=qn6p7pGS7xCbeEAudqsgCV0UCDKjw0EXSIqt4uVJa7aVsad2C9ezhgT3IRUlZAPPm7 RIXXASFXco/A4xeOwuCYlP/+DvDeqUWYRTQsnwwp2x0aI4CKgKTbng2hTX5L0d1+JmUU 81XlslJLd6CUVKrFxKtKRGEs69oCZ7KgDB67mzn6YXql6VffeWMkyr0GQ0zm4lh4vb8K vil5LIFW/GJ7Ju4HMgCpjnAQMG8kh7+5XOaxwgBXX/09EzwA5di0QPL6ANGZtXd5ZEX0 MOywHSPZE+It1WTeKimGqgpx8VPbgy3iRIeV4XDzQZfOcipxmAJc8iBVWqmT2Cic4zng L82Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=+v9NjBhwLAaJe/EbVJhx9vAYTfxFlbRRAjgjSkyUqxY=; b=R7RqlSzuE+189QsKjBGXks/yu9WmTQeJfv9KgX5k6mAqe8a3VRkf7megeIztzKWU9J RDSmc/yryRvZaQJJsNfQ7v3xktL6YXjHEYzJfn1FqCMr8kl+nby9S0oaJ6Y+BJ+MwyNV AKZjC1l6JhuszQExydrbDmu35sjhr0CpbBJEO8WBONsyNa/6oIRi5XhRM1k58GgWDuuP ynpyyl+48vcIwq8QM+VIGJhAdB3YkgxzXCT6+72LAJZSl1f6ZCrqbuJlXVUMp4y+NZTk S5xCQ0D3qaxfyWuJgWwLFAYgbXLHttUC5X+sSjridnu2jBseh9goXazbgdtkcgNI9/aj J4TA== X-Gm-Message-State: AOUpUlENsWoTIiD1ZLbuTGVLla7qMQNcGpX8dT3HC3h9j73rB0vkCEHd X7A0Nv2G4uou8hegENybCVSczaHh X-Google-Smtp-Source: AA+uWPwW+nne+LIt/2bUQkkqnym/mFEJCW9UCYCi04FhmbnXZJ+2dBc//6al0XvZSb1MVZZcugt3bA== X-Received: by 2002:a19:ec04:: with SMTP id b4-v6mr9088778lfa.91.1534095759684; Sun, 12 Aug 2018 10:42:39 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id q19-v6sm2679066lje.29.2018.08.12.10.42.38 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 12 Aug 2018 10:42:38 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sun, 12 Aug 2018 20:42:33 +0300 To: Honda Michio Cc: freebsd-current@freebsd.org Subject: Re: TCP server app performance Message-ID: <20180812204233.0fcc4f04@gmail.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 17:42:42 -0000 On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read() and write(). (in more detail, it's > https://github.com/micchie/netmap/tree/paste/apps/phttpd) 1. Call accept() in loop until get error. 2. Use reuseport option for load balance. From owner-freebsd-current@freebsd.org Sun Aug 12 17:50:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A8D4810780F8 for ; Sun, 12 Aug 2018 17:50:53 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2381B734EE for ; Sun, 12 Aug 2018 17:50:53 +0000 (UTC) (envelope-from rozhuk.im@gmail.com) Received: by mail-ed1-x533.google.com with SMTP id r4-v6so7121361edp.9 for ; Sun, 12 Aug 2018 10:50:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=Vo25WlJ30zfmGh7gX4QGL4Q3cd4XdNfdvUX4nIMgeRQ=; b=tkmdhWdrUfkTMR+LB1B3icZ32VPA0Mc1vz7gQfR2v1nm2RRO0qq0fZJJCg0wHsHmei oJTA0V5PY3x2kWPQx0l3rIg48YU9hlQiEZwA2MB2nDl1IRyV1N3Iu8XvwJsaSGjaQpDC OyghP4bWKNg4NLNqsrH3m74hN++G2WMlDHbnM5MamrXEf37EzYnHaqhn8VLDPi/dUurx oELJlJ3jCYwnndk+5G8PkbqSPhDE/+OAhSgcx/oMNU0/j6lve07CujuP5GLEG7oS51nQ JWW/5GPEvjeaSNv8NtAZA8+Htw6INujH+sL2f/tnlyWBe17vDHSX/LE858J+M3wwHU22 BXRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Vo25WlJ30zfmGh7gX4QGL4Q3cd4XdNfdvUX4nIMgeRQ=; b=okgUjveOHfx4ukbn9qdAKqI2WDL03RsFKO3qrRka0Td4y64VuuXPO1rJcTkJYp2+0W ezQNuppImHdlHUtipqNhpcVP9LHHTmm0EIqJ3nKBqxjsYLjlR9H5GWL5eQWSIYQqWbJM AJj4YmrXSX9xVP27VK+xkAfTp2TUZIKVwug7Q1ACIiKKWvg+4PfWAeIg6hb8JOHosfiH jKT0+0wkDrd6WZGULWgu8dd2oKluvMxa3wvN6pctmpbvEW0AVsMliiwW/KTIxSCHdAtP m/hf456u0oKFXtJ/6fXtzl9hNtbOQx5cllYZB8jjYTPtd/9xdCSddbu2dOcnaaDJrpQm xABA== X-Gm-Message-State: AOUpUlGDow36jWvzHoiuImxnR5J/a4wr+SaRz3rU4WdLlpr1J6wpdWpI gFTzzW06JXgfXon2useZ0Aw+KUes X-Google-Smtp-Source: AA+uWPwXKEC6jzR7rKJ5IxxnjATU/7zMeYfkFVT3sUzVC9bvHItNjrJXYZkE0BahYgiFUcAvlp1jPA== X-Received: by 2002:a50:e885:: with SMTP id f5-v6mr18889211edn.39.1534096252059; Sun, 12 Aug 2018 10:50:52 -0700 (PDT) Received: from localhost ([2001:470:1f15:3d8:7285:c2ff:fe37:5722]) by smtp.gmail.com with ESMTPSA id a8-v6sm15519418eda.27.2018.08.12.10.50.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sun, 12 Aug 2018 10:50:51 -0700 (PDT) From: Rozhuk Ivan X-Google-Original-From: Rozhuk Ivan Date: Sun, 12 Aug 2018 20:50:49 +0300 To: Honda Michio Cc: freebsd-current@freebsd.org Subject: Re: TCP server app performance Message-ID: <20180812205049.097f806f@gmail.com> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 17:50:53 -0000 On Sun, 12 Aug 2018 18:50:17 +0200 Honda Michio wrote: > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the > clients. It monitors sockets using kqueue, and processes each ready > descriptor using a pair of read() and write(). (in more detail, it's > https://github.com/micchie/netmap/tree/paste/apps/phttpd) > PS: 2. SO_REUSEPORT_LB From owner-freebsd-current@freebsd.org Sun Aug 12 17:54:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45F9010784F1 for ; Sun, 12 Aug 2018 17:54:54 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D107F73AAA for ; Sun, 12 Aug 2018 17:54:53 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id ouY0fWZIS5HxqouYYf3daP; Sun, 12 Aug 2018 11:54:29 -0600 X-Authority-Analysis: v=2.3 cv=BMcHU2YG c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=dapMudl6Dx4A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=fIo_VA3yx5p4pKlKQl0A:9 a=nVQWsmEAlx1SqZgH:21 a=bZJs49aFhF741wrA:21 a=CjuIK1q_8ugA:10 a=LazV5FRf0DQA:10 a=kr_CPwnYwPbC5r0VVngA:9 a=N8gA6gZTWyg3rYqS:21 a=HJrHeyKbWGyKFEPl:21 a=p52p5dNK7hR_jHsw:21 a=_W_S_7VecoQA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from [25.170.83.228] (S0106002401cb186f.gv.shawcable.net [70.67.125.17]) by spqr.komquats.com (Postfix) with ESMTPSA id 79E1F96D; Sun, 12 Aug 2018 10:53:24 -0700 (PDT) MIME-Version: 1.0 From: Cy Schubert Subject: RE: zpool scrub. Wtf? Date: Sun, 12 Aug 2018 10:53:03 -0700 To: Shawn Webb , "Alex V. Petrov" CC: freebsd-current Message-Id: <20180812175324.79E1F96D@spqr.komquats.com> X-CMAE-Envelope: MS4wfJA8RuLngDYpWd7fyz02XWUs6hwaRrm7lTudnVmY8ZFEubCq/wiiiedZTQwcIaUqsMcGkR0VnrfwhQNVZQnc8wgAKYZVRQlLe37UgEBAnCOt7TYCabiQ 3+GhH0JKjuxN2BKIwQ2amZV+uL0/mHjj2NtvIhFCpM5T4LDx7VE7G2bqVkCZDeXmZM8+/GZm38gVGkmuXLFk25IBEhx6hifKkIWvOrm0SGMiEybu7A0bAGmX eBTkjBDs+R/o2hf3wKRmA6kSDzBISagrUeuz3AZDGJo= Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 17:54:54 -0000 I haven't looked at it closely but from what I saw it was counting scan rea= ds and issued reads. It may be a simple matter of dividing by 2. --- Sent using a tiny phone keyboard. Apologies for any typos and autocorrect. Also, this old phone only supports top post. Apologies. Cy Schubert or The need of the many outweighs the greed of the few. --- -----Original Message----- From: Shawn Webb Sent: 12/08/2018 09:12 To: Alex V. Petrov Cc: freebsd-current Subject: Re: zpool scrub. Wtf? On Tue, Aug 07, 2018 at 10:50:13PM +0700, Alex V. Petrov wrote: > # zpool status > pool: zroot > state: ONLINE > scan: scrub in progress since Tue Aug 7 21:21:51 2018 > 804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total > 0 repaired, 129,87% done, 929637 days 13:43:01 to go > config: >=20 > NAME STATE READ WRITE CKSUM > zroot ONLINE 0 0 0 > ada0p4 ONLINE 0 0 0 >=20 > errors: No known data errors >=20 > smart is OK >=20 > FreeBSD 12.0-CURRENT #3 r337364: Mon Aug 6 07:01:42 +07 2018 amd64 I'm seeing the same issue. --=20 Shawn Webb Cofounder and Security Engineer HardenedBSD Tor-ified Signal: +1 443-546-8752 Tor+XMPP+OTR: lattera@is.a.hacker.sx GPG Key ID: 0x6A84658F52456EEE GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89 3D9E 6A84 658F 5245 6EEE From owner-freebsd-current@freebsd.org Sun Aug 12 19:32:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A7BD8107A3D2 for ; Sun, 12 Aug 2018 19:32:39 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:146]) (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 36EE5765DC for ; Sun, 12 Aug 2018 19:32:39 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from n-1059.office.hd (pD9F0CC73.dip0.t-ipconnect.de [217.240.204.115]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 28EA2278433; Mon, 13 Aug 2018 04:32:33 +0900 (JST) Subject: Re: TCP server app performance To: Rozhuk Ivan Cc: freebsd-current@freebsd.org References: <20180812205049.097f806f@gmail.com> From: Michio Honda Message-ID: Date: Sun, 12 Aug 2018 21:32:28 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180812205049.097f806f@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 19:32:39 -0000 Hi Rozhuk, I only use a single CPU core and thread, so SO_REUSEPORT_LB has no effect. Also, I already accept() in loop until getting error, but this is not a point as I use persistent TCP connections... Cheers, - Michio On 08/12/2018 07:50 PM, Rozhuk Ivan wrote: > On Sun, 12 Aug 2018 18:50:17 +0200 > Honda Michio wrote: > >> I'm measuring TCP server app performance using my toy web server. >> It just accept TCP connections and responds back HTTP OK to the >> clients. It monitors sockets using kqueue, and processes each ready >> descriptor using a pair of read() and write(). (in more detail, it's >> https://github.com/micchie/netmap/tree/paste/apps/phttpd) >> > > PS: > 2. SO_REUSEPORT_LB > From owner-freebsd-current@freebsd.org Sun Aug 12 19:40:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14F5D107A621 for ; Sun, 12 Aug 2018 19:40:31 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (ms-10.1blu.de [178.254.4.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9E048767FF for ; Sun, 12 Aug 2018 19:40:30 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [80.187.97.119] (helo=localhost.unixarea.de) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1fowDs-0003nr-By for freebsd-current@freebsd.org; Sun, 12 Aug 2018 21:40:20 +0200 Received: from localhost.my.domain (localhost [127.0.0.1]) by localhost.unixarea.de (8.15.2/8.14.9) with ESMTPS id w7CJeJuR005323 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Sun, 12 Aug 2018 21:40:19 +0200 (CEST) (envelope-from guru@unixarea.de) Received: (from guru@localhost) by localhost.my.domain (8.15.2/8.14.9/Submit) id w7CJeJWf005322 for freebsd-current@freebsd.org; Sun, 12 Aug 2018 21:40:19 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: localhost.my.domain: guru set sender to guru@unixarea.de using -f Date: Sun, 12 Aug 2018 21:40:19 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Subject: Re: TCP server app performance Message-ID: <20180812194019.GA5265@c720-r314251> Reply-To: Matthias Apitz Mail-Followup-To: freebsd-current@freebsd.org References: <20180812205049.097f806f@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 12.0-CURRENT r314251 (amd64) X-message-flag: Mails containing HTML will not be read! Please send only plain text. User-Agent: Mutt/1.8.0 (2017-02-23) X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 80.187.97.119 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 19:40:31 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable El d=C3=ADa domingo, agosto 12, 2018 a las 09:32:28p. m. +0200, Michio Hond= a escribi=C3=B3: > Hi Rozhuk, >=20 > I only use a single CPU core and thread, so SO_REUSEPORT_LB has no=20 > effect. Also, I already accept() in loop until getting error, but this=20 > is not a point as I use persistent TCP connections... >=20 > Cheers, > - Michio Hi Michio, Don't top post, please. matthias --=20 Matthias Apitz, =E2=9C=89 guru@unixarea.de, http://www.unixarea.de/ +49-176= -38902045 Public GnuPG key: http://www.unixarea.de/key.pub 13. August 2018: Ich w=C3=BCrde gern einen AUSREISEANTRAG stellen. August 13, 2018: I'd like to ask for an exit permit of this country. --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEXmn7rBYYViyzy/vBR8z35Hb+nREFAltwjRoACgkQR8z35Hb+ nRFcoQ/+PnAqYDp/f8Jn+ph89C62Rx3bbHPykUPKy8c3OtDhe9Y+2kyuThJqzGV0 qxuvD340MqHBqHMc76dgA9QaeW9XmGaDCfteWoT4SaaTyc0yrhajks6OtLXQC5DB LjdM+aywp71jUIygDR0ZkEwwgy5Vd/L8+HTaUUI/K/u7IM8yvuPmHfIgpcwbENrL ewRqlogFGRWTkmgKXxEky+PFA9S0n9QYuKowlfCWZ529/Imw8PGiNI83LIlQXCo0 mEsCOa2QPiSj+Hv3t9W+XqRevNsI8BP3EJOoohWJuAG3fKE55bDfKvbFQRrYeFMr 0PR/rrABQxVROFzKqB7W/JO4WCsrg1DJUnipTAwnnHMwQpG9tMVUBHc99zdr523J A/gENj7Lq8EpYKnEia42i6+08OLtHKcDvk1nE2IgUd5XvfPzTe++I4CdYFP+GF5w yORg4fKx3OP5IRS+wIwfFps+ruUWWBUFiUf4geBZ6N+ME5do/4C+1F+XriaXtLIN 9d9kmV2ln8DkL1jH/b9BHpIdcxA6temkeQBqdLlqx6hQ3E3sEIZ7KqWntEviT4KR mASbnR5pVEh2X44OAJWtbLDJClGnv7wTLultWb8nYDMvLchsC0eIADbcE9E+YeAd 3nIn6iJusIP5twgMhj0tC4kmRRZ1K4TFJrXwrqRtpJ9WqGyj7go= =Jlgn -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT-- From owner-freebsd-current@freebsd.org Sun Aug 12 19:46:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0B4FF107A8AE for ; Sun, 12 Aug 2018 19:46:51 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 68F7476BEA; Sun, 12 Aug 2018 19:46:50 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w7CJkkwG033268 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 12 Aug 2018 21:46:47 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w7CJkj6v033265; Sun, 12 Aug 2018 21:46:46 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Sun, 12 Aug 2018 21:46:45 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Michael Butler cc: FreeBSD Current , mmacy@freebsd.org Subject: Re: kernel build failure In-Reply-To: Message-ID: References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 19:46:51 -0000 On Sun, 12 Aug 2018 16:51+0200, Trond Endrestøl wrote: > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > > > Is anyone else seeing this when building a new kernel with ZFS compiled in? > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > > --- kernel --- > > linking kernel > > ld: error: undefined symbol: dbuf_stats_init > > >>> referenced by dbuf.c > > >>> dbuf.o:(dbuf_init) > > > > ld: error: undefined symbol: dbuf_stats_destroy > > >>> referenced by dbuf.c > > >>> dbuf.o:(dbuf_fini) > > *** [kernel] Error code 1 > > I was just about to create a thread of my own. > > I suspect r337670 didn't add everything > cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See > lines 652 and 697. > > Meanwhile, I'll attempt to revert to r337669. r337669 builds and runs. Looking further into r337670, it seems cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dbuf.h added prototypes for dbuf_stats_init() and dbuf_stats_destroy(), but no implementation can be found in any of the files affected by r337670. -- Trond. From owner-freebsd-current@freebsd.org Sun Aug 12 21:39:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 486A0107D348 for ; Sun, 12 Aug 2018 21:39:17 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EE5A67ABD2 for ; Sun, 12 Aug 2018 21:39:16 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it0-f47.google.com (mail-it0-f47.google.com [209.85.214.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id B3EA01C4E4 for ; Sun, 12 Aug 2018 21:39:16 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it0-f47.google.com with SMTP id 139-v6so10491774itf.0 for ; Sun, 12 Aug 2018 14:39:16 -0700 (PDT) X-Gm-Message-State: AOUpUlE7mij64KayEH/0NjGMrzm8kxr89aOq5tLuUZF9lJuu/HIa6kBa JMnX4zEU2wuhXakO7QT/t18w004vuWvqgfmMAQE= X-Google-Smtp-Source: AA+uWPwn2zqb7Aq4I4ZDJcvzVMWeC0WBuvsZoj46PU+jzFAHoOrpeKVpgWKInIkl4YLGnuG1rpApqnjKZW8iOpY2DkM= X-Received: by 2002:a24:6c04:: with SMTP id w4-v6mr8865536itb.4.1534109956119; Sun, 12 Aug 2018 14:39:16 -0700 (PDT) MIME-Version: 1.0 References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> In-Reply-To: From: Matthew Macy Date: Sun, 12 Aug 2018 14:39:04 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: kernel build failure To: Trond.Endrestol@fagskolen.gjovik.no Cc: Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 21:39:17 -0000 Sorry guys, last time I touched ZFS I tried to push to make it an option to statically link and was actually told that it wasn't something anyone else wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. -M On Sun, Aug 12, 2018 at 12:46 PM Trond Endrest=C3=B8l < Trond.Endrestol@fagskolen.gjovik.no> wrote: > On Sun, 12 Aug 2018 16:51+0200, Trond Endrest=C3=B8l wrote: > > > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > > > > > Is anyone else seeing this when building a new kernel with ZFS > compiled in? > > > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > > > --- kernel --- > > > linking kernel > > > ld: error: undefined symbol: dbuf_stats_init > > > >>> referenced by dbuf.c > > > >>> dbuf.o:(dbuf_init) > > > > > > ld: error: undefined symbol: dbuf_stats_destroy > > > >>> referenced by dbuf.c > > > >>> dbuf.o:(dbuf_fini) > > > *** [kernel] Error code 1 > > > > I was just about to create a thread of my own. > > > > I suspect r337670 didn't add everything > > cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See > > lines 652 and 697. > > > > Meanwhile, I'll attempt to revert to r337669. > > r337669 builds and runs. > > Looking further into r337670, it seems > cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dbuf.h added prototypes > for dbuf_stats_init() and dbuf_stats_destroy(), but no implementation > can be found in any of the files affected by r337670. > > -- > Trond. From owner-freebsd-current@freebsd.org Sun Aug 12 22:25:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0ED91055817 for ; Sun, 12 Aug 2018 22:25:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6674D7CC1D for ; Sun, 12 Aug 2018 22:25:41 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22b.google.com with SMTP id z20-v6so12775393iol.0 for ; Sun, 12 Aug 2018 15:25:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VaCjEWc5stBfseoJJCFaWfUs/vVa7EGMgLDti64d9J4=; b=kZVpMnPvKPNn/hFVGjy8ShmFq6GfoDKCuhu3RSuC8kckt0cVR5POLwquRd3UFpVzMb 6V7RmVXbutolo32fF27VMxhXTdemfQRJYCWXWncv/4AVBAB6M2BwDs8r7gOHAqN3M38o blY5Ud+VuHF9OwPi1YDugabApKYFz9Gsw/IOd5+J6njePFKhUjMTnUfCx66vguqWQc0r NhQttIk+QLU0XBuWljLMjLFRUpnvf9JPzHoVmKZzGr3u79hzBJRFvtBkFErGmtTycHOk hv7U6gp71PMAWaCjvvcMGSbEJlvQeyWIec0JekcMOK849eixvkw6iCIaIvW7lSEAWaJ0 +3TA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VaCjEWc5stBfseoJJCFaWfUs/vVa7EGMgLDti64d9J4=; b=e4TlVbm/BazFVp8Ykh5eFZLMuVOmB4LK+6Y6IZAGWGHzEr9hxi/o4U0jLgY7v1zPTB 5AyUF2Jr1Sm63PcEqoiznoRIkTlsqFA+MmcRLUkvGa0c1XFGqiXc5U/0/aP0CGR3+KBy bCf8TlM32NLceC6yhKgUFx4o5W5aUVUO6vdnaZy3zi+BG6iMZ9A/VoCVTsfUgvZ3emRD ediZeCa7LmwnVm77dyyyLMtB340DSckyQBWAQY5Sq74Ur+XFq7MFW2t5jobNFCd35h+g Uc4W05Lp62FDmaf9iECCi/uo7SxMPfwvThk7Qm2oa7IMILNq7vqADdc1F0HLFTX0fknd cdMA== X-Gm-Message-State: AOUpUlEN2/EZFjcivGDxtpt0JkAcNtXJhFjOziC+IjSEI5S745nmgWUN xKIgxiEN8QDfbIpIqJ4xcfwNl9I4DWb+7lrazmgl7g== X-Google-Smtp-Source: AA+uWPzMTAFIup9g/Dn0TqKVgS48KGBUj438B7mx9cHBIXTBb5z+MNDdwitdpoRbWeGsHmCA1NECJniqcbPaCCSS3Gc= X-Received: by 2002:a6b:f70f:: with SMTP id k15-v6mr5362797iog.37.1534112740683; Sun, 12 Aug 2018 15:25:40 -0700 (PDT) MIME-Version: 1.0 References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> In-Reply-To: From: Warner Losh Date: Sun, 12 Aug 2018 16:25:28 -0600 Message-ID: Subject: Re: kernel build failure To: Matt Macy Cc: =?UTF-8?Q?Trond_Endrest=C3=B8l?= , Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 22:25:42 -0000 On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an option = to > statically link and was actually told that it wasn't something anyone els= e > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > LINT is generated from NOTES automatically... Warner -M > > On Sun, Aug 12, 2018 at 12:46 PM Trond Endrest=C3=B8l < > Trond.Endrestol@fagskolen.gjovik.no> wrote: > > > On Sun, 12 Aug 2018 16:51+0200, Trond Endrest=C3=B8l wrote: > > > > > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: > > > > > > > Is anyone else seeing this when building a new kernel with ZFS > > compiled in? > > > > > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o > > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel > > > > --- kernel --- > > > > linking kernel > > > > ld: error: undefined symbol: dbuf_stats_init > > > > >>> referenced by dbuf.c > > > > >>> dbuf.o:(dbuf_init) > > > > > > > > ld: error: undefined symbol: dbuf_stats_destroy > > > > >>> referenced by dbuf.c > > > > >>> dbuf.o:(dbuf_fini) > > > > *** [kernel] Error code 1 > > > > > > I was just about to create a thread of my own. > > > > > > I suspect r337670 didn't add everything > > > cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See > > > lines 652 and 697. > > > > > > Meanwhile, I'll attempt to revert to r337669. > > > > r337669 builds and runs. > > > > Looking further into r337670, it seems > > cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dbuf.h added prototypes > > for dbuf_stats_init() and dbuf_stats_destroy(), but no implementation > > can be found in any of the files affected by r337670. > > > > -- > > Trond. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Sun Aug 12 22:27:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 37ADB10558EA for ; Sun, 12 Aug 2018 22:27:07 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D55F47CD5A for ; Sun, 12 Aug 2018 22:27:06 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io0-f178.google.com (mail-io0-f178.google.com [209.85.223.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 9C3F11C9ED for ; Sun, 12 Aug 2018 22:27:06 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io0-f178.google.com with SMTP id v26-v6so12751411iog.5 for ; Sun, 12 Aug 2018 15:27:06 -0700 (PDT) X-Gm-Message-State: AOUpUlFvB+tyT8MWHPK4Sl75/iFLAc9fCtPEeTH2drC4N6tys3R5TZ8f XB/I4g2gcidBbmU2m9qw4cOEO5VlfllflUe/eyA= X-Google-Smtp-Source: AA+uWPzxYVGdbqNjnG7H31otavWtKfDBkXVfU1chzBAgWaVIcof7DACSej2B21QujCihoDxPpQwtYsGUTN2woVG3bXQ= X-Received: by 2002:a6b:5a08:: with SMTP id o8-v6mr12813661iob.5.1534112826124; Sun, 12 Aug 2018 15:27:06 -0700 (PDT) MIME-Version: 1.0 References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> In-Reply-To: From: Matthew Macy Date: Sun, 12 Aug 2018 15:26:54 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: kernel build failure To: Warner Losh Cc: Trond.Endrestol@fagskolen.gjovik.no, Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 22:27:07 -0000 On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > > > On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: > >> Sorry guys, last time I touched ZFS I tried to push to make it an option >> to >> statically link and was actually told that it wasn't something anyone el= se >> wanted. The issue comes from ZFS not being in NOTES and thus not in LINT= . >> > > LINT is generated from NOTES automatically... > Yes, hence the "and thus not in LINT" > Warner > > -M >> >> On Sun, Aug 12, 2018 at 12:46 PM Trond Endrest=C3=B8l < >> Trond.Endrestol@fagskolen.gjovik.no> wrote: >> >> > On Sun, 12 Aug 2018 16:51+0200, Trond Endrest=C3=B8l wrote: >> > >> > > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: >> > > >> > > > Is anyone else seeing this when building a new kernel with ZFS >> > compiled in? >> > > > >> > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o >> > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel >> > > > --- kernel --- >> > > > linking kernel >> > > > ld: error: undefined symbol: dbuf_stats_init >> > > > >>> referenced by dbuf.c >> > > > >>> dbuf.o:(dbuf_init) >> > > > >> > > > ld: error: undefined symbol: dbuf_stats_destroy >> > > > >>> referenced by dbuf.c >> > > > >>> dbuf.o:(dbuf_fini) >> > > > *** [kernel] Error code 1 >> > > >> > > I was just about to create a thread of my own. >> > > >> > > I suspect r337670 didn't add everything >> > > cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See >> > > lines 652 and 697. >> > > >> > > Meanwhile, I'll attempt to revert to r337669. >> > >> > r337669 builds and runs. >> > >> > Looking further into r337670, it seems >> > cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dbuf.h added prototypes >> > for dbuf_stats_init() and dbuf_stats_destroy(), but no implementation >> > can be found in any of the files affected by r337670. >> > >> > -- >> > Trond. >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g >> " >> > From owner-freebsd-current@freebsd.org Sun Aug 12 22:28:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C2DA71055A08 for ; Sun, 12 Aug 2018 22:28:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5580C7CE98 for ; Sun, 12 Aug 2018 22:28:25 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x235.google.com with SMTP id d70-v6so9868052ith.1 for ; Sun, 12 Aug 2018 15:28:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tdIusj2GIkCLwQz3pWfMiMHpFOdG7L8d5qP6TF7HYnw=; b=1R/xJo/HKU+HClDCQk7F5DwQZVLhYCVKYlyWJcD9TTuQXuvc5lFcsYyLNs8jwaVVWv QyniSTpm2LLFtiJ1FFKv5XmXTSLhlYRMmm9FfSb2Wze1zjcAII7WBeX7fGRWNytoFDLe kdvkjRdpCvTTEJnvfnAYJATO7vTAT4/6F5NDllCMVpQenx+4+EGc9oFsa5S+Dt4DZDL/ OxM3qNWJRmX9m1uKNrspl/8G6Euz586lztxKoaTGtAy60FTesFbbWMlD7LxcsnheQYUD e3NmV6cbKSZzjbqy/3gqdENNuw/d909gUMR2saMHUcUTpfMTvDU7O8o0gsuC6qbeBlYy n0PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tdIusj2GIkCLwQz3pWfMiMHpFOdG7L8d5qP6TF7HYnw=; b=YtWrWZwFBHNkpskye1cGXWUsk+5MY4DsoAL3RtBk9ryxluehE2P7uWA0XZHeh9QC8Q eo2f0no8LzLh/EyaurWtR3n/YUzvjhApujMkNlqpXSNoUh2FtajPx0R7ZyovRfdnc+MU MmOprO/tdM1uWGHQvJryNs77IKfltwzna+iV1ANINqmcbLHmbHoDUh/YLry2KKQyPymL CLlZS6n/Q+FVpnfi/riJpX+YxOH2aEtxUJTfyERPYjLZY1ZrUTE+Pi8IAczwqIkezrDl w2hG7oH3Hz2aFqIyjwxeL3yQusalIMijkUVh1NYxYbhiw8+FZLO3jZ7I/N/NVeoreBkU kd+w== X-Gm-Message-State: AOUpUlG3w3swXzbBS+j6Kd6syhlqFl5CIVH42xKn6d8vXfx4Fw2ZqPgY bjkFefpWafeap8wpp93+/yPgjoJS+WGDRo7g2WIUqBvpwz0= X-Google-Smtp-Source: AA+uWPyF59QJ410PFcc43HrD22BdC6pb/ngtwdLRQEDyI7/lhXL4krl8db+6cWIzDm/dcDlNfdoSCFS3vw1XHZMaW0g= X-Received: by 2002:a02:3344:: with SMTP id k4-v6mr13473036jak.45.1534112904576; Sun, 12 Aug 2018 15:28:24 -0700 (PDT) MIME-Version: 1.0 References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> In-Reply-To: From: Warner Losh Date: Sun, 12 Aug 2018 16:28:13 -0600 Message-ID: Subject: Re: kernel build failure To: Matt Macy Cc: =?UTF-8?Q?Trond_Endrest=C3=B8l?= , Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Aug 2018 22:28:26 -0000 On Sun, Aug 12, 2018, 4:27 PM Matthew Macy wrote: > > > On Sun, Aug 12, 2018 at 3:25 PM Warner Losh wrote: > >> >> >> On Sun, Aug 12, 2018, 3:40 PM Matthew Macy wrote: >> >>> Sorry guys, last time I touched ZFS I tried to push to make it an optio= n >>> to >>> statically link and was actually told that it wasn't something anyone >>> else >>> wanted. The issue comes from ZFS not being in NOTES and thus not in LIN= T. >>> >> >> LINT is generated from NOTES automatically... >> > > Yes, hence the "and thus not in LINT" > I missed one of the nots :( Warner > >> Warner >> >> -M >>> >>> On Sun, Aug 12, 2018 at 12:46 PM Trond Endrest=C3=B8l < >>> Trond.Endrestol@fagskolen.gjovik.no> wrote: >>> >>> > On Sun, 12 Aug 2018 16:51+0200, Trond Endrest=C3=B8l wrote: >>> > >>> > > On Sun, 12 Aug 2018 09:37-0400, Michael Butler wrote: >>> > > >>> > > > Is anyone else seeing this when building a new kernel with ZFS >>> > compiled in? >>> > > > >>> > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/vers.o >>> > > > Building /usr/obj/usr/src/amd64.amd64/sys/VM01/kernel >>> > > > --- kernel --- >>> > > > linking kernel >>> > > > ld: error: undefined symbol: dbuf_stats_init >>> > > > >>> referenced by dbuf.c >>> > > > >>> dbuf.o:(dbuf_init) >>> > > > >>> > > > ld: error: undefined symbol: dbuf_stats_destroy >>> > > > >>> referenced by dbuf.c >>> > > > >>> dbuf.o:(dbuf_fini) >>> > > > *** [kernel] Error code 1 >>> > > >>> > > I was just about to create a thread of my own. >>> > > >>> > > I suspect r337670 didn't add everything >>> > > cddl/contrib/opensolaris/uts/common/fs/zfs/dbuf.c depends on. See >>> > > lines 652 and 697. >>> > > >>> > > Meanwhile, I'll attempt to revert to r337669. >>> > >>> > r337669 builds and runs. >>> > >>> > Looking further into r337670, it seems >>> > cddl/contrib/opensolaris/uts/common/fs/zfs/sys/dbuf.h added prototype= s >>> > for dbuf_stats_init() and dbuf_stats_destroy(), but no implementation >>> > can be found in any of the files affected by r337670. >>> > >>> > -- >>> > Trond. >>> _______________________________________________ >>> freebsd-current@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current >>> To unsubscribe, send any mail to " >>> freebsd-current-unsubscribe@freebsd.org" >>> >> From owner-freebsd-current@freebsd.org Mon Aug 13 05:30:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B696310665C0 for ; Mon, 13 Aug 2018 05:30:44 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl2.internode.on.net (ipmail06.adl2.internode.on.net [150.101.137.129]) by mx1.freebsd.org (Postfix) with ESMTP id ED6DA8AE00 for ; Mon, 13 Aug 2018 05:30:43 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from unknown (HELO leader.local) ([118.211.111.37]) by ipmail06.adl2.internode.on.net with ESMTP; 13 Aug 2018 13:56:10 +0930 Subject: Re: FreeBSD elf_machine_id To: blubee blubeeme Cc: FreeBSD current References: From: Shane Ambler Message-ID: <69ca3709-fea2-efad-b108-b9173261eefd@ShaneWare.Biz> Date: Mon, 13 Aug 2018 13:56:05 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 05:30:44 -0000 On 12/8/18 11:32 pm, blubee blubeeme wrote: > On Sun, Aug 12, 2018 at 9:59 PM blubee blubeeme wrote: > >> >> >> On Sun, Aug 12, 2018 at 7:43 PM Dimitry Andric wrote: >> >>> On 12 Aug 2018, at 13:21, blubee blubeeme wrote: >>>> >>>> What's the elf_machine_id for FreeBSD amd64 systems? >>>> >>>> How can I find this info? >>> >>> There isn't any FreeBSD-specific machine ID, just a machine ID for >>> x86-64 (aka amd64) in general: >>> >>> $ grep x86-64 /usr/include/sys/elf_common.h >>> #define EM_X86_64 62 /* Advanced Micro Devices x86-64 */ >>> #define EM_AMD64 EM_X86_64 /* Advanced Micro Devices x86-64 >>> (compat) */ >>> >>> -Dimitry >>> >>> Thank you for the clarification. >> >> I think in this case I was looking for 62. >> >> Best, >> Owen >> > Actually I had another quick question along these lines. > > if x86_64 is already defined should I bother changing those to amd64 or > just use x86_64 and make FreeBSD modifications where Linux specifics are > defined? As I understand it, AMD designed the 64bit extensions and early adopters referred to it as amd64, then when Intel adopted it they needed a more generic term, so x86_64 was started, now usually both __X86_64__ and __amd64__ are compiler defined based on the target. So it may depend on why you are asking for the elf_machine_id. For general C/C++ programming - #if defined(__x86_64__) // 64bit code #else // 32 bit code #endif or to be safe you can check all variations #if defined(__X86_64__) || defined(__amd64__) For freebsd specific changes - #if defined(__FreeBSD__) #include #if __FreeBSD_version < 1101000 // version specific see porters handbook for version list #endif #endif If you want to see all the compiler defined environment macros run clang++ -dM -E -x c /dev/null or clang++ -dM -E -x c++ /dev/null or for a 32bit env clang++ -dM -E -m32 -x c++ /dev/null works for clang and gcc. I believe when multiple variations exist, the __xx__ macros are most common eg use __x86_64__ not __x86_64 -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-current@freebsd.org Mon Aug 13 09:34:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BB63B106C09A for ; Mon, 13 Aug 2018 09:34:31 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from smtp.fagskolen.gjovik.no (smtp.fagskolen.gjovik.no [IPv6:2001:700:1100:1:200:ff:fe00:b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.fagskolen.gjovik.no", Issuer "Fagskolen i Gj??vik" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3750D71E50; Mon, 13 Aug 2018 09:34:31 +0000 (UTC) (envelope-from trond@fagskolen.gjovik.no) Received: from mail.fig.ol.no (localhost [127.0.0.1]) by mail.fig.ol.no (8.15.2/8.15.2) with ESMTPS id w7D9YFix086276 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 13 Aug 2018 11:34:15 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) Received: from localhost (trond@localhost) by mail.fig.ol.no (8.15.2/8.15.2/Submit) with ESMTP id w7D9YElm086273; Mon, 13 Aug 2018 11:34:14 +0200 (CEST) (envelope-from trond@fagskolen.gjovik.no) X-Authentication-Warning: mail.fig.ol.no: trond owned process doing -bs Date: Mon, 13 Aug 2018 11:34:14 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Sender: Trond.Endrestol@fagskolen.gjovik.no To: Matthew Macy cc: Michael Butler , freebsd-current Subject: Re: kernel build failure In-Reply-To: Message-ID: References: <748179e1-72bd-99e3-2267-302274be3d32@protected-networks.net> User-Agent: Alpine 2.21.9999 (BSF 287 2018-06-16) Organization: Fagskolen Innlandet OpenPGP: url=http://fig.ol.no/~trond/trond.key MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-2.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.fig.ol.no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 09:34:31 -0000 On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > Sorry guys, last time I touched ZFS I tried to push to make it an option to > statically link and was actually told that it wasn't something anyone else > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. If consensus is that "options ZFS" is no longer valid, then maybe UPDATING should reflect the fact. I can live with loading zfs.ko and opensolaris.ko at boot time, but I think this is a step backwards. -- Trond. From owner-freebsd-current@freebsd.org Mon Aug 13 16:30:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0F139107717D for ; Mon, 13 Aug 2018 16:30:08 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 915A280C29; Mon, 13 Aug 2018 16:30:07 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w7DGSwA5037858; Mon, 13 Aug 2018 09:28:58 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w7DGSvOm037857; Mon, 13 Aug 2018 09:28:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> Subject: Re: kernel build failure In-Reply-To: To: =?ISO-8859-1?Q?Trond_Endrest=F8l?= Date: Mon, 13 Aug 2018 09:28:57 -0700 (PDT) CC: Matthew Macy , Michael Butler , freebsd-current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 16:30:08 -0000 > On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > > > Sorry guys, last time I touched ZFS I tried to push to make it an option to > > statically link and was actually told that it wasn't something anyone else > > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > > If consensus is that "options ZFS" is no longer valid, then maybe > UPDATING should reflect the fact. > > I can live with loading zfs.ko and opensolaris.ko at boot time, but I > think this is a step backwards. Please no, I can think of no sound reason that you should be forced to use modules. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Mon Aug 13 16:35:18 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2D3471077472 for ; Mon, 13 Aug 2018 16:35:18 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 CD61E81083; Mon, 13 Aug 2018 16:35:17 +0000 (UTC) (envelope-from yuripv@yuripv.net) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id 2CF5A21949; Mon, 13 Aug 2018 12:35:17 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Mon, 13 Aug 2018 12:35:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yuripv.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=3Z+KUDz1ASswzH5EvpKSzhJ9+ScSb kkWwjklkU0On0M=; b=slizx2Wf/68xmfXp9RXiAMrCYfo80gAA3v9B3oaaCvf5s Meihwks7dOkwwN8XolA6zZ0xNssVjmP5dARPIXmRk0de1aekrdxdz+VDVP+wvFvQ sbFEOtbAqn4NAgZHnlH7mTY6DHUzLM7nS8Iu4pt0WsVJX73gDTxl/LVzk3qlZQYQ QpQew6eX7sECIhM1uFsSJ+ns0m3LhtI0v0WoMA2i+5Op42nINTyzB3TQvpydooa5 Gh10fgQR1gwRTAXqxQI1wEap47lI/mwXKXCKYgzni6xY9KvzqJsS/1yGyXjMPVIK 5GPQn4UD5SWn4euV6/mPETKH0hUu3QLxGCr8i9fgA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=3Z+KUD z1ASswzH5EvpKSzhJ9+ScSbkkWwjklkU0On0M=; b=syC6bGrpvWysj/oZ2uoWD5 fXnnyhkK4flGjphsKSvs02fthLF8N2uvrR7g4fqUuGQUoCzpcgOa4WpxPCBIVLWq SuQ+Szvftapc4q1X6GZ/x8DUHjzzGHL4M98vZje3SCRBUjKRpIrLnYBsA5MF2AFz pwry7vcSPTyKv/W9jcKAjCm/vSJCKSuMVCwBvMqL8O2pYR5/G5jpxSDjame4l1IA hOUcu/bYIfWKipy7/sGZtpn3JJ0e5lQYKnB3/mMB/WLJXG33mE68AJQ51EYY/dZF tTZ1fu7J3cb5KJvA8XzjDJADze3txdF0NjRR+HZfw1S7JMFyD6New+myqVL/oBMg == X-ME-Proxy: X-ME-Sender: Received: from [192.168.1.2] (unknown [5.138.208.65]) by mail.messagingengine.com (Postfix) with ESMTPA id 86A79E4439; Mon, 13 Aug 2018 12:35:14 -0400 (EDT) Subject: Re: kernel build failure To: "Rodney W. Grimes" , =?UTF-8?Q?Trond_Endrest=c3=b8l?= Cc: Matthew Macy , Michael Butler , freebsd-current References: <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> From: Yuri Pankov Message-ID: <65768f5e-2228-3abb-9f99-8398ceab6911@yuripv.net> Date: Mon, 13 Aug 2018 19:35:13 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Aug 2018 16:35:18 -0000 Rodney W. Grimes wrote: >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: >> >>> Sorry guys, last time I touched ZFS I tried to push to make it an option to >>> statically link and was actually told that it wasn't something anyone else >>> wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. >> >> If consensus is that "options ZFS" is no longer valid, then maybe >> UPDATING should reflect the fact. >> >> I can live with loading zfs.ko and opensolaris.ko at boot time, but I >> think this is a step backwards. > > Please no, I can think of no sound reason that you should be > forced to use modules. Isn't it already fixed in r337690? From owner-freebsd-current@freebsd.org Tue Aug 14 00:33:49 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0F4B105A835 for ; Tue, 14 Aug 2018 00:33:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-QB1-obe.outbound.protection.outlook.com (mail-eopbgr660060.outbound.protection.outlook.com [40.107.66.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2BB8C74357; Tue, 14 Aug 2018 00:33:49 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB1658.CANPRD01.PROD.OUTLOOK.COM (52.132.45.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1038.25; Tue, 14 Aug 2018 00:33:47 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127%2]) with mapi id 15.20.1017.022; Tue, 14 Aug 2018 00:33:47 +0000 From: Rick Macklem To: "Rodney W. Grimes" , =?iso-8859-1?Q?Trond_Endrest=F8l?= CC: Matthew Macy , Michael Butler , freebsd-current Subject: Re: kernel build failure Thread-Topic: kernel build failure Thread-Index: AQHUMkHEMR6ykmvW6UWy+GTgG+tskKS8M2GAgABSgYCAAB9iAIAAx9AAgABz34CAAIaOLA== Date: Tue, 14 Aug 2018 00:33:47 +0000 Message-ID: References: , <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> In-Reply-To: <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB1658; 6:Seow+8SZkJJrNfwt2m7Tz+yQruiTrKFxAiMHE3iy7rJ0ckrQ6SGRjYSA0yRbD6+5t2ZtnU4CFW+LRykoqrpndFEjx5WgRPEzL5VEYTS1KLgt//B+TeaMoJk9YF3Ub9BRVrNOnAj7UOUuCLxO0M37jq5+MIIhOmn5NbpqCmnLrqMzFzPG08mAKM/wViVns3pNlUaNRMWWBpeHpqFt57+roO1R49LEM7d7yPwXMYIH1Xd1KxC2pMwqOBB+Ei9ChLi64bI+nbDDe27V/QhafZsU6IhOMdq35T0L7Fs4MP52SU8SfREG/ZLRKu5qpporLRurhnuB62db854gb5v4j52ONtwEuRLME0J+kZOU2V5MrBzetdJQL7qpEpczILZkyrovFNwhWE53dQePDoylm/fWDxFfBsSE2qNpYYGRWngtU4ERMMeCrgIzA92Dy0gQLRwi0adh1JbtHMkHZBqbjR1iMw==; 5:jy8+1QD7UuTTG9LXxrg8HPlv2HxOQV4BuruXXgCEhhNH4/5+Dac6LW5ci/GlsDom1Ln1E1Kbkf/eBYDpdKOvFDt3673obXUdR4v0PWziCLWJSgfydr6WkD4cPHvdtVtskaSnxSVTLCvu8tJ5rm5h79iELjFcssUjKBS6if6aH8g=; 7:ok0DKnk7LrAr8is2m5xZ+D1ZxZkfItiy4mA77yt8SgGuIdI3EKjN1tJCRVoeeg/KZqLfXOZ6OJbsS+2r/bBzFlwgpq4H60hg35kL/T6wxkXx5/8Tj5/1dnczYbGLNQvaSmdmTUsRqv6mTBbUJaq+jyarxbdoEkMkZ5KKDboDdn3E6Pu+0ETAswbORBoBepPc1jPvdVu9Nahl+hr2ZlzY3kjmjbKbAHbEKtKfpcQ0v6INUXIk3CoOYhoP5YcqWD4o x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: d7e46217-7f8e-4884-112e-08d6017d9932 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB1658; x-ms-traffictypediagnostic: YTOPR0101MB1658: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(100405760836317); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123560045)(20161123564045)(20161123562045)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:YTOPR0101MB1658; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB1658; x-forefront-prvs: 0764C4A8CD x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(346002)(376002)(366004)(136003)(396003)(39860400002)(199004)(189003)(446003)(476003)(8936002)(11346002)(53936002)(316002)(786003)(54906003)(110136005)(3480700004)(76176011)(7116003)(7696005)(486006)(5660300001)(99286004)(86362001)(68736007)(25786009)(74316002)(186003)(2900100001)(4326008)(26005)(6246003)(6436002)(9686003)(305945005)(55016002)(6506007)(102836004)(81156014)(81166006)(74482002)(97736004)(8676002)(5250100002)(106356001)(2906002)(229853002)(105586002)(33656002)(478600001)(14454004)(256004); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB1658; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: hZBTr4TzTRXrGqKm8G+WjYreAFjNnEibrBaulT2s7+eYREXXRDOk3WVKYjs+kATU59cgoQJhNJf398s7psp0ECKpZK6xSHwN/RVPBd7Zr+CIUNU9IrVIe+HlwbdB4X7pi64/wtRpvWziQhZn/Ru+4tji8YMeqgoSOYsWi1TT6gUZW0XYlL98q8wq68nok8FwLoJgVOB6oO5J7GBcx7YpaldeMfRMRxWZ/DK7BT5pyEevlrvUw+TIYHGk0fT6PWOtbRdDoONw41j/lLvR1W2vsPtaKM1Uc9//+SPFYpnFiuhKenmdjgLUD6aafRJDkxQ7aY4sRT+B6WxIQfcCYD5099qb4fsBfxGKE6XJwmIJ3SY= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: d7e46217-7f8e-4884-112e-08d6017d9932 X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Aug 2018 00:33:47.1301 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB1658 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 00:33:49 -0000 Rodney W. Grimes wrote: >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: >> >> > Sorry guys, last time I touched ZFS I tried to push to make it an opti= on to >> > statically link and was actually told that it wasn't something anyone = else >> > wanted. The issue comes from ZFS not being in NOTES and thus not in LI= NT. >> >> If consensus is that "options ZFS" is no longer valid, then maybe >> UPDATING should reflect the fact. >> >> I can live with loading zfs.ko and opensolaris.ko at boot time, but I >> think this is a step backwards. > >Please no, I can think of no sound reason that you should be >forced to use modules. I thought that ZFS was required to be a module because of the licensing terms (they didn't want any CDDL code in the core kernel)? rick From owner-freebsd-current@freebsd.org Tue Aug 14 00:35:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EADE9105A94A for ; Tue, 14 Aug 2018 00:35:30 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9B00174472 for ; Tue, 14 Aug 2018 00:35:30 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-it0-f45.google.com (mail-it0-f45.google.com [209.85.214.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 61D712688D for ; Tue, 14 Aug 2018 00:35:30 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-it0-f45.google.com with SMTP id 139-v6so17237117itf.0 for ; Mon, 13 Aug 2018 17:35:30 -0700 (PDT) X-Gm-Message-State: AOUpUlEKipZhqAhgkOWHF9lprCGvZjI3Nutw2Y4Mtly40iFnd80EZce+ oq1DmGUYpJL80NXwgqq3lvf7t95xMJfBfDRuG+4= X-Google-Smtp-Source: AA+uWPyS9IBQRgl2/5uJAimw0gNYte8+ZHbVAXWu065WIMe8swvVomAKyEZkhz6gtTaYPjqIV/MfBhxmr3NpmTh0jIY= X-Received: by 2002:a02:8c94:: with SMTP id f20-v6mr16954462jak.98.1534206929924; Mon, 13 Aug 2018 17:35:29 -0700 (PDT) MIME-Version: 1.0 References: <201808131628.w7DGSvOm037857@pdx.rh.CN85.dnsmgr.net> In-Reply-To: From: Matthew Macy Date: Mon, 13 Aug 2018 17:35:18 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: kernel build failure To: Rick Macklem Cc: freebsd-rwg@pdx.rh.cn85.dnsmgr.net, =?UTF-8?Q?Trond_Endrest=C3=B8l?= , Michael Butler , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 00:35:31 -0000 On Mon, Aug 13, 2018 at 5:33 PM Rick Macklem wrote: > Rodney W. Grimes wrote: > >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > >> > >> > Sorry guys, last time I touched ZFS I tried to push to make it an > option to > >> > statically link and was actually told that it wasn't something anyone > else > >> > wanted. The issue comes from ZFS not being in NOTES and thus not in > LINT. > >> > >> If consensus is that "options ZFS" is no longer valid, then maybe > >> UPDATING should reflect the fact. > >> > >> I can live with loading zfs.ko and opensolaris.ko at boot time, but I > >> think this is a step backwards. > > > >Please no, I can think of no sound reason that you should be > >forced to use modules. > I thought that ZFS was required to be a module because of the licensing > terms (they didn't want any CDDL code in the core kernel)? > It can't be in _GENERIC_ for that reason. There's no reason it can't be in LINT or end users can't configure a CDDL tainted kernel. -M > rick > > From owner-freebsd-current@freebsd.org Tue Aug 14 01:53:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24C801061484 for ; Tue, 14 Aug 2018 01:53:32 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [202.12.127.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id BBBC777ADD; Tue, 14 Aug 2018 01:53:31 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1534211603; bh=OHMp4LioAMXhZ6po+k1Mth7lKa9tKPs2j0Uf/68 wEK8=; b=IALIqpgimIaAYrqTkVzrR6ddMBlJ6h96098ChRK29/unX8oEEDN6Cuo c0z8zmQMR+bc09+cXSWa8XITAfe984xziRD5HSK6RulQYM5DGoQgrB8GekPwSKBP v+UtYDeDTc4tZ+qSie2qzxAi+v4jH9ws12N83KE36+Aqu28CyzWc= Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [192.168.1.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 6A699233EA; Mon, 13 Aug 2018 21:53:23 -0400 (EDT) To: FreeBSD Current , markj@freebsd.org From: Michael Butler Subject: non-SMP i386 build failure after SVN r337715 Openpgp: preference=signencrypt Message-ID: Date: Mon, 13 Aug 2018 21:53:22 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 01:53:32 -0000 non-SMP builds apparently don't define some required structures .. --- kernel --- linking kernel ld: error: undefined symbol: cpu_info >>> referenced by ucode.c >>> ucode.o:(ucode_load_ap) ld: error: undefined symbol: cpu_apic_ids >>> referenced by ucode.c >>> ucode.o:(ucode_load_ap) ld: error: undefined symbol: cpu_info >>> referenced by ucode.c >>> ucode.o:(ucode_reload) ld: error: undefined symbol: cpu_apic_ids >>> referenced by ucode.c >>> ucode.o:(ucode_reload) *** [kernel] Error code 1 imb From owner-freebsd-current@freebsd.org Tue Aug 14 02:11:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B13210649A7 for ; Tue, 14 Aug 2018 02:11:54 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (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 CA43F78E48; Tue, 14 Aug 2018 02:11:53 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w7E2Aeaj039934; Mon, 13 Aug 2018 19:10:40 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w7E2AeOs039933; Mon, 13 Aug 2018 19:10:40 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201808140210.w7E2AeOs039933@pdx.rh.CN85.dnsmgr.net> Subject: Re: kernel build failure In-Reply-To: To: Rick Macklem Date: Mon, 13 Aug 2018 19:10:40 -0700 (PDT) CC: =?ISO-8859-1?Q?Trond_Endrest=F8l?= , Matthew Macy , Michael Butler , freebsd-current X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 02:11:54 -0000 [ Charset ISO-8859-1 unsupported, converting... ] > Rodney W. Grimes wrote: > >> On Sun, 12 Aug 2018 14:39-0700, Matthew Macy wrote: > >> > >> > Sorry guys, last time I touched ZFS I tried to push to make it an option to > >> > statically link and was actually told that it wasn't something anyone else > >> > wanted. The issue comes from ZFS not being in NOTES and thus not in LINT. > >> > >> If consensus is that "options ZFS" is no longer valid, then maybe > >> UPDATING should reflect the fact. The consensus here should be that options ZFS is totally valid. > >> I can live with loading zfs.ko and opensolaris.ko at boot time, but I > >> think this is a step backwards. > > > >Please no, I can think of no sound reason that you should be > >forced to use modules. > I thought that ZFS was required to be a module because of the licensing > terms (they didn't want any CDDL code in the core kernel)? I am not asking that we distribute a statically linked kernel, that does create an issue for a GPL kernel, but not for a BSD kernel, I am asking that we continue to be able to statically link ZFS into the kernel as we have been able to for some time. For a very short period of time due to mmacy commit this was broken, he quickly fixed it, so this is a moot issue again. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Tue Aug 14 09:13:16 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6E7291072228 for ; Tue, 14 Aug 2018 09:13:16 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD9A386430 for ; Tue, 14 Aug 2018 09:13:15 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x233.google.com with SMTP id c14-v6so11513977wmb.4 for ; Tue, 14 Aug 2018 02:13:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FCOEQoZ3MoVXlDoqF7wm+a/0XzIaolMztkomDs6cV84=; b=VbNGRk8EwJd/cDJTl1LZh4VDAZbA9n0EybBW3IAjb1lI9r2xjWWE/D4FyPH8LQqigi SeA64XVcohpIh67LaXAAnJKOYR9p6iaOZKfYKvEMWRlBek0Mwb3GLwMKMU71TiF0nvL8 J6VnnL+Ij2Bq7MFtgKwPTP6yJMoIkxjXho8KFMO4WDO22nDiJmVN3rDwWw0ejlegC2I4 ySPbmiRFNDzZtmeGaVdK8mTqOIBJcx4kfr6K6DQLXnXHV8rA0J7CQiydbEiCgu7K3CCy Y5HJ4dGWBd+9BM2S3y6b7qvzPsbb09uMRS5VT3PDtSbFSaZ3P1SsBxt/wkNfFNkimCQG BzRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=FCOEQoZ3MoVXlDoqF7wm+a/0XzIaolMztkomDs6cV84=; b=DrxcHjruddvO3N4Vr4ozCktnotIipA38O3EVP0LpWAnzY2G4BlVbDwu3EbULSr732x UDxb/JZRGJ0cKWfMfyvrKhSQM3nKbT+d8NEziQbe0I9Bf7J6LwhueMm0PmXR8O82r26o vOPF2FvqWvTcJSg0xq6llPfwZ9c2fR0BHXQ4ky0XhqVDzvJ4C1gvZiKmBdkSHoNHr+2N /rk2JCtqP72eVSGuOj5d87T6Hx5sH3/r+99CVyLlSyYIImtAn7Hp7qOdEte1Q3love3c yBZsrU3Sf08MYqnqh58lU60O0TV+cKlT3bRQ0I0ebysnod6PTBVLMilGrfbCntOszNY3 0oCQ== X-Gm-Message-State: AOUpUlGoAM1Zn/+j0FFKeWbDeCvImgeFrhU+cnquLxaZoVi3l74C2Cq+ 6d7jhEkdODCPFrrO+lQSjPmeB0lykEqYKSwl9rSDIiK2 X-Google-Smtp-Source: AA+uWPytWgzRViDr9yuDMUH2t3gFQHLoE/hsOxofqQf7gkZJ1aVLCr1cvd+WgJ6gfkT7A1XytBNvlxssnZkqpIae9Hw= X-Received: by 2002:a1c:f03:: with SMTP id 3-v6mr10291851wmp.129.1534237994659; Tue, 14 Aug 2018 02:13:14 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Tue, 14 Aug 2018 10:12:37 +0100 Message-ID: Subject: Make drm drivers use MTRR write-combine To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 09:13:16 -0000 Hi Something that we have seen for a long time on FreeBSD is the boot message Failed to add WC MTRR for [0xd0000000-0xdfffffff]: -22; performance may suffer Taking a closer look at this with memcontrol I can see that the 256 MB region that DRM wants to set as WC is already covered by this entry 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active Similar on both my Skylake and Broadwell systems. The linuxkpi wrapper can be found here: https://github.com/FreeBSDDesktop/kms-drm/blob/drm-v4.15/linuxkpi/gplv2/src/linux_mtrr.c There doesn't seem to exist a function for changing the properties of a sub region: https://github.com/FreeBSDDesktop/freebsd-base/blob/master/sys/dev/mem/memutil.c Any ideas of a good solution to this? Can this region be blacklisted or is there a safe way to split the big region into several regions with different flags when the drm driver loads? For reference, my AMD machine logs this # dmesg | grep MTRR Successfully added WC MTRR for [0xe0000000-0xefffffff]: 0; # memcontrol list --SNIP-- 0xff000/0x1000 BIOS write-protect fixed-base fixed-length set-by-firmware active 0x0/0x80000000 BIOS write-back set-by-firmware active 0x80000000/0x40000000 BIOS write-back set-by-firmware active 0xc0000000/0x20000000 BIOS write-back set-by-firmware active 0xe0000000/0x10000000 drm write-combine active Not sure if it's a BIOS or CPU vendor issue. From owner-freebsd-current@freebsd.org Tue Aug 14 13:55:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A980A1078AC9 for ; Tue, 14 Aug 2018 13:55:39 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) (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 590C08FA89 for ; Tue, 14 Aug 2018 13:55:39 +0000 (UTC) (envelope-from eric@vangyzen.net) Received: from hammy.vangyzen.net (unknown [147.178.0.137]) by smtp.vangyzen.net (Postfix) with ESMTPSA id 9461C5646E for ; Tue, 14 Aug 2018 08:55:37 -0500 (CDT) Subject: Re: Make drm drivers use MTRR write-combine To: freebsd-current@freebsd.org References: From: Eric van Gyzen Message-ID: <3b53edb8-e1d2-109f-6ec7-81513c513433@vangyzen.net> Date: Tue, 14 Aug 2018 08:55:36 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 13:55:39 -0000 On 8/14/18 4:12 AM, Johannes Lundberg wrote: > Hi > > Something that we have seen for a long time on FreeBSD is the boot message > > Failed to add WC MTRR for [0xd0000000-0xdfffffff]: -22; performance may > suffer > > Taking a closer look at this with memcontrol I can see that the 256 MB > region that DRM wants to set as WC is already covered by this entry > 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active > > Similar on both my Skylake and Broadwell systems. I see something similar on my Dell XPS 13 with a Kaby Lake R: Failed to add WC MTRR for [0x90000000-0x9fffffff]: -22; performance may suffer 0x80000000/0x80000000 BIOS uncacheable set-by-firmware active The only mappings in this range are MMIO: machdep.efi_map: Type Physical Virtual #Pages Attr [snip] MemoryMappedIO 0000e0000000 0xe0000000 00010000 RUNTIME MemoryMappedIO 0000fe000000 0xfe000000 00000011 UC RUNTIME MemoryMappedIO 0000fec00000 0xfec00000 00000001 UC RUNTIME MemoryMappedIO 0000fee00000 0xfee00000 00000001 UC WT WB WP RUNTIME MemoryMappedIO 0000ff000000 0xff000000 00001000 UC WT WB WP RUNTIME Eric From owner-freebsd-current@freebsd.org Tue Aug 14 13:59:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BBB731078E28 for ; Tue, 14 Aug 2018 13:59:08 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E9C567003C for ; Tue, 14 Aug 2018 13:59:07 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl0-x230.google.com with SMTP id d5-v6so8358113pll.4 for ; Tue, 14 Aug 2018 06:59:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=MzyfKvrAOIlMZYXfwz9IQ6qJ8Yj/0rTh/zyGPorGOVY=; b=nA3PSg/ztmeo9gFOpo1JIw9Wf+ZYSlgwRbnC592OXVwDofqwtPidQ5VUWjJJ7UZpFY mPUZTHSb8s4uXyOXTEYFxwUF+3y++u8BoFYCl8x9wbzdnI1KRhAEimldl3O1JplI+NMB gkTZErCuoCFmVxekZTZBeVe96wKkRqVCvgSqcy8F5cMAI5XzkwFDclQkgiJTh1TgZHvc C7cIP29TlclJGr2mSMuZcHuX+QQQd5FHMYU561prkJXabkKMHOKahwYhuJjQ9cxaiq/7 UIJgvif5LFO70v5beIm6zMCWtlemIl6zREVXUL6UaNsvUtqJw3TFR+Hzkgsiz8KgXlky 0Zgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=MzyfKvrAOIlMZYXfwz9IQ6qJ8Yj/0rTh/zyGPorGOVY=; b=ZFssSnISGi6z8c2IYx1/eJdTc870mrj6rr7FgpLY+qbrcKc3klse/Jq/jUTHt7+yc7 /AKyH+d3jvS218wuoMpIKewJDBKHWhealtmsNA0khH8sWZ1oRnVtYhykKF5rs/j2VmA6 wEe8XqJz2MyB8LPc/Zjh8TL7BR1LjkHm0/DH7edYToRFrXNn61Vb9jRRCtkNffhTEws+ XqZyFHT4nb0iy0X0QhcMz7VvrzqfjTsBktXC0CDsiMqx1wWpjCD9TVh9BIOrePjgTyT2 IQJW8yqe9P5XOmNOpHwEQkRaIWK9gAdV2+6TeX89nSrogj6KtjTm1xSWFEcFmUQiv8/K HXDg== X-Gm-Message-State: AOUpUlHHcvwdkaT0GB1Kg1fxVG8VNn7dnxRpJNKi8ZUU4af2J1e3Cip8 M9nmP/UOoUJEGl7NtV/5wit9tekZ X-Google-Smtp-Source: AA+uWPwX68+GfNJ87lqB9euv1gXOyPguToWNnhLX4wIyoLQll/S6rwMe0BK+Ok1uLLFYes3Vp85c/Q== X-Received: by 2002:a17:902:bc41:: with SMTP id t1-v6mr20845639plz.26.1534255147029; Tue, 14 Aug 2018 06:59:07 -0700 (PDT) Received: from raichu (toroon0560w-lp130-09-70-52-224-239.dsl.bell.ca. [70.52.224.239]) by smtp.gmail.com with ESMTPSA id i62-v6sm30866926pge.66.2018.08.14.06.59.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Aug 2018 06:59:06 -0700 (PDT) Sender: Mark Johnston Date: Tue, 14 Aug 2018 09:59:00 -0400 From: Mark Johnston To: Michael Butler Cc: FreeBSD Current Subject: Re: non-SMP i386 build failure after SVN r337715 Message-ID: <20180814135900.GA17101@raichu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 13:59:08 -0000 On Mon, Aug 13, 2018 at 09:53:22PM -0400, Michael Butler wrote: > non-SMP builds apparently don't define some required structures .. Thanks, this should be fixed by r337751. From owner-freebsd-current@freebsd.org Tue Aug 14 14:37:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5B2491079EDE for ; Tue, 14 Aug 2018 14:37:30 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CDA61720FC for ; Tue, 14 Aug 2018 14:37:29 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7EEbI4P099884 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 14 Aug 2018 17:37:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7EEbI4P099884 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7EEbIYK099883; Tue, 14 Aug 2018 17:37:18 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 14 Aug 2018 17:37:18 +0300 From: Konstantin Belousov To: Eric van Gyzen Cc: freebsd-current@freebsd.org Subject: Re: Make drm drivers use MTRR write-combine Message-ID: <20180814143718.GL2340@kib.kiev.ua> References: <3b53edb8-e1d2-109f-6ec7-81513c513433@vangyzen.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3b53edb8-e1d2-109f-6ec7-81513c513433@vangyzen.net> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 14:37:30 -0000 On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote: > On 8/14/18 4:12 AM, Johannes Lundberg wrote: > > Hi > > > > Something that we have seen for a long time on FreeBSD is the boot message > > > > Failed to add WC MTRR for [0xd0000000-0xdfffffff]: -22; performance may > > suffer > > > > Taking a closer look at this with memcontrol I can see that the 256 MB > > region that DRM wants to set as WC is already covered by this entry > > 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active > > > > Similar on both my Skylake and Broadwell systems. > I see something similar on my Dell XPS 13 with a Kaby Lake R: > > Failed to add WC MTRR for [0x90000000-0x9fffffff]: -22; performance may > suffer > > 0x80000000/0x80000000 BIOS uncacheable set-by-firmware active > > The only mappings in this range are MMIO: > > machdep.efi_map: > Type Physical Virtual #Pages Attr > [snip] > MemoryMappedIO 0000e0000000 0xe0000000 00010000 RUNTIME > MemoryMappedIO 0000fe000000 0xfe000000 00000011 UC RUNTIME > MemoryMappedIO 0000fec00000 0xfec00000 00000001 UC RUNTIME > MemoryMappedIO 0000fee00000 0xfee00000 00000001 UC WT WB WP RUNTIME > MemoryMappedIO 0000ff000000 0xff000000 00001000 UC WT WB WP RUNTIME Yes, the cause of the message is that current x86 mtrr code is not sufficient to handle this situation. You have BIOS-configured variable range MTRR which covers upper half of the low 4G, as uncacheable (UC). It is reasonable for BIOS to set it up this way because this is where PCIe BARs and other devices MMIO regions are located. One of the BARs there is the GPU aperture that really should be WC (write-combining). There are two ways to achieve this: split the UC variable-length MTRR range into three, UC/WC/UC, which would require three MTRRs to cover. This is what current x86_mem.c code does not support. Another way is to set WC mode in the page table entries (PTEs) using Page Attribute Table (PAT), for all PTEs. According to the rules of combination of the memory access types between MTRR and PAT, WC in PAT and any access mode in MTRR gives effective WC. I saw the same warning when I initially ported GEM. My code used WC PAT type, which makes the warning cosmetical, and which made me to not add MTRR split. If new drm driver also consistently uses WC memattr when creating aperture mappings, then the warning can be ignored as well. From owner-freebsd-current@freebsd.org Tue Aug 14 14:43:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97A49107A1B4 for ; Tue, 14 Aug 2018 14:43:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2CD1072647 for ; Tue, 14 Aug 2018 14:43:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22e.google.com with SMTP id s7-v6so18458242itb.4 for ; Tue, 14 Aug 2018 07:43:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:from:date:message-id:subject:to; bh=xpXAHMJo/VPBJx/Xjx2f4QmOnuNqhPkqFqPmC8cI334=; b=A9Qv9rhDZKzsi29SlVoQ+x8OVg4ykijeqDsrem/1X9FmSycrnSqh0RGMTBsHNb2c2a 9hKKPM92sdhCcZbknsOkqBl3W8g0DTWU93uTJ44867+BJ0v22/rNIkMZNuRR7EKlCrWd ZZSNjJ5Q1pzmn9OOlgs9NQX2xtvOtUq0N6QU8H/9iTgkO0nnD9evjctu6wSL95IQjRzD TSjJroNXXHvCNjDlHiTQYnK8suSX1cOoAoElOlOgz1LW5mQLbk3Xm7GvfoA3FpQ/lrMh 0lCYL5A1EcIugXgYxRrpGcSVSIHDl1JiTwC64pAl4CpwueYas1WBNZvXQX/rIX7S7Bjf 9B3w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:from:date:message-id:subject :to; bh=xpXAHMJo/VPBJx/Xjx2f4QmOnuNqhPkqFqPmC8cI334=; b=BdXaVvYAQP7R9I4Z6i8LyCffLS2ysl5hM3NoitakOVGPkO3j+dtpf+swNbVpu0hMTb 9GtCHbj1hdu6D9YjvHRtdXe4ferJQTpf2J8HsCEGUsufGQuooEax+w4E6v16gXyw5KHA Wx2wSrUw8cOmTNyMbtalRMSgJtZVC491r22wFn2GHnoVEnIU0VOMMdSiTUMrkHXbaH1O Goo8WymDQ/HcIlyE4QBwpaPKEzKoL39HV3w5B3aCwKQEAyKWM5ECN656dvZzw/mbUVGW Z6MoVjpTWCdp9VFXGeHVrD1fEOGDleDICeqmfLMObQNCTuqBf5iex6CLRwGMPSnroaDS y5Kw== X-Gm-Message-State: AOUpUlFZ1O1de9rYBG5uCW5R2T2qvt60q2MfnHpkMg0oyhtTGqDqmwDN VeBMf2rpuLV7D4bkEm3BQbuE1MeRNOTy0nPjIOP5afTnbmPTsA== X-Google-Smtp-Source: AA+uWPzlec/Bh2+gjCQH6QguG1zHfEqsssjU6HjWEOP8O2eAaFhDtgtt9iPw3VQdxyH6e7vAD685Fr+0l1dzYX9QMXs= X-Received: by 2002:a24:3ec3:: with SMTP id s186-v6mr14695373its.73.1534257810265; Tue, 14 Aug 2018 07:43:30 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:381a:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 07:43:29 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] From: Warner Losh Date: Tue, 14 Aug 2018 08:43:29 -0600 X-Google-Sender-Auth: fHihkZGUxPW8YraSOrVIrjQZ6Kc Message-ID: Subject: Mergemaster tweak To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 14:43:31 -0000 I never have /usr/src on my system (other than the directory that mtree creates). So when I run mergemaster it's always failing until I remember to add the -m . (or was it -t ., I sometimes forget). Given the recent ntpd stuff, I was annoyed enough with this default behavior to create a fix for it, which I've uploaded to https://reviews.freebsd.org/D16709 for review. Basically, if the proposed SOURCEDIR doesn't have a Makefile.inc1, but . does, then it prompts to use that. If it can't find one, it errors out early as a nice side effect. Please comment on the review. Thanks! Warner From owner-freebsd-current@freebsd.org Tue Aug 14 16:04:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FEC1107C7F0 for ; Tue, 14 Aug 2018 16:04:59 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2083576CA1 for ; Tue, 14 Aug 2018 16:04:58 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [10.101.2.76] (unknown [176.12.107.132]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 08B12721BBD15 for ; Tue, 14 Aug 2018 18:04:55 +0200 (CEST) From: Michael Tuexen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Panic in efi_get_time() on EPCY system when booting Message-Id: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> Date: Tue, 14 Aug 2018 18:04:53 +0200 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.9.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 16:05:00 -0000 Dear all, r337761 panics on boot with a GENERIC kernel on a EPYC system: Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights = reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-ALPHA1 #3 r337761: Tue Aug 14 17:59:05 CEST 2018 tuexen@epyc.nplab.de:/usr/home/tuexen/head/sys/amd64/compile/TCP = amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on = LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 1024x768 CPU: AMD EPYC 7551P 32-Core Processor (2000.05-MHz = K8-class CPU) Origin=3D"AuthenticAMD" Id=3D0x800f12 Family=3D0x17 Model=3D0x1 = Stepping=3D2 = Features=3D0x178bfbff = Features2=3D0x7ed8320b AMD Features=3D0x2e500800 AMD = Features2=3D0x35c233ff Structured Extended = Features=3D0x209c01a9 XSAVE Features=3D0xf AMD Extended Feature Extensions ID = EBX=3D0x1007 SVM: NP,NRIP,VClean,AFlush,DAssist,NAsids=3D32768 TSC: P-state invariant, performance statistics real memory =3D 137438953472 (131072 MB) avail memory =3D 133661786112 (127469 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: < > FreeBSD/SMP: Multiprocessor System Detected: 64 CPUs FreeBSD/SMP: 1 package(s) x 4 groups x 2 cache groups x 4 core(s) x 2 = hardware threads random: unblocking device. ioapic0: Changing APIC ID to 128 ioapic1: Changing APIC ID to 129 ioapic2: Changing APIC ID to 130 ioapic3: Changing APIC ID to 131 ioapic4: Changing APIC ID to 132 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-55 on motherboard ioapic2 irqs 56-87 on motherboard ioapic3 irqs 88-119 on motherboard ioapic4 irqs 120-151 on motherboard Launching APs: 14 6 52 16 28 44 42 36 20 13 37 4 54 15 21 5 55 18 30 8 = 26 9 29 58 53 10 56 38 31 11 49 46 22 48 43 12 35 45 41 23 39 51 32 24 = 27 61 63 33 1 62 60 7 59 40 34 47 2 3 17 19 50 25 57 Timecounter "TSC" frequency 2000054700 Hz quality 1000 random: entropy device external interface netmap: loaded module [ath_hal] loaded module_register_init: MOD_LOAD (vesa, 0xffffffff81126100, 0) error 19 kbd1 at kbdmux0 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 panic: mutex pmap not owned at ../../../amd64/amd64/efirt_machdep.c:268 cpuid =3D 60 time =3D 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame = 0xffffffff826ce810 vpanic() at vpanic+0x1a3/frame 0xffffffff826ce870 panic() at panic+0x43/frame 0xffffffff826ce8d0 __mtx_assert() at __mtx_assert+0xb4/frame 0xffffffff826ce8e0 efi_arch_enter() at efi_arch_enter+0x30/frame 0xffffffff826ce910 efi_get_time() at efi_get_time+0xbd/frame 0xffffffff826ce960 efirtc_probe() at efirtc_probe+0x17/frame 0xffffffff826ce990 device_probe_child() at device_probe_child+0x164/frame = 0xffffffff826ce9f0 device_probe() at device_probe+0x98/frame 0xffffffff826cea20 device_probe_and_attach() at device_probe_and_attach+0x32/frame = 0xffffffff826cea50 bus_generic_attach() at bus_generic_attach+0x18/frame 0xffffffff826cea70 device_attach() at device_attach+0x3f3/frame 0xffffffff826ceab0 device_probe_and_attach() at device_probe_and_attach+0x71/frame = 0xffffffff826ceae0 bus_generic_new_pass() at bus_generic_new_pass+0xdd/frame = 0xffffffff826ceb10 bus_set_pass() at bus_set_pass+0x8c/frame 0xffffffff826ceb40 configure() at configure+0x9/frame 0xffffffff826ceb50 mi_startup() at mi_startup+0x118/frame 0xffffffff826ceb70 btext() at btext+0x2c KDB: enter: panic [ thread pid 0 tid 100000 ] Stopped at kdb_enter+0x3b: movq $0,kdb_why db>=20 Any idea what is wrong? Best regards Michael From owner-freebsd-current@freebsd.org Tue Aug 14 16:09:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C8F0107CA1E for ; Tue, 14 Aug 2018 16:09:15 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C652076F08; Tue, 14 Aug 2018 16:09:14 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 8C8F7BFCBB; Tue, 14 Aug 2018 10:09:02 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id b0QphIEnS0zB; Tue, 14 Aug 2018 10:09:01 -0600 (MDT) Received: from Rebeccas-iPhone.mail (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Tue, 14 Aug 2018 10:09:01 -0600 (MDT) Date: Tue, 14 Aug 2018 10:06:42 -0600 From: Rebecca Cran To: Michael Tuexen Cc: freebsd-current@freebsd.org Message-ID: In-Reply-To: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> References: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> Subject: Re: Panic in efi_get_time() on EPCY system when booting X-Mailer: Airmail iOS (362) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 16:09:15 -0000 This also happens on Qemu with UE=46I. =E2=80=94 =20 Rebecca (Apologies for top posting, I=E2=80=99m replying on my phone) On August 14, 2018 at 10:04:53 AM, Michael Tuexen (tuexen=40freebsd.org(m= ailto:tuexen=40freebsd.org)) wrote: > Dear all, > =20 > r337761 panics on boot with a GENERIC kernel on a EPYC system: > =20 > Copyright (c) 1992-2018 The =46reeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 199= 4 > The Regents of the University of California. All rights reserved. > =46reeBSD is a registered trademark of The =46reeBSD =46oundation. > =46reeBSD 12.0-ALPHA1 =233 r337761: Tue Aug 14 17:59:05 CEST 2018 > tuexen=40epyc.nplab.de:/usr/home/tuexen/head/sys/amd64/compile/TCP amd6= 4 > =46reeBSD clang version 6.0.1 (tags/RELEASE=5F601/final 335540) (based = on LLVM 6.0.1) > WARNING: WITNESS option enabled, expect reduced performance. > VT(efifb): resolution 1024x768 > CPU: AMD EPYC 7551P 32-Core Processor (2000.05-MHz K8-class CPU) > Origin=3D=22AuthenticAMD=22 Id=3D0x800f12 =46amily=3D0x17 Model=3D0x1 S= tepping=3D2 > =46eatures=3D0x178bfbff<=46PU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,M= TRR,PGE,MCA,CMOV,PAT,PSE36,CL=46LUSH,MMX,=46XSR,SSE,SSE2,HTT> > =46eatures2=3D0x7ed8320b > AMD =46eatures=3D0x2e500800 > AMD =46eatures2=3D0x35c233ff > Structured Extended =46eatures=3D0x209c01a9<=46SGSBASE,BMI1,AVX2,SMEP,B= MI2,RDSEED,ADX,SMAP,CL=46LUSHOPT,SHA> > XSAVE =46eatures=3D0xf > AMD Extended =46eature Extensions ID EBX=3D0x1007 > SVM: NP,NRIP,VClean,A=46lush,DAssist,NAsids=3D32768 > TSC: P-state invariant, performance statistics > real memory =3D 137438953472 (131072 MB) > avail memory =3D 133661786112 (127469 MB) > Event timer =22LAPIC=22 quality 600 > ACPI APIC Table: < > > =46reeBSD/SMP: Multiprocessor System Detected: 64 CPUs > =46reeBSD/SMP: 1 package(s) x 4 groups x 2 cache groups x 4 core(s) x 2= hardware threads > random: unblocking device. > ioapic0: Changing APIC ID to 128 > ioapic1: Changing APIC ID to 129 > ioapic2: Changing APIC ID to 130 > ioapic3: Changing APIC ID to 131 > ioapic4: Changing APIC ID to 132 > ioapic0 irqs 0-23 on motherboard > ioapic1 irqs 24-55 on motherboard > ioapic2 irqs 56-87 on motherboard > ioapic3 irqs 88-119 on motherboard > ioapic4 irqs 120-151 on motherboard > Launching APs: 14 6 52 16 28 44 42 36 20 13 37 4 54 15 21 5 55 18 30 8 = 26 9 29 58 53 10 56 38 31 11 49 46 22 48 43 12 35 45 41 23 39 51 32 24 27= 61 63 33 1 62 60 7 59 40 34 47 2 3 17 19 50 25 57 > Timecounter =22TSC=22 frequency 2000054700 Hz quality 1000 > random: entropy device external interface > netmap: loaded module > =5Bath=5Fhal=5D loaded > module=5Fregister=5Finit: MOD=5FLOAD (vesa, 0xffffffff81126100, 0) erro= r 19 > kbd1 at kbdmux0 > random: registering fast source Intel Secure Key RNG > random: fast provider: =22Intel Secure Key RNG=22 > nexus0 > panic: mutex pmap not owned at ../../../amd64/amd64/efirt=5Fmachdep.c:2= 68 > cpuid =3D 60 > time =3D 1 > KDB: stack backtrace: > db=5Ftrace=5Fself=5Fwrapper() at db=5Ftrace=5Fself=5Fwrapper+0x2b/frame= 0xffffffff826ce810 > vpanic() at vpanic+0x1a3/frame 0xffffffff826ce870 > panic() at panic+0x43/frame 0xffffffff826ce8d0 > =5F=5Fmtx=5Fassert() at =5F=5Fmtx=5Fassert+0xb4/frame 0xffffffff826ce8e= 0 > efi=5Farch=5Fenter() at efi=5Farch=5Fenter+0x30/frame 0xffffffff826ce91= 0 > efi=5Fget=5Ftime() at efi=5Fget=5Ftime+0xbd/frame 0xffffffff826ce960 > efirtc=5Fprobe() at efirtc=5Fprobe+0x17/frame 0xffffffff826ce990 > device=5Fprobe=5Fchild() at device=5Fprobe=5Fchild+0x164/frame 0xffffff= ff826ce9f0 > device=5Fprobe() at device=5Fprobe+0x98/frame 0xffffffff826cea20 > device=5Fprobe=5Fand=5Fattach() at device=5Fprobe=5Fand=5Fattach+0x32/f= rame 0xffffffff826cea50 > bus=5Fgeneric=5Fattach() at bus=5Fgeneric=5Fattach+0x18/frame 0xfffffff= f826cea70 > device=5Fattach() at device=5Fattach+0x3f3/frame 0xffffffff826ceab0 > device=5Fprobe=5Fand=5Fattach() at device=5Fprobe=5Fand=5Fattach+0x71/f= rame 0xffffffff826ceae0 > bus=5Fgeneric=5Fnew=5Fpass() at bus=5Fgeneric=5Fnew=5Fpass+0xdd/frame 0= xffffffff826ceb10 > bus=5Fset=5Fpass() at bus=5Fset=5Fpass+0x8c/frame 0xffffffff826ceb40 > configure() at configure+0x9/frame 0xffffffff826ceb50 > mi=5Fstartup() at mi=5Fstartup+0x118/frame 0xffffffff826ceb70 > btext() at btext+0x2c > KDB: enter: panic > =5B thread pid 0 tid 100000 =5D > Stopped at kdb=5Fenter+0x3b: movq =240,kdb=5Fwhy > db> > =20 > Any idea what is wrong=3F > =20 > Best regards > Michael > =20 > =20 > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > freebsd-current=40freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to =22freebsd-current-unsubscribe=40freeb= sd.org=22 From owner-freebsd-current@freebsd.org Tue Aug 14 16:10:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 22497107CA79 for ; Tue, 14 Aug 2018 16:10:01 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA77377029; Tue, 14 Aug 2018 16:10:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 68EF0C73F; Tue, 14 Aug 2018 16:10:00 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f177.google.com with SMTP id q127-v6so15765060ljq.11; Tue, 14 Aug 2018 09:10:00 -0700 (PDT) X-Gm-Message-State: AOUpUlFVHPt53QJ/UtfwCW3+hn+orXbmu1GpGSsBvIjzmhYXtzAU7KFg zmfUxjPFo4nA8PtXlGyK4OENUf+bflffLkszIcM= X-Google-Smtp-Source: AA+uWPzEDkD9br6O5iAKojx0T0K/eJRhE/UNXeHXJKHl5DYOhEXFMED0+3yH9VYdA+XVHFuGME2IU7ZwRy92NsNyMa0= X-Received: by 2002:a2e:2b0e:: with SMTP id q14-v6mr15192146lje.147.1534262998887; Tue, 14 Aug 2018 09:09:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 09:09:38 -0700 (PDT) In-Reply-To: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> References: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> From: Kyle Evans Date: Tue, 14 Aug 2018 11:09:38 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Panic in efi_get_time() on EPCY system when booting To: Michael Tuexen Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 16:10:01 -0000 On Tue, Aug 14, 2018 at 11:04 AM, Michael Tuexen wrote: > Dear all, > > r337761 panics on boot with a GENERIC kernel on a EPYC system: Oy. =( > [...] > panic: mutex pmap not owned at ../../../amd64/amd64/efirt_machdep.c:268 > [...] > > Any idea what is wrong? > Ah, this should be fixed by https://reviews.freebsd.org/D16618 -- immediate workaround is set efi.rt.disabled=1 in loader.conf(5) or at loader prompt. Apologies for the hassle. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Tue Aug 14 16:28:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71F15107D5BF for ; Tue, 14 Aug 2018 16:28:22 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from drew.franken.de (mail-n.franken.de [193.175.24.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.franken.de", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 11CC278522; Tue, 14 Aug 2018 16:28:21 +0000 (UTC) (envelope-from tuexen@freebsd.org) Received: from [10.101.2.76] (unknown [176.12.107.132]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id 60044721BBD15; Tue, 14 Aug 2018 18:28:19 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Panic in efi_get_time() on EPCY system when booting From: Michael Tuexen In-Reply-To: Date: Tue, 14 Aug 2018 17:28:17 +0100 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <697FCAD9-6295-4F84-8B3E-269255520844@freebsd.org> To: Kyle Evans X-Mailer: Apple Mail (2.3445.9.1) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=disabled version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail-n.franken.de X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 16:28:22 -0000 > On 14. Aug 2018, at 17:09, Kyle Evans wrote: >=20 > On Tue, Aug 14, 2018 at 11:04 AM, Michael Tuexen = wrote: >> Dear all, >>=20 >> r337761 panics on boot with a GENERIC kernel on a EPYC system: >=20 > Oy. =3D( >=20 >> [...] >> panic: mutex pmap not owned at = ../../../amd64/amd64/efirt_machdep.c:268 >> [...] >>=20 >> Any idea what is wrong? >>=20 >=20 > Ah, this should be fixed by https://reviews.freebsd.org/D16618 -- > immediate workaround is set efi.rt.disabled=3D1 in loader.conf(5) or = at > loader prompt. Apologies for the hassle. Hi Kyle, I can confirm that r337761 + D16618 boots fine. Thanks for the quick response! Best regards Michael >=20 > Thanks, >=20 > Kyle Evans From owner-freebsd-current@freebsd.org Tue Aug 14 19:30:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05F17105582F for ; Tue, 14 Aug 2018 19:30:11 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70E2083B53 for ; Tue, 14 Aug 2018 19:30:10 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pf1-x42c.google.com with SMTP id k19-v6so9702535pfi.1 for ; Tue, 14 Aug 2018 12:30:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=XbWP14XG0K1PIQfwLDS8ghB0M8U9hrDdPQW7DjN2oi0=; b=QsccPVHTTIuOQQIRNPSx5JzOPqkVKiIl0yfCBmuK+L/z2azQNqi1EXQZCmWY/gS4Gg fV58XiXI24xlRaqqt0TZ7Bp3cXBY+1728EKtizs/6HgkDSa2tyvFhd0931f3/pJi33xD aT5/tx9U3xWS1MZLp22gqPa5EzCYcIdnrKfs/o6O+HdiqNGH/t7xKRUPDojN3eT1mxan xMS9d/cey/xxSFPebI5r++tV81rg5z7D2AQvHVWFVnvAXgA+emRY5s/QlLjUQ+p6Gw7g 406gi3AlsCwY4QmNn1lVSe+OzaKVtfsP8IEcW1PZbIBaPo/XkDKOfoEgc6gaAu5GB0hy nALQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:openpgp :autocrypt:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=XbWP14XG0K1PIQfwLDS8ghB0M8U9hrDdPQW7DjN2oi0=; b=p4ZV7jWO13FxXlx0ywpHpgtFGFjYzzi4mJXljE8qBv4aEbwH6JylxKgxQtsMMv0vco TFGTcQbK8+XXig1lHWRRj62VLAepMoniSpgoziJXfr6JqxNmYCtnGmi7Bc9sfyXLmmLe /IMb6ZoFY/zlnPcg3DuHsWCUZeAgy/aMSJvlMFPReNvaZbfuUoDR4+NrT7m4MI7bZ/Gs /iwr9E7Y9umEFZWWVPjc7QcUWLZWswXCCDleJODxXrkN/oCiMSt7An5WrsBx1MpUUJPM /Wt/SxHjg0sLAuQ8Y4BHGtgWwHkHxuP6f63BNJSbLX9jc1gN8iJGLr+PRg3dzJeRjdYX gQKQ== X-Gm-Message-State: AOUpUlHb1AhdrmRgIdSgq27q9iUytRL9xzmDQ17i+x6GaRMJ6tPEL6yA LiWLg0nPz+Z6auetG7PGe7rIxk/O X-Google-Smtp-Source: AA+uWPx6HEyNz41rS9e2x1Z1AdCrNOgghMD6Llks4cCDB+faaOetB011ZJl7Wi+3AkWKR/8TKn6eAQ== X-Received: by 2002:a63:f18:: with SMTP id e24-v6mr22509382pgl.320.1534275009246; Tue, 14 Aug 2018 12:30:09 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id x184-v6sm26485272pfd.169.2018.08.14.12.30.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Aug 2018 12:30:08 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: TCP server app performance To: Honda Michio , freebsd-current@freebsd.org References: From: Navdeep Parhar Openpgp: preference=signencrypt Autocrypt: addr=np@FreeBSD.org; prefer-encrypt=mutual; keydata= xsDiBEosaGcRBACOXnXquGEW53BjpMt2jViod/TUf1xgjMekcbDxqOODPeX7eYfrwJ8G6BCN OpGjBmWDu/JcNj4Z+gmTilJ6WLZQ7ecFZfEeO91pt6ys0cyWh0xfO+/mT83D7W81S/kqrJBk QbBIdV6LumevdErHo272r8RcMELC4Ru87eRtX3hmEwCgnnGNJMpQFUfYTt5XE7nY0yQoeV8D /0OcWmJbEZWxX9O7AuliCe3zd2Dw0B4LB9SZ2Dis7+gpVd3xVgYnt5wRE9kM+ThgrMA/wqr8 07qmEG6bcfUsfwwGN9YUtNF3xAN07cXTs026sCIFNZK816PrThBzCgkwR7pDpkMzGWIBr8Wi XXy0eB+JlQ6UV4PEiXuZ5ulzP0b1A/9CZm3wJfrNC0r1gMyrfVedg4zwKU997bmPLGcYs+rW XDTI9CvMseOUYn4CoDZQCp/9zxuHK+VU7Y/w0c/hVE5ERACSn4SjN2unEDstK9njZBMHEPVk Ae/YvSG5cmc97SHlVE+eu/bbLKcvFb6rRLPOaVFQJMJA2VJEGWtYhvP7Zc0fTmF2ZGVlcCBQ YXJoYXIgPG5wQEZyZWVCU0Qub3JnPsJgBBMRAgAgBQJKLGhnAhsDBgsJCAcDAgQVAggDBBYC AwECHgECF4AACgkQyrIrk6yriBL0MQCfUJOiS2PbJFDeiav1ylcXXwfpggAAoJRoS7GDENGy M4BzjJ4b0ptZqTLRzsFNBEosaGcQCACFCWs47SL4DQA6bNDlVJu4w8wLf8uVOyatuGmdXX8Y /OTVQJgA3vS+ODNVJCxhKVlvhcn7bhBdGdWKS9K+lr8+eEvr4hf2bQpesoHC+uFgKyILkCBN L8raixbhysyq0pfZWWDJMyn+G42BG1yJJi+bykygdpYnbIVA8dYHmBibI8mkPKOHSohjXT1S RfGGn+l1w54OO4NlJhCXMkjTA/Z9Bt4XeaiR85uJi0UUfV8FGZHhgSvT+/P1xIvz+nytuehS P/QLXl13CtAG/nKVkAcZnsT/3NrJ4Z2r45k+c50Wrf210scAaBogrrV5eIHfNGgOANApN8+8 vj+aXO4pXRuXAAMFB/44ea8rd+P5N3OMrfuM8i91Qe1bJ+BIoroKPOr8jvCry0h3QpdfLKUN IgaqbS3JZeBJ8HHnWSGCF+o6H5gzRe1hvylPEclLPDCuPe7T746h9Mzejf2hNDJvOg+BuweD ZW4KhovVbdS+syJEvpGF4bO8qgHT2CKgruXSHbFetdQWbkM0rfMmTuo0GcR2BEVrPb/SPFv6 4ZZyAZzmnGO4vT1bzClnTzJixrDpH74M3vSEYegMB4KdbLYBi8Jx4QUKgVEhJHjJubKWX4et yU/uuehOC3xYrmr1UXvsom3U8r36Dvdo77Yr3dgDVXa7bolNx0TIhdWxZI+R4z9E75QY+/wg wkkEGBECAAkFAkosaGcCGwwACgkQyrIrk6yriBI+JQCfUxgyqGtzZvLh5Al7gsTmRc11PLwA niD3NfWGRcO2+9uxSSQqRH1ywC4n Message-ID: Date: Tue, 14 Aug 2018 12:30:07 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 19:30:11 -0000 On 8/12/18 9:50 AM, Honda Michio wrote: > Hi, > > I'm measuring TCP server app performance using my toy web server. > It just accept TCP connections and responds back HTTP OK to the clients. > It monitors sockets using kqueue, and processes each ready descriptor using > a pair of read() and write(). (in more detail, it's > https://github.com/micchie/netmap/tree/paste/apps/phttpd) > > Using 100 persistent TCP connections (the client sends 44 B HTTP GET and > the server responds with 151 B of HTTP OK) and a single CPU core, I only > get 152K requests per second, which is 2.5x slower than Linux that runs the > same app (except that it uses epoll instead of kqueue). > I cannot justify this by myself. Does anybody has some intuition about how > much FreeBSD would get with such workloads? > I tried disabling TCP delayed ack and changing interrupt rates, but no > significant difference was observed. > > I use FreeBSD-CURRENT with GENERIC-NODEBUG (git commit hash: 3015145c3aa4b). > For hardware, the server has Xeon Silver 4110 and Intel X540 NIC (activate > only a single queue as I test with a single CPU core). All the offloadings > are disabled. I hope hw L3/L4 checksumming is still on? Are your results similar to what you get with 100 (same number as your test clients) netperf's doing TCP_RR on this setup, or wildly different? Regards, Navdeep From owner-freebsd-current@freebsd.org Tue Aug 14 19:37:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 106F41055CAA for ; Tue, 14 Aug 2018 19:37:27 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 97AA98411F for ; Tue, 14 Aug 2018 19:37:26 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 064EC21957 for ; Tue, 14 Aug 2018 15:37:26 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 14 Aug 2018 15:37:26 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=iZQBO65w7daa03C5a+oWQ3532LKnjYa9uZpmfUk+OCs=; b=h499Tafi RBh4A7EaezgU/MfJxhaWD8hKHckXB9hzohbi8b8D59y1EySIf7jcokWvd3VnNOg5 +ja7wAyhLl30yH1Uy+42de9Dad5F9Gq5E4WoI2x08BTByYZdcBJ/nfjMP5g/FYHI odGSfIeMARm9iw7DeQKtqXPyZ4HHRCblbj6KOM6q3EdV2bouG/ZNeYPdE511YiKT dT8cy4BXw+GIciJB7i74NcGx2yJGZTM+e3mySagLT8xzbdn7ZlzdaPMFlNdQNRaA PNoVYfm1OFz0Mta3dNubsf0C6rLH4RMr0tlh2gBt0P4ONMiPzk3AFOWAUcADGAiJ AH/pri2iQsP6Sg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=iZQBO65w7daa03C5a+oWQ3532LKnj Ya9uZpmfUk+OCs=; b=W34UZnHZuzx2tWExc+7dnSCQ3/EFOouQ1QrtOr9RCyxgV vFyxvDZGKqmQyCVqc6cP+TE6m0tnKJ6mkL+8OByS1gnHaxpu6VUYcIaB/yfJx5TZ QQT2rTeTJJah/DupSAYeoswExPHvG2TUbm10KfkKSx2IA2fVMqe4YYz8X1ue0Z/1 oTwpSKqV4eCSfqssBpsJ0sMp1oSmcb7kE83WIN3eXTY28uIYTnnVIZMPhM3Ey9a4 9zAKZQDsT6XBSapIB3Jtmvas4yjfFD5jNjMcZcAsZ0sLfwRymhez6ew8S3utt+OM kG0h7Pj+pQZghmlCqTE7d5WYB7moHtn3mdWqg///g== X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 746BE10261 for ; Tue, 14 Aug 2018 15:37:25 -0400 (EDT) To: freebsd-current@freebsd.org From: tech-lists Subject: boot errors since upgrading to 12-current Organization: none Message-ID: Date: Tue, 14 Aug 2018 20:37:24 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 19:37:27 -0000 Hello, context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is *not* root-on-zfs. It boots to an SSD. The three disks indicated below are spinning rust. NAME STATE READ WRITE CKSUM storage ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 0 0 This machine was running 11.2 up until about a month ago. Recently I've seen this flash up on the screen before getting to the beastie screen: BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 [the above is normal and has always has been seen on every boot] read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 the above has been happening since upgrading to -current a month ago ZFS: i/o error - all block copies unavailable ZFS: can't read MOS of pool storage the above is alarming and has been happening for the past couple of days, since upgrading to r337682 on the 12th August. The beastie screen then loads and it boots normally. Should I be concerned? Is the output indicative of a problem? thanks, -- J. From owner-freebsd-current@freebsd.org Tue Aug 14 19:56:02 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0193B1058A8F for ; Tue, 14 Aug 2018 19:56:02 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yw1-xc2c.google.com (mail-yw1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 911B9850FC for ; Tue, 14 Aug 2018 19:56:01 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yw1-xc2c.google.com with SMTP id 139-v6so17129752ywg.12 for ; Tue, 14 Aug 2018 12:56:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=Akiu2qTCLBpDMyKMGsHz99+20TN4XTsGF7ARJrUhnwg=; b=JtkWVKnwlV2QAH442kzwhD8nwpIVUAFVQAzFmofyQJlbx20Y+AlkH6kORFApvizKM0 Bvjblyb9yvY+ML0IulpOewoh9HShHdpANzRRomhbjAVXlT9FNrV7iII3kjhMTxSzHlfj z7hpoSExXxStkyXrPbhSePIRui5ua8AiEe5obKkIz4qOvyRf8Mgmdm0o2Et0l+/baW1I CPvlpKGtST6shS553jtbo6sCZ33vET+tHOjB9SLqKuPGj7UUWnA3W4MGBiUsRzx4sBya YDXGbB9O9kotxyyB0Tx8+mmyi7Ao/yp5J5DE5FHNNl/Y3jKwAoMsvKk7QBuZ2XozvzWm I+2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=Akiu2qTCLBpDMyKMGsHz99+20TN4XTsGF7ARJrUhnwg=; b=aoqlQ3oOSUHWwXS7NVTCAFV3ru41s+VJtuLTjFMmxuARiwMfXI75i5imUEbrZtY0f7 TzTwQVOZb0NvFjgQcE3h+xJaVQd/xMD2lPznRG+s8rgA4feFe2gZQW35HdzmIn2Zs7jT xzB+uFn9ACxN8gDomJ4QraxmcbSSinSfMqQimeACySuwy84kTPseyoAM2VX6LjM/JWSn SBxdWYE5r4qnuLrq4z4m8GSTMQGxpRUUK89/ukry/9Aj8PGhu8WiDplTpDfvblp6h689 b/mO3RdBilbH0C8/2nny3LhEJElsaMst2/AWAWGf9VqJaevvoppAIKZ8JSUpxaAOC24X axMQ== X-Gm-Message-State: AOUpUlHaP1gmFHzr2cWEY/ALGSieHGdce+gOe3YsJ6sAvgiyRFuEPYWi KT/vAgkklpI6C5OzytscFlbvut5lXaIMhOIQUtzrDw== X-Google-Smtp-Source: AA+uWPzCuhIUS73VJmuzRQlL6ES2qra518EN1oOLQ076fiSozwfjRZy6JSVCpZ9OS9TEUTjTR29BS+FsEvXuBVTMlso= X-Received: by 2002:a0d:df47:: with SMTP id i68-v6mr12194140ywe.337.1534276560621; Tue, 14 Aug 2018 12:56:00 -0700 (PDT) MIME-Version: 1.0 From: Matthias Gamsjager Date: Tue, 14 Aug 2018 21:55:32 +0200 Message-ID: Subject: Restart at boot with new kernel To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 19:56:02 -0000 Hi list, just compiled current and after reboot into the new kernel the machine reboots itself at the marked line below. No further info as the reset is sudden. Reboot with the old kernel from 12 aug works. Removed all kernel modules but with no result. Any pointers how to approach this? Aug 14 21:35:19 workstation kernel: ---<>--- Aug 14 21:35:19 workstation kernel: Copyright (c) 1992-2018 The FreeBSD Project. Aug 14 21:35:19 workstation kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Aug 14 21:35:19 workstation kernel: The Regents of the University of California. All rights reserved. Aug 14 21:35:19 workstation kernel: FreeBSD is a registered trademark of The FreeBSD Foundation. Aug 14 21:35:19 workstation kernel: FreeBSD 12.0-ALPHA1 #9 8501082ee8a(master): Tue Aug 14 21:13:15 CEST 2018 Aug 14 21:35:19 workstation kernel: root@workstation:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 Aug 14 21:35:19 workstation kernel: FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) Aug 14 21:35:19 workstation kernel: VT(efifb): resolution 1024x768 Aug 14 21:35:19 workstation kernel: CPU: Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz (3410.09-MHz K8-class CPU) Aug 14 21:35:19 workstation kernel: Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 Aug 14 21:35:19 workstation kernel: Features=0xbfebfbff Aug 14 21:35:19 workstation kernel: Features2=0x1f9ae3bf Aug 14 21:35:19 workstation kernel: AMD Features=0x28100800 Aug 14 21:35:19 workstation kernel: AMD Features2=0x1 Aug 14 21:35:19 workstation kernel: XSAVE Features=0x1 Aug 14 21:35:19 workstation kernel: VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID Aug 14 21:35:19 workstation kernel: TSC: P-state invariant, performance statistics Aug 14 21:35:19 workstation kernel: real memory = 34359738368 (32768 MB) Aug 14 21:35:19 workstation kernel: avail memory = 33333342208 (31789 MB) Aug 14 21:35:19 workstation kernel: Event timer "LAPIC" quality 600 Aug 14 21:35:19 workstation kernel: ACPI APIC Table: Aug 14 21:35:19 workstation kernel: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs Aug 14 21:35:19 workstation kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 hardware threads Aug 14 21:35:19 workstation kernel: random: unblocking device. Aug 14 21:35:19 workstation kernel: ioapic0 irqs 0-23 on motherboard >> REBOOT Aug 14 21:35:19 workstation kernel: Launching APs: 1 7 3 6 4 5 ---<>--- Aug 14 21:35:19 workstation kernel: Copyright (c) 1992-2018 The FreeBSD Project........ From owner-freebsd-current@freebsd.org Tue Aug 14 20:00:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 534E41058DBB for ; Tue, 14 Aug 2018 20:00:38 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yw1-xc30.google.com (mail-yw1-xc30.google.com [IPv6:2607:f8b0:4864:20::c30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E076685493 for ; Tue, 14 Aug 2018 20:00:37 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yw1-xc30.google.com with SMTP id 139-v6so17140565ywg.12 for ; Tue, 14 Aug 2018 13:00:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pS0AfRcIy8WhjiqnAp404W+YNZirID1y0B6mVwhGKiQ=; b=Xhr5GAHVTeVPxonsPuEYv+nTcJa2yazqtR1aKO+kmNM69ez+dYf0e4y7Z8jxlsbZNb E91kFn5kdkrH91T62BPE2QZ3J2E/s1JF22FJPwWZYaa77vAwHrhNt25eqZCtVoOvZD9E sMR2raTWG50bKxT7QERaUgzN0oRFelacASclw6tHFIGR5+6kasswVSnL0W2tduZW3SEs 60D5yQe54+vJGPJ03XLzAoOUWKYqyNv2h06piAlR0/SQTmpLLGuKsbIGtHndHUg7HGGt 9PCbyF5Mvx6szR6mYF+bYgZfKNNzBcGCwyu/IeSWbKqzWyF7IJB1C7CttCoWJQlu6/8Q F2ww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=pS0AfRcIy8WhjiqnAp404W+YNZirID1y0B6mVwhGKiQ=; b=K89X0I6BbPXMVr6UkUqS4IAf1B+h+GW+GU5n+5XNAHMnnsNcgLTsNFwsDa1v4bYq6W EOri2XVH1pSV3BvNo0Dzrrs/Q5mO+0p2Sw0fiAhzH0DAQBFaiaTn2YXeG06QmUhn5f3X aWmJsva9bHQN5AFZxk0Q1CfCM30GDWSZNNLsOKT1tH206HhxFlAlJ9xMMyLLWOP+Vpqj Ct3esJZyee4AfoyV46UAxEfCWHCiAjs2Vt2jJhOTp3vlWZypxQhJEDTTL1hOApixZDH/ Y6M6ZGYgplXGAi4qTOhNyvD1G+ccMJmMJhveXumkAhZLIAEeuW1ABBj4OfCYyTrrBxFi GgAg== X-Gm-Message-State: AOUpUlE3+O6ORdkXtJxRkeId2Fi3lkKq+gP3Vt2hPskyb7EW6MZew0BR ph/3xrJazhn8euwqeWM/LSJSl/ntb5EjFVAMzAEJNZsJ X-Google-Smtp-Source: AA+uWPwmrqEsYbJgH/4mnlYI4VTKFd9XfgY8Xesv2hqvWHNvU8OGymdpwXbmvNxDxKXzlnD3B7DmKIVgijHz+1wUijg= X-Received: by 2002:a81:6bc6:: with SMTP id g189-v6mr12884183ywc.267.1534276836046; Tue, 14 Aug 2018 13:00:36 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthias Gamsjager Date: Tue, 14 Aug 2018 22:00:10 +0200 Message-ID: Subject: Re: Restart at boot with new kernel To: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 20:00:38 -0000 Ok missed the solution posted earlier: adding ' efi.rt.disabled=1' to loader.conf fixed the issue for me as well From owner-freebsd-current@freebsd.org Tue Aug 14 20:11:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 70897105B5E1 for ; Tue, 14 Aug 2018 20:11:51 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw1-xc2b.google.com (mail-yw1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 135EA85F54 for ; Tue, 14 Aug 2018 20:11:50 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw1-xc2b.google.com with SMTP id 139-v6so17167388ywg.12 for ; Tue, 14 Aug 2018 13:11:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=s/ArawnPirt/cTJUA+gZDMifeWcIRXwnsN00rs2Udz0=; b=ksouCTKvKuLl1+0D00hA/UfAfgW8xM5V7c7HwgHFc9FuNsWAEpzv7ELewTCufqA/uT uG0HIIxoFSoc8h4fHP2GIBesIpwUqOQrdegriyfm80oXUrd4n/pJl2sJbNpxqqI1R1xq ggxte/y3xLGBHQ3RIxnFw6/6y3YPNOkaMxZTsF+8P6JrJD2yRw532anZddi0nC2bOL9K s5dC8SPUXy0kC/9JCXxHFLInanPAhca3DqVTZtmkU7ckIQH8RdCjSilZM8D9FBmN8V+M P7YlF7Dy/gaHAwrwuJhe8wAiLXGoUg/ZtSqXsafRpac/xrt7pxyPCPDeEqtUEgfVpE/V V/+g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=s/ArawnPirt/cTJUA+gZDMifeWcIRXwnsN00rs2Udz0=; b=eSaOzQ4KIMIZW3RsT3f8YrRHzmnQ5rDvKzYlLSYvNJD2HBe0Pc6FooWCRojYYiNlAV X3frdsfZispB/L7CLzzQqssJxFYfLCbY85WbSAMNSFhONEVmk8YBLbmaXmAWzyotvjDw SMNnabLVhlq9ThTI2esziivR4yM+rY5BTakjlCbtwtWlNnLo09sVH4XN9iaWBxqrFaGv fQdZKPAGkZjI2HS7s6wcd3dpid5KKbOLzTeX9TMU46iS4TulhN9FLnhoEDqj4iqp1gIx VNTIzrNrVub2uQxWRhfhn336985XnUakvAoHV9i2BKBhO+l0uTxXTJssWs1KbzLpDyOv lr2w== X-Gm-Message-State: AOUpUlEMTNeeLpMAiGGNQbgm/NbwWLzlFxXy81g1PpjKKzMwC1brHigT nUXlHN7n19l34WAlbhVaSpAU83JZdSoeSeMfKwJtyrvXw0M= X-Google-Smtp-Source: AA+uWPyJujAgxvdjagbOJLAZzCozqCFOkIZhMojSPdUMOAhI9lFrTczXi65TTyZTHoU/6dt6eAmZo4mWnu1/noboRFU= X-Received: by 2002:a81:4511:: with SMTP id s17-v6mr13376053ywa.104.1534277510329; Tue, 14 Aug 2018 13:11:50 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:f205:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 13:11:49 -0700 (PDT) In-Reply-To: References: From: Oliver Pinter Date: Tue, 14 Aug 2018 22:11:49 +0200 Message-ID: Subject: Re: Restart at boot with new kernel To: Matthias Gamsjager Cc: FreeBSD Current , kib@freebsd.org, kevans@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 20:11:51 -0000 On 8/14/18, Matthias Gamsjager wrote: > Hi list, > > just compiled current and after reboot into the new kernel the machine > reboots itself at the marked line below. No further info as the reset is > sudden. Reboot with the old kernel from 12 aug works. Removed all kernel > modules but with no result. > > Any pointers how to approach this? > > Aug 14 21:35:19 workstation kernel: ---<>--- > Aug 14 21:35:19 workstation kernel: Copyright (c) 1992-2018 The FreeBSD > Project. > Aug 14 21:35:19 workstation kernel: Copyright (c) 1979, 1980, 1983, 1986, > 1988, 1989, 1991, 1992, 1993, 1994 > Aug 14 21:35:19 workstation kernel: The Regents of the University of > California. All rights reserved. > Aug 14 21:35:19 workstation kernel: FreeBSD is a registered trademark of > The FreeBSD Foundation. > Aug 14 21:35:19 workstation kernel: FreeBSD 12.0-ALPHA1 #9 > 8501082ee8a(master): Tue Aug 14 21:13:15 CEST 2018 > Aug 14 21:35:19 workstation kernel: > root@workstation:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG > amd64 > Aug 14 21:35:19 workstation kernel: FreeBSD clang version 6.0.1 > (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) > Aug 14 21:35:19 workstation kernel: VT(efifb): resolution 1024x768 > Aug 14 21:35:19 workstation kernel: CPU: Intel(R) Core(TM) i7-2600K CPU @ > 3.40GHz (3410.09-MHz K8-class CPU) > Aug 14 21:35:19 workstation kernel: Origin="GenuineIntel" Id=0x206a7 > Family=0x6 Model=0x2a Stepping=7 > Aug 14 21:35:19 workstation kernel: > Features=0xbfebfbff > Aug 14 21:35:19 workstation kernel: > Features2=0x1f9ae3bf > Aug 14 21:35:19 workstation kernel: AMD > Features=0x28100800 > Aug 14 21:35:19 workstation kernel: AMD Features2=0x1 > Aug 14 21:35:19 workstation kernel: XSAVE Features=0x1 > Aug 14 21:35:19 workstation kernel: VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > Aug 14 21:35:19 workstation kernel: TSC: P-state invariant, performance > statistics > Aug 14 21:35:19 workstation kernel: real memory = 34359738368 (32768 MB) > Aug 14 21:35:19 workstation kernel: avail memory = 33333342208 (31789 MB) > Aug 14 21:35:19 workstation kernel: Event timer "LAPIC" quality 600 > Aug 14 21:35:19 workstation kernel: ACPI APIC Table: > Aug 14 21:35:19 workstation kernel: FreeBSD/SMP: Multiprocessor System > Detected: 8 CPUs > Aug 14 21:35:19 workstation kernel: FreeBSD/SMP: 1 package(s) x 4 core(s) x > 2 hardware threads > Aug 14 21:35:19 workstation kernel: random: unblocking device. > Aug 14 21:35:19 workstation kernel: ioapic0 irqs 0-23 on > motherboard >>> REBOOT Aug 14 21:35:19 workstation kernel: Launching APs: 1 7 3 6 4 5 > ---<>--- > Aug 14 21:35:19 workstation kernel: Copyright (c) 1992-2018 The FreeBSD > Project........ I observed the same with the MFC'd back r337773 to 11-STABLE. So CC kib@ and @kevans. My system is a Dell Latitude e5440 with EFI. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue Aug 14 20:14:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D965A105B701 for ; Tue, 14 Aug 2018 20:14:34 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 88F8B8622C for ; Tue, 14 Aug 2018 20:14:34 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 2679EE086 for ; Tue, 14 Aug 2018 20:14:34 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f52.google.com with SMTP id v22-v6so14688900lfe.8 for ; Tue, 14 Aug 2018 13:14:34 -0700 (PDT) X-Gm-Message-State: AOUpUlGL+dsBNTGDTSIpo1mbyCm/yd1xgEkPHNP7n+CGRtTp7IpdJeiO U84gaQNFkXnvBgKik06SyN7g4TmowG6/Eian+q4= X-Google-Smtp-Source: AA+uWPyBxYnJcrQYnwCMi1YlsRyWk1bZlPQi8e6OtTvEGKRYvp70MTAc9R3kkb12FpGsLHaYjzGg1N88aQ3jf3ivIyA= X-Received: by 2002:a19:1460:: with SMTP id k93-v6mr15180990lfi.15.1534277672753; Tue, 14 Aug 2018 13:14:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 13:14:12 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Tue, 14 Aug 2018 15:14:12 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Restart at boot with new kernel To: Matthias Gamsjager Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 20:14:35 -0000 On Tue, Aug 14, 2018 at 3:00 PM, Matthias Gamsjager wrote: > Ok missed the solution posted earlier: adding ' efi.rt.disabled=1' to > loader.conf fixed the issue for me as well Is your kernel up to r337773 yet? That should have addressed the EFIRT boot issue. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Tue Aug 14 20:21:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E3C34105BADA for ; Tue, 14 Aug 2018 20:21:07 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: from mail-yw1-xc2b.google.com (mail-yw1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 869B88674F for ; Tue, 14 Aug 2018 20:21:07 +0000 (UTC) (envelope-from mgamsjager@gmail.com) Received: by mail-yw1-xc2b.google.com with SMTP id s68-v6so17207126ywg.2 for ; Tue, 14 Aug 2018 13:21:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:cc; bh=tM6+jUSziymeTywISmEVN/6GLjdz7IzFn4+0RAzgL34=; b=pvWD8ficE9UJp8j9Kn0CcHyAt35PxV5CKet4rnISecLD3Mtk+X7zp+w1ivhkacX9tY x9NEs8vgohlb6O3B3OaxYnxToCatQjfh7KM7ODe5ER4BnHW/BLF4BEGpwuKvFyRzQiso Hi/1t+zOTPjuM63MO5b8zDvdR6KoI50+I/q5mexEpDf7fKcfPRXrWlMvOxhD1nzvwqWG 3p2VfB5NPsIvQ+J7CqBfUCmGOEmxfF4lZFpvZQFZ5dKyxr5ykvM4WOGkGOtNo8VBL5wf kGEwa6E5vPdVsm7tKQJryIJB3hgvEuweKa8FajOlPquFxFFJzUEw9CWMJGb2lJkJBFhW l7Fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:cc; bh=tM6+jUSziymeTywISmEVN/6GLjdz7IzFn4+0RAzgL34=; b=rwu+Tqk2YgjiyvhhEkELr1+1uzZHF5Sm+Zj01VwgIuYL7+FYoPRA/CRvx0rQUo3uFQ Qlj+Az8K7prUlrA/iuunqfDNc65Ip82T2V72G6/aOM95p65yYh/VIPxjiNwjPdQ+HpPv hwO+pU5LOGvGAzI9iptGXvgjXMSOw3zpdSjYjietz1NMozrdo95u7QSkoupgHBjxHaCd 97y4MJ+oWM316z0e8tEKSdY6CXZGAm6znoNvJtpZyASITtZksVm26capcw/RQe+G8s7y eRzB1He11/NE+96Vc8ivFJsLFWnZ0KtKVbLq+TsiMPDhSxtMD4w038KQr2dkkwwL0iSV eohA== X-Gm-Message-State: AOUpUlEP9yAkt9DofPlQm4VJ45OY5galjGK5uAEu7BinRBgpjpsd6Kah K07uXmbnb2N6ZcT4qQWGLtW+32RGi44VhOpDCIACQA== X-Google-Smtp-Source: AA+uWPz8WLLT/ENql9pYNYXAd5yl7Kv6QcqW9zO8SoHTBDP2quQbjj/Z3Opjul5BZujG1Zb9gds76cV0uUejT6BMmZg= X-Received: by 2002:a81:85c2:: with SMTP id v185-v6mr13385515ywf.425.1534278066992; Tue, 14 Aug 2018 13:21:06 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Matthias Gamsjager Date: Tue, 14 Aug 2018 22:20:40 +0200 Message-ID: Subject: Re: Restart at boot with new kernel Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 20:21:08 -0000 > Is your kernel up to r337773 yet? That should have addressed the EFIRT > boot issue. > > Rebuilding now. Not sure how late I started so I might have missed it. From owner-freebsd-current@freebsd.org Tue Aug 14 20:54:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6329F1061BDD for ; Tue, 14 Aug 2018 20:54:52 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3525889B6 for ; Tue, 14 Aug 2018 20:54:51 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x430.google.com with SMTP id v14-v6so18339224wro.5 for ; Tue, 14 Aug 2018 13:54:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=EqqL+NyTbbuhcKsV4jyJSPS9ojPwOhowI7SHxteVnVY=; b=VabCEeorqghnKrLvKdFHVAi58dF/NrMa1l2DusOuBSr0VWqpvzry2giCr8Y+eeTD/0 guJos1ClIYBSA2VRA2vcWERPvQ3NhXMbIjY2pSqViC+byJ911aLM2+FNa+9Buq+Aee9o 93JdJYRIoCcTvM4c8/atpgOAoYeNrXIRRJq02he1lhBiy7u9Lv2eiU8x60ZK4lAXkOfQ +HUPiXO8dfP87DHZJzEG8l+qVSLYe77hz0tswzVL9kpqGHxK7EiyZvTRCiJcZAERkULY NbqudI1NlLRfNd6tyQ7qEz9VOl8bxuwb6cvvYjtKJe15LwFRpJTr+CBpkjYlNCMBxQeb 3T+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=EqqL+NyTbbuhcKsV4jyJSPS9ojPwOhowI7SHxteVnVY=; b=drJDAVnMCOZuxMPU2e9Dz1kRcbw8aGc/0UnAGKzjUYd8cbQTDHYEt4dRu7Em3fbyK3 H5a227rK0RrALzrgq0vwIu9oiWYioe0q7V3z5UG49MITOZxnkvRz1nCJuj5kn22L0RX5 oL2izMXEk+JqXp7EeBBhMxkpKzart3UVX8DByiSKrMsGP8FjC/88qtFSOPpkxV0u1WrK mv0G7bki+v/z27w7GFwCm937LbCzCqQeqcLj5Az8CPSKEvJM1XVRMep1tY/1tXe/u6aJ YyKf/31Uh7zyyuoqXVJb+AAnpHb6kmhkJPHsroWYfFY/orcf3mbdwq5IHgfNHagrrtpT p8Lg== X-Gm-Message-State: AOUpUlG9K4XQdRSjYcvf0dPV6lPUzu9St4Aa5RBvBqTohYUjS/d9CR5S DWrARjg2rbeE6GK50n8oeBa1rwcCmZHxB9R7YJs= X-Google-Smtp-Source: AA+uWPz7nvFDETxiMkxopKaUijynbKmPOJ4B7EUBojYfkKAonS/T3xJOINbCoqtSLut+d8YUXcsf7g7iHJ/ywd7K3Oc= X-Received: by 2002:adf:f390:: with SMTP id m16-v6mr14586263wro.279.1534280090871; Tue, 14 Aug 2018 13:54:50 -0700 (PDT) MIME-Version: 1.0 References: <3b53edb8-e1d2-109f-6ec7-81513c513433@vangyzen.net> <20180814143718.GL2340@kib.kiev.ua> In-Reply-To: <20180814143718.GL2340@kib.kiev.ua> From: Johannes Lundberg Date: Tue, 14 Aug 2018 21:54:13 +0100 Message-ID: Subject: Re: Make drm drivers use MTRR write-combine To: Konstantin Belousov Cc: eric@vangyzen.net, freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 20:54:52 -0000 On Tue, Aug 14, 2018 at 3:39 PM Konstantin Belousov wrote: > On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote: > > On 8/14/18 4:12 AM, Johannes Lundberg wrote: > > > Hi > > > > > > Something that we have seen for a long time on FreeBSD is the boot > message > > > > > > Failed to add WC MTRR for [0xd0000000-0xdfffffff]: -22; performance may > > > suffer > > > > > > Taking a closer look at this with memcontrol I can see that the 256 MB > > > region that DRM wants to set as WC is already covered by this entry > > > 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active > > > > > > Similar on both my Skylake and Broadwell systems. > > I see something similar on my Dell XPS 13 with a Kaby Lake R: > > > > Failed to add WC MTRR for [0x90000000-0x9fffffff]: -22; performance may > > suffer > > > > 0x80000000/0x80000000 BIOS uncacheable set-by-firmware active > > > > The only mappings in this range are MMIO: > > > > machdep.efi_map: > > Type Physical Virtual #Pages Attr > > [snip] > > MemoryMappedIO 0000e0000000 0xe0000000 00010000 RUNTIME > > MemoryMappedIO 0000fe000000 0xfe000000 00000011 UC RUNTIME > > MemoryMappedIO 0000fec00000 0xfec00000 00000001 UC RUNTIME > > MemoryMappedIO 0000fee00000 0xfee00000 00000001 UC WT WB WP RUNTIME > > MemoryMappedIO 0000ff000000 0xff000000 00001000 UC WT WB WP RUNTIME > > Yes, the cause of the message is that current x86 mtrr code is not > sufficient to handle this situation. You have BIOS-configured variable > range MTRR which covers upper half of the low 4G, as uncacheable (UC). > It is reasonable for BIOS to set it up this way because this is where > PCIe BARs and other devices MMIO regions are located. > > One of the BARs there is the GPU aperture that really should be WC > (write-combining). There are two ways to achieve this: split the UC > variable-length MTRR range into three, UC/WC/UC, which would require > three MTRRs to cover. This is what current x86_mem.c code does not > support. > > Another way is to set WC mode in the page table entries (PTEs) using > Page Attribute Table (PAT), for all PTEs. According to the rules of > combination of the memory access types between MTRR and PAT, WC in PAT > and any access mode in MTRR gives effective WC. > > I saw the same warning when I initially ported GEM. My code used WC PAT > type, which makes the warning cosmetical, and which made me to not add > MTRR split. If new drm driver also consistently uses WC memattr when > creating aperture mappings, then the warning can be ignored as well. > Hi Kib Thanks for the detailed answer. This might already be the case for the out of tree drivers as well. From what I read about the VESA driver the performance difference should be quite big w/o WC and I haven't noticed and performance issues with the newer drivers at all. I will confirm this tomorrow. _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue Aug 14 21:17:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C3E31064A00 for ; Tue, 14 Aug 2018 21:17:12 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8094489667 for ; Tue, 14 Aug 2018 21:17:11 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDG00A00VZBTZ00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Tue, 14 Aug 2018 20:16:11 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDG00IPEWAVIN50@st13p35im-asmtp002.me.com>; Tue, 14 Aug 2018 20:16:09 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-14_09:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1011 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808140204 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: boot errors since upgrading to 12-current From: Toomas Soome In-reply-to: Date: Tue, 14 Aug 2018 23:16:06 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> References: To: tech-lists X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 21:17:12 -0000 > On 14 Aug 2018, at 22:37, tech-lists wrote: >=20 > Hello, >=20 > context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is = *not* root-on-zfs. It boots to an SSD. The three disks indicated below = are spinning rust. >=20 > NAME STATE READ WRITE CKSUM > storage ONLINE 0 0 0 > raidz1-0 ONLINE 0 0 0 > ada1 ONLINE 0 0 0 > ada2 ONLINE 0 0 0 > ada3 ONLINE 0 0 0 >=20 > This machine was running 11.2 up until about a month ago. >=20 > Recently I've seen this flash up on the screen before getting to the = beastie screen: >=20 > BIOS drive C: is disk0 > BIOS drive D: is disk1 > BIOS drive E: is disk2 > BIOS drive F: is disk3 > BIOS drive G: is disk4 > BIOS drive H: is disk5 > BIOS drive I: is disk6 > BIOS drive J: is disk7 >=20 > [the above is normal and has always has been seen on every boot] >=20 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 > read 1 from 0 to 0xcbdb1330, error: 0x31 >=20 > the above has been happening since upgrading to -current a month ago >=20 > ZFS: i/o error - all block copies unavailable > ZFS: can't read MOS of pool storage >=20 > the above is alarming and has been happening for the past couple of = days, since upgrading to r337682 on the 12th August. >=20 > The beastie screen then loads and it boots normally. >=20 > Should I be concerned? Is the output indicative of a problem? >=20 Not immediately and yes. In BIOS loader, we do all disk IO with INT13 = and the error 0x31 is often hinting about missing media or some other = controller related error. Could you paste the output from loader lsdev = -v output? The drive list appears as an result of probing the disks in biosdisk.c. = The read errors are from attempt to read 1 sector from sector 0 (that = is, to read the partition table from the disk). Why this does end with = error, would be interesting to know, unfortunately that error does not = tell us which disk was probed. Since you are getting errors from data pool =E2=80=98storage=E2=80=99, = it does not affect the boot. Why the pool storage is unreadable - it = likely has to do about the errors above, but can not tell for sure based = on the data presented here=E2=80=A6.=20 rgds, toomas From owner-freebsd-current@freebsd.org Tue Aug 14 22:18:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 45E571066A42 for ; Tue, 14 Aug 2018 22:18:07 +0000 (UTC) (envelope-from kostikbel@gmail.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 DD44E8BA3F for ; Tue, 14 Aug 2018 22:18:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id A11E71066A41; Tue, 14 Aug 2018 22:18:06 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8FE651066A40 for ; Tue, 14 Aug 2018 22:18:06 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1180B8BA3D for ; Tue, 14 Aug 2018 22:18:05 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7EMHtMs006061 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 15 Aug 2018 01:17:58 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7EMHtMs006061 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7EMHtA6006060 for current@freebsd.org; Wed, 15 Aug 2018 01:17:55 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 15 Aug 2018 01:17:55 +0300 From: Konstantin Belousov To: current@freebsd.org Subject: EFIRT on machines with pcid after r337773 Message-ID: <20180814221755.GV2340@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 22:18:07 -0000 If you use UEFI boot, have EFIRT compiled in kernel (the case of GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, and the machine resets during kernel initialization, try this. diff --git a/sys/amd64/amd64/pmap.c b/sys/amd64/amd64/pmap.c index d5d795ab502..c9334eab916 100644 --- a/sys/amd64/amd64/pmap.c +++ b/sys/amd64/amd64/pmap.c @@ -1188,7 +1188,7 @@ pmap_bootstrap(vm_paddr_t *firstaddr) kernel_pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN; kernel_pmap->pm_pcids[i].pm_gen = 1; } - PCPU_SET(pcid_next, PMAP_PCID_KERN + 1); + PCPU_SET(pcid_next, PMAP_PCID_KERN + 2); PCPU_SET(pcid_gen, 1); /* * pcpu area for APs is zeroed during AP startup. @@ -2651,8 +2651,8 @@ pmap_pinit0(pmap_t pmap) bzero(&pmap->pm_stats, sizeof pmap->pm_stats); pmap->pm_flags = pmap_flags; CPU_FOREACH(i) { - pmap->pm_pcids[i].pm_pcid = PMAP_PCID_NONE; - pmap->pm_pcids[i].pm_gen = 0; + pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN + 1; + pmap->pm_pcids[i].pm_gen = 1; if (!pti) { __pcpu[i].pc_kcr3 = PMAP_NO_CR3; __pcpu[i].pc_ucr3 = PMAP_NO_CR3; From owner-freebsd-current@freebsd.org Tue Aug 14 22:57:50 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9DD571068B48 for ; Tue, 14 Aug 2018 22:57:50 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id F37538CD3A for ; Tue, 14 Aug 2018 22:57:49 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 55081 invoked by uid 89); 14 Aug 2018 22:51:07 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@46.244.231.99) by mail.grem.de with ESMTPA; 14 Aug 2018 22:51:07 -0000 Date: Wed, 15 Aug 2018 00:51:06 +0200 From: Michael Gmelin To: Konstantin Belousov Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180815005106.69402d23@bsd64.grem.de> In-Reply-To: <20180606010625.62632920@bsd64.grem.de> References: <20180603144840.44bfea41@bsd64.grem.de> <20180603132110.GP3789@kib.kiev.ua> <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> X-Mailer: Claws Mail 3.15.1 (GTK+ 2.24.31; amd64-portbld-freebsd10.3) X-Face: $wrgCtfdVw_H9WAY?S&9+/F"!41z'L$uo*WzT8miX?kZ~W~Lr5W7v?j0Sde\mwB&/ypo^}> +a'4xMc^^KroE~+v^&^#[B">soBo1y6(TW6#UZiC]o>C6`ej+i Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAJFBMVEWJBwe5BQDl LASZU0/LTEWEfHbyj0Txi32+sKrp1Mv944X8/fm1rS+cAAAACXBIWXMAAAsTAAAL EwEAmpwYAAAAB3RJTUUH3wESCxwC7OBhbgAAACFpVFh0Q29tbWVudAAAAAAAQ3Jl YXRlZCB3aXRoIFRoZSBHSU1QbbCXAAAAAghJREFUOMu11DFvEzEUAGCfEhBVFzuq AKkLd0O6VrIQsLXVSZXoWE5N1K3DobBBA9fQpRWc8OkWouaIjedWKiyREOKs+3PY fvalCNjgLVHeF7/3bMtBzV8C/VsQ8tecEgCcDgrzjekwKZ7TwsJZd/ywEKwwP+ZM 8P3drTsAwWn2mpWuDDuYiK1bFs6De0KUUFw0tWxm+D4AIhuuvZqtyWYeO7jQ4Aea 7jUqI+ixhQoHex4WshEvSXdood7stlv4oSuFOC4tqGcr0NjEqXgV4mMJO38nld4+ xKNxRDon7khyKVqY7YR4d+Cg0OMrkWXZOM7YDkEfKiilCn1qYv4mighZiynuHHOA Wq9QJq+BIES7lMFUtcikMnkDGHUoncA+uHgrP0ctIEqfwLHzeSo+eUA66AqzwN6n 2ZHJhw6Qh/PoyC/QENyEyC/AyNjq74Bs+3UH0xYwzDUC4B97HgLocg1QLYgDDO1v f3UX9Y307Ew4AHh67YAFFsxEpkXwpXY3eIgMhAAE3R19L919nNnuD2wlPcDE3UeT L2ytEICQib9BXgS2fU8PrD82ToYO1OEmMSnYTjSqSv9wdC0tPYC+rQRQD9ESnldF CyqfmiYW+tlALt8gH2xrMdC/youbjzPXEun+/ReXsMCDyve3dZc09fn2Oas8oXGc Jj6/fOeK5UmSMPmf/jL+GD8BEj0k/Fn6IO4AAAAASUVORK5CYII= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 22:57:50 -0000 On Wed, 6 Jun 2018 01:06:25 +0200 Michael Gmelin wrote: > On Tue, 5 Jun 2018 16:11:35 +0300 > Konstantin Belousov wrote: > > > On Mon, Jun 04, 2018 at 11:17:56PM +0200, Michael Gmelin wrote: > > > > > > > > > On Mon, 4 Jun 2018 14:06:55 +0300 > > > Konstantin Belousov wrote: > > > > > > > On Mon, Jun 04, 2018 at 12:46:32AM +0200, Michael Gmelin > > > > wrote: > > > > > > [...] > > > > > > > > > This machine comes with it by default (my model was > > > > > > > > > delivered with SeaBIOS 20131018_145217-build121-m2). > > > > > > > > > So I didn't flash anything (didn't feel like bricking > > > > > > > > > it). > > > > > > > > > > > > > > > > > > > > > kernel trap 12 with interrupts disabled > > > > > > > > > > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > > > > > cpuid = 0; apic id = 00 > > > > > > > > > > > fault virtual address = 0xfffff80001000000 > > > > > > > > > > > fault code = supervisor write data, > > > > > > > > > > > protection violation instruction pointer = > > > > > > > > > > > 0x20:Oxffffffff8102955f stack pointer = > > > > > > > > > > > 0x28:0xffffffff82a79be0 frame pointer = > > > > > > > > > > > 0x28:0xffffffff82a79c10 code segment = > > > > > > > > > > > base Ox0, limit Oxfffff, type Ox1b = DPL 0, pres > > > > > > > > > > > 1, long 1, def32 0, gran 1 processor > > > > > > > > > > > eflags = resume, IOPL = 0 current > > > > > > > > > > > process = 0 () [ thread pid 0 tid 0 ] > > > > > > > > > > > Stopped at native_start_all_aps+0x08f: > > > > > > > > > > > movq %rax,(%rsi) > > > > > > > > > > Look up the source line number for this address. > > > > > > > > > > > > > > > > > > > > > > > > > > > > I guess that's sys/amd64/amd64/support.S line 854 (in > > > > > > > > > rdmsr), called by native_start_all_aps. Any additional > > > > > > > > > hints how I can track it down? > > > > > > > > Why did you decided that this is rdmsr_safe() ? First, > > > > > > > > native_start_all_aps() does not call rdmsr, second the > > > > > > > > ddb report clearly indicates that the fault occured > > > > > > > > acessing DMAP in native_start_all_aps(). > > > > > > > > > > > > > > > > Just look up the source line by the address > > > > > > > > native_start_all_aps+0x08f. > > > > > > > > > > > > > > Okay, according to kgbd this should be here: > > > > > > > > > > > > > > https://svnweb.freebsd.org/base/head/sys/amd64/amd64/mp_machdep.c?revision=333368&view=markup#l369 > > > > > > > > > > > > > > 364 > > > > > > > 365 /* Create the initial 1GB replicated page tables */ > > > > > > > 366 for (i = 0; i < 512; i++) { > > > > > > > 367 /* Each slot of the level 4 pages points to > > > > > > > the same level 3 page */ 368 pt4[i] = > > > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + PAGE_SIZE); > > > > > > > 369 pt4[i] |= PG_V | PG_RW | PG_U; 370 > > > > > > > 371 /* Each slot of the level 3 pages points to > > > > > > > the same level 2 page */ 372 pt3[i] = > > > > > > > (u_int64_t)(uintptr_t)(mptramp_pagetables + (2 * > > > > > > > PAGE_SIZE)); 373 pt3[i] |= PG_V | PG_RW | PG_U; > > > > > > > 374 375 /* The level 2 page slots are mapped > > > > > > > with 2MB pages for 1GB. */ 376 pt2[i] = i * (2 > > > > > > > * 1024 * 1024); 377 pt2[i] |= PG_V | PG_RW | > > > > > > > PG_PS | PG_U; 378 } > > > > > > > > > > > > > > -m > > > > > > You have fault on write due to read-only mapping of the > > > > > > portion of the direct map, which maps the kernel text. It > > > > > > is consistent with the faulting address. It is not clear > > > > > > if it is something new on your machine, or before the > > > > > > kernel text was silently corrupted, since ro protection is > > > > > > somewhat recent. > > > > > > > > > > > > It seems that mp_bootaddress() selected the bad place for > > > > > > the bootstrap page tables. Even more, we do not include the > > > > > > kernel text into the physmem[] array, so it is not clear > > > > > > how did it happen. This code was also changed recently. > > > > > > > > > > > > Can you add the print of the physmap[] array somewhere > > > > > > before the panic, to see what is the kernel idea of the > > > > > > available memory ? It should be already done if you have > > > > > > serial console and set debug.late_console tunable to > > > > > > 0. > > > > > > > > > > This is a sad little machine without any kind of serial > > > > > console. > > > > > > > > > > Physmap looks like this after calling getmemsize(): > > > > > > > > > > [0]: 0x10000 > > > > > [1]: 0x30000 > > > > > [2]: 0x40000 > > > > > [3]: 0x9e000 > > > > > [4]: 0x100000 > > > > > [5]: 0xf00000 > > > > > [6]: 0x1003000 > > > > > [7]: 0x7bf7a000 > > > > > > > > > > Physical memory chunks logged in cpu_startup are: > > > > > > > > > > 0x0000000000010000 - 0x000000000002ffff, 141072 bytes (32 > > > > > pages) 0x0000000000040000 - 0x000000000009dfff, 385024 bytes > > > > > (94 pages) > > > > These two chunks reports are consistent with the physmap[0-1, > > > > 2-3]. > > > > > 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 > > > > > pages) 0x0000000002c00000 - 0x0000000075467fff, 1921417216 > > > > > bytes (469096 pages) 0x0000000100000000 - 0x00000001005e7fff, > > > > > 6193152 bytes (1512 pages) > > > > But these three looks completely unrelated to the rest of the > > > > physmap, perhaps except the physmap[4]. We allocate boot pages > > > > from the top of the last physmap chunk, but I am certain that we > > > > do not consume that much memory for boot to make physmap[7] from > > > > the last reported address. > > > > > > > > Are you sure that there are no typos in the values above ? > > > > > > Double checked the numbers. I changed it a bit more, > > > so that debug output appears all on one page. Please see here for > > > the results: > > > > > > https://gist.github.com/grembo/cebb9f7e2a98c37a51bee1e508f7d890 > > Ok, I have a guess what is going on. Does the result of the quirks > > end up as hw.physmem tunable passed to kernel ? It seems that there > > is physmap[] element pointing outside the DMAP-mapped region. > > > > Perhaps print the dmap limit too, to see whether I am on the right > > track. > > I didn't print the dmap limit yet, but I tested your patch: > > > > > Try the following change. It lacks i386 bits. > > > > diff --git a/sys/amd64/amd64/machdep.c b/sys/amd64/amd64/machdep.c > > index e5c69ed91fa..bd6bbf04006 100644 > > --- a/sys/amd64/amd64/machdep.c > > +++ b/sys/amd64/amd64/machdep.c > > @@ -1254,7 +1254,7 @@ getmemsize(caddr_t kmdp, u_int64_t first) > > * in real mode mode (e.g. SMP bare metal). > > */ > > if (init_ops.mp_bootaddress) > > - init_ops.mp_bootaddress(physmap, &physmap_idx); > > + init_ops.mp_bootaddress(physmap, &physmap_idx, > > first); > > /* > > * Maxmem isn't the "maximum memory", it's one larger than > > the diff --git a/sys/amd64/amd64/mp_machdep.c > > b/sys/amd64/amd64/mp_machdep.c index 30146142087..292a6cefa91 100644 > > --- a/sys/amd64/amd64/mp_machdep.c > > +++ b/sys/amd64/amd64/mp_machdep.c > > @@ -103,7 +103,8 @@ static int start_ap(int apic_id); > > * Calculate usable address in base memory for AP trampoline code. > > */ > > void > > -mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx) > > +mp_bootaddress(vm_paddr_t *physmap, unsigned int *physmap_idx, > > + vm_paddr_t dmap_limit) > > { > > unsigned int i; > > bool allocated; > > @@ -117,8 +118,9 @@ mp_bootaddress(vm_paddr_t *physmap, unsigned int > > *physmap_idx) > > * store the initial page tables. Note that it > > needs to be > > * aligned to a page boundary. > > */ > > - if (physmap[i] >= GiB(4) || > > - (physmap[i + 1] - round_page(physmap[i])) < > > (PAGE_SIZE * 3)) > > + if (physmap[i] >= GiB(4) || physmap[i + 1] - > > + round_page(physmap[i]) < PAGE_SIZE * 3 || > > + physmap[i + 1] - PAGE_SIZE * 3 > dmap_limit) > > continue; > > > > allocated = true; > > diff --git a/sys/amd64/include/smp.h b/sys/amd64/include/smp.h > > index 2ecfe62cf9f..24f0580fe51 100644 > > --- a/sys/amd64/include/smp.h > > +++ b/sys/amd64/include/smp.h > > @@ -58,7 +58,7 @@ void invlpg_pcid_handler(void); > > void invlrng_invpcid_handler(void); > > void invlrng_pcid_handler(void); > > int native_start_all_aps(void); > > -void mp_bootaddress(vm_paddr_t *, unsigned int *); > > +void mp_bootaddress(vm_paddr_t *, unsigned int *, > > vm_paddr_t); > > #endif /* !LOCORE */ > > #endif /* SMP */ > > diff --git a/sys/x86/include/init.h b/sys/x86/include/init.h > > index 880cabaa949..58bbe0a5fd6 100644 > > --- a/sys/x86/include/init.h > > +++ b/sys/x86/include/init.h > > @@ -41,7 +41,7 @@ struct init_ops { > > void (*early_clock_source_init)(void); > > void (*early_delay)(int); > > void (*parse_memmap)(caddr_t, vm_paddr_t *, int *); > > - void (*mp_bootaddress)(vm_paddr_t *, unsigned int > > *); > > + void (*mp_bootaddress)(vm_paddr_t *, unsigned int *, > > vm_paddr_t); int (*start_all_aps)(void); > > void (*msi_init)(void); > > }; > > With the patch I could boot without problems and the machine appears > to be stable (ran some high load & memory intensive tests - by the > way, the machine only has 2gb of ram [even though 4g are reported on > boot - usable memory appears to be reported ok]). > > Thanks, > Michael > Hi, Reviving this old thread, since I just updated to r337818 and a similar problem is happening again. Since the fix in r334799 (review https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, so maybe this is related (https://svnweb.freebsd.org/base?view=revision&revision=334799). Please see the screenshot of the panic below: https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 This is me not digging any deeper, hoping that this is something obvious. Please let me know if you need more input. Thanks, Michael -- Michael Gmelin From owner-freebsd-current@freebsd.org Tue Aug 14 23:38:15 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5410A1069CEE for ; Tue, 14 Aug 2018 23:38:15 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.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 E43908E12A for ; Tue, 14 Aug 2018 23:38:14 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A7EAF1069CEC; Tue, 14 Aug 2018 23:38:14 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85DDF1069CEB for ; Tue, 14 Aug 2018 23:38:14 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw1-xc41.google.com (mail-yw1-xc41.google.com [IPv6:2607:f8b0:4864:20::c41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 219938E128 for ; Tue, 14 Aug 2018 23:38:14 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw1-xc41.google.com with SMTP id 139-v6so17557051ywg.12 for ; Tue, 14 Aug 2018 16:38:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rPBFScVB4IeWpaV9VE7m3FQsR41d/JY96v5qhfj6t1s=; b=PicrDwRWTCgRKx+LHYp27omB3oSxCKfjeC44bf5j+KEqg3Gh3XL3Nwfrd7ia0KX+mv +FSJje3XBGhsMZWooeZD9zrvDJCfoNvU5BRn0ROZ/WybzLWIL7NzmzBirOfvMA0CGG6T 9IynRNtlakbCiV0NlJOm6J0ug1nXNYU6XT8GRwjUQ4URIyIdrlFFcV/LSBSx6+ySWakV VpYs+LxQu96X3KtdKDCWyYEQSXlvN5xydNXhuyRYt2Iirj3y1HeHwlcwkIp53JDrMeTI WscYg3w0TXz5epzCFa8LYzCBUft/5GxKYUhYuTIimGgMimlO5moYTCcRyrSAtFaRGMMe YdBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rPBFScVB4IeWpaV9VE7m3FQsR41d/JY96v5qhfj6t1s=; b=rK57532nHucxUne5Fs9rGeM94X0u+wWpMb5DOINj4hRZNshij9WaJw0w0EpdhvirjJ RQcSfwRsGkC+Q3ZvWKWYN1s0FCOVwFMXvJkgjpggtb/hAw+/Ra77MTiwC1pHVneboyEx VCzbOEiDdkxqcXKxd7QqSO43m47/df9T2tuWirymZ7O8lIPcY1d/zIT/YCfOseAMniuH L5djndQ4AV8+t39n8mKAw3z3GInEW82KcwCek7uHNFkPVIYooW18ZC0xaGBfeA/Ufrjs /UmJ/QoI/JU2y19pHNQTx5IuTHM6LEl0yrSAs7Hgl6YxOo+ldqvsBHdD7ldpyTJ9qslk 1NVQ== X-Gm-Message-State: AOUpUlHZwezh35VAbN8ibWI83FHdzO+r5KlDQgF2Eiho/mFNxjc6/YOD ujh0tyKSjb4sOpjIfpBsBG01tI72pwKfypnAxFisuw== X-Google-Smtp-Source: AA+uWPwIvuxem9bQuohKhXpXvgK7C03O/QKgTrkVrTqiX9klgK33FgyOyGIGRjn/XQr9XPtm5qGVCHtDhBf9c2fkjs4= X-Received: by 2002:a5b:141:: with SMTP id c1-v6mr12676532ybp.331.1534289893647; Tue, 14 Aug 2018 16:38:13 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:f205:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 16:38:13 -0700 (PDT) In-Reply-To: <20180814221755.GV2340@kib.kiev.ua> References: <20180814221755.GV2340@kib.kiev.ua> From: Oliver Pinter Date: Wed, 15 Aug 2018 01:38:13 +0200 Message-ID: Subject: Re: EFIRT on machines with pcid after r337773 To: Konstantin Belousov Cc: current@freebsd.org, kevans@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Aug 2018 23:38:15 -0000 Hi! Seems like this patch fixed the boot issue on Dell e5440 with UEFI. Once you get to MFC, please X-MFC-with the following patch: commit dfe1112fa878c5d8fa0605d1de10c96ecc993569 Author: rlibby Date: Fri Jul 21 17:11:36 2017 +0000 __pcpu: gcc -Wredundant-decls Pollution from counter.h made __pcpu visible in amd64/pmap.c. Delete the existing extern decl of __pcpu in amd64/pmap.c and avoid referring to that symbol, instead accessing the pcpu region via PCPU_SET macros. Also delete an unused extern decl of __pcpu from mp_x86.c. Reviewed by: kib Approved by: markj (mentor) Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D11666 Notes: svn path=/head/; revision=321335 On 8/15/18, Konstantin Belousov wrote: > If you use UEFI boot, have EFIRT compiled in kernel (the case of > GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, > and the machine resets during kernel initialization, try this. > > diff --git a/sys/amd64/amd64/pmap.c b/sys/amd64/amd64/pmap.c > index d5d795ab502..c9334eab916 100644 > --- a/sys/amd64/amd64/pmap.c > +++ b/sys/amd64/amd64/pmap.c > @@ -1188,7 +1188,7 @@ pmap_bootstrap(vm_paddr_t *firstaddr) > kernel_pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN; > kernel_pmap->pm_pcids[i].pm_gen = 1; > } > - PCPU_SET(pcid_next, PMAP_PCID_KERN + 1); > + PCPU_SET(pcid_next, PMAP_PCID_KERN + 2); > PCPU_SET(pcid_gen, 1); > /* > * pcpu area for APs is zeroed during AP startup. > @@ -2651,8 +2651,8 @@ pmap_pinit0(pmap_t pmap) > bzero(&pmap->pm_stats, sizeof pmap->pm_stats); > pmap->pm_flags = pmap_flags; > CPU_FOREACH(i) { > - pmap->pm_pcids[i].pm_pcid = PMAP_PCID_NONE; > - pmap->pm_pcids[i].pm_gen = 0; > + pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN + 1; > + pmap->pm_pcids[i].pm_gen = 1; > if (!pti) { > __pcpu[i].pc_kcr3 = PMAP_NO_CR3; > __pcpu[i].pc_ucr3 = PMAP_NO_CR3; > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Aug 15 00:29:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D13FE106BBA3 for ; Wed, 15 Aug 2018 00:29:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 3AAC070090 for ; Wed, 15 Aug 2018 00:29:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 8a702682 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Tue, 14 Aug 2018 17:29:00 -0700 (PDT) To: FreeBSD Current From: Pete Wright Subject: CURRENT from today throws lots of ACPI errors, lost HDMI detection Message-ID: Date: Tue, 14 Aug 2018 17:28:56 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 00:29:03 -0000 howdy, running code from today and having lots of issues.  when i boot the system (a kabylake laptop) using legacy mode in the BIOS i see lots of these errors are thrown in dmesg: acpi0: on motherboard Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) Firmware Error (ACPI): Failure creating [\134_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20180810/dswload2-468) ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180810/psobject-372) ACPI Error: Skip parsing opcode OpcodeName unavailable (20180810/psloop-689) there are lots more, i can post a pastebin link if needed. i also attempted to boot using UEFI but the system hangs very early in the boot process.  i have reverted to legacy mode for now so that i can work, but am keen to test out any patches or do any other debugging that is needed. thx! -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Aug 15 01:13:44 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E25B106CEEC for ; Wed, 15 Aug 2018 01:13:44 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A83B7713C4 for ; Wed, 15 Aug 2018 01:13:43 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f52.google.com (mail-lf1-f52.google.com [209.85.167.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 44ED1FED8 for ; Wed, 15 Aug 2018 01:13:43 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f52.google.com with SMTP id y200-v6so15139931lfd.7 for ; Tue, 14 Aug 2018 18:13:43 -0700 (PDT) X-Gm-Message-State: AOUpUlESdWjA5uZFWLAGGnlg1iSBUBOuhosHMCShi3qc7+++/KR3QM65 EUTANlm7KFWlBuA2Isn7+3Cg4U6hhE0iYFd+N9Q= X-Google-Smtp-Source: AA+uWPzVyKfATlK9umO15r7CVCa/iWvwAudjjy2jLMDQjF0Gw08jc6OIqGYVTPQhzlUlvCldfTP2txsC9iBJTjcKuDc= X-Received: by 2002:a19:26d2:: with SMTP id m201-v6mr14581214lfm.43.1534295621904; Tue, 14 Aug 2018 18:13:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 18:13:21 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Tue, 14 Aug 2018 20:13:21 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Pete Wright Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 01:13:44 -0000 On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > i also attempted to boot using UEFI but the system hangs very early in the > boot process. i have reverted to legacy mode for now so that i can work, > but am keen to test out any patches or do any other debugging that is > needed. Hi Pete, Where in the process does it hang with UEFI? I can't help much with any of your other problems, but I am curious about this one. =) Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Aug 15 03:06:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9231106FBCA for ; Wed, 15 Aug 2018 03:06:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 6500A74CC2 for ; Wed, 15 Aug 2018 03:06:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id C0CAF20B78; Tue, 14 Aug 2018 23:06:17 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 14 Aug 2018 23:06:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=n+e04OTKf7HcO3eQ71mxiYaln5bzg o/zJUGKmFFhsPs=; b=L44iaeiMLUyHrWxZvZvVs6EbRd+EP5QkjXeMjScek8jbc N3QuJtJIAauzX1vYDY2abhUuI9iQaXEozzb5Rcp/bhJC6LtQlP4O7A9SalxwaJH6 xOcv/dkybr8K6J2KxZ2SxG2uTz8q77oVB7V74GGTJDXCkwRX4wkLz43KpDCJA9o4 qH8W8itDkQikWVeCFvPTaLx99ilO0zF+JxPDcJTMNdJH/yXbR8vhKptUWm2TojXG Sb3S87uW4SDNJIZfVuF5KUDYcHQ0R/EJP+4+qIWgEMdN6dZbwnsg8F3qFLEGa3Gf 7IlD3g1b4hy/ogVRRxyyz5daZdO6VE8GUy6uXkI/g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=n+e04O TKf7HcO3eQ71mxiYaln5bzgo/zJUGKmFFhsPs=; b=nN80SDZkrUy7aOAXRUK9/T UYKy8cFwgJ6ySqlR/JF/TDMs/EPuL4tkIL06swg95M4xGmhsDAAko1dxnW7mDAA2 wQhR1cnFk8cLIkuMZql246OBZS3e5qgDSVUK5TU1n7ZJjt3QFxp6F3d1zHqggSVA zshpzkVd70oNu+DoGPeZgQspobAwUIBmI8rO4eCd1o7i/pNDOoczxrqcH8CHLrqA 9NYi8g3I0Gkn521fsytHX5p+Mdi+iz7BRidHIbirZkFukybFPysoGw7+GuN3cfdG kjkDZ4XPYXpAK8PJNjM1RQ5TPuS5ox0S5eEtFhNl58d4DXVzcIhavn8F1Q22h5Cg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 1C84D10273; Tue, 14 Aug 2018 23:06:17 -0400 (EDT) Subject: Re: boot errors since upgrading to 12-current To: Toomas Soome Cc: freebsd-current@freebsd.org References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> From: tech-lists Organization: none Message-ID: <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> Date: Wed, 15 Aug 2018 04:06:15 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:06:24 -0000 On 14/08/2018 21:16, Toomas Soome wrote: > > >> On 14 Aug 2018, at 22:37, tech-lists wrote: >> >> Hello, >> >> context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is >> *not* root-on-zfs. It boots to an SSD. The three disks indicated >> below are spinning rust. >> >> NAME STATE READ WRITE CKSUM storage ONLINE 0 >> 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 >> 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 >> 0 0 >> >> This machine was running 11.2 up until about a month ago. >> >> Recently I've seen this flash up on the screen before getting to >> the beastie screen: >> >> BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is >> disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: >> is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 >> >> [the above is normal and has always has been seen on every boot] >> >> read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >> 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 >> read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >> 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 >> read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >> 0xcbdb1330, error: 0x31 >> >> the above has been happening since upgrading to -current a month >> ago >> >> ZFS: i/o error - all block copies unavailable ZFS: can't read MOS >> of pool storage >> >> the above is alarming and has been happening for the past couple of >> days, since upgrading to r337682 on the 12th August. >> >> The beastie screen then loads and it boots normally. >> >> Should I be concerned? Is the output indicative of a problem? >> > > Not immediately and yes. In BIOS loader, we do all disk IO with INT13 > and the error 0x31 is often hinting about missing media or some other > controller related error. Could you paste the output from loader > lsdev -v output? > > The drive list appears as an result of probing the disks in > biosdisk.c. The read errors are from attempt to read 1 sector from > sector 0 (that is, to read the partition table from the disk). Why > this does end with error, would be interesting to know, unfortunately > that error does not tell us which disk was probed. Hi Toomas, thanks for looking at this. lsdev -v looks like this: OK lsdev -v disk devices: disk0: BIOS drive C (16514064 X 512): disk0s1: FreeBSD 111GB disk0s1a: FreeBSD UFS 108GB disk0s1b: FreeBSD swap 3881MB disk1: BIOS drive D (16514064 X 512): disk2: BIOS drive E (16514064 X 512): disk3: BIOS drive F (16514064 X 512): disk4: BIOS drive G (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk5: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk6: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 disk7: BIOS drive D (2880 X 512): read 1 from 0 to 0xcbde0a20, error 0x31 OK disk4 to disk7 corresponds with da0 to da3 which are sd/mmc devices without any media in. What made me notice it is it never showed the read 1 from 0 to $random_value on 11-stable. The system runs 12-current now. disk1 to disk3 are the hard drives making up ZFS. These are 4TB Western Digital SATA-3 WDC WD4001FAEX. >> Since you are getting errors from data pool ‘storage’, it does not >> affect the boot. Why the pool storage is unreadable - it likely has >> to do about the errors above, but can not tell for sure based on the >> data presented here…. Thing is, the data pool works fine when boot completes. i.e it loads read/write and behaves normally. thanks, -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 03:19:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 622F31070259 for ; Wed, 15 Aug 2018 03:19:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 DDAAB753E0 for ; Wed, 15 Aug 2018 03:19:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7978321B81; Tue, 14 Aug 2018 23:19:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Tue, 14 Aug 2018 23:19:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=RgqVsybZEZLjr5yhxQ1J+7GaQS/Z5 eIqr7sBWK5fjto=; b=khkC2FCPs8+ZIx33s6/+jfuU+5jeVCeMSqPW723TFYOIj iD5gCGuCQNHCW1GYuVyGY4AeF4cCSySdnfAnGtzAnq+xl9f5eOUr4JamUo6uvGB8 /ArdN9KUHHvoQJVE32Z8J0mBsYNiEzOqg+GJvelmva9b/Flu2XHe5o/fMQVQhLYc Xyj8yCaI2Uixx663/R/QnT2mRYH9S26HZe3g4NoDWnhSDX6POzdmTc6xK56G6dJt gwEB7ak4ZUWGPAP3HF7i1/SQbfJo9f4ekocJAoO6SSc2NAq0DfzLHLUuJaYX6B/w DJbKoNEYZNW0oZxqG4hZYUwmCQ/ybRCQYC88QymcQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=RgqVsy bZEZLjr5yhxQ1J+7GaQS/Z5eIqr7sBWK5fjto=; b=X1yife9RDWvym6ryNzUKr/ syGJf+0/l1ZqTI75P9P3SweyDBL1TH22aXqMn65CFKt1DHlWxxl7TScangP+2hCi 2VAaQ01GUetBgvV/AG+xunB8IlvSrAsBvkuJgJOmLJRhQFtvtGdAcW+4LA8te7cA 65Fsw+KPgIVMaXFJr1juKjhhwyxHsSjWP7M946MqR2OVa0WxY4fBlqScWloSmA+D MGZd6h7QINC1/DG+P/M9z154FHKF0PY6wsTOUkfzZcG3kKIbeJ9JX5Gkv/6EivvS yuGVXQMn31zaNYjM6TN6H/RYN23VepJaUrS8/EUaM52Rrkrn42v9aLe76aLx588A == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 5C65A10268; Tue, 14 Aug 2018 23:19:22 -0400 (EDT) Subject: Re: zpool scrub. Wtf? To: Cy Schubert , Shawn Webb , "Alex V. Petrov" Cc: freebsd-current References: <20180812175324.79E1F96D@spqr.komquats.com> From: tech-lists Organization: none Message-ID: <93818fab-6b53-bade-dffa-afcf322dce29@zyxst.net> Date: Wed, 15 Aug 2018 04:19:21 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180812175324.79E1F96D@spqr.komquats.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:19:24 -0000 On 12/08/2018 18:53, Cy Schubert wrote: > I haven't looked at it closely but from what I saw it was counting scan reads and issued reads. It may be a simple matter of dividing by 2. Dividing what by 2? scan: scrub in progress since Tue Aug 7 21:21:51 2018 804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total 0 repaired, 129,87% done, 929637 days 13:43:01 to go I'm also seeing this problem running 12.0-ALPHA1 #0 r337682 thanks, -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 03:41:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B3771070973 for ; Wed, 15 Aug 2018 03:41:10 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 7CDE275EC2; Wed, 15 Aug 2018 03:41:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 95ecb2ee TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 14 Aug 2018 20:41:07 -0700 (PDT) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Kyle Evans Cc: FreeBSD Current References: From: Pete Wright Message-ID: Date: Tue, 14 Aug 2018 20:41:03 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:41:10 -0000 On 8/14/18 6:13 PM, Kyle Evans wrote: > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >> i also attempted to boot using UEFI but the system hangs very early in the >> boot process. i have reverted to legacy mode for now so that i can work, >> but am keen to test out any patches or do any other debugging that is >> needed. > Hi Pete, > > Where in the process does it hang with UEFI? I can't help much with > any of your other problems, but I am curious about this one. =) sure thing - the last several lines are: random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module nexus0 at this point it hangs.  let me know if you want me to try booting with verbose output to dmesg or something. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Aug 15 03:45:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CA0E91070C4A for ; Wed, 15 Aug 2018 03:45:41 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7C93F761AE for ; Wed, 15 Aug 2018 03:45:41 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 1A27510E22 for ; Wed, 15 Aug 2018 03:45:41 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f177.google.com with SMTP id s12-v6so17071403ljj.0 for ; Tue, 14 Aug 2018 20:45:41 -0700 (PDT) X-Gm-Message-State: AOUpUlE4LM35DJEYunww4JLQK5cDdCulAPLsPd4fy0iSCfY5lo9uvzRc jtE6hAAkM/gHuciBJrlPDmsuZ5lxh4casKuqWDQ= X-Google-Smtp-Source: AA+uWPy93ypiDdnBknYXYSzeayvydT0hLDe2ijthchsVClt4SYupBRQEchLZ/iYsXZLCDBTukoIlsTfcJb5xEGyQDPg= X-Received: by 2002:a2e:1004:: with SMTP id j4-v6mr17889135lje.2.1534304739633; Tue, 14 Aug 2018 20:45:39 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 20:45:19 -0700 (PDT) In-Reply-To: References: From: Kyle Evans Date: Tue, 14 Aug 2018 22:45:19 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Pete Wright Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:45:42 -0000 On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >>> >>> i also attempted to boot using UEFI but the system hangs very early in >>> the >>> boot process. i have reverted to legacy mode for now so that i can work, >>> but am keen to test out any patches or do any other debugging that is >>> needed. >> >> Hi Pete, >> >> Where in the process does it hang with UEFI? I can't help much with >> any of your other problems, but I am curious about this one. =) > > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 > > at this point it hangs. let me know if you want me to try booting with > verbose output to dmesg or something. > Are you running GENERIC, or custom config? Any modules loaded? I'm curious if you've been bitten somehow by recently enabling EFIRT in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and see where that gets you? From owner-freebsd-current@freebsd.org Wed Aug 15 03:49:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2F3661070DDE for ; Wed, 15 Aug 2018 03:49:10 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-so.shaw.ca (smtp-out-so.shaw.ca [64.59.136.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B4A0076330 for ; Wed, 15 Aug 2018 03:49:09 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id pmmZfmzyLwyxUpmn7fYQs6; Tue, 14 Aug 2018 21:48:57 -0600 X-Authority-Analysis: v=2.3 cv=NPJhBHyg c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=dapMudl6Dx4A:10 a=vxP3BzG0AAAA:8 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=DxxTMZUXB4jeFQZQwtEA:9 a=CjuIK1q_8ugA:10 a=4tHceQipB5Rc01mo_vQZ:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy8 [10.2.2.6]) by spqr.komquats.com (Postfix) with ESMTPS id D0E121C0; Tue, 14 Aug 2018 20:48:04 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w7F3lfjw053615; Tue, 14 Aug 2018 20:47:41 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w7F3lfsQ053607; Tue, 14 Aug 2018 20:47:41 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201808150347.w7F3lfsQ053607@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: tech-lists cc: Cy Schubert , Shawn Webb , "Alex V. Petrov" , freebsd-current Subject: Re: zpool scrub. Wtf? In-Reply-To: Message from tech-lists of "Wed, 15 Aug 2018 04:19:21 +0100." <93818fab-6b53-bade-dffa-afcf322dce29@zyxst.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Aug 2018 20:47:41 -0700 X-CMAE-Envelope: MS4wfA41vtUPh3abhMqNdzEWAnwVDLb1RO2Fo39VUEk+TXsndxUfRcLN+JQ07o7722lweHXYJx1wPuUAKjUBZgY2y+GVNat/NGTe0okEqX+dHGwvxG7J8L/s L62z9vF0zLicekqSqX9JKWxWtrA0nA5IL62arYGFqwjMi+7G8vzkeyV+M1WNtakZI26gLiJIVXb20bE/v3yzYSbItQzRtd6OqBfImd033QozO0bYGOKPQBsZ esQtsT2KH7toiL9W0dtDFsi32TP8f7DbEzzGZqJacH8= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:49:10 -0000 In message <93818fab-6b53-bade-dffa-afcf322dce29@zyxst.net>, tech-lists writes: > On 12/08/2018 18:53, Cy Schubert wrote: > > I haven't looked at it closely but from what I saw it was counting scan rea > ds and issued reads. It may be a simple matter of dividing by 2. > > Dividing what by 2? > > scan: scrub in progress since Tue Aug 7 21:21:51 2018 > 804G scanned at 163M/s, 1,06T issued at 219M/s, 834G total > 0 repaired, 129,87% done, 929637 days 13:43:01 to go > > I'm also seeing this problem running 12.0-ALPHA1 #0 r337682 This is probably incorrect but this is what I was talking about. Index: cddl/contrib/opensolaris/cmd/zpool/zpool_main.c =================================================================== --- cddl/contrib/opensolaris/cmd/zpool/zpool_main.c (revision 337830) +++ cddl/contrib/opensolaris/cmd/zpool/zpool_main.c (working copy) @@ -4492,8 +4492,8 @@ scanned = ps->pss_examined; pass_scanned = ps->pss_pass_exam; - issued = ps->pss_issued; - pass_issued = ps->pss_pass_issued; + issued = ps->pss_issued / 2; + pass_issued = ps->pss_pass_issued / 2; total = ps->pss_to_examine; /* we are only done with a block once we have issued the IO for it */ -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Wed Aug 15 03:56:09 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 016BE10711CC for ; Wed, 15 Aug 2018 03:56:09 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 6262A767F4; Wed, 15 Aug 2018 03:56:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 6ae06376 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 14 Aug 2018 20:56:06 -0700 (PDT) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Kyle Evans Cc: FreeBSD Current References: From: Pete Wright Message-ID: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> Date: Tue, 14 Aug 2018 20:56:02 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 03:56:09 -0000 On 8/14/18 8:45 PM, Kyle Evans wrote: > On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >> On 8/14/18 6:13 PM, Kyle Evans wrote: >>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >>>> i also attempted to boot using UEFI but the system hangs very early in >>>> the >>>> boot process. i have reverted to legacy mode for now so that i can work, >>>> but am keen to test out any patches or do any other debugging that is >>>> needed. >>> Hi Pete, >>> >>> Where in the process does it hang with UEFI? I can't help much with >>> any of your other problems, but I am curious about this one. =) >> sure thing - the last several lines are: >> >> random: fast provider: "Intel Secure Key RNG" >> kbd1 at kbdmux0 >> netmap: loaded module >> nexus0 >> >> at this point it hangs. let me know if you want me to try booting with >> verbose output to dmesg or something. >> > Are you running GENERIC, or custom config? Any modules loaded? this is a GENERIC kernel using ZFS as well as GELI full disk encryption. > > I'm curious if you've been bitten somehow by recently enabling EFIRT > in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and > see where that gets you? i did attempt to set that in loader.conf - and it progressed farther but kernel panic'd when trying to bring up my iwn wireless interface. i'm building an older version in an attempt to bisect this issue (i have a skylake system running a checkout from monday without issues, so testing that now).  if i am still running into problems i'll boot with efi.rt.disabled=1 and will post the gdb panic string here. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Aug 15 04:02:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 856651071530 for ; Wed, 15 Aug 2018 04:02:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 336D076C39 for ; Wed, 15 Aug 2018 04:02:20 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id C82D71101C for ; Wed, 15 Aug 2018 04:02:19 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lf1-f54.google.com with SMTP id n96-v6so8069lfi.1 for ; Tue, 14 Aug 2018 21:02:19 -0700 (PDT) X-Gm-Message-State: AOUpUlH2hmvNF8n/gkvE5hXtR3GwKYUqWCm0gX8YXw8Gy2QtzAKd4fiZ N9GX4CXmadFGdo4syDnco9jXdU4e6X+l9R/Ksfw= X-Google-Smtp-Source: AA+uWPzrF2G2DnNP5EmZAK4xb8bfY+4OxYLZZmSCwseCJEXhzJ4uuXAO3WRDrm8w2rbdzXF9y8tmQCOZXNWh3Bqlgrw= X-Received: by 2002:a19:2194:: with SMTP id h142-v6mr14858340lfh.75.1534305738460; Tue, 14 Aug 2018 21:02:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Tue, 14 Aug 2018 21:01:57 -0700 (PDT) In-Reply-To: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> From: Kyle Evans Date: Tue, 14 Aug 2018 23:01:57 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Pete Wright Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 04:02:20 -0000 On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: > > On 8/14/18 8:45 PM, Kyle Evans wrote: >> >> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >>> >>> On 8/14/18 6:13 PM, Kyle Evans wrote: >>>> >>>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright >>>> wrote: >>>>> >>>>> i also attempted to boot using UEFI but the system hangs very early in >>>>> the >>>>> boot process. i have reverted to legacy mode for now so that i can >>>>> work, >>>>> but am keen to test out any patches or do any other debugging that is >>>>> needed. >>>> >>>> Hi Pete, >>>> >>>> Where in the process does it hang with UEFI? I can't help much with >>>> any of your other problems, but I am curious about this one. =) >>> >>> sure thing - the last several lines are: >>> >>> random: fast provider: "Intel Secure Key RNG" >>> kbd1 at kbdmux0 >>> netmap: loaded module >>> nexus0 >>> >>> at this point it hangs. let me know if you want me to try booting with >>> verbose output to dmesg or something. >>> >> Are you running GENERIC, or custom config? Any modules loaded? > > > > this is a GENERIC kernel using ZFS as well as GELI full disk encryption. > Good to know, thanks! > >> >> I'm curious if you've been bitten somehow by recently enabling EFIRT >> in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and >> see where that gets you? > > > i did attempt to set that in loader.conf - and it progressed farther but > kernel panic'd when trying to bring up my iwn wireless interface. > Interesting... out of side curiosity, what does this panic look like? Can you also try running a kernel >= r337773 with kib's patch from [1] applied to make sure this the EFI part of this isn't already solved? > > i'm building an older version in an attempt to bisect this issue (i have a > skylake system running a checkout from monday without issues, so testing > that now). if i am still running into problems i'll boot with > efi.rt.disabled=1 and will post the gdb panic string here. > Excellent. > -pete > Thanks, Kyle Evans [1] https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070660.html From owner-freebsd-current@freebsd.org Wed Aug 15 04:06:35 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2488B1071712 for ; Wed, 15 Aug 2018 04:06:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 845C876E4A; Wed, 15 Aug 2018 04:06:34 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 096f02c7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 14 Aug 2018 21:06:32 -0700 (PDT) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Kyle Evans Cc: FreeBSD Current References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> From: Pete Wright Message-ID: Date: Tue, 14 Aug 2018 21:06:28 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 04:06:35 -0000 On 8/14/18 9:01 PM, Kyle Evans wrote: > >>> I'm curious if you've been bitten somehow by recently enabling EFIRT >>> in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and >>> see where that gets you? >> >> i did attempt to set that in loader.conf - and it progressed farther but >> kernel panic'd when trying to bring up my iwn wireless interface. >> > Interesting... out of side curiosity, what does this panic look like? > Can you also try running a kernel >= r337773 with kib's patch from [1] > applied to make sure this the EFI part of this isn't already solved? sure i can give that a spin. >> i'm building an older version in an attempt to bisect this issue (i have a >> skylake system running a checkout from monday without issues, so testing >> that now). if i am still running into problems i'll boot with >> efi.rt.disabled=1 and will post the gdb panic string here. >> > Excellent. so i have reverted back to this git hash: 90f37b39e4a https://github.com/freebsd/freebsd/commit/90f37b39e4ad481d3e5a059123f7d68ac153f0c5 and i can confirm that i am able to boot with EFI enabled, do not experience any issues bringing up my iwn interface and HDMI is recognized according to xrandr.  so that solves my immediate problem! :)  interestingly enough i still see the ACPI errors I reported earlier, but perhaps that is a red herring. i'll go back to the tip of master and apply kib's patch and see how it goes. -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Aug 15 04:19:37 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F227F1071D43 for ; Wed, 15 Aug 2018 04:19:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 5117077381; Wed, 15 Aug 2018 04:19:36 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.190] (cpe-23-243-162-239.socal.res.rr.com [23.243.162.239]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id e1b2aa38 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 14 Aug 2018 21:19:34 -0700 (PDT) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection From: Pete Wright To: Kyle Evans Cc: FreeBSD Current References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> Message-ID: <337febb2-1c14-f679-1dd4-5d1c9ad73be1@nomadlogic.org> Date: Tue, 14 Aug 2018 21:19:30 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 04:19:37 -0000 On 8/14/18 9:06 PM, Pete Wright wrote: > > On 8/14/18 9:01 PM, Kyle Evans wrote: >> >>>> I'm curious if you've been bitten somehow by recently enabling EFIRT >>>> in GENERIC. Can you try setting efi.rt.disabled=1 at loader prompt and >>>> see where that gets you? >>> >>> i did attempt to set that in loader.conf - and it progressed farther >>> but >>> kernel panic'd when trying to bring up my iwn wireless interface. >>> >> Interesting... out of side curiosity, what does this panic look like? >> Can you also try running a kernel >= r337773 with kib's patch from [1] >> applied to make sure this the EFI part of this isn't already solved? > > sure i can give that a spin. > > >>> i'm building an older version in an attempt to bisect this issue (i >>> have a >>> skylake system running a checkout from monday without issues, so >>> testing >>> that now).  if i am still running into problems i'll boot with >>> efi.rt.disabled=1 and will post the gdb panic string here. >>> >> Excellent. > > so i have reverted back to this git hash: > 90f37b39e4a > > https://github.com/freebsd/freebsd/commit/90f37b39e4ad481d3e5a059123f7d68ac153f0c5 > > > and i can confirm that i am able to boot with EFI enabled, do not > experience any issues bringing up my iwn interface and HDMI is > recognized according to xrandr.  so that solves my immediate problem! > :)  interestingly enough i still see the ACPI errors I reported > earlier, but perhaps that is a red herring. > > i'll go back to the tip of master and apply kib's patch and see how it > goes. > ok great (thank's ccache for making buildkernel fast :) ) so after applying the patch from kib i have the same behavior as i'm seeing on git hash 90f37b39e4a. i.e. boots fine with UEFI enabled, iwn interface comes up, HDMI output is detected by xrandr and interesting ACPI warning messages. i'll dogfood this patch tomorrow when i get into the office and validate connecting my HDMI display works as expected and will report any other issues i bump into. thanks for your help Kyle!  I didn't think to test kib's patch as i was assuming my issue was related to the ACPI errors, but this seems to get me back to where i need to be to work tomorrow so i'm good to go :) -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Wed Aug 15 05:37:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0FEA1073552 for ; Wed, 15 Aug 2018 05:37:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 38B05796D1; Wed, 15 Aug 2018 05:37:04 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lv8hi-1fxxN53oby-010JT5; Wed, 15 Aug 2018 07:36:58 +0200 Date: Wed, 15 Aug 2018 07:36:53 +0200 From: "O. Hartmann" To: Pete Wright Cc: Kyle Evans , FreeBSD Current Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection Message-ID: <20180815073653.2d206677@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:b4kO+7Du+ru0HtoGJaEmEo99QSktcJuRLdumIWnj0kddLDk4Tna iwls3x3aUgsbNTkitnvDxMNgqsoytLPl79BeBI4YpfpfCtj6jNodpuycdize4e0P/wmHaew SfhQwJwUAIq56KcRP8bO4GkqVn+IqiXitjpx6IVCr8h6LxfScbu5PzsXaXajcqLgtHeBOXP nW8TYtO0Lp7ISLHJ0MKzw== X-UI-Out-Filterresults: notjunk:1;V01:K0:5K8eGkKIlcI=:6AP9B86R4s23M7dRjyoQqw Xvzr8PVMWJOBMWWwCTuarIO69Lj24ezPYci1m7uDY5jxdcIU3TWzpdR4wGafd/Oj4445ceyY6 dxDK7WfHJZYEbZK6IpE4aOpbMhIejOqbvVKjAqZL/02NIXtclBQxVKq43Mu8337i9STvgNLaV c6ymLgeo+aAaIC2l8ka5a8W+2ju5SY5dk1PJGpWa6RWk09Wx1Metvpln0c1jrbisU8Qui7QBZ mBpSGYAeFZwwV+VtWjM+HT7DsRSf8dHeINd+z9OHF0pJqyXKNraaboH3yJF+HXt/cSSMZuTFa iICNfl2z0C9Q9j189oRRYeqtnagi+hwdgPX9y87esNWeCgUpt8g4U+Vig4xkkE0/iC9kuORer hy2FzXb33a+xVgxrhcB8P+YUdn/QzO5SRMO0OrrfPjjwtjorjHthg1EPeAQoO0jYFN3dTAxlS jItdIbFIYQVeoforgybPntppWhKV4IXnucXdNqv++E3oeHgBq8GsHkUoJjjMiNN1U0BNVYEIa w8ed5R3VN9aahn2bCSAQu57iNIsr2KuYvJi0KWtgkJ3ozUhGuo4yyS5mZtGB1GJf3A4IpYcev JAQxlIFn2lBDrVbHgpVaBz7GFpwIYbuKjgKjI8GvGEBl6m1GygqllrVv/Q/VjUxJh3c8vMBrB iHlUMRIf8Jv09GbzzHxiHTYj+k3lg3pVmwFnxfyn3a8hNx4Xt29Yenn+ZHpxdzvV/XIbXC0V+ l7PC9a2uJq004h/vvoBnd/f1b3lVRIVHXNyWzt1UMOMcHEDEitO+a0+EvEnzOryYv8z9eOg0X yIekbg7 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 05:37:05 -0000 On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrot= e: =20 > >> i also attempted to boot using UEFI but the system hangs very early in= the > >> boot process. i have reverted to legacy mode for now so that i can wo= rk, > >> but am keen to test out any patches or do any other debugging that is > >> needed. =20 > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =3D) =20 > sure thing - the last several lines are: >=20 > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 Similar situation same here on a Lenovo ThinkPad E540, except that the netm= pa message occurs prior to "random: fast provider: "Intel Secure Key RNG" >=20 > at this point it hangs.=C2=A0 let me know if you want me to try booting w= ith=20 > verbose output to dmesg or something. >=20 >=20 > cheers, > -pete >=20 > Other UEFI booting systems (oldish Asrock Z77-Pro4/Pro4-M) throw some infos shortly after booting the kernel which look like the stuff I can see from t= he UEFI loader very early - but it is to fast to catch with the naked eye. The boxes reboot and spinning booting this way.=20 Addon: this is with CURRENT r337832 Last known working version for me is: r337718 From owner-freebsd-current@freebsd.org Wed Aug 15 06:31:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CEBE9107776E for ; Wed, 15 Aug 2018 06:31:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp002.me.com (st13p35im-asmtp002.me.com [17.164.199.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8ED0A7CDF7 for ; Wed, 15 Aug 2018 06:31:07 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp002.me.com by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDH00K00ONVQB00@st13p35im-asmtp002.me.com> for freebsd-current@freebsd.org; Wed, 15 Aug 2018 06:31:06 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDH004VNORREN40@st13p35im-asmtp002.me.com>; Wed, 15 Aug 2018 06:31:06 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808150070 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-15_03:,, signatures=0 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: boot errors since upgrading to 12-current Date: Wed, 15 Aug 2018 09:31:03 +0300 In-reply-to: <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> Cc: freebsd-current@freebsd.org To: tech-lists References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 06:31:08 -0000 > On 15 Aug 2018, at 06:06, tech-lists wrote: >=20 > On 14/08/2018 21:16, Toomas Soome wrote: >>> On 14 Aug 2018, at 22:37, tech-lists wrote: >>> Hello, >>> context: amd64, FreeBSD 12.0-ALPHA1 #0 r337682, ZFS. The system is >>> *not* root-on-zfs. It boots to an SSD. The three disks indicated >>> below are spinning rust. >>> NAME STATE READ WRITE CKSUM storage ONLINE 0 >>> 0 0 raidz1-0 ONLINE 0 0 0 ada1 ONLINE 0 >>> 0 0 ada2 ONLINE 0 0 0 ada3 ONLINE 0 >>> 0 0 >>> This machine was running 11.2 up until about a month ago. >>> Recently I've seen this flash up on the screen before getting to >>> the beastie screen: >>> BIOS drive C: is disk0 BIOS drive D: is disk1 BIOS drive E: is >>> disk2 BIOS drive F: is disk3 BIOS drive G: is disk4 BIOS drive H: >>> is disk5 BIOS drive I: is disk6 BIOS drive J: is disk7 >>> [the above is normal and has always has been seen on every boot] >>> read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >>> 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 = read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >>> 0xcbdb1330, error: 0x31 read 1 from 0 to 0xcbdb1330, error: 0x31 = read 1 from 0 to 0xcbdb1330, error: 0x31 read 1 from 0 to >>> 0xcbdb1330, error: 0x31 >>> the above has been happening since upgrading to -current a month >>> ago >>> ZFS: i/o error - all block copies unavailable ZFS: can't read MOS >>> of pool storage >>> the above is alarming and has been happening for the past couple of >>> days, since upgrading to r337682 on the 12th August. >>> The beastie screen then loads and it boots normally. >>> Should I be concerned? Is the output indicative of a problem? >> Not immediately and yes. In BIOS loader, we do all disk IO with INT13 >> and the error 0x31 is often hinting about missing media or some other >> controller related error. Could you paste the output from loader >> lsdev -v output? >> The drive list appears as an result of probing the disks in >> biosdisk.c. The read errors are from attempt to read 1 sector from >> sector 0 (that is, to read the partition table from the disk). Why >> this does end with error, would be interesting to know, unfortunately >> that error does not tell us which disk was probed. >=20 > Hi Toomas, thanks for looking at this. >=20 > lsdev -v looks like this: >=20 > OK lsdev -v > disk devices: > disk0: BIOS drive C (16514064 X 512): > disk0s1: FreeBSD 111GB > disk0s1a: FreeBSD UFS 108GB > disk0s1b: FreeBSD swap 3881MB >=20 > disk1: BIOS drive D (16514064 X 512): > disk2: BIOS drive E (16514064 X 512): > disk3: BIOS drive F (16514064 X 512): > disk4: BIOS drive G (2880 X 512): > read 1 from 0 to 0xcbde0a20, error 0x31 > disk5: BIOS drive D (2880 X 512): > read 1 from 0 to 0xcbde0a20, error 0x31 > disk6: BIOS drive D (2880 X 512): > read 1 from 0 to 0xcbde0a20, error 0x31 > disk7: BIOS drive D (2880 X 512): > read 1 from 0 to 0xcbde0a20, error 0x31 > OK >=20 > disk4 to disk7 corresponds with da0 to da3 which are sd/mmc devices = without any media in. What made me notice it is it never showed the read = 1 from 0 to $random_value on 11-stable. The system runs 12-current now. Yea, its not about random value, but the rework to process the missing = media is on the way to current, stay tuned:) >=20 > disk1 to disk3 are the hard drives making up ZFS. These are 4TB = Western Digital SATA-3 WDC WD4001FAEX. Well that does explain the problem, if you look on the sizes reported=E2=80= =A6 so your BIOS is reporting wrong sizes, is unable to access whole 4TB = space and the zfs reader is not getting the correct data from the disks = - and is resulting with errors. Thats why you get the errors from = =E2=80=98storage=E2=80=99 pool and yes, this is harmless for boot = because you have separate (small) disk for the boot. rgds, toomas >=20 >>> Since you are getting errors from data pool =E2=80=98storage=E2=80=99,= it does not >>> affect the boot. Why the pool storage is unreadable - it likely has >>> to do about the errors above, but can not tell for sure based on the >>> data presented here=E2=80=A6. >=20 > Thing is, the data pool works fine when boot completes. i.e it loads = read/write and behaves normally. >=20 > thanks, > --=20 > J. From owner-freebsd-current@freebsd.org Wed Aug 15 06:45:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77DC010780C9 for ; Wed, 15 Aug 2018 06:45:01 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: from mail-wr1-x42e.google.com (mail-wr1-x42e.google.com [IPv6:2a00:1450:4864:20::42e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C94167D898 for ; Wed, 15 Aug 2018 06:45:00 +0000 (UTC) (envelope-from grahamperrin@gmail.com) Received: by mail-wr1-x42e.google.com with SMTP id g1-v6so238997wru.2 for ; Tue, 14 Aug 2018 23:45:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=KYRBX1vwYfoqAmGRN+hl8ctmzUGoAqWU1NRzYyWjouo=; b=O+/RdYXmvpRRukmvcOB8r7IeOZOWF8yKkmT5Gv/vNKLDJ7U8Jop3TMVidQ2p5MlaEZ VPDPePmaDESC+hpBUfZZyY0SnNb1VuGrCXcO314/44RsuBve2/ZKFbOoQxDqiq5fM18A fB0hvztWb4tHmUbd2NIQDhoUZ2cV3I/Aflvqs6uogDSKhtAbfbgcD6zC/vMd6w880AuB QrgYaMVEcjAJQp8AyIKNjvk5BsMsYDe5LtBN9qahUZTy/irR80SMm3MvoOh3KlnnHV6c ea0ImN1kuMWn+xri2wo0zJ4lKkZZihZfIhxM9B/CH7S9OnguoYqFIqb8nAIniNw7tN1n nEzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=KYRBX1vwYfoqAmGRN+hl8ctmzUGoAqWU1NRzYyWjouo=; b=ily4ZhHYZeRjmDTNaG5jvL9RUV2fkiaIPD5V/XkU4qYPlWa1n1e0J5FuLqOklJYNgb ZZfutqlGOPI0Ar53bBPK2FCixu78PjHxPQDTNCAqiaZ3ZUPtWZFRJV9P6gGMN1+6teCw MpPu0aFZzHN4xMtzh/7lNe5qmVzXlGXU7unxwvJDmKlu2d6PQOPc2FIOqcYDn/YYzGxv A80r5xIZPhUMjiWgST8oVu+/RDXkwCUmn69eihYK2fGI5rTxttXJKjMH0dTBKm56V0vw y3GgSlhCMwOATxJCQm8qgip8iz7eeQ9dj9GpyrIhTTA5gNu5wPLhUdT6LEHEXKZxjpuZ 453w== X-Gm-Message-State: AOUpUlFMmJBeouDw1lJsG4ws2oEupt8ifxqRDhxABDUmHFM5bJsLLmEc LpgqWhs+7M0rM2oNBaevJSBYDggBKGw= X-Google-Smtp-Source: AA+uWPzkIfIQi3xW/WJRXX8AB0xxS+E/WmcyujQxFbAKCl4v+IiAJg9NR+ev3MSVo65vY1gyHOK3QA== X-Received: by 2002:a5d:694e:: with SMTP id r14-v6mr15061823wrw.278.1534315499270; Tue, 14 Aug 2018 23:44:59 -0700 (PDT) Received: from [192.168.1.231] (host-78-150-66-180.as13285.net. [78.150.66.180]) by smtp.gmail.com with ESMTPSA id j133-v6sm2849931wmd.12.2018.08.14.23.44.58 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 14 Aug 2018 23:44:58 -0700 (PDT) To: FreeBSD Current From: Graham Perrin Subject: npviewer.bin exited on signal 6 (core dumped) with www/linux-flashplayer Message-ID: <8a0c0a2c-332b-32af-221f-9a6ff5ab0b21@gmail.com> Date: Wed, 15 Aug 2018 07:44:57 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 06:45:01 -0000 I don't know whether it's specific to www/linux-flashplayer, but whenever the plug-in loads (in Waterfox or Firefox) there's a dump. This morning, for example (from dmesg, after a few visits to ): pid 34576 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 35395 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36304 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36316 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36359 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36371 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36401 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36414 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36446 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) pid 36459 (npviewer.bin), uid 1004: exited on signal 6 (core dumped) Should I raise a bug against www/linux-flashplayer, or against something else? ---- For one of the exits, with Firefox run in safe mode at the command line: *** NSPlugin Viewer  *** WARNING: grmpf, despite much effort, I could not determine the actual plugin area size... Fontconfig warning: "/usr/local/etc/fonts/local.conf", line 1093: saw number, expected matrix *** glibc detected *** /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin: free(): invalid next size (fast): 0x08104998 *** ======= Backtrace: ========= /lib/libc.so.6(+0x70bb1)[0x289afbb1] /lib/libc.so.6(+0x73611)[0x289b2611] /lib/libstdc++.so.6(_ZdlPv+0x22)[0x2a346df2] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x5951a4)[0x297951a4] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x55e75b)[0x2975e75b] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x55e59c)[0x2975e59c] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x389698)[0x29589698] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x4d499f)[0x296d499f] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x548ab1)[0x29748ab1] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x38448a)[0x2958448a] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x54914c)[0x2974914c] /usr/local/lib/browser_plugins/linux-flashplayer/libflashplayer.so(+0x54fcba)[0x2974fcba] /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin[0x8051a1d] /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin[0x805a335] /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin[0x805ab90] /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin[0x8050e32] /lib/libc.so.6(__libc_start_main+0xe6)[0x28955d26] /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin[0x804b311] ======= Memory map: ======== 08048000-0806c000 r-xp 00026000 00:00 306218     /usr/local/lib/nspluginwrapper/i386/linux/npviewer.bin 0806c000-080f7000 rw-p 0008b000 00:00 0 080f7000-08127000 rw-p 00030000 00:00 0 2806c000-2808b000 r-xp 00024000 00:00 1874517     /compat/linux/usr/lib/ld-2.12.so 2808b000-2808c000 r--p 00024000 00:00 1874517     /compat/linux/usr/lib/ld-2.12.so 2808c000-2808e000 rw-p 00002000 00:00 0 2808e000-2808f000 r--p 05e98000 00:00 1874710     /compat/linux/usr/lib/locale/locale-archive 2808f000-28090000 r--p 00001000 00:00 1876252     /compat/linux/usr/share/locale/en_GB/LC_MESSAGES/libc.mo 28090000-28095000 r--p 00005000 00:00 499790     /compat/linux/usr/share/locale/en_GB/LC_MESSAGES/gdk-pixbuf.mo 28095000-28096000 rw-p 00001000 00:00 0 28096000-2814e000 r-xp 000bb000 00:00 709315     /compat/linux/usr/lib/libgdk-x11-2.0.so.0.2400.23 2814e000-28151000 rw-p 000bb000 00:00 709315     /compat/linux/usr/lib/libgdk-x11-2.0.so.0.2400.23 28151000-2819c000 r-xp 0004c000 00:00 1874593     /compat/linux/usr/lib/libgobject-2.0.so.0.2800.8 2819c000-2819d000 rw-p 0004c000 00:00 1874593     /compat/linux/usr/lib/libgobject-2.0.so.0.2800.8 2819d000-2819e000 rw-p 00001000 00:00 0 2819e000-281a2000 r-xp 00004000 00:00 1874601     /compat/linux/usr/lib/libgthread-2.0.so.0.2800.8 281a2000-281a3000 rw-p 00004000 00:00 1874601     /compat/linux/usr/lib/libgthread-2.0.so.0.2800.8 281a3000-281a4000 rw-p 00001000 00:00 0 281a4000-281fc000 r-xp 0005b000 00:00 6748     /compat/linux/usr/lib/libXt.so.6.0.0 281fc000-28200000 rw-p 0005b000 00:00 6748     /compat/linux/usr/lib/libXt.so.6.0.0 28200000-286a2000 r-xp 004a8000 00:00 709317     /compat/linux/usr/lib/libgtk-x11-2.0.so.0.2400.23 286a2000-286a8000 rw-p 004a8000 00:00 709317     /compat/linux/usr/lib/libgtk-x11-2.0.so.0.2400.23 286a8000-286a9000 rw-p 00001000 00:00 0 286a9000-287c5000 r-xp 0011d000 00:00 1874583     /compat/linux/usr/lib/libglib-2.0.so.0.2800.8 287c5000-287c6000 rw-p 0011d000 00:00 187*** NSPlugin Wrapper *** ERROR: NPP_Destroy() wait for reply: Connection closed *** NSPlugin Wrapper *** ERROR: NPObject proxy 0x80a204860 is no longer valid! JavaScript error: https://d9.flashtalking.com/d9core, line 1: SecurityError: The operation is insecure. From owner-freebsd-current@freebsd.org Wed Aug 15 08:44:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 920171079FBB for ; Wed, 15 Aug 2018 08:44:01 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lf1-x12c.google.com (mail-lf1-x12c.google.com [IPv6:2a00:1450:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D484E80701; Wed, 15 Aug 2018 08:44:00 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lf1-x12c.google.com with SMTP id f18-v6so386518lfc.2; Wed, 15 Aug 2018 01:44:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=Y4/xXPcBepDpm3JIMyWOMgmJPgg7s5s42aI7lZNSS5E=; b=slb+MFXXDoQRMcUYWaRWMm0LYs3hJ/PnfKZGsf2VMM0kywgU+TzMlSk7rrx7W8MO76 tB5ggvRZF4BwQzo18k+s2Vw2CVtPYUYgPzWGzrZoJ6cqgb4wp0xW8hFroB19zFtwde/I Dw+Bc6U6Sraq9UoghbtCXteu2/A+oxn4mhvEf1DEwkOho/mRy76ntPU55/L3I8a2hGIP Oo2aqVYGOE1BpDXRI3Yy0PGU4RyUDexaac6jnSjLUHpaekwOBzBhhLEKWveF5K4y3OrR dMxMTqna8cEAZl+VuViOz4+kGOFW3ME5u6tCq5pz8+HIKfJDT6tydyNGb6b212vC9HCL O+PA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=Y4/xXPcBepDpm3JIMyWOMgmJPgg7s5s42aI7lZNSS5E=; b=CwhMMUsMXBnA1xQCaqLuQ9mirKcSRN+K/dDM9uidXXRHNcimiaGJdrLSeZxIRBvdcC VMAstE82rwf78I3FlE5S/85m+8uQmt6wjvqX9AczdRO0CVNE/2glV0US2KzDDb1IH74k V4IzcSJBN55GTQWOtcqDOQjxj004Lxxd4EDs0KaEXa1NkdNELzJ7xu3+Ntvw1vl/g7BA 1BoMDVKMNih9chQiHR43pvg7qSUJGYuTZjlqNSkDA/aBV6ZiGhSZJF9E9r+XJTGL/lu/ pb7QKqW21pKyD/zPHegMHskjHNo6LoBRY8UX9avKsFHA1VS7rv6I19VXD/4BfLgaqiGU WNCQ== X-Gm-Message-State: AOUpUlHm73aR2gP0RwQ4mFE3yvJqrghTffGqMLp+Kizs/4MQ1wiP0b+s rB7GnohSbGUYOAlRnLPfrn7cACLc X-Google-Smtp-Source: AA+uWPwRCo4KjM6EeAxIIEtNSwsKAZrWfBz5I8ZXAMoT4DBJk3y50ME9T90IbIcI8iIc8h89tnsU3Q== X-Received: by 2002:a19:4ecd:: with SMTP id u74-v6mr15597383lfk.57.1534322639216; Wed, 15 Aug 2018 01:43:59 -0700 (PDT) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id k77-v6sm4412531lfi.46.2018.08.15.01.43.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Aug 2018 01:43:58 -0700 (PDT) Date: Wed, 15 Aug 2018 11:43:57 +0300 From: Vladimir Zakharov To: Pete Wright Cc: Kyle Evans , FreeBSD Current Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection Message-ID: <20180815084357.yv2nnxjnomov5knk@vzakharov> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Operating-System: FreeBSD 12.0-ALPHA1 amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20180716-184-a71513 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 08:44:01 -0000 Hello! On Tue, Aug 14, 2018, Pete Wright wrote: > > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: > > > i also attempted to boot using UEFI but the system hangs very early in the > > > boot process. i have reverted to legacy mode for now so that i can work, > > > but am keen to test out any patches or do any other debugging that is > > > needed. > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =) > sure thing - the last several lines are: > > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 > > at this point it hangs.  let me know if you want me to try booting with > verbose output to dmesg or something. I've updated from r337734 and got the same here with HP Probook 430 G2. Setting efi.rt.disabled=1 in /boot/loader.conf fixed the problem for me. # uname -a FreeBSD vzakharov 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #24 r337829: Wed Aug 15 06:33:54 MSK 2018 root@vzakharov:/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Wed Aug 15 09:56:03 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29255107BF31 for ; Wed, 15 Aug 2018 09:56:03 +0000 (UTC) (envelope-from ohartmann@walstatt.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 BC4C182D2F for ; Wed, 15 Aug 2018 09:56:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: by mailman.ysv.freebsd.org (Postfix) id 80EB8107BF2F; Wed, 15 Aug 2018 09:56:02 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6F97D107BF2E for ; Wed, 15 Aug 2018 09:56:02 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF63782D2E for ; Wed, 15 Aug 2018 09:56:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Ln8Tl-1gNXj02Sc9-00hQlc; Wed, 15 Aug 2018 11:55:59 +0200 Date: Wed, 15 Aug 2018 11:55:58 +0200 From: "O. Hartmann" To: Konstantin Belousov Cc: current@freebsd.org Subject: Re: EFIRT on machines with pcid after r337773 Message-ID: <20180815115550.00f73ab9@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <20180814221755.GV2340@kib.kiev.ua> References: <20180814221755.GV2340@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K1:11OgwAHIV24rgjYVej+h7c/+Fr17kyHRChg822jUsjAKuIYaWGT SB+QPLoeynDsMgblJ/Js5CXZggYDGJy3yFnIY3eTG0WkDQnlmehrgK4owjPmAzSocQg+F9m sU7LEnFP69wvLV1ShPonooERSI9A+32qK1HcF6sbKyr6pdxyEq1Kf4fmFe5m7OCqtWjl/ZQ BJEKWSI3LMZNLne6f5xJA== X-UI-Out-Filterresults: notjunk:1;V01:K0:DOW+B6n/S+o=:dnm6uLI6X/uh3zYsJQiRo7 JrV+jcfgH0xsK8ChkJoYhmuz6FGgWmsDMEE8ihkA0u80oDAmDlIyXOvczWgIMQSUE28ahlzG8 /QoKdRKL4rOlkGx9b19cRnpHaLZ/0xEupnd2NYGOr5XBFCEM+dwdFXYyEqegvT8AREKATCS9I YJDfNaCAYF2G6FpTd/caE0KkPVu4L8Rkug03TonroFlHtE58wT9zKLlfwfNvijCGH+6IquZB8 f378np2KaEDyuWTDW2wzdcuXlF+ykccoRDI4hp4j8SvOcPGhZ1rHm9BW6liw04488Lx4Ma6qc qErkyGnNadF0vRH1Tb5N6sPFDyS8uYQUewGitdnvIH9H7PJLbf8+mV/E5wG2O4olKAUsgl4Pe n/G+OeRTOlaFVBDD2CrTo26LBD41ov2ZoFuKP7lojKSMmzPESZ0W+/s9OPHqshpPX5PuDyspb +VpM6VYoNjQckta3xCZljAzRGOqDURkhmMDk2mwnXw0lkf8pqBi/YaS1I1R5AMBOWXYouDmHd i/WsSA3Xm6AYLnadZec2dXFMCkeBuc9bygtpE4QYk+s6T6Ndpvf3FkZeL6WWNZ4slOljWEGdr cwBlkDyxyTb7Ng/w85qEbnJr5/V08ACQ18FcL/m4oU6Ho9XVJ5uik+RiGsnrJL260QDCCt3O0 H1raOI01oFYUYQuEMKa/gmbyXeECviB/Rw4Yh57fk+EudQ1RuCm6QYecwwBOaRgYMoqOak3ks 6W+X7vQkL7hWf8vzjhRtgeX3JRSg9mlakOIywKUNoXuVkfLsvKSx88IkqluKc8MZ0JMiKYwQq 4MHjQMs X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 09:56:03 -0000 On Wed, 15 Aug 2018 01:17:55 +0300 Konstantin Belousov wrote: > If you use UEFI boot, have EFIRT compiled in kernel (the case of > GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, > and the machine resets during kernel initialization, try this. > > diff --git a/sys/amd64/amd64/pmap.c b/sys/amd64/amd64/pmap.c > index d5d795ab502..c9334eab916 100644 > --- a/sys/amd64/amd64/pmap.c > +++ b/sys/amd64/amd64/pmap.c > @@ -1188,7 +1188,7 @@ pmap_bootstrap(vm_paddr_t *firstaddr) > kernel_pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN; > kernel_pmap->pm_pcids[i].pm_gen = 1; > } > - PCPU_SET(pcid_next, PMAP_PCID_KERN + 1); > + PCPU_SET(pcid_next, PMAP_PCID_KERN + 2); > PCPU_SET(pcid_gen, 1); > /* > * pcpu area for APs is zeroed during AP startup. > @@ -2651,8 +2651,8 @@ pmap_pinit0(pmap_t pmap) > bzero(&pmap->pm_stats, sizeof pmap->pm_stats); > pmap->pm_flags = pmap_flags; > CPU_FOREACH(i) { > - pmap->pm_pcids[i].pm_pcid = PMAP_PCID_NONE; > - pmap->pm_pcids[i].pm_gen = 0; > + pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN + 1; > + pmap->pm_pcids[i].pm_gen = 1; > if (!pti) { > __pcpu[i].pc_kcr3 = PMAP_NO_CR3; > __pcpu[i].pc_ucr3 = PMAP_NO_CR3; > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" Is this patch going to hit the tree soon? Since it seems crucial to UEFI booting systems having options EFIRT set in the kernel (as GENERIC does). Regards, oh From owner-freebsd-current@freebsd.org Wed Aug 15 05:33:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2A7410734AD for ; Wed, 15 Aug 2018 05:33:24 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A49979675; Wed, 15 Aug 2018 05:33:23 +0000 (UTC) (envelope-from o.hartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx001 [212.227.17.190]) with ESMTPSA (Nemesis) id 0M0y8F-1g9oJt3bLz-00v6Fm; Wed, 15 Aug 2018 07:33:18 +0200 Date: Wed, 15 Aug 2018 07:33:16 +0200 From: "O. Hartmann" To: Pete Wright Cc: Kyle Evans , FreeBSD Current Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection Message-ID: <20180815073313.14aca8af@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:BDnpXWrcFYF2OwCsgd8EJ+UBVnpm3VrjYkQ0SNOtwLN6Ihr6ddh VP7RIns1B3oIdnNc0mX43uiUJw+i/JFKdXUWgae5T8A7uoW8a28KnkYJmIYngnLxVhHQlz0 ixLnRTR97mKvFuWlpf/gxoOxUPN0qFi8rGU00LXDAnSILYJS9EMOrr2Dcr7ZQmjVUCpoI54 ekhS5KliC0CGrhUpFunZg== X-UI-Out-Filterresults: notjunk:1;V01:K0:XeMGyRMi99k=:MyoedTtFvceHq1T3jyGxC0 Q012Tx35pHVYEWNeFfgYC1hhxvuWZsF3+5H2lEJDfo1VmFHuIQhvejKRTN3jZtKl7RDBHBL05 ZYlYMhVddSH2Pj3TTFZWShbWvcd6gnNlFv2F8P44k9Qgg/IQeM9KakQxIG4UK6nbovZ8KMS+K 0Ref1ZfSsI31appZ8DwdgSooFaZ0eptB2vnqdDphDXlwUzq26D+tbnYtfnqiUf/tEJxWbeTWo ga48Gbu0uLE6f7NGH5x10YljRm6+ofuvLYcMrEUXOu6NzZMJmDwd8nWGNDDMws7Kl1lnXH6T3 ijzCgdjLPsjzBfb/ZruED3eR3aRKdIUuYaX05KRhJY4XhUkaP7//2i48QKvES+m5hbQLJlvZz 4iiQXobcc+OALaVfJPQPADxf/nZIiREHY4yKVfJNCPQM2e0RvddS/4JGNI0FzcSvSN2/3Znhz NDiJGEoE4Z0JHsKo87JGo42d1Jq4L8s3aoMiuuQy0Rpt8ZHu0gPxiA5htXrSG6LjdMs66ofD4 PezPR0JPOmESToVoP3O0WRIfgnFEvLDo7TDmJWz+L3CypaaFnDJE/K+xrbVHeeB/AfHikexe+ ZmHnp17RRRsrr/hUWWpc314ceM/2etAkgpXKHCLJnkM9WpbIXP1HtTEWrY0CmAhI3EnPQvbSQ Peuy1N71IFa7TskmdOotbWV4OsF181qZj7jHmHgpcOb2wdUapylo4zWVDo6B145pST6zP/Fao /GtgpWLPR1CljuqhpWQj/L74JidELUT22kaBgiAp/+ddvS4ie7/1ci5ueOgox8yxumNV5Zx54 k0/oeju X-Mailman-Approved-At: Wed, 15 Aug 2018 10:04:45 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 05:33:25 -0000 On Tue, 14 Aug 2018 20:41:03 -0700 Pete Wright wrote: > On 8/14/18 6:13 PM, Kyle Evans wrote: > > On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrot= e: =20 > >> i also attempted to boot using UEFI but the system hangs very early in= the > >> boot process. i have reverted to legacy mode for now so that i can wo= rk, > >> but am keen to test out any patches or do any other debugging that is > >> needed. =20 > > Hi Pete, > > > > Where in the process does it hang with UEFI? I can't help much with > > any of your other problems, but I am curious about this one. =3D) =20 > sure thing - the last several lines are: >=20 > random: fast provider: "Intel Secure Key RNG" > kbd1 at kbdmux0 > netmap: loaded module > nexus0 Similar situation same here on a Lenovo ThinkPad E540, except that the netm= pa message occurs prior to "random: fast provider: "Intel Secure Key RNG" >=20 > at this point it hangs.=C2=A0 let me know if you want me to try booting w= ith=20 > verbose output to dmesg or something. >=20 >=20 > cheers, > -pete >=20 > Other UEFI booting systems (oldish Asrock Z77-Pro4/Pro4-M) throw some infos shortly after booting the kernel which look like the stuff I can see from t= he UEFI loader very early - but it is to fast to catch with the naked eye. The boxes reboot and spinning booting this way.=20 From owner-freebsd-current@freebsd.org Wed Aug 15 09:43:17 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D1A8107BA91 for ; Wed, 15 Aug 2018 09:43:17 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 891F9827A7; Wed, 15 Aug 2018 09:43:16 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w7F9hDqp060750; Wed, 15 Aug 2018 11:43:13 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id EBE77ABA; Wed, 15 Aug 2018 11:43:12 +0200 (CEST) Subject: non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection] To: Kyle Evans , Pete Wright Cc: FreeBSD Current References: <68a10054-44a6-c363-8e05-01aa7f8201c3@nomadlogic.org> From: Harry Schmalzbauer Organization: OmniLAN Message-ID: Date: Wed, 15 Aug 2018 11:43:12 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Wed, 15 Aug 2018 11:43:13 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-Mailman-Approved-At: Wed, 15 Aug 2018 10:23:06 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 09:43:17 -0000 Am 15.08.2018 um 06:01 schrieb Kyle Evans: > On Tue, Aug 14, 2018 at 10:56 PM, Pete Wright wrote: >> On 8/14/18 8:45 PM, Kyle Evans wrote: >>> On Tue, Aug 14, 2018 at 10:41 PM, Pete Wright wrote: >>>> On 8/14/18 6:13 PM, Kyle Evans wrote: >>>>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright >>>>> wrote: >>>>>> i also attempted to boot using UEFI but the system hangs very early in >>>>>> the >>>>>> boot process. i have reverted to legacy mode for now so that i can >>>>>> work, >>>>>> but am keen to test out any patches or do any other debugging that is >>>>>> needed. >>>>> Hi Pete, >>>>> >>>>> Where in the process does it hang with UEFI? I can't help much with >>>>> any of your other problems, but I am curious about this one. =) >>>> sure thing - the last several lines are: >>>> >>>> random: fast provider: "Intel Secure Key RNG" >>>> kbd1 at kbdmux0 >>>> netmap: loaded module >>>> nexus0 >>>> >>>> at this point it hangs. let me know if you want me to try booting with >>>> verbose output to dmesg or something. >>>> >>> Are you running GENERIC, or custom config? Any modules loaded? >> >> >> this is a GENERIC kernel using ZFS as well as GELI full disk encryption. >> > Good to know, thanks! Hello, me too here, kind of... Machine resets after nexus0 – took my SLR with 1s exposure time to make sure there's no more GOP output available :-( Haven't tried efi.rt.disabled=1 yet, since I had to spend some time to get the old kernel in place. non-booting kernel inquestion is custom r337804. Like Pete, I'm booting from a ZFS pool utilizing GOP, load_geli, zfs, aesni, nut my machine dosen't hang after "nexus0" but hard resets. The modules loaded don't influence the problem, even with only "kernel" (which is MINIMAL_config + very view devices/filesystems added) loaded, the machine resets after "nexus0". Will try efi.rt.disabled=1 tomorrow. Anyone intending to update a haswell/UEFI machine (Intel DH87MC in my case, with INVPCID microcode updated BIOS) could run into simialr situation I guess, so please make sure to be prepared... My first suspicion were side effects of r337715.  But this is just a wild guess, haven't bisected anything yet. Thanks, -harry From owner-freebsd-current@freebsd.org Wed Aug 15 10:00:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92D09107C22E for ; Wed, 15 Aug 2018 10:00:31 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0924C82F20; Wed, 15 Aug 2018 10:00:30 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w7FA0TUU060933; Wed, 15 Aug 2018 12:00:29 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 743C3AC4; Wed, 15 Aug 2018 12:00:29 +0200 (CEST) Subject: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection To: Vladimir Zakharov , Pete Wright Cc: Kyle Evans , FreeBSD Current References: <20180815084357.yv2nnxjnomov5knk@vzakharov> From: Harry Schmalzbauer Organization: OmniLAN Message-ID: <35402421-cd1f-1d15-a768-5fe9012dc38e@omnilan.de> Date: Wed, 15 Aug 2018 12:00:25 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180815084357.yv2nnxjnomov5knk@vzakharov> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Wed, 15 Aug 2018 12:00:29 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-Mailman-Approved-At: Wed, 15 Aug 2018 10:23:21 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 10:00:31 -0000 Am 15.08.2018 um 10:43 schrieb Vladimir Zakharov: > Hello! > > On Tue, Aug 14, 2018, Pete Wright wrote: >> On 8/14/18 6:13 PM, Kyle Evans wrote: >>> On Tue, Aug 14, 2018 at 7:28 PM, Pete Wright wrote: >>>> i also attempted to boot using UEFI but the system hangs very early in the >>>> boot process. i have reverted to legacy mode for now so that i can work, >>>> but am keen to test out any patches or do any other debugging that is >>>> needed. >>> Hi Pete, >>> >>> Where in the process does it hang with UEFI? I can't help much with >>> any of your other problems, but I am curious about this one. =) >> sure thing - the last several lines are: >> >> random: fast provider: "Intel Secure Key RNG" >> kbd1 at kbdmux0 >> netmap: loaded module >> nexus0 >> >> at this point it hangs.  let me know if you want me to try booting with >> verbose output to dmesg or something. > I've updated from r337734 and got the same here with HP Probook 430 G2. > Setting efi.rt.disabled=1 in /boot/loader.conf fixed the problem for me. > > # uname -a > FreeBSD vzakharov 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #24 r337829: Wed Aug 15 06:33:54 MSK 2018 > root@vzakharov:/home/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 > I can confirm efi.rt.disabled=1 in /boot/loader.conf fixes my problem too, which I posted in reply to Kyle's r337773 hint (non-bootable (UEFI, geli, ZFS) kernel on haswell [Was: Re: CURRENT from today throws lots of ACPI errors, lost HDMI detection]) Machine here is DH87MC+i3-4330 (LynxPoint/Series8+haswell) -harry From owner-freebsd-current@freebsd.org Wed Aug 15 10:32:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F0BD9107D0AB for ; Wed, 15 Aug 2018 10:32:10 +0000 (UTC) (envelope-from freebsd@omnilan.de) 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 9229E8440A for ; Wed, 15 Aug 2018 10:32:10 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: by mailman.ysv.freebsd.org (Postfix) id 57138107D0A7; Wed, 15 Aug 2018 10:32:10 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1D043107D0A0 for ; Wed, 15 Aug 2018 10:32:10 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 93C4684402 for ; Wed, 15 Aug 2018 10:32:09 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id w7FAW8th061132; Wed, 15 Aug 2018 12:32:08 +0200 (CEST) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 438AEACF; Wed, 15 Aug 2018 12:32:08 +0200 (CEST) Subject: Re: EFIRT on machines with pcid after r337773 To: Konstantin Belousov , current@freebsd.org References: <20180814221755.GV2340@kib.kiev.ua> From: Harry Schmalzbauer Organization: OmniLAN Message-ID: Date: Wed, 15 Aug 2018 12:32:05 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180814221755.GV2340@kib.kiev.ua> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-Greylist: ACL 130 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Wed, 15 Aug 2018 12:32:08 +0200 (CEST) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-Mailman-Approved-At: Wed, 15 Aug 2018 10:38:51 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 10:32:11 -0000 Am 15.08.2018 um 00:17 schrieb Konstantin Belousov: > If you use UEFI boot, have EFIRT compiled in kernel (the case of > GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, > and the machine resets during kernel initialization, try this. > > diff --git a/sys/amd64/amd64/pmap.c b/sys/amd64/amd64/pmap.c > index d5d795ab502..c9334eab916 100644 > --- a/sys/amd64/amd64/pmap.c > +++ b/sys/amd64/amd64/pmap.c > @@ -1188,7 +1188,7 @@ pmap_bootstrap(vm_paddr_t *firstaddr) > kernel_pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN; > kernel_pmap->pm_pcids[i].pm_gen = 1; > } > - PCPU_SET(pcid_next, PMAP_PCID_KERN + 1); > + PCPU_SET(pcid_next, PMAP_PCID_KERN + 2); > PCPU_SET(pcid_gen, 1); > /* > * pcpu area for APs is zeroed during AP startup. > @@ -2651,8 +2651,8 @@ pmap_pinit0(pmap_t pmap) > bzero(&pmap->pm_stats, sizeof pmap->pm_stats); > pmap->pm_flags = pmap_flags; > CPU_FOREACH(i) { > - pmap->pm_pcids[i].pm_pcid = PMAP_PCID_NONE; > - pmap->pm_pcids[i].pm_gen = 0; > + pmap->pm_pcids[i].pm_pcid = PMAP_PCID_KERN + 1; > + pmap->pm_pcids[i].pm_gen = 1; > if (!pti) { > __pcpu[i].pc_kcr3 = PMAP_NO_CR3; > __pcpu[i].pc_ucr3 = PMAP_NO_CR3; Thanks a lot! Just wanted to confirm this fixed booting _without_ "efi.rt.disabled=1" for me: ---<>--- Copyright (c) 1992-2018 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994         The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 12.0-FP0_ALPHA1 #0 r337804M: Wed Aug 15 12:14:43 CEST 2018 hes@preed.egn.mo1.omnilan.net:/usr/local/share/deploy-tools/obj/HEAD-HWLYNX/usr/local/share/deploy-tools/HEAD/src/amd64.amd64/ sys/HWLYNX.titan amd64 FreeBSD clang version 6.0.1 (tags/RELEASE_601/final 335540) (based on LLVM 6.0.1) WARNING: WITNESS option enabled, expect reduced performance. VT(efifb): resolution 1600x1200 link_elf_obj: symbol critical_enter undefined KLD file vboxdrv.ko - could not finalize loading info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Core(TM) i3-4330 CPU @ 3.50GHz (3491.98-MHz K8-class CPU)   Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c Stepping=3 Features=0xbfebfbff Features2=0x7fdafbbf   AMD Features=0x2c100800   AMD Features2=0x21   Structured Extended Features=0x27ab   Structured Extended Features3=0xc000000   XSAVE Features=0x1   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID   TSC: P-state invariant, performance statistics real memory  = 17179869184 (16384 MB) avail memory = 16288931840 (15534 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 hardware threads random: unblocking device. ioapic0 irqs 0-23 on motherboard Launching APs: 1 3 2 Timecounter "TSC-low" frequency 1745992496 Hz quality 1000 Cuse v0.1.35 @ /dev/cuse random: entropy device external interface random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80b6f400, 0) error 19 nexus0 efirtc0: on motherboard efirtc0: registered as a time-of-day clock, resolution 1.000000s Curious what this means: smbios0: SMBIOS checksum failed. Has always been there on this LynxPoint/Haswell machine... thanks, -harry From owner-freebsd-current@freebsd.org Wed Aug 15 10:41:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92361107D720 for ; Wed, 15 Aug 2018 10:41:06 +0000 (UTC) (envelope-from zakharov.vv@gmail.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 259188481B for ; Wed, 15 Aug 2018 10:41:06 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DEF2E107D716; Wed, 15 Aug 2018 10:41:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDE3C107D710 for ; Wed, 15 Aug 2018 10:41:05 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 484B584814 for ; Wed, 15 Aug 2018 10:41:05 +0000 (UTC) (envelope-from zakharov.vv@gmail.com) Received: by mail-lj1-x231.google.com with SMTP id p6-v6so615634ljc.5 for ; Wed, 15 Aug 2018 03:41:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=dYyc/PBrHxTKSGj+v5yUNX4QHKEaNVGbcOhIemc4WJM=; b=TqiqaQ2swZ25BVuVfJG0/xSqRIIRcnAaOD9Fvo8rDNro1GfT4L1lBnbWw0B8HwA45n kF8hk39eqHbVXqdN7VcMhFKMQ3eIS7OrW0KvzVdufRF+P6Xnvyvm5W1aMyAGLp/BvcdC vcbtDpBD+GchM+LFM7cSqhkOm2q53BFmj0ua2Kui1M7FjG2CYpuXDC4ks+XGLjRJzqe4 sl7c+L5gkxNTKtMkKt3pgCrBPdg47hBAvtlMu84S69+923kB48ug/5j6MXhQX+q8gQIx IluzUqnbKIF6JmEKeUx3cpoKSnLMMx8ebomGPMzAdymOieJTDGuK46my0TAgkn6BnSBa Hnww== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=dYyc/PBrHxTKSGj+v5yUNX4QHKEaNVGbcOhIemc4WJM=; b=Avo57qqImamsYGEj4zFPne9CoTygKNJ1plMjT8+uPS3aCEJCnlFAJSoOjLee8b9ACZ PSdqUtsV044KBxdGYWoV3WagtU8KgD8DukrAAwZPH3TgLfwb834dFS4ram7u9D8C+Rwy Npf4Q/o7VDMj9MzGgTnWWf5xxoV+BvnrOZyZuvDYR+bCYTGHl9+Aui3jF85dZnnMAcDb pyD015J4YtYGDy39vmRm1Bm8dG0K6V4wjCp7roAvajPROLvMixJ2+9KTjPRBMUQ3h88F TDUBwbFlIkYPgdOCoyy4apvRp4+9lIJ1dor2WEDhQ3sZa09CBSqoESS+se8jTHTqxOSa fNhA== X-Gm-Message-State: AOUpUlEPCZsq5IK9tg9kH7PTfG/vMzbi8IPVx2/2gB90r9OZp3RPfw8+ oUoOcUHLoUlp5wY2XypOwVg= X-Google-Smtp-Source: AA+uWPysFy4BiN+OsF2lD/y/o2POQ+Xan5g/55R6cEdn9gvtq481t3VcMjMJxmT2C4KteT3Pagd+rA== X-Received: by 2002:a2e:6505:: with SMTP id z5-v6mr17091716ljb.62.1534329664035; Wed, 15 Aug 2018 03:41:04 -0700 (PDT) Received: from localhost ([81.19.73.153]) by smtp.gmail.com with ESMTPSA id n19-v6sm3964610lja.87.2018.08.15.03.41.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Aug 2018 03:41:03 -0700 (PDT) Date: Wed, 15 Aug 2018 13:41:02 +0300 From: Vladimir Zakharov To: Konstantin Belousov Cc: current@freebsd.org Subject: Re: EFIRT on machines with pcid after r337773 Message-ID: <20180815104102.4qodbfnvmefyniuc@vzakharov> References: <20180814221755.GV2340@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180814221755.GV2340@kib.kiev.ua> X-Operating-System: FreeBSD 12.0-ALPHA1 amd64 X-PGP-Key: http://vzakharov.ru/pubkey.asc User-Agent: NeoMutt/20180716-185-3fa3f6 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 10:41:06 -0000 On Wed, Aug 15, 2018, Konstantin Belousov wrote: > If you use UEFI boot, have EFIRT compiled in kernel (the case of > GENERIC) or pre-loaded as module, and efirt is not disabled by a tunable, > and the machine resets during kernel initialization, try this. > Patch fixed boot hanging for me on HP ProBook 430 G2. Thanks -- Regards, | "In theory there is no difference between theory Vladimir Zakharov | and practice. In practice there is."- Yogi Berra From owner-freebsd-current@freebsd.org Wed Aug 15 10:43:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F094C107DBFC for ; Wed, 15 Aug 2018 10:43:57 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 9D9AA84B7D for ; Wed, 15 Aug 2018 10:43:57 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id B499821BFD; Wed, 15 Aug 2018 06:43:56 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 15 Aug 2018 06:43:56 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbalan.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=shEyTYKA8cyF9CfW7kVhQOCmbxAJ9v/ya1T+RBffsWg=; b=OQiYvfsf +e7qTdJWymiUqcVcsHrzemtXaNDN6lDiZ/iWgeqCKJCB8RxmZBvZt7Zltov2O/yL acgV4DfKvcOhiR91E35w+T0sUZzxNsUbkFzmUpqNuTQd0HMpsYelH9bcN5tknSzk cvUmglU91GdBc2tZ3VVYokogmD/5qWI6LPbhFP3Jzc+8RlddCQB6ZV5XVYBlibKn UIZgyj+eC4HTL20ROldyjIr7u6w3nA4g3jPm5uCmRyG8NvzAQH/vf8luH0/XCFXi PGumvyHagEz0afT5OEpihRwCyaSvG8V3fGRSHAnktUpPCUaI3/xHaQXm5greEix4 K1dWIHRGsKDV6Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=shEyTYKA8cyF9CfW7kVhQOCmbxAJ9 v/ya1T+RBffsWg=; b=ssAkneNaBHp10aJzhtmYmnff8ZA6N2isUYUI/4o59axeI D7MR0FCJYImHTw1RheyVLmzoPFXTnvQDjrpQI5lN3basLaiA6a49Mx7G6al3WgkK wM1viKjmFvAwUOsbIHrGPtpphqumqOP64SyjUim6kVTviikqnvTydHkMZYkxzkw+ TDbgetO/AeTs778nNyGciX2X2+7A/0e34vXMXC9blAxcMmOxAZzsfWcLf+pTQtV7 VSVE0Ttg5Clb9qk62gxFtNuZpQQLLOCOt9iwGDC4zEw2KX6IeSumPixQlDMiy7Pr hikLqR4Hb6Fw9wYtFRLK4uBVR8Cr5tCy+xKMnJRFg== X-ME-Proxy: X-ME-Sender: Received: from localhost (p5b0714d6.dip0.t-ipconnect.de [91.7.20.214]) by mail.messagingengine.com (Postfix) with ESMTPA id A505310268; Wed, 15 Aug 2018 06:43:55 -0400 (EDT) Date: Wed, 15 Aug 2018 12:43:53 +0200 From: Dhananjay Balan To: Erich Dollansky Cc: freebsd-current@freebsd.org Subject: Re: Ethernet troubles with X230 Message-ID: <20180815104353.afdazuvj37xdcydj@kazhap> References: <20180805101824.qjale5wkzzxozio3@kazhap> <20180805182557.2aabb5d2.freebsd.ed.lists@sumeritec.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180805182557.2aabb5d2.freebsd.ed.lists@sumeritec.com> User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 10:43:58 -0000 On Sun, Aug 05, 2018 at 06:25:57PM +0800, Erich Dollansky wrote: > when I ran into this problem, I delete the IP address 0.0.0.0, kill > dhclient and start a new dhclient. As we used fixed IP addresses for > em0, the problem comes up only on wlan. I tried that, but now the interface just gives up with no carrier, eventhough the cables are plugged in properly. sudo dhclient em0 em0: no link .............. giving up This is with 12.0-ALPHA1 #18 r337684 and my dmesg(8) is filled with em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 em0: TX(0) desc avail = 1024, pidx = 0 - Dhananjay From owner-freebsd-current@freebsd.org Wed Aug 15 10:48:07 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 15E39107E3BF for ; Wed, 15 Aug 2018 10:48:07 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 B5A3685091 for ; Wed, 15 Aug 2018 10:48:06 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 3A3FC20F50; Wed, 15 Aug 2018 06:48:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 15 Aug 2018 06:48:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbalan.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=6xREd/AGARQvoDT6a+z6drIxl46UMh6XysjOVJvJk6M=; b=yFV9gcD3 e9rkGA4mlId8fb30Wikk3CjAdxQt3LzmTOyTsu2C5JC3gnBfQ0WAHw7H1XfFmvPt 2425xOUyfESSLq2YsPjhqWLe8oxctCsP2IzVXHKIAHlRm7v4ZVqAkKvdgxfZt1Gc JyB8y3VLajF15lA2CtOGwmyZKExyOMAixWB1OF6m1jy2Q7//QFYvWFe+z0ZVJqcb a4qf/bhUed0mZwfjtqUAl65ZpmFntNBiavbqYGorDmrpAVrbwkK0ZtiQJA/DIhho RFaH45MSV1lCfgwepukRUoOeE+vL/AWGPsBIdLPeWu/z5CsVHg8yJIDg5ng7aOcp szimKanjf0ObnQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=6xREd/AGARQvoDT6a+z6drIxl46UM h6XysjOVJvJk6M=; b=OPikQd7bTHhVa4SYyxX+d2vQ9b98+TDGHOoESqNtp/ePE UGsXp6xwyEE1ecMzbEuo0bWVqFnTGBgrbv0zJAcd33WZH5JWEHjXrCoKjFpSxuBU CAraS+Ra9mTWdrnKDvYa0MsCYlNX5TGZGSU2P85aRj5vE/Epc3g2wwzgVNCFfR66 XH7bloOfzoDOoje4U7E+VaqrjzQ/lZKRNq199pd4wp2vf7DTtT9CINYrc9fORa+e 8P5SGP9GFxrxDi/za2ejWrd00kqZPhBpVYevAPnXQCs6C8mUuciFfy4cKiq3aUz7 yVWW8xRRTw7lu1BNDqr1rquwcafi1VEFq9FSx4Xzw== X-ME-Proxy: X-ME-Sender: Received: from localhost (p5b0714d6.dip0.t-ipconnect.de [91.7.20.214]) by mail.messagingengine.com (Postfix) with ESMTPA id EE3CE1025D; Wed, 15 Aug 2018 06:48:04 -0400 (EDT) Date: Wed, 15 Aug 2018 12:48:03 +0200 From: Dhananjay Balan To: "R. Tyler Croy" Cc: Michael Butler , tech-lists , freebsd-current@freebsd.org Subject: Re: em0 link fail Message-ID: <20180815104803.yuxvrk76cdgays5s@kazhap> References: <739ef71a-f29f-68ea-955a-fb53c57960a6@protected-networks.net> <8e2bf594-6d7e-477e-836b-4cc4483cb525@protected-networks.net> <64e462dd-16fc-b57f-7bf2-02068d0e24c8@zyxst.net> <7a4607ce-e212-5cba-bc04-1d0abf1a7824@protected-networks.net> <20180726044705.GB5081@grape.lasagna.io> <20180801042034.GD3303@grape.lasagna.io> <20180806184847.GA17800@grape.lasagna.io> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180806184847.GA17800@grape.lasagna.io> User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 10:48:07 -0000 On Mon, Aug 06, 2018 at 11:48:47AM -0700, R. Tyler Croy wrote: > 173.228.82.255 > Aug 5 23:46:18 strawberry dhclient: New Routers (em1): 173.228.82.1 > Aug 5 23:46:19 strawberry syslogd: last message repeated 1 times > Aug 5 23:49:35 strawberry dhclient[12645]: send_packet: No route to host > > > At the tail end of the syslog I was trying to get a new lease but was then > unable to get a lease or restore functionality to the em1 device. > > > This is rather perplexing to me, but I'm not savvy enough to figure out how to > further be a useful debugger here :-/ > > Any suggestions would be appreciated! It seems that I am hitting similiar problems with em(4) on my X230. https://lists.freebsd.org/pipermail/freebsd-current/2018-August/070490.html - Dhananjay From owner-freebsd-current@freebsd.org Wed Aug 15 11:22:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DB76107FE56 for ; Wed, 15 Aug 2018 11:22:25 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 CB16D868FC for ; Wed, 15 Aug 2018 11:22:24 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 49C7521C08; Wed, 15 Aug 2018 07:22:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 15 Aug 2018 07:22:24 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=gkhbcZz8LmAAFn2pYCkBJmK4tkhKv TH/uhPgilOl7uM=; b=KgDKIFjIFtKyvE1mMWWAlstJrYKx0Au94rDYQ/Nzw7gZ6 gyPVUwln83K/qXTSRGCrFfoT9o5Hf7DcdK2I+KgW/sbXtsX7t6knp+YQGKk2Q+FB 98d3jFc8KdtZz+jIiBorZC3+p/3sAwD7jaI2U5BgnVu7IGDaxFkIFXXNn8umBwxQ a/zC9u1dhE85qU12SoNd7e68wSN32om+mqN/V8H8dIE0eDl0lR7bkq2TZvtX6I7L 7rdh1NbWvLajfW45DXtc9K6K0WeYFIPe6v9Fio+A6Bd2G5oOAA/vK2r2a9EarxP+ Sx+gXDIKXfce22SMAC5F59WnxicnFYmE1WUulKXhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=gkhbcZ z8LmAAFn2pYCkBJmK4tkhKvTH/uhPgilOl7uM=; b=OZ8uYnoOJ04V7cwe4owPaJ Qy2Gi/s2srGAxOFEDViqNW1gevuBSWqTpsxtFL2b3e/i8pJFVsKt36suPFrPlyij 4ouAZShAgb4WOBZGHWkUKWTM41KpiCRNQNm7V8DsDUGhfEQjLVKXgKznamZ3TcCy BCbWcmKpuocZgxTmVyp3TacwA+oPeGlCoFWO6pnuzHrYDzcLcQ86g3v1o/4+7WDX DA4O5D2GD2dGQY3pic07/hqd0onJil3VKw2Pz4zuZvefGynAF+bb7jeKzXPfgmAV G4dsolaV9mxoMLobAAh59WbvsOSJOJgBBbQ4iypApDzQUfnXQIw0u8harW8/vnhw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id A130B1028B; Wed, 15 Aug 2018 07:22:23 -0400 (EDT) Subject: Re: boot errors since upgrading to 12-current To: Toomas Soome Cc: freebsd-current@freebsd.org References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> From: tech-lists Organization: none Message-ID: Date: Wed, 15 Aug 2018 12:22:22 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 11:22:25 -0000 Hello Toomas, On 15/08/2018 07:31, Toomas Soome wrote: > Well that does explain the problem, if you look on the sizes reported… > so your BIOS is reporting wrong sizes, is unable to access whole 4TB > space and the zfs reader is not getting the correct data from the disks Do you know why this was not happening on 11-stable but is happening on 12-current? The BIOS has not been modified since the machine was bought back in 2014. Once booted, the whole drives in the pool are accessible: Filesystem Size Used Avail Capacity Mounted on storage 5.8T 1.1T 4.8T 18% /storage The pool is raidz1-0 so this is the available size I'd expect with 3 x 4Tb drives. Am I incorrect here? > - and is resulting with errors. Thats why you get the errors from > ‘storage’ pool and yes, this is harmless for boot because you have > separate (small) disk for the boot. Is it also harmless for the 'storage' pool ? thanks, -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 11:50:13 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F32AB1080949 for ; Wed, 15 Aug 2018 11:50:12 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A68A888004 for ; Wed, 15 Aug 2018 11:50:12 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 4406713EFB for ; Wed, 15 Aug 2018 11:50:12 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f180.google.com with SMTP id p6-v6so740352ljc.5 for ; Wed, 15 Aug 2018 04:50:12 -0700 (PDT) X-Gm-Message-State: AOUpUlHk7CCChf44M1Pk4xvkPWyhdKgFvHW6Y5uZsiYn7qEUFcDSgwGT tIOOaPL/uGilsyhaQ3aMnWKkBvB/Po3AKNVc86M= X-Google-Smtp-Source: AA+uWPwJ2rBkL+SM5WQpS+rLBO5vYg+rUW06n2i/yMXD0kIzz0DbM2EHOgp63FG9TQI4HF2OsmqL+/b8eem7d4fLgW8= X-Received: by 2002:a2e:8617:: with SMTP id a23-v6mr19252354lji.43.1534333810822; Wed, 15 Aug 2018 04:50:10 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 04:49:50 -0700 (PDT) In-Reply-To: References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> From: Kyle Evans Date: Wed, 15 Aug 2018 06:49:50 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: boot errors since upgrading to 12-current To: tech-lists Cc: Toomas Soome , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 11:50:13 -0000 On Wed, Aug 15, 2018 at 6:22 AM, tech-lists wrote: > Hello Toomas, > > On 15/08/2018 07:31, Toomas Soome wrote: >> >> Well that does explain the problem, if you look on the sizes reported=E2= =80=A6 so >> your BIOS is reporting wrong sizes, is unable to access whole 4TB space = and >> the zfs reader is not getting the correct data from the disks > > > Do you know why this was not happening on 11-stable but is happening on > 12-current? > > The BIOS has not been modified since the machine was bought back in 2014. > Perhaps r335245, which fixed a logical error and completely changed the calculations for this stuff and possibly sent you on dramatically different path. There's not too many commits to this area that haven't yet landed back in stable/11, fortunately. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Aug 15 12:20:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7CAA010822DB for ; Wed, 15 Aug 2018 12:20:23 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 279E58945E; Wed, 15 Aug 2018 12:20:22 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 2C80E21B62; Wed, 15 Aug 2018 08:20:22 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 15 Aug 2018 08:20:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=INkCkn78fGW+eDXPvZBi2d2J3boXk MhQR4o7rXrUBKk=; b=HBVXLFTMzlxNbCSYl5SVY0DNhjmqaBg9MEHv2SH/odRTo OjiOJuVpWSXTzmxcPPQyx4p5Htwt50kBCEU9yfprWLAMOz2ooFg4aVvQYL7ZXWTv efeWLv69SSKdD4es1ehiCriOfrZ6Jg5tiau9mNMJam5egG3prV70gZ/H/MBqqHrH ldaGHvspXOLfMr3dC1AQ79pom3weTQZOkKY/wiim1uc0KWxdFzu7mjObW56kwLLa X69HV67IwzlWpqEIRUnEIE6Lsjspy5NOlWjCUkMLUM/CBLpqE6WgwtekXb5YPWB9 hazqbwXPwY35//P+zhzlV0FT+BG9VRyH+hXx1+z6w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=INkCkn 78fGW+eDXPvZBi2d2J3boXkMhQR4o7rXrUBKk=; b=NkxsFS65AGxC4aGz6w9N3z ctHfV5N6gspO0/Dt0YAYXnh1l8pIyWjtsvZotzDmn9p0xogbsF+kddHlvwxqVP/n hqI/LPeq+QqsVVWsXH1lT73u1M3ktGf/tv5cqA1l+FRhw7ZBci02qTdNd+Lc0Mx9 i+NDNjceQw/TSwGwXUh6RZK0zxW+j8l6Hs1+J+Z1N9TLsXpp2CnT7EnXkO7kkp95 2q0CVFw8xtejGNbcwt3hrsMiDnoYqFp6sqXtjE+jYoFx1NV5NvMcfYSQAh4PXbPz rxzRs01evSfMRN52PpiYfWWDGAmNgfEF1p2BZWHD7+lhlJdXprtFm6RB5/uVSWMw == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 615F61025D; Wed, 15 Aug 2018 08:20:21 -0400 (EDT) Subject: Re: boot errors since upgrading to 12-current To: Kyle Evans Cc: Toomas Soome , FreeBSD Current References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> From: tech-lists Organization: none Message-ID: Date: Wed, 15 Aug 2018 13:20:19 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 12:20:23 -0000 On 15/08/2018 12:49, Kyle Evans wrote: > On Wed, Aug 15, 2018 at 6:22 AM, tech-lists wrote: >> Hello Toomas, >> >> On 15/08/2018 07:31, Toomas Soome wrote: >>> >>> Well that does explain the problem, if you look on the sizes reported… so >>> your BIOS is reporting wrong sizes, is unable to access whole 4TB space and >>> the zfs reader is not getting the correct data from the disks >> >> >> Do you know why this was not happening on 11-stable but is happening on >> 12-current? >> >> The BIOS has not been modified since the machine was bought back in 2014. >> > > Perhaps r335245, which fixed a logical error and completely changed > the calculations for this stuff and possibly sent you on dramatically > different path. There's not too many commits to this area that haven't > yet landed back in stable/11, fortunately. > > Thanks, > > Kyle Evans > Thank you Toomas and Kyle for the clarifications. -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 12:40:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 851951082CC9 for ; Wed, 15 Aug 2018 12:40:10 +0000 (UTC) (envelope-from david@catwhisker.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 1C7DB89F90 for ; Wed, 15 Aug 2018 12:40:10 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id D1DE21082CC8; Wed, 15 Aug 2018 12:40:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C08DD1082CC7 for ; Wed, 15 Aug 2018 12:40:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 00EF189F8F for ; Wed, 15 Aug 2018 12:40:08 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7FCe1rd056784; Wed, 15 Aug 2018 12:40:01 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7FCe0kP056783; Wed, 15 Aug 2018 05:40:00 -0700 (PDT) (envelope-from david) Date: Wed, 15 Aug 2018 05:40:00 -0700 From: David Wolfskill To: current@freebsd.org Cc: kevans@frreebsd.org Subject: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" Message-ID: <20180815124000.GB1190@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org, kevans@frreebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="PTtevmzQfeILqsiI" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 12:40:10 -0000 --PTtevmzQfeILqsiI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I'm tracking head/amd64 daily twice on each of two machines: my "build machine" ("freebeast") and my laptop, each first using the traditional Forth loader, then (on a different slice), the Lua loader. Each is using BIOS and MBR (not UEFI; not GPT). Yesterday's update was to r337738, and was uneventful for each of the four environments. Today's was to r337834, and was uneventful for the build machine (both Forth and Lua loaders -- though there remains no means of interacting with the loader on the build machine if it's booted using the Lua loader). The laptop had no issues using the Forth loader, but the boot process was ... severely abbreviated ... using the Lua loader. I don't have a serial consoloe on the laptop, so I snapped a photo; it may be found at . As the name suggests, the final message was: BTX halted at which point, I found no way to get the laptop to respond to anything but a power cycle. Additional information (including, e.g., a verbose dmesg.boot from the laptop running: FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r337834M= /337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root@g1-215.catwhisker.or= g:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 -- using the Forth loader) may be found at . Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --PTtevmzQfeILqsiI Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt0HyBfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7heXRgf+IuuphZsRrxDdewRXzYjyZ0GbWMDo/XHfSB3ds8rEjl0K7VaJ2JNZswJO raOQMWkcQ5ne7IeQCrxU755I5byFBi5aQUeUQ9/QuqXVe6KSkw+CblDvugCgKVjQ qpFsV69ZfEMp40o7juUpwYpnPIhXC7QMTXRaJ6HbjnfSYt6oyXvw6fnyrhYWgo9G 2x2Hl4w5JsXkIoYcc9izFfECw6zL6upJtpt/IEHTlVxq+qmxZP3dH6NK2yZkPkkf YyM7LBznXWhB3d/sAcQ1gUiwJanA2VQ5k8hdTTtwfxtTNrDC2ZMH3RedxpzA20to Vz7t4FSZPAZkKbrkYHiUZ7Z//jhRkA== =fcyS -----END PGP SIGNATURE----- --PTtevmzQfeILqsiI-- From owner-freebsd-current@freebsd.org Wed Aug 15 12:42:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E99541082EF3 for ; Wed, 15 Aug 2018 12:42:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 961928A1E8 for ; Wed, 15 Aug 2018 12:42:18 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDI00100320FR00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Wed, 15 Aug 2018 11:41:21 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDI00HR234U2W00@st13p35im-asmtp001.me.com>; Wed, 15 Aug 2018 11:41:21 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808150128 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-15_04:,, signatures=0 Content-type: text/plain; charset=utf-8 MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: boot errors since upgrading to 12-current From: Toomas Soome In-reply-to: Date: Wed, 15 Aug 2018 14:41:17 +0300 Cc: freebsd-current@freebsd.org Content-transfer-encoding: quoted-printable Message-id: References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> To: tech-lists X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 12:42:19 -0000 > On 15 Aug 2018, at 14:22, tech-lists wrote: >=20 > Hello Toomas, >=20 > On 15/08/2018 07:31, Toomas Soome wrote: >> Well that does explain the problem, if you look on the sizes = reported=E2=80=A6 so your BIOS is reporting wrong sizes, is unable to = access whole 4TB space and the zfs reader is not getting the correct = data from the disks >=20 > Do you know why this was not happening on 11-stable but is happening = on 12-current? The current has few bits updated about diagnostics (that concerns the = 0x31 error messages), the storage pool issue depends on how the pool is = filled with data - once the BIOS limits are exceeded, we will be unable = to read those data blocks and the errors will appear... >=20 > Once booted, the whole drives in the pool are accessible: >=20 > Filesystem Size Used Avail Capacity Mounted on > storage 5.8T 1.1T 4.8T 18% /storage >=20 > The pool is raidz1-0 so this is the available size I'd expect with 3 x = 4Tb drives. Am I incorrect here? >=20 >> - and is resulting with errors. Thats why you get the errors from = =E2=80=98storage=E2=80=99 pool and yes, this is harmless for boot = because you have separate (small) disk for the boot. >=20 > Is it also harmless for the 'storage' pool ? >=20 Yes, well the catch there is that with this machine, you can not use = those 4TB disks fo boot pool, unless you will create separate smaller = partition within BIOS limits. But if you do not plan to make it = bootable, the data pool does not concern boot loader other than we do = probe disk devices to detect [boot] pool configuration and to make it = possible to boot from different pool. rgds, toomas= From owner-freebsd-current@freebsd.org Wed Aug 15 12:53:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9ABBA1083686 for ; Wed, 15 Aug 2018 12:53:28 +0000 (UTC) (envelope-from kevans@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 3A78C8ADCA for ; Wed, 15 Aug 2018 12:53:28 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id F345F1083685; Wed, 15 Aug 2018 12:53:27 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E1E1C1083684 for ; Wed, 15 Aug 2018 12:53:27 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8AB7A8ADC9 for ; Wed, 15 Aug 2018 12:53:27 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com [209.85.208.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 1EC7214628 for ; Wed, 15 Aug 2018 12:53:27 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f177.google.com with SMTP id y17-v6so867396ljy.8 for ; Wed, 15 Aug 2018 05:53:27 -0700 (PDT) X-Gm-Message-State: AOUpUlHbW9z6Od2jUY6uudiNC6qrPf8IKMAcM5r9COowEVgQHNVqlQaE A6KCRklLwOSDrdhSh0mgYvvN1qYhfI2gvjGrxoU= X-Google-Smtp-Source: AA+uWPxzLQ7wWisbyVlFz/IbcIfzcvtddRAczZwA1/XuHvDANg7fvdZ4pMhZtOmagdjtqabUKZA6p8yHT8PUmYkedyI= X-Received: by 2002:a2e:2b0e:: with SMTP id q14-v6mr17598765lje.147.1534337605750; Wed, 15 Aug 2018 05:53:25 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 05:53:05 -0700 (PDT) In-Reply-To: <20180815124000.GB1190@albert.catwhisker.org> References: <20180815124000.GB1190@albert.catwhisker.org> From: Kyle Evans Date: Wed, 15 Aug 2018 07:53:05 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" To: David Wolfskill , current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 12:53:28 -0000 On Wed, Aug 15, 2018 at 7:40 AM, David Wolfskill wrote: > I'm tracking head/amd64 daily twice on each of two machines: my "build > machine" ("freebeast") and my laptop, each first using the traditional > Forth loader, then (on a different slice), the Lua loader. > > Each is using BIOS and MBR (not UEFI; not GPT). > > Yesterday's update was to r337738, and was uneventful for each of > the four environments. > > Today's was to r337834, and was uneventful for the build machine (both > Forth and Lua loaders -- though there remains no means of interacting > with the loader on the build machine if it's booted using the Lua > loader). > > The laptop had no issues using the Forth loader, but the boot process > was ... severely abbreviated ... using the Lua loader. > > I don't have a serial consoloe on the laptop, so I snapped a photo; it > may be found at > . > > As the name suggests, the final message was: > > BTX halted > > at which point, I found no way to get the laptop to respond to anything > but a power cycle. Interesting. It seems to have died in the middle of loading a module... any insight into what that module may have been? Any way to hack beastie_disable="YES" into loader.conf(5) and see if that changes things? The only real change in lualoader in the past day was the update to 5.3.5 and removal of some float stuff- the former was pretty tiny, and the latter was unused cruft anyways. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Aug 15 13:00:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B004A108391A for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@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 4C9768B08E for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 116EE1083918; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 004E71083917 for ; Wed, 15 Aug 2018 13:00:30 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A55E68B085 for ; Wed, 15 Aug 2018 13:00:29 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-lj1-f180.google.com (mail-lj1-f180.google.com [209.85.208.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id 43AA61462A for ; Wed, 15 Aug 2018 13:00:29 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-lj1-f180.google.com with SMTP id p6-v6so884061ljc.5 for ; Wed, 15 Aug 2018 06:00:29 -0700 (PDT) X-Gm-Message-State: AOUpUlECeAEVt1GoXDp1lqkAiiJoFf/rzd4JfosxNoio2rNVDzww1Its Zgr8wgToDDTu+k3ltnB4JwMgYHpzlaEhk3NsyBw= X-Google-Smtp-Source: AA+uWPyzG4+oM2bA9RSN5H8FfehUSkGSaC0XCRYjk6vVaN5ptwTvE25WH+wkKISXUCzFMuefihRhdiiKAarYd60s+XQ= X-Received: by 2002:a2e:144f:: with SMTP id 15-v6mr19194535lju.122.1534338027915; Wed, 15 Aug 2018 06:00:27 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a2e:5742:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 06:00:07 -0700 (PDT) In-Reply-To: References: <20180815124000.GB1190@albert.catwhisker.org> From: Kyle Evans Date: Wed, 15 Aug 2018 08:00:07 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" To: David Wolfskill Cc: current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:00:30 -0000 On Wed, Aug 15, 2018 at 7:53 AM, Kyle Evans wrote: > On Wed, Aug 15, 2018 at 7:40 AM, David Wolfskill wrote: >> I'm tracking head/amd64 daily twice on each of two machines: my "build >> machine" ("freebeast") and my laptop, each first using the traditional >> Forth loader, then (on a different slice), the Lua loader. >> >> Each is using BIOS and MBR (not UEFI; not GPT). >> >> Yesterday's update was to r337738, and was uneventful for each of >> the four environments. >> >> Today's was to r337834, and was uneventful for the build machine (both >> Forth and Lua loaders -- though there remains no means of interacting >> with the loader on the build machine if it's booted using the Lua >> loader). >> >> The laptop had no issues using the Forth loader, but the boot process >> was ... severely abbreviated ... using the Lua loader. >> >> I don't have a serial consoloe on the laptop, so I snapped a photo; it >> may be found at >> . >> >> As the name suggests, the final message was: >> >> BTX halted >> >> at which point, I found no way to get the laptop to respond to anything >> but a power cycle. > > Interesting. It seems to have died in the middle of loading a > module... any insight into what that module may have been? > > Any way to hack beastie_disable="YES" into loader.conf(5) and see if > that changes things? > To be clear- the test I'm interested in will not be productive unless beastie_disable="YES" is present in loader.conf or the environment before lualoader engages at all. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Wed Aug 15 13:04:58 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C5211083CFD for ; Wed, 15 Aug 2018 13:04:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BF0408B779; Wed, 15 Aug 2018 13:04:57 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7FD4lqM007544 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Aug 2018 16:04:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7FD4lqM007544 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7FD4l4Q007543; Wed, 15 Aug 2018 16:04:47 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 15 Aug 2018 16:04:47 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180815130447.GZ2340@kib.kiev.ua> References: <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180815005106.69402d23@bsd64.grem.de> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:04:58 -0000 On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: > Reviving this old thread, since I just updated to r337818 and a similar > problem is happening again. Since the fix in r334799 (review > https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, > so maybe this is related > (https://svnweb.freebsd.org/base?view=revision&revision=334799). > > Please see the screenshot of the panic below: > https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 > > This is me not digging any deeper, hoping that this is something > obvious. Please let me know if you need more input. I do not see how recent mp_machdep.c changes could affect this. Can you try newest kernel but old loader ? From owner-freebsd-current@freebsd.org Wed Aug 15 13:52:41 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EE48B108561F for ; Wed, 15 Aug 2018 13:52:40 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 495E98DE48 for ; Wed, 15 Aug 2018 13:52:39 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 72107 invoked by uid 89); 15 Aug 2018 13:52:38 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.231.99) by mail.grem.de with ESMTPA; 15 Aug 2018 13:52:38 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) From: Michael Gmelin X-Mailer: iPhone Mail (15G77) In-Reply-To: <20180815130447.GZ2340@kib.kiev.ua> Date: Wed, 15 Aug 2018 15:52:37 +0200 Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20180603165500.361ec894@bsd64.grem.de> <20180603150423.GQ3789@kib.kiev.ua> <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> To: Konstantin Belousov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:52:41 -0000 > On 15. Aug 2018, at 15:04, Konstantin Belousov wrote= : >=20 >> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >> Reviving this old thread, since I just updated to r337818 and a similar >> problem is happening again. Since the fix in r334799 (review >> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, >> so maybe this is related >> (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799). >>=20 >> Please see the screenshot of the panic below: >> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>=20 >> This is me not digging any deeper, hoping that this is something >> obvious. Please let me know if you need more input. >=20 > I do not see how recent mp_machdep.c changes could affect this. > Can you try newest kernel but old loader ? I will try (but that will take a while). Oh, also, it still boots in save mo= de/with smp disabled. -m= From owner-freebsd-current@freebsd.org Wed Aug 15 13:52:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16D791085625 for ; Wed, 15 Aug 2018 13:52:42 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 AF4E88DE61; Wed, 15 Aug 2018 13:52:41 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 1037421B54; Wed, 15 Aug 2018 09:52:41 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 15 Aug 2018 09:52:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=yXudO/UC1RzeGcKPcmJmyYyEydKrp TO6P2p3ymhet4M=; b=HxnncOZvYeFoH4JX5d/DvmfPvKQDj8TP1qbgkqBxAsdHa Dyloa8T/H00eyg9AjhLophjc/GIz5ydeHKGkBjOXjcUPm/xVx6+MMSPrDHORHlEu M4hh1j2NMxSmDNTD88VF8CUQ2fejKALh740kUFRxKldZ/EUiFy8ZQ0yjj9jgFS/L s6tKgUMmiqKtzOb5tGMqwFaKIYK+Uj4NDv+kKSHtLnp5u+zUdoLwpZVSWXntRxRv 80e1sCmDJGaFMbYxqaEkp18a2Nh90vVK00Zz2jPdLyCBk+8Vj6kVpNOPmQRRv+Aa HJSiIm54goQelCOOcPeTHFGQptHqMnBefczKFt84Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=yXudO/ UC1RzeGcKPcmJmyYyEydKrpTO6P2p3ymhet4M=; b=AQaSXhDRR+PTiSSZebdfSB Opba3OrI1EUDGELm0UfTooAMcjIYpXKczOg0L8sPLzCiOwuMngOTOahQAZppAU46 A9AhyghnRi81YxofRzOFcUQ9Axw5nukaf7kRvGqKbuKSCO78qCNYRNOTl2TaqiUn pry2Ce9Y0P1V6SMBfG8tdUfaTE9so/u6PQ9bw+dOxe/10qPOpMuiA2L4GaP3E0Qr yTv5bT+UvzM7W6amqrV0Dqybb+45EIEjLOpVDY2btWGVRY0gw4B/KmkcxplxDIw9 99xSgawSTJUQFEhV/rxzL0c6AnjDW+aqY1amRzThdJncPLYMQpf5XhqeUWadiMgg == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 400001028B; Wed, 15 Aug 2018 09:52:40 -0400 (EDT) Subject: Re: boot errors since upgrading to 12-current From: tech-lists To: Kyle Evans Cc: Toomas Soome , FreeBSD Current References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> Organization: none Message-ID: Date: Wed, 15 Aug 2018 14:52:39 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:52:42 -0000 On 15/08/2018 13:20, tech-lists wrote: > On 15/08/2018 12:49, Kyle Evans wrote: >> On Wed, Aug 15, 2018 at 6:22 AM, tech-lists wrote: >>> Hello Toomas, >>> >>> On 15/08/2018 07:31, Toomas Soome wrote: >>>> >>>> Well that does explain the problem, if you look on the sizes >>>> reported… so >>>> your BIOS is reporting wrong sizes, is unable to access whole 4TB >>>> space and >>>> the zfs reader is not getting the correct data from the disks >>> >>> >>> Do you know why this was not happening on 11-stable but is happening on >>> 12-current? >>> >>> The BIOS has not been modified since the machine was bought back in >>> 2014. >>> >> >> Perhaps r335245, which fixed a logical error and completely changed >> the calculations for this stuff and possibly sent you on dramatically >> different path. There's not too many commits to this area that haven't >> yet landed back in stable/11, fortunately. >> >> Thanks, >> >> Kyle Evans >> > > Thank you Toomas and Kyle for the clarifications. > addendum to this - installed new world and kernel r337835 and the zfs warning at boot seems to have disappeared. Something else odd has started happening though, will make a new email for it - usb keyboard no longer functioning at the beastie menu, but functions when boot completes. -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 13:55:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E483610857C4 for ; Wed, 15 Aug 2018 13:55:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60CB68E107; Wed, 15 Aug 2018 13:55:42 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7FDtVNO021187 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 15 Aug 2018 16:55:34 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7FDtVNO021187 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7FDtVKJ021186; Wed, 15 Aug 2018 16:55:31 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 15 Aug 2018 16:55:31 +0300 From: Konstantin Belousov To: Michael Gmelin Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180815135531.GA2340@kib.kiev.ua> References: <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:55:43 -0000 On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: > > > > On 15. Aug 2018, at 15:04, Konstantin Belousov wrote: > > > >> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: > >> Reviving this old thread, since I just updated to r337818 and a similar > >> problem is happening again. Since the fix in r334799 (review > >> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, > >> so maybe this is related > >> (https://svnweb.freebsd.org/base?view=revision&revision=334799). > >> > >> Please see the screenshot of the panic below: > >> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 > >> > >> This is me not digging any deeper, hoping that this is something > >> obvious. Please let me know if you need more input. > > > > I do not see how recent mp_machdep.c changes could affect this. > > Can you try newest kernel but old loader ? > > I will try (but that will take a while). Oh, also, it still boots in save mode/with smp disabled. Right, this is because the access to that address through DMAP is only needed when configuring AP startup resources. Also, I think it is safe to suggest that the bisect is needed. From owner-freebsd-current@freebsd.org Wed Aug 15 13:57:01 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BE7AA108587B for ; Wed, 15 Aug 2018 13:57:01 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (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 4E0898E1E4 for ; Wed, 15 Aug 2018 13:57:01 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DBF8821B6F for ; Wed, 15 Aug 2018 09:57:00 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 15 Aug 2018 09:57:00 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=3uSpaN8LXuTNwaBifeftbf3bWyuOMsSUmwITkf3DDEA=; b=JFh+zYke ueCcq8IljXLtqQsgG3+gEgiDB7ipHYV/dXVAgKk3aNXHVGkCXJeSvc/itA6zhAJr IOO22MWDK+SCGTLJUVpnKaNpEUro9tZv3HBJ6r8H2SQRsb2IUSJuPlzqRkmQFFTq fJbwqewEhcLpwj1eWE8Ls662aefXcmAx+rNt3/A3s5bwzRynp9B0BRkIAFXbTzjM fKq4zxhmWDGT1+/cJLO8c5Ctx8bIiK597egjFsM00DPu2ehSV5KEh6dWwJNFrEUT hPXCNrBPDFFxff3S8WJ/Edmk8da+K4b4/FRKEEKbQB1c+7ZTXmrNa+2Cr7Qh3kCM IRPDBQjGoNcpHw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=3uSpaN8LXuTNwaBifeftbf3bWyuOM sSUmwITkf3DDEA=; b=IWTOXxpXhgNAu/olZkrXhsX+66Zs+JVtx3uAGQmkKKEFE y1qmyqFl4HmxWLxIhzFbKAoyUZQCsPPRPBSu57PKnwpnLkg95uwoWxdn3yvo5apH fHi+oQmNWQJOnhSupVH2Yi9Bl5KT2KHChhh1SK4K+Rf9A0Zrq5Im/u1o+yKF3cxh Awqc+0n4SYo4eTFWLeChnAXflMStQTXKLBgP/g0/8h1od6i4/Xq423pvly+WTcmf rWEc2IFjsuc94zqzYwzhO5K9M2QsuI1oA0HOld//zkCs98NkqwGIsFjvQiSOehqj fsKMSIoES74T9aLQIW3Da1LoV24TZg5EvJm6ijZlg== X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 457FB10255 for ; Wed, 15 Aug 2018 09:57:00 -0400 (EDT) To: FreeBSD Current From: tech-lists Subject: usb keyboard nonfunctional at beastie menu after r337835 Organization: none Message-ID: Date: Wed, 15 Aug 2018 14:56:59 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 13:57:01 -0000 Hi, context: amd64 FreeBSD 12.0-ALPHA1 #0 r337835 USB keyboard is non-functional after r337835. It's fine when booting completes. I'm happy to do more diagnostics if anyone can suggest any. thanks, -- J. From owner-freebsd-current@freebsd.org Wed Aug 15 15:18:38 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 60CDE105B69E for ; Wed, 15 Aug 2018 15:18:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EA66291DE6; Wed, 15 Aug 2018 15:18:37 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDI00G00CWXON00@st13p35im-asmtp001.me.com>; Wed, 15 Aug 2018 15:18:20 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDI00BLVD6G7650@st13p35im-asmtp001.me.com>; Wed, 15 Aug 2018 15:18:20 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=2 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808150163 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-15_04:,, signatures=0 From: Toomas Soome Message-id: MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: boot errors since upgrading to 12-current Date: Wed, 15 Aug 2018 18:18:16 +0300 In-reply-to: Cc: Kyle Evans , FreeBSD Current To: tech-lists References: <22F5A9FD-3167-4029-8CFF-B4096E9E69BB@me.com> <24f2e3f5-67b3-a5ac-8394-a7b5ecd0ce39@zyxst.net> X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 15:18:38 -0000 > On 15 Aug 2018, at 16:52, tech-lists wrote: >=20 > On 15/08/2018 13:20, tech-lists wrote: >> On 15/08/2018 12:49, Kyle Evans wrote: >>> On Wed, Aug 15, 2018 at 6:22 AM, tech-lists = wrote: >>>> Hello Toomas, >>>>=20 >>>> On 15/08/2018 07:31, Toomas Soome wrote: >>>>>=20 >>>>> Well that does explain the problem, if you look on the sizes = reported=E2=80=A6 so >>>>> your BIOS is reporting wrong sizes, is unable to access whole 4TB = space and >>>>> the zfs reader is not getting the correct data from the disks >>>>=20 >>>>=20 >>>> Do you know why this was not happening on 11-stable but is = happening on >>>> 12-current? >>>>=20 >>>> The BIOS has not been modified since the machine was bought back in = 2014. >>>>=20 >>>=20 >>> Perhaps r335245, which fixed a logical error and completely changed >>> the calculations for this stuff and possibly sent you on = dramatically >>> different path. There's not too many commits to this area that = haven't >>> yet landed back in stable/11, fortunately. >>>=20 >>> Thanks, >>>=20 >>> Kyle Evans >>>=20 >> Thank you Toomas and Kyle for the clarifications. >=20 > addendum to this - installed new world and kernel r337835 and the zfs = warning at boot seems to have disappeared. Something else odd has = started happening though, will make a new email for it - usb keyboard no = longer functioning at the beastie menu, but functions when boot = completes. >=20 >=20 The size related problem is entirely about luck - to read the pool, we = get pool config from label, and then read MOS (meta object set), and if = we can not read MOS, we are busted. if we can read MOS, the zfs probe in = boot loader is happy (actual file reads is still different story). = However, whenever the pool is changed, the MOS will get updates and its = location can (and will) change. rgds, toomas From owner-freebsd-current@freebsd.org Wed Aug 15 16:45:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1615F106734E for ; Wed, 15 Aug 2018 16:45:06 +0000 (UTC) (envelope-from wlosh@bsdimp.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 A193895F2A for ; Wed, 15 Aug 2018 16:45:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mailman.ysv.freebsd.org (Postfix) id 6678B106734D; Wed, 15 Aug 2018 16:45:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44B2D106734C for ; Wed, 15 Aug 2018 16:45:05 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC9D095F27 for ; Wed, 15 Aug 2018 16:45:04 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x22b.google.com with SMTP id e14-v6so2543413itf.1 for ; Wed, 15 Aug 2018 09:45:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=Qnp+zKlgLJNIbNQ6Q4wxp9tOFebUNlUIPZFwUOtGXm0=; b=pE6Qo1u8ndz0x0+jpQlfyop2lymd/wWBg7VW70UsT5bdFz6kFyZVBZM2JrDG0hCsID 5/44lPt2t0rAul4mi3Hh5t9IeC0+dUucaG9t/WTB8jUzdPK4F3rg+qFAsVuRKIInyDjK tP0ENB+Stt3IXTUpYaf+NZrmyN4/Dr/70HbhmLXaqxkIzLHbYSQ3M+4bASeyLhS1ym8W 9r5tfpN0CKkj3M+pNchubncbQaTs/4s0WzfG2ZL7kV+pBRK74qmWTcxzXn0CjbM/HkxF csfA8aGxcL5foYI5Dsn/bYWpjDu9OmUUmxsWnj8+nW9cXDlhoEk+16Xm93eLaAYm+rc1 zl/g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=Qnp+zKlgLJNIbNQ6Q4wxp9tOFebUNlUIPZFwUOtGXm0=; b=PmXMe/dsTY5oS2+RtEiaxObqwPNIDlCB5LvCEiCk/86ifF9rAjdu2F/0I4GawiahFy zKMrM9DHW2Wj2cm2EIuJG3vj4TOKxfTVSN07tQEKFmWpi9qaCpPeTRsW3q/wixBJVmPI YyVXOuGBsSzK9EdksOO595ERkWTMt66u1K5LXUKChOZA3zbilNVwdWca1D8buyCjJ5A1 R9QeU4a+kB7EyexrSU6PnBcoKGi9Yov7l7YGDFVyZzL3U22IYRRR2M2AxRB2TuTs9YYW LupbQNNhZi3jUREv//BEuOyT3BkJf5BpuHI24P/qQyFMOV0YjWVYT7xKFKuKaIXmqcpR KV0Q== X-Gm-Message-State: AOUpUlFC9RvDwixWBZ5c6QlTXX0hp+hiqYEMNNSuQKDHa42lKkStcoEf QxECQBUJKNTcEZUYL1Mo9qa3lhkhEpgpT9MOIQMJDQ== X-Google-Smtp-Source: AA+uWPxyNWdX5kJBUMdNBVvHWYQk8Cp/WVcUP09MGCy+XqO7IqJf1v6PfVNgLueE4GjwIKW1YNwzfcxgBQB2rEZX78Q= X-Received: by 2002:a24:b211:: with SMTP id u17-v6mr18147526ite.1.1534351504085; Wed, 15 Aug 2018 09:45:04 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:257:0:0:0:0:0 with HTTP; Wed, 15 Aug 2018 09:45:03 -0700 (PDT) X-Originating-IP: [50.227.106.226] In-Reply-To: References: <20180815124000.GB1190@albert.catwhisker.org> From: Warner Losh Date: Wed, 15 Aug 2018 10:45:03 -0600 X-Google-Sender-Auth: N5WmopI4PCfEL7-CBjY-9K0GWFU Message-ID: Subject: Re: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" To: Kyle Evans Cc: David Wolfskill , current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 16:45:06 -0000 On Wed, Aug 15, 2018 at 7:00 AM, Kyle Evans wrote: > On Wed, Aug 15, 2018 at 7:53 AM, Kyle Evans wrote: > > On Wed, Aug 15, 2018 at 7:40 AM, David Wolfskill > wrote: > >> I'm tracking head/amd64 daily twice on each of two machines: my "build > >> machine" ("freebeast") and my laptop, each first using the traditional > >> Forth loader, then (on a different slice), the Lua loader. > >> > >> Each is using BIOS and MBR (not UEFI; not GPT). > >> > >> Yesterday's update was to r337738, and was uneventful for each of > >> the four environments. > >> > >> Today's was to r337834, and was uneventful for the build machine (both > >> Forth and Lua loaders -- though there remains no means of interacting > >> with the loader on the build machine if it's booted using the Lua > >> loader). > >> > >> The laptop had no issues using the Forth loader, but the boot process > >> was ... severely abbreviated ... using the Lua loader. > >> > >> I don't have a serial consoloe on the laptop, so I snapped a photo; it > >> may be found at > >> . > >> > >> As the name suggests, the final message was: > >> > >> BTX halted > >> > >> at which point, I found no way to get the laptop to respond to anything > >> but a power cycle. > > > > Interesting. It seems to have died in the middle of loading a > > module... any insight into what that module may have been? > > > > Any way to hack beastie_disable="YES" into loader.conf(5) and see if > > that changes things? > > > > To be clear- the test I'm interested in will not be productive unless > beastie_disable="YES" is present in loader.conf or the environment > before lualoader engages at all. You may need to build a smaller loader_lua. If so please see https://reviews.freebsd.org/D16724 and apply and rebuild. The good news is that you only need to rebuild src/stand, which is fast. Warner From owner-freebsd-current@freebsd.org Wed Aug 15 16:48:10 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F21AF10674D6 for ; Wed, 15 Aug 2018 16:48:09 +0000 (UTC) (envelope-from david@catwhisker.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 91E129609C for ; Wed, 15 Aug 2018 16:48:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 5674010674D3; Wed, 15 Aug 2018 16:48:09 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4532C10674D2 for ; Wed, 15 Aug 2018 16:48:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 6B79196099; Wed, 15 Aug 2018 16:48:08 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7FGm4kO060052; Wed, 15 Aug 2018 16:48:04 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7FGm4i8060051; Wed, 15 Aug 2018 09:48:04 -0700 (PDT) (envelope-from david) Date: Wed, 15 Aug 2018 09:48:04 -0700 From: David Wolfskill To: Warner Losh Cc: Kyle Evans , current Subject: Re: r337738 -> r337834: Forth loader OK; Lua loader says "BTX halted" Message-ID: <20180815164804.GS1190@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Warner Losh , Kyle Evans , current References: <20180815124000.GB1190@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="NKhuVLqspgl309C2" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 16:48:10 -0000 --NKhuVLqspgl309C2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 15, 2018 at 10:45:03AM -0600, Warner Losh wrote: > ... > You may need to build a smaller loader_lua. If so please see > https://reviews.freebsd.org/D16724 and apply and rebuild. The good news is > that you only need to rebuild src/stand, which is fast. >=20 > Warner Aye; testing that now on the build machine (which had been idel). Laptop is kinda "in use" at the moment, so that will probably be delayed a bit. :-) Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --NKhuVLqspgl309C2 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt0WURfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hdWZwf+Phc7bcDdKPMABtYufXfIV/hmM0RhmfnvcZiRmdLK7FipTx7Gr6LXmSST fV3XzsjGzafA6K3WxZoxEqKMvYAdCYnSFA1hbSOvNblfEOzEUjx8qwj++APU7fL7 U77ltO0B/pPrV/lteqtw93j+JWAiXxcoDuYIvg14v286jHNiruIUm9YgBMtzlITq Y1BWYvF7Obyq0TnsrE3m7+zkY24yrAMCMIiIDgISLFLc2Rfx9SqkSe2oltSTugtD n/a04aTxHD3wbYgArQ4eOhBkXvHwhdfMiLRChw7dyTkNVMnbOUhCri6Es32FV68S q1DCDVvxCd1BfRNFDfcMSVsy5Kq/MQ== =WUDq -----END PGP SIGNATURE----- --NKhuVLqspgl309C2-- From owner-freebsd-current@freebsd.org Wed Aug 15 16:52:27 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9D68410677AF for ; Wed, 15 Aug 2018 16:52:27 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:146]) (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 2EB3C96490; Wed, 15 Aug 2018 16:52:27 +0000 (UTC) (envelope-from micchie@sfc.wide.ad.jp) Received: from n-1059.office.hd (mito.neclab.eu [195.37.70.39]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 4749E2799BD; Thu, 16 Aug 2018 01:52:22 +0900 (JST) Subject: Re: TCP server app performance To: Navdeep Parhar , freebsd-current@freebsd.org References: From: Michio Honda Message-ID: <9e67c516-799c-8a1e-0cc5-64ab1e582a98@sfc.wide.ad.jp> Date: Wed, 15 Aug 2018 18:52:17 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 16:52:27 -0000 On 08/14/2018 09:30 PM, Navdeep Parhar wrote: > On 8/12/18 9:50 AM, Honda Michio wrote: >> Hi, >> >> I'm measuring TCP server app performance using my toy web server. >> It just accept TCP connections and responds back HTTP OK to the clients. >> It monitors sockets using kqueue, and processes each ready descriptor using >> a pair of read() and write(). (in more detail, it's >> https://github.com/micchie/netmap/tree/paste/apps/phttpd) >> >> Using 100 persistent TCP connections (the client sends 44 B HTTP GET and >> the server responds with 151 B of HTTP OK) and a single CPU core, I only >> get 152K requests per second, which is 2.5x slower than Linux that runs the >> same app (except that it uses epoll instead of kqueue). >> I cannot justify this by myself. Does anybody has some intuition about how >> much FreeBSD would get with such workloads? >> I tried disabling TCP delayed ack and changing interrupt rates, but no >> significant difference was observed. >> >> I use FreeBSD-CURRENT with GENERIC-NODEBUG (git commit hash: 3015145c3aa4b). >> For hardware, the server has Xeon Silver 4110 and Intel X540 NIC (activate >> only a single queue as I test with a single CPU core). All the offloadings >> are disabled. > > I hope hw L3/L4 checksumming is still on? They are off but exchanged messages are too small to benefit from these offloads anyways. > > Are your results similar to what you get with 100 (same number as your > test clients) netperf's doing TCP_RR on this setup, or wildly different? I cannot find any netperf option that sends multiple connections with TCP_RR. I also don't find any equivalent in iperf. But single-connection performance is similar to what I get with wrk and my HTTP server. Running 100 netperf processes does not show aggregate throughput, and that also means running 100 kevent() loops, which is quite different behaviour from what I want. Cheers, - Michio > > Regards, > Navdeep > From owner-freebsd-current@freebsd.org Wed Aug 15 20:47:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1985D1070056 for ; Wed, 15 Aug 2018 20:47:33 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [IPv6:2a01:4f8:150:80b1:fe57:f772:524c:99d0]) (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 ADDE87AB58 for ; Wed, 15 Aug 2018 20:47:32 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:107f:1620:b3d:c003:d132:e3aa]) by madarka.gustik.eu (Postfix) with ESMTPSA id A8E2E140C7 for ; Wed, 15 Aug 2018 22:47:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1534366035; bh=iygXExs0Rlft0hdhjfD17/mOv0ehEnJEwVRf5Y4GzXc=; h=Date:From:To:Subject; b=v/H2/r3zUqpGMM1FUApigE2tw9OApYqcN70Br3ODGRVHAk0POnRV19mYXMcxkyIKO n7iJxLBIyjnId7g6jFdaxlxaGmc23KSNJhmsewiM8WzLz/xmAaaxCUzsE3JYWIC8Ze y1ZXfMIbkNRzH38gImlpiKBNs1GOTgZmdERFIM7w= Date: Wed, 15 Aug 2018 22:47:22 +0200 From: Lars Schotte To: FreeBSD current Subject: gif does not work when going over IPv6 on current Message-ID: <20180815224722.48071501@romy.j20.helspy.pw> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 20:47:33 -0000 Hey folks, when you create a gif with IPv6 tunnel endpoints tcpdump on the underlying interface will show you some kind of error that 0 != 6 and packets will be dropped. IP6 version error: 0 != 6 repeating for each packet. happens only while sending. receiving works. This happens only on 12-current as I am aware, 11-stable works good. I worked around this issue by setting IPv4 tunnel endpoints. And this issue is not related to what you transport. You can do IPv4 or IPv6 ( proto 4 or proto 41 ) the issue remains the same. With IPv4 tunnel endpoints ( inet tunnel ) it does dualstack w/o any issues. Strange. Isn't it? -- Lars Schotte Mudroňova 13 92101 PieÅ¡Å¥any From owner-freebsd-current@freebsd.org Wed Aug 15 21:09:55 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44AD11070C9E for ; Wed, 15 Aug 2018 21:09:55 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) 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 DEFB37BE82 for ; Wed, 15 Aug 2018 21:09:54 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: by mailman.ysv.freebsd.org (Postfix) id A34841070C9A; Wed, 15 Aug 2018 21:09:54 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 91D9E1070C98 for ; Wed, 15 Aug 2018 21:09:54 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) Received: from mailin.dlr.de (mailin.dlr.de [194.94.201.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailin.dlr.de", Issuer "DFN-Verein Global Issuing CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DDABE7BE7F for ; Wed, 15 Aug 2018 21:09:53 +0000 (UTC) (envelope-from Hartmut.Brandt@dlr.de) X-IronPort-AV: E=Sophos;i="5.53,244,1531778400"; d="scan'208";a="6792688" From: To: Subject: make problem Thread-Topic: make problem Thread-Index: AdQ029EIaHpOe4QLS92QP4lSxnUegg== Date: Wed, 15 Aug 2018 21:08:42 +0000 Deferred-Delivery: Wed, 15 Aug 2018 21:08:00 +0000 Message-ID: <611243783F62AF48AFB07BC25FA4B1062A0A4A75@DLDEFFMIMP01EXC.intra.dlr.de> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Aug 2018 21:09:55 -0000 Hi, what is wrong with the following Makefile? FILES=3D a.in b.in a b FILESDIR=3D /tmp/foo .include .SUFFIXES: .in .in: cp $(.IMPSRC) $(.TARGET) Given that a.in and b.in exist and 'make' has been executed, 'make install'= gives the following error: # sudo make install installing DIRS FILESDIR install -d -m 0755 -o root -g wheel /tmp/foo install -o root -g wheel -m 444 a.in /tmp/foo/a.in install -o root -g wheel -m 444 b.in /tmp/foo/b.in install -o root -g wheel -m 444 a /tmp/foo/a cp _FILESINS1_a.in _FILESINS1_a cp: _FILESINS1_a.in: No such file or directory *** Error code 1 Stop. From owner-freebsd-current@freebsd.org Thu Aug 16 09:19:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F1F4510836C1 for ; Thu, 16 Aug 2018 09:19:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward102j.mail.yandex.net (forward102j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F371763BF for ; Thu, 16 Aug 2018 09:19:32 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from mxback10g.mail.yandex.net (mxback10g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:171]) by forward102j.mail.yandex.net (Yandex) with ESMTP id A3EC15602417; Thu, 16 Aug 2018 12:19:21 +0300 (MSK) Received: from smtp4o.mail.yandex.net (smtp4o.mail.yandex.net [2a02:6b8:0:1a2d::28]) by mxback10g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id PZkekoLDaH-JLK4nPaY; Thu, 16 Aug 2018 12:19:21 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1534411161; bh=+lOZFIIAf/VDc7qmzEUnPwpyLCWC1cwH4gH+67a6s3Q=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=bmzClX7w+u6CIqIQqSoVKL2B1IXtME+u3tQQNlvbTHzQZzPSwONi0X6fEXIza6oI0 tBNGVhik27uPpdMJqyJgJ/K7mhwJon+QJiod0lvlS2A2M/pmehVfONuWq3w6rEZAeJ 5JCzEr7IqsF800D+MtgLv1Xbt9UcbWX4ix90Dxbw= Received: by smtp4o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 1s9u18EJo4-JKF8Vldr; Thu, 16 Aug 2018 12:19:20 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1534411160; bh=+lOZFIIAf/VDc7qmzEUnPwpyLCWC1cwH4gH+67a6s3Q=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=HSu4+eZiIzogKPYEhG11h/uWSMck+AnIPZ8+ob6k9C23ieT/rve/x8uInW5gvbgH6 i+whDPHhWOsUNsoJxL3rN9pi3HtCAFkFHe/g9WJqVRR+SCH3Cgesvmaf4YaeQrAMKr Zy2afssIXgKiYqZ2vrWe/rdpkAK6/aOn9GoCNbcc= Authentication-Results: smtp4o.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: gif does not work when going over IPv6 on current To: Lars Schotte , FreeBSD current References: <20180815224722.48071501@romy.j20.helspy.pw> From: "Andrey V. Elsukov" Openpgp: id=E6591E1B41DA1516F0C9BC0001C5EA0410C8A17A Autocrypt: addr=bu7cher@yandex.ru; prefer-encrypt=mutual; keydata= xsBNBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYbxNk7qUC5 21YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ijZEjWHV91hY1YTHEF ZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7QEiWpyLVwECgLX2eOAXByT8B bCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDBVDGiOgvfxqidab7fdkh893IBCXa82H9N CNwnEtcgzh+BSKK5BgvPohFMgRwjti37TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEB AAHNIkFuZHJleSBWLiBFbHN1a292IDxhZUBmcmVlYnNkLm9yZz7CwHsEEwECACUCGwMGCwkI BwMCBhUIAgkKCwQWAgMBAh4BAheABQJMB/ruAhkBAAoJEAHF6gQQyKF6MLwH/3Ri/TZl9uo0 SepYWXOnxL6EaDVXDA+dLb1eLKC4PRBBjX29ttQ0KaWapiE6y5/AfzOPmRtHLrHYHjd/aiHX GMLHcYRXD+5GvdkK8iMALrZ28X0JXyuuZa8rAxWIWmCbYHNSBy2unqWgTI04Erodk90IALgM 9JeHN9sFqTM6zalrMnTzlcmel4kcjT3lyYw3vOKgoYLtsLhKZSbJoVVVlvRlGBpHFJI5AoYJ SyfXoN0rcX6k9X7Isp2K50YjqxV4v78xluh1puhwZyC0p8IShPrmrp9Oy9JkMX90o6UAXdGU KfdExJuGJfUZOFBTtNIMNIAKfMTjhpRhxONIr0emxxDOwE0ETAEXWQEIAJ2p6l9LBoqdH/0J PEFDY2t2gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+ LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cvoYxj3dz4 S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQravXpZkl5JG4eOqJVIU X316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhYkPKVn7z1sZiB7W2H2TojbmcK HZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUAEQEAAcLAXwQYAQIACQUCTAEXWQIbDAAK CRABxeoEEMihegkYCAC3ivGYNe2taNm/4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw 98OmX7G0OV9snxMW+6cyNqBrVFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQ WfyJJIM7l3gv5ZS3DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLoz BcFCNdDAyXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85JJrV1mi5i Message-ID: <9fd75304-5660-df19-243e-034c724a75bf@yandex.ru> Date: Thu, 16 Aug 2018 12:18:44 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180815224722.48071501@romy.j20.helspy.pw> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jphyri4N4t3XZXPtqAez9tLH9u6FOjflT" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 09:19:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jphyri4N4t3XZXPtqAez9tLH9u6FOjflT Content-Type: multipart/mixed; boundary="qDl1Dr80GmsZLji7WRlVPuNeFK5yt4rBX"; protected-headers="v1" From: "Andrey V. Elsukov" To: Lars Schotte , FreeBSD current Message-ID: <9fd75304-5660-df19-243e-034c724a75bf@yandex.ru> Subject: Re: gif does not work when going over IPv6 on current References: <20180815224722.48071501@romy.j20.helspy.pw> In-Reply-To: <20180815224722.48071501@romy.j20.helspy.pw> --qDl1Dr80GmsZLji7WRlVPuNeFK5yt4rBX Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 15.08.2018 23:47, Lars Schotte wrote: > Hey folks, >=20 > when you create a gif with IPv6 tunnel endpoints > tcpdump on the underlying interface will show you some kind of error > that 0 !=3D 6 and packets will be dropped. >=20 > IP6 version error: 0 !=3D 6 > repeating for each packet. > happens only while sending. receiving works. >=20 > This happens only on 12-current as I am aware, 11-stable works good. > I worked around this issue by setting IPv4 tunnel endpoints. Hi, should be fixed in r337900. Thanks for the report. And sorry for breakage. --=20 WBR, Andrey V. Elsukov --qDl1Dr80GmsZLji7WRlVPuNeFK5yt4rBX-- --jphyri4N4t3XZXPtqAez9tLH9u6FOjflT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQEzBAEBCAAdFiEE5lkeG0HaFRbwybwAAcXqBBDIoXoFAlt1QXQACgkQAcXqBBDI oXpkBwf8DYOxvBD+Jm9lRHswvmTGInFp9aL2vV/uAhGw4A5garuyQZMWH7vII0T2 IAD86/xRsrgp1qJTmcy3b7kW22pZIAuEd/q3Hf6vlw09AaRY/nkFrdoFpS4JOqQc Zzshbhf2yKJf0yepofruUcUXu9ENLhdhKN88XOBhqd1gWLrWvCkbuh7sCMxnuFqD HR0bu1Jsv89K97utn7xmAiNittKlSZX9BJC7Kd3sv0tKYcktqx39eRNTJPndkN3/ qlnVt98jw1PNDFNbKmN6EAsoV8Pb0GRXzAvApmCio/DA1J6A0e++kHN9f9anIRCH wPNvzUQqBfl+EbcipbSVKHT8m2N7sQ== =eN39 -----END PGP SIGNATURE----- --jphyri4N4t3XZXPtqAez9tLH9u6FOjflT-- From owner-freebsd-current@freebsd.org Thu Aug 16 09:59:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB7931084825 for ; Thu, 16 Aug 2018 09:59:12 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 940AD79697; Thu, 16 Aug 2018 09:59:12 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 86BB41B863; Thu, 16 Aug 2018 09:59:12 +0000 (UTC) Date: Thu, 16 Aug 2018 09:59:12 +0000 From: Alexey Dokuchaev To: Mark Johnston Cc: Kevin Lo , Lev Serebryakov , gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180816095912.GA80650@FreeBSD.org> References: <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> <20180605214808.GA94301@pesky> <20180615051025.GA79327@ns.kevlo.org> <20180615084022.GA32922@pesky.lan> <20180627104638.GA15311@FreeBSD.org> <20180627115526.GA52468@pesky> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180627115526.GA52468@pesky> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 09:59:13 -0000 On Wed, Jun 27, 2018 at 07:55:26AM -0400, Mark Johnston wrote: > On Wed, Jun 27, 2018 at 10:46:38AM +0000, Alexey Dokuchaev wrote: > > On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote: > > > ... > > > The change was committed as r334752. Are you seeing unexpected OOM > > > kills on or after that revision? > > > > I've just discovered this thread. I've updated my -CURRENT desktop ca. > > June 4th and my X.org session crashes within several minutes. This is > > on i386 system with 4G RAM. > > > > I cannot get SVN revision of that kernel because something got broken > > and it was not embedded in the image. :-( > > > > Rebooting with kernel="kernel.old" from May 12th made this problem go > > away. Is the root cause is known at this time? Which revision shall > > I try to see whether it does not exhibit this bug any longer? Thanks, > > As noted earlier in the thread, r329882 introduced a problem where > out-of-memory kills were taking place despite an abundance of free pages > and swap space. That bug was fixed in r334752. If you are seeing a > problem that is fixed in a kernel from May 12th, then it is possibly > unrelated to this bug, but it is worth testing r334752 or later to > confirm. Thanks, I can confirm that r334752 fixed the out-of-memory kills for me now that I've been running it for two weeks without a single problem. ./danfe From owner-freebsd-current@freebsd.org Thu Aug 16 10:11:34 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDE081085022 for ; Thu, 16 Aug 2018 10:11:33 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 69AA77A712 for ; Thu, 16 Aug 2018 10:11:33 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr1-x433.google.com with SMTP id r16-v6so3615372wrt.11 for ; Thu, 16 Aug 2018 03:11:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5NUewAzncNKNWuSaXjeKL97XztFpOd9QTDENMPB2ff8=; b=orOn+R3c4kP7MxPchFxva6L+1uw3a4DrgYDP2BbI992K90Tknmpruc5FX11X/V7qXW OomARWGjoIpHna+UuDP3PFT3frAfzLzR1ssemGr1XAs2FmFCngQrzf44txOVxcz2g1Yx 2MnlQFvHFN9liCK4jyhC+E3l43eM+iODqKV/mrCLxvNPBacQY6+3VMis+058PMQpzonT Ym0VKlUv/zotDtjyem+nC9nRGJrGw1HHOjus3VXj5fydQSoIjGd12dodbz1mIf6VZGoT BswfhkKMQYgnGVThC1giVs0+B+J7QW2Th7LFc1ZY2P2GIp+Vdp3KvdjpgQCl+a1LrlRN b10Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5NUewAzncNKNWuSaXjeKL97XztFpOd9QTDENMPB2ff8=; b=D7ZslL79HBYQ9Ah4Cq0nhDV/0yRfzsxeSEF3BswezKIAvJjETjEiOQWkHRGbLmITen P9L2Zj4LLgOBRNe9bb9O4bbtSAScavZN8eZVOEWKRnwNnLSUhdss5Sc8xfxgsevZNpk1 CoLeRyqOEL9s1TfcU+ZQOMjO3baAqrd4nBXyhfotoMVX8rJ4tJZR2DyToHyl+hFIkXXQ 73td6+xfL6MWhsokUAgoAC6JugIydzuThL4lk4ljm+MOnVVQUjrsKDImqHSot7y1ylBo tszQiyFpZtzh4MhLirYgD4FMR1IelI2iFl8S9r708v+pnL4Gh1yBVYmBZNY381Z16kXu yYHA== X-Gm-Message-State: AOUpUlHnOVGDpAdIvTLkS8crvtwQ3GRs2Qzkd7FbzDPsBoMQy5/UJpfw 1hqG4XURX3vNeQWkdbuKM75+5iqilu2bAXMARgM= X-Google-Smtp-Source: AA+uWPysbLCUnEiDBrRlfyVHpojYt0MuyVohTAhlvEDLl4CeFaUjBCrcBubBOu4XZE1+HM75tNOQ0pUQu2urtZL4mr8= X-Received: by 2002:adf:f390:: with SMTP id m16-v6mr19006463wro.279.1534414292454; Thu, 16 Aug 2018 03:11:32 -0700 (PDT) MIME-Version: 1.0 References: <3b53edb8-e1d2-109f-6ec7-81513c513433@vangyzen.net> <20180814143718.GL2340@kib.kiev.ua> In-Reply-To: From: Johannes Lundberg Date: Thu, 16 Aug 2018 11:10:55 +0100 Message-ID: Subject: Re: Make drm drivers use MTRR write-combine To: Konstantin Belousov Cc: eric@vangyzen.net, freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 10:11:34 -0000 On Tue, Aug 14, 2018 at 9:54 PM Johannes Lundberg wrote: > > > On Tue, Aug 14, 2018 at 3:39 PM Konstantin Belousov > wrote: > >> On Tue, Aug 14, 2018 at 08:55:36AM -0500, Eric van Gyzen wrote: >> > On 8/14/18 4:12 AM, Johannes Lundberg wrote: >> > > Hi >> > > >> > > Something that we have seen for a long time on FreeBSD is the boot >> message >> > > >> > > Failed to add WC MTRR for [0xd0000000-0xdfffffff]: -22; performance >> may >> > > suffer >> > > >> > > Taking a closer look at this with memcontrol I can see that the 256 MB >> > > region that DRM wants to set as WC is already covered by this entry >> > > 0xc0000000/0x40000000 BIOS uncacheable set-by-firmware active >> > > >> > > Similar on both my Skylake and Broadwell systems. >> > I see something similar on my Dell XPS 13 with a Kaby Lake R: >> > >> > Failed to add WC MTRR for [0x90000000-0x9fffffff]: -22; performance may >> > suffer >> > >> > 0x80000000/0x80000000 BIOS uncacheable set-by-firmware active >> > >> > The only mappings in this range are MMIO: >> > >> > machdep.efi_map: >> > Type Physical Virtual #Pages Attr >> > [snip] >> > MemoryMappedIO 0000e0000000 0xe0000000 00010000 RUNTIME >> > MemoryMappedIO 0000fe000000 0xfe000000 00000011 UC RUNTIME >> > MemoryMappedIO 0000fec00000 0xfec00000 00000001 UC RUNTIME >> > MemoryMappedIO 0000fee00000 0xfee00000 00000001 UC WT WB WP RUNTIME >> > MemoryMappedIO 0000ff000000 0xff000000 00001000 UC WT WB WP RUNTIME >> >> Yes, the cause of the message is that current x86 mtrr code is not >> sufficient to handle this situation. You have BIOS-configured variable >> range MTRR which covers upper half of the low 4G, as uncacheable (UC). >> It is reasonable for BIOS to set it up this way because this is where >> PCIe BARs and other devices MMIO regions are located. >> >> One of the BARs there is the GPU aperture that really should be WC >> (write-combining). There are two ways to achieve this: split the UC >> variable-length MTRR range into three, UC/WC/UC, which would require >> three MTRRs to cover. This is what current x86_mem.c code does not >> support. >> >> Another way is to set WC mode in the page table entries (PTEs) using >> Page Attribute Table (PAT), for all PTEs. According to the rules of >> combination of the memory access types between MTRR and PAT, WC in PAT >> and any access mode in MTRR gives effective WC. >> >> I saw the same warning when I initially ported GEM. My code used WC PAT >> type, which makes the warning cosmetical, and which made me to not add >> MTRR split. If new drm driver also consistently uses WC memattr when >> creating aperture mappings, then the warning can be ignored as well. >> > > Hi Kib > > Thanks for the detailed answer. This might already be the case for the out > of tree drivers as well. From what I read about the VESA driver the > performance difference should be quite big w/o WC and I haven't noticed and > performance issues with the newer drivers at all. > > I will confirm this tomorrow. > Yeah, seems like it's already done. https://github.com/FreeBSDDesktop/kms-drm/blob/drm-v4.15/linuxkpi/gplv2/src/linux_page.c#L260 https://github.com/FreeBSDDesktop/kms-drm/blob/drm-v4.15/drivers/gpu/drm/i915/i915_gem_gtt.c#L415 https://github.com/FreeBSDDesktop/kms-drm/blob/drm-v4.15/drivers/gpu/drm/ttm/ttm_page_alloc.c#L534 > > _______________________________________________ >> freebsd-current@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org >> " >> > From owner-freebsd-current@freebsd.org Thu Aug 16 11:11:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F20A610861D9 for ; Thu, 16 Aug 2018 11:11:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from st13p35im-asmtp001.me.com (st13p35im-asmtp001.me.com [17.164.199.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 879687C38D for ; Thu, 16 Aug 2018 11:11:38 +0000 (UTC) (envelope-from tsoome@me.com) Received: from process-dkim-sign-daemon.st13p35im-asmtp001.me.com by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PDJ00M00W702K00@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Thu, 16 Aug 2018 11:11:37 +0000 (GMT) Received: from icloud.com ([127.0.0.1]) by st13p35im-asmtp001.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PDJ00NIUWFAM810@st13p35im-asmtp001.me.com> for freebsd-current@freebsd.org; Thu, 16 Aug 2018 11:11:36 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1808160119 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-08-16_03:,, signatures=0 From: Toomas Soome MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: 4kn and biosdisk.c Message-id: <8F96FE65-4F53-4BD6-8EC1-C4B43CEA5980@me.com> Date: Thu, 16 Aug 2018 14:11:33 +0300 To: FreeBSD Current X-Mailer: Apple Mail (2.3445.9.1) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 11:11:39 -0000 hi! if you have 4kn disks and BIOS capable of 4k IO with INT13, could you = please test https://reviews.freebsd.org/D11174 = and give some feedback:) The patch itself has been in use for some time in illumos. PS: as noted = in test plan, this only can be tested by loader now and not by earlier = stages (lsdev, lszfs, ls device:path commands). thanks, toomas= From owner-freebsd-current@freebsd.org Thu Aug 16 11:15:36 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A0511086613 for ; Thu, 16 Aug 2018 11:15:36 +0000 (UTC) (envelope-from david@catwhisker.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 219C87C6C9 for ; Thu, 16 Aug 2018 11:15:36 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id D74401086612; Thu, 16 Aug 2018 11:15:35 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B279E1086611 for ; Thu, 16 Aug 2018 11:15:35 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 1DF6A7C6C8 for ; Thu, 16 Aug 2018 11:15:34 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7GBFWPV071430 for ; Thu, 16 Aug 2018 11:15:32 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7GBFWWn071429 for current@freebsd.org; Thu, 16 Aug 2018 04:15:32 -0700 (PDT) (envelope-from david) Date: Thu, 16 Aug 2018 04:15:32 -0700 From: David Wolfskill To: current@freebsd.org Subject: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] Message-ID: <20180816111532.GY1190@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QwVuF0T/sxuZ/Zeu" Content-Disposition: inline User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 11:15:36 -0000 --QwVuF0T/sxuZ/Zeu Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Running: FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r337834M= /337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root@g1-215.catwhisker.or= g:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 after updating working copy to r337903, I'm seeing: =2E.. >>> stage 4.3: building everything =2E.. --- ifconfig_make --- Building /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/ifco= nfig/af_inet6.o --- all_subdir_secure --- --- moduli --- /usr/bin/ld: error: undefined symbol: main >>> referenced by crt1.c >>> /common/S4/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_s= tart) /usr/bin/ld: error: undefined symbol: Fssh_error =2E... make[5]: stopped in /usr/src/secure/usr.sbin/sshd =2EERROR_TARGET=3D'moduli' =2EERROR_META_FILE=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/ss= hd/moduli.meta' =2EMAKE.LEVEL=3D'5' MAKEFILE=3D'' =2EMAKE.MODE=3D'meta missing-filemon=3Dyes missing-meta=3Dyes silent=3Dyes = verbose' _ERROR_CMD=3D'cc -target x86_64-unknown-freebsd12.0 --sysroot=3D/common/S4/= obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/bi= n -O2 -pipe -I/usr/src/crypto/openssh -include ssh_namespace.h -DHAVE_LDN= S=3D1 -DUSE_BSM_AUDIT=3D1 -DHAVE_GETAUDIT_ADDR=3D1 -DUSE_BLACKLIST=3D1 -I/u= sr/src/contrib/blacklist/include -include krb5_config.h -DLIBWRAP=3D1 -std= =3Dgnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-st= ring-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unu= sed-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversi= on -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno= -switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argumen= ts -L/common/S4/obj/usr/src/amd64.amd64/lib/libblacklist /usr/src/crypto= /openssh/moduli.c -o moduli; ;' =2ECURDIR=3D'/usr/src/secure/usr.sbin/sshd' =2EMAKE=3D'make' =2EOBJDIR=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/sshd' =2ETARGETS=3D'all' DESTDIR=3D'/common/S4/obj/usr/src/amd64.amd64/tmp' =2E... (on both the laptop and the build machine). I have copied the .ERROR_META_FILE to . Additional information (previous day's verbose dmesg.bot, etc.) may be found at . Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --QwVuF0T/sxuZ/Zeu Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt1XNRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hf8yggAnyT603Bd/n/7YygTj+yt3REbAfQ1v8bdVjYdaMteS187WzmDipyQmdev KSdeR9n0+OT+i3gY2i4QtYy5OuTW75Wjf8pRyo3Hn3PQ3ZjBs4Z5Ltnj5da4ALAl ZaGSNnym4fVvoO49aj9gyWEF1V4AwEH30KfzSibH6QVL1aN1L0F4rAcs+5zZ0VQE TvWINLVeEAHuTU/hHgVOnMRWT55XeseLtp3CP7Mm/KlvWBERXK5e7RHoGesQANki x5QbIO7TLZzfpS1OoG76ZjcaqpnJ9RCG4iwy+gg6l19+9ee0E+t7gtkrJQkZwv4z G9tQm1AO0mp2a7LlyhMlbex+vMMElQ== =sy14 -----END PGP SIGNATURE----- --QwVuF0T/sxuZ/Zeu-- From owner-freebsd-current@freebsd.org Thu Aug 16 12:58:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A577410587B4 for ; Thu, 16 Aug 2018 12:58:29 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id 1FAEF8066A for ; Thu, 16 Aug 2018 12:58:28 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 99610 invoked by uid 89); 16 Aug 2018 12:58:21 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.231.99) by mail.grem.de with ESMTPA; 16 Aug 2018 12:58:21 -0000 Mime-Version: 1.0 (1.0) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) From: Michael Gmelin X-Mailer: iPhone Mail (15G77) In-Reply-To: <20180815135531.GA2340@kib.kiev.ua> Date: Thu, 16 Aug 2018 14:58:20 +0200 Cc: "freebsd-current@freebsd.org" , Matthias Apitz , jhb@freebsd.org Message-Id: References: <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> To: Konstantin Belousov Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 12:58:29 -0000 > On 15. Aug 2018, at 15:55, Konstantin Belousov wrote= : >=20 >> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>=20 >>=20 >>>> On 15. Aug 2018, at 15:04, Konstantin Belousov wr= ote: >>>>=20 >>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >>>> Reviving this old thread, since I just updated to r337818 and a similar= >>>> problem is happening again. Since the fix in r334799 (review >>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, >>>> so maybe this is related >>>> (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799). >>>>=20 >>>> Please see the screenshot of the panic below: >>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>>>=20 >>>> This is me not digging any deeper, hoping that this is something >>>> obvious. Please let me know if you need more input. >>>=20 >>> I do not see how recent mp_machdep.c changes could affect this. >>> Can you try newest kernel but old loader ? >>=20 >> I will try (but that will take a while). Oh, also, it still boots in save= mode/with smp disabled. >=20 > Right, this is because the access to that address through DMAP is only=20 > needed when configuring AP startup resources. >=20 > Also, I think it is safe to suggest that the bisect is needed. Using an older loader didn=E2=80=99t help, but I identified the problem: https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334952 modified the code you introduced in https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799 By correcting units to pages it also broke booting the Chromebook as a side e= ffect - so the previous fix just worked due to a bug it seems. Is there an easy way to output the content of physmap at that point (debug.l= ate_console=3D0 doesn=E2=80=99t work) - like an existing buffer I could use,= or would this be more elaborate (I did something complicated last time but d= idn=E2=80=99t save it, so any simple solution would be preferred). Thanks, Michael=20 From owner-freebsd-current@freebsd.org Thu Aug 16 16:14:04 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A2F7106C742 for ; Thu, 16 Aug 2018 16:14:04 +0000 (UTC) (envelope-from delphij@gmail.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 055FD8ACD4 for ; Thu, 16 Aug 2018 16:14:04 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id BE4FB106C741; Thu, 16 Aug 2018 16:14:03 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C6D6106C73E for ; Thu, 16 Aug 2018 16:14:03 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-it0-x235.google.com (mail-it0-x235.google.com [IPv6:2607:f8b0:4001:c0b::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 342A58ACD2; Thu, 16 Aug 2018 16:14:03 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-it0-x235.google.com with SMTP id e14-v6so7027629itf.1; Thu, 16 Aug 2018 09:14:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=NrHj8tlIRKuI2Yn0dROZkl05sdTVAiz7DNMTtBFJso4=; b=qtP2On/G5pgcD+hB64cKELHUpjDDPPRXyak61MKGqU0KYxW9hQkmjGXgDjcndaXZgK Cb+PYTdTGmcTXs9SERq2w32YlETeSORTA2cLSazaTxzcJCDmExHx4NMbjgB17lWxM625 9A4X/Vjz/3C/WkWknqP6oKSQmrxZe588Lgm/Aws30knjDk5x85i/m3TR3GkmTaTpdSQi EOii7AY57qTVM3xj/UxRtwj7KswlkDUDMfB3suOt0j6aiUsMzX5LvsMvngRN5EheN/jH 2Iw5H5a+PvFl4cYQTAvYienBPoUcgCkmtsDbNLLiKlF4zzUF2+7vqkCYkjmrK2Lq+Dwm KY5A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:content-transfer-encoding; bh=NrHj8tlIRKuI2Yn0dROZkl05sdTVAiz7DNMTtBFJso4=; b=spz74qOeWKVDnL04tYA2albxuX4bN/OGi2cyrr3Ze/3LQOaDZJiy4RvPxwR5VEvxt8 pHSSA6uR0uatkqiEOfH2kc45vXk/uYo37SD+COIYq2X2ZcSKXavHURYMwn9a1ohqqm+0 bEZPCvM9ssB2vz27FHiYN56+09nc5g2kZZg5I4bSamZhrL9XMC9cPAMj3+AV9YqzAem7 1PEMlijFP8jsxO34w3ubZrynM9/OsbZhnGUJCPnYiNRan7w7QlZ9KAmV3BvFqcdRIdIl gtxGNXz7q+IZlpSiHtCwia/PvOgLEcd6yPSsDUqn4ZBwtk1haKg5bPcenys5zLUFq+AW /dQg== X-Gm-Message-State: AOUpUlHLfANrms83vVHusWo2wepG6rmo+sim/5UkYWuIfZM9+6nNBTVs P+CN9tBWhuluaQX9oDfW6p60Z1xvWyKF0TyGPs90gINl X-Google-Smtp-Source: AA+uWPwmC3p+iql321T5Nj6L335Z3T9VI98x/YzaAj5twaf6N4hWU2hhoqX9GqBm0FCDhxHYwPFdKGkbe5c0A78/OC4= X-Received: by 2002:a02:8c75:: with SMTP id j50-v6mr27813529jal.76.1534436042052; Thu, 16 Aug 2018 09:14:02 -0700 (PDT) MIME-Version: 1.0 References: <20180816111532.GY1190@albert.catwhisker.org> In-Reply-To: <20180816111532.GY1190@albert.catwhisker.org> From: Xin LI Date: Thu, 16 Aug 2018 09:13:50 -0700 Message-ID: Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] To: current@freebsd.org, Brad Davis Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:14:04 -0000 This was caused by r337852, but I didn't investigated further. The problem is that we have a source file called 'moduli.c' in crypto/openssh/ while the build target was moduli, and bmake seen 'moduli' in source tree as older than moduli.c, and decided to rebuild it from source, while the two files are unrelated. Cheers, On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill wrot= e: > > Running: > > FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r33783= 4M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root@g1-215.catwhisker.= org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > after updating working copy to r337903, I'm seeing: > > ... > >>> stage 4.3: building everything > ... > --- ifconfig_make --- > Building /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/if= config/af_inet6.o > --- all_subdir_secure --- > --- moduli --- > /usr/bin/ld: error: undefined symbol: main > >>> referenced by crt1.c > >>> /common/S4/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(= _start) > /usr/bin/ld: error: undefined symbol: Fssh_error > .... > make[5]: stopped in /usr/src/secure/usr.sbin/sshd > .ERROR_TARGET=3D'moduli' > .ERROR_META_FILE=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/ss= hd/moduli.meta' > .MAKE.LEVEL=3D'5' > MAKEFILE=3D'' > .MAKE.MODE=3D'meta missing-filemon=3Dyes missing-meta=3Dyes silent=3Dyes = verbose' > _ERROR_CMD=3D'cc -target x86_64-unknown-freebsd12.0 --sysroot=3D/common/S= 4/obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/= bin -O2 -pipe -I/usr/src/crypto/openssh -include ssh_namespace.h -DHAVE_L= DNS=3D1 -DUSE_BSM_AUDIT=3D1 -DHAVE_GETAUDIT_ADDR=3D1 -DUSE_BLACKLIST=3D1 -I= /usr/src/contrib/blacklist/include -include krb5_config.h -DLIBWRAP=3D1 -st= d=3Dgnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-s= tring-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-un= used-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-convers= ion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wn= o-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-argume= nts -L/common/S4/obj/usr/src/amd64.amd64/lib/libblacklist /usr/src/crypt= o/openssh/moduli.c -o moduli; ;' > .CURDIR=3D'/usr/src/secure/usr.sbin/sshd' > .MAKE=3D'make' > .OBJDIR=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/sshd' > .TARGETS=3D'all' > DESTDIR=3D'/common/S4/obj/usr/src/amd64.amd64/tmp' > .... > > (on both the laptop and the build machine). > > I have copied the .ERROR_META_FILE to > a typescript of the attempted build to > . > > Additional information (previous day's verbose dmesg.bot, etc.) may > be found at . > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-4495930= 0 > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Thu Aug 16 16:26:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 34F77106CDC6 for ; Thu, 16 Aug 2018 16:26:12 +0000 (UTC) (envelope-from brd@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 C6C2F8B5E8 for ; Thu, 16 Aug 2018 16:26:11 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8B87D106CDC5; Thu, 16 Aug 2018 16:26:11 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 699E3106CDC4 for ; Thu, 16 Aug 2018 16:26:11 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C7248B5E7; Thu, 16 Aug 2018 16:26:11 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: brd/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id E836D1ED3B; Thu, 16 Aug 2018 16:26:10 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id EB37821FF5; Thu, 16 Aug 2018 12:26:09 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute5.internal (MEProxy); Thu, 16 Aug 2018 12:26:09 -0400 X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 4C6BCBA4CF; Thu, 16 Aug 2018 12:26:09 -0400 (EDT) Message-Id: <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> From: Brad Davis To: Xin LI , current@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-7b72137a In-Reply-To: Date: Thu, 16 Aug 2018 10:26:09 -0600 References: <20180816111532.GY1190@albert.catwhisker.org> Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:26:12 -0000 On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: > This was caused by r337852, but I didn't investigated further. > > The problem is that we have a source file called 'moduli.c' in > crypto/openssh/ while the build target was moduli, and bmake seen > 'moduli' in source tree as older than moduli.c, and decided to rebuild > it from source, while the two files are unrelated. Hi Xin, I don't see how that could be the case as I didn't move the file around, I just moved how it gets installed. I have done many many builds with this change in and haven't seen this problem.. Regards, Brad Davis > On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill wrote: > > > > Running: > > > > FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r337834M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > > > after updating working copy to r337903, I'm seeing: > > > > ... > > >>> stage 4.3: building everything > > ... > > --- ifconfig_make --- > > Building /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/ifconfig/af_inet6.o > > --- all_subdir_secure --- > > --- moduli --- > > /usr/bin/ld: error: undefined symbol: main > > >>> referenced by crt1.c > > >>> /common/S4/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1.o:(_start) > > /usr/bin/ld: error: undefined symbol: Fssh_error > > .... > > make[5]: stopped in /usr/src/secure/usr.sbin/sshd > > .ERROR_TARGET='moduli' > > .ERROR_META_FILE='/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/sshd/moduli.meta' > > .MAKE.LEVEL='5' > > MAKEFILE='' > > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' > > _ERROR_CMD='cc -target x86_64-unknown-freebsd12.0 --sysroot=/common/S4/obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -I/usr/src/crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -DUSE_BSM_AUDIT=1 -DHAVE_GETAUDIT_ADDR=1 -DUSE_BLACKLIST=1 -I/usr/src/contrib/blacklist/include -include krb5_config.h -DLIBWRAP=1 -std=gnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -L/common/S4/obj/usr/src/amd64.amd64/lib/libblacklist /usr/src/crypto/openssh/moduli.c -o moduli; ;' > > .CURDIR='/usr/src/secure/usr.sbin/sshd' > > .MAKE='make' > > .OBJDIR='/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/sshd' > > .TARGETS='all' > > DESTDIR='/common/S4/obj/usr/src/amd64.amd64/tmp' > > .... > > > > (on both the laptop and the build machine). > > > > I have copied the .ERROR_META_FILE to > > > a typescript of the attempted build to > > . > > > > Additional information (previous day's verbose dmesg.bot, etc.) may > > be found at . > > > > Peace, > > david > > -- > > David H. Wolfskill david@catwhisker.org > > Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 > > > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Thu Aug 16 16:30:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41C9D106D2BC for ; Thu, 16 Aug 2018 16:30:53 +0000 (UTC) (envelope-from jmg@gold.funkthat.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 03E0C8BB33 for ; Thu, 16 Aug 2018 16:30:53 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: by mailman.ysv.freebsd.org (Postfix) id BCDA5106D2B7; Thu, 16 Aug 2018 16:30:52 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABB11106D2B6 for ; Thu, 16 Aug 2018 16:30:52 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 243898BB17; Thu, 16 Aug 2018 16:30:48 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id w7GGUf06065998 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Aug 2018 09:30:41 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id w7GGUfrl065997; Thu, 16 Aug 2018 09:30:41 -0700 (PDT) (envelope-from jmg) Date: Thu, 16 Aug 2018 09:30:41 -0700 From: John-Mark Gurney To: current@FreeBSD.org Cc: bsdimp@FreeBSD.org Subject: buffer device_printf... Message-ID: <20180816163041.GW97145@funkthat.com> Mail-Followup-To: current@FreeBSD.org, bsdimp@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Thu, 16 Aug 2018 09:30:41 -0700 (PDT) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:30:53 -0000 On my arm64 board, various console messages get intermixed because of SMP. This makes messages harder to read than the could be. One issue is that device_printf uses two printf's, one for the device, and one for the provided message.. This prevents PRINTF_BUFR_SIZE from combining the two messages into a single write. The review https://reviews.freebsd.org/D16690 makes device_printf use an sbuf w/ a printf drain to effectively buffer these messages together. previously: Trying to mount root from ufs:/dev/ufs/rootfs [rw]... mmc0: Instruction Set Attributes 0 = ACMD42 failed, RESULT: 4 Instruction Set Attributes 1 = <> mmc0: Processor Features 0 = Card at relative address 43690 failed to set bus width w/ patch: mmc0: ACMD42 failed, RESULT: 4 Trying to mount root from ufs:/dev/ufs/rootfs [rw]... Instruction Set Attributes 0 = mmc0: Card at relative address 43690 failed to set bus width Instruction Set Attributes 1 = <> Processor Features 0 = Comments? -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@freebsd.org Thu Aug 16 16:44:48 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D6DBD106DD72 for ; Thu, 16 Aug 2018 16:44:47 +0000 (UTC) (envelope-from ml@vishwin.info) 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 5CD318CA26 for ; Thu, 16 Aug 2018 16:44:47 +0000 (UTC) (envelope-from ml@vishwin.info) Received: by mailman.ysv.freebsd.org (Postfix) id 21786106DD71; Thu, 16 Aug 2018 16:44:47 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB367106DD70 for ; Thu, 16 Aug 2018 16:44:46 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (varun.vishwin.info [46.101.93.59]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "varun.vishwin.info", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FEE28CA25 for ; Thu, 16 Aug 2018 16:44:46 +0000 (UTC) (envelope-from ml@vishwin.info) Received: from varun.vishwin.info (fd35:9eae:7575::2 [IPv6:fd35:9eae:7575::2]) by varun.vishwin.info (OpenSMTPD) with ESMTP id 934184a2 for ; Thu, 16 Aug 2018 12:43:53 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=vishwin.info; h=subject :references:to:from:message-id:date:mime-version:in-reply-to :content-type; s=fuccboi12; bh=pT9zTYns0MhbUS9YhYN/ETuKbAaPlrGH2 f5zilAi3TM=; b=G8PaqQWB7bgJMDuqO6Uq8H5pwtinWW/3lRVgN0uMz6uc99QLH iJ9Cgeh+gKOai0ImZ8uEkX4gDyqx/97lUXxx1tfAX8vW2w9QKos68DGE9PS0zQO1 RI7Xjuhs6/4VUCV0hNIQl2PwlwrtgufB6eXaCdo8nomBb9aiJV3IYP1pyK4vujVf waOq5rOO/9n8kW3SRMatLNoyyCzXdqakhSdapNxkw/RYh7wBPmN/saX/NpREdQSM Um3xyRE6jtWRWe5Up1+42FMXh5R8yAnybyUUAXqghLRO1MFLcXRN3ETs6mzZkz3z O2yGQLpLQYRyu/IYPx7PlovPUjELR5koqeSkg== Received: from [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d] (2001:470:8:6ca:cad7:19ff:fec0:a06d [IPv6:2001:470:8:6ca:cad7:19ff:fec0:a06d]) by varun.vishwin.info (OpenSMTPD) with ESMTPSA id bb6b27e7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Thu, 16 Aug 2018 12:43:53 -0400 (EDT) Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> To: current@freebsd.org From: Charlie Li Openpgp: preference=signencrypt Autocrypt: addr=ml@vishwin.info; keydata= xsFNBFe4p7sBEADHSqa7WkWYRhRiAYsECn4Ek29AkNS7SF4YAbZTzg+3xkPL5cM5zbNCR4U4 o99wC0Y5wQn9y9X9wM16k1AxBkeQ7Dgh+AjxYGnwDjyrVdx9fcId8dQvLV/xw4V2b5CtU0Et M9IE3MDOkgLtWJamTWIL/MfrNgWk5nRZDBhDcygkTO87t0Pi4WC/QQ3TrrDya6FbBPI7I5Y2 0arX2LAeXqJ6pF7uPfjqogKy3UL+t++9nTG6FNR2oftlts1AB+kGHXJf1GiewXLpPEJTGlXx P+XGhjALqJkFw6azELYKjZcd9zGEOWiKJKp2c2RUDdEJHy+cm6cJ8g7dabVA4ZXs5O7NzeMr on7xFbBx/l/0qHux+d7gS4Z+GJ9WGvzvuj4L8MLgA0eaNzn564RJ5FCtPpaulMhcSc78LhZs NCN3rq8VxsxNrIFTlvnLdLsTNITZOKXnyalE9WlM3cK6UlQaagShhO3FliI2hIOW7j4QWJZC Thynnnj5wIAOgKv1WKFwnKJsMfsohIME6uqmt5AcH5okXGZCcBJx30+enqsoEYOvg0pi5oY7 6F/bQdvHzY2prjeujo0oJhVSeRpv5tjEUBDjX525SPNqvr4uddHiavrFBkesOh7nnOjsEMZ1 i5Q6iZrQpteoafFZTld7tfLw8gMwyiSleKN+x7tJG1H3d1Bd7QARAQABzSFDaGFybGllIExp IDx2aXNod2luQHZpc2h3aW4uaW5mbz7CwYAEEwEIACoCGwMFCQPCZwAFCwkIBwIGFQgJCgsC BBYCAwECHgECF4AFAlfq/VYCGQEACgkQtQ4IJhNZSS0i+g//fRJwTJHY/sjK0T0Mh0PzwSnm OSYEcscxTuMR9BQaXPMFjEPpArtms0Wd9S29BgzLB+F7To9MCFGiDB6yvF5fba4Zz+oJ9hB8 lJ3lvY1Hr/hxdxK6Etzl/oXM8LN08Hi9XrHDWm1yuLLJvpaynoOGotZYDLoh0hPomPp3j1w/ BcVK6cRCUArAhXwH0HWTKYlZcRsL/paTXvVgi0TKqF29u2ADhjukQh7qAwcZebC+FfxV9On4 1gCkco144JJX77Ak7g/IWeJy7MJCzbwH41PNyn/X5lwv5N+4cKcGlSOi1ndJuySY2G2Pr1Wu rRyUQ/BF70/laaQOsd5Eg4QimzhOJ3G7QqtYOCZdFBvRs4i3ht0tyKgh4NIr9Zl6FaX/AsDJ d1PBdaWdUaY3NHEDFHtntL9xWxdc+UM21fMqAh+TK4zY+FhaudZO1MdBjrMd8ukjpveaoWZJ NgFageX28AWqxFpOhcPDchkUnydqmEEnl87zuZ8OS+HilDH4JzVGAnYrCG4+/h0b9V4QGevS Jp5lnmSXv2/YFkTDHSXmyBTXrVCjfZM3zH9I+3unYxwio0iAhj8sE4gD2Mx53fmBzoS/3ckf dbG0rZ2lecEFiWez4wn7YTHWLl2ujmeBbhjoyY5JPjvOCkn2Gbcy7tJZqTW7ajkWzZQcexyW 7lLoCkCXz9zOwU0EV7inuwEQAOaRmAfkM3cDXbGYr+8QZ08T037xFyTx3pPtfg74BaL1DF5o 4nr7XG410rHT3biOUxH3Gk7NILQibA746zm/TKjj8m/S4xc+aGA8l/Wx34C/6UO+zUNg0Cpz Vynmwtvj6oh/guoPuO2mELf0tQTXEP8vo4nRVcuYlDm0VKHS5OFadlZuYc8vlCx3jOC0vXyC DUKSZu5HdcP3a75OUrHFa7fS6A6n4J8/OKyiXXO9+tUielafHv0zF4Enl7pJgRXLPoJm5FZk RQWNdltVXtfPeOvhM8Plwk5XXjkNShGhsCzTF56f2DUlHCXJQAVDHAbYuscifUY+2HrA41SY SMM1nS5YpQXRWOMuxeh1xwia1GNvgaJdaucCKZ4Fff1F6YuTPKGCOEOifRPoLfO6Te93o2Fs NvNWutiCO0jJj1rlLLdV44chMbiOIsdMtsMpj5/T/Jrm7aD2NvWXJy5+aDyqjmE529oVBYha ouX9XEeWzUL5MxdqgT2LlmBv/y6XbXhXTOUHBBQyCBbqDqiQOWPtOkusiCajTyY0lsM3gR24 +igkJEMND+kJmMdn7G8pSKy7LgRlW4haGmz+80xfMf593APbzlnGB8gD0aH7/ejYCMkGaYz+ ZwFopkl0I4QQxSc3tvVljDhWNyGZxz2Dw4DNALHiG6xmESX00itf2zMPABMrABEBAAHCwWUE GAEIAA8FAle4p7sCGwwFCQPCZwAACgkQtQ4IJhNZSS3BIxAAsXD7PgkrQWu1DunaiPlL0MbR gv2evjY+2cLdpMt8Je3+e25r8JTbPKIV1QY3q0ju0yXgWLW0dM1hWSVpsQURLNyFYnivXt4q rLuDv4T/xTUo/xuV0rUOXp+oTDVKQ7KhpvKtaZFkP0a1z0pVFJbk7AI5UkQ4+lcuyTqzawxd vxn41s/FNKIxXTtj0PAgthzE0ZivAIj4USRaULC20ZvOYFW6rc10UPmrkLsrfXepakGBc0KJ EajF8LiOUqPE4c4BH2CoeEFu+e5OJAAl4kjj/CuNvtlko1Qjd31HPpMaha4l/WAd4kKPmMeW WuRxFkOwkkJFKW2ycH837Njl8Jn6dFSpgZ5/DPBvRdBXjAgDhySr2h9Zn5b6svtnh1ByKJKv ovzp+64IRqfotlLK3J9X1eKHlq10SyprH6IlxsGyXi987ZeV6/04UUAdmPXio/Enxbtna7D2 Cvo+aXTGM9Yu/YwxfmkWRJvEUUzqCOq63Z0Aa5ckOi+8FLUj3ZryS3ctmph/x/flN+ab4R22 pDL8LW1kwMH4Y4krv7l4GBgJPzkBGmonMclGf19i9zwC3TV8oSQ26cyi5d6QmuE3KN9NuLrD CJo3QQ3fpqQrnJbtd0M6fjuKWN0o7UTVEkcOXWWRF85d33VXG8XTDXEJmAJsELG7txDPNZ9o FqGGsWKHymE= Message-ID: Date: Thu, 16 Aug 2018 12:43:42 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="fcGsCu4DkwAkmEI7QogYEnmPyGF6VKy94" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:44:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fcGsCu4DkwAkmEI7QogYEnmPyGF6VKy94 Content-Type: multipart/mixed; boundary="ZPGA2ptRTpY1LBudAyG9UN72WNEo6AvM5"; protected-headers="v1" From: Charlie Li To: current@freebsd.org Message-ID: Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> In-Reply-To: <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> --ZPGA2ptRTpY1LBudAyG9UN72WNEo6AvM5 Content-Type: text/plain; charset=utf-8 Content-Language: en-GB-large Content-Transfer-Encoding: quoted-printable On 16/08/2018 12:26, Brad Davis wrote: > On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: >> This was caused by r337852, but I didn't investigated further. >> >> The problem is that we have a source file called 'moduli.c' in >> crypto/openssh/ while the build target was moduli, and bmake seen >> 'moduli' in source tree as older than moduli.c, and decided to rebuild= >> it from source, while the two files are unrelated. >=20 > Hi Xin, >=20 > I don't see how that could be the case as I didn't move the file around= , I just moved how it gets installed. >=20 > I have done many many builds with this change in and haven't seen this = problem.. >=20 I've found this one intermittent at best. I'll run a buildworld on anything newer than r337852, get the linker error, update to even the next newer revision that changes completely unrelated files, build succeeds. Case in point, r337835 to r337863 failed, but r337863 to r337865 succeeded. This is all with META_MODE, so could be a bug with that. --=20 Charlie Li Can't think of a witty .sigline today=E2=80=A6 (This email address is for mailing list use only; replace local-part with vishwin for off-list communication) --ZPGA2ptRTpY1LBudAyG9UN72WNEo6AvM5-- --fcGsCu4DkwAkmEI7QogYEnmPyGF6VKy94 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE/RdyC3Asy49czZEGtQ4IJhNZSS0FAlt1qcgACgkQtQ4IJhNZ SS3nnw//TwizEWTK1QGowhmvQ+hwgIrPvAC6W8z3uh0pcJmtDlzTC/4dZ923C3Q7 IWQdB8QYrGMREBgE+n3a3m27HXA7pymJi/1qM0flRpqq6RWepElhAIBM0p32H/Dz yyT5idWiTBqt9uylMdF6aOSgVniJgXXKgbtBPMkwmH0HCkGU7TTlKdFkPQ4r7fGe AtqiY+SID86J3fMOVTlp9Uu56+c5nAALYbOgj6hfkMRRbKwg3QYGksq9PBqxU4FQ iVzP/C0KgT4CFC+q1jsshwiswPnkVJEOvLX6RBLxJj3geyxdQnWpm7wmsjgVYlNM PFK5bziEmXUcFb4axHRKe03CYspGyhFWJyVICo3JC15lOneB1NMVEL33LOT1TIih e0wYRsWxWmaSku4bxSqH0xVnKTLn8il9AYP6893UlHIHQnW94FtQunr6uAhqPU3b WgQqdTRH/pWp7zDeXOmG8kpB0Phcoh9tvY1xDzuMag8zG/AbLV3hTVjQFZz7jXKJ 6Btkuf5I9NNnOfu3Up9Mv0DrgEqGdsEhSD49YGNGrnnJENoQG69ih4glnuXePZrU MSGGDEEfW+jecUrr9czUSdMhiLyDeYtqpIx7HqTIYboLzoAnlHDpH2CQfBUZGAYV 3WQNgEM7EVoU8pYnAQRi9sdBDJZSit6R4lOWIb7vyu/PmExT/oU= =f1hK -----END PGP SIGNATURE----- --fcGsCu4DkwAkmEI7QogYEnmPyGF6VKy94-- From owner-freebsd-current@freebsd.org Thu Aug 16 16:52:08 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B6BE106E1C1 for ; Thu, 16 Aug 2018 16:52:08 +0000 (UTC) (envelope-from david@catwhisker.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 E12968D1AD for ; Thu, 16 Aug 2018 16:52:07 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id A5DA7106E1C0; Thu, 16 Aug 2018 16:52:07 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 94987106E1BF for ; Thu, 16 Aug 2018 16:52:07 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 D6BE88D1A7 for ; Thu, 16 Aug 2018 16:52:06 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7GGpvVT076564; Thu, 16 Aug 2018 16:51:57 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7GGpvss076563; Thu, 16 Aug 2018 09:51:57 -0700 (PDT) (envelope-from david) Date: Thu, 16 Aug 2018 09:51:57 -0700 From: David Wolfskill To: Charlie Li Cc: current@freebsd.org Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] Message-ID: <20180816165157.GB1190@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , Charlie Li , current@freebsd.org References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="1suy130rwF7rDuYl" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:52:08 -0000 --1suy130rwF7rDuYl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 16, 2018 at 12:43:42PM -0400, Charlie Li wrote: > .... > I've found this one intermittent at best. I'll run a buildworld on > anything newer than r337852, get the linker error, update to even the > next newer revision that changes completely unrelated files, build > succeeds. Case in point, r337835 to r337863 failed, but r337863 to > r337865 succeeded. I got the "one" I reported twice this morning, on each of two different machines, so that's four out of four. Granted, that doesn't necessarily make it "reproducible," but it does reduce the odds that its another race condition, for example. And one of those machines is currently available for testing possible fixes (after I power it back up). > This is all with META_MODE, so could be a bug with that. True -- I am using META_MODE (as my mention of the .ERROR_META_FILE indicated). Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --1suy130rwF7rDuYl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt1q61fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7he9xAf+N2KH2yoHriHf5nq8uJyL+hKoQtH522QjE1WeE9qUYS1fK5kBwAemZlfI 5xgvIUE7DwMMR67qIEIkJrwbQcTt4h0P621GqWWGM2fDsSGwWmcTPgITcqChfyog Q1gUIWuEAnjFM7wsWUKPjMT/doH/Fbsf5tlut8MHPcf5UFg2HfUvvRCoiNKO2XLR aTrOo+neytsdBWn7TdmTlvqRGVTGSvkFujKtym/K2fzACXeKPHKy3fxYJ7EPM/jP sbeukJcVqqRnu8JesPjK/2/vT631aZRpFuHOC/iLt3+ZTKQfXO3C3UvYNC0B/mHr QvZHxkBNr2F0GWEZMBZo6XZ/sMxlgQ== =9aUP -----END PGP SIGNATURE----- --1suy130rwF7rDuYl-- From owner-freebsd-current@freebsd.org Thu Aug 16 16:53:39 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC00B106E40F for ; Thu, 16 Aug 2018 16:53:39 +0000 (UTC) (envelope-from ler@lerctr.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 54C718D45C for ; Thu, 16 Aug 2018 16:53:39 +0000 (UTC) (envelope-from ler@lerctr.org) Received: by mailman.ysv.freebsd.org (Postfix) id 1A385106E402; Thu, 16 Aug 2018 16:53:39 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D4896106E3FF for ; Thu, 16 Aug 2018 16:53:38 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [IPv6:2001:470:1f0f:3ad:bb:dcff:fe50:d900]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.lerctr.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 790368D45A for ; Thu, 16 Aug 2018 16:53:38 +0000 (UTC) (envelope-from ler@lerctr.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lerctr.org; s=lerami; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=oNycxP93LkQS3/mdYWGTM6TG1yORxvC3xesHUdKlHZU=; b=vmE7+uVL/hyTRiqYrYnDF4pKYO zIi1JVVQclJRWkIMaK+DgzQCph+Gr10L/WEyzn2SicSZmMZMalu4UpeUlbNjipuEqvpa37F61Ju+Q iWL9HPIN4P8YyLr3r4zpuo4OfceZw4OExwcHJ0eXeRngTGG+HmTAStdyoXdYlkmhkh7g=; Received: from [2600:1700:210:b18f:4c0:e5c4:68ef:d5be] (port=54517 helo=ler-imac.local) by thebighonker.lerctr.org with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91 (FreeBSD)) (envelope-from ) id 1fqLWj-000IWX-RX; Thu, 16 Aug 2018 11:53:37 -0500 Date: Thu, 16 Aug 2018 11:53:37 -0500 From: Larry Rosenman To: Charlie Li Cc: current@freebsd.org Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] Message-ID: <20180816165337.n4uxpkbpn52mewfa@ler-imac.local> References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="dhdv4r42yvl3da6j" Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 16:53:40 -0000 --dhdv4r42yvl3da6j Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 16, 2018 at 12:43:42PM -0400, Charlie Li wrote: > On 16/08/2018 12:26, Brad Davis wrote: > > On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: > >> This was caused by r337852, but I didn't investigated further. > >> > >> The problem is that we have a source file called 'moduli.c' in > >> crypto/openssh/ while the build target was moduli, and bmake seen > >> 'moduli' in source tree as older than moduli.c, and decided to rebuild > >> it from source, while the two files are unrelated. > >=20 > > Hi Xin, > >=20 > > I don't see how that could be the case as I didn't move the file around= , I just moved how it gets installed. > >=20 > > I have done many many builds with this change in and haven't seen this = problem.. > >=20 > I've found this one intermittent at best. I'll run a buildworld on > anything newer than r337852, get the linker error, update to even the > next newer revision that changes completely unrelated files, build > succeeds. Case in point, r337835 to r337863 failed, but r337863 to > r337865 succeeded. >=20 > This is all with META_MODE, so could be a bug with that. I've seen the same thing with meta-mode. A svn up after the failure restores the missing moduli file, and a re-run will succeed. borg.lerctr.org /usr/src $ sudo svn up Updating '.': Restored 'crypto/openssh/moduli' At revision 337914. borg.lerctr.org /usr/src $ >=20 > --=20 > Charlie Li > Can't think of a witty .sigline today=E2=80=A6 >=20 > (This email address is for mailing list use only; replace local-part > with vishwin for off-list communication) >=20 --=20 Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: ler@lerctr.org US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106 --dhdv4r42yvl3da6j Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQHABAABCgCqFiEEHjgknedhWzvJgwVzaXyZsatIp30FAlt1rBEsFIAAAAAAFQAO cGthLWFkZHJlc3NAZ251cGcub3JnbGVyQGxlcmN0ci5vcmdfFIAAAAAALgAoaXNz dWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDFFMzgy NDlERTc2MTVCM0JDOTgzMDU3MzY5N0M5OUIxQUI0OEE3N0QACgkQaXyZsatIp32q GAf+MJyDkOP+C96LQWF54aud1+hcWGMELssKceDMt5Xz3J91L1+vtBFgKoJHJ35R 2eK3JevfnMeqi9/4xVVrq18/JT0Nw32wpFLUtjNeO7MS1pFD2616aKMiw2/Vmr1F ZDQPaAjLJalndZATNNGRD9KaA1VneARdyMKpdruw20BshossaXQD5k8zyV4MpUEC Hb+AcRtXz/E32LjD963INpHr9G5BmdVPGpShoOnE5V9J7f3EhAwqn25myY1Jqdy/ 0eOxGmIPlv3SFi3H6JmFjhy7dLQvuVuAi8m2SZv3Qs0WhfCSeA0PtiYNRuOlUgAJ ew0wvKdNgaUtGQG5b3mPmUXgOQ== =xjmB -----END PGP SIGNATURE----- --dhdv4r42yvl3da6j-- From owner-freebsd-current@freebsd.org Thu Aug 16 18:25:52 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61E041071E6B for ; Thu, 16 Aug 2018 18:25:52 +0000 (UTC) (envelope-from delphij@gmail.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 F04DF7185B for ; Thu, 16 Aug 2018 18:25:51 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B51A91071E69; Thu, 16 Aug 2018 18:25:51 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 933961071E68 for ; Thu, 16 Aug 2018 18:25:51 +0000 (UTC) (envelope-from delphij@gmail.com) Received: from mail-io0-x242.google.com (mail-io0-x242.google.com [IPv6:2607:f8b0:4001:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2AD7E71859; Thu, 16 Aug 2018 18:25:51 +0000 (UTC) (envelope-from delphij@gmail.com) Received: by mail-io0-x242.google.com with SMTP id m4-v6so4676984iop.3; Thu, 16 Aug 2018 11:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bPJdUaP01IGYte6aNaiVn2zQUCqNONRMwkAgaBZawOg=; b=bVtueghwymi0iO93KBpX2iikdT2TR96JPHf96a4zfqUFf6ikhfbi9aOeX0ozESG1GZ V9mjUGimpBYGGIs1O8kmgrwGxzM7n6BDiuoIb/YfLUsGd0Id5JiR9flT1AK/pQGbc+u8 hDZaSlsmEytxNxRzVusgbbM2Swfz4sRULEpKFgWWd0enlRNRZTN9DspBLJPjEJVJPES2 q1LC5AlgVUwjkRCb+VXCX1XL4e3XXSG50f2uPwE7TVwLWkv9rNv3FrCPiKfcjmuCXksv zFCqwuhT+KujO77D3PBwbRCQmCT5I2oki34A8OP5s1bW7K1YOY2FbKiTc2cKTt8XrHSO YkaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bPJdUaP01IGYte6aNaiVn2zQUCqNONRMwkAgaBZawOg=; b=W2ralk4E6P4AVc/DPgBCQ5RRbMm0UEH3jVXxpR5otptriXubMTMau9KqU78iHhFTsR qRVe5a9RqvjqrsG85NDBjjIpeh/ffaRUsx/1+Imay7Y9mh3qDyGMOQlDej1x9pDJE0s6 XSL+JXH5QP4pySf6TM1a2jlk8BfC4lho9k4rGewI7PBOcaR7xnWO/VsdHIMLOtQtmLp+ C2WfuiLcbWPCwadEZS2zw+tNRFW8kEt4PjeHvMH7D069vDmDKbLo+X6ZAQao+gZwA7Ow m+H3xKWSf2sToAVR/IkuVWkPF7JTEjut/dQqSW9Y1Rr3cmL3xc1SLQsgpopB4RVdVnJh vjbg== X-Gm-Message-State: AOUpUlGnXR6d1paRnXYu1nm2hhBtyyFgiO1m8+SLC45Pf6mlaW6s5hKR 96OzD50n5ct5L77pgQQwi4EfvcA2tgnW8JlNdYfwAA== X-Google-Smtp-Source: AA+uWPz8fRCRxeSyt0snFIX0gih5F3hV1YF3+6Y3jQ9RiStjZ0G50BixMuuhcZsYMJLyETOIXmRibLdNLybhFHoKNuQ= X-Received: by 2002:a6b:1e52:: with SMTP id e79-v6mr27333314ioe.110.1534443949820; Thu, 16 Aug 2018 11:25:49 -0700 (PDT) MIME-Version: 1.0 References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> In-Reply-To: <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> From: Xin LI Date: Thu, 16 Aug 2018 11:25:39 -0700 Message-ID: Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] To: Brad Davis Cc: current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 18:25:52 -0000 On Thu, Aug 16, 2018 at 9:26 AM Brad Davis wrote: > > On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: > > This was caused by r337852, but I didn't investigated further. > > > > The problem is that we have a source file called 'moduli.c' in > > crypto/openssh/ while the build target was moduli, and bmake seen > > 'moduli' in source tree as older than moduli.c, and decided to rebuild > > it from source, while the two files are unrelated. > > Hi Xin, > > I don't see how that could be the case as I didn't move the file around, = I just moved how it gets installed. > > I have done many many builds with this change in and haven't seen this pr= oblem.. Yeah, let me rephrase: this might have been exposed by r337852; I don't think your change itself really caused or should have caused problem, but my theory based on what we have observed was that it might have exposed a bug where either bmake itself, or some .mk files might have generated e.g. automatic rule for ${foo}: ${foo}.c rules (haven't traced that part down yet). The most scaring part is that the build system seems to trying building crypto/openssh/moduli because moduli.c was newer, and the file was deleted as part of the rebuild; should moduli.c compile by its own, we would end up with a binary moduli file. I'll take another look tonight if I had some time. > > > Regards, > Brad Davis > > > On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill = wrote: > > > > > > Running: > > > > > > FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #80 r3= 37834M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018 root@g1-215.catwhis= ker.org:/common/S4/obj/usr/src/amd64.amd64/sys/CANARY amd64 > > > > > > after updating working copy to r337903, I'm seeing: > > > > > > ... > > > >>> stage 4.3: building everything > > > ... > > > --- ifconfig_make --- > > > Building /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbi= n/ifconfig/af_inet6.o > > > --- all_subdir_secure --- > > > --- moduli --- > > > /usr/bin/ld: error: undefined symbol: main > > > >>> referenced by crt1.c > > > >>> /common/S4/obj/usr/src/amd64.amd64/tmp/usr/lib/crt1= .o:(_start) > > > /usr/bin/ld: error: undefined symbol: Fssh_error > > > .... > > > make[5]: stopped in /usr/src/secure/usr.sbin/sshd > > > .ERROR_TARGET=3D'moduli' > > > .ERROR_META_FILE=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbi= n/sshd/moduli.meta' > > > .MAKE.LEVEL=3D'5' > > > MAKEFILE=3D'' > > > .MAKE.MODE=3D'meta missing-filemon=3Dyes missing-meta=3Dyes silent=3D= yes verbose' > > > _ERROR_CMD=3D'cc -target x86_64-unknown-freebsd12.0 --sysroot=3D/comm= on/S4/obj/usr/src/amd64.amd64/tmp -B/common/S4/obj/usr/src/amd64.amd64/tmp/= usr/bin -O2 -pipe -I/usr/src/crypto/openssh -include ssh_namespace.h -DHA= VE_LDNS=3D1 -DUSE_BSM_AUDIT=3D1 -DHAVE_GETAUDIT_ADDR=3D1 -DUSE_BLACKLIST=3D= 1 -I/usr/src/contrib/blacklist/include -include krb5_config.h -DLIBWRAP=3D1= -std=3Dgnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -W= no-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wn= o-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-con= version -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch= -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-ar= guments -L/common/S4/obj/usr/src/amd64.amd64/lib/libblacklist /usr/src/c= rypto/openssh/moduli.c -o moduli; ;' > > > .CURDIR=3D'/usr/src/secure/usr.sbin/sshd' > > > .MAKE=3D'make' > > > .OBJDIR=3D'/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/sshd' > > > .TARGETS=3D'all' > > > DESTDIR=3D'/common/S4/obj/usr/src/amd64.amd64/tmp' > > > .... > > > > > > (on both the laptop and the build machine). > > > > > > I have copied the .ERROR_META_FILE to > > > > > a typescript of the attempted build to > > > . > > > > > > Additional information (previous day's verbose dmesg.bot, etc.) may > > > be found at . > > > > > > Peace, > > > david > > > -- > > > David H. Wolfskill david@catwhisker.org > > > Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-449= 59300 > > > > > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@freebsd.org Thu Aug 16 19:10:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06A5A10734E9 for ; Thu, 16 Aug 2018 19:10:06 +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 9B6C2740BD for ; Thu, 16 Aug 2018 19:10:05 +0000 (UTC) (envelope-from ian@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 60B2B10734E7; Thu, 16 Aug 2018 19:10:05 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F09D10734E5 for ; Thu, 16 Aug 2018 19:10:05 +0000 (UTC) (envelope-from ian@freebsd.org) Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org [52.58.109.202]) (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 C26FA740B8 for ; Thu, 16 Aug 2018 19:10:04 +0000 (UTC) (envelope-from ian@freebsd.org) X-MHO-RoutePath: aGlwcGll X-MHO-User: f7c22bcd-a187-11e8-aff6-0b9b8210da61 X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information X-Originating-IP: 67.177.211.60 X-Mail-Handler: DuoCircle Outbound SMTP Received: from ilsoft.org (unknown [67.177.211.60]) by outbound1.eu.mailhop.org (Halon) with ESMTPSA id f7c22bcd-a187-11e8-aff6-0b9b8210da61; Thu, 16 Aug 2018 19:09:59 +0000 (UTC) Received: from rev (rev [172.22.42.240]) by ilsoft.org (8.15.2/8.15.2) with ESMTP id w7GJ9wKZ078491; Thu, 16 Aug 2018 13:09:58 -0600 (MDT) (envelope-from ian@freebsd.org) Message-ID: <1534446597.1466.42.camel@freebsd.org> Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] From: Ian Lepore To: Xin LI , Brad Davis Cc: current@freebsd.org Date: Thu, 16 Aug 2018 13:09:57 -0600 In-Reply-To: References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 19:10:06 -0000 On Thu, 2018-08-16 at 11:25 -0700, Xin LI wrote: > On Thu, Aug 16, 2018 at 9:26 AM Brad Davis wrote: > > > > > > On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: > > > > > > This was caused by r337852, but I didn't investigated further. > > > > > > The problem is that we have a source file called 'moduli.c' in > > > crypto/openssh/ while the build target was moduli, and bmake seen > > > 'moduli' in source tree as older than moduli.c, and decided to > > > rebuild > > > it from source, while the two files are unrelated. > > Hi Xin, > > > > I don't see how that could be the case as I didn't move the file > > around, I just moved how it gets installed. > > > > I have done many many builds with this change in and haven't seen > > this problem.. > Yeah, let me rephrase: this might have been exposed by r337852; I > don't think your change itself really caused or should have caused > problem, but my theory based on what we have observed was that it > might have exposed a bug where either bmake itself, or some .mk files > might have generated e.g. automatic rule for ${foo}: ${foo}.c rules > (haven't traced that part down yet). > There is an implicit rule to build file from file.c, it's why you can type "make foo" in a dir that contains a foo.c and no Makefile. The CONFS=moduli makes moduli into a target.  The implicit rules search finds the rule to make moduli from moduli.c and because of the .PATH it's able to find a moduli.c. It might be fixable by simply adding a target with a do-nothing script for building moduli in usr.sbin/sshd/Makefile.  Something like moduli:     @ : # Do nothing. But that's just a wild guess on my part, not sure that'll work. Hmm, in fact, it'll probably cause a make warning about duplicate targets with scripts. --Ian > The most scaring part is that the build system seems to trying > building crypto/openssh/moduli because moduli.c was newer, and the > file was deleted as part of the rebuild; should moduli.c compile by > its own, we would end up with a binary moduli file. > > I'll take another look tonight if I had some time. > > > > > > > > > Regards, > > Brad Davis > > > > > > > > On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill > > .org> wrote: > > > > > > > > > > > > Running: > > > > > > > > FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 > > > > #80  r337834M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018      > > > > root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/s > > > > ys/CANARY  amd64 > > > > > > > > after updating working copy to r337903, I'm seeing: > > > > > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > > stage 4.3: building everything > > > > ... > > > > --- ifconfig_make --- > > > > Building > > > > /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/i > > > > fconfig/af_inet6.o > > > > --- all_subdir_secure --- > > > > --- moduli --- > > > > /usr/bin/ld: error: undefined symbol: main > > > > > > > > > > > > > > > > > > > > > > > > > referenced by crt1.c > > > > > > >               /common/S4/obj/usr/src/amd64.amd64/tmp/usr/ > > > > > > > lib/crt1.o:(_start) > > > > /usr/bin/ld: error: undefined symbol: Fssh_error > > > > .... > > > > make[5]: stopped in /usr/src/secure/usr.sbin/sshd > > > > .ERROR_TARGET='moduli' > > > > .ERROR_META_FILE='/common/S4/obj/usr/src/amd64.amd64/secure/usr > > > > .sbin/sshd/moduli.meta' > > > > .MAKE.LEVEL='5' > > > > MAKEFILE='' > > > > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes > > > > silent=yes verbose' > > > > _ERROR_CMD='cc -target x86_64-unknown-freebsd12.0 -- > > > > sysroot=/common/S4/obj/usr/src/amd64.amd64/tmp > > > > -B/common/S4/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe   - > > > > I/usr/src/crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 > > > > -DUSE_BSM_AUDIT=1 -DHAVE_GETAUDIT_ADDR=1 -DUSE_BLACKLIST=1 > > > > -I/usr/src/contrib/blacklist/include -include krb5_config.h > > > > -DLIBWRAP=1 -std=gnu99 -fstack-protector-strong -Wno-pointer- > > > > sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const- > > > > variable -Wno-tautological-compare -Wno-unused-value -Wno- > > > > parentheses-equality -Wno-unused-function -Wno-enum-conversion > > > > -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno- > > > > switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno- > > > > parentheses  -Qunused-arguments   - > > > > L/common/S4/obj/usr/src/amd64.amd64/lib/libblacklist  /usr/src/ > > > > crypto/openssh/moduli.c  -o moduli; ;' > > > > .CURDIR='/usr/src/secure/usr.sbin/sshd' > > > > .MAKE='make' > > > > .OBJDIR='/common/S4/obj/usr/src/amd64.amd64/secure/usr.sbin/ssh > > > > d' > > > > .TARGETS='all' > > > > DESTDIR='/common/S4/obj/usr/src/amd64.amd64/tmp' > > > > .... > > > > > > > > (on both the laptop and the build machine). > > > > > > > > I have copied the .ERROR_META_FILE to > > > > > > > eta and > > > > a typescript of the attempted build to > > > > > > > pt>. > > > > > > > > Additional information (previous day's verbose dmesg.bot, etc.) > > > > may > > > > be found at > > > > . > > > > > > > > Peace, > > > > david > > > > -- > > > > David H. Wolfskill                              david@catwhiske > > > > r.org > > > > Trump is gaslighting us: https://www.bbc.com/news/world-us-cana > > > > da-44959300 > > > > > > > > See http://www.catwhisker.org/~david/publickey.gpg for my > > > > public key. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd > .org" From owner-freebsd-current@freebsd.org Thu Aug 16 19:44:23 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 333CE1074A15 for ; Thu, 16 Aug 2018 19:44:23 +0000 (UTC) (envelope-from bdrewery@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 B924375FBE for ; Thu, 16 Aug 2018 19:44:22 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 7A8391074A13; Thu, 16 Aug 2018 19:44:22 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 587A51074A12 for ; Thu, 16 Aug 2018 19:44:22 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CD99C75FBD; Thu, 16 Aug 2018 19:44:21 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id 9AEBD9984; Thu, 16 Aug 2018 19:44:21 +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 D5F6D130F; Thu, 16 Aug 2018 19:44:20 +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 UGP0Crujg215; Thu, 16 Aug 2018 19:44:13 +0000 (UTC) Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 4525F1301 To: Larry Rosenman , Charlie Li Cc: current@freebsd.org References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> <20180816165337.n4uxpkbpn52mewfa@ler-imac.local> From: Bryan Drewery Openpgp: preference=signencrypt Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8FAlJp hmsCGwwFCQlmAYAACgkQNddxu25Gl89UPggA2mGQp28yCUKsJ6KHFVy/lpHfoQrKF+s7HfKT U2ObVeVNX4I8ZdW1UO48mRqxEOwY8r5YSH6X06OmiqCX2aSMXg3N06/l+ztlB0+UGGlkXBjv l9/nii+bC6b8XWuu0X7Qpb9oYBK9YtoaoyuVplAmjdj/cPou65meKIaS1yDTjHh450DrW8Qg he6l0bFX4BHKTSm99U90ML7EY19B6iI2BZSqWutVsyD71oAREY6NGgDpCOIO6FS41+WeYCDR j8vsa/BiaoX2d2SBDsCwsEwe9fg5PYMi2uVIhvL6OrxnwOdB+TkgvOy5zZSNO29UG/JilZKo Ndz2wpEaUzChGGqLvcLAZQQYAQoADwIbDAUCWujOKAUJCmB7PQAKCRA113G7bkaXz6bkB/9H dUR3E0wBwMh6z0AOFDKh+PbRI9Xd4IncdhE55tNK410650a3gADIDwqz3i72GIinkgaxzpEO xP1bs7a+BeF3p5Xd6Jjk6J/nEshisgNW7VjUbJHFGs8Sf9A6oM3q4VkI/ArVo5qkZxgKs72U HSAy5NV+AdqdTrWuAL20xfQ6gA7JF35Xf8zyUM2GMl0X8ik7dJ1jMp+TB27LipqbDgamFzH9 F9hC9gur94OQ/x3nQ+mFZ1uipYHA1EdrKuhb/Ts4bN/Ezl8nmYGxc9Bw7ZBxGOTId/rEIzoe LWpAvg6dcw0T9lNfSWc6PX+kf3dOXNIdkw9NqKID8wEPe8axcGYG Organization: FreeBSD Message-ID: <1ce1779f-5fae-0ffe-83f7-11adf85c5cc6@FreeBSD.org> Date: Thu, 16 Aug 2018 12:44:11 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20180816165337.n4uxpkbpn52mewfa@ler-imac.local> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 19:44:23 -0000 On 8/16/18 9:53 AM, Larry Rosenman wrote: > On Thu, Aug 16, 2018 at 12:43:42PM -0400, Charlie Li wrote: >> On 16/08/2018 12:26, Brad Davis wrote: >>> On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: >>>> This was caused by r337852, but I didn't investigated further. >>>> >>>> The problem is that we have a source file called 'moduli.c' in >>>> crypto/openssh/ while the build target was moduli, and bmake seen >>>> 'moduli' in source tree as older than moduli.c, and decided to rebuild >>>> it from source, while the two files are unrelated. >>> >>> Hi Xin, >>> >>> I don't see how that could be the case as I didn't move the file around, I just moved how it gets installed. >>> >>> I have done many many builds with this change in and haven't seen this problem.. >>> >> I've found this one intermittent at best. I'll run a buildworld on >> anything newer than r337852, get the linker error, update to even the >> next newer revision that changes completely unrelated files, build >> succeeds. Case in point, r337835 to r337863 failed, but r337863 to >> r337865 succeeded. >> >> This is all with META_MODE, so could be a bug with that. > I've seen the same thing with meta-mode. A svn up after the failure > restores the missing moduli file, and a re-run will succeed. > > borg.lerctr.org /usr/src $ sudo svn up > Updating '.': > Restored 'crypto/openssh/moduli' > At revision 337914. > borg.lerctr.org /usr/src $ > > FYI it's not META_MODE related. It happens with a clean build as long as the moduli timestamp is old enough. > ~/git/freebsd/secure/usr.sbin/sshd # make buildconfig -dmM MK_META_MODE=no > Make_ExpandUse: examine buildconfig > MakeAddChild: need to examine moduli > MakeAddChild: need to examine sshd_config > Make_ExpandUse: examine moduli > MakeAddChild: need to examine moduli.c > Make_ExpandUse: examine sshd_config > Make_ExpandUse: examine moduli.c > Examining moduli.c...modified 7:59:30 Jun 07, 2018...up-to-date. > Examining moduli...modified 0:00:00 Nov 30, 2017...modified before source /root/git/freebsd/crypto/openssh/moduli.c...out-of-date. > cc -O2 -pipe -I/root/git/freebsd/crypto/openssh -include ssh_namespace.h -DHAVE_LDNS=1 -DUSE_BSM_AUDIT=1 -DHAVE_GETAUDIT_ADDR=1 -DUSE_BLACKLIST=1 -I/root/git/freebsd/contrib/blacklist/include -include > krb5_config.h -DLIBWRAP=1 -DXAUTH_PATH=\"/usr/local/bin/xauth\" -g -std=gnu99 -fstack-protector-strong -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautologic > al-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-pa > rameter -Wno-parentheses -fcolor-diagnostics -Qunused-arguments -L/scratch/obj/root/git/freebsd/amd64.amd64/lib/libblacklist /root/git/freebsd/crypto/openssh/moduli.c -o /root/git/freebsd/crypto/op > enssh/moduli > /usr/bin/ld: error: undefined symbol: main -- Regards, Bryan Drewery From owner-freebsd-current@freebsd.org Thu Aug 16 19:49:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5539F1074CCF for ; Thu, 16 Aug 2018 19:49:12 +0000 (UTC) (envelope-from bdrewery@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 F04B676563 for ; Thu, 16 Aug 2018 19:49:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id B1F781074CCB; Thu, 16 Aug 2018 19:49:11 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 77C041074CC9 for ; Thu, 16 Aug 2018 19:49:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 173657655E; Thu, 16 Aug 2018 19:49:11 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (unknown [127.0.1.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id D6C1A9DE9; Thu, 16 Aug 2018 19:49:10 +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 1AA431368; Thu, 16 Aug 2018 19:49:10 +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 fLziLlV0rfmN; Thu, 16 Aug 2018 19:49:07 +0000 (UTC) Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com 81FB01350 To: Ian Lepore , Xin LI , Brad Davis Cc: current@freebsd.org References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> <1534446597.1466.42.camel@freebsd.org> From: Bryan Drewery Openpgp: preference=signencrypt Autocrypt: addr=bdrewery@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJphmsBCADiFgmS4bIzwZijrS31SjEMzg+n5zNellgM+HkShwehpqCiyhXdWrvH6dTZ a6u50pbUIX7doTR7W7PQHCjCTqtpwvcj0eulZva+iHFp+XrbgSFHn+VVXgkYP2MFySyZRFab D2qqzJBEJofhpv4HvY6uQI5K99pMqKr1Z/lHqsijYYu4RH2OfwB5PinId7xeldzWEonVoCr+ rfxzO/UrgA6v/3layGZcKNHFjmc3NqoN1DXtdaEHqtjIozzbndVkH6lkFvIpIrI6i5ox8pwp VxsxLCr/4Musd5CWgHiet5kSw2SzNeA8FbxdLYCpXNVu+uBACEbCUP+CSNy3NVfEUxsBABEB AAHNJEJyeWFuIERyZXdlcnkgPGJkcmV3ZXJ5QEZyZWVCU0Qub3JnPsLAgAQTAQoAKgIbAwUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAIZAQUCWujOIgUJCmB7NwAKCRA113G7bkaXz/xpB/9b /UWIPbieY1IeIuHF2pyYPE7Hytkh3HVsxMA0F5Ma2AYQsXZZeKNKWrF7RPyDyDwUklLHJkhm k3EfClBbHxf08kMIm1vWCJRtgxic9knY/bzYGiWMpHjg3cSd1XfrYH1autYqTZAjDwIkgOjU dR//Tbn4V36sY7y2jz+kdMVWvK53U32aZqiwBbCn4DPe1wSZcUs17mV/0uZdIoGdj74B1orN A/0py5vHYo6HcbBNoaR8pKRLf5VZNRsxqGIMhTucx4SJWcHpuRBWYyvJSFzwvxdK4ZD4Yqoc kFGPVtOXktVMai9exrLvP3G77fKMu8DI6j4QRU4wCesnHuIfRPFuzsBNBFJphmsBCACiVFPf kNfaFtUSuY0395ueo/rMyHPGPQ2iwvERFCpeFGSQSgagpenNHLpFQKTg/dl6FOoST5tqyxMq fyHGHDzzU51bvA/IfaGoNi/BIhTe/toZNMRvpcI3PLjiGcnJnuwCCbAVOAGdb+t5cZtpNdOI cKYmrYG3u9RiBpe6dTF+qLrD/8Bs1wjhduQ8fcNNgnkXu8xDH4ZxY0lIc3QgvYWp9vimlQe6 iKjUd2/DX28ETZcD5h6pYV331KMPTrEI0p0yvFijUZce8c1XHFyL1j9sBAha5qpszJl6Uq5i LolhKRcGfcdmtD72vHQjUYglUyudSJUVyo2gMYjdbiFKzJulABEBAAHCwGUEGAEKAA8FAlJp hmsCGwwFCQlmAYAACgkQNddxu25Gl89UPggA2mGQp28yCUKsJ6KHFVy/lpHfoQrKF+s7HfKT U2ObVeVNX4I8ZdW1UO48mRqxEOwY8r5YSH6X06OmiqCX2aSMXg3N06/l+ztlB0+UGGlkXBjv l9/nii+bC6b8XWuu0X7Qpb9oYBK9YtoaoyuVplAmjdj/cPou65meKIaS1yDTjHh450DrW8Qg he6l0bFX4BHKTSm99U90ML7EY19B6iI2BZSqWutVsyD71oAREY6NGgDpCOIO6FS41+WeYCDR j8vsa/BiaoX2d2SBDsCwsEwe9fg5PYMi2uVIhvL6OrxnwOdB+TkgvOy5zZSNO29UG/JilZKo Ndz2wpEaUzChGGqLvcLAZQQYAQoADwIbDAUCWujOKAUJCmB7PQAKCRA113G7bkaXz6bkB/9H dUR3E0wBwMh6z0AOFDKh+PbRI9Xd4IncdhE55tNK410650a3gADIDwqz3i72GIinkgaxzpEO xP1bs7a+BeF3p5Xd6Jjk6J/nEshisgNW7VjUbJHFGs8Sf9A6oM3q4VkI/ArVo5qkZxgKs72U HSAy5NV+AdqdTrWuAL20xfQ6gA7JF35Xf8zyUM2GMl0X8ik7dJ1jMp+TB27LipqbDgamFzH9 F9hC9gur94OQ/x3nQ+mFZ1uipYHA1EdrKuhb/Ts4bN/Ezl8nmYGxc9Bw7ZBxGOTId/rEIzoe LWpAvg6dcw0T9lNfSWc6PX+kf3dOXNIdkw9NqKID8wEPe8axcGYG Organization: FreeBSD Message-ID: Date: Thu, 16 Aug 2018 12:49:06 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <1534446597.1466.42.camel@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="lx8RFjRFPQNJyMUY8oCdvMyxTvcGQH44n" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 19:49:12 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --lx8RFjRFPQNJyMUY8oCdvMyxTvcGQH44n Content-Type: multipart/mixed; boundary="e5ZZ5HvJQvOC6ZpVEZyiwWyAtUs74K6mf"; protected-headers="v1" From: Bryan Drewery To: Ian Lepore , Xin LI , Brad Davis Cc: current@freebsd.org Message-ID: Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> <1534446597.1466.42.camel@freebsd.org> In-Reply-To: <1534446597.1466.42.camel@freebsd.org> --e5ZZ5HvJQvOC6ZpVEZyiwWyAtUs74K6mf Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 8/16/18 12:09 PM, Ian Lepore wrote: > On Thu, 2018-08-16 at 11:25 -0700, Xin LI wrote: >> On Thu, Aug 16, 2018 at 9:26 AM Brad Davis wrote: >>> >>> >>> On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: >>>> >>>> This was caused by r337852, but I didn't investigated further. >>>> >>>> The problem is that we have a source file called 'moduli.c' in >>>> crypto/openssh/ while the build target was moduli, and bmake seen >>>> 'moduli' in source tree as older than moduli.c, and decided to >>>> rebuild >>>> it from source, while the two files are unrelated. >>> Hi Xin, >>> >>> I don't see how that could be the case as I didn't move the file >>> around, I just moved how it gets installed. >>> >>> I have done many many builds with this change in and haven't seen >>> this problem.. >> Yeah, let me rephrase: this might have been exposed by r337852; I >> don't think your change itself really caused or should have caused >> problem, but my theory based on what we have observed was that it >> might have exposed a bug where either bmake itself, or some .mk files >> might have generated e.g. automatic rule for ${foo}: ${foo}.c rules >> (haven't traced that part down yet). >> >=20 > There is an implicit rule to build file from file.c, it's why you can > type "make foo" in a dir that contains a foo.c and no Makefile. >=20 > The CONFS=3Dmoduli makes moduli into a target. =C2=A0The implicit rules= search > finds the rule to make moduli from moduli.c and because of the .PATH > it's able to find a moduli.c. >=20 > It might be fixable by simply adding a target with a do-nothing script > for building moduli in usr.sbin/sshd/Makefile. =C2=A0Something like >=20 > moduli: > =C2=A0 =C2=A0 @ : # Do nothing. >=20 > But that's just a wild guess on my part, not sure that'll work. Hmm, in= > fact, it'll probably cause a make warning about duplicate targets with > scripts. >=20 > --Ian >=20 >> The most scaring part is that the build system seems to trying >> building crypto/openssh/moduli because moduli.c was newer, and the >> file was deleted as part of the rebuild; should moduli.c compile by >> its own, we would end up with a binary moduli file. >> >> I'll take another look tonight if I had some time. >> >>> >>> >>> >>> Regards, >>> Brad Davis >>> >>>> >>>> On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill >>> .org> wrote: >>>>> >>>>> >>>>> Running: >>>>> >>>>> FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 >>>>> #80=C2=A0=C2=A0r337834M/337834:1200077: Wed Aug 15 04:34:45 PDT 201= 8=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 >>>>> root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/s >>>>> ys/CANARY=C2=A0=C2=A0amd64 >>>>> >>>>> after updating working copy to r337903, I'm seeing: >>>>> >>>>> ... >>>>>> >>>>>>> >>>>>>>> >>>>>>>> stage 4.3: building everything >>>>> ... >>>>> --- ifconfig_make --- >>>>> Building >>>>> /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/i >>>>> fconfig/af_inet6.o >>>>> --- all_subdir_secure --- >>>>> --- moduli --- >>>>> /usr/bin/ld: error: undefined symbol: main >>>>>> r337928 should fix it. --=20 Regards, Bryan Drewery --e5ZZ5HvJQvOC6ZpVEZyiwWyAtUs74K6mf-- --lx8RFjRFPQNJyMUY8oCdvMyxTvcGQH44n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE+Rc8ssOq6npcih8JNddxu25Gl88FAlt11TMACgkQNddxu25G l89pRgf/RTKp03Ef/5iHKsVqqMe4qKxQ6aZaPSz4Ipua0fSGfWrPEESAhKGiPccU YmkudHpBBr+U+0pu07djhWCiHLT7ixg9sR+tpiCiTG6eqF5zXxAF52G+q/RTvAx4 3vwJbuD5DpMl8k0zwzyOHXBKdOOfc3J6qhhxJ3/wKpuEAh/pHQUfv3OPTauiH/gZ LVJsSSjy1X1a08cnkVnfyArhyaRV2x9QYkSjOm0DSZduvkZ/icfzWYDLnJznRuZo QHcVg0lw1/jwkZT8yilstLf+mr7jfeEVvI6XAIpaQMIfUdTvUBfdGKlntobBBlVs kPvT0PtSzyPZ22YC0AQ9rWr10xYQfQ== =jrc6 -----END PGP SIGNATURE----- --lx8RFjRFPQNJyMUY8oCdvMyxTvcGQH44n-- From owner-freebsd-current@freebsd.org Thu Aug 16 20:03:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 938BE10755CB for ; Thu, 16 Aug 2018 20:03:22 +0000 (UTC) (envelope-from brd@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 1A1D8771D7 for ; Thu, 16 Aug 2018 20:03:22 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id D2E0B10755CA; Thu, 16 Aug 2018 20:03:21 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B0ED710755C9 for ; Thu, 16 Aug 2018 20:03:21 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D0EC771D4; Thu, 16 Aug 2018 20:03:21 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from auth1-smtp.messagingengine.com (auth1-smtp.messagingengine.com [66.111.4.227]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: brd/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 394CC20370; Thu, 16 Aug 2018 20:03:21 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailauth.nyi.internal (Postfix) with ESMTP id 08E2E21D23; Thu, 16 Aug 2018 16:03:21 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute5.internal (MEProxy); Thu, 16 Aug 2018 16:03:21 -0400 X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 6BB8C41D5; Thu, 16 Aug 2018 16:03:20 -0400 (EDT) Message-Id: <1534449800.3133736.1476651000.26ADC4C2@webmail.messagingengine.com> From: Brad Davis To: Bryan Drewery , Ian Lepore , Xin LI Cc: current@freebsd.org MIME-Version: 1.0 X-Mailer: MessagingEngine.com Webmail Interface - ajax-7b72137a Date: Thu, 16 Aug 2018 14:03:20 -0600 In-Reply-To: References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> <1534446597.1466.42.camel@freebsd.org> Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 20:03:22 -0000 On Thu, Aug 16, 2018, at 1:49 PM, Bryan Drewery wrote: > On 8/16/18 12:09 PM, Ian Lepore wrote: > > On Thu, 2018-08-16 at 11:25 -0700, Xin LI wrote: > >> On Thu, Aug 16, 2018 at 9:26 AM Brad Davis wrote:> >>> > >>> > >>> On Thu, Aug 16, 2018, at 10:13 AM, Xin LI wrote: > >>>> > >>>> This was caused by r337852, but I didn't investigated further. > >>>> > >>>> The problem is that we have a source file called 'moduli.c' in > >>>> crypto/openssh/ while the build target was moduli, and bmake seen> >>>> 'moduli' in source tree as older than moduli.c, and decided to > >>>> rebuild > >>>> it from source, while the two files are unrelated. > >>> Hi Xin, > >>> > >>> I don't see how that could be the case as I didn't move the file > >>> around, I just moved how it gets installed. > >>> > >>> I have done many many builds with this change in and haven't seen> >>> this problem.. > >> Yeah, let me rephrase: this might have been exposed by r337852; I > >> don't think your change itself really caused or should have caused> >> problem, but my theory based on what we have observed was that it > >> might have exposed a bug where either bmake itself, or some .mk > >> files> >> might have generated e.g. automatic rule for ${foo}: ${foo}.c rules> >> (haven't traced that part down yet). > >> > > > > There is an implicit rule to build file from file.c, it's why > > you can> > type "make foo" in a dir that contains a foo.c and no Makefile. > > > > The CONFS=moduli makes moduli into a target. The implicit rules > > search> > finds the rule to make moduli from moduli.c and because of the .PATH> > it's able to find a moduli.c. > > > > It might be fixable by simply adding a target with a do-nothing > > script> > for building moduli in usr.sbin/sshd/Makefile. Something like > > > > moduli: > > @ : # Do nothing. > > > > But that's just a wild guess on my part, not sure that'll work. > > Hmm, in> > fact, it'll probably cause a make warning about duplicate > > targets with> > scripts. > > > > --Ian > > > >> The most scaring part is that the build system seems to trying > >> building crypto/openssh/moduli because moduli.c was newer, and the> >> file was deleted as part of the rebuild; should moduli.c compile by> >> its own, we would end up with a binary moduli file. > >> > >> I'll take another look tonight if I had some time. > >> > >>> > >>> > >>> > >>> Regards, > >>> Brad Davis > >>> > >>>> > >>>> On Thu, Aug 16, 2018 at 4:19 AM David Wolfskill >>>> .org> wrote: > >>>>> > >>>>> > >>>>> Running: > >>>>> > >>>>> FreeBSD g1-215.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 > >>>>> #80 r337834M/337834:1200077: Wed Aug 15 04:34:45 PDT 2018> >>>>> root@g1-215.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/s> >>>>> ys/CANARY amd64 > >>>>> > >>>>> after updating working copy to r337903, I'm seeing: > >>>>> > >>>>> ... > >>>>>> > >>>>>>> > >>>>>>>> > >>>>>>>> stage 4.3: building everything > >>>>> ... > >>>>> --- ifconfig_make --- > >>>>> Building > >>>>> /common/S4/obj/usr/src/amd64.amd64/rescue/rescue/usr/src/sbin/i> >>>>> fconfig/af_inet6.o > >>>>> --- all_subdir_secure --- > >>>>> --- moduli --- > >>>>> /usr/bin/ld: error: undefined symbol: main > >>>>>> > > r337928 should fix it. > Thank you. Regards, Brad Davis From owner-freebsd-current@freebsd.org Thu Aug 16 20:43:20 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A848C10765DB for ; Thu, 16 Aug 2018 20:43:20 +0000 (UTC) (envelope-from david@catwhisker.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 4784B78E52 for ; Thu, 16 Aug 2018 20:43:20 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0C9FA10765DA; Thu, 16 Aug 2018 20:43:20 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EF8A310765D9 for ; Thu, 16 Aug 2018 20:43:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 367EE78E4E; Thu, 16 Aug 2018 20:43:19 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7GKhHuf078910; Thu, 16 Aug 2018 20:43:17 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7GKhHpE078909; Thu, 16 Aug 2018 13:43:17 -0700 (PDT) (envelope-from david) Date: Thu, 16 Aug 2018 13:43:17 -0700 From: David Wolfskill To: Bryan Drewery Cc: Ian Lepore , Xin LI , Brad Davis , current@freebsd.org Subject: Re: /usr/bin/ld: error: undefined symbol: main [r337834 -> r337903] Message-ID: <20180816204317.GF1190@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Bryan Drewery , Ian Lepore , Xin LI , Brad Davis References: <20180816111532.GY1190@albert.catwhisker.org> <1534436769.312158.1476422048.77F4DB62@webmail.messagingengine.com> <1534446597.1466.42.camel@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="cGRd61phkNp4O6T3" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Aug 2018 20:43:20 -0000 --cGRd61phkNp4O6T3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 16, 2018 at 12:49:06PM -0700, Bryan Drewery wrote: > ... > r337928 should fix it. >=20 >=20 > --=20 > Regards, > Bryan Drewery >=20 Just tested after applying r337928 on top of sources at r337903; the rebuild after restoring crypto/openssh/moduli was successful: FreeBSD freebeast.catwhisker.org 12.0-ALPHA1 FreeBSD 12.0-ALPHA1 #285 r337= 903M/337903:1200078: Thu Aug 16 13:30:45 PDT 2018 root@freebeast.catwhi= sker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC amd64 Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --cGRd61phkNp4O6T3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt14eRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hf23wf/STj+PpKc10+TkB1AX/8Xzzay+ar0zo7K2F5OqCCGCdrE/8yozdNNDNtw gxFOIFOHM/cZNWWp6gua4dtNx7+g71aDRHkEYWYj39K2xcUo5QL2j0p2qUEwudGW Ervd4vZ69zJ2FIAgBNW14Mai2pcOUEoZDfr1VYh1DQKdYdoqek4Gi+hd1kLh/9y4 U/OQcNWCwp6CbMpJkzmv3sUcDDq2HbOrMvsJygfFB0f9LIFegETb3b5aJBxHVYf7 2Dbx8Js6uJ3Lknnh3W+oaSTt7X0Lds9xFZy2PHD4xaS6b5Ck/HPwf6W7AXEcaNrj ZcT1iRI1TD4cPmevKb4EooH7vTN+0A== =FACu -----END PGP SIGNATURE----- --cGRd61phkNp4O6T3-- From owner-freebsd-current@freebsd.org Fri Aug 17 06:17:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58BEF1083DDC for ; Fri, 17 Aug 2018 06:17:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.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 033D78E952 for ; Fri, 17 Aug 2018 06:17:43 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from John-Baldwins-MacBook-Pro-2.local (unknown [51.52.172.98]) by mail.baldwin.cx (Postfix) with ESMTPSA id 9039510AFCD; Fri, 17 Aug 2018 02:17:41 -0400 (EDT) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) To: Michael Gmelin , Konstantin Belousov References: <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> Cc: "freebsd-current@freebsd.org" , Matthias Apitz From: John Baldwin Message-ID: Date: Fri, 17 Aug 2018 07:17:40 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 17 Aug 2018 02:17:42 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 06:17:43 -0000 On 8/16/18 1:58 PM, Michael Gmelin wrote: > > > On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: > >> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>> >>> >>>> On 15. Aug 2018, at 15:04, Konstantin Belousov > wrote: >>>> >>>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >>>>> Reviving this old thread, since I just updated to r337818 and a similar >>>>> problem is happening again. Since the fix in r334799 (review >>>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, >>>>> so maybe this is related >>>>> (https://svnweb.freebsd.org/base?view=revision&revision=334799). >>>>> >>>>> Please see the screenshot of the panic below: >>>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>>>> >>>>> This is me not digging any deeper, hoping that this is something >>>>> obvious. Please let me know if you need more input. >>>> >>>> I do not see how recent mp_machdep.c changes could affect this. >>>> Can you try newest kernel but old loader ? >>> >>> I will try (but that will take a while). Oh, also, it still boots in save mode/with smp disabled. >> >> Right, this is because the access to that address through DMAP is only >> needed when configuring AP startup resources. >> >> Also, I think it is safe to suggest that the bisect is needed. > > Using an older loader didn’t help, but I identified the problem: > > https://svnweb.freebsd.org/base?view=revision&revision=334952 > > modified the code you introduced in > > https://svnweb.freebsd.org/base?view=revision&revision=334799 > > By correcting units to pages it also broke booting the Chromebook as a side effect - so the previous fix just worked due to a bug it seems. > > Is there an easy way to output the content of physmap at that point (debug.late_console=0 doesn’t work) - like an existing buffer I could use, or would this be more elaborate (I did something complicated last time but didn’t save it, so any simple solution would be preferred). How about reverting the commit for now so you get a working console and print out the physmap array values along with Maxmem later in the boot (or just use kgdb to examine them once the system is running)? -- John Baldwin From owner-freebsd-current@freebsd.org Fri Aug 17 08:54:53 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D9E710872B0 for ; Fri, 17 Aug 2018 08:54:53 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id C7C1473132 for ; Fri, 17 Aug 2018 08:54:52 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 25135 invoked by uid 89); 17 Aug 2018 08:54:51 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.231.99) by mail.grem.de with ESMTPA; 17 Aug 2018 08:54:51 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) From: Michael Gmelin X-Mailer: iPhone Mail (15G77) In-Reply-To: Date: Fri, 17 Aug 2018 10:54:49 +0200 Cc: Konstantin Belousov , "freebsd-current@freebsd.org" , Matthias Apitz Content-Transfer-Encoding: quoted-printable Message-Id: <07E28AC5-EBE6-4893-810A-6C03F07925C8@grem.de> References: <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> To: John Baldwin X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 08:54:53 -0000 > On 17. Aug 2018, at 08:17, John Baldwin wrote: >=20 >> On 8/16/18 1:58 PM, Michael Gmelin wrote: >>=20 >>=20 >>> On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: >>>=20 >>>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>>>=20 >>>>=20 >>>>>> On 15. Aug 2018, at 15:04, Konstantin Belousov > wrote: >>>>>>=20 >>>>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >>>>>> Reviving this old thread, since I just updated to r337818 and a simil= ar >>>>>> problem is happening again. Since the fix in r334799 (review >>>>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched,= >>>>>> so maybe this is related >>>>>> (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799). >>>>>>=20 >>>>>> Please see the screenshot of the panic below: >>>>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>>>>>=20 >>>>>> This is me not digging any deeper, hoping that this is something >>>>>> obvious. Please let me know if you need more input. >>>>>=20 >>>>> I do not see how recent mp_machdep.c changes could affect this. >>>>> Can you try newest kernel but old loader ? >>>>=20 >>>> I will try (but that will take a while). Oh, also, it still boots in sa= ve mode/with smp disabled. >>>=20 >>> Right, this is because the access to that address through DMAP is only >>> needed when configuring AP startup resources. >>>=20 >>> Also, I think it is safe to suggest that the bisect is needed. >>=20 >> Using an older loader didn=E2=80=99t help, but I identified the problem: >>=20 >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334952 >>=20 >> modified the code you introduced in >>=20 >> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799 >>=20 >> By correcting units to pages it also broke booting the Chromebook as a si= de effect - so the previous fix just worked due to a bug it seems. >>=20 >> Is there an easy way to output the content of physmap at that point (debu= g.late_console=3D0 doesn=E2=80=99t work) - like an existing buffer I could u= se, or would this be more elaborate (I did something complicated last time b= ut didn=E2=80=99t save it, so any simple solution would be preferred). >=20 > How about reverting the commit for now so you get a working console > and print out the physmap array values along with Maxmem later in > the boot (or just use kgdb to examine them once the system is running)? >=20 This is before the system has a working console (part of calling getmem...),= disabling late console makes it hang, physmap changes afterwards, so runnin= g kgdb later doesn=E2=80=99t help. Last time I kept a copy of physmap and lo= gged it later to know the original content. I can do that again, I just thou= ght maybe there is a simple mechanism I=E2=80=99m not aware of that would sa= ve me some time. Thanks, Michael From owner-freebsd-current@freebsd.org Fri Aug 17 09:02:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C6EDF108771A for ; Fri, 17 Aug 2018 09:02:11 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from mail.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 7057573604 for ; Fri, 17 Aug 2018 09:02:11 +0000 (UTC) (envelope-from jhb@FreeBSD.org) Received: from dhcp-10-248-98-203.eduroam.wireless.private.cam.ac.uk (global-5-141.nat-2.net.cam.ac.uk [131.111.5.141]) by mail.baldwin.cx (Postfix) with ESMTPSA id AF05010AFD2; Fri, 17 Aug 2018 05:02:09 -0400 (EDT) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) To: Michael Gmelin References: <20180603215020.452a81d8@bsd64.grem.de> <20180603205340.GS3789@kib.kiev.ua> <20180604004632.56ca6afa@bsd64.grem.de> <20180604110654.GA2450@kib.kiev.ua> <20180604231756.2ed2adb9@bsd64.grem.de> <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> <07E28AC5-EBE6-4893-810A-6C03F07925C8@grem.de> Cc: Konstantin Belousov , "freebsd-current@freebsd.org" , Matthias Apitz From: John Baldwin Message-ID: <8726bc32-6023-bfe1-7600-5b2c706236f8@FreeBSD.org> Date: Fri, 17 Aug 2018 10:02:08 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <07E28AC5-EBE6-4893-810A-6C03F07925C8@grem.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 17 Aug 2018 05:02:10 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 09:02:12 -0000 On 8/17/18 9:54 AM, Michael Gmelin wrote: > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: >> >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: >>> >>> >>>> On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: >>>> >>>>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>>>> >>>>> >>>>>>> On 15. Aug 2018, at 15:04, Konstantin Belousov > wrote: >>>>>>> >>>>>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >>>>>>> Reviving this old thread, since I just updated to r337818 and a similar >>>>>>> problem is happening again. Since the fix in r334799 (review >>>>>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, >>>>>>> so maybe this is related >>>>>>> (https://svnweb.freebsd.org/base?view=revision&revision=334799). >>>>>>> >>>>>>> Please see the screenshot of the panic below: >>>>>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>>>>>> >>>>>>> This is me not digging any deeper, hoping that this is something >>>>>>> obvious. Please let me know if you need more input. >>>>>> >>>>>> I do not see how recent mp_machdep.c changes could affect this. >>>>>> Can you try newest kernel but old loader ? >>>>> >>>>> I will try (but that will take a while). Oh, also, it still boots in save mode/with smp disabled. >>>> >>>> Right, this is because the access to that address through DMAP is only >>>> needed when configuring AP startup resources. >>>> >>>> Also, I think it is safe to suggest that the bisect is needed. >>> >>> Using an older loader didn’t help, but I identified the problem: >>> >>> https://svnweb.freebsd.org/base?view=revision&revision=334952 >>> >>> modified the code you introduced in >>> >>> https://svnweb.freebsd.org/base?view=revision&revision=334799 >>> >>> By correcting units to pages it also broke booting the Chromebook as a side effect - so the previous fix just worked due to a bug it seems. >>> >>> Is there an easy way to output the content of physmap at that point (debug.late_console=0 doesn’t work) - like an existing buffer I could use, or would this be more elaborate (I did something complicated last time but didn’t save it, so any simple solution would be preferred). >> >> How about reverting the commit for now so you get a working console >> and print out the physmap array values along with Maxmem later in >> the boot (or just use kgdb to examine them once the system is running)? >> > > This is before the system has a working console (part of calling getmem...), disabling late console makes it hang, physmap changes afterwards, so running kgdb later doesn’t help. Last time I kept a copy of physmap and logged it later to know the original content. I can do that again, I just thought maybe there is a simple mechanism I’m not aware of that would save me some time. I thought we only modified phys_avail[], but saving a copy of physmap[] and dumping it from kgdb is probably the simplest thing to do. -- John Baldwin From owner-freebsd-current@freebsd.org Fri Aug 17 10:13:19 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3687B1055046 for ; Fri, 17 Aug 2018 10:13:19 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8DD9F75B48; Fri, 17 Aug 2018 10:13:18 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w7HAD6cK043603 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 17 Aug 2018 13:13:09 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w7HAD6cK043603 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w7HAD66p043602; Fri, 17 Aug 2018 13:13:06 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 17 Aug 2018 13:13:06 +0300 From: Konstantin Belousov To: John Baldwin Cc: Michael Gmelin , "freebsd-current@freebsd.org" , Matthias Apitz Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) Message-ID: <20180817101306.GG2340@kib.kiev.ua> References: <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> <07E28AC5-EBE6-4893-810A-6C03F07925C8@grem.de> <8726bc32-6023-bfe1-7600-5b2c706236f8@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8726bc32-6023-bfe1-7600-5b2c706236f8@FreeBSD.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 10:13:19 -0000 On Fri, Aug 17, 2018 at 10:02:08AM +0100, John Baldwin wrote: > On 8/17/18 9:54 AM, Michael Gmelin wrote: > > > > > >> On 17. Aug 2018, at 08:17, John Baldwin wrote: > >> > >>> On 8/16/18 1:58 PM, Michael Gmelin wrote: > >>> > >>> > >>>> On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: > >>>> > >>>>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: > >>>>> > >>>>> > >>>>>>> On 15. Aug 2018, at 15:04, Konstantin Belousov > wrote: > >>>>>>> > >>>>>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: > >>>>>>> Reviving this old thread, since I just updated to r337818 and a similar > >>>>>>> problem is happening again. Since the fix in r334799 (review > >>>>>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touched, > >>>>>>> so maybe this is related > >>>>>>> (https://svnweb.freebsd.org/base?view=revision&revision=334799). > >>>>>>> > >>>>>>> Please see the screenshot of the panic below: > >>>>>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 > >>>>>>> > >>>>>>> This is me not digging any deeper, hoping that this is something > >>>>>>> obvious. Please let me know if you need more input. > >>>>>> > >>>>>> I do not see how recent mp_machdep.c changes could affect this. > >>>>>> Can you try newest kernel but old loader ? > >>>>> > >>>>> I will try (but that will take a while). Oh, also, it still boots in save mode/with smp disabled. > >>>> > >>>> Right, this is because the access to that address through DMAP is only > >>>> needed when configuring AP startup resources. > >>>> > >>>> Also, I think it is safe to suggest that the bisect is needed. > >>> > >>> Using an older loader didn???t help, but I identified the problem: > >>> > >>> https://svnweb.freebsd.org/base?view=revision&revision=334952 > >>> > >>> modified the code you introduced in > >>> > >>> https://svnweb.freebsd.org/base?view=revision&revision=334799 > >>> > >>> By correcting units to pages it also broke booting the Chromebook as a side effect - so the previous fix just worked due to a bug it seems. > >>> > >>> Is there an easy way to output the content of physmap at that point (debug.late_console=0 doesn???t work) - like an existing buffer I could use, or would this be more elaborate (I did something complicated last time but didn???t save it, so any simple solution would be preferred). > >> > >> How about reverting the commit for now so you get a working console > >> and print out the physmap array values along with Maxmem later in > >> the boot (or just use kgdb to examine them once the system is running)? > >> > > > > This is before the system has a working console (part of calling getmem...), disabling late console makes it hang, physmap changes afterwards, so running kgdb later doesn???t help. Last time I kept a copy of physmap and logged it later to know the original content. I can do that again, I just thought maybe there is a simple mechanism I???m not aware of that would save me some time. > > I thought we only modified phys_avail[], but saving a copy of physmap[] and > dumping it from kgdb is probably the simplest thing to do. UP boot works ? From owner-freebsd-current@freebsd.org Fri Aug 17 12:19:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 80B79106BC08 for ; Fri, 17 Aug 2018 12:19:56 +0000 (UTC) (envelope-from freebsd@grem.de) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id DAF4379CA7 for ; Fri, 17 Aug 2018 12:19:55 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 29296 invoked by uid 89); 17 Aug 2018 12:19:54 -0000 Received: from unknown (HELO ?192.168.250.192?) (mg@grem.de@46.244.231.99) by mail.grem.de with ESMTPA; 17 Aug 2018 12:19:54 -0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Fatal trap 12: page fault on Acer Chromebook 720 (peppy) From: Michael Gmelin X-Mailer: iPhone Mail (15G77) In-Reply-To: <20180817101306.GG2340@kib.kiev.ua> Date: Fri, 17 Aug 2018 14:19:52 +0200 Cc: John Baldwin , "freebsd-current@freebsd.org" , Matthias Apitz Content-Transfer-Encoding: quoted-printable Message-Id: <04B03A28-B894-46A6-B75D-C05B55234245@grem.de> References: <20180605131135.GH2450@kib.kiev.ua> <20180606010625.62632920@bsd64.grem.de> <20180815005106.69402d23@bsd64.grem.de> <20180815130447.GZ2340@kib.kiev.ua> <20180815135531.GA2340@kib.kiev.ua> <07E28AC5-EBE6-4893-810A-6C03F07925C8@grem.de> <8726bc32-6023-bfe1-7600-5b2c706236f8@FreeBSD.org> <20180817101306.GG2340@kib.kiev.ua> To: Konstantin Belousov X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 12:19:56 -0000 > On 17. Aug 2018, at 12:13, Konstantin Belousov wrote= : >=20 >> On Fri, Aug 17, 2018 at 10:02:08AM +0100, John Baldwin wrote: >>> On 8/17/18 9:54 AM, Michael Gmelin wrote: >>>=20 >>>=20 >>>>> On 17. Aug 2018, at 08:17, John Baldwin wrote: >>>>>=20 >>>>> On 8/16/18 1:58 PM, Michael Gmelin wrote: >>>>>=20 >>>>>=20 >>>>>>> On 15. Aug 2018, at 15:55, Konstantin Belousov > wrote: >>>>>>>=20 >>>>>>> On Wed, Aug 15, 2018 at 03:52:37PM +0200, Michael Gmelin wrote: >>>>>>>=20 >>>>>>>=20 >>>>>>>>> On 15. Aug 2018, at 15:04, Konstantin Belousov > wrote: >>>>>>>>>=20 >>>>>>>>> On Wed, Aug 15, 2018 at 12:51:06AM +0200, Michael Gmelin wrote: >>>>>>>>> Reviving this old thread, since I just updated to r337818 and a si= milar >>>>>>>>> problem is happening again. Since the fix in r334799 (review >>>>>>>>> https://reviews.freebsd.org/D15675) (mp_)machdep.c have been touch= ed, >>>>>>>>> so maybe this is related >>>>>>>>> (https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799= ). >>>>>>>>>=20 >>>>>>>>> Please see the screenshot of the panic below: >>>>>>>>> https://gist.github.com/grembo/78d0f2a100dd4f16775b85a118769658 >>>>>>>>>=20 >>>>>>>>> This is me not digging any deeper, hoping that this is something >>>>>>>>> obvious. Please let me know if you need more input. >>>>>>>>=20 >>>>>>>> I do not see how recent mp_machdep.c changes could affect this. >>>>>>>> Can you try newest kernel but old loader ? >>>>>>>=20 >>>>>>> I will try (but that will take a while). Oh, also, it still boots in= save mode/with smp disabled. >>>>>>=20 >>>>>> Right, this is because the access to that address through DMAP is onl= y >>>>>> needed when configuring AP startup resources. >>>>>>=20 >>>>>> Also, I think it is safe to suggest that the bisect is needed. >>>>>=20 >>>>> Using an older loader didn???t help, but I identified the problem: >>>>>=20 >>>>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334952 >>>>>=20 >>>>> modified the code you introduced in >>>>>=20 >>>>> https://svnweb.freebsd.org/base?view=3Drevision&revision=3D334799 >>>>>=20 >>>>> By correcting units to pages it also broke booting the Chromebook as a= side effect - so the previous fix just worked due to a bug it seems. >>>>>=20 >>>>> Is there an easy way to output the content of physmap at that point (d= ebug.late_console=3D0 doesn???t work) - like an existing buffer I could use,= or would this be more elaborate (I did something complicated last time but d= idn???t save it, so any simple solution would be preferred). >>>>=20 >>>> How about reverting the commit for now so you get a working console >>>> and print out the physmap array values along with Maxmem later in >>>> the boot (or just use kgdb to examine them once the system is running)?= >>>>=20 >>>=20 >>> This is before the system has a working console (part of calling getmem.= ..), disabling late console makes it hang, physmap changes afterwards, so ru= nning kgdb later doesn???t help. Last time I kept a copy of physmap and logg= ed it later to know the original content. I can do that again, I just though= t maybe there is a simple mechanism I???m not aware of that would save me so= me time. >>=20 >> I thought we only modified phys_avail[], but saving a copy of physmap[] a= nd >> dumping it from kgdb is probably the simplest thing to do. > UP boot works ? >=20 Well, I can boot if I remove atop(...) (reverting the patch). If this is wha= t you mean. From owner-freebsd-current@freebsd.org Fri Aug 17 12:49:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ACC8106CE31 for ; Fri, 17 Aug 2018 12:49:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from CAN01-TO1-obe.outbound.protection.outlook.com (mail-eopbgr670089.outbound.protection.outlook.com [40.107.67.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B05177B3F8 for ; Fri, 17 Aug 2018 12:49:04 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM (52.132.44.160) by YTOPR0101MB2060.CANPRD01.PROD.OUTLOOK.COM (52.132.49.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1038.23; Fri, 17 Aug 2018 12:49:03 +0000 Received: from YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127]) by YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM ([fe80::f171:1f28:a0a2:f127%3]) with mapi id 15.20.1059.021; Fri, 17 Aug 2018 12:49:03 +0000 From: Rick Macklem To: Konstantin Belousov CC: "freebsd-current@FreeBSD.org" , "peter@holm.cc" Subject: Re: ffs_truncate3 panics Thread-Topic: ffs_truncate3 panics Thread-Index: AQHULkj8zfSrFB+Dkkqu0NmeGvZbQKS0RKaAgAGEoXWAAKUlgIAANVYCgACitwCAAJvZIoABYIyAgAEw+G+AAA/YgIABir2AgAfkjyU= Date: Fri, 17 Aug 2018 12:49:03 +0000 Message-ID: References: <20180807131445.GC1884@kib.kiev.ua> <20180808221647.GH1884@kib.kiev.ua> <20180809111004.GK1884@kib.kiev.ua> <20180810172941.GA2113@kib.kiev.ua> , <20180811123755.GD2113@kib.kiev.ua>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=rmacklem@uoguelph.ca; x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; YTOPR0101MB2060; 6:2YwEV3Q97Q/wwYJ5Eq0zdsG5PQ0c8HFlMOA6ZgwLTN2qJfZ1iPV1bKz7Juy9fjyjRbu8x0RnLMaQY7uIS4Yp8VBb8P4WNTPIZNgPwYz3wKCYUSBhKJ0023B5mMu52vzrv6ulCIqmyAQO7h8gbDUjD1QCEBb4wJL+B4G0z1UxxVeKbBWWv/sIZj8QIZGNZHCK2QzHgo0INZPC3I25ajLatqpUTZC2k3T3M8kfAxJjAouhkmzHZa1uPh+AThRQLZRCtWHzYCb9CXl4+CF7zndhm4E4+aHR6PSqtzs3Nzilvo/d/fWTu8WCu5XfgJ5BuzSElD8Px1L1wJSRvhnWGOa3acPvw2FfY4JiAASUbj5vVg7ltML6lQnUW2c3PmuRH98UlYRv5mOmHokSWhnlv7plbc/kMikswYEJFPT6h5Urq88haFKMZnrDrTJEx9c/ZByJhXD8eEKhWDjlU6X4wMixiA==; 5:lY1v5MF0ti0YSSD0XB+w+Z/XbsUSBm3a51ep/ojM9ncPRAKqjy7oR8zB2D1FuzkA0Tm2j36n+XWLnKTlVHGRrlY0GW1kf49R6qAiVOAMSGDWBi2KdSd0d96QB0MuJ9KYrLTJ93cOqxHsyStvvCSvHdTPGMELBiCOJTtt15tj3Zk=; 7:Vh+Q4CGima6G/S76X7rEEN25YQalt3kKwwyDrAiHjFogqY14L3Y5gZL70vR70muPH/AfdqrS6Zp3ryTTEe+ng1Wx8gCvYRHOVrPd987/EQTB3aSVL3s6Z7Jo8fyq1ow99cKqahqslH+ZQGtDDqUEr8jtVdZjhzM3j/mgue4DZ9O2G/J93BmBCG8uc+c3lUyv5jNukPAy0zhsgiMHqI2a6bN7UkadI+BA6eioJDaH39BXf5TFxyS4JRNPRBEK7ABc x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 3958001d-236e-4570-7f21-08d6043fcf9c x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:YTOPR0101MB2060; x-ms-traffictypediagnostic: YTOPR0101MB2060: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231311)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(201708071742011)(7699016); SRVR:YTOPR0101MB2060; BCL:0; PCL:0; RULEID:; SRVR:YTOPR0101MB2060; x-forefront-prvs: 076777155F x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(39850400004)(136003)(366004)(346002)(396003)(189003)(199004)(40764003)(1411001)(786003)(68736007)(478600001)(6246003)(39060400002)(4326008)(256004)(53936002)(316002)(86362001)(54906003)(25786009)(14454004)(9686003)(2906002)(229853002)(5250100002)(6436002)(55016002)(7116003)(5660300001)(486006)(7696005)(76176011)(6916009)(476003)(446003)(11346002)(2900100001)(6506007)(26005)(186003)(102836004)(33656002)(105586002)(106356001)(99286004)(74482002)(81156014)(8676002)(81166006)(93886005)(8936002)(97736004)(305945005)(74316002); DIR:OUT; SFP:1101; SCL:1; SRVR:YTOPR0101MB2060; H:YTOPR0101MB1820.CANPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: uoguelph.ca does not designate permitted sender hosts) x-microsoft-antispam-message-info: ju9e/EAIErjhUMIfkyEMkxQlSrmQreP5IcPLhuCCDXomfchpXcKkWp9hNiov8Ca/eATr0HhZ9RVYxL9JZHeLxsgwjOiGUqGiVUvoCzqJxjyhc5VWJfCjb0zmSLIA6dP7h9pPVM47TH7uDq0CdB6nismOaiMkn5jSrM/ed0Mn1vlKZBUy1glFzyZjVZ5ng4/zoJS+MlWZNvAxKfy1Wisgu6BxPtONJwdoLOOi6GbPdtO4aqWIa67WcB/j/f9Gub+SrewjuKZICRMVqz6ALzz39ldatejPPHT8dSq3VG0MBt/pRUhMKpy1kjOg2ifd7OYBrHQkJBdhxzsa5punWvxHTgk5cyfSCePD811dWEJf9Tc= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: uoguelph.ca X-MS-Exchange-CrossTenant-Network-Message-Id: 3958001d-236e-4570-7f21-08d6043fcf9c X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Aug 2018 12:49:03.1474 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: be62a12b-2cad-49a1-a5fa-85f4f3156a7d X-MS-Exchange-Transport-CrossTenantHeadersStamped: YTOPR0101MB2060 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 12:49:05 -0000 Just fyi, I have committed r337962 to head, which stops the pNFS service from creating non-zero length empty files. Since these files were the ones causing the "ffs_truncate3" panics, the pan= ics should no longer occur. I will take a closer look at some point to see if I can spot why the panics= () occur and can easily revert this patch on my test setup if others have suggested patches to try related to this. Thanks for your help with this, rick From owner-freebsd-current@freebsd.org Fri Aug 17 13:02:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 49FA4106D465 for ; Fri, 17 Aug 2018 13:02:59 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) (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 D6E847BD13 for ; Fri, 17 Aug 2018 13:02:58 +0000 (UTC) (envelope-from Mark.Martinec+freebsd@ijs.si) Received: from amavis-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 41sNfS58dCz78h for ; Fri, 17 Aug 2018 15:02:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= user-agent:message-id:organization:subject:subject:from:from :date:date:content-transfer-encoding:content-type:content-type :mime-version:received:received:received:received; s=jakla4; t= 1534510966; x=1537102967; bh=H+CzHQRL7fuD7vdLbwm9mPv5sXsKM1GuHxk /ls4zTGk=; b=bq6UR3Ayt4mO0dBEMbqYlTaNmuZGYWflc6qa/vakhahoxGetZ0e UTMwfPUcClwkjz1YILBl7drbqx/dRQgCCFq/uFPvMMu5iMH5Ql5+8rQ2lfcbccxf HzD2XpnRbloo8RTub+R7NCTo+KQtQnUw7DMfcpIgg6O4RJVRSI74viNU= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10026) with LMTP id OSSqiLZ7Gpcr for ; Fri, 17 Aug 2018 15:02:46 +0200 (CEST) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP id 41sNfG1gK0z78W for ; Fri, 17 Aug 2018 15:02:45 +0200 (CEST) Received: from nabiralnik.ijs.si (nabiralnik.ijs.si [IPv6:2001:1470:ff80::80:16]) by mildred.ijs.si (Postfix) with ESMTP id 41sNfF6j7gznG for ; Fri, 17 Aug 2018 15:02:45 +0200 (CEST) Received: from neli.ijs.si (2001:1470:ff80:88:21c:c0ff:feb1:8c91) by nabiralnik.ijs.si with HTTP (HTTP/1.1 POST); Fri, 17 Aug 2018 15:02:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 17 Aug 2018 15:02:45 +0200 From: Mark Martinec To: freebsd-current@freebsd.org Subject: Reminder - [Bug 213276] port 502 is officially mbap (Modbus Application Protocol), /etc/services claims outdated asa-appl-proto Organization: Jozef Stefan Institute Message-ID: X-Sender: Mark.Martinec+freebsd@ijs.si User-Agent: Roundcube Webmail/1.3.1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 13:02:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213276 Any chance of getting this simple fix of /etc/services into CURRENT before it's too late for 12.0 ... From owner-freebsd-current@freebsd.org Fri Aug 17 21:50:28 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 09B23107CA8B for ; Fri, 17 Aug 2018 21:50:28 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81B60746FE; Fri, 17 Aug 2018 21:50:27 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id d70-v6so2653154ith.1; Fri, 17 Aug 2018 14:50:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=sNrJxuZe8X/N/3BRcLJn0SoMeh5DpP6newlesZV+xT4=; b=tPnkumgNoKaC/S3PQmdCbSTybD6g+d4sskP7N9eOp/uGslyzUmnNqWInayv6N3w/cY bOPSPnxjaolTOzx6iBpJMujPdrkCM0hXc1zch1speBgV7GQ4kSoS0vPICDms144A5CGJ bNHPgMTVwIL9/QeVdGi2igS0ojNVUiJO55DzNPWqwP+wbdMoq+1g1lyDeZni+gSsO5P6 8VNr4eLP0KmRXAUEMeuBrPzB2SESZvcSATAaRR+PaRN6CicFSS35Z0fdjNwcDO/O0/DQ Jibgn7suOdfjlO4J4JhZ96cuniJotRYjTGDdL9yoqayJd7x6fSdTslXbbgy47a7ASNli LwBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=sNrJxuZe8X/N/3BRcLJn0SoMeh5DpP6newlesZV+xT4=; b=EqHL2JmabgpRP4+kLPLblcSAWm+eg+B4shdMEvvr8Vyzcw3ylSuSuhYluAzfTZ1w/F bR9CBsukAwV5O5QJI7nHETGv5AReIrDAEwG7+9ZooLkWsy6AcEEelpp4xvpGHh6NBFPY fh2fc0MhV0UsSfjIqMfgipt81QpGZXWNMS0g54lVavXTcuARWGAqCTXJs59dEMLUjs7m //WMPagksoukN6K7msblKS9ycXTlV6PCh7otoJMvMYqnvps53HU7D15vTgc42cwrAqRr B6ES2fmppQKi+GJUEOQZMnCoZci0DpnIypOQZvMsj3fdaw/Kk60SyFtmlGdeMH0jaBkn VIxQ== X-Gm-Message-State: AOUpUlH2PpJGVC8mY0EOrKdJ1UByt3+Lvt5xbUkz3tTGreoNk75rOTIk INQ+q1mtmxgZZDIIfskU6lWpduoCzti71HXSTJuiag== X-Google-Smtp-Source: AA+uWPzNBiVrp27mDl9S3O1Ss8+a2o1jTmisGY3wct7rPd4j6VgL0lHI7opROsGsYvgPJPSlGWhr19Nh2FnFS8WfHow= X-Received: by 2002:a24:3d81:: with SMTP id n123-v6mr5602659itn.40.1534542627032; Fri, 17 Aug 2018 14:50:27 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:4a08:0:0:0:0:0 with HTTP; Fri, 17 Aug 2018 14:50:06 -0700 (PDT) In-Reply-To: References: <20180808165819.GA87623@troutmask.apl.washington.edu> <20180808171936.GA87930@troutmask.apl.washington.edu> From: Ed Maste Date: Fri, 17 Aug 2018 17:50:06 -0400 X-Google-Sender-Auth: H4-Q75J00ODnXB0jbLWDRZxYccw Message-ID: Subject: Re: kldref: unhandled relocation type 2 To: Warner Losh Cc: Steve Kargl , Dimitry Andric , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 21:50:28 -0000 On 8 August 2018 at 13:27, Warner Losh wrote: > >> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel >> kldxref: unhandled relocation type 2 >> (40+ messages...) > > > Oh, wait: relocation type, not module info.... That's not me, that's ed and > the new linker I think, or Dimitry and the new clang... 2 is R_386_PC32. It looks like the kernel's relocation code handles this, but not kldxref. I hope to be able to look at it soon. From owner-freebsd-current@freebsd.org Fri Aug 17 23:11:31 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B69CC107E20B for ; Fri, 17 Aug 2018 23:11:31 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3779376B43; Fri, 17 Aug 2018 23:11:31 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w7HMoCJ0092995 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 17 Aug 2018 15:50:12 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w7HMoCMB092994; Fri, 17 Aug 2018 15:50:12 -0700 (PDT) (envelope-from sgk) Date: Fri, 17 Aug 2018 15:50:12 -0700 From: Steve Kargl To: Ed Maste Cc: Warner Losh , Dimitry Andric , FreeBSD Current Subject: Re: kldref: unhandled relocation type 2 Message-ID: <20180817225012.GA92976@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180808165819.GA87623@troutmask.apl.washington.edu> <20180808171936.GA87930@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Aug 2018 23:11:31 -0000 On Fri, Aug 17, 2018 at 05:50:06PM -0400, Ed Maste wrote: > On 8 August 2018 at 13:27, Warner Losh wrote: > > > >> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel > >> kldxref: unhandled relocation type 2 > >> (40+ messages...) > > > > > > Oh, wait: relocation type, not module info.... That's not me, that's ed and > > the new linker I think, or Dimitry and the new clang... > > 2 is R_386_PC32. It looks like the kernel's relocation code handles > this, but not kldxref. I hope to be able to look at it soon. Thanks, Ed. If you need any other information, just ask. -- Steve From owner-freebsd-current@freebsd.org Sat Aug 18 08:23:33 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 834BB1089170 for ; Sat, 18 Aug 2018 08:23:33 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 044EE872EF; Sat, 18 Aug 2018 08:23:32 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 848A439D89; Sat, 18 Aug 2018 10:23:31 +0200 (CEST) From: Dimitry Andric Message-Id: Content-Type: multipart/signed; boundary="Apple-Mail=_760CC6BA-0C07-452E-B6F7-4B069B48BB2F"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: kldref: unhandled relocation type 2 Date: Sat, 18 Aug 2018 10:23:27 +0200 In-Reply-To: <20180817225012.GA92976@troutmask.apl.washington.edu> Cc: Ed Maste , Warner Losh , FreeBSD Current To: sgk@troutmask.apl.washington.edu References: <20180808165819.GA87623@troutmask.apl.washington.edu> <20180808171936.GA87930@troutmask.apl.washington.edu> <20180817225012.GA92976@troutmask.apl.washington.edu> X-Mailer: Apple Mail (2.3445.9.1) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 08:23:33 -0000 --Apple-Mail=_760CC6BA-0C07-452E-B6F7-4B069B48BB2F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 18 Aug 2018, at 00:50, Steve Kargl = wrote: >=20 > On Fri, Aug 17, 2018 at 05:50:06PM -0400, Ed Maste wrote: >> On 8 August 2018 at 13:27, Warner Losh wrote: >>>=20 >>>> % /usr/obj/usr/src/i386.i386/usr.sbin/kldxref/kldxref /boot/kernel >>>> kldxref: unhandled relocation type 2 >>>> (40+ messages...) >>>=20 >>>=20 >>> Oh, wait: relocation type, not module info.... That's not me, that's = ed and >>> the new linker I think, or Dimitry and the new clang... >>=20 >> 2 is R_386_PC32. It looks like the kernel's relocation code handles >> this, but not kldxref. I hope to be able to look at it soon. >=20 > Thanks, Ed. If you need any other information, just ask. This rabbit hole is a bit deeper though. Almost all .ko files in /boot/kernel contain R_386_PC32 relocations: $ for i in /boot/kernel/*.ko; do readelf -r $i | grep -q R_386_PC32 && = echo $i; done | wc -l 861 But kldxref *only* complains specifically about if_bge.ko, and it is not clear to me why. Maybe the R_386_PC32 relocations are first preprocessed away, somehow, before they end up in kldxref's ef_reloc(), where the "unhandled relocation type" warning is produced? In any case, I tried the following patch, which at least makes the warning go away, but might not be the right solution: Index: usr.sbin/kldxref/ef_i386.c =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- usr.sbin/kldxref/ef_i386.c (revision 337959) +++ usr.sbin/kldxref/ef_i386.c (working copy) @@ -82,11 +82,17 @@ ef_reloc(struct elf_file *ef, const void *reldata, addr =3D (Elf_Addr)addend + relbase; *where =3D addr; break; - case R_386_32: /* S + A - P */ + case R_386_32: /* S + A */ addr =3D EF_SYMADDR(ef, symidx); addr +=3D addend; *where =3D addr; break; + case R_386_PC32: /* S + A - P */ + addr =3D EF_SYMADDR(ef, symidx); + addr +=3D addend; + addr -=3D (Elf_Addr)where; + *where =3D addr; + break; case R_386_GLOB_DAT: /* S */ addr =3D EF_SYMADDR(ef, symidx); *where =3D addr; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D While here, I corrected the comment for R_386_32 relocations. At least, all the documentation I could find states that such relocations only add the addend to the symbol, and the actual code also does that. -Dimitry --Apple-Mail=_760CC6BA-0C07-452E-B6F7-4B069B48BB2F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.2 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCW3fXfwAKCRCwXqMKLiCW oyigAJwIrcLp60pZvbYwbaxsL22a9KcNvQCgvF1GP4UBLaQz1ehbpFNWAZFLwKQ= =wBDN -----END PGP SIGNATURE----- --Apple-Mail=_760CC6BA-0C07-452E-B6F7-4B069B48BB2F-- From owner-freebsd-current@freebsd.org Sat Aug 18 10:05:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 706B4108B901 for ; Sat, 18 Aug 2018 10:05:06 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-wr1-f46.google.com (mail-wr1-f46.google.com [209.85.221.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E04938BC71 for ; Sat, 18 Aug 2018 10:05:05 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-wr1-f46.google.com with SMTP id w11-v6so6455003wrc.5 for ; Sat, 18 Aug 2018 03:05:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=+k3zF5zqFbzuG9YLLcbE7RVKGrPhKL+5DJ2RoseoG3Q=; b=eEsf3xI2xx7pRWaAGLe2LSnwBPnaetK2Fvi9ESWYqhq+Yj+yRSxOhtHRskmWsYrBOJ srFZDn4BMF2B5uNwIWcaflw25bZfPfy0JMsZzLnSRIsi/k6lhCnkRxqYx/v1/ZW8WjTR EdVoxRoSHnEk4Mr9dljd8o0PCgHfUp6kmwHkPcXbaQseTI3AXjOppaPltIA2KIcQLgJX bAUOAd7S6U8Rcna8vntSKLoeUxap317jJQ5ryuWhaxxL53zlZLL6Q2J2ubORRM2Qkeki GFfEhh4zmDyYoN3NptdJtbb6bxNtPCyLNmxWiBGlFNqWmOZZCQBUF1X/rsHLpBoRZqAB jQHA== X-Gm-Message-State: AOUpUlHRzBN60Vppk4j9Qs9gRrDO+qhwEd83DI54c90Ue1JCSGsP40yZ juP1Tk15yjkNijYHTJLsGg0= X-Google-Smtp-Source: AA+uWPzf7/v+hwvJR/yxfa1YaDFc63U/B2yfNw65bkYzYnqJJQh6eV6t0ex6xZlq06qAWWIjoeyiEQ== X-Received: by 2002:adf:ba12:: with SMTP id o18-v6mr24016879wrg.249.1534586698654; Sat, 18 Aug 2018 03:04:58 -0700 (PDT) Received: from e5500 (global-5-184.nat-2.net.cam.ac.uk. [131.111.5.184]) by smtp.gmail.com with ESMTPSA id 200-v6sm11263251wmv.6.2018.08.18.03.04.58 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 18 Aug 2018 03:04:58 -0700 (PDT) Date: Sat, 18 Aug 2018 11:04:54 +0100 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Samy Mahmoudi Cc: freebsd-current@freebsd.org Subject: Re: awk manual is outdated Message-ID: <20180818110454.339e9929@e5500> In-Reply-To: References: X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; i386-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 10:05:06 -0000 On Tue, 24 Jul 2018 01:06:19 +0200 Samy Mahmoudi wrote: >The awk manual seems out of date. > >For example, the -V option is documented but is unknown at execution. >Reciprocally, --version is not documented but is functional at execution. >Under FreeBSD 12.0-CURRENT, the date at the end of the manual also seems >older than expected, as the FreeBSD Manual Pages indicates a newer date for >FreeBSD 11.2. > >I could edit awk.1 and copy/paste a patch to solve these but reviewing the >whole manual may be better to eradicate other omissions. From the FreeBSD >Manual Pages, I have found out that options (including -V) were introduced >between 11.0 RELEASE and 11.1 RELEASE. > >By the way, choosing the "FreeBSD 12-current" manual on that web page > >actually gives the "FreeBSD 11.2" manual, seemingly. I've created an issue on Bugzilla for this. Thanks for the heads up. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230730 From owner-freebsd-current@freebsd.org Sat Aug 18 13:19:05 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AD9F2106CC4F for ; Sat, 18 Aug 2018 13:19:05 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from smtp.digiware.nl (smtp.digiware.nl [176.74.240.9]) (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 4CC2D9195C for ; Sat, 18 Aug 2018 13:19:05 +0000 (UTC) (envelope-from wjw@digiware.nl) Received: from router.digiware.nl (localhost.digiware.nl [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 4C84978CCC; Sat, 18 Aug 2018 15:18:58 +0200 (CEST) X-Virus-Scanned: amavisd-new at digiware.com Received: from smtp.digiware.nl ([127.0.0.1]) by router.digiware.nl (router.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X8M7_Gd7RG0w; Sat, 18 Aug 2018 15:18:57 +0200 (CEST) Received: from [192.168.11.152] (unknown [192.168.11.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 877FE78CCB for ; Sat, 18 Aug 2018 15:18:57 +0200 (CEST) Subject: Fwd: Warnings about dlclose before thread exit. __cxa_thread_call_dtors References: <4b231ed8-f853-fb7e-06a7-b1bd57028ced@digiware.nl> To: freebsd current From: Willem Jan Withagen X-Forwarded-Message-Id: <4b231ed8-f853-fb7e-06a7-b1bd57028ced@digiware.nl> Message-ID: <6a57c77d-944d-166b-07a3-263aac8fe297@digiware.nl> Date: Sat, 18 Aug 2018 15:18:56 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <4b231ed8-f853-fb7e-06a7-b1bd57028ced@digiware.nl> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 13:19:05 -0000 Hi, I've sent the question below to the Ceph-devel list, asking if any recent changes would be able to cause this. But then of course this could stem from FreeBSD libs, and of ports.... So the question here is if anybody has gotten these "warnings" in other tools. --WjW -------- Forwarded Message -------- Subject: Warnings about dlclose before thread exit Date: Sat, 18 Aug 2018 14:46:35 +0200 From: Willem Jan Withagen To: Ceph Development Hi, I've have upgraded to FreeBSD ALPHA 12.0, but I don't think the errors them from there. Although they could be in one of the libs that came along with the upgrade. I'm getting these warnings during rbd and ceph (maybe even more) invocations that indicate that indicate a possible problem because: === It could be possible that a dynamically loaded library, use thread_local variable but is dlclose()'d before thread exit. The destructor of this variable will then try to access the address, for calling it but it's unloaded, so it'll crash. We're using __elf_phdr_match_addr() to detect and prevent such cases and so prevent the crash. === this is from : https://github.com/freebsd/freebsd/blob/master/lib/libc/stdlib/cxa_thread_atexit_impl.c Now it could be that dlclose() and thread exit are just closed to one another. But still this is hard core embedded in libc already since 2017, so I'm sort of expecting that a recent change has caused this. And as indicated it is a possible cause for crashed, because thread_exit is going to clean up things that are no longer there. Now the 20 dollar question is: Where was this introduced?? Otherwise I'll have to try and throw my best gdb capabilities at it, and try to invoke an rbd call and see where it activates this warning. --WjW From owner-freebsd-current@freebsd.org Sat Aug 18 13:26:06 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C3D7B106D0EE; Sat, 18 Aug 2018 13:26:05 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53E7491EAA; Sat, 18 Aug 2018 13:26:05 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id s7-v6so14985238itb.4; Sat, 18 Aug 2018 06:26:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=/TadZbk+C82NXSbF2uIJldlDDf7OredmFiuLczT6UNA=; b=WpzTDtFpWdKeZ6w+/iSBsNpMkaDATG1/7k/uHGfXo3eqgVlYEps/zzZri0+Swk9VeF pRQc0if7g9ga6TAXf/dvnj7ZiLjBKsg1Et7ENciCDQ1UHyEH20kMjrJK7ZDBdQQ50Emq Iqc3B4dHGnLvRNeHSSTjvB40kprjYlzvoAMAttQ2Fe4vSs/Np4UHWCCBoRdioUuroRjL yiXRXN4i7fbA+/57FrKorJ7psUoceYThq8Td6JwyVPaYn853+F3W37qDRU4GtXWoiCca QHSJW5YzZquH22r8ZNIf6vFN/5tDBsIS7CG2apgqHczCfMHcHso85rf6HxFN1vi6Qxt8 OGcw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=/TadZbk+C82NXSbF2uIJldlDDf7OredmFiuLczT6UNA=; b=Y8fkQvwQYXVYEtHX4rw9QlljD7kSOF5BO6Xkf7SLmCpnGaI/lVcbbCw/qThHmMkM2x WTkuak0JYb4ZW6q8FRSFhQPFy8vcZj0LhsXdPVYMKYXMrVhgoUcOrSCPbJXVr3xalIut uiSguydVSdGgH2yuGDshXtywsQIkkX/e9RGAQN8XXTDGOaD5ozMt4uO8o9a1UvsM2CSF vLbxrqrE9BQM1Iw4AGNOHgjGcvR4EL6W8Cauet3XRHoWhCYdVK+9VtMyQ6DavhdC1EOP cktebHTaDj284KC99wWK0hV1t8suubqRxGHxm9+eddoCpW/CMyN1CWDENRQDbzMCmQqm ct1w== X-Gm-Message-State: AOUpUlGZXL0VpzCSW7bEKyCUkBCUyqb+JT+zVxT1IoyaQfW8TwEaJQlY /Uq7Vcp0Xf6nVL4Ng4odROCHk1LQxwp7lxogu/YloQJN X-Google-Smtp-Source: AA+uWPxVUKw5i+09nm+XeY1EEObmn6nM5qxDncHYTDEy+cXjEvd3dsJhFLlmd6pNEvUqtZ07PxLBAweHZ1k6oTqs9CM= X-Received: by 2002:a24:7c4a:: with SMTP id a71-v6mr21105375itd.69.1534598764492; Sat, 18 Aug 2018 06:26:04 -0700 (PDT) MIME-Version: 1.0 From: blubee blubeeme Date: Sat, 18 Aug 2018 21:25:53 +0800 Message-ID: Subject: Executables with [ -def __linux__ ] To: FreeBSD current , FreeBSD Ports Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 13:26:06 -0000 This is going out to both current and ports in hopes someone can offer some guidance on this issue. I'm porting some code that seems to want to have -def __linux__ when I run the executable with verbose output, take a look below -------------------------------------------------------------- -opt 0 -terse 1 -inform warn -nohpf -nostatic -inform warn -x 19 0x400000 -quad -x 68 0x1 -x 59 4 -x 15 2 -x 49 0x400004 -x 51 0x20 -x 57 0x4c -x 58 0x10000 -x 124 0x1000 -tp px -x 57 0xfb0000 -x 58 0x78031040 -x 47 0x08 -x 48 4608 -x 49 0x100 -def unix -def __unix -def __unix__ -def linux -def __linux -def __linux__ -def __NO_MATH_INLINES -def __LP64__ -def __x86_64 -def __x86_64__ -def __LONG_MAX__=9223372036854775807L -def __SIZE_TYPE__=unsigned long int -def __PTRDIFF_TYPE__=long int -def __THROW= -def __extension__= -def __amd_64__amd64__ -def __k8 -def __k8__ -def __PGLLVM__ -freeform -vect 48 -y 54 1 -x 70 0x40000000 -y 163 0xc0000000 -x 189 0x10 -stbfile test-276576.stb -modexport test-276576.cmod -modindex test-276576.cmdx -output test-276576.ilm ---------------------------------------------------------------- As you can see from above there's some -def linux, def __linux, etc.. FreeBSD isn't Linux and I'd like to better understand where these things are being set, it's a cmake project and I've grepped through a lot of the sources and can't really find where these flags are coming from. Any tips on finding where they are coming from and fixing them to reflect the correct platform information? Best, Owen From owner-freebsd-current@freebsd.org Sat Aug 18 22:34:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 427D71077DB3 for ; Sat, 18 Aug 2018 22:34:32 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (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 BAE137A343 for ; Sat, 18 Aug 2018 22:34:30 +0000 (UTC) (envelope-from mail@dbalan.in) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 96BF2429 for ; Sat, 18 Aug 2018 18:34:23 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sat, 18 Aug 2018 18:34:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dbalan.in; h= content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=Wp52v/fbBw2W90vWK JUKmLpVw6prkItS6y2kQPf+vhU=; b=1PfvOw8PT+h/xHmKg/6GevyJUGRnR3rex ihi9fb4nQ1qYTU/Tt5i8fatHsbkKuI8vbOLbq5/xFl1q+YQbtZuydFpbj9Vf7B8v hAjDDj8gSZZ9Uk0YkIBON4tuPsODVweVFbiMAxEdYFMGfuDFj1+2SnPasK/4hQqK yVmMe2IiM4GeF1Ig3koEdDoBO3sAOuDPGfbdu9esgsarJdMbE2qOtu/4R+Ko61kV auSYkktcc/wA8NirtKIx1dgIKXANjwX+jgEMIBsyZJvZaxEEtKVrxXEWjGqMN7qh hTSHxJl3RaLJsnZltwaEHyvqKAuh4ypE4CNqUKvlk+mNg0A14yPVQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=Wp52v/fbBw2W90vWKJUKmLpVw6prkItS6y2kQPf+vhU=; b=na9KADoH 6XZWEzcYJ6+DXJ/MeuVcZ6OWeSltloWZwKDemysnn9FcTfB6isZpoa2XA+yub/YC AABmWceBXA+CB3z5YxYXNLVmiE2GB8Vct0doWSffMiJHj0ak4by/FX/C9xoBKmU6 /r5fO7YLk9vDzbLm2SMGB0kVoreipvwiAF3/+Z3L/x0p/bZeFWzBgDe0n3RCVVcd mpbRc3p7QEodbF34zYSTkvjBRfQ2QZzFPh0bQOBawYereToZZx8hFmJzSrWlJqFa GTcjCacg2PpXgVNwnWDhjOjqubWMe4173YkHApiAVryqtR3RPfBNvZiJg34rA/BH lgE1QBG+dB/eLg== X-ME-Proxy: X-ME-Sender: Received: from localhost (p5b071082.dip0.t-ipconnect.de [91.7.16.130]) by mail.messagingengine.com (Postfix) with ESMTPA id 3888110286 for ; Sat, 18 Aug 2018 18:34:22 -0400 (EDT) Date: Sun, 19 Aug 2018 00:34:20 +0200 From: Dhananjay Balan To: freebsd-current@freebsd.org Subject: Sharing compiled builds between multiple 12-CURRENT boxes. Message-ID: <20180818223420.rjisst4vuxzxbcrl@kazhap> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 22:34:32 -0000 Hi, I run 12-CURRENT on few machines, some more powerful that other (all of them x86_64, march varies). Is there is a way to avoid building CURRENT on all machines? Rather than building everywhere, can I just build it on the big server that I have and copy and update my laptop? - Dhananjay Balan From owner-freebsd-current@freebsd.org Sat Aug 18 23:36:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 924981079077 for ; Sat, 18 Aug 2018 23:36:22 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 10F067BD86 for ; Sat, 18 Aug 2018 23:36:21 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from spqr.komquats.com ([70.67.125.17]) by shaw.ca with ESMTPA id rAlQfhCPsWppDrAlRfN8XY; Sat, 18 Aug 2018 17:36:14 -0600 X-Authority-Analysis: v=2.3 cv=YIcrNiOx c=1 sm=1 tr=0 a=VFtTW3WuZNDh6VkGe7fA3g==:117 a=VFtTW3WuZNDh6VkGe7fA3g==:17 a=kj9zAlcOel0A:10 a=dapMudl6Dx4A:10 a=YxBL1-UpAAAA:8 a=6I5d2MoRAAAA:8 a=SVtz_uFXmA0QvfbJkhoA:9 a=CjuIK1q_8ugA:10 a=Ia-lj3WSrqcvXOmTRaiG:22 a=IjZwj45LgO3ly-622nXo:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTPS id 8EFBEC0; Sat, 18 Aug 2018 16:36:42 -0700 (PDT) Received: from slippy.cwsent.com (localhost [127.0.0.1]) by slippy.cwsent.com (8.15.2/8.15.2) with ESMTP id w7INaGdW088309; Sat, 18 Aug 2018 16:36:16 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Received: from slippy (cy@localhost) by slippy.cwsent.com (8.15.2/8.15.2/Submit) with ESMTP id w7INaF5J088304; Sat, 18 Aug 2018 16:36:16 -0700 (PDT) (envelope-from Cy.Schubert@cschubert.com) Message-Id: <201808182336.w7INaF5J088304@slippy.cwsent.com> X-Authentication-Warning: slippy.cwsent.com: cy owned process doing -bs X-Mailer: exmh version 2.8.0 04/21/2012 with nmh-1.7.1 Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Dhananjay Balan cc: freebsd-current@freebsd.org Subject: Re: Sharing compiled builds between multiple 12-CURRENT boxes. In-Reply-To: Message from Dhananjay Balan of "Sun, 19 Aug 2018 00:34:20 +0200." <20180818223420.rjisst4vuxzxbcrl@kazhap> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Aug 2018 16:36:15 -0700 X-CMAE-Envelope: MS4wfEyf7xcMnmqau8PW1SrIWMDyrKrxzuaM8/hdqojltzfnj+HFWot6WiyZo037JCttYG6Q1t3XBWEqVa4sfRxuZ8cEWchVqNgl9m6omL0AAwcEApHgHEcz IENR54ypOV2mpfT76qycrSikr6ol4J9mOxF4sxhsjQeIV0S/WlCOwEzkLV+n/QIQE5dTcf8EqRfOMmIAX/qaOQg/5mjfl1VQ5BbnuuYeCy1lf89CfSU8Q1wh X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 23:36:22 -0000 In message <20180818223420.rjisst4vuxzxbcrl@kazhap>, Dhananjay Balan writes: > Hi, > > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies). > > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I just build it on the big server that I > have and copy and update my laptop? You can use NFS or rsync. Make sure the src and obj path names are exactly the same on all thes servers. I used to use NFS until a year or two ago when I started using different patches on different machines. On occasion I've used rsync followed by a NO_CLEAN, WORLDFAST, KERNFAST build on the target machine or simply installkernel and installworld. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. From owner-freebsd-current@freebsd.org Sat Aug 18 23:59:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EC7B510797AA for ; Sat, 18 Aug 2018 23:59:39 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (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 34A937C5EE for ; Sat, 18 Aug 2018 23:59:38 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w7INxPZs016525; Sat, 18 Aug 2018 23:59:25 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w7INxPT5016524; Sat, 18 Aug 2018 16:59:25 -0700 (PDT) (envelope-from david) Date: Sat, 18 Aug 2018 16:59:25 -0700 From: David Wolfskill To: Dhananjay Balan Cc: freebsd-current@freebsd.org Subject: Re: Sharing compiled builds between multiple 12-CURRENT boxes. Message-ID: <20180818235925.GR1190@albert.catwhisker.org> Reply-To: current@freebsd.org Mail-Followup-To: current@freebsd.org, Dhananjay Balan , freebsd-current@freebsd.org References: <20180818223420.rjisst4vuxzxbcrl@kazhap> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="36AFPy6HsFnek/nA" Content-Disposition: inline In-Reply-To: <20180818223420.rjisst4vuxzxbcrl@kazhap> User-Agent: Mutt/1.10.1 (2018-07-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2018 23:59:40 -0000 --36AFPy6HsFnek/nA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Aug 19, 2018 at 12:34:20AM +0200, Dhananjay Balan wrote: > Hi, >=20 > I run 12-CURRENT on few machines, some more powerful that other (all > of them x86_64, march varies).=20 >=20 > Is there is a way to avoid building CURRENT on all machines? Rather > than building everywhere, can I just build it on the big server that I > have and copy and update my laptop? > .... There are ways (note plural) to do this kind of thing, yes. Depending on a lot of factors, some may be more feasible than others. While the machines for which I do something similar run stable (at present, stable/11), I believe that the approach I use, and which is described at may (at least) be a useful case study. There is also a log (of sorts) of the successful updates at . Note that I explicitly avoid optimizations that would not work for all of the machines in question. That's probably obvious, but.... :-) As Cy Schubert pointed out, paths need to be set up to look identical; setting that up initially may be a little more "interesting" than one might prefer, but in my experience, once that's done, things Just Work (at least, using the approach I use). I'll skip trying to mention other approaches, as I don't actually use them. Peace, david --=20 David H. Wolfskill david@catwhisker.org Trump is gaslighting us: https://www.bbc.com/news/world-us-canada-44959300 See http://www.catwhisker.org/~david/publickey.gpg for my public key. --36AFPy6HsFnek/nA Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlt4stxfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hc2lggAzuycMjuY1mg/+IGnMIA5j8V97vPxcpif8dUmITwfBsiwC8dZGo5Zjvcr sAVWIj08EdfRJcdhF3InbKbrYxSQoJw27dWQX4lG/2ytShC8+gaGE6LibZdzTf0Y A0RNiuG+KkCTYzDzrJIn/qvrlZtHSHiDw2shRO6uFrxUiKcTtOXIyvBkgcL2Brg0 M/32s54S/WCtC/uR8haaXzaAEc7tRVYJy7+PQ4Y3QVjhqMkx+syyIzDPC+/uB3RH pX0MfA4/F2cwQnXCuDjYkeGLuIwVOpz3otuRrQbu0ch+rt8zjzCNSknh+qWbp//y NqGcAC0WagBvXma6Z9tnSYi5VR5Y3w== =qUYb -----END PGP SIGNATURE----- --36AFPy6HsFnek/nA--