From owner-freebsd-current@freebsd.org Sun May 27 02:31: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 B43F7F749A1 for ; Sun, 27 May 2018 02:31:19 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic307-4.consmr.mail.bf2.yahoo.com (sonic307-4.consmr.mail.bf2.yahoo.com [74.6.134.43]) (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 543366A8D4 for ; Sun, 27 May 2018 02:31:18 +0000 (UTC) (envelope-from marklmi@yahoo.com) X-YMail-OSG: wR4HDDoVM1kec5j_hs9T5TjuPSvgihLXsAzDphR_hZylxk8VE1dRKyU7IO17dK_ neXThW.7CamernmS5dCBpS_aqQNHKVsrJz_nbnZMByLQtKrWeB_YrfEqnYp1rJTb0KbWvM1K7qXB KjQlsTWfklQDl_R.aQmTWzw8Kx5IrY3RbbNM6zkos5nTBZpLKSAikwUdHsu2vvBAXxFbuKS_SwAi rl446exA57frJ4t2s7L1jsUScVKo27oX1bGjIJMqYfDy3mtsuonxOe34QePuPLHfIUqcCVLVKuzv duLUgmyPW5fY8bVPg29eHfwHQZsWXlxMUCLAI24UJzr99iqbZmJXMr.VnN_nG4MLuTe5qnRNIfqJ IxHUQHvPSiLfGESVTF2mw6BGDB6iJuBlmcOsygfzUAeyA363XkSqVQtA6Q9ZsydAzS5gEFZt_8sY Nwo3MuyECA6kNtxP1PDldlv.b82M2NXbhoLUQI4sm6hBmj.MnwLIgic9Wfp6AwYeNQTXxZ4y_0Cw 8AQdI9O1lQ5D7HE4fgHzbuFR6WlEG3QnfCdlQ.kZ6Nuv2PrxYtDXCjKbFDuel0ySCddVkRYsdh69 1rzwKDLBPCVjcvP13bliIUf.Scgk38ljeeEg8CtN8e2MtMM4Ty1.pk25cDoF59zYg0WX8L1tc4M1 roa5dAiNf0oIVaUmqoTsJD1UxL8_xRFC8ENVg Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.bf2.yahoo.com with HTTP; Sun, 27 May 2018 02:31:12 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.25]) ([76.115.7.162]) by smtp429.mail.bf1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 1c42ce5e67f44733b3bc50e17152e136; Sun, 27 May 2018 02:31:10 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: bugzilla 213937: not just arm and not just stable/11 Message-Id: <910869D6-0CA7-4B3C-BF91-A56EFD62FDA8@yahoo.com> Date: Sat, 26 May 2018 19:31:08 -0700 To: freebsd-arm@freebsd.org, FreeBSD Current X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 02:31:19 -0000 I've updated the description and such for: Bug 213937 - stable/11 -r334246 on BPi-M3 (cortex-a7), amd64, and more, = also head: ktrace misreports bad svc (SIGSYS) number The primary description is really Comment 2 from Oleksandr Tymoshenko : > This is not ARM specific, the same bug can be reproduced in amd64 = using syscall(2) function. >=20 > The reason for this that in sys/sys/ktrace.h syscall code is defined = as short: > struct ktr_syscall { > short ktr_code; /* syscall number */ > short ktr_narg; /* number of arguments */ > /* > * followed by ktr_narg register_t > */ > register_t ktr_args[1]; > }; >=20 > This definitely does not match syscall(2) API where code is defined as = integer and all architectures define it as u_int in struct syscall_args. It is that way in every stable/11 and head version of the file that I have looked at. =3D=3D=3D Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Sun May 27 03:17: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 22622F76C4E for ; Sun, 27 May 2018 03:17:18 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fmsmga102.fm.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 775626BF0F for ; Sun, 27 May 2018 03:17:17 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2018 20:17:09 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,446,1520924400"; d="scan'208,217";a="42490524" Received: from orsmsx108.amr.corp.intel.com ([10.22.240.6]) by fmsmga007.fm.intel.com with ESMTP; 26 May 2018 20:17:09 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.64]) by ORSMSX108.amr.corp.intel.com ([169.254.2.31]) with mapi id 14.03.0319.002; Sat, 26 May 2018 20:17:08 -0700 From: "Pieper, Jeffrey E" To: =?windows-1256?Q?freebsd-current_=FD=5Bfreebsd-current=40freebsd=2Eorg=5D?= =?windows-1256?Q?=FD?= Subject: ifa_ifwithnet failed ??? Thread-Topic: ifa_ifwithnet failed ??? Thread-Index: AdP1aKTP8RdOghFiQEmVOKBaZRDBLQ== Date: Sun, 27 May 2018 03:17:07 +0000 Message-ID: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.19.9.46] MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 03:17:18 -0000 I'm seeing this spam dmesg continuously on a build from this afternoon (r33= 4252): May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed May 27 03:06:03 u0855 syslogd: last message repeated 11 times May 27 03:06:03 u0855 kernel: . May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed May 27 03:06:39 u0855 syslogd: last message repeated 60 times May 27 03:08:39 u0855 syslogd: last message repeated 59 times Is anyone else seeing this? Jeff Pieper From owner-freebsd-current@freebsd.org Sun May 27 03:20: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 9245DF76E4F for ; Sun, 27 May 2018 03:20:06 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 229136C0CF for ; Sun, 27 May 2018 03:20:06 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x233.google.com with SMTP id y10-v6so10154584otg.10 for ; Sat, 26 May 2018 20:20:06 -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=bIwTd932fUjt8/7pAkve968KiT8X5rSAWfiSPHFcDQk=; b=F6pvxF41SPCvdBB6f/cBlZmlr1oRdtDvx4vyOiXldGZ7wuSHDiSQ0vXN4s3b+8U39z JWMWLfbJydmyenV8NIe/pArynNgXYETOAy/flQ1wc0qMBE5jXcEVQahmPvLs/XYHySQD p5czAgSArBI5tbgsJ4ssGZ5qaew+qxIqooPilpzVMvqnuIEWLIh4jW8gd1PrmyHP8FRl IyYvW2Bh8ONefwhAYBqPWsPvNEbYW4HtK2qUPAuc+Hcrf8ZJQ1t6T4Tx1b/X/z0QgD45 FWvcpjO8GF08C9YptfeRAzhaNVJ5OXg+skk9qgzpoWfRY0DY1CpwonX0CAhNbcA8/HFQ Bhlw== 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=bIwTd932fUjt8/7pAkve968KiT8X5rSAWfiSPHFcDQk=; b=GdU0hBaYGGS/X//nWgNcsMtZIbtsjIS6VvU34Iy8DeCAzMkKslHXAeDHbJxku1odM2 sg+0x+oxWqeb2v1VYFbarbwSwJa5VsMMKIbZokRexeVYJ2apWDh8gzlxuBMf5y6Jvli+ 8569kHvJwT/1kd+bSx5VGbV81nYFgkijqaWcT/345q4qWCPnU11cW8T14YPOPbGe0rvj TiKNoG4AZ0vcGcrecQGXyfE4Vp4zQMkcHG3MQqNiQc/ef/tlSkQrDw5Ifwy6k0dvtUxc Uv7w3M8evKiI1s6TKGBDKgtdGshMJIP2zxSaVvXMLN9/SlZQTiKYSB3dIaziQUp/0h8B CIrQ== X-Gm-Message-State: ALKqPweunIbelPU0Sy5r0bSdSqI49517LTmete3Iglohi0wyLMS1hl3y 3vZ7moM9Y0wDNgXtMuD3fil2DKqmG/hWfiJD0Uo= X-Google-Smtp-Source: ADUXVKK7FwGWNZDQLLgfOl+jKOOq81bAvaeVWkYUl7YpqKg8oKIUFefhzJTZxwvl/s7RQSOCqs4ff2aDKcSaKE/MSZA= X-Received: by 2002:a9d:3e4c:: with SMTP id h12-v6mr3670855otg.150.1527391205434; Sat, 26 May 2018 20:20:05 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Sat, 26 May 2018 20:20:05 -0700 (PDT) In-Reply-To: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> From: "K. Macy" Date: Sat, 26 May 2018 20:20:05 -0700 X-Google-Sender-Auth: bbI9bxPb4c77p2nzxwC8cXGmliw Message-ID: Subject: Re: ifa_ifwithnet failed ??? To: "Pieper, Jeffrey E" Cc: =?UTF-8?B?ZnJlZWJzZC1jdXJyZW50IOKAjltmcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmdd4oCO?= Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 03:20:06 -0000 On Sat, May 26, 2018 at 8:17 PM, Pieper, Jeffrey E wrote: > I'm seeing this spam dmesg continuously on a build from this afternoon (r334252): > > May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed > May 27 03:06:03 u0855 syslogd: last message repeated 11 times > May 27 03:06:03 u0855 kernel: . > May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed > May 27 03:06:39 u0855 syslogd: last message repeated 60 times > May 27 03:08:39 u0855 syslogd: last message repeated 59 times What did this happen subsquent to? > Is anyone else seeing this? > > Jeff Pieper > _______________________________________________ > 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 May 27 03:34: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 5EDF1F777DE for ; Sun, 27 May 2018 03:34:25 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga105.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 877406CB08; Sun, 27 May 2018 03:34:24 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2018 20:33:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,446,1520924400"; d="scan'208";a="62015236" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by orsmga002.jf.intel.com with ESMTP; 26 May 2018 20:33:13 -0700 Received: from orsmsx112.amr.corp.intel.com (10.22.240.13) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sat, 26 May 2018 20:33:13 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.64]) by ORSMSX112.amr.corp.intel.com ([169.254.3.95]) with mapi id 14.03.0319.002; Sat, 26 May 2018 20:33:12 -0700 From: "Pieper, Jeffrey E" To: "K. Macy" CC: =?windows-1256?Q?freebsd-current_=FD=5Bfreebsd-current=40freebsd=2Eorg=5D?= =?windows-1256?Q?=FD?= Subject: RE: ifa_ifwithnet failed ??? Thread-Topic: ifa_ifwithnet failed ??? Thread-Index: AdP1aKTP8RdOghFiQEmVOKBaZRDBLQAO6LiA//+MCAw= Date: Sun, 27 May 2018 03:33:11 +0000 Message-ID: <2A35EA60C3C77D438915767F458D6568B8A5590D@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.19.9.46] Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 03:34:25 -0000 =0A= ________________________________________=0A= From: kmacybsd@gmail.com [kmacybsd@gmail.com] on behalf of K. Macy [kmacy@f= reebsd.org]=0A= Sent: Saturday, May 26, 2018 8:20 PM=0A= To: Pieper, Jeffrey E=0A= Cc: freebsd-current =FD[freebsd-current@freebsd.org]=FD=0A= Subject: Re: ifa_ifwithnet failed ???=0A= =0A= On Sat, May 26, 2018 at 8:17 PM, Pieper, Jeffrey E=0A= wrote:=0A= > I'm seeing this spam dmesg continuously on a build from this afternoon (r= 334252):=0A= >=0A= > May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed=0A= > May 27 03:06:03 u0855 syslogd: last message repeated 11 times=0A= > May 27 03:06:03 u0855 kernel: .=0A= > May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed=0A= > May 27 03:06:39 u0855 syslogd: last message repeated 60 times=0A= > May 27 03:08:39 u0855 syslogd: last message repeated 59 times=0A= =0A= =0A= > What did this happen subsquent to?=0A= =0A= I just started seeing it yesterday on current, but prior to that we've been= pulling from https://github.com/intel-wired-ethernet/freebsd, but that isn= 't rebased as frequently as it should be so that probably doesn't help very= much. We just started using current for https://reviews.freebsd.org/D15577= .=0A= =0A= Jeff=0A= =0A= > _______________________________________________=0A= > freebsd-current@freebsd.org mailing list=0A= > https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "=0A= From owner-freebsd-current@freebsd.org Sun May 27 03:35: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 67C4CF778A5 for ; Sun, 27 May 2018 03:35:56 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8E8C6CC11 for ; Sun, 27 May 2018 03:35:55 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-oi0-x22d.google.com with SMTP id c203-v6so7762388oib.7 for ; Sat, 26 May 2018 20:35:55 -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:content-transfer-encoding; bh=oaEfLdpprk4t6pfqc1peMZxzU95sBbftyfMSKhAoOAo=; b=fkoVrIVj4AZyn8lp/D1rsGV9XWTVRPSE/xgK+Ygv0O3HCKl0SnEBHhvd4m4DBNyJCx 0jmby5AehAnQMp5ETXyC9edzJ86UrXcUxmqGlqTci1aQXcHwcloLuCuKTbvPz67A1xtD N+oXUvdv1fEkeUPONbB6Qv3kcwHQGpaT+KLENPMYg+41HV0LSU+bQ6Pe/NoxIp6iujGY ra+/1YPEhZ/gpRTIXGTrJbah4+d3xcXKb4mRKyqSCcWIi9aCHhvE5qLmvUMkUXhudrME 4yy8584XjiUf6ETZsL3p2XpORg7tb6RlQsZ1Mw5k2kMJZRZKR8p9+A9TpeiMLmJcE7Rq tumA== 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:content-transfer-encoding; bh=oaEfLdpprk4t6pfqc1peMZxzU95sBbftyfMSKhAoOAo=; b=reV3b5/eZw6K/ewgmz0ZX0v4+4hEcUlf75vOlzCdeWR8Pfk9xgydXAG3RBNlnheIvH jixTGCSzTHXP+coilM62hoG8JwnnQarvRW7nzNdt6x7d8ssjS8xoZtjeHIxHe1mQX+jP x+zhNbRFO3xvyBAVklcrrwgLJHwTIwf3oB96gU83QjfZqGvvmB86nM/p0sqX7PPYC2lo XIDwzszu+SVkhWLMcZJ9QoSkgjxf9mLo8dvaaAQle46XP/t1LWANAcsVvJaP7zosv9i0 4Y18zjPTLMTqTZtQZNNxoxSSSJAlLsb5E6VCygpndFU21VUVtq/JKoyowkKvdZO8m6LV yA5A== X-Gm-Message-State: ALKqPwcJu/j05ycnEFZnjTOzHDNx1dG1/5xwdJNLrdbqpfhgk137ZMYb XGRZmu9bkMASI3MPvnao52kqVGWeHHw3CWXQkCuGRA== X-Google-Smtp-Source: ADUXVKJqIsR7SjYCOmuWXHQM3JG6nncxtJ6Owb/fJTWrJqUisDgMQuUsRk+bziHnjXgJHM0M/4do84/i/dox5bTS1eY= X-Received: by 2002:a54:4e8b:: with SMTP id c11-v6mr4936474oiy.250.1527392155285; Sat, 26 May 2018 20:35:55 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Sat, 26 May 2018 20:35:54 -0700 (PDT) In-Reply-To: <2A35EA60C3C77D438915767F458D6568B8A5590D@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> <2A35EA60C3C77D438915767F458D6568B8A5590D@ORSMSX111.amr.corp.intel.com> From: "K. Macy" Date: Sat, 26 May 2018 20:35:54 -0700 X-Google-Sender-Auth: ls-PdGFNbJjQoBbPJZOL2LL-VAw Message-ID: Subject: Re: ifa_ifwithnet failed ??? To: "Pieper, Jeffrey E" Cc: =?UTF-8?B?ZnJlZWJzZC1jdXJyZW50IOKAjltmcmVlYnNkLWN1cnJlbnRAZnJlZWJzZC5vcmdd4oCO?= Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 03:35:56 -0000 My guess is that this is caused by my changes. However, this is the first time I've heard this reported so it would be useful to know how I might reproduce it. Thanks. -M On Sat, May 26, 2018 at 8:33 PM, Pieper, Jeffrey E wrote: > > ________________________________________ > From: kmacybsd@gmail.com [kmacybsd@gmail.com] on behalf of K. Macy [kmacy= @freebsd.org] > Sent: Saturday, May 26, 2018 8:20 PM > To: Pieper, Jeffrey E > Cc: freebsd-current =E2=80=8E[freebsd-current@freebsd.org]=E2=80=8E > Subject: Re: ifa_ifwithnet failed ??? > > On Sat, May 26, 2018 at 8:17 PM, Pieper, Jeffrey E > wrote: >> I'm seeing this spam dmesg continuously on a build from this afternoon (= r334252): >> >> May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed >> May 27 03:06:03 u0855 syslogd: last message repeated 11 times >> May 27 03:06:03 u0855 kernel: . >> May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed >> May 27 03:06:39 u0855 syslogd: last message repeated 60 times >> May 27 03:08:39 u0855 syslogd: last message repeated 59 times > > >> What did this happen subsquent to? > > I just started seeing it yesterday on current, but prior to that we've be= en pulling from https://github.com/intel-wired-ethernet/freebsd, but that i= sn't rebased as frequently as it should be so that probably doesn't help ve= ry much. We just started using current for https://reviews.freebsd.org/D155= 77. > > Jeff > >> _______________________________________________ >> 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 May 27 03:52: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 37DD1F78286 for ; Sun, 27 May 2018 03:52:02 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga101.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DB996D5BF; Sun, 27 May 2018 03:52:01 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 May 2018 20:51:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,446,1520924400"; d="scan'208";a="232168165" Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by fmsmga006.fm.intel.com with ESMTP; 26 May 2018 20:51:53 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.64]) by ORSMSX101.amr.corp.intel.com ([169.254.8.143]) with mapi id 14.03.0319.002; Sat, 26 May 2018 20:51:52 -0700 From: "Pieper, Jeffrey E" To: "K. Macy" CC: =?windows-1256?Q?freebsd-current_=FD=5Bfreebsd-current=40freebsd=2Eorg=5D?= =?windows-1256?Q?=FD?= Subject: RE: ifa_ifwithnet failed ??? Thread-Topic: ifa_ifwithnet failed ??? Thread-Index: AdP1aKTP8RdOghFiQEmVOKBaZRDBLQAO6LiA//+MCAyAAHhjAP//jgz5 Date: Sun, 27 May 2018 03:51:51 +0000 Message-ID: <2A35EA60C3C77D438915767F458D6568B8A55936@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> <2A35EA60C3C77D438915767F458D6568B8A5590D@ORSMSX111.amr.corp.intel.com>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.19.9.46] Content-Type: text/plain; charset="windows-1256" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 03:52:02 -0000 =0A= ________________________________________=0A= From: kmacybsd@gmail.com [kmacybsd@gmail.com] on behalf of K. Macy [kmacy@f= reebsd.org]=0A= Sent: Saturday, May 26, 2018 8:35 PM=0A= To: Pieper, Jeffrey E=0A= Cc: freebsd-current =FD[freebsd-current@freebsd.org]=FD=0A= Subject: Re: ifa_ifwithnet failed ???=0A= =0A= > My guess is that this is caused by my changes. However, this is the=0A= > first time I've heard this reported so it would be useful to know how=0A= > I might reproduce it.=0A= =0A= > Thanks.=0A= > -M=0A= =0A= ERJ did commit at least one iflib patch yesterday as well. =0A= =0A= This is the kernel config:=0A= =0A= include GENERIC-NODEBUG=0A= =0A= ident VALIDATION=0A= =0A= option MROUTING=0A= option DDB=0A= =0A= # iWARP support=0A= options OFED=0A= options OFED_DEBUG_INIT=0A= options COMPAT_LINUXKPI=0A= options SDP=0A= options IPOIB_CM=0A= =0A= nodevice em=0A= nodevice igb=0A= nodevice fxp=0A= nodevice ix=0A= nodevice ixv=0A= nodevice ixl=0A= nodevice ixlv=0A= =0A= device netmap=0A= =0A= Jeff=0A= =0A= =0A= From owner-freebsd-current@freebsd.org Sun May 27 06:42: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 4592AF7E9CA for ; Sun, 27 May 2018 06:42:20 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (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 AB26072131 for ; Sun, 27 May 2018 06:42:19 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.14.87.226]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lwarz-1gPXuf0lHb-018Lwd; Sun, 27 May 2018 08:36:58 +0200 Date: Sun, 27 May 2018 08:36:19 +0200 From: "O. Hartmann" To: "Pieper, Jeffrey E" Cc: "freebsd-current =?ISO-8859-1?Q?=3F[freebsd-current@freebsd.org]=3F?=" Subject: Re: ifa_ifwithnet failed ??? Message-ID: <20180527083646.27d457d5@thor.intern.walstatt.dynvpn.de> In-Reply-To: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:knyMIIeumEQuAi1jngzc/EpkF03LfJ+Vcc8IXw2kMz9+0pHN+Fo YXNC5haryNRbRZ9Na5kSlx4q4Y482dzWmlcEJ6q0kB1GBQPCKvOBM15XMG3oU0dlnqA3+eV 8kBQAfZ0rdQQ5/nzcAfJawCrEINwkWaA8k3W5HopreD2tykq4Lltgt5NYqjJvZRWWo15PDB T+9W7FNvVkUgjPW8o8Bnw== X-UI-Out-Filterresults: notjunk:1;V01:K0:SFD/TznX66Q=:D9Gszf1br4p2JkO6uUvb9H qFliMvpye8oWS10L56i+z9XPsEv7LrCjrm6v5gUQg6x5kYHtCQIPEpha5ufowEEsqpegktZF7 yy+LyBIw9E1WOaluWr+Q1q40RCSzsbami0sJxp9IzLjpFq/dDP8eMkwQv9x/Y8Rd+opokPAWF soWmVV4AjZidh7N2faaYxTWMSnlQnW19FLhivZrVS+Aneyx7a88txnL34LQPI5U50EOrYvD0H GGBzJy/a4tG+CF7jwDhdSjVezPHOolFHW2jD7rBADGA6KF1KOHGCADoybacMYiKb6+k33tcNk 7sY2M3YRVTwDAq/DzrU2rEIC8asc/PllEN5ptXCdLnfuQPsjtZXfChrWEud7ITkxravwyLyvz 0lnrNBEM06HqkgkUsbLWklo5ILA3DwXOwPBRZby0iclW5bJjMAAmm9knnRxAXZHNsjV0g9tTa GaF4BXwGA5UNRGYwLxhjkShWApz0P6SOXGReCHkTLi9Kiqv4QnSslV57GIID1H2GcejjxfYkp B2v+FfOcXaD6Wf9HONvMDKK+3PhBamGbTu1/LP5qYjJTLzgXSCEK/D+gbMUK0RLIXZq/bssA/ zqBBZROFctmJnh5EMkHjLLvKEOTHb5loy8n1726JOG86PO2H1dhEkRcPgZ5Op3fZkUZyXI0zk esgQbVJdX566c0SOBwIVTsHd1JRIO1Z+HgDyU6c7uhfShp7WEkWBgk8WQeTkNmBseRAMbl+uI yUtMuP4ZhDQ6CIaERKEBvRqtG/DGbVTiyH54jQ3+8+9AXqmXzDGNUIboAAvMYFaUJjeIuOHjh oa0Osgz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 06:42:20 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFN1 biwgMjcgTWF5IDIwMTggMDM6MTc6MDcgKzAwMDANCiJQaWVwZXIsIEplZmZyZXkgRSIgPGplZmZy ZXkuZS5waWVwZXJAaW50ZWwuY29tPiBzY2hyaWViOg0KDQo+IEknbSBzZWVpbmcgdGhpcyBzcGFt IGRtZXNnIGNvbnRpbnVvdXNseSBvbiBhIGJ1aWxkIGZyb20gdGhpcyBhZnRlcm5vb24gKHIzMzQy NTIpOg0KPiANCj4gTWF5IDI3IDAzOjA2OjAzIHUwODU1IGtlcm5lbDogaWZhX2lmd2l0aG5ldCBm YWlsZWQNCj4gTWF5IDI3IDAzOjA2OjAzIHUwODU1IHN5c2xvZ2Q6IGxhc3QgbWVzc2FnZSByZXBl YXRlZCAxMSB0aW1lcw0KPiBNYXkgMjcgMDM6MDY6MDMgdTA4NTUga2VybmVsOiAuDQo+IE1heSAy NyAwMzowNjowNSB1MDg1NSBrZXJuZWw6IGlmYV9pZndpdGhuZXQgZmFpbGVkDQo+IE1heSAyNyAw MzowNjozOSB1MDg1NSBzeXNsb2dkOiBsYXN0IG1lc3NhZ2UgcmVwZWF0ZWQgNjAgdGltZXMNCj4g TWF5IDI3IDAzOjA4OjM5IHUwODU1IHN5c2xvZ2Q6IGxhc3QgbWVzc2FnZSByZXBlYXRlZCA1OSB0 aW1lcw0KPiANCj4gDQo+IElzIGFueW9uZSBlbHNlIHNlZWluZyB0aGlzPw0KPiANCj4gSmVmZiBQ aWVwZXINCj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N Cj4gZnJlZWJzZC1jdXJyZW50QGZyZWVic2Qub3JnIG1haWxpbmcgbGlzdA0KPiBodHRwczovL2xp c3RzLmZyZWVic2Qub3JnL21haWxtYW4vbGlzdGluZm8vZnJlZWJzZC1jdXJyZW50DQo+IFRvIHVu c3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLWN1cnJlbnQtdW5zdWJzY3JpYmVA ZnJlZWJzZC5vcmciDQoNCk1lLCB0b28sIG9uIGEgcm91dGVyL2ZpcmV3YWxsIHN5c3RlbSBydW5u aW5nOg0KDQpGcmVlQlNEIDEyLjAtQ1VSUkVOVCAjNyByMzM0MjM2OiBTYXQgTWF5IDI2IDA4OjAz OjM5IENFU1QgMjAxOA0KDQpUaGUgY29uc29sZSBpcyBzcGFtbWVkIHdpdGggaWZhX2lmd2l0aG5l dCBmYWlsZWQgYWZ0ZXIgZmlyc3QgYm9vdCBidXQgd2hpbGUgcnVubmluZywgdGhlDQptZXNzYWdl IGRpc2FwcGVhcnMgb3IgYXQgbGVhc3QgdGhlIGNvbnNvbGUgaXNuJ3Qgc3BhbW1lZCBhbnkgbW9y ZS4NCg0Kb2gNCg0KLS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCg0KaUxVRUFSTUtBQjBX SVFRWlZaTXpBdHdDMlQvODZUclM1MjhmeUZoWWxBVUNXd3BSL2dBS0NSRFM1MjhmeUZoWQ0KbER5 ZEFmOXIxUVB3azZGZDUxZ05hZlRCVjlJenp6Y2Y2TDBISkV5WldPZHhaMiszSG1WV0F2MWpBOWhl cTMzcQ0KTmpuSlJpQ1ljVW8vYU9RME1zMUF0ME5vMnRyWEFmc0V5NDdIekh2Q1NqVlduSnZXSkRS MjJMTHBva0FaeXZmTQ0KWEJIWmJQU0JkTG12Vzc1WFNIcVZmU3pDS0tjcHkycWVMQjE5c1RJS1cz Sy9SSVFrTHhBTA0KPUNVbHENCi0tLS0tRU5EIFBHUCBTSUdOQVRVUkUtLS0tLQ0K From owner-freebsd-current@freebsd.org Sun May 27 06:47: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 2AC54EEA19F for ; Sun, 27 May 2018 06:47:38 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-ot0-x244.google.com (mail-ot0-x244.google.com [IPv6:2607:f8b0:4003:c0f::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AED7572547 for ; Sun, 27 May 2018 06:47:37 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-ot0-x244.google.com with SMTP id l22-v6so10385256otj.0 for ; Sat, 26 May 2018 23:47:37 -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=XFEQ+IBtslF4p12PnbhTyzL+Snu4l7AOWPNA0r/yjTU=; b=hsnGE6NDjFVkDVr6HYUrihoYEgWC7r4jTiN25E8C1us/qFp95BsWMxpDSrDNkAwwkF uUJetKopzx8yrvZ3Nvq77/IfAQOqXnct2rC5+JKqeFhvp+q4vdFJrtELc9xiboQ2EG7/ 5OpwjaZ+QRfciFHKAzsA2KFTZwO7y6xqPFDrfb5rfQgBQ1CJqGxx+HzPe87PmtoJrf2V Ajn/inITDe9AA+MgE48TJYRURiJpKfcM/N1LEjQ48JbJE3tXysxzzBbR5nqjObPW80B4 1Zvqha5Ps+1MzCyNnUxWP0DvuWJjpCxUoH+V4GHP/yOTJcgJUAZq5gWalbF2Cx72q5Gg TogQ== 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=XFEQ+IBtslF4p12PnbhTyzL+Snu4l7AOWPNA0r/yjTU=; b=rlh1WMhQ5BGBTS+exxI6F7eC2TDfVopY3Or22+TXXNmVJ0Nz+fUEVQdDHYaNVV0VJm B8tsKMqtoRli4sMvnlhh0ulBTC28l6BdUFdK5JtexN2Ex9PXDgcxLU86B6+I5Zgy/ZPJ FS2koOb/F6yydBjcb42bz75ivipJ5BgiyN6V1M2DiJFRD6Z+M9d8j03UXTr/+M+shWaA RzQNOrxrrbTe97IC1Zd1Tw+3WvbQcMfvCvvvSCOmmGa/t4Gkhy871LqGpmt28LsVUXYG AUWwS8l3rqcumwMRio8x3h+VdtY+mA6dW+esBvSQfGQVWGsOEpfsPng32TKrKKMWSdAS orZQ== X-Gm-Message-State: ALKqPwdcZ0c3VqBtnjhqzswBufiQhYTRG/qSYjq4h4EGUr56yKIanix/ MC+PQ0OEJfWBR04dBCUJYzsxk7nQS5l8d+ZA+KXWN6FG X-Google-Smtp-Source: AB8JxZpnLpnOLkBIUJukynJKcTBS6AQe1kFUAwYyM0+ytFiBVkXuUZpGwzO/kKxOassqiVl3sCrIGAPXOiAhThWduN8= X-Received: by 2002:a9d:3116:: with SMTP id e22-v6mr5474035otc.29.1527403656995; Sat, 26 May 2018 23:47:36 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Sat, 26 May 2018 23:47:36 -0700 (PDT) In-Reply-To: <20180527083646.27d457d5@thor.intern.walstatt.dynvpn.de> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> <20180527083646.27d457d5@thor.intern.walstatt.dynvpn.de> From: "K. Macy" Date: Sat, 26 May 2018 23:47:36 -0700 X-Google-Sender-Auth: UnZrPr54QGsAMf9icYErv87ps_M Message-ID: Subject: Re: ifa_ifwithnet failed ??? To: "O. Hartmann" Cc: "Pieper, Jeffrey E" , "freebsd-current ?[freebsd-current@freebsd.org]?" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 06:47:38 -0000 please update to r334253 On Sat, May 26, 2018 at 11:36 PM, O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am Sun, 27 May 2018 03:17:07 +0000 > "Pieper, Jeffrey E" schrieb: > >> I'm seeing this spam dmesg continuously on a build from this afternoon (r334252): >> >> May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed >> May 27 03:06:03 u0855 syslogd: last message repeated 11 times >> May 27 03:06:03 u0855 kernel: . >> May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed >> May 27 03:06:39 u0855 syslogd: last message repeated 60 times >> May 27 03:08:39 u0855 syslogd: last message repeated 59 times >> >> >> Is anyone else seeing this? >> >> Jeff Pieper >> _______________________________________________ >> 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" > > Me, too, on a router/firewall system running: > > FreeBSD 12.0-CURRENT #7 r334236: Sat May 26 08:03:39 CEST 2018 > > The console is spammed with ifa_ifwithnet failed after first boot but while running, the > message disappears or at least the console isn't spammed any more. > > oh > > -----BEGIN PGP SIGNATURE----- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWwpR/gAKCRDS528fyFhY > lDydAf9r1QPwk6Fd51gNafTBV9Izzzcf6L0HJEyZWOdxZ2+3HmVWAv1jA9heq33q > NjnJRiCYcUo/aOQ0Ms1At0No2trXAfsEy47HzHvCSjVWnJvWJDR22LLpokAZyvfM > XBHZbPSBdLmvW75XSHqVfSzCKKcpy2qeLB19sTIKW3K/RIQkLxAL > =CUlq > -----END PGP SIGNATURE----- > _______________________________________________ > 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 May 27 16:00: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 D9739F78B0F for ; Sun, 27 May 2018 16:00:36 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "orsmga105.jf.intel.com", Issuer "COMODO RSA Organization Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A31F84B88; Sun, 27 May 2018 16:00:35 +0000 (UTC) (envelope-from jeffrey.e.pieper@intel.com) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 May 2018 09:00:33 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,448,1520924400"; d="scan'208";a="43211275" Received: from orsmsx106.amr.corp.intel.com ([10.22.225.133]) by fmsmga008.fm.intel.com with ESMTP; 27 May 2018 09:00:33 -0700 Received: from orsmsx158.amr.corp.intel.com (10.22.240.20) by ORSMSX106.amr.corp.intel.com (10.22.225.133) with Microsoft SMTP Server (TLS) id 14.3.319.2; Sun, 27 May 2018 09:00:32 -0700 Received: from orsmsx111.amr.corp.intel.com ([169.254.12.64]) by ORSMSX158.amr.corp.intel.com ([169.254.10.48]) with mapi id 14.03.0319.002; Sun, 27 May 2018 09:00:31 -0700 From: "Pieper, Jeffrey E" To: "K. Macy" , "O. Hartmann" CC: "freebsd-current ?[freebsd-current@freebsd.org]?" Subject: RE: ifa_ifwithnet failed ??? Thread-Topic: ifa_ifwithnet failed ??? Thread-Index: AdP1aKTP8RdOghFiQEmVOKBaZRDBLQAVwy6AAABk4gAABKCOpA== Date: Sun, 27 May 2018 16:00:30 +0000 Message-ID: <2A35EA60C3C77D438915767F458D6568B8A55A84@ORSMSX111.amr.corp.intel.com> References: <2A35EA60C3C77D438915767F458D6568B8A558E5@ORSMSX111.amr.corp.intel.com> <20180527083646.27d457d5@thor.intern.walstatt.dynvpn.de>, In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.3.86.137] 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.26 Precedence: 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, 27 May 2018 16:00:37 -0000 Thanks Matt, no more spam :)=0A= ________________________________________=0A= From: kmacybsd@gmail.com [kmacybsd@gmail.com] on behalf of K. Macy [kmacy@f= reebsd.org]=0A= Sent: Saturday, May 26, 2018 11:47 PM=0A= To: O. Hartmann=0A= Cc: Pieper, Jeffrey E; freebsd-current ?[freebsd-current@freebsd.org]?=0A= Subject: Re: ifa_ifwithnet failed ???=0A= =0A= please update to r334253=0A= =0A= On Sat, May 26, 2018 at 11:36 PM, O. Hartmann wrot= e:=0A= > -----BEGIN PGP SIGNED MESSAGE-----=0A= > Hash: SHA512=0A= >=0A= > Am Sun, 27 May 2018 03:17:07 +0000=0A= > "Pieper, Jeffrey E" schrieb:=0A= >=0A= >> I'm seeing this spam dmesg continuously on a build from this afternoon (= r334252):=0A= >>=0A= >> May 27 03:06:03 u0855 kernel: ifa_ifwithnet failed=0A= >> May 27 03:06:03 u0855 syslogd: last message repeated 11 times=0A= >> May 27 03:06:03 u0855 kernel: .=0A= >> May 27 03:06:05 u0855 kernel: ifa_ifwithnet failed=0A= >> May 27 03:06:39 u0855 syslogd: last message repeated 60 times=0A= >> May 27 03:08:39 u0855 syslogd: last message repeated 59 times=0A= >>=0A= >>=0A= >> Is anyone else seeing this?=0A= >>=0A= >> Jeff Pieper=0A= >> _______________________________________________=0A= >> freebsd-current@freebsd.org mailing list=0A= >> https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.or= g"=0A= >=0A= > Me, too, on a router/firewall system running:=0A= >=0A= > FreeBSD 12.0-CURRENT #7 r334236: Sat May 26 08:03:39 CEST 2018=0A= >=0A= > The console is spammed with ifa_ifwithnet failed after first boot but whi= le running, the=0A= > message disappears or at least the console isn't spammed any more.=0A= >=0A= > oh=0A= >=0A= > -----BEGIN PGP SIGNATURE-----=0A= >=0A= > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWwpR/gAKCRDS528fyFhY=0A= > lDydAf9r1QPwk6Fd51gNafTBV9Izzzcf6L0HJEyZWOdxZ2+3HmVWAv1jA9heq33q=0A= > NjnJRiCYcUo/aOQ0Ms1At0No2trXAfsEy47HzHvCSjVWnJvWJDR22LLpokAZyvfM=0A= > XBHZbPSBdLmvW75XSHqVfSzCKKcpy2qeLB19sTIKW3K/RIQkLxAL=0A= > =3DCUlq=0A= > -----END PGP SIGNATURE-----=0A= > _______________________________________________=0A= > freebsd-current@freebsd.org mailing list=0A= > https://lists.freebsd.org/mailman/listinfo/freebsd-current=0A= > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= "=0A= From owner-freebsd-current@freebsd.org Sun May 27 19:12:57 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 B064BF7D6BB for ; Sun, 27 May 2018 19:12:57 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (bastille.leidinger.net [89.238.82.207]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 22BEC6A1BE for ; Sun, 27 May 2018 19:12:57 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Sun, 27 May 2018 21:12:17 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1527448374; bh=jJ4RyT3WOUYozSAOIYh+imDGLE4Ew8sb8Sr7omxEsfk=; h=Date:From:To:Subject:References:In-Reply-To; b=nwoANvwNxlOWuA88zMf7Jsmi/ltrbNLPBMKDTofdlwNH2tzQmVWk50nhdVlAOLKve P1K/QSPMNv4DwQC3m5hRntiBNcVN5jg32TOAFQI7HwC0ayk2qt+IXjYt5IKsk/sTpd DUvvtWJXo4RDSycoUhUBQJsndPnIksnQGWOnE+mvxXp1DG5Lif9dO4jWjHWDUNq5Vw 8hO2hB8Qyq9ziaTMxVgtJnKcK7EfoIrivdJj1Mx3Y97TBZ/vsR1b5CPPXfWF71JUHD +XdknmspsaBFa06Qj+BNfrrXTw8kimb5K0larDtgzc8hBKkYJ2LU6MchrJtJKEPMrs 9axiiyrP0J7lA== Message-ID: <20180527211217.Horde.opQzHI4VOIxPiirx10J9wTe@webmail.leidinger.net> From: Alexander Leidinger To: freebsd-current@freebsd.org Subject: Re: Recent changes in routing or IPv6 related parts? References: <20180522101222.Horde.qCL_Frz6tcSPJrYy4UFWDEH@webmail.leidinger.net> <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> In-Reply-To: <34db4188119c29a5e38c9216b15f3411@udns.ultimatedns.net> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_X95Ezf14toofUPDphvQ_IRR"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 19:12:58 -0000 This message is in MIME format and has been PGP signed. --=_X95Ezf14toofUPDphvQ_IRR Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Chris H (from Tue, 22 May 2018=20=20 09:59:04=20-0700): > On Tue, 22 May 2018 10:12:22 +0200 "Alexander Leidinger"=20=20 >=20 said > >> Hi, >> >> I've updated 2 machines to r333966 and I see a change in the=20=20 >>=20behavior in the network area on one of the systems. >> >> To begin with, the "original" behavior was not OK either, the em=20=20 >>=20NIC fails to "do proper network communication"=20=20=20 >>=20(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220997). A=20=20= =20 >>=20workaround for me was so far to do an IPv4 ping to the router from=20= =20=20 >>=20time to time, and if it fails do some ifconfig down/up. If the ping=20= =20 >>=20 doesn't work afterwards, reboot. Most of the time this worked. >> >> Now I see a change in behavior, the scripts kicks in, all is ok for=20= =20 >>=20 the script afterwards, but internally (inside the machine) I can't=20= =20 >>=20 reach ipv6 jails. The system is reachable externally (only tested=20= =20 >>=20so far is the main host-IP). >> >> The setup is vimage based, several jails (via iocage) on epairs=20=20=20 >>=20connected via bridge to the NIC. One bridge for IPv6, one for IPv4.=20= =20 >>=20 rc.conf has prefer IPv4 setting after encountering another issue. >> >> One IPv4 address (/32) for the host where a nginx is running to=20=20 >>=20proxy port 80 and 443 requests on IPv4 to the IPv6 addresses of=20=20 >>=20the jails (IPv6 access is going directly to the jails). >> >> After a reboot, the nginx on the main IPv4 address delivers data=20=20 >>=20from the ipv6 addresses of the jails (rev-proxy setup). After a=20=20 >>=20while this stops working. The workaround-script mentioned above=20=20 >>=20doesn't change this behavior. Restarting nginx doesn't help. A=20=20 >>=20reboot helps. >> >> Has someone an idea of recent changes in a related area which may=20=20 >>=20be able to cause such an issue? Any rev I could try to revert to=20= =20 >>=20check if it is related? > Hello, Alexander. > I'm not sure if this landed in -CURRENT. I only know it landed in 11. > But your trouble might be related to pr #224247 : > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224247 > > Hope this helps. Thanks, I've compiled a kernel which will print a message with the=20=20 interface=20name when a packet will be dropped because of this. If I see=20= =20 something=20which makes it look like it could be related, I will disable=20= =20 it=20and try again. Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_X95Ezf14toofUPDphvQ_IRR Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbCwMRAAoJEKrxQhqFIICEF2EQALX7FSkUsisvL1+vbnH9rSFB PIkSb8YCapQpXscCeOgEbTGztnhI/jDMcFvMzOLr+f2Dy0z46MrgLPn/6pcmk52Q sBSu/rv24lUpgVD5kb1qAk9IhC8Pa7DU4CT23HAyXHP12h2UEdeQgFKS/mMc2Loi rD/E3r0qzgn5oIXvnW5qe231r+7Wmdstf1qoPThVETfA3RPhKV7CJa0BPnDYUcl4 OqB8u3AboButhHfSLgBUcas3OJdIrz3imUzQIbb8Mc0t1oo8qGALgxugsP+aEm6N 3rFW/Z8pUAn15/5E/sq5F96zG8lPde65uSBHH9zf4cNXRpDdgcmm9rUsFbcY9cY7 SPPL0HZm4xEsRe7hpLiTUcL6crOcnE6qkkV3noQpBWGmQhdVvcWIkytWd1Xdpu3Y RYaF4PCxn69jtUowEHbhp2mUNRhv1X0dsy4VUQ1r15liWFiH3hLrM45lv+GktI7j 9p/tlvsowL5ql/JPs1aKnAFX23HcOPEJHzKa2+X1qDTkWXoCK6wDb7TExNWKqVV0 aDTPrGkQbiFTecA1yJ0MhWhZCa36VhqjO1qx3YtcqGNim9c8unv65UwAKsYXXAyK C680MZs6jq5nvkokdMu0JY76jPuYPTBnqdlYCmL6/vYWqiXwuk46fhwxPEEoBwIU ssSQzZBX3IQixtjw10AI =JqqR -----END PGP SIGNATURE----- --=_X95Ezf14toofUPDphvQ_IRR-- From owner-freebsd-current@freebsd.org Sun May 27 19:42: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 CA297F7E29E for ; Sun, 27 May 2018 19:42:02 +0000 (UTC) (envelope-from kp@krion.cc) Received: from krion.cc (krion.cc [148.251.235.209]) (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 683CA6B1F3 for ; Sun, 27 May 2018 19:42:02 +0000 (UTC) (envelope-from kp@krion.cc) Received: from jo (90-152-149-189.static.highway.a1.net [90.152.149.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by krion.cc (Postfix) with ESMTPSA id 9BD701EB1F; Sun, 27 May 2018 21:42:00 +0200 (CEST) Date: Sun, 27 May 2018 21:41:59 +0200 From: Kirill Ponomarev To: Slawa Olhovchenkov Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180527194159.v54ox3vlthpuvx4q@jo> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ptgiukr3w63nhqco" Content-Disposition: inline In-Reply-To: <20180522144055.GD1954@zxy.spb.ru> User-Agent: NeoMutt/20180512 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 19:42:03 -0000 --ptgiukr3w63nhqco Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 05/22, Slawa Olhovchenkov wrote: > > It has been a while since I tried Karl's patch the last time, and I =20 > > stopped because it didn't apply to -current anymore at some point. > > Will what is provided right now in the patch work on -current? >=20 > I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g > I am don't know how to have two distinct patch (for stable and current) i= n one review. =20 I'm experiencing these issues sporadically as well, would you mind to publish this patch for fresh current? --ptgiukr3w63nhqco Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQFdBAABCABHFiEEJCHRFhEAQujKni1pDyI9/LMCykUFAlsLCgcpFIAAAAAAFQAL cGthLWFkZHJlc3NAZ251cGcub3Jna3BAa3Jpb24uY2MACgkQDyI9/LMCykUiPQf+ Lssi/ksaBHOd9qcW+tEwc4b8+U4L+CGhyw+Eghq74f99LztEoWXE0sXrdgPP7a8R HTUmBjXoP5115r4IXTb3MtLMd7xSuF6IZXr6Bi8V+nIgcZ3p4dQDo6SYhj/ygWJn 0dI9kw0OAAgSUZNSEWtXzPAji/H9Rt/7PhimI1WtURzNctB5DsbvmXjDHOJdob2i tqo1GTic2/Ki6hDzAmU97or8AnsjNvOqvcwBxHQ1IS2yKH+SyRg5uKubK8w6KoqK SYPjGSSpQigQDWoTPK2KE0Sjn28OLpfYOoxw0bScq6tvZOZoieOy+qMZOV0EIN/5 Blsf/YH2EruTa30BiEplVg== =uP1A -----END PGP SIGNATURE----- --ptgiukr3w63nhqco-- From owner-freebsd-current@freebsd.org Sun May 27 22:06:26 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 34133EEE505 for ; Sun, 27 May 2018 22:06:26 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7954709C8 for ; Sun, 27 May 2018 22:06:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fN3no-000OTP-Va; Mon, 28 May 2018 01:06:12 +0300 Date: Mon, 28 May 2018 01:06:12 +0300 From: Slawa Olhovchenkov To: Kirill Ponomarev Cc: Alexander Leidinger , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180527220612.GK1926@zxy.spb.ru> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180527194159.v54ox3vlthpuvx4q@jo> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 27 May 2018 22:06:26 -0000 On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: > On 05/22, Slawa Olhovchenkov wrote: > > > It has been a while since I tried Karl's patch the last time, and I > > > stopped because it didn't apply to -current anymore at some point. > > > Will what is provided right now in the patch work on -current? > > > > I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g > > I am don't know how to have two distinct patch (for stable and current) in one review. > > I'm experiencing these issues sporadically as well, would you mind > to publish this patch for fresh current? Week ago I am adopt and publish patch to fresh current and stable, is adopt need again? From owner-freebsd-current@freebsd.org Mon May 28 03:26: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 9FFA4EF6551 for ; Mon, 28 May 2018 03:26:54 +0000 (UTC) (envelope-from timur@bat.ru) Received: from mail-oi0-x22f.google.com (mail-oi0-x22f.google.com [IPv6:2607:f8b0:4003:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B4F279728 for ; Mon, 28 May 2018 03:26:53 +0000 (UTC) (envelope-from timur@bat.ru) Received: by mail-oi0-x22f.google.com with SMTP id e80-v6so9229646oig.11 for ; Sun, 27 May 2018 20:26:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=com-bat-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=5iCKZ1ObhioI9RdWWNbQJeoso1Ztz4/T1x0A7ANJ/WE=; b=zewC7tGokBo1QdXATZXTEK6qf7wV9yvJvXeZ3SOsyq2shQjwWl2GhYfjsCkej5rDKd VljL2BxbxH4qKuh6okhWit/Y7ysoJMs5xxVGkd8Wujy9c5zXAOyXVJxq0l0yqFkL3/JO 42mKccE7tcvmC/DNfrTkypftx0XNiH3DXRfO2wnayoEiuz26MLUCRp9WfiAaWWoivN3I 8Nx95laaFldqF31vamnR0nDnx0vv2COE6jOrCV3hkUWVtCKZ6ieV0yU48ai7oPSPcE6f hkHwTNhFBRtm6nFxmr2O08M6sWZH777FTAKnOfLUKEvuU4BPWbCck8p+JVbnLZHIdlk9 PQfA== 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=5iCKZ1ObhioI9RdWWNbQJeoso1Ztz4/T1x0A7ANJ/WE=; b=Pdo/xzKIVMOOtLuiX8eSDu0xIeEyssfyYfBhOjkNXZfpwLDgh6BwyRpDfEBGuWGRVA rzZZizQrpaGL81a8EmYfRRxFqF6nt5xrprtQeRuUtYTZorF4OnmhFC/z6bClvwSYByNd RZoBcLSvq3byx/3/C7AlyUXxdml470w50HxvsZm6syByQ716hQaVpBzGTEIH35gOf9tb NZ2xaPJ02LDOUkRcPX9aP8f8yxdKgylTfoMHoOP5Y319c366gOByccJkolHb3nWwKtad vo7BwfQ31xbiM3Rq04EsfbL1WD/S1VzVVBGTKWE8n8Llue5FRBJq9cw/OtCmt1ZWmWfA wozA== X-Gm-Message-State: ALKqPwfHc8sGJRUKQzEG63R9iNB8N3LclPUzjkLuqO+p0S1WZD6wI7QC eKhwfhD81rIArht6qd4rLNndX3Fs2Cpe67w+q2q3VsWUZzY= X-Google-Smtp-Source: ADUXVKISXT1yLR3MTI6YRavHYHME7ccoVF9u+Sm2WZ4BEEn81cLDnxTBPjV/j8NjrB5JDJVXkJRqCgOVFo6QcBKc2tA= X-Received: by 2002:aca:72d3:: with SMTP id p202-v6mr5966105oic.278.1527478012795; Sun, 27 May 2018 20:26:52 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a4a:1c2:0:0:0:0:0 with HTTP; Sun, 27 May 2018 20:26:22 -0700 (PDT) From: "Timur I. Bakeyev" Date: Mon, 28 May 2018 05:26:22 +0200 Message-ID: Subject: Odd w/who behavior for the last 12 years To: FreeBSD Current , Ed Schouten , Robert Watson , Alan Jude , Michal Mertl Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 03:26:54 -0000 Hi all! Recently I was trying to fix UTMP logging support in Samba, which supposed to add login entries for all authenticated Samba sessions, writing down user, session ID and remote host into the UTMP database(s). It used to work with Samba 3.x and FreeBSD 6/7, but got broken since then, apparently. Fixing Samba code to support "new" utmpx.h API was easy, but, despite that I couldn't see the active session in the "w" and "who" output. Still, "last" was showing the session normally: timur smb/3863840071 test-server1.local Fri May 25 14:20 - 14:37 (00:17) Quick look into the source code brought me to this 12 y.o. commit: https://svnweb.freebsd.org/base?view=revision&revision=155875 > In wall and who, check that the utmp entry isn't stalled, as it is done in w. > Apparently with the new pts code stalled entries are printed, when they are > not with the BSD ptys. > > Submitted by: Michal Mertl > > That can be tracked down to the https://docs.freebsd.org/cgi/getmsg.cgi?fetch=822832+0+/usr/local/www/mailindex/archive/2006/freebsd-current/20060205.freebsd-current While for the "wall" this patch has sense, it's quite broken for the "who"(and similar broken "fix" exists for "w"). First of all, both of those programs supposed to show information about ALL active sessions on the given machine. From the top of my head, besides "ssh" and other programs, that allocate ptys there is a bunch of other programs that write their sessions into UTMP, namely: xdm/gdm, vsftpd(and probably few other FTPDs), gnome-terminal(I wrote the BSD* code in gnome-pty-helper) and Samba. I'm pretty sure I miss some other software that also stores session info into UTMP, but I hope my point is clear. Next, while in 2006 ptmx/pts was pretty flanky, there was a large work done by Rober Watson ( https://docs.freebsd.org/cgi/getmsg.cgi?fetch=324362+0+archive/2007/freebsd-current/20071209.freebsd-current) and Ed Schouten ( https://docs.freebsd.org/cgi/getmsg.cgi?fetch=22996+0+archive/2008/freebsd-current/20080727.freebsd-current) that should fix the issues with ghost ptys. So I propose to remove the said patch(or make it verify only "pts/" devices). any objections? With regards, Timur Bakeyev. From owner-freebsd-current@freebsd.org Mon May 28 05:53: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 62B40EFA4E9 for ; Mon, 28 May 2018 05:53:04 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) Received: from mail2.mands.hu (mail2.mands.hu [93.189.114.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.mands.hu", Issuer "e-Szigno SSL CA 2014" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C61077D802; Mon, 28 May 2018 05:53:03 +0000 (UTC) (envelope-from Krasznai.Andras@mands.hu) From: =?utf-8?B?TSZTIC0gS3Jhc3puYWkgQW5kcsOhcw==?= To: Bryan Drewery , Mark Millard , FreeBSD Current CC: "Cy.Schubert@cschubert.com" , "O. Hartmann" Subject: RE: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh Thread-Topic: Another recent WITH_META_MODE= gotcha ": handling svn commit: r334008 - head/bin/sh Thread-Index: AQHT85CWy0NxEI2nikGrjACNHS43+qRAMcmggABRn4CABCR08A== Date: Mon, 28 May 2018 05:52:54 +0000 Message-ID: <5451ff189efd47bf9ed783999aced87c@MSEXCH13.mands.hu> References: <2E8F4907-F2AD-4EAD-A78F-E3236E516C8B@yahoo.com> <0f2dd2ac-009a-4298-1007-2e4a7766b546@FreeBSD.org> In-Reply-To: Accept-Language: en-US, hu-HU Content-Language: hu-HU X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [192.168.6.59] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 05:53:04 -0000 SGkNCg0KSSB1c2UgbWV0YSBtb2RlIGFuZCBjY2FjaGUgZm9yIGNvbXBpbGUuDQoNCkkgaGFkIFdJ VEhPVVRfUkVTQ1VFPSBpbiAvZXRjL3NyYy5jb25mLg0KDQpUaGVuIEkgcmVuYW1lZCAodGhhdGlz IHByYWN0aWNhbGx5IHJlbW92ZWQpIC9ldGMvc3JjLmNvbmYsIGFuZCByZW1vdmVkIHRoZSBLRVJO Q09ORj1teWtlcm5lbCBmcm9tIG1ha2UuY29uZiB0byBjb21waWxlIEdFTkVSSUMuIA0KDQpBZnRl ciB0aGlzIEkgZm91bmQgdGhlIGVycm9yIGRlc2NyaWJlZC4gDQoNCk4uQi4gSSB3ZW50IGJhY2sg dG8gbXkgb3JpZ2luYWwgc2V0dXAgKHNyYy5jb25mIHdpdGggV0lUSE9VVF9SRVNDVUUgYW5kIG15 a2VybmVsIGFzIEtFUk5DT05GKSBhbmQgZ290IHRoZSBzYW1lLiANCg0KVGhlIG5leHQgdGhpbmcg SSB3aWxsIHRlc3QgY29tcGlsaW5nIHdpdGhvdXQgbWV0YSBtb2RlIGEgR0VORVJJQyBrZXJuZWwu DQoNCnJnZHMNCg0KQW5kcsOhcyBLcmFzem5haQ0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0t LQ0KRnJvbTogQnJ5YW4gRHJld2VyeSBbbWFpbHRvOmJkcmV3ZXJ5QEZyZWVCU0Qub3JnXSANClNl bnQ6IEZyaWRheSwgTWF5IDI1LCAyMDE4IDY6MzMgUE0NClRvOiBNJlMgLSBLcmFzem5haSBBbmRy w6FzOyBNYXJrIE1pbGxhcmQ7IEZyZWVCU0QgQ3VycmVudA0KQ2M6IEN5LlNjaHViZXJ0QGNzY2h1 YmVydC5jb207IE8uIEhhcnRtYW5uDQpTdWJqZWN0OiBSZTogQW5vdGhlciByZWNlbnQgV0lUSF9N RVRBX01PREU9IGdvdGNoYSAiOiBoYW5kbGluZyBzdm4gY29tbWl0OiByMzM0MDA4IC0gaGVhZC9i aW4vc2gNCg0KT24gNS8yNS8yMDE4IDI6NDkgQU0sIE0mUyAtIEtyYXN6bmFpIEFuZHLDoXMgd3Jv dGU6DQo+IEhpDQo+IA0KPiBJIGZvdW5kIGFub3RoZXIgcHJvYmxlbSB3aXRoIGNvbXBpbGluZyBG cmVlQlNELUNVUlJFTlQNCj4gDQo+IHdoZW4gSSB0cmllZCB0byBjb21waWxlIEdFTkVSSUMgaW5z dGVhZCBvZiBteSBjdXN0b20gSSBydW4gaW50byB0aGUgZm9sbG93aW5nOg0KPiANCj4gbWFrZSBp bnN0YWxsd29ybGQgZmFpbHMgd2l0aA0KPiANCj4gL2Jpbi9zaDogL3Vzci9vYmovdXNyL3NyYy9h bWQ2NC5hbWQ2NC9yZXNjdWUvcmVzY3VlL3Jlc2N1ZTogbm90IGZvdW5kIA0KPiByZXNjdWUvc2gg Y2hlY2sgZmFpbGVkLCBpbnN0YWxsYXRpb24gYWJvcnRlZC4NCj4gDQo+IEkgdXNlZCBvcmlnaW5h bGx5IGEgY3VzdG9taXplZCBzcmMuY29uZiB3aGljaCAtIGFtb25nIG90aGVycyAtIHNwZWNpZmll cyBXSVRIT1VUX1JFU0NVRS4NCj4gV2hlbiB0cnlpbmcgdG8gY29tcGlsZSBHRU5FUklDIEkgcmVt b3ZlZCBzcmMuY29uZiBhbmQgSSB0aG91Z2h0IEkgd291bGQgZ2V0IGEgY29tcGxldGUgRnJlZUJT RC1DVVJSRU5UIHdpdGggR0VORVJJQywgd2l0aCByZXNjdWUgZmlsZXMsIGV0Yy4gDQo+IA0KDQpV bmNsZWFyIHRvIG1lLiBZb3UgZGlkIGJ1aWxkd29ybGQgd2l0aCBXSVRIT1VUX1JFU0NVRT15ZXMg c2V0IGFuZCB0aGVuIHJlbW92ZWQgJ1dJVEhPVVRfUkVTQ1VFJyBmcm9tIHlvdXIgc3JjLmNvbmYg KGJ5IHJlbW92aW5nIHNyYy5jb25mKSwgYW5kIHRoZW4gZGlkIGJ1aWxkd29ybGQgYW5kIHRoZW4g aW5zdGFsbHdvcmxkIGFuZCBoaXQgdGhpcyBpc3N1ZT8gQWxsIHdpdGggV0lUSF9NRVRBX01PREU9 eWVzPyBPciBkaWQgeW91IGRpc2FibGUgTUVUQV9NT0RFIGF0IHNvbWUgcG9pbnQ/DQoNCj4gVGhl IHNvdXJjZSB0cmVlIGlzIGF0IHIzMzQyMDANCj4gDQo+IA0KPiBiZXN0IHJlZ2FyZHMNCj4gDQo+ IEFuZHLDoXMgS3Jhc3puYWkNCg0KDQotLQ0KUmVnYXJkcywNCkJyeWFuIERyZXdlcnkNCg0K From owner-freebsd-current@freebsd.org Mon May 28 07:02: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 F2E3DEFE977 for ; Mon, 28 May 2018 07:02:23 +0000 (UTC) (envelope-from Alexander@leidinger.net) Received: from mailgate.Leidinger.net (mailgate.leidinger.net [IPv6:2a00:1828:2000:375::1:5]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 678647FC0B for ; Mon, 28 May 2018 07:02:23 +0000 (UTC) (envelope-from Alexander@leidinger.net) Date: Mon, 28 May 2018 09:02:01 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=leidinger.net; s=outgoing-alex; t=1527490941; bh=97P31DUBbTrAz8xgHUVeiQYOWOX2Xo7BOulHEdCS/c0=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=PJJhlSynFNnITrwxL3YLysym3kw2U08jsJfO5fzm/aGDj0XwY5fBHuaGbybw/Xoji UY9y0pkIk4B+B4Z/o5DQ27+YzSlBa8vrynpxzfZNQi7TEIjkDr0SeCiF1YFvxellJZ vaC9WJJ6YVXORglzRTyDWpT8P+tuFV2/cODa2lWkkX9sz+BXUtMNM7U7ZdYFrU0ITX 9eslL/R6qnblGXvlRec1ilanPGCQ1aZME3fVnKSTRxPg3nqujV4I7CMX/5DOZXlB/i odczvgeAo2aik3vNt2xT4DtlWzHXurtKj5Q83jg+VFX4TAvejOBNNSfG3vgeK56a3R P+2jlpfUfg+Yg== Message-ID: <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> From: Alexander Leidinger To: Slawa Olhovchenkov Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> In-Reply-To: <20180527220612.GK1926@zxy.spb.ru> User-Agent: Horde Application Framework 5 Content-Type: multipart/signed; boundary="=_dyVR2pjXgIq_aY-n7Njz_BJ"; protocol="application/pgp-signature"; micalg=pgp-sha1 MIME-Version: 1.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 07:02:24 -0000 This message is in MIME format and has been PGP signed. --=_dyVR2pjXgIq_aY-n7Njz_BJ Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Quoting Slawa Olhovchenkov (from Mon, 28 May 2018=20=20 01:06:12=20+0300): > On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: > >> On 05/22, Slawa Olhovchenkov wrote: >> > > It has been a while since I tried Karl's patch the last time, and I >> > > stopped because it didn't apply to -current anymore at some point. >> > > Will what is provided right now in the patch work on -current? >> > >> > I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g >> > I am don't know how to have two distinct patch (for stable and=20=20 >>=20current) in one review. >> >> I'm experiencing these issues sporadically as well, would you mind >> to publish this patch for fresh current? > > Week ago I am adopt and publish patch to fresh current and stable, is > adopt need again? I applied the patch in the review yesterday to rev 333966, it applied=20=20 OK=20(with some fuzz). I will try to reproduce my issue with the patch. Some thoughts I had after looking a little bit at the output of top...=20= =20 half=20of the RAM of my machine is in use, the other half is listed as=20= =20 free.=20Swap gets used while there is plenty of free RAM. I have NUMA in=20= =20 my=20kernel (it's 2 socket Xeon system). I don't see any NUMA specific=20= =20 code=20in the diff (and I don't expect something there), but could it be=20= =20 that=20some NUMA related behavior comes into play here too? Does it make=20= =20 sense=20to try without NUMA in the kernel? Bye, Alexander. --=20 http://www.Leidinger.net=20Alexander@Leidinger.net: PGP 0x8F31830F9F2772BF http://www.FreeBSD.org netchild@FreeBSD.org : PGP 0x8F31830F9F2772BF --=_dyVR2pjXgIq_aY-n7Njz_BJ Content-Type: application/pgp-signature Content-Description: Digitale PGP-Signatur Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJbC6lpAAoJEKrxQhqFIICEanUP/0kmlwJK0yfZqwtb94EfBjYZ k9i5c9Ht1MNKdum/M+YfsIsQFZ0g5ilacZMtue0po0qNXQIR27MTp+WqUygPb3kk 3w+JgE2gi75b37s/1X+agOUPqGpIYOsLSpvFAxCNsy45aPNJTY22r+s8si1qrKY9 zjV48YF3jsEUxeXQ5augg77bdKq+Al8ltgVzdxLDwHLq6lNtmrV4f9m+/k356nya s5jyKSB2edH+vfBRKsu40R6Mgnb7wiAo8PUN5lmAoH2tYiWcg0aGfKgceRlNXAWG o0iNw8hQaBQQSwc8GuY0oczDY1i121YOUJr3NqpK4bB6vhh2hwNkwRijX5Iii2Cf 658aq/gNf//oTLv1t6fItTyr0MAjO4W4YVOBvsJxs9vmkaisqMLWb9hdHBgwaxEl jbfmgtYsx6AhCBnUtSufYONbjCudLGZsg2XSDPSTfib5HDSWV0JcYpuSCnJ0A3zq VwYisnGP3R9NBhMfblaqjkaYSPj1iJuYAeRVtzyQS7eU6IPlRYhVJkuU6Ubkbhwu +opiC4B6xhPPCWOkZPRupJ/QiIU48oKT3IKcPXdbpYkd4LIeh0my3kb6BfpNPS/r FpBHV3oYpKl9SN4PJOivfob94bUxujSAcr6kK/BoNFmX43eVajYXPiOstxAIJ6R6 KuSSa57940QkwNBsDEUz =kzV7 -----END PGP SIGNATURE----- --=_dyVR2pjXgIq_aY-n7Njz_BJ-- From owner-freebsd-current@freebsd.org Mon May 28 08:10: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 9069EF71DBE for ; Mon, 28 May 2018 08:10:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 25CBC8237B for ; Mon, 28 May 2018 08:10:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1fNDEs-0004hH-Ft; Mon, 28 May 2018 11:10:46 +0300 Date: Mon, 28 May 2018 11:10:46 +0300 From: Slawa Olhovchenkov To: Alexander Leidinger Cc: Kirill Ponomarev , freebsd-current@freebsd.org Subject: Re: Deadlocks / hangs in ZFS Message-ID: <20180528081046.GL1926@zxy.spb.ru> References: <20180522101749.Horde.Wxz9gSxx1xArxkYMQqTL0iZ@webmail.leidinger.net> <20180522122924.GC1954@zxy.spb.ru> <20180522161632.Horde.ROSnBoZixBoE9ZBGp5VBQgZ@webmail.leidinger.net> <20180522144055.GD1954@zxy.spb.ru> <20180527194159.v54ox3vlthpuvx4q@jo> <20180527220612.GK1926@zxy.spb.ru> <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180528090201.Horde._E4JZcuEaZHfj_BNzWjci2O@webmail.leidinger.net> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 08:10:52 -0000 On Mon, May 28, 2018 at 09:02:01AM +0200, Alexander Leidinger wrote: > Quoting Slawa Olhovchenkov (from Mon, 28 May 2018 > 01:06:12 +0300): > > > On Sun, May 27, 2018 at 09:41:59PM +0200, Kirill Ponomarev wrote: > > > >> On 05/22, Slawa Olhovchenkov wrote: > >> > > It has been a while since I tried Karl's patch the last time, and I > >> > > stopped because it didn't apply to -current anymore at some point. > >> > > Will what is provided right now in the patch work on -current? > >> > > >> > I am mean yes, after s/vm_cnt.v_free_count/vm_free_count()/g > >> > I am don't know how to have two distinct patch (for stable and > >> current) in one review. > >> > >> I'm experiencing these issues sporadically as well, would you mind > >> to publish this patch for fresh current? > > > > Week ago I am adopt and publish patch to fresh current and stable, is > > adopt need again? > > I applied the patch in the review yesterday to rev 333966, it applied > OK (with some fuzz). I will try to reproduce my issue with the patch. > > Some thoughts I had after looking a little bit at the output of top... > half of the RAM of my machine is in use, the other half is listed as > free. Swap gets used while there is plenty of free RAM. I have NUMA in > my kernel (it's 2 socket Xeon system). I don't see any NUMA specific > code in the diff (and I don't expect something there), but could it be > that some NUMA related behavior comes into play here too? Does it make > sense to try without NUMA in the kernel? Good question, NUMA in FreeBSD too new, nobody know it. For Linux, some effectt exists: exhaust all memory in one NUMA domain can cause memory deficit (swap/allocation failure/etc) simultaneous with many free memory in other NUMA domain. Yes, try w/o NUMA, this is may be interesting for NUMA developers. From owner-freebsd-current@freebsd.org Mon May 28 22:19: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 BA0ABEF96FA for ; Mon, 28 May 2018 22:19:10 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.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 547808EADC for ; Mon, 28 May 2018 22:19:10 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id 138BFEF96F8; Mon, 28 May 2018 22:19: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 00E21EF96F6 for ; Mon, 28 May 2018 22:19:09 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 8F7C88EAD6 for ; Mon, 28 May 2018 22:19:09 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1fNPps-0005qw-05 for current@freebsd.org; Mon, 28 May 2018 23:37:48 +0200 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1fNPpr-000324-U0 for current@freebsd.org; Mon, 28 May 2018 23:37:47 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); for ; Mon, 28 May 2018 21:37:47 GMT From: "Jeffrey Bouquet" To: "current" Subject: how to browse svnweb source? Date: Mon, 28 May 2018 14:37:47 -0700 (PDT) X-Mailer: RMM6 Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 22:19:10 -0000 Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed sequenti= al source as for example xx1966 on april 3 .... xx2040 on april 4 this year, i= s not loading in the browser. It was informative to read color coded the source backport= ed to v10 v11 vs new, and new drivers coming into play. I can find NOWHERE except freshsource.org which has the ports updates interspersed which makes the in= formation too time consuming. As an example, 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c]=20 on 5-10-2017 adding the -C and --capacity options... ....................................... What was educational to browse now is found at ???????? ......................................= From owner-freebsd-current@freebsd.org Mon May 28 23:04: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 0CE34EFD12E for ; Mon, 28 May 2018 23:04:19 +0000 (UTC) (envelope-from sbruno@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 80F3C68E75 for ; Mon, 28 May 2018 23:04:18 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3CBABEFD12A; Mon, 28 May 2018 23:04:18 +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 00424EFD129 for ; Mon, 28 May 2018 23:04:17 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (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 7F60A68E73 for ; Mon, 28 May 2018 23:04:16 +0000 (UTC) (envelope-from sbruno@freebsd.org) Received: from [192.168.0.6] (67-0-245-183.albq.qwest.net [67.0.245.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 8C934192888; Mon, 28 May 2018 15:14:44 +0000 (UTC) Subject: Re: how to browse svnweb source? To: Jeffrey Bouquet , current References: From: Sean Bruno Openpgp: preference=signencrypt Autocrypt: addr=sbruno@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFk+0UEBCADaf4bgxxKvMOhRV5NPoGWRCCGm49d6+1VFNlQ77WsY/+Zvf95TPULdRlnG w648KfxWt7+O3kdKhdRwnqlXWC7zA2Qt0dRE1yIqOGJ4jp4INvp/bcxWzgr0aoKOjrlnfxRV bh+s0rzdZt6TsNL3cVYxkC8oezjaUkHdW4mFJU249U1QJogkF8g0FeKNfEcjEkwJNX6lQJH+ EzCWT0NCk6J+Xyo+zOOljxPp1OUfdvZi3ulkU/qTZstGVWxFVsP8xQklV/y3AFcbIYx6iGJ4 5L7WuB0IWhO7Z4yHENr8wFaNYwpod9i4egX2BugbrM8pOfhN2/qqdeG1L5LMtXw3yyAhABEB AAHNN1NlYW4gQnJ1bm8gKEZyZWVCU0QgRGV2ZWxvcGVyIEtleSkgPHNicnVub0BmcmVlYnNk Lm9yZz7CwJQEEwEKAD4WIQToxOn4gDUE4eP0ujS95PX+ibX8tgUCWT7RQQIbAwUJBaOagAUL CQgHAwUVCgkICwUWAwIBAAIeAQIXgAAKCRC95PX+ibX8ttKTCACFKzRc56EBAlVotq02EjZP SfX+unlk6AuPBzShxqRxeK+bGYVCigrYd1M8nnskv0dEiZ5iYeND9HIxbpEyopqgpVTibA7w gBXaZ7SOEhNX1wXwg14JrralfSmPFMYni+sWegPMX/zwfAsn1z4mG1Nn44Xqo3o7CfpkMPy6 M5Bow2IDzIhEYISLR+urxs74/aHU35PLtBSDtu18914SEMDdva27MARN8mbeCDbuJVfGCPWy YHuy2t+9u2Zn5Dd+t3sBXLM9gpeaMm+4x6TNPpESygbVdh4tDdjVZ9DK/bWFg0kMgfZoaq6J l0jNsQXrZV3bzYNFbVw04pFcvA2GIJ7xzsBNBFk+0UEBCADIXBmQOaKMHGbc9vwjhV4Oj5aZ DdhNedn12FVeTdOXJvuTOusgxS29lla0RenHGDsgD08UiFpasBXWq/E+BhQ19d+iRbLLR17O KKc1ZGefoVbLARLXD68J5j4XAyK+6k2KqBLlqzAEpHTzsksM9naARkVXiEVcrt6ciw0FSm8n kuK3gDKKe93XfzfP+TQdbvvzJc7Fa+appLbXz61TM1aikaQlda8bWubDegwXbuoJdB34xU1m yjr/N4o+raL0x7QrzdH+wwgrTTo+H4S2c1972Skt5K5tbxLowfHicRl23V8itVQr3sBtlX4+ 66q+Apm7+R36bUS/k+G45Sp6iPpxABEBAAHCwHwEGAEKACYWIQToxOn4gDUE4eP0ujS95PX+ ibX8tgUCWT7RQQIbDAUJBaOagAAKCRC95PX+ibX8trrIB/9Pljqt/JGamD9tx4dOVmxSyFg9 z2xzgklTLuDgS73MM120mM7ao9AQUeWiSle/H0UCK7xPOzC/aeUC4oygDQKAfkkNbCNTo3+A qDjBRA8qx0e9a/QjDL+RFgD4L5kLT4tToY8T8HaBp8h03LBfk510IaI8oL/Jg7vpM3PDtJMW tUi2H+yNFmL3NfM2oBToWKLFsoP54f/eeeImrNnrlLjLHPzqS+/9apgYqX2Jwiv3tHBc4FTO GuY8VvF7BpixJs8Pc2RUuCfSyodrp1YG1kRGlXAH0cqwwr0Zmk4+7dZvtVQMCl6kS6q1+84q JwtItxS2eXSEA4NO0sQ3BXUywANh Message-ID: <6a212103-830c-54ea-1223-1dcc48ad0ffc@freebsd.org> Date: Mon, 28 May 2018 17:04:11 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="g92GsGz9YmlvKIbhcouQZSFeNh2kWWH6W" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 28 May 2018 23:04:19 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --g92GsGz9YmlvKIbhcouQZSFeNh2kWWH6W Content-Type: multipart/mixed; boundary="J99rJCvXp93YvUxyoRk0dc74I1Ez390T5"; protected-headers="v1" From: Sean Bruno To: Jeffrey Bouquet , current Message-ID: <6a212103-830c-54ea-1223-1dcc48ad0ffc@freebsd.org> Subject: Re: how to browse svnweb source? References: In-Reply-To: --J99rJCvXp93YvUxyoRk0dc74I1Ez390T5 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 05/28/18 15:37, Jeffrey Bouquet wrote: > Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed sequ= ential > source as for example xx1966 on april 3 .... xx2040 on april 4 this yea= r, is not loading > in the browser. It was informative to read color coded the source back= ported to v10 > v11 vs new, and new drivers coming into play. I can find NOWHERE excep= t > freshsource.org which has the ports updates interspersed which makes th= e information > too time consuming. As an example, >=20 > 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c] = > on 5-10-2017 adding the -C and --capacity options... >=20 > ....................................... > What was educational to browse now is found at ???????? > ...................................... > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 https://svnweb.freebsd.org/base/head/ ? sean --J99rJCvXp93YvUxyoRk0dc74I1Ez390T5-- --g92GsGz9YmlvKIbhcouQZSFeNh2kWWH6W Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEE6MTp+IA1BOHj9Lo0veT1/om1/LYFAlsMiutfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEU4 QzRFOUY4ODAzNTA0RTFFM0Y0QkEzNEJERTRGNUZFODlCNUZDQjYACgkQveT1/om1 /La4uAgAhoFoJ6olyLF1v3cvzs0XgTOPdgV4i8+HKj5Xmkl3sHgtfoQpSV/0rqOu IYt2gBKS5dC9ZxAxIV6wRvBtChq7s+NVeHBuv7oRw8VBFaGFp+HA7S9hzr1/2XXY fRNvTyCmc8NyeoCofrns4zhNsd8StK5fJwYrKhsOKn1AD3hp3sHCk/K5l2x3vNab qFQnRR6O4kYzTitMAYMDBuKDE94+xxWRxpmx6VCabcIXcTArexa2PogdbGgQxRsQ iZIWw3N50Q5Xj0DKev4gVpi5MuPo/Sl8HOuM8sCRph4TjWHmZLcrF9gBfFqyQe2D 0wU+sJqv+D1m5lNFtn5lu3kURHt+lw== =9vUf -----END PGP SIGNATURE----- --g92GsGz9YmlvKIbhcouQZSFeNh2kWWH6W-- From owner-freebsd-current@freebsd.org Tue May 29 01:06: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 8DC1AF7261F for ; Tue, 29 May 2018 01:06:10 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.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 2AEF76D2B9 for ; Tue, 29 May 2018 01:06:10 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id D5AABF7261E; Tue, 29 May 2018 01:06: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 C41A5F7261D for ; Tue, 29 May 2018 01:06:09 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 6141F6D2B7; Tue, 29 May 2018 01:06:09 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1fNT5T-0002C4-BS; Tue, 29 May 2018 03:06:07 +0200 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1fNT5T-0005fI-A8; Tue, 29 May 2018 03:06:07 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Tue, 29 May 2018 01:06:07 GMT From: "Jeffrey Bouquet" To: "Sean Bruno" CC: "current" Subject: Re: how to browse svnweb source? Date: Mon, 28 May 2018 18:06:07 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: <6a212103-830c-54ea-1223-1dcc48ad0ffc@freebsd.org> Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 01:06:10 -0000 On Mon, 28 May 2018 17:04:11 -0600, Sean Bruno wrote: >=20 >=20 > On 05/28/18 15:37, Jeffrey Bouquet wrote: > > Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed sequ= ential > > source as for example xx1966 on april 3 .... xx2040 on april 4 this yea= r, is not loading > > in the browser. It was informative to read color coded the source back= ported to v10 > > v11 vs new, and new drivers coming into play. I can find NOWHERE except > > freshsource.org which has the ports updates interspersed which makes th= e information > > too time consuming. As an example, > >=20 > > 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c]= =20 > > on 5-10-2017 adding the -C and --capacity options... > >=20 > > ....................................... > > What was educational to browse now is found at ???????? > > ...................................... > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > >=20 >=20 >=20 > https://svnweb.freebsd.org/base/head/ >=20 > ? >=20 > sean I tried that url every which way, sorting the headings, etc, and onscreen would be at best, a description of the new source but not specifically which files were changed and their complete path. Nothing like the url mentioned = above at .de in the latter's overview.=20= From owner-freebsd-current@freebsd.org Tue May 29 06:25: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 5A14FEF1B1B for ; Tue, 29 May 2018 06:25:35 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B02F7791F6 for ; Tue, 29 May 2018 06:25:34 +0000 (UTC) (envelope-from joh.hendriks@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id i12-v6so23420651wrc.4 for ; Mon, 28 May 2018 23:25:34 -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=fbxpSh3Z+SZZyyvmeSYfoRkwbJlesfTZo2aoU/IEzAE=; b=Cnl7tgJm7DSs6kJGJET2f+1emf+kqNhjnENdR2mEw6EW4iqlYkYfxs+kLKbkdoGeG4 9rV2iaBPYrNr8jrWE8J0z62WywP2AthFuiqIaAgAIzJ+RRJ+48ErvK9cKCX1gcfLN/ce QHC7NQkQ4kQ3Ews4EYcvTDXrdasRSeDWjt9l0YkBwOLDSov2kri8ewtPHSRVRR5LmFw8 fmLNYlPJAfx5OTRNxNbVYZaB8KzAcknZoZtS4eAyhH+jWgJFXp4ObGqzZgNeb2vIxf3x xeHKRyjpEwNF/AJW4/xxbAgwVvEmo423vb1N47hF46EoQ1y/VQryATTj9+e2ilC20tCM bzAA== 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=fbxpSh3Z+SZZyyvmeSYfoRkwbJlesfTZo2aoU/IEzAE=; b=tI8Ia8n/qZsyqDrLYrzLR1z2gtW2UGfmYwcaPGUwbnqwYbOjr4Mb2wiBR9iX3mZUCZ cgEh8tLD+ru3VtWV0MTZToJpAySZYpH2dn4JP0KKfGv777Emr9iLmjhdnD4/A8yURxrm O1vLG+ir2tiizfNS7PyaywZ5mBhPTjd+g4nqxFRKXHsLeHv1sSB5p7XWeAOxPjYld8j4 GpV1mhaXPYmHz/Uwa3FIHxPlRDAYMzASGYlRFRDBmfnWAFGm4h2CiFsWV1YE0YByIZXw hDpgJvGFqC65aB0nCftBMBHO4bopIcsvTCY7+XLwvLFfY6PLD0WC/v3pkDBnPlfbUWD5 evNg== X-Gm-Message-State: ALKqPwcDJnU19ZRdZimpaSZJ7/W7VtaoKzsIJiiVjj3ccu/HfKyO4Rb2 sS8pZXLkWCtX1D4wfTu96zVIcNSXAaOGMmvW/Yo= X-Google-Smtp-Source: ADUXVKIze2tbVvKVfAGa0yzj/HNPUdJ4m2kKJP0W5ZffbbLUl+QX096+wcT4X5/heC2z/rEHnywWh2RR2La4APQwpwU= X-Received: by 2002:adf:a032:: with SMTP id k47-v6mr5491704wrk.202.1527575132754; Mon, 28 May 2018 23:25:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johan Hendriks Date: Tue, 29 May 2018 08:25:22 +0200 Message-ID: Subject: Re: how to browse svnweb source? To: Jeffrey Bouquet Cc: FreeBSD Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 06:25:35 -0000 Op di 29 mei 2018 00:28 schreef Jeffrey Bouquet : > Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed > sequential > source as for example xx1966 on april 3 .... xx2040 on april 4 this year, > is not loading > in the browser. It was informative to read color coded the source > backported to v10 > v11 vs new, and new drivers coming into play. I can find NOWHERE except > freshsource.org which has the ports updates interspersed which makes the > information > too time consuming. As an example, > > 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c] > on 5-10-2017 adding the -C and --capacity options... > > ....................................... > What was educational to browse now is found at ???????? > ...................................... > _______________________________________________ > 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" > You can try www.freshbsd.org it has all the BSD's covered. You can select the branch you want to watch. > From owner-freebsd-current@freebsd.org Tue May 29 06:30: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 BBE81EF1F03 for ; Tue, 29 May 2018 06:30:06 +0000 (UTC) (envelope-from peter@rulingia.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 4C7867949B for ; Tue, 29 May 2018 06:30:06 +0000 (UTC) (envelope-from peter@rulingia.com) Received: by mailman.ysv.freebsd.org (Postfix) id 02E6BEF1F01; Tue, 29 May 2018 06:30: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 D4A84EF1F00 for ; Tue, 29 May 2018 06:30:05 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vtr.rulingia.com (vtr.rulingia.com [IPv6:2001:19f0:5801:ebe:5400:1ff:fe53:30fd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vtr.rulingia.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2560B7949A for ; Tue, 29 May 2018 06:30:04 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from server.rulingia.com (ppp59-167-167-3.static.internode.on.net [59.167.167.3]) by vtr.rulingia.com (8.15.2/8.15.2) with ESMTPS id w4T6Ts7h007590 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 29 May 2018 16:30:00 +1000 (AEST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.15.2/8.15.2) with ESMTPS id w4T6TmXV077751 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 29 May 2018 16:29:48 +1000 (AEST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.15.2/8.15.2/Submit) id w4T6TmaJ077750; Tue, 29 May 2018 16:29:48 +1000 (AEST) (envelope-from peter) Date: Tue, 29 May 2018 16:29:48 +1000 From: Peter Jeremy To: Jeffrey Bouquet Cc: current Subject: Re: how to browse svnweb source? Message-ID: <20180529062948.GG96747@server.rulingia.com> References: <6a212103-830c-54ea-1223-1dcc48ad0ffc@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Y5rl02BVI9TCfPar" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 06:30:07 -0000 --Y5rl02BVI9TCfPar Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2018-May-28 18:06:07 -0700, Jeffrey Bouquet = wrote: >> > Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed seq= uential >> > source as for example xx1966 on april 3 .... xx2040 on april 4 this ye= ar, is not loading >> > in the browser. That site is not associated with the FreeBSD Project so you would need to discuss the absence of information on that site with whoever runs it. >I tried that url every which way, sorting the headings, etc, and onscreen >would be at best, a description of the new source but not specifically whi= ch >files were changed and their complete path. Nothing like the url mentioned= above at >.de in the latter's overview.=20 Without knowing what that site displayed, it's very difficult to know where (or if) svnweb provides the information. Given a known revision, you can check (eg) https://svnweb.freebsd.org/base?view=3Drevision&revision=3D333926 If you want a sequential list of commits, you might be better off with (eg) https://lists.freebsd.org/pipermail/svn-src-all/ --=20 Peter Jeremy --Y5rl02BVI9TCfPar Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7rKYbDBnHnTmXCJ+FqWXoOSiCzQFAlsM81xfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVF QjI5ODZDMzA2NzFFNzRFNjVDMjI3RTE2QTU5N0EwRTRBMjBCMzQACgkQFqWXoOSi CzS3HA/9FWEznGc3s8/ZnP+PA4Hnjz2mfLgGV2YjYWTsbVBtvTLQ7q6QTzHyu1hP rfmrEQ88t6OV1J4uVI8UTyn1682Fca8nw+yeolc74zezIvtUdmjQuLf4DXoemnIq Oa1M4tkIc0kuAukYm+89/wUF2i2J07AeNEMIpkCXYqnhnGleRSQkydc0B+MQysun 2a/GPrd1U6I0sstwPGfOrdM9TD+w5WjrCq7ckXTlM0xwnAWL5YGdae1eqTyyiOoG KPTc+saFYpQzkbT3rYb3/8TnwEOBYGMgdA5bTfpTQ3G5EYrMipzm9b4ddFTQyhFC rrSbUTjXoAgmjWt9QnCHv4lGkBB/NlvAOXts4gQuU2Qsuf/j0RX9K6e8xVjWkhQU PkbnaE3ZVI5qifapCnUiozbVhiiqZA4SER16rzNFVUjLc8kusQnB1iiqS84a5FKr TI1mC8uujZV6dH0Gra3hnQGmy5lBAFtFrti/ifRwzrRhUY4LS2q1sAg+1p7HEOxa pQkjrXIISm1xcj+EU/xQKm4r7fMMCWYTKRpUBHg5dJNy9Pz4cgvPaZ4jLxeJNeew ZeNaXjFKQkNvSSSZoVN/xDDcYRMdMywONGOyhPOWxVKYVpXYOuHMJL0EzrqvAAvD 5lrJDCYjopN0zVPvi5c/7u+GDnefl9qW4Z9rikNsbYediJ98I4g= =7mzX -----END PGP SIGNATURE----- --Y5rl02BVI9TCfPar-- From owner-freebsd-current@freebsd.org Tue May 29 08:41: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 01D49EFAC93 for ; Tue, 29 May 2018 08:41:40 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (tunnel7249-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8C43B7DC3B for ; Tue, 29 May 2018 08:41:38 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from Vincents-MacBook-Pro-2.local (unknown [89.192.2.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by unsane.co.uk (Postfix) with ESMTPSA id B4A6930034 for ; Tue, 29 May 2018 09:41:35 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=unsane.co.uk; s=251017; t=1527583298; bh=P9EmCTY3Qw8cVL+CW4H6Px8haqHNmM5mC4RqsYl1ID4=; h=Subject:To:References:From:Date:In-Reply-To; b=V2i5Ef84MhvAEY8EcymuM+d4uscV9oUur2+7mPOFN0oMQpuTVqOr9pIU3norpg735 TndP2O8if85ZiVGGnMvd9S8W2orZ8bDuALTWHpmlB+quewTMkZtLYwWFWiXtM4lrk2 2eAwmG7Yzrg0/o+4jnNNZefpCJ3CLJIIMhPI50Ec= Subject: Re: how to browse svnweb source? To: freebsd-current@freebsd.org References: From: Vincent Hoffman-Kazlauskas Openpgp: preference=signencrypt Autocrypt: addr=vince@unsane.co.uk; prefer-encrypt=mutual; keydata= xsDiBESPz78RBADybNTkAA4eQLuwYC1Qsn7qaDLzBvq2RmA0niwngigEPy/tLh9aF2zR85fL PTvxh9MyLzFZHc5RVO0tKM93CSRXjTo5xo2P1/YTopPyzTBB3eOB7uqJRi+suBnKPfXvkeW1 g5yo3pKINsqW0ed91lDwrQ1NofbIFkOOYnhQpccdiwCg0GF13Vk9Rz683bkSawFethAcVx8E AKGPTj6KfVmnhB8a3y0UeZ46LMfoZnjLF4ZDMtrZHY639zbZBJiKJ/M1B8z3GJgmRmOEXoW4 Mdoi0XaSkinIWmtdI+vhIfb/7ufFzujM0wEbEnpJ/mvTuSas6DG7MPMiJMavz3Hf/dVOX7Dd Ma+z03JKIHuMj8HVMFccjgFJLmteBADkdDBQin+YzgGuPs/Sf8KvVPVRDT5QJkHUEU/gcmSP YbPfmwC7tl1iXR9Gu4foQyk2UJJezCRUWggNScybcrLp2jQ0XWkw18uus/QC2ZCfW/f2vXg8 uL5W7cLGbeSKh3K0CFMbACmcrcMZk7JwW9a/VlAhmqOUk1MYJ1rR2ZZIp80mVmluY2VudCBI b2ZmbWFuIDx2aG9mZm1hbkBuYW1lcy5jby51az7CYAQTEQIAIAUCRI/PvwIbAwYLCQgHAwIE FQIIAwQWAgMBAh4BAheAAAoJEMQkmEPMfxC+ik0An0EFsHC1cTRRq+MgAWoM3WRvOeQFAJ9D 2GwjK6Zaiu6s+KaxeWh4yrk0Jc7BTQREj8/REAgA5AQP4RpCo/O9U/Zd4s0mArJpGQhAnYb8 2r+u3e/MyGK5hTH+ODAOZ1TeiPb75xYQ9QGOX+ygpCSDmDjG+MJyPivdZMuuwnhisYZPNuhE Tw/CdP5mekqPzZAvIqBi5q6Bdmz0tORu4L6y/zPnQ8qrkBnibK9AOKz1XkguOlzcIlfxpsOC AgTRWoOpW8oQtQl80Ik22prSExgKllBfq3/sRix28r86L51P5hHG7mlWtbv8txaLyihBO3aw mkTXLAk5IMgrlillkDvMYUsO7lOkwk54C3oq+lYarNJ4Ul7Wfyg1ufjCc8CynXrlgFMJ+wbg Uhk4lbidSuGRkT10yqlNrwAECwf/YA3W3eSNQIn6s5eBTR+Qocmp+11zTNQMwB3xRzKQFBBd UwTbFiyhxMS7+xJzEUzuhTOy/OI/QCto595C/68y53TU0fwII0e2XLRYDIWO1FqSCGyDMviO 1ixnSHMkXeIEPbalF9n+KB2ozX0OOxl3oA7wt/DmOq8nLNzCMOKHD6mJRnBAp0En9WYpnbSl nucjh2+Ry9XAK5HCZ9k1SWxFPCEvxv4nwhZnYFdm5O4M6MHw8T/viWIBa96yt2CTGP7gOz+s YKcjUTQ7UdtYFVguGW9uehvtqbCLv69clBCmooRYAmTkiupI8R1zIfKVDjllDONWoPZfCz2d LwHnLW/ZMsJJBBgRAgAJBQJEj8/RAhsMAAoJEMQkmEPMfxC+he0An3g4+nwMH9lsde9IFgQY TDhDySz9AKCZSsEaPlGPvj7Fd7c47Eh4Nt9j9w== Message-ID: Date: Tue, 29 May 2018 09:41:34 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 29 May 2018 08:41:40 -0000 On 29/05/2018 02:06, Jeffrey Bouquet wrote: > > > On Mon, 28 May 2018 17:04:11 -0600, Sean Bruno wrote: > >> >> >> On 05/28/18 15:37, Jeffrey Bouquet wrote: >>> Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed sequential >>> source as for example xx1966 on april 3 .... xx2040 on april 4 this year, is not loading >>> in the browser. It was informative to read color coded the source backported to v10 >>> v11 vs new, and new drivers coming into play. I can find NOWHERE except >>> freshsource.org which has the ports updates interspersed which makes the information >>> too time consuming. As an example, >>> >>> 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c] >>> on 5-10-2017 adding the -C and --capacity options... >>> >>> ....................................... >>> What was educational to browse now is found at ???????? >>> ...................................... >>> _______________________________________________ >>> 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" >>> >> >> >> https://svnweb.freebsd.org/base/head/ >> >> ? >> >> sean > > > I tried that url every which way, sorting the headings, etc, and onscreen > would be at best, a description of the new source but not specifically which > files were changed and their complete path. Nothing like the url mentioned above at > .de in the latter's overview. Possibly freshbsd.org? I follow the 11-STABLE branch using https://freshbsd.org/?branch=RELENG_11&project=freebsd Vince > _______________________________________________ > 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 May 29 09:10: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 8ADE0EFCA7B for ; Tue, 29 May 2018 09:10:34 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 2C3667EE5F for ; Tue, 29 May 2018 09:10:33 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.129] (helo=rmmprod07.runbox) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1fNaeF-0005gT-Bn; Tue, 29 May 2018 11:10:31 +0200 Received: from mail by rmmprod07.runbox with local (Exim 4.86_2) (envelope-from ) id 1fNaeF-00060X-AW; Tue, 29 May 2018 11:10:31 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Tue, 29 May 2018 09:10:31 GMT From: "Jeffrey Bouquet" To: "Vincent Hoffman-Kazlauskas" CC: "freebsd-current" Subject: Re: how to browse svnweb source? Date: Tue, 29 May 2018 02:10:31 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 09:10:34 -0000 On Tue, 29 May 2018 09:41:34 +0100, Vincent Hoffman-Kazlauskas wrote: >=20 >=20 > On 29/05/2018 02:06, Jeffrey Bouquet wrote: > >=20 > >=20 > > On Mon, 28 May 2018 17:04:11 -0600, Sean Bruno wro= te: > >=20 > >> > >> > >> On 05/28/18 15:37, Jeffrey Bouquet wrote: > >>> Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed se= quential > >>> source as for example xx1966 on april 3 .... xx2040 on april 4 this y= ear, is not loading > >>> in the browser. It was informative to read color coded the source ba= ckported to v10 > >>> v11 vs new, and new drivers coming into play. I can find NOWHERE exc= ept > >>> freshsource.org which has the ports updates interspersed which makes = the information > >>> too time consuming. As an example, > >>> > >>> 09:36:34 - r 318137 Affects: /head/usr.bin/mking/mking.1 [ mking.c= ]=20 > >>> on 5-10-2017 adding the -C and --capacity options... > >>> > >>> ....................................... > >>> What was educational to browse now is found at ???????? > >>> ...................................... > >>> _______________________________________________ > >>> 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" > >>> > >> > >> > >> https://svnweb.freebsd.org/base/head/ > >> > >> ? > >> > >> sean > >=20 > >=20 > > I tried that url every which way, sorting the headings, etc, and onscre= en > > would be at best, a description of the new source but not specifically = which > > files were changed and their complete path. Nothing like the url mentio= ned above at > > .de in the latter's overview.=20 >=20 > Possibly freshbsd.org? > I follow the 11-STABLE branch using > https://freshbsd.org/?branch=3DRELENG_11&project=3Dfreebsd >=20 >=20 > Vince > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" > >=20 > _______________________________________________ > 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" Thanks to all that replied svn-src-all ... too much RSI and expertise and time needed at least fo= r now freshbsd ... HEAD includes ports, a duplicate of freshports.org freshbsd ... CURRENT includes pc-bsd, etc freshbsd ... FreeBSD <<< this appears to be what I was posting to loo= k for. Thanks! Jeff=20= From owner-freebsd-current@freebsd.org Tue May 29 09:16: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 45E72EFD1D4 for ; Tue, 29 May 2018 09:16:09 +0000 (UTC) (envelope-from koobs.freebsd@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 C54707F3FC for ; Tue, 29 May 2018 09:16:08 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 7F51DEFD1D2; Tue, 29 May 2018 09:16:08 +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 57C0BEFD1D1 for ; Tue, 29 May 2018 09:16:08 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pl0-x233.google.com (mail-pl0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C7FA27F3FA for ; Tue, 29 May 2018 09:16:07 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pl0-x233.google.com with SMTP id az12-v6so8588556plb.8 for ; Tue, 29 May 2018 02:16:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=/x+WHLDHSuENxBlrXo8xBjDQv81AGt37l/xAHLaJetY=; b=sGvjWklvS1rbLYodAkU6knn69rCe2zS1UfCBJv5KvXyzdq/XNa1N9wsKjs0E5MqF6C 0WTrahlsX16txV+Zc/3W4jY6ecY1diNfXqw2RrtpoGIAHujA2/tPa5p1PSeOiOd62KI+ EDd9Q6mfH3XR0zIfAZjrjOP++kzaBuBNd1yqMn5/5Zh56SxbvVCHj6drLKKG5H/GrAho 0coH3IlDctoha3ec4JrvqWoFp5PpnkWMDsi6LlCvIwliM5b6euU+/dnSDjEMaZ3AHpFm PO1Za+8B8IUAy6xfYwcV8GlC8r8ZINAk0ePmkzDr7ce4lzp9dT5NNtilNdUVrtttM/+R /ePw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=/x+WHLDHSuENxBlrXo8xBjDQv81AGt37l/xAHLaJetY=; b=KSSzXq4C9h9xKJJqq+C3QkV+7UdPaTc4lCb5VJc5Dyd3TXgS37pI6wec0Tarp7c1ey vhHEOoB+oFzvu8zhMgwIyQptf3YrrmbUPjAwwY2P8qfM7gLk9DapAQpQcBMjsDw8NcXN 8bgORwOANiCeLi1kovD5mEgnrxXCBvaRZXjW4NT28UIlP8rttumSzftKpal2LvkLiDOf b4j04vcf6LNnrX7P1xgETkpLU85KNjrDj22Zc6f4cVxk5p4A/0h3yxSUfqr5tVueDHBz kOdmQm5w2k8TzNOwz7Ujs3gamM6PyVB6d3yyggZ1fEdYtBH/dTCAI2WRSxBWYl0C3Ekl 1gmg== X-Gm-Message-State: ALKqPwfRbUYYgEqhwSK5MaIpyw5PkS/3MWn3LvZgApBC4/g4C655Lz78 o1sBW2HreQA4gEOTKAyWb0gMS27/ X-Google-Smtp-Source: AB8JxZq5cGAvtHFUCZZfrotGiRyi06ikw0SPl0ynkFuHS1tF7vL+vHrZxGWMVhky/EbBIfiDZegS8g== X-Received: by 2002:a17:902:8a81:: with SMTP id p1-v6mr17229043plo.33.1527585366633; Tue, 29 May 2018 02:16:06 -0700 (PDT) Received: from [192.168.1.112] (116.133.220.111.sta.wbroadband.net.au. [111.220.133.116]) by smtp.gmail.com with ESMTPSA id a11-v6sm46735143pgn.64.2018.05.29.02.16.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 02:16:06 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: how to browse svnweb source? To: Peter Jeremy , Jeffrey Bouquet Cc: current References: <6a212103-830c-54ea-1223-1dcc48ad0ffc@freebsd.org> <20180529062948.GG96747@server.rulingia.com> From: Kubilay Kocak Message-ID: Date: Tue, 29 May 2018 19:16:02 +1000 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: <20180529062948.GG96747@server.rulingia.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.26 Precedence: 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, 29 May 2018 09:16:09 -0000 On 29/05/2018 4:29 pm, Peter Jeremy wrote: > On 2018-May-28 18:06:07 -0700, Jeffrey Bouquet wrote: >>>> Suddenly the site www.secnetix.de/olli/FreeBSD/svnews which showed sequential >>>> source as for example xx1966 on april 3 .... xx2040 on april 4 this year, is not loading >>>> in the browser. > > That site is not associated with the FreeBSD Project so you would need to > discuss the absence of information on that site with whoever runs it. > >> I tried that url every which way, sorting the headings, etc, and onscreen >> would be at best, a description of the new source but not specifically which >> files were changed and their complete path. Nothing like the url mentioned above at >> .de in the latter's overview. > > Without knowing what that site displayed, it's very difficult to know where > (or if) svnweb provides the information. Given a known revision, you can > check (eg) https://svnweb.freebsd.org/base?view=revision&revision=333926 > > If you want a sequential list of commits, you might be better off with (eg) > https://lists.freebsd.org/pipermail/svn-src-all/ > svnweb (ViewVC) has a "Revision Log" link to see commit logs for files, but paths also support it too. Unfortauntely there's just no link to it in the UI. Just append ?view=log to the URL, which will show you a commit log history, at that path. Eg: https://svnweb.freebsd.org/ports/head/?view=log From owner-freebsd-current@freebsd.org Tue May 29 11:20: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 9B557F739F9 for ; Tue, 29 May 2018 11:20:48 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B2D5845FF for ; Tue, 29 May 2018 11:20:47 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wm0-f53.google.com with SMTP id o78-v6so39611397wmg.0 for ; Tue, 29 May 2018 04:20:47 -0700 (PDT) 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:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=GlTXdlKsojUqf/84rpoYYQffsUd7ulRXD+7xzLYC0ew=; b=U28czQNSq31I5poKrpmr2XbCJmksddnbACZ51TgOXMal0ZgtFGvJC88UGVB1ZZw4Wp +QO7ATsfjWU4x6ccC/3HWIto1zPLWqQZHd/jUDi/ssHh359bL0dmtrchJaQxIMGt+L4t A8caaMB6VO1TFS7j1UJKUYGB6Xuck2BPV6WrgHniWhff0P3rSuDO+yd0hP5/jkuCqwAS Sg7RwTHrShIsRn9KYYgZM1OLMStCWuGyjbgLvB/U56larKMe4SMHTYHv9DOjqOfYtIEM LYl5BJMi2PayzQXiPCDeKhCsfhK6jTHvaD0G5Bqnv+AW8Ddc85XtTdmzmq3xhfRd7dLz gUvQ== X-Gm-Message-State: ALKqPwfVcFNQ427BrOzBha+NsKEDQx3ZI1SRBWn/Mk63mFY47wGb0eHW pjMFYdkTc2Cd1GApxN1i0phWyjWw X-Google-Smtp-Source: ADUXVKIDp6fXsk+BO4VkOx4CYg12ksTcNQ12Bqwl0Cv+F9eeXVhFpmTg2HbbS0IN73sLLk6LkxxbYA== X-Received: by 2002:a2e:4082:: with SMTP id r2-v6mr10706006lje.48.1527592840433; Tue, 29 May 2018 04:20:40 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id t14-v6sm7293789lfi.92.2018.05.29.04.20.39 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 04:20:39 -0700 (PDT) To: FreeBSD Current From: Andriy Gapon Subject: head@r334204, Bad link elm in callout_process() Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Tue, 29 May 2018 14:20:38 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.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.26 Precedence: 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, 29 May 2018 11:20:48 -0000 Has anyone else seen this panic? Any suspect commits? Any suggestion on analyzing the problem? Thanks! panic: Bad link elm 0xfffffe004bfed798 next->prev != elm cpuid = 0 time = 1527257839 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00413be770 vpanic() at vpanic+0x1a3/frame 0xfffffe00413be7d0 panic() at panic+0x43/frame 0xfffffe00413be830 callout_process() at callout_process+0x30d/frame 0xfffffe00413be8b0 handleevents() at handleevents+0x1a5/frame 0xfffffe00413be8f0 timercb() at timercb+0x254/frame 0xfffffe00413be940 lapic_handle_timer() at lapic_handle_timer+0xa7/frame 0xfffffe00413be980 Xtimerint() at Xtimerint+0xa5/frame 0xfffffe00413be980 --- interrupt, rip = 0xffffffff811cf8d6, rsp = 0xfffffe00413bea50, rbp = 0xfffffe00413bea50 --- acpi_cpu_c1() at acpi_cpu_c1+0x6/frame 0xfffffe00413bea50 acpi_cpu_idle() at acpi_cpu_idle+0x2ee/frame 0xfffffe00413beaa0 cpu_idle_acpi() at cpu_idle_acpi+0x3f/frame 0xfffffe00413beac0 cpu_idle() at cpu_idle+0x95/frame 0xfffffe00413beae0 sched_idletd() at sched_idletd+0x517/frame 0xfffffe00413bebb0 fork_exit() at fork_exit+0x84/frame 0xfffffe00413bebf0 fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00413bebf0 --- trap 0, rip = 0, rsp = 0, rbp = 0 --- KDB: enter: panic (kgdb) bt #0 kdb_enter (why=0xffffffff812f802e "panic", msg=) at /usr/devel/svn/head/sys/kern/subr_kdb.c:479 #1 0xffffffff80b93390 in vpanic (fmt=, ap=0xfffffe00413be810) at /usr/devel/svn/head/sys/kern/kern_shutdown.c:852 #2 0xffffffff80b93423 in panic (fmt=0xffffffff81df35b8 "\362\315+\201\377\377\377\377") at /usr/devel/svn/head/sys/kern/kern_shutdown.c:790 #3 0xffffffff80bab86d in callout_process (now=8718488703935) at /usr/devel/svn/head/sys/kern/kern_timeout.c:562 #4 0xffffffff8119a205 in handleevents (now=8718488703935, fake=0) at /usr/devel/svn/head/sys/kern/kern_clocksource.c:217 #5 0xffffffff8119a984 in timercb (et=0xffffffff81feb1d8 , arg=) at /usr/devel/svn/head/sys/kern/kern_clocksource.c:361 #6 0xffffffff811d9097 in lapic_handle_timer (frame=0xfffffe00413be990) at /usr/devel/svn/head/sys/x86/x86/local_apic.c:1308 #7 #8 acpi_cpu_c1 () at /usr/devel/svn/head/sys/x86/x86/cpu_machdep.c:137 #9 0xffffffff804602ee in acpi_cpu_idle (sbt=) at /usr/devel/svn/head/sys/dev/acpica/acpi_cpu.c:1187 #10 0xffffffff811cfeff in cpu_idle_acpi (sbt=178798794) at /usr/devel/svn/head/sys/x86/x86/cpu_machdep.c:430 #11 0xffffffff811cffa5 in cpu_idle (busy=0) at /usr/devel/svn/head/sys/x86/x86/cpu_machdep.c:578 #12 0xffffffff80bc28d7 in sched_idletd (dummy=) at /usr/devel/svn/head/sys/kern/sched_ule.c:2832 #13 0xffffffff80b524c4 in fork_exit (callout=0xffffffff80bc23c0 , arg=0x0, frame=0xfffffe00413bec00) at /usr/devel/svn/head/sys/kern/kern_fork.c:1039 #14 (kgdb) fr 3 #3 0xffffffff80bab86d in callout_process (now=8718488703935) at /usr/devel/svn/head/sys/kern/kern_timeout.c:562 562 } (kgdb) i loc first = 8719562445759 firstb = 519662 nowb = 519662 lookahead = last = 8720629104640 lastb = 519789 cc = 0xffffffff82011980 max = 8720629104640 tmp = tmpn = tmp_max = sc = (kgdb) p *cc $2 = { cc_lock = { lock_object = { lo_name = 0xffffffff8131227d "callout", lo_flags = 720896, lo_data = 0, lo_witness = 0x0 }, mtx_lock = 18446735277670449152 }, cc_exec_entity = {{ cc_curr = 0x0, cc_drain = 0x0, ce_migration_func = 0x0, ce_migration_arg = 0x0, ce_migration_cpu = 256, ce_migration_time = 0, ce_migration_prec = 0, cc_cancel = true, cc_waiting = false }, { cc_curr = 0x0, cc_drain = 0x0, ce_migration_func = 0x0, ce_migration_arg = 0x0, ce_migration_cpu = 256, ce_migration_time = 0, ce_migration_prec = 0, cc_cancel = false, cc_waiting = false }}, cc_next = 0x0, cc_callout = 0xfffffe0003841000, cc_callwheel = 0xfffffe0003963000, cc_expireq = { tqh_first = 0xffffffff81af68c8 , tqh_last = 0xffffffff81af68c8 }, cc_callfree = { slh_first = 0xfffffe00039622c0 }, cc_firstevent = 8718488678823, cc_lastscan = 8718488703935, cc_cookie = 0xfffff8000338fd00, cc_bucket = 28118, cc_inited = 1, cc_ktr_event_name = "callwheel cpu 0\000\000\000\000" } (kgdb) p cc->cc_callwheel[firstb & callwheelmask] $4 = { lh_first = 0xfffffe004bfed798 } (kgdb) p *$4.lh_first $5 = { c_links = { le = { le_next = 0xffffffff81bb08c8 , le_prev = 0xfffffe0003999f70 }, sle = { sle_next = 0xffffffff81bb08c8 }, tqe = { tqe_next = 0xffffffff81bb08c8 , tqe_prev = 0xfffffe0003999f70 } }, c_time = 8718482236373, c_precision = 26843543, c_arg = 0xfffffe004bfe9000, c_func = 0xffffffff8060cef0 , c_lock = 0x0, c_flags = 2, c_iflags = 20, c_cpu = 0 } (kgdb) p *$4.lh_first->c_links.le.le_next $6 = { c_links = { le = { le_next = 0x0, le_prev = 0xfffffe0003999f98 }, sle = { sle_next = 0x0 }, tqe = { tqe_next = 0x0, tqe_prev = 0xfffffe0003999f98 } }, c_time = 8718576725647, c_precision = 26843543, c_arg = 0x0, c_func = 0xffffffff8045bfa0 , c_lock = 0x0, c_flags = 2, c_iflags = 20, c_cpu = 0 } -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 29 11:53: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 EC546F758C8 for ; Tue, 29 May 2018 11:53:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 83F62858CE; Tue, 29 May 2018 11:53:22 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 288E62603AE; Tue, 29 May 2018 13:53:21 +0200 (CEST) Subject: Re: head@r334204, Bad link elm in callout_process() To: Andriy Gapon , FreeBSD Current References: From: Hans Petter Selasky Message-ID: <84341ca3-90a5-97ef-8eee-dc1bbb07503c@selasky.org> Date: Tue, 29 May 2018 13:53:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 29 May 2018 11:53:23 -0000 On 05/29/18 13:20, Andriy Gapon wrote: > (kgdb) p *$4.lh_first->c_links.le.le_next > $6 = { > c_links = { > le = { > le_next = 0x0, > le_prev = 0xfffffe0003999f98 Where does the le_prev point? Typically happens when callouts are not properly drained before freeing memory. --HPS From owner-freebsd-current@freebsd.org Tue May 29 13:50: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 2A1CEF7E142 for ; Tue, 29 May 2018 13:50:19 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 81A906B4A5; Tue, 29 May 2018 13:50:18 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wm0-f47.google.com with SMTP id l1-v6so40894175wmb.2; Tue, 29 May 2018 06:50:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=n1ouPVbYLeQkY8oJoJJhTq2b3SxHfUAN4Ltjfla6KB4=; b=ro37/ZK+OYK8teWQRJS3qimbfFqZitMQ6TqBci3DMK5LBGTLRL2EhFXLUAvMbSmRUk 9mQn+TLkpBpfSn9fYzQuuzqRKtpPAS+tqrpRWSRvoyOgkaDJ4Stak91/GSD4/hX9sYbm hBXqkXp8Ovw3LJhdltPNlXtPoU2T2HHBJBNM4PwZl9wblfybO4ksEXnNpo5R0XRQgr+J +WFoVyK7VhPRc82SFa+n2Y5x+ilsO4lUoSPpUTwc6FwTrgkiL2Z2a+WwY89vBZofW94Z BwkuYM/4jsYIleRsn1RqXp/fCdXZG55HvcwbWSTltTfKaEcSAdO4u+jfYDq+Jm21yHbX eWmA== X-Gm-Message-State: ALKqPwf1x/krrg+3qYVLho3oWxVwsJDQxeVjV62t8YbHKiGy0Or8unBe 5FA/S9kWYmqtYiB649qmQWEeEc+I X-Google-Smtp-Source: AB8JxZrMCQw15e+sk8nPYl2uk9l/s3QkQc7D6ZveuklDltKIQ9LnHJJWUMXk3pYL5yJckeDqJjdF7Q== X-Received: by 2002:a2e:985a:: with SMTP id e26-v6mr11147437ljj.124.1527601816381; Tue, 29 May 2018 06:50:16 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id q25-v6sm1663537lji.41.2018.05.29.06.50.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 06:50:15 -0700 (PDT) Subject: Bad link elm in vm_object_terminate [Was: crash on process exit.. current at about r332467] To: freebsd-current References: <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org> Cc: Julian Elischer , Bryan Drewery , Mark Johnston From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <9bf4b2b0-65a2-90ef-c8c0-3022e80bc149@FreeBSD.org> Date: Tue, 29 May 2018 16:50:14 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org> 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.26 Precedence: 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, 29 May 2018 13:50:19 -0000 On 23/04/2018 17:50, Julian Elischer wrote: > back trace at:  http://www.freebsd.org/~julian/bob-crash.png > > If anyone wants to take a look.. > > In the exit syscall, while deallocating a vm object. > > I haven't see references to a similar crash in the last 10 days or so.. But if > it rings any bells... We have just got another one: panic: Bad link elm 0xfffff80cc3938360 prev->next != elm Matching disassembled code to C code, it seems that the crash is somewhere in vm_object_terminate_pages (inlined into vm_object_terminate), probably in one of TAILQ_REMOVE-s there: if (p->queue != PQ_NONE) { KASSERT(p->queue < PQ_COUNT, ("vm_object_terminate: " "page %p is not queued", p)); pq1 = vm_page_pagequeue(p); if (pq != pq1) { if (pq != NULL) { vm_pagequeue_cnt_add(pq, dequeued); vm_pagequeue_unlock(pq); } pq = pq1; vm_pagequeue_lock(pq); dequeued = 0; } p->queue = PQ_NONE; TAILQ_REMOVE(&pq->pq_pl, p, plinks.q); dequeued--; } if (vm_page_free_prep(p, true)) continue; unlist: TAILQ_REMOVE(&object->memq, p, listq); } Please note that this is the code before r332974 Improve VM page queue scalability. I am not sure if r332974 + r333256 would fix the problem or if it just would get moved to a different place. Does this ring a bell to anyone who tinkered with that part of the VM code recently? Looking a little bit further, I think that object->memq somehow got corrupted. memq contains just two elements and the reported element is not there. (kgdb) p *(struct vm_page *)0xfffff80cc3938360 $22 = { plinks = { q = { tqe_next = 0xfffff80cd7175398, tqe_prev = 0xfffff80cb9f69170 }, s = { ss = { sle_next = 0xfffff80cd7175398 }, pv = 0xfffff80cb9f69170 }, memguard = { p = 18446735332764767128, v = 18446735332276081008 } }, listq = { tqe_next = 0xfffff80cc3938568, <============= tqe_prev = 0xfffff8078c11b848 <============= }, object = 0x0, pindex = 1548, phys_addr = 14695911424, md = { pv_list = { tqh_first = 0x0, tqh_last = 0xfffff80cc3938398 }, pv_gen = 1205766, pat_mode = 6 }, wire_count = 0, busy_lock = 1, hold_count = 0, flags = 0, aflags = 0 '\000', oflags = 0 '\000', queue = 255 '\377', psind = 0 '\000', segind = 5 '\005', order = 13 '\r', pool = 0 '\000', act_count = 5 '\005', valid = 0 '\000', dirty = 0 '\000' } (kgdb) p object->memq $11 = { tqh_first = 0xfffff80cb861cfb8, tqh_last = 0xfffff80cc3938780 } (kgdb) p *object->memq.tqh_first $25 = { plinks = { q = { tqe_next = 0xfffff80cb9f69108, tqe_prev = 0xfffff80cd7175398 }, s = { ss = { sle_next = 0xfffff80cb9f69108 }, pv = 0xfffff80cd7175398 }, memguard = { p = 18446735332276080904, v = 18446735332764767128 } }, listq = { tqe_next = 0xfffff80cb56eafb0, <============= tqe_prev = 0xfffff8078c11b848 <============= }, object = 0xfffff8078c11b800, pindex = 515, phys_addr = 7299219456, md = { pv_list = { tqh_first = 0xfffff80b99e4ff88, tqh_last = 0xfffff80b99e4ff90 }, pv_gen = 466177, pat_mode = 6 }, wire_count = 0, busy_lock = 2, hold_count = 0, flags = 0, aflags = 0 '\000', oflags = 0 '\000', queue = 255 '\377', psind = 0 '\000', segind = 5 '\005', order = 13 '\r', pool = 0 '\000', act_count = 5 '\005', valid = 255 '\377', dirty = 0 '\000' } (kgdb) p *object->memq.tqh_first->listq.tqe_next $26 = { plinks = { q = { tqe_next = 0x0, tqe_prev = 0xfffff80cc92e1d18 }, s = { ss = { sle_next = 0x0 }, pv = 0xfffff80cc92e1d18 }, memguard = { p = 0, v = 18446735332531379480 } }, listq = { tqe_next = 0x0, <============= tqe_prev = 0xfffff80cb861cfc8 <============= }, object = 0xfffff8078c11b800, pindex = 1548, phys_addr = 5350158336, md = { pv_list = { tqh_first = 0xfffff80a07222808, tqh_last = 0xfffff80a07222810 }, pv_gen = 7085, pat_mode = 6 }, wire_count = 0, busy_lock = 1, hold_count = 0, flags = 0, aflags = 1 '\001', oflags = 0 '\000', queue = 1 '\001', psind = 0 '\000', segind = 5 '\005', order = 13 '\r', pool = 0 '\000', act_count = 5 '\005', valid = 255 '\377', dirty = 255 '\377' } Pages 0xfffff80cc3938360 (the reported one) and 0xfffff80cb56eafb0 (the last one on memq) have the same index 1548. Also, memq.tqh_last points to the reported page, but it is not reachable via tqe_next pointers. It's also potentially interesting is that the reported page looks like it's already freed and the replacement page is both valid and dirty. The object, just in case: (kgdb) p *object $34 = { lock = { lock_object = { lo_name = 0xffffffff81202c27 "vm object", lo_flags = 627245056, lo_data = 0, lo_witness = 0xfffff80cffd6a700 }, rw_lock = 18446735286009226592 }, object_list = { tqe_next = 0xfffff80b2481e200, tqe_prev = 0xfffff80b2481e020 }, shadow_head = { lh_first = 0x0 }, shadow_list = { le_next = 0xfffff809c070f900, le_prev = 0xfffff80869c06c30 }, memq = { tqh_first = 0xfffff80cb861cfb8, tqh_last = 0xfffff80cc3938780 }, rtree = { rt_root = 18446735279843613792 }, size = 1561, domain = { dr_policy = 0x0, dr_iterator = 0 }, generation = 1, ref_count = 0, shadow_count = 0, memattr = 6 '\006', type = 0 '\000', flags = 12296, pg_color = 1809, paging_in_progress = 0, resident_page_count = 5, backing_object = 0x0, backing_object_offset = 0, pager_object_list = { tqe_next = 0x0, tqe_prev = 0x0 }, rvq = { lh_first = 0xfffff80cad278b60 }, handle = 0x0, un_pager = { vnp = { vnp_size = 19444, writemappings = 0 }, devp = { devp_pglist = { tqh_first = 0x4bf4, tqh_last = 0x0 }, ops = 0x0, dev = 0x0 }, sgp = { sgp_pglist = { tqh_first = 0x4bf4, tqh_last = 0x0 } }, swp = { swp_tmpfs = 0x4bf4, swp_blks = { pt_root = 0 } } }, cred = 0xfffff806811adc00, charge = 6393856, umtx_data = 0x0 } Interesting that it is on a shadow list. -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 29 13:53: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 B3064F7E554 for ; Tue, 29 May 2018 13:53:22 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wr0-f173.google.com (mail-wr0-f173.google.com [209.85.128.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2685E6B965 for ; Tue, 29 May 2018 13:53:21 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wr0-f173.google.com with SMTP id w10-v6so25682043wrk.9 for ; Tue, 29 May 2018 06:53:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=PuRHwHVWPEb2oBdQvi4LJtv5gRROW3oUXtwLcm/xDW4=; b=DUe6UMNul4rtuuqPiaUGsQVNpxepRK0YvFlzZ7zi3gvrlfqRpi1nzacXdi2iCWe56u JFTZizxBTgF06uS+PSYTcn59mYBV3XmX4OvQudANj66ZJVC+L1CbEcXi1vxtLOeVuLEs i2MzdkWMhcUv8vNKOli8fNhaQZGyMKrvHmH67nfBpKbSgW0L0Kq/QGPx39kDjJCHw5J9 Mqgw3qwtVLbV3vezAWvidBqYdOKOJ/vkWN9vYg9Q6oYvrrh78NCdXfHqpV5sBstitBuF 96WuSepeUd6Y5Zqh8ZxLEymPZc3ciK0/P46yepqQsHd0UeXqn31eldHH4TKxpSa68Gtk pCfA== X-Gm-Message-State: ALKqPwejVq0PpfNvw/16lTa9X4uXkaR8bnASA4bQbiUxBnTikra1PLRb e/HM11H77N2ERQ2ynzu2xkIW9RdT X-Google-Smtp-Source: ADUXVKKO+C+WRec25eHL4i3tgtc78T7TCOQEHPIGdb70SGM+TW/JLPjJOntzkj3XUfuBr6CKJcwo4A== X-Received: by 2002:a19:e21e:: with SMTP id z30-v6mr9188055lfg.58.1527601995347; Tue, 29 May 2018 06:53:15 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id z5-v6sm1365309lff.87.2018.05.29.06.53.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 06:53:14 -0700 (PDT) Subject: Re: head@r334204, Bad link elm in callout_process() To: Hans Petter Selasky , FreeBSD Current References: <84341ca3-90a5-97ef-8eee-dc1bbb07503c@selasky.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <0df613ac-70aa-f793-1b7b-7a5e097fef28@FreeBSD.org> Date: Tue, 29 May 2018 16:53:13 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <84341ca3-90a5-97ef-8eee-dc1bbb07503c@selasky.org> 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.26 Precedence: 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, 29 May 2018 13:53:22 -0000 On 29/05/2018 14:53, Hans Petter Selasky wrote: > On 05/29/18 13:20, Andriy Gapon wrote: >> (kgdb) p *$4.lh_first->c_links.le.le_next >> $6 = { >>    c_links = { >>      le = { >>        le_next = 0x0, >>        le_prev = 0xfffffe0003999f98 > > Where does the le_prev point? > > Typically happens when callouts are not properly drained before freeing memory. Yeah, this could have been a pilot error. I added some debugging code and that code could do callout_init + callout_reset on an active or pending callout. I am not seeing the problem without the debugging code. Sorry for the noise! -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 29 14:18: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 641F0F7FE1C for ; Tue, 29 May 2018 14:18:08 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wr0-f170.google.com (mail-wr0-f170.google.com [209.85.128.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C89726D1F8 for ; Tue, 29 May 2018 14:18:07 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wr0-f170.google.com with SMTP id a15-v6so25843245wrm.0 for ; Tue, 29 May 2018 07:18:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:from:to:references:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=SfxlJib+4VquC20ZFnCej0Dglh8nhZN/hXtR8teCJcg=; b=TK45G/6eYcwigCqz1CMbb7x6ET+D73iF9ymnSVorYqDbxZjlyYJM8njom3zuFRznP0 auuK0o3iAcX6NCyelsm24jz3fPT8cQrHlYRYyi7aT0HZBZn73Q+q/HGcWr6z2Ckect7i mny5CfzAmfucJDdrXx8kGO50h8DpQBEuJENCyO9vItq7EXlrvAHP90M4XFUnlVkdOG3I RtC8aAEG7/QQGq53/6EbjQJf5V4s39yziOnp22WAwcuDbESQdpSrG3SBXdRr53eFEDFt +6qHkM5+LauXjW8GIOZ99cae1F10U2Nf1GJ2BVbdhROms8XedI9sCE7s6qC/cvvO7Cv5 QRgg== X-Gm-Message-State: ALKqPwdx3Asp1nNmKUaHR8dc+zpWAlEtXz8ELtNEuPFMXBSDctZIa+0W ZkdoV7O4Ze1aUYbjSH36jw/pcKJd X-Google-Smtp-Source: ADUXVKIN1+4JhWdiqbrmrvtyUAtMBKdrUuCA0YO9h1zZf9c2ZSLV7D7MPzKjlnZun0iIofeqPJo5BQ== X-Received: by 2002:a19:5ad4:: with SMTP id y81-v6mr9254718lfk.82.1527603486091; Tue, 29 May 2018 07:18:06 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id k5-v6sm6521756lji.39.2018.05.29.07.18.04 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 07:18:05 -0700 (PDT) Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 From: Andriy Gapon To: FreeBSD Current References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: Date: Tue, 29 May 2018 17:18:03 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> 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.26 Precedence: 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, 29 May 2018 14:18:08 -0000 [ping] On 21/05/2018 11:44, Andriy Gapon wrote: > > FreeBSD 12.0-CURRENT amd64 r332472 > Does this panic ring a bell to anyone? > Has it already been fixed? > Thank you! > > panic: vm_phys_free_pages: page 0xfffff80cbfb71958 has unexpected order 0 > cpuid = 3 > time = 1526822662 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe017547c340 > vpanic() at vpanic+0x18d/frame 0xfffffe017547c3a0 > doadump() at doadump/frame 0xfffffe017547c420 > vm_phys_free_pages() at vm_phys_free_pages+0x253/frame 0xfffffe017547c450 > vm_page_free_phys_pglist() at vm_page_free_phys_pglist+0x37/frame 0xfffffe017547c470 > vm_object_terminate() at vm_object_terminate+0x405/frame 0xfffffe017547c4d0 > vm_object_deallocate() at vm_object_deallocate+0x45c/frame 0xfffffe017547c530 > vm_map_process_deferred() at vm_map_process_deferred+0x99/frame 0xfffffe017547c560 > vm_map_remove() at vm_map_remove+0xc6/frame 0xfffffe017547c590 > exec_new_vmspace() at exec_new_vmspace+0x185/frame 0xfffffe017547c5f0 > exec_elf64_imgact() at exec_elf64_imgact+0x907/frame 0xfffffe017547c6e0 > kern_execve() at kern_execve+0x82c/frame 0xfffffe017547ca40 > sys_execve() at sys_execve+0x4c/frame 0xfffffe017547cac0 > amd64_syscall() at amd64_syscall+0x79b/frame 0xfffffe017547cbf0 > fast_syscall_common() at fast_syscall_common+0x101/frame 0xfffffe017547cbf0 > I am adding some more details. There is certain similarity between this crash and the one reported in https://lists.freebsd.org/pipermail/freebsd-current/2018-April/069246.html For example, they have vm_object_terminate_pages() in common. (kgdb) bt #0 __curthread () at ./machine/pcpu.h:230 #1 doadump (textdump=1) at /usr/src/sys/kern/kern_shutdown.c:361 #2 0xffffffff80b67942 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:441 #3 0xffffffff80b67ead in vpanic (fmt=, ap=0xfffffe017547c3e0) at /usr/src/sys/kern/kern_shutdown.c:837 #4 0xffffffff80b67c30 in kassert_panic (fmt=0xffffffff812d06bd "vm_phys_free_pages: page %p has unexpected order %d") at /usr/src/sys/kern/kern_shutdown.c:723 #5 0xffffffff80eae4e3 in vm_phys_free_pages (m=0xfffff80cbfb71958, order=0) at /usr/src/sys/vm/vm_phys.c:922 #6 0xffffffff80ea6687 in vm_page_free_phys_pglist (tq=) at /usr/src/sys/vm/vm_page.c:3286 #7 0xffffffff80e9e185 in vm_object_terminate_pages (object=) at /usr/src/sys/vm/vm_object.c:792 #8 vm_object_terminate (object=0xfffff8036a7cc700) at /usr/src/sys/vm/vm_object.c:861 #9 0xffffffff80e9d1dc in vm_object_deallocate (object=0xfffff8036a7cc700) at /usr/src/sys/vm/vm_object.c:684 #10 0xffffffff80e923d9 in vm_map_entry_deallocate (system_map=, entry=) at /usr/src/sys/vm/vm_map.c:2997 #11 vm_map_process_deferred () at /usr/src/sys/vm/vm_map.c:541 #12 0xffffffff80e974b6 in _vm_map_unlock (map=, file=, line=3189) at /usr/src/sys/vm/vm_map.c:554 #13 vm_map_remove (map=, start=4096, end=140737488355328) at /usr/src/sys/vm/vm_map.c:3189 #14 0xffffffff80b215a5 in exec_new_vmspace (imgp=0xfffffe017547c8b0, sv=) at /usr/src/sys/kern/kern_exec.c:1099 #15 0xffffffff80af7d37 in exec_elf64_imgact (imgp=) at /usr/src/sys/kern/imgact_elf.c:922 #16 0xffffffff80b2018c in do_execve (td=, args=, mac_p=) at /usr/src/sys/kern/kern_exec.c:606 #17 kern_execve (td=, args=, mac_p=) at /usr/src/sys/kern/kern_exec.c:351 #18 0xffffffff80b1f61c in sys_execve (td=0xfffff803e08cf000, uap=0xfffff803e08cf3c0) at /usr/src/sys/kern/kern_exec.c:225 #19 0xffffffff810270ab in syscallenter (td=0xfffff803e08cf000) at /usr/src/sys/amd64/amd64/../../kern/subr_syscall.c:134 #20 amd64_syscall (td=0xfffff803e08cf000, traced=0) at /usr/src/sys/amd64/amd64/trap.c:936 #21 #22 0x00000008003ddd9a in ?? () Backtrace stopped: Cannot access memory at address 0x7fffffffe6c8 (kgdb) fr 8 #8 vm_object_terminate (object=0xfffff8036a7cc700) at /usr/src/sys/vm/vm_object.c:861 861 vm_object_terminate_pages(object); (kgdb) p *object $1 = { lock = { lock_object = { lo_name = 0xffffffff81202c27 "vm object", lo_flags = 627245056, lo_data = 0, lo_witness = 0xfffff80cffd6a700 }, rw_lock = 18446735294268764160 }, object_list = { tqe_next = 0xfffff8036a7cc800, tqe_prev = 0xfffff8036a7cc620 }, shadow_head = { lh_first = 0x0 }, shadow_list = { le_next = 0xfffff803705a7a00, le_prev = 0xfffff805b994d830 }, memq = { tqh_first = 0xfffff80cbfb71958, tqh_last = 0xfffff80cbfb71900 }, rtree = { rt_root = 18446735295662474800 }, size = 1561, domain = { dr_policy = 0x0, dr_iterator = 0 }, generation = 1, ref_count = 0, shadow_count = 0, memattr = 6 '\006', type = 0 '\000', flags = 12296, pg_color = 1809, paging_in_progress = 0, resident_page_count = 5, backing_object = 0x0, backing_object_offset = 0, pager_object_list = { tqe_next = 0x0, tqe_prev = 0x0 }, rvq = { lh_first = 0xfffff80cad51cc40 }, handle = 0x0, un_pager = { vnp = { vnp_size = 5, writemappings = 0 }, devp = { devp_pglist = { tqh_first = 0x5, tqh_last = 0x0 }, ops = 0x0, dev = 0x0 }, sgp = { sgp_pglist = { tqh_first = 0x5, tqh_last = 0x0 } }, swp = { swp_tmpfs = 0x5, swp_blks = { pt_root = 0 } } }, cred = 0xfffff80c131d0500, charge = 6393856, umtx_data = 0x0 } (kgdb) fr 5 #5 0xffffffff80eae4e3 in vm_phys_free_pages (m=0xfffff80cbfb71958, order=0) at /usr/src/sys/vm/vm_phys.c:922 922 KASSERT(m->order == VM_NFREEORDER, (kgdb) p *m $2 = { plinks = { q = { tqe_next = 0xfffff80cfa917ae8, tqe_prev = 0xfffff80cfa816fb8 }, s = { ss = { sle_next = 0xfffff80cfa917ae8 }, pv = 0xfffff80cfa816fb8 }, memguard = { p = 18446735333359975144, v = 18446735333358923704 } }, listq = { tqe_next = 0xfffff80cbfb71820, tqe_prev = 0xfffff80cfa816fc8 }, object = 0x0, pindex = 1548, phys_addr = 12144705536, md = { pv_list = { tqh_first = 0x0, tqh_last = 0xfffff80cbfb71990 }, pv_gen = 65204, pat_mode = 6 }, wire_count = 0, busy_lock = 1, hold_count = 0, flags = 0, aflags = 0 '\000', oflags = 0 '\000', queue = 255 '\377', psind = 0 '\000', segind = 5 '\005', order = 0 '\000', pool = 0 '\000', act_count = 5 '\005', valid = 0 '\000', dirty = 0 '\000' } -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 29 14:24: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 46B2AFBE462 for ; Tue, 29 May 2018 14:24:16 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D6C776D784; Tue, 29 May 2018 14:24:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (115-166-25-190.dyn.iinet.net.au [115.166.25.190]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w4TEOA5k068898 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 29 May 2018 07:24:13 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: head@r334204, Bad link elm in callout_process() To: Andriy Gapon , Hans Petter Selasky , FreeBSD Current References: <84341ca3-90a5-97ef-8eee-dc1bbb07503c@selasky.org> <0df613ac-70aa-f793-1b7b-7a5e097fef28@FreeBSD.org> From: Julian Elischer Message-ID: Date: Tue, 29 May 2018 22:24:05 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <0df613ac-70aa-f793-1b7b-7a5e097fef28@FreeBSD.org> 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.26 Precedence: 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, 29 May 2018 14:24:16 -0000 On 29/5/18 9:53 pm, Andriy Gapon wrote: > On 29/05/2018 14:53, Hans Petter Selasky wrote: >> On 05/29/18 13:20, Andriy Gapon wrote: >>> (kgdb) p *$4.lh_first->c_links.le.le_next >>> $6 = { >>>    c_links = { >>>      le = { >>>        le_next = 0x0, >>>        le_prev = 0xfffffe0003999f98 >> Where does the le_prev point? >> >> Typically happens when callouts are not properly drained before freeing memory. > Yeah, this could have been a pilot error. > I added some debugging code and that code could do callout_init + callout_reset > on an active or pending callout. I am not seeing the problem without the > debugging code. > Sorry for the noise! did you add code to that machine?? (bob.$work) > From owner-freebsd-current@freebsd.org Tue May 29 16: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 BEE19EF6368 for ; Tue, 29 May 2018 16:22:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pf0-x244.google.com (mail-pf0-x244.google.com [IPv6:2607:f8b0:400e:c00::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 438C4732FF; Tue, 29 May 2018 16:22:25 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pf0-x244.google.com with SMTP id f189-v6so7530492pfa.7; Tue, 29 May 2018 09:22:25 -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:content-transfer-encoding:in-reply-to :user-agent; bh=a+i7pIp5GL8+F4QArh2NOHBV3KJdyFI05sVHWVDoxjw=; b=dExinrwvSEdJ1ah/ZTjDDOZNTmSUMlwapMegUmGXRNLueL3eIawArpF5orTv86TCIg XIjMw4BZ5/JpR49icLf57bmFRZnwtgdoQM48RR4W1ew4b6G0Ca80ISQYQRvCdLk7/KPO OXvZavJ6DL2TbmF5b40NsItmxaPxvKACThuexjwn1dN7sJpnDH9a7Rm8xSsuRpcwFji2 WjIAZXgxEPmKMQhJiKGrRyxzIwjPHI3YEU68D8FECvvr2ujNQUGupXSRF5wOKOgV2Buz rYmmCeV64KqV3cCRmUZAFP8UlbjdxHHLb4wv95QNm7PyCUpIkA08P2+ISK9mnYjhOeOT Ea+w== 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 :content-transfer-encoding:in-reply-to:user-agent; bh=a+i7pIp5GL8+F4QArh2NOHBV3KJdyFI05sVHWVDoxjw=; b=Ny492IhzcTYqRQW0Mn7GStItRXZh+6xyMjM40SoB9abfRI+oxn1/vgIgtwvVn7w7Kg niEsvW+8HJ72QEFF21cdcmNge4zR4pH9HBx8Ib6o9uDlszkEykjwcuzD7IJunPKQrLeT LU5MlS1tYK/5GZ5nFVxIYjkoEv0pwYngm+YoscMAeoOO2Nq77ahnq5ZNY93KJsoQDCw9 qox5gDmL/UxzPl9gk0ZJj0IK+9FrYkqYa047fU0Hh5Z3cEKNzRe39tWjcdmCBlvU8JCM q2/qICF0weXdDF7KpDSjwFW1I1EQN9HzZwtnwYJDsJJpzIFLCN0ptfineXmYe9D1yC3S Xljw== X-Gm-Message-State: ALKqPwejLllGNAm4cQeE0UhKGrrU0HLcJDfHGgrBeVOudvsnRG7OFKhf mQQoJ0JL5s+jIukLjT8IdPfsJg== X-Google-Smtp-Source: AB8JxZpI0fLa+C7FtSwPAgoiz7JEkZYhAmtkHte1Lnm1DbGu963DPzhOuwQptXmu7ELej4wRXEoC/A== X-Received: by 2002:a62:1549:: with SMTP id 70-v6mr18080799pfv.91.1527610943961; Tue, 29 May 2018 09:22:23 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-156.dsl.bell.ca. [70.49.169.156]) by smtp.gmail.com with ESMTPSA id z7-v6sm44151323pgp.74.2018.05.29.09.22.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 09:22:22 -0700 (PDT) Sender: Mark Johnston Date: Tue, 29 May 2018 12:22:17 -0400 From: Mark Johnston To: Andriy Gapon Cc: freebsd-current , Julian Elischer , Bryan Drewery Subject: Re: Bad link elm in vm_object_terminate [Was: crash on process exit.. current at about r332467] Message-ID: <20180529162217.GA99109@raichu> References: <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org> <9bf4b2b0-65a2-90ef-c8c0-3022e80bc149@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9bf4b2b0-65a2-90ef-c8c0-3022e80bc149@FreeBSD.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 16:22:26 -0000 On Tue, May 29, 2018 at 04:50:14PM +0300, Andriy Gapon wrote: > On 23/04/2018 17:50, Julian Elischer wrote: > > back trace at:  http://www.freebsd.org/~julian/bob-crash.png > > > > If anyone wants to take a look.. > > > > In the exit syscall, while deallocating a vm object. > > > > I haven't see references to a similar crash in the last 10 days or so.. But if > > it rings any bells... > > We have just got another one: > panic: Bad link elm 0xfffff80cc3938360 prev->next != elm > > Matching disassembled code to C code, it seems that the crash is somewhere in > vm_object_terminate_pages (inlined into vm_object_terminate), probably in one of > TAILQ_REMOVE-s there: > if (p->queue != PQ_NONE) { > KASSERT(p->queue < PQ_COUNT, ("vm_object_terminate: " > "page %p is not queued", p)); > pq1 = vm_page_pagequeue(p); > if (pq != pq1) { > if (pq != NULL) { > vm_pagequeue_cnt_add(pq, dequeued); > vm_pagequeue_unlock(pq); > } > pq = pq1; > vm_pagequeue_lock(pq); > dequeued = 0; > } > p->queue = PQ_NONE; > TAILQ_REMOVE(&pq->pq_pl, p, plinks.q); > dequeued--; > } > if (vm_page_free_prep(p, true)) > continue; > unlist: > TAILQ_REMOVE(&object->memq, p, listq); > } > > > Please note that this is the code before r332974 Improve VM page queue scalability. > I am not sure if r332974 + r333256 would fix the problem or if it just would get > moved to a different place. > > Does this ring a bell to anyone who tinkered with that part of the VM code recently? This doesn't look familiar to me and I doubt that r332974 fixed the underlying problem, whatever it is. > Looking a little bit further, I think that object->memq somehow got corrupted. > memq contains just two elements and the reported element is not there. Based on the debugging session, it would be interesting to know if there were any other threads somehow manipulating the (dead) object at the time of the panic. Among the panics that you observed, is it the same application that is causing the crash in each case? From owner-freebsd-current@freebsd.org Tue May 29 16:38: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 E4859EF742E for ; Tue, 29 May 2018 16:38:29 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-wr0-f193.google.com (mail-wr0-f193.google.com [209.85.128.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4E5FC73B4B; Tue, 29 May 2018 16:38:29 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-wr0-f193.google.com with SMTP id j1-v6so26626083wrm.1; Tue, 29 May 2018 09:38:29 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=uO9v9Yw8m91uvXXCMeJsr24QMNk8LB8HYbFTru++qMU=; b=rGGMoNeisCLBahX2sgua/+SKAweHEnXItTwbqBb5TfD7Pc1OuGyEx67RMc8HMUF2Sp 0z4soCACcKw+BDhZfabERoMZBOnSi3bnCZ9hKA1NhlwipFa4d+Tw4hRq/pKmvOLbgBem cru9kZmaHm/54dyUHPj9lsAg8ZIne2y06Dkrlgh7dpSqtKrgqfYx8qnMdG0X5lbEUE+y TBKuW5SPmi5uVGUgnlseZtnHdFdxyGWhwRSRboHpmeuMhJ2Ye+ESxgir/vR1MvKV/fGy Kwtb39Kgu+5WFowCdCN43V2g+vZmitPcyD5axbh6zLmxARyOhle4euR50a0W57jipS+N BvgA== X-Gm-Message-State: ALKqPwd0pJRlv1ibe5MjfXpRxjkOV2ymSoUY3B1CU8kv8GdfVBQn1WaA P/px+SyXaNE7v7gLnhn8zynOLHKQ X-Google-Smtp-Source: ADUXVKLbKc+e3m7kZjINOq5PGTSBJ2UML5fZ+OyxwyV1ckP7GIoDzanQc0kCU6WneFSTpmESfuH7nA== X-Received: by 2002:a19:3b0e:: with SMTP id i14-v6mr9612660lfa.48.1527611901502; Tue, 29 May 2018 09:38:21 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id o9-v6sm1573844lfk.2.2018.05.29.09.38.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 09:38:20 -0700 (PDT) Subject: Re: Bad link elm in vm_object_terminate [Was: crash on process exit.. current at about r332467] To: Mark Johnston Cc: freebsd-current , Julian Elischer , Bryan Drewery References: <9479e941-39be-e6e2-869e-aac475c5e33a@freebsd.org> <9bf4b2b0-65a2-90ef-c8c0-3022e80bc149@FreeBSD.org> <20180529162217.GA99109@raichu> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <8ac5295c-d915-2994-6bcd-bc5a1a68f075@FreeBSD.org> Date: Tue, 29 May 2018 19:38:19 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180529162217.GA99109@raichu> 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.26 Precedence: 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, 29 May 2018 16:38:30 -0000 On 29/05/2018 19:22, Mark Johnston wrote: > On Tue, May 29, 2018 at 04:50:14PM +0300, Andriy Gapon wrote: >> On 23/04/2018 17:50, Julian Elischer wrote: >>> back trace at:  http://www.freebsd.org/~julian/bob-crash.png >>> >>> If anyone wants to take a look.. >>> >>> In the exit syscall, while deallocating a vm object. >>> >>> I haven't see references to a similar crash in the last 10 days or so.. But if >>> it rings any bells... >> >> We have just got another one: >> panic: Bad link elm 0xfffff80cc3938360 prev->next != elm >> >> Matching disassembled code to C code, it seems that the crash is somewhere in >> vm_object_terminate_pages (inlined into vm_object_terminate), probably in one of >> TAILQ_REMOVE-s there: >> if (p->queue != PQ_NONE) { >> KASSERT(p->queue < PQ_COUNT, ("vm_object_terminate: " >> "page %p is not queued", p)); >> pq1 = vm_page_pagequeue(p); >> if (pq != pq1) { >> if (pq != NULL) { >> vm_pagequeue_cnt_add(pq, dequeued); >> vm_pagequeue_unlock(pq); >> } >> pq = pq1; >> vm_pagequeue_lock(pq); >> dequeued = 0; >> } >> p->queue = PQ_NONE; >> TAILQ_REMOVE(&pq->pq_pl, p, plinks.q); >> dequeued--; >> } >> if (vm_page_free_prep(p, true)) >> continue; >> unlist: >> TAILQ_REMOVE(&object->memq, p, listq); >> } >> >> >> Please note that this is the code before r332974 Improve VM page queue scalability. >> I am not sure if r332974 + r333256 would fix the problem or if it just would get >> moved to a different place. >> >> Does this ring a bell to anyone who tinkered with that part of the VM code recently? > > This doesn't look familiar to me and I doubt that r332974 fixed the > underlying problem, whatever it is. I see. >> Looking a little bit further, I think that object->memq somehow got corrupted. >> memq contains just two elements and the reported element is not there. > > Based on the debugging session, it would be interesting to know if there > were any other threads somehow manipulating the (dead) object at the > time of the panic. I will check for this. > Among the panics that you observed, is it the same application that is > causing the crash in each case? I have two crash dumps right now and in both cases it's sh exec-ing grep. But I cannot imagine what could be so special about that. Actually, I see that the shell ran a long pipeline with many grep-s in it, so there were many exec-s and exits of grep, perhaps some of them concurrent. -- Andriy Gapon From owner-freebsd-current@freebsd.org Tue May 29 19:28: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 13F36F6FA53; Tue, 29 May 2018 19:28:59 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::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 9FDF67AE16; Tue, 29 May 2018 19:28:58 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40wP0m6pDpzDhTS; Tue, 29 May 2018 19:28:56 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id mV5fncUU8_J4; Tue, 29 May 2018 19:28:56 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40wP0m1mdCzDhBg; Tue, 29 May 2018 19:28:56 +0000 (UTC) Subject: Re: [RFC] Deprecation and removal of the drm2 driver From: Niclas Zeising To: freebsd-x11@freebsd.org, freebsd-current@freebsd.org References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> Message-ID: <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> Date: Tue, 29 May 2018 21:28:49 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 19:28:59 -0000 On 05/18/18 19:58, Niclas Zeising wrote: > [ Cross posted to freebsd-current@ and freebsd-x11@.=C2=A0 Please respe= ct=20 > reply-to and send all replies to freebsd-x11@.=C2=A0 Thanks! ] >=20 >=20 > Hi! > I propose that we remove the old drm2 driver (sys/dev/drm2) from=20 > FreeBSD.=C2=A0 I suggest the driver is marked as deprecated in 11.x and= =20 > removed from 12.0, as was done for other drivers recently.=C2=A0 Some=20 > background and rationale: >=20 > The drm2 driver was the original port of a KMS driver to FreeBSD.=C2=A0= It=20 > was done by Konstantin Belousov to support Intel graphics cards, and=20 > later extended by Jean-S=C3=A9bastien P=C3=A9dron as well as Konstantin= to match=20 > what's in Linux 3.8.=C2=A0 This included unstable support from Haswell,= but=20 > nothing newer than that. >=20 > For quite some time now we have had the graphics/drm-stable-kmod and=20 > graphics/drm-next-kmods which provides support for modern AMD and Intel= =20 > graphics cards.=C2=A0 These ports, together with the linuxkpi, or lkpi,= has=20 > made it significantly easier to port and update our graphics drivers.=20 > Further, these new drivers cover the same drivers as the old drm2 drive= r. >=20 > What does the community think?=C2=A0 Is there anyone still using the dr= m2=20 > driver on 12-CURRENT?=C2=A0 If so, what is preventing you from switchin= g to=20 > the port? >=20 Wow, this blew up quite a lot bigger than I anticipated. I'll try to=20 summarize the discussion a bit below and then suggest a way forward. The primary reasons we want to do this is because there are conflicts=20 between the new drm drivers in ports, and the drm drivers in base, since=20 they control the same hardware. It is hard to make conflicting drivers=20 to auto load in a consistent way. In order to improve the desktop=20 experience I'd like to see that graphics drivers are loaded on system=20 boot. There is also a push from upstream to have the xf86-video*=20 drivers stop loading driver kernel modules. It is also easier to keep a=20 port updated than keeping the base system updated, and updates can=20 propagate to multiple FreeBSD versions at once. This will also ensure=20 that all ports use the same firmware blobs. So, to the summary. A lot of people are using i386, and as such still=20 need the old drm drivers. There were also some reports about issues=20 with the drm-next/stable drivers, which needs investigating. Power is=20 another architecture that also is not supported by drm-next/stable,=20 although we hope to extend support to powerpc in the future. There was a=20 lot of discussion regarding making it into a port, or only excluding the=20 driver on amd64, and similar suggestions. To move forward, we'll do the following: Note that this is for current=20 only. We take the drm and drm2 drivers and make a port for it, maintained by=20 the graphics team (x11@). After a transition period, then the drivers=20 are removed from base. At the same time, pkg-messages are added to=20 relevant places to point people to the various available drm drivers. Regards --=20 Niclas Zeising FreeBSD graphics/x11 team From owner-freebsd-current@freebsd.org Tue May 29 21:29: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 988F0F77590; Tue, 29 May 2018 21:29:30 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F27347FECA; Tue, 29 May 2018 21:29:29 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-lf0-f67.google.com with SMTP id u4-v6so992067lff.3; Tue, 29 May 2018 14:29:29 -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=rLB4BNKisZC0lgEpnrmdnRtKBcw7NLz9hK480uQ3UE0=; b=Vtr06iPIESUs2nIa+zlnVHBkOrODixQwbQKJAQbDFNvFGCISxuS3yNmLjBXF1j3323 t8SVesmPHGvNFicVneKCIOXN2i2vXSaHMYtUjNY/P+/j+ilWiHgZiqmc1/6Y0+HT0+Wh j3G5O1KcGpaM8NAaKOYIvYAc8mbQpF0yf+ftPcTs5XOUmDfe4+f6KqIFu6+GHNpWUVUy 1nhW4V+B98N1c+p2di/oT84Y+6ZVU/WFwuLFM9x5HfeJZ+hBvfAc7Ak3iD8fbPZOLvtM E+J8yg1oTgSBgemLZVYtNjMkfHrVAngtaswE0yyaC23CZ5xZrf5RLSjtI/U3syb1YdoN tCUQ== X-Gm-Message-State: ALKqPweZY7XZKmp9/SNifM2ahGskSI7VmsQw9m5wzfG4fQfDLMr9CCce roUeHGtJ7V3DRu+cdLGky2AA/0T3 X-Google-Smtp-Source: ADUXVKJcHzevqT4Mm5Q6AFkHeudDe/UIS53yypDUu2PvFmENjgvMoz/V+TR12QrnV0PV71a5LWdDFA== X-Received: by 2002:a19:b2c2:: with SMTP id t63-v6mr5009lfk.27.1527627625103; Tue, 29 May 2018 14:00:25 -0700 (PDT) Received: from oxy (89-76-8-18.dynamic.chello.pl. [89.76.8.18]) by smtp.gmail.com with ESMTPSA id j8-v6sm2518507lja.21.2018.05.29.14.00.24 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 14:00:24 -0700 (PDT) Date: Tue, 29 May 2018 23:01:31 +0200 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: Niclas Zeising Cc: freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180529230131.211ff1da@oxy> In-Reply-To: <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 29 May 2018 21:29:30 -0000 On Tue, 29 May 2018 21:28:49 +0200 Niclas Zeising wrote: >On 05/18/18 19:58, Niclas Zeising wrote: >> [ Cross posted to freebsd-current@ and freebsd-x11@.=C2=A0 Please respect >> reply-to and send all replies to freebsd-x11@.=C2=A0 Thanks! ] >> >> [...] >> >> What does the community think?=C2=A0 Is there anyone still using the drm2 >> driver on 12-CURRENT?=C2=A0 If so, what is preventing you from switching= to >> the port? >> > > >Wow, this blew up quite a lot bigger than I anticipated. I'll try to >summarize the discussion a bit below and then suggest a way forward. > > [...] > >To move forward, we'll do the following: Note that this is for current >only. >We take the drm and drm2 drivers and make a port for it, maintained by >the graphics team (x11@). After a transition period, then the drivers >are removed from base. At the same time, pkg-messages are added to >relevant places to point people to the various available drm drivers. Let's also remember about our handbooks and those two wiki page: * https://wiki.freebsd.org/Graphics * https://wiki.freebsd.org/Graphics/FAQ From owner-freebsd-current@freebsd.org Tue May 29 23:40: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 5D647F7F06B for ; Tue, 29 May 2018 23:40:33 +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 DAF9D8464A; Tue, 29 May 2018 23:40:32 +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=1527637230; bh=ovG3GAX+G+36sxbCZTa0b9s+D/FXJCPgbgQVB/z YkQQ=; b=o3ujY/skMdTCZp9XAt0cVhRMVHbvv09Rf3dtof4L/7D11s5NV4cyJrq 1VnO0LRKEgjfdL7WdZFbvV5Zprdr+seYMwmjOLmn0nHglSlPVXrwoBVZkd/+dumL q0NGSG5OJp9SWPVZfpR7/IWQu38BTA9wotfrM1n0Lc5+3OvbsHWQ= 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 E3D9420309; Tue, 29 May 2018 19:40:30 -0400 (EDT) To: freebsd-current , mmacy@freebsd.org From: Michael Butler Subject: @SVN r334360 i386 build fails (pmc-related) Openpgp: preference=signencrypt Autocrypt: addr=imb@protected-networks.net; prefer-encrypt=mutual; keydata= xsDiBETHZAURBACJicNaIbVVVZahtQcdJeogtTLjCYAdj4kFMpy6Y3Ac19UNWDM+TrD4yFPi 5nc/pp9M/5Q4RNBr6a97fTYroTaq+vDwWdklOHwD2ZXs7FqwWOtVSIPT/rev5fUvwEF2VFYE sNDbpE5HHpP/oFUw5scEJZVyOBJSGvYb1IhV55NWswCgzkUGbG8A3s+oZXkHqTCYGW/seukD +wTo/L835xLpbTJxoxEKeGA3aWifSsRvpWWHyXye6sTkSN3SmtE9A8Pqmdb1dBEO0eOms6GD RamvCFgdvg2HesAv9l7L/7Mm9iKJs6uTAa+taIQslpumGh4PRc94IepVFzAa4Ef/FA4mWx9w P/EqNsKUPE2U5HI1decbopkxH/d/A/9Hupc10lPsXVMACd54/YZRsSTTcArheekm8qE/f8Hl 1Q7At+yuFgfMll4QPAhefnrLUanXF1bWtxG5PmaJktDYp3HOmy43giZgacgt+a3TVd6vu8Gs DnI4FOfYllq7mZFezMIulCWUYtnkMEXEeyzp39dygi7blPIjckWlQ2sc380rTWljaGFlbCBC dXRsZXIgPGltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0PsJgBBMRAgAgBQJEx2QFAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AACgkQQv9rrgRC1JL7mgCdEnPeo22kqT/bES+D78QSGhNR r8cAn2xOMeu6pBrc2tDY8Ky/70HBctmjzsFNBETHZA4QCACKbm/PMn4QcyDEvIn4MF+t2E1A zgiBAkPCMtWT1CcqeUj13OwNM8qJD/mBWjCZCnr1hKVbvzOmgKaM4uDCWIcSCdoDTJx1DqMx abr+EpHz1fL6aagEOKHz5sCYOkDXt3zzZ/5RBMdkEJwunXYtAbu5e68oty+d0DFzAM3pBp6l GC0TE3VutmFR/KK66rf0KB83YQBf/IAtyqsRIQPP9t0SLfJ+kqKXf73nvAUFEtb21gZSzhTm QP87QKyQvenE8o4PQ2tEslq2jICB7pGcqIrwP4o3Hl4V+HXi3lA26MMJ5rakQB2sKKWroPVQ BiRXO+W8Qf+0oQFq38oMXR5sPOs/AAMFB/sEKcjzvkwviZOsDElthxtgrmqUNKC9G/4Fw0tK k6fMynv+bcKz85k2uWOIfefUKBFoQ0SCphU4jquJENqqy6BPTkXePlIJok2/GkF7xtHm2FPq tTTuYmoBrGsls28Z9dn2LcBwFHz59SSWM9JFPIvFr9HCkKtp6zPUsJd5b02+0wgzDubTMQS9 M2LwGSh9xK6xl4MGgngl22b0TZDh5qHwmsywOX6SbGsQfeNpkptJ4gPjShypusFyF+pevnCM wTfUPCBd/AFbu2fHFQjA8sgkr5IqXuc4PoiIBXc9upoFpDqGkYssAKbzGcRsK94a8hRROJV9 bzPyYempIWaPXr2EwkkEGBECAAkFAkTHZA4CGwwACgkQQv9rrgRC1JKqhwCgsS3SHFrWg/xW A5PXgoua8GbPm7QAoK1rZ8tvEovm62uqv3GbwQ9G5jgy Message-ID: <155aef9d-cf82-6bb9-edbd-f8c6bb67d076@protected-networks.net> Date: Tue, 29 May 2018 19:40:30 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 29 May 2018 23:40:33 -0000 World build fails as follows: --- cmd_pmc_stat.o --- /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:274:48: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] fprintf(pmc_args.pa_printfile, "%16ld %s\n", cvals[CYCLES], stat_mode_names[CYCLES]); ~~~~~ ^~~~~~~~~~~~~ %16llu /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:275:73: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] fprintf(pmc_args.pa_printfile, "%16ld %s\t\t#\t%01.03f inst/cycle\n", cvals[INST], stat_mode_names[INST], ~~~~~ ^~~~~~~~~~~ %16llu /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:277:48: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] fprintf(pmc_args.pa_printfile, "%16ld %s\n", cvals[BR], stat_mode_names[BR]); --- all_subdir_usr.sbin/ntp --- --- all_subdir_usr.sbin/ntp/ntpdate --- ===> usr.sbin/ntp/ntpdate (all) --- all_subdir_usr.sbin/pmc --- ~~~~~ ^~~~~~~~~ %16llu /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:280:7: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] cvals[BR_MISS], stat_mode_names[BR_MISS], ^~~~~~~~~~~~~~ /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:284:7: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] cvals[BR_MISS], stat_mode_names[BR_MISS]); ^~~~~~~~~~~~~~ /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:285:48: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] fprintf(pmc_args.pa_printfile, "%16ld %s%s", cvals[CACHE], stat_mode_names[CACHE], ~~~~~ ^~~~~~~~~~~~ %16llu /usr/src/usr.sbin/pmc/cmd_pmc_stat.c:290:48: error: format specifies type 'long' but the argument has type 'uint64_t' (aka 'unsigned long long') [-Werror,-Wformat] fprintf(pmc_args.pa_printfile, "%16ld %s%s", cvals[CACHE_MISS], stat_mode_names[CACHE_MISS], ~~~~~ ^~~~~~~~~~~~~~~~~ %16llu 7 errors generated. *** [cmd_pmc_stat.o] Error code 1 imb From owner-freebsd-current@freebsd.org Wed May 30 00:40: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 378B9FC7F4D; Wed, 30 May 2018 00:40:02 +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 B095C8693D; Wed, 30 May 2018 00:40:01 +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 w4U0dvw9067744; Tue, 29 May 2018 17:39:57 -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 w4U0dvPx067743; Tue, 29 May 2018 17:39:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805300039.w4U0dvPx067743@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: <20180529230131.211ff1da@oxy> To: Mateusz Piotrowski <0mp@freebsd.org> Date: Tue, 29 May 2018 17:39:57 -0700 (PDT) CC: Niclas Zeising , freebsd-x11@freebsd.org, freebsd-current@freebsd.org 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.26 Precedence: 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, 30 May 2018 00:40:02 -0000 [ Charset UTF-8 unsupported, converting... ] > On Tue, 29 May 2018 21:28:49 +0200 > Niclas Zeising wrote: > > >On 05/18/18 19:58, Niclas Zeising wrote: > >> [ Cross posted to freebsd-current@ and freebsd-x11@.? Please respect > >> reply-to and send all replies to freebsd-x11@.? Thanks! ] > >> > >> [...] > >> > >> What does the community think?? Is there anyone still using the drm2 > >> driver on 12-CURRENT?? If so, what is preventing you from switching to > >> the port? > >> > > > > > >Wow, this blew up quite a lot bigger than I anticipated. I'll try to > >summarize the discussion a bit below and then suggest a way forward. > > > > [...] > > > >To move forward, we'll do the following: Note that this is for current > >only. > >We take the drm and drm2 drivers and make a port for it, maintained by > >the graphics team (x11@). After a transition period, then the drivers > >are removed from base. At the same time, pkg-messages are added to > >relevant places to point people to the various available drm drivers. > > Let's also remember about our handbooks and those two wiki page: > * https://wiki.freebsd.org/Graphics > * https://wiki.freebsd.org/Graphics/FAQ This one has a bit rot on this claim: "The i915kms kernel-side driver is already built into the generic FreeBSD kernel. No need to install anything. ' That is slightly miss leading, it is not "built into the generic", it is avaliable as a module, at least on 11 and 12, not sure on 10 as I dont have 10 running any place anymore. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed May 30 00:51: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 E00B5FC8DB3; Wed, 30 May 2018 00:51:05 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: from mail-lf0-f67.google.com (mail-lf0-f67.google.com [209.85.215.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 572AE870A6; Wed, 30 May 2018 00:51:05 +0000 (UTC) (envelope-from mpp302@gmail.com) Received: by mail-lf0-f67.google.com with SMTP id v135-v6so1539372lfa.9; Tue, 29 May 2018 17:51: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=24xl0qJOOz7d6ppEadNBNow+hUsqOL9w1T6sFkcmkIs=; b=BoxCgpEyo8vAcDHGiBnTWnczwBngrGBD4YPl/MeToN714szkd2t4aHrOpqlnGydCDt yXk8THWJHMd14MRVHp5cmLuFruRRV+Zk86JL263yaD15yYqmYwC9xntANg/+r4QQExER 0LoiqQiY+qFEMlBrSJBOFF+JeLG4BLQguBEgNDasulLUCO9IrHcShnTceuC/szRKIGQ0 Sqzy5KKdMBtvP3yG4S+MVF/RtXLMAsylkulo9qHoi88HSFV44tPi8yRCdMztlDKYChei KkF33BVe3otY2o8As2hc4J7TzMr2BjExfQZwRqsScnTstqdCP7N1/718Dp7u/ncHMS4t kiVg== X-Gm-Message-State: ALKqPwc94Dj6sSSlna/xHJnH377f4+co/gArIbTCl5IlfZyLuHAGCEMa H8zKTIHCSWVgkHTehgQ8HwswNovF9vk= X-Google-Smtp-Source: ADUXVKJIgq9ZK0bgIWLXifCYtxbsNxS22uQtEgkMpvsUjXbuCwHdg0/p8dg7aaWRVUj4m/4sgyN9Sw== X-Received: by 2002:a2e:404d:: with SMTP id n74-v6mr403799lja.6.1527641463628; Tue, 29 May 2018 17:51:03 -0700 (PDT) Received: from oxy (89-76-8-18.dynamic.chello.pl. [89.76.8.18]) by smtp.gmail.com with ESMTPSA id h201-v6sm7582143lfh.34.2018.05.29.17.51.03 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 29 May 2018 17:51:03 -0700 (PDT) Date: Wed, 30 May 2018 02:52:08 +0200 From: Mateusz Piotrowski <0mp@FreeBSD.org> To: "Rodney W. Grimes" Cc: Niclas Zeising , freebsd-x11@freebsd.org, freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180530025208.7e966684@oxy> In-Reply-To: <201805300039.w4U0dvPx067743@pdx.rh.CN85.dnsmgr.net> References: <20180529230131.211ff1da@oxy> <201805300039.w4U0dvPx067743@pdx.rh.CN85.dnsmgr.net> 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.26 Precedence: 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, 30 May 2018 00:51:06 -0000 On Tue, 29 May 2018 17:39:57 -0700 (PDT) "Rodney W. Grimes" wrote: >> Let's also remember about our handbooks and those two wiki page: >> * https://wiki.freebsd.org/Graphics >> * https://wiki.freebsd.org/Graphics/FAQ >This one has a bit rot on this claim: > "The i915kms kernel-side driver is already built into the > generic FreeBSD kernel. No need to install anything. ' > >That is slightly miss leading, it is not "built into the generic", >it is avaliable as a module, at least on 11 and 12, not sure on >10 as I dont have 10 running any place anymore. Good catch! Thanks. From owner-freebsd-current@freebsd.org Wed May 30 10:38: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 43E1DF7F1A7; Wed, 30 May 2018 10:38:03 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from dnvrco-cmomta02.email.rr.com (dnvrco-outbound-snat.email.rr.com [107.14.73.231]) (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 B99D67B3DA; Wed, 30 May 2018 10:38:02 +0000 (UTC) (envelope-from mueller6722@twc.com) Received: from localhost ([96.28.161.151]) by cmsmtp with ESMTP id NyPofWQa0lFijNyPrfeLqf; Wed, 30 May 2018 10:33:15 +0000 Date: Wed, 30 May 2018 10:33:02 +0000 From: "Thomas Mueller" To: freebsd-current@freebsd.org CC: freebsd-x11@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> X-CMAE-Envelope: MS4wfJomCTLUct+KbYm7UC1J5O+I7l/PMmB36VG+GUtn8AXlBQA/KEI4heQZ6oCZJkVQpNCG5yBWPCYA2pEMmANApFInkyNTEBONKRktSZlew5R7f9/nkBhV VZKAtNK9lIVA0pNWwOVZkFwJWy0P3a3+twFAPf5e3eDDv4Uwc6RcPcBiH2JB02bDvWZhtG4y0w8IzpW2E3Twdv/RHb4cweS7uwA= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 10:38:03 -0000 > Wow, this blew up quite a lot bigger than I anticipated. I'll try to > summarize the discussion a bit below and then suggest a way forward. > The primary reasons we want to do this is because there are conflicts between > the new drm drivers in ports, and the drm drivers in base, since they control > the same hardware. It is hard to make conflicting drivers to auto load in a > consistent way. In order to improve the desktop experience I'd like to see > that graphics drivers are loaded on system boot. There is also a push from > upstream to have the xf86-video* drivers stop loading driver kernel modules. > It is also easier to keep a port updated than keeping the base system updated, > and updates can propagate to multiple FreeBSD versions at once. This will > also ensure that all ports use the same firmware blobs. > So, to the summary. A lot of people are using i386, and as such still need > the old drm drivers. There were also some reports about issues with the > drm-next/stable drivers, which needs investigating. Power is another > architecture that also is not supported by drm-next/stable, although we hope > to extend support to powerpc in the future. There was a lot of discussion > regarding making it into a port, or only excluding the driver on amd64, and > similar suggestions. > To move forward, we'll do the following: Note that this is for current only. > We take the drm and drm2 drivers and make a port for it, maintained by the > graphics team (x11@). After a transition period, then the drivers are removed > from base. At the same time, pkg-messages are added to relevant places to > point people to the various available drm drivers. > Regards > Niclas Zeising > FreeBSD graphics/x11 team One reason I can think of to maintain i386 compatibility is to be able to run wine and possibly other software that requires i386 compatibility. That said, I currently have no active FreeBSD i386 installation, and probably won't get around to it anytime soon. I believe Linux can run wine on an amd64 multilib installation, but FreeBSD is not up to that yet. For the above purpose, keeping drm and drm2 as a port might be good enough, as opposed to being part of base. i386 is not dead. While some Linux distros (such as Arch) and DragonFlyBSD have quit i386 support, Haiku maintains 32-bit support to be able to run old BeOS software as well as newer things. Tom From owner-freebsd-current@freebsd.org Wed May 30 13:47: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 36CEBEFDEC9 for ; Wed, 30 May 2018 13:47:34 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F19B883EEE for ; Wed, 30 May 2018 13:47:32 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: by mail-it0-x244.google.com with SMTP id 144-v6so23157885iti.5 for ; Wed, 30 May 2018 06:47:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=IURdYtqG73CSlUEhcocpRJMDUJZbx/XPoGbHhwmuZ7U=; b=Z1S/m5maiy2qT5Xt3t6zZuLCmSbqeC6USaxBsu1lTIU5p96qhtuv8HHPxbRcWqn9jL dDyHaddX0EOkyTyDBoMAfmKYVIwpYfPFC5x4vebN1/FrTu1xJn2vsxVXXrVyzq1FbDLK J/J1GaHFhYt2mHjAGcwVq7lEi91P0K8MSE3EI= 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=IURdYtqG73CSlUEhcocpRJMDUJZbx/XPoGbHhwmuZ7U=; b=EdVQZ6F0/ypvzn30k/k2zoadsnsk3Hb8KzbQ9F5TMd4vX1DRFM0+9JwbMT/Z4f3EtG Gh4A4FEvPYeBeAhX9BXxNqhLmCBT4b6DkkiRm2Eu1timVqlZ5o/uDfhQiMYyg/50XPAz VZ7Oe/0ZqvvrNN7H++jzHI+xnqEhgP0rG2Fs+xRCaWHs4BW9HIiU1f+kY2co5B1rhOfI kRMRA9KdROr8B8IyTEHDouismCSJCfgrfysBk9grfS2SI/SkbL+jzK5pA9zYVCEhs6OT 977IdEwMsZwjClp1C0bCXOnZ55u5MSgGeldeCdzx3WXBUdGOCg3Dn5mieug3xzBxzVtN aSkA== X-Gm-Message-State: ALKqPwezeQZhKbrW/1Go5hBxl22BxI1ZpbpSYByt27Xzaiih0QvLNFLl 1woWXLx5Tq56hpVvvmZUzVa/xfrG3/YxkT8Yn65C0w== X-Google-Smtp-Source: ADUXVKKSqpi2CT/kKaM+5TKDmtcgPi6mk+nr5jS6NfhEW+/wJt41+q7ogoHSC7i+QpdZXVxw3luZFAvkM8McXV/XzmA= X-Received: by 2002:a24:1f4a:: with SMTP id d71-v6mr1715913itd.53.1527688051699; Wed, 30 May 2018 06:47:31 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:a1cd:0:0:0:0:0 with HTTP; Wed, 30 May 2018 06:47:31 -0700 (PDT) In-Reply-To: <5b0e8026.1c69fb81.100eb.ce66SMTPIN_ADDED_MISSING@mx.google.com> References: <3a5edc5c-3caa-830b-4bd9-53ff52feb8a7@freebsd.org> <50b21ccf-f89d-cfd0-fb23-39ba80732143@freebsd.org> <5b0e8026.1c69fb81.100eb.ce66SMTPIN_ADDED_MISSING@mx.google.com> From: Kevin Bowling Date: Wed, 30 May 2018 06:47:31 -0700 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Thomas Mueller Cc: freebsd-current@freebsd.org, x11-list freebsd Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 13:47:34 -0000 32b compat is quite different than i386 arch. It makes sense to maintain 32b compat for quite a while. On Wed, May 30, 2018 at 3:33 AM, Thomas Mueller wrote: >> Wow, this blew up quite a lot bigger than I anticipated. I'll try to >> summarize the discussion a bit below and then suggest a way forward. > >> The primary reasons we want to do this is because there are conflicts between >> the new drm drivers in ports, and the drm drivers in base, since they control >> the same hardware. It is hard to make conflicting drivers to auto load in a >> consistent way. In order to improve the desktop experience I'd like to see >> that graphics drivers are loaded on system boot. There is also a push from >> upstream to have the xf86-video* drivers stop loading driver kernel modules. >> It is also easier to keep a port updated than keeping the base system updated, >> and updates can propagate to multiple FreeBSD versions at once. This will >> also ensure that all ports use the same firmware blobs. > >> So, to the summary. A lot of people are using i386, and as such still need >> the old drm drivers. There were also some reports about issues with the >> drm-next/stable drivers, which needs investigating. Power is another >> architecture that also is not supported by drm-next/stable, although we hope >> to extend support to powerpc in the future. There was a lot of discussion >> regarding making it into a port, or only excluding the driver on amd64, and >> similar suggestions. > >> To move forward, we'll do the following: Note that this is for current only. >> We take the drm and drm2 drivers and make a port for it, maintained by the >> graphics team (x11@). After a transition period, then the drivers are removed >> from base. At the same time, pkg-messages are added to relevant places to >> point people to the various available drm drivers. > >> Regards > >> Niclas Zeising >> FreeBSD graphics/x11 team > > One reason I can think of to maintain i386 compatibility is to be able to run wine and possibly other software that requires i386 compatibility. > > That said, I currently have no active FreeBSD i386 installation, and probably won't get around to it anytime soon. > > I believe Linux can run wine on an amd64 multilib installation, but FreeBSD is not up to that yet. > > For the above purpose, keeping drm and drm2 as a port might be good enough, as opposed to being part of base. > > i386 is not dead. While some Linux distros (such as Arch) and DragonFlyBSD have quit i386 support, Haiku maintains 32-bit support to be able to run old BeOS software as well as newer things. > > Tom > > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed May 30 14:56:45 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 BCAA0F73577 for ; Wed, 30 May 2018 14:56:44 +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 G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EA99D873BF for ; Wed, 30 May 2018 14:56:43 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x22c.google.com with SMTP id j186-v6so23791427ita.5 for ; Wed, 30 May 2018 07:56:43 -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=/CHZxbAyuR37+tt+76LljKanzgyQNlDRg/7vz72DTuE=; b=qc2CnTziAlOfsfpubwM0JkEUHmH2YxoB0/tz8kAnC6cKz+sQuLuqqFO5Omnetrduc/ NuDV+DebCCsCt4pKykvijnnlCIog+UW8E/+leBg+mJSngqEe+dBgJJ+WmFGAFkLtZH/E fntkdyt7qrFXGqTbTmL6VoUTMuousk2X2pppcQLAw4VhnBzaTUI44jxfqN3iRAwpH980 J344oaoGUHUePNS7qp1uLPSUB1v55xztzjjYcH/BOlRBxjtFSz3nlKBxeuPmDOvBhd1L pFKAarb+I73PB/Y1w6GjRch6sBNzafXE/q2sgkkdDzSKq8EEsb+c7WkqFDQ1W/fn5vNu LoAQ== 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=/CHZxbAyuR37+tt+76LljKanzgyQNlDRg/7vz72DTuE=; b=eQM/AKE4l22dKDK+EgfjxFba4cRIiMYt6IVqwNEw5kPyLwuXKxjrIpsBASQFh68Qgo GMW2/02uQmRZYSkYBT+7nE37QffOjrCI8T0JwtY+FyWL++/+NysRB7unrS77z5KHTQX7 rZQdc5tgYfV4Qd515vKg8kPKK7upH98iVfV8Gyc1ZyU29PpqK1TtwABriBwM6dlOPii4 UhFtoQ4zOmxicyZuOFLncoZmgIVWc0pcg/rJj+QbyS9nWHDXb16+h4y6DpMSrL3UMvMr SfWWRC+/CbiQjfpJ248e8f2Gt5YIXQbJn0RrBmLqy/mTePBygXhe3YToEPOrXtfA9z3o 0uIw== X-Gm-Message-State: APt69E1ho6NQyNDl3D2PV82aQbAXRjdMToGRMNNTyHKEQH8POaamD3+N DBIdNc2y5JhsBskQhtgWJ5ael8G0COlgI/eNqkI= X-Google-Smtp-Source: ADUXVKJOc9boAZEEPQCLeZt5oF5fGJKkAqDDMzgU5kLB/QZO3uotLIQXLt4d79hJhSLIlwYni5UzQGghP3LbhZfTLmc= X-Received: by 2002:a24:4293:: with SMTP id i141-v6mr1878711itb.54.1527692203428; Wed, 30 May 2018 07:56:43 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:87c4:0:0:0:0:0 with HTTP; Wed, 30 May 2018 07:56:22 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Wed, 30 May 2018 10:56:22 -0400 X-Google-Sender-Auth: WCT1FQd8U0UgGRUnM8t01uygzDc Message-ID: Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) To: Philip Homburg Cc: Johannes Lundberg , FreeBSD Current , Andreas Nilsson Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 14:56:45 -0000 On 25 May 2018 at 04:51, Philip Homburg wrote: > > I have bad news and some good news. > > The bad news is that with this image the USB stick doesn't get recognized as > a boot device. Same as with the 11.2-BETA2 images. At least it's not a regression. > The good news is that if I completely recreate the MBR, keeping the layout of > the partitions the same, then the USB stick is recognized. Strange. Can you try an updated test image of mine (https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) or this week's -CURRENT snapshot? From owner-freebsd-current@freebsd.org Wed May 30 15:29: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 7499BF76A5D for ; Wed, 30 May 2018 15:29:59 +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 EFCC1692E7; Wed, 30 May 2018 15:29:58 +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 w4UFTvIs072535; Wed, 30 May 2018 08:29:57 -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 w4UFTvJe072534; Wed, 30 May 2018 08:29:57 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805301529.w4UFTvJe072534@pdx.rh.CN85.dnsmgr.net> Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) In-Reply-To: To: Ed Maste Date: Wed, 30 May 2018 08:29:57 -0700 (PDT) CC: Philip Homburg , Johannes Lundberg , FreeBSD Current , Andreas Nilsson 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.26 Precedence: 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, 30 May 2018 15:29:59 -0000 > On 25 May 2018 at 04:51, Philip Homburg wrote: > > > > I have bad news and some good news. > > > > The bad news is that with this image the USB stick doesn't get recognized as > > a boot device. Same as with the 11.2-BETA2 images. > > At least it's not a regression. > > > The good news is that if I completely recreate the MBR, keeping the layout of > > the partitions the same, then the USB stick is recognized. > > Strange. Can you try an updated test image of mine > (https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) or this > week's -CURRENT snapshot? What version(s) of the snapshots sould be tested? disc1.iso? dvd1.iso? memstick? -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Wed May 30 15:36:46 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 5513FF7751D for ; Wed, 30 May 2018 15:36:46 +0000 (UTC) (envelope-from gjb@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 02C27699D3; Wed, 30 May 2018 15:36:46 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from 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 did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id AD1C7AAD; Wed, 30 May 2018 15:36:45 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 30 May 2018 15:36:44 +0000 From: Glen Barber To: "Rodney W. Grimes" Cc: Ed Maste , Philip Homburg , Johannes Lundberg , FreeBSD Current , Andreas Nilsson Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180530153644.GD97814@FreeBSD.org> References: <201805301529.w4UFTvJe072534@pdx.rh.CN85.dnsmgr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="9zSXsLTf0vkW971A" Content-Disposition: inline In-Reply-To: <201805301529.w4UFTvJe072534@pdx.rh.CN85.dnsmgr.net> User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 15:36:46 -0000 --9zSXsLTf0vkW971A Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 30, 2018 at 08:29:57AM -0700, Rodney W. Grimes wrote: > > On 25 May 2018 at 04:51, Philip Homburg wro= te: > > > > > > I have bad news and some good news. > > > > > > The bad news is that with this image the USB stick doesn't get recogn= ized as > > > a boot device. Same as with the 11.2-BETA2 images. > >=20 > > At least it's not a regression. > >=20 > > > The good news is that if I completely recreate the MBR, keeping the l= ayout of > > > the partitions the same, then the USB stick is recognized. > >=20 > > Strange. Can you try an updated test image of mine > > (https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) or this > > week's -CURRENT snapshot? >=20 > What version(s) of the snapshots sould be tested? > disc1.iso? dvd1.iso? memstick? >=20 The *memstick.img for amd64, from this week. (20180529 r334337) https://lists.freebsd.org/pipermail/freebsd-snapshots/2018-May/000411.html Glen --9zSXsLTf0vkW971A Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlsOxQsACgkQAxRYpUeP 4pMVshAAnAHF/9JoSdc98ayE7uLnmgYxGeWQj/vyqmU8oaZqsOnrDEjW7CZfW/Wo agthpVbqYtuMJJcpiDsQ50LEGNgAEk3aaWITrttO4faOGqgFbOnKiSqyqXJGJoa3 XKn5qn70Gpbu6fnvkOOO6XNBpxGWreA7+YHRWcoydR2hRqN7fG1X7IrWUF6/C+xy qtULtv+sgjmZcFvcJnpaHgdKgjrpmi1ZfFESVFFzhP6CFTBnSlR2nrNX0qFdxjcu 19rFxpVfx8YXdPXyEZDKWRjdmzQcu3ckq1j6VKlumuCuTxKXg40fwjx99K+DT3GB Mvd1ZmP8R8eB2ZDKfIdvRuYVsHwzOoDVfGXEETRIpSjOdNQ7oHfYOq+ef4IIRmaC x33ToVlt3CubjJzy/911PskmLheX5C73wVCr/j3J+3TlgWZibYycdHxQqsEqSO+X Cf66Rsb4aNcIRv+FAFPf3nti+ShsV6WfLc7yRwhA6CKxokWtJK4si202UfJGUzSw e/nmiiaW4Qw6uBcAdmlg20GHBSmfnqALNFo6R7dNzZV18X2QGCk3+49tGCP36opA 02ojyWbd0OCQ+cohpHFazSJvKZpWE0BkczZL2mXP6eB5w42sqyVmXHHhzKqwtitE PVpV/c0XZnKHMKK5W1pZjNlUoWZDQV3yNsdv2AOaXNPrnjncJwY= =OZtM -----END PGP SIGNATURE----- --9zSXsLTf0vkW971A-- From owner-freebsd-current@freebsd.org Wed May 30 15:50: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 7A9A6F788E6; Wed, 30 May 2018 15:50:41 +0000 (UTC) (envelope-from gjb@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 31EE86A709; Wed, 30 May 2018 15:50:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from 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 did not present a certificate) by freefall.freebsd.org (Postfix) with ESMTPS id E986E10E2; Wed, 30 May 2018 15:50:40 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Wed, 30 May 2018 15:50:39 +0000 From: Glen Barber To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: Ed Maste Subject: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-ID: <20180530155039.GE97814@FreeBSD.org> Reply-To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="1SQmhf2mF2YjsYvc" Content-Disposition: inline User-Agent: Mutt/1.9.1 (2017-09-22) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 15:50:41 -0000 --1SQmhf2mF2YjsYvc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, Could folks please help boot-test the most recent 12.0-CURRENT amd64 memstick images on various hardware? Note, this is not a request to install 12.0-CURRENT, only a boot-test with various system knobs tweaked. The most recent images are available at: https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we would like to get this included in the upcoming 11.2-RELEASE if the change that had been committed addresses several boot issues reported recently. Please help test, and report back (both successes and failures). Thanks, Glen --1SQmhf2mF2YjsYvc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjRJAPC5sqwhs9k2jAxRYpUeP4pMFAlsOyE8ACgkQAxRYpUeP 4pPYpQ//V1MXYEdzUR69mydSHsEkmy53rcQ9wzx+tbwGnhXVaSsxD7y5J1034mOQ GAfgJHwVxwEvUW1F6nyE9xa/SheQqrQIg/9bJdJqu1L14I7x34tEbuDEA0Z5Heac 7Q0uuvgJw3QZ+ypnGxJFwaf5+mjeMSN8WceZwl8ObFr3ZSFzeIK8o6nEZ3F5W+hV rSZrlRnld91NOVBDlwo6j5AlXUBjLD8n8B1+wXAO+VDRzN6+fBCJ2PwhIWS7X71K UkB82jx3dyf/trcVpN7zJCdW1vDmbp/j1Y6oI4eXidNoIlA4/xuR8ErUKnW36zNS R4u0AkaaYffO7sVxX2MK8y9P5E+YXFOHnBxJatl6nGoOw8+Qmo0wsK3Bg30N7zof +9a5V8A1U6zV90qT2DfgYPO5rvKdOIwpTzjwZVRSkGvfBHOusLEsEB/0sTAxd+k+ ylwNhPWCQxSCPF8dcwUhkniLRx90hUxx9CtmXkEhMTV1y7COdzrqX/tCc1dQc4ze lVaBTuC1n8igXBPi8YUoF/76HfsLcCyYPwN9ubjWO95BDQXpn+vu/lyImCtQ1DSJ /sEIXh+R5ceJGOh2NmIPPTG89M2fFCb1vuZvCHCU0v/SXEdgUQycmkEekbWnLFqJ grBKNNsiQosIu/9IunaPFC1itvqg5eywgAwK6lu0uIXfJVZvwAc= =CdUK -----END PGP SIGNATURE----- --1SQmhf2mF2YjsYvc-- From owner-freebsd-current@freebsd.org Wed May 30 21: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 58733F71B41 for ; Wed, 30 May 2018 21:51:12 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout1.freenet.de (mout1.freenet.de [IPv6:2001:748:100:40::2:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "*.freenet.de", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B445A7CB4C for ; Wed, 30 May 2018 21:51:11 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.142] (helo=mjail2.freenet.de) by mout1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fO8zt-0007K6-HX for freebsd-current@freebsd.org; Wed, 30 May 2018 23:51:09 +0200 Received: from [::1] (port=48430 helo=mjail2.freenet.de) by mjail2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fO8zt-0001em-Bp for freebsd-current@freebsd.org; Wed, 30 May 2018 23:51:09 +0200 Received: from mx7.freenet.de ([195.4.92.17]:58610) by mjail2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fO8xs-0000Ye-95 for freebsd-current@freebsd.org; Wed, 30 May 2018 23:49:04 +0200 Received: from p4fd9f0de.dip0.t-ipconnect.de ([79.217.240.222]:26235 helo=freebsd-t450.fritz.box) by mx7.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1fO8xs-0002Zo-6l for freebsd-current@freebsd.org; Wed, 30 May 2018 23:49:04 +0200 Date: Wed, 30 May 2018 23:49:02 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Re: Fatal trap 12 Message-ID: <20180530214901.GA61021@freebsd-t450.fritz.box> References: <20180526114642.GA17171@freebsd-t450.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180526114642.GA17171@freebsd-t450.fritz.box> User-Agent: Mutt/1.10.0 (2018-05-17) X-Spam-score: -3.4 X-Spamreport: Action: no action Symbol: RCVD_COUNT_ONE(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: MIME_GOOD(-0.10) Symbol: RCVD_TLS_ALL(0.00) Symbol: BAYES_HAM(-0.34) Symbol: FREEMAIL_ENVFROM(0.00) Symbol: TO_DN_NONE(0.00) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: ASN(0.00) Symbol: RCPT_COUNT_ONE(0.00) Symbol: FREEMAIL_FROM(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: NEURAL_HAM(-3.00) Message-ID: 20180530214901.GA61021@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 79.217.240.222!26235 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 21:51:12 -0000 On Sat, May 26, 2018 at 01:46:42PM +0200, Manuel Stühn wrote: >Since upgrading my Lenovo T450 from r333740 to r334167 I'm experiencing >several "Fatal traps 12". Before the update i did not have any of those. >In all cases the traps occured some time after resume. > I tried to debug this further by building different kernel versions (all GENERIC-NODEBUG). The last working revision is r334117, the first not working is r334123. Revisions 334118-334122 of the kernel did not build, so i cannot try these. Any ideas what could cause these issue? -- Manuel From owner-freebsd-current@freebsd.org Wed May 30 21:52: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 6D256F71DB4 for ; Wed, 30 May 2018 21:52:17 +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 D84EA7CED2; Wed, 30 May 2018 21:52:16 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([77.14.42.184]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LuP19-1gM3Ot3uL9-011k83; Wed, 30 May 2018 23:52:05 +0200 Date: Wed, 30 May 2018 23:51:29 +0200 From: "O. Hartmann" Cc: "Rodney W. Grimes" , Glen Barber , Philip Homburg , "K. Macy" , "A. Wilcox" , FreeBSD Current , Ed Maste Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> In-Reply-To: <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:DfvUNHPaknYO3X3Bw1FwYqr9eOim2qo9Y7R70llxdLREKuIog7p iAZcgnXfPWx23Ea60AMs1fOKxb2B5Cn8ohg/vdm1kz5eA0cDBF0pOk6yS8Ce6BQR3N90jQf bed1mMlf3d0wTebs6L1a2NKGmmHCYd83nQg93pQJAoCuEJmWcD6pk3LcndC/Lp/omqJ/Uax Ft49XMIL4UKHW+O8vXndw== X-UI-Out-Filterresults: notjunk:1;V01:K0:px53Boab/2c=:C0LxXiahD8BfwaepwwrSDl 5JcaviWXD8uXNlMS2L1avsykwYeLAvb8LIWmQyt4VrOpl9Pz8+weOp4Ah/b58ftHOjkdliph/ x+WX5OYn4U+bmehQKt13QvLYQSObjdXIpTSja54poiDuJ4wPYoqXJDNgp4ZhXHK3u+ox6XnEG VS4baFSY/TQJNnDaxselFQFl35GPoG9XFql+SpAnHsVrWAAY2zquMgTfxdBhpBx2b2DC4GOLe zyZq4Ga0wQPLvJBaPSd/ciK890vvSv3v2YeGgZticLJYHHAN+GWXcIMBhHFO12uY3w55sIwyC MNkpy1NbGZiySANXZO5ShaMQcM7kTdS4O6pVebJca5Yclq8nZh9F0H2lPOGAB24KnKv6CtBdJ mt/9rhw7BPBhOa+9KccLNMRwGCsqehcKJWlmpmV8TqytpymtlpuA86aEXhLxxJHXXl5qGPmQ7 REkyRLeBMDkU6v3/SfanEXESPecqZ1fAQ4u0q2H9ezgSX51sd2kpdg1iviePgUagti8nA1pa2 MWSFGj0VwgHWlg5FlPRwq52PuVf+/Eg+mWrmZ3dagocvtRx2vW9jGtrb9JY6q36iRK9yZCq9M 8NmxBukr+CSG3i19s4LbSCWmXgtKXR3Fw7rT/Ze5b3PlMQ3TmsQmH3lD8yfi8TJyXU1t5mn/0 Fs0qR/qoaeUG72Y34QV6kQmp+6JckavlH4KSfyuzFjCRjdNH19dNdKpYhwGnfuVOdpFxI+ZV+ kfbv53C6H4lgHEo+D0uWjW5iWFfpJ3mF4uOOd2O2+9vxmJag/7TBNr07nMxyYhDEzxpxstGgI Kzxl9Ep X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 21:52:17 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCkFtIFRo dSwgMjQgTWF5IDIwMTggMDk6MTA6MTAgLTA3MDAgKFBEVCkNCiJSb2RuZXkgVy4gR3JpbWVzIiA8 ZnJlZWJzZC1yd2dAcGR4LnJoLkNOODUuZG5zbWdyLm5ldD4gc2NocmllYjoNCg0KPiAtLSBTdGFy dCBvZiBQR1Agc2lnbmVkIHNlY3Rpb24uDQo+ID4gT24gVGh1LCBNYXkgMjQsIDIwMTggYXQgMDg6 MjI6MTJBTSAtMDcwMCwgUm9kbmV5IFcuIEdyaW1lcyB3cm90ZTogIA0KPiA+ID4gPiBPbiBXZWQs IE1heSAyMywgMjAxOCBhdCAxMTo0ODozOEFNICswMjAwLCBQaGlsaXAgSG9tYnVyZyB3cm90ZTog IA0KPiA+ID4gPiA+ID5BbHNvIGFzIHRoZSBNb29yZSdzIGxhdyBjdXJ2ZSBmbGF0dGVucyBleHBl Y3QgdGhlIGxpZmUgb2YgdGhlc2UNCj4gPiA+ID4gPiA+b2xkZXIsIGJ1dCBub3Qgc28gb2xkLCBt YWNoaW5lcyB0byBsaXZlIHF1aWV0IHNvbWUgdGltZS4gIEkNCj4gPiA+ID4gPiA+YmVsaWV2ZSB3 ZSBhcmUgdGFsa2luZyBzYW5keSBicmlkZ2UgYW5kIGVhcmxpZXI/ICBJZiB0aGF0IGlzDQo+ID4g PiA+ID4gPmNvcnJldCBTYW5keSBicmlkZ2UgaXMgc3RpbGwgYSB2ZXJ5IHZpYWJsZSBzeXN0ZW0u ICANCj4gPiA+ID4gPiANCj4gPiA+ID4gPiBJIG5vdGljZWQgdGhpcyBsYWNrIG9mIGxvdmUgZm9y IG9sZGVyIHN5c3RlbXMgcmVjZW50bHkuIA0KPiA+ID4gPiA+IA0KPiA+ID4gPiA+IEkgd2FudGVk IHRvIHVzZSBhbiBvbGRlciBEZWxsIHNlcnZlciB0byB0ZXN0IHRoZSAxMS4yIEJFVEFzIGFuZCBS Q3MuDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gVHVybnMgb3V0LCB5b3UgY2FuJ3QgaW5zdGFsbCBG cmVlQlNEIHVzaW5nIGEgVVNCIHN0aWNrIGltYWdlIGJlY2F1c2UgdGhlDQo+ID4gPiA+ID4gQklP UyBvbmx5IHN1cHBvcnQgTUJSLiBObyBpZGVhIHdoeSBNQlIgc3VwcG9ydCB3YXMgZHJvcHBlZCBm b3IgdGhlIFVTQiBpbWFnZXMuDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gSW4gdGhlIGVuZCBJIGhh ZCB0byBmaW5kIGEgQ0QgYnVybmVyLCBhbmQgYWZ0ZXIgYSBjb3VwbGUgb2YgdHJpZXMgbWFuYWdl ZCB0bw0KPiA+ID4gPiA+IGluc3RhbGwgZnJvbSBDRC4NCj4gPiA+ID4gPiANCj4gPiA+ID4gPiBB ZnRlciB0aGF0LCBteSBhbnNpYmxlIHBsYXlib29rcyBzdGFydGVkIGZhaWxpbmcgYmVjYXVzZSAv Ym9vdC9sb2FkZXIuY29uZiANCj4gPiA+ID4gPiBpcyBhYnNlbnQgaWYgeW91IGJvb3QgZnJvbSB6 ZnMgaW4gY29tYmluYXRpb24gd2l0aCBNQlIuDQo+ID4gPiA+ID4gDQo+ID4gPiA+ID4gUGl0eS4g VGhpcyBvbGRlciBzZXJ2ZXIgaGFyZHdhcmUgaXMgZ3JlYXQgZm9yIHRyeWluZyBvdXQgbmV3IHJl bGVhc2VzLCBwbGF5IA0KPiA+ID4gPiA+IHdpdGggemZzLCBldGMuICANCj4gPiA+ID4gDQo+ID4g PiA+IFRoZSBkaXNjMS5pc28gKGFzIHdlbGwgYXMgYm9vdG9ubHkuaXNvIGFuZCBkdmQxLmlzbykg aW1hZ2VzIGFyZSBub3cNCj4gPiA+ID4gYnVpbHQgYXMgaHlicmlkIGltYWdlcywgc3VwcG9ydGlu ZyBib3RoIE1CUiBhbmQgR1BULCBhcyB3ZWxsIGFzIGJlaW5nDQo+ID4gPiA+IHdyaXR0ZW4gdG8g YSBmbGFzaCBkcml2ZSAobGlrZSBtZW1zdGljay5pbWcpIGFzIHdlbGwgYXMgYSBDRC4gIA0KPiA+ ID4gDQo+ID4gPiBUbyBjbGFyaWZ5IGEgbWlub3IgcG9pbnQgaGVyZSwgYXJlIHRoZSBhbWQ2NCBk aXNjMS5pc28gaW1hZ2VzIG9yDQo+ID4gPiBib3RoIHRoZSBhbWQ2NCBhbmQgaTM4NiBkaXNrMS5p c28gaW1hZ2VzIGJlaW5nIGJ1aWx0IGFzICJoeWJyaWQiPw0KPiA+ID4gICANCj4gPiANCj4gPiBP bmx5IGFtZDY0LiAgaTM4NiBkb2VzIG5vdCBoYXZlIFVFRkktL0dQVC1yZWxhdGVkIGJvb3QgaXNz dWVzLiAgDQo+IA0KPiBIZXJlIGlzIGEgZGF0YSBwb2ludDoNCj4gDQo+IFRlc3Qgc3lzdGVtIGlz IERlbGwgUjcxMCwNCj4gRmlyc3QgYXR0ZW1wdCBpcyB3aXRoIEJJT1MgaW4gQm9vdCBtb2RlOiBC aW9zIA0KPiBTZWNvbmQgYXR0ZW1wdCBpcyB3aXRoIEJJT1MgaW4gQm9vdCBtb2RlOiBVRUZJDQo+ IA0KPiBBdHRlbXRwZWQgdG8gYm9vdCBhbWQ2NCB2ZXJzaW9uOg0KPiBTY3JlZW4gZ29lcyB3aGl0 ZSBiYWNrZ3JvdW5kLCB0ZXh0IGFwcGVhcnMgKHllcywgd2F5IGluZGVudGVkKQ0KPiAgICAgICAg ICAgICAgICAgICAgICAgICBCVFggdmVyc2lvbiBpcyAxLjAyDQo+IENvbnNvbGVzOiBpbnRlcm5h bCB2aWRlby9rZXlib2FyZA0KPiBfDQo+ICANCj4gVGhhdCBsYXN0IF8gaXMgYSBibGlua2luZyBj dXJzb3IsIHN5c3RlbSBpcyBodW5nLCBkb2VzIHJlcHNvbmQgdG8gQy1BLWRlbA0KPiAgDQo+ICAN Cj4gU2Vjb25kIGF0dGVtcHQ6DQo+IFdvcmtzIHByb3Blcmx5DQo+ICANCj4gDQo+IEkgYW0gZ29p bmcgYWZ0ZXIgRWQgTWFzdGUncyBwb3N0ZWQgYnVpbGQgaW1hZ2UgaW4gdGhlIG90aGVyIHRocmVh ZCBub3cuLi4NCj4gDQo+IA0KPiA+ICAgDQo+ID4gPiBBcyB0aGlzIGlzIHdoYXQgSSBzZWUgb24g bXkgc3lzdGVtOg0KPiA+ID4gcm9vdEB4MjMwYTovaG9tZS9JU08veCAjIGZpbGUgRnJlZUJTRC0x MS4yLUJFVEEyLSoNCj4gPiA+IEZyZWVCU0QtMTEuMi1CRVRBMi1hbWQ2NC1kaXNjMS5pc286IERP Uy9NQlIgYm9vdCBzZWN0b3I7IHBhcnRpdGlvbiAxIDogSUQ9MHhlZSwNCj4gPiA+IHN0YXJ0LUNI UyAoMHgwLDAsMiksIGVuZC1DSFMgKDB4M2ZmLDI1NSw2MyksIHN0YXJ0c2VjdG9yIDEsIDE0NzI2 OTUgc2VjdG9ycw0KPiA+ID4gRnJlZUJTRC0xMS4yLUJFVEEyLWkzODYtZGlzYzEuaXNvOiAgSVNP IDk2NjAgQ0QtUk9NIGZpbGVzeXN0ZW0gZGF0YQ0KPiA+ID4gJzExXzJfQkVUQTJfSTM4Nl9DRCcg KGJvb3RhYmxlKSANCj4gPiA+ID4gTUJSIHN1cHBvcnQgd2FzIGluaXRpYWxseSByZW1vdmVkIGZy b20gdGhlIG1lbXN0aWNrIGluc3RhbGxlciwgYXMgaXQgaXMNCj4gPiA+ID4gbm90IGNvbXBhdGli bGUgd2l0aCBzb21lIFVFRkkgaW1wbGVtZW50YXRpb25zLiAgKE9yLCBhdCBsZWFzdCB0aGF0IGlz IG15DQo+ID4gPiA+IHVuZGVyc3RhbmRpbmcsIGJhc2VkIG9uIG15IGxpbWl0ZWQgaW50aW1hdGUg a25vd2xlZGdlIG9mIFVFRkkuKQ0KPiA+ID4gPiAgIA0KPiA+IA0KPiA+IEdsZW4NCj4gPiAgIA0K PiAtLSBFbmQgb2YgUEdQIHNlY3Rpb24sIFBHUCBmYWlsZWQhDQo+IA0KDQpUb2RheSwgSSB0cmll ZCB0byBlbGltaW5hdGUgRnJlZUJTRCdzIG5hdGl2ZSBLTVMgZHJtMiBieSBpbnN0YWxsaW5nDQpn cmFwaGljcy9kcm0tc3RhYmxlLWttb2QgKHBvcnRzIHRyZWUgYXQgcmV2aXNpb24gNDcxMTcyKSBv biBDVVJSRU5UIChGcmVlQlNEIDEyLjAtQ1VSUkVOVA0KIzQ2IHIzMzQ0MDE6IFdlZCBNYXkgMzAg MjM6MzI6NDUgQ0VTVCAyMDE4IGFtZDY0LCBDVVNUT00ga2VybmVsKS4NCg0KVGhlIGhhcmR3YXJl IGlzIGEgcHJlc3VtYWJseSBVRUZJIGNhcGFibGUgQVNST0NLIFo3Ny1Qcm80TSAobGF0ZXN0IGZp cm13YXJlIGF2YWlsYWJsZQ0KZnJvbSBsYXRlIDIwMTMpIGVxdWlwdGVkIHdpdGggYSBYRU9OIEl2 eUJyaWRnZToNCg0KQ1BVOiBJbnRlbChSKSBYZW9uKFIpIENQVSBFMy0xMjQ1IFYyIEAgMy40MEdI eiAoMzQwMC4wOS1NSHogSzgtY2xhc3MgQ1BVKQ0KICBPcmlnaW49IkdlbnVpbmVJbnRlbCIgIElk PTB4MzA2YTkgIEZhbWlseT0weDYgIE1vZGVsPTB4M2EgIFN0ZXBwaW5nPTkNCiAgRmVhdHVyZXM9 MHhiZmViZmJmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LEFQSUMsU0VQLE1U UlIsUEdFLE1DQSxDTU9WLFBBVCxQU0UzNixDTEZMVVNILERUUyxBQ1BJLE1NWCxGWFNSLFNTRSxT U0UyLFNTLEhUVCxUTSxQQkU+DQogIEZlYXR1cmVzMj0weDdmYmFlM2ZmPFNTRTMsUENMTVVMUURR LERURVM2NCxNT04sRFNfQ1BMLFZNWCxTTVgsRVNULFRNMixTU1NFMyxDWDE2LHhUUFIsUERDTSxQ Q0lELFNTRTQuMSxTU0U0LjIseDJBUElDLFBPUENOVCxUU0NETFQsQUVTTkksWFNBVkUsT1NYU0FW RSxBVlgsRjE2QyxSRFJBTkQ+DQogIEFNRCBGZWF0dXJlcz0weDI4MTAwODAwPFNZU0NBTEwsTlgs UkRUU0NQLExNPg0KICBBTUQgRmVhdHVyZXMyPTB4MTxMQUhGPg0KICBTdHJ1Y3R1cmVkIEV4dGVu ZGVkIEZlYXR1cmVzPTB4MjgxPEZTR1NCQVNFLFNNRVAsRVJNUz4NCiAgWFNBVkUgRmVhdHVyZXM9 MHgxPFhTQVZFT1BUPg0KICBWVC14OiBQQVQsSExULE1URixQQVVTRSxFUFQsVUcsVlBJRA0KICBU U0M6IFAtc3RhdGUgaW52YXJpYW50LCBwZXJmb3JtYW5jZSBzdGF0aXN0aWNzDQpyZWFsIG1lbW9y eSAgPSAxNzE3OTg2OTE4NCAoMTYzODQgTUIpDQphdmFpbCBtZW1vcnkgPSAxNjI5NTEzNzI4MCAo MTU1NDAgTUIpDQpFdmVudCB0aW1lciAiTEFQSUMiIHF1YWxpdHkgNjAwDQpBQ1BJIEFQSUMgVGFi bGU6IDxBTEFTS0EgQSBNIEk+DQpGcmVlQlNEL1NNUDogTXVsdGlwcm9jZXNzb3IgU3lzdGVtIERl dGVjdGVkOiA4IENQVXMNCg0KDQpUaGUgYm94IGlzbid0IGNhcGFibGUgb2YgYm9vdGluZyBGcmVl QlNEIGluIFVFRkkgKHdoaWxlIExpbnV4IGFuZCBXaW5kb3dzIHNlZW1zIHRvIHdvcmspLg0KU28g SSdtIHN0dWNrIHdpdGggQklPUy4NCg0KTG9hZGluZyBpOTE1a21zLmtvL2RybTIua28gb24gdGhl IHN5c3RlbSBwdXQgdGhlIGNvbnNvbGUgaW4gYSBoaWdoLXJlc29sdXRpb24gbW9kZQ0KaW5zdGVh ZCBvZiB0aGlzIGNyYXAgODB4MjUgYW5jaWVudCBjb25zb2xlIGltbWVkaWF0ZWx5Lg0KDQpMb2Fk aW5nIGdyYXBoaWNzL2RybS1zdGFibGUta21vZCBhcyByZXF1ZXN0ZWQgKHZpYSByYy5jb25mLmxv Y2FsKSBlbmRzIHVwIGluIGEgdHJhcA0KMTIvY3Jhc2guIFZlcnkgbmljZSBmb3Igc3VjaCBhbiBv bGQgaGFyZHdhcmUuIGdyYXBoaWNzL2RybS1uZXh0LWttb2QgZG9lcyBsb2FkIHdpdGhvdXQNCmNy YXNoaW5nIHRoZSBzeXN0ZW0gLSBidXQgdGhlIGNvbnNvbGUgaXMgc3R1Y2sgaW4gdGhlIGNsdW1z eSA4MHgyNSBtb2RlLg0KDQpTbyB3aHkgc2hvdWxkIEkgdm90ZSBmb3Igbm9uLXdvcmtpbmcgZHJp dmVycyB0byByZXBsYWNlIHBlcmZlY3RseSB3b3JraW5nIG9uZXM/DQoNCm9oDQoNCg0KLSAtLSAN Ck8uIEhhcnRtYW5uDQoNCkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJlcm1p dHRsdW5nIG1laW5lciBEYXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1hcmt0 LSBvZGVyIE1laW51bmdzZm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJFR0lO IFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0MyVC84NlRyUzUy OGZ5RmhZbEFVQ1d3OGMvQUFLQ1JEUzUyOGZ5RmhZDQpsQmw3QWYwUjd5bU96a1dwN0djcXltaFVp T2dmeTNxdlRTbUhZZ2JUell4c0Q1NEdFSWZvQU12SDFwSEZwNHlMDQpiME5ZeDlIUitCVTNkNkdB ZjBYcTBzcTc4a01GQWY5S1VoRE1MVUhmMDYrQVNKa1MydVB5citqWkJaZUJsVFJjDQpJc0UwUGF4 RXJiWXk4WUxKaFdYZ3JTWUNNMUtISVppc0JOVU9MR2NrY0NJZ1R2dTBNUnNRDQo9eUZ6Vw0KLS0t LS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Wed May 30 22:08: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 A53B4F739D9 for ; Wed, 30 May 2018 22:08:36 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 10D247DEBF; Wed, 30 May 2018 22:08:35 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fO9Gj-0000I3C; Thu, 31 May 2018 00:08:33 +0200 Message-Id: To: Ed Maste Cc: Johannes Lundberg , FreeBSD Current , Andreas Nilsson Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com References: In-reply-to: Your message of "Wed, 30 May 2018 10:56:22 -0400 ." Date: Thu, 31 May 2018 00:08:32 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 30 May 2018 22:08:36 -0000 >Strange. Can you try an updated test image of mine >(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) That gives a 404. I have the strong suspision that your previous image doesn't get recognized as bootable because the C/H/S values are not filled in. From owner-freebsd-current@freebsd.org Thu May 31 00:25:57 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 90E03F7F268 for ; Thu, 31 May 2018 00:25:57 +0000 (UTC) (envelope-from oldriverbsd9@gmail.com) Received: from mail-vk0-x241.google.com (mail-vk0-x241.google.com [IPv6:2607:f8b0:400c:c05::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2306682E6D for ; Thu, 31 May 2018 00:25:57 +0000 (UTC) (envelope-from oldriverbsd9@gmail.com) Received: by mail-vk0-x241.google.com with SMTP id y137-v6so12273461vkd.6 for ; Wed, 30 May 2018 17:25:57 -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=ZWZxHsGHWrIRy9g7RGHGkbUwsygD07duI2IGB2ALdVs=; b=RUUxqHzaJDoWcex7/NgWmC2acQg8XUPTJiPLWAYkoGapQ7fQdYfKswwteI4ptqPv9p LCgi4bIoVK5LBrlMZ8FyuxuMtk7+K1wWzlhD3LfGbEAYPec8cpFASw7s0wh8RrLq7SRN f/g54uhRXt1ezPNf9H2i9bUXiEGzewDKjCsgWMpI8vfiyxirIk7zMkmxKcj2bJrWZHZM nkGRdTiKYJQLusoVemR88vaJoOo9E0ox28K920Y9Fp4I5QUA4cxoGqhyVn4aJXRQsLgo 7vgeyVbkfSl/98k1jn1TIw7EnKYkL1DmZf4Xi/Uv2sNJUE+x1vnpFEB/9UhidoS79Q84 x7xg== 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=ZWZxHsGHWrIRy9g7RGHGkbUwsygD07duI2IGB2ALdVs=; b=qYNUpjYDhWA7FWjzYlHFZeyzob3/EmZfq2DJ36101csi74qhUefy3j4LAIFzqXO0XW ByjdFt4PaUNncsg8iHbVN8P2UAxLJ7y/5iwThBGg1FCoS0uWArcXvOwqHH61gnpJqkTZ VC10XyHZcOUy3ZgTsBS9D2fDN/p9p4tvHC0p8uGIQsAWQjZ9347DDNpqFLgf37Fcs6zV O+ggIHhB9M0M2nJlfvjsuyY6txJ/pi6mXZSjpNUF+a8douq+xs1t3ue4o4/j/lLNeTLg rLqkqX5MaKgITXhlZDJMO8hFlgRg8II2oGShSHJvjKArXWRn1knKRPV8feadJKJ2Ulyy ILCQ== X-Gm-Message-State: ALKqPwescq5iOa1pCXnuRi7XjReIKcsX6rHMtcSXdNTC1E/8GoFkb9xi JMHM182Wnvx6w05N2Uiz1xj/vjdycshac7QMwJ7NyqCuob4= X-Google-Smtp-Source: ADUXVKIs6ew2bml23dVXywQzljjI1F7loqsBQIaBMN5G94iRysUInWfdirvAQQQ57zM0+KgwoWKlIklEa2v6eHbvYzw= X-Received: by 2002:a1f:ff1a:: with SMTP id p26-v6mr2896274vki.124.1527726355938; Wed, 30 May 2018 17:25:55 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a67:1746:0:0:0:0:0 with HTTP; Wed, 30 May 2018 17:25:55 -0700 (PDT) From: "Dave M." Date: Thu, 31 May 2018 00:25:55 +0000 Message-ID: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 00:25:57 -0000 On Wed, 30 May 2018 15:50:39 +0000, Glen Barber Wrote, >Hi, > > >Could folks please help boot-test the most recent 12.0-CURRENT amd64 >memstick images on various hardware? Note, this is not a request to >install 12.0-CURRENT, only a boot-test with various system knobs tweaked. >The most recent images are available at: >https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img >https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > >We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we >would like to get this included in the upcoming 11.2-RELEASE if the >change that had been committed addresses several boot issues reported >recently. >Please help test, and report back (both successes and failures). >Thanks, >Glen I did boot with CSM/BIOS/legacy mode on, Manufacturer: ASUSTeK COMPUTER INC, Product Name: K30AD_M31AD_M51AD_M32AD, BIOS information : Vendor: American Megatrends Inc. Version: 0601 Release Date: 06/09/2014 BIOS Revision: 4.6 Machine class: amd64 CPU Model: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz and that went well, also went into the shell with a gpart show, again all good! -- Dave M. From owner-freebsd-current@freebsd.org Thu May 31 00:58: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 97504FC82DA for ; Thu, 31 May 2018 00:58:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27C5D8431B for ; Thu, 31 May 2018 00:58:35 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-it0-x234.google.com with SMTP id l6-v6so12587955iti.2 for ; Wed, 30 May 2018 17:58:35 -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=VHt8JmnAj6i7am2TnHDJ3oUAs9DANAzhANqKhERz2DU=; b=Gm3xWVvOimvazXBl7uFgRi4Bbdec4ZdjgMXkvUjazGGIxPA3pv9kNWvbWdBFqlKSM7 GFyVps2kpLWOZcZ8FwHqKfqWPJl7yLtCWbQjIH5SWKLeb4g3r0BZsDKlxSdE6kj0Cayz 0i4pAvRijrI3FbPu6sJwUQyU5TCne8TKCrhEKNS4BcPyh4eP2wevHspXNc2nHcC8l47T YldQq2xeeBsYpjJJ4pxi0Rv//+wCigGbjz7rVHAhXkDaI3nECVKqJZg0xhVf4HZ3ucds 89UHA1EenFOS+NAG7dAZKhdkMmX0IJN5o15AAUmex+4iPg/SvhuhPEvuPCR14dGWUj5q w9jw== 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=VHt8JmnAj6i7am2TnHDJ3oUAs9DANAzhANqKhERz2DU=; b=jUurChZ767UR+7slOtdXvc1Q8lKMAQ5jOxLMgyE5q1+/I/fpeBg7fMbWIryF74z7w3 tePNaCKVYx6VRTtcLptabMK2uLYaXchYBfPmr4OohrwIyf6J1Vu0CrdkxnLouJYAQ/nF FxQQNiQryiq6lC+2gHPFbdvzasLg7DbKPMfj/VkKJnJDyVeLOQ0LfP9V3SJmlih3cARX WdleKrgFXpjQau2t5iaxSulcJmAP6m8Hae1a3dmMWN6OFTxvOMAwRTOqiZ7Rl+YRhBAu 4u+w/UtFSpFFZEWnU308/lnhOPPQs816DjowXTd/Pmz3FBHPfhyv6rqTVekgORWM92w/ PABw== X-Gm-Message-State: APt69E0rozI7QWA+wzi9b4lCaYT7hGcVvhbHR1jHQEfNrtfKOSytzT/u ls4vvVpqKYkz2vY5dCyoGN4IBxkp2nCWz5JCJUI= X-Google-Smtp-Source: ADUXVKKCP4z2eBZxOH3CqN0+v5Giu9B4ORQgTwgmcB0I8PFLZ1MOHlnPDwYgMYAal+o7O4HpAK27QzHRjkzAgaLmdlo= X-Received: by 2002:a24:2111:: with SMTP id e17-v6mr3899003ita.114.1527728314543; Wed, 30 May 2018 17:58:34 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 2002:a6b:87c4:0:0:0:0:0 with HTTP; Wed, 30 May 2018 17:58:14 -0700 (PDT) In-Reply-To: References: From: Ed Maste Date: Wed, 30 May 2018 20:58:14 -0400 X-Google-Sender-Auth: LFM0WQQw_HC57DCC2pPKqncnaqQ Message-ID: Subject: Re: Boot USB memstick with MBR (WAS: Re: [RFC] Deprecation and removal of the drm2 driver) To: Philip Homburg Cc: Johannes Lundberg , FreeBSD Current , Andreas Nilsson Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 00:58:35 -0000 On 30 May 2018 at 18:08, Philip Homburg wrote: >>Strange. Can you try an updated test image of mine >>(https://people.freebsd.org/~emaste/mini-image-2018-05-28.xz) Oops - that should have been https://people.freebsd.org/~emaste/mini-image-2018-05-28-amd64.xz But the most recent snapshot images have been built the same way now: https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img From owner-freebsd-current@freebsd.org Thu May 31 02:04: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 6BD30EF424E for ; Thu, 31 May 2018 02:04:22 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E009B87A9F; Thu, 31 May 2018 02:04:21 +0000 (UTC) (envelope-from jonlooney@gmail.com) Received: by mail-wm0-f43.google.com with SMTP id x2-v6so43668003wmh.5; Wed, 30 May 2018 19:04:21 -0700 (PDT) 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=ixtbzleMwgQjSyjd38tNmkosUBQLeXU+1yciXLjJir8=; b=GIj6LEK5rgG7mD68D+0gui79bRjglNIq+zRssiiCc7k+ymG0mGtT/pK6Ls7qwE0wvX nrbe50GlhWclP4mI8YeNO1pJrc3bQ69LYre+SQDNCLlk51/L1nGHC68AYQCjO+eb3bSx 5cyajiFWK0S4V6MMfxJ90TG00UNpdL5bY+Ou71Db6am/+UrC64k3qQ5VaTvrY2jyXKi6 0HDRrnAi7PLDGBIiHYXKLFBREq9/2VBe87d6QvXkmA9TMKVI9G+scRDcpKkHDVPveVNa V3LXQPZ0Id0AkPikvvw/2VXF0lld6Otz685SoJchq7ksdQWZRDn74pK1FiqOy/poCU4b VB4w== X-Gm-Message-State: ALKqPwdfRxf3PZ/ALkJgRgnQjpjt1GyMZ4ZAQjbbuY4skNre7/uMKD+v /EDDiGhpk8rza8to0nov/rKhF0d+ X-Google-Smtp-Source: ADUXVKKUaa7Zb9cgZQa6a1vaOvGWDoYnj0aVtMANvZo0iQvpvrWDMRdHh86R3pkZ6cu0HkIU989vfA== X-Received: by 2002:a50:cfca:: with SMTP id i10-v6mr5800550edk.35.1527732255206; Wed, 30 May 2018 19:04:15 -0700 (PDT) Received: from mail-wm0-f52.google.com (mail-wm0-f52.google.com. [74.125.82.52]) by smtp.gmail.com with ESMTPSA id r48-v6sm21029369edd.16.2018.05.30.19.04.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 30 May 2018 19:04:14 -0700 (PDT) Received: by mail-wm0-f52.google.com with SMTP id x2-v6so43667970wmh.5; Wed, 30 May 2018 19:04:14 -0700 (PDT) X-Received: by 2002:a1c:170f:: with SMTP id 15-v6mr2925443wmx.90.1527732254393; Wed, 30 May 2018 19:04:14 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:c50c:0:0:0:0:0 with HTTP; Wed, 30 May 2018 19:04:13 -0700 (PDT) In-Reply-To: References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> From: "Jonathan T. Looney" Date: Wed, 30 May 2018 22:04:13 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 To: Andriy Gapon Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 02:04:22 -0000 On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon wrote: > > [ping] > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > Does this panic ring a bell to anyone? > > Has it already been fixed? > > Thank you! > Is there any chance that r333703 fixes this problem for you? It fixes a race that can manifest itself in other ways. I'm honestly not sure whether it could also cause this problem. Jonathan From owner-freebsd-current@freebsd.org Thu May 31 07:10: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 21ABFFC772D for ; Thu, 31 May 2018 07:10:50 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 79674742E6; Thu, 31 May 2018 07:10:49 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f46.google.com with SMTP id 36-v6so6205608lfr.11; Thu, 31 May 2018 00:10:49 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=tYPf2PvIxkSArfUu4ADv9+LYb7FX8BaNZK8XIvMq//A=; b=HaC0ns0gOhL30H/XsBsGmju7Y4iNbj0R8cAJn9fQvJcPaGz54Paasc1pN/JpvNeHbB LPC5leLucQ3PlFGJq+fcfyEj5XPexphjHDE7qCWQVO/QUeselaah5tTMmmlKpAQEr7V8 PoQyJZPDANAsAYs9IZwYd7kmGiVwems2fXBauyvVZeJoEpaNQwzizF7Oqqq7qF31UhTw NjqHNo57E3Q27MZPib3/DVTlSCzBnbG6kFw5th1ZDqJ9iOwVKuVGAAZS6jjyqgbLhdOU 5AWrKswnGY/qPUuxNwsCD74oPHbMOZQiq43P2RWb7dm+3bonjjk4c8gQIXOnlDj2rySe rdeA== X-Gm-Message-State: ALKqPwcMgJ8yAjeAyAzsbJQC/dGcjbioksF4Y0H3SPvQa/7uNmN836qO 9dmVE15cH6ouRekc9XZGk5R3Gj1j X-Google-Smtp-Source: ADUXVKISyTJPz8xnNbRTHdAWgD56kntRjB/e4FWNMhyS+TCtSgfUEywLSs5sdOpVCOF7ah47ru5QQg== X-Received: by 2002:a2e:80c1:: with SMTP id r1-v6mr4513332ljg.85.1527750641751; Thu, 31 May 2018 00:10:41 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id w15-v6sm140406lfe.45.2018.05.31.00.10.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 00:10:41 -0700 (PDT) Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 To: "Jonathan T. Looney" Cc: FreeBSD Current References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> Date: Thu, 31 May 2018 10:10:40 +0300 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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 07:10:50 -0000 On 31/05/2018 05:04, Jonathan T. Looney wrote: > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon > wrote: > > > [ping] > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > Does this panic ring a bell to anyone? > > Has it already been fixed? > > Thank you! > > > Is there any chance that r333703 fixes this problem for you? It fixes a race > that can manifest itself in other ways. I'm honestly not sure whether it could > also cause this problem. Thank you for the suggestion. I guess it's worth trying that fix. I'll report back in a while. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 31 07:29: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 49B58FC916C for ; Thu, 31 May 2018 07:29:09 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [88.99.82.50]) (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 D643174C27; Thu, 31 May 2018 07:29:08 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id E4CAB260338; Thu, 31 May 2018 09:29:05 +0200 (CEST) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: "O. Hartmann" Cc: "Rodney W. Grimes" , Glen Barber , Philip Homburg , "K. Macy" , "A. Wilcox" , FreeBSD Current , Ed Maste References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> From: Hans Petter Selasky Message-ID: <24a94651-f516-485d-36f4-0937824ca3d7@selasky.org> Date: Thu, 31 May 2018 09:28:52 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> 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.26 Precedence: 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, 31 May 2018 07:29:09 -0000 On 05/30/18 23:51, O. Hartmann wrote: > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up in a trap > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does load without > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > So why should I vote for non-working drivers to replace perfectly working ones? Usually the crashes you get are low hanging fruit. Why not get the backtrace and resolve the crash? It should take less than 10 minutes. --HPS From owner-freebsd-current@freebsd.org Thu May 31 07:35: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 1B5B5FC9C2A for ; Thu, 31 May 2018 07:35:23 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com [IPv6:2a00:1450:400c:c09::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8822E753D3; Thu, 31 May 2018 07:35:22 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wm0-x244.google.com with SMTP id r15-v6so24463822wmc.1; Thu, 31 May 2018 00:35:22 -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=kxemJCt05hBAKntgVopK5ZTZJy2E0aL0EejUpztx/sc=; b=Me2c4woBggdO13tDEKuPVH+AwpqMGQ4/OazHc3b5wwVq2cspTNEOKv00t0UI0HhbqM nQ7hjrsdwfOR/deb0Xg46m83QhnoVJUvOOs8ed0YFzC4MUMF/pJI8pwGVtcqfsplztVi EMAwn+vEEJYyRrj1d+5X1LS6qGupdUOXW7svkVrN2R++RH5vBcJcz91P1vhGc00Yxt+O LA4dKQDtTRKcvFgb10PCf6XJbTpw3I/p3yPiiA0rIKbSCdFoHPPFyFV7fb3fgVgGoWqy Q0mVTlC+0qdvRm1XVsbPY8DJaV4Mp09lNKj5zbHFj6DEJiQl+uSjKq00NhnPyt8TgZLi hIZA== 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=kxemJCt05hBAKntgVopK5ZTZJy2E0aL0EejUpztx/sc=; b=pDg0M7xfPCtFSM33b3uFaju4bafrW+eWdwnaRdB4pyGDElORialHSjkQhG6WxsG4EY Tp4GyY6dxwgmFWK3C52Vw1GD1KFuy8esQMx+Gy8MdCRLa0fpdqTlH3N67wGE0HguclnV Ed1On7CSNJ95SE4RALDWXhl+ncRLQd9xbk+e4UNyK+JaDZNWKhQmlGAZL6v1SevUQlQX YaaumqUgmWWWk+78YtTtUcnfIiBax+yIiGyfN3uoj2fi+8AsILz2Fqgn1u8bccb/A0c/ 99t912EugB6WWGPHsIrRxZxZuUwJ6NdsHDTDHbFrisKeBstuhTUZldI4z/DHHV47FNeJ dRqg== X-Gm-Message-State: ALKqPwczLdbtXf4iZG5kgaB4EwE2/kmta2rA+4xwSYSiJzy9OCd54TYW T0ikzQDVBvd2VUF7/ovpVzQEU3/+YGKOTq419CM= X-Google-Smtp-Source: ADUXVKIM6oAuQDjPYXGDbGZAscWxP+FLBkMy5eJPWi0TAbTDgf3wysUpkWS7COsDMwDkDbGSAF1CSCHHphmoqIeDTbQ= X-Received: by 2002:a1c:f714:: with SMTP id v20-v6mr3686910wmh.73.1527752121335; Thu, 31 May 2018 00:35:21 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> In-Reply-To: <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> From: Johannes Lundberg Date: Thu, 31 May 2018 08:34:44 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: ohartmann@walstatt.org Cc: freebsd-rwg@pdx.rh.cn85.dnsmgr.net, gjb@freebsd.org, Philip Homburg , "K. Macy" , AWilcox@wilcox-tech.com, freebsd-current , Ed Maste Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 07:35:23 -0000 On Wed, May 30, 2018 at 10:57 PM O. Hartmann wrote= : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > "Rodney W. Grimes" schrieb: > > > -- Start of PGP signed section. > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > > > >Also as the Moore's law curve flattens expect the life of thes= e > > > > > > >older, but not so old, machines to live quiet some time. I > > > > > > >believe we are talking sandy bridge and earlier? If that is > > > > > > >corret Sandy bridge is still a very viable system. > > > > > > > > > > > > I noticed this lack of love for older systems recently. > > > > > > > > > > > > I wanted to use an older Dell server to test the 11.2 BETAs and > RCs. > > > > > > > > > > > > Turns out, you can't install FreeBSD using a USB stick image > because the > > > > > > BIOS only support MBR. No idea why MBR support was dropped for > the USB images. > > > > > > > > > > > > In the end I had to find a CD burner, and after a couple of > tries managed to > > > > > > install from CD. > > > > > > > > > > > > After that, my ansible playbooks started failing because > /boot/loader.conf > > > > > > is absent if you boot from zfs in combination with MBR. > > > > > > > > > > > > Pity. This older server hardware is great for trying out new > releases, play > > > > > > with zfs, etc. > > > > > > > > > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are n= ow > > > > > built as hybrid images, supporting both MBR and GPT, as well as > being > > > > > written to a flash drive (like memstick.img) as well as a CD. > > > > > > > > To clarify a minor point here, are the amd64 disc1.iso images or > > > > both the amd64 and i386 disk1.iso images being built as "hybrid"? > > > > > > > > > > Only amd64. i386 does not have UEFI-/GPT-related boot issues. > > > > Here is a data point: > > > > Test system is Dell R710, > > First attempt is with BIOS in Boot mode: Bios > > Second attempt is with BIOS in Boot mode: UEFI > > > > Attemtped to boot amd64 version: > > Screen goes white background, text appears (yes, way indented) > > BTX version is 1.02 > > Consoles: internal video/keyboard > > _ > > > > That last _ is a blinking cursor, system is hung, does repsond to C-A-d= el > > > > > > Second attempt: > > Works properly > > > > > > I am going after Ed Maste's posted build image in the other thread now.= .. > > > > > > > > > > > As this is what I see on my system: > > > > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > > > > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition = 1 > : ID=3D0xee, > > > > start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 > sectors > > > > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data > > > > '11_2_BETA2_I386_CD' (bootable) > > > > > MBR support was initially removed from the memstick installer, as > it is > > > > > not compatible with some UEFI implementations. (Or, at least tha= t > is my > > > > > understanding, based on my limited intimate knowledge of UEFI.) > > > > > > > > > > > Glen > > > > > -- End of PGP section, PGP failed! > > > > Today, I tried to eliminate FreeBSD's native KMS drm2 by installing > graphics/drm-stable-kmod (ports tree at revision 471172) on CURRENT > (FreeBSD 12.0-CURRENT > #46 r334401: Wed May 30 23:32:45 CEST 2018 amd64, CUSTOM kernel). > > The hardware is a presumably UEFI capable ASROCK Z77-Pro4M (latest > firmware available > from late 2013) equipted with a XEON IvyBridge: > > CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class CPU) > Origin=3D"GenuineIntel" Id=3D0x306a9 Family=3D0x6 Model=3D0x3a Step= ping=3D9 > > Features=3D0xbfebfbff > > Features2=3D0x7fbae3ff > AMD Features=3D0x28100800 > AMD Features2=3D0x1 > Structured Extended Features=3D0x281 > XSAVE Features=3D0x1 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics > real memory =3D 17179869184 (16384 MB) > avail memory =3D 16295137280 (15540 MB) > Event timer "LAPIC" quality 600 > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > The box isn't capable of booting FreeBSD in UEFI (while Linux and Windows > seems to work). > So I'm stuck with BIOS. > > Loading i915kms.ko/drm2.ko on the system put the console in a > high-resolution mode > instead of this crap 80x25 ancient console immediately. > > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up > in a trap > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does > load without > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > So why should I vote for non-working drivers to replace perfectly working > ones? > > oh > > We're not replacing anything. We are moving the older drm1 and drm2 from kernel to ports to make it easier for the majority of the users to load the correct driver without conflicts. We have updated drm-stable-kmod so that it now works on some older amd64 system also covered by drm2 but as always, ymmv. drm2 will later be available as drm-legacy-kmod or something like that (name to be announced later). Simply use/install the one that works best for you. > > - -- > O. Hartmann > > Ich widerspreche der Nutzung oder =C3=9Cbermittlung meiner Daten f=C3=BCr > Werbezwecke oder f=C3=BCr die Markt- oder Meinungsforschung (=C2=A7 28 Ab= s. 4 BDSG). > -----BEGIN PGP SIGNATURE----- > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWw8c/AAKCRDS528fyFhY > lBl7Af0R7ymOzkWp7GcqymhUiOgfy3qvTSmHYgbTzYxsD54GEIfoAMvH1pHFp4yL > b0NYx9HR+BU3d6GAf0Xq0sq78kMFAf9KUhDMLUHf06+ASJkS2uPyr+jZBZeBlTRc > IsE0PaxErbYy8YLJhWXgrSYCM1KHIZisBNUOLGckcCIgTvu0MRsQ > =3DyFzW > -----END PGP SIGNATURE----- > _______________________________________________ > 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 May 31 07:41: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 AAC71FCA991; Thu, 31 May 2018 07:41:58 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) (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 4131075D30; Thu, 31 May 2018 07:41:58 +0000 (UTC) (envelope-from satan@ukr.net) Received: from satan by hell.ukr.net with local ID 1fOIDc-000Nrz-4r ; Thu, 31 May 2018 10:41:56 +0300 Date: Thu, 31 May 2018 10:41:56 +0300 From: Vitalij Satanivskij To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: Ed Maste Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-ID: <20180531074156.GA91726@hell.ukr.net> References: <20180530155039.GE97814@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180530155039.GE97814@FreeBSD.org> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 07:41:58 -0000 Hi Tested both images in both modes on: Supermicro X9SCL-F E3-1230 CPU Work perfectly Glen Barber wrote: GB> Hi, GB> GB> Could folks please help boot-test the most recent 12.0-CURRENT amd64 GB> memstick images on various hardware? Note, this is not a request to GB> install 12.0-CURRENT, only a boot-test with various system knobs GB> tweaked. GB> GB> The most recent images are available at: GB> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img GB> https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img GB> GB> We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we GB> would like to get this included in the upcoming 11.2-RELEASE if the GB> change that had been committed addresses several boot issues reported GB> recently. GB> GB> Please help test, and report back (both successes and failures). GB> GB> Thanks, GB> GB> Glen GB> From owner-freebsd-current@freebsd.org Thu May 31 07:45:45 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 B3AD1FD0072 for ; Thu, 31 May 2018 07:45:45 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2F01876105 for ; Thu, 31 May 2018 07:45:45 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x231.google.com with SMTP id u12-v6so31922842wrn.8 for ; Thu, 31 May 2018 00:45:45 -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=JzAOrsqQgEf9Q0kuixkL5rFvOzj6rOVFlz4EiJdWkgs=; b=T4psXVcDxxRqlGiKLCpJ7Gx9SsP3KuV0kEw/AV1WJ5CpF6qHlH8cj7qcmnwwLXJ7No /neDm2ImmIsNQmGb5w+RpBp4+PAV75qNKvczfFg9D5y4P781BIqSsnjwgttUC5spS1Jo eQplDy9IuuaRBNUA8xihQWMlg7PsjEe7ra0agtuo9YDBKHfwuCUwbWpMir7zq79U64Pt 3kydKaJhcwSDEPR6T6K6HebaEgVUESCWnqdYjnyhtOE6PJLoKGJ0bcuwGJwk+XSzeQG1 9VQhefVW6bZxuoSpp0zQQ8eAtnf6urQ86yxuqcqGRsBX5msIJspDJy8/GDUXbpI6jVi8 IzRg== 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=JzAOrsqQgEf9Q0kuixkL5rFvOzj6rOVFlz4EiJdWkgs=; b=GRFzSy2ImXwCj5SDsMWB0UwwRpM9wr+XKH3xkNidvMg2Jxro66f0r+Qgib55S5oDB2 y2o2qXoompAmf/8WKpt0FZWk1tu+ln6pt6mcgrClujFn9kgaOA7nwnvs1I7SRj/b6Nry P7wUySOsmfO11xJyBF4hTbblpEoWBfzXMtoIcAdZe7oeFo3JJvMrwoEw7Gp6TJwRjR7U LO3KtAIPEqSxhL6CV9NGg75hzKcvmIqOaQ7hdynqlkvbuOJHGWz0CIn2Z2bQwD6BQQ73 F7cgQ4/183wHeDJDKx4R7SoXoEYvxHsioxpNt4Lkdm0/Kya5jEZF3PiwvjMb2vYUuGQx nW3g== X-Gm-Message-State: ALKqPwd1cLidqK6Hiey/yzQ5DDhi84rK5oV1tPjW7lg/vI7cePbPhT23 22J58UHv0+DTPiZvHq5J95p/Vts5pap4xyg/uhA= X-Google-Smtp-Source: ADUXVKJHX+rV08KgKKulrWcioL8+WClqDEja82rqUsxfxVbCOHgbpinIZ5hkeW0KQQMhX+z7s62ltjWJLd36rwosncg= X-Received: by 2002:adf:a0b9:: with SMTP id m54-v6mr4305289wrm.76.1527752743698; Thu, 31 May 2018 00:45:43 -0700 (PDT) MIME-Version: 1.0 From: Johannes Lundberg Date: Thu, 31 May 2018 08:45:07 +0100 Message-ID: Subject: evdev + ps/2 dell touchpad weirdness To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 07:45:46 -0000 Hi I could swear this was working a couple of months ago but since installing new kernel+world a couple of times and revisiting using Weston or X with udev+evdev+libinput I can't get all the events. Using libinput-debug-events on my dell laptop touchpad (psm driver with hw.psm.synaptics=1) I get events for two finger scroll Y (no horizontal scroll but that's another issue), single finger tap (left mouse), two finger tap (right mouse) but not single finger movements, that is I can't move the mouse cursor... Changing to trackpoint, elantech, etc makes no difference. All packages are from stock ports. From owner-freebsd-current@freebsd.org Thu May 31 07:52: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 D548DFD0CBA for ; Thu, 31 May 2018 07:52:27 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4AD05768C3 for ; Thu, 31 May 2018 07:52:27 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id o12-v6so908596wrm.12 for ; Thu, 31 May 2018 00:52:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:reply-to:mime-version :content-transfer-encoding; bh=XihfV26dSOeHXGJGZT+2SoC1D+wggH4w1j1Cqxuv7BI=; b=PviK5ZHzNb/abI40ziodCfZI9ayMbgem2Y7WxY9Wq3mJ3vOZa/waaIYyv0rbogi5Aq KAEcfDBDyREmJgRpf/6TbVaqmdUyNrCFaCMnuJQKIeIiNk5J/6lfDnbRVaLYajugs8MH ZCxfzccw38oHYUwwLMe0fxxfTDhgZQDXH70sOwrPgPWl4rrWHMA+clwrLDZ6EwYJvItF 4Qw7wQyqxGFVcdO3Ts3o/C7Dj4GbsjIeRokUwfu/N+c5yGI8HPadv6fG41o2K16LP+ZA 2fuzbv4AHwInp1uvcxRV2LvV62Swol873q0pvdxdk4OZhQwZmuyykpfM1FZCGVixBT1r tw8Q== 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:subject:message-id:reply-to :mime-version:content-transfer-encoding; bh=XihfV26dSOeHXGJGZT+2SoC1D+wggH4w1j1Cqxuv7BI=; b=HhfCVDKaGJzXf8Qt9zKw9jAJ25ExYfqChdD2I66FaHRkortda8LQlH60A4Wrn1vlC8 X/FvqBGSEBym3s4Ci0ZkIQZtD+YOmOcxReJ4pOxVieFETB7bhnLGJgIxVBPAC/76c1tU tQ2/dPfgRDfyl0R2AUtHgaRnjHbyPphq1zsBjwtCyoHM+s+gjcC92Gg/MObkkdpGk79O 9rXvlzJFPLM/sL+GoG3gtJbAva4T4IwsBWc847RPHCZL9uC7IAB8Q+vt8vOXJp6W6Xfh 9hAzT+Zp+8rfZDgBSU6REYqMkfEFRR/Jg0LsWxn3VLgp6hyTEvQd3lIiubH7HKyyG0/I 0Opw== X-Gm-Message-State: ALKqPwd+NJfF6+iYsWB3xdHBkT0gcpe9JIOueZIe6xKoODcSx8g7/XWj /Jm0/6Gz2Lw144Cm3RMx5YKHMQ== X-Google-Smtp-Source: ADUXVKLmGreDQy7IsEJzsUrnNZYjKjx0cWMjKWZo00x9iIjgwy4BMXOSot2qEllecTiGz32sKHHuPw== X-Received: by 2002:adf:edc6:: with SMTP id v6-v6mr3939231wro.264.1527753146164; Thu, 31 May 2018 00:52:26 -0700 (PDT) Received: from ernst.home (p5B02337A.dip0.t-ipconnect.de. [91.2.51.122]) by smtp.gmail.com with ESMTPSA id k17-v6sm558096wmc.23.2018.05.31.00.52.25 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 00:52:25 -0700 (PDT) Date: Thu, 31 May 2018 09:52:22 +0200 From: Gary Jennejohn To: FreeBSD Current Subject: ``make buildkernel'' fails when /usr/obj is empty Message-ID: <20180531095222.399e7a37@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.26 Precedence: 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, 31 May 2018 07:52:28 -0000 There's something totally screwy about trying to build a kernel when /usr/obj is not populated. I ran ``make clean'' in /usr/src and then ``make buildkernel''. This fails with make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel requires linker ifunc support This is total BS because /usr/bin/ld --version LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) which is exactly what bsd.linker.mk is looking for to set ifunc. If I do this: mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin the buildkernel then succeeds. Considering that (reformatted output from make) PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: /sbin:/bin:/usr/sbin:/usr/bin it seems like /usr/bin/ld should be found by bsd.linker.mk and no error should be reported. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu May 31 07:58: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 A69A2FD1517 for ; Thu, 31 May 2018 07:58:55 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 04D6876C55 for ; Thu, 31 May 2018 07:58:55 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x22e.google.com with SMTP id f8-v6so52367930wmc.4 for ; Thu, 31 May 2018 00:58:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:subject:message-id:in-reply-to:references:reply-to :mime-version:content-transfer-encoding; bh=wrUOSmpdikcN38ivtHDvxdXTTkRyJaHyDt9Yl/8KynU=; b=j3x+sR9uPPxzvkExyTSKkas8EemkoGGPs/mY5CuhDG9JplOGDAuP5S8M9cqkzgAXaB Z5ltIJlX4OPt+cV4wyfMMEwMv/a1Im0rbQ6aaMSdvlDJTq4UW1H+Dpi3Co8pLcXZ7cXI SsU6gRduBAaEx9oJA3F6uQitFk/8uFBsKDjR9lfFYfaDCPRZsSJ4HqPNSgEWyqGh727R DmnC2536ardJCUIgjm2S7+hlHpcfQEEjyRe2uSAal52JRNv2HFKGcj6j3zhsyRvXiCfO QSlEjjgnU+Gy+7c5lqlECClXnSy1ZbAwj8BzMu5HY0M979I0ziG1kx8CxYwyfqN2rO0L b0Mg== 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:subject:message-id:in-reply-to :references:reply-to:mime-version:content-transfer-encoding; bh=wrUOSmpdikcN38ivtHDvxdXTTkRyJaHyDt9Yl/8KynU=; b=ofMSmAeNTJ1Qmsl4gISYjNCjb17FOQVGFKxqqVnYY9/CVEfmBABrGuAoLBE7px04cb y5NjIlI/MmX39Z9xfrwbhJJ/FStllf1v2k1OEgRbKEfqBqkHsDejtWi64CUGAExlMqkK BBm2tLOr8p+FhQuqA+ynGAdmCvbTJD05CrBOe/tEAJCa47y7eioKqtnwzeOJ+L6UWvyZ x9xJtxssaPez0hzcjqhf5UrF4BB2OhDsYiF46w3mnyTFePJUNQgh99BADEm511qwiPwH 084MZXKiLnei4S+Xd6NWE9WRWxkEhR6ccnOnOt1l5YKQPPzaeSLvP7MZCdSPUhnK8iR7 851A== X-Gm-Message-State: ALKqPwfQB/KKCTGdzPRR+IQ6WiGhji82z5I/yHJBsOto2wHuaOG+R3Pc lgoFh3mwwwnii7SLFx+Wy1UZNw== X-Google-Smtp-Source: ADUXVKIQrbGCTDqRXlkhsChwImQYm92WRSXkPOw79Z0CiICNA7ov3kwpPt3QKvKEBzKdFhAvwFWqOA== X-Received: by 2002:a1c:96c1:: with SMTP id y184-v6mr3493447wmd.156.1527753533850; Thu, 31 May 2018 00:58:53 -0700 (PDT) Received: from ernst.home (p5B02337A.dip0.t-ipconnect.de. [91.2.51.122]) by smtp.gmail.com with ESMTPSA id n56-v6sm29894873wrn.72.2018.05.31.00.58.51 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 00:58:53 -0700 (PDT) Date: Thu, 31 May 2018 09:58:50 +0200 From: Gary Jennejohn To: FreeBSD Current Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Message-ID: <20180531095850.5845fd7a@ernst.home> In-Reply-To: <20180531095222.399e7a37@ernst.home> References: <20180531095222.399e7a37@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.26 Precedence: 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, 31 May 2018 07:58:55 -0000 On Thu, 31 May 2018 09:52:22 +0200 Gary Jennejohn wrote: > There's something totally screwy about trying to build a kernel when > /usr/obj is not populated. > > I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > fails with > make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > requires linker ifunc support > > This is total BS because > > /usr/bin/ld --version > LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) > > which is exactly what bsd.linker.mk is looking for to set ifunc. > > If I do this: > > mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > > the buildkernel then succeeds. > > Considering that (reformatted output from make) > > PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: > /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: > /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: > /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: > /sbin:/bin:/usr/sbin:/usr/bin > > it seems like /usr/bin/ld should be found by bsd.linker.mk and no > error should be reported. > OK, it seems that ``make clean'' does not remove the contents of /usr/obj/usr/src/amd64.amd64/tmp/legacy. If I delete everything under /usr/obj then ``make buildkernel'' works. Still, it seems pretty strange to me to make building a kernel depend on some random junk which is left laying around under /usr/obj. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Thu May 31 08:32: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 AAE57EEF4A2 for ; Thu, 31 May 2018 08:32:54 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1C7CF781A8 for ; Thu, 31 May 2018 08:32:54 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x230.google.com with SMTP id k16-v6so4858558wro.0 for ; Thu, 31 May 2018 01:32:54 -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=/Klw6I1QzNx9aZy5EW33HnMnIzArZBkA0drzUwx8azs=; b=IxeKRNUIZDlCxDGQEwJbHtyU5hmn8jUJivFu9rgCPRiUVT4EW8yXVhy/Sh3tATIvPc OD/3o1feMrjr9Q+I9kXEY24lGSwhVaVrquek6cGiWFngxOdO5VD//nkR1HW/TGtPZg2l ecsjg3SUmn2qH3OhmmmBjHatNiyFVrrA1ZS/CM4wL9CIa54m6QKjDL8cXYStJsINZoxc pbVm8QKzQyl0zLtHEasHNAI9uB+wq9WF9xQy72repmm/oQtQifYBAQGF/3oxoz1+lsIO SWpNG3EZB/BqPYKkLzDf0Hiu5iKvZ6IkECFaBCZ3inVji8hdvDth6AkTZyIGM+bfj4iZ vZIA== 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=/Klw6I1QzNx9aZy5EW33HnMnIzArZBkA0drzUwx8azs=; b=LGUrG/x34Zc+KNlUvVFL0B5CUHmi/WD2KG/lg7CJakEVCI+VMt2rEDwXwVhcHw+W/7 BukMiSkvvrjMk8CZ6ujkdp6T6ne/iYithVaRmILaVE67GQb5aGp3QgoPHdQfANGMG9to r1oj9v4s69l2/wX5duDuzInsid8YBQO0Pv8uCzWMoJnb2HtwHs6fTta7iSfnEe8rKsOl /AlnVJCDoDUOgQ43nbcTcWWvB6+F81hhVx4ahMtTRvgInB4Imx1frVPiQBfnBwVQ915C FRHJDl5/CkJZXNRSMpfORVZtV1yJILRF0rkiA4r+su0kh9fnzbyXLALwMBk90bTP+ZhQ Vd5w== X-Gm-Message-State: ALKqPweA1Nm3vN0KGS9hq+BCHC75aGoW4MlPfGsz9tCtPuRyuGyaIQY8 wjBvvYd/YocjgKkimrsaH4WVwYEVEVHsYbTHbNje9w== X-Google-Smtp-Source: ADUXVKIlIi1JpY2nNoWwfP2hLyAel0M0RmljiK9GC8ne86cRot2Vs/nD/IbtCeUT0GvZ3Ux9jZZIB7DIA2x9ojvYm0E= X-Received: by 2002:adf:e590:: with SMTP id l16-v6mr1096682wrm.190.1527755572946; Thu, 31 May 2018 01:32:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Thu, 31 May 2018 09:32:16 +0100 Message-ID: Subject: Re: evdev + ps/2 dell touchpad weirdness To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 08:32:55 -0000 On Thu, May 31, 2018 at 8:45 AM Johannes Lundberg wrote: > Hi > > I could swear this was working a couple of months ago but since installing > new kernel+world a couple of times and revisiting using Weston or X with > udev+evdev+libinput I can't get all the events. > > Using libinput-debug-events on my dell laptop touchpad (psm driver with > hw.psm.synaptics=1) I get events for two finger scroll Y (no horizontal > scroll but that's another issue), single finger tap (left mouse), two > finger tap (right mouse) but not single finger movements, that is I can't > move the mouse cursor... > > Changing to trackpoint, elantech, etc makes no difference. > > All packages are from stock ports. > To add more information. With PSM_DEBUG in kernel I can see that I'm getting interrupts for single finger movement psmintr: 38 f4 fd 00 00 00 psmintr: 38 f4 ff 00 00 00 psmintr: 18 f5 00 00 00 00 psmintr: 18 f5 00 00 00 00 psmintr: 18 f5 03 00 00 00 psmintr: 18 f7 04 00 00 00 psmintr: 18 f9 05 00 00 00 From owner-freebsd-current@freebsd.org Thu May 31 10:16: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 51FE6EFD5D0 for ; Thu, 31 May 2018 10:16:55 +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 CEAF77C221 for ; Thu, 31 May 2018 10:16:54 +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 ESMTP id w4VAGhgi063376; Thu, 31 May 2018 13:16:46 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w4VAGhgi063376 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w4VAGh5J063375; Thu, 31 May 2018 13:16:43 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 31 May 2018 13:16:43 +0300 From: Konstantin Belousov To: Johannes Lundberg Cc: freebsd-current Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <20180531101643.GV3789@kib.kiev.ua> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.0 (2018-05-17) 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.26 Precedence: 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, 31 May 2018 10:16:55 -0000 On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > On Wed, May 30, 2018 at 10:57 PM O. Hartmann wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > > "Rodney W. Grimes" schrieb: > > > > > -- Start of PGP signed section. > > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > > > > >Also as the Moore's law curve flattens expect the life of these > > > > > > > >older, but not so old, machines to live quiet some time. I > > > > > > > >believe we are talking sandy bridge and earlier? If that is > > > > > > > >corret Sandy bridge is still a very viable system. > > > > > > > > > > > > > > I noticed this lack of love for older systems recently. > > > > > > > > > > > > > > I wanted to use an older Dell server to test the 11.2 BETAs and > > RCs. > > > > > > > > > > > > > > Turns out, you can't install FreeBSD using a USB stick image > > because the > > > > > > > BIOS only support MBR. No idea why MBR support was dropped for > > the USB images. > > > > > > > > > > > > > > In the end I had to find a CD burner, and after a couple of > > tries managed to > > > > > > > install from CD. > > > > > > > > > > > > > > After that, my ansible playbooks started failing because > > /boot/loader.conf > > > > > > > is absent if you boot from zfs in combination with MBR. > > > > > > > > > > > > > > Pity. This older server hardware is great for trying out new > > releases, play > > > > > > > with zfs, etc. > > > > > > > > > > > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now > > > > > > built as hybrid images, supporting both MBR and GPT, as well as > > being > > > > > > written to a flash drive (like memstick.img) as well as a CD. > > > > > > > > > > To clarify a minor point here, are the amd64 disc1.iso images or > > > > > both the amd64 and i386 disk1.iso images being built as "hybrid"? > > > > > > > > > > > > > Only amd64. i386 does not have UEFI-/GPT-related boot issues. > > > > > > Here is a data point: > > > > > > Test system is Dell R710, > > > First attempt is with BIOS in Boot mode: Bios > > > Second attempt is with BIOS in Boot mode: UEFI > > > > > > Attemtped to boot amd64 version: > > > Screen goes white background, text appears (yes, way indented) > > > BTX version is 1.02 > > > Consoles: internal video/keyboard > > > _ > > > > > > That last _ is a blinking cursor, system is hung, does repsond to C-A-del > > > > > > > > > Second attempt: > > > Works properly > > > > > > > > > I am going after Ed Maste's posted build image in the other thread now... > > > > > > > > > > > > > > > As this is what I see on my system: > > > > > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > > > > > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition 1 > > : ID=0xee, > > > > > start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 > > sectors > > > > > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data > > > > > '11_2_BETA2_I386_CD' (bootable) > > > > > > MBR support was initially removed from the memstick installer, as > > it is > > > > > > not compatible with some UEFI implementations. (Or, at least that > > is my > > > > > > understanding, based on my limited intimate knowledge of UEFI.) > > > > > > > > > > > > > > Glen > > > > > > > -- End of PGP section, PGP failed! > > > > > > > Today, I tried to eliminate FreeBSD's native KMS drm2 by installing > > graphics/drm-stable-kmod (ports tree at revision 471172) on CURRENT > > (FreeBSD 12.0-CURRENT > > #46 r334401: Wed May 30 23:32:45 CEST 2018 amd64, CUSTOM kernel). > > > > The hardware is a presumably UEFI capable ASROCK Z77-Pro4M (latest > > firmware available > > from late 2013) equipted with a XEON IvyBridge: > > > > CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class CPU) > > Origin="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 > > > > Features=0xbfebfbff > > > > Features2=0x7fbae3ff > > AMD Features=0x28100800 > > AMD Features2=0x1 > > Structured Extended Features=0x281 > > 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 = 16295137280 (15540 MB) > > Event timer "LAPIC" quality 600 > > ACPI APIC Table: > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > > > > The box isn't capable of booting FreeBSD in UEFI (while Linux and Windows > > seems to work). > > So I'm stuck with BIOS. > > > > Loading i915kms.ko/drm2.ko on the system put the console in a > > high-resolution mode > > instead of this crap 80x25 ancient console immediately. > > > > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up > > in a trap > > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does > > load without > > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > > > So why should I vote for non-working drivers to replace perfectly working > > ones? > > > > oh > > > > > We're not replacing anything. We are moving the older drm1 and drm2 from > kernel to ports to make it easier for the majority of the users to load the > correct driver without conflicts. You do understand that you increase your maintainence load by this move. dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable branches, so you will need to chase these updates. > > We have updated drm-stable-kmod so that it now works on some older amd64 > system also covered by drm2 but as always, ymmv. drm2 will later be > available as drm-legacy-kmod or something like that (name to be announced > later). Simply use/install the one that works best for you. > > > > > > > - -- > > O. Hartmann > > > > Ich widerspreche der Nutzung oder ??bermittlung meiner Daten f??r > > Werbezwecke oder f??r die Markt- oder Meinungsforschung (?? 28 Abs. 4 BDSG). > > -----BEGIN PGP SIGNATURE----- > > > > iLUEARMKAB0WIQQZVZMzAtwC2T/86TrS528fyFhYlAUCWw8c/AAKCRDS528fyFhY > > lBl7Af0R7ymOzkWp7GcqymhUiOgfy3qvTSmHYgbTzYxsD54GEIfoAMvH1pHFp4yL > > b0NYx9HR+BU3d6GAf0Xq0sq78kMFAf9KUhDMLUHf06+ASJkS2uPyr+jZBZeBlTRc > > IsE0PaxErbYy8YLJhWXgrSYCM1KHIZisBNUOLGckcCIgTvu0MRsQ > > =yFzW > > -----END PGP SIGNATURE----- > > _______________________________________________ > > 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" > > > _______________________________________________ > 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 May 31 11:04: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 48BC0F71C24 for ; Thu, 31 May 2018 11:04:48 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B30287DEF8; Thu, 31 May 2018 11:04:47 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-pl0-x22b.google.com with SMTP id 31-v6so3113537plc.4; Thu, 31 May 2018 04:04:47 -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=W8AyVLcRiZv/WWc0nuIn26WGQt+vv7MNFnzB6TM8qxQ=; b=vGMZlJDnPNAsBv8qAlu6uy+EN2+pnPI+shNpP5ED1hZ+LKv+FF7G+85aKURyNu4kEh l7jqjCQO8mTaN62KooCIDPfv6DAOqCtC4rX6qBTJ04xotekq9zWcjpZ59uzjGWbYyTDk m8cuWnOukimA94nA5DAqlIofZ/fm40qu/RuRUwCGdc9tS84XODYtP0s+X06U8xjD41Me H0dkvEhsV4M+3RgG9a1Dk3+9T4/w7zMwktUHFqcQMwCtfnHBsWbbbTf9wiDVrw5yOrvM 8mhzrLWXYcvnU0e09IeH/cDiSMJo3du5wugOw9w8shDd5/0ai4kUbKW+QvqVwoGegTUQ a7dg== 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=W8AyVLcRiZv/WWc0nuIn26WGQt+vv7MNFnzB6TM8qxQ=; b=YV/7x2PqXpCwgvzb2Y86MdkUjlzzeKxVuDbwsKP+WVLII+TdzNmTI8Xqty6ljVwuEl hQqHA2HOpML/q4NnvsKq2bBZsCOb65fZ/8RQsClym9jmM8gyf5822eyWZO5C6kuoY0+s RZ7KK+6ZTCTT8jwiQtIuYotslL9F5nkyy55DgPCEy+VBOpWoJgV4nFcvw5LnjB1I/Ew4 K40ndh22t4PTujbWpH+5hOU2oAyUCa4A+SMM1DK+TuvLGx9R4kZ7HFsCn7MutzXiYAat 6k2/ZjdP2rVCuGwl6Dc7FU32+swQC215gGxwIbXm/K7cpYq7IBZ6NvC7UIprF98vbkXt ChOA== X-Gm-Message-State: ALKqPwfe0eJF1URpGXtvV4MpfWuV7HwpxQz3UOKUhloks9WrrdBp9Sga 6+/kTIgoH+AyCpyDpceog9hsPA== X-Google-Smtp-Source: ADUXVKJh7PIaPVa4Y61FR9LdDcziDqx5S3m1NNMdv/NXLE63RW5TvssJP5x5CEECVe5+TUljm1zH5g== X-Received: by 2002:a17:902:7841:: with SMTP id e1-v6mr6644539pln.197.1527764686405; Thu, 31 May 2018 04:04:46 -0700 (PDT) Received: from raichu (toroon0560w-lp140-02-70-49-169-156.dsl.bell.ca. [70.49.169.156]) by smtp.gmail.com with ESMTPSA id z192-v6sm1522375pgz.6.2018.05.31.04.04.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 04:04:45 -0700 (PDT) Sender: Mark Johnston Date: Thu, 31 May 2018 07:04:40 -0400 From: Mark Johnston To: Andriy Gapon Cc: "Jonathan T. Looney" , FreeBSD Current Subject: Re: panic: vm_phys_free_pages: page 0x... has unexpected order 0 Message-ID: <20180531110433.GA41152@raichu> References: <932853d2-16f9-67c0-fcf8-745bb5e358d4@FreeBSD.org> <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <783f525c-d1ab-f4cd-9e3e-64d2e70f549b@FreeBSD.org> User-Agent: Mutt/1.9.5 (2018-04-13) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 11:04:48 -0000 On Thu, May 31, 2018 at 10:10:40AM +0300, Andriy Gapon wrote: > On 31/05/2018 05:04, Jonathan T. Looney wrote: > > On Tue, May 29, 2018 at 10:18 AM, Andriy Gapon > > wrote: > > > > > > [ping] > > > > On 21/05/2018 11:44, Andriy Gapon wrote: > > > > > > FreeBSD 12.0-CURRENT amd64 r332472 > > > Does this panic ring a bell to anyone? > > > Has it already been fixed? > > > Thank you! > > > > > > Is there any chance that r333703 fixes this problem for you? It fixes a race > > that can manifest itself in other ways. I'm honestly not sure whether it could > > also cause this problem. > > Thank you for the suggestion. > I guess it's worth trying that fix. > I'll report back in a while. r333703 fixes a bug in r332974, while the problem was reported on r332472, so it won't address the crash. From owner-freebsd-current@freebsd.org Thu May 31 11:40: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 ECCB5F752DB for ; Thu, 31 May 2018 11:40:26 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 68F2E7F627 for ; Thu, 31 May 2018 11:40:26 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id l41-v6so32726557wre.7 for ; Thu, 31 May 2018 04:40:26 -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=i0q4geH2kZ14tiyEGV5t7/ruQRp26ANuYXgazhB3eGs=; b=haQpNudn2Mbt317xROvgqfOxZeinL2Mg5QX/j5WiuHv3vI0cF8ZJ06e/iueNDTA8NA gzKd+TigEsL/v9/gTK46RIHiJFauZdTDRMsVdJ+w2g+NK5L/yDmhaTXsveAmeWr8J/+E luuG6bBoSp3QLcMbsPY8ApAOPPPKvuA4Ube1TDidbBGdLB+1KwJIGDDAanitlQckXr7a oeMUMy4bTi5BRgqNe3EItugeAUQDcCFmthLTEsxzNPKvcF17vtmntcuB3ybQSVNO+XqJ 1uEVgrpdbdcInJasXgZkmlMjZ3CVvS0uSW3vYIfhXSJdC7FznQ8EopQfar57Ds1DccVK rHxw== 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=i0q4geH2kZ14tiyEGV5t7/ruQRp26ANuYXgazhB3eGs=; b=PsZpmTn9PnMhJHbbzsL4n1EG9IgyrymlU8cjPn6CJoK6hPLgRi2Xt6jzsDXVWPLirr gz311uEceZCbBa9oc+nHCBxa6TMDyNmw/UsYYEYsXLWbMmVOUSzd0nAgm7HStc0XiR3j 7Mua0MW3vzh+F60UL2UG9cthP8UhUrFvxAqZM+TQn09lfYyBhgUddITeHmXlLXpSLdz2 H5ebzZitLlnKVQkI0jgHtEoDO6YGnuwvFH5k/wpP4TcdR3fgSzmJKiTGXy5kAAndHk0s n2KpeJUZxAs5b3J6GmdtczGLmOjJHLiHZiGiT2XLg6x2tb0mkYwCepadCqrqYbEUS1rB IY+Q== X-Gm-Message-State: ALKqPwcPp1FiVBB8uE2ILGfmH5hh/pFUuhPlNmG6/oVcrYQm+dS2ejL2 qF7ZSNrj7zZjBnYeI2dFScqKp+RQvgYM7LRms9t9pw== X-Google-Smtp-Source: ADUXVKKoi84N/VXl/JPHWuNL4wySOcrhjW82O4xgpwQtzO77KI88PwdpaCkfL6OPYwNLjOmuhBn372ZFfd61s4+jZ7w= X-Received: by 2002:adf:aa08:: with SMTP id p8-v6mr4938476wrd.140.1527766825150; Thu, 31 May 2018 04:40:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Johannes Lundberg Date: Thu, 31 May 2018 12:39:48 +0100 Message-ID: Subject: Re: evdev + ps/2 dell touchpad weirdness To: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 11:40:27 -0000 On Thu, May 31, 2018 at 9:32 AM Johannes Lundberg wrote: > > > On Thu, May 31, 2018 at 8:45 AM Johannes Lundberg > wrote: > >> Hi >> >> I could swear this was working a couple of months ago but since >> installing new kernel+world a couple of times and revisiting using Weston >> or X with udev+evdev+libinput I can't get all the events. >> >> Using libinput-debug-events on my dell laptop touchpad (psm driver with >> hw.psm.synaptics=1) I get events for two finger scroll Y (no horizontal >> scroll but that's another issue), single finger tap (left mouse), two >> finger tap (right mouse) but not single finger movements, that is I can't >> move the mouse cursor... >> >> Changing to trackpoint, elantech, etc makes no difference. >> >> All packages are from stock ports. >> > > To add more information. With PSM_DEBUG in kernel I can see that I'm > getting interrupts for single finger movement > > psmintr: 38 f4 fd 00 00 00 > psmintr: 38 f4 ff 00 00 00 > psmintr: 18 f5 00 00 00 00 > psmintr: 18 f5 00 00 00 00 > psmintr: 18 f5 03 00 00 00 > psmintr: 18 f7 04 00 00 00 > psmintr: 18 f9 05 00 00 00 > > > Ok got the fix. Can someone commit? EV_REL is for pushing events. For evdev_push_rel(), use REL_{axis}. diff --git a/sys/dev/atkbdc/psm.c b/sys/dev/atkbdc/psm.c index 0b6a061e15b..227b73e7088 100644 --- a/sys/dev/atkbdc/psm.c +++ b/sys/dev/atkbdc/psm.c @@ -4966,8 +4966,8 @@ psmsoftintr(void *arg) if (evdev_rcpt_mask & EVDEV_RCPT_HW_MOUSE && sc->hw.model != MOUSE_MODEL_ELANTECH && sc->hw.model != MOUSE_MODEL_SYNAPTICS) { - evdev_push_rel(sc->evdev_r, EV_REL, x); - evdev_push_rel(sc->evdev_r, EV_REL, -y); + evdev_push_rel(sc->evdev_r, REL_X, x); + evdev_push_rel(sc->evdev_r, REL_Y, -y); switch (sc->hw.model) { case MOUSE_MODEL_EXPLORER: From owner-freebsd-current@freebsd.org Thu May 31 12:11: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 30811F78EF1 for ; Thu, 31 May 2018 12:11:24 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (turbocat.net [IPv6:2a01:4f8:c17:6c4b::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 C6B9281311 for ; Thu, 31 May 2018 12:11:23 +0000 (UTC) (envelope-from hps@selasky.org) Received: from hps2016.home.selasky.org (unknown [62.141.128.70]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id ECBFA2600B9; Thu, 31 May 2018 14:11:21 +0200 (CEST) Subject: Re: evdev + ps/2 dell touchpad weirdness To: Johannes Lundberg , freebsd-current References: From: Hans Petter Selasky Message-ID: <7ebab91e-fbd2-07bf-4f0e-1022c313d318@selasky.org> Date: Thu, 31 May 2018 14:11:08 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 31 May 2018 12:11:24 -0000 On 05/31/18 13:39, Johannes Lundberg wrote: > EV_REL is for pushing events. For evdev_push_rel(), use REL_{axis}. Does this work: https://svnweb.freebsd.org/changeset/base/334422 --HPS From owner-freebsd-current@freebsd.org Thu May 31 12:14: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 2E6D5F79369 for ; Thu, 31 May 2018 12:14:15 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99B568183B for ; Thu, 31 May 2018 12:14:14 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id f16-v6so17459523wrm.3 for ; Thu, 31 May 2018 05:14:14 -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=ROgUC3HFi6rN6m82VwLnY511nlbK6m4MNe2VTbFXbkQ=; b=BqqfoDaqG61Hpn7jupYOz4hfUpzOogGGxIzhTFb9v+CkSU3PxtCh8+Bq0DVGFWc2LR Dlsf38LRpTuA/+VopnL2SiANmCDjyFeDBT3S+gVQIu/QqmlyT/5oMkj3ThZUMnOZZoHj FGnDcWq6YC/qJhnA2nbp+jgUphRqEhShKbrLGY/IGdG+Gjn5JtSt04odGA+Hpn8AwBMA PAIL4wok9ybHgBovslBq/MezUS3l3HnDSGeiHd0IZ9nVerKEjE7JYvrxsWBYQYb8czO2 nXsVoYPIZJW9zPcz6iltxxYQi0Mmnfd/5PkxuC8P/Wb0JoCSpJFi2c+IZ92h2Yfoqebx diCg== 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=ROgUC3HFi6rN6m82VwLnY511nlbK6m4MNe2VTbFXbkQ=; b=AX2SW4tY1vCDn6swTXE3RSqnQYaSiCD4o+Swi3w8gPW00pObxe6rK7wb/KnMZSe/6J 1SHB8pLI6TWuhfAemzXVutNY0UiJ+71/GXBkkk5bdazZCExkmeh5lxoczBZiv9Axk5Cb LuHj3n/YohkzYIPsa6FlK+KClwMCXPVR7K/qb13jv6pSaWK59EVe0CFVeU19pDECfhnN AS8LlikKIqn8M7gsg9uIec224Pa6ph1E255G2W3NAZfd5iZGyOOBhpXx7DVNnhFY2eCK Mqv/Vr4qW5yj0+D77WsdNS4t+WxynFnU8SKUB5KeCYPLA5e3zHRAH5nt4JUmHt3nh3BR WsnA== X-Gm-Message-State: ALKqPwcoGYd9+HGC8ojgCnDIdzy0mtdacxScEYnY+1iYSWmCG2hwFH5H HrzoA3EIVOc4aYR3Rv0SaI9KKCX+eNxSgEu2Qz8= X-Google-Smtp-Source: ADUXVKI/11Aty80JmXb/gK9TkDdHYYK2x6T9iPS4SK3HXlfvL4cbas1D4+q0JxuvSlv+3+1IQRgyGD9YH7dxptnzji8= X-Received: by 2002:adf:aa08:: with SMTP id p8-v6mr5032286wrd.140.1527768853613; Thu, 31 May 2018 05:14:13 -0700 (PDT) MIME-Version: 1.0 References: <7ebab91e-fbd2-07bf-4f0e-1022c313d318@selasky.org> In-Reply-To: <7ebab91e-fbd2-07bf-4f0e-1022c313d318@selasky.org> From: Johannes Lundberg Date: Thu, 31 May 2018 13:13:37 +0100 Message-ID: Subject: Re: evdev + ps/2 dell touchpad weirdness To: Hans Petter Selasky Cc: freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 12:14:15 -0000 On Thu, May 31, 2018 at 1:11 PM Hans Petter Selasky wrote: > On 05/31/18 13:39, Johannes Lundberg wrote: > > EV_REL is for pushing events. For evdev_push_rel(), use REL_{axis}. > > Does this work: > https://svnweb.freebsd.org/changeset/base/334422 Perfect. Thanks! > > > --HPS > From owner-freebsd-current@freebsd.org Thu May 31 14:14: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 21E82FD16A7 for ; Thu, 31 May 2018 14:14:09 +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 9A878879F5 for ; Thu, 31 May 2018 14:14:08 +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 w4VEE5wR076966; Thu, 31 May 2018 07:14:05 -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 w4VEE57n076965; Thu, 31 May 2018 07:14:05 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805311414.w4VEE57n076965@pdx.rh.CN85.dnsmgr.net> Subject: Re: ``make buildkernel'' fails when /usr/obj is empty In-Reply-To: <20180531095222.399e7a37@ernst.home> To: gljennjohn@gmail.com Date: Thu, 31 May 2018 07:14:05 -0700 (PDT) CC: 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.26 Precedence: 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, 31 May 2018 14:14:09 -0000 > There's something totally screwy about trying to build a kernel when > /usr/obj is not populated. > > I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > fails with > make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > requires linker ifunc support > > This is total BS because > > /usr/bin/ld --version > LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) > > which is exactly what bsd.linker.mk is looking for to set ifunc. > > If I do this: > > mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > > the buildkernel then succeeds. > > Considering that (reformatted output from make) > > PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: > /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: > /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: > /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: > /sbin:/bin:/usr/sbin:/usr/bin > > it seems like /usr/bin/ld should be found by bsd.linker.mk and no > error should be reported. AHH!! That explains why I was still seeing this too! I been forcing the LD= work around and just ignoring this failure thinking it was something in my not so normal setup, but infact I always start with an empty /usr/obj due to a zfs rollback pool/usr/obj@empty So this is a "confirmed" this occurs, including in a 20180521 freshly installed snapshot. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu May 31 14: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 D0267FD215D for ; Thu, 31 May 2018 14:21: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 2886D87DEC for ; Thu, 31 May 2018 14:21:08 +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 w4VEL6O9076987; Thu, 31 May 2018 07:21:06 -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 w4VEL6f1076986; Thu, 31 May 2018 07:21:06 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201805311421.w4VEL6f1076986@pdx.rh.CN85.dnsmgr.net> Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: <20180531101643.GV3789@kib.kiev.ua> To: Konstantin Belousov Date: Thu, 31 May 2018 07:21:06 -0700 (PDT) CC: Johannes Lundberg , 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.26 Precedence: 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, 31 May 2018 14:21:09 -0000 > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA512 > > > > > > Am Thu, 24 May 2018 09:10:10 -0700 (PDT) > > > "Rodney W. Grimes" schrieb: > > > > > > > -- Start of PGP signed section. > > > > > On Thu, May 24, 2018 at 08:22:12AM -0700, Rodney W. Grimes wrote: > > > > > > > On Wed, May 23, 2018 at 11:48:38AM +0200, Philip Homburg wrote: > > > > > > > > >Also as the Moore's law curve flattens expect the life of these > > > > > > > > >older, but not so old, machines to live quiet some time. I > > > > > > > > >believe we are talking sandy bridge and earlier? If that is > > > > > > > > >corret Sandy bridge is still a very viable system. > > > > > > > > > > > > > > > > I noticed this lack of love for older systems recently. > > > > > > > > > > > > > > > > I wanted to use an older Dell server to test the 11.2 BETAs and > > > RCs. > > > > > > > > > > > > > > > > Turns out, you can't install FreeBSD using a USB stick image > > > because the > > > > > > > > BIOS only support MBR. No idea why MBR support was dropped for > > > the USB images. > > > > > > > > > > > > > > > > In the end I had to find a CD burner, and after a couple of > > > tries managed to > > > > > > > > install from CD. > > > > > > > > > > > > > > > > After that, my ansible playbooks started failing because > > > /boot/loader.conf > > > > > > > > is absent if you boot from zfs in combination with MBR. > > > > > > > > > > > > > > > > Pity. This older server hardware is great for trying out new > > > releases, play > > > > > > > > with zfs, etc. > > > > > > > > > > > > > > The disc1.iso (as well as bootonly.iso and dvd1.iso) images are now > > > > > > > built as hybrid images, supporting both MBR and GPT, as well as > > > being > > > > > > > written to a flash drive (like memstick.img) as well as a CD. > > > > > > > > > > > > To clarify a minor point here, are the amd64 disc1.iso images or > > > > > > both the amd64 and i386 disk1.iso images being built as "hybrid"? > > > > > > > > > > > > > > > > Only amd64. i386 does not have UEFI-/GPT-related boot issues. > > > > > > > > Here is a data point: > > > > > > > > Test system is Dell R710, > > > > First attempt is with BIOS in Boot mode: Bios > > > > Second attempt is with BIOS in Boot mode: UEFI > > > > > > > > Attemtped to boot amd64 version: > > > > Screen goes white background, text appears (yes, way indented) > > > > BTX version is 1.02 > > > > Consoles: internal video/keyboard > > > > _ > > > > > > > > That last _ is a blinking cursor, system is hung, does repsond to C-A-del > > > > > > > > > > > > Second attempt: > > > > Works properly > > > > > > > > > > > > I am going after Ed Maste's posted build image in the other thread now... > > > > > > > > > > > > > > > > > > > As this is what I see on my system: > > > > > > root@x230a:/home/ISO/x # file FreeBSD-11.2-BETA2-* > > > > > > FreeBSD-11.2-BETA2-amd64-disc1.iso: DOS/MBR boot sector; partition 1 > > > : ID=0xee, > > > > > > start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 1472695 > > > sectors > > > > > > FreeBSD-11.2-BETA2-i386-disc1.iso: ISO 9660 CD-ROM filesystem data > > > > > > '11_2_BETA2_I386_CD' (bootable) > > > > > > > MBR support was initially removed from the memstick installer, as > > > it is > > > > > > > not compatible with some UEFI implementations. (Or, at least that > > > is my > > > > > > > understanding, based on my limited intimate knowledge of UEFI.) > > > > > > > > > > > > > > > > > Glen > > > > > > > > > -- End of PGP section, PGP failed! > > > > > > > > > > Today, I tried to eliminate FreeBSD's native KMS drm2 by installing > > > graphics/drm-stable-kmod (ports tree at revision 471172) on CURRENT > > > (FreeBSD 12.0-CURRENT > > > #46 r334401: Wed May 30 23:32:45 CEST 2018 amd64, CUSTOM kernel). > > > > > > The hardware is a presumably UEFI capable ASROCK Z77-Pro4M (latest > > > firmware available > > > from late 2013) equipted with a XEON IvyBridge: > > > > > > CPU: Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz (3400.09-MHz K8-class CPU) > > > Origin="GenuineIntel" Id=0x306a9 Family=0x6 Model=0x3a Stepping=9 > > > > > > Features=0xbfebfbff > > > > > > Features2=0x7fbae3ff > > > AMD Features=0x28100800 > > > AMD Features2=0x1 > > > Structured Extended Features=0x281 > > > 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 = 16295137280 (15540 MB) > > > Event timer "LAPIC" quality 600 > > > ACPI APIC Table: > > > FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs > > > > > > > > > The box isn't capable of booting FreeBSD in UEFI (while Linux and Windows > > > seems to work). > > > So I'm stuck with BIOS. > > > > > > Loading i915kms.ko/drm2.ko on the system put the console in a > > > high-resolution mode > > > instead of this crap 80x25 ancient console immediately. > > > > > > Loading graphics/drm-stable-kmod as requested (via rc.conf.local) ends up > > > in a trap > > > 12/crash. Very nice for such an old hardware. graphics/drm-next-kmod does > > > load without > > > crashing the system - but the console is stuck in the clumsy 80x25 mode. > > > > > > So why should I vote for non-working drivers to replace perfectly working > > > ones? > > > > > > oh > > > > > > > > We're not replacing anything. We are moving the older drm1 and drm2 from > > kernel to ports to make it easier for the majority of the users to load the > > correct driver without conflicts. > You do understand that you increase your maintainence load by this move. > dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable > branches, so you will need to chase these updates. This is my major concern with any discussion of drm that lives outside of base. I am actually pretty amazed that kmod-next works as often as it does. I do remeber for a long time this was a -current only modules, is that still true, or can I load it on 11.0, 11.1 and 11.2Beta3 now? > > We have updated drm-stable-kmod so that it now works on some older amd64 > > system also covered by drm2 but as always, ymmv. drm2 will later be > > available as drm-legacy-kmod or something like that (name to be announced > > later). Simply use/install the one that works best for you. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-current@freebsd.org Thu May 31 14:29: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 98DADFD330F for ; Thu, 31 May 2018 14:29:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from mail.netplex.net (mail.netplex.net [204.213.176.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.netplex.net", Issuer "RapidSSL RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B7186882A for ; Thu, 31 May 2018 14:29:16 +0000 (UTC) (envelope-from deischen@freebsd.org) Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11]) by mail.netplex.net (8.15.1/8.15.1/NETPLEX) with ESMTP id w4VENX3A023944; Thu, 31 May 2018 10:23:33 -0400 X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.netplex.net) X-Greylist: Message whitelisted by DRAC access database, not delayed by milter-greylist-4.4.3 (mail.netplex.net [204.213.176.9]); Thu, 31 May 2018 10:23:34 -0400 (EDT) Date: Thu, 31 May 2018 10:23:33 -0400 (EDT) From: Daniel Eischen X-X-Sender: eischen@sea.ntplx.net Reply-To: Daniel Eischen To: Konstantin Belousov cc: Johannes Lundberg , freebsd-current Subject: Re: [RFC] Deprecation and removal of the drm2 driver In-Reply-To: <20180531101643.GV3789@kib.kiev.ua> Message-ID: References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 14:29:16 -0000 On Thu, 31 May 2018, Konstantin Belousov wrote: > On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > >> We're not replacing anything. We are moving the older drm1 and drm2 from >> kernel to ports to make it easier for the majority of the users to load the >> correct driver without conflicts. > > You do understand that you increase your maintainence load by this move. > dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable > branches, so you will need to chase these updates. I agree. One argument previously made was that it's easier to maintain in ports. One data point from me - I rarely update my ports, I update my OS much more frequently. In fact, some times my ports get so out of date I just (take off and) nuke /usr/local (from orbit, it's the only way to be sure). Also, are we trying to solve a problem by moving drm[2] to ports that won't be a problem when base is pkg'ized? If drm[2] is a package unto itself, then you don't have this problem of ports conflicting with it, at least not so much. You can either not install the base drm[2] package or deinstall it to make way for a conflicting port. Once drm[2] is pkg rm'd, it's not going to be reinstalled again when you update the base OS. And don't we have the same problem with sendmail and a few other base services? -- DE From owner-freebsd-current@freebsd.org Thu May 31 15:34: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 7D24EEF8A52 for ; Thu, 31 May 2018 15:34:20 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: from mail-qt0-x244.google.com (mail-qt0-x244.google.com [IPv6:2607:f8b0:400d:c0d::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0E7F26CA5D for ; Thu, 31 May 2018 15:34:19 +0000 (UTC) (envelope-from jmaloney@ixsystems.com) Received: by mail-qt0-x244.google.com with SMTP id e8-v6so28373177qth.0 for ; Thu, 31 May 2018 08:34:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ixsystems-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=8Td8l3Hnz9FB2DYq/62JoX+qtR3GgK+WB75cqwVMNHE=; b=EpzT35bcOMbbRtcRklQr3KHmWUM8m2LjY2wEvYhzPJNd/1V00smvH0EqD4iaMoVQ4y Q/1nTsQcE94cr3Ra0gHs3KE+QNHrLT4XpVQZgT8xgOAB08Iy6XXqDajgXFuxPOgmHEzz mxzRzzA+jMY+p60iTktakLWb3/S84GZoTy/7YJtrfBYHCVMWDd7P68RGrV8xKU/d2qu9 8ZuByJaf+ZEfDFjLvxCkTyy4++VPNiXfkKI5/n8VS38Ht0f5yNpstM1WaHXx/ZgfpyhS 1EDMaeXDJeY3MoUq2NxBbHozHH/3y22Wzg8dntlNaLJJQIiDysTB90mvFStWBgqMr/OK VVzw== 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=8Td8l3Hnz9FB2DYq/62JoX+qtR3GgK+WB75cqwVMNHE=; b=KPq5xkrdSPvEQ2E6gUVAxLibpLYK8XV8Ql5xF7inddyuCCxlN9uaoJf41NqsegColP 3GQf/g67zxNYGhC0DZTIN1xIv7p+mpHwuYFDvHSB34iRRYD73lBWaBZ0z9ZKwt34U9xt DDeiUF+5nGEDMyQTWXTog2gegJa8MADnDsT6eYcEuwHh+sCP1OKtZZIrBX7u2F2bZXJO BnGqDX77XF0E4ZQqr4EMixy3oCFo/KcJ8GKKqSaGH1DfjZX0OhenNNWkiVnN7Eq3wwCG bMjRCsn61GwnVh24XStZdk4H2vqVWkml0P2Awq2+TQ/qvMiOyvzMMXcA69gEHwsH89VE y6xA== X-Gm-Message-State: APt69E1X92EqVj/0OON+na6ksxRSueaOfa/ZLHdjChn7cXLVd0ONNFfc oa1ss9MHcgrvDJ6FC7xsGFCouANVnnYcFiXxg4knpw== X-Google-Smtp-Source: ADUXVKJTEUGMInL6OFYhX8gkqfOCa1gMccMFZvQpIg14kA1poWKSUFqBXzHghkFYBM5wc83tHpTNSiMonWmH9I0hSyY= X-Received: by 2002:a0c:b2ca:: with SMTP id d10-v6mr2048002qvf.16.1527780859240; Thu, 31 May 2018 08:34:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac8:41c2:0:0:0:0:0 with HTTP; Thu, 31 May 2018 08:34:18 -0700 (PDT) In-Reply-To: References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Joe Maloney Date: Thu, 31 May 2018 11:34:18 -0400 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Daniel Eischen Cc: Konstantin Belousov , Johannes Lundberg , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 15:34:20 -0000 I personally wish that more drivers, and firmware were separated from base. For example wireless firmware: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 That was a ticket which I chimed in on about a firmware I needed to make my wireless adapter work. I went through numerous efforts on IRC, and elsewhere to try to bring attention that ticket in order to attempt to get that firmware backported for several 10.x releases in a row without success. The firmware worked perfectly fine in PC-BSD where it was cherry picked for numerous 10.x releases. Technically since I was using PC-BSD, and was a committer for that project I had no real dire need to reach out to FreeBSD about the issue. I was simply trying to help anyone else who might be encountering the same issue trying to use stock FreeBSD because it was a simple backport. If my effort had turned out to be more fruitful I would have spent more time pursuing tickets, diffs, or whatever to get more things back-ported when I found them. I am not sure where the breakdown was which did not allow that to happen. Anyways I don't want to bikeshed, or anything but I just wanted to point out how I think having more drivers, and firmware in ports could be helpful to enhance compatibility for end users. Having a separate port for legacy drm could definitely make things easier to providing installation options for end users, and automating the post install action chosen in TrueOS, GhostBSD, and future derivative projects tailored for the desktop use case. For example for TrueOS we boot the installer in failsafe mode with either VESA, or SCFB depending on whether or not BIOS, or EFI is booted. Then we could simply make a checkbox for legacy intel, or skylake + to install the correct package then the module path for either driver can more or less remain the same. Eventually with something like devmatch maybe that can even be fully automatic. Joe Maloney On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen wrote: > On Thu, 31 May 2018, Konstantin Belousov wrote: > > On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: >> >> We're not replacing anything. We are moving the older drm1 and drm2 from >>> kernel to ports to make it easier for the majority of the users to load >>> the >>> correct driver without conflicts. >>> >> >> You do understand that you increase your maintainence load by this move. >> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable >> branches, so you will need to chase these updates. >> > > I agree. One argument previously made was that it's easier > to maintain in ports. One data point from me - I rarely > update my ports, I update my OS much more frequently. In > fact, some times my ports get so out of date I just > (take off and) nuke /usr/local (from orbit, it's the only > way to be sure). > > Also, are we trying to solve a problem by moving drm[2] to > ports that won't be a problem when base is pkg'ized? If > drm[2] is a package unto itself, then you don't have this > problem of ports conflicting with it, at least not so > much. You can either not install the base drm[2] package > or deinstall it to make way for a conflicting port. Once > drm[2] is pkg rm'd, it's not going to be reinstalled > again when you update the base OS. > > And don't we have the same problem with sendmail and a > few other base services? > > -- > DE > > _______________________________________________ > 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 May 31 16:02: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 DDFE1EFCEA6 for ; Thu, 31 May 2018 16:02:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 7CD5A6FBEC; Thu, 31 May 2018 16:02:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fOQ1y-0004vq-BX; Thu, 31 May 2018 18:02:27 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "Daniel Eischen" , "Joe Maloney" Cc: "Konstantin Belousov" , "Johannes Lundberg" , freebsd-current Subject: Re: [RFC] Deprecation and removal of the drm2 driver References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> Date: Thu, 31 May 2018 18:02:26 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 049f1f45ba4289533fd3e2bb72fd36da X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 16:02:30 -0000 On Thu, 31 May 2018 17:34:18 +0200, Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. > > For example wireless firmware: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 > > That was a ticket which I chimed in on about a firmware I needed to make > my > wireless adapter work. I went through numerous efforts on IRC, and > elsewhere to try to bring attention that ticket in order to attempt to > get > that firmware backported for several 10.x releases in a row without > success. The firmware worked perfectly fine in PC-BSD where it was > cherry > picked for numerous 10.x releases. I would support an idea that the FreeBSD project only delivers CURRENT (and one periodic release with security fixes) and parties like PC-BSD maintain stable branches and support for companies. I read about this somewhere a while ago and the idea sticks. Backporting to code 2+ years old is not the best use of human volunteer resources IMHO. Regards, Ronald. > > Technically since I was using PC-BSD, and was a committer for that > project > I had no real dire need to reach out to FreeBSD about the issue. I was > simply trying to help anyone else who might be encountering the same > issue > trying to use stock FreeBSD because it was a simple backport. If my > effort > had turned out to be more fruitful I would have spent more time pursuing > tickets, diffs, or whatever to get more things back-ported when I found > them. I am not sure where the breakdown was which did not allow that to > happen. Anyways I don't want to bikeshed, or anything but I just wanted > to > point out how I think having more drivers, and firmware in ports could be > helpful to enhance compatibility for end users. > > Having a separate port for legacy drm could definitely make things easier > to providing installation options for end users, and automating the post > install action chosen in TrueOS, GhostBSD, and future derivative projects > tailored for the desktop use case. For example for TrueOS we boot the > installer in failsafe mode with either VESA, or SCFB depending on whether > or not BIOS, or EFI is booted. Then we could simply make a checkbox for > legacy intel, or skylake + to install the correct package then the module > path for either driver can more or less remain the same. Eventually with > something like devmatch maybe that can even be fully automatic. > > Joe Maloney > > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen > wrote: > >> On Thu, 31 May 2018, Konstantin Belousov wrote: >> >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: >>> >>> We're not replacing anything. We are moving the older drm1 and drm2 >>> from >>>> kernel to ports to make it easier for the majority of the users to >>>> load >>>> the >>>> correct driver without conflicts. >>>> >>> >>> You do understand that you increase your maintainence load by this >>> move. >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in >>> stable >>> branches, so you will need to chase these updates. >>> >> >> I agree. One argument previously made was that it's easier >> to maintain in ports. One data point from me - I rarely >> update my ports, I update my OS much more frequently. In >> fact, some times my ports get so out of date I just >> (take off and) nuke /usr/local (from orbit, it's the only >> way to be sure). >> >> Also, are we trying to solve a problem by moving drm[2] to >> ports that won't be a problem when base is pkg'ized? If >> drm[2] is a package unto itself, then you don't have this >> problem of ports conflicting with it, at least not so >> much. You can either not install the base drm[2] package >> or deinstall it to make way for a conflicting port. Once >> drm[2] is pkg rm'd, it's not going to be reinstalled >> again when you update the base OS. >> >> And don't we have the same problem with sendmail and a >> few other base services? >> >> -- >> DE >> >> _______________________________________________ >> 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" >> > _______________________________________________ > 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 May 31 16:02: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 B1C8DEFCF0E for ; Thu, 31 May 2018 16:02:43 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f52.google.com (mail-lf0-f52.google.com [209.85.215.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C85D6FC25; Thu, 31 May 2018 16:02:43 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f52.google.com with SMTP id z142-v6so10505439lff.5; Thu, 31 May 2018 09:02:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=68w5sXAEnOA5oFcK95PaMk/iRit+GNpWd7NOS4nNKRI=; b=fJEVUYSqI6yhNG4w/YkrWXUX60LqIxQUknpThQnAFMdZNQ1sGIrI5LZv+gzITI7vY4 y8g8kPf8lO5vKAuf1rdRt8hWQv6D9z7aNHM5/9/8ywqp56eGa8tWWZa9LWdB2pNPtk/8 N8jtgr8ZvNCty71fNoFcTz4qj/Er7Vp684TxxnTLg+6+Z09YR3iuieEzTo8teHMe5l1y Dn1eV26bCm2gnv9h0/9buqcNGjA8+hxlTF8V0WSWN2Vk89DJurRIvKgRxc/6UItiKp7X AjKTIiTq02fzKBRoHzGQtZTI8oZ3NzoqOOH9gXNVpyeLe2B5UcVP1r62TcV1MyhWpimc CGPg== X-Gm-Message-State: ALKqPwfCoNcslWUMJSAfOE+waZTh/exmzB28W5gt4Yv7ofFebZMePLMO KIMgz0J4kbv+3IWgmo0oBlc9GOUh X-Google-Smtp-Source: ADUXVKI9PRmfQc0OwHZq3gCxv4QWqPC+3zYx0+ghc3UXo/gBJ34JuLV3dfnd1q6XV+oPZ95EN8pZKw== X-Received: by 2002:a2e:3e0c:: with SMTP id l12-v6mr5946609lja.23.1527782555344; Thu, 31 May 2018 09:02:35 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id k23-v6sm5299783ljh.27.2018.05.31.09.02.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 31 May 2018 09:02:33 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Joe Maloney , Daniel Eischen Cc: Konstantin Belousov , Johannes Lundberg , freebsd-current References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Andriy Gapon Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <8cd5aaf7-67ab-272b-8b81-1d0c972487e3@FreeBSD.org> Date: Thu, 31 May 2018 19:02:32 +0300 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 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 16:02:43 -0000 On 31/05/2018 18:34, Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. I would agree with you IF FreeBSD had a defined and stable Device Driver Interface. Or Thirdparty Module Interface. Or whatever the name. -- Andriy Gapon From owner-freebsd-current@freebsd.org Thu May 31 16:03: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 69DBAEFD134 for ; Thu, 31 May 2018 16:03:50 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 0EB9A6FD5D for ; Thu, 31 May 2018 16:03:49 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fOQ3I-0005IS-9e for freebsd-current@freebsd.org; Thu, 31 May 2018 18:03:48 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes Subject: Fwd: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 References: To: "FreeBSD Current" Date: Thu, 31 May 2018 18:03:48 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: Quoted-Printable From: "Ronald Klop" Message-ID: In-Reply-To: User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 70fa7ded7688ec2dda44e4941c8407df X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 16:03:50 -0000 cross-post to -current to get more feedback ------- Forwarded message ------- From: "Ronald Klop" To: freebsd-arm@freebsd.org Cc: Subject: panic: Assertion td->td_lock =3D=3D TDQ_LOCKPTR(tdq) failed at = = /usr/src/sys/kern/sched_ule.c:2137 Date: Thu, 31 May 2018 17:53:12 +0200 I had a crash on mu RPI-3B+ running freebsd 12/aarch64 from the 29 may snapshot. It was building world -j4 and portsnap extract. I will keep it in the debugger for about an hour so if I need to provide= more information, please mail me. db> show panic panic: Assertion td->td_lock =3D=3D TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 db> bt Tracing pid 20 tid 100063 td 0xfffffd00014fe000 db_trace_self() at db_stack_trace+0xf0 pc =3D 0xffff0000006680f4 lr =3D 0xffff0000000d8b18 sp =3D 0xffff000053972e10 fp =3D 0xffff000053972e40 db_stack_trace() at db_command+0x220 pc =3D 0xffff0000000d8b18 lr =3D 0xffff0000000d879c sp =3D 0xffff000053972e50 fp =3D 0xffff000053972f30 db_command() at db_command_loop+0x60 pc =3D 0xffff0000000d879c lr =3D 0xffff0000000d8560 sp =3D 0xffff000053972f40 fp =3D 0xffff000053972f60 db_command_loop() at db_trap+0xf4 pc =3D 0xffff0000000d8560 lr =3D 0xffff0000000db678 sp =3D 0xffff000053972f70 fp =3D 0xffff000053973190 db_trap() at kdb_trap+0x1d8 pc =3D 0xffff0000000db678 lr =3D 0xffff0000003beca0 sp =3D 0xffff0000539731a0 fp =3D 0xffff000053973250 kdb_trap() at do_el1h_sync+0xf0 pc =3D 0xffff0000003beca0 lr =3D 0xffff000000683094 sp =3D 0xffff000053973260 fp =3D 0xffff000053973290 do_el1h_sync() at handle_el1h_sync+0x74 pc =3D 0xffff000000683094 lr =3D 0xffff00000066a074 sp =3D 0xffff0000539732a0 fp =3D 0xffff0000539733b0 handle_el1h_sync() at kdb_enter+0x34 pc =3D 0xffff00000066a074 lr =3D 0xffff0000003be34c sp =3D 0xffff0000539733c0 fp =3D 0xffff000053973450 kdb_enter() at vpanic+0x1c4 pc =3D 0xffff0000003be34c lr =3D 0xffff00000037a3a4 sp =3D 0xffff000053973460 fp =3D 0xffff000053973510 vpanic() at kassert_panic+0x1bc pc =3D 0xffff00000037a3a4 lr =3D 0xffff00000037a134 sp =3D 0xffff000053973520 fp =3D 0xffff0000539735d0 kassert_panic() at sched_switch+0x994 pc =3D 0xffff00000037a134 lr =3D 0xffff0000003a3d1c sp =3D 0xffff0000539735e0 fp =3D 0xffff0000539736c0 sched_switch() at mi_switch+0x1a0 pc =3D 0xffff0000003a3d1c lr =3D 0xffff000000385044 sp =3D 0xffff0000539736d0 fp =3D 0xffff0000539736f0 mi_switch() at uma_reclaim_locked+0x1cc pc =3D 0xffff000000385044 lr =3D 0xffff0000006169b4 sp =3D 0xffff000053973700 fp =3D 0xffff000053973750 uma_reclaim_locked() at uma_reclaim+0x34 pc =3D 0xffff0000006169b4 lr =3D 0xffff0000006167cc sp =3D 0xffff000053973760 fp =3D 0xffff000053973770 uma_reclaim() at vm_pageout_worker+0x3e8 pc =3D 0xffff0000006167cc lr =3D 0xffff000000636d08 sp =3D 0xffff000053973780 fp =3D 0xffff000053973b10 vm_pageout_worker() at vm_pageout+0x140 pc =3D 0xffff000000636d08 lr =3D 0xffff000000635b58 sp =3D 0xffff000053973b20 fp =3D 0xffff000053973b50 vm_pageout() at fork_exit+0x7c pc =3D 0xffff000000635b58 lr =3D 0xffff00000033bb14 sp =3D 0xffff000053973b60 fp =3D 0xffff000053973b90 fork_exit() at fork_trampoline+0x10 pc =3D 0xffff00000033bb14 lr =3D 0xffff000000682e14 sp =3D 0xffff000053973ba0 fp =3D 0x0000000000000000 Accidently I had this in a xterm: (da4s1b is the label/usbswap) dT: 1.008s w: 1.000s L(q) ops/s r/s kBps ms/r w/s kBps ms/w %busy Name 18 1 0 0 0.0 1 32 430.5 42.7| mmcsd0= 0 0 0 0 0.0 0 0 0.0 0.0| da0 0 0 0 0 0.0 0 0 0.0 0.0| mmcsd0= s1 18 1 0 0 0.0 1 32 430.5 42.7| mmcsd0= s2 0 0 0 0 0.0 0 0 0.0 0.0| msdosfs/MSDOSBOOT 18 1 0 0 0.0 1 32 430.5 42.7| mmcsd0= s2a 18 1 0 0 0.0 1 32 430.6 42.7| ufs/ro= otfs 0 0 0 0 0.0 0 0 0.0 0.0| da1 0 0 0 0 0.0 0 0 0.0 0.0| da2 0 0 0 0 0.0 0 0 0.0 0.0| da3 6 315 5 52 963.9 310 2158 11.6 92.6| da4 0 0 0 0 0.0 0 0 0.0 0.0| da2s1 0 0 0 0 0.0 0 0 0.0 0.0| da2s2 6 314 5 52 963.9 309 2158 11.6 92.6| da4s1 0 0 0 0 0.0 0 0 0.0 0.0| da2s2a= 1 0 0 0 0.0 0 0 0.0 0.0| da4s1a= 5 314 5 52 963.9 309 2158 11.6 92.6| da4s1b= 0 0 0 0 0.0 0 0 0.0 0.0| ufs/oldsdrootfs 1 0 0 0 0.0 0 0 0.0 0.0| ufs/usbrootfs 5 314 5 52 963.9 309 2158 11.6 92.6| label/usbswap =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80= =E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80=E2=94=80 last pid: 74521; load averages: 3.31, 3.34, 3.72 up 0+17:21:58 17:19:13 63 processes: 3 running, 60 sleeping CPU 0: 3.9% user, 45.5% nice, 22.0% system, 2.4% interrupt, 26.3% idle= CPU 1: 1.2% user, 51.8% nice, 13.3% system, 0.4% interrupt, 33.3% idle= CPU 2: 2.0% user, 51.0% nice, 12.9% system, 0.0% interrupt, 34.1% idle= CPU 3: 1.2% user, 50.6% nice, 14.5% system, 0.8% interrupt, 32.9% idle= Mem: 522M Active, 132K Inact, 210M Laundry, 156M Wired, 60M Buf, 12M Fre= e Swap: 984M Total, 390M Used, 594M Free, 39% Inuse, 204K In, 3440K Out PID USERNAME THR PRI NICE SIZE RES STATE C TIME = CPU COMMAND 73952 ronald 1 100 15 160M 97092K CPU3 3 0:39 82.81%= c++ 73953 ronald 1 103 15 165M 106M CPU0 0 0:39 80.99%= c++ 72549 ronald 1 52 15 517M 54008K swread 3 3:31 34.70%= c++ 71551 ronald 1 52 15 448M 62524K swread 3 6:14 23.43%= c++ 2806 ronald 1 21 0 30928K 2004K select 0 5:12 2.= 58% tmux 74521 root 1 52 0 15092K 5692K biord 1 0:00 2.18%= bsdtar 94955 root 1 52 0 12660K 464K wait 1 5:03 0.71%= sh 53784 root 1 20 0 14220K 2568K nanslp 3 0:24 0.48%= gstat 67541 ronald 1 20 0 13912K 2600K CPU1 1 0:06 0.30%= top 53277 ronald 1 20 0 20992K 1464K select 0 0:07 0.18%= sshd 94954 root 1 20 0 10820K 1800K pipewr 1 0:00 0.03%= cat 746 root 1 20 0 17916K 18000K select 1 0:14 0.= 02% ntpd 5027 ronald 1 35 15 11048K 184K select 0 0:02 0.= 01% make 62849 ronald 1 35 15 14772K 468K select 0 0:06 0.01%= make 2887 ronald 1 35 15 10348K 180K select 0 0:02 0.= 01% make _______________________________________________ freebsd-arm@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-arm To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Thu May 31 16:09: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 DC5AAEFDCAB for ; Thu, 31 May 2018 16:09:51 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (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 7EF5B702A9 for ; Thu, 31 May 2018 16:09:51 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074425-b35ff700000009ce-8f-5b101cfb7d13 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id B0.59.02510.BFC101B5; Thu, 31 May 2018 12:04:11 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id w4VG4Aix006282; Thu, 31 May 2018 12:04:11 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id w4VG46jq023048 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2018 12:04:09 -0400 Date: Thu, 31 May 2018 11:04:06 -0500 From: Benjamin Kaduk To: Gary Jennejohn Cc: FreeBSD Current Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Message-ID: <20180531160406.GD27985@kduck.kaduk.org> References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180531095850.5845fd7a@ernst.home> User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrBIsWRmVeSWpSXmKPExsUixG6nrvtbRiDaoGeihsWcNx+YLFa/+s7s wOQx49N8Fo+ds+6yBzBFcdmkpOZklqUW6dslcGVs3NHOVNDOV3Ftz1qmBsbt3F2MnBwSAiYS q988YO9i5OIQEljMJPG1cwIbhLORUeLOi0VMEM5VJokjL/4xgbSwCKhK7Pp1lQXEZhNQkWjo vswMYosIaEp0vb3OCmIzCxhKNO/7C1YjLGAnsWj3KaA4Bwcv0LoXR+tATCGBcImvt1JAKngF BCVOznzCAtGpJXHj30smkBJmAWmJ5f84QExOoIGPus1BKkQFlCX29h1in8AoMAtJ8ywkzbMQ mhcwMq9ilE3JrdLNTczMKU5N1i1OTszLSy3StdDLzSzRS00p3cQIDlAX1R2Mc/56HWIU4GBU 4uHV+MIfLcSaWFZcmXuIUZKDSUmU9905oBBfUn5KZUZicUZ8UWlOavEhRgkOZiUR3illQDne lMTKqtSifJiUNAeLkjhvziLGaCGB9MSS1OzU1ILUIpisDAeHkgRvNDAShQSLUtNTK9Iyc0oQ 0kwcnCDDeYCGM4HU8BYXJOYWZ6ZD5E8xKkqJ836XBkoIgCQySvPgekEJRCJ7f80rRnGgV4R5 C0HaeYDJB677FdBgJqDBHW0gVxeXJCKkpBoYu+5+P9DaHx/Tv6Bk3pqnz7NnbZp0YnVZWId6 SZhKdCufWKVsxJ2tBcaf3hxyePnh7seFLVH7L8TffzRt7vz72V5vnm5hu6Dv+21iyQaTFSka jl/ZPSQthGauFBNn73qnN8HTPzy90fzqLANec7tDW2XqVXl/b2n7Y7AwRWv/1Ncc9zyPXXVV VmIpzkg01GIuKk4EAA5nPlD7AgAA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 16:09:52 -0000 On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > On Thu, 31 May 2018 09:52:22 +0200 > Gary Jennejohn wrote: > > > There's something totally screwy about trying to build a kernel when > > /usr/obj is not populated. > > > > I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > > fails with > > make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > > requires linker ifunc support > > > > This is total BS because > > > > /usr/bin/ld --version > > LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) > > > > which is exactly what bsd.linker.mk is looking for to set ifunc. > > > > If I do this: > > > > mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > > cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > > > > the buildkernel then succeeds. > > > > Considering that (reformatted output from make) > > > > PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: > > /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: > > /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: > > /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: > > /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: > > /sbin:/bin:/usr/sbin:/usr/bin > > > > it seems like /usr/bin/ld should be found by bsd.linker.mk and no > > error should be reported. > > > > OK, it seems that ``make clean'' does not remove the contents of > /usr/obj/usr/src/amd64.amd64/tmp/legacy. If I delete everything > under /usr/obj then ``make buildkernel'' works. > > Still, it seems pretty strange to me to make building a kernel > depend on some random junk which is left laying around under > /usr/obj. Whatever happened to the "run buildworld or kernel-toolchain before buildkernel" requirement? -Ben From owner-freebsd-current@freebsd.org Thu May 31 16:54: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 3EC3EF741CD for ; Thu, 31 May 2018 16:54:15 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 CB75A72B77 for ; Thu, 31 May 2018 16:54:14 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40xYTB6WRTzDhXb; Thu, 31 May 2018 16:54:06 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id XAfmv_Toag0f; Thu, 31 May 2018 16:54:06 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40xYTB1zrCzDhBg; Thu, 31 May 2018 16:54:06 +0000 (UTC) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: "Rodney W. Grimes" References: <201805311421.w4VEL6f1076986@pdx.rh.CN85.dnsmgr.net> Cc: freebsd-current From: Niclas Zeising Message-ID: <93da9083-35ad-688b-9e76-67bae72b0bc3@freebsd.org> Date: Thu, 31 May 2018 18:53:56 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <201805311421.w4VEL6f1076986@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.26 Precedence: 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, 31 May 2018 16:54:15 -0000 On 05/31/18 16:21, Rodney W. Grimes wrote: > > I do remeber for a long time this > was a -current only modules, is that still true, or can I > load it on 11.0, 11.1 and 11.2Beta3 now? drm-stable-kmod works on 11.2 (including the betas) and later. We can't backport the needed changes to the lkpi to the releases, for obvious reasons, but they were backported some time between 11.1 and now. Regards -- Niclas From owner-freebsd-current@freebsd.org Thu May 31 17:41: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 38875F79200 for ; Thu, 31 May 2018 17:41:53 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 C95C974AEF; Thu, 31 May 2018 17:41:52 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.127] (helo=rmmprod05.runbox) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from ) id 1fORa2-0002IT-16; Thu, 31 May 2018 19:41:42 +0200 Received: from mail by rmmprod05.runbox with local (Exim 4.86_2) (envelope-from ) id 1fORa1-0005uA-VC; Thu, 31 May 2018 19:41:41 +0200 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Thu, 31 May 2018 17:41:41 GMT From: "Jeffrey Bouquet" To: "Ronald Klop" CC: "Daniel Eischen" , "Joe Maloney" , "Konstantin Belousov" , "Johannes Lundberg" , "freebsd-current" Subject: Re: [RFC] Deprecation and removal of the drm2 driver Date: Thu, 31 May 2018 10:41:41 -0700 (PDT) X-Mailer: RMM6 In-Reply-To: Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 17:41:53 -0000 On Thu, 31 May 2018 18:02:26 +0200, "Ronald Klop" wr= ote: > On Thu, 31 May 2018 17:34:18 +0200, Joe Maloney = =20=20 > wrote: >=20 > > I personally wish that more drivers, and firmware were separated from > > base. > > > > For example wireless firmware: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D169433 > > > > That was a ticket which I chimed in on about a firmware I needed to mak= e=20=20 > > my > > wireless adapter work. I went through numerous efforts on IRC, and > > elsewhere to try to bring attention that ticket in order to attempt to= =20=20 > > get > > that firmware backported for several 10.x releases in a row without > > success. The firmware worked perfectly fine in PC-BSD where it was=20= =20 > > cherry > > picked for numerous 10.x releases. >=20 >=20 > I would support an idea that the FreeBSD project only delivers CURRENT=20= =20 > (and one periodic release with security fixes) and parties like PC-BSD=20= =20 > maintain stable branches and support for companies. >=20 > I read about this somewhere a while ago and the idea sticks. Backporting= =20=20 > to code 2+ years old is not the best use of human volunteer resources IMH= O. >=20 > Regards, > Ronald. >=20 >=20 >=20 > > > > Technically since I was using PC-BSD, and was a committer for that=20=20 > > project > > I had no real dire need to reach out to FreeBSD about the issue. I was > > simply trying to help anyone else who might be encountering the same=20= =20 > > issue > > trying to use stock FreeBSD because it was a simple backport. If my=20= =20 > > effort > > had turned out to be more fruitful I would have spent more time pursuing > > tickets, diffs, or whatever to get more things back-ported when I found > > them. I am not sure where the breakdown was which did not allow that to > > happen. Anyways I don't want to bikeshed, or anything but I just wante= d=20=20 > > to > > point out how I think having more drivers, and firmware in ports could = be > > helpful to enhance compatibility for end users. > > > > Having a separate port for legacy drm could definitely make things easi= er > > to providing installation options for end users, and automating the post > > install action chosen in TrueOS, GhostBSD, and future derivative projec= ts > > tailored for the desktop use case. For example for TrueOS we boot the > > installer in failsafe mode with either VESA, or SCFB depending on wheth= er > > or not BIOS, or EFI is booted. Then we could simply make a checkbox for > > legacy intel, or skylake + to install the correct package then the modu= le > > path for either driver can more or less remain the same. Eventually wi= th > > something like devmatch maybe that can even be fully automatic. > > > > Joe Maloney > > > > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen > > wrote: > > > >> On Thu, 31 May 2018, Konstantin Belousov wrote: > >> > >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > >>> > >>> We're not replacing anything. We are moving the older drm1 and drm2= =20=20 > >>> from > >>>> kernel to ports to make it easier for the majority of the users to= =20=20 > >>>> load > >>>> the > >>>> correct driver without conflicts. > >>>> > >>> > >>> You do understand that you increase your maintainence load by this=20= =20 > >>> move. > >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in=20= =20 > >>> stable > >>> branches, so you will need to chase these updates. > >>> > >> > >> I agree. One argument previously made was that it's easier > >> to maintain in ports. One data point from me - I rarely > >> update my ports, I update my OS much more frequently. In > >> fact, some times my ports get so out of date I just > >> (take off and) nuke /usr/local (from orbit, it's the only > >> way to be sure). > >> > >> Also, are we trying to solve a problem by moving drm[2] to > >> ports that won't be a problem when base is pkg'ized? If > >> drm[2] is a package unto itself, then you don't have this > >> problem of ports conflicting with it, at least not so > >> much. You can either not install the base drm[2] package > >> or deinstall it to make way for a conflicting port. Once > >> drm[2] is pkg rm'd, it's not going to be reinstalled > >> again when you update the base OS. > >> > >> And don't we have the same problem with sendmail and a > >> few other base services? > >> > >> -- > >> DE > >> > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to=20=20 > >> "freebsd-current-unsubscribe@freebsd.org" > >> > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to=20=20 > > "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > 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 there a way to do that and ensure that it can be installed also on low p= ower and/or non UEFI -- mbr devices such as a 700 mhz ancient CPU? with the less memory? Not important any longer here due to time constraints but would ensure maybe a ten percent greater user base from here on out than otherwise... ........................................... If my overview is correct anyway.= From owner-freebsd-current@freebsd.org Thu May 31 17: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 CC948F79BB1 for ; Thu, 31 May 2018 17:48:09 +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 65AB274F82 for ; Thu, 31 May 2018 17:48:09 +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 DEB8143A45; Thu, 31 May 2018 19:48:01 +0200 (CEST) From: Dimitry Andric Message-Id: <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_F8370567-F1DC-41BB-A27B-9F3D4EAA1CDB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Date: Thu, 31 May 2018 19:47:57 +0200 In-Reply-To: <20180531160406.GD27985@kduck.kaduk.org> Cc: Gary Jennejohn , FreeBSD Current To: Benjamin Kaduk References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 17:48:10 -0000 --Apple-Mail=_F8370567-F1DC-41BB-A27B-9F3D4EAA1CDB Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: >> On Thu, 31 May 2018 09:52:22 +0200 >> Gary Jennejohn wrote: >> >>> There's something totally screwy about trying to build a kernel when >>> /usr/obj is not populated. >>> >>> I ran ``make clean'' in /usr/src and then ``make buildkernel''. This >>> fails with >>> make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel >>> requires linker ifunc support >>> >>> This is total BS because >>> >>> /usr/bin/ld --version >>> LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) >>> >>> which is exactly what bsd.linker.mk is looking for to set ifunc. >>> >>> If I do this: >>> >>> mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin >>> cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin >>> >>> the buildkernel then succeeds. >>> >>> Considering that (reformatted output from make) >>> >>> PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: >>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: >>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: >>> /sbin:/bin:/usr/sbin:/usr/bin >>> >>> it seems like /usr/bin/ld should be found by bsd.linker.mk and no >>> error should be reported. >>> >> >> OK, it seems that ``make clean'' does not remove the contents of >> /usr/obj/usr/src/amd64.amd64/tmp/legacy. If I delete everything >> under /usr/obj then ``make buildkernel'' works. >> >> Still, it seems pretty strange to me to make building a kernel >> depend on some random junk which is left laying around under >> /usr/obj. > > Whatever happened to the "run buildworld or kernel-toolchain before > buildkernel" requirement? That is still a requirement, yes. Otherwise, you might have outdated toolchain components are in your /usr/obj. -Dimitry --Apple-Mail=_F8370567-F1DC-41BB-A27B-9F3D4EAA1CDB 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWxA1TQAKCRCwXqMKLiCW o20qAJ9MwibgMWR7yG5bC8q6GksjqGIumQCg9RS3pHS0jH02b7u0i5TRYLFP/Xg= =8B91 -----END PGP SIGNATURE----- --Apple-Mail=_F8370567-F1DC-41BB-A27B-9F3D4EAA1CDB-- From owner-freebsd-current@freebsd.org Thu May 31 17:52: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 7EB4DF7A448 for ; Thu, 31 May 2018 17:52:28 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB6387557B; Thu, 31 May 2018 17:52:27 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x229.google.com with SMTP id i14-v6so33822551wre.2; Thu, 31 May 2018 10:52:27 -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=NcXvEFMubZzXuHlE2SlhPL+G0YzX3vkOMldAYb+vd6w=; b=ISbKFrwDfKbcYAXGP7w44/8xtcFzGarfbi2itQRKGe1cNX33Z4kD7Z7IdHfem9dgg0 9hCkAC43AweuADRISfTTlWurp+xyw06imU2kCjoewhedJGb5uPkzI1VuIri2cLZ2h8Wb r9Y4XQ523FMQRhh+eR+cJWzBtcSH7vKgpmy23dkh5HVrc0FSb+UN+ZtInBBF9iOgNBYx +vjqAxC1BiuAR1YHKXwCQ7wbE0R3l8ZieAAoYpdQyphW/cElOWSii+6cTQdJ3MrD0RXr XYRHyMWJdtDBGOPqyQByV5wF8MTXywc0uFWwvOhVfK/jlAjwqaMzJ/45V3fCIwk2QOqj xaUw== 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=NcXvEFMubZzXuHlE2SlhPL+G0YzX3vkOMldAYb+vd6w=; b=fE7T+WzJEuXiZtd5bVf0ZntbwONuPCdWX82aiLT1XJFH07/ybgSmFXUdTsv0bcrLGT 75ptacPdcOOzoSuGy5uLjASyuJqAoSphvxUFxd/YejpcO6lqac4ewFpG8No+ygMhB2yx xbidbbYpRiEvqVY9eqC9iNgoZC9D1r682W08AmjPKKD/0mGl7hkcSKr6Uv3R9D8z5DUi Pc9Q+pI5y4xToqvoKIepTZz7El+5eehIiUZtcD5B65cw04jgssUuqayWdp47G5FWQDEz RtVksiKTAGZUaOT9115wa+aC1mSE4xD102tNl+dE42b0JAuiTLgbn7eFHyqrjY9gcjrV w75g== X-Gm-Message-State: ALKqPwc37OpWOnDlszZf4UOE2AUC1yR6+WJK8DDT0Zqv3yUNVc7xa2aB 609xeo0PSq5S/mSdPDxIeoSiTXP2QnnngKcVrx4= X-Google-Smtp-Source: ADUXVKKFqFWb8oZxlkyeAt5q7Jaqu3ZxBtQACerqoJRM5b5sm7jb6gXvvgsVTLzNKCKpog1VoUnNlSyz2xE2wKgxISw= X-Received: by 2002:adf:a0b9:: with SMTP id m54-v6mr5951084wrm.76.1527789146836; Thu, 31 May 2018 10:52:26 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Johannes Lundberg Date: Thu, 31 May 2018 18:51:50 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: jmaloney@ixsystems.com Cc: deischen@freebsd.org, Konstantin Belousov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 17:52:28 -0000 On Thu, May 31, 2018 at 4:34 PM Joe Maloney wrote: > I personally wish that more drivers, and firmware were separated from > base. > > I'm not a committer but as I understand there's not pre-commit integration tests.. If one had that, plus that it would test build kmod ports against the pre-commit state of head as well, then maybe this would work. > For example wireless firmware: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 > > That was a ticket which I chimed in on about a firmware I needed to make > my wireless adapter work. I went through numerous efforts on IRC, and > elsewhere to try to bring attention that ticket in order to attempt to get > that firmware backported for several 10.x releases in a row without > success. The firmware worked perfectly fine in PC-BSD where it was cherry > picked for numerous 10.x releases. > > Technically since I was using PC-BSD, and was a committer for that project > I had no real dire need to reach out to FreeBSD about the issue. I was > simply trying to help anyone else who might be encountering the same issue > trying to use stock FreeBSD because it was a simple backport. If my effort > had turned out to be more fruitful I would have spent more time pursuing > tickets, diffs, or whatever to get more things back-ported when I found > them. I am not sure where the breakdown was which did not allow that to > happen. Anyways I don't want to bikeshed, or anything but I just wanted to > point out how I think having more drivers, and firmware in ports could be > helpful to enhance compatibility for end users. > > Having a separate port for legacy drm could definitely make things easier > to providing installation options for end users, and automating the post > install action chosen in TrueOS, GhostBSD, and future derivative projects > tailored for the desktop use case. For example for TrueOS we boot the > installer in failsafe mode with either VESA, or SCFB depending on whether > or not BIOS, or EFI is booted. Then we could simply make a checkbox for > legacy intel, or skylake + to install the correct package then the module > path for either driver can more or less remain the same. Eventually with > something like devmatch maybe that can even be fully automatic. > > Joe Maloney > > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen > wrote: > >> On Thu, 31 May 2018, Konstantin Belousov wrote: >> >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: >>> >>> We're not replacing anything. We are moving the older drm1 and drm2 from >>>> kernel to ports to make it easier for the majority of the users to load >>>> the >>>> correct driver without conflicts. >>>> >>> >>> You do understand that you increase your maintainence load by this move. >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in stable >>> branches, so you will need to chase these updates. >>> >> >> I agree. One argument previously made was that it's easier >> to maintain in ports. One data point from me - I rarely >> update my ports, I update my OS much more frequently. In >> fact, some times my ports get so out of date I just >> (take off and) nuke /usr/local (from orbit, it's the only >> way to be sure). >> >> Also, are we trying to solve a problem by moving drm[2] to >> ports that won't be a problem when base is pkg'ized? If >> drm[2] is a package unto itself, then you don't have this >> problem of ports conflicting with it, at least not so >> much. You can either not install the base drm[2] package >> or deinstall it to make way for a conflicting port. Once >> drm[2] is pkg rm'd, it's not going to be reinstalled >> again when you update the base OS. >> >> And don't we have the same problem with sendmail and a >> few other base services? >> >> -- >> DE >> >> _______________________________________________ >> 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 May 31 18:08:21 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 21874F7C466 for ; Thu, 31 May 2018 18:08:21 +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 C87C3762C3 for ; Thu, 31 May 2018 18:08:20 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) (Authenticated sender: mmacy) by smtp.freebsd.org (Postfix) with ESMTPSA id 8EFC811DBD for ; Thu, 31 May 2018 18:08:20 +0000 (UTC) (envelope-from mmacy@freebsd.org) Received: by mail-io0-f177.google.com with SMTP id e20-v6so26794217iof.4 for ; Thu, 31 May 2018 11:08:20 -0700 (PDT) X-Gm-Message-State: ALKqPweVFHt+0CipVFXLK2iBZb99btq8UQoAF9WADDD/anRRKajKTrpt RnuqAlVv0ouqYUTWZUMI3WlSVxurFuhe2cLb250= X-Google-Smtp-Source: ADUXVKJ6hIX5yQVjoCeOrPPPYZdznI82cBro0zVuJOQJSDq7jNdisdAoLBpbdaVl0WQdfrahkME1QdLZ7NdYmxX+vD0= X-Received: by 2002:a6b:5009:: with SMTP id e9-v6mr7516451iob.5.1527790099526; Thu, 31 May 2018 11:08:19 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:85ca:0:0:0:0:0 with HTTP; Thu, 31 May 2018 11:08:18 -0700 (PDT) From: Matthew Macy Date: Thu, 31 May 2018 11:08:18 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: hwpmc - wither ppro and p4 To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 18:08:21 -0000 Intel now provides comprehensive tables for all performance counters and the various valid configuration permutations as text .json files. I've converted libpmc to use these and simplified the hwpmc_core to pass the values through. I'd like to remove all the existing Intel tables from the kernel. The one gotcha is that they don't support pentium pro and and pentium IV. Based on the i386 discussion I recognize that there's a great deal of sentimental attachment to older hardware. However, there's very few users of hwpmc on _amd64_ kernels on new hardware. I don't think anyone is doing low level optimization on 15 year old Intel hardware. I'm going to remove all the tables and the now unsupported p4 and ppro configuration bits in the kmod. However, if someone feels strongly enough to implement the corresponding tables for p4 and ppro I will reinstate the files in to the build. -M From owner-freebsd-current@freebsd.org Thu May 31 18: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 2178FF7CB32 for ; Thu, 31 May 2018 18:11:54 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A2A4C766C0 for ; Thu, 31 May 2018 18:11:53 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x236.google.com with SMTP id q72-v6so29177498itc.0 for ; Thu, 31 May 2018 11:11:53 -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=Vak0GIHKt84mzLMyEIzjMBfb/ILePy+Y3ERFS2E8nl8=; b=xoN3RjUHXRHNwKMJTx2t4v4UfgWslZLn+wSLewZxpPjtGYpjlkeqmTOhoNjigR9iIj +NaW9HFfyQE/2U5tjrRrWgj82v7wao9RWzHPPQ2faBF6X36I0PBDSj3sfYyCbTjTdaFd 5u6SOMkL+qZfZ/s6sl1aG+DtaNsTZMsqQzAEtskeCBQHVq2Qy78P+rpVFln9iy/1dhV2 fy2f85/HLtJNs1CfS4AcZv/yw6z0DMXSkurWvlOIe3ABJSJN42UulgTUqzp1k4PFdoJ7 8DTy3EbwITj96jD+FPSVJtztmSbxhmE+tB4eLNTH8zXlS5wPH+fF0RM76oA1DUIhrejy NDYw== 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=Vak0GIHKt84mzLMyEIzjMBfb/ILePy+Y3ERFS2E8nl8=; b=ttKzi8P8VZWMFf3PIDVTas153xYlPh6+UyOiFh2s2yB8ScMUDkiSOh0d3/w+o+KzI6 1/5iHTEonNakM2WRQVA5vEZHF2GU1Achl6MgeE5zmrYBxUwZ+bkUglLimm2RynIzzYHr FbvMDUSyLcqFkZ2pIyviisYIhE7uJRu9QMUq9eoMp2bg/Y9lpYdjpPgIIqZ8cTKob320 CqjOFfCqxm2rsF6HHtRFpgF99u21AqkGyeuK1Ub2QKqEjFxC42sDE/DnEYd4KjCSm5bY jbMFyXa8y/0e+fAvQRH58gvXIjsgMUuIXJMg+No4pgNzzAGsFAYV03FlDnEDyNCMbC4p z63w== X-Gm-Message-State: ALKqPwfpaMsXIFC/3a9eXqmjGLPL41sq0rad4a7pOuEgh1WBOQhCXWAB Tm95G+M33Z7Y9xW7pPSvT9QJyNe6lEt/oRdPcutbCw== X-Google-Smtp-Source: ADUXVKLSFLS0YJTsMmtnKWWSVyxuyMunRwdYaQqbQp+2ZKyU95WYo+9YysnWo72Tz4vFOitHPD9aslQiHXpOVx0jq5A= X-Received: by 2002:a24:42c6:: with SMTP id i189-v6mr1035434itb.73.1527790312972; Thu, 31 May 2018 11:11:52 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Thu, 31 May 2018 11:11:52 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> From: Warner Losh Date: Thu, 31 May 2018 12:11:52 -0600 X-Google-Sender-Auth: PSe1miZ-fqfd32Ewk4J7WFGOv8I Message-ID: Subject: Re: ``make buildkernel'' fails when /usr/obj is empty To: Dimitry Andric Cc: Benjamin Kaduk , Gary Jennejohn , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 18:11:54 -0000 On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > >> On Thu, 31 May 2018 09:52:22 +0200 > >> Gary Jennejohn wrote: > >> > >>> There's something totally screwy about trying to build a kernel when > >>> /usr/obj is not populated. > >>> > >>> I ran ``make clean'' in /usr/src and then ``make buildkernel''. This > >>> fails with > >>> make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel > >>> requires linker ifunc support > >>> > >>> This is total BS because > >>> > >>> /usr/bin/ld --version > >>> LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) > >>> > >>> which is exactly what bsd.linker.mk is looking for to set ifunc. > >>> > >>> If I do this: > >>> > >>> mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > >>> cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin > >>> > >>> the buildkernel then succeeds. > >>> > >>> Considering that (reformatted output from make) > >>> > >>> PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: > >>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: > >>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: > >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: > >>> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: > >>> /sbin:/bin:/usr/sbin:/usr/bin > >>> > >>> it seems like /usr/bin/ld should be found by bsd.linker.mk and no > >>> error should be reported. > >>> > >> > >> OK, it seems that ``make clean'' does not remove the contents of > >> /usr/obj/usr/src/amd64.amd64/tmp/legacy. If I delete everything > >> under /usr/obj then ``make buildkernel'' works. > >> > >> Still, it seems pretty strange to me to make building a kernel > >> depend on some random junk which is left laying around under > >> /usr/obj. > > > > Whatever happened to the "run buildworld or kernel-toolchain before > > buildkernel" requirement? > > That is still a requirement, yes. Otherwise, you might have outdated > toolchain components are in your /usr/obj. > Usually you can get away without doing that, and now that clang is the toolchain that's rebuilt (and that's not fast) people try to get away with it more and more... Warner From owner-freebsd-current@freebsd.org Thu May 31 18:19: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 BDA45F7D6EC for ; Thu, 31 May 2018 18:19: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 5958D76AF9 for ; Thu, 31 May 2018 18:19:25 +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 00DF843A4D; Thu, 31 May 2018 20:19:23 +0200 (CEST) From: Dimitry Andric Message-Id: <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_B5567DE5-22B6-46B3-9C22-D2F4A1A551CC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Date: Thu, 31 May 2018 20:19:20 +0200 In-Reply-To: Cc: Benjamin Kaduk , Gary Jennejohn , FreeBSD Current To: Warner Losh References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 18:19:25 -0000 --Apple-Mail=_B5567DE5-22B6-46B3-9C22-D2F4A1A551CC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 31 May 2018, at 20:11, Warner Losh wrote: >=20 > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric = wrote: > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > >> On Thu, 31 May 2018 09:52:22 +0200 > >> Gary Jennejohn wrote: ... > > Whatever happened to the "run buildworld or kernel-toolchain before > > buildkernel" requirement? >=20 > That is still a requirement, yes. Otherwise, you might have outdated > toolchain components are in your /usr/obj. >=20 > Usually you can get away without doing that, and now that clang is the = toolchain that's rebuilt (and that's not fast) people try to get away = with it more and more... Actually clang doesn't get updated *that* often, but there is a minor snag that one of llvm's config files = (lib/clang/include/llvm/Config/config.h) includes , so each time __FreeBSD_version is bumped, quite a lot of dependencies get triggered... The version is only used for two checks: #if __FreeBSD_version >=3D 1000052 /* Define to 1 if you have the `backtrace' function. */ #define HAVE_BACKTRACE TRUE and: /* Define to 1 if you have the `futimens' function. */ #if __FreeBSD_version >=3D 1100056 #define HAVE_FUTIMENS 1 #endif Maybe the first check could be dropped, assuming that backtrace() is always available, but I'm not sure about futimens(). Is there any supported version of FreeBSD left that does *not* have it? -Dimitry --Apple-Mail=_B5567DE5-22B6-46B3-9C22-D2F4A1A551CC 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWxA8qAAKCRCwXqMKLiCW o+FWAJ9C7rLpduS2kGwWPnviVa90f9MvBgCeKMo8tmVLyOwr65qbNmeovmN9dR8= =Nclm -----END PGP SIGNATURE----- --Apple-Mail=_B5567DE5-22B6-46B3-9C22-D2F4A1A551CC-- From owner-freebsd-current@freebsd.org Thu May 31 19:50: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 8A353FD34BA for ; Thu, 31 May 2018 19:50:16 +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 DBE167AEEF; Thu, 31 May 2018 19:50:15 +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 ESMTP id w4VJo4Lm089889; Thu, 31 May 2018 22:50:07 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w4VJo4Lm089889 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w4VJo30T089885; Thu, 31 May 2018 22:50:03 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 31 May 2018 22:50:03 +0300 From: Konstantin Belousov To: Dimitry Andric Cc: Warner Losh , Benjamin Kaduk , Gary Jennejohn , FreeBSD Current Subject: Re: ``make buildkernel'' fails when /usr/obj is empty Message-ID: <20180531195003.GZ3789@kib.kiev.ua> References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7464D18D-2879-4C2A-ADD3-BF84D80940BB@FreeBSD.org> User-Agent: Mutt/1.10.0 (2018-05-17) 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.26 Precedence: 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, 31 May 2018 19:50:16 -0000 On Thu, May 31, 2018 at 08:19:20PM +0200, Dimitry Andric wrote: > On 31 May 2018, at 20:11, Warner Losh wrote: > > > > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > > On 31 May 2018, at 18:04, Benjamin Kaduk wrote: > > > On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: > > >> On Thu, 31 May 2018 09:52:22 +0200 > > >> Gary Jennejohn wrote: > ... > > > Whatever happened to the "run buildworld or kernel-toolchain before > > > buildkernel" requirement? > > > > That is still a requirement, yes. Otherwise, you might have outdated > > toolchain components are in your /usr/obj. > > > > Usually you can get away without doing that, and now that clang is the toolchain that's rebuilt (and that's not fast) people try to get away with it more and more... > > Actually clang doesn't get updated *that* often, but there is a minor > snag that one of llvm's config files (lib/clang/include/llvm/Config/config.h) > includes , so each time __FreeBSD_version is bumped, quite > a lot of dependencies get triggered... > > The version is only used for two checks: > > #if __FreeBSD_version >= 1000052 > /* Define to 1 if you have the `backtrace' function. */ > #define HAVE_BACKTRACE TRUE > > and: > > /* Define to 1 if you have the `futimens' function. */ > #if __FreeBSD_version >= 1100056 > #define HAVE_FUTIMENS 1 > #endif > > Maybe the first check could be dropped, assuming that backtrace() is > always available, but I'm not sure about futimens(). Is there any > supported version of FreeBSD left that does *not* have it? Or you can manually define the symbols as needed on each branch, eliminating the need for osreldate.h and reusable if some other configuration variable needs to be conditionally set. From owner-freebsd-current@freebsd.org Thu May 31 20:20: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 128AFFDC9EC for ; Thu, 31 May 2018 20:20:22 +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 7CCC87C7EE; Thu, 31 May 2018 20:20:21 +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 w4VJwNlQ056836 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 31 May 2018 12:58:23 -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 w4VJwNbJ056835; Thu, 31 May 2018 12:58:23 -0700 (PDT) (envelope-from sgk) Date: Thu, 31 May 2018 12:58:23 -0700 From: Steve Kargl To: Matthew Macy Cc: freebsd-current@freebsd.org Subject: Re: hwpmc - wither ppro and p4 Message-ID: <20180531195823.GA56813@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 20:20:22 -0000 On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > Based on the i386 discussion I recognize that there's a great deal of > sentimental attachment to older hardware. However, there's very few s/sentimental/practical -- Steve From owner-freebsd-current@freebsd.org Thu May 31 20:29: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 4BD7EEEE150 for ; Thu, 31 May 2018 20:29:47 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8AA37D186; Thu, 31 May 2018 20:29:46 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 7ECB9E38; Thu, 31 May 2018 15:23:57 -0500 (CDT) Date: Thu, 31 May 2018 15:23:56 -0500 From: Mark Linimon To: Steve Kargl Cc: Matthew Macy , freebsd-current@freebsd.org Subject: Re: hwpmc - wither ppro and p4 Message-ID: <20180531202356.GA24090@lonesome.com> References: <20180531195823.GA56813@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180531195823.GA56813@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 20:29:47 -0000 On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > Based on the i386 discussion I recognize that there's a great deal of > > sentimental attachment to older hardware. However, there's very few > > s/sentimental/practical I know, but ... in this special case of _performance measurement_ code on old hardware, I'm going to have to agree with Matt. mcl From owner-freebsd-current@freebsd.org Thu May 31 20: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 29C4BEF334A for ; Thu, 31 May 2018 20:41:10 +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 B3A777DC5D; Thu, 31 May 2018 20:41:09 +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 w4VKf8hC057176 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 31 May 2018 13:41:08 -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 w4VKf8tW057175; Thu, 31 May 2018 13:41:08 -0700 (PDT) (envelope-from sgk) Date: Thu, 31 May 2018 13:41:08 -0700 From: Steve Kargl To: Mark Linimon Cc: Matthew Macy , freebsd-current@freebsd.org Subject: Re: hwpmc - wither ppro and p4 Message-ID: <20180531204108.GA56995@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180531195823.GA56813@troutmask.apl.washington.edu> <20180531202356.GA24090@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180531202356.GA24090@lonesome.com> User-Agent: Mutt/1.9.2 (2017-12-15) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 20:41:10 -0000 On Thu, May 31, 2018 at 03:23:56PM -0500, Mark Linimon wrote: > On Thu, May 31, 2018 at 12:58:23PM -0700, Steve Kargl wrote: > > On Thu, May 31, 2018 at 11:08:18AM -0700, Matthew Macy wrote: > > > > > > Based on the i386 discussion I recognize that there's a great deal of > > > sentimental attachment to older hardware. However, there's very few > > > > s/sentimental/practical > > I know, but ... in this special case of _performance measurement_ code > on old hardware, I'm going to have to agree with Matt. > I did not state that a I disagree or agree with Matt's proposed removal of support for pmc on old hardware. I simply corrected his unwarranted passive aggressive comment. -- Steve From owner-freebsd-current@freebsd.org Thu May 31 20:49: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 1E25CEF7E5F for ; Thu, 31 May 2018 20:49:49 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B8F6E7E739; Thu, 31 May 2018 20:49:48 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id C26CEE38; Thu, 31 May 2018 15:49:47 -0500 (CDT) Date: Thu, 31 May 2018 15:49:46 -0500 From: Mark Linimon To: Joe Maloney Cc: Daniel Eischen , Konstantin Belousov , Johannes Lundberg , freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180531204946.GB24090@lonesome.com> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 20:49:49 -0000 Straying off-topic from the Subject line ... On Thu, May 31, 2018 at 11:34:18AM -0400, Joe Maloney wrote: > Technically since I was using PC-BSD, and was a committer for that > project I had no real dire need to reach out to FreeBSD about the > [wireless driver issue]. I was simply trying to help anyone else > who might be encountering the same issue trying to use stock FreeBSD > because it was a simple backport. If my effort had turned out to be > more fruitful I would have spent more time pursuing tickets, diffs, > or whatever to get more things back-ported when I found them. FreeBSD doesn't do well handling problem reports. We've known it for years but no one has come up with a magic solution yet. We have volunteers willing to triage, but not enough committers willing to suspend working on their own priorities to work through the backlog. (It's understandable, really.) And the backlog is astounding. (*) I hesitate to even look, but ... kern 3270 ports 2010 bin 1607 The flow has decreased from where it was a few years ago -- this stat says that 727 total new ones have come in this month. We do slightly better turning over ports PRs -- due to the fact that we attach a maintainer field to each port. This doesn't completely solve the problem, but it goes some distance. Finally, the number of PRs with patches stands around 1021. That is particularly disappointing. Well, it's too bad we weren't able to corral you into keeping working on such things. fwiw. mcl *: there are other categories but these constitute the majority (9485 in total). From owner-freebsd-current@freebsd.org Thu May 31 22:14: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 13690F76951 for ; Thu, 31 May 2018 22:14:20 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [150.101.137.143]) by mx1.freebsd.org (Postfix) with ESMTP id 06B928347F; Thu, 31 May 2018 22:14:18 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 124-169-238-31.dyn.iinet.net.au (HELO leader.local) ([124.169.238.31]) by ipmail03.adl6.internode.on.net with ESMTP; 01 Jun 2018 07:39:08 +0930 Subject: Re: ``make buildkernel'' fails when /usr/obj is empty To: Warner Losh , Dimitry Andric Cc: Benjamin Kaduk , Gary Jennejohn , FreeBSD Current References: <20180531095222.399e7a37@ernst.home> <20180531095850.5845fd7a@ernst.home> <20180531160406.GD27985@kduck.kaduk.org> <32C087A4-1B67-4694-B769-16A347D4804E@FreeBSD.org> From: Shane Ambler Message-ID: Date: Fri, 1 Jun 2018 07:39:06 +0930 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.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.26 Precedence: 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, 31 May 2018 22:14:20 -0000 On 01/06/2018 03:41, Warner Losh wrote: > On Thu, May 31, 2018 at 11:47 AM, Dimitry Andric wrote: > >> On 31 May 2018, at 18:04, Benjamin Kaduk wrote: >>> >>> On Thu, May 31, 2018 at 09:58:50AM +0200, Gary Jennejohn wrote: >>>> On Thu, 31 May 2018 09:52:22 +0200 >>>> Gary Jennejohn wrote: >>>> >>>>> There's something totally screwy about trying to build a kernel when >>>>> /usr/obj is not populated. >>>>> >>>>> I ran ``make clean'' in /usr/src and then ``make buildkernel''. This >>>>> fails with >>>>> make[2]: "/usr/src/sys/conf/kern.pre.mk" line 125: amd64 kernel >>>>> requires linker ifunc support >>>>> >>>>> This is total BS because >>>>> >>>>> /usr/bin/ld --version >>>>> LLD 6.0.0 (FreeBSD 326565-1200002) (compatible with GNU linkers) >>>>> >>>>> which is exactly what bsd.linker.mk is looking for to set ifunc. >>>>> >>>>> If I do this: >>>>> >>>>> mkdir -p /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin >>>>> cp /usr/bin/ld /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin >>>>> >>>>> the buildkernel then succeeds. >>>>> >>>>> Considering that (reformatted output from make) >>>>> >>>>> PATH=/usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/sbin: >>>>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/usr/bin: >>>>> /usr/obj/usr/src/amd64.amd64/tmp/legacy/bin: >>>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/sbin: >>>>> /usr/obj/usr/src/amd64.amd64/tmp/usr/bin: >>>>> /sbin:/bin:/usr/sbin:/usr/bin >>>>> >>>>> it seems like /usr/bin/ld should be found by bsd.linker.mk and no >>>>> error should be reported. >>>>> >>>> >>>> OK, it seems that ``make clean'' does not remove the contents of >>>> /usr/obj/usr/src/amd64.amd64/tmp/legacy. If I delete everything >>>> under /usr/obj then ``make buildkernel'' works. >>>> >>>> Still, it seems pretty strange to me to make building a kernel >>>> depend on some random junk which is left laying around under >>>> /usr/obj. >>> >>> Whatever happened to the "run buildworld or kernel-toolchain before >>> buildkernel" requirement? >> >> That is still a requirement, yes. Otherwise, you might have outdated >> toolchain components are in your /usr/obj. >> > > Usually you can get away without doing that, and now that clang is the > toolchain that's rebuilt (and that's not fast) people try to get away with > it more and more... There is WITH_SYSTEM_COMPILER to not bootstrap if possible. -- FreeBSD - the place to B...Software Developing Shane Ambler From owner-freebsd-current@freebsd.org Thu May 31 22:34: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 A4A11F79D7C for ; Thu, 31 May 2018 22:34:59 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A8A98463B for ; Thu, 31 May 2018 22:34:58 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yb0-x232.google.com with SMTP id x36-v6so8125777ybi.0 for ; Thu, 31 May 2018 15:34:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=owIlGfV0ZgiQ+8u4omudWdSkLBIcRw/cWbABXNN33lA=; b=lXgYNdT5DWSO437BZpolJLcu+h4A4Le+Lfl+wdZVNKV3rdnze9GNkAqKdY4dYe1lVg ERVIQqtF4LWIzFka1KVeSho6wou9MrztNPj6K3aLtMqeRfhy0qZKv6Mrhm94F1SQ0K9E /vfceku47N72yjyrU3ifrzba8QXdNjT2ckGyS4H8iwLdfM5gcqINT1gd0cGGcoIb2vOu e+3M7bIlmKzzYml4OynUyLQsI4gbUHCvZAxQWyw6DBxjofEw/kfgaDp6q9RJ5ojB8pkl DbPIm7C51LchG6a5X0AXkIcZfFnkIWQeb90CaAkyhEQlS5CwzhMrwZl7Jt6TNFzAVzz4 hT/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:in-reply-to:references:from:date :message-id:subject:to:cc; bh=owIlGfV0ZgiQ+8u4omudWdSkLBIcRw/cWbABXNN33lA=; b=NnyT3PPN8bFr8KlH0uwpWPb73pK7GV1LgLxcdOKWokOa8kKepayGRaWKItqNmmbR3T q5giFeJtVEl35Zna3F23L39JLz7p2+4B5wjclCyN7LEgUVXZOa4EnKCb3dFFU1GAjn3E 9omZZkqzsSHc48zkGgXZ3CTKjLbMbEmV++lP6kihbpgI12MDR1CJAt0wkgnRAkZsCvnr LGoJHWsT6SxQsNHAtEZXwk1TFyURH2unDlXfWk43c9ygBb8Q9b2903NXm+OQImNt+eNT OAJl9XsUp033r5s++zjynZ6pCmg2N88ofc9PWm5D/mJTXeMTfdAHD7K9J3jXYL7ElGN4 4RDA== X-Gm-Message-State: ALKqPwddNsCo2xPkwN7bMGLdxEv0VE/nFR/LKRhcxk3ZKNdJs8/7aTxe fPMmBRYDX0xVTLh+h2HQgWss0MhwPBrRsW9+JLWRzw== X-Google-Smtp-Source: ADUXVKLa+7xmwjqIYb5jAWCX8Mqfn0yY09YCjLac84KiZKJ7N9l06oFUwSOnrQjg0uxt0fYbn2UJVjP8qp2c76Xfhyo= X-Received: by 2002:a25:55d4:: with SMTP id j203-v6mr4845573ybb.199.1527806098288; Thu, 31 May 2018 15:34:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:db86:0:0:0:0:0 with HTTP; Thu, 31 May 2018 15:34:57 -0700 (PDT) In-Reply-To: References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Oliver Pinter Date: Fri, 1 Jun 2018 00:34:57 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Johannes Lundberg Cc: "jmaloney@ixsystems.com" , "deischen@freebsd.org" , Konstantin Belousov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 22:34:59 -0000 On Thursday, May 31, 2018, Johannes Lundberg wrote: > On Thu, May 31, 2018 at 4:34 PM Joe Maloney > wrote: > > > I personally wish that more drivers, and firmware were separated from > > base. > > > > > I'm not a committer > > If you are not a committer, how and why want to remove drm2 from the base system? >From other side, how you want to maintain VM and other KPI changes in unmaintained and abandoned port? ;) Or how you can guarantee to everyone who breaks KPI to follow these breaks in an external abandoned port? > > but as I understand there's not pre-commit integration > tests.. If one had that, plus that it would test build kmod ports against > the pre-commit state of head as well, then maybe this would work. > > > > For example wireless firmware: > > > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 > > > > That was a ticket which I chimed in on about a firmware I needed to make > > my wireless adapter work. I went through numerous efforts on IRC, and > > elsewhere to try to bring attention that ticket in order to attempt to > get > > that firmware backported for several 10.x releases in a row without > > success. The firmware worked perfectly fine in PC-BSD where it was > cherry > > picked for numerous 10.x releases. > > > > Technically since I was using PC-BSD, and was a committer for that > project > > I had no real dire need to reach out to FreeBSD about the issue. I was > > simply trying to help anyone else who might be encountering the same > issue > > trying to use stock FreeBSD because it was a simple backport. If my > effort > > had turned out to be more fruitful I would have spent more time pursuing > > tickets, diffs, or whatever to get more things back-ported when I found > > them. I am not sure where the breakdown was which did not allow that to > > happen. Anyways I don't want to bikeshed, or anything but I just wanted > to > > point out how I think having more drivers, and firmware in ports could be > > helpful to enhance compatibility for end users. > > > > Having a separate port for legacy drm could definitely make things easier > > to providing installation options for end users, and automating the post > > install action chosen in TrueOS, GhostBSD, and future derivative projects > > tailored for the desktop use case. For example for TrueOS we boot the > > installer in failsafe mode with either VESA, or SCFB depending on whether > > or not BIOS, or EFI is booted. Then we could simply make a checkbox for > > legacy intel, or skylake + to install the correct package then the module > > path for either driver can more or less remain the same. Eventually with > > something like devmatch maybe that can even be fully automatic. > > > > Joe Maloney > > > > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen > > wrote: > > > >> On Thu, 31 May 2018, Konstantin Belousov wrote: > >> > >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: > >>> > >>> We're not replacing anything. We are moving the older drm1 and drm2 > from > >>>> kernel to ports to make it easier for the majority of the users to > load > >>>> the > >>>> correct driver without conflicts. > >>>> > >>> > >>> You do understand that you increase your maintainence load by this > move. > >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in > stable > >>> branches, so you will need to chase these updates. > >>> > >> > >> I agree. One argument previously made was that it's easier > >> to maintain in ports. One data point from me - I rarely > >> update my ports, I update my OS much more frequently. In > >> fact, some times my ports get so out of date I just > >> (take off and) nuke /usr/local (from orbit, it's the only > >> way to be sure). > >> > >> Also, are we trying to solve a problem by moving drm[2] to > >> ports that won't be a problem when base is pkg'ized? If > >> drm[2] is a package unto itself, then you don't have this > >> problem of ports conflicting with it, at least not so > >> much. You can either not install the base drm[2] package > >> or deinstall it to make way for a conflicting port. Once > >> drm[2] is pkg rm'd, it's not going to be reinstalled > >> again when you update the base OS. > >> > >> And don't we have the same problem with sendmail and a > >> few other base services? > >> > >> -- > >> DE > >> > >> _______________________________________________ > >> 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 > >> " > >> > > > > > _______________________________________________ > 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 May 31 23:00: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 9C15AF7DE17 for ; Thu, 31 May 2018 23:00:40 +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 0365185A2E; Thu, 31 May 2018 23:00:39 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.208] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id f99856b2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Thu, 31 May 2018 16:00:37 -0700 (PDT) Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Oliver Pinter , Johannes Lundberg Cc: "jmaloney@ixsystems.com" , "deischen@freebsd.org" , Konstantin Belousov , freebsd-current References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Pete Wright Message-ID: Date: Thu, 31 May 2018 16:00:36 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 31 May 2018 23:00:40 -0000 On 05/31/2018 15:34, Oliver Pinter wrote: > On Thursday, May 31, 2018, Johannes Lundberg wrote: > >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney >> wrote: >> >>> I personally wish that more drivers, and firmware were separated from >>> base. >>> >>> >> I'm not a committer > >> > If you are not a committer, how and why want to remove drm2 from the base > system? Johannes did not start this threat.  A committer, Niclas Zeising, did.  Johannes has stepped up and done a ton of work (along with many others, some committers and some not) to get modern intel and amd GPU's working under freebsd.  this was something that was a gaping hole in freebsd when this work started a bit over a year ago, and i'm not sure why more committers weren't embarrassed by this gap nor motivated to chip in. regardless - not sure why you'd take his comment out of context :/ the full quote was: "I'm not a committer but as I understand there's not pre-commit integration tests.. If one had that, plus that it would test build kmod ports against the pre-commit state of head as well, then maybe this would work." not really sure what's controversial about that statement which would prompt your reply - but i guess people dedicating their spare time to help create useful things for others shouldn't go unpunished. well i guess i broke my promise to ignore this bikeshed :( -p -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Thu May 31 23:38: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 74B2AFD040E for ; Thu, 31 May 2018 23:38:31 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 026A38708A for ; Thu, 31 May 2018 23:38:31 +0000 (UTC) (envelope-from oliver.pinter@hardenedbsd.org) Received: by mail-yw0-x231.google.com with SMTP id r19-v6so4406301ywc.10 for ; Thu, 31 May 2018 16:38:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Mu4Cb9xL3LdAPiOWl85QKO0LzQyETFqb2pQndN9kY7E=; b=0Wt7fXUgtmfRRRv0vPcJ6UzYnSKN4a7B+w/AzkF1aqJuoGprYe6xEczpiIEX7+cSrT MzXXblUysZfPbtB81N5xvR4ARW7ontA0yaWKF4lTOzoy33iSojq2nIrP+dVyPZ1KopZo c/iumyfWBTlkxuQoiIjWGfl3YW6K8p61+C8lSXu2ouBOdsd8kLZ+q/if5J1GYolxm8L8 X1V8rRZo/wMt7LkXCcEUI/6B7qVdFXV2l0DwPVsOqsV0NqSPgPVHMyq8vMg44aAV2/7x emdEognItgCAWVc67TLfAzMZgeQKIZYQ8Q0mIuNGBh9aIN3WCPfKlWZza/tk3wzPV8Wd 8tAw== 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=Mu4Cb9xL3LdAPiOWl85QKO0LzQyETFqb2pQndN9kY7E=; b=HeN8+9pStjJkws/6E+Izps8rgdrqxaJa63MVD4PRPrgjkBz1JjyovCEJYRsa4hLpUo nlPK1DemG8/bxmPk/CUWPYYs5iXRo2CzTO/YfgQtmVrQCmTMG+vp41puaD3I/MMU2ueO NQBlRvUkaaeQiSoFYkZaC2mYotsBDSkybGIqEPK1WF8PTeFgjY7FO2WAGNQkmwqkvlLK 5kCRZtDy3d0iCVf2uJk/efSF6zBKWRYiIcxIYoIgGFKu6TcZtbo5k9lCKZYIjCLgO8hs 6pfm4iQOlXxdB8PTs1NPwsfacYMIIB26KEUlEpJ3YmrmRJVDSiZB6FocUMHMJ+PP9Crb V6Iw== X-Gm-Message-State: ALKqPwfKjcJ+9R08MjboNgABIw8tFETIAURjscRxMrw0ZoAPXKuq7ltP o5XCOONYyCQdFRTGVYn2Yh+2l9XZ0MMs2bFjraAUng== X-Google-Smtp-Source: ADUXVKJfV0NV7sVT3fq+EnaStLCC4UHpevuZ2IHfp1eSsLbnTaQ3bnOsBy7CFYURda9hx98N99Pff8ZCiFEc3LKjudg= X-Received: by 2002:a81:698b:: with SMTP id e133-v6mr4710305ywc.265.1527809910185; Thu, 31 May 2018 16:38:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a25:db86:0:0:0:0:0 with HTTP; Thu, 31 May 2018 16:38:29 -0700 (PDT) In-Reply-To: References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> From: Oliver Pinter Date: Fri, 1 Jun 2018 01:38:29 +0200 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Pete Wright Cc: Johannes Lundberg , "jmaloney@ixsystems.com" , "deischen@freebsd.org" , Konstantin Belousov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 31 May 2018 23:38:31 -0000 On Friday, June 1, 2018, Pete Wright wrote: > > > On 05/31/2018 15:34, Oliver Pinter wrote: > >> On Thursday, May 31, 2018, Johannes Lundberg wrote: >> >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney >>> wrote: >>> >>> I personally wish that more drivers, and firmware were separated from >>>> base. >>>> >>>> >>>> I'm not a committer >>> >> >> >>> If you are not a committer, how and why want to remove drm2 from the >> base >> system? >> > Johannes did not start this threat. A committer, Niclas Zeising, did. > Johannes has stepped up and done a ton of work (along with many others, > some committers and some not) to get modern intel and amd GPU's working > under freebsd. > True. Yes I agree that their work is hard and it's a very big step forward for supporting modern hardwares. And it's required modern desktops, but please don't break the existing ones. This is my only request, probably it was expressed in a harsh way, sorry. > > > this was something that was a gaping hole in freebsd when this work > started a bit over a year ago, and i'm not sure why more committers weren't > embarrassed by this gap nor motivated to chip in. > > regardless - not sure why you'd take his comment out of context :/ the > full quote was: > "I'm not a committer but as I understand there's not pre-commit > integration tests.. If one had that, plus that it would test build kmod > ports against the pre-commit state of head as well, then maybe this would > work." > > not really sure what's controversial about that statement which would > prompt your reply - but i guess people dedicating their spare time to help > create useful things for others shouldn't go unpunished. > > well i guess i broke my promise to ignore this bikeshed :( > > -p > > -- > Pete Wright > pete@nomadlogic.org > @nomadlogicLA > > From owner-freebsd-current@freebsd.org Fri Jun 1 01: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 6409EEFD012; Fri, 1 Jun 2018 01:32:39 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C0F1B6CA3C; Fri, 1 Jun 2018 01:32:38 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id o9-v6so12440105lfk.1; Thu, 31 May 2018 18:32:38 -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=BpGBwFMSs3PvhSRmME15HeVArNWV4I58xbdfdvWPhxQ=; b=nr06SBRhJClgUZ1O6xj04AzzWYYVzQNm5hwza0oCigRPAj737U4E/dEfdMd5YEakHs NaxH96z8FGzvmyHxPomk2uxQ3zKiqcu6RuHM8m/LcCYzJFI3Hn0GEJpLopjIsGp242b5 WY6C0o7Bv09pP4J2l//OeD7Cb95CfFGDmxT+Mvf0b1/AZbqYw0P2LtGm9+i+e9wsd4fb dH25kAdoqvAPW//OUu/88xqma2pqj3jRsncrc4yqAahDiZ9tGKWCvZftiJvaCnhBvpV3 OmrPCazO4UDiH8I+A/RZPbPx+2Did5C9pd7u8BrIs75Ivu+lZItsG4c53KkIOFVRiR5K TsFQ== 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=BpGBwFMSs3PvhSRmME15HeVArNWV4I58xbdfdvWPhxQ=; b=Po+Qhtv6vHuuOJgYpuAlet5B0ZqaoEsxJ4Pzx6B9CuxWc9fx2Z/bBpaE2x0BBWqcQM VsxS3dQu+ncKsc2ruDlvD+LyjrYQQCZRt0AgFQX7kial6hmMeM8DaIH/xnKPVvqRBDPW 3FHgflQvMV1RnMeqI/iEQs5KOW4KXK6qgfuxd1+iU82FNQuQ7KTwrFO4azAoMDaTPwmN 4b20UYZfEb00rENqDoYSikitd/k+CrzJbi5RNYf0nfGvf54nZsAGukbjbRd+Tce5gHwl 99dKjZjjCnBy93Wv/q5bmlmwvZAKoONnU42wjBTPIOmhHu6KxYOw2OOOrIOzIxGsWWGQ X/Xw== X-Gm-Message-State: ALKqPwduK0aYmwcDLb9HaWEge9Yq2qEQWfZfXNAPnuxt6/5AZHBIbd9n ErSYqqjVu4EsK6kIkxDmxaWa7WanhTQ1VXdXb0g= X-Google-Smtp-Source: ADUXVKLj8qPFhPtNt0piHUDQ0p/F0b9zIVhimsmgUCrzYc0eyZ0OZlcdlgjkEkZHXjvn4MVZ4780UWfM1N0J1AWDk5k= X-Received: by 2002:a2e:29cf:: with SMTP id p76-v6mr6889177ljp.12.1527816757099; Thu, 31 May 2018 18:32:37 -0700 (PDT) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 2002:ab3:724f:0:0:0:0:0 with HTTP; Thu, 31 May 2018 18:32:36 -0700 (PDT) In-Reply-To: <20180530155039.GE97814@FreeBSD.org> References: <20180530155039.GE97814@FreeBSD.org> From: Alan Somers Date: Thu, 31 May 2018 19:32:36 -0600 X-Google-Sender-Auth: 7Ne8-_LEc83ytzD-Uu_8BeQgO1k Message-ID: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: FreeBSD CURRENT , FreeBSD Cc: Ed Maste Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 01:32:39 -0000 On Wed, May 30, 2018 at 9:50 AM, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > No problems with a System76 Lemur in both UEFI and non-UEFI mode. It's a SkyLake-based system. From owner-freebsd-current@freebsd.org Fri Jun 1 03:31:45 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 A0472F7DFB2 for ; Fri, 1 Jun 2018 03:31:45 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from mail.infocus-llc.com (mail.infocus-llc.com [199.15.120.13]) (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 470997249A for ; Fri, 1 Jun 2018 03:31:45 +0000 (UTC) (envelope-from fullermd@over-yonder.net) Received: from draco.over-yonder.net (tunnel180062-pt.tunnel.tserv8.dal1.ipv6.he.net [IPv6:2001:470:1f0e:11ae::2]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.tarragon.infocus-llc.com (Postfix) with ESMTPSA id 40xqTM0qbSzWCG; Thu, 31 May 2018 22:25:11 -0500 (CDT) Received: by draco.over-yonder.net (Postfix, from userid 100) id 40xqTL0lZqz106l; Thu, 31 May 2018 22:25:10 -0500 (CDT) Date: Thu, 31 May 2018 22:25:10 -0500 From: "Matthew D. Fuller" To: Mark Linimon Cc: freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180601032510.GJ11482@over-yonder.net> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> <20180531204946.GB24090@lonesome.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180531204946.GB24090@lonesome.com> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 03:31:45 -0000 On Thu, May 31, 2018 at 03:49:46PM -0500 I heard the voice of Mark Linimon, and lo! it spake thus: > > We do slightly better turning over ports PRs -- due to the fact that > we attach a maintainer field to each port. This doesn't completely > solve the problem, but it goes some distance. >From my perspective as a maintainer of some and occasional contributor to others, I think "slightly" undersells it a bit; hardly without exception, but it generally works OK. I wrote up a couple more paragraphs about why I think it happens and what we'd need to do to import more of that sense over into src. But it was way longer than it needs to be. We get a lot more man-hours in ports/ acting as conduits for the "outside patches -> svn" pipeline because the incentives are rigged. A bad outside contribution brought into ports more often yields "hey, you should have noticed" to the committer and more opprobrium back to the submitter. A bad outside contribution brought into src falls all over the commiter. Not entirely unreasonable, since a lot of even small-ish breakages in src are much bigger deals than even large-ish breakages in ports. But it still makes it expensive to contemplate being a conduit... -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. From owner-freebsd-current@freebsd.org Fri Jun 1 03:31: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 61A1AF7DCE4; Fri, 1 Jun 2018 03:31:10 +0000 (UTC) (envelope-from christopherhall.hsw@gmail.com) Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB3B9723DF; Fri, 1 Jun 2018 03:31:09 +0000 (UTC) (envelope-from christopherhall.hsw@gmail.com) Received: by mail-pg0-x242.google.com with SMTP id l65-v6so241083pgl.8; Thu, 31 May 2018 20:31:09 -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 :mime-version:content-transfer-encoding; bh=X0ZFs1wgebB3sCetuXleiZyEWXFSEatRHwcIjE59hlo=; b=jqW0VNVezwRM1EIQxA3qETi6MkIeiD1PLhncIFDbH13Ozlk/z1MqzigwhVvRVRArMf fuIKPJuGbEBorofwSn9pwwuZ6q+YP8qjBU996QrebzYPPZoxE423pHKay157UPzuxjnw LgdSyySdwB1b5kGpZLyUHNOpgDSSi0BE10vvKDRdjUdP9UNHZ0nrRvR1ay3Nq1QZI8Z0 B0FSUWSotqlQNLD6bA2JBun/3Sur8ggAxfkaVIfqDYhWAnG3+w2BSDC5s9N1H6m4EQDG 5fGRSzI3aFGh/mK4tku3v9tXOiw7pY4dvP0lo9lTUTYJ0P3g+f64uitVndiZi79KfcYk aoLQ== 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=X0ZFs1wgebB3sCetuXleiZyEWXFSEatRHwcIjE59hlo=; b=GWjPrd7WSiKv/cVYyd+XQuzVRLVinU4ntz5BLyh52WH4Uxw++872U0jDu1mKkM/xKY MKPfFFCmt7g4G6RMf+GjF+000vwbldgl2PhPydHYjuPfTVf0RcBjIfcT5iFYybysMkAj NtaX7me+khoPaR6FumL1aKhb90HiHhzXHYZ7BcNie8MzigyqC7XQVbJ0eZS42TKy+5cR TnQVMgl751933XbChYMDeWUUUSFfHo6REmhabeiZ6v9fsM1kj0vFywFeS5pL31+BDutK uB3D4UyakiinqSDlKunY+ElKIBUDbpGaVtgZ1IpK6AHRWz9/3024R7pgnFUp2t8yqUoD 1lVw== X-Gm-Message-State: ALKqPwchGulx/bQns2ULydDS1N+mlgk//m/fjaVWmhZhDRJldpFwaa4R 4e6+VVai7KnEAUpcMm+nFXU1EPKj37I= X-Google-Smtp-Source: ADUXVKJ7Oyn8utxMG/hlPTbAlzhvfmpIlbeimAZ+6ToX5V9uPkNIQA+KuRLySE4kmpanI0BNBFesDw== X-Received: by 2002:a63:a60a:: with SMTP id t10-v6mr7479690pge.351.1527823868715; Thu, 31 May 2018 20:31:08 -0700 (PDT) Received: from localhost (2001-b030-2314-0200-f279-59ff-fe6a-4741.hinet-ip6.hinet.net. [2001:b030:2314:200:f279:59ff:fe6a:4741]) by smtp.gmail.com with ESMTPSA id g4-v6sm22492883pfg.38.2018.05.31.20.31.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 31 May 2018 20:31:08 -0700 (PDT) Date: Fri, 1 Jun 2018 11:31:02 +0800 From: Christopher Hall To: Glen Barber Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, Ed Maste Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-ID: <20180601113048.00910728@gmail.com> In-Reply-To: <20180530155039.GE97814@FreeBSD.org> References: <20180530155039.GE97814@FreeBSD.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.31; amd64-portbld-freebsd12.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 01 Jun 2018 03:49:35 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 03:31:10 -0000 Hello Glen, On Wed, 30 May 2018 15:50:39 +0000, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). on Thinkpad T420s mini image boots in both UEFI and Legacy modes, but UEFI is considerably faster. > > Thanks, > > Glen > -- Best Regards. Christopher Hall. From owner-freebsd-current@freebsd.org Fri Jun 1 04:04: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 A3451FCA629 for ; Fri, 1 Jun 2018 04:04:27 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2529473D7D for ; Fri, 1 Jun 2018 04:04:27 +0000 (UTC) (envelope-from kmacybsd@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id c128-v6so12157634oig.11 for ; Thu, 31 May 2018 21:04: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=Xz9uWxl0kvOxJmIl5TCFnLw6yZTWdjuwUxesEY24Qa0=; b=RxDk9G49kl9S53ylZywMnImKyLrAyqQQMBUSjpvRWwmwPKfEHdh05WjTfD+fT/xZUA 6GwhtFYHO4vgJWjoTRRpbFXhPu/LgQD8hEzF+vNgWVujVt1I0+7buUeCGlsc+NuzQhdl lgNgxB09ioye5U8McF/azxRouans45oCHXsSOJaU1xr6XvqvRmv12FOgwiMDpbZMXANj J4zRBnPcHOBBIaDRtRNaAfSKa1q2G3gJ2T7KCvgVMbXhU1lAFxGm6XO9K9YO8UMEkx5m RFdDdz4/EcEpX/w2dIdIHwH8fLTj+XC1YuUTsdM/0Qb3EQAOu2vFAGRf5WGOQstaCoOB TFdw== 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=Xz9uWxl0kvOxJmIl5TCFnLw6yZTWdjuwUxesEY24Qa0=; b=K/GDxHFz+GcRBJPfpzQfljDYugHOMekQF2XtPbjP16mWxtEhQarEt6ZzYt17PpN6Vm DqkNlVON0GMvw25oN4wKTLlgoCcA6/39kXWikyasJKuOsmNG+EA4qTD/maR9cln8D/xD Mp22+ncjwy5jAuNCfhTjAM3TQQ/U2dP66EKAL7ZSJSHUS4LOeY67Hr7jyf3AEikM9W0L onLmArQKk57VkSMDBfFmP6xyIl+mVPtY+KbWEvUX9UDbU4HbZdMPprNhElCTuaxw1IuT 2+LfVm6GXNy4w5NIS+xt+CrjVC3z4Qym/mL9xUPH5j0BfodrJ5YUHcdnLEcrpIOwK2vB RadQ== X-Gm-Message-State: ALKqPwcjLL3iZMJB83C/ulfPEN8ZihBsYcS3SutHyR58SCuSTR5a9aa+ ZyL/DaYpF9hV0jH9w1rSlk+WNq2dMQzEJNWI9qWcJnl1 X-Google-Smtp-Source: ADUXVKLqLz+xDhravpDzHI8TZOajKPoJityOSyayJ/sp75zbqImaWr3a2oIlqJVvVn2vRwZzFhtL7AYlxz+BTLVDieo= X-Received: by 2002:aca:3a42:: with SMTP id h63-v6mr4976858oia.251.1527825866310; Thu, 31 May 2018 21:04:26 -0700 (PDT) MIME-Version: 1.0 Sender: kmacybsd@gmail.com Received: by 2002:a9d:3f0:0:0:0:0:0 with HTTP; Thu, 31 May 2018 21:04:25 -0700 (PDT) In-Reply-To: <20180601032510.GJ11482@over-yonder.net> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> <20180531204946.GB24090@lonesome.com> <20180601032510.GJ11482@over-yonder.net> From: "K. Macy" Date: Thu, 31 May 2018 21:04:25 -0700 X-Google-Sender-Auth: t0ayEefB_HfAwyL9aM7ht0qnw5Y Message-ID: Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) To: "Matthew D. Fuller" Cc: Mark Linimon , freebsd-current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 04:04:28 -0000 > > I wrote up a couple more paragraphs about why I think it happens and > what we'd need to do to import more of that sense over into src. But > it was way longer than it needs to be. We get a lot more man-hours in > ports/ acting as conduits for the "outside patches -> svn" pipeline > because the incentives are rigged. A bad outside contribution brought > into ports more often yields "hey, you should have noticed" to the > committer and more opprobrium back to the submitter. A bad outside > contribution brought into src falls all over the commiter. > > Not entirely unreasonable, since a lot of even small-ish breakages in > src are much bigger deals than even large-ish breakages in ports. But > it still makes it expensive to contemplate being a conduit... Whereas the incentives in ports are structured such as to encourage being a conduit and arguably it's a big part of being a responsible porter, in src there is an active disincentive. A committer invites substantial criticism by breaking src by importing a change but invites no criticism for ignoring review requests or patches. There are a few people who go through the pain of wading through patches and committing them but as a general rule one has to have some level of rapport with a proxy to get changes in without a bit. Whereas with TrueOS the Git PR system lets one submit a change, the CI system builds it to verify, and then it's thumbs up or thumbs down and it goes in, undergoes further review / refinement, or is rejected outright. There's something to be said for automation. Submitting enhancements is even harder. There's always someone who will be upset by a change in existing behavior, no matter how logical a change may seem to the rest of us. This obvious change is almost 10 years old and seems completely common sense: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139389 I've been keeping it in my bookmarks hoping that Eitan will commit it, but may at some point overcome my reservations and just go ahead and commit. My problem with the bug system is classification. If a bug report refers to something I touched recently, it's easy to assign it to me. However, when I've tried wading through the bug system to find things that I might be able to fix, I have not found it easy at all. This is where culling older bug reports comes in. With a poor signal to noise ratio from too many PRs, what really happens is _fewer_ things get fixed, not more. Cheers. -M From owner-freebsd-current@freebsd.org Fri Jun 1 04: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 B256CFD3CA4 for ; Fri, 1 Jun 2018 04:38:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DD5F754A5; Fri, 1 Jun 2018 04:38:43 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x230.google.com with SMTP id 76-v6so332726itx.4; Thu, 31 May 2018 21:38:43 -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=DQK9qTybS1X8vXTvKX2NoRxERC8WDY8GyiBumqZWzJI=; b=b2tRbJQ1Fm2oyo2aULOn5+q+k/m6eAV6IXWw5gzHZSV6NyM/aaCRk9uhKXy1T9AJNs kd4b2rGhPDFwf+c3gQ0i0T/DtKs1TW17uiS0pHKuIMkol0vetCyZBNuoBQejjF1jv1j3 3pElDWmEqk+HkhRu8oeogzIS2L2DtCxq2DoGsgPtzy4mY5B1tWezc/wSJFVannDVGzVx lSTltzhNO5B9PeX2jUIjSsfgp0aqv2oOxEFa3qu0sFb6C89RYHE1W6vEGYmKeEDSaIwj r//TwD78LwgxupnsHsWSKiqhVAu4T93iHDYeMBAnyeqltUOrMO+BNOv7vrfvxz8YC1+V Kf+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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DQK9qTybS1X8vXTvKX2NoRxERC8WDY8GyiBumqZWzJI=; b=g7ecnCLymu/k3luxWVKDjySv1p/LarF7p8lT0XcDZQVfVWJGIutKnWcuXTGQL5O6Fu qIONIva1nYkA5LCNXvHjNNggUEDMzz3EaKhclQewc/v3Md1jg8lJa2ef4AgdV9axG7Hv wmqPdhEFNDz5aNTsU/zE/BDVeGrZa+ivj1o//O28U75tvSYSmbBdxW4bIxcTYRuYsi7E Uh6pLQLojLS8Mo4jK5nBFkMjawjNaSSqr6TU9jQJMokFwM3NBYZvIRKBq4yJIZNdrt4z 2YG0n/sh4xV2NxxD+xgRmQO9oSpVXXKk+uKW0paf2Nw2um/N1ZvX2v/BwlPCXHrcf9Q6 lLNA== X-Gm-Message-State: APt69E3zmGC+8LKrWFOauMjAGFbRkVcXye7MTsKbCU20Gqu2MIP7DqjI 8/SU5ctJZsUzFG9VP6xgjv/hDlXWgkvnw/QNboA= X-Google-Smtp-Source: ADUXVKLkdcPjhth3FAWD9cRue6vL6ZOIhft/4xY06CKvZEjaNioArmmuhXvs4zBdgN6hu4sTYDTr7vC++y4U22riIlc= X-Received: by 2002:a24:5686:: with SMTP id o128-v6mr2775684itb.10.1527827922618; Thu, 31 May 2018 21:38:42 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: blubee blubeeme Date: Fri, 1 Jun 2018 12:38:42 +0800 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Oliver Pinter Cc: Johannes Lundberg , Konstantin Belousov , Pete Wright , "deischen@freebsd.org" , freebsd-current , "jmaloney@ixsystems.com" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 04:38:43 -0000 On Fri, Jun 1, 2018, 07:42 Oliver Pinter wrote: > On Friday, June 1, 2018, Pete Wright wrote: > > > > > > > On 05/31/2018 15:34, Oliver Pinter wrote: > > > >> On Thursday, May 31, 2018, Johannes Lundberg > wrote: > >> > >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney > >>> wrote: > >>> > >>> I personally wish that more drivers, and firmware were separated from > >>>> base. > >>>> > >>>> > >>>> I'm not a committer > >>> > >> > >> > >>> If you are not a committer, how and why want to remove drm2 from the > >> base > >> system? > >> > > Johannes did not start this threat. A committer, Niclas Zeising, did. > > Johannes has stepped up and done a ton of work (along with many others, > > some committers and some not) to get modern intel and amd GPU's working > > under freebsd. > > > > > True. Yes I agree that their work is hard and it's a very big step forward > for supporting modern hardwares. And it's required modern desktops, but > please don't break the existing ones. Agreed This is my only request, probably it > was expressed in a harsh way, sorry. > > > > > > > > > this was something that was a gaping hole in freebsd when this work > > started a bit over a year ago, and i'm not sure why more committers > weren't > > embarrassed by this gap nor motivated to chip in. > > > > regardless - not sure why you'd take his comment out of context :/ the > > full quote was: > > "I'm not a committer but as I understand there's not pre-commit > > integration tests.. If one had that, plus that it would test build kmod > > ports against the pre-commit state of head as well, then maybe this would > > work." > > > > not really sure what's controversial about that statement which would > > prompt your reply - but i guess people dedicating their spare time to > help > > create useful things for others shouldn't go unpunished. > > > > well i guess i broke my promise to ignore this bikeshed :( > > > > -p > > > > -- > > Pete Wright > > pete@nomadlogic.org > > @nomadlogicLA > > > > > _______________________________________________ > 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 Fri Jun 1 06:09: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 2D948EF8FA8 for ; Fri, 1 Jun 2018 06:09:08 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-wr0-x235.google.com (mail-wr0-x235.google.com [IPv6:2a00:1450:400c:c0c::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 924C77F5C0; Fri, 1 Jun 2018 06:09:07 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-wr0-x235.google.com with SMTP id d8-v6so3907767wro.4; Thu, 31 May 2018 23:09: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:to :cc; bh=FEI5bA5bdSRHe6ItwWQyOjnkMrmeJuuLhP+WGTU/yFo=; b=IwB+Uk13sAdD7pxqt6OaCCEWRx18g5/gbg389JLnQoUrLFvrIlOc6eC7wWLpXbUwrB AUf2xRta1SIAN9KnkG4CiP3Ogi4QKfvIXPRsdkfQXHP+/Fwi0Mst1y1M8KcFut8EcUX2 sAqqHX39jlzeAJotzaQKtuYJwSBcDpiSjEFXeOXebyn86r3DARDR255E3bWtjgbKoa8h zHc6jKl2u3iEszEiIIkS65BwBB+0LYViR7+VFOhHBczomsTYs4uIYxLWMKGdCmmQuIZg 0Ebzuj2WZyJmu8a2ZENp7BgwxZ+GGVjjPsQNJWfU9n/ZqFA1g2l+ljRuF6kjBdKZm0/X +jWQ== 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=FEI5bA5bdSRHe6ItwWQyOjnkMrmeJuuLhP+WGTU/yFo=; b=lfBebP4Jw9nEAwbOYcMQeVSkBmHhK4hv7AWInfN7lxqHvhR8ZSwgheKzfAJf4FUMA6 hC0CTD+k194lLJhRgxEAMlhCJNaGayS7Il34eRgn8Jzq+WiihjsH30tNPJQmcBcS7I3u jpGuwu6Ysz2HhzfItcNKB2YNb3CDF0GSzSp4JBMYtyv/yufbbp0IVVW3ckYhXKBsQJPA pxXLWqXAb1/umr3ee1nGjwWa6v9wShSC9jVl0dhCRBlufNL6aUekD4q/i/A60mBrb6e5 pv/FHYREzJpCkWIi49oAC6KY+z+/ej8I8Y7Wf+fNMKZdPL+x9Fc0yHx/zDwwepXYjEXw Z/YA== X-Gm-Message-State: ALKqPwew+iWZm5sVKJ1RFCRSRdw24dvvbLDH+RatvSrnNvMTT1qOfAFE IVN6cMuHoHkZRCYGujG32yxIhgRvCdIA+Y8DnLw= X-Google-Smtp-Source: ADUXVKKE05cCRwJTI4jCecyH7WtMYcfvmDsNmY+F52mxshjKHQglqFXjaBso5LEVNYeDEGfclXn51TWIgobM+W/W+7U= X-Received: by 2002:a5d:46c6:: with SMTP id g6-v6mr1227353wrs.76.1527833346450; Thu, 31 May 2018 23:09:06 -0700 (PDT) MIME-Version: 1.0 References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> In-Reply-To: From: Johannes Lundberg Date: Fri, 1 Jun 2018 07:08:29 +0100 Message-ID: Subject: Re: [RFC] Deprecation and removal of the drm2 driver To: Oliver Pinter Cc: jmaloney@ixsystems.com, deischen@freebsd.org, Konstantin Belousov , freebsd-current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 06:09:08 -0000 On Thu, May 31, 2018 at 11:34 PM Oliver Pinter < oliver.pinter@hardenedbsd.org> wrote: > > > On Thursday, May 31, 2018, Johannes Lundberg wrote: > >> On Thu, May 31, 2018 at 4:34 PM Joe Maloney >> wrote: >> >> > I personally wish that more drivers, and firmware were separated from >> > base. >> > >> > >> I'm not a committer > > >> >> > If you are not a committer, how and why want to remove drm2 from the base > system? > Nice way to shoot down people (who are working together with active committers) trying to make FreeBSD and it's derivatives a better OS for its users. As a way to help prevent breakage I suggested an upgrade to the outdated build infrastructure. Something that should be done anyway. But what do I know, I don't have a commit bit... > > From other side, how you want to maintain VM and other KPI changes in > unmaintained and abandoned port? ;) Or how you can guarantee to everyone > who breaks KPI to follow these breaks in an external abandoned port? > > >> >> but as I understand there's not pre-commit integration >> tests.. If one had that, plus that it would test build kmod ports against >> the pre-commit state of head as well, then maybe this would work. >> >> >> > For example wireless firmware: >> > >> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169433 >> > >> > That was a ticket which I chimed in on about a firmware I needed to make >> > my wireless adapter work. I went through numerous efforts on IRC, and >> > elsewhere to try to bring attention that ticket in order to attempt to >> get >> > that firmware backported for several 10.x releases in a row without >> > success. The firmware worked perfectly fine in PC-BSD where it was >> cherry >> > picked for numerous 10.x releases. >> > >> > Technically since I was using PC-BSD, and was a committer for that >> project >> > I had no real dire need to reach out to FreeBSD about the issue. I was >> > simply trying to help anyone else who might be encountering the same >> issue >> > trying to use stock FreeBSD because it was a simple backport. If my >> effort >> > had turned out to be more fruitful I would have spent more time pursuing >> > tickets, diffs, or whatever to get more things back-ported when I found >> > them. I am not sure where the breakdown was which did not allow that to >> > happen. Anyways I don't want to bikeshed, or anything but I just >> wanted to >> > point out how I think having more drivers, and firmware in ports could >> be >> > helpful to enhance compatibility for end users. >> > >> > Having a separate port for legacy drm could definitely make things >> easier >> > to providing installation options for end users, and automating the post >> > install action chosen in TrueOS, GhostBSD, and future derivative >> projects >> > tailored for the desktop use case. For example for TrueOS we boot the >> > installer in failsafe mode with either VESA, or SCFB depending on >> whether >> > or not BIOS, or EFI is booted. Then we could simply make a checkbox for >> > legacy intel, or skylake + to install the correct package then the >> module >> > path for either driver can more or less remain the same. Eventually >> with >> > something like devmatch maybe that can even be fully automatic. >> > >> > Joe Maloney >> > >> > On Thu, May 31, 2018 at 10:23 AM, Daniel Eischen >> > wrote: >> > >> >> On Thu, 31 May 2018, Konstantin Belousov wrote: >> >> >> >> On Thu, May 31, 2018 at 08:34:44AM +0100, Johannes Lundberg wrote: >> >>> >> >>> We're not replacing anything. We are moving the older drm1 and drm2 >> from >> >>>> kernel to ports to make it easier for the majority of the users to >> load >> >>>> the >> >>>> correct driver without conflicts. >> >>>> >> >>> >> >>> You do understand that you increase your maintainence load by this >> move. >> >>> dev/drm and dev/drm2 use KPIs which cannot be kept stable even in >> stable >> >>> branches, so you will need to chase these updates. >> >>> >> >> >> >> I agree. One argument previously made was that it's easier >> >> to maintain in ports. One data point from me - I rarely >> >> update my ports, I update my OS much more frequently. In >> >> fact, some times my ports get so out of date I just >> >> (take off and) nuke /usr/local (from orbit, it's the only >> >> way to be sure). >> >> >> >> Also, are we trying to solve a problem by moving drm[2] to >> >> ports that won't be a problem when base is pkg'ized? If >> >> drm[2] is a package unto itself, then you don't have this >> >> problem of ports conflicting with it, at least not so >> >> much. You can either not install the base drm[2] package >> >> or deinstall it to make way for a conflicting port. Once >> >> drm[2] is pkg rm'd, it's not going to be reinstalled >> >> again when you update the base OS. >> >> >> >> And don't we have the same problem with sendmail and a >> >> few other base services? >> >> >> >> -- >> >> DE >> >> >> >> _______________________________________________ >> >> 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 >> >> " >> >> >> > >> > >> _______________________________________________ >> 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 Fri Jun 1 06:45: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 A3656EFF116; Fri, 1 Jun 2018 06:45:10 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1773C84096; Fri, 1 Jun 2018 06:45:09 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id w516iGcN063649 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 1 Jun 2018 14:44:17 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id w516iGeE063648; Fri, 1 Jun 2018 14:44:16 +0800 (CST) (envelope-from kevlo) Date: Fri, 1 Jun 2018 14:44:16 +0800 From: Kevin Lo To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Cc: Ed Maste Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-ID: <20180601064416.GA63626@ns.kevlo.org> References: <20180530155039.GE97814@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180530155039.GE97814@FreeBSD.org> User-Agent: Mutt/1.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 06:45:10 -0000 On Wed, May 30, 2018 at 03:50:39PM +0000, Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). Tested memstick.img in both UEFI and legacy mode on : Lenovo ThinkPad T430s MSI Cubi 3 Silent Both work for me. > Thanks, > > Glen Kevin From owner-freebsd-current@freebsd.org Fri Jun 1 08:07: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 6A395FD4797; Fri, 1 Jun 2018 08:07:25 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (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 D9DC469A39; Fri, 1 Jun 2018 08:07:24 +0000 (UTC) (envelope-from pch-bCE2691D2@u-1.phicoh.com) Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1fOf5m-0000EfC; Fri, 1 Jun 2018 10:07:22 +0200 Message-Id: To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted From: Philip Homburg Sender: pch-bCE2691D2@u-1.phicoh.com In-reply-to: Your message of "Wed, 30 May 2018 15:50:39 +0000 ." <20180530155039.GE97814@FreeBSD.org> Date: Fri, 01 Jun 2018 10:07:22 +0200 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 08:07:25 -0000 >https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD >-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img Works fine on a Lenovo ThinkPad x201 Fails on a Dell PowerEdge 2950 - The USB stick doen't show up in the boot menu - After fixing the partition table entries, the USB stick does show up - And then fails with 'Missing operating system' Note that after fixing the partition table entries, it still works on the ThinkPad. From owner-freebsd-current@freebsd.org Fri Jun 1 09:12: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 A26F2F76239; Fri, 1 Jun 2018 09:12:41 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f46.google.com (mail-lf0-f46.google.com [209.85.215.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6364C6CD61; Fri, 1 Jun 2018 09:12:38 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f46.google.com with SMTP id d24-v6so13793007lfa.8; Fri, 01 Jun 2018 02:12:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:from:subject:openpgp:autocrypt:message-id :date:user-agent:mime-version:content-language :content-transfer-encoding; bh=7xH2Jr+f02nYAulnOiZSgHEGBjwz4f8AkpmCCGDX0aA=; b=UzoZp9rj9CHcjB0zpCRXyISfzyfh67qJKvN1hXmQa+9SHLwI/+RMcebmTQjv6Q31Z2 BD64T1lmlh8Y+1RWV7dnYQZHqIGHW42il2NKvb4M/dgXCfh2OZgJOmXnKCNljakZ//iR 43bgGX4PbWzDJKaGMxGzNsHcTj+sjhdpqfKUxp3EQHeZ+u7yN9ZvpmJdLqMnRdPWB6Jm lqeYYexHexZosdvsRwGTQp/16lANWm+Cnmu6GpPqYACuTxGJvc4ZwOxSuW0cl4DNvO4d Vb9ig1mrMVp7MrqzNDdG24zF3q/gKSzAWi3DBb5+q7t+sIuD88UBFgwqfx6CTZkb/jU+ 09Qw== X-Gm-Message-State: ALKqPweTMCR8Ke3MlPjqe+evmwkIGtjGToio0j7FyH6K3uNmB4Opp3QD qbKxGtTZ5pyvJduKDOER5jVM3vmZ X-Google-Smtp-Source: ADUXVKKF7npXVipnuivRgTE2Gg7OQHjg6fTi0QNwirjk5bsPCUlOuaZo5Soj2ZRpYow5GOnkBrGHtw== X-Received: by 2002:a2e:80c1:: with SMTP id r1-v6mr7906471ljg.85.1527844350919; Fri, 01 Jun 2018 02:12:30 -0700 (PDT) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id c63-v6sm8332771lfc.37.2018.06.01.02.12.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 02:12:30 -0700 (PDT) To: FreeBSD Hackers Cc: FreeBSD Current From: Andriy Gapon Subject: HPET-based NMI (debug) watchdog Openpgp: preference=signencrypt Autocrypt: addr=avg@FreeBSD.org; prefer-encrypt=mutual; keydata= xsFNBFm4LIgBEADNB/3lT7f15UKeQ52xCFQx/GqHkSxEdVyLFZTmY3KyNPQGBtyvVyBfprJ7 mAeXZWfhat6cKNRAGZcL5EmewdQuUfQfBdYmKjbw3a9GFDsDNuhDA2QwFt8BmkiVMRYyvI7l N0eVzszWCUgdc3qqM6qqcgBaqsVmJluwpvwp4ZBXmch5BgDDDb1MPO8AZ2QZfIQmplkj8Y6Z AiNMknkmgaekIINSJX8IzRzKD5WwMsin70psE8dpL/iBsA2cpJGzWMObVTtCxeDKlBCNqM1i gTXta1ukdUT7JgLEFZk9ceYQQMJJtUwzWu1UHfZn0Fs29HTqawfWPSZVbulbrnu5q55R4PlQ /xURkWQUTyDpqUvb4JK371zhepXiXDwrrpnyyZABm3SFLkk2bHlheeKU6Yql4pcmSVym1AS4 dV8y0oHAfdlSCF6tpOPf2+K9nW1CFA8b/tw4oJBTtfZ1kxXOMdyZU5fiG7xb1qDgpQKgHUX8 7Rd2T1UVLVeuhYlXNw2F+a2ucY+cMoqz3LtpksUiBppJhw099gEXehcN2JbUZ2TueJdt1FdS ztnZmsHUXLxrRBtGwqnFL7GSd6snpGIKuuL305iaOGODbb9c7ne1JqBbkw1wh8ci6vvwGlzx rexzimRaBzJxlkjNfMx8WpCvYebGMydNoeEtkWldtjTNVsUAtQARAQABzR5BbmRyaXkgR2Fw b24gPGF2Z0BGcmVlQlNELm9yZz7CwZQEEwEIAD4WIQS+LEO7ngQnXA4Bjr538m7TUc1yjwUC WbgsiAIbIwUJBaOagAULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgAAKCRB38m7TUc1yj+JAEACV l9AK/nOWAt/9cufV2fRj0hdOqB1aCshtSrwHk/exXsDa4/FkmegxXQGY+3GWX3deIyesbVRL rYdtdK0dqJyT1SBqXK1h3/at9rxr9GQA6KWOxTjUFURsU7ok/6SIlm8uLRPNKO+yq0GDjgaO LzN+xykuBA0FlhQAXJnpZLcVfPJdWv7sSHGedL5ln8P8rxR+XnmsA5TUaaPcbhTB+mG+iKFj GghASDSfGqLWFPBlX/fpXikBDZ1gvOr8nyMY9nXhgfXpq3B6QCRYKPy58ChrZ5weeJZ29b7/ QdEO8NFNWHjSD9meiLdWQaqo9Y7uUxN3wySc/YUZxtS0bhAd8zJdNPsJYG8sXgKjeBQMVGuT eCAJFEYJqbwWvIXMfVWop4+O4xB+z2YE3jAbG/9tB/GSnQdVSj3G8MS80iLS58frnt+RSEw/ psahrfh0dh6SFHttE049xYiC+cM8J27Aaf0i9RflyITq57NuJm+AHJoU9SQUkIF0nc6lfA+o JRiyRlHZHKoRQkIg4aiKaZSWjQYRl5Txl0IZUP1dSWMX4s3XTMurC/pnja45dge/4ESOtJ9R 8XuIWg45Oq6MeIWdjKddGhRj3OohsltKgkEU3eLKYtB6qRTQypHHUawCXz88uYt5e3w4V16H lCpSTZV/EVHnNe45FVBlvK7k7HFfDDkryM7BTQRZuCyIARAAlq0slcsVboY/+IUJdcbEiJRW be9HKVz4SUchq0z9MZPX/0dcnvz/gkyYA+OuM78dNS7Mbby5dTvOqfpLJfCuhaNYOhlE0wY+ 1T6Tf1f4c/uA3U/YiadukQ3+6TJuYGAdRZD5EqYFIkreARTVWg87N9g0fT9BEqLw9lJtEGDY EWUE7L++B8o4uu3LQFEYxcrb4K/WKmgtmFcm77s0IKDrfcX4doV92QTIpLiRxcOmCC/OCYuO jB1oaaqXQzZrCutXRK0L5XN1Y1PYjIrEzHMIXmCDlLYnpFkK+itlXwlE2ZQxkfMruCWdQXye syl2fynAe8hvp7Mms9qU2r2K9EcJiR5N1t1C2/kTKNUhcRv7Yd/vwusK7BqJbhlng5ZgRx0m WxdntU/JLEntz3QBsBsWM9Y9wf2V4tLv6/DuDBta781RsCB/UrU2zNuOEkSixlUiHxw1dccI 6CVlaWkkJBxmHX22GdDFrcjvwMNIbbyfQLuBq6IOh8nvu9vuItup7qemDG3Ms6TVwA7BD3j+ 3fGprtyW8Fd/RR2bW2+LWkMrqHffAr6Y6V3h5kd2G9Q8ZWpEJk+LG6Mk3fhZhmCnHhDu6CwN MeUvxXDVO+fqc3JjFm5OxhmfVeJKrbCEUJyM8ESWLoNHLqjywdZga4Q7P12g8DUQ1mRxYg/L HgZY3zfKOqcAEQEAAcLBfAQYAQgAJhYhBL4sQ7ueBCdcDgGOvnfybtNRzXKPBQJZuCyIAhsM BQkFo5qAAAoJEHfybtNRzXKPBVwQAKfFy9P7N3OsLDMB56A4Kf+ZT+d5cIx0Yiaf4n6w7m3i ImHHHk9FIetI4Xe54a2IXh4Bq5UkAGY0667eIs+Z1Ea6I2i27Sdo7DxGwq09Qnm/Y65ADvXs 3aBvokCcm7FsM1wky395m8xUos1681oV5oxgqeRI8/76qy0hD9WR65UW+HQgZRIcIjSel9vR XDaD2HLGPTTGr7u4v00UeTMs6qvPsa2PJagogrKY8RXdFtXvweQFz78NbXhluwix2Tb9ETPk LIpDrtzV73CaE2aqBG/KrboXT2C67BgFtnk7T7Y7iKq4/XvEdDWscz2wws91BOXuMMd4c/c4 OmGW9m3RBLufFrOag1q5yUS9QbFfyqL6dftJP3Zq/xe+mr7sbWbhPVCQFrH3r26mpmy841ym dwQnNcsbIGiBASBSKksOvIDYKa2Wy8htPmWFTEOPRpFXdGQ27awcjjnB42nngyCK5ukZDHi6 w0qK5DNQQCkiweevCIC6wc3p67jl1EMFY5+z+zdTPb3h7LeVnGqW0qBQl99vVFgzLxchKcl0 R/paSFgwqXCZhAKMuUHncJuynDOP7z5LirUeFI8qsBAJi1rXpQoLJTVcW72swZ42IdPiboqx NbTMiNOiE36GqMcTPfKylCbF45JNX4nF9ElM0E+Y8gi4cizJYBRr2FBJgay0b9Cp Message-ID: <9dbc2ddd-95f1-61aa-d8ce-6ab2b29b6b60@FreeBSD.org> Date: Fri, 1 Jun 2018 12:12:29 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.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.26 Precedence: 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, 01 Jun 2018 09:12:41 -0000 Maybe this patch / hack would be interesting to anyone else besides me :) If it is, I would appreciate any testing or review. https://reviews.freebsd.org/D15630 -- Andriy Gapon From owner-freebsd-current@freebsd.org Fri Jun 1 10:14:57 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 124E2FD51BA for ; Fri, 1 Jun 2018 10:14:57 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B136371296 for ; Fri, 1 Jun 2018 10:14:56 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 8EE8F282; Fri, 1 Jun 2018 05:14:55 -0500 (CDT) Date: Fri, 1 Jun 2018 05:14:54 -0500 From: Mark Linimon To: "Matthew D. Fuller" Cc: freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180601101454.GA25691@lonesome.com> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> <20180531204946.GB24090@lonesome.com> <20180601032510.GJ11482@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180601032510.GJ11482@over-yonder.net> User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 10:14:57 -0000 On Thu, May 31, 2018 at 10:25:10PM -0500, Matthew D. Fuller wrote: > because the incentives are rigged. A bad outside contribution brought > into ports more often yields "hey, you should have noticed" to the > committer and more opprobrium back to the submitter. I believe you're missing two important points: - there is feedback to the ports committers that goes on behind the scenes (e.g. not on public mailing lists); - everyone who uses FreeBSD needs src to work. Not everyone who uses FreeBSD needs even a large fraction of ports to work. Let me reframe this debate. To me, the correct comparison is: "compare commits to src" vs. "compare commits to key ports pieces such as Mk/, perl, apache24, &c" Commits to the latter are thoroughly tested* in external staging areas and/or "exp-runs" done by portmgr, _before_ they hit the tree. For src committers that aren't aware: since adopting the exp-runs, there have been far, far, fewer large-scale regressions of the ports tree. Check the monthly portmgr reports to see how much work is going into this -- and that doesn't count projects like gnome and kde that do their own external precommit work. Also, IMHO talking about whether this process is, or should be, automated misses the point. The distinguishing feature is the buy-in by the people who are making changes to the tree to have done sufficient testing _first_. Without that buy-in, the tools are irrelvant. Next, let me assure you that anyone who breaks those key pieces of ports hears about it _immediately_. tl:dr; at least for the key pieces, FreeBSD ports has moved away from the "throw it at the wall to see if it will stick" paradigm. That's the part of the codebase that ought to be the comparison point. mcl * almost always. They are supposed to be, in any case. Humans are involved. From owner-freebsd-current@freebsd.org Fri Jun 1 10:31: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 A27ADEF7817 for ; Fri, 1 Jun 2018 10:31:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [192.108.105.60]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.soaustin.net", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6205272BFB; Fri, 1 Jun 2018 10:31:52 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from lonesome.com (bones.soaustin.net [192.108.105.22]) by mail.soaustin.net (Postfix) with ESMTPSA id 87CDA282; Fri, 1 Jun 2018 05:31:51 -0500 (CDT) Date: Fri, 1 Jun 2018 05:31:50 -0500 From: Mark Linimon To: "K. Macy" Cc: "Matthew D. Fuller" , freebsd-current Subject: Re: PR backlog (was: [RFC] Deprecation and removal of the drm2 driver) Message-ID: <20180601103150.GB25691@lonesome.com> References: <20180524160234.GD68014@FreeBSD.org> <201805241610.w4OGAAGY041280@pdx.rh.CN85.dnsmgr.net> <20180530235156.310870d0@thor.intern.walstatt.dynvpn.de> <20180531101643.GV3789@kib.kiev.ua> <20180531204946.GB24090@lonesome.com> <20180601032510.GJ11482@over-yonder.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 10:31:52 -0000 On Thu, May 31, 2018 at 09:04:25PM -0700, K. Macy wrote: > This is where culling older bug reports comes in. Well, even with doing that, the sheer number really doesn't help the S/N that much. It may make someone a bit neurotic like me feel a bit better, but that's all. > However, when I've tried wading through the bug system to find things > that I might be able to fix, I have not found it easy at all. To me, reasoning about 'search' is the riqht direction to go. (Apologies to folks for the long URLs, but I would rather not hide the search terms here.) We've been inconsistent about applying the 'patch-ready' tag to indicate something is ready to go, but here's the current list for the Base System: https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=patch-ready&keywords_type=allwords&list_id=232422&product=Base%20System&query_format=advanced&resolution=--- 8 bugs. Not that bad. The 'patch' tag by itself produces a much less satisfying result: https://bugs.freebsd.org/bugzilla/buglist.cgi?keywords=patch&keywords_type=allwords&limit=0&list_id=232422&order=bug_id%20DESC&product=Base%20System&query_format=advanced&resolution=--- 600 bugs. Moderately overwhelming. Narrowing it down to just the 'kern' component only helps a little: https://bugs.freebsd.org/bugzilla/buglist.cgi?component=kern&keywords=patch&keywords_type=allwords&list_id=232433&product=Base%20System&query_format=advanced&resolution=--- 300 bugs. Looking for tag 'regression' within that is more satisfying: https://bugs.freebsd.org/bugzilla/buglist.cgi?component=kern&keywords=regression&keywords_type=allwords&list_id=232433&product=Base%20System&query_format=advanced&resolution=--- 82 bugs. tl:dr; expecting any sane person to 'browse' thousands of entries of any kind from _any_ kind of list, is itself madness. OTOH myself, and koobs and others, are willing to work on the search metadata to at least make 'search' reasonable. [obv. disclaimer: I am only citing statistics for Bugzilla here, not Phabricator; I simply know it better.] mcl From owner-freebsd-current@freebsd.org Fri Jun 1 09:10: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 70069F758D1 for ; Fri, 1 Jun 2018 09:10:39 +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 16F486C90B for ; Fri, 1 Jun 2018 09:10:38 +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 0663721BE3 for ; Fri, 1 Jun 2018 05:10:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 01 Jun 2018 05:10:38 -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=ibzF/LZLTkK5Mde4s +bzQYXKuq+TDJJ43XGI8pvucZw=; b=VEF59BaHbkuF/49pxcBted317YSxx8WHs GcQnvojeMgGa9sXaTcSRMGb/gRKIZPaY/4xjnLjHfDE6xL7ttMbwqJAhs9yYfH6W YXtYBQbq8dLauNqyc5ez/7MaIX4JVvFrc68FgBumcPNmpbVdkg+PCGZSg63Kif4Q 6XQTZ2xmCN8rFRZt7fH9atcfuxZxECNwVx4CH2Q0FS1TqhqED/TAmXB7JzAjjP9Z pl2xbbmcvPadcqn0eEtVgwRLi6SJrM66N/22VoO/SkYeKtasReY4E52gb72h0nyZ ewCj9a/BhzLL2f1EtQKlah2bJtW9BNon+XRAz4SmYz2yq4p7cQg6w== 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= fm2; bh=ibzF/LZLTkK5Mde4s+bzQYXKuq+TDJJ43XGI8pvucZw=; b=U8u8RKg4 TAC1vdmslm/0FQkAUKFV1QzhCiEVhkQnyZ4xiNtMuZVQW7g7FBP1srY+5W35iyG8 7miH7o7cbZ0KqLqn+qDkH6XXS4L5W042cAsyuxP1f8NSeoi3NvE700Hew8G1hLpI CL4hOGKnTRNRp+l6B9ONrqyG0FXQcfLAxCLH48RgYQFK/RInes8JQAKTBchhDbup fPgGH5oS2lu55naoJAPZUp0JxGXT9aV4WZK/mY16cEZUCvjK2uckDb0HRUPoNqNd vfj58fE8EcAjUXP/odHSVwaR+KYkmKm8Mwx6+cwJ0YnYBfUkGqlJRRj8eGIf1a4X yA0fiw4DP+XJZQ== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: from localhost (unknown [137.97.90.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 67E3DE4648 for ; Fri, 1 Jun 2018 05:10:35 -0400 (EDT) Date: Fri, 1 Jun 2018 14:40:31 +0530 From: Dhananjay Balan To: freebsd-current@freebsd.org Subject: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180601091031.72u7tqfkatsl3guh@kazhap> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20180323 X-Mailman-Approved-At: Fri, 01 Jun 2018 11:00:47 +0000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 09:10:39 -0000 Hi, (Apologies if this is the wrong list, please point me at the right one if you know) I run 12-CURRENT (r334442) on a Thinkpad X230. This machine has an Intel Centrino Advanced N 6205. But freebsd only uses in in 11g mode. When I try to scan, it won't even display 5GHz aps. wlan0: flags=8843 metric 0 mtu 1500 ether a4:4e:31:02:70:3c inet 192.168.1.108 netmask 0xffff0000 broadcast 192.168.255.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid SSID channel 7 (2442 MHz 11g ht/20) bssid bc:8a:e8:0b:a9:3f regdomain FCC4 country DE authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 protmode CTS ampdulimit 32k ampdudensity 16 -amsdutx amsdurx shortgi -stbc -ldpc wme roaming MANUAL groups: wlan >From reading man pages, I can see that iwn(4) supports 11n. Is it really supprted? What can I do to enable 11n? Here are my configs /etc/rc.conf wlans_iwn0="wlan0" ifconfig_wlan0="ssid SSID WPA SYNCDHCP" /etc/wpa_supplicant.conf ctrl_interface=/var/run/wpa_supplicant eapol_version=2 ap_scan=1 fast_reauth=1 network={ ssid="SSID" scan_ssid=0 psk="PSK" priority=5 } /boot/loader.conf # wifi if_iwn_load="YES" iwn1000fw_load="YES" iwn100fw_load="YES" iwn105fw_load="YES" iwn135fw_load="YES" iwn2000fw_load="YES" iwn2030fw_load="YES" iwn4965fw_load="YES" iwn5000fw_load="YES" iwn5150fw_load="YES" iwn6000fw_load="YES" iwn6000g2afw_load="YES" iwn6000g2bfw_load="YES" iwn6050fw_load="YES" From owner-freebsd-current@freebsd.org Fri Jun 1 13:36: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 52DBEFD3FB6; Fri, 1 Jun 2018 13:36:25 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from dec.sakura.ne.jp (dec.sakura.ne.jp [210.188.226.8]) (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 AD4BC7BE95; Fri, 1 Jun 2018 13:36:24 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from fortune.joker.local (124-18-70-98.dz.commufa.jp [124.18.70.98]) (authenticated bits=0) by dec.sakura.ne.jp (8.15.2/8.15.2/[SAKURA-WEB]/20080708) with ESMTPA id w51DaLZC017634; Fri, 1 Jun 2018 22:36:22 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Fri, 1 Jun 2018 22:36:21 +0900 From: Tomoaki AOKI To: freebsd-stable@freebsd.org Cc: freebsd-current@freebsd.org, gjb@FreeBSD.org Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted Message-Id: <20180601223621.c4ded65073ef9bafa7720a70@dec.sakura.ne.jp> In-Reply-To: <20180530155039.GE97814@FreeBSD.org> References: <20180530155039.GE97814@FreeBSD.org> Reply-To: junchoon@dec.sakura.ne.jp Organization: Junchoon corps X-Mailer: Sylpheed 3.7.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.26 Precedence: 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, 01 Jun 2018 13:36:25 -0000 Hi. Booted as expected on ThinkPad T420. Fixed with descrete (nvidia) GPU, CPU internal GPU is disabled. Both UEFI and Legacy (CSM) boot are enabled. UEFI first : Boot on UEFI mode. [Confirmed efifb is used.] Legecy first: Boot on CSM mode. [Confirmed vt(vga) is used.] UEFI boot is much faster than legacy (CSM) boot. Is firmware version needed? On Wed, 30 May 2018 15:50:39 +0000 Glen Barber wrote: > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > -- Tomoaki AOKI From owner-freebsd-current@freebsd.org Fri Jun 1 14:20: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 0B252FDEE12; Fri, 1 Jun 2018 14:20:13 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B6147E30E; Fri, 1 Jun 2018 14:20:12 +0000 (UTC) (envelope-from gljennjohn@gmail.com) Received: by mail-wm0-x229.google.com with SMTP id a8-v6so3368702wmg.5; Fri, 01 Jun 2018 07:20:12 -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=QoLkrjAq47IuWZdDFrrDj0YS8iMLxm4f7c/nwbupvoo=; b=dARQvIcpZGisSuOCQxc6JYglvP873R4yepmzinDwOMnqrGHIPNiVQBPtPtt7OGoOIE OzjBba+JXcZIXo7PfRByyNJXN2PfsGBtbbzdT7VtvsA4+pmMPDV6yh9jEjDbnkFz0Y8m Ifc27enkxbRgaeAow53AG4pOQ9ecFjNtkFejk6BoTB1qqKBWIPZdVOMzQ3tVtDbv4Ap1 iB8qQsc/tQe0sZJ0scabo6+Ny+sKGLCjT7O+e6DmBV6Pi90vmyZEJ6bDKlrwhsPN98/s 8/DiaYeJ5TWvJ2jMB7JQEdG3KccNutt4I62X+Pe3jlFbOPUk7QJG3FyEuNlHhajVOKT0 RwXQ== 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=QoLkrjAq47IuWZdDFrrDj0YS8iMLxm4f7c/nwbupvoo=; b=Dtkc13shhNEYIIdegZ6zKlSqh4tCCLN//kPJckKMj+S6OEGeAbMa15atOI8St39qUU Ba5zIPLZswEJva6n5QhA5okYUPM69XI5bEHeCeEzQdQ95fpXyB1tqWajJMWHsRLb9aoz 3VDXQlI5XEk8OmkyNsiFtOr6fbZIMF8t0v1PazJxwqFWc5Fbqz9x9xkIYxbhs5c6i/XU qipONcTUt1n2MAnqaQrKkqF9yzWPmyjmRF0Mj+q8diIg+QCBwOp8ZRh4zsz3f1l0A1hI Uf23Hr5LF9dxAnkX5wX1xrzk31/ClP5aT0DoS9FWwAhtERVn7Fisl1SnKhpRVNABv27A ouQA== X-Gm-Message-State: APt69E1qXEB4ReQZIEFS4QoyTICOZ7/c5qgAuxwbkiBrJ8gF6R82uMLB Cc9Y+yW/2ewntf+B6kkpxrSeBg== X-Google-Smtp-Source: ADUXVKLAsz0X5Os820O9l13GL1ubgRTdLiAg+NB8G+vWXMZflv+W7EnRHtdWwrE22V9jW7fex4II7A== X-Received: by 2002:a1c:f52:: with SMTP id 79-v6mr2971492wmp.24.1527862810705; Fri, 01 Jun 2018 07:20:10 -0700 (PDT) Received: from ernst.home (p5B02337A.dip0.t-ipconnect.de. [91.2.51.122]) by smtp.gmail.com with ESMTPSA id b205-v6sm2089878wmh.46.2018.06.01.07.20.09 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 01 Jun 2018 07:20:09 -0700 (PDT) Date: Fri, 1 Jun 2018 16:20:08 +0200 From: Gary Jennejohn To: Andriy Gapon Cc: FreeBSD Hackers , FreeBSD Current Subject: Re: HPET-based NMI (debug) watchdog Message-ID: <20180601162008.2088cc56@ernst.home> In-Reply-To: <9dbc2ddd-95f1-61aa-d8ce-6ab2b29b6b60@FreeBSD.org> References: <9dbc2ddd-95f1-61aa-d8ce-6ab2b29b6b60@FreeBSD.org> 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.26 Precedence: 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, 01 Jun 2018 14:20:13 -0000 On Fri, 1 Jun 2018 12:12:29 +0300 Andriy Gapon wrote: > Maybe this patch / hack would be interesting to anyone else besides me :) > If it is, I would appreciate any testing or review. > https://reviews.freebsd.org/D15630 > This could be of interest to me because my AMD Ryzen 5 1600 system hangs randomly and I don't know why. I suspect an infinite loop somewhere in the USB stack, but can't prove it because the box is totally unresponsive and I have to hit the reset switch. But my single HPET doesn't seem to be using MSI. -- Gary Jennejohn From owner-freebsd-current@freebsd.org Fri Jun 1 18:49:26 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 5ECE0EF339F for ; Fri, 1 Jun 2018 18:49:26 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (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 C8B2B6C8AF for ; Fri, 1 Jun 2018 18:49:25 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.229.134.253]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Lj61K-1g1jxi1Pwc-00dFVB for ; Fri, 01 Jun 2018 20:49:16 +0200 Date: Fri, 1 Jun 2018 20:48:41 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: create-kernel-packages-extra-flavor-debug: *** Error code 70: Unable to open plist Message-ID: <20180601204900.464563b6@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:mukZz/6iCN/wOvwk11hBq/pZzslpD/h6WvSvRsPMVxf041wJTMZ cNuABpARXynbWp2HACC9ldziJ0bqEJGy0DeFH3UOzeZ/XYWYnBveoinZ02y7f3OqYHQcpTo h79KTH1et4Y+bS6SvTsmg9yltk8D0S0ti+JwPJm267SnNR5Sa0ubevYmh4uYiI12IqPJOHI BsvYYNPUMhMPeQAxeqOfg== X-UI-Out-Filterresults: notjunk:1;V01:K0:8yajQJXXDn8=:AW71RIBgc0mF2a9ZFT0ix9 IzDLW/X2Ym1Rl14IhP3lioz/ZQ/6pskX36/oIiKDcWyUMp7+cjVstDVwp/sFGT28nGS0z6M/a BEy15W1F0tuAvApgMyDg0JF2oEHuk6l/PldEnF127OocbIZAlorsq/oyMkcmISerKDdCCclBU A740uXQkWzR3mgOmmRckIL/UgrcYVPExrU9uP1rYPYIyj+jeDdtztf/kRPzESIUSU87YsI9nL OzJU2nPKLewVuloUo8q1bR0XkF5xmhgzVedsANZlhj9pt7cAfPdxwGe22+nVfUuLJvcNRziKL 88NYjbnbZ4+4781U5C1QJk2qhYfDVfz6/jTyx/bOQ+YHUHnR8aRe1kIxWf5+1kq0pV2n5QsKk JgaIMKC4yYG4S4DwP/EplOScJFEQ345W1fWbxDIuyVW7qRKPy6k8lPKsMAacIWhP2wMuzausu BiY3a+gwx26hsAJNhhjcKsrk7NIFCvjqQbrYjerDejnD1UH3aMywXl5rQnxoQvWOYmWR8BDy6 +cQGXygKicXjdggklHReDGSWSwtSNqWhpYZwKnfNkPhx4JY1MYf8J+PQIcLW/hg7khe0f6KAS gMvPQiz7nMQV+wQnxVm21voUHiOlqQo+qld5FDbRM9xI8touGdg9V91ELhgfuPuO9MVh4TUV7 UtDIiGIzHXbM/H6CTWhMEcdZtX82WHBE+u3OVELjZVV8kbDOZCUNo4iyawvJHjG9pEIlOCh5v oJF1LS7PsooG78vc7AMg74yVdebUoNF25Okqf++YaRn1yRYL246s7XJoPKBI+JK6sF+nHD0G4 jVAUvCZ X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 18:49:26 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCk9uIHJl Y2VudCBDVVJSRU5UIHdpdGggcmVjZW50IENVUlJFTlQgc291cmNlcyAocjMzNDQ5MCksIGJ1aWxk aW5nIEZyZWVCU0QgcGFja2FnZXMgZm9yDQpGcmVlQlNELWJhc2UgZmFpbHMgb24gYXJtNjQuYWFy Y2g2NCB3aXRoIGEgY3VzdG9tIGtlcm5lbCAoc2VlIGJlbG93KS4NCg0KV0lUSF9NRVRBX01PREUg aXMgdXNlZC4NCg0KU3VjaCBwcm9ibGVtcyBkbyBub3Qgb2NjdXIgd2hlbiBidWlsZGluZyAibWFr ZSBwYWNrYWdlcyIgb24gY3VzdG9tIGtlcm5lbHMgb24gYW1kNjQgb24NCndoaWNoIEkgaGF2ZSBl cmFzZWQgYWxsIERFQlVHIGZhY2lsaXRpZXMgb3IgREVCVUcgb3B0aW9ucy4gVGhlIHNhbWUgaXMg d2l0aCBhIGN1c3RvbWlzZWQNClBJTkU2NCBrZXJuZWwuDQoNCkl0IGlzIHN0cmFuZ2UgdGhhdCB0 aGUgR0VORVJJQyBrZXJuZWwgY2FuIGJlIHBhY2thZ2VkLg0KDQpBbnkgaWRlYXM/DQoNCktpbmQg cmVnYXJkcywNCg0Kb2gNCg0KDQpbLi4uXQ0KPT09PiBDcmVhdGluZyBGcmVlQlNELXpmcy0xMi4w LnMyMDE4MDYwMTE3MzgxNA0KcGtnIC1vDQpBQklfRklMRT0vcG9vbC9zb3VyY2VzL0NVUlJFTlQv b2JqL3Bvb2wvc291cmNlcy9DVVJSRU5UL3NyYy9hcm02NC5hYXJjaDY0L3dvcmxkc3RhZ2UvYmlu L3NoDQotIC1vIEFMTE9XX0JBU0VfU0hMSUJTPXllcyAgY3JlYXRlDQotIC1NIC9wb29sL3NvdXJj ZXMvQ1VSUkVOVC9vYmovcG9vbC9zb3VyY2VzL0NVUlJFTlQvc3JjL2FybTY0LmFhcmNoNjQvd29y bGRzdGFnZS96ZnMudWNsDQotIC1wIC9wb29sL3NvdXJjZXMvQ1VSUkVOVC9vYmovcG9vbC9zb3Vy Y2VzL0NVUlJFTlQvc3JjL2FybTY0LmFhcmNoNjQvd29ybGRzdGFnZS96ZnMucGxpc3QNCi0gLXIg L3Bvb2wvc291cmNlcy9DVVJSRU5UL29iai9wb29sL3NvdXJjZXMvQ1VSUkVOVC9zcmMvYXJtNjQu YWFyY2g2NC93b3JsZHN0YWdlDQotIC1vIC9wb29sL3NvdXJjZXMvQ1VSUkVOVC9vYmovcG9vbC9z b3VyY2VzL0NVUlJFTlQvc3JjL3JlcG8vJChwa2cgLW8NCkFCSV9GSUxFPS9wb29sL3NvdXJjZXMv Q1VSUkVOVC9vYmovcG9vbC9zb3VyY2VzL0NVUlJFTlQvc3JjL2FybTY0LmFhcmNoNjQvd29ybGRz dGFnZS9iaW4vc2gNCmNvbmZpZyBBQkkpLzEyLjAuczIwMTgwNjAxMTczODE0ID09PT4gQ3JlYXRp bmcNCkZyZWVCU0Qta2VybmVsLWdlbmVyaWMtMTIuMC5zMjAxODA2MDExNzM4MTQgPT09PiBDcmVh dGluZw0KRnJlZUJTRC1rZXJuZWwtZ2VuZXJpYy1kZWJ1Zy0xMi4wLnMyMDE4MDYwMTE3MzgxNCA9 PT0+IENyZWF0aW5nDQpGcmVlQlNELWtlcm5lbC1waW5lNjQtMTIuMC5zMjAxODA2MDExNzM4MTQg PT09PiBDcmVhdGluZw0KRnJlZUJTRC1rZXJuZWwtcGluZTY0LWRlYnVnLTEyLjAuczIwMTgwNjAx MTczODE0IHBrZzogVW5hYmxlIHRvIG9wZW4gcGxpc3QNCmZpbGU6IC9wb29sL3NvdXJjZXMvQ1VS UkVOVC9vYmovcG9vbC9zb3VyY2VzL0NVUlJFTlQvc3JjL2FybTY0LmFhcmNoNjQva2VybmVsc3Rh Z2Uva2VybmVsLlBJTkU2NC9rZXJuZWwuUElORTY0LWRlYnVnLnBsaXN0DQoqKiogRXJyb3IgY29k ZSA3MA0KDQpTdG9wLg0KbWFrZVs0XTogc3RvcHBlZCBpbiAvcG9vbC9zb3VyY2VzL0NVUlJFTlQv c3JjDQoqKiogRXJyb3IgY29kZSAxDQoNCg0KLSAtLSANCk8uIEhhcnRtYW5uDQoNCkljaCB3aWRl cnNwcmVjaGUgZGVyIE51dHp1bmcgb2RlciDDnGJlcm1pdHRsdW5nIG1laW5lciBEYXRlbiBmw7xy DQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIgZGllIE1hcmt0LSBvZGVyIE1laW51bmdzZm9yc2NodW5n ICjCpyAyOCBBYnMuIDQgQkRTRykuDQotLS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQpp TFVFQVJNS0FCMFdJUVFaVlpNekF0d0MyVC84NlRyUzUyOGZ5RmhZbEFVQ1d4R1ZKQUFLQ1JEUzUy OGZ5RmhZDQpsQ25RQWZrQjZSb1I4WDc5MWwwRmtIZnAzbW15dSt2SCtlczA5cG8yNUxadFpPY3Rr YTdnSnFVWXBORW54WUJsDQppcHFUclBGdXlwQVlsQUhQQlJGQkxPK09KYnBvQWdDVnZSVmN0WWg0 bmxYSkJUNzJsOE03amV3aGdxV24vZ1JjDQpYUE1VdXhlcUc5MWVRU3hHT3Nqa0JNcDdjQk5DaVhu ZXRWN0tiM0JQNGNFcENDUTJ1YUIyDQo9cUo4Qw0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0t DQo= From owner-freebsd-current@freebsd.org Fri Jun 1 19:40: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 EFBF0EFD8EE for ; Fri, 1 Jun 2018 19:40:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8799E6EE06 for ; Fri, 1 Jun 2018 19:40:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x234.google.com with SMTP id x66-v6so16219015vka.11 for ; Fri, 01 Jun 2018 12:40:06 -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=HSW0Q81giaB91AG+fWo4ddyXiGZ4yl62HEjkstbxP3Y=; b=bryJIoOTr6KwRA+5o5sEnRnWrq+nTjLlKvBK9/2kDxzamAyVFMpDvuKJF3ioQq0MGU chV6356DDZXytvS9t4uHvSTZZas/Q8ZrE6fL28LdbtEyYIeDztP0BE4XCOqSdZ2ycqxr HXlCwI8AgHR/EO30uJV7AKXJutL3jtsdpR6dgPdyZKz4e9w/LkYvYh2kG2BaxaevpjmM OWsLF8JJn8eoN10N0QyF8VdVyy2X/xG9ivOjxfaHrRmMAUpRSdTHL2v1jv+yTcDhpiRi AtqgLYRcmaFGxoM2WSWK/Y85krWiYdfjQ+K1CwtYruInHCwENZ1IXYkk6ABFzrN2e74+ Q1Qw== 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=HSW0Q81giaB91AG+fWo4ddyXiGZ4yl62HEjkstbxP3Y=; b=o5IVmNyQtDxZByDf1Un0GRtKBs/vzluwhr8TEgKKQhUd+NNOcIMM/G2UU1wqfZ+/k7 KicqjOFuaxPc9u/nE0UOyQhtqTu3CiofBvcCNP7IZOmsyZrenpknRotVQGBY3x1lfsfn p6otujy0vrc+j9/VlnziVgukVfZqWLUoqWBTgbQu9MlssxYmwZC36UDsg2JJ5KrLAxjG fqhkJE2tAcw0knJ1rgPAdnoUpDKd0R8WLSx0e5lB4qMZNVRfxmPbwMAlyof8gqBkcF5c R5SqHR8rbaLG8ZAkkiJcXlZuwpkgUsX5oXRKMU2sQFE+M/BaHKIQyfPkTQrV2GAeRVsQ k5hA== X-Gm-Message-State: APt69E3WB+rbzJYyH/O+wYPbll22LglTns0hE/JjNRDmh0Jb3t7byeQ4 3jENLVN+6cXi1LQ+7YoeDasrcoZtokDta9oUTytTEbkf X-Google-Smtp-Source: ADUXVKJ2QI1VduzQ4a4qj4NYuNsaTAJYABZdVtRMGPfbhXszuz3SiRGcmz02Z4ZE8Ygb+ohkIcB9KLgxcbDhaP5Zm3c= X-Received: by 2002:a1f:2444:: with SMTP id k65-v6mr2272911vkk.115.1527882005866; Fri, 01 Jun 2018 12:40:05 -0700 (PDT) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 2002:a67:8f05:0:0:0:0:0 with HTTP; Fri, 1 Jun 2018 12:40:05 -0700 (PDT) In-Reply-To: <20180601091031.72u7tqfkatsl3guh@kazhap> References: <20180601091031.72u7tqfkatsl3guh@kazhap> From: Kevin Oberman Date: Fri, 1 Jun 2018 12:40:05 -0700 X-Google-Sender-Auth: p1x4kSqZbnOqbmYbr9zE8dPVyE0 Message-ID: Subject: Re: Can't seem to use 5GHz APs with Intel wireless To: Dhananjay Balan Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 19:40:07 -0000 On Fri, Jun 1, 2018 at 2:10 AM, Dhananjay Balan wrote: > Hi, > > (Apologies if this is the wrong list, please point me at the right one if > you know) > > I run 12-CURRENT (r334442) on a Thinkpad X230. This machine has an Intel > Centrino Advanced N 6205. But freebsd only uses in in 11g mode. When I > try to scan, it won't even display 5GHz aps. > > > wlan0: flags=8843 metric 0 mtu > 1500 > ether a4:4e:31:02:70:3c > inet 192.168.1.108 netmask 0xffff0000 broadcast 192.168.255.255 > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet MCS mode 11ng > status: associated > ssid SSID channel 7 (2442 MHz 11g ht/20) bssid bc:8a:e8:0b:a9:3f > regdomain FCC4 country DE authmode WPA2/802.11i privacy ON > deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 10 scanvalid 60 > protmode CTS ampdulimit 32k ampdudensity 16 -amsdutx amsdurx > shortgi > -stbc -ldpc wme roaming MANUAL > groups: wlan > > > > From reading man pages, I can see that iwn(4) supports 11n. Is it > really supprted? What can I do to enable 11n? > > > Here are my configs > > /etc/rc.conf > wlans_iwn0="wlan0" > ifconfig_wlan0="ssid SSID WPA SYNCDHCP" > > > /etc/wpa_supplicant.conf > ctrl_interface=/var/run/wpa_supplicant > eapol_version=2 > ap_scan=1 > fast_reauth=1 > > network={ > ssid="SSID" > scan_ssid=0 > psk="PSK" > priority=5 > } > > > /boot/loader.conf > # wifi > if_iwn_load="YES" > iwn1000fw_load="YES" > iwn100fw_load="YES" > iwn105fw_load="YES" > iwn135fw_load="YES" > iwn2000fw_load="YES" > iwn2030fw_load="YES" > iwn4965fw_load="YES" > iwn5000fw_load="YES" > iwn5150fw_load="YES" > iwn6000fw_load="YES" > iwn6000g2afw_load="YES" > iwn6000g2bfw_load="YES" > iwn6050fw_load="YES" > ___________________ > First, if you are using GENERIC, the driver and firmware are either in the kernel (driver) or auto-loaded. Yo should not have anything about this in your loader.conf. As far as other configuration goes, rc.local should not need (or want) the SSID. That is why it is in wpa_supplicant.conf. All global wpa_supplicant global definition is not needed except for eapol_version=2 as 1 is default. Normally teh default works, but some APs insist on V2. Still, it should not hurt to define everything. I do find the iwn driver to be pretty poor and sometimes a bit unstable, but it does work. I have 11n and 54 MHz working. what do you see with 'ifconfig wlan0 list aps'? If 54M is available, it should show up. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 From owner-freebsd-current@freebsd.org Fri Jun 1 22:37: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 D45B7FDBC56 for ; Fri, 1 Jun 2018 22:37:23 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [IPv6:2a01:4f8:140:50a2::3:1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "ns.exwg.net", Issuer "Christoph Moench-Tegeder" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7236A7837D for ; Fri, 1 Jun 2018 22:37:23 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from localhost (localhost [127.0.0.1]) by smtp.burggraben.net (Postfix) with ESMTP id CCEE06002F3 for ; Sat, 2 Jun 2018 00:37:21 +0200 (CEST) X-Spam-Scanned: by amavisd-new at exwg.net Received: from smtp.burggraben.net ([127.0.0.1]) by localhost (ns.burggraben.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWOfc7fZMMbK for ; Sat, 2 Jun 2018 00:37:12 +0200 (CEST) Received: from elch.exwg.net (elch.exwg.net [IPv6:2001:470:7120:1:127b:44ff:fe4f:148d]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "elch.exwg.net", Issuer "Christoph Moench-Tegeder" (verified OK)) by smtp.burggraben.net (Postfix) with ESMTPS for ; Sat, 2 Jun 2018 00:37:12 +0200 (CEST) Received: by elch.exwg.net (Postfix, from userid 1000) id 24E2B2730D; Sat, 2 Jun 2018 00:37:12 +0200 (CEST) Date: Sat, 2 Jun 2018 00:37:12 +0200 From: Christoph Moench-Tegeder To: freebsd-current@freebsd.org Subject: Re: Can't seem to use 5GHz APs with Intel wireless Message-ID: <20180601223711.GA93642@elch.exwg.net> References: <20180601091031.72u7tqfkatsl3guh@kazhap> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180601091031.72u7tqfkatsl3guh@kazhap> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 01 Jun 2018 22:37:24 -0000 ## Dhananjay Balan (mail@dbalan.in): > From reading man pages, I can see that iwn(4) supports 11n. Is it > really supprted? What can I do to enable 11n? The wlan system will auto-select 11n (wide channels, MIMO) as supported by interface and network. See "ht" flag in ifconfig(8). > wlans_iwn0="wlan0" > ifconfig_wlan0="ssid SSID WPA SYNCDHCP" Did you try adding "mode 11a" to select 5GHz band? (This might be out-of-date, as my WiFi stuff is all on 11) (currently I'm also using 2.4GHz only, for compatibility with some devices and the fact that I have quite some trouble running 2.4GHz and 5GHz from the same interface at the same time). Regards, Christoph -- Spare Space From owner-freebsd-current@freebsd.org Fri Jun 1 23: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 F1DD2EFB45A for ; Fri, 1 Jun 2018 23:42:18 +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 2622E7C815; Fri, 1 Jun 2018 23:42:17 +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=1527896528; bh=5REdv8+X3MLE4bjxhFVRqHtBJNQUriRWJXVZ57z 3iDQ=; b=SGskSp2fNlnEh7fRY0Zlba5X8+WNb1URQah9C+GMf+dik27h6ki7PDS JS/UvfFuwgVV3KTStVNL9s+XPSk393Dwy7Dd+q41zag0WZLb36TyTJJdGMMKLY2b dlguXf8KO52G/fjQkQmXFs2ezxCaLMi1yKFc4JUD+ut85qlOxYTM= 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 4B5311382A; Fri, 1 Jun 2018 19:42:08 -0400 (EDT) To: freebsd-current , alc@freebsd.org From: Michael Butler Subject: SVN r334499 breaks i386 kernel build Openpgp: preference=signencrypt Autocrypt: addr=imb@protected-networks.net; prefer-encrypt=mutual; keydata= xsDiBETHZAURBACJicNaIbVVVZahtQcdJeogtTLjCYAdj4kFMpy6Y3Ac19UNWDM+TrD4yFPi 5nc/pp9M/5Q4RNBr6a97fTYroTaq+vDwWdklOHwD2ZXs7FqwWOtVSIPT/rev5fUvwEF2VFYE sNDbpE5HHpP/oFUw5scEJZVyOBJSGvYb1IhV55NWswCgzkUGbG8A3s+oZXkHqTCYGW/seukD +wTo/L835xLpbTJxoxEKeGA3aWifSsRvpWWHyXye6sTkSN3SmtE9A8Pqmdb1dBEO0eOms6GD RamvCFgdvg2HesAv9l7L/7Mm9iKJs6uTAa+taIQslpumGh4PRc94IepVFzAa4Ef/FA4mWx9w P/EqNsKUPE2U5HI1decbopkxH/d/A/9Hupc10lPsXVMACd54/YZRsSTTcArheekm8qE/f8Hl 1Q7At+yuFgfMll4QPAhefnrLUanXF1bWtxG5PmaJktDYp3HOmy43giZgacgt+a3TVd6vu8Gs DnI4FOfYllq7mZFezMIulCWUYtnkMEXEeyzp39dygi7blPIjckWlQ2sc380rTWljaGFlbCBC dXRsZXIgPGltYkBwcm90ZWN0ZWQtbmV0d29ya3MubmV0PsJgBBMRAgAgBQJEx2QFAhsDBgsJ CAcDAgQVAggDBBYCAwECHgECF4AACgkQQv9rrgRC1JL7mgCdEnPeo22kqT/bES+D78QSGhNR r8cAn2xOMeu6pBrc2tDY8Ky/70HBctmjzsFNBETHZA4QCACKbm/PMn4QcyDEvIn4MF+t2E1A zgiBAkPCMtWT1CcqeUj13OwNM8qJD/mBWjCZCnr1hKVbvzOmgKaM4uDCWIcSCdoDTJx1DqMx abr+EpHz1fL6aagEOKHz5sCYOkDXt3zzZ/5RBMdkEJwunXYtAbu5e68oty+d0DFzAM3pBp6l GC0TE3VutmFR/KK66rf0KB83YQBf/IAtyqsRIQPP9t0SLfJ+kqKXf73nvAUFEtb21gZSzhTm QP87QKyQvenE8o4PQ2tEslq2jICB7pGcqIrwP4o3Hl4V+HXi3lA26MMJ5rakQB2sKKWroPVQ BiRXO+W8Qf+0oQFq38oMXR5sPOs/AAMFB/sEKcjzvkwviZOsDElthxtgrmqUNKC9G/4Fw0tK k6fMynv+bcKz85k2uWOIfefUKBFoQ0SCphU4jquJENqqy6BPTkXePlIJok2/GkF7xtHm2FPq tTTuYmoBrGsls28Z9dn2LcBwFHz59SSWM9JFPIvFr9HCkKtp6zPUsJd5b02+0wgzDubTMQS9 M2LwGSh9xK6xl4MGgngl22b0TZDh5qHwmsywOX6SbGsQfeNpkptJ4gPjShypusFyF+pevnCM wTfUPCBd/AFbu2fHFQjA8sgkr5IqXuc4PoiIBXc9upoFpDqGkYssAKbzGcRsK94a8hRROJV9 bzPyYempIWaPXr2EwkkEGBECAAkFAkTHZA4CGwwACgkQQv9rrgRC1JKqhwCgsS3SHFrWg/xW A5PXgoua8GbPm7QAoK1rZ8tvEovm62uqv3GbwQ9G5jgy Message-ID: <7f7c1430-c311-ce7c-1893-ef90963f26e9@protected-networks.net> Date: Fri, 1 Jun 2018 19:42:07 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.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.26 Precedence: 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, 01 Jun 2018 23:42:19 -0000 Building /usr/obj/usr/src/i386.i386/sys/SARAH/vm_mmap.o --- vm_mmap.o --- /usr/src/sys/vm/vm_mmap.c:245:6: error: use of undeclared identifier 'MAP_32BIT' MAP_32BIT | MAP_ALIGNMENT_MASK)) != 0)) ^ 1 error generated. *** [vm_mmap.o] Error code 1 imb From owner-freebsd-current@freebsd.org Fri Jun 1 23:53: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 E649DEFCE9E for ; Fri, 1 Jun 2018 23:53:00 +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 635E37D2F8; Fri, 1 Jun 2018 23:53:00 +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 ESMTP id w51NqnLH066420; Sat, 2 Jun 2018 02:52:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w51NqnLH066420 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w51NqnF0066419; Sat, 2 Jun 2018 02:52:49 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sat, 2 Jun 2018 02:52:49 +0300 From: Konstantin Belousov To: Michael Butler Cc: freebsd-current , alc@freebsd.org Subject: Re: SVN r334499 breaks i386 kernel build Message-ID: <20180601235249.GF3789@kib.kiev.ua> References: <7f7c1430-c311-ce7c-1893-ef90963f26e9@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7f7c1430-c311-ce7c-1893-ef90963f26e9@protected-networks.net> User-Agent: Mutt/1.10.0 (2018-05-17) 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.26 Precedence: 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, 01 Jun 2018 23:53:01 -0000 On Fri, Jun 01, 2018 at 07:42:07PM -0400, Michael Butler wrote: > Building /usr/obj/usr/src/i386.i386/sys/SARAH/vm_mmap.o > --- vm_mmap.o --- > /usr/src/sys/vm/vm_mmap.c:245:6: error: use of undeclared identifier > 'MAP_32BIT' > MAP_32BIT | MAP_ALIGNMENT_MASK)) != 0)) > ^ > 1 error generated. > *** [vm_mmap.o] Error code 1 Should be fixed by r334507. From owner-freebsd-current@freebsd.org Sat Jun 2 00:14: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 27920F71650 for ; Sat, 2 Jun 2018 00:14:11 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: from mail-vk0-x243.google.com (mail-vk0-x243.google.com [IPv6:2607:f8b0:400c:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B286D7E787 for ; Sat, 2 Jun 2018 00:14:10 +0000 (UTC) (envelope-from dsifriend@gmail.com) Received: by mail-vk0-x243.google.com with SMTP id s187-v6so4763571vke.9 for ; Fri, 01 Jun 2018 17:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language; bh=VgSxdU9FWfFLBFRwmxzii5qek5CrF5AQZwvNCY1KyMA=; b=p7hKOQ+Fu1tFojAjHyzloZt/nCJc9dcrhTI2vHjm1pKDENJozMItpYvB7JoMJi1hM2 hBg1aEQ+GKwaISTKxeoVIzoR0KwDlcXmtLEc0tVGYywaywDy0CIw/GgGuWzVvyN3qSbm 4+Fivq0DSF5kBZR5ebRrDVIRwdsNxGkjzk5/lTAFWl4LlfFINXQ+YJ4thUckebWo+0WS z/yUOqA67983DtEWvdIQknO1kzds54DXMcnLtFdhnKKsHMKiuvz9Br0Phm3j6VaRfT+q l1aOLKMcuYvJcLirQAdpPL5MnnTr/uBCXHYQHTNR58SQcdbq81A89SbFCMuHPoLu8RXA BpCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language; bh=VgSxdU9FWfFLBFRwmxzii5qek5CrF5AQZwvNCY1KyMA=; b=pphVibVFPeJgGzE5tZux+H2lIkt/HlcRGHrpU5pcHCW/t/TEC+G5NY6vRwTmhk1jt1 4YP7ZWNxzpE7BcmSsgubPvPegmFO1v1lfdqH0e6BqYkAppZT1gyo+3ZVYW+byt6PxdFO +gP2526lWjDS+xxEi/WKQ5LanN/WHL3Xq1D7sIFDPTuxkPOsnq0GCqYWkWaUCTNIWGD8 iMufDBCPpwQuncheqlWVglXxoAmJjZJgsw/AXiaULxUJwPfCwB2MW4OzgiNE3rPvpHWI Kg6bXGXq+hTVK/BGwFfgSqqHt37i/T+oZnWQYYKupvUbVJE9muw9RckTYaaU1EFZ8FpX Og6A== X-Gm-Message-State: ALKqPwc+PLMBF0vnO9USQsD7a8W0R6gcHY69dX2tsUDCTSd9dT0Jfdn9 ps9d6SXb8MVMLinRJ45rkds= X-Google-Smtp-Source: ADUXVKIlmRSfc/bx7xWIJOX63xBgKyf6WW+OZ5jT5ROHfc5F7FiTpdU06/PBP9+o8b8I4Jx+nqTJMg== X-Received: by 2002:a1f:3195:: with SMTP id x143-v6mr7770671vkx.6.1527898450123; Fri, 01 Jun 2018 17:14:10 -0700 (PDT) Received: from [192.168.1.120] ([24.171.250.32]) by smtp.gmail.com with ESMTPSA id 103-v6sm7384176uav.19.2018.06.01.17.14.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 01 Jun 2018 17:14:09 -0700 (PDT) From: Albert Subject: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing To: freebsd-current@freebsd.org Message-ID: <9af6cfd7-114a-1613-9b65-37090a0f17fe@gmail.com> Date: Fri, 1 Jun 2018 20:14:06 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 00:14:11 -0000 Hi all, I'd like to start out by saying that I'm a newcomer to FreeBSD, but I've been running Linux for years now and I'm still having a few issues transitioning. Despite that. I've been having a blast setting things up for myself, and I'm hopeful I can get this resolved soon enough. I'm trying to get FreeBSD running on my laptop, an "Acer Chromebook 14" (EDGAR), and although I've managed to overcome most of the problems I've faced along the way (needing to upgrade to a UEFI, misnamed wireless modules, video drivers not working on RELEASE nor STABLE), I just can't seem to get the touchpad on this thing to work. For reference, EDGAR is an Intel Celeron N3160 SoC. Pretty much the only thing in it that isn't Intel are the case, the keyboard, the webcam and the touchpad. On Linux, the touchpad appears in _/proc_ as I: Bus=0018 Vendor=04f3 Product=0055 Version=0000 N: Name="Elan Touchpad" P: Phys= S: Sysfs=/devices/pci0000:00/808622C1:05/i2c-1/i2c-ELAN0000:00/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=5 B: EV=b B: KEY=e520 10000 0 0 0 0 B: ABS=663800013000003 It seems _dmesg_ confirms this: [   18.416171] input: Elan Touchpad as /devices/pci0000:00/808622C1:05/i2c-1/i2c-ELAN0000:00/input/input5 and it can be seen from _lsmod_ as *elan_i2c*. The source for the corresponding driver can be found here: Google ChromeOS Git. Now on FreeBSD, it's as though it didn't even exist. Without applying any of the changes I've tried to get it working, here's the (verbose) output to _dmesg_ on FreeBSD: (vdmesg-nochanges ). With the knowledge I have so far, this is to be expected, as it seems FreeBSD requires the *ig4* module to work with *i2c* devices. Loading it at boot does seem to make the buses visible, but the touchpad still doesn't appear (or not properly, I don't know all these codes): (vdmesg-ig4 ). The obvious solution is to enable support for elantech devices with _hw.psm.elantech_support_, but nada: (vdmesg-elantech ). The only difference is _sysctl_ shows that option is enabled. Aside from that, it seems I'm not the only one who's had this sort of issue before, so support has been worked on and is claimed to be working. Loading the recommended cyapa and chromebook_platform modules at boot does not fix this issue: (vdmesg-chromebook ). The reason appears, at least to me, to be that the cyapa driver isn't a proper elan driver. These are /different/ devices. I'm determined to get this working /somehow/, so any help would be appreciated. It feels like there's a solution here somewhere and I'm either too dumb to find it or it's just not there quite yet. If it's the latter, I'm willing to put some work into porting the right driver with a little guidance. (I have plenty of experience with C but none of this driver stuff.) - Albert PS. External mice are working perfectly, so it's nothing to do with the base install. From owner-freebsd-current@freebsd.org Sat Jun 2 05:41:21 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 9CFE8F75B94 for ; Sat, 2 Jun 2018 05:41:21 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc13.plala.or.jp (msc13.plala.or.jp [60.36.166.23]) by mx1.freebsd.org (Postfix) with ESMTP id DE0806D79F for ; Sat, 2 Jun 2018 05:41:20 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc11.plala.or.jp with ESMTP id <20180602053540.FAL5024.msc11.plala.or.jp@localhost> for ; Sat, 2 Jun 2018 14:35:40 +0900 Date: Sat, 02 Jun 2018 14:35:35 +0900 (JST) Message-Id: <20180602.143535.1390554190272814876.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: How to run drm-next-kmod on r334511 From: Masachika ISHIZUKA X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Sat, 2 Jun 2018 14:35:40 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 05:41:21 -0000 Hi. When I updated to r334511, drm-next-kmod is not working with the message '[drm:fw_domain_wait_ack] render: timed out waiting for forcewake ack request.'. drm-next-kmod was working fine on r333704. My CPU is pentium G4560(kaby lake). -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Sat Jun 2 06:56: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 6421DF7FC19 for ; Sat, 2 Jun 2018 06:56:53 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CC121708D8 for ; Sat, 2 Jun 2018 06:56:52 +0000 (UTC) (envelope-from johalun0@gmail.com) Received: by mail-oi0-x22c.google.com with SMTP id c128-v6so15097874oig.11 for ; Fri, 01 Jun 2018 23:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=bhFEP+khlSqIDB2Gx7ttH5tBzCmAhNqw/5pH+hBYggc=; b=NgFqLOJCZNHS7+jGKNdn0jkcrD/EeTMIIGUwJF6+m5n9EX7FYvIPgLLQ53hOZBPwja 5PT2fSdMMkI6tJIxMhbIRJ0+/7VpHBunzvxKXrGGCmWK5sKt7QbhsYzA+Bsy147CQY54 F7bpH+IswUIovazhImAkHTBaiSHK75y5XIW0ae7od5gxaMv93e/J78Id76VoUGGU5snV vZL/iTuEkbOHiq1Qlqf7ptu7qhQwPTJwVH3ktCJPa+exTrHDKM+fo2XwO97iZWgx5EoL oEh9ifENIQbfuK4e0V62hWm7P4l8AJcpr38nd2VeRgGhr361Te8JKvWzgL5Vk64wmk/s TgvQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=bhFEP+khlSqIDB2Gx7ttH5tBzCmAhNqw/5pH+hBYggc=; b=BUHbDl5j/eDzUUWJ69eXdLi/URiPyO43Ywvkyj2n9MYAIsEfzYgNmiads9jiLVryc0 3r0dnOpxOhpj4g8NkBOisalWFA2/VBzusNvJJpkOkSocBQUEY+06PWnAs7HV1UQ5khX9 09pwB7wnipjSrIm401RgBt0DReRjf6XDQzTT28iUvst2AzDB/l6vZp+uUL7be5aX8VOd RtEKX1xrTcMgwiEmpYTFZhgUmK5fBDfl7R+EAYd8Ga9LHpNBfUxQb+3nFQD2Fz+9qJUE afmhsm1o6ACjq9Rd/c7NcN+tGMPU2DLREumK4JFVlbYqkKOJ/HgY+lbQ4Zxy6WSRP0+X Fsgw== X-Gm-Message-State: ALKqPwcOVzaTusv7oDznvt7Mvgp1bXZEL8yEpp/4vRlhjN4iX6FPtRvM 4gUPxb12Z4vVJZMmu6lTCYud++us X-Google-Smtp-Source: ADUXVKLhE+P/ni8NLGjJF9M850x6jboqIwnCDNLkvpYxtPPiVhsAu5Te282gCIkvfVq11cwEXbeSxg== X-Received: by 2002:aca:7541:: with SMTP id q62-v6mr5082464oic.319.1527922611964; Fri, 01 Jun 2018 23:56:51 -0700 (PDT) Received: from jd.gmail.com ([81.174.250.12]) by smtp.gmail.com with ESMTPSA id s26-v6sm20349052otd.16.2018.06.01.23.56.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 01 Jun 2018 23:56:51 -0700 (PDT) References: <20180602.143535.1390554190272814876.ish@amail.plala.or.jp> User-agent: mu4e 1.0; emacs 25.3.1 From: Johannes Lundberg To: Masachika ISHIZUKA Cc: freebsd-current@freebsd.org Subject: Re: How to run drm-next-kmod on r334511 In-reply-to: <20180602.143535.1390554190272814876.ish@amail.plala.or.jp> Date: Sat, 02 Jun 2018 07:56:48 +0100 Message-ID: <864liloevj.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 06:56:53 -0000 Masachika ISHIZUKA writes: > Hi. > > When I updated to r334511, drm-next-kmod is not working with > the message '[drm:fw_domain_wait_ack] render: timed out waiting > for forcewake ack request.'. > > drm-next-kmod was working fine on r333704. > > My CPU is pentium G4560(kaby lake). Hi We are working on a fix now. Sorry for any trouble caused. /Johannes From owner-freebsd-current@freebsd.org Sat Jun 2 07:12: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 33452FC9DBB for ; Sat, 2 Jun 2018 07:12:18 +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 820AF71379 for ; Sat, 2 Jun 2018 07:12:17 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from thor.intern.walstatt.dynvpn.de ([92.229.134.253]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MRGvT-1fsPOo1b3f-00UbCO for ; Sat, 02 Jun 2018 09:12:09 +0200 Date: Sat, 2 Jun 2018 09:11:36 +0200 From: "O. Hartmann" To: FreeBSD CURRENT Subject: rndc: connect failed: 127.0.0.1#953: permission denied Message-ID: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> Organization: WALSTATT User-Agent: OutScare 3.1415926 X-Operating-System: ImNotAnOperatingSystem 3.141592527 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Provags-ID: V03:K1:ZMuL63CGDAubZueuWfor2bINhW0Xfv9k1WDqwq4BfdGkPZE+NJE 1/0KhUWeBAdF9K1CL0X97ZN6UqL6xMtjbv3IAaVKxL7WU1UtvEqloTIcs8sA3wSHAX0ZjgF Cl3vTVVirA9DvwOtNPqZGkSoGWDMIekyYG2Lt83YwoiB+Z6ugo8A10T+UwNSi/zhW/ankHg ESnRSyGhBiare5qqRpAWQ== X-UI-Out-Filterresults: notjunk:1;V01:K0:MQjeqemLric=:/srJ5EZ1xtdMAWC5+R1Ie1 s/32Q6qU6eYwfWUgritdJeYKu0tIJNr7GugdhovvESltbdvlscxaHWgMyZntj9vT1XrC2+FYJ As8kcT/rK60lcUyjZIGMJMazaC95ytFZtOPUA9nJyaJBPn1gurnjmBkC6HdXPBPvITG8yhCuS s6ONVT3xZjdwSl8FSNWm359jDInCGtIzI2PuSIGSXZcTif0Qpbqi2A1JeHZrkVb5u6pHy0wQN 74oDpQNDmN0FLAsn6P4ZcV1TUN3bcfDLhxjfFLK0eDggntBukbbflC3lUe0GjS0mSBgdzRqRQ UWUhjr0KmweMY1odpij0dQxK5lA7JAYpmTaahPqxZP1zH0fD0/tOjjqdOvZiYNCiyUP3pMR1D eE2HHCASJ+wrvoF02lAv4EAcfy4VVgvJCkmK4W1t5FB8zFCeVhnvbzSD/uYRi35U2v2G3ju1c xGzMCifJkZMBtHmu9fuPcq2iQtZUuvpt4tFi2FHB4po0a+bLUSDT5jeww6kXAB0zTbOxOthyb nzYRqHbYxqpnc6MuEyq1tp4XKlqyofRyXok1qBMLy8b1+c1O5ljX+zEC2s8mIDZQWy2p3mB1Q pTQ+bV+iVNTTUAKGCKtphrjZw/iccjcuy/k7zM7pLq3LGU6OjDOzJpQ+vhL+s5dMizDsahvwA MiwYYlkbSJVLSHkpNJOJoO3bgCqWB/lZRPCtdSrK4OEzd17qb7Ngm99UrZt43areDl+49TtrU 6Xpa67ia8LnxaSfQpTKhVY48Hp7+2YPQjP09VOjDOhPe2/48qwC6zZRzuMV59b898TMVJBHdV g/6U8tX X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 07:12:18 -0000 LS0tLS1CRUdJTiBQR1AgU0lHTkVEIE1FU1NBR0UtLS0tLQ0KSGFzaDogU0hBNTEyDQoNCk9uIENV UlJFTlQsIHJ1bm5pbmcgb24gYW4gQVBVIGFzIHJvdXRlci9maXJld2FsbCBzZXJ2aWNlLCBvdXQg b2YgdGhlIGJsdWUgYWZ0ZXIgYW4gdXBkYXRlDQpJIHJlY2VpdmUgdGhpcyB3ZWlyZCBtZXNzYWdl IHdoZW4gdHJ5aW5nIHRvIHJlc3RhcnQgIm5hbWVkIiAoQklORCA5LjEyLCBsYXRlc3QgZnJvbSB0 aGUNCnBvcnRzKToNCg0Kc2VydmljZSBuYW1lZCByZXN0YXJ0DQpybmRjOiBjb25uZWN0IGZhaWxl ZDogMTI3LjAuMC4xIzk1MzoNCnBlcm1pc3Npb24gZGVuaWVkIHJuZGMgZmFpbGVkLCB0cnlpbmcg a2lsbDogV2FpdGluZyBmb3IgUElEUzogODcxLg0KDQpTZWFyY2hpbmcgdGhlIG5ldCByZXZlYWxz IHRoYXQgcG9zc2libGUgYWNjZXNzIHJpZ2h0cyBpc3N1ZXMgY291bGQgY2F1c2UgdGhpcyBwcm9i bGVtLA0KYnV0IEkgZG8gbm90IHNlZSBhbnkuIERvZXMgc29tZWJvZHkgc2VlIHN1Y2ggcHJvYmxl bXMsIHRvbyBhbmQgZG9lcyBoYXZlIGEgc29sdXRpb24/DQoNCktpbmQgcmVnYXJkcywNCg0Kb2gN Cg0KLSAtLSANCk8uIEhhcnRtYW5uDQoNCkljaCB3aWRlcnNwcmVjaGUgZGVyIE51dHp1bmcgb2Rl ciDDnGJlcm1pdHRsdW5nIG1laW5lciBEYXRlbiBmw7xyDQpXZXJiZXp3ZWNrZSBvZGVyIGbDvHIg ZGllIE1hcmt0LSBvZGVyIE1laW51bmdzZm9yc2NodW5nICjCpyAyOCBBYnMuIDQgQkRTRykuDQot LS0tLUJFR0lOIFBHUCBTSUdOQVRVUkUtLS0tLQ0KDQppTFVFQVJNS0FCMFdJUVFaVlpNekF0d0My VC84NlRyUzUyOGZ5RmhZbEFVQ1d4SkRRd0FLQ1JEUzUyOGZ5RmhZDQpsRzk5QWY5ZmdZWFd1MHVY ZlJlcXBNWEJuR3BTaGREelkvamgwWVBTYkFSbnFjRWJDWHRyWk8vMC9KeW9kRitrDQpjRDFjSkw1 UTRCTEJJTTFPcEMwNHZPMUx6dzhOQWY0MGZjWC9GcVhRMUdGOUVLT2gvOGpONDQzeUVzNGNGMk9m DQpwUHhnODlNbEd2QTY3UW44MThHak1wUEt5SlR0cEY5bnVrd3BFRzNibzgrVGUrbUVtVXhaDQo9 T3ZLMg0KLS0tLS1FTkQgUEdQIFNJR05BVFVSRS0tLS0tDQo= From owner-freebsd-current@freebsd.org Sat Jun 2 07:19: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 79F6AFCAE3D; Sat, 2 Jun 2018 07:19:43 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EFCC7717C1; Sat, 2 Jun 2018 07:19:42 +0000 (UTC) (envelope-from maurizio1018@gmail.com) Received: by mail-pg0-x235.google.com with SMTP id p8-v6so12212791pgq.10; Sat, 02 Jun 2018 00:19:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=hGDUHr8KUp+MnR+C1PxoOfxP3jMCfJTeYgMDc6oI5pU=; b=h/noPZNHQuD8ZDsNvHj3cfOnSTXHHD3kMApQbwumq3EmmkwYO6F+Vg+VJ44cYhpsO4 tsWsq0jq2IHOgUsUc5iv9JMvNTlLuv3jzY+Flm6InlM8X3zS6d2OQyHUefcvYgRcUvQG pxRNo64lgIMLwepg8aWukmtp4F0BcsxB/XdbPFkW8CtPkOqKOrSkYenzqpMwkS1tsaIm OdDqrL6r2lVYmRllAhb2T4u4gCb262f56KNKyMMrNOhkUVmS57q6ZLwYPGlUohUDi/o2 gQZ12Ac97hALYbHMm4pMQP+5n5LUCmww5+NNlf7cCQTeD+zeeHOkC0Gno3YkHVZ6iAb2 uFFA== 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; bh=hGDUHr8KUp+MnR+C1PxoOfxP3jMCfJTeYgMDc6oI5pU=; b=BH15HvNbSSc042MUy9Y8YT7990iWjOheO3UocSJHmcNXL/UBE0CbgdQVhxcseYufsQ WlGgbkw0lLWn4CwnepDRfN3dUl4PHa1Xgxta3uSHXM3Ba1VKQscJkQUj2xAuqwGRehzX JXmNDV+nyZsCclWF+iHSQBcbpB5HoDH+jq+ak3SdLuHIPslHA0PP2kUOZosYkbedpHly o0HusYZ21uUujMUG9NeYwaYi+m4V5QiaS/nuuC7CP9ySDAwXAc53N1b1HOPKetRtnRrE J2KTyzuXO5uotE//g//d3YKoUkbj6ZC39sF+ty4eYPKaCNpCmmP5HP57J+fQp4KlKNo8 KO8g== X-Gm-Message-State: ALKqPwf5ocGBB3WlYA0Vn0n/7nHCbBF4vtJ42LHifRCxzC/WCcrSDFQE iinFOP7MMJfXoE3qaq9Hhu4U6CbBJ+xhffiFjto= X-Google-Smtp-Source: ADUXVKJSPJIAQAXAoWK9K/WVHQNn5em8Yw4ddRoIo/p7cRDZWOAYDTNYx9tmU1FkPmDtaO5vn7Z20mFNCeU6vD/7znw= X-Received: by 2002:a65:608c:: with SMTP id t12-v6mr10904872pgu.182.1527923981764; Sat, 02 Jun 2018 00:19:41 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:ad94:0:0:0:0 with HTTP; Sat, 2 Jun 2018 00:19:41 -0700 (PDT) In-Reply-To: <20180530155039.GE97814@FreeBSD.org> References: <20180530155039.GE97814@FreeBSD.org> From: Maurizio Vairani Date: Sat, 2 Jun 2018 09:19:41 +0200 Message-ID: Subject: Re: Call for Testing: 12.0-CURRENT amd64 memstick installer boot-testing wanted To: freebsd-current , freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 07:19:43 -0000 2018-05-30 17:50 GMT+02:00 Glen Barber : > Hi, > > Could folks please help boot-test the most recent 12.0-CURRENT amd64 > memstick images on various hardware? Note, this is not a request to > install 12.0-CURRENT, only a boot-test with various system knobs > tweaked. > > The most recent images are available at: > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-mini-memstick.img > https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO- > IMAGES/12.0/FreeBSD-12.0-CURRENT-amd64-20180529-r334337-memstick.img > > We are interested in testing both UEFI and CSM/BIOS/legacy mode, as we > would like to get this included in the upcoming 11.2-RELEASE if the > change that had been committed addresses several boot issues reported > recently. > > Please help test, and report back (both successes and failures). > > Thanks, > > Glen > > Hi, successfully tested the memstick.img on: HP Microserver Gen8, BIOS Samsung NP270E5E laptop, BIOS and UEFI -- Maurizio From owner-freebsd-current@freebsd.org Sat Jun 2 07:56: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 BAFA0FD4B99 for ; Sat, 2 Jun 2018 07:56:56 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc11.plala.or.jp (msc11.plala.or.jp [60.36.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id DB3467347E for ; Sat, 2 Jun 2018 07:56:55 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc11.plala.or.jp with ESMTP id <20180602075651.GQP5024.msc11.plala.or.jp@localhost> for ; Sat, 2 Jun 2018 16:56:51 +0900 Date: Sat, 02 Jun 2018 16:56:45 +0900 (JST) Message-Id: <20180602.165645.1988449322524261535.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: How to run drm-next-kmod on r334511 From: Masachika ISHIZUKA In-Reply-To: <864liloevj.fsf@gmail.com> References: <20180602.143535.1390554190272814876.ish@amail.plala.or.jp> <864liloevj.fsf@gmail.com> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Sat, 2 Jun 2018 16:56:52 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 07:56:56 -0000 >> When I updated to r334511, drm-next-kmod is not working with >> the message '[drm:fw_domain_wait_ack] render: timed out waiting >> for forcewake ack request.'. >> drm-next-kmod was working fine on r333704. >> My CPU is pentium G4560(kaby lake). > > We are working on a fix now. > Sorry for any trouble caused. Thank you for reply, Johannes Since it works well in 11.2-RC1, it is not in a hurry, but I am looking forward to being fixed. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Sat Jun 2 10:26: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 69AFFF73CD1 for ; Sat, 2 Jun 2018 10:26:17 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [IPv6:2605:2700:0:3:a800:ff:fee9:2feb]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hraggstad.unrelenting.technology", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 05BF2796C2 for ; Sat, 2 Jun 2018 10:26:16 +0000 (UTC) (envelope-from greg@unrelenting.technology) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=unrelenting.technology; h=date:from:subject:to:message-id; s=default; bh=ZeikKmabtsrd6BQ5uilEbGIE5gwvUq64oOo5lcIclw8=; b=lbjyEbQooJsEFukdQI/NKDajayyfTCmtxTRx2adiuUSqMkwAUGUEO+C3TewaX7nS/QRAuHHzB7NTBsJO2wuLma74zRrZEDQd6HHfCw7TyxOg5R/rBs4mCjYjIj5FoQ0GTqRxrRDRBZKALi2RWgueijOF8bSlp9QGRBSK+787Nxg= Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id c8f475c7 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO; Sat, 2 Jun 2018 10:26:09 +0000 (UTC) Date: Sat, 02 Jun 2018 13:26:03 +0300 From: Greg V Subject: Re: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing To: Albert Cc: freebsd-current@freebsd.org Message-Id: <1527935163.4856.0@hraggstad.unrelenting.technology> In-Reply-To: <9af6cfd7-114a-1613-9b65-37090a0f17fe@gmail.com> References: <9af6cfd7-114a-1613-9b65-37090a0f17fe@gmail.com> X-Mailer: geary/0.12.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 10:26:17 -0000 On Sat, Jun 2, 2018 at 3:14 AM, Albert wrote: > Hi all, > > > I'd like to start out by saying that I'm a newcomer to FreeBSD, but > I've been running Linux for years now and I'm still having a few > issues transitioning. Despite that. I've been having a blast setting > things up for myself, and I'm hopeful I can get this resolved soon > enough. > > I'm trying to get FreeBSD running on my laptop, an "Acer Chromebook > 14" (EDGAR), and although I've managed to overcome most of the > problems I've faced along the way (needing to upgrade to a UEFI, > misnamed wireless modules, video drivers not working on RELEASE nor > STABLE), I just can't seem to get the touchpad on this thing to work. > > For reference, EDGAR is an Intel Celeron N3160 SoC. Pretty much the > only thing in it that isn't Intel are the case, the keyboard, the > webcam and the touchpad. On Linux, the touchpad appears in _/proc_ as > [...] > and it can be seen from _lsmod_ as *elan_i2c*. The source for the > corresponding driver can be found here: Google ChromeOS Git. > > > Now on FreeBSD, it's as though it didn't even exist. Without applying > any of the changes I've tried to get it working, here's the (verbose) > output to _dmesg_ on FreeBSD: (vdmesg-nochanges > ). > With the knowledge I have so far, this is to be expected, as it seems > FreeBSD requires the *ig4* module to work with *i2c* devices. Loading > it at boot does seem to make the buses visible, but the touchpad > still doesn't appear (or not properly, I don't know all these codes): > (vdmesg-ig4 > ). > The obvious solution is to enable support for elantech devices with > _hw.psm.elantech_support_, but nada: (vdmesg-elantech > ). > The only difference is _sysctl_ shows that option is enabled. Aside > from that, it seems I'm not the only one who's had this sort of issue > before, so support has been worked on and is claimed to be working. > Loading the recommended cyapa and chromebook_platform modules at boot > does not fix this issue: (vdmesg-chromebook > ). > The reason appears, at least to me, to be that the cyapa driver isn't > a proper elan driver. These are /different/ devices. > > I'm determined to get this working /somehow/, so any help would be > appreciated. It feels like there's a solution here somewhere and I'm > either too dumb to find it or it's just not there quite yet. If it's > the latter, I'm willing to put some work into porting the right > driver with a little guidance. (I have plenty of experience with C > but none of this driver stuff.) Hi! hw.psm.elantech_support is not the solution. hw.psm... psm means PS/2 Mouse. This is for PS/2 Elantech touchpads. cyapa is indeed not the right driver either. The "cy" is for Cypress. That's the touchpad found in e.g. the Acer C720. So there's no support for your touchpad right now. OpenBSD has HID over i2c support: https://man.openbsd.org/imt -- you could try porting that... Also, should be possible to add i2c support to webcamd I guess, that would get the Linux driver running in userspace. From owner-freebsd-current@freebsd.org Sat Jun 2 11:40: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 020F5F7E3E0; Sat, 2 Jun 2018 11:40:29 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.92]) (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 901837D05A; Sat, 2 Jun 2018 11:40:28 +0000 (UTC) (envelope-from ronald-lists@klop.ws) Received: from smtp.greenhost.nl ([213.108.110.112]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1fP4tW-0007nu-AK; Sat, 02 Jun 2018 13:40:26 +0200 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: "bob prohaska" Cc: freebsd-arm@freebsd.org, "FreeBSD Current" Subject: Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 References: <20180601154153.GA62632@www.zefox.net> Date: Sat, 02 Jun 2018 13:40:27 +0200 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20180601154153.GA62632@www.zefox.net> User-Agent: Opera Mail/12.16 (FreeBSD) X-Authenticated-As-Hash: 398f5522cb258ce43cb679602f8cfe8b62a256d1 X-Virus-Scanned: by clamav at smarthost1.samage.net X-Spam-Level: / X-Spam-Score: -0.2 X-Spam-Status: No, score=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 autolearn=disabled version=3.4.0 X-Scan-Signature: 897836312160ed0141c32cdc6ac56212 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 11:40:29 -0000 This happened again. Now I have a crashdump. Anyone interested? Some more answers below. On Fri, 01 Jun 2018 17:41:54 +0200, bob prohaska wrote: > On Thu, May 31, 2018 at 05:53:12PM +0200, Ronald Klop wrote: >> I had a crash on my RPI-3B+ running freebsd 12/aarch64 from the 29 may >> snapshot. >> It was building world -j4 and portsnap extract. >> >> I will keep it in the debugger for about an hour so if I need to provide >> more information, please mail me. >> >> >> db> show panic >> panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at >> /usr/src/sys/kern/sched_ule.c:2137 >> > This used to be a fairly common error on my RPI3, but I haven't seen > it in some time. > > As a matter of curiosity, have you been able to run a -j4 buildworld > to completion on your RPI3? If so, please post your setup. For several > months now all my attempts at j4 buildworld have failed with "killed, > out of swap" even though top seems to report minimal swap usage. It > even happens with no -j value set at all, but usually restarting with > -DNO_CLEAN allowed progress to pick up where it left off. > > Alas, as I write this, the kernel just reported > > Jun 1 08:34:34 www kernel: pid 19399 (c++), uid 0, was killed: out of > swap space > > top is showing > Swap: 4096M Total, 17M Used, 4079M Free > but since top is alive the value is stale. Nonetheless, I have seen top > killed while still showing minimal swap usage. > > It seems as if the "out of swap" kills are being issued in error.. > > Thanks for reading, > > bob prohaska > I just received my RPI3 this week. It is running GENERIC with debug options still. Building a -NODEBUG kernel from src didn't succeed yet because of the mentioned panic. I'm now building with -j2 to be on the safe side. After I have the -NODEBUG kernel it will be a bit faster and I will try -j4 again. Regards, Ronald. From owner-freebsd-current@freebsd.org Sat Jun 2 11:59: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 5B534FC8AF0 for ; Sat, 2 Jun 2018 11:59:34 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from ms-10.1blu.de (mail.dpedia.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 E9A9F7DCC9 for ; Sat, 2 Jun 2018 11:59:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from [89.14.243.85] (helo=[192.168.179.55]) by ms-10.1blu.de with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.86_2) (envelope-from ) id 1fP3yy-0004OL-RQ for freebsd-current@freebsd.org; Sat, 02 Jun 2018 12:42:00 +0200 From: Matthias Apitz To: Subject: Re: Elantech Touchpad Woes - Support for Elantech touchpads over =?iso-8859-1?Q?i2c/SMBus_still_possibly_missing?= Date: Sat, 02 Jun 2018 12:41:59 +0200 User-Agent: Dekko/0.6.20; Qt/5.4.1; ubuntumirclient; Linux; MIME-Version: 1.0 Message-ID: <239e12c8-735a-4b3c-afd5-7399c73dd3be@unixarea.de> In-Reply-To: <1527935163.4856.0@hraggstad.unrelenting.technology> References: <9af6cfd7-114a-1613-9b65-37090a0f17fe@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Con-Id: 51246 X-Con-U: 0-guru X-Originating-IP: 89.14.243.85 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 11:59:34 -0000 On Saturday, 2 June 2018 12:26:03 CEST, Greg V=20 wrote: >=20 > ... > cyapa is indeed not the right driver either. The "cy" is for Cypress.=20 > That's the touchpad found in e.g. the Acer C720. >=20 > ... Side note: I own three C720, they all came with Cypress TP. One was for repair at=20 Acer.com and returned with an Elantech TP. As well, there are no spare=20 parts of Cypress any more for replacement, even if the dealer claimes so,=20 they came all as Elan and I returned them. Said this, we need support for Elan in our beloved FreeBSD. Matthias. --=20 Sent from my Ubuntu phone http://www.unixarea.de/ From owner-freebsd-current@freebsd.org Sat Jun 2 12:19: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 E7EC6FD0BCC for ; Sat, 2 Jun 2018 12:19:10 +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 39A6C7EBC2 for ; Sat, 2 Jun 2018 12:19:09 +0000 (UTC) (envelope-from freebsd@grem.de) Received: (qmail 65608 invoked by uid 89); 2 Jun 2018 12:12:27 -0000 Received: from unknown (HELO ?100.67.141.236?) (mg@grem.de@109.41.193.204) by mail.grem.de with ESMTPA; 2 Jun 2018 12:12:27 -0000 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: Elantech Touchpad Woes - Support for Elantech touchpads over i2c/SMBus still possibly missing From: Michael Gmelin X-Mailer: iPhone Mail (15E302) In-Reply-To: <239e12c8-735a-4b3c-afd5-7399c73dd3be@unixarea.de> Date: Sat, 2 Jun 2018 14:12:26 +0200 Cc: freebsd-current@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <0E69C450-42AE-438A-8C33-54B8E4B561F5@grem.de> References: <9af6cfd7-114a-1613-9b65-37090a0f17fe@gmail.com> <239e12c8-735a-4b3c-afd5-7399c73dd3be@unixarea.de> To: Matthias Apitz X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 12:19:11 -0000 > On 2. Jun 2018, at 12:41, Matthias Apitz wrote: >=20 >> On Saturday, 2 June 2018 12:26:03 CEST, Greg V wrote: >> ... >> cyapa is indeed not the right driver either. The "cy" is for Cypress. Tha= t's the touchpad found in e.g. the Acer C720. >> ... >=20 > Side note: >=20 > I own three C720, they all came with Cypress TP. One was for repair at Ace= r.com and returned with an Elantech TP. As well, there are no spare parts of= Cypress any more for replacement, even if the dealer claimes so, they came a= ll as Elan and I returned them. Yeah, I ported the cyapa driver to FreeBSD, but then I gave my working cyapa= pad to Matthias, trading it for an elan pad. I hoped to port this driver as= well - unfortunately I didn=E2=80=99t find the time yet, but good to know t= hat there is demand. -m >=20 > Said this, we need support for Elan in our beloved FreeBSD. >=20 > Matthias. >=20 >=20 > --=20 > Sent from my Ubuntu phone > http://www.unixarea.de/ > _______________________________________________ > 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 Sat Jun 2 13:07: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 E656EFDB7CE for ; Sat, 2 Jun 2018 13:07:43 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 8689980A6D for ; Sat, 2 Jun 2018 13:07:43 +0000 (UTC) (envelope-from zeising@freebsd.org) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40yhLw5RmvzDhGj; Sat, 2 Jun 2018 13:07:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id 8XhtEPVP4UYj; Sat, 2 Jun 2018 13:07:36 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40yhLv64Szz62Tw; Sat, 2 Jun 2018 13:07:35 +0000 (UTC) Subject: Re: How to run drm-next-kmod on r334511 To: Masachika ISHIZUKA , freebsd-current@freebsd.org References: <20180602.143535.1390554190272814876.ish@amail.plala.or.jp> <864liloevj.fsf@gmail.com> <20180602.165645.1988449322524261535.ish@amail.plala.or.jp> From: Niclas Zeising Message-ID: <4a38309c-e478-b977-c7d2-612829c8264c@freebsd.org> Date: Sat, 2 Jun 2018 15:07:26 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20180602.165645.1988449322524261535.ish@amail.plala.or.jp> 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.26 Precedence: 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, 02 Jun 2018 13:07:44 -0000 On 06/02/18 09:56, Masachika ISHIZUKA wrote: >>> When I updated to r334511, drm-next-kmod is not working with >>> the message '[drm:fw_domain_wait_ack] render: timed out waiting >>> for forcewake ack request.'. >>> drm-next-kmod was working fine on r333704. >>> My CPU is pentium G4560(kaby lake). >> >> We are working on a fix now. >> Sorry for any trouble caused. > > Thank you for reply, Johannes > > Since it works well in 11.2-RC1, it is not in a hurry, but I am > looking forward to being fixed. > This should be fixed as of ports r471368. https://svnweb.freebsd.org/ports?view=revision&revision=471368 Regards -- Niclas From owner-freebsd-current@freebsd.org Sat Jun 2 13:34: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 4D2DFFDEC0C for ; Sat, 2 Jun 2018 13:34:54 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from msc11.plala.or.jp (msc11.plala.or.jp [60.36.166.21]) by mx1.freebsd.org (Postfix) with ESMTP id 595BF81C0E for ; Sat, 2 Jun 2018 13:34:52 +0000 (UTC) (envelope-from ish@amail.plala.or.jp) Received: from localhost ([2400:4050:9320:7a00::8]) by msc11.plala.or.jp with ESMTP id <20180602133450.NRK5024.msc11.plala.or.jp@localhost> for ; Sat, 2 Jun 2018 22:34:50 +0900 Date: Sat, 02 Jun 2018 22:34:44 +0900 (JST) Message-Id: <20180602.223444.506024668248590838.ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: How to run drm-next-kmod on r334511 From: Masachika ISHIZUKA In-Reply-To: <4a38309c-e478-b977-c7d2-612829c8264c@freebsd.org> References: <864liloevj.fsf@gmail.com> <20180602.165645.1988449322524261535.ish@amail.plala.or.jp> <4a38309c-e478-b977-c7d2-612829c8264c@freebsd.org> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-VirusScan: Outbound; mvir-ac11; Sat, 2 Jun 2018 22:34:50 +0900 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 13:34:54 -0000 >>>> When I updated to r334511, drm-next-kmod is not working with >>>> the message '[drm:fw_domain_wait_ack] render: timed out waiting >>>> for forcewake ack request.'. >>>> drm-next-kmod was working fine on r333704. >>>> My CPU is pentium G4560(kaby lake). >>> >>> We are working on a fix now. >>> Sorry for any trouble caused. >> Thank you for reply, Johannes >> Since it works well in 11.2-RC1, it is not in a hurry, but I am >> looking forward to being fixed. > > This should be fixed as of ports r471368. > https://svnweb.freebsd.org/ports?view=revision&revision=471368 Thank you, Niclas. Now, drm-next-kmod works again on r334511. -- Masachika ISHIZUKA From owner-freebsd-current@freebsd.org Sat Jun 2 13:43: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 CC5DCFDFC05 for ; Sat, 2 Jun 2018 13:43:19 +0000 (UTC) (envelope-from vladimir@kondratyev.su) Received: from corp.infotel.ru (corp.infotel.ru [195.170.219.3]) by mx1.freebsd.org (Postfix) with ESMTP id 5990182261 for ; Sat, 2 Jun 2018 13:43:18 +0000 (UTC) (envelope-from vladimir@kondratyev.su) Received: from corp (corp.infotel.ru [195.170.219.3]) by corp.infotel.ru (Postfix) with ESMTP id 9C0FA20B1C for ; Sat, 2 Jun 2018 16:34:02 +0300 (MSK) X-Virus-Scanned: amavisd-new at corp.infotel.ru Received: from corp.infotel.ru ([195.170.219.3]) by corp (corp.infotel.ru [195.170.219.3]) (amavisd-new, port 10024) with ESMTP id ofnMChjO7eZr for ; Sat, 2 Jun 2018 16:33:56 +0300 (MSK) Received: from mail.cicgroup.ru (unknown [195.170.219.74]) by corp.infotel.ru (Postfix) with ESMTP id E398C20B15 for ; Sat, 2 Jun 2018 16:33:56 +0300 (MSK) Received: from mail.cicgroup.ru (localhost [127.0.0.1]) by mail.cicgroup.ru (Postfix) with ESMTP id 5221E422129 for ; Sat, 2 Jun 2018 16:33:48 +0300 (MSK) X-Virus-Scanned: amavisd-new at cicgroup.ru Received: from mail.cicgroup.ru ([127.0.0.1]) by mail.cicgroup.ru (mail.cicgroup.ru [127.0.0.1]) (amavisd-new, port 10024) with SMTP id uTfI0bmKXzuY for ; Sat, 2 Jun 2018 16:33:41 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by mail.cicgroup.ru (Postfix) with ESMTPA id 98608422128 for ; Sat, 2 Jun 2018 16:33:41 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 02 Jun 2018 16:33:41 +0300 From: Vladimir Kondratyev To: freebsd-current@freebsd.org Subject: Proper way to remove never used ioctls Message-ID: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> X-Sender: vladimir@kondratyev.su User-Agent: Roundcube Webmail/1.3.5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 13:43:20 -0000 Hi, Our sys/mouse.h header has a definition of MOUSE_GETVARS and MOUSE_SETVARS ioctls which are not documented and only stubbed in a few drivers: mse(4), psm(4) and syscon's sysmouse(4). The only exception is MOUSE_GETVARS implemented in psm(4) Given the fact that they were introduced 20 years ago, implementation was never completed and googling on them shows no traces of usage in indexed universe, is it acceptable to just drop both defines and implementation w.o. leaving any COMPAT_FREEBSD shims? -- WBR Vladimir Kondratyev From owner-freebsd-current@freebsd.org Sat Jun 2 15:03: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 BECF0F71D77 for ; Sat, 2 Jun 2018 15:03:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5A49786129 for ; Sat, 2 Jun 2018 15:03:06 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22f.google.com with SMTP id l19-v6so23292087ioj.5 for ; Sat, 02 Jun 2018 08:03:06 -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=LnzmrS2Epis3BttWXMJXAxw5DlhEU7mrzjLmy+8tAUc=; b=CRhG+B7jGIaLOahlFU04ENmloZm0PjCT2Tz5eEtBATNJQ/vQMEL9Dh4l85ZFl+NICz +lH7lpsxqm8dyK9W5yhA830j7yCKKuB8eYwJjZaIrK3tqhUTC8Nzmofk5lvLyH3VFCfz s1bZPMyWQXMT4bDEcYTC84MTcFInH4EefwNneo5nbRGopjokkXTWDLzKmAzyK2FZ3nH1 sKWIuDmo+uSCryV8rPIABcSjt9CWE/iSCcOvu4iLDWKbf9t69DXYtpLGzC+1u5SokG// ycvx+WZCmHOK99XV127+sphBvpIskHlDO4XSOFOCphdMxo2MZVGJovGmBog+FBkG84Ne k70Q== 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=LnzmrS2Epis3BttWXMJXAxw5DlhEU7mrzjLmy+8tAUc=; b=gy28dFzAo9U/MojPEWGQ/DNqZ2b8dLlLcbTqg1mtynqbumvcQDN+volvQnvpYyxD6T vyrApzQpM7Tp7xOgmEUmukbfMGhhlrhpZ2UrRr01zSmYT0rUnhkrC5ob86qAUy+6cJV/ 6Rmf7ZAwK3SrvXxhF/PgAZn1g0UCLotFb54tGN75AvObwkiH4ptLrk7cRC7eriF79RhI vIiFrPXWCnHQxsMRhTmSyOUpKfTkBwi+CIL2gxlI8fZD5pLjf2smZAwqUV5SZFpZEglv Br8i0TpANh6sWld6qJElagM8rFNxKH7UVqt55laVByLU23sLEsqIxw4rPp4y0TdadTRH oBdw== X-Gm-Message-State: ALKqPweZOFUphXBt2rLef8Quwwbc2gjNmDeLnYKJCm1e3kxMiU0yiZBN fxAyEmMYarG4r3iednBMxFLMnO0/sJJgNVy/iva6KBqq X-Google-Smtp-Source: ADUXVKLaSlrnEj4h40Mxca7AKfPfkqSvvphgN9H8KnBSH+saYY3gmyAUEQbBtdRlHLtWvz2dxUQdyKYeSwnAkLlRdBA= X-Received: by 2002:a6b:be01:: with SMTP id o1-v6mr14458385iof.299.1527951785378; Sat, 02 Jun 2018 08:03:05 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:d028:0:0:0:0:0 with HTTP; Sat, 2 Jun 2018 08:03:04 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> References: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> From: Warner Losh Date: Sat, 2 Jun 2018 09:03:04 -0600 X-Google-Sender-Auth: -9VeQOVNkaRt-pWBf2ddMjmk-Qs Message-ID: Subject: Re: Proper way to remove never used ioctls To: Vladimir Kondratyev Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 15:03:07 -0000 On Sat, Jun 2, 2018 at 7:33 AM, Vladimir Kondratyev wrote: > Hi, > > Our sys/mouse.h header has a definition of MOUSE_GETVARS and MOUSE_SETVARS > ioctls which are not documented and only stubbed in a few drivers: mse(4), > psm(4) and syscon's sysmouse(4). The only exception is MOUSE_GETVARS > implemented in psm(4) > > Given the fact that they were introduced 20 years ago, implementation was > never completed and googling on them shows no traces of usage in indexed > universe, is it acceptable to just drop both defines and implementation > w.o. leaving any COMPAT_FREEBSD shims? I'd prepare a patch just removing them. I'd then send that patch to the ports mgr team and request a exp-run. Details for that can be found in https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html Once that's done, submit a Phabricator review and send me email. I'll make sure it gets pushed in if there's no objections. Warner From owner-freebsd-current@freebsd.org Sat Jun 2 17:36: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 4E324FD5D20 for ; Sat, 2 Jun 2018 17:36:50 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) (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 DF1296E535 for ; Sat, 2 Jun 2018 17:36:49 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 6FA381F72A for ; Sat, 2 Jun 2018 17:36:49 +0000 (UTC) Subject: Re: Proper way to remove never used ioctls To: freebsd-current@freebsd.org References: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> From: Allan Jude Openpgp: preference=signencrypt Autocrypt: addr=allanjude@freebsd.org; prefer-encrypt=mutual; keydata= xsFNBFVwZcYBEADwrZDH0xe0ZVjc9ORCc6PcBLwS/RTXA6NkvpD6ea02pZ8lPOVgteuuugFc D34LdDbiWr+479vfrKBh+Y38GL0oZ0/13j10tIlDMHSa5BU0y6ACtnhupFvVlQ57+XaJAb/q 7qkfSiuxVwQ3FY3PL3cl1RrIP5eGHLA9hu4eVbu+FOX/q/XVKz49HaeIaxzo2Q54572VzIo6 C28McX9m65UL5fXMUGJDDLCItLmehZlHsQQ+uBxvODLFpVV2lUgDR/0rDa0B9zHZX8jY8qQ7 ZdCSy7CwClXI054CkXZCaBzgxYh/CotdI8ezmaw7NLs5vWNTxaDEFXaFMQtMVhvqQBpHkfOD 7rjjOmFw00nJL4FuPE5Yut0CPyx8vLjVmNJSt/Y8WxxmhutsqJYFgYfWl/vaWkrFLur/Zcmz IklwLw35HLsCZytCN5A3rGKdRbQjD6QPXOTJu0JPrJF6t2xFkWAT7oxnSV0ELhl2g+JfMMz2 Z1PDmS3NRnyEdqEm7NoRGXJJ7bgxDbN+9SXTyOletqGNXj/bSrBvhvZ0RQrzdHAPwQUfVSU2 qBhQEi2apSZstgVNMan0GUPqCdbE2zpysg+zT7Yhvf9EUQbzPL4LpdK1llT9fZbrdMzEXvEF oSvwJFdV3sqKmZc7b+E3PuxK6GTsKqaukd/3Cj8aLHG1T1im1QARAQABzSJBbGxhbiBKdWRl IDxhbGxhbmp1ZGVAZnJlZWJzZC5vcmc+wsF/BBMBAgApBQJVcGXGAhsjBQkSzAMABwsJCAcD AgEGFQgCCQoLBBYCAwECHgECF4AACgkQGZU1PhKYC34Muw/+JOKpSfhhysWFYiRXynGRDe07 Z6pVsn7DzrPUMRNZfHu8Uujmmy3p2nx9FelIY9yjd2UKHhug+whM54MiIFs90eCRVa4XEsPR 4FFAm0DAWrrb7qhZFcE/GhHdRWpZ341WAElWf6Puj2devtRjfYbikvj5+1V1QmDbju7cEw5D mEET44pTuD2VMRJpu2yZZzkM0i+wKFuPxlhqreufA1VNkZXI/rIfkYWK+nkXd9Efw3YdCyCQ zUgTUCb88ttSqcyhik/li1CDbXBpkzDCKI6I/8fAb7jjOC9LAtrZJrdgONywcVFoyK9ZN7EN AVA+xvYCmuYhR/3zHWH1g4hAm1v1+gIsufhajhfo8/wY1SetlzPaYkSkVQLqD8T6zZyhf+AN bC7ci44UsiKGAplB3phAXrtSPUEqM86kbnHg3fSx37kWKUiYNOnx4AC2VXvEiKsOBlpyt3dw WQbOtOYM+vkfbBwDtoGOOPYAKxc4LOIt9r+J8aD+gTooi9Eo5tvphATf9WkCpl9+aaGbSixB tUpvQMRnSMqTqq4Z7DeiG6VMRQIjsXDSLJEUqcfhnLFo0Ko/RiaHd5xyAQ4DhQ9QpkyQjjNf /3f/dYG7JAtoD30txaQ5V8uHrz210/77DRRX+HJjEj6xCxWUGvQgvEZf5XXyxeePvqZ+zQyT DX61bYw6w6bOwU0EVXBlxgEQAMy7YVnCCLN4oAOBVLZ5nUbVPvpUhsdA94/0/P+uqCIh28Cz ar56OCX0X19N/nAWecxL4H32zFbIRyDB2V/MEh4p9Qvyu/j4i1r3Ex5GhOT2hnit43Ng46z5 29Es4TijrHJP4/l/rB2VOqMKBS7Cq8zk1cWqaI9XZ59imxDNjtLLPPM+zQ1yE3OAMb475QwN UgWxTMw8rkA7CEaqeIn4sqpTSD5C7kT1Bh26+rbgJDZ77D6Uv1LaCZZOaW52okW3bFbdozV8 yM2u+xz2Qs8bHz67p+s+BlygryiOyYytpkiK6Iy4N7FTolyj5EIwCuqzfk0SaRHeOKX2ZRjC qatkgoD/t13PNT38V9tw3qZVOJDS0W6WM8VSg+F+bkM9LgJ8CmKV+Hj0k3pfGfYPOZJ/v18i +SmZmL/Uw2RghnwDWGAsPCKu4uZR777iw7n9Io6Vfxndw2dcS0e9klvFYoaGS6H2F13Asygr WBzFNGFQscN4mUW+ZYBzpTOcHkdT7w8WS55BmXYLna+dYer9/HaAuUrONjujukN4SPS1fMJ2 /CS/idAUKyyVVX5vozoNK2JVC1h1zUAVsdnmhEzNPsvBoqcVNfyqBFROEVLIPwq+lQMGNVjH ekLTKRWf59MEhUC2ztjSKkGmwdg73d6xSXMuq45EgIJV2wPvOgWQonoHH/kxABEBAAHCwWUE GAECAA8FAlVwZcYCGwwFCRLMAwAACgkQGZU1PhKYC34w5A//YViBtZyDV5O+SJT9FFO3lb9x Zdxf0trA3ooCt7gdBkdnBM6T5EmjgVZ3KYYyFfwXZVkteuCCycMF/zVw5eE9FL1+zz9gg663 nY9q2F77TZTKXVWOLlOV2bY+xaK94U4ytogOGhh9b4UnQ/Ct3+6aviCF78Go608BXbmF/GVT 7uhddemk7ItxM1gE5Hscx3saxGKlayaOsdPKeGTVJCDEtHDuOc7/+jGh5Zxpk/Hpi+DUt1ot 8e6hPYLIQa4uVx4f1xxxV858PQ7QysSLr9pTV7FAQ18JclCaMc7JWIa3homZQL/MNKOfST0S 2e+msuRwQo7AnnfFKBUtb02KwpA4GhWryhkjUh/kbVc1wmGxaU3DgXYQ5GV5+Zf4kk/wqr/7 KG0dkTz6NLCVLyDlmAzuFhf66DJ3zzz4yIo3pbDYi3HB/BwJXVSKB3Ko0oUo+6/qMrOIS02L s++QE/z7K12CCcs7WwOjfCYHK7VtE0Sr/PfybBdTbuDncOuAyAIeIKxdI2nmQHzl035hhvQX s4CSghsP319jAOQiIolCeSbTMD4QWMK8RL/Pe1FI1jC3Nw9s+jq8Dudtbcj2UwAP/STUEbJ9 5rznzuuhPjE0e++EU/RpWmcaIMK/z1zZDMN+ce2v1qzgV936ZhJ3iaVzyqbEE81gDxg3P+IM kiYh4ZtPB4Q= Message-ID: Date: Sat, 2 Jun 2018 13:36:49 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="SduJM6ALE2xb4qIQyBnyMJ5byptvH4Enk" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 17:36:50 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SduJM6ALE2xb4qIQyBnyMJ5byptvH4Enk Content-Type: multipart/mixed; boundary="X95spYZdoIBGAr6EMZBRnjXOSCVoVHvnt"; protected-headers="v1" From: Allan Jude To: freebsd-current@freebsd.org Message-ID: Subject: Re: Proper way to remove never used ioctls References: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> In-Reply-To: --X95spYZdoIBGAr6EMZBRnjXOSCVoVHvnt Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2018-06-02 11:03, Warner Losh wrote: > On Sat, Jun 2, 2018 at 7:33 AM, Vladimir Kondratyev > wrote: >=20 >> Hi, >> >> Our sys/mouse.h header has a definition of MOUSE_GETVARS and MOUSE_SET= VARS >> ioctls which are not documented and only stubbed in a few drivers: mse= (4), >> psm(4) and syscon's sysmouse(4). The only exception is MOUSE_GETVARS >> implemented in psm(4) >> >> Given the fact that they were introduced 20 years ago, implementation = was >> never completed and googling on them shows no traces of usage in index= ed >> universe, is it acceptable to just drop both defines and implementatio= n >> w.o. leaving any COMPAT_FREEBSD shims? >=20 >=20 > I'd prepare a patch just removing them. I'd then send that patch to the= > ports mgr team and request a exp-run. Details for that can be found in > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/p= orts.html >=20 > Once that's done, submit a Phabricator review and send me email. I'll m= ake > sure it gets pushed in if there's no objections. >=20 > Warner > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" >=20 This indeed seems to be the correct approach. The exp-run will compile the entire ports tree against the patched base system, and identify any 3rd party software that fails to compile because of the change. --=20 Allan Jude --X95spYZdoIBGAr6EMZBRnjXOSCVoVHvnt-- --SduJM6ALE2xb4qIQyBnyMJ5byptvH4Enk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJbEtWxAAoJEBmVNT4SmAt+GRMP/RzO/9F87F6incGpd1y1nun1 20HPznyAq1ARJMjPdkQqL7A/CwP07nmo4BqS3p8bw+oTkTA/el/ifArxz2Cjj4LA Q/4I25uInBpm3sh+IIAcX3nAmwvrE6yoG+WK5aycEqz87TRQDatR7FdJ+jWRj2Ht oiJhK2I2wY5yYN/YUwERcNBp3qonfzOnGATJ2gecO56kNiVWommi4P6PpVg83OpA dmc2/e9LWirXK/ZRLHQnkfYl0M+NY7eGdK+etW1WAk50T4+qM1h6PtkqYkVskLz9 zELH1miEfpylvVynVVw94U7IGWwdjNAS8EvGGcD8k0JsXpTXOC4iAfVhYXL859+W MvZMRpRe1T7v2HxxkRjoBiFjnWy4oKJ6Nxe5UZNjqOzjKhQckK8f20KAQe5P9fjQ JbeRn0Hwl9BJrFxfQ5KfQ1ow0bJRR/3G5ckqUU8ibrrYeZZM369NQoJ9cMitNon5 KXKL5jnIch5+XaKcC+haofWsBzgefVYSljrysIKvREc5eSsg6KaZTRuJLKz6+/RM N7gFTSd4yymGfjRiqDR4YbTH65DMHcR8BBM0mgroHLhhrApemt9H/cxdzP+II/ty N1N79jUUdSjowsNxSN2LJ4JlcDh0R8QMLaMwRIeK6zdi0TDFZD3HjOjq5DLcg30G mkfTLOoWIhMt1LyillAJ =WGNY -----END PGP SIGNATURE----- --SduJM6ALE2xb4qIQyBnyMJ5byptvH4Enk-- From owner-freebsd-current@freebsd.org Sat Jun 2 18:30: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 4C0E9FD0277; Sat, 2 Jun 2018 18:30:42 +0000 (UTC) (envelope-from vladimir@kondratyev.su) Received: from corp.infotel.ru (corp.infotel.ru [195.170.219.3]) by mx1.freebsd.org (Postfix) with ESMTP id D544170EDA; Sat, 2 Jun 2018 18:30:41 +0000 (UTC) (envelope-from vladimir@kondratyev.su) Received: from corp (corp.infotel.ru [195.170.219.3]) by corp.infotel.ru (Postfix) with ESMTP id 1E66E20490; Sat, 2 Jun 2018 21:30:36 +0300 (MSK) X-Virus-Scanned: amavisd-new at corp.infotel.ru Received: from corp.infotel.ru ([195.170.219.3]) by corp (corp.infotel.ru [195.170.219.3]) (amavisd-new, port 10024) with ESMTP id 16D-rOIu57KM; Sat, 2 Jun 2018 21:30:21 +0300 (MSK) Received: from mail.cicgroup.ru (unknown [195.170.219.74]) by corp.infotel.ru (Postfix) with ESMTP id 3F42920484; Sat, 2 Jun 2018 21:30:21 +0300 (MSK) Received: from mail.cicgroup.ru (localhost [127.0.0.1]) by mail.cicgroup.ru (Postfix) with ESMTP id 7733E422129; Sat, 2 Jun 2018 21:30:17 +0300 (MSK) X-Virus-Scanned: amavisd-new at cicgroup.ru Received: from mail.cicgroup.ru ([127.0.0.1]) by mail.cicgroup.ru (mail.cicgroup.ru [127.0.0.1]) (amavisd-new, port 10024) with SMTP id hCOmoX2Hapx3; Sat, 2 Jun 2018 21:30:10 +0300 (MSK) Received: from localhost (localhost [127.0.0.1]) by mail.cicgroup.ru (Postfix) with ESMTPA id 1D0A9422128; Sat, 2 Jun 2018 21:30:10 +0300 (MSK) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 02 Jun 2018 21:30:09 +0300 From: Vladimir Kondratyev To: Allan Jude Cc: freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Subject: Re: Proper way to remove never used ioctls In-Reply-To: References: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> Message-ID: <8f0bd4c0195ecaf1038268831576c461@kondratyev.su> X-Sender: vladimir@kondratyev.su User-Agent: Roundcube Webmail/1.3.5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 18:30:42 -0000 On 2018-06-02 20:36, Allan Jude wrote: > On 2018-06-02 11:03, Warner Losh wrote: >> On Sat, Jun 2, 2018 at 7:33 AM, Vladimir Kondratyev >> >> wrote: >> >>> Hi, >>> >>> Our sys/mouse.h header has a definition of MOUSE_GETVARS and >>> MOUSE_SETVARS >>> ioctls which are not documented and only stubbed in a few drivers: >>> mse(4), >>> psm(4) and syscon's sysmouse(4). The only exception is MOUSE_GETVARS >>> implemented in psm(4) >>> >>> Given the fact that they were introduced 20 years ago, implementation >>> was >>> never completed and googling on them shows no traces of usage in >>> indexed >>> universe, is it acceptable to just drop both defines and >>> implementation >>> w.o. leaving any COMPAT_FREEBSD shims? >> >> >> I'd prepare a patch just removing them. I'd then send that patch to >> the >> ports mgr team and request a exp-run. Details for that can be found in >> https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html >> >> Once that's done, submit a Phabricator review and send me email. I'll >> make >> sure it gets pushed in if there's no objections. >> >> Warner > > This indeed seems to be the correct approach. The exp-run will compile > the entire ports tree against the patched base system, and identify any > 3rd party software that fails to compile because of the change. Thank you, Allan and Warner! I'll follow yours advice. -- WBR Vladimir Kondratyev From owner-freebsd-current@freebsd.org Sat Jun 2 22:52: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 3505CFF33C4; Sat, 2 Jun 2018 22:52:40 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4C147F187; Sat, 2 Jun 2018 22:52:39 +0000 (UTC) (envelope-from gurenchan@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id 144-v6so5873753iti.5; Sat, 02 Jun 2018 15:52:39 -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=8HpuRO4JDSUxMm29QiRwBMkJKD4vfCpUdq2NHISlFAs=; b=BB8HnF10CBknWWv1XaWzIYY8iEpXZulKV2po7OWoY+bikQBxlolCxqAcZobcsSMkD+ se0T0i5z0nXuwEao9JSYLnmf4ooPlgJbkmHJPhWc8HhEpMZuuUOx6lqLb4ywMFT1JX1n woy2FvJD48jEjXkUteXtoEYIunP87SclB0Xz+HQ4VD/nUujOpy5MrYqY7G+UMp9mmsbj BXH/JHk/I8yprKfEQg9MjWBo9l+Dfq0wxaHl+CVr2jGIBn9WbaN4r14Z9epXLAbkIbeh GuWdWuhScdtZm4coFaXitvItsDk5fuy0J1nS01DHzrpmM2W8iFyU4zSWgxzuqB1+p2lP K74w== 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=8HpuRO4JDSUxMm29QiRwBMkJKD4vfCpUdq2NHISlFAs=; b=d5FivDClM0XtnAbhkLhQHAoxtPBI3Top6lqEtr65FO3Ihcx6B38tk4G70OM+dATXFf DjP90m4C8t11ryM7+K5KFckgtPfkoMMbSCsD7SN/eiPH+HJi0kpItdb3FkU+pNcm4btc khKhzOc/70fkMuwdh/vw86LORCvMXhvwgRgvCxVSaThPVmcVULCdS4eSK+RtkuutfZEj J2bFYZEvo5lSoGl35awcIYnJLbVdsEsXV2JWkqy0Kpa1C5uFA1/T1zQGI6ly59v0pZ/V GnSXyM2exm4UfWTf/tjWFLPb5L+EIPRWu+RGErAzmH885qKJh66Swzx1u4smF+g9BbtO fK1A== X-Gm-Message-State: APt69E2OzKG7BqxrgFC4yI8H26oyrXWkO6S7DVAJVZOKBWpmWBJXQpcg WcIL0UqbMeOjSejCx3+pWGh6ni5+LvGpT/g3N0I= X-Google-Smtp-Source: ADUXVKLAZS1waKkkPvh8IwSFgVztmWaX4Ose7BGP5WYTBLbQuNs7h3eE+ax2wPMAUppVQJEdYyIiJ73lKJj7WU3Kbto= X-Received: by 2002:a24:918d:: with SMTP id i135-v6mr9419258ite.39.1527979959066; Sat, 02 Jun 2018 15:52:39 -0700 (PDT) MIME-Version: 1.0 References: <3ea085128a4e677a4d4150be18b366bd@kondratyev.su> <8f0bd4c0195ecaf1038268831576c461@kondratyev.su> In-Reply-To: <8f0bd4c0195ecaf1038268831576c461@kondratyev.su> From: blubee blubeeme Date: Sun, 3 Jun 2018 06:52:38 +0800 Message-ID: Subject: Re: Proper way to remove never used ioctls To: Vladimir Kondratyev Cc: Allan Jude , freebsd-current@freebsd.org, owner-freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 22:52:40 -0000 On Sun, Jun 3, 2018, 02:34 Vladimir Kondratyev wrote: > On 2018-06-02 20:36, Allan Jude wrote: > > On 2018-06-02 11:03, Warner Losh wrote: > >> On Sat, Jun 2, 2018 at 7:33 AM, Vladimir Kondratyev > >> > >> wrote: > >> > >>> Hi, > >>> > >>> Our sys/mouse.h header has a definition of MOUSE_GETVARS and > >>> MOUSE_SETVARS > >>> ioctls which are not documented and only stubbed in a few drivers: > >>> mse(4), > >>> psm(4) and syscon's sysmouse(4). The only exception is MOUSE_GETVARS > >>> implemented in psm(4) > >>> > >>> Given the fact that they were introduced 20 years ago, implementation > >>> was > >>> never completed and googling on them shows no traces of usage in > >>> indexed > >>> universe, is it acceptable to just drop both defines and > >>> implementation > >>> w.o. leaving any COMPAT_FREEBSD shims? > >> > >> > >> I'd prepare a patch just removing them. I'd then send that patch to > >> the > >> ports mgr team and request a exp-run. Details for that can be found in > >> > https://www.freebsd.org/doc/en_US.ISO8859-1/articles/committers-guide/ports.html > >> > >> Once that's done, submit a Phabricator review and send me email. I'll > >> make > >> sure it gets pushed in if there's no objections. > >> > >> Warner > > > > This indeed seems to be the correct approach. The exp-run will compile > > the entire ports tree against the patched base system, and identify any > > 3rd party software that fails to compile because of the change. > > Thank you, Allan and Warner! I'll follow yours advice. > > -- > WBR > Vladimir Kondratyev > _______________________________________________ > 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" > This was great information. > From owner-freebsd-current@freebsd.org Sat Jun 2 23:07:57 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 8E416FF4DA5 for ; Sat, 2 Jun 2018 23:07:57 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 289E77FB2B for ; Sat, 2 Jun 2018 23:07:57 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w52N9feb097346 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 2 Jun 2018 23:09:43 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w52N0GiH088740 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Jun 2018 16:07:48 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Sat, 2 Jun 2018 16:07:48 -0700 (PDT) From: Don Lewis Subject: Re: rndc: connect failed: 127.0.0.1#953: permission denied To: "O. Hartmann" cc: FreeBSD CURRENT In-Reply-To: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> Message-ID: References: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: 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, 02 Jun 2018 23:07:57 -0000 On 2 Jun, O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On CURRENT, running on an APU as router/firewall service, out of the blue after an update > I receive this weird message when trying to restart "named" (BIND 9.12, latest from the > ports): > > service named restart > rndc: connect failed: 127.0.0.1#953: > permission denied rndc failed, trying kill: Waiting for PIDS: 871. > > Searching the net reveals that possible access rights issues could cause this problem, > but I do not see any. Does somebody see such problems, too and does have a solution? Do you have a firewall rule that blocks sending to UDP port 953 on 127.0.0.1?