From owner-freebsd-current@freebsd.org Sun Feb 25 14:42: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 9CE23F31139; Sun, 25 Feb 2018 14:42:52 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from smtpq2.tb.mail.iss.as9143.net (smtpq2.tb.mail.iss.as9143.net [212.54.42.165]) (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 333247F4A5; Sun, 25 Feb 2018 14:42:51 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from [212.54.42.133] (helo=smtp9.tb.mail.iss.as9143.net) by smtpq2.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1epxAj-0002l5-Uj; Sun, 25 Feb 2018 15:21:01 +0100 Received: from 5ed231fb.cm-7-3a.dynamic.ziggo.nl ([94.210.49.251] helo=wan0.bsd4all.org) by smtp9.tb.mail.iss.as9143.net with esmtp (Exim 4.86_2) (envelope-from ) id 1epxAj-000203-TF; Sun, 25 Feb 2018 15:21:01 +0100 Received: from newnas (localhost [127.0.0.1]) by wan0.bsd4all.org (Postfix) with ESMTP id E164D2174; Sun, 25 Feb 2018 15:20:59 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from wan0.bsd4all.org ([127.0.0.1]) by newnas (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fTlXV4v4ILMO; Sun, 25 Feb 2018 15:20:50 +0100 (CET) Received: from [192.168.1.65] (unknown [192.168.1.65]) by wan0.bsd4all.org (Postfix) with ESMTPSA id 2376A2166; Sun, 25 Feb 2018 15:20:50 +0100 (CET) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: Re: INTRNG From: peter.blok@bsd4all.org In-Reply-To: <401A33BD-F3AE-4139-9D47-6F85C8333022@brawn.org> Date: Sun, 25 Feb 2018 15:20:49 +0100 Cc: freebsd-arm@freebsd.org, FreeBSD current Content-Transfer-Encoding: quoted-printable Message-Id: <694A18B8-60FB-48C8-AE63-C63250F6D940@bsd4all.org> References: <401A33BD-F3AE-4139-9D47-6F85C8333022@brawn.org> To: Jon Brawn X-Mailer: Apple Mail (2.3445.5.20) X-SourceIP: 94.210.49.251 X-Ziggo-spambar: / X-Ziggo-spamscore: 0.0 X-Ziggo-spamreport: CMAE Analysis: v=2.3 cv=XYenMrx5 c=1 sm=1 tr=0 a=7fK1ynn72W3Z/oi6DA4Tww==:17 a=IkcTkHD0fZMA:10 a=Op4juWPpsa0A:10 a=79WsMlhMAAAA:8 a=qZHiuq15OrB9ri-jzK0A:9 a=XQNlMLMPhtl59P3B:21 a=RBS4klvuPhtMt2ah:21 a=QEXdDO2ut3YA:10 a=0SLe_2h_PVcu0AVkMdds:22 none X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 25 Feb 2018 14:42:52 -0000 While on the subject INTRNG - does anybody know the status of handling = GPIO interrupts with queue/kevent? There were some patches before INTRNG, but they require some work. Peter > On 23 Feb 2018, at 07:25, Jon Brawn wrote: >=20 > Wotcha Gang! >=20 > In my travels through the arm64 GENERIC config file I came across the = option =E2=80=98INTRNG=E2=80=99, and wondered what it was: >=20 > INTeRrupt Next Generation? > INTeger Random Number Generator? > IN TRaiNinG? > INTerrupt Random Number Generator? > INdependent TRaiNinG? >=20 > So, please put me out of my misery, what does INTRNG stand for, and = what are its implications when selected vs not selected? >=20 > Cheers! >=20 > Jon. From owner-freebsd-current@freebsd.org Sun Feb 25 16:25: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 74415F386A5; Sun, 25 Feb 2018 16:25:49 +0000 (UTC) (envelope-from jmd@freebsd.org) Received: from www.poelloepaeae.de (v22017034403546374.happysrv.de [188.68.38.182]) (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 0E48F8503C; Sun, 25 Feb 2018 16:25:48 +0000 (UTC) (envelope-from jmd@freebsd.org) Received: from manray.ogolem.org (c-73-199-171-107.hsd1.nj.comcast.net [73.199.171.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by www.poelloepaeae.de (Postfix) with ESMTPSA id 48DED18813A; Sun, 25 Feb 2018 10:49:11 -0500 (EST) Date: Sun, 25 Feb 2018 10:48:44 -0500 From: Johannes M Dieterich To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE Message-ID: <20180225104844.726b4f17@manray.ogolem.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-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 25 Feb 2018 16:25:49 -0000 Dear all, Please CC me as I am not subscribed. On behalf of the FreeBSDDesktop team and thanks to the tireless efforts of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to report that the graphics/drm-next-kmod port just received an update to Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent CURRENT and 11-STABLE. We have tested this on a range of hardware ourselves: * Haswell * Broadwell * Skylake * Evergreen * Kaveri (both radeon and amgpu KMS) * Carrizo * Polaris Needless to say, the possible space of hardware this could run on is significantly larger. Hence, if you find issues and/or want to propose patches, please do so at our development github: https://github.com/FreeBSDDesktop/kms-drm We absolutely do welcome contributions! Johannes From owner-freebsd-current@freebsd.org Sun Feb 25 22:51: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 E1305F300A4 for ; Sun, 25 Feb 2018 22:51:03 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x236.google.com (mail-yb0-x236.google.com [IPv6:2607:f8b0:4002:c09::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 863A375014 for ; Sun, 25 Feb 2018 22:51:03 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x236.google.com with SMTP id u8-v6so2997109ybo.10 for ; Sun, 25 Feb 2018 14:51:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=uMJdJ1loACneqBYCfQz5mCspkOY/xCQgKJGLK4Nx2Ag=; b=hVjUKQKNXKNOy7TESfPWNJtXvcvKKN+vC0GOfsZt+FgpTacUzAq4EYNczZJP9BqC7y ilPIDbXdsE5UtNzYE6YMiGIiNnyz6ETE344+I6dyMGjBYKzGE4j5g+5IQCb24b9jLPqV nkGD72lwFKgXiJfAmIkl40SeXQi5h1Asy0SnA= 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 :content-transfer-encoding; bh=uMJdJ1loACneqBYCfQz5mCspkOY/xCQgKJGLK4Nx2Ag=; b=HYwyBJfSfCbxLY0vOboCi5XFAW0wX8qrKDc+/d8QAS+8TghtauoS9o/CmfebKMhU7H lvMuFVFoqVPmUmcxR0/kAVObq+ybp2neua40750mj9L3wMTT53hQpg+GcNtu51lnMb2T zJmWE1Mngtn2eb0dlXpJtBPOJqd6vWecEjmRjlzQHguhWA+CftKoWKLORDa+dWgEEoE+ XHQUT/1+LCn8jC6hnkyMCXr45PvKPglMmsfRQnV3azeCbEpkKeh1VpGh5hERKGhBdKFg qjFvRtCcoc2eZnstlmIZ4/Mj0hMxcAGmy1w5ywilCGBfn9jiGHT5ysjwRsUWmu/uYoBC oqHA== X-Gm-Message-State: APf1xPDLgWGK8V3aRw/apa5Ck4ohbpYV1F7AwZyBqnLOj2gmxkR0de7P u9/V6BpO+EbYGSRn+Tb8/gZDkV/Dt7vJsieqyiUGEVno X-Google-Smtp-Source: AG47ELs6/YyOBauCr7lVO4mJhRAnib9hp9DhgYki4Et3vAYhJVHHd9iUWM4Yac/4rwpao4levDjMQ1PE0xCpqZyi2K4= X-Received: by 2002:a25:d091:: with SMTP id h139-v6mr5769013ybg.479.1519599062316; Sun, 25 Feb 2018 14:51:02 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:dfcb:0:0:0:0:0 with HTTP; Sun, 25 Feb 2018 14:50:31 -0800 (PST) From: Eitan Adler Date: Sun, 25 Feb 2018 14:50:31 -0800 Message-ID: Subject: iocage on current seems broken / ascii errors with iocage To: freebsd-current Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 25 Feb 2018 22:51:04 -0000 =E2=88=B4sudo iocage activate zroot =E2=88=B4sudo iocage list +-----+------+-------+---------+-----+ | JID | NAME | STATE | RELEASE | IP4 | +=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D= =3D=3D=3D=3D+=3D=3D=3D=3D=3D+ +-----+------+-------+---------+-----+ =E2=88=B4sudo iocage create -r 11.1-RELEASE Fetching: 11.1-RELEASE Downloading : MANIFEST [####################] 100% 0Mbit/s Downloading : base.txz [####################] 100% 26.51Mbit/s Downloading : lib32.txz [####################] 100% 26.02Mbit/s Downloading : doc.txz [####################] 100% 26.12Mbit/s Downloading : src.txz [####################] 100% 26.4Mbit/ss ... 709c103b-1f43-4c3b-a5db-100d19822ccb successfully created! =E2=88=B4sudo iocage list =E2=88=B4zfs list (git:global)-[master] NAME USED AVAIL REFER MOUNTPOINT ... zroot/ROOT 2.98G 802G 88K none zroot/ROOT/default 2.98G 802G 2.98G / ... zroot/iocage 1.19G 802G 100K /iocage zroot/iocage/download 260M 802G 88K /iocage/download zroot/iocage/download/11.1-RELEASE 260M 802G 260M /iocage/download/11.1-RELEASE zroot/iocage/images 88K 802G 88K /iocage/images zroot/iocage/jails 368K 802G 88K /iocage/jails zroot/iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb 280K 802G 92K /iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb zroot/iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb/root 188K 802G 961M /iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb/root zroot/iocage/log 88K 802G 88K /iocage/log zroot/iocage/releases 961M 802G 88K /iocage/releases zroot/iocage/releases/11.1-RELEASE 961M 802G 88K /iocage/releases/11.1-RELEASE zroot/iocage/releases/11.1-RELEASE/root 961M 802G 961M /iocage/releases/11.1-RELEASE/root zroot/iocage/templates 88K 802G 88K /iocage/templates ... =E2=88=B4sudo iocage rename 709c103b-1f43-4c3b-a5db-100d19822ccb bastion (git:global)-[master] Traceback (most recent call last): File "/usr/local/bin/iocage", line 10, in sys.exit(cli()) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in= main rv =3D self.invoke(ctx) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke return _process_result(sub_ctx.command.invoke(sub_ctx)) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke return callback(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/iocage/cli/rename.py", line 39, in cli ioc.IOCage(exit_on_error=3DTrue, jail=3Djail).rename(new_name) File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", line 1211, in rename self.set(f"host_hostuuid=3D{new_name}", rename=3DTrue) File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", line 1415, in set self.get(_prop) File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", line 1121, in get exit_on_error=3Dself.exit_on_error).json_get_value(prop) File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_json.py", line 563, in json_get_value conf =3D self.json_load() File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_json.py", line 226, in json_load if jail_dataset.mountpoint is None: File "libzfs.pyx", line 2311, in libzfs.ZFSDataset.mountpoint.__get__ UnicodeDecodeError: 'ascii' codec can't decode byte 0xc0 in position 320: ordinal not in range(128) What should I do from here? --=20 Eitan Adler From owner-freebsd-current@freebsd.org Sun Feb 25 23:16: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 91E8CF31BA9 for ; Sun, 25 Feb 2018 23:16:01 +0000 (UTC) (envelope-from asomers@gmail.com) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::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 E49C67602C for ; Sun, 25 Feb 2018 23:16:00 +0000 (UTC) (envelope-from asomers@gmail.com) Received: by mail-lf0-x22d.google.com with SMTP id 37so19582717lfs.7 for ; Sun, 25 Feb 2018 15:16:00 -0800 (PST) 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=77DWCUM1AqFf4U93V07c1LL7oIopXNDWtWEViMBRk4Q=; b=U+6t2SNGA8NVjXYV71wksJRsQFzH8AJb/lyAI+z8imyX11jXw/WMOJgD/eNiFkWOoY QZnlOsn/SO0w2jDoqceaf1PeFfudBiQmeXQL0sPHlrDC9rCqj1erRexG20qtJVi7rf7l xHZyxbRQtNvVPE8Wsf0B1+9xXhek+CP5AKZOOmdhzE8Zgkq1I57+UtW74EfOtzXiTp7M rmrlub0AMWNwKdH8WX4iEf3TmARuD4cNnT7owetrW7o8N6UC3PIiAOw90Ov5Yf6vG1Sj z6UreDYkNwqR2cCEK3GcLWnb8GxD6EwH/wr4AzM/sVKfWgif0dNUVVNh63B8UBrv4awV On5g== 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=77DWCUM1AqFf4U93V07c1LL7oIopXNDWtWEViMBRk4Q=; b=ZEBOb/irXEwPY6i4P/703yV1cpnk6YAe8aMBwl4I7taQ3cOhDLh20pYUkl9nCCJ7QU l3rRWxxOx2UqOms+PMHD+imoLjELLrB0X56W8Cp/dWG13ZBFb/MZtyOjVrmP/3HmcLvu CObeeg+eMAOSZ9lkrZbDikqQCxsVLYFi6Nw+6bJgoh5c0l8XBBLwgNjGp1Co2Y+Cu/Ry 6CS7Zo2XcRK+K1LaIA5/326/AkzMPR+STcy+Z2IFMhiIxx+UkKRuF2/REiKkyK15rLv1 2LGCkVO1m/pOKq3i1+EfcZRAge1k6U//L8YGU4h60BMJ9AawubBmwHOxRqSUmKSTZRlH SqQg== X-Gm-Message-State: APf1xPCyItZa9za7z6b7bdmPApVfy1DgfmHPMf6TVdluVYobV6anPAIT ht6iuenH74axaPNq5Klyw6NMyB5KY2SUJB7xSiKFsQ== X-Google-Smtp-Source: AG47ELv8xKYG+MSgM6MTLebNbjNWOJjyVlQx8FraWZ/jfprqIIeMIiEnEJEYttrIzghimffitNd8yTsS0A/VfAJ2SpA= X-Received: by 10.25.147.219 with SMTP id w88mr6233817lfk.58.1519600559448; Sun, 25 Feb 2018 15:15:59 -0800 (PST) MIME-Version: 1.0 Sender: asomers@gmail.com Received: by 10.179.30.66 with HTTP; Sun, 25 Feb 2018 15:15:58 -0800 (PST) In-Reply-To: References: From: Alan Somers Date: Sun, 25 Feb 2018 16:15:58 -0700 X-Google-Sender-Auth: Nu4cQ00vol2K5dScvMqZg75dceI Message-ID: Subject: Re: iocage on current seems broken / ascii errors with iocage To: Eitan Adler Cc: freebsd-current Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 25 Feb 2018 23:16:02 -0000 On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler wrote: > =E2=88=B4sudo iocage activate zroot > =E2=88=B4sudo iocage list > +-----+------+-------+---------+-----+ > | JID | NAME | STATE | RELEASE | IP4 | > +=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D=3D=3D+=3D=3D=3D=3D=3D= =3D=3D=3D=3D+=3D=3D=3D=3D=3D+ > +-----+------+-------+---------+-----+ > =E2=88=B4sudo iocage create -r 11.1-RELEASE > Fetching: 11.1-RELEASE > > Downloading : MANIFEST [####################] 100% 0Mbit/s > Downloading : base.txz [####################] 100% 26.51Mbit/s > Downloading : lib32.txz [####################] 100% 26.02Mbit/s > Downloading : doc.txz [####################] 100% 26.12Mbit/s > Downloading : src.txz [####################] 100% 26.4Mbit/ss > ... > 709c103b-1f43-4c3b-a5db-100d19822ccb successfully created! > =E2=88=B4sudo iocage list > =E2=88=B4zfs list > (git:global)-[master] > NAME USED > AVAIL REFER MOUNTPOINT > ... > zroot/ROOT 2.98G > 802G 88K none > zroot/ROOT/default 2.98G > 802G 2.98G / > ... > zroot/iocage 1.19G > 802G 100K /iocage > zroot/iocage/download 260M > 802G 88K /iocage/download > zroot/iocage/download/11.1-RELEASE 260M > 802G 260M /iocage/download/11.1-RELEASE > zroot/iocage/images 88K > 802G 88K /iocage/images > zroot/iocage/jails 368K > 802G 88K /iocage/jails > zroot/iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb 280K > 802G 92K /iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb > zroot/iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb/root 188K > 802G 961M /iocage/jails/709c103b-1f43-4c3b-a5db-100d19822ccb/root > zroot/iocage/log 88K > 802G 88K /iocage/log > zroot/iocage/releases 961M > 802G 88K /iocage/releases > zroot/iocage/releases/11.1-RELEASE 961M > 802G 88K /iocage/releases/11.1-RELEASE > zroot/iocage/releases/11.1-RELEASE/root 961M > 802G 961M /iocage/releases/11.1-RELEASE/root > zroot/iocage/templates 88K > 802G 88K /iocage/templates > ... > =E2=88=B4sudo iocage rename 709c103b-1f43-4c3b-a5db-100d19822ccb bastion > (git:global)-[master] > Traceback (most recent call last): > File "/usr/local/bin/iocage", line 10, in > sys.exit(cli()) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line > 722, in __call__ > return self.main(*args, **kwargs) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, > in main > rv =3D self.invoke(ctx) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line > 1066, in invoke > return _process_result(sub_ctx.command.invoke(sub_ctx)) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line > 895, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line > 535, in invoke > return callback(*args, **kwargs) > File "/usr/local/lib/python3.6/site-packages/iocage/cli/rename.py", > line 39, in cli > ioc.IOCage(exit_on_error=3DTrue, jail=3Djail).rename(new_name) > File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", > line 1211, in rename > self.set(f"host_hostuuid=3D{new_name}", rename=3DTrue) > File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", > line 1415, in set > self.get(_prop) > File "/usr/local/lib/python3.6/site-packages/iocage/lib/iocage.py", > line 1121, in get > exit_on_error=3Dself.exit_on_error).json_get_value(prop) > File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_json.py", > line 563, in json_get_value > conf =3D self.json_load() > File "/usr/local/lib/python3.6/site-packages/iocage/lib/ioc_json.py", > line 226, in json_load > if jail_dataset.mountpoint is None: > File "libzfs.pyx", line 2311, in libzfs.ZFSDataset.mountpoint.__get__ > UnicodeDecodeError: 'ascii' codec can't decode byte 0xc0 in position > 320: ordinal not in range(128) > > > What should I do from here? > > It's a well-known problem. You need to patch your copy of py-libzfs. Unfortunately, the patch hasn't been picked up by upstream because the port maintainer believes it to be incorrect, but hasn't found the correct solution yet. Here's the patch: https://github.com/trueos/freebsd-ports/commit/00da370342012d87331eae3d74ef= 6784ed8172be And here's the discussion: https://github.com/iocage/iocage/issues/153 -Alan From owner-freebsd-current@freebsd.org Mon Feb 26 01:42: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 F01B0F3A984 for ; Mon, 26 Feb 2018 01:42:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::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 8E85D7B29B for ; Mon, 26 Feb 2018 01:42:34 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x230.google.com with SMTP id l200so4604293ywb.0 for ; Sun, 25 Feb 2018 17:42:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PuMxvLL8nLHxhm90JnU9yppANT/jIGF6PM8iHVrCFlE=; b=ZeyjKppM6lJSjlqGyYt9N7rGjeuA00quDnxXjk2buUqmImcId8lX1xi/+O/RxVscPe m+hWtbUc8A9BOeRYokjWLb1M+M3s/Rx7zx0zUh8Gg8BO0B5PUpm3NNktTrUODY8OOT/J Sxebc+NGCskG8oMF8e722ZjO1h6YunUEM3sHg= 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=PuMxvLL8nLHxhm90JnU9yppANT/jIGF6PM8iHVrCFlE=; b=b3S3o1hCfWrH0luBxgNmeJubfu0xevXdeKdyhMD/JVqnkiyDib6gBTnBZJZqSjPObA nRzbXtmEjO2V4osJb57OjAVabKbRKHCDxPFgQ4CFo6ICBya83K2LAxmG6NGObMUFp9Mg 0KIjPJzoY2Iw5KiH6uiHTb14u9DeZkk3spoqKyaCLE0gIbWPhhx4vziCzH0odw0WdAcH 5Q52KY1lBncsznyN5J53gC+mla/DCH8ZT7e0jrmxSNsIliYxyW3JOSRdRaLCjlyY3t3s fr9eWhVxUYe35fQwyh45SPO3uZKs3Kgd5UoAGsJM2OQS6X6TBd6kCmVP10CTeLSEfbgf KUug== X-Gm-Message-State: APf1xPDeBYLs8x1HNWrN0m03fBzZg1kueL6SLVaX/LRwcTYzhSAde03X 0CGPiYtFo6pJJNk/tujSl87ZeyNGJVUulDFB8tUyXg== X-Google-Smtp-Source: AH8x2248JRzVx6EIDEIsNe6+7Xp5cXwKA8MSvDQN1V0h03VUKFBruNIWCSuFI2dg1pfcMhOgDeyEwFlvTe2FFEsmMiY= X-Received: by 10.13.219.79 with SMTP id d76mr5658765ywe.182.1519609353778; Sun, 25 Feb 2018 17:42:33 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:dfcb:0:0:0:0:0 with HTTP; Sun, 25 Feb 2018 17:42:03 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Sun, 25 Feb 2018 17:42:03 -0800 Message-ID: Subject: Re: iocage on current seems broken / ascii errors with iocage To: Alan Somers Cc: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 01:42:35 -0000 On 25 February 2018 at 15:15, Alan Somers wrote: > On Sun, Feb 25, 2018 at 3:50 PM, Eitan Adler wrote: >> What should I do from here? >> > > It's a well-known problem. You need to patch your copy of py-libzfs. > Unfortunately, the patch hasn't been picked up by upstream because the port > maintainer believes it to be incorrect, but hasn't found the correct > solution yet. Thanks! I searched by email but not the iocage project. That fixed it. -- Eitan Adler From owner-freebsd-current@freebsd.org Mon Feb 26 05:19:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9B3B6F2BAD2 for ; Mon, 26 Feb 2018 05:19:00 +0000 (UTC) (envelope-from jon@brawn.org) Received: from ahs1.r4l.com (ahs1.r4l.com [198.27.81.125]) (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 034048343C for ; Mon, 26 Feb 2018 05:18:59 +0000 (UTC) (envelope-from jon@brawn.org) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=brawn.org; s=default; h=To:Date:Message-Id:Subject:Mime-Version:Content-Type:From: Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=glN/4iL1Em+CRohRG5pbR40YtwzFNJyX2pZ5Da57Prg=; b=qWp3WkhHtScHI+yfbtPek5ppk/ 3X+wjiC6iCQQ78lwAKrlmtDZE0d3fAL3vLJQ2I+N4ccFmwg4qm5C6/LhhFJOLaLgRuZSGjXzDov4p Ownx3f9pKXvELxEhvXzB3tqT8XYXGebf/F6Osir5E2TQuAvkyHXzzDjvwSuNwZU62ClV59RJGF4ZL R+fv3v/35cwhvduVoJWCrI+vnAWwWPaTwRu4XajGGi8snRFAlTsn/v8FdZ+d4rip+/DjXnRzCplai ZXpBoeCGFTYaF5cE3r9kJpvnTbB6ZtG4xOPm76wa/Pao/Li8pWYV+MbJSbMLZfsYm5mc/vP5bvGUY 6OIqR6Fw==; Received: from [136.62.171.86] (port=49321 helo=[192.168.1.120]) by ahs1.r4l.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89_1) (envelope-from ) id 1eqBBW-000FyL-S2 for freebsd-current@freebsd.org; Mon, 26 Feb 2018 00:18:47 -0500 From: Jon Brawn Content-Type: multipart/signed; boundary="Apple-Mail=_30593960-CB93-4397-8A20-5CAC20A9FD35"; protocol="application/pkcs7-signature"; micalg=sha1 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) Subject: lock order reversal Message-Id: Date: Sun, 25 Feb 2018 23:18:45 -0600 To: FreeBSD current X-Mailer: Apple Mail (2.3445.5.20) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ahs1.r4l.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - brawn.org X-Get-Message-Sender-Via: ahs1.r4l.com: authenticated_id: jon@brawn.org X-Authenticated-Sender: ahs1.r4l.com: jon@brawn.org X-Source: X-Source-Args: X-Source-Dir: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 05:19:00 -0000 --Apple-Mail=_30593960-CB93-4397-8A20-5CAC20A9FD35 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Wotcha! So, I=E2=80=99ve been using FreeBSD 12-CURRENT at various svn releases = for a while now, and I get quite a few =E2=80=9Clock order reversal=E2=80=9D= dumps. The one I=E2=80=99ve got on my screen at the moment is for ufs / = bufwait / ufs: root@brax:/usr/src/stand # lock order reversal: 1st 0xfffffd0003ec17e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 2nd 0xffff0000410efa20 bufwait (bufwait) @ = /usr/src/sys/ufs/ffs/ffs_vnops.c:282 3rd 0xfffffd00b83ca7e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 stack backtrace: #0 0xffff0000003b59d4 at witness_debugger+0x64 #1 0xffff00000032bd34 at __lockmgr_args+0x6ac #2 0xffff0000005c6af0 at ffs_lock+0x88 #3 0xffff000000679eb0 at VOP_LOCK1_APV+0xac #4 0xffff000000426fa8 at _vn_lock+0x64 #5 0xffff000000417550 at vget+0x78 #6 0xffff000000409fdc at vfs_hash_get+0xec #7 0xffff0000005c2b94 at ffs_vgetf+0x44 #8 0xffff0000005b96a8 at softdep_sync_buf+0x9f4 #9 0xffff0000005c7834 at ffs_syncvnode+0x26c #10 0xffff0000005a1b5c at ffs_truncate+0x6b0 #11 0xffff0000005ce3cc at ufs_direnter+0x778 #12 0xffff0000005d64bc at ufs_makeinode+0x4b8 #13 0xffff0000005d2b90 at ufs_create+0x38 #14 0xffff000000677168 at VOP_CREATE_APV+0xac #15 0xffff00000042691c at vn_open_cred+0x264 #16 0xffff00000041fc84 at kern_openat+0x208 #17 0xffff00000064b59c at do_el0_sync+0x8bc Is there something I should be doing to help debug these? Jon.= --Apple-Mail=_30593960-CB93-4397-8A20-5CAC20A9FD35 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILEzCCBSUw ggQNoAMCAQICECQcc6QQWc3Um5HgAnmjhBYwDQYJKoZIhvcNAQELBQAwgZcxCzAJBgNVBAYTAkdC MRswGQYDVQQIExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoT EUNPTU9ETyBDQSBMaW1pdGVkMT0wOwYDVQQDEzRDT01PRE8gUlNBIENsaWVudCBBdXRoZW50aWNh dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTE3MTAyODAwMDAwMFoXDTE4MTAyODIzNTk1OVow HjEcMBoGCSqGSIb3DQEJARYNam9uQGJyYXduLm9yZzCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBALEscuT73gkjXEfkaQU3QXOOIDFilHr9RV/FKPk+ZO3wyXpoChqRW+anE+kKBLSCsmoX 6HnhAmcq3j9umj5jIYwpD84m26XbWQK+uo42GZ3cAF12VvO0g/toUvI+nJcxiD39APWowPKQ4Nae 4FN4hLOcwd2zyF3LiJgq4aXXcBQxl2s1JRCb7STFl5qpp73JVbFp1MkABmESyzI6KE0LLH3hHICU d2m+Omg6L8T+RgsTEKmgTvw1hYD04ms9ttji/viI8LtR3V9p9DDGH0iSCF56kPo4WfsbfGVBs1km tw8uvB6OVNGiD0q05kR/GI4jGiMLa4UhlCC0VsYfx7ZyGEUCAwEAAaOCAeMwggHfMB8GA1UdIwQY MBaAFIKvbIz4xf6WYXzoHz0rcUhexIvAMB0GA1UdDgQWBBRYtBFf7BnRYLxKWDc5DiI35q5WVzAO BgNVHQ8BAf8EBAMCBaAwDAYDVR0TAQH/BAIwADAgBgNVHSUEGTAXBggrBgEFBQcDBAYLKwYBBAGy MQEDBQIwEQYJYIZIAYb4QgEBBAQDAgUgMEYGA1UdIAQ/MD0wOwYMKwYBBAGyMQECAQEBMCswKQYI KwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5uZXQvQ1BTMFoGA1UdHwRTMFEwT6BNoEuG SWh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9ET1JTQUNsaWVudEF1dGhlbnRpY2F0aW9uYW5k U2VjdXJlRW1haWxDQS5jcmwwgYsGCCsGAQUFBwEBBH8wfTBVBggrBgEFBQcwAoZJaHR0cDovL2Ny dC5jb21vZG9jYS5jb20vQ09NT0RPUlNBQ2xpZW50QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFp bENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDovL29jc3AuY29tb2RvY2EuY29tMBgGA1UdEQQRMA+B DWpvbkBicmF3bi5vcmcwDQYJKoZIhvcNAQELBQADggEBAKZgWVdxinnS81TZvPWc8kXjtzxKSBFU 6ZXBkofX+CSRuD+Wmg4vlt6fNIaVWqWDF95qjR3TOwyb+LQJnsMyYhAl9NI6AJTxgfghzKK49MVP aC0K7V4TnWCiucJsfK+xDqZIevPFPF3mpYz7/Uf8VPbX2uK80/uUoBRroXDLyHv7fTzG8K+bHBh6 l2x2xFB04nxAhRS4yaJvOeV6ckPOHvCgHhncXQ1HoPUvV/M94K3jaURLPvSUm2tgzODJ97QDHDWM SF7xfItpAM7AVAmN0M0U8sWI/qDykqpoeOc/TrMNeRTEcuphuJASMuN+oP57T+XZFq/lOEEIw1H+ 4QZ1mnIwggXmMIIDzqADAgECAhBqm+E4O/8ra58B1dm4p1JWMA0GCSqGSIb3DQEBDAUAMIGFMQsw CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3Jk MRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDErMCkGA1UEAxMiQ09NT0RPIFJTQSBDZXJ0aWZp Y2F0aW9uIEF1dGhvcml0eTAeFw0xMzAxMTAwMDAwMDBaFw0yODAxMDkyMzU5NTlaMIGXMQswCQYD VQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRow GAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBDbGllbnQgQXV0 aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAL6znlesKHZ1QBbHOAOY08YYdiFQ8yV5C0y1oNF9Olg+nKcxLqf2NHbZhGra0D00SOTq 9bus3/mxgUsg/Wh/eXQ0pnp8tZ8XZWAnlyKMpjL+qUByRjXCA6RQyDMqVaVUkbIr5SU0RDX/kSsK wer3H1pT/HUrBN0X8sKtPTdGX8XAWt/VdMLBrZBlgvnkCos+KQWWCo63OTTqRvaq8aWccm+KOMjT cE6s2mj6RkalweyDI7X+7U5lNo6jzC8RTXtVV4/Vwdax720YpMPJQaDaElmOupyTf1Qib+cpukNJ nQmwygjD8m046DQkLnpXNCAGjuJy1F5NATksUsbfJAr7FLUCAwEAAaOCATwwggE4MB8GA1UdIwQY MBaAFLuvfgI9+qbxPISOre44mOzZMjLUMB0GA1UdDgQWBBSCr2yM+MX+lmF86B89K3FIXsSLwDAO BgNVHQ8BAf8EBAMCAYYwEgYDVR0TAQH/BAgwBgEB/wIBADARBgNVHSAECjAIMAYGBFUdIAAwTAYD VR0fBEUwQzBBoD+gPYY7aHR0cDovL2NybC5jb21vZG9jYS5jb20vQ09NT0RPUlNBQ2VydGlmaWNh dGlvbkF1dGhvcml0eS5jcmwwcQYIKwYBBQUHAQEEZTBjMDsGCCsGAQUFBzAChi9odHRwOi8vY3J0 LmNvbW9kb2NhLmNvbS9DT01PRE9SU0FBZGRUcnVzdENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov L29jc3AuY29tb2RvY2EuY29tMA0GCSqGSIb3DQEBDAUAA4ICAQB4XLKBKDRPPO5fVs6fl1bsj6Jr F/bz9kkIBtTYLzXN30D+03Hj6OxCDBEaIeNmsBhrJmuubvyE7HtoSmR809AgcYboW+rcTNZ/8u/H v+GTrNI/AhqX2/kiQNxmgUPt/eJPs92Qclj0HnVyy9TnSvGkSDU7I5Px+TbO+88G4zipA2psZaWe EykgzClZlPz1FjTCkk77ZXp5cQYYexE6zeeN4/0OqqoAloFrjAF4o50YJafX8mnahjp3I2Y2mkjh k0xQfhNqbzlLWPoT3m7j7U26u7zg6swjOq8hITYc3/np5tM5aVyu6t99p17bTbY7+1RTWBviN9YJ zK8HxzObXYWBf/L+VGOYNsQDTxAk0Hbvb1j6KjUhg7fO294F29QIhhmiNOr84JHoy+fNLpfvYc/Q 9EtFOI5ISYgOxLk3nD/whbUe9rmEQXLp8MB933Ij474gwwCPUpwv9mj2PMnXoc7mbrS22XUSeTwx CTP9bcmUdp4jmIoWfhQm7X9w/Zgddg+JZ/YnIHOwsGsaTUgj7fIvxqith7DoJC91WJ8Lce3CVJqb 1XWeKIJ84F7YLXZN0oa7TktYgDdmQVxYkZo1c5noaDKH9Oq9cbm/vOYRUM1cWcef20Wkyk5S/GFy yPJwG0fR1nRas3DqAf4cXxMiEKcff7PNa4M3RGTqH0pWR8p6EjGCA7cwggOzAgEBMIGsMIGXMQsw CQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3Jk MRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09NT0RPIFJTQSBDbGllbnQg QXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQJBxzpBBZzdSbkeACeaOEFjAJBgUr DgMCGgUAoIIB3zAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xODAy MjYwNTE4NDZaMCMGCSqGSIb3DQEJBDEWBBQtC1tAj0/tj4RsUYrCtLQZ1QsjIzCBvQYJKwYBBAGC NxAEMYGvMIGsMIGXMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAw DgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE9MDsGA1UEAxM0Q09N T0RPIFJTQSBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBDQQIQJBxzpBBZ zdSbkeACeaOEFjCBvwYLKoZIhvcNAQkQAgsxga+ggawwgZcxCzAJBgNVBAYTAkdCMRswGQYDVQQI ExJHcmVhdGVyIE1hbmNoZXN0ZXIxEDAOBgNVBAcTB1NhbGZvcmQxGjAYBgNVBAoTEUNPTU9ETyBD QSBMaW1pdGVkMT0wOwYDVQQDEzRDT01PRE8gUlNBIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQg U2VjdXJlIEVtYWlsIENBAhAkHHOkEFnN1JuR4AJ5o4QWMA0GCSqGSIb3DQEBAQUABIIBAGJU6wHs m1MZlYhviSXytHkq+Q3EhFRKzl3VaS8kUAiwXz/doYlZAVBQxmyrrGl+4PnzvQRNWIQJq53bJRBN FIAXeoBnn2VGlMCEjT6Ys6u31rH45h+6NqstEvRXOJgQBgcs6IJkoUeS42iJpGRz2lBmM6Mh914q RSESAcyJiKhm4KgpknEWRT/9SmC85Va9SjQ+kGyhJm4ae29jB8knDMh/cQ7obKNZgttSG+H28M0S T0G95kT6gvFOlKGCFH9B5npC4Cu65MPERdJCrNZhnjTVfx4ORRoS7HDlteYwA5cU1QEyJvnIk/OS WCzrH7sahPSiK1klzEZdwp+bpT0yx4YAAAAAAAA= --Apple-Mail=_30593960-CB93-4397-8A20-5CAC20A9FD35-- From owner-freebsd-current@freebsd.org Mon Feb 26 06: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 252D4F2EF15 for ; Mon, 26 Feb 2018 06:42:19 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f44.google.com (mail-lf0-f44.google.com [209.85.215.44]) (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 91F8485E03 for ; Mon, 26 Feb 2018 06:42:18 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f44.google.com with SMTP id f75so15546203lfg.6 for ; Sun, 25 Feb 2018 22:42:18 -0800 (PST) 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:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iBMl6yFRmby7Y9SNFKdc18/hc1DkEW5PKKkryEvP3qg=; b=BDjc65WaADqBaa+iGJgSaVUiHucYLYyz34RQB7AxfN6KycUTXYhcQPfEswFhMwzvOT B/wM9un1UW29nU4qEQbO9JmfhnouKH0RNjxlkv7b1bqBFwZLp5dn40I1NsSeFU1Mt74P +iIgwj7+Dx1Xul+9apS8EgylOluzTdW9zLXDY0XZbBwh0+0Lfqz8aP5qDPST/+nTwaOr 3IkPpdacnqjve4Yf+k5hR4xqF0GEVo1x86gdbFQhEUSIKuI7t5BsvltWnARNnqQVYAdp /S9gyiPoPdEW+SKtRKYg7LAFihBexQJRB+fke4zCPGh88axmztI9TZQaLH5lir/ZiUTx nIww== X-Gm-Message-State: APf1xPCf4Lfpe+p4LHnkAjTuSsf4895PrmnxlKbISugw5ISR/4gSDcNy LFMuzefqdC+zWcxSzBPY5ifpOEhd X-Google-Smtp-Source: AG47ELtUfXb4HmyVwI4bscv6QPj97J2caTe9vPcM8uM69GXqCa4IBpflZJTbQFs6Ap0a+AaDTJcy1g== X-Received: by 10.25.150.78 with SMTP id y75mr6999798lfd.81.1519627336609; Sun, 25 Feb 2018 22:42:16 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id a189sm1820083lfb.32.2018.02.25.22.42.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 25 Feb 2018 22:42:15 -0800 (PST) Subject: Re: lock order reversal To: Jon Brawn , FreeBSD current References: From: Andriy Gapon Message-ID: <244ca590-bd28-154c-84f3-4cda50ccd8e6@FreeBSD.org> Date: Mon, 26 Feb 2018 08:42:14 +0200 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-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 06:42:19 -0000 On 26/02/2018 07:18, Jon Brawn wrote: > Wotcha! > > So, I’ve been using FreeBSD 12-CURRENT at various svn releases for a while now, and I get quite a few “lock order reversal” dumps. The one I’ve got on my screen at the moment is for ufs / bufwait / ufs: > > root@brax:/usr/src/stand # lock order reversal: > 1st 0xfffffd0003ec17e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 > 2nd 0xffff0000410efa20 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:282 > 3rd 0xfffffd00b83ca7e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2602 > stack backtrace: > #0 0xffff0000003b59d4 at witness_debugger+0x64 > #1 0xffff00000032bd34 at __lockmgr_args+0x6ac > #2 0xffff0000005c6af0 at ffs_lock+0x88 > #3 0xffff000000679eb0 at VOP_LOCK1_APV+0xac > #4 0xffff000000426fa8 at _vn_lock+0x64 > #5 0xffff000000417550 at vget+0x78 > #6 0xffff000000409fdc at vfs_hash_get+0xec > #7 0xffff0000005c2b94 at ffs_vgetf+0x44 > #8 0xffff0000005b96a8 at softdep_sync_buf+0x9f4 > #9 0xffff0000005c7834 at ffs_syncvnode+0x26c > #10 0xffff0000005a1b5c at ffs_truncate+0x6b0 > #11 0xffff0000005ce3cc at ufs_direnter+0x778 > #12 0xffff0000005d64bc at ufs_makeinode+0x4b8 > #13 0xffff0000005d2b90 at ufs_create+0x38 > #14 0xffff000000677168 at VOP_CREATE_APV+0xac > #15 0xffff00000042691c at vn_open_cred+0x264 > #16 0xffff00000041fc84 at kern_openat+0x208 > #17 0xffff00000064b59c at do_el0_sync+0x8bc > > Is there something I should be doing to help debug these? IMO, no. Please ignore LORs involving "bufwait", "filedesc structure", "syncer" unless you experience any real problem (like a lock up). -- Andriy Gapon From owner-freebsd-current@freebsd.org Mon Feb 26 09:44: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 D9CADF38E96 for ; Mon, 26 Feb 2018 09:44:31 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (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 6ABBE6C98E for ; Mon, 26 Feb 2018 09:44:30 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w1Q9ikFx063667 for ; Mon, 26 Feb 2018 01:44:52 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 In-Reply-To: <244ca590-bd28-154c-84f3-4cda50ccd8e6@FreeBSD.org> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "FreeBSD current" Subject: Re: lock order reversal Date: Mon, 26 Feb 2018 01:44:52 -0800 Message-Id: <6abdec7728c2481db68739a5622ab7fc@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 09:44:32 -0000 On Mon, 26 Feb 2018 08:42:14 +0200 "Andriy Gapon" said > On 26/02/2018 07:18, Jon Brawn wrote: > > Wotcha! > >=20 > > So, I=E2=80=99ve been using FreeBSD 12-CURRENT at various svn releases = for a while > > now, and I get quite a few =E2=80=9Clock order reversal=E2=80=9D dumps=2E= The one I=E2=80=99ve got > > on my screen at the moment is for ufs / bufwait / ufs: > >=20 > > root@brax:/usr/src/stand # lock order reversal: > > 1st 0xfffffd0003ec17e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr=2Ec:2602 > > 2nd 0xffff0000410efa20 bufwait (bufwait) @ > > /usr/src/sys/ufs/ffs/ffs_vnops=2Ec:282 > > 3rd 0xfffffd00b83ca7e8 ufs (ufs) @ /usr/src/sys/kern/vfs_subr=2Ec:2602 > > stack backtrace: > > #0 0xffff0000003b59d4 at witness_debugger+0x64 > > #1 0xffff00000032bd34 at __lockmgr_args+0x6ac > > #2 0xffff0000005c6af0 at ffs_lock+0x88 > > #3 0xffff000000679eb0 at VOP_LOCK1_APV+0xac > > #4 0xffff000000426fa8 at _vn_lock+0x64 > > #5 0xffff000000417550 at vget+0x78 > > #6 0xffff000000409fdc at vfs_hash_get+0xec > > #7 0xffff0000005c2b94 at ffs_vgetf+0x44 > > #8 0xffff0000005b96a8 at softdep_sync_buf+0x9f4 > > #9 0xffff0000005c7834 at ffs_syncvnode+0x26c > > #10 0xffff0000005a1b5c at ffs_truncate+0x6b0 > > #11 0xffff0000005ce3cc at ufs_direnter+0x778 > > #12 0xffff0000005d64bc at ufs_makeinode+0x4b8 > > #13 0xffff0000005d2b90 at ufs_create+0x38 > > #14 0xffff000000677168 at VOP_CREATE_APV+0xac > > #15 0xffff00000042691c at vn_open_cred+0x264 > > #16 0xffff00000041fc84 at kern_openat+0x208 > > #17 0xffff00000064b59c at do_el0_sync+0x8bc > >=20 > > Is there something I should be doing to help debug these? >=20 > IMO, no=2E Please ignore LORs involving "bufwait", "filedesc structure", > "syncer" > unless you experience any real problem (like a lock up)=2E Or build a kernel without WITNESS (and FULL_BUF_TRACKING?) :-) --Chris >=20 > --=20 > Andriy Gapon > _______________________________________________ > freebsd-current@freebsd=2Eorg mailing list > https://lists=2Efreebsd=2Eorg/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd=2Eorg= " From owner-freebsd-current@freebsd.org Mon Feb 26 15:23: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 A6BC0F2CB4F; Mon, 26 Feb 2018 15:23:53 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 23A9B7A060; Mon, 26 Feb 2018 15:23:52 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w1QFNjqW021033 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Feb 2018 07:23:46 -0800 (PST) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w1QFNjLF021032; Mon, 26 Feb 2018 07:23:45 -0800 (PST) (envelope-from fbsd) Date: Mon, 26 Feb 2018 07:23:45 -0800 From: bob prohaska To: freebsd-arm@freebsd.org Cc: freebsd-current@freebsd.org, bob prohaska Subject: Errors compiling LLVM on RPi3 at 330019 Message-ID: <20180226152345.GA21006@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 15:23:53 -0000 At revision 330019 -DNO_CLEAN buildworld stops with --- Target/X86/X86ISelDAGToDAG.o --- /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: error: use of undeclared identifier 'SelectCode' SelectCode(ZextTarget.getNode()); ^ /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2464:7: error: use of undeclared identifier 'SelectCode' SelectCode(Brind.getNode()); ^ /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2480:5: error: use of undeclared identifier 'SelectCode' SelectCode(VSelect.getNode()); ^ /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:3072:3: error: use of undeclared identifier 'SelectCode' SelectCode(Node); Should I wait for an update, or run cleandir? This is on a Pi3. Thanks for reading, bob prohaska From owner-freebsd-current@freebsd.org Mon Feb 26 18:16: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 DCB1BF37F35; Mon, 26 Feb 2018 18:16:21 +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 757B481530; Mon, 26 Feb 2018 18:16:21 +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 B0BBF8329; Mon, 26 Feb 2018 19:16:14 +0100 (CET) From: Dimitry Andric Message-Id: <6AAA36E2-CDE3-42C3-B070-3C75044656C6@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_3ABC99C8-E8AC-4180-A3F4-099890C3F398"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Errors compiling LLVM on RPi3 at 330019 Date: Mon, 26 Feb 2018 19:16:18 +0100 In-Reply-To: <20180226152345.GA21006@www.zefox.net> Cc: freebsd-arm@freebsd.org, freebsd-current@freebsd.org To: bob prohaska References: <20180226152345.GA21006@www.zefox.net> X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 18:16:22 -0000 --Apple-Mail=_3ABC99C8-E8AC-4180-A3F4-099890C3F398 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 26 Feb 2018, at 16:23, bob prohaska wrote: >=20 > At revision 330019 -DNO_CLEAN buildworld stops with >=20 > --- Target/X86/X86ISelDAGToDAG.o --- > /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2463:7: = error: use of undeclared identifier 'SelectCode' > SelectCode(ZextTarget.getNode()); > ^ > /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2464:7: = error: use of undeclared identifier 'SelectCode' > SelectCode(Brind.getNode()); > ^ > /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:2480:5: = error: use of undeclared identifier 'SelectCode' > SelectCode(VSelect.getNode()); > ^ > /usr/src/contrib/llvm/lib/Target/X86/X86ISelDAGToDAG.cpp:3072:3: = error: use of undeclared identifier 'SelectCode' > SelectCode(Node); >=20 > Should I wait for an update, or run cleandir? This is on a Pi3. =46rom which revision were you upgrading? It looks like your .inc files were not regenerated properly by llvm-tblgen, maybe timestamps out of whack? I would indeed try a clean build. -Dimitry --Apple-Mail=_3ABC99C8-E8AC-4180-A3F4-099890C3F398 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWpRO8gAKCRCwXqMKLiCW oxKAAKC4GHhn3d0pm3LQRoKLHI6meBgW4ACgwcS+ku+a/fNe6Pbn5vFgF3zUdQA= =Hhgl -----END PGP SIGNATURE----- --Apple-Mail=_3ABC99C8-E8AC-4180-A3F4-099890C3F398-- From owner-freebsd-current@freebsd.org Mon Feb 26 19:42:42 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AB82DF3E0B8; Mon, 26 Feb 2018 19:42:42 +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 49CC58610F; Mon, 26 Feb 2018 19:42:41 +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 1eqOfS-0007PZ-A2; Mon, 26 Feb 2018 20:42:34 +0100 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org, "Johannes M Dieterich" Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE References: <20180225104844.726b4f17@manray.ogolem.org> Date: Mon, 26 Feb 2018 20:42:35 +0100 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Ronald Klop" Message-ID: In-Reply-To: <20180225104844.726b4f17@manray.ogolem.org> 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: dfea3049d3b923820beb462d65569822 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 26 Feb 2018 19:42:42 -0000 On Sun, 25 Feb 2018 16:48:44 +0100, Johannes M Dieterich wrote: > Dear all, > > Please CC me as I am not subscribed. > > On behalf of the FreeBSDDesktop team and thanks to the tireless efforts > of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to > report that the graphics/drm-next-kmod port just received an update to > Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent > CURRENT and 11-STABLE. > > We have tested this on a range of hardware ourselves: > * Haswell > * Broadwell > * Skylake > * Evergreen > * Kaveri (both radeon and amgpu KMS) > * Carrizo > * Polaris > > Needless to say, the possible space of hardware this could run on is > significantly larger. Hence, if you find issues and/or want to propose > patches, please do so at our development github: > > https://github.com/FreeBSDDesktop/kms-drm > > We absolutely do welcome contributions! > > Johannes Nice work. It might be nice to edit the linux 4,9 reference from pkg-descr. Regards, Ronald. From owner-freebsd-current@freebsd.org Tue Feb 27 01:24:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFB23F34840 for ; Tue, 27 Feb 2018 01:24:50 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Received: from mail1.protonmail.ch (mail1.protonmail.ch [185.70.40.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2C6E47727D for ; Tue, 27 Feb 2018 01:24:49 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Date: Mon, 26 Feb 2018 20:17:57 -0500 To: "freebsd-current@freebsd.org" From: Mylan Connolly Reply-To: Mylan Connolly Subject: Compilation failure of the kernel for drm-next Message-ID: Feedback-ID: LynW_1UfPsCNIeRmn6VnQX7Jv_J-d7679pwNAQLet51aNK-bYdze1ldqgK4iRhJvu9suK3NkzvrvvdOCSoLZ4w==:Ext:ProtonMail MIME-Version: 1.0 X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 27 Feb 2018 01:24:51 -0000 SGVsbG8gYWxsLAoKSSdtIG5vdCBzdXJlIGlmIHRoaXMgaXMgdGhlIGJlc3QgcGxhY2UgdG8gc2Vu ZCB0aGlzLCBidXQgaXQgbG9va3MgbGlrZSB0aGUgaXNzdWUgdHJhY2tlciBpbiBHaXRodWIgaXMg YSBiaXQgZGVhZC4KCkkgaGF2ZSBiZWVuIHRyeWluZyB0byBjb21waWxlIGl0IGZvciB0aGUgcGFz dCBmZXcgd2Vla3MgYWZ0ZXIgZG93bmxvYWRpbmcgdGhlIGxhdGVzdCBjb2RlIGFib3V0IG9uY2Ug YSB3ZWVrIGFuZCBpdCBsb29rcyBsaWtlIHRoaXMgaXNzdWUgaGFzbid0IHJlc29sdmVkIGl0c2Vs Zi4KCldoZW4gSSB0cnkgdG8gY29tcGlsZSB0aGUga2VybmVsICh1c2luZyB0aGUgY29tbWFuZCBg bWFrZSBrZXJuZWxgKSBJIGdldCB0aGUgZm9sbG93aW5nIGVycm9yLiBMZXQgbWUga25vdyBpZiB0 aGVyZSdzIGFueXRoaW5nIGVsc2UgSSBjYW4gZG8gdG8gYXNzaXN0LgoKL3Vzci9sb2NhbC9iaW4v Y2NhY2hlIGNjIC10YXJnZXQgeDg2XzY0LXVua25vd24tZnJlZWJzZDEyLjAgLS1zeXNyb290PS91 c3Ivb2JqL3Vzci9zcmMvYW1kNjQuYW1kNjQvdG1wIC1CL3Vzci9vYmovdXNyL3NyYy9hbWQ2NC5h bWQ2NC90bXAvdXNyL2JpbiAgLU8yIC1waXBlICctREtCVUlMRF9NT0ROQU1FPSJpOTE1a21zIicg LWluY2x1ZGUgL3Vzci9zcmMvc3lzL2Rldi9kcm0vZHJtX29zX2NvbmZpZy5oIC1tYXJjaD1za3ls YWtlICAtZm5vLXN0cmljdC1hbGlhc2luZyAtV2Vycm9yIC1EX0tFUk5FTCAtREtMRF9NT0RVTEUg LW5vc3RkaW5jICAtSS91c3Ivc3JjL3N5cy9jb21wYXQvbGludXhrcGkvZHVtbXkvaW5jbHVkZSAt SS91c3Ivc3JjL3N5cy9jb21wYXQvbGludXhrcGkvZ3BsdjIvaW5jbHVkZSAtSS91c3Ivc3JjL3N5 cy9jb21wYXQvbGludXhrcGkvY29tbW9uL2luY2x1ZGUgLUkvdXNyL3NyYy9zeXMvY29tcGF0L2xp bnV4a3BpL2NvbW1vbi9pbmNsdWRlL3VhcGkgLURIQVZFX0tFUk5FTF9PUFRJT05fSEVBREVSUyAt aW5jbHVkZSAvdXNyL29iai91c3Ivc3JjL2FtZDY0LmFtZDY0L3N5cy9HRU5FUklDL29wdF9nbG9i YWwuaCAtSS4gLUkvdXNyL3NyYy9zeXMgLWZuby1jb21tb24gLWcgLWZuby1vbWl0LWZyYW1lLXBv aW50ZXIgLW1uby1vbWl0LWxlYWYtZnJhbWUtcG9pbnRlciAtSS91c3Ivb2JqL3Vzci9zcmMvYW1k NjQuYW1kNjQvc3lzL0dFTkVSSUMgICAtTUQgIC1NRi5kZXBlbmQuaW50ZWxfZnJlZWJzZC5vIC1N VGludGVsX2ZyZWVic2QubyAtbWNtb2RlbD1rZXJuZWwgLW1uby1yZWQtem9uZSAtbW5vLW1teCAt bW5vLXNzZSAtbXNvZnQtZmxvYXQgIC1mbm8tYXN5bmNocm9ub3VzLXVud2luZC10YWJsZXMgLWZm cmVlc3RhbmRpbmcgLWZ3cmFwdiAtZnN0YWNrLXByb3RlY3RvciAtZ2R3YXJmLTIgLVdhbGwgLVdy ZWR1bmRhbnQtZGVjbHMgLVduZXN0ZWQtZXh0ZXJucyAtV3N0cmljdC1wcm90b3R5cGVzIC1XbWlz c2luZy1wcm90b3R5cGVzIC1XcG9pbnRlci1hcml0aCAtV2lubGluZSAtV2Nhc3QtcXVhbCAtV3Vu ZGVmIC1Xbm8tcG9pbnRlci1zaWduIC1EX19wcmludGZfXz1fX2ZyZWVic2Rfa3ByaW50Zl9fIC1X bWlzc2luZy1pbmNsdWRlLWRpcnMgLWZkaWFnbm9zdGljcy1zaG93LW9wdGlvbiAtV25vLXVua25v d24tcHJhZ21hcyAtV25vLWVycm9yLXRhdXRvbG9naWNhbC1jb21wYXJlIC1Xbm8tZXJyb3ItZW1w dHktYm9keSAtV25vLWVycm9yLXBhcmVudGhlc2VzLWVxdWFsaXR5IC1Xbm8tZXJyb3ItdW51c2Vk LWZ1bmN0aW9uIC1Xbm8tZXJyb3ItcG9pbnRlci1zaWduIC1Xbm8tZXJyb3Itc2hpZnQtbmVnYXRp dmUtdmFsdWUgLVduby1lcnJvci1hZGRyZXNzLW9mLXBhY2tlZC1tZW1iZXIgLVduby1wb2ludGVy LWFyaXRoIC1Xbm8tZm9ybWF0ICAtbW5vLWFlcyAtbW5vLWF2eCAgLXN0ZD1pc285ODk5OjE5OTkg LWMgL3Vzci9zcmMvc3lzL2Rldi9kcm0vaTkxNS9pbnRlbF9mcmVlYnNkLmMgLW8gaW50ZWxfZnJl ZWJzZC5vCgovdXNyL3NyYy9zeXMvZGV2L2RybS9pOTE1L2ludGVsX2ZyZWVic2QuYzoyMDM6NTog ZXJyb3I6IHVzZSBvZiB1bmRlY2xhcmVkIGlkZW50aWZpZXIgJ1ZNX1dBSVQnOyBkaWQgeW91IG1l YW4gJ1ZNX0xBU1QnPwoKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBWTV9XQUlUOwoK ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBefn5+fn5+CgogICAgICAgICAgICAgICAg ICAgICAgICAgICAgICAgIFZNX0xBU1QKCi91c3Ivc3JjL3N5cy9zeXMvc3lzdG0uaDo4MTo1MDog bm90ZTogJ1ZNX0xBU1QnIGRlY2xhcmVkIGhlcmUKCiAgICAgICAgICAgICAgICBWTV9HVUVTVF9W TVdBUkUsIFZNX0dVRVNUX0tWTSwgVk1fR1VFU1RfQkhZVkUsIFZNX0xBU1QgfTsKCiAgICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIF4K Ci91c3Ivc3JjL3N5cy9kZXYvZHJtL2k5MTUvaW50ZWxfZnJlZWJzZC5jOjIwMzo1OiBlcnJvcjog ZXhwcmVzc2lvbiByZXN1bHQgdW51c2VkIFstV2Vycm9yLC1XdW51c2VkLXZhbHVlXQoKICAgICAg ICAgICAgICAgICAgICAgICAgICAgICAgICBWTV9XQUlUOwoKICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICBefn5+fn5+CgoyIGVycm9ycyBnZW5lcmF0ZWQuCgoqKiogW2ludGVsX2ZyZWVi c2Qub10gRXJyb3IgY29kZSAxCgptYWtlWzZdOiBzdG9wcGVkIGluIC91c3Ivc3JjL3N5cy9tb2R1 bGVzL2RybS9pOTE1L2k5MTVrbXMKCjEgZXJyb3IKCm1ha2VbNl06IHN0b3BwZWQgaW4gL3Vzci9z cmMvc3lzL21vZHVsZXMvZHJtL2k5MTUvaTkxNWttcwoKKioqIFthbGxfc3ViZGlyX2RybS9pOTE1 L2k5MTVrbXNdIEVycm9yIGNvZGUgMgoKbWFrZVs1XTogc3RvcHBlZCBpbiAvdXNyL3NyYy9zeXMv bW9kdWxlcy9kcm0vaTkxNQoKMSBlcnJvcgoKbWFrZVs1XTogc3RvcHBlZCBpbiAvdXNyL3NyYy9z eXMvbW9kdWxlcy9kcm0vaTkxNQoKKioqIFthbGxfc3ViZGlyX2RybS9pOTE1XSBFcnJvciBjb2Rl IDIKCm1ha2VbNF06IHN0b3BwZWQgaW4gL3Vzci9zcmMvc3lzL21vZHVsZXMvZHJtCgoxIGVycm9y CgptYWtlWzRdOiBzdG9wcGVkIGluIC91c3Ivc3JjL3N5cy9tb2R1bGVzL2RybQoKKioqIFthbGxf c3ViZGlyX2RybV0gRXJyb3IgY29kZSAyCgptYWtlWzNdOiBzdG9wcGVkIGluIC91c3Ivc3JjL3N5 cy9tb2R1bGVzCgoxIGVycm9yCgptYWtlWzNdOiBzdG9wcGVkIGluIC91c3Ivc3JjL3N5cy9tb2R1 bGVzCgoqKiogW21vZHVsZXMtYWxsXSBFcnJvciBjb2RlIDIKCm1ha2VbMl06IHN0b3BwZWQgaW4g L3Vzci9vYmovdXNyL3NyYy9hbWQ2NC5hbWQ2NC9zeXMvR0VORVJJQwoKMSBlcnJvcgoKbWFrZVsy XTogc3RvcHBlZCBpbiAvdXNyL29iai91c3Ivc3JjL2FtZDY0LmFtZDY0L3N5cy9HRU5FUklDCgoq KiogW2J1aWxka2VybmVsXSBFcnJvciBjb2RlIDIKCm1ha2VbMV06IHN0b3BwZWQgaW4gL3Vzci9z cmMKCjEgZXJyb3IKCm1ha2VbMV06IHN0b3BwZWQgaW4gL3Vzci9zcmMKCioqKiBbYnVpbGRrZXJu ZWxdIEVycm9yIGNvZGUgMgoKbWFrZTogc3RvcHBlZCBpbiAvdXNyL3NyYwoKMSBlcnJvcgoKbWFr ZTogc3RvcHBlZCBpbiAvdXNyL3NyYwoKTXlsYW4= From owner-freebsd-current@freebsd.org Tue Feb 27 02:04: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 37C92F391FC for ; Tue, 27 Feb 2018 02:04:02 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A991F79CE7 for ; Tue, 27 Feb 2018 02:04:01 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.26] (cpe-23-243-164-20.socal.res.rr.com [23.243.164.20]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id b113d121 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Mon, 26 Feb 2018 18:03:54 -0800 (PST) Subject: Re: Compilation failure of the kernel for drm-next To: Mylan Connolly , "freebsd-current@freebsd.org" References: From: Pete Wright Message-ID: Date: Mon, 26 Feb 2018 18:03:54 -0800 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; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 27 Feb 2018 02:04:02 -0000 On 02/26/2018 17:17, Mylan Connolly wrote: > Hello all, > > I'm not sure if this is the best place to send this, but it looks like the issue tracker in Github is a bit dead. there may not be much traffic on it recently, but people are def still actively working on the repository and will see when new issues are reported. as of now your best to to use or test out the drm-next bits is to run a recent 12-CURRENT with no patches applied.  then you can build the port or package via the ports tree under graphics/drm-next-kmod.  it currently runs on my end under 12-CURRENT and 11-STABLE. cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-current@freebsd.org Tue Feb 27 08:51: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 893C4F313E3 for ; Tue, 27 Feb 2018 08:51:48 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from hraggstad.unrelenting.technology (hraggstad.unrelenting.technology [71.19.146.151]) (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 020AF6A18E for ; Tue, 27 Feb 2018 08:51:47 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: by hraggstad.unrelenting.technology (OpenSMTPD) with ESMTPSA id b89df967 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 27 Feb 2018 08:51:33 +0000 (UTC) Subject: Re: Compilation failure of the kernel for drm-next To: Pete Wright , Mylan Connolly , "freebsd-current@freebsd.org" References: From: Greg V Message-ID: Date: Tue, 27 Feb 2018 11:51:30 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.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.25 Precedence: 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, 27 Feb 2018 08:51:48 -0000 On 2/27/2018 5:03 AM, Pete Wright wrote: > > > On 02/26/2018 17:17, Mylan Connolly wrote: >> Hello all, >> >> I'm not sure if this is the best place to send this, but it looks >> like the issue tracker in Github is a bit dead. > > there may not be much traffic on it recently, but people are def still > actively working on the repository and will see when new issues are > reported. > > as of now your best to to use or test out the drm-next bits is to run > a recent 12-CURRENT with no patches applied.  then you can build the > port or package via the ports tree under graphics/drm-next-kmod.  it > currently runs on my end under 12-CURRENT and 11-STABLE. Yeah, and the issue tracker for drm-next-kmod is https://github.com/FreeBSDDesktop/kms-drm/issues NOT https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues From owner-freebsd-current@freebsd.org Tue Feb 27 14:50: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 D10EEF2C36D for ; Tue, 27 Feb 2018 14:50:58 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Received: from mail2.protonmail.ch (mail2.protonmail.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6CD767B4E2 for ; Tue, 27 Feb 2018 14:50:57 +0000 (UTC) (envelope-from mylan.connolly@protonmail.com) Date: Tue, 27 Feb 2018 09:43:40 -0500 To: Greg V From: Mylan Connolly Cc: Pete Wright , "freebsd-current@freebsd.org" Reply-To: Mylan Connolly Subject: Re: Compilation failure of the kernel for drm-next Message-ID: In-Reply-To: References: Feedback-ID: LynW_1UfPsCNIeRmn6VnQX7Jv_J-d7679pwNAQLet51aNK-bYdze1ldqgK4iRhJvu9suK3NkzvrvvdOCSoLZ4w==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 27 Feb 2018 14:50:59 -0000 Thanks for the help, all. Last night I set my computer to compile from the 12-CURRENT head and went t= o sleep. This morning, I installed the graphics/drm-next-kmod port and after a littl= e troubleshooting (I had to set the compat.linuxkpi.enable_hangcheck=3D0 bo= otflag) I got it up and running. The only issue now is I cannot adjust the = backlight. Thanks again for all the help =E2=80=8BMylan =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me= ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 On February 27, 2018 3:51 AM, Greg V wrote: > On 2/27/2018 5:03 AM, Pete Wright wrote: >=20 > > On 02/26/2018 17:17, Mylan Connolly wrote: > >=20 > > > Hello all, > > >=20 > > > I'm not sure if this is the best place to send this, but it looks > > >=20 > > > like the issue tracker in Github is a bit dead. > >=20 > > there may not be much traffic on it recently, but people are def still > >=20 > > actively working on the repository and will see when new issues are > >=20 > > reported. > >=20 > > as of now your best to to use or test out the drm-next bits is to run > >=20 > > a recent 12-CURRENT with no patches applied.=C2=A0 then you can build t= he > >=20 > > port or package via the ports tree under graphics/drm-next-kmod.=C2= =A0 it > >=20 > > currently runs on my end under 12-CURRENT and 11-STABLE. >=20 > Yeah, and the issue tracker for drm-next-kmod is >=20 > https://github.com/FreeBSDDesktop/kms-drm/issues >=20 > NOT https://github.com/FreeBSDDesktop/freebsd-base-graphics/issues From owner-freebsd-current@freebsd.org Wed Feb 28 10:01: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 69B4EF39C35 for ; Wed, 28 Feb 2018 10:01:10 +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 EB1486F291 for ; Wed, 28 Feb 2018 10:01:09 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MSMr9-1fJBhX1bit-00TWBE for ; Wed, 28 Feb 2018 11:01:08 +0100 Date: Wed, 28 Feb 2018 11:01:02 +0100 From: "O. Hartmann" To: freebsd-current Subject: CURRENT: md: g_handleattr: md0 bio_length 24 len 31 -> EFAULT Message-ID: <20180228110102.067cb9f0@freyja.zeit4.iv.bundesimmobilien.de> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:HKmKs9I5OnA9whMFuX43G2eWbJzEC7KL42lXqRVqUp6QD5rptMe POtJk1mdctwfRdmBG/6Tm95zIzm9eO58mxa+vgU8LMYpCe2kgcQudenJwIujpt2QlvAzFEu Bv6uxF9NARBafyzLfBgQCRKZ6lIn7gxwDs/ayazn7nvYb47uPm20RrDkyi6DhczCuXbsxIy DYfQNzmeETIgUXomDTHHA== X-UI-Out-Filterresults: notjunk:1;V01:K0:nru6tLEWh+A=:oc+upupTlIBEbm+yW3VCi8 hh/XVuEIM9c6Q7MIxQ5LrKv9dAHQQau85GBX0ficuR0Niq/ir7d/K4V7uuZOqP8rSBm0+GImE iecd2Z9eSn63XVCYFQEjnhF0TgZlf6/ZpZhHVqwrqtQHQDiDmfnjl1Fyezx96EUZmwOlJ6mGz eYyUfUymGzeWcy2lJ0koKmSGwRNqnuiknGmPZeDEk4Uq5ulQpQQzD6Bi0KpnUQ8GC6rPeRSf/ ZQXuyY6ea3PJx2NT9sNpLqyTnY+Rskfzfs13ANIdKe3OXPEPLZ097kid1YNlzc5JXJzJBfPgd nmTqhqxeS0xwJlA/MxC64pSj+kNaWahmDwkZ9eUCuKAtAsqYCJwU1KWsCgTiDfBGNIfxT+9l7 OH+CCIlINzQ/p+t4PIEzwNNzGn9B4PP3R9dabDvu2T726AmWWIDmjSiJL1gc882WoAwUsVuRq VUE4r+gOyPcKOcM8E3+OPEn30AMW8aSNhiApjeTGmbqQldmbJzAXGjP2DzrfHkQA7EpTbGFYl J5Iw0iwB4cyHAvmxSyEQ5/Bh5rBuR7ahax06tuCORYfql7op5LIMj27nZFsEbC4Lr3xcLARpZ AK1ThARQXx7KTO6A442SI2h6tKnvtrB2C7YJy+ShswFfZtzo+jdA1Q17PcLTSFDeXVJ6Q2LvF 2JIqGwZsb18L4JfGU/ablISfyqgdykiFgGkJdbNShQsL/AKJU3nLJE8MiBaVdqqfWsNlBYCZ0 1GZNwGJCjil1H/Kx7/0IjQ1KVJXXbrr04xu/F4y1oCt1x1M0yzzgyo+Kp9SKF0XETT3IpuB7p mKHfBaD/eYxCtc1BSHN5tfRacbmYVSmKrLtcOOPZ+1Ni0hmhPA= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 10:01:10 -0000 While writing out a md based disk image (NanoBSD) onto a ZFS based filesystem, the console is flooded on CURRENT host (FreeBSD 12.0-CURRENT #78 r330019: Mon Feb 26 16:23:09 CET 2018 amd64) with the message: g_handleattr: md0 bio_length 24 len 31 -> EFAULT Writing out the md image of a size of ~ 2,5 GB to ZFS filesystem takes more than 20 minutes, which is a pain in the arse. ZFS hasn't any neat features enabled or disabled, so deduplication is disabled, atime is off, checksum is sha256 and compression is disabled. The box in question is a Haswell XEON, 6 cores, 3,4 GHz clock and 32 GB RAM - so insufficient performance should not be the issue. What am I doing wrong? Kind regards and thanks in advance, Oliver From owner-freebsd-current@freebsd.org Wed Feb 28 16:54: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 13B1DF34915; Wed, 28 Feb 2018 16:54:08 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from mail.rlwinm.de (mail.rlwinm.de [IPv6:2a01:4f8:171:f902::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A999282805; Wed, 28 Feb 2018 16:54:07 +0000 (UTC) (envelope-from crest@rlwinm.de) Received: from crest.bultmann.eu (unknown [IPv6:2a00:c380:c0d5:1:991d:96fd:2133:4d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.rlwinm.de (Postfix) with ESMTPSA id 19565E995; Wed, 28 Feb 2018 16:53:59 +0000 (UTC) Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Johannes M Dieterich , freebsd-current@freebsd.org, freebsd-stable@freebsd.org References: <20180225104844.726b4f17@manray.ogolem.org> From: Jan Bramkamp Message-ID: Date: Wed, 28 Feb 2018 17:53:58 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180225104844.726b4f17@manray.ogolem.org> 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.25 Precedence: 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, 28 Feb 2018 16:54:08 -0000 On 25.02.18 16:48, Johannes M Dieterich wrote: > Dear all, > > Please CC me as I am not subscribed. > > On behalf of the FreeBSDDesktop team and thanks to the tireless efforts > of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to > report that the graphics/drm-next-kmod port just received an update to > Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent > CURRENT and 11-STABLE. > > We have tested this on a range of hardware ourselves: > * Haswell > * Broadwell > * Skylake > * Evergreen > * Kaveri (both radeon and amgpu KMS) > * Carrizo > * Polaris > > Needless to say, the possible space of hardware this could run on is > significantly larger. Hence, if you find issues and/or want to propose > patches, please do so at our development github: > > https://github.com/FreeBSDDesktop/kms-drm > > We absolutely do welcome contributions! > > Johannes Thx for your hard work. The drm-next-kmod port enabled me to finally replace my ageing Thinkpad X220 with newer hardware. The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod port introduced a regression which causes Xorg on my T470s running 12-current from a few days ago to fail at startup stating that it didn't find any screen. From owner-freebsd-current@freebsd.org Wed Feb 28 17:03: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 385F9F355F5; Wed, 28 Feb 2018 17:03:36 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::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 C07BE83041; Wed, 28 Feb 2018 17:03:35 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: by mail-it0-x242.google.com with SMTP id n7so4253543ita.5; Wed, 28 Feb 2018 09:03:35 -0800 (PST) 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=BavO3sRWuyHIu2bD8tz+i48Y4RHiFXIaKRZLK4r/goM=; b=Y9/PmmyoLO2Cgdc8X5gTxK208q60RgUkhn+vPWAnCFlNsqqauJIiuJC/K3NtBLpXwt 3Oonyl7m7JfRt7lB42RHZGzgkeTSFdBlL2axI4bT0qpG/XHdbTUfev+bkFuBYpVtFINv 6m2aVyMbKmD/+PO7Sjg0b6ipfcZykv1blRRRLU6YyUyvsVjE8Wlngvdl/GzkFXwzgCnt KwyBkJYKPGdtzfoYm9esTfLJDQNkzMQJgSkyCABo2muuclnBqSznXqzCJrSNmbGnalnw 9dkjJF9wWAOA5dDv2dhmn9HiDvk6hW96huWXhsuvKDy5gpzaikRbAjTXxQmpUkTl2ZqX CTgw== 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=BavO3sRWuyHIu2bD8tz+i48Y4RHiFXIaKRZLK4r/goM=; b=JrbJA1blLO8nU+LVM9gXkZF1AW5BpAsOysqILLmT+Lm9A25bzz3mpDwTdkzYeMnKcD v1vO68N6Mu3Vad35dcATzzhS3snnX1PgX7VceD6DupA5FM7tkhRv7HOI3PXWPF6pQgbP LsVJdpWo+lbMyKdyoLHRTA4OpqbFmTTv8aKVJPU2hve0wWqTWwSjw6lpqWiDlm4JeeC7 NcwNHFydrCvaOihuCb0UZep+PP8NFaJFLzEVebmCoh5GdLScALbmEiUNLpR/OVX4THbv ay708MEPfm/AqoykhuHl0rphl+kDIu7jalnL7PAOX0PTO4yvPS1Qc5NFmyhpeEEzqZIl LGLw== X-Gm-Message-State: APf1xPBhSjO4X3qjpVOt/W6BYEWEt18CBPpvp0X1yU7N6ksy/ry3tv60 a0Dm63YRc9aBTzAqRxueItp6UYooP7HzPu8tah4= X-Google-Smtp-Source: AG47ELstxZ/dqoIp2/8Hsi/QhqUZYOe12xAHOzn4iBFp33p/rzkvf/uoCtFMqvBv7xU7oIjrtGLVmF+2SLFwYEWBRlg= X-Received: by 10.36.148.201 with SMTP id j192mr10094219ite.139.1519837414974; Wed, 28 Feb 2018 09:03:34 -0800 (PST) MIME-Version: 1.0 References: <20180225104844.726b4f17@manray.ogolem.org> In-Reply-To: From: Hadi Rezaee Date: Wed, 28 Feb 2018 17:03:24 +0000 Message-ID: Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Jan Bramkamp Cc: Johannes M Dieterich , freebsd-current@freebsd.org, freebsd-stable@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 17:03:36 -0000 Hello there, My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But now it getting failed. Tried to build from source, but same result. Laptop model: Lenovo E470 On Wed, Feb 28, 2018 at 5:56 PM Jan Bramkamp wrote: > On 25.02.18 16:48, Johannes M Dieterich wrote: > > Dear all, > > > > Please CC me as I am not subscribed. > > > > On behalf of the FreeBSDDesktop team and thanks to the tireless efforts > > of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to > > report that the graphics/drm-next-kmod port just received an update to > > Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent > > CURRENT and 11-STABLE. > > > > We have tested this on a range of hardware ourselves: > > * Haswell > > * Broadwell > > * Skylake > > * Evergreen > > * Kaveri (both radeon and amgpu KMS) > > * Carrizo > > * Polaris > > > > Needless to say, the possible space of hardware this could run on is > > significantly larger. Hence, if you find issues and/or want to propose > > patches, please do so at our development github: > > > > https://github.com/FreeBSDDesktop/kms-drm > > > > We absolutely do welcome contributions! > > > > Johannes > > Thx for your hard work. The drm-next-kmod port enabled me to finally > replace my ageing Thinkpad X220 with newer hardware. > > The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod > port introduced a regression which causes Xorg on my T470s running > 12-current from a few days ago to fail at startup stating that it didn't > find any screen. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Wed Feb 28 18:40: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 2DB2FF3BF8C for ; Wed, 28 Feb 2018 18:40:35 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 87FE987012; Wed, 28 Feb 2018 18:40:34 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from creek.local (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 9d45e77a TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 28 Feb 2018 10:40:27 -0800 (PST) Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Jan Bramkamp , Johannes M Dieterich , freebsd-current@freebsd.org References: <20180225104844.726b4f17@manray.ogolem.org> From: Pete Wright Message-ID: Date: Wed, 28 Feb 2018 10:40:26 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 18:40:35 -0000 On 2/28/18 8:53 AM, Jan Bramkamp wrote: > On 25.02.18 16:48, Johannes M Dieterich wrote: >> Dear all, >> >> Please CC me as I am not subscribed. >> >> On behalf of the FreeBSDDesktop team and thanks to the tireless efforts >> of Johannes Lundberg and Hans Petter Selasky (hselasky), I am pleased to >> report that the graphics/drm-next-kmod port just received an update to >> Linux level 4.11 KMS/DRM for amdgpu, radeon, and i915 for both recent >> CURRENT and 11-STABLE. >> >> We have tested this on a range of hardware ourselves: >> * Haswell >> * Broadwell >> * Skylake >> * Evergreen >> * Kaveri (both radeon and amgpu KMS) >> * Carrizo >> * Polaris >> >> Needless to say, the possible space of hardware this could run on is >> significantly larger. Hence, if you find issues and/or want to propose >> patches, please do so at our development github: >> >> https://github.com/FreeBSDDesktop/kms-drm >> >> We absolutely do welcome contributions! >> >> Johannes > > Thx for your hard work. The drm-next-kmod port enabled me to finally > replace my ageing Thinkpad X220 with newer hardware. > > The latest update (g20180117_3 -> 4.11.g20180224) to the drm-next-kmod > port introduced a regression which causes Xorg on my T470s running > 12-current from a few days ago to fail at startup stating that it > didn't find any screen. (removing freebsd-stable@ from this reply since this is a current system) interesting, so Xorg complains about no displays being present if i understand correctly? can you verify that the i915 module is being loaded at boot, kld stat should show something like this: $ kldstat |grep i915  7    1 0xffffffff82f38000 11f615   i915kms.ko If it is present, can you also verify that you are a member of the "video" group?  And failing that it will be helpful to post your dmesg and Xorg.log.0 to help triage this. Cheers, -pete -- Pete Wright pete@nomadlogic.org 310.309.9298 From owner-freebsd-current@freebsd.org Wed Feb 28 18:42: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 9FD37F3C28C for ; Wed, 28 Feb 2018 18:42:16 +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 0804187356; Wed, 28 Feb 2018 18:42:15 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from creek.local (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 57e92492 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 28 Feb 2018 10:42:15 -0800 (PST) Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Hadi Rezaee , Jan Bramkamp Cc: Johannes M Dieterich , freebsd-current@freebsd.org References: <20180225104844.726b4f17@manray.ogolem.org> From: Pete Wright Message-ID: Date: Wed, 28 Feb 2018 10:42:14 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 18:42:16 -0000 On 2/28/18 9:03 AM, Hadi Rezaee wrote: > Hello there, > My laptop is running FreeBSD-12 CURRENT, and i hadnt any problem with my > graphic before upgrading drm-next (g20180117_3 -> 4.11.g20180224). But now > it getting failed. Tried to build from source, but same result. > Laptop model: Lenovo E470 > (removing stable since this is a potential issue on CURRENT) we'll need more details to help triage and hopefully fix this issue.  what errors are you seeing?  are you having problems loading the driver, or is Xorg having issues? -pete -- Pete Wright pete@nomadlogic.org 310.309.9298 From owner-freebsd-current@freebsd.org Wed Feb 28 19:05: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 E70CAF3DA8A for ; Wed, 28 Feb 2018 19:05:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9942888361; Wed, 28 Feb 2018 19:05:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 2223310A87D; Wed, 28 Feb 2018 14:05:52 -0500 (EST) From: John Baldwin To: freebsd-current@freebsd.org, cem@freebsd.org Cc: Ronald Klop Subject: Re: pkg does not recognize correct kernel version Date: Wed, 28 Feb 2018 10:57:53 -0800 Message-ID: <20287587.l4BUZnE1AB@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 28 Feb 2018 14:05:52 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 19:05:59 -0000 On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > > wrote: > > > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > > > > Which man page? I can't find it in pkg help update or pkg help upgrade or > > man pkg. > > I had to dig for quite a while to find a reference (pkg.conf(5)): > > ABI: string The ABI of the package you want to install. Default: > derived from the ABI of the /bin/sh binary. > > >> version note: > >> orion% file /bin/ls > >> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 > >> (1101506), FreeBSD-style, stripped > >> > >> Update world past the __FreeBSD_version which is reported for the > >> repository. > > > > > > Does this mean I always have to do a *clean* buildworld after every version > > bump? This takes ages. > > You could also do a -DNO_CLEAN buildworld. > > Or you can continue to override with "-o OSVERSION=foo", although that > may eventually result in broken packages. In general the OSVERSION is > bumped conservatively (more often than will actually result in > breakage), so you can get away with the easy workaround for a while > between buildworlds. NO_CLEAN=yes doesn't work. A clean buildworld is required. The reason is that the __FreeBSD_version embedded in binaries is stored in /usr/lib/crt*.o, but that the dependency rules in lib/csu/Makefile do not rebuild these .o files everytime changes (so a NO_CLEAN=yes buildworld won't rebuild them leaving them with a stale version). Furthermore, when binaries and shared libraries are built, our Makefiles do not specify that the relevant /usr/lib/crt*.o files are dependencies, so even if we fixed the missing dependency, no binaries would relink to pick up the updated __FreeBSD_version file unless some other input to the binary changed. This one could perhaps be mostly mitigated by forcing libc to depend on the relevant crt*.o files explicitly (or even having it depend on to force relinking of everything when changes). This matters for more than just pkg as the kernel also looks at the embedded __FreeBSD_version in binaries to make decisions about compat shims to enable (grep for P_OSREL in sys/). -- John Baldwin From owner-freebsd-current@freebsd.org Wed Feb 28 19:46:00 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B9134F406F8 for ; Wed, 28 Feb 2018 19:46: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 3BAB88A031; Wed, 28 Feb 2018 19:46: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 ESMTPS id w1SJjlgJ070573 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 28 Feb 2018 21:45:50 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w1SJjlgJ070573 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w1SJjl7H070572; Wed, 28 Feb 2018 21:45:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 28 Feb 2018 21:45:47 +0200 From: Konstantin Belousov To: John Baldwin Cc: freebsd-current@freebsd.org, cem@freebsd.org, Ronald Klop Subject: Re: pkg does not recognize correct kernel version Message-ID: <20180228194547.GA7123@kib.kiev.ua> References: <20287587.l4BUZnE1AB@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20287587.l4BUZnE1AB@ralph.baldwin.cx> User-Agent: Mutt/1.9.3 (2018-01-21) 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.25 Precedence: 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, 28 Feb 2018 19:46:01 -0000 On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote: > On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > > > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > > > wrote: > > > > > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > > > > > > > Which man page? I can't find it in pkg help update or pkg help upgrade or > > > man pkg. > > > > I had to dig for quite a while to find a reference (pkg.conf(5)): > > > > ABI: string The ABI of the package you want to install. Default: > > derived from the ABI of the /bin/sh binary. > > > > >> version note: > > >> orion% file /bin/ls > > >> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > > >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 > > >> (1101506), FreeBSD-style, stripped > > >> > > >> Update world past the __FreeBSD_version which is reported for the > > >> repository. > > > > > > > > > Does this mean I always have to do a *clean* buildworld after every version > > > bump? This takes ages. > > > > You could also do a -DNO_CLEAN buildworld. > > > > Or you can continue to override with "-o OSVERSION=foo", although that > > may eventually result in broken packages. In general the OSVERSION is > > bumped conservatively (more often than will actually result in > > breakage), so you can get away with the easy workaround for a while > > between buildworlds. > > NO_CLEAN=yes doesn't work. A clean buildworld is required. The reason is that > the __FreeBSD_version embedded in binaries is stored in /usr/lib/crt*.o, but > that the dependency rules in lib/csu/Makefile do not rebuild these .o files > everytime changes (so a NO_CLEAN=yes buildworld won't rebuild them > leaving them with a stale version). Furthermore, when binaries and shared > libraries are built, our Makefiles do not specify that the relevant > /usr/lib/crt*.o files are dependencies, so even if we fixed the missing > dependency, no binaries would relink to pick up the updated > __FreeBSD_version file unless some other input to the binary changed. This > one could perhaps be mostly mitigated by forcing libc to depend on the > relevant crt*.o files explicitly (or even having it depend on > to force relinking of everything when changes). libc already depends on sys/param.h. I think it would be enough to specify that crt1.o depends on sys/param.h as well. Although it is also strange, because e.g. for amd64 the dep thread is csu/amd64/crt1.c->csu/common/crtbrand.c->sys/param.h, which should be detected by the include file calculation. > > This matters for more than just pkg as the kernel also looks at the embedded > __FreeBSD_version in binaries to make decisions about compat shims to enable > (grep for P_OSREL in sys/). > > -- > John Baldwin > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@freebsd.org Wed Feb 28 22:42: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 0B3BFF29C54 for ; Wed, 28 Feb 2018 22:42:31 +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 6E73C69E3F; Wed, 28 Feb 2018 22:42:30 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from creek.local (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id f62af8f2 TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 28 Feb 2018 14:42:23 -0800 (PST) Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Hadi Rezaee Cc: Jan Bramkamp , Johannes M Dieterich , freebsd-current@freebsd.org References: <20180225104844.726b4f17@manray.ogolem.org> From: Pete Wright Message-ID: <421c2bbc-6ffe-a771-ab23-26395f51ca6f@nomadlogic.org> Date: Wed, 28 Feb 2018 14:42:23 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 22:42:31 -0000 On 2/28/18 2:30 PM, Hadi Rezaee wrote: > Hello Pete, sorry I’m on trip so i cannot output the logs in proper > way. About i915 kernel module please refer to screen shot.  > > I can confirm that i915 module is not getting loaded normaly at system > startup, so kldstat shows nothing.  > > Yes, the user is already in video group. (Generally didnt changed > anything on system config, just updated pkg and this happend) thanks for posting the screen shot - it looks like your kernel and world may not be recent enough to load the kld.  i'd suggest pulling the latest code from svn or git for 12-CURRENT then removing and reinstalling the drm-next-kmod pkg after you have booted into this fresh checkout. that's the first thing that comes to my mind when seeing that your kernel is unable to handle these modules.  you also may want to remove the drm-next-kmod package and ensure there are no artifacts left behind in /boot/modules/ that were installed via the pkg, then re-install from the upstream pkg servers. hope this helps, -pete -- Pete Wright pete@nomadlogic.org 310.309.9298 From owner-freebsd-current@freebsd.org Wed Feb 28 22:47: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 83FC3F2A148 for ; Wed, 28 Feb 2018 22:47:13 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::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 C51D46A134; Wed, 28 Feb 2018 22:47:12 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: by mail-io0-x229.google.com with SMTP id e30so5038127ioc.3; Wed, 28 Feb 2018 14:47:12 -0800 (PST) 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=qUCxwt9FlVTvptiIO7SkWJ+wcx0ndEHxRZElS3FFUGk=; b=G76vpSWVivZmZDA85JDmonKJEJ15pTaRIGevn/lTpPVmYHMDQ3Z4RiOyU5Gb4i64PX mMCiF0fi2lK7zAYEstTDVZ32aiS0IH9DUf/+z6WN5uO/uylF8qxqR/ee+D5VMLpzZN34 psvj2FLg9q8mdH8Cogw/Aeu5orNOV8TI3oFkgfz//7z5zhBEN0EdgDMMZ6tbMU98gUAH jK8ZVQPxLVYbigmjfZS4LeyIQMPmtf+8mpQ6s8rdnb424+JL1PJRhSRY1D48DgUNHRze msG8E9w9LKhHt75nMpx431gmJZh53DAf7wy7cffrDe0BO0qY9vBspthUbAStObP6Hyb+ QJxg== 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=qUCxwt9FlVTvptiIO7SkWJ+wcx0ndEHxRZElS3FFUGk=; b=XiwkXjDEiexA3SXdDMwWpXRaZaD35dDV2l411AxgiKjSTMd1k4qxsvuEh4Qx432fU3 +khpF1oiWI73VB++UJMHrFK5F376mxH7rv3JjRCYkiugtIutQSCNSZ3V6t4xLtZr/6lC w8r2Sfr6kaZm48RfEJngEog88kRfZRZ/M4bfzxpSldlYGsLBMIUj08KN+BFwJQ9mygi9 95gvLSqUfK5aRKY/skHKPlBFGqTT5OSBM21fJwseufokA4bfg87GSna6nA/5vxf//sI/ xc9jsRyf8o7FIh1YjlhD659GgHt8JFxA+mbuTjvzhEOs4IBMze+5yh2tu7LjcyAZ2PIb 4SRg== X-Gm-Message-State: APf1xPDQzLh8bjgg/P/Pi2j/GxaHSOzHjScjpNjYTc/KUYuie/SWxmUP Bqzzio2Elq6/Fwih/VvXe2fJ+JC6H4tOHVjGD5ZkSg== X-Google-Smtp-Source: AG47ELvKV1N+JLk8W89IWSoS0Pd0tFebiJc5k+xxfzluErU/+yN/v3npcboBRni36aOi2Z6jYxJFZQNn3Yzvh3lD48Y= X-Received: by 10.107.174.27 with SMTP id x27mr20875968ioe.27.1519858032140; Wed, 28 Feb 2018 14:47:12 -0800 (PST) MIME-Version: 1.0 References: <20180225104844.726b4f17@manray.ogolem.org> <421c2bbc-6ffe-a771-ab23-26395f51ca6f@nomadlogic.org> In-Reply-To: <421c2bbc-6ffe-a771-ab23-26395f51ca6f@nomadlogic.org> From: Hadi Rezaee Date: Wed, 28 Feb 2018 22:47:01 +0000 Message-ID: Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Pete Wright Cc: Jan Bramkamp , Johannes M Dieterich , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 22:47:13 -0000 Thanks Pete, i=E2=80=99ll try your solution. But just wanted to report back= the system current revision: r329639 On Wed, Feb 28, 2018 at 11:42 PM Pete Wright wrote: > > > On 2/28/18 2:30 PM, Hadi Rezaee wrote: > > Hello Pete, sorry I=E2=80=99m on trip so i cannot output the logs in pr= oper > > way. About i915 kernel module please refer to screen shot. > > > > I can confirm that i915 module is not getting loaded normaly at system > > startup, so kldstat shows nothing. > > > > Yes, the user is already in video group. (Generally didnt changed > > anything on system config, just updated pkg and this happend) > > thanks for posting the screen shot - it looks like your kernel and world > may not be recent enough to load the kld. i'd suggest pulling the > latest code from svn or git for 12-CURRENT then removing and > reinstalling the drm-next-kmod pkg after you have booted into this fresh > checkout. > > that's the first thing that comes to my mind when seeing that your > kernel is unable to handle these modules. you also may want to remove > the drm-next-kmod package and ensure there are no artifacts left behind > in /boot/modules/ that were installed via the pkg, then re-install from > the upstream pkg servers. > > hope this helps, > -pete > > -- > Pete Wright > pete@nomadlogic.org > 310.309.9298 > > From owner-freebsd-current@freebsd.org Wed Feb 28 23:11: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 B052EF2BCDD for ; Wed, 28 Feb 2018 23:11:41 +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 1A7C76AF6D; Wed, 28 Feb 2018 23:11:41 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from creek.local (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3d00d0cf TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 28 Feb 2018 15:11:39 -0800 (PST) Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Hadi Rezaee Cc: Jan Bramkamp , Johannes M Dieterich , freebsd-current@freebsd.org References: <20180225104844.726b4f17@manray.ogolem.org> <421c2bbc-6ffe-a771-ab23-26395f51ca6f@nomadlogic.org> From: Pete Wright Message-ID: <0ea32620-aa3d-9dbf-17da-c07f421ca512@nomadlogic.org> Date: Wed, 28 Feb 2018 15:11:39 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 23:11:41 -0000 On 2/28/18 2:47 PM, Hadi Rezaee wrote: > Thanks Pete, i’ll try your solution. But just wanted to report back > the system current revision: r329639 > > sounds great, let me know how it looks. i suggest we move the rest of this discussion to the freebsd-x11@freebsd.org list so we don't SPAM the -current list. cheers! -pete -- Pete Wright pete@nomadlogic.org 310.309.9298 From owner-freebsd-current@freebsd.org Wed Feb 28 23:59: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 9F918F2EBD8 for ; Wed, 28 Feb 2018 23:59:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4B8CD6C8C4; Wed, 28 Feb 2018 23:59:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 681AB10A87D; Wed, 28 Feb 2018 18:59:43 -0500 (EST) From: John Baldwin To: Konstantin Belousov Cc: freebsd-current@freebsd.org, cem@freebsd.org, Ronald Klop Subject: Re: pkg does not recognize correct kernel version Date: Wed, 28 Feb 2018 15:32:43 -0800 Message-ID: <1796463.2W2Te48fqL@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180228194547.GA7123@kib.kiev.ua> References: <20287587.l4BUZnE1AB@ralph.baldwin.cx> <20180228194547.GA7123@kib.kiev.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Wed, 28 Feb 2018 18:59:43 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 28 Feb 2018 23:59:45 -0000 On Wednesday, February 28, 2018 09:45:47 PM Konstantin Belousov wrote: > On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote: > > On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > > > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > > > > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > > > > wrote: > > > > > > > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > > > > > > > > > > Which man page? I can't find it in pkg help update or pkg help upgrade or > > > > man pkg. > > > > > > I had to dig for quite a while to find a reference (pkg.conf(5)): > > > > > > ABI: string The ABI of the package you want to install. Default: > > > derived from the ABI of the /bin/sh binary. > > > > > > >> version note: > > > >> orion% file /bin/ls > > > >> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > > > >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 > > > >> (1101506), FreeBSD-style, stripped > > > >> > > > >> Update world past the __FreeBSD_version which is reported for the > > > >> repository. > > > > > > > > > > > > Does this mean I always have to do a *clean* buildworld after every version > > > > bump? This takes ages. > > > > > > You could also do a -DNO_CLEAN buildworld. > > > > > > Or you can continue to override with "-o OSVERSION=foo", although that > > > may eventually result in broken packages. In general the OSVERSION is > > > bumped conservatively (more often than will actually result in > > > breakage), so you can get away with the easy workaround for a while > > > between buildworlds. > > > > NO_CLEAN=yes doesn't work. A clean buildworld is required. The reason is that > > the __FreeBSD_version embedded in binaries is stored in /usr/lib/crt*.o, but > > that the dependency rules in lib/csu/Makefile do not rebuild these .o files > > everytime changes (so a NO_CLEAN=yes buildworld won't rebuild them > > leaving them with a stale version). Furthermore, when binaries and shared > > libraries are built, our Makefiles do not specify that the relevant > > /usr/lib/crt*.o files are dependencies, so even if we fixed the missing > > dependency, no binaries would relink to pick up the updated > > __FreeBSD_version file unless some other input to the binary changed. This > > one could perhaps be mostly mitigated by forcing libc to depend on the > > relevant crt*.o files explicitly (or even having it depend on > > to force relinking of everything when changes). > libc already depends on sys/param.h. Hmm, even when I removed /usr/obj/usr/src/lib/csu entirely and then did a buildworld NO_CLEAN=yes recently /bin/sh was not relinked, though perhaps at that point libc already thought it was up-to-date relative to from the previous build. > I think it would be enough to specify that crt1.o depends on sys/param.h > as well. Although it is also strange, because e.g. for amd64 the dep > thread is csu/amd64/crt1.c->csu/common/crtbrand.c->sys/param.h, which should > be detected by the include file calculation. I think the detour via assembly + sed is what breaks the dependency chain. FWIW, I found that on at least MIPS with clang I did not need the SED_FIX_NOTE hack. -- John Baldwin From owner-freebsd-current@freebsd.org Thu Mar 1 12:03: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 3EBD8F41C1F for ; Thu, 1 Mar 2018 12:03:10 +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 9F1947F8C1; Thu, 1 Mar 2018 12:03:09 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kib@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w21C2wFC023962 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 1 Mar 2018 14:03:01 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w21C2wFC023962 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id w21C2wCp023961; Thu, 1 Mar 2018 14:02:58 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Thu, 1 Mar 2018 14:02:58 +0200 From: Konstantin Belousov To: John Baldwin Cc: freebsd-current@freebsd.org, cem@freebsd.org, Ronald Klop Subject: Re: pkg does not recognize correct kernel version Message-ID: <20180301120257.GB3194@kib.kiev.ua> References: <20287587.l4BUZnE1AB@ralph.baldwin.cx> <20180228194547.GA7123@kib.kiev.ua> <1796463.2W2Te48fqL@ralph.baldwin.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1796463.2W2Te48fqL@ralph.baldwin.cx> User-Agent: Mutt/1.9.3 (2018-01-21) 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.25 Precedence: 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, 01 Mar 2018 12:03:10 -0000 On Wed, Feb 28, 2018 at 03:32:43PM -0800, John Baldwin wrote: > On Wednesday, February 28, 2018 09:45:47 PM Konstantin Belousov wrote: > > On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote: > > > On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > > > > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > > > > > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > > > > > wrote: > > > > > > > > > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > > > > > > > > > > > > > Which man page? I can't find it in pkg help update or pkg help upgrade or > > > > > man pkg. > > > > > > > > I had to dig for quite a while to find a reference (pkg.conf(5)): > > > > > > > > ABI: string The ABI of the package you want to install. Default: > > > > derived from the ABI of the /bin/sh binary. > > > > > > > > >> version note: > > > > >> orion% file /bin/ls > > > > >> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > > > > >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 > > > > >> (1101506), FreeBSD-style, stripped > > > > >> > > > > >> Update world past the __FreeBSD_version which is reported for the > > > > >> repository. > > > > > > > > > > > > > > > Does this mean I always have to do a *clean* buildworld after every version > > > > > bump? This takes ages. > > > > > > > > You could also do a -DNO_CLEAN buildworld. > > > > > > > > Or you can continue to override with "-o OSVERSION=foo", although that > > > > may eventually result in broken packages. In general the OSVERSION is > > > > bumped conservatively (more often than will actually result in > > > > breakage), so you can get away with the easy workaround for a while > > > > between buildworlds. > > > > > > NO_CLEAN=yes doesn't work. A clean buildworld is required. The reason is that > > > the __FreeBSD_version embedded in binaries is stored in /usr/lib/crt*.o, but > > > that the dependency rules in lib/csu/Makefile do not rebuild these .o files > > > everytime changes (so a NO_CLEAN=yes buildworld won't rebuild them > > > leaving them with a stale version). Furthermore, when binaries and shared > > > libraries are built, our Makefiles do not specify that the relevant > > > /usr/lib/crt*.o files are dependencies, so even if we fixed the missing > > > dependency, no binaries would relink to pick up the updated > > > __FreeBSD_version file unless some other input to the binary changed. This > > > one could perhaps be mostly mitigated by forcing libc to depend on the > > > relevant crt*.o files explicitly (or even having it depend on > > > to force relinking of everything when changes). > > libc already depends on sys/param.h. > > Hmm, even when I removed /usr/obj/usr/src/lib/csu entirely and then did a buildworld > NO_CLEAN=yes recently /bin/sh was not relinked, though perhaps at that point > libc already thought it was up-to-date relative to from the previous > build. > > > I think it would be enough to specify that crt1.o depends on sys/param.h > > as well. Although it is also strange, because e.g. for amd64 the dep > > thread is csu/amd64/crt1.c->csu/common/crtbrand.c->sys/param.h, which should > > be detected by the include file calculation. > > I think the detour via assembly + sed is what breaks the dependency chain. > FWIW, I found that on at least MIPS with clang I did not need the SED_FIX_NOTE > hack. Perhaps the FIX_NOTE should be re-evaluated for all the changes happen in the toolchains since the hack was needed. From owner-freebsd-current@freebsd.org Thu Mar 1 20:26:32 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9718F269E6 for ; Thu, 1 Mar 2018 20:26:32 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 3CAAE7888F; Thu, 1 Mar 2018 20:26:32 +0000 (UTC) (envelope-from rezaee.hadi@gmail.com) Received: by mail-io0-x230.google.com with SMTP id f1so8510515iob.0; Thu, 01 Mar 2018 12:26:32 -0800 (PST) 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 :cc; bh=+h6OdMOy41nzUvBlKtVyXQkVOjMHeHGXPA6u2gG3fg0=; b=p1F3AyqkpT8FfYnP/RQXlKErm311m5eh0Q+3DEy0Hd5dzStsov0WeD4f+W5hDfqetl xu0ZmI1+fWtH/FaziLgh/VE33QCDXf0scrT0kZCojJG3uJLybpa3t3Boev2ztQkb/z86 8EFOElamLGtCpnJYR9G3h3A+GoyL/YOAYB7wrDe4qOZHFs6Bc3SRSPiHZRh/cKQ0YDnR 6m1ajNp/hZOWHFolhHwOr/nSSIFvB/1Mm4v4DBlaKZmFVriGsHrgFcZJLUBPMAJSX2ay FxATs8m2O0yTQQ4w4DKWK/hK/SqLWxNFy8vCUMLR0eg2HV20g0JwWqYKmeVxEuQtkBxQ LHKA== 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=+h6OdMOy41nzUvBlKtVyXQkVOjMHeHGXPA6u2gG3fg0=; b=sZh8uhhMwloaSOmzZMbizKryBt+d8xBITq47P6BNp9FZu9BtbIfWyxLr2xBXtzts5d jZW9YUX2cwG8wizSH7ftnI2758Sr9IRW2GOztj84WtUkF8t3N+Uv4Gg5oPnJ9zsjuYUL gGY/0K71qYcXyUdbPjigee7Zj8AwIppnwrNkpxhLDSDD8anaibhZGzn/MjX1/+pjV1Bj qc9r7Wv4F9eGiG43OAprajs3Z2Y9GTZksD7Ae41agVY5U8vJpPLL/Wx3MpGpmSu3DDLA Op+VuvzaKa+igP+4u3RsESn0gZXAwhx11d0ImYGY+zTkRE2D25B+bHuAKQUBtnuaM76F 00Ig== X-Gm-Message-State: APf1xPDCHiMJyc5ix2qsEVCpsUJxVYwYzZPigvbOClLKMuXyXthSSTkk uq5/X497o4bwgp/ZL7HywZfukocxYy68yLVbu4g= X-Google-Smtp-Source: AG47ELvXi+3HlOV4p7LJMlrrtZG05t3rwozKFWXpo3WQkphAGLK8rr+kae1FGGfwa59RAKz1hl2QjL/LqZjzvbssiwM= X-Received: by 10.107.222.10 with SMTP id v10mr3614615iog.267.1519935991436; Thu, 01 Mar 2018 12:26:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.161.146 with HTTP; Thu, 1 Mar 2018 12:26:11 -0800 (PST) In-Reply-To: <0ea32620-aa3d-9dbf-17da-c07f421ca512@nomadlogic.org> References: <20180225104844.726b4f17@manray.ogolem.org> <421c2bbc-6ffe-a771-ab23-26395f51ca6f@nomadlogic.org> <0ea32620-aa3d-9dbf-17da-c07f421ca512@nomadlogic.org> From: Hadi Rezaee Date: Thu, 1 Mar 2018 23:56:11 +0330 Message-ID: Subject: Re: update of graphics/drm-next-kmod to Linux 4.11 level for recent CURRENT and 11-STABLE To: Pete Wright Cc: Jan Bramkamp , Johannes M Dieterich , freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 01 Mar 2018 20:26:33 -0000 Hey Pete, Thanks for the help, updated to newer revision (r330133) and it resolved the problem :) On Thu, Mar 1, 2018 at 2:41 AM, Pete Wright wrote: > > > On 2/28/18 2:47 PM, Hadi Rezaee wrote: > > Thanks Pete, i=E2=80=99ll try your solution. But just wanted to report = back > > the system current revision: r329639 > > > > > sounds great, let me know how it looks. > > i suggest we move the rest of this discussion to the > freebsd-x11@freebsd.org list so we don't SPAM the -current list. > > cheers! > -pete > > -- > Pete Wright > pete@nomadlogic.org > 310.309.9298 > > From owner-freebsd-current@freebsd.org Fri Mar 2 09:34: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 D640CF33FDD for ; Fri, 2 Mar 2018 09:34:42 +0000 (UTC) (envelope-from tobik@FreeBSD.org) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (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 890A3773EA for ; Fri, 2 Mar 2018 09:34:42 +0000 (UTC) (envelope-from tobik@FreeBSD.org) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 9938420DCC for ; Fri, 2 Mar 2018 04:34:41 -0500 (EST) Received: from web5 ([10.202.2.215]) by compute4.internal (MEProxy); Fri, 02 Mar 2018 04:34:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=y34pT6MMhpxjvhfKbJnct1gLFa5EH kZrd2NA0X8Eldc=; b=Zl7S9GIsEL1jVSJp2f+kS8KZ+jrVK15VUYqN8hA4VgxkN 5nKyD42ZRXpStErwE4L6u0JeWXk43Fru1NR3SbGYTL6SXID/nbqyJXm70V8K3j2W 8GKgMNyam+aYmYR4fwIAB6K4Iq3AP8wUrQ3G3TzHe+JBvOTPjhL6U96XUb/WseZw xAJrf9y4cz85zzmMMuwHYYV+ySiDITJprfSZAXkG0ReUeam29hliD5hVh1hWr34Z 3IgsUcBL2khnTWH7bnKQy+UP/YhXoKXLc66jBMnjJ/9qjOK/qdOSuyXOkg9TbzbZ JeIZHtUOH0YnPyqNhJQajeYdG+rXSDoEqoRsmgSNg== X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 7D9CE9E21F; Fri, 2 Mar 2018 04:34:41 -0500 (EST) Message-Id: <1519983281.528132.1288885120.3C05D54E@webmail.messagingengine.com> From: Tobias Kortkamp To: freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-b08ff009 Subject: Conflict between FreeBSD-binutils and FreeBSD-lld packages Date: Fri, 02 Mar 2018 10:34:41 +0100 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 09:34:43 -0000 Building pkgbase packages with r330236 results in FreeBSD-binutils and FreeBSD-lld packages conflicting with each other. Both want to install /usr/share/man/man1/ld.1.gz For now I'm working around it by manually extracting FreeBSD-lld. FreeBSD-binutils should install its man page as ld.bfd.1.gz if lld is the set as the default linker via WITH_LLD_IS_LD. From owner-freebsd-current@freebsd.org Fri Mar 2 12:06: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 880C3F3F7C5 for ; Fri, 2 Mar 2018 12:06:41 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::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 1FD437D105; Fri, 2 Mar 2018 12:06:41 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mail-qk0-x230.google.com with SMTP id z197so11581183qkb.6; Fri, 02 Mar 2018 04:06:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:to:cc:from:subject:message-id:date:user-agent:mime-version; bh=V/DCpkmuLC3YuZjQr8kezOR4reH0IUE2J7zb+bcA5vc=; b=pevQVAzocOla1Chhpoxrp7BeIxYpOEtIb39r2BxV2YiKvCrlWYdaauJDIWFEkkFb3U qqJnMSPy4pySienpMF3eNJUGqDSf02lJu/uBXw951ftlcygi3njRDIlCZLWKOpRJKDrl m1npdmopxAu44bAkjbj8O7T+fCyOaCAANUcL2cgesWRGBa4CVRiMrZ1IPrEtpyLOCaER KiN5eov+6ntsbXGn/YBaCKv8fpMPKHT70gU43WddhE8dK74waBF0RfAqVz70GWZQiT8y YBzCGQ248+YZrFDXBw0Bm4cUMIEGujJtfgCveAMBd/RUgzjQgeZd/wQGKcXih6XyIu8s N92g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:cc:from:subject:message-id:date :user-agent:mime-version; bh=V/DCpkmuLC3YuZjQr8kezOR4reH0IUE2J7zb+bcA5vc=; b=h1kxf7TS4CurbrusI+r9HDvcI9fwYzhBpnGUi9HASqN8xHIO0MdGW/NFwXT4VaFBf3 fLhhXVxBL9hRJPHL3lujM15RV6DhRpMNEk7+/nxQ84Zvu4yFbV39+5G9i6Do9inq+eSJ Qih+fiR5wSSrXfJ2bymAcDnOOa//BKpjjAysyFd4vBIgD1uxe91ueG4oOo2XDOcGErmK 6DD6JnQL2lyDQr9MUkmnnHQAdU6MyYuUFABWTxOo+SfqrT0uiQDkP/I743EeCKKmLsYc Q/+kR4TG3bpzwcSqEU6KeeCuMxlv+Sm9NQvTCLzniIfvgDZilY7QZ+sqTktloNScWaXt hkKw== X-Gm-Message-State: AElRT7H21OJftfPruJs2VWa9vdW5OAyw+69+L4YnzUpyvhb1QwN7c+RB kdsDLgv3iM7Ha53R0C4Dz0GcRYjh X-Google-Smtp-Source: AG47ELtFcoegjbzkGUHCpT+4qEfK2NxPxDV4TxrYw/wfyEqW3GA8NnWFVHgXRggWm7RaI1LYg0xYrA== X-Received: by 10.55.214.130 with SMTP id p2mr8023742qkl.304.1519992400324; Fri, 02 Mar 2018 04:06:40 -0800 (PST) Received: from mbp.home ([177.53.86.172]) by smtp.gmail.com with ESMTPSA id d30sm4587151qte.46.2018.03.02.04.06.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 04:06:39 -0800 (PST) Sender: Renato Botelho To: kevans@freebsd.org Cc: FreeBSD Current From: Renato Botelho Subject: Question mark on Lua menu box Message-ID: Date: Fri, 2 Mar 2018 09:06:34 -0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="u9fR1XbsWIiHrwtmDmQkmsOnaCuIAWFUd" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 12:06:41 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --u9fR1XbsWIiHrwtmDmQkmsOnaCuIAWFUd Content-Type: multipart/mixed; boundary="omt8MIHqWhwhCS6dozgFomM3JJrB2Oo8m"; protected-headers="v1" From: Renato Botelho To: kevans@freebsd.org Cc: FreeBSD Current Message-ID: Subject: Question mark on Lua menu box --omt8MIHqWhwhCS6dozgFomM3JJrB2Oo8m Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Kyle, I've moved to Lua loader to help testing and it worked fine. The only odd thing I noted is the menu box with odd chars as you can see at [1]. My laptop is running a recent current (r330275) with ZFS and UEFI. [1] https://imgur.com/a/kIQ0O --=20 Renato Botelho --omt8MIHqWhwhCS6dozgFomM3JJrB2Oo8m-- --u9fR1XbsWIiHrwtmDmQkmsOnaCuIAWFUd Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEExxiLNMqsn7yXmTy7W54Ew5ZrhhoFAlqZPktfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEM3 MTg4QjM0Q0FBQzlGQkM5Nzk5M0NCQjVCOUUwNEMzOTY2Qjg2MUEACgkQW54Ew5Zr hhr3pgf+NVq9nhu6sjTYVed0/8L8DAjaxgV2iyLbrU68ZlYSPTt/fveAo3Vu1G8Q R8Zr6JPrfT6nuorgZzIDlv4r718kBg+nGbYiNseT2j99r5/yPNjM0+fJL4elYMpS oBJ2W4LdU2WQ2r3vS/zJ4n6Xx36o4jpqWWlYJTa9V1V8AM+iiyIOVELEWeCesC+B JcRd5X7MeMxT3glKK3Qe8w7y6P7049BMtMjzh9wza0IbZLPd9Wk1LIkQTHpw6fAu sdvP11j6eLMvHO16VNY1WB6FsRj9N7mibu6vxo9zwq8IFoL9BQfGi44WiDYDoDx0 SvPJjcsuxZUQU9iW3vtf54i95T8FvA== =90jh -----END PGP SIGNATURE----- --u9fR1XbsWIiHrwtmDmQkmsOnaCuIAWFUd-- From owner-freebsd-current@freebsd.org Fri Mar 2 13:02: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 71115F439D0 for ; Fri, 2 Mar 2018 13:02:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 0B1187F7BD for ; Fri, 2 Mar 2018 13:02:48 +0000 (UTC) (envelope-from david@catwhisker.org) Received: by mailman.ysv.freebsd.org (Postfix) id BECBBF439CF; Fri, 2 Mar 2018 13:02:47 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7EF4AF439CD for ; Fri, 2 Mar 2018 13:02:47 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from mx.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFA6A7F7BB for ; Fri, 2 Mar 2018 13:02:46 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id w22D2jNq059000 for ; Fri, 2 Mar 2018 13:02:45 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id w22D2ibv058999; Fri, 2 Mar 2018 05:02:44 -0800 (PST) (envelope-from david) Date: Fri, 2 Mar 2018 05:02:44 -0800 From: David Wolfskill To: current@freebsd.org Subject: Possible race in buildworld, @r330236 -> @r330274 Message-ID: <20180302130244.GI1144@albert.catwhisker.org> Mail-Followup-To: David Wolfskill , current@freebsd.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="U+z1uOwmvmmbFBAc" Content-Disposition: inline User-Agent: Mutt/1.9.3 (2018-01-21) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 13:02:48 -0000 --U+z1uOwmvmmbFBAc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On the two machines where I track head daily, I had failures during "make buildworld" ... in different places on the two machines; re-trying the build succeeded (in each case). Lately, I have (also) been tracking head on these machines with /etc/src.conf augmented with: # For Lua loader experiments WITHOUT_FORTH=3Dyes WITH_LOADER_LUA=3Dyes (on a separate slice, so each machine is booted to that environment and an upgrade-in-place build is done). Curiously, no failures were observed in the case where he Lua loader is being used & built. (I am explicitly NOT claiming any causal relationship here.) I have copied the build typescripts for each combination of machine and boot loader, together with the associated /etc/make.conf, src.conf, and src-env.conf for each to my Web server. The build typescripts also have compressed copies -- the Web server is on the "consumer" end of a residential ADSL: it works, but it's not fast. For the above-cited material, please see ; here's what's there: albert(11.1-S)[9] ls -lhRT total 1 drwxr-xr-x 4 david staff 4B Mar 2 04:36:15 2018 Forth drwxr-xr-x 4 david staff 4B Mar 2 04:36:15 2018 Lua =2E/Forth: total 33 drwxr-xr-x 2 david staff 7B Mar 2 04:49:55 2018 freebeast drwxr-xr-x 2 david staff 7B Mar 2 04:49:57 2018 laptop =2E/Forth/freebeast: total 1609 -rw-r--r-- 1 david staff 5.4M Mar 2 04:11:28 2018 build.txt -rw-r--r-- 1 david staff 351K Mar 2 04:11:28 2018 build.txt.bz2 -r--r--r-- 1 david staff 108B Feb 4 10:01:28 2014 make.conf -r--r--r-- 1 david staff 19B May 24 10:28:11 2017 src-env.conf -r--r--r-- 1 david staff 48B Mar 22 04:35:38 2016 src.conf =2E/Forth/laptop: total 1865 -rw-r--r-- 1 david staff 6.1M Mar 2 04:11:29 2018 build.txt -rw-r--r-- 1 david staff 403K Mar 2 04:11:29 2018 build.txt.bz2 -r--r--r-- 1 david staff 503B Jul 30 03:55:27 2017 make.conf -r--r--r-- 1 david staff 19B May 30 04:15:48 2016 src-env.conf -r--r--r-- 1 david staff 197B Jul 8 02:58:12 2017 src.conf =2E/Lua: total 33 drwxr-xr-x 2 david staff 7B Mar 2 04:49:59 2018 freebeast drwxr-xr-x 2 david staff 7B Mar 2 04:50:00 2018 laptop =2E/Lua/freebeast: total 1529 -rw-r--r-- 1 david staff 5.1M Mar 2 04:37:38 2018 build.txt -rw-r--r-- 1 david staff 337K Mar 2 04:37:38 2018 build.txt.bz2 -r--r--r-- 1 david staff 108B Feb 4 10:01:28 2014 make.conf -r--r--r-- 1 david staff 19B May 24 10:28:11 2017 src-env.conf -r--r--r-- 1 david staff 115B Feb 13 05:39:36 2018 src.conf =2E/Lua/laptop: total 1545 -rw-r--r-- 1 david staff 5.1M Mar 2 04:28:53 2018 build.txt -rw-r--r-- 1 david staff 341K Mar 2 04:28:53 2018 build.txt.bz2 -r--r--r-- 1 david staff 503B Jul 30 03:55:27 2017 make.conf -r--r--r-- 1 david staff 19B May 30 04:15:48 2016 src-env.conf -r--r--r-- 1 david staff 264B Feb 13 06:09:49 2018 src.conf albert(11.1-S)[10]=20 (Files were copied with -p; I thought having timestamps that showed when they actually were last modified make be of some use.) Peace, david --=20 David H. Wolfskill david@catwhisker.org Yes, the indictments don't "prove" guilt; that's what trials are for. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --U+z1uOwmvmmbFBAc Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEzLfO+ReoAfQwZNd7FTnMQKBJ7hcFAlqZS3RfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEND QjdDRUY5MTdBODAxRjQzMDY0RDc3QjE1MzlDQzQwQTA0OUVFMTcACgkQFTnMQKBJ 7hfuwwf/WAKVopcYzImZhnBGju3A/W7RB2uiTzA8lzjUiZKBsCpT9QGQfsBSF+4K DhTEda8lGcaX1UTbhdo1XRtyatPk8bQxzuPLdnIH+/kjprVAAMylPG/uUQgwACaV ONITb/0T8NnNzIUc+0aR774vQIMUfz8Dkccf4YPiHZ9C1w4CeZai94PcDSuL0sKG ok2tdICp82wvpE0KlHAitQAPXt5gYpvzgOkulyLYsUoGIG5pXiv7jP9speQd9Od7 whGkIHmeUKjZdDIBQvtBBvZ9W6tgou9C6AobInDsreAAmjy0d8Kt2aOl4/Q9Rt2X 1ZMaEBhtJbyLj8LFArkWzHuOG/+yZw== =vNMN -----END PGP SIGNATURE----- --U+z1uOwmvmmbFBAc-- From owner-freebsd-current@freebsd.org Fri Mar 2 14:25: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 B4813F27DA3 for ; Fri, 2 Mar 2018 14:25:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 475FD835B1; Fri, 2 Mar 2018 14:25:33 +0000 (UTC) (envelope-from carpeddiem@gmail.com) Received: by mail-io0-x234.google.com with SMTP id d71so10778567iog.4; Fri, 02 Mar 2018 06:25:33 -0800 (PST) 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=/s31tFDOs0B3NfJV/N63VuOayk7njWN3e1yVdew/yzk=; b=LAy6Y5yauXGbSEft1tDRVXnWk9w/zJENhPRKMV9GiiSqs+BSUCWAVJlipmta+vzHCH bApPvESjj/CBDNgd0mxGcZPZIKwRiW/0N/3aFq/wybhEx2E2SLc1OndIW9lofIFl1sVn f5kX8RUENXslyaFBY0PUL4t/XPPr7C6BNhJwfv+/GWDAN1UE2g18sDThJ6v7uacY0uIj joeRyGdr82W8pLEU2PsMFwXAqn+lRuBPWCx7ku2cJIW7tqEftsY/PQjeZUKAk3wilhBK qfZlWzCRSZe9n/9zODc/p1ShzKwuqQgQEId6o+5lxbc94wbm7mTVH8iDNKXX20ckdUtv 7mtA== 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=/s31tFDOs0B3NfJV/N63VuOayk7njWN3e1yVdew/yzk=; b=KUhMQ5HoqkfXdCgURSwZsL9+zjOPwSFyFzl3xTAnjTQr73MGmyggkzDaQJ8ROUYbP9 WpOJ+9TxUTFkbKjnXe6yS7hJGFMiv0onQ/kO+MRab15DPkN/6EdYAvNVWjhDy4T8rxME +jmUynx/Lr84L4iYnXlrLxFq5HpeWHRGMb7t8OYy93Ke5KBq2xnPWRIzWODmYANhS4qS XbAvoYHY4Xh7TwZi4lMXcGTR7+R+9gWhlIJkOjD7vueV+ye+DDZCW/StlAfITwL7u793 ysTQfWcAnZpisb+/+8DPnK2L0/OFBgkXdRBu8K5LCGeR3Vw3C0YEqr7T5Z8taQhEcJeD UVUQ== X-Gm-Message-State: APf1xPDtacWgPGwcaEZR8/MaISi0AQK0LbnSLkWynFN3YEy6N8xpHrhe cxjNwG0hgTwt+yHzrk6YiQFX3p96ECWa79VxnjOnKg== X-Google-Smtp-Source: AG47ELsg1cuThmH7lkKZBZplOJt1ESlO5xN4EeEtGLoenb95o263SlDZhmUj/imtS2/SsOtBp03uaQ2Zb1hzcLVIoAQ= X-Received: by 10.107.141.12 with SMTP id p12mr6822281iod.288.1520000732493; Fri, 02 Mar 2018 06:25:32 -0800 (PST) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.163.13 with HTTP; Fri, 2 Mar 2018 06:25:12 -0800 (PST) In-Reply-To: References: From: Ed Maste Date: Fri, 2 Mar 2018 09:25:12 -0500 X-Google-Sender-Auth: 6OsjJHf5DsVtlmH7GgcTaMA6t5A Message-ID: Subject: Re: Question mark on Lua menu box To: Renato Botelho Cc: Kyle Evans , FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 14:25:33 -0000 On 2 March 2018 at 07:06, Renato Botelho wrote: > Kyle, > > I've moved to Lua loader to help testing and it worked fine. The only > odd thing I noted is the menu box with odd chars as you can see at [1]. Hi Renato, thanks for testing! Are you booting via BIOS or UEFI? From owner-freebsd-current@freebsd.org Fri Mar 2 15: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 00188F2D0A9 for ; Fri, 2 Mar 2018 15:31:51 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f47.google.com (mail-lf0-f47.google.com [209.85.215.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 650CA86A39; Fri, 2 Mar 2018 15:31:51 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f47.google.com with SMTP id q69so13864391lfi.10; Fri, 02 Mar 2018 07:31:51 -0800 (PST) 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=r0QB/pjJ+4klY/8SeVao19i0AyQrdin2oHZROsvDliM=; b=rWuSMz6WIBHiYi8TtE6zgh6LbMCAXOZz9wnCHKuP2rBT6/S7ueMSXnStjghfMAy1As v+yVgOudQMtbORQMYFME6EbT+Qshi9tS2JP8unHD451el2IZMRBoP0C7HYzDZEDUy9E+ FtBBK8lrv6Bu/biJDwMrwP36+ndyxySpI6nDgJ84y1EFpvu3TSkZ8unbH5k83tuK2qsY 36wPzzOlvpnb/WC5tyipNgjCagR2+r3LQy62Y4Dpu+kZYmdPSjSSBqOBhi+YDIMxYecM 7bn5dl0Fi1DwTAGxETzd9haQ7JqTZn42RLpTag2mSrTaccNdqfr8OAXafXmujM6aoKR6 OU1Q== X-Gm-Message-State: AElRT7FiZRxLZrDOOiZLj2cI4V34+yCqlFbZ8gLX6oPd5E4gqfos8V5q e8pfUEDMIuBOTQRByLZ21iisbFSv X-Google-Smtp-Source: AG47ELtioZyUS/KRmxgB7Ik1YvIqmIbubUiTO20mwt+iH+gZ+YC5mkfciU5PbKA20fKdmUhobK5J6g== X-Received: by 10.25.234.75 with SMTP id i72mr4382987lfh.65.1520004704025; Fri, 02 Mar 2018 07:31:44 -0800 (PST) Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com. [209.85.215.48]) by smtp.gmail.com with ESMTPSA id c70sm1354128ljf.34.2018.03.02.07.31.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 07:31:43 -0800 (PST) Received: by mail-lf0-f48.google.com with SMTP id t204so13830188lff.9; Fri, 02 Mar 2018 07:31:43 -0800 (PST) X-Received: by 10.46.83.87 with SMTP id t23mr4432998ljd.38.1520004703782; Fri, 02 Mar 2018 07:31:43 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Fri, 2 Mar 2018 07:31:23 -0800 (PST) In-Reply-To: References: From: Kyle Evans Date: Fri, 2 Mar 2018 09:31:23 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Question mark on Lua menu box To: Renato Botelho Cc: FreeBSD Current , Ed Maste Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 15:31:52 -0000 On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: > Kyle, > > I've moved to Lua loader to help testing and it worked fine. The only > odd thing I noted is the menu box with odd chars as you can see at [1]. > > My laptop is running a recent current (r330275) with ZFS and UEFI. > > [1] https://imgur.com/a/kIQ0O > -- > Renato Botelho > Hi, Thanks for testing! =) Can you give it a shot with EFI boot after r330281 (just committed), please? I think our working theory is that we were printing newlines along with our box-drawing characters, and that could be problematic. The new version handles all of that a little better and respects loader_menu_frame to boot. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Fri Mar 2 15:52: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 69C45F2EDE7 for ; Fri, 2 Mar 2018 15:52:23 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::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 2723D87E33; Fri, 2 Mar 2018 15:52:23 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mail-qt0-x230.google.com with SMTP id a23so12412942qtn.0; Fri, 02 Mar 2018 07:52:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=HgtO9WZqw012jHirYkUExpEgGVy0E02lsUfqpgEwAJk=; b=bxkYx7CGncUx2u/R0eiGFLNwnGAn07YK4ArpHh4MHG4RdM1QvlCLGNmXsxKA8/eR/G glgXd61575fDQX1Dxm8UYFp6VKgbK+RSekYvpi1evFhPWBSD31AnO3gX2t6+h2jwPEqv 24NXtxSg3vKHr9QiB6k8TuBPIMx81RHQq/xOmunBbHoOrIKt1mz4NE31O/Qn5JTioXsI xODKZ5oC4T8coxi+u7sSCVJFo6OWth2b6p78Gz4Eunx4NFF5WE1tszb+EiHO0zhumWZj Tiwa+tVWWWMnaiPE3Pawys4j0N4vXh64P+edJ6cc1Wnf9iqwvsqkfl4qnMmP6zwqEzvd KZ7A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=HgtO9WZqw012jHirYkUExpEgGVy0E02lsUfqpgEwAJk=; b=jKkYP7aEL6asF0P1a8hjZjP29zsjKpKsHvgf0OFlVnGUR2H7yQnLDvMQC3LPl/riVb 1ko6PdqdP5FJddpMz3exFWdJ+Szx3xAtk6DMeLJ/qB78kfQbh5hfra+eMefgWH4bfM/j 3HXJ4HM3B1e7JXbc73dWp6MVrJFour4aklX58uwyC+xIbgadaztc0kyAMnggF1Lg3VRa +Tds3FKQqeDDPFQF11efr21Xabv1Gooe26s2DbseZcqxU3NHSMru0RvINicxJkg5m/CV nXUtQ31GubrSPPkQdcqFvtId20q4kqAZeTjrmXKWSawM1mhgCJN2/ly3lNO/wFVyZ5ze zfVw== X-Gm-Message-State: AElRT7Ftxc7yq25hfPol0qXKpsRD51Qk5TSSe+0rpWobt7Hru6HmClE8 AfVfzeopLy+WHE/W8uF0U7NE6t4c X-Google-Smtp-Source: AG47ELvEHh0RyvjPFgWuEr3AMl9kVvMB+Gm5F/DCOYsFnn6jH7klt3evWYONMmvg+snzHgoLfYNXfQ== X-Received: by 10.200.52.204 with SMTP id x12mr9091299qtb.267.1520005942510; Fri, 02 Mar 2018 07:52:22 -0800 (PST) Received: from mbp.home ([177.53.86.172]) by smtp.gmail.com with ESMTPSA id d184sm4769049qka.68.2018.03.02.07.52.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 07:52:21 -0800 (PST) Sender: Renato Botelho Subject: Re: Question mark on Lua menu box To: Kyle Evans Cc: FreeBSD Current , Ed Maste References: From: Renato Botelho Message-ID: <86a6a648-be6a-41b8-7cee-c78cc72a894f@FreeBSD.org> Date: Fri, 2 Mar 2018 12:52:18 -0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; 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-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 15:52:23 -0000 On 02/03/18 12:31, Kyle Evans wrote: > On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >> Kyle, >> >> I've moved to Lua loader to help testing and it worked fine. The only >> odd thing I noted is the menu box with odd chars as you can see at [1]. >> >> My laptop is running a recent current (r330275) with ZFS and UEFI. >> >> [1] https://imgur.com/a/kIQ0O >> -- >> Renato Botelho >> > > Hi, > > Thanks for testing! =) Can you give it a shot with EFI boot after > r330281 (just committed), please? > > I think our working theory is that we were printing newlines along > with our box-drawing characters, and that could be problematic. The > new version handles all of that a little better and respects > loader_menu_frame to boot. Hi, Unfortunately it didn't change anything. -- Renato Botelho From owner-freebsd-current@freebsd.org Fri Mar 2 15:56: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 00B20F2F57E for ; Fri, 2 Mar 2018 15:56:05 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) (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 6926B68167; Fri, 2 Mar 2018 15:56:04 +0000 (UTC) (envelope-from byond.lenox@gmail.com) Received: by mail-lf0-f49.google.com with SMTP id m69so13995738lfe.8; Fri, 02 Mar 2018 07:56:04 -0800 (PST) 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=b0ZYG0+J2rIb4pMjzVkff4wv1BkzBxz/uhz0Zsg5VgQ=; b=SEHZjZTcH1PXGN7h1Ha1EmYMAUz+CTAxUQGSd7IlwdILz9RqFzz6wQX2QIe3mZTpYD 0uJhfM4m7tP26q+jI3Pq5Yw0IZeEUKJiECotdfl/HAD/3e8ABFQqM5ODORmxei8MB+sB /KMRS0FS5AjfqIXP10G1NrrLQggC9/jTHWXc7Mw5KelYj0qNNloOAPr8sV796U3Onurb 08ycYllFiThkqZiJHU1AxWowqOL6ZzoSGsavmxj2BjhJeqw7SfLJjKKlRYPb5K55AOhq I6XeVztBAA9t0MY/d3arg+W2taUOkGX6TRlpUfyHnOUXzQ1hr0/i81rDZbTxRqJinW1E sbcQ== X-Gm-Message-State: AElRT7H6RU4rnjcUJmdlGGSnp48Oala345YsJKdWwGDUx4rv/PxWm+GL fhq2yZGmqLAKPxE3H3lS+A5P9dAp X-Google-Smtp-Source: AG47ELu8IxBaCziU9yawt2d7Ex9Jy50UU7muTC76PlZg2H5yAWwZtEaECDZNjYwV2pnn7s8putRcPQ== X-Received: by 10.25.105.18 with SMTP id e18mr4237224lfc.52.1520006156454; Fri, 02 Mar 2018 07:55:56 -0800 (PST) Received: from mail-lf0-f41.google.com (mail-lf0-f41.google.com. [209.85.215.41]) by smtp.gmail.com with ESMTPSA id t81sm1396209lff.58.2018.03.02.07.55.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 07:55:56 -0800 (PST) Received: by mail-lf0-f41.google.com with SMTP id 70so14004789lfw.2; Fri, 02 Mar 2018 07:55:56 -0800 (PST) X-Received: by 10.46.4.74 with SMTP id 71mr4182817lje.51.1520006156225; Fri, 02 Mar 2018 07:55:56 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.54.1 with HTTP; Fri, 2 Mar 2018 07:55:35 -0800 (PST) In-Reply-To: <86a6a648-be6a-41b8-7cee-c78cc72a894f@FreeBSD.org> References: <86a6a648-be6a-41b8-7cee-c78cc72a894f@FreeBSD.org> From: Kyle Evans Date: Fri, 2 Mar 2018 09:55:35 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: Question mark on Lua menu box To: Renato Botelho Cc: FreeBSD Current , Ed Maste Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 15:56:05 -0000 On Fri, Mar 2, 2018 at 9:52 AM, Renato Botelho wrote: > On 02/03/18 12:31, Kyle Evans wrote: >> On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >>> Kyle, >>> >>> I've moved to Lua loader to help testing and it worked fine. The only >>> odd thing I noted is the menu box with odd chars as you can see at [1]. >>> >>> My laptop is running a recent current (r330275) with ZFS and UEFI. >>> >>> [1] https://imgur.com/a/kIQ0O >>> -- >>> Renato Botelho >>> >> >> Hi, >> >> Thanks for testing! =) Can you give it a shot with EFI boot after >> r330281 (just committed), please? >> >> I think our working theory is that we were printing newlines along >> with our box-drawing characters, and that could be problematic. The >> new version handles all of that a little better and respects >> loader_menu_frame to boot. > > Hi, > > Unfortunately it didn't change anything. > Aw =(. Can you take a picture of what Forth loader looks like for you with the default frame style on an EFI boot? I'm wondering if it's not doing something sneaky that I can't determine from the things I've looked at. Thanks, Kyle Evans From owner-freebsd-current@freebsd.org Fri Mar 2 16:34: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 9FEF8F3266F for ; Fri, 2 Mar 2018 16:34:11 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::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 451446A58E; Fri, 2 Mar 2018 16:34:11 +0000 (UTC) (envelope-from garga.bsd@gmail.com) Received: by mail-qk0-x22c.google.com with SMTP id y137so12631783qka.4; Fri, 02 Mar 2018 08:34:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=uvIxkRCRuoJs+TAAAJzcatmCN4eKrCCjz8HKj690Big=; b=X1pv6eFHL7bf7IZaFx879dvvF2YqZLAnlSqBMx4S50eZDxsCbm51DnNkOegwJhEjiB a0ggoJqGindd+y37zi9LcYtOh3N2fL/nICi7Gx1/iet47ZM5r1qp4SKZpJVieyAJLIuu lRiChytQxAD1FRHP8FuZ2GGXDYKfi5OBP736G3yPP2x84LPIFkWYoEvXqDE0PcXgNIu1 QHJoK3S6JIHhKga98yq0fIy1yxE9xXZ59r2Mn5Jk90eWCsW+k5ed+GRfAv9xvL+250z7 koCAM6ZDwlqa0IQWDxkNPutN2EB99H+G1ooeLJBAJJ+hFPidfEPYo8acLF66NfalN2nU +QOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=uvIxkRCRuoJs+TAAAJzcatmCN4eKrCCjz8HKj690Big=; b=T+QzPyboTDon0NjkI/k4btPm7I8nlr2c5yYHP7GX+XK2WXealXDd0Slp5I8re0Zi2L URynZTqvvMlIiEOoC3IEow2BL8TZMnYhz5DZ0JkSqR0FYxp8VJTluZUWcK+wDoYOVjeY 5bRfS6x71zxdYflPU8vfOZW3JqGSjEvbVWDBpK/Ext8GJapjZ3PbGt1Cz9CTDN0Zofi5 mMA4JGqOXG6uydsC+Y6616wbvZaO4AFN186Fd+lCrX/p5mN1Pmj4G9PIfsmfw6h+2qS/ J3TXtzxpQrcw/pQ6C8VvNgRzc0a3Pw4/NC6JipiK+m/rejvpz138V1MEanH8lx87LCnD Rezg== X-Gm-Message-State: AElRT7FB0x4LD2EzwmgmcBkmf77crog7x2DsyypKnHSWQcbpp+0PBv/F FTpaSxXsLj2iWCcROSKlxtdqYX4P X-Google-Smtp-Source: AG47ELvu2P8sImoSCFgXZ1K1g+8igkRee2Gbw7NVXT00Xguu637IKXwDV5x465yQu3GeempEBRQqUg== X-Received: by 10.55.6.10 with SMTP id 10mr9179292qkg.191.1520008450427; Fri, 02 Mar 2018 08:34:10 -0800 (PST) Received: from mbp.home ([177.53.86.172]) by smtp.gmail.com with ESMTPSA id c42sm4870520qtc.42.2018.03.02.08.34.08 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Mar 2018 08:34:09 -0800 (PST) Sender: Renato Botelho Subject: Re: Question mark on Lua menu box To: Kyle Evans Cc: FreeBSD Current , Ed Maste References: <86a6a648-be6a-41b8-7cee-c78cc72a894f@FreeBSD.org> From: Renato Botelho Message-ID: <1577158e-59ad-6882-7328-a6c572af4b6b@FreeBSD.org> Date: Fri, 2 Mar 2018 13:34:07 -0300 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; 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-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 16:34:11 -0000 On 02/03/18 12:55, Kyle Evans wrote: > On Fri, Mar 2, 2018 at 9:52 AM, Renato Botelho wrote: >> On 02/03/18 12:31, Kyle Evans wrote: >>> On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >>>> Kyle, >>>> >>>> I've moved to Lua loader to help testing and it worked fine. The only >>>> odd thing I noted is the menu box with odd chars as you can see at [1]. >>>> >>>> My laptop is running a recent current (r330275) with ZFS and UEFI. >>>> >>>> [1] https://imgur.com/a/kIQ0O >>>> -- >>>> Renato Botelho >>>> >>> >>> Hi, >>> >>> Thanks for testing! =) Can you give it a shot with EFI boot after >>> r330281 (just committed), please? >>> >>> I think our working theory is that we were printing newlines along >>> with our box-drawing characters, and that could be problematic. The >>> new version handles all of that a little better and respects >>> loader_menu_frame to boot. >> >> Hi, >> >> Unfortunately it didn't change anything. >> > > Aw =(. Can you take a picture of what Forth loader looks like for you > with the default frame style on an EFI boot? I'm wondering if it's not > doing something sneaky that I can't determine from the things I've > looked at. Sure, here it is: https://imgur.com/a/fmO8w -- Renato Botelho From owner-freebsd-current@freebsd.org Fri Mar 2 17:43: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 8F99EF37A36 for ; Fri, 2 Mar 2018 17:43:09 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) (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 2FA346DCEE for ; Fri, 2 Mar 2018 17:43:09 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1eroi2-0000xi-Im for freebsd-current@freebsd.org; Fri, 02 Mar 2018 18:43:06 +0100 Received: from [::1] (port=46328 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1eroi2-00020i-Cc for freebsd-current@freebsd.org; Fri, 02 Mar 2018 18:43:06 +0100 Received: from mx2.freenet.de ([195.4.92.12]:38788) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1erofe-0007Nq-MA for freebsd-current@freebsd.org; Fri, 02 Mar 2018 18:40:38 +0100 Received: from p4fd9ed31.dip0.t-ipconnect.de ([79.217.237.49]:18749 helo=freebsd-t420.fritz.box) by mx2.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1erofe-00043d-Fm for freebsd-current@freebsd.org; Fri, 02 Mar 2018 18:40:38 +0100 Date: Fri, 2 Mar 2018 17:40:45 +0100 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: drm-next-kmod regression Message-ID: <20180302164045.GA45988@freebsd-t420.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline User-Agent: Mutt/1.9.3 (2018-01-21) X-Originated-At: 79.217.237.49!18749 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 17:43:09 -0000 Hi, the last drm-next-kmod worked fine on my Lenovo T420 with i5-2520M and a HD Graphics 3000. After the update to the actual version (4.11) from ports, I'm seeing regression in form of a very slow xfce4-desktop. The slowness starts after some short time. Slow means for example that I can type faster than the terminal prints the chars or when i move windows they lag extremely behind the mouse's motion. One entry in Xorg.0.log caught my attention: [ 128.266] (EE) intel(0): Failed to submit rendering commands (Bad address), disabling acceleration. Disabling the xfce4-compositor improves the situation significantly, but not entirely. Switching back to the systems i915 driver resolves the issue. Any ideas? From owner-freebsd-current@freebsd.org Fri Mar 2 18:32: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 33F68F3B6C2 for ; Fri, 2 Mar 2018 18:32:45 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from mail.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D2205708C8; Fri, 2 Mar 2018 18:32:44 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (ralph.baldwin.cx [66.234.199.215]) by mail.baldwin.cx (Postfix) with ESMTPSA id 771D010A8BA; Fri, 2 Mar 2018 13:32:43 -0500 (EST) From: John Baldwin To: Konstantin Belousov Cc: freebsd-current@freebsd.org, cem@freebsd.org, Ronald Klop Subject: Re: pkg does not recognize correct kernel version Date: Fri, 02 Mar 2018 10:18:44 -0800 Message-ID: <1815467.EQChbu9SGs@ralph.baldwin.cx> User-Agent: KMail/4.14.10 (FreeBSD/11.1-STABLE; KDE/4.14.30; amd64; ; ) In-Reply-To: <20180301120257.GB3194@kib.kiev.ua> References: <1796463.2W2Te48fqL@ralph.baldwin.cx> <20180301120257.GB3194@kib.kiev.ua> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mail.baldwin.cx); Fri, 02 Mar 2018 13:32:43 -0500 (EST) X-Virus-Scanned: clamav-milter 0.99.2 at mail.baldwin.cx X-Virus-Status: Clean X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 18:32:45 -0000 On Thursday, March 01, 2018 02:02:58 PM Konstantin Belousov wrote: > On Wed, Feb 28, 2018 at 03:32:43PM -0800, John Baldwin wrote: > > On Wednesday, February 28, 2018 09:45:47 PM Konstantin Belousov wrote: > > > On Wed, Feb 28, 2018 at 10:57:53AM -0800, John Baldwin wrote: > > > > On Tuesday, February 20, 2018 10:19:02 AM Conrad Meyer wrote: > > > > > On Mon, Feb 19, 2018 at 2:38 PM, Ronald Klop wrote: > > > > > > On Mon, 19 Feb 2018 22:05:51 +0100, Konstantin Belousov > > > > > > wrote: > > > > > > > > > > > >> Look at the man page. pkg reads version from the /bin/sh ELF FreeBSD > > > > > > > > > > > > > > > > > > Which man page? I can't find it in pkg help update or pkg help upgrade or > > > > > > man pkg. > > > > > > > > > > I had to dig for quite a while to find a reference (pkg.conf(5)): > > > > > > > > > > ABI: string The ABI of the package you want to install. Default: > > > > > derived from the ABI of the /bin/sh binary. > > > > > > > > > > >> version note: > > > > > >> orion% file /bin/ls > > > > > >> /bin/ls: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD), > > > > > >> dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 11.1 > > > > > >> (1101506), FreeBSD-style, stripped > > > > > >> > > > > > >> Update world past the __FreeBSD_version which is reported for the > > > > > >> repository. > > > > > > > > > > > > > > > > > > Does this mean I always have to do a *clean* buildworld after every version > > > > > > bump? This takes ages. > > > > > > > > > > You could also do a -DNO_CLEAN buildworld. > > > > > > > > > > Or you can continue to override with "-o OSVERSION=foo", although that > > > > > may eventually result in broken packages. In general the OSVERSION is > > > > > bumped conservatively (more often than will actually result in > > > > > breakage), so you can get away with the easy workaround for a while > > > > > between buildworlds. > > > > > > > > NO_CLEAN=yes doesn't work. A clean buildworld is required. The reason is that > > > > the __FreeBSD_version embedded in binaries is stored in /usr/lib/crt*.o, but > > > > that the dependency rules in lib/csu/Makefile do not rebuild these .o files > > > > everytime changes (so a NO_CLEAN=yes buildworld won't rebuild them > > > > leaving them with a stale version). Furthermore, when binaries and shared > > > > libraries are built, our Makefiles do not specify that the relevant > > > > /usr/lib/crt*.o files are dependencies, so even if we fixed the missing > > > > dependency, no binaries would relink to pick up the updated > > > > __FreeBSD_version file unless some other input to the binary changed. This > > > > one could perhaps be mostly mitigated by forcing libc to depend on the > > > > relevant crt*.o files explicitly (or even having it depend on > > > > to force relinking of everything when changes). > > > libc already depends on sys/param.h. > > > > Hmm, even when I removed /usr/obj/usr/src/lib/csu entirely and then did a buildworld > > NO_CLEAN=yes recently /bin/sh was not relinked, though perhaps at that point > > libc already thought it was up-to-date relative to from the previous > > build. > > > > > I think it would be enough to specify that crt1.o depends on sys/param.h > > > as well. Although it is also strange, because e.g. for amd64 the dep > > > thread is csu/amd64/crt1.c->csu/common/crtbrand.c->sys/param.h, which should > > > be detected by the include file calculation. > > > > I think the detour via assembly + sed is what breaks the dependency chain. > > FWIW, I found that on at least MIPS with clang I did not need the SED_FIX_NOTE > > hack. > > Perhaps the FIX_NOTE should be re-evaluated for all the changes happen in > the toolchains since the hack was needed. I believe modern GCC still needs the hack unfortunately. :( -- John Baldwin From owner-freebsd-current@freebsd.org Fri Mar 2 19:52: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 A718EF410C7 for ; Fri, 2 Mar 2018 19:52:19 +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 4B4BA75144 for ; Fri, 2 Mar 2018 19:52:19 +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 A4A3E260224; Fri, 2 Mar 2018 20:52:17 +0100 (CET) Subject: Re: drm-next-kmod regression To: =?UTF-8?Q?Manuel_St=c3=bchn?= , freebsd-current@freebsd.org References: <20180302164045.GA45988@freebsd-t420.fritz.box> From: Hans Petter Selasky Message-ID: Date: Fri, 2 Mar 2018 20:52:14 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180302164045.GA45988@freebsd-t420.fritz.box> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 19:52:19 -0000 On 03/02/18 17:40, Manuel Stühn wrote: > Hi, > the last drm-next-kmod worked fine on my Lenovo T420 with i5-2520M and a > HD Graphics 3000. After the update to the actual version (4.11) from > ports, I'm seeing regression in form of a very slow xfce4-desktop. The > slowness starts after some short time. Slow means for example that I can > type faster than the terminal prints the chars or when i move windows > they lag extremely behind the mouse's motion. > > One entry in Xorg.0.log caught my attention: > [   128.266] (EE) intel(0): Failed to submit rendering commands (Bad > address), disabling acceleration. > > Disabling the xfce4-compositor improves the situation significantly, but > not entirely. > > Switching back to the systems i915 driver resolves the issue. > > Any ideas? > Which version of FreeBSD is this. Are you using the latest kernel sources? Did you build drm-next-kmod from source? --HPS From owner-freebsd-current@freebsd.org Fri Mar 2 20:05: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 71127F41EB0 for ; Fri, 2 Mar 2018 20:05:55 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout2.freenet.de (mout2.freenet.de [IPv6:2001:748:100:40::2:4]) (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 09A2575B57 for ; Fri, 2 Mar 2018 20:05:54 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1erqwD-0004FC-5O for freebsd-current@freebsd.org; Fri, 02 Mar 2018 21:05:53 +0100 Received: from [::1] (port=34192 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1erqwD-000386-1W for freebsd-current@freebsd.org; Fri, 02 Mar 2018 21:05:53 +0100 Received: from mx3.freenet.de ([195.4.92.13]:56344) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1erqtR-0000zQ-Bz for freebsd-current@freebsd.org; Fri, 02 Mar 2018 21:03:01 +0100 Received: from p4fd9ed31.dip0.t-ipconnect.de ([79.217.237.49]:54680 helo=freebsd-t420.fritz.box) by mx3.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1erqtR-0002eY-5c for freebsd-current@freebsd.org; Fri, 02 Mar 2018 21:03:01 +0100 Date: Fri, 2 Mar 2018 20:03:08 +0100 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Re: drm-next-kmod regression Message-ID: <20180302190308.GA94740@freebsd-t420.fritz.box> References: <20180302164045.GA45988@freebsd-t420.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: User-Agent: Mutt/1.9.3 (2018-01-21) X-Originated-At: 79.217.237.49!54680 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 02 Mar 2018 20:05:55 -0000 On Fri, Mar 02, 2018 at 08:52:14PM +0100, Hans Petter Selasky wrote: >On 03/02/18 17:40, Manuel Sthn wrote: >> Hi, >> the last drm-next-kmod worked fine on my Lenovo T420 with i5-2520M and a >> HD Graphics 3000. After the update to the actual version (4.11) from >> ports, I'm seeing regression in form of a very slow xfce4-desktop. The >> slowness starts after some short time. Slow means for example that I can >> type faster than the terminal prints the chars or when i move windows >> they lag extremely behind the mouse's motion. >> >> One entry in Xorg.0.log caught my attention: >> [ 128.266] (EE) intel(0): Failed to submit rendering commands (Bad >> address), disabling acceleration. >> >> Disabling the xfce4-compositor improves the situation significantly, but >> not entirely. >> >> Switching back to the systems i915 driver resolves the issue. >> >> Any ideas? >> > >Which version of FreeBSD is this. Are you using the latest kernel >sources? uname -a FreeBSD freebsd-t420 12.0-CURRENT FreeBSD 12.0-CURRENT #11 r330283: Fri Mar 2 17:35:08 CET 2018 root@valinor:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 >Did you build drm-next-kmod from source? Yes, ports from today built against the revision mentioned above. From owner-freebsd-current@freebsd.org Sat Mar 3 03: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 A361CF3B7D8 for ; Sat, 3 Mar 2018 03:37:23 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::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 320756A5F3 for ; Sat, 3 Mar 2018 03:37:23 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: by mail-io0-x230.google.com with SMTP id h23so12644338iob.11 for ; Fri, 02 Mar 2018 19:37:23 -0800 (PST) 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=2rpRJ9c9Xhu8K+Vkuh0MGxh4lQjtvz9KjWT7j8o66uI=; b=GaopxKF08iwYzA96tYq7pVw6XUmgqLGdxkJ+YTe4v68+iu7Pmgpa35AxKkyAHGz4IO fjcQuozdM2C0o5Oc0dwxe2p7312d7qnoz9ezrG4sq7nSs5gcGTcpz0ZyF37sqNbuLOiv 7dEyv7tuN9GkUSNbOCUHx01054UFQQxc0OHclzRdhXIt/HIzmPB8T0YtZ9FEuI41BttP vb2Xwbqe+mXEjXYCnA1M8MxQn9heetOttQeXvOyNEmj7T1CacUzgDSzTTqWrI3b06jBL qsnV0hLEcUp5ZXjc9AlbUa+y8ue6w+NSor1eBVSgSdmss5gBkvWjvL9BB6BF4QtNDaUK 5NKg== 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=2rpRJ9c9Xhu8K+Vkuh0MGxh4lQjtvz9KjWT7j8o66uI=; b=ctDOJbXcOxNLWMbeeGfLbLHKLDCowPOEvZdXHyRJMBTDsfsxf3Kls+9EppE31uA/n1 2FZNC5OUugcgQaaD0+tDg/+A+RfLjBNyCJmuYip9V3dhrsqeZKGWR2FjxjhSOsFFqgi7 zXmtp7ma+2Z/a4uxAUGdFYR6I8DVlv17ShuSJJTYLjitQN2LICB+Eh+dp1afTVNpT0iI SwjAUSuiJgYsvDsgSduO/r2phPxsayF8Z2UT2acccXOlJ1E32yPwwzmeaBaxXUVxxVF4 PRxJXVrOxgIzsd4YufimY+yI8oUryiOU7YwIml1sEZYvIJ/qizVIK47tOUAbloTOpjOt No2w== X-Gm-Message-State: APf1xPDYlKCMr3fao7lQZ4inYF5yBOn8Na/2ZKPZSjZY6A79OJ8e+Q9A fFPaThrDNRJLuPxVF+Qu5g9bjd+9RHzD3SUObkz1pg== X-Google-Smtp-Source: AG47ELu+Pwc5L6SR8AX6wB8EZCN0pH+h1EQNygQLEXNYbrYJhcTg2IF9t1zvla1e2l5Uu/091sALegWnwnlElpEZIlU= X-Received: by 10.107.130.74 with SMTP id e71mr9219319iod.245.1520048242421; Fri, 02 Mar 2018 19:37:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.80.134 with HTTP; Fri, 2 Mar 2018 19:37:21 -0800 (PST) From: Oleg Lelchuk Date: Fri, 2 Mar 2018 22:37:21 -0500 Message-ID: Subject: drm-next-kmod-4.11 and vaapi hardware acceleration To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 03:37:23 -0000 I run 12-CURRENT-r330303. My cpu is Haswell. After compiling drm-next-kmod-4.11 and libva-intel-driver, I get garbled videos in both mpv and vlc when the vaapi hardware acceleration is enabled. I had no such problem with the previous version of drm-next-kmod. Is it possible that libva-intel-driver-2.1 and drm-next-kmod-4.11 are not fully compatible with one another? Please tell me what I should do to resolve this issue. From owner-freebsd-current@freebsd.org Sat Mar 3 04:22:51 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1133BF3DC1D for ; Sat, 3 Mar 2018 04:22:51 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yw0-x22a.google.com (mail-yw0-x22a.google.com [IPv6:2607:f8b0:4002:c05::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 A84D76C637 for ; Sat, 3 Mar 2018 04:22:50 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yw0-x22a.google.com with SMTP id u84so3990312ywg.9 for ; Fri, 02 Mar 2018 20:22:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=eX5S0NuKDamZ9JHkmfU0l20pmikJOl16HjNRNI5aieU=; b=Vzm+D6UibKk0bHEk6KpdBVvHFh7MIRUcTQpQ/BVGPngDQGmKEDOggHyX71fENPtd9s IcGWB46/embFiC0n/oSjSkU/lL951vus6coNFjIPoKWCiRxOsGYTMjVN39QDw9ucRFhc trnbcZuCkf6ov9Bft0F+12x9tN/VqjRqH1/40= 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 :content-transfer-encoding; bh=eX5S0NuKDamZ9JHkmfU0l20pmikJOl16HjNRNI5aieU=; b=SeNlvEZ7ihlwDGoEexwFSGa6axm0AGWGjajzlcl2b2RWKb5K6yx5V7r2rejv3UXtFt CBxEpIRsoMoygjtt4BzDBg9o5iKfbcv3qouYbUSRCFoVMkEI/JPKD6BLZaQ1Sl26te5V XRoLgcX4GHWv6vL4Gxt3UdhFZKjBjjRdFMQvBAtCEuUleC3anVYLxtuT5L7GtMkGoexB QP9TsNzoKc/VzZvJnMpQAmibM2iaFTe9EUqPaZ+ENZrVc1/tnsFUxhgH3pAMNGpCX1iv QRqw3OMLw40OFbFJSCJG5lFY8B0WKxWDk1ASAJ8iQ8RRz3nmUstGgXdAhcouP3czChHM yFhg== X-Gm-Message-State: AElRT7EWRpS8bAVBYw64tIcwBHx44bk/lEzgezWcDtCo+zdKtgl/9Wro nsjS1ibv3SPGFHs+/+YrTiYb9Gl7InW/cJBpFRVomMSz X-Google-Smtp-Source: AG47ELuMcGzh7umXTd6uB2CHGKThGmXXfFfWsm/LeUPgnLpqLvfvjBpda+gKU1M5QuhhUiXeGWWH/b0dEW3XsbbFQ60= X-Received: by 10.129.62.11 with SMTP id l11mr5137334ywa.387.1520050969578; Fri, 02 Mar 2018 20:22:49 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:c68c:0:0:0:0:0 with HTTP; Fri, 2 Mar 2018 20:22:19 -0800 (PST) From: Eitan Adler Date: Fri, 2 Mar 2018 20:22:19 -0800 Message-ID: Subject: unable to build head - iconv issues To: freebsd-current Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 04:22:51 -0000 uname -a: FreeBSD develop 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r329949: Sat Feb 24 07:58:23 UTC 2018 eax@fasteagle:/srv/obj/fbsd/head/srv/src/fbsd/head/amd64.amd64/sys/GENERIC amd64 src-env.conf: MAKEOBJDIRPREFIX=3D/srv/obj src.conf: MALLOC_PRODUCTION=3Dyes WITHOUT_SVNLITE=3Dtrue version: head:330309 =E2=88=B4make buildworld ... =3D=3D=3D> bin/csh (all) cc -target x86_64-unknown-freebsd12.0 --sysroot=3D/srv/obj/srv/src/fbsd/head/tmp -B/srv/obj/srv/src/fbsd/head/tmp/usr/bin -O2 -pipe -I. -I/srv/src/fbsd/head/bin /csh -I/srv/src/fbsd/head/contrib/tcsh -D_PATH_TCSHELL=3D'"/bin/csh"' -DHAVE_ICONV -g -std=3Dgnu99 -fstack-protector-strong -Wsystem-headers -Werror -Wno-pointer- sign -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-functio n -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunu sed-arguments -o csh.full sh.o sh.dir.o sh.dol.o sh.err.o sh.exec.o sh.char.o sh.exp.o sh.file.o sh.func.o sh.glob.o sh.hist.o sh.init.o sh.lex.o sh.misc.o s h.parse.o sh.print.o sh.proc.o sh.sem.o sh.set.o sh.time.o glob.o mi.termios.o tw.help.o tw.init.o tw.parse.o tw.spell.o tw.comp.o tw.color.o ed.chared.o ed.d efns.o ed.init.o ed.inputl.o ed.refresh.o ed.screen.o ed.xmap.o ed.term.o tc.alloc.o tc.bind.o tc.const.o tc.disc.o tc.func.o tc.nls.o tc.os.o tc.printf.o tc. prompt.o tc.sched.o tc.sig.o tc.str.o tc.vers.o tc.who.o dotlock.o tc.defs.o -ltermcapw -lcrypt /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:1275 (/srv/src/fbsd/head/contrib/tcsh/sh.c:1275) >>> sh.o:(main) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:1278 (/srv/src/fbsd/head/contrib/tcsh/sh.c:1278) >>> sh.o:(main) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:896 (/srv/src/fbsd/head/contrib/tcsh/sh.c:896) >>> sh.o:(main) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:2306 (/srv/src/fbsd/head/contrib/tcsh/sh.c:2306) >>> sh.o:(process) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:2322 (/srv/src/fbsd/head/contrib/tcsh/sh.c:2322) >>> sh.o:(process) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:2324 (/srv/src/fbsd/head/contrib/tcsh/sh.c:2324) >>> sh.o:(process) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:2309 (/srv/src/fbsd/head/contrib/tcsh/sh.c:2309) >>> sh.o:(process) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.c:2319 (/srv/src/fbsd/head/contrib/tcsh/sh.c:2319) >>> sh.o:(process) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.dir.c:93 (/srv/src/fbsd/head/contrib/tcsh/sh.dir.c:93) >>> sh.dir.o:(dinit) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.dir.c:93 (/srv/src/fbsd/head/contrib/tcsh/sh.dir.c:93) >>> sh.dir.o:(dinit) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.err.c:210 (/srv/src/fbsd/head/contrib/tcsh/sh.err.c:21= 0) >>> sh.err.o:(errinit) /srv/obj/srv/src/fbsd/head/tmp/usr/bin/ld: error: undefined symbol: iconv_catgets >>> referenced by sh.err.c:214 (/srv/src/fbsd/head/contrib/tcsh/sh.err.c:21= 4) >>> sh.err.o:(errinit) any ideas on how to fix this? --=20 Eitan Adler From owner-freebsd-current@freebsd.org Sat Mar 3 05:14: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 5D3CDF41373 for ; Sat, 3 Mar 2018 05:14:41 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 044526E405; Sat, 3 Mar 2018 05:14:41 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id E69362243; Sat, 3 Mar 2018 05:14:40 +0000 (UTC) From: Jan Beich To: Oleg Lelchuk Cc: freebsd-current@freebsd.org Subject: Re: drm-next-kmod-4.11 and vaapi hardware acceleration References: Date: Sat, 03 Mar 2018 06:14:27 +0100 In-Reply-To: (Oleg Lelchuk's message of "Fri, 2 Mar 2018 22:37:21 -0500") Message-ID: <371h-oi4s-wny@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 05:14:41 -0000 Oleg Lelchuk writes: > I run 12-CURRENT-r330303. My cpu is Haswell. After compiling > drm-next-kmod-4.11 and libva-intel-driver, I get garbled videos in both mpv > and vlc when the vaapi hardware acceleration is enabled. I had no such > problem with the previous version of drm-next-kmod. Is it possible that > libva-intel-driver-2.1 and drm-next-kmod-4.11 are not fully compatible with > one another? Please tell me what I should do to resolve this issue. See also https://github.com/FreeBSDDesktop/kms-drm/issues/32 From owner-freebsd-current@freebsd.org Sat Mar 3 05:25: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 33B2AF41F76 for ; Sat, 3 Mar 2018 05:25:01 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D44806EA82; Sat, 3 Mar 2018 05:25:00 +0000 (UTC) (envelope-from jbeich@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1354) id B18A1242F; Sat, 3 Mar 2018 05:25:00 +0000 (UTC) From: Jan Beich To: Manuel =?utf-8?Q?St=C3=BChn?= Cc: freebsd-current@freebsd.org Subject: Re: drm-next-kmod regression References: <20180302164045.GA45988@freebsd-t420.fritz.box> Date: Sat, 03 Mar 2018 06:24:55 +0100 In-Reply-To: <20180302164045.GA45988@freebsd-t420.fritz.box> ("Manuel =?utf-8?Q?St=C3=BChn=22's?= message of "Fri, 2 Mar 2018 17:40:45 +0100") Message-ID: 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.25 Precedence: 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, 03 Mar 2018 05:25:01 -0000 Manuel St=C3=BChn writes: > Hi, > the last drm-next-kmod worked fine on my Lenovo T420 with i5-2520M and > a HD Graphics 3000. After the update to the actual version (4.11) from > ports, I'm seeing regression in form of a very slow xfce4-desktop. The > slowness starts after some short time. Slow means for example that I > can type faster than the terminal prints the chars or when i move > windows they lag extremely behind the mouse's motion. > > One entry in Xorg.0.log caught my attention: > [ 128.266] (EE) intel(0): Failed to submit rendering commands (Bad > address), disabling acceleration. Did you build xf86-video-intel with SNA option enabled or have Option "AccelMethod" "SNA" in xorg.conf? If so see also https://github.com/FreeBSDDesktop/kms-drm/issues/32 From owner-freebsd-current@freebsd.org Sat Mar 3 06:13: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 6C134F43E13 for ; Sat, 3 Mar 2018 06:13:23 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 00C6A70247 for ; Sat, 3 Mar 2018 06:13:23 +0000 (UTC) (envelope-from oleglelchuk@gmail.com) Received: by mail-io0-x234.google.com with SMTP id p78so12834472iod.13 for ; Fri, 02 Mar 2018 22:13:22 -0800 (PST) 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=Kreuap8gKjW1z4Nw6/U1UEzejucRnlQJQpTHl8iPVO4=; b=dv+QTObT6n+pjY6YywTX32MNTxdRD3G3gM5Qx0C0K6X1Hg25t15sXozRTY/KQqCQ/P 2RAhwTFWd+1k1Cmval7KGH+Lqso1jZZdYJXkUglUJbJ05UGdmd8v8qGtbJQzRI79LTrT YN6iFMQh8iS0I5mEaLFoXCA94/h9zDUVL3/3vuXTMmKSQnhuuTRY7fd9BfmOAtgpFWcF HgkSQxbZbHF1bYtAXG1bM6oc9YAuiQOK/ZEXRYN3DVgqCMlMmBXcYzbhsU4KOcktwlL4 +Nap0uL4RuRwcbTlyrOEqZ8eOFkxdGJ7swcY+wYCzX+TJQdFFQbD4nntUcTthk5mJFP9 5KVg== 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=Kreuap8gKjW1z4Nw6/U1UEzejucRnlQJQpTHl8iPVO4=; b=colLFilzr39nARtNxCKWR+Ni41hHb9TKg6PS6vGuB+DkqNkOEUcOHHoaSSp/Ikui2z klX3FIozsdE6f6v3peroeoQqRKA1kIPujkhGGGp7tl8/F7j7lgBs8EnmLr0Yi5nZpNXx oNM5lWOuz06HGItqG/mo+MvHg79t5f+Xy3qzNP0wxILHygNiAKnlgi05WcLWKxISgGlx 4figIF5B3CoXklyZELX7iaFzUA0Av2YtquplvEt6xpRcLmc0sastabwfzTlhl+r+F5b/ fp1SHsi9NKsOxnKxKFwxLglBOdnz0EIt9lc4G2JvYfPRtGWbmYmvlNuglAN7pilvvzlD zisQ== X-Gm-Message-State: APf1xPBgnysjB47tqwAJ03kNC4iPW37fn20t2BSbCMOubjmL1DSvyhrt h2ht09wipPT7wEdx7YdqJUH7ZTVZaP6cwj0HyuY= X-Google-Smtp-Source: AG47ELtXU7/QWbNAzq9IwcTOYk1b24Kea2DrZusQavsT6UpQKjCbK34lR+klwNF6eVRmIHwdmBZ+ltyc7RqQfAxtCPU= X-Received: by 10.107.34.199 with SMTP id i190mr9527292ioi.185.1520057602333; Fri, 02 Mar 2018 22:13:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.80.134 with HTTP; Fri, 2 Mar 2018 22:13:21 -0800 (PST) In-Reply-To: References: <371h-oi4s-wny@FreeBSD.org> From: Oleg Lelchuk Date: Sat, 3 Mar 2018 01:13:21 -0500 Message-ID: Subject: Fwd: drm-next-kmod-4.11 and vaapi hardware acceleration To: freebsd-current@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 06:13:23 -0000 ---------- Forwarded message ---------- From: Oleg Lelchuk Date: Sat, Mar 3, 2018 at 1:12 AM Subject: Re: drm-next-kmod-4.11 and vaapi hardware acceleration To: Jan Beich Well, hopefully, this regression will be fixed soon. On Sat, Mar 3, 2018 at 12:14 AM, Jan Beich wrote: > Oleg Lelchuk writes: > > > I run 12-CURRENT-r330303. My cpu is Haswell. After compiling > > drm-next-kmod-4.11 and libva-intel-driver, I get garbled videos in both > mpv > > and vlc when the vaapi hardware acceleration is enabled. I had no such > > problem with the previous version of drm-next-kmod. Is it possible that > > libva-intel-driver-2.1 and drm-next-kmod-4.11 are not fully compatible > with > > one another? Please tell me what I should do to resolve this issue. > > See also https://github.com/FreeBSDDesktop/kms-drm/issues/32 > From owner-freebsd-current@freebsd.org Sat Mar 3 07:20: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 59027F4627E for ; Sat, 3 Mar 2018 07:20:03 +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 EB165723AE for ; Sat, 3 Mar 2018 07:20:02 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1es1Sa-0006bD-Fx for freebsd-current@freebsd.org; Sat, 03 Mar 2018 08:20:00 +0100 Received: from [::1] (port=34756 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1es1Sa-0003HH-C9 for freebsd-current@freebsd.org; Sat, 03 Mar 2018 08:20:00 +0100 Received: from mx4.freenet.de ([195.4.92.14]:47874) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1es1Qd-0002Gs-8E for freebsd-current@freebsd.org; Sat, 03 Mar 2018 08:17:59 +0100 Received: from p4fd9effe.dip0.t-ipconnect.de ([79.217.239.254]:34118 helo=freebsd-t420.fritz.box) by mx4.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1es1Qd-0004zC-1m for freebsd-current@freebsd.org; Sat, 03 Mar 2018 08:17:59 +0100 Date: Sat, 3 Mar 2018 07:18:07 +0100 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Re: drm-next-kmod regression Message-ID: <20180303061807.GA9357@freebsd-t420.fritz.box> References: <20180302164045.GA45988@freebsd-t420.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: User-Agent: Mutt/1.9.3 (2018-01-21) X-Originated-At: 79.217.239.254!34118 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 07:20:03 -0000 On Sat, Mar 03, 2018 at 06:24:55AM +0100, Jan Beich wrote: >Manuel Sthn writes: > >> Hi, >> the last drm-next-kmod worked fine on my Lenovo T420 with i5-2520M and >> a HD Graphics 3000. After the update to the actual version (4.11) from >> ports, I'm seeing regression in form of a very slow xfce4-desktop. The >> slowness starts after some short time. Slow means for example that I >> can type faster than the terminal prints the chars or when i move >> windows they lag extremely behind the mouse's motion. >> >> One entry in Xorg.0.log caught my attention: >> [ 128.266] (EE) intel(0): Failed to submit rendering commands (Bad >> address), disabling acceleration. > >Did you build xf86-video-intel with SNA option enabled or have >Option "AccelMethod" "SNA" in xorg.conf? If so see also # pkg info xf86-video-intel-2.99.917.20180214 | grep -A2 Options Options : SNA : off UXA : on # cat /usr/local/etc/X11/xorg.conf.d/driver-intel-mode.conf Section "Device" Identifier "Intel Graphics" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" EndSection From owner-freebsd-current@freebsd.org Sat Mar 3 12:21: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 4752BF37090 for ; Sat, 3 Mar 2018 12:21:27 +0000 (UTC) (envelope-from listjm@club.fr) Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6ABD7EB55 for ; Sat, 3 Mar 2018 12:21:26 +0000 (UTC) (envelope-from listjm@club.fr) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) by msfrf2619.sfr.fr (SMTP Server) with ESMTP id 424EE1C00042A for ; Sat, 3 Mar 2018 13:14:32 +0100 (CET) Received: from [192.168.1.51] (125.164.7.84.rev.sfr.net [84.7.164.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: juanmolina@sfr.fr) by msfrf2619.sfr.fr (SMTP Server) with ESMTPSA; Sat, 3 Mar 2018 13:14:31 +0100 (CET) Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=juanmolina@sfr.fr From: Juan =?iso-8859-1?b?UmFt824=?= Molina Menor Subject: Question mark on Lua menu box To: FreeBSD-Current , Kyle Evans References: <2AFF3AE4-8740-4776-9D8D-7D709EE051C6@gmail.com> <1b9e58fe-2616-b04b-13c2-fee78a33ad6e@club.fr> Message-ID: <06e8dff0-4fc3-6ede-eba2-9e51e73e849e@club.fr> Date: Sat, 3 Mar 2018 13:14:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: X-sfr-mailing: LEGIT Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 12:21:27 -0000 > On 02/03/18 12:31, Kyle Evans wrote: >> On Fri, Mar 2, 2018 at 6:06 AM, Renato Botelho wrote: >>> Kyle, >>> >>> I've moved to Lua loader to help testing and it worked fine. The only >>> odd thing I noted is the menu box with odd chars as you can see at [1]. >>> >>> My laptop is running a recent current (r330275) with ZFS and UEFI. >>> >>> [1] https://imgur.com/a/kIQ0O >>> -- >>> Renato Botelho >>> >> >> Hi, >> >> Thanks for testing! =) Can you give it a shot with EFI boot after >> r330281 (just committed), please? >> >> I think our working theory is that we were printing newlines along >> with our box-drawing characters, and that could be problematic. The >> new version handles all of that a little better and respects >> loader_menu_frame to boot. Hi! The drawing issue was still there after updating to r330281, but pushing it up to r330287 has solved it. Thanks! From owner-freebsd-current@freebsd.org Sat Mar 3 18:14:14 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 3B223F2EFA7 for ; Sat, 3 Mar 2018 18:14:14 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-yb0-x229.google.com (mail-yb0-x229.google.com [IPv6:2607:f8b0:4002: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 C8C156E7A4 for ; Sat, 3 Mar 2018 18:14:13 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x229.google.com with SMTP id v8-v6so4459681ybk.6 for ; Sat, 03 Mar 2018 10:14:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:from:date:message-id:subject:to; bh=Xd/FqtO4asw80/bvQ3szV394CiysADDG99ji0aRdrcE=; b=SJ0TvpM4q2Lg2H2GuP8MB9NRZ7ocfv9lVn5Wlwd7EouJVrwcA/JqQDiw8ohJT/NNZK 4IXc4O2wAaoubtzBNPY+rHxx0l5IKNU4zVKD8/8hqyVF9frGQ5wS7HHo4cEtvf032++I ULazraXGdhc6HyafyRP6GZrskqlIixA/U2ufA= 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=Xd/FqtO4asw80/bvQ3szV394CiysADDG99ji0aRdrcE=; b=XAGic6bnGyNOMM67BpAu+xCgJl8PQ+kOXV2XLEJSz+34eSjk/RJm3SKJTQQcxTwWJ/ z2QDNXARz9ap3MlqEx0mLSQzv71fyrjt3/2DUIb9xmWVDTJTRzzs3/rE+9HChodMRXsL +2Azfp2IHNv8UakZ+kjktBIwZgn6GhQq3PfNLW8C+HksKHV7UGzhvQqw7K2Ha/WRxhCC 8xHykR+Dlq6UWa/UDJmkFMhytHivcj/cmBrSrLl23bYb351Xwc/RTocvfNaJzbrQfgAE UJ25Hw/lTE4dCFo4O/5GWP3hbPxfLBC+NcMFpjCMAPguLW6qL7vSxPrYDfcnbO0YEeC6 A6NQ== X-Gm-Message-State: APf1xPCnxYBM5nte9MW+LHDGoEPMLlW3oxKf0y/7d1vxD7d5k4ycVkYD rW5AnK/97GTu143MomQd9r4gSXYtB50XUdrtXXeaXuJc X-Google-Smtp-Source: AG47ELu6ag8h1NQF+K0xN097ROCYwEOSnkbBhjAWwfUwL7nL53h8oZPnTGG++nsbRX7kxtmcDFjyA9Fn65lUYOcFlEw= X-Received: by 2002:a25:7b06:: with SMTP id w6-v6mr6022918ybc.69.1520100852929; Sat, 03 Mar 2018 10:14:12 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:23d2:0:0:0:0:0 with HTTP; Sat, 3 Mar 2018 10:13:42 -0800 (PST) From: Eitan Adler Date: Sat, 3 Mar 2018 10:13:42 -0800 Message-ID: Subject: building current with meta mode To: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 18:14:14 -0000 #make toolchain ... Building /srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full c++: error: no such file or directory: '/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminimal.a' *** Error code 1 Stop. make[1]: stopped in /srv/src/fbsd/head/usr.bin/clang/clang-tblgen .ERROR_TARGET='clang-tblgen.full' .ERROR_META_FILE='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full.meta' .MAKE.LEVEL='1' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='/usr/bin/c++ -O2 -pipe -I/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvm -I/srv/src/fbsd/head/lib/clang/include -I/srv/src/fbsd/head/ contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DLLV M_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"\" -ffunction-sections -fdata-sections -isystem /srv/obj/srv/src/fbsd/head/stage/freebsd12-am d64/usr/include -DHOSTPROG -gline-tables-only -fstack-protector-strong -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compa re -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch - Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -Wl ,--gc-sections -Wl,-rpath-link,/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib -o clang-tblgen.full ClangASTNodesEmitter.o ClangAttrEmitter.o ClangC ommentCommandInfoEmitter.o ClangCommentHTMLNamedCharacterReferenceEmitter.o ClangCommentHTMLTagsEmitter.o ClangDataCollectorsEmitter.o ClangDiagnosticsEmitter .o ClangOptionDocEmitter.o ClangSACheckersEmitter.o NeonEmitter.o TableGen.o /srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminima l.a -L/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib -lncursesw -lpthread;' .CURDIR='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen' .MAKE='make' .OBJDIR='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen' .TARGETS=' all' DESTDIR='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64' LD_LIBRARY_PATH='' MACHINE='host' MACHINE_ARCH='amd64' ... Stop. make: stopped in /srv/src/fbsd/head .ERROR_TARGET='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen.host' .ERROR_META_FILE='' .MAKE.LEVEL='0' MAKEFILE='' .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' _ERROR_CMD='.PHONY' .CURDIR='/srv/src/fbsd/head' .MAKE='make' .OBJDIR='/srv/obj/srv/src/fbsd/head/amd64.amd64' .TARGETS='toolchain' DESTDIR='' LD_LIBRARY_PATH='' MACHINE='amd64' MACHINE_ARCH='amd64' MAKEOBJDIRPREFIX='' MAKESYSPATH='/srv/src/fbsd/head/share/mk' MAKE_VERSION='20170510' PATH='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/sbin:/srv/obj/srv/src/fbsd/head/stage/free bsd12-amd64/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/sbin:/home/eax/bin:/opt/local/libexec/ccache:/usr/local/libexec/ccache:/home/eax/.cargo/bin:/ Users/eax/.local/bin:/home/eax/.local/lib/npm/bin:/home/eax/.gem/ruby/2.5.0/bin:/home/eax/.rvm/bin:/home/eax/Library/Python/3.6/bin:/home/eax/Library/Python/2 .7/bin:/opt/local/sbin:/opt/local/bin:/opt/local/bin/pear:/opt/local/lib/mariadb-10.2/bin:/usr/local/mysql/bin:/opt/local/libexec/perl5.24/sitebin:/home/eax/p erl5/bin:/home/eax/Library/Android/sdk/platform-tools:/home/eax/.luarocks/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' SRCTOP='/srv/src/fbsd/head' OBJTOP='/srv/obj/srv/src/fbsd/head/amd64.amd64' @ 1520100350 [2018-03-03 18:05:50] Failed toolchain seconds=351 make toolchain 181.64s user 100.10s system 80% cpu 5:51.48 total; max RSS 165028Ki -- Eitan Adler From owner-freebsd-current@freebsd.org Sat Mar 3 18:46: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 E1463F313D1 for ; Sat, 3 Mar 2018 18:46:05 +0000 (UTC) (envelope-from bryan-lists@shatow.net) Received: from mail.xzibition.com (mail.xzibition.com [52.11.127.251]) (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 7A70A70004 for ; Sat, 3 Mar 2018 18:46:04 +0000 (UTC) (envelope-from bryan-lists@shatow.net) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 654D48C5B; Sat, 3 Mar 2018 18:46:03 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id vXhwSJ1n8V6n; Sat, 3 Mar 2018 18:46:00 +0000 (UTC) Subject: Re: building current with DIRDEPS_BUILD [was meta mode] DKIM-Filter: OpenDKIM Filter v2.10.3 mail.xzibition.com B81648C52 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shatow.net; s=mxc204805312015; t=1520102760; bh=6otIto1Lc44kUlgBZF1rN4TAAmJo0VjoW20AGYZbuDo=; h=Subject:To:References:From:Date:In-Reply-To; b=WTVIWZzZE+PdtjwWGinPCdnLAShXPyBi5sJLEHugjjpi5cMWNleDckA+b8OA2b+XJ ePUPxZt8UrtlkAT8CWzT7EsS7M8Ot4/qk3HM2m0+K76byikRQac8EaBZAKk3yCT1F4 LBY0/kat/iZ3rvz9zGCXPN26Gv2tXm2ZCkkbn6kNOTc6RQDv1i8g9BBcGv979KAYaK ACMGWUhqlZ7x5Mkz++ES9Ry5jqEPKtqnEfcMzzoz62uUSrUF/4g/mO840ltypPGJ2Q e2AQXHU11m34Ij9jN1OS0/GgWzexSnciUoplddz2evkO6IvEWppsYpo1n9TJmb1brO x0p9xFrXo0b5Q== To: Eitan Adler , freebsd-current Current References: From: Bryan Drewery Message-ID: <54a44f3d-26cc-21ae-beb5-53d565c9d15e@shatow.net> Date: Sat, 3 Mar 2018 10:46:01 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; 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-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 18:46:06 -0000 On 3/3/2018 10:13 AM, Eitan Adler wrote: > #make toolchain > This is now known as DIRDEPS_BUILD. META_MODE is something different now, see man src.conf. This failure is not unexpected as the build breaks with LLVM updates. I'll work on a fix this next week. > ... > Building /srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full > c++: error: no such file or directory: > '/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminimal.a' > *** Error code 1 > > Stop. > make[1]: stopped in /srv/src/fbsd/head/usr.bin/clang/clang-tblgen > .ERROR_TARGET='clang-tblgen.full' > .ERROR_META_FILE='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full.meta' > .MAKE.LEVEL='1' > MAKEFILE='' > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' > _ERROR_CMD='/usr/bin/c++ -O2 -pipe > -I/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvm > -I/srv/src/fbsd/head/lib/clang/include -I/srv/src/fbsd/head/ > contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS > -D__STDC_CONSTANT_MACROS > -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DLLV > M_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"\" > -ffunction-sections -fdata-sections -isystem > /srv/obj/srv/src/fbsd/head/stage/freebsd12-am > d64/usr/include -DHOSTPROG -gline-tables-only -fstack-protector-strong > -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable > -Wno-tautological-compa > re -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function > -Wno-enum-conversion -Wno-unused-local-typedef > -Wno-address-of-packed-member -Wno-switch - > Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses > -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ > -Wno-c++11-extensions -Wl > ,--gc-sections -Wl,-rpath-link,/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib > -o clang-tblgen.full ClangASTNodesEmitter.o ClangAttrEmitter.o ClangC > ommentCommandInfoEmitter.o > ClangCommentHTMLNamedCharacterReferenceEmitter.o > ClangCommentHTMLTagsEmitter.o ClangDataCollectorsEmitter.o > ClangDiagnosticsEmitter > .o ClangOptionDocEmitter.o ClangSACheckersEmitter.o NeonEmitter.o > TableGen.o /srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminima > l.a -L/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib > -lncursesw -lpthread;' > .CURDIR='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen' > .MAKE='make' > .OBJDIR='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen' > .TARGETS=' all' > DESTDIR='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64' > LD_LIBRARY_PATH='' > MACHINE='host' > MACHINE_ARCH='amd64' > ... > > Stop. > make: stopped in /srv/src/fbsd/head > .ERROR_TARGET='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen.host' > .ERROR_META_FILE='' > .MAKE.LEVEL='0' > MAKEFILE='' > .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose' > _ERROR_CMD='.PHONY' > .CURDIR='/srv/src/fbsd/head' > .MAKE='make' > .OBJDIR='/srv/obj/srv/src/fbsd/head/amd64.amd64' > .TARGETS='toolchain' > DESTDIR='' > LD_LIBRARY_PATH='' > MACHINE='amd64' > MACHINE_ARCH='amd64' > MAKEOBJDIRPREFIX='' > MAKESYSPATH='/srv/src/fbsd/head/share/mk' > MAKE_VERSION='20170510' > PATH='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/sbin:/srv/obj/srv/src/fbsd/head/stage/free > bsd12-amd64/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/sbin:/home/eax/bin:/opt/local/libexec/ccache:/usr/local/libexec/ccache:/home/eax/.cargo/bin:/ > Users/eax/.local/bin:/home/eax/.local/lib/npm/bin:/home/eax/.gem/ruby/2.5.0/bin:/home/eax/.rvm/bin:/home/eax/Library/Python/3.6/bin:/home/eax/Library/Python/2 > .7/bin:/opt/local/sbin:/opt/local/bin:/opt/local/bin/pear:/opt/local/lib/mariadb-10.2/bin:/usr/local/mysql/bin:/opt/local/libexec/perl5.24/sitebin:/home/eax/p > erl5/bin:/home/eax/Library/Android/sdk/platform-tools:/home/eax/.luarocks/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin' > SRCTOP='/srv/src/fbsd/head' > OBJTOP='/srv/obj/srv/src/fbsd/head/amd64.amd64' > @ 1520100350 [2018-03-03 18:05:50] Failed toolchain seconds=351 > make toolchain 181.64s user 100.10s system 80% cpu 5:51.48 total; max > RSS 165028Ki > -- Regards, Bryan Drewery bdrewery@freenode/EFNet From owner-freebsd-current@freebsd.org Sat Mar 3 21:19: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 1BCE5F3D41F for ; Sat, 3 Mar 2018 21:19:21 +0000 (UTC) (envelope-from lists@eitanadler.com) 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 A77117713F for ; Sat, 3 Mar 2018 21:19:20 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: by mail-yb0-x232.google.com with SMTP id w9-v6so819544ybe.13 for ; Sat, 03 Mar 2018 13:19:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=o9INVVaQg94GYEZs901rYyWcKH4wX4xmp/wGjamtcb4=; b=fYRedojfdvuyyq3CyjH6Svo3AvmzXdr9iPWLLc8pmopvT9tBF0fUnE+dpW0EWMJEct 4WjWsoSdE2NfZc4OKJ/n8rqva/CdugbH7irEnV6vsXJ09JHmpi1BNdOzNwUd0rmG2D3P dnfQMDP7XSEkgpOaue2LopVfPIGOeoXOvNaUE= 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=o9INVVaQg94GYEZs901rYyWcKH4wX4xmp/wGjamtcb4=; b=neAkXID2Psy0dIWbbU2MdNEkdbYZtmi4VwaQfKdccptvAHD8aH0OUPVl5sEfhBUqk/ obpUq4GUrnOh51z5uYTSuymRhpV2U1wx6md7cEZSbz3NW+zRhIwQFp2inpSgGY0NGUx0 dpQqXpho+UAfkomNXn7B3yDLG+ggsYSls+v4L03hpnwFZtkWhMB3GFr01CVcLIwDrvC7 DhkX7cq4lLiS7bigQ1sHWkF/NyMgamKWtRovZLkVQ/fsqiNzdBp6882GpKlqymwsDkwV Ng1d4dKrbp7lc+5PE/yhSBvq2XHb9qiaj26wabTFfan3ZlWFwiyA26MfabAwndm/iyv8 yeDA== X-Gm-Message-State: AElRT7GpXvokVNpOniH8Au/gasDu2MbJhePohmCzgq1rwIqRwBv8lvHc x4fEmqpBDJM5MYMQqtnJmMKP5E5WiaFisBZOA8ipSRpN X-Google-Smtp-Source: AG47ELsAIoAka6KEOr7cjDMUjExkJpUP1DyaCAjTOTwqmExfysSCk7K3N95fG8DbHCP778yq8Tbcfl5RsjZ8EoZiORQ= X-Received: by 2002:a25:ae5b:: with SMTP id g27-v6mr1637847ybe.87.1520111959713; Sat, 03 Mar 2018 13:19:19 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a25:23d2:0:0:0:0:0 with HTTP; Sat, 3 Mar 2018 13:18:49 -0800 (PST) In-Reply-To: References: From: Eitan Adler Date: Sat, 3 Mar 2018 13:18:49 -0800 Message-ID: Subject: Re: unable to build head - iconv issues To: freebsd-current Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 21:19:21 -0000 On 2 March 2018 at 20:22, Eitan Adler wrote: > uname -a: FreeBSD develop 12.0-CURRENT FreeBSD 12.0-CURRENT #0 > r329949: Sat Feb 24 07:58:23 UTC 2018 > eax@fasteagle:/srv/obj/fbsd/head/srv/src/fbsd/head/amd64.amd64/sys/GENERIC > amd64 > > src-env.conf: > > MAKEOBJDIRPREFIX=/srv/obj With some help from bdrewery the issue was that this needed to be MAKEOBJDIRPREFIX?=/srv/obj instead. -- Eitan Adler From owner-freebsd-current@freebsd.org Sat Mar 3 22:30: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 E9315F41C51; Sat, 3 Mar 2018 22:30:25 +0000 (UTC) (envelope-from timmcgrawfan@protonmail.com) Received: from mail3.protonmail.ch (mail3.protonmail.ch [185.70.40.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.protonmail.ch", Issuer "QuoVadis Global SSL ICA G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8235079B8E; Sat, 3 Mar 2018 22:30:25 +0000 (UTC) (envelope-from timmcgrawfan@protonmail.com) Date: Sat, 03 Mar 2018 17:30:14 -0500 To: "freebsd-advocacy@freebsd.org" From: John Darrah Cc: "freebsd-current@freebsd.org" Reply-To: John Darrah Subject: FreeBSD has a politics problem Message-ID: Feedback-ID: VvheuvgUquOYdMb7y1Y-WM9EGdLMAd7SZ9qvt84-dBa3ore_6mxdpjyoPCJwIxNi6B13ZdwwmG7sESPnOYqtmw==:Ext:ProtonMail MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.1 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.protonmail.ch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 22:30:26 -0000 FreeBSD recently introduced an updated Code of Conduct that developers and members must adhere to. There has been much backlash online about it and about introducing identity politics into a technical OS project in general. The Code of Conduct was adopted from the "Geek Feminism" wiki's version, which claims (among other things) that racism against whites doesn't exist, sexism against men doesn't exist, and that certain protected classes of people should not be criticised. Emails of the internal discussion about this controversial Code of Conduct have now been leaked publicly, painting a picture of the disagreement in the FreeBSD project about how this was handled. A number of developers, particularly benno@, phk@ and des@, have used racis= t and sexist remarks against those criticising the far-reaching project polic= y change, saying that the concerns about the policy essentially boil down to "white male privilege" and being "on the wrong side of history". Other developers expressed concern about the policy being thrown upon them with no discussion or debate, as well as The FreeBSD Foundation's choice to pay an outside person (with donations from the users) to work on the Code of Conduct's enforcement. Said person identifies as a feminist. Mods on BSD and FreeBSD-related subreddits are censoring posts, removing threads, and banning users for posting the link. Colin Percival is among the mods doing the removal. FreeBSD forum mods are also cracking down and eliminating any discussion. Censorship is not the way to win culture wars. This file is an email archive in MBOX format. You can open it with any email client (including the mail or mutt commands) or view it as plaintext with any text editor. It contains just over 200 emails. View: https://privatebin.net/?4c0fb59e63e8271e#irS3KFaEdtuFxsVM4xzQ4/llXLhSz0oZLV= 9WuOEUHBc=3D Download: https://mega.nz/#!xBpHBSAb!ENyoYPopqGVlx320X-a4ecpRjJBtPvd9jmRT9h57eao https://my.mixtape.moe/nhybsi.mbox I encourage you to read and form your own opinions, especially with regard to how the project is handling donation money. From owner-freebsd-current@freebsd.org Sat Mar 3 23:32:11 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8BE06F45FB3; Sat, 3 Mar 2018 23:32:11 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.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 29B677CD8A; Sat, 3 Mar 2018 23:32:10 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f52.google.com with SMTP id e64so5959538ita.5; Sat, 03 Mar 2018 15:32:10 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=neiY6hOGZUSbMumFixrKyxaiB18lHyApBzgQrWa1ES4=; b=ueqT3G0SQi7dH0Sf7geOLgt6+aQLRLvVKPXsRO39Bnfb8jfIHr9xaoY/kGN5Qnh5zl SdLmhEqgoUz7I5sKz+yBRHb9zansJV+JEa9Ts8TCvFf5fv4NAVGYFJlpzqxQu40xU2NE MOQ8oRTCNr12k2Uou0ovFINbKVD0Bk3A9aLNF/I43tmA4G4Bw0AWsDrDyioGiwc6GZYI efd+sdVwvy++845YwCnFfIXtnypU1HUC2JcEkBIiwhRModeRbyFuQSpCwoUukN/BRsfO KwVTExkMqYYBf8mCZFlYBNP5PW/JgTZfIgzPK1Iix8fVq0ijWY1ylHxvmuuCyjEnZcP0 A5xw== X-Gm-Message-State: AElRT7EJBYHN26tHsEbRHnjHJj/wnGAwWffK5pKtKvoAqgKMs8yBEEw7 K+vLBaMSnHE0gbO6QEPYOfbZiQGk X-Google-Smtp-Source: AG47ELuAz52Oi9/T9pPYuo7bHuRz70Df3FvduXUlCsOLZszXXZke42Vd/9QTJhJqwiN3rR60TYGRsg== X-Received: by 10.36.83.142 with SMTP id n136mr8758541itb.0.1520119545201; Sat, 03 Mar 2018 15:25:45 -0800 (PST) Received: from mail-it0-f43.google.com (mail-it0-f43.google.com. [209.85.214.43]) by smtp.gmail.com with ESMTPSA id 185sm2514284itw.44.2018.03.03.15.25.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Mar 2018 15:25:44 -0800 (PST) Received: by mail-it0-f43.google.com with SMTP id n7so5549416ita.5; Sat, 03 Mar 2018 15:25:44 -0800 (PST) X-Received: by 10.36.161.2 with SMTP id y2mr2224093ite.53.1520119544283; Sat, 03 Mar 2018 15:25:44 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.2.30.149 with HTTP; Sat, 3 Mar 2018 15:25:43 -0800 (PST) In-Reply-To: References: From: Conrad Meyer Date: Sat, 3 Mar 2018 15:25:43 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: FreeBSD has a politics problem To: John Darrah Cc: "freebsd-advocacy@freebsd.org" , "freebsd-current@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 23:32:11 -0000 John, A good portion of your original email happens to be inaccurate or misleading. In the spirit of good faith discussion, I'm going to assume you're just accidentally misinformed, and not willfully misrepresenting things. So, some corrections and clarifications follow. If you have further questions about the code of conduct, I suggest reaching out to the drafting committee or core directly. They're nice people, they don't bite, and they're happy to help clarify intent and nuance. Thanks. On Sat, Mar 3, 2018 at 2:30 PM, John Darrah wrote: > FreeBSD recently introduced an updated Code of Conduct that developers and > members must adhere to. There has been much backlash online about it and > about introducing identity politics into a technical OS project in general. > The Code of Conduct was adopted In part, with editorial review and modification by a committee of conscientious project members. > from the "Geek Feminism" wiki's version, > which claims (among other things) that racism against whites doesn't exist, This claim is factually erroneous. The Geek Feminism example anti-harassment policy simply makes no such claim. (Furthermore, criticizing the Geek Feminism document is wholly off-topic for FreeBSD. Our code of conduct is not identical to GF's example policy. The only conduct document relevant to FreeBSD is the one at https://www.freebsd.org/internal/code-of-conduct.html .) > sexism against men doesn't exist, This claim is also objectively absent from the plain language of either document. > and that certain protected classes of > people should not be criticised. Again, this hysterical claim comes from blue sky. > A number of developers, particularly benno@, phk@ and des@, have used racist > and sexist remarks Again, this is a claim made without any evidence. I've briefly re-skimmed the developers discussion on this topic and don't see any examples. (And, this accusation is so far outside of Benno's demeanor as to be completely laughable.) phk@ and des@ have used less conciliatory language but I still do not see any sexist or racist remarks. > against those criticising the far-reaching project policy > change, saying that the concerns about the policy essentially boil down to > "white male privilege" and being "on the wrong side of history". They're entitled to their opinions, as you are. Note that neither des@ nor phk@ sit on or represent the Core team. > Other developers expressed concern about the policy being thrown upon them > with no discussion or debate, as well as The FreeBSD Foundation's choice > to pay an outside person (with donations from the users) to work on the > Code of Conduct's enforcement. The Foundation chooses how to spend donation dollars at its sole discretion. That's the deal with 501(c)(3) charities. If you want to pick and choose how your donated dollars are spent, Linux Foundation is a 501(c)(6). > Said person identifies as a feminist. We don't object to contribution from people who identify as Republican, Catholic, or Pastafarian. Why do you think someone who identifies as a feminist is incapable of doing a good job advising the drafting committee? > Mods on BSD and FreeBSD-related subreddits are censoring posts, removing > threads, and banning users for posting the link. This is a misleading oversimplification. FreeBSD-the-project doesn't control or have any moderation privileges on BSD-topic subreddits. The only active moderator on one of the subreddits (freebsd) isn't even a developer, just some random reddit user who happened to register long ago. Colin Percival happens to have moderation privileges on the other subreddit (BSD), but again, is acting on his personal volition. He does not sit on nor represent the Core team. Most discussions on the code of conduct in both locations have been left in place, despite fairly low quality discussion. (The usual name-calling, spreading of outright FUD, othering, etc etc.) The few posts that have been removed were outright, low-effort trolling. Not any kind of nuanced criticism of the actual code of conduct. Note that links to discussion on the BSD subreddits have been shared in high drama, non-technical subreddits like r/Drama, r/KotakuInAction, and r/SJWHate, likely leading to an influx of users from those other spaces. > Colin Percival is among the mods doing the removal. Colin can speak to what has been moderated. Removed subjects and comments are still easily discovered on reddit archive sites, e.g., https://ceddit.com/r/BSD . You can judge whether anything of value was lost. (I think not, but that's just my opinion.) Clearly, discussion has not been eliminated. There's tons of active "discussion" going on. I don't think it's particularly valuable discourse because the same misrepresentations and outright falsehoods are repeated over and over again, but it certainly hasn't been scrubbed clean by moderators (who are mostly not under control of the project anyway). What has been moderated is largely duplicate threads trying to game reddit's post ordering system to get repeated visibility, or low-effort trolling. > View: > https://privatebin.net/ > > Download: > https://mega.nz/ > https://my.mixtape.moe/ Please do not leak internal, private project emails. Conrad From owner-freebsd-current@freebsd.org Sat Mar 3 23:53: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 283E0F4739C for ; Sat, 3 Mar 2018 23:53:17 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-qt0-x233.google.com (mail-qt0-x233.google.com [IPv6:2607:f8b0:400d:c0d::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 BE3927DCA5 for ; Sat, 3 Mar 2018 23:53:16 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: by mail-qt0-x233.google.com with SMTP id c7so16372699qtn.3 for ; Sat, 03 Mar 2018 15:53:16 -0800 (PST) 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 :cc; bh=y1v5ht39jzRzGHxOqsJXw0dbSOfPe6/68J7T+e+xuxg=; b=enXNdhWFfU8QriRFVl4Uh8vSDTEfGr0Lgli177hjdRuhywleXlOnkhxBVTbqC5+iu0 7aYm6YMf83f6duC3pUKBKSIxhgA/vD1y52csVNWXpGUozrv1+jBUrYCm2tLKb+HpGcw/ x/Wq4VIQLDvuTUnGzGMcR8LwprxIPkifopydyqoL9XveU4LuOTy3x7P3GD7NFEQVf3+K T27k0S+zy4aHQuFlIGFMMMzGdUOjS3ZN4jm9AlQ86XQOQMMr121DEOxK16jq1BxgTPBY 8RH6y1YUBeE7tdyMpOk8KN5zMq5h841PeqVSHJEArCVvdJ/GpcQsZjj9TpeAlH2xKO1m ZUBw== 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=y1v5ht39jzRzGHxOqsJXw0dbSOfPe6/68J7T+e+xuxg=; b=c+ajf0LLVS9cKo413pcKMfNV5TctHGQktFXqmH9qB1JrSbUPQSBstgNGgJXpKH143s LOXYfcoC6+lVOBXjvIRQ0SwWaXikATTEBMqaXlwI+03fct5XX4L+3v1X6BmZQw5YQ1LJ jZx1lJ6wK2Hc3L/zCKYfAciVeXkiFDKM3ef+pLqr1SOkhFJLtK7Lfh4bE47ssXxJ+Xm/ 92G7z7ruB/F8zBqZ5GPNmhsS7ri9ngXZv3eNAHY6hzcJ4EQdssHhH1JnzdEBd0q3HCgh f7XxTC6YZf1iLy2oAR1vkaxsju8CeCKCgzZuN6tqqvXsP1VF8eewlqwmIz8bTO9X4ZVQ 70hA== X-Gm-Message-State: AElRT7GphN7W2y4Nz6V+FRMtDtiPvwGZ22/MWbY2p6cEW9CuEk9xy+yN VJYACw5lBuWkp/rjhkJpOnfwotb3M7S7ffayjU8= X-Google-Smtp-Source: AG47ELvBzX2gaV0/fUNOJg6l0K9X9GNw1B0tXWHanBvF6sCh9eO5S2MmiiTSbw0hL9DBYO6GlG7ssKCIyy7aRpoXnLQ= X-Received: by 10.200.82.152 with SMTP id s24mr15025318qtn.63.1520121196268; Sat, 03 Mar 2018 15:53:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.237.32.200 with HTTP; Sat, 3 Mar 2018 15:53:15 -0800 (PST) In-Reply-To: References: <20180212085852.GA94212@kib.kiev.ua> From: Ryan Stone Date: Sat, 3 Mar 2018 18:53:15 -0500 Message-ID: Subject: Re: Panic in prison_alloc() on boot To: Konstantin Belousov Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: 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, 03 Mar 2018 23:53:17 -0000 To close the loop on this, the root cause ended up being a mistake on my end. This system had a rather convoluted boot process, and as a result of that was loading a nullfs.ko built for a months-old kernel. This setup accidentally worked for some time, but I guess some recent change to struct thread changed the ABI, causing the old nullfs.ko to be incompatible and fail to boot. Sorry for the noise, Ryan