From owner-freebsd-current@freebsd.org Sun May 6 07:30:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 13B4AFAA981 for ; Sun, 6 May 2018 07:30:43 +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 9E16869B57 for ; Sun, 6 May 2018 07:30:42 +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 1fFE80-0003QG-1P for freebsd-current@freebsd.org; Sun, 06 May 2018 09:30:40 +0200 Received: from [::1] (port=50252 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fFE7z-0000UR-Tr for freebsd-current@freebsd.org; Sun, 06 May 2018 09:30:40 +0200 Received: from mx3.freenet.de ([195.4.92.13]:58264) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fFE61-0007jw-R9 for freebsd-current@freebsd.org; Sun, 06 May 2018 09:28:37 +0200 Received: from p4fd9f223.dip0.t-ipconnect.de ([79.217.242.35]:56760 helo=freebsd-t450.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 1fFE61-0003YI-H1 for freebsd-current@freebsd.org; Sun, 06 May 2018 09:28:37 +0200 Date: Sun, 6 May 2018 09:28:35 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: freebsd-current@freebsd.org Subject: Re: Regression Resume Lenovo T450 Message-ID: <20180506072835.GA87831@freebsd-t450.fritz.box> References: <20180504060717.GA88565@freebsd-t450.fritz.box> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20180504060717.GA88565@freebsd-t450.fritz.box> User-Agent: Mutt/1.9.5 (2018-04-13) X-Spamscore: -5.9 (-----) X-Spamreport: Action: no action Symbol: FROM_HAS_DN(0.00) Symbol: TO_DN_NONE(0.00) Symbol: ASN(0.00) Symbol: NEURAL_HAM(-2.78) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: RCPT_COUNT_ONE(0.00) Symbol: MIME_GOOD(-0.10) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: RCVD_COUNT_ONE(0.00) Symbol: RCVD_TLS_ALL(0.00) Symbol: BAYES_HAM(-3.00) Message-ID: 20180506072835.GA87831@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 79.217.242.35!56760 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, 06 May 2018 07:30:43 -0000 On Fri, May 04, 2018 at 08:07:17AM +0200, Manuel Stühn wrote: > >Since some time now CURRENT runs very smoothly on my Lenovo T450 in >conjunction with drm-stable-kmod installed. WLAN, Suspense&Resume worked >out of the box (at least ... until now). Due to pkg(8) complaining about >wrong ABI of packages, I've made an update from r332385 (1200061) to >r333091 (1200062), and now the T450 does not resume anymore; i have to >hold the power button for some time to power it down. The >ZFS-Boot-Environment I've made beforehand updating is still capable of >resuming. > >I tried to find out which commit broke the resume for me by installing >older kernels, but even installing r332385 kernel (into the actual >r333091 userland) does not restore its capability to resume. > Some more testing has happened: Since I have a BootEnvironment capable of suspend/resume, I've tried some combinations of kernels (in fact, whole boot-folders) and unserlands. I copied the boot-folder from the BE r332385 (which works) into the current BE and restarted. This combination was NOT able to resume. But the other way around is (current boot-folder (r333091) in the r332385 based BootEnvironment) It seems to me, that not the kernel but either some change in userland or package broke the resume somehow. But I do not have a clue, which of those even can impact the resume procedure at all. Two packages came to my mind: 1. graphics/drm-stable-kmod, but the installed packages are identical for both, the "old" and the current BE. (both packages are installed from ports along with the respective buildworld+buildkernel) 2. The firmwares used by sysutils/cpupdate, but after replacing the firmware files with the firmwares from the old BE resume still doesn't work. Any ideas? -- Manuel From owner-freebsd-current@freebsd.org Sun May 6 11:47:43 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97FA0FB7220 for ; Sun, 6 May 2018 11:47:43 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward100j.mail.yandex.net (forward100j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D613C80EC5 for ; Sun, 6 May 2018 11:47:42 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback7g.mail.yandex.net (mxback7g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:168]) by forward100j.mail.yandex.net (Yandex) with ESMTP id 61EDA5D820BB; Sun, 6 May 2018 14:47:31 +0300 (MSK) Received: from smtp2o.mail.yandex.net (smtp2o.mail.yandex.net [2a02:6b8:0:1a2d::26]) by mxback7g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id GFh1hog8IC-lVR0oGhe; Sun, 06 May 2018 14:47:31 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1525607251; bh=nQmg3aQ0+QfKPc1nGhK/Dt2nZh5OAAKhKMi7n9y6AIs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=WaLHf0ahKog3OW6dVpPChpP4BLZM9ctqU9TOY4j/aWzIyt9QjSBs10F8jKCs1R+Mi WdbUunmG4MANPad1FOAQCvFp0GLyaOjULCRGn3CYgKz7PG99hEiCazs9MSNJwMjR1T RxY8lp6B03W7f9q6f0t+ZVUsd6BV5+oYFJSMLdy8= Received: by smtp2o.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 9xsgCyL9mb-lTbG96fs; Sun, 06 May 2018 14:47:29 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1525607249; bh=nQmg3aQ0+QfKPc1nGhK/Dt2nZh5OAAKhKMi7n9y6AIs=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=cFdJCFc5eS+/EQQp2C2P3//dE98lJtJYNAnHrwT8hd1BTw+NtaYw27JsNC/pEkwAO pZM0KfR6pefe4VtZ8O4A3wKJ36ImbTiJvzskSpNDXQwCr3L8JrN/Qy9o16x73Ik4+i CT7oyEnEFPBFlzQfUQxle/rPqdgp4xDJ8uZoV6k0= Authentication-Results: smtp2o.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: IGNORE_OSVERSION=yes -- can't install pkg To: bsd-lists@BSDforge.com, FreeBSD Current References: <7c58b8eb1bc3f83819c2aab6bfea322c@udns.ultimatedns.net> From: Boris Samorodov Openpgp: preference=signencrypt Autocrypt: addr=bsam@passap.ru; prefer-encrypt=mutual; keydata= xsFNBFKPjHIBEACwdrpPbV9pGnP/MFO0lsubC1ruUr7y79tnT/gWKlI3i8gPPS3GG5FVFwjM 9YsSv7H5wxKlHa7ufFa8BETQQF+tBWlOy5lGh0a55M9qNCY+jlnAbmRRNdrIpr8ywHHd3eIr DBafMB6CG5GIgEMJ1OBcHmNuIUOd1A8Esi4eGpd6NFRcT3O58dC8wHfEqpdCVVX+mrPEWAno Q72i0q+j6NtsyTNTFEiACiuXeW+h2xl4zj09rr1CXlCcBV4SQ20uxJ4gegGapAMXzXDUpvCD X1M8wcjlUVa44PtTvGj5OxhGypKZJnz1CQcIQJ4qjPxvg6p8PsGnAaEWfdXPL5CH5GUmuaUt qMRbzyR/Bo/K8bYMYl5o/YcAjXopkn4ij1H3KACqE5YWvEwcfiNKX++uhuVhtja34sOTWJl9 ilboFJ9C9RDq/zE6oxF4vBGMVWjF4qm88P2PXWULLPPyhg98NxFMbH0XXWnOUt0x8yqY2v0t kz2sWn1ft/o09gQ0aaUtzYvG+cLg3FeU0EeXYum+jdTKdA27uKtTmgRuwQ135XIf0+4M5hrX pw2dBh/JljkQiv1lhKiCQrVBdS52nRvRXaCo7t0OiRR4y7268LYPr7ellCq3Ywykdj8bWvmt szYcnYBi7wiftHCid8wR0bQdyGRUcuc4IH4fCf7hS8trSjukWQARAQABzSJCb3JpcyBTYW1v cm9kb3YgPGJzYW1ARnJlZUJTRC5vcmc+wsF9BBMBCAAnBQJSj4yzAhsDBQkJZgGABQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAAoJEJYOILA6P20ooagP/3r6OfyiGW5B3Fv1ylBWp8lzHZVD mI8pGW7J4ubizPsz6t+CHBofNvCkrxjW7C1WDq7qRDfgqL6rYBV6D6GMtdUm5oKmnyJNNET5 hXRP7/ljzYDaLbBaVY5Oidu7OBS4k6RRwlypo5vFaI7/YJp6iIm80eIC6MCmPJpsRqdsY6pj ng5/F8obspP+HfrORHYLYRg8mt0PLG6UwkkiOdP48z2X0Arhjbt2v5QCDwOzwerE7JfN3/P6 Knf1Soiki9vWw6CAaC5K/oo/tdbvfiUzrzxSAaV8K7HQ4dVqaKFxI5xQ2GnafnEfyPLBZQQR WdmYJcL1qwCk4D76VrN2whR94+ZczPFji6jGCxOUo4mM/hqwq44KF9xi7asZmZC7/LHZ11ac j8NMEPHQJ4nmB7q9of4Wwu9XeJUrTt7oY+AQKpmewRxab5K0EJDd9IyfQusNgHHVpF2Jpa7U MAxClPtWdoXfRSk3esxeLhu33WJOpVpAUVeLIXF9g6EokOflV/0rb0onjuSeisVihvX/eG20 8eiSomt3xYgM+2ijGWugm5ie6eHkv5o34fcG9oanG71t9QIb7IgJ36UnLYGUcOyrpByUGEfg bYQgSEgSiDBbZBZVdM+aT2kJgbqRRYeqaqjmIXvSzL4c7zSRqQXv6h0L/P11CbMjycVNQ6uo iiP0eu5vzsFNBFKPjHIBEADUsIZuXuLo8baU85CU+Mv4gdyHwXzgIeNEG28O7Iu9bssY+Gt+ NiLI+4ZpBeQDbFzBGvyA/UoYDfURdY3KT6lXl2qamRaFz7SDtXuGpN9jDVgU048bbMjN4nk/ vV5ioqWw3V0x7eOiBtUbb17P1CVnnl249KyjdtMDu8jf7KRe2KgiFXgoL5ZeiGuN4g4n17VT H9DQCXJhIYPl5d7NEeGaUVKtPTEE1mClNt048dF/euduFRomxpwgXsg+tkSdZb1ffinYuFa7 mSMLg96LubVaels2rqQu097OO9GFqxyoBFzXtRwCOl2LbRJpG2ktJisin1zEshHx8slMC0km veXQv4S/LL33TNFPhfrbTJddMQhcrjwe4kDtdGY3XtBV2VEjUGRs63BSjtHPAQWx/JQTaBwx 5IPwuJAs0H0eJwjNtq+ZunzM1Dgbbtq4rQPsgrPIrtjHSv+u6ORW2wmd5uHxGyvADB8YyYRj R6scSLzLp7KrcFmkGq3RJcB3aDYi9r4TXr/gSZk4P0swhEXqo9oiddwRo7tv6JboRwltLG1F o91W5H8pwV5iG/R0EsM2k/aIAMOTBiZ2Lkk0bBH62hd/mp4p08z0E12QL/IYbH7VuXtz9ToA KiMtAAKg4nDe58ILAkfEAhNNsStSMOEjlXMz/6n7gsRrLljS16nmgd+8FQARAQABwsFlBBgB CAAPBQJSj4xyAhsMBQkJZgGAAAoJEJYOILA6P20odvEP/0KAbaBFAyJqhwXmj4ta1i55rkd+ 6vc46Az4trNZ6H/0XOJK5v9JGW1mz5aOURzSaSCitqS9uQa1qMssggn7a2pDRYA6LPKd0xgF 9KT68QMApN3KOtpFgn1D8rV6wywovntl3CpubiaDEmBD/fD7wrHiG+KsFzR48Dqzoth94D82 zIlCzfhbKDUzPwgc5ipds48MuP150WTwyKvOytwZbH/0RBGlqw/jkA6z3P86We4TuD0RFHZl /hpuSNadbUkfAOYI0LUfSFz/uYds08Rjf/YIawjA34mZFsDsWuoHhHqjl/x9uHA/o553LSw7 TmW/oR1xja/sWBaub/9WG9ZwuhPFE25DIG2eFQdv9d7XR7dyF+SIIkhiq4TuhD8hYYWPnvfN nzI9pfq3b9ag31P1ZHjpy9WxDplW7nTQq1yGLYOsd8Hoeh+QCY7PC/Ws8N566kW0bcUM1d12 2ZXA5XS0EBabmaAccuFtrIMt86XXgPYUqDOW4N/qKdF1dG+bhPPlFN3Lx9Sf3fbbNvJaI1DY bPgGUnCzctuLLfiARaFdgACXVhJ8ZhB6h7zPBOK8SB/bVSOqxcZh9elnusnkelNg57Up1qX3 pgkTpbOtvicdN2gogQQvtV40Nljrxmu2o0MoMcyqAxVG7KhKUih38fFqqrWEpFsVaLJeFk1u 4YL+0DfP Message-ID: Date: Sun, 6 May 2018 14:47:28 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <7c58b8eb1bc3f83819c2aab6bfea322c@udns.ultimatedns.net> Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU 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: Sun, 06 May 2018 11:47:43 -0000 05.05.2018 18:26, Chris H пишет: > On Fri, 04 May 2018 22:57:52 -0700 said > >> I just setup a jail from a 12-CURRENT I built awhile ago. It has no ports >> tree. So I'm attempting >> to install svnlite. issuing pkg search svnlite returns >> The package management tool is not yet installed on your system. >> Do you want to fetch and install it now? [y/N]: y >> Bootstrapping pkg from >> pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/latest, >> please wait... >> Verifying signature with trusted certificate >> pkg.freebsd.org.2013102301... >> done >> [12current.localhost] Installing pkg-1.10.5... >> Newer FreeBSD version for package pkg: >> To ignore this error set IGNORE_OSVERSION=yes >> - package: 1200062 >> - running kernel: 1200054 >> Allow missmatch now?[Y/n]: >> >> Umm, what? Should I ignore this error? If so, why is there an error at >> all? >> I answered no. Guess I won't be able to use pkg(8) on this jail(8). :-( >> >> --Chris > OK the only reference[1] I can find regarding this, indicates that > answering "Y" > to Allow missmatch now? resulted in an ABI mismatch that caused pkg(8) > to be > unusable. > This is on an older version of 12, so I don't have anything that might have > appeared in UPDATING. I really need this jail to resolve accumulating > pr(1)'s > on ports(7) I maintain. FreeBSD project has packages for the latest HEAD. But you may build your own packages via poudriere. First, build the needed base system, then build needed packages. -- WBR, bsam From owner-freebsd-current@freebsd.org Sun May 6 22:32: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 EF7A0FC94D6 for ; Sun, 6 May 2018 22:32:12 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-io0-f177.google.com (mail-io0-f177.google.com [209.85.223.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CE0D6F9FB for ; Sun, 6 May 2018 22:32:12 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-io0-f177.google.com with SMTP id e78-v6so31544037iod.0 for ; Sun, 06 May 2018 15:32:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc:content-transfer-encoding; bh=T3W9JVE4Dp9yI3IUxq14raYfEE3qfi5cl4aa1mvabL4=; b=e3TSXyw++C41lWh2+4lyoV1Npy8lrZdlmuTwQY7r0CS7hrymyfaIx33MtgB8LeMqtb ZvzFCKUEu2LecGYEgWB8sBX6vgrP+2LfequiU5imMoP6+4cjG5CVeujFw96+Bm17gC69 J328f528Q36cY7nMze+/i6VKi0Kn6gUxj+t1+di84EurSuBxfcAn20tSiwZHQnixcxHn ou7v75iW4RZKxEXK6YeuiGOh9xmG2jd3sNx/VV9RnWq8m+7iujv4QJpkvRUtCo7CW/2I YmdiT/EfH03IqIQY3N+DuAX39pyaDzheyaFjjG3uo82jZO7aISN4QsrwK8QU7qkvOTAu 88Wg== X-Gm-Message-State: ALQs6tAJ8n+jWb578POAnyMoBf3H5L3ZM7I9K2C27azVUtOjJ7Lr5FGU MZvibniyzjxDelVzqvS42kM660x9 X-Google-Smtp-Source: AB8JxZroJs2ezszk09DwQrO3KQohdfnfIsPupmRArWyDi2CSZcEYXARxjAmK2Rp8qIrrJHC89fzzyw== X-Received: by 2002:a6b:264d:: with SMTP id m74-v6mr36853404iom.154.1525645931533; Sun, 06 May 2018 15:32:11 -0700 (PDT) Received: from mail-io0-f175.google.com (mail-io0-f175.google.com. [209.85.223.175]) by smtp.gmail.com with ESMTPSA id y25-v6sm4055133ioa.83.2018.05.06.15.32.10 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 May 2018 15:32:11 -0700 (PDT) Received: by mail-io0-f175.google.com with SMTP id r9-v6so31510829iod.6 for ; Sun, 06 May 2018 15:32:10 -0700 (PDT) X-Received: by 2002:a6b:3a87:: with SMTP id h129-v6mr10416176ioa.220.1525645930820; Sun, 06 May 2018 15:32:10 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 2002:a02:a40b:0:0:0:0:0 with HTTP; Sun, 6 May 2018 15:32:10 -0700 (PDT) In-Reply-To: <9D64510E-32AE-45DC-87EC-4DFB41B9369F@yahoo.com> References: <9D64510E-32AE-45DC-87EC-4DFB41B9369F@yahoo.com> From: Conrad Meyer Date: Sun, 6 May 2018 15:32:10 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] To: Mark Millard Cc: FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 06 May 2018 22:32:13 -0000 The same change as for powerpc needs to be made for riscv =E2=80=94 the (bcopy) trick =E2=80=94 to avoid expansion. Best, Conrad P.S., Mark, your email server is misconfigured and most/all of your emails get flagged as spam. I only saw this because I occasionally check the spam folder. On Sat, May 5, 2018 at 4:39 PM, Mark Millard wro= te: > --- bcopy.o --- > In file included from /workspace/src/sys/riscv/riscv/bcopy.c:39:0: > /workspace/src/sys/sys/systm.h:262:31: error: expected identifier or '(' = before '{' token > #define bcopy(from, to, len) ({ \ > ^ > /workspace/src/sys/riscv/riscv/bcopy.c:134:1: note: in expansion of macro= 'bcopy' > bcopy(const void *src0, void *dst0, size_t length) > ^~~~~ From owner-freebsd-current@freebsd.org Sun May 6 22:58:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E893FC9C59 for ; Sun, 6 May 2018 22:58:30 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x229.google.com (mail-it0-x229.google.com [IPv6:2607:f8b0:4001:c0b::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 D94BC7532D for ; Sun, 6 May 2018 22:58:29 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x229.google.com with SMTP id z6-v6so9265380iti.4 for ; Sun, 06 May 2018 15:58:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=hdCOeYALxQCcekDjzUC5siL9zI8lWfMijwqt2prmPcI=; b=OGUNHOfP6HKVP75q0D66TiEz+bMxbeUYzIJspcxkelm6v7bg7+S4qfiIa5CXNLnYm8 fFkM0DLzKj0gfdLNS4rRi4WO84bPpNkDYoKuGe78AJx6ROBvUbnLIHZtQCU5Qcje4Its iZr5VFK9l/AMSdifiebr0IgiOeNbRNFnmn5fDYsdZquJt0v9g5lrU1PKBQnPbszuxQ8g DhxsBnM7qrBy8KBZtqBRSZrHfP/t5seK6OLzj/UWJG1ILpuRG1qpzkgIcs40bsZyj4lN fp3ob+2A3+5p16Tz2KrAZ+Dhv6Nz2H+SnOxlR8VVVXliF4SHpr9p0q3M5U4aRBXGXq9R 1VYw== 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=hdCOeYALxQCcekDjzUC5siL9zI8lWfMijwqt2prmPcI=; b=AR8iKw+8ejFXJ88nhkDYOyhuls9yTJaNt76CIljhw/cICSIjas86kog7MFBXbdL3c+ ZYh0Y3pszLBfDmMKpLUCAqxeMkxj9DhDQQE/YNVUhGqWoVFSTxWgtI6KhTi0Q0ITQ0B8 SlF1uLX6TV0L42pOnz12ll4iGZqHf7TVkyYCk4hzg2KwEhORV0/X+QQ8rHwZVis7Pfwz qnaQqtlUqo34UeP542vUgaZ/+1rzx7aRADqq2NqbVaR8un6Z/kptSTSFQ8PkHYX4hO5I zEs3HD2xg0C9jS0rjLkEWr0SnWekbzmXYxSblBlxaohRWd0WOpUmyrWMLa+gRjttAkde Dnhg== X-Gm-Message-State: ALQs6tCB0tcp+5aNh5LMC1HHN1PE6eClTP8XlIUKpnIhD06gDz3nzqPu iqrZkAbmzf2GJHq0NBN2jv/PkHQeYnf2eeUQsJNqEQ== X-Google-Smtp-Source: AB8JxZpZ2gr8dtj6VfEdUDQN6U0qd7fjx2Zfk/kLD/ztoIiQzzO/iwFc+uOz5j+5Khzk5xFfofiE+y+giaX7UJE3PRs= X-Received: by 2002:a24:42c6:: with SMTP id i189-v6mr36178754itb.73.1525647508982; Sun, 06 May 2018 15:58:28 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a65a:0:0:0:0:0 with HTTP; Sun, 6 May 2018 15:58:28 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:1052:acc7:f9de:2b6d] In-Reply-To: References: <9D64510E-32AE-45DC-87EC-4DFB41B9369F@yahoo.com> From: Warner Losh Date: Sun, 6 May 2018 16:58:28 -0600 X-Google-Sender-Auth: BjESRxHpxq2JsYTf5yILkQ1Eg0Y Message-ID: Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] To: "Conrad E. Meyer" Cc: Mark Millard , FreeBSD 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, 06 May 2018 22:58:30 -0000 What we really need to do is to make bcopy a wrapper around memmove on all architectures, not just some. It's this lack of uniformity that's causing problems. Warner On Sun, May 6, 2018 at 4:32 PM, Conrad Meyer wrote: > The same change as for powerpc needs to be made for riscv =E2=80=94 the > (bcopy) trick =E2=80=94 to avoid expansion. > > Best, > Conrad > > P.S., Mark, your email server is misconfigured and most/all of your > emails get flagged as spam. I only saw this because I occasionally > check the spam folder. > > On Sat, May 5, 2018 at 4:39 PM, Mark Millard > wrote: > > --- bcopy.o --- > > In file included from /workspace/src/sys/riscv/riscv/bcopy.c:39:0: > > /workspace/src/sys/sys/systm.h:262:31: error: expected identifier or > '(' before '{' token > > #define bcopy(from, to, len) ({ \ > > ^ > > /workspace/src/sys/riscv/riscv/bcopy.c:134:1: note: in expansion of > macro 'bcopy' > > bcopy(const void *src0, void *dst0, size_t length) > > ^~~~~ > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > From owner-freebsd-current@freebsd.org Mon May 7 02:53:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5C739FCD907 for ; Mon, 7 May 2018 02:53:54 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic307-12.consmr.mail.ne1.yahoo.com (sonic307-12.consmr.mail.ne1.yahoo.com [66.163.190.35]) (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 E97078874A for ; Mon, 7 May 2018 02:53:53 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: pRy7ElcVM1n47eZ30Mzj_4ZwwmfFFWvUTRIENHa5NZ2gehvl4SyGxVwddESFfDs .RrheVufaMUMwJDYC9DUMAAlfSqLR7rLhMWFSychQ88umCZgaLDEz2WPuYYnPePuSWa8the25TaB Qdzuc9UrySZPQ_b_1pyAjFwkGWToQYWmS52V28PsICbtFIhWx5yrYdOwNWTRmRZ84b26eszG6FF6 h.uK0aOWAX2HoQpKlxaWh3dHA_gUvZuDelH0Dp7DuyQlATXszpxN2fCnBvkmBpuqEP6Z_5yZ7mmH HccodZ4sSc1_48QeShlrdzqWhoOljkqxAmSBvJtsyiEGTSl_jfUBcffgG0oWF9_nZASluCmY4ezM zp7xrBUDf7KnkfhiQX_HudzuHuydQrDMDJ.F0DRxc_aE89N76BlCZ1jFD5LL_rAqeDS_xQPtVXo6 vpJppVh0x10dPrLQPs61wZXg3D6M9BXW1zhWkQR_YDL6SjoBHeVOgi9lbzJ8YkC7KaEg5f.r0o9f bNm0huzGekd0g5Xkpp7gn9k1B0Iy_kL2lUycYho_IXrfgpIK4yLMW0.Dy__3HXNb604dD9pGQLum PTSVNKlnUZRVIy3ijfEZuU3bHWkxf0LliTiGBGbr029UwlY9_M7q5fXG20_9k6RAulxx26JLil46 6gF1sb7E- Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.ne1.yahoo.com with HTTP; Mon, 7 May 2018 02:53:52 +0000 Received: from c-76-115-7-162.hsd1.or.comcast.net (EHLO [192.168.1.158]) ([76.115.7.162]) by smtp424.mail.ne1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 65a09db5e9e52ef6b35440b2fc441c41; Mon, 07 May 2018 02:33:36 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] Message-Id: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> Date: Sun, 6 May 2018 19:33:34 -0700 To: FreeBSD Current , FreeBSD PowerPC ML X-Mailer: Apple Mail (2.3445.6.18) 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, 07 May 2018 02:53:54 -0000 Conrad Meyer cem at freebsd.org wrote on Sun May 6 22:32:13 UTC 2018, as part of a reply: > P.S., Mark, your email server is misconfigured and most/all of your > emails get flagged as spam. I only saw this because I occasionally > check the spam folder. I wrote back directly indicating that I'd need evidence in order to submit something to yahoo.com. Although, the original was not sent directly to Conrad, so he likely got the message directly from a freebsd-current server, with a yahoo.com's Email server as an intermediate stage. (I do not run my own servers.) The Email was composed in macOS's Mail.app [V11.3 (3445.6.18)]. Of course, that reply was likely classified as spam. If anyone else has such problems with the classification of my Emails and can send material that would allow reporting evidence to be submitted someplace, please do so. === Mark Millard marklmi26-fbsd at yahoo.com ( dsl-only.net went away in early 2018-Mar) From owner-freebsd-current@freebsd.org Mon May 7 07:56: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 DC93EFA9DA3 for ; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from smtp.freebsd.org (unknown [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8FA0C831BD; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from ivaldir.etoilebsd.net (etoilebsd.net [178.32.217.76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: bapt) by smtp.freebsd.org (Postfix) with ESMTPSA id 5FFD515CF1; Mon, 7 May 2018 07:56:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: by ivaldir.etoilebsd.net (Postfix, from userid 1001) id 392F649B71; Mon, 7 May 2018 09:56:16 +0200 (CEST) Date: Mon, 7 May 2018 09:56:16 +0200 From: Baptiste Daroussin To: Ian Lepore Cc: bsd-lists@BSDforge.com, FreeBSD Current Subject: Re: IGNORE_OSVERSION=yes -- can't install pkg Message-ID: <20180507075616.qtqplco6rasy4zbp@ivaldir.net> References: <7c58b8eb1bc3f83819c2aab6bfea322c@udns.ultimatedns.net> <1525538856.57768.293.camel@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="h5pmvhg5ne5od6pl" Content-Disposition: inline In-Reply-To: <1525538856.57768.293.camel@freebsd.org> User-Agent: NeoMutt/20180323 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, 07 May 2018 07:56:48 -0000 --h5pmvhg5ne5od6pl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, May 05, 2018 at 10:47:36AM -0600, Ian Lepore wrote: > On Sat, 2018-05-05 at 08:26 -0700, Chris H wrote: > > On Fri, 04 May 2018 22:57:52 -0700 said > >=20 > > >=20 > > > I just setup a jail from a 12-CURRENT I built awhile ago. It has no > > > ports > > > tree. So I'm attempting > > > to install svnlite. issuing pkg search svnlite returns > > > The package management tool is not yet installed on your system. > > > Do you want to fetch and install it now? [y/N]: y > > > Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/ > > > latest, > > > please wait... > > > Verifying signature with trusted certificate > > > pkg.freebsd.org.2013102301... > > > done > > > [12current.localhost] Installing pkg-1.10.5... > > > Newer FreeBSD version for package pkg: > > > To ignore this error set IGNORE_OSVERSION=3Dyes > > > - package: 1200062 > > > - running kernel: 1200054 > > > Allow missmatch now?[Y/n]: > > >=20 > > > Umm, what? Should I ignore this error? If so, why is there an error > > > at all? > > > I answered no. Guess I won't be able to use pkg(8) on this jail(8). > > > :-( > > >=20 > > > --Chris > > OK the only reference[1] I can find regarding this, indicates that > > answering "Y" > > to Allow missmatch now? resulted in an ABI mismatch that caused > > pkg(8) to be > > unusable. > > This is on an older version of 12, so I don't have anything that > > might have > > appeared in UPDATING. I really need this jail to resolve accumulating > > pr(1)'s > > on ports(7) I maintain. > >=20 > > Thank you. >=20 > The difference between 1200062 and 1200054 isn't going to affect > anything except modules which are intimate with kernel internals, such > as video drivers or virtualbox type stuff. >=20 > IMO, this new version checking done by pkg(8) is just bad Bad BAD. The > only control you get is a knob that tells you to ignore any version > mismatch. There appears to be no option to get the historical worked- > really-well behavior of ignoring mismatches of the minor version for > people who track -current. >=20 Except you devs are looking at it with a -CURRENT usage in mind. Most of our users are running releases. And you end up with en issue when let's say FreeBSD 10.0 is EOLed then the packages are now built on 10.1, if people continue running 10.0 because for instance they missed the notice about the 10.0 being EOL, they end up insta= lling packages that may be broken: new libc symbols for example, new syscalls etc. This check was one of the number 1 request over the last 3 years... For all people running -CURRENT they can add IGNORE_OSVERSION=3Dyes. More over, I received so many false bug report because actually developpers= were reporting "pkg is broken!!!" because they run pkg upgrade on a current syst= em that was 6+ month old or running pkg upgrade just after an ABI change that I consider this warning worth it. The only thing I would accept considering here is an advice on how to make = the tests more smooth for -CURRENT users. I consider an IGNORE_OSVERSION to be = good enough. I might change in next versions of pkg the runtime OSVERSION detection read= ing /bin/ls binary to be replaced by uname(1) to make it more friendly with incremental rebuild. Bapt --h5pmvhg5ne5od6pl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEgOTj3suS2urGXVU3Y4mL3PG3PloFAlrwBp0ACgkQY4mL3PG3 Plo1PhAA30fxmOTASuAEfNf7vXBbo/K00eU0hx+573nnXqxtZt72LKDuNyCHDqeb HnF6efab4bbMHXZtkS86a2Z3Q6z7xWFIhS0rctrxbAaRmjpdFcYxTLCUhSBz+p8l BZSK0lHI2oXqYc0PF0sztUzsQKvzoqy+7zzEgDbOa72l4aOGYCEkOunq6oJ2Gs/q MRbzszhSr14XtwetXLdN7Bugnoccxf6QL8RCka1INqzrRmu+hFujF+WKW13jDUQR YOCQllT8b2QK38MNXY7rpc9Jf5gD1ulkc/PW2sf783AsreaQVGE7o6ZeYcRRIXJ7 RF7eab9DJLFj9XUxa94kXf/TFGOf5tvugtgLrHN1vV4g6PpT+zCLfyhFCUpgLkN+ BAHQMkytaXNwj8JuM4HOs9uuhBLZ7sU4rgUm0JJXKRFY1IxQr8v/NTN5UnEt+npS i1wtuYbPxicDDCZxsQF+Tkcjumigzq3xnQT6JAJPLZmBaZ+3rpYIYWXykHDIzOKm TeAhETjl+sP5WXYMoPKQC1JmhUw/RUyAzARLI1jO0fZL8MVv/VFjhWB180cDzhns r7vnpTadwiqvfz5SyFc5dVxylYIugUKFANWMDYiVqgb8q2g7mt9b4IBjQ02tYLGF ssHYcbG5jcEnmogSEACvXwjVc9kWz5knlhGfavOsq+I5PFMOKUA= =3xuA -----END PGP SIGNATURE----- --h5pmvhg5ne5od6pl-- From owner-freebsd-current@freebsd.org Mon May 7 11:05:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5D21BFAE311 for ; Mon, 7 May 2018 11:05:12 +0000 (UTC) (envelope-from loader@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 1559A873D5; Mon, 7 May 2018 11:05:12 +0000 (UTC) (envelope-from loader@freebsd.org) Received: from localhost (unknown [127.0.1.132]) by freefall.freebsd.org (Postfix) with ESMTP id 5D9FB3278; Mon, 7 May 2018 11:05:10 +0000 (UTC) (envelope-from loader@freebsd.org) Date: Mon, 07 May 2018 11:05:07 +0000 From: loader To: Mark Millard Cc: FreeBSD Current Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] In-Reply-To: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> (Mark Millard's message of "Sun, 6 May 2018 19:33:34 -0700") References: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Message-Id: <20180507110510.5D9FB3278@freefall.freebsd.org> 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, 07 May 2018 11:05:12 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable On Sun, 6 May 2018 19:33:34 -0700, Mark Millard = wrote: > Conrad Meyer cem at freebsd.org wrote on > Sun May 6 22:32:13 UTC 2018, as part of a reply: > >> P.S., Mark, your email server is misconfigured and most/all of your >> emails get flagged as spam. I only saw this because I occasionally >> check the spam folder. > > I wrote back directly indicating that I'd need evidence > in order to submit something to yahoo.com. Although, the > original was not sent directly to Conrad, so he likely > got the message directly from a freebsd-current server, > with a yahoo.com's Email server as an intermediate stage. > (I do not run my own servers.) The Email was composed > in macOS's Mail.app [V11.3 (3445.6.18)]. > > Of course, that reply was likely classified as spam. > > If anyone else has such problems with the classification > of my Emails and can send material that would allow > reporting evidence to be submitted someplace, please do > so. It seems the freebsd-current@ list doesn't have=20 from_is_list =3D 1 "Munge From" enabled ... https://wiki.list.org/DEV/DMARC Regards, loader --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQR8BAEBCgBmBQJa8DI6XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0MjBGMjQxRERFRTQ3N0VEMjNFRTA5QzE1 NzBDQTMxRTNGMjc3Q0QyAAoJEFcMox4/J3zS+JggAJiOoK4wao7iXgDuQD1LB/nZ 2xd/Hpy+3PVFOJiE7+oC0UpYL2pXkhJ0pEQiOlc+coc8QxcnvnH7eA8Mz+nMdCio PnyPGTN88ljTfl2kxfvUSRUEfkxw+XK2xCW/UYzxvAqJX6Km55qT33GuK8N7ClXJ H5cqtVoDq1AR8/RlUJ9KLcNRdMCq9HclLr1JXYg86ZsyGO6oaY+myMm6OwRmOybm czg1BM019y8cbnxWaxcVMcqHIATZpPmV7eg+CfFy+jc2ATPlISiv35UyzVNLE12B hUpkLdKA7js+H9kf+0zhzlZpIRb8WjAgKvJfcV0jo+PwOeOCWcp0n/3A4Od40aoG ft5URjP5rIiKMb2ygRfLR77mkeUK+UR06VujhzrVo4jSkrThiyTLsSkUfJokCEvz 2fqco4G77Jphm3KYeJLCyIhylCSPZ1RSmdus7jPv43cIolykxSepo3tQ0dXNXdQf 8i2+haH5FG84/q0fFNsnh3x0du/Y9xkCG7prP1Nz3SXZE0RaKebVApfU9GXPdUTP LFK8ZrzvC5L8vrR7Uc6p67+XZgSAPs8d0nH/tsBoDN2l8hfO4m8Q+qVE8UFm2iZG skPzp4J45fY3xJzH3khbWm5Tqj6XTyFcr4ZAOisrOxxGd1YIEJ9OHSqXbJnpwWYw 8B7M+iFoOtLe40lFVwY8OlU2k+kX2hi1mvJnTirgoqV3rZZw+N9+SwIoJK7bj0n1 xnhsaDNtVG4+hk+GcVwRFZD/QIMUEnWk/8+AVbu381kJceWXjiHOeha+u4onj3YU 1iZNeo/xK95hwbcLdJFOvJHhfuVA+JPxaNT2BdSlawrYg9V1N8T4rh1maIC5s6+z g22izaUKw541EYtKslHTHcPzG1tg3NjvmJ3GtwYKAEXLndjUF62IUwKwFA/xKL6T OME6POaLP8v2Lfne3BeTXnPJAtB++kgRksnneiXbxBRfNoMQwaehHx+LKsO+Kedp MQB6XZSH+RcBOU6MaLB5kMy6F4dm6oSvJrsbjcTEw8ecLuJtaet8tSwOanH+VMcN G4HTo6P+sY6IDor881rqNzjwHN9jsiW9a77Q07vaIfvrGeGwo7pwEP/HXyDFTd9K kQzKxzive8XKigQPoN9P42cQwWrhRMpGNaNFwCzav0HlN9x1IEOCBWu/FC4dyN9O cEd1849ksIGGbzYYqHHsUrIrg2vkFG1Br/5TEH6xmvUX29178ZyYLcadyAOdM2JN H5fOzFGLNcSlcck14SmATqTrqJvDZSDLtb6fGTyr05iDn0t5E4THheT8/EJYONVR ai60HWiKVQSBvhQTI1hEayrGJ7N01a5cRSwu3qslDxQNfx/AeE9hF4Wkch0aJFo= =u1Z7 -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-current@freebsd.org Mon May 7 11:24:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 61B81FAEBF8 for ; Mon, 7 May 2018 11:24:12 +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 0294C6B8BB; Mon, 7 May 2018 11:24:11 +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 7AD5421C6; Mon, 7 May 2018 13:24:04 +0200 (CEST) From: Dimitry Andric Message-Id: <0412E3E1-680E-4A0B-AFB5-C3FEC7BE94CA@FreeBSD.org> Content-Type: multipart/signed; boundary="Apple-Mail=_18FD1F26-43C5-42CE-8D17-148EDED04731"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] Date: Mon, 7 May 2018 13:23:54 +0200 In-Reply-To: <20180507110510.5D9FB3278@freefall.freebsd.org> Cc: Mark Millard , FreeBSD Current To: loader References: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> <20180507110510.5D9FB3278@freefall.freebsd.org> X-Mailer: Apple Mail (2.3445.6.18) 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, 07 May 2018 11:24:12 -0000 --Apple-Mail=_18FD1F26-43C5-42CE-8D17-148EDED04731 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 7 May 2018, at 13:05, loader wrote: >=20 > On Sun, 6 May 2018 19:33:34 -0700, Mark Millard = wrote: >=20 >> Conrad Meyer cem at freebsd.org wrote on >> Sun May 6 22:32:13 UTC 2018, as part of a reply: >>=20 >>> P.S., Mark, your email server is misconfigured and most/all of your >>> emails get flagged as spam. I only saw this because I occasionally >>> check the spam folder. >>=20 >> I wrote back directly indicating that I'd need evidence >> in order to submit something to yahoo.com. Although, the >> original was not sent directly to Conrad, so he likely >> got the message directly from a freebsd-current server, >> with a yahoo.com's Email server as an intermediate stage. >> (I do not run my own servers.) The Email was composed >> in macOS's Mail.app [V11.3 (3445.6.18)]. >>=20 >> Of course, that reply was likely classified as spam. >>=20 >> If anyone else has such problems with the classification >> of my Emails and can send material that would allow >> reporting evidence to be submitted someplace, please do >> so. >=20 > It seems the freebsd-current@ list doesn't have > from_is_list =3D 1 "Munge From" enabled ... > https://wiki.list.org/DEV/DMARC Aha, so that is what the LLVM lists apparently do, and it is somtimes *very* confusing, as all mails seem to come from the same "via" user. Maybe it's easier to just strip off all the kludgy DMARC headers, as it certainly hasn't stopped much spam. ;-) -Dimitry --Apple-Mail=_18FD1F26-43C5-42CE-8D17-148EDED04731 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 iF0EARECAB0WIQR6tGLSzjX8bUI5T82wXqMKLiCWowUCWvA3SgAKCRCwXqMKLiCW o8I+AKDl6CPLnWzR0KHXC3GpqTOKMVARXACdGJFwyoUhFNA3npVxRdDbb/2yRMc= =eiZm -----END PGP SIGNATURE----- --Apple-Mail=_18FD1F26-43C5-42CE-8D17-148EDED04731-- From owner-freebsd-current@freebsd.org Mon May 7 13:18: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 BFAF0FB1D69 for ; Mon, 7 May 2018 13:18:58 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3CFD785F4C for ; Mon, 7 May 2018 13:18:58 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id E8333FB1D67; Mon, 7 May 2018 13:18:57 +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 A5360FB1D66 for ; Mon, 7 May 2018 13:18:57 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0122785F4A; Mon, 7 May 2018 13:18:56 +0000 (UTC) (envelope-from imb@protected-networks.net) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d= protected-networks.net; h=content-transfer-encoding :content-language:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from; s= 201508; t=1525699135; bh=7eDKQ/JWk1KxtoVoPRvKX3N77rydlnA8Z4fWApA B1z4=; b=HKCYoU7CHpz2zhj6ibb57MvufN8yUgawVTFizJubvSfLRp7LSIK1zsI Xlb8fFAXRzmIkEPnvW5yAiflk/7RWlmAZurBsW3G1G796qcOlkLzLyFQIrZtMSG8 LAY47nEoxaeOvsPxRsEvD6AeWRigrl6/lGya5o6xiyMRIkNOFRKI= Received: from Michaels-MBP.fios-router.home (gw.auburn.protected-networks.net [192.168.1.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 104DC2F585; Mon, 7 May 2018 09:18:55 -0400 (EDT) To: FreeBSD Current , markj@freebsd.org From: Michael Butler Subject: conflicting definitions: SVN r333283 et al Openpgp: preference=signencrypt Autocrypt: addr=imb@protected-networks.net; prefer-encrypt=mutual; keydata= xsFNBFlwzP4BEAD8qaxGJ/DxOY8G0DOkWuRLTJyyfxDkkrJfjtphvOaS20CPdRfFMUWVJByc MPvDEeBPIGgKIokG4g0F2V+4u6B/+L0FBkk0fO3HMpZ8bPGhjBTfWBKgen+uTzxrUJRDujRN 2W8osUufJQKJghiFbmlhwfTvb4BD9ZqvWFS8h1m1A45+lft1waIBEYDzzHoD4K9T8DjCKKYy r4UsMvPs5fZ/2MdIDcsjlG8fp8CVeIfz3yghMDvadBtr00hOFKvO9H5wpTxB3uHKmnG8IQJ/ TZ5/drCP92WZi9eaPdSLEHfcRldmCooHIA6p2GZEU6AOR9ySIrn+oD7k/ZuWEqTNkDeKDr1v EA2PYy63mT3ockwPizXC+Rb2+CvWKsmIvr46GH6lw7jE9Ng3eGXAmBc6TAUPLBJD23vAPL57 /qnh0uesQiaWH2kmFyMP4MTpqHKixKWhyREcR5efTubDuR0qq6wqOCXEIWFzWDtEuueN/Ba0 ZaJ/UebxUDwPftulJpYspCKN5OarGrCdy6r0hIdDLEsj2I84eEYkqVR7wopg22NxnuMKpuYR 2yS1LckxWuULjgy7heMO8Z/nQ6f6QbLFO/aoHlXaijSCUqdXHao0Q6TwS9ZRGiUOJ1vugp19 mpt5t7oSQKuber7nDwpN/RZ5CzAJyDFPzx23R/8ZrVnK2Hmw7wARAQABzStNaWNoYWVsIEJ1 dGxlciA8aW1iQHByb3RlY3RlZC1uZXR3b3Jrcy5uZXQ+wsGUBBMBCAA+FiEEwudrhWUnkG1N aZxManivVE3Y6IMFAllwzP4CGyMFCQlmAYAFCwkIBwIGFQgJCgsCBBYCAwECHgECF4AACgkQ anivVE3Y6IMl/BAA+cD7iAxOhD7/9AYCXCZeSYVzv5SESVF668BiaoYxsg3EcgNDXS6NFDqk 2Zi/Bp1k0/WaBYpNqhL5EkpEwkeUAZX0ogRZ4IcYzOp4OhdySbO0HBl+hNMGlgH7YrzMjbTX MlwH77fTq75ggvXWIaQRZr3lgzLt5waEVCt/yF7g0wejKjCkcaimxHajR9UXwpCV5DnYp0TD mfIQTY6nwTvkoMkmpRk+TwvmOXjLAwdDotiZ03KbJ1p2x1akAPSyN/LpRon18dQxdZgiePIS V0IGYrxjsEGnNQUcwgtHXiqjZ5h4KgvBjTICIsfFXnEb23aENK4spicjRUe3FiNMRpGhp8lw q7cBwvTUnFLzhwXp0393u6JVbPPCzBRB+sqZJAHqP2cF2cB1ow1P8qXte+NXBsdP0K8ofTrC m+fNmnp5a8Ac8PmRZxom9HS6pIwrrMEXj9HSvaTe+AEERzschMrJW0vgPnXY1KBtcqZwoEGT jCHUjeilmePNztS0RLmiO0OzQNPjpilmczfudwMMBmSeLU5K73uokodddh2uEEKN6GFe+Mn1 TTYeCnL5/rRmLibGacNWlPIBkCHdNyInlHmhAyx9IHmXv68K/1anVTS7eILvQBhV29mer4UA QhExT/Jb/ycqx4ec1f33yga+9mfC6M3/Exat3PYFTrNTX/wupXTOwU0EWXDM/gEQANE5DmEK Kjh6aaKKAWr1ALTkshYycM5SUTe30H3EwsRaK0ELMlr3cs1A72pMzAWn27C7oX79+NgDTaxl zb3XasLyhGbytnzHvZyTkXz+HDuWaXRTWplMHzRaDam+2YhFOaHBP3oSs8MiN9RqS1AVK39I wp7XUiCCiUSYIe52XEKvZ7dJ5OPPWKPIqfqbx+N3RTJoUb9wp6L65uW4KEq/X2GOdsNQy4ij QOibehKsiNE6t/WZJVc1Lt3bsAp4ySP/QptXh50eXuLRBUKCgVrFkracL8zd1Tb6sKdYNvxy SbVJFhPO2rxSr4fLP3V/Cs7ZdofDzj67AgFdkiSCWIkNgesfXdROU5QXyeB/xMLggPBLuMGm 5DlD+446+zz5omWqykcnTfk3Zz16FefSUMu0LclPK0bc1rX9WHv17a4quGcxHdTlWUgM0pHN K5SozuHI6IeyYB0pJ36k8ALTfvO20zs+RZyuYVeRgaBWql7PmUEpHv7c5mzeZ3mZ5cuBpUE6 cZ5E2MWEbv1frCVXzBE9rdIDIlJRzClhEnvk3AyEXg/mNTE5SQYJpjgjbSqr/RpvQ+Ba0aqM MfSHv2TV7iHzD6fog8Dztgb3nLNBmasC0bMxrfy9r24LJFR57mN9U51HHk2gmiD1mFPit4lM 5x4rhT0u3hoJd0OCXp21eSBAhHB/ABEBAAHCwXwEGAEIACYWIQTC52uFZSeQbU1pnExqeK9U TdjogwUCWXDM/gIbDAUJCWYBgAAKCRBqeK9UTdjogycmD/wN2cK2ksic5zUtL6bQp/tRpkJT TbAXilMRy20wFhl+CeKf8vvhDGTjeAiiYkjSTbbOz7VaRZ6QY+OsEZ4ZcJGmINHJiRIbNSGX OhdIMQhffH5ytVVnrBQq9cnwfF6kDv44FAg2F2TnxuPbTnohskVGQ3PjfwGrwWTEisSBUy64 OsW4p4d8wtT6n+cTxMX90HrEHZNh10RjkPGWxR2ZSQrjgN4kPCV7J8xv1oqsc6C43ovwupCX u4+A3LyPoPVkV4lm7nWiHx/aAuAK04moM+oggIJ+NMChwtBY1HBUj2F5NjXCO+INpXMDz6Ms dtjPSt1ynLH+smDkooIUAzeTGWmmoaoqkiAN28e0rTm4Lkl0Mc+DlCgN6FvdMdloFP2/dKAh griiEDhiBEmOm3o7q3cLO3rzKh2seFprQ1buJijUPiB+RQ+3Y3EdHxPXHR08td1LyjG2Ig3U 324/iJaVDHRU/p4ndv+WKdSJCRvrFdIskG8qpB1XppPqm1UKa0LAMGcRfZ8nmDYMGoEDo/9w AYXSF11vrmIXUpk8eswSGI7Ia4e0j1z6hd1x2UftyphPY5JcUf//HZn1UKfUZuKVxm+s5cWC poXs88dzpjou54RCcIBqnVvjxC4JNA20D/6hWnDifvBo+MtvqeCRwhYNC44SJb8V4/R2THyU twYCBN2sKQ== Message-ID: <37efc4e0-6f47-8cf5-8287-d6cb38b00e77@protected-networks.net> Date: Mon, 7 May 2018 09:18:54 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 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, 07 May 2018 13:18:59 -0000 Recent netdump changes appear to introduced/highlighted conflicting definitions .. Building /usr/obj/usr/src/i386.i386/lib/libsysdecode/ioctl.c In file included from :70: In file included from /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: In file included from /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:48: /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/socket.h:251:9: warning: 'AF_INET6' macro redefined [-Wmacro-redefined] #define AF_INET6 28 /* IPv6 */ ^ /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1467:10: note: previous definition is here # define AF_INET6 26 ^ In file included from :70: In file included from /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:58:10: warning: 'IFNAMSIZ' macro redefined [-Wmacro-redefined] #define IFNAMSIZ IF_NAMESIZE ^ /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1415:9: note: previous definition is here #define IFNAMSIZ 16 ^ 2 warnings generated. imb From owner-freebsd-current@freebsd.org Mon May 7 14:16: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 239FBFB3141 for ; Mon, 7 May 2018 14:16:41 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 93EE371DD4 for ; Mon, 7 May 2018 14:16:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 4E792FB3140; Mon, 7 May 2018 14:16:40 +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 27843FB313F for ; Mon, 7 May 2018 14:16:40 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-io0-x22a.google.com (mail-io0-x22a.google.com [IPv6:2607:f8b0:4001:c06::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 A9D4071DB4 for ; Mon, 7 May 2018 14:16:39 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-io0-x22a.google.com with SMTP id z4-v6so33918258iof.5 for ; Mon, 07 May 2018 07:16:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=9Lm7g7VkbWjPyDmDgUgOiUHVlbAKvUUJefWasIxXfss=; b=GGAYKxOGnaqBP1ekIcOYhJ1PcMSgQp0EVENTPaqvllqw9x0z76BpHlcz/Ywmy0TGuI 5sleGJXHHc/+/2mimw+C7BxPV2gk74Ho6ArKwViBO4tyNUraBmwnOzXm5+UVnX/25oj7 +lCsAKGpwfj2/KmOIiJ7yePl35/4wu1alOqvChmYk+ZEvhY4peUHUvBrBsfu0j9iv99p iNlAZM/zCAW5g8lOUnV5mKVrW10e0d/KPSJKl1kPWoHzr1tVP1CeGRXrfzb2IzPKCudN ZB3qqg/Bc5nPkWajAmwdVU5FrN/n1TyCGF9xDoiQVInYjlQQLSLaeBoTj741T0tVteOU IbCA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=9Lm7g7VkbWjPyDmDgUgOiUHVlbAKvUUJefWasIxXfss=; b=Mcxr9lwNSTRTth1Fs2BvcpKwnLi1wlfAafFLCR9Hot5O5kr5vjjXycs1xXm+WFp5rB 5T0v50raqIwYp6OOx0tzDB5YaQdRZrcNbPWy6SQntJP5hqs5K6DDI1lTmskSS8wdqWdA 8vVpEm6KFTfGYOh9LUpII7wn2MlGmg7BooAWmsjIB2FQvKCybIrEQfiXrv06Ef8QlRIp c/iZG9YAaIKBAWaVDC4hZ/kSXqQEoniH+/acd8r+a3vLhw/sUCMESmpcgZY9GVdofWVk 1x0JexGRpUx0N/ERakR+c9TR7oC9eqr4t+WprgBxLHMEAQ+Oi0XjRxsCCw69chGgXbu3 dgCw== X-Gm-Message-State: ALQs6tDKyTd8XvDvOqRVoUKQ4Yv+YYa5s2VQNnIWC9oAD04RiSYnqldg b+qDNZ69uLIKIPuOcbnoetmHig== X-Google-Smtp-Source: AB8JxZoWTvK6i8jreIcUBJvZt0b1Nlq+1AA5VSkcTGCPz7EI4cRYAa2kzmutF6LuCsIR6NBB9cKXYQ== X-Received: by 2002:a6b:1e4d:: with SMTP id e74-v6mr41523443ioe.36.1525702598706; Mon, 07 May 2018 07:16:38 -0700 (PDT) Received: from raichu (toroon0560w-lp130-04-184-145-252-74.dsl.bell.ca. [184.145.252.74]) by smtp.gmail.com with ESMTPSA id p16-v6sm4324751itp.3.2018.05.07.07.16.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 May 2018 07:16:37 -0700 (PDT) Sender: Mark Johnston Date: Mon, 7 May 2018 10:16:36 -0400 From: Mark Johnston To: Michael Butler Cc: FreeBSD Current Subject: Re: conflicting definitions: SVN r333283 et al Message-ID: <20180507141635.GC57279@raichu> References: <37efc4e0-6f47-8cf5-8287-d6cb38b00e77@protected-networks.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <37efc4e0-6f47-8cf5-8287-d6cb38b00e77@protected-networks.net> User-Agent: Mutt/1.9.5 (2018-04-13) 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, 07 May 2018 14:16:41 -0000 On Mon, May 07, 2018 at 09:18:54AM -0400, Michael Butler wrote: > Recent netdump changes appear to introduced/highlighted conflicting > definitions .. The conflicting definitions in ip_compat.h already existed, and I'm not sure why the netdump import brought them to light. I didn't see this failure when doing build testing, and the CI jobs aren't reporting anything. Is this happening during a buildworld? > Building /usr/obj/usr/src/i386.i386/lib/libsysdecode/ioctl.c > In file included from :70: > In file included from > /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: > In file included from > /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:48: > /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/socket.h:251:9: warning: > 'AF_INET6' macro redefined [-Wmacro-redefined] > #define AF_INET6 28 /* IPv6 */ > ^ > /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1467:10: > note: previous definition is here > # define AF_INET6 26 > ^ > In file included from :70: > In file included from > /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: > /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:58:10: warning: > 'IFNAMSIZ' macro redefined [-Wmacro-redefined] > #define IFNAMSIZ IF_NAMESIZE > ^ > /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1415:9: > note: previous definition is here > #define IFNAMSIZ 16 > ^ > 2 warnings generated. > > imb > From owner-freebsd-current@freebsd.org Mon May 7 16:53:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D9A49FB6909 for ; Mon, 7 May 2018 16:53:40 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 714A871B44 for ; Mon, 7 May 2018 16:53:40 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: by mailman.ysv.freebsd.org (Postfix) id 28EF2FB6907; Mon, 7 May 2018 16:53:40 +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 15275FB6906 for ; Mon, 7 May 2018 16:53:40 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from mail.protected-networks.net (mail.protected-networks.net [IPv6:2001:470:8d59:1::8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protected-networks.net", Issuer "Protected Networks CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A93F171B26; Mon, 7 May 2018 16:53:39 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from [IPv6:2607:fb90:6882:41fe:212a:5e35:29e1:504f] (unknown [IPv6:2607:fb90:6882:41fe:212a:5e35:29e1:504f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: imb@mail.protected-networks.net) by mail.protected-networks.net (Postfix) with ESMTPSA id 7625239511; Mon, 7 May 2018 12:53:31 -0400 (EDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: conflicting definitions: SVN r333283 et al From: Michael Butler X-Mailer: iPhone Mail (15E302) In-Reply-To: <20180507141635.GC57279@raichu> Date: Mon, 7 May 2018 12:53:28 -0400 Cc: FreeBSD Current Content-Transfer-Encoding: quoted-printable Message-Id: References: <37efc4e0-6f47-8cf5-8287-d6cb38b00e77@protected-networks.net> <20180507141635.GC57279@raichu> To: Mark Johnston 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, 07 May 2018 16:53:41 -0000 Entirely possible - I haven=E2=80=99t focused on =E2=80=98make buildworld=E2= =80=99 logs for a while - just concerned how many applications rely on the a= fnet6 definition .. Sent from my iPhone > On May 7, 2018, at 10:16, Mark Johnston wrote: >=20 >> On Mon, May 07, 2018 at 09:18:54AM -0400, Michael Butler wrote: >> Recent netdump changes appear to introduced/highlighted conflicting >> definitions .. >=20 > The conflicting definitions in ip_compat.h already existed, and I'm not > sure why the netdump import brought them to light. I didn't see this > failure when doing build testing, and the CI jobs aren't reporting > anything. Is this happening during a buildworld? >=20 >> Building /usr/obj/usr/src/i386.i386/lib/libsysdecode/ioctl.c >> In file included from :70: >> In file included from >> /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: >> In file included from >> /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:48: >> /usr/obj/usr/src/i386.i386/tmp/usr/include/sys/socket.h:251:9: warning: >> 'AF_INET6' macro redefined [-Wmacro-redefined] >> #define AF_INET6 28 /* IPv6 */ >> ^ >> /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1467:10: >> note: previous definition is here >> # define AF_INET6 26 >> ^ >> In file included from :70: >> In file included from >> /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/netdump/netdump.h:37: >> /usr/obj/usr/src/i386.i386/tmp/usr/include/net/if.h:58:10: warning: >> 'IFNAMSIZ' macro redefined [-Wmacro-redefined] >> #define IFNAMSIZ IF_NAMESIZE >> ^ >> /usr/obj/usr/src/i386.i386/tmp/usr/include/netinet/ip_compat.h:1415:9: >> note: previous definition is here >> #define IFNAMSIZ 16 >> ^ >> 2 warnings generated. >>=20 >> imb >>=20 From owner-freebsd-current@freebsd.org Mon May 7 23:11:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 69AB1FC0DC7 for ; Mon, 7 May 2018 23:11:22 +0000 (UTC) (envelope-from lebarondemerde@privacychain.ch) Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::608]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EDBA66DF15 for ; Mon, 7 May 2018 23:11:21 +0000 (UTC) (envelope-from lebarondemerde@privacychain.ch) Received: from mxback6j.mail.yandex.net (mxback6j.mail.yandex.net [IPv6:2a02:6b8:0:1619::10f]) by forward105o.mail.yandex.net (Yandex) with ESMTP id 6D31E44441B2 for ; Tue, 8 May 2018 02:11:18 +0300 (MSK) Received: from smtp2j.mail.yandex.net (smtp2j.mail.yandex.net [2a02:6b8:0:801::ac]) by mxback6j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id ywApm9UlKS-BIwq1gCR; Tue, 08 May 2018 02:11:18 +0300 Received: by smtp2j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id 91mDydMz2X-BFu0W6MK; Tue, 08 May 2018 02:11:16 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Date: Mon, 7 May 2018 20:11:10 -0300 From: Le Baron =?utf-8?B?ZOKAmU1lcmRl?= To: freebsd-current@freebsd.org Subject: AES67 Message-ID: <20180507231110.h3iomipyad6hqa7c@privacychain.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: NeoMutt/20180323 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, 07 May 2018 23:11:22 -0000 Hello! Is there any known attempt to implement AES67 (is an open standard for audio over IP and audio over ethernet interoperability) on FreeBSD? http://medianetworkingalliance.com/faq-aes67/ Thanks! -- Best Regards. LBdM. From owner-freebsd-current@freebsd.org Tue May 8 03:02: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 37B58FC9FAA for ; Tue, 8 May 2018 03:02:45 +0000 (UTC) (envelope-from peter@wemm.org) Received: from smtp2.wemm.org (smtp2.wemm.org [192.203.228.78]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp2.wemm.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CA709841AE; Tue, 8 May 2018 03:02:44 +0000 (UTC) (envelope-from peter@wemm.org) Received: from overcee.wemm.org (canning.wemm.org [192.203.228.65]) by smtp2.wemm.org (Postfix) with ESMTP id DC83563D; Mon, 7 May 2018 20:02:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=m20140428; t=1525748562; bh=6QK1MClL7orbQvLk5J1rJ7Y6gyQTYVqTwUbyBMCqCLI=; h=From:To:Cc:Subject:Date:In-Reply-To:References; b=Tl7IOBWYpKnqegjsGuhCeFP2SunDUjIEKS027+mB/hnKKQKaHmYpJbKjf5PY+fT6W bKJL5vJIqHdUqL9XdlpgdBWzajePFOtq+LfGlSn0HB6VCA7bz4d4ebRVrw0eysrQzq 4b6NB7V7qZZnlIDfUPyga4w8rVNqgQGh1VPh3Sh8= From: Peter Wemm To: freebsd-current@freebsd.org Cc: Ian Lepore , bsd-lists@bsdforge.com Subject: Re: IGNORE_OSVERSION=yes -- can't install pkg Date: Mon, 07 May 2018 20:02:41 -0700 Message-ID: <3873602.OYXp4yczo3@overcee.wemm.org> In-Reply-To: <1525538856.57768.293.camel@freebsd.org> References: <7c58b8eb1bc3f83819c2aab6bfea322c@udns.ultimatedns.net> <1525538856.57768.293.camel@freebsd.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 08 May 2018 03:02:45 -0000 On Saturday, May 5, 2018 9:47:36 AM PDT Ian Lepore wrote: > On Sat, 2018-05-05 at 08:26 -0700, Chris H wrote: > > On Fri, 04 May 2018 22:57:52 -0700 said > > > > > I just setup a jail from a 12-CURRENT I built awhile ago. It has no > > > ports > > > tree. So I'm attempting > > > to install svnlite. issuing pkg search svnlite returns > > > The package management tool is not yet installed on your system. > > > Do you want to fetch and install it now? [y/N]: y > > > Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/FreeBSD:12:amd64/ > > > latest, > > > please wait... > > > Verifying signature with trusted certificate > > > pkg.freebsd.org.2013102301... > > > done > > > [12current.localhost] Installing pkg-1.10.5... > > > Newer FreeBSD version for package pkg: > > > To ignore this error set IGNORE_OSVERSION=yes > > > - package: 1200062 > > > - running kernel: 1200054 > > > Allow missmatch now?[Y/n]: > > > > > > Umm, what? Should I ignore this error? If so, why is there an error > > > at all? > > > I answered no. Guess I won't be able to use pkg(8) on this jail(8). > > > > > > :-( > > > > > > --Chris > > > > OK the only reference[1] I can find regarding this, indicates that > > answering "Y" > > to Allow missmatch now? resulted in an ABI mismatch that caused > > pkg(8) to be > > unusable. > > This is on an older version of 12, so I don't have anything that > > might have > > appeared in UPDATING. I really need this jail to resolve accumulating > > pr(1)'s > > on ports(7) I maintain. > > > > Thank you. > > The difference between 1200062 and 1200054 isn't going to affect > anything except modules which are intimate with kernel internals, such > as video drivers or virtualbox type stuff. > > IMO, this new version checking done by pkg(8) is just bad Bad BAD. The > only control you get is a knob that tells you to ignore any version > mismatch. There appears to be no option to get the historical worked- > really-well behavior of ignoring mismatches of the minor version for > people who track -current. There was an unfortunate Incident caused OSVERSION handling at a certain Verizon company that happens to run FreeBSD. We hit an OSVERSION implementation bug on the freebsd.org cluster today. We've disabled it across the entire site as it is unusable for us in this form. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com "All of this is for nothing if we don't go to the stars" - JMS/B5 From owner-freebsd-current@freebsd.org Tue May 8 03:52: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 C4FFFFCC35D for ; Tue, 8 May 2018 03:52:45 +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 547526FF08; Tue, 8 May 2018 03:52:44 +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 w483sNue050641; Mon, 7 May 2018 20:54:29 -0700 (PDT) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 Cc: "FreeBSD Current" In-Reply-To: <20180507075616.qtqplco6rasy4zbp@ivaldir.net> From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: "Baptiste Daroussin" , "Ian Lepore" Subject: Re: IGNORE_OSVERSION=yes -- can't install pkg Date: Mon, 07 May 2018 20:54:29 -0700 Message-Id: <07b3d0a366a44301a72b65f6d3ddf947@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: Tue, 08 May 2018 03:52:46 -0000 On Mon, 7 May 2018 09:56:16 +0200 "Baptiste Daroussin" s= aid > On Sat, May 05, 2018 at 10:47:36AM -0600, Ian Lepore wrote: > > On Sat, 2018-05-05 at 08:26 -0700, Chris H wrote: > > > On Fri, 04 May 2018 22:57:52 -0700 said > > >=20 > > > >=20 > > > > I just setup a jail from a 12-CURRENT I built awhile ago=2E It has no > > > > ports > > > > tree=2E So I'm attempting > > > > to install svnlite=2E issuing pkg search svnlite returns > > > > The package management tool is not yet installed on your system=2E > > > > Do you want to fetch and install it now? [y/N]: y > > > > Bootstrapping pkg from pkg+http://pkg=2EFreeBSD=2Eorg/FreeBSD:12:amd64/ > > > > latest, > > > > please wait=2E=2E=2E > > > > Verifying signature with trusted certificate > > > > pkg=2Efreebsd=2Eorg=2E2013102301=2E=2E=2E > > > > done > > > > [12current=2Elocalhost] Installing pkg-1=2E10=2E5=2E=2E=2E > > > > Newer FreeBSD version for package pkg: > > > > To ignore this error set IGNORE_OSVERSION=3Dyes > > > > - package: 1200062 > > > > - running kernel: 1200054 > > > > Allow missmatch now?[Y/n]: > > > >=20 > > > > Umm, what? Should I ignore this error? If so, why is there an error > > > > at all? > > > > I answered no=2E Guess I won't be able to use pkg(8) on this jail(8)=2E > > > > :-( > > > >=20 > > > > --Chris > > > OK the only reference[1] I can find regarding this, indicates that > > > answering "Y" > > > to Allow missmatch now? resulted in an ABI mismatch that caused > > > pkg(8) to be > > > unusable=2E > > > This is on an older version of 12, so I don't have anything that > > > might have > > > appeared in UPDATING=2E I really need this jail to resolve accumulating > > > pr(1)'s > > > on ports(7) I maintain=2E > > >=20 > > > Thank you=2E > >=20 > > The difference between 1200062 and 1200054 isn't going to affect > > anything except modules which are intimate with kernel internals, such > > as video drivers or virtualbox type stuff=2E Thanks, Ian=2E Glad to hear it=2E > >=20 > > IMO, this new version checking done by pkg(8) is just bad Bad BAD=2E The > > only control you get is a knob that tells you to ignore any version > > mismatch=2E There appears to be no option to get the historical worked- > > really-well behavior of ignoring mismatches of the minor version for > > people who track -current=2E > >=20 >=20 > Except you devs are looking at it with a -CURRENT usage in mind=2E >=20 > Most of our users are running releases=2E >=20 > And you end up with en issue when let's say FreeBSD 10=2E0 is EOLed then th= e > packages are now built on 10=2E1, if people continue running 10=2E0 because f= or > instance they missed the notice about the 10=2E0 being EOL, they end up > installing > packages that may be broken: new libc symbols for example, new syscalls e= tc=2E >=20 > This check was one of the number 1 request over the last 3 years=2E=2E=2E > For all people running -CURRENT they can add IGNORE_OSVERSION=3Dyes=2E >=20 > More over, I received so many false bug report because actually developpe= rs > were > reporting "pkg is broken!!!" because they run pkg upgrade on a current > system > that was 6+ month old or running pkg upgrade just after an ABI change tha= t I > consider this warning worth it=2E >=20 > The only thing I would accept considering here is an advice on how to mak= e > the > tests more smooth for -CURRENT users=2E I consider an IGNORE_OSVERSION to b= e > good > enough=2E >=20 > I might change in next versions of pkg the runtime OSVERSION detection > reading > /bin/ls binary to be replaced by uname(1) to make it more friendly with > incremental rebuild=2E Thanks for the reply, Bapt! I hear your point, and it seems reasonable=2E But I have a couple nits; 1) Adding IGNORE_OSVERSION=3Dyes to make=2Econf(5) had no affect=2E 2) Would it be remotely possible for the error to be slightly more informative? As it stands, it appears that in order to use pkg(8) in this situation=2E Ones *only* option is to answer Y=2E IMHO this seems wrong=2E Thanks again! --Chris >=20 > Bapt From owner-freebsd-current@freebsd.org Tue May 8 04:20:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6ED62FCD02C for ; Tue, 8 May 2018 04:20:40 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: from mail-pl0-x232.google.com (mail-pl0-x232.google.com [IPv6:2607:f8b0:400e:c01::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 E14497808A; Tue, 8 May 2018 04:20:39 +0000 (UTC) (envelope-from koobs.freebsd@gmail.com) Received: by mail-pl0-x232.google.com with SMTP id q18-v6so1430760plr.6; Mon, 07 May 2018 21:20:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:reply-to:subject:to:cc:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Hc4/LBAwCe6hJ8qEZusyNb+MXL4zh2u1HhQdTpXjxZ4=; b=b6Eto7lnxSqxwfFNcFB9m6wNLBiawb9jph1R/7sdgy7jqDHmR7xTr7Ag+dF3RWh7Rk FCWBCu9BkB9OAqS6tVvfRz+u2lu3YmNFmHpHJFKidIyaCLwkxH1PsshLbSQnV3UI90HG i221sBIwKaQqXVrXjcMqjjQDjq/0EdzNDF6gL255hJwong1uF2O4NxJGVarJJBBf7+oB uB7Uo6ABAkDObl43hbc9ohiNAdPv+uxKMMmX/EAzO3mY67qOuMWREYS6kUcs8njFfraT uB4WxTcqkqFkmbj9qoD8DAOYe8lhMnOto6LeyBnwFU5wCiM0/jRlbe986XMI4O3Ergaj F0mA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:subject:to:cc:references:from :openpgp:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=Hc4/LBAwCe6hJ8qEZusyNb+MXL4zh2u1HhQdTpXjxZ4=; b=e3rPB7Uv9wiGuztk0/Fl3fZkgR/7igizPeVqG8uG5I7PDWwhF4JPxEGa7qojvFfHd3 W5oCyvYv4SRXpXzrNngdFzKYnW5zQ+2XiU5pzHsXYRRSowEsPYxpVeiY2N7qihHYql78 1MQRo1sDf+lV/MFNk/SWE9kjy/e5nNCzBrHTHKFvJQGcmeThRlzTMk2galy0bmeVUN3o uTUUkXGFDOM1UN2NWQSwvSPnv/MsH/gn6WWq0Ve98fIAJvRMxDd3122kk/58CSvTnRvW zCHkVMesudRvWiDb+EMWNejvQaNZ+yKuFVKY1jlt304mJ20D7AVUolJTxXNIBtDHNCe/ p0iA== X-Gm-Message-State: ALQs6tCdS6q5U5VPsnPHCmIHR9HzD837YPGhDHH4ywuQMN1qvmeSUTnU HXt6ehDB+UDoaZwM0zmZ9No8ZZlS X-Google-Smtp-Source: AB8JxZpCVB2Q/ijo1HxW5Iu56Dm/7ZBbBJnsdYSaOsOru5nNMsK+S3wx6pwVOORtKrk7jluf2Dx+sA== X-Received: by 2002:a17:902:3f83:: with SMTP id a3-v6mr40046628pld.279.1525753238618; Mon, 07 May 2018 21:20:38 -0700 (PDT) Received: from [192.168.1.106] (116.133.220.111.sta.wbroadband.net.au. [111.220.133.116]) by smtp.gmail.com with ESMTPSA id b29sm47822799pfh.155.2018.05.07.21.20.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 07 May 2018 21:20:38 -0700 (PDT) Sender: Kubilay Kocak Reply-To: koobs@FreeBSD.org Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] To: loader , Mark Millard Cc: FreeBSD Current References: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> <20180507110510.5D9FB3278@freefall.freebsd.org> From: Kubilay Kocak Openpgp: preference=signencrypt Message-ID: <64bf296a-d21f-8b36-b3aa-fde65397c79d@FreeBSD.org> Date: Tue, 8 May 2018 14:20:34 +1000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <20180507110510.5D9FB3278@freefall.freebsd.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 08 May 2018 04:20:40 -0000 On 7/05/2018 9:05 pm, loader wrote: > On Sun, 6 May 2018 19:33:34 -0700, Mark Millard wrote: > >> Conrad Meyer cem at freebsd.org wrote on >> Sun May 6 22:32:13 UTC 2018, as part of a reply: >> >>> P.S., Mark, your email server is misconfigured and most/all of your >>> emails get flagged as spam. I only saw this because I occasionally >>> check the spam folder. >> >> I wrote back directly indicating that I'd need evidence >> in order to submit something to yahoo.com. Although, the >> original was not sent directly to Conrad, so he likely >> got the message directly from a freebsd-current server, >> with a yahoo.com's Email server as an intermediate stage. >> (I do not run my own servers.) The Email was composed >> in macOS's Mail.app [V11.3 (3445.6.18)]. >> >> Of course, that reply was likely classified as spam. >> >> If anyone else has such problems with the classification >> of my Emails and can send material that would allow >> reporting evidence to be submitted someplace, please do >> so. > > It seems the freebsd-current@ list doesn't have > from_is_list = 1 "Munge From" enabled ... > https://wiki.list.org/DEV/DMARC > > Regards, > loader > See Also: Mail forwarded from list to members fails DKIM/SPF/DMARC authentication https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210457 From owner-freebsd-current@freebsd.org Tue May 8 05:25:46 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7FA55FCF0F0 for ; Tue, 8 May 2018 05:25:46 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (unknown [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 193FB870A1 for ; Tue, 8 May 2018 05:25:45 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fFv8C-000P7J-Bm; Tue, 08 May 2018 07:25:44 +0200 Date: Tue, 8 May 2018 07:25:44 +0200 From: Kurt Jaeger To: Le Baron d???Merde Cc: freebsd-current@freebsd.org Subject: Re: AES67 Message-ID: <20180508052544.GW37752@home.opsec.eu> References: <20180507231110.h3iomipyad6hqa7c@privacychain.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180507231110.h3iomipyad6hqa7c@privacychain.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, 08 May 2018 05:25:46 -0000 Hi! > Is there any known attempt to implement AES67 (is an open standard > for audio over IP and audio over ethernet interoperability) on FreeBSD? > http://medianetworkingalliance.com/faq-aes67/ I found https://www.collabora.com/news-and-blog/blog/2017/04/25/receiving-an-aes67-stream-with-gstreamer/ which describes AES67 as RTP with some clock sync. But it looks like there is no open source implementation at all right now. -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Tue May 8 06:02:22 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 26A66FCFEA6 for ; Tue, 8 May 2018 06:02:22 +0000 (UTC) (envelope-from ashmew2@gmail.com) Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A616E6EA44; Tue, 8 May 2018 06:02:21 +0000 (UTC) (envelope-from ashmew2@gmail.com) Received: by mail-it0-x22b.google.com with SMTP id t7-v6so13220101itf.0; Mon, 07 May 2018 23:02:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=phNrC23s8UUGTp6BM3Q+le3xUnpu6VOJcPXuf7UFc88=; b=qjw9B8v3RICHQDY6iF/IRz9kVWw52xDslu8EIVDwCBw8/FuGi5RILw+G1UZCCkTFxF 3MZiJuXw497p1GlG0L3Uomcn2tdEptqT4WS8v/Zs/WhjMoezDTDaBMScDysKA4ih1ijx yORJP5nrEqz0jhS2Ho5c4SqDD1E8/RrNTYJzyZcfbsIEQKzvYnq8GBJzjUDfYkMycyvA NeFx5P6XPhfmWEYm9/tuCnZTT8QazVN/Q6NHLcF1XpxTRhRMwE30cZJKe13jJuAMziHS lHrSfBnCZyxq9vrEkkKNNFVXoS5CyJPGqJC/AcdMR6VezHYdruFpe57b10tddHy8PF6P WnVA== 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=phNrC23s8UUGTp6BM3Q+le3xUnpu6VOJcPXuf7UFc88=; b=fqHKZGOQWXI5WUXNNZQa+BVp/ahZGY0WDNzic6WzYOxdtMLUTXOwqEJZBQeRa0R9HU pauMF1oYCwBZTpm2dVn49OqbHrC/juJJqI0NNciYiKEuRcfX0yJCl14i6gMUfxMYSZXF t/A9Qe1ozhQQUJRgXVCdOWnKiNlN0YZKSeBUWssiCj/a5YVngFf4nAszkzpoCW/0ETJ1 xz1Z4Aa0JPfPjcpTE2I08zaMLyvBmEnWh3c/KYhBdWGYdl0QPuXndd8b5o2i+wcryJ3C iJAQR1D5yCLipTiQIp2lF0Qupb/6Qngngps2fPym+NLXhADLEEK6ys8P+chvroJ7PEJD xC7A== X-Gm-Message-State: ALQs6tDU+PhR//K4dFjaCW8+iyg9MJiE9R5JCSF8fjeIJuaxQqLX09CA 4tQxDGeA/RXGSqQ1hyyaSKb+aNeRLqNcx1ZNcD8= X-Google-Smtp-Source: AB8JxZrFHps+Hs1OK1xB4UZ7Q3Mdybm2DOTuLcV0V/ttpT1VAE04perW2+C1+v/8IElexyex9ZzHxGSz/w7V2zawSHY= X-Received: by 2002:a24:a0cc:: with SMTP id o195-v6mr4507916ite.115.1525759340887; Mon, 07 May 2018 23:02:20 -0700 (PDT) MIME-Version: 1.0 References: <8E3C5DFF-BC87-4822-9A35-BF206A735EAA@yahoo.com> <20180507110510.5D9FB3278@freefall.freebsd.org> <64bf296a-d21f-8b36-b3aa-fde65397c79d@FreeBSD.org> In-Reply-To: <64bf296a-d21f-8b36-b3aa-fde65397c79d@FreeBSD.org> From: Ashish Gupta Date: Tue, 08 May 2018 06:02:10 +0000 Message-ID: Subject: Re: svn commit: r333240 - in head/sys: powerpc/powerpc sys [appears to have broken the builds of head for riscv64] To: koobs@freebsd.org Cc: loader , FreeBSD Current , marklmi26-fbsd@yahoo.com 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: Tue, 08 May 2018 06:02:22 -0000 Hi, Not sure if this is already known. I have a gmail account, which complains about your mails: Why is this message in Spam? It's from an address in the yahoo.com domain but has failed yahoo.com's required tests for authentication. On Tue, 8 May 2018, 06:22 Kubilay Kocak, wrote: > On 7/05/2018 9:05 pm, loader wrote: > > On Sun, 6 May 2018 19:33:34 -0700, Mark Millard < > marklmi26-fbsd@yahoo.com> wrote: > > > >> Conrad Meyer cem at freebsd.org wrote on > >> Sun May 6 22:32:13 UTC 2018, as part of a reply: > >> > >>> P.S., Mark, your email server is misconfigured and most/all of your > >>> emails get flagged as spam. I only saw this because I occasionally > >>> check the spam folder. > >> > >> I wrote back directly indicating that I'd need evidence > >> in order to submit something to yahoo.com. Although, the > >> original was not sent directly to Conrad, so he likely > >> got the message directly from a freebsd-current server, > >> with a yahoo.com's Email server as an intermediate stage. > >> (I do not run my own servers.) The Email was composed > >> in macOS's Mail.app [V11.3 (3445.6.18)]. > >> > >> Of course, that reply was likely classified as spam. > >> > >> If anyone else has such problems with the classification > >> of my Emails and can send material that would allow > >> reporting evidence to be submitted someplace, please do > >> so. > > > > It seems the freebsd-current@ list doesn't have > > from_is_list = 1 "Munge From" enabled ... > > https://wiki.list.org/DEV/DMARC > > > > Regards, > > loader > > > > See Also: > > Mail forwarded from list to members fails DKIM/SPF/DMARC authentication > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210457 > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Tue May 8 08:16: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 51C6EFACF16 for ; Tue, 8 May 2018 08:16:59 +0000 (UTC) (envelope-from rum1cro@yandex.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BFEFC6B13E for ; Tue, 8 May 2018 08:16:58 +0000 (UTC) (envelope-from rum1cro@yandex.ru) Received: from mxback10o.mail.yandex.net (mxback10o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::24]) by forward101o.mail.yandex.net (Yandex) with ESMTP id 1113D1342A4B; Tue, 8 May 2018 11:16:56 +0300 (MSK) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback10o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 0rAq7HagVT-GtYqxXJC; Tue, 08 May 2018 11:16:56 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1525767416; bh=rbt78/A5IUEagqQHl4O7omU8um0Q0vP77aHpA9X8FJQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=C0Xw1pjGJQCCeZExL8xEr/LD3P1mSJqHp4BavGDlnKabQIh4RvMPHcR5Hm1HLvXUQ QKTo2Vt30VzVUoZeCXbEiDlk3lb98/a/M/DV4GHkW8e9Uw1LJwJdU0o8iluTxam7Nc UJ2WG+L5xc7ORCj5vF5ciuIf0Y+dphFf+bEoolXM= Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id krgfR4hrNa-GsCCTUte; Tue, 08 May 2018 11:16:54 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1525767414; bh=rbt78/A5IUEagqQHl4O7omU8um0Q0vP77aHpA9X8FJQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=SWmE/ioXtmWDQiZeB9DfuTAPjCFevnvFI37r3VUkNhJYwgqnirym5h3XLHe7r7Qe3 Crgn4qH1QlkGGF2/kD+wOsPydE9LuM6dEiJVeTOiu798g7xWK9n3zUwtZ0YOdtd2vH ASIEbk0tNBk2VZgiF934Qy5UMXqL8Q06r8c1OPGU= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: Regression Resume Lenovo T450 To: =?UTF-8?Q?Manuel_St=c3=bchn?= , freebsd-current@freebsd.org References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> From: "Ilya A. Arkhipov" Message-ID: <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> Date: Tue, 8 May 2018 11:16:48 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180506072835.GA87831@freebsd-t450.fritz.box> Content-Type: text/plain; charset=iso-8859-15; 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, 08 May 2018 08:16:59 -0000 On 06.05.2018 10:28, Manuel Stühn wrote: > On Fri, May 04, 2018 at 08:07:17AM +0200, Manuel Stühn wrote: >> >> Since some time now CURRENT runs very smoothly on my Lenovo T450 in >> conjunction with drm-stable-kmod installed. WLAN, Suspense&Resume worked >> out of the box (at least ... until now). Due to pkg(8) complaining about >> wrong ABI of packages, I've made an update from r332385 (1200061) to >> r333091 (1200062), and now the T450 does not resume anymore; i have to >> hold the power button for some time to power it down. The >> ZFS-Boot-Environment I've made beforehand updating is still capable of >> resuming. >> >> I tried to find out which commit broke the resume for me by installing >> older kernels, but even installing r332385 kernel (into the actual >> r333091 userland) does not restore its capability to resume. >> > > Some more testing has happened: > > Since I have a BootEnvironment capable of suspend/resume, I've tried > some combinations of kernels (in fact, whole boot-folders) and > unserlands. I copied the boot-folder from the BE r332385 (which works) > into the current BE and restarted. This combination was NOT able to > resume. But the other way around is (current boot-folder (r333091) in > the r332385 based BootEnvironment) > > It seems to me, that not the kernel but either some change in userland > or package broke the resume somehow. But I do not have a clue, which > of those even can impact the resume procedure at all. Two packages > came to my mind: > > 1. graphics/drm-stable-kmod, but the installed packages are identical > for both, the "old" and the current BE. (both packages are installed > from ports along with the respective buildworld+buildkernel) > > 2. The firmwares used by sysutils/cpupdate, but after replacing the > firmware files with the firmwares from the old BE resume still doesn't > work. > > Any ideas? > > -- > Manuel > > _______________________________________________ > 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" Hi, I have same issue (thinkpad T450s) after resume notebook cant wake up but on:  FreeBSD 12.0-CURRENT #0 r332796: Fri Apr 20 00:42:44 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 with: drm-next-kmod-4.11.g20180224 gpu-firmware-kmod-g20180206_1 # sysctl debug.bootverbose=1 # sysctl debug.acpi.suspend_bounce=1 In log (I think it related): May  8 01:05:06 m1cro kernel: vgapci0: child drmn0 requested pci_set_powerstate May  8 01:05:06 m1cro kernel: pci0:0:2:0: Transition from D0 to D3 May  8 01:05:06 m1cro kernel: pci0: set ACPI power state D3 on \_SB_.PCI0.VID_ May  8 01:05:06 m1cro kernel: pci0: failed to set ACPI power state D3 on \_SB_.PCI0.VID_: AE_BAD_PARAMETER where pci0:0:2:0: vgapci0@pci0:0:2:0:     class=0x030000 card=0x503617aa chip=0x16168086 rev=0x09 hdr=0x00     vendor     = 'Intel Corporation'     device     = 'HD Graphics 5500'     class      = display     subclass   = VGA From owner-freebsd-current@freebsd.org Tue May 8 15:29: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 87249FB8F34 for ; Tue, 8 May 2018 15:29:51 +0000 (UTC) (envelope-from lebarondemerde@privacychain.ch) Received: from forward104j.mail.yandex.net (forward104j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 164B685FE6 for ; Tue, 8 May 2018 15:29:50 +0000 (UTC) (envelope-from lebarondemerde@privacychain.ch) Received: from mxback1g.mail.yandex.net (mxback1g.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:162]) by forward104j.mail.yandex.net (Yandex) with ESMTP id A4528440AD; Tue, 8 May 2018 18:29:47 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback1g.mail.yandex.net (nwsmtp/Yandex) with ESMTP id sdp55grxvb-Tl7WUg6I; Tue, 08 May 2018 18:29:47 +0300 Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id YbQVkO4HYQ-ThIOoZDq; Tue, 08 May 2018 18:29:44 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) Date: Tue, 8 May 2018 12:29:39 -0300 From: Le Baron d???Merde To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: AES67 Message-ID: <20180508152939.3m2izxsubhn5zwoz@privacychain.ch> References: <20180507231110.h3iomipyad6hqa7c@privacychain.ch> <20180508052544.GW37752@home.opsec.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20180508052544.GW37752@home.opsec.eu> User-Agent: NeoMutt/20180323 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, 08 May 2018 15:29:51 -0000 Hi! > Hi! > > > Is there any known attempt to implement AES67 (is an open standard > > for audio over IP and audio over ethernet interoperability) on FreeBSD? > > > http://medianetworkingalliance.com/faq-aes67/ > > I found > > https://www.collabora.com/news-and-blog/blog/2017/04/25/receiving-an-aes67-stream-with-gstreamer/ > > which describes AES67 as RTP with some clock sync. But it looks I guess the sync part is the most problematic one to implement. :-) > like there is no open source implementation at all right now. I would like to say: FreeBSD will have the first then, but I do not code... :-/ IIRC, I heard the OpenBSD sndio developer do use OpenBSD for professional audio. So, I guess, the implementation is more likely to happen in there first. :-) Apparently there is some proprietary Linux implementations, including a 'professional' embedded solution (what I know nothing about but also support AES70): https://www.youraudiosystems.com/en/aes67-linux/ Interestingly, Merging (also heard something about Dante) apparently can provide a Linux driver, +based on this thread: https://www.gearslutz.com/board/music-computers/1193399-merging-hapi-horus-aes67-linux.html Thank you! > > -- > pi@opsec.eu +49 171 3101372 2 years to go ! -- Best Regards. LBdM. From owner-freebsd-current@freebsd.org Tue May 8 18:33:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 638F0FC5A34 for ; Tue, 8 May 2018 18:33:30 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) by mx1.freebsd.org (Postfix) with ESMTP id 00D7E737B0; Tue, 8 May 2018 18:33:29 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim Subject: Re: New ACPI Errors To: Claude Buisson , Pete Wright Cc: FreeBSD-current References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> Openpgp: preference=signencrypt Autocrypt: addr=jkim@FreeBSD.org; prefer-encrypt=mutual; keydata= xsBNBFJBztUBCAChqNyGqmFuNo0U7MBzsD+q/G6Cv0l7LGVrOAsgh34M8wIWhD+tztDWMVfn AhxNDd0ceCj2bYOe67sTQxAScEcbt2FfvPOLp9MEXb9qohZj172Gwkk7dnhOhZZKhVGVZKM4 NcsuBDUzgf4f3Vdzj4wg6WlqplnTZo8lPE4hZWvZHoFIyunPTJWenybeV1xnxK7JkUdSvQR0 fA59RfTTECMwTrSEfYGUnxIDBraxJ7Ecs/0hGQ7sljIj8WBvlRDU5fU1xfF35aw56T8POQRq F4E6RVJW3YGuTpSwgtGZOTfygcLRhAiq3dFC3JNLaTVTpM8PjOinJyt9AU6RoITGOKwDABEB AAHNHkp1bmctdWsgS2ltIDxqa2ltQEZyZWVCU0Qub3JnPsLAfQQTAQoAJwUCUkHO1QIbAwUJ E0/POwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRB8n5Ym/NvxRqyzB/wL7QtsIpeGfGIA ZPMtgXMucM3NWzomyQMln2j2efUkDKthzh9jBxgF53TjOr7imwIt0PT2k1bqctPrq5IRqnu9 mGroqaCLE3LG2/E3jEaao4k9PO6efwlioyivUo5NrqIQOQ4k3EAXw7d2y0Dk1VpTgdMrnUAB hj7lGlLqS4ydcrf24DdbCRGdEQwqd9DBeBgbWynxAJMgbZBhYVEyIHuQKkJ8qY0ibIPXXuF0 KYDeH0qUHtWV2K3srNyPtymUkBQD84Pl1GWRYx05XdUHDmnX0JV3lg0BfYJZgZv0ehPQrMfY Fd9abTkf9FHQYz1JtsC8wUuRgqElRd6+YAGf8Tt9zsBNBFJBztUBCADLtSrP44El2VoJmH14 OFrlOgxzZnbn+Y/Gf1k12mJBiR+A+pBeRLD50p7AiTrjHRxO3cHcl9Dh0uf1VSbXgp8Or0ye iP/86fZPd4k5HXNmDTLL0HecPE08SCqGZ0W8vllQrokB1QxxRUB+fFMPJyMCjDAZ7P9fFTOS dTw1bJSTtOD8Sx8MpZUa9ti06bXFlVYDlaqSdgk181SSx+ZbSKkQR8CIMARlHwiLsa3Z9q9O EJr20HPyxe0AlTvwvFndH61hg7ds63eRvglwRnNON28VXO/lvKXq7Br/CiiyhFdKfINIx2Z5 htYq22tgGTW7mBURbIKoECFBTX9Lv6BXz6w9ABEBAAHCwGUEGAEKAA8FAlJBztUCGwwFCRNP zzsACgkQfJ+WJvzb8UZcJQf+IsTCxUEqY7W/pT84sMg5/QD3s6ufTRncvq14fEOxCNq1Rf4Q 9P+tOFa8GZfKDGB2BFGIrW7uT5mlmKdK1vO6ZIA930y5kUsnCmBUEBJkE2ciSQk01aB/1o62 Q3Gk/F6BwtNY9OXiqF7AcAo+K/BMIaqb26QKeh+IIgK1NN9dQiq3ByTbl4zpGZa6MmsnnRTu mzGKt2nkz7vBzH6+hZp1OzGZikgjjhYWVFoJo1dvf/rv4obs0ZJEqFPQs/1Qa1dbkKBv6odB XJpPH0ssOluTY24d1XxTiKTwmWvHeQkOKRAIfD7VTtF4TesoZYkf7hsh3e3VwXhptSLFnEOi WwYofg== Message-ID: Date: Tue, 8 May 2018 14:33:20 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="t9kLvMaX18YVGbJScNvWwfM3fmDuExapt" 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, 08 May 2018 18:33:30 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --t9kLvMaX18YVGbJScNvWwfM3fmDuExapt Content-Type: multipart/mixed; boundary="ydfSDwsSStOvRwRS7BH0iEJieVx0JhWRM"; protected-headers="v1" From: Jung-uk Kim To: Claude Buisson , Pete Wright Cc: FreeBSD-current Message-ID: Subject: Re: New ACPI Errors References: <58d889fa-a9c5-5108-c838-01f4904950cd@nomadlogic.org> <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> In-Reply-To: <8fed618b-5402-f396-b51e-48de8ac4f36b@orange.fr> --ydfSDwsSStOvRwRS7BH0iEJieVx0JhWRM Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 02/13/2018 17:34, Claude Buisson wrote: > On 02/13/2018 22:49, Pete Wright wrote: >> Hello, >> I have started seeing a lot of these messages spam my system log: >> >> ACPI Error: No pointer back to namespace node in package >> 0xfffff8000f79a080 (20180209/dsargs-472) >> ACPI Error: Method parse/execution failed \134_SB.AC.ADJP, >> AE_AML_INTERNAL (20180209/psparse-677) >> ACPI Error: Method parse/execution failed \134_SB.AC._PSR, >> AE_AML_INTERNAL (20180209/psparse-677) >> >> I noticed this starting from a CURRENT build i installed two weeks >> ago, and still see it from a world/kernel i built last night.=C2=A0 tw= o >> questions: >> 1) has anyone else noticed this? >> 2) is this something to worry about? >> >> i can help debug the issue but am not sure where to start poking. >> >> thanks! >> -pete >> > Here I have >=20 > ACPI Error: No pointer back to namespace node in package > 0xfffff8000171f700 (20180209/dsargs-472) > ACPI Error: AE_AML_INTERNAL, While resolving operands for [OpcodeName > unavailable] (20180209/dswexec-606) > ACPI Error: Method parse/execution failed > \134_PR.CPU0._CST,AE_AML_INTERNAL (20180209/psparse-677) >=20 > with svn 329142 on a Lenovo ThinkCentre M83 > ACPI APIC Table: >=20 > Claude Buisson This problem should be fixed now (r333380). Sorry for the delay. Jung-uk Kim --ydfSDwsSStOvRwRS7BH0iEJieVx0JhWRM-- --t9kLvMaX18YVGbJScNvWwfM3fmDuExapt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEl1bqgKaRyqfWXu/CfJ+WJvzb8UYFAlrx7XkACgkQfJ+WJvzb 8UblJgf/UBZjF+HvI0OzADRniHUxmvMle5K5qcoInnHU2GHIe0vUzYZPjfuFjr0T J0gMZUdRv1CgzVtbu/ieKj3InDYU8AnRE7lp0U48c1mr9zeCPMPVeQDLXb91kZE+ R94qylMHl8wnpZS527jj1AC/Nb6cUJqU/t+e5BjIU534HIEE8ue70IiV0TXvftBN IrVACvP6/uI25i99hC7UyXOe9cD1UGuR+SE60YitqXk8cD9HzGt+1267VbO0vwzR XQ5LYMQONz6z3Yr0Dpl6gPLyLrqlhwE+x/spkXlGwbWvVtH1DpUB8n09IEaPxotl G1LT9Zu7tJH7F1CS/AdPnGDvflDDFQ== =HDs0 -----END PGP SIGNATURE----- --t9kLvMaX18YVGbJScNvWwfM3fmDuExapt-- From owner-freebsd-current@freebsd.org Tue May 8 20:11:24 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 99412FC8B92 for ; Tue, 8 May 2018 20:11:24 +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 1DD668A86E for ; Tue, 8 May 2018 20:11:24 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.142] (helo=mjail2.freenet.de) by mout2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fG8xF-0006lm-MO; Tue, 08 May 2018 22:11:21 +0200 Received: from [::1] (port=52428 helo=mjail2.freenet.de) by mjail2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fG8xF-0004lx-IO; Tue, 08 May 2018 22:11:21 +0200 Received: from mx5.freenet.de ([195.4.92.15]:45196) by mjail2.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fG8vE-0002k0-TX; Tue, 08 May 2018 22:09:16 +0200 Received: from p5b22af58.dip0.t-ipconnect.de ([91.34.175.88]:32981 helo=freebsd-t450.fritz.box) by mx5.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1fG8vE-00042L-DM; Tue, 08 May 2018 22:09:16 +0200 Date: Tue, 8 May 2018 22:09:14 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: "Ilya A. Arkhipov" Cc: freebsd-current@freebsd.org Subject: Re: Regression Resume Lenovo T450 Message-ID: <20180508200914.GA73930@freebsd-t450.fritz.box> References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> User-Agent: Mutt/1.9.5 (2018-04-13) X-Spamscore: -6.1 (------) X-Spamreport: Action: no action Symbol: ASN(0.00) Symbol: TO_DN_SOME(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: BAYES_HAM(-3.00) Symbol: NEURAL_HAM(-3.00) Symbol: RCPT_COUNT_TWO(0.00) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: MIME_GOOD(-0.10) Symbol: RCVD_TLS_ALL(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: RCVD_COUNT_ONE(0.00) Message-ID: 20180508200914.GA73930@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 91.34.175.88!32981 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, 08 May 2018 20:11:24 -0000 On Tue, May 08, 2018 at 11:16:48AM +0300, Ilya A. Arkhipov wrote: >Hi, > >I have same issue (thinkpad T450s) after resume notebook cant wake up >but on: >  FreeBSD 12.0-CURRENT #0 r332796: Fri Apr 20 00:42:44 UTC 2018 >root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 >with: >drm-next-kmod-4.11.g20180224 >gpu-firmware-kmod-g20180206_1 > ># sysctl debug.bootverbose=1 ># sysctl debug.acpi.suspend_bounce=1 > >In log (I think it related): >May  8 01:05:06 m1cro kernel: vgapci0: child drmn0 requested >pci_set_powerstate >May  8 01:05:06 m1cro kernel: pci0:0:2:0: Transition from D0 to D3 >May  8 01:05:06 m1cro kernel: pci0: set ACPI power state D3 on >\_SB_.PCI0.VID_ >May  8 01:05:06 m1cro kernel: pci0: failed to set ACPI power state D3 on >\_SB_.PCI0.VID_: AE_BAD_PARAMETER > >where pci0:0:2:0: >vgapci0@pci0:0:2:0:     class=0x030000 card=0x503617aa chip=0x16168086 >rev=0x09 hdr=0x00 >     vendor     = 'Intel Corporation' >     device     = 'HD Graphics 5500' >     class      = display >     subclass   = VGA My T450 does resume now with an current CURRENT(r333291), but unfortunately i do not know why... I tried to track down the phenomenon. I saw that the kernel seemed not to be involved in this matter, since the old BE equipped with a new kernel was able to resume. I cloned the BE capable of resuming and startet copying userland-stuff from the "default" BE to this BE. Stuff was like bin/sbin/lib/libexec folders from / and /usr and so on. It stayed able to resume! Then i made an installworld/installkernel of r333291 into this BE, (but without mergemaster)! Even after this it stayed able to resume! Then I backed up the /etc folder of my "default" BE (which was not able to resume) and copied the /etc from the old BE to "default". After this, "default" was also able to resume again! Long story short, i'm happy my machine resumes again, but i do not have a clue why... P.S. I'm useing drm-stable-kmod, drm-next-kmod did not work for me. -- Manuel From owner-freebsd-current@freebsd.org Wed May 9 03:52: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 72D2AFD36A1 for ; Wed, 9 May 2018 03:52:33 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 CC52187327 for ; Wed, 9 May 2018 03:52:32 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x232.google.com with SMTP id r2-v6so12780121lff.4 for ; Tue, 08 May 2018 20:52:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:openpgp:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=kGsbz0GCJ6yghgKkYHl406XI4dz0lx3yI6dZKU6wt0o=; b=PUa2AUTCij6jb7602LtdCEmRot/i3IcAPNUV1NNPxJMaQ8NMW/76bW+9liwCojw0vW 6kNczVHO9vgNCl1Q8NFDvx1lXAkrw4Qu2eLuLA06oVubFaOMr4dl5HGMM7jWHF16PA3M 5KEGwu79s0iNb+sxhMFb2Dj0v9xLC7iGdAC+Q/sUx5QJ3JqS0XIbR4qxXBgx88Ku7F36 cI0nfSrEv/GBMePj8FHEApKimq2TOOOGw0tLyuDByYEdYBOYVvuVJDHE2OTnDtShNLPo qXNMFK0Y/OmhRzcbYCxdCPZ1bPQb8srZJrYhag4QbG6i4PGoagLkuLP5XHwGbpTaFdEx aktw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:openpgp:message-id:date :user-agent:mime-version:content-language:content-transfer-encoding; bh=kGsbz0GCJ6yghgKkYHl406XI4dz0lx3yI6dZKU6wt0o=; b=pnEMWA4MgimfnG9r/mmAWlqvQSPYR9do2e7FrC3wRTIhqS9GLS2+5egoeEuBnRQTdX 4b9Nkv9shjhEM1UTeBBGYGdz+9UNVBtPW4JIFOda8fPDWO1cyjKBwR91AbPJ+HzSBe/n GiuWYj0Wd0jOFNjCfHTdUbCRbK+CizlX8T1Q+L5qnWpCHmIrIWjN3P5CQBfAaNchFPDp e0aPo4qZeL5J32cn5mrGo/WmZAAbG7kPL3SPHAX3DecowKJTMFiYG/MnHWHXH2uUXd6Y COnfTIcxSkpa27u9cG/2LKTYvFzD5J6CPs5jL1cuyc6rb2HYfkRQQh5SbX2exQnvjoi6 Wdpw== X-Gm-Message-State: ALQs6tBNWWnosKl4clXATvY4fAiMEKSkh5Ile1mF+Q6PDqUej7G9qSoF 0AR7Hjot5Rs8GTCWluYjNdeoaw== X-Google-Smtp-Source: AB8JxZqOB1T7zxC7cIV0sfbzZZHD/MWQToS1ugp5qaFsrK58IW0U1Bvl9YHi/iY00pSeZL4LeQaZKQ== X-Received: by 2002:a2e:6c10:: with SMTP id h16-v6mr17249116ljc.81.1525837950228; Tue, 08 May 2018 20:52:30 -0700 (PDT) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id p5-v6sm4902723ljh.3.2018.05.08.20.52.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 May 2018 20:52:28 -0700 (PDT) To: freebsd-current@freebsd.org From: "Alex V. Petrov" Subject: Help USB keyboard trouble Openpgp: preference=signencrypt Message-ID: <20fe1b1c-1563-ca86-a10d-a91684244c2c@gmail.com> Date: Wed, 9 May 2018 10:52:27 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 09 May 2018 03:52:33 -0000 The new USB-keyboard "Qumo Dragon War Mechanicus K11" continues to print "A" when connected, as if the "a" key is pressed. But in Windows and Linux keyboard work normaly. In log: May 9 10:43:38 alex kernel: ugen2.3: at usbus2 May 9 10:43:38 alex kernel: ukbd0 on uhub6 May 9 10:43:38 alex kernel: ukbd0: on usbus2 May 9 10:43:38 alex kernel: kbd2 at ukbd0 May 9 10:43:38 alex kernel: ukbd1 on uhub6 May 9 10:43:38 alex kernel: ukbd1: on usbus2 May 9 10:43:38 alex kernel: kbd3 at ukbd1 ^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^AMay 9 10:43:46 alex kernel: ugen2.3: at usbus2 (disconnected) May 9 10:43:46 alex kernel: ukbd0: at uhub6, port 3, addr 3 (disconnected) May 9 10:43:46 alex kernel: ukbd0: detached May 9 10:43:46 alex kernel: ukbd1: at uhub6, port 3, addr 3 (disconnected) May 9 10:43:46 alex kernel: ukbd1: detached -- ----- Alex. From owner-freebsd-current@freebsd.org Wed May 9 07:08:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A2FDFFAC79C for ; Wed, 9 May 2018 07:08:25 +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 3DC9F6DAB7 for ; Wed, 9 May 2018 07:08:25 +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 D2F112620AD; Wed, 9 May 2018 09:08:23 +0200 (CEST) Subject: Re: Help USB keyboard trouble To: "Alex V. Petrov" , freebsd-current@freebsd.org References: <20fe1b1c-1563-ca86-a10d-a91684244c2c@gmail.com> From: Hans Petter Selasky Message-ID: Date: Wed, 9 May 2018 09:08:16 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20fe1b1c-1563-ca86-a10d-a91684244c2c@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 09 May 2018 07:08:25 -0000 On 05/09/18 05:52, Alex V. Petrov wrote: > The new USB-keyboard "Qumo Dragon War Mechanicus K11" continues to print > "A" when connected, as if the "a" key is pressed. > But in Windows and Linux keyboard work normaly. > > In log: > > May 9 10:43:38 alex kernel: ugen2.3: at usbus2 > May 9 10:43:38 alex kernel: ukbd0 on uhub6 > May 9 10:43:38 alex kernel: ukbd0: 2.00/1.00, addr 3> on usbus2 > May 9 10:43:38 alex kernel: kbd2 at ukbd0 > May 9 10:43:38 alex kernel: ukbd1 on uhub6 > May 9 10:43:38 alex kernel: ukbd1: 2.00/1.00, addr 3> on usbus2 > May 9 10:43:38 alex kernel: kbd3 at ukbd1 > ^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^AMay > 9 10:43:46 alex kernel: ugen2.3: at usbus2 > (disconnected) > May 9 10:43:46 alex kernel: ukbd0: at uhub6, port 3, addr 3 (disconnected) > May 9 10:43:46 alex kernel: ukbd0: detached > May 9 10:43:46 alex kernel: ukbd1: at uhub6, port 3, addr 3 (disconnected) > May 9 10:43:46 alex kernel: ukbd1: detached > Hi, Can you show the output from: usbconfig -d ugen2.3 dump_device_desc dump_curr_config_desc And also have a look at: usbdump -i usbus2 -f 3 -vvv -s 65536 --HPS BTW: We have a list specifically for USB problems: freebsd-usb@freebsd.org From owner-freebsd-current@freebsd.org Wed May 9 08:06:25 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05B1EFAE4F8 for ; Wed, 9 May 2018 08:06:25 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 987F97BE55 for ; Wed, 9 May 2018 08:06:24 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40gppQ4nzgzDhC3 for ; Wed, 9 May 2018 08:06:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1525853182; bh=ym2hNSAQy8Ruw1YqdHwj/vKE LJOUf/8lRAUCOOZYyrs=; b=OW0DOJrVk4WN46zkOuRo3Iv50zDcZNrASrQZFXE3 UYBk+zckXhF50KFjnfsmWN2BNCV4iR1k1pa56k5BnaJfeDXtW1TNTWAFgo2u3qFS xBXBie1MOgGbLkRNeCoaK1pVTAhk1HWhjdH5Bo1hR0nLeZg4C6D2jMkLWWtNJFpu yoU= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id mpHCPERZwlXD for ; Wed, 9 May 2018 08:06:22 +0000 (UTC) Received: from garnet.daemonic.se (host-90-236-243-88.mobileonline.telia.com [90.236.243.88]) by mail.daemonic.se (Postfix) with ESMTPSA id 40gppQ1CC2zDhBg for ; Wed, 9 May 2018 08:06:22 +0000 (UTC) Subject: Re: Regression Resume Lenovo T450 To: freebsd-current@freebsd.org References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> <20180508200914.GA73930@freebsd-t450.fritz.box> From: Niclas Zeising Message-ID: <2d6880a1-8ad4-9003-8ebb-f4d2b68fe932@daemonic.se> Date: Wed, 9 May 2018 10:06:19 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <20180508200914.GA73930@freebsd-t450.fritz.box> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Language: en-US 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: Wed, 09 May 2018 08:06:25 -0000 On 05/08/18 22:09, Manuel St=FChn wrote: >=20 > P.S. > I'm useing drm-stable-kmod, drm-next-kmod did not work for me. What issues are you seeing with drm-next-kmod? Regards --=20 Niclas From owner-freebsd-current@freebsd.org Wed May 9 11:32: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 6BD41FB4841 for ; Wed, 9 May 2018 11:32:03 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 44AE868706 for ; Wed, 9 May 2018 11:32:02 +0000 (UTC) (envelope-from alexvpetrov@gmail.com) Received: by mail-lf0-x22c.google.com with SMTP id o123-v6so50432359lfe.8 for ; Wed, 09 May 2018 04:32:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:openpgp:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=4wVYSzdDN1Z9y7+Jd9u9BSIxgVoVxGMZSqu777Uy8qw=; b=NsNsqa55t92LQXapJDrxE/ETbWgsVTYp/cBULVNdts4KGWp/0RwWv1xA9sHkPIPnES yXoFXCuBdkVdpOTGnOI2VgV/hJP+zSz+149wFkqmBV8jCJOcdEcjYOtqzJMzFLIRyHVo /B1t0vvvml8syGaKOx91J7kDt4h70Jz++W4i2yEua9Sq3ZbIWSe4gbuDEbEAlnWxIrkk OSMfPIZYbXt2qJJG4OBtA9PUpiWfdVpwTRztpKGVsb6xqz8VpAnzXPZlCNtZDkYNEVuG 16iM1exkJ6L2ifHmcr3XC4CmDgtDjvNd2xA3dLKIoXPpbYRR8fbYkZ9Xepl44vcYHGuB au2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:openpgp:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=4wVYSzdDN1Z9y7+Jd9u9BSIxgVoVxGMZSqu777Uy8qw=; b=WhIVpPGApczgVQVbCY7SVK1WvHcPmv/Yb1+o6KCBDaOv6PIbqk60wAlPzuM1dgmml+ ywdBYhsT7lGCdQTLyeHPvnX6+T0DLDuRxJEilSnl+UDSfIdfBfBIiFYm9/op7UOePQrq WW45FTFZG8/zP4XA3Ut7/cOfznS+TRMpj2iuh2n9kpwjyuqySAv/Vn6iUsNNeKxrYPhD 2j5W1QBfLsNwnzwmUDgKOKHsp5IeyU6JYYp0EFCd53X6MR4DcDUia1+BlqpyhbdVzfKj zKclfxbYWa3ig+xNdKSDRPXXdHAPS8yfkUmc+r8gDocbCBb3RDBNbHT2IIQbKlh4Zm6K Xdeg== X-Gm-Message-State: ALKqPwcFxDlDN0OxemXEUNzWQ5N2to/clCGtUIzhcx7BcVc9nuOglUIT ChBzawlG190VZNDcN9UZfsK5ug== X-Google-Smtp-Source: AB8JxZqBDw8rJlBmDqvftgQXxnutXEhWYG2MMcXOUVq7Fdh247GLXbOF8lH3hto47HyZv8qF81TUng== X-Received: by 2002:a19:13ce:: with SMTP id 75-v6mr8761450lft.106.1525865518184; Wed, 09 May 2018 04:31:58 -0700 (PDT) Received: from alex.super (stone.g-service.ru. [84.22.141.217]) by smtp.googlemail.com with ESMTPSA id o18-v6sm5666198lfg.16.2018.05.09.04.31.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 May 2018 04:31:56 -0700 (PDT) Subject: Re: Help USB keyboard trouble To: Hans Petter Selasky , freebsd-current@freebsd.org References: <20fe1b1c-1563-ca86-a10d-a91684244c2c@gmail.com> From: "Alex V. Petrov" Openpgp: preference=signencrypt Message-ID: <0d62c58e-57a7-bc9b-e690-c96d55904d88@gmail.com> Date: Wed, 9 May 2018 18:31:54 +0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 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: Wed, 09 May 2018 11:32:03 -0000 09.05.2018 14:08, Hans Petter Selasky пишет: > On 05/09/18 05:52, Alex V. Petrov wrote: >> The new USB-keyboard "Qumo Dragon War Mechanicus K11" continues to print >> "A" when connected, as if the "a" key is pressed. >> But in Windows and Linux keyboard work normaly. >> >> In log: >> >> May  9 10:43:38 alex kernel: ugen2.3: at usbus2 >> May  9 10:43:38 alex kernel: ukbd0 on uhub6 >> May  9 10:43:38 alex kernel: ukbd0: > 2.00/1.00, addr 3> on usbus2 >> May  9 10:43:38 alex kernel: kbd2 at ukbd0 >> May  9 10:43:38 alex kernel: ukbd1 on uhub6 >> May  9 10:43:38 alex kernel: ukbd1: > 2.00/1.00, addr 3> on usbus2 >> May  9 10:43:38 alex kernel: kbd3 at ukbd1 >> ^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^A^AMay >> >>   9 10:43:46 alex kernel: ugen2.3: at usbus2 >> (disconnected) >> May  9 10:43:46 alex kernel: ukbd0: at uhub6, port 3, addr 3 >> (disconnected) >> May  9 10:43:46 alex kernel: ukbd0: detached >> May  9 10:43:46 alex kernel: ukbd1: at uhub6, port 3, addr 3 >> (disconnected) >> May  9 10:43:46 alex kernel: ukbd1: detached >> > > Hi, > > Can you show the output from: > > usbconfig -d ugen2.3 dump_device_desc dump_curr_config_desc > > And also have a look at: > > usbdump -i usbus2 -f 3 -vvv -s 65536 > > --HPS > > BTW: We have a list specifically for USB problems: freebsd-usb@freebsd.org > ugen2.3: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x0c45 idProduct = 0x0820 bcdDevice = 0x0100 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 Configuration index 0 bLength = 0x0009 bDescriptorType = 0x0002 wTotalLength = 0x003b bNumInterfaces = 0x0002 bConfigurationValue = 0x0001 iConfiguration = 0x0000 bmAttributes = 0x00a0 bMaxPower = 0x0032 Interface 0 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0000 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0001 iInterface = 0x0000 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x4f, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0081 bmAttributes = 0x0003 wMaxPacketSize = 0x0008 bInterval = 0x0008 bRefresh = 0x0000 bSynchAddress = 0x0000 Interface 1 bLength = 0x0009 bDescriptorType = 0x0004 bInterfaceNumber = 0x0001 bAlternateSetting = 0x0000 bNumEndpoints = 0x0001 bInterfaceClass = 0x0003 bInterfaceSubClass = 0x0001 bInterfaceProtocol = 0x0002 iInterface = 0x0000 Additional Descriptor bLength = 0x09 bDescriptorType = 0x21 bDescriptorSubType = 0x11 RAW dump: 0x00 | 0x09, 0x21, 0x11, 0x01, 0x00, 0x01, 0x22, 0x71, 0x08 | 0x00 Endpoint 0 bLength = 0x0007 bDescriptorType = 0x0005 bEndpointAddress = 0x0082 bmAttributes = 0x0003 wMaxPacketSize = 0x0040 bInterval = 0x0001 bRefresh = 0x0000 bSynchAddress = 0x0000 18:27:21.923619 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 00 05 03 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | flags 0x50 status 0xea3a3 18:27:21.925027 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x50 status 0xca3a1 18:27:21.925048 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0 frame[0] WRITE 0 bytes flags 0x10 status 0xca0a3 18:27:21.927027 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 0 bytes flags 0x10 status 0xea0a1 18:27:21.941516 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 01 00 00 08 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 8 bytes flags 0x10 status 0xea1a3 18:27:21.943021 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 8 bytes 0000 12 01 00 02 00 00 00 40 -- -- -- -- -- -- -- -- |.......@ | flags 0x10 status 0xca1a1 18:27:21.946603 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 01 00 00 12 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 18 bytes flags 0x10 status 0xea1a3 18:27:21.948007 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 18 bytes 0000 12 01 00 02 00 00 00 40 45 0C 20 08 00 01 01 02 |.......@E. .....| 0010 00 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xca1a1 18:27:21.948038 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xca1a3 18:27:21.950018 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 04 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xea1a1 18:27:21.950041 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 03 00 00 04 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 4 bytes flags 0x10 status 0xea1a3 18:27:21.952019 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 4 bytes 0000 04 03 09 04 -- -- -- -- -- -- -- -- -- -- -- -- |.... | flags 0x10 status 0xca1a1 18:27:21.952043 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xca1a3 18:27:21.953992 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 0C 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xea1a1 18:27:21.954013 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 01 03 09 04 0C 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 12 bytes flags 0x10 status 0xea1a3 18:27:21.955992 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 12 bytes 0000 0C 03 53 00 4F 00 4E 00 69 00 58 00 -- -- -- -- |..S.O.N.i.X. | flags 0x10 status 0xca1a1 18:27:21.956023 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 02 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 2 bytes flags 0x10 status 0xca1a3 18:27:21.957994 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 2 bytes 0000 16 03 -- -- -- -- -- -- -- -- -- -- -- -- -- -- |.. | flags 0x10 status 0xea1a1 18:27:21.958017 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 02 03 09 04 16 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 22 bytes flags 0x10 status 0xea1a3 18:27:21.960001 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=24,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 22 bytes 0000 16 03 55 00 53 00 42 00 20 00 44 00 45 00 56 00 |..U.S.B. .D.E.V.| 0010 49 00 43 00 45 00 -- -- -- -- -- -- -- -- -- -- |I.C.E. | flags 0x10 status 0xca1a1 18:27:21.960034 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 02 00 00 09 00 -- -- -- -- -- -- -- -- |........ | frame[1] READ 9 bytes flags 0x10 status 0xca1a3 18:27:21.961993 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=12,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 9 bytes 0000 09 02 3B 00 02 01 00 A0 32 -- -- -- -- -- -- -- |..;.....2 | flags 0x10 status 0xea1a1 18:27:21.962017 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 80 06 00 02 00 00 3B 00 -- -- -- -- -- -- -- -- |......;. | frame[1] READ 59 bytes flags 0x10 status 0xea1a3 18:27:21.963992 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=60,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 59 bytes 0000 09 02 3B 00 02 01 00 A0 32 09 04 00 00 01 03 01 |..;.....2.......| 0010 01 00 09 21 11 01 00 01 22 4F 00 07 05 81 03 08 |...!...."O......| 0020 00 08 09 04 01 00 01 03 01 02 00 09 21 11 01 00 |............!...| 0030 01 22 71 00 07 05 82 03 40 00 01 -- -- -- -- -- |."q.....@.. | flags 0x10 status 0xca1a1 18:27:21.964014 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 00 09 01 00 00 00 00 00 -- -- -- -- -- -- -- -- |........ | flags 0x10 status 0xca1a3 18:27:21.966005 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xea1a1 18:27:21.967955 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 00 00 4F 00 -- -- -- -- -- -- -- -- |..."..O. | frame[1] READ 79 bytes flags 0x10 status 0xea1a3 18:27:21.969995 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=80,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 79 bytes 0000 05 01 09 06 A1 01 05 07 19 E0 29 E7 15 00 25 01 |..........)...%.| 0010 75 01 95 08 81 02 95 01 75 08 81 01 95 05 75 01 |u.......u.....u.| 0020 05 08 19 01 29 05 91 02 95 01 75 03 91 01 95 06 |....).....u.....| 0030 75 08 15 00 26 FF 00 05 07 19 00 2A FF 00 81 00 |u...&......*....| 0040 05 0C 09 00 15 80 25 7F 95 40 75 08 B1 02 C0 -- |......%..@u.... | flags 0x10 status 0xca1a1 18:27:21.971148 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 00 00 4F 00 -- -- -- -- -- -- -- -- |..."..O. | frame[1] READ 79 bytes flags 0x10 status 0xca1a3 18:27:21.972994 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=80,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 79 bytes 0000 05 01 09 06 A1 01 05 07 19 E0 29 E7 15 00 25 01 |..........)...%.| 0010 75 01 95 08 81 02 95 01 75 08 81 01 95 05 75 01 |u.......u.....u.| 0020 05 08 19 01 29 05 91 02 95 01 75 03 91 01 95 06 |....).....u.....| 0030 75 08 15 00 26 FF 00 05 07 19 00 2A FF 00 81 00 |u...&......*....| 0040 05 0C 09 00 15 80 25 7F 95 40 75 08 B1 02 C0 -- |......%..@u.... | flags 0x10 status 0xea1a1 18:27:21.973061 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 21 0A 00 00 00 00 00 00 -- -- -- -- -- -- -- -- |!....... | flags 0x10 status 0xea1a3 18:27:21.974996 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xca1a1 18:27:21.976524 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 00 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0xea1a3 18:27:21.976533 usbus2.3 SUBM-INTR-EP=00000081,SPD=FULL,NFR=1,SLEN=0,IVAL=8 frame[0] READ 8 bytes flags 0xa status 0xeb023 18:27:21.977993 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 01 00 71 00 -- -- -- -- -- -- -- -- |..."..q. | frame[1] READ 113 bytes flags 0x10 status 0x4a1a3 18:27:21.977998 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xca1a1 18:27:21.979993 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=116,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 113 bytes 0000 05 01 09 06 A1 01 85 01 05 07 19 04 29 70 15 00 |............)p..| 0010 25 01 75 01 95 78 81 02 C0 05 01 09 80 A1 01 85 |%.u..x..........| 0020 02 05 01 19 81 29 83 15 00 25 01 95 03 75 01 81 |.....)...%...u..| 0030 02 95 01 75 05 81 01 C0 05 0C 09 01 A1 01 85 03 |...u............| 0040 15 00 26 FF 1F 19 00 2A FF 1F 75 10 95 01 81 00 |..&....*..u.....| 0050 C0 06 1C FF 09 92 A1 01 85 04 19 00 2A FF 00 15 |............*...| 0060 00 26 FF 00 75 08 95 3F 91 00 19 00 29 FF 81 00 |.&..u..?....)...| 0070 C0 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0x10 status 0xea1a1 18:27:21.980946 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 01 00 71 00 -- -- -- -- -- -- -- -- |..."..q. | frame[1] READ 113 bytes flags 0x10 status 0xea1a3 18:27:21.982991 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=116,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 113 bytes 0000 05 01 09 06 A1 01 85 01 05 07 19 04 29 70 15 00 |............)p..| 0010 25 01 75 01 95 78 81 02 C0 05 01 09 80 A1 01 85 |%.u..x..........| 0020 02 05 01 19 81 29 83 15 00 25 01 95 03 75 01 81 |.....)...%...u..| 0030 02 95 01 75 05 81 01 C0 05 0C 09 01 A1 01 85 03 |...u............| 0040 15 00 26 FF 1F 19 00 2A FF 1F 75 10 95 01 81 00 |..&....*..u.....| 0050 C0 06 1C FF 09 92 A1 01 85 04 19 00 2A FF 00 15 |............*...| 0060 00 26 FF 00 75 08 95 3F 91 00 19 00 29 FF 81 00 |.&..u..?....)...| 0070 C0 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0x10 status 0xca1a1 18:27:21.983607 usbus2.3 SUBM-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 81 06 00 22 01 00 71 00 -- -- -- -- -- -- -- -- |..."..q. | frame[1] READ 113 bytes flags 0x10 status 0xca1a3 18:27:21.984985 usbus2.3 DONE-CTRL-EP=00000080,SPD=FULL,NFR=2,SLEN=116,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] READ 113 bytes 0000 05 01 09 06 A1 01 85 01 05 07 19 04 29 70 15 00 |............)p..| 0010 25 01 75 01 95 78 81 02 C0 05 01 09 80 A1 01 85 |%.u..x..........| 0020 02 05 01 19 81 29 83 15 00 25 01 95 03 75 01 81 |.....)...%...u..| 0030 02 95 01 75 05 81 01 C0 05 0C 09 01 A1 01 85 03 |...u............| 0040 15 00 26 FF 1F 19 00 2A FF 1F 75 10 95 01 81 00 |..&....*..u.....| 0050 C0 06 1C FF 09 92 A1 01 85 04 19 00 2A FF 00 15 |............*...| 0060 00 26 FF 00 75 08 95 3F 91 00 19 00 29 FF 81 00 |.&..u..?....)...| 0070 C0 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0x10 status 0xea1a1 18:27:21.985190 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 21 0B 00 00 01 00 00 00 -- -- -- -- -- -- -- -- |!....... | flags 0x10 status 0xea1a3 18:27:21.986981 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xca1a1 18:27:21.987057 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=8,IVAL=0 frame[0] WRITE 8 bytes 0000 21 0A 00 00 01 00 00 00 -- -- -- -- -- -- -- -- |!....... | flags 0x10 status 0xca1a3 18:27:21.988983 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes flags 0x10 status 0xea1a1 18:27:21.989128 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 01 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 00 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0xea1a3 18:27:21.989135 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0xeb023 18:27:21.990981 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xca1a1 18:27:21.990984 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x6b023 18:27:21.990987 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=4,IVAL=1,ERR=0 frame[0] READ 3 bytes 0000 FF 01 47 -- -- -- -- -- -- -- -- -- -- -- -- -- |..G | flags 0xa status 0xcb021 18:27:21.997877 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 01 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 05 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0xca1a3 18:27:21.997891 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x4b023 18:27:21.997894 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=64,IVAL=1,ERR=0 frame[0] READ 64 bytes 0000 00 00 00 00 00 00 00 00 01 00 00 00 12 00 00 00 |................| 0010 BE 7D 00 00 02 00 00 00 3B 00 00 00 36 7F 00 00 |.}......;...6...| 0020 03 00 00 00 04 00 00 00 71 7F 00 00 03 09 00 00 |........q.......| 0030 04 00 00 00 71 7F 00 00 03 00 01 00 0C 00 00 00 |....q...........| flags 0xa status 0xcb021 18:27:22.004433 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 00 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 05 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0x4a1a3 18:27:22.004440 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xea1a1 18:27:22.004454 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x4b023 18:27:22.004456 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=64,IVAL=1,ERR=0 frame[0] READ 64 bytes 0000 00 00 00 00 00 00 00 00 01 00 00 00 12 00 00 00 |................| 0010 BE 7D 00 00 02 00 00 00 3B 00 00 00 36 7F 00 00 |.}......;...6...| 0020 03 00 00 00 04 00 00 00 71 7F 00 00 03 09 00 00 |........q.......| 0030 04 00 00 00 71 7F 00 00 03 00 01 00 0C 00 00 00 |....q...........| flags 0xa status 0xeb021 18:27:22.005981 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 01 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0x6a1a3 18:27:22.005987 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xea1a1 18:27:22.007995 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x6b023 18:27:22.008000 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=64,IVAL=1,ERR=0 frame[0] READ 64 bytes 0000 00 00 00 00 00 00 00 00 01 00 00 00 12 00 00 00 |................| 0010 BE 7D 00 00 02 00 00 00 3B 00 00 00 36 7F 00 00 |.}......;...6...| 0020 03 00 00 00 04 00 00 00 71 7F 00 00 03 09 00 00 |........q.......| 0030 04 00 00 00 71 7F 00 00 03 00 01 00 0C 00 00 00 |....q...........| flags 0xa status 0xeb021 18:27:22.008008 usbus2.3 SUBM-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=12,IVAL=0 frame[0] WRITE 8 bytes 0000 21 09 00 02 00 00 01 00 -- -- -- -- -- -- -- -- |!....... | frame[1] WRITE 1 bytes 0000 01 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- |. | flags 0 <0> status 0x6a1a3 18:27:22.008012 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xca1a1 18:27:22.009992 usbus2.3 DONE-CTRL-EP=00000000,SPD=FULL,NFR=2,SLEN=0,IVAL=0,ERR=0 frame[0] WRITE 8 bytes frame[1] WRITE 1 bytes flags 0 <0> status 0xca1a1 18:27:26.234883 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x6b023 18:27:26.234891 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=4,IVAL=1,ERR=0 frame[0] READ 3 bytes 0000 03 01 04 -- -- -- -- -- -- -- -- -- -- -- -- -- |... | flags 0xa status 0xcb021 18:27:35.733017 usbus2.3 DONE-INTR-EP=00000081,SPD=FULL,NFR=0,SLEN=0,IVAL=8,ERR=CANCELLED flags 0xa status 0xab01c 18:27:35.733024 usbus2.3 DONE-INTR-EP=00000081,SPD=FULL,NFR=0,SLEN=0,IVAL=8,ERR=CANCELLED flags 0xa status 0x8b00c 18:27:35.733493 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1,ERR=IOERROR frame[0] READ 0 bytes flags 0xa status 0xcb021 18:27:35.736016 usbus2.3 SUBM-INTR-EP=00000082,SPD=FULL,NFR=1,SLEN=0,IVAL=1 frame[0] READ 64 bytes flags 0xa status 0x4b023 18:27:35.736022 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=0,SLEN=0,IVAL=1,ERR=CANCELLED flags 0x10a status 0x83025 18:27:35.742030 usbus2.3 DONE-INTR-EP=00000082,SPD=FULL,NFR=0,SLEN=0,IVAL=1,ERR=CANCELLED flags 0xa status 0xab00c -- ----- Alex. From owner-freebsd-current@freebsd.org Wed May 9 14:10:29 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 73DF4FBB82A for ; Wed, 9 May 2018 14:10:29 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [IPv6:2a01:4f8:150:80b1:fe57:f772:524c:99d0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 133686C03A for ; Wed, 9 May 2018 14:10:29 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:14e1:4320:4dfb:a36e:7dc7:d7d]) by madarka.gustik.eu (Postfix) with ESMTPSA id 9FA841330D for ; Wed, 9 May 2018 16:10:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1525875021; bh=bOaTY8yGKkoiWS3yBAEAJJLIG3+pQnaynGIuiwba+Tc=; h=Date:From:To:Subject; b=Ry+A7JpdspnAS6vdFzm2zjVq9YimEfTye5CM5V6yLu90P5xBIW3Uu97BmdIotOHJr ni+SqPjOCRrbpXyaMlNHagbT3rKny1BwsgGgbLK+KvxIBx3fBOEH+sA6cxngKPXGSZ cR8puoU/pPB9vz3fdKGzY6HL9PHTuTBQPv0YwV+M= Date: Wed, 9 May 2018 16:10:20 +0200 From: Lars Schotte To: freebsd-current@freebsd.org Subject: pfctl: igb0: driver does not support altq Message-ID: <20180509161020.1eb7325a@romy.j20.helspy.pw> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 09 May 2018 14:10:29 -0000 Hi folks, I get a message: pfctl: igb0: driver does not support altq on: 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r333388: Wed May 9 00:58:52 CEST 2018 root@***censored***:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK amd64 where /usr/src/sys/amd64/conf/GUSTIK contains: include GENERIC ident GUSTIK options ALTQ options ALTQ_CBQ # Class Based Queueing options ALTQ_RED # Random Early Detection options ALTQ_RIO # RED In/Out options ALTQ_CODEL # CoDel Active Queueing options ALTQ_HFSC # Hierarchical Packet Scheduler options ALTQ_FAIRQ # Fair Packet Scheduler options ALTQ_CDNR # Traffic conditioner options ALTQ_PRIQ # Priority Queueing options ALTQ_NOPCC # Required if the TSC is unusable options ALTQ_DEBUG Problem does not seem to appear on 10-stable, or 11-stable. Actually on 10.4 it worked as expected. I will investigate if this problem affects only igbX driver or some others as well, I have reX and emX at my disposal. -- Lars Schotte Mudroňova 13 92101 PieÅ¡Å¥any From owner-freebsd-current@freebsd.org Wed May 9 16:01: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 9EE96FC3B59 for ; Wed, 9 May 2018 16:01:13 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2F17D86EC9 for ; Wed, 9 May 2018 16:01:13 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fGRWj-00056b-QP; Wed, 09 May 2018 18:01:13 +0200 Date: Wed, 9 May 2018 18:01:13 +0200 From: Kurt Jaeger To: Lars Schotte Cc: freebsd-current@freebsd.org Subject: Re: pfctl: igb0: driver does not support altq Message-ID: <20180509160113.GX37752@home.opsec.eu> References: <20180509161020.1eb7325a@romy.j20.helspy.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180509161020.1eb7325a@romy.j20.helspy.pw> 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, 09 May 2018 16:01:13 -0000 Hi! > I get a message: > pfctl: igb0: driver does not support altq > > on: > 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r333388: > Wed May 9 00:58:52 CEST 2018 > root@***censored***:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK > amd64 [...] > Problem does not seem to appear on 10-stable, or 11-stable. > Actually on 10.4 it worked as expected. There is a long ongoing debate on the future of ALTQ, and one PR that might be of interest: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257 See also: http://undeadly.org/cgi?action=article&sid=20140419151959 http://bsdly.blogspot.de/2011/07/anticipating-post-altq-world.html https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409 -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Wed May 9 19:00:12 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0E122FC8593 for ; Wed, 9 May 2018 19:00:12 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 871256FFDD for ; Wed, 9 May 2018 19:00:11 +0000 (UTC) (envelope-from bsam@passap.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 47AB0FC858F; Wed, 9 May 2018 19:00:11 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 206D3FC858E for ; Wed, 9 May 2018 19:00:11 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward106p.mail.yandex.net (forward106p.mail.yandex.net [IPv6:2a02:6b8:0:1472:2741:0:8b7:109]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A8E36FFD9 for ; Wed, 9 May 2018 19:00:10 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback12j.mail.yandex.net (mxback12j.mail.yandex.net [IPv6:2a02:6b8:0:1619::87]) by forward106p.mail.yandex.net (Yandex) with ESMTP id D21202D84DBD for ; Wed, 9 May 2018 21:59:59 +0300 (MSK) Received: from smtp3p.mail.yandex.net (smtp3p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:8]) by mxback12j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 1vfSc02eZy-xxlaMNwo; Wed, 09 May 2018 21:59:59 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1525892399; bh=zgtT2Ff/kKWFf+Z6QaYgwX4abVEshguKRhLKDeIEbZc=; h=To:From:Subject:Message-ID:Date; b=lZVq3HPKr2OTfmueNEC7SgReE/tg04zdL61ziR9j3ZJS6Lm4ZtTMtd04X/Q4uhRlf amri9h/R0Ot2MdZuIXTdjJT+kfd+HhxWGJVnu4bKidujQjr1/deB1Ns2oug0L0v/tO BoCI/YLnOd4HKhxAcBFH7iiT7Puv6XTYAbSk97PY= Received: by smtp3p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id WLoy5d4MR5-xxcKta7Y; Wed, 09 May 2018 21:59:59 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1525892399; bh=zgtT2Ff/kKWFf+Z6QaYgwX4abVEshguKRhLKDeIEbZc=; h=To:From:Subject:Message-ID:Date; b=lZVq3HPKr2OTfmueNEC7SgReE/tg04zdL61ziR9j3ZJS6Lm4ZtTMtd04X/Q4uhRlf amri9h/R0Ot2MdZuIXTdjJT+kfd+HhxWGJVnu4bKidujQjr1/deB1Ns2oug0L0v/tO BoCI/YLnOd4HKhxAcBFH7iiT7Puv6XTYAbSk97PY= Authentication-Results: smtp3p.mail.yandex.net; dkim=pass header.i=@passap.ru To: current@freebsd.org From: Boris Samorodov Subject: pkg, drm-next-kmod and base packages Openpgp: preference=signencrypt Autocrypt: addr=bsam@passap.ru; prefer-encrypt=mutual; keydata= xsFNBFKPjHIBEACwdrpPbV9pGnP/MFO0lsubC1ruUr7y79tnT/gWKlI3i8gPPS3GG5FVFwjM 9YsSv7H5wxKlHa7ufFa8BETQQF+tBWlOy5lGh0a55M9qNCY+jlnAbmRRNdrIpr8ywHHd3eIr DBafMB6CG5GIgEMJ1OBcHmNuIUOd1A8Esi4eGpd6NFRcT3O58dC8wHfEqpdCVVX+mrPEWAno Q72i0q+j6NtsyTNTFEiACiuXeW+h2xl4zj09rr1CXlCcBV4SQ20uxJ4gegGapAMXzXDUpvCD X1M8wcjlUVa44PtTvGj5OxhGypKZJnz1CQcIQJ4qjPxvg6p8PsGnAaEWfdXPL5CH5GUmuaUt qMRbzyR/Bo/K8bYMYl5o/YcAjXopkn4ij1H3KACqE5YWvEwcfiNKX++uhuVhtja34sOTWJl9 ilboFJ9C9RDq/zE6oxF4vBGMVWjF4qm88P2PXWULLPPyhg98NxFMbH0XXWnOUt0x8yqY2v0t kz2sWn1ft/o09gQ0aaUtzYvG+cLg3FeU0EeXYum+jdTKdA27uKtTmgRuwQ135XIf0+4M5hrX pw2dBh/JljkQiv1lhKiCQrVBdS52nRvRXaCo7t0OiRR4y7268LYPr7ellCq3Ywykdj8bWvmt szYcnYBi7wiftHCid8wR0bQdyGRUcuc4IH4fCf7hS8trSjukWQARAQABzSJCb3JpcyBTYW1v cm9kb3YgPGJzYW1ARnJlZUJTRC5vcmc+wsF9BBMBCAAnBQJSj4yzAhsDBQkJZgGABQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAAoJEJYOILA6P20ooagP/3r6OfyiGW5B3Fv1ylBWp8lzHZVD mI8pGW7J4ubizPsz6t+CHBofNvCkrxjW7C1WDq7qRDfgqL6rYBV6D6GMtdUm5oKmnyJNNET5 hXRP7/ljzYDaLbBaVY5Oidu7OBS4k6RRwlypo5vFaI7/YJp6iIm80eIC6MCmPJpsRqdsY6pj ng5/F8obspP+HfrORHYLYRg8mt0PLG6UwkkiOdP48z2X0Arhjbt2v5QCDwOzwerE7JfN3/P6 Knf1Soiki9vWw6CAaC5K/oo/tdbvfiUzrzxSAaV8K7HQ4dVqaKFxI5xQ2GnafnEfyPLBZQQR WdmYJcL1qwCk4D76VrN2whR94+ZczPFji6jGCxOUo4mM/hqwq44KF9xi7asZmZC7/LHZ11ac j8NMEPHQJ4nmB7q9of4Wwu9XeJUrTt7oY+AQKpmewRxab5K0EJDd9IyfQusNgHHVpF2Jpa7U MAxClPtWdoXfRSk3esxeLhu33WJOpVpAUVeLIXF9g6EokOflV/0rb0onjuSeisVihvX/eG20 8eiSomt3xYgM+2ijGWugm5ie6eHkv5o34fcG9oanG71t9QIb7IgJ36UnLYGUcOyrpByUGEfg bYQgSEgSiDBbZBZVdM+aT2kJgbqRRYeqaqjmIXvSzL4c7zSRqQXv6h0L/P11CbMjycVNQ6uo iiP0eu5vzsFNBFKPjHIBEADUsIZuXuLo8baU85CU+Mv4gdyHwXzgIeNEG28O7Iu9bssY+Gt+ NiLI+4ZpBeQDbFzBGvyA/UoYDfURdY3KT6lXl2qamRaFz7SDtXuGpN9jDVgU048bbMjN4nk/ vV5ioqWw3V0x7eOiBtUbb17P1CVnnl249KyjdtMDu8jf7KRe2KgiFXgoL5ZeiGuN4g4n17VT H9DQCXJhIYPl5d7NEeGaUVKtPTEE1mClNt048dF/euduFRomxpwgXsg+tkSdZb1ffinYuFa7 mSMLg96LubVaels2rqQu097OO9GFqxyoBFzXtRwCOl2LbRJpG2ktJisin1zEshHx8slMC0km veXQv4S/LL33TNFPhfrbTJddMQhcrjwe4kDtdGY3XtBV2VEjUGRs63BSjtHPAQWx/JQTaBwx 5IPwuJAs0H0eJwjNtq+ZunzM1Dgbbtq4rQPsgrPIrtjHSv+u6ORW2wmd5uHxGyvADB8YyYRj R6scSLzLp7KrcFmkGq3RJcB3aDYi9r4TXr/gSZk4P0swhEXqo9oiddwRo7tv6JboRwltLG1F o91W5H8pwV5iG/R0EsM2k/aIAMOTBiZ2Lkk0bBH62hd/mp4p08z0E12QL/IYbH7VuXtz9ToA KiMtAAKg4nDe58ILAkfEAhNNsStSMOEjlXMz/6n7gsRrLljS16nmgd+8FQARAQABwsFlBBgB CAAPBQJSj4xyAhsMBQkJZgGAAAoJEJYOILA6P20odvEP/0KAbaBFAyJqhwXmj4ta1i55rkd+ 6vc46Az4trNZ6H/0XOJK5v9JGW1mz5aOURzSaSCitqS9uQa1qMssggn7a2pDRYA6LPKd0xgF 9KT68QMApN3KOtpFgn1D8rV6wywovntl3CpubiaDEmBD/fD7wrHiG+KsFzR48Dqzoth94D82 zIlCzfhbKDUzPwgc5ipds48MuP150WTwyKvOytwZbH/0RBGlqw/jkA6z3P86We4TuD0RFHZl /hpuSNadbUkfAOYI0LUfSFz/uYds08Rjf/YIawjA34mZFsDsWuoHhHqjl/x9uHA/o553LSw7 TmW/oR1xja/sWBaub/9WG9ZwuhPFE25DIG2eFQdv9d7XR7dyF+SIIkhiq4TuhD8hYYWPnvfN nzI9pfq3b9ag31P1ZHjpy9WxDplW7nTQq1yGLYOsd8Hoeh+QCY7PC/Ws8N566kW0bcUM1d12 2ZXA5XS0EBabmaAccuFtrIMt86XXgPYUqDOW4N/qKdF1dG+bhPPlFN3Lx9Sf3fbbNvJaI1DY bPgGUnCzctuLLfiARaFdgACXVhJ8ZhB6h7zPBOK8SB/bVSOqxcZh9elnusnkelNg57Up1qX3 pgkTpbOtvicdN2gogQQvtV40Nljrxmu2o0MoMcyqAxVG7KhKUih38fFqqrWEpFsVaLJeFk1u 4YL+0DfP Message-ID: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> Date: Wed, 9 May 2018 21:59:58 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 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: Wed, 09 May 2018 19:00:12 -0000 Hi All, I use self-built base packages. How can I test/use drm-next-kmod? Packages for kernel and drm-nex-kmod are in conflict: ----- ╰→ sudo pkg install drm-next-kmod-4.11.g20180224 Updating FreeBSD-base repository catalogue... FreeBSD-base repository is up to date. Updating FreeBSD repository catalogue... FreeBSD repository is up to date. Updating passap repository catalogue... passap repository is up to date. All repositories are up to date. Checking integrity... done (1 conflicting) - drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on /boot/modules/drm.ko Checking integrity... done (0 conflicting) The following 3 package(s) will be affected (of 0 checked): Installed packages to be REMOVED: FreeBSD-kernel-pkg64x-12.0.s20180509041454 New packages to be INSTALLED: drm-next-kmod: 4.11.g20180224 [FreeBSD] gpu-firmware-kmod: g20180206_1 [FreeBSD] Number of packages to be removed: 1 Number of packages to be installed: 2 The operation will free 91 MiB. Proceed with this action? [y/N]: ----- -- WBR, bsam From owner-freebsd-current@freebsd.org Wed May 9 20:49: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 53964FCBC79 for ; Wed, 9 May 2018 20:49:52 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from madarka.gustik.eu (madarka.gustik.eu [176.9.62.177]) (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 E83556ADB7 for ; Wed, 9 May 2018 20:49:51 +0000 (UTC) (envelope-from lars@gustik.eu) Received: from romy.j20.helspy.pw (unknown [IPv6:2a01:c844:14e1:4320:4dfb:a36e:7dc7:d7d]) by madarka.gustik.eu (Postfix) with ESMTPSA id BEAF513324; Wed, 9 May 2018 22:49:49 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gustik.eu; s=mail; t=1525898989; bh=dhHFwZND08C8DWIRlz8uXQzf0DvhfGY2n3O2dBE1YYw=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=WXe1U8OtQ7GpD8HYPrzofh/RV8xB86YXLe/BkYhotkZ6llBsvYAcZnhxFRNG9ZJIF GLwSK3MiPmR11fh9emFaMywCUtAVed6M+CQGAEkOFmh4Z1uB+1KuebMlUNCae+gLJo 95Xrae9JFoD7sZdBD7Cqp/tCjfFP4Ilp2wYQu3sI= Date: Wed, 9 May 2018 22:49:48 +0200 From: Lars Schotte To: Kurt Jaeger Cc: freebsd-current@freebsd.org Subject: Re: pfctl: igb0: driver does not support altq Message-ID: <20180509224948.2f1a8717@romy.j20.helspy.pw> In-Reply-To: <20180509160113.GX37752@home.opsec.eu> References: <20180509161020.1eb7325a@romy.j20.helspy.pw> <20180509160113.GX37752@home.opsec.eu> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.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, 09 May 2018 20:49:52 -0000 As OpenBSD fan, who also uses OpenBSD on EdgerouterLite, I would be pleased to hear that FreeBSD-12 would be a release where PF is updated to some newer version, possibly having parity with OpenBSD. In the meantime it looks like I will need to learn IPFW to do QoS. BTW: I was looking at the whatsnew-wiki of FreeBSD and I can not find any reliable resources of what FreeBSD-12 will be like. On the FreeBSD website it is already noted as incomming, however I have no idea what will be included in this release. Do you know of some? Thanks. On Wed, 9 May 2018 18:01:13 +0200 Kurt Jaeger wrote: > Hi! > > > I get a message: > > pfctl: igb0: driver does not support altq > > > > on: > > 12.0-CURRENT FreeBSD 12.0-CURRENT #1 r333388: > > Wed May 9 00:58:52 CEST 2018 > > root@***censored***:/usr/obj/usr/src/amd64.amd64/sys/GUSTIK > > amd64 > [...] > > Problem does not seem to appear on 10-stable, or 11-stable. > > Actually on 10.4 it worked as expected. > > There is a long ongoing debate on the future of ALTQ, > and one PR that might be of interest: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257 > > See also: > > http://undeadly.org/cgi?action=article&sid=20140419151959 > http://bsdly.blogspot.de/2011/07/anticipating-post-altq-world.html > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409 > -- Lars Schotte Mudroňova 13 92101 PieÅ¡Å¥any From owner-freebsd-current@freebsd.org Wed May 9 23:45: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 A63A7FCF1ED; Wed, 9 May 2018 23:45:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3DD3572828; Wed, 9 May 2018 23:45:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w49NjqaE039550 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 9 May 2018 16:45:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w49Njp0F039549; Wed, 9 May 2018 16:45:51 -0700 (PDT) (envelope-from sgk) Date: Wed, 9 May 2018 16:45:51 -0700 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Runtime loader issue Message-ID: <20180509234551.GA39526@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.9.2 (2017-12-15) 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, 09 May 2018 23:45:59 -0000 In review PR 228007, it came to my attention some individuals are mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD issue". See https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html The problem can be summarized by the following % gfortran7 -o z h.f90 % ./z /lib/libgcc_s.so.1: version GCC_4.8.0 required by \ /usr/local/lib/gcc7/libgfortran.so.4 not found gfortran7 is installed from ports/lang/gcc7. This is not a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. Specifically, there is a shared library name clash. % ldconfig -r | grep gcc_ 6:-lgcc_s.1 => /lib/libgcc_s.so.1 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 % ldd z z: libgfortran.so.4 => /usr/local/lib/gcc7/libgfortran.so.4 (0x200645000) libm.so.5 => /lib/libm.so.5 (0x200a17000) libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x200a4b000) libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200a63000) libc.so.7 => /lib/libc.so.7 (0x200ca3000) So, the runtime loader finds 6 instead of 716, tries to link, fails, and issues an error message. There are a number ways to fix this issue. 1) By far, the best solution would be to stop hijacking the libgcc name in libraries installed on FreeBSD that are not related to actual GCC software. % ls -l /lib/libgcc* /usr/lib/libgcc* (trimming lines) /lib/libgcc_s.so.1 /usr/lib/libgcc.a@ -> libcompiler_rt.a /usr/lib/libgcc_eh.a /usr/lib/libgcc_eh_p.a /usr/lib/libgcc_p.a@ -> libcompiler_rt_p.a /usr/lib/libgcc_s.so@ -> ../../lib/libgcc_s.so.1 Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm aware that clang does not work on all archs and the ancient gcc lives on. 2) Given the expected push back againt solution 1), this solution proposes bumping the library version for /lib/libgcc_s.so.1 from 1 to some larger value, say, 10. It is unlikely that GCC will bump its shared library number anytime soon. GCC bumped it from 0 to 1 some 16 years ago. https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 This solution, however, papers over the general problem with name clashes. 3) This solution is to actually fix the runtime loader. If an error occurs with loading a shared library, then iterate over the entries in the hints file to check to see if another hint would satisfy the linking. Here, instead of issuing the above error, the loader would find entry 716, and load the correct libgcc_s.so.1. Admittedly, I haven't looked to see how difficult this solution would be. 4) Bump the shared library number of the individual ports. As a proof of concept, I've done this with ports/lang/gcc6. % cat /usr/ports/lang/gcc6/files/patch-t-slibgcc --- libgcc/config/t-slibgcc.orig 2018-05-08 12:47:42.334495000 -0700 +++ libgcc/config/t-slibgcc 2018-05-08 12:45:26.872312000 -0700 @@ -20,7 +20,7 @@ SHLIB_EXT = .so SHLIB_SOLINK = @shlib_base_name@.so -SHLIB_SOVERSION = 1 +SHLIB_SOVERSION = 2 SHLIB_SONAME = @shlib_base_name@.so.$(SHLIB_SOVERSION) SHLIB_MAP = @shlib_map_file@ SHLIB_OBJS = @shlib_objs@ % ldconfig -r | grep gcc_ 6:-lgcc_s.1 => /lib/libgcc_s.so.1 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 766:-lgcc_s.2 => /usr/local/lib/gcc6/libgcc_s.so.2 % gfortran6 -o z h.f90 % ./z hello % ldd z z: libgfortran.so.3 => /usr/local/lib/gcc6/libgfortran.so.3 (0x200645000) libm.so.5 => /lib/libm.so.5 (0x20096c000) libgcc_s.so.2 => /usr/local/lib/gcc6/libgcc_s.so.2 (0x2009a0000) libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) libc.so.7 => /lib/libc.so.7 (0x200df7000) This works for this particular name conflict. Hopefully, FreeBSD never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, however, introduces an incompatibility with what is actually distributed by GCC. Finally, can people stop referring to the above error as "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. -- Steve From owner-freebsd-current@freebsd.org Thu May 10 03:25: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 BBB7CFAB87F for ; Thu, 10 May 2018 03:25:02 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4BC268102B for ; Thu, 10 May 2018 03:25:02 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fGcCR-0006t0-SX; Thu, 10 May 2018 05:24:59 +0200 Date: Thu, 10 May 2018 05:24:59 +0200 From: Kurt Jaeger To: Lars Schotte Cc: freebsd-current@freebsd.org Subject: What's in FreeBSD12 Message-ID: <20180510032459.GY37752@home.opsec.eu> References: <20180509161020.1eb7325a@romy.j20.helspy.pw> <20180509160113.GX37752@home.opsec.eu> <20180509224948.2f1a8717@romy.j20.helspy.pw> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180509224948.2f1a8717@romy.j20.helspy.pw> 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, 10 May 2018 03:25:02 -0000 Hi! > As OpenBSD fan, who also uses OpenBSD on EdgerouterLite, > I would be pleased to hear that FreeBSD-12 would be a release where PF > is updated to some newer version, possibly having parity with OpenBSD. > > In the meantime it looks like I will need to learn IPFW to do QoS. > > BTW: I was looking at the whatsnew-wiki of FreeBSD and I can not find > any reliable resources of what FreeBSD-12 will be like. On the FreeBSD > website it is already noted as incomming, however I have no idea what > will be included in this release. Do you know of some? https://wiki.freebsd.org/WhatsNew/FreeBSD12 has a few bits. I have this list, from reviews and posts and things I stumbled over: - netflow netgraph ipfw add ngtee - ipfw setdscp Set specified DiffServ codepoint for an IPv4/IPv6 packet. analog: ipfw dscp - vimage will be included in the generic kernel https://svnweb.freebsd.org/base?view=revision&revision=324810 https://people.freebsd.org/~olivier/talks/2017_EuroBSDCon-Tuning_FreeBSD_for_routing_and_firewalling.pdf - ccp(4): experimental driver for AMD Crypto Co-Processor https://svnweb.freebsd.org/base?view=revision&revision=328150 - jedec_dimm: report asset info and temperatures for DDR3 and DDR4 DIMMs - ps aux | some stuff gets full width output - TCP blackbox recorder code https://wiki.freebsd.org/DevSummit/201706/Transport https://reviews.freebsd.org/D11085 - VMCI (Virtual Machine Communication Interface) driver https://reviews.freebsd.org/D14289 - sysvipc works in jails (I think this is already in some 11.x) https://www.skyforge.at/posts/a-note-in-sysvipc-and-jails-on-freebsd/ bisher: allow.sysvipc = 1 nun: sysvmsg, sysvsem and sysvshm sysvshm = ["disable"|"inherit"|"new"]; - ether random https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211984 - zpool temporary names https://github.com/openzfs/openzfs/pull/600 https://reviews.freebsd.org/D14972 - isoboot, see https://reviews.freebsd.org/D14914 - control CPU topology in bhyve https://reviews.freebsd.org/D9930 - netdump, dump core over the network https://lists.freebsd.org/pipermail/freebsd-arch/2018-April/018927.html https://reviews.freebsd.org/D15253 - socket-option SO_REUSEPORT_LB multiple processes can listen on the same port, for load balancing https://reviews.freebsd.org/D11003 - D15234: remove support for ixgb This driver was for an early and uncommon legacy PCI 10GbE for a single ASIC, Intel 82597EX. Intel quickly shifted to the long lived ixgbe family. - bhyve debug server for gdb, D15022 -- pi@opsec.eu +49 171 3101372 2 years to go ! From owner-freebsd-current@freebsd.org Thu May 10 07:45:54 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 982E6FB69B2 for ; Thu, 10 May 2018 07:45:54 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 27DFD73E33 for ; Thu, 10 May 2018 07:45:54 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id E0237FB69B0; Thu, 10 May 2018 07:45:53 +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 BD83FFB69AF for ; Thu, 10 May 2018 07:45:53 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-wr0-x22c.google.com (mail-wr0-x22c.google.com [IPv6:2a00:1450:400c:c0c::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 2374D73E32 for ; Thu, 10 May 2018 07:45:53 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: by mail-wr0-x22c.google.com with SMTP id h5-v6so988330wrm.4 for ; Thu, 10 May 2018 00:45:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:cc:from:subject:in-reply-to:references:content-transfer-encoding :date:message-id:mime-version; bh=Ic4N5krjOD8KGdXuRACutZvKOfMn6UqAbysEHHAKFW4=; b=ojBK0R1OqP0H379CFV+Nu0B+AHB6HRXM8znpoWM07exNJhJNUx34CYgmssS6XiUvNk zqF9hTaKdmw3gi7i1EKTNpMtWIVH5BuCEXhylnrgfxADFODlrNcyzu1MDKxRSRfoon/z n7eyByRaNpo85pT7ti8dXz7aCAkbfF7XXk9z6/XkM2o+V2fQYy/6n1iGNAdMD1JXnE7b mbGAje5X9G3E2VPmWBXc4AFOQROhviJGLwA9czTeQNtmsjt+EYtATYRCGMw8qnwXlUZ2 ZZZrTmvlNOJqF1H18Z2/RjdJ5shPQusHqTpMCAopBi+7Ks/jmsfzK4Llmmlip2tmO6xu EHqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:from:subject:in-reply-to:references :content-transfer-encoding:date:message-id:mime-version; bh=Ic4N5krjOD8KGdXuRACutZvKOfMn6UqAbysEHHAKFW4=; b=RQE24BDsjG2CLz4rj10y41oLYAPNt5Tbt+ryesR9ENPvbQKlgxNzPHz6AfnnPgIg8I 1zj6nwIrzbpImceXIVYaSUxJ05wg4aDkObP5dxEhJ44Ch4Vsg70xoHSXY5lxvobPmzrv 6dMQV3w4EfZwcLZ9HfYIqXQRwLAIqJ1ONy9ixRAjwv1xNzIapmtxZh6hNmUBiJ+V2Jw+ y9x0u4GsAjKNX0MpzHj6ygc18D+LIAL4z06sJH984Ts0XVGSvUC4+d0cqRn2Lt5X3VCL 3WtYhuY+QpFW4FEb8rPsCuwB/Mum4L/p9ydgRLrx+2Z9QnG/RlDFzDDTKVQEbGJ8ZPFD Jfuw== X-Gm-Message-State: ALKqPwfSGly+z7SqLjApIoxUG3sPnPnKJl396Q/4WLQb5vskepH+SUX4 sM7t1UiF5SVcsw1nrldWpf8= X-Google-Smtp-Source: AB8JxZoUUJnuQcn7dBKVb/vrIDVhMFli8C1Z5bQ9YBLNdNJgyebBJq4N7sHLwFl6AOlD68BDRV3zEQ== X-Received: by 2002:adf:8703:: with SMTP id a3-v6mr379873wra.178.1525938351427; Thu, 10 May 2018 00:45:51 -0700 (PDT) Received: from [127.0.0.1] ([2a02:8070:b87:5e00:86c7:eaff:fe31:83e1]) by smtp.gmail.com with ESMTPSA id j8-v6sm713801wra.58.2018.05.10.00.45.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 00:45:50 -0700 (PDT) X-Priority: 3 To: bsam@passap.ru Cc: current@freebsd.org From: Johannes Dieterich Subject: Re: pkg, drm-next-kmod and base packages In-Reply-To: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> References: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 Date: Thu, 10 May 2018 07:45:48 +0000 Message-ID: <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> MIME-Version: 1.0 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, 10 May 2018 07:45:54 -0000 SGkNCg0KT24gV2VkbmVzZGF5LCBNYXkgOSwgMjAxOCwgQm9yaXMgU2Ftb3JvZG92IHdyb3RlOg0K PiBIaSBBbGwsDQo+IA0KPiBJIHVzZSBzZWxmLWJ1aWx0IGJhc2UgcGFja2FnZXMuIEhvdyBjYW4g SSB0ZXN0L3VzZSBkcm0tbmV4dC1rbW9kPw0KPiBQYWNrYWdlcyBmb3Iga2VybmVsIGFuZCBkcm0t bmV4LWttb2QgYXJlIGluIGNvbmZsaWN0Og0KPiAtLS0tLQ0KPiDilbDihpIgc3VkbyBwa2cgaW5z dGFsbCBkcm0tbmV4dC1rbW9kLTQuMTEuZzIwMTgwMjI0DQo+IA0KPiBVcGRhdGluZyBGcmVlQlNE LWJhc2UgcmVwb3NpdG9yeSBjYXRhbG9ndWUuLi4NCj4gRnJlZUJTRC1iYXNlIHJlcG9zaXRvcnkg aXMgdXAgdG8gZGF0ZS4NCj4gVXBkYXRpbmcgRnJlZUJTRCByZXBvc2l0b3J5IGNhdGFsb2d1ZS4u Lg0KPiBGcmVlQlNEIHJlcG9zaXRvcnkgaXMgdXAgdG8gZGF0ZS4NCj4gVXBkYXRpbmcgcGFzc2Fw IHJlcG9zaXRvcnkgY2F0YWxvZ3VlLi4uDQo+IHBhc3NhcCByZXBvc2l0b3J5IGlzIHVwIHRvIGRh dGUuDQo+IEFsbCByZXBvc2l0b3JpZXMgYXJlIHVwIHRvIGRhdGUuDQo+IENoZWNraW5nIGludGVn cml0eS4uLiBkb25lICgxIGNvbmZsaWN0aW5nKQ0KPiAgIC0gZHJtLW5leHQta21vZC00LjExLmcy MDE4MDIyNCBbRnJlZUJTRF0gY29uZmxpY3RzIHdpdGgNCj4gRnJlZUJTRC1rZXJuZWwtcGtnNjR4 LTEyLjAuczIwMTgwNTA5MDQxNDU0IFtpbnN0YWxsZWRdIG9uDQo+IC9ib290L21vZHVsZXMvZHJt LmtvDQo+IENoZWNraW5nIGludGVncml0eS4uLiBkb25lICgwIGNvbmZsaWN0aW5nKQ0KPiBUaGUg Zm9sbG93aW5nIDMgcGFja2FnZShzKSB3aWxsIGJlIGFmZmVjdGVkIChvZiAwIGNoZWNrZWQpOg0K PiANCj4gSW5zdGFsbGVkIHBhY2thZ2VzIHRvIGJlIFJFTU9WRUQ6DQo+ICAgICAgICAgRnJlZUJT RC1rZXJuZWwtcGtnNjR4LTEyLjAuczIwMTgwNTA5MDQxNDU0DQo+IA0KPiBOZXcgcGFja2FnZXMg dG8gYmUgSU5TVEFMTEVEOg0KPiAgICAgICAgIGRybS1uZXh0LWttb2Q6IDQuMTEuZzIwMTgwMjI0 IFtGcmVlQlNEXQ0KPiAgICAgICAgIGdwdS1maXJtd2FyZS1rbW9kOiBnMjAxODAyMDZfMSBbRnJl ZUJTRF0NCj4gDQo+IE51bWJlciBvZiBwYWNrYWdlcyB0byBiZSByZW1vdmVkOiAxDQo+IE51bWJl ciBvZiBwYWNrYWdlcyB0byBiZSBpbnN0YWxsZWQ6IDINCj4gDQo+IFRoZSBvcGVyYXRpb24gd2ls bCBmcmVlIDkxIE1pQi4NCj4gDQo+IFByb2NlZWQgd2l0aCB0aGlzIGFjdGlvbj8gW3kvTl06DQo+ IC0tLS0tDQpTaW5jZSBJIGRvbid0IGhhdmUgYSBzeXN0ZW0gd2l0aCBwa2diYXNlIGNvbmZpZ3Vy ZWQsIGlzIHRoZXJlIGEgd2F5IHRvIGZpZ3VyZSBvdXQgd2hhdCBmaWxlcyBjb25mbGljdD8gSXQg c3VycHJpc2VzIG1lIHRoYXQgdGhlcmUgYXJlIGFueSBzaW5jZSB3ZSBkbyBub3Qgb3ZlcnJpZGUg YW55dGhpbmcgbm9ybWFsbHkgKHNvbWUga2VybmVsIG1vZHVsZXMgYXJlIGluZGVlZCBvdmVybGFw cGluZyBidXQgdGhleSBnZXQgaW5zdGFsbGVkIGluIGRpZmZlcmVudCBkaXJlY3RvcmllcykuDQoN ClRoYW5rcywNCg0Kam1k From owner-freebsd-current@freebsd.org Thu May 10 09:08:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4B549FB9BB5 for ; Thu, 10 May 2018 09:08:56 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from mout3.freenet.de (mout3.freenet.de [IPv6:2001:748:100:40::2:5]) (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 D35BB86744 for ; Thu, 10 May 2018 09:08:55 +0000 (UTC) (envelope-from freebsdnewbie@freenet.de) Received: from [195.4.92.141] (helo=mjail1.freenet.de) by mout3.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (port 25) (Exim 4.90_1 #2) id 1fGhZF-0008W5-1Z; Thu, 10 May 2018 11:08:53 +0200 Received: from [::1] (port=50590 helo=mjail1.freenet.de) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fGhZE-0006Kd-Tt; Thu, 10 May 2018 11:08:53 +0200 Received: from mx18.freenet.de ([195.4.92.28]:56824) by mjail1.freenet.de with esmtpa (ID freebsdnewbie@freenet.de) (Exim 4.90_1 #2) id 1fGhXA-0003i5-A9; Thu, 10 May 2018 11:06:44 +0200 Received: from p4fd9eac2.dip0.t-ipconnect.de ([79.217.234.194]:63241 helo=freebsd-t450.fritz.box) by mx18.freenet.de with esmtpsa (ID freebsdnewbie@freenet.de) (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (port 587) (Exim 4.90_1 #2) id 1fGhX9-0000GT-QH; Thu, 10 May 2018 11:06:44 +0200 Date: Thu, 10 May 2018 11:06:41 +0200 From: Manuel =?iso-8859-15?Q?St=FChn?= To: Niclas Zeising Cc: freebsd-current@freebsd.org Subject: Re: Regression Resume Lenovo T450 Message-ID: <20180510090641.GA47899@freebsd-t450.fritz.box> References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> <20180508200914.GA73930@freebsd-t450.fritz.box> <2d6880a1-8ad4-9003-8ebb-f4d2b68fe932@daemonic.se> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <2d6880a1-8ad4-9003-8ebb-f4d2b68fe932@daemonic.se> User-Agent: Mutt/1.9.5 (2018-04-13) X-Spamscore: -6.1 (------) X-Spamreport: Action: no action Symbol: NEURAL_HAM(-3.00) Symbol: TO_DN_SOME(0.00) Symbol: MIME_GOOD(-0.10) Symbol: TO_MATCH_ENVRCPT_ALL(0.00) Symbol: RCPT_COUNT_TWO(0.00) Symbol: RCVD_VIA_SMTP_AUTH(0.00) Symbol: FROM_HAS_DN(0.00) Symbol: RCVD_COUNT_ONE(0.00) Symbol: RCVD_TLS_ALL(0.00) Symbol: FROM_EQ_ENVFROM(0.00) Symbol: BAYES_HAM(-2.99) Symbol: ASN(0.00) Symbol: TAGGED_RCPT(0.00) Message-ID: 20180510090641.GA47899@freebsd-t450.fritz.box X-FN-Spambar: X-Originated-At: 79.217.234.194!63241 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, 10 May 2018 09:08:56 -0000 On Wed, May 09, 2018 at 10:06:19AM +0200, Niclas Zeising wrote: >On 05/08/18 22:09, Manuel Stühn wrote: > >> >> P.S. >> I'm useing drm-stable-kmod, drm-next-kmod did not work for me. > >What issues are you seeing with drm-next-kmod? I mixed my machines up. The one showing problems with drm-next was the T420: https://lists.freebsd.org/pipermail/freebsd-current/2018-March/068725.html On my T450 i've never installed drm-next, only drm-stable-kmod. -- Manuel From owner-freebsd-current@freebsd.org Thu May 10 07:47: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 53CC9FB6A20; Thu, 10 May 2018 07:47:03 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C53E874861; Thu, 10 May 2018 07:47:02 +0000 (UTC) (envelope-from 6yearold@gmail.com) Received: by mail-pg0-x229.google.com with SMTP id z4-v6so588735pgu.13; Thu, 10 May 2018 00:47:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=k/t7kNBOazgBE3FJBSinMgaoORlvKqtQygY335rcIRM=; b=tR32XjXb49tbaQbHwnsLUimw2kcnkWqEET9eRCaKbn82M32ayIcLVyGmTs9rLnCaS9 WhGY6H1ARPVLJi3SIcxevWiCIrYBQ7y/CDzSrtQbrCY/6Ik47evXdFSIbLiruEcSd/Uz krG7msq71D0XVTIY/IHHRKO8dk3o9ixbwbQJFoSxLuxWzLKzDa5rVRPh0n8/afp+RmH+ 5T31LZ9ir+Mdftw/WSphYJH3fjJXHyP2KQvO0ovXUvMno6alT8YYuf+ryPdwFgZ5xDOA Po1ZHQhf0NxGS9CQSONFnGqYNmfMDnSe5dLtjD9VQOEYoL4IOnK+rgjzy05dHpW4xUq8 xgwQ== 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=k/t7kNBOazgBE3FJBSinMgaoORlvKqtQygY335rcIRM=; b=NREZeXFEXIHLQpKQrjbc8A4zxoaxZMJL3iJ7td5Ttd1FTeMuqyzzeR9193USIraIoS zztSqF2AuMABN/PxJ7h42DOl/fUyFEVOzqeTGu4GNEGt5ixkqbhvzhVmzXECed3+JcR1 2mO/jiZb7Egy5NJfvbCSiTFGVwCIfG73ujrxjTcILwd9sveM3miYLOlMBmUEZq8ltJV3 vY8r3ZQwFvua457jdI9aUbpMLcbqta6RTeQNIC1qMHJn2bgf6n51RvC7wuB0qFjrGtRk Yqv+5DosF9vropc/5v5GnRWpuGeRNSkRsCk9Jr2Y0o3GtvNnYBTV9BRi/W7cVChFal2E XrlA== X-Gm-Message-State: ALKqPwc6fG/hStXLT+eo09UcRvyhHaLz2tcKh/4k9725K5e726vtbrMQ l4NXKy4Rl6qu2pKL5jVtpN8qBNwnA/QKmY6GfdXpQA== X-Google-Smtp-Source: AB8JxZq5UCu+fS3SwzcYxTMD5/vFnOuRyN50VTd+xdTQOcM8BqBrkp4Kn83wW5FY8w3lvFw6wsKMRm8L8/lzZAqNXkI= X-Received: by 2002:a63:b046:: with SMTP id z6-v6mr293063pgo.16.1525938421694; Thu, 10 May 2018 00:47:01 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.182.201 with HTTP; Thu, 10 May 2018 00:46:31 -0700 (PDT) In-Reply-To: <20180509234551.GA39526@troutmask.apl.washington.edu> References: <20180509234551.GA39526@troutmask.apl.washington.edu> From: Gleb Popov <6yearold@gmail.com> Date: Thu, 10 May 2018 10:46:31 +0300 Message-ID: Subject: Re: Runtime loader issue To: sgk@troutmask.apl.washington.edu Cc: FreeBSD Current , freebsd-hackers , FreeBSD ports list X-Mailman-Approved-At: Thu, 10 May 2018 10:39:57 +0000 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: Thu, 10 May 2018 07:47:03 -0000 On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < sgk@troutmask.apl.washington.edu> wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". See > > https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html > > The problem can be summarized by the following > > % gfortran7 -o z h.f90 > % ./z > /lib/libgcc_s.so.1: version GCC_4.8.0 required by \ > /usr/local/lib/gcc7/libgfortran.so.4 not found > > gfortran7 is installed from ports/lang/gcc7. This is not > a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. > > Specifically, there is a shared library name clash. > > % ldconfig -r | grep gcc_ > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 > > % ldd z > z: > libgfortran.so.4 => /usr/local/lib/gcc7/libgfortran.so.4 (0x200645000) > libm.so.5 => /lib/libm.so.5 (0x200a17000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x200a4b000) > libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200a63000) > libc.so.7 => /lib/libc.so.7 (0x200ca3000) > > So, the runtime loader finds 6 instead of 716, tries to link, > fails, and issues an error message. There are a number ways to > fix this issue. > > 1) By far, the best solution would be to stop hijacking the libgcc > name in libraries installed on FreeBSD that are not related to > actual GCC software. > > % ls -l /lib/libgcc* /usr/lib/libgcc* > (trimming lines) > /lib/libgcc_s.so.1 > /usr/lib/libgcc.a@ -> libcompiler_rt.a > /usr/lib/libgcc_eh.a > /usr/lib/libgcc_eh_p.a > /usr/lib/libgcc_p.a@ -> libcompiler_rt_p.a > /usr/lib/libgcc_s.so@ -> ../../lib/libgcc_s.so.1 > > Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm > aware that clang does not work on all archs and the ancient gcc > lives on. > > 2) Given the expected push back againt solution 1), this solution > proposes bumping the library version for /lib/libgcc_s.so.1 from > 1 to some larger value, say, 10. It is unlikely that GCC will > bump its shared library number anytime soon. GCC bumped it from > 0 to 1 some 16 years ago. > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 > > This solution, however, papers over the general problem with > name clashes. > > 3) This solution is to actually fix the runtime loader. If an error > occurs with loading a shared library, then iterate over the entries > in the hints file to check to see if another hint would satisfy > the linking. Here, instead of issuing the above error, the loader > would find entry 716, and load the correct libgcc_s.so.1. > > Admittedly, I haven't looked to see how difficult this solution > would be. > > 4) Bump the shared library number of the individual ports. As a proof > of concept, I've done this with ports/lang/gcc6. > > % cat /usr/ports/lang/gcc6/files/patch-t-slibgcc > --- libgcc/config/t-slibgcc.orig 2018-05-08 12:47:42.334495000 -0700 > +++ libgcc/config/t-slibgcc 2018-05-08 12:45:26.872312000 -0700 > @@ -20,7 +20,7 @@ > > SHLIB_EXT = .so > SHLIB_SOLINK = @shlib_base_name@.so > -SHLIB_SOVERSION = 1 > +SHLIB_SOVERSION = 2 > SHLIB_SONAME = @shlib_base_name@.so.$(SHLIB_SOVERSION) > SHLIB_MAP = @shlib_map_file@ > SHLIB_OBJS = @shlib_objs@ > > % ldconfig -r | grep gcc_ > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 > 766:-lgcc_s.2 => /usr/local/lib/gcc6/libgcc_s.so.2 > > % gfortran6 -o z h.f90 > % ./z > hello > % ldd z > z: > libgfortran.so.3 => /usr/local/lib/gcc6/libgfortran.so.3 (0x200645000) > libm.so.5 => /lib/libm.so.5 (0x20096c000) > libgcc_s.so.2 => /usr/local/lib/gcc6/libgcc_s.so.2 (0x2009a0000) > libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) > libc.so.7 => /lib/libc.so.7 (0x200df7000) > > This works for this particular name conflict. Hopefully, FreeBSD > never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, > however, introduces an incompatibility with what is actually distributed > by GCC. > > Finally, can people stop referring to the above error as > "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. > Our libgcc also lacks some functionality compared to the original one: https://reviews.freebsd.org/D11482 > -- > Steve > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-current@freebsd.org Thu May 10 14: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 938DDFCB0A2; Thu, 10 May 2018 14:25:01 +0000 (UTC) (envelope-from db@db.net) Received: from artemis.db.net (artemis.db.net [45.32.229.41]) by mx1.freebsd.org (Postfix) with ESMTP id 334468A077; Thu, 10 May 2018 14:25:00 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (localhost [127.0.0.1]) by artemis.db.net (Postfix) with ESMTP id 7DB3D1023A; Thu, 10 May 2018 14:24:53 +0000 (UTC) Received: by night.db.net (Postfix, from userid 1000) id C788E39813; Thu, 10 May 2018 10:24:52 -0400 (EDT) Date: Thu, 10 May 2018 10:24:52 -0400 From: Diane Bruce To: Gleb Popov <6yearold@gmail.com> Cc: sgk@troutmask.apl.washington.edu, freebsd-hackers , FreeBSD Current , FreeBSD ports list Subject: Re: Runtime loader issue Message-ID: <20180510142452.GA69005@night.db.net> References: <20180509234551.GA39526@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) 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, 10 May 2018 14:25:01 -0000 On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > > > In review PR 228007, it came to my attention some individuals are > > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > > issue". See Indeed. I've tried to make it clear it is a name conflict with libgcc in my own bug reports on the subject. > > > > https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html > > > > The problem can be summarized by the following ... > > gfortran7 is installed from ports/lang/gcc7. This is not > > a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. > > > > Specifically, there is a shared library name clash. > > > > % ldconfig -r | grep gcc_ > > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 Yep. See https://wiki.freebsd.org/libgcc%20problem > > > > So, the runtime loader finds 6 instead of 716, tries to link, > > fails, and issues an error message. There are a number ways to > > fix this issue. > > > > 1) By far, the best solution would be to stop hijacking the libgcc > > name in libraries installed on FreeBSD that are not related to > > actual GCC software. Agreed, however this has the side effect of meaning conflicts with libraries between clang and gcc libs. Notably gfortran and flang use different conventions for I/O :( See http://people.FreeeBSD.org/~db/fortran_libs.txt > > > > Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm > > aware that clang does not work on all archs and the ancient gcc > > lives on. > > I've argued for this as well and frankly I still think it is the best solution all around. > > 2) Given the expected push back againt solution 1), this solution > > proposes bumping the library version for /lib/libgcc_s.so.1 from > > 1 to some larger value, say, 10. It is unlikely that GCC will > > bump its shared library number anytime soon. GCC bumped it from > > 0 to 1 some 16 years ago. > > > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 > > > > This solution, however, papers over the general problem with > > name clashes. Yep. I know work is slowly being done to modernise our libgcc already but the toolchain folks are busy... > > > > 3) This solution is to actually fix the runtime loader. If an error > > occurs with loading a shared library, then iterate over the entries > > in the hints file to check to see if another hint would satisfy > > the linking. Here, instead of issuing the above error, the loader > > would find entry 716, and load the correct libgcc_s.so.1. This breaks if the bad libgcc is already linked. We'd have to rip out the original bindings at run time, then re-bind to a new libgcc. I looked at the rtld code months ago. Nasty and silly. > > > > Admittedly, I haven't looked to see how difficult this solution > > would be. Very ;) > > > > 4) Bump the shared library number of the individual ports. As a proof > > of concept, I've done this with ports/lang/gcc6. > > ... > > > > Finally, can people stop referring to the above error as > > "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. Yes, please. I tracked it down to libgcc months ago, made my findings generally available and yet people are still calling it a libgfortran problem. > > > > Our libgcc also lacks some functionality compared to the original one: > https://reviews.freebsd.org/D11482 Yes. Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@freebsd.org Thu May 10 15:15: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 727C6FCD0C6; Thu, 10 May 2018 15:15:33 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC3A6EC9A; Thu, 10 May 2018 15:15:32 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4AFFOJF043970 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 May 2018 08:15:24 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4AFFMHh043969; Thu, 10 May 2018 08:15:22 -0700 (PDT) (envelope-from sgk) Date: Thu, 10 May 2018 08:15:22 -0700 From: Steve Kargl To: Diane Bruce Cc: Gleb Popov <6yearold@gmail.com>, freebsd-hackers , FreeBSD Current , FreeBSD ports list Subject: Re: Runtime loader issue Message-ID: <20180510151522.GA43677@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180509234551.GA39526@troutmask.apl.washington.edu> <20180510142452.GA69005@night.db.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180510142452.GA69005@night.db.net> User-Agent: Mutt/1.9.2 (2017-12-15) 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, 10 May 2018 15:15:33 -0000 On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote: > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > > sgk@troutmask.apl.washington.edu> wrote: > > > > > In review PR 228007, it came to my attention some individuals are > > > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > > > issue". See > > Indeed. I've tried to make it clear it is a name conflict with libgcc > in my own bug reports on the subject. > > > > > > > https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html > > > > > > The problem can be summarized by the following > ... > > > gfortran7 is installed from ports/lang/gcc7. This is not > > > a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. > > > > > > Specifically, there is a shared library name clash. > > > > > > % ldconfig -r | grep gcc_ > > > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > > > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 > > Yep. > See https://wiki.freebsd.org/libgcc%20problem > Interesting page. I was aware that in the past you tried working out a solution to the problem. I did not realize you docoumented the issue. A few corrections to your wiki page. 1) The correct spelling of the name of the language is Fortran (with a capital F). It has been the official standard spelling since Fortran 90. 2) You have "... to always support quad math (*8) and ...". Quad precision in gfortran is REAL(16) (the REAL*16 notation is nonstandard). 3) "subsitute" is normally spelled with an extra 't'. :-) > > > So, the runtime loader finds 6 instead of 716, tries to link, > > > fails, and issues an error message. There are a number ways to > > > fix this issue. > > > > > > 1) By far, the best solution would be to stop hijacking the libgcc > > > name in libraries installed on FreeBSD that are not related to > > > actual GCC software. > > Agreed, however this has the side effect of meaning conflicts with libraries > between clang and gcc libs. Notably gfortran and flang use different > conventions for I/O :( > > See http://people.FreeeBSD.org/~db/fortran_libs.txt > Page doesn't appear to exist? If I go to https://people.freebsd.org/homepage.html you're not listed. > > > Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm > > > aware that clang does not work on all archs and the ancient gcc > > > lives on. > > > > > I've argued for this as well and frankly I still think it is the best > solution all around. > > > > 2) Given the expected push back againt solution 1), this solution > > > proposes bumping the library version for /lib/libgcc_s.so.1 from > > > 1 to some larger value, say, 10. It is unlikely that GCC will > > > bump its shared library number anytime soon. GCC bumped it from > > > 0 to 1 some 16 years ago. > > > > > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 > > > > > > This solution, however, papers over the general problem with > > > name clashes. > > Yep. I know work is slowly being done to modernise our libgcc already > but the toolchain folks are busy... > > > > > > > 3) This solution is to actually fix the runtime loader. If an error > > > occurs with loading a shared library, then iterate over the entries > > > in the hints file to check to see if another hint would satisfy > > > the linking. Here, instead of issuing the above error, the loader > > > would find entry 716, and load the correct libgcc_s.so.1. > > This breaks if the bad libgcc is already linked. We'd have to rip > out the original bindings at run time, then re-bind to a new libgcc. > I looked at the rtld code months ago. Nasty and silly. > > > > > > > Admittedly, I haven't looked to see how difficult this solution > > > would be. > > Very ;) Just started reading the source code. Don't scare the unwary. :-) -- Steve From owner-freebsd-current@freebsd.org Thu May 10 15:30:40 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBA76FCDAF9 for ; Thu, 10 May 2018 15:30:39 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8147C74771 for ; Thu, 10 May 2018 15:30:39 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 426C7FCDAF7; Thu, 10 May 2018 15:30:39 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 07B1FFCDAF5 for ; Thu, 10 May 2018 15:30:39 +0000 (UTC) (envelope-from theron.tarigo@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 968537476B for ; Thu, 10 May 2018 15:30:38 +0000 (UTC) (envelope-from theron.tarigo@gmail.com) Received: by mail-qt0-x233.google.com with SMTP id q6-v6so3078936qtn.3 for ; Thu, 10 May 2018 08:30:38 -0700 (PDT) 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-transfer-encoding:content-language; bh=qqewOJLxQHzozP675nqdY6EmI7cdKRIf/kX2BzaRFBo=; b=d3cJiBEfbQyEX0pxsBhW3d9St9PMDsPd+n/EZwu1SwevuSlwgnoOxpVPTX81pFjtgx e2UmmsmlhJ6xwwnvYzwVgbI4HE1N+sw+gp6u9DhuE4+H73LiyNtq1xL/s+xsjGEwZxXl vsjMN/MnzesYrkfebixgj9kX6z+SkDOdZCNAaLyT08F1BDokH9iRA4Azzw9O7YZZyxox In56jgSjtO/dEX99LwjSZSULanHke2M8HMRzIMSZPur9y6HB3n1/iKlavYrFkh/ugvBK 9rQ+1pJzTPBGen7Y2xKbUG/t8GgNzJ2XaIXp9fQGsh90XxjXz0istuAK1aehWAWn2yAr 3V4g== 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-transfer-encoding :content-language; bh=qqewOJLxQHzozP675nqdY6EmI7cdKRIf/kX2BzaRFBo=; b=ow6Cq6lzgEvpqkzYnzO1wLUswUA4zzZMrzyoChHwwFuPjbTZJIdh78iQDqDLUbWHmv zJZB3ZCYZUtnbrpoLv925yZjdR63X+a6JjOUVvh2iHGGOdmIbsFpophXsaQ74o0P5Uds Lu3Se+PJTA3MUn4820BZcO/aO0gi3C+X5Xa4LJKzIGb1c6MBMN4q9BdkGYPg9/fz1/x7 2bwQFo3Q6ATYDvDWABka7qD/CeHE5YPHnBOYwkt/o/pfz66tW+8c14Koccsvy8Wr+VPI +RCUsBipxsxqYFrn5vv4lN2SlAX5MIF2tNsKxA6pUa/vq8foXiLH8G86Zew5fvgPnhb0 8cOA== X-Gm-Message-State: ALKqPwcbGADOuZZya5NKOl9VVPK9bnaCvuukssBx2uRts5mGRe+L4Qea s9YHu2L/UTaFQucMvYjnwPuWKX2P X-Google-Smtp-Source: AB8JxZrWoremHc1p3iOjxzEk/hxHpEBL4H6n0BxSSpaGMoY4gngpIhn4guS57/hewsctg+zc4qRAYw== X-Received: by 2002:aed:3aa4:: with SMTP id o33-v6mr1867864qte.186.1525966237979; Thu, 10 May 2018 08:30:37 -0700 (PDT) Received: from [155.41.107.219] (dhcp-wifi-8021x-155-41-107-219.bu.edu. [155.41.107.219]) by smtp.gmail.com with ESMTPSA id s16-v6sm752328qks.78.2018.05.10.08.30.37 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 08:30:37 -0700 (PDT) Sender: Theron Tarigo Subject: Re: pkg, drm-next-kmod and base packages To: Johannes Dieterich , bsam@passap.ru Cc: current@freebsd.org References: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> From: Theron Message-ID: Date: Thu, 10 May 2018 11:30:37 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> 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: Thu, 10 May 2018 15:30:40 -0000 On 05/10/18 03:45, Johannes Dieterich wrote: > Hi > > On Wednesday, May 9, 2018, Boris Samorodov wrote: >> Hi All, >> >> I use self-built base packages. How can I test/use drm-next-kmod? >> Packages for kernel and drm-nex-kmod are in conflict: >> ----- >> Checking integrity... done (1 conflicting) >> - drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with >> FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on >> /boot/modules/drm.ko >> Checking integrity... done (0 conflicting) >> ----- > Since I don't have a system with pkgbase configured, is there a way to figure out what files conflict? The pkg output indicates that /boot/modules/drm.ko is the conflicting file. > It surprises me that there are any since we do not override anything normally (some kernel modules are indeed overlapping but they get installed in different directories). On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in /boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/.  Any kernel modules from base being placed outside of /boot/kernel is not what I would expect for a non-pkgbase system; is there a reason pkgbase should not follow this rule? Theron From owner-freebsd-current@freebsd.org Thu May 10 16: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 99B98FCEC77 for ; Thu, 10 May 2018 16:05:59 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 252157ABDE for ; Thu, 10 May 2018 16:05:59 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id DD857FCEC76; Thu, 10 May 2018 16:05:58 +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 B9109FCEC75 for ; Thu, 10 May 2018 16:05:58 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: from mail-lf0-x234.google.com (mail-lf0-x234.google.com [IPv6:2a00:1450:4010:c07::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 35BA37ABB8 for ; Thu, 10 May 2018 16:05:58 +0000 (UTC) (envelope-from andrnils@gmail.com) Received: by mail-lf0-x234.google.com with SMTP id o123-v6so3709782lfe.8 for ; Thu, 10 May 2018 09:05:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/zxFqV/m5PJ5MHQB2fQ8e1STD3+0L8FfoARFF6srS+M=; b=ltAZuwUU3ntwEEnI01wFUARGb9RchD3A28DeSZTuWmZB473mbH45VP+bKozzl6Ud0P h39W9BHS0x2cUTNmAu4bPCYTYBbaJ/xQCyQb4xpN3DcUGsw3M9+0i1tSRbWERMOJWp+K pK2yNBjfmciJ2XMcQnVuQWmOK4jAdQpew36TmCyga8B3VpBHsv86Qvjz8aYAAHg9X9Iv oZQSZCcTWQln7L+pvZTaDTX35xhShET551Dy3oBeTsregLTDTa3HSBd4t1qR4dk+r1+0 y8do8vgVjykAxAh9n3GobbHoDPuc7S40jFe2L9ao+7iTZoIb34zUaCwf6SnbKw+gF1Iv JgSQ== 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=/zxFqV/m5PJ5MHQB2fQ8e1STD3+0L8FfoARFF6srS+M=; b=nim6Nybj8QujOZfyfmSHZvEvZucw9PweZGmt0slcazwLAL+WO7tpXcGCqBXOFMsvti VlBwkfp2617V+7ChJP7hsoSLAL/rcG3LUDGgyl7qXN3CyONOljT9oM2RbyaGCCazf0ro k8y/iBwPsLu65haHm4y/rImq7fbP7aGfSNR5yD77AwYm+FDDl/Ta/Bj9hGEziJmWwYbT ZqOzeOJYml3PkyVOKWYyuZQU75xQoKOS/Sc/gWkA8+A/L9tb3no6YB90Ix80M5h2ZmYN 2LSGgQFYy4K8BEgAoX/qHovWsMST+IWer5kUIFDzsWfLlFmaag7jAv4CJlYrJ2XGZaH4 sg8w== X-Gm-Message-State: ALKqPwdSEIZZNWBFdpnmgb1ujhTpRaLLhuWfdtzfua4ROpOXPESEA6fV QwHTQ6ersZXwt/kLZ9rxaP+18zXvDlbdZb9Cspo= X-Google-Smtp-Source: AB8JxZqtaiiIRiGgU4jqspr+nrs+NW2hV2BSKmJbD/fYCwYfFflSp2X/kf4JDn+89e97qOSR6tTaYXP50D0ApKFR7UY= X-Received: by 2002:a2e:8518:: with SMTP id j24-v6mr1671635lji.12.1525968356667; Thu, 10 May 2018 09:05:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.131.76 with HTTP; Thu, 10 May 2018 09:05:56 -0700 (PDT) In-Reply-To: References: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> From: Andreas Nilsson Date: Thu, 10 May 2018 18:05:56 +0200 Message-ID: Subject: Re: pkg, drm-next-kmod and base packages To: Theron Cc: Johannes Dieterich , bsam@passap.ru, 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: Thu, 10 May 2018 16:05:59 -0000 On Thu, May 10, 2018 at 5:30 PM, Theron wrote: > On 05/10/18 03:45, Johannes Dieterich wrote: > >> Hi >> >> On Wednesday, May 9, 2018, Boris Samorodov wrote: >> >>> Hi All, >>> >>> I use self-built base packages. How can I test/use drm-next-kmod? >>> Packages for kernel and drm-nex-kmod are in conflict: >>> ----- >>> Checking integrity... done (1 conflicting) >>> - drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with >>> FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on >>> /boot/modules/drm.ko >>> Checking integrity... done (0 conflicting) >>> ----- >>> >> Since I don't have a system with pkgbase configured, is there a way to >> figure out what files conflict? >> > The pkg output indicates that /boot/modules/drm.ko is the conflicting file. > >> It surprises me that there are any since we do not override anything >> normally (some kernel modules are indeed overlapping but they get installed >> in different directories). >> > On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in > /boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/. Any > kernel modules from base being placed outside of /boot/kernel is not what I > would expect for a non-pkgbase system; is there a reason pkgbase should not > follow this rule? > > Theron > > I recently converted my system to pkgbase, but I have no such package as FreeBSD-kernel-pkg64x. How and from where did you get the sources? I seem to remember that the git repo FreeBSDDesktop /freebsd-base-graphics shipped the module in /boot/modules. If you are using that git repo, you do not need the port. Best regards Andreas From owner-freebsd-current@freebsd.org Thu May 10 16:23: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 0FF5FFCF2E6; Thu, 10 May 2018 16:23:05 +0000 (UTC) (envelope-from tijl@freebsd.org) Received: from mailrelay118.isp.belgacom.be (mailrelay118.isp.belgacom.be [195.238.20.145]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "relay.skynet.be", Issuer "GlobalSign Organization Validation CA - SHA256 - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 545928056B; Thu, 10 May 2018 16:23:03 +0000 (UTC) (envelope-from tijl@freebsd.org) X-Belgacom-Dynamic: yes IronPort-PHdr: =?us-ascii?q?9a23=3AMGvo9BRN2zWJRwDIA2poOab9VNpsv+yvbD5Q0YIu?= =?us-ascii?q?jvd0So/mwa6zYhCN2/xhgRfzUJnB7Loc0qyK6/umATRIyK3CmUhKSIZLWR4BhJ?= =?us-ascii?q?detC0bK+nBN3fGKuX3ZTcxBsVIWQwt1Xi6NU9IBJS2PAWK8TW94jEIBxrwKxd+?= =?us-ascii?q?KPjrFY7OlcS30P2594HObwlSizexfb1/IA+qoQnNq8IbnZZsJqEtxxXTv3BGYf?= =?us-ascii?q?5WxWRmJVKSmxbz+MK994N9/ipTpvws6ddOXb31cKokQ7NYCi8mM30u683wqRbD?= =?us-ascii?q?VwqP6WACXWgQjxFFHhLK7BD+Xpf2ryv6qu9w0zSUMMHqUbw5Xymp4qF2QxHqlS?= =?us-ascii?q?gHLSY0/m/XhMJukaxVoxCupxJwzIHIe4yVMeZycr/HcN8GWWZNQMBcXDFBDIOm?= =?us-ascii?q?aIsPCvIMM/hZr4n/o1sFsAWzBQ6rBOP01DBIg2X53ash0+88FgzGwA0gH9AKsH?= =?us-ascii?q?nPrNv1LrkdXv6owafVwzvPdfRW2S3y6IXRdB0qvP+CXbV1ccXLyEkvERvIjluK?= =?us-ascii?q?qYP7ITyazf8NvHWB4+pnT+KvhHYrqw5trTezx8ogkJXGiZgJylzc+iV5xps1Kc?= =?us-ascii?q?e/SE5hbt6pFoZbuSKCN4ZuQc4uXntktDg1x7Ebo5K3YjQGxIo9yxLCa/GKfY6F?= =?us-ascii?q?6Q/5WumLOzd3nndldaq6hxa17Eev1PXxVtKx0FZWtipFlcTMtmwV2xzT9MeHTv?= =?us-ascii?q?x981+i2TmV0wDT6+RELl4ularcMZIh3r8wlpgXsUjZAiD2n0L2jLSIeUUh4Oeo?= =?us-ascii?q?7f/nbq/hpp+GOI94kgD+MqIwlcyjGek1MRUCU3KF9emzybHv51P1TKlUgvEsj6?= =?us-ascii?q?XUsJ7XKdwepqGjAg9V1ogj6wy4DzejyNkYgXgHLFBBeB+cgYjpIU/BL+7jAvek?= =?us-ascii?q?nlugijBrx+rJPrH5GJXCMmDDkKv9fbZ680NcxhAzws5B6J1PEbEOPev/Wlf2tN?= =?us-ascii?q?zCEh85KBe5w+j9CNpjyIwRQnmPDbKDPKPVq1+I6folI/OQa48NpDb9N/8l6ubg?= =?us-ascii?q?jX8jh1ASY7Km3YAKZ3yhHvRpOVmWYXnyjdcbCmcHpQQ+TPb0h1KcSjFTfGu9U7?= =?us-ascii?q?g75jEhB4KsFZ3DSZy1gLydwCe7GYVbZm5cCl+SD3jnbJ6EVOoVZC2OP89hiCYE?= =?us-ascii?q?WqanS489zhyuuhX6xKR5IeXP4S0XqIjv1N9v5+3cxlkO8mlPE8mD3imuRnt7mi?= =?us-ascii?q?tcXDA19LxlplFhz16Y0u5xm/geCtVI5/JPXRs9M9jRw/EsWP7oXQeUQtaLTB6N?= =?us-ascii?q?RdK9DDQ4SMl5l8MPYUJVNc+vgzr482ytGbBDxO/DP4A97q+Jhyu5HM160XuTjK?= =?us-ascii?q?Q=3D?= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2BgBQBscfRa/5nK8VFcDg4BAQEEAQEKA?= =?us-ascii?q?QGDQ1MOeyiLdF6MDgEBgXgxAV2TM4F4Iw2BUoJ1AoJ/IjQYAQIBAQEBAQECAWs?= =?us-ascii?q?cDII1IoJSAQEEASYvIxALDgoJJQ8ZER4GExuDCoIDC60tM4hDgjkPijiEGoMRA?= =?us-ascii?q?wEBF4caAoU7hlmEb4cqCYNEgiOCUoI6K4MmaYwHiU6ILRw4gVJNMAhIEYIlCVa?= =?us-ascii?q?KMYUEPD0wAY1xKoIcAQE?= X-IPAS-Result: =?us-ascii?q?A2BgBQBscfRa/5nK8VFcDg4BAQEEAQEKAQGDQ1MOeyiLdF6?= =?us-ascii?q?MDgEBgXgxAV2TM4F4Iw2BUoJ1AoJ/IjQYAQIBAQEBAQECAWscDII1IoJSAQEEA?= =?us-ascii?q?SYvIxALDgoJJQ8ZER4GExuDCoIDC60tM4hDgjkPijiEGoMRAwEBF4caAoU7hlm?= =?us-ascii?q?Eb4cqCYNEgiOCUoI6K4MmaYwHiU6ILRw4gVJNMAhIEYIlCVaKMYUEPD0wAY1xK?= =?us-ascii?q?oIcAQE?= Received: from 153.202-241-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.241.202.153]) by relay.skynet.be with ESMTP; 10 May 2018 18:21:53 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.15.2/8.15.2) with ESMTP id w4AGLpjR078852; Thu, 10 May 2018 18:21:53 +0200 (CEST) (envelope-from tijl@FreeBSD.org) Date: Thu, 10 May 2018 18:21:51 +0200 From: Tijl Coosemans To: Steve Kargl Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Runtime loader issue Message-ID: <20180510182151.409b7fb8@kalimero.tijl.coosemans.org> In-Reply-To: <20180509234551.GA39526@troutmask.apl.washington.edu> References: <20180509234551.GA39526@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="MP_/nD2m3FmfImDp2u+ur0Mr4sg" 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, 10 May 2018 16:23:05 -0000 --MP_/nD2m3FmfImDp2u+ur0Mr4sg Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". See > > https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html > > The problem can be summarized by the following > > % gfortran7 -o z h.f90 > % ./z > /lib/libgcc_s.so.1: version GCC_4.8.0 required by \ > /usr/local/lib/gcc7/libgfortran.so.4 not found > > gfortran7 is installed from ports/lang/gcc7. This is not > a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. > > Specifically, there is a shared library name clash. > > % ldconfig -r | grep gcc_ > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 > > % ldd z > z: > libgfortran.so.4 => /usr/local/lib/gcc7/libgfortran.so.4 (0x200645000) > libm.so.5 => /lib/libm.so.5 (0x200a17000) > libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x200a4b000) > libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200a63000) > libc.so.7 => /lib/libc.so.7 (0x200ca3000) > > So, the runtime loader finds 6 instead of 716, tries to link, > fails, and issues an error message. There are a number ways to > fix this issue. > > 1) By far, the best solution would be to stop hijacking the libgcc > name in libraries installed on FreeBSD that are not related to > actual GCC software. > > % ls -l /lib/libgcc* /usr/lib/libgcc* > (trimming lines) > /lib/libgcc_s.so.1 > /usr/lib/libgcc.a@ -> libcompiler_rt.a > /usr/lib/libgcc_eh.a > /usr/lib/libgcc_eh_p.a > /usr/lib/libgcc_p.a@ -> libcompiler_rt_p.a > /usr/lib/libgcc_s.so@ -> ../../lib/libgcc_s.so.1 > > Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm > aware that clang does not work on all archs and the ancient gcc > lives on. > > 2) Given the expected push back againt solution 1), this solution > proposes bumping the library version for /lib/libgcc_s.so.1 from > 1 to some larger value, say, 10. It is unlikely that GCC will > bump its shared library number anytime soon. GCC bumped it from > 0 to 1 some 16 years ago. > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 > > This solution, however, papers over the general problem with > name clashes. > > 3) This solution is to actually fix the runtime loader. If an error > occurs with loading a shared library, then iterate over the entries > in the hints file to check to see if another hint would satisfy > the linking. Here, instead of issuing the above error, the loader > would find entry 716, and load the correct libgcc_s.so.1. > > Admittedly, I haven't looked to see how difficult this solution > would be. > > 4) Bump the shared library number of the individual ports. As a proof > of concept, I've done this with ports/lang/gcc6. > > % cat /usr/ports/lang/gcc6/files/patch-t-slibgcc > --- libgcc/config/t-slibgcc.orig 2018-05-08 12:47:42.334495000 -0700 > +++ libgcc/config/t-slibgcc 2018-05-08 12:45:26.872312000 -0700 > @@ -20,7 +20,7 @@ > > SHLIB_EXT = .so > SHLIB_SOLINK = @shlib_base_name@.so > -SHLIB_SOVERSION = 1 > +SHLIB_SOVERSION = 2 > SHLIB_SONAME = @shlib_base_name@.so.$(SHLIB_SOVERSION) > SHLIB_MAP = @shlib_map_file@ > SHLIB_OBJS = @shlib_objs@ > > % ldconfig -r | grep gcc_ > 6:-lgcc_s.1 => /lib/libgcc_s.so.1 > 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 > 766:-lgcc_s.2 => /usr/local/lib/gcc6/libgcc_s.so.2 > > % gfortran6 -o z h.f90 > % ./z > hello > % ldd z > z: > libgfortran.so.3 => /usr/local/lib/gcc6/libgfortran.so.3 (0x200645000) > libm.so.5 => /lib/libm.so.5 (0x20096c000) > libgcc_s.so.2 => /usr/local/lib/gcc6/libgcc_s.so.2 (0x2009a0000) > libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) > libc.so.7 => /lib/libc.so.7 (0x200df7000) > > This works for this particular name conflict. Hopefully, FreeBSD > never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, > however, introduces an incompatibility with what is actually distributed > by GCC. > > Finally, can people stop referring to the above error as > "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. libgcc_s.so implements the _Unwind_* API to handle stack unwinding. This code is shared between all compilers and languages because the stack can contain frames from different compilers and languages. So, you cannot change the name or version of the library. I've been testing the attached patch in combination with the ports tree patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228046. The patch makes three changes to /etc/rc.d/ldconfig: 1) Use 'sort -r' so /usr/local/lib/gcc7 appears before /usr/local/lib/gcc6. 2) Move hardcoded paths like /lib and /usr/lib to /etc/defaults/rc.conf so the order relative to other paths can be configured. 3) Change the order of ldconfig_local_dirs and ldconfig_paths so /lib and /usr/lib appear last. This brings rc.d/ldconfig in line with compilers and rtld(1) which also search /lib and /usr/lib last. --MP_/nD2m3FmfImDp2u+ur0Mr4sg Content-Type: text/x-patch Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=ldconfig.patch Index: etc/defaults/rc.conf =================================================================== --- etc/defaults/rc.conf (revision 333461) +++ etc/defaults/rc.conf (working copy) @@ -629,14 +629,14 @@ linux_enable="NO" # Linux binary compatibility loaded clear_tmp_enable="NO" # Clear /tmp at startup. clear_tmp_X="YES" # Clear and recreate X11-related directories in /tmp ldconfig_insecure="NO" # Set to YES to disable ldconfig security checks -ldconfig_paths="/usr/lib/compat /usr/local/lib /usr/local/lib/compat/pkg" +ldconfig_paths="/usr/local/lib /usr/local/lib/compat/pkg /usr/lib /usr/lib/compat /lib" # shared library search paths ldconfig32_paths="/usr/lib32 /usr/lib32/compat" # 32-bit compatibility shared library search paths -ldconfigsoft_paths="/usr/libsoft /usr/libsoft/compat /usr/local/libsoft" +ldconfigsoft_paths="/usr/local/libsoft /usr/libsoft /usr/libsoft/compat" # soft float compatibility shared library search paths # Note: temporarily with extra stuff for transition -ldconfig_paths_aout="/usr/lib/compat/aout /usr/local/lib/aout" +ldconfig_paths_aout="/usr/local/lib/aout /usr/lib/aout /usr/lib/compat/aout" # a.out shared library search paths ldconfig_local_dirs="/usr/local/libdata/ldconfig" # Local directories with ldconfig configuration files. Index: etc/rc.d/ldconfig =================================================================== --- etc/rc.d/ldconfig (revision 333461) +++ etc/rc.d/ldconfig (working copy) @@ -17,22 +17,23 @@ stop_cmd=":" ldconfig_start() { - local _files _ins + local _files _ins _paths _LDC _ins= ldconfig=${ldconfig_command} checkyesno ldconfig_insecure && _ins="-i" if [ -x "${ldconfig_command}" ]; then - _LDC="/lib /usr/lib" + _paths="" for i in ${ldconfig_local_dirs}; do if [ -d "${i}" ]; then _files=`find ${i} -type f` if [ -n "${_files}" ]; then - ldconfig_paths="${ldconfig_paths} `cat ${_files} | sort -u`" + _paths="${_paths} `cat ${_files} | sort -ru`" fi fi done - for i in ${ldconfig_paths} /etc/ld-elf.so.conf; do + _LDC="" + for i in ${_paths} ${ldconfig_paths} /etc/ld-elf.so.conf; do if [ -r "${i}" ]; then _LDC="${_LDC} ${i}" fi @@ -42,16 +43,17 @@ ldconfig_start() case `sysctl -n hw.machine_arch` in amd64|powerpc64) + _paths="" for i in ${ldconfig_local32_dirs}; do if [ -d "${i}" ]; then _files=`find ${i} -type f` if [ -n "${_files}" ]; then - ldconfig32_paths="${ldconfig32_paths} `cat ${_files} | sort -u`" + _paths="${_paths} `cat ${_files} | sort -ru`" fi fi done _LDC="" - for i in ${ldconfig32_paths}; do + for i in ${_paths} ${ldconfig32_paths}; do if [ -r "${i}" ]; then _LDC="${_LDC} ${i}" fi @@ -64,16 +66,17 @@ ldconfig_start() case `sysctl -n hw.machine_arch` in armv[67]) + _paths="" for i in ${ldconfig_localsoft_dirs}; do if [ -d "${i}" ]; then _files=`find ${i} -type f` if [ -n "${_files}" ]; then - ldconfigsoft_paths="${ldconfigsoft_paths} `cat ${_files} | sort -u`" + _paths="${_paths} `cat ${_files} | sort -ru`" fi fi done _LDC="" - for i in ${ldconfigsoft_paths}; do + for i in ${_paths} ${ldconfigsoft_paths}; do if [ -r "${i}" ]; then _LDC="${_LDC} ${i}" fi @@ -87,10 +90,8 @@ ldconfig_start() # Legacy aout support for i386 only case `sysctl -n hw.machine_arch` in i386) - # Default the a.out ldconfig path. - : ${ldconfig_paths_aout=${ldconfig_paths}} _LDC="" - for i in /usr/lib/aout ${ldconfig_paths_aout} /etc/ld.so.conf; do + for i in ${ldconfig_paths_aout} /etc/ld.so.conf; do if [ -r "${i}" ]; then _LDC="${_LDC} ${i}" fi --MP_/nD2m3FmfImDp2u+ur0Mr4sg-- From owner-freebsd-current@freebsd.org Thu May 10 16: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 68D08FCFEEF; Thu, 10 May 2018 16:47:13 +0000 (UTC) (envelope-from db@db.net) Received: from artemis.db.net (artemis.db.net [45.32.229.41]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB8E8472B; Thu, 10 May 2018 16:47:12 +0000 (UTC) (envelope-from db@db.net) Received: from night.db.net (localhost [127.0.0.1]) by artemis.db.net (Postfix) with ESMTP id 6619F101BD; Thu, 10 May 2018 16:47:09 +0000 (UTC) Received: by night.db.net (Postfix, from userid 1000) id D298739813; Thu, 10 May 2018 12:47:08 -0400 (EDT) Date: Thu, 10 May 2018 12:47:08 -0400 From: Diane Bruce To: Steve Kargl Cc: Diane Bruce , Gleb Popov <6yearold@gmail.com>, freebsd-hackers , FreeBSD Current , FreeBSD ports list Subject: Re: Runtime loader issue Message-ID: <20180510164708.GA76611@night.db.net> References: <20180509234551.GA39526@troutmask.apl.washington.edu> <20180510142452.GA69005@night.db.net> <20180510151522.GA43677@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180510151522.GA43677@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.5 (2018-04-13) 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, 10 May 2018 16:47:13 -0000 On Thu, May 10, 2018 at 08:15:22AM -0700, Steve Kargl wrote: > On Thu, May 10, 2018 at 10:24:52AM -0400, Diane Bruce wrote: > > On Thu, May 10, 2018 at 10:46:31AM +0300, Gleb Popov wrote: > > > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > > > sgk@troutmask.apl.washington.edu> wrote: > > > ... > > > > Yep. > > See https://wiki.freebsd.org/libgcc%20problem > > > > Interesting page. I was aware that in the past you tried working > out a solution to the problem. I did not realize you docoumented > the issue. A few corrections to your wiki page. > > 1) The correct spelling of the name of the language is Fortran (with a > capital F). It has been the official standard spelling since Fortran > 90. Fixed > > 2) You have "... to always support quad math (*8) and ...". Quad > precision in gfortran is REAL(16) (the REAL*16 notation is nonstandard). I think I got it right this time... > > 3) "subsitute" is normally spelled with an extra 't'. :-) OOOps ;) fixed > > Very ;) > > Just started reading the source code. Don't scare the unwary. :-) ;) > > -- > Steve Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db From owner-freebsd-current@freebsd.org Thu May 10 17:22: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 1267EFD0DB1; Thu, 10 May 2018 17:22:01 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A36B36F021; Thu, 10 May 2018 17:22:00 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4AHLxra046778 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 May 2018 10:21:59 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4AHLxef046777; Thu, 10 May 2018 10:21:59 -0700 (PDT) (envelope-from sgk) Date: Thu, 10 May 2018 10:21:59 -0700 From: Steve Kargl To: Tijl Coosemans Cc: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Runtime loader issue Message-ID: <20180510172159.GA46553@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180509234551.GA39526@troutmask.apl.washington.edu> <20180510182151.409b7fb8@kalimero.tijl.coosemans.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180510182151.409b7fb8@kalimero.tijl.coosemans.org> User-Agent: Mutt/1.9.2 (2017-12-15) 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, 10 May 2018 17:22:01 -0000 On Thu, May 10, 2018 at 06:21:51PM +0200, Tijl Coosemans wrote: > On Wed, 9 May 2018 16:45:51 -0700 Steve Kargl wrote: > > > > So, the runtime loader finds 6 instead of 716, tries to link, > > fails, and issues an error message. There are a number ways to > > fix this issue. > > > > 1) By far, the best solution would be to stop hijacking the libgcc > > name in libraries installed on FreeBSD that are not related to > > actual GCC software. > > > > % ls -l /lib/libgcc* /usr/lib/libgcc* > > (trimming lines) > > /lib/libgcc_s.so.1 > > /usr/lib/libgcc.a@ -> libcompiler_rt.a > > /usr/lib/libgcc_eh.a > > /usr/lib/libgcc_eh_p.a > > /usr/lib/libgcc_p.a@ -> libcompiler_rt_p.a > > /usr/lib/libgcc_s.so@ -> ../../lib/libgcc_s.so.1 > > > > Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm > > aware that clang does not work on all archs and the ancient gcc > > lives on. > > > > 2) Given the expected push back againt solution 1), this solution > > proposes bumping the library version for /lib/libgcc_s.so.1 from > > 1 to some larger value, say, 10. It is unlikely that GCC will > > bump its shared library number anytime soon. GCC bumped it from > > 0 to 1 some 16 years ago. > > > > https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 > > > > This solution, however, papers over the general problem with > > name clashes. > > > > libgcc_s.so implements the _Unwind_* API to handle stack unwinding. This > code is shared between all compilers and languages because the stack can > contain frames from different compilers and languages. So, you cannot > change the name or version of the library. Well, yes one could change the name and/or shared library number. All those other tools would then need to be adapted to look for a renamed or number-bumped library. Yes, painful. > I've been testing the attached patch in combination with the ports tree > patch from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228046. > > The patch makes three changes to /etc/rc.d/ldconfig: > 1) Use 'sort -r' so /usr/local/lib/gcc7 appears before /usr/local/lib/gcc6. > 2) Move hardcoded paths like /lib and /usr/lib to /etc/defaults/rc.conf > so the order relative to other paths can be configured. > 3) Change the order of ldconfig_local_dirs and ldconfig_paths so /lib and > /usr/lib appear last. This brings rc.d/ldconfig in line with compilers > and rtld(1) which also search /lib and /usr/lib last. This appears to work around the problem with libgcc_s.so.1. It would be a welcomed solution to so-called "gfortran's FreeBSD issue", but is does not solve the problem with name clashes. It is possible to have two independent libraries for independent projects where no shuffling of order in hints will work. -- Steve From owner-freebsd-current@freebsd.org Thu May 10 19:22:57 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 74164FD417D; Thu, 10 May 2018 19:22:57 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: from puchar.net (puchar.net [194.1.144.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "puchar.net", Issuer "puchar.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AD63B878A3; Thu, 10 May 2018 19:22:56 +0000 (UTC) (envelope-from wojtek@puchar.net) Received: Received: from 127.0.0.1 (localhost [127.0.0.1]) by puchar.net (8.15.2/8.15.2) with ESMTPS id w4AJDiPB064759 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 May 2018 21:13:44 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Received: from localhost (puchar-wojtek@localhost) by puchar.net (8.15.2/8.15.2/Submit) with ESMTP id w4AJDdFm064756; Thu, 10 May 2018 21:13:39 +0200 (CEST) (envelope-from puchar-wojtek@puchar.net) Date: Thu, 10 May 2018 21:13:39 +0200 (CEST) From: Wojciech Puchar To: Gleb Popov <6yearold@gmail.com> cc: sgk@troutmask.apl.washington.edu, freebsd-hackers , FreeBSD Current , FreeBSD ports list Subject: Re: Runtime loader issue In-Reply-To: Message-ID: References: <20180509234551.GA39526@troutmask.apl.washington.edu> User-Agent: Alpine 2.20 (BSF 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Thu, 10 May 2018 19:48:42 +0000 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, 10 May 2018 19:22:57 -0000 just another - out of thousands - example that shared libraries are one of the worst thing invented in computing. Maybe except of single system wide shared library with constant interface. On Thu, 10 May 2018, Gleb Popov wrote: > On Thu, May 10, 2018 at 2:45 AM, Steve Kargl < > sgk@troutmask.apl.washington.edu> wrote: > >> In review PR 228007, it came to my attention some individuals are >> mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD >> issue". See >> >> https://lists.freebsd.org/pipermail/freebsd-fortran/2018-May/000124.html >> >> The problem can be summarized by the following >> >> % gfortran7 -o z h.f90 >> % ./z >> /lib/libgcc_s.so.1: version GCC_4.8.0 required by \ >> /usr/local/lib/gcc7/libgfortran.so.4 not found >> >> gfortran7 is installed from ports/lang/gcc7. This is not >> a "gfortran's FreeBSD issue". This is a FreeBSD loader issue. >> >> Specifically, there is a shared library name clash. >> >> % ldconfig -r | grep gcc_ >> 6:-lgcc_s.1 => /lib/libgcc_s.so.1 >> 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 >> >> % ldd z >> z: >> libgfortran.so.4 => /usr/local/lib/gcc7/libgfortran.so.4 (0x200645000) >> libm.so.5 => /lib/libm.so.5 (0x200a17000) >> libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x200a4b000) >> libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200a63000) >> libc.so.7 => /lib/libc.so.7 (0x200ca3000) >> >> So, the runtime loader finds 6 instead of 716, tries to link, >> fails, and issues an error message. There are a number ways to >> fix this issue. >> >> 1) By far, the best solution would be to stop hijacking the libgcc >> name in libraries installed on FreeBSD that are not related to >> actual GCC software. >> >> % ls -l /lib/libgcc* /usr/lib/libgcc* >> (trimming lines) >> /lib/libgcc_s.so.1 >> /usr/lib/libgcc.a@ -> libcompiler_rt.a >> /usr/lib/libgcc_eh.a >> /usr/lib/libgcc_eh_p.a >> /usr/lib/libgcc_p.a@ -> libcompiler_rt_p.a >> /usr/lib/libgcc_s.so@ -> ../../lib/libgcc_s.so.1 >> >> Why not use libcompiler_rt_s.so.1 (or libclang_s.so.1)? Yes, I'm >> aware that clang does not work on all archs and the ancient gcc >> lives on. >> >> 2) Given the expected push back againt solution 1), this solution >> proposes bumping the library version for /lib/libgcc_s.so.1 from >> 1 to some larger value, say, 10. It is unlikely that GCC will >> bump its shared library number anytime soon. GCC bumped it from >> 0 to 1 some 16 years ago. >> >> https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=43316 >> >> This solution, however, papers over the general problem with >> name clashes. >> >> 3) This solution is to actually fix the runtime loader. If an error >> occurs with loading a shared library, then iterate over the entries >> in the hints file to check to see if another hint would satisfy >> the linking. Here, instead of issuing the above error, the loader >> would find entry 716, and load the correct libgcc_s.so.1. >> >> Admittedly, I haven't looked to see how difficult this solution >> would be. >> >> 4) Bump the shared library number of the individual ports. As a proof >> of concept, I've done this with ports/lang/gcc6. >> >> % cat /usr/ports/lang/gcc6/files/patch-t-slibgcc >> --- libgcc/config/t-slibgcc.orig 2018-05-08 12:47:42.334495000 -0700 >> +++ libgcc/config/t-slibgcc 2018-05-08 12:45:26.872312000 -0700 >> @@ -20,7 +20,7 @@ >> >> SHLIB_EXT = .so >> SHLIB_SOLINK = @shlib_base_name@.so >> -SHLIB_SOVERSION = 1 >> +SHLIB_SOVERSION = 2 >> SHLIB_SONAME = @shlib_base_name@.so.$(SHLIB_SOVERSION) >> SHLIB_MAP = @shlib_map_file@ >> SHLIB_OBJS = @shlib_objs@ >> >> % ldconfig -r | grep gcc_ >> 6:-lgcc_s.1 => /lib/libgcc_s.so.1 >> 716:-lgcc_s.1 => /usr/local/lib/gcc7/libgcc_s.so.1 >> 766:-lgcc_s.2 => /usr/local/lib/gcc6/libgcc_s.so.2 >> >> % gfortran6 -o z h.f90 >> % ./z >> hello >> % ldd z >> z: >> libgfortran.so.3 => /usr/local/lib/gcc6/libgfortran.so.3 (0x200645000) >> libm.so.5 => /lib/libm.so.5 (0x20096c000) >> libgcc_s.so.2 => /usr/local/lib/gcc6/libgcc_s.so.2 (0x2009a0000) >> libquadmath.so.0 => /usr/local/lib/gcc7/libquadmath.so.0 (0x200bb7000) >> libc.so.7 => /lib/libc.so.7 (0x200df7000) >> >> This works for this particular name conflict. Hopefully, FreeBSD >> never needs to bump /lib/libgcc_s.so.1 to /lib/libgcc_s.so.2. This, >> however, introduces an incompatibility with what is actually distributed >> by GCC. >> >> Finally, can people stop referring to the above error as >> "gfortran's FreeBSD issue". This is a FreeBSD runtime loader issue. >> > > Our libgcc also lacks some functionality compared to the original one: > https://reviews.freebsd.org/D11482 > > >> -- >> Steve >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > > From owner-freebsd-current@freebsd.org Thu May 10 23:36: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 8DBADFDAF0C; Thu, 10 May 2018 23:36:53 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask", Issuer "troutmask" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 232C482F73; Thu, 10 May 2018 23:36:53 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) by troutmask.apl.washington.edu (8.15.2/8.15.2) with ESMTPS id w4ANapgG055326 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 10 May 2018 16:36:51 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.15.2/8.15.2/Submit) id w4ANap8V055325; Thu, 10 May 2018 16:36:51 -0700 (PDT) (envelope-from sgk) Date: Thu, 10 May 2018 16:36:51 -0700 From: Steve Kargl To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Runtime loader issue Message-ID: <20180510233651.GA54955@troutmask.apl.washington.edu> Reply-To: sgk@troutmask.apl.washington.edu References: <20180509234551.GA39526@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180509234551.GA39526@troutmask.apl.washington.edu> User-Agent: Mutt/1.9.2 (2017-12-15) 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, 10 May 2018 23:36:53 -0000 On Wed, May 09, 2018 at 04:45:51PM -0700, Steve Kargl wrote: > In review PR 228007, it came to my attention some individuals are > mis-characterizing a FreeBSD loader issue as "gfortran's FreeBSD > issue". See It seems we've had the same discussion 2 years ago. My time flies. ttps://lists.freebsd.org/pipermail/freebsd-ports/2016-August/104384.html -- Steve From owner-freebsd-current@freebsd.org Fri May 11 21:08: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 DC3EDFCD6ED for ; Fri, 11 May 2018 21:08:48 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6426372F2D for ; Fri, 11 May 2018 21:08:48 +0000 (UTC) (envelope-from bsam@passap.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 24B49FCD6E7; Fri, 11 May 2018 21:08:48 +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 F14AEFCD6E6 for ; Fri, 11 May 2018 21:08:47 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from forward104j.mail.yandex.net (forward104j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5301072F2B for ; Fri, 11 May 2018 21:08:46 +0000 (UTC) (envelope-from bsam@passap.ru) Received: from mxback15j.mail.yandex.net (mxback15j.mail.yandex.net [IPv6:2a02:6b8:0:1619::91]) by forward104j.mail.yandex.net (Yandex) with ESMTP id DC6D7455BA; Sat, 12 May 2018 00:08:43 +0300 (MSK) Received: from smtp1p.mail.yandex.net (smtp1p.mail.yandex.net [2a02:6b8:0:1472:2741:0:8b6:6]) by mxback15j.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 8gl2m30FmX-8hjWOrB4; Sat, 12 May 2018 00:08:43 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526072923; bh=QxsZpmZ0RqT0frTyGPHRTt9+p2xeljLCPdNywn0OaGI=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=SMqHgAtEe+bPfHaTJU9won8WBXAMqqGC1MoN/u5kBtQ28v9x+SBFe5CmmQpPk2G26 /4KQDtzuXcz8TMIMh2WpjtRZW9FI7g5F7z3nHYsY4kfZZsMxUSXHDuBQH3YUUOPRFu MOtfjKYXE8Zqn+AscRv+mgVOZa+qczpWZXDo07TI= Received: by smtp1p.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id LBkjq7Vo6j-8h0SfWop; Sat, 12 May 2018 00:08:43 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=passap.ru; s=mail; t=1526072923; bh=QxsZpmZ0RqT0frTyGPHRTt9+p2xeljLCPdNywn0OaGI=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=SMqHgAtEe+bPfHaTJU9won8WBXAMqqGC1MoN/u5kBtQ28v9x+SBFe5CmmQpPk2G26 /4KQDtzuXcz8TMIMh2WpjtRZW9FI7g5F7z3nHYsY4kfZZsMxUSXHDuBQH3YUUOPRFu MOtfjKYXE8Zqn+AscRv+mgVOZa+qczpWZXDo07TI= Authentication-Results: smtp1p.mail.yandex.net; dkim=pass header.i=@passap.ru Subject: Re: pkg, drm-next-kmod and base packages To: Andreas Nilsson , Theron Cc: Johannes Dieterich , current@freebsd.org References: <63f77348-5b6c-e149-b6a3-71909ea301bf@passap.ru> <7iq1xp.p8i5ke.0-qmf@smtp.gmail.com> From: Boris Samorodov Openpgp: preference=signencrypt Autocrypt: addr=bsam@passap.ru; prefer-encrypt=mutual; keydata= xsFNBFKPjHIBEACwdrpPbV9pGnP/MFO0lsubC1ruUr7y79tnT/gWKlI3i8gPPS3GG5FVFwjM 9YsSv7H5wxKlHa7ufFa8BETQQF+tBWlOy5lGh0a55M9qNCY+jlnAbmRRNdrIpr8ywHHd3eIr DBafMB6CG5GIgEMJ1OBcHmNuIUOd1A8Esi4eGpd6NFRcT3O58dC8wHfEqpdCVVX+mrPEWAno Q72i0q+j6NtsyTNTFEiACiuXeW+h2xl4zj09rr1CXlCcBV4SQ20uxJ4gegGapAMXzXDUpvCD X1M8wcjlUVa44PtTvGj5OxhGypKZJnz1CQcIQJ4qjPxvg6p8PsGnAaEWfdXPL5CH5GUmuaUt qMRbzyR/Bo/K8bYMYl5o/YcAjXopkn4ij1H3KACqE5YWvEwcfiNKX++uhuVhtja34sOTWJl9 ilboFJ9C9RDq/zE6oxF4vBGMVWjF4qm88P2PXWULLPPyhg98NxFMbH0XXWnOUt0x8yqY2v0t kz2sWn1ft/o09gQ0aaUtzYvG+cLg3FeU0EeXYum+jdTKdA27uKtTmgRuwQ135XIf0+4M5hrX pw2dBh/JljkQiv1lhKiCQrVBdS52nRvRXaCo7t0OiRR4y7268LYPr7ellCq3Ywykdj8bWvmt szYcnYBi7wiftHCid8wR0bQdyGRUcuc4IH4fCf7hS8trSjukWQARAQABzSJCb3JpcyBTYW1v cm9kb3YgPGJzYW1ARnJlZUJTRC5vcmc+wsF9BBMBCAAnBQJSj4yzAhsDBQkJZgGABQsJCAcD BRUKCQgLBRYDAgEAAh4BAheAAAoJEJYOILA6P20ooagP/3r6OfyiGW5B3Fv1ylBWp8lzHZVD mI8pGW7J4ubizPsz6t+CHBofNvCkrxjW7C1WDq7qRDfgqL6rYBV6D6GMtdUm5oKmnyJNNET5 hXRP7/ljzYDaLbBaVY5Oidu7OBS4k6RRwlypo5vFaI7/YJp6iIm80eIC6MCmPJpsRqdsY6pj ng5/F8obspP+HfrORHYLYRg8mt0PLG6UwkkiOdP48z2X0Arhjbt2v5QCDwOzwerE7JfN3/P6 Knf1Soiki9vWw6CAaC5K/oo/tdbvfiUzrzxSAaV8K7HQ4dVqaKFxI5xQ2GnafnEfyPLBZQQR WdmYJcL1qwCk4D76VrN2whR94+ZczPFji6jGCxOUo4mM/hqwq44KF9xi7asZmZC7/LHZ11ac j8NMEPHQJ4nmB7q9of4Wwu9XeJUrTt7oY+AQKpmewRxab5K0EJDd9IyfQusNgHHVpF2Jpa7U MAxClPtWdoXfRSk3esxeLhu33WJOpVpAUVeLIXF9g6EokOflV/0rb0onjuSeisVihvX/eG20 8eiSomt3xYgM+2ijGWugm5ie6eHkv5o34fcG9oanG71t9QIb7IgJ36UnLYGUcOyrpByUGEfg bYQgSEgSiDBbZBZVdM+aT2kJgbqRRYeqaqjmIXvSzL4c7zSRqQXv6h0L/P11CbMjycVNQ6uo iiP0eu5vzsFNBFKPjHIBEADUsIZuXuLo8baU85CU+Mv4gdyHwXzgIeNEG28O7Iu9bssY+Gt+ NiLI+4ZpBeQDbFzBGvyA/UoYDfURdY3KT6lXl2qamRaFz7SDtXuGpN9jDVgU048bbMjN4nk/ vV5ioqWw3V0x7eOiBtUbb17P1CVnnl249KyjdtMDu8jf7KRe2KgiFXgoL5ZeiGuN4g4n17VT H9DQCXJhIYPl5d7NEeGaUVKtPTEE1mClNt048dF/euduFRomxpwgXsg+tkSdZb1ffinYuFa7 mSMLg96LubVaels2rqQu097OO9GFqxyoBFzXtRwCOl2LbRJpG2ktJisin1zEshHx8slMC0km veXQv4S/LL33TNFPhfrbTJddMQhcrjwe4kDtdGY3XtBV2VEjUGRs63BSjtHPAQWx/JQTaBwx 5IPwuJAs0H0eJwjNtq+ZunzM1Dgbbtq4rQPsgrPIrtjHSv+u6ORW2wmd5uHxGyvADB8YyYRj R6scSLzLp7KrcFmkGq3RJcB3aDYi9r4TXr/gSZk4P0swhEXqo9oiddwRo7tv6JboRwltLG1F o91W5H8pwV5iG/R0EsM2k/aIAMOTBiZ2Lkk0bBH62hd/mp4p08z0E12QL/IYbH7VuXtz9ToA KiMtAAKg4nDe58ILAkfEAhNNsStSMOEjlXMz/6n7gsRrLljS16nmgd+8FQARAQABwsFlBBgB CAAPBQJSj4xyAhsMBQkJZgGAAAoJEJYOILA6P20odvEP/0KAbaBFAyJqhwXmj4ta1i55rkd+ 6vc46Az4trNZ6H/0XOJK5v9JGW1mz5aOURzSaSCitqS9uQa1qMssggn7a2pDRYA6LPKd0xgF 9KT68QMApN3KOtpFgn1D8rV6wywovntl3CpubiaDEmBD/fD7wrHiG+KsFzR48Dqzoth94D82 zIlCzfhbKDUzPwgc5ipds48MuP150WTwyKvOytwZbH/0RBGlqw/jkA6z3P86We4TuD0RFHZl /hpuSNadbUkfAOYI0LUfSFz/uYds08Rjf/YIawjA34mZFsDsWuoHhHqjl/x9uHA/o553LSw7 TmW/oR1xja/sWBaub/9WG9ZwuhPFE25DIG2eFQdv9d7XR7dyF+SIIkhiq4TuhD8hYYWPnvfN nzI9pfq3b9ag31P1ZHjpy9WxDplW7nTQq1yGLYOsd8Hoeh+QCY7PC/Ws8N566kW0bcUM1d12 2ZXA5XS0EBabmaAccuFtrIMt86XXgPYUqDOW4N/qKdF1dG+bhPPlFN3Lx9Sf3fbbNvJaI1DY bPgGUnCzctuLLfiARaFdgACXVhJ8ZhB6h7zPBOK8SB/bVSOqxcZh9elnusnkelNg57Up1qX3 pgkTpbOtvicdN2gogQQvtV40Nljrxmu2o0MoMcyqAxVG7KhKUih38fFqqrWEpFsVaLJeFk1u 4YL+0DfP Message-ID: <628efb27-a8de-13da-7969-1811a48fe9ae@passap.ru> Date: Sat, 12 May 2018 00:08:42 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: ru-RU 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, 11 May 2018 21:08:49 -0000 10.05.2018 19:05, Andreas Nilsson пишет: > On Thu, May 10, 2018 at 5:30 PM, Theron wrote: > >> On 05/10/18 03:45, Johannes Dieterich wrote: >> >>> Hi >>> >>> On Wednesday, May 9, 2018, Boris Samorodov wrote: >>> >>>> Hi All, >>>> >>>> I use self-built base packages. How can I test/use drm-next-kmod? >>>> Packages for kernel and drm-nex-kmod are in conflict: >>>> ----- >>>> Checking integrity... done (1 conflicting) >>>> - drm-next-kmod-4.11.g20180224 [FreeBSD] conflicts with >>>> FreeBSD-kernel-pkg64x-12.0.s20180509041454 [installed] on >>>> /boot/modules/drm.ko >>>> Checking integrity... done (0 conflicting) >>>> ----- >>>> >>> Since I don't have a system with pkgbase configured, is there a way to >>> figure out what files conflict? >>> >> The pkg output indicates that /boot/modules/drm.ko is the conflicting file. >> >>> It surprises me that there are any since we do not override anything >>> normally (some kernel modules are indeed overlapping but they get installed >>> in different directories). >>> >> On a non-pkgbase -CURRENT system, drm.ko and drm2.ko from base are in >> /boot/kernel/, while drm.ko from drm-stable-kmod is in /boot/modules/. Any >> kernel modules from base being placed outside of /boot/kernel is not what I >> would expect for a non-pkgbase system; is there a reason pkgbase should not >> follow this rule? > > I recently converted my system to pkgbase, but I have no such package as > FreeBSD-kernel-pkg64x. How and from where did you get the sources? That is my custom kernel. I build that one and GENERIC plus their counterparts with debug symbols per each build. > I seem to remember that the git repo FreeBSDDesktop > /freebsd-base-graphics > shipped the > module in /boot/modules. If you are using that git repo, you do not need > the port. Actually my point is that pkg-base packages and ports packages are in conflict and cannot coexist currently. > Best regards > Andreas -- WBR, bsam From owner-freebsd-current@freebsd.org Sat May 12 15:02: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 00AC2FDFF6E for ; Sat, 12 May 2018 15:02:16 +0000 (UTC) (envelope-from se@freebsd.org) Received: from mailout09.t-online.de (mailout09.t-online.de [194.25.134.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mailout00.t-online.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 77A9B7FE37 for ; Sat, 12 May 2018 15:02:15 +0000 (UTC) (envelope-from se@freebsd.org) Received: from fwd36.aul.t-online.de (fwd36.aul.t-online.de [172.20.26.137]) by mailout09.t-online.de (Postfix) with SMTP id CFAA34256EC9 for ; Sat, 12 May 2018 16:54:51 +0200 (CEST) Received: from Stefans-MBP-10.fritz.box (Z6NtQgZOZhY-3zfsNM8loQ7+pW6F4tg7Qa+UidsDxYB5Uu01N7iXzwtsR+beDx9grJ@[84.154.105.176]) by fwd36.t-online.de with (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384 encrypted) esmtp id 1fHVv5-1XcLOS0; Sat, 12 May 2018 16:54:47 +0200 To: FreeBSD Current From: Stefan Esser Subject: Strange problem with tar in -CURRENT (VM problem?) Openpgp: preference=signencrypt Autocrypt: addr=se@freebsd.org; prefer-encrypt=mutual; keydata= xsBNBFVxiRIBCADOLNOZBsqlplHUQ3tG782FNtVT33rQli9EjNt2fhFERHIo4NxHlWBpHLnU b0s4L/eItx7au0i7Gegv01A9LUMwOnAc9EFAm4EW3Wmoa6MYrcP7xDClohg/Y69f7SNpEs3x YATBy+L6NzWZbJjZXD4vqPgZSDuMcLU7BEdJf0f+6h1BJPnGuwHpsSdnnMrZeIM8xQ8PPUVQ L0GZkVojHgNUngJH6e21qDrud0BkdiBcij0M3TCP4GQrJ/YMdurfc8mhueLpwGR2U1W8TYB7 4UY+NLw0McThOCLCxXflIeF/Y7jSB0zxzvb/H3LWkodUTkV57yX9IbUAGA5RKRg9zsUtABEB AAHNKVN0ZWZhbiBFw59lciAoWWFob28hKSA8c3QuZXNzZXJAeWFob28uZGU+wsCWBBMBCgBA AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AWIQSjceplnAvsyCtxUxNH67XvWv31RAUC WvLvqwUJCyUBEwAKCRBH67XvWv31REySCACc6vqcSFQCRyBRc2CV5ZBjbbnTy7VBoXbUS3/c 4Hn8I0YQ39q7//2z8vYsgLeM1mMXL4PUIU/0f0dBAFBLpxV7bntGzyCJls6SeGS/qcQKhqaI 6I7NcWg8OkIJIhUL6q238cS1ql9pU65fyHe0PP8JS08m81PDpX2/4wTE6h2jgYUy55eXRzoF MEjr1S8SSnidsBem27o7iWu9ltJsUtE86071iZlLzbuHv2nvucrjAV9cK9tHrxYT/YiY8QhT L48iWj2xIjLjg1ebmgIFZ2k881we/KTIoUugqOOR1gDSc4qwM8CA388cN3frjtl98CwhAT5T UV8tIDqri+/Z1AKwzsBNBFVxiRIBCACxI/aglzGVbnI6XHd0MTP05VK/fJub4hHdc+LQpz1M kVnCAhFbY9oecTB/togdKtfiloavjbFrb0nJhJnx57K+3SdSuu+znaQ4SlWiZOtXnkbpRWNU eMm+gtTDMSvloGAfr76RtFHskdDOLgXsHD70bKuMhlBxUCrSwGzHaD00q8iQPhJZ5itb3WPq z3B4IjiDAWTO2obD1wtAvSuHuUj/XJRsiKDKW3x13cfavkad81bZW4cpNwUv8XHLv/vaZPSA ly+hkY7NrDZydMMXVNQ7AJQufWuTJ0q7sImRcEZ5EIa98esJPey4O7C0vY405wjeyxpVZkpq ThDMurqtQFn1ABEBAAHCwHwEGAEKACYCGwwWIQSjceplnAvsyCtxUxNH67XvWv31RAUCWvLv qwUJCyUBGQAKCRBH67XvWv31RLnrB/9gzcRlpx71sDMosoZULWn7wysBJ/8AIEfIByRaHQe3 pn/KwE57pB+zFbbQqB7YzeZb7/UUgR4zU2ZbOcEfwDZcHUbj0B3fGRsS3t0uiLlAd8w0sBZb SxrqzjdpDjIbOZkxssqUmvrsN67UG1AFWH9aD24keBS7YjPBS8hLxPeYV+Xz6vUL8fRZje/Z JgiBMIwyj6g2lH/zkdnxBdC0iG1xxJOLTaghMMeQyCdH6ef8+VMyAlAJsMckbOTvx63tY8z7 DFcrnTJfbe1EziRilVsEaK8tTzJzhcTfos+f3eBYWEilxe5HzIhYKJeC7lmsSUcGwa6+9VRg a0ctmi9Z8OgX Message-ID: <19a18e0f-d881-cecd-3bae-4145fac10be4@freebsd.org> Date: Sat, 12 May 2018 16:54:46 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-ID: Z6NtQgZOZhY-3zfsNM8loQ7+pW6F4tg7Qa+UidsDxYB5Uu01N7iXzwtsR+beDx9grJ X-TOI-MSGID: 62171993-49cf-46d4-93e0-52235dbef88f 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, 12 May 2018 15:02:16 -0000 While searching for the reason an upgrade of math/atlas failed on my amd64 -CURRENT system, I found that tar fails to create an archive of some 10KB. It is killed (-9) after some 30 seconds during which it grows seemingly without bounds. The port processes some TAR files in order to fixup paths in them with the following shell loop (edited for readability): cd ${WRKDIR}/ATLAS/CONFIG/ARCHS for t in *.tgz ; do /bin/mv ${t} ${t}.bak /usr/bin/tar -s '/gcc/gcc6/' -xf ${t}.bak /usr/bin/tar -czf ${t} ${t%.tgz} # (***) /bin/rm -f -r ${t%.tgz} ${t}.bak done The command that fails is the one marked (***) and I have tried to trace it with ktrace and truss, but only see that a large amount of memory is mapped and the tar process is killed without having produced any output. I have added "-v" to watch progress and the log does also indicate, that tar does not even start to write to the archive. Removal of the "z" option makes no difference. Typical "ps l" output is: UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 2269 2254 0 30 0 105946804 21244044 pfault D 0 0:31,48 /usr/bin/tar -czf Core232SSE3.tgz Core232SSE3 (bsdtar) VSZ is 105946804 KB or about 100 GB, RSS 21 GB when tar is killed ... The files to be processed are: -rw-r--r-- 1 root wheel 11399 May 12 16:40 AMD64K10h32SSE3.tgz -rw-r--r-- 1 root wheel 11697 May 12 16:40 AMD64K10h64SSE3.tgz -rw-r--r-- 1 root wheel 1305 May 12 16:40 BOZOL1.tgz -rw-r--r-- 1 root wheel 9909 May 12 16:40 Core232SSE3.tgz drwxr-xr-x 5 root wheel 9 Feb 25 2009 Core264SSE3/ -rw-r--r-- 1 root wheel 0 May 12 16:40 Core264SSE3.tgz -rw-r--r-- 1 root wheel 10212 May 14 2011 Core264SSE3.tgz.bak -rw-r--r-- 1 root wheel 8544 May 14 2011 Corei164SSE3.tgz [...] The failure may be caused by a race-condition, since sometimes tar fails on a later file (e.g. Corei164SSE3.tgz). If I replace "${TAR} -czf" with "gtar -czf", then the port can be built. But I do not think that this is a problem in BSDTAR, since the failure can be reproduced (also after a buildworld/buildkernel and reboot), but there have been no changes to BSDTAR since the libarcjive upgrade in January. I guess this is a VM problem, that happens to show itself in this specific program invocation. (The system runs without other obvious problems and tar works outside this specific usage in the port ...) Any ideas? Best regards, STefan